Root HBOOT?!?!

[g60madman]

Since I am still a n00b with the Evo in terms of hboot knowledge, what versions of the hboot are out there? And what in the world is the difference?!?!

I am currently on 1.04.2000 I can install my CM10, my CM9 Alpha (haven't released it yet), and also Harmonia. I just tried to install Mobstergunz HD lite and it crashed all over the place. I also have read that to use the Viper ROM you need to use hboot 1.58 and or 1.57. So can some one give me a crash course on the hboot, or direct me to a link pretty please

 

[mysticalnyte]

Good place to start is here for different versions available:
Unlimited.IO

Evo3d(CDMA)HBoot/S-off Differences & Rooting Background Info 10-13-12:
http://forum.xda-developers.com/showthread.php?t=1817513

Hope this helps!

 

[Brian706]

You can also look here for all the stock hboot downloads

http://androidforums.com/cdma-evo-3d-all-things-root/648902-radios-hboot-firmware-all-downloads.html

 

[BackHandLegend]

I run any ROM with 1.04

Viper ROM works flawlessly, and so does mobstergunz HD ROM.

 

[xploPR]

I run any ROM with 1.04

Viper ROM works flawlessly, and so does mobstergunz HD ROM.

+1

Im currently running Mazda's version of aokp cm10. With 1.04 and no issues.

 

[Prinny]

Hai g60, plz2b responding to ur thredz.

Originally Posted by mpgrimm2
Here is a list of Hboot differences and compatibilities gathered from various posts.
If you are S-Off and want to change your Hboot/Bootloader, see the next post for a How-To courtesy of xhausx and a download links courtesy of RamJet73. (Remember to thank them both!)

Hboots: ____________________ Differences:

1.04.2000 (Eng Hboot) = Extended functions ................. Appear to be incompatible with newer 2.89 based kernels
1.30 (Stock Hboot with 1.07.651.1 Gb) .................... Appear to be incompatible with newer 2.89 based kernels
1.40 (Stock Hboot with 1.13.651.7 Gb) ................... Appear to be incompatible with newer 2.89 based kernels
1.40.1100 (incl. w/Revolutionary S-Off) ........................... Appear to be incompatible with newer 2.89 based kernels

1.50 (Stock Hboot with 2.08.651.3 Gb) ................... Appear to be incompatible with newer 2.89 based kernels (VM ICS Leak Kernel will boot)

1.57 (Stk Hboot w/ 1.13.652.1 VM ICS Leak) ...... May be compatible with other ICS Leak kernels & newer 2.89 based kernels. (some reports)
.................................................. ..............................edit: Nandroid of GB roms will boot, but Clean GB Installs bootloop.

1.50.5050 (incl. w/Jbear for GB S-Off) ........................... May be compatible with newer 2.89 based kernels & prior fw/kernels (some reports)
1.57.5757 (incl. w/Jbear for ICS S-Off) .......................... May be compatible with newer 2.89 based kernels & prior fw/kernels (some reports)

1.58 (Stock Hboot with 2.89.651.2 ICS) ............. Compatible with newer 2.89 based kernels (& Vm ICS Leak), not GB based (some reports)
.................................................. ...........................edit: Some boot issues with AOSP/AOKP roms & kernels reported (ie CM9)

1.58.5858 (incl. w/Jbear for Sprint ICS S-Off) ............... Compatible with newer 2.89 based kernels (& Vm ICS Leak), not GB based (some reports)
.................................................. ...........................edit: Some boot issues with AOSP/AOKP roms & kernels reported (ie CM9)

Hboot Note: Stock Hboots Do Not Support All Fastboot Commands (see below)

Kernel Note:
.......... VM ICS Leak Kernel: 3.0.16-g4211684

....... Sprint 2.89 ICS Kernel: 3.0.16-g294f767

Madmaxx & Ramjet73 have identified why kernels may not flash correctly AFTER the Sprint 2.89 Base kernel has been installed. See Madmaxx's explanation further down.

See full post here:

http://forum.xda-developers.com/showthread.php?t=1817513

Edit: mysticalnyte beat me to it. Maybe I should read responses before posting. >.>

 

[SuperAfnan]

I just use the ENG hboot everything works fine and smooth on it....


What's the point of switching to another then?

 

[ramjet73]

I just use the ENG hboot everything works fine and smooth on it....


What's the point of switching to another then?

It used to be that the 1.57.xxxx or 1.58.xxxx hboot was needed to run the Viper3D ROM, but as of r310 it will work with any hboot. AFAIK, the only ROM's that require one of the ICS hboots at this point are the stock ROM and Cool ICS.

There are some issues using TWRP with hboots other than the ICS version documented in the http://androidforums.com/evo-v-4g-all-things-root/663486-twrp-2-3-htc-evo-3d.html thread. I'm not sure if the error with other hboots will cause any significant problems or not but if you are using TWRP and only flashing Sense based ICS ROM's it might be best to use the 1.57 stock or JBear 1.57.5757 hboot.

ramjet73

 

[joe_blow]

Problem: When I try and install g60madman's CM10 builds it boot loops. I am running JBear 1.57.5757 hboot. It will boot loop even after I restore a working backup and even if I install stock hboot etc. The only way to get out of the boot loop that I have found is to restore the phone to stock and then restore the working backup.

1) Could the CM10 build be made to work with an hboot of 1.57.xx or latter?
2) What is the way to get out of the "boot loop" that does not require a full 5 steps back to stock?

