[guide] back to stock from facepalm s-off - HTC One S

WARNING!!!
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 but its a matter of time before this comes up,so here ya go:
prerequisites:
-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://forum.xda-developers.com/showthread.php?t=2155955
flash "lock_bootloader.zip" in your recovery of choice,then procede to the following steps.
1)donwload and run an RUU for your most current STOCK carrier/reigonal build
2)open a cmd window. plug in phone,charge only mode,usb debugging on.
3)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:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>[COLOR="Red"]cd c:\mini-adb_vigor[/COLOR]
c:\mini-adb_vigor>[COLOR="red"]adb devices[/COLOR]
List of devices attached
HTxxxxxxxxxx device
c:\mini-adb_vigor>[COLOR="Red"]adb reboot bootloader[/COLOR]
c:\mini-adb_vigor>[COLOR="red"]fastboot devices[/COLOR]
HTxxxxxxxxxx fastboot
c:\miniadb_ville>[COLOR="Red"]fastboot oem writecid HTC__001[/COLOR]
...
(bootloader) Start Verify: 0
OKAY [ 0.014s]
finished. total time: 0.016s
c:\miniadb_ville>[COLOR="red"]fastboot reboot-bootloader[/COLOR]
rebooting into bootloader...
OKAY [ 0.066s]
finished. total time: 0.068s
c:\miniadb_ville>[COLOR="red"]fastboot getvar cid[/COLOR]
cid: HTC__001
finished. total time: 0.004s
c:\mini-adb_vigor>[COLOR="red"]fastboot oem writesecureflag 3[/COLOR]
... OKAY [ 0.051s]
finished. total time: 0.051s
c:\mini-adb_vigor>[COLOR="red"]fastboot reboot-bootloader[/COLOR]
rebooting into bootloader... OKAY [ 0.177s]
finished. total time: 0.177s
c:\mini-adb_vigor>[COLOR="red"]fastboot reboot[/COLOR]
rebooting...
finished. total time: 0.168s
c:\mini-adb_vigor>
*verified working if you need it for warranty.
*current RUUs can be found here:
http://androidfiles.org/ruu/?dir=Ville
or here:
http://shipped-roms.com/index.php?category=android&model=Ville
*if you need adb/fastboot you can use this:
http://www.mediafire.com/?hzf1u4bowjewhdq
(extract,move to root of c,change to that directory with cd c:\mini-adb )

mine

Thank you! This will come in handy for many.
Sent from my HTC One S using xda premium

AW: [guide] back to stock from facepalm s-off
My stock cid is O2___102 but i changed it to HTC__102 can i use the HTC cid for S-ON?
Gesendet von meinem HTC One S mit Tapatalk 2

Why did you change your CID?Because your phone is branded to O2 and you want to flash different RUU??
If you want to S-ON it again make sure that your CID is for your region and you will flash the correct RUU for it.
After you flashed....and everything looks good you can use "fastboot oem writesecureflag 3" for S-ON.

hi,
i'm currently on an s-off with supercid and twrp recovery with cyanogen image.
I need to revert back to stock firmware, stock recovery, stock cid, s-on, * LOCKED * bootloader.....
anyone can just highlight correct steps sequence to follow to get that?
Thanks in advance

It's all in the first post.

El_Svanto said:
It's all in the first post.
Click to expand...
Click to collapse
I don't see anything about putting back stock recovery...
Also what about changing cid after installing ruu...I read somewhere else it doesn't work...is it true?

The ruu installs stock recovery as a part of the firmware. If you are s-off you can still change cid after ruu. Use command "fastboot oem writecid HTC__001". Use your cid instead of HTC__001.

Related

[Q] problem when unlocking my boatloader

Hi All
i am trying to unlock my boat loader (S-off) through official HTCDEV.com and i am stucked at step 8 when i give the command (fastboot oem get_identifier_token) the next message appear to me!?
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.008s]
finished. total time: 0.009s
my Hboot ver:1.04.0000
MicroP: 0557
Radio: 7.47..35.17
S-on RL
so any one can help me about this error!?
they dont have unlock for chacha.. check the list

