Database Info

Semi-bricked, ICS RUU issues

Last night I flashed the gingerbread coredroid ROM and it worked fine. I just didn't really like the looks of some things, so I thought I'd change to a different ROM.
I thought about flashing the ICS Insertcoin ROM, so I flashed it, and it kept trying to boot, but turned off and kept repeating. But then I read that I was supposed to update the firmware, so I took out the SIM card and connected it to the computer and copied the 3.24 RUU to the SD card.
I followed the instructions and the RUU set up properly through HBoot the first time. Then i went in to recovery to wipe data. It had to reboot the phone before I did anything else, and it went back into HBOOT and tried to install the RUU again, but this time it failed due to CID being incorrect! I didn't give it a second thought, but then the insertcoin ROM was doing the same thing, going through the boot up images and shutting off right in the middle, and repeating.
I tried another ICS ROM, Android Revolution, and same result. Failed booting. Then I tried restoring my nandroid backup from before coredroid, and it also kept trying to boot and then shut down. Then I tried coredroid again, and it had the same reaction, failed booting! I redownloaded the ICS RUU 4 times and repeated this process 4 different times, even with other GB versions of insertcoin and ARHD, and no dice!
I'm not entirely tech savvy, so maybe there is soemthing I havent covered yet. Now the RUU fails not because of CID, but because of incorrect Model ID. I read about goldcards, but I can't make a new one because the phone won't even boot! Please help me!
edit: as of now, the phone does not turn on to any rom or homescreen, ONLY Hboot and recovery.

Hello Jagerlowe,
The 3.24 RUU installs fully with 2 Boots into Bootloader, so there is nothing to be worried about. Here's how you could solve your problem.
1. Please follow step 4 from this Guide to obtain SuperCID, make sure that the SuperCID is 11111111! Mismatch of the SUPERCID causes the Error you were previously facing.
2. With the updated SuperCID, reinstall the latest ARHD 6.2.1 ROM.
3. Boot & flash the suggested radio if you are using the ARHD ROM.
You should be alright
Please keep me posted about your problem and hope it helped!
Remember to Thank me!

CursedBat said:
Hello Jagerlowe,
The 3.24 RUU installs fully with 2 Boots into Bootloader, so there is nothing to be worried about. Here's how you could solve your problem.
1. Please follow step 4 from this Guide to obtain SuperCID, make sure that the SuperCID is 11111111! Mismatch of the SUPERCID causes the Error you were previously facing.
2. With the updated SuperCID, reinstall the latest ARHD 6.2.1 ROM.
3. Boot & flash the suggested radio if you are using the ARHD ROM.
You should be alright
Please keep me posted about your problem and hope it helped!
Remember to Thank me!
Click to expand...
Click to collapse
I can't quite do that because the phone doesn't turn on. It goes to the boot screen then shuts off. Then turns on, boot screen, off again. So I can't connect it to the computer or do anything like that.

This thread might help you... ICS flashing is little bit different than GB...
http://forum.xda-developers.com/showthread.php?t=1459767
Sent from my HTC Sensation 4G with Beats

Jagerlowe said:
I can't quite do that because the phone doesn't turn on. It goes to the boot screen then shuts off. Then turns on, boot screen, off again. So I can't connect it to the computer or do anything like that.
Click to expand...
Click to collapse
Can you boot your device into Recovery mode?

