Database Info

Sensation bricked.. I think anyway

My sensation went off last night and wont come back on, no charging light no screen etc...
the only thing is usb does kinda pick it up as QHSUSB_DLOAD with no drivers to install, any ideas?
edit: never mind i now know this is bricked and a jtag needs doing....

Help! Same problem
I have no power to the device. Tmobile sent me a new sensation but i would like to try and fix the old one before i send it back, only have 5 more days.
Its not the battery or the sd since they both work fine in new phone.
Windows reads the same thing when on usb. No drivers. No power No nothing????
Can anyone help please or am i done for?

anarchyuk said:
My sensation went off last night and wont come back on, no charging light no screen etc...
the only thing is usb does kinda pick it up as QHSUSB_DLOAD with no drivers to install, any ideas?
edit: never mind i now know this is bricked and a jtag needs doing....
Click to expand...
Click to collapse
Could you explain what you did to cause this? I really hope you were messing with things other than what most people have done, otherwise, this could be a real problem for the rest of us.
Matt

Yes i would also like toknow what You did please
Sent from my HTC Sensation 4G using XDA Premium App

mrg02d said:
Could you explain what you did to cause this? I really hope you were messing with things other than what most people have done, otherwise, this could be a real problem for the rest of us.
Matt
Click to expand...
Click to collapse
+1
10Char

If you did brick there is a thred in the dev's that can and will show you how to unbrick and you can shop and decide on witch Rom you won't to go with look at it this way you have the best of both worlds good luck
Sent from my HTC Sensation 4G using XDA App

Had an issue today similar to yours, unlocked the bootloader today and kept the stock rom. Tonight I started deleting the bloatware, mainly using root explorer, no issues really. Used titanium backup to "force remove by exploit" I think its called. Did that and phone went black, tried powering back on, pulled battery etc, nada.
Ended up plugging device to usb charger and booted into bootloader, rebooted from there and its fine.

I ran into this tonight. See this thread:
http://forum.xda-developers.com/showthread.php?t=1198585
Short story -- Clockwork Recovery is bugged and won't charge the phone. Your battery level is too low to power on, so you need to use another method to get some power into it.
I did this:
http://dl.dropbox.com/u/15034469/tmp/recovery_fail.jpg
And yeah it's a lame problem.

Ahh, so this is not really a bricked phone, but a case of CWM dead battery! Good to know, as its an "easy" fix then. I was afraid that the phone, simply S-off and perm rooted, had somehow crashed permanently.
Matt

Straight Bricked
For me its not the battery, when tmobile sent me a new sensation i used my old battery, sdcard and sim and the battery still had around a 75% charge. I cant boot from usb i cant do anything. Its completely dead.

As for what i did?
I had been flashing multiple roms and kernels for 2 weeks. Overclocking, undervloting bla bla. No issues a wipe and flash couldnt take care of. I think i did a wipe and flash of a new rom and thats it. Dead. Wish i could remember exactly what it was. I guess im gonna mail it back since i have a new one and probably get charged full retail if they see its s-off and root.

blackstarnino said:
I had been flashing multiple roms and kernels for 2 weeks. Overclocking, undervloting bla bla. No issues a wipe and flash couldnt take care of. I think i did a wipe and flash of a new rom and thats it. Dead. Wish i could remember exactly what it was. I guess im gonna mail it back since i have a new one and probably get charged full retail if they see its s-off and root.
Click to expand...
Click to collapse
Ahh..So it wasnt the silly CWM ordeal then. That sucks!
Try to pinpoint what you were doing right before this happened. Were you wiping something? (what were you wiping) Were you flashing a ROM? (What were to flashing)
Try to provide more details, as I am sure some of the devs here will be looking to jump all over it shortly.
EDIT: Were to making sure to check that the ROM you were flashing was meant for your version of the phone as well as the files not corrupted? I know it sounds silly, but its something to rule out.
Matt

happened to me too on two batteries. I believe that it is due to overclocking the cpu. because the battery stats are calibrated for a slower CPU speed, it drains it past the failsafe point to pure failure. CWM will recognize CPU for the given ROM. i flashed back to S-ON and regular RUU 1.29 and charging my batteries again for the correct CPU + battery stats. wish me best of luck

Wow, am i that stupid
Not positive but i think i figured out what i did. Something really stupid.
I think i flashed: [Desire] InsertCoin CM7/STOCK 1.1.0
So am i fully bricked?
Gotta put the phone in the mail tomorrow.
Do you think they will see that its s-off or if its (truly) bricked can they not?
Nino

blackstarnino said:
Not positive but i think i figured out what i did. Something really stupid.
I think i flashed: [Desire] InsertCoin CM7/STOCK 1.1.0
So am i fully bricked?
Gotta put the phone in the mail tomorrow.
Do you think they will see that its s-off or if its (truly) bricked can they not?
Nino
Click to expand...
Click to collapse
They'll know....

actually... having worked in a few cell phone repair / refurbish facilities... i can tell you that they won't even look. they just plug the phone up to their bench and it overides everything and does a fresh flash. from there they just replace plastics to make it look like a brand new phone. if they are unable to flash it at the bench, they replace internals. so relax... no one will know or care what you did to it. these places get thousands of phones a day. and each tech at the bench has a quota to get through.

Thanks for your feedback guys. Shipping it off now...
Still cant believe it. Still have my n1 from launch day and it took everything i could throw at it. Still kicking like a beast. **** my g1 is still running cm4 i think lol.

anarchyuk said:
My sensation went off last night and wont come back on, no charging light no screen etc...
the only thing is usb does kinda pick it up as QHSUSB_DLOAD with no drivers to install, any ideas?
edit: never mind i now know this is bricked and a jtag needs doing....
Click to expand...
Click to collapse
I'm in the same situation. This sucks. I tried to get back S-ON. Did you receive a new phone?

So you flashed a desire ROM.... Well no ****...
Sent from my Transformer TF101 using xda premium

Anyone Have Any Experience With HTC Warranty Department?

Hey Guys I have a question, Last night my One X suddenly powered off while browsing the internet now it won't turn on and no led lights come on when it's on the charger computer won't recognize it, It's just dead in the water left it on the charger overnight and still nothing. So my question is has anyone had any experience with HTC and their warranty with the one x? I can't go through at&t because not even 5 days ago I switched to straight talk after buying out of my contract with them so I don't have Their insurance anymore and I was in the middle of looking for insurance online through a 3rd party so I didn't have that either. I know HTC is "supposed" to have a 1 year warranty on the product but most people I see here get it replaced through at&t.

Have you held power button down for at least 10 seconds since talking off charger this morning by chance?
WR
Burnt off a Beast CleanRom-V @ 2.1

WarRaven said:
Have you held power button down for at least 10 seconds since talking off charger this morning by chance?
WR
Burnt off a Beast CleanRom-V @ 2.1
Click to expand...
Click to collapse
Yeah, Power Down For 10 Second's Holding volume down plus power to get into bootloader, Connecting to usb and holding down buttons tried all of them still nothing just dead.

efan0388 said:
Hey Guys I have a question, Last night my One X suddenly powered off while browsing the internet now it won't turn on and no led lights come on when it's on the charger computer won't recognize it, It's just dead in the water left it on the charger overnight and still nothing. So my question is has anyone had any experience with HTC and their warranty with the one x? I can't go through at&t because not even 5 days ago I switched to straight talk after buying out of my contract with them so I don't have Their insurance anymore and I was in the middle of looking for insurance online through a 3rd party so I didn't have that either. I know HTC is "supposed" to have a 1 year warranty on the product but most people I see here get it replaced through at&t.
Click to expand...
Click to collapse
You can call HTC and they will have you mail it away (to Texas I think if you are in the US). If they determine it is their fault, they will fix the phone. If they determine it is not their fault, you have to pay them like $50 for them to mail the phone back.

efan0388 said:
Yeah, Power Down For 10 Second's Holding volume down plus power to get into bootloader, Connecting to usb and holding down buttons tried all of them still nothing just dead.
Click to expand...
Click to collapse
You held jut the power button right?
Not with volume down.
If so, disregard an call HTC.
WR
Burnt off a Beast CleanRom-V @ 2.1

I would assume that HTC would replace your phone no problem, they may make you do some troubleshooting steps but it's worth it for a new phone.
Sent from my Speak and Spell

danny39 said:
I would assume that HTC would replace your phone no problem, they may make you do some troubleshooting steps but it's worth it for a new phone.
Sent from my Speak and Spell
Click to expand...
Click to collapse
Yeah, I can already tell this is gonna be a Pain in the ass HTC keeps telling me to contact at&t since it's a branded phone from them. At&t says since I bought out of my contract it's Htc I need to talk to. Round and round we go.

Make sure you have a back up phone. HTC service is very slow moving. Their phones are repaired by a third party and they have very little access to progress information. You're looking at 3 weeks minimum.
I went through hell with them when my one x gsm broke.
Don't let them tell you they don't have anything to do with the att one Xl...they sent me the one I have now after waiting for 2 months for them to repair my one x gsm
Sent from my One X using xda premium

nooomoto said:
Make sure you have a back up phone. HTC service is very slow moving. Their phones are repaired by a third party and they have very little access to progress information. You're looking at 3 weeks minimum.
I went through hell with them when my one x gsm broke.
Don't let them tell you they don't have anything to do with the att one Xl...they sent me the one I have now after waiting for 2 months for them to repair my one x gsm
Sent from my One X using xda premium
Click to expand...
Click to collapse
I'd be happy for them just to take the phone at this point. There telling me pretty much its at&t's problem and at&t is telling me it's HTC's problem. It has started to try install new devices when plugged into my computer now though. It's trying to install qhsub_dload mode driver and usb_input. So I dunno whats going on. I didn't flash anything and it was running perfect then just bam so Guess I'll just keep working on HTC.

qhsub_dload is called download mode, and its a real bad sign. It means everything is gone, including hboot. Its not easily recoverable, and you probably wouldn't be able to do so. And it might be a straight out hardware failure, anyway. If its not bootloader unlocked or anything, its not worth you messing around with anyway, since you can just get a repair or replacement by warranty.

redpoint73 said:
qhsub_dload is called download mode, and its a real bad sign. It means everything is gone, including hboot. Its not easily recoverable, and you probably wouldn't be able to do so. If its not bootloader unlocked or anything, its not worth you messing around with anyway, since you can just get a repair or replacement by warranty.
Click to expand...
Click to collapse
It is bootloader unlocked but if they can't even boot it up I doubt they would be able to tell? Just weird that it happened like I said I didn't flash anything it just shut down in the middle of internet browsing. So I don't know how everything got erased.

efan0388 said:
It is bootloader unlocked but if they can't even boot it up I doubt they would be able to tell? Just weird that it happened like I said I didn't flash anything it just shut down in the middle of internet browsing. So I don't know how everything got erased.
Click to expand...
Click to collapse
True, they can't tell on the phone that its BL unlocked, if it can't be powered on at all (even hboot). But unless you used the IMEI spoof BL unlock method, you had to submit your IMEI to HTC to get the unlock token. Now whether they actually keep a record of that, and will hold it against you, is another question.
From your description, it doesn't sound like anything you did. My gut feeling its a straight out hardware failure.

Used RUU, screen doesn't turn on

I used the jellybean RUU from HTC after relocking my bootloader, and now it won't "turn on." When I've got it plugged into the computer and I power it off and on, I can hear the device connect/disconnect sounds, but my screen does nothing. Any help appreciated.

I'm guessing you were SuperCID, and S-on? If so, sorry to say you are now bricked.
Should have read this, stickied to the top of General: http://forum.xda-developers.com/showthread.php?t=2181929

Wow. The level of suck here is amazing. Thanks. Nothing that can be done at all?

Jonathan_A said:
When I've got it plugged into the computer and I power it off and on, I can hear the device connect/disconnect sounds, but my screen does nothing.
Click to expand...
Click to collapse
Does the phone power on at all? Its not clear when you say "power it on" whether you are talking about the phone or the computer.
Any charge LED when the phone is plugged to USB or the wall charger?
Any message about QHSUSB_DLOAD drivers popup on the computer when you connect the phone by USB? If you get this, and no charge LED, you are bricked.

redpoint73 said:
Does the phone power on at all? Its not clear when you say "power it on" whether you are talking about the phone or the computer.
Any charge LED when the phone is plugged to USB or the wall charger?
Any message about QHSUSB_DLOAD drivers popup on the computer when you connect the phone by USB? If you get this, and no charge LED, you are bricked.
Click to expand...
Click to collapse
I meant the phone, when I power the phone on, I hear the device connect sound through the computer. No charge LED, but I do get the QHSUSB_DLOAD in device manager. So crap . Thanks for your help (not sarcasm). Level of stupidity/annoyance that I'm feeling right now is OVER NINE THOUSAND. Can't believe I missed a sticky. Thanks a million for the informative thread there though, I'll never use an RUU again, bet your bottom dollar.

Jonathan_A said:
I meant the phone, when I power the phone on, I hear the device connect sound through the computer. No charge LED, but I do get the QHSUSB_DLOAD in device manager. So crap . Thanks for your help (not sarcasm). Level of stupidity/annoyance that I'm feeling right now is OVER NINE THOUSAND. Can't believe I missed a sticky. Thanks a million for the informative thread there though, I'll never use an RUU again, bet your bottom dollar.
Click to expand...
Click to collapse
Some people have resurrected their phones from this using the JET tool. Failing that, it's fixable via jtag, though it wil set you back about $100.

Everyone makes stupid mistakes once in a while. But yeah, that really sucks. If you have access to a Linux computer, you might try the JET tool in Development, or check the unbricking thread in General. But I don't think anyone has been able to come back from this after the 3.18 RUU or OTA + SuperCID.
Beyond that, you can try to find a repair shop that will JTAG the phone. It will cost you, but better than buying a new phone.

iElvis said:
Some people have resurrected their phones from this using the JET tool. Failing that, it's fixable via jtag, though it wil set you back about $100.
Click to expand...
Click to collapse
Well, it's still under warranty, and I'm hoping that since the bootloader was relocked and the RUU technically succeeded, they'll just send me a new one or something. Though I'll take a whack at the JET thing if I can find my Linux live CD... Thanks a ton, I'm feeling pretty dumb here and you guys have been really helpful.

Jonathan_A said:
I'll never use an RUU again, bet your bottom dollar.
Click to expand...
Click to collapse
RUU is usually a safe thing to do (typically its a good tool for recovering from all sorts of issues). It really shouldn't cause a brick, and nobody is really sure why it does in this case. So really, its kind of an honest mistake. Its folks that OTA while rooted, etc. without doing any reading that I kinda wonder about.

redpoint73 said:
RUU is usually a safe thing to do (typically its a good tool for recovering from all sorts of issues). It really shouldn't cause a brick, and nobody is really sure why it does in this case. So really, its kind of an honest mistake. Its folks that OTA while rooted, etc. without doing any reading that I kinda wonder about.
Click to expand...
Click to collapse
Ah well, thanks for making me feel less stupid I guess I meant that I'll do some checking before I RUU again, heh.

Jonathan_A said:
Ah well, thanks for making me feel less stupid I guess I meant that I'll do some checking before I RUU again, heh.
Click to expand...
Click to collapse
Unfortunately HTC will be of no help as once you unlock the bootloader, even if you relock and the RUU bricks you, that's the end of your warranty.
The Carrier would usually be your best bet but they will most likely charge you to fix it
In this Case a Jtag will probably be your cheapest option. That isn't to say you shouldn't try HTC and your carrier first, just keep this in mind as it's most likely how things will go.
I'm speaking from experience of course. As I have bricked a one X the same way you did before it was known that super CID + S-ON + ruu = brick

exad said:
Unfortunately HTC will be of no help as once you unlock the bootloader, even if you relock and the RUU bricks you, that's the end of your warranty.
The Carrier would usually be your best bet but they will most likely charge you to fix it
In this Case a Jtag will probably be your cheapest option. That isn't to say you shouldn't try HTC and your carrier first, just keep this in mind as it's most likely how things will go.
I'm speaking from experience of course. As I have bricked a one X the same way you did before it was known that super CID + S-ON + ruu = brick
Click to expand...
Click to collapse
Well, we'll see. I'm sending it back tomorrow, will update on what happens. Praying that it gets a really lazy reviewer or something, haha.

Jonathan_A said:
Well, we'll see. I'm sending it back tomorrow, will update on what happens. Praying that it gets a really lazy reviewer or something, haha.
Click to expand...
Click to collapse
Good luck bud!
Sent from my HTC One X using xda app-developers app

Jonathan_A said:
Well, we'll see. I'm sending it back tomorrow, will update on what happens. Praying that it gets a really lazy reviewer or something, haha.
Click to expand...
Click to collapse
HTC will give you some grief. AT&T doesn't appear to care and from what I have seen has happily replaced lots of bricked phones without being concerned about relocking.

iElvis said:
HTC will give you some grief. AT&T doesn't appear to care and from what I have seen has happily replaced lots of bricked phones without being concerned about relocking.
Click to expand...
Click to collapse
Ooh, thanks. Good to know. They'll be my next try. You all have probably just saved me ~$300

