Okay, so, I'm gonna grab my Eris and install the v3 leak and then try the RUU and even try re-installing the v3 leak again to see how things behave...back soon(-ish) 
.
.-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root help save a brick
- Thread starter 13kyl
- Start date
-
- Tags
- htc droid eris
WormDoes
Android Expert
Yo, WormDoes! Long time, mate! Good to see you again. Saw a few recent posts from you in the Guides forum (congrats, btw
Hey buddy! Nice seeing you as well. And thanks for the congrats. It was a wild, wild ride that's for sure.
well this does tell us why the PB00IMG failed... 2.37.605.4 is indeed newer than the v3 leak and the root rom
let me guess... its giving you an error message thats something to the affect of using the wrong file? i forget what it was exactly...
edit: on the leaving,its cool... sometimes these things happen
It looks like the version on the phone is newer than the V3 leak, right?
Okay, I installed the 2.1 v3 leak.
Then, I re-installed it (no problems).
Then, I ran the RUU (no problems).
Here's the details:
So, I've got a 2.1 v3 leak installed on my phone (3 times in 30 minutes, LOL) and an S-ON bootloadereek: -- no biggie, though 
).
I don't remember seeing what, if anything, 13kyl reported that the RUU said about what version (i.e., "From: Image version...") he was running...
Then, I re-installed it (no problems).
Then, I ran the RUU (no problems).
Here's the details:
Code:
[COLOR=blue]First, moved the 2.1 v3 leak PB00IMG.zip to /sdcard[/COLOR]
[COLOR=blue]Rebooted in HBOOT mode and allowed PB00IMG.zip to be installed:[/COLOR]
1:33 finished applying v3 update
1:36 saw VZW lock banner
1:37 prompted with setup menus (wi-fi, Gmail, etc.)
1:39 pretty much finished booting
[COLOR=blue]Okay, now, re-doing 2.1 v3 leak install via HBOOT:[/COLOR]
1:39 HBOOT mode w/PB00IMG.zip still installed
1:39 still checking...
1:40 passed verification...second check in-progress
1:40 asking for to install "Do you want to start update?"
1:41 trackball pressed
1:41 starting v3 leak PB00IMG.zip install all over again...
1:42 went from "checking..." to "Update is in progress" with red status bar on top-right
1:43 black status bar while SYSTEM is being updated...then red status bar...
1:44 "Update complete", "Do you want to reboot device?"
1:45 trackball pressed
1:45 skating Androids...
1:45 htc quietly brilliant"
1:46 VERIZON wireless splash screen
1:48 lock screen sash, pulled-down, now "htc" splash screen (white letters on black screen)
1:48 setup menus again...
1:49 finished rebooting...
1:50 powered-off phone
[COLOR=blue]Next, the RUU:[/COLOR]
1:50 started RUU_Desire_C_Verizon_WWE_2.36.605.1_release_signed_with_driver.exe
1:52 HTC Android Phone ROM Update Utility 1.0.2.11 splash screen ("Welcome...", "Caution:...")
1:52 search hard-drives for ROM.zip file...(found "rom.zip" in C:\Users\scaryalien\AppData\Local\Temp\{793AE93F-1F6A-4771-89FC-8A61DA14E373}\{8069F5A6-8C8C-4645-8C74-CC7ACC0522E1}
2:05 put phone in FASTBOOT USB mode
2:05 Image version: 2.36.605.1
2:06 selected "Update"
2:06 From: Image version 2.36.605.1 To: Image version: 2.36.605.1
2:07 hit Next
2:07 hit Next
2:07 flashed bootloader...Sending...Updating Signature...(white "htc" splash screen on black background)...
2:08 "Waiting for Bootloader..."...Sending..."Updating the ROM image on your Android phone"...Updating Signature...
2:09 Updating Radio...52%...Updating Recovery...66%.....Updating System...69%....(htc splash screen also has green progress bar too)
2:10 Upating User Data...83%...100%...Done! "Congratulations! You ROM update has been completed. Your Android phone is now ready for use."
2:11 phone is rebooting (cycling through the normal skating Android, htc quietly brilliant, and VERIZON wireless splash screens)
2:13 still finishing-up rebooting...
2:14 setup menus...blah, blah, blah...So, I've got a 2.1 v3 leak installed on my phone (3 times in 30 minutes, LOL) and an S-ON bootloader
eek: -- no biggie, though ).I don't remember seeing what, if anything, 13kyl reported that the RUU said about what version (i.e., "From: Image version...") he was running...
That would make sense (no pun intended) if your dad had taken all of the OTA updates...
But I thought that it was the HBOOT / misc.img version that was important here and not the O/S version.
Scotty?
The image on my phone is more new than the Rom update Utility Image.
Since my phone is now a 2.1 v3 leak, it just got an OTA update, which I'm currently installing...
I'll try to re-do the v3 leak PB00IMG.zip install after the update is finished...
Howdy folks.
Whew! Just reading this thread wore me out!
13kyl, you are in good hands - scotty and scary are leading you down the exact path that I would also recommend.
Don't give up - success is just around the corner. The "rom.zip" file (to be deleted and replaced with the "Root" PB00IMG.zip file renamed to "rom.zip" at the same location) will certainly be on your hard drive, so long as you still have the RUU utility running, and waiting for you at the screen which indicates that flashing will begin as soon as you click.
[ scotty/scary: to my knowledge, there are no button-press sequences which will put the phone into RUU mode, but as you discovered, the RUU utility can "get it there" if the phone is in FASTBOOT USB mode to start with. Note that the RUU utility actually "speaks fastboot dialect" with the phone, so there may be a way to do it using a fastboot oem command as well. With the regular OS booted "adb shell reboot oem-78" will also do it so long as the ROM cook didn't replace the HTC "reboot" binary with a busybox symlink ]
eu1
Whew! Just reading this thread wore me out!
13kyl, you are in good hands - scotty and scary are leading you down the exact path that I would also recommend.
Don't give up - success is just around the corner. The "rom.zip" file (to be deleted and replaced with the "Root" PB00IMG.zip file renamed to "rom.zip" at the same location) will certainly be on your hard drive, so long as you still have the RUU utility running, and waiting for you at the screen which indicates that flashing will begin as soon as you click.
[ scotty/scary: to my knowledge, there are no button-press sequences which will put the phone into RUU mode, but as you discovered, the RUU utility can "get it there" if the phone is in FASTBOOT USB mode to start with. Note that the RUU utility actually "speaks fastboot dialect" with the phone, so there may be a way to do it using a fastboot oem command as well. With the regular OS booted "adb shell reboot oem-78" will also do it so long as the ROM cook didn't replace the HTC "reboot" binary with a busybox symlink ]
eu1
Thanks for the confirmation, eu1 (whew! I feel much better knowing that Scotty and I aren't total numbskulls
).The update is done and I'm sitting at:
Firmware: 2.1
Baseband version: 2.42.01.04.27
Kernel version: 2.6.29-8a03cb9a htc-kernel@and18-2 #1
Build number: 2.37.605.4 CL185970 release keys
Software number: 2.37.605.4
Which I think matches what 13kyl has.
I'm actually going to try the rom.zip replacement thing from the RUU this time.
Back in a few...
<img src="http://i45.photobucket.com/albums/f99/13kyl/Eris/screenshot1.jpg">
Or go here: Eris pictures by 13kyl - Photobucket
I hope this works.
I cannot find rom.zip I even hilighted every file on my C: drive and unchecked hide
I went into Control Panel --> folder options --> view
and selected the radio button "Show hidden files, folders, or drives
Or go here: Eris pictures by 13kyl - Photobucket
I hope this works.
I cannot find rom.zip I even hilighted every file on my C: drive and unchecked hide
I went into Control Panel --> folder options --> view
and selected the radio button "Show hidden files, folders, or drives
Getting the same "ERROR [140]: BOOTLOADER VERSION ERROR" that 13kyl is seeing when trying to replace the rom.zip with the base root ROM.
So, the SoSicWitIt rooting method won't work in this case...
Phone's still rebooting, but I'm sure I still have the S-ON bootloader...
edit: yep.
Getting the same "ERROR [140]: BOOTLOADER VERSION ERROR" that 13kyl is seeing when trying to replace the rom.zip with the base root ROM.
So, the SoSicWitIt rooting method won't work in this case...
Phone's still rebooting, but I'm sure I still have the S-ON bootloader...
edit: yep.
Okay, I still had the 2.1 v3 leak's PB00IMG.zip file on my SD card. Its installing just fine right now...and should for you since I think my phone was set to the same versions are yours.
So, 13kyl, I think you should grab the 2.1 v3 leak PB00IMG.zip file and try to install it via HBOOT...
(I thought you had tried this, but let's double-check the MD5 and such first, okay?)
You got the best of the best helping you my man. Stick with it and they'll have up and running again.
That's the one I used...MD5 sum matches.
Make sure you've really nuked / renamed / moved any other PB00IMG.zip file from your /sdcard's top path and then move the above one over as PB00IMG.zip. Check its size too (109,946,224 bytes) after you move it over to the /sdcard and make sure you do a safe-eject from Windows before un-mounted and disconnecting.
Then, reboot under HBOOT and watch things carefully (hopefully, they'll follow the stuff I posted above).
Crossing fingers again...
Sorry, I didn't answer your question quite exactly.
The v1/v2/v3 leaks are all Android 2.1 for the Eris (so is the base root ROM). Its just that there were snapshots of 2.1 taken at different times and contain varying degrees of bugs, etc. (the base root ROM is especially buggy).
I was having you use the v3 leak since that seemed to match your current configuration and it worked okay for me.
Okay, back to our originally, scheduled broadcast...
Ugh!
I'm pretty-much tapped-out, idea-wise...and I have to step out for a couple of hours with my nephew...I'll be here for about 15 minutes more, though...
Scotty, eu1...?
Getting the same "ERROR [140]: BOOTLOADER VERSION ERROR" that 13kyl is seeing when trying to replace the rom.zip with the base root ROM.
So, the SoSicWitIt rooting method won't work in this case...
Phone's still rebooting, but I'm sure I still have the S-ON bootloader...
edit: yep.
Are you saying that this version check error occurs *before* the screen which aaks you whether or not you want to proceed with flashing?
13kyl - after you see the "can't open /cache/recovery/command" message when booting the (stock) recovery, do you see the rest of the recovery menu appear?
eu1
OK, Here's what I am thinking (scary will probably reply to my Q before I finish typing this).
If the "SoSicWitIt" (RUU/replace the rom.zip with the ROOT PB00IMG.zip) trick does not work, there really is only one more long shot available - the "tereg double race condition exploit".
Yeah, I know - scary and scotty are rolling their eyes right now
That's because it is tedious, and only about one in five people who attempted it could get it to work - I tried for days and never succeeded. (That's the nature of race conditions - they are statistically improbable).
Before anybody goes down that route, though, I guess we should be absolutely convinced that
- the HBOOT (ROOT) PB00IMG.zip install fails without installing even the S-OFF bootloader
- the SoSicWitIt ("rom.zip" file replacement) can't be coerced into working
- fastboot can not be used to get the phone into RUU mode ("oem-78") before the RUU utility is started.
scary, I can't find my notes - if you run the fastboot command "fastboot oem ?" with the phone in fastboot mode, what output does the 1.49.0000 bootloader produce?
eu1
Well, it looked like it was all going to work like the v3 RUU did...I think this message came-up after it asked me if I wanted to proceed (but I'm not 100% sure)...
I just tried it again...
1. Main splash screen (i.e., "Welcome to the ROM Update Utility...")
2. Second screen ("Follow the instructions below to prepare the phone for the update:")
3. Current information about your Android phone: Image version 2.36.605.1, select "Update" (clicked "Update" button) to update the current ROM version
4. Fourth screen: "Verify that you want to update the ROM version:" (from Image version 2.36.605.1 to 2.19.605.1)...hit the "Next" button
5. Fifth screen: "You are now ready to update your ROM image..."...hit Next button...
6. Rebooting to Bootloader...Sending....
7. Finally comes back with the "ERROR [140]: BOOTLOADER VERSION ERROR"
Gotta run...be back in 2-ish hours... Good luck!
scotty85
Extreme Android User
Nice! WormDoes was around here a lot "back in the day", LOL, when the Eris was king
Anyway, I wonder if we are just missing the point here...
1. The phone is un-rooted
2. It appears to have the v3 leak already on it
3. Why wouldn't the v3 leak's PB00IMG.zip be able to be re-applied? The version shouldn't be older at that point, right? This would also imply that the v3 RUU should also work...
I'm wondering if we just missed something and have assumed that something that should work, didn't work, but wasn't quite done right?
Dunno...
this is the prollem i think... looking at the below,it doesnt have the v3 leak,wich would be firmware 2.36.605.1....
the 2.37.605.4 firmware is the july 4th 2010 OTA. this does tell us why the PB00IMG failed... 2.37.605.4 is indeed newer than the v3 leak and the root rom. the stupid bootloader realizes what we are trying to run an ruu with older firmware than what it is supposed to have
but i think you hit the nail on the head:
i dont think there exist full rom RUUs or hboot files for the 4th 2010 OTA,or march 2011 OTAs,since they were just partial updates. if they did exist,flashing them would be next option.
but i wonder if a store could push that software? if he took it to a store,i wonder if they could flash a full rom including the july 2010 or march 2011 updates?
i think that may be a last resort... call the major stores in your area and find one capable of updating firmware... explain it wont boot past the skateboard guys(i wouldnt explain exactly why
),explain the most current RUU failed,and see if they are willing to try and flash firmware to it.grrr this fustrates the crap out of me
if it had s-off,or we could figure a way to make it s-off,i think we could fix it.edit:
holy crap alot of new post while i was typin