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

Root Stuck in boot-up screen.

When i boot phone holding VolDwn i see HBOOT with 1.49.2000 S-OFF. Yea You're right it's amazing.
But my attempts to flash the recovery under cmd are failure:
C:\Users\Vlad\Desktop\mini>fastboot flash recovery recovery-RA-eris-v1.6.2-trackball-optional.img
sending 'recovery' (3834 KB)... OKAY [ 5.086s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 5.909s

C:\Users\Vlad\Desktop\mini>fastboot reboot
rebooting...
finished. total time: 0.041s

C:\Users\Vlad\Desktop\mini>fastboot flash recovery recovery.img
sending 'recovery' (3834 KB)... OKAY [ 0.842s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 1.665s

C:\Users\Vlad\Desktop\mini>fastboot reboot
rebooting...
finished. total time: 0.039s
Am i stupid and have to unlock it before flashing or i should flash it under fastboot oem rebootRUU
OH, i forgot, that i've tryied to flash it under fastboot oem rebootRUU
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 0x1FF60000 2048 0 failed (-74), correct
INFO 0 bits
INFOmsm_nand_dm_read_oob 0x1FF80000 2048 0 failed (-74), correct
INFO 0 bits
OKAY [ 0.043s]
finished. total time: 0.043s

C:\Users\Vlad\Desktop\mini>fastboot flash recovery recovery-RA-eris-v1.6.2-track
ball-optional.img
sending 'recovery' (3834 KB)... OKAY [ 5.077s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 5.897s

C:\Users\Vlad\Desktop\mini>
 
Upvote 0
When i boot phone holding VolDwn i see HBOOT with 1.49.2000 S-OFF. Yea You're right it's amazing.
But my attempts to flash the recovery under cmd are failure:
C:\Users\Vlad\Desktop\mini>fastboot flash recovery recovery-RA-eris-v1.6.2-trackball-optional.img
sending 'recovery' (3834 KB)... OKAY [ 5.086s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 5.909s

C:\Users\Vlad\Desktop\mini>fastboot reboot
rebooting...
finished. total time: 0.041s

C:\Users\Vlad\Desktop\mini>fastboot flash recovery recovery.img
sending 'recovery' (3834 KB)... OKAY [ 0.842s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 1.665s

C:\Users\Vlad\Desktop\mini>fastboot reboot
rebooting...
finished. total time: 0.039s
Am i stupid and have to unlock it before flashing?

1.49.2000 S-OFF is unlocked by default.

I still wonder about a nand flash issue in the recovery partition.

One idea is to 1-click root with the app in Scary Alien's scenario 5 here: http://androidforums.com/eris-all-t...2-custom-recovery-trackball-not-required.html

(Download/copy that app to SD. Enable third-party app installs in settings->applications on the phone. Run the app. Restart the phone. Then, shut down the phone. Try to start in Recovery by holding VolUp.)

Maybe that will get recovery on there?
 
Upvote 0
Not much to add... The s off bootloader should let you flash a recovery just fine.

You did flash the nuke zip,correct?

Make sure you're actually in fastboot ,and not hboot.

Other than that , you might run to inspect zip again and see if you still have bad blocks in recovery. But to my knowledge there's no reason you shouldn't be able to install it at this point
 
  • Like
Reactions: vladrytskiy
Upvote 0
I still wonder about a nand flash issue in the recovery partition.

Oh, i'm very sorry .
Is this info would be helpfull?
#################################### 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: 31
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

This info i took from MTD_Inspect.txt before flashing verizons rom.
 
Upvote 0
This info i took from MTD_Inspect.txt before flashing verizons rom.

Bad blocks in Recovery partition.

Did you flash ErisMTDNuke_v0.9.zip after running the inspect? Any error messages if yes?

Scotty/Scary - does the mini rescue recovery allow for the ErisMTDNuke_v0.9.zip script to actually do anything? I know that there is a lot of stuff stripped from the rescue recovery....

[edit] BTW, I'm going to be on the road until about 2 pm today, so may not be able to answer back here until after then...
 
Upvote 0
The rscue recovery should flash the nuke zip just fine. I'm also wondering if that output was taken before it was flashed or if it was not flashed.

I just read the ErisMTDNuke_v0.9.zip script - it should flash Amon_RA as the last step. I never knew that... It also doesn't seem to flash erase the Recovery partition. Hmm....

Code:
assert compatible_with("0.2") == "true"
# this is only for the Eris ( == desirec )
assert getprop("ro.product.device") == "desirec" || getprop("ro.build.product") == "desirec"

# NOTE THIS SCRIPT PERFORMS OPERATIONS USING THE "MTDUTILS" flash_erase UTILITY
# WHICH SHOULD NEVER BE USED UNDER NORMAL OPERATING CIRCUMSTANCES.
#
# IT IS USED HERE ONLY FOR A DIRE SITUATION WITH THE HTC DROID ERIS WHERE THE
# ALTERNATIVE WOULD BE TO THROW THE PHONE AWAY - IT IS A "LAST DITCH EFFORT"
# RESCUE METHOD
#
# YOU HAVE BEEN WARNED.  IF YOU HAVE ANY DOUBTS, DO NOT USE THIS.
#
show_progress 0.1 0

# Here we flash jcase's "Flash Any RUU" patch to the misc partition
# (note included flash_image binary is from Amon_RA's recovery for the Eris, v1.6.2)
# We do this first in case subsequent steps fail - perhaps the ROOT PB00IMG could be used after
#
copy_dir PACKAGE:misc_img CACHE:
run_program PACKAGE:flash_image misc /cache/misc.img
delete CACHE:misc.img

show_progress 0.6 10

# Perform the MTDUTILS flash_erase, unmarking any bad blocks.
#
# Eris mtd2 = boot
run_program PACKAGE:flash_erase -N /dev/mtd/mtd2 0 0
# Eris mtd3 = system
run_program PACKAGE:flash_erase -N /dev/mtd/mtd3 0 0
# Eris mtd4 = cache, BUT IT IS CURRENTLY MOUNTED - see below
# Eris mtd5 = userdata
run_program PACKAGE:flash_erase -N /dev/mtd/mtd5 0 0

show_progress 0.1 10

# Replace the Amon_RA recovery with the stock (HTC) Eris July OTA (2.37.605.4) recovery
# Note:  included flash_image binary is from Amon_RA's recovery for the Eris, v1.6.2
# 
# Note2: You would think that this could be done with a simple "write_raw_image PACKAGE:recovery.img RECOVERY:",
#   but it seems that Amon_RA barfs on that, complaining it can not "mount" RECOVERY: 
#
copy_dir PACKAGE:recovery_img CACHE:
run_program PACKAGE:flash_image recovery /cache/recovery-RA-eris-v1.6.2.img
delete CACHE:recovery-RA-eris-v1.6.2.img

show_progress 0.1 10

# Here we attempt to clear the cache the "regular" way
delete_recursive CACHE:
format CACHE:
 
Upvote 0
Bad blocks in Recovery partition.

Did you flash ErisMTDNuke_v0.9.zip after running the inspect? Any error messages if yes?
YES i made this. But both of them ended with fail.
Don't remember after wich flashing i made tis pic:
33Tzgxzs_ck.jpg
may be the whole MTD_Inspect info will be helpfull...
Eris MTD Partition Status Report Generated on Wed Mar 6 12:27:59 UTC 2013

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

misc /dev/mtd/mtd0 655360 2 5 12 0 0
recovery /dev/mtd/mtd1 5242880 31 40 0 0 0
boot /dev/mtd/mtd2 2621440 0 20 0 0 0
system /dev/mtd/mtd3 178257920 0 1360 0 0 0
cache /dev/mtd/mtd4 136314880 393 1040 328 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: 12
ECC corrected: 0
Number of bad blocks: 2
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






#################################### 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: 31
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






#################################### 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: 0
Number of bbt blocks: 0
Block size 131072, page size 2048, OOB size 0
Dumping data starting at 0x00000000 and ending at 0x00001000...






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

Partition Symbolic Name: cache
Partition (character-special) Device: /dev/mtd/mtd4
Partition Total Size: 136314880
Partition EraseBlock Size: 131072
ECC failed: 328
ECC corrected: 0
Number of bad blocks: 393
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






#################################### 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...
 
  • Like
Reactions: scotty85
Upvote 0
When you flashed the root ROM did any partition updates fail?

unfortunately i do not remember, cause i left the phone and went away. but it seems that there were no partrition updates fail.
EDITED.
While i was waiting for your reply i became interested in any fails ehile flashing root ROM..
so i reflashed it one more time and yes there is one fail:
wxsVjyDRdy4.jpg
then i reflashed rescue recovery.
the next step was inspect here is the whole info:
Eris MTD Partition Status Report Generated on Wed Mar 6 16:28:51 UTC 2013

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

misc /dev/mtd/mtd0 655360 2 5 8 0 0
recovery /dev/mtd/mtd1 5242880 31 40 0 0 0
boot /dev/mtd/mtd2 2621440 0 20 0 0 0
system /dev/mtd/mtd3 178257920 0 1360 0 0 0
cache /dev/mtd/mtd4 136314880 393 1040 393 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: 8
ECC corrected: 0
Number of bad blocks: 2
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






#################################### 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: 31
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






#################################### 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: 0
Number of bbt blocks: 0
Block size 131072, page size 2048, OOB size 0
Dumping data starting at 0x00000000 and ending at 0x00001000...






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

Partition Symbolic Name: cache
Partition (character-special) Device: /dev/mtd/mtd4
Partition Total Size: 136314880
Partition EraseBlock Size: 131072
ECC failed: 393
ECC corrected: 0
Number of bad blocks: 393
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






#################################### 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...
then tere was nuke
a7I26Va9HJQ.jpg

and misc reset:
-9CjiEso6K8.jpg
now i can reach recovery only in cmd by sending fastboot reboot.
and i'm planning to try to flash GSB.v4.5-final_ODEXED_CM7.2-Eris from recovery.....
 
  • Like
Reactions: scotty85
Upvote 0
Ok, a significant number of bad blocks in the recovery and misc partitions (as well as cache, though that seems less critical.)

Scotty, Scary: what do you think? Is there any reason why we shouldn't update erisuser1's script to flash_erase the mtd0 (recovery) and mtd1 (misc) partitions as well? Or, should vladrytskiy try to flash GSB and run the phone until the rest of the flash memory fails?
 
Upvote 0
Guys , I'm very pleased you're trying to help me, but may be there is no reason you to spend your time because this is not my phone it's the phone of one friend of mine. she just asked me to install cm 7 cause she wants to sell it.
It works rather good with cm7 , but there is no opportunity to enter recovery now and I forgot to install gaps the last time I was in recovery . the only way to start recovery is to reflash hboot, then rescue recovery, under it I can flash cm7 one more time, but you know I'm a little bit scared , that the next time will be the last one with no way back ...

There is one more reason you not to try cause I'm planning to give it back to my friend we decided to meet at 11 am and there is a leek of time.

I'm glad that I met such good people like you who are willing to help with my trouble . :thumbup:
And the last one, I'm really sorry for my bad English :(
 
Upvote 0
Guys , I'm very pleased you're trying to help me, but may be there is no reason you to spend your time because this is not my phone it's the phone of one friend of mine. she just asked me to install cm 7 cause she wants to sell it.
It works rather good with cm7 , but there is no opportunity to enter recovery now and I forgot to install gaps the last time I was in recovery . the only way to start recovery is to reflash hboot, then rescue recovery, under it I can flash cm7 one more time, but you know I'm a little bit scared , that the next time will be the last one with no way back ...

There is one more reason you not to try cause I'm planning to give it back to my friend we decided to meet at 11 am and there is a leek of time.

I'm glad that I met such good people like you who are willing to help with my trouble . :thumbup:
And the last one, I'm really sorry for my bad English :(

As I recall, the latest version of GSB includes gapps these days. Flashing gapps actually messes up the Maps app. If the market is in the app drawer, and talk, then you are all set...
 
Upvote 0
Sorry guys been busy at work today,so I havent looked too closely.

Just a couple things right now...
1) I can't see any reason not t mod eu1s script off the top of my head

2) while our main desire is to help get your phone working,we also do this because we enjoy it. It may not be as important to you,but I consider it to be research :D anything we learn helping you may help us save others in the future :)

Last and not least,I think your English is not bad at all
 
Upvote 0
Yes, you are right maps and market are installed I was so happy that it booted that didn't notice them :eek:
I just called to my friend she said that decided not to sell it but wants to keep it as a second phone . She said it would be better if it'll die in her hands than in someone's and it would be awful to sell half-died gadget.:rolleyes:

Ok if it can help someone else in the future I agree to experiment once again . Just send the files and instructions :)
 
Upvote 0
Yes, you are right maps and market are installed I was so happy that it booted that didn't notice them :eek:
I just called to my friend she said that decided not to sell it but wants to keep it as a second phone . She said it would be better if it'll die in her hands than in someone's and it would be awful to sell half-died gadget.:rolleyes:

Ok if it can help someone else in the future I agree to experiment once again . Just send the files and instructions :)

