Database Info

Semi-Bricked HTC ONE X

SO I've basically tried everything here,
it all went wrong when I stupidly forgot that I was in the wrong section and was trying to flash a international rom...
anyways now the phone only goes up to the HTC white screen and is stuck there.
BAsically i did the fastboot clearing and erything.
I also locked my bootloader and then tried to write the ruu again.
However while im doing that about after 4% , it gives me the error code 171, saying that my phone ahs been disconnected. I installed the HTC sync and everything what am i doing wrong....thanks
im using the ruu 1.85

you are lucky to have white screen

You posted in the wrong section...
This is for devsonly
Sent from my HTC One X using xda premium

xpurpleblob said:
SO I've basically tried everything here,
it all went wrong when I stupidly forgot that I was in the wrong section and was trying to flash a international rom...
anyways now the phone only goes up to the HTC white screen and is stuck there.
BAsically i did the fastboot clearing and erything.
I also locked my bootloader and then tried to write the ruu again.
However while im doing that about after 4% , it gives me the error code 171, saying that my phone ahs been disconnected. I installed the HTC sync and everything what am i doing wrong....thanks
im using the ruu 1.85
Click to expand...
Click to collapse
If you updated to 4.0.4 (2.20) before you killed your phone, then use the 2.20 RUU found on HTC's website. You can't be updated and use a downgraded RUU. If that doesn't work, and your bootloader is locked and everything, then idk what to say. Try taking it to ATT if you're stillin your 30 day period. If try even if you're not.
---------- Post added at 12:19 AM ---------- Previous post was at 12:17 AM ----------
And you are in the wrong section. This belongs in the Q&A.

vin255764 said:
you are lucky to have white screen
Click to expand...
Click to collapse
what does this mean...

xpurpleblob said:
what does this mean...
Click to expand...
Click to collapse
It means your lucky your phone still turns on. A brick means the phone won't turn on at all, or anything. You're lucky to be seeing the white HTC Screen. You really are.
EDIT: Download the HTC Drivers again, and reinstall them. That might help the connectivity issues. Or, try using a different USB port on your computer. When you plug the phone in, do you hear a resounding "beep", meaning the computer has recognized the device being plugged in?

HTC_Phone said:
It means your lucky your phone still turns on. A brick means the phone won't turn on at all, or anything. You're lucky to be seeing the white HTC Screen. You really are.
EDIT: Download the HTC Drivers again, and reinstall them. That might help the connectivity issues. Or, try using a different USB port on your computer. When you plug the phone in, do you hear a resounding "beep", meaning the computer has recognized the device being plugged in?
Click to expand...
Click to collapse
I believe so, maybe not I'm currently doing work right now so I will check later.
However, the computer seems to recognize my phone when I'm applying the RUU, it stops at about 7% then shows the ERRor message 171
Thanks for the help.

can anyone please help

Where can I get stock recovery, stock boot for the phone?

First to Relock your device, you will want to boot into your bootloader and select fastboot. After you've selected fastboot plug your device into your pc and open a command prompt. You'll want to type 'cd C:\Android' and then 'fastboot oem lock' and your phone will restart with a locked bootloader. Now you can upgrade to the RUU without any issues.
Now find your ruu here http://forum.xda-developers.com/show....php?t=1671237 under STOCK RUUs AND RELATED.
Once you've finished upgrading your ruu you will want to boot into your bootloader again, with your device unplugged, and select fastboot. THEN plug your device in and run your command prompt again on your PC. Again, cd to C:\Android and type in the following command to unlock your bootloader again: 'fastboot flash unlocktoken Unlock_code.bin'
Hope this helps ^____^

thanks for the reply, however ur link is broken.

And if possible can someone list all the programs I need for this task...
the Htc sync, android sdk,.. etc
and do i need the adt file??

Also i am getting a signature verify failure when im flashing a recovery.img....
also btw i have the nandroid backups. i cant access the recovery in the hot boot though

xpurpleblob said:
thanks for the reply, however ur link is broken.
Click to expand...
Click to collapse
He meant to link the Index thread for the RUUs: http://forum.xda-developers.com/showthread.php?t=1671237

I did the same. :silly: I've allways used CM recovery. couldn't get to flash. TWRP worked great!
If you have fastboot hopfully this works. May not get back to stock without RUU. However who cares.
Flashing custom ROMs is fun. :victory:
http://theunlockr.com/2012/06/05/how-to-install-twrp-2-1-recovery-on-att-and-rogers-htc-one-x/

subarudroid said:
I did the same. :silly: I've allways used CM recovery. couldn't get to flash. TWRP worked great!
If you have fastboot hopfully this works. May not get back to stock without RUU. However who cares.
Flashing custom ROMs is fun. :victory:
http://theunlockr.com/2012/06/05/how-to-install-twrp-2-1-recovery-on-att-and-rogers-htc-one-x/
Click to expand...
Click to collapse
I don't think I can use that because my bootloader is locked.

Did you try SUPERCID? How did you do all that without SUPERUSER# ?
correct me if I'm wrong but you should still be able to unlock the bootloader if you have fastboot?

subarudroid said:
Did you try SUPERCID? How did you do all that without SUPERUSER# ?
correct me if I'm wrong but you should still be able to unlock the bootloader if you have fastboot?
Click to expand...
Click to collapse
i relocked my bootloader to run the RUU, however when I run it the eroor code 170 comes up

I tried 3 diff. RUU's none of them worked. I'm on AT&T.
You should be able to Unlock bootloader again though.
HTC devs would have email you the unlock_code.bin file
Maybe you deleted from desktop? IT might still be in your email?
IF your windows you can hit (Shift+rightclick) in folder run CMD.
fastboot erase cache
fastboot flash unlocktoken Unlock_code.bin make sure your fastboot files are in there also.
THis thread might also help. I take no credit. But I hope we can help you get your phone up and running to some degree.
http://forum.xda-developers.com/showthread.php?t=1671396
---------- Post added at 08:03 PM ---------- Previous post was at 07:37 PM ----------
I should also know note that I cannot take any responsibility for your phone being destroyed
Sent from my One X using xda app-developers app

Alright I got it working. If anybody ever gets the same problem as me, disable your antivirus, take out your internet connection from the computer, run as administrator for the RUU, and close all programs except for the RUU.
I BELIEVE THE MOST IMPORTANT WAS TO OPEN A NEW ADMINISTRATOR ACCOUNT ON THE COMPUTER.
I don't know which of these factors are definite but follow these steps and hopefully you will solve your problem too.

