Database Info

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] Has someone figured out how to Unbrick A2 using JTAG Method?

Hi,
My A2 was hard bricked 2 months ago during downgrading from ICS to GB. Since then its nothing but a expensive paper weight for me. I have seen people recovering their HTC and samsung phones using Jtag method I was hoping someone has figured that for A2 as well. I live in India so I was not able to claim warranty. Any help will be highly appreciated.
Thank you.

john1989 said:
Hi,
My A2 was hard bricked 2 months ago during downgrading from ICS to GB. Since then its nothing but a expensive paper weight for me. I have seen people recovering their HTC and samsung phones using Jtag method I was hoping someone has figured that for A2 as well. I live in India so I was not able to claim warranty. Any help will be highly appreciated.
Thank you.
Click to expand...
Click to collapse
I am pretty sure people have looked into this man, but to no avail.
I'm not sure, but I wonder if the jtag method is rough for us due to our locked boot loader.
HTC and Samsung's are all unlocked for the most part.
Sent from my SAMSUNG-SGH-I727 using xda premium

Fall of Enosis said:
I am pretty sure people have looked into this man, but to no avail.
I'm not sure, but I wonder if the jtag method is rough for us due to our locked boot loader.
HTC and Samsung's are all unlocked for the most part.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
But, My friend had an old atrix for a while and even after having a locked bootloader using schematics and Riff box he flashed the firmware and was able to use his phone after a Hardbrick.

john1989 said:
But, My friend had an old atrix for a while and even after having a locked bootloader using schematics and Riff box he flashed the firmware and was able to use his phone after a Hardbrick.
Click to expand...
Click to collapse
I'm not sure if this would work on our phone, but I'm not saying it couldn't either. I think what it boils down to, and someone correct me if I'm wrong, but nobody has actually gotten the JTag or Riff boxes to even make an attempt at this. Therefore, we don't actually have a definitive answer to this...
Sent from my SAMSUNG-SGH-I747 Anti-Motorola Ballistic Missile

Apex_Strider said:
I'm not sure if this would work on our phone, but I'm not saying it couldn't either. I think what it boils down to, and someone correct me if I'm wrong, but nobody has actually gotten the JTag or Riff boxes to even make an attempt at this. Therefore, we don't actually have a definitive answer to this...
Sent from my SAMSUNG-SGH-I747 Anti-Motorola Ballistic Missile
Click to expand...
Click to collapse
Yes, I agree to you, Its just that because of non popularity of Motorola phones very less hardware repairs are possible. If this be a samsung we might have thousand way to fix it. I know Jtag method little bit if someone provide me the Schematics and firmware then I will buy a riff box and flash it to my A2.

Well saw this video today : http://www.youtube.com/watch?v=4RL8pm_yRYs&feature=plcp
Is it relevant ? I mean i can see riff box and Jtag..can that be done for A2 also ?

john1989 said:
Yes, I agree to you, Its just that because of non popularity of Motorola phones very less hardware repairs are possible. If this be a samsung we might have thousand way to fix it. I know Jtag method little bit if someone provide me the Schematics and firmware then I will buy a riff box and flash it to my A2.
Click to expand...
Click to collapse
If you can come up with the JTAG and RIFF boxes, I'm hopeful you can enlist the help of your friend who's already done this type of thing. As for a schematic diagram for the Atrix 2, you may find something online, but not sure...
Sent from my SAMSUNG-SGH-I747 Anti-Motorola Ballistic Missile

Guys the issue is what was done with the issue in the last leak. It hit an efuse, so unless someone knows how to reset that efuse with a jtag, then great, but when I was at at&t looking into it with the mobile design team we were unable to get the jtag and riff to see the a2.
so.... there are challenges that moto has thrown us with the last bricks that we will have to get past before we can resurrect the a2s that were bricked.

jimbridgman said:
Guys the issue is what was done with the issue in the last leak. It hit an efuse, so unless someone knows how to reset that efuse with a jtag, then great, but when I was at at&t looking into it with the mobile design team we were unable to get the jtag and riff to see the a2.
so.... there are challenges that moto has thrown us with the last bricks that we will have to get past before we can resurrect the a2s that were bricked.
Click to expand...
Click to collapse
What are efuse? What are the chances of resetting it?

Apex_Strider said:
If you can come up with the JTAG and RIFF boxes, I'm hopeful you can enlist the help of your friend who's already done this type of thing. As for a schematic diagram for the Atrix 2, you may find something online, but not sure...
Sent from my SAMSUNG-SGH-I747 Anti-Motorola Ballistic Missile
Click to expand...
Click to collapse
I asked my friend who used JTAG method on his old Atrix he said we need to find out the test points where the wires from riff box have to be soldered and then we will need a firmware that we have to flash from our computer. Test points can be obtained from Schematics diagram of a PCB board.

I'm no expert but Jtag basically connects (solders) to the board giving direct access to the NAND allowing you to, in a sense, force upload your firmware/bootloaders etc. I believe every phone should have this as Motorola has to have a port somewhere to debug and refurb the devices. I'm not saying it will work by default to a basic rift box, how ever it should be possible. I'm sure this process will equal to many many dead devices and a lot of patience from the dev trying to find it.
Edit: I've never owned or disassembled a Atrix 2 my statement is my logical thought line assuming Motorola has any sense in them. Also OMAP SoC are probably the most open source chipset out there.

So basically, someone needs to jump into this head first. Heck I got nothing else to do... research time!
Sent from my SAMSUNG-SGH-I727 using xda premium

Fall of Enosis said:
So basically, someone needs to jump into this head first. Heck I got nothing else to do... research time!
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
The thing is you need to figure out how to reverse the efuse. I have no issues seeing our phone on the riff with jtag, if the the efuse is not blown. Once the ICS fxz fails happened I tested this at att corp, and we could no longer see the devices that I bricked with our old fxz method. we found the efuse that blew the circuit that brings power to the phone and the chipset, but we could not reverse it with jtag and riff.

Well shoot Jim, if you had no luck, this whole jtag thing is looking rather grim.
Thanks for looking into it though man.
Sent from my SAMSUNG-SGH-I727 using xda premium

My understanding of the matter is this: even if you manage to flash another firmware over the bootloader, you gain nothing, as there is a set of efuses required to be burned in to even allow the NS bootloader to run. Is this the case, or does it just prevent flashing the NS bootloader when the efuses are in their default state?

Hatrack said:
My understanding of the matter is this: even if you manage to flash another firmware over the bootloader, you gain nothing, as there is a set of efuses required to be burned in to even allow the NS bootloader to run. Is this the case, or does it just prevent flashing the NS bootloader when the efuses are in their default state?
Click to expand...
Click to collapse
I think I already answered this a few posts above. The efuses that are flipped basically render the phone completely useless and there is no power getting to the board or cpu anymore, only the white led is allowed power in this case. When this happens even jtag and riff box can not see the phone with the proper connections.

jimbridgman said:
I think I already answered this a few posts above. The efuses that are flipped basically render the phone completely useless and there is no power getting to the board or cpu anymore, only the white led is allowed power in this case. When this happens even jtag and riff box can not see the phone with the proper connections.
Click to expand...
Click to collapse
back in the day I used to "experiment" with DTV boxes. They were not ever meant to be flashed "manually." So, JTAG was the only way. There were two different ways depending on the box. One required power for the flash chip to come from the box, which had to be turned on in a "debug" mode. Others, you had to power the chip yourself and then flash it. So, I would think that even if efuse is blown you could still flash the chip with the proper schematic to locate the points. Problem is, you would have a properly flashed phone that still dont work because it can no longer power itself. The Jtag I used worked on xbox, dtv boxes, many things, JTAG is JTAG. If you had the right img JTAG would work, but with blown efuse it is a waste of time. anyone who is soft-bricked or stuck in FASTBOOT I think could benefit, but only them.

jimbridgman said:
I think I already answered this a few posts above. The efuses that are flipped basically render the phone completely useless and there is no power getting to the board or cpu anymore, only the white led is allowed power in this case. When this happens even jtag and riff box can not see the phone with the proper connections.
Click to expand...
Click to collapse
I didn't mean those efuses - you already told us that Moto's got some that render the phone useless. There are others that allow the NS bootloader to run though, no?

What are efuse ? can someone please explain me what it is?
I now understand that my A2 can never run again, but I only for my satisfaction I wanted to know that what is stopping from booting it up.
I hope you all can understand.

john1989 said:
What are efuse ? can someone please explain me what it is?
I now understand that my A2 can never run again, but I only for my satisfaction I wanted to know that what is stopping from booting it up.
I hope you all can understand.
Click to expand...
Click to collapse
I thought I knew, but motorola says Im wrong:
http://www.engadget.com/2010/07/16/motorola-responds-to-droid-x-bootloader-controversy-says-efuse/
Question is, are they lying, or would a jtag of a proper IMG result in reversing the efuse as they claim? Kinda makes me wonder if you send in a hardbricked phone, and then an hour later they're selling it as a refurbished.

[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] Apeared to have bricked my phone. Recommendations?

I have an ATT HTC X one I had been running a clean ROM. I searched for a Jelly Bean ROM I thought I correctly identified my phone but...
After installing slim rom I get nothing on power on. And I get nothing with the charger plugged in.
Sucks these devices have such similar names. I suppose things went so well last time I was somewhat more casual.
I am leaving it plugged in over night.
Currently on Linux but do have the Windows 7 boot disk I used to do the rooting.
Can someone point me to a description of possible solutions?
Clearly the take it back to ATT and say it just stopped working one is on the list.
I have seen the attempt to boot and power cycle while watching for auto detect devices. I certainly can put a mini linux on a thumb drive.
I suppose the goal is to somehow write something that can boot strap me back?
I am a Linux savvy person so I can use dd if needed. Just need someone to contact me to point me in the right direction.

xophere said:
I have an ATT HTC X one I had been running a clean ROM. I searched for a Jelly Bean ROM I thought I correctly identified my phone but...
After installing slim rom I get nothing on power on. And I get nothing with the charger plugged in.
Sucks these devices have such similar names. I suppose things went so well last time I was somewhat more casual.
I am leaving it plugged in over night.
Currently on Linux but do have the Windows 7 boot disk I used to do the rooting.
Can someone point me to a description of possible solutions?
Clearly the take it back to ATT and say it just stopped working one is on the list.
I have seen the attempt to boot and power cycle while watching for auto detect devices. I certainly can put a mini linux on a thumb drive.
I suppose the goal is to somehow write something that can boot strap me back?
I am a Linux savvy person so I can use dd if needed. Just need someone to contact me to point me in the right direction.
Click to expand...
Click to collapse
If you had the 1.14 hboot you are Sol. Check my signature
Sent from my One X using xda app-developers app

smh ....... so many of these topics ....

xophere said:
I have an ATT HTC X one I had been running a clean ROM. I searched for a Jelly Bean ROM I thought I correctly identified my phone but...
After installing slim rom I get nothing on power on. And I get nothing with the charger plugged in.
Sucks these devices have such similar names. I suppose things went so well last time I was somewhat more casual.
I am leaving it plugged in over night.
Currently on Linux but do have the Windows 7 boot disk I used to do the rooting.
Can someone point me to a description of possible solutions?
Clearly the take it back to ATT and say it just stopped working one is on the list.
I have seen the attempt to boot and power cycle while watching for auto detect devices. I certainly can put a mini linux on a thumb drive.
I suppose the goal is to somehow write something that can boot strap me back?
I am a Linux savvy person so I can use dd if needed. Just need someone to contact me to point me in the right direction.
Click to expand...
Click to collapse
Still happening...crazy...{banging head}

No one reads all the warnings we put up. Why do we bother?
Sent from my HTC One X using Tapatalk 2

You bricked, and now you're mad. I don't get it? If we put up giant flashing red warning all over this site, it still wouldn't do any good...
Before I get flamed and what not over calling you mad, take a look at the post in the unbrick evita thread.
Sent from my HTC One XL cellular device over clocked to 1.9Ghz

Unfortunately I've just done the same thing.. Got casual as this fellow previously stated.
So, not sure what to do with it now, any pointers?

voltarian said:
Unfortunately I've just done the same thing.. Got casual as this fellow previously stated.
So, not sure what to do with it now, any pointers?
Click to expand...
Click to collapse
What hboot were you on?....If you say 1.14 I'm sorry but you have a paperweight anything under is fixable

omario8484 said:
What hboot were you on?....If you say 1.14 I'm sorry but you have a paperweight anything under is fixable
Click to expand...
Click to collapse
I'm not sure, but probably. My friend had told me about this Ice Cold Jelly or something that I should get. For some reason I didn't even check that it was international. Though I was wondering more along the lines of warranty, could I possibly take it to an AT&T store and get a replacement?
Searched some forms relating to this and really wish I came here before making the attempt based off of all the warnings. Good excuses I can come up with.

voltarian said:
I'm not sure, but probably. My friend had told me about this Ice Cold Jelly or something that I should get. For some reason I didn't even check that it was international. Though I was wondering more along the lines of warranty, could I possibly take it to an AT&T store and get a replacement?
Searched some forms relating to this and really wish I came here before making the attempt based off of all the warnings. Good excuses I can come up with.
Click to expand...
Click to collapse
None. Honesty is what we promote on this site. Not lying because you were to lazy to read.
Sent from my HTC One XL cellular device over clocked to 1.9Ghz

[Q] Fu*%ked my phone after two years of modding =(

Well I've finally done it. Hard brinked my phone. wont turn on wont flash any notification lights at me. no response at all. Tried to get back to stock through RUUing, definitely did something wrong. because now the only thing that hints my phone has any life in it, is the small connection sound when hooked up to usb to my computer. Just the sound though. No actual picture of device connected in "My Computer", and nothing on the phone comes up.
Im hopping there is still hope out there but I think it's lost. *que in Star wars quote.
any ideas?

korext said:
Well I've finally done it. Hard brinked my phone. wont turn on wont flash any notification lights at me. no response at all. Tried to get back to stock through RUUing, definitely did something wrong. because now the only thing that hints my phone has any life in it, is the small connection sound when hooked up to usb to my computer. Just the sound though. No actual picture of device connected in "My Computer", and nothing on the phone comes up.
Im hopping there is still hope out there but I think it's lost. *que in Star wars quote.
any ideas?
Click to expand...
Click to collapse
I'v research a bit and havn't found anything too promising, so if there has been any updates on un-bricking phones in the last few months, it'd be great to know..

First I'm going to kindly ask that you change the title of this topic.
Second I'm going to ask what you did prior to the phone becoming unresponsive ie. What ruu?
Third some details about your phone as in is it s-off what hboot do you have.
XDA Moderator

Did you try to run the 3.18 Ruu with s-on and superCID? If you did, jtag or replacement are your options.
Sent from my evita

RollTribe said:
Did you try to run the 3.18 Ruu with s-on and superCID? If you did, jtag or replacement are your options.
Sent from my evita
Click to expand...
Click to collapse
i just made the same mistake the other day.. its being sent into repair right now. im just hoping they have no way to tell HOW the phone got bricked and my warranty isn't void.. here's the link to my thread maybe some helpful info for the OP http://forum.xda-developers.com/showthread.php?t=2393960
but as RollTribe said.. only way to fix it is JTAG or replace motherboard lol.