Database Info

how to S-ON HTC wildfire after revolutionary!

HI everyone. i have started this thread as i didnt know what to do when i first had to send my wildfire back for repairs. first download the attatched zip. unzip to desktop and make sure u have got the drivers for your bootloader interface already installed. to do this you will need just two things. the zip you have just downloaded and the HBOOT which i included inside the ziped file. once extracted run the java file named S-ON.jar and plug your phone in and turn on fastboot. once connected make sure you click on check connection. once you have done that you should see your serial number appear. okay your ready to go. look for the first tab and click on it. then click on HBOOT/SPL. locate the HBOOT file you inzipped with the S-ON tool and then click it. once done just click on flash HBOOT/SPL. once done you will see it says FLASH HBOOT/SPL/SUCCESS. thanks for takuing time to look at my GUIDE and i hope it helps you. just remember one thing only flash the new HBOOT after you have installed the RUU which is android 2.1 update 1 so you can root again.

thanks for posting this, gonna try it now since I have to send my wildfire in for repair..

no problem if you have any trouble let me know and ill help you gain s-on

Hmm well it didn't work, so just sent it in as it was. I replaced the custom recovery and the custom rom with stock from an RUU, I hope thats enough.
To gain S-ON I also tried the suggestions from a few other posts, I guess the problem is that I didn't gain S-OFF by software but by using an XTC-Clip. The fastboot command to flash the hboot always returned something like remotly denied or simular

kaefert said:
Hmm well it didn't work, so just sent it in as it was. I replaced the custom recovery and the custom rom with stock from an RUU, I hope thats enough.
To gain S-ON I also tried the suggestions from a few other posts, I guess the problem is that I didn't gain S-OFF by software but by using an XTC-Clip. The fastboot command to flash the hboot always returned something like remotly denied or simular
Click to expand...
Click to collapse
this will not work with xtc clip i have 1 other way tho. please try this.
go into you start menu click RUN the type cmd in the dialog box. when you have the cmd up type C:\fastboot>fastboot oem mb 9C068490 1 30 then it will say okay. then open the s-on tool then try to flash the HBOOT. let me know if you have anymore problems. but this way shud work for you
they will not accept it as they just have to go into the HBOOT menu and they will be able to see it is s-off. and they will send it back as it is and wont carrie out any sort of repairs on it as you have hacked the phone and comprimised the security software

hmm, well we will see. I will post as soon as I get an response. That command "fastboot oem mb 9C068490 1 30" always threw an error and somewhere I read that maximum 3 parameters are allowed

kaefert said:
hmm, well we will see. I will post as soon as I get an response. That command "fastboot oem mb 9C068490 1 30" always threw an error and somewhere I read that maximum 3 parameters are allowed
Click to expand...
Click to collapse
okay no worries. if they wont repair it. then get back to me and ill cook somthing up and get you back to s-on. this is the trouble when gaining s-off with a xtc clip. its a pain to get back to s-on again lol but good luck anyways

Thanks for the moral support, I hope they will repair it...
Well back then I had no chance, my Wildfire was delivered to me with hboot 1.01.001 back in the time where there was no software S-OFF method for 1.01.001 and up, so I found myself a shop that had an XTC-Clip and invested 10€ on him

Okey! So they repaired it although it had S-OFF done by XTC-Clip. Got it back yesterday, and the phone earpeace is working again

kaefert said:
Okey! So they repaired it although it had S-OFF done by XTC-Clip. Got it back yesterday, and the phone earpeace is working again
Click to expand...
Click to collapse
Great news for you mate im glad they sorted it out for you. and your very lucky as they sent mine back twice for being s-off lol.

lol, where are you from? and where did they send your device? Im from austria and they sent my device to slovakia and they gave me a slovenian report of what they did so I had to use google translate to understand it

[Q] can someone help me?

i just bought a sensation, and now i'm a previous HD2 owner. so i'm not a noob, i hope.
so...unlocking bootloader and rooting and s-Off...which one to follow? the official on hTCDev website or the revolutionary way?! any difference between those?
please someone clarify some things, as i just became a sensation user, i have no idea about anything of these since HD2 is way different as i noticed and since there are a lot of info on the net, i don't wanna get into things i shouldn't.
i got a second hand sensation but it's still on factory default with android 2.3.4 and sense 3.0
really any help is greatly appreciated

If your HBOOT is supported by Revolutionary ALWAYS use that one...
I dont like HTCdev - It should only be used if your HBOOT is unsupported
Just have a good read through all the noob guides. Be sure of what you're doing before attempting anything...
I cant stress how important it is to follow the guides 100%

azzledazzle said:
If your HBOOT is supported by Revolutionary ALWAYS use that one...
I dont like HTCdev - It should only be used if your HBOOT is unsupported
Just have a good read through all the noob guides. Be sure of what you're doing before attempting anything...
I cant stress how important it is to follow the guides 100%
Click to expand...
Click to collapse
okay great, that was so helpful! you're really a good Q&A contributor, i don't know were i would have learned that anywhere else!
i'm off to check if my Hboot is supported.
thanks button clicked, cheers!

cant help but detect some sarcasm there

azzledazzle said:
cant help but detect some sarcasm there
Click to expand...
Click to collapse
eh? why would you say that?!

Maybe i misinterpreted it !
who knows ?

azzledazzle said:
cant help but detect some sarcasm there
Click to expand...
Click to collapse
no really i searched like two hours and on youtube but i couldn't know what's the difference between the official tool and the one called revolutionary...why you felt sarcasm in my words is beyond me...sorry anyway...

haha maybe its just me..
Anyway, Revolutionary IS THEE best tool for S-OFF... providing your HBOOT is supported of course. Did you check to see if its supported ?

if you got hboot 1.18.0000 please use revolutionary method to unlock your boot loader. If you unlock your bootloader with htcdev method you will unlock somd parts of the hboot. not every thing. then you cant flash a custom kernel because it already locked boot.img and cant write a new file over it. thne you will get wifi,bluetooth problems. so unlock your bootloader with revolutionary.
Sent from my HTC Sensation Z710e using XDA

azzledazzle said:
haha maybe its just me..
Anyway, Revolutionary IS THEE best tool for S-OFF... providing your HBOOT is supported of course. Did you check to see if its supported ?
Click to expand...
Click to collapse
yep, it's supported i will do it tonight before bed and sleep at ease having it unlocked ^.^

namila007 said:
if you got hboot 1.18.0000 please use revolutionary method to unlock your boot loader. If you unlock your bootloader with htcdev method you will unlock somd parts of the hboot. not every thing. then you cant flash a custom kernel because it already locked boot.img and cant write a new file over it. thne you will get wifi,bluetooth problems. so unlock your bootloader with revolutionary.
Sent from my HTC Sensation Z710e using XDA
Click to expand...
Click to collapse
i appreciate your concern i'll certainly use revolutionary.

arabology said:
i appreciate your concern i'll certainly use revolutionary.
Click to expand...
Click to collapse
great
Sent from my HTC Sensation Z710e using XDA

arabology said:
yep, it's supported i will do it tonight before bed and sleep at ease having it unlocked ^.^
Click to expand...
Click to collapse
Happing rooting...
Just curious, how will rooting (& thereby voiding the warranty) bring you some peace... For most people, it would bring anxiety (& bad dreams)...
Wait a minute, you said unlocking, i hope you didn't mean sim-unlock instead of rooting?
Cheers, Jp

japinder said:
Happing rooting...
Just curious, how will rooting (& thereby voiding the warranty) bring you some peace... For most people, it would bring anxiety (& bad dreams)...
Wait a minute, you said unlocking, i hope you didn't mean sim-unlock instead of rooting?
Cheers, Jp
Click to expand...
Click to collapse
hehe yeah. no my phone is not sim locked

it didn't work!!
i tried it and my HBOOT is 1.18.0000 revolutionary supports it! i filled up everything correctly on the site and got a beta key. on revolutionary.exe, it ditects my phone just fine, after that i copy/paste the beta key. it starts but after a minute is gives "failed to get root "
help?

Did you get S-OFF via revolutionary ??
what does your HBOOT say now ??

azzledazzle said:
Did you get S-OFF via revolutionary ??
what does your HBOOT say now ??
Click to expand...
Click to collapse
thanks for your reply. nothing changed in my after i tried revolutionary. HBOOT is still 1.18.0000

and it still says S-ON ??
If so try it again Copy the beta key into notepad and enter it into revolutionary manually.
then tell me what happens, also, link me to the guide you are / was following, and what step you got to before this problem occurred

azzledazzle said:
and it still says S-ON ??
If so try it again Copy the beta key into notepad and enter it into revolutionary manually.
then tell me what happens, also, link me to the guide you are / was following, and what step you got to before this problem occurred
Click to expand...
Click to collapse
yeah it still rights LOCKED up with pinkish red highlight and under it S-ON RL
i already tried like 5-6 times...nothing worked...i installed drivers, unticked fast boot on phone, and ticks usb debugging...
i followed this method: http://forum.xda-developers.com/showthread.php?t=1192300

