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
Related
I checked all the other bricked threads and none have the same problem as me.
My HTC ONE X will not boot and or charge. I cannot get access to the bootloader or recovery.
My HTC ONE X had it's bootloader unlocked via the rogers htc-dev method. I also installed clockwork recovery. It is rooted also but you prob figured that already...
I pulled a bonehead move by flashing the MIUI rom the international one x by changing the update script to flash onto my phone. After it flashed it looked like it worked. When I left recovery and shut the phone off it would not turn back on.
I called AT&T they said they will switch it for me when they get a shipment but I want to keep this phone because the boatloader is unlocked and they might patch the rogers method.
Thanks in advanced.
P.S. I know how to use adb and other tools such as RUU and they did not work.
Have you tried holding the power button for 10 seconds to reset it? You should see the 3 lights below flashing.
Ouch.... Another loss for htc sales
Sent from my HTC One X using xda premium
you cant get to hboot? 0.o
First of all, you should be able to get to H-Boot by holding volume down when turning it on.
Second of all, this is why they lock the bootloader in the first place.
-sassafras
Reply
equlizer said:
Have you tried holding the power button for 10 seconds to reset it? You should see the 3 lights below flashing.
Click to expand...
Click to collapse
No nothing happens even with the charging adapter plugged in.
kevina90 said:
you cant get to hboot? 0.o
Click to expand...
Click to collapse
Nope
sassafras_ said:
First of all, you should be able to get to H-Boot by holding volume down when turning it on.
Second of all, this is why they lock the bootloader in the first place.
-sassafras
Click to expand...
Click to collapse
H-Boot key combo is not working.
I have been flashing roms since the samsung moment, I built and modified roms on my EVO and ported roms from other phones to the EVO. I always had recovery to fall back onto to get my phone booting again. Even when I had the Xperia Play that required a PC to boot recovery I was still able to get the phone to work. This phone is strange that is will not even turn onto H-boot/Bootloader.
jfn0802 said:
H-Boot key combo is not working.
I have been flashing roms since the samsung moment, I built and modified roms on my EVO and ported roms from other phones to the EVO. I always had recovery to fall back onto to get my phone booting again. Even when I had the Xperia Play that required a PC to boot recovery I was still able to get the phone to work. This phone is strange that is will not even turn onto H-boot/Bootloader.
Click to expand...
Click to collapse
I like to play with my phones and this one is so finicky I'm scared to do too much.
I bricked one myself.
gunnyman said:
I like to play with my phones and this one is so finicky I'm scared to do too much.
I bricked one myself.
Click to expand...
Click to collapse
Im glad I have my iPhone to fall back on but it is really annoying that I cannot even get the bootloader to load. I only had it 3 days and already broke it.
Thank God the dude at AT&T cannot get into the bootloader also to see that is was tampered with so they are giving me a replacement.
And people wonder why at&t locks their phones down. I'm guessing you just told them "my phone broke...I have no idea what happened". Just lovely.
Sent from my HTC One X using Tapatalk 2
jfn0802 said:
Im glad I have my iPhone to fall back on but it is really annoying that I cannot even get the bootloader to load. I only had it 3 days and already broke it.
Thank God the dude at AT&T cannot get into the bootloader also to see that is was tampered with so they are giving me a replacement.
Click to expand...
Click to collapse
Where do they have them in stock? I need to replace mine (screen issue) and can't find any around here.
powerwagon said:
And people wonder why at&t locks their phones down. I'm guessing you just told them "my phone broke...I have no idea what happened". Just lovely.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
+ 1
Sent from my HTC One X using xda premium
powerwagon said:
And people wonder why at&t locks their phones down. I'm guessing you just told them "my phone broke...I have no idea what happened". Just lovely.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
+2
Honestly, not trying to call you stupid or something, but did you really think it was going to run on this phone when it was meant for another one? The GPU and CPU are completely different...
Anyway, I'm glad AT&T is replacing it for you. Hopefully if someone else bricks the same way then they will be able to get a replacement as well.
so you are smart enough to use adb, an RUU, unlock your bootloader, root, flash roms.......but you aren't smart enough to see the hundreds of posts saying that the international roms don't work on our phones??
lol
Coming from a phone that is virtually unbrickable (Captivate), I'm quite curious about how you managed to get it into this state. What exactly did you flash? Did the package contain both the system image and bootloaders for the tegra3 one x?
Just pull the batte..... oh
jmattp said:
Just pull the batte..... oh
Click to expand...
Click to collapse
+1 for when I drowned my first one and it was stuck in a boot loop. I know it could have been saved if the battery would have been taken out.
Sent from my HTC One X
modest_mandroid said:
Coming from a phone that is virtually unbrickable (Captivate), I'm quite curious about how you managed to get it into this state. What exactly did you flash? Did the package contain both the system image and bootloaders for the tegra3 one x?
Click to expand...
Click to collapse
My EVO was unbrickable too, I flashed a rom that was designed for the international version. It only contained system and other basic rom stuff, nothing that was crazy.
No idea why you wouldn't be able to boot into recovery then. I hope all HTC handsets aren't like this..
Sent from my SGH-I897 using XDA
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
I messed something up while trying to install ROM so I was playing around with it to see if I could fix it. When I try to reboot TWRP says "No OS install do you wish to reboot". Phone is screwed any suggestions on how to fix?
I'm facing a similar problem I believe:
On my HTC One X I successfully unlocked bootloader and then flashed a custom recovery TWRP 2.4.1.0 using the HTC One X All in One Kit. I then tried to install the latest version of Viper XL. When the installation started I got an assert message, something like this:
assert failed: getprop("ro.product.device")=="endeavoru" ||
getprop("ro.build.product")=="endeavoru" ||
getprop("ro.product.board")=="endeavoru" ||
Afterwards my phone went into the infinite reboot cycle and I've been unable to even make it to bootloader by holding down the power and volume keys until my hands went numb. No luck, still rebooting loop to the HTC home screen.
My carrier is AT&T if that matters.
Have I bricked it? Is there a way out of this? Any help at all would be greatly appreciated!
tfig88 said:
I messed something up while trying to install ROM so I was playing around with it to see if I could fix it. When I try to reboot TWRP says "No OS install do you wish to reboot". Phone is screwed any suggestions on how to fix?
Click to expand...
Click to collapse
Download a rom. Mount usb from within twrp. copy rom. flash rom.
Sent from my One X using xda app-developers app
zkuzmanic said:
I'm facing a similar problem I believe:
On my HTC One X I successfully unlocked bootloader and then flashed a custom recovery TWRP 2.4.1.0 using the HTC One X All in One Kit. I then tried to install the latest version of Viper XL. When the installation started I got an assert message, something like this:
assert failed: getprop("ro.product.device")=="endeavoru" ||
getprop("ro.build.product")=="endeavoru" ||
getprop("ro.product.board")=="endeavoru" ||
Afterwards my phone went into the infinite reboot cycle and I've been unable to even make it to bootloader by holding down the power and volume keys until my hands went numb. No luck, still rebooting loop to the HTC home screen.
My carrier is AT&T if that matters.
Have I bricked it? Is there a way out of this? Any help at all would be greatly appreciated!
Click to expand...
Click to collapse
Quad core or dual core. Just because you have an att sim doesn't mean you have an att one x
Sent from my HTC One XL
You tried to flash a Rom for the international version (endevoru) luckily that dev put in asserts so it didn't flash and didn't brick your device. Your phone is att version (evita) only flash things in these forums
Sent from my VENOMized HoxL
tfig88 said:
I messed something up while trying to install ROM so I was playing around with it to see if I could fix it. When I try to reboot TWRP says "No OS install do you wish to reboot". Phone is screwed any suggestions on how to fix?
Click to expand...
Click to collapse
If you can boot into recovery, then you should be fine. Just mount USB and copy ROM for evita into your sdcard, then flash it.
area51avenger said:
You tried to flash a Rom for the international version (endevoru) luckily that dev put in asserts so it didn't flash and didn't brick your device. Your phone is att version (evita) only flash things in these forums
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
That sounds likely, but then what do I do to break the reboot cycle?
954wrecker said:
Quad core or dual core. Just because you have an att sim doesn't mean you have an att one x
Sent from my HTC One XL
Click to expand...
Click to collapse
I'm not sure how I could tell. It has At&t printed on the One X at the top.
You have the att dual core so just find a Rom in this forum and you won't see that endeavor error
Sent from my HTC One XL
i have that same problem and did that but i didn't get a fix
cuteyr said:
i have that same problem and did that but i didn't get a fix
Click to expand...
Click to collapse
Did you flash boot image seperately? Hboot 1.14?
AT&T HTC OneX
Android 4.1.1
ViperXL
cuteyr said:
i have that same problem and did that but i didn't get a fix
Click to expand...
Click to collapse
this is nothing like your problem, this person tried to flash a rom for the endeavor you just need to flash a rom in the first place cause you wiped your phone and didnt flash a rom. all you need to go is go to recovery flash a rom and fastboot boot.img if you arent s-off.
DvineLord said:
this is nothing like your problem, this person tried to flash a rom for the endeavor you just need to flash a rom in the first place cause you wiped your phone and didnt flash a rom. all you need to go is go to recovery flash a rom and fastboot boot.img if you arent s-off.
Click to expand...
Click to collapse
Man is he sneaky. he is all over the place.
AT&T HTC OneX
Android 4.1.1
ViperXL
How many more times are people going to flash the wrong rom because of the crappy naming convention of this phone and the mislabeling of these forums. These forums should be called HTC one x evita!
OP, if all else fails.....flash a RUU to go back to stock
Sent from my One X using xda app-developers app
Palmetto_X said:
How many more times are people going to flash the wrong rom because of the crappy naming convention of this phone and the mislabeling of these forums. These forums should be called HTC one x evita!
OP, if all else fails.....flash a RUU to go back to stock
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I have to disagree. It says AT&T HTC One X. If the people would take the time to read and study what type of phone they have, they wouldn't have these kind of issues. They just go in, say "Oh man. That looks cool. I will flash that." Every rom I have seen on here tells you if it is for evita or states "International Only." Developers do not have the time to hold there hand and flash roms for them. They have jobs and do this work in their spare time for people who complain when it doesn't work. If you can't take the time to read and learn, stay with a stock phone or ask questions "before" you flash. I would be more than happy to show the links to the right steps. It's easier than trying to show them after the fact because they have know idea what they are doing in the first place. Everything you need to know is on this sight. I found it on my own. Don't be babies.
AT&T HTC OneX
Android 4.1.1
ViperXL
Actually, when I first bought my HTC One X I didn't know there were two different models and like always I rooted my phone and tried "ice cold jelly" and erased my whole OS after flashing the boot image (from image gui no less) and got stuck...that's how I discovered viper xl which is the best Rom in my opinion, but he may not be able to mount his SD card just in case Google HTC one X error ad card not mounted...team nocturnal has a fix
Sent from my HTC One X using xda premium
In a stroke of genius and attention to detail, I flashed the endeavor CM10 instead of the evita CM10 ROM to my ATT-branded HTC One X.
I unlocked, rooted, got CID 11111111, etc. before flashing the ROM. I had flashed CWM 6.something as the recovery option.
After flashing the incorrect ROM in CWM, I get nothing out of the phone. Blank screen, no red light, nothing. Hooking it up to a Windows box prompts me to install QHSUSB_DLOAD drivers.
I've tried JET and the evita unbricking thread (http://forum.xda-developers.com/showpost.php?p=33528546&postcount=1). The phone's emmc partitions do not show up, and JET times out on "waking device".
Am I totally SOL, or is there something else I can try?
shikind said:
In a stroke of genius and attention to detail, I flashed the endeavor CM10 instead of the evita CM10 ROM to my ATT-branded HTC One X.
I unlocked, rooted, got CID 11111111, etc. before flashing the ROM. I had flashed CWM 6.something as the recovery option.
After flashing the incorrect ROM in CWM, I get nothing out of the phone. Blank screen, no red light, nothing. Hooking it up to a Windows box prompts me to install QHSUSB_DLOAD drivers.
I've tried JET and the evita unbricking thread (http://forum.xda-developers.com/showpost.php?p=33528546&postcount=1). The phone's emmc partitions do not show up, and JET times out on "waking device".
Am I totally SOL, or is there something else I can try?
Click to expand...
Click to collapse
Your hit.. jtag or sell for parts. HTC can fix but gonna run a easy couple hundred dollars. Any warranty from att left?
Sent from my HTC One XL using xda premium
Phone was purchased when it was the new "in" thing, so a little over a year ago iirc. No warranty or insurance.
Sounds like I'm either off to cl for another one, or this is a good excuse to get the N4.
31ken31 said:
Your hit.. jtag or sell for parts. HTC can fix but gonna run a easy couple hundred dollars. Any warranty from att left?
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
This, unless you can travel back in time.
Id prob buy a nexus or another one x off Craig'slist or something
Sent from my HTC One X using xda premium
shikind said:
Phone was purchased when it was the new "in" thing, so a little over a year ago iirc. No warranty or insurance.
Sounds like I'm either off to cl for another one, or this is a good excuse to get the N4.
Click to expand...
Click to collapse
Wow - expensive mistake. Good luck on your next device!
Hey all, my One X won't boot past the splash screen.
I unlocked the bootloader this morning (HTC Dev Official) and the device worked fine. I then went a step further to root the device and the process I was using stalled and canceled out on me. I'm now left with a phone that doesn't get past the splash screen no matter weather I click on factory reset or recovery in the menu.
Not quite sure what to do, tried finding a RUU for my device but I couldn't find one that matched. (Not that I was entirely sure what I was looking for) I've cleared the fastboot cache with no avail.
First post here, thanks for any help or suggestions that you guys have.
You need to provide more information if you want help, it's very hard to help someone who just says "I tried something and it didn't work".
First off, do you have the One X or the One XL / at&t One X? What are your bootloader details? Which root exploit did you try?
Sent from my Evita
timmaaa said:
You need to provide more information if you want help, it's very hard to help someone who just says "I tried something and it didn't work".
First off, do you have the One X or the One XL / at&t One X? What are your bootloader details? Which root exploit did you try?
Sent from my Evita
Click to expand...
Click to collapse
Sorry, I realise I've left a few important parts out. It's a a One X International (Tegra 3 I believe), it's got S-on, and the bootloader is unlocked. I used this root kit (I can't post the link here, but here's the youtube vid name 'HTC One X - How To Root (Easy)') and halfway through the rooting process, it said 'Error, can't communicate with device'. Then I'm stuck at the splash screen.
I've successfully flashed TWRP 2.3 onto the device, and have just managed to copy the CM 10.3 onto the sd card, however when trying to install the zip I get an error message.
Thanks again, Hope that I make a little more sense this time.
Ok, but you're posting in the wrong forum. This is the One XL (dual core LTE) forum.
Sent from my Evita
timmaaa said:
Ok, but you're posting in the wrong forum. This is the One XL (dual core LTE) forum.
Sent from my Evita
Click to expand...
Click to collapse
Sorry, I didn't realise that. Where is the correct forum?
There's a text box that says "type to find your device here" at the top of the XDA website...
Sent from my Evita