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
Related
Picked a 3D up on CL, clean ESN, $50, I couldn't pass it up. In great shape, so I'm a couple weeks into this, read, read, read, and managed to get the wire trick to work on 1.58 so I'm S-Off. Now what?
I guess my main question is, I'm reading S-off trumps all, but how exactly does your HBOOT version affect what ROMs you can load? Is it tied to Kernel basically? Or the base the ROM works on?
This hasn't been so clear in my search education.
I'm running Trib's SolidROM ver 2.1, at the moment (which is stellar), but I'm a flashaholic in need of a fix every few days... and there are so many options, but I can't seem to see the forest for the trees...
Thanks in advance. This place rocks.
trouinky said:
Picked a 3D up on CL, clean ESN, $50, I couldn't pass it up. In great shape, so I'm a couple weeks into this, read, read, read, and managed to get the wire trick to work on 1.58 so I'm S-Off. Now what?
I guess my main question is, I'm reading S-off trumps all, but how exactly does your HBOOT version affect what ROMs you can load? Is it tied to Kernel basically? Or the base the ROM works on?
This hasn't been so clear in my search education.
I'm running Trib's SolidROM ver 2.1, at the moment (which is stellar), but I'm a flashaholic in need of a fix every few days... and there are so many options, but I can't seem to see the forest for the trees...
Thanks in advance. This place rocks.
Click to expand...
Click to collapse
Well there are very few rom's that are compatible with the 1.58 hboot so if your a flashoholic then you better off going to hboot 1.40 since with 1.40 hboot you can run both ICS & GB. GB has better compatibility in fact it can only play the 3d games and older gameloft games.
If you downgrade to a lower hboot please let me know how it went because I am thinking of upgrading to 1.58 to try out a new rom but I am afraid to because I am already s-off hboot 1.4.
trouinky said:
Picked a 3D up on CL, clean ESN, $50, I couldn't pass it up. In great shape, so I'm a couple weeks into this, read, read, read, and managed to get the wire trick to work on 1.58 so I'm S-Off. Now what?
I guess my main question is, I'm reading S-off trumps all, but how exactly does your HBOOT version affect what ROMs you can load? Is it tied to Kernel basically? Or the base the ROM works on?
This hasn't been so clear in my search education.
I'm running Trib's SolidROM ver 2.1, at the moment (which is stellar), but I'm a flashaholic in need of a fix every few days... and there are so many options, but I can't seem to see the forest for the trees...
Thanks in advance. This place rocks.
Click to expand...
Click to collapse
90% sure of the following information.
Roms that are based directly on the Sprint ICS OTA require 1.58, some roms have used some tricks to let it run on 1.50 like SolidROM did.
1.58 for you means u can flash any ROM and not bootloop.
S-OFF means u can flash a rom FULLY, some of these ROMS have custom Kernels, and without flashing the kernel u get bootloops. u can also add your own Kernel.
so in conclusion your in good shape. u can flash Gingerbread- VM ICS - sprint ICS.
just be sure to stay away from changing your HBOOT, especially any VM firmware!
Hboot 1.58: Can load the new ICS kernel and all sense ICS ROMs. Cannot load AOSP and GB ROMs.
Hboot 1.4 (and others): Can load most ROMs (sense with vm leak kernel, GB, AOSP). Cannot load the new ICS kernel (or any ROM with that).
hboot 1.5 s-off
How can I go back to my original hboot 1.5 s-off, the other day I flashed MeanROM ICS v2.6 and upgrade my hboot to 1.58, for the 2.89 kernel
I also try out SOS M | VER 2.6, and ZR3DX-Sense 3.6, wifi teather will not work on none of those roms, any one know how to get the teathering working. I'm thinking of going back to hboot 1.5 s-off any one know how to go back to 1.5 s-off.
cc2278 said:
How can I go back to my original hboot 1.5 s-off, the other day I flashed MeanROM ICS v2.6 and upgrade my hboot to 1.58, for the 2.89 kernel
I also try out SOS M | VER 2.6, and ZR3DX-Sense 3.6, wifi teather will not work on none of those roms, any one know how to get the teathering working. I'm thinking of going back to hboot 1.5 s-off any one know how to go back to 1.5 s-off.
Click to expand...
Click to collapse
Go to juopunutbear website and download hboot for GB. Rename to PG86IMG.zip and place at root of SD card. boot to boot loader. Select yes and then reboot. Don't forget to delete from SD card root!
Sent from my PG86100 using xda premium
plaidcounty said:
Go to juopunutbear website and download hboot for GB. Rename to PG86IMG.zip and place at root of SD card. boot to boot loader. Select yes and then reboot. Don't forget to delete from SD card root!
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
I'll try that thanks.
cc2278 said:
How can I go back to my original hboot 1.5 s-off, the other day I flashed MeanROM ICS v2.6 and upgrade my hboot to 1.58, for the 2.89 kernel
I also try out SOS M | VER 2.6, and ZR3DX-Sense 3.6, wifi teather will not work on none of those roms, any one know how to get the teathering working. I'm thinking of going back to hboot 1.5 s-off any one know how to go back to 1.5 s-off.
Click to expand...
Click to collapse
I answered you on the other place you posted this.
Read, Search, Read again, ... Then Ask with Tapatalk 2
plaidcounty said:
Go to juopunutbear website and download hboot for GB. Rename to PG86IMG.zip and place at root of SD card. boot to boot loader. Select yes and then reboot. Don't forget to delete from SD card root!
Click to expand...
Click to collapse
Thanks! This worked great. My research had me thinking the only way to do this was a ridiculously complex 15 step process.
I did the OTA update to ICS and hboot 1.58 and was trying to flash to PagePlus but ran into problems doing "APN Backup and Restore"; it's not allowed on ICS, I tried to go back to a gingerbread ROM but it kept bootlooping because I had hboot 1.58. Your advice got me back to hboot 1.50, then I installed an old cyanogenmod ROM, so I can do the APN backup.
Hey guys, my 3VO hasn't been acting right lately. I was having trouble booting Agrabrens latest CM10 build for CDMA, it bootlooped, but then i was able to run it again later without issue. Now my phone is having trouble running ICS based Sense roms, the roms bootloop. None of these roms have a 1.58 hboot requirement and i'm running eng hboot. Lately my phone only can run AOSP/AOSP based roms(except for at least one i've tried) without bootloops. Does anyone know what the problem could be?
Juanito216 said:
Hey guys, my 3VO hasn't been acting right lately. I was having trouble booting Agrabrens latest CM10 build for CDMA, it bootlooped, but then i was able to run it again later without issue. Now my phone is having trouble running ICS based Sense roms, the roms bootloop. None of these roms have a 1.58 hboot requirement and i'm running eng hboot. Laterly my phone only can run AOSP/AOSP based roms(except for at least one i've tried) without bootloops. Does anyone know what the problem could be?
Click to expand...
Click to collapse
Sounds like Sense is mad at you for trying AOSP ROM's.
I'm assuming you are S-OFF since you mentioned the ENG bootloader, but have you flashed the 2.89.651.2 (Sprint ICS) firmware yet? My preference would be to flash the whole RUU if you haven't already and then reflash recovery, but there is a .zip file in Virus's OTA thread that contains only the firmware, including hboot 1.58, that can be flashed from your current bootloader. You can always go back to the ENG bootloader once you get past this problem.
ramjet73
Does your recovery bootloop as well? What recovery on are you on?
Details, details.
Mobilemodz said:
Does your recovery bootloop as well? What recovery on are you on?
Details, details.
Click to expand...
Click to collapse
Recovery wouldnt have anything to do with his bootloops unless you flashed the a mod, kernel, or theme that doesnt play nice with the Rom. Like ramjet said, its more than likely a firmware and or hboot issue. Go with ramjet and try his solution.
ramjet73 said:
Sounds like Sense is mad at you for trying AOSP ROM's.
I'm assuming you are S-OFF since you mentioned the ENG bootloader, but have you flashed the 2.89.651.2 (Sprint ICS) firmware yet? My preference would be to flash the whole RUU if you haven't already and then reflash recovery, but there is a .zip file in Virus's OTA thread that contains only the firmware, including hboot 1.58, that can be flashed from your current bootloader. You can always go back to the ENG bootloader once you get past this problem.
ramjet73
Click to expand...
Click to collapse
Thanks bro, flashing the newest boot helped. Iinm I used Viruses zip. Now I'm back on eng hboot.
Sent from my PG86100 using Tapatalk 2
damn im in the same boat right now, tried virus zip and no luck......continuous boot loop.
riassan said:
damn im in the same boat right now, tried virus zip and no luck......continuous boot loop.
Click to expand...
Click to collapse
Edit: for this puppy back in business has to flash full ruu as you mentioned ramjet73 and not I'm 1.58 s-off locked, which really doesn't matter since I can just flash PG86IMG and go back to eng hboot.
Sent from my Galaxy Nexus using xda premium
ooooook...this'll either get me killed or contented.
here goes.
the first part of this i basically stole from sullivan's post over at mik's.
there was no answer to his question...
there are too many guides, tutorials and suggested methods that I can't chose the right one to narrow it down...
i'm asking the same manner of question...
<<<<<
EVO 3d
sprint
-Revolutionary-
SHOOTER XC SHIP S-OFF RL
HBOOT 1.40.1100
RADIO-1.06.00.1216
eMMC-boot
Jun 8 2011,17:20:22
hardware 002
running smooth criminal (chose a random sense rom to update pri.prl)
kernel version is 3.0.50-ck1 butteredtoast ics rls 12.2+
Build # is 2.89.651.2 CL409645 release-keys
PRI Version 1.42_003
PRL Version 21090
i used htc unlock and closeone's toolkit.
was using mikvirgin for a while. vm leak without problems. couldn't update pri.prl
changed a few things here and there...then, i started having heat and drain issues. notably from browsing and swype beta.
figured it was time for a clean slate and new rom.
From what I've gathered I need an ics hboot, ie, 1.58 in order to run ics kernels the right way??
What should i do to be current??
start by updating my radio. (where's the latest file?)
should i upgrade hboot? 1.58?
Do I need to relock, ruu, then unlock again? (what method is most recent and where)
i thought i read that i can just change my hboot on its own and then also bootload the latest radio?
ideally, i'd love to be able to run a few aosp jb roms...cm 10...as well as any ics roms without issue.
also, is the deal with ext3 versus ext4 still the same? ext4 can't run sense roms...or, was that only for the evo4g?
>>>>>>>>>>>>>
advice would be considered a thankable and appreciated offense!
many, many thanks, everyone.
i need to head to bed.
clear my brain a bit.
between ramjet's and mpgrimm2's threads...i'm going into overload.
but, thanks. seriously. you guys rock.
--------------------------------------------------------------
what? you think just cause a guy reads comics he can't kick some a$$?
I would relock the bootloader and run the Sprint ICS ruu.exe. This will update you to the latest firmware, radio, hboot, etc, but you'll still be s-off. Then downgrade your hboot to 1.4 or 1.04 and install a custom recovery like 4ext. You should then be ready to install a custom Rom.
coal686 said:
I would relock the bootloader and run the Sprint ICS ruu.exe. This will update you to the latest firmware, radio, hboot, etc, but you'll still be s-off. Then downgrade your hboot to 1.4 or 1.04 and install a custom recovery like 4ext. You should then be ready to install a custom Rom.
Click to expand...
Click to collapse
i'm thinking running the ruu might be the way to go, too.
(if anyone would like to point me in the direction of the latest ruu "how-to" thread...much appreciated)
however, i'm not quite sold on the idea of downgrading hboot back to what i have (or, another 1.4 variation).
as per ramjet's thread on the subject...even the most flexible hboot "eng hboot" has issues with compatibility running 2.89 based kernels.
the ones that run ics and above are the 1.58 hboots and it's variables.
so, anyone have ideas as to what my specs should be to successfully run a cm 10 based rom and kernel successfully?
not to mention that i'd like to continue to swap into a sense based rom every now and again.
that leads me back to the ext3 vs ext4 question.
is ext4 still not a viable ext for sense based roms or was that only for the evo 4g?
thanks again, coal!
cipher77 said:
i'm thinking running the ruu might be the way to go, too.
(if anyone would like to point me in the direction of the latest ruu "how-to" thread...much appreciated)
however, i'm not quite sold on the idea of downgrading hboot back to what i have (or, another 1.4 variation).
as per ramjet's thread on the subject...even the most flexible hboot "eng hboot" has issues with compatibility running 2.89 based kernels.
the ones that run ics and above are the 1.58 hboots and it's variables.
so, anyone have ideas as to what my specs should be to successfully run a cm 10 based rom and kernel successfully?
not to mention that i'd like to continue to swap into a sense based rom every now and again.
that leads me back to the ext3 vs ext4 question.
is ext4 still not a viable ext for sense based roms or was that only for the evo 4g?
thanks again, coal!
Click to expand...
Click to collapse
This post was for a user in a situation similar to yours. It's basically what coal suggested and you can use my guide through Step2, but there is no need to relock the bootloader since you are S-OFF.
If your case, you might want to flash the ENG or JBear 1.50.5050 bootloader after running the RUU.exe since both of those will flash and run GB, ICS and JB ROM's except for a few Sense ROM's that require the stock 1.58 or JBear 1.58.5858 bootloader.
As far as EXT3 versus EXT4 goes, most current Sense and AOSP ROM's support both, but I usually just "format all partitions except SD card" in 4EXT recovery before flashing a ROM and let it default to that (EXT4) or whatever format the dev configured for the ROM. I just checked the nandroids on my SD card and they are all in the EXT4 format.
ramjet73
IMO, you should just update your radio (if you can find the latest PG86IMG.zip) or get the one from virus's thread which contains the latest hboot too. Then to install CM10 ROM downgrade back to eng hboot or 1.4 you should be able to run CM10 ROMs just fine. And if you want sense 3.6 ROM, you can try smoothcriminal ROM after updating your radio. It works with all hboots.
RUU vs OTA vs firmware zip file
mnomaanw said:
IMO, you should just update your radio (if you can find the latest PG86IMG.zip) or get the one from virus's thread which contains the latest hboot too. Then to install CM10 ROM downgrade back to eng hboot or 1.4 you should be able to run CM10 ROMs just fine. And if you want sense 3.6 ROM, you can try smoothcriminal ROM after updating your radio. It works with all hboots.
Click to expand...
Click to collapse
There's some good information about flashing an RUU versus taking an OTA in this thread on the HTC Desire forum, and flashing the firmware zip updates even less than taking the OTA. I've attached screen shots of the contents of virus's firmware zip file versus the RUU rom.zip file from the same build (Sprint ICS 2.89.651.2). As you can see, even discounting the boot, system, and data partitions, there's more that gets updated with the RUU than what's contained in the firmware .zip, which is why I recommend starting with an RUU flash (.exe or .zip) when upgrading to a new build.
ramjet73
ramjet73 said:
There's some good information about flashing an RUU versus taking an OTA in this thread on the HTC Desire forum, and flashing the firmware zip updates even less than taking the OTA. I've attached screen shots of the contents of virus's firmware zip file versus the RUU rom.zip file from the same build (Sprint ICS 2.89.651.2). As you can see, even discounting the boot, system, and data partitions, there's more that gets updated with the RUU than what's contained in the firmware .zip, which is why I recommend starting with an RUU flash (.exe or .zip) when upgrading to a new build.
ramjet73
Click to expand...
Click to collapse
Although mnomaanw makes a great point, I agree with ramjet on this one. My phone recently decided not to let me install ANY CM, GB, or JB based ROMs. The only ones that would successfully boot were Sense 3.6 and 4.0 based ICS ROMs. The rest would show my splash screen and then the phone would bootloop before even the boot ani showed. I tried to flash different radios, hboots, firmware, etc to no avail. Finally, I ran the ruu.exe, downgraded my hboot to 1.4 Revolutionary to try the MIUI ROM everyone is raving about and installed 4ext custom recovery. Everything is running great now.
I can confirm that it does more than just the firmware zip updates as it wiped my custom splash screen I had installed. Going through the hassle of running the ruu is worth it if you want to be sure that everything is completely updated properly.
ramjet73 said:
This post was for a user in a situation similar to yours. It's basically what coal suggested and you can use my guide through Step2, but there is no need to relock the bootloader since you are S-OFF.
If your case, you might want to flash the ENG or JBear 1.50.5050 bootloader after running the RUU.exe since both of those will flash and run GB, ICS and JB ROM's except for a few Sense ROM's that require the stock 1.58 or JBear 1.58.5858 bootloader.
As far as EXT3 versus EXT4 goes, most current Sense and AOSP ROM's support both, but I usually just "format all partitions except SD card" in 4EXT recovery before flashing a ROM and let it default to that (EXT4) or whatever format the dev configured for the ROM. I just checked the nandroids on my SD card and they are all in the EXT4 format.
ramjet73
Click to expand...
Click to collapse
first off...
huge, huge thanks for the responses, guys.
so, yeah...i've actually been using 4ext as my recovery for a while now. i have to say...it's quite good.
however, i always have wondered what the deal was with ext3 vs ext4. clearing that up more definitively than what i've been able to find on my own, as well as my own experiences, is great.
sounds like i'll be running the ruu executable.
just to confirm...already being s-off means that i don't have to relock my bootloader, yeah?
excellent. one less step.
as for the hboot...this seems to be where it gets tricky.
ramjet...you suggested downgrading hboot after the ruu flash to ENG or 1.50.5050.
i'm definitely dumb to NOT take your advice...so, i will. more than likely the 1.50.5050 hboot. seems to be more likely to play well with 2.89 kernels. otherwise, i'd do the ENG hboot.
from your thread, you mention that the only ones that DO run 2.89 based kernels are stock (1.58) and jbear's (1.58.5858).
do you think ENG hboot will be pliable enough at any point to be compatible with them? THAT would be pretty great.
thanks again, gang.
--------------------------------------------------------------
what? you think just cause a guy reads comics he can't kick some a$$?
cipher77 said:
ramjet...you suggested downgrading hboot after the ruu flash to ENG or 1.50.5050.
i'm definitely dumb to NOT take your advice...so, i will. more than likely the 1.50.5050 hboot. seems to be more likely to play well with 2.89 kernels. otherwise, i'd do the ENG hboot.
from your thread, you mention that the only ones that DO run 2.89 based kernels are stock (1.58) and jbear's (1.58.5858).
do you think ENG hboot will be pliable enough at any point to be compatible with them? THAT would be pretty great.
Click to expand...
Click to collapse
Unfortunately, there is no hboot that will run all Evo 3D CDMA ROM's but there are only three ROM's that I know require 1.58 or JBear 1.58.5858 at this time and that's the Sprint ICS stock ROM, Cool ICS and Viper3D. Some ROM developers have incorporated the "VM leak" kernel in place of the stock Sprint ICS 2.89(.651.2) kernel just to avoid that requirement. The reason I'm recommending JBear GB (1.50.5050) or the engineering (ENG-1.04) bootloader at this point is that there are far more ROM's that can be flashed and run with those than the 1.58.x versions, and they both support the fastboot commands that would normally require an unlocked bootloader.
ramjet73
ramjet73 said:
Unfortunately, there is no hboot that will run all Evo 3D CDMA ROM's but there are only three ROM's that I know require 1.58 or JBear 1.58.5858 at this time and that's the Sprint ICS stock ROM, Cool ICS and Viper3D. Some ROM developers have incorporated the "VM leak" kernel in place of the stock Sprint ICS 2.89(.651.2) kernel just to avoid that requirement. The reason I'm recommending JBear GB (1.50.5050) or the engineering (ENG-1.04) bootloader at this point is that there are far more ROM's that can be flashed and run with those than the 1.58.x versions, and they both support the fastboot commands that would normally require an unlocked bootloader.
ramjet73
Click to expand...
Click to collapse
gotcha.
makes sense that devs would swap out the vm leak just to avoid the hassle.
thanks for the info, btw.
about to flash the ruu from your qaderso zip.
not having to relock before doing the flash is nice.
thanks again for all of your help.
i'll report back with success...or, hang ups.
update...
just wanted to check in.
i went ahead and ran the ruu.exe without any issues.
since i was already s-off and unlocked via htc...i didn't bother relocking.
once the ruu did its thing it changed the hboot to stock and the previous REVOLUTIONARY in the bootloader header disappeared and it just read UNLOCKED.
not sure if this was right...but, i didn't have to unlock again.
i stayed s-off AND unlocked after the ruu.
i re-ran the ruu later in the day since staying s-off and unlocked didn't sit well with me after the intial run. but, the result was the same.
so, i'm all good, i suppose.
any takers?
installed SU, reinstalled 4ext (had been using it successfully for a while now. great recovery.) and busybox.
then, something strange happened.
rather, something i didn't expect.
after changing the hboot to 1.50.5050 via bootloader...
as instructed...i powered down.
extracted the zip from the root so i wouldn't be in a bootloop.
but, it still wouldn't load the stock rom.
is that weird? or, expected?
i actually had to reinstall via recovery another sense rom.
otherwise, i think everything's going well.
waiting to get some time to flash a cm10 rom at this point.
unless someone thinks otherwise!
thanks again...
cipher77 said:
then, something strange happened.
rather, something i didn't expect.
after changing the hboot to 1.50.5050 via bootloader...
as instructed...i powered down.
extracted the zip from the root so i wouldn't be in a bootloop.
but, it still wouldn't load the stock rom.
is that weird? or, expected?
i actually had to reinstall via recovery another sense rom.
otherwise, i think everything's going well.
waiting to get some time to flash a cm10 rom at this point.
unless someone thinks otherwise!
thanks again...
Click to expand...
Click to collapse
That's normal. As a reminder, I'll quote from a post I made earlier in this thread:
ramjet73 said:
Unfortunately, there is no hboot that will run all Evo 3D CDMA ROM's but there are only three ROM's that I know require 1.58 or JBear 1.58.5858 at this time and that's the Sprint ICS stock ROM, Cool ICS and Viper3D.
Click to expand...
Click to collapse
The stock 2.89.651.2 ROM is in fact one of the few that currently require the 1.58 bootloader. That's why my guide recommends installing the JBear 1.58.5858 bootloader by default since the RUU installs the stock ICS ROM.
Also, the reason your bootloader shows unlocked is probably because you htcdev unlocked it before doing the hboot 1.4 downgrade for S-OFF. I've never done that method myself, but in discussing it with mpgrimm2, apparently the downgrade method doesn't reset the bootloader status to locked like the JupunutBear (wire trick) method does.
ramjet73
ramjet73 said:
That's normal. As a reminder, I'll quote from a post I made earlier in this thread:
The stock 2.89.651.2 ROM is in fact one of the few that currently require the 1.58 bootloader. That's why my guide recommends installing the JBear 1.58.5858 bootloader by default since the RUU installs the stock ICS ROM.
Also, the reason your bootloader shows unlocked is probably because you htcdev unlocked it before doing the hboot 1.4 downgrade for S-OFF. I've never done that method myself, but in discussing it with mpgrimm2, apparently the downgrade method doesn't reset the bootloader status to locked like the JupunutBear (wire trick) method does.
ramjet73
Click to expand...
Click to collapse
RE: hboot bootloop...doy! consider me FACEPALMED.
maybe, RAM-PALMED!
hell, i probably read over that line twenty times and never really READ it.
so, thanks again.
either way, since not many will stay on stock soft or stock hboot...i suppose it's not really an issue.
change hboot and change rom.
but, it did give me a scare for a minute.
as for the lock versus unlock...your guess is as good as, if not infinitely better, than mine.
everything definitely works, tho.
appreciate you seeing this through and checking in on me, btw.
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
I could not load what i believe is newer (ICS) roms. My phone would restart after the loading screen. so i did the s-off thing and i could now run ics roms.
now. i need to access the # codes. only one of them works. If i try older roms, including the backup from when i first rooted the phone, it gets to sense, then resets after a second or two.
is this because of S-OFF?
how can i undo the S-OFF so i can put my stock rom back on and access the # codes.
thanks for the help
No its not because of s-off.
What is your current hboot version?
What rom are you using now?
And your backup was ICS or Gingerbread?
If you want to boot a Gingerbread ROM you need to be on older hboot.
What is the code that you want to try?
I guess almost all Gingerbread dialer codes should work on sense based ICS rom.
mnomaanw said:
No its not because of s-off.
What is your current hboot version?
What rom are you using now?
And your backup was ICS or Gingerbread?
If you want to boot a Gingerbread ROM you need to be on older hboot.
What is the code that you want to try?
I guess almost all Gingerbread dialer codes should work on sense based ICS rom.
Click to expand...
Click to collapse
hboot is 1.58
iv tried several roms including my original backup.
i believe backup was gingerbread. what the phone came with 2 years ago.
only one of hte codes worked. i dont know which ones specificialy i need
for soem reason they jsut dont work on ics roms
i assumed it was s-off because s-on was what kept me from running ics
What are you trying to do?
birddseedd said:
hboot is 1.58
iv tried several roms including my original backup.
i believe backup was gingerbread. what the phone came with 2 years ago.
only one of hte codes worked. i dont know which ones specificialy i need
for soem reason they jsut dont work on ics roms
i assumed it was s-off because s-on was what kept me from running ics
Click to expand...
Click to collapse
You have hboot 1.58, so you have a Sprint evo 3d.. so you need hboot 1.4 or 1.5 or eng hboot or revolutionary hboot or jb 1.50.5050 to boot you gingerbread backup. Just download and try few of these by renaming them to PG86IMG.zip and installing through bootloader. If the backup is almost 2 year old try revolutionary or 1.40 hboot.
And what recovery are you using now? Back then there was no touch recoveries. Only non touch cwm. So the backup is most likely made from that recovery. I don't know whether your current recovery restores it correctly or not.
And what exactly are you trying to do? Most codes work on Sense based ICS roms.
mnomaanw said:
You have hboot 1.58, so you have a Sprint evo 3d.. so you need hboot 1.4 or 1.5 or eng hboot or revolutionary hboot or jb 1.50.5050 to boot you gingerbread backup. Just download and try few of these by renaming them to PG86IMG.zip and installing through bootloader. If the backup is almost 2 year old try revolutionary or 1.40 hboot.
And what recovery are you using now? Back then there was no touch recoveries. Only non touch cwm. So the backup is most likely made from that recovery. I don't know whether your current recovery restores it correctly or not.
And what exactly are you trying to do? Most codes work on Sense based ICS roms.
Click to expand...
Click to collapse
I dont know exactly which codes. but i know that only one of them worked.
basically i want to downgrade hboot and turn S-ON. i THINK this is what i need to do to run a gingerbread rom and have access to the # codes i need that wouldnt work on multiple ics roms
If you turn back to s-on you won't be able to downgrade.
But with s-off you can upgeade/downgrade anytime.
Your gingerbread rom will boot on s-off. There are many cases of bricked devices while turning s-off to s-on which can be fixed but there's no reason for you to turn it s-on, is there?
i dont know. s-off is what i had to do when i coudl boot gignerbread and not ics, so im under the assumption that to run gingerbread and not ics i need s-on. if this is not the case then all i need to do is go back to hboot 1.4? can you point me in the direction of downgrading please?
birddseedd said:
i dont know. s-off is what i had to do when i coudl boot gignerbread and not ics, so im under the assumption that to run gingerbread and not ics i need s-on. if this is not the case then all i need to do is go back to hboot 1.4? can you point me in the direction of downgrading please?
Click to expand...
Click to collapse
There's a difference between assumption and fact...
When you first did s-off you had a Gingerbread ROM and not ics and it was able to boot.
Currently I am dual booting with one ICS rom and one gingerbread rom and I'm s-off and they both boot perfectly. ON S-OFF GINGERBREAD BOOTS WITHOUT ISSUES.
Download the hboot 1.40.zip from somewhere (cannot attach using phone right now and I'm too lazy to search ramjet73 post ) and rename it to PG86IMG.zip and put it on root of sdcard then reboot into bootloader, let it scan and it will ask to update.. Hit volume up key then power key and it will reboot but before it boots, remove battery as your current ROM is not going to boot on that hboot unless it uses vm kernel. Now remove memory card and delete/rename/move that file from your sdcard using a card reader. Then boot into recovery and restore your backup. Make sure you use the same recovery that you used to make the backup. Only use the HBOOT 1.40 if you have evo 3d from sprint.
.
.
.
If you dont want to do all these download RUU. Exe file made for your phone from shipped-roms.com and run it and follow the instructions, it will get you to stock rom and will unroot your phone. Your phone will be like new with stock recovery but still s-off. You can still flash custom recoveries and ROMs and hboots later.
that site seems to not have an ruu for me
mnomaanw said:
There's a difference between assumption and fact...
When you first did s-off you had a Gingerbread ROM and not ics and it was able to boot.
Currently I am dual booting with one ICS rom and one gingerbread rom and I'm s-off and they both boot perfectly. ON S-OFF GINGERBREAD BOOTS WITHOUT ISSUES.
Download the hboot 1.40.zip from somewhere (cannot attach using phone right now and I'm too lazy to search ramjet73 post ) and rename it to PG86IMG.zip and put it on root of sdcard then reboot into bootloader, let it scan and it will ask to update.. Hit volume up key then power key and it will reboot but before it boots, remove battery as your current ROM is not going to boot on that hboot unless it uses vm kernel. Now remove memory card and delete/rename/move that file from your sdcard using a card reader. Then boot into recovery and restore your backup. Make sure you use the same recovery that you used to make the backup. Only use the HBOOT 1.40 if you have evo 3d from sprint.
.
.
.
If you dont want to do all these download RUU. Exe file made for your phone from shipped-roms.com and run it and follow the instructions, it will get you to stock rom and will unroot your phone. Your phone will be like new with stock recovery but still s-off. You can still flash custom recoveries and ROMs and hboots later.
Click to expand...
Click to collapse
i cannot seem to find an attached zip
birddseedd said:
that site seems to not have an ruu for me
Click to expand...
Click to collapse
Are you sure that you have HTC SHOOTER AKA EVO 3D?
These are RUUs from sprint from 1st to last
1. Gingerbread http://shipped-roms.com/download.ph...0.0518_NV_SPCS_1.15_release_193503_signed.exe
2. Gingerbread http://shipped-roms.com/download.ph...530_NV_NV_SPCS_1.16_release_198109_signed.exe
3. Gingerbread http://shipped-roms.com/download.ph...08_NV_SPCS_1.31_003_release_208230_signed.exe
4. Gingerbread http://shipped-roms.com/download.ph...08_NV_SPCS_1.31_003_release_219445_signed.exe
5. Gingerbread http://shipped-roms.com/download.ph...216_NV_NV_spcs_1.42_release_233304_signed.exe
6. ICS http://shipped-roms.com/download.ph...06__NV_NV_SPCS_1.43_release_271101_signed.exe
These are for sprint evo 3d......And not gsm or virgin.
EDIT : I see you edited it yourself.
yep. that is my phone
ok im confused. i thought that sense and apex were just ui options? i chose sense with a ics rom and now ##3424#. im confsued.
birddseedd said:
ok im confused. i thought that sense and apex were just ui options? i chose sense with a ics rom and now ##3424#. im confsued.
Click to expand...
Click to collapse
yes
raptoro07 said:
yes
Click to expand...
Click to collapse
grr. that doesnt help. lol. so sense vs apex is more than the ui? it is actualy involved in the core of the os? or do each simply have different dialers?