Ok, I will work on it a bit later. I'm going to try on my old Eris first, just to see what happens. It shouldn't take long to tell, one way or the other.
 
Upvote 0
Ok, I will work on it a bit later. I'm going to try on my old Eris first, just to see what happens. It shouldn't take long to tell, one way or the other.

Ok, attached is ErisMTDNukeRecovery.zip. This dis not do anything bad to my Eris, though I had no bad blocks to start.

vladrytskiy, it's possible that you'll see error messages. It's possible that this will brick the phone. If it works, the phone should have Amon_RA recovery on it, accessible by restarting by holding VolUp. Or - better! - you can run MTD_Inspect_v0.9.zip right after and show us what the bad block count is. (You should find the MTD_Inspect.txt file on the sdcard when MTD_Inspect is done.)

It's up to you if you want to try it...

Sorry, but you will need to reflash GSB after this is done.

Let me know if there are any errors that stop the script from running.

And, please, people reading this message in the future - ask about running this before you do!!!
 

Attachments

  • ErisMTDNukeRecovery.zip
    4.1 MB · Views: 89
Upvote 0
Hi.
That's me with my report.
Oh by the way the flashing ended with fail... MTD inspection after the flashing folows:
Eris MTD Partition Status Report Generated on Thu Mar 7 05:56:42 UTC 2013

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

