Database Info

How on the earth can i have "S OFF''????

Ok as soon as some one reads the title they would be thinking another thread by a noob. I may be a noobb but after having many android devices and installing many custom ROMs its hard act like a noob. But i am really frustrated with the complications that are involved in getting the S OFF on HTC Sensation.
I have gone through all the possible posts on achieving the S OFF but with no luck at all Now can some one please help me here????
Ok now my phone is running Hboot version 1.18 and i have tried the revolutionary method some 10 times and i also looked in to this tool as well http://forum.xda-developers.com/showthread.php?t=1668276 but still cant get S OFF. I have few questions for which i have searched all over the web only to find different answers.
Do i need both S OFF and Unlock on the phone to install a custom ROM? And also do i need the S OFF first to do the super CID? Because i thought if i can at least have the super CID i can run a different RUU and have ICS. But again failed to achieve CID it says HTC_038 instead of 11111.
I have read in several places that i need the latest 3.32 firmware to install a ICS ROM. So i am yet to figure out how on the earth can i install the 3.32 firmware.
I have unlocked my phone using HTC Dev website and i have also rooted the phone. I have installed the CWM but not able to flash a custom ROM. So should i have first done the S OFF and then unlock it or can i still S Off on the phone with the boot loader unlocked?
So in case if i have to re lock the device then do the S OFF , can some one give a link to the latest RUU?
Or can some one help me find a way to S OFF???? Thanks for any help.

shri080 said:
Ok as soon as some one reads the title they would be thinking another thread by a noob. I may be a noobb but after having many android devices and installing many custom ROMs its hard act like a noob. But i am really frustrated with the complications that are involved in getting the S OFF on HTC Sensation.
I have gone through all the possible posts on achieving the S OFF but with no luck at all Now can some one please help me here????
Ok now my phone is running Hboot version 1.18 and i have tried the revolutionary method some 10 times and i also looked in to this tool as well http://forum.xda-developers.com/showthread.php?t=1668276 but still cant get S OFF. I have few questions for which i have searched all over the web only to find different answers.
Do i need both S OFF and Unlock on the phone to install a custom ROM?
I have read in several places that i need the latest 3.32 firmware to install a ICS ROM. So i am yet to figure out how on the earth can i install the 3.32 firmware.
I have unlocked my phone using HTC Dev website and i have also rooted the phone. I have installed the CWM but not able to flash a custom ROM. So should i have first done the S OFF and then unlock it or can i still S Off the phone with the boot loaded unlocked?
So in case if i have to re lock the device then do the S OFF first can some one give a link to the latest RUU?
Or can some one help me find a way to S OFF???? Thanks for any help.
Click to expand...
Click to collapse
1.SOFF is pretty simple for you ..don't know what actually caused you the problem as you havent mentioned what error happened when trying SOFF process
now when you said you tried revolutionary you might have zerg root failed error
if thats the case
kgs tool would have solved the issue ...but you are saying that failed too (which normally wont happen)
that says that you tried kgs tool with unlocked bootloader and having cwm recovery also root ..to SOFF which wont work
(the alternative to by pass the zerg root error revolutionary has a prerequisite which is to have everything completely stock )
now ...the question comes how to do SOFF then
kgs tool has already given the solution (YOU read all the guides and searched all over the world ..but forgot to read the second post in the kgs tool guide )
as i am a good man and i feel like helping a blind person ...i'll tell you where
in the second post of the thread you've linked
TIPS sub section - 6th point ..please foolw the post there ..to make SOFF work
now regarding the other questions
1.no way you can flash a firmware unless you are SOFF
2.once you got SOFF via revolutionary ..dont even bother about HTC-dev unlock ...as the bootloader provided by revolutionary after SOFF(engineering-bootloader) ..is much much better than the HTC-DEV unlocked bootloader
3.After SOFF best guide for you to flash ICS rom is this (post #1 and post #2)

Thanks a lot for you quick reply. really appreciated !! I am not a complete blind though well i tried restoring the recovery image back to stock then tried the kgs tool but it again failed. The only thing i had not tried was to do the factory reset after restoring the stock recovery. I extracted the stock recovery.img by running the Indian RUU. But i dont know if it makes any difference if i flash the recovery image attached in that post. Let me try that too Thanks again for taking time to reply !!!

shri080 said:
Thanks a lot for you quick reply. really appreciated !! I am not a complete blind though well i tried restoring the recovery image back to stock then tried the kgs tool but it again failed. The only thing i had not tried was to do the factory reset after restoring the stock recovery. I extracted the stock recovery.img by running the Indian RUU. But i dont know if it makes any difference if i flash the recovery image attached in that post. Let me try that too Thanks again for taking time to reply !!!
Click to expand...
Click to collapse
can you please elaborate the error you got when you did SOFF ....screenshot will do too ..if you tell us the exact error you got ..you might get perfect solution
until then it will be shot in the dark
PS: regarding the blind comment ..dont take it seriously ...its meant to be sarcastic thats all

I know what this error is. [ Failed to get root & taco root also fails. Happens on an unlocked bootloader ]
Please come over to the help channel: #helpmenow.
Once there, ping me by typing my name.

ok i also had some issues to S-OFF my sensation with HBoot 1.18
now here what i did to successfully S-OFF the device and root it..
1st Download Tacoroot (as you already told that revolutionary isnt working for you) :- http://db.tt/PxZRO0d1
then switch on your sensation and connect your HTC to your PC in Charger Mode and Enable USB Debugging.. [ Remember to install HTC Drivers ]
now open adb and type the commands [ dont forget to keep the tacoroot.bin file on your adb folder ]
Code:
adb push tacoroot.bin /data/local
adb shell chmod 755 /data/local/tacoroot.bin
adb shell /data/local/tacoroot.bin --setup
The phone will reboot to recovery.
Press Volume Up, Volume Down and Power.
Reboot.
Press the Power button once if the screen remains blank (dark).
Wait for boot.
Run the following command.
Code:
adb shell /data/local/tacoroot.bin --root
The phone will reboot.
Run Revolutionary and now try to S-OFF your mobile using revolutionary.
Once Revolutionary is successful, reboot.
Run the following command.
Code:
adb shell /data/local/tacoroot.bin –undo
now once its done install recovery and continue flashing your rom.
This tut i found on XDA by a member .. Thanks to him :
Code:
http://forum.xda-developers.com/showpost.php?p=23482010&postcount=29

[SOLVED]
deepsaha007 said:
ok i also had some issues to S-OFF my sensation with HBoot 1.18
now here what i did to successfully S-OFF the device and root it..
1st Download Tacoroot (as you already told that revolutionary isnt working for you) :- http://db.tt/PxZRO0d1
then switch on your sensation and connect your HTC to your PC in Charger Mode and Enable USB Debugging.. [ Remember to install HTC Drivers ]
now open adb and type the commands [ dont forget to keep the tacoroot.bin file on your adb folder ]
Code:
adb push tacoroot.bin /data/local
adb shell chmod 755 /data/local/tacoroot.bin
adb shell /data/local/tacoroot.bin --setup
The phone will reboot to recovery.
Press Volume Up, Volume Down and Power.
Reboot.
Press the Power button once if the screen remains blank (dark).
Wait for boot.
Run the following command.
Code:
adb shell /data/local/tacoroot.bin --root
The phone will reboot.
Run Revolutionary and now try to S-OFF your mobile using revolutionary.
Once Revolutionary is successful, reboot.
Run the following command.
Code:
adb shell /data/local/tacoroot.bin –undo
now once its done install recovery and continue flashing your rom.
This tut i found on XDA by a member .. Thanks to him :
Code:
http://forum.xda-developers.com/showpost.php?p=23482010&postcount=29
Click to expand...
Click to collapse
Tacoroot did not work for him. It was something else.
In some phones, tacoroot causes the phone to get stuck on the HTC screen.
The phone can't be temp rooted that way.
This happens usually only in HTC dev unlocked phones that had custom recovery installed and then flashed stock recovery before tacoroot.
Sent from my HTC Sensation XE with beats audio
PS: anyone who wants to know how to make this work -
Root your phone by installing su.
Modify local.prop to get root prompt by default in shell.

ohh i see , i didn't have that problem but once i was stuck in boot loop after i upgraded the firmware to install ics but it was fixed after i installed a custom ICS rom..

[Q] I need help with S-Off/Installing ROMs on hboot 1.14. See my problem?

So I've done the procedures correctly from the Facepalm S-Off for HTC One S and I still don't have S-Off.
I got to the last process of getting S-Off, did the:
adb push soffbin3 /data/local/tmp/
adb shell chmod 744 /data/local/tmp/soffbin3
adb shell su -c "/data/local/tmp/soffbin3"
then rebooted to bootloader to see if I have S-Off, but then I still don't.
I read online somewhere that with S-Off, I could install a ROM easily through recovery, is it true?
I also need help installing ROMs on this phone ):
Here's the story:
I hardbricked my old HTC so I got a new one. My old one, one that I bought after graduation around June, it had hboot 1.09 and was able to install ROMs easily in twrp while I was S-On+Unlocked Bootloader ONLY. No SuperCID or S-Off. So, I bought a new HTC One S from someone selling it on Craigslist. It had hboot 1.14, which I did not check yet. I bought it, so happy I got another One S until I realized I was only getting EDGE/2G. I read somewhere online where it was part of T-Mobile's update that messed it up, and a way to fix it was to install a new ROM. Any ROM I tried installing wouldn't go past the boot animation screen. Let's say I installed BB7, it wouldn't go past the boot animation.
If anyone can help, please. I'm on a 4g plan on T-Mobile getting only EDGE/2g and not able to install any other ROMs w/out getting stuck on boot animation. Old phone was faster than this.
HTC One S | hboot 1.14 | radio 1.08 | SuperCID | Stock Rom atm (until I install new ROM)
If anyone needs any additional info to assist in my doing, feel free to ask. Thank you!

dinodustin said:
So I've done the procedures correctly from the Facepalm S-Off for HTC One S and I still don't have S-Off.
I got to the last process of getting S-Off, did the:
adb push soffbin3 /data/local/tmp/
adb shell chmod 744 /data/local/tmp/soffbin3
adb shell su -c "/data/local/tmp/soffbin3"
then rebooted to bootloader to see if I have S-Off, but then I still don't.
I read online somewhere that with S-Off, I could install a ROM easily through recovery, is it true?
I also need help installing ROMs on this phone ):
Here's the story:
I hardbricked my old HTC so I got a new one. My old one, one that I bought after graduation around June, it had hboot 1.09 and was able to install ROMs easily in twrp while I was S-On+Unlocked Bootloader ONLY. No SuperCID or S-Off. So, I bought a new HTC One S from someone selling it on Craigslist. It had hboot 1.14, which I did not check yet. I bought it, so happy I got another One S until I realized I was only getting EDGE/2G. I read somewhere online where it was part of T-Mobile's update that messed it up, and a way to fix it was to install a new ROM. Any ROM I tried installing wouldn't go past the boot animation screen. Let's say I installed BB7, it wouldn't go past the boot animation.
If anyone can help, please. I'm on a 4g plan on T-Mobile getting only EDGE/2g and not able to install any other ROMs w/out getting stuck on boot animation. Old phone was faster than this.
HTC One S | hboot 1.14 | radio 1.08 | SuperCID | Stock Rom atm (until I install new ROM)
If anyone needs any additional info to assist in my doing, feel free to ask. Thank you!
Click to expand...
Click to collapse
Did you try fastboot flashing the boot.img?

dbrewer24 said:
Did you try fastboot flashing the boot.img?
Click to expand...
Click to collapse
Yes, I did that before flashing the ROM zip in twrp

dinodustin said:
Yes, I did that before flashing the ROM zip in twrp
Click to expand...
Click to collapse
Have you tried doing it after? I have seen different instructions that say to do it different ways.

I have heard about the data issue too. I heard you could just go to network settings. change it to GSM only and then reboot. then switch back to Auto and rebooted again and it would come back (not an official solution... just something I read on here somewhere)
I am not have this issue.
regarding flashing a new ROM.... the phone should not be doing this...
I would go through the final steps of S-off again and see if you can get it to work.
I have heard of some issues that people are having... so I have not tried S-off yet... It doesnt bug me... it takes two more seconds to use fastboot.
just keep trying with different process... like hard reset then flash. or recover an old ROM then wipe and flash... IDK... just trying to help.
good luck

dbrewer24 said:
Have you tried doing it after? I have seen different instructions that say to do it different ways.
Click to expand...
Click to collapse
Like which instructions? I've tried to flash through TWRP, but I've seen other people have problems with flashing through TWRP with hboot 1.14, which includes me. So, I've tried that method and using CMD to fastboot it. Both didn't go so well. I also haven't tried testing other ROMs cos I've tried to flash 2 different ROMs (BB7, Liquid Smooth, JellyBam 4.1.0), but all 3 of them stayed on the boot animation screen and I never got to use my phone. My solution to those not working since I'm not able to flash any ROMs was to Go into Bootloader> Relock Bootloader > Go to Fastboot > & Ran RUU_Ville_U_ICS_40_S_TMOUS_2.35.531.7_Radio_1.08ts.50.02.16_10.08e.50.04L_release_279577_signed.exe
Ryandroid86 said:
I have heard about the data issue too. I heard you could just go to network settings. change it to GSM only and then reboot. then switch back to Auto and rebooted again and it would come back (not an official solution... just something I read on here somewhere)
I am not have this issue.
regarding flashing a new ROM.... the phone should not be doing this...
I would go through the final steps of S-off again and see if you can get it to work.
I have heard of some issues that people are having... so I have not tried S-off yet... It doesnt bug me... it takes two more seconds to use fastboot.
just keep trying with different process... like hard reset then flash. or recover an old ROM then wipe and flash... IDK... just trying to help.
good luck
Click to expand...
Click to collapse
I'll try changing my network settings and get back to you on that.
How long would you wait on the Boot Animation screen? Cos I waited for about 5 minutes for it to load and it never loaded all the way.
I've tried the final step +3 times. The last few times I've tried it, it looked successful when I saw that my CMD sent the file and it said "OKAY", so I rebooted into my Bootloader like the very last step Facepalm's S-Off guide had said, but I didn't see what I was looking for ):
I've tried hard reset and flash, no luck. I'll try the old ROM thing.
It's such a hassle to get back to a working ROM, which you all know is phone's stock ROM I've been using, with the RUU exe.

suggestion
If your s off u should try flashing the .1.09 hboot, with s off its easier than ever to upgrade or downgrade an hboot, I have had throuble on higher hboots to even with s off

dinodustin said:
So I've done the procedures correctly from the Facepalm S-Off for HTC One S and I still don't have S-Off.
HTC One S | hboot 1.14 | radio 1.08 | SuperCID | Stock Rom atm (until I install new ROM)
If anyone needs any additional info to assist in my doing, feel free to ask. Thank you!
Click to expand...
Click to collapse
I have a Tmous too, the only way i got S-off was installing previously all t-mobile updates, ithen was easy getting s-off, but i don't know if that will solve your 4G problem, because i never had that.
(sorry about my english)
charly

Sorry I got ahead of my self I my post, I could only s off on viper 1.2 it was wierd, but let me ask u this do u get error 92 or 99 after flashing the zip

Ice Master Ben said:
Sorry I got ahead of my self I my post, I could only s off on viper 1.2 it was wierd, but let me ask u this do u get error 92 or 99 after flashing the zip
Click to expand...
Click to collapse
The very first time i get 92 an then failed in the second part of "pushing soffbin", when i tried again, i get error 99, but then i read some post about powering off the device, and it worked i get again error 92 and worked fine.

I had the same error and situation, first time error 92 but not after that,keept getting error 99 keept trying with diffrent Roms until I got the 92. I was on the 1.09 hboot the funny part is since I have s off I upgraded to the latest hboot 2.15( thanks to the flashable zips in the theam section) to my surpprize I could not flash viperon that hboot, so I went back to my 1.09 hboot and everything worked really good like always, so my poqint is were still having problems on higher hboots even with s off why?????, the only good thing about s off I have found is thanks to the flashable zips we can upgrade or downgrade the hboot just by flashing it, now its back to the 1.09 hboot

Ice Master Ben said:
If your s off u should try flashing the .1.09 hboot, with s off its easier than ever to upgrade or downgrade an hboot, I have had throuble on higher hboots to even with s off
Click to expand...
Click to collapse
Related to this, i have S-Off and Hboot 1.09, yet am still having problems flashing the latest daily CM 10.1 roms to by One XL, any suggestions?
I'm getting an immediate FAILED error in TWRP 2.6

Try twrp 2.3.3.0 it's supposed to be the most stable
Sent from my HTC One S using xda app-developers app

[Q] CM10.1 to AOKP Touch screen issue

