Root How To Install Engineering bootloader

[jcase]

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.

adb push flash_image /data/local/flash_image
adb shell chmod 777 /data/local/flash_image

Step 3:
Push custom.img to your phone

adb push custom.img /data/local/custom.img

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.

Step 4:
Copy PB00IMG.zip to your sdcard

Step 5:
Flash custom.img

If you flashed engtools3.zip (http://www.multiupload.com/L97EUYBG3V)

adb shell flash_image misc /data/local/custom.img

If you pushed flash_image

adb shell /data/local/flash_image misc /data/local/custom.img

Step 6:
Reboot to Bootloader and flash PB00IMG.zip

adb reboot bootloader

After the new rom is flashed, you can now use fastboot to flash a recovery image while in the bootloader

fastboot flash recovery recovery.img

Enjoy

Like my work? Buy a bum a beer downtown or donate to local homeless youth org.

 

[Papadroid]

Bump!

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.

 

[jcase]

Bump!

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.

 

[wendroid]

What does this mean? I have to know before attempting.

 

[kobel1up]

I can't get custom.img to be recognized in my cmd prompt. I am stuck. I installed the engtools.zip on my phone but still nothing.

 

[Demache]

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.

 

[bberryhill0]

Now that I have rooted and overclocked my leak 3 Eris this would be the obvious next step but I don't understand the instructions at all.

 

[kobel1up]

I know what you mean bberryhillo. Im stuck on step 5.

 

[gpa111]

I am on a 1.47 s-on bootloader rooted with:

http://androidforums.com/htc-droid-eris/125436-detailed-leak-root-tutorial-2.html

On step 5 I get:

user-MacBook-Pro:tools Arcadia$ ./adb shell /data/local/flash_image misc /data/local/custom.img
/data/local/flash_image: permission denied
user-MacBook-Pro:tools Arcadia$

 

[gpa111]

Think its working..

 

[gpa111]

Im getting fastboot permission denied on step 6, and fastboot devices lists nothing, any ideas?

 

[EricB]

I know what you mean bberryhillo. Im stuck on step 5.

Same here, I can't get it to work at all. I thought I did, but I'm still 1.49 S-On

 

[Papadroid]

Im getting fastboot permission denied on step 6, and fastboot devices lists nothing, any ideas?

Did you flash the PB00IMG file, you're not going to use adb until after you flash this file.

Same here, I can't get it to work at all. I thought I did, but I'm still 1.49 S-On

Which method did you use to root?

 

[EricB]

This one: http://androidforums.com/htc-droid-eris/125436-detailed-leak-root-tutorial.html

 

[gpa111]

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.

I'm going to try it on my windows partition soon.

 

[wendroid]

.

 

[ppbb]

stuck at step 5 too. its no clear to me where the downloaded files need to be saved. onto the phones sd card or the tools directory in sdk?

 

[large]

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?

 

[banduraj]

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.

 

[scary alien]

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:

http://androidforums.com/eris-all-t...pcs-no-scripts-needed-easy-2.html#post1416274

and this

http://androidforums.com/eris-all-things-root/125436-detailed-leak-root-tutorial-10.html#post1401164

Good luck!

 

[stagger]

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.

 

[erisuser1]

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

If you are interested, have a look at previous comments I made on this flash.

eu1


.

 

[scotty85]

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

 

[erisuser1]

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

 

[scotty85]

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