Jagerlowe said:
Last night I flashed the gingerbread coredroid ROM and it worked fine. I just didn't really like the looks of some things, so I thought I'd change to a different ROM.
I thought about flashing the ICS Insertcoin ROM, so I flashed it, and it kept trying to boot, but turned off and kept repeating. But then I read that I was supposed to update the firmware, so I took out the SIM card and connected it to the computer and copied the 3.24 RUU to the SD card.
I followed the instructions and the RUU set up properly through HBoot the first time. Then i went in to recovery to wipe data. It had to reboot the phone before I did anything else, and it went back into HBOOT and tried to install the RUU again, but this time it failed due to CID being incorrect! I didn't give it a second thought, but then the insertcoin ROM was doing the same thing, going through the boot up images and shutting off right in the middle, and repeating.
I tried another ICS ROM, Android Revolution, and same result. Failed booting. Then I tried restoring my nandroid backup from before coredroid, and it also kept trying to boot and then shut down. Then I tried coredroid again, and it had the same reaction, failed booting! I redownloaded the ICS RUU 4 times and repeated this process 4 different times, even with other GB versions of insertcoin and ARHD, and no dice!
I'm not entirely tech savvy, so maybe there is soemthing I havent covered yet. Now the RUU fails not because of CID, but because of incorrect Model ID. I read about goldcards, but I can't make a new one because the phone won't even boot! Please help me!
edit: as of now, the phone does not turn on to any rom or homescreen, ONLY Hboot and recovery.
Click to expand...
Click to collapse
did you solve this because i think im having the same issue as you

Mookie_Jones said:
did you solve this because i think im having the same issue as you
Click to expand...
Click to collapse
Can you boot your device into Recovery mode?

CursedBat said:
Can you boot your device into Recovery mode?
Click to expand...
Click to collapse
Yes, I can boot it into recovery and HBOOT, thats it.

Jagerlowe said:
Yes, I can boot it into recovery and HBOOT, thats it.
Click to expand...
Click to collapse
What I am about to guide you through is downgrading your HBoot.
Firstly, download 1.17RUU - CHOOSE WHICH Service Provider, Location (CHOOSE THE RIGHT ONE)
http://forum.xda-developers.com/showthread.php?t=1459767
1. Boot into recovery mode and connect your phone to your computer.
2. Select "mounts and storage"
3. Then select mount sd card.
4. Copy the PG58IMG.zip into the Root of your SD Card.
5. Reboot your phone into bootloader again.
Your phone should automatically prompt you to begin update. After the update,
Your Bootloader should be downgraded. Then Flash a simple - any Gingerbread based ROM, and follow my post on doing SuperCID
Goodluck! Cheers

CursedBat said:
What I am about to guide you through is downgrading your HBoot.
Firstly, download 1.17RUU - CHOOSE WHICH Service Provider, Location (CHOOSE THE RIGHT ONE)
http://forum.xda-developers.com/showthread.php?t=1459767
1. Boot into recovery mode and connect your phone to your computer.
2. Select "mounts and storage"
3. Then select mount sd card.
4. Copy the PG58IMG.zip into the Root of your SD Card.
5. Reboot your phone into bootloader again.
Your phone should automatically prompt you to begin update. After the update,
Your Bootloader should be downgraded. Then Flash a simple - any Gingerbread based ROM, and follow my post on doing SuperCID
Goodluck! Cheers
Click to expand...
Click to collapse
Oh my gosh! Can I like marry you!? You fixed my problem! Thank you so much!

Jagerlowe said:
Oh my gosh! Can I like marry you!? You fixed my problem! Thank you so much!
Click to expand...
Click to collapse
You're welcome I'm just glad to be of any use.
Good luck experimenting with ICS
Cheers!

htc one s brik problem [SOLVED]

Hi i have a big problem with my new htc one s
i follow all instructions: clear data, factory reset, install rom, then install boot.img
Roms boot until it shows wallpaper and top toolbar with the battery icon and time, then can read preparing phone storage.... and an error appears asking me to wait or close system process
The rom restarts and stucks at this point dont know what else do, i try installing stock recovery and clear data factory reset and try install with 3 versions of recovery whith same result, have tried some different roms and its the same.
Wonder if anyone knows what i have to do solve this..
Thankyou in advance.
--------------------------
solution on post #7

Moved To Q&A​
This is a development section, its not the place for questions.​

Which roms did you try to flash? Did you flash the correct boot.img
Sent from my HTC One S using XDA

