Database Info

Revert back to pre-OTA?

Is there a way to revert back to pre-OTA/2.3.3? It seems like there are many more issues that fixes with this OTA. I hardly had any problems at all, and now my camera won't focus (can't use any barcode/qr readers), I'm getting the annoying screen capture/home button problem, etc, etc...
Quite annoying and I would have hoped that they would have come up with a fix by now.

RUU is the only way, which means losing all data (unless you root/back up first) - and you'd need to set your phone to Super CID to go backwards (I think) from a newer version to and older one

EddyOS said:
RUU is the only way, which means losing all data (unless you root/back up first) - and you'd need to set your phone to Super CID to go backwards (I think) from a newer version to and older one
Click to expand...
Click to collapse
As long as you're using the correct RUU for the phone, you don't need to change CID. I did it on my T-Mobile Sensation, from OTA 2.3.4 back to stock 2.3.3 through the RUU.

nxt said:
As long as you're using the correct RUU for the phone, you don't need to change CID. I did it on my T-Mobile Sensation, from OTA 2.3.4 back to stock 2.3.3 through the RUU.
Click to expand...
Click to collapse
Sent you a pm
Sent from my LG-P999 using XDA App

EddyOS said:
RUU is the only way, which means losing all data (unless you root/back up first) - and you'd need to set your phone to Super CID to go backwards (I think) from a newer version to and older one
Click to expand...
Click to collapse
He'll be okay flashing an RUU without SuperCID, it's only needed if flashing an RUU not authorized by the device.
Basically, if the update changed Hboot, he'll need to run revolutionary, then run RUU again as RUU doesn't accept downgrading hboot, which gives weird error codes.
The only way I figured out, was using Revolutionary as it updates the Hboot to an older one.
But as I understand OTA doesn't update Hboot. Right?
Sent from my HTC Sensation Z710e

Can't Get Back To Unrooted Stock No Matter What I Try

Last week I went back to stock to familiarize myself with the process (which unfortunately brought my HBoot to 1.14). I also decided to try out TWRP when I rooted again. But before I could finish up I hit a button in TWRP that didn't need any confirmation. I don't remember which button because it did what it did quicker than I could notice. After that I couldn't even flash a ROM because I couldn't mount the sd card and whatever happened erased everything on my phone but I ended up figuring that out.Now I'm on ViperOneS but I can't unroot. I can't flash either of the RUU (Error 155) that are for T-Mobile US I even changed my CID to 11111111 but no dice(and yes I did flash the stock recovery and boot before relocking). The only thing I can do to get close to unrooted stock is flash the nandroid of a rooted stock ROM. Now I haven't mentioned every method I've tried, so before I start getting bashed for not searching, I want to mention that I've been at this for about 4 days and I have tried EVERYTHING that I've found on XDA and other forums but nothings worked. Is it my HBoot that prevents from doing anything? Should get another One S? Or should I just be thankful that I have a functioning phone?
Sorry for the long winded post but I wanted to make sure I put in as much detail as possible.

antny said:
Last week I went back to stock to familiarize myself with the process (which unfortunately brought my HBoot to 1.14). I also decided to try out TWRP when I rooted again. But before I could finish up I hit a button in TWRP that didn't need any confirmation. I don't remember which button because it did what it did quicker than I could notice. After that I couldn't even flash a ROM because I couldn't mount the sd card and whatever happened erased everything on my phone but I ended up figuring that out.Now I'm on ViperOneS but I can't unroot. I can't flash either of the RUU (Error 155) that are for T-Mobile US I even changed my CID to 11111111 but no dice(and yes I did flash the stock recovery and boot before relocking). The only thing I can do to get close to unrooted stock is flash the nandroid of a rooted stock ROM. Now I haven't mentioned every method I've tried, so before I start getting bashed for not searching, I want to mention that I've been at this for about 4 days and I have tried EVERYTHING that I've found on XDA and other forums but nothings worked. Is it my HBoot that prevents from doing anything? Should get another One S? Or should I just be thankful that I have a functioning phone?
Sorry for the long winded post but I wanted to make sure I put in as much detail as possible.
Click to expand...
Click to collapse
It's most likely your hboot that prevents the RUU's from working. You can only use a RUU that contain a hboot of 1.14 or higher.
Since your signature says HBoot: 1.14 & Radio: 1.08ts.50.02.16_10.08e.50.04L. I assume you updated via the T-mobile US OTA, is that correct?
What's interesting is that other hboots in the 1.14 family are listed as 1.14.0002 but the T-mobile OTA the hboot is labeled 1.14.0004. I haven't seen anyone state if this is will prevent "downgrading" to 1.14.002 and don't feel like finding out myself.
What RUU are you trying?

