Database Info

[Q] HTC Sensation: Phone ON, but screen BLANK after Android 2.3.4 OTA update!

Hi all,
I got the Android 2.3.4 OTA update, downloaded and installed it. The Sensation switched on right after update. The HTC boot screen came up, the boot-up sound played, AND THE SCREEN WENT BLANK!!
Now, I know the phone is actually ON, because I can call it from another phone and it rings. Also, the regular gesture on the screen to answer a call works too, but still, nothing shows on the display.. it's totally BLANK..
How can i solve this issue?? Thanks in advance

Try flashing a RUU again, there's a thread with all available RUUs here: http://forum.xda-developers.com/showthread.php?t=1074559
If you have a Tmobile Sensation then select TMOUS and open it after it downloads, and follow instructions. If it doesn't work, you should put the warranty to use if it has warranty.

KCuadrado said:
Try flashing a RUU again, there's a thread with all available RUUs here: http://forum.xda-developers.com/showthread.php?t=1074559
If you have a Tmobile Sensation then select TMOUS and open it after it downloads, and follow instructions. If it doesn't work, you should put the warranty to use if it has warranty.
Click to expand...
Click to collapse
Thanks for the quick reply!
Just wanted to note to you that my phone has never been rooted or has never had any custom firmware or any such thing done. This was the only OS update i've done since i bought it. Other than that, only tiny apps and games have been installed.
Also, the phone is not locked to any network.
Does your instruction still apply? if so, please let me know the way ahead. Thanks again

RUU
MicroWise said:
Thanks for the quick reply!
Just wanted to note to you that my phone has never been rooted or has never had any custom firmware or any such thing done. This was the only OS update i've done since i bought it. Other than that, only tiny apps and games have been installed.
Also, the phone is not locked to any network.
Does your instruction still apply? if so, please let me know the way ahead. Thanks again
Click to expand...
Click to collapse
Yes, the RUU is a file that you open and it's like an OTA update but for computer, something like that. I have a Tmobile Sensation and I flashed this one:
RUU_Pyramid_TMOUS_1.29.531.2_Radio_10.42.9007.00P_10.11.9007.15_M_release_193714_signed
It's the latest leaked RUU I think, and it's the same version that came with my phone when I got it. I used it to get S-ON too after S-Off and rooting. There's a tutorial for that too here if you want to root. Let me know how it works.

KCuadrado said:
Yes, the RUU is a file that you open and it's like an OTA update but for computer, something like that. I have a Tmobile Sensation and I flashed this one:
RUU_Pyramid_TMOUS_1.29.531.2_Radio_10.42.9007.00P_10.11.9007.15_M_release_193714_signed
It's the latest leaked RUU I think, and it's the same version that came with my phone when I got it. I used it to get S-ON too after S-Off and rooting. There's a tutorial for that too here if you want to root. Let me know how it works.
Click to expand...
Click to collapse
Yea, that's the thing, my friend. I don't want to do anything like rooting/unrooting etc. etc. all i want is my phone's screen to start working.
before the 2.3.4 OTA update, I had Android 2.3.3 on my phone. is there any way to go back to that version of Android?

You not rooting/unrooting. You're just flashing the stock ROM back onto the phone. See it as reformating a PC hard drive for a clean installation. You will lose all data, mind

EddyOS said:
You not rooting/unrooting. You're just flashing the stock ROM back onto the phone. See it as reformating a PC hard drive for a clean installation. You will lose all data, mind
Click to expand...
Click to collapse
aah ic.. apologies for my stupid questions.. i'me truly a newbie when it comes to stuff like this..
can you please give me directions on which RUU to choose and how to go about doing the installation? umm... please...? *innocent eyes*

Haven't tried taking the battery out yet..? First thing I would do

Hi Tirozz,
Yea i've done all of that:
- took off battery, put it in after 30 seconds, switched it on
- did hard reset by going into that special mode by pressing power and volume down
- took off memory card and switched on
still nothing..

MicroWise, there is a way to get back to Android 2.3.3. Download this RUU if you have a Tmobile Sensation:
http://www.filefactory.com/file/cb7...00P_10.11.9007.15_M_release_193714_signed.exe
Open it in your Windows PC and follow the instructions, then you'll have the stock Android 2.3.3 back again.
If you don't have the TMobile one, download the corresponding one from here:
http://forum.xda-developers.com/showthread.php?t=1074559
Let me know how it goes.

I had the same problem,
& i solve it by installing the previous ROM & don't flash the update
install your compatible Rom form the thread above,