thanks for your answer
Yes i flash [ROM][ICS] |June 13th| Energy™ -.¸¸.·´¯ Blue with the boot.img from the downloads
and [ROM] Ir2 1.78.401.2 - HTC One S Stock ROM DUO [Deodexed-Updated-Optimised]
When finish flasing from recovery reboot on fastboot and flash the boot.img and always is the same result.
I've tried to change to stock version of recovery and wipe all, reset to factory default then flash custom recovery and start the process but is the same.
when i whipe from stock or custom version of recovery there isn't any error message.
thankyou very much.

you don't flash the boot.img from recovery--read OP

boot.img
I flash it from fastboot not installing a zip from recovery. I also try installing by script like on [ROM][ICS] |June 14th| Energy™ -.¸¸.·´¯ Blue that there is an script that makes the installation always from fastboot

[solved]
Hi, find a way to make my htc one s woking again
This is the solution:
first i've to change my CID because my phone is from ORANGE spain and cannot flash a official RUU.
for this i follow this tutorial
http://forum.xda-developers.com/showthread.php?p=26516911#post26516911
Second flash stock recovery and lock boot
finally i've downloaded the last europe RUU, and execute it.The process works like a charm and in 15 or 20 minutes my one s was working again.
Now i have lock boot, stock recovery and unrooted phone and have one question:
for root my phone again have to unlock and flash a custom recovery, and then.....
should I need to put back again stock recovery and lock boot for working an official RUU?? or can work without problems with unloked boot an custom recovery?
Thanks in advance.

Hey I have the exact same issue but running RUU didnt solve it. I have the US Tmobile Htc one s, S-off, supercid, hboot 1.14. I could load custom roms and mount usb storage only through recovery. my sd card does not show in fastboot. However, my phone never completely boots. It goes all the way to the lockscreen, allows me to pull the ring, then gets stuck on preparing phone storage. Flashing RUU does the same.
can anyone help?

joemanbui said:
Hey I have the exact same issue but running RUU didnt solve it. I have the US Tmobile Htc one s, S-off, supercid, hboot 1.14. I could load custom roms and mount usb storage only through recovery. my sd card does not show in fastboot. However, my phone never completely boots. It goes all the way to the lockscreen, allows me to pull the ring, then gets stuck on preparing phone storage. Flashing RUU does the same.
can anyone help?
Click to expand...
Click to collapse
i too have same prob tried all kinds of ruu's. been trying for 14 hours if you find soething please report how you did it

I have the same problem any ideas?
anyone know of any gurus in the forum knows how to fix
I've been trying for a month
any rom to put loads and after a 10-20sec reset

For you with sd-card problems, have you tried to flash stock recovery and then boot to bootloader and choose clear storage? It worked for me.
If you installed a RUU, ofcourse you already have stock recovery.
Sent from my One S using Tapatalk 4 Beta

I have the same problem, and decided to work on it today... I can say frustratingly i've not had ANY success in getting past the screen that pops up with the lock ring on the bottom...I've tried RUUs , the clear storage ... what is going on... I'm S-off as well so i really don't get why this would happen.

One S (s4)
twrp 2.5
S-on
T-mobile US
CM10.2
kernel 3.4
Hboot 2.15
openDsp v31.1.0.45.0815
current raido :1.11.50.05.28_10.27.50.08L
using the getvar method
i get this
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: HTC__203
using fastboot getvar version-main
Version-main : ( BLANK)
Click to expand...
Click to collapse
after following the steps for s-off it worked
the bootloader shows VLE PVT SHIP -S-OFF RL
CID-11111111
right after i followed the last step of the face palm method which was
boot into android and issue the 3 commands
adb push soffbin3 /data/local/tmp/
adb shell chmod 744 /data/local/tmp/soffbin3
adb shell su -c "/data/local/tmp/soffbin3"
Click to expand...
Click to collapse
i went into the bootloader confirmed everything then wen back to CM and it woudnt load
so i wiped everything and flashed a new version and an older 10.1 stable version which didnt work either
it would just freeze at the loading screen and restart
so i tried wiping everything and flash a stock RUU from HTC (t-mobile) 4.1.1
everything went off without a hitch
went to bootloader which showed a new version of the radio
tried to boot it up
and it did boot up but i coudnt go any further it just keeps saying
Preparing phone storage
then restarts
i tried wipe/data factory reset but it says cant mount SDCARD even though TWRP has no problem with wiping it

