Database Develop

Ota 4.3 & twrp 2.6.3.0

I am relatively new to the HTC. I am running a Stock rooted image with TWRP 2.6.3.0 recovery.
The OTA for 4.3 came down and whenever I start the install the phone reboots and ends up in twrp recovery and I do not know where to go from there. I tried searching the forums but the search is down at the moment.
Here comes the Noob question : A little help please as I am not sure where to go next?

I just asked almost the same question. One thing everyone says is don't take the OTA update.
I found a few places with the pre-rooted stock ROM update, but it does not include the firmware update, that is a separate flashable zip, but I'm not sure how to update the "Full Firmware w/o hboot, boot, recovery" without S-off. I don't know if doing the "full firmware update" will mess up my recovery/root.
http://forum.xda-developers.com/showthread.php?t=2467607
http://forum.xda-developers.com/showthread.php?p=46110767

generosity21 said:
I just asked almost the same question. One thing everyone says is don't take the OTA update.
I found a few places with the pre-rooted stock ROM update, but it does not include the firmware update, that is a separate flashable zip, but I'm not sure how to update the "Full Firmware w/o hboot, boot, recovery" without S-off. I don't know if doing the "full firmware update" will mess up my recovery/root.
http://forum.xda-developers.com/showthread.php?t=2467607
http://forum.xda-developers.com/showthread.php?p=46110767
Click to expand...
Click to collapse
I have been all over the forums looking at this and came up with squat.
If I take the OTA will I loose root? Can't seem to find an answer to that.
I was running an earlier version of twrp and thought that might be the issue but after updating twrp I am still at the same place. The sprint update notifications are still coming.
If I find something I will post it here.

Must be on stock firmware and recovery to take the update guys.... It has been posted numerous times. You must also ahve the stock kernel.
Yes you will lose root if you take the OTA, you always do. Also TWRP appears to be broken with 4.3, no responsive, etc, etc

jziggy101 said:
I am relatively new to the HTC. I am running a Stock rooted image with TWRP 2.6.3.0 recovery.
The OTA for 4.3 came down and whenever I start the install the phone reboots and ends up in twrp recovery and I do not know where to go from there. I tried searching the forums but the search is down at the moment.
Here comes the Noob question : A little help please as I am not sure where to go next?
Click to expand...
Click to collapse
you can't flash the update with custom recovery installed, you need thev stock recovery image which is posted numerous times in this forum

jziggy101 said:
The OTA for 4.3 came down and whenever I start the install the phone reboots and ends up in twrp recovery and I do not know where to go from there.
Click to expand...
Click to collapse
You have to have stock recovery to take the OTA
generosity21 said:
I just asked almost the same question. One thing everyone says is don't take the OTA update.
Click to expand...
Click to collapse
You can take the OTA if you are prepared for, and know what to do - also, don't take it if you are currently S-ON and ever want S-OFF because it comes with a new hboot.
jziggy101 said:
If I take the OTA will I loose root? Can't seem to find an answer to that.
Click to expand...
Click to collapse
Yes, you will probably lose root unless you are using the OTA preservation function of SuperSU and it works for you, but either way, it is easy to get it back.
Bottom line, how you take the OTA depends on whether you are S-ON or S-OFF, the latter is much easier. Assuming you are S-ON and running the Sprint stock ROM, here is what you need to do.
1. Flash stock recovery.
2. Lock the bootloader
3. Take the OTA update
4. Unlock the bootloader
5. Flash custom recovery (TWRP)
6. Flash root (SuperSU)
If you are S-off you can skip numbers 2 and 4.

Aldo101t said:
you can't flash the update with custom recovery installed, you need thev stock recovery image which is posted numerous times in this forum
Click to expand...
Click to collapse
Thanks for the replies. It's very confusing whether people are referencing the OTA update, or the tweaked, rooted downloadable update (http://forum.xda-developers.com/showthread.php?p=46110767). This forum should be friendly to questions when things are confusing.
Even with the two replies on this thread, it's still not clear to me if the downloadable (NOT OTA) updates can be flashed with a custom recovery, or what the procedure is for an S-On device regarding firmware and ROM updates. Sorry to offend anyone if they feel this has been answered somewhere in the forums, but it's still unclear to some of us.
EDIT: 
 @PillowMetal Thanks for the very helpful reply. I guess the next question is, is it possible to get S-Off on 1.31.651.2 without losing everything?

Kraizk said:
Must be on stock firmware and recovery to take the update guys.... It has been posted numerous times. You must also ahve the stock kernel.
Yes you will lose root if you take the OTA, you always do. Also TWRP appears to be broken with 4.3, no responsive, etc, etc
Click to expand...
Click to collapse
If your not stock ota will mess you up big time. I just rooted my HTC one on sprint with the update that was on a swap out for bad speakers . Twrp isn't responsive if you use the one in toolkit. I downloaded 2.6.3 loaded it in the data folder of toolkit installed through the toolkit and bam... I got response out of Twrp. I'll find the link and post for you guys.
Sent from my SGH-M919 using Tapatalk 4

generosity21 said:
@PillowMetal Thanks for the very helpful reply. I guess the next question is, is it possible to get S-Off on 1.31.651.2 without losing everything?
Click to expand...
Click to collapse
Not without losing everything because it requires tricking your bootloader by writing to your misc partition, then running the 1.29 RUU - http://forum.xda-developers.com/showthread.php?t=2390821

http://techerrata.com/browse/twrp2/m7wls
This is the link for people who are stock and unlocking their phone. If you're using the toolkit put it in the data folder and rename to twrp. Be careful though the other files are the same name but in capital letters! Flash it and u will have responsive twrp and rooted 4.3 ota
Sent from my SGH-M919 using Tapatalk 4
---------- Post added at 02:10 PM ---------- Previous post was at 01:34 PM ----------
Anyone having poor reception?
Sent from my SGH-M919 using Tapatalk 4

PillowMetal said:
Not without losing everything because it requires tricking your bootloader by writing to your misc partition, then running the 1.29 RUU - http://forum.xda-developers.com/showthread.php?t=2390821
Click to expand...
Click to collapse
Tried this once more, and successfully got S-off without downgrading anything, as a few others have reported.
http://forum.xda-developers.com/showthread.php?t=2314582

Brand new device Stock 1.29 Rom Uninstalled SuperSU Unrooted for Updates
PillowMetal said:
You have to have stock recovery to take the OTA
You can take the OTA if you are prepared for, and know what to do - also, don't take it if you are currently S-ON and ever want S-OFF because it comes with a new hboot.
Yes, you will probably lose root unless you are using the OTA preservation function of SuperSU and it works for you, but either way, it is easy to get it back.
Bottom line, how you take the OTA depends on whether you are S-ON or S-OFF, the latter is much easier. Assuming you are S-ON and running the Sprint stock ROM, here is what you need to do.
1. Flash stock recovery.
2. Lock the bootloader
3. Take the OTA update
4. Unlock the bootloader
5. Flash custom recovery (TWRP)
6. Flash root (SuperSU)
If you are S-off you can skip numbers 2 and 4.
Click to expand...
Click to collapse
Think I messed up a step in my attempt to return to unroot to be ready to get the 4.3 jellybean update. I was stock rom 1.29, rooted, SuperSU, twerp 2.6.3. Unlocked sim. I unistalled SuperSU using the full unroot option and relocked the bootloader. When the phone attempts to update it reboots into the bootloader straight into fastboot. Will not reboot and stay in hboot. Recovery option does nothing. Do I even want the ota 1.31? Do I just skip the OTA 1.31 and get the 4.3 jellybean update. I'm new first Android phone. Sorry for the idiocy I have portrayed here. Hope someone can help with knowledge of OTA's and Jellybean update. My problem seems so simple compared to all the other posts I read but I can't seem to figure it out on my own. Thanks everyone

upowersystems said:
Think I messed up a step in my attempt to return to unroot to be ready to get the 4.3 jellybean update. I was stock rom 1.29, rooted, SuperSU, twerp 2.6.3. Unlocked sim. I unistalled SuperSU using the full unroot option and relocked the bootloader. When the phone attempts to update it reboots into the bootloader straight into fastboot. Will not reboot and stay in hboot. Recovery option does nothing. Do I even want the ota 1.31? Do I just skip the OTA 1.31 and get the 4.3 jellybean update. I'm new first Android phone. Sorry for the idiocy I have portrayed here. Hope someone can help with knowledge of OTA's and Jellybean update. My problem seems so simple compared to all the other posts I read but I can't seem to figure it out on my own. Thanks everyone
Click to expand...
Click to collapse
Did you flash stock recovery? The OTA needs that. You did not need to unroot though. Also not sure if having an unlocked SIM interferes with OTA, never performed that myself. Since we don't have RUUs for anything later than 1.29, then yes, you will need to take the 1.31 OTA update first, then the 3.04 update.