KCuadrado said:
MicroWise, there is a way to get back to Android 2.3.3. Download this RUU if you have a Tmobile Sensation:
http://www.filefactory.com/file/cb7...00P_10.11.9007.15_M_release_193714_signed.exe
Open it in your Windows PC and follow the instructions, then you'll have the stock Android 2.3.3 back again.
If you don't have the TMobile one, download the corresponding one from here:
http://forum.xda-developers.com/showthread.php?t=1074559
Let me know how it goes.
Click to expand...
Click to collapse
Thanks for the instructions, KCuadrado. And again, i'm very sorry for being an absolute idiot in this area and bugging you all with it..
my sensation is not a Tmobile.. infact its not tied to ANY operators.. and doesn't have any operator logos on it either.. it is not network locked.. so which RUU do i use from there?

I don't know how to help you now :/
Check the RUU forum thread and ask if someone has a RUU for your HTC. Or you can try rooting and getting SuperCID so you can flash any RUU file, but it's easier to ask on the forum thread for your compatible RUU file.

Alright, Thanks a lot, dude.
I shall go over there
---------- Post added at 10:53 PM ---------- Previous post was at 10:50 PM ----------
KCuadrado said:
I don't know how to help you now :/
Check the RUU forum thread and ask if someone has a RUU for your HTC. Or you can try rooting and getting SuperCID so you can flash any RUU file, but it's easier to ask on the forum thread for your compatible RUU file.
Click to expand...
Click to collapse
Bad idea.. apparently i'm too young on this forum to post anything on that thread.. :/
please help..

Dear,
I have the same problem when i updated my phone to 2.3.4 (Official Arabic ROM)
i changed my ROM & put the ORIGINAL One (T-Mobile) & i update it, everything is OK,
The problem is with the official Arabic ROM only (I think)
is there any solution available ??
Thank you all

hey i have the same problem
REVOLUTIONARY
PYRAMID
HBOOT-1.27.1100
RADIO-10.14.9035.01_M
eMMC-BOOT
Jan 13 2012 ,17.33.34
i have no idea what i have to do
i was reading and reading but nothing concrete
id like to know if could u help me ??

MicroWise said:
Alright, Thanks a lot, dude.
I shall go over there
---------- Post added at 10:53 PM ---------- Previous post was at 10:50 PM ----------
Bad idea.. apparently i'm too young on this forum to post anything on that thread.. :/
please help..
Click to expand...
Click to collapse
What is the model of your phone and what region are you in? I assume it's an XE or XL, not 4g. I will try to help you.. are you at all familiar with adb? What does it say on the screen of the phone when you press the vol- and power power? Can you take a photo and upload it?
Sent from my HTC Sensation 4G with Beats Audio using xda premium

jesusanz33 said:
hey i have the same problem
REVOLUTIONARY
PYRAMID
HBOOT-1.27.1100
RADIO-10.14.9035.01_M
eMMC-BOOT
Jan 13 2012 ,17.33.34
i have no idea what i have to do
i was reading and reading but nothing concrete
id like to know if could u help me ??
Click to expand...
Click to collapse
You can't flash an ota with custom recovery. Nothing concrete? Have you tried using the search function on the forum, hundreds of posts about it?
Sent from my HTC Sensation 4G with Beats Audio using xda premium

so do i have to go back to stock recovery?? how to do that??? and i have s-off and rooted stock rom thx

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

Solution to [email protected]:\# and get s-off

Just got S-OFF now on my HTC one XL Woohoo and excited that its gonna be my first development thread
Thats not a new idea but its a solution for those guys who having problem when they type "adb shell" and get screen displaying "[email protected]:\#" and they cant go further because of it and cant get their supercid.
U gonna need:
a) u need ROM Toolbox Lite to installed in your phone, if u have extra money , u can buy pro version but there is no need of it [play store link : https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolbox&hl=en]
b) Phone has to be rooted (if your phone has SuperCID on already you can skip steps 1-3)
so:
1. Boot to recovery TWRP and go to the file manager and go to /dev/block/... copy mmcblk0p4 your sd-card
2. Copy mmcblk0p4 to your computer
3. Open the file (mmcblk0p4) with your hex editor.
4. Look for offset 00000210 (if your on RUU version 1.82 the offset may be 00000214) and you should see your cid number [mine was rogers001] with your IMEI number attached to it.
5. Change rogers001 [or whatever ur cid number is] to 11111111 and save the file as mmcblk0p4MOD. This will give you SuperCID as well. MAKE SURE AT THIS POINT THAT THE FILE IS THE EXACT SIZE IT WAS BEFORE YOU HEX EDITED IT!
6.Now, save that mmcblk0p4MOD file to your sdcard [not in any folder].
7. Now open ur ROM Toolbox Lite and go to open TERMINAL EMULATOR
8. Type adb shell and hit enter , its gonna give u no device found error but dont worry about it.
9. Then type "su" and hit enter again. This will put you back into the android shell and give you root privileges.
10. Type "dd if=/sdcard/mmcblk0p4MOD of=/dev/block/mmcblk0p4" and hit enter.
11. To test if it worked restart the phone into fastboot and once the bootloader screen comes up type "fastboot oem readcid" and hit enter. It should read "11111111".
12. Go to http://forum.xda-developers.com/showthread.php?t=2155071 & Followed instructions 1-9 (Note- even my model id showed PJ8310000 but PJ8312000-OneX.zip works)
13. Should have S-OFF
That is what worked for my HTC One X Rogers!!!

