yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
I can't seem to load that page, is the ROM rooted? Maybe you should try attempting this on another ROM.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] Macguyver1980:
Yes this was the issue, even with some errors but I finally was able to be S-Off... not yes sure to have a good firmware for JellyBean but I'll give it a try... Thanks.
[AT&T, Rogers HTC One X, Telstra One XL] maxpower2078:
how to display the CID after the fact.

I am pretty sure I have the super CID set but can't remember exactly.

I was trying to view it in the bootloader but it does say

***** TAMPERED ****

***** UNLOCKED *****

at the top, I am guessing I do want to see that right?
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
You need to enter the following fastboot command to find out:

fastboot oem readcid

If it comes back as 11111111 you have SuperCID.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] ted77usa:
is the device should be on bootloader with fastboot mode first or just type

fastboot oem readcid

from cmd prompt?
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Your phone needs to be in bootloader/fastboot mode for fastboot commands to work.

And yes you enter that from the command prompt. Make sure you open the command prompt from within your fastboot folder on your pc (shift+ right click anywhere inside the folder, then select open command prompt here).

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] ted77usa:
Is that mean wait for the phone to boot up into android OS before entering those 3 command? (one command at a time) ......but i got error device not found everytime i enter each command .....any idea? and then closed cmd prompt window.....trying to start from the beginning keep saying error device not found ( USB Debugging is Checked )
[AT&T, Rogers HTC One X, Telstra One XL] maxpower2078:
I have gotten this far but I can't get into the fastboot mode,

I tried the adb devices command and it lists my phone but the fastboot reboot-bootloader just sits there and says, "waiting for devices" forever
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
That's because fastboot only works while you're in fastboot mode. You need to use adb commands while you're bored into the system:

adb reboot bootloader

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] maxpower2078:
I have gone through the steps in the OP but I still have S-ON.

One major thing I noticed is that after the flash zip step, the error message comes up pretty fast and I can't send the oem boot command fast enough before the phone automatically reboots. I continue on with the rest of the steps but still have S-ON

I have checked the soffbin3 file and it has the 744 permissions that CHMOD gave it too.

What else should I be looking at?
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
The phone shouldn't automatically reboot after flashing the zip. What error are you getting? Do you have SuperCID? Can you post the text from the command prompt here please?

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] zinter95:
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?
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
You've already asked this in your other thread, and it's against the rules to duplicate posts. I've already answered your question in the other thread.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] zinter95:
Sorry i didn't pay attention i followed all instructions, but i have another problem this time:

when i try to type the last commands it says: error: more than device and emulator

ow can i solve it?
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
I haven't seen that error before. Did you start again from the beginning?

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] davidalindsey:
THANK YOU!!!!!

This works.
[AT&T, Rogers HTC One X, Telstra One XL] rogersmithjr:
THANK YOU

i have tried this 300 hundred times, all different kinds of ways and the only thing that worked was what you said David,, thanks so much

it works everyone, TRY IT if you have problems with error 99 or 92 (something like that)

Code......

1) fastboot oem writecid 11111111

2) fastboot oem rebootRUU

3) fastboot oem boot

4)

adb push soffbin3 /data/local/tmp/

adb shell chmod 744 /data/local/tmp/soffbin3

adb shell su -c "/data/local/tmp/soffbin3"

5) adb reboot bootloader

rebooted and S-OFF is now there!!!!!

i think beaups need to adjust his instructions for some people, not sure why but just is..

The funny thing about all of this is I ran the command "fastboot oem readcid" and it came back with 1111111111 (all ones) so it was good but until I ran 1) fastboot oem writecid 11111111 -- that command which dont why i had to but like said, UNTIL I RAN IT. i could never be S-OFF

thanks for all the help on this, but i think we got it totally resolved, I only tried 307 times.. LOL
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
That's a bit all over the place. The first section contains multIple failed attempts at writing SuperCID, yet later in the script it shows your CID as SuperCID (you never needed to use the writecid command because you already have SuperCID).

On to the next part, between the "fastboot oem rebootRUU" command and the "fastboot oem boot" command there is a command missing (fastboot flash zip PJ8312000-OneX.zip). I understand that the quoted post by [MENTION=1869278]rogersmithjr[/MENTION] does not contain that command, but his tutorial is incomplete, the entire process is useless unless you flash that zip.

His little tutorial, while it may have worked for him, is incomplete. You should follow the instructions at the beginning of this thread exactly and not deviate at all. It's most likely an absolute fluke that the process happened to work after rogersmithjr gave the "fastboot oem writecid 11111111" command.

So, more importantly, when you follow the proper instructions exactly where does the process fail?

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] rogersmithjr:
So sorry

sorry [MENTION=4153349]timmaaa[/MENTION], my instructions are incomplete, my fault, i forgot to add that one line, typing wayyy fast, SORRY, nice catch!!! I did run the "fastboot flash zip PJ8312000-OneX.zip" command... I promise, i have NO reason to lie, I tried this so many times!!! only when i did the "fastboot oem writecid 11111111" command. only after, it all worked. I had no reason not to to try what [MENTION=3965781]davidalindsey[/MENTION] tried, because nothing else would work, plus that makes 2 people, me and [MENTION=3965781]davidalindsey[/MENTION] both to try fastboot oem writecid 11111111 and ONLY THEN, ours phones became S-OFF... the instructions at the beginning of THREAD, (Page 1) are correct, but for some reason( i think its has something to do with flashing roms and Kernals so much that every device has changed somewhat enough that the instructions on page 1 may not cover ALL devices due to flashing roms/kernals differently) just my 2 cents

***********please note************ picture is after i updated my firmware so just FYI when looking at my updated numbers on my Bootloader screen.... just saying

full commands code........

1) fastboot oem writecid 11111111

2) fastboot oem rebootRUU

3) fastboot flash zip PJ8312000-OneX.zip

4) fastboot oem boot

5)

adb push soffbin3 /data/local/tmp/

adb shell chmod 744 /data/local/tmp/soffbin3

adb shell su -c "/data/local/tmp/soffbin3"

6) adb reboot bootloader
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
To be honest, the first time I read your tutorial (when you posted it) I didn't even notice the missing line. It was only after delving into Aaron79's command prompt readout that I noticed the command missing and looked at the tutorial a little closer.

I wasn't saying that you're lying, I honestly just think it was a coincidence that the s-off process happened to work on the attempt following your giving of that command. But I could be wrong, wouldn't be the first time lol.

In any case, it certainly wouldn't hurt to try the writecid command for those who are having trouble getting s-off. More often than not it's something very simple messing up the process, like a misspelled command, usb debugging not enabled, or something of that nature.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] rogersmithjr:
OK, no problem, thats funny because the first 150 times i tried this, My USB debugging was not ON!! LOL, i'm a goof!! so you are very correct. could be just a fluke and happened to work, LOL

thanks buddy for support
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
I just saw your edited post and you're 100% correct when it comes to ROMs having a deciding factor in whether the process will work or not. I've gotten s-off on two devices personally, one running a 4.1 Sense ROM and the other running a 4.1 aosp ROM. I've just recently been helping anther user get s-off, and we tried everything under the sun (including 4.1 ROMs) but it wasn't until he flashed a 4.0 ROM that it finally worked. It just goes to show that it can be a very finicky process.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] arses:
Hi

is it possible to gain s off without supercid?

Is it dangerous if I try it?

Thanks for your answer
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
No it isn't possible, that's why it's stated you must have SuperCID in the OP. I don't think it's dangerous but I'm absolutely certain it won't work.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] arses:
Thanks timmaaa

as I told you my hboot is 2.10 with htc__J15 and Im upset.

I dont know why this hboot does not work with supercid method.

