Database Info

HTC deserves MAD props.

We have got to give it to HTC here. The One S is, quite possibly, the easiest phone to root and flash there is. The instructions are so easy, even a caveman can do it. It literally took me less than 20 minutes to get CM9 installed on my brand spankin new One S...and most of that time was spent waiting on the slow WiFi at Starbucks to catch up.
I'm in love. For now.

mrcrassic said:
We have got to give it to HTC here. The One S is, quite possibly, the easiest phone to root and flash there is. The instructions are so easy, even a caveman can do it. It literally took me less than 20 minutes to get CM9 installed on my brand spankin new One S...and most of that time was spent waiting on the slow WiFi at Starbucks to catch up.
I'm in love. For now.
Click to expand...
Click to collapse
Thank the devs not HTC. HTC actually slowed development at first by not releasing code right away. Samsung GS3 is actually easier.
Sent from my HTC One S using Xparent ICS Tapatalk 2

You've obviously never used a Motorola Triumph. That is the easiest phone to root and flash.
I hate that device.
Sent from my HTC VLE_U using xda app-developers app

villainhalf said:
You've obviously never used a Motorola Triumph. That is the easiest phone to root and flash.
I hate that device.
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
I like my Triumph seems pretty indestructible, yea it's easy to root and flash, I want the HTC evo V
next
Sent from my Triumph using xda app-developers app

You can say many great things about the one s, but it's NOT the easiest phone to root. You have to u unlock bootloader and we still don't have s off: /
Sent from my HTC One S using xda app-developers app

Perhaps I'm a little jaded. I came from using the Galaxy S II and the Vibrant where getting a custom ROM installed was considerably more time consuming.
I don't understand the disadvantages of unlocking the bootloader when HTC made it very easy to re-lock (though not with factory encryption) and they still honor hardware damages if the phone is still under warranty.
I also don't understand the advantages of having S-OFF. Perhaps your experiences are different, but I've never gained any advantages from switching radios on any device I've owned.
I guess using the regular USB drivers provided by Google and being able to unlock the bootloader directly from fastboot without having to decrypt its unlock key would have made it easier, but it was a moot point to me given that HTC made both of these very easy to do.
And yes, the developers here are nothing short of amazing.

The one thing I want S-OFF for is repartitioning. I don't need 2 gb for apps, 1 would do, and I certainly DO NOT need 4 gb for system. That's just crazy. So after that I will have 3 gb more storage for nandroids, music, videos etc. That will be awesome

Habarug said:
The one thing I want S-OFF for is repartitioning. I don't need 2 gb for apps, 1 would do, and I certainly DO NOT need 4 gb for system. That's just crazy. So after that I will have 3 gb more storage for nandroids, music, videos etc. That will be awesome
Click to expand...
Click to collapse
+1, looking for that. In the mean time I use the /data partition to store videos since it has like 1.5 GB lying around doing nothing. Just have to change the permission for /data to be readable by all. I would use the 2 GB+ on /system also, but then it would be erased whenever a new ROM is flashed I think.

The One S is far from being an easy phone to root. It's certainly not hard and don't require lot of steps or requirements like a Gold Card but still...
When I had a LG G2x, rooting it was baby easy: Install APX drivers on windows, boot the phone in update mode, shoot it CWM in one click with NvFlasher, flash your rom, done.

I found Samsung phones easier to Install custom Roms than HTC devices. Don't get me wrong, I love HTC's, soo much that I sold my 3weeks old SGSII just to buy the ONE S ( And I have owned other 5 HTC Phones)
On samsungs you only have to get into download mode and flash recovery and custom rom via Odin.
HTC made it easier now on the ONE Series, but you still have to unlock the bootloader via HTC Dev and bla bla bla bla, previous HTC Devices used to be a PITA considering we had to unlock bootloader (and in other cases install a ENG bootloader) hack to get Super CID, Obtain S-OFF and so on...

NienorGT said:
When I had a LG G2x, rooting it was baby easy: Install APX drivers on windows, boot the phone in update mode, shoot it CWM in one click with NvFlasher, flash your rom, done.
Click to expand...
Click to collapse
I was gonna mention this too. I hesitated to root my HOS for a couple of months because it seemed complicated compared to the G2x.
Sent from my HTC VLE_U using xda app-developers app