Please help installing CleanROM 4.5....Stuck in Recovery....

I had my phone rooted and unlocked and was also using CleanROM 4.1 before I decided today to change to CleanROM 4.5.
So, I downloaded the file and went to Recovery and flashed it (it did take very little time with flashing which I found rather strange.) When I rebooted, the phone was stuck at the HTC screen. I figured that I MIGHT have had CWM installed and I didn't know it (I can't be quite 100% sure of this as I thought I DID have TWRP since it was a touch recovery that I had.) Since I was able to boot back up to Fastboot, I said "Let me flash the TWRP recovery file and try again".....Well, I did that and according to the Command Prompt it was successful (showed sending, writing, finished etc....) Once finished, I rebooted back and all I see now is the TeamWin logo in Recovery and THAT'S IT. It won't give me any menu options. If I let it sit, it will reboot back to the HTC screen.
What are my options right now? Is there a specific file I can flash through Fastboot that will allow me to proceed?
I would appreciate the help and I'll be sure to come back and let you know how successful I was. :fingers-crossed:
****BTW, I want to point out that my phone has had this strange message everytime it reboots (over the past few months since unlocked) stating: "This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission....etc..." What does that mean? I don't like that message to appear everytime I reboot my phone. Thanks again!

reflash
Try flashing the boot.IMG from the the zipped ROM you were trying to flash to boot partition through the bootloader (cmd in windows: fastboot flash boot boot.img[enter] after you put The boot.img in the same folder as the adb & cd to that folder) and flash cwm for recovery, then you can reflash twrp

thesm4rt1 said:
Try flashing the boot.IMG from the the zipped ROM you were trying to flash to boot partition through the bootloader (cmd in windows: fastboot flash boot boot.img[enter] after you put The boot.img in the same folder as the adb & cd to that folder) and flash cwm for recovery, then you can reflash twrp
Click to expand...
Click to collapse
I will definitely be trying that. Will be back in a couple of hours and let you know how it went. Thank you!

bbonline said:
I had my phone rooted and unlocked and was also using CleanROM 4.1 before I decided today to change to CleanROM 4.5.
So, I downloaded the file and went to Recovery and flashed it (it did take very little time with flashing which I found rather strange.) When I rebooted, the phone was stuck at the HTC screen. I figured that I MIGHT have had CWM installed and I didn't know it (I can't be quite 100% sure of this as I thought I DID have TWRP since it was a touch recovery that I had.) Since I was able to boot back up to Fastboot, I said "Let me flash the TWRP recovery file and try again".....Well, I did that and according to the Command Prompt it was successful (showed sending, writing, finished etc....) Once finished, I rebooted back and all I see now is the TeamWin logo in Recovery and THAT'S IT. It won't give me any menu options. If I let it sit, it will reboot back to the HTC screen.
What are my options right now? Is there a specific file I can flash through Fastboot that will allow me to proceed?
I would appreciate the help and I'll be sure to come back and let you know how successful I was. :fingers-crossed:
****BTW, I want to point out that my phone has had this strange message everytime it reboots (over the past few months since unlocked) stating: "This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission....etc..." What does that mean? I don't like that message to appear everytime I reboot my phone. Thanks again!
Click to expand...
Click to collapse
In the future I suggest factory wipe even if going from CR to CR. Also, make sure to check the MD5 once you move the file on to your storage.

Butters619 said:
In the future I suggest factory wipe even if going from CR to CR. Also, make sure to check the MD5 once you move the file on to your storage.
Click to expand...
Click to collapse
I did do the factory wipe.
By the way, I tried what I was told to do and nothing happened. It successfully flashes the boot image and recovery, but when it tries to boot into the recovery, it just freezes in the recovery with the word TEAMWIN and a blue background....No menu or options.... I did try several different ways by downloading and installing several versions of the CWM and TWRP, but no success. Any other suggestions? Will I be stuck with this piece of brick now? Please help.

bbonline said:
****BTW, I want to point out that my phone has had this strange message everytime it reboots (over the past few months since unlocked) stating: "This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission....etc..." What does that mean? I don't like that message to appear everytime I reboot my phone. Thanks again!
Click to expand...
Click to collapse
^That right there is normal by the way and will always be there.
Looks like it's time for you to relock your bootloader (don't worry you can unlock it again), download an RUU, and try again.

Butters619 said:
^That right there is normal by the way and will always be there.
Looks like it's time for you to relock your bootloader (don't worry you can unlock it again), download an RUU, and try again.
Click to expand...
Click to collapse
Ughh! Do you know if I will lose any documents/pictures that are in my USB storage? Which RUU do you think is the best in my case? Thanks!

bbonline said:
Ughh! Do you know if I will lose any documents/pictures that are in my USB storage? Which RUU do you think is the best in my case? Thanks!
Click to expand...
Click to collapse
You will lose the contents of your SD card, which is why you should back that up before flashing. Since you were on CR 4.1, I would go with the 1.85 RUU. If you use 2.20, you will add an extra step or two in when it comes to flashing ROMs. But hey, your phone should work again!

Butters619 said:
You will lose the contents of your SD card, which is why you should back that up before flashing. Since you were on CR 4.1, I would go with the 1.85 RUU. If you use 2.20, you will add an extra step or two in when it comes to flashing ROMs. But hey, your phone should work again!
Click to expand...
Click to collapse
I know, silly me. Usually I backup the data and everything goes well and when I don't, there goes my luck! I really appreciate the suggestion.
One quick question, if in the future I need to have the phone sent in for warranty, is this the same procedure I need to follow? Relock and flash an RUU? Will they not know it had been unlocked before?

bbonline said:
I know, silly me. Usually I backup the data and everything goes well and when I don't, there goes my luck! I really appreciate the suggestion.
One quick question, if in the future I need to have the phone sent in for warranty, is this the same procedure I need to follow? Relock and flash an RUU? Will they not know it had been unlocked before?
Click to expand...
Click to collapse
Exact same procedure, but yes they will know. The giant RELOCKED gives it away lol.

Butters619 said:
Exact same procedure, but yes they will know. The giant RELOCKED gives it away lol.
Click to expand...
Click to collapse
Darn.... I just hope I don't have to deal with sending it for any repair. Gave you thanks!

Butters619 said:
Exact same procedure, but yes they will know. The giant RELOCKED gives it away lol.
Click to expand...
Click to collapse
But only if they reboot and look, which from what I've seen here, they never seem to do.

iElvis said:
But only if they reboot and look, which from what I've seen here, they never seem to do.
Click to expand...
Click to collapse
I took my One X back to Best Buy to swap it out just before the return policy expired because my gf dropped it and put a small dent in the casing and I didn't even bother to relock or even RUU my device. I said I had a software issue and couldn't get the OTA. They turned it on and played with it and it had a custom boot animation and a ROM on it lol. They also couldn't get the OTA so they approved the return.

Butters619 said:
Exact same procedure, but yes they will know. The giant RELOCKED gives it away lol.
Click to expand...
Click to collapse
it doesn't say RELOCKED when you run an RUU. It gets rid of everything like Tampered and Unlocked and returns the phone to LOCKED. like it came
---------- Post added at 08:34 PM ---------- Previous post was at 08:31 PM ----------
Butters619 said:
I took my One X back to Best Buy to swap it out just before the return policy expired because my gf dropped it and put a small dent in the casing and I didn't even bother to relock or even RUU my device. I said I had a software issue and couldn't get the OTA. They turned it on and played with it and it had a custom boot animation and a ROM on it lol. They also couldn't get the OTA so they approved the return.
Click to expand...
Click to collapse
hahaha, thank god for company cutbacks sometimes... it makes the employees not give a ****. and rightfully so too!!
the fact that companies cut back to make a few more billion dollars makes me sick anyways. but this is not the place for this conversation. carry-on

trichrome1 said:
it doesn't say RELOCKED when you run an RUU. It gets rid of everything like Tampered and Unlocked and returns the phone to LOCKED. like it came
---------- Post added at 08:34 PM ---------- Previous post was at 08:31 PM ----------
hahaha, thank god for company cutbacks sometimes... it makes the employees not give a ****. and rightfully so too!!
the fact that companies cut back to make a few more billion dollars makes me sick anyways. but this is not the place for this conversation. carry-on
Click to expand...
Click to collapse
Nope once you unlocked it won't ever say locked again. Just re-locked

gunnyman said:
Nope once you unlocked it won't ever say locked again. Just re-locked
Click to expand...
Click to collapse
not true, mine said LOCKED after running the att 1.85 RUU.. I had SUPERcid though if that makes any difference.

trichrome1 said:
not true, mine said LOCKED after running the att 1.85 RUU.. I had SUPERcid though if that makes any difference.
Click to expand...
Click to collapse
You should probably double check that. Anybody with an AT&T One X had to have SuperCID to unlock their bootloader so that wouldn't matter. I have unlocked two AT&T One Xs and run the 1.85 RUU on both (one of them a couple times) and I have run the 2.20 RUU on one. every time it says RELOCKED.

Mine did this to when going to 4.5.
I did the following to get back into Recovery.
Use fastboot to flash the boot.img from the cleanrom 4.5 zip.
"fastboot flash boot boot.img"
I then flashed the recovery (TWRP 2.2.1.4 at the moment) again to the phone.
next I erased Cache.
"fastboot erase cache"
I then used the phone itself to reboot the bootloader and went into recovery. It took about 10 minutes but recovery finally booted.
At this point I had no access to anything on the SD card. so I selected mount and mounted the sd card as disk drive to access it through my PC. I was forced to format the drive at this point and loaded a fresh copy of the ROM onto the drive for flashing.

You probably just got a wrong recovery. The recovery on twrp website didn't work for me. The one I downloaded from the development section works fine.
Sent from my One X using xda app-developers app

trichrome1 said:
not true, mine said LOCKED after running the att 1.85 RUU.. I had SUPERcid though if that makes any difference.
Click to expand...
Click to collapse
Screenshots PLS

Could really use a wish right now.. Stuck in Bootloader after failed flash of TWRP

Ok friend just got his new one x on att just moments ago.. wanted it rooted.. so i did i think.
installed Rom toolbox and tried to add that Twrp or what ever its caled custoer recovery (ot Clockwork mod)
Then selected boot to recover and its now stuck on a boot loader screen and will no go anwehere other than that pretty mch,, if i reboot it has the htc logo a warning about this beinga dev and then back to bootloader witch says s-on tampered and locked..
Im trying everyting and i got my boot loader key thing but i cant submit it to htc cause im guessing att wants it to sstay locked..
I cannot boot into the rom or anything i have a downloaded folder of http://www.mediafire.com/?d41k2x8sm9gesup
and tried to flash the fastboot cache still... notta..
What do i do to get out of this.. to unlock it and et back to root or even back to 1.85.. anything

Have you tried an ruu?
Sent from my One X using xda app-developers app

Mortland said:
Ok friend just got his new one x on att just moments ago.. wanted it rooted.. so i did i think.
installed Rom toolbox and tried to add that Twrp or what ever its caled custoer recovery (ot Clockwork mod)
Then selected boot to recover and its now stuck on a boot loader screen and will no go anwehere other than that pretty mch,, if i reboot it has the htc logo a warning about this beinga dev and then back to bootloader witch says s-on tampered and locked..
Im trying everyting and i got my boot loader key thing but i cant submit it to htc cause im guessing att wants it to sstay locked..
I cannot boot into the rom or anything i have a downloaded folder of http://www.mediafire.com/?d41k2x8sm9gesup
and tried to flash the fastboot cache still... notta..
What do i do to get out of this.. to unlock it and et back to root or even back to 1.85.. anything
Click to expand...
Click to collapse
Hold the power button until the phone shuts off, then try booting it up and see if it actually boots
EDIT: Just seen you did try to reboot...my bad. Like guy above me said try an RUU

after googling to death the only one i could find is a exe that needs to be dont via the phone being in the on working state, got any links for a ruu to flash?

The sticky at the top of the forum has the links:
http://forum.xda-developers.com/showthread.php?t=1671237
You can flash an RUU while in bootloader mode.
Your problem is that you didn't unlock the bootloader and you are running a third party recovery. The security "features" of the bootloader being locked and you being S-ON prevent the phone from booting.

Well you would have had to have rooted it first before installing a custom recovery like twrp.
To get back, you'll want to:
Download the RUU file from this link
http://forum.xda-developers.com/showthread.php?t=1670238
Download the HTC driver from this link
HTCDriver3.0.0.007.exehttp://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
Install the HTC driver and restart your computer
Plug in your phone and run the Ruu.exe file
This will put your phone back to the way it was when you bought it.
Then, take some time and read the threads about rooting and installing twrp before trying again.
Also, try not to post questions in the Dev section.

z28james said:
The sticky at the top of the forum has the links:
http://forum.xda-developers.com/showthread.php?t=1671237
You can flash an RUU while in bootloader mode.
Your problem is that you didn't unlock the bootloader and you are running a third party recovery. The security "features" of the bootloader being locked and you being S-ON prevent the phone from booting.
Click to expand...
Click to collapse
Yea realized what i did after i did it.. I have a Thnderbolt on verizon and also had to s-off. I figured out where to get a ruu i think for the moment so ty lets hope lol

mod should probably move this one to q&a.
Sent from my One X using xda app-developers app

im following this http://forum.xda-developers.com/show...709296&page=38
and so i did this and it worked ok i think on the first try.... like a idiot i attempted to flash a recovry wit s-on and the bootloader lockd so i got stuck in a bootloader loop and then was able to ruu back to 1.85 on att.. now i do excatly the instructions and when i get to
adb shell ls -l /data/local.prop
i get "no such file or directory"
and i have changed dates up the wazoo forwards backwards back to the current, reset the phone by factory wipe and reset via bootloader.. im stuck
also if it matters i get no such file or dir on
adb shell rm /data/data/com.redbend.vdmc/lib/libvd
and link failed file exists on
adb shell ln -s /data/local.prop /data/data/com.redbend.vdmc/lib/libvdmscomo.so

Mortland said:
im following this http://forum.xda-developers.com/show...709296&page=38
and so i did this and it worked ok i think on the first try.... like a idiot i attempted to flash a recovry wit s-on and the bootloader lockd so i got stuck in a bootloader loop and then was able to ruu back to 1.85 on att.. now i do excatly the instructions and when i get to
adb shell ls -l /data/local.prop
i get "no such file or directory"
and i have changed dates up the wazoo forwards backwards back to the current, reset the phone by factory wipe and reset via bootloader.. im stuck
also if it matters i get no such file or dir on
adb shell rm /data/data/com.redbend.vdmc/lib/libvd
and link failed file exists on
adb shell ln -s /data/local.prop /data/data/com.redbend.vdmc/lib/libvdmscomo.so
Click to expand...
Click to collapse
First, you double posted in the Dev section,, if you browse this forum you'll quickly realize that there a no other questions in here..... As such your thread is going to be moved, and you'll probably be flamed more than I'm flaming you now.
Second, if your bootloader was locked how did you try to flash TWRP, If you're still locked are you tampered? Just flash a stock RUU. If 1.85 doesn't work flash a newer one, and then pray to god someone roots it.
Third, with the S-OFF ,, well I would like to know what this has to do with anything as this hasn't been achieved yet. You obviously did a ton of reading before you embarked on your noob flashing.
If you're locked and not tampered (which I doubt) just take your phone back to the store and give them some BS like your battery is bad and have them swap you phone out (if you're ATT).
EDIT: I re-read this. Ignore everything I said with the exception of you posting in the wrong forums. I see you don't even have a One X .... dude ... quit posting here and make a new thread

HydroSkillet said:
EDIT: I re-read this. Ignore everything I said with the exception of you posting in the wrong forums. I see you don't even have a One X .... dude ... quit posting here and make a new thread
Click to expand...
Click to collapse
He said he's trying to root/mod his friends One X (while he himself has a Thunderbolt). But yeah, its confusing.
---------- Post added at 09:27 AM ---------- Previous post was at 09:23 AM ----------
Mortland said:
installed Rom toolbox
Click to expand...
Click to collapse
AFAIK, there is no ROM Toolbox that works for this device. That was probably your biggest mistake. Don't install/flash/mod things willy-nilly before doing the proper research. Every Android device is rooted, S-Off etc. a bit (or very) differently. Lots has changed on HTC phones since the Thunderbolt. Just because something worked for that phone, does not mean it will on the One X.
Back off, and do the proper research before doing anything else. Stick to this subforum (AT&T One X) and don't go Googling around on random sites. Everything you need is here, and safe. At least you have bootloader, so you can probably recover. Mess with it more, without knowing what you are doing, and you may well hard brick it.
You can start your research by reading the sticky at the top of this forum that says not to post questions in Development.
---------- Post added at 09:33 AM ---------- Previous post was at 09:27 AM ----------
Mortland said:
im following this http://forum.xda-developers.com/show...709296&page=38
Click to expand...
Click to collapse
Link is broken, can't tell what you are trying to do.
Your best bet is to flash a stock RUU, I'd start with the 1.85 one. RUUs can be found here: http://forum.xda-developers.com/showthread.php?t=1671237
Make sure your bootloader screen says LOCKED or RELOCKED. If it somehow got UNLOCKED in your tinkerings, you will need to get RELOCKED (RUU will not run with bootloader unlocked). But that is likely not the case.

SIM unlock didn't work, factory reset wiped everything, phone doesn't boot.

But wait, there's more.
I just exchanged an Xperia S for this HTC One S in excellent condition. It was already bootloader unloked, has TWRP only that it was sim locked. I tried the unlock.sh script (both from terminal emulator, and root explorer) then manually getting the UN_lock_code and subtracting the reversed 7 digits from the IMEI (with the added one), and even the automated app. The script kept running and never show the unlock code, and the one I got using this method wasn't accepted.
Then I thought I should to a factory reset and try again. So I reboot to bootloader, chose factory reset and now everything is wiped. No OS installed so I can't boot, TWRP won't mount USB storage so I can' flash any other rom.
Please help.

Is this a ville or the ville C2?
From your hbot, it seems like C2

42freelancer said:
Is this a ville or the ville C2?
From your hbot, it seems like C2
Click to expand...
Click to collapse
It is a C2, yes. How does that help me?
edit: Well, some good news is that I managed to be able to mount USB storage from TWRP (a simple FORMAT in windows seems to have fixed it). Any particular rom I should flash before attempting to sim unlock again?