misc /dev/mtd/mtd0 655360 2 5 14 0 0
recovery /dev/mtd/mtd1 5242880 31 40 0 0 0
boot /dev/mtd/mtd2 2621440 0 20 0 0 0
system /dev/mtd/mtd3 178257920 0 1360 0 0 0
cache /dev/mtd/mtd4 136314880 393 1040 392 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: 14
ECC corrected: 0
Number of bad blocks: 2
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






#################################### 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: 31
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






#################################### 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: 0
Number of bbt blocks: 0
Block size 131072, page size 2048, OOB size 0
Dumping data starting at 0x00000000 and ending at 0x00001000...






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

Partition Symbolic Name: cache
Partition (character-special) Device: /dev/mtd/mtd4
Partition Total Size: 136314880
Partition EraseBlock Size: 131072
ECC failed: 392
ECC corrected: 0
Number of bad blocks: 393
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






#################################### 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...
It's a pity i've forgotten to make a pic of the fail but it seemd to be another line (22)..


Guys , I have one idea, but don't know how to realise it...
Once I was reading one Russian forum about Samsung galaxy s 2 there were a couple of people who had troubles with their system partition it refused to work at all also there were one solution to make the phone work they had to make a partition on ext sd card , some programming in cmd and finally they could get rather working phone ...
So maybe there is similar solution to my problem ?
But I can't find neither this thread neither that forum.
 
  • Like