Jonathan_A said:
I used the jellybean RUU from HTC after relocking my bootloader, and now it won't "turn on." When I've got it plugged into the computer and I power it off and on, I can hear the device connect/disconnect sounds, but my screen does nothing. Any help appreciated.
Click to expand...
Click to collapse
Happened to me too :c Has anyone had any luck using JET?

If the emmc partition table is still intact its feasible, but im pretty sure the ruu/ota kills it upon install. who knows why. seems to be a security "feature" since s-off seems to work fine.

Just called AT&T, they're sending me the replacement and then I send this one back in the box that the replacement came in and then the replacement is free. They said that they basically can't do anything with the dead one since it's dead, so I think all's well that ends well? Updates as events warrant, if need be. Thanks so much Redpoint73, iElvis, and exad.

I had a similar issue where my screen wouldn't turn on but it was still on and usable. I went to the AT&T store and got a replacement. Tell them you installed the AT&T update and then the screen stopped working. They probably won't be able to fix it but they'll give ya a new phone if you're under warranty. My phone was far from stock (rooted, bootloader unlocked, S-off, custom kernel and ROM), and they still gave me a new one. Make sure you go to an AT&T store though, I tried three different Best Buys and they were all noobs that had no idea what to do.
Edit: Didn't read post above so you can disregard this. But if you go to a store they can give you a new one on the spot instead of having to wait for one to be shipped to you.

Jonathan_A said:
Just called AT&T, they're sending me the replacement and then I send this one back in the box that the replacement came in and then the replacement is free. They said that they basically can't do anything with the dead one since it's dead, so I think all's well that ends well? Updates as events warrant, if need be. Thanks so much Redpoint73, iElvis, and exad.
Click to expand...
Click to collapse
Since the phone is bricked, there is really no way of them knowing (by checking the phone anyway) that you modded it. And as mentioned, AFAIK there has never been a reported case of AT&T denying warranty service due to the bootloader having been unlocked (and probably aren't even going to check). AT&T is much less strict then HTC, as its in AT&T self interest to keep you as a happy customer (paying that big old monthly bill), rather then fight over something like a single warranty exchange.
There have been some cases of the OTA randomly bricking devices that are fully stock (and probably possible with the RUU as well). Any time you mess with the hboot, if things get interrupted somehow, its possible to brick the phone. So for all AT&T knows, this is what happened in your case.
I'm normally not a big fan of making a warranty claim for your own negligence, and as a result of you modding the phone. But I suppose this is a bit of a gray area, since the RUU really shouldn't brick the phone solely due to SuperCID.
---------- Post added at 10:04 AM ---------- Previous post was at 09:58 AM ----------
exad said:
Unfortunately HTC will be of no help as once you unlock the bootloader, even if you relock and the RUU bricks you, that's the end of your warranty.
The Carrier would usually be your best bet but they will most likely charge you to fix it
In this Case a Jtag will probably be your cheapest option. That isn't to say you shouldn't try HTC and your carrier first, just keep this in mind as it's most likely how things will go.
I'm speaking from experience of course. As I have bricked a one X the same way you did before it was known that super CID + S-ON + ruu = brick
Click to expand...
Click to collapse
Did HTC actually deny your warranty service due to a record of you having unlocked the bootloader? Just curious, because it would be the first I have heard of that actually happening.
Yes, as the warning state when you unlock the bootloader, it voids the warranty (at least in theory). But in actual practice, whether they honor the warranty or not after BL unlock seems to be much more of a gray area.
Its true that the carrier will be more lenient than HTC. But I know there was some discussion on the "international" (quad core) One X forum, where HTC was actually honoring the warranty if the bootloader was unlocked. But they were actually denying warranty service if any custom ROM had ever been installed on the device. Even if the device was returned to the stock ROM before sending in. So apparently, they have some way of knowing a custom ROM was previously installed (even if uninstalled). If the phone was bricked, I wonder if they would still be able to check this?
Of course, how HTC honors the warranty may also vary from region to region.

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

[Q] AT&T One X bricked/warranty question

Hi, I'm wondering if anyone can help me with my situation. I have an AT&T One X that I rooted and flashed CM10.1, but was having problems with, so I relocked/unrooted the bootloader and restored the factory stock RUU using instructions from a youtube video to 2.20.
I then wanted to update to Jellybean using AT&T OTA software update, but that didn't work so I downloaded the RUU from the official HTC website. Everything was going fine until the end, when it said that the I was finished and the phone would restart. So I stupidly clicked finish and unplugged the phone from the computer, thinking that it would restart on its own. But the phone didn't restart, and I tried to hold the power button, no luck. I tried plugging the charger in, no red notification light came on. I tried holding the down volume button and power button, and that didn't work. I researched some online and it seems that my phone is bricked.
My question is will I be able to go to the ATT store or send it to HTC under warranty (it's been less than a year since I got this phone) for repair/replacement, or is the warranty void even after I relocked and unrooted the phone back to factory stock? If so, is sending it to JTAG it the best option? Thanks a lot.

nitwit2033 said:
Hi, I'm wondering if anyone can help me with my situation. I have an AT&T One X that I rooted and flashed CM10.1, but was having problems with, so I relocked/unrooted the bootloader and restored the factory stock RUU using instructions from a youtube video to 2.20.
I then wanted to update to Jellybean using AT&T OTA software update, but that didn't work so I downloaded the RUU from the official HTC website. Everything was going fine until the end, when it said that the I was finished and the phone would restart. So I stupidly clicked finish and unplugged the phone from the computer, thinking that it would restart on its own. But the phone didn't restart, and I tried to hold the power button, no luck. I tried plugging the charger in, no red notification light came on. I tried holding the down volume button and power button, and that didn't work. I researched some online and it seems that my phone is bricked.
My question is will I be able to go to the ATT store or send it to HTC under warranty (it's been less than a year since I got this phone) for repair/replacement, or is the warranty void even after I relocked and unrooted the phone back to factory stock? If so, is sending it to JTAG it the best option? Thanks a lot.
Click to expand...
Click to collapse
S-on and SuperCID = brick
Think of it this way if you can't power it on neither can they. It's not quite honest but att shouldn't give you a problem if it's under warranty
Sent from my HTC One XL using xda premium

If it's truly bricked they won't bee able to tell anyway. And from all reports, at&t don't even care if you messed with the phone. So you should take it in to get it replaced as your first option.
Sent from my Evita

Would it be worth it to try the unlimited.io solution for QHUSB-DLOAD mode, since that's what shows up when I plug the phone in?

nitwit2033 said:
Would it be worth it to try the unlimited.io solution for QHUSB-DLOAD mode, since that's what shows up when I plug the phone in?
Click to expand...
Click to collapse
Never tried it. Won't hurt though
Sent from my HTC One XL using xda premium

31ken31 said:
Never tried it. Won't hurt though
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
I tried it, didn't work. Gonna go to the ATT store tomorrow and hope they can fix/replace it under warranty.

nitwit2033 said:
I tried it, didn't work. Gonna go to the ATT store tomorrow and hope they can fix/replace it under warranty.
Click to expand...
Click to collapse
Just play stupid. And ask them if they can make it turn on. They will most likely give up quick and hand off a new one
Sent from my HTC One XL using xda premium

nitwit2033 said:
My question is will I be able to go to the ATT store or send it to HTC under warranty (it's been less than a year since I got this phone) for repair/replacement, or is the warranty void even after I relocked and unrooted the phone back to factory stock? If so, is sending it to JTAG it the best option? Thanks a lot.
Click to expand...
Click to collapse
The AT&T store won't help you, unless the phone is less than 30 days from purchase. After 30 days, you need to work through the AT&T warranty department, and send the phone in, unless you happen to have a AT&T device support center nearby.
http://www.att.com/esupport/article.jsp?sid=KB91429&cv=820#fbid=Vcnkfogij67
HTC is much more strict about denying warranty service than AT&T. AT&T doesn't care if the phone is modded, bootloader unlocked, even custom ROM. But in the state your phone is in, they can't tell anyway. They just want to keep you happy as a service customer, paying that montly bill. Recommend you sent to AT&T, not to HTC.
Also, you should have done more reading before running the RUU: http://forum.xda-developers.com/showthread.php?t=2181929

Thanks for the info guys. The ATT store sent me to a nearby device support center and they couldn't turn it on and so they replaced it under warranty! Thanks again for the help.

nitwit2033 said:
Thanks for the info guys. The ATT store sent me to a nearby device support center and they couldn't turn it on and so they replaced it under warranty! Thanks again for the help.
Click to expand...
Click to collapse
Out of curiosity... How long they try and get it to boot up?
Sent from my HTC One XL using xda premium