I am running Midnight ROM now but would like the ability to work on g60madman's CM10 builds. Is there a way to go between the two?

 

[Prinny]

Problem: When I try and install g60madman's CM10 builds it boot loops. I am running JBear 1.57.5757 hboot. It will boot loop even after I restore a working backup and even if I install stock hboot etc. The only way to get out of the boot loop that I have found is to restore the phone to stock and then restore the working backup.

1) Could the CM10 build be made to work with an hboot of 1.57.xx or latter?
2) What is the way to get out of the "boot loop" that does not require a full 5 steps back to stock?

I am running Midnight ROM now but would like the ability to work on g60madman's CM10 builds. Is there a way to go between the two?

Try the 1.04 eng hboot. See if it.works for both.

 

[ramjet73]

Try the 1.04 eng hboot. See if it.works for both.

The engineering (ENG) hboot should work for both, but causes errors in the TWRP 2.3.3.0 recovery that joe_blow is using.

I just tested the JBear GB (1.50.5050) hboot with TWRP 2.3.3.0 and that seems to work fine, and it boots mazda's AOKP 3.5.2. It also boots the ICS Sense based ROM's fine, so you might want to give that hboot version a try.

ramjet73

 

[thebryceee]

I've ran Viper on 1.04. I used to run everything on that.

 

[g60madman]

1.04 works on my cm10 still working on revamping it. Been also working on cm9

 

[treysmith]

Never have any problem with HBoot 1.04 for EVO V 3D 4G.
I was running HBoot 1.57 S-Off with JBear.
Now I'm running HBoot 1.04, because of CM/AOSP/AOKP
Mobstergunz, HD Lite and Unlocked Potential Rom works flawlessly on HBoot 1.04.

I appreciate devs hard work.
Thanks, guys for y'all hard work.

 

[ramjet73]

Never have any problem with HBoot 1.04 for EVO V 3D 4G.
I was running HBoot 1.57 S-Off with JBear.
Now I'm running HBoot 1.04, because of CM9 and CM10 Roms.

Most AOSP based ROM's (CM9, CM10, AOKP, PA) flash and boot fine with any hboot lower than 1.57. However, TWRP2 touch recovery doesn't seem to like the partition configuration of the ENG 1.04 bootloader so I recommend JBear GB (1.50.5050) over 1.04 if you are a TWRP2 user.

ramjet73

 

[joe_blow]

Ramjet73, good observation!
I installed PG86IMG_JBear_1.50.5050_hboot_GB.zip from your post http://forum.xda-developers.com/showpost.php?p=30014044&postcount=7