Reactions: scary alien
Upvote 0
Hmmm so the new nuke zip was not able to wipe recovery? Can you flash it again and give us the exact failure error? It wasn't something simple like a signiture failure was it?

yes, i'll do it a little bit later, maybe in hour.
no it wasn't signature fail.
it was smth like that but with anoter line i gues it was 22
-9CjiEso6K8.jpg
 
Upvote 0
Hi.
That's me with my report.
Oh by the way the flashing ended with fail... MTD inspection after the flashing folows:It's a pity i've forgotten to make a pic of the fail but it seemd to be another line (22)..

Line 22? That is suspiciously before any of the partitions actually get flash erased. What happens at line 22 of the script is that the app tries to flash the misc partition with something in case the phone craps out in the flash erase stage. I think that nothing actually happened - especially if you still have GSB on the phone.

Let me try uploading another version of this app that doesn't try to flash the MISC partition before the flash erases.


Guys , I have one idea, but don't know how to realise it...
Once I was reading one Russian forum about Samsung galaxy s 2 there were a couple of people who had troubles with their system partition it refused to work at all also there were one solution to make the phone work they had to make a partition on ext sd card , some programming in cmd and finally they could get rather working phone ...
So maybe there is similar solution to my problem ?
But I can't find neither this thread neither that forum.