Hey, first time I'm posting here. I recently was able to root, unlock bootloader, and flash a custom ROM for my AT&T HTC One X. I started with CM 10.1 and got that to work fine. I'm using the latest version of clockwork recovery and have made several backups (I'm a bit paranoid about ruining my phone).
After getting CM 10.1 to work, I wanted to try out AOKP. I've downloaded both the Milestone as well as a nightly build. I've followed the instructions carefully to try to get this ROM to work and even tried some variants. I've wiped cache, dvalrik cache, factory reset and then flashed the boot.img. And then I've gone into recovery and loaded the milestone onto my phone after rewiping the cache, dvalrik cache and factory reset. I then loaded the google apps. I've tried flashing flashing the ROM first, the boot.img first, and any number of different cache wipes and factory resets. And every time I seem to have the same problem: my touchscreen refuses to work. I get to the setup page for the ROM and all the other buttons work, but not the touchscreen. I've looked everywhere I could think of for a solution to this problem but couldn't find one. Can anybody help me out?
I also should mention that each time I've been successful in restoring my phone to CM 10.1 using a backup, and no touchscreen problem persists.

What hboot are you on? And which cm10.1 did you flash? The latest nightly?
Sent from my Evita

Additional Info:
HBoot-2.14
Radio-0.24p.32.09.06
S-On
OpenDSP-v34.1.0.45.1219
Thanks.

timmaaa said:
What hboot are you on? And which cm10.1 did you flash? The latest nightly?
Sent from my Evita
Click to expand...
Click to collapse
Flashed cm10.1-20130623-unofficial. And hboot is above.

Ok I believe the latest CM builds have been made to work with the newer touchscreen firmware, so I think that's why cm is working ok for you. You have the newer touchscreen firmware, by looking at your hboot version.
To use all other aosp ROMs you'd need to downgrade your touchscreen firmware, which means you would need to s-off first.
Sent from my Evita

timmaaa said:
Ok I believe the latest CM builds have been made to work with the newer touchscreen firmware, so I think that's why cm is working ok for you. You have the newer touchscreen firmware, by looking at your hboot version.
To use all other aosp ROMs you'd need to downgrade your touchscreen firmware, which means you would need to s-off first.
Sent from my Evita
Click to expand...
Click to collapse
Yeah I literally just found this thread: http://forum.xda-developers.com/showthread.php?t=2159863.
So that's the process I need to go through, which requires S-Off... Is there any way I can tell if I have superCID already for the facepalm s-off process?
Thanks for your help!

steffyd said:
Yeah I literally just found this thread: http://forum.xda-developers.com/showthread.php?t=2159863.
So that's the process I need to go through, which requires S-Off... Is there any way I can tell if I have superCID already for the facepalm s-off process?
Thanks for your help!
Click to expand...
Click to collapse
boot to bootloader/fastboot
do:
fastboot oem readcid
if it says 11111111 or 22222222 then supercid=yes
if its anything else then no

exad said:
boot to bootloader/fastboot
do:
fastboot oem readcid
if it says 11111111 or 22222222 then supercid=yes
if its anything else then no
Click to expand...
Click to collapse
Thanks guys! Got it all worked out now, I appreciate the help!

Just make sure you only flash ROMs from this section, if you flash an International One X ROM you'll brick your phone.
Welcome to XDA
Sent from my Evita

got any guide on how do i s-off without being able to touch the screen? android debugging was not enabled by default. however, i can get into cwm n use all the features there. im having a evita with cm10.1, when i install cm, i wipe all, so the rom loads but i cant touch anything, adb was not recognise bcos i cant turn on usb debugging.

Try flashing a Sense ROM.
Sent from my Evita

The reason im getting my hands on custom rom is bcos my stock XL(Asian version) will neve sync google contacts properly, i tried to flash ICS/JB stock RUU, but its same. then, i started to tamper my fon with unlocking bootloader via htcdev, flash cwm(twrp mess on my sdcard storage). i had experience on older htc devices but its my 1st time on the htc one series. right now, im on evita s-on, unlocked bootloader, hboot 2.14, cwm recovery(twrp mess on my sdcard storage), not-super CID. I 'm left with a non-touchable cm10.1, i can flash any rom that supports s-on. tried to relock bootloader but i cant flash stock ICS ruu.will try stock JB RUU now. my target now is to s-off n superCID.

i have read alot of posts, but most sense rom require s-off. do u know which one that i can flash with s-on?

None of the Sense ROMs "require" s-off.
Sent from my Evita

thx timmaa. i restored to sense 5 rom n then proceed to s-ooff/dgrade tpanel, all works fine. here are my ways, all credits belong to the OP, i just wanna put up my ways here, so forummers who faces same problem will find a simpler solution, i hope it has not been posted cos i cant search for the solution yest :
the XL nick is evita, X is endeavour
unlock bootloader at htcdev.com
fastboot flash recovery TWRP5.img, if it messed with storage, use CWM
fLASH CUSTOM ROM N REMEMBER TO fastboot flash boot boot.img (use Evita Sense 5 R3 if touch panel not working), custom rom already rooted
-----------------------------------------------------------------------------------------------------------------
SuperCID (must have root, usb debugging enabled)
adb shell
# su
# echo -ne "11111111" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
Reboot to bootloader n
fastboot getvar cid
the cid shud be 11111111
--------------------------------------------------------------------------------------------------------------------
S-off (must have unlocked bootloader, rooted, superCID) facepalm method
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip PJ8312000-OneX.zip
After a while, You should see the following error “FAILED (remote: 92 supercid! please flush image again immediately)”
fastboot oem boot
You may see some errors, just wait for the device to boot into Android (only now, you should be booted into Android with no eMMC write protection of any kind active).
adb push soffbin3 /data/local/tmp/
adb shell chmod 744 /data/local/tmp/soffbin3
adb shell su -c "/data/local/tmp/soffbin3"
adb reboot bootloader

Need serious Help concerning roms

Hey guys,
I have a serious problem with my at&t htc one x, first time when i wanted to install a custom rom, i didn't backup ( i know my fault)
i had some problems with installation that drives me to change my cid to HTC_621 ( i don't know why i changed the 1st time, im noob)
now i can only install custom roms like viperXL and also,but it drains my battery,so i want to go back to stock room, or CM10.2 but i can't, when i try RUU it always give me an error, and when i downloaded the CM10.2.zip and tried to flash it via twrp it says Installation Failed. im totally confused and need real help.
my HBOOT infos:
Tampered
Unlocked
EVITA PVT SHIP S ON RL
HBOOT 1.14.0002
RADIO 0.19as.32.09.11_2
OpenDSP-v29.1.0.45.622
eMMC-boot
Jun 11 201. 14:36

What's your Cid? It should be 1111 etc.. Make sure ur super cid, then s- off.. After following those steps then try running the RUU
Sent from my Nexus 4 using XDA Premium 4 mobile app

zinter95 said:
Hey guys,
I have a serious problem with my at&t htc one x, first time when i wanted to install a custom rom, i didn't backup ( i know my fault)
i had some problems with installation that drives me to change my cid to HTC_621 ( i don't know why i changed the 1st time, im noob)
now i can only install custom roms like viperXL and also,but it drains my battery,so i want to go back to stock room, or CM10.2 but i can't, when i try RUU it always give me an error, and when i downloaded the CM10.2.zip and tried to flash it via twrp it says Installation Failed. im totally confused and need real help.
my HBOOT infos:
Tampered
Unlocked
EVITA PVT SHIP S ON RL
HBOOT 1.14.0002
RADIO 0.19as.32.09.11_2
OpenDSP-v29.1.0.45.622
eMMC-boot
Jun 11 201. 14:36
Click to expand...
Click to collapse
Why did you change the CID to HTC__621? That doesn't even look like it's for our device. That's the reason the RUU is failing.
The reason cm10.2 won't boot is because you need to RUU to 3.18 with the 2.14 hboot to flash that ROM, it does state that clearly in the install instructions for that ROM.
You're gonna need to get SuperCID first, then you can get s-off, then you can RUU to 3.18, then you can flash the cm10.2 ROM.
Sent from my Evita

I tried to SuperCID but i couldnt, i tried the hex editor way, but it gives me always errors, i guess thats why i can s-off.
Any solutions?

Ok, but why did you change it HTC__621? I don't think that's a CID for our device, were you trying to install software or something? The only problem is that without s-off you can only manually change the CID once, and you've used that one chance up by changing it to HTC__621. As far as a solution goes I'm not sure, there are a few different methods to change your CID, I'd suggest you try them all.
Sent from my Evita

zinter95 said:
I tried to SuperCID but i couldnt, i tried the hex editor way, but it gives me always errors, i guess thats why i can s-off.
Click to expand...
Click to collapse
SuperCID is mandatory for the s-off method. So yes, that is why you can't s-off.

i changed my cid to 11111111 now, but i still cannot change it to s-off i followed the instructions but i always failed.

You need to give more info. Where in the process did it fail?
Sent from my Evita

At the first time i failed when i type that code;
Code:
adb push soffbin3 /data/local/tmp/
adb shell chmod 744 /data/local/tmp/soffbin3
adb shell su -c "/data/local/tmp/soffbin3"
and when i wanted to try another time it keeps failing in the step before that one.

You're not being very specific, just saying it fails doesn't help diagnosing the problem.
Have you extracted the soffbin zip into the fastboot folder as per the instructions? Do you have usb debugging enabled in developer options? If applicable (on aosp ROM) have you granted adb root access in developer options?
When you say the step before that one, you mean the fastboot flash zip command right? And my guess is that you're getting error 99 instead of error 92? If you get error 99, force a reboot into the bootloader (by holding volume down and power) and start again from the beginning.
Sent from my Evita

timmaaa said:
You're not being very specific, just saying it fails doesn't help diagnosing the problem.
Have you extracted the soffbin zip into the fastboot folder as per the instructions? Do you have usb debugging enabled in developer options? If applicable (on aosp ROM) have you granted adb root access in developer options?
When you say the step before that one, you mean the fastboot flash zip command right? And my guess is that you're getting error 99 instead of error 92? If you get error 99, force a reboot into the bootloader (by holding volume down and power) and start again from the beginning.
Sent from my Evita
Click to expand...
Click to collapse
heey, im in this step right now
adb push soffbin3 /data/local/tmp/
adb shell chmod 744 /data/local/tmp/soffbin3
adb shell su -c "/data/local/tmp/soffbin3"
any time i run that command it says Device offline or device not found, but i have the latest updates of htc synmanager ..
im running RageXl 1.03 ROM.
How can i solve it please?

Uninstall HTC Sync Manager but leave the drivers installed. Make sure you have usb debugging enabled in developer options. When you try again you might get error 99 instead of error 92 after flashing the zip st the beginning. If this happens, force a reboot back to bootloader by holding volume down and power and start again from the beginning of the process.
Sent from my Evita

timmaaa said:
Uninstall HTC Sync Manager but leave the drivers installed. Make sure you have usb debugging enabled in developer options. When you try again you might get error 99 instead of error 92 after flashing the zip st the beginning. If this happens, force a reboot back to bootloader by holding volume down and power and start again from the beginning of the process.
Sent from my Evita
Click to expand...
Click to collapse
i uninstalled htc syn manager but it still telling me device offline!!!!!!!!!!!!!!!!!

Wow, that's a lot of exclamation marks. Maybe you need to try on a different ROM. Check your drivers, check adb, make sure usb debugging is enabled. It's almost impossible for me to diagnose what's going on without being there, you need to troubleshoot it.
Sent from my Evita

timmaaa said:
You're not being very specific, just saying it fails doesn't help diagnosing the problem.
Have you extracted the soffbin zip into the fastboot folder as per the instructions? Do you have usb debugging enabled in developer options? If applicable (on aosp ROM) have you granted adb root access in developer options?
When you say the step before that one, you mean the fastboot flash zip command right? And my guess is that you're getting error 99 instead of error 92? If you get error 99, force a reboot into the bootloader (by holding volume down and power) and start again from the beginning.
Sent from my Evita
Click to expand...
Click to collapse
Heey,
I installed an aosp rom, and everything was going alrgiht until the last step , the last command;
C:\Android>adb shell su -c "/data/local/tmp/soffbin3.zip"
/data/local/tmp/soffbin3.zip[2]: ┴¹Í♣î¶: not found
/data/local/tmp/soffbin3.zip[4]: syntax error: '³' unexpected
/data/local/tmp/soffbin3.zip[2]: ©╚ÇÎ⌂idþº╬R░4↔´NØU÷Å┘)È¿jØ&j+ò╩U¿PñF╩‗ÇTAäBÑJÇJ
ôç
►╝D<B}░wYQéäèÈ─ï¨╬▄;╗wªnEÃ>{¯╣þþ×{¯╣?þ╣╣┼yMË╚*ö: not found
/data/local/tmp/soffbin3.zip[2]: ┘ªnc↕♂mè◄←ßîÃÚ: not found
/data/local/tmp/soffbin3.zip[2]: can't create │╗▒Î÷: Read-only file system
/data/local/tmp/soffbin3.zip[2]: ô♦ý☻─Q└: not found
/data/local/tmp/soffbin3.zip[2]: ª↕Wê2└Ù}▄G╗2öó^*▲ñ¹®ç♦/│.×: not found
C:\Android>
i dont know whats the problem, may you help me?

What language and locale is your Windows and phone set to?
To me it looks like an application that does not correctly handle non-English locales.
Or something is corrupt.

twistedddx said:
What language and locale is your Windows and phone set to?
To me it looks like an application that does not correctly handle non-English locales.
Or something is corrupt.
Click to expand...
Click to collapse
my phone is set to english and my computer to french!but i dont think thats the problem.

anyone can help me guys??

You've entered the command incorrectly. There should be no ".zip" at the end of the command. Because of this I'm also assuming you haven't extracted (unzipped) the soffbin zip file into your adb/fastboot folder? Read the instructions on the s-off thread again, you must follow them absolutely precisely with no deviations.
Sent from my Evita

timmaaa said:
You've entered the command incorrectly. There should be no ".zip" at the end of the command. Because of this I'm also assuming you haven't extracted (unzipped) the soffbin zip file into your adb/fastboot folder? Read the instructions on the s-off thread again, you must follow them absolutely precisely with no deviations.
Click to expand...
Click to collapse
Yeah, when modding your phone, don't improvise or add things, unless you are positive of what you are doing. Folks have bricked their phones by not following instructions exactly.

How To Install Cyanogenmod with S-ON??

Hi,
I have just unlocked my HTC A9, says it's unlocked in bootloader. S-ON is still on and I think it's stopping me from installing TWRP as my recovery image so I cannot flash the Cyanogenmod .zip file. Does anyone know how I can turn S-ON off or where I should go from here, how that the bootloader is unlocked.
Thanks,
Kieran

Go to htcdev.com on your computer and follow the steps to unlock bootloader. Your phone won't be S-off but with the unlocked bootloader you'll be able to fastboot the twrp recovery.

Your phone does not need s-off in order to flash custom recoveries and ROMS, all that you need is an unlocked bootloader

Bull****, you can't flash recoveries or bootloader with "S-ON"
>FAILED (remote: cannot flash this partition in s-on state)
How do you change it to S-OFF?

Jisifus said:
Bull****, you can't flash recoveries or bootloader with "S-ON"
>FAILED (remote: cannot flash this partition in s-on state)
How do you change it to S-OFF?
Click to expand...
Click to collapse
Well that's strange, I'm s-on with twrp 3.0.0.2 and the latest cyanogenmod nightly running
Sent from my HTC One A9 using XDA-Developers mobile app

MGfusion said:
Well that's strange, I'm s-on with twrp 3.0.0.2 and the latest cyanogenmod nightly running
Sent from my HTC One A9 using XDA-Developers mobile app
Click to expand...
Click to collapse
It turns out I was in the white background bootloader, not the download mode, that's why it didn't work. Sorry for the harsh reply, I was getting really inpatient with my device...
Now I can't flash CM13 because my firmware version is 1.64 and it needs to be 1.27. But there is no RUU for 1.64 so I'm completely out of ideas what to do next, jesus christ...

Stuck in bootloop after installing CM13...
I´ve managed to install CM13 & GAppss successfully via TWRP (it says so) but when I reboot the device to start CM, I am trapped in a bootloop
How do I get CM started? For now, I have re-installed the original ROM just by placing it as 2PQ9IMG.zip on the device to get a working device again, but I really want a CM13...
Any hints appreciated - thanks,
Rob

Jisifus said:
It turns out I was in the white background bootloader, not the download mode, that's why it didn't work. Sorry for the harsh reply, I was getting really inpatient with my device...
Now I can't flash CM13 because my firmware version is 1.64 and it needs to be 1.27. But there is no RUU for 1.64 so I'm completely out of ideas what to do next, jesus christ...
Click to expand...
Click to collapse
Haha, no problem... to downgrade I think you have to be s-off, however I'm not really sure on that one
Jisifus said:
It turns out I was in the white background bootloader, not the download mode, that's why it didn't work. Sorry for the harsh reply, I was getting really inpatient with my device...
Now I can't flash CM13 because my firmware version is 1.64 and it needs to be 1.27. But there is no RUU for 1.64 so I'm completely out of ideas what to do next, jesus christ...
Click to expand...
Click to collapse
Sent from my HTC One A9 using XDA-Developers mobile app

Same issue
RobOtter said:
Stuck in bootloop after installing CM13...
I´ve managed to install CM13 & GAppss successfully via TWRP (it says so) but when I reboot the device to start CM, I am trapped in a bootloop
How do I get CM started? For now, I have re-installed the original ROM just by placing it as 2PQ9IMG.zip on the device to get a working device again, but I really want a CM13...
Any hints appreciated - thanks,
Rob
Click to expand...
Click to collapse
I'm in the same situation. You solved?

You have to downgrade to 1.27.xxx.x.
To downgrade you have to say your phone your on 1.10.xxx.x.
enter these commands.
adb shell
echo -ne "1.10.xxx.x\x00\x00" | dd of=/dev/block/mmcblk0p28 bs=1 seek=2208
exit
adb reboot bootloader
then you can flash the signed 1.27 RUU.
after you downgraded you can flash the CM via twrp
worked for me on the .401. edition.

Thank you, but...
Thank you, I've try to downgrade but the operation fail, the message is 7 RU_CID_FAIL cid in android-info mismatched
dav375 said:
You have to downgrade to 1.27.xxx.x.
To downgrade you have to say your phone your on 1.10.xxx.x.
enter these commands.
adb shell
echo -ne "1.10.xxx.x\x00\x00" | dd of=/dev/block/mmcblk0p28 bs=1 seek=2208
exit
adb reboot bootloader
then you can flash the signed 1.27 RUU.
after you downgraded you can flash the CM via twrp
worked for me on the .401. edition.
Click to expand...
Click to collapse

frank531 said:
Thank you, I've try to downgrade but the operation fail, the message is 7 RU_CID_FAIL cid in android-info mismatched
Click to expand...
Click to collapse
seems like you used the wrong ruu for your phone. whats your cid?

I don't know....
Where can I find it? :angel:
dav375 said:
seems like you used the wrong ruu for your phone. whats your cid?
Click to expand...
Click to collapse

frank531 said:
I don't know....
Where can I find it? :angel:
Click to expand...
Click to collapse
fastboot getvar all
in download mode

Ok is the VODAP001 , now I download the right one.
Thank you so much. I hope it works...:good:
dav375 said:
fastboot getvar all
in download mode
Click to expand...
Click to collapse

Not sure if this applies to this thread, but I'm having a similar issue to the first one given. I unlocked the bootloader on my ATT A9, but when I flashed the recoery in download mode and reboot to recovery, it sends me to the stock recovery. Can anyone help?

I've try, but doesn't work...
Afther the adb shell and echo -ne........
this message:
o -ne "1.10.161.7\x00\x00" | dd of=/dev/block/mmcblk0p28 bs=1 seek=2208 <
dd: /dev/block/mmcblk0p28: Permission denied
1|[email protected]_hiaeuhl:/ $
next I've try to flash from the download mode and now the error message says: 19 RU_MAIN_VER_FAIL os-version in android-info missing or i
Maybe the problem is the recovery? Now I have the TWRP not the stock...
I search for a trend for go back to the stock but I haven't found it...
dav375 said:
fastboot getvar all
in download mode
Click to expand...
Click to collapse
frank531 said:
Ok is the VODAP001 , now I download the right one.
Thank you so much. I hope it works...:good:
Click to expand...
Click to collapse

Has it been solved. I seem to have the same issue??

I confirm that downgrading to 1.27 let's you Flash latest CM13.
Does anyone know, what firmware really does? Does it affect security in any way?

dav375 said:
You have to downgrade to 1.27.xxx.x.
To downgrade you have to say your phone your on 1.10.xxx.x.
enter these commands.
adb shell
echo -ne "1.10.xxx.x\x00\x00" | dd of=/dev/block/mmcblk0p28 bs=1 seek=2208
exit
adb reboot bootloader
then you can flash the signed 1.27 RUU.
after you downgraded you can flash the CM via twrp
worked for me on the .401. edition.
Click to expand...
Click to collapse
Is Working! Thanks! But You Forget To Must type "su" but is ok,thank you so much! i save my 25$ to S-off,Thank!