Root Stuck in boot-up screen.

[doogald]

Hey guys, me again

I recently dropped my phone and it ended up doing the same thing, being stuck on the droid load-up screen.
I did VolDn>Recovery>Reboot System now [It won't let me scroll down to anything else] but that didn't do anything.

I believe that we installed the trackball-optional recovery, right? If so, you *should* be able to scroll down the recovery menu with the green (call) key, and select an option with the red (end call) key.

If you can scroll, and you created a backup using "Backup/Restore", you can try restoring an old backup. Otherwise, you can try a "Wipe data/factory reset" and reset the phone from scratch.

But I'd be shocked that dropping the phone caused some problem that would be fixed by wipe data. Anyway, report back if you can or cannot get one of those things to work.

 

[kloroformkandi]

Ahh I didn't think to use the green/call key to scroll! >_>

I was able to scroll to backup/restore. Restore was 'completed', but sadly my phone still won't turn on properly.

I have no idea if dropping it actually had anything to do with this problem reoccurring [I have dropped it so many times >.<], but I figured if it was once fixed it could be fixed again?

 

[doogald]

I wonder if you are having bad sectors in flash memory again? (It's also possible that the phone is bad...)

Remembering that well-charged battery is important for this (i.e., try to get the battery charged up, if it is not already), perhaps it's time to go back and try to flash the MTD_Inspect_v0.9.zip file that you downloaded before. If it's still on the SD card, that's great; flash that file from recovery (remembering the hardware key scrolling method). You actually skipped that step the last time, as I think I was pretty sure that you had bad sectors anyway.

When you flash that zip file, it will create a file on the sdcard called "MTDInspect.txt". If you don't have an external SD card reader, you can connect the phone to your computer using the USB cable and select the option in recovery called "MS-USB toggle", it will mount the SD card as an external drive on your computer, where you can look for that file. Open that text file and see if there are any bad blocks in any of the partitions. The report will look something like this:

Eris MTD Partition Status Report Generated on Wed Mar 16 05:20:45 UTC 2011

PARTITION  DEVICE_NAME    SIZE(Bytes)  BAD_BLOCKS  #_E-BLKS  ECC_FAIL  ECC_CORR  BBT_BLOCKS

misc       /dev/mtd/mtd0     655360       0           5      0         0         0       
recovery   /dev/mtd/mtd1    5242880       0          40      0         0         0       
boot       /dev/mtd/mtd2    2621440       0          20      0         0         0       
system     /dev/mtd/mtd3  178257920       1        1360      0         0         0       
cache      /dev/mtd/mtd4  136314880       1        1040      0         0         0       
userdata   /dev/mtd/mtd5  167247872       0        1276      0         0         0

[From this post: http://forum.xda-developers.com/showpost.php?p=12131623&postcount=9]

 

[kloroformkandi]

Seems there are two bad blocks.

Eris MTD Partition Status Report Generated on Tue Dec 4 03:01:07 UTC 2012

PARTITION DEVICE_NAME SIZE(Bytes) BAD_BLOCKS #_E-BLKS ECC_FAIL ECC_CORR BBT_BLOCKS

misc /dev/mtd/mtd0 655360 0 5 0 0 0
recovery /dev/mtd/mtd1 5242880 0 40 0 0 0
boot /dev/mtd/mtd2 2621440 0 20 0 0 0
system /dev/mtd/mtd3 178257920 1 1360 0 0 0
cache /dev/mtd/mtd4 136314880 0 1040 0 0 0
userdata /dev/mtd/mtd5 167247872 1 1276 0 0 0



#################################### misc PARTITION ###################################

Partition Symbolic Name: misc
Partition (character-special) Device: /dev/mtd/mtd0
Partition Total Size: 655360
Partition EraseBlock Size: 131072
ECC failed: 0
ECC corrected: 0
Number of bad blocks: 0
Number of bbt blocks: 0
Block size 131072, page size 2048, OOB size 0
Dumping data starting at 0x00000000 and ending at 0x00001000...






#################################### recovery PARTITION ###################################

Partition Symbolic Name: recovery
Partition (character-special) Device: /dev/mtd/mtd1
Partition Total Size: 5242880
Partition EraseBlock Size: 131072
ECC failed: 0
ECC corrected: 0
Number of bad blocks: 0
Number of bbt blocks: 0
Block size 131072, page size 2048, OOB size 0
Dumping data starting at 0x00000000 and ending at 0x00001000...






#################################### boot PARTITION ###################################

Partition Symbolic Name: boot
Partition (character-special) Device: /dev/mtd/mtd2
Partition Total Size: 2621440
Partition EraseBlock Size: 131072
ECC failed: 0
ECC corrected: 0
Number of bad blocks: 0
Number of bbt blocks: 0
Block size 131072, page size 2048, OOB size 0
Dumping data starting at 0x00000000 and ending at 0x00001000...






#################################### system PARTITION ###################################

Partition Symbolic Name: system
Partition (character-special) Device: /dev/mtd/mtd3
Partition Total Size: 178257920
Partition EraseBlock Size: 131072
ECC failed: 0
ECC corrected: 0
Number of bad blocks: 1
Number of bbt blocks: 0
Block size 131072, page size 2048, OOB size 0
Dumping data starting at 0x00000000 and ending at 0x00001000...
ECC: 1 uncorrectable bitflip(s) at offset 0x00000000
ECC: 1 uncorrectable bitflip(s) at offset 0x00000800






#################################### cache PARTITION ###################################

Partition Symbolic Name: cache
Partition (character-special) Device: /dev/mtd/mtd4
Partition Total Size: 136314880
Partition EraseBlock Size: 131072
ECC failed: 0
ECC corrected: 0
Number of bad blocks: 0
Number of bbt blocks: 0
Block size 131072, page size 2048, OOB size 0
Dumping data starting at 0x00000000 and ending at 0x00001000...






#################################### userdata PARTITION ###################################

Partition Symbolic Name: userdata
Partition (character-special) Device: /dev/mtd/mtd5
Partition Total Size: 167247872
Partition EraseBlock Size: 131072
ECC failed: 0
ECC corrected: 0
Number of bad blocks: 1
Number of bbt blocks: 0
Block size 131072, page size 2048, OOB size 0
Dumping data starting at 0x00000000 and ending at 0x00001000...

 

[doogald]

It may be a bad block in a critical area.

I'd say the next thing to do is to try the ErisMTDNuke_v0.9.zip

So, from Recovery,

"Flash a zip from sdcard"

Choose ErisMTDNuke_v0.9.zip

Press trackball to confirm.

Report any error messages.

Actually, if you get no error messages, you may want to try to do a Nandroid restore right away, then see if the phone works after a restart.

Just the standard warning that the phone may still be unusable after this... though of course it is now anyway.

 

[kloroformkandi]

Yay It works! ^_^
Except when I went to restore there were two choices?
I wasn't sure if it mattered which one I chose.

 

[doogald]

Yay It works! ^_^
Except when I went to restore there were two choices?
I wasn't sure if it mattered which one I chose.

The backup files have a date code - they should look something like BCDS-yyyymmdd-hhmm IIRC, where the yyyy, mm, and dd mean what you think they do

Good thing on it working, too.

 

[kloroformkandi]

Thank you once again~

 

[CapnO]

This thread fixed my soft bricked Eris (1.49 S-ON, stock recovery, stuck on 3 skateboards).

Agree with post above; this thread is why I love Android...the community. Best step-by-step guide I've EVER seen ...no contest (I root my Samsung Vibrant as well).

 

[Bob Cat]

Welcome to the forums CapnO! We're glad you got it going.

BC

 

[vladrytskiy]

Hi, maybe someone can help me.
I faced the following trouble stuck on 3 droids on skates.
Device info:

Spoiler

*UNLOCKED*
PB00100 XC SHIP S-ON
HBOOT-1.51.0000 (PB0010000)
MICROP-0111
TOUCH PANEL-SYN0104
RADIO-2.42.01.04.27

Spoiler

C:\Users\Vlad\Desktop\mini>fastboot devices
HT.......... fastboot

C:\Users\Vlad\Desktop\mini>fastboot flash recovery recovery.img
sending 'recovery' (3834 KB)... OKAY [ 0.843s]
writing 'recovery'... FAILED (remote: not allow)
finished. total time: 0.844s

This is aproblem when i'm trying to push recovery.img

Spoiler

C:\Users\Vlad\Desktop\mini>fastboot flash zip recovery.zip
sending 'zip' (3818 KB)... OKAY [ 5.065s]
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
INFOstart image[recovery] unzipping & flushing...
INFO[RUU]UZ,recovery,0
INFO[RUU]UZ,recovery,20
INFO[RUU]UZ,recovery,40
INFO[RUU]UZ,recovery,60
INFO[RUU]UZ,recovery,80
INFO[RUU]UZ,recovery,100
INFO[RUU]WP,recovery,0
INFO[RUU]WP,recovery,20
FAILED (remote: 51 partition update fail)
finished. total time: 8.311s

As you see i also can't push recovery.zip
What's the trouble ?
P.S. The size of recovery files differ, cause i tried to flash different recoveries, from different threads

 

[doogald]

Hi, maybe someone can help me.
I faced the following trouble stuck on 3 droids on skates.


As you see i also can't push recovery.zip
What's the trouble ?
P.S. The size of recovery files differ, cause i tried to flash different recoveries, from different threads

vladrytskiy, try the instructions and recovery in this post (post 40 in this thread): http://androidforums.com/eris-all-things-root/556826-stuck-in-boot-up-screen.html#post4481107

Show the results when you try to fastboot flash zip recovery.zip

 

[vladrytskiy]

Today I tried at least 5 times, the first result is one of shown above .
Ok, I'll try one more ..
in 10 minutes ill post new result ...

 

[vladrytskiy]

hre it is.
C:\One_X_All-In-One_Kit_v1.2.2\Data>fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 0.062s]
finished. total time: 0.063s

C:\One_X_All-In-One_Kit_v1.2.2\Data>fastboot oem rebootRUU
... INFOmsm_nand_dm_read_oob 0x1FF60000 2048 0 fai
led (-74), correct
INFO 0 bits
INFOmsm_nand_dm_read_oob 0x1FF80000 2048 0 failed (-74), correct
INFO 0 bits
INFOmsm_nand_dm_read_oob 0x1FFA0000 2048 0 failed (-74), correct
INFO 0 bits
INFOmsm_nand_dm_read_oob 0x1FFA0800 2048 0 failed (-74), correct
INFO 0 bits
INFOmsm_nand_dm_read_oob 0x1FF60000 2048 0 failed (-74), correct
INFO 0 bits
INFOmsm_nand_dm_read_oob 0x1FF80000 2048 0 failed (-74), correct
INFO 0 bits
INFOmsm_nand_dm_read_oob 0x1FFA0000 2048 0 failed (-74), correct
INFO 0 bits
INFOmsm_nand_dm_read_oob 0x1FFA0800 2048 0 failed (-74), correct
INFO 0 bits
OKAY [ 0.065s]
finished. total time: 0.065s

C:\One_X_All-In-One_Kit_v1.2.2\Data>fastboot erase cache
erasing 'cache'... OKAY [ 3.807s]
finished. total time: 3.807s

C:\One_X_All-In-One_Kit_v1.2.2\Data>fastboot flash zip recovery.zip
sending 'zip' (2463 KB)... FAILED (status read failed (Too many links))
finished. total time: 282.770s
Here is a screen before flashing

Spoiler

it's after faild status

Spoiler

it's me disconected usb

Spoiler

it refuses to boot at all

Spoiler

the only way to boot is to flah the hboot again...but it's some kind of loop

 

[doogald]

It looks to me as if the flash memory on the phone has failed in a way that prevents the recovery partition from being flashed. Does the phone restart in HBOOT if you power up while holding down VolDn? If yes, is it still 1.51.0000 *UNLOCKED*?

The recovery.zip in the post that I linked above is 2523 KB, while the two results you showed were 3834 KB and 3818 KB, so the recovery.zip were two different files. That's why I wanted to see the result of fastboot flash zip recovery.zip.

 

[vladrytskiy]

no it doesn't boot in hboot, it starts with black screen with no signs, the only way to boot it now in hboot is to reflash it and then i can unlock it.
the last image shows the screen after connecting via usb.

It looks to me as if the flash memory on the phone has failed in a way that prevents the recovery partition from being flashed.

is it dead with no hope on recoveryng at all?

 

[scotty85]

i wouldnt write him off just yet. if we can get a recovery image to boot,even if we cant get it to permantly flash,there is hope. give us a few minutes

 

[scary alien]

Hey vladrytskiy,

Scotty sent me some things for you to try, but it would also help if you could let us know what the recoveries were that you flashed (i.e., description, file sizes and MD5 checksums if you can).

Anyway, there's also a special "rescue recovery" that we built that might help you in this situation (no guarantees, though ). It's smaller and doesn't have all of the bells and whistles (options/features) as the full-blown Amon_RA recovery.

Here's a link to it: PB00IMG-rescue-recovery.zip

It's file size is 2,583,818 bytes and it's MD5 sum is a2f3b8007df147bed7247efa2920a513.

Try to flash this tiny/rescue recovery:

fastboot flash zip PB00IMG-rescue-recovery.zip​

Then do a "fastboot reboot" to see if that will take you into that special recovery.

By the way, Scotty wanted to note:

hes getting stuck in ruu mode simply becasue his recovery zips are failing to flash,and the eris doesnt support the "fastboot oem reset RUUflag" or similar command to get you back to the regular bootloader.

Let us know what you find/see from the above.

Thanks!

 

[scotty85]

Thanks mister scary.

Hopefully that will get a recovery boooted. Holler if you have questions

 

[vladrytskiy]

It's rather hard to find all info about that recoveries that I tried to flash , cause there were lots of them .. after the multiple tries I deleted them :banghead:
I'll try flash rescue recovery in two hours , then I'll send feedback...

 

[vladrytskiy]

So i tried to send command fastboot oem reset RUUflag an got

C:\Users\Vlad\Desktop\mini>fastboot oem reset RUUflag
... FAILED (status read failed (Too many links))
finished. total time: 0.004s

then i disconnected usb relocked bootloader and flashed PB00IMG-eris-1.51.0000-hboot.zip

Spoiler

C:\Users\Vlad\Desktop\mini>fastboot devices
HT9B1HG0**** fastboot

C:\Users\Vlad\Desktop\mini>fastboot flash zip PB00IMG-eris-1.51.0000-hboot.zip
sending 'zip' (180 KB)... OKAY [ 0.167s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
INFOstart image[hboot] unzipping & flushing...
INFO[RUU]UZ,hboot,0
INFO[RUU]UZ,hboot,100
INFO[RUU]WP,hboot,0
INFO[RUU]WP,hboot,100
OKAY [ 1.470s]
finished. total time: 1.637s

C:\Users\Vlad\Desktop\mini>fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 0.062s]

then i unlocked bootloader

Spoiler

sending 'unlocktoken' (0 KB)...
OKAY [ 0.102s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.010s]
finished. total time: 0.115s

the md5 A2F3B8007DF147BED7247EFA2920A513 is correct for the file ofrecovery so i tried to flash it.
the first attempt was faild so i tied the second wit command fastboot oem rebootRUU and it send me OK.

Spoiler

C:\Users\Vlad\Desktop\mini>fastboot devices
HT9B1HG05423 fastboot

C:\Users\Vlad\Desktop\mini>fastboot flash zip PB00IMG-rescue-recovery.zip
sending 'zip' (2523 KB)... OKAY [ 3.374s]
writing 'zip'... FAILED (remote: not allow)
finished. total time: 3.377s

C:\Users\Vlad\Desktop\mini>fastboot oem rebootRUU
... INFOmsm_nand_dm_read_oob 0x1FF60000 2048 0 fai
led (-74), correct
INFO 0 bits
INFOmsm_nand_dm_read_oob 0x1FF80000 2048 0 failed (-74), correct
INFO 0 bits
INFOmsm_nand_dm_read_oob 0x1FFA0000 2048 0 failed (-74), correct
INFO 0 bits
INFOmsm_nand_dm_read_oob 0x1FFA0800 2048 0 failed (-74), correct
INFO 0 bits
INFOmsm_nand_dm_read_oob 0x1FF60000 2048 0 failed (-74), correct
INFO 0 bits
INFOmsm_nand_dm_read_oob 0x1FF80000 2048 0 failed (-74), correct
INFO 0 bits
INFOmsm_nand_dm_read_oob 0x1FFA0000 2048 0 failed (-74), correct
INFO 0 bits
INFOmsm_nand_dm_read_oob 0x1FFA0800 2048 0 failed (-74), correct
INFO 0 bits
OKAY [ 0.068s]
finished. total time: 0.068s

C:\Users\Vlad\Desktop\mini>fastboot flash zip PB00IMG-rescue-recovery.zip
sending 'zip' (2523 KB)... OKAY [ 0.582s]
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
INFOstart image[boot] unzipping & flushing...
INFO[RUU]UZ,boot,0
INFO[RUU]UZ,boot,42
INFO[RUU]UZ,boot,94
INFO[RUU]UZ,boot,100
INFO[RUU]WP,boot,0
INFO[RUU]WP,boot,40
INFO[RUU]WP,boot,80
INFO[RUU]WP,boot,100
OKAY [ 2.299s]
finished. total time: 2.882s

after sending fastboot reboot

Spoiler

it rebootet in recovery with folowing signs

what i'll have to do next?
should i do this:

Spoiler

..into the custom recovery and flash the ErisMiscReset_v0.9.zip file (watch for any errors - stop if you see errors!).

- in the same recovery session flash the MTD_Inspect_v0.9.zip file and determine if you have massive (bad block) corruption in any of /boot, /system, or /data. (See instructions here)

- If the above mentioned partitions only have one or two bad blocks, skip the next step.

- Flash (in recovery) ErisMTDNuke_v0.9.zip

- Re-lock the 1.51.0000 bootloader (phone in fastboot mode) with "fastboot oem lock

"

but i don't understand if i'll see some erors in the first flashing (flash the ErisMiscReset_v0.9.zip) what does it mean stop it means that next 2 flashing i have to miss and try to flash

- Flash the Eris Root ROM (from shipped-roms.com), using the HBOOT+PB00IMG.zip install method.

?

 

[scotty85]

Yes! That is exactly what you should do,only flash the misc reset last.

Flash:
-inspect
-nuke
-misc reset

Im fairly certain inspect will reveal a large number of bad blocks,so likey plan on flashing them all

After that,you will flash the "root rom" to get the real s off hboot,and put a bootable os back on the phone.

Don't want to get your hopes up too much,but I think you are well on your way to possible recovery!

 

[vladrytskiy]

Good news is that i cold restore the phone and flashed HTC Eris March 2011 OTA Stock ROM - v2.41.605.6 which boots and works.
Yhank you guys.
The bad news is i can't reach recovery and can't flash nither anoter recovery nither any ROM.

Any ideas?

 

[scotty85]

Awesome! That is great news. What troubles are you having flashing recovery? You should be able to install it just as you did before, with the fastboot flash recovery command. This time, you can use 1 of the normal images, and not the special rescue recovery. Another option if you could find it, would be to run the heiress 1 click root app

 

[doogald]

Good news is that i cold restore the phone and flashed HTC Eris March 2011 OTA Stock ROM - v2.41.605.6 which boots and works.
Yhank you guys.
The bad news is i can't reach recovery and can't flash nither anoter recovery nither any ROM.

Any ideas?

Ugh, it's been so long since I have done this...

If you restart the phone while holding VolDn, do you see the HBOOT start screen? Or do you see Amon_RA Recovery?

If HBOOT, my thinking is that the *best* thing to do is to run the root ROM PB00IMG.zip from HBOOT to get the 1.49.2000 S-OFF bootloader, so you can now more reliably fastboot flash from now on. After that, you would need to either flashing the latest radio (the root ROM has an older one) or flash a good Amon_RA recovery, then the Flashback_21v2 (to get the latest radio), fastboot flash Amon_RA recovery again, and then flash the ROM of you choice.

Scotty, what do you think?