-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root Practically Impossible to brick
- Thread starter andrizoid
- Start date
-
- Tags
- htc droid eris
Joe Eris
Android Enthusiast
I'm pretty sure that if you took your phone for a little swim with you, you would successfully brick itAndrizoid, here is a 100% sure way to brick the Eris:
(1) Start flashing (any) ROM.
(2) Pull the battery.
(3) Take a deep breath.
(4) Put it down on the pavement.
(5) Step on it.
(6) Drive over it.
(6) Sweep up the debris to clean up after yourself.
funkyfender
Well-Known Member
Guys, I just tried some of these and now my phone won't boot. I get stuck at the bootloader with an error message. Any hope of unbricking?
Here's a pic of my phone:
http://img844.imageshack.us/img844/8251/img0184w.jpg
Here's a pic of my phone:
http://img844.imageshack.us/img844/8251/img0184w.jpg
Andrizoid,
Have a look at this thread on XDA. This is the second (or third?) person that went down this path (make sure to look at both post #1 and post #4).
Perhaps some good could come by trying to understand why that sequence bricks the phone.
Seems like the sequence to a brick in this case is to follow up a failed ROM flashing operation in Clockwork recovery with an attempt to use HBOOT with a PB00IMG.ZIP file.
A different user on XDA ("Stick" or "stick") reported the same sequence, and there have been a couple others that messed up their phones as well.
eu1
Have a look at this thread on XDA. This is the second (or third?) person that went down this path (make sure to look at both post #1 and post #4).
Perhaps some good could come by trying to understand why that sequence bricks the phone.
Seems like the sequence to a brick in this case is to follow up a failed ROM flashing operation in Clockwork recovery with an attempt to use HBOOT with a PB00IMG.ZIP file.
A different user on XDA ("Stick" or "stick") reported the same sequence, and there have been a couple others that messed up their phones as well.
eu1
ACD168
Android Expert
talespin
Newbie
Starting to panic here -- thought I might try this thread since folks sound so confident about the General Eris resilience.
I've been running Nonsensikal Black V4.4 and really liking it. But, I had issues with a couple of my apps not being readable with the black theme. I decided to flash the final release version in vanilla. I did a Titanium backup as well as a nandroid backup with clockwork recovery. After wiping everything -- and I mean everything -- and beginning to flash the rom, I got a message that the install was aborted because the file was bad. Tried again. Then, stupidly, when I now realize I probably should have just flashed the older version until I could sort it out, I tried to reboot. Now the phone is stuck on the skating androids screen and completely unresponsive to power off, reboot, anything so...well, now what? Can I get back somehow to the older rom? I can't figure out how to get back to the point where I can restore anything.
I'm probably unhealthily addicted to my phone and I think I'll end up bricking myself if I can't sort it out.
Update: found some old threads and succeeded in getting into Android system recovery; now stuck there because the phone doesn't respond to volume up/down or trackball. So, any help on that?
I've been running Nonsensikal Black V4.4 and really liking it. But, I had issues with a couple of my apps not being readable with the black theme. I decided to flash the final release version in vanilla. I did a Titanium backup as well as a nandroid backup with clockwork recovery. After wiping everything -- and I mean everything -- and beginning to flash the rom, I got a message that the install was aborted because the file was bad. Tried again. Then, stupidly, when I now realize I probably should have just flashed the older version until I could sort it out, I tried to reboot. Now the phone is stuck on the skating androids screen and completely unresponsive to power off, reboot, anything so...well, now what? Can I get back somehow to the older rom? I can't figure out how to get back to the point where I can restore anything.
I'm probably unhealthily addicted to my phone and I think I'll end up bricking myself if I can't sort it out.
Update: found some old threads and succeeded in getting into Android system recovery; now stuck there because the phone doesn't respond to volume up/down or trackball. So, any help on that?
talespin,
What exactly do you mean by "Android system recovery" ? That sounds suspiciously like a stock recovery boot - and I can't imagine how that would have gotten on the phone, unless you flashed one of the "Flashback" ROMs (or ran a RUU Utility, or applied a PB00IMG.ZIP file with HBOOT).
Are you sure you don't mean Amon_RA ?
I would stop messing with your phone until you get some expert advice.
If you want the best advice possible, you should fully describe the current state of the phone, and also what your capabilities are:
- What bootloader version is on the phone?
- Do you know how to get the phone into each of the following modes: HBOOT, FASTBOOT, Recovery?
- Have you ever used either "adb" or "fastboot" from the PC successfully?
- What is the last software you installed successfully, and was this before or after all your "wipes"?
- What method did you use to originally root the phone?
- Do you know where to find the latest RUU and/or any of the HTC PB00IMG.ZIP files?
- Are you making sure to keep your phone well charged during this crisis?
What exactly do you mean by "Android system recovery" ? That sounds suspiciously like a stock recovery boot - and I can't imagine how that would have gotten on the phone, unless you flashed one of the "Flashback" ROMs (or ran a RUU Utility, or applied a PB00IMG.ZIP file with HBOOT).
Are you sure you don't mean Amon_RA ?
I would stop messing with your phone until you get some expert advice.
If you want the best advice possible, you should fully describe the current state of the phone, and also what your capabilities are:
- What bootloader version is on the phone?
- Do you know how to get the phone into each of the following modes: HBOOT, FASTBOOT, Recovery?
- Have you ever used either "adb" or "fastboot" from the PC successfully?
- What is the last software you installed successfully, and was this before or after all your "wipes"?
- What method did you use to originally root the phone?
- Do you know where to find the latest RUU and/or any of the HTC PB00IMG.ZIP files?
- Are you making sure to keep your phone well charged during this crisis?
talespin
Newbie
talespin,
What exactly do you mean by "Android system recovery" ? That sounds suspiciously like a stock recovery boot - and I can't imagine how that would have gotten on the phone, unless you flashed one of the "Flashback" ROMs.
Are you sure you don't mean Amon_RA ?
I would stop messing with your phone until you get some expert advice.
What bootloader version is on the phone?[/QUOTE]
Yes, for whatever reason, I'm looking at the following screen (with the only differences being RA-eris-v1.6.2).
I haven't flashed anything at all.
And, expert advice is why I'm checking the forum.
What exactly do you mean by "Android system recovery" ? That sounds suspiciously like a stock recovery boot - and I can't imagine how that would have gotten on the phone, unless you flashed one of the "Flashback" ROMs.
Are you sure you don't mean Amon_RA ?
I would stop messing with your phone until you get some expert advice.
What bootloader version is on the phone?[/QUOTE]
Yes, for whatever reason, I'm looking at the following screen (with the only differences being RA-eris-v1.6.2).
I haven't flashed anything at all.
And, expert advice is why I'm checking the forum.
Just wanted to point-out that talespin mentioned "clockwork recovery"...not sure how relevant this is at this point, eu1, since I know you've recently done some research and testing with ClockworkMod Recovery to familiarize yourself with it.
Cheers!
Cheers!
OK, that's good (phew!)
(Note I added a bunch of questions to my post just above - you might consider answering them, as every bit of information that you can provide is useful).
As far as the trackball goes, was it working under clockwork?
The first and most important thing you can do is get your phone fully charged, and then we can proceed from there.
Here is something important though to note: because ROM Manager/Clockwork stores it's "nandroid" backups in a different location from where Amon_RA stores its' "nandroid" backups, you will not be able to immediately restore your "nandroid" backup using Amon_RA.
I'll add a little bit in a couple of minutes - have a look at my questions and answer what you are able to.
eu1
talespin
Newbie
Yes, I do know how to get the phone into HBOOT, FASTBOOT and Recovery.
I'm not at all familiar with "adb" or "fastboot" from the PC.
The last software I installed was the pro version of Titanium Backup and paid upgrade to ROM Manager. Everything installed before the "wipes"
I rooted the phone using your Universal Eris Root for Dummies (thanks).
As for the latest RUU and/or any of the HTC PB00IMG.ZIP files -- not a clue. And if they're on the phone itself, no idea how I would get to them.
Oh, and yes, I've been keeping it charged.
I'm not at all familiar with "adb" or "fastboot" from the PC.
The last software I installed was the pro version of Titanium Backup and paid upgrade to ROM Manager. Everything installed before the "wipes"
I rooted the phone using your Universal Eris Root for Dummies (thanks).
As for the latest RUU and/or any of the HTC PB00IMG.ZIP files -- not a clue. And if they're on the phone itself, no idea how I would get to them.
Oh, and yes, I've been keeping it charged.
OK, good.
The one rub in the ointment that we will have is that ROM Manager/Clockwork Mod stores it's Nandroid backups in a different location than Amon_RA, so, with Amon_RA running, you won't be able to get the nandroid backup restored (right now) - we'll need to take some intermediate step.
Here's the thing about the trackball, though. The current versions of ROM Manager/Clockwork play a little trick where Amon_RA is first booted, and then the ClockworkMod recovery shows up a little bit after that. You might remember that the text on the screen changes color a little (from the green you are seeing now to a more lavender colored menu). This explains why you get a different "recovery menu" when you cold-boot the phone into recovery versus warm-booting it from within ROM Manager.
That also makes it very, very curious that you can't use the trackball - because in the newer version(s) of ROM Manager/ClockworkMod, you are literally using the identical kernel that Amon_RA uses.
So, more questions about the trackball - have you had any problems with it in the past that you can remember?
BTW, Vol-Up and Vol-Down won't do anything in the toplevel Amon_RA menu - so you can breath easy about that.
What I would recommend you try is to shut the phone down (power off - you can pull the battery), and get into recovery first by going to HBOOT and then using the HBOOT menu to get to the recovery. While you are in HBOOT mode, though, please make a note of the HBOOT version number, and report it here.
When you get back into Amon_RA, see if you the trackball scrolling works. (BTW, if you have the USB cable plugged in while doing this, if the trackball scroll doesn't work, gently move the USB connector around a little to see if that changes the trackball behavior)
talespin,
BTW do you have a Media card slot or some other way to transfer files onto the SD card from the PC if we can't get the trackball to function under Amon_RA?
PS - Just to re-assure you - there is no doubt we will get your phone running again. At this point, though, it is only a question of how to provide instructions that are the easiest for you. If we can get the trackball to work, that will be the easiest approach (that doesn't require you to learn a whole bunch of new things)
BTW do you have a Media card slot or some other way to transfer files onto the SD card from the PC if we can't get the trackball to function under Amon_RA?
PS - Just to re-assure you - there is no doubt we will get your phone running again. At this point, though, it is only a question of how to provide instructions that are the easiest for you. If we can get the trackball to work, that will be the easiest approach (that doesn't require you to learn a whole bunch of new things)
talespin
Newbie
I've actually powered down by pulling the battery a couple of times now (the only way it can be done with no response from the trackball.) As to the trackball, I've never encountered any problems with it in the past beyond being a bit fiddly the way any such tiny trackball will be.
I'm fixed for card readers and the like, no difficulty there.
I've got it in HBOOT at present and the version number is 1.47.0000.
Another note, it's never gotten beyond the "green text" version of the recovery menu . . . just frozen there at the initial screen.
Have I covered everything so far?
I'm fixed for card readers and the like, no difficulty there.
I've got it in HBOOT at present and the version number is 1.47.0000.
Another note, it's never gotten beyond the "green text" version of the recovery menu . . . just frozen there at the initial screen.
Have I covered everything so far?
talespin,
I have some incredibly important stuff that I need to handle, and won't be back here until at least 3-4 pm EST.
If you absolutely, positively must have your phone back immediately, then what I would suggest you do is run the "Official 2.1 RUU" from your Windows PC.
You can get it from this thread on XDA - it is the RUU utility named
RUU_Desire_C_Verizon_WWE_2.36.605.1_release_signed _with_driver.exe
(check the name carefully - there are a couple different RUUs mentioned on that page).
This is a utility that your run on your PC to flash the phone back to a Stock HTC 2.1 phone, which can then be re-rooted. Scary Alien has a method (documented in several of his posts) which allows you to repeat the "Dummies" method, but using a small variation which will replace the Amon_RA recovery with his variation that does not need the trackball.
If you don't mind being without use of your phone for the better part of the day, you can avoid re-rooting (depending on the outcome of your trackball experiments).
scary alien, if you want to jump in the breach I don't mind.
eu1
I have some incredibly important stuff that I need to handle, and won't be back here until at least 3-4 pm EST.
If you absolutely, positively must have your phone back immediately, then what I would suggest you do is run the "Official 2.1 RUU" from your Windows PC.
You can get it from this thread on XDA - it is the RUU utility named
RUU_Desire_C_Verizon_WWE_2.36.605.1_release_signed _with_driver.exe
(check the name carefully - there are a couple different RUUs mentioned on that page).
This is a utility that your run on your PC to flash the phone back to a Stock HTC 2.1 phone, which can then be re-rooted. Scary Alien has a method (documented in several of his posts) which allows you to repeat the "Dummies" method, but using a small variation which will replace the Amon_RA recovery with his variation that does not need the trackball.
If you don't mind being without use of your phone for the better part of the day, you can avoid re-rooting (depending on the outcome of your trackball experiments).
scary alien, if you want to jump in the breach I don't mind.
eu1
Yes, that's all good.
Because you have the 1.47.0000 HBOOT, it might be worthwhile to flash the phone using the "ROOT" PB00IMG.ZIP file, rather than using the "Official 2.1 RUU utility" - that would provide you with some flexibility (and some disaster recovery) in the future. That is also mentioned in the "Consolidated HTC ROMs" thread (with a download link). It is applied to the phone using the method documented here with pictures. It can be re-rooted using the "Dummies method" also.
Do you have any "known good" ROM files on the root of your SD card? (ROMs files that you know to be good because you've used them previously?)
Gotta go... late!
Sorry, just got back from lunch...
Glad you found it.By the way, after you've done the Official RUU or the base root ROM eu1 mentioned and if you are going to use the http://androidforums.com/eris-all-t...2-custom-recovery-trackball-not-required.html thread while re-rooting with eu1's "univerals root for dummies" thread to get the "friendlier" version of Amon_RA's recovery, you'll want the "SCENARIO 1" installation section in my thread (all you are doing in this section is replacing the Amon_RA recovery that comes with eu1's "root for dummies" gscript.zip with this alternate one).
Good luck!
talespin
Newbie
Because you have the 1.47.0000 HBOOT, it might be worthwhile to flash the phone using the "ROOT" PB00IMG.ZIP file, rather than using the "Official 2.1 RUU utility"
This, then, is the problem...I don't seem to have it (PB00IMG.ZIP). Not sure how it dematerialized but it seems clear I need to replace it -- EU1 mentioned a thread, but there are no download links. Any thoughts?
(Wow. Thank the gods this is a snow day!)
This, then, is the problem...I don't seem to have it (PB00IMG.ZIP). Not sure how it dematerialized but it seems clear I need to replace it -- EU1 mentioned a thread, but there are no download links. Any thoughts?
(Wow. Thank the gods this is a snow day!)
Okay, here are two dowload locations for the base root ROM:
Multiupload.com - upload your files to multiple file hosting sites! - PB00IMG.zip - MD5 sum: 63eacc5ede3b179f95dc22d8ef585f94
The second download location: http://android.grdlock.net/index.php?&direction=0&order=&directory=HTC%20Droid%20Eris/PB00IMG%20Roms (you'll want: the PB00IMG-root.zip; it lists the same checksum as the above multiupload location: MD5: 63eacc5ede3b179f95dc22d8ef585f94 -- I pasted this second one from Grdlock's site for double-checking and it appears to be the same to my eyes). Edit: if you download from this site, you'll want to rename it to simply "PB00IMG.zip" before using the instruction thread eu1 supplied.
I believe the size of the file (in bytes) is: 107,427,740
Good luck!
talespin
Newbie
I followed the instructions for flashing PB00IMG.ZIP file -- I got to this final screen and the only option is to reboot: Yes
There is no "No" option so I can't toggle into Fastboot.
I'm on my second try because the first time, I went ahead and hit "yes" which got me back to the stock. No problem, I figured, I'll re-root. That didn't work; I went from step 1 up to figure 18 and there were no part s 1 and 2 root files. I guessed they must already be on there somewhere since I had rooted before and proceeded to the next step . . . no go.
So, went back and started over flashing PB00IMG.ZIP file. Here I am again with no "no" option. What am I missing?
There is no "No" option so I can't toggle into Fastboot.
I'm on my second try because the first time, I went ahead and hit "yes" which got me back to the stock. No problem, I figured, I'll re-root. That didn't work; I went from step 1 up to figure 18 and there were no part s 1 and 2 root files. I guessed they must already be on there somewhere since I had rooted before and proceeded to the next step . . . no go.
So, went back and started over flashing PB00IMG.ZIP file. Here I am again with no "no" option. What am I missing?