[Q] In a jam. Phone won't boot despite wipes, wont even restore nand

cabbieBot · Sep 30, 2010 at 4:03 PM

*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 "Error: run 'nandroid-mobile.sh 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

seems like this thread may hold a clue: http://forum.xda-developers.com/showthread.php?t=608400

cabbieBot · Sep 30, 2010 at 4:15 PM

well i dont know if its a problem with the sd card. i put the latest nand on a different sd card, popped it in and still giving me the "Error: run 'nandroid-mobile.sh restore via adb" msg and wont boot up past splash screen

rutter9 · Dec 31, 2007 301 7 0

Are you using clockwork? If so you need to do the wipes through adb since clockwork does not work the greatest. I prefer RA recovery.

Personally I would just wipe the data and reflash my rom. I always have my apps backed up with Titanium, not sure if you do or not.

cabbieBot · Sep 30, 2010 at 4:25 PM

using RA

wiped data multiple times and tried reflashing rom, nothin doin

im going to try the full starting over method with the pc136 img in the bootloader now

cabbieBot · Sep 30, 2010

Okay, huge progress.

I did the Starting Over method: http://forum.xda-developers.com/showthread.php?t=715915

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.

I have cross-posted this thread over to androidforums.com for those tuning in. link

_MetalHead_ · Sep 30, 2010 at 5:43 PM

Have you tried flashing a rooted stock PC36IMG.zip? When I get into a bind like yours that's the first thing I do. It will get you back up to speed with the current update including the radios.

Here is a link to the most current one. It will put clockwork as your recovery but you can always flash Amon_RA afterwards.

cabbieBot · Sep 30, 2010 at 5:50 PM

_MetalHead_ said:
Have you tried flashing a rooted stock PC36IMG.zip? When I get into a bind like yours that's the first thing I do. It will get you back up to speed with the current update including the radios.

Here is a link to the most current one. It will put clockwork as your recovery but you can always flash Amon_RA afterwards.

yea i did, the starting over method i linked is based on the 1.47.651.1 RUU. Its old, but it got the phone booted.

I might have to try that one.

I flashed 3.3, rebooted and im back stuck on the bootscreen for 15 minutes so far. 5 more minutes of this and I'm going to try a battery pull because one time that worked for me after a hangup trying to flash a new ROM

cabbieBot · Sep 30, 2010 at 5:51 PM

ah crap, know what? i forgot to full wipe before flashing 3.3. dammit.

playya · Sep 30, 2010 at 6:12 PM

Not sure if this pertains to you but I got this error run 'nandroid-mobile.sh restore' via adb" when I tried to do a nand restore and my battery was low

cabbieBot · Sep 30, 2010 at 6:24 PM

playya said:
Not sure if this pertains to you but I got this error run 'nandroid-mobile.sh restore' via adb" when I tried to do a nand restore and my battery was low

in the big battery drain i mentioned in the OP, it brought me down to 10%. I powered down, popped in a battery with a good charge and booted up. I dont remember whether I wiped cache/dalvik as i booted up the first time with the good battery or not, or whether that matters

cabbieBot · Sep 30, 2010 at 6:38 PM

_MetalHead_ said:
Have you tried flashing a rooted stock PC36IMG.zip? When I get into a bind like yours that's the first thing I do. It will get you back up to speed with the current update including the radios.

Here is a link to the most current one. It will put clockwork as your recovery but you can always flash Amon_RA afterwards.

whoa whoa whoa...was i really supposed to flash this, or do it through the bootloader? I just did it through the bootloader, and after it was done and i loaded into clockwork and selected reboot system...it reboots, splash screen, back into clockwork with E: Invalid command argument.

cabbieBot · Sep 30, 2010 at 7:07 PM

Here's where im at:

Used bootloader to install the PC36IMG Metalhead 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.

cabbieBot · Sep 30, 2010 at 7:13 PM

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.

cabbieBot · Sep 30, 2010 at 8:03 PM

sigh...tried to flash RA manually via fastboot, per this thread: http://forum.xda-developers.com/showthread.php?t=705026

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

_MetalHead_ · Sep 30, 2010 at 8:29 PM

cabbieBot said:
whoa whoa whoa...was i really supposed to flash this, or do it through the bootloader? I just did it through the bootloader, and after it was done and i loaded into clockwork and selected reboot system...it reboots, splash screen, back into clockwork with E: Invalid command argument.

You did it right, it's supposed to be done through the bootloader. I don't know why you're continuing to have issues. Are you currently still able to boot into a ROM?

Per the thread for Amon_RA, it looks like the commands you entered for fastboot were incorrect. That could be why you got that error.

cabbieBot · Sep 30, 2010 at 9:27 PM

i changed the filename but ill try redownloading and leaving it exactly as is

cabbieBot · Oct 3, 2010 at 3:38 AM

tried both the fastboot and terminal method and i still cant get off clockwork. im stumped.

cabbieBot · Oct 5, 2010 at 8:29 PM

I'm just tried this method and got the result quoted after:

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

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
~ #

im wondering if the flash_image file is in the wrong place. I flashed this rom before fresh 3.3: http://forum.xda-developers.com/showthread.php?t=791019

A search using root explorer for 'flash_image' revealed two results:

/data/data/com.koushikdutta.rommanager/files/flash_image
/system/xbin/flash_image

hmmm...?

cabbieBot · Oct 5, 2010 at 8:38 PM

sonofa....

i took a look in the bootloader and I have S-ON. No wonder this is giving me crap. now i got to figure that out how to turn it back off then try this again. Lost my engineering bootloader, it seems ;( My fault for not reading enough

cabbieBot · Oct 5, 2010 at 9:01 PM

ive never used unrevoked, but is it possible for me to use unrevoked forever to turn S-OFF even though i never use unrevoked3

[Q] In a jam. Phone won't boot despite wipes, wont even restore nand

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member