-
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
scotty85
Extreme Android User
you might try running it again,and see if it gets any firther
also... check hboot. s-off? (crossed fingers)
Well it didn't appear to work s-on, still.
I may try that again. I will try the above first though.
scotty85
Extreme Android User
its my impression hes still useing the root rom. hopefully this is a correct statement
scotty85
Extreme Android User
yikes!the leak v3 isnt going to give you the s-off bootloader
when youre charged up,try it again... and this time use the root rom. Eris_RootROM_v2.19.605.1_PB00IMG.zip
yikes!the leak v3 isnt going to give you the s-off bootloader
when youre charged up,try it again... and this time use the root rom. Eris_RootROM_v2.19.605.1_PB00IMG.zip
+1
13kyl, what we are attempting to do by replacing the "rom.zip" file with the Root PB00IMG.zip file is to get the S-OFF bootloader installed. It is the *first* thing flashed during the RUU install ... and sometimes it occurs even if the rest of the ROM installation fails due to "version problems".
So, repeat what you tried (including getting the phone into RUU mode with fastboot before you start the RUU utility), but use the ROOT PB00IMG.zip file - and when finished, restart the phone in either fastboot or hboot mode to see if the bootloader version changed to 1.49.2000 S-OFF
I assume that means that you repeated everything, following all instructions, and still got a negative result. Did any of the RUU outputs appear to change?
Next step - boot normally (so the phone hangs on the three skaters) with the phone plugged into the PC, and try the command "adb devices". Report the output of the adb program.
Yes I think I did everything right.
I downloaded: Eris_RootROM_v2.19.605.1_PB00IMG.zip
I got the phone in RUU mode (HTC on black on the phone screen) through the RUU command line. (fastboot oem rebootRUU)
I then ran the RUU
I stopped at the screen with three dash (-) warnings right before beginning the process
I then replaced rom.zip in the temp files under my user folder (with: Eris_RootROM_v2.19.605.1_PB00IMG.zip) and renamed it rom.zip
The RUU then ran until I got a BOOTLOADER error.
I can't seem to find adb.exe
I typed "dir adb.exe" in the same directory as "fastboot.exe"
I downloaded: Eris_RootROM_v2.19.605.1_PB00IMG.zip
I got the phone in RUU mode (HTC on black on the phone screen) through the RUU command line. (fastboot oem rebootRUU)
I then ran the RUU
I stopped at the screen with three dash (-) warnings right before beginning the process
I then replaced rom.zip in the temp files under my user folder (with: Eris_RootROM_v2.19.605.1_PB00IMG.zip) and renamed it rom.zip
The RUU then ran until I got a BOOTLOADER error.
I can't seem to find adb.exe
I typed "dir adb.exe" in the same directory as "fastboot.exe"
Change to (cd) to the platform-tools directory underneath your Android SDK's installation (should be at the same level as the tools directory). Its probably there. Google changed / moved it fairly recently on new SDK installations.
From your Windows Prompt, it'll look something like this:
c:\android-sdk-windows\tools> cd ..
c:\android-sdk-windows> cd platform-tools
c:\android-sdk-windows\platform-tools> dir adb.exe
You can also use Windows Explorer to look to see if its there before doing the above.
Good luck!
And I've got to sign-off for now...its 12:36 AM local time and I have work in the morning (and I'm on-call this week, ugh!).
Thanks for joining the party, eu1...we all really appreciate your knowledge, efforts, and presence when things get "sticky"
.Good luck to you 13kyl, eu1, and Scotty if you are still up and watching.
Cheers and I'll check back in the morning.
That sounds as if we have eliminated scenarios #1 and #2 - only the long shot scenario (#3 - the "tereg race condition recovery exploit") remains.
[Tutorial] Root for LEAKERS 7/4/10 - xda-developers
I'm not sure I can recommend this method - it is not clear what percentage of folks who tried it succeeded at it. Some that did succeed at it spent days trying before they got it. Add to that the additional uncertainty of your recovery boot being a different version than the one for which the exploit was (rarely) successful.
Sorry for your lost phone - and for dragging you through all this. Just so you are aware of it, there have been several instances of phones in similar straights as yours being successfully revived using the procedures we just went through.
At this point, however, I am not optimistic that we/you are going to be successful recovering your phone - sorry.
eu1
Well thank you all for being so diligent. This really was quite a nice walk-through for me even though it didn't work out in the end. I very much appreciate the positive, helpful experience I've had on this forum. You all have been great and patient and I really appreciate it. I'll try the exploit... why not?
To be honest I've been eyeing a droid x on craigslist the last half of today. It's really cheap! If you all don't mind I'll be back to try to root that one
It takes a special kind of person to destroy a perfectly good phone, and then be itching to see how much damage he can do to the next one. Maybe some day I'll know enough not to destroy my phone, and I can help someone the way you all have helped help me. You've been very generous with your time and resources.
Thanks,
~Kyle
P.S. Then again, maybe another Eris is the way to go, I really liked it while it worked and I have more "experience" with them... decisions.
To be honest I've been eyeing a droid x on craigslist the last half of today. It's really cheap! If you all don't mind I'll be back to try to root that one
It takes a special kind of person to destroy a perfectly good phone, and then be itching to see how much damage he can do to the next one. Maybe some day I'll know enough not to destroy my phone, and I can help someone the way you all have helped help me. You've been very generous with your time and resources.
Thanks,
~Kyle
P.S. Then again, maybe another Eris is the way to go, I really liked it while it worked and I have more "experience" with them... decisions.
I would make the following recommendation, that applies to any phone you might be dealing with in the future.
Stay away from rooting instructions written up by sites like The Unlockr.
This also approximately applies to "multi-purpose" rooting tools like z4root or UnrEVOked.
Why, you say?
It comes down to this:
"Jack of all trades, master of none."
You will get far better (and correct) advise from forums with contributors that own and specialize in manipulation of individual phone models. Particularly the individual phone forums at XDA. The problem with sites like the Unlockr is that they try to provide rooting advise for every phone under the sun; in general, they do this essentially by copying content from other sites. Because there is often no direct experience with a particular phone, they sometimes make critical and/or boneheaded mistakes in their editorial process. Sure, those guys have probably owned a phone or two - but not every single one that's on the market. Nobody has that much experience.
UnrEVOked and Z4root are slightly different - they are put together by folks with solid technical skills, but the same problem of lack of specialization occurs here, too - when there is a minor hiccup revolving around a specific bootloader or specific ROM on a specific phone model - what is the chance that a general-purpose tool will have the correct logic in it to deal with that special case?
And there's another thing to be aware of: if you use a "simple to use" and "opaque" (slick & simple GUI) rooting tool, when something goes wrong, there will be no-one available to help you understand what happened, or how to recover from what went wrong. And good luck getting any support from the program authors. In contrast, methods that you find in forums might be a little more clunky, but you will learn more about how your phone works - and more importantly, there will be a number of folks that have gone in front of you, so that if something goes wrong - they will probably already be familiar with those troubles and able to help.
Good luck
eu1
Thank you so much erisuser1. I will approach my next phone much more studiously.
If anyone checks back on this post one more time I'd like to throw something out there for feedback. I believe my next step will actually be to do this:
Buy an Eris off of ebay with a broken screen (guaranteed to run). They are available for $20.00 or so. I will use the motherboard from that phone and merge it with the lcd/touchscreen hardware from mine.
If you foresee hardware conflicts please let me know.
Seriously, thanks again so much for your help.
If anyone checks back on this post one more time I'd like to throw something out there for feedback. I believe my next step will actually be to do this:
Buy an Eris off of ebay with a broken screen (guaranteed to run). They are available for $20.00 or so. I will use the motherboard from that phone and merge it with the lcd/touchscreen hardware from mine.
If you foresee hardware conflicts please let me know.
Seriously, thanks again so much for your help.
Kyle,
Kudos to you again for hanging-in there with us... This actually went better, communication-wise, than a lot of sessions we've been through and much of that credit goes to you.
erisuser1 is really a shining example of the kind of members with extensive depth of knowledge about Android phones (and practically everything else, LOL).
Kudos to metlcat for reaching-out to several of us to make sure we saw your thread to try to help.
Thanks too to Scotty for always being there and willing to try any crazy experiments on his phone that will be helpful, interesting, and instructive.
I hope that you'll continue to be an active member of AndroidForums no matter which phone you end-up with, so we can count you too as a contributing member of our little corner of the Android world.
Cheers!
Kudos to you again for hanging-in there with us... This actually went better, communication-wise, than a lot of sessions we've been through and much of that credit goes to you.
erisuser1 is really a shining example of the kind of members with extensive depth of knowledge about Android phones (and practically everything else, LOL).
Kudos to metlcat for reaching-out to several of us to make sure we saw your thread to try to help.
Thanks too to Scotty for always being there and willing to try any crazy experiments on his phone that will be helpful, interesting, and instructive.
I hope that you'll continue to be an active member of AndroidForums no matter which phone you end-up with, so we can count you too as a contributing member of our little corner of the Android world.
Cheers!