I will try it soon. I have a Rogers as well and have been trying to s-off for months with no success.
Sent from my HTC One XL using XDA Premium 4 mobile app

good work!
but, how does this differ from the all in one toolkit or facepalm?

mistertim said:
good work!
but, how does this differ from the all in one toolkit or facepalm?
Click to expand...
Click to collapse
This isn't for s-off. Thus is to help people achieve supercid if they are having trouble with it.
Sent from my Alienized Evita using XDA Premium IV

Myrder said:
This isn't for s-off. Thus is to help people achieve supercid if they are having trouble with it.
Sent from my Alienized Evita using XDA Premium IV
Click to expand...
Click to collapse
Thanks a lot!!.. You are awesome!! I managed to get S-Off finally!!

feel good to help
its feel good when u help any1 ,
thats not different method , its just another way to get supercid and s-off for those who having error [email protected]:\# when they type ADB SHELL in cmd ..

I was trying to help you on another thread. Glad to see you figured out a solution.
But as this thread does not contain any original work that you developed, it will likely be removed from Development, and into General.

but thanx for your time
redpoint73 said:
I was trying to help you on another thread. Glad to see you figured out a solution.
But as this thread does not contain any original work that you developed, it will likely be removed from Development, and into General.
Click to expand...
Click to collapse
yeah i remember that and i m thank full to you bcoz after all those pms and questioning , i came to know that i have to do this from another angle and thanx to GOD , i figured it out ,
i dont mind where this thread will move or not , i just want to help those persons who getting failure and failure after every method they use for s-off like me so that they dont waste their time , as i did , i almost wasted 7,8 months

You guys are just getting s-off now?? I have been s-off from day one and my one xl is from Rogers
Also my girl friends one xl rogers has been too
Sent from my HTC One XL using xda app-developers app

johnnyp12321 said:
You guys are just getting s-off now?? I have been s-off from day one and my one xl is from Rogers
Also my girl friends one xl rogers has been too
Click to expand...
Click to collapse
You realize not everyone buys their phones at the same time, right?

Maybe these guys have only recently gotten this phone. It's great that you got s-off early but this ain't a pissing contest.
Sent from my Evita

redpoint73 said:
You realize not everyone buys their phones at the same time, right?
Click to expand...
Click to collapse
Yea I realize this and my gf got hers way after I got mine and also the carrier would not change the phone all one xls rogers had would be pretty much the same and able to s-off just took some Google research to figure out how to achieve it
Sent from my HTC One XL using xda app-developers app
---------- Post added at 02:31 PM ---------- Previous post was at 02:28 PM ----------
Also not trying to have a pising contest all info is good info if it helps people out
Sent from my HTC One XL using xda app-developers app

Good work. Since this is more of a guide and not really development, Im going to move this to the General section. Thanks for putting this together.

johnnyp12321 said:
Yea I realize this and my gf got hers way after I got mine and also the carrier would not change the phone all one xls rogers had would be pretty much the same and able to s-off just took some Google research to figure out how to achieve it
Click to expand...
Click to collapse
I was helping the OP, and if I remember correctly, he just got the phone. Yes, carrier doesn't matter. But the error message he was getting in adb, I was not familiar with, and neither was another experienced "helper" here. He found a solution himself (which I applaud) and decided to post it here. So what is the issue with that? Aside from the fact this doesn't belong in Development (and I see its just been moved). There are also a significant number of people still coming here every day, asking about s-off.

I didn't say I had I problem with the information posted I was just curious why people from rogers couldn't achieve s-off sorry if you took offence to my post they were not ment to be rude or disrespectful
Sent from my HTC One XL using xda app-developers app

What Redpoint said. Plus, this is actually a solution to a problem during the SuperCID process, not the s-off process. Yeah all it usually takes is some research but that's irrelevant if you run into an issue that nobody has seen before (and therefore there is no published fix). That is exactly what this guide is addressing, and I too applaud the OP for finding a way around this unique problem and sharing it with the community.
Sent from my Evita

