[ Guide ] Successful S-OFF for GB or ICS after Brick ( non proper Wrong S-ON , Security Warning ) using htc dev Unlock , Also for Downgrade latest GB OTA Firmware
My Other Posts Links
this Method
How htc dev unlock method Works
DISCLAIMER
Verify with HTC and your Carrier that you are legally Allowed to use any Method in this Post Before using it ,
and Don't use it if you are not legally allowed to
I am not responsible if following this Method results in bricking your phone
Whatever you do is at your Own Risk
Downgrade Firmware and Latest GB OTA updates ( Needed for first time S-OFF using Revolutionary , Proved working on GB )
Custom Rom Flash ( Gingerbread and ICS , Proved Working on hboot 1.18 )
[ Implementation ][/FONT] Successful S-OFF using the above method by member ( had done a Wrong S-on and Semi Brick Security Warning )
Install any ICS Custom Rom for ( S-ON Devices with hboot 1.27.0000 )
Revolutionary Method and Precautions ( Gingerbread )
Revolutionary Method ( ICS , General discussion )
Useful links ( Only use legally allowed content in those links )
Press the thanks Button for this Post
My Other Posts Links
this Method
- this method is to get S-off for bricked devices ( either on GB or ICS Firmware boot.img ) for members accidentally done wrong S-ON without following the proper procedure resulting in Brick S-ON with Security warning
- This method also Downgrades devices that came with new GB firmware ( or updated by GB OTA firmware ) to a lower Firmware version to allow Revolutionary to do first time S-off.
- This method also Downgrades ICS boot.img based on firmware 3.12 Android 4.0 ( the lastest firmware when writing this Guide is firmware 3.12 with hboot 1.23 ) , so firmware 3.32 with hboot 1.27 is not addressed in the following methods
- you have to verify with htc or your carrier if you are allowed to use this method
- This method is reported implemented successfully by more than a user ( who tried all other methods till writing this guide with no success, until they used this method )
- This method should work with gingerbread and gingerbread mixed with ICS boot.img ( i.e Android 4 with hboot 1.18 at least ) , I will not discuss any thing related to the Radio
- Summery of this method is :
- use htc dev unlock method to unlock bootloader or Super tool or Check this Post in XDA Portal ( if it is legal to use them )
- Install custom Rom ( old Stock Rooted Rom v2.3.x preferred 2.3.3 )
- Extract boot.img of the same Rom and Flash it via bootloader ( fastboot usb ) using fastboot in ADB tools . Also this downgrades ICS boot.img into Gingerbread boot.img
- Now you have a working Gingerbread Rom ready for use with revolutionary to get S-OFF
- In this post there is a Step by step Successful S-OFF implementation of this method for wrong S-ON by member ( please note that I don’t have a Sensation yet )
How htc dev unlock method Works
- first of all , i don't like this method ( htc dev unlock method ) because it is tricky
- this method unlocks some options for Bootloader ( Not All of them ) . htc dev site says unlocking your bootloader may or could void your warranty !!
- the Boot.img and Bootloader are still locked , and of course the Radio area is still locked ( it is not the radio we flash to improve signal )
- locked means those areas can not be over-written
- it allows you to install Custom Roms , But what htc maybe forgot to tell you is that the custom rom should be using their htc Boot,img ( i.e Stock kernel ) in order to work without errors !!!!!!! . ( Otherwise for Roms with custom kernels , you have to install the boot.img ( Custom Kernels ) in a certain Method to avoid errors like WiFi error or sometimes boot loop when you do wrong S-on !!!! )
- this certain Method is to flash locked items ( like Boot.img that includes custom Kernel ) through fastboot ( i.e bootloader )
- htc dev unlock method does not give S-off , it only unlocks some options for Bootloader . so , displaying ( Unlocked and S-on ) is normal for htc method
- Some mistakenly think that htc dev unlock method is the same as Revolutionary S-OFF , AND IT IS NOT
DISCLAIMER
Verify with HTC and your Carrier that you are legally Allowed to use any Method in this Post Before using it ,
and Don't use it if you are not legally allowed to
I am not responsible if following this Method results in bricking your phone
Whatever you do is at your Own Risk
Downgrade Firmware and Latest GB OTA updates ( Needed for first time S-OFF using Revolutionary , Proved working on GB )
- to know if your software need downgrade or not , if you software need downgrade Revolutionary will give you the following Error " Zerg ..... failed to S-OFF " , this indicates that your GB Software needs to be downgraded before using Revolutionary , for ICS software there is no downgrade method yet and you need to use other ways for achieving S-OFF
- you have to verify with htc or your carrier if you are allowed to use this method
- unlocked Bootloader using htc dev ( may or could void your warranty ) or Super tool or Check this Post in XDA Portal ( if it is legal to use them ) and ( use htc drivers v3.0.0.7 )
- You will need to Install custom recovery preferably CWM recovery as follows:
- go here for all methods How To Install Custom Recovery or use the following methods
- Method one : is install through bootloader , if needed rename recovery to PG58IMG.zip , Place PG58IMG.zip on the root of SD Card , then install it from bootloader as an update PG58IMG
- Method two : from your PC using ADB tools download for WINDOWS or download for LINUX and the device should be in fastboot usb . Extract recovery.img from zip file and put it inside ADB Folder , and start cmd as administrator and navigate to ADB folder which includes fastboot.exe and execute fastboot flash recovery recovery.img , then after installation is finished execute fastboot reboot-bootloader
- For 4EXT Go to 4EXT thread or Download the user-friendly 4EXT Recovery touch flashing tool and read the guide inside ( link by joaquinf ) .
- follow instructions mentioned in title "Custom Rom Flash " , and in title "[FONT="][ Implementation ][/FONT][FONT="]" [/FONT]in this Guide
- Your new Firmware and ICS Android v4 boot.img ( if ICS boot.img exists due to wrong S-ON ) is downgraded by installing the Old Rooted Stock Custom Rom ,you Must lock the bootloader for Revolutionary to work , then use Revolutionary to get S-OFF ( Proved Working )
Custom Rom Flash ( Gingerbread and ICS , Proved Working on hboot 1.18 )
- this method is used to solve :
- wrong S-ON on GB Bricked devices
- wrong S-ON on GB mixed with ICS v4 boot.img by downgrading both firmware and boot.img
- Downgrade GB Firmware ( and downgrade latest GB OTA ) for new S-on devices ,
- Allow revolutionary to do the S-OFF after downgrade
- this method is proved working on hboot 1.18
- Unlock bootloader using htc dev unlock method ( may or could void your warranty ) or Super tool or Check this Post in XDA Portal ( if it is legal to use them ) and ( use htc drivers v3.0.0.7 )
- Do a NAND backup for your rom , then do a full wipe or factory reset through recovery or bootloader , Don't use Super wipe
- Find a Custom rom ( an old Stock Rooted Rom Android 2.3.x “ better 2.3.3 , note that 2.3.5 will not work with revolutionary “ with unsecured Boot.img and this is mentioned in the rom features sometimes but not necessarily ) , and flash the rom from recovery (try this Rom used by member ) this 2.3.3 ROM ( Update Here is a mirror for the 2.3.3 rom: Dropbox )
- Update you can use any Stock Rooted Rom v2.3.3 or 2.3.4 in Xda Development section or look in list of HTC Sensation Android Roms , one member reported successful S-OFF using ARHD v3.x , if ARHD v3.x Rom don't include boot.img then just skip flashing Boot.img or use Alternative Method to Flash Boot.img for Custom Roms )
- Reboot into bootloader , ( for some roms , if you let the rom boots maybe it will be stuck on htc splash screen or getting boot loops because it needs its boot.img )
- Update there is now a new version of 4EXT recovery for S-ON devices v 1.0.0.5 , enable smart flashing in recovery \ tools and it will flash the boot.img by itself " read the restrictions for that method in 4EXT recovery thread " . Also 4EXT recovery Control has an option to flash boot.img from home screen
- extract Boot.img from the same rom zip you flashed , ( in Multi device Roms , extraxt the boot.img for your exact device ) , then Flash it as follows :
- Bootloader should be unlocked
- the phone should be in bootloader ( fastboot usb )
- Put boot.img inside adb folder in same place your fastboot.exe , ADB tools download for WINDOWS
- Start cmd as administrator and navigate to ADB folder which includes fastboot.exe and type fastboot flash boot boot.img and press enter
- after finish , type fastboot reboot-bootloader and press enter
- Reboot , the device may reboot several times before reaching the home screen
[ Update ] Alternative Method to Flash Boot.img for Custom Roms
[FONT="] - Update there is now a new version of 4EXT recovery for S-ON devices v 1.0.0.5 , enable smart flashing in recovery \ tools and it will flash the boot.img by itself " read the restrictions for that method in 4EXT recovery thread " . . Also 4EXT recovery Control has an option to flash boot.img from home screen
- follow the above steps , except instead of extracting Boot.img and flashing it through fastboot , do the following :
- Download recovery img for either CWM or 4EXT
- Put recovery img ( recovery name.img ) inside ADB folder in same place your fastboot.exe ,
- recovery name.img is the exact name for the downloaded recovery img that you put inside the ADB Folder
- it is NOT PG58IMG.zip recovery
- Start cmd as administrator and navigate to ADB Folder which includes fastboot.exe and type the command fastboot boot recovery name.img and press enter
- your phone should now go to recovery screen ( loaded through fastboot )
- install your custom rom as normal and reboot your phone , ( this will install the custom Rom and the Boot.img of the same Custom Rom in the same time )
- Reboot , the device may reboot several times before reaching the home screen
- if this method doesn't work , then go back to the original Method
[ Implementation ][/FONT] Successful S-OFF using the above method by member ( had done a Wrong S-on and Semi Brick Security Warning )
- a step by step procedure , the following is what member practically did to implement this method , i added some to his words to make every thing organized and clear ( please note that I don’t have a Sensation yet )
- member problem was he installed Custom ICS Rom and then installed RUU_Pyramid_Orange_PL and did a wrong S-ON ( so he is on ICS boot.img and a GB RUU with a wrong S_ON ) , his Hboot is 1.18
- “ I unlocked device via htc and did factory reset from bootloader. This way I gained access to my 4ext recovery which was not erased during RUU process.
- First, I extracted boot.img from custom ROM zip in my PC and put it to the same folder when my fastboot.exe is . Device was in Fastboot USB mode
- Next, I put custom gingerbread ROM this 2.3.3 ROM ( Update Here is a mirror for the 2.3.3 rom: Dropbox )into sd card and flashed it from recovery, then immediately, from recovery, rebooted into fastboot and flashed boot.img from my PC:
fastboot flash boot boot.img - ( Update you can use any Stock Rooted Rom v2.3.3 or 2.3.4 in Xda Development section or look in list of HTC Sensation Android Roms , one member reported successful S-OFF using ARHD v3.x , if ARHD v3.x Rom don't include boot.img then just skip flashing Boot.img or use Alternative Method to Flash Boot.img for Custom Roms )
- I did it twice, with additional full wipe from recvovery, first with RCMix 3.5 which didn't work with revolutionary, and the second with this 2.3.3 ROM ( Here is a mirror for the 2.3.3 rom: Dropbox ) that finally worked and gave me S-Off . Currently I'm on stock, branded Orange PL ROM, relocked, S-on and ready to be sent for repair.”
Install any ICS Custom Rom for ( S-ON Devices with hboot 1.27.0000 )
- See post # 2 below for how to install any Custom Rom on S-ON Devices with hboot 1.27.0000
Revolutionary Method and Precautions ( Gingerbread )
- Video link for very detailed instructions ( for htc Incredible 2 phone ,it is for gingerbread also ) , Procedure is the same , Only difference is you have to replace any required information " name and bootloader " and downloads " recovery " to fit sensation , Link is here
- It Should be used after doing one of these 3 methods ( i.e a device with GB Rom - New S-ON devices that has acceptable software version for Revolutionary can skip this step ) mentioned above in this post ( [FONT="]Custom Rom Flash [/FONT]or Downgrade Firmware and Latest OTA or [FONT="]RUU flash ) [/FONT][FONT="]using Android 2.3.x Rom ( 2.3.3 preferred )[/FONT]
- uninstall htc new drivers and htc Sync , and use the old htc drivers (v 3.0.0.007) mentioned in revolutionary page ( for windows users ) ,New htc drivers prevent Revolutionary from doing its job ( Proved ).
- revolutionary page is here
- Old htc driver download link for HTCDriver3.0.0.007.exe
- if you are using htc dev unlock method , you have to re-lock your bootloader before using revolutionary
- run Revolutionary as administrator
- usb debugging must be enabled in setting \ application \ development
- untick fast boot box in setting \ power
- remove any conflicting software ( like Doubletwist ,Verizon vcast ) , remove any conflicting APK from your device that may connect to the phone over USB and automatically sync
- Disable any firewall or antivirus , use a different clean browser without the add-on extensions , clean browser cache
Copy and Paste in cmd
RUU flash ( Gingerbread and ICS ) ( not proved )- Better to avoid typing , use copy and Paste
- Right click top toolbar of cmd window and select edit then paste or copy
- Error " Waiting for device .... " , this is caused by new htc Drivers and htc sync , remove both and install old htc driver
- Error " Zerg ..... failed to S-OFF " , this indicates that your GB Software needs to be downgraded before using Revolutionary , for ICS software there is no downgrade method yet and you need to use other ways for achieving S-OFF
- Error regarding the SN and beta key , to solve that use copy and Paste in cmd window instead of typing
- Error " revolutionary Runs and finishes and don't give error and also don't do S-OFF " , to solve that Run Revolutionary as administrator
- You can try this method , and see if works with you instead of the above ( no feed back about it yet )
- Normally you should Lock bootloader in order to Flash RUU ( But since there is a wrong S-ON , then try also to Unlock if it didn’t work ) using htc dev unlock ( may or could void your warranty )
- Do a NAND backup for your rom , then do a full wipe or factory reset through recovery or bootloader , Don't use Super wipe
- note that flashing RUU.exe requires htc sync to be installed and the device is connected in sync mode , and that usb debugging is enabled , and fast boot box is unchecked " in Setting \ power "
- if you have problems when you flash a ruu , try the following :
fastboot erase cache
fastboot oem rebootRUU
And then flash the ruu by executing the RUU.exe - from your PC , Flash RUU.exe ( similar to your original RUU , or should be old Gingerbread RUU ) in Fastboot ( not Hboot ) , if not working , then remove Battery and put it back and press volume down and power to go to bootloader , and repeat the RUU.exe flash
- after flashing the RUU , if it didn’t boots and stuck on the splash , then try Unlock bootloader and extract the Boot.img that came with the same RUU zip file , and flash it as follows ( it is only a trial , not sure it would work ) :
- Bootloader should be unlocked
- the phone should be in bootloader ( fastboot usb )
- Put boot.img inside adb folder in same place your fastboot.exe
- Start cmd as administrator and navigate to ADB folder which includes fastboot.exe as and type fastboot flash boot boot.img and press enter
- type fastboot reboot-bootloader and press enter
- Reboot , the device may reboot several times before reaching the home screen
Revolutionary Method ( ICS , General discussion )
- [FONT="][ Update 1 ] [/FONT]there is now a new modified Firmware 3.24 Unlocked for ICS 4.0.3 that has the Unlocked bootloader hboot 1.27 (posted by Mike1986) , that could lead to other ways and solutions
- [FONT="][ Update 2 ] :[/FONT]
- there is this beta method for S-OFF here http://unlimited.io/ , Sensation/XE/4G Super Utility (all in one) by kgs1992 , [GUIDE] Juopunutbear S-OFF NO VOIDING WARRANTY (1.2x HBOOTS)--NEW: ONE CLICK ROOT ,
- Check the following Posts Post in XDA Portal
- there is this beta method for S-OFF here http://unlimited.io/ , Sensation/XE/4G Super Utility (all in one) by kgs1992 , [GUIDE] Juopunutbear S-OFF NO VOIDING WARRANTY (1.2x HBOOTS)--NEW: ONE CLICK ROOT ,
- ICS firmware , more information is at Mike link here and this guide here
- ICS problem solution ( Firmware 3.12 Only mixed with hboot 1.18 ) is to downgrade the software and ICS boot.img to gingerbread as above method [FONT="]"[/FONT]Custom Rom Flash ( Gingerbread and ICS )"
- ICS firmware disables fastboot commands ( no write ) on 1.23.xxxx-1.20.xxxx and i think also 1.18.xxxx
- So , for those who did wrong S-ON on devices having hboot 1.18 mixed with ICS Boot.img ( firmware 3.12 Android 4 Only ) , Revolutionary will not be able to write S-off because Android 4 software boot.img is too new for Revolutionary, Also Revolutionary doesn’t support hboot 1.23
- there is an Hboot 1.17 ( which I think is Eng Hboot similar or same as 1.17.0008 ) which allows fastboot commands , use Firmware v3.12 ( for sense 3.5 based GB ROM only ) or v1.17 for older GB ROM
- you can't downgrade the firmware if the devvice is S-ON , or when the bootloader is unlocked on S-ON devices
- ICS Roms 3.12.401.102 will only boot on certain Hboot versions ( not all of them ) , Hboot 1.17 will not boot ICS Roms 3.12.401.102
Useful links ( Only use legally allowed content in those links )
Press the thanks Button for this Post
Last edited: