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

Root help save a brick

Stepping in to see if I can be of some help. I don't have my Eris anymore, but the more than merrier as Scotty put it ;) Hopefully eu1 will see this tomorrow and figure this all out as he's done numerous times in the past.

So, just to catch me up, you tried to root, but pulled your battery while in hboot? Tried RUU and no dice, correct?
 
Stepping in to see if I can be of some help. I don't have my Eris anymore, but the more than merrier as Scotty put it ;) Hopefully eu1 will see this tomorrow and figure this all out as he's done numerous times in the past.

So, just to catch me up, you tried to root, but pulled your battery while in hboot? Tried RUU and no dice, correct?

hasnt gotten the ruu installer to work yet. we have failed hboot flashes of the the root rom and v3 leak(main version higher error).

our next step is to get his pc/installer to see the phone. even if the install itself fails,we can use the installer to sneek the s-off bootloader onto the phone. at that point we can fastboot or hboot a recovery,then hopefully flash a rom. or actually once hes s-off he may be able to flash the root rom in hboot without the main version higher error

thanks for joinin the party :D
 
hasnt gotten the ruu installer to work yet. we have failed hboot flashes of the the root rom and v3 leak(main version higher error).

our next step is to get his pc/installer to see the phone. even if the install itself fails,we can use the installer to sneek the s-off bootloader onto the phone. at that point we can fastboot or hboot a recovery,then hopefully flash a rom. or actually once hes s-off he may be able to flash the root rom in hboot without the main version higher error

thanks for joinin the party :D

Ok, did the OP bow out for the evening or is he still around?

It's my pleasure. When I saw your PM I couldn't not come in here and see if I could help.
 
Sorry I had to step away for a bit pretty unexpectedly, pesky emergencies.

Thank you so much scotty and scary. You've really gotten me far!
The RUU appears to be working now.

I really would be lost without the help I've received here.

WormDoes, Howdy.

I'm hoping this work if you're still around, everything appears to be going smoothly.

... It didn't work. I'm going to run it again so I can catch the error before it closes.
 
I am really bummed I left right when we got more backup, I'm sorry about that guys I had no idea I would have to be gone that long.

Rom Update Utility is telling my I'm updating
from:
Image version:
2.37.605.4

to:
Image version:
2.36.605.1
 
I am really bummed I left right when we got more backup, I'm sorry about that guys I had no idea I would have to be gone that long.

Rom Update Utility is telling my I'm updating
from:
Image version:
2.37.605.4

to:
Image version:
2.36.605.1

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 :)
 
This is what RUU tells me:

ERROR [140]: BOOTLOADER VERSION ERROR

The ROM Update Utility cannot update your Android phone.
Pleas get the correct ROM Update Utility and try again.

I'm going to hunt around more and try to do that.
 
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...

exactly
 
Scotty85, I didn't know you were still on here.

Is there a RUU that is newer?

I saw on the vido link earlier that the version was rolled back with an RUU
 
the next thing we can try is to get the s-off bootloader onto the phone. in a nutshell,the installer creates a temporary spot for the rom its going to flash. you need to find this spot,delete "rom.zip" and replace it on your pc with the root rom,wich you will rename "rom.zip".

this is copied from another thread on how to do it:


first,are you 100% sure youre using the rootrom? i dont see anything about hboot in your info,so it makes me wonder exactly what RUU youre using. the download youre using should have an md5 sum of: 63eacc5ede3b179f95dc22d8ef585f94 do you have a way to check it on your PC?

i actually got this to work(tho in my case it successfully flashed the entire root rom since im not bricked). im on windows 7,so if youre on something else it may be a lil different.
1)verify youre using the correct root rom.
2)run installer
3) you will get to a screen that says the following:
you are now ready to update your rom. the update will take approximately 10 minutes to finish
during the process the following things will occur:
-the android phone will be prepaired for the update process
-the process will be displayed on your pc and android phone
-the update completed screen will be displayed on your pc