cars ontols
zgomot said:
It is a C2, yes. How does that help me?
edit: Well, some good news is that I managed to be able to mount USB storage from TWRP (a simple FORMAT in windows seems to have fixed it). Any particular rom I should flash before attempting to sim unlock again?
Click to expand...
Click to collapse
Knowing that it is C2 will prevent you from flashing a ROM that isn't compatible with your phone. From experience, I'd go with PAC Rom. It has a ton of features, and should allow you to do anything you want. As far as SIM unlocking, shouldn't you be S-Off first?
And you formatted the phone via Windows? I've never heard of such a thing, never mind it actually fixing a problem.
But if it ain't broke, don't fix it. And your issue seems to be resolved for the most part. Regarding booting, that is.

42freelancer said:
Knowing that it is C2 will prevent you from flashing a ROM that isn't compatible with your phone. From experience, I'd go with PAC Rom. It has a ton of features, and should allow you to do anything you want.
Click to expand...
Click to collapse
How about ViperSC2? Will that do?
42freelancer said:
As far as SIM unlocking, shouldn't you be S-Off first?
Click to expand...
Click to collapse
I'm not sure, tbh, do I? But if I do, that's what I'll do first, however, I don't recall reading anywhere S-OFF being a prerequisite to sim unlocking.
42freelancer said:
And you formatted the phone via Windows? I've never heard of such a thing, never mind it actually fixing a problem.
But if it ain't broke, don't fix it. And your issue seems to be resolved for the most part. Regarding booting, that is.
Click to expand...
Click to collapse
Well yeah... oddly enough... I formatted the phone's internal storage via windows and then I was able to mount it as USB storage from recovery.
further edit: I managed to flash a rom and boot the phone.

For the sake of trying everything, I would s-off first. The easiest way is from stock right after running an RUU, without a custom recovery, No SU or busybox, and a locked bootloader. Moonshine worked for me after trying all the other methods.
I personally love the Viper ROMS. I only wish they would have kept updating the ones for the ONE S and slammed kitkat into it. It would be my daily driver. I use a ville with dirty unicorn 4.4. It's my daily driver.
Awesome that you got it mounted. Maybe that forced the drivers to reinstall properly. Did you check for fastboot and ADB functionality and visibility from the computer? You'll need both of those before attempting s-off.
Sent from my One S using xda app-developers app
---------- Post added at 07:32 PM ---------- Previous post was at 06:59 PM ----------
zgomot said:
How about ViperSC2? Will that do?
I'm not sure, tbh, do I? But if I do, that's what I'll do first, however, I don't recall reading anywhere S-OFF being a prerequisite to sim unlocking.
Well yeah... oddly enough... I formatted the phone's internal storage via windows and then I was able to mount it as USB storage from recovery.
further edit: I managed to flash a rom and boot the phone.
Click to expand...
Click to collapse
Not sure if you saw my last post before this one, I forgot to reply with your quote.

42freelancer said:
For the sake of trying everything, I would s-off first. The easiest way is from stock right after running an RUU, without a custom recovery, No SU or busybox, and a locked bootloader. Moonshine worked for me after trying all the other methods.
I personally love the Viper ROMS. I only wish they would have kept updating the ones for the ONE S and slammed kitkat into it. It would be my daily driver. I use a ville with dirty unicorn 4.4. It's my daily driver.
Awesome that you got it mounted. Maybe that forced the drivers to reinstall properly. Did you check for fastboot and ADB functionality and visibility from the computer? You'll need both of those before attempting s-off.
Sent from my One S using xda app-developers app
---------- Post added at 07:32 PM ---------- Previous post was at 06:59 PM ----------
Not sure if you saw my last post before this one, I forgot to reply with your quote.
Click to expand...
Click to collapse
adb devices lists the phone, however fastboot devices does not... it keeps waiting for device. I tried this fix for windows 8.1 but I can't get it to take the modded drivers. It says it finds them but can't install because the system supposedly cannot find the file.

That seems to be an issue with Windows 8.1. It also seems to be the only OS affecting fastboot. There is a file I used to get all of my drivers working properly, with ADB and fastboot. Fastboot is required with any S-Off attempt. I'll go scope out the file and return here.
---------- Post added at 08:04 PM ---------- Previous post was at 07:59 PM ----------
zgomot said:
adb devices lists the phone, however fastboot devices does not... it keeps waiting for device. I tried this fix for windows 8.1 but I can't get it to take the modded drivers. It says it finds them but can't install because the system supposedly cannot find the file.
Click to expand...
Click to collapse
Try this! This should work: http://forum.xda-developers.com/showthread.php?t=2588979
This is what I used last night to reinstall my drivers with working ADB and Fastboot. It also comes with a picture guide on how to fix the device detection. It's fast, easy, lightweight, and best of all, it works!

Your help is really appreciated.
I already tried this fix as well but I get the same error message. Damn system can't seem to find the file when I am pointing it to it...
I need to get some sleep now, will try more tomorrow.

Tried that and I still can't get fastboot devices to enumerate my device. Pfffft.

zgomot said:
Your help is really appreciated.
I already tried this fix as well but I get the same error message. Damn system can't seem to find the file when I am pointing it to it...
I need to get some sleep now, will try more tomorrow.
Click to expand...
Click to collapse
No sweat. I've got nothing going on later, so I'll do some research for ya! Night

OK, I managed to get fastboot working, but not S-OFF. Moonshine doesn't work, it keeps saying something needs to be fixed and that I need to read, haha funny. Thing is I followed the exact procedure and met all the prerequisites except for being on a stock ROM.
Currently I am running ViperS C2 5.1.0 baseband 16.22.30.03U_16.11.20.24_M, build number 3.19.401.101. I tried a couple RUUs but none worked. Which am I to use? What next?

zgomot said:
OK, I managed to get fastboot working, but not S-OFF. Moonshine doesn't work, it keeps saying something needs to be fixed and that I need to read, haha funny. Thing is I followed the exact procedure and met all the prerequisites except for being on a stock ROM.
Currently I am running ViperS C2 5.1.0 baseband 16.22.30.03U_16.11.20.24_M, build number 3.19.401.101. I tried a couple RUUs but none worked. Which am I to use? What next?
Click to expand...
Click to collapse
What is your carrier and CID? MAybe I have a RUU downloaded. I tend to grab them all. 2tb space, plus tons of cloud storage.
[EDIT] I also posted a thread on how to s-off, if that helps. I'll still look for the appropriate RUU.
http://forum.xda-developers.com/showthread.php?t=2652601

42freelancer said:
What is your carrier and CID? MAybe I have a RUU downloaded. I tend to grab them all. 2tb space, plus tons of cloud storage.
[EDIT] I also posted a thread on how to s-off, if that helps. I'll still look for the appropriate RUU.
http://forum.xda-developers.com/showthread.php?t=2652601
Click to expand...
Click to collapse
CID: HTC__032 And when you ask about my carrier do you mean the one I want to use? It's Vodafone Romania and so far I'm sure the phone works with Orange Romania. Other networks I haven't tried.

zgomot said:
CID: HTC__032 And when you ask about my carrier do you mean the one I want to use? It's Vodafone Romania and so far I'm sure the phone works with Orange Romania. Other networks I haven't tried.
Click to expand...
Click to collapse
I found this repository with some RUU. The last one is the most recent and the closest to your radio version. Reverting flashing this RUU should update your radio to match it. Once stock, you should have the ability to s-off and will have a new kernel. Have you tried flashing the kernel through fastboot?

42freelancer said:
I found this repository with some RUU. The last one is the most recent and the closest to your radio version. Reverting flashing this RUU should update your radio to match it. Once stock, you should have the ability to s-off and will have a new kernel. Have you tried flashing the kernel through fastboot?
Click to expand...
Click to collapse
If you mean this one then I tried that and eventually it gives error 131 CUSTOMER ID ERROR and saying it cannot update my device.

zgomot said:
If you mean this one then I tried that and eventually it gives error 131 CUSTOMER ID ERROR and saying it cannot update my device.
Click to expand...
Click to collapse
Was your bootloader UNLOCKED when you tried that update? Because RUU require that the bootloader be LOCKED before they have the ability to flash.
fastboot oem lock
if you didn't know.
Other than that, I'm at a loss. Until you find the appropriate RUU i guess

42freelancer said:
Was your bootloader UNLOCKED when you tried that update? Because RUU require that the bootloader be LOCKED before they have the ability to flash.
fastboot oem lock
if you didn't know.
Other than that, I'm at a loss. Until you find the appropriate RUU i guess
Click to expand...
Click to collapse
Nope. Bootloader is Relocked.
Now I'm facing another problem. I flashed TWRP via WinDroid HTC ONE S Toolkit and now, when I chose recovery from HBOOT, I get a red triangle with an exclamation mark.
edit: the red triangle was due to flashing TWRP on a locked bootloader. What I plan to do do now is flash this stock rom and try getting S-OFF and eventually sim unlock from there.
*fingers crossed*
further edit: apparently my cid is not supported by this rom.

zgomot said:
Nope. Bootloader is Relocked.
Now I'm facing another problem. I flashed TWRP via WinDroid HTC ONE S Toolkit and now, when I chose recovery from HBOOT, I get a red triangle with an exclamation mark.
edit: the red triangle was due to flashing TWRP on a locked bootloader. What I plan to do do now is flash this stock rom and try getting S-OFF and eventually sim unlock from there.
*fingers crossed*
further edit: apparently my cid is not supported by this rom.
Click to expand...
Click to collapse
You will have to SuperCID then. That requires S-Off most of the time. Back to stock it seems. The RUU hunt continues. I've been looking for you, just to see if I stumble upon it.
[EDIT] http://forum.xda-developers.com/showthread.php?t=2644607 TRY THE FIRST RUU HERE! This one is the same CID as your carrier. it may upgrade your radio and hboot.

42freelancer said:
You will have to SuperCID then. That requires S-Off most of the time. Back to stock it seems. The RUU hunt continues. I've been looking for you, just to see if I stumble upon it.
[EDIT] TRY THE FIRST RUU HERE! This one is the same CID as your carrier. it may upgrade your radio and hboot.
Click to expand...
Click to collapse
PROGRESS!
I managed to get S-OFF. Do I try sim-unlocking now, or is there anything else I have to do first?

I think I bricked my HTC One X AT&T

Hello everyone,
I am in trouble but not sure if I bricked my HTC One X AT&T hboot 1.09 or not
Here is what happened:
I had Android 4.0.3 running and rooted with bootloader unlocked.
S-ON for sure.
Yesterday I tried to install custom rom or I thought if anything wrong goes bad I would upgrade it to the latest
4.2.2 from HTC.
with some commands from the fastboot I believe I distressed the entire system to the point where it cannot boot.
the only thing my device is doing now is just booting to the screen where HTC in green and the red text beneath it or I can go to the
bootloader menu.
I tried to fix this by flashing openrecovery-twrp-2.4.1.0-evita.img
it worked, and I was able to push several ROMs but non of them got installed, I kept getting error status 7.
I wiped everything from the recovery and then locked the bootleader and now I am really really stuck.
just the bootloader is showing.
One last experiment I tried to do, I put my device into fastboot and run the RUU for one of the ROM I downloaded for my device
but I only see a black screen with HTC logo and it kept me waiting more than half hour, I knew this will not work but I thought I would try.
Is my device done and I should through it away or there is a hope of fixing it?
I had this device for more than 2 years so no way AT&T would help, that's my guess.
Please guys, any suggestion? I am all for fixing it.
It was a stupid mistake ahhhh.
Thanks in advance.

Wrong forum mate, this is for the international hox quad-core version. You have to be in the at&t HTC one XL forum.

Mr Hofs said:
Wrong forum mate, this is for the international hox quad-core version. You have to be in the at&t HTC one XL forum.
Click to expand...
Click to collapse
Sorry, is there anyway someone can move this thread to the appropriate forum.
I apologize.

I will report this one to get it moved. Good luck in the correct section

Moved to: AT&T, Rogers HTC One X, Telstra One XL > One X Q&A, Help & Troubleshooting.
(mod team)

Looks like you've possibly made several mistakes there. First problem is you've been lurking in the wrong forum, which means you've probably been trying to flash ROMs that aren't for our device. Our device forum is here:
http://forum.xda-developers.com/forumdisplay.php?f=1538
Bookmark that page and make sure you stay within our forum. Flashing ROMs/kernels/radios that aren't intended for our device can very easily result in a bricked phone.
I think your phone is fine as long as you can get it into the bootloader. Your problem when you were flashing ROMs is that TWRP 2.4.x and 2.5.x are buggy and are basically useless. This is probably a blessing in disguise if you were attempting to flash the wrong ROM, it probably saved your ass. Download at least TWRP 2.6 from here and you should be able to flash with no problems, just make sure they're actually our Evita ROMs that you're flashing.
Now, just to make sure this doesn't happen again, what were the commands you issued through fastboot that "distressed" your system? I need to know what you were doing that caused your device to falter. Also, don't ever run a jb RUU while you're s-on or you'll definitely brick your phone, doing that (SuperCID + s-on + jb RUU) has a 100% kill rate.
As a piece of advice, I'd suggest you stop "experiencing" with your device because the experiments you've been conducting could have easily bricked your phone on several occasions. You're extremely lucky. It seems to me that you need to do some research about our device and what you can and can't do with it. A good place to start would be my Evita FAQ and How-To Guide For Beginners threads in my signature, and build from there.
Sent from my Evita

You are not bricked. With this phone, as long as the screen comes on, you are almost certainly not bricked. You just don't know how to recover.
shakash3obd said:
with some commands from the fastboot I believe I distressed the entire system to the point where it cannot boot.
Click to expand...
Click to collapse
What the heck does "some commands" mean? You need to be specific about the exact steps you took. If you don't know the commands you tried, that is a problem, as it implies you are not being careful while modding the phone.
shakash3obd said:
I tried to fix this by flashing openrecovery-twrp-2.4.1.0-evita.img
it worked, and I was able to push several ROMs but non of them got installed, I kept getting error status 7.
Click to expand...
Click to collapse
That is a very outdated version of TWRP, and probably part of your problem. Use an up to date version.
shakash3obd said:
One last experiment I tried to do, I put my device into fastboot and run the RUU for one of the ROM I downloaded for my device
but I only see a black screen with HTC logo and it kept me waiting more than half hour, I knew this will not work but I thought I would try.
Click to expand...
Click to collapse
You can't (and shouldn't) just run any RUU. You should run the proper RUU for your carrier version (AT&T) and with s-on it has to be equal or later then the hboot version on the phone. Also do not run a Jellybean RUU on the phone, since SuperCID + S-on will brick the device on most Jellybean RUUs. You're okay if the screen is coming on, but don't run any RUUs unless somewhere here specifically instructs you to.
You have a couple options to proceed:
1) Re-unlock the bootloader, install an updated TWRP version, and try flashing a custom ROM.
2) If still on hboot 1.09, try running the 1.73 or 1.85 RUU (do you remember what build number you were on when you unlocked the bootloader?).

shakash3obd said:
I had this device for more than 2 years so no way AT&T would help, that's my guess.
Click to expand...
Click to collapse
AT&T warranties phones for 1 year. So you are out of the warranty period, if that is what you are wondering about. And warranty covers manufacturing defects, not damage done by the owner due to their negligence.
Besides, you don't need a repair or replacement. You just need to know how to recover properly from what you have done.

timmaaa said:
Download at least TWRP 2.6 from here and you should be able to flash with no problems, just make sure they're actually our Evita ROMs that you're flashing.
...
Now, just to make sure this doesn't happen again, what were the commands you issued through fastboot that "distressed" your system?
....
Click to expand...
Click to collapse
Thanks for stopping by,
I believe that I cannot flash any recovery mod such as clockwork or TWRP now, because as I explained. I locked the bootloader again.
I attempted to unlock it using the htcdev unlock bin file that they sent me but in the terminal I got the message
sending 'unlocktoken' (0 KB)...
OKAY [ 0.142s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.148s
that's why I am stock in the bootloader.
I didn't mean 'distressed' I was trying to say I destroyed, spilling correction mistake.
to be honest with you, there were 10's of fastboot commands that I tried some are related to s-off even.
but I think what killed the system is this
fastboot flash file.img
and the file was extracted from a ROM
CARBON-KK-NIGHTLY-20140319-1133-endeavoru
I now realize it's wrong. Please do not judge me :crying:

redpoint73 said:
That is a very outdated version of TWRP, and probably part of your problem. Use an up to date version.
You have a couple options to proceed:
1) Re-unlock the bootloader, install an updated TWRP version, and try flashing a custom ROM.
2) If still on hboot 1.09, try running the 1.73 or 1.85 RUU (do you remember what build number you were on when you unlocked the bootloader?).
Click to expand...
Click to collapse
Thanks for your comments.
I put the command I used in the previous reply.
As far as the version of TWRP, I originally tried the latest one, but it wont flash at at that's why I tried an older version.
Again in my previous reply i said that I am not able to Re-unlock the bootloader.
Yes I am still in hboot 1.09 but don't remember the build number unfortunately.
Because all what I am in is because of my lack of knowledge of custom roms, would you be able to
point me to where I can download 1.73 or 1.85 RUU?
Also, Do you think I will be able to run RUU even from the bootloader menu. I tried to run RUU from the bootloader and it got stock in the
black screen with HTC logo forever!!

