[GUIDE] How to Return to 100% Stock

Search This thread

borgqueenx

Senior Member
Jun 25, 2008
713
34
when booting up i dont see the red warning screen... i did saw it on my android revolution with custom kernel and advanced power menu version, but i flashed back stock rom and the red warning text is gone.
version does show 1.44.0000
 

crushalot

Senior Member
Jun 18, 2011
1,020
1,275
Raleigh
www.htc1guru.com
Can someone create a rom.zip for the asian wwe?
You will have to specify which RUU you want the zip from, as I see 2 different Asia WWE RUU's. Hopefully acquiredhate is still reading the thread and would be nice enough to do it for you. If he does it would be great if he could share how he pulled the zip for anyone else who may want to do so.
Thanks
 

natzakaria

Senior Member
Feb 3, 2004
353
41
You will have to specify which RUU you want the zip from, as I see 2 different Asia WWE RUU's. Hopefully acquiredhate is still reading the thread and would be nice enough to do it for you. If he does it would be great if he could share how he pulled the zip for anyone else who may want to do so.
Thanks

This one HTC One 2.24.401.1 (WWE UL GSM+LTE)
 

acquiredhate

Member
Apr 30, 2013
29
18
Thanks for uploading my friend. Just to be sure, you've used this to fastboot flash back to 100% stock? I know there's other steps involved because I'm s-off and all that, but just wanted to make sure. Thanks for your efforts acquiredhate!

Were you able to get it working? I believe the bootloader has to be relocked prior to flashing.
 

duraeas

Senior Member
Sep 11, 2010
79
13
I'm potentially looking to do this, but to be honest based on what I've done to the phone thus far, I'm not sure if my HBOOT is correct. Maybe I should start with...

Whether I should revert to stock: It took me a day to notice numerous instances of dust under the screen - at this point I was S-OFF with a newly released stock ROM. The phone is a replacement from Asurion for a broken device - I decided to initiate a replacement under the warranty. Warranties are a form of insurance contract, which my job leaves me very well versed in - the warranty very clearly excludes defects caused by changes to the firmware, but states absolutely nothing about it affecting any other defects. I can't think of a something more unequivocally unrelated to the operating system (a dead pixel would even be debatable) so I see no grounds upon which they could deny a claim.

Moreover, the phone would be sent back to HTC by Asurion rather than myself. The process of pursuing me through them should be more trouble than it's worth.

