Related
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
Moved this question from here: http://forum.xda-developers.com/showthread.php?p=51198721
I'm currently stock, rooted, S-OFF, and TWRP recovery. I'm flashed to 3.06.651.6 firmware.
I still get the OTA notifications, and my goal is to install the latest OTA update (without RUU) so that I can preserve data. I've created a TWRP backup, but that's the extent of it.
Any help is appreciated.
Other background - I reverted back to 3.06.651.6 after flashing firmware 4.06.xxx because I could not boot normally after that or did not know how.
My bootloader says Tampered, relocked
vflock said:
Moved this question from here: http://forum.xda-developers.com/showthread.php?p=51198721
I'm currently stock, rooted, S-OFF, and TWRP recovery. I'm flashed to 3.06.651.6 firmware.
I still get the OTA notifications, and my goal is to install the latest OTA update (without RUU) so that I can preserve data. I've created a TWRP backup, but that's the extent of it.
Any help is appreciated.
Other background - I reverted back to 3.06.651.6 after flashing firmware 4.06.xxx because I could not boot normally after that or did not know how.
My bootloader says Tampered, relocked
Click to expand...
Click to collapse
Ok
I have never done an OTA or Ran an RUU personally.
To the best of my knowledge you will have to flash the stock recovery and a stock rom to be able to take the OTA.
Sidenote: You say you are re-locked...when you unlock again it's going to wipe your device.
Backup everything important to your PC then run the RUU stuff is gonna get wiped either way might as well use the RUU as it's a cleaner method.
You'll have to flash the 4.06 firmware I pointed you to from the other thread to get the required hboot.
BD619 said:
Ok
I have never done an OTA or Ran an RUU personally.
To the best of my knowledge you will have to flash the stock recovery and a stock rom to be able to take the OTA.
Sidenote: You say you are re-locked...when you unlock again it's going to wipe your device.
Backup everything important to your PC then run the RUU stuff is gonna get wiped either way might as well use the RUU as it's a cleaner method.
You'll have to flash the 4.06 firmware I pointed you to from the other thread to get the required hboot.
Click to expand...
Click to collapse
Serious Q - Am I not On the stock ROM if I never switched ROMs?
But OK, s=you're saying if I were even able to get the stock revoery reloaded, and receive the OTA, but then if i try to unloack bootloader after that I won't be able to? Also serious Q - Do you have a link on performing a good nandroid backup?
Next - if I did run the RUU, how would i quickly restore my data - just using titanium backup? is that the quickest/only way?
vflock said:
Serious Q - Am I not On the stock ROM if I never switched ROMs?
But OK, s=you're saying if I were even able to get the stock revoery reloaded, and receive the OTA, but then if i try to unloack bootloader after that I won't be able to? Also serious Q - Do you have a link on performing a good nandroid backup?
Next - if I did run the RUU, how would i quickly restore my data - just using titanium backup? is that the quickest/only way?
Click to expand...
Click to collapse
If you never changed roms then yes you are on a stock rom.
To unlock the bootloader again you would use Htc Dev again(unless you still have your unlock token) and by doing so it will wipe your phone.
Only way to nandroid is to have a custom recovery which means unocking bootloader.
I personally don't use Titanium Backup so can't answer that...I backup my phone/sdcard to my PC at least once a month (copy and paste to a folder on my PC)
So, i have a motox (xt1058) with stock rom and twrp recovery. If i receive the lolipop via OTA, can i install it? or do i have to flash the original firmware?
Thanks in advance
You will have to flash stock recovery. Uninstall any xposed modules and unfreeze/restore any system apps.
PedroAlba said:
So, i have a motox (xt1058) with stock rom and twrp recovery. If i receive the lolipop via OTA, can i install it? or do i have to flash the original firmware?
Thanks in advance
Click to expand...
Click to collapse
This is asked every time an new OTA comes out, and we get many threads started covering it.
To date...
For the Motorola X 2013, the OTA's are incremental updates. You must be on a specific previous ROM, and "step up." To put it another way... to take the 4.4.2 OTA, your phone needs to be on 4.4. To take the 4.4 OTA, your phone needs to be on the 4.2.2 w/camera fix version. To take the 4.2.2 w/camera fix OTA, your phone needs to be on the initial shipping ROM version.
None of the OTA's will install if you have TWRP recovery on your phone. Instead you get stuck in a bootloop. (mfastboot erase cache will get you out of the bootloop). You need to have stock recovery on your phone. NOTE: I don't recall what happens when using Philz or CWM as recovery.
Each OTA so far has included a "Pre-Install Verification Check", a manifest of files and their checksum/hashes which the update compares against your phone. If expected files are missing, or the wrong hash, the OTA will fail to install. - So any removed or modified "bloat", system files, etc. need to be in place. Any apps like Xposed which change /system need to be disabled/removed. In some cases Freezing apps using Titanium Backup cause the OTA to fail, and the apps need to be unfrozen. However, some have not had to unfreeze. Using the phone's app manager to disable an app (Settings -> Apps -> open app listing -> DISABLE) does not have to be undone.
If you have version mismatch between GPT.BIN or Motoboot.img and the ROM on your phone, taking an OTA WILL brick the phone. - Grab the FULL SBF for the Stock Moto ROM which matches the bootloader version on your phone, or a newer SBF (i.e. if you have the bootloader version that corresponds to 4.4.2, grab the 4.4.2 SBF or 4.4.4 SBF), and flash it via mfastboot. You may need some extra steps to flash GPT.BIN and Motoboot.img.
If you've used hacks to root/disable write protection because you have a locked bootloader, you may lose root, and wont be able to re-root until a new exploit is found. Those hacks might also get in the way of the OTA's pre-install validation checks.
If you have unlocked your bootloader via mfastboot oem unlock UNIQUECODE or Sunshine, the bootloader will not re-lock.
There have been some posts (twitter and G+) about how Lollipop poses new security features which are a challenge to rooting, even with an unlocked bootloader. Since I don't know the technical ins and outs, all I can say is.. Even with an unlocked bootloader, I wont jump on Lollipop as soon as its available, until I know if I can still root my X.
(I have a little bit more detail posted here -> http://mark.cdmaforums.com/MotoX-OTA.html)
lowvolt1 said:
You will have to flash stock recovery. Uninstall any xposed modules and unfreeze/restore any system apps.
Click to expand...
Click to collapse
For what it's worth, you don't need to uninstall the modules. Just use the Xposed Disabler zip in your SD card, then install the framework again once you've flashed /system and taken the update.
When I did updated to 4.4.4 I disabled the modules in the Xposed UI (not sure if that was necessary or not), but did not actually uninstall any of the APKs for the modules. When I reinstalled Xposed after updating, all I just turned all my modules back on and rebooted.
Call me paranoid, but whenever there is an update, I always flash back to 100% stock and then do the OTA update. Then, I'll re-root using philz recovery and restore my desktop with a backup of Nova. I'm always worried that taking an OTA update with and previous tinkering will lead to a gummed up phone.
That is just me, though.
mtpease said:
Call me paranoid, but whenever there is an update, I always flash back to 100% stock and then do the OTA update. Then, I'll re-root using philz recovery and restore my desktop with a backup of Nova. I'm always worried that taking an OTA update with and previous tinkering will lead to a gummed up phone.
That is just me, though.
Click to expand...
Click to collapse
Not really a bad practice either way, if you clear stuff out now and again. If you try to take an OTA with a modified /system partition, it usually just fails during the hash checks and never installs/modifies anything.
You started your thread title with a [q].... Perhaps the Q&A section would be the section to ask your question? ?
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.
So I've reset my HTC One back to stock 2 days ago and since then have received a lot of OTA updates.
Then I found that I had lost root.
I managed to reinstall TWRP and root today, but got another OTA update notification.
Because I don't want to lose root (and because TWRP says you should not update with custom recoveries), I'm looking for another way to update.
TWRP suggests to "wait for the developers to create a new ROM" but honestly, finding something in this forum is not easy...
My update is 6.09.401, but if there is something more recent I'll take that (but still KitKat). I've looked in the ROM collection but the latest seems to be 5.x or jump to 7.xx.
If I have to do some work (e.g. more research) please direct me to the right direction and I'll be happy to do it.
Will RUUs work? Still not clear what they are.
algiogia said:
So I've reset my HTC One back to stock 2 days ago and since then have received a lot of OTA updates.
Then I found that I had lost root.
Click to expand...
Click to collapse
Yep, you'll always loose root after an OTA update. Must ppl doesn't matter about that since it only takes a few minutes to root again.
I managed to reinstall TWRP and root today, but got another OTA update notification.
Because I don't want to lose root (and because TWRP says you should not update with custom recoveries), I'm looking for another way to update.
Click to expand...
Click to collapse
The only way to use ota update is by flashing back the stock recovery that match your version-main. Like said above, you'll loose root after an update. You can also update your phone by flashing a RUU but you'll also loose root and all your file since the RUU will make your phone stock, like if it was brand new.
TWRP suggests to "wait for the developers to create a new ROM" but honestly, finding something in this forum is not easy...
Click to expand...
Click to collapse
My update is 6.09.401,?but if there is something more recent I'll take that (but still KitKat). I've looked in the ROM collection but the latest seems to be 5.x or jump to 7.xx.
Click to expand...
Click to collapse
The latest Kitkat version is 6.09.401.12 otherwise its lollipop 7.19.401.x
I think the simplest solution since you want to stay on kitkat is to reflash your stock recovery 6.09.401.? (you didn't typed the last number), install the ota updates until you are on 6.09.401.11 or 6.09.401.12, reflash twrp and flash Supersu to re-root.
If I have to do some work (e.g. more research) please direct me to the right direction and I'll be happy to do it.
Will RUUs work? Still not clear what they are.[/QUOTE]
RUU are packages that will restore then entire phone Software and firmware partitions.
Thanks alray.
So are you saying there is not pre-rooted 6.09.401.11 ROM available to flash on the forum?
Where shall I look for it?
algiogia said:
Thanks alray.
So are you saying there is not pre-rooted 6.09.401.11 ROM available to flash on the forum?
Where shall I look for it?
Click to expand...
Click to collapse
Maybe i don't know. All roms are posted in the development section. Why not simply updating your phone and flashing Supersu again? It will take you maybe 20 min to install the update, reflash twrp and root...
alray said:
Maybe i don't know. All roms are posted in the development section. Why not simply updating your phone and flashing Supersu again? It will take you maybe 20 min to install the update, reflash twrp and root...
Click to expand...
Click to collapse
I'll have to find and flash the stock ROM first, do the updates, then flash TWRP and SuperSu.
If there is a way to flash only once why should I waste time (and increase chances of bricking the phone)?
algiogia said:
I'll have to find and flash the stock ROM first, do the updates, then flash TWRP and SuperSu.
If there is a way to flash only once why should I waste time (and increase chances of bricking the phone)?
Click to expand...
Click to collapse
You already are on the stock rom, just flash the stock recovery over twrp, install ota update(s) until you are on the desired version, flash twrp and supersu. There isn't really any chances to brick....
Code:
fastboot flash recovery your_stock_recovery.img
fastboot erase cache
fastboot reboot
Then boot the phone, install update(s). Once updated to the desired version, reflash twrp:
Code:
fastboot flash recovery twrp.img
fastboot erase cache
fastboot reboot-bootloader
Boot in twrp, install supersu 2.46.zip then reboot in the OS and you're done.
But yes if you prefer you can find a stock rooted rom of 6.09.401.11 if there is still one somewhere.