Database Info

[Q] htc one x at&t soft brick help please :(

:crying: please somebody help me, im desperate, my dad just bought me the htc one x at&t for a gift after my galaxy s 2 got stolen a while back, i had previous exerience rooting, unlocking, and modding basic stuff, the only thing i didnt like about the phone was the multitasking button instead of a menu button, so i rooted it and unlocked the bootloader using the method on onexroot.com and it all worked and i installed twrp recovery, but when i flashed the button remap (cant remember which one) it now gets stuck at the one x screen, i figured this wasnt a problem and i could just download another rom and flash it, but from recovery usb wont moun it get and error something like
something about the sdcard
checking partitions
E: cant mount sd card
E: failed to open lunfile (doesnt exist)
i might be messing up but i am unable to get it to appear in adb always says device not found
am i screwed? am i stuck with a broken rom that cant be fixed?
Please help, it will mean the world to me

Uh read up on ODIN. I used it to get my friends SGS out of a soft brick. I'm not sure if it's for the one x though. What it does is after you put your phone into recovery mode or force pushes a ROM to the SD card then flashes it. Also try googling a tool to force it into recovery. ODIN might I'm not too sure though.
Sent from my HTC One X using XDA

Can you load into the bootloader..?
<Hold power button for ~10 seconds until the buttons flash at the bottom>
<Once its off, hold the power button and the Volume Down [NOT UP = Very bad]>
That should load up the bootloader. Then you can attempt to go into the recovery again OR reinstall it through bootloader.
Now if that doesn't work, You can attempt running the 1.85 RUU from your computer. It <might> overwrite all existing partitions and create a solid and fresh foundation for re-rooting and all.

And to answer your question if you're screwed, in my experience it is almost never an issue to get your phone out of a soft brick as long as you can access some sort of recovery.
Sent from my HTC One X using XDA

heres the rundown
bootloader - yes
recovery - yes
adb - no
fastboot - yes
mount storage - no (makes recovery kinda useless)
i sure hope im not screwed, but since i cant find a way to get a clean rom on the phone i dont see a way to fix it, odin is strictly samsung sadly, and i know nothing about ruu, i dont care about root or anything anymore i just want my phone to work so whatever it takes

Ok, I wasnt sure about ODIN. Try an RUU. Basically an RUU is an .exe or executable file that is almost completely automated that flashes the complete package (Rom, radio, kernel). It might not work depending on what you have installed on windows (drivers and such). You might have to uninstall HTC drivers & sync and try again if that doesn't work install the drivers only then rerun the RUU. RUU is your best bet now. Download one and start the exe. Remember if you're on Mac OSX or linux you're going to have to use a Virtual machine or windows emulator to run the RUU
Sent from my HTC One X using XDA

Pm me if you need further help
Sent from my HTC One X using XDA

i have my mac dualbooted with windows 8 consumer preview, interestingly fastboot doesnt work on the windows end but it does on a mac, im gunna assume i did more than one thing wrong when i previously tried (failed to detect device) to ruu it, where do i get the ruu, where do i get the drivers, and if i use a virtual machine do i need the drivers?
your help is much appreciated

Mac OSX is not the right platform to be using nor is windows 8 (because it is unproven and still in beta). I would recommend using a fresh installation. If you have a windows 7 .ISO you can install it and use it for 30 days before they lock you out with out a key.
Here is a helpful tool to install it as fast as possible VIA USB (provided you have a >4GB drive) http://www.microsoftstore.com/store/msstore/html/pbPage.Help_Win7_usbdvd_dwnTool
If you are running Mac OSX here is an XDA developers guide for linux (Mac OSX is based off of Free BSD a linux distribution) by Jeepfreak. The process will differ some but not a lot.
Here it is....
http://forum.xda-developers.com/showthread.php?t=1668156
I want to emphasize NOT using Windows 8... It is unproven Beta software....

i have a computer i can use, it has vista, but i would need to go where i can get wifi and know the exact files i need to download as i have a horribly slow connection off a mifi card an am pushing my cap as it is, if you could tell me exactly what to download and run i would be increadibly greatful

http://forum.xda-developers.com/showthread.php?t=1649658 This is still rootable
or
http://forum.xda-developers.com/showthread.php?t=1644338 This is the RUU the phone likely shipped with
Transfer the RUU's to your Vista comp using a USB drive.
Make sure you don't have HTC Sync or if you do it is not running in the background.

ok so i download the ruu, got that, i think i have the android sdk on that computer, will that cover any drivers i need? and for the ruu what to i have to do on the phone end?

i ran "fastboot getvar version-main" and it returned "version-main: 1.73.502.1" will the difference between .502 vs .502.1 make a differnece?

Shouldn't make a difference.... And i would try running the RUU first then download the necessary drivers if that doesn't work...

Jtn.Siren said:
i ran "fastboot getvar version-main" and it returned "version-main: 1.73.502.1" will the difference between .502 vs .502.1 make a differnece?
Click to expand...
Click to collapse
The .1 is for att. But you'll want to run the ruu in fast boot that's either the same version or a higher version like 1.85.502.1.
Sent from my HTC One X using xda premium

thank you so much thus far, as a matter a fact i already have the 502.1 downloaded, could you please explain to me any drivers, files, and commands i will need to execute this

dkirchik said:
The .1 is for att. But you'll want to run the ruu in fast boot that's either the same version or a higher version like 1.85.502.1.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Yes but if he trys to root it all bets are off unless he did superCID. I would recommend the first RUU I posted
---------- Post added at 12:24 PM ---------- Previous post was at 12:22 PM ----------
Jtn.Siren said:
thank you so much thus far, as a matter a fact i already have the 502.1 downloaded, could you please explain to me any drivers, files, and commands i will need to execute this
Click to expand...
Click to collapse
The drivers you can get off of htc's website under ATT ONE X, or just search XDA for them...
You do not need any commands to run an RUU. Like I said it is completely automated...

and what mode on the phone off, bootloader, fastboot?

Jtn.Siren said:
and what mode on the phone off, bootloader, fastboot?
Click to expand...
Click to collapse
Try Bootloader then Recovery. It usually does it for you though if you were booted into a ROM.

Jtn.Siren said:
and what mode on the phone off, bootloader, fastboot?
Click to expand...
Click to collapse
Irish has it right and fastboot make sure the fasboot USB is there. Then open and run the RUU and you're golden.
Sent from my HTC One X using xda premium

Help!!!Messed it up

Hello dear members, Ok to start with I am having One X at&t and I am using it at the moment in Pakistan. It is sim unlocked. I was new to this rooting stuff but I already had a lot of experience with jailbreaking iphone stuff so I thought there should be no problem.
I started with rooting and after going through all the threads on this forum plus other websites I was able to root my cell and then I unlocked the bootloader. I was having difficulty with the drivers as I am using windows 8 but somehow managed to fix it (Thanks to xda forums).At this point I thought of upgrading to ota update but since I am out of range of at&t so I tried to manually install it by PC. Now when I tried to install, it was stuck on waiting for bootloader menu and then ultimately gave "error 171" "please check if your phone is connected by USB cable" .I checked the drivers they are properly installed and device manager recognizes my phone in bootloader menu too. I again surfed the net and forums and realized I have to relock the bootloader before installing RUU. So I relocked the bootloader by "fastboot oem lock" command and then tried again but no luck. But this time this thing happened when the cell screen was stuck at "blank screen+htc logo" and I got the error 171, I restarted my device and it automatically opened bootloader menu which on the top says *tampered* then *relocked* and then *security warning". I rebooted again and the phone is in working condition as of now but when I enter the bootloader menu first it says this is build verison for htc only blah blah and then there is security warning in bootloader menu.
I now just want to get my phone in the stock condition and then update it to RUU 2.20 . Can anyone help me with it?
Sorry for such a long and boring post but I tried to make my point clear.
I have attached the pics of my software info incase they may help.
Plus this is the info I get in bootloader menu:
Evita PVT SHIP S-ON RL
HBOOT-1.09.0000
RADIO-0.17.32.09.12
OPENDSP-v28.1.0.32.0504
eMMC-boot
Apr 2 2012,21:08:24

Ok so the tampered flag is due to you rooting your phone. It will go away if you RUU back to stock. The relocked flag will not go away even if you go back to stock. The security warning when it loads up the kernel (that red text that says "This build if for development purposes only yada yada yada") is nothing, don't even worry about it, we all have it once we start messing with our phones.
Anyway...Did you install HTC Sync on your PC? That installs all the necessary drivers to make sure your phone is recognized. I don't really know how Windows 8 behaves with our phone but if you have HTC Sync and the drivers installed and it still doesn't work then I would try borrowing a friend's Win7 computer and trying it there.
When you're in the bootloader and go to the fastboot menu does it say FASTBOOT USB at the top when you have it plugged in?

stnguyen09 said:
Ok so the tampered flag is due to you rooting your phone. It will go away if you RUU back to stock. The relocked flag will not go away even if you go back to stock. The security warning when it loads up the kernel (that red text that says "This build if for development purposes only yada yada yada") is nothing, don't even worry about it, we all have it once we start messing with our phones.
Anyway...Did you install HTC Sync on your PC? That installs all the necessary drivers to make sure your phone is recognized. I don't really know how Windows 8 behaves with our phone but if you have HTC Sync and the drivers installed and it still doesn't work then I would try borrowing a friend's Win7 computer and trying it there.
When you're in the bootloader and go to the fastboot menu does it say FASTBOOT USB at the top when you have it plugged in?
Click to expand...
Click to collapse
Thanks for replying. Yes it does says FASTBOOT USB highlighted in red. And yes I have installed HTC Sync which apparantely didn't install the required drivers and I had to install them manually from device manager but they are properly installed now as there is yellow triangle in device manager and it recognizes my phone as "android adb interface" when the phone is in bootloader menu and "android composite ABD interface " when the phone is on.

UsmanImtiaz said:
Thanks for replying. Yes it does says FASTBOOT USB highlighted in red. And yes I have installed HTC Sync which apparantely didn't install the required drivers and I had to install them manually from device manager but they are properly installed now as there is yellow triangle in device manager and it recognizes my phone as "android adb interface" when the phone is in bootloader menu and "android composite ABD interface " when the phone is on.
Click to expand...
Click to collapse
Hmmm... I'm not sure anymore. Did you try using another usb port? It sounds stupid but I've had more than one instance of certain usb ports not doing what they should because of drivers only being installed/recognizing certain ports.
Which RUU did you try running? The 2.20 or the 1.85?
Sent from my One X using xda premium

stnguyen09 said:
Hmmm... I'm not sure anymore. Did you try using another usb port? It sounds stupid but I've had more than one instance of certain usb ports not doing what they should because of drivers only being installed/recognizing certain ports.
Which RUU did you try running? The 2.20 or the 1.85?
Sent from my One X using xda premium
Click to expand...
Click to collapse
Ok I will try changing the ports. I am trying to run 2.20 RUU

Can never understand why people who are rooted and bootloader unlocked want to install 2.20 OTA or RUU. You will lose ability to flash kernels using recovery.
Consider it a blessing that the RUU did not install. There is no benefit to installing the 2.20 RUU. just flash the pre-rooted stock 2.20 in the Development forum. Better yet, rooted stock 2.23, which is newer, or custom ROMs based on 2.23 or 2.29.
Sent from my HTC One XL using xda app-developers app

redpoint73 said:
Can never understand why people who are rooted and bootloader unlocked want to install 2.20 OTA or RUU. You will lose ability to flash kernels using recovery.
Consider it a blessing that the RUU did not install. There is no benefit to installing the 2.20 RUU. just flash the pre-rooted stock 2.20 in the Development forum. Better yet, rooted stock 2.23, which is newer, or custom ROMs based on 2.23 or 2.29.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Wait, we lost kernel flashing with 2.20?

stnguyen09 said:
Wait, we lost kernel flashing with 2.20?
Click to expand...
Click to collapse
yep. new Hboot locks down the boot partition. This is a good thing IMHO less bricks due to flashing ROMS meant for the Tegra 3 HOX.
fastboot still works for boot.img.

More importantly it WP's hboot. Good for some users (such as OP), bad for others.

Bootloader Malfunction

I'm trying to get to S-OFF using Facepalm S-OFF, however when I connect my One X in bootloader to my PC (I have 2 laptops & 1 desktop) it pops up that the USB device that you connected has malfunctioned and windows does not recognize it it does the same thing on all 3 PC's.I originally posted in the Facepalm thread and am now posting here as per thedailyl3af recomendation that I post here since he could not help me. When I connect my One X to the PC the phone is recognized by both the PC & HTC Sync manager (yes I shut down the Sync manager) but soon as I go to bootloader the PC no longer recognizes it. The main reason I want S-OFF is so that I can flash different kerrnals and radio's to try and clear up the One X clearity problem, when I am talking to people most of the I am saying "what" or "could you repeat that". My One X is unlocked and I do have SuperCID. Please Help! Thank you in advance

Install HTC drivers and uninstall HTC sync
Sent from my One X using xda app-developers app

That is weird. Did you try different USB ports or a different cable? That normally helps. Try to wait 10 mins as well
Sent from my Carbon-ize Evita using xda-developers app

Why not just connect your phone normally to the computer, stop HTC sync and use adb commands to put your phone into bootloader?
Sent from my HTC One X using xda premium

Venomtester said:
Why not just connect your phone normally to the computer, stop HTC sync and use adb commands to put your phone into bootloader?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I have done that, When I connect my One X to my computer, HTC Sync starts, I shut it down. I open command pompt. Then I use adb commands to open bootloader and soon as it goes into bootloader the PC stops recognizing it and says the USB device has malfunctioned. I am unlocked, have SuperCID, Have Super user and am able to use it. I am running ViperXL rom. I have uninstalled drivers on my PC and re-downloaded them and re-installed them many times, so I know it is not drivers on my PC.
Something had to go wrong when I flashed TWRP v2.4.1.0. My problem is everything that evryone is telling me to do goes through bootloader, well if my PC does not recognize my phone while in bootloader how am I going to get past that point. I even tried to flash to TWRP v2.3.1.0, through TWRP recovery, both as a seprate zip file and by starting to reinstall ViperXL (Aroma) installer and I can't even back to TWRP 2.3.1.0 which I know is not as buggy as v2.4.1.0. When I go through the Aroma installer it says that it installed it, but when I go back to TWRP it still says v2.4.1.0.
Was on Facepalm S-OFF Thread and they recomended that I try this forum since evrything they had me try did not work. I am stuck and I just want some straight to the point advice on how to get past this issue. Don't know if this will help but when I am in bootloader this what the bootloader image says, I'm only putting the first part down as you guys know what the rest says.
*** TAMPERED ***
*** UNLOCKED ***
EVITA PUT SHP S-ON RL
HBOOT-1.14.0002
RADIO-0.19as.32.09.11.2
OpenDSPv29.1.0.45.0622
eMMC-boot
Jun 11 2012, 14:36:28

You have hboot 1.14. Aroma installer fails to flash images you may have to flash twrp manually. Also there was a bug in on of the versions of viperxl that would not mount. What version of viper are you running?
Sent from my HTC One X using xda premium

scrappy1959 said:
I have done that, When I connect my One X to my computer, HTC Sync starts, I shut it down. I open command pompt. Then I use adb commands to open bootloader and soon as it goes into bootloader the PC stops recognizing it and says the USB device has malfunctioned. I am unlocked, have SuperCID, Have Super user and am able to use it. I am running ViperXL rom. I have uninstalled drivers on my PC and re-downloaded them and re-installed them many times, so I know it is not drivers on my PC.
Something had to go wrong when I flashed TWRP v2.4.1.0. My problem is everything that evryone is telling me to do goes through bootloader, well if my PC does not recognize my phone while in bootloader how am I going to get past that point. I even tried to flash to TWRP v2.3.1.0, through TWRP recovery, both as a seprate zip file and by starting to reinstall ViperXL (Aroma) installer and I can't even back to TWRP 2.3.1.0 which I know is not as buggy as v2.4.1.0. When I go through the Aroma installer it says that it installed it, but when I go back to TWRP it still says v2.4.1.0.
Was on Facepalm S-OFF Thread and they recomended that I try this forum since evrything they had me try did not work. I am stuck and I just want some straight to the point advice on how to get past this issue. Don't know if this will help but when I am in bootloader this what the bootloader image says, I'm only putting the first part down as you guys know what the rest says.
*** TAMPERED ***
*** UNLOCKED ***
EVITA PUT SHP S-ON RL
HBOOT-1.14.0002
RADIO-0.19as.32.09.11.2
OpenDSPv29.1.0.45.0622
eMMC-boot
Jun 11 2012, 14:36:28
Click to expand...
Click to collapse
I already told you to uninstall HTC sync.
Sent from my One X using xda app-developers app

There is one more thing that could cause you problems and that is that your cable is bad. If you have another one that will fit your phone laying around you might want to try swapping out.
Sent from my HTC One X using xda premium
---------- Post added at 09:52 PM ---------- Previous post was at 09:49 PM ----------
Sorry herc didn't see you posted that already.
Sent from my HTC One X using xda premium

Venomtester said:
There is one more thing that could cause you problems and that is that your cable is bad. If you have another one that will fit your phone laying around you might want to try swapping out.
Sent from my HTC One X using xda premium
---------- Post added at 09:52 PM ---------- Previous post was at 09:49 PM ----------
Sorry herc didn't see you posted that already.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I just went through all of this. Been having this problem for the past few days. I tried different cable, differenent port, installing/unistalling htc sync, install htc driver/uninstall htc drivers, install android sdk/unistall android sdk, installing pdanet drivers, stopping htc sync, manually uninstalling all android related drivers and reinstalling them. In the end after 4 days of long hours of trial and error I gave up. EVERY solution on the internet fail. Every one of them. Came to the conclusion that something else besides android related drivers is interfereing with fastboot. So the only solution I found was to download virtual box and install a copy of windows in it. Install htc sync on the virtual machine and dont uninstall it. Then plug in your phone while in bootloader connect to the virtual machine and let it install the rest of the drivers. Then fastboot WILL work.
Im not saying don't try all of what everyone is telling you first. What Im saying is that if nothing else works although it may be a bit complicated I can almost guarantee it will work because everything is fresh and there should be no conflicts.

ImagioX1 said:
I just went through all of this. Been having this problem for the past few days. I tried different cable, differenent port, installing/unistalling htc sync, install htc driver/uninstall htc drivers, install android sdk/unistall android sdk, installing pdanet drivers, stopping htc sync, manually uninstalling all android related drivers and reinstalling them. In the end after 4 days of long hours of trial and error I gave up. EVERY solution on the internet fail. Every one of them. Came to the conclusion that something else besides android related drivers is interfereing with fastboot. So the only solution I found was to download virtual box and install a copy of windows in it. Install htc sync on the virtual machine and dont uninstall it. Then plug in your phone while in bootloader connect to the virtual machine and let it install the rest of the drivers. Then fastboot WILL work.
Im not saying don't try all of what everyone is telling you first. What Im saying is that if nothing else works although it may be a bit complicated I can almost guarantee it will work because everything is fresh and there should be no conflicts.
Click to expand...
Click to collapse
While I agree with you, there are steps you take with troubleshooting to narrow down the cause this way if you don't HAVE to do a fresh install of Windows on a virtual machine, you don't.

exad said:
While I agree with you, there are steps you take with troubleshooting to narrow down the cause this way if you don't HAVE to do a fresh install of Windows on a virtual machine, you don't.
Click to expand...
Click to collapse
Exactly. That was what I was trying to say in the last line of my post.

I had the same problem and tried all of these solutions. Now I tried virtualbox with XP and still no luck. What seems to be happening is that Windows 8.1 cannot even hand off my phone to the virtualbox USB controller because I am getting that error that the device malfunctioned. I've also put a filter to catch all USB devices and enabled/disabled USB 2.0 controller. Any suggestions?

[Q] Help, may have bricked

A little foreshadow. I attempted to install the jellybean update on a rooted ATT phone. I ended up getting sent to the TWRT (?) screen on the install. I was silly and decided to clear the system... Which erased my OS completely.
For a while I was able to get to the TWRT(?) screen where I could mount my sd card, etc. While researching the problem I came across this:
a solution of fastbooting a recovery.img
I ran the fastboot recovery.img. The only problem is the only screen I can now access is the bootloader. I have bootloader 1.14.0002 loaded onto my phone if that helps.
Is there anyway to try to get a operating system or flash a rom onto this phone still or is it bricked for good? Also if I was able to put a rom onto it, what do you sugggest?
When I try to go to Recovery or Factory Reset, I get the HTC screen with the red text underneath it and it never goes any further.
Evita PVT Ship S-ON RL
HBOOT-1.14.0002
Radio-0.19as 32.09.11_2
OpenDSP-V29.1.0.45.0622
eMMC-boot
Jun 11 2012, 14:36:28
That is the information listed in my bootloader as of now. I am not showing it listed as a drive in my computer when connected to USB. Also when I 'power off' I am in a reset cycle that doesn't stop.
I really appreciate any help in advance. This was a big wake up call to myself about how I should be a lot more careful when messing with these things.
Thank you to everyone that answers!

http://forum.xda-developers.com/showthread.php?p=38909732
[Public Service Announcement] Read before installing the AT&T Jellybean OTA or RUU
You might be hosed. Can you get into bootloader?
Sent from my One X using xda premium

Read before doing anything. Such a simple task. It's easy to read, it's hard to come back from a brick.
Sent from my One XL using XDA Premium

You are not bricked, you are not even close to bricked... If you are already rooted, get the official jellybean update of your head. Clear your thoughts and lock it away. There are tons of custom jellybean ROMs available, a couple based on atts JB update... Flash one of those. If you can get to bootloader you're fine. If you can still access twrp, even better... Which version of twrp do you have IF you can still access? We'll start with that. If not You'll have to fastboot a recovery. 2.3.3.0 is your safest bet, I think the community will agree this is one of the most stable versions for our device.. Just in case you have to push it, download from here onto your computer. http://goo.im/devs/OpenRecovery/evita/openrecovery-twrp-2.3.3.0-evita.img
Now drop that image file into your adb/fastboot folder. Right click your adb/fastboot folder and open a command prompt from there. Shoot this command.
Fastboot flash recovery openrecovery-twrp-2.3.3.0-evita.img
Now from bootloader choose to boot into recovery. Awwww yea now we on to something!
Now you can download the rom of choice onto your computer. Since you opted for official JB, take a look at Scotts CleanRom. It uses ATT firmware as base :thumbup: once downloaded, double click the zip file (rom) it'll show contents, and youll see a boot.img. simply drop the boot.img into your fastboot/adb folder.
Now on your phone. Choose "mount" in recovery. Make sure it mounts and shows files on your computer. From here drag the entire rom zip (cleanrom) onto your SD card. Now "unmount" hell yea we getting close. I can feel it!
Back out and choose "install" find cleanrom.zip, and swipe to flash. F*ckin rite, this is what android is all about.
Once its completed, DO NOT REBOOT SYSTEM. Since your s-on and have 1.14 hboot, you'll have to fastboot the boot.img you put in your adb folder. Choose to boot into bootloader! Make sure once again it says fastboot usb
Fire up command prompt inside that folder.
Shoot the command ---> fastboot flash boot boot.img
Sending.......
Okay....
Finished.....
OMG success!!! Some people will say to ---> fastboot erase cache
I don't necessarily do this, but it definitely won't hurt. Now reboot system and enjoy Scotts hard work. They don't calls his ROMs the most stable ROMs on the planet for nothing
Sent from my One X using Tapatalk 2

Not only does fastboot erase cache not take long it avoids many stupid little issues. I would say it's a must when flashing a new recovery.
Sent from my One X using xda app-developers app

sinkthehalffoot said:
I attempted to install the jellybean update on a rooted ATT phone. I ended up getting sent to the TWRT (?) screen on the install.
Click to expand...
Click to collapse
The reason it went to recovery is very simple. The OTA needs to have stock recovery in order to install. You don't have stock recovery on your phone anymore, you have custom recovery (TWRP). So the OTA stalled there, when it didn't find stock recovery.
sinkthehalffoot said:
I was silly and decided to clear the system... Which erased my OS completely.
Click to expand...
Click to collapse
Of course it did, what were you expecting to happen? Wiping the OS is the very definition of what happens when you wipe system. If you didn't know what wiping system would do, you shouldn't have done it. For that matter, you shouldn't be doing anything on your phone if you don't know what its for.
A lot of this points to a fundamental lack of reading and understanding:
- Don't know the name of the custom recovery installed on the system
- Wiping things without knowing what they are
- Basic rule (that many folks here seem to ignore, for reasons unknown): Don't install any OTA on a rooted device without first researching what will happen
Lack of basic understanding which spells almost certain doom when modding smartphones. I would highly suggest a few solid hours of research before messing with your phone anymore. I'm not saying this to be a jerk. I'm saying it so you don't brick your phone.
You aren't bricked. With very few exceptions (and this isn't one of those) if the screen turns on, and you can get into hboot, the phone is recoverable. And probably fairly easily so, with the right steps. But you need to do some homework before proceeding.