oh i got the error on step 1 in revolutionary...

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] CID # for AT&T U.S.

I currently have S-ON with SuperCID, and I'm trying to get S-OFF with stock AT&T CID. I've heard that it's a fairly simple process to change the CID ("fastboot oem writecid HTC_001"), but HTC_001 is for the unbranded international version, and I'm having a hard time finding the code for the AT&T version, which I suppose I failed to write down before overwriting with SuperCID. Hope someone can help? Also, should I be s-ON or S-OFF to write the CID?

bikeracer4487 said:
I currently have S-ON with SuperCID, and I'm trying to get S-OFF with stock AT&T CID. I've heard that it's a fairly simple process to change the CID ("fastboot oem writecid HTC_001"), but HTC_001 is for the unbranded international version, and I'm having a hard time finding the code for the AT&T version, which I suppose I failed to write down before overwriting with SuperCID. Hope someone can help? Also, should I be s-ON or S-OFF to write the CID?
Click to expand...
Click to collapse
You can only S-OFF with super CID 11111111
After S-OFF you can write it back to the default of CWS__001 for AT&T, but there is no advantage to doing so. You can do whatever you like regardless of what your CID is after S-OFF. I set mine to R00T_001 after for example. (must be 8 characters)
Just noticed your other thread and see why you want the default CID. If you're selling it, make sure your cid is currently 11111111 then S-OFF then you can use that command to change the cid to default. If you're going to sell it, after S-OFF, I'd just format the SD card and run the 3.18 RUU and then power it off after so the person you sell it to will have a fresh start.

exad said:
After S-OFF you can write it back to the default of CWS__001 for AT&T, but there is no advantage to doing so.
Click to expand...
Click to collapse
From what I understand, CID can be changed once from SuperCID to something else, without s-off.
The OP wants to sell his phone, per this thread: http://forum.xda-developers.com/showthread.php?t=2251955
I suggested either changing from SuperCID, or achieving S-off, so the next owner doesn't unintentionally brick the phone by trying to install the 3.18 OTA or RUU (since he is currently SuperCID and S-on).
Not sure why he started this thread, I would have just answered the AT&T CID question in the other thread.

redpoint73 said:
From what I understand, CID can be changed once from SuperCID to something else, without s-off.
The OP wants to sell his phone, per this thread: http://forum.xda-developers.com/showthread.php?t=2251955
I suggested either changing from SuperCID, or achieving S-off, so the next owner doesn't unintentionally brick the phone by trying to install the 3.18 OTA or RUU (since he is currently SuperCID and S-on).
Not sure why he started this thread, I would have just answered the AT&T CID question in the other thread.
Click to expand...
Click to collapse
Sorry, the other thread was started because I couldn't turn my phone on, and was becoming unrelated to original post, thought it would be prudent to create a new thread. Really appreciate your help though.

Just a heads up, I bricked my first TELUS HOXL eventhough I had changed my CID back to the default prior to RUUing. May have been a fluke but yeah do with this info what you will.

