Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,809,924 Members 45,395 Now Online
XDA Developers Android and Mobile Development Forum

[GUIDE] How to Return to 100% Stock

Tip us?
 
crushalot
Old
(Last edited by crushalot; 21st October 2013 at 09:24 PM.) Reason: Added Extra warning before steps to lock bootloader
#1  
crushalot's Avatar
Recognized Contributor - OP
Thanks Meter 1,136
Posts: 977
Join Date: Jun 2011
Location: Raleigh

 
DONATE TO ME
Post [GUIDE] How to Return to 100% Stock

This Guide will help you reset your HTC One back to 100% stock form with no trace of modifications. S-Off Required!

In order for you to be able to reset your device to complete stock it will require that you have S-Off.
For those that still have S-On and cannot gain S-Off due to having one of the updated firmwares there is not much you can do other than restore a stock rom and stock recovery. S-On users can find my 2.24.401.x stock rom with recovery included here:
http://www.htc1guru.com/2013/09/gurureset-aroma/
I am working on more versions now.

If you restore one of the stock Nandroid backups with a 1.2x version, you will probably have issues with the touch screen not working since the updated touchscreen drivers in the newer firmware updates, prevent the touch screen from working in the stock level 4.1.2 software. Keep checking the Download section for Guru Resets as I will be adding more stock rom versions.

If you have a working touch screen on the stock software, after restoring the stock kernel and stock recovery, your bootloader will show RELOCKED instead of LOCKED once you lock it.

I have easily unlocked bootloader, got S-off and super CID for many different HTC One devices from a few carriers, but that is because they came with hboot 1.44 so revone worked without issues to gain S-Off. If you buy a new phone now, regardless if what firmware version and/or software it come with, after you unlock the bootloader be sure the first thing you do is to make a Nandroid backup of your phone in its stock form. If it is a stock Nandroid on the newer 2.24.401.x base, please contact me as I would love to host it as many people could use that if not s-off.

If you are lucky enough to buy a new phone that comes with early hboot 1.44, I advise you get S-off right after you make that stock Nandroid backup. S-off really comes in handy for so many things. There is no danger of bricking your phone unless you start flashing things you don;t understand and other actions without fully understanding the repercussions. If you are unsure about something then just make a post and someone here should be able to provide you with the correct information.

If you don稚 know what these terms mean do a search, they have been answered many, many times. Here are some quick links to some common items for modifications::
胞asily unlock bootloader, flash custom recovery, flash ROM, and ADB sideload (in case you forgot to copy your ROM to your phone) plus much more:
http://forum.xda-developers.com/show....php?t=2242635

胞asily get S-off by using revone (We will also use this tool reset Security back to S-On)
http://forum.xda-developers.com/show....php?t=2314582

***I advise you to get S-off before doing anything else and keep S-off unless you are going to return the device. The latest OTA/firmware contains an hboot that revone will not currently unlock, but if you have s-off you can downgrade your hboot if needed***

胞asily get Super CID
http://forum.xda-developers.com/show....php?t=2317536

Now you can do some of these things easily:
*Remove red warning from boot screen + custom hboot:
http://forum.xda-developers.com/show....php?t=2316726
http://forum.xda-developers.com/show....php?t=2156368

*Flash custom splash screens:
http://forum.xda-developers.com/show....php?t=2324746
*Flash new firmware:

Concise and easy for noobs: http://forum.xda-developers.com/show...postcount=5082
Also http://forum.xda-developers.com/show...ostcount=33758
Post #2 has the download for the custom firmware to flash without screwing anything else up:
http://forum.xda-developers.com/show....php?t=2182823
__________________________________________________ ____________________________________

Resetting your device to stock
覧覧覧覧覧覧覧覧覧覧覧覧
So now for the good stuff. You totally modded the hell out of your One and something happens where you need to return the device to your carrier/vendor. First thing, always go to your carrier/vendor for hardware exchanges NOT direct to HTC. For the most part US carriers don稚 care much about modded software on the devices in regards to warranty but HTC does. However just because the person in the device exchange center doesn稚 check for root, doesn稚 mean someone won稚 flag your phone when repairing it. So why take the chance, it only takes a few minutes to return to 100% stock.
Secondly unless your device is totally unusable, I advise you to call the ATT(or your carrier) warranty number and they will send you a replacement and a return shipping label, and then you have 12 days to return it. This way you can access data and settings on your first device if needed and make sure that everything is cool with your replacement before you reset your first device to stock and send it back.
As it is required for most of the modifications mentioned above these steps require that you have your devices drivers installed on your PC and also ADB. If you need help setting up ADB: http://forum.xda-developers.com/show....php?t=1427008

