Hi,
HTC flyer user here - using it as a telephone
I've just read that there should be automatic upgrade for HTC Flyer for Europe withing few weeks. My flyer (as probably most of You here) is rooted and S-OFF'ed.
Here's the history :
1. Bought HTC Flyer
2. HBOOT version was 1.07 so it was not supported by revolutionary.io tool
3. Automatically upgraded to newest software by gingerbread's built-in update so HBOOT changed to 1.10 so i could ROOT and S-OFF my flyer
Now here comes the question - what will happen if Honeycomb update appears ? Can I safely do it without any danger that my tablet will become brick or something ? Will it still be S-OFF'ed ?
regards
I don't know how senior and experienced users think but to my thought, it original FOTA update may result an error for s-off and rooted Flyer. 2 weeks ago when I was using my Flyer like you do, there appeared an OTA update and I said "yes" by mistake. It gave an error, resulting a problem in the GSM interface (like "call" or "stop call" keys disappeared etc)
Better to s-on and unroot to apply an original FOTA.
Please share your news source.
If you install a OTA RUU you will certainly lose s-off and root. I'm sure there will be custom installs, non-ota that will fix root and s-off. In fact the current HC leak is already rooted,
So if I download theatest leak and run it I will be rooted?
Yes it's already rooted
I have S-OFF and had issues installing the OTA security fix last month. I had to downloading it officially (as if I were going to complete the OTA) and then select 'install later'
Booted into recovery and then installed the zip (in downloads) from there. It seemed to work okay..
adaimespechip said:
I have S-OFF and had issues installing the OTA security fix last month. I had to downloading it officially (as if I were going to complete the OTA) and then select 'install later'
Booted into recovery and then installed the zip (in downloads) from there. It seemed to work okay..
Click to expand...
Click to collapse
Hmm, that might be a good way of installing OTAs. Thanks for that hint.
DigitalMD said:
Please share your news source.
If you install a OTA RUU you will certainly lose s-off and root. I'm sure there will be custom installs, non-ota that will fix root and s-off. In fact the current HC leak is already rooted,
Click to expand...
Click to collapse
Root maybe, S-OFF no. We have overwrite protection in the Revolutionary hboots
You'd have to dd in an unsigned stock hboot to overwrite the revolutionary hboot.
globatron said:
Root maybe, S-OFF no. We have overwrite protection ine the Revolutionary hboots
You'd have to dd in an unsigned stock hboot to overwrite the revolutionary hboot.
Click to expand...
Click to collapse
HUmm, you are correct. Won't that cause a boot issue if you manage to install a OTA that requires a different hboot?
DigitalMD said:
HUmm, you are correct. Won't that cause a boot issue if you manage to install a OTA that requires a different hboot?
Click to expand...
Click to collapse
It could but you don't really want an OTA that steals S-OFF anyway, far better to have to restore your backup and make a decision to go back to a stock HBOOT than possibly to permanently lose S-OFF. It's not such a big deal with the new hboots and the unlocker, but before that would mean the end of root, custom recovery and full backups.
Related
hi,all!
I root my Aria with unrevoked,but hboot screen still S-ON.
how to S-Off my Aria?
leyan22 said:
hi,all!
I root my Aria with unrevoked,but hboot screen still S-ON.
how to S-Off my Aria?
Click to expand...
Click to collapse
That feature has not been made available for the Aria as of yet. If you notice all of the phones that Unrevoked has S-OFF for are CDMA phones (Sprint, Verizon, US Celluar, etc.)
any other way to S-Off HTC G9?
Is there any update on how to S-Off the HTC Aria?
rvonins said:
Is there any update on how to S-Off the HTC Aria?
Click to expand...
Click to collapse
not yet, but look here......alpharev.nl
What exactly would this enable/allow?
whynot_ said:
What exactly would this enable/allow?
Click to expand...
Click to collapse
S-OFF (security off) unlocks the NAND on the phone and would allow you to flash new zip and img files to your Aria such as ROMs and custom recovery images.
tpbklake said:
S-OFF (security off) unlocks the NAND on the phone and would allow you to flash new zip and img files to your Aria such as ROMs and custom recovery images.
Click to expand...
Click to collapse
Would that still be possible with the AT&T update installed, or would that overwrite the S-OFF? Just trying to get all my ducks in a row
whynot_ said:
Would that still be possible with the AT&T update installed, or would that overwrite the S-OFF? Just trying to get all my ducks in a row
Click to expand...
Click to collapse
So far those HTC devices that they have been able to achieve S-OFF have been unaffected by new HBOOT, thus they are still rootable, but I wouldn't take a chance by going and installing the AT&T Froyo update and hoping that an S-OFF solution will be found.
Check out http://unrevoked.com/forever for a better explanation about S-OFF.
I wasn't going to install, but was just curious. Thanks for the link.
hxxp://modmymobile.com/forums/666-htc-aria/562661-guide-s-off-root-aria-2-2-2-a.html
(replace hxxp with http)
I think this site has given all instructions to do the S-Off and then root.
I have not tried it yet, but will be doing so soon
very useful information
I just did it last night by using the how to by zedbra......
check it out:
http://forum.xda-developers.com/showthread.php?t=1122574
http://forum.xda-developers.com/showthread.php?t=1159237
This thread is regarding RUU for HTC devices.
I've seen some similar threads but could not fully get the answer I was looking for.
From what I already understand, a RUU updates the ROM, the H-BOOT possibly and updates the recovery with a stock recovery. It cannot do anything that a BL-Unlocked user cannot do through adb or fastboot because the RUU uses only adb and fastboot. This means that the RUU does not (And cannot) update the radio. Am I correct in this?
And if so, what is the point of updating the RUU once you start flashing custom ROMs because they also flash the /system and /boot partitions and the only thing a custom ROM doesn't do is reflash the H-BOOT and the recovery.
And even if you update using a RUU for some reason (Whether it updates or if you just want to return to stock), do you have to choose the RUU that exactly matches your current radio version?
Assume for all the questions that the device is either BL-Unlocked or Stock (But S-ON either way).
Thanks in advance.
AceRoom said:
This thread is regarding RUU for HTC devices.
I've seen some similar threads but could not fully get the answer I was looking for.
From what I already understand, a RUU updates the ROM, the H-BOOT possibly and updates the recovery with a stock recovery. It cannot do anything that a BL-Unlocked user cannot do through adb or fastboot because the RUU uses only adb and fastboot. This means that the RUU does not (And cannot) update the radio. Am I correct in this?
And if so, what is the point of updating the RUU once you start flashing custom ROMs because they also flash the /system and /boot partitions and the only thing a custom ROM doesn't do is reflash the H-BOOT and the recovery.
And even if you update using a RUU for some reason (Whether it updates or if you just want to return to stock), do you have to choose the RUU that exactly matches your current radio version?
Assume for all the questions that the device is either BL-Unlocked or Stock (But S-ON either way).
Thanks in advance.
Click to expand...
Click to collapse
Hi, an ruu updates what you mentioned and a lot more. It will do things like change the splash screen, update the radio. and change the hboot which you cannot do with only an unlocked bootloader. It can do those things because its signed.
I had to use ruu's a few times, recently for an hboot downgrade to achieve s-off. Now that I have s-off I can flash any file I want in hboot asblong as its named correctly. Like a splash screen, or a lower hboot version.
Since an ruu updates the radio, it doesn't matter which version you choose, as long as its the same version you have or higher, but it won't let you flash a lower versionWith s-off I can flash any ruu version I want.
ok, so if I am currently running 2.3.4 and htc sense 3.0, does that mean that I can flash my phone with ics (4.0) as long as it is for the right phone and carrier???
HTC evo 3D with Rogers
icecursor said:
ok, so if I am currently running 2.3.4 and htc sense 3.0, does that mean that I can flash my phone with ics (4.0) as long as it is for the right phone and carrier???
HTC evo 3D with Rogers
Click to expand...
Click to collapse
Yes.
Theonew said:
Yes.
Click to expand...
Click to collapse
now, if I upgrade it through the ruu, is that the exact same upgrade that comes from the carrier? As in, even the HTC update too?
And if it is, is the ruu just the rooted phones way of updating?
Thanks
icecursor said:
now, if I upgrade it through the ruu, is that the exact same upgrade that comes from the carrier? As in, even the HTC update too?
And if it is, is the ruu just the rooted phones way of updating?
Thanks
Click to expand...
Click to collapse
Yes it is the same update. Updating with the RUU can be used either way (rooted or non-rooted). Just keep in mind that you'll lose root access after updating.
Theonew said:
Yes.
Click to expand...
Click to collapse
Theonew said:
Yes it is the same update. Updating with the RUU can be used either way (rooted or non-rooted). Just keep in mind that you'll lose root access after updating.
Click to expand...
Click to collapse
ok, so last question,
do I need hboot 1.5? I am currently running revolutionary s-off, HBOOT 1.49.1107.
Originally Posted by Theonew
Yes.
Click to expand...
Click to collapse
Originally Posted by Theonew
Yes it is the same update. Updating with the RUU can be used either way (rooted or non-rooted). Just keep in mind that you'll lose root access after updating.
Click to expand...
Click to collapse
ok, so last question,
do I need hboot 1.5? I am currently running revolutionary s-off, HBOOT 1.49.1107.
Click to expand...
Click to collapse
I'm not sure for your device, but as long as the RUU is for it, it should work (boot loader version doesn't usually affect it).
hello, i wanted to know if RUU also achieves S-ON. I need to return my droid incredible to verizon for replacement due to screen malfunction. I cannot see anything on the display, but everything inside works fine.
I had unlocked bootloader using htcdev and rooted with S-OFF running 4.1.1. I am now on stock Froyo thanks to RUU, but I still need to get S-ON and bootloader locked.
So does the RUU achieve S-ON? I have downloaded the forever SON zip file. But I dont know how to flash it using ADB. Can someone guide me.
haunteddevil619 said:
hello, i wanted to know if RUU also achieves S-ON. I need to return my droid incredible to verizon for replacement due to screen malfunction. I cannot see anything on the display, but everything inside works fine.
I had unlocked bootloader using htcdev and rooted with S-OFF running 4.1.1. I am now on stock Froyo thanks to RUU, but I still need to get S-ON and bootloader locked.
So does the RUU achieve S-ON? I have downloaded the forever SON zip file. But I dont know how to flash it using ADB. Can someone guide me.
Click to expand...
Click to collapse
The RUU does not return S-ON. What is in the zip file?
achieve S-ON on htc...
haunteddevil619 said:
hello, i wanted to know if RUU also achieves S-ON. I need to return my droid incredible to verizon for replacement due to screen malfunction. I cannot see anything on the display, but everything inside works fine.
I had unlocked bootloader using htcdev and rooted with S-OFF running 4.1.1. I am now on stock Froyo thanks to RUU, but I still need to get S-ON and bootloader locked.
So does the RUU achieve S-ON? I have downloaded the forever SON zip file. But I dont know how to flash it using ADB. Can someone guide me.
Click to expand...
Click to collapse
for S-ON try this Post ...
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
My device is stock, unrooted, S-On, AT&T. I want to get the new software pieces from the OTA update without taking the actual OTA itself because I do not want to update HBoot in case I decide to do S-Off again in the future. Is there a file or set of files I can install from the outside? Or can I flash just the new radio, or even get the phone to quit bugging me about the update?
My HBoot is 1.44, May 2013. My roommate has the same setup but he took the OTA and now his HBoot is 1.44, June 2013 and revone doesn't work on that version.
K.AuthoR said:
My device is stock, unrooted, S-On, AT&T. I want to get the new software pieces from the OTA update without taking the actual OTA itself because I do not want to update HBoot in case I decide to do S-Off again in the future. Is there a file or set of files I can install from the outside? Or can I flash just the new radio, or even get the phone to quit bugging me about the update?
My HBoot is 1.44, May 2013. My roommate has the same setup but he took the OTA and now his HBoot is 1.44, June 2013 and revone doesn't work on that version.
Click to expand...
Click to collapse
Just flash the stock 1.26.502.15 ROM from this thread. It doesn't contain any firmware files so your firmware will remain untouched.
K.AuthoR said:
My device is stock, unrooted, S-On, AT&T. I want to get the new software pieces from the OTA update without taking the actual OTA itself because I do not want to update HBoot in case I decide to do S-Off again in the future. Is there a file or set of files I can install from the outside? Or can I flash just the new radio, or even get the phone to quit bugging me about the update?
My HBoot is 1.44, May 2013. My roommate has the same setup but he took the OTA and now his HBoot is 1.44, June 2013 and revone doesn't work on that version.
Click to expand...
Click to collapse
I wouldn't wait to s-off if I were you. That update will end up running when you least expect it and then you're done.
jdk2 said:
I wouldn't wait to s-off if I were you. That update will end up running when you least expect it and then you're done.
Click to expand...
Click to collapse
I might as well.
My concern is, if I S-Off, can I then accept the OTA? Or how could I go about updating everything EXCEPT for HBoot?
K.AuthoR said:
I might as well.
My concern is, if I S-Off, can I then accept the OTA? Or how could I go about updating everything EXCEPT for HBoot?
Click to expand...
Click to collapse
S-Off doesn't affect OTA's. You just need stock recovery to accept them. But if that update installs to your phone, there's no telling when S-Off may be available. Once you're S-Off, you can flash anything and you'll remain S-Off.
jdk2 said:
S-Off doesn't affect OTA's. You just need stock recovery to accept them. But if that update installs to your phone, there's no telling when S-Off may be available. Once you're S-Off, you can flash anything and you'll remain S-Off.
Click to expand...
Click to collapse
Gotcha, excellent!
(first HTC Android device after coming from nothing but Nexus devices, so HTC's setup is totally foreign to me)
I just went ahead with the S-Off. Am I good to accept this OTA or will this override HBoot / return me to S-On? Or what if it runs while I'm asleep one night, would that screw me?
K.AuthoR said:
Gotcha, excellent!
(first HTC Android device after coming from nothing but Nexus devices, so HTC's setup is totally foreign to me)
I just went ahead with the S-Off. Am I good to accept this OTA or will this override HBoot / return me to S-On? Or what if it runs while I'm asleep one night, would that screw me?
Click to expand...
Click to collapse
Once you're S-Off, you remain S-Off until you change it. Accepting OTA at this point won't change that.
You can also manually update firmware and ROM.
Sent from my HTC One using xda app-developers app
ilal2ielli said:
Once you're S-Off, you remain S-Off until you change it. Accepting OTA at this point won't change that.
You can also manually update firmware and ROM.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Question, I understand the need for stock recovery to attain the OTA. I'm already s-off and Super CID and the like. What I'd like to know is the best method for flashing just the stock recovery to receive the OTA. Also, would having the device rooted, with bloatware removed, effect the device in any way, during installation of the OTA, or after?
Or on the other hand, would it just be best to manual flash the rom from here? I'd like to pretty much attain the all of the aspects of the rom, including firmware, radio etc. I'm wary of changing the H-Boot, even though i'm already s-off. I'd hate to fall into a situation later where I need to go s-on, then turn around and want to do s-off again, but can't, because of the h-boot change. I am trying to read up on everything as best as i can, but some of it is quite confusing, and i don't keep up with the forums like I used to. So I'd totally apprecate a little clarification. thanks.
Hey,
Doing some work on a friends device. He brought it in said that he bought the device a while ago and it was custom and wanted to simply return to stock so he could update to the newest firmware. Normally I can search and find the answers I need but Im stumped at the moment.
So when he brought it to me, the system was in this state:
Bootloader - UNLOCKED
S-ON
HBOOT - 1.44
Recovery - CWM
ROM - CleanRom1.0
Android Version 4.2
So I figured I would relock the bootloader and run an RUU to bring him back to stock. I used "RUU_M7_UL_JB_50_Cingular" to bring him back to stock. It actually brought the device back to 4.1.2 which is what I believe it was on when it was rooted and customized in the first place. Anyhow, I popped my ATT card in there and hit software update and it downloaded it, restarted, and when it came back up, its still on 4.1.2?? And the software update and ATT software update section both say the device is up to date.
Then I downloaded the latest stock RUU which is - "RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R10_Radio_4T.24.3218.09_10.26.1718.01L_release_356565_signed_2"
Ran that and it tells gives me and error saying that I should download the correct image file.
So my question to you is, do I need to unlock the bootloader again and gain S-OFF to run this RUU properly? I was under the impression that once the device was back to stock, I could update it again. My goal here is to get this phone on KitKat for him.
Current System State -
Bootloader - RELOCKED
S-ON
HBOOT - 1.44
Recovery - STOCK? Just get a phone with a red triangle with an ! in the middle.
ROM - Stock
Android Version - 4.1.2
Thanks in advance.
I would recommend trying to S-OFF the device first, before updating anything. The current S-OFF tools may not work after the latest updates. Try Firewater w/ the temproot method first. Once you get S-OFF you have more options to update.
I've seen a few posts lately where the latest AT&T 4.4 RUU isn't working for some people (see this thread: http://forum.xda-developers.com/showthread.php?t=2723785). I'm planning on trying it this weekend. If it doesn't work for me, my plan is to run the 4.3 RUU from here then install the OTA, either through "Software Updates" on the phone or install it manually.
sharksfan7 said:
I would recommend trying to S-OFF the device first, before updating anything. The current S-OFF tools may not work after the latest updates. Try Firewater w/ the temproot method first. Once you get S-OFF you have more options to update.
I've seen a few posts lately where the latest AT&T 4.4 RUU isn't working for some people (see this thread: http://forum.xda-developers.com/showthread.php?t=2723785). I'm planning on trying it this weekend. If it doesn't work for me, my plan is to run the 4.3 RUU from here then install the OTA, either through "Software Updates" on the phone or install it manually.
Click to expand...
Click to collapse
Yeah, I just downloaded the 4.3 update to give that a try...
My HBOOT version is 1.44 so technically, gaining S-OFF should be really easy with the HTC One Toolkit no?
digisolnc said:
Yeah, I just downloaded the 4.3 update to give that a try...
My HBOOT version is 1.44 so technically, gaining S-OFF should be really easy with the HTC One Toolkit no?
Click to expand...
Click to collapse
I would think so. I never looked at HTC One Toolkit, though so don't know what it's all about. When I was researching S-OFF, Rumrunner then Firewater were the goto tools to S-OFF. Personally, I prefer not to use toolkits. Just rather figure out the commands to run myself. But if they work for you, go for it.
digisolnc said:
Yeah, I just downloaded the 4.3 update to give that a try...
My HBOOT version is 1.44 so technically, gaining S-OFF should be really easy with the HTC One Toolkit no?
Click to expand...
Click to collapse
I was able to gain S-OFF using revone with the 1.44 version of HBOOT. Detailed instructions http://forum.xda-developers.com/showthread.php?t=2497712
sharksfan7 said:
I would think so. I never looked at HTC One Toolkit, though so don't know what it's all about. When I was researching S-OFF, Rumrunner then Firewater were the goto tools to S-OFF. Personally, I prefer not to use toolkits. Just rather figure out the commands to run myself. But if they work for you, go for it.
Click to expand...
Click to collapse
the android 4.3 ruu followed by the OTA update is the easy way to AT&T 4.4.2
http://dl3.htc.com/application/RUU_...13_10.38j.1157.04_release_334235_signed_2.exe
and the OTA is here if you want to flash it manually
http://www.androidfilehost.com/?fid=23329332407573841