shakash3obd said:
Thanks for stopping by,
I believe that I cannot flash any recovery mod such as clockwork or TWRP now, because as I explained. I locked the bootloader again.
I attempted to unlock it using the htcdev unlock bin file that they sent me but in the terminal I got the message
sending 'unlocktoken' (0 KB)...
OKAY [ 0.142s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.148s
that's why I am stock in the bootloader.
I didn't mean 'distressed' I was trying to say I destroyed, spilling correction mistake.
to be honest with you, there were 10's of fastboot commands that I tried some are related to s-off even.
but I think what killed the system is this
fastboot flash file.img
and the file was extracted from a ROM
CARBON-KK-NIGHTLY-20140319-1133-endeavoru
I now realize it's wrong. Please do not judge me :crying:
Click to expand...
Click to collapse
I won't judge you, I'm here to try and help you. Go to htcdev and try unlocking the bootloader again from scratch, hopefully that'll work. If not, I'm really not sure what you can do. In future, just be careful and make sure know exactly what you're doing before you do it. Fastboot commands have very specific functions and should only be used in specific situations, issuing random commands is a bad idea. I you're unsure about anything or if you have any question at all please feel free to ask here or in my q&a thread.
Sent from my Evita

timmaaa said:
Go to htcdev and try unlocking the bootloader again from scratch, hopefully that'll work.
Sent from my Evita
Click to expand...
Click to collapse
I just did that and I got the following message from htcdev website
Unlocking Bootloader Instructions
We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won't work.
So, that's another route that will lead to no fix
Thanks again

shakash3obd said:
I just did that and I got the following message from htcdev website
Unlocking Bootloader Instructions
We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won't work.
So, that's another route that will lead to no fix
Thanks again
Click to expand...
Click to collapse
That message suggests that you haven't copied the identifier token correctly. You need to make sure you copy the whole thing, including all of the arrows at the beginning and end.
Sent from my Evita

shakash3obd said:
I just did that and I got the following message from htcdev website
Unlocking Bootloader Instructions
We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won't work.
So, that's another route that will lead to no fix
Thanks again
Click to expand...
Click to collapse
That error message simply means you cut and pasted the token incorrectly (included an extra character or characters that you were not supposed to). Follow the instruction very carefully and exactly for what exactly needs to be cut and pasted.
---------- Post added at 03:43 PM ---------- Previous post was at 03:37 PM ----------
shakash3obd said:
would you be able to
point me to where I can download 1.73 or 1.85 RUU?
Click to expand...
Click to collapse
All you will mostly likely ever need for this device is in my Index thread:
http://forum.xda-developers.com/showthread.php?t=1671237
shakash3obd said:
Also, Do you think I will be able to run RUU even from the bootloader menu. I tried to run RUU from the bootloader and it got stock in the
black screen with HTC logo forever!!
Click to expand...
Click to collapse
RUU is meant as a recovery tool, and therefore is intended to work while the phone is in almost any condition (as long as the screen comes on), including bootloader.
The reason the RUU did not work, is likely because it was the wrong RUU.
---------- Post added at 03:54 PM ---------- Previous post was at 03:43 PM ----------
shakash3obd said:
I attempted to unlock it using the htcdev unlock bin file that they sent me but in the terminal I got the message
sending 'unlocktoken' (0 KB)...
OKAY [ 0.142s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.148s
that's why I am stock in the bootloader.
Click to expand...
Click to collapse
The bootloader unlock is a bit finicky, and its known to fail for some folks for no good reason (even if you did it all correct), possibly even numerous times. I would suggest just making sure you do the steps correctly and keep trying.
shakash3obd said:
to be honest with you, there were 10's of fastboot commands that I tried some are related to s-off even.
but I think what killed the system is this
fastboot flash file.img
and the file was extracted from a ROM
CARBON-KK-NIGHTLY-20140319-1133-endeavoru
I now realize it's wrong. Please do not judge me
Click to expand...
Click to collapse
The only judgement I have of you, is that you seem to be rushing forward a bit too much, and not researching properly.
Fastboot (and phone modding in general) is not a place to be experimenting. You should not be trying fastboot commands haphazardly. I've seen more than a few devices on this forum bricked with a couple careless fastboot commands. I would recommend you not running any fastboot commands, unless you have obtained them from one of the established guides on this forum, or from a reputable/knowledgeable contributor on this forum.

redpoint73 said:
All you will mostly likely ever need for this device is in my Index thread:
http://forum.xda-developers.com/showthread.php?t=1671237
Click to expand...
Click to collapse
Hey guys, I got my device unlocked, i think I copied an extra character.
Now I have an unlocked bootloader + recovery mod 2.6.0.
What should I do next?
should I download RUU from your thread or should should I do something else?
I
I am waiting right here right now until my phone is fixed.
Thank you so much guys
EDIT:
I tried to download RUU 1.73 and the links were down
so i downloaded 1.85 for now.
Waiting for your other instructions. Sir.

shakash3obd said:
Hey guys, I got my device unlocked, i think I copied an extra character.
Now I have an unlocked bootloader + recovery mod 2.6.0.
What should I do next?
should I download RUU from your thread or should should I do something else?
Click to expand...
Click to collapse
Download a custom ROM, move it to your phone, and flash it.
If a custom ROM is what you wanted to begin with, no reason to go backward and RUU (since you were able to get the bootloader unlocked again, and custom recovery installed).

redpoint73 said:
Download a custom ROM, move it to your phone, and flash it.
If a custom ROM is what you wanted to begin with, no reason to go backward and RUU (since you were able to get the bootloader unlocked again, and custom recovery installed).
Click to expand...
Click to collapse
This is actually my original intention, I don't want to have all the junk that comes from HTC and the one from AT&T.
Any recommendation to get something like the kitkat rom that is stable and reliable.
I am asking for recommendation because after all trouble I went through last night, I just want to get my phone to something very nice and stable other than the RUU with HTC and AT&T stuff.
Really appreciate your help.

shakash3obd said:
Any recommendation to get something like the kitkat rom that is stable and reliable.
I am asking for recommendation because after all trouble I went through last night, I just want to get my phone to something very nice and stable other than the RUU with HTC and AT&T stuff.
Click to expand...
Click to collapse
Best/recommended/favorite ROM discussions are not allowed on XDA. They are each good in their own way, and everyone has different preferences. Part of the fun of flashing custom ROMs is trying them out, to see what you like the best.
Try any of the ROMs on my Index thread, and you won't need to worry about a brick. But read through the specific ROM thread as some ROMs have specific flashing procedures.
Bear in mind that KitKat means you will be on an AOSP ROM. Sense is limited to Jellybean, for now.
---------- Post added at 04:35 PM ---------- Previous post was at 04:33 PM ----------
shakash3obd said:
Thank you so much guys
Click to expand...
Click to collapse
Feel free to click the "Thanks" button for any posts that you found helpful.

redpoint73 said:
Best/recommended/favorite ROM discussions are not allowed on XDA.
Try any of the ROMs on my Index thread, and you won't need to worry about a brick. But read through the specific ROM thread as some ROMs have specific flashing procedures.
Bear in mind that KitKat means you will be on an AOSP ROM
.
Click to expand...
Click to collapse
I will check the index of yours when I find it since I am always lost in the xda forum.
Sorry to ask for something not allowed in XDA, I will start looking for AOSP ROM since I want something like KitKat.
If we can forget about "recommendation/best ROM" will anyone can point me to where to find KitKat like ROM for my device or
give a list of names or links to threads in XDA. Or even the whole forum starting point for which i can find these type of ROMs
just to avoid bricking my device since it's S-On

redpoint73 said:
RUU is meant as a recovery tool, and therefore is intended to work while the phone is in almost any condition (as long as the screen comes on), including bootloader.
The reason the RUU did not work, is likely because it was the wrong RUU.
Click to expand...
Click to collapse
What I was afraid of is happening, I run RUU 1.85 and I am right now passed 50 minute with the phone screen is black with HTC logo on it.
is this normal?
should I be doing anything? or just wait more or unplug the phone from the PC?