I have been trying to find a way to unroot my AT&T HTC One and revert back to stock, but I keep reading that I need a RUU and the AT&T one is now out. I have had success in unlocking and locking the boot loader, but in doing so, a nandroid backup was wiped. I currently have the bootloaded unlocked and twrp recovery with SuperSU installed, but I would like to remove SuperSU.
Is there any way to remove it for good or reflash my device to bring it back to stock?
Thanks
aophyz said:
I have been trying to find a way to unroot my AT&T HTC One and revert back to stock, but I keep reading that I need a RUU and the AT&T one is now out. I have had success in unlocking and locking the boot loader, but in doing so, a nandroid backup was wiped. I currently have the bootloaded unlocked and twrp recovery with SuperSU installed, but I would like to remove SuperSU.
Is there any way to remove it for good or reflash my device to bring it back to stock?
Thanks
Click to expand...
Click to collapse
http://www.andromods.com/unroot-locking/how-to-restore-to-stock-unbrick-unrooting-htc-one-m7.html
You have probably already read this, I'm not aware of the RUU being available for the AT&T variant yet. Where did you find it?
You have probably already read this, I'm not aware of the RUU being available for the AT&T variant yet. Where did you find it?
Click to expand...
Click to collapse
Terribly sorry, but I meant to write "not out" instead of "now out"
And yes I have read that and keep checking back every couple of days to see if the AT&T one ever shows up.
Related
I rooted my TMo HTC One (still s-on), installed TWRP, and immediately took a back up, before flashing anything else. If I need to return to stock, can I just restore said backup and re-lock the bootloader? I did NOT install any firmware updates.
Sisyphus306 said:
I rooted my TMo HTC One (still s-on), installed TWRP, and immediately took a back up, before flashing anything else. If I need to return to stock, can I just restore said backup and re-lock the bootloader? I did NOT install any firmware updates.
Click to expand...
Click to collapse
Here's a nice step-by-step guide on restoring to stock for T-Mobile. --> http://forum.xda-developers.com/showthread.php?t=2357624
I just followed the guide today and have a complete untouched, stock phone now.
I've had a lot of trouble upgrading to KitKat. After attempting to flash different image files for stock recovery/boot/system, I found it impossible to completely unroot the phone using the instructions posted because the phone kept re-rooting itself. Finally, I S-offed, wrote superCID, used the Telus RUU, applied the OTA downloaded to the phone, changed the CID back to GLOBA001 (my carrier is WindMobile). And finally! I know I relocked and unlocked the bootloader somewhere in the process, but I can't quite remember when.
Now, before I even think of re-rooting the phone or installing a custom recovery, I'd like to create a backup of the stock boot, recovery, and system. I tried running
Code:
fastboot boot openrecovery-twrp-2.7.1.1-zaracl.img
using the special KitKat TWRP. There's a message about boot.img being downloaded successfully but the phone reboots to a black screen.
I know that TWRP 2.7.1.0 downloaded from their website worked fine on my phone before I ran the RUU . So I'm not sure that the new TWRP is incompatible with my phone.
If I wanted to use adb instead, I'd need to root the phone before being able to pull the stock recovery, boot, and system images using adb shell. If I have to resort to rooting, is there any way to do so without flashing a custom recovery first? If there is, I might be able to unroot the phone afterward and make it stick. (Delete the supersu apk and su binary, right?)
I remember that the first time my phone attempted to download and apply the OTA automatically, my phone wiped itself. It was a lot of hard work to get it back to a usable state, but it was my own fault for not having a proper backup. I'd like to avoid making that mistake again, and have a stock backup handy on my computer in case there are carrier updates for my phone in the future.
To re-iterate, possible to back up stock everything without root? If not, possible to root without installing custom recovery?
You can no longer boot into a custom recovery, you have to actually flash it.
As far as having the stock recovery and boot, those are actually inside the OTA so you can pull it from there.
Since you'll have the stock recovery already, you can flash TWRP and use that to backup boot and system.
When you need to go stock, just use TWRP to restore your backup and then manually flash the stock recovery.
Since you made the device S-OFF, I recommend that if you need to lock/unlock the bootloader that you use the commands in this thread versus using the htcdev method as that wipes the /data/preload/ folder (as part of its normal /data wipe) which includes a few stock apps.
I had already re-locked the bootloader using the HTCdev method after the upgrade and before starting the thread. Do you think the potential loss of apps would cause any future OTAs to fail? If so, I don't mind re-doing the RUU (no important data on the phone right now). If not, I'll proceed with flashing TWRP.
Thanks for the tip on the alternate unlock method. I'll use that method the next time I need to re-unlock the bootloader.
EveKnight75 said:
I had already re-locked the bootloader using the HTCdev method after the upgrade and before starting the thread. Do you think the potential loss of apps would cause any future OTAs to fail? If so, I don't mind re-doing the RUU (no important data on the phone right now). If not, I'll proceed with flashing TWRP.
Thanks for the tip on the alternate unlock method. I'll use that method the next time I need to re-unlock the bootloader.
Click to expand...
Click to collapse
Locking the bootloader won't do anything, it's only unlocking using the htcdev token that causes the data wipe. So if you haven't unlocked using the htcdev method since running the RUU you will still have the 2 - 3 apps.
I don't know if the /data/preload/ folder is a requirement for a successful OTA update or not but I checked inside my OTA zip for my phone and it does include the 3 items stored there for the VM variant.
The unlock was AFTER the RUU. I ran the RUU, then used the OTA to upgrade to KitKat, then unlocked the bootloader again. However, I didn't notice any apps disappearing and the OTA zip for Wind also has a /data/preload folder.
*Shrugs* Seems good enough to me. TWRP, here I come!
needing wind stock stuck with wind awsy amd wont connect
I have an unlocked desire 601 it finds only wind away I'm trying to get a backup of the stock Rom to flash it does anyone k ow if there any around or even a back up I can use to try to get my phone working on wind home
jayjsteez said:
I have an unlocked desire 601 it finds only wind away I'm trying to get a backup of the stock Rom to flash it does anyone k ow if there any around or even a back up I can use to try to get my phone working on wind home
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2804427
needing help for s-off
EveKnight75 said:
I had already re-locked the bootloader using the HTCdev method after the upgrade and before starting the thread. Do you think the potential loss of apps would cause any future OTAs to fail? If so, I don't mind re-doing the RUU (no important data on the phone right now). If not, I'll proceed with flashing TWRP.
Thanks for the tip on the alternate unlock method. I'll use that method the next time I need to re-unlock the bootloader.
Click to expand...
Click to collapse
hey i have unlocked desire 601 but only says wind away and wont connect ive knoticed the wind version is the same as the other versions but im wondering do i need the wind rom in order for it to pick up the wind home i cant seem to find anywhere online the wind rom and everytime i try to s-off it saysfailed and ive followed everything is there any insite you could give me to help me with this issue if its fixable again my phone says wind away but wont connect to it and i need to get it working as its my only device and carrier i use thx
---------- Post added at 11:29 PM ---------- Previous post was at 11:16 PM ----------
EveKnight75 said:
I had already re-locked the bootloader using the HTCdev method after the upgrade and before starting the thread. Do you think the potential loss of apps would cause any future OTAs to fail? If so, I don't mind re-doing the RUU (no important data on the phone right now). If not, I'll proceed with flashing TWRP.
Thanks for the tip on the alternate unlock method. I'll use that method the next time I need to re-unlock the bootloader.
Click to expand...
Click to collapse
hey i have unlocked desire 601 but only says wind away and wont connect ive knoticed the wind version is the same as the other versions but im wondering do i need the wind rom in order for it to pick up the wind home i cant seem to find anywhere online the wind rom and everytime i try to s-off it saysfailed and ive followed everything is there any insite you could give me to help me with this issue if its fixable again my phone says wind away but wont connect to it and i need to get it working as its my only device and carrier i use thx
-Duir- said:
You can no longer boot into a custom recovery, you have to actually flash it.
As far as having the stock recovery and boot, those are actually inside the OTA so you can pull it from there.
Since you'll have the stock recovery already, you can flash TWRP and use that to backup boot and system.
When you need to go stock, just use TWRP to restore your backup and then manually flash the stock recovery.
Since you made the device S-OFF, I recommend that if you need to lock/unlock the bootloader that you use the commands in this thread versus using the htcdev method as that wipes the /data/preload/ folder (as part of its normal /data wipe) which includes a few stock apps.
Click to expand...
Click to collapse
I don't understand how you can pull the stock recovery from the OTA. I thought OTA's are immediately installed, instead of stored untill you want to install it? So, how do you backup the stock recovery?
It is saved until you want to install. When it go finishes Downloading, just choose install later. And you will be able to copy it into other storage devices and extract files and what not. I'm not sure if it stores in internal or external I'm 80% sure external sd if you have one.
Sent from my HTC0P4E1 using XDA Free mobile app
Hey,
I currently have a stock, rooted, s-off m8 with TWRP recovery. I have already read the thread on converting to the developer edition but I have a quick question that I could'nt find in the thread. I know that through this conversion, I will lose root so the first thing I will do after following the procedure will be to re-root the device. Since this involves installing a custom recovery, I will also lose the ability to process ota's. If I then go on to flash the stock recovery, will I still maintain root with the ability to process ota's?
Thanks!
neilmopar said:
Hey,
I currently have a stock, rooted, s-off m8 with TWRP recovery. I have already read the thread on converting to the developer edition but I have a quick question that I could'nt find in the thread. I know that through this conversion, I will lose root so the first thing I will do after following the procedure will be to re-root the device. Since this involves installing a custom recovery, I will also lose the ability to process ota's. If I then go on to flash the stock recovery, will I still maintain root with the ability to process ota's?
Thanks!
Click to expand...
Click to collapse
With S-Off, root isn't important. Yes, you will need stock recovery for OTA. Easiest way to convert is change CID to BS_0001 , run RUU from HTC, and be done with it, everything will be overwritten. I even left mine with that CID and get far better signal strength on ATT and instead of hanging on to a weak LTE like ATT does, it will switch to what it needs to. Loving it and wouldn't have it any other way.
hack14u said:
With S-Off, root isn't important. Yes, you will need stock recovery for OTA. Easiest way to convert is change CID to BS_0001 , run RUU from HTC, and be done with it, everything will be overwritten. I even left mine with that CID and get far better signal strength on ATT and instead of hanging on to a weak LTE like ATT does, it will switch to what it needs to. Loving it and wouldn't have it any other way.
Click to expand...
Click to collapse
Thanks for the response! I ended converting it earlier this evening. Could you elaborate on what you mean by saying that root doesn't matter since Im s-off? Should I just now flash a custom recovery so that I can flash the SU .zip and then reflash the stock recovery so that I can continue to get ota's?
Thanks!
S-Off is greater than root. With S-Off you can do anything. I think though that to install SU you do need root, I could be wrong though. But, once you root it again, you can unroot and reroot with a simple command. As far as the rest, yep, you got it now. You can use the custom recovery to flash / install whatever you want, and then go back to stock for OTA.
Hey everyone, I've done some research and found plenty of people trying to keep root while accepting an OTA, but couldn't find anything pertaining exactly to my question. does anyone know if i accept the next OTA from att will it unroot and remove the tampered banner on my m8? all i've done is root my device. haven't changed anything or flashed anything other than twrp recovery. just want to go back to stock as easily as possible.
thanks for any help
stumcmahan said:
Hey everyone, I've done some research and found plenty of people trying to keep root while accepting an OTA, but couldn't find anything pertaining exactly to my question. does anyone know if i accept the next OTA from att will it unroot and remove the tampered banner on my m8? all i've done is root my device. haven't changed anything or flashed anything other than twrp recovery. just want to go back to stock as easily as possible.
thanks for any help
Click to expand...
Click to collapse
You need to flash stock recovery, or the OTA won't install. In fact, you might even get stuck in a bootloop as the phone repeatedly boots into TWRP, looking for stock recovery (to install the OTA) and not finding it.
Also, if any system files have been modified by root, you need to return them to "stock" state. Otherwise the OTA will fail to install, saying the system has been modified. You can either return any system files to stock manually, or flash a stock ROM, nandroid, or RUU.
You will lose root when you OTA. But its an easy manner to just flash TWRP again, and flash SU/SuperSU to gain root. Unlocked bootloader is okay for OTA, so you don't even need to relock, unlock again, etc. to flash TWRP. But locked bootloader is required for RUU (unless you have s-off) if you choose that route in the paragraph above.
So, long story short, I recently bought a Nexus 9 from ebay which arrived with factory reset protection.
I have spoken to both Google and HTC about the situation and both were of no real help except for saying a few things outright between them to give me good enough reason to believe one of two things.
That 1 - it is possible to flash factory images over a device with a locked bootloader
or 2 - it is possible to unlock the bootloader without having access to developer settings
Anyone have any experience with either of these possibilities?
https://developers.google.com/android/ota
Full OTA Images can be flashed onto devices with locked boot loaders.
You need to boot into recovery and select sideload update.
Yeah, I know how to do that, but that only goes for updates, doesn't it? I tried to sideload a previous build onto the tablet but it failed the procedure, so it doesn't really solve the issue and if I flash a more recent update I still get FRP :/ If I wanted to revert back to the 7.0, or even marshmallow, would that be possible? Or does that require an unlocked bootloader?
enriquejones666 said:
https://developers.google.com/android/ota
Full OTA Images can be flashed onto devices with locked boot loaders.
You need to boot into recovery and select sideload update.
Click to expand...
Click to collapse
Yeah, I know how to do that, but that only goes for updates, doesn't it? I tried to sideload a previous build onto the tablet but it failed the procedure, so it doesn't really solve the issue and if I flash a more recent update I still get FRP :/ If I wanted to revert back to the 7.0, or even marshmallow, would that be possible? Or does that require an unlocked bootloader?
BigDomTheFirst said:
Yeah, I know how to do that, but that only goes for updates, doesn't it? I tried to sideload a previous build onto the tablet but it failed the procedure, so it doesn't really solve the issue and if I flash a more recent update I still get FRP :/ If I wanted to revert back to the 7.0, or even marshmallow, would that be possible? Or does that require an unlocked bootloader?
Click to expand...
Click to collapse
Those are full ota images, same as factory image. Meaning full package.
BigDomTheFirst said:
Yeah, I know how to do that, but that only goes for updates, doesn't it? I tried to sideload a previous build onto the tablet but it failed the procedure, so it doesn't really solve the issue and if I flash a more recent update I still get FRP :/ If I wanted to revert back to the 7.0, or even marshmallow, would that be possible? Or does that require an unlocked bootloader?
Click to expand...
Click to collapse
Ah yes, now I see your predicament. Unfortunately, there is no "there" there. You do need an unlocked bootloader to wipe the system clean with a factory image, and as you noted, the Full OTA Image will recover you from a system that won't boot, but it won't get rid of FRP.
enriquejones666 said:
Ah yes, now I see your predicament. Unfortunately, there is no "there" there. You do need an unlocked bootloader to wipe the system clean with a factory image, and as you noted, the Full OTA Image will recover you from a system that won't boot, but it won't get rid of FRP.
Click to expand...
Click to collapse
Exactly Hence my questions as to how do the manufacturers wipe everything and flash the new image without unlocking the bootloader? Or will it always be a trade secret?...... Hmmmm
BigDomTheFirst said:
Exactly Hence my questions as to how do the manufacturers wipe everything and flash the new image without unlocking the bootloader? Or will it always be a trade secret?...... Hmmmm
Click to expand...
Click to collapse
did we ever fix this? my bootloader is locked and no os installed. Was trying to return to factory and went thru all the flashing steps successfully then at the end locked the bootloader. Now tablet says "for development purposes only not for production use" and boots back to fastboot. It will not reboot at all
Uncleheff said:
did we ever fix this? my bootloader is locked and no os installed. Was trying to return to factory and went thru all the flashing steps successfully then at the end locked the bootloader. Now tablet says "for development purposes only not for production use" and boots back to fastboot. It will not reboot at all
Click to expand...
Click to collapse
Never found out how they do this.... are you able to boot in to recovery? if you can do that you may be able to flash a recovery OTA through 'apply update from ADB'. Worth a shot
Uncleheff said:
did we ever fix this? my bootloader is locked and no os installed. Was trying to return to factory and went thru all the flashing steps successfully then at the end locked the bootloader. Now tablet says "for development purposes only not for production use" and boots back to fastboot. It will not reboot at all
Click to expand...
Click to collapse
If up dont mind my asking how did it get that way by just locking the bootloader? I was just about to flash stock and lock on my volantis, then read this...?
Bryanx86 said:
If up dont mind my asking how did it get that way by just locking the bootloader? I was just about to flash stock and lock on my volantis, then read this...?
Click to expand...
Click to collapse
definitely don't lock your bootloader. That is a horrible move and serves no purpose
madbat99 said:
definitely don't lock your bootloader. That is a horrible move and serves no purpose
Click to expand...
Click to collapse
I actually reflashed last factory stock image and relocked without issue. It is a horrible move, I agree...I already miss root, but it suits the purpose. Thanks for your reply.
Bryanx86 said:
I actually reflashed last factory stock image and relocked without issue. It is a horrible move, I agree...I already miss root, but it suits the purpose. Thanks for your reply.
Click to expand...
Click to collapse
it's only a bad move if you make a mistake and can't repair it because your bootloader is now locked. But if it goes well then you're all set.