Database Info

Hboot 2.00.0002 ** S ON ** NOT rooted STUCK! what to do?

hello guys! i am completely clueless now... ive been wandering around this forum for more than 4 hours. and i just can't find any help.
my situation is as following:
i tried to unroot my desire s to get the warranty back with this guide: http://forum.xda-developers.com/showthread.php?t=1460713
at some point i accidently flashed hboot 2.00.0002. than i was stuck with the ruu update's error: 140..
i have a goldcard but it just wouldn't let me downgrade to this ruu: RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed i am pretty sure that this is the right one...
i got my desire s at an o2 shop here in germany and it comes unbranded.
i tried so many guides, but i can't get out of this misery.
although i was able to get to the recovery (4ext touch), unlocked via htcdev, but unrooted and S-ON.
now my phone boots and gets stock at the ics fallout "htc one" bootscreen.
is there a way to get my desire s to be stock again?

Wierd you can access recovery!!!
Well All I can say is that never try to downgrade from any ics rom to stock ginger bread rom without downgradin your misc version mate.And unfortunately, i think you have to wait for official stock ICS rom.

UmairAhmad said:
Wierd you can access recovery!!!
Well All I can say is that never try to downgrade from any ics rom to stock ginger bread rom without downgradin your misc version mate.And unfortunately, i think you have to wait for official stock ICS rom.
Click to expand...
Click to collapse
yea, very wierd, isn't it?
i tried to fake a misc-version downgrade via adb cmd and i was able to do it once, but it was still higher than the ruu version.

WhatWouldJesusDo said:
yea, very wierd, isn't it?
i tried to fake a misc-version downgrade via adb cmd and i was able to do it once, but it was still higher than the ruu version.
Click to expand...
Click to collapse
Actually I myself encountered this problem using exactly the same guide but somehow i was able to find the higher RUU which did the trick for me. Try to find some higher RUU.
Otherwise go for jtag or xtc clip if u can't wait..
BTW update is just around the corner if you dont want to apply hardware methods

UmairAhmad said:
Actually I myself encountered this problem using exactly the same guide but somehow i was able to find the higher RUU which did the trick for me. Try to find some higher RUU.
Otherwise go for jtag or xtc clip if u can't wait..
BTW update is just around the corner if you dont want to apply hardware methods
Click to expand...
Click to collapse
that's great news! hope is rising
hardware fixes are no option for me, yet. the hole point is to get my phone replaced, so i don't want to eff around too much.
you probably don't know the ruu file anymore, do you?
thanks again.

WhatWouldJesusDo said:
that's great news! hope is rising
hardware fixes are no option for me, yet. the hole point is to get my phone replaced, so i don't want to eff around too much.
you probably don't know the ruu file anymore, do you?
thanks again.
Click to expand...
Click to collapse
RUU_Saga_S_hTC_Asia_India_2.15.720.3_Radio_20.4801 .30.0822U_3822.10.08.04_M_release_226809_signed.exe
As my phone was shipped for India..
I very much doubted that it will help even!!!!
Try to look out for OS 2.3.5 with sense 3.0 for your region...

somehow i managed to install a ruu with a miscversion downgrade.
i did the same thing "nenad_l" did here: http://forum.xda-developers.com/showthread.php?t=1604255
and now i am at 68% completion. i'll report when it's done.
___
it's done!
i appreciate your support umair! thank's a lot!

WhatWouldJesusDo said:
somehow i managed to install a ruu with a miscversion downgrade.
i did the same thing "nenad_l" did here: http://forum.xda-developers.com/showthread.php?t=1604255
and now i am at 68% completion. i'll report when it's done.
___
it's done!
i appreciate your support umair! thank's a lot!
Click to expand...
Click to collapse
Dats nice to hear it

Having unlocked the bootloader and having a functional custom recovery, all you had to do was to run misc_version script from recovery, reboot to bootloader, lock it and proceed with RUU flash. Nothing more.

Got your same problem. I was stuck at the bootloader because I had my desire s unlocked with HTCdev.com. Relocked it and flashed with a previous RUU like 1.47... it worked and then flashed hboot and radio...

u shd hv just unroot n den lock ur bootloader with the token provided when u did htc dev unlock
run d misc ver. changer n zergrush
and den run RUU ...