Twerp to Stock recovery
PillowMetal said:
Did you flash stock recovery? The OTA needs that. You did not need to unroot though. Also not sure if having an unlocked SIM interferes with OTA, never performed that myself. Since we don't have RUUs for anything later than 1.29, then yes, you will need to take the 1.31 OTA update first, then the 3.04 update.
Click to expand...
Click to collapse
Darn, no I did not flash the stock recovery. Also I read another thread said I needed to unroot!lol So I was back tracing my steps to unroot, so I thought.. I did save the original backup before installing Twerp 2.6.3 and rooting so its in there if I can get to it. I really dont know how to proceed from here. There are no options in the bootloader to proceed.

Twerp vs Stock recovery
PillowMetal said:
Did you flash stock recovery? The OTA needs that. You did not need to unroot though. Also not sure if having an unlocked SIM interferes with OTA, never performed that myself. Since we don't have RUUs for anything later than 1.29, then yes, you will need to take the 1.31 OTA update first, then the 3.04 update.
Click to expand...
Click to collapse
Do I need to figure out how to flash or return to stock recovery from Twerp or can I simploy flash the 1.29 ruu back in to the device for a return to stock?

Twerp 2.6.3
PillowMetal said:
Did you flash stock recovery? The OTA needs that. You did not need to unroot though. Also not sure if having an unlocked SIM interferes with OTA, never performed that myself. Since we don't have RUUs for anything later than 1.29, then yes, you will need to take the 1.31 OTA update first, then the 3.04 update.
Click to expand...
Click to collapse
Kraizk said:
Must be on stock firmware and recovery to take the update guys.... It has been posted numerous times. You must also ahve the stock kernel.
Yes you will lose root if you take the OTA, you always do. Also TWRP appears to be broken with 4.3, no responsive, etc, etc
Click to expand...
Click to collapse
Maybe you can help. Will a re-install of the stock ruu 1.29 without removing twerp 2.6.3 and reverting to stock recovery cause issues.. Will this just completely re-install everything including stock Recovery or will twerp remain. I am running stock 1.29 rom, did save an original backup when I loaded twerp. How would I get in it to load it. Then I would not need to load the complete ruu. When I try for the ota it used to reboot to twerp. Since I unrooted it reboots to bootloader and there are NO options for load, Recovery option doesnt work. I have asked this question on several threads no one seems to know or its too simple for them to reply since I'm a newb. Thanks

upowersystems said:
Maybe you can help. Will a re-install of the stock ruu 1.29 without removing twerp 2.6.3 and reverting to stock recovery cause issues.. Will this just completely re-install everything including stock Recovery or will twerp remain. I am running stock 1.29 rom, did save an original backup when I loaded twerp. How would I get in it to load it. Then I would not need to load the complete ruu. When I try for the ota it used to reboot to twerp. Since I unrooted it reboots to bootloader and there are NO options for load, Recovery option doesnt work. I have asked this question on several threads no one seems to know or its too simple for them to reply since I'm a newb. Thanks
Click to expand...
Click to collapse
Are you S-Off? Is so, the easiest way to to get up to date for you would be to RUU back to 1.29 which will restore everything on your phone back to stock including recovery. Make sure you copy anything you want to keep off your phone's internal memory (/sdcard) because it will wipe that too.
But from there, you can then easily take the OTA update for 1.31, then take the update for 3.04. Now you have the latest and greatest and can now flash TWRP, SuperSU, and any 4.3 ROM you want. With S-Off, you do not need the bootloader unlocked, but if you want to, you can flash an old hboot 1.29 from May or earlier and use revone -u, or go through htcdev to unlock. But like I said, totally unnecessary and more of a pain for me than it is worth.
Now, if you are S-ON, that is a totally different story, you cannot flash back to 1.29 RUU unless you still on 1.29 and have not updated to 1.31 yet. If you are currently on 1.31 you will have to try and restore the backup you said you had through TWRP, flash stock recovery from fastboot, re-lock your bootloader and all kinds of other crap to get to 3.04 and unlocked and rooted again.
You would have to tell me more about what condition your phone is currently in. hboot version? recovery custom or stock? ROM version installed? S-On or S-Off, etc.

