• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root **FAIL** calling upon the AF braintrust. Phone can't boot up despite wipes/restores

cabbie

Android Expert
Mar 23, 2010
1,333
553
Heres how it happened.

*I bought the pro version of twidroyd
*Bit later noticed some big battery drain
*Rebooted
*Had a ton of process.acore FCs
*Uninstalled twidroyd
*Continued to have issues
*Cache/dalvik wipe
*Issues remained
*Attempted nand restore to one I made earlier today
*Had error asking me to restore via adb
*Phone rebooted and would not go past the splash screen...20+ minutes
*Reboot into recovery, factory wipe
*Phone not going past splash screen
*Tried another nand restore with one I made last week....failed with previous error
*Phone not going past splash screen
*Tried restoring with my oldest nand...the one I made after the 'starting over' method from a couple months ago. After about 15 minutes (and 10 lines of "..............") it finally finished and rebooted
*Phone not going past splash screen
*Battery pull

nothing :( I don't think its hopeless because I can still boot into the bootloader and get into recovery, but I have no idea how to fix this. I can't fix this myself, I've exhausted my own methods. I am now phoneless and out of contact with the world while awaiting advice about how I can fix this, whether it by RUU or some other means (anything but RUU :( )

halp ;(
 
Heres how it happened.

*I bought the pro version of twidroyd
*Bit later noticed some big battery drain
*Rebooted
*Had a ton of process.acore FCs
*Uninstalled twidroyd
*Continued to have issues
*Cache/dalvik wipe
*Issues remained
*Attempted nand restore to one I made earlier today
*Had error asking me to restore via adb
*Phone rebooted and would not go past the splash screen...20+ minutes
*Reboot into recovery, factory wipe
*Phone not going past splash screen
*Tried another nand restore with one I made last week....failed with previous error
*Phone not going past splash screen
*Tried restoring with my oldest nand...the one I made after the 'starting over' method from a couple months ago. After about 15 minutes (and 10 lines of "..............") it finally finished and rebooted
*Phone not going past splash screen
*Battery pull

nothing :( I don't think its hopeless because I can still boot into the bootloader and get into recovery, but I have no idea how to fix this. I can't fix this myself, I've exhausted my own methods. I am now phoneless and out of contact with the world while awaiting advice about how I can fix this, whether it by RUU or some other means (anything but RUU :( )

halp ;(

Yuo probably got the adb error because your battery was under 30%. Charge it up a little with the phone off and try the nand again. To be on the safe side, leave it plugged in to ac power while attempting to restore.
 
Upvote 0
Damn, that usually solves my problem when I get that message...

Have you tried the starting over method where you load the PC36IMG file in bootloader?

I know you loaded a nand that you did after using that method but maybe running all of the steps again will work.

its come to that. i just need to back and find the thread. i even tried putting the latest nand on a different sd card and that didnt work.
 
Upvote 0
How long did you wait on the splash screen.

I was playing with overclock and hung my phone hard. I had to pull the battery to turn it off.

When I turned it back on it was on the white Evo 4G screen for a LONG time - like 5+ minutes and then the boot animation for 3-4x as long as normal. It finally came back and it seemed to have backed off the CPU clock to the previous setting.

If that doesn't work I'd do liek the previous guy suggested. Factory reset, clear cache, clear dalvik and re-flash ROM.
 
Upvote 0
Okay, huge progress.

I did the Starting Over method: How to start over: Fully rooted stock 1.47.651.1 in one shot (no adb!) - xda-developers

Phone booted, never thought I'd be so damn happy to see that sprint bootscreen.

However: Rebooted back into recovery, attempted nand restore again, and got the adb error. I noticed though that the phone has RA version 1.7.0.1 which I think is outdated. Also noticed my radio was 2.05.00.06.10 which i know is outdated so my wimax radio is probably as well.

Now attempting to re-flash Fresh3.3 and going from there.
 
Upvote 0
Here's where im at:

Used bootloader to install the PC36IMG Metalhead on XDA suggested
Phone wouldnt boot despite multiple restarts, took me right back to clockwork
Tried flashing fresh3.3, but reboots still took me right back to clockwork
Decided to try and flash PC36IMG
Phone booted up into fresh 3.3.

Wow.

Last step of the puzzle is to get back to RA recovery and restore my nand. I grabbed ROM manager from the market and it says I have RA already, but when I boot into recovery its clockwork. Lil confused about that, I can't restore till I get RA back.ROM Mgr said clockwork wasnt even installed when I opened it, just said I had RA. But when I reboot into recovery, it still brings me to clockwork. I tried flashing clockwork so ROM Mgr would recognize it had it, then re-flashed RA over it and rebooted into recovery, but still bringing me to clockwork. I tried using the QuickBoot app from the market to reboot into recovery, still clockwork. Just need to get RA back and not sure how.
 
Upvote 0
Here's where im at:

Used bootloader to install the PC36IMG Metalhead on XDA suggested
Phone wouldnt boot despite multiple restarts, took me right back to clockwork
Tried flashing fresh3.3, but reboots still took me right back to clockwork
Decided to try and flash PC36IMG
Phone booted up into fresh 3.3.

Wow.

Last step of the puzzle is to get back to RA recovery and restore my nand. I grabbed ROM manager from the market and it says I have RA already, but when I boot into recovery its clockwork. Lil confused about that, I can't restore till I get RA back.ROM Mgr said clockwork wasnt even installed when I opened it, just said I had RA. But when I reboot into recovery, it still brings me to clockwork. I tried flashing clockwork so ROM Mgr would recognize it had it, then re-flashed RA over it and rebooted into recovery, but still bringing me to clockwork. I tried using the QuickBoot app from the market to reboot into recovery, still clockwork. Just need to get RA back and not sure how.
Flash clockwork in rom manager then flash ra and you should be good
 
Upvote 0
sigh...tried to flash RA manually via fastboot, per this thread: [Recovery] [28-August-2010] RA-evo-v1.8.0 - xda-developers

this is what happened.

c:\sdk\tools>fastboot flash recovery recoveryRA1.8.img
sending 'recovery' (3750 KB)... OKAY [ 1.069s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.582s
 
Upvote 0
I'm not sure if you got it working or not, or if this will help you, but it was the only way i was able to go from clockwork to RA.

-You'll need to download the androidsdk if you don't have it.
-Place the amon ra recovery image in the main directory of your sd card.
-DO NOT type the $ or the #'s. Also, you will only need to use the su command if after you enter adb shell you're presented with a $. If you see the #, skip the su command.

---HOW TO FLASH CUSTOM RECOVERY IMAGE---
1. Boot your phone into recovery mode
2. Plug your phone into your PC
3. Open cmd on PC and change directory to your androidsdk/tools folder
4. Run the following command(s):
adb shell
$su (not required if you have root already)
#mount -a (You might get some error messages, ignore it, keep going)
#flash_image recovery /sdcard/recovery-RA-evo-v1.8.0.img
reboot recovery

Can't remember where i found the steps, but whoever posted them was a godsend. I tried a lot of different methods before i came across this one and it was very easy. I really hope this helps you (signed up for the forums just to post this lol). Good luck.
 
Upvote 0
This is what I get. the directory and file names are correct. :(

C:\sdk\tools>adb shell
~ # mount -a
mount -a
mount: mounting /dev/block/mmcblk0p2 on /sd-ext failed: No such file or director
y
~ # flash_image recovery /sdcard/ra18.img
flash_image recovery /sdcard/ra18.img
mtd: erase failure at 0x00000000 (I/O error)
mtd: erase failure at 0x00000000 (I/O error)
mtd: skipping write block at 0x00000000
mtd: erase failure at 0x00020000 (I/O error)
mtd: erase failure at 0x00020000 (I/O error)
mtd: skipping write block at 0x00020000
mtd: erase failure at 0x00040000 (I/O error)
mtd: erase failure at 0x00040000 (I/O error)
mtd: skipping write block at 0x00040000
mtd: erase failure at 0x00060000 (I/O error)
mtd: erase failure at 0x00060000 (I/O error)
mtd: skipping write block at 0x00060000
mtd: erase failure at 0x00080000 (I/O error)
mtd: erase failure at 0x00080000 (I/O error)
mtd: skipping write block at 0x00080000
mtd: erase failure at 0x000a0000 (I/O error)
mtd: erase failure at 0x000a0000 (I/O error)
mtd: skipping write block at 0x000a0000
mtd: erase failure at 0x000c0000 (I/O error)
mtd: erase failure at 0x000c0000 (I/O error)
mtd: skipping write block at 0x000c0000
mtd: erase failure at 0x000e0000 (I/O error)
mtd: erase failure at 0x000e0000 (I/O error)
mtd: skipping write block at 0x000e0000
mtd: erase failure at 0x00100000 (I/O error)
mtd: erase failure at 0x00100000 (I/O error)
mtd: skipping write block at 0x00100000
mtd: erase failure at 0x00120000 (I/O error)
mtd: erase failure at 0x00120000 (I/O error)
mtd: skipping write block at 0x00120000
mtd: erase failure at 0x00140000 (I/O error)
mtd: erase failure at 0x00140000 (I/O error)
mtd: skipping write block at 0x00140000
mtd: erase failure at 0x00160000 (I/O error)
mtd: erase failure at 0x00160000 (I/O error)
mtd: skipping write block at 0x00160000
mtd: erase failure at 0x00180000 (I/O error)
mtd: erase failure at 0x00180000 (I/O error)
mtd: skipping write block at 0x00180000
mtd: erase failure at 0x001a0000 (I/O error)
mtd: erase failure at 0x001a0000 (I/O error)
mtd: skipping write block at 0x001a0000
mtd: erase failure at 0x001c0000 (I/O error)
mtd: erase failure at 0x001c0000 (I/O error)
mtd: skipping write block at 0x001c0000
mtd: erase failure at 0x001e0000 (I/O error)
mtd: erase failure at 0x001e0000 (I/O error)
mtd: skipping write block at 0x001e0000
mtd: erase failure at 0x00200000 (I/O error)
mtd: erase failure at 0x00200000 (I/O error)
mtd: skipping write block at 0x00200000
mtd: erase failure at 0x00220000 (I/O error)
mtd: erase failure at 0x00220000 (I/O error)
mtd: skipping write block at 0x00220000
mtd: erase failure at 0x00240000 (I/O error)
mtd: erase failure at 0x00240000 (I/O error)
mtd: skipping write block at 0x00240000
mtd: erase failure at 0x00260000 (I/O error)
mtd: erase failure at 0x00260000 (I/O error)
mtd: skipping write block at 0x00260000
mtd: erase failure at 0x00280000 (I/O error)
mtd: erase failure at 0x00280000 (I/O error)
mtd: skipping write block at 0x00280000
mtd: erase failure at 0x002a0000 (I/O error)
mtd: erase failure at 0x002a0000 (I/O error)
mtd: skipping write block at 0x002a0000
mtd: erase failure at 0x002c0000 (I/O error)
mtd: erase failure at 0x002c0000 (I/O error)
mtd: skipping write block at 0x002c0000
mtd: erase failure at 0x002e0000 (I/O error)
mtd: erase failure at 0x002e0000 (I/O error)
mtd: skipping write block at 0x002e0000
mtd: erase failure at 0x00300000 (I/O error)
mtd: erase failure at 0x00300000 (I/O error)
mtd: skipping write block at 0x00300000
mtd: erase failure at 0x00320000 (I/O error)
mtd: erase failure at 0x00320000 (I/O error)
mtd: skipping write block at 0x00320000
mtd: erase failure at 0x00340000 (I/O error)
mtd: erase failure at 0x00340000 (I/O error)
mtd: skipping write block at 0x00340000
mtd: erase failure at 0x00360000 (I/O error)
mtd: erase failure at 0x00360000 (I/O error)
mtd: skipping write block at 0x00360000
mtd: erase failure at 0x00380000 (I/O error)
mtd: erase failure at 0x00380000 (I/O error)
mtd: skipping write block at 0x00380000
mtd: erase failure at 0x003a0000 (I/O error)
mtd: erase failure at 0x003a0000 (I/O error)
mtd: skipping write block at 0x003a0000
mtd: erase failure at 0x003c0000 (I/O error)
mtd: erase failure at 0x003c0000 (I/O error)
mtd: skipping write block at 0x003c0000
mtd: erase failure at 0x003e0000 (I/O error)
mtd: erase failure at 0x003e0000 (I/O error)
mtd: skipping write block at 0x003e0000
mtd: erase failure at 0x00400000 (I/O error)
mtd: erase failure at 0x00400000 (I/O error)
mtd: skipping write block at 0x00400000
mtd: erase failure at 0x00420000 (I/O error)
mtd: erase failure at 0x00420000 (I/O error)
mtd: skipping write block at 0x00420000
mtd: erase failure at 0x00440000 (I/O error)
mtd: erase failure at 0x00440000 (I/O error)
mtd: skipping write block at 0x00440000
mtd: erase failure at 0x00460000 (I/O error)
mtd: erase failure at 0x00460000 (I/O error)
mtd: skipping write block at 0x00460000
error writing recovery: No space left on device
~ # reboot recovery
reboot recovery
/sbin/sh: reboot: not found
~ #
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones