How To Install Engineering bootloader FOR LEAK ROOTERS
This is for people that used either of the leak root methods. The engineering bootloader is an unsecured bootloader, and is better in many ways (google it I am not explaining why). Just say its harder to brick with it.
Before attempting, please check your md5sums.
I want to thank Framework for being my punching back and helping with this. And the desire guy's who's work stuck in my head and gave me this idea (Sorry I forgot who you are!!).
Needed Files: Original Root Rom - PB00IMG.zip - 63eacc5ede3b179f95dc22d8ef585f94 Custom Misc Image - custom.img - 19de71cf42b3a7992d2660e7980c50bf Fastboot for linux - 4baca1f80fc9bb31aa75fd3fee2cc36b Amon's Recovery - 354d30c38c59b442340c8b72aa9f547e
Windows users should have fastboot in the sdk, and mac users I dont have a copy of yours. lash_image - 16559f2c27d08ff1ddfcaca05fbf10fb
Step 1:
Get follow root tutorials and get amon's recovery installed. If you want to skip installing a new rom after rooting, You can flash EngTools.zip will root your device . If you flash engtools you can skip step 2.
Step 2:
Take a nandroid backup, if you wish as this will wipe your device.
Custom.img is the misc img for your device, it contains the mainversion. I took one off a rooted phone and hex edited the version to be lower than the original root rom so it will flash.
Linking to pirated/illegal software: It's a shame I actually have to touch on this. Don't do it. It will be removed and repeat offenses will result in a ban.
For those that just rooted their hboot 1.49 s-on phones and think you are fine now, you really should follow the above instructions from jcase and get the hboot 1.49 s-off. As jcase said with 1.49 s-on it can increase your chances of bricking your phone as compared to s-off. Also if you ever have to use flashboot command to flash something like a new kernel you will get permission denied with the s-on.
Thanks to jcase for providing the instructions to do this.
For those that just rooted their hboot 1.49 s-on phones and think you are fine now, you really should follow the above instructions from jcase and get the hboot 1.49 s-off. As jcase said with 1.49 s-on it can increase your chances of bricking your phone as compared to s-off. Also if you ever have to use flashboot command to flash something like a new kernel you will get permission denied with the s-on.
Thanks to jcase for providing the instructions to do this.
I don't think it has an increased chance of bricking, its just that s-off will make it easier to fix problems that may arise.
What does this mean? I have to know before attempting.
It gets rid of the secured bootloader. So you could flash an alternate kernel or whatever if you wish. I *also* believe it allows you to use ADB in fastboot, making it easier to fix problems if your phone becomes unbootable and you can't get into recovery (and this actually happened to me before, lol).
I just went ahead and did it, since there are definitely no drawbacks to doing it. It would also allow you to downgrade to 1.5 if ever wanted to for some odd reason.
The Following User Says Thank You to Demache For This Useful Post:
Did you flash the PB00IMG file, you're not going to use adb until after you flash this file.
Yes I did, then right after it flashed I was sitting in the FASTBOOT USB page with that highlighted, and my mac says permission denied to any fastboot command.
When I boot into the bootloader and flash the pb00IMG.zip it goes through the first screen then on the second screen it says
"CID incorrect!
Update Fail!
Do you want to reboot device?
<Action> Yes"
Some other things...
PB00100 XC
HBOOT-1.41.0000 (PB0010000)
MICROP-0111
TOUCH PANEL... (not important)
RADIO02.42.00.04.12
Anyone have any ideas why I get this strange CID error?
Is there any way to flash this bootloader without re-flashing a new rom. I just flashed a rom and got it set up the way I like it. I would really hate to flash again.
Is there any way to flash this bootloader without re-flashing a new rom. I just flashed a rom and got it set up the way I like it. I would really hate to flash again.
banduraj,
I'm not advocating using this thread / method since I haven't done it myself (I rooted using the old / first root method, so my bootloader is already S-OFF), but you should be able to take a Nandroid backup of your current setup and then restore it later.
Be very careful! As erisuser1 has pointed-out in numerous posts/threads: this is the single most dangerous thing you can do to your phone; reference this post:
Sorry to bump this thread, but have a question regarding this.
For someone that's rooted, did a data/factory reset & Dalvik-cache, flashed to a new rom (in my case KaosFroyov38), do the same steps still apply? I just want to get my eris to S-OFF.
Sorry to bump this thread, but have a question regarding this.
For someone that's rooted, did a data/factory reset & Dalvik-cache, flashed to a new rom (in my case KaosFroyov38), do the same steps still apply? I just want to get my eris to S-OFF.
If you just want to get the 1.49.2000 S-OFF bootloader installed, it is probably easiest to just download the "erisengspl.zip" from this post on XDA and flash it similar to the way you would flash a ROM - the only difference here is that you are not replacing a ROM, so you would just perform the flash operation - no wiping or any other operations.
Doing things this way insures (because of the ROM-signing operation) that file corruption risks will be minimized.
The MD5 sig of "erisengspl.zip" should be df014009668389ef145fbb047b5ec56c
i just downloaded "erisengspl.zip" file and flashed it. seemed to work,and before the skateboard guys i got a quick pic of an alien jumping out of box. came back up just fine,powered off,then into fastboot and im on 1.47.0000 s-on
i rooted from the ota 2.1 using the market app,and am running nonsensikal 16.1
any ideas?
edit:The MD5 sig of "erisengspl.zip" is df014009668389ef145fbb047b5ec56c
Last edited by scotty85; January 3rd, 2011 at 08:33 PM.
i just downloaded "erisengspl.zip" file and flashed it. seemed to work,and before the skateboard guys i got a quick pic of an alien jumping out of box. came back up just fine,powered off,then into fastboot and im on 1.47.0000 s-on
i rooted from the ota 2.1 using the market app,and am running nonsensikal 16.1
any ideas?
edit:The MD5 sig of "erisengspl.zip" is df014009668389ef145fbb047b5ec56c
I have tested installation of it (erisengspl.zip) with both the 1.49.0000 and 1.47.0000 S-ON bootloaders on the phone, and it only seems to work correctly with the 1.49.0000 bootloader.
Your alternative is a multi-step process:
- Make a Nandroid backup of your current ROM
- Flash the misc.img from the (jcase) "Flash any RUU" thread (XDA)**
- Flash the Root ROM (PB00IMG.ZIP) using HBOOT
- "root" the Root ROM (One Click or Dummies), or flash Amon_RA's recovery with fastboot (since you will have the S-OFF bootloader at this point),
- restore your Nandroid backup.
That's an outline, (not a spoon feeding)... but it will work.
** make sure to read that thread far enough along to pick up the correction to Jcase's original command sequence.
eu1
The Following User Says Thank You to erisuser1 For This Useful Post:
thanks for the outline. if im understanding it correctly,ill need to do the 2nd step following jcase's directions from the computer,not simply flashing it in recovery as i did the erisengspl.zip file.
my desktop just crashed so i guess when i get that figured out ill read up on how to do that. i dont want to do too much messing with my phone using the GFs laptop
i just got this phone used,and for cheap. so ill never have to return it to stock to send it back verizon. as long as i can get to Amon_RA's recovery,ill never really need an unlocked bootloader, so i guess it can wait a few days
Last edited by scotty85; January 4th, 2011 at 08:01 AM.
thanks for the outline. if im understanding it correctly,ill need to do the 2nd step following jcase's directions from the computer,not simply flashing it in recovery as i did the erisengspl.zip file.
by desktop just crashed so i guess when i get that figured out ill read up on how to do that. i dont want to do too much messing with my phone using the GFs laptop
i just got this phone used,and for cheap. so ill never have to return it to stock to send it back verizon. as long as i can get to Amon_RA's recovery,ill never really need an unlocked bootloader, so i guess it can wait a few days
If you want to avoid installing software on a pc (to run adb), you could perform the flash_image commands from a root shell in a terminal emulator - I infer from your post that there is already a rooted ROM present. But that's kind of tedious and error prone, since you can't cut and paste.
thanks. it wont turn on at all with a new power supply,so it may be time for a new one.
im enjoying this rooting and flashing,and modifying my phone,and i would like to to install the software and become savy in the "old school" method. just for the experience of it. and to make it easier to mess with phones that arent as easy to mess with as the eris,lol.
been pokin around some... would another option be to simply flash the in PB00IMG.ZIP hboot and do the battery pull has described in your thread Visual Example: The PB00IMG.ZIP update method ?
been pokin around some... would another option be to simply flash the in PB00IMG.ZIP hboot and do the battery pull has described in your thread Visual Example: The PB00IMG.ZIP update method ?
That might or might not work, depending on the past history of the phone. If you first flash the misc partition with Jcase's ("Flash any RUU") misc.img, then it will certainly work, as that prevents the "Main Version is Older!" problem from occuring - but then you are basically back to my instructions.
You can give it a shot though - it will either fail (harmlessly) with a Main Version error, or it will succeed. I would advise you to make a Nandroid backup first anyway before you begin, though: one time out of the many, many times I used the battery pull trick, the second phase of the PB00IMG.ZIP install happened after I reinserted the battery and re-started. (If that happens, you can put the custom recovery back with fastboot and then restore your saved Nandroid backup.)
eu1
The Following User Says Thank You to erisuser1 For This Useful Post:
thanks again for the help. i went ahead and gave it a shot. it worked as illustrated,with the exception that the screen was only dark for about half a second
i saw figure 5(in the visual example thread) coming on as i pulled the battery. i assure you i dint slack on it,lol... i had the cover off and my fingers on the battery as i pushed volume up.
i put the battery back in and booted into hboot and when it came up it continued to update. i did see the the 1.49.0000 s-off bootloader had been installed,so not knowing how to flash Amon_RA's recovery in adb or a terminal emulator if i let it completely update, i pulled the battery again in a moment of panic.
at this point i thot i had done a really bad thing,so i put the battery back in and booted it back up normally.it came upand seemed fine so i connected it back to the laptop and simply removed the PB00IMG.ZIP from the sd card.
i know it was reckless,but it seemed to work... powered it off,booted into hboot,and i still have the s-off bootloader,and only send for fastboot and vol up for recovery. went to recovery,picked reboot and when it came back up i sent texts,made some phone calls,took some pics,made sure it was all still working.
so looks like i have the unlocked bootloader and the little guy will be safe from whatever screwups i might have in the future.
im happy to report no eris's were harmed in the making of this post
Last edited by scotty85; January 4th, 2011 at 09:16 PM.
i saw figure 5(in the visual example thread) coming on as i pulled the battery. i assure you i dint slack on it,lol... i had the cover off and my fingers on the battery as i pushed volume up.
i put the battery back in and booted into hboot and when it came up it continued to update. i did see the the 1.49.0000 s-off bootloader had been installed,so not knowing how to flash Amon_RA's recovery in adb or a terminal emulator if i let it completely update, i pulled the battery again in a moment of panic.
at this point i thot i had done a really bad thing,so i put the battery back in and booted it back up normally.it came upand seemed fine so i connected it back to the laptop and simply removed the PB00IMG.ZIP from the sd card.
i know it was reckless,but it seemed to work... powered it off,booted into hboot,and i still have the s-off bootloader,and only send for fastboot and vol up for recovery. went to recovery,picked reboot and when it came back up i sent texts,made some phone calls,took some pics,made sure it was all still working.
Rest your mind. The sequence that it goes through first flashes the bootloader, and then the phone reboots rather quickly. This is done so that it is the *new* bootloader that finishes off the installation.
Immediately after the reboot, the (newly installed) bootloader starts verifying the original PB00IMG.ZIP file all over again - and this takes over a minute to perform. There is no writing to flash memory of the .zip file components during this time. That's why the "battery pull" is fairly safe - you have nearly a minute after the phone initially reboots before it is ready to actually begin writing to the phone's flash memory again. (Under normal circumstances - for almost every other device in the world - it is an extremely bad idea to pull power from a device that is having its' firmware flashed; in this peculiar case of the Eris though, you have a full minute or more where it is guaranteed that no writing to flash memory is occurring).
But I did tell you that there was a possibility that would happen, and gave you the prescription for that eventuality - make a Nandroid backup.
(BTW, the "Root" PB00IMG.ZIP ROM can also be "rooted" (as in, install Amon_RA's custom recovery) using One Click or Dummies - so you can let the PB00IMG.ZIP Root ROM installation run to completion, and still not need a PC with the SDK/adb/drivers installed on it.)
Backups are your friend - if you haven't done it yet, make one NOW.
eu1
The Following User Says Thank You to erisuser1 For This Useful Post:
thanks for the explanations. i did make backups,i was just unsure of how id get Amon_RA's recovery back onto the phone using fastboot so that i could run it. id assumed that allowing the update to complete would have put the phone into a state that my current Amon_RA recovery wouldnt have been there.
thanks for the explanations. i did make backups,i was just unsure of how id get Amon_RA's recovery back onto the phone using fastboot so that i could run it. id assumed that allowing the update to complete would have put the phone into a state that my current Amon_RA recovery wouldnt have been there.
You are correct that letting the Root PB00IMG.ZIP process run all the way through to completion would have over-written the custom recovery with an HTC (engineering) recovery.
But, as I pointed out twice - you can "root the root ROM" with either OneClick or Dummies, and this installs Amon_RA's recovery back into place without needing a PC/fastboot/adb.
In any event, it sounds like you are all set - enjoy the journey.
eu1
The Following User Says Thank You to erisuser1 For This Useful Post:
But, as I pointed out twice - you can "root the root ROM" with either OneClick or Dummies, and this installs Amon_RA's recovery back into place without needing a PC/fastboot/adb.
In any event, it sounds like you are all set - enjoy the journey.
eu1
wow it just clicked how easy it would have been to use the dummies method to put amons_ recovery back on... i was makin it way more complicatged in my mind than it actually was
well,i guess i know for the future. like you said,its set now and i am enjoying the journey! thanks again for your help directly,and everything you do for the forum
The HTC Droid Eris launched for Verizon Wireless on November 6th in part as the carrier's first Android Phone. However it was overshadowed by the other member of the inaugural Verizon Droid duo - the Motorola Droid. The Droid Eris might look fa... Read More