[How-To] From S-OFF to 100% Stock S-ON [Facepalm/JTAG/RevOne/Moonshine/Rumrunner]

Search This thread

chayos00

Senior Member
Feb 19, 2012
81
6
Do you still have a custom recovery?

Yes, I have CWM loaded still. I don't remember seeing to remove it so I didn't even think about restoring the factory recovery. I will do that and give it a shot. Thanks Phaded!

********Edit*********
After a bit of looking, I'm not seeing the factory recovery anywhere. I thought it would be in the DNA toolbox, but that is just CWM or TWRP. Do you have any idea where it is? I'm going to still look for it, but as it's early morning, I need to get ready for work.
 
Last edited:

Phaded

Senior Member
Apr 6, 2010
1,127
371
216
Yes, I have CWM loaded still. I don't remember seeing to remove it so I didn't even think about restoring the factory recovery. I will do that and give it a shot. Thanks Phaded!

********Edit*********
After a bit of looking, I'm not seeing the factory recovery anywhere. I thought it would be in the DNA toolbox, but that is just CWM or TWRP. Do you have any idea where it is? I'm going to still look for it, but as it's early morning, I need to get ready for work.

I was asking for a different reason...

If you still have CWM loaded, download the lock bootloader zip in the post of one of the other methods. Flash it in recovery, boot into bootloader. Verify that it says locked...

If not let me know.
 

chayos00

Senior Member
Feb 19, 2012
81
6
I was asking for a different reason...

If you still have CWM loaded, download the lock bootloader zip in the post of one of the other methods. Flash it in recovery, boot into bootloader. Verify that it says locked...

If not let me know.

That did not work, I just tried it twice.
 

Phaded

Senior Member
Apr 6, 2010
1,127
371
216
Correct, the fastboot window still shows S-OFF and says nothing about locked or unlocked.

Hmm... it should say that... it's possible Moonshine removes that flag... I didn't use Moonshine so I don't know. You could try the moonshine irc channel and talk to beaups.

If not...

Try the RUU. Let me know after doing that what it says if anything.
 

chayos00

Senior Member
Feb 19, 2012
81
6
Hmm... it should say that... it's possible Moonshine removes that flag... I didn't use Moonshine so I don't know. You could try the moonshine irc channel and talk to beaups.

If not...

Try the RUU. Let me know after doing that what it says if anything.

I just came across this thread Stock Recovery? and will try flashing this recovery to see if it works for me.

*******EDIT********
That recovery worked and I am now without CWM. As I get time at work, I'll try to run the relock and then RUU.
 
Last edited:

Phaded

Senior Member
Apr 6, 2010
1,127
371
216
I just came across this thread Stock Recovery? and will try flashing this recovery to see if it works for me.

Stock recovery has nothing to do with it. You should be able to set the lock flag with custom recovery or stock.

It looks like moonshine removes the area where the locked/unlocked status should be.

If you ran the adb command from the OP, just run the RUU. After that, go into bootloader and tell me what you see.
 

chayos00

Senior Member
Feb 19, 2012
81
6
Stock recovery has nothing to do with it. You should be able to set the lock flag with custom recovery or stock.

It looks like moonshine removes the area where the locked/unlocked status should be.

If you ran the adb command from the OP, just run the RUU. After that, go into bootloader and tell me what you see.

I ran the RUU and then got the 158 error then had to flash the HBOOT. After that flash the phone showed "***Tampered*** & ***LOCKED***". I then proceeded to run the RUU and it completed at that point with no issues. Then the last few DOS commands for fastboot and back to Locked and S-On. I updated back from 1.15 up through 2.06. Also doing so that made me realize you have to step from 1.15 to 2.04 and finally 2.06. So far the 4G is still working. I will keep it stock for a few days to ensure no further 4G issues then I will be moonshining again!!

So I'm gonna say that you might want to mention doing the locked unlocked may not show and just to continue doing the RUU after the first step that should lock the phone.
 
  • Like
Reactions: Phaded

Phaded

Senior Member
Apr 6, 2010
1,127
371
216
I ran the RUU and then got the 158 error then had to flash the HBOOT. After that flash the phone showed "***Tampered*** & ***LOCKED***". I then proceeded to run the RUU and it completed at that point with no issues. Then the last few DOS commands for fastboot and back to Locked and S-On. I updated back from 1.15 up through 2.06. Also doing so that made me realize you have to step from 1.15 to 2.04 and finally 2.06. So far the 4G is still working. I will keep it stock for a few days to ensure no further 4G issues then I will be moonshining again!!

So I'm gonna say that you might want to mention doing the locked unlocked may not show and just to continue doing the RUU after the first step that should lock the phone.

I'll add it tomorrow, thanks
 

pgag

Senior Member
Jun 7, 2013
56
1
tinley park
I'll add it tomorrow, thanks

I used hasson2000 all in one to flash the ruu last week, I did something wrong when flashing a new Rom totally bricked my DNA so I was thinking I know the all in one don't work anymore for soff but I remember it had other options on it. Pretty much it was totally bricked had to hold down power button so pc could pick up device , once it did connect click on install stock ruu took a few seconds and was back to normal! Hope this helps! :)

sent from unlocked,rooted,s_off DNA
 

Jon8RFC

Senior Member
Apr 3, 2010
165
94
TX
This was excellent and quick! I was:
*TAMPERED*
*UNLOCKED*
S-OFF

Now, I'm:
*LOCKED*
S-ON


I can finally get rid of my DNA with confidence. Thank you to everyone who played a role in DNA restoration =)
 

chayos00

Senior Member
Feb 19, 2012
81
6
I used hasson2000 all in one to flash the ruu last week, I did something wrong when flashing a new Rom totally bricked my DNA so I was thinking I know the all in one don't work anymore for soff but I remember it had other options on it. Pretty much it was totally bricked had to hold down power button so pc could pick up device , once it did connect click on install stock ruu took a few seconds and was back to normal! Hope this helps! :)

sent from unlocked,rooted,s_off DNA

Not sure if you know but a "bricked" phone is a device that got corrupted to the point where you could not recover from the issue. A phone that just had to be hard restarted would be more of, it froze and had to be rebooted. Kind of like a PC that gave a BSOD and when rebooted had a corrupt OS that won't boot back into windows.
 

Prodiigy

Member
Jun 9, 2013
22
0
When I go to flash the stock hboot i get this error:

C:\Users\Home\Desktop\DNA\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-
x86_64-20130522\sdk\platform-tools>fastboot flash zip PL83IMG.zip
error: cannot load 'PL83IMG.zip': Unknown error

when i download the stock hboot it shows up as a disc image file as the file type. I am using 64 bit windows 7. do i need to change the file type or change any other settings on my computer?
 

chayos00

Senior Member
Feb 19, 2012
81
6
When I go to flash the stock hboot i get this error:

C:\Users\Home\Desktop\DNA\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-
x86_64-20130522\sdk\platform-tools>fastboot flash zip PL83IMG.zip
error: cannot load 'PL83IMG.zip': Unknown error

when i download the stock hboot it shows up as a disc image file as the file type. I am using 64 bit windows 7. do i need to change the file type or change any other settings on my computer?


Yes rename the file. Nothing else should need to change.
 

Prodiigy

