Database Info

Back from repair now not sure how to root

Hi all, got my phone back from repair, with the latest orange crap and newest hboot. Ive read that I need to use Juopunutbear, to the s-off, root etc, but I dont like the look of Juopunutbear, (using wire? no chance_. I found the old revolution way much safer and easy to do. How can i still do it like that? Would i need to flash the old orange ruu on the sdcard?

elgrego4 said:
Hi all, got my phone back from repair, with the latest orange crap and newest hboot. Ive read that I need to use Juopunutbear, to the s-off, root etc, but I dont like the look of Juopunutbear. I found the old revolution way much safer and easy to do. How can i still do it like that? Would i need to flash the old orange ruu on the sdcard?
Click to expand...
Click to collapse
You can't run older ruu when SON
To have custom rom's you need to do SOFF via Juopunutbear way or htc dev unlock
The later might not work for you.. As you might got motherboard replaced..
So only solution is JB via temproot
Link in my signature
Sent from my pyramid.. Through blazing fast sonic waves

My repair was only for dust under the screen. so i have the choice of voiding warranty via a piece of wire (visual void), or I virtually tell htc im voiding it? There must be a sneakier way?

elgrego4 said:
so i have the choice of voiding warranty via a piece of wire (visual void), or I virtually tell htc im voiding it? There must be a sneakier way?
Click to expand...
Click to collapse
I believe you do know that.. To turn back SON.. Just one command will do... So it literally means the process is reversible
And I'm afraid that there is no other way to use root/custom rom
Sent from my pyramid.. Through blazing fast sonic waves

I dont actually mean using the exe, i mean pulling the pg file out and putting it on the sd, then it would let me flash back to gingerbread in the bootloader?

I see what you mean about not being able to go backwards. Im stuck now as the dev unlock is no use and I do not have the steady hand to do the wire trick

elgrego4 said:
I see what you mean about not being able to go backwards. Im stuck now as the dev unlock is no use and I do not have the steady hand to do the wire trick
Click to expand...
Click to collapse
You can still flash ROMs while S On.

Its just that I found everything easier with s-off, rooted and supercid

elgrego4 said:
Its just that I found everything easier with s-off, rooted and supercid
Click to expand...
Click to collapse
yes with SOFF ..everything is easy ..but sadly the JB method is the only way for you

Anyone working on a way to do it without the wire?

elgrego4 said:
Anyone working on a way to do it without the wire?
Click to expand...
Click to collapse
idk and i dont think there's gonna be another SOFF process..as now ppl are concentrating on SOFF for ONE series

elgrego4 said:
Anyone working on a way to do it without the wire?
Click to expand...
Click to collapse
I highly doubt it. If you're uncomfortable, you should stick with stock. It's always wise to not do it if you aren't sure of it..

If I had steady hands it wouldnt be a problem, Im a flashaholic, hate stock lol x

Maybe if you read over it a few times you might get a bit more comfortable with it? What I do is even print out the guide so I don't miss a step.this has really helped me in the past when doing new things, I know it may sound silly but its nice to have a printed guide infront of you incase you get in a pinch. This way all the steps are right there in front of you. This is what I do. Just a suggestion. If you DO decide to give it a shot then maybe this might help. I wish you the best in which ever you decide. I just wanted to share this with you because having a printed guide has really helped me out in the past. Good luck and best wishes to you!
Sent from my HTC Sensation 4G using xda premium

Well I decided to give it a go, downloaded everything printed of instructions etc. Ran the temp root file, then it said now run the bear, but after bear connected to my phone it says not rooted? Now I'm stuck.
Sent from my HTC Sensation Z710e using XDA

elgrego4 said:
Well I decided to give it a go, downloaded everything printed of instructions etc. Ran the temp root file, then it said now run the bear, but after bear connected to my phone it says not rooted? Now I'm stuck.
Sent from my HTC Sensation Z710e using XDA
Click to expand...
Click to collapse
not properly rooted ..it seems..
did you got any errors when temp root was run...also make sure htc sync is uninstalled(have the drivers installed too) and the phone should be kept in htc sync mode ...also no hubs or usb 3.0 ports

Thanks for the help, it worked sort of. I completed the s off I said yes to modified hboot, then removed temp root. Then applied root. Problem is the hboot still shows as the normal but with s off and when I try to install recovery it says wrong cid. Nearly there
Sent from my HTC Sensation Z710e using XDA

elgrego4 said:
Thanks for the help, it worked sort of. I completed the s off I said yes to modified hboot, then removed temp root. Then applied root. Problem is the hboot still shows as the normal but with s off and when I try to install recovery it says wrong cid. Nearly there
Sent from my HTC Sensation Z710e using XDA
Click to expand...
Click to collapse
what nearly there ...you are done lol..
just do a supercid
(first note down the actual cid though..just in case ...fastboot getvar cid ..to know cid)
fastboot oem writecid 11111111
EDIT: ohh the hboot is still locked huh ..
then get the pyramic ics one from here http://unlimited.io/hboot-downloads/
and flash it (instructions in the same link)
also after those instructions..to get back to bootloader..the command is "fastboot reboot-bootloader" without quotes

elgrego4 said:
Thanks for the help, it worked sort of. I completed the s off I said yes to modified hboot, then removed temp root. Then applied root. Problem is the hboot still shows as the normal but with s off and when I try to install recovery it says wrong cid. Nearly there
Sent from my HTC Sensation Z710e using XDA
Click to expand...
Click to collapse
If your Hboot still says *locked* you cannot flash a recovery.
Please get the correct Hboot from here & follow flashing instructions: http://unlimited.io/hboot-downloads/
You can then proceed to flashing recovery.

Right done that even though the green line never goes to the end my hboot no longer says locked. I put the recovery zip on the sd, booted into bootloader said yes, completed and rebooted, but no custom recovery there?
Sent from my HTC Sensation Z710e using XDA

To be or not to be...bricked?

Hey guys,
some days ago I tried to get rid of my branded Sensation ROM, hboot 1.27, so I tried the bear method and everything was fine (did root/flash rom several time before, but with 1.17) until...until the wire trick was successful...then there was a driver issue due to my stupidity not to check the adb drivers before flashing...
result -> bricked device! No bootloader anymore, no power, no status LEDs...nothing...I prepared myself and my PC/Phone to unbrick the device. Launched linux and tried to figure out the device node so to be able to proceed with unbrick, no success. Linux didn't show anything. Frustration...now I tried to give it a last last-ditch attempt.........and I couldn't believe it: LED came alive, linux message "new high speed usb device, Product: Android Phone", [sdb] Attached scsi removable disk", phone is booting and I can see something like Android but the screen is black...apart of the top part, where I can see the correct time, battery power (charging!), some status messages.
I'm able to enter recovery and this is where I stopped and need advice: What happend? Is the device bricked? Should I proceed with "unbrick" ? I was close to "The phone is water under the bridge", now I want to avoid any further stupid mistake...I guess the phone is still S-On (***locked*** in recovery) so I think its not that easy to simply flash a new rom?
Thanks to anyone in advance for advice!

It sounds to me you will need to re flash your firmware. Go to the IRC channel and sign in. The people there can walk you through thing.

T-Macgnolia said:
It sounds to me you will need to re flash your firmware. Go to the IRC channel and sign in. The people there can walk you through thing.
Click to expand...
Click to collapse
Thanks I will do that tomorrow, I think it's better to wait until the battery is fully charged (it's close to zero since my s-off attempt some days ago...).
Best regards