[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] HOX is dead Please HELP!

Hi, i updated my htc one x at&t through HTC Manager with RUU Stock Rom. Everything was going fine and i don't know wth happen!!! Now my HOX wont power on after upgrade!! If i plug it to computer this one recognize the phone but htc sync manager doesn´t. PLease help me if you need more info please ask for it!! thank you very much!

Have you tried flashing stock?
Sent from that one guy with the cool phone
If I helped you hit that Thanks button!

ayo234 said:
Have you tried flashing stock?
Sent from that one guy with the cool phone
If I helped you hit that Thanks button!
Click to expand...
Click to collapse
how can i do that? i can't get into bootloader or recovery to do it! thanks for your reply

Were you son or soff? Stock or rooted?
Sent from my HTC One XL using xda app-developers app

exactly same problem here... I think this is a brick.... soft or hard i cant tell. I am trying to use a home made jig still no progress, may be i connected it badly.
Still got faith b4 opening this beast/beauty... I'll post if any advance...

There's no such thing as a soft brick, it's either bricked or it's not.
Sent from my Evita

Thanx got that timmaaa....
Exad mine was at
S-ON
ROOTED
SuperCID

Qnatz said:
Thanx got that timmaaa....
Exad mine was at
S-ON
ROOTED
SuperCID
Click to expand...
Click to collapse
Sorry to say this but your bricked
Running RUU while S-ON = Brick.

yap.... that's the beauty...
on a pc when flashing cmos there are
jumpers/pins if connected they wipe cmos
is this similar with the htc one x board..... maybe it would work.
has anyone done this....

Kinotsu said:
Sorry to say this but your bricked
Running RUU while S-ON = Brick.
Click to expand...
Click to collapse
Hi, i'm
S-ON
Rooted (but i unroot before installing stock rom) and,
SuperCID
HBOOT 1.14
I really don't understand. Am i in the same situation? why do this happen to a phone? there must be a way to solve this kind of problems. I downloaded the stock rom (.exe file) from htc webpage at at&t htc one x update tutorial. why if htx is letting someone downloading it the phone can get bricked? thank you for your answers

germanjo said:
Hi, i'm
S-ON
Rooted (but i unroot before installing stock rom) and,
SuperCID
HBOOT 1.14
I really don't understand. Am i in the same situation? why do this happen to a phone? there must be a way to solve this kind of problems. I downloaded the stock rom (.exe file) from htc webpage at at&t htc one x update tutorial. why if htx is letting someone downloading it the phone can get bricked? thank you for your answers
Click to expand...
Click to collapse
I unfortunately had the same issue, The SuperCID & S-ON come into play. You would want to do the JTAG revival, your only hope. Your SuperCID indicates the modification done, which primarily causes this.

humdingor said:
I unfortunately had the same issue, The SuperCID & S-ON come into play. You would want to do the JTAG revival, your only hope. Your SuperCID indicates the modification done, which primarily causes this.
Click to expand...
Click to collapse
Would you recomend riff jtag? i know it is very expensive but i will look for some one in my city who has it. Any other idea of how to solve it? any idea if i can build jtag on my own. i'm good with electronics so i think i can do it if i get the circuit diagram. thank you

To be honest you'd be better off getting someone who knows what they're doing to do it for you. HTC have nothing to do with the RUU bricking phones, it's nit a fault with the RUU. It's because it looks for certain criteria wharf it runs and if you don't have those criteria it goes bad. It's up to the users to educate themselves about what happens when they've modified their phones.
Sent from my Evita

germanjo said:
Hi, i'm
S-ON
Rooted (but i unroot before installing stock rom) and,
SuperCID
HBOOT 1.14
I really don't understand. Am i in the same situation? why do this happen to a phone? there must be a way to solve this kind of problems. I downloaded the stock rom (.exe file) from htc webpage at at&t htc one x update tutorial. why if htx is letting someone downloading it the phone can get bricked? thank you for your answers
Click to expand...
Click to collapse
The brick is due to SuperCID, which is a mod/hack that you did. HTC is not responsible for that. RUU with SuperCID typically shouldn't result in a brick. But on the other hand, you should always do thorough research before applying any stock updates (RUU or OTA) to a modded phone.
If there was a way to come back form this short of JTAG, it hasn't been found yet. And its been worked on by some knowledgeable and skilled folks here.