[Q] A little help required on unrooting

Hi everyone
i am trying to unroot my HTC Desire S and get it back to the original form. here's some info regarding he phone
AlphaRev
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-38.03.02,15_M
eMMC-boot
endymion V3.3 is installed with sense 3.5
i have tried to get back to HBOOT-0.98.2000 using the PG88IMG.zip and the Android Flasher
but the android flasher shows this message and the HBOOT still remains the same (6.98.1002)
"sending 'hboot' (1024 KB)...
OKAY [ 0.192s]
writing 'hboot'...
(bootloader) image update is bypassed!
OKAY [ 0.016s]
finished. total time: 0.208s
rebooting into bootloader...
OKAY [ 0.165s]
finished. total time: 0.165s
rebooting...
finished. total time: -0.000s
"
any help will be greatly appreciated
Regards
download suitable RUU and flash it...
Applying the RUU will still leave the hboot.
Are other ways to change your hboot, you can try fastboot yourself (although thats what flasher is using), you can also try a dd command in adb shell.
Make sure that command is right, easy way to brick your phone!!!!!!
dd if=/dev/block/mmcblk0p18 of=/sdcard/backup.img (backup your current hboot)
dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18 (flashes new hboot)
Click to expand...
Click to collapse
And before you do anything, MAKE a goldcard, (mmc2) please, if people just made one as a safeguard they wouldn't have half the RUU problems they have.
Also make sure you you misc/main version is equal or lower than the RUU you will be flashing.
All this can be done by researching.
i just flashed a RUU rom in fastboot...hboot is still remains the same

[Q] writing 'recovery'...FAILED (remote: not allowed)