Current State
PillowMetal said:
Are you S-Off? Is so, the easiest way to to get up to date for you would be to RUU back to 1.29 which will restore everything on your phone back to stock including recovery. Make sure you copy anything you want to keep off your phone's internal memory (/sdcard) because it will wipe that too.
But from there, you can then easily take the OTA update for 1.31, then take the update for 3.04. Now you have the latest and greatest and can now flash TWRP, SuperSU, and any 4.3 ROM you want. With S-Off, you do not need the bootloader unlocked, but if you want to, you can flash an old hboot 1.29 from May or earlier and use revone -u, or go through htcdev to unlock. But like I said, totally unnecessary and more of a pain for me than it is worth.
Now, if you are S-ON, that is a totally different story, you cannot flash back to 1.29 RUU unless you still on 1.29 and have not updated to 1.31 yet. If you are currently on 1.31 you will have to try and restore the backup you said you had through TWRP, flash stock recovery from fastboot, re-lock your bootloader and all kinds of other crap to get to 3.04 and unlocked and rooted again.
You would have to tell me more about what condition your phone is currently in. hboot version? recovery custom or stock? ROM version installed? S-On or S-Off, etc.
Click to expand...
Click to collapse
Was told if I un-rooted and relocked the bootloader I should be able to update. This is a brand new phone. No data to worry about losing.
Currently:
Stock ROM 1.29, S-On, (Was rooted) Now Unrooted
Hboot 1.44 (Bootloader relocked)
Twerp Recovery (although with attempt to update to 1.31 twerp did not open as it did in prior attempts to update before unroot)
Now You have opened an interesting subject. Do I need to S-off before any updates to defeat the new hboot? New stuff is being written for the new hboot as we speak right? Read a thread last night about it. Sounded like they could s-off a 1.31 and I wouldn't need to worry about s-off'ing before upgrading. It also seems like I should be able to re load the backup of the stock recovery somehow and skip the complete load of the ruu 1.29 since I am already running it. I am probably making somethong more difficult than it needs to be but I would like to learn the little details. My first Android here. Want to learn quickly here as I Also bought the New 4g LTE Nexus 7 tablet with jelly bean. I get 4g LTE from T-mobile and just hotspot my phone.

upowersystems said:
Was told if I un-rooted and relocked the bootloader I should be able to update. This is a brand new phone. No data to worry about losing.
Currently:
Stock ROM 1.29, S-On, (Was rooted) Now Unrooted
Hboot 1.44 (Bootloader relocked)
Twerp Recovery (although with attempt to update to 1.31 twerp did not open as it did in prior attempts to update before unroot)
Now You have opened an interesting subject. Do I need to S-off before any updates to defeat the new hboot? New stuff is being written for the new hboot as we speak right? Read a thread last night about it. Sounded like they could s-off a 1.31 and I wouldn't need to worry about s-off'ing before upgrading. It also seems like I should be able to re load the backup of the stock recovery somehow and skip the complete load of the ruu 1.29 since I am already running it. I am probably making somethong more difficult than it needs to be but I would like to learn the little details. My first Android here. Want to learn quickly here as I Also bought the New 4g LTE Nexus 7 tablet with jelly bean. I get 4g LTE from T-mobile and just hotspot my phone.
Click to expand...
Click to collapse
If you don't want to go the RUU route, then the condition your phone is currently in would only require you to flash stock recovery from 1.29.651.10 (which I got from the actual OTA file). The problem is that your bootloader is now locked and your are S-ON, so you will not be able to flash stock recovery unless you unlock again. If you still have the unlock.bin file from htcdev, that will still work if was done on your current hboot version, otherwise, you would have to visit the site again. Then flash stock recovery, and relock bootloader again. Then the 1.31 update will succeed followed by the 3.04 update.
As far as S-OFF, if you ever want it, you should get it now before updating to anything - even 1.31 (as long as the date on your hboot is May 2013 or earlier). Because, you WILL get the new hboots when you update to 1.31 and 3.04 and since you are S-ON, you will be stuck with it. There is no guarantee that you will ever be able to get S-OFF again with the new hboots. People on hboot 1.54 have been waiting and clamoring for months and there has been no progress and other phones have never even been able to get S-OFF.
Using revone to S-OFF will not wipe your phone or remove anything, it does not require root, and it you do not need to be unlocked. I have performed it from the computer 3 times on Sprint phones and even have made a post about how to make it succeed. There is also a video showing how it can be done on the phone too via terminal emulator, but that method requires root.
Having S-OFF just makes life so much easier, but with it carries great responsibility because security has been turned off and you need to know what you are flashing or you can run into trouble. But as long as you can get to the bootloader, you can recover.