Actually, my current phone - the Motorola Droid 3 - has a custom recovery/bootstrap that allows just this - it creates /system, /cache, /data partitions on the SD card and runs the phone from there.

Unfortunately, it's way beyond my ability to know how to do this for the Eris. YOu do not have problems with the system or data partitions anyway - your major problem is that there are bad nand blocks in the recovery partition, so you cannot get a custom recovery on the phone.

I'll have a new nuke utility up in a few minutes. Don't run it, though, if you ended up losing GSB after the last one.
 
Upvote 0
Here is the new nuke utility, ErisMTDNukeRecovery_v2.zip. Make sure to run that one. Report back if you see an error message. For example, you may see error in line 72 this time.

Also run another Inspect and we'll see whether it does anything for the recovery and misc partitions.

Also, as usual, this may brick the phone. Just so you know...
 

Attachments

  • ErisMTDNukeRecovery_v2.zip
    4.1 MB · Views: 110
Upvote 0
HO-HO-HO!!
this is a pic from the rescue recovery
HtDp2q85o4g.jpg
this is a pic of a new recovery
PO-NAuNonoU.jpg
inspection:
Eris MTD Partition Status Report Generated on Thu Mar 7 17:37:31 UTC 2013

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 0 1360 0 0 0
cache /dev/mtd/mtd4 136314880 393 1040 328 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: 0
Number of bbt blocks: 0
Block size 131072, page size 2048, OOB size 0
Dumping data starting at 0x00000000 and ending at 0x00001000...






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

Partition Symbolic Name: cache
Partition (character-special) Device: /dev/mtd/mtd4
Partition Total Size: 136314880
Partition EraseBlock Size: 131072
ECC failed: 328
ECC corrected: 0
Number of bad blocks: 393
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






#################################### 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...
the next objective is to flash another radio . i have 2.40.00.01.22 now.
but i have no ideas how to make this. there were i gues 2.42...... is it possible?
 
Upvote 0
the next objective is to flash another radio . i have 2.40.00.01.22 now.
but i have no ideas how to make this. there were i gues 2.42...... is it possible?


First, great news! Still some bad blocks in cache and data, but I think that's not so critical - cache should have enough space for usability, and the same with the data partition.

I'm going to attach a recovery-flashable zip of the latest radio. Generally what we tell people to do is flash Flashback21_v2, which unroots the phone but updates the radio, then re-root, etc. But let's skip a step...

Flash this attached file to get the latest radio. After it reboots, it should restart recovery and you will see a messages that says something like "Formatting CACHE..." but you never see a completed message. It probably takes just a few seconds to format cache; after, say, 10 seconds you should be able to do anything else - flash a ROM, restart the phone, etc.

MD5: f15cf77b1c08cfb1f357e2574f386f5f if you want to check. But, the way that signed zips work, if it flashes, it should be ok.

You may also want to fastboot flash Scary Alien's better recovery. I suppose that I should have included that in the nuke flash zip above - I wasn't even paying attention. I believe that I will update both Erisuser1's original MTD Nuke and my new one to reflash that better recovery. Instructions are here in Scary's post, scenario 4 - I believe that you have 1.49.2000 S-OFF, so fastboot flash recovery recovery-RA-eris-v1.6.2-trackball-optional.img should now work fine!
 

Attachments

  • 2.42.02.10.29.zip
    6.9 MB · Views: 71
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