Hi, i have followed the tutorial for S-OFF my HTC sensation (http://forum.xda-developers.com/showthread.php?t=1864053). I'am right now S-OFF HBOOT 1.29 but when trying to flash recovery i get :
sending 'recovery' (4876 KB)...
OKAY [ 1.131s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.458s
What is wrong for me ?
Many thx for reply
I'm not sure why its not working need a bit more info but why not just rename to PG58IMG and flash through hboot?
Or use 4ext app from playstore
Sent from my HTC Sensation XE with Beats Audio Z715e using xda app-developers app
aranna said:
Hi, i have followed the tutorial for S-OFF my HTC sensation (http://forum.xda-developers.com/showthread.php?t=1864053). I'am right now S-OFF HBOOT 1.29 but when trying to flash recovery i get :
sending 'recovery' (4876 KB)...
OKAY [ 1.131s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.458s
What is wrong for me ?
Many thx for reply
Click to expand...
Click to collapse
You are s-off but your bootloader is locked. Unlock bootloader via HTC dev and the problem should be fixed.
Dosnt jupontubear hboot allow fastboot commands
Sent from my HTC Sensation XE with Beats Audio Z715e using xda app-developers app
AndroidSupporter318 said:
You are s-off but your bootloader is locked. Unlock bootloader via HTC dev and the problem should be fixed.
Click to expand...
Click to collapse
Hi,
If you are s-off,then do NOT use HTCDEV.
This will probably screw up your phone.
@aranna
If you have a locked bootloader look HERE
Use the :
HBoot 1.27.1100 Patch (Go from Hboot 1.29.0000 to 1.27.1100)
malybru said:
Hi,
If you are s-off,then do NOT use HTCDEV.
This will probably screw up your phone.
@aranna
If you have a locked bootloader look HERE
Use the :
HBoot 1.27.1100 Patch (Go from Hboot 1.29.0000 to 1.27.1100)
Click to expand...
Click to collapse
Hmm...that happened to me after I s-offed my sensation and all I did to fix it was to unlock it via htc dev...i guess i did it the wrong way, but nothing bad happened to my phone though...
AndroidSupporter318 said:
Hmm...that happened to me after I s-offed my sensation and all I did to fix it was to unlock it via htc dev...i guess i did it the wrong way, but nothing bad happened to my phone though...
Click to expand...
Click to collapse
Hi,
I am glad nothing bad happened to your phone.
But I have seen many instances of problems caused by using HTCDEV with s-off.
Kohr-Ah's solution is simple and effective.
Hum... i hope i understand well.. Here my complete current data
HBOOT 1.29
version-main: 3.33.401.153
cid: HTC__203
mid: PG5813001
As i understand i should download this one
Step 1) HBoot 1.27.1100 Patch (Go from Hboot 1.29.0000 to 1.27.1100) => downgrade to HBOOT 1.27
Step 2) Flash recovery with fastboot (can i use 4Ext Recovery recovery bin image ?
Step 3) HBoot 1.29.0000 Patch (Go from Hboot 1.27.1100 to 1.29.0000) => Go Back to HBOOT 1.29
I'am right ?
aranna said:
Hum... i hope i understand well.. Here my complete current data
HBOOT 1.29
version-main: 3.33.401.153
cid: HTC__203
mid: PG5813001
As i understand i should download this one
Step 1) HBoot 1.27.1100 Patch (Go from Hboot 1.29.0000 to 1.27.1100) => downgrade to HBOOT 1.27
Step 2) Flash recovery with fastboot (can i use 4Ext Recovery recovery bin image ?
Step 3) HBoot 1.29.0000 Patch (Go from Hboot 1.27.1100 to 1.29.0000) => Go Back to HBOOT 1.29
I'am right ?
Click to expand...
Click to collapse
No need for step #3
You can stay at 1.27.1100 hboot.. Changing to hboot 1.29 doesn't give you any advantage or benefit... There is technically no change between 1.29 hboot and 1.27.1100 hboot
Sent from my HTC Sensation using xda premium
samething is wrong, i have download and copy PG58IMG.ZIP file (HBoot 1.27.1100 Patch) on my sdcard root (MD5 is good), reboot on bootloader, it scan for file, but nothing happened... (on the list of file PG58IMG.zip is scanned)
aranna said:
samething is wrong, i have download and copy PG58IMG.ZIP file (HBoot 1.27.1100 Patch) on my sdcard root (MD5 is good), reboot on bootloader, it scan for file, but nothing happened... (on the list of file PG58IMG.zip is scanned)
Click to expand...
Click to collapse
do via fastboot way
copy the PG58IMG.zip to your adb/fastboot folder in PC
then connect the phone from bootloader to PC (if the phone says FASTBOOT USB that means it has proper connection)
then open command prompt from your adb/fastboot folder and type these commands one by one
fastboot erase cache (if failed ignore it )
fastboot oem rebootRUU (black screen with green HTC )
fastboot flash zip PG58IMG.zip (this will do the flashing of hboot )
fastboot reboot-bootloader (reboot to bootloader )
ganeshp said:
do via fastboot way
copy the PG58IMG.zip to your adb/fastboot folder in PC
then connect the phone from bootloader to PC (if the phone says FASTBOOT USB that means it has proper connection)
then open command prompt from your adb/fastboot folder and type these commands one by one
fastboot erase cache (if failed ignore it )
fastboot oem rebootRUU (black screen with green HTC )
fastboot flash zip PG58IMG.zip (this will do the flashing of hboot )
fastboot reboot-bootloader (reboot to bootloader )
Click to expand...
Click to collapse
WONDERFULL !!!!!!!!!! WHAT ELSE !!!! EXCEPT MANY THANKS !!!! S-OFF / 4Ext installer / HD REVOLUTION
Today I want to flash the cwm custom recovery to gain root and further install 4EXT. I have never done this before.
But I stuck on the first step:
I used an other thread (click here, but it's German). At the beginning, the author provides a collections of tools including the cwm recovery for step 5.
After entering the command shows:
C:\adb>fastboot flash recovery recovery.img
sending 'recovery' (4618 KB)... OKAY [ 1.094s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 1.411s
Click to expand...
Click to collapse
I did some researched and found this thread. I used the cwm recovery from that link step "flash the recovery".
But it shows the same error:
C:\adb>fastboot flash recovery recovery-clockwork-touch-5.8.0.9-pyramid.img
sending 'recovery' (4876 KB)... OKAY [ 1.128s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 1.445s
Click to expand...
Click to collapse
Here is a current photo of my bootloader.
I unlocked it with revolutionary while GingerBread was running. After that, I debranded my device and installed an official HTC RUU without branding (GingerBread) and did the update to ICS and via OTA to the latest provided version (see my signature). After that, it shows S-OFF but also *** locked ***
I´m not sure, what I have to do to gain my destination with 4EXT (requires root and this requires cwm) and finally Android Revolution HD or DarkForest.
Should I flash the universal firmware from here?
The command "fastboot getvar all" shows this:
C:\adb>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.27.0000
INFOversion-baseband: N/A
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.33.401.53
INFOserialno: ************** (censored...)
INFOimei: ************** (censored...)
INFOproduct: pyramid
INFOplatform: HBOOT-8260
INFOmodelid: PG5813000
INFOcidnum: HTC__102
INFObattery-status: good
INFObattery-voltage: 4133mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 617f0a98
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.495s
Click to expand...
Click to collapse
I don't want to brick my phone or my it unusable, so I´m very carefully.
*** EDIT:
I fixed the first step as follows:
I created a new zip file named "PG58IMG.zip". I put the recovery.img and the android-info.txt in it. The MID and CID in the txt-file have to match to my device. After that, I put the zip file onto my sdcard into the root directory. Then I started my device into bootloader and accepted the requested update. After that, I got my cwm recovery.
Source: http://forum.cyanogenmod.com/topic/74316-a-solution-to-fastboot-flash-recovery-not-allowed-error/
because you had a locked bootloader that's why you couldn't perform fastboot commands
you had to flash the pg58img.zip from bootloader as you did
it gave you also a patched hboot which is unlocked
ganeshp said:
do via fastboot way
copy the PG58IMG.zip to your adb/fastboot folder in PC
then connect the phone from bootloader to PC (if the phone says FASTBOOT USB that means it has proper connection)
then open command prompt from your adb/fastboot folder and type these commands one by one
fastboot erase cache (if failed ignore it )
fastboot oem rebootRUU (black screen with green HTC )
fastboot flash zip PG58IMG.zip (this will do the flashing of hboot )
fastboot reboot-bootloader (reboot to bootloader )
Click to expand...
Click to collapse
thank you!!! after scouring the internet for answers for hours & hours, this one finally did it!
AndroidSupporter318 said:
You are s-off but your bootloader is locked. Unlock bootloader via HTC dev and the problem should be fixed.
Click to expand...
Click to collapse
Not true. Just did it. I am not able to enter recovery mode
writing 'recovery'... FAILED (remote: not allowed)
nass1470 said:
Not true. Just did it. I am not able to enter recovery mode
writing 'recovery'... FAILED (remote: not allowed)
Click to expand...
Click to collapse
did you unlock the bootloader?
rzr86 said:
because you had a locked bootloader that's why you couldn't perform fastboot commands
you had to flash the pg58img.zip from bootloader as you did
it gave you also a patched hboot which is unlocked
Click to expand...
Click to collapse
writing 'recovery'... FAILED (remote: not allowed)
I USED 4EXT RECOVERY.IMG
I do not know what to do anymore
nass1470 said:
writing 'recovery'... FAILED (remote: not allowed)
I USED 4EXT RECOVERY.IMG
I do not know what to do anymore
Click to expand...
Click to collapse
can you post your bootloader details pls?
rzr86 said:
can you post your bootloader details pls?
Click to expand...
Click to collapse
His problem is exactly as u said, he has to unlock bootloader via htcdev again. I had to do it with my old sensation because i flashed an ruu so then the bootloader became relocked but still s-off so to use fastboot commands again i had to unlock bootloader.

[Q] CM11 and Hboot 2.13

Will I be able to flash CM11 or any other KK ROM with Hboot 2.13? I have searched around without much luck, when I updated my Hboot, I got stuck with this strange version of it.
Thanks
gooner98 said:
Will I be able to flash CM11 or any other KK ROM with Hboot 2.13? I have searched around without much luck, when I updated my Hboot, I got stuck with this strange version of it.
Thanks
Click to expand...
Click to collapse
Try upgrade your hboot to 2.15:
1. Download here
2. Move the file to the location of fastboot on your computer
3. Windows: Open fastboot folder and hold shift and right click, then select Open Command Window Here.
Mac: Open a terminal window and your fastboot folder alongside each other. drag fastboot from folder to terminal window
4. Get into fastboot mode and type the following commands
fastboot oem rebootRUU
fastboot flash zip orig_hboot_2.15.0000.zip
fastboot reboot-bootloader
5. You should see Hboot 2.15.0000. If you had s-off with hboot 2.13 you will have it with 2.15
6. You should be able to flash cm11 nightlies now
Thanks for that, I'll give it a go.
OK, I got a fail
C:\fastboot>fastboot oem rebootRUU
... INFOStart Verify: 0
OKAY [ 0.280s]
finished. total time: 0.280s
C:\fastboot>fastboot flash zip orig_hboot_2.15.0000.zip
sending 'zip' (400 KB)... OKAY [ 0.238s]
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 1.928s
C:\fastboot>fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 0.383s]
finished. total time: 0.383s
Do the command again, when you flash your firmware.zip with fastboot, this first try fail but the second is good. I don't know it may be some kind of security
Envoyé de mon One S en utilisant Tapatalk
Hi Guys
Any confirmation with this one? Did it work?
I do also have similat HBoot 2.13.
Have a phone from "3" / Three UK network with this HBOOT.
I was able to do the S-OFF.
Previous CID: CID: H3G__001 (H3G_01)
Current state:
CID: 11111111
Bootloader (HBOOT) 2.13 version
Baseband is 1.11.50.05.28
TWRM 2.6.0.0
Model: PJ4010000
I have checked the zip file from this thread and found txt file with details:
modelid: PJ4010000
cidnum: HTC__001
mainver: 3.16.401.8
btype:1
aareport:1
hbootpreupdate:1
...
Should I change CID before proceeding with HBOOT upgrade?
I am really afraid cause flashing HBOOT causes most of the bricks?
You guys are either not reading much or dont know how to search. The assert check in updater-script for any ROM allows flashing for the following hboots: 2.13.0000, 2.15.4444 and 2.15.0000
It is like this from the beginning and it was stated several times. So you don't need to update any hboot if you're on 2.13.
Sent from nowhere over the air...
Thanks Rapier. and I am sorry for taking your time. can I just clarify? you're saying that I can flash my phone with even kitkat (4.4) when I am on HBOOT 2.13? even when all threads are mentioning HBOOT in version 2.15/2.16?
really confusing for me. like I have missed something really basic over the last 3-4 weeks of reading this forum ?

Having trouble changing the CID

Hello,
I have an HTC One S (S4 version from t-mobile), and was hoping to upgrade from HBOOT 2.15 to 2.16. I have already unlocked my device via HTC-dev, installed a custom recovery and rom, and have root access
From the various tutorials I figure that I need to get SuperCID, S-OFF, and then I touch the write protected parts of the phone.
However, when I try to get SuperCID per this tutorial, The cid does not change from
Code:
$ sudo fastboot oem readcid
...
(bootloader) cid: T-MOB010
OKAY [ 0.009s]
finished. total time: 0.009s]
to 11111111.
Any thoughts? I am using an ubuntu 16.04 machine.

Categories

Resources