PillowMetal said:
You have to have stock recovery to take the OTA
You can take the OTA if you are prepared for, and know what to do - also, don't take it if you are currently S-ON and ever want S-OFF because it comes with a new hboot.
Yes, you will probably lose root unless you are using the OTA preservation function of SuperSU and it works for you, but either way, it is easy to get it back.
Bottom line, how you take the OTA depends on whether you are S-ON or S-OFF, the latter is much easier. Assuming you are S-ON and running the Sprint stock ROM, here is what you need to do.
1. Flash stock recovery.
2. Lock the bootloader
3. Take the OTA update
4. Unlock the bootloader
5. Flash custom recovery (TWRP)
6. Flash root (SuperSU)
If you are S-off you can skip numbers 2 and 4.
Click to expand...
Click to collapse
On the att variant you don't need to relock the boot loader to ota.
Sent from my XT1058 using Tapatalk 2

[Q] Verizon DE Software Upgrade Q

If I have the Verizon DE Moto X, do I need to be stock (no root) and re-locked bootloader to get software updates? Or just one or the other? Neither?
Thanks,
Mike

Mike7143 said:
If I have the Verizon DE Moto X, do I need to be stock (no root) and re-locked bootloader to get software updates? Or just one or the other? Neither?
Thanks,
Mike
Click to expand...
Click to collapse
You need stock /system partition and stock recovery. It doesn't matter whether the bootloader is locked or unlocked.

Mike7143 said:
If I have the Verizon DE Moto X, do I need to be stock (no root) and re-locked bootloader to get software updates? Or just one or the other? Neither?
Thanks,
Mike
Click to expand...
Click to collapse
To install? or to be notified and receive the update?
To receive the update you'll need to be running the "stock" Verizon firmware, rooted/unrooted and bootloader locked/unlocked doesn't matter.
For it to install successfully, to expand on what kbluhm posted...
Keep in mind that usually OTA updates will look for certain files to be present on your phone and verify their size and check sums (MD5 or the like) before the OTA update will install. If files are missing or changed, the ota update will fail. That is why "stock /system" is required.
And "stock recovery" is needed because when the phone reboots to install the update, it tries to boot to stock recovery and run the install script. The 3rd party recoveries don't seem to work, or have errors, when installing the OTA update zips.
If you've rooted with SlapMyMoto, RockMyMoto, or thel like, you may have other issues to deal with in order to take any OTA updates since those processes can touch other files/partitions on the phone which will cause problems with the OTA Updates.

So in order to install the update I need to re-flash the stock recovery over TWRP, correct? How do I go about doing this?

Ah okay, thanks guys. What a hassle. I'm unlocked and using TWRP, flashed a new boot logo, and am rooted. Probably just easiest to just SBF back to stock and re-do everything.
Thanks!

You could grab the factory image from Motorola and flash only system and recovery using fastboot. That is my plan. You can find the zip file on Motorola's site or there is a topic here on XDA.
Sent from my XT1060 using Tapatalk

guitarbedlam said:
So in order to install the update I need to re-flash the stock recovery over TWRP, correct? How do I go about doing this?
Click to expand...
Click to collapse
Mike7143 said:
Ah okay, thanks guys. What a hassle. I'm unlocked and using TWRP, flashed a new boot logo, and am rooted. Probably just easiest to just SBF back to stock and re-do everything.
Thanks!
Click to expand...
Click to collapse
There are several threads about using Fastboot to flash recovery or parts of the rom rather than having to use RSDLite and flash the SBF of everything..
Example: see option 2 in -> http://forum.xda-developers.com/showthread.php?t=2536735

KidJoe said:
There are several threads about using Fastboot to flash recovery or parts of the rom rather than having to use RSDLite and flash the SBF of everything..
Example: see option 2 in -> http://forum.xda-developers.com/showthread.php?t=2536735
Click to expand...
Click to collapse
Thus, all I'd have to flash (I'm stock unlocked rooted) is the recovery and I'd be good to install the update. Then install the custom recovery and install the superuser zip. and BAM. But first I need the whole 4.4.2 update thing...

guitarbedlam said:
Thus, all I'd have to flash (I'm stock unlocked rooted) is the recovery and I'd be good to install the update. Then install the custom recovery and install the superuser zip. and BAM. But first I need the whole 4.4.2 update thing...
Click to expand...
Click to collapse
Sure, we need the 4.4.2 update.
And as long as you didn't delete any stock apps/apk's, freeze them with Titanium Backup or something similar, or rename them manually (and forgot to rename them back)... then yes.. just flash stock recovery, take update, flash TWRP and use SuperSU to re-root.

KidJoe said:
Sure, we need the 4.4.2 update.
And as long as you didn't delete any stock apps/apk's, freeze them with Titanium Backup or something similar, or rename them manually (and forgot to rename them back)... then yes.. just flash stock recovery, take update, flash TWRP and use SuperSU to re-root.
Click to expand...
Click to collapse
You can freeze them all you want and leave them frozen. They are still there, untouched, waiting to be checked/verified against and patched/updated. Once you obtain root again and grant it to Titanium Backup it will be re-frozen.
You just can't delete, rename or swap out.....frozen apps are still right there as normal.

tcrews said:
You can freeze them all you want and leave them frozen. They are still there, untouched, waiting to be checked/verified against and patched/updated. Once you obtain root again and grant it to Titanium Backup it will be re-frozen.
You just can't delete, rename or swap out.....frozen apps are still right there as normal.
Click to expand...
Click to collapse
Interesting. One of the issues reported with the Kit Kat update was the OTA failing due to apps frozen with Titanium Backup. I only "disable" via the stock app manager, so I haven't had a problem.

Most likely those with failures had modified/deleted/renamed something else that was causing the issues and blaming it on the frozen apps. I have updated every device I've had with frozen apps. Freezing, at least in Titanium Backup, tells the OS the app is not available. In recovery, the OS is not loaded and knows nothing about frozen apps. Titanium doesn't touch the actual files so they are still present to be patched by the OTA.
Sent from my Nexus 10

Newbie to unlocking bootloader rooting and getting s-off

I have an HTC ONE on verizon.
I have been reading up on unlocking of the bootloader, rooting and achieving s-off, I have a few questions that I am hoping the XDA community can help with.
1.I am on 4.3 jellybean on my ONE will the new tool for HTC devices?
2. I just checked and the new software for the one 4.4 KitKat is out for my version of the one finally! My question is would the new tool still work if I took the 4.4 OTA update or would I loose the ability to use the new tool?
3. Also I know in this process some where that you loose everything on your phone, can someone recommend a method and/or an app to backup all of that stuff so that I do not loose it?

As for backing up your data, I'd suggest Helium. Since you're not rooyed, you will need a companion app on your computer.
Sent from my One using Tapatalk

anyone else ideas?

Noobies should not attempt to root or modify

Dont take the kk update and use firewater to unlock and get s-off. Once s-off flash a recovery and use it to backup the phone. Make sure to move the backup to your pc. Then reflash stock recovery and take the ota. Then reflash custom recovery and flash superuser with it. You would then be s-off stock rooted kitkat.