4)this is where you need to stop. dont click next till youve found and replaced the file.
5)you need to make sure your hidden files are visible.
6)search your c drive for "rom.zip" or maybe just for "rom" since .zip is a file extension,not part of the name. when you find it,right click,then show in folder,or simply navigate to it in a windows explorer window. delete "rom.zip". drag the root rom to this exact location. rename it "rom.zip"(again,on windows,you prolly just want to name it "rom" as windows will automagically add the ".zip" and i dont believe you want the file to be named "rom.zip.zip )

* heres a lil tidbit- its in a different place every time you run it. so if you find it once and want to run it again,youll need to find rom.zip and swap it out each time you run the ruu.

7)once youve replaced rom.zip with the correct root rom,go to the installer and click next.
8) cross fingers

since your not getting a "bootloader fail/pass" or "hboot fail/pass" on the display,i think youre just flashing a RUU without a bootloader upate.... so i think there is hope for you

luckily,the ruu is trying to flash. if you were unfortunate enuff to be on the v3 leak rom,the ruu will not run,and no s-off bootloader. again,this indicates there is hope.

start reading on this thread,on post #140 http://androidforums.com/eris-all-things-root/350856-htc-eris-ruu-wont-run-3.html

i think it will fail with the same error,i dont want to get your hopes up. but its worth a shot :) if it does work theres a few different options from there. :)
 
I was going to say the V3 2.1 leak, but I found the RUU and the v3 leak links back-to-back in bftb0's (eu1's) thread:

[HTC ROMs] Consolidated HTC Eris RUU/OTA/ROM URLs - xda-developers

13kyl, you can download either the MR3 RUU or the LeakV3 from the above page. Here's the file sizes and MD5 sums of those files:

[ 2.36.605.1 ] a.k.a. "Leak-V3" (or MR3/"Official" RUU) - (Eclair/2.1)
RUU: RUU_Desire_C_Verizon_WWE_2.36.605.1_release_signed _with_driver.exe
130,323,038 bytes; MD5 signature: 74035b1685b279b1aa4f17fafdbec78b

PB00IMG.ZIP: Eris_LeakV3_v2.36.605.1_PB00IMG.ZIP
109,946,224 bytes; MD5 signature: 1c0b0182356242a9d673a661e7458587

The v3 leak is probably easiest since its basically the same as what he's been doing.

The V3 leak is also a PB00IMG.zip file just like the base root ROM you've been using. You'll want to:

1. Download the above "LeakV3" file
2. Verify the file size and MD5 checksum (lemme know if you still have questions about how to use the MD5 utility you just downloaded)
3. Make sure you've still got a good charge on your Eris's battery
4. Rename or remove the current (base root ROM) PB00IMG.zip file that you have on your SD card and replace it with the LeakV3 file you just downloaded
5. Boot and install like you have been

Scotty, sound okay?

I thought I got the RUU from here I'm double checking the md5 sum and I'll go get a new one if need be.

It looks like I have the same RUU from the "quoted" text above, but that RUU is different from the one a few posts up that you gave me the md5 sum for. If the RUU from a few posts up is the one I need I was wondering if you could tell me where you got that one.
 
I am on Windows 7, and I do NOT appear to have the same RUU.

im on windows 7 also... and the above is how i got it to work. shouldnt matter wich RUU you use... youre replacing the rom its going to flash with the base root rom that we had you try and flash first.
 
Ok I just figured out you were talking about the PB00IMG.ZIP md5 sum.

I do have the same md5 sum for the PB00IMG.ZIP file I have.

I'm going through the steps carefully. I'm at the point where I need to locate the rom.zip file.
 
this rom you need to sneek into the installer is the "root rom" that we were referencing in post 17. it should be the same one you downloaded from the unlockr,so if it matches the md5 listed,you can feel free to use it,no need to redownload.

if you do need to redownload,you can get the rootrom here: [HTC ROMs] Consolidated HTC Eris RUU/OTA/ROM URLs - xda-developers

[ 2.19.605.1 ] a.k.a. "Root ROM" - (Eclair/2.1)
RUU: n/a
PB00IMG.ZIP: Eris_RootROM_v2.19.605.1_PB00IMG.zip
107,427,740 bytes; MD5 signature: 63eacc5ede3b179f95dc22d8ef585f94
MultiUpload.com - Eris_RootROM_v2.19.605.1_PB00IMG.zip
OTA: n/a
 
I cannot find a rom.zip file anywhere. I wish I had XP so I could search by file extension.

Does you know how to narrow search results in Windows 7?
 
I cannot find a rom.zip file anywhere. I wish I had XP so I could search by file extension.

Does you know how to narrow search results in Windows 7?

I did a search for:

"rom type:=.zip"

that should have narrowed it down to .zip file extensions, but I have no results.
The "Show hidden files, folders, and drives" radio button is selected in folder options.
 
im using windows 7 also... i just searched drive c for "rom.zip" and found it... are your hidden files showing? it will be in a hidden folder
 
I did a search for every .zip file on my computer and went through them one by one, and none of them appear to be associated with the RUU.
 
I have selected the show hidden files and folders in folder options, but that may not make them appear in search.
 
All-right I'm calling it a night. I stayed up half the night last night and I'm tired.

Thank you so much for your help. I'll pick it up tomorrow. I just can't find that rom.zip! weird.



Thanks again guys, hopefully sleep will help.
 
sorry,i fell asleep,too. :o

how are you searching for the file? i was just using the lil search box in a windows explorer window,with the window looking at the root of the c drive.

wonder if maybe you should search all drives? is it possible your pc or laptop(not sure which youre using at this point) is storing it somewhere else?
 
Hey guys! Wow, I missed a lot after zonking-out last night :eek: ;).

----------

Yo, WormDoes! Long time, mate! Good to see you again :). Saw a few recent posts from you in the Guides forum (congrats, btw :)). Thanks for jumping-in here, too...any ideas are welcome!

----------

Hey 13kyl, my laptop is Windows 7 Home Edition and when I run the RUU, its files get extracted to here:

C:\Users\scaryalien\AppData\Local\Temp\{129C6B37-4DDB-4494-A304-E7690E996985}\{8069F5A6-8C8C-4645-8C74-CC7ACC0522E1}

and, of course, the temporary sub-folders change each time you run it, but you should be able start your search for the ROM.zip file starting in C:\Users\scaryalien\AppData\Local\Temp\, but substituting your username for "scaryalien".

The ROM.zip file should be present at the time you see the main RUU's splash screen (i.e., where it says "Welcome to the ROM Update Utility for your Android phone. Caution: Installing this update will delete all the information and data on your phone. We recommend that you review the ReadMe first for important information before continuing." and having to hit the "I understand the caution..." checkbox, etc).

Let us know.
 
scary,worm and i are partners in crime in the TB forum. i figured he may have some insight :)

the question is.. if this fails,is there anywhere else we can go? i fear its going to fail with the same error message as when it tried to run the leak v3 ruu :(

some random thots:
1)cant hboot or fastboot recovery with s-on
2)cant push jcases run any ruu exploits without an OS or fastboot
3)cant push rootrom with s-on and newer firmware
4)no newer firmware to hboot flash or RUU
5)cant modify a PB00IMG file as it wont past the signiture test

we really need s-off so we can do further repairs,and if this last effort fails im unfortunately out of ideas :(

its about time for eu1 to swoop in and save the day :)
 
scary,worm and i are partners in crime in the TB forum. i figured he may have some insight :)

the question is.. if this fails,is there anywhere else we can go? i fear its going to fail with the same error message as when it tried to run the leak v3 ruu :(

some random thots:
1)cant hboot or fastboot recovery with s-on
2)cant push jcases run any ruu exploits without an OS or fastboot
3)cant push rootrom with s-on and newer firmware
4)no newer firmware to hboot flash or RUU
5)cant modify a PB00IMG file as it wont past the signiture test

we really need s-off so we can do further repairs,and if this last effort fails im unfortunately out of ideas :(

its about time for eu1 to swoop in and save the day :)

Nice! WormDoes was around here a lot "back in the day", LOL, when the Eris was king (:eek: :D).

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...
 
Back
Top Bottom