This is a modified HBOOT that is designed to be compatible with ICS while retaining its S-OFF capabilities. It is NOT an ENG hboot, but rather a S-OFF hboot. It still has fastboot capabilities.
This is not my work, but I got the permission to release the modified leak (the full ICS leak) from Unlimited.io team (Hyuh).
This has the modified hboot in it, so you do not need to flash an engineering hboot before flashing the leak. It has everything in it. Just flash this as you would with the normal leak such as:
renaming it to PH85IMG.zip and then flashing it through hboot, or flashing this with fastboot under RUU mode, or whatever method works best for you
The only difference with this is that this is fully compatible with the ICS ROM, while the other ENG hboots are not. ENG hboots still will work, but it is said that this hboot is more compatible.
REMINDER: YOU MUST HAVE S-OFF BEFORE FLASHING THE MODIFIED ROM OR BEFORE FLASHING THE MODIFIED HBOOT!!!
Disclaimer: I am not responsible for bricks or malfunctions you may experience. Flashing a new hboot can be dangerous, so heed caution. (Insert standard disclaimer here)
LINK for the -FULL- modified ICS leak:
http://hyuh.net/files/ruby/PH85IMG_juopunutbear.zip
CREDITS: Unlimited.io and hyuh for their awesome work, and Football for releasing this leak!
I also took the liberty of pulling the hboot from the modified ICS leak, for those who need to flash the updated hboot on the ICS ROM, as I previously had an incompatible (but working) ENG hboot on the ICS rom. I just flashed this and it worked.
Again, you must have S-OFF!
Instructions: Download the file and then flash in fastboot with this command
fastboot flash hboot updatedhbootICS.img
Note: I used this method when I had an ENG hboot beforehand, so results may vary.
This updated hboot version is 1.93.2222
Link: Look at file attached
Thanks for the post, but the ENG boot loader DOES work just fine with ICS. Don't want other people to be confused.
If it is working, I'm not sure how it is supposedly incompatible.
Sent from my HTC_Amaze_4G using XDA
Keylogger_0 said:
This is a modified HBOOT that is designed to be compatible with ICS while retaining its S-OFF capabilities.
This is not my work, but I got the permission to release the modified leak (the full ICS leak) from Unlimited.io team (Hyuh).
This has the modified hboot in it, so you do not need to flash an engineering hboot before flashing the leak. It has everything in it. Just flash this as you would with the normal leak such as:
renaming it to PH85IMG.zip and then flashing it through hboot, or flashing this with fastboot under RUU mode, or whatever method works best for you
The only difference with this is that this is fully compatible with the ICS ROM, while the other ENG hboots are not.
REMINDER: YOU MUST HAVE S-OFF BEFORE FLASHING THE MODIFIED ROM OR BEFORE FLASHING THE MODIFIED HBOOT!!!
Disclaimer: I am not responsible for bricks or malfunctions you may experience. Flashing a new hboot can be dangerous, so heed caution. (Insert standard disclaimer here)
LINK for the -FULL- modified ICS leak:
http://hyuh.net/files/ruby/PH85IMG_juopunutbear.zip
CREDITS: Unlimited.io and hyuh for their awesome work, and Football for releasing this leak!
I also took the liberty of pulling the hboot from the modified ICS leak, for those who need to flash the updated hboot on the ICS ROM, as I previously had an incompatible (but working) ENG hboot on the ICS rom. I just flashed this and it worked.
Again, you must have S-OFF!
Instructions: EXTRACT the zip file and then flash in fastboot with this command
fastboot flash hboot updatedhbootICS.img
Note: I used this method when I had an ENG hboot beforehand, so results may vary.
This updated hboot version is 1.93.2222
Link: Look at file attached
Click to expand...
Click to collapse
I'm using the eng hboot with ics right now with no problems........ anyway is the hboot and eng hboot or is it just s-off
Fixed post. It is a regular S-OFF hboot. Hyuh himself said that this hboot update is more compatible with ICS, and that an ENG hboot is NOT necessary.
Keylogger_0 said:
Fixed post. It is a regular S-OFF hboot. Hyuh himself said that this hboot update is more compatible with ICS, and that an ENG hboot is NOT necessary.
Click to expand...
Click to collapse
While an eng hboot is not necessary its more useful then a standard release hboot and its not more compatible its just a bootloader the eng hboot and this hboot are equally compatible with any rom
sportsstar89 said:
While and eng hboot is not necessary its more useful then a standard release hboot and its not more compatible its just a bootloader the eng hboot and this hboot are equally compatible with any rom
Click to expand...
Click to collapse
I'm just rephrasing what hyuh mentioned to me that's all. Nevertheless, it is here.
Keylogger_0 said:
I'm just rephrasing what hyuh mentioned to me that's all. Nevertheless, it is here.
Click to expand...
Click to collapse
Yep just letting you know the facts
Any differences besides "compatability"??
Sent from my HTC_Amaze_4G using xda premium
rbaruch said:
Any differences besides "compatability"??
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
Nope its just the same way jupuntobear modified the other stock hboot i would recommend sticking to eng hboot if you got it
rbaruch said:
Any differences besides "compatability"??
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
From what I've seen in the other thread, to flash the NFC part of the ICS update, you need the new HBOOT, and this allows the NFC part to flash correctly
Keylogger_0 said:
From what I've seen in the other thread, to flash the NFC part of the ICS update, you need the new HBOOT, and this allows the NFC part to flash correctly
Click to expand...
Click to collapse
Right, and the Tmous ICS RUU comes with a version of HBoot necessary to flash the updated NFC (and thus why it reboots on its own a few times).
So the point of having a "more compatible" HBoot I don't understand, unless for futureproofing a new version of NFC or something.
Sent from my HTC Amaze 4G using XDA
I flashed it and checked it out. This actually gives you the functions of both ENG and SHIP HBoots. You can SuperCID and run fastboot flash commands. Seems like this might be the better HBoot to flash. If only it didn't say "JuopunutBear" where it should say "Locked"/"Unlocked"
Stupid question... (the best kind!)
Will flashing this hboot wipe my device or my CWM?
I understand flashing the whole freakin leak will, but if flashing this hboot isn't going to change anything other than supposedly be more compatible - why not?
djxspike said:
Stupid question... (the best kind!)
Will flashing this hboot wipe my device or my CWM?
Click to expand...
Click to collapse
I don't see that as a stupid question, alot of people won't know that answer. Aren't we a community, here to help each other?
Sent from my HTC_Amaze_4G using Tapatalk 2
I had troubles with other hboots and this worked perfectly for me. Running ICS on my amaze 4g from mobilicty , thanks for all your help OP!
djxspike said:
Stupid question... (the best kind!)
Will flashing this hboot wipe my device or my CWM?
I understand flashing the whole freakin leak will, but if flashing this hboot isn't going to change anything other than supposedly be more compatible - why not?
Click to expand...
Click to collapse
No it will not wipe your device or your recovery
djxspike said:
Stupid question... (the best kind!)
Will flashing this hboot wipe my device or my CWM?
I understand flashing the whole freakin leak will, but if flashing this hboot isn't going to change anything other than supposedly be more compatible - why not?
Click to expand...
Click to collapse
No, the hboot alone will not wipe anything, I tested it myself.
Sent from my HTC_Amaze_4G using Tapatalk 2 Beta-5
ok ive never just done the hboot so how do we install it ,,,put on sd card and open comand prompt or what,,,,thanks in advance
crose948 said:
ok ive never just done the hboot so how do we install it ,,,put on sd card and open comand prompt or what,,,,thanks in advance
Click to expand...
Click to collapse
Download the file from post 1. Copy to your external sd card root folder and rename to ph85img.zip (do not extract the download). Reboot into bootloader and it will automatically update.
St Veronus said:
Download the file from post 1. Copy to your external sd card root folder and rename to ph85img.zip (do not extract the download). Reboot into bootloader and it will automatically update.
Click to expand...
Click to collapse
ah ezzz ok thank you so much ,,,
Related
This is for old firmware folks only! IF ARE RUNNING THE ICS LEAK FIRMWARE, DON'T FLASH THIS!
If you S-ON your device with this installed, IT WILL BRICK.
What is this and why is it better than the ENG Hboot?
This is a patched version of the 2.11 Hboot. This is for GB firmware users. This was patched by the Juopunutbear team. It is very similar to their 2.21 patched hboot. It allows for fastboot commands without HTCDev.com unlock, but not the full engineering set. This is safer for users. This is also not a leaked HBoot like the ENG one was, so this should cause fewer issues with devices like the ENG hboot may have. If you are on the ENG hboot and do not need the extended subset of commands and/or are having issues with the ENG hboot, I recommend flashing this one.
Please thank the Juopunutbear team for developing this as a better alternative to the engineering hboot.
Installation:
-1.S-OFF the device
0. Make sure you aren't on ICS firmware
1. CHECK MD5!!!!
2. Rename file to PH98IMG.zip and place on SD card
3. Reboot to HBOOT
4. Flash bootloader when prompted with volume up.
Download: HERE
MD5: cf20a2a731b4415fa11a60920730747a
If any issues arise from the use of this hboot, please bring it to my attention so I can contact the Juopunutbear team. I am just the messenger with this one.
Again, flashing this or anything you find on the internet is your responsibility. Myself or the Juopunutbear team can't be held responsible.
con247 said:
This is for old firmware folks only! IF ARE RUNNING THE ICS LEAK FIRMWARE, DON'T FLASH THIS!
What is this and why is it better than the ENG Hboot?
This is a patched version of the 2.11 Hboot. This is for GB firmware users. This was patched by the Juopunutbear team. It is very similar to their 2.21 patched hboot. It allows for fastboot commands without HTCDev.com unlock, but not the full engineering set. This is safer for users. This is also not a leaked HBoot like the ENG one was, so this should cause fewer issues with devices like the ENG hboot may have. If you are on the ENG hboot and do not need the extended subset of commands and/or are having issues with the ENG hboot, I recommend flashing this one.
Please thank the Juopunutbear team for developing this as a better alternative to the engineering hboot.
Installation:
-1.S-OFF the device
0. Make sure you aren't on ICS firmware
1. CHECK MD5!!!!
2. Rename file to PH98IMG.zip and place on SD card
3. Reboot to HBOOT
4. Flash bootloader when prompted with volume up.
Download: HERE
MD5: cf20a2a731b4415fa11a60920730747a
If any issues arise from the use of this hboot, please bring it to my attention so I can contact the Juopunutbear team. I am just the messenger with this one.
Again, flashing this or anything you find on the internet is your responsibility. Myself or the Juopunutbear team can't be held responsible.
Click to expand...
Click to collapse
Thanks for this, I wont be using as im on the ics leak but im sure those on 2.11 will find this useful
Just to make sure, I was on the ics leak before getting s-off then flashed the eng hboot GB firmware PH98IMG that suprchilpil posted. This would still be relevant for me if I didn't need the eng hboot right?
Sorry if it's a dumb question, but I guess better to ask and confirm.
Con, would you recommend downgrading if on the ICS leak and getting back to Hboot 2.11 ?
Con, you're a great man for what you do, but could you PLEASE make a wtf to do with s-off for dummies, (from incredible where everything was easy, only one hboot) Most of this confuses the hell out of me. If anyone could make a "what is all this" or whatever thread it would be of much thanks.
Edit: so in other words, i have no idea what any of this means lol.
I will stay on the 2.11 eng hboot for the time being as I have had no issues since downgrading from 2.21.
I will however download this and keep it handy just in case.
Thanks
I can write more notes tomorrow. I will have time in the next couple days to hopefully do a big info dump.
Thanks for putting this out there....
Sent from my ADR6425LVW using Tapatalk
Thanks for this con! I resolved my data loss problems by ruu and factory reset, but was unable to use fastboot commands to install the latest amonra. This is the perfect solution!
Sent from my ADR6425LVW using Tapatalk 2
Does this still say locked? Or does it have jb in place? I kinda like that the eng hboot just says locked
Sent from my ADR6425LVW using Tapatalk
isdnmatt said:
Does this still say locked? Or does it have jb in place? I kinda like that the eng hboot just says locked
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
It says juopunutbear.
Sent from my ADR6425LVW using Tapatalk 2
Remember, you can always flash the stock hboot to get locked back
Thanks for this con, I feel better using this over the ENG hboot
i flashed the gb firmware but not the ruu, but now im trying to flash the ruu to try and fix the 4g problem.. but this hboot wont flash the gb ph98img file. i dont have to relock do i? or is that my problem?
emarietta said:
i flashed the gb firmware but not the ruu, but now im trying to flash the ruu to try and fix the 4g problem.. but this hboot wont flash the gb ph98img file. i dont have to relock do i? or is that my problem?
Click to expand...
Click to collapse
What do you mean it won't flash?
con247 said:
What do you mean it won't flash?
Click to expand...
Click to collapse
I've tried twice as well I even did the ad card fix and it won't flash
Sent from my ADR6425LVW using XDA
shawnshawn90 said:
I've tried twice as well I even did the ad card fix and it won't flash
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
Flashed just fine for me this a.m. I was on stock ota boot, unlocked. Just renamed and it flashed like a ph98 file.
Sent from my ADR6425LVW using xda premium
con247 said:
What do you mean it won't flash?
Click to expand...
Click to collapse
First time it found it and the side bar thing loaded like it was going to flash then it sent me right to recovery. And now it won't even find it at all
Had the ENG version
Downloaded via phone
Verified MD5 using AFV
Copied to root ext sdcard
Renamed PH98IMG.zip
Booted phone into bootloader
Flashed
Rebooted
Fine.... Worked great..
Thanks con247...
Via Rezound using XDA Premium
Con question for you or anyone else who has done it. Have you upgraded to this hboot from ENG? If so do you recommend it? Reason I'm asking is I haven't done it yet...still with ENG and it's working fine. I know if it ain't broke then don't fix it. Just want to hear the consensus on this one. Thanks.
Sent from my ADR6425LVW using Tapatalk
The main question is the title - Should you S-off before or after the OTA?
I have seen people around the forums (via a few searches) say that it is likely a good idea to perform S-off before OTA because we didn't know for sure if the OTA would close the S-off exploit. Now that the OTA is a known quantity, is that still the best route?
My device is:
Stock rom and firmware (2.01.605.11)
Unlocked
AmonRA 3.15 recovery
Rooted
I'm a little nervous about doing S-off, but I figure it will be really handy to have it once its done, and I understand it really is no big deal. My end goal is to run the Venom rom and then move to AOKP/CM9 once they have most of the bugs worked out. Would my best course of action be to S-Off, run the firmware updater, reinstall recovery (probably TWRP, seems like that is the most popular one at the moment), then flash my rom of choice? Will I need to re-root if I switch to a different recovery?
UPDATE:
S-off is done and was no big deal, I got it on my third try. I selected to not install the jb_hboot during the process, since I'm doing RUU next.
The 3.14.605.12 RUU (from android police) was as simple as could be, I renamed the file to PH98IMG.zip and dumped it into my sd card, once I rebooted into the bootloader it was automatic from there
I got stuck on the "flash juopunut Bear hboot" part, I am using Hasoon2000's HTC Rezound ALL-In-One Kit and S-Off Toolkit. I thought I could just flash the hboot from this and be done... I learned that unless you have the jb_hboot (the latest vigor hboot from unlimited.io) installed you can't use ADB commands (which the toolkits use). The solution was very simple. I just renamed the jb_hboot to PH98IMG.zip, rebooted into the bootloader and it was installed.
TWRP v. 2.20 flashed, for some reason my phone doesn't charge while plugged in and booted into this recovery. I guess I need to make sure I have a nice charge if I want to do anything major.
Installed ViperRez rom 1.03, now I'm toying around with it
Originally Posted by AshtonTS
Originally Posted by YTHero
My device is:
Stock rom and firmware (2.01.605.11)
Unlocked
AmonRA 3.15 recovery
Rooted
I want to run a custom (like ViperRez or CM9) ICS rom with the OTA (3.14.605.12) updated firmware.
So my process will be:
S-Off -> flash Hboot/radio/firmware files from 3.14.605.12 -> flash juopunut Bear hboot -> flash TWRP -> Flash ICS rom
Is my plan correct in that I should flash juopunutBear hboot after I flash the Hboot/radio/firmware files from 3.14.605.12? If so why?
Is there anything else that I should do in between these steps that I haven't identified? Am I taking any unnecessary risks by doing it this way?
Click to expand...
Click to collapse
Yeah, flash the RUU, then the JBear hboot, then TWRP/Amon Ra, then a Rom
Click to expand...
Click to collapse
I would do it beforehand. Once you are s-off, you can flash the latest firmware without installing the whole RUU also.
But it limits from getting the actual ota which I love to see
Sent from my ADR6425LVW using xda app-developers app
I would do it before and then after you S-Off run through this PH98IMG RUU. From talks, this is the OTA.
http://forum.xda-developers.com/showthread.php?t=1810931
Then flash the patched 2.25.2525 JB hboot from http://unlimited.io/hboot-downloads/
EDIT:
Alternatively you could S-Off, flash latest radios and patched hboot, then flash a rom of your choosing based on 605.10 or 605.12.
I'm still going to wait to see if we can get s-off on ics before updating today as I don't have the wire to currently do the exploit.
Sent from my ADR6425LVW using xda app-developers app
All I am saying is this. Why wait for the OTA when their are already roms based off 605.10, barely anything changed from it to 605.12. Also, S-Off will stick as long as you make it stick.
why wait for the ota when the ota was leaked?
YTHero said:
The main question is the title - Should you S-off before or after the OTA?
I have seen people around the forums (via a few searches) say that it is likely a good idea to perform S-off before OTA because we didn't know for sure if the OTA would close the S-off exploit. Now that the OTA is a known quantity, is that still the best route?
My device is:
Stock rom and firmware (2.01.605.11)
Unlocked
AmonRA 3.15 recovery
Rooted
I'm a little nervous about doing S-off, but I figure it will be really handy to have it once its done, and I understand it really is no big deal. My end goal is to run the Venom rom and then move to AOKP/CM9 once they have most of the bugs worked out. Would my best course of action be to S-Off, run the firmware updater, reinstall recovery (probably TWRP, seems like that is the most popular one at the moment), then flash my rom of choice? Will I need to re-root if I switch to a different recovery?
Click to expand...
Click to collapse
You are on Gingerbread firmware, that's the first thing to recognize. There's lots of development tools that were designed AFTER the Gingerbread firmware (2.xx is GB; 3.xx is ICS). In fact Amon Ra 3.15 was the version done after the ICS leak (because mount points were changed).
So you can (and probably should) do the S-OFF using the GB version over at Juopunut's site and then either wait for the ICS OTA to come to your phone or flash it in bootloader as a PH98IMG.ZIP (the RUU is available via Android Police, 3.14.605.12 is the "official" ICS, and I'm pretty sure its here on XDA but I don't remember the thread.)
If you don't want to wait for the OTA, it doesn't matter whether you are S-ON or S-OFF, you'll still have to flash the RUU in hboot. Both will completely wipe your phone, and the S-OFF process will wipe your CARD so use a different card before you do it!
Finally, to reiterate what's all over by now: the "official" update, 3.14.605.12 is only marginally different than the unofficial leak that's been out since May, 3.14.605.10, and the radios, kernel and hboot are all the same.
hgoldner said:
So you can (and probably should) do the S-OFF using the GB version over at Juopunut's site and then either wait for the ICS OTA to come to your phone or flash it in bootloader as a PH98IMG.ZIP (the RUU is available via Android Police, 3.14.605.12 is the "official" ICS, and I'm pretty sure its here on XDA but I don't remember the thread.)
If you don't want to wait for the OTA, it doesn't matter whether you are S-ON or S-OFF, you'll still have to flash the RUU in hboot. Both will completely wipe your phone, and the S-OFF process will wipe your CARD so use a different card before you do it!
Click to expand...
Click to collapse
I recieved the OTA today from Verizon, but deferred to take until I figured out what I want to do. If I understand what you are saying:
S-Off -> OTA -> install TWRP -> then Flash ViperRez or whatever rom
Taking the OTA seems like the easiest and most straight forward way of upgrading to ICS radios/hboot. Will I need to do anything else before or following the OTA? I feel like somewhere I read that I will need to patch the hboot because I will be S-off.
YTHero said:
I recieved the OTA today from Verizon, but deferred to take until I figured out what I want to do. If I understand what you are saying:
S-Off -> OTA -> install TWRP -> then Flash ViperRez or whatever rom
Taking the OTA seems like the easiest and most straight forward way of upgrading to ICS radios/hboot. Will I need to do anything else before or following the OTA? I feel like somewhere I read that I will need to patch the hboot because I will be S-off.
Click to expand...
Click to collapse
After you s off, flash juopunutBears hboot it should be on his website
Sent from my ADR6425LVW using xda app-developers app
Squirrel1620 said:
After you s off, flash juopunutBears hboot it should be on his website
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
I'm trying to understand this post
http://forum.xda-developers.com/showpost.php?p=29715514&postcount=51
and this thread
http://forum.xda-developers.com/showthread.php?t=1614366
superchilpil said:
New firmware patch huh?
This is simply for those upgrading to ICS firmware on a GB rom Or and ICS rom that had the gingerbread patch flashed over it
Whats the difference between the stock Hboots and the JB/ENG Hboots?
Simply, These Hboots have fastboot commands enabled WITHOUT unlocking the bootloader
I suggest if you use fastboot alot to use these hboots
Click to expand...
Click to collapse
I'm just trying to figure out if I will have to reflash the juopunutBears hboot after I flash the Hboot/radio/firmware files from 3.14.605.12
So will it be:
S-Off -> Hboot/radio/firmware files from 3.14.605.12 -> juopunut Bear hboot ->install TWRP -> then Flash ViperRez or whatever ICS rom
YTHero said:
So will it be:
S-Off -> Hboot/radio/firmware files from 3.14.605.12 -> juopunut Bear hboot ->install TWRP -> then Flash ViperRez or whatever ICS rom
Click to expand...
Click to collapse
You got it right on.
Sent from my ADR6425LVW using xda app-developers app
Is there a way to swap the Hboot for different ROMs without having to use a PC to remove PC86IMG.zip from the SD card? Many AOSP ROMs require older Hboot versions and some of the new 2.89 base ROMs need the newer 1.58 Hboot to but after you flash the older Hboot you are stuck if you are running the new base and have to use a PC to remove the PC86IMG.zip from the SD card. Seems like we need an option in recovery or some other way to switch Hboots when away from a computer to change ROMs.
bpc4209 said:
Is there a way to swap the Hboot for different ROMs without having to use a PC to remove PC86IMG.zip from the SD card? Many AOSP ROMs require older Hboot versions and some of the new 2.89 base ROMs need the newer 1.58 Hboot to but after you flash the older Hboot you are stuck if you are running the new base and have to use a PC to remove the PC86IMG.zip from the SD card. Seems like we need an option in recovery or some other way to switch Hboots when away from a computer to change ROMs.
Click to expand...
Click to collapse
Put the hboot pg86 on your sd.
Flash Rom
Reboot to bootloader (from recovery) to flash hboot
Boot system and rename the pg86 with a file manager
You don't have to remove the pg86img, just rename it.Does this answer your question?
Sent from my PG86100 using Tapatalk 2
Wikd said:
Put the hboot pg86 on your sd.
Flash Rom
Reboot to bootloader (from recovery) to flash hboot
Boot system and rename the pg86 with a file manager
You don't have to remove the pg86img, just rename it.Does this answer your question?
Sent from my PG86100 using Tapatalk 2
Click to expand...
Click to collapse
No... Because after you flash an older Hboot say, 1.40 and you were on a new 2.89 base ROM it will no longer boot because it requires the new 1.58 Hboot sooo..you can't just use a file explorer to change the name...
bpc4209 said:
No... Because after you flash an older Hboot say, 1.40 and you were on a new 2.89 base ROM it will no longer boot because it requires the new 1.58 Hboot sooo..you can't just use a file explorer to change the name...
Click to expand...
Click to collapse
Right, I've done that on accident before. What I'm saying is, don't flash the new hboot until after the Rom flash. I go from zr3dx to venom all the time with no computer. They require different hboots. This is how I do it.
Let's say I'm on zr3dx with hboot 1.4 and I want to go to venom. I'll rename my "158hbootPG86IMG.zip" to PG86IMG first. then I go to recovery and flash venom, then I reboot to bootloader from recovery and it'll flash the hboot 1.58. It boots up and I promptly rename it back to "158hbootPG86IMG.zip".
If I want to go back to zr3dx I just do the same process with the 1.4 hboot that's on my sd and flash zr3dx.
Sent from my PG86100 using Tapatalk 2
Wikd said:
Right, I've done that on accident before. What I'm saying is, don't flash the new hboot until after the Rom flash. I go from zr3dx to venom all the time with no computer. They require different hboots. This is how I do it.
Let's say I'm on zr3dx with hboot 1.4 and I want to go to venom. I'll rename my "158hbootPG86IMG.zip" to PG86IMG first. then I go to recovery and flash venom, then I reboot to bootloader from recovery and it'll flash the hboot 1.58. It boots up and I promptly rename it back to "158hbootPG86IMG.zip".
If I want to go back to zr3dx I just do the same process with the 1.4 hboot that's on my sd and flash zr3dx.
Sent from my PG86100 using Tapatalk 2
Click to expand...
Click to collapse
That was the answer I was looking for thank you very much!!! I hope this helps other people as this may become a very common problem...
Now if I can just remember the correct order...lol thanks again.
bpc4209 said:
That was the answer I was looking for thank you very much!!! I hope this helps other people as this may become a very common problem...
Now if I can just remember the correct order...lol thanks again.
Click to expand...
Click to collapse
Glad to help, I kind of thought my 1st answer wasn't enough info, that's why I asked if it answered your question.
Sent from my PG86100 using Tapatalk 2
Here is where I am with my phone.
Shooter XC Ship S-OFF RL
HBOOT-1.40.1100
RADIO-0.97.10.0530
Rooted
clockworkmod
Cool Sense v11
-----------------------------------------
I am hoping that I am not the only one that has NO idea what to do with the HBOOT and what HBOOT I need or should be running.
So here are a few questions I hope other have. I guess things have changed a bit since I was on my EVO 4G?
Seeing that for now I am on a ICS rom, will it hurt to upgrade my HBOOT?
Will I lose anything by upgrading my HBOOT?
Can I run ICS and JB ROMS on the new HBOOT?
What is the HBOOT really? (help me understand it a little)
Can I run ANY recovery with any HBOOT?
HBOOT anf KERNEL's, do they play nice?
---------------------------------------------------------
Here is the deal, I want to jump to a JB rom as soon as one is fully working, and want to try out the new Cool Sense v11 but I think being on the old HBOOT is giving me boot loops, but even if not I want to understand them a little more and know if I should upgrade it.
Thanks for filling me in a bit!
Its not the hboot that gives bootloop. its the firmware. You are S-off so hboot doesnt really matter.
http://d-h.st/Mf1
put in sdcard. reboot to bootloader and accept update.
will wipe data so make a backup.
As for the recovery try 4EXT. best out there for evo 3d
and as for JB try agrabrens Disarmed Toaster. still a few bugs but really smooth
EM|NEM said:
Its not the hboot that gives bootloop. its the firmware. You are S-off so hboot doesnt really matter.
http://d-h.st/Mf1
put in sdcard. reboot to bootloader and accept update.
will wipe data so make a backup.
As for the recovery try 4EXT. best out there for evo 3d
and as for JB try agrabrens Disarmed Toaster. still a few bugs but really smooth
Click to expand...
Click to collapse
Whoa!
That PG86IMG.zip file looks like a complete set of firmware for a GSM phone and the OP clearly has a CDMA phone.
And much testing on the Evo 3D CDMA model has proven that the version of the bootloader installed, not just the rest of the firmware, can cause booting problems. The bootloader is actually part of the firmware and works in conjunction with the other firmware to write and erase partitions, in addition to the other functions it performs.
ramjet73
Sorry, should of said I am cdma (Sprint)
Sent from my PG86100 using xda premium
OP, I was in the same situation as you until yesterday. Now I'm latest hboot and unlocked (still s-off)
I took the advice in Tribulattifather's rom on the last page. Jbear's cdma ics hboot and latest 1.58 yesterday and I'm G2G. No issues whatsoever. Also if you're s-off you can change hboot anytime you likely. PM me if you need more info but its simple even for me who has half a brain
Edit
Here's more
http://forum.xda-developers.com/showthread.php?t=1885108
oops.. sorry my bad :S
should have realized that *facepalm*
I'm sure the hboot does matter but i was just saying that its not really a requirement to have the latest hboot to run JB,kernels or recoveries. I have the revolutionary hboot and havn't had any problems with the latest roms/kernels.
EM|NEM said:
oops.. sorry my bad :S
should have realized that *facepalm*
I'm sure the hboot does matter but i was just saying that its not really a requirement to have the latest hboot to run JB,kernels or recoveries. I have the revolutionary hboot and havn't had any problems with the latest roms/kernels.
Click to expand...
Click to collapse
I guess the GSM and CDMA models are a little different in that respect, since the most recent Sprint ICS 1.58 bootloader has problems booting GB and AOSP ROM's on the CDMA model. The older hboots do run those ROM's.
ramjet73
So I should. . .
Use this HBOOT
http://forum.xda-developers.com/showpost.php?p=30014044&postcount=7
PG86IMG_1.58-hboot.zip
This Recovery
http://forum.xda-developers.com/showthread.php?t=1561999
and I will be ok to run most, ICS or JB ROM?
Anymore I am only half sure what is going on, lol in the old days you could just flash away.
And thanks everyone!!!
Really, I am not sure if I have to do it in order or if it matters?
Also, I see 4ext will not let you update firmware or the radio. . . How do I know if I have the ones I should have. . ?
If coolexe's rom is using the new kernel, then the 1.4 hboot is causing the issue. You would need the 1.58 hboot.
1.58 hboot: needed to flash anything with the latest kernel. Can flash any sense based ics rom. Cannot flash AOSP, CM, or GB roms.
1.4 hboot: Can flash any custom rom except ones that use the new kernel.
No recovery can flash hboots or firmware , but since you are s-off, you can flash either hboot at will in the bootloader. You can also update to the latest firmware using freeza's 2.89 zip available in the development thread.
I think that answers all your questions, but if not, please reply.
Read, Search, Read again, ... Then Ask with Tapatalk 2
coal686 said:
If coolexe's rom is using the new kernel, then the 1.4 hboot is causing the issue. You would need the 1.58 hboot.
1.58 hboot: needed to flash anything with the latest kernel. Can flash any sense based ics rom. Cannot flash AOSP, CM, or GB roms.
1.4 hboot: Can flash any custom rom except ones that use the new kernel.
No recovery can flash hboots or firmware , but since you are s-off, you can flash either hboot at will in the bootloader. You can also update to the latest firmware using freeza's 2.89 zip available in the development thread.
I think that answers all your questions, but if not, please reply.
Read, Search, Read again, ... Then Ask with Tapatalk 2
Click to expand...
Click to collapse
That about does it, just one more thing that I am not to clear on. How is the firmware different than a ROM?
chaos67731 said:
That about does it, just one more thing that I am not to clear on. How is the firmware different than a ROM?
Click to expand...
Click to collapse
Technically it could all be considered firmware since it is all flashed to the NAND memory of the phone, and an RUU.exe flashes all of it, but generally people think of the boot, system and data partitions as the "ROM" and more as software than firmware. The system and data partitions are also modified during normal operation which is generally not true of the firmware partitions. The "firmware" consists mostly of the bootloader, radios and low level functions similar to BIOS on a PC, and it gets flashed to different partitions.
ramjet73
This is going to be a short and simple guide for S-OFF users that want to update to the current RUU level or refresh their phone because they are having issues like being unable to boot certain ROM's. You will not lose S-OFF by flashing the RUU.
1. Do a nandroid backup of your current ROM if you want to restore it later.
2. Download the current version of the RUU for your phone in exe or zip format from this page.
3. Run the exe version of the RUU in Windows or the zip version as a PG86IMG.zip file through the bootloader. If using the bootloader method make sure the file is named exactly "PG86IMG.zip" and placed in the root of your SD card before starting the bootloader.
There is no need to unlock the bootloader before running it if you are S-OFF and there is troubleshooting information in this post if you have problems. It may be necessary to run the RUU twice if you have a custom bootloader installed when it is run the first time. If the utility hangs after flashing the bootloader from Windows just cancel it and restart.
I recommend downloading and installing the OTA(s) immediately after flashing the RUU to get the most current firmware while still 100% stock, but the OTA firmware update(s) can be downloaded as a separate PG86IMG.zip file if you forget or can't do that for some reason.
4. Flash a custom hboot using the instructions in this post. My recommendation for a good general purpose hboot is the JBear GB 1.50.5050 version unless you are running an ICS Sense ROM like stock or Cool ICS that requires an ICS bootloader (1.57.xxxx or 1.58.xxxx).
5. Connect your phone to a PC and start the bootloader in "fastboot USB " mode, then issue the following command to flash your favorite recovery:
fastboot flash recovery recovery.img (where "recovery.img" is the name of the recovery file in your ADB/fastboot directory)
6. Boot into recovery and restore a nandroid or flash another custom ROM. You may have to wipe cache+dalvik and restart recovery if you get any error messages from the recovery program.
That's it. You're now updated or re-synced with the current firmware, the hboot that meets your requirements and your favorite recovery.
Here are some additional links that might be helpful:
4EXT Recovery OP for the Evo 3D CDMA thread with a direct link to recovery.img in the download section (not the most current version)
Current TeamWin (TWRP2) touch recovery for the CDMA Evo 3d.
Virgin Mobile OTA firmware only in PG86IMG.zip format.
Sprint OTA firmware only in PG86IMG.zip format.
ramjet73
Thanks for this.
Question,the RUU links...
Am I looking for the link with the radio he has currently on his phone?
0.97.10.0530?
3volution said:
Thanks for this.
Question,the RUU links...
Am I looking for the link with the radio he has currently on his phone?
0.97.10.0530?
Click to expand...
Click to collapse
No. That's an older GB level and the most current RUU for the Evo 3D is the 2.89.651.2 ICS version. That's the one I recommend.
Since he is S-OFF already it's easy to revert to a GB RUU if neccessary.
ramjet73
I better not mess with it,lol
This isn't anything like flashing new ROM's on my phone.
Thanks though.
3volution said:
I better not mess with it,lol
This isn't anything like flashing new ROM's on my phone.
Thanks though.
Click to expand...
Click to collapse
You're welcome.
It's not really that difficult if you are familiar with rooting and flashing HTC devices but I can understand how it might be for users coming from other brands. Samsung in particular is definitely less complicated.
ramjet73
Thanks!
Thanks for this great post ramjet. Really a great concise How-to.
Nevermind, fixed.
ramjet73 said:
No. That's an older GB level and the most current RUU for the Evo 3D is the 2.89.651.2 ICS version. That's the one I recommend.
Since he is S-OFF already it's easy to revert to a GB RUU if neccessary.
ramjet73
Click to expand...
Click to collapse
I flashed the above RUU .exe and I'll get to 10%, then my phone reboots (RUU program says "attaining bootloader" or something) and go into a bootloop. Is there a specific hboot necessary to run this. I am on 1.04.200 and s-off, 1.09.00.706
I also tried updating via the bootloader method as well..... runs well....updates like four of the ten check offs and then bootloops as well.
Edit: turns out I was flashing the wrong version, oops
Hedied4me said:
I flashed the above RUU .exe and I'll get to 10%, then my phone reboots (RUU program says "attaining bootloader" or something) and go into a bootloop. Is there a specific hboot necessary to run this. I am on 1.04.200 and s-off, 1.09.00.706
Click to expand...
Click to collapse
From experience I've discovered that the RUU.exe utility will sometimes stop after flashing the stock bootloader if it is run with a custom hboot installed, which is why I put this comment in the OP:
If the utility hangs after flashing the bootloader from Windows just cancel it and restart.
Click to expand...
Click to collapse
I've had no problem completing the RUU.exe flash if I just cancel the utility in the Windows task manager and restart it.
Others have reported that re-flashing the RUU.zip file through the bootloader also works if the original flash is incomplete.
Also, make sure that you downgrade your hboot after flashing the RUU since the stock hboot won't boot GB or AOSP based ROM's.
ramjet73
Ok one more stupid question, after successfully flashing the correct RUU my phone boots into the stock virgin mobile. How do I get into bootloader (to flash OTA update and hboot) from here since holding power and volume down button from off no longer work.
Sent from my HTCEVOV4G using Tapatalk 2
Hedied4me said:
Ok one more stupid question, after successfully flashing the correct RUU my phone boots into the stock virgin mobile. How do I get into bootloader (to flash OTA update and hboot) from here since holding power and volume down button from off no longer work.
Click to expand...
Click to collapse
Try removing/replacing the battery and then use the Power+VolumeDown buttons together to enter the bootloader.
The stock ROM has the "fast boot" option turned on in the power settings by default and that will interfere if you try to enter the bootloader after powering down from the stock ROM.
ramjet73
Thank you very much for your patience and help Ramjet. Everything went well.
Sent from my Evo V 4G using Tapatalk 2
Please excuse me this might have been asked before.
I'm currently S-Off H-boot 1.40 but still on gingerbread firmware(2.17 radio 0.97.10.0530). also flashed to Boost Mobile. My question is if I run RUU to newest build will I lose boost mobile flash?
El Queson said:
Please excuse me this might have been asked before.
I'm currently S-Off H-boot 1.40 but still on gingerbread firmware(2.17 radio 0.97.10.0530). also flashed to Boost Mobile. My question is if I run RUU to newest build will I lose boost mobile flash?
Click to expand...
Click to collapse
I honestly don't know.
There is a post by a cricket user in my rooting and S-OFF guide that says the customization is not lost for that carrier but I've never used Boost and can't speak to that.
Perhaps another Boost user on these forums has experience with flashing the RUU.
ramjet73
++sorry++
Using the bootloader procedure is, by far, the easiest way of doing the RUU process that I've encountered. From custom ROM, to stock, back to a custom ROM in less than 45 minutes.
ramjet, thank you for your contributions to our platform.
so my wife is hboot 1.40, radio version 0.97.... running a GB ROM. I need to update her EVERYTHING(you pointed me here) and get her on NegaLite BluROM. I believe I will need to update her hboot as well. At what point in this process should that be done? Do I need to be worried that her current ROM is incompatible with either the new RUU or the new bootloader? And if it is, then I just work through it all in recovery?
Very useful thread, and thank you very much, by the way.
GAPO said:
so my wife is hboot 1.40, radio version 0.97.... running a GB ROM. I need to update her EVERYTHING(you pointed me here) and get her on NegaLite BluROM. I believe I will need to update her hboot as well. At what point in this process should that be done? Do I need to be worried that her current ROM is incompatible with either the new RUU or the new bootloader? And if it is, then I just work through it all in recovery?
Very useful thread, and thank you very much, by the way.
Click to expand...
Click to collapse
Is her phone S-OFF? If so, there is a link in the OP to a post that covers updating the hboot. If not, the only way to update the hboot is to flash a more current RUU.
ramjet73
ramjet73 said:
Is her phone S-OFF? If so, there is a link in the OP to a post that covers updating the hboot. If not, the only way to update the hboot is to flash a more current RUU.
ramjet73
Click to expand...
Click to collapse
Yes she is S-off. She also already has 4ext recovery installed.
Does this negate my need to flash recovery in the downloader?
Since she is S-off, this should be pretty easy.
I will still need to access the bootloader via Windows cmd, yes? Or can I accomplish all of this using only the handset?
Sent from my PG86100 using xda premium
---------- Post added at 07:07 PM ---------- Previous post was at 06:52 PM ----------
Her hboot is:
SHOOTER XC SHIP S-OFF RL
HBOOT-1.40.0000
RADIO-0.97.10.0530
eMMC-boot
Jun 8 2011, 17:20:22
Is this a custom hboot, or stock? I ask because of the caution on the OP regarding custom bootloaders. And I am not sure because I changed her bootloader a week or so ago and had to change it back.
Sent from my PG86100 using xda premium
GAPO said:
Is this a custom hboot, or stock? I ask because of the caution on the OP regarding custom bootloaders. And I am not sure because I changed her bootloader a week or so ago and had to change it back.
Click to expand...
Click to collapse
That's a stock hboot so you should be fine. You can still update using the RUU if a custom hboot is installed, but it might take a restart to complete after the stock hboot is installed.
ramjet73