I'd like to update to the new Stock ROM with Goodies- Questions....
1. Hotspot work on this ROM?
2. What firmware/Radio do I need for this or does any of that get updated automatically?
3. Is there a walk through instruction/video for this update...from such an old ROM?
I have:
Hboot 1.12.0000
S-on
Radio 1.02.12.0427
TWRP 2.1.8
Well to start you need to decide if you want to s- off or not. If you don't i believe you can update firmware with the 1.12 hboot.
I'd update the firmware in consecutive order from where you are now. You want the firmware zips without the hboot img
Then you can flash the new rom you want.
I would follow the directions for s- off personally. It makes things alot easier
Sent from my EVO using xda premium
NaterTots said:
Well to start you need to decide if you want to s- off or not. If you don't i believe you can update firmware with the 1.12 hboot.
I'd update the firmware in consecutive order from where you are now. You want the firmware zips without the hboot img
Then you can flash the new rom you want.
I would follow the directions for s- off personally. It makes things alot easier
Sent from my EVO using xda premium
Click to expand...
Click to collapse
If I turn the device into s-off, then I can use TWRP to update from zip files right?
I read that I don't want to jump firmware to the latest or I could brick the device. So I thought the process might look like this.
PLEASE CORRECT ME IF I'M WRONG:
1. LazyPanda ( http://forum.xda-developers.com/showthread.php?t=1737123 )
to "s-off" the device
2. Run zip for 2.13.651.1 OTA (which one though?)
....Reboot THEN
run zip for 3.16.651.3 OTA
So I don't brick it
http://themikmik.com/showthread.php...dio-Collection&p=220556&viewfull=1#post220556
3. Install Stock ROM with Goodies...
Am I missing something?
What about the radio (comes with the firmware?)? What's the deal with the boot.img or not (I don't see the firmware WITHOUT boot.img included)?
Lazy panda is not technically supported anymore, so not sure how much luck you'll have there, but I would say run the 3.15 RUU, then s-off with dirty racun .
Stock with goodies is using the 3.16 base, so once you're s-off you can update to that firmware/radio version via the bootloader...assuming you're coming from 3.15. Just make sure to flash the 3.16 zip without the tp img, or your touch screen won't work with any other base.
http://forum.xda-developers.com/showthread.php?t=1704612
Sent from my EVO LTE
premo15 said:
Lazy panda is not technically supported anymore, so not sure how much luck you'll have there, but I would say run the 3.15 RUU, then s-off with dirty racun .
Stock with goodies is using the 3.16 base, so once you're s-off you can update to that firmware/radio version via the bootloader...assuming you're coming from 3.15. Just make sure to flash the 3.16 zip without the tp img, or your touch screen won't work with any other base.
http://forum.xda-developers.com/showthread.php?t=1704612
Sent from my EVO LTE
Click to expand...
Click to collapse
OK. let me revise then
1. S-off through RUU 3.15, then use Dirty Racun
2. Then update through TWRP (do I need a specific version or do I HAVE to use the Hboot?) to 3.15, then reboot and change to 3.16 (without tp.img in it)
3. install new ROM stock with goodies 3.16
Do I have it now?
(sigh...my Sprint Epic 4G first gen, and my wife's Galaxy Note 2 are SOOO much less complicated than HTC stuff)
ZenInsight said:
OK. let me revise then
1. S-off through RUU 3.15, then use Dirty Racun
2. Then update through TWRP (do I need a specific version or do I HAVE to use the Hboot?) to 3.15, then reboot and change to 3.16 (without tp.img in it)
3. install new ROM stock with goodies 3.16
Do I have it now?
(sigh...my Sprint Epic 4G first gen, and my wife's Galaxy Note 2 are SOOO much less complicated than HTC stuff)
Click to expand...
Click to collapse
That's what I was saying in another thread. With samsung phones you just flash and reboot. With these HTC phones you have to update this downgrade that just to flash a rom. I came from a one X and you had to flash the boot.img every time you wanted to flash a rom/kernel/modem.
Sent from my SAMSUNG-SGH-I717
No. Dont s-off then run dirty racun. S-off is what dirty racun does. He's saying Use RUU to get to 3.15, THEN use dirty racun (as per their instructions).
Then STAY at 3.15. Uncles you wanna use a 3.16 sense ROM (which is no different than a 3.15 ROM). If you S-off and update to 3.16 firmware AND flash the 3.16 touch panel image (tp.IMG), you will not be able to use any ROMs that aren't sense 3.16. I would suggest leaving your firmware where it is, and try the ROM you want. Generally, you DO NOT need current firmware to run a current ROM. The two are mutually exclusive (firmware and ROM). I always rock old radios. Newer isn't always better.
From my Evo LTE, yup.
1. S-OFF with DirtyRacun (doesn't really matter which RUU you choose)
2. Install custom recovery through fastboot (latest TWRP should be fine, depending on the ROM you choose - you might need 2.4.0.0 or older if flashing a ROM with an outdated update binary)
3. Flash ROM of your choice.
4. Update to latest firmware using most recent zip from firmware thread (this is done through the bootloader, not recovery)
5. Profit.
I feel pretty stupid with how confusing this is.
So
1. Use dirty Racun to go to s-off
2. I already have TWRP 2.1.8 for installing zip updates (Can I leave that version or do I need to change it?),,,
3. Install 3,15 firmware (or install 3.16 but without the tp img or my touchscreen in recovery will be busted.
Also, once I go to 3.16 I can only use 3.16 ROMS in the future.
4. Install any ROM which automatically changes me to the latest radio (is that true?).
I want this one:
http://forum.xda-developers.com/showthread.php?t=1701117
but does that mean I HAVE to have 3.16 firmware to use a 3.16 ROM? Or can I just leave it at 3.15?
ZenInsight said:
I feel pretty stupid with how confusing this is.
So
1. Use dirty Racun to go to s-off
2. I already have TWRP 2.1.8 for installing zip updates (Can I leave that version or do I need to change it?),,,
3. Install 3,15 firmware (or install 3.16 but without the tp img or my touchscreen in recovery will be busted.
Also, once I go to 3.16 I can only use 3.16 ROMS in the future.
4. Install any ROM which automatically changes me to the latest radio (is that true?).
I want this one:
http://forum.xda-developers.com/showthread.php?t=1701117
but does that mean I HAVE to have 3.16 firmware to use a 3.16 ROM? Or can I just leave it at 3.15?
Click to expand...
Click to collapse
2. The S-OFF process involved flashing an RUU, which will replace TWRP with the stock recovery. So like I said, you will need to flash TWRP. Since I don't know if flex has updated the update binary in that ROM, I would flash TWRP 2.4.0.0.
3. Just flash the 3.16 firmware. I've taken out anything that would be of concern, so you can flash whatever ROMs you want.
4. Radio is part of the firmware.
Captain_Throwback said:
2. The S-OFF process involved flashing an RUU, which will replace TWRP with the stock recovery. So like I said, you will need to flash TWRP. Since I don't know if flex has updated the update binary in that ROM, I would flash TWRP 2.4.0.0.
3. Just flash the 3.16 firmware. I've taken out anything that would be of concern, so you can flash whatever ROMs you want.
4. Radio is part of the firmware.
Click to expand...
Click to collapse
Ok. I get it. I lose TWRP once I "s-off", so I have to put it back on.
Just flash 3.16...it doesn't matter anymore about the touchscreen, that's been fixed.
Radio is included in the 3.16 firmware, not the ROM.
Flash the Stock with goodies...and I'll be fine.
Phew.... I hope this is right.
Do not flash 3.16 firmware if you haven't already flashed 3.15 first. Will brick.
From my Evo LTE, yup.
scottspa74 said:
Do not flash 3.16 firmware if you haven't already flashed 3.15 first. Will brick.
From my Evo LTE, yup.
Click to expand...
Click to collapse
No, it won't. Otherwise I would've said so. You obviously haven't been reading the firmware thread .
scottspa74 said:
Do not flash 3.16 firmware if you haven't already flashed 3.15 first. Will brick.
From my Evo LTE, yup.
Click to expand...
Click to collapse
Funny you say that since 3.15 firmware was causing soft bricks with older hboots. The only problem with the latest update is that aosp roms are stuck with out touch screen support for now.
Captain_Throwback said:
No, it won't. Otherwise I would've said so. You obviously haven't been reading the firmware thread .
Click to expand...
Click to collapse
Alright. Guess I missed something. Last time I was in there , if you didn't do 3.15 prior to 3.16 you were hosed.
But I did see the firmware haus dropped that it was said would be OK regardless of 3.15 or not. Just hadn't seen anyone try it.
Definitely listen to Cap'n. He's the man when it comes to firmwares and radios.
From my Evo LTE, yup.
Okay, I wish I had read this before I did what I just did. My device seems to be bricked
Was running 1.22.651.3 and MeanROM-ICS-v65 and went to update things to JB. Updated using PJ75IMG_3.16.651.3_firmware in HBOOT and now the screen won't turn on and none of the LEDs light up when plugged in. The device manager shows QHSUSB_DLOAD when it's plugged into the PC.
Any way to unbrick this?
(insert obligatory "I feel like an idiot for not doing more reading on here ahead of time" statement)
Trioculus said:
Okay, I wish I had read this before I did what I just did. My device seems to be bricked
Was running 1.22.651.3 and MeanROM-ICS-v65 and went to update things to JB. Updated using PJ75IMG_3.16.651.3_firmware in HBOOT and now the screen won't turn on and none of the LEDs light up when plugged in. The device manager shows QHSUSB_DLOAD when it's plugged into the PC.
Any way to unbrick this?
(insert obligatory "I feel like an idiot for not doing more reading on here ahead of time" statement)
Click to expand...
Click to collapse
Did you not download the most recent firmware from my thread? Because there's no way it should've bricked you. I personally updated from 1.22 firmware up to 3.16 with no issues, and someone else updated from 1.13 firmware up to 3.16. What exact file did you use?
EDIT: I just looked, and I don't even have a file available with that name in my thread (anymore). The only one I have is this, which is the extended firmware which eliminates the bricking issue. Sounds like you had an old download.
Captain_Throwback said:
What exact file did you use?
Click to expand...
Click to collapse
I used the one linked to from the wiki page: http://d-h.st/9L9 PJ75IMG_3.16.651.3_firmware.zip
Any way to fix this? Thanks for your help
Trioculus said:
I used the one linked to from the wiki page: http://d-h.st/9L9 PJ75IMG_3.16.651.3_firmware.zip
Any way to fix this? Thanks for your help
Click to expand...
Click to collapse
Ouch. I'll have to update the Wiki. I'll be sure to mention it to Haus.
And no, your device is bricked. Time to get a replacement.
EDIT: Wiki updated with proper link.
Captain_Throwback said:
Ouch. I'll have to update the Wiki. I'll be sure to mention it to Haus.
And no, your device is bricked. Time to get a replacement.
EDIT: Wiki updated with proper link.
Click to expand...
Click to collapse
ouch..That sucks, man.
Related
Ok, I'm really curious about this. I want to quickly know what ROMs can be flashed to a phone that is HTC Dev Unlocked and S-On.
Currently running MeanROM 1.91 (and HTC Dev Unlocked & S-On), but I would really like to run Cyanogenmod on it.
I understand you can flash the radio in an S-On phone, but it has to be done in recovery, vs doing it in the bootloader with an S-Off phone.
kusanagi-sama said:
Ok, I'm really curious about this. I want to quickly know what ROMs can be flashed to a phone that is HTC Dev Unlocked and S-On.
Currently running MeanROM 1.91, but I would really like to run Cyanogenmod on it.
I understand you can flash the radio in an S-On phone, but it has to be done in recovery, vs doing it in the bootloader with an S-Off phone.
Click to expand...
Click to collapse
You can flash whatever ROM you want, as long as you have a custom recovery.
And you can flash radios through recovery as long as your HBOOT isn't the one from the latest OTA (1.15). In that case, you can't.
You can. just backup, and do a full wipe, and and flash.
Sent from my EVO using Tapatalk 2
I think the only thing you gain with s-off is the ability to update your firmware.
Sent from my EVO using Tapatalk 2
Captain_Throwback said:
You can flash whatever ROM you want, as long as you have a custom recovery.
And you can flash radios through recovery as long as your HBOOT isn't the one from the latest OTA (1.15). In that case, you can't.
Click to expand...
Click to collapse
I got my phone a week ago (actually on the 13th), and as soon as I got it, I let it do the updated to 1.22.
I have TWRP 2.2 as my recovery. HBoot is 1.15. In that case, is there any ability at all to update the radio to something newer?
Wakawaka024 said:
I think the only thing you gain with s-off is the ability to update your firmware.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
What does the firmware changes?
tybo31316 said:
What does the firmware changes?
Click to expand...
Click to collapse
I think he meant you can only update the radio firmware with S-Off.
kusanagi-sama said:
I got my phone a week ago (actually on the 13th), and as soon as I got it, I let it do the updated to 1.22.
I have TWRP 2.2 as my recovery. HBoot is 1.15. In that case, is there any ability at all to update the radio to something newer?
Click to expand...
Click to collapse
Well, currently there isn't a newer radio, but if there was, you'd have to relock and take whatever the new OTA would be to upgrade your firmware (including radio).
Radios cannot be flashed through recovery with the new 1.15 HBOOT, nor can splash screens or kernels.
Captain_Throwback said:
Well, currently there isn't a newer radio, but if there was, you'd have to relock and take whatever the new OTA would be to upgrade your firmware (including radio).
Radios cannot be flashed through recovery with the new 1.15 HBOOT, nor can splash screens or kernels.
Click to expand...
Click to collapse
So, to relock, I would have to follow one of the threads on unrooting and relocking the phone? You can't do that by just re-flashing the stock ROM (its how it worked with my LG Optimus S and Motorola Photon 4G)?
The point is, I want to run CM9 or 10 once it becomes stable for this phone (when camera, MMS, and everything else works)
kusanagi-sama said:
So, to relock, I would have to follow one of the threads on unrooting and relocking the phone? You can't do that by just re-flashing the stock ROM (its how it worked with my LG Optimus S and Motorola Photon 4G)?
The point is, I want to run CM9 or 10 once it becomes stable for this phone (when camera, MMS, and everything else works)
Click to expand...
Click to collapse
Actually, you don't have to re-lock to take an OTA, if you're on stock. But being as though you want to run a custom ROM, you'd have to nandroid backup your current setup. Relock the bootloader ("fastboot oem lock"), and then flash the latest RUU, at which point you'd be updated to the latest firmware.
Captain_Throwback said:
Actually, you don't have to re-lock to take an OTA, if you're on stock. But being as though you want to run a custom ROM, you'd have to nandroid backup your current setup. Relock the bootloader ("fastboot oem lock"), and then flash the latest RUU, at which point you'd be updated to the latest firmware.
Click to expand...
Click to collapse
Well, I'm already running MeanROM 1.91, as mentioned in the first post.
kusanagi-sama said:
Well, I'm already running MeanROM 1.91, as mentioned in the first post.
Click to expand...
Click to collapse
I was just saying, based on what you said you want to run in the future, at which point there may be some firmware updates to actually update to .
Captain_Throwback said:
I was just saying, based on what you said you want to run in the future, at which point there may be some firmware updates to actually update to .
Click to expand...
Click to collapse
I'm sure there will be.
So, the process would be:
1.) relock the bootloader
2.) flash the latest RUU
3.) unlock the bootloader, and re-root
4.) flash to the latest CM9/10 port (and install the latest gapps)
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
I've been (at least trying to) patiently wait for Deck to post full install instructions for CM10 but the CM10 op is still bare as bones. Has anyone else posted an install guide or instructions yet?
I'm currently rooted with RegawMod and running MeanRom 2.1 and it's really terribly laggy and frustrating, I can't wait any longer for CM10. Do I need S-off to install CM10 or do I just wipe, flash, and go?
Thanks for any help or links!
If you are on hboot 1.15 or higher you have to fast boot flash the kernel.
Other than that its just like a normal aosp install. Wipe flash rom flash gapps.
Its been my daily for 3 weeks.
Sent from my EVO using Tapatalk 2
You don't need s-off. You will however have to flash the boot IMG separately by using fastboot or the app flash image GUI and a full wipe is definitely required. There is a helpful thread in Q&A called "don't panic" that will answer all your questions
Good luck
Sent from my EVO using xda app-developers app
corcgaigh said:
You don't need s-off. You will however have to flash the boot IMG separately by using fastboot or the app flash image GUI and a full wipe is definitely required. There is a helpful thread in Q&A called "don't panic" that will answer all your questions
Good luck
Click to expand...
Click to collapse
Dont use flash image gui unless you know how to do it manually through fastboot. You are just asking for issues
Instructions:
http://androidforums.com/evo-4g-lte-all-things-root/606748-how-install-kernels-h-boot-1-15-a.html
Rxpert said:
If you are on hboot 1.15 or higher you have to fast boot flash the kernel.
Other than that its just like a normal aosp install. Wipe flash rom flash gapps.
Click to expand...
Click to collapse
I'm on hboot 1.12, so does that mean I can just flash normally?
edit - From what I can tell from reading, hboot 1.12 doesn't have the same restrictions that 1.15+ do, so I think I'm OK but I would like verification.
Thanks for the help everyone.
Yes hboot 1.12 allows for access to the boot partition
Also luuuuucckkyyyyyy...
EdhyMonker said:
I'm on hboot 1.12, so does that mean I can just flash normally?
edit - From what I can tell from reading, hboot 1.12 doesn't have the same restrictions that 1.15+ do, so I think I'm OK but I would like verification.
Thanks for the help everyone.
Click to expand...
Click to collapse
If you are on Hboot 1.12 I'd strongly suggest looking into getting S-OFF. Theres really no reason not to.
Up to you though, its not required
Bit off topic, anyone check to see if you can push a new splash, right now I'm too lazy to start my PC just to fastboot one measly splash
Rxpert said:
If you are on Hboot 1.12 I'd strongly suggest looking into getting S-OFF. Theres really no reason not to.
Up to you though, its not required
Click to expand...
Click to collapse
The S-OFF guide was way over my head so I just let it be. If there's not a real good reason for doing it, and I can still run CM10, then I'd rather not.
It allows you to directly flash new firmware like radios to fix any problems a device might be having. If you have Son and want the latest firmware you have to revert back to stock and accept ota, then unlock reflash recovery and reflash custom ROM or rooted stock, you could also just flash root installer if you want to just root stock
om4 said:
It allows you to directly flash new firmware like radios to fix any problems a device might be having. If you have Son and want the latest firmware you have to revert back to stock and accept ota, then unlock reflash recovery and reflash custom ROM or rooted stock, you could also just flash root installer if you want to just root stock
Click to expand...
Click to collapse
No, S-ON people with 1.12 H-boot can flash radios and firmware from recovery. They can do whatever they please in recovery just like S-OFF. S-OFF users can flash things from bootloader and even change the appearance of their h-boot to read S-ON and **locked** even though they are S-OFF
To the OP, this is the best rooting guide I've seen. It really explains everything step by step. http://androidforums.com/evo-4g-lte...panda-s-htc-dev-ltevo-root-dummies-guide.html Its recommended to have Linux at least bootable, because in the small chance the phone gets bricked... the unbricker program requires linux.
I ran it in windows before the unbricker was available, no issues here
You basically just hook the phone up to it and run the program like you do for most other root programs. All 1-click
Ah yeah forgot to mention that, most everyone is on 1.15 or 1.19 sorry
om4 said:
Ah yeah forgot to mention that, most everyone is on 1.15 or 1.19 sorry
Click to expand...
Click to collapse
Alright, I got S-Off using Lazy Panda and it went better than expected!
Do I need to flash updated firmware / radios separately from CM10, or does CM10 include latest firmware?
Sorry to ask dumb questions, but I do hope this thread will also be a good resource for others like me.
You don't have to flash any firmware updates. There are a few users with issues although they may be related to the ROM update and not necessarily the firmware included. I haven't really checked since I'm s on. If you want to update the radios there's an update zip here somewhere, be sure to read through everything carefully. Radios are more risky then every day flashing
Alright everyone now I need some help!
I flashed CM10 after s-off, was on stocked 1.13 rooted rom.
Now when CM10 boots up I am faced with a phone activation screen. It says something like "you will not be able to place calls or access the mobile network until the device is activated". I am unable to make calls or receive calls or access the internet. I have tried reflashing cm10 and the problem persists.
In the mean time, I will try flashing a nand backup and see where that gets me. I appreciate any and all help, and I have found no posts in the CM10 thread with a similar issue.
Update: I wiped and restored a back-up, MeanRom 2.1. Upon boot, hands-free activation ran and activated the phone and downloaded a PRL update. Everything is working fine now. Not sure if I should try CM10 again or what? Any advice?
EdhyMonker said:
Alright everyone now I need some help!
I flashed CM10 after s-off, was on stocked 1.13 rooted rom.
Now when CM10 boots up I am faced with a phone activation screen. It says something like "you will not be able to place calls or access the mobile network until the device is activated". I am unable to make calls or receive calls or access the internet. I have tried reflashing cm10 and the problem persists.
In the mean time, I will try flashing a nand backup and see where that gets me. I appreciate any and all help, and I have found no posts in the CM10 thread with a similar issue.
Update: I wiped and restored a back-up, MeanRom 2.1. Upon boot, hands-free activation ran and activated the phone and downloaded a PRL update. Everything is working fine now. Not sure if I should try CM10 again or what? Any advice?
Click to expand...
Click to collapse
ive only ever seen this issue with cyanogenmod and the old htc vogues, still great phones for what they were
EdhyMonker said:
Alright, I got S-Off using Lazy Panda and it went better than expected!
Do I need to flash updated firmware / radios separately from CM10, or does CM10 include latest firmware?
Sorry to ask dumb questions, but I do hope this thread will also be a good resource for others like me.
Click to expand...
Click to collapse
Yes, you should be flashing the upgraded firmware. You'll see the full firmware as the very first downloadable link. Flash that
http://themikmik.com/showthread.php...dio-Collection&p=220556&viewfull=1#post220556
Rename the file to "PJ75IMG.zip", place on root of SD card, and boot into HBOOT to flash. Check the md5 to make sure its right. With radios you want to make sure its the correct file.
Welcome to S-OFF my friend
Rxpert said:
Yes, you should be flashing the upgraded firmware. You'll see the full firmware as the very first downloadable link. Flash that
http://themikmik.com/showthread.php...dio-Collection&p=220556&viewfull=1#post220556
Rename the file to "PJ75IMG.zip", place on root of SD card, and boot into HBOOT to flash. Check the md5 to make sure its right. With radios you want to make sure its the correct file.
Welcome to S-OFF my friend
Click to expand...
Click to collapse
Thanks, but I tried this and it says "no image or wrong image" when trying to flash the PJ75IMG.zip file.
Did you type in PJ75IMG.zip or PJ75IMG and kept it a zip file...you should do the 2nd.
joebarkho said:
Did you type in PJ75IMG.zip or PJ75IMG and kept it a zip file...you should do the 2nd.
Click to expand...
Click to collapse
I thought that might've been the issue so I tried it both ways, didn't work either way. I'll take another shot at it tomorrow.
First I must say that I have already fixed the problem. I flashed and RUU using step 8 and up on the DirtyRacun method and my phone us back to normal.
I'm S-off
HBOOT 1.15.2222
Originally had Venom 2.0.1 installed (error: i have 3.0.1)
Flashed Using TWRP 2.4.1.0
I did a full wipe before flashing. While I was flashing MeanBean 2.02 I think it just restarted without warning. When I tried going into TWRP again it wouldn't load, it would show the boot screen for a split second then reboot into bootloops. I tried fastboot flashing other version of TWRP but that didn't do anything.
From here I relocked and flashed my RUU accordingly with the DirtyRacun process. After unlocking my bootloader and flashing TWRP 2.3.1.0 I restored my old backup of Venom and I'm back to normal.
I checked the MD5 sums of the MeanBean ROM and they matched.
What the heck happen during the install?
Flash new radios now my phone is bricked and get teh DLOAD drivers on windows.
I'm gonna take a guess and say you flashed the latest firmware 3.16 without flashing the previous firmware update 3.15.
There is no radio only zip available from the latest OTA update for this very reason.
If this is the case your phone is unrecoverable . back to sprint
Sent from my EVO using xda premium
Shad Stang said:
First I must say that I have already fixed the problem. I flashed and RUU using step 8 and up on the DirtyRacun method and my phone us back to normal.
I'm S-off
HBOOT 1.15.2222
Originally had Venom 2.0.1 installed
Flashed Using TWRP 2.4.1.0
I did a full wipe before flashing. While I was flashing MeanBean 2.02 I think it just restarted without warning. When I tried going into TWRP again it wouldn't load, it would show the boot screen for a split second then reboot into bootloops. I tried fastboot flashing other version of TWRP but that didn't do anything.
From here I relocked and flashed my RUU accordingly with the DirtyRacun process. After unlocking my bootloader and flashing TWRP 2.3.1.0 I restored my old backup of Venom and I'm back to normal.
I checked the MD5 sums of the MeanBean ROM and they matched.
What the heck happen during the install?
Click to expand...
Click to collapse
u must have did something u wasnt suupposed to do cause meanbean would not hurt your phone in anyway bro
I second this, I am having issues as well.
Let this be a warning for others that may follow in your footsteps. You need to make sure you know what you are doing before you start flashing firmware. Firmware is meant to be upgraded one step at a time, not jumping from an old firmware to the latest, this will brick you phone in most cases. Please make sure you have verified your current firmware that you are on and upgrade to the next highest in sequence until you finally reach the newest. Also, the radio is just a part of the firmware, so if you did not upgrade the full firmware in the past then you need to go back and install the full firmware that you were on and then upgrade to each subsequent one. If you are s-on the only way to do this is to relock and take the OTA. For those that are s-off visit Captain Throwbacks thread in the development section and start reading and learning. You may find a solution in it.
Cruise was right, i thought i had the radio that came with 3.15 but i really had the radio that came with 1.22 XD.
Need to Update...not sure how!
cruise350 said:
Let this be a warning for others that may follow in your footsteps. You need to make sure you know what you are doing before you start flashing firmware. Firmware is meant to be upgraded one step at a time, not jumping from an old firmware to the latest, this will brick you phone in most cases. Please make sure you have verified your current firmware that you are on and upgrade to the next highest in sequence until you finally reach the newest. Also, the radio is just a part of the firmware, so if you did not upgrade the full firmware in the past then you need to go back and install the full firmware that you were on and then upgrade to each subsequent one. If you are s-on the only way to do this is to relock and take the OTA. For those that are s-off visit Captain Throwbacks thread in the development section and start reading and learning. You may find a solution in it.
Click to expand...
Click to collapse
(1) How do I know if I'm s-off or on?
(2) I keep getting an OTA update notification. Do I take this update? If so, once it downloads then what?
-Running MeanBean_1.7 (I know sooo...far behind. That's why I want to update)
-Android 4.1.1
-PRL 25012
-Kernel: [email protected] #1 SMP PREEMPT
BaseB - 1.12.11.1119
Build - 3.15.651.16 CL124461 release-keys
I just need a step by step process on how to update this thing. Video, tutorial. etc.
Thanks in advance!
KEMODREAMS said:
(1) How do I know if I'm s-off or on?
(2) I keep getting an OTA update notification. Do I take this update? If so, once it downloads then what?
-Running MeanBean_1.7 (I know sooo...far behind. That's why I want to update)
-Android 4.1.1
-PRL 25012
-Kernel: [email protected] #1 SMP PREEMPT
BaseB - 1.12.11.1119
Build - 3.15.651.16 CL124461 release-keys
I just need a step by step process on how to update this thing. Video, tutorial. etc.
Thanks in advance!
Click to expand...
Click to collapse
Unless you bought your phone used, you should know whether you are s-on or s-off since it is an involved process to get your phone s-off. What ota notices are you getting? Are they from the ota updater built in to MeanBean, or is it the HTC update?
If its the MeanBean update you can let it update and it should work just fine. Your firmware will not be up to date, but MeanBean will still work. If its HTC then don't take the update.
If you are s-off you can update you firmware with the file provided in the first post of the MeanBean thread.
If you are s-on, the only way to update your firmware is returning to stock, locking your bootloader, and taking the HTC ota update.
Sent from my icrap 2 using Tapatalk HD
cruise350 said:
Unless you bought your phone used, you should know whether you are s-on or s-off since it is an involved process to get your phone s-off. What ota notices are you getting? Are they from the ota updater built in to MeanBean, or is it the HTC update?
If its the MeanBean update you can let it update and it should work just fine. Your firmware will not be up to date, but MeanBean will still work. If its HTC then don't take the update.
If you are s-off you can update you firmware with the file provided in the first post of the MeanBean thread.
If you are s-on, the only way to update your firmware is returning to stock, locking your bootloader, and taking the HTC ota update.
Sent from my icrap 2 using Tapatalk HD
Click to expand...
Click to collapse
+1 if you boot into boot loader you will see whether you are s-off or not.
Sent from my Nexus 7 using xda app-developers app
Need to Update...not sure how!
ronniemayo said:
+1 if you boot into boot loader you will see whether you are s-off or not.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Ok so I did that and it says I'm s-on. Now what? Do I take the OTA update that says "This will update your ROM (MeanBean) to version MeanBean_3.06"? If so, once it's downloaded what do I do? Restart into bootloader? Also my Titanium backup is saying that it "could not acquire root privileges" What does that mean? Thanks for your help.
If you want to update meanbean then backup and flash the latest meanbean. If yours breaks like mine did, flash an ruu and dont be an idiot like me. im guessing it s a rare occurrence that mine broke the recovery
If your goal is to flash new radios then you have two options:
Two methods:
Get your adventure face on and follow the DirtyRacun S-Off process step by step (It worked for me on windows 7 x64 but its easy to use a ubuntu livecd)
Once you are s-off you can flash radios. DO NOT JUMP VERSIONS... EVER use the baseband version as reference in about phone and flash each version up until you are at the latest
OR
staying s-on and leaving yourself less prone to brick hell
recovery nandroid backup: system, data, boot
flash ruu
ota update
reroot
restore backup.
i dont know how to root from the latest version so idk if this is a good procedure. make sure you can root with the latest version
But really if you have a choice, ditch the evo and get the s3. you can firmware jump all you want, but the downside is that the s3 has sh*t roms. I miss venom and stock with goodies :crying:
Shad Stang said:
If you want to update meanbean then backup and flash the latest meanbean. If yours breaks like mine did, flash an ruu and dont be an idiot like me. im guessing it s a rare occurrence that mine broke the recovery
If your goal is to flash new radios then you have two options:
Two methods:
Get your adventure face on and follow the DirtyRacun S-Off process step by step (It worked for me on windows 7 x64 but its easy to use a ubuntu livecd)
Once you are s-off you can flash radios. DO NOT JUMP VERSIONS... EVER use the baseband version as reference in about phone and flash each version up until you are at the latest
OR
staying s-on and leaving yourself less prone to brick hell
recovery nandroid backup: system, data, boot
flash ruu
ota update
reroot
restore backup.
i dont know how to root from the latest version so idk if this is a good procedure. make sure you can root with the latest version
But really if you have a choice, ditch the evo and get the s3. you can firmware jump all you want, but the downside is that the s3 has sh*t roms. I miss venom and stock with goodies :crying:
Click to expand...
Click to collapse
You should read Captain _Throwback's firmware thread
You can root the latest OTA just click the link in my sig
Sent from my PoS MoPho
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