hellbot77 said:
Thanks I will do that tomorrow, I think it's better to wait until the battery is fully charged (it's close to zero since my s-off attempt some days ago...).
Best regards
Click to expand...
Click to collapse
After doing some reading today it seems like you need to remove temp root from your device to solve your problem. But still go to the IRC channel as XDA Recognized Contributor ganeshp will be there. It was one of his post that I got this info from, he is on of the most knowledgeable people about using Juopunutbear S-off.

hellbot77 said:
Thanks I will do that tomorrow, I think it's better to wait until the battery is fully charged (it's close to zero since my s-off attempt some days ago...).
Best regards
Click to expand...
Click to collapse
No.. No flashing Firmware... First you need to remove temproot first.. As T-Mac said
Go to my soff guide (link in signature)
And get the soff tool (ignore if you already have it)
Then connect the device with the black screen to pc.. Then run the
remove_temp_root file.. That will remove the temp root.. Then you can boot normal
Sent from my pyramid.. Through blazing fast sonic waves

ganeshp said:
No.. No flashing Firmware... First you need to remove temproot first.. As T-Mac said
Go to my soff guide (link in signature)
And get the soff tool (ignore if you already have it)
Then connect the device with the black screen to pc.. Then run the
remove_temp_root file.. That will remove the temp root.. Then you can boot normal
Sent from my pyramid.. Through blazing fast sonic waves
Click to expand...
Click to collapse
Wohooo, Phone is online again
Thanks Thanks Thanks!