So with that:
CM10 works 100%
TWRP 2.3.3 works 100%
Stock ROM ( like midnight ) boot loop.

Is there any way to win? Any way to boot both but with a 1.5x hboot?

 

[ramjet73]

Stock ROM ( like midnight ) boot loop.

Is there any way to win? Any way to boot both but with a 1.5x hboot?

I'm surprised the Sense based ROM's for the Evo V don't flash and boot with the JBear 1.50.5050 hboot since I know every ROM does on the Evo 3D at this point except Cool ICS and the stock Sprint ICS ROM. In fact, I currently have the JBear 1.50.5050 hboot installed while I'm trying to become more familiar with TWRP 2.3.3.0.

Other than asking the Evo V developers about the hboot requirement for their ROM's, I don't know what to tell you since there is no single hboot that will run all ROM's on the Evo 3D/V. Viper3D used to have a requirement for the 1.57/1.58 hboot, but now it runs with any bootloader. Maybe virus would be willing to share what he did to remove that restriction with the ROM developers for the Evo V.

Edit: What Evo V Sense ROM are you trying to run? I can flash it on my Evo 3D with JBear 1.50.5050 and 4EXT Recovery to see if I can get it to boot.

ramjet73

 

[treysmith]

I'm surprised the Sense based ROM's for the Evo V don't flash and boot with the JBear 1.50.5050 hboot since I know every ROM does on the Evo 3D at this point does except Cool ICS and the stock Sprint ICS ROM. In fact, I currently have the JBear 1.50.5050 hboot installed while I'm trying to become more familiar with TWRP 2.3.3.0.

Other than asking the Evo V developers about the hboot requirement for their ROM's, I don't know what to tell you since there is no single hboot that will run all ROM's on the Evo 3D/V. Viper3D used to have a requirement for the 1.57/1.58 hboot, but now it runs with any bootloader. Maybe virus would be willing to share what he did to remove that restriction with the ROM developers for the Evo V.

Edit: What Evo V Sense ROM are you trying to run? I can flash it on my Evo 3D with JBear 1.50.5050 and 4EXT Recovery to see if I can get it to boot.

ramjet73

Actually I have no problem using H.Boot 1.04 it works prefectly for any Rom and CM/AOSP/AOKP Roms.
I'm currently running H.Boot 1.04 CyanogenMod10 Android version 4.1.2 ParanoidAndAndroid and it work perfectly.

 

[ramjet73]

Actually I have no problem using H.Boot 1.04 it works prefectly for any Rom and CM/AOSP/AOKP Roms.
I'm currently running H.Boot 1.04 CyanogenMod10 Android version 4.1.2 ParanoidAndAndroid and it work perfectly.

Can you flash and boot all the Sense based ICS ROM's for the Evo V that are available on this forum with that bootloader? If so, that might be an advantage of engineering (ENG) 1.04 hboot, at least for 4EXT Recovery users. I've never had problems with most of the ICS Sense ROM's for the Evo 3D, so until I try the ROM's specific to the Evo V flashed with 4EXT and the JBear 1.50.5050 hboot I'm not ready to say that the ENG hboot is any more "universal" for the Evo V than other hboots at 1.50 or below, including the 1.4 version that seems to be popular with Evo 3D users. And it's been proven already that the 1.50.XXXX hboots are more compatible with TWRP2 (touch) than the ENG bootloader.

The ENG 1.04 hboot works fine on most ROM's but doesn't boot anything based on the Sprint 2.89.651.2 kernel. Currently that includes the Cool ICS and Sprint ICS stock ROM's and versions of Viper3D at r284 or lower, which require hboot 1.57 or higher. Most Evo 3D ROM dev's have downgraded the kernel and/or other components of their Sense ICS ROM's to make them compatible with older hboots like ENG, but it's not clear what will be required for the JB 4.1.1 Sense 4+ ROM's to boot once they are available on the Evo 3D/V since there are none working yet.

