Hi, new to the forums and completely perplexed by this rom root flashing stuff. I have tried following some guides but I'm just not sure that they are applicable in my circumstance:
Situation:
1. Complete technophobe sister came back from holiday complaining she needed a new battery for her Sensation as it just kept rebooting over and over.
2. This phone has NEVER been modded or flashed or god knows what. It was unlocked from its carrier (Vodafone) though by the previous owner. Bought in the UK.
3. I had another spare battery and used that. Same situation.
4. I started googling. Lots of people with similar situations but not identical. Key difference is that all of them have meddled with their devices FIRST and THEN got into this bootloop.
5. All the advice is therefore a few steps ahead of where I am and is leaving me confused and puzzles.
What the device can/can't do:
I can get to the Boot menu and navigate it
I cannot boot into Android proper as it were.
"Recovery" and "Factory Reset" both send the phone into its boot loop cycle.
Defining what I call a bootloop:
Goes to the blank white screen with HTC logo then off then rinse and repeat over and over.
What I have done:
I tired following some links from some of these threads and did a SuperCID??? (the thing where you go to cmd and do fastboot-reboot 11111111 or something similar) as all the threads kept complaining that the OP hadn't done this yet. This seemed to be successful but the instructions following then didn't seem to apply.
Other info you might need?
PYRAMID PVT SHIP S-ON RL
HBOOT-1.27.0000
RADIO-11.29A350418_M
OpenADSP-v)".6/0/2266.00.0131
eMMC-boot
Jan 13 2012,17:33:34
I hope I have written all you need. Apologies if I have not.
theonetruewill said:
Hi, new to the forums and completely perplexed by this rom root flashing stuff. I have tried following some guides but I'm just not sure that they are applicable in my circumstance:
Situation:
1. Complete technophobe sister came back from holiday complaining she needed a new battery for her Sensation as it just kept rebooting over and over.
2. This phone has NEVER been modded or flashed or god knows what. It was unlocked from its carrier (Vodafone) though by the previous owner. Bought in the UK.
3. I had another spare battery and used that. Same situation.
4. I started googling. Lots of people with similar situations but not identical. Key difference is that all of them have meddled with their devices FIRST and THEN got into this bootloop.
5. All the advice is therefore a few steps ahead of where I am and is leaving me confused and puzzles.
What the device can/can't do:
I can get to the Boot menu and navigate it
I cannot boot into Android proper as it were.
"Recovery" and "Factory Reset" both send the phone into its boot loop cycle.
Defining what I call a bootloop:
Goes to the blank white screen with HTC logo then off then rinse and repeat over and over.
What I have done:
I tired following some links from some of these threads and did a SuperCID??? (the thing where you go to cmd and do fastboot-reboot 11111111 or something similar) as all the threads kept complaining that the OP hadn't done this yet. This seemed to be successful but the instructions following then didn't seem to apply.
Other info you might need?
PYRAMID PVT SHIP S-ON RL
HBOOT-1.27.0000
RADIO-11.29A350418_M
OpenADSP-v)".6/0/2266.00.0131
eMMC-boot
Jan 13 2012,17:33:34
I hope I have written all you need. Apologies if I have not.
Click to expand...
Click to collapse
You could try putting paper or cardboard between the battery and the back cover to keep snug and fit.
If that doesn't work, then I would try to run a ruu.exe to restore the phone to stock. Look here for ruu.exe: http://forum.xda-developers.com/showthread.php?p=26541170
Sent from my Ouya
AndroidSupporter318 said:
You could try putting paper or cardboard between the battery and the back cover to keep snug and fit.
If that doesn't work, then I would try to run a ruu.exe to restore the phone to stock. Look here for ruu.exe: http://forum.xda-developers.com/showthread.php?p=26541170
Sent from my Ouya
Click to expand...
Click to collapse
I'd like to add just because you do not seem to be S-OFF, which means you don't have SuperCID, pick an RUU based on your device's CID, else it will not work. check what your CID is and pick the RUU compatible with it. It should be what the phone came with (same region and carrier).
I believe RUU should fix this issue, so you should definitely try that. SuperCID cannot be achieved while S-ON, but it doesn't really matter in your situation (unless you can't find the appropriate RUU).
astar26 said:
I'd like to add just because you do not seem to be S-OFF, which means you don't have SuperCID, pick an RUU based on your device's CID, else it will not work. check what your CID is and pick the RUU compatible with it. It should be what the phone came with (same region and carrier).
I believe RUU should fix this issue, so you should definitely try that. SuperCID cannot be achieved while S-ON, but it doesn't really matter in your situation (unless you can't find the appropriate RUU).
Click to expand...
Click to collapse
Some phones do have superCID with s-on. Iv seen it with the htc desire / s
jmcclue said:
Some phones do have superCID with s-on. Iv seen it with the htc desire / s
Click to expand...
Click to collapse
Anyway, checking the CID before doing anything should be good, just to be safe. And at least as far as I know, it's only possible to achieve SuperCID while S-OFF (possible to S-ON later, but to achieve you must have S-OFF at the time). But this doesn't matter to the problem at hand.
astar26 said:
Anyway, checking the CID before doing anything should be good, just to be safe. And at least as far as I know, it's only possible to achieve SuperCID while S-OFF (possible to S-ON later, but to achieve you must have S-OFF at the time). But this doesn't matter to the problem at hand.
Click to expand...
Click to collapse
I have put card in-between this to keep it secure before on a trial and error when it was having connection issues. It is not this that is the problem. Thank you for your input though.
astar26 said:
Anyway, checking the CID before doing anything should be good, just to be safe. And at least as far as I know, it's only possible to achieve SuperCID while S-OFF (possible to S-ON later, but to achieve you must have S-OFF at the time). But this doesn't matter to the problem at hand.
Click to expand...
Click to collapse
How do I do this. Please bear in mind I have not rooted etc before. I performed Step 4 of this guide before and that is why I believed I had done this. http://forum.xda-developers.com/showthread.php?t=1192300
I'd like to add just because you do not seem to be S-OFF, which means you don't have SuperCID, pick an RUU based on your device's CID, else it will not work. check what your CID is and pick the RUU compatible with it. It should be what the phone came with (same region and carrier).
I believe RUU should fix this issue, so you should definitely try that. SuperCID cannot be achieved while S-ON, but it doesn't really matter in your situation (unless you can't find the appropriate RUU).
Click to expand...
Click to collapse
This is where I got confused and started to seek assistance. I have no idea what my CID is or really how to use an RUU or what one to pick. It was a UK Vodafone handset but I don't know how this corresponds to anything or what to do about it.
AndroidSupporter318 said:
...If that doesn't work, then I would try to run a ruu.exe to restore the phone to stock. Look here for ruu.exe: http://forum.xda-developers.com/showthread.php?p=26541170
Sent from my Ouya
Click to expand...
Click to collapse
When I do (and did before) step 3 I just get a list of commands and no current software version showing. This was exactly when I came here. I thus went no further as what I had did not correspond.
If you got your device from UK vodaphone then this should be your RUU (got it from RUU thread in Sensation Development).
if you want to check CID (you need adb and fastboot with device drivers on your computers, I'll explain in short (and assume you have the tools)):
connect phone to computer with USB debugging enabled
-adb reboot bootloader
when bootloader starts, run this:
-"fastboot getvar cid"
this will give you the CID your device has.
astar26 said:
If you got your device from UK vodaphone then this should be your RUU (got it from RUU thread in Sensation Development).
if you want to check CID (you need adb and fastboot with device drivers on your computers, I'll explain in short (and assume you have the tools)):
connect phone to computer with USB debugging enabled
-adb reboot bootloader
when bootloader starts, run this:
-"fastboot getvar cid"
this will give you the CID your device has.
Click to expand...
Click to collapse
I just get a series of commands and what they do. I don't get anything else. I can also not check if USB debugging is enabled as the phone wont turn on to turn it on.
jmcclue said:
Some phones do have superCID with s-on. Iv seen it with the htc desire / s
Click to expand...
Click to collapse
in the sensation forums no one reported that he had supercid while on S-ON
theonetruewill said:
I just get a series of commands and what they do. I don't get anything else. I can also not check if USB debugging is enabled as the phone wont turn on to turn it on.
Click to expand...
Click to collapse
open the cmd window in the folder where you have adb and fastboot files and perform there the command
also make sure that in hboot screen it shows fastboot usb
rzr86 said:
in the sensation forums no one reported that he had supercid while on S-ON
Click to expand...
Click to collapse
Hi. Maybe no one has reported it but u can have supercid with s-on, and i dont mean by going s-off first. It is very rare tho, like if u work for lets say vodafone then u can get a stock s-on phone with supercid. For development r something i think. But like i said, its very rare that us general public get our hands on them. But it is possible
Got it to show my cid. Error when flashing the rom using the executable file. Will try again when back from work
Getting stuck at step 4.2/4.3 of this guide (http://forum.xda-developers.com/showthread.php?p=26541170). The archive is always corrupt and thus changes cannot be made to the text file. I can't do 4.3 because it says error not correct id (ERROR [130]: MODEL ID ERROR)and it directs back to 4.2. Any suggestions?
I have also tried HTCs own flash update (https://support.htc.com/en-us/HTC_S..._Updates/Software_Update_for_HTC_Sensation_4G) this also fails to work for exactly the same reasons.
theonetruewill said:
Getting stuck at step 4.2/4.3 of this guide (http://forum.xda-developers.com/showthread.php?p=26541170). The archive is always corrupt and thus changes cannot be made to the text file. I can't do 4.3 because it says error not correct id (ERROR [130]: MODEL ID ERROR)and it directs back to 4.2. Any suggestions?
I have also tried HTCs own flash update (https://support.htc.com/en-us/HTC_S..._Updates/Software_Update_for_HTC_Sensation_4G) this also fails to work for exactly the same reasons.
Click to expand...
Click to collapse
maybe you used an RUU of SE when you are not (or otherwise, regular for XE). beside CID, there is MID. the procedure of adding your MID and checking the MID is similiar to the CID.
MID indicates your model - in this case mainly three are possible: one for regular sensation, one for XE, and one for 4G.
theonetruewill said:
Getting stuck at step 4.2/4.3 of this guide (http://forum.xda-developers.com/showthread.php?p=26541170). The archive is always corrupt and thus changes cannot be made to the text file. I can't do 4.3 because it says error not correct id (ERROR [130]: MODEL ID ERROR)and it directs back to 4.2. Any suggestions?
I have also tried HTCs own flash update (https://support.htc.com/en-us/HTC_S..._Updates/Software_Update_for_HTC_Sensation_4G) this also fails to work for exactly the same reasons.
Click to expand...
Click to collapse
when you are trying to add your cid to the text file don't extract it
just open it as it is,add your cid and then save it
rzr86 said:
when you are trying to add your cid to the text file don't extract it
just open it as it is,add your cid and then save it
Click to expand...
Click to collapse
I am doing this. The zipped folder is unable to be opened in windows explorer (opened not extracted) as it says it is not valid. I then tried to use winrar to open it (not extract it) This worked. However when I attempt to save the modifications it says archive corrupt and unable to save.
I can't even do the S-OFF then Super CID thing because my HBOOT (1.27.0000) isn't listed here..... http://revolutionary.io
Managed to get a RUUto flash to it - http://freakshare.com/files/gt7345y....23.3504.07_M2_release_251541_signed.exe.html
Unfortunately this has not fixed the problem. I suspect this may be terminal. Any suggestions?
HI there guys, I have the phone in my hands now.
Will is one of my close friends and I plan to get it back alive.
I'll try and look around and post questions here, as I'm not familiar with HTC devices.
I've flashed god knows how many Samsung's and helped quite a few hundred thousand people with flashing via ODIN.
To me: The phone seems locked, and stuck in a bootloop.
Wiping doesn't resolve the issue, nor does trying to flash another firmware as it comes with errors.
theonetruewill said:
I can't even do the S-OFF then Super CID thing because my HBOOT (1.27.0000) isn't listed here..... http://revolutionary.io
Click to expand...
Click to collapse
with that hboot version you can only use juopunutbear method to S-OFF the device
try to unlock the bootloader via htcdev site
flash a custom recovery(i suggest 4ext)
flash a custom rom from recovery(before flashing enable smartflash from 4ext)
---------- Post added at 02:55 AM ---------- Previous post was at 02:54 AM ----------
TotallydubbedHD said:
HI there guys, I have the phone in my hands now.
Will is one of my close friends and I plan to get it back alive.
I'll try and look around and post questions here, as I'm not familiar with HTC devices.
I've flashed god knows how many Samsung's and helped quite a few hundred thousand people with flashing via ODIN.
To me: The phone seems locked, and stuck in a bootloop.
Wiping doesn't resolve the issue, nor does trying to flash another firmware as it comes with errors.
Click to expand...
Click to collapse
post your bootloader details and what exactly did you do ?
---------- Post added at 02:58 AM ---------- Previous post was at 02:55 AM ----------
theonetruewill said:
I am doing this. The zipped folder is unable to be opened in windows explorer (opened not extracted) as it says it is not valid. I then tried to use winrar to open it (not extract it) This worked. However when I attempt to save the modifications it says archive corrupt and unable to save.
Click to expand...
Click to collapse
do it with notepad++
Related
Hi all
I would like to know if it is possible to return a Desire S to S-ON if it were made it S-OFF, rooted and then upgraded from a network-specific ROM to a higher generic HTC ROM.
I've seen various threads about this, but can't find any specific steps for a relative newbie.
The revolutionary.io method would be used to go S-OFF.
Any input very much appreciated.
schnidex said:
Hi all
I would like to know if it is possible to return a Desire S to S-ON if it were made it S-OFF, rooted and then upgraded from a network-specific ROM to a higher generic HTC ROM.
I've seen various threads about this, but can't find any specific steps for a relative newbie.
The revolutionary.io method would be used to go S-OFF.
Any input very much appreciated.
Click to expand...
Click to collapse
Go to shippedroms and download the RUU for your phone. Although why you'd want to return to stock is beyond me?
You're saying that just running a branded RUU will return it to S-ON? Are you sure about that?
It's because I'd need the phone sent back under warranty, which S-OFF invalidates.
schnidex said:
You're saying that just running a branded RUU will return it to S-ON? Are you sure about that?
It's because I'd need the phone sent back under warranty, which S-OFF invalidates.
Click to expand...
Click to collapse
+1 sending my phne back on Monday. I read the guide, but I still don't get it. It's too confusing. What's adb shell etc?
olyloh6696 said:
+1 sending my phne back on Monday. I read the guide, but I still don't get it. It's too confusing. What's adb shell etc?
Click to expand...
Click to collapse
ADB is Android Debug Bridge. It's installed on your PC and enables you to control the phone over USB (if you have USB debugging on) and HTC drivers installed on PC.
adb shell - is simply when you run a shell through a command prompt on a PC so that you're able to directly type commands into the phone from the PC.
You should be able to see the adb drivers as a link within my signature, download and install these as a quick workaround which should enable you to run adb shell or you could follow the full correct method of installing the full Android SDK and JDK see below:
kartkk said:
do a nandroid backup & also set up your adb beforehand
setting up adb saved me from possibly bricking my device a few times
try this guide
Click to expand...
Click to collapse
ben_pyett said:
ADB is Android Debug Bridge. It's installed on your PC and enables you to control the phone over USB (if you have USB debugging on) and HTC drivers installed on PC.
adb shell - is simply when you run a shell through a command prompt on a PC so that you're able to directly type commands into the phone from the PC.
You should be able to see the adb drivers as a link within my signature, download and install these as a quick workaround which should enable you to run adb shell or you could follow the full correct method of installing the full Android SDK and JDK see below:
Click to expand...
Click to collapse
Thanks Ben! Makes sense! But to s-on again, can I just flash the h-boot., but then how do I use RUU to get back to stock? Will u need to wipe data first etc?
Sent from my HTC Desire S using XDA Premium App
olyloh6696 said:
Thanks Ben! Makes sense! But to s-on again, can I just flash the h-boot., but then how do I use RUU to get back to stock? Will u need to wipe data first etc?
Click to expand...
Click to collapse
I'm afraid that I don't know about S-ON after S-OFF with AlphaRevx as I used XTC clip to get S-OFF myself, which is one way process.
So as I've never gone through the process myself I can't really confirm its success or failure.
But, I assume that you're following this GUIDE which involves running an RUU as the final step.
I wouldn't bother wiping data first as I imagine that the RUU process will do that as part of its operation. If not and it works you can always run a factory reset afterwards.
ben_pyett said:
I'm afraid that I don't know about S-ON after S-OFF with AlphaRevx as I used XTC clip to get S-OFF myself, which is one way process.
So as I've never gone through the process myself I can't really confirm its success or failure.
But, I assume that you're following this GUIDE which involves running an RUU as the final step.
I wouldn't bother wiping data first as I imagine that the RUU process will do that as part of its operation. If not and it works you can always run a factory reset afterwards.
Click to expand...
Click to collapse
cheers ben. will this also remove cutom recoveries from the phone (cwm) ?
so it would be truly stock then?
olyloh6696 said:
cheers ben. will this also remove cutom recoveries from the phone (cwm) ?
so it would be truly stock then?
Click to expand...
Click to collapse
If the ruu runs successfully to competition I believe that it will return the device do that it's identical to stock
Swyped from HTC Desire S using XDA Premium
After many, many hours of trying to figure out what the hell half the terminology about Android actually means and wondering whether or not I would brick my phone..
..I'm now back to S-ON. It's been a pretty horrible experience all in all. Yes, it's easy when you know how but knowing how has been through trial and fortunately not much error.
From being on 6.98.1002, I used the Jorgen method in Ben's link above to get to 0.98.0000. I should note that when my phone was first supplied, I was on 0.98.0002 and very worried that the earlier software wouldn't work - but I tried it anyway, and it did. However, I was still S-OFF.
I then re-installed my stock network ROM using the RUU. This kept me on 0.98.0000 but put the phone to S-ON. I flashed the branded ROM that the phone was shipped with thinking that this would take me to 0.98.0002 but to my surprise it didn't. Otherwise though, the phone is now stock condition again.
So I then tried to update OTA to the problematic software which caused me all this grief in the first place - and it appears my network have withdrawn it. And rightly so, pending a fix.
schnidex said:
Ben, I've seen elsewhere you've said:
"If you load the latest RUU you may end up updating the HBOOT so that it can't be downgraded."
..in which case, Houston, we may have a problem. The latest HTC non-branded ROM (1.47...) gives you HBOOT 6.98.1002.
Click to expand...
Click to collapse
You're right, I'm afriad that this is an area where I'm no expert, But HBOOT = 6.98.1002. = Alpharevx = so you've not upgraded it simply failed to downgrade (which is slightly better- I think )
I notice that there are a couple of guides, allow I've obviously not tried either of them both are in the [GUIDE] A Complete Tutorial for the Beginners and Others sticky
The second guide looks quite complex and not for beginners...
Although I've just spotted a note within the second guide which says says
Note 2: RUU 1.46 or greater can not be downgraded as yet, since gingerbreak does not work on these RUUs.
So Opps....a full nights sleep may shed some more light on this.....and hopefully so sound advice from someone who has already performed this task.
Good luck. (I'll back online in the morning) - but, only really able to answer easier questions and not unfortunately not provide you with a solution.....but I'll do what I can!
Alternate way to restore your phone to S-ON and stock
If your attempts are unsuccessful, there's another potential way to go S-ON.
http://forum.xda-developers.com/showpost.php?p=17481836&postcount=2
Maarten
I got a bricked T-mobile Sensation today at the shop and after checking it out I thought it would be easy to fix but unfortunately its proving to be much more difficult than I expected. Here's what I'm working with:
Locked s-on
Hboot 1.18.0000
radio 10.14.9035.01_m
First, I tried all kinds of PG58 zips. None worked. I figure I need to be unlocked to do it. Did the HTC unlock and got to the warning screen and where it asks to choose yes or no. I can navigate to yes or no but when I choose yes it just freezes and doesn't do anything. I tried it 3 different times, same thing. I can't even choose factory reset in Hboot, it just freezes. I don't know what the eff is going on. I've been downloading RUUs but have yet to find the correct one. I don't know what firmware it has because it does not boot up.
I thought, well shoot, I have fastboot, maybe I could just s-off and root from fastboot, but I can't find any thread explaining how to do it.
Any help would be great.
Thanks!
Edit:
Found the correct RUU, 1.50.xxxx whatever. WHen I run the utility It says its rebooting into bootloader but stays in the same screen and doesn't do anything. I don't know if this helps, but when I go into the bootloader I cannot go back into hboot. It just, freezes.
Have you tried this guide?
http://forum.xda-developers.com/showthread.php?t=1192300
And you need to be s-off to flash those pg58 zips, thats why they failed.
As you're on HBOOT 1.18.0000 use the revolutionary method to get S-OFF. http://revolutionary.io
The HTC unlock is a bit redundant as it doesn't give S-OFF which you need.
There are many guides here on XDA to help you. Such as:
http://forum.xda-developers.com/showthread.php?t=1192300
EDIT: Oops didn't notice that "Kazireh" has already posted the link.
You'll need the HTC drivers (download HTC Sync install it then delete HTC Sync leaving the drivers installed).
You should also get the ADB tools installed as at some stage they'll be useful.
As far as the RUU is concerned you need to make sure it's the right one for the current CID on the phone.
Kazireh said:
Have you tried this guide?
http://forum.xda-developers.com/showthread.php?t=1192300
And you need to be s-off to flash those pg58 zips, thats why they failed.
Click to expand...
Click to collapse
gol_n_dal said:
As you're on HBOOT 1.18.0000 use the revolutionary method to get S-OFF. http://revolutionary.io
The HTC unlock is a bit redundant as it doesn't give S-OFF which you need.
There are many guides here on XDA to help you. Such as:
http://forum.xda-developers.com/showthread.php?t=1192300
EDIT: Oops didn't notice that "Kazireh" has already posted the link.
You'll need the HTC drivers (download HTC Sync install it then delete HTC Sync leaving the drivers installed).
You should also get the ADB tools installed as at some stage they'll be useful.
As far as the RUU is concerned you need to make sure it's the right one for the current CID on the phone.
Click to expand...
Click to collapse
Thanks for the help guys, but heres the deal:
I cannot s-off due to it not being able to boot.
I could try Junopbears s-off but I cannot unlock, as it just freezes when I try.
I found the correct ruu but again it freezes and does not boot into the bootloader.
My CID is T-mob010
I have all drivers installed, adb, fastboot, etc
If your on hboot 1.18 you have a gingerbread fw, look for that
Sent from my HTC Sensation 4G
its completely possible that the motherboard is failing. I see this in my shop all the time, though usually with the MyTouch 4G (faulty eMMC chip) but the sensation and a few other HTC's also see this. we havent come up with a solution between my two stores employees, so hopefully someone here can?
q said you did not understand, is how I explain more thoroughly I am new to the subject
and my device does not enter the system and when using the mode prop vo comand says device not found what to do? sensation with my ta hboot 1.27.0000 s-s on rl unloked help me
2strokenut said:
Thanks for the help guys, but heres the deal:
I cannot s-off due to it not being able to boot.
Click to expand...
Click to collapse
Can you get into "Fastboot USB" ?
I could try Junopbears s-off but I cannot unlock, as it just freezes when I try.
Click to expand...
Click to collapse
Junopbear is wrong as it's for 1.2x.xxxx HBOOT, try Revolutionary.
I found the correct ruu but again it freezes and does not boot into the bootloader.
My CID is T-mob010
Click to expand...
Click to collapse
Eek.
T-MOB010 == RUU x.xx.531.xxxxxxxxx according to my list.
I have all drivers installed, adb, fastboot, etc
Click to expand...
Click to collapse
Good.
There are a few "unbrick" guides, never tried to use them so can't help on that front.
nickL0V3 said:
its completely possible that the motherboard is failing. I see this in my shop all the time, though usually with the MyTouch 4G (faulty eMMC chip) but the sensation and a few other HTC's also see this. we havent come up with a solution between my two stores employees, so hopefully someone here can?
Click to expand...
Click to collapse
Yeah that's what I'm leaning toward right now, there is nothing else I can do. I have 4 or 5 Mytouchs on the shelf with bad eMMc chips so I guess this one is joining them.
gol_n_dal said:
Can you get into "Fastboot USB" ?
Junopbear is wrong as it's for 1.2x.xxxx HBOOT, try Revolutionary.
Eek.
T-MOB010 == RUU x.xx.531.xxxxxxxxx according to my list.
Good.
There are a few "unbrick" guides, never tried to use them so can't help on that front.
Click to expand...
Click to collapse
Yes the RUU was 1.50.531.xxxxxx
Yes, I can get into Fastboot usb, I can do fastboot commands, it just freezes when the RUU tries to do its thing.
Jbear would still work if the bootloader were locked, but I couldn't unlock the bootloader. Revolutionary will not work either because its run while the phone is on, which I can't do.
I think I've exhausted every option, it seems to all point to a failed eMMc chip, shame though, I really like these phones.
Thanks for the help fellas
GL
///////////////
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.
I finally got S-Off, and thought life was good. Installed the newest MagioRom (I had a much older version), but now the phone just hangs. The ROM attempts to load, goes through its splash screen, then the screen turns white with a green HTC in the center, and the buttons light up. After about a minute, the screen will darken. The screen buttons will make the phone vibrate, but they don't do anything. Occasionally, between the splash screen and the white screen, the taskbar will appear at the top. The phone shows no signal, but trying to pull the bar down does nothing. The ROM was a clean install with a full wipe. The power button will bring up the power menu, but selecting anything gets stuck and I have to do a hard reset. I powered it down through the bootloader. Any ideas?
I'm S-off (finally), CID 11111111, HBoot 2.16.0000 and radio 1.20.50.05.16
EDIT: And just found that the sdcard won't mount.
Here is a link to fix your sd-card:
http://forum.xda-developers.com/showthread.php?t=1630459&page=36
mannte said:
Here is a link to fix your sd-card
Click to expand...
Click to collapse
Thats what I was thinking it was. It did get worse before it got better. Trying to pull out of it gave the phone a bootloop at the white HTC screen. I finally quit trying to fix it per all the unmounted sdcard threads and tried an RUU. It boots now, but hangs as it is trying to load the sdcard. The OEM recovery can't see it either. I've even done the clear storage and factory reset in the bootloader to see if it would help. The only thing that I have got out of it is losing my "tampered" warning at the top.
Could my sdcard be dead?
It's not very likely that your sd-card is dead because it is just a partition, so if your sdcard is dead your phone probably wouldn't work at all.
Normally I should say that it would be a firmware, partition problem or a bad flash but the RUU should have fixed that.
I have two question if the answers are both yes than i have no other idea's and would advise you to return it for warranty and hope for the best.
1. Did you run an signed RUU.exe file. The filename should look like something like this: RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe
2. Did the RUU run without any errors?
You could also try to run the RUU one's more or try another RUU, you should get the right one matching provider and country/region.
Here is a list of RUU's for the htc one s:
http://www.androidruu.com/index.php?developer=Ville
One last thing did you change your CID, that is also known to cause problems.
If you want to return it for warranty then I wrote a guide how to get your phone completely back to stock:
http://forum.xda-developers.com/showthread.php?t=2606312
You could also just relock it and then return it but they maybe let you pay then.
mannte said:
1. Did you run an signed RUU.exe file. The filename should look like something like this: RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe
2. Did the RUU run without any errors?
Click to expand...
Click to collapse
I ran: RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S.16_2_10.22.31501S.10L_release_263233_signed.exe
It ran without any problems.
mannte said:
Here is a list of RUU's for the htc one s:
http://www.androidruu.com/index.php?developer=Ville
One last thing did you change your CID, that is also known to cause problems.
Click to expand...
Click to collapse
That is where I picked this RUU up from.
I am CID: 11111111
mannte said:
If you want to return it for warranty then I wrote a guide how to get your phone completely back to stock:
Click to expand...
Click to collapse
I doubt it even still has one, I bought it a week after it made it to the US market.
I ran: RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S.16_2_10.22.31501S.10L_release_263233_signed.exe
It ran without any problems.
Click to expand...
Click to collapse
Try this RUU it's a newer version:
http://www.androidruu.com/getdownlo..._10.30.50.08L_release_309489_signed_ICS_2.exe
I am CID: 11111111
Click to expand...
Click to collapse
If you're still S-OFF, try changing your CID back to the original, it's probably: T-MOB010
You can change your CID by typing: 'fastboot oem writecid yourCIDnumber' when you are in fastboot mode.
You can also use one of the HTC One S toolkits like Hasoon200 toolkit or the toolkit form squabbi.
I doubt it even still has one, I bought it a week after it made it to the US market.
Click to expand...
Click to collapse
In Europe you get 2 year's of warranty (In some countries even without a receipt), I don't know the US rules though.
ville
why my one s usually have some reboot????????
Hi, any help will be much appreciated getting my Sensation working again!
What happened:
I am trying to unroot and unS-Off my Sensation XE to get it back to stock (I have a new phone, although I've had a lot of fun with my Pyramid). I stupiudly managed to brick my Sensation completely and have since unbricked it thanks to the clever guys here http://forum.xda-developers.com/showthread.php?t=1522351.
Where I am:
However, now, whatever I try, I can't successfully flash a stock HTC ROM. I'm stuck at the bootloader screen. If I try flashing a stock Sensation RUU file through Windows, and I've tried about four all compatible for my phone varient, towards the end of the process I get an signature check error in the RUU application. This is despite the phone's CID, if that's the right term, matching the RUU's accepted CIDs. Other methods I've tried, e.g. KGS Utilty, also fail (seems to stall).
I'm thinking something needs to be done to the phone before I can flash an RUU, following the unbricking.
Phone info:
Here is the bootlader info etc.
"*** LOCKED ***
*** Security Warning ***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
RADIO-10.14.9035.02_2
eMMC-boot
Aug 2 2011,22:35:52"
It's a European SIM-free Sensation XE (direct from HTC as a replacement after my Desire HD failed a long time ago!)
If more info is needed am happy to oblige, preferably if I can have the fastboot command to show all the details if applicable.
What can I do ?! (That's the Q)
Thank you.
Berky99 said:
Hi, any help will be much appreciated getting my Sensation working again!
What happened:
I am trying to unroot and unS-Off my Sensation XE to get it back to stock (I have a new phone, although I've had a lot of fun with my Pyramid). I stupiudly managed to brick my Sensation completely and have since unbricked it thanks to the clever guys here http://forum.xda-developers.com/showthread.php?t=1522351.
Where I am:
However, now, whatever I try, I can't successfully flash a stock HTC ROM. I'm stuck at the bootloader screen. If I try flashing a stock Sensation RUU file through Windows, and I've tried about four all compatible for my phone varient, towards the end of the process I get an signature check error in the RUU application. This is despite the phone's CID, if that's the right term, matching the RUU's accepted CIDs. Other methods I've tried, e.g. KGS Utilty, also fail (seems to stall).
I'm thinking something needs to be done to the phone before I can flash an RUU, following the unbricking.
Phone info:
Here is the bootlader info etc.
"*** LOCKED ***
*** Security Warning ***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
RADIO-10.14.9035.02_2
eMMC-boot
Aug 2 2011,22:35:52"
It's a European SIM-free Sensation XE (direct from HTC as a replacement after my Desire HD failed a long time ago!)
If more info is needed am happy to oblige, preferably if I can have the fastboot command to show all the details if applicable.
What can I do ?! (That's the Q)
Thank you.
Click to expand...
Click to collapse
post the output from this command
fastboot getvar all
don't show your imei and s/n
The only RUU's I could find according to your device was:
RUU_Pyramid_LE_hTC_Asia_TW_1.73.709.4_Radio_10.58.9035.00U_10.15.9035.02_2_release_221625_signed.exe
RUU_PYRAMID_LE_ICS_35_S_HTC_Europe_3.33.401.153_Radio_11.76A.3504.00U_11.24A.3504.31_M_release_281004_signed.exe
As long as you have hboot 1.18 i think you can s-off your device by using Revolutionary S-OFF
When I had a ***Security Warning*** with an Incredible S I had the same problem.The only thing I could do (furtunatly for me) was to s-off it using Revolutionary.As long as you have a working Hboot you should be able to S-OFF it like this and then you run an RUU to fully recover your phone.
** I read you may have to repeat 2 or 3 times the proccess to S-Off your device. **
You can check this guide too:
[Guide] Successful S-OFF after (wrong S-ON) brick for ICS/GB ,Downgrade S-ON firmware
Somewhere I have read when you are in ***Security Warning*** you could still be S-OFF but you possibly have to use a gold card to flash a zip from your device.
[TOOL] Goldcard img creator
Thanks both for your replies. (Sorry for delay, I was away from home.)
rzr86 - attached, thank you.
Gatosbil - I don't want S-OFF, I want S-ON! In case you didn't see that, shall I still follow your suggested links?
I will await any further info you can gleen from my attached screenshot.
Thanks again.
Berky99 said:
Thanks both for your replies. (Sorry for delay, I was away from home.)
rzr86 - attached, thank you.
Gatosbil - I don't want S-OFF, I want S-ON! In case you didn't see that, shall I still follow your suggested links?
I will await any further info you can gleen from my attached screenshot.
Thanks again.
Click to expand...
Click to collapse
use the second ruu from post #3 of Gatosbil
it is an ics ruu.exe
Berky99 said:
Thanks both for your replies. (Sorry for delay, I was away from home.)
rzr86 - attached, thank you.
Gatosbil - I don't want S-OFF, I want S-ON! In case you didn't see that, shall I still follow your suggested links?
I will await any further info you can gleen from my attached screenshot.
Thanks again.
Click to expand...
Click to collapse
I know you don't want s-off but in order to make your device working again after wrong s-on (as long as you are in *** Security Warning ***) you have to revert it to s-off again and after you flash the right RUU (probably it will update your eng boot and you will lose s-off) you can revernt it to S-On.Even if the RUU don't revert your device to S-On after a right RUU flash you could do it by using the command fastboot oem writesecureflag 3.
Cheers both. I'm downloading
RUU_Pyramid_LE_hTC_Asia_TW_1.73.709.4_Radio_10.58. 9035.00U_10.15.9035.02_2_release_221625_signed.exe
RUU_PYRAMID_LE_ICS_35_S_HTC_Europe_3.33.401.153_Ra dio_11.76A.3504.00U_11.24A.3504.31_M_release_28100 4_signed.exe
and will let you know how I get on. I think I understand that if this doesn't flash, I'll need to follow one of the processes described, such as make my device fully S-OFF and go from there. Will update you!
Hi guys. The RUU above fails with the same error message. Revolutionary doesn't get past 'waiting for device' with the device in fastboot usb mode - I've tried different USB ports and have installed the recommended HTC 3.0.0.007 Windows driver. Any suggestions from here? I feel I've come too far with this phone to give up on it, it's like a beloved grandmother* to me.
*If my gran was an Android.
Berky99 said:
Hi guys. The RUU above fails with the same error message. Revolutionary doesn't get past 'waiting for device' with the device in fastboot usb mode - I've tried different USB ports and have installed the recommended HTC 3.0.0.007 Windows driver. Any suggestions from here? I feel I've come too far with this phone to give up on it, it's like a beloved grandmother* to me.
*If my gran was an Android.
Click to expand...
Click to collapse
what error msg do you have?
try this one
http://shipped-roms.com/download.ph...0U_11.24A.3504.31_M_release_280871_signed.exe
let's see if you will have success with a ruu for normal sensation
If you are using Windows8 you probably have some problem with drivers (check on device manager / you have to uninstall and clean install HTC 3.0.0.007 drivers).You could also use some linux distribution to execute revolutionary.You have just to download the revolutionary version for linux.
rzr86 said:
what error msg do you have?
try this one
http://shipped-roms.com/download.ph...0U_11.24A.3504.31_M_release_280871_signed.exe
let's see if you will have success with a ruu for normal sensation
Click to expand...
Click to collapse
Thanksrzr86, I tried that one and it fails in the same way (screenshot now attached).
Gatosbil, the PC is s actually ol' WIndows XP! I can't help but read your name as 'The Great Gatsby'.
Okay I will try the Revolutionary on a Linux dist.
Cheers guys, don't go too far!
Berky99 said:
Thanksrzr86, I tried that one and it fails in the same way (screenshot now attached).
Gatosbil, the PC is s actually ol' WIndows XP! I can't help but read your name as 'The Great Gatsby'.
Okay I will try the Revolutionary on a Linux dist.
Cheers guys, don't go too far!
Click to expand...
Click to collapse
yeah man try revolutionary to S-OFF
then change the cid to supercid and use whatever ruu you want
rzr86 said:
yeah man try revolutionary to S-OFF
then the cid to supercid and use whatever ruu you want
Click to expand...
Click to collapse
Cheers, just hope I have better luck doing it on Linux! I guess it is Android's natural home so...
Hi guys, I have Officially Given Up on this!
I tried running Revolutionary from Ubuntu but realised, after following a never-ending series of guides and links that I just don't have the know-how to get Linux to recognise my device ID etc. properly.
Thank you for your help anyway. I'm going to sell this on eBay, don't expect I'll get anything for it but maybe someone somewhere might want it for parts.
Berky99 said:
Hi guys, I have Officially Given Up on this!
I tried running Revolutionary from Ubuntu but realised, after following a never-ending series of guides and links that I just don't have the know-how to get Linux to recognise my device ID etc. properly.
Thank you for your help anyway. I'm going to sell this on eBay, don't expect I'll get anything for it but maybe someone somewhere might want it for parts.
Click to expand...
Click to collapse
did you try it in windows?
rzr86 said:
did you try it in windows?
Click to expand...
Click to collapse
I did mate, extensively. Revolutionary just didn't complete.