Stuck on HTC screen, can't unlock bootloader, can't root from Fastboot

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

[Q] phone down for a week now

ok like the title says ive been messing with this thing for a week now and im getting to the point im about to smash it with a hammer
its stuck in a boot loop and i have no backup to load apparently. it was rooted when i got it and my roomate messed it up while i was at work im not sure how or what was done but no matter what i try to do i cant get it out of this loop. im not familiar with android at all ive been reading and searching but i cant find anything helpful ive tried to ruu a few times not really knowing which files to use i finally found out that the radio needed to be the same found a matching file but still no luck i know im gonna get flamed for being so uneducated in this matter but i have indeed searched and i feel im left with no other option then to ask for assistance here
i can get to the boot loader and im just going to type down exactly what i see on it although i dont really know what any of it means
***tampered***
***unlocked***
evita pvt ship s-on rl
hboot-1.14.0002
radio-0.19as.32.09.11_2
opendsp-v29.1..0.45.0622
emmc-boot
jun 11 2012,14:36:28
fastboot usb
vol up
vol down
power
fastboot
recovery
factory reset
clear storage
simlock
image crc
power down
im in need of a thourough stepo by step instruction on how to fix this thing i dont care if its by means of a custom rom stock rom whatevers easiest. i know how to utilize fastboot with instruction and ive changed back and forth between cwm and twrp but no matter how many tuts i follow i always end up in a loop and im not sure why again i apologize for being such a noob but ive come to realize that this forum is the best at fixing stupid problems like mine fairly quickly
thanks in advance for your help....

Alright, is there a custom recovery installed on it? Go to recovery from bootloader menu and it it says TWRP or CWM then there is.
Edit: Also, I'm assuming you have no knowledge of adb and fastboot commands? Because you might need to learn. And did you try this ruu? It's for your firmware version. http://forum.xda-developers.com/showthread.php?t=1814217

RollTribe said:
Alright, is there a custom recovery installed on it? Go to recovery from bootloader menu and it it says TWRP or CWM then there is.
Click to expand...
Click to collapse
yes i can get to the custom recovery but it seemes like everytime i try to go into it it falls back into a loop unless i flash it and then imiediatly go into it but right now i have twrp on here

im downloading that one now and ill give it a try i really hope this helps. im not to familiar with fastboot but i with instruction from someone who is im sure i can figure it out ya know

frankthebunny said:
yes i can get to the custom recovery but it seemes like everytime i try to go into it it falls back into a loop unless i flash it and then imiediatly go into it but right now i have twrp on here
Click to expand...
Click to collapse
frankthebunny said:
im downloading that one now and ill give it a try i really hope this helps. im not to familiar with fastboot but i with instruction from someone who is im sure i can figure it out ya know
Click to expand...
Click to collapse
Alright, so I'm assuming the problem is there is no ROM on the phone or someone did factory reset in bootloader. So if the ruu helps, great (it should). If not, then I'm sure we'll figure it out.

