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

unrooted, s-on, Desire S stuck on hboot/fastboot

Hello.
I could really do with some help, please.
I have a HTC Desire S, completely stock standard, un-rooted, s-on etc etc, and it i stuck on the hboot/fastboot.
First off it became unresponsive, so pulled the battery and tried restarting it. It bootlooped a few times, so decided to use volume down/power buttons and tried fastboot then recovery. I can't remember what it did in those options as it was a few days ago now and I've been trying to find a solution since.
Anyway, I eventually did a factory reset from hboot and that seemed to do the trick for about an hour after which it crashed and entered the state it's in now.
The only thing it'll do is boot into fastboot. It doesn't matter what option I choose, it shows the android on a skateboard and returns to fastboot. The only thing it'll do is power down.
The phone is un-rooted, s-on.
The only details I have are on the fastboot screen which says
*** LOCKED ***
SAGA PUT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-BOOT
Oh and if I plug in into my Mac, it says "Fastboot USB" & "hboot USB plug" but not seen on by the Mac.
Help. Please.
I've bricked it, haven't I?

Unlock the bootloader through htcdev, flash a custom recovery, flash a ROM (see sticky guide for more details). Or Run a RUU , use windows
Sent from my HTC Desire XS using xda app-developers app

razi914 said:
Unlock the bootloader through htcdev, flash a custom recovery, flash a ROM (see sticky guide for more details). Or Run a RUU , use windows
Sent from my HTC Desire XS using xda app-developers app
Click to expand...
Click to collapse
htcdev wont work because adb is not working, and he'll keep getting "fail to verify signature" error. or the screen will stuck on "Waiting device"
I'm having the exact same problem, and I'm trying to fix it since yesterday...

Have you tried running an ruu?
“We are all in the gutter, but some of us are looking at the stars.”
― Oscar Wilde

I've tried plugging it into a windows machine with the same results - nothing.
I'm at work at the moment so don't have time to read the sticky mentioned (I will do later this evening), but I've run adb (on mac and windows) and it doesn't find a device.
I cannot 'get onto' the device, via USB or sd card, to do anything with it. I would've tried running RUU's and whatever but all the guides need the phone to be seen by a computer or run something from an sd card.
I've even tried swearing at it while gesticulating angrily..
I'm hoping you guys are going to tell me it's not an ineffectual doorstop just yet, but I fear it may be so.

biloz_nexus said:
htcdev wont work because adb is not working, and he'll keep getting "fail to verify signature" error. or the screen will stuck on "Waiting device"
I'm having the exact same problem, and I'm trying to fix it since yesterday...
Click to expand...
Click to collapse
no, no need for adb ,, only fastboot ,
u should install the drivers on windows , then type in adb/fastboot cmd 'fastboot devices' (ur phone should be in fastboot mode) unlock the bootloader (baby easy) please read this guide [Guide] How to root, install EXT4 recovery and custom ROM on HBOOT 2.00.0002 not so hard, OR run a ruu through fastboot
edit: use windows 7 , it will automatically install the drivers

I shall have go at that tonight and let you report back.
Thank you.
Sent from my GT-I9305 using xda app-developers app

sim-o said:
I shall have go at that tonight and let you report back.
Thank you.
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
What windows os are you using
“We are all in the gutter, but some of us are looking at the stars.”
― Oscar Wilde

jugg1es said:
What windows os are you using
“We are all in the gutter, but some of us are looking at the stars.”
― Oscar Wilde
Click to expand...
Click to collapse
err, either Vista or 7. The wifes laptop is 7, but she'll probably be busy with something important like facebook, and the other win machine I think is Vista.
or 7.
maybe...
If I've gotta download drivers, I've gotta download drivers.

sim-o said:
err, either Vista or 7. The wifes laptop is 7, but she'll probably be busy with something important like facebook, and the other win machine I think is Vista.
or 7.
maybe...
If I've gotta download drivers, I've gotta download drivers.
Click to expand...
Click to collapse
Only asked because win8 has issues installing the driver's
“We are all in the gutter, but some of us are looking at the stars.”
― Oscar Wilde

If you pulled the battery and that's when the problems started, you might have bricked the emmc. In that case you do NOT want to unlock.
Verify that your emmc is OK first before unlocking through htcdev!

Ah, I think I read some mention that in another thread I read.
So, first check the emmc is ok then follow the guide mentioned above if it's ok.
Sent from my GT-I9305 using xda app-developers app

Can't find out how to check if emmc is fried or not.
Can't get PC to see phone.
Can't even get chuffing drivers installed on the chuffing PC:
"HTC Sync - InstallShield Wizard
The installation of HTC Driver Installer 4.0.1.001 appears to have failed"
grrrr
Thanks for you're suggestions, gentlemen. but I think I'm just gonna take a sledge hammer to the phone and the pc.

try another computer?

razi914 said:
try another computer?
Click to expand...
Click to collapse
I will, just not tonight. It's been a bad week for me and dodgy tech. I'll try again tomorrow or Sunday.

For the record, I've tried another computer and HTC Driver Installer 4.01.001 failed again.
This is ridiculous.
Unless someone has a link to the drivers form somewhere other HTC, which I doubt, I'll be back, but I could be sometime.

Try a computer running win 7 , dont download any drivers, make sure internet connection is okay on pc, just connect ur phone in fastboot mode with PC, it will automattically download drivers,, also install htc-sync
Sent from my HTC Desire XS using xda app-developers app

[Q] Getting Error 170 while trying to RUU to 3.18...what am I doing wrong?

As the title says: I'm trying to install the 3.18 RUU for my AT&T HTC One X. I'm currently on an old build of CM10.1 (beautifully maintained by H8rift) and was wanting to try the latest build he posted with the 3.4 Kernel. I am S-Off and Unlocked. I searched the forum (internal search seems to be broken at the moment) and all I keep seeing is mostly go to fastboot THEN run the RUU. Well I'm in fastboot (enabled the menu from within CM...less I just misunderstood that completely). Fastboot shows "Fastboot USB" but the RUU still gives Error 170. What did I do wrong?
Running this on a Windows 8 x64 system, installed HTC Sync Manager (still didn't help). I updated the Android SDK Tools to the latest version. My CID is all 1's (as per the S-Off directions). I'm at a loss here hehe.
Ooh I have TWRP 2.4.1.0. And yes I barely post, just always looking, reading, etc.

Is the USB port you're using 2.0 or 3.0? If it's 3.0 (it should have the USB icon and a little ss) try switching to 2.0. Also, try running RUU while not in fastboot.

RollTribe said:
Is the USB port you're using 2.0 or 3.0? If it's 3.0 (it should have the USB icon and a little ss) try switching to 2.0. Also, try running RUU while not in fastboot.
Click to expand...
Click to collapse
Yup running it on my USB 2.0 ports. Tried my case ports and the motherboard ones, same thing. Also just tried it with the phone booted. No dice. Even using the HTC USB Cable (not like there should be a difference but hey, just in case). Maybe I should threaten the phone...with a hammer. (Nah I'm not that mean).

Turbo Mach 5 said:
Yup running it on my USB 2.0 ports. Tried my case ports and the motherboard ones, same thing. Also just tried it with the phone booted. No dice. Even using the HTC USB Cable (not like there should be a difference but hey, just in case). Maybe I should threaten the phone...with a hammer. (Nah I'm not that mean).
Click to expand...
Click to collapse
Is your phone showing up in adb?

Heh had to look it up but after doing it...no just says List of devices attached. Nothing else.

Turbo Mach 5 said:
Heh had to look it up but after doing it...no just says List of devices attached. Nothing else.
Click to expand...
Click to collapse
Hmm... is your USB debugging on? If yes, try reinstalling the driver.

Turbo Mach 5 said:
Heh had to look it up but after doing it...no just says List of devices attached. Nothing else.
Click to expand...
Click to collapse
It seems to me like a driver issue.
if while in fastboot mode fastboot devices does not show the device, The RUU will not work.
uninstall HTC driver and HTC sync and any other phone software (for samsung or whatever else)
Install latest HTC sync
make sure fastboot devices lists your device, then run the RUU

exad said:
It seems to me like a driver issue.
if while in fastboot mode fastboot devices does not show the device, The RUU will not work.
uninstall HTC driver and HTC sync and any other phone software (for samsung or whatever else)
Install latest HTC sync
make sure fastboot devices lists your device, then run the RUU
Click to expand...
Click to collapse
Roll, yah USB Debugging is on hehe. I even turned it off and back on. Exad: Ok. Uninstalling both HTC Sync and Samsung Kies (have to use that for my brother's Galaxy S2 Skyrocket). Uninstalling both now (might have to also run out of town so reply could be a little late).

Turbo Mach 5 said:
Roll, yah USB Debugging is on hehe. I even turned it off and back on. Exad: Ok. Uninstalling both HTC Sync and Samsung Kies (have to use that for my brother's Galaxy S2 Skyrocket). Uninstalling both now (might have to also run out of town so reply could be a little late).
Click to expand...
Click to collapse
Hey you said you were on Windows 8. You may have to manually install the driver to get it work, that's what I had to do. Or you could use the universal adb driver, but if you're gonna RUU, I'd be safe and use the HTC one.

RollTribe said:
Hey you said you were on Windows 8. You may have to manually install the driver to get it work, that's what I had to do. Or you could use the universal adb driver, but if you're gonna RUU, I'd be safe and use the HTC one.
Click to expand...
Click to collapse
Alrite after removing both managers (HTC and Samsung), reinstalling, and then having to turn off debugging then turn it back on...it now sees it
HT25CW****** device (first said offline but I looked at the phone and noticed it was asking for permission).
Time to continue flashing! I think what happened is I had the universal USB drivers but then had to install KIES for my bro so it replaced them. Then installing HTC on top of that made it give up. Thanks you two! I'll post if I have any other strange issues.

Turbo Mach 5 said:
Alrite after removing both managers (HTC and Samsung), reinstalling, and then having to turn off debugging then turn it back on...it now sees it
HT25CW****** device (first said offline but I looked at the phone and noticed it was asking for permission).
Time to continue flashing! I think what happened is I had the universal USB drivers but then had to install KIES for my bro so it replaced them. Then installing HTC on top of that made it give up. Thanks you two! I'll post if I have any other strange issues.
Click to expand...
Click to collapse
Annd now when I was all set to update to his latest one he posted, H8rift goes and begins posting nightlies and I don't have to downgrade touchpanel firmware! Hahaha (I had downgraded it and was about to install)! Still, thank you guys. I'm back in business!

Dear Turbo Mach 5,
Could you please provide the detailed steps you followed to RUU your ATT HTC One X.
I am also planning to update my ATT HTC One X with 3.18 RUU to use CM 10.2 based roms.
Please provide this information which will help me to start with my device.
1) Whether we need to re-lock the bootloader ? (I have SuperCID and S-Off)
2) After RUU ing whether we need to unclok the boot loader and root the device if we have SuperCID and S-off?
Thanks and Regards,
Sathish.
Turbo Mach 5 said:
Alrite after removing both managers (HTC and Samsung), reinstalling, and then having to turn off debugging then turn it back on...it now sees it
HT25CW****** device (first said offline but I looked at the phone and noticed it was asking for permission).
Time to continue flashing! I think what happened is I had the universal USB drivers but then had to install KIES for my bro so it replaced them. Then installing HTC on top of that made it give up. Thanks you two! I'll post if I have any other strange issues.
Click to expand...
Click to collapse

sathish804 said:
Dear Turbo Mach 5,
Could you please provide the detailed steps you followed to RUU your ATT HTC One X.
I am also planning to update my ATT HTC One X with 3.18 RUU to use CM 10.2 based roms.
Please provide this information which will help me to start with my device.
1) Whether we need to re-lock the bootloader ? (I have SuperCID and S-Off)
2) After RUU ing whether we need to unclok the boot loader and root the device if we have SuperCID and S-off?
Thanks and Regards,
Sathish.
Click to expand...
Click to collapse
You don't need to relock your bootloader to the run the RUU because you have s-off. And your s-off status and unlocked bootloader should survive the RUU process. All you need to do afterwards is flash TWRP recovery again, then you can flash a ROM. Please be aware that cm10.2 is still very alpha and multiple users have reported bricks from running it.
Sent from my Evita

Hi timmaaa,
Thank You very much for the clarification and update on cm 10.2 rom.
I was thinking with RUU my bootloader is going to re-lock even though I have S-off.
Thanks and Regards,
Sathish.
timmaaa said:
You don't need to relock your bootloader to the run the RUU because you have s-off. And your s-off status and unlocked bootloader should survive the RUU process. All you need to do afterwards is flash TWRP recovery again, then you can flash a ROM. Please be aware that cm10.2 is still very alpha and multiple users have reported bricks from running it.
Sent from my Evita
Click to expand...
Click to collapse

Hi,
I'm having trouble using the RUU as well. The problem seems to be getting the usb driver for my oneXL working. every time i plug it into my win7 pc, it goes through this installing drivers process but having clicked on "display details", the "android phone" component of the drivers says "failed". I've tried universal adb driver, and HTC usb driver with and without htc sync installed. the HTC sync manager keeps saying there is an update available for usb driver, even though I uninstalled the driver manager and htc sync.
Have not been able to get adb working, when i recently S_OFF my phone I had to use adb over wifi - but it worked.
Any help greatly appreciated, thanks!

Your post is a bit confusing as to which drivers you actually have installed. Download the latest HTC Sync Manager from the HTC One XL page at HTC.com, install it, connect your phone, drivers will install, uninstall HTC Sync Manager but leave drivers installed. Also, make sure you're using a usb 2.0 port and the HTC cable that came with the phone.
Sent from my Evita

thelloydr said:
Hi,
I'm having trouble using the RUU as well. The problem seems to be getting the usb driver for my oneXL working. every time i plug it into my win7 pc, it goes through this installing drivers process but having clicked on "display details", the "android phone" component of the drivers says "failed". I've tried universal adb driver, and HTC usb driver with and without htc sync installed. the HTC sync manager keeps saying there is an update available for usb driver, even though I uninstalled the driver manager and htc sync.
Have not been able to get adb working, when i recently S_OFF my phone I had to use adb over wifi - but it worked.
Any help greatly appreciated, thanks!
Click to expand...
Click to collapse
Scratch that...
Manually installed drivers and i got it working. Had to manual install twice, after one more error (171 this time), the RUU is applied. CM10.2 here i come!

htc vivid
Freinds My HTC vivid is like dead not able to turn on nor charging and not able to run ruu, its showing unrecognized malfunctioned, did uninstall and install of driver still nothing is happening please help.

biradar said:
Freinds My HTC vivid is like dead not able to turn on nor charging and not able to run ruu, its showing unrecognized malfunctioned, did uninstall and install of driver still nothing is happening please help.
Click to expand...
Click to collapse
You're in the wrong section, this is the HTC One XL section, you need to go here:
http://forum.xda-developers.com/htc-vivid

Just had the same issue trying to manually update my M9 to Nougat. Rebooted to download mode (Volume down & Power from off state) and it worked.

New out of Box Phone not connectting to PC

Help needed,
Got a brand new HOXL, unlocked yesterday and from AT&T shipped to me in the carribeans. So shipping back is not an option.
Android 4.1.1
software version 3.18
Hboot 2.14
S-On
Boot loader Locked
Two windows 7 laptops
Two usb cables, one official from HTC and another that I had lying around at home
The phone doesn't connects to a Pc and it charges. However the PC does not recognize the device. And usually says something about unidentified usb device.
- I have gone into device manager and tried different things (uninstalling device/leaving device plugged in while reboting the PC...etc) to get it to work.
- And I have the latest drivers installed via HTC sync.
- Tried installing only the drivers and then also tried installing all of HTC sync.
- I can get into fastboot and while there phone is still undetected by the laptop.
- If i try and open recovery I get a screen with a phone picture on it and a caution sign and after a while phone reboots. Don't know if thats normal or if its cause my bootloader is still locked.
Any assistance will be greatly apprecuated. thanks.

Do you have the latest version of HTC Sync Manager? The connection protocol changed from usb mass storage to MTP so I believe you need the latest version. I'd advise uninstalling HTC Sync and all drivers and downloading HTC Sync Manager from HTC again. The caution sign when entering recovery is normal, that's normal for stock recovery. Are the usb ports on your laptop 2.0 or 3.0?
Sent from my Evita

Thanks. I was able to sort the problem and I've gone on to unlock bootloader, flash twrp and root. Haven't done s-off yet or tried any new Rom. Wanna get a feel of the stock Rom first that way I have a better handle on what I Want or dont want.
My fix was kinda strange. Previously had HTC sync manager fully installed and then only the drivers of HTC sync installed. Didn't uninstall anything. Put my phone into hboot and then went into fastboot then plugged it in. The laptop discovered the phone and stayed downloading a "android 1.0" driver. My hox could now be recognized as a usb device only in fastboot. Test the phone, and this time around windows downloaded and installed all the necessary drivers.
Strange.
Any Rom recommendations? Looking for something as close to stock as close to stock as possible. Currently leaning towards the viper x sense5 Rom.
Sent from my HTC One X using xda app-developers app

I won't say any recommendations, but make sure that everything you flash is from this device forum ONLY.
Sent from my One X using Tapatalk

Lol.... of course. That goes without saying. I've been around for quite a bit.
Anyways, S-offed and all that. Gonna let the phone run as stock for a week or two while I explore my rom options.

Lorddeff07 said:
Lol.... of course. That goes without saying. I've been around for quite a bit.
Click to expand...
Click to collapse
Nothing here "goes without saying". Its far better for folks to point out the seemingly "obvious"; instead of folks bricking due to something that went unsaid. Aside from your post count and join date, we know nothing of your experience. And even so, just because you know it, does not mean that everyone reading this thread will also know it. So its just good all around to point out even the simple things.
---------- Post added at 11:31 AM ---------- Previous post was at 11:29 AM ----------
Lorddeff07 said:
Any Rom recommendations? Looking for something as close to stock as close to stock as possible. Currently leaning towards the viper x sense5 Rom.
Click to expand...
Click to collapse
Since you've been around for a while, you should know that asking for ROM recommendations is a no-no on XDA. Just look through the ROMs and see what fits your needs and wants. And its not hard to figure out which ROMs are well liked without asking.
---------- Post added at 11:33 AM ---------- Previous post was at 11:31 AM ----------
Lorddeff07 said:
- If i try and open recovery I get a screen with a phone picture on it and a caution sign and after a while phone reboots. Don't know if thats normal or if its cause my bootloader is still locked.
Click to expand...
Click to collapse
Its normal, as that is the stock recovery. You won't have a custom recovery until you unlock the bootloader and flash a custom recovery.

Get what u mean Redpoint.
And to everyone else this problem has been resolved. I have done everything including using a custom Rom. For those that may have a similar problem this was my fix.
- make sure usb debug is on. put ur phone in hboot and plug to computer. Windows should detect the phone and install one driver "android 1.0
- with phone still plugged to computer, reboot phone. Windows should detect device and install all other drivers.
- done.
Sent from my HTC One XL

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