Recovering from iphodroid

From iDroid Project

Users who have previously used iPhodroid but have decided to use the official OpeniBoot have experienced some issues in upgrading. Here are some workarounds for some common issues. Take note though, because iPhodroid's source code is not public (which is against GPL), not all issues can be fixed.

Contents 1 OpeniBoot Issues 1.1 Directly boots into OpeniBoot Console 2 Bricked Devices 2.1 DFU Restore 2.2 NOR Backup 2.3 iRecovery

OpeniBoot Issues

Directly boots into OpeniBoot Console

Users who have recently upgraded to use OpeniBoot from iPhodroid sometimes experience directly booting into OpeniBoot console. The OS Menu does not display and "WELCOME TO OPENIBOOT" is shown instead. This is because "opib-hide-menu true" is set in iPhodroid. This flag is saved into settings and will persist even after uninstall and install of OpeniBoot. To fix this:

1. Install OpeniBoot if you haven't.
2. It will automatically boot into the OpeniBoot console.
3. Open Linux or OS X terminal, and enter the command:

   sudo ./oibc

4. Once you are in the OpeniBoot console, enter these commands:

   printenv

   If it displays "opib-hide-menu true" then set it to false by entering the command:

   setenv opib-hide-menu false

   saveenv

5. Then reboot:

   reboot

The Menu should now be displayed.

Bricked Devices

Sometimes, iOS fails to boot after an installation or un-installation of iPhodroid. This usually manifests as booting into iOS with the Apple Logo showing then it suddenly restarts or powers off. Here are some possible ways to fix this.

DFU Restore

Try going into DFU mode and restore with iTunes.

NOR Backup

If DFU does not work, maybe the NOR is corrupted as iPhodroid can "rape your NOR card"[sic]. Try to restore your NOR (refer to the NOR Backup guide for details).

iRecovery

If you do not have a NOR Backup lying somewhere and DFU won't work, then try using this iRecovery Guide from iHackintosh.

If that still doesn't work, then you have an expensive paperweight.