Database Info

[Q] HELP? I'm stuck in QHSUSB Download Mode?

I went to flash some things...and now it's stuck in the qualcomm download mode? How the hell do I get out of it??

You can't, you're screwed
I had this on my old Sensation, it stands for Qualcomm High Speed USB
Basically what's happened is your phone has lost the drivers for the chip set and needs them re-installed, as far as I'm aware, no-one has managed to find a way to do it.
Hope its still under warranty mate, I think its the only way you'll get it sorted
Sent from my GT-I9100 using xda premium

redrumsilence said:
You can't, you're screwed
I had this on my old Sensation, it stands for Qualcomm High Speed USB
Basically what's happened is your phone has lost the drivers for the chip set and needs them re-installed, as far as I'm aware, no-one has managed to find a way to do it.
Hope its still under warranty mate, I think its the only way you'll get it sorted
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
You're kidding, right? Well I installed the drivers for that, and it's now recognized by my computer, but there's nothing I can do? At all?

What exactly did you do to cause this?
Sent from my HTC One X using Tapatalk 2

random1204 said:
You're kidding, right? Well I installed the drivers for that, and it's now recognized by my computer, but there's nothing I can do? At all?
Click to expand...
Click to collapse
When it happened to me, I found the QHSUSB drivers and installed them, my computer recognised my Sensation, but nothing else.
I scoured XDA, Google, all sorts, I couldn't find anything, I just sent mine in under insurance and got a new one
Sent from my GT-I9100 using xda premium

Your not screwed. Pmed
Sent from my HTC One X using xda premium

Galaxy s3 Tmobile in same state
18th.abn said:
Your not screwed. Pmed
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Hey do you have any info on this mode? I would love to have some kind of info as to a course of action, even though this is for a different model...

18th.abn said:
Your not screwed. Pmed
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
i to am stuck in this mode. i flashed clockwork recovery (gsm) on my at&t one x thinking it was for our phone since it wasnt there the last time i checked. after i did a reboot the phone never came back on.

rob219 said:
i to am stuck in this mode. i flashed clockwork recovery (gsm) on my at&t one x thinking it was for our phone since it wasnt there the last time i checked. after i did a reboot the phone never came back on.
Click to expand...
Click to collapse
Is it completely dead and unresponsive? Just flashing the wrong recovery shouldn't kill your phone. I've done it myself a couple of times by accident, and fixing it was just a matter of flashing the right one.
Sounds like you actually flashed the wrong rom. Doing that can kill your bootloader, which will put you in QHSUSB mode. There is a way out that's been discussed, but I can't find it at the moment. It involves pushing a new hboot onto your phone and I believe requires Linux.

iElvis said:
Is it completely dead and unresponsive? Just flashing the wrong recovery shouldn't kill your phone. I've done it myself a couple of times by accident, and fixing it was just a matter of flashing the right one.
Sounds like you actually flashed the wrong rom. Doing that can kill your bootloader, which will put you in QHSUSB mode. There is a way out that's been discussed, but I can't find it at the moment. It involves pushing a new hboot onto your phone and I believe requires Linux.
Click to expand...
Click to collapse
it wasnt a rom. it was definetly the clockwork recovery in rom manager. it said gsm next to htc one x and its a new one so i was stupid enough to flash it. i did a reboot and it was dead. i already talk to at&t about it and there sending me a new one.

rob219 said:
it wasnt a rom. it was definetly the clockwork recovery in rom manager. it said gsm next to htc one x and its a new one so i was stupid enough to flash it. i did a reboot and it was dead. i already talk to at&t about it and there sending me a new one.
Click to expand...
Click to collapse
That's interesting, because I did (almost) the same thing. When I first unlocked my HOX, I installed ROM Manager and accidentally flashed the Samsung GSII recovery. I was able to fix it just by going back to bootloader and adb flashing the correct version.

iElvis said:
That's interesting, because I did (almost) the same thing. When I first unlocked my HOX, I installed ROM Manager and accidentally flashed the Samsung GSII recovery. I was able to fix it just by going back to bootloader and adb flashing the correct version.
Click to expand...
Click to collapse
just found out the one x international recovery flashes on the partition that on our phones is the boot loader partition. could be fixed inside of linux, but i didnt get into how.

I had the same problem with the QHSUSB Download it turns out my phone had a really drained battery so how I managed to fix it was had it plugged into my computer and let the lights flash until i got a solid amber light. after about 15 minutes, I turned it on and it worked fine!

on my tablet i pressed for a really long time the power button and then it started up
it enters almos allways in qualcomm download mode when the battery is depleated.

you revived a dead thread to say something about your tablet?

I'm going to go revive some too now
Sent from my HTC One XL using Tapatalk 2

DvineLord said:
you revived a dead thread to say something about your tablet?
Click to expand...
Click to collapse
Someone can find my reply useful, compared to you and the other troll that did not say anything useful.

Same situation for me .. i flashed TWRP, backedup my rom, flashed a new rom and reboot. black screen, no light, unresponsive .. this same message shows up on my windows machine "QHUSB_LOAD no driver found"

atombone said:
Same situation for me .. i flashed TWRP, backedup my rom, flashed a new rom and reboot. black screen, no light, unresponsive .. this same message shows up on my windows machine "QHUSB_LOAD no driver found"
Click to expand...
Click to collapse
I'm guessing you flashed an international ROM on your One XL. That will do it.

iElvis said:
I'm guessing you flashed an international ROM on your One XL. That will do it.
Click to expand...
Click to collapse
Its a One X (ATT) but your probably right. I downloaded it from ONEXROOT.com. just strange to me that because i flashed a rom it screws the bootloader. ugh... sucks

Tip/warning rom manager recovery for htc one x (gsm)

I am creating this post as a tip and warning to everyone with an at&t htc one x (mostly noobs for help). If you have rom manager on your phone do not use it to flash the new recovery listed for the htc one x (gsm). I've been messing with android since 2009, but me seeing a new recovery for the one x with (gsm) next to it thought hey finally got an official clockwork recovery for our phones!!!!! Well i was wrong. Its for the international versions only not ours. The partition it writes the recovery to is on our bootloader partition, and flashing it will kill your phone. I flashed it, kept it on for hours but as soon as i rebooted the phone it turned off and would not turn on or charge. You'll pretty much be screwed and have to get a new phone unless you know how to run linux and ask for help fixing it which is harder than you think. Again do not flash the htc one x (gsm) recovery in rom manager!!!!!
Hope this helps some of you before hand and not after.
If this post isn't necessary i am sorry and please close it.

Nobody should ever use ROM Manager for anything, EVER.
Sorry for your loss.

Why would you flash a recovery for a different device and expect it to work?
When ROM manger is supported on your device its a great tool, like on the sgs2. If its not officilially supported on your device, don't mess with it.
Sent from my Nexus 7 using xda premium

nooomoto said:
Why would you flash a recovery for a different device and expect it to work?
When ROM manger is supported on your device its a great tool, like on the sgs2. If its not officilially supported on your device, don't mess with it.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
it was new on there at the time and with gsm next to i i figured it was for ours, anyway point is if i knew it wasnt for my phone i wouldnt have flashed it.

rob219 said:
it was new on there at the time and with gsm next to i i figured it was for ours, anyway point is if i knew it wasnt for my phone i wouldnt have flashed it.
Click to expand...
Click to collapse
in fact, it is not really that hard to fix. Just re-lock the phone via fastboot. then run RUU package from AT&T
It should set every thing back to original.
if your phone is not respond RUU, try reboot on RUU via fastboot.
By the way, The only recovery that works now is TWRP
Use this one only

sugeraddict said:
in fact, it is not really that hard to fix. Just re-lock the phone via fastboot. then run RUU package from AT&T
It should set every thing back to original.
if your phone is not respond RUU, try reboot on RUU via fastboot.
By the way, The only recovery that works now is TWRP
Use this one only
Click to expand...
Click to collapse
The ruu has to access the boot loader to verify your version. If you end up flashing a device and it writes certain partitions of your boot loader (ICJ).... Well your left with a permabrick, until someone finds a way to JTAG the One X(AT&T). I've heard that its already been done, but the person who has performed it has kept the pinout secret.
I'm not entirely sure which partitions your ROM manager has wrote to, if you can find that out you might be able to fix it... Depending on which ones have been written too.
Sent from my One X using xda app-developers app

Zombie thread alert!

Like many of us have said before. We are not the one x. We are the one XL.
Sent from my One X using xda app-developers app

_MetalHead_ said:
Nobody should ever use ROM Manager for anything, EVER.
Sorry for your loss.
Click to expand...
Click to collapse
Sorry, but I disagree!
I've had more problem locating backup files and restoring when in TWRP, than ROM manager!
Mike

MaverickCoast said:
Sorry, but I disagree!
I've had more problem locating backup files and restoring when in TWRP, than ROM manager!
Mike
Click to expand...
Click to collapse
You must be doing something wrong then. You don't even need to locate backups with TWRP, they're found automatically. Anyway, was it really necessary to revive an 18 month old thread just to say that?
Sent from my Evita

Can't flash a ROM. Help!

I can get it to get into recovery mode, but it wont go any further than the red lettered warning banner. I tried to flash the ROM from the clockwork mod app from the market. No luck. My phone is not in the list of phones in the "Flash clockwork mod recovery". I tried to flash the 5.8.4.0 endeavoru.img file to my phone, but in my command prompt on my computer, it doesn't recognize my command as a batch command or anything. Any help folks? I was trying to find a stick on rooting, unlocking bootloader, and then flasing roms, but to my surprise I didn't find them all in one. I don't know what I'm doing wrong at this point. Spent a few hours last night, and now it all seems like a blur. Help please!

CP24EVA said:
I can get it to get into recovery mode, but it wont go any further than the red lettered warning banner. I tried to flash the ROM from the clockwork mod app from the market. No luck. My phone is not in the list of phones in the "Flash clockwork mod recovery". I tried to flash the 5.8.4.0 endeavoru.img file to my phone, but in my command prompt on my computer, it doesn't recognize my command as a batch command or anything. Any help folks? I was trying to find a stick on rooting, unlocking bootloader, and then flasing roms, but to my surprise I didn't find them all in one. I don't know what I'm doing wrong at this point. Spent a few hours last night, and now it all seems like a blur. Help please!
Click to expand...
Click to collapse
Do some research first because seems like u don't have even a custom recovery or even roooted... Now also never install anything that says endeavour or you will **** up your phone enough said...now do u have att one x or rogers telstra

WOAH, STOP RIGHT THERE.
endeavoru.img IS THE WRONG IMAGE!!!! I can smell a brick!!! the endeavoru image is for the quad core tegra one x. I am assuming you have a OneXL or one of the other Qualcomm DUAL CORE One X's
Our phone is called EVITA.
If you have a non ATT one x like a Telstra One XL or rodgers go to htcdev website.
If you have a ATT version I have recently found out that some versions cannot be rooted, and root is needed to unlock the bootloader. If it has ATT logo on the top where HTC should be, then you need to know the version number of your current rom before putting in any more effort to unlock. Check settings>about phone>
Check the forum in the One X Android Development/[INDEX] AT&T/ROGERS One X Resources Compilation Roll-Up (Updated 10/2/12) for the versions that can be rooted/unlocked.
Hope this helps
-Liam

mine is the ATT version......
My phone isn't bricked yet...phew. SO....going to get the EVITA then. right? for ATT version?

First thing is first you need to know the version of the stock rom you have, go to settings/about phone, I believe that if your version is greater than 1.85 then you are pretty screwed. You can only wait until A) ATT allow unlocking B) someone finds an exploit. If your One X is brand new, I doubt it is 1.85 as this is an old version.

llambkin said:
First thing is first you need to know the version of the stock rom you have, go to settings/about phone, I believe that if your version is greater than 1.85 then you are pretty screwed. You can only wait until A) ATT allow unlocking B) someone finds an exploit. If your One X is brand new, I doubt it is 1.85 as this is an old version.
Click to expand...
Click to collapse
Many phones are still being sent out with 1.85/1.73:angel: and to op DONT use clock word mod oonce you root and unlock bootloader I will show u which recovery to flash

WOW, Thats good. Ours are shipped with the latest, well at least my sisters one was. I thought she would have been screwed, But I was able to unlock with HTCDEV
@omario8484, is there a reason for not using CWM? I have it on my OneXL. I got the touch version, TWRP is good I guess, but I am more familiar with the CWM interface.
-Liam

omario8484 said:
Many phones are still being sent out with 1.85/1.73:angel: and to op DONT use clock word mod oonce you root and unlock bootloader I will show u which recovery to flash
Click to expand...
Click to collapse
I'm simply looking for a link to the evita version. I keep seeing the other one .
Sent from my HTC One X using Tapatalk 2

Also mine was 1.82. Found it on craigslist.
Sent from my HTC One X using Tapatalk 2

AWESOME!!!
Try This http://forum.xda-developers.com/showthread.php?t=1777773
:good:

CP24EVA said:
Also mine was 1.82. Found it on craigslist.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
That's because clock work doesn't support out phone officially !!!!!!!!!!!!!

ChummyDays said:
If you flash some roms with cwm, they sometimes will have serious problems. Twrp works with very Rom perfectly fine.
Click to expand...
Click to collapse
OK, I might flash back to TWRP then, I have always used CWM....I did like the skinnable interface of TWRP tho :

llambkin said:
OK, I might flash back to TWRP then, I have always used CWM....I did like the skinnable interface of TWRP tho :
Click to expand...
Click to collapse
Yes use twrp because USB mount works also some Tom's like he said will have problems

Ok, I got it all sorted. Out. My main problem is I didn't know what the goo interface let me do. Once I found out then it was cake from there. I'm loving this AOKP one so far.

I there a way to get to the play store that doesn't include using an internet browser?

CP24EVA said:
I there a way to get to the play store that doesn't include using an internet browser?
Click to expand...
Click to collapse
Maybe the play store app?

I don't see a play store app in the app tray at all. and when I press the PLAY STORE option in the menu tray, it does nothing.

bricked after flashing rom please help

I just obtaind root today and i flashed icecoldjelly and now my phone wont turn on. is there any way that i can fix this. i love this phone and just got it to my liking please help

We don't have an icecoldjelly ROM.
Please read before you flash.
Can you get to boot?
Sent from my One X using Tapatalk 2

superchilpil said:
We don't have an icecoldjelly ROM.
Please read before you flash.
Can you get to boot?
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
i got the rom from onex.com and they said the rom was for the one x, and no no boot

omarh3 said:
i got the rom from onex.com and they said the rom was for the one x, and no no boot
Click to expand...
Click to collapse
IceColdJelly is for the international One X, not the AT&T One XL.
Someone else managed to brick their phone doing this. Check this thread and do what I told the other guy:
http://forum.xda-developers.com/showthread.php?t=1953975

omarh3 said:
i got the rom from onex.com and they said the rom was for the one x, and no no boot
Click to expand...
Click to collapse
Goto - http://forum.xda-developers.com/showthread.php?p=33198089
User had similar issue and he solved

omarh3 said:
I just obtaind root today and i flashed icecoldjelly and now my phone wont turn on. is there any way that i can fix this. i love this phone and just got it to my liking please help
Click to expand...
Click to collapse
Do you have the 2.20 hboot? I imagine you do if you just rooted today. If that is the case you're lucky since hboot partition is read only and cannot be clobbered. Just re-flash TWRP recovery via fastboot and flash a ROM for the one XL and you should be good to go.
If you have pre-2.20 hboot you might be bricked.

denversc said:
Do you have the 2.20 hboot? I imagine you do if you just rooted today. If that is the case you're lucky since hboot partition is read only and cannot be clobbered. Just re-flash TWRP recovery via fastboot and flash a ROM for the one XL and you should be good to go.
If you have pre-2.20 hboot you might be bricked.
Click to expand...
Click to collapse
same thing happened to me and it was the same rom i think please help in any way you can

nvidia31337 said:
same thing happened to me and it was the same rom i think please help in any way you can
Click to expand...
Click to collapse
You flashed IceColdJelly? Your phone is completely dead?

iElvis said:
You flashed IceColdJelly? Your phone is completely dead?
Click to expand...
Click to collapse
yeah completely and says same message in device manager

nvidia31337 said:
yeah completely and says same message in device manager
Click to expand...
Click to collapse
You're bricked, sorry. There is a way out if you have access to a Linux computer; see that other thread.

yea same here cant even get into recovery, same error sound when connected to the pc. Dont have access to a linux computer, No effect when i try to put in recovery mode or anything. Looks like im going to have to get a new phone

Try the steps here:
http://unlimited.io/qhsusbdload.htm
Everyone has access to a linux computer, you download a live cd, burn it and then restart your computer to boot into linux

area51avenger said:
Try the steps here:
http://unlimited.io/qhsusbdload.htm
Everyone has access to a linux computer, you download a live cd, burn it and then restart your computer to boot into linux
Click to expand...
Click to collapse
Is this confirmed to work on One X's bricked from flashing international ROMs? I've seen it mentioned several times before that Qualcomm download mode can be recovered from using a Linux computer. But this is the first time I've actually seen the instructions. And it really doesn't look all that complicated.
Seems like quite a few people that have bricked (by flashing international ROMs) would benefit from this, and it deserves its own thread.

redpoint73 said:
Is this confirmed to work on One X's bricked from flashing international ROMs? I've seen it mentioned several times before that Qualcomm download mode can be recovered from using a Linux computer. But this is the first time I've actually seen the instructions. And it really doesn't look all that complicated.
Seems like quite a few people that have bricked (by flashing international ROMs) would benefit from this, and it deserves its own thread.
Click to expand...
Click to collapse
Cannot confirm if this can fix a corrupted hboot partition, but it's worth a shot. Haven't found any solid guides for pushing a new hboot partition to the phone while in this mode yet. Also do not want to brick my phone to test it

redpoint73 said:
Is this confirmed to work on One X's bricked from flashing international ROMs? I've seen it mentioned several times before that Qualcomm download mode can be recovered from using a Linux computer. But this is the first time I've actually seen the instructions. And it really doesn't look all that complicated.
Seems like quite a few people that have bricked (by flashing international ROMs) would benefit from this, and it deserves its own thread.
Click to expand...
Click to collapse
didn't beaups write something about this at some point, trying to find it again..

what commands do i run to un brick my phone? ive downloaded a linux based os please help. the phone is compleatley bricked but some one said i could unbrick it in this fashon

omarh3 said:
what commands do i run to un brick my phone? ive downloaded a linux based os please help. the phone is compleatley bricked but some one said i could unbrick it in this fashon
Click to expand...
Click to collapse
and ive run the commands that were in the link and it says command not found

Did you pay attention to: Type the following commands (note: linux is case sensitive)

Crappyvate said:
didn't beaups write something about this at some point, trying to find it again..
Click to expand...
Click to collapse
Totally possible. I don't recall, or haven't seen it. I've seen a few posts to the effect of "if you have Linux, it can be fixed, PM me" but that is all I've seen. Would be nice if there was a writeup we can point people to (and I can add to my index thread).

Go to Evo 4g LTE forum and go to original development. 1st page should have a thread by yarrimapirate about downgrade. He recently figured how to brick, downgrade hboot and get s-off from QHuSB. Mode. The guys is a genius. That thread may have some answers or at least some help or info for you. People in that thread are stepping over themselves trying to help people.
Good luck.
I'd post a link, but I know as soon as I step out of this thread I'll never find it again (xda app)
Edit: go here http://forum.xda-developers.com/showthread.php?t=1940512
[HBOOT][10/24/12] 1.15/1.19 downgrade tool (Linux)
hurled from my AOKP'd Evo LTE. Enjoy.

[Q] Help! Bricked HTC One X AT&T

I've been using Hassoon2000's All in one toolkit. I successfully unlocked the boot loader. I was going to install Cyanogenmod 10. I copied the boot.img into the kernals folder for the AIO toolkit. I flashed that and that's where it went south. My phone continuously rebooted at the HTC bootup screen.
After some reading I have "relocked" the bootloader. I attempted to flash what I thought was the stock RUU. I can get into fast boot, but not the recovery. ( I was using the TWRP recovery that came with the tool kit). If I try to choose factory reset, it acts like it's flashing my phone (gray screen with a progress bar, but then goes back into fastboot after about 30sec.)
Am I SOL? I'm willing to compensate via pay pal if we get this thing going. If not, I did find a site call JTag brick repair.

When you flashed the kernel, did you install the actual Rom? If your phone can turn on, its not bricked. Which ruu did you download? Why isn't it working?
Sent from my HTC One XL using xda app-developers app

area51avenger said:
When you flashed the kernel, did you install the actual Rom? If your phone can turn on, its not bricked. Which ruu did you download? Why isn't it working?
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
I found an ruu after some googling. I perhaps didn't get the right one. No I didn't install the rom after I flashed the kernel. I flashed the kernel first, then I was going to boot into the recovery to install the rom. The phone just hung at the HTC screen before going into recovery. In red letters it says: This build is for development purposes only... etc"

Did you hold volume down and power at the same time to boot into recovery? Also make sure you get the right ruu. Which carrier are you on and what firmware were you before you flashed? The ruu is an exe you run from your desktop while your phone is in fastboot
Sent from my HTC One XL using xda app-developers app

Here's where I'm currently at. I have the bootload unlocked again through the toolkit. I also have the TWRP installed. I CAN get into TWRP.

I have AT&T, I'll do some searching on trying to find an RUU.
Hboot-1.14.0002
Radio-0.19as.32.09.11_2
openDSP-v29.1.0.45.0622

Awesome. Now mount USB storage in twrp and plug it in to your computer. If windows asks you to format. Say yes and format fat32. Copy the cm10.zip file to your sd card. Install from twrp. You may have to flash the boot.img again in fastboot.
Sent from my HTC One XL using xda app-developers app

I get an E:Error in sdcard/cm10.zip (Status 7)
Error flashing zip
Updating partition details...
I did do a factory reset and wipe cache.

Is it the right cm10 for HTC evita

omario8484 said:
Is it the right cm10 for HTC evita
Click to expand...
Click to collapse
I'm doing endevarou. I have the HTC One X, not the XL.

You have the one xl if you have the dual core att evita. if you have the quad core international one x then it's the endeavor.
Sent from my HTC One XL

deathbyenduser said:
I'm doing endevarou. I have the HTC One X, not the XL.
Click to expand...
Click to collapse
If so, then you are in the wrong forum, and if you used the toolkit from this forum, it also explains why you are stuck in the state you are. This forum is for the Evita. Are you sure you have the quad core Tegra3 version? What carrier is your phone from?
Also, if you can get into hboot, you are nowhere near bricked. Any type of power on (even just hboot) is not that hard to recover from. The only real brick is if the screen doesn't come on at all, and no charge LED when plugged to charger. Even then, the phone can sometimes be unbricked in Linux.

redpoint73 said:
If so, then you are in the wrong forum, and if you used the toolkit from this forum, it also explains why you are stuck in the state you are. This forum is for the Evita. Are you sure you have the quad core Tegra3 version? What carrier is your phone from?
Also, if you can get into hboot, you are nowhere near bricked. Any type of power on (even just hboot) is not that hard to recover from. The only real brick is if the screen doesn't come on at all, and no charge LED when plugged to charger. Even then, the phone can sometimes be unbricked in Linux.
Click to expand...
Click to collapse
Okay. I have the One XL for LTE. I was thinking the XL meant the bigger HTC One X that was out.

deathbyenduser said:
I'm doing endevarou. I have the HTC One X, not the XL.
Click to expand...
Click to collapse
deathbyenduser said:
Okay. I have the One XL for LTE. I was thinking the XL meant the bigger HTC One X that was out.
Click to expand...
Click to collapse
Really?! You my friend should not be flashing, rooting, unlocking bootloaders until you know the process and you can do it without reading how to do so. Learn how to swim before you jump into the deep end.

This is my third my root. I had the OG Motorola Droid and HTC Sensation with Tmobile. Now this One X LTE.
I can see why you said that though. I made an honest mistake. Looking back at the HTC models what I meant to say for some stupid reason I thought the HTC One X + (new one for att) was actually the HTC One XL. So I confused myself, flashed the wrong kernel. Luckily with some confirmation from you guys I'm back on the road. My phone is working.
My phone is working with CM10. I just need to get a compatible version of Gapps on. I'll be sending someone beer money. :victory:

deathbyenduser said:
This is my third my root. I had the OG Motorola Droid and HTC Sensation with Tmobile. Now this One X LTE.
I can see why you said that though. I made an honest mistake. Looking back at the HTC models what I meant to say for some stupid reason I thought the HTC One X + (new one for att) was actually the HTC One XL. So I confused myself, flashed the wrong kernel. Luckily with some confirmation from you guys I'm back on the road. My phone is working.
My phone is working with CM10. I just need to get a compatible version of Gapps on. I'll be sending someone beer money. :victory:
Click to expand...
Click to collapse
Great to hear.
You are very lucky you didn't do it the other way around (flash an endeavor rom on an evita device), as you would be the proud owner of a very expensive paperweight.
HTC can get stuffed for naming 3 different phones almost exactly the same One X/ One XL (or AT&T One X) / One X+. It is a minefield for people new to the phone.

Regardless of how many phones you've rooted, its pretty clear that you didn't do the enough reading to know the difference between the X, XL, and X+, and to know what you own. As already mentioned, you're lucky you didn't brick.
Only flash things from our forum, and you'll be safe: http://forum.xda-developers.com/forumdisplay.php?f=1538