If I should: I achieved S-Off on my device to use the Developer Edition RUU. I then switched to custom recovery and loaded a stock ROM. Would my Hboot still be "stock" (ie: going S-On won't brick the phone) if it isn't necessarily the one that shipped on my phone? I do have a Nandroid backup of my original Telus state of affairs. Or is it fine by virtue of being from the developer RUU. Again, I don't know if it's even worth trying to revert back to stock.

Cheers
 

VacTacks11

Senior Member
May 8, 2012
111
20
I'm potentially looking to do this, but to be honest based on what I've done to the phone thus far, I'm not sure if my HBOOT is correct. Maybe I should start with...

Whether I should revert to stock: It took me a day to notice numerous instances of dust under the screen - at this point I was S-OFF with a newly released stock ROM. The phone is a replacement from Asurion for a broken device - I decided to initiate a replacement under the warranty. Warranties are a form of insurance contract, which my job leaves me very well versed in - the warranty very clearly excludes defects caused by changes to the firmware, but states absolutely nothing about it affecting any other defects. I can't think of a something more unequivocally unrelated to the operating system (a dead pixel would even be debatable) so I see no grounds upon which they could deny a claim.

Moreover, the phone would be sent back to HTC by Asurion rather than myself. The process of pursuing me through them should be more trouble than it's worth.

If I should: I achieved S-Off on my device to use the Developer Edition RUU. I then switched to custom recovery and loaded a stock ROM. Would my Hboot still be "stock" (ie: going S-On won't brick the phone) if it isn't necessarily the one that shipped on my phone? I do have a Nandroid backup of my original Telus state of affairs. Or is it fine by virtue of being from the developer RUU. Again, I don't know if it's even worth trying to revert back to stock.

Cheers

I'm with you on that one. I just flashed the Developer Edition RUU, which flashed everything back to stock, including hboot 1.44.0000. But the text on the op says that if I don't see the red text when I boot up the phone, to NOT go back to S-ON. I'm S-OFF and unlocked Bootlocker, and I don't see that text. Could be that it's the Developer Edition. I'm not sure. I want to go back to S-ON, but it's not seeing that red text that's causing me to pause, even with hboot 1.44.0000.

Any help there would be more than appreciated.
 

crushalot

Senior Member
Jun 18, 2011
1,020
1,275
Raleigh
www.htc1guru.com
I'm with you on that one. I just flashed the Developer Edition RUU, which flashed everything back to stock, including hboot 1.44.0000. But the text on the op says that if I don't see the red text when I boot up the phone, to NOT go back to S-ON. I'm S-OFF and unlocked Bootlocker, and I don't see that text. Could be that it's the Developer Edition. I'm not sure. I want to go back to S-ON, but it's not seeing that red text that's causing me to pause, even with hboot 1.44.0000.

Any help there would be more than appreciated.
Sorry for the confusion. I will try to clarify here and also edit the OP.
The red warning shows if you have a custom recovery. If you have the stock recovery (Flashed manually or through a RUU process) then I believe the red warning does not appear. I have not tinkered with the developers edition of the phone so I can't be certain about differences.

Basically if you see the red warning, it is a sign that something is modified or non-stock and therefore if you tried to s-on and lock with those modified parts it would brick the device.

Since the thread has expanded to cover different methods and users end up here just to finish the locking process, I wanted to give noobs a easy way to see if it was safe to s-on.

After running a RUU all parts should be back to stock and it should be ok to lock and s-on. I left that section because I saw a few reports of users running a RUU and it stated it was successful, however it didn't really flash the RUU, but that was related to not being s-off or locked bootloader, so no worries for those that follow my guide.

EDIT: Original Post has now been corrected. Thanks for the catch
 
Last edited:

VacTacks11

Senior Member
May 8, 2012
111
20
Sorry for the confusion. I will try to clarify here and also edit the OP.
The red warning shows if you have a custom recovery. If you have the stock recovery (Flashed manually or through a RUU process) then I believe the red warning does not appear. I have not tinkered with the developers edition of the phone so I can't be certain about differences.

Basically if you see the red warning, it is a sign that something is modified or non-stock and therefore if you tried to s-on and lock with those modified parts it would brick the device.

Since the thread has expanded to cover different methods and users end up here just to finish the locking process, I wanted to give noobs a easy way to see if it was safe to s-on.

After running a RUU all parts should be back to stock and it should be ok to lock and s-on. I left that section because I saw a few reports of users running a RUU and it stated it was successful, however it didn't really flash the RUU, but that was related to not being s-off or locked bootloader, so no worries for those that follow my guide.

EDIT: Original Post has now been corrected. Thanks for the catch

Thank you. I've done the ./revone -s 3 -l command, and it was successful. Now when I try to run the fastboot oem writesecureflag 3 command, the window tells me it's waiting for device.

Can I reboot into bootloader at this point and run that command there? Or does this HAVE to be done in Windows?
 

akashj17

Senior Member
Sep 21, 2011
324
63
hey will it also remove the red warning about it is for development purpose bla bla... in red color

i mean to say any clue will not be left that my phone was rooted when I've to return it
 

Fatelord

Senior Member
Jun 12, 2010
180
13
To make sure I can NOT go back to 100% stock if I was unlocked rooted S-On with the new Hboot ?

I hope I won't have to ..
 

gunnyman

Senior Member
Apr 12, 2010
7,998
2,668
Greenville SC
A snag I ran into with supercid and s-off on the 1.54 hboot, was until I flashed the 1.44 hboot ruu failed. This is using the at&t ruu.
 

RaptorMD

Senior Member
May 2, 2010
1,820
228
I wanted to say thank you for this thread. I for one have a DE H1 and have done everything I can to make it custom and my own. That said I also plan to as I always do sell it down the road and parlay that cash into a new phone. Depending on how the HTC One Max looks, and feels it likely WILL be my next phone because I am hooked on the BOOM sound and the phones design.

I knew I could reverse what I did but with everything there is always risk and hey why not take a little risk and live it up :)
 
  • Like
Reactions: crushalot

crushalot

Senior Member
Jun 18, 2011
1,020
1,275
Raleigh
www.htc1guru.com
Actually, I was able to get the RUU to run fine on phones with 1.54 hboot. They were s-off but you had to have the original CID for the RUU to work. Super CID didn't work. It was one reason why I have setting to the stock CID in step 1. :)
 

Top Liked Posts

  • There are no posts matching your filters.
  • 189
    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’t 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::
    –Easily 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://xdaforums.com/showthread.php?t=2242635

    –Easily get S-off by using revone (We will also use this tool reset Security back to S-On)
    http://xdaforums.com/showthread.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***

    –Easily get Super CID
    http://xdaforums.com/showthread.php?t=2317536

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

    *Flash custom splash screens:
    http://xdaforums.com/showthread.php?t=2324746
    *Flash new firmware:

    Concise and easy for noobs: http://xdaforums.com/showpost.php?p=43551752&postcount=5082
    Also http://xdaforums.com/showpost.php?p=43328416&postcount=33758
    Post #2 has the download for the custom firmware to flash without screwing anything else up:
    http://xdaforums.com/showthread.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’t 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’t check for root, doesn’t mean someone won’t 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://xdaforums.com/showthread.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’t 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’t be stock from your carrier if not the correct RUU. I like to set the stock CID back now so we don’t 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’s won’t 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://xdaforums.com/showthread.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.14.3250.13_10.33.1150.01_release_318450_signed_2.exe 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://xdaforums.com/showthread.php?t=2477792


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

    http://xdaforums.com/showthread.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://xdaforums.com/showthread.php?t=2314582and http://xdaforums.com/showthread.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’s 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
    6
    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.

    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

    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
    3
    @cdt82002 it's such a dead thread here. You must be 100% stock, bootloader locked and probably have a stock CID to get OTA updates again. Are you S-off?

    @Meatfish it is not so complicated. Yes, you need root and S-Off, but not custom recovery to reset tampered flag and bootloader to "locked". Make sure to have SuperSU as your root app. So, yes you need a custom recovery just to flash SuperSU. Then when you're S-off just flash stock recovery again, lock the bootloader, remove tampered flag, reset bootloader to locked, set to S-On and open SuperSU app and check the option that it should unroot/completely remove itself from the phone. Then you are 100% stock again.
    :D
    3
    Let me make something clear for everyone.

    FOR RECEIVING OTA AND FLASHING IT YOU DON'T NEED TO BE S-ON, LOCKED BOOTLOADER OR UNROOTED.
    ALL YOU NEED IS STOCK ROM WITH STOCK RECOVERY.
    2
    Great guide, this should be a sticky!