Anyway thanks for your response.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Ahh yeah, the Arabic model One XL. It's very possible that the 2.10 hboot has write protection enabled, therefore not allowing the edited file to be pushed back to give you SuperCID. You're in a bit of a tough situation, nobody really knows a great deal about your model, and there are so few that any real development specific to your model is pretty unlikely. Sorry man, it sucks.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] 696kris969:
I could be completely out here but I couldnt get s-off ages ago for the reason that supercid just wouldn't work.. I had to hexedit to get it working? Could be a possibility? I was hboot 1.14 on the UK version
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Well it's great to see it finally worked for you. It's hard to suggest a kernel to use because it's apparent that some kernels work for some users and others don't. The best solution for you now that you have s-off though is to upgrade to the 2.15 kernel. You'll find that in the first post of Turge's stock Sense 5 ROM thread in the Android Development section, along with instructions.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] jcta79:
After a few on reading and rereading and redoing my steps I finally got my phone to have s-off, unlocked and rooted thanks to all the people who put in work to help us newbs. Much appreciated.

:good:
[AT&T, Rogers HTC One X, Telstra One XL] style2burn:
you're the best!!
[AT&T, Rogers HTC One X, Telstra One XL] fotowca:
I've been digging through the forums for the last 2 days and not having much luck so I'm hoping someone here can help. My ultimate goal is to get back to stock. I have the ARUWizard and the shiped zip 1.74 RUU for my Rogers One X (Evita) but I can not flash it because my bootloader is to high, and I am currently S-ON. So i'm trying to follow the S-Off instructions here but running into the following error

(remote: 99 unkown fail)

My additional details are as follows

TAMPERED

UNLOCKED

EVITA PVT SHIP S-ON RL

HBOOT=1.11.000

CID=ROGER001

I am running the stable CyanogenMod 10.0, and have turned on USB debugging, and granted apps and ADB root.

Any assistance is greatly appreciated.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Did you read the requirements for the s-off process? You should probably take another look. Hint: CID.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] thedailyl3af:
+1

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] finallygreen:
I followed the instructions exactly and everything went as the first post said it would...except at the end, I wound up with:

*** TAMPERED ***

*** UNLOCKED ***

EVITA PVT SHIP S-ON RL

HBOOT-1.14.0002

What could have gone wrong for me to not get the S-OFF?
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Try again, and post the text from the command prompt here.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] finallygreen:
c:\android>adb reboot bootloader

c:\android>fastboot oem rebootRUU
... INFOStart Verify: 3
OKAY

