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.
Related
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.
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
Alright guys, after seeing 2.20 being rootable I decided to dive back into the One X. I traded my S3 for it + $50. Flawless S3, seriously. The guy I traded with seemed perfectly cool and legitimate but now an issue has arisen.
I didn't think to check it when we made the trade (though I checked other things like mobile data, etc.) but when I made a call later, the person on the other end couldn't hear me.
Here's what I've found:
Microphone works for recording video
Microphone works *on speaker phone*
Microphone works with an external source (bluetooth headset or earbuds with mic)
but the regular handset microphone does not appear to work.
Does anyone have ANY idea what might cause this? Unfortunately, I've already rooted. Literally the only thing I've done. I tried AOKP nightly, I've tried Nocturnal Limited edition. Next I'm going to attempt a RUU.
I've talked to the guy. He swears it was working, I'd like to believe him but neither of us tested it. He didn't test calls on the S3 either so it's not like he wasn't taking the same gamble.
He says that if I can get it working, he'll trade back but since he gave it to me working (as far as he knows) he won't trade back
I'm at a loss here. Can I (legally) mark the S3 as stolen? In that as far as I know, he made me a bad trade and will not simply give me my device back in return for his and his money
HAAAAALLLLLLPPPPP!
Thanks
MyronJ906 said:
Alright guys, after seeing 2.20 being rootable I decided to dive back into the One X. I traded my S3 for it + $50. Flawless S3, seriously. The guy I traded with seemed perfectly cool and legitimate but now an issue has arisen.
I didn't think to check it when we made the trade (though I checked other things like mobile data, etc.) but when I made a call later, the person on the other end couldn't hear me.
Here's what I've found:
Microphone works for recording video
Microphone works *on speaker phone*
Microphone works with an external source (bluetooth headset or earbuds with mic)
but the regular handset microphone does not appear to work.
Does anyone have ANY idea what might cause this? Unfortunately, I've already rooted. Literally the only thing I've done. I tried AOKP nightly, I've tried Nocturnal Limited edition. Next I'm going to attempt a RUU.
I've talked to the guy. He swears it was working, I'd like to believe him but neither of us tested it. He didn't test calls on the S3 either so it's not like he wasn't taking the same gamble.
He says that if I can get it working, he'll trade back but since he gave it to me working (as far as he knows) he won't trade back
I'm at a loss here. Can I (legally) mark the S3 as stolen? In that as far as I know, he made me a bad trade and will not simply give me my device back in return for his and his money
HAAAAALLLLLLPPPPP!
Thanks
Click to expand...
Click to collapse
tell him you fixed it and when u meet up, switch phones and RUN off. thank me if I helped :good:
adulel08 said:
tell him you fixed it and when u meet up, switch phones and RUN off. thank me if I helped :good:
Click to expand...
Click to collapse
lol you helped with a good laugh. That's genius, dude
Run the ruu. If the microphone works in other situations you're fine. Run the ruu.
And no you can't legally say it was stolen.
Sent from my HTC One XL
---------- Post added at 08:37 PM ---------- Previous post was at 08:29 PM ----------
Can't seem to edit my post. I didn't realize you were using the other microphone. You should run the ruu regardless to at least try and sort out any sort of software issue.
Sent from my HTC One XL
ECEXCURSION said:
Run the ruu. If the microphone works in other situations you're fine. Run the ruu.
And no you can't legally say it was stolen.
Sent from my HTC One XL
Click to expand...
Click to collapse
That's about what I thought actually. I'll run the RUU but can you explain what might have happened? If it's not actually broken hardware I don't have a problem keeping the phone but need to know how to avoid it
MyronJ906 said:
That's about what I thought actually. I'll run the RUU but can you explain what might have happened? If it's not actually broken hardware I don't have a problem keeping the phone but need to know how to avoid it
Click to expand...
Click to collapse
The microphone volume is a perennial problem with this phone. No one seems to know for sure what causes it. Reseting and ruu'ing ought to fix it.
Thanks guys, downloading the 2.20 RUU now. It does have to be the 2.20 RUU since I'm already on 2.20 right? No downgrading, is that correct?
I really hope this fixes it, because I love the One X. Haha, don't know how I dodged this problem the first time I had it.
Now I must ask and re-verify.
While booted into Nocturnal Lite
Run RUU
Reboot into stock and make sure everything's working
Reinstall recovery via fastboot
Install ROM of choice
Fastboot boot.img for ROM of choice
Boot up
Love One X
That's it right?
MyronJ906 said:
Thanks guys, downloading the 2.20 RUU now. It does have to be the 2.20 RUU since I'm already on 2.20 right? No downgrading, is that correct?
I really hope this fixes it, because I love the One X. Haha, don't know how I dodged this problem the first time I had it.
Now I must ask and re-verify.
While booted into Nocturnal Lite
Run RUU
Reboot into stock and make sure everything's working
Reinstall recovery via fastboot
Install ROM of choice
Fastboot boot.img for ROM of choice
Boot up
Love One X
That's it right?
Click to expand...
Click to collapse
Correct, you cannot downgrade. But to RUU, you have to relock or it will fail. Also, once you relock, you have to RUU then and there because your phone won't boot up. You'll need to go through the whole unlock/root process again. Remember this will wipe your phone.
iElvis said:
Correct, you cannot downgrade. But to RUU, you have to relock or it will fail. Also, once you relock, you have to RUU then and there because your phone won't boot up. You'll need to go through the whole unlock/root process again. Remember this will wipe your phone.
Click to expand...
Click to collapse
Cool, so I'm not as much of an idiot as I thought. having a new problem though. All my RUUs keep failing. USB error? I feel like a noob.
I was perfectly fine with my first One X and this one is giving me hell now. That's what I get for dancing with the devil lol
By the way, thanks a lot guys. I usually don't need half this much assistance, but you know ish happens.
MyronJ906 said:
Cool, so I'm not as much of an idiot as I thought. having a new problem though. All my RUUs keep failing. USB error? I feel like a noob.
I was perfectly fine with my first One X and this one is giving me hell now. That's what I get for dancing with the devil lol
By the way, thanks a lot guys. I usually don't need half this much assistance, but you know ish happens.
Click to expand...
Click to collapse
Did you relock? An RUU will fail otherwise.
iElvis said:
Did you relock? An RUU will fail otherwise.
Click to expand...
Click to collapse
Yeah man, relocked. I'm running the AT&T RUU found here. Fastboot OEM readCID still shows SuperCID, I'm reinstalling HTC Drivers and then I'll restart the computer. Maybe that's all it is.
MyronJ906 said:
Yeah man, relocked. I'm running the AT&T RUU found here. Fastboot OEM readCID still shows SuperCID, I'm reinstalling HTC Drivers and then I'll restart the computer. Maybe that's all it is.
Click to expand...
Click to collapse
Unplug your phone, turn it off, and restart it. Sometimes that helps. It won't boot, but you can get it back into the bootloader.
Does it need to be in Fastboot or Bootloader? I'm close to giving up on the laptop (which worked fine for the other 90%) and trying my ancient desktop
MyronJ906 said:
Does it need to be in Fastboot or Bootloader? I'm close to giving up on the laptop (which worked fine for the other 90%) and trying my ancient desktop
Click to expand...
Click to collapse
Bootloader.
Pretty sure my drivers have just fubarred. I'm not showing up on adb devices either. GRRRRRR this is driving me mad
EDIT: Finally got the RUU to run. Had to replace the standalone HTC drivers with fullblown HTC sync but it's whatever lol. Now to see if the RUU actually fixes the problem
Ran the RUU. Didn't fix it. I'll run it again, but any more ideas?
MyronJ906 said:
Ran the RUU. Didn't fix it. I'll run it again, but any more ideas?
Click to expand...
Click to collapse
"It" meaning the microphone? The phone is working okay otherwise? If so, I'm out of ideas. Might try flashing different roms to see if there's any change.
iElvis said:
"It" meaning the microphone? The phone is working okay otherwise? If so, I'm out of ideas. Might try flashing different roms to see if there's any change.
Click to expand...
Click to collapse
Yeah, I meant the microphone still isn't working. I've been on the stock RUU, AOKP, and Nocturnal. All of them have the same issue so I'm expecting that it's hardware.
I just don't know what to do guys. I guess I'll e-mail HTC, swing by the AT&T store in hopes of something, and call it done. I find it ****ty that the guy won't cooperate so far because truthfully I *would* at least cooperate but it's tough when he says it was working when he had it and I say it wasn't working when I had it.
BUT he says that he didn't make any calls that day. However, he "knows it was working when he gave it to me"
Guys, I just don't even know what to do. If I can't get it replaced, he completely won out on the trade. I was originally asking for + $100 and lowered it to + $50 for him. Yet he doesn't want to do anything for me.
I want to handle all of this responsibly, but I also want a completely functional phone
MyronJ906 said:
Can I (legally) mark the S3 as stolen?
Click to expand...
Click to collapse
For what purpose, a homeowners/renters insurance claim, or something else? Don't want to sound preachy, but insurance fraud is serious business, and a federal crime. Not worth it for a phone. Homeowners insurance claims for theft also require a police report, which is also something you obviously do not want to falsify.
If the microphone was malfunctioning before you did any mods to the phone, it would seem to me that the guy scammed you. Its highly improbable it was working for him, then just "coincidentally" broke around the time he traded it.
Try unlocking again, and flashing a new ROM. Combination of RUU, then fresh ROM may make a difference. Otherwise, I don't think HTC can do a warranty repair without proof of purchase. But they can probably fix it for a fee. True, the other guy will have made out on the deal, but at least you'll have a working phone.
redpoint73 said:
For what purpose, a homeowners/renters insurance claim, or something else? Don't want to sound preachy, but insurance fraud is serious business, and a federal crime. Not worth it for a phone. Homeowners insurance claims for theft also require a police report, which is also something you obviously do not want to falsify.
If the microphone was malfunctioning before you did any mods to the phone, it would seem to me that the guy scammed you. Its highly improbable it was working for him, then just "coincidentally" broke around the time he traded it.
Try unlocking again, and flashing a new ROM. Combination of RUU, then fresh ROM may make a difference. Otherwise, I don't think HTC can do a warranty repair without proof of purchase. But they can probably fix it for a fee. True, the other guy will have made out on the deal, but at least you'll have a working phone.
Click to expand...
Click to collapse
I did mean for the insurance claim. I didn't want to do it fraudulently which is why I asked. I wasn't sure what the exact definition of stolen (or even lost) in this regard is. But this doesn't count so that's no longer an option. Haha I now see that the AT&T warranty plan doesn't cover user idiocy, just drops and spillage.
I'll RUU again then install an AOSP ROM. I'm pretty sure it's the hardware mic that's busted though. Does speakerphone use a secondary microphone? I imagine videorecording does. If so, do the camcorder and speakerphone use the same mic?
Maybe the noisecanceling mic is screwing things up and that could be software but I think the microphone is just physically broken.
Idiot me, being the hardcore modder made changes to the phone *before* testing for the microphone. In my defense, I've owned the One X before so I knew what the hardware was capable of. I knew the current state of ROMs, so why not pick up where I left off?
I'll send HTC a pity e-mail and see where that gets me. Better to try and fail than to never have tried at all.
EDIT: I wanted to ask as well, does anyone think ROM flashing/BL unlocking etc. Really could have caused this? I mean, if it did there's no reason different software shouldn't fix it. But if it's hardware, that establishes that it's more likely that it wasn't my fault, right?
Well I've finally done it. Hard brinked my phone. wont turn on wont flash any notification lights at me. no response at all. Tried to get back to stock through RUUing, definitely did something wrong. because now the only thing that hints my phone has any life in it, is the small connection sound when hooked up to usb to my computer. Just the sound though. No actual picture of device connected in "My Computer", and nothing on the phone comes up.
Im hopping there is still hope out there but I think it's lost. *que in Star wars quote.
any ideas?
korext said:
Well I've finally done it. Hard brinked my phone. wont turn on wont flash any notification lights at me. no response at all. Tried to get back to stock through RUUing, definitely did something wrong. because now the only thing that hints my phone has any life in it, is the small connection sound when hooked up to usb to my computer. Just the sound though. No actual picture of device connected in "My Computer", and nothing on the phone comes up.
Im hopping there is still hope out there but I think it's lost. *que in Star wars quote.
any ideas?
Click to expand...
Click to collapse
I'v research a bit and havn't found anything too promising, so if there has been any updates on un-bricking phones in the last few months, it'd be great to know..
First I'm going to kindly ask that you change the title of this topic.
Second I'm going to ask what you did prior to the phone becoming unresponsive ie. What ruu?
Third some details about your phone as in is it s-off what hboot do you have.
XDA Moderator
Did you try to run the 3.18 Ruu with s-on and superCID? If you did, jtag or replacement are your options.
Sent from my evita
RollTribe said:
Did you try to run the 3.18 Ruu with s-on and superCID? If you did, jtag or replacement are your options.
Sent from my evita
Click to expand...
Click to collapse
i just made the same mistake the other day.. its being sent into repair right now. im just hoping they have no way to tell HOW the phone got bricked and my warranty isn't void.. here's the link to my thread maybe some helpful info for the OP http://forum.xda-developers.com/showthread.php?t=2393960
but as RollTribe said.. only way to fix it is JTAG or replace motherboard lol.