UGGGHHH, this is getting frustrating...had to root the phone to get to S-OFF, so I used the X-FACTOR exploit, but when I tried to get S-OFF (http://forum.xda-developers.com/showthread.php?t=2155071) I got the first 2 adb command off but the second one said it couldn't find 'su' so I assumed to root hadn't worked. So I decided it would just be easiest to go back to CyanogenMod and start the whole process over. Only when I tried to unlock the bootloader again, I found that it wouldn't stick. It would SAY it was successful and reboot the phone, but when I would reboot to bootloader it would say "relocked". SO decided to run an RUU, only now the hboot was up to 2.14 from the S-OFF flashing, so I decided to run the 3.15 RUU instead of the 2.20, and that SEEMED to work fine, except that now I'm right back to where I was with not being able to turn the phone on, and I tried my previous trick of the Vol Down + Power...
EDIT: Aaaand, no LED when charging...

bikeracer4487 said:
UGGGHHH, this is getting frustrating...had to root the phone to get to S-OFF, so I used the X-FACTOR exploit, but when I tried to get S-OFF (http://forum.xda-developers.com/showthread.php?t=2155071) I got the first 2 adb command off but the second one said it couldn't find 'su' so I assumed to root hadn't worked. So I decided it would just be easiest to go back to CyanogenMod and start the whole process over. Only when I tried to unlock the bootloader again, I found that it wouldn't stick. It would SAY it was successful and reboot the phone, but when I would reboot to bootloader it would say "relocked". SO decided to run an RUU, only now the hboot was up to 2.14 from the S-OFF flashing, so I decided to run the 3.15 RUU instead of the 2.20, and that SEEMED to work fine, except that now I'm right back to where I was with not being able to turn the phone on, and I tried my previous trick of the Vol Down + Power...
EDIT: Aaaand, no LED when charging...
Click to expand...
Click to collapse
That's a brick. Do you have a linux boot disk? if not, create a linux boot disk or usb and then try the unbrick evita thread. If you can get past step 3, you should be able to unbrick. if not, Sorry to hear.

exad said:
That's a brick. Do you have a linux boot disk? if not, create a linux boot disk or usb and then try the unbrick evita thread. If you can get past step 3, you should be able to unbrick. if not, Sorry to hear.
Click to expand...
Click to collapse
Hm, not having much luck so far, but I AM seeing QHSUSB_DLOAD in the device manager...

bikeracer4487 said:
Hm, not having much luck so far, but I AM seeing QHSUSB_DLOAD in the device manager...
Click to expand...
Click to collapse
Yeah that bid brick I believe. Get live USB stick running Linux. All you need is small USB stick like 2 or 4 GB. Then download pen drive USB image creator. And run Linux from that. Then exad mentioned a thread to look into. I recommend an Ubuntu based distro. I use Linux mint
Sent from my Carbon-ize Evita using xda-developers app

There's a guide to making a bootable Linux usb in q&a if you need it.
Sent from my One X using xda app-developers app

exad said:
There's a guide to making a bootable Linux usb in q&a if you need it.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Yeah, booting from Linux isn't a problem, but as I said, I was trying to put it to stock so I could sell it...but then I discovered it was still under warranty (with just a week left), so instead of messing around in Linux I took it to an AT&T warranty center on my way home and they just straight up replaced with a new One X... Everything turned out better than expected

bikeracer4487 said:
Yeah, booting from Linux isn't a problem, but as I said, I was trying to put it to stock so I could sell it...but then I discovered it was still under warranty (with just a week left), so instead of messing around in Linux I took it to an AT&T warranty center on my way home and they just straight up replaced with a new One X... Everything turned out better than expected
Click to expand...
Click to collapse
Great!! But is it on the new unrootable software?

ImagioX1 said:
Great!! But is it on the new unrootable software?
Click to expand...
Click to collapse
Yup :-/ Software version 3.18, 2.14 hboot, S-ON, and CID of CWS__001... But since I won't be keeping this phone, it'll be someone else's problem...

bikeracer4487 said:
Yup :-/ Software version 3.18, 2.14 hboot, S-ON, and CID of CWS__001... But since I won't be keeping this phone, it'll be someone else's problem...
Click to expand...
Click to collapse
LoL!!
Sent from Xparent Red using my Venomized Evita

It is technically better to have a brand new in box phone for selling. That's awesome! Congrats! I wish Canadian carriers warranted phones like they do in the US. You only get manufacturer warranty here.
Sent from my One X using xda app-developers app

exad said:
It is technically better to have a brand new in box phone for selling. That's awesome! Congrats! I wish Canadian carriers warranted phones like they do in the US. You only get manufacturer warranty here.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
You could pay the 7 bucks a month for device protection then drive over it with a car when you brick it
Sent from my VENOMized HoxL

area51avenger said:
You could pay the 7 bucks a month for device protection then drive over it with a car when you brick it
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
Or just keep it and say that you lost it. And of you are able to fix it, sell it and you still keep a new phone.
Sent from my Carbon-ize Evita using xda-developers app

Pft, that's an extra 252$ within my contract period. Forget that noise! I doubt I'll even have this phone in a year lol.
Sent from my One X using xda app-developers app
---------- Post added at 10:17 AM ---------- Previous post was at 10:06 AM ----------
Herc08 said:
Or just keep it and say that you lost it. And of you are able to fix it, sell it and you still keep a new phone.
Sent from my Carbon-ize Evita using xda-developers app
Click to expand...
Click to collapse
They don't warrant lost phones here.
Sent from my One X using xda app-developers app

exad said:
Pft, that's an extra 252$ within my contract period. Forget that noise! I doubt I'll even have this phone in a year lol.
Sent from my One X using xda app-developers app
---------- Post added at 10:17 AM ---------- Previous post was at 10:06 AM ----------
They don't warrant lost phones here.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Oh wow. Didn't know that
Sent from my Carbon-ize Evita using xda-developers app

exad said:
They don't warrant lost phones here.
Click to expand...
Click to collapse
They don't cover lost phones on warranty anywhere. He was talking about insurance, not a warranty.

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