On the other hand, if you don't want S-Off (I doubt you need it), you should OTA-upgrade first to get the newest firmware for your device, then unlock and root. You should still be able to S-Off after that if you want.
If you go this route, you will lose all the contents of the phone. Helium (buggy as it is, it mostly works) a backup of SMS/call log/contacts (if they're not stored in a Google account), and a backup of /sdcard is approximately everything. Also take screenshots of what your desktop looks like, just in case you have a hard time getting that back.

You can take the ota first, it has been confirmed that firewater works on the new ota.

fenstre said:
On the other hand, if you don't want S-Off (I doubt you need it), you should OTA-upgrade first to get the newest firmware for your device, then unlock and root. You should still be able to S-Off after that if you want.
If you go this route, you will lose all the contents of the phone. Helium (buggy as it is, it mostly works) a backup of SMS/call log/contacts (if they're not stored in a Google account), and a backup of /sdcard is approximately everything. Also take screenshots of what your desktop looks like, just in case you have a hard time getting that back.
Click to expand...
Click to collapse
I agree. I doubt you will need S-OFF. You really only need it if the phone didn't allow flashing kernels, radios, and images with S-ON. But since you only need root with the HTC One, I'd suggest to stay away from S-OFF. A simple typo could brick your phone if I'm not mistaken.
Sent from my One using Tapatalk

cmlusco said:
You can take the ota first, it has been confirmed that firewater works on the new ota.
Click to expand...
Click to collapse
Are you sure? I have been reading around these forums and others and haven't heard anything? Not doubting you just don't want to take the OTA update and then loose my chance to do this to my phone?

I just Ulocked, rooted and S-offed my Freshly OTA updated to 4.4.2 One. No problems or issues.
I used :
HTCDEV to unlock
CWM for recovery and root
and FireWater to S-off
Had some hiccups along the way but nothing that came close to bricking it. Just had to change a few settings and permissions.

Asking questions in International GSM htc one will not help with a Verizon device
sent from my mobile device

cmlusco said:
You can take the ota first, it has been confirmed that firewater works on the new ota.
Click to expand...
Click to collapse
Iz3man said:
I just Ulocked, rooted and S-offed my Freshly OTA updated to 4.4.2 One. No problems or issues.
I used :
HTCDEV to unlock
CWM for recovery and root
and FireWater to S-off
Had some hiccups along the way but nothing that came close to bricking it. Just had to change a few settings and permissions.
Click to expand...
Click to collapse
I thought HTC Dev no longer worked for the htc one?

JSDragon said:
I thought HTC Dev no longer worked for the htc one?
Click to expand...
Click to collapse
Worked great for me yesterday. They emailed me a Unlock.bin file, ran it withbadb and presto unlocked.

Iz3man said:
Worked great for me yesterday. They emailed me a Unlock.bin file, ran it withbadb and presto unlocked.
Click to expand...
Click to collapse
what would you recommend for backing up all of your stuff so you can restore it after all of this?

JSDragon said:
what would you recommend for backing up all of your stuff so you can restore it after all of this?
Click to expand...
Click to collapse
I use adb backup its so far the best I've used... I didntvuse anything this go around, this one was a warranty replacement and I've been driving with my note 3... I just decided to unlock, root and soff this yesterday as a weeknight project

Iz3man said:
I use adb backup its so far the best I've used... I didntvuse anything this go around, this one was a warranty replacement and I've been driving with my note 3... I just decided to unlock, root and soff this yesterday as a weeknight project
Click to expand...
Click to collapse
Mmmmm not sure how to use that for backing up my phone.

What will an update do?

HTC One M8 - I rooted my phone, installed TWRP, S-OFF, and Titanium Backup to get rid of bloatware.
Let's say an update comes through some day from HTC for something.. should I accept it? Or what about if one day we get a newer version of Android update such as 4.5 Lollipop or whatever the next is going to be? Should I accept it?
I will have to re-root/s-off after that or what?

If you are rooted and S-OFF you should never take an OTA update this could brick your phone or damage it. Just for personal knowledge, with my rooted/S-off M8 I accidentally took an OTA update and without reading said yes to the install. My phone restarted but would not load the updater, and then powered itself off. I dodged a bullet on that one. Anyway if you are worried about getting updates the developers here at XDA usually have rooted, S-OFF safe, ROMs that can be flashed in TWRP which give you all the goodies while maintaining your root/s-off status.

captain008 said:
If you are rooted and S-OFF you should never take an OTA update this could brick your phone or damage it. Just for personal knowledge, with my rooted/S-off M8 I accidentally took an OTA update and without reading said yes to the install. My phone restarted but would not load the updater, and then powered itself off. I dodged a bullet on that one. Anyway if you are worried about getting updates the developers here at XDA usually have rooted, S-OFF safe, ROMs that can be flashed in TWRP which give you all the goodies while maintaining your root/s-off status.
Click to expand...
Click to collapse
My bootloader's unlocked and I'm S-Off. I took the OTA from the settings option on the Harman/Kardon RUU and never bricked.
OP, your bootloader and S-Off status will be unchanged when taking an OTA. However, I think most people would tell you to just flash the OTA in stock recovery or fastboot.

Since you are s-off there is never a need to take an OTA.

BD619 said:
Since you are s-off there is never a need to take an OTA.
Click to expand...
Click to collapse
To add, it should not brick you phone with s-off.
you probably have to reinstall recovery and reflash a rooted rom.

Can anyone help explain this to me? I believe I had took the OTA update(with the Extreme Power Saver) but then I rooted/s-offed with no problem...In this case, was there anything I needed to do? I just assumed everything was working so it was ok.

SlapSticka said:
Can anyone help explain this to me? I believe I had took the OTA update(with the Extreme Power Saver) but then I rooted/s-offed with no problem...In this case, was there anything I needed to do? I just assumed everything was working so it was ok.
Click to expand...
Click to collapse
I did the same. All you need to do now is install a custom recovery, but it's not required. You can still still run Stock Rooted like you are now and take all OTA's if you don't want to run a custom ROM. Just remember: OTAs and RUUs won't change your S-Off status.
Sent from my 831C using Tapatalk

brandonair95 said:
I did the same. All you need to do now is install a custom recovery, but it's not required. You can still still run Stock Rooted like you are now and take all OTA's if you don't want to run a custom ROM. Just remember: OTAs and RUUs won't change your S-Off status.
Sent from my 831C using Tapatalk
Click to expand...
Click to collapse
Thanks for clarifying! :highfive: TWRP was installed along with the root so I guess I'm set to go!

Thanks. I'm happily running ViperROM 1.6.0 and it works great. You're right. No need to take OTA updates. Uses a little more battery than stock, but no problem. I just worry if I take a trip somewhere because I have no car charger.

How are we supposed to take the StageFright update?

I have S-off and a custom recovery. If I want to update to the latest software (.7), what do I have to do? I'm guessing I only need to flash a stock recovery, lock my bootloader, and take the OTA but I want to make sure this update doesn't S-On, as it is security based. Also, since I'm S-Off, do I actually have to lock my bootloader? It's sorta a PITA to unlock again.

Interested to know the answer to this myself.

sauprankul said:
I have S-off and a custom recovery. If I want to update to the latest software (.7), what do I have to do? I'm guessing I only need to flash a stock recovery, lock my bootloader, and take the OTA but I want to make sure this update doesn't S-On, as it is security based. Also, since I'm S-Off, do I actually have to lock my bootloader? It's sorta a PITA to unlock again.
Click to expand...
Click to collapse
I tried to take the OTA on my stock rooted ROM and it wouldn't boot. My guess is root or xposed caused the issue as I've heard (after the fact) that the system partition needs to be stock. While HTC used to make OTAs that would switch s-off back to s-on, I haven't heard of them doing that recently (by recently, I mean ever on the m7). I don't think you need to relock to take the OTA, but I wasn't successful, so maybe that was the reason.

I successfully took the update with no data loss and all applications kept (s-off) by running the Xposed uninstaller zip from recovery, unrooting via superSU, and flashing the stock recovery_signed.img included in the zip in this thread. Then accepting the update, after update reapplying all these things worked flawlessly.

Joshlul said:
I successfully took the update with no data loss and all applications kept (s-off) by running the Xposed uninstaller zip from recovery, unrooting via superSU, and flashing the stock recovery_signed.img included in the zip in this thread. Then accepting the update, after update reapplying all these things worked flawlessly.
Click to expand...
Click to collapse
so looks like S-Off people just have to 1) unroot, 2) remove Xposed and 3)flash the stock recovery to take the OTA update. Will do!