germanjo said:
Would you recomend riff jtag? i know it is very expensive but i will look for some one in my city who has it. Any other idea of how to solve it? any idea if i can build jtag on my own. i'm good with electronics so i think i can do it if i get the circuit diagram. thank you
Click to expand...
Click to collapse
I've messed up my phone twice & was rescued through JTAG by MobileVideotech. The service is good, although the AT&T ROM that they loaded kept my phone rebooting frequently. However, I have seen that issue ever since I came on custom ROMs. You can give it a try if you wish.

[Q] HTC One (m7) need help..

Hey I have an HTC One I let my friend try to root and he screwed it up and didn't tell me what happened... I'm a little pissed off but in bootloader it says unlocked and tampered. It didn't have an OS when he gave it back to me and I've literally spent this past week in my free time trying to fix it and nothing. I got a viper rom running but the touch screen doesn't work so i would really like to take this experience and learn not to let other people mess with my phone and also not mess with it. Do you think i could get help restoring it to stock? Ill give any information you need just name it. Thanks!

Jerod U. said:
Hey I have an HTC One I let my friend try to root and he screwed it up and didn't tell me what happened... I'm a little pissed off but in bootloader it says unlocked and tampered. It didn't have an OS when he gave it back to me and I've literally spent this past week in my free time trying to fix it and nothing. I got a viper rom running but the touch screen doesn't work so i would really like to take this experience and learn not to let other people mess with my phone and also not mess with it. Do you think i could get help restoring it to stock? Ill give any information you need just name it. Thanks!
Click to expand...
Click to collapse
Use the matching RUU to get it back to stock. Or flash a matching firmware.zip and install a custom rom again

LS.xD said:
Use the matching RUU to get it back to stock. Or flash a matching firmware.zip and install a custom rom again
Click to expand...
Click to collapse
Well the thing is I can't find my matching RUU and I really feel like a complete noob right now. Thanks for the info but do you think you could help me find it?

Jerod U. said:
Well the thing is I can't find my matching RUU and I really feel like a complete noob right now. Thanks for the info but do you think you could help me find it?
Click to expand...
Click to collapse
Received my pm?

safe ruu to get me to hboot 2.15

bootloader currently showing....
Bootloader info:
*** LOCKED ***
VLE PVT SHIP S-ON RL
HBOOT-1.14.005
RaDIO-1.13.50.05.25
OpenDSP-v29.1.0.45.0622
eMMC-boot
Nov 21 2012,12:17:41
Software Number
2.35.531.12 710RD
Android
4.04
much thanks

the 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 found here is the latest one released for unbranded devices afaik.
alltho itll downgrade your radio as it seems...

Dolour said:
the 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 found here is the latest one released for unbranded devices afaik.
alltho itll downgrade your radio as it seems...
Click to expand...
Click to collapse
That one won't work. He has a T-Mobile US phone (SKU 531) and is a S-ON user. The RUU you linked is for the SKU 401. You can't change your SKU with S-ON.
@20twins10: Try this RUU. It should set your phone back to stock. You can update it afterwards to the latest version by using the OTA function in "settings>about". If the RUU doesn't work as expected you should turn off your internet connection, your firewall and you antivirus software, boot your phone to fastboot mode and try again.

Flippy498 said:
That one won't work. He has a T-Mobile US phone (SKU 531) and is a S-ON user. The RUU you linked is for the SKU 401. You can't change your SKU with S-ON.
Click to expand...
Click to collapse
well, the site linked allso contains the TMO ruus available, didnt figure from the bootloader info its a branded device.

Dolour said:
well, the site linked allso contains the TMO ruus available, didnt figure from the bootloader info its a branded device.
Click to expand...
Click to collapse
I know that. Guess where I found the TMOUS ruu.

Flippy498 said:
I know that. Guess where I found the TMOUS ruu.
Click to expand...
Click to collapse
well gj then i suppose.
a word of warning tho: updates messing with the hboot version seem to have a tendency to bork your mmcblk0p20, causing you to end up on edge only(im trying for weeks now,
to get my hands on a WORKING image for unbranded eu devices, without any luck).
so make sure to pull a backup to be able to revert!