---Instructions for returning to 100% stock from S-off:

Before we begin please note that these instructions are for a device with S-off and the stock CID. Your CID should be stock unless you changed it in order to get a specific country/region OTA or as a lot do for flashing ease and just use Super CID.
In order to run the RUU to reset everything to stock, the CID will have to match the device for which the RUU was intended.
So you can稚 really mess anything up because if your CID is not correct the RUU will not run and not flash anything.

**-Technically if you have S-off you can run any RUU and it should run fine but your phones image won稚 be stock from your carrier if not the correct RUU. I like to set the stock CID back now so we don稚 forget. However if using another variant/RUU, since you are s-off, you can do this step after running the RUU.**

If you have stock CID or the CID matches the RUU you can proceed to step 1.
If you have any other CID you need to change it before beginning. In this example I am talking about the US ATT variant for which he stock CID is CWS__001
Code:
adb reboot-bootloader
Phone should boot to the bootloader. Now run:
Code:
fastboot oem writecid CWS__001
Now verify that the stock CID shows on the bootloader screen by running:
Code:
fastboot reboot-bootloader
Reboot device if CID on bootloader screen shows the stock CID. If not retry


*****The next step will wipe the entire contents of the device which includes all of your data. Be sure to back it up to a PC so you can transfer it onto the new device if needed.*****


These instructions are assuming you are running a Windows OS. If you are not then these exe RUU痴 won稚 be of much use. You will have to use the RUU.zip files which can accomplish the same results as a RUU from flashing in fastboot. You can replace step 1 below with these steps:
  • Restoring using a RUU.zip

Download the RUU.zip file and place in your ADB/fastboot folder. I would recommend renaming the zip file to something simple like ruu.zip.
Boot your phone into the bootloader by holding the power and vol up/down buttons at the same time until you see the bootloader screen or if you have your phone booted you can use the ADB command:
Code:
adb reboot-bootloader
Now use these fastboot commands:
Code:
fastboot oem rebootRUU
Should see the Silver HTC logo. Now issue this command to flash your phone using the ruu.zip file:
Code:
fastboot flash zip ruu.zip
Now the first time you issue a command to flash firmware/ruu in fastboot it only prepares the flash. You have to issue the exact command again:
Code:
fastboot flash zip ruu.zip
The green status bar usually does not reach the 100% mark. When the output in the command window is complete, you can reboot:
Code:
fastboot reboot
or
Code:
fastboot reboot-bootloader
**Notes about the RUU.zip method. You still need to have the proper CID for the RUU. You can run the RUU.zip with super CID, but you will have to lock your bootloader first. If you are running the RUU.zip as base to downgrade all your firmware because you are going to then going to restore a stock Nandroid so the RUU might not be made for your MID, so you may need to edit the android-info.txt inside the ruu.zip to include your MID or CID.

  • Restoring using a RUU.exe

1. - Now we need to download the RUU (ROM Update Utility) that flash our device back to mostly stock. It can be downloaded HERE for US AT&T users. Other carriers should be able to find their appropriate RUU in this thread:

http://forum.xda-developers.com/show....php?t=2428276 or here: http://www.htc1guru.com/downloads/

If there is not a RUU for your phone, but there is a Stock Nandroid backup, you should still complete the step above. Just make note of your original CID and change yours to CWS__001 so the RUU will run. This will reset all your firmware and other modifications (like modified hboot and splash screens) back to the default stock level regardless of region.
Once downloaded run the RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.1 4.3250.13_10.33.1150.01_release_318450_signed_2.ex e and it will guide you through resetting the device. After it finishes your device will be almost back to stock. It will have the stock images for recovery, boot, ROM, radio, firmware hboot, etc.

Stock Nandroid restores will require these additional steps before proceeding to step 2:

When you ran the RUU (Either EXE or ZIP) all data was wiped and your custom recovery was reset back to stock, It is recommended to keep this stock recovery in place and use a command that only works on the hboot 1.44 (which you know have form the RUU)

Download the latest version of the recovery that matches the stock Nandroid backup (Either CWM or TWRP) and place it in your ADB/fastboot folder.

Now use this command to boot that custom recovery without installing it:
Code:
fastboot boot TWRP.img   or  fastboot boot CWM.img
It should load the custom recovery. Now make a test backup and allow it to complete.

Now boot your phone (Do not take OTA updates if prompted) and look to see where exactly the recovery placed the backup. You can install a simple file manager from the play store for this. Take note of the location and folder structure that the recovery has used for the backup.

Now copy the downloaded stock backup files from your PC to that location in the last step. Be sure the folders are in the correct place.
Now reboot into the bootloader and then boot the custom recovery again using that same command as before:
Code:
fastboot boot TWRP.img   or  fastboot boot CWM.img
Restore the backup and reboot when finished. Important Do not accept any OTA updates until the complete phone reset process is finished.
Now delete all your backup files and installed applications by doing a factory reset from Settings Backup and Reset Erase All Data From Phone. Software and firmware on your phone should be back to stock and you can continue with the next step in the guide.



**Before continuing with the guide make sure you have changed your CID back to stock if you changed it to a non stock one in order to run a RUU to downgrade firmware.**

******If you continue with the next 2 steps to lock the bootloader and you do not have a stock hboot, you will instantly BRICK your device. Shouldn't be an issue if the RUU ran correctly, however you may want to boot into the bootloader and verify that it shows version 1.44.0000 for the hboot. Also your custom recovery should be gone and back to stock (If you boot into the stock recovery it will just look like a red warning triangle with no options). If you are still able to boot into your custom recovery, it is a sign that not all partitions have been flashed back to stock and you should find out why before proceeding]******

Now that we have lots of users who have S-Off from other methods than revone, mainly the new rumrunner method here are the generic instructions for any S-Off device and not just for user with revone:

Before you can proceed with the 2 following threads for removing Tampered and then Locking you need to have Superuser installed. There are links to how to do this in each thread. You can also use this toolkit. Just remember to delete the SuperUser and busybox apk if installed before you return the phone.

2. - First remove the Tampered Flag. Instructions are in this thread

http://forum.xda-developers.com/show....php?t=2477792


3. - Second Lock the bootloader. Instructions are in this thread

http://forum.xda-developers.com/show....php?t=2475914



The older REVONE commands/instructions for Tampered and Locking:

 
I recommended using revone to gain S-off, so that is how we will undo it. If you don't still have it we will need the revone file again. It can be downloaded here: http://revolutionary.io/revone (From thread: http://forum.xda-developers.com/show....php?t=2314582and http://forum.xda-developers.com/show....php?t=2315467)

Push revone to your device:
Put the downloaded revone file in your adb/fastboot folder and push it using this command:
Code:
adb push revone /data/local/tmp/
open a adb shell by typing:
Code:
adb shell
Now change to that directory:
Code:
cd /data/local/tmp
Now set permissions
Code:
chmod 755 revone
Now re-lock the bootloader:
Code:
./revone -l
Remove Tampered flag:
Code:
./revone -t
The newer revisions of revone don't do the actual locking any longer but it should output the command you need to run to fully re-lock:
Type exit to exit the adb shell session and issue the command to re-lock the device:
Code:
fastboot oem writesecureflag 3
Now verify that it worked by booting into the bootloader:
Code:
adb reboot bootloader
You should see it say LOCKED at the top and S-On, just like it was out of the box!
I doubt anyone at the warranty repair center is going to snoop around a device that says Locked and S-On, but I like to cleanup and remove the revone file.
Just reboot the phone and skip over the setup wizard
Now start another adb shell session:
Code:
adb shell
Now change back to the folder where we put revone
Code:
cd /data/local/tmp
Now run this command to delete the revone file
Code:
rm revone


Now since you had to install SuperUser to perform the previous 2 steps make sure you unroot by deleting the Superuser.apk and busybox.apk (If installed) from the /system/app folder and also the su binary from /system/xbin on your phone.

If you ran a RUU your systems firmware and software is all reset back to stock. If you restored via Stock ROM reset or Nandroid you should be running the stock software but it could be on non stock (version mismatch) firmware.


In either case your bootloader should display Locked and no Tampered just like out of the box. Now all that痴 left is to S-On. To do that issue this fastboot command:
Code:
fastboot oem writesecureflag 3
Done - device should be just like it was out of the box with no indication of any modding.