johnnyp12321 said:
I didn't say I had I problem with the information posted I was just curious why people from rogers couldn't achieve s-off sorry if you took offence to my post they were not ment to be rude or disrespectful
Click to expand...
Click to collapse
I never said or implied you were being rude or disrespectful, so no need to apologize. People are allowed to disagree or discuss different viewpoints here.
It says right in the OP what his issue with getting s-off (actually SuperCID, as timmaaa clarified) was: he was getting the message "[email protected]:\#" from adb, and would not let him progress any further.
As timmaaa mentioned, not everyone encounters the same things when trying to mod their phones. I can name quite a few times on various devices, where I followed the XDA instructions to a tee, and something happened that wasn't "supposed" to (phone froze, had to pull battery, etc.).

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 what 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

magellan14 said:
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 what 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
Click to expand...
Click to collapse
Yeah unfortunately because of the write protection there is no method that'll work for you. I guess jtag is your only solution.
Sent from my Evita

[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.

[Q] AT&T HTC One X ROM & Kernel Problem

Hi guys,
I'm newbie about android and please do not be angry to me for this question. I was read lots of topics from xda and another forums but I can't find anything.
I have AT&T HTC One X and i was happy with my phone. Maybe one year ago I rooted my phone and install ATT Stock Root - 3.18.502.6 - JB 4.1.1.zip. So, i followed instructions from xda's web site and everything was fine.
Last two weeks my phone starts to restarts it self. So, I decide to install everything again and open my phone in recovery mode with TWRP and wipe all data. (I don't have any backup of my original data)
I have TRWP's 2.7.1.0 version and I tried to install ATT Stock Root - 3.18.502.6 - JB 4.1.1.zip because I install it one year ago and it works fine. It installs fine but when I press restart my phone stuck at Quietly Brilliant screen and after 2 minutes my phone restarts it self.
Also I can't s-off my phone. I have unlock code bin and I applied it to my phone but something was wrong.
So please can any one help me please. I don't know why my phone acts like that.
Thanks in advance.

Ok so I know your a newbie but do you know your firmware is way out of date? We now have firmware for at&t that is at least 4 realises older than the current. I would say upgrade to a new ROM and firmware. If you don't wish to upgrade I have to ask what kernel you are using?

What he said. Also, did you flash the boot.img from the rom zip via fastboot? As you are s-on, you must perform that additional step.

I suggest he reads timaaas thread. Sounds to me like he should run a ruu to which he can still obtain s off.

Well thanks for suggestions, but I don't know what is the sequence for installing new firmware, rom and kernel. Could you guys please explain the it.

marknoll said:
I suggest he reads timaaas thread. Sounds to me like he should run a ruu to which he can still obtain s off.
Click to expand...
Click to collapse
No, no, no! He can't run an RUU while s-on because it'll brick his phone. I know you mean well but you need to increase your own knowledge before you can start giving advice here, I've seen at least a few times where you've given advice that would result in a brick. I'm sure you don't want that on your conscience.
Sent from my Evita
---------- Post added at 08:56 PM ---------- Previous post was at 08:53 PM ----------
ahrar said:
Well thanks for suggestions, but I don't know what is the sequence for installing new firmware, rom and kernel. Could you guys please explain the it.
Click to expand...
Click to collapse
You more than likely only needed to flash the boot.img from the ROM zip by fastboot. Flash the ROM, then flash the boot.img, and your phone should boot up. Once you're all booted you need to get s-off. Look in my guide thread in my signature for instructions.
Sent from my Evita

timmaaa said:
No, no, no! He can't run an RUU while s-on because it'll brick his phone. I know you mean well but you need to increase your own knowledge before you can start giving advice here, I've seen at least a few times where you've given advice that would result in a brick. I'm sure you don't want that on your conscience.
Sent from my Evita
---------- Post added at 08:56 PM ---------- Previous post was at 08:53 PM ----------
You more than likely only needed to flash the boot.img from the ROM zip by fastboot. Flash the ROM, then flash the boot.img, and your phone should boot up. Once you're all booted you need to get s-off. Look in my guide thread in my signature for instructions.
Sent from my Evita
Click to expand...
Click to collapse
No no. I didn't mean for him to run ruu. I suggested he read your thread to see what requisite is needed to do so. I wasn't suggestioning to ruu..omg no. Lol

marknoll said:
No no. I didn't mean for him to run ruu. I suggested he read your thread to see what requisite is needed to do so. I wasn't suggestioning to ruu..omg no. Lol
Click to expand...
Click to collapse
But that's exactly what you said:
Sounds to me like he should run a ruu...
Click to expand...
Click to collapse
Sent from my Evita

Yes. Run a ruu if he meets the requirementz

marknoll said:
Yes. Run a ruu if he meets the requirementz
Click to expand...
Click to collapse
But he doesn't, and that's the point. Why say that when it's clear that he doesn't meet the requirements? What if he took your advice and ran the RUU? Would you have bought him a nice new phone? Am I making sense here?
Sent via Bacon

Yep