Member
Jun 9, 2013
22
0
I renamed it to PL93IMG.zip and I'm getting the unknown error. I'll try re-downloading it again. Since I ran the step on locking the bootloader (even though it doesn't say locked) don't I need to do that step again before flashing the hboot and RUU?

Sent from my HTC6435LVW using xda premium
 

Phaded

Senior Member
Apr 6, 2010
1,127
371
216
I renamed it to PL93IMG.zip and I'm getting the unknown error. I'll try re-downloading it again. Since I ran the step on locking the bootloader (even though it doesn't say locked) don't I need to do that step again before flashing the hboot and RUU?

Sent from my HTC6435LVW using xda premium

Which method did you use?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 37
    ONLY FOLLOW THIS GUIDE FOR WARRANTY REPLACEMENTS OR IF YOU NEED TO BE STOCK FOR A SALE. THERE IS NO OTHER REASON TO FOLLOW THIS GUIDE.

    ALSO MAKE SURE YOU FOLLOW THE GUIDE PROPERLY. FAR TOO MANY ERRORS ARE BEING MADE BY NOT READING OR FOLLOWING STEPS IN ORDER.



    This guide will help you get your phone back to stock after using any of the 5 S-Off methods that either have been or are currently available to us.

    Credit to Scotty1223. I edited his One S guide for the DNA.

    First post is for Facepalm and JTAG S-off only. RevOne instructions are in the second post. Moonshine and Rumrunner is in post 3.


    ***IF YOU HAVE A CUSTOM SPLASH SCREEN INSTALLED, THE STOCK SPLASH SCREEN MUST BE FLASHED BEFORE DOING ANYTHING! SEE FOURTH POST FOR LINKS AND INSTRUCTIONS FOR FLASHING THE STOCK SPLASH SCREEN***

    ***DO NOT ISSUE ANY OF THE WRITESECUREFLAG COMMANDS ON AN ENG HBOOT AS IT WILL BRICK THE DEVICE. JUST FOLLOW THE GUIDE.***



    For those who want to return to stock and have used the JTAG method for achieving S-Off, this guide will also work for you. It all depends on what you did AFTER you got your JTAG phone back. If you wrote a new CID using fastboot and HTCDev unlocked, follow the guide as it is written out.

    If you didn't write a new CID and use HTCDev unlock and just merely flashed a modified/ENG HBOOT, then the process would be: Fastboot flash stock hboot, RUU to stock, fastboot oem writesecureflag 3, then allow phone to update using the OTA process. You can find the commands/files/steps for these 3 simple steps below as well.


    Files needed:

    Lock bootloader zip: lock bootloader MD5: f335f78f9f46469c823da0c671026de5
    3.06 RUU: 3.06 RUU


    Steps:
    1.Copy the "lock bootloader zip" onto root of internal storage and flash in recovery of your choice. Once it is flashed Reboot your phone.
    2.Reboot into bootloader either using 4 in 1 power menu (if your ROM supports it). Or plug your phone into a USB port, turn on USB debugging and open a command prompt and type:
    Code:
    adb devices (Your device ID should be listed)
    adb reboot bootloader
    Verify you are **LOCKED** If not, re-flash the zip. If still not locked, try downloading the file again and re-flashing.

    IF YOU ARE RUNNING ANY HBOOT THAT IS NOT THE 3.06 HBOOT (1.54 in bootloader), YOU MUST FLASH 3.06 HBOOT BEFORE CONTINUING - SEE POST 4

    3. run the RUU as admin (right click, run as administrator)
    4. After RUU completes and phone reboots, make sure usb debugging is on and in charge only mode and open cmd prompt
    5. Run the following:
    Code:
    adb devices (your device should be listed)
    
    adb reboot bootloader
    
    fastboot devices (your device should be listed)
    
    fastboot oem writecid VZW__001 (2 underscores)
    
    fastboot reboot-bootloader
    
    fastboot getvar cid (verify your stock CID)
    
    fastboot oem writesecureflag 3
    
    fastboot reboot-bootloader
    
    *verify you are locked s-on
    
    fastboot reboot


    Should now be 100% stock, S-ON, with CID 100% stock as well.
    29
    Return to stock on Moonshine, Rumrunner and Firewater S-Off

    Files needed:

    Lock bootloader zip: lock bootloader MD5: f335f78f9f46469c823da0c671026de5
    3.06 RUU: 3.06 RUU


    Steps:
    1.Copy the "lock bootloader zip" onto root of internal storage and flash in recovery of your choice. Once it is flashed Reboot your phone.
    2.Reboot into bootloader either using 4 in 1 power menu (if your ROM supports it). Or plug your phone into a USB port, turn on USB debugging and open a command prompt and type:
    Code:
    adb devices (Your device ID should be listed)
    adb reboot bootloader

    You are locked. The s-off process removes the flag from displaying, but it is now locked.

    IF YOU ARE RUNNING ANY HBOOT THAT IS NOT THE 3.06 HBOOT (1.54 in bootloader), YOU MUST FLASH 3.06 HBOOT BEFORE CONTINUING - SEE POST 4

    3. run the RUU as admin (right click, run as administrator)
    4. After RUU completes and phone reboots, make sure usb debugging is on and in charge only mode and open cmd prompt
    5. Run the following:
    Code:
    adb devices (your device should be listed)
    
    adb reboot bootloader
    
    fastboot devices (your device should be listed)
    
    fastboot oem writesecureflag 3
    
    fastboot reboot-bootloader
    
    *verify you are locked s-on
    
    fastboot reboot

    You are now out of box stock.
    14
    FLASHING THE STOCK HBOOT:
    *Credit to .torrented*


    1. download 3.06 HBOOT: 3.06 HBOOT
    2. Rename stock hboot file to : PL83IMG.zip and place in the folder that contains your fastboot.exe file (On your computer)
    3. Flash hboot
    Code:
    Step 1) adb reboot bootloader
    
    Step 2) fastboot oem rebootRUU
    
    Step 3) CD to directory containing hboot zip (i.e. cd C:\sdk\)
    
    Step 4) fastboot flash zip PL83IMG.zip
    
    *** When it says it is done in the terminal/cmdprompt execute the following *** 
    [The green bar only fills up about 75% of the way]
    
    Step 5) fastboot reboot-bootloader




    Flashing the Stock Splash Image

    *All credit goes to E.T.Heil

    1. Download the stock splash image here.
    2. Rename file to splash1.img
    3. Place the file in the same folder you have adb.exe and fastboot.exe located.
    4. Plug in your phone to a USB port, turn on USB debugging and open a command prompt. cd to the directory your adb/fastboot is located
    5. Run the following:
    Code:
    adb devices (your device ID should be displayed)
    adb reboot bootloader
    Once in the bootloader, run:
    Code:
    fastboot flash splash1 splash1.img
    Once complete, reboot the phone using the menu or
    Code:
    fastboot reboot
    12
    Returning to stock from RevOne

    It is pretty much the same process, but with a slight deviation.

    AGAIN, IF YOU HAVE A MODIFIED/ENG HBOOT, DO NOT ISSUE ANY WRITESECURE FLAG COMMANDS. JUST FOLLOW THE GUIDE.

    First, download these two files:

    Files needed:

    Lock bootloader zip: lock bootloader MD5: f335f78f9f46469c823da0c671026de5
    3.06 RUU: 3.06 RUU


    Steps:
    1.Copy the "lock bootloader zip" onto root of internal storage and flash in recovery of your choice. Once it is flashed Reboot your phone.
    2.Reboot into bootloader either using 4 in 1 power menu (if your ROM supports it). Or plug your phone into a USB port, turn on USB debugging and open a command prompt and type:
    Code:
    adb devices (Your device ID should be listed)
    adb reboot bootloader
    Verify you are **LOCKED** If not, re-flash the zip. If still not locked, try downloading the file again and re-flashing.

    IF YOU ARE RUNNING ANY HBOOT THAT IS NOT THE 3.06 HBOOT (1.54 in bootloader), YOU MUST FLASH 3.06 HBOOT BEFORE CONTINUING - SEE POST 4

    3. run the RUU as admin (right click, run as administrator)
    4. After RUU completes and phone reboots, make sure usb debugging is on and in charge only mode and open cmd prompt
    5. Run the following:
    Code:
    adb devices (your device should be listed)
    
    adb reboot bootloader
    
    fastboot devices (your device should be listed)
    
    fastboot oem writesecureflag 3
    
    fastboot reboot-bootloader
    
    *verify you are locked s-on
    
    fastboot reboot

    You are now out of box stock.
    3
    updated with RevOne and Moonshine...

    If anyone sees anything I missed let me know. Otherwise guide is complete.