redpoint73 said:
Lack of basic understanding which spells almost certain doom when modding smartphones. I would highly suggest a few solid hours of research before messing with your phone anymore. I'm not saying this to be a jerk. I'm saying it so you don't brick your phone.
Click to expand...
Click to collapse
+1000
This is exactly the kind of situation that occurs when people get in over their heads and start blundering around.
http://forum.xda-developers.com/showthread.php?t=2232141

InflatedTitan said:
You are not bricked, you are not even close to bricked... If you are already rooted, get the official jellybean update of your head. Clear your thoughts and lock it away. There are tons of custom jellybean ROMs available, a couple based on atts JB update... Flash one of those. If you can get to bootloader you're fine. If you can still access twrp, even better... Which version of twrp do you have IF you can still access? We'll start with that. If not You'll have to fastboot a recovery. 2.3.3.0 is your safest bet, I think the community will agree this is one of the most stable versions for our device.. Just in case you have to push it, download from here onto your computer.
Now drop that image file into your adb/fastboot folder. Right click your adb/fastboot folder and open a command prompt from there. Shoot this command.
Fastboot flash recovery openrecovery-twrp-2.3.3.0-evita.img
Now from bootloader choose to boot into recovery. Awwww yea now we on to something!
Now you can download the rom of choice onto your computer. Since you opted for official JB, take a look at Scotts CleanRom. It uses ATT firmware as base :thumbup: once downloaded, double click the zip file (rom) it'll show contents, and youll see a boot.img. simply drop the boot.img into your fastboot/adb folder.
Now on your phone. Choose "mount" in recovery. Make sure it mounts and shows files on your computer. From here drag the entire rom zip (cleanrom) onto your SD card. Now "unmount" hell yea we getting close. I can feel it!
Back out and choose "install" find cleanrom.zip, and swipe to flash. F*ckin rite, this is what android is all about.
Once its completed, DO NOT REBOOT SYSTEM. Since your s-on and have 1.14 hboot, you'll have to fastboot the boot.img you put in your adb folder. Choose to boot into bootloader! Make sure once again it says fastboot usb
Fire up command prompt inside that folder.
Shoot the command ---> fastboot flash boot boot.img
Sending.......
Okay....
Finished.....
OMG success!!! Some people will say to ---> fastboot erase cache
I don't necessarily do this, but it definitely won't hurt. Now reboot system and enjoy Scotts hard work. They don't calls his ROMs the most stable ROMs on the planet for nothing
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
In case anyone ends up stumbling here with a similar issue, this solution worked to a 'T'. Thank you again InflatedTitan.
To everyone else, yes I know, I should of read more than I had. I saw the jellybean update and have been wanting it for a while and acted with haste. I learned a valuable lesson from it all.

