Related
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!!!
....i think? Running bamf ginger remix and the latest OTA radio not the leaks. I fixed my permissions and noticed my 4g kept going in and out. The phone got warm so i rebooted and got the splash screen, then it hung and rebooted two more times before booting normal. I literally freaked out for a second. Phone seems ok now. Should i be worried? What could cause this?
fixxxer2008 said:
....i think? Running bamf ginger remix and the latest OTA radio not the leaks. I fixed my permissions and noticed my 4g kept going in and out. The phone got warm so i rebooted and got the splash screen, then it hung and rebooted two more times before booting normal. I literally freaked out for a second. Phone seems ok now. Should i be worried? What could cause this?
Click to expand...
Click to collapse
Sounds like the radio to me. That's the thing that will suck up power the worst if it can't get it's crap together finding a signal, even to the point of heating that thing up. Mine starts cooking if I tether it and watch movies on it. Never had boot loops though, and I use the 1.70 radio for weeks.
im glad i have full insurance on this phone in case. so far, so good today. in case i do brick is there a way to set the phone back to stock before returning it?
fixxxer2008 said:
im glad i have full insurance on this phone in case. so far, so good today. in case i do brick is there a way to set the phone back to stock before returning it?
Click to expand...
Click to collapse
In that event, I say "Brick? What brick? It fell out of my pocket and sank to the bottom of a VERY deep lake." I've never had Asurion ask me for a phone back. The whole "My CRAZY ex stole it!" worked just fine.
loonatik78 said:
In that event, I say "Brick? What brick? It fell out of my pocket and sank to the bottom of a VERY deep lake." I've never had Asurion ask me for a phone back. The whole "My CRAZY ex stole it!" worked just fine.
Click to expand...
Click to collapse
yeah but there has to be a way to set it to stock in case right?
How do you "almost brick" a phone ? How does one know it was "almost" ?
fixxxer2008 said:
yeah but there has to be a way to set it to stock in case right?
Click to expand...
Click to collapse
I think if there was a way to set things back to stock, you wouldn't actually be bricked.
hallstevenson said:
How do you "almost brick" a phone ? How does one know it was "almost" ?
Click to expand...
Click to collapse
it started to endless reboot, that's what people say happened when they bricked.
loonatik78 said:
I think if there was a way to set things back to stock, you wouldn't actually be bricked.
Click to expand...
Click to collapse
if im correct i thought there was a way to do it. ill have to do some checking. if i had to bring it in, if they found out i was rooted it would void my warranty.
fixxxer2008 said:
if im correct i thought there was a way to do it. ill have to do some checking. if i had to bring it in, if they found out i was rooted it would void my warranty.
Click to expand...
Click to collapse
I don't really know what to describe the "brick situation" we were having back in the day with the first leaked gingerbread as. Technically, it's not REALLY a brick because many of them could be fixed. It was more of a boot-loop issue. That whole situation muddied the waters of what defines a brick, but before that I always understood a brick to be a completely useless device beyond any help. Whether it could be powered on to view the hboot S-on or S-off state, I don't know because thankfully I've never had that problem.
There's always the option of electrocuting it until it won't power on though. Take an electronic lighter, remover the piezo igniter, and use that to zap sensitive parts of it's guts until it never worked again. That's like a few thousand volts. Not much inside there will survive that for long. (Yes, I really do sit around thinking about how to destroying things in undetectable ways.)
it's funny because everytime i hear about someone getting insurance for their cell phone i think "lol.. sucker!" but broke 2 phones so far and had to "craigslist" like crazy to find replacements at decent prices.
fixxxer2008 said:
if im correct i thought there was a way to do it. ill have to do some checking. if i had to bring it in, if they found out i was rooted it would void my warranty.
Click to expand...
Click to collapse
When the boot loop of death thing happened people were still able to get into hboot. So from there you would just flash an RUU and get back to s-on. If it truly is the same issue people were having the phone will be s-on after the RUU, but it will still just bootloop. If you are using the patched hboot I don't know if you would be able go get back because I don't know if fastboot was functioning.
Sent from my HTC Thunderbolt
I think i just bricked my phone. I am trying to return to S-on and after following all the instructions in the main sticky, i wrote the SUPERCID back to tmobile, and put in the writesecuflag 3 command, and rebooted the bootloader. Now the phone will not turn on at all. Won't power on regular and cannot turn it on into the bootloader. When i plug the phone into the computer QHUSB-DLOAD comes up in the device manager as to what it is saying it is attatched as. Adb shows no devices and RUU's cannot find the device. Omg i really hope i didnt hose this phone.
Did you flash first the ruu that came with your phone?
Sent from my HTC Sensation Z710e using XDA App
and1kar said:
Did you flash first the ruu that came with your phone?
Sent from my HTC Sensation Z710e using XDA App
Click to expand...
Click to collapse
Nope i used the tmous 1.50.
I am pretty sure you forgot to run the RUU, and sadly yes I have to inform you that it is bricked :/
xsteven77x said:
I think i just bricked my phone. I am trying to return to S-on and after following all the instructions in the main sticky, i wrote the SUPERCID back to tmobile, and put in the writesecuflag 3 command, and rebooted the bootloader. Now the phone will not turn on at all. Won't power on regular and cannot turn it on into the bootloader. When i plug the phone into the computer QHUSB-DLOAD comes up in the device manager as to what it is saying it is attatched as. Adb shows no devices and RUU's cannot find the device. Omg i really hope i didnt hose this phone.
Click to expand...
Click to collapse
Sounds like you bricked it, yes :s
Thanks for the replies guys.
Since i got it from craigslist my only hope is paying htc to repair it i'm assuming?
It should still be covered by the original warranty right?
LooieENG said:
It should still be covered by the original warranty right?
Click to expand...
Click to collapse
Just got off the phone with HTC. It is still covered under their warranty. Hopefully since all my void stickers in good standing, I have no physical damage, was able to get the CID back to Tmous and the write secureflag3 went through, there will be no reason to deny it. Here is hoping! I think EXT4 recovery is still on there though. Hopefully it will be so bricked that they will have to reset it and reload the software to be able to do anything with it
Hope you manage to get it fixed!
A question, I have yet to root my XE, but is SUPERCID a must on a sim free phone if you want to flash roms?
the fact is that if it is so bricked that it won't turn on at all they won't check it further. many members achieved to get a new phone as replacement
Just make sure you tell HTC you are the original owner and didnt get it from craigslist.Also DO NOT UNDER ANY CIRCUMSTANCES Mention any hacking forums like XDA,or ROOT, Just claim that it said "an update was available" so you chose to update and the battery died.I've had free repairs under warranty by using that same advice, A friend of mine mentioned root on his nexus one and they charged him for repair even though it was a month old as he voided the warranty
bonesy said:
Just make sure you tell HTC you are the original owner and didnt get it from craigslist.Also DO NOT UNDER ANY CIRCUMSTANCES Mention any hacking forums like XDA,or ROOT, Just claim that it said "an update was available" so you chose to update and the battery died.I've had free repairs under warranty by using that same advice, A friend of mine mentioned root on his nexus one and they charged him for repair even though it was a month old as he voided the warranty
Click to expand...
Click to collapse
I definitely didnt mention xda or flashing roms or anything, and I told them i received it as an anniversary gift (even though i really did get it from craigslist). Told them i rebooted the phone and it just never came back on. Which really is what happened while leaving out a few details lol.
I wonder what would them HTC guys think if they are already among us
same thing happened to me the other day on my evo 3d...gonna send it in to htc as well...hope they won't know...what are the chances of them getting the phone to turn on??
xsteven77x said:
I think i just bricked my phone. I am trying to return to S-on and after following all the instructions in the main sticky, i wrote the SUPERCID back to tmobile, and put in the writesecuflag 3 command, and rebooted the bootloader. Now the phone will not turn on at all. Won't power on regular and cannot turn it on into the bootloader. When i plug the phone into the computer QHUSB-DLOAD comes up in the device manager as to what it is saying it is attatched as. Adb shows no devices and RUU's cannot find the device. Omg i really hope i didnt hose this phone.
Click to expand...
Click to collapse
poktangju said:
same thing happened to me the other day on my evo 3d...gonna send it in to htc as well...hope they won't know...what are the chances of them getting the phone to turn on??
Click to expand...
Click to collapse
From everything i read online it really seems hit or miss depending on the technician you get. More often than not they seem to let things slide even if it seems obvious that they should have been able to see it was rooted etc. Here is hoping . I'm gonna send it out tomorrow and will keep this thread updated with developments if anyone is interested in how it went. I have read some HORROR stories about people sending there phone to HTC and it become missing in action for MONTHS. I really pray to christ that does not happen to me.
O/T a little bit, but how come with just about any other "thing" in life a warranty is good and is tied to the object and not to the person. Even though i got this phone off of craigslist, why should that have ANYTHING to do with it. The phone is the phone and the warranty is the warranty regardless of whose possession it is in. I just don't think tmobile should be able to do that. Also i think it's BS that if you buy a brand new phone and it breaks 2 days later, they give you a refurb and not a new one. How do they get away with this ****!
i think im gonna take my chances as well...the person i talked to at htc did say that if the damages were caused by me then i would have a choice to pay them to fix if not i would have to pay $35 to get the phone back...so this could end up costing the shipping to send phone and the $35 to get the phone back.
xsteven77x said:
From everything i read online it really seems hit or miss depending on the technician you get. More often than not they seem to let things slide even if it seems obvious that they should have been able to see it was rooted etc. Here is hoping . I'm gonna send it out tomorrow and will keep this thread updated with developments if anyone is interested in how it went.
Click to expand...
Click to collapse
Just wondering how this has progressed. Did you send your phone to HTC? Did they say what the potential repair costs could be?
Well i sent it out on 12/21 and they received it on 12/28. On the tracking website, it says "In repair". From experience, if it is going to have any issues or gonna charge you any money, it says under review until you have spoke to them and made arrangements or paid them. One thing that is pissing me off good is that every day, the day it says it was received is changed. So everyday i have checked, it went from saying received on 12/28, to 12/29, to 12/30, and now 1/1. So i dont know if that is just the way the system works, or if they are trying to sheist me and take forever and a day like some of the horror stories i have read. Not really sure what their is to do but send a replacement since it is hard bricked and cannot be resuscitated even with professional tools from all the research i have done online. In the meantime, i bought a galaxy s 2 and am LOVING it, except for the lack of development in comparison to here in sensation land!
did you get your phone back?
xsteven77x said:
Well i sent it out on 12/21 and they received it on 12/28. On the tracking website, it says "In repair". From experience, if it is going to have any issues or gonna charge you any money, it says under review until you have spoke to them and made arrangements or paid them. One thing that is pissing me off good is that every day, the day it says it was received is changed. So everyday i have checked, it went from saying received on 12/28, to 12/29, to 12/30, and now 1/1. So i dont know if that is just the way the system works, or if they are trying to sheist me and take forever and a day like some of the horror stories i have read. Not really sure what their is to do but send a replacement since it is hard bricked and cannot be resuscitated even with professional tools from all the research i have done online. In the meantime, i bought a galaxy s 2 and am LOVING it, except for the lack of development in comparison to here in sensation land!
Click to expand...
Click to collapse
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.
I first unlocked my google pixel (Verizon) bootloader, i then went on to try to root it. This went on to go into a boot loop. Me being dumb, forgot that you can just flash the stock firmware. I locked the bootloader. Now im stuck, when i try to boot it gives me the "Your device is corrupt" screen and it goes to the white battery display. I try to reinstall stock firmware and it says i need an unlocked bootloader. In order for me to unlock the bootloader i need usb debugging enabled. I can't get into the phone to enable it so im at a stuck point... I really would appreciate some help. I have extended warranty if Verizon can do anything with that.
Unfortunately, the instructions were pretty clear to not relock the bootloader unless the phone was 100% stock. From what I've seen, you are stuck. Haven't heard anyone recovering from relocking the bootloader with a bad install.
You made the decision to void your warranty when you unlocked the bootloader, so Verizon owes you nothing (extended warranty or not). That being said, they may replace it if you "played dumb" and said it happened during an update, but that poses an ethical quandary. So it's up to you how to proceed.
thanks for the reply
stranula said:
Unfortunately, the instructions were pretty clear to not relock the bootloader unless the phone was 100% stock. From what I've seen, you are stuck. Haven't heard anyone recovering from relocking the bootloader with a bad install.
You made the decision to void your warranty when you unlocked the bootloader, so Verizon owes you nothing (extended warranty or not). That being said, they may replace it if you "played dumb" and said it happened during an update, but that poses an ethical quandary. So it's up to you how to proceed.
Click to expand...
Click to collapse
Thanks a ton, yeah gonna try that "playing dumb" tactic today, was thinking the same thing... lets hope it works.
This is why providers lock bootloaders. Passing the cost to them instead of owning up to your screw up. Im sorry you bricked your device but that cost should be on you not verizon.
Sent from my Pixel using Tapatalk
jbjancuski said:
Thanks a ton, yeah gonna try that "playing dumb" tactic today, was thinking the same thing... lets hope it works.
Click to expand...
Click to collapse
For your sake, I hope it works. But, as I said, this is ethically questionable (on a personal level) and wrong on a grander level. You took responsibility when you unlocked the bootloader. If you are fortunate and Verizon gives you a new one. Either leave it stock, or read more thoroughly before making changes to your phone.
maulich said:
This is why providers lock bootloaders. Passing the cost to them instead of owning up to your screw up. Im sorry you bricked your device but that cost should be on you not verizon.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Unfortunately, this is absolutely the case. When we make the decision to do things to our phones that operators don't want us doing, we are accepting responsibility for the phone, and if we brick it we should deal with that consequence. But of course, some people aren't really prepared for this reality, and want someone else to get them out of it.
Agreed.......i have had to pay the piper before for my screw ups. Even a brand new device of my wifes that i was trying to get twrp on. Phone was less than 6 hours old and rendered a paper weight. Expensive lessons are a part of life.........The sad thing is verizon will get a ton of these returned for this very thing, and it will only force them to lock down the bootloader even better hurting the individuals who want a little freedom for a better price.
Sent from my Pixel using Tapatalk