Edit: It seems the Evo V ROM that joe_blow is having problems with using the 1.50.5050 hboot is one the Midnight ROM's. Can you flash and boot those with the ENG 1.04 hboot? I noticed that the OP's for those ROM's have links to the 1.57 hboot.

ramjet73

 

[nsciucco]

1.04 eng H boot. Works for me. Never had a problem. I use 4EXT. It seems to be a better recovery

 

[ramjet73]

1.04 eng H boot. Works for me. Never had a problem. I use 4EXT. It seems to be a better recovery

It works on most ROM's with 4EXT, but not all.

Have you used either of the Midnight ROM's for the Evo V with the ENG 1.04 hboot?

ramjet73

 

[nsciucco]

It works on most ROM's with 4EXT, but not all.

Have you used either of the Midnight ROM's for the Evo V with the ENG 1.04 hboot?

ramjet73

yes. I have tried every ROM for this phone. Now I just use my Rom MOBSTER/UNSENSEABLE

 

[ramjet73]

yes. I have tried every ROM for this phone. Now I just use my Rom MOBSTER/UNSENSEABLE

Then I wonder why both of the Midnight ROM's link the 1.57 hboot on their OP's and say to download and install it if you can't boot.

I'll try flashing the standard version of Midnight with hboot 1.50.5050 and TWRP2 and if that doesn't boot, as joe_blow reported, I'll try it with 4EXT. If both of those fail, I'll try it with the ENG hboot.

ramjet73

 

[ramjet73]

yes. I have tried every ROM for this phone. Now I just use my Rom MOBSTER/UNSENSEABLE

What was the last version of Midnight ROM that you installed?

I just tried flashing the current (1.4.2) version of Midnight ROM with hboot 1.50.5050 and 4EXT and it hung on the boot animation for a while, then rebooted and hung again at the same point. I switched to the ENG 1.04 hboot and got exactly the same result. I even re-flashed it with 1.04 just to make sure everything was done correctly.

Next I flashed it again with hboot 1.58.5858 installed, which is the Sprint equivalent of 1.57.5757, and it booted fine so it appears the current version of Midnight ROM is like the Evo 3D ROM's I mentioned previously that require the current version of the bootloader. I'd be very surprised if you could flash and boot the 1.4.2 version of Midnight ROM with the ENG 1.04 hboot.

So I still believe that the JBear GB 1.50.5050 hboot (and probably others that are lower numbered than 1.57) is just as "universal" as the ENG 1.04 hboot and doesn't cause errors with TWRP 2.3.3.0, so I recommend it as the preferred hboot when using the TWRP2 touch recovery.

I'm not sure why Midnight ROM 1.4.2 seems to require the current hboot but maybe the XDA thread I linked in post #19 of this thread could help the developer make it compatible with other hboots.

ramjet73

 

[nsciucco]

What was the last version of Midnight ROM that you installed?

I just tried flashing the current (1.4.2) version of Midnight ROM with hboot 1.50.5050 and 4EXT and it hung on the boot animation for a while, then rebooted and hung again at the same point. I switched to the ENG 1.04 hboot and got exactly the same result. I even re-flashed it with 1.04 just to make sure everything was done correctly.

Next I flashed it again with hboot 1.58.5858 installed, which is the Sprint equivalent of 1.57.5757, and it booted fine so it appears the current version of Midnight ROM is like the Evo 3D ROM's I mentioned previously that require the current version of the bootloader. I'd be very surprised if you could flash and boot the 1.4.2 version of Midnight ROM with the ENG 1.04 hboot.

So I still believe that the JBear GB 1.50.5050 hboot (and probably others that are lower numbered than 1.57) is just as "universal" as the ENG 1.04 hboot and doesn't cause errors with TWRP 2.3.3.0, so I recommend it as the preferred hboot when using the TWRP2 touch recovery.

I'm not sure why Midnight ROM 1.4.2 seems to require the current hboot but maybe the XDA thread I linked in post #19 of this thread could help the developer make it compatible with other hboots.

ramjet73

wow. thats a lot of testing. lol. Good Work!!! -- It was a much older version of Midnight. Probably last september