*******I am not responsible for any problems you encounter. I am simply informing you of what is needed to complete a restoration to Stock. Read all steps and commands carefully and perform them in the correct order.********

Credits/Thanks
Thanks to all those with threads I mentioned that contain great info and support. Especially scotty1223 for his Tampered removal and Locking threads.


This Guide is always available at my site: http://www.htc1guru.com/guides/return-stock-guide/

[EDIT]9-10-13 Post overhaul with how to combine Nandroid and RUU process to reset.
[EDIT]10-19-13 Post was changed to reflect new S-off, so changed the Tampered and Locking steps from revone
The Following 166 Users Say Thank You to crushalot For This Useful Post: [ Click to Expand ]
 
dsf767
Old
#2  
Senior Member
Thanks Meter 15
Posts: 391
Join Date: Oct 2007
Location: Marshfield, MA
Great guide, this should be a sticky!
Tablet:
Microsfot Surface

Phone:
Silver HTC One [AT&T]
The Following 2 Users Say Thank You to dsf767 For This Useful Post: [ Click to Expand ]
 
Rex2369
Old
(Last edited by Rex2369; 10th July 2013 at 09:08 PM.)
#3  
Rex2369's Avatar
Senior Member
Thanks Meter 67
Posts: 238
Join Date: Jun 2013
Kindly excuse me and no offense to the OP. But if you have S-OFF, all you have to do is change your CID back to your original and then run the RUU and you are nearly done Next thing is you have to lock the bootloader and have S-ON and that is it. You are now back to stock.
The Following User Says Thank You to Rex2369 For This Useful Post: [ Click to Expand ]
 
NxNW
Old
#4  
NxNW's Avatar
Senior Member
Thanks Meter 517
Posts: 1,427
Join Date: Apr 2011
Very helpful guide. But it can't be said enough times YOU WILL BRICK YOUR DEVICE going S-ON with a non-stock HBOOT

The guide does mention this in the relevant section, but it should probably be noted somewhere near the top of the OP. In big red letters.

Sent from my HTC One using xda app-developers app
The Following User Says Thank You to NxNW For This Useful Post: [ Click to Expand ]
 
Rex2369
Old
#5  
Rex2369's Avatar
Senior Member
Thanks Meter 67
Posts: 238
Join Date: Jun 2013
Quote:
Originally Posted by NxNW View Post
Very helpful guide. But it can't be said enough times YOU WILL BRICK YOUR DEVICE going S-ON with a non-stock HBOOT

The guide does mention this in the relevant section, but it should probably be noted somewhere near the top of the OP. In big red letters.

Sent from my HTC One using xda app-developers app
That's why I think it's safer to just run the RUU because that will flash the stock HBOOT and then you can have S-ON back without the worry of bricking the device.
 
iElvis
Old
(Last edited by iElvis; 10th July 2013 at 09:24 PM.)
#6  
iElvis's Avatar
Recognized Contributor
Thanks Meter 1,882
Posts: 3,753
Join Date: May 2012
Location: Modville
Nice work. But this block is incorrect and may lead to problems:

Quote:
Originally Posted by crushalot View Post
2. - You will need the stock splash screen so we need to do the same procedure as above with the stock splash screen. Download the stock splash screen here: http://d-h.st/F7H (From thread:http://forum.xda-developers.com/show....php?t=2324746)
Rename the file so it has no spaces like stock_splash.zip and put it in your ADB/fastboot folder.
Reboot into bootloader:
Code:
adb reboot bootloader
Now run this command:
Code:
fastboot oem rebootRUU
You should see the screen turn to a silver HTC logo. Now run this command:
Code:
fastboot flash zip stock_splash.zip
If you get an output in the console that says "(bootloader) ...... Successful" proceed to next step. If any errors use this thread for troubleshooting: http://forum.xda-developers.com/show....php?t=2324746
Those splashes in my thread are designed to be flashed in recovery. They will not work in RUU mode because the zip file is constructed incorrectly for it. Best approach would be to just flash the stock splash in recovery in step one.