I thought the Desire was really easy to root and S-Off. Back in the day.
HTC don't really deserve any props. They give us a half assed unlock offering, when what people really want is s-off. When I had my One S, I could have really done with being able to partition and get some of the /data storage that I was never gonna use on to the /sdcard partition as I used up the measly amount of storage quite quickly.

Jigswa said:
I thought the Desire was really easy to root and S-Off. Back in the day.
HTC don't really deserve any props. They give us a half assed unlock offering, when what people really want is s-off. When I had my One S, I could have really done with being able to partition and get some of the /data storage that I was never gonna use on to the /sdcard partition as I used up the measly amount of storage quite quickly.
Click to expand...
Click to collapse
They could gave us a completely locked device...
Sent from my HTC One S using xda premium

I think the HTC phones which can use Revolutionary method are most easy to get S-OFF. Like Incredible S. The only thing you have to do is running a little tool.exe on your pc with your phone connected. Almost full automatic and in a few minutes. And yes we just could run that tool on out brand new untouched phones, to gain untouched ROM, Radio and Reovery with S-OFF. Only bootloader is modified.
No locks relocks or tampered messages. Getting back S-ON with full warranty is even more simple. Thats how it has to be.
Sent from my HTC One S using xda premium

If I were a cell manufacturer and I was tired of people sending back s=off bricks for warranty exchanges I would try to stop that from happening myself.
However, u can unlock bootloader flash recovery and SU in 5 minutes... seriously. And flashing roms in recovery along with any recovery action is SOOOOOO much faster on our phones then the Amaze 4g that had the s3.
So... really... its not hard to root or flash roms. S=off is another beast... but I get why they make it so hard.
Sent from my HTC One S using Tapatalk 2

I would say they deserve mad props, for sure, but its not for the "EASE" of unlocking. Obviously the king in that area would ne ANY nexus device. Its litterally ONE fastboot command and you are done!
However, i found this fairly simple to root and install a custom rom. what i think HTC really deserves props for is the hardware of this phone AND honestly... I know i am gonna get slammed for this, but... SENSE 4. Seriously. Coming from someone that has owned3 previous HTC phones all with varying versions of sense, i gotta say sense 4 is pretty awesome. I do LOVE stock android, but i cant honestly say that it performs any better than TrickDroid or Axiom, and the camera software and picture quality you get on a sense rom is hands down a MILLION times better at teh moment than any CM or AOKP that i have tried.
Habarug said:
The one thing I want S-OFF for is repartitioning. I don't need 2 gb for apps, 1 would do, and I certainly DO NOT need 4 gb for system. That's just crazy. So after that I will have 3 gb more storage for nandroids, music, videos etc. That will be awesome
Click to expand...
Click to collapse
this is actually the ONLY reason i have seen to REALLY get s-off. I hadnt thought about repartitioning (but have on other phones) this phone, but man... that makes a LOT of sense!! lol
Jigswa said:
HTC don't really deserve any props. They give us a half assed unlock offering, when what people really want is s-off. When I had my One S, I could have really done with being able to partition and get some of the /data storage that I was never gonna use on to the /sdcard partition as I used up the measly amount of storage quite quickly.
Click to expand...
Click to collapse
Seriously?? Cmon man... the one s is a damn impressive phone (and this is coming from someone that is EXTREMELY picky about phones). What did you get since you dont have a one s now?

Nexus phones are definitely easy to unlock, but this isn't too far off. 3 fastboot commands vs 1 which equates to, what, 1 more minute of typing at worst?
The only thing that could have made this easier was if the Android USB drivers provided by Google supported this phone out of the box. The other drivers should have been easier to find too, but c'est la vie.
Still easier to unlock and root than the Vibrant, GS2 and even the Inspire I had before it.
The design of this phone is definitely top-notch, though its real test will be how it holds up six months from now. That is usually a problem point for HTC devices.

What I wish now is that HTC could make us able to use the ImageSense chip in AOSP roms as well

villainhalf said:
You've obviously never used a Motorola Triumph. That is the easiest phone to root and flash.
I hate that device.
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
I used to have a Moto Triumph (good riddance VM)
It wasnt too hard to root, but it had weird problems
Most definetly one of the most durable phones ive ever had though (I started with the Samsung Intercept, then Optimus V, then Triumph, now One S)

Habarug said:
What I wish now is that HTC could make us able to use the ImageSense chip in AOSP roms as well
Click to expand...
Click to collapse
Man, i REALLY wish this would happen. I am really loving the new Sense... HOWEVER, the camera is what keeps me from running any AOSP rom for an extended period of time. Its really bad in any AOSP rom i have tried.

All Atrix 2 Users on ICS Leak!

I'am putting this thread out as a warning to all Atrix 2 users. Currently it seems that there is something wrong with the fkz patch to 2.3.5 from ICS. About 5 or 6 people have encountered this and after trying to flash through RSD Lite they have HARD BRICKED their phones. According to Jim, there might be something in the ROM (similar to the HK leaks) that causes a hard brick during an RSD flash. So this means we currently have no way to get back to stock. Jim and the other devs are looking into it.
SO UNTIL FURTHER NOTICE I STRONGLY ADVICE, FOR NOW, NOT TO DO ANYTHING THAT COULD BRICK YOUR PHONE, AS YOUR PHONE WILL STAY BRICKED.

farshad525hou said:
I'am putting this thread out as a warning to all Atrix 2 users. Currently it seems that there is something wrong with the fkz patch to 2.3.5 from ICS. About 5 or 6 people have encountered this and after trying to flash through RSD Lite they have HARD BRICKED their phones. According to Jim, there might be something in the ROM (similar to the HK leaks) that causes a hard brick during an RSD flash. So this means we currently have no way to get back to stock. Jim and the other devs are looking into it.
SO UNTIL FURTHER NOTICE I STRONGLY ADVICE, FOR NOW, NOT TO DO ANYTHING THAT COULD BRICK YOUR PHONE, AS YOUR PHONE WILL STAY BRICKED.
Click to expand...
Click to collapse
You can get an advanced exchange by calling AT&T at the following number, if you have bricked using RSDlite:
1-800-801-1101
As usual, play dumb.

I don't plan I going back anyway...this leak blew everything out the water. I'll stick around on rooted stock till yall get this ball rolling. I have faith! Hahaha!
Sent From My DROID That DOES. Not Your APPLE That DIDN'T.

Good warning though. Thanks man!
Sent From My DROID That DOES. Not Your APPLE That DIDN'T.

DX2Trip said:
I don't plan I going back anyway...this leak blew everything out the water. I'll stick around on rooted stock till yall get this ball rolling. I have faith! Hahaha!
Sent From My DROID That DOES. Not Your APPLE That DIDN'T.
Click to expand...
Click to collapse
You also cant get more leaks since cheesecake is not working with ICS at this moment... and you are also off the OTA train as well, since this is a leak, and the real ICS OTA will most likely have some more checks for system apps signatures.

jimbridgman said:
You can get an advanced exchange by calling AT&T at the following number, if you have bricked using RSDlite:
1-800-801-1101
As usual, play dumb.
Click to expand...
Click to collapse
Will they figure out later what we did to the phone and decline the warranty? I am kind of worried.
I was thinking about walking in an att store for an exchange. Should I call instead?

qtqt710 said:
Will they figure out later what we did to the phone and decline the warranty? I am kind of worried.
I was thinking about walking in an att store for an exchange. Should I call instead?
Click to expand...
Click to collapse
as long as it is totally bricked, you should be ok. I guess you could just shock the hell out of the motherboard, but I wouldn't, even though it would be fun. Car battery anyone?

qtqt710 said:
Will they figure out later what we did to the phone and decline the warranty? I am kind of worried.
I was thinking about walking in an att store for an exchange. Should I call instead?
Click to expand...
Click to collapse
No they will not figure it out, and if they do you will already have your replacement. I have had 4 replacements now, due to my hacking this phone, and I have had an advenced replacement each time and never had an issue or been questioned once.
If you walk into a store, they will call this same number while you are there, and you will still have to be sent a replacement through 3 day delivery. Have a backup phone, even if you go grab a 10 dollar track phone and put your att sim in it.

Well this sucks. Thanks for the heads up on this. I was going to go back to 2.3.5 today because of the overclocking in this leak. The battery drain with it is a issue for me. I'll wait till a fix is available. Thanks again.
Sent from my MB865 using xda premium

jimbridgman said:
You also cant get more leaks since cheesecake is not working with ICS at this moment... and you are also off the OTA train as well, since this is a leak, and the real ICS OTA will most likely have some more checks for system apps signatures.
Click to expand...
Click to collapse
exactly, the problem is, once you go to the ics leak, you may never be able to get the real ics update. it may be possible, since you could keep this boot image and just flash the system, but there is no guarantee that would work and may even cause hard brick.
Keep in mind, this risk of hard brick is simply becaus moto decided to lock us down even more. they made an rsd flash not really possible. I think this same thing happend to the OG atrix people.
For some reason, Jim has had no problem getting back, but the rest of us have not been able to as of yet. we are looking into why that is and trying to find a way around it.
I do believe we will be able to find a way to get users now on ICS back to GB and back on the ota track, but even if not we may be able to at least make it so that they can unbrick from ics by flashing an ICS fxz like thing.
For those that have already bricked, there may not be a way back, but you can get an exchange.
For better or worse, one or two of our devs (not to be named here) hard bricked. while that means they will not be able to do much until they get replacements, they should be the best at figuring out how to get out of it if possible.
THE MOST IMPORTANT THING TO TAKE FROM THIS WHOLE PROCESS IS THAT YOU CANNOT GET MAD AT THE DEVS FOR NOT WARNING YOU. NONE OF US SAW THIS COMING. THERE IS AN INHERENT RISK IN MODDING YOUR PHONE, AND THIS IS EXACTLY IT.

Good warning! This will save a lot of ppl.

Thanks for the heads up, will wait for further info. Really enjoying this leak so far though.
Sent from my MB865 using Tapatalk 2

I bought my Atrix 2 in the USA and I live in Aruba, is there anything I can do to use warranty or something? Mine is not an AT&T phone.
I don't seem to find an MB865 motherboard online for sale.

Fowitho from
So about this "replacement" under warranty. What is the warranty on our phones? And if we do end up bricking, we just take it to ATT retail store? What if we bought it from ebay?

darkmixta said:
I bought my Atrix 2 in the USA and I live in Aruba, is there anything I can do to use warranty or something? Mine is not an AT&T phone.
I don't seem to find an MB865 motherboard online for sale.
Click to expand...
Click to collapse
call or chat with moto, see if they will sell you one directly, but that might be expensive

Would this hard brick have to do with the generation of mb865? Because it work for Jim right? Maybe it fails with some models. There must be a constant in the hardbrick, maybe the affected members can give us some background info of their phones.
Sent from my MB865 using xda premium

jfrank1485 said:
Would this hard brick have to do with the generation of mb865? Because it work for Jim right? Maybe it fails with some models. There must be a constant in the hardbrick, maybe the affected members can give us some background info of their phones.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
So, just curious... are we screwed when the official ICS update comes out? I mean, I installed this on my man's phone last night and it is working great but I'm sure the final one is gonna have tons of fixes for various things... Wouldn't we be able to install bootstrap and flash a new official custom ICS rom when they come out? I've already rooted his phone on ICS. I'm just worried he's gonna end up mad with me now. Lol!

I'm confused as to why this would work fine for some people and hard brick others? The Fxz worked totally fine for me!

Daiskei said:
So, just curious... are we screwed when the official ICS update comes out? I mean, I installed this on my man's phone last night and it is working great but I'm sure the final one is gonna have tons of fixes for various things... Wouldn't we be able to install bootstrap and flash a new official custom ICS rom when they come out? I've already rooted his phone on ICS. I'm just worried he's gonna end up mad with me now. Lol!
Click to expand...
Click to collapse
I think when the devs find a way to get back to 2.3.5, 2.36 then we'll be able to take the OTA. No cheesecake support and cannot check for system updates. I'm sure these devs will figure it out for us...They're smart.
Sent From My DROID That DOES. Not Your APPLE That DIDN'T.

big ach said:
I'm confused as to why this would work fine for some people and hard brick others? The Fxz worked totally fine for me!
Click to expand...
Click to collapse
I think they're talkin about goin back to 2.3.5 or 2.3.6 from the ICS leak. Many have bricked I guess in doing so. So beware lol. If you on the leak, stay put.
Sent From My DROID That DOES. Not Your APPLE That DIDN'T.

HTC one X: ? Hard bricked

