Sometimes hax go awry. When we’re lucky they only go slightly awry and things are relatively easy to recover once you get all the tools and ducks lined up. In this case it was an Asus Transformer TF101 that the BIL of a friend had tried to root and rom about a year ago. APPARENTLY about a year ago there was a fairly common bug in the tools available that resulted in devices like the Transformer getting stuck in a boot-loop where they’ll only start in recovery mode but won’t ever boot up android by themselves without user-intervention. That user-intervention for reference is:
- Press and hold Power and Vol- until the device reboots and small white text shows up saying press Vol+ within 5seconds for recovery. Do not press Vol+.
- It will then prompt you to cold-boot in to either recovery or android, follow the directions on screen to select android and start.
That seems rather annoying to have to do every time you restart the bloody thing. The permanent fix requires either root access via terminal emulator under the installed version of android, or running a remote shell on it with the Android sdk. I chose the latter.
As with all ASDK tomfoolery, start the adb server
Check to make sure the device shows up
Start the required remote shell session
Run the follow magic command to make everything happy again
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
And then reboot the device.
Once you know it works, take a picture of your haxxing assistant and post to social media.
[PiwigoPress id=67 url=’http://gallery.justanotherdave.ca/’ size=’me’ desc=1 class=’img-shadow’]