Alternatively, keep the instructions as is and use the stock splash from this post: http://forum.xda-developers.com/show...27&postcount=1
________________
Current
HTC One/M7 (Android Revolution HD 81.0, ElementalX 17.2, 6.09.401.5 firmware, XSBM)
Nexus 7 (Dirty Unicorns v7.9/M-Kernel a69)
Dynavin D99+ (///M3Evolution)

Retired
HTC One XL
iPhone 4, 3G

Generic Noob Advice
The name of this site is xda-developers, not xda-overly-entitled-users. Ponder this well.
No Android mod is completely risk-free.
Formula for xda success: R > 10S > 100P, where R = posts read, S = searches, and P = post count.
Do you want to root your phone? Click here.
If someone helps you, click the "Thanks" button rather than posting "Thanks." This reduces thread clutter.

Custom HTC Bootsplashes and Animations
My designs + requests: Splashes | Animations

 
crushalot
Old
#7  
crushalot's Avatar
Recognized Contributor - OP
Thanks Meter 1,136
Posts: 977
Join Date: Jun 2011
Location: Raleigh

 
DONATE TO ME
Quote:
Originally Posted by iElvis View Post
Nice work. But this block is incorrect and may lead to problems:



Those splashes in my thread are designed to be flashed in recovery. They will not work in RUU mode because the zip file is constructed incorrectly for it. Best approach would be to just flash the stock splash in recovery in step one.

Alternatively, keep the instructions as is and use the stock splash from this post: http://forum.xda-developers.com/show...27&postcount=1
Yes, you are right sorry. So many threads I messed up the link. Kinda the reason I wanted to put all this in one place. I will update the OP and revise the first few steps to make it easier since the RUU should include the stock hboot and splash.

Thanks for all the feedback.
The Following 2 Users Say Thank You to crushalot For This Useful Post: [ Click to Expand ]
 
Dan37tz
Old
#8  
Dan37tz's Avatar
Senior Member
Thanks Meter 290
Posts: 303
Join Date: Apr 2011
I thought you needed SU permission to run revone? Am I mistaken?

Do you need root access to push revone to the /data/local/tmp directory?

After running the RUU.exe file, wouldn't you lose root?

I just want to double check.
 
crushalot
Old
(Last edited by crushalot; 11th July 2013 at 01:56 AM.)
#9  
crushalot's Avatar
Recognized Contributor - OP
Thanks Meter 1,136
Posts: 977
Join Date: Jun 2011
Location: Raleigh

 
DONATE TO ME
Quote:
Originally Posted by Dan37tz View Post
I thought you needed SU permission to run revone? Am I mistaken?

Do you need root access to push revone to the /data/local/tmp directory?

After running the RUU.exe file, wouldn't you lose root?

I just want to double check.
No you don't need root to use it as it has a root hack in the binary itself. That's why in ieftm's post on the usage of revone to S-off has optional wording on step 3
"3. (optional) If your device is unlocked and rooted please switch to root using su."
However I can confirm that it has worked better for me when I didn't run it as SU.

No you do not need root to push files using adb, well at least not to /data. You probably would to push to /system

Correct, after running the RUU you lose root. That is why I manually flashed the hboot and splash back myself while still on my rooted rom with utilities and most importantly a recovery in which I could use to get back running and try again if something failed.
The Following 2 Users Say Thank You to crushalot For This Useful Post: [ Click to Expand ]
 
crushalot
Old
#10  
crushalot's Avatar
Recognized Contributor - OP
Thanks Meter 1,136
Posts: 977
Join Date: Jun 2011
Location: Raleigh

 
DONATE TO ME
Quote:
Originally Posted by Rex2369 View Post
Kindly excuse me and no offense to the OP. But if you have S-OFF, all you have to do is change your CID back to your original and then run the RUU and you are nearly done Next thing is you have to lock the bootloader and have S-ON and that is it. You are now back to stock.
Thanks updated post to simplify.

Quote:
Originally Posted by NxNW View Post
Very helpful guide. But it can't be said enough times YOU WILL BRICK YOUR DEVICE going S-ON with a non-stock HBOOT

The guide does mention this in the relevant section, but it should probably be noted somewhere near the top of the OP. In big red letters.

Sent from my HTC One using xda app-developers app
Thanks but the updated post now avoids the possibility as we just let RUU flash all stock parts

Quote:
Originally Posted by Rex2369 View Post
That's why I think it's safer to just run the RUU because that will flash the stock HBOOT and then you can have S-ON back without the worry of bricking the device.
Thanks. Reflected in updated OP

The Following 6 Users Say Thank You to crushalot For This Useful Post: [ Click to Expand ]
Tags
reset, stock, unroot, warranty
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes