Related
So i think i am getting lost and I really want to be careful before i re-start my crack flashing habits again.
I flashed senseless ics, loved it, but wanted to go back to gb. So i went back to senseless 1.1, extracted boot.img, and adb pushed and flashed then did a nandroid back up and every thing is A-ok .
Here is my confusion.
What problems are ppl refering to with Mainver? ( what is that even )
Why do ppl have to RUU ( again what is it)
is my method right ? Which is : if the rom came with an auto script to flash from hboot then hurray, if not, then flash boot.img from adb via fast boot and flash to my liking ?
the only roms i gave been on so far : cleanrom 1.5.5, inefebellis, senesless 1.1, senseless ecs, then back to senseless 1.1 via nandroid like mentioned.
jmichaels1982 said:
So i think i am getting lost and I really want to be careful before i re-start my crack flashing habits again.
I flashed senseless ics, loved it, but wanted to go back to gb. So i went back to senseless 1.1, extracted boot.img, and adb pushed and flashed then did a nandroid back up and every thing is A-ok .
Here is my confusion.
What problems are ppl refering to with Mainver? ( what is that even )
Why do ppl have to RUU ( again what is it)
is my method right ? Which is : if the rom came with an auto script to flash from hboot then hurray, if not, then flash boot.img from adb via fast boot and flash to my liking ?
the only roms i gave been on so far : cleanrom 1.5.5, inefebellis, senesless 1.1, senseless ecs, then back to senseless 1.1 via nandroid like mentioned.
Click to expand...
Click to collapse
ruu is flashing stock. method is right with the boot.img which is also the kernel but without other kernel files found in the flashable zip. If the rom doesnt have the boot.img u can also use cleanflash tool to flash the kernel/boot into your current rom,restart,then wipe/flash rom
sent from my rezound using tapatalk
RUU files are the official software releases from HTC.
RUU files are signed. (They give proper "official" codes to hboot to get past the s=on security)
This means that they can flash all parts of the device, even the bootloader and radio firmware, which we can not normally flash because it is write locked. (do to s=on we can't flash them even with root)
Sometimes people have issues and need to get the phone back to pure stock so they use the RUU.
Mainver is data on the software version number of the kernel (I believe... it may be for some other part, either way it is version info)
Think V1... V1.2... V1.5... V1.5.5
Because of s=on we are not allowed to "downgrade/revert" to older software versions.
The leaked ICS build has a newer Mainver, some people flashed the leak unmodified, and that changed the Mainver info. Now they need to use a special trick to trick the s=on security to allow flashing of older kernels. The ICS ROMs we have now, have been modified so they do not change the Mainver. This makes it easier to go back to GB or switch to other ROMs.
Marine6680 said:
RUU files are the official software releases from HTC.
RUU files are signed. (They give proper "official" codes to hboot to get past the s=on security)
This means that they can flash all parts of the device, even the bootloader and radio firmware, which we can not normally flash because it is write locked. (do to s=on we can't flash them even with root)
Sometimes people have issues and need to get the phone back to pure stock so they use the RUU.
Mainver is data on the software version number of the kernel (I believe... it may be for some other part, either way it is version info)
Think V1... V1.2... V1.5... V1.5.5
Because of s=on we are not allowed to "downgrade/revert" to older software versions.
The leaked ICS build has a newer Mainver, some people flashed the leak unmodified, and that changed the Mainver info. Now they need to use a special trick to trick the s=on security to allow flashing of older kernels. The ICS ROMs we have now, have been modified so they do not change the Mainver. This makes it easier to go back to GB or switch to other ROMs.
Click to expand...
Click to collapse
Good write up !
waw
Thank you Thank you Thank you ! best crash course ever ...
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'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.
I tried searching for this answer before I posted this but I was not successful at finding it. So.....
Is there anything that cannot be updated by the ROMs? Are there items that can only be updated by taking the latest OTA update? I am trying to figure out if I need to take this latest update to get the latest firmware, kernel, etc.
I am OK with waiting for the ROM updates to come out if they will update everything, too. If they can't, I might as well get these OTA updates to see if they fix some of my problems.
Thanks for the help.
badtlc said:
I tried searching for this answer before I posted this but I was not successful at finding it. So.....
Is there anything that cannot be updated by the ROMs? Are there items that can only be updated by taking the latest OTA update? I am trying to figure out if I need to take this latest update to get the latest firmware, kernel, etc.
I am OK with waiting for the ROM updates to come out if they will update everything, too. If they can't, I might as well get these OTA updates to see if they fix some of my problems.
Thanks for the help.
Click to expand...
Click to collapse
Yes there are a lot of files that cant be updated with roms. The only way to get all of the new firmware is to run the ruu. Turge has figured out how to flash radios now without flashing the ruu so thats good. But thats not everything. I'd wait to run the ruu until the devs change their rom base to the new update. Otherwise no custom rom yet. You can root the stock update after installing, just not many goodies atm.
Thank you very much for your help.
When you say the only way to get the new firmware is to run the new RUU, does that mean running the RUU from at&t or one of the modified RUUs posted on here?
If it is the At&t one, the only way to get it to fully update is by going back to the stock 1.15 ROM, correct?
Yep I ran ruu and got it running stock but my 2nd x+ still running old one wit elegancia till roms get updated I don't mind unrooting updating and rooting takes 30 min tops just patiently waiting for a update hell if viper gets updated first ill rock that
Sent from my HTC One X+ using XDA Premium HD app
badtlc said:
Thank you very much for your help.
When you say the only way to get the new firmware is to run the new RUU, does that mean running the RUU from at&t or one of the modified RUUs posted on here?
If it is the At&t one, the only way to get it to fully update is by going back to the stock 1.15 ROM, correct?
Click to expand...
Click to collapse
The latest ruu for ATT to get the newest firmware is 1.19.502.1 http://dl3.htc.com/application/RUU_E...178_signed.exe
nugzo said:
The latest ruu for ATT to get the newest firmware is 1.19.502.1 http://dl3.htc.com/application/RUU_E...178_signed.exe
Click to expand...
Click to collapse
Correct, but I wasn't sure if you could update directly to that RUU from a custom ROM and get all the updates like hboot, firmware and radio. I was wondering if I needed to go from a custom ROM back to stock 1.15 and THEN do this 1.19 update to get everything updated properly.
If you update your phone to the latest RUU, you won't be able to installed a custom ROM until the devs update their ROM. You update, you stay stock for a moment. You still can ROOT the stock ROM.
badtlc said:
If it is the At&t one, the only way to get it to fully update is by going back to the stock 1.15 ROM, correct?
Click to expand...
Click to collapse
Not exactly. You can upgrade with a RUU if your actual version is equal or lower. You can't downgrade your version unless your phone is S-OFF.
To flash the RUU
Reboot in fastboot mode
type at the prompt >fastboot oem lock
Rebooting
Keep your phone in FASTBOOT USB mode
Run the RUU installer on your computer.
This will FULLY WIPE the phone.
[QUOTE"badtlc"]If it is the At&t one, the only way to get it to fully update is by going back to the stock 1.15 ROM, correct?[/QUOTE]
Not exactly. You can upgrade with a RUU if your actual version is equal or lower. You can't downgrade your version unless your phone is S-OFF.
To flash the RUU
Reboot in fastboot mode
type at the prompt >fastboot oem lock
Rebooting
Keep your phone in FASTBOOT USB mode
Run the RUU installer on your computer.
This will FULLY WIPE the phone.[/QUOTE]
Doing this method, one could use the latest 1.19 directly from HTC and get everything updated? No need to do this method, install the older 1.15, and then do the 1.19 RUU update?
badtlc said:
If it is the At&t one, the only way to get it to fully update is by going back to the stock 1.15 ROM, correct?
Not exactly. You can upgrade with a RUU if your actual version is equal or lower. You can't downgrade your version unless your phone is S-OFF.
To flash the RUU
Reboot in fastboot mode
type at the prompt >fastboot oem lock
Rebooting
Keep your phone in FASTBOOT USB mode
Run the RUU installer on your computer.
This will FULLY WIPE the phone.
Doing this method, one could use the latest 1.19 directly from HTC and get everything updated? No need to do this method, install the older 1.15, and then do the 1.19 RUU update?
Click to expand...
Click to collapse
You can do one of two things to get the full update. One is to go back to a 1.15 stock ROM, flash the stock recovery and run the OTA. The other is to run the latest RUU from HTC (the one from the link posted above) after you've flashed the stock recovery and re-locked the bootloader (otherwise the RUU might not proceed). Bare in mind that running the RUU will wipe your phone to factory settings.
I started a thread here http://forum.xda-developers.com/showthread.php?t=2245955 about people's experiences updating and post-update. Once you decide to update feel free to share your experience there!
I have already updated. I went from elegancia. I locked the bootloader, rebooted to fastboot, and then ran the 1.15 stock RUU. After that, I ran the 1.19 update I downloaded from HTC. I was just trying to figure out if I would have went straight from elegancia to 1.19 if everything including radio, kernel, etc. would have updated properly since elegancia was on the phone and not stock version 1.15. I don't know what these RUUs look at before applying their updates.
I've already unlocked bootloader and rooted device, following which I realized that there is no s-off option for me on the current hboot I have (1.44 after May) and not realizing that s-off is available for the latest AT&T release with 4.3. This is my second HTC device but it is my first go at s-off. I've been doing a lot of research but keep hitting dead ends it seems. Ideally, I would like to flash back to stock recovery and unroot by flashing stock 1.26.502.15 RUU (which is what I am currently on) so I can get OTA then use rumrunner to obtain s-off. I've also looked into downgrading/upgrading the current software number from 1.26.502.15 to 1.26.502.12/3.17.502.3 so I can use revone/rumrunner but I can't confirm whether or not I can flash RUU without being s-off'ed. If anyone can provide any advise I would greatly appreciate it. I'm also not sure if I'm using the terminologies correctly or if this is even posted in the right section.. Thanks in advance!
If you are currently on .12 firmware then you should still have 1.44 HBoot. If so, all you need is REVONE to S-Off. Doing anything else will make it even more of a chore. I believe if you update after then it is S-On again unless you flash one of the other ROM's that are available. You can also run the current RUU from the HTC website to give you the 4.3 update, but you will have 1.55, thus having to use Rumrunner. To run the current RUU, I think you have to relock it too, and unlock it again, at least I did with AIO. You can run any RUU without S-Off that is compatible with ATT. If you want the Brightstar GPE RUU, then yes, you must have S-Off, and change the CID to match that version, and etc for other versions.
hack14u said:
If you are currently on .12 firmware then you should still have 1.44 HBoot. If so, all you need is REVONE to S-Off. Doing anything else will make it even more of a chore. I believe if you update after then it is S-On again unless you flash one of the other ROM's that are available. You can also run the current RUU from the HTC website to give you the 4.3 update, but you will have 1.55, thus having to use Rumrunner. To run the current RUU, I think you have to relock it too, and unlock it again, at least I did with AIO. You can run any RUU without S-Off that is compatible with ATT. If you want the Brightstar GPE RUU, then yes, you must have S-Off, and change the CID to match that version, and etc for other versions.
Click to expand...
Click to collapse
I'm on .15 right now but didn't know if I could update to HTC website 4.3 because I am currently unlocked and rooted and do not have s-off. When I relocked bootloader and tried OTA I had to reboot and it just kept rebooting to TWRP and would not update successfully. So I didn't think the manual update would work?
The manual update will work, but it will WIPE everything. Been there done that, not a big deal though. Went through it, re-unlocked, re-flashed CWM, and that was that. I was going to do S-Off to get the GPE RUU, but heck, with the ATT Remove Bloat script, don't see the need anymore. Got 4.3 running as smooth as it can be, no ATT bloat, and GREAT battery life.
So even though I do NOT have S-off, I can still use the HTC released update to flash onto my phone with the current modifications that I've made already (Unlock and root on JB 4.1.2, software 1.26.502.15, hboot 1.44)? I was under the impression that with S-ON you cannot flash RUU, is that not correct? In the current state, I have to just re-lock bootloader and I can install the official HTC released update? And after which all my data will be wiped, including the custom recovery (TWRP) and root, all of this will be gone? (which is fine) I just have been researching and see that bricking the device is more likely to happen if the device is S-ON and you attempt to flash.
Rumrummer actually has a version available for 1.26.502.15, I used it on Sunday successfully to gain s-off with my mom's phone.
LightSpeedIII said:
Rumrummer actually has a version available for 1.26.502.15, I used it on Sunday successfully to gain s-off with my mom's phone.
Click to expand...
Click to collapse
are you shure? i have a htc one at&t on my hands with 1.26.502.15 firmware and it can not be done. I think you are very confused, 1.26.502.12 firmware is not the same!
---------- Post added at 12:03 PM ---------- Previous post was at 11:55 AM ----------
merck3d said:
So even though I do NOT have S-off, I can still use the HTC released update to flash onto my phone with the current modifications that I've made already (Unlock and root on JB 4.1.2, software 1.26.502.15, hboot 1.44)? I was under the impression that with S-ON you cannot flash RUU, is that not correct? In the current state, I have to just re-lock bootloader and I can install the official HTC released update? And after which all my data will be wiped, including the custom recovery (TWRP) and root, all of this will be gone? (which is fine) I just have been researching and see that bricking the device is more likely to happen if the device is S-ON and you attempt to flash.
Click to expand...
Click to collapse
With S-ON
As far as i have read, you can:
Update to a newer firmware. (but i don't really know if you can flash another htc one rom model, eg. flash an m7 rom into a m7att phone)
Reflash the same stock firmware via recovery (http://www.htc1guru.com/downloads)
YOU CAN NOT DOWNGRADE.
Install CWM Recovery or TWRP Recovery.
Root.
mpjoe2000 said:
-snip-
Click to expand...
Click to collapse
I am very sure, I still have the zip in my downloads folder, however, Rumrunner has been updated to be universal across most firmwares, this should include 1.26.502.15 because there was a version of rumrunner for it previously. Just go to rumrunner.us and follow their instructions.
LightSpeedIII said:
I am very sure, I still have the zip in my downloads folder, however, Rumrunner has been updated to be universal across most firmwares, this should include 1.26.502.15 because there was a version of rumrunner for it previously. Just go to rumrunner.us and follow their instructions.
Click to expand...
Click to collapse
you are right!!! i have a linux firewall old pc at home + a tplink open-wrt firmware, and i had to connect my modem's internet device directly to my pc to allow rumrunner to work properly!
No problem, glad I could help