c:\android>fastboot flash zip PJ8312000-OneX.Zip
sending 'zip' (36064 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
FAILED (remote: 92 supercid! please flush image again immediately)

c:\android>fastboot oem boot
< waiting for device >
... INFOBoot/Recovery signature checking...
INFOBoot/Recovery signature checking...
INFOsetup_tag addr=0x80400100 cmdline add=0xC02F9E3C
INFOTAG:Ramdisk OK
INFOTAG:skuid 0x2FD0C
INFOTAG:hero panel = 0x4940047
INFOTAG:engineerid = 0x5
INFOTAG: PS ID = 0x0
INFOTAG: Gyro ID = 0x2
INFODevice CID is super CID
INFOCID is super CID
INFOBackup CID is CWS__001
INFOsetting->cid::CWS__001
INFOserial number: HT29EW303266
INFOcommandline from head: console=ttyHSL0,115200,n8
INFOcommand line length =716
INFOactive commandline: poweron_status=1 reset_status=0 board_el
INFOite.disable_uart3=0 diag.enabled=0 board_elite.debug_uart=0
INFOuserdata_sel=0 androidboot.emmc=true androidboot.pagesize=20
INFO48 skuid=0 ddt=20 ats=0 androidboot.lb=1 td.td=1 td.sf=1 td
INFO.ofs=328 td.prd=1 td.dly=0 td.tmo=300 imc_online_log=0 andr
INFOoidboot.efuse_info=NFSL androidboot.baseband=0.19as.32.09.11
INFO_2 androidboot.cid=CWS__001 androidboot.devicerev=3 androidb
INFOoot.batt_poweron=good_battery androidboot.carrier=ATT androi
INFOdboot.mid=PJ8310000
INFOaARM_Partion[0].name=misc
INFOaARM_Partion[1].name=recovery
INFOaARM_Partion[2].name=boot
INFOaARM_Partion[3].name=system
INFOaARM_Partion[4].name=local
INFOaARM_Partion[5].name=cache
INFOaARM_Partion[6].name=userdata
INFOaARM_Partion[7].name=devlog
INFOaARM_Partion[8].name=pdata
INFOaARM_Partion[9].name=fat
INFOaARM_Partion[A].name=extra
INFOaARM_Partion[B].name=radio
INFOaARM_Partion[C].name=adsp
INFOaARM_Partion[D].name=dsps
INFOaARM_Partion[E].name=wcnss
INFOaARM_Partion[F].name=radio_config
INFOaARM_Partion[10].name=modem_st1
INFOaARM_Partion[11].name=modem_st2
INFOpartition number=18
INFOValid partition num=18
INFOTZ_HTC_SVC_SET_DDR_MPU ret = 0
INFOsmem 90005000 (phy 90005000): TZ_HTC_SVC_UPDATE_SMEM ret = 0
INFOTZ_HTC_SVC_LOG_OPERATOR ret = 0
INFOTZ_HTC_SVC_ENC ret = 0
INFOTZ_HTC_SVC_DISABLE ret = 474079232 (0x1C41E000)
INFOjump_to_kernel: machine_id(3766), tags_addr(0x80400100), ker
INFOnel_addr(0x80408000)
INFO-------------------hboot boot time:9454 msec
FAILED (status read failed (Too many links))

c:\android>adb push soffbin3 /data/local/tmp/
356 KB/s (4751 bytes in 0.013s)

c:\android>adb shell chmod 744 /data/local/tmp/soffbin3

c:\android>adb shell su -c "/data/local/tmp/soffbin3"

c:\android>adb reboot bootloader

That's from my first try. Second try looks the same, except I get different error(s) after flashing the zip. Here's those:

c:\android>fastboot flash zip PJ8312000-OneX.zip
sending 'zip' (36064 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOzip header checking...
INFOzip info parsing...
FAILED (remote: 99 unknown fail)
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
The first attempt looks ok. The error 99 on the other attempt is a problem, but when you get that just force a reboot to bootloader by holding volume down and power and start again and you should get error 92 again. Some folks have reported it taking a few attempts for this to work. What ROM are you on while attempting it?

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] finallygreen:
Stock. Per your advice, I was going to achieve the S-OFF and then go ROM hunting.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Ok. You could try flashing a ROM to get s-off, sometimes a ROM change does a world of good. There are several ROMs you could flash without really needing to alter anything first.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] thedailyl3af:
Almost always had success with viperxl 3.2.8 and the people I've told. I'm pretty sure clean rom 4.1.1 would work as well.

edit: I ment to do a double quote but I forgot lol

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] AlwaysDroid:
Anybody else having issues with the zip file being invalid? Or is it just me
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Is the zip in your fastboot folder? Are you sure you're entering the command correctly?

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] fotowca:
Thanks for the reply. I'm looking into that now.
[AT&T, Rogers HTC One X, Telstra One XL] finallygreen:
Well, this is getting a bit scary because I've followed every instruction to the letter and now I think I might have a brick :(

I went ahead and tried to install a ROM like you told me to (wiped data and installed via TWRP), and now my phone's just sitting at the white HTC screen.

What do I do now??
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
You don't have a brick, your phone is powering on. A brick is when the phone won't power on and you get zero response from it. Which ROM did you flash? Did you flash the boot.img via fastboot afterwards? You're s-on do you need to do that when flashing ROMs/kernels.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] finallygreen:
OK, I got back up and running, and I restored the backup I made yesterday when we were unlocking in the first place.

I'm searching high and low and I can't find the correct procedure for flashing a ROM while I'm S-On. I have the zip and I get that I need to extract the img from the zip and flash it from the PC, but I can't find the proper order of steps for this anywhere. Could you point me in the right direction for that?

---------- Post added at 08:53 PM ---------- Previous post was at 08:30 PM ----------