Dolour said:
well gj then i suppose.
a word of warning tho: updates messing with the hboot version seem to have a tendency to bork your mmcblk0p20, causing you to end up on edge only(im trying for weeks now,
to get my hands on a WORKING image for unbranded eu devices, without any luck).
so make sure to pull a backup to be able to revert!
Click to expand...
Click to collapse
I actually never faced such a problem. And I upgraded and downgraded my One S's fimware a lot during the last three years. (But I think this is going too much off topic. So let's leave it at that. )
@20twins10: I just noticed that your bootloader is still locked. (I guess I have missed that info earlier.) So your phone seems to be untouched in terms of bootloader unlocking and rooting. That actually makes me wonder why you don't use the OTA function in settings>about?

Flippy498 said:
I actually never faced such a problem. And I upgraded and downgraded my One S's fimware a lot during the last three years. (But I think this is going too much off topic. So let's leave it at that. )
Click to expand...
Click to collapse
well, considering the 30+ pages long thread on this forum, regarding the issue, i wouldnt exactly call it OT, just bc youve been lucky until now.
btw, you dont, by "chance" *cough*, have one of the above mentioned mmcblk0p20's for unbranded, european devices handy(or could dd one if you find a couple minz)?

Dolour said:
well, considering the 30+ pages long thread on this forum, regarding the issue, i wouldnt exactly call it OT, just bc youve been lucky until now.
btw, you dont, by "chance" *cough*, have one of the above mentioned mmcblk0p20's for unbranded, european devices handy(or could dd one if you find a couple minz)?
Click to expand...
Click to collapse
But as far as I know the problems arose after people S-OFFed their phones and/or downgraded their hboot using a ruu. (Haven't checked that thread for over a year.) And neither of these processes has anything to do with this topic. So let's continue this discussion via PM.

Flippy498 said:
But as far as I know the problems arose after people S-OFFed their phones and/or downgraded their hboot using a ruu. (Haven't checked that thread for over a year.) And neither of these processes has anything to do with this topic. So let's continue this discussion via PM.
Click to expand...
Click to collapse
well it happened to me after doing a simple factory reset, no s-off, not even root, it definetly isnt related to hboot 2.16 or s-offing at all.
therefore i consider the suggestion of backing everything up before doing any changes to the OS pretty important, and totally on-topic.

hey guys thanks for all the responses. i need to get some time to sit and read them. i've been busy with work and school and was not able to get time back to xda till now.. just a quick update: i was able to adjust my driver files and get fastboot to recogonize my phone, i did get my bootloader unlocked and twrp flashed.. as far back as i can remember ive never used OTA's and always go about it . i guess ive always come to the conclusion an ota dl will get you on the hot list if you are out of warranty or conretact type deal..
but either way.. there is progress on my end. my wife runs a couple apps that require 5.0 or better so i'd like to get that to work for her.. she'll ***** when she needs to re-enter her pw's though.. cant wint.. much thanks..

20twins10 said:
hey guys thanks for all the responses. i need to get some time to sit and read them. i've been busy with work and school and was not able to get time back to xda till now.. just a quick update: i was able to adjust my driver files and get fastboot to recogonize my phone, i did get my bootloader unlocked and twrp flashed.. as far back as i can remember ive never used OTA's and always go about it . i guess ive always come to the conclusion an ota dl will get you on the hot list if you are out of warranty or conretact type deal..
but either way.. there is progress on my end. my wife runs a couple apps that require 5.0 or better so i'd like to get that to work for her.. she'll ***** when she needs to re-enter her pw's though.. cant wint.. much thanks..
Click to expand...
Click to collapse
I don't know what you mean with "getting on the hot list". (Sorry English isn't my mother tongue.)
Actually the unlock process and the flashing of TWRP was completely unnecessary. Before you should start flashing any custom files you need to upgrade to the latest firmware. Many of the android 5 custom roms won't work if your firmware is too old. Just flash the RUU and then install the OTAs. (Since you flashed TWRP you now must use the RUU whereas it's been optional at the point where you started this thread.)