I was running cm7 on my phone, and was throwing on the audio fix to get better speaker volume, which sent the phone into a boot loop. I tried to put my phone into hboot (power+volume-) which it does not. It tries to boot every time. I've tried probably 50+ times and same result. I'm guessing it has to deal with the poor built buttons on this phone and the volume down just does not work. My question is despite the fact I'm rooted and running cm7, am I safe to say this is a hardware issue? I just don't want to send in my phone to Verizon and get billed for the fact the phones "tampered" with.
Should verizon replace your phone after you borked it? I think you already know the answer
xebryus said:
I was running cm7 on my phone, and was throwing on the audio fix to get better speaker volume, which sent the phone into a boot loop. I tried to put my phone into hboot (power+volume-) which it does not. It tries to boot every time. I've tried probably 50+ times and same result. I'm guessing it has to deal with the poor built buttons on this phone and the volume down just does not work. My question is despite the fact I'm rooted and running cm7, am I safe to say this is a hardware issue? I just don't want to send in my phone to Verizon and get billed for the fact the phones "tampered" with.
Click to expand...
Click to collapse
long of it, no they shouldn't. will they? who knows, depends on if you tell them the truth or not.
Should they? Technically no. Will they? Sure. They would be happy to.
but he didnt break it if the loop comes from a hardware defect,all he did was get it to fail sooner than later basically what happened to others,so technically yes they should,or can anyone prove the software killed the hardware.
sent from a screamin' bamfed out tbolt
satseaker said:
but he didnt break it if the loop comes from a hardware defect,all he did was get it to fail sooner than later basically what happened to others,so technically yes they should,or can anyone prove the software killed the hardware.
sent from a screamin' bamfed out tbolt
Click to expand...
Click to collapse
Honestly, it doesn't matter if anyone can prove the software did it or not. He voided his warranty by rooting. But they likely will replace his phone, driving up the costs for future phones.
You rooted your phone. Take it for what it is...a non-warrantied phone.
Touchy
I will start off by saying I don't have a solid answer but being as it is a hardware problem they "should" fix it. Will they? Probably not. They'll take one look, see it's rooted, and tell you that you broke it by tampering with it. All bets are off as soon as the phone is rooted...unless you can unroot and take it in I think you're in trouble but since the button is broken you can't do anything with it. Good luck and let us know what you were able to get done.
I see what you guys are saying from a moral standpoint. I'm just angry cause I know for a fact my buttons are not up to par to what they're supposed to be. I don't want to fraud the companies over something that is my fault, but in this case I'm almost positive it's related to the fact this phone was not built too well. I dunno, do "authorized retailers" handle claims with faulty hardware or just official Verizon wireless stores?
This is why you should have ADB installed and working on your computer. Hook up the phone via USB, get into ADB and reboot into recovery. There are a few threads out there for ADB you should be able to find them using Google, hopefully that will be able to help you.
If you can get into the boot loader with and then you might be able to save your phone.. Maybe, not clear take your as card out and import the rhi, they might work...
Sent from my ThunderBolt using XDA App
if you can prove that the failure was not caused by rooting, then they should fix it for you under warranty. but that is hard to prove.
xebryus said:
I see what you guys are saying from a moral standpoint. I'm just angry cause I know for a fact my buttons are not up to par to what they're supposed to be. I don't want to fraud the companies over something that is my fault, but in this case I'm almost positive it's related to the fact this phone was not built too well. I dunno, do "authorized retailers" handle claims with faulty hardware or just official Verizon wireless stores?[/QUOTE
Did you try BOTH volume buttons at the same time? This got me to bootloader.
Click to expand...
Click to collapse
Just say you tried to install the last update and your phone wont boot now. They won't know the difference.
dpham00 said:
if you can prove that the failure was not caused by rooting, then they should fix it for you under warranty. but that is hard to prove.
Click to expand...
Click to collapse
Caused by rooting or not, there is NO warranty once a phone is rooted. Has nothing to do with what caused the malfunction.
ADB reboot bootloader or recovery should work though, as long as he catches it with the right timing during the loop.
Sent from my ADR6400L using XDA App
Well update on the situation. I called Verizon telling them I can't turn on my because it "freezes" when it tries to boot up every time. He told me to try a hard reset (try to go into hboot) and I told him I tried that at least 30 times and it won't. I said I think there's something wrong with my buttons because they're not very responsive and stick really easily (which they do) and he said they're overnighting a phone to me. That was yesterday, its waiting for me at home. I'm gonna send my old phone back asap.
I'm wondering, if they have a way to find out I'm rooted, will they charge me for the phone? I don't think they'll be able to though because if I can't get into hboot, how will they? I tried adb into bootloader, but as many times as I tried, no devices were found.
you're probably aright since they might just get it and toss it in the "to be refurbed" bin. It costs a lot of money to test every return. Good luck and let us know how it turns out.
xebryus said:
I'm wondering, if they have a way to find out I'm rooted, will they charge me for the phone? I don't think they'll be able to though because if I can't get into hboot, how will they? I tried adb into bootloader, but as many times as I tried, no devices were found.
Click to expand...
Click to collapse
If they do find out, they will charge you. Don't know if they will, but be prepared for the worst.
Sent from my ThunderBolt using Tapatalk
Yes, they get broken down abd only really check for water/physical damage
Sent from the Swag ThunderBolt ADR6400L with some GingerLove (Gingeritis 1.0) using XDA Premium App
Must Watch Before Any Forum Post http://goo.gl/b4IJJ
xebryus said:
Well update on the situation. I called Verizon telling them I can't turn on my because it "freezes" when it tries to boot up every time. He told me to try a hard reset (try to go into hboot) and I told him I tried that at least 30 times and it won't. I said I think there's something wrong with my buttons because they're not very responsive and stick really easily (which they do) and he said they're overnighting a phone to me. That was yesterday, its waiting for me at home. I'm gonna send my old phone back asap.
I'm wondering, if they have a way to find out I'm rooted, will they charge me for the phone? I don't think they'll be able to though because if I can't get into hboot, how will they? I tried adb into bootloader, but as many times as I tried, no devices were found.
Click to expand...
Click to collapse
Congrats on getting a new phone I guess.
I have noticed Verizon has been VERY accomodating with these phones. One call is all that's needed to get a new phone. Im guess they're so generous because they devices have been so finnicky so far and they just want to keep people pleased for now.
I envision them cracking down hard sooner or later though. They're not stupid. They've already come down on tethering and such, so it probably wont be long until they get hardcore on replacements.
My son works for VZ...
and he takes your calls... and this is what he told me. Anything covered under insurance (Asurion), they really don't check/don't care about rooting. VZ, on the other hand, will look pretty extensively if it's covered under the warranty. They will look for rooting or anything else that would break warranty coverage.
Related
I just called Verizon and told them after updating I have been getting random reboots. The tech said its happening to certain phones and is sending a replacement, no questions asked. Im sure my phones not defective I agree with those that say its a radio issue. I even mentioned that to the tech and he said he doesn't think so. Kinda sucks I got to restore to stock, and reroot and what not. I'll be sure to let everyone know if the replacement has the same issues.
Update: Just so you know I've gotten two replacements, and it didn't help my situation. So no point in getting one unless you got a little cosmetic issue with your phone. Htc is working on a fix for these pesky reboots. It's in testing stages right now supposedly.
Sent from my Thunderbolt
It may be a pain to return to stock & root the new phone, but at least verizon is swapping your phone for free. It wouldn't surprise me if they didn't try to blame it on the owner & charge for the exchange
Yeah the tech was real cool about it. Free overnight fed ex and everything.
Do you have to send your current phone back to them, then, or what?
Interesting that they're doing this. I thought this was happening on all TBs, not just individual ones. Maybe I should call. Anybody else had this experience with the techs? Or did ajd88 just happen to catch a tech that had already put in his 2 weeks notice and didn't care.
I called this morning. Having a new one next-day shipped to me. My phone has become unusable.
My phone has rebooted maybe 3 times total since I installed the leaked radio when it first was leaked, you guys think I should try and get a replacement just to be on the safe side?
Sent from my ADR6400L using XDA App
While my phone isn't randonly rebooting it does loose 4G all the time, rarely goes into 3G and 1x seems to be the norm. I live in Chicago so I know it has a solid 4G signal. Wonder if it's worth the trouble of swapping out. But knowing my luck they will give me a refurbished phone...
sublimaze said:
It may be a pain to return to stock & root the new phone, but at least verizon is swapping your phone for free. It wouldn't surprise me if they didn't try to blame it on the owner & charge for the exchange
Click to expand...
Click to collapse
in my experience, verizon has always been really good at replacing phones. I had a droid since launch day before upgrading to my TB, and it had been replaced 2 times.
The first time the camera stopped focusing, the second time it just stopped turning on.
I walked in to a VZW store on a Wednesday, and I had fedex at my door delivering new phone on thursday afternoon. badass!
You know he funny thigh here is. It probably is happening on all thunderbolts or some people just arent ppaying attention and not realizing that this is happening. It even happens on my wife's fascinate. So ineradicable of sending back my non defective phone that random rebooted once in a while for a "refurbished" phone. Ill keep my new out of box one. Not one someone else has allready had. Just because of a software issue.
Well it seems like I get the short end of the stick with VZW on a daily basis. I called and explained it all to the rep and explained how this is a known issue and that there are plently of reputable community sites (like XDA) confirming this and there is rarely a common thread between two devices. Apparently, the rep I spoke to, said that this isn't a known issue.
Got told to factory reset and if it comes down to an exchange, I'd be getting a "certified like-new device" a.k.a. crappy refurb. Again, IF it comes down to that. Awesome. Now they want me to wait it out and see if it keeps acting up. Fun.
I asked the tech if i was gonna get a refurb, he said no. He better not be lying.
Of course theres a gb leak right after, probably with a new radio that fixes it lol.
ajd88 said:
I asked the tech if i was gonna get a refurb, he said no. He better not be lying.
Click to expand...
Click to collapse
You'll most likely get a "Certified Like-New" It's a refurb. But, a refurb with a working power button is better than what I have now so I'm going to give this a go.
ProTekk said:
Well it seems like I get the short end of the stick with VZW on a daily basis. I called and explained it all to the rep and explained how this is a known issue and that there are plently of reputable community sites (like XDA) confirming this and there is rarely a common thread between two devices. Apparently, the rep I spoke to, said that this isn't a known issue.
Got told to factory reset and if it comes down to an exchange, I'd be getting a "certified like-new device" a.k.a. crappy refurb. Again, IF it comes down to that. Awesome. Now they want me to wait it out and see if it keeps acting up. Fun.
Click to expand...
Click to collapse
I just got the same response. Tech support said not a known issue. They want me to see if I can make it happen again. I guess random reboot isn't telling. I know they have to go through their troubleshooting process and I'm not upset about that, but i can see where this is going. I won't get another reboot today which will tell them I don't have a problem. Alright, I'm off the soapbox.
Sent from my ADR6400L using XDA Premium App
ERIFNOMI said:
You'll most likely get a "Certified Like-New" It's a refurb. But, a refurb with a working power button is better than what I have now so I'm going to give this a go.
Click to expand...
Click to collapse
Yeah my power button is F'ed too. Whatever if they send me a phone thats in worse shape then the one i got ill just send it back rather than my old one.
Busphan said:
I just got the same response. Tech support said not a known issue. They want me to see if I can make it happen again. I guess random reboot isn't telling. I know they have to go through their troubleshooting process and I'm not upset about that, but i can see where this is going. I won't get another reboot today which will tell them I don't have a problem. Alright, I'm off the soapbox.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
The guy i spoke to asked if I did a factory restore, I lied told him yes. So there was no troubleshooting. I told him its all over google, he put me on hold came back and said he looked on google and confirmed with me he sees that some people are having problems. After that he told me he was confident a new device would solve my problems and thats it. I guess i might have just got lucky.
It is possible that physical defects in the phones are contributing to the issue. Something like a bad run of filter components could cause the radio to operate ever so slightly out of spec, but still within QA tolerances. Then, if they then tweaked the radio parameters a bunch in the update, it could have pushed the performance requirements of the RF hardware closer to the device tolerances - suddenly revealing a whole bunch of bad components they did not see previously.
I got my new phone today and no reboots and my screen is a lot nicer and brighter. I'm happy
Sent from my ADR6400L using XDA Premium App
Can someone explain the nature of the reboots that they are experiencing? I had a reboot on Friday but it was much more then just a reboot, after the phone was finishing powering back up I had no ability to call out as if there was no service. I tried numerous battery pulls and even had Verizon do a reset on there end, nothing helped yet I was still able to receive and send data. Finally after about an hour my service was back. Then the same thing happened again yesterday, I went through the same processes with no success yet. I have tried all the different radio choices and nothing is working, does anyone have any suggestions?
Thanks!!!
Also I am rooted and using the stock rom
Couple different things I'd like to point out. Most vzw employees at the sales level will replace your phone if they actually see it reboot on its own. Some, though, chalk it up to being just a part of the device. I, myself, am a vzw employee and would most definitely exchange your device if its rebooting. However, rooting your phone voids the manufacturers warranty, so you better have insurance. Also, certified like news are not refurbished phones. They are phones that are brought back within the 14-day return policy because the customer either didn't like it or didn't understand how to use it. They're cleared out, tested, and repackaged as CLNRs. Certified pre-owned are, in fact, refurbished. Just thought I'd clear that up.
Sent from my HTC RootedBolt running CM-7.0.
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 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
Hi, my headphone jack has always been pick about having things plugged in just right, usually the slightest bit of ling screws it up. Finally today, it just started giving serious static in right side. when music or any sound starts it goes away, but the volume is very low on that side. It only does it when there is power (battery is in), so I think it is a bad connection in there. I have some questions regarding this.
1. How horrible is the Motorola service? they say 5-7 days, but is that really the case (In the U.S.). My warranty is still good, I'll just flash back to stock.
2. will opening the phone up void my warranty? I am somewhat experienced with electronics, so I could probably fix it, but I don't wantt to void the warranty in case it doesn't work.
3. I also have a stuck pixel on my screen that has been there since I got the phone (New). Will they fix that as well even though I can only select one problem on the application form? Should I mention it as well so that they might fix it?
Thank you,
-lkrasner
P.S. Unfortunately this means that I might be unable to do much for a while when I send my phone away. I hope you guys get ICS without me, and I will be waiting to try it out myself.
lkrasner said:
Hi, my headphone jack has always been pick about having things plugged in just right, usually the slightest bit of ling screws it up. Finally today, it just started giving serious static in right side. when music or any sound starts it goes away, but the volume is very low on that side. It only does it when there is power (battery is in), so I think it is a bad connection in there. I have some questions regarding this.
1. How horrible is the Motorola service? they say 5-7 days, but is that really the case (In the U.S.). My warranty is still good, I'll just flash back to stock.
2. will opening the phone up void my warranty? I am somewhat experienced with electronics, so I could probably fix it, but I don't wantt to void the warranty in case it doesn't work.
3. I also have a stuck pixel on my screen that has been there since I got the phone (New). Will they fix that as well even though I can only select one problem on the application form? Should I mention it as well so that they might fix it?
Thank you,
-lkrasner
P.S. Unfortunately this means that I might be unable to do much for a while when I send my phone away. I hope you guys get ICS without me, and I will be waiting to try it out myself.
Click to expand...
Click to collapse
Just do a mis-flash or delete the system partition and take it into a store and tell/show them it does not boot, that you picked it up off the charger and it was like that, and you need a replacement. They will send you a replacement and you have 30 days to return your "broken" phone. I have done this 4 times with my A2s.
jimbridgman said:
Just do a mis-flash or delete the system partition and take it into a store and tell/show them it does not boot, that you picked it up off the charger and it was like that, and you need a replacement. They will send you a replacement and you have 30 days to return your "broken" phone. I have done this 4 times with my A2s.
Click to expand...
Click to collapse
But my AT&T warranty is up?!?! will it still work? I still have my 1 year moto warranty.
Edit: If this does work I owe you something huge, plus I would get my screen problem fixed
EDIT 2: would I be better off just deleting something that would just stop if from booting past the boot logo (big M) so it wouldn't be so obvious that I just killed it with is basically sayins so on the fastboot screen. If so what could I delete that wouldn't prove I had rooted, probably nothing now that I say that.
lkrasner said:
But my AT&T warranty is up?!?! will it still work? I still have my 1 year moto warranty.
Click to expand...
Click to collapse
That is the Moto warranty, AT&T will just help you "file" it since it is done through them anyhow.
Just don't call moto yourself.
jimbridgman said:
That is the Moto warranty, AT&T will just help you "file" it since it is done through them anyhow.
Just don't call moto yourself.
Click to expand...
Click to collapse
sweet, I will try that, what should I do to brick just erase system with fastboot? isn't that really obvious? or are all the employees just stupid. Obviously I need to do something recoverable so that i can get it back if it doesn't work.
lkrasner said:
sweet, I will try that, what should I do to brick just erase system with fastboot? isn't that really obvious? or are all the employees just stupid. Obviously I need to do something recoverable so that i can get it back if it doesn't work.
Click to expand...
Click to collapse
Do anything that will make it either boot loop or stick on the dual core/moto boot screen. Whacking system/boot should do that, and you can still flash it back to stock before you send it back if you really want to.... they are just going to fully refurb it and re-sell it...
The secret is to act dumb, pretend like you know nothing bout flashing and this site... just act like it just went nuts and started this, and it will not boot.
Ask for the advanced replacement.
jimbridgman said:
Do anything that will make it either boot loop or stick on the dual core/moto boot screen. Whacking system/boot should do that, and you can still flash it back to stock before you send it back if you really want to.... they are just going to fully refurb it and re-sell it...
Click to expand...
Click to collapse
OK, and they will not be able to see root then, and if they flash it back to stock it will no longer be rooted, so I should be fine. I opened a service request with Moto earlier, do you think that will be a problem? Should I wait until it expires so they don't get suspicious that I bricked it on purpose.
lkrasner said:
OK, and they will not be able to see root then, and if they flash it back to stock it will no longer be rooted, so I should be fine. I opened a service request with Moto earlier, do you think that will be a problem? Should I wait until it expires so they don't get suspicious that I bricked it on purpose.
Click to expand...
Click to collapse
if it is borked when you take it to the store they can't see that it is rooted cause it won't boot... all they are going to do it call their 1-800 number and help you file a support request... then the person the phone will let you know of the "requirements" and ask if the phone has any visible water damage, yadda yadda...
Then they will send you a new phone and you should get it in 3 or so days and you are supposed to send the old one back in the SAME box... so you will already have flashed the fxz and been using the phone the whole time you waited for the new one to show up... just don't forget to send it back... I did and waited until 25 days later, and I was bugged mercillessly by att...
Just make sure you factory wipe and take out your sim and SDcard, and battery door... they do not send anything but the core of the phone, no batt or batt door or anything.
lkrasner said:
OK, and they will not be able to see root then, and if they flash it back to stock it will no longer be rooted, so I should be fine. I opened a service request with Moto earlier, do you think that will be a problem? Should I wait until it expires so they don't get suspicious that I bricked it on purpose.
Click to expand...
Click to collapse
@jim on playing dumb,hilarious ..i do that when i upgrade my phone.im such an ass when i upgraded to a2 from xperia x10 that i didnt even bother restoring it to stock, i left cm7 on it,custom bootlogo ,said "free xperia team" on boot.i just pretended i didnt know what happend. it was so enjoyable.
service rep - "it appears to be rooted"
My response - "What do you mean rooted? It has roots like a plant?".
@krasner
You worry to much,they cant prove anything.just brick it and youll be fine.u could even play dumb as u crack a smile while doing so and they still really cant do anything to prove u did it and have to exchange it.
Sent from my MB865 using xda premium
worked beautifully! I deleted build.prop and default.prop, so it just went to a black screen after the moto logo. when the guy called the warranty center he said it was "extremely defective and clearly in need of replacement."
After I walked out, I went home, booted into bp tools, taking me to cwm and used adb to push the two files back. The phone already shipped.
However I am thinking of selling it BNIB and getting something else, any ideas what I could get for it
lkrasner said:
worked beautifully! I deleted build.prop and default.prop, so it just went to a black screen after the moto logo. when the guy called the warranty center he said it was "extremely defective and clearly in need of replacement."
After I walked out, I went home, booted into bp tools, taking me to cwm and used adb to push the two files back. The phone already shipped.
However I am thinking of selling it BNIB and getting something else, any ideas what I could get for it
Click to expand...
Click to collapse
Maybe 150. It wont be "NIB" you will not get a box, batt, back cover, etc. With the replacement.
Sent from my SAMSUNG-SGH-I747, running CM9, 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.