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
Related
Hi,
I had my phone replace the camera because of the purple-tint problem, HTC upgraded my phone to HBoot 1.54 and android 4.2.2 without informing me . Anyway.
After receiving my phone, I unlocked my phone again by the official method, then I wanted to make a clean backup of my rom, so I tried to boot my phone to third party recovery image by "fastboot boot some_CWM.img", my phone just hung there. I was frustrated, if I flash the CWM.img to the phone, would I brick my phone? Before the upgrade, my phone could be booted in the same CWM image file, can I use third party CWM after upgrade my HBoot to 1.54?
Any idea? please
Since you have HBOOT 1.54, you cannot boot into recovery using fastboot anymore, you have to flash the recovery and then backup the ROM.
You flash the recovery by "fastboot flash recovery recovery.img"
I also recommend TWRP, its so much easier to use and if you cant find it ill attach it here if you want!
EDIT: **** This will replace your stock recovery by CWM or TWRP ****
HTC One 1.54 bootloader, flash recovery.
Hey guys, new member, and thanks for the extensive information provided on the forum!
I have a related question to what the OP posted...possibly pertinent info about the phone itself:
I have an HTC One with 1.54 bootloader, it used to be a 4.1.2 with 1.44 bootloader AT&T device, which I rooted, S-OFF, CWM etc. I then realized I couldn't take OTA updates and was stuck either on 4.1.2 or a custom ROM, so I downloaded a 4.4 stock google edition RUU and installed it. Everything is good so far, but I cannot do a full backup anymore because it has the stock recovery.
My question is, can I just flash the CWM recovery, backup the phone, and flash back the stock recovery? My goal is to get best of both worlds, get OTA updates from google as well as do a full back-up of my phone.
Please advise, and thanks in advance for your input!
PS: Since the 4.4 RUU update, my phone still says "unlocked" and "S-OFF", if that matters at all.
Krish_1 said:
Hey guys, new member, and thanks for the extensive information provided on the forum!
I have a related question to what the OP posted...possibly pertinent info about the phone itself:
I have an HTC One with 1.54 bootloader, it used to be a 4.1.2 with 1.44 bootloader AT&T device, which I rooted, S-OFF, CWM etc. I then realized I couldn't take OTA updates and was stuck either on 4.1.2 or a custom ROM, so I downloaded a 4.4 stock google edition RUU and installed it. Everything is good so far, but I cannot do a full backup anymore because it has the stock recovery.
My question is, can I just flash the CWM recovery, backup the phone, and flash back the stock recovery? My goal is to get best of both worlds, get OTA updates from google as well as do a full back-up of my phone.
Please advise, and thanks in advance for your input!
PS: Since the 4.4 RUU update, my phone still says "unlocked" and "S-OFF", if that matters at all.
Click to expand...
Click to collapse
Sure you can but the stock recovery is only needed for OTA and they don't come that often.
and your phone has to be stock with stock recovery (no apps removed).
most people just ruu back to stock for the ota... not run custom recovery just long enough to backup.
Thanks for the quick response! I think what you're saying makes sense, though I don't have a stock AT&T RUU. I'm guessing I can download it with similar firmware so I can switch as needed. Thanks again!
Krish_1 said:
Thanks for the quick response! I think what you're saying makes sense, though I don't have a stock AT&T RUU. I'm guessing I can download it with similar firmware so I can switch as needed. Thanks again!
Click to expand...
Click to collapse
here's all the ruu's you should ever need
http://www.htc1guru.com/downloads
Awesome, thanks again!
I looked around the site before posting this, didn't find anything specific. I have a Nandroid backup of the stock phone before I started messing with it. If I do a recovery of that image using CWM, is it the same as downloading and flashing one of the stock RUUs? I'm guessing not, but would like to know for sure. Is the difference that RUUs have firmware, radio etc, while a Nandroid backup is of the OS and SD card?
Krish_1 said:
Awesome, thanks again!
I looked around the site before posting this, didn't find anything specific. I have a Nandroid backup of the stock phone before I started messing with it. If I do a recovery of that image using CWM, is it the same as downloading and flashing one of the stock RUUs? I'm guessing not, but would like to know for sure. Is the difference that RUUs have firmware, radio etc, while a Nandroid backup is of the OS and SD card?
Click to expand...
Click to collapse
well for one thing when you unlock the booloader it deletes some system files when it wipes the phone.. so your stock backup is already flawed (not true stock). and like i said to take OTA you must have a complete Stock phone. the only real Stock phone comes from RUU. I hope this clears it up for you. And no your sdcard is not backed up in the Nandroid
clsA said:
well for one thing when you unlock the booloader it deletes some system files when it wipes the phone.. so your stock backup is already flawed (not true stock). and like i said to take OTA you must have a complete Stock phone. the only real Stock phone comes from RUU. I hope this clears it up for you. And no your sdcard is not backed up in the Nandroid
Click to expand...
Click to collapse
Makes perfect sense, thanks again for the super quick responses!
Hi guys, sorry in advance for digging up an old thread!
I have an AT&T HTC One, installed the Google Edition 4.4.2 with this group's help, rooted etc.
I received an OTA update from google today (4.4.3), and while I tried installing it, it crashes with a "SET_METADATA_RECURSIVE" something failed etc. I tried it with both the recovery.img that I have from the Google Edition ROM as well as the CWM recovery.
I've searched for stuff in the forum and the only thing I found is that I may need the latest version of clockworkmod, but I think I already do...I have 6.0.4.3, which is the HTC One AT&T one. Also, since I installed the Google Edition ROM, I haven't removed or uninstalled any system apps..so my phone is pretty stock as far as Google is concerned.
Can someone point me in the right direction?
Thanks!
---------- Post added at 07:10 PM ---------- Previous post was at 06:17 PM ----------
I figured it out...I had to get the recovery.img from the 4.4.2 RUU, fastboot flash the bugger into my phone (CWK didn't work), and I was able to download and install the 4.4.3 with no issues. Pissed away a few hrs trying different things, hopefully this update is worth it!!!
Krish_1 said:
Hi guys, sorry in advance for digging up an old thread!
I have an AT&T HTC One, installed the Google Edition 4.4.2 with this group's help, rooted etc.
I received an OTA update from google today (4.4.3), and while I tried installing it, it crashes with a "SET_METADATA_RECURSIVE" something failed etc. I tried it with both the recovery.img that I have from the Google Edition ROM as well as the CWM recovery.
I've searched for stuff in the forum and the only thing I found is that I may need the latest version of clockworkmod, but I think I already do...I have 6.0.4.3, which is the HTC One AT&T one. Also, since I installed the Google Edition ROM, I haven't removed or uninstalled any system apps..so my phone is pretty stock as far as Google is concerned.
Can someone point me in the right direction?
Thanks!
Click to expand...
Click to collapse
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)
Hey guys
A friend told me, he updated his htc one via OTA with just flashing stock recovery and not relocking the phone.
Is it possible?
I doubt because from the begining I have read everywhere that bootloader needs to be relocked.
Thanks for your answer,
Sent by myself, without help )
the last update worked for me without locked bootloader
arses said:
Hey guys
A friend told me, he updated his htc one via OTA with just flashing stock recovery and not relocking the phone.
Is it possible?
I doubt because from the begining I have read everywhere that bootloader needs to be relocked.
Thanks for your answer,
Sent by myself, without help )
Click to expand...
Click to collapse
Just stock recovery and unchanged stock rom, rooted is oK, bootloader doesn't matter
there is NO need for (re-)locking the bootloader in order to get the OTA.
You should just have anything stock, i.e. firmware, recovery and unmodified hboot of course.
You receive the OTA if you are UNLOCKED and S-OFF!
Thanks guys.
Sent by myself, without help )
darkarvan said:
there is NO need for (re-)locking the bootloader in order to get the OTA.
You should just have anything stock, i.e. firmware, recovery and unmodified hboot of course.
You receive the OTA if you are UNLOCKED and S-OFF!
Click to expand...
Click to collapse
OK, some dumb questions... I have a rooted stock Tmous device with 4.3 on it. The OTA obviously didn't work. I tried flashing a stock recovery I found online, but it may not have been the right one as I was never able to get it to upgrade.
So can you be specific of the steps necessary to get back to stock firmware, recovery and unmodified hboot? or is there another way to flash Kitkat easily?
I have TWRP right now, and have successfully been able to communicate with my device via ADB etc...
kendoori said:
OK, some dumb questions... I have a rooted stock Tmous device with 4.3 on it. The OTA obviously didn't work. I tried flashing a stock recovery I found online, but it may not have been the right one as I was never able to get it to upgrade.
So can you be specific of the steps necessary to get back to stock firmware, recovery and unmodified hboot? or is there another way to flash Kitkat easily?
I have TWRP right now, and have successfully been able to communicate with my device via ADB etc...
Click to expand...
Click to collapse
The T-Mobile OTA is very picky about the stock recovery. I had to run the RUU for the T-Mobile stock 4.3 which put my phone completely stock. Then it did the OTA to 4.4.2 just fine. Since I am S-OFF, it was then easy enough to unlock and root. I've since found what appears to be the recovery.img from the OTA 4.4.2 update, so when they release another OTA update, I should be able to simply flash that recovery and get the update as normal. I hope.
Fuzi0719 said:
The T-Mobile OTA is very picky about the stock recovery. I had to run the RUU for the T-Mobile stock 4.3 which put my phone completely stock. Then it did the OTA to 4.4.2 just fine. Since I am S-OFF, it was then easy enough to unlock and root. I've since found what appears to be the recovery.img from the OTA 4.4.2 update, so when they release another OTA update, I should be able to simply flash that recovery and get the update as normal. I hope.
Click to expand...
Click to collapse
Can you point me in the direction of the RUU you used? Of would you DropBox it to me (or some other file share method)?
Also, I'm currently S-On, so do you think my first step is to S-Off?
I've stayed with stock because I need WiFi calling, although I was just about to try Revolution HD 61 which supposedly has WiFi calling.
Any help is apperciated.
I didn't relock, but I did s-off
I've been trying to upgrade to 4.4 for weeks and finally figured out how to do it....
1) Installed Rumrunner to get s-off. I found Rumrunner and instructions here: http://rumrunner.us/
2) Downloaded older TMOUS firmware package that I found here: http://forum.xda-developers.com/showpost.php?p=43383588&postcount=2 and extracted recovery.img from it (to get me back to stock recovery)
3) Used Fastboot and flashed the stock recovery
4) Ran the standard update from within 4.3 and let it follow standard OTA process
5) Flashed latest TWRP via Fastboot (for some reason the openrecovery script method from the goo.im app didn't work) which I found here: http://techerrata.com/browse/twrp2/m7
Just got a new m9 been away from htc and rooting for a long time. just upgraded from my trusty galaxy s3. Is there any thing i should be aware of before unlocking boot loader and rooting. the phone is bone stock on 5.0.2 Should i let it update before unlocking boot loader and rooting. To my understanding i should unlock boot loader install twrp and don't mount the system before making a back up. Then install supersu and root or use sunshine to get root and do both.
tw39515 said:
Just got a new m9 been away from htc and rooting for a long time. just upgraded from my trusty galaxy s3. Is there any thing i should be aware of before unlocking boot loader and rooting. the phone is bone stock on 5.0.2 Should i let it update before unlocking boot loader and rooting. To my understanding i should unlock boot loader install twrp and don't mount the system before making a back up. Then install supersu and root or use sunshine to get root and do both.
Click to expand...
Click to collapse
Welcome back to HTC
It really depends on what you plan to do with your M9.
If you plan on using custom roms then yes unlock and install TWRP. Root is not required to flash roms.
Sunshine does not root or unlock but removes secure write (S-Off) which allows you to install different firmware's etc.
With S-on you can only move forward with firmware's. Lots of people complain about the 25.00, But its well worth it.
If you are not concerned about the cost, then unlock, twrp, flash superSu, and install sunshine and S-off then your free to do anything.
backup if you like but there is a thread with stock backups etc...
hope this helps
My main concern was if i want to use the phone first with out unlocking and it receives the tmobile update that i can unlock and root later.
tw39515 said:
My main concern was if i want to use the phone first with out unlocking and it receives the tmobile update that i can unlock and root later.
Click to expand...
Click to collapse
Yes you can still unlock and root and S-off on the current OS 5.1 - 2.11.531.19, but I would do it before MM comes out for this device.
will do viperone had issues on initial firmware so i flashed the latest ruu, sunshine is next. thanks for the advice.
Hi everyone,
I need some help if you may please. I bought an HTC One M9 phone and for a while it's been telling me to update to the newest android version. However, this was impossible because even when I downloaded de update from TMobile, when restarting, TWRP would kick in and wouldn't let me go through the whole setup. So, I got to some tutorials and I found some guidance but it's all so confusing and I've gotten to a point where I have no idea what to do next.
Phone is from:
-TMobile
What I did:
-Got rid of TWRP
-Got it back to unroot
Phone status as of now:
It works fine, but it's still not updated.
When going into the HTC Download mode screen, i get the following info:
-UNLOCKED
-htc_himaul PVT S-ON
-OS-1.32.531.24
-Warning: Security checking failed NOT_FIND_SMARTIO
FILE /mnt/media_rw/ext_sd/0PJAIMG.zip
File NOT FOUND
ADB is not reading my device when in download mode, I was trying to install stock recovery by following a tutorian in android soul: how to install stock recovery on htc one m9 (sorry but the forum won't let me post the link.
What do I need to do? There are so many tutorials out ther with so many different instructions that I'm totally confused now as to what to install or not to install . I'd like to install the Developer version but if I have to deal with the Tmobile one, that's ok.
Thanks in advance
Umang jain
[email protected]
umangilu said:
Hi everyone,
I need some help if you may please. I bought an HTC One M9 phone and for a while it's been telling me to update to the newest android version. However, this was impossible because even when I downloaded de update from TMobile, when restarting, TWRP would kick in and wouldn't let me go through the whole setup. So, I got to some tutorials and I found some guidance but it's all so confusing and I've gotten to a point where I have no idea what to do next.
Phone is from:
-TMobile
What I did:
-Got rid of TWRP
-Got it back to unroot
Phone status as of now:
It works fine, but it's still not updated.
When going into the HTC Download mode screen, i get the following info:
-UNLOCKED
-htc_himaul PVT S-ON
-OS-1.32.531.24
-Warning: Security checking failed NOT_FIND_SMARTIO
FILE /mnt/media_rw/ext_sd/0PJAIMG.zip
File NOT FOUND
ADB is not reading my device when in download mode, I was trying to install stock recovery by following a tutorian in android soul: how to install stock recovery on htc one m9 (sorry but the forum won't let me post the link.
What do I need to do? There are so many tutorials out ther with so many different instructions that I'm totally confused now as to what to install or not to install . I'd like to install the Developer version but if I have to deal with the Tmobile one, that's ok.
Thanks in advance
Umang jain
[email protected]
Click to expand...
Click to collapse
You say you got rid of twrp and tried to flash the stock recovery but adb is not working, so what recovery is currently on the phone?
I think the simplest solution would be to run the latest RUU from your sd card since you have adb issues (most likely a driver).
This will bring you to current stock 2.11.531.19. This will wipe the device and you must use a 4-32GB sd card.
Place it on the root of the sd card and boot into download mode, vol up to update and let it run.
you can get the RUU here
tw39515 said:
My main concern was if i want to use the phone first with out unlocking and it receives the tmobile update that i can unlock and root later.
Click to expand...
Click to collapse
kc6wke said:
Yes you can still unlock and root and S-off on the current OS 5.1 - 2.11.531.19, but I would do it before MM comes out for this device.
Click to expand...
Click to collapse
Wait. I just picked up an M9 myself, and my current plan is to wait until the official T-Mobile Marshmallow OTA is released before I unlock bootloader and S-OFF. My logic being that I could create then create a backup point in TWRP if I can't find a custom ROM that suitably handles T-Mobile specific features (WiFi calling, etc.) and just restore to the stock T-Mobile image.
Are you saying that updating OTA to Marshmallow could limit my ability to use Sunshine for S-OFF?
I suppose I could just S-OFF now and then RUU back to Stock T-Mobile Marshmallow once released?
edit: I'm already on Lollipop 5.1 on my M9. Am I already ****-out-of-luck for Sunshine?
Miguel_Lancaster said:
Wait. I just picked up an M9 myself, and my current plan is to wait until the official T-Mobile Marshmallow OTA is released before I unlock bootloader and S-OFF. My logic being that I could create then create a backup point in TWRP if I can't find a custom ROM that suitably handles T-Mobile specific features (WiFi calling, etc.) and just restore to the stock T-Mobile image.
Are you saying that updating OTA to Marshmallow could limit my ability to use Sunshine for S-OFF?
I suppose I could just S-OFF now and then RUU back to Stock T-Mobile Marshmallow once released?
edit: I'm already on Lollipop 5.1 on my M9. Am I already ****-out-of-luck for Sunshine?
Click to expand...
Click to collapse
Sunshine will work on the current version. We never know what will come when a new OTA's come out.
An OTA wont relock the bootloader or return it to S-ON. That is why I would recommend to do the S-off before an OTA.
kc6wke said:
Sunshine will work on the current version. We never know what will come when a new OTA's come out.
An OTA wont relock the bootloader or return it to S-ON. That is why I would recommend to do the S-off before an OTA.
Click to expand...
Click to collapse
Makes sense.
But won't unlocking the bootloader, flashing TWRP, then going S-OFF with Sunshine make it so that the newest OTA won't be accepted as an actual over-the-air update due to the altered filesystem? I know that I can still RUU, but will RUU not revert my S-OFF back to S-ON and re-lock the bootloader? Or are those things unaffected by RUU, even as an executable RUU?
Miguel_Lancaster said:
Makes sense.
But won't unlocking the bootloader, flashing TWRP, then going S-OFF with Sunshine make it so that the newest OTA won't be accepted as an actual over-the-air update due to the altered filesystem? I know that I can still RUU, but will RUU not revert my S-OFF back to S-ON and re-lock the bootloader? Or are those things unaffected by RUU, even as an executable RUU?
Click to expand...
Click to collapse
The RUU will not relock bootloader or rewrite S-On. To accept OTA, you need to have stock unmodified device.
You could run the RUU again or just unroot and flash stock recovery. The OTA will not wipe the device but the RUU will.
Hope this helps.
kc6wke said:
You say you got rid of twrp and tried to flash the stock recovery but adb is not working, so what recovery is currently on the phone?
I think the simplest solution would be to run the latest RUU from your sd card since you have adb issues (most likely a driver).
This will bring you to current stock 2.11.531.19. This will wipe the device and you must use a 4-32GB sd card.
Place it on the root of the sd card and boot into download mode, vol up to update and let it run.
you can get the RUU here
Click to expand...
Click to collapse
Thanks for this! Im having trouble with my computer and have been looking for a ruu zip all day lol. Will give this a shot on my TMOUS S-Off M9 tomorrow so I can jump to my next device.
Hey guy
So i need to update firmware currently on 1.32.531.33 on my t mobile htc one m9 s-on. I was gonna use ruu.exe from herehttp://forum.xda-developers.com/tmobile-one-m9/general/please-read-rooting-using-twrp-t3069022. To my understading this will unroot and flash stock rom and i will be able update via OTA. Am I suppose to use the 1.32.531.33exe or 2.7.531.6exe(since on trying to update it)? Do I need to be s-off to use? Will this relock my bootloader? Is there any other changes in adb I need to make. Anything else I should be on the lookout for? Planning on rerooting after update. I couldnt find a guide with this info so any help is much appreciated. Thanks!
Accidental Genius said:
Hey guy
So i need to update firmware currently on 1.32.531.33 on my t mobile htc one m9 s-on. I was gonna use ruu.exe from herehttp://forum.xda-developers.com/tmobile-one-m9/general/please-read-rooting-using-twrp-t3069022. To my understading this will unroot and flash stock rom and i will be able update via OTA. Am I suppose to use the 1.32.531.33exe or 2.7.531.6exe(since on trying to update it)? Do I need to be s-off to use? Will this relock my bootloader? Is there any other changes in adb I need to make. Anything else I should be on the lookout for? Planning on rerooting after update. I couldnt find a guide with this info so any help is much appreciated. Thanks!
Click to expand...
Click to collapse
If you are looking to upgrade to the latest 2.11.531.19, you can get the RUU here.
You do not need to S-Off unless you plan on flashing older or intl firmware, Ruu will not relock the bootloader.
keep in mind, running RUU will completely wipe the phone, so Backup.
I would
1. Run latest RUU let it boot and set up.
2. Reboot to bootloader, flash Twrp (fastboot flash recovery twrp-2.8.7.0-hima.img)
3. Reboot to recovery and flash SuperSU here.
Unless you are going to flash roms then you only need to flash the firmware and twrp and rom
You can get the firmware in my thread here
Hope this helps
kc6wke said:
If you are looking to upgrade to the latest 2.11.531.19, you can get the RUU here.
You do not need to S-Off unless you plan on flashing older or intl firmware, Ruu will not relock the bootloader.
keep in mind, running RUU will completely wipe the phone, so Backup.
I would
1. Run latest RUU let it boot and set up.
2. Reboot to bootloader, flash Twrp (fastboot flash recovery twrp-2.8.7.0-hima.img)
3. Reboot to recovery and flash SuperSU here.
Unless you are going to flash roms then you only need to flash the firmware and twrp and rom
You can get the firmware in my thread here
Hope this helps
Click to expand...
Click to collapse
Thanks! I took a chance yesterday and ran the 1.32.531.33.exe to play it safe and updated via OTA to 2.7.531.6. But for future reference is it's okay to run RUUs that are above current firmware or do you have to use the one your current firmware matches (for instance running 2.7.531.6.exe when the device firmware is on 1.32.531.33). Also will roms running on older firmware work if device firmware is on 2.11.531.19?
Accidental Genius said:
Thanks! I took a chance yesterday and ran the 1.32.531.33.exe to play it safe and updated via OTA to 2.7.531.6. But for future reference is it's okay to run RUUs that are above current firmware or do you have to use the one your current firmware matches (for instance running 2.7.531.6.exe when the device firmware is on 1.32.531.33). Also will roms running on older firmware work if device firmware is on 2.11.531.19?
Click to expand...
Click to collapse
With S-on you can only use current of newer firmware.
They might, depends the roms base.
Hey guys,
I just got HTC ONE M9 T-Mobile version. I'm trying to unlock it. Saw a bunch of stuff online and keep trying everything what is out there. Tried to unlock it from htcdev but it says token is too long. I copied it multiple times the way it was described, still nothing happened. Copied it piece by piece, typed it... nothing worked same thing. Questions is this, I can't get it to root, unlock bootloader, s-off or any of that so what's going to happen if I install a RUU which is rooted so at least I'll have a start cause now I can't do ANYTHING. Whatever ideas you have, please let me know.
I tried htcdev, sunshine, kingroot, kingoroot, supersu, root apps.... nothing. The tmobile unlock app, no chance... Thanks
dohcvtec said:
Hey guys,
I just got HTC ONE M9 T-Mobile version. I'm trying to unlock it. Saw a bunch of stuff online and keep trying everything what is out there. Tried to unlock it from htcdev but it says token is too long. I copied it multiple times the way it was described, still nothing happened. Copied it piece by piece, typed it... nothing worked same thing. Questions is this, I can't get it to root, unlock bootloader, s-off or any of that so what's going to happen if I install a RUU which is rooted so at least I'll have a start cause now I can't do ANYTHING. Whatever ideas you have, please let me know.
I tried htcdev, sunshine, kingroot, kingoroot, supersu, root apps.... nothing. The tmobile unlock app, no chance... Thanks
Click to expand...
Click to collapse
I'm still an amateur myself but here is my understanding and recommendations.
RUU will update firmware and flash stock rom basically bringing you back to square one. You should be able to use it with a locked bootloader. If you can't do anything with the phone I would suggest to to use RUU dot exe of the latest firmware and update all OTAs. I used a video guide on youtube by "sakitech" when I rooted mine. Just search "root HTC One m9" it should be the first link. Make sure you're copying no more no less than your token ID. Hope this helps
You're way ahead of yourself, RUU is not rooted. It's a completely stock system. Like if you were to buy a brand new phone. It will wipe your phone completely too, nothing on sdcard.
Sent from my SM-N920T using Tapatalk
Hey guys,
Thank you very much for responding.
So what would be the best thing for me to do?