Go Back   Android Forums > Android Phones > HTC Droid Eris > Eris - All Things Root
Eris - All Things Root Rooting, ROMS, Overclocking, etc.

test: Reply
 
LinkBack Thread Tools
Old May 8th, 2010, 04:58 AM   #1 (permalink)
Senior Member
Thread Author (OP)
 
Join Date: Nov 2009
Posts: 1,644
 
Device(s):
Carrier: Not Provided

Thanks: 50
Thanked 758 Times in 377 Posts
Default Visual Example: The PB00IMG.ZIP update method

My purpose behind this "a picture is worth 1000 words" thread is twofold:

1) For newbs that experience some trouble(s) getting the inital stages of "getting root" to happen correctly, it is helpful for them to know what things should look like when everything goes the way it should. That makes it much easier to recognize it when something goes wrong.

2) Make it very clear when to do the "battery pull" if you are interested in only installing the S-OFF bootloader (and nothing else) using Toastcfh's "battery pull trick".

In the first image below, the Eris has been restarted by simultaneously pressing the Vol-down and End (power) buttons, and a PB00IMG.ZIP file has been placed in the root folder of the SD card:



If the "PB00IMG.ZIP" file was not found on the SD card, the list of files shown above would flash across the screen and disappear very quickly - less than one second. If this is what you experience, there are a couple of possible reasons why this might have occurred:
  1. There is no file named PB00IMG.ZIP in the root folder of the SD card
  2. You put the file there, but misspelled the name
  3. The SD Card needs to be re-formatted **
  4. The SD card is "questionable" - replace with a "beter" card **

** I never experienced these problems with the Verizon-supplied SD card, but other folks have reported that this solved a problem where they were sure the file was present in the root folder, but apparently was not recognized.

The important thing to point out here is that the PB00IMG.ZIP files are large - as much as 100 MB. Merely reading the file to compute a checksum or crypto signature from a flash device takes many tens of seconds: if the file is found by the phone, it will spend some time chewing on it. If you see the above list of files (in green) flash by and nothing happens, then it is absolutely clear that the phone did not "find" the file - for whatever reason.

In the image above, we see that the phone is reading the file, as indicated by the blue progress bar in the upper right-hand corner of the screen. This process takes a fair amount of time - perhaps as much as a full minute.

Note that the HTC crypto signature is over the whole zip file (excluding the first 256 bytes); at this point, the phone is simply checking that the .zip file has the correct crypto signature - it is not even unpacking the zip file (yet)

In the next image, the phone is beginning to unpack the zip file into separate components: the crypto sig check has succeeded, and the phone says nothing exceptional, other than "Checking"




In the next image below, the phone presents a list of images that are in the PB00IMG.ZIP file. The list shown only tells you what the function of the image file is, but does not display the exact file name in the .zip file. (Unpack the PB00IMG.ZIP yourself on your PC if you are curious).

The phone also asks you if you "Do you want to start update?".

NOTE: This point in time is extremely critical if you are going to do the battery pull method!

Note that the second item in the list, (#2) is listed as "BOOTLOADER". What will happen if you choose to perform the update, is that the new bootloader from the PB00IMG.ZIP file will be flashed right away. This sort of makes sense: it is the new bootloader that is responsible for installing all the other new images in the PB00IMG.ZIP file.

The bootloader is quite small - about 512k bytes - so it flashes onto the phone very quickly. As soon as this finishes (less than one second after you start the update), the phone screen will go dark, indicating that a reboot is in progress.

IF YOU INTEND TO USE THE BATTERY PULL METHOD, YOU NEED TO BE PREPARED FOR THIS MOMENT, WITH THE COVER ALREADY OFF THE PHONE - YOU'LL HAVE 3-4 SECONDS BEFORE THE PHONE REBOOTS AND BEGINS TO CONTINUE WITH THE REST OF THE ROM FLASHING. YOU CAN PULL THE BATTERY AS SOON AS YOU SEE THE SCREEN GO DARK. (The remaining steps shown below will not occur if you pull the battery.)

Toastcfh on XDA was the first to suggest this method; it is especially useful if you want to create a backup of your "factory" 1.5 system.




The photo images used for this documentation were taken from a manual upgrade of 1.16.605.1 to 1.17.605.1 (MR1 to MR2 update on Cupcake). Both of those updates use the exact same (S-ON) bootloader, so in the pictures which follow, we won't notice a difference in version numbers or appearance of "S-OFF" at the top of the screen. But if we were doing the "root" PB00IMG.ZIP upgrade, we would see the new version number and also "S-OFF", as the new bootloader would be "live" at this point.

In the image below, (following the reboot) we see what appears to be a complete repeat of what we saw at the beginning of the process: it appears as if the .zip file is being unpacked all over again, complete with the blue progress bar showing in the upper right hand corner of the screen:




Again, we see the "Checking" message (below). But rest assured, the update process has been launched, and will continue without prompting until the end. Don't let the fact that you are seeing a repeat of these same screens you saw earlier throw you - that is normal. And again, since the file involved is large - 100 MB - it takes a little while for the phone to chug through these steps.




Now the updater lists the (functional) contents of the PB00IMG.ZIP file, and starts the update process without stopping to ask permission. Note that the bootloader is no longer mentioned (in item #2, or anywhere): it was already installed!




When the flash memory is being written, the progress bar in the upper right hand corner of the screen will display in red (as shown below)




If the updater is merely unpacking an image file (within the .zip file), the progress bar will show up in a black color as shown below. (This will be most apparent for large images such as the "system" image)




When the update is complete, the system will pause and ask you if you want to reboot. (In the case of the root PBOOIMG.ZIP update, the new S-OFF bootloader is up and running at this point, so if you wanted to toggle it in to fastboot mode and flash Amon_RA's recovery image, you could do that.



That's what it should look like! Hope this is useful to someone.

eu1

Advertisements
erisuser1 is offline  
Reply With Quote
The Following 4 Users Say Thank You to erisuser1 For This Useful Post:
afaivre (January 11th, 2011), JrzDroid (June 3rd, 2010), rdjr82 (February 6th, 2011), zloetakoe (November 14th, 2011)
sponsored links
Old May 8th, 2010, 06:18 AM   #2 (permalink)
Senior Member
 
LexusBrian400's Avatar
 
Join Date: Mar 2010
Location: I'm a drifter.. here and there.
Posts: 699
 
Device(s): Droid X w/Root & OC -HTC Droid Eris (EOL)
Carrier: Not Provided

Thanks: 73
Thanked 154 Times in 79 Posts
Default

This could really help new people wanting to root. Immediate vote for Sticky.
LexusBrian400 is offline  
Reply With Quote
Old May 8th, 2010, 09:59 AM   #3 (permalink)
Senior Member
 
jreed2560's Avatar
 
Join Date: Dec 2009
Location: Tennessee
Gender: Male
Posts: 3,922
 
Device(s): (NONE) LG G2 HTC DNA Droid RAZR HTC Rezound HTC Thunderbolt Droid X Droid Eris
Carrier: Verizon Wireless

Thanks: 561
Thanked 451 Times in 305 Posts
jreed2560@gmail.com
Default

+1 or atleast incorporated with the other rooting stickies with full credit to you.
jreed2560 is offline  
Reply With Quote
Old May 27th, 2010, 10:56 AM   #4 (permalink)
New Member
 
Join Date: May 2010
Posts: 13
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 1 Time in 1 Post
Default

I started trying this, but got cold feet when bootloader was listed as 6 instead of 2.

My list:
[1] USERDATA
[2] SYSTEM
[3] RECOVERY
[4] RADIO_VZ
[5] BOOT
[6] BOOTLOADER

I'm running 2.1 OTA and saw a couple of threads saying that 2.1 could be rooted using the 1.5 instructions. I thought the battery pull method might also be an option to backup the phone before going through the full root process.

Anyone know if the battery pull method works with 2.1 OTA?

ETA: I got brave (or stupid) and tried it. The bootloader loads first and then it immediately reboots. It seems like this works for 2.1 OTA as well. I'll finish the process after lunch.
cloudedice is offline  
Last edited by cloudedice; May 27th, 2010 at 11:13 AM.
Reply With Quote
The Following User Says Thank You to cloudedice For This Useful Post:
Old May 27th, 2010, 11:39 AM   #5 (permalink)
Member
 
Rossco_Pee's Avatar
 
Join Date: Dec 2009
Location: Iowa
Posts: 270
 
Device(s):
Carrier: Not Provided

Thanks: 46
Thanked 12 Times in 12 Posts
Default

Very nice write-up sir.
__________________
If you are lonely when you're alone, you are in bad company.

-Sartre
Rossco_Pee is offline  
Reply With Quote
Old May 27th, 2010, 12:19 PM   #6 (permalink)
New Member
 
Join Date: May 2010
Posts: 13
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 1 Time in 1 Post
Default

I was able to use the battery pull method to successfully back up my eris. After pulling the battery I skipped the rest of these instructions and just followed the original from Toastcfh.

One thing to note on my 2.1 OTA run through, using the phone to run the backup did not work. Instead I had to execute nandroid-mobile.sh -b from the adb shell. BART didn't work from phone or adb shell.
cloudedice is offline  
Reply With Quote
Old May 27th, 2010, 01:20 PM   #7 (permalink)
Senior Member
Thread Author (OP)
 
Join Date: Nov 2009
Posts: 1,644
 
Device(s):
Carrier: Not Provided

Thanks: 50
Thanked 758 Times in 377 Posts
Default

Quote:
Originally Posted by cloudedice View Post
I started trying this, but got cold feet when bootloader was listed as 6 instead of 2.

My list:
[1] USERDATA
[2] SYSTEM
[3] RECOVERY
[4] RADIO_VZ
[5] BOOT
[6] BOOTLOADER

I'm running 2.1 OTA and saw a couple of threads saying that 2.1 could be rooted using the 1.5 instructions. I thought the battery pull method might also be an option to backup the phone before going through the full root process.

Anyone know if the battery pull method works with 2.1 OTA?

ETA: I got brave (or stupid) and tried it. The bootloader loads first and then it immediately reboots. It seems like this works for 2.1 OTA as well. I'll finish the process after lunch.
The photographs in the original post were taken on a phone that was undergoing an upgrade from OTA-1.5(1) (the December '09 1.5 update) to MR2. You are correct that the order of the listing appears different going from a 1.17.605.1 phone to the root-ROM, but that is an innocuous difference... as you found out.

I've been through this process multiple times on my phone, where I restored completely back to 1.5, re-burning everything including the bootloader (& radio images), and then rolled forward again to a rooted phone - it works in exactly the same sequence. Just be sure to wait until the screen goes dark before you pull the battery. I have never waited much more than 3 or 4 seconds, so I wouldn't encourage people to wait very long after the screen goes dark, although there is no reason to panic over whether you do it in 2 seconds or 5 seconds.

Note that doing the battery pull trick only changes the bootloader. It does not touch the Radio image, so, a stock 1.5 phone which has been upgraded to a 2.1 (non-HTC) ROM via the battery pull hack will be slightly different than a OTA-2.1 phone which is rooted.

If these details are important to you, check this XDA thread to see how the different paths to 2.1 - rooted ROMs might vary in regard to Radio (& NVRAM!) images. Since you started with an OTA-2.1 phone, you should already have the latest radio image.



I'll throw in one more variation, just for giggles, as if things were not complicated enough already: you can actually do a Nandroid backup without ever installing Amon_RA on the phone so long as you have the S-OFF bootloader in place:


Just boot into fastboot mode on the phone (after you have installed the S-OFF bootloader), and then (from the PC) do a

fastboot boot recovery-RA-eris-v1.6.2.img

( md5sum: e3932991f097993602af3c7a4b61a4f8 recovery-RA-eris-v1.6.2.img
this only works when you have an S-OFF bootloader )

Note that doing this allows you root access to the phone via adb to the Amon RA recovery boot, even though the Amon_RA recovery has not been flashed to the recovery partition.

I'm not sure how useful that really turns out to be, but the ultra-paranoid could conceivably even make a back up their old recovery partition by using the "dump_image" command.

eu1
erisuser1 is offline  
Last edited by erisuser1; May 27th, 2010 at 01:23 PM.
Reply With Quote
Old May 27th, 2010, 01:33 PM   #8 (permalink)
Senior Member
Thread Author (OP)
 
Join Date: Nov 2009
Posts: 1,644
 
Device(s):
Carrier: Not Provided

Thanks: 50
Thanked 758 Times in 377 Posts
Default

Quote:
Originally Posted by cloudedice View Post
I was able to use the battery pull method to successfully back up my eris. After pulling the battery I skipped the rest of these instructions and just followed the original from Toastcfh.

One thing to note on my 2.1 OTA run through, using the phone to run the backup did not work. Instead I had to execute nandroid-mobile.sh -b from the adb shell. BART didn't work from phone or adb shell.
I've only used the Nandroid backup, so I don't know exactly what to expect from BART But to be cautious, boot the phone into (Amon_RA) recovery, and then log in to the phone via adb and do a

# more /cache/recovery/log

to see if you see any strange errors. If you see something that gives you some indigestion, post it up here an I'll have a look at it.


eu1
erisuser1 is offline  
Reply With Quote
Old May 27th, 2010, 01:40 PM   #9 (permalink)
New Member
 
Join Date: May 2010
Posts: 13
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 1 Time in 1 Post
Default

Quote:
Originally Posted by erisuser1 View Post
I've only used the Nandroid backup, so I don't know exactly what to expect from BART But to be cautious, boot the phone into (Amon_RA) recovery, and then log in to the phone via adb and do a

# more /cache/recovery/log

to see if you see any strange errors. If you see something that gives you some indigestion, post it up here an I'll have a look at it.


eu1
I'll take a look later. Now that I've got my phone rooted and Ivan's 1.0 ROM installed I'm going to play around with it for a while and try to get wireless tethering working.
cloudedice is offline  
Reply With Quote
Old May 27th, 2010, 03:01 PM   #10 (permalink)
Senior Member
Thread Author (OP)
 
Join Date: Nov 2009
Posts: 1,644
 
Device(s):
Carrier: Not Provided

Thanks: 50
Thanked 758 Times in 377 Posts
Default

Quote:
Originally Posted by cloudedice View Post
I'll take a look later. Now that I've got my phone rooted and Ivan's 1.0 ROM installed I'm going to play around with it for a while and try to get wireless tethering working.
I used the 2.0.1-pre1 (CM-5.0.6 ds - quckfix) version from
Downloads - android-wifi-tether - Project Hosting on Google Code
( wireless_tether_2_0-pre10.apk )
on the same ROM, no problems.

Some of the later revs probably work too - for as little as I have used it, I didn't experience any trouble, so I haven't updated it (yet).

Good luck
erisuser1 is offline  
Reply With Quote
sponsored links
Old May 28th, 2010, 09:03 AM   #11 (permalink)
New Member
 
Join Date: May 2010
Posts: 13
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 1 Time in 1 Post
Default

Quote:
Originally Posted by erisuser1 View Post
I used the 2.0.1-pre1 (CM-5.0.6 ds - quckfix) version from
Downloads - android-wifi-tether - Project Hosting on Google Code
( wireless_tether_2_0-pre10.apk )
on the same ROM, no problems.

Some of the later revs probably work too - for as little as I have used it, I didn't experience any trouble, so I haven't updated it (yet).

Good luck
The problem was in my understanding of how the functionality works. I expected to be able to see a wireless hotspot running in infrastructure mode, but it appears as an ad-hoc wireless network. The devices I was using to test during the day only supported infrastructure mode. After checking my laptop at home, I was able to connect and surf the web. Thanks for your help!

Also, wireless-tether 2.0.1 stable is available from the Android Market. 2.0.2-pre9 or something is available through the link you provided, but it's not stable enough for me to run. It does have some nice additions including a battery temp indicator.
cloudedice is offline  
Reply With Quote
Old May 28th, 2010, 12:54 PM   #12 (permalink)
New Member
 
Join Date: May 2010
Posts: 13
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 1 Time in 1 Post
Default

Here's the portion of log when running bart.

Code:
Create BART backup?
Press Trackball to confirm,
any other key to abort.

Performing backup : .mount: mounting /dev/block/mmcblk0p2 on /system/sd failed:
No such file or directory
Unable to mount /system/sd ...



Error : Run 'bart' via adb!
For completeness, here's the nanroid+ext which also failed:
Code:
Create Nandroid + ext backup?
Press Trackball to confirm,
any other key to abort.

Performing backup : .
nandroid-mobile v2.2.1

Using G1 keyboard, enter a prefix substring and then <CR>
or just <CR> to accept default: Accepting default.

Using - prefix to create a backup folder

mounting system and data read-only, sdcard read-write
.............checking free space on sdcard
..Dumping boot to /sdcard/nandroid/HT9C1HG14265/BDES-20100528-1751/boot.img.....
done
Dump of the recovery partition suppressed.
Dump of the misc partition suppressed.
Dumping system to /sdcard/nandroid/HT9C1HG14265/BDES-20100528-1751/system.img...
...........................................done
Dumping data to /sdcard/nandroid/HT9C1HG14265/BDES-20100528-1751/data.img.......
............done
Dump of the cache partition suppressed.
Storing the ext2(Apps, Dalvik-cache) contents in the backup folder.
Warning: --ext2 specified but unable to mount the ext2 partition.


Error : Run 'nandroid-mobile.sh' via adb!
Standard nandroid backup works without issue, as does running nandroid-mobile.sh from the adb shell
cloudedice is offline  
Reply With Quote
Old May 28th, 2010, 02:14 PM   #13 (permalink)
Senior Member
Thread Author (OP)
 
Join Date: Nov 2009
Posts: 1,644
 
Device(s):
Carrier: Not Provided

Thanks: 50
Thanked 758 Times in 377 Posts
Default

Quote:
Originally Posted by cloudedice View Post
Here's the portion of log when running bart...

snip!
cloudedice,


Both of those errors appear to be because of a lack of an ext[2|3] partition on your SD card.

That's OK, though - just don't do a backup/restore that expects one to be there! For Nandroid, just the regular backup/restore.

Note that everything else in the Nandroid backup succeeded - (boot.img, system.img, and data.img). If you don't have an ext partition on your SD card, then you are not using apps2sd (even if the ROM supports it), and the "ext" functionality isn't needed.

I haven't used BART, so I don't know if it always wants an ext[2|3] partition or not, but the error that is being is certainly because there isn't one present.

eu1
erisuser1 is offline  
Reply With Quote
Old May 29th, 2010, 10:27 AM   #14 (permalink)
Senior Member
 
thenestor's Avatar
 
Join Date: Dec 2009
Location: Orange, California
Gender: Male
Posts: 1,038
 
Device(s): HTC Droid Incredible 4G LTE
Carrier: Not Provided

Thanks: 213
Thanked 318 Times in 159 Posts
Default

This guide was very helpful. Thank you for doing this.
thenestor is offline  
Reply With Quote
Old June 3rd, 2010, 12:54 PM   #15 (permalink)
Senior Member
 
thenestor's Avatar
 
Join Date: Dec 2009
Location: Orange, California
Gender: Male
Posts: 1,038
 
Device(s): HTC Droid Incredible 4G LTE
Carrier: Not Provided

Thanks: 213
Thanked 318 Times in 159 Posts
Default

I'm not in a position to do this right now, but I was thinking it would be helpful if someone could post screen shots of the other two parts of rooting: a) Installing Recovery and b) Flashing a ROM. And I still think this thread should be sticky, or at least mentioned in the other rooting stickies.
thenestor is offline  
Reply With Quote
Old June 3rd, 2010, 03:54 PM   #16 (permalink)
Senior Member
 
JrzDroid's Avatar
 
Join Date: Nov 2009
Location: NJ
Posts: 1,682
 
Device(s): Droid Bionic- Rooted Droid X- MIUI G1- AOSP ICS Nook-MIUI
Carrier: Not Provided

Thanks: 48
Thanked 319 Times in 169 Posts
Send a message via AIM to JrzDroid brettNJ
Default

ST!CKY STiCKY
__________________
WARNING Posts May Contain Anywhere between 30 - 100% SARCASM
PM me if you need any further help, i'm here to help
Google+ 4 Life
JrzDroid is offline  
Reply With Quote
Old June 22nd, 2010, 12:57 PM   #17 (permalink)
Senior Member
 
thenestor's Avatar
 
Join Date: Dec 2009
Location: Orange, California
Gender: Male
Posts: 1,038
 
Device(s): HTC Droid Incredible 4G LTE
Carrier: Not Provided

Thanks: 213
Thanked 318 Times in 159 Posts
Default

Seriously, this needs to be a sticky, or at least linked from the GUIDE sticky. I'll PM a mod about it.
thenestor is offline  
Reply With Quote
Old June 22nd, 2010, 06:24 PM   #18 (permalink)
Junior Member
 
Flames92's Avatar
 
Join Date: Dec 2009
Location: Under a rock ]:
Posts: 28
 
Device(s): HTC Droid Eris <3!
Carrier: Not Provided

Thanks: 7
Thanked 0 Times in 0 Posts
Default

Aww where was this like a few days ago when I needed it xD +1!!
Flames92 is offline  
Reply With Quote
Old June 22nd, 2010, 11:11 PM   #19 (permalink)
Senior Member
 
cableguynoe's Avatar
 
Join Date: Mar 2010
Location: Monterey, CA
Posts: 2,026
 
Device(s): Droid 3 Rooted Droid 2 Rooted Droid 4..broken IPHONE5
Carrier: Not Provided

Thanks: 150
Thanked 260 Times in 224 Posts
Default

Quote:
Originally Posted by Flames92 View Post
Aww where was this like a few days ago when I needed it xD +1!!
been around since early May
cableguynoe is offline  
Reply With Quote
Old August 14th, 2010, 07:13 PM   #20 (permalink)
New Member
 
Join Date: Jun 2010
Posts: 6
 
Device(s): HTC Eris
Carrier: Not Provided

Thanks: 0
Thanked 1 Time in 1 Post
Default

(Regarding post by erisuser1, Root for Dummies)
Hey thanks so much for helping me with rooting my device! (root for dummies) I found your step by step instructions awesome! Been having fun. Can you help me with the install of the XTRrom 3.03? Have heared alot of good things about this rom. What do you think?
daholein1 is offline  
Reply With Quote
sponsored links
Old August 15th, 2010, 10:23 PM   #21 (permalink)
Junior Member
 
Join Date: Aug 2010
Posts: 25
 
Device(s):
Carrier: Not Provided

Thanks: 3
Thanked 1 Time in 1 Post
Default

Right after image #2 I get an error saying "Main version is older! Update fail!"

Any idea why?
bkleinkn is offline  
Reply With Quote
Old August 15th, 2010, 11:33 PM   #22 (permalink)
Senior Member
Thread Author (OP)
 
Join Date: Nov 2009
Posts: 1,644
 
Device(s):
Carrier: Not Provided

Thanks: 50
Thanked 758 Times in 377 Posts
Default

Quote:
Originally Posted by bkleinkn View Post
Right after image #2 I get an error saying "Main version is older! Update fail!"

Any idea why?
Lots of ideas. But there would be far fewer possibilities we would need to run through if you described what you are trying to accomplish, and what state your phone is in to begin with.

For instance: if you are trying to root, there are far easier methods than using this one - look at the Sticky posts "Universal Root for Dummies" or "Universal 1 Click Eris App Apk". Also, while those methods make this method irrelevant for rooting purposes, I'll note that you will get the error message you reported if you try to do this:

Leak-V1, Leak-V2, or Leak-V3 bootloader (1.49.0000) -> Root bootloader (1.49.2000) OR
Leak-V1, Leak-V2, or Leak-V3 bootloader (1.49.0000) -> any 1.5 bootloader (1.45, 1.46, 1.47)

whereas the following two scenarios will work:

1.5 bootloaders (1.45, 1.46, 1.47) -> 1.49.0000 OR 1.49.2000
Root Bootloader (1.49.2000) -> ANY


Over the past couple of days, I have advised people that were trying to restore their phones back to factory condition that they can use these instructions if they are having difficulties using the "RUU" to reinstall back to factory - the instructions for doing so are essentially identical to those given here, except that the proper ROM to start with is the Leak-V3 ROM, rather than the root ROM.


So - what are you trying to accomplish, and what bootloader and OS is presently on your phone?


eu1
erisuser1 is offline  
Reply With Quote
Old August 16th, 2010, 06:01 PM   #23 (permalink)
Junior Member
 
Join Date: Aug 2010
Posts: 25
 
Device(s):
Carrier: Not Provided

Thanks: 3
Thanked 1 Time in 1 Post
Default

Quote:
Originally Posted by erisuser1 View Post
Lots of ideas. But there would be far fewer possibilities we would need to run through if you described what you are trying to accomplish, and what state your phone is in to begin with.

For instance: if you are trying to root, there are far easier methods than using this one - look at the Sticky posts "Universal Root for Dummies" or "Universal 1 Click Eris App Apk". Also, while those methods make this method irrelevant for rooting purposes, I'll note that you will get the error message you reported if you try to do this:

Leak-V1, Leak-V2, or Leak-V3 bootloader (1.49.0000) -> Root bootloader (1.49.2000) OR
Leak-V1, Leak-V2, or Leak-V3 bootloader (1.49.0000) -> any 1.5 bootloader (1.45, 1.46, 1.47)

whereas the following two scenarios will work:

1.5 bootloaders (1.45, 1.46, 1.47) -> 1.49.0000 OR 1.49.2000
Root Bootloader (1.49.2000) -> ANY


Over the past couple of days, I have advised people that were trying to restore their phones back to factory condition that they can use these instructions if they are having difficulties using the "RUU" to reinstall back to factory - the instructions for doing so are essentially identical to those given here, except that the proper ROM to start with is the Leak-V3 ROM, rather than the root ROM.


So - what are you trying to accomplish, and what bootloader and OS is presently on your phone?


eu1

I have the Droid Eris and I want to be able to run Cyanogensmod.

Here's what I know about the phone:

-It's still the way I got it from Verizon
bkleinkn is offline  
Reply With Quote
Old August 16th, 2010, 06:15 PM   #24 (permalink)
not really so scary
 
scary alien's Avatar
 
Join Date: Mar 2010
Location: Indy
Posts: 17,468
 
Device(s): LG Nexus 5, Samsung Galaxy Nexus, Asus Nexus 7, Moto Droid X, HTC Droid Eris
Carrier: T-Mobile

Thanks: 33,032
Thanked 15,044 Times in 7,385 Posts
Default

Quote:
Originally Posted by bkleinkn View Post
I have the Droid Eris and I want to be able to run Cyanogensmod.

Here's what I know about the phone:

-It's still the way I got it from Verizon
edit: wow, can't believe that I missed the posts earlier about "main version is older"...I didn't see those and would not have just merrily suggested options for rooting. Sorry 'bout that.

You should be good-to-go. Here's your recipe for rooting:

1) Download / acquire your ROM (your choice):

{rom} CYANOGEN ROM 6.0.O DS RC 1 test - xda-developers

- or -

{ cyanogen tazz v8 themed/unthemed/8/14/10/camera \gps fixed\CM6/Froyo Edition - xda-developers

- or -

[ROM]-[5/25/2010] CyanogenERIS v1.1 + Senseless[JIT/Overclock/Vanilla!!!] - xda-developers

2) Root using either http://androidforums.com/all-things-root-eris/127861-universal-eris-root-dummies.html (eu1's thread) or http://androidforums.com/all-things-root-eris/139178-universal-1-click-eris-app-apk-no-pcs-no-scripts-needed-easy.html (jcase's thread); either will work wonderfully.

As erisuser1 was pointing-out in his previous posts, the method you were trying to use is the old, original, "traditional" root method (that I and a lot of folks used). The ones above are pretty simple and work on any Eris phone, regardless of HBOOT version or Android version.

3) Flash your selected ROM per the instructions in your selected root method

Cheers!
scary alien is online now  
Last edited by scary alien; August 28th, 2010 at 08:26 PM.
Reply With Quote
Old August 23rd, 2010, 07:00 PM   #25 (permalink)
Senior Member
 
andrizoid's Avatar
 
Join Date: Mar 2010
Posts: 2,266
 
Device(s): Eris, White Widow 4.6 ; dErisROM 3.6
Carrier: Not Provided

Thanks: 92
Thanked 356 Times in 184 Posts
kenkyger@mail.com
Default

Quote:
Originally Posted by scary alien View Post
You should be good-to-go. Here's your recipe for rooting:

1) Download / acquire your ROM (your choice):

{rom} CYANOGEN ROM 6.0.O DS RC 1 test - xda-developers

- or -

{ cyanogen tazz v8 themed/unthemed/8/14/10/camera \gps fixed\CM6/Froyo Edition - xda-developers

- or -

[ROM]-[5/25/2010] CyanogenERIS v1.1 + Senseless[JIT/Overclock/Vanilla!!!] - xda-developers

2) Root using either http://androidforums.com/all-things-root-eris/127861-universal-eris-root-dummies.html (eu1's thread) or http://androidforums.com/all-things-root-eris/139178-universal-1-click-eris-app-apk-no-pcs-no-scripts-needed-easy.html (jcase's thread); either will work wonderfully.

As erisuser1 was pointing-out in his previous posts, the method you were trying to use is the old, original, "traditional" root method (that I and a lot of folks used). The ones above are pretty simple and work on any Eris phone, regardless of HBOOT version or Android version.

3) Flash your selected ROM per the instructions in your selected root method

Cheers!
ewwww. your recommended CyanogenEris?
__________________
Andrizoid's Space is online! Come stop in and say hi!
Check out my stuff on Rom Manager!
andrizoid is offline  
Reply With Quote
Old August 23rd, 2010, 07:44 PM   #26 (permalink)
not really so scary
 
scary alien's Avatar
 
