Hello all, First time poster here. Having some issues of course with my Eris. I rooted it with scary aliens no trackball required recovery mode. Everything was going well for almost a year. Couple nights ago I was having trouble with anything working right on the phone. I decided to try and pull the battery and let the phone reset. It got stuck on the "android" startup screen and was like that for about 2 hours. I pulled the battery again, and did a master reset. Lost some pictures and some songs, but most of my stuff was backed up. I thought everything was going to be fine, but yesterday I noticed that I wasn't getting text messages. I can send them, but can't receive them. So I've been trying to get into recovery mode for a while and it's been a no go. I get the screen with the 3 droids skateboarding and the phone freezes up. When I turn the phone on normally (without recovery) it works fine. I'm thinking a bunch of my sd files got messed up (when I open astro file manager a lot of the files are empty now) somehow and this is the result? Anyway, I didn't want to try anything too drastic before I consulted the wise minds here and got some advice about how to proceed. Any help would be much appreciated. Let me know what info I can provide. Thanks a ton in advance! This forum has been a ton of help!
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root Eris half-brick
- Thread starter zloetakoe
- Start date
-
- Tags
- htc droid eris
Podivin
Android Expert
Welcome to the forum.
The first thing that *I* can think of would be restore a backup that you hopefully have made sometime in the past.
If you don't have one, then reflashing the ROM might solve the problem - doing this of course would wipe all data on your phone, so backup what you can first. (Titanium Backup is your friend!
)
The first thing that *I* can think of would be restore a backup that you hopefully have made sometime in the past.
If you don't have one, then reflashing the ROM might solve the problem - doing this of course would wipe all data on your phone, so backup what you can first. (Titanium Backup is your friend!
)Try downloading to your computer (to make sure that the files are unzipping properly - it sounds like you are getting an incomplete download) and copy the files over to the phone's SD card from the PC. Then try running the GScript from the phone.
If that doesn't work, it may be time for more drastic measures.
By the way, do you have HBOOT S-ON or S-OFF (restart the phone to HBOOT by holding VolDn when powering up and look at the first line.) Also, if it is S-ON, which version number is HBOOT? (1.46.0000, 1.47.0000, 1.49.0000 would be the three that I know of.)
If that doesn't work, it may be time for more drastic measures.
By the way, do you have HBOOT S-ON or S-OFF (restart the phone to HBOOT by holding VolDn when powering up and look at the first line.) Also, if it is S-ON, which version number is HBOOT? (1.46.0000, 1.47.0000, 1.49.0000 would be the three that I know of.)
zloetakoe,
You should still have several options for getting Amon_RA's recovery re-installed on your phone, which is where I think doogald is going with his questions about which HBOOT and security setting you have.
It is a little curious that you've somehow lost custom recovery, though...
You also didn't mention whether or not you had a Nandroid backup saved-off somewhere (that would help you, although not for the recovery).
Let us know.
Cheers!
Right, just in case he can't get Amon_RA on with traditional methods, it'd be nice to know if we can use fastboot ...
Doogald,
PB00100 XC SHIP S-ON
HBOOT-1.49.0000 (PB0010000)
SA,
I think a bunch of files got messed up on my SD card somehow. A LOT of stuff not working properly from the SD card. Maybe the SD card itself is jacked, but most of the phone is working? Unfortunately I don't ever remember doing a Nandroid backup. So I don't think there is one? Unless the Eris is smart enough to do that for me.
Also for both of you, I've tried to connect a cable from the phone to the computer and the computer doesn't recognize the phone as a storage device and I don't get the usual USB symbol in the notification bar.
???
Doogald, If I understand you correctly I could download the recovery .zip to my computer, unzip it there and then transfer the files to the eris? I would love to do that, but I'm unsure if the computer and the eris are able to communicate at the moment.
PB00100 XC SHIP S-ON
HBOOT-1.49.0000 (PB0010000)
SA,
I think a bunch of files got messed up on my SD card somehow. A LOT of stuff not working properly from the SD card. Maybe the SD card itself is jacked, but most of the phone is working? Unfortunately I don't ever remember doing a Nandroid backup. So I don't think there is one? Unless the Eris is smart enough to do that for me.
Also for both of you, I've tried to connect a cable from the phone to the computer and the computer doesn't recognize the phone as a storage device and I don't get the usual USB symbol in the notification bar.
???
Doogald, If I understand you correctly I could download the recovery .zip to my computer, unzip it there and then transfer the files to the eris? I would love to do that, but I'm unsure if the computer and the eris are able to communicate at the moment.
zloetakoe,
Looks like your phone had one of the 2.1 leaks installed by your HBOOT version and security status.
You won't be able to re-flash your recovery with fastboot since you have an S-ON HBOOT.
And sadly, there is not auto-creation of a Nandroid backup enforced (if only there were, LOL).
You didn't mention if you were running a custom ROM or not, but you might be able to simply download and re-run jcase's 1-click root app (https://market.android.com/search?q=erisroot&so=1&c=apps) or the version that I modded to use my trackball-optional version of Amon_RA's custom recovery--see scenario 5 in here:
http://androidforums.com/eris-all-things-root/214240-amon_ra-1-6-2-custom-recovery-trackball-not-required.html
I'm sure doogald will also reply with something I missed...he's kind of cool like that
.
Cheers!
P.S. apologies for not saying welcome to the AndroidForums earlier than now (sorry its under these circumstances).
Looks like your phone had one of the 2.1 leaks installed by your HBOOT version and security status.
You won't be able to re-flash your recovery with fastboot since you have an S-ON HBOOT.
And sadly, there is not auto-creation of a Nandroid backup enforced (if only there were, LOL).
You didn't mention if you were running a custom ROM or not, but you might be able to simply download and re-run jcase's 1-click root app (https://market.android.com/search?q=erisroot&so=1&c=apps) or the version that I modded to use my trackball-optional version of Amon_RA's custom recovery--see scenario 5 in here:
http://androidforums.com/eris-all-things-root/214240-amon_ra-1-6-2-custom-recovery-trackball-not-required.html
I'm sure doogald will also reply with something I missed...he's kind of cool like that
.Cheers!
P.S. apologies for not saying welcome to the AndroidForums earlier than now (sorry its under these circumstances).
Thanks a lot for all the help, Doesn't sound good. I'll keep tweaking it until it dies or heals itself.zloetakoe,
Looks like your phone had one of the 2.1 leaks installed by your HBOOT version and security status.
You won't be able to re-flash your recovery with fastboot since you have an S-ON HBOOT.
And sadly, there is not auto-creation of a Nandroid backup enforced (if only there were, LOL).
You didn't mention if you were running a custom ROM or not, but you might be able to simply download and re-run jcase's 1-click root app (https://market.android.com/search?q=erisroot&so=1&c=apps) or the version that I modded to use my trackball-optional version of Amon_RA's custom recovery--see scenario 5 in here:
http://androidforums.com/eris-all-t...2-custom-recovery-trackball-not-required.html
I'm sure doogald will also reply with something I missed...he's kind of cool like that
Cheers!
P.S. apologies for not saying welcome to the AndroidForums earlier than now (sorry its under these circumstances).
I think I'm running OMGB (something like that)
So I've been trying all the suggestions. I've reloaded the 1 click root by jcase. Nothin working.
Anything else?
Thanks for all the help by the way.
EDIT: wow dooglad, must have read my mind, lol. I'll try the 1click a few more times just to make sure that I'm doing it right. Right now when I get to the part where amon-ra recovery pops up, I just get the same 3 skateboarding droids.
Anything else?
Thanks for all the help by the way.
EDIT: wow dooglad, must have read my mind, lol. I'll try the 1click a few more times just to make sure that I'm doing it right. Right now when I get to the part where amon-ra recovery pops up, I just get the same 3 skateboarding droids.
Hey, just one more thing: if you start in HBOOT (hold VolDn while starting until the HBOOT screen shows) there should be a little text display saying something like "Press VolUp for Recovery." What happens when you press VolUp at that point? Skateboarders or does it go into Recovery?
Scary, I'm wondering if zloetakoe's phone has corruption on the MISC partition. I'm thinking (with the exception of the fact that the phone actually runs) it looks a lot like this: [SOLVED] Anyway to Unbricked a Droid Eris? - xda-developers (Zloetake, *don't* try any of that yet.)
I'm trying to decide if it would be smart (assuming that Recovery doesn't start when zloetakoe tries VolUp from HBOOT....) to try installing an RUU next, and then, if it works, root using 1-click?
It's a common issue ...
Scary, I'm wondering if zloetakoe's phone has corruption on the MISC partition. I'm thinking (with the exception of the fact that the phone actually runs) it looks a lot like this: [SOLVED] Anyway to Unbricked a Droid Eris? - xda-developers (Zloetake, *don't* try any of that yet.)
I'm trying to decide if it would be smart (assuming that Recovery doesn't start when zloetakoe tries VolUp from HBOOT....) to try installing an RUU next, and then, if it works, root using 1-click?
It's a common issue ...
Sorry for the delay...I was messing with phone stuff with my son and then had to re-read the XDA link you sent me, doogald (man, all that seems like forever ago, LOL...).
Yeah, it seems similar...and the 3 skating Androids when trying to boot into recovery certainly indicates one or more partitions are borked...
doogald, when you say RUU, you mean the RUU plus the replace the ROM.zip with the base root ROM's PB00IMG.zip file, right (so zloetakoe can (hopefully) get an S-OFF HBOOT) and then use fastboot to flash and/or boot into custom recovery.
zloetakoe, your phone isn't 100% right is it (texting issues, right?)...do you really want to mess with this (i.e., if your phone is partially working and that's liveable--we just don't want to lead you down a path that would be worse than things are now).
We don't have a way to backup your stuff now, but your phone's situation does seem less dire than a few we've seen.
edit / P.S. zloetakoe, you'll have to bust-out some various rooting skillz like using the Android SDK, adb, fastboot, the HTC RUU (ROM update utility), etc. in order to proceed here...that's part of the equation...
Sweet. I'm pretty comfortable messing with the phone as long as someone can point me in the general direction. I enjoy learning as I go. If the phone fails, it was fun while it lasted and I'll pick up another one. If I didn't like doing this stuff, I'd have given up on this project long ago.
If only I knew as much about these phones as you two do.I've attempted to get to recovery through HBOOT with the vol. up trick. Still just getting 3 frozen droids attempting tricks on skateboards.
Sweet. I'm pretty comfortable messing with the phone as long as someone can point me in the general direction. I enjoy learning as I go. If the phone fails, it was fun while it lasted and I'll pick up another one. If I didn't like doing this stuff, I'd have given up on this project long ago.
I've attempted to get to recovery through HBOOT with the vol. up trick. Still just getting 3 frozen droids attempting tricks on skateboards.
Yeah, it sounds like the recovery partition (at least) is borked.
I'd start leading you through some things tonight, but in a little while, I have to do some tasks for my "real" work, LOL, that will take me a couple of hours (and afterwards, bedtime
).You could start reading the XDA thread that doogald linked above (don't necessarily do anything yet, mind you) so you can see and prepare the things that will/might be involved.
Its really not too, hard, but the nature of leading someone through all of this over forums posts is certainly not ideal, eh?
. At least you have the best template (i.e., the XDA thread), guided by bftb0 (our erisuser1, by the way) who is the guy I'd want helping me with any serious issue on my phone.Also note in the second post of that XDA thread where bftb0 references this thread: [Q] semi-Bricked?? fix? - xda-developers. That thread also has some key information and steps that are referenced that would help if you were familiar with.
I've done the ROM.zip replacement in the RUU before (been a while), but I've never run the ErisMTDNuke.zip file (few have, thankfully, LOL), so, if the RUU rooting trick that SoSicWiTiT discovered works for you to get the S-OFF HBOOT, you should be well on your way to recovering your phone (fingers crossed, of course).
If I'm not back to you in the morning, certainly doogald might be and is eminently qualified to guide you in this effort.
Anyway, start doing a little reading if you haven't already. Sorry for the forced delay on my part, but I've got work stuff I gotta do tonight that I can't ignore.
Cheers!
No problem. The phone works for now. I'll do my own homework and let you know what I think will work best. If you guys concur I'll have at it and see where I get cornered! Thanks for your help, get some rest!Yeah, it sounds like the recovery partition (at least) is borked.
I'd start leading you through some things tonight, but in a little while, I have to do some tasks for my "real" work, LOL, that will take me a couple of hours (and afterwards, bedtime
You could start reading the XDA thread that doogald linked above (don't necessarily do anything yet, mind you) so you can see and prepare the things that will/might be involved.
Its really not too, hard, but the nature of leading someone through all of this over forums posts is certainly not ideal, eh?
Also note in the second post of that XDA thread where bftb0 references this thread: [Q] semi-Bricked?? fix? - xda-developers. That thread also has some key information and steps that are referenced that would help if you were familiar with.
I've done the ROM.zip replacement in the RUU before (been a while), but I've never run the ErisMTDNuke.zip file (few have, thankfully, LOL), so, if the RUU rooting trick that SoSicWiTiT discovered works for you to get the S-OFF HBOOT, you should be well on your way to recovering your phone (fingers crossed, of course).
If I'm not back to you in the morning, certainly doogald might be and is eminently qualified to guide you in this effort.
Anyway, start doing a little reading if you haven't already. Sorry for the forced delay on my part, but I've got work stuff I gotta do tonight that I can't ignore.
Cheers!
Unfortunately, I'm away all day, starting about right now. I'm heading up to Maine to watch my daughter sing in a recital.
I think that if the RUU was going to be run that it may as well be done with the replace the ROM.zip file trick. I'll be able to point out the tricks later on. I'm thinking about the exact steps to start the RUU, find the location of ROM.zip, the way to replace it with the PB00IMG.zip file with the S-OFF HBOOT, etc.
I think that if the RUU was going to be run that it may as well be done with the replace the ROM.zip file trick. I'll be able to point out the tricks later on. I'm thinking about the exact steps to start the RUU, find the location of ROM.zip, the way to replace it with the PB00IMG.zip file with the S-OFF HBOOT, etc.
Unfortunately, I'm away all day, starting about right now. I'm heading up to Maine to watch my daughter sing in a recital.
I think that if the RUU was going to be run that it may as well be done with the replace the ROM.zip file trick. I'll be able to point out the tricks later on. I'm thinking about the exact steps to start the RUU, find the location of ROM.zip, the way to replace it with the PB00IMG.zip file with the S-OFF HBOOT, etc.
Yeah, I'm gathering notes and links to post here for zloetakoe...not sure which RUU to have him use, though...there are two listed in bftb0's thread:
[HTC ROMs] Consolidated HTC Eris RUU/OTA/ROM URLs - xda-developers
(I'm guessing the second one).
Anyway, I'll post back here in a bit with an outline...have a good, safe trip, doogald.
Cheers!
However, you should be able to find the RUU here: Multiupload.com - upload your files to multiple file hosting sites!
and the PB00IMG.zip file with the S-OFF bootloader here: Multiupload.com - upload your files to multiple file hosting sites!
(Thanks, as always, to bftb0/Erisuser1 and his post here: [HTC ROMs] Consolidated HTC Eris RUU/OTA/ROM URLs - xda-developers )
and the PB00IMG.zip file with the S-OFF bootloader here: Multiupload.com - upload your files to multiple file hosting sites!
(Thanks, as always, to bftb0/Erisuser1 and his post here: [HTC ROMs] Consolidated HTC Eris RUU/OTA/ROM URLs - xda-developers )
I just cross-posted the link before reading your post, but the RUU is the one under "[ 2.36.605.1 ] a.k.a. "Leak-V3" (or MR3/"Official" RUU)" - the RUU, not the PB00IMG.zip file.
Yeah, they all match my links from the HTC ROMs list eu1 created over on XDA, but the RUU download doesn't match the first or second one in that list (I'll grab it and see which one it is).
BRB...
LOL, thanks! Didn't see that third .exe in the last...this makes me feel better
.Its good to have a second set of eyes, eh?
I'm looking in an old thread I was involved in (http://androidforums.com/eris-all-things-root/371983-help-save-brick-3.html) to get the detailed steps for running the RUU (that'll make things a little easier for zloetakoe).
Cheers!
zloetakoe,
Okay, since your phone has the 1.49.0000 S-ON bootloader, you don't have any many options for fixing it. But the good news is that your phone still (pretty-much) works (i.e., Android works), but custom recovery clearly seems borked.
So, the keep seems to be trying to get the S-OFF HBOOT installed. You can't directly load the base root ROM's PB00IMG.zip because of the "main version is older issues" you'd get.
So, we can try SoSicWiTiT's RUU/rom.zip rooting trick to try to get the RUU to flash the S-OFF bootloader for you.
I must warn you that the stuff below may not necessarily work...we tried this on another phone in your similar situation without success (http://androidforums.com/eris-all-things-root/371983-help-save-brick.html). We'll know pretty quickly, though, since you'll either gain S-OFF via the RUU / rom.zip swap or you won't.
By the way, there's a TON of good information and detail in that above "help save a brick" thread that might be useful to you or at least provide more explaination for some of the tasks below).
-------------------------------------------------------------------------
Resources / downloads you'll need:
1. First, grab the base root ROM from here:
Multiupload.com - upload your files to multiple file hosting sites!
referenced in this page: [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
Be sure to verify the file's size and MD5 checksum (don't want any "variables" here).
2. Next, grab the MR3 "Official" RUU (ROM update utility) from the above same page:
Multiupload.com - upload your files to multiple file hosting sites!
[ 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
MultiUpload.com - RUU_Desire_C_Verizon_WWE_2.36.605.1_release_signed _with_driver.exe
You don't need the PB00IMG.zip that's associated with that RUU--we'll be using the base root ROM's PB00IMG.zip instead (that you grabbed above).
3. Third, grab the ErisMTDNuke_v0.9.zip file from this post:
xda-developers - View Single Post - [SOLVED] Anyway to Unbricked a Droid Eris?
http://forum.xda-developers.com/attachment.php?attachmentid=527459&d=1298672645
Be sure to verify the MD5 and size of the file after downloading:
MD5: d671b18143910f297c8ebe8454b59fd7
File Size: 4,250,141 bytes
4. Lastly, let's grab my trackball-optional version of Amon_RA's custom recovery:
http://androidforums.com/eris-all-t...2-custom-recovery-trackball-not-required.html
https://sites.google.com/site/scary...ecovery-RA-eris-v1.6.2-trackball-optional.img
File size: 3,926,016 bytes
MD5 checksum: 3217768b831a3841180699942204762d
You'll want to place this file in the c:\android-sdk-windows\platform-tools directory (or where ever adb.exe and fastboot.exe is).
-------------------------------------------------------------------------
The process:
1. Make sure you've got a full charge on your phone
2. Get all files and resources downloaded (above) and ready
3. Re-verify that you cannot boot into custom recovery:
-- press, simultaneously, both the call/send and end/pwr hard keys on the front bottom of the phone
-- this should take you to the FASTBOOT menu (or FASTBOOT USB if you have your USB cable plugged-in)
-- press the volume-DOWN key rocker to go into HBoot Mode
-- press the volume-UP key rocker to go into recovery (hopefully custom)
-- one of three things will happen here:
a. you'll see the stock recovery (triangle, etc.)
b. you'll the Amon_RA's custom recovery (pretty sure you won't at this point)
c. you'll get the three skating Androids that you've previously reported
4. Okay, if you are seeing 3.c (three skating Androids) instead of custom recovery, let's do the RUU rom.zip replacement trick. Go ahead and do a battery-pull to get your phone back. Let it charge while we start the RUU (we'll soon be putting it into FASTBOOT USB mode as described above).
5. From your Windows PC, go-ahead and run the RUU (ROM update utility) and make sure you have the base root ROM's PB00IMG.zip file handy and ready to go. Don't proceed past the main / first page.
6. Now, for the part that should be simple but is tricky for some (stupid MS/Windows, LOL), is to find the "rom.zip" file on your PC. Reference these posts:
xda-developers - View Single Post - [SOLVED] Anyway to Unbricked a Droid Eris?
http://androidforums.com/eris-all-things-root/371983-help-save-brick-2.html#post2931013
http://androidforums.com/eris-all-things-root/371983-help-save-brick-2.html#post2931864
Like I indicated in my post, I'm running Windows 7 Home Premium and I found the rom.zip file in C:\Users\scaryalien\AppData\Local\Temp\{bunch-of-hex-chars}\{bunch-of-hex-chars} with a simple Windows Explorer search of the C:\Users\scaryalien\AppData\Local\Temp folder structure.
Go ahead and rename or delete the original rom.zip (or ROM.zip) and replace it with the base root ROM's PB00IMG.zip file (i.e., put it in the same place where the rom.zip file was and name it rom.zip).
7. Boot your phone into FASTBOOT USB mode (i.e., have it connected between your phone and the PC) and then start running the RUU to see if it will get the base root ROM (disguised as the rom.zip) installed on your phone so you can get the S-OFF HBOOT.
8. Note: the RUU might very well fail (with an RUU Error 110), but if / when that happens, re-check your HBOOT version--hopefully, you'll be 1.49.2000 and S-OFF.
-------------------------------------------------------------------------
I'm going to pause here at this point since going any further is entirely contingent and reliant on you being able to get the S-OFF HBOOT.
If you do have an S-OFF HBOOT, you'll next need to bust-out your Android SDK skillz and prepare to run some fastboot commands
Future steps
------------
1. You might be able to flash custom recovery this way:
-- or --
you might need to soft-boot custom recovery (i.e., in-memory) like this:
which you can only do when you have the S-OFF HBOOT.
2. If you do see custom recovery, transfer the ErisMTDNuke_v0.9.zip file to the phone's SD card and try to flash it in recovery. This will "reset" all of the memory blocks marked as bad on your phone's internal memory partitions.
If this is successful, you should be able to wipe (as normal) and re-flash your favorite ROM.
-------------------------------------------------------------------------
Sorry for the massive post .
I'm going to go-ahead and post this and go-back and clean-up the links and formatting.
Any success you might have for the above should really go to bftb0 / erisuser1 and SoSicWiTiT for working throuh this in the first place.
Cheers and let me know if you have any questions before you begin.
Okay, since your phone has the 1.49.0000 S-ON bootloader, you don't have any many options for fixing it. But the good news is that your phone still (pretty-much) works (i.e., Android works), but custom recovery clearly seems borked.
So, the keep seems to be trying to get the S-OFF HBOOT installed. You can't directly load the base root ROM's PB00IMG.zip because of the "main version is older issues" you'd get.
So, we can try SoSicWiTiT's RUU/rom.zip rooting trick to try to get the RUU to flash the S-OFF bootloader for you.
I must warn you that the stuff below may not necessarily work
...we tried this on another phone in your similar situation without success (http://androidforums.com/eris-all-things-root/371983-help-save-brick.html). We'll know pretty quickly, though, since you'll either gain S-OFF via the RUU / rom.zip swap or you won't.By the way, there's a TON of good information and detail in that above "help save a brick" thread that might be useful to you or at least provide more explaination for some of the tasks below).
-------------------------------------------------------------------------
Resources / downloads you'll need:
1. First, grab the base root ROM from here:
Multiupload.com - upload your files to multiple file hosting sites!
referenced in this page: [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
Be sure to verify the file's size and MD5 checksum (don't want any "variables" here
).2. Next, grab the MR3 "Official" RUU (ROM update utility) from the above same page:
Multiupload.com - upload your files to multiple file hosting sites!
[ 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
MultiUpload.com - RUU_Desire_C_Verizon_WWE_2.36.605.1_release_signed _with_driver.exe
You don't need the PB00IMG.zip that's associated with that RUU--we'll be using the base root ROM's PB00IMG.zip instead (that you grabbed above).
3. Third, grab the ErisMTDNuke_v0.9.zip file from this post:
xda-developers - View Single Post - [SOLVED] Anyway to Unbricked a Droid Eris?
http://forum.xda-developers.com/attachment.php?attachmentid=527459&d=1298672645
Be sure to verify the MD5 and size of the file after downloading:
MD5: d671b18143910f297c8ebe8454b59fd7
File Size: 4,250,141 bytes
4. Lastly, let's grab my trackball-optional version of Amon_RA's custom recovery:
http://androidforums.com/eris-all-t...2-custom-recovery-trackball-not-required.html
https://sites.google.com/site/scary...ecovery-RA-eris-v1.6.2-trackball-optional.img
File size: 3,926,016 bytes
MD5 checksum: 3217768b831a3841180699942204762d
You'll want to place this file in the c:\android-sdk-windows\platform-tools directory (or where ever adb.exe and fastboot.exe is).
-------------------------------------------------------------------------
The process:
1. Make sure you've got a full charge on your phone
2. Get all files and resources downloaded (above) and ready
3. Re-verify that you cannot boot into custom recovery:
-- press, simultaneously, both the call/send and end/pwr hard keys on the front bottom of the phone
-- this should take you to the FASTBOOT menu (or FASTBOOT USB if you have your USB cable plugged-in)
-- press the volume-DOWN key rocker to go into HBoot Mode
-- press the volume-UP key rocker to go into recovery (hopefully custom)
-- one of three things will happen here:
a. you'll see the stock recovery (triangle, etc.)
b. you'll the Amon_RA's custom recovery (pretty sure you won't at this point
)c. you'll get the three skating Androids that you've previously reported
4. Okay, if you are seeing 3.c (three skating Androids) instead of custom recovery, let's do the RUU rom.zip replacement trick. Go ahead and do a battery-pull to get your phone back. Let it charge while we start the RUU (we'll soon be putting it into FASTBOOT USB mode as described above).
5. From your Windows PC, go-ahead and run the RUU (ROM update utility) and make sure you have the base root ROM's PB00IMG.zip file handy and ready to go. Don't proceed past the main / first page.
6. Now, for the part that should be simple but is tricky for some (stupid MS/Windows, LOL), is to find the "rom.zip" file on your PC. Reference these posts:
xda-developers - View Single Post - [SOLVED] Anyway to Unbricked a Droid Eris?
http://androidforums.com/eris-all-things-root/371983-help-save-brick-2.html#post2931013
http://androidforums.com/eris-all-things-root/371983-help-save-brick-2.html#post2931864
Like I indicated in my post, I'm running Windows 7 Home Premium and I found the rom.zip file in C:\Users\scaryalien\AppData\Local\Temp\{bunch-of-hex-chars}\{bunch-of-hex-chars} with a simple Windows Explorer search of the C:\Users\scaryalien\AppData\Local\Temp folder structure.
Go ahead and rename or delete the original rom.zip (or ROM.zip) and replace it with the base root ROM's PB00IMG.zip file (i.e., put it in the same place where the rom.zip file was and name it rom.zip).
7. Boot your phone into FASTBOOT USB mode (i.e., have it connected between your phone and the PC) and then start running the RUU to see if it will get the base root ROM (disguised as the rom.zip
) installed on your phone so you can get the S-OFF HBOOT.8. Note: the RUU might very well fail (with an RUU Error 110), but if / when that happens, re-check your HBOOT version--hopefully, you'll be 1.49.2000 and S-OFF.
-------------------------------------------------------------------------
I'm going to pause here at this point since going any further is entirely contingent and reliant on you being able to get the S-OFF HBOOT.
If you do have an S-OFF HBOOT, you'll next need to bust-out your Android SDK skillz and prepare to run some fastboot commands
Future steps
------------
1. You might be able to flash custom recovery this way:
Code:
c:\android-sdk-windows\platform-tools> [B]fastboot flash recovery recovery-RA-eris-v1.6.2-trackball-optional.img and then reboot your phone into your shiny-new custom recovery[/B]-- or --
you might need to soft-boot custom recovery (i.e., in-memory) like this:
Code:
c:\android-sdk-windows\platform-tools> [B]fastboot boot recovery-RA-eris-v1.6.2-trackball-optional.img[/B]which you can only do when you have the S-OFF HBOOT.
2. If you do see custom recovery, transfer the ErisMTDNuke_v0.9.zip file to the phone's SD card and try to flash it in recovery. This will "reset" all of the memory blocks marked as bad on your phone's internal memory partitions.
If this is successful, you should be able to wipe (as normal) and re-flash your favorite ROM.
-------------------------------------------------------------------------
Sorry for the massive post
.I'm going to go-ahead and post this and go-back and clean-up the links and formatting.
Any success you might have for the above should really go to bftb0 / erisuser1 and SoSicWiTiT for working throuh this in the first place.
Cheers and let me know if you have any questions before you begin.
zloetakoe,
Okay, since your phone has the 1.49.0000 S-ON bootloader, you don't have any many options for fixing it. But the good news is that your phone still (pretty-much) works (i.e., Android works), but custom recovery clearly seems borked.
So, the keep seems to be trying to get the S-OFF HBOOT installed. You can't directly load the base root ROM's PB00IMG.zip because of the "main version is older issues" you'd get.
So, we can try SoSicWiTiT's RUU/rom.zip rooting trick to try to get the RUU to flash the S-OFF bootloader for you.
I must warn you that the stuff below may not necessarily work
By the way, there's a TON of good information and detail in that above "help save a brick" thread that might be useful to you or at least provide more explaination for some of the tasks below).
-------------------------------------------------------------------------
Resources / downloads you'll need:
1. First, grab the base root ROM from here:
Multiupload.com - upload your files to multiple file hosting sites!
referenced in this page: [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
[COLOR="Red"]Be sure to verify the file's size and MD5 checksum (don't want any "variables" here
2. Next, grab the MR3 "Official" RUU (ROM update utility) from the above same page:
Multiupload.com - upload your files to multiple file hosting sites!
[ 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
MultiUpload.com - RUU_Desire_C_Verizon_WWE_2.36.605.1_release_signed _with_driver.exe
You don't need the PB00IMG.zip that's associated with that RUU--we'll be using the base root ROM's PB00IMG.zip instead (that you grabbed above).
3. Third, grab the ErisMTDNuke_v0.9.zip file from this post:
xda-developers - View Single Post - [SOLVED] Anyway to Unbricked a Droid Eris?
http://forum.xda-developers.com/attachment.php?attachmentid=527459&d=1298672645
[COLOR="red"]Be sure to verify the MD5 and size of the file after downloading[/COLOR]:
MD5: d671b18143910f297c8ebe8454b59fd7
File Size: 4,250,141 bytes
4. Lastly, let's grab my trackball-optional version of Amon_RA's custom recovery:
http://androidforums.com/eris-all-t...2-custom-recovery-trackball-not-required.html
https://sites.google.com/site/scary...ecovery-RA-eris-v1.6.2-trackball-optional.img
File size: 3,926,016 bytes
MD5 checksum: 3217768b831a3841180699942204762d
You'll want to place this file in the c:\android-sdk-windows\platform-tools directory (or where ever adb.exe and fastboot.exe is).
-------------------------------------------------------------------------
The process:
1. [COLOR="Blue"]Make sure you've got a full charge on your phone[/COLOR]
2. Get all files and resources downloaded (above) and ready
3. Re-verify that you cannot boot into custom recovery:
-- press, simultaneously, both the call/send and end/pwr hard keys on the front bottom of the phone
-- this should take you to the FASTBOOT menu (or FASTBOOT USB if you have your USB cable plugged-in)
-- press the volume-DOWN key rocker to go into HBoot Mode
-- press the volume-UP key rocker to go into recovery (hopefully custom)
-- one of three things will happen here:
a. you'll see the stock recovery (triangle, etc.)
b. you'll the Amon_RA's custom recovery (pretty sure you won't at this point
c. you'll get the three skating Androids that you've previously reported
4. Okay, if you are seeing 3.c (three skating Androids) instead of custom recovery, let's do the RUU rom.zip replacement trick. Go ahead and do a battery-pull to get your phone back. Let it charge while we start the RUU (we'll soon be putting it into FASTBOOT USB mode as described above).
5. From your Windows PC, go-ahead and run the RUU (ROM update utility) and make sure you have the base root ROM's PB00IMG.zip file handy and ready to go. Don't proceed past the main / first page.
6. Now, for the part that should be simple but is tricky for some (stupid MS/Windows, LOL), is to find the "rom.zip" file on your PC. Reference these posts:
xda-developers - View Single Post - [SOLVED] Anyway to Unbricked a Droid Eris?
http://androidforums.com/eris-all-things-root/371983-help-save-brick-2.html#post2931013
http://androidforums.com/eris-all-things-root/371983-help-save-brick-2.html#post2931864
Like I indicated in my post, I'm running Windows 7 Home Premium and I found the rom.zip file in C:\Users\scaryalien\AppData\Local\Temp\{bunch-of-hex-chars}\{bunch-of-hex-chars} with a simple Windows Explorer search of the C:\Users\scaryalien\AppData\Local\Temp folder structure.
Go ahead and rename or delete the original rom.zip (or ROM.zip) and replace it with the base root ROM's PB00IMG.zip file (i.e., put it in the same place where the rom.zip file was and name it rom.zip).
7. Boot your phone into FASTBOOT USB mode (i.e., have it connected between your phone and the PC) and then start running the RUU to see if it will get the base root ROM (disguised as the rom.zip
8. Note: the RUU might very well fail (with an RUU Error 110), but if / when that happens, re-check your HBOOT version--hopefully, you'll be 1.49.2000 and S-OFF.
-------------------------------------------------------------------------
I'm going to pause here at this point since going any further is entirely contingent and reliant on you being able to get the S-OFF HBOOT.
If you do have an S-OFF HBOOT, you'll next need to bust-out your Android SDK skillz and prepare to run some fastboot commands
Future steps
------------
1. You might be able to flash custom recovery this way:
Code:c:\android-sdk-windows\platform-tools> [B]fastboot flash recovery recovery-RA-eris-v1.6.2-trackball-optional.img and then reboot your phone into your shiny-new custom recovery[/B]
-- or --
you might need to soft-boot custom recovery (i.e., in-memory) like this:
Code:c:\android-sdk-windows\platform-tools> [B]fastboot boot recovery-RA-eris-v1.6.2-trackball-optional.img[/B]
which you can only do when you have the S-OFF HBOOT.
2. If you do see custom recovery, transfer the ErisMTDNuke_v0.9.zip file to the phone's SD card and try to flash it in recovery. This will "reset" all of the memory blocks marked as bad on your phone's internal memory partitions.
If this is successful, you should be able to wipe (as normal) and re-flash your favorite ROM.
-------------------------------------------------------------------------
Sorry for the massive post
I'm going to go-ahead and post this and go-back and clean-up the links and formatting.
Any success you might have for the above should really go to bftb0 / erisuser1 and SoSicWiTiT for working throuh this in the first place.
Cheers and let me know if you have any questions before you begin.
I almost fell asleep reading that.
Good post.
I almost fell asleep reading that.
Good post.
Thanks, BC
.A little "tl;dr", eh?
Hopefully it won't been too much for zloetakoe, but I think he's up to the challenge.
Cheers!
P.S., for zloetakoe and dooglad, I'll be AKF later this afternoon (my regular Sunday afternoon soccer pickup game--probably only able to do this a few more times this season before winter clamps down on us), but I'll be back on-line this evening if needed.