Scratch that...I figured that part out and seem to have successfully installed my first custom ROM. Once I've verified that, I'll go back and see if I finally have or can get S-Off.

---------- Post added at 09:40 PM ---------- Previous post was at 08:53 PM ----------

Ugh..well, at least I'm not bricked....installed the latest CleanROM and all seems fine, but...I still can NOT get the dang S-Off, despite following every direction to the letter. Now for whatever reason, I'm getting "error: device not found" whenever I try this process. Why is this happening?
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
You should try an earlier ROM, Android 4.0 or 4.1 should do.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] Denzkay:
Is the procedure to get S-OFF any different for CM10.2 23/10/2013?
[AT&T, Rogers HTC One X, Telstra One XL] thedailyl3af:
Try restarting your computer. The cmd and adb like to keep the last attempts ending results lol. Who knows might even help you get s off lol

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
The only difference is that as well as enabling usb debugging in developer options you need to grant root access to adb in developer options too.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] Denzkay:
alright.. How do i do those two things? Do I tap the 'build number' option in 'about phone' to get developer options?
[AT&T, Rogers HTC One X, Telstra One XL] sbacham:
dont worry

guys im gonna show you some tricks for who are getting troubles in s off.(these are my experiences)

1.install htc driver(no need sync only drivers)

2.switch off phone and on with power+vol down for bootloader(remember uncheck fast boot in settings+power)(dont do adb reboot bootloader for going to bootloader i got troubles thats why m saying do it manually )

if u even dont get s off then try this

3.change usb port back to front or other ports of pc/lappy

4.be sure your phone rooted then do factory reset in settings not in recovery.(its also imp cuz ive tried 30 times without success then i did factory reset and tried voila succeed) then enable usb debug and try all above once again.

back up your data befor doing facrery reset.

try this i hope you will succeed by trying above(ofcourse they are not in particular order).

keep posting your experiences cuz that help others alot.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
You probably should have mentioned that doing a factory reset in bootloader will corrupt the sd card and will require it be formatted in order to work again. That's pretty important if you ask me because someone not knowing that would lose all of their data upon following your instructions. It isn't even necessary, it might have worked for you (possibly even a complete coincidence) but it certainly isn't a must for achieving s-off. Also, saying it will definitely work is a bit extreme, there can be many contributing factors to the s-off process not working, many of which aren't mentioned in your post.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] sbacham:
thanks ,edited.
[AT&T, Rogers HTC One X, Telstra One XL] Zehmistah:
Whenever I type a command with fastboot, it stays at (waiting for device) forever. Ugh, any ideas? Phones running ViperXL 4.2 and when I go into fastboot it says "One of the usb devices attached to this computer malfunction and windows does not recognize it".

EDIT: FIXED THE PROBLEM, PLUGGED IT INTO ANOTHER PORT. NEW PROBLEM!! How do I get SuperCID on Rogers HOX? I tried the link provided and still have the Original CID
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Try the hex edit.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] finallygreen:
Thoroughly confused....hoping someone can help me.

So I've got through this process over and over again. Sometimes I get the correct (92) error, and sometimes I get the incorrect (99) error. Even when I do get the correct error, when I get to the final step, I'm met with a Segmentation fault.

I've searched this thread extensively....over and over again it is said that the fix for these problems is a stock JellyBean kernel. Trouble is, the whole reason I'm trying to GET S-Off is because the first ROM I flashed to after rooting (latest CleanROM) has signal dropouts and random reboots that are said to only be fixable by flashing to a different kernel....but that I can't flash a kernel until I'm S-OFF. Soooo....what exactly can I do to get past this problem?
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
What ROM are you attempting the s-off process on? Cleanrom Sense 5? If so, you need to downgrade to an Android 4.0 or 4.1 ROM for it to work. If you get error 99 you need to force a reboot to bootloader by holding volume down and power together, then start again (without the adb reboot bootloader command because you're already in bootloader).

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] exad:
And for the record, you can flash a kernel without s-off.. you just need to fastboot flash the boot.img extracted from the zip right before or after flashing the zip in recovery.