Join Date: Mar 2010
Location: Indy
Posts: 17,468
 
Device(s): LG Nexus 5, Samsung Galaxy Nexus, Asus Nexus 7, Moto Droid X, HTC Droid Eris
Carrier: T-Mobile

Thanks: 33,032
Thanked 15,044 Times in 7,385 Posts
Default

Quote:
Originally Posted by andrizoid View Post
ewwww. your recommended CyanogenEris?
lol...I just included the links of the "Cyanogen"-referenced ROMs that I could find on XDA (that's what they were asking for)...is one of yours Cyanogen-based? (he asks, knowing that an awesome answer is forthcoming )...
scary alien is online now  
Last edited by scary alien; August 23rd, 2010 at 07:47 PM.
Reply With Quote
Old August 25th, 2010, 01:24 PM   #27 (permalink)
Senior Member
 
andrizoid's Avatar
 
Join Date: Mar 2010
Posts: 2,266
 
Device(s): Eris, White Widow 4.6 ; dErisROM 3.6
Carrier: Not Provided

Thanks: 92
Thanked 356 Times in 184 Posts
kenkyger@mail.com
Default

haha yes!
two of them are actually, suave smush and white widow.
i just thought it was odd to see cyanogen eris. i guess with the patches i released for it you could still run it OK, but its so outdated.
andrizoid is offline  
Reply With Quote
Old August 25th, 2010, 01:28 PM   #28 (permalink)
not really so scary
 
scary alien's Avatar
 
Join Date: Mar 2010
Location: Indy
Posts: 17,468
 
Device(s): LG Nexus 5, Samsung Galaxy Nexus, Asus Nexus 7, Moto Droid X, HTC Droid Eris
Carrier: T-Mobile

Thanks: 33,032
Thanked 15,044 Times in 7,385 Posts
Default

Quote:
Originally Posted by andrizoid View Post
haha yes!
two of them are actually, suave smush and white widow.
i just thought it was odd to see cyanogen eris. i guess with the patches i released for it you could still run it OK, but its so outdated.
I thought so...I remember when you released them, but couldn't remember the details.

But you were releasing ROMs left and right back then .

Did you ever hop on the Incredible track and build ROMs for that phone or any others? Just curious...
scary alien is online now  
Reply With Quote
Old August 25th, 2010, 01:32 PM   #29 (permalink)
Senior Member
 
andrizoid's Avatar
 
Join Date: Mar 2010
Posts: 2,266
 
Device(s): Eris, White Widow 4.6 ; dErisROM 3.6
Carrier: Not Provided

Thanks: 92
Thanked 356 Times in 184 Posts
kenkyger@mail.com
Default

Quote:
Originally Posted by scary alien View Post
I thought so...I remember when you released them, but couldn't remember the details.

But you were releasing ROMs left and right back then .

Did you ever hop on the Incredible track and build ROMs for that phone or any others? Just curious...
i was going to port smash over to the INC, but i forgot about the MDPI and HDPI difference

once i get my DINC i will start on those, but i gotta raise the money first. i did get donated an Eris dev phone last night though

ill be able to sell my personal phone, and then keep that one to continue to futz with over here.
andrizoid is offline  
Reply With Quote
Old August 27th, 2010, 11:17 AM   #30 (permalink)
Junior Member
 
eddieb1983's Avatar
 
Join Date: Aug 2010
Posts: 48
 
Device(s): HTC Droid Incredible
Carrier: Not Provided

Thanks: 8
Thanked 0 Times in 0 Posts
Default

HELP! When I follow the instructions to the t, my phone comes back with the following under HBOOT:

<SEND> FastBoot Mode
<VOL UP> Recovery

If I go to recovery, it goes to the amon recovery which does not help me because I can not scroll down. I am never asked to update. Please help because I need to unroot my phone to send it back to vw AGAIN because of the trackball.

I used eu1 universal root instructions and flashed xtrROM 3.0.3.
eddieb1983 is offline  
Reply With Quote
sponsored links
Old August 27th, 2010, 03:58 PM   #31 (permalink)
Senior Member
Thread Author (OP)
 
Join Date: Nov 2009
Posts: 1,644
 
Device(s):
Carrier: Not Provided

Thanks: 50
Thanked 758 Times in 377 Posts
Default

Quote:
Originally Posted by eddieb1983 View Post
HELP! When I follow the instructions to the t, my phone comes back with the following under HBOOT:

<SEND> FastBoot Mode
<VOL UP> Recovery

If I go to recovery, it goes to the amon recovery which does not help me because I can not scroll down. I am never asked to update. Please help because I need to unroot my phone to send it back to vw AGAIN because of the trackball.

I used eu1 universal root instructions and flashed xtrROM 3.0.3.
eddieb1983,

If you correctly put a PB00IMG.ZIP file in the root folder of the SD card, booting into HBOOT would have automatically started unpacking it and doing a signature check. You didn't even mention those behaviors, so I suspect you didn't put it there, or you named it incorrectly, or you got it into the wrong folder on the SD card, or you accidentally unpacked it onto the SD card, or something like that. Go back and have a look at the pictures in this thread again.

Having said that, I'm not going to answer your same inquiry in three different threads. Look for my responses in the other thread, starting from here

eu1


.
erisuser1 is offline  
Last edited by erisuser1; August 27th, 2010 at 04:00 PM.
Reply With Quote
Old August 28th, 2010, 07:33 AM   #32 (permalink)
Junior Member
 
eddieb1983's Avatar
 
Join Date: Aug 2010
Posts: 48
 
Device(s): HTC Droid Incredible
Carrier: Not Provided

Thanks: 8
Thanked 0 Times in 0 Posts
Default

Problem solved thanks to EU1. See this thread.
eddieb1983 is offline  
Reply With Quote
Old December 2nd, 2010, 06:45 PM   #33 (permalink)
j3h
Junior Member
 
Join Date: Aug 2010
Location: San Diego
Posts: 32
 
Device(s): HTC Droid Eris
Carrier: Not Provided

Thanks: 1
Thanked 0 Times in 0 Posts
Default

so if i am already rooted, can i still ise this method and the battery pull to get the s-off bootloader or is there another process i should follow?
j3h is offline  
Reply With Quote
Old December 3rd, 2010, 10:09 AM   #34 (permalink)
Senior Member
Thread Author (OP)
 
Join Date: Nov 2009
Posts: 1,644
 
Device(s):
Carrier: Not Provided

Thanks: 50
Thanked 758 Times in 377 Posts
Default

Quote:
Originally Posted by j3h View Post
so if i am already rooted, can i still ise this method and the battery pull to get the s-off bootloader or is there another process i should follow?
You can still use this method (with or without the battery trick) if your current bootloader is not 1.49.0000 S-ON ... just like "the old days".

Since you are already rooted, though, and you just want to install the engineering bootloader, you might find it easier to just flash the "erisengspl.zip" as if you were flashing a new ROM (it only installs the bootloader, so there are no wipes involved)

You can find a link to the relevant thread on XDA here.

Make sure your battery is well charged, verify file checksums, and take your time doing this - flashing the bootloader is the single most dangerous flashing operation you can perform.

eu1
erisuser1 is offline  
Reply With Quote
Old December 3rd, 2010, 11:14 AM   #35 (permalink)
Senior Member
 
Podivin's Avatar
 
Join Date: Nov 2009
Location: Jacksonville, Fl
Posts: 3,575
 
Device(s): Rooted Galaxy S4, Rooted Asus TF700, Stock HTC Droid Incredible
Carrier: Not Provided

Thanks: 535
Thanked 831 Times in 551 Posts
Default

Quote:
Originally Posted by erisuser1 View Post
Make sure your battery is well charged, verify file checksums, and take your time doing this - flashing the bootloader is the single most dangerous flashing operation you can perform.
Is there really any gain in doing this?
Podivin is offline  
Reply With Quote
Old December 3rd, 2010, 01:12 PM   #36 (permalink)
Senior Member
Thread Author (OP)
 
Join Date: Nov 2009
Posts: 1,644
 
Device(s):
Carrier: Not Provided

Thanks: 50
Thanked 758 Times in 377 Posts
Default

Quote:
Originally Posted by mhotovec View Post
Is there really any gain in doing this?
Do you mean "any gain" wrt being careful, or "any gain" wrt having a S-OFF bootloader?

As to the latter, having an S-OFF bootloader allows you to flash a recovery, boot, data, radio, or even a different bootloader image via the "fastboot" tool on the PC even if the OS or recovery on the phone is borked. (You can't flash the system image this way on the Eris because it is too large). You can also boot bootable images without writing them to flash using fastboot - this would be useful if the "bad block" problem develops in the recovery partition, and you need recover "bad blocks" using mtdtools.

For someone that rooted late (using the one-click or dummies method), there are a few catastrophe recovery scenarios which are simply not possible with a S-ON bootloader. The one that is most evident is when the recovery gets screwed up somehow (using Clockwork?) and the rooted OS develops a boot fault (e.g. boot loop) and USB debugging has not been toggled on. So, having a S-OFF bootloader has some value for some rescue scenarios when things go horribly wrong.

As for the former, well - in principle, there is no need to check a signed ROM's checksum, as it is impossible that Amon_RA will allow it to be installed if it does not pass a verification check; OTOH Clockwork has options that allow signatures to be ignored - in that case it is critically important, especially for something involving the bootloader - that the user insures he has a valid file before attempting installation. I mentioned it only because folks in this forum have repeatedly failed to notice when Amon_RA gave them an error condition - checking their downloaded files (hopefully the copy which is actually on the SD card) nips that in the bud.

Similarly, it is true that the regular OS of the phone routinely is allowed to write to flash memory even though the charge state of the battery can drop to only 7 or 8% - and the flash memory involved in those "risky writes" is the same flash memory is the physical device which also stores the bootloader, the recovery partition, et cetera. The difference is that the "regular" OS only writes to /data and /cache - which can easily be wiped with a factory reset procedure - so, even if the probability of a bad flash memory write is elevated for those kinds of "ordinary" write operations, there is a built-in reset procedure - but not for more critical things like the bootloader (or recovery and system partitions on a stock phone).

HTH

eu1
erisuser1 is offline  
Last edited by erisuser1; December 3rd, 2010 at 01:15 PM. Reason: clarification
Reply With Quote
Old December 3rd, 2010, 06:10 PM   #37 (permalink)
j3h
Junior Member
 
Join Date: Aug 2010
Location: San Diego
Posts: 32
 
Device(s): HTC Droid Eris
Carrier: Not Provided

Thanks: 1
Thanked 0 Times in 0 Posts
Default

i feel like i trust the PB00IMG.zip method to work and not brick my phone more than i do with the erisengspl.zip method because it doesnt look like it has been proven to work. i do like the thought of just being able to flash it tho. do you specifically have a preference?
j3h is offline  
Reply With Quote
Old December 3rd, 2010, 10:50 PM   #38 (permalink)
Senior Member
Thread Author (OP)
 
Join Date: Nov 2009
Posts: 1,644
 
Device(s):
Carrier: Not Provided

Thanks: 50
Thanked 758 Times in 377 Posts
Default

Quote:
Originally Posted by j3h View Post
i feel like i trust the PB00IMG.zip method to work and not brick my phone more than i do with the erisengspl.zip method because it doesnt look like it has been proven to work. i do like the thought of just being able to flash it tho. do you specifically have a preference?
I actually can not remember whether I have personally tried flashing "erisengspl.zip". In my analysis of it (my alter ego over on XDA is bftb0), I downloaded it and inspected it's contents, and everything looked quite kosher (bootloader checksum, signing integrity) and straightforward (very simple "update-script" file). Probably I didn't use it simply because I already had 1.49.2000 S-OFF on my phone.

There is no doubt that I have done the battery-pull trick many, many times - but note that in every case that I did that, the pre-existing bootloader was a 1.47.xxxx bootloader - the "root rom" (plus battery pull) hack will not work for folks with 1.49.0000 bootloaders. Also note this: on one occasion, my phone surprised me by continuing to install the rest of the ROM after the battery was re-inserted and I restarted the phone. So, moral of that story is: do a nandroid backup before you do either method - just in case.

eu1
erisuser1 is offline  
Reply With Quote
The Following User Says Thank You to erisuser1 For This Useful Post:
j3h (December 4th, 2010)
Old December 4th, 2010, 02:59 PM   #39 (permalink)
j3h
Junior Member
 
Join Date: Aug 2010
Location: San Diego
Posts: 32
 
Device(s): HTC Droid Eris
Carrier: Not Provided

Thanks: 1
Thanked 0 Times in 0 Posts
Default

ok, i did read your alter ego's story on xda and didnt know if i could really trust his information because i didnt recall seeing any of his other work or reports on that method but now i know and will go ahead with the flash method. Thank you very much!
j3h is offline  
Reply With Quote
Old December 11th, 2010, 11:20 AM   #40 (permalink)
j3h
Junior Member
 
Join Date: Aug 2010
Location: San Diego
Posts: 32
 
Device(s): HTC Droid Eris
Carrier: Not Provided

Thanks: 1
Thanked 0 Times in 0 Posts
Default

alright i finally got a chance to try flashing the bootloader. i downloaded the erisengspl.zip, checked the md5 put it on my phone, did a nand backup, flashed it, rebooted to the hboot to check it and my phone still said

DESIREC XC SHIP S-ON
HBOOT-1.47.0000

so i rebooted again and let the phone power all the way up in case that made a difference, turned it off and booted back into hboot and nothing changed. what happend? why didnt the flash take?
j3h is offline  
Reply With Quote
sponsored links
Old December 11th, 2010, 12:07 PM   #41 (permalink)
Senior Member
Thread Author (OP)
 
Join Date: Nov 2009
Posts: 1,644
 
Device(s):
Carrier: Not Provided

Thanks: 50
Thanked 758 Times in 377 Posts
Default

Quote:
Originally Posted by j3h View Post
alright i finally got a chance to try flashing the bootloader. i downloaded the erisengspl.zip, checked the md5 put it on my phone, did a nand backup, flashed it, rebooted to the hboot to check it and my phone still said

DESIREC XC SHIP S-ON
HBOOT-1.47.0000

so i rebooted again and let the phone power all the way up in case that made a difference, turned it off and booted back into hboot and nothing changed. what happend? why didnt the flash take?
Did you see a message on the screen when performing the Amon_RA flash that had an "(E)" in it?

That would indicate that an error occurred - the most likely being that the file didn't pass the verification step as a result of corruption when you transferred the file to the phone (I.couldn't tell from your post whether you checked the md5 of the file on your SD card or on the PC - the former is the preferred method.)

The other possibility is that due to the way that Amon_RA relies on the bootloader to do the flashing - is that erisengspl.zip will not work correctly with the 1.47.0000 bootloader.

If that turns out to be the case, then just use the method in this thread. Make a Nandroid backup before you begin.

eu1
erisuser1 is offline  
Reply With Quote
Old December 11th, 2010, 01:21 PM   #42 (permalink)
j3h
Junior Member
 
Join Date: Aug 2010
Location: San Diego
Posts: 32
 
Device(s): HTC Droid Eris
Carrier: Not Provided

Thanks: 1
Thanked 0 Times in 0 Posts
Default

i used adb to push the file to the phone then checked the file on the phone using astro then details and looked at the md5 that way. i did not see an (E) but then again i didnt look for one. ill try flashing it again and looking for the E and if that doesnt work ill do the battery pull.
j3h is offline  
Reply With Quote
Old December 11th, 2010, 01:32 PM   #43 (permalink)
Senior Member
Thread Author (OP)
 
Join Date: Nov 2009
Posts: 1,644
 
Device(s):
Carrier: Not Provided

Thanks: 50
Thanked 758 Times in 377 Posts
Default

Quote:
Originally Posted by j3h View Post
i used adb to push the file to the phone then checked the file on the phone using astro then details and looked at the md5 that way. i did not see an (E) but then again i didnt look for one. ill try flashing it again and looking for the E and if that doesnt work ill do the battery pull.
If the md5 was correct on the phone, then the 2nd explanation (1.47.0000 incompatibility) is probably the answer - the way that installations of radios and bootloader firmware is supposed to work is that the recovery partition stages the file somewhere (perhaps in /cache ?), and then communicates with the bootloader through nonvolatile information stored in the BCB (?), so it is supposed to be the bootloader's job to perform the actual flashing. (Normally you would see a different splash screen right after you perform a "reboot" from Amon_RA - but only very briefly, as it takes only about 1/4 second to flash the bootloader).

It could be that the dev that packaged up erisengspl.zip only tested it with 1.49.0000, and that technique doesn't work correctly with 1.47.0000. The old-fashioned rooting method will work though.

Make sure to make a nandroid backup of your current ROM, just in case the PB00IMG.zip install decides to continue the other flashes after the battery pull and replacement (as I mentioned previously, this happened to me once out of many, many iterations of the battery pull trick).

eu1
erisuser1 is offline  
Reply With Quote
Old December 11th, 2010, 01:41 PM   #44 (permalink)
Senior Member
Thread Author (OP)
 
Join Date: Nov 2009
Posts: 1,644
 
Device(s):
Carrier: Not Provided

Thanks: 50
Thanked 758 Times in 377 Posts
Default

Quote:
Originally Posted by j3h View Post
... flashed it, rebooted to the hboot to check it
Maybe I missed something - when you were in Amon_RA, after flashing you should have selected the menu item "Reboot", rather than power down (or pulling the battery). IIRC, there is a message at the bottom of the screen when Amon_RA finishes flashing anything involving a radio or bootloader that gives you explicit directions on what to do. Deviating from this sequence (for instance battery pull or shutdown, followed by a key-press startup) can interfere with the use of the BCB (boot control block).

Don't know if that's what happened, but couldn't tell exactly from the description.

Damn computers; they're so picky!
erisuser1 is offline  
Reply With Quote
Old December 11th, 2010, 01:47 PM   #45 (permalink)
j3h
Junior Member
 
Join Date: Aug 2010
Location: San Diego
Posts: 32
 
Device(s): HTC Droid Eris
Carrier: Not Provided

Thanks: 1
Thanked 0 Times in 0 Posts
Default

yes i just did it again and it said reboot holding down the vol down vol up or menu key so i held volume down clicked reboot and it did just that. when it rebooted there was that andriod and the box with the arrow that stayed on screen for a few seconds then went back into recovery and said "formating cache". then the menus popped up i powered it down went back into hboot to check the results and still nothing changed.

Update: i decided to just go ahead with the PB00IMG.zip and everything worked out perfectly. Thank you for all your help and work with the eris.
j3h is offline  
Last edited by j3h; December 11th, 2010 at 02:29 PM.
Reply With Quote
Old December 11th, 2010, 05:19 PM   #46 (permalink)
Senior Member
Thread Author (OP)
 
Join Date: Nov 2009
Posts: 1,644
 
Device(s):
Carrier: Not Provided

Thanks: 50
Thanked 758 Times in 377 Posts
Default

Quote:
Originally Posted by j3h View Post
yes i just did it again and it said reboot holding down the vol down vol up or menu key so i held volume down clicked reboot and it did just that. when it rebooted there was that andriod and the box with the arrow that stayed on screen for a few seconds then went back into recovery and said "formating cache". then the menus popped up i powered it down went back into hboot to check the results and still nothing changed.

Update: i decided to just go ahead with the PB00IMG.zip and everything worked out perfectly. Thank you for all your help and work with the eris.
Sounds like you are well on your way to becoming an Eris rooting expert.

If you ever use fastboot to flash things to the phone, be very very careful about md5 checksums and so forth - the one thing which is nice about the signing methodology used with ROMs and Amon_RA is that it makes it impossible to flash a corrupted ROM file - but when flashing with fastboot, no protection is provided for you, so you need to be damn sure you are working with correct and unmangled files.

(Under most circumstances, use of the S-OFF features of the HTC bootloader should not really need to be used, once a custom recovery is installed - but it is nice to know that it is there in case disaster strikes.)

eu1
erisuser1 is offline  
Reply With Quote
Old December 11th, 2010, 05:23 PM   #47 (permalink)
j3h
Junior Member
 
Join Date: Aug 2010
Location: San Diego
Posts: 32
 
Device(s): HTC Droid Eris
Carrier: Not Provided

Thanks: 1
Thanked 0 Times in 0 Posts
Default

yes i do realize this and am always very careful even with using a flashable zip. i only wanted to do this for that disaster that could be lurking around the corner. im looking into building roms now and thought this added security would just be a nice thing to have for peace of mind
j3h is offline  
Reply With Quote
Old January 28th, 2011, 03:31 PM   #48 (permalink)
Junior Member
 
talespin's Avatar
 
Join Date: Aug 2010
Location: Western Mass
Posts: 34
 
Device(s): Thunderbolt, rooted Eris running Nonsensikal ROM
Carrier: Not Provided

Thanks: 10
Thanked 1 Time in 1 Post
Default

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.
talespin is offline  
Reply With Quote
Old February 11th, 2011, 11:59 PM   #49 (permalink)
New Member
 
Join Date: Aug 2010
Posts: 2
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Exclamation i know

i know this is the old way to root the eris but im kinda in a spot where i need to root this way. i deleted gtalk off my eris when i was previously rooted and i reinstalled and was golden till i had problems which made me factory restore and when it restored gtalk was gone now cant use market...... nor do i have file manager to install gtalk..... the issue im having with this process though is i get to the second picture and after about 20 seconds it goes to the

FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK

page. im running the same version hboot as the pictures the only difference i have from the pictures is my Radio is RADIO-2.42.01.04.27
any help with this as soon as you can would be extremely helpful
usmcgeorgia421 is offline  
Reply With Quote
Old February 12th, 2011, 03:27 AM   #50 (permalink)
Senior Member
Thread Author (OP)
 
Join Date: Nov 2009
Posts: 1,644
 
Device(s):
Carrier: Not Provided

Thanks: 50
Thanked 758 Times in 377 Posts
Default

Quote:
Originally Posted by usmcgeorgia421 View Post
i know this is the old way to root the eris but im kinda in a spot where i need to root this way. i deleted gtalk off my eris when i was previously rooted and i reinstalled and was golden till i had problems which made me factory restore and when it restored gtalk was gone now cant use market...... nor do i have file manager to install gtalk..... the issue im having with this process though is i get to the second picture and after about 20 seconds it goes to the

FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK

page. im running the same version hboot as the pictures the only difference i have from the pictures is my Radio is RADIO-2.42.01.04.27
any help with this as soon as you can would be extremely helpful

There is probably something that I am missing from your description. Well, several things actually; but that's OK - sometimes folks that are new to this don't know exactly what details to provide or what the right questions to ask are.


If your phone is "rooted" is there some reason why you can not simply flash a ROM using the custom recovery?

Or, do you not have a custom recovery on the phone?

What method did you originally use to root the phone?

I tried to parse your description above; I read it several times. I could be going off on the wrong direction here, but here goes:

If a complete PB00IMG.ZIP file is found in the top folder of the SD card, it will stay on that first screen unpacking that file for OVER ONE MINUTE. Not twenty seconds - at least a minute. That's because those PB00IMG.ZIP files are big - all of them are approximately 100 MB.

Does that sound right - over one minute on the FIRST SCREEN?

Also, please verify: You said "same as in the picture" - explicitly, do you mean that your HBOOT version is 1.47.0000 ? (If you rooted "the old" way, that would not be the case.)


I don't recall how long it spends on the second screen. But I do remember that if you only get the "SIMLOCK" message if you cancel the install, or perhaps if the file is short/corrupted.

BTW, WHICH PB00IMG.ZIP file are you working with, and have you (at a minimum) verified that it's length is correct or checked its' MD5 checksum ? (The download links, file length, and MD5 checksums for all HTC PB00IMG.ZIP files are given in this XDA post)


Normally there are only two outcomes at this 2nd screen - you get a menu asking whether you want to continue the install, or it says "Main Version Older!" and you get a menu. I suppose the third option is that it fails the checking process and gives you a menu. In any event, if you DID NOT SEE a "Main Version is Older" message, that strongly suggests you have a corrupted or truncated (short) PB00IMG.ZIP file on your SD Card.


??
erisuser1 is offline  
Reply With Quote
Reply


Go Back   Android Forums > Android Phones > HTC Droid Eris > Eris - All Things Root
Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT -5. The time now is 09:48 PM.
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.