[Q] Do I need an RUU? - T-Mobile HTC One (M7)

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.

Related

[Q] Restore stock and unroot?

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.

[Q] How to get Stock Rom back ???

Hey Guys I've bought a HTC one x+ in Germany which I rooted time ago. Now I just want to unroot my device to get the original HTC Sense 5 Android 4.2.2 update. My problem is I dont have a any backups nor find any RUU with the following CID version: 1.17.206.1
My HBOOT Version is 1.35 , I also tried some RUU's which was canceled during the update progress since I did not have the right CID version needed.
However I'm going crazy and loosing my hope, please help me how to install the original HTC Rom.:crying::crying:
Thanks
jackson7000 said:
Hey Guys I've bought a HTC one x+ in Germany which I rooted time ago. Now I just want to unroot my device to get the original HTC Sense 5 Android 4.2.2 update. My problem is I dont have a any backups nor find any RUU with the following CID version: 1.17.206.1
My HBOOT Version is 1.35 , I also tried some RUU's which was canceled during the update progress since I did not have the right CID version needed.
However I'm going crazy and loosing my hope, please help me how to install the original HTC Rom.:crying::crying:
Thanks
Click to expand...
Click to collapse
seems like you have a phone with o2 cid, so your out of luck, there's no ruu that worsk with that version.
but there's a german forum i recently found, where you can find stock backups (including boot.img) and stock recoveries.
http://www.android-hilfe.de/root-cu...04-one-x-plus-ruu-s-fuer-htc-o2-vodafone.html
just put the backup into the right folder on your phone, make sure CWM/TWRP recognizes this backup, then flash stock boot.img in fastboot, restore stock backup in your recovery, flash stock recovery in fastboot and finally relock bootloader.
then your phone should be back to stock software.
thank you so far. another problem is I somewhere I have to delete Superuser and relock my bootloader to flash the stock rom. Thats why I deleted Superuser and locked my bootloader again. My question is now can I still flash to stock rom or do I have unlock bootloader again ?
jackson7000 said:
thank you so far. another problem is I somewhere I have to delete Superuser and relock my bootloader to flash the stock rom. Thats why I deleted Superuser and locked my bootloader again. My question is now can I still flash to stock rom or do I have unlock bootloader again ?
Click to expand...
Click to collapse
you probably need to unlock your phone again.
as soon as you restored the stock backup, everything you had on your phone except internal storage will be replaced by stock software, all settings will be reset, all userdata will be wiped!!!
so better backup/copy everything you need to your computer before you restore that backup.

[Q] help wih stock backup pre-root

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

Rooted M8 - How can I update to lollipop from 4.4.4 with s-on

