Database Info

Having Withdrawals Already!!!

Ok so today I mow my yard and I plug in my Thunderbolt in to the USB charger on my PC when I come inside my phone is bootlooping. So I think ok whatever I will flash one of the many backup's I made.
So I pull the battery and boot into the bootloader, then when I go into recovery after about 2 seconds the phone powers off and starts bootlooping again??? Ok that's a first for me and I have been flashing and rooting since launch day of the OG Droid, (ok, ok not since the first day but like a month later). So I pull the battery again this time for 30 minutes because I read someone else had something like this happen yesterday. When I put the battery back in same thing! Now I pull the battery for 4 hours...same outcome.
Now I'm thinking RUU time so I grab the stock RUU pull the SD card from my Thunderbolt pop it in my Incredible load the RUU renamed to PG05IMG.zip and put it back in the Thunderbolt. Load the bootloader and flash the RUU. Reboot after it's done and would you believe it...the same thing! the phone won't load past the splash screen before rebooting.
I forgot to mention before trying all this I tried using adb to reboot into recovery and I kept getting "error: device not found" and I know how to use adb.
It's only been about 9 hours since I've been able to use my 2.3.4 GingerBread with parts of 3.0 Sense Thunderbolt and I already having withdrawals how am I going to make the next 2 to 3 weeks while it's being repaired???
Ok end rant...

Go to verizon, swap it for a new one. Warranty case for sure.

bilbobrian said:
Go to verizon, swap it for a new one. Warranty case for sure.
Click to expand...
Click to collapse
Thanks, but I rooted it, therefore I have no warranty. I knew the chance I was taking when I rooted it so I'm paying for it to be repaired.

I'm loosing faith in the Thunderbolt. I really feel we are all just a bunch of beta testers.

bunklung said:
I'm loosing faith in the Thunderbolt. I really feel we are all just a bunch of beta testers.
Click to expand...
Click to collapse
Huh? Off topic and makes no sense.
//Tap'd on my TBolt while grounded\\

bp328i said:
Thanks, but I rooted it, therefore I have no warranty. I knew the chance I was taking when I rooted it so I'm paying for it to be repaired.
Click to expand...
Click to collapse
I understand your rooted but if it cant boot up then there is a problem. Just go to verizon and show them. Once they see it cant boot properly they will exchange it or overnight one to you.
I apologize if Im missing something..

bp328i said:
Thanks, but I rooted it, therefore I have no warranty. I knew the chance I was taking when I rooted it so I'm paying for it to be repaired.
Click to expand...
Click to collapse
You may get away with getting it swapped through warranty. But I can't promise you it won't come back at you. Someone may have a solution for you though. Wouldn't give up yet. Sorry I don't.
//Tap'd on my TBolt while grounded\\

chkmate said:
Huh? Off topic and makes no sense.
//Tap'd on my TBolt while grounded\\
Click to expand...
Click to collapse
*Shrug*
He has a problem, I do too. We both own Thunderbolts. Maybe I should have been more specific.
To each his own. The end.

bunklung said:
*Shrug*
He has a problem, I do too. We both own Thunderbolts. Maybe I should have been more specific.
To each his own. The end.
Click to expand...
Click to collapse
Well then relate your problem with his. Just saying "your losing faith in Thunderbolt" tells me nothing. Don't mean to sound like an a$$, just saying. When I read your first comment I got nothing from it.
That being said...I haven't been a Bolt owner for long, but it does seem like a strange issue. You would think flashing a radio or backup would resolve the issue. But hasn't.
//Tap'd on my TBolt while grounded\\

Definitely sounds like a Warranty Issue. I'd try to get it exchanged if no one can come up for a solution to the problem.

I had a G1 back in the day that had some odd problem and I was rooted, Tmo looked at it and wouldn't touch it. So, I called HTC. I told them that I purchased the phone off Craigslist so Tmo couldn't help me, and asked how the warranty works on their end. They said that since the production of the phone started less than a year ago, they knew it was still eligible for warranty even without a receipt. There would be a triage fee if it was found to be a non-warranty issue, and it was something like $40 including the shipping back. I acted dumb when they asked if it was rooted...asked them what that meant? LOL. Sent it in, they fixed it and sent it back to me, no charge. Fast too. I was very happy and that is why I have stuck with HTC since then. It may or may not work for you, but it was painless for me.