sauprankul said:
so looks like S-Off people just have to 1) unroot, 2) remove Xposed and 3)flash the stock recovery to take the OTA update. Will do!
Click to expand...
Click to collapse
Unless you're me and try to do it rooted. Then, after your phone won't boot, you have to try to run the RUU and find it doesn't work right on Windows 10 (at least for me the window would just disappear/crash after accepting the licensing agreement). Then you have to find an old Windows 7 laptop. Try the latest HTC Sync and find it doesn't work. Use the "naked" adb driver which gives fastboot access, but then get error 170 when running the RUU. So, uninstall HTC Sync and find an old copy of the HTC Drivers on your hard drive. Install that and then run the RUU to go back to stock. Wait for the phone to boot, then finally take the OTA. :crying:
I'm going to update my guide to include the HTC Drivers that finally worked for me.

coal686 said:
Unless you're me and try to do it rooted. Then, after your phone won't boot, you have to try to run the RUU and find it doesn't work right on Windows 10 (at least for me the window would just disappear/crash after accepting the licensing agreement). Then you have to find an old Windows 7 laptop. Try the latest HTC Sync and find it doesn't work. Use the "naked" adb driver which gives fastboot access, but then get error 170 when running the RUU. So, uninstall HTC Sync and find an old copy of the HTC Drivers on your hard drive. Install that and then run the RUU to go back to stock. Wait for the phone to boot, then finally take the OTA. :crying:
I'm going to update my guide to include the HTC Drivers that finally worked for me.
Click to expand...
Click to collapse
Thanks for taking one for the team, coal.

Joshlul said:
unrooting via superSU.
Click to expand...
Click to collapse
I'm actually unable to do this. It just gets stuck on "Uninstalling, please wait."
I uninstalled all of my root apps, no cigar.
How do I unroot my phone if I can't do it via the app?
EDIT: disregard, I'm an idiot. Don't disable superuser before uninstalling it - SU requires root to uninstall itself LOL
EDIT 2: Also, I remember installing a custom kernel at some point. I should probably reflash the stock rom just in case (dirty of course).
EDIT 3: Aaand we have bootup! yay. Hopefully this update has more goodies than just the stagefright fix. I was thinking this would fix the mediaserver drain. I'll update this post if it does.