I'm kind of new to rooting and flashing. But I was wondering how can I update my rooted at&t m8 4.4.4 (s-on) to the new lollipop update and stay rooted? Any help would be greatly appreciated.
natec806 said:
I'm kind of new to rooting and flashing. But I was wondering how can I update my rooted at&t m8 4.4.4 (s-on) to the new lollipop update and stay rooted? Any help would be greatly appreciated.
Click to expand...
Click to collapse
In short, you can't (update by official means and stay rooted). But its pretty easy to update, then just root again.
Couple options:
1) To OTA, you need stock ROM and stock recovery. Stock ROM means root is okay, but no system files can be missing or altered by you using the root permission (such as removing bloatware, frozen apps, added apps, etc.). You either need to put them back to stock, or revert to a stock nandroid of flash the stock 4.4.4 AT&T ROM. Then you need to find the stock recovery, flash it to the phone. At that time you can go into setting and look for the update. Unlocked bootloader is okay to OTA.
After the LP OTA installs, flash TWRP back to the phone and flash latest SuperSU to root again.
2) Another way, is to relock the bootloader and install the Lollipop RUU with your phone connected to a PC. RUU will then just update the phone to a stock LP image. This method is probably easier than tracking down the stock ROM and recovery, and getting them back on the phone. But the downside is that your data will be wiped by the RUU. Plus you have the added steps of relocking the bootloader; than unlocking again after the RUU. But I like RUU better as its a cleaner install than OTA and keeping user data (eliminates chance of random bugs caused by migrating user data).
After RUU, just flash TWRP and root again, same is the last part of method #1 above.
Thanks redpoint73. Worked liked a charm
Redpoint -
I used the RUU to update, and now I can't get the SU Binary to update.
I think my backup of the app is messing things up. I installed the latest via zip file (TWRP), and am not really rooted yet.
I'm trying a clean install (wiped cache, dalvik), so I'll see if I can get rid of the original SU app I had installed (chainfire).
Edit: Still can't get rid of SU app.
Any ideas?
DanGeorges said:
I think my backup of the app is messing things up. I installed the latest via zip file (TWRP), and am not really rooted yet.
Click to expand...
Click to collapse
Latest being what number? I would suggest SuperSU 2.46.
redpoint73 said:
Latest being what number? I would suggest SuperSU 2.46.
Click to expand...
Click to collapse
That was, indeed, my problem. I was being directed to an older version of SuperSU update.zip.
Once i grabbed the REAL latest version, it worked like a charm!
Thanks, Redpoint.
redpoint73 said:
In short, you can't (update by official means and stay rooted). But its pretty easy to update, then just root again.
Couple options:
1) To OTA, you need stock ROM and stock recovery. Stock ROM means root is okay, but no system files can be missing or altered by you using the root permission (such as removing bloatware, frozen apps, added apps, etc.). You either need to put them back to stock, or revert to a stock nandroid of flash the stock 4.4.4 AT&T ROM. Then you need to find the stock recovery, flash it to the phone. At that time you can go into setting and look for the update. Unlocked bootloader is okay to OTA.
After the LP OTA installs, flash TWRP back to the phone and flash latest SuperSU to root again.
2) Another way, is to relock the bootloader and install the Lollipop RUU with your phone connected to a PC. RUU will then just update the phone to a stock LP image. This method is probably easier than tracking down the stock ROM and recovery, and getting them back on the phone. But the downside is that your data will be wiped by the RUU. Plus you have the added steps of relocking the bootloader; than unlocking again after the RUU. But I like RUU better as its a cleaner install than OTA and keeping user data (eliminates chance of random bugs caused by migrating user data).
After RUU, just flash TWRP and root again, same is the last part of method #1 above.
Click to expand...
Click to collapse
What is required to run a RUU? I'm completely stock 4.4.4
redpoint73 said:
In short, you can't (update by official means and stay rooted). But its pretty easy to update, then just root again.
Couple options:
1) To OTA, you need stock ROM and stock recovery. Stock ROM means root is okay, but no system files can be missing or altered by you using the root permission (such as removing bloatware, frozen apps, added apps, etc.). You either need to put them back to stock, or revert to a stock nandroid of flash the stock 4.4.4 AT&T ROM. Then you need to find the stock recovery, flash it to the phone. At that time you can go into setting and look for the update. Unlocked bootloader is okay to OTA.
After the LP OTA installs, flash TWRP back to the phone and flash latest SuperSU to root again.
2) Another way, is to relock the bootloader and install the Lollipop RUU with your phone connected to a PC. RUU will then just update the phone to a stock LP image. This method is probably easier than tracking down the stock ROM and recovery, and getting them back on the phone. But the downside is that your data will be wiped by the RUU. Plus you have the added steps of relocking the bootloader; than unlocking again after the RUU. But I like RUU better as its a cleaner install than OTA and keeping user data (eliminates chance of random bugs caused by migrating user data).
After RUU, just flash TWRP and root again, same is the last part of method #1 above.
Click to expand...
Click to collapse
Would this work if i am living out side the US? i do have an AT&T simcard but still not connected to their network!
polar2792 said:
What is required to run a RUU? I'm completely stock 4.4.4
Click to expand...
Click to collapse
Backup your personal data (RUU will wipe the phone), and own a PC. That's it. RUU is intended to be run on a stock device, so nothing special is required.
---------- Post added at 11:36 AM ---------- Previous post was at 11:33 AM ----------
Boudjelal said:
Would this work if i am living out side the US? i do have an AT&T simcard but still not connected to their network!
Click to expand...
Click to collapse
Are you saying you are still using your AT&T account while living in a foreign country? In that case, you will usually not get the OTA. I think there are a few exceptions, such as roaming in Mexico or Caribbean areas. But otherwise, not OTA.
The RUU method noted above will work anywhere.

