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 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!
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
Hey all,
I've been a long time lurker on these forums and I've noticed quite a few people upgrading to the Sensation. From what I can tell, there's a way to get a FREE Sensation by sending your mt4g to T-Mobile for repairs since HTC no longer makes the mt4g. Is this correct? I asked a T-mo customer service rep and she said it isn't true. Of course, she could have been told to tell customers that so we don't all suddenly break our phones and have a new more expensive phone given to us.
If this is true, how can I return a phone after I've rooted it? I've seen various guides on how to return to stock and put s-on back. Would this be enough to get passed the voided warranty issue of a rooted phone?
What if my mt4g is actually in 100% working condition? Is there a safe way to damage it just enough to warrant a replacement?
Thanks, all! Sorry if this was posted in the wrong area.
Becareful because sometimes they send you the Mytouch.. LG version
Yeah, I read about that too. I would tell them up front that I will not accept a downgrade but require a phone of equal or greater value. I'm used to crappy service from these big companies and have found that if you make a big deal out of something, they'll do anything they can to shut you up.
only a few lucky people have gotten the Sensation as a replacement... :/
it kinda depends on whether you get a good rep or not... if you get a bad one.. well good luck with that... lol
as far as bricking... i guess you could always flash a Radio or some system file not made for this device... but be careful with that
Thanks for the reply, S, but I never mentioned bricking in my post lol.
So it looks like the only two devices that are given as replacements are the Sensation and the LG mt4g, right?
Now to my final question; how do you purposely cause your phone to malfunction so T-mo will have to replace it while not voiding your warranty? My guess is to press one of the hardware keys hard enough so it gets stuck. Probably the track pad since I've read reports of people getting theirs stuck. Worst case scenario here is that your phone has no track pad, but who uses that on their mt4g anyway?
Novarox said:
Thanks for the reply, S, but I never mentioned bricking in my post lol.
So it looks like the only two devices that are given as replacements are the Sensation and the LG mt4g, right?
Now to my final question; how do you purposely cause your phone to malfunction so T-mo will have to replace it while not voiding your warranty? My guess is to press one of the hardware keys hard enough so it gets stuck. Probably the track pad since I've read reports of people getting theirs stuck. Worst case scenario here is that your phone has no track pad, but who uses that on their mt4g anyway?
Click to expand...
Click to collapse
Uuuh, that's what saranhai was referring to. Reread his post.
be careful, I think in your situation it would be best to report it lost. Personally, my wife lost her phone and they were going to send us an LG phone, but I said no way. It is the MT4G or a better phone. I also told them that my contract is up in a few months and will leave if i get an LG. They said they will call me back today.
estallings15 said:
Uuuh, that's what saranhai was referring to. Reread his post.
Click to expand...
Click to collapse
He suggested I brick my phone which would imply I rooted my phone which would in turn void my warranty.
oak25 said:
be careful, I think in your situation it would be best to report it lost. Personally, my wife lost her phone and they were going to send us an LG phone, but I said no way. It is the MT4G or a better phone. I also told them that my contract is up in a few months and will leave if i get an LG. They said they will call me back today.
Click to expand...
Click to collapse
Correct me if I'm wrong but don't you get charged a little over $100 if you report your phone as lost or stolen?
Novarox said:
He suggested I brick my phone which would imply I rooted my phone which would in turn void my warranty.
Correct me if I'm wrong but don't you get charged a little over $100 if you report your phone as lost or stolen?
Click to expand...
Click to collapse
Yes $130. Oh, if it is a malfunction you do not pay right?
Novarox said:
He suggested I brick my phone which would imply I rooted my phone which would in turn void my warranty.
Correct me if I'm wrong but don't you get charged a little over $100 if you report your phone as lost or stolen?
Click to expand...
Click to collapse
Flashing a PD15IMG.zip from another device doesn't require root access...
Plus I turned in a dead phone that was rooted. They never found out or if they did... they didn't care.
Sent from my Infernalized Glacier!
-Team Inferno
Lol. Assuming always gets me too.
Hypothetically, you could TRY getting, say, a radio from a different HTC device and renaming it PD15IMG.zip and placing it on the root of your sd card. Boot into bootloader and it will check for the file and ask if you want to flash it. Flashing the wrong radio will totally screw your phone over. No root needed. However, I can't condone insurance fraud. That's highly illegal
Id imagine they'd send you an HTC mytouch 4g seeing as it is still sold on there website so no use In destroying your phone unless you have a bad emmc/screen
Sent from my HTC Glacier using XDA App
Unless they're in a good mood or something they'll send a sidekick 4G (A pink one at that) and I've gone as far as demanding to speak to a supervisor to no avail and then I see 3-4 guys getting sensations, ugh. Hahah but yes flashing a radio doesn't require root neither does pulling the battery a few times while doing that.
Sent from my HTC Glacier using xda premium
This entire thread is an awful idea.
Snakecharmed said:
This entire thread is an awful idea.
Click to expand...
Click to collapse
You are correct, and this is the reason phones and plans cost so much! I'd the phone is fine then why duck it up and become a criminal because you want a new phone! I wish I knew your name and number so I could call and report you!
Sent from my HTC Glacier using xda premium
I agree with you man.
Honestly, i don't understand why you want a new phone in the first place, the MT4G is a great phone and probably performs as well as the sensation anyway...
And Nic, you're right, they offered my a sidekick 4g and then they got upset that i didn't want a downgrade lol....
I have the bad emmc but good screen (which makes it all better)
I would like to see a "good " screen, because I've owned 4 "bad" ones, & they have all been brilliant. In fact, I can't see it getting any better...
Sent from my HTC Mytouch 4G using Tapatalk
irrelephant said:
You are correct, and this is the reason phones and plans cost so much! I'd the phone is fine then why duck it up and become a criminal because you want a new phone! I wish I knew your name and number so I could call and report you!
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
Am i?
I've never done this, and I had the same view as you expressed here. But after reading of so many people thinking of doing this, and no one expressly trying to stop this, I figured why not join the bandwagon.
If you can't beat em, join em, especially if there's no opposition. Anyway, relax. This was mostly theoretical and I've decided to wait on the HTC One for my upgrade. Or maybe even something even better that may or may not spring up by then.
I doubt they'll send you a sensation...
A couple of months ago I got a replacement phone sent because the proximity sensor on my old mt4g would cause the screen to go black during a call and I would not be able to get it to turn back on unless I turned the phone off. So I sent off my old phone and got a replacement mt4g.
I'm pretty sure they still have them in their warehouses.
Novarox said:
Am i?
I've never done this, and I had the same view as you expressed here. But after reading of so many people thinking of doing this, and no one expressly trying to stop this, I figured why not join the bandwagon.
If you can't beat em, join em, especially if there's no opposition. Anyway, relax. This was mostly theoretical and I've decided to wait on the HTC One for my upgrade. Or maybe even something even better that may or may not spring up by then.
Click to expand...
Click to collapse
So because I live in an area where there are dope dealers I should sell dope too? I guess keeping good values when other dont is just too much for some people... I refuse to let myself be brought down to,that level. I find it more gratifying to work my ass off and save a little to get the thing I want/need, rather than lie cheat and steal! Its not a shot at you, but at all the people that have been doing it. As this make everything worse on all of us!
Sent from my HTC Glacier using xda premium
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.