I have the same problem..
qwerty warrior said:
after following the steps for s-off it worked
the bootloader shows VLE PVT SHIP -S-OFF RL
CID-11111111
right after i followed the last step of the face palm method which was
i went into the bootloader confirmed everything then wen back to CM and it woudnt load
so i wiped everything and flashed a new version and an older 10.1 stable version which didnt work either
it would just freeze at the loading screen and restart
so i tried wiping everything and flash a stock RUU from HTC (t-mobile) 4.1.1
everything went off without a hitch
went to bootloader which showed a new version of the radio
tried to boot it up
and it did boot up but i coudnt go any further it just keeps saying
Preparing phone storage
then restarts
i tried wipe/data factory reset but it says cant mount SDCARD even though TWRP has no problem with wiping it
Click to expand...
Click to collapse
I have the exact same problem did you ever figure out a way of fixing it?

qwerty warrior said:
i went into the bootloader confirmed everything then wen back to CM and it woudnt load
so i wiped everything and flashed a new version and an older 10.1 stable version which didnt work either
it would just freeze at the loading screen and restart
so i tried wiping everything and flash a stock RUU from HTC (t-mobile) 4.1.1
everything went off without a hitch
went to bootloader which showed a new version of the radio
tried to boot it up
and it did boot up but i coudnt go any further it just keeps saying
Preparing phone storage
then restarts
i tried wipe/data factory reset but it says cant mount SDCARD even though TWRP has no problem with wiping it
Click to expand...
Click to collapse
exact same problem except i didnt flash a custom rom. i flashed a radio following this http://forum.xda-developers.com/showthread.php?t=1998270 ( i did everything that I was instructed to do in this page) then my wifi didnt work so i reflash the RUU. now im stuck in preparing storage which then lead to bootloop
found the solution
Originally Posted by muriani View Post
well, as a last resort, i set cid to t-mob010 (stock for my phone), ran the latest ruu for t-mobile, and same result.
I've given it up for lost.
Edit: Holy f*ckballs.
So, i didn't give up after all. Found a couple of other threads, and apparently yes, you have to relock, reset cid, and go s-on (fastboot oem writesecureflag 3) and then run the ruu.
I have a stock fresh tmous 4.1.1 one s now.

xxgummyxx said:
exact same problem except i didnt flash a custom rom. i flashed a radio following this http://forum.xda-developers.com/showthread.php?t=1998270 ( i did everything that I was instructed to do in this page) then my wifi didnt work so i reflash the RUU. now im stuck in preparing storage which then lead to bootloop
found the solution
Originally Posted by muriani View Post
well, as a last resort, i set cid to t-mob010 (stock for my phone), ran the latest ruu for t-mobile, and same result.
I've given it up for lost.
Edit: Holy f*ckballs.
So, i didn't give up after all. Found a couple of other threads, and apparently yes, you have to relock, reset cid, and go s-on (fastboot oem writesecureflag 3) and then run the ruu.
I have a stock fresh tmous 4.1.1 one s now.
Click to expand...
Click to collapse
thank you thanks !!!!!!! two days without finding the solution and in the last paragraph that I will write opened the sky, put it in s-on, Greetings

dosariland said:
thank you thanks !!!!!!! two days without finding the solution and in the last paragraph that I will write opened the sky, put it in s-on, Greetings
Click to expand...
Click to collapse
For about some days, I flash an RUU when I was still s-off and boot-unlocked, then I flash twrp-recovery, make the adb thinks with mmcblk* (dd flash) and flash again a RUU. As you can read here.
But same boot loop problem with "Preparing Phone Storage...".
Because dd flash (the mmcblk* file) under linux and with startet recovery did not solve my bootloop / prepairing sd card problem (I had still access to my sd card with twrp-recovery! All the time!) I really think about to enable s-on
I am only scared when I do:
fastboot oem writesecureflag 3
Click to expand...
Click to collapse
How can I re-enable s-off if my os still hangs on "Preparing Phone Storage" after putting s-on and try to flash an ruu to fix my bootloop/Preparing Phone Storage problem?
I did my s-off with rumrunner.
Would be very thankfull about help.
Greetings by I_did_it_just_tmrrow
you have to relock, reset cid, and go s-on (fastboot oem writesecureflag 3) and then run the ruu.
Click to expand...
Click to collapse
THX!!!
I leave superCID and it works! I hope my signal would be fine under stock.
THX a lot!
Greetings by I_did_it_just_tmrrow

[Q] Unable to flash new roms

First some background. I am S-off and currently running cleanrom6 r2. I tried to flash the unoffical cm10.1 but got some errors (can't remember all of it but i think it had something to do with an error code 7?) so I restored my backup from twrp and was able to reboot with no problem. I then decided to try running viperxl 3.27. It says that it installs properly but when I go to reboot it just sits at the htc boot screen with the tamper warning. I have to reboot into recovery and then I can restore to the backup and then it boots fine. I am doing the whole clear cache and system thing before i am flashing the roms. Any ideas?

wmorrow said:
First some background. I am S-off and currently running cleanrom6 r2. I tried to flash the unoffical cm10.1 but got some errors (can't remember all of it but i think it had something to do with an error code 7?) so I restored my backup from twrp and was able to reboot with no problem. I then decided to try running viperxl 3.27. It says that it installs properly but when I go to reboot it just sits at the htc boot screen with the tamper warning. I have to reboot into recovery and then I can restore to the backup and then it boots fine. I am doing the whole clear cache and system thing before i am flashing the roms. Any ideas?
Click to expand...
Click to collapse
What Hboot and what recovery?

exad said:
What Hboot and what recovery?
Click to expand...
Click to collapse
hboot is 1.14.0002 and my recovery is TWRP 2.3.1.0

wmorrow said:
hboot is 1.14.0002 and my recovery is TWRP 2.3.1.0
Click to expand...
Click to collapse
RUU up to 2.14 (3.18 or 3.17, depending on your carrier) Then downgrade the touchscreen firmware (sticky in original android development). I've seen others not able to boot newer AOSP and Sense roms based on 3.17/3.18 unless they are on 2.14 hboot. Why? I'm not sure. But I'm positive it will work after.
When you RUU, since you're S-OFF, no need to change CID or relock the bootloader, in case you didn't know.
You can update TWRP or flash the same one, just don't flash any version above 2.3.3.1 I'm not sure 2.3.1.0 will work (the touchscreen that is) until you downgrade the touchscreen firmware.

exad said:
RUU up to 2.14 (3.18 or 3.17, depending on your carrier) Then downgrade the touchscreen firmware (sticky in original android development). I've seen others not able to boot newer AOSP and Sense roms based on 3.17/3.18 unless they are on 2.14 hboot. Why? I'm not sure. But I'm positive it will work after.
When you RUU, since you're S-OFF, no need to change CID or relock the bootloader, in case you didn't know.
You can update TWRP or flash the same one, just don't flash any version above 2.3.3.1 I'm not sure 2.3.1.0 will work (the touchscreen that is) until you downgrade the touchscreen firmware.
Click to expand...
Click to collapse
I will try this once I get some freetime today. I have never really messed with RUU's. Do you flash them the same way as you would a ROM? Thank you for your help on this.

wmorrow said:
I will try this once I get some freetime today. I have never really messed with RUU's. Do you flash them the same way as you would a ROM? Thank you for your help on this.
Click to expand...
Click to collapse
Download the exe and run it on your PC with your phone plugged in. To say it's simple would be an understatement.

exad said:
Download the exe and run it on your PC with your phone plugged in. To say it's simple would be an understatement.
Click to expand...
Click to collapse
After running the ruu and downgrading the touch screen firmware and then loading the twrp I tried to load Cleanrom and once again got stuck on the htc quietly brilliant screen with red text.

wmorrow said:
After running the ruu and downgrading the touch screen firmware and then loading the twrp I tried to load Cleanrom and once again got stuck on the htc quietly brilliant screen with red text.
Click to expand...
Click to collapse
Weird, what version of TWRP? did you wipe cache, dalvik, system, factory reset prior to flashing?
If so you can try to fastboot flash boot boot.img from cleanrom though you should not have to if you are S-OFF.

exad said:
Weird, what version of TWRP? did you wipe cache, dalvik, system, factory reset prior to flashing?
If so you can try to fastboot flash boot boot.img from cleanrom though you should not have to if you are S-OFF.
Click to expand...
Click to collapse
I'm using 2.3.1.0 and im doing "System", "Factory Reset", Dalvik Cache" and "Cache" in that order.

Hmm, did you check MD5 of twrp before flashing?
Did you check MD5 of Cleanrom before flashing?
If so, I would try flashing TWRP 2.3.3.x and then do fastboot erase cache
then wipe everything in twrp then reflash rom

exad said:
Hmm, did you check MD5 of twrp before flashing?
Did you check MD5 of Cleanrom before flashing?
If so, I would try flashing TWRP 2.3.3.x and then do fastboot erase cache
then wipe everything in twrp then reflash rom
Click to expand...
Click to collapse
Still nothing and i installed 2.3.3.1. Why should I not install 2.5?

wmorrow said:
Still nothing and i installed 2.3.3.1. Why should I not install 2.5?
Click to expand...
Click to collapse
TWRP 2.4+ has issues wiping and leads to the kind of issue you're having now. I'm at a loss.. I'm really not sure why you can't boot. If you're doing everything as directed you shouldn't be having any issues.

exad said:
TWRP 2.4+ has issues wiping and leads to the kind of issue you're having now. I'm at a loss.. I'm really not sure why you can't boot. If you're doing everything as directed you shouldn't be having any issues.
Click to expand...
Click to collapse
I went ahead and wiped the sd card and went step by step from the RUU and I was finally able to get it to load roms again. Thank you very much.

[Q] Need help!

ok, I was super cid and hboot was moonshine i was running the unknown rom and went to install a bulletproof kernel. it booted and soon after rebooted, I went into cwm and it came up with a whole bunch of errors about storage and started soft resetting again. I reset with an ruu from tmobile and it still wont boot properly. my hboot was reset and now im bootloader locked again and i cant flash a recovery it resets into the ruu image thats installed an trys to scan phone storage and then just resets. am I screwed?

davwman said:
ok, I was super cid and hboot was moonshine i was running the unknown rom and went to install a bulletproof kernel. it booted and soon after rebooted, I went into cwm and it came up with a whole bunch of errors about storage and started soft resetting again. I reset with an ruu from tmobile and it still wont boot properly. my hboot was reset and now im bootloader locked again and i cant flash a recovery it resets into the ruu image thats installed an trys to scan phone storage and then just resets. am I screwed?
Click to expand...
Click to collapse
Why not just Unlock bootloader again and flash recovery anew, flash ROM.

Boot to bootloader and select clear storage. Then boot to bootloader and do a factory reset. Hopefully that will do it. Then you can unlock bootloader again and flash a custom recovery.
Sent from my One S using Tapatalk 4

El_Svanto said:
Boot to bootloader and select clear storage. Then boot to bootloader and do a factory reset. Hopefully that will do it. Then you can unlock bootloader again and flash a custom recovery.
Sent from my One S using Tapatalk 4
Click to expand...
Click to collapse
how do I unlock boot loader from bootloader. I tried fastboot oem unlock, and nothing. I cant use adb because i cant boot into android

Did the RUU install correctly? So you are now on a stock ROM? If so, did you try the first two steps i wrote?
Sent from my One S using Tapatalk 4

tried that too. still just bootloops. it will boot up show the internal storage than just bootloops.

I would try to enter fastboot and run the RUU again to be sure it flashed correctly. Then try clear storage one more time to fix your SD-card. If that doesn't work i think there is a manual way to format the sd-card. Maybe someone can provide a link?
BTW, going to sleep now.
Sent from my One S using Tapatalk 4

El_Svanto said:
I would try to enter fastboot and run the RUU again to be sure it flashed correctly. Then try clear storage one more time to fix your SD-card. If that doesn't work i think there is a manual way to format the sd-card. Maybe someone can provide a link?
BTW, going to sleep now.
Sent from my One S using Tapatalk 4
Click to expand...
Click to collapse
ok im unlocked on hboot 2.15.0000 again due in part to the ruu and s-off. im getting errors in fastboot trying to install a recovery

davwman said:
ok im unlocked on hboot 2.15.0000 again due in part to the ruu and s-off. im getting errors in fastboot trying to install a recovery
Click to expand...
Click to collapse
factory recovery is now accessible

davwman said:
ok im unlocked on hboot 2.15.0000 again due in part to the ruu and s-off. im getting errors in fastboot trying to install a recovery
Click to expand...
Click to collapse
Usual errors while installing a recovery are because the boot loader is locked (relocked).
You sure you unlocked the boot loader after you ran the RUU?

Def. Was unlocked. I am running completely stock rooted right now, only because I need the phone reliably for a few days. Cell service took forever to connect after the restore to stock and speeds are really bad on data now. Have to figure that one out. After 12 hours getting this thing to finally resemble its former self, I have files all over my laptop and am going to completely flush everything pertaining to this phone and start from scratch to get back to s off and moonshine hboot. This phone is a pita, though.

[Q] stuck on htc logo

Hi! i have a problem with my ATT one x. (hboot 2.14, bootloader Unlocked, Cid 111111, twrp 2.6 , But S-ON!!) When i trying to get S-OFF, i made advanced wipe in TWRP, and then phone begin stuck on htc logo. i trying to load cm 10, but it stuck on cm logo... how i can go out from this???:crying:

Watcher505 said:
Hi! i have a problem with my ATT one x. (hboot 2.14, bootloader Unlocked, Cid 111111, twrp 2.6 , But S-ON!!) When i trying to get S-OFF, i made advanced wipe in TWRP, and then phone begin stuck on htc logo. i trying to load cm 10, but it stuck on cm logo... how i can go out from this???:crying:
Click to expand...
Click to collapse
good news its showing something start it up in boot loader go to recovery and repeat the flashing process!
now that you are bootloader unlocked and SOFF i don't think its possible to restore it through RESET option in bootloader.
well did u happen to wipe everything?
that had once happened with me try Mounting USB from recovery put any ROM in it and you should flash it!
and btw what method did u follow for SOFF?

Sonone said:
good news its showing something start it up in boot loader go to recovery and repeat the flashing process!
now that you are bootloader unlocked and SOFF i don't think its possible to restore it through RESET option in bootloader.
well did u happen to wipe everything?
that had once happened with me try Mounting USB from recovery put any ROM in it and you should flash it!
and btw what method did u follow for SOFF?
Click to expand...
Click to collapse
its was my mistake(about full wipe)... i now have att 3.18 and as i understend, i cannt go to write roms by ruu... i trying some customs rom, but without effect.. i cannt get soff without load and cannot load witout flash ruu or ota as i understand...

Did you flash the boot.img via fastboot when you flashed the ROM? You're s-on so you need to do that.
Sent from my Evita

timmaaa said:
Did you flash the boot.img via fastboot when you flashed the ROM? You're s-on so you need to do that.
Sent from my Evita
Click to expand...
Click to collapse
many thanks!!!!! didnt see anywhere about this!! now all ok
)))):good:

No problems. If you get s-off you won't need to worry about that anymore.
Sent from my Evita