I think my ATT htc one x may be hard bricked...
I was playing around with ROMs and lost track of time. The last recovery I had on there was clockworkmod (was going back and forth between it and twrp).
I was trying to install the new jellybean rom and it kept on giving me an "assert failed" error. At this point, I deleted the assert lines from the recovery script as advised by one of the posters, and ran the install again. Went through... rebooted and...
The phone is completely dead now. I think it may have discharged? I plugged it in to the wall socket and nothing... absolutely no lights, no screen..... Power+ vol down does not work either....
Please help me, is there any way to recover from this situation?

Wrong subforum.

You don't flash a Tegra One X ROM to your Qcom S4 One X did you? I assume the partition layouts are quite different, so this is bad.

Rusty! said:
You don't flash a Tegra One X ROM to your Qcom S4 One X did you? I assume the partition layouts are quite different, so this is bad.
Click to expand...
Click to collapse
Doesn't seem like a rare thing occurring. Either people are overseeing this or they are not really aware that for you can't flash a rom made for a tegra quad core device onto a dual krait.

I used this....
http://forum.xda-developers.com/showthread.php?t=1763240
Sheesh..... Is this meant for the tegra? I never thought I would do such a thing.... I was aware of the issue/hardware differences....
Is there any hope? Actually, in device manager it shows up as QHSUSB_DLOAD and I heard thats a bad sign?
If it cannot be fixed, does anyone have an estimate about how much HTC would charge to reflash/fix it?
My signficant other is as po'ed at me as can be... especially since I had really pushed for the upgrade.... man...

Yes it's meant for the Tegra One X, that's why it wouldn't install (that, and it's not in the AT&T One X section). You bypassed the check the install script does to make sure you're installing it on the right phone.
In short, yes you have buggered it, QHUSUSB_DLOAD is a state where you can write things to the phone, but whether anyone as done any research into it on the S4 One X I don't know.
As for getting it fixed, I have no idea on cost, however... if you convince HTC that you didn't do it yourself, it might be possible to get it done under warranty.
Edit: Did a bit of research and /system on the Tegra One X is is HBOOT on the S4 One X, that's why it's ruined your phone.

htc would just replace the motherboard and charge for that - loads of people have reported the cost its something like £169 to replace motherboard, which would of course un brick it.

Have you tried to keep it plugged in to a charger for an hour or so? My HOX was dead too but started to flash red light after an hour, moment after solid light and it booted
Sent from my HTC One X using Tapatalk 2

He doesn't have an HBOOT any more, there is nothing he can do.

This is why people should stop being stubborn and call that phone HTC One XL. These kinds of situations would happen sooner or later.
Sent from my HTC One X using xda app-developers app

I guess I did... I actually had come to that page via google and since, perhaps I was a bit sleepy, did not verify the source... should have....
Is there any fix at all? Like loading the drivers and reformatting it or something?
Im a bit confused about the motherboard replacement: since its a software issue, cant HTC fix it with a software update? Ill call them today and post the answer on this group as well, but knowing what I am dealing with may help in talking with them.
Thanks to everyone again

No fix that I'm aware of. You really need to be asking this in the XL section though. The phones really are quite different, we don't have the mode you're stuck in (not being Qualcomm based).

Rusty! said:
No fix that I'm aware of. You really need to be asking this in the XL section though. The phones really are quite different, we don't have the mode you're stuck in (not being Qualcomm based).
Click to expand...
Click to collapse
Thanks... Someone in that section has kindly agreed to see if he/she can help me... Keeping fingers crossed... doent feel right to tell att that my phone stopped working for a replacemenf...

Hate to say it but your phone is dead. It's not revivable ar this time and so your only option is jtag or warranty replacement because you overwrote the Hboot.
Sent from my Inspire 4G using xda app-developers app

Don't let morals get you on that one. Lie to them, if not for yourself than for me.
Sent from my HTC One X using xda app-developers app

RobertX1 said:
I used this....in device manager it shows up as QHSUSB_DLOAD ..
Click to expand...
Click to collapse
I am sorry, QHSUSB_DLOAD is dead end at every HTC phone. There is nothing you can do. I know what I am speaking, I hardbrick my last HTC in the same way.
But quarrantee will work, HTC cannot find out that you root it. They will replace you mainboard..as someone already mentioned

Not quite, there is a debricking method for the Sensation that can recover from it.
In most cases though, you're right.

