[International] [how to]return to 100% stock from revone or moonshine s off

Last Updated:

  1. scotty85

    scotty85 Guides Guide

    DO NOT turn your secureflag on unless on a stock,signed hboot.

    s-on with an eng signed or patched hboot will hard brick your device immediately.
    (read: permanently bricked,unrecoverable)

    in other words,ONLY use the writesecureflag 3 command AFTER running an RUU. never before.

    im sure were mostly to excited to want to go back to s on just yet,since we just got s-off :eek: but its a matter of time before this comes up,so here ya go:

    -that you know your stock CID and build number(x.xx.xxx.x for example, xxx=531= tmobile, xxx=401= htc europe)

    if you have a relocked bootloader,and want to reset the lock status to read locked,reference this thread: http://androidforums.com/internatio...t/732395-how-reset-your-lock-status-flag.html

    if needed,flash "lock_bootloader.zip" in clockwork recovery,then procede to the following steps.

    1)restore your mid,if you changed that.
    2)donwload and run an RUU for your most current STOCK carrier/reigonal build
    3)open a cmd window. plug in phone,charge only mode,usb debugging on.
    4)run the following:

    adb devices

    adb reboot bootloader

    fastboot devices

    fastboot oem writecid xxxxxxxx (where xxxxxxxx is your stock CID. example: HTC__001 or T-MOB010)

    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

    Code (Text):
    1. Microsoft Windows [Version 6.1.7601]
    2. Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
    4. C:\Users\Scott>[COLOR="Red"]cd c:\mini-adb_vigor[/COLOR]
    6. c:\mini-adb_vigor>[COLOR="red"]adb devices[/COLOR]
    7. List of devices attached
    8. HTxxxxxxxxxx    device
    11. c:\mini-adb_vigor>[COLOR="Red"]adb reboot bootloader[/COLOR]
    13. c:\mini-adb_vigor>[COLOR="red"]fastboot devices[/COLOR]
    14. HTxxxxxxxxxx    fastboot
    16. c:\miniadb_ville>[COLOR="Red"]fastboot oem writecid HTC__001[/COLOR]
    17. ...
    18. (bootloader) Start Verify: 0
    19. OKAY [  0.014s]
    20. finished. total time: 0.016s
    22. c:\miniadb_ville>[COLOR="red"]fastboot reboot-bootloader[/COLOR]
    23. rebooting into bootloader...
    24. OKAY [  0.066s]
    25. finished. total time: 0.068s
    27. c:\miniadb_ville>[COLOR="red"]fastboot getvar cid[/COLOR]
    28. cid: HTC__001
    29. finished. total time: 0.004s
    31. c:\mini-adb_vigor>[COLOR="red"]fastboot oem writesecureflag 3[/COLOR]
    32.                               ... OKAY [  0.051s]
    33. finished. total time: 0.051s
    35. c:\mini-adb_vigor>[COLOR="red"]fastboot reboot-bootloader[/COLOR]
    36.      rebooting into bootloader... OKAY [  0.177s]
    37. finished. total time: 0.177s
    39. c:\mini-adb_vigor>[COLOR="red"]fastboot reboot[/COLOR]
    40.                      rebooting...
    41. finished. total time: 0.168s
    43. c:\mini-adb_vigor>
    *verified working if you need it for warranty. :)

    *current RUUs can be found here:
    AndroidFiles RUU
    or here:
    Shipped ROMs

    *if you need adb/fastboot you can use this:
    (extract,move to root of c,change to that directory with cd c:\mini-adb )

  2. jasperwill

    jasperwill Well-Known Member

    those letters should be all caps.
  3. scotty85

    scotty85 Guides Guide



    think twice about attempting to turn s on on a vzw device whose bootloader is nto officially unlockable. you may end up locked into bootloader with security warning that you cannot recovery from without an official signed ruu.

    for reference:
    why you should NOT turn s-on! - xda-developers
    jasperwill likes this.

Share This Page