Ok so I was an idiot and risked it with a ht24 which seemed fine in September when I got it. Now its got the dreaded WiFi problem and its really annoying. Drops out every 5 seconds and just can't use the phone unless I use mobile network.
The problem is, I've rooted and running a custom rom, so I've broke the warranty terms. Will HTC fix it for a fee? And if so, how hefty is this fee for a seemingly simple problem and simple solution.
Sent from my HTC One X using xda app-developers app
They'll fix it, because it's a hardware fault which they are aware of, but it seems like pot luck whether they'll charge you anything. They can't charge to fix the hardware issue, but I remember someone saying that they'd had a repair done and because there was a custom ROM on they'd swapped out the motherboard and charged for that. About £130 if I remember correctly, the post's in the general section somewhere.
Your best bet is to return completely to stock, relock the bootloader, return the phone for the known defect, don't mention anything about having done anything to it, and hope that they just fix it no questions asked as they have done many times before.
take it back the shop, where you buy it, i think yhey will help you.
Related
Here's the problem around the second week of this month my boyfriend's Acer a100 bricked itself. When you turn it on it gets stuck on the Acer logo and will not go any further. I called Acer to try and see if they could help me but they stated that it was a hardware issue and to send it in to be repaired; however, there is some major damage done to the screen. It is crack very bad but it is still usable. I'm wondering is there anyone that can give me some advice on how to fix it or what to do to get it where it can be used again. Another thing is I'm thinking that because of the damage done to the device that it voids the warranty, does anyone know if I am right? oh yeah his device is not rooted.
My device had the same problem one day. i messed around with some things to try to fix it and just made things worse , when i talked to acer it seemed as if it was a common thing because in a matter of mintues i was getting the details of where to ship it to be repaired. To my understanding the cracked screen shouldnt be a problem since they would be replacing the motherboard(i believe) and the screen will come back the same way you sent it to them.
devin12321 said:
My device had the same problem one day. i messed around with some things to try to fix it and just made things worse , when i talked to acer it seemed as if it was a common thing because in a matter of mintues i was getting the details of where to ship it to be repaired. To my understanding the cracked screen shouldnt be a problem since they would be replacing the motherboard(i believe) and the screen will come back the same way you sent it to them.
Click to expand...
Click to collapse
I think thats what he's gon have to do because I have clue what else he should do. I wanna call back and ask them will the damage effect the warranty but I'm to nervous they will actually say yes.
Send it to them and if they call you then you accuse them of breaking it...problem solved lol
Sent from my A100 using xda app-developers app
I read through few posts about people being able to claim their warranty even after unlocking their bootloader , now these people had almost the same problem ..there screen wouldn't display anything or their phone wouldn't boot up at all. So I guess HTC won't check for your warranty if your phone is not booting up ...they'll just check your bill and see if its under warranty and do it for free ...
Sent from my HTC One X using xda app-developers app
Well I've seen people get away with this, but I still darent unlock/root.
Because I know what my luck is like and I would be the only one that doesn't get repaired !!
It took me 4 weeks to pluck up the courage to unlock my phone and I'm glad I did. I now have no warrenty but I do have an awesome phone.
Also I heard that if your phone is completely dead there is no way to tell if the phone is unlocked or not. So there is a reasonable chance you'll get your phone replaced.
Awt67 said:
It took me 4 weeks to pluck up the courage to unlock my phone and I'm glad I did. I now have no warrenty but I do have an awesome phone.
Also I heard that if your phone is completely dead there is no way to tell if the phone is unlocked or not. So there is a reasonable chance you'll get your phone replaced.
Click to expand...
Click to collapse
lol sounds like a good plan, now everyone who needs repair will burn it's phone and get new replacement under warranty
Awt67 said:
It took me 4 weeks to pluck up the courage to unlock my phone and I'm glad I did. I now have no warrenty but I do have an awesome phone.
Also I heard that if your phone is completely dead there is no way to tell if the phone is unlocked or not. So there is a reasonable chance you'll get your phone replaced.
Click to expand...
Click to collapse
Yeah I've been debating for about 3 weeks now, would you really say its worth it?
What ROM you using?
And, about the warranty, what does completely dead mean?
Not booting?
Or bricked etc?
Cheers mate.
I am using Cyanogen Domination 10. It is still work in progress but it stable enough for everyday use. I would also say if you do unlock your phone try roms other as well because they all offer something different.
Dead as in bricked, although if you follow unlock steps carefully there is little chance of bricking your phone
I unlocked my phone the day I bought it ... I'm not regretting it all but the little yellow spot in the bottom left corner is annoying sometimes ..
Sent from my HTC One X using xda app-developers app
lets just make this clear, its certainly posted here already in many many threads...
if you read the unlocking stuff properly on the htc website, it clearly says that the warranty will be invalid for anything caused by unlocking the bootloader
so if you have a blatant hardware problem, ie the wifi antenna problem, they still have to repair it foc
so basically, unless you brick your device, you still have a warranty.
they might try insisting on replacing the main board for a cost, which i've heard quite often. the wifi fix requires changing the main board anyway, so for at least that problem, they shouldn't charge to fix.
still, it does depend on the type of problem as to whether you could convince them not to change the main board..
After flashing the stock google (yukju) roms on my galaxy nexus, everything went fine for a couple of months and now I am getting weird haywire issues with my touch screen. Without me touching anything, the phone will act like a part of my screen is being touched, it will not respond when I am indeed touching it at times, the screen will flicker back and forth and generally act strangely. Then for the other 70% of the time it is fine. I have re-flashed all stock roms, did a factory reset, and the problem persists.
Is anyone else having these problems?
any idea what to do next.
After contacting my provider, they said they cant help me because I had unlocked the phone. I have since relocked the phone so I might try calling back and seeing if it will fool them, but I doubt it. Now that I have re-locked the phone should I try to deal with Samsung?
Any help appreciated!
It sounds like a hardware issue. Most likely the touchscreen itself is bad. If you still have warranty or insurance coverage then bring it back to the store and tell them it is defective. By the way, NEVER mention that you have ever unlocked or rooted your phone.
Sent from my Xoom using Tapatalk 2
Thanks for the reply. Im worried that, like you say, it is a hardware issue because I bought it used, and therefore will probably have problems with warranty/insurance. My carrier has already said that they wont help me with it so I would have to go right to Samsung. Any tips on dealing with Samsung? I have already returned to stock and re-lock the phone and I never rooted it, I certainly wont say I did anything to it in any way. Anything else I should be aware of? Will they even help me out since I wasn't the one who bought the phone in the first place?
GentlemanBasdard said:
Thanks for the reply. Im worried that, like you say, it is a hardware issue because I bought it used, and therefore will probably have problems with warranty/insurance. My carrier has already said that they wont help me with it so I would have to go right to Samsung. Any tips on dealing with Samsung? I have already returned to stock and re-lock the phone and I never rooted it, I certainly wont say I did anything to it in any way. Anything else I should be aware of? Will they even help me out since I wasn't the one who bought the phone in the first place?
Click to expand...
Click to collapse
Although most manufacturers offer a 1 year warranty on hardware, I doubt they will honor it since you were not the original owner. Your next option is repairing it yourself. It took a look at prices on eBay and it looks like the digitizer (touchscreen) for a galaxy nexus goes for about $30 and the combination of digitizer and LCD screen go for about $150. I don't know how difficult it would be to separate the digitizer from the LCD on your phone, but $150 for the set is still better than buying a new phone.
Sent from my Xoom using Tapatalk 2
As has been said, it is probably a hardware issue - I had an HTC Desire S before my GNex and had the same issue with it, started all of a sudden. (The screen would go haywire as you said, almost as if a ghost was pushing buttons quickly - that's the best way I can describe it). Mine did not have warranty coverage because I had rooted and unlocked it but the HTC rep was helpful and said it happens sometimes because of moisture or humidity or some such thing and to replace the lcd/digitizer. Cost me a little ($110) but phone was as good as new after that, used it for six months before selling it and buying the GNex.
Hello everyone,
Recently my Verizon HTC one stopped working. After reading around and contacting HTC customer support, I determined there was nothing to be done but send it back in for warranty. The phone would not respond to any inputs and could not be reset. The charging LED would not turn on when the phone was plugged into an AC adapter, nor would charging it for an extended period of time bring it back. It was dead.
After sending it in for warranty, I am now seeing that they are wanting $200 to fix it because I've rooted it. The included images show a picture of the bootloader which (I believe, it's a pretty small image) indicates that it has been rooted. My question is, if they were able to get it to boot into the bootloader does that mean I could likely refuse the repair and just fix any software issues my self? Has anyone else had a similar issue and solved it without having to pay the $200 repair fee?
Thanks
If they got it into the bootloader then yes, it should be fixable (if its just a software issue), I'd ask for it back and update to the latest firmware if its not already....or.....Get the decrypted RUU and take it back to stock and start over (or just leave it alone).......alot of this information can be found in the Android Development forum, hope this helps...goodluck
I was aware to believe that that Verizon did not check for unlocked or s-off status. Did they update their replacement policy in the past 2 years?
geeibara said:
I was aware to believe that that Verizon did not check for unlocked or s-off status. Did they update their replacement policy in the past 2 years?
Click to expand...
Click to collapse
Maybe I screwed up, but this was through HTC directly. For better or worse I have requested that the phone be sent back to me. If it is still dead when I receive it, I'm assuming I can either send it back in again for repair by HTC or try Verizon (if that is an option)?
I'd ask if anyone has tried this before, but my guess is I'm probably in uncharted waters here...
You can't send it back to HTC as I am sure they logged all the serial numbers that's on that phone and has already logged the phone as having a voided warranty due to rooting. You can try Verizon and hope they don't have access to HTC voided warranty list.
Sent from my HTC6500LVW using Tapatalk
Dark Jedi said:
You can't send it back to HTC as I am sure they logged all the serial numbers that's on that phone and has already logged the phone as having a voided warranty due to rooting. You can try Verizon and hope they don't have access to HTC voided warranty list.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
I would not really expect them to take it back for warranty work, but would they not take it back if I was willing to pay their required $200 fee? Or are you saying they won't even service out of warranty phones for pay?
Yeah if you are willing to pay the fee to get it fixed then they will fix it.
Sent from my HTC6500LVW using Tapatalk
I've never had Verizon give me an issue with rooted or unlocked devices.
More stupid questions.
I got the phone back, it turns on and seemed to work fine, but this morning it spontaneously rebooted and now the vibrate motor seems to be hosed. I have done a factory reset and a restore from an older nandroid backup, but nothing seems to make it work. I know for a fact it was working after I got the phone back. It just seems to suddenly have stopped functioning.
Is this something others have dealt with, or am I likely just dealing with a phone that has an intermittent hardware issue? I'm going to try flashing a different ROM, but thought I would check in with you guys here before doing anything too drastic.
Regarding Verizon, if I bought the phone at Best Buy, would it still be possible to go through Verizon and see if they would send me a replacement for the faulty hardware? Unless this is a known software issue, I'm really starting to think this phone has a hardware issue.
Wildwoodashes said:
More stupid questions.
I got the phone back, it turns on and seemed to work fine, but this morning it spontaneously rebooted and now the vibrate motor seems to be hosed. I have done a factory reset and a restore from an older nandroid backup, but nothing seems to make it work. I know for a fact it was working after I got the phone back. It just seems to suddenly have stopped functioning.
Is this something others have dealt with, or am I likely just dealing with a phone that has an intermittent hardware issue? I'm going to try flashing a different ROM, but thought I would check in with you guys here before doing anything too drastic.
Regarding Verizon, if I bought the phone at Best Buy, would it still be possible to go through Verizon and see if they would send me a replacement for the faulty hardware? Unless this is a known software issue, I'm really starting to think this phone has a hardware issue.
Click to expand...
Click to collapse
have you tried an RUU on it first. it could just be bad software if the thing turns on. i would try that before anything else is done. you'll need to be s-off to do so though.
Well, I flashed back to stock, locked, and s-on. Still no vibrate functionality.
What is the general consensus on Verizon's CLNR policy? I do not see any defects on the phone cosmetically, but what are the chances I'd end up being charged for a replacement? The phone has pretty much been in a case since I got it, and I keep it in a pocket by its self.
As far as my dealings is just as long as it doesn't look like it went through ww3 you should be fine. I sent phones back that had scratches abd a few nicks on the case. They never had a problem with that.
Sent from my HTC6500LVW using Tapatalk
First off my device is unlocked and rooted but that is it and I did that weeks and weeks ago when the latest android patch came out.
It has been working fine but I had a sleep over with the kids last weekend and they like to play with it as usual. After they left, hours later I noticed the device showing the google start screen like it was stuck there. I tried to get it into the boot loader or recovery and nothing. Now it appears dead, no lights, etc.
I tried charging and tried using the volume and power thing, etc to no avail. When connected to the pc I am gettng the dreaded QHSUSB_Dload thing.
#First question is there a fix for this? I have searched every where and have yet to find anything substancial other than the volume thing which is not working.
# second question is can I rma this or will it not be accepted due to it being rooted? There is no way I can bring it back to stock without accessing the bootloader.
#last question - If I cannot rms it can I take it apart and do something to repair it or is there anything I can do?
Thanks guys. This really sucks. i have never had an issue up until now and this thing is totally stock besides being rooted and unlocked.
Have you tried this: http://forum.xda-developers.com/showthread.php?t=2381582
That will not work with a hard brick. I cannot get into bootloader or adb.
Sent from my Nexus 4 using xda app-developers app
Bump
Do you guys think I can do an RMA?
Sent from my Nexus 4 using xda app-developers app
Thanks for the outpouring of support here. :banghead:
I think it is clear I'm screwed.
Pretty unbelievable as I'm all stock except for recovery.
Sent from my Nexus 4 using xda app-developers app
Richieboy67 said:
Bump
Do you guys think I can do an RMA?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I'd try to send it back for repair. What do you have to lose?
What I have to lose is money. If I RMA it is possible for Google to keep the payment and I'm not about to buy another unit because one fails through nothing I did.
Sent from my Nexus 4 using xda app-developers app
Richieboy67 said:
What I have to lose is money. If I RMA it is possible for Google to keep the payment and I'm not about to buy another unit because one fails through nothing I did.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I understand that, but right now you have a $200 paper weight. So why not gamble on the s/h for the rma?
I think you are misunderstanding what I am saying.
Google basically makes you pay for a replacement. Upon inspection they refund the money. If they do not refund the money then I am out the full cost.
I could find that reasonable if I was playing around or something but I have kept my devices all stock ever since the latest version came out except for unlocking and rooting.
I guess the other option would be to find someone to do a jtag repair and I could only find one guy and I don't think he touches Nexus 7s. Not sure though but waiting for him to reply. This sucks! My device was perfect and I loved it.Great battery, no touch screen issues. Not a single issue and then all of a sudden this. i really cannot understand what caused it.
Thanks for the reply. I really figured there would be others this happened too but everyone gets Hard Brick mixed up with soft brick and every hard brick post I read is not a hard brick. Hard Brick = F#cked :crying:
I gotcha. I thought you paid to send it back & then you had the option to pay to fix it if it wasn't covered by warranty.
That could be through Asus directly but not sure.
I think though if they go to repair it they will see the unlocked boot loader. That voids the warranty
Sent from my Nexus 4 using xda app-developers app
If it was mine I would take the back cover off and unplug the battery and let it sit for ~5 min. If there is a physical reset plug then push that in a couple times.
dkryder said:
If it was mine I would take the back cover off and unplug the battery and let it sit for ~5 min. If there is a physical reset plug then push that in a couple times.
Click to expand...
Click to collapse
Yeah, if you know an RMA is a very very very poor shot / don't want to try it. I guess a tear down is your second best bet.
You should check out Adam Outler's tear down videos if you feel you might be able to take this on. I'll link Outler's videos below. They MAY help you in deciding if you want to go through with it (and what you may expect to see).
http://www.youtube.com/watch?v=RMzi4K_PwPs (Transplant Nexus 7 Boards)
http://www.youtube.com/watch?v=QOFpY1nXFew (Nexus 7 Unboxed the XDA way)
Thanks guys.
I finally got an email back from those guys that do Jtag repairs and he said it was a hardware issue but I am not sure if he understood my issue.
I do not think taking it apart and unplugging the battery will work here if the bootloader is corrupt. I am going to try to let the battery go completely dead though and then try to do the volume/power key thing to see if there is any chance.
I do not know much about this but what I read is that if the bootloader is stopped somehow while loading it can become corrupt in some cases and you cannot do anything without it and there is a device specific key involved. That is why only someone with some specific software can fix it. I thought this key as called Jtag but again, I do not know much about this. The Jtag guy said it was hardware.
Man, I have an Hp touchpad that I got years ago. I installed Android on it years ago and have it overclocked it to over 1700mhz and that thing is still going strong. The kids even dropped it and it has a crack in the screen and it still will not die. Here I have a Nexus only a few months old fully stock except for root and unlock and it is dead. Kills me especially after the way I always stand up for the Nexus line. Still loving my Nexus 4 though and it is well over a year old. Oh well, if that one goes like this one I am jumping off a high bridge. :laugh:
Richieboy67 said:
What I have to lose is money. If I RMA it is possible for Google to keep the payment and I'm not about to buy another unit because one fails through nothing I did.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I am confused as to why you are so sure what is wrong with it, how do you know the bootloader is corrupt if you claim no wrong doing. Also technically speaking you did do something to begin with, you knew full well that you would be voiding the warranty by rooting and installing a custom recovery. More than likely if kids messing with it actually did end up with it how it is now they probably accepted an OTA and it corrupted the boot, on the LG G2 they have figured out how to delete the FOTA information that it continuously tries to boot from and return normal boot sequence.
But I reiterate you cannot blame this on anyone but yourself right now, being angry with ASUS or the kids will do you no good. You knowingly voided your warranty now it is time to put your nose down and see if you can fix it, there are a lot of resources here to do such.
whoamanwtf said:
I am confused as to why you are so sure what is wrong with it, how do you know the bootloader is corrupt if you claim no wrong doing. Also technically speaking you did do something to begin with, you knew full well that you would be voiding the warranty by rooting and installing a custom recovery. More than likely if kids messing with it actually did end up with it how it is now they probably accepted an OTA and it corrupted the boot, on the LG G2 they have figured out how to delete the FOTA information that it continuously tries to boot from and return normal boot sequence.
But I reiterate you cannot blame this on anyone but yourself right now, being angry with ASUS or the kids will do you no good. You knowingly voided your warranty now it is time to put your nose down and see if you can fix it, there are a lot of resources here to do such.
Click to expand...
Click to collapse
First off, I am not sure what is wrong with it which is why I am posting here. I stated numerous times that I do not know much about this.
And yes, I know this that rooting and unlocking voids the warranty. I also know that it is my fault for doing it but I have been doing it for around 3 years now and have used various roms and kernals in the paqs and have never had an issue. Perhaps it is a hardware issue. I just do not think this issue was caused by me.
In terms of the kids playing with the device. They play games, things like that. The desktop is locked and they have no access to settings or anything. When I said messing with it I just meant playing games though sometimes they open new games and leave the old ones running. I do not know how that would cause this.
There was no ota or update.
I am not sure what you are saying about LG.
And again, I am not angry with Google or Asus. My point was that this issue was most likely not caused due to rooting or unlocking and an ota would not cause a dhsusb issue even if it did go bad.Lets try to remember that nearly everyone here roots, unlockes and installs roms, etc. I have done so as well but not on this device. This one I wanted to keep pretty much vanilla but I wanted to be able to use Titanium back up, etc. And also, I rooted and unlocked months ago when I first got the device and had to root again when the latest version came out which was awhile ago.
In terms of fixing I have not found a solution for this. I do not know if it is a hardware issue or a software issue. That is why I am posting here. I am looking for some information from people who know this stuff. I know nothing but what I have read and so far I have read many different things. I am here to learn.
OK so here is what I meant with the G2..
I had a stock/rooted/TWRP G2 and half asleep accepted an OTA Update, when it does this it downloads the update into a partition that the device checks before booting. Because I had the custom recovery obviously the update failed but it left that code in the boot partition that would now allow me to even get into download mode. See this post here for how it was fixed http://forum.xda-developers.com/showthread.php?t=2582142
I am not sure if this would be the same problem or how to go about fixing it because of the device difference, but maybe it could help? I didn't mean to come off as a ****, just far too many people like to get into their devices and void the warranty then blame everyone else.
It is really not difficult to pull the back cover off and unplug the battery, I suggest doing this it could very well help just be careful not to crack the back while pulling it off, a credit card/ID and a butter knife should do the trick without leaving marks.
No worries. I appreciate the help.
I agree with you totally.
Sent from my Nexus 4 using xda app-developers app