I'm currently running Stock w Goodies 1.75, I'm S-ON & H-boot 1.12.
I'd like to flash my radio since it's all still on the original but from what I've read I can only flash my radio using recovery and need to be S-OFF to flash everything and do it from the bootloader. Given my current setup, should I 1) Just flash the radio from recovery or 2) Flash the ROM suggested in the LazyPanda thread (Fresh 5.1.1 w/ 1.13), get S-Off and then flash everything before moving back to my current setup? Are there any issues with going that route besides it just taking some time?
Thanks!
S-off is really the way to go. There's some risk involved so take your time. After you get s-off you can flash any updates directly without using an ruu or reverting to stock and taking ota
ericande said:
I'm currently running Stock w Goodies 1.75, I'm S-ON & H-boot 1.12.
I'd like to flash my radio since it's all still on the original but from what I've read I can only flash my radio using recovery and need to be S-OFF to flash everything and do it from the bootloader. Given my current setup, should I 1) Just flash the radio from recovery or 2) Flash the ROM suggested in the LazyPanda thread (Fresh 5.1.1 w/ 1.13), get S-Off and then flash everything before moving back to my current setup? Are there any issues with going that route besides it just taking some time?
Thanks!
Click to expand...
Click to collapse
just follow post number 2, i used fresh 5.1.1 and it worked perfect, then i flashed the new hboot, then the firmware then the rom of choice...just to be safe i rebooted the device after each install
cool, when I get some time I'll go with the recommended ROM and go that route.
Maybe not the place to ask, but anyone else other than flex have goodies 2.05?
Ask me about my ability to annoy complete strangers!
Thanks guys, I changed my ROM to the recommended one, Lazy Panda was really easy and now I'm back to my old setup but S-OFF with updated radios.
Related
i've been wondering if anyone else has been having any issues with mean rom ics, i've flashed it twice, and even done a full wipe and everything. but it seems every time i restart (or the phone powers down) i go through about 6 - 10 crashes before it can run stable enough for me to use it at all. has anyone else had this issue or have this issue and can shed any light on what could be causing it?
Strange. Are you s-on or s-off?
Read, Search, Read again, ... Then Ask with Tapatalk 2
Im s-off via Juopunutbear. My phone came with bootloader 1.50 but I updated for ics using what was posted Here, so I could retain s-off
I was having some odd things happen when I first moved to MeanROM 2.6 as well so I flashed the 2.89 RUU when it became available to make sure that the software and firmware were completely in sync. That's pretty easy to do if you are S-OFF since all you have to do is connect your phone to a Windows PC and run the RUU.exe, then flash a custom recovery and optionally a different bootloader.
Things seem to be a little smoother for me after flashing the 2.89 RUU as a base.
ramjet73
ramjet73 said:
I was having some odd things happen when I first moved to MeanROM 2.6 as well so I flashed the 2.89 RUU when it became available to make sure that the software and firmware were completely in sync. That's pretty easy to do if you are S-OFF since all you have to do is connect your phone to a Windows PC and run the RUU.exe, then flash a custom recovery and optionally a different bootloader.
Things seem to be a little smoother for me after flashing the 2.89 RUU as a base.
ramjet73
Click to expand...
Click to collapse
but isn't flashing via bootloader the firmware bits doing (the long-ish way) the same thing as what the RUU would do? I'm still on the stock HTC bootloader for 1.58 because i was updated to it from the firmware bits, but if the RUU does something extra then maybe i would benefit from flashing with it. but i mean i also have MIUI 2.8.17 and i installed it (after i was able to use my phone) through boot manager a few weeks after installing MeanROM and booting to it yields me no issues of crashing or anything. do note its based off (supposedly) the GSM port for the E3D as well as files from the sprint/htc ICS release
AlexxSeven said:
but isn't flashing via bootloader the firmware bits doing (the long-ish way) the same thing as what the RUU would do? I'm still on the stock HTC bootloader for 1.58 because i was updated to it from the firmware bits, but if the RUU does something extra then maybe i would benefit from flashing with it. but i mean i also have MIUI 2.8.17 and i installed it (after i was able to use my phone) through boot manager a few weeks after installing MeanROM and booting to it yields me no issues of crashing or anything. do note its based off (supposedly) the GSM port for the E3D as well as files from the sprint/htc ICS release
Click to expand...
Click to collapse
There's no guaranty that flashing the RUU will fix anything but it did seem to help on my phone. The RUU flashes both the stock ROM and all the firmware, including the bootloader, so it makes your phone 100% stock except for the S-ON/S-OFF radio security and bootloader locked/unlocked status. It won't change either of those, but you must have your bootloader locked (or relocked) to run the RUU if S-ON.
After running the RUU.exe you can flash a custom recovery and bootloader if you want. It should be the same as returning to stock and taking the OTA update, but flashing the RUU.exe is faster and easier.
ramjet73
Hboot 1.5 s-on and I'm running meanrom ICS 2.6 .
I did the HTC unlock. Then installed Su zip from this site. Then I installed 4ext and rebooted into recovery...flashed the meanrom zip (it flashed the kernel that comes w the Rom ) and that was it. Now I'm on sw 2.89 build w the 3.0.16 kernel and like I said still s off and hboot 1.5
If anyone knows any where to get a kernel to overclock please let me know
Sent from my PG86100 using xda app-developers app
ramjet73 said:
There's no guaranty that flashing the RUU will fix anything but it did seem to help on my phone. The RUU flashes both the stock ROM and all the firmware, including the bootloader, so it makes your phone 100% stock except for the S-ON/S-OFF radio security and bootloader locked/unlocked status. It won't change either of those, but you must have your bootloader locked (or relocked) to run the RUU if S-ON.
After running the RUU.exe you can flash a custom recovery and bootloader if you want. It should be the same as returning to stock and taking the OTA update, but flashing the RUU.exe is faster and easier.
ramjet73
Click to expand...
Click to collapse
i actually decided to give it a try after making a nand backup ofc, and still had the same issues :s after re-flashing from my backup though it seems to boot fairly stable now. even between switching roms im not sure exactly why but could it have been an issue with anything that is permanent between any rom?
First, a big big thanks to Virus!! My phone info:
Sprint EVO3D CDMA
SHOOTER XC SHIP S-OFF RL
HBOOT-1.40.0000
RADIO-1.06.00.1216
eMMC-boot
Jun 8 2011, 17:20:22
TWRP v1.1.1
I previously flashed Freeza's v2.17.651.5 firmware and then the Stock ROM + root Shooter_S_Sprint_WWE_2.17.651.5_odex.zip which I'm currently running.
I've read this entire post OTA_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2-2.17.651.5 along with mpgrimm2's post Evo3d(CDMA)HBoot/S-off Differences & Rooting Background Info 8-20-12 and just want to ask before I "leap"! My steps as far as I see it:
1. Run my backups (Titanium, etc) and create a TWRP nandroid.
2. Flash the Stock 2.89.651.2-2.17.651.5 firmware
3. Install the superwipe zip (presumably install zip via TWRP recovery?)
4. Flash the Stock Rooted 2.89.651.2-2.17.651.5 ROM
5. If necessary, flash the BT fix.
At this point I should be up and running the DEODEX'd version of the Stock ICS ROM as if I'd done the ICS OTA. Question here is whether I'll hit compatibility problems with any apps I have installed? I know hard to say w/o knowing what all I've got installed, but if problems I figure just uninstall the app and find something compatible... Any other problems I could expect or should look for?
If for some reason I wanted to go back to my current GB ROM nandroid before the ICS update, I can just reflash hboot 1.40 and restore the nandroid made in my step 1? Do I need to worry about reflashing any other 2.17 firmware? It sounds like I can just restore my nandroid on hboot 1.58 but thinking I'd rather be back at hboot 1.40.
I too have run into the "remote: not allowed" error when using fastboot to flash images. From mpgrimm2's post, it's looks to be because my radio is s-off while my stock hboot 1.40 is technically not s-off? To have a fully functional fastboot via pc, I'd need to flash JBear hboot 1.40 (for GB) or JBear hboot 1.58.5858 (for ICS) from Ramjet's Pick your bootloader!, right? Seeing that I'm ok with flashing by booting into recovery, is there any other advantages (or disadvantages) to using the JBear hboots?
Sorry for the long post, but wanted to be complete... All help is greatly appreciated!
It looks like you have it right. To clarify one point, you don't need to downgrade firmware to run GB (I don't think that's even possible). Just the hboot.
Read, Search, Read again, ... Then Ask with Tapatalk 2
coal686 said:
It looks like you have it right. To clarify one point, you don't need to downgrade firmware to run GB (I don't think that's even possible). Just the hboot.
Read, Search, Read again, ... Then Ask with Tapatalk 2
Click to expand...
Click to collapse
Thanks for the confirmation on my steps and being able to revert if I want to...I figured I would want to keep some of the updated firmware but wasn't sure what all could/should keep.
Although like the idea of being able to use fastboot fully, thinking best to just stick with the stock hboot for now...
Again thanks and if anyone has any other thoughts, they're always welcome!
I delayed doing the ICS update using the steps above, have read through the new pages/posts on the http://forum.xda-developers.com/showthread.php?t=1808150 post, and now have a few last questions before I jump in! Sorry if seem obvious, but have done the reading but now a bit confused or need clarification. I could just do it and recover if necessary, but rather ask up front.
If reading right, doing the Superwipe in step 2 will format both my phone and sdcard, cleaning out and recreating the partitions. Does this mean I'll have to use my TB Pro backups to restore all my personal apps & data? And if so, will I encounter any issues restoring such thing as my call log (or just restore the data and I'll be ok)? Reading up on Superwipe gets me thinking it deletes everything when I thought flashing this would be like an OTA update and keep my current apps, etc. Sorry again it's been awhile since flashing the stock 2.18.651.5 rooted ROM and just not remembering!
Also part way through the threads, there's mention of needing to first flash a ROM that will boot on 1.58 hboot or will get boot looping. I figure if my 2.18.651.5 GB rooted ROM won't boot after step 1, I'd just have to remove the firmware P86IMG file from the sdcard to proceed to step 2. The OP doesn't mention this - or is this a different situation than mine?
Lastly, on P.59, mpgrimm2 recommends flashing the full stock RUU to clean out all bits & pieces that might be left (I'm figuring it's the RUU_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2_Radio_1.09.00.0706__NV_NV_SPCS_1.43_release_271101_signed.exe) and reinstalling a custom recovery to have the stock rooted ICS. Is this a special case for one person or an alternative to the 3 step method? And it would mean I'd be reinstalling all apps and restoring all my data afterwards, right? Should I even consider this route if the three steps do an upgrade and keep my apps/data?
Thanks and sorry again for so many questions - just getting a headache keeping all straight and sorting through what's special case scenarios...oh and one last, is this Sense 3.5 or 3.6 - the OTA on HTC's site is listed as 3.6, right?
That's correct sir. It is 3.6
Alright So I've done a little research...and to the best of my knowledge...kernels have to be flashed from fastboot, and everything else can be flashed from recovery (Except radios because of S-on) when you use HTC's unlock method correct? If so can someone point me in the direction of how to flash roms via fastboot? I've always had S-off on my evo 3D and full root on my nexus so I'm new to the S-on restrictions, Thanks! :good:
With hboot 1.12 you can flash ROMs normally, but hboot 1.15 and up require the kernel be flashed separately. The methods for flashing a kernel are fastboot, flash image gui, and HTC dumlock. Firmware for hboot 1.15 and up require that you either run the ruu or you flash stock rom, and then stock recovery, relock bootloader, and take the ota. Updating isn't really advised but it can be done should the need arise. Never try to downgrade firmware or hboot. If you have enabled wallet, go ahead and reset wallet from within the app to be safe and then flash. It's still not certain what damages the secure element. When flashing a rom and kernel be sure to match the base, when flashing from one custom rom to a different one always wipe the phone first. I guess that this should be enough of a primer. Read don't panic in Q&A if you want more in depth information
Thanks for the info!
Sent from my EVO using xda app-developers app
I recently installed Mean Horsey Face ROM, but realized I have really old radios that I've never updated. What's the easiest way to update my radios via this ROM? I know I can flash them from hboot if I were S-OFF, but how can I do it from S-ON?
Thanks!
Old radios? Please post the version information from software info in about phone.
Sent from my ADR6425LVW using Xparent Red Tapatalk 2
If you want the global firmware, follow this - http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
It will wipe out your rom, recovery, etc so back up your phone first. Once you're done you can re-unlock your bootloader, flash your custom recovery and restore your rom/re-flash your boot.img.
Will installing this RUU install the default rezound ROM and leave my phone fully functional? I will unlock bootloader / custom recovery and all re-flash my own rom at some point, but I want to see how long this will all take. Thanks.
facted said:
Will installing this RUU install the default rezound ROM and leave my phone fully functional? I will unlock bootloader / custom recovery and all re-flash my own rom at some point, but I want to see how long this will all take. Thanks.
Click to expand...
Click to collapse
It returns the phone to out of the box stock basically but will update all the firmware to the latest. You have to go through the whole unlock/root/recovery process again.
As long as you saved your unlock token from before, it's a piece of cake to re-do it all..
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.