Database Info

[GUIDE] Upgrade to ATT 2.20 OTA Safely

Ok this is a simple guide more for newer users as older members here already will know this information probably.
As people may have heard there is a new OTA for ATT. I and gunnyman bit the bullet to see if the old way of doing things ( upgrading, etc as long as you already had unlock token ) still worked with this new base and OTA.
Im proud to say yes. thanks to gunnyman and zounduser for help and hopes that I made it though un harmed lol
Disclaimer As usual this works as I am proof. However I cant be held liable if you mess up your phone! This only works for those who are already unlocked rooted etc.
Here are the steps to getting the update safely.
Prerequisites:
1. You must already be unlocked with supercid and have your Unlock_code.bin file still on your pc. ( there is a thread for this )
2. you must be rooted
3. You must have an understanding of adb and how it works (threads all over xda)
4. Have an RUU available I used 1.85
5. copy of custom recovery twrp 2.1.8.1 is what i used
6. copy of superuser in a zip available in attachments at bottom.
7. Disable HTC SYNC from running!
Here we go:
1. Reboot your phone into fastboot
2. Open a command promp and point to your adb directory. Type the following command: fastboot oem lock
This will lock your bootloader allowing you to RUU
3. Open the 1.85 RUU file.
4. Go through the RUU process.
5. Once you have finished RUUing boot the phone up if it isint booted already
6. Do a minimal setup just skip through the initial set up screens.
7. Check for att software update.
8. A box will appear saying a security update is available. enable your wifi and download it.
9. Allow the update to install
10. After the update finishes ( takes roughly 8-10 mins) some faster some longer. Boot the phone if it isin't booted ( should be ) disable fastboot under system settings power. Enable USB debugging under system developer options.
11. Attach your phone to your pc if it isint already.
12. Open a command promp and point to your adb directory.
type: adb reboot bootloader. If you get an error from adb type adb reboot-bootloader
13. Locate your unlocktoken Unlock_code.bin and place it in the same folder as your adb, fastboot, etc if its not already there from the last time you unlocked.
14. Flash your unlock token. Open a command prompt and type:
fastboot flash unlocktoken Unlock_code.bin
15. Once the token flashes before selecting yes to unlock, unplug your phone from pc. After you unplug it go ahead and select yes.
16. Once phone boots up do a minimal set up as before. Plug your phone back in to pc. Open command prompt and type: to verify unlock
adb reboot bootloader if you get an error from adb type adb reboot-bootloader
you should now see UNLOCKED at the top. If not repeat number 14 until it sticks can take a few tries.
17. If your screen says unlocked, flash your custom recovery. Locate your recovery flash it by typing in command promp: fastboot flash recovery recoveryname.img ( twrp2.1.8.1.img is mine replace with whatever yours is)
18. Once you have the recovery flashed reboot the phone.
19. Plug the phone in and select disk drive. Copy the superuser zip over to your sd card.
20. After that select charge only, open a command prompt and type:
adb reboot recovery
21. Once in recovery locate the superuser zip and flash it.
22. Reboot enjoy you should now be on OTA 2.20 Unlocked, Rooted, etc
O one thing I forgot Please hit thanks if this helped you!
Issues:
1. If you update you will get a newer hboot, you may not be able to use other older ruu's such as 1.85, etc. Recommend immediately making a backup once rooted, unlocked, etc.
2. Updating results in boot.IMG from custom roms not being flashed again. Have to flash the boot.IMG of custom Rom in fastboot as before.
3. Radio.img will not flash on new hboot either must be done in fastboot same as boot.img.

Wanna dd a radio img for me?
Sent from my HTC One X using xda app-developers app

First.. lol thanks man, nice guide!!! Site this will help our nooblets
Sent from my HTC One XL using xda app-developers app

Yeah, we want radio. Good guide too.
Sent from my HTC One X using xda premium

Thought gunnyman switched to the dark side and got a galaxy lol
Sent from my HTC One X using xda app-developers app

InflatedTitan said:
Thought gunnyman switched to the dark side and got a galaxy lol
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
He came Back!

if you have a higher hboot. u cant RUU with a lower hboot correct?

daddioj said:
if you have a higher hboot. u cant RUU with a lower hboot correct?
Click to expand...
Click to collapse
Hmm dunno that one. I was on 1.85 CleanROM 4.5 asia2.23 base when I went to new OTA. I thought as long as one had super cid RUU would work either way up or down software.

thanks for the tutorial.

john9 said:
thanks for the tutorial.
Click to expand...
Click to collapse
Welcome

eraste said:
Hmm dunno that one. I was on 1.85 CleanROM 4.5 asia2.23 base when I went to new OTA. I thought as long as one had super cid RUU would work either way up or down software.
Click to expand...
Click to collapse
well yea if you a custom rom. base dont matter b/c hboot does not get updated. i went to offical asia RUU and hboot got updated i am pretty sure u cant go backwards without s-off i could be wrong though

Any idea if root exploit works after update? People are saying it won't work on 1.85 now bc of update on server.
Sent from my HTC One X using xda app-developers app

drummaniac83 said:
Any idea if root exploit works after update? People are saying it won't work on 1.85 now bc of update on server.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
its right in the OP. as long as YOU HAVE the unlock code file from htc dev already you can update then unlock and root with the file posted. but if you didnt unlock already DO NOT UPDATE i dont think anyone knows yet
or are u talking about the original 1.85 exploit?

daddioj said:
or are u talking about the original 1.85 exploit?
Click to expand...
Click to collapse
Orignal exploit. I'm on 1.85 non root. Was going to root this weekend since CR 4.5 was final. DOH!
Sent from my HTC One X using xda app-developers app

drummaniac83 said:
Any idea if root exploit works after update? People are saying it won't work on 1.85 now bc of update on server.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
I do not know that one as it was designed for 1.85 I would say no. People are working on root for the ota as we speak

eraste said:
I do not know that one as it was designed for 1.85 I would say no. People are working on root for the ota as we speak
Click to expand...
Click to collapse
Good to know. I got my One x last month from att with 1.85 loaded. I think I'm fine without the update. I'll stick to custom ROMs lol. And your awesome boot animations :thumbup:
Sent from my HTC One X

Updating now.
I prefer to run sense roms based on ATT, just seem to work a bit better imo.
Besides, with what i know of the 4.0.4 (clean rom) it is much smoother and all around much better than the 4.0.3 we got originally, may not need to run a custom rom to get the results i require (though i probably still will haha).

so if im unlocked, i can update and worry about rooting and unlocking tomorrow since i already have the unlock.bin file ?
Sent from my HTC One X using xda app-developers app

Psst; the command to rebooting to bootloader is 'adb reboot-bootloader'
...that hyphen is pretty important.

JSLEnterprises said:
Psst; the command to rebooting to bootloader is 'adb reboot-bootloader'
...that hyphen is pretty important.
Click to expand...
Click to collapse
hmm adb setup on my pc doesnt require that particular hyphen. I never have to use " either thought that was a little wierd. It works tho. I do need that hypen when doing kill-server start-server tho. Those are the only two commands that seem to not work without it for me.
thanks ill update lines.

Possible to change "modelid" of HTC One S?

Hi guys! I have T-Mobile US version of One S and have changed to SuperCID and have the latest rom from Euro RUU 2.31. The model of my phone is different form european, so after checking I found the model to be PJ40110. I have first tried to make CID as HTC__001, but it wouldn't install RUU saying that model id doesn't match. Then I found txt file and saw that it needs a different model id, so this is when SuperCID came into play. Is there a way to change 'modelid' of the phone?
Thanks in advance!

In the build.prop
T-MobileUS HTC One S

fastboot write mid?
Sent from pixels to more pixels

usaff22 said:
fastboot write mid?
Sent from pixels to more pixels
Click to expand...
Click to collapse
I have tried the following command: fastboot oem writemid PJ4010000, the is the midel id I need to change to, but I get "Info[ERR] Command Error!!!" I know that this command is correct and looks like I would have to wait for S-OFF to make it work.

Charkatak said:
I have tried the following command: fastboot oem writemid PJ4010000, the is the midel id I need to change to, but I get "Info[ERR] Command Error!!!" I know that this command is correct and looks like I would have to wait for S-OFF to make it work.
Click to expand...
Click to collapse
Yes, I think it is only possible with the Engineering HBOOT, with S-OFF.
I don't think it is possible with HTCDev. You'll have to wait until we get S-OFF.
Sent from pixels to more pixels

usaff22 said:
Yes, I think it is only possible with the Engineering HBOOT, with S-OFF.
I don't think it is possible with HTCDev. You'll have to wait until we get S-OFF.
Sent from pixels to more pixels
Click to expand...
Click to collapse
- Now we have SOFF. What I did was I debranded the TMOUS HOS to WWE EU and flashed ICS rom.zip from RUU. All was fine till now and I have SOFF, relocked BL etc.
- Moreover, I do get notification for JB OTA and it also completes the download. However, it doesn't install as my MID is PJ4011000. EU RUU expects it to be PJ4010000.
- On searching, I found this thread. I tried issuing: sudo ./fastboot oem writemid PJ4010000 as well as sudo ./fastboot oem modelid PJ4010000. However, it still gives error:
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.012s]
finished. total time: 0.012s
- I have Ubuntu 12.04 on 64-bit 8 core machine (not sure if this is of any help but still thought of mentioning) which I am using for the playing with my HOS.
I guess now I need to find out how to change MID with SOFF.
Edit: I checked my build.prop and it has MID PJ4010000. So this MID is also stored somewhere apart from build.prop. Damn it !!

chota_shivaji said:
- Now we have SOFF. What I did was I debranded the TMOUS HOS to WWE EU and flashed ICS rom.zip from RUU. All was fine till now and I have SOFF, relocked BL etc.
- Moreover, I do get notification for JB OTA and it also completes the download. However, it doesn't install as my MID is PJ4011000. EU RUU expects it to be PJ4010000.
- On searching, I found this thread. I tried issuing: sudo ./fastboot oem writemid PJ4010000 as well as sudo ./fastboot oem modelid PJ4010000. However, it still gives error:
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.012s]
finished. total time: 0.012s
- I have Ubuntu 12.04 on 64-bit 8 core machine (not sure if this is of any help but still thought of mentioning) which I am using for the playing with my HOS.
I guess now I need to find out how to change MID with SOFF.
Click to expand...
Click to collapse
You need an Engineering HBOOT which supports those commands

usaff22 said:
You need an Engineering HBOOT which supports those commands
Click to expand...
Click to collapse
Thanks for the update.
I guess I am now *really* stuck on WWE ICS (for stock). Of course, I can flash any ROMs I want since I am SOFF, so not a big deal. I must say WWE ICS ROM is better than TMOUS with their bloat (which is anyway not useful to me at all since I am out of USA now).

chota_shivaji said:
Thanks for the update.
I guess I am now *really* stuck on WWE ICS (for stock). Of course, I can flash any ROMs I want since I am SOFF, so not a big deal. I must say WWE ICS ROM is better than TMOUS with their bloat (which is anyway not useful to me at all since I am out of USA now).
Click to expand...
Click to collapse
I'd bet money you could dd the correct partition from the phone change it with a hex editor and dd it back to the phone. I've done it with a handful of things and never had a problem.

I decrypted the zip and changed it to the US model. Run the RUU and before letting it install it to your phone, open up the temp directory and replace my zip with the 'rom.zip' in the temp folder. I will upload mine after I am home
Sent from my HTC One S using xda app-developers app

dc211 said:
I'd bet money you could dd the correct partition from the phone change it with a hex editor and dd it back to the phone. I've done it with a handful of things and never had a problem.
Click to expand...
Click to collapse
Hey thanks for the update. I agree with you on this point. Do you know what partition holds the MID in HOS?
Sent from my HTC One S using xda app-developers app
---------- Post added at 07:19 AM ---------- Previous post was at 07:16 AM ----------
leald said:
I decrypted the zip and changed it to the US model. Run the RUU and before letting it install it to your phone, open up the temp directory and replace my zip with the 'rom.zip' in the temp folder. I will upload mine after I am home
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Fantastic !! Would you mind sharing how to decrypt the zip? In any case awaiting for your rom.zip which has TMOUS MID in android_info.txt extracted EU JB RUU and decrypted .
Sent from my HTC One S using xda app-developers app

chota_shivaji said:
Hey thanks for the update. I agree with you on this point. Do you know what partition holds the MID in HOS?
Sent from my HTC One S using xda app-developers app
---------- Post added at 07:19 AM ---------- Previous post was at 07:16 AM ----------
Fantastic !! Would you mind sharing how to decrypt the zip? In any case awaiting for your rom.zip which has TMOUS MID in android_info.txt extracted EU JB RUU and decrypted .
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Ill try and upload it tonight but it might not be up until tomorrow morning because of its side. And actually you will have to "fastboot oem writecid HTC__001" asi already repackaged the zip before thinking I would have to add a tmobile cid, sorry
Sent from my HTC One S using xda app-developers app

leald said:
Ill try and upload it tonight but it might not be up until tomorrow morning because of its side. And actually you will have to "fastboot oem writecid HTC__001" asi already repackaged the zip before thinking I would have to add a tmobile cid, sorry
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
- I think you misunderstood me.
- My HOS is de-branded and has CID = HTC__001 from TMOUS & SOFF. I am on 2.31 EU stock ICS. The only hurdle now for me to use JB OTA/RUU/rom.zip is MID.
- So, what I am looking for is: rom.zip from JB EU RUU with android_info.txt changed for TMOUS MID and decrypted. Once I get that, I can use via RUU mode of fastboot.

chota_shivaji said:
- I think you misunderstood me.
- My HOS is de-branded and has CID = HTC__001 from TMOUS & SOFF. I am on 2.31 EU stock ICS. The only hurdle now for me to use JB OTA/RUU/rom.zip is MID.
- So, what I am looking for is: rom.zip from JB EU RUU with android_info.txt changed for EU MID and decrypted. Once I get that, I can use via RUU mode of fastboot.
Click to expand...
Click to collapse
- I found this thread http://forum.xda-developers.com/showthread.php?t=2084470 which has a tool to decrypt the JB RUU. It uses the libcrypt on Linux host machine to decrypt the rom.zip. It looks like for many phones JB RUU is encrypted.
- The tool mentions that it supports HTC One S (ville).
- I tried this tool to decrypt the rom.zip from JB EU RUU. It runs fine and I am able to get the decrypted rom.zip with MID = TMOUS in android_info.txt. However, I have not flashed it yet as I am not brave enough to face a brick (even though my signature mentions JB, I am still on ICS).
Can someone try this tool and flash as well? It needs Linux machine to compile and generate the binary to be useful.
Please note: I am not responsible if you brick your HOS due to this. You have been warned, do not attempt if you don't understand what you are doing.

Charkatak said:
Hi guys! I have T-Mobile US version of One S and have changed to SuperCID and have the latest rom from Euro RUU 2.31. The model of my phone is different form european, so after checking I found the model to be PJ40110. I have first tried to make CID as HTC__001, but it wouldn't install RUU saying that model id doesn't match. Then I found txt file and saw that it needs a different model id, so this is when SuperCID came into play. Is there a way to change 'modelid' of the phone?
Thanks in advance!
Click to expand...
Click to collapse
I think you should put the breaks on your project. Why exactly are you trying to change your MID anyways. If it's to get a RUU to run I'd suggest that you not go forward with your plan. There is no real reason to run an RUU if you have S-off other then to "start over" on a clean install of everything.
You can flash any: rom, firmware, radio, and hboot you choose so why change the model ID to run a RUU. Which is something I've NEVER seen anyone do in this forum to run a RUU. What's the full name of the RUU you want to run?
It looks like you're doing all this just to get to the official Jelly Bean release is that your goal? If so why not just flash it without using a RUU?

If so why not just flash it without using a RUU?[/QUOTE]
because the JB zip won't flash in a Tmous device because of different model id..

cyriantherockstar said:
because the JB zip won't flash in a Tmous device because of different model id..
Click to expand...
Click to collapse
Why not just install the rom that someone made compatible with TWRP then flash the firmware separately?

you can hex mod the mmcblk0p6 partition. it has a string pj0011000 in there somewhere as well as a spaced out string p j 0 0 1 1 0 0 0. if you edit those out, you should be fine to flash the ruu. first you need to supercid and s off though.

chota_shivaji said:
- I found this thread http://forum.xda-developers.com/showthread.php?t=2084470 which has a tool to decrypt the JB RUU. It uses the libcrypt on Linux host machine to decrypt the rom.zip. It looks like for many phones JB RUU is encrypted.
- The tool mentions that it supports HTC One S (ville).
- I tried this tool to decrypt the rom.zip from JB EU RUU. It runs fine and I am able to get the decrypted rom.zip with MID = TMOUS in android_info.txt. However, I have not flashed it yet as I am not brave enough to face a brick (even though my signature mentions JB, I am still on ICS).
Can someone try this tool and flash as well? It needs Linux machine to compile and generate the binary to be useful.
Please note: I am not responsible if you brick your HOS due to this. You have been warned, do not attempt if you don't understand what you are doing.
Click to expand...
Click to collapse
correct me if i am wrong here, but why dont you just take the rom.zip from the ruu, decrypt it and change the androidinfo.txt and change the model id to say the one you need. then rezip it with winrar or 7zip and feed it to the hboot... you are s-off so it shouldnt ask any questions regarding the signiture of the zip file, but i am not sure about the compression.

untrueparadox said:
you can hex mod the mmcblk0p6 partition. it has a string pj0011000 in there somewhere as well as a spaced out string p j 0 0 1 1 0 0 0. if you edit those out, you should be fine to flash the ruu. first you need to supercid and s off though.
Click to expand...
Click to collapse
Has anyone had success doing this?

[Q] Can't update CM 10.1 OTA

I'm having issues updating to the latest version of CM 10.1. I currently run CM10.1-2013-0509-UNOFFICIAL-evita (4.2.2, May 9 2013) and when I try to update OTA I get the following error:
assert failed: getprop("ro.bootloader") == "2.14.000"
E: Error in sdcard/cmupdater/cm-10.1-2013030725-NIGHTLY-evita.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse
I've been trying to research the solution on my own and I'm confused. I think my hboot is out of date but in order to update it I need to have s-off and Super CID enabled (or change my CID to 111111 or 00000, can't remember which). Anyways, can anyone give me some guidance on how to get the latest CM versions installed?

Yeah you have to s-off and then run the 3.18 ruu. No way around it.
Sent from my evita

Fastboot OEM readcid will give you your current cid. If your phone is from at&t you should have it already. What hboot are you on right now?
Sent from my One X using xda app-developers app

RollTribe said:
Yeah you have to s-off and then run the 3.18 ruu. No way around it.
Sent from my evita
Click to expand...
Click to collapse
Can you point me in the direction of some guides? I've found different posts and guides and it's all confusing as I'm not sure which order to follow or if they all apply to my phone.
exad said:
Fastboot OEM readcid will give you your current cid. If your phone is from at&t you should have it already. What hboot are you on right now?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
My phone is from Rogers, I'm on hboot 1.11
I found a guide for fastboot oem readcid which reads:
Connect your phone with USB Debugging enabled
Open up an adb shell (if you don't know how to do this, Google it!)
Reboot into fastboot mode in the Bootloader.
Type: fastboot oem writecid 11111111
Type: adb reboot-bootloader
Type: fastboot oem readcid
If it says 11111111 then you have SuperCID
You can reboot as normal
Click to expand...
Click to collapse
When following the steps (only typing fastboot oem readcid, not the other lines) my cid is stated as: ROGER001
I do have S-ON enabled if that matters. I know I have to disable it but I'm not sure if I have to do that before or after I rewrite my CID, against some more confusion on my part and I've read doing it wrong can brick my device.

http://forum.xda-developers.com/showthread.php?t=2349919
Sent from my HTC One X using xda app-developers app

exad said:
http://forum.xda-developers.com/showthread.php?t=2349919
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
So I followed the steps and was able to enable S-OFF and achieve CID 11111111. I tried to update the hboot following the instructions here: http://forum.xda-developers.com/showthread.php?t=2156686
I tried installing the first version of the Hboot and when I rebooted the screen hung on the CM 10.1 boot logo. I tried to enter recovery through fastboot but a red exclamation mark screen would load. I reinstalled recovery through fastboot and then tried to do a factory reset through recovery and fastboot and my device is now stuck on the HTC logo when booting. I've tried reinstalling different versions of hboot (which I downloaded from those instructions) and nothing happens. Please advise, as of now my phone won't boot.
Edit:
I think what caused this problem was flashing this file: /ALL FILES FROM OTA 3.17 T-MO germain hboot 2.14 (incl recovery and other firmware files, be careful with that).
I'm pretty sure I did the firmware and recovery files as it took 60s to flash and I remember seeing a lot of RADIO files being written. My cell phone is a Rogers cell phone is there a stock version I can re-flash to make it work?
Edit II:
I was able to mount my phone via recovery and install cm 10.1. However, the phone isn't responding to any touch.

Which version of CM10.1 did you install? It sounds like it's an older one because they're not compatible with the newer touchscreen firmware. Download the latest nightly and flash that and you should be ok.
Sent from my Evita

Okay I finally got her working. I followed instructions here http://forum.xda-developers.com/showthread.php?t=2159863 to re-install the touch panel firmware, installed the corrected hboot update and upgraded to the latest cm 10.1. Cheers to everyone who contributed and helped me out!

For anyone who may find this thread in the future, the best thing to do would have been run an older RUU because there is no 3.17 RUU i believe and then either install the ota through stock recovery or Download the OTA through android (check for updates)

exad said:
For anyone who may find this thread in the future, the best thing to do would have been run an older RUU because there is no 3.17 RUU i believe and then either install the ota through stock recovery or Download the OTA through android (check for updates)
Click to expand...
Click to collapse
I was wondering if you could help me as I am getting the same error as the original poster and I can't update cyanogenmod. The only difference I think is that I am on the AT&T htc one x. I'm just looking for some direction so I don't end up bricking my phone. Thanks!

Are you s-off?
Sent from my HTC One X using xda app-developers app

exad said:
Are you s-off?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Nope! I have super cid never bothered with s-off. Is it required? I'm also on hboot 1.14...

You can't be serious.
Did you not read the rest of this thread? Or the clear install instructions on the cm10.1 thread? Must s-off and RUU to 3.18. Ugh.
Sent from my Evita

Can't S-OFF with Hboot 2.15...

Hi everyone,
I need your help because I can't S-OFF my HTC One S (s4) : Latest official ROM 3.16.401 (if I remember well), Bootloader unlocked, SuperCID and Hboot 2.15
I can't S-OFF with Facepalm, cause I have Hboot 2.15 right ?
And I can't either with Moonshine cause only compatible with :
3.14.531.11 (T-MOB)
3.16.666.9 (BM)
3.16.111.10 (TMO_DE)
3.16.661.4 (Telus)
So if I am SupedCID i must be able to flash any firmware above mine right ? Or do I need to match the CID anyway ?
In fact I didn't succeed in, at first with bootloader unlocked it said error in parsing android-info file (tried with 2 RUUs) then I tried with bootloader relocked and then it says "remote 12 : signature verify fail"
So...I am a little bit lost, what should I do ? Any idea ?
Thanks.

A bit off topic but still kinda related.
So i got my phone used, and when i got it, it was already bootloader unlocked and s-off. Now my question is, a lot of people are having trouble getting s-off on 2.15 hBoot, but that's what i have, along with TMOB010 CID.
I want to know how this device got s-off, and the thing is, in bootloader it doesn't even have **tampered** showing on there.
Anyone have any idea? I just want to know so that if i mess up the phone I'd know how to get it back to its previous state.
Sent from my One S using XDA Premium 4 mobile app

Noplait said:
Hi everyone,
I need your help because I can't S-OFF my HTC One S (s4) : Latest official ROM 3.16.401 (if I remember well), Bootloader unlocked, SuperCID and Hboot 2.15
I can't S-OFF with Facepalm, cause I have Hboot 2.15 right ?
And I can't either with Moonshine cause only compatible with :
3.14.531.11 (T-MOB)
3.16.666.9 (BM)
3.16.111.10 (TMO_DE)
3.16.661.4 (Telus)
So if I am SupedCID i must be able to flash any firmware above mine right ? Or do I need to match the CID anyway ?
In fact I didn't succeed in, at first with bootloader unlocked it said error in parsing android-info file (tried with 2 RUUs) then I tried with bootloader relocked and then it says "remote 12 : signature verify fail"
So...I am a little bit lost, what should I do ? Any idea ?
Thanks.
Click to expand...
Click to collapse
If you have SuperCID then yes you can flash RUU above yours. I did, but for me moonshine still didn't work but occasionally Facepalm did.
---------- Post added at 12:25 AM ---------- Previous post was at 12:20 AM ----------
JiroPrinz8 said:
A bit off topic but still kinda related.
So i got my phone used, and when i got it, it was already bootloader unlocked and s-off. Now my question is, a lot of people are having trouble getting s-off on 2.15 hBoot, but that's what i have, along with TMOB010 CID.
I want to know how this device got s-off, and the thing is, in bootloader it doesn't even have **tampered** showing on there.
Anyone have any idea? I just want to know so that if i mess up the phone I'd know how to get it back to its previous state.
Sent from my One S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Tampered flag can be removed by tool revone.
This time I know just 2 methods how to do S-Off, moonshine and facepalm.

Can't think of one!
------> Noplait
Managed to S-Off mine with the following specs...
Baseband version : 1.12.50.05.05_10.28.50.08L
Software number : 3.16.61.10
Android version: 4.1.1
Hboot: 2.15.0000
Followed the instructions Exactly.
1. Bootloader unlock via HTCDev.
2. Steps 1,2&3 as found here
http://forum.xda-developers.com/showthread.php?t=1583427
3. SuperCID as found here
http://forum.xda-developers.com/showthread.php?p=26516911#post26516911
4. Bootloader unlock via HTCDev
(Out of curiosity did you go back to HTCDev and go through the unlock process again? As this is what I did (as per instructions)?).
5. Facepalm S-Off as found here
http://forum.xda-developers.com/showthread.php?t=2155135
(Note: for instructions 5, I dragged the appropriate zip into the command prompt line from where I had downloaded zip file,
and for instruction 7 dragged the appropriate file from the folder into the first command prompt line only - adb push <locaction of this file only: soffbin3> /data/local/tmp/
Then copied and paste the remaining two commands one at a time, remember to press enter after each of the 3 commands)
Hope that helps.

Step 3 (changig CID) seems to cause trouble to users with base 3.16.401.8, including me.
It looks like mmcblk0p4 is write protected here, so the changing of the CID just does not work.
I also didn't find a working way around yet...

Hello! I need some help here.Probably not the right place,sorry about that!
My problem is that I'm s-on,and it's seems that I can't do the supercid witch is the first step for Facepalm process.
I red a lot about this topic, everything what I have found.
It appears that I got the hboot 2.15 version with Jb ota Update ,because of this the mmcblk0p4 file is write protected... so the cid overwrite is undone.
Tried on ViperOneS 1.2.1 - 2.2.0,on Tricktroid 7-9.1 and on Jb Stock also.The adb ,the termal emulaton on phone ,hex editing works well.
This is my hboot:
*** TEMPERED ***
*** UNLOCKED ***
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.11.50.05.28
OpenDSP-v31.1.0.45.0815
eMM-boot
Dec 14 2012,17:10:57:-1
My cid is Tim--401 so not Moonshine s-off compatibile.
Is exist any other method to gain S-off? or the only solution is riff/jtag?
I red the folowing treads about supercid:
http://forum.xda-developers.com/showthread.php?t=2446750&highlight=hboot+2+15+supercid&page=5
http://forum.xda-developers.com/showthread.php?t=2460148
http://forum.xda-developers.com/showthread.php?t=2453595&highlight=hboot+2+15+supercid
http://forum.xda-developers.com/showthread.php?t=1671643&page=48
http://forum.xda-developers.com/showthread.php?p=26516911#post26516911

gforums said:
Step 3 (changig CID) seems to cause trouble to users with base 3.16.401.8, including me.
It looks like mmcblk0p4 is write protected here, so the changing of the CID just does not work.
I also didn't find a working way around yet...
Click to expand...
Click to collapse
You're certain it's .8 and not the .9
I did it on 8 with no problems way back.
Verzonden vanaf mijn HTC One S met behulp van Tapatalk now Free

Here is what worked for me to get supercid 22222222 then facepalm to S-Off. Easy as Pie! But that was for me, hboot 2.15. I take no responsibility! Lol

LibertyMonger said:
Here is what worked for me to get supercid 22222222 then facepalm to S-Off. Easy as Pie! But that was for me, hboot 2.15. I take no responsibility! Lol
Click to expand...
Click to collapse
I had the 3.16.401.9, en after de ruu of 3.16.401.8 it is still write protected.
echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
worked for me.

robertus12 said:
I had the 3.16.401.9, en after de ruu of 3.16.401.8 it is still write protected.
echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
worked for me.
Click to expand...
Click to collapse
It was very relieving huh? I thought we couldn't do it! Glad it worked! :good:

Hi,
This ia maybe very noop question but i gonna give a shot.
I have also 16.401.9 version with hboot 2.15 i will a root access.
Unlock bootloader already done.
But supercid en s-off is mess.
I read here about special line that you must typ in command AFTER su permission.
Can somebody tell me how you gonna get SU permission? When i typ it down is tell me not found? Pfff
Sorry for my english.
Sent from my HTC One S using xda app-developers app

cashvillle said:
Hi,
This ia maybe very noop question but i gonna give a shot.
I have also 16.401.9 version with hboot 2.15 i will a root access.
Unlock bootloader already done.
But supercid en s-off is mess.
I read here about special line that you must typ in command AFTER su permission.
Can somebody tell me how you gonna get SU permission? When i typ it down is tell me not found? Pfff
Sorry for my english.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
1. Fire up your command prompt and go to the directory that you have ADB installed to. Type "adb shell" and hit enter.
2. Type "su" and hit enter. You now have root privileges.

You have the key!
robertus12 said:
I had the 3.16.401.9, en after de ruu of 3.16.401.8 it is still write protected.
echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
worked for me.
Click to expand...
Click to collapse
Could you please elaborate on your process for getting your CID to 22222222? Do I need to modify mmcblk0p4 as the other guides have indicated? Could you please write a short guide?

sliponby said:
Could you please elaborate on your process for getting your CID to 22222222? Do I need to modify mmcblk0p4 as the other guides have indicated? Could you please write a short guide?
Click to expand...
Click to collapse
1. Fire up your command prompt and go to the directory that you have ADB installed to. Type "adb shell" and hit enter.
2. Type "su" and hit enter. You now have root privileges.
3. Type "echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20" and hit enter. To test if it worked restart the phone into fastboot (type "adb reboot bootloader" and hit enter) and once the bootloader screen comes up
type "fastboot oem readcid" and hit enter. It should read "22222222".
4. type "fastboot oem get_identifier_token" and hit enter. Leave that up on your screen and go to HTCdev.com. Follow the instructions from there.
5. Once you have confirmed you have SuperCID, get started with facepalm.

Thanks!
robertus12 said:
1. Fire up your command prompt and go to the directory that you have ADB installed to. Type "adb shell" and hit enter.
2. Type "su" and hit enter. You now have root privileges.
3. Type "echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20" and hit enter. To test if it worked restart the phone into fastboot (type "adb reboot bootloader" and hit enter) and once the bootloader screen comes up
type "fastboot oem readcid" and hit enter. It should read "22222222".
4. type "fastboot oem get_identifier_token" and hit enter. Leave that up on your screen and go to HTCdev.com. Follow the instructions from there.
5. Once you have confirmed you have SuperCID, get started with facepalm.
Click to expand...
Click to collapse
Thanks for the quick reply! Unfortunately it looks like I'm stills screwed. I followed your instructions exactly and I'm still getting my CID as TMOBO-10. If you have any other ideas, I'm listening.

sliponby said:
Thanks for the quick reply! Unfortunately it looks like I'm stills screwed. I followed your instructions exactly and I'm still getting my CID as TMOBO-10. If you have any other ideas, I'm listening.
Click to expand...
Click to collapse
you can ask the guys on irc
http://chat.andirc.net:8080/?channels=facepalm
They Know what to do.

You can't get facepalm s-off, but you could get moonshine s-off
Go to moonshine.io and look for the supported RUU versions and install one that corresponds to your cid. Then you could install moonshine s-off.
Sent from my One S using Tapatalk 4

RyogoNA said:
You can't get facepalm s-off, but you could get moonshine s-off
Go to moonshine.io and look for the supported RUU versions and install one that corresponds to your cid. Then you could install moonshine s-off.
Sent from my One S using Tapatalk 4
Click to expand...
Click to collapse
i have tried... after second test, monshine awaits adb for too short time...about 2-3 secs is missing for phone to reboot completly for monshine could connect with adb... after time counts 60 secs, monshine says i need to fix my adb...

try here

EDIT - I found a workaround and have successfully achieved s-off

[Guide][How-To]How To Root/S-Off/Recovery/&FirmwareUpdate on ATT 3.18

ONLY Works For HTC Evita By AT&T On 3.18..... and I threw this together so people can have all there information on 3.18 in a single thread. I take no credit for the work.... Because I'm not the dev that's made the exploits, or files.
How To Root on the ATT 3.18 firmware for HTC One XL and SuperCID.
- Linux Simplified
- Windows Explained*
DOWNLOAD : ( 3.18 root exploit )
http://forum.xda-developers.com/attachment.php?attachmentid=1973170&d=1368918573
Linux Version.
Requirements -
--Adb Environment--
--Knowledge on how to use adb--
--AT&T HTC One XL and linux based computer haha--
As @myusernam3 says
1. just extract zip*
2. run pwn.sh......This automated method*
3. or follow the windows steps on linux ( the adb steps )
Windows Version
Requirements -
--Adb Environment--
--Adb Knowledge--
-- AT&T HTC One XL and windows based computer
1. Open Command Promt and navigate to your Adb folders and make sure the xpwn.tar.gz Is extracted to the main folder of adb...
2. Execute this command
Code:
adb push oneXchopper /data/local/tmp/xpwn
Followed by*
Code:
adb push busybox /data/local/tmp/busybox
Followed By
Code:
adb push ownage /data/local/tmp/phase1.sh
Next*
Code:
adb shell chmod 755 /data/local/tmp/xpwn /data/local/tmp/busybox
Next*
Code:
adb shell ln -s /data/local/tmp/busybox /data/local/tmp/sed
Next
Code:
adb shell "/data/local/tmp/xpwn"
Next
Code:
adb reboot bootloader
Just to clarify, this is a temp root which sets your CID to SuperCID allowing a bootloader unlock via HTCDev. It does NOT install Superuser or anything of that sort.
I'm not responsible for bricks, warranty voiding, etc. and please let me know if this works*
Thanks to Dan Rosenberg for Motochopper, which I modified very slightly for use in this script.
Thanks also to the people who paid the bounty. You guys are awesome and probably just bought me something nice. Not sure what yet
One more thanks to Daft Punk for providing some decent music to listen to while I worked on this. I was up all night to get lucky xD
Click to expand...
Click to collapse
All credits to the OP of this thread http://forum.xda-developers.com/showthread.php?t=2285086
Sent from my HTC One XL using XDA Premium 4 mobile app

How to S-Off After completing above
Original Thread http://forum.xda-developers.com/showthread.php?t=2155071
Once you have confirmed you have SuperCID, get started (read it through first so you understand it all):
1.) Download patcher and unzip it in your working directory:
soffbin3.zip soffbin3.zip Mirror
2.) Download the zip below
OneX.zip = MD5: 99a8eced1010543e12cbd4e4e8f9638f,* Mirror
3.)
Code:
adb reboot bootloader
(wait for bootloader)
4.)
Code:
fastboot oem rebootRUU
(wait for black HTC Screen)
5.)
Code:
fastboot flash zip PJ8312000-OneX.zip
After a while, You should see the following error “FAILED (remote: 92 supercid! please flush image again immediately)”
6.) Immediately issue the following command:
Code:
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).
7.) Issue the following 3 commands to update the security partition with S-off flags (one command at a time!):
Code:
adb push soffbin3 /data/local/tmp/
adb shell chmod 744 /data/local/tmp/soffbin3
adb shell su -c "/data/local/tmp/soffbin3"
(wait for a few seconds)
8.)
Code:
adb reboot bootloader
9.) You should see what you are looking for!
If you need help or just care to say thanks, join us on IRC:* #FacePalm http://chat.andirc.net:8080/?channels=facepalm
Enjoy.
Click to expand...
Click to collapse
Credits To @beaups

TeamWin Recovery Project -http://forum.xda-developers.com/showthread.php?t=1677447
ClockworkMod Recovery -
To flash recovery. ..
1. Boot into bootloader
2. Select fastboot
3. Open Command Prompt and navigate to adb and fastboot folder. Place " recovery.img " in that folder
4. Plug cord into pc and the phone.
5. Once pacific drivers installed for fastboot control execute
Code:
fastboot flash recovery recovery.img
Sent from my HTC One XL using XDA Premium 4 mobile app

Firmware Update After Achieving S-Off If You Want To Use Sense 5 4.2.2
Firmware (Optional)(But Recommend): http://www.androidfilehost.com/?fid=23060877490004040 (Doesn't overwrite kernel and recovery)
Installing the Firmware (Warning: You MUST be S-OFF and Super CID to flash this! Flash at own risk!)
[*]Reboot to bootloader (adb reboot bootloader if "USB Debugging" is enabled in Android)
[*] Run: fastboot oem rebootRUU
[*] Run: fastboot flash zip
[*] If the output ends with "FAILED (remote: 90 hboot pre-update! please flush image again immediately)", run the previous command AGAIN
[*] If it ends with "INFO..... OK", reboot to the bootloader: fastboot reboot-bootloader
[*] Verify everything was successful by running: fastboot getvar all
[*] Reboot into Android: fastboot reboot or into recovery: fastboot reboot-recovery
Credits to @Turge*

You might want to mention that the 2.15 firmware is only really necessary/recommended for users wanting to run Android 4.2.2 Sense 5 ROMs. It isn't required for anything else. You might also want to mention that the work isn't your own, and give credit to all the people that actually did the work on these exploits.
Sent from my Evita

timmaaa said:
You might want to mention that the 2.15 firmware is only really necessary/recommended for users wanting to run Android 4.2.2 Sense 5 ROMs. It isn't required for anything else. You might also want to mention that the work isn't your own, and give credit to all the people that actually did the work on these exploits.
Sent from my Evita
Click to expand...
Click to collapse
First post mentions nothing on this page is my work and that I take no credit and all 3 post have the credits given to the devs
Sent from my HTC One XL using XDA Premium 4 mobile app

My mistake, I guess missed the credits, sorry about that.
Sent from my Evita

timmaaa said:
My mistake, I guess missed the credits, sorry about that.
Sent from my Evita
Click to expand...
Click to collapse
It's fine
Sent from my HTC One XL using XDA Premium 4 mobile app

Deleted

timmaaa said:
You might want to mention that the 2.15 firmware is only really necessary/recommended for users wanting to run Android 4.2.2 Sense 5 ROMs. It isn't required for anything else. You might also want to mention that the work isn't your own, and give credit to all the people that actually did the work on these exploits.
Sent from my Evita
Click to expand...
Click to collapse
What about 2,14 firmware? Is it necessary for Sense 5 JB 4.2.2 ROMs?