Returning M8 with S-ON, TWRP and modified kernel to Stock (has Skydragon 9.0)

Please bear with me since I'm not too experienced on this and did research on XDA to the best I could before asking. I'm planning on returning my device to stock, but I'm worried I might brick it. I'm currently running the Skydragon 9.0 rom (http://forum.xda-developers.com/att-htc-one-m8/development/rom-sd-4-0-sense7-port-sdkernel-t3062367) and toggled on quite a lot of things. Mainly, I remember allowing it to overwrite my current kernel.
My device has S-ON from what I saw on HBOOT, is using the Skydragon custom kernel, and I'm using TWRP custom recovery. I still have the RUU I downloaded from AT&T to return my device to stock 5.0.2 firmware. My question is, shall I just run the RUU and it will all be back to stock? Should I flash the stock recovery first? Should I relock the bootloader first? and if any of those are true, in what order?
The guide which seemed the most similar to me was this one http://forum.xda-developers.com/showthread.php?t=2751011 but that required S-OFF which I don't have and don't think it's a good thing to have. Could anyone point me in the right direciton? thanks!
First of all, what is your intent in returning to stock: to sell or give away the phone? Or return for warranty service?
sarxion said:
Please bear with me since I'm not too experienced on this and did research on XDA to the best I could before asking. I'm planning on returning my device to stock, but I'm worried I might brick it.
Click to expand...
Click to collapse
You won't brick the phone with s-on. You just won't.
You might screw something up, and temporarily render the phone unable to boot. But that can easily be fixed with the right knowledge; and that is not a brick.
sarxion said:
I'm currently running the Skydragon 9.0 rom (http://forum.xda-developers.com/att-htc-one-m8/development/rom-sd-4-0-sense7-port-sdkernel-t3062367) and toggled on quite a lot of things. Mainly, I remember allowing it to overwrite my current kernel.
Click to expand...
Click to collapse
On this device, flashing a custom ROM always overwrites the kernel. What you selected when you flashed the ROM, is to flash the custom SD kernel instead of flashing the "stock" HTC kernel that came with the ROM base (that Skydragon 9 is based on).
None of that matters, once you return to stock, the custom ROM (including kernel) and any other settings, tweaks, etc. will be returned to their "stock" condition.
sarxion said:
My question is, shall I just run the RUU and it will all be back to stock?
Click to expand...
Click to collapse
Will "all" be back to stock? No. The bootloader will still say RELOCKED instead of the original LOCKED condition. You need s-off to make it say LOCKED.
Also bear in mind that HTC has a record of you unlocking the bootloader, if you did it via HTCDev.com (which is most likely the case). Nothing will change that fact, and it should be disclosed to potential buyers if selling/trading the phone (that it was bootloader unlocked and modded, then returned to near-stock condition).
But everything else will be back to stock after RUU: Stock ROM, stock kernel, stock recovery, and the user data will be wiped.
sarxion said:
Should I flash the stock recovery first? Should I relock the bootloader first? and if any of those are true, in what order?
Click to expand...
Click to collapse
No need to flash stock recovery.
You will need to relock the bootloader to RUU.
Backup (move) anything you want to keep (personal photos, etc.) to your computer, etc. before RUU, as RUU will wipe the phone.
sarxion said:
The guide which seemed the most similar to me was this one http://forum.xda-developers.com/showthread.php?t=2751011 but that required S-OFF which I don't have and don't think it's a good thing to have.
Click to expand...
Click to collapse
As I've mentioned, s-off is only needed if you want to return the phone to LOCKED (instead of RELOCKED). I will agree its probably not necessary to spend $25 for s-off just to do that.
Further, the guide is very old (May 2014 - right after the phone was released) and probably before any RUU was available. It follows a much more complicated path to "return to stock" and needlessly so.
Just relock the bootloader and run the RUU, is my recommendation.
redpoint73 said:
First of all, what is your intent in returning to stock: to sell or give away the phone? Or return for warranty service?
You won't brick the phone with s-on. You just won't.
You might screw something up, and temporarily render the phone unable to boot. But that can easily be fixed with the right knowledge; and that is not a brick.
On this device, flashing a custom ROM always overwrites the kernel. What you selected when you flashed the ROM, is to flash the custom SD kernel instead of flashing the "stock" HTC kernel that came with the ROM base (that Skydragon 9 is based on).
None of that matters, once you return to stock, the custom ROM (including kernel) and any other settings, tweaks, etc. will be returned to their "stock" condition.
Will "all" be back to stock? No. The bootloader will still say RELOCKED instead of the original LOCKED condition. You need s-off to make it say LOCKED.
Also bear in mind that HTC has a record of you unlocking the bootloader, if you did it via HTCDev.com (which is most likely the case). Nothing will change that fact, and it should be disclosed to potential buyers if selling/trading the phone (that it was bootloader unlocked and modded, then returned to near-stock condition).
But everything else will be back to stock after RUU: Stock ROM, stock kernel, stock recovery, and the user data will be wiped.
No need to flash stock recovery.
You will need to relock the bootloader to RUU.
Backup (move) anything you want to keep (personal photos, etc.) to your computer, etc. before RUU, as RUU will wipe the phone.
As I've mentioned, s-off is only needed if you want to return the phone to LOCKED (instead of RELOCKED). I will agree its probably not necessary to spend $25 for s-off just to do that.
Further, the guide is very old (May 2014 - right after the phone was released) and probably before any RUU was available. It follows a much more complicated path to "return to stock" and needlessly so.
Just relock the bootloader and run the RUU, is my recommendation.
Click to expand...
Click to collapse
Thank you very much for your quick answer. I'm returning it to stock firmware to sell the device. Is it safe to lock the bootloader while Skydragon is on my device? and after that, just run the AT&T RUU and I'm done, right?
Also, do you by any chance have any resource on how to relock the bootloader? I've searched for guides on this but I the guides I find don't look very trustworthy, or don't apply, such as this one that requires S-OFF http://forum.xda-developers.com/showthread.php?t=2708571
sarxion said:
Thank you very much for your quick answer. I'm returning it to stock firmware to sell the device. Is it safe to lock the bootloader while Skydragon is on my device? and after that, just run the AT&T RUU and I'm done, right?
Click to expand...
Click to collapse
Correct. It doesn't matter what ROM is on the device when you relock the bootloader. The phone will be rendered unable to boot (may even wipe OS) when you relock.
sarxion said:
Also, do you by any chance have any resource on how to relock the bootloader? I've searched for guides on this but I the guides I find don't look very trustworthy
Click to expand...
Click to collapse
I don't know what you mean by "trustworthy". But you won't fine a "guide" because its a single fastboot command: fastboot oem lock
redpoint73 said:
Correct. It doesn't matter what ROM is on the device when you relock the bootloader. The phone will be rendered unable to boot (may even wipe OS) when you relock.
I don't know what you mean by "trustworthy". But you won't fine a "guide" because its a single fastboot command: fastboot oem lock
Click to expand...
Click to collapse
Thank you very much. So I can run the RUU with my M8 on bootloader mode? Because after relocking the bootloader, I'm asuming it probably won't even boot since it's running a custom ROM and kernel. (I'll be running the exact same RUU version I ran before installing the custom rom)
sarxion said:
So I can run the RUU with my M8 on bootloader mode?
Click to expand...
Click to collapse
The RUU will run with the phone in bootloader-fastboot mode, yes.
sarxion said:
Because after relocking the bootloader, I'm asuming it probably won't even boot since it's running a custom ROM and kernel.
Click to expand...
Click to collapse
That is correct. And in fact, as far as I know, the phone is rendered unable to boot into OS after relocking the bootloader, even if you were on the stock ROM.
OP,
Were you able to go back to stock?

Categories

Resources