dc211 said:
It's most likely your hboot that prevents the RUU's from working. You can only use a RUU that contain a hboot of 1.14 or higher.
Since your signature says HBoot: 1.14 & Radio: 1.08ts.50.02.16_10.08e.50.04L. I assume you updated via the T-mobile US OTA, is that correct?
What's interesting is that other hboots in the 1.14 family are listed as 1.14.0002 but the T-mobile OTA the hboot is labeled 1.14.0004. I haven't seen anyone state if this is will prevent "downgrading" to 1.14.002 and don't feel like finding out myself.
What RUU are you trying?
Click to expand...
Click to collapse
Yeah it was the T-Mobile OTA, worst decision ever... I've tried both the 1.84 and 1.53 T-Mo RRU's multiple times and since I changed my CID I've thought of trying another carriers but I don't want to possibly make things worse.
Sent from my HTC One S using xda premium

antny said:
Yeah it was the T-Mobile OTA, worst decision ever... I've tried both the 1.84 and 1.53 T-Mo RRU's multiple times and since I changed my CID I've thought of trying another carriers but I don't want to possibly make things worse.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
I feel your pain. I updated with the OTA that moved us to hboot 1.13 before anyone said they changed the security :crying:.
The 1.84 and 1.53 RUU's wouldn't work for sure. 1.84 has the 1.13 hboot and 1.53 has the 1.09 hboot. Your only hope of using an RUU at this time is one of the Europe RUU's. The good news is that you already moved to supercid so you got that out of the way.
The ones that might work are the ones labeled "RUU_Ville_U_ICE_40_S_Europe_2.xxxxxx"
Here you can get the 2.21 RUU I can't recall if it's the 4.0.4 based one though. Not really sure where to get the other ones as file factory changed their download rules.
http://www.mediafire.com/?xlklqrlljb2zt#r9489rkr82wh2
You might need to click the "mainver error fix" on the on the All-in-one tool kit to get them to work since you would be downgrading the rom.
And if you do use that RUU from mediafire you can go here and click the thanks button for SneakyGhost for putting up the RUU for you to download.
http://forum.xda-developers.com/showpost.php?p=32262143&postcount=153
Then go here and click the thanks button for Football since he's the only source of RUU's there is.
http://forum.xda-developers.com/showpost.php?p=23542379&postcount=1
Good luck.

I've downgraded from 2.31 to 2.21, I know both have HBOOT 1.14 but not exactly sure if they have the exact identical numbers after the 1.14.
HTC One S
---------- Post added at 08:38 AM ---------- Previous post was at 08:34 AM ----------
antny said:
Yeah it was the T-Mobile OTA, worst decision ever... I've tried both the 1.84 and 1.53 T-Mo RRU's multiple times and since I changed my CID I've thought of trying another carriers but I don't want to possibly make things worse.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
2.21 RUU worked better for me than the T-Mobile stock Rom, it doesn't have w Wi-Fi calling do if that's a must for you only hope is to wait for the T-Mobile 2.35 RUU to be released.
HTC One S

dc211 said:
I feel your pain. I updated with the OTA that moved us to hboot 1.13 before anyone said they changed the security :crying:.
The 1.84 and 1.53 RUU's wouldn't work for sure. 1.84 has the 1.13 hboot and 1.53 has the 1.09 hboot. Your only hope of using an RUU at this time is one of the Europe RUU's. The good news is that you already moved to supercid so you got that out of the way.
The ones that might work are the ones labeled "RUU_Ville_U_ICE_40_S_Europe_2.xxxxxx"
Here you can get the 2.21 RUU I can't recall if it's the 4.0.4 based one though. Not really sure where to get the other ones as file factory changed their download rules.
http://www.mediafire.com/?xlklqrlljb2zt#r9489rkr82wh2
You might need to click the "mainver error fix" on the on the All-in-one tool kit to get them to work since you would be downgrading the rom.
And if you do use that RUU from mediafire you can go here and click the thanks button for SneakyGhost for putting up the RUU for you to download.
http://forum.xda-developers.com/showpost.php?p=32262143&postcount=153
Then go here and click the thanks button for Football since he's the only source of RUU's there is.
http://forum.xda-developers.com/showpost.php?p=23542379&postcount=1
Good luck.
Click to expand...
Click to collapse
I've thanked Football and gone to the link you provided but I don't get the whole Pt.1,2 and 3 thing. What am I supposed to do with that?
Edit: All good, just got it from the Dropbox link.... T-Mobile and Easy Tether don't mix.
fmedrano1977 said:
I've downgraded from 2.31 to 2.21, I know both have HBOOT 1.14 but not exactly sure if they have the exact identical numbers after the 1.14.
HTC One S
---------- Post added at 08:38 AM ---------- Previous post was at 08:34 AM ----------
2.21 RUU worked better for me than the T-Mobile stock Rom, it doesn't have w Wi-Fi calling do if that's a must for you only hope is to wait for the T-Mobile 2.35 RUU to be released.
HTC One S
Click to expand...
Click to collapse
I don't really care about wifi calling, cool feature but I hardly use it. Is it 4.0.4 and Sense 4.1 though? It wouldnt stop me from using it if it wasn't but I'm just curious haha.

4.0.4 and Sense 4.0
HTC One S

fmedrano1977 said:
4.0.4 and Sense 4.0
HTC One S
Click to expand...
Click to collapse
Cool Cool Cool thanks

Ah! Great success. I'm now running the European 2.21 RUU and it's great. Thanks again guys. Hopefully if someone's in the same position as I was they'll find this useful.
Sent from my HTC One S using xda premium

antny said:
Ah! Great success. I'm now running the European 2.21 RUU and it's great. Thanks again guys. Hopefully if someone's in the same position as I was they'll find this useful.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Glad it worked out for you.

antny said:
Ah! Great success. I'm now running the European 2.21 RUU and it's great. Thanks again guys. Hopefully if someone's in the same position as I was they'll find this useful.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
One last thing I did after installing that RUU was edit the build.prop to match some lines from the T-Mobile one:
ro.ril.hsdpa.category=24
ro.ril.hsupa.category=6
ro.ril.hsxpa=4
ro.ril.fast.dormancy.rule=2
ro.ril.radio.svn=1
Make sure those match, these have given me the fastest DL speeds.
HTC One S

Yes! Thank you. This seems to be what I'm looking for. You can see the question I posted recently about this similar issue. But I also don't understand the part 1, 2, and 3 thing. Help?

DoogleDood said:
Yes! Thank you. This seems to be what I'm looking for. You can see the question I posted recently about this similar issue. But I also don't understand the part 1, 2, and 3 thing. Help?
Click to expand...
Click to collapse
What are you trying to do?
HTC One S

Nevermind I got it! I wasn't sure if the 3 "parts" of the EU RUU needed to be combined or... what. But upon extracting I found the full file.

fmedrano1977 said:
One last thing I did after installing that RUU was edit the build.prop to match some lines from the T-Mobile one:
ro.ril.hsdpa.category=24
ro.ril.hsupa.category=6
ro.ril.hsxpa=4
ro.ril.fast.dormancy.rule=2
ro.ril.radio.svn=1
Make sure those match, these have given me the fastest DL speeds.
HTC One S
Click to expand...
Click to collapse
Why thank you sir.

antny said:
Why thank you sir.
Click to expand...
Click to collapse
Please someone help me I just flashed axiom rom wifif won't work I tryd other roms too, wifi won't work how can I fix this ??
Do I need to flash a RUU I am new to this. I had th latest tmo update before I rooted the phone people says that's why wifi won't work in other thread.
Please help me fix this !!!

johnyguy said:
Please someone help me I just flashed axiom rom wifif won't work I tryd other roms too, wifi won't work how can I fix this ??
Do I need to flash a RUU I am new to this. I had th latest tmo update before I rooted the phone people says that's why wifi won't work in other thread.
Please help me fix this !!!
Click to expand...
Click to collapse
I'm honestly not to sure on how to fix this. I've searched it before I went back to stock (going back to stock is a definite fix) and couldn't find much on it. I'm sure something has developed from it by now though. Actually :: navigates to another tab:: http://forum.xda-developers.com/showthread.php?t=1900644 if it's compatible with your ROM, this kernel claims to have a fix for wifi and sound (I don't know what the sound issue is all about) but try that, it might work. But most importantly search, read, search and read some more, especially since you're new to this, I've rooted many phones and I still had problems with the One S. Good luck!

Found RUU 2.35 and finally got my phone back to stock. I posted info here:
http://forum.xda-developers.com/showthread.php?t=1941402

sylvestk said:
Found RUU 2.35 and finally got my phone back to stock. I posted info here:
http://forum.xda-developers.com/showthread.php?t=1941402
Click to expand...
Click to collapse
That release gives you the no data when screen is off issue.
HTC One S

HTC ONE S - Unbranding process

Hi all,
I've got a HTC ONE S that has Vodafone (UK) branding on it but the phone is unlocked so it takes my Orange sim card. What's the best method to remove the Vodafone branding? I just want a generic handset.
Thanks in advanced.

Are you talking about the actual physical branding or the software branding?. A simple flash to a 3rd party Rom would "debrand" your device.
Sent from my HTC One S using xda app-developers app

DxTcmix said:
Are you talking about the actual physical branding or the software branding?. A simple flash to a 3rd party Rom would "debrand" your device.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Software unbranding mate. It has Vodafone crap on it. Just want it generic.

bouncyball said:
Software unbranding mate. It has Vodafone crap on it. Just want it generic.
Click to expand...
Click to collapse
Just flash a debranded rom, any here exept tmobile roms would do it.
Oh and WRONG SECTION. Read the rules before posting... sheesh.....

masterkamon842 said:
Just flash a debranded rom, any here exept tmobile roms would do it.
Oh and WRONG SECTION. Read the rules before posting... sheesh.....
Click to expand...
Click to collapse
tryout trickdroid's latest version

Apologies for the wrong forum, I realised that afterwards.
Right, I've now rooted my device so could someone recommend me a STOCK rom to clear out the Vodafone crap?
Thank you
EDIT - I have the S4 ONE S (1.5Ghz version)

bouncyball said:
Apologies for the wrong forum, I realised that afterwards.
Right, I've now rooted my device so could someone recommend me a STOCK rom to clear out the Vodafone crap?
Thank you
EDIT - I have the S4 ONE S (1.5Ghz version)
Click to expand...
Click to collapse
Choose wise, choose carefully:
http://www.shipped-roms.com/index.php?category=android&model=Ville
Eu 1.78 is pretty good actually
Sent from my One S using xda app-developers app

JohnKoeMan said:
Choose wise, choose carefully:
http://www.shipped-roms.com/index.php?category=android&model=Ville
Eu 1.78 is pretty good actually
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Thanks for that. I updated the phone to JB the other night so will these be compatible?
Also - I tried a ROM last night and it wasn't the right file type but I wiped my old OS. But as a guide told me to make a backup, I did and restored without any problems but lost SuperSU - Is this normal? Shall I just re-install?
Downloaded one but unsure how to install them as they're EXE files. What state does my phone need to be in? It also says
From:
Image Version
3.16.161.9
To:
Image Version:
1.78.401.2
Error [155]: UNKNOWN ERROR
I've tried locking my bootloader again it says 'RELOCKED' but still says TAMPERED
EDIT - In recovery screen also, it says at the top
***TAMPERED***
***UNLOCKED***
Is this normal?

I am getting no where with this and it's becoming very annoying!
I've tried reading through forum and forum, YouTube videos and various different methods!
All I want is my phone to be STOCK and it's taking me over 4 hours this morning to get no where!

bouncyball said:
I am getting no where with this and it's becoming very annoying!
I've tried reading through forum and forum, YouTube videos and various different methods!
All I want is my phone to be STOCK and it's taking me over 4 hours this morning to get no where!
Click to expand...
Click to collapse
Really strange that it says relocked/tampered and tampered/unlocked in recovery...
You might've gone wrong with the relocking of your phone, undoubtedly have you checked this out.
Can you tell me what you've ben trying so far?
And another thing: if you updated to JB, these RUUs might not work any longer since they are ICS mostly.
The best thing for you is to go by a custom ROM, it is at least the easiest thing to do now.
You can always fiddle around to restore to STOCK but as you've experienced yourself already, it isn't easy.
Here's a link to what I used when I bricked my phone, it might be of some help.
http://www.htconeforum.com/forum/ht...unbrick-restore-htc-one-s-stock-relocked.html

JohnKoeMan said:
Really strange that it says relocked/tampered and tampered/unlocked in recovery...
You might've gone wrong with the relocking of your phone, undoubtedly have you checked this out.
Can you tell me what you've ben trying so far?
And another thing: if you updated to JB, these RUUs might not work any longer since they are ICS mostly.
The best thing for you is to go by a custom ROM, it is at least the easiest thing to do now.
You can always fiddle around to restore to STOCK but as you've experienced yourself already, it isn't easy.
Here's a link to what I used when I bricked my phone, it might be of some help.
http://www.htconeforum.com/forum/ht...unbrick-restore-htc-one-s-stock-relocked.html
Click to expand...
Click to collapse
Thanks for the reply.
EDIT - Locking my handset I'm doing the following ;
Placing my Unlock_code.bin in the DATA folder on the toolkit and pressing RELOCK BOOTLOADER
I've tried the following ;
Running RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed.EXE while the phone is on the HOME SCREEN and BOOTLOADER
Running OTA_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_1.11.50.05.28_10.27.50.08L_release_301852xf01hejl416oev96.ZIP using Hasoon's Toolkit.
I'm getting ERROR messages 151 when installing from the phones HOME SCREEN and ERROR 131 when installing from Bootloader.
I've tried both methods while the phone is LOCKED and UNLOCKED
Currently my phone is displaying the following in the bootloader menu ;
***TAMPERED***
***UNLOCKED***
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.11-50.05.28
OpenDSP-v31.1.0.45.0815
eMMC-boot
Dec 14 2012, 17:10:57-1
My goal is put have a stock or stock looking ROM with the Vodafone software removed.
Thanks for reading.

Double post

bouncyball said:
Thanks for the reply.
EDIT - Locking my handset I'm doing the following ;
Placing my Unlock_code.bin in the DATA folder on the toolkit and pressing RELOCK BOOTLOADER
I've tried the following ;
Running RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed.EXE while the phone is on the HOME SCREEN and BOOTLOADER
Running OTA_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_1.11.50.05.28_10.27.50.08L_release_301852xf01hejl416oev96.ZIP using Hasoon's Toolkit.
I'm getting ERROR messages 151 when installing from the phones HOME SCREEN and ERROR 131 when installing from Bootloader.
I've tried both methods while the phone is LOCKED and UNLOCKED
Currently my phone is displaying the following in the bootloader menu ;
***TAMPERED***
***UNLOCKED***
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.11-50.05.28
OpenDSP-v31.1.0.45.0815
eMMC-boot
Dec 14 2012, 17:10:57-1
My goal is put have a stock or stock looking ROM with the Vodafone software removed.
Thanks for reading.
Click to expand...
Click to collapse
Error 131 means the RUU is incompatible with your CID. Do you know it? Not sure where to find cid specific RUU but searching XDA will always yield answers.
Lock phone, fastboot usb connect phone, find right RUU and open the .exe
Btw you htc drivers installed on you're pc right?
Sent from my One S using xda app-developers app

JohnKoeMan said:
Error 131 means the RUU is incompatible with your CID. Do you know it? Not sure where to find cid specific RUU but searching XDA will always yield answers.
Lock phone, fastboot usb connect phone, find right RUU and open the .exe
Btw you htc drivers installed on you're pc right?
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply.
CID is something I've seen pop up - I'll have a look into this. I have HTC drivers yeah.
CID: VODAP001

bouncyball said:
Thanks for the reply.
CID is something I've seen pop up - I'll have a look into this. I have HTC drivers yeah.
CID: VODAP001
Click to expand...
Click to collapse
Check here for your RUU and maybe new insight:
http://forum.xda-developers.com/showthread.php?t=1936905&page=2
---------- Post added at 03:11 PM ---------- Previous post was at 03:00 PM ----------
JohnKoeMan said:
Check here for your RUU and maybe new insight:
http://forum.xda-developers.com/showthread.php?t=1936905&page=2
Click to expand...
Click to collapse
Ignore that, was for htc one X XD
---------- Post added at 03:24 PM ---------- Previous post was at 03:11 PM ----------
bouncyball said:
Thanks for the reply.
CID is something I've seen pop up - I'll have a look into this. I have HTC drivers yeah.
CID: VODAP001
Click to expand...
Click to collapse
Read this article carefully. It will give you an insight in how difficult the process we're doing is:
http://www.xda-developers.com/android/facepalm-s-off-for-htc-one-s-one-xl-and-droid-dna/
You said you downloaded the latest OTA right? This article states that with the latest OTA update we are no longer able to SUPERCID the phone, meaning only CID-specific RUUs can be applied. I can't find any RUUs for your CID, so this might just be the end of the road for this plan.
So maybe installing a ROM similar to stock might be the only good solution for you.

JohnKoeMan said:
Check here for your RUU and maybe new insight:
http://forum.xda-developers.com/showthread.php?t=1936905&page=2
---------- Post added at 03:11 PM ---------- Previous post was at 03:00 PM ----------
Ignore that, was for htc one X XD
---------- Post added at 03:24 PM ---------- Previous post was at 03:11 PM ----------
Read this article carefully. It will give you an insight in how difficult the process we're doing is:
http://www.xda-developers.com/android/facepalm-s-off-for-htc-one-s-one-xl-and-droid-dna/
You said you downloaded the latest OTA right? This article states that with the latest OTA update we are no longer able to SUPERCID the phone, meaning only CID-specific RUUs can be applied. I can't find any RUUs for your CID, so this might just be the end of the road for this plan.
So maybe installing a ROM similar to stock might be the only good solution for you.
Click to expand...
Click to collapse
Thanks for the information - I'll give this a read in a while. I've also looked into changing the CID of my phone, followed a couple of guides but they don't seem to work, they just crash my phone.
EDIT - So, basically I have to stick with the Vodafone branding on my ONE S unless I flash to a custom ROM?

bouncyball said:
Thanks for the information - I'll give this a read in a while. I've also looked into changing the CID of my phone, followed a couple of guides but they don't seem to work, they just crash my phone.
EDIT - So, basically I have to stick with the Vodafone branding on my ONE S unless I flash to a custom ROM?
Click to expand...
Click to collapse
Yeah, its the only way I guess...
Nothing wrong with custom ROMs, they're the best, trust me! :good:

JohnKoeMan said:
Yeah, its the only way I guess...
Nothing wrong with custom ROMs, they're the best, trust me! :good:
Click to expand...
Click to collapse
Can you recommend me a good one to try? One that's as close to stock as possible that doesn't have any problems. This is my 3rd HTC device and the last 2 devices always had problems, hence why I wanted stock.
EDIT - Also, what steps do I need to take to get it back to before I rooted it? Completely factory before I installed anything.

Still getting nowhere.
I've even managed to change my CID to 11111111 from the Vodafone branded one using HEX editor. Still getting the same error's when I'm trying to install .ZIP and .EXE's when the bootloader is RELOCKED.

Could no one else shed some light on this for me please?
CID is now HTC__001 and still get the same error messages!
How hard can it be to remove a service providers software from a phone?
I would really appreciate someones help - I've tried pretty much all I can try!
Could I install an Android version lower than what I've got? I don't mind it not being JB as it's pretty much the same as ICS!

[Q] HBoot - Unable to update.

After finally managing to work around Windows 8 and its BS, I rooted and unlocked the bootloader on my AT&T One X.
I'm now at the point of trying to update HBoot so that I can use the JB Roms. The phone is currently still running ICS. I followed the tutorial on YouTube from"onexroot" using JBWFlasher. My HBOOT versin is 1.14 currently, Originally my phone was S-ON with a CID of "11111111". I S-OFF'ed the phone and changed the CID to HTC__001 and all the way down the list because I keep getting the error "FAILED (remote: 41 model id check fail)". No matter which CID I give the phone or if I attempt to update for a device with S-ON or S-OFF.
Not really sure what else to try at this point as I've searched here and all over Google. I didn't want to bother you guys with it but I don't know where else to go.
Thanks for any help in advance.

Neorift said:
After finally managing to work around Windows 8 and its BS, I rooted and unlocked the bootloader on my AT&T One X.
I'm now at the point of trying to update HBoot so that I can use the JB Roms. The phone is currently still running ICS. I followed the tutorial on YouTube from"onexroot" using JBWFlasher. My HBOOT versin is 1.14 currently, Originally my phone was S-ON with a CID of "11111111". I S-OFF'ed the phone and changed the CID to HTC__001 and all the way down the list because I keep getting the error "FAILED (remote: 41 model id check fail)". No matter which CID I give the phone or if I attempt to update for a device with S-ON or S-OFF.
Not really sure what else to try at this point as I've searched here and all over Google. I didn't want to bother you guys with it but I don't know where else to go.
Thanks for any help in advance.
Click to expand...
Click to collapse
Unless I'm missing something, you don't need to update hboot to use JB ROMs. I never did and I've been using Sense and AOSP jellybean ROMs for the past 7 months or so.

RollTribe said:
Unless I'm missing something, you don't need to update hboot to use JB ROMs. I never did and I've been using Sense and AOSP jellybean ROMs for the past 7 months or so.
Click to expand...
Click to collapse
Really? Everything I read today mentioned the need to update hboot. My concern is being able to recover from it if it fails.

Yeah there's no need to update anything, just flash a jb rom from recovery. Once you have s-off hboot version kinda becomes moot
Sent from my HTC One X using xda premium

That model Id check fail is because your trying to flash a rom for the wrong phone.
Your lucky that's happening because usually it just bricks.
I should probably add that some people cannot boot newer JB Roms without updating hboot but that is not always the case and I still have no idea why it is so for some.

Yeah I should've asked... Do you have dual or quad core One X?

exad said:
That model Id check fail is because your trying to flash a rom for the wrong phone.
Your lucky that's happening because usually it just bricks.
I should probably add that some people cannot boot newer JB Roms without updating hboot but that is not always the case and I still have no idea why it is so for some.
Click to expand...
Click to collapse
I hadn't even gotten to the step to flash the ROM at that point. It was just for the hboot.
Anyway, got it sorted now. Thanks for the help everyone.

[Q] HTC One X Need RUU (Cant Find CID AT ALL/11111111) Need Stock!

Hello everybody! I need help urgent! I have my AT&T HTC One X (XL according to my "Settings" "Model Number" and I need to restore back to stock. I'll list everything that is wrong, I need help with, and more settings on my device. MAINLY, IF ANYBODY CAN AT LEAST HELP ME TO FIND MY CID AS SOON AS POSSIBLE, THAT'S ALL I NEED AS FAR AS I KNOW RIGHT NOW.
My Device Settings:
1. Android Version: 4.1.1
2. I did successfully flash to "MIUI-3.8.9" using "Hasoon2000's HTC One X (Evita) All-In-One Toolkit" for most of this.
3. HBOOT/Bootloader:
*** TAMPERED ***
***RELOCKED ***
EVITA PVT SHIP S-OFF RL
CID-11111111
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
4. RECOVERY:
ClockworkMod Recovery v6.0.3.1
Notes:
1. I looked at the video on youtube, "TUTORIAL: HTC One X stock ROM update: 4.1.1 to 4.2.2 (via CWM)" using CWM (same version) but kept getting status error 0 no matter whether odexed or deodexed.
2. I tried using fastboot options I saw on other posts on this website to find your stock CID, but it still showed 11111111.
3. I used "Hasoons200's Toolkit" to SuperCID to 11111111.
4. "Xfactor" on the toolkit to exploit the device's CID.
Help With:
1. To at least get/find out a way to find out my TRUE STOCK CID as quick as possible.
2. To find the RUU used for this device.
I truly thank all of you for your help!

If your phone is an at&t model the original CID is CWS__001. Your CID doesn't actually matter anyway because you're s-off, you can run any Evita RUU without any problems regardless of your CID. The reason fastboot commands were showing your CID as 11111111 is because your CID is 11111111, that's because SuperCID overwrites the original CID.
There's nothing at all "wrong" with your device. I think you're extremely confused. I'm not sure why you've been trying all those toolkits, those give you SuperCID, they don't reverse it. You seem to lack a basic understanding of this device, modifying it, and what you can and can't do with it. Why exactly do you want to return to stock? I can tell you exactly how to do it but I'd like to know why first.
Sent from my Evita

timmaaa said:
If your phone is an at&t model the original CID is CWS__001. Your CID doesn't actually matter anyway because you're s-off, you can run any Evita RUU without any problems regardless of your CID. The reason fastboot commands were showing your CID as 11111111 is because your CID is 11111111, that's because SuperCID overwrites the original CID.
There's nothing at all "wrong" with your device. I think you're extremely confused. I'm not sure why you've been trying all those toolkits, those give you SuperCID, they don't reverse it. You seem to lack a basic understanding of this device, modifying it, and what you can and can't do with it. Why exactly do you want to return to stock? I can tell you exactly how to do it but I'd like to know why first.
Sent from my Evita
Click to expand...
Click to collapse
Yeah I do have AT&T. Also, yes, I'm pretty new at rooting and such, but I am still learning
I forgot to add this in the post, will edit it in, that I am using "MIUI" like said, and I decided I wanted to get another rom. I tried to get "Paranoid Android", latest version, boot-loader both unlocked and locked, and TWRP and CWM recovery. It came up with status 0 (having to do with the update-binary) but luckily I made a nandroid backup. The device is still working from the nandroid backup, but I will probably use the CID (CWS__001) to get the stock RUU endeavor, then flash.

Eh.. You have an evita, not endeavor. If you flash endeavor stuff you will likely brick.
Sent from my HTC One XL using xda app-developers app

exad said:
Eh.. You have an evita, not endeavor. If you flash endeavor stuff you will likely brick.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Ok. IS there anyway to know which RUU I would need to get stock without CID? If you need any information to help me with this (such as rom version I'm currently using and such) I'll let you know.

Antm50jr said:
Yeah I do have AT&T. Also, yes, I'm pretty new at rooting and such, but I am still learning
I forgot to add this in the post, will edit it in, that I am using "MIUI" like said, and I decided I wanted to get another rom. I tried to get "Paranoid Android", latest version, boot-loader both unlocked and locked, and TWRP and CWM recovery. It came up with status 0 (having to do with the update-binary) but luckily I made a nandroid backup. The device is still working from the nandroid backup, but I will probably use the CID (CWS__001) to get the stock RUU endeavor, then flash.
Click to expand...
Click to collapse
The installer for Paranoid Android probably failed because the ROM wasn't meant for this phone, you got lucky it didn't brick you. You have the Evita, not the Endeavoru, I'm not sure where you're downloading your ROMs from but it's the wrong place. Only ever download ROMs from within this device forum you're posting in now, NEVER anywhere else.
Sent from my Evita
---------- Post added at 04:40 AM ---------- Previous post was at 04:37 AM ----------
Antm50jr said:
Ok. IS there anyway to know which RUU I would need to get stock without CID? If you need any information to help me with this (such as rom version I'm currently using and such) I'll let you know.
Click to expand...
Click to collapse
You have s-off so you can run any Evita RUU that you want, your CID doesn't matter when you have s-off. Go to androidruu.com and get one from there, just make sure it's from the Evita section. I still have no idea why you want to RUU though, you said you just want to change ROMs, an RUU will return your phone to being completely stock.
Sent from my Evita

timmaaa said:
The installer for Paranoid Android probably failed because the ROM wasn't meant for this phone, you got lucky it didn't brick you. You have the Evita, not the Endeavoru, I'm not sure where you're downloading your ROMs from but it's the wrong place. Only ever download ROMs from within this device forum you're posting in now, NEVER anywhere else.
Sent from my Evita
---------- Post added at 04:40 AM ---------- Previous post was at 04:37 AM ----------
You have s-off so you can run any Evita RUU that you want, your CID doesn't matter when you have s-off. Go to androidruu.com and get one from there, just make sure it's from the Evita section. I still have no idea why you want to RUU though, you said you just want to change ROMs, an RUU will return your phone to being completely stock.
Sent from my Evita
Click to expand...
Click to collapse
I can't believe this! It turns out, it's bricked I think! I tried to restore from a nandroid backup I got off the internet, not sure whether it was evita or not, WAS ON THIS WEBSITE (XDA), and not it won't boot. The screen is on, but it shows the white screen HTC logo with red letters under it, and made a low buh-buh sound when in USB. I cant find a way to enter boot-loader or recovery (computer cant detect it) but it does show the solid red light at the top. Please, even if it involves downloading a ton of computer applications, I'm willing to.

I can believe it. Why the hell did you restore a nandroid if you're not even sure if it was for Evita? Have you not listened to a word we've been saying to you? I'm not sure why I bothered trying to help you if you're ignoring the advice I'm giving. Your phone isn't bricked, if it turns on it isn't bricked. Do some research and figure out how to recover.
Sent from my Evita

timmaaa said:
I can believe it. Why the hell did you restore a nandroid if you're not even sure if it was for Evita? Have you not listened to a word we've been saying to you? I'm not sure why I bothered trying to help you if you're ignoring the advice I'm giving. Your phone isn't bricked, if it turns on it isn't bricked. Do some research and figure out how to recover.
Sent from my Evita
Click to expand...
Click to collapse
I just wanted to say that I am sorry, and I did fix the problem. Thank you for your support! You are right: I should have listened and pay more attention. Thank you though! I'll always check to see whether a rom is Evita or Endeavor.