MRaaJR said:
What about 2,14 firmware? Is it necessary for Sense 5 JB 4.2.2 ROMs?
Click to expand...
Click to collapse
No. It's the 2.15 firmware that's recommended for the Sense 5 ROMs.
Sent from my Evita

MRaaJR said:
What about 2,14 firmware? Is it necessary for Sense 5 JB 4.2.2 ROMs?
Click to expand...
Click to collapse
Well you can use 2.14 firmware but to fix any issues that come with sense 5 you will need to use Zarboz Kernel... If you update to 2.15 firmware that was made for Sense 5 4.2.2 you won't have any issues... But to upgrade firmware you must be S-Off
Sent from my HTC One XL using XDA Premium 4 mobile app

Where can i get 2.15 firmare....i tried to find on androidruu but did not get it
Sent from my HTC One XL using XDA Premium 4 mobile app

It's in the first post of Turge's stock Sense 5 ROM thread.
Sent from my Evita

haq.adnan said:
Where can i get 2.15 firmare....i tried to find on androidruu but did not get it
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
timmaaa said:
It's in the first post of Turge's stock Sense 5 ROM thread.
Sent from my Evita
Click to expand...
Click to collapse
It's also in 4th post.
Sent from my HTC One XL using XDA Premium 4 mobile app

Yeah, searching and reading would have found that.
Sent from my Evita

Need minor help
[*] Run: fastboot flash zip
Click to expand...
Click to collapse
Please update this command some 1 .,.... i get unknown partition when i just type it like that ... if i type the file-name.zip i still get the same error. I have used Fastboot, just wanna know which partition to flash the 2.15 firmware in....
FYI: on 3.18 RUU
My System Details
**UNLOCKED**
EVITA PVT SHIP S-OFF RL
CID-11111111
HBOOT-2.14.000
Radio-0.24p.32.09.06
Hope i am not much of a trouble. Tc Have a nice day.
FIXED: its "fastboot flash zip filename.zip" & u should not change the default filename which also throws error. Pulled from Turge's Stock Rom post. All creditz to him.

What changes from 2.14 to 2.15?
Sent from my HTC One XL using xda app-developers app

johnnyham89 said:
What changes from 2.14 to 2.15?
Click to expand...
Click to collapse
The most significant change is (suspected) to have to do with the radio included in the 2.15 firmware package. The power save function on Sense 5 ROMs cause signal drop and reboot issues for some folks, likely having to do with older radios not playing well with the power save function.

Thanks redpoint! Those are the exact problems that I am experiencing! Time to upgrade!!!!
Sent from my HTC One XL using xda app-developers app