thats what ive been assuming as well im really hoping this works out and i do appreciate the help ive been trying to figure out for hours how to find the correct ruu that i need.
now just to be clear there isnt any kind of preperation or anything for this right? im just going to go into the bootloader and make sure the usb is connected and recognized and the open the file on my pc and let it do its thing...
i got about 20 minutes left on this download (my internet connection is poop out here) and ill let you know how it works out
thanks again :good:

frankthebunny said:
thats what ive been assuming as well im really hoping this works out and i do appreciate the help ive been trying to figure out for hours how to find the correct ruu that i need.
now just to be clear there isnt any kind of preperation or anything for this right? im just going to go into the bootloader and make sure the usb is connected and recognized and the open the file on my pc and let it do its thing...
i got about 20 minutes left on this download (my internet connection is poop out here) and ill let you know how it works out
thanks again :good:
Click to expand...
Click to collapse
Yup. Since you're on an older hboot there's no preparation needed. I'm assuming you don't really want to get into all this rooting stuff and just want a working phone? If you want help with rooting, come back here when the ruu is done, but if you like it stock, then you should be good to go :beer:

Ps take care not to flash 3.18 ruu or ota without advise. You are likely supercid and are s-on, a bad combination.
Once 2.20 is installed come back here before installing 3.18 even if the phone offers it to you.
Sent from my HTC One XL using xda app-developers app

actually i would like to root it after i get it all fixed and put a custom rom on it and what not. like i said earlier i can follow instructions this was just a difficult spot to start from ya know.

twistedddx said:
Ps take care not to flash 3.18 ruu or ota without advise. You are likely supercid and are s-on, a bad combination.
Once 2.20 is installed come back here before installing 3.18 even if the phone offers it to you.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Hopefully he see's this post. If his phone isn't from AT&T Shouldn't be Scid

right on ill do that. is there anything else i should be downloding now to prepare for what ever it is i need to do to protect my phone from messing up again?

exad said:
Hopefully he see's this post. If his phone isn't from AT&T Shouldn't be Scid
Click to expand...
Click to collapse
yeah it is an at&t phone. at least it says on the top of it however im using straight talk t-mobile i believe.
will i need to root it again in order to utilize the t-mobile carrier?

No need to root for your carrier.
But you will need to root again to install other roms.
So is this phone back up and running again yet?
Sent from my HTC One XL using xda app-developers app

damn it didnt work.
error [155]: unkown error
the rom update utility cannot update your android phone
please get the correct rom update utility and try again
this is what ive run into every time ive tried this

frankthebunny said:
damn it didnt work.
error [155]: unkown error
the rom update utility cannot update your android phone
please get the correct rom update utility and try again
this is what ive run into every time ive tried this
Click to expand...
Click to collapse
What ruu?
Did you relock the bootloader?

no i didnt relock the bootloader i didnt realize i needed to. i asked if i needed to prep in anyway before i ran it and i used the ruu that was recommended to me in the beggining of the thread...
if relocking the bootloader will solve my problem how do i go about doing that...
heres the name of the file
htc_one_x_RUU_2.20.502.7_att_us_08022012

frankthebunny said:
no i didnt relock the bootloader i didnt realize i needed to. i asked if i needed to prep in anyway before i ran it and i used the ruu that was recommended to me in the beggining of the thread...
if relocking the bootloader will solve my problem how do i go about doing that...
Click to expand...
Click to collapse
First do :
fastboot oem readcid and tell me what it says
if it's CWS__001 then do:
fastboot oem lock
And chill, your phone will work when I'm done with you.

it say
cid: 11111111

frankthebunny said:
it say
cid: 11111111
Click to expand...
Click to collapse
ok hopefully since it didn't say CWS__001 you didn't use the lock command.
do:
fastboot oem writecid CWS__001 (be sure to note there are two "_")
then do
fastboot oem readcid
It should now say CWS__001
please confirm

nice ok ive changed it now to CWS__001

[Q] HTC Sensation totally stock in boot loop

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