Castellano2 said:
I am sorry, QHSUSB_DLOAD is dead end at every HTC phone. There is nothing you can do. I know what I am speaking, I hardbrick my last HTC in the same way.
But quarrantee will work, HTC cannot find out that you root it. They will replace you mainboard..as someone already mentioned
Click to expand...
Click to collapse
i already revived 2 sensation xe's from the qhusb_dload.
need linux though but it definetly is possible:-o

Please move this thread to the XL subforum
miniterror said:
i already revived 2 sensation xe's from the qhusb_dload.
need linux though but it definetly is possible:-o
Click to expand...
Click to collapse
Thanks... any hope for this being possible for the one XL? Also, could the mods please move this thread to the ATT section (sorry for posting it in the wrong section... but I really didnt know the importance of the difference.... wanna look at my phone? )
Thanks everyone. I think I might send the phone to HTC to get it repaired.... although the s***ty thing with that is that Ive heard they take that opportunity to replace the motherboard instead of just replacing the software, and hit me with a big bill rather than a reasonable/fair price....
So.... trying to be honest (by not returning the phone as defective to HTC) ensures that I get scammed by them... :victory:

Possible? Yes of course, that's the point of that mode as I understand it, with some other HTC phones you can hook it up to a RIFF Box and load it up.
Likely? Probably not, as it'll take people looking into it in depth to figure it out and as far as I can see, no-one has/is looked/is looking into it on the OXL.
It really does look like you'll need to send it to HTC, which (as you sound quite honest) will probably be expensive.

[Q]what causes hard bricking?

I just want to know cuz I'm a coward and I don't want to flash my own roms
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

cpu999 said:
I just want to know cuz I'm a coward and I don't want to flash my own roms
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
You are my hero of the day
Seriously though, a couple things can cause bricks. Battery pull during radio flash. Flashing a kernel with the wrong mount points. Formatting internal memory is a good way. Not like normal in recovery when you wipe, but in the way when you make your updater-script and aren't paying close attention to what your doing, lol. Yes, I have done this, haha.
There is plenty more ways for sure, but just pay close attention to what your doing and watch other devs around you and learn what they are doing and you'll be fine.

And how do you recover? USB isn't an option anymore and you need a JTAG or similar?

lap777 said:
And how do you recover? USB isn't an option anymore and you need a JTAG or similar?
Click to expand...
Click to collapse
Well normally there isn't a way to recover, hence "hard bricked". But, if there is a way there will be a recovery method posted somewhere in your device forums to recover bricks. Its a hard thing to come back from though.
Here is a pretty good example of a hard brick that a fix was eventually found for quite awhile after the device was released, went through eol, and people started leaving for newer devices. All credits go to the legend, Doug Piston of course. HTC Droid Incredible and its 5 vibe hard brick: http://forum.xda-developers.com/showthread.php?t=1110865
I heard jcase (teamandirc) say the GS3 is pretty easy to recover though, so I'm not sure you'd have much issue if you did brick. I'm not familiar with Samsung, I use HTC devices, so I'm not sure what method you boys would use.
I know for HTC devices, bricks most commonly occur when we accidentally mount something wrong, format something incorrectly, or a lot here lately, libs. Libs can cause issues to. The good thing though is we have the protection of a secure bootloader, s-on, which means if something harmful is flashed it won't hurt the phone since the bootloader is unlocked through HTC but still s-on. I think Samsung is about the same in this area. But I don't know. I'm just bored and felt like typing a bunch of text, lol

Good man.
Sent from my ZTE N881E using xda premium

[Q] Phone Bricked...I Think...

Ok so heres the short of it. I was attempting to root my phone with the Hasoon V1.1 Tool kit and needless to say, everything went wrong. Here's what happened. I did everything to unlock the bootloader. Got my token ID and all that stuff. Next, I loaded the twrp recovery. Cleared everything out of the phone, and went to load a rom. It kept telling me "Failed" when I tried applying the rom. It ended up getting into a boot loop and wouldn't do much. I got it to go back to the recovery when this started and still it wouldn't load any of the ATT Htc One x Roms. I made sure those were the ones I had. Now, at random throughout the process at some point last night, it wouldn't do anything. It has a blank screen. When I plug it in, the status light shows nothing. It was on the charger last night all night, and has not changed. No status light, no screen, nothing! I know you guys are going to ask for more information, but low and behold, like most people you smart guys deal with, I'm a noob. I rooted my google G1, and my HTC inspire without too much trouble, but this is just completely beyond me. As I was doing research I read about problems people were having with the blank screen of death. I'm just worried because I don't have insurance and I'm pretty much screwed without a phone. Does anyone have any input as to what I can do? I'm just beyond aggrivated not having a phone, and I don't have much money to be getting a new one. PLEASE HELP ME
-Mike

Which Rom exactly were you trying to install?
Sent from my HTC One X using xda app-developers app

Which ROM you flashed? Did you successfully root? Can you hold power + volume down to access twrp? Did you try to charge it? What does it do when plugged to computer?
Sent from my One X using xda premium

InflatedTitan said:
Which ROM you flashed? Did you successfully root? Can you hold power + volume down to access twrp? Did you try to charge it? What does it do when plugged to computer?
Sent from my One X using xda premium
Click to expand...
Click to collapse
This, as well as... Which phone do you have, the X or XL. The XL is specific in which rooting method you can use.
Sent from my HTC One XL using xda app-developers app

-Power and volume down do absolutely nothing
-Rom was Endeavoru Cyanogen Mod
-Kernel was Franco Kernel r21
-Plugged into computer, does nothing. No status light, nothing.
I am thinking it wasn't the software that did it. It was plugged into the usb port of my laptop the whole time, but may have died. I read online somewhere if you completely discharge the phone, you need a special charger to charge it. If I loaded the wrong kernel it could have gotten below it's "dead" percentage. Correct me if I'm wrong, but with Lithium Ion batteries, completely discharging them is not good for the battery. If it had nothing to tell it to stop, and the usb port on my laptop didn't keep up with the amount I was messing with it, it could just be completely dead. I don't know. I'm an idiot and I apologize about all the gapps I'm giving you guys with information. I'm doing the best I can, but bottom line is after it didn't work at first, I tried a few different recoveries with Hasoons tool kit, and a couple different roms but the roms never loaded. Always failed.

The phone I have I believe to be the One X, but I don't know the difference. When I booted my phone, it did the HTC Quietly Brilliant screen, then the ATT Rethink possible screen. What is the difference between the one X and one XL? I thought the XL was a larger version of the phone unfortunately, and now I'm seeing differently. It's the ATT phone, 16 gb internal storage, mini sim on the top, Dual Core processor not quad core.

With your battery being so low and possibly even dead when you tried to do anything with it, could have a problem. The other problem, if my memory is correct in what I was reading the Endeavoru cyanogen ROM is for the X only, international version. If yours is AT&T like you say, if the flash was performed correctly.... I hate to say this but you might have a nice $500 paperweight, for now. I would PM Abdolutelygrim and see what he thinks, unless he isn't already here.. his current project is unbricking Evita.
Sent from my HTC One XL using xda app-developers app

minimac21234 said:
The phone I have I believe to be the One X, but I don't know the difference. When I booted my phone, it did the HTC Quietly Brilliant screen, then the ATT Rethink possible screen. What is the difference between the one X and one XL? I thought the XL was a larger version of the phone unfortunately, and now I'm seeing differently. It's the ATT phone, 16 gb internal storage, mini sim on the top, Dual Core processor not quad core.
Click to expand...
Click to collapse
You have what we call an HTC one xl or AT&T one x. The phones look almost exactly the same but the internal components are completely different. (youre in the right forum)
Sent from my HTC One XL

I went through almost the same thing last night, with the exception of my battery dying. In the event that you are able to get the phone to charge, this guide helped me get my phone working again.
Good luck!

The phone was fully charged when I began, and I periodically connected and disconnected it when I was having my initial problems. I deleted my cache dalvic cache, etc everything after I saved all my important pictures and videos and files etc. so I just deleted everything to start over fresh. I don't know what the hell I did. I just figured this wouldnt be too hard since I did it with 2 of my own phones in the past, and a few friends phones also. I think my problem may have been with being ignorant and not knowing there were multiple versions of this phone that all look identical but aren't. Ohhhhhhhh boy. This is bad lol.

minimac21234 said:
I think my problem may have been with being ignorant and not knowing there were multiple versions of this phone that all look identical but aren't. Ohhhhhhhh boy. This is bad lol.
Click to expand...
Click to collapse
That is indeed your problem. The One X and One XL use a different partition layout, and international roms will attempt to overwrite the One XL boot partition. Hboot is wp in 2.20 but not in earlier versions. Even so, you can end up with corrupted firmware even if hboot is untouched. Numerous people have done it. Some devs are working on a way to fix this. Here's the thread, you'll need to get yourself in the queue or just see if you can get a replacement.
http://forum.xda-developers.com/showthread.php?t=1966850

Replacement isn't an option. I didn't get a chance to get insurance on it because I cracked the digitizer within the first 2 weeks of having the phone, and I opened it last night to see if something from when I cracked the digitizer came loose causing the phone to not boot. Thanks for the feedback so far guys. I'm not expecting miracles. I put myself into this mess, I'm just really hoping someone may be able to fix it soon. Not having a phone is really going to put a damper on my side work. Can't get phone calls from people on craigslist if I don't have a phone SH!T

Do you know what firmware your phone was on before you did this........it will be the determining factor if it's fixable atm
Sent from my HTC One XL using Tapatalk 2

I'm wondering if when I was trying to use CWM it screwed me up too. I read in a few peoples signatures that CWM also isn't compatable with the One XL. I feel like the biggest jackass. I'm the computer/cell phone/electronics guy in my area, and now I feel as if I should go into early retirement. I will stay open minded and hopeful that absolutelygrim and others come up with a solution, but bottom line, for all you guys that have made this process damn near idiot proof for people like me, I want to say thanks, and also apologize for all of us noobs that make something as simple as knowing what you are doing before you do it and following directions harder for the developers. It's awesome you guys do what you do in your spare time, only for people like myself to make it more of a hastle. Once again, thanks for trying to fix this guys. My bad.
18th... I was on 2.20. I read that there is a work around for 1.80(I think that's the firmware), but either way, yes I was on 2.20. I have been looking once a week for a new exploit to be able to root the one x, since there wasnt any options until about a week ago if you had 2.20. I bet that's why there are so many people screwing this up. They, like myself, are probably so eager to root it they don't take their time. I remember the first time I rooted my HTC inspire I took about 3-4 hours because I quadrouple checked what I was doing. And damn it am I kicking myself in the ass that I didn't do that this time around.

The problem was the endeavor Rom....but depending on what firmware you were on, 1.85 or 2.20 it can be fixed. If you were on 1.85 or below, it's fixable right now. If 2.20 then not atm.
Sent from my HTC One XL using Tapatalk 2

minimac21234 said:
I'm wondering if when I was trying to use CWM it screwed me up too. I read in a few peoples signatures that CWM also isn't compatable with the One XL.
Click to expand...
Click to collapse
The problem with CWM is that the version for the One XL is an unsupported port. So it's buggy, but the worst I've heard of it doing is corrupting people's sd card or occasionally borking installs, both of which are easily fixable.
The only time I've heard of CWM bricking One XL phones is when people use ROM Manager (which isn't supported for this phone, though GP will let you install it anyway) to install the endeavour version, which causes the same problem as flashing an endeavour rom.

Dang.. I thought it was just icecoldjelly that been banging up peoples OneX. I guess the new hboots aren't as noob-proof as we thought
Sent from my Liquidy Smooth, blazingly fast as f#@k OneXL using xda premium app.

InflatedTitan said:
Dang.. I thought it was just icecoldjelly that been banging up peoples OneX. I guess the new hboots aren't as noob-proof as we thought
Sent from my Liquidy Smooth, blazingly fast as f#@k OneXL using xda premium app.
Click to expand...
Click to collapse
It very well could be just Ice Cold Jelly. There is no guarantee something else I did last night bricked my phone. I know I attempted ICJ, and a few other stupid and ignorant attempts. But, I would guess it was from that.

minimac21234 said:
I know I attempted ICJ
Click to expand...
Click to collapse
There you are. That is surely the culprit.

iElvis said:
There you are. That is surely the culprit.
Click to expand...
Click to collapse
Lol... I knew I could get it out of him
Just jokin, hope everything works out OP... just keep following absolutelygrimm's unbricking thread and hope for a breakthrough
Sent from my Liquidy Smooth, blazingly fast as f#@k OneXL using xda premium app.