bp328i said:
Thanks, but I rooted it, therefore I have no warranty. I knew the chance I was taking when I rooted it so I'm paying for it to be repaired.
Click to expand...
Click to collapse
Such chivalry is rare in these days.
Applaud. Best of luck!
Sent from my ADR6400L using Tapatalk

bp328i said:
Thanks, but I rooted it, therefore I have no warranty. I knew the chance I was taking when I rooted it so I'm paying for it to be repaired.
Click to expand...
Click to collapse
They don't care. Take my word for it. If it never boots they won't care.

I'm actually having this exact same issue. Has anyone found a solution yet or is the only solution to have the phone replaced?

Wow. I thought for sure hbooting the unsigned stock RUU would fix this. How about hbooting a signed ruu? It wouldn't hurt at this point.
Also make sure when you renamed the pgimg05. Zip that there was nothing at the end of the extention. I've heard some people say that windows has been known not to show that full file extension correctly.

raider3bravo said:
Wow. I thought for sure hbooting the unsigned stock RUU would fix this. How about hbooting a signed ruu? It wouldn't hurt at this point.
Also make sure when you renamed the pgimg05. Zip that there was nothing at the end of the extention. I've heard some people say that windows has been known not to show that full file extension correctly.
Click to expand...
Click to collapse
I thought hbooting the stock RUU would fix it as well, and yep it was named correctly. It's funny because it would stay on the hboot screen as long as I let it with no issue what so ever but within 2 seconds of going into recovery it would reboot.
I went back to Best Buy today as that is where I bought it to see how much they would charge to ship it out to be fixed. The mobile manager remembered me because I was 1st on the pre-order list. (I'm sure we all remember the train wreck the Best Buy pre-orders became) So any way he really went out of his way to help me. He said he has had 3 other Thunderbolts brought in for the same issue. He was able to send my phone in under their Black Tie program.
I told him I rooted the phone and was willing to pay for the repairs but he said he was pretty sure that the other 3 phones were not rooted. He said that he knew FOR SURE that at least one of the phones was not rooted because the lady that owned it did not have any branches in her family tree, (his words not mine). Since he has seen it 3 times he was not charging me. He only asked that I had the stock hboot on the phone. I had already flashed that in my attempt to get it running.

I'm with cstrife, I managed to destroy my tab with a mix of flashing and charging via outlets in India. It bootlooped for a while then just kind of gave up and began to display a strange download screen when I plugged it in to charge. I brought it to VZW and played stupid, I told them I woke up and it had this weird screen... I had a brand new one at my door the next morning and haven't heard a word from them... It probably just costs more to check it out deep enough to find out its rooted than it does to just give you a refurbished one, gut swap yours, and then send to someone else as a refurbished one...
Sent from my SCH-I800 using XDA App

Had this happen to me and just pulled my SD card, rebooted and it was fine. Not saying it will work for u but give it a shot.
Sent from my ADR6400L using XDA App

bp328i said:
I thought hbooting the stock RUU would fix it as well, and yep it was named correctly. It's funny because it would stay on the hboot screen as long as I let it with no issue what so ever but within 2 seconds of going into recovery it would reboot.
I went back to Best Buy today as that is where I bought it to see how much they would charge to ship it out to be fixed. The mobile manager remembered me because I was 1st on the pre-order list. (I'm sure we all remember the train wreck the Best Buy pre-orders became) So any way he really went out of his way to help me. He said he has had 3 other Thunderbolts brought in for the same issue. He was able to send my phone in under their Black Tie program.
I told him I rooted the phone and was willing to pay for the repairs but he said he was pretty sure that the other 3 phones were not rooted. He said that he knew FOR SURE that at least one of the phones was not rooted because the lady that owned it did not have any branches in her family tree, (his words not mine). Since he has seen it 3 times he was not charging me. He only asked that I had the stock hboot on the phone. I had already flashed that in my attempt to get it running.
Click to expand...
Click to collapse
Honesty turned out to be the best policy in this case. Congrats.
Sent from my ADR6400L using Tapatalk

MrHawaii said:
Honesty turned out to be the best policy in this case. Congrats.
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
Thanks, now I just have to wait 2 to 3 weeks to get it back. What to do with all that time!!!

[Q] Opinions please!

I have sent my sensation back for repair after totally bricking it in the process of returning my device to s-on.
My phone was completely dead, no response from charging, no response from computer adb, fastboot just DEAD!
I tried to supercharge my battery to make sure the recovery was not to blame but no joy there either.
My question is, with my phone in this state, will htc repair be able to tell that i have voided my warranty?? I told them that this happened during an ota update
Any opinions or comments from those who have done the same would be appreciated.

bobsie41 said:
I have sent my sensation back for repair after totally bricking it in the process of returning my device to s-on.
My phone was completely dead, no response from charging, no response from computer adb, fastboot just DEAD!
I tried to supercharge my battery to make sure the recovery was not to blame but no joy there either.
My question is, with my phone in this state, will htc repair be able to tell that i have voided my warranty?? I told them that this happened during an ota update
Any opinions or comments from those who have done the same would be appreciated.
Click to expand...
Click to collapse
Hi,
Sorry to hear about your predicament.
Did you actually manage to get S-ON ?
If not ,then it will be obvious what you have done.
No point in lying about it .
Just come clean or they will think you are taking the p*$$

malybru said:
Hi,
Sorry to hear about your predicament.
Did you actually manage to get S-ON ?
If not ,then it will be obvious what you have done.
No point in lying about it .
Just come clean or they will think you are taking the p*$$
Click to expand...
Click to collapse
I bricked my phone in the final step of returning to s-on...fastboot reboot-bootloader.....ok.....no response from phone DEAD.
Since posting i have checked the tracker for my phone repair and it says that it has been shipped today with no mention of cost. Obviously i haven't recieved the device yet but it looks very promising.
After reading many nightmare stories regarding htc uk repair service, if the information that i have just seen on the tracker is true i.e. phone recieved on 22nd. - dispatched on 23rd., i think that is excellent service especially considering the nature of the fault.
I'll be more buoyant when the phone is in my hands though!

malybru said:
Hi,
Sorry to hear about your predicament.
Did you actually manage to get S-ON ?
If not ,then it will be obvious what you have done.
No point in lying about it .
Just come clean or they will think you are taking the p*$$
Click to expand...
Click to collapse
Yes, they will try to find every reason to make sure the repairs are not covered under warranty...if they dont, then you can say it was your Good Luck!!!

bobsie41 said:
I bricked my phone in the final step of returning to s-on...fastboot reboot-bootloader.....ok.....no response from phone DEAD.
Since posting i have checked the tracker for my phone repair and it says that it has been shipped today with no mention of cost. Obviously i haven't recieved the device yet but it looks very promising.
After reading many nightmare stories regarding htc uk repair service, if the information that i have just seen on the tracker is true i.e. phone recieved on 22nd. - dispatched on 23rd., i think that is excellent service especially considering the nature of the fault.
I'll be more buoyant when the phone is in my hands though!
Click to expand...
Click to collapse
Hi,
Hope all goes well.

Well, as I know, some people sent their sensation back to repair with ENG OFF and did not really got into any trouble with warranty problem.

Think about it...How would they know? You cant get the phone to boot up, so how would they? They will just reflash the phone through the original process or replace the board inside. They dont have the time and money to go looking for evidence of you voiding the warranty. Its cheaper for them to reflash the phone than to see what you did. Not sure how they do it, but I know they have a method that most of us cannot do. Wont cost them much, at all. Im sure its related to a jtag. They will hook up the board to a device that will reflash the software.
Matt

Just an update to the situation.
I recieved my phone back today fully repaired, new PCBA-mainboard etc. etc. un-branded, un-locked. Was told it would have the latest os installed but came with 2.33 but i've successfully upgraded it. Now to play (a lot more carefully this time!).
For those who totally brick there phone like i did, take heart from my escapade but, perhaps i was just lucky!

Purchasing a potentially bricked Sensation; Advice and Suggestions?

Hey guys. I have a chance to pick up a mint sensation locally for a cheap price. The seller is under the impression it is bricked. I've read through the threads for a while now but thought I would ask for some help/advice. The seller told me that he bricked the phone by trying to unroot it but has also said he was trying to "flash boot or something." He has made it clear that the phone will not turn on or show any signs of life. He has tried multiple batteries as well.
So, is there any way to ensure it is bricked? I had thought that maybe he messed up flashing a new rom.
If it is clearly bricked, what would be a good price to snag it for?
Would it be possible to buy it and contact HTC in regard to the warranty? What would this cost?
Thanks in advance,
PS; I have read about the inablility to charge after flashing CWM. I'm not sure if CWM was installed or not. I will ask that asap.

Sounds like an inappropriate file was flashed to hboot, in which case it's dead. Short of jtagging there is no way to fix it.

Thanks for the quick reply globatron. That sucks to hear that it probably is fried. Would the HTC warranty cover this type of repair?

MRpeabodyia said:
Thanks for the quick reply globatron. That sucks to hear that it probably is fried. Would the HTC warranty cover this type of repair?
Click to expand...
Click to collapse
No, they wouldnt as it was from user error.
Matt

Do you know for sure they wouldn't cover it? All morality aside it could be argued that it wasn't user error considering I'm not entirely sure what the seller did to it.

MRpeabodyia said:
Do you know for sure they wouldn't cover it? All morality aside it could be argued that it wasn't user error considering I'm not entirely sure what the seller did to it.
Click to expand...
Click to collapse
Well,morality aside you can always tell them that the OTA update bricked it.If you are a TMOUS customer you can try and contact T-mo first.They are usually easier to deal with than HTC.

NYCguy I read through your thread discussing your dealings with Tmous. I had thought about contacting them but they have been a huge pain for me lately. (Almost to the point of ending my contract). I shot HTC an email out of curiousity so I should hear back from them soon. I've had to replace a phone before via T-mobile and it was pretty smooth. I just don't want to do it all the time as this may look odd on their end.

NYCguy I read through your thread discussing your dealings with Tmous. I had thought about contacting them but they have been a huge pain for me lately. (Almost to the point of ending my contract). I shot HTC an email out of curiousity so I should hear back from them soon. I've had to replace a phone before via T-mobile and it was pretty smooth. I just don't want to do it all the time as this may look odd on their end.

Well I bought my "bricked" sensation. I spoke with the seller for a while and it seems he had rooted it, received notification of the OTA, and attempted to unroot it. He didn't give me specifics on the procedure he used but I'm going to read as much as I can, depending on when my monster child will let me, and attempt to fix this thing. I read about the battery tricks and will try those tonight. Any suggestions as this point guys?

Well after reading and tinkering with this thing for a while it seems I have the dreaded qhsusb brick. I already spoke with HTC and it is under warranty until November of 2013. My new question is, Will HTC be able to tell the device was ever rooted? A rom was never installed so it should be stock. Seems the seller made a mistake in trying to go from s-off to s-on. Just hoping I won't have to pay much to have a new one sent from the manufacturer.
Thanks

MRpeabodyia said:
Well after reading and tinkering with this thing for a while it seems I have the dreaded qhsusb brick. I already spoke with HTC and it is under warranty until November of 2013. My new question is, Will HTC be able to tell the device was ever rooted? A rom was never installed so it should be stock. Seems the seller made a mistake in trying to go from s-off to s-on. Just hoping I won't have to pay much to have a new one sent from the manufacturer.
Thanks
Click to expand...
Click to collapse
Well if it's a QHSUB brick that means the phone is truely DEAD.If you can't boot into bootloader,can't charge it and can't connect to a PC,then i don't see how could they tell if it was rooted or not.There is no way for them to tell.You just tell them you bricked it while trying to install the OTA update,or do as i did and contact T-mobile.
Good luck!

Thought I would update this thread for anyone who may stumble across it at a later date. I went ahead and sent my bricked phone into HTC. They repaired the phone and sent it back. I was suprised to see that they didn't send me a refurb.
I have to say that HTC were very easy to work with were quick in returning my phone.

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.

Warranty return after s-off and/or root

Has anyone ever been "caught" and denied a warranty return after s-off and\or root? You hear all of these horror stories of you warranty being void but I personally have never had a problem.
I rooted my original Incredible and got two warranty replacements in the first year. One was for a blown speaker and the other was because I bricked it. When I bricked it I called Verizon and played dumb and said 'I don't know what is going on with my phone but it won't boot up'. They asked me a few questions and then said something like 'wow, I have never seen that before we will send you a new one.'
On my Incredible 4G, I rooted and s-offed (via HTC DEV before they removed it from the list) and got a warranty replacement (I don't remember what the problem was that caused me to exchange it). In fact, when I got the replacement it was obviously s-on and no longer unlockable via HTC Dev so I called Verizon to complain (told them something about being a software developer so I needed a phone I could ROM and develop on) hoping they would give me a HTC One (M7). Of course they did not but my point is no one seems to care about s-off or root.
Each time I have done a warranty exchange I have done it via phone not in the store. They ship me a new phone next day and I send my old one back. I would find it hard to believe that they have someone sitting there opening returned phones, checking for root or s-off, comparing them to the call that originated the return and then following up. Instead, I am sure the process is more like: Get the returned phone, note the RMA and note on the account that the old phone was returned, check for physical damage, throw it in a pile with all of the other returned phones to be formatted, re-flashed, tested and sold as refurbished phones.
I exchanged my weaksauce rooted M8 to the store last Friday due to frequent reboots. The sales guy turned on the screen, set it down, and rang me up a new one. He didn't boot into HBoot to look for s-off, and didn't look for any root checker or rooting application.
My experience is that the 'you will void your warranty' line is a scare tactic and it doesn't worry me one bit. While I am sure s-off and rooting can cause physical harm to a phone (maybe by doing something like overclocking) but I do not believe that the big cell phone companies like Verizon have any process in place to catch this. They do thousands of returns a day and don't care to slow down their return exchange process to check for the 1 out of 1000 rooted\s-off phones they come through.
This is my opinion and experience I would be interested in yours.

dneiding said:
Has anyone ever been "caught" and denied a warranty return after s-off and\or root? You hear all of these horror stories of you warranty being void but I personally have never had a problem.
I rooted my original Incredible and got two warranty replacements in the first year. One was for a blown speaker and the other was because I bricked it. When I bricked it I called Verizon and played dumb and said 'I don't know what is going on with my phone but it won't boot up'. They asked me a few questions and then said something like 'wow, I have never seen that before we will send you a new one.'
I rooted and s-offed (via HTC DEV before they removed it from the list) and got a warranty replacement (I don't remember what the problem was that caused me to exchange it). In fact, when I got the replacement it was obviously s-on and no longer unlockable via HTC Dev so I called Verizon to complain (told them something about being a software developer so I needed a phone I could ROM and develop on) hoping they would give me a HTC One (M7). Of course they did not but my point is no one seems to care about s-off or root.
Each time I have done a warranty exchange I have done it via phone not in the store. They ship me a new phone next day and I send my old one back. I would find it hard to believe that they have someone sitting there opening returned phones, checking for root or s-off, comparing them to the call that originated the return and then following up. Instead, I am sure the process is more like: Get the returned phone, note the RMA and note on the account that the old phone was returned, check for physical damage, throw it in a pile with all of the other returned phones to be formatted, re-flashed, tested and sold as refurbished phones.
I exchanged my weaksauce rooted M8 to the store last Friday due to frequent reboots. The sales guy turned on the screen, set it down, and rang me up a new one. He didn't boot into HBoot to look for s-off, and didn't look for any root checker or rooting application.
My experience is that the 'you will void your warranty' line is a scare tactic and it doesn't worry me one bit. While I am sure s-off and rooting can cause physical harm to a phone (maybe by doing something like overclocking) but I do not believe that the big cell phone companies like Verizon have any process in place to catch this. They do thousands of returns a day and don't care to slow down their return exchange process to check for the 1 out of 1000 rooted\s-off phones they come through.
This is my opinion and experience I would be interested in yours.
Click to expand...
Click to collapse
There is always a risk, although I personally will send in phones S-OFF even, and never had an issue. (I don't suggest this)
From my understanding, they get so many devices to repair, really all they look at is for water damage and things of that nature.
It would take too long to go through every device they get returned for whatever reason to see if it has been rooted at on point.
I also am yet to know of anyone to get caught and having to pay for the device due to rooting.

I've destroyed one phone (older Samsung 4G) by accidentally installing inappropriate software. It was about 3 days old, bricked it completely. Even the service guys couldn't reflash it. The folks at the store really didn't check anything or ask any questions, They just threw it in the return barrel and gave me a new one. Wouldn't worry too much, unless you return frequently, they shouldn't give you a hard time. After all, what do they care?

This made me think of a question. With this phone being an all-in-one construction, how would they tell if it has water damage?

sitlet said:
This made me think of a question. With this phone being an all-in-one construction, how would they tell if it has water damage?
Click to expand...
Click to collapse
I'm guessing they're not too worried about water damage with these phones...

They do pay attention in the retail stores though. My account was once flagged for having a rooted phone, galaxy nexus, when I took it in for some issue, I don't remember why. Yes, first mistake was allowing them to have my phone, lesson learned. Luckily I know people who work for Verizon and they had to go in and remove the note which stated my phone was rooted and warrantee was voided.
Sent from my HTC6525LVW using xda app-developers app

I went in to return my M8 due to battery issues and the Verizon guy who had to call tech support stated that when they send the phones in if they've been rooted in the past that even if you unroot it and turn S-On they can tell that it's been rooted and that S was indeed On and turned Off. He stated they can tell how many times you do it and boom you get a $400 charge on your account for the price of the phone they gave you and you had a voided warranty.
As hard as that is to believe, I feel like there may be such a thing where they Devs can tell if the phone was rooted, when, and how many times... But i'm no Dev. Someone working for Verizon care to chime in?

kj13569 said:
I went in to return my M8 due to battery issues and the Verizon guy who had to call tech support stated that when they send the phones in if they've been rooted in the past that even if you unroot it and turn S-On they can tell that it's been rooted and that S was indeed On and turned Off. He stated they can tell how many times you do it and boom you get a $400 charge on your account for the price of the phone they gave you and you had a voided warranty.
As hard as that is to believe, I feel like there may be such a thing where they Devs can tell if the phone was rooted, when, and how many times... But i'm no Dev. Someone working for Verizon care to chime in?
Click to expand...
Click to collapse
Maybe they can tell but do they even look or care? My experience is that they don't care. In my case, three times, I have returned a s-off and rooted phone (not to the store, via mail). I didn't bother to try to go back to s-on or un-root. They wouldn't need black magic to tell my phones were tampered with - just turn it on. My point is they don't care and they don't look (at least when you deal with Verizon via phone).
I stand by my claim that it is a scare tactic and they don't even look.

dneiding said:
Maybe they can tell but do they even look or care? My experience is that they don't care. In my case, three times, I have returned a s-off and rooted phone (not to the store, via mail). I didn't bother to try to go back to s-on or un-root. They wouldn't need black magic to tell my phones were tampered with - just turn it on. My point is they don't care and they don't look (at least when you deal with Verizon via phone).
I stand by my claim that it is a scare tactic and they don't even look.
Click to expand...
Click to collapse
i tried to take a phone in recently for a warranty return. the sales guy at the corporate store takes my phone to the back to test it and comes back a few minutes later to tell me my phone was rooted and the warranty was void. he was nice enough to tell me his manager told him to flag my account, but he didn't. he just said to undo the process and bring it back in.

Abe21599 said:
i tried to take a phone in recently for a warranty return. the sales guy at the corporate store takes my phone to the back to test it and comes back a few minutes later to tell me my phone was rooted and the warranty was void. he was nice enough to tell me his manager told him to flag my account, but he didn't. he just said to undo the process and bring it back in.
Click to expand...
Click to collapse
That's why I say deal with 1-800 Verizon not a store. You get a replacement the next day so long as you can be without the replacement for a day that is the way to go.

Edited.

dneiding said:
That's why I say deal with 1-800 Verizon not a store. You get a replacement the next day so long as you can be without the replacement for a day that is the way to go.
Click to expand...
Click to collapse
i wish i would have known that before bothering going into the store. would have saved me an hour. good to know.

Yeah I never go to a store. Complain on the phone then have them ship me a new one. Swap and done.
Sent from my Nexus 7 using Tapatalk

blestsol said:
Yeah I never go to a store. Complain on the phone then have them ship me a new one. Swap and done.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I'm assuming you guys all have insurance then right? Otherwise why are your carriers to easily swapping you new phones?

rudyolph said:
I'm assuming you guys all have insurance then right? Otherwise why are your carriers to easily swapping you new phones?
Click to expand...
Click to collapse
Warranty claims they will easily swap. I called about a Rezound that would get incredibly hot while charging. They sent me a new phone that arrived the next day. I sent back the old phone with S-Off, rooted, and a custom rom installed. From what I've read all they check is that the phone will power on.

I'll find out soon. Enough just sent an M8 back to BIG RED Monday. I'll update when it shows received and there are no extra charges added to my account.

I have a replacement on the way myself. Hopefully we have no issues. The phone aesthetically is in perfect condition.

I claimed my warranty the other week from a cracked screen and I just flashed a modified hboot before sending it off so that it said locked and s-on

Upgrading my phone at Verizon took me hours to do. While the time passed I talked to the Verizon associate about how I've rooted every smart phone I've ever owned and he didn't seem to mind a bit that those were all their phones, and actually seemed quite intrigued about doing so himself. Anyway my microphone piece won't work during calls, so I'm going to replace mine through Verizon's warrantee claims phone number. I'll post with results.
Unlocked, s-off, rooted with modified hboot that shows status locked and s-on.

Just an update. All seems good no extra charges or calls asking WTF?? Just a message saying thanks for returning the phone and my next bill came. Which is normal.