Lol this "solution" was around before you posted. You just didn't read or search enough.
Sent from my One X using xda app-developers app

F**kin right! That's what android is all about. Hahaha!
Sent from my HTC One X using xda premium

Venomtester said:
F**kin right! That's what android is all about. Hahaha!
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Lol :beer:
Sent from my HTC One X using xda app-developers app

Venomtester said:
F**kin right! That's what android is all about. Hahaha!
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Its almost like a high every time I slide to flash lol
Sent from my HTC One XL using Tapatalk 2

InflatedTitan said:
Its almost like a high every time I slide to flash lol
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
I thought I was the only one. In fact I just rooted a nook tablet and installed twrp. Slides to flash... And I could swear I was on cloud 9.
But bravo on the explanation sir. Love a good write up. Even though i already know it, feels good to read it.
Sent from my Carbon-ize Evita using xda-developers app

[HELP] Not sure if bricked or hardware issue?
I know this is my first post, but I really need the help.
(Also, I'm sorry if this is a bit long)
I've have searched the HOX Evita and Android Q&A forums countless time in the past 3 days trying to figure this out. This thread and this one: "http://forum.xda-developers.com/showthread.php?t=2156665&highlight=fastboot+usb+hangs", are the most similar to what I think is happening to my phone.
Just a little background:
- Bought a used HTC One X, but has a cracked digitizer which I'll be replacing this weekend. (Not sure if this is causing the problems, could it?)
- I was told that the OS was still stock, but I know that's not true now.
- During the first 12 hours I used it, I had no problems.
- Then while I was playing music it rebooted and went to the HTC boot up screen with the red text. Stopped then rebooted again to the normal HTC boot up screen but just hanged there and vibrated nonstop.
- I then used the power button to force a shut down and haven't been able to use it since then.
Here's where I'm at now:
- I'm able to get to the bootloader screen sometimes with the VOL DOWN+PWR method, but most of the time it goes to the QHSUSB mode.
- When I can get to the bootloader, I try to get to Fastboot or Recovery mode but once I press the power button it just stops and does nothing.
- The few times I have gotten into fastboot, and plug in an USB cable, it hangs.
- So far I have NOT gotten it to show "FASTBOOT USB" therefore I haven't been able to use a RUU or flash a boot.img.
- I have reinstalled the drivers almost 5 times now, and tried with different sources from here and HTC Sync. And also tried with 3 different cables and USB ports on my laptop. But still no signs of a connection with my laptop.
- And at one time I (before I knew I shouldn't have) I did try to Factory Reset from the bootloader, but nothing happened. I hope that won't become my downfall.
But yeah, sorry again for the long post, just trying to be thorough. If anyone has an idea of what I can do, please I need your help. It really doesn't matter to me whether my HOX goes back to stock, or use a ROM like CleanROM 6, as long as I can use it again.
Also here's the info at the bootloader screen.
***TAMPERED***
***LOCKED***
Evita PVT Ship S-ON RL
HBOOT-1.14.0002
Radio-0.19as 32.09.11_2
OpenDSP-V29.1.0.45.0622
eMMC-boot
Jun 11 2012, 14:36:28

pharrjw said:
I know this is my first post, but I really need the help.
(Also, I'm sorry if this is a bit long)
I've have searched the HOX Evita and Android Q&A forums countless time in the past 3 days trying to figure this out. This thread and this one: "http://forum.xda-developers.com/showthread.php?t=2156665&highlight=fastboot+usb+hangs", are the most similar to what I think is happening to my phone.
Just a little background:
- Bought a used HTC One X, but has a cracked digitizer which I'll be replacing this weekend. (Not sure if this is causing the problems, could it?)
- I was told that the OS was still stock, but I know that's not true now.
- During the first 12 hours I used it, I had no problems.
- Then while I was playing music it rebooted and went to the HTC boot up screen with the red text. Stopped then rebooted again to the normal HTC boot up screen but just hanged there and vibrated nonstop.
- I then used the power button to force a shut down and haven't been able to use it since then.
Here's where I'm at now:
- I'm able to get to the bootloader screen sometimes with the VOL DOWN+PWR method, but most of the time it goes to the QHSUSB mode.
- When I can get to the bootloader, I try to get to Fastboot or Recovery mode but once I press the power button it just stops and does nothing.
- The few times I have gotten into fastboot, and plug in an USB cable, it hangs.
- So far I have NOT gotten it to show "FASTBOOT USB" therefore I haven't been able to use a RUU or flash a boot.img.
- I have reinstalled the drivers almost 5 times now, and tried with different sources from here and HTC Sync. And also tried with 3 different cables and USB ports on my laptop. But still no signs of a connection with my laptop.
- And at one time I (before I knew I shouldn't have) I did try to Factory Reset from the bootloader, but nothing happened. I hope that won't become my downfall.
But yeah, sorry again for the long post, just trying to be thorough. If anyone has an idea of what I can do, please I need your help. It really doesn't matter to me whether my HOX goes back to stock, or use a ROM like CleanROM 6, as long as I can use it again.
Also here's the info at the bootloader screen.
***TAMPERED***
***LOCKED***
Evita PVT Ship S-ON RL
HBOOT-1.14.0002
Radio-0.19as 32.09.11_2
OpenDSP-V29.1.0.45.0622
eMMC-boot
Jun 11 2012, 14:36:28
Click to expand...
Click to collapse
You will have to get a proper fastboot connection before you can do anything. Then unlock the bootloader then you can flash a recovery on there. Is this an AT&T phone?

exad said:
You will have to get a proper fastboot connection before you can do anything. Then unlock the bootloader then you can flash a recovery on there. Is this an AT&T phone?
Click to expand...
Click to collapse
Thanks for the reply. Yes, it is an AT&T phone. I understand that I need a fastboot connection, I'm just having difficulties timing it. Is it normally this difficult to get a FASTBOOT USB connection? Or is there something else that I could be missing, or any other method?
I have thought about booting Windows XP on my laptop from a flash drive then trying to connect from that. Does XP have a better record when it comes to unlocking and flashing with android?

If you did a factory reset from bootloader your sd is corrupted. When you can get into the bootloader what does it do if you click on recovery?
Sent from my HTC One X using xda app-developers app

pharrjw said:
Thanks for the reply. Yes, it is an AT&T phone. I understand that I need a fastboot connection, I'm just having difficulties timing it. Is it normally this difficult to get a FASTBOOT USB connection? Or is there something else that I could be missing, or any other method?
I have thought about booting Windows XP on my laptop from a flash drive then trying to connect from that. Does XP have a better record when it comes to unlocking and flashing with android?
Click to expand...
Click to collapse
There's nothing to time. Drivers and fastboot/adb are all you need. HTC Sync can get in the way so kill or uninstall it if it's running. When you boot to Bootloader, select fastboot, plug in the phone, if you have the the drivers it should go into fastboot USB. I have seen people having issues before due to something interfering with the HTC drivers but it's not common. You can try creating a VM for a clean environment with less chance of anything interfering.

Thanks again for the replies guys.
31ken31 said:
If you did a factory reset from bootloader your sd is corrupted. When you can get into the bootloader what does it do if you click on recovery?
Click to expand...
Click to collapse
I was just able to get back into Bootloader, and tried to go into recovery, but with no luck. It just hangs at the bootloader screen. :
EDIT: Not sure if relevant, but after that it eventually shut down, and when I checked it in the Device Manager it appeared again as QHSUSB-DLOAD.
exad said:
There's nothing to time. Drivers and fastboot/adb are all you need. HTC Sync can get in the way so kill or uninstall it if it's running. When you boot to Bootloader, select fastboot, plug in the phone, if you have the the drivers it should go into fastboot USB. I have seen people having issues before due to something interfering with the HTC drivers but it's not common. You can try creating a VM for a clean environment with less chance of anything interfering.
Click to expand...
Click to collapse
I'm gonna try it again with HTC Sync uninstalled. But if I get the same results I'll probably will endup creating a VM, and hopefully get better results.
I would also like to add that when I do try to get to the bootloader I get various results. Sometimes it goes into QHSUSB like I said in my first post. Then sometimes just nothing but a blank screen and the LED light blinking like the battery is low, or it's solid as if it is charging even though my HOX isn't plugged in to anything. That's what I was referring to when I said I was having difficulties timing it.

pharrjw said:
Thanks again for the replies guys.
I was just able to get back into Bootloader, and tried to go into recovery, but with no luck. It just hangs at the bootloader screen. :
EDIT: Not sure if relevant, but after that it eventually shut down, and when I checked it in the Device Manager it appeared again as QHSUSB-DLOAD.
I'm gonna try it again with HTC Sync uninstalled. But if I get the same results I'll probably will endup creating a VM, and hopefully get better results.
I would also like to add that when I do try to get to the bootloader I get various results. Sometimes it goes into QHSUSB like I said in my first post. Then sometimes just nothing but a blank screen and the LED light blinking like the battery is low, or it's solid as if it is charging even though my HOX isn't plugged in to anything. That's what I was referring to when I said I was having difficulties timing it.
Click to expand...
Click to collapse
factory reset in bootloader corrupts the SD card. We wont worry about that just yet as there's nothing we can do about it until we can get recovery on there.
You're going to have to be very careful because it sounds like your EMMC partitions might have some issues. if you can get it to bootlaoder KEEP IT AT THAT SCREEN. don't power it off or anything, leave it there. Because one wrong move could be a perma brick. If we can get a rom on there to S-OFF with, we can RUU to restore your emmc partitions.

[Q] S-off attempts timing out in bootloader

Hi all,
I am attempting to S-off the wife's ATT HTC One X, so that I can install a Kit Kat Rom in it. Her phone is unlocked and running CM10.2, but she's S-on.
I've tried several toolkits, but they get stuck and time out waiting for the device once it reboots into the bootloader. In debugging mode, adb devices identified the phone just fine, but the computer (running Windows 8.1) says doesn't recognize the phone when in bootloader. I've got Koush's Universal ADB driver installed, installed HTC Sync for the drivers, then uninstalled the program. The drivers are still there when I navigate to them.
If this isn't the appropriate forum, then I apologize.
Many thanks in advance!

What method are you trying to use?
Sent from my HTC One X using xda premium

magnetboard said:
What method are you trying to use?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Rumrunner is one. It reboots into bootloader post the warnings then runs its 120 seconds and times out waiting for the device.

Ah, windows 8 and newer have problems with fastboot. That's why. Do you have access to a computer with windows 7 or lower?
Sent from my HTC One X using xda premium

magnetboard said:
Ah, windows 8 and newer have problems with fastboot. That's why. Do you have access to a computer with windows 7 or lower?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I can put an old HD back in with W7. I take it there is no workaround with 8.1?

Windows 8 is fine with fastboot but 8.1 is where the problems begin. No workaround yet. What see the bootloader details though? Depending on your current setup you might not even need s-off yet. S-off isn't required to flash the ROMs, but it's required to update your firmware (via an RUU). If your firmware is up to date you can just flash.
Sent from my Evita

timmaaa said:
Windows 8 is fine with fastboot but 8.1 is where the problems begin. No workaround yet. What see the bootloader details though? Depending on your current setup you might not even need s-off yet. S-off isn't required to flash the ROMs, but it's required to update your firmware (via an RUU). If your firmware is up to date you can just flash.
Sent from my Evita
Click to expand...
Click to collapse
What all do you need to know? She has her phone with her today.
She has 2.18. I don't know other details off the top of my head and walking her through to boot to bootloader would be an utter disaster, lol.
The reason for trying to get S-off was that both the KitKat versions of CM and PA stated that S-off was required.
Thanks for your help.

If your cousin can't get to the bootloader by herself, then she has absolutely no business having a modified phone. Handing a modified device to someone who has no idea about what they're doing is a bad idea. The device has root privileges, access to areas that see not normally accessible. This means it's easy top screw up the device if you don't know what you're doing. Also, if something goes wrong she's not gonna know what to do, will probably panic and screw it up even more. Return it to stock.
Sent from my Evita

timmaaa said:
If your cousin can't get to the bootloader by herself, then she has absolutely no business having a modified phone. Handing a modified device to someone who has no idea about what they're doing is a bad idea. The device has root privileges, access to areas that see not normally accessible. This means it's easy top screw up the device if you don't know what you're doing. Also, if something goes wrong she's not gonna know what to do, will probably panic and screw it up even more. Return it to stock.
Sent from my Evita
Click to expand...
Click to collapse
Appreciate the concern. This is my wife's phone, and she's handled CM10.2 just fine for the last 6 months. She's informed enough to not do something stupid, but let's me handle rooting and flashing.