Database Info

Rooting, Warranty, Insuranc?

I'm aware that rooting my Xoom voids the manufacturers warranty, but does anyone know how it effects the insurance from Verizon? No point in paying $12 a month if they aren't going to replace it anyway.
Sent from my Xoom using Tapatalk

crauzz said:
I'm aware that rooting my Xoom voids the manufacturers warranty, but does anyone know how it effects the insurance from Verizon? No point in paying $12 a month if they aren't going to replace it anyway.
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Rooting does not effect insurance at all. Also if you can unroot before sending it back in, it won't effect your warranty either .

bwcorvus said:
Rooting does not effect insurance at all. Also if you can unroot before sending it back in, it won't effect your warranty either .
Click to expand...
Click to collapse
Insurance I can agree with, you pay for it, you should be able to use it. Think of your car & how it works.
However, the Warranty is still void by rooting it, end of story. Getting a replacement on warranty is dishonest and only contributes to the problem of them locking the boot loaders down even more.

orionshock said:
Insurance I can agree with, you pay for it, you should be able to use it. Think of your car & how it works.
However, the Warranty is still void by rooting it, end of story. Getting a replacement on warranty is dishonest and only contributes to the problem of them locking the boot loaders down even more.
Click to expand...
Click to collapse
Not going to debate you, but let me ask you one question. If i root my phone, then my usb plug brakes you are saying i should not be able to claim it under warranty?

I think he means if you mess up your phone by flashing firmware. I don't agree with all those people who root when they have no business doing so, without the required knoledge, then when something goes wrong they freak out and lie their way into a new device
Sent from my Desire HD using XDA App

If you root it, shouldn't effect warranty of hardware - honestly just restore it and send it in. Hardware is unrelated to software bricks

I guess really you can just use the one click root method to unroot and re lock the boot loader and no one would really know is that true?

gysgtusmc said:
I guess really you can just use the one click root method to unroot and re lock the boot loader and no one would really know is that true?
Click to expand...
Click to collapse
you can't relock the wifi only. still has issues.

oh ok did not know that thank you!

SD Card unmounted/unavailable

I just flashed MIUI and im getting this error. I cant get to my SD card via USB cable/PC either.
Wtf is going on? Im out of my 30 day return period with radioshack and AT&T wont let me exchange the phone because I got it from radioshack
****ing bull****

Same question as your other post. Don't make multiple threads (cross post) about the same topic.
And don't return your phone under warranty because you were messing with the phone and screwed it up. Crap like that is the reason they lock bootloaders in the first place.
Sent from my HTC One X using XDA

Gave suggestion in other thread....

Look, I'm not trying to come off as a ****, but this is what I think.
You voided your warranty by unlocking the bootloader. You knew that by doing this, you won't be able to return it to HTC. You are the one who flashed the ROM, knowing that it could very well screw up your phone.
AT&T and HTC didn't do anything to push you to do that. So for you to turn around and say that they are "bull$hit" is utter and completetly stupid. They didnt do anything to your device. They provided you with an excellent phone that you turned around and screwed up. If you had any sense of moral, you wouldn't return your phone, because it is your fault that you screwed your phone up.
So next time, don't get mad at the carriers. Get mad at yourself for f'ing up your device.
Think twice before you do anything that will void your warranty. It's people like you unfortunately that cause locked bootloaders and very quick patches for root exploits for the rest of us.

I agree with everything said about this being your fault. However, try seeing if you can format the SD card inside recovery. Or try relocking the boot loader and ruu back to stock and see if that fixes the SD card. If it does, be glad you dodged a bullet.
Sent from my MIUI'd HTC One X

rohan32 said:
Look, I'm not trying to come off as a ****, but this is what I think.
You voided your warranty by unlocking the bootloader. You knew that by doing this, you won't be able to return it to HTC. You are the one who flashed the ROM, knowing that it could very well screw up your phone.
AT&T and HTC didn't do anything to push you to do that. So for you to turn around and say that they are "bull$hit" is utter and completetly stupid. They didnt do anything to your device. They provided you with an excellent phone that you turned around and screwed up. If you had any sense of moral, you wouldn't return your phone, because it is your fault that you screwed your phone up.
So next time, don't get mad at the carriers. Get mad at yourself for f'ing up your device.
Think twice before you do anything that will void your warranty. It's people like you unfortunately that cause locked bootloaders and very quick patches for root exploits for the rest of us.
Click to expand...
Click to collapse
lol

lessthanzach said:
I agree with everything said about this being your fault. However, try seeing if you can format the SD card inside recovery. Or try relocking the boot loader and ruu back to stock and see if that fixes the SD card. If it does, be glad you dodged a bullet.
Sent from my MIUI'd HTC One X
Click to expand...
Click to collapse
I had the EXACT same issue as the OP. What worked was this.
Get into FastBoot mode and connect via usb. Relock your bootloader (htcdev site tells you how), then RUU back to stock. If you try to ruu back to stock without relocking your bootloader it will not work.
After I went back to stock, I re-unlocked the bootloader (took liek 20 tries) and all is well again.

CollegeProfesor said:
lol
Click to expand...
Click to collapse
most ironic username EVER!

gunnyman said:
most ironic username EVER!
Click to expand...
Click to collapse
Whats even more ironic is that I'm in high school...

rohan32 said:
Whats even more ironic is that I'm in high school...
Click to expand...
Click to collapse
u must be so smrt bro!

rohan32 said:
Whats even more ironic is that I'm in high school...
Click to expand...
Click to collapse
it's like raiaiiaaaaaaaaain on yer wedding day....

Posting.

Downgrading after new update? Also warranty and root/unlock questions

As a preface, I got the ATT one x a few days ago, so far I'm really happy with it, but would like to get rid of a bunch of the bloatware and want to get root.
So this morning I woke up to the update message. Now I read up on it the night before on these forums that I should wait to update if I want to root/etc, so naturally I don't want to update quite yet. But here's the problem. The message popped up so fast that I could barely read the message. My thumb must have been right above the accept button, since the message disappeared almost instantly and the process started up. I exited it as far as possible, and it seemed to work. I used apps on the phone, and everything seemed fine. As soon as I locked the phone again, it decided to reboot, initiating the update, all on its own. Even a forced power-off wouldn't stop the wheels turning. And now I feel like an idiot. So is there any way/what is the best way to downgrade or reverse the update?
TL;DR: I accidentally updated the new update, is there, and or what is the best way to downgrade so I can eventually root?
As for my second question, obviously the warranty will be in question if I root/unlock. I've read that HTC will honor the warranty even if it's an unlock, but not a rom flash (even after a return to stock?) If I root/unlock, run into a problem, and return to stock will by warranty be effected? I've never done a warranty return, so would there be a difference if I tried to go through HTC, ATT, or Costco (purchase location)? The reason I ask is because my last phone's (Original Atrix, love it so much) wifi died before the 2 year period, and we had an upgrade on the family account, and this time the One x was purchased with American Express, so I now effectively have a 2 year warranty to cover such problems I might have.
I know that with enough time I could find some of these answers on the forums, but because they are so lively, it's hard to keep track and sift through the forums for information. Thanks for your time and thank you in advance for your help.

In regards to the root on the update there is no way to downgrade or root given your situation at this time but hopefully one of the talented people here on xda wil find a new exploit like they did for the 1.85
As far as warranty goes someone else will.have to let you know.
Sent from my Nocturnalized Beast

same boat
I am in exactly the same boat. I didn't check the MD5 on a download of CR4.5 and it completed wiped my phone (SD Card as well). I was away from my laptop and had to wait days to get it back online. When I finally got it up and running, I was rooting through the one click and in checking the update, it updated to 2.20. So now I'm stuck.
I have my previous unlock token, but I'm not sure if that will do me any good. I don't want to do much until a new RUU becomes available.
misiek93 said:
As a preface, I got the ATT one x a few days ago, so far I'm really happy with it, but would like to get rid of a bunch of the bloatware and want to get root.
So this morning I woke up to the update message. Now I read up on it the night before on these forums that I should wait to update if I want to root/etc, so naturally I don't want to update quite yet. But here's the problem. The message popped up so fast that I could barely read the message. My thumb must have been right above the accept button, since the message disappeared almost instantly and the process started up. I exited it as far as possible, and it seemed to work. I used apps on the phone, and everything seemed fine. As soon as I locked the phone again, it decided to reboot, initiating the update, all on its own. Even a forced power-off wouldn't stop the wheels turning. And now I feel like an idiot. So is there any way/what is the best way to downgrade or reverse the update?
TL;DR: I accidentally updated the new update, is there, and or what is the best way to downgrade so I can eventually root?
As for my second question, obviously the warranty will be in question if I root/unlock. I've read that HTC will honor the warranty even if it's an unlock, but not a rom flash (even after a return to stock?) If I root/unlock, run into a problem, and return to stock will by warranty be effected? I've never done a warranty return, so would there be a difference if I tried to go through HTC, ATT, or Costco (purchase location)? The reason I ask is because my last phone's (Original Atrix, love it so much) wifi died before the 2 year period, and we had an upgrade on the family account, and this time the One x was purchased with American Express, so I now effectively have a 2 year warranty to cover such problems I might have.
I know that with enough time I could find some of these answers on the forums, but because they are so lively, it's hard to keep track and sift through the forums for information. Thanks for your time and thank you in advance for your help.
Click to expand...
Click to collapse

BB2DX said:
I am in exactly the same boat. I didn't check the MD5 on a download of CR4.5 and it completed wiped my phone (SD Card as well). I was away from my laptop and had to wait days to get it back online. When I finally got it up and running, I was rooting through the one click and in checking the update, it updated to 2.20. So now I'm stuck.
I have my previous unlock token, but I'm not sure if that will do me any good. I don't want to do much until a new RUU becomes available.
Click to expand...
Click to collapse
The ruu is out for the 2.20 on the HTC dev site
If you already have your unlock token you should be fine just run through the steps to unlock then root. Your still stuck with the new hboot so your previous nandroids will no longer work and you can no longer flash boot images from recovery.
Sent from my Nocturnalized Beast

misiek93 said:
As for my second question, obviously the warranty will be in question if I root/unlock. I've read that HTC will honor the warranty even if it's an unlock, but not a rom flash (even after a return to stock?) If I root/unlock, run into a problem, and return to stock will by warranty be effected? I've never done a warranty return, so would there be a difference if I tried to go through HTC, ATT, or Costco (purchase location)? The reason I ask is because my last phone's (Original Atrix, love it so much) wifi died before the 2 year period, and we had an upgrade on the family account, and this time the One x was purchased with American Express, so I now effectively have a 2 year warranty to cover such problems I might have.
Click to expand...
Click to collapse
Consensus seems to be that a warranty return to AT&T, they don't normally check for bootloader unlock at all. Technically, they can check, and void your warranty. But to this point, they don't seem to be. This is probably your safest bet. But that warranty is only one year.
Based on various reports by XDA users HTC seems to be much more strict about enforcing their own warranty terms. I would suggest going through AT&T rather than HTC.
For your AmEx warranty, I think that would be handled by AmEx (not AT&T). You should probably check through them, and see what the warranty terms our (might be handled by a 3rd party?). I think only someone that has had experience with the AmEx process could say for sure what would happen in this case. So maybe somebody will chime in.

redpoint73 said:
Consensus seems to be that a warranty return to AT&T, they don't normally check for bootloader unlock at all. Technically, they can check, and void your warranty. But to this point, they don't seem to be. This is probably your safest bet. But that warranty is only one year.
Based on various reports by XDA users HTC seems to be much more strict about enforcing their own warranty terms. I would suggest going through AT&T rather than HTC.
For your AmEx warranty, I think that would be handled by AmEx (not AT&T). You should probably check through them, and see what the warranty terms our (might be handled by a 3rd party?). I think only someone that has had experience with the AmEx process could say for sure what would happen in this case. So maybe somebody will chime in.
Click to expand...
Click to collapse
Amex is extremely lax. All they want is a copy of the original warranty and require doing the work at an authorized repair shop. Then they reimburse you, no questions asked.

GroovyGeek said:
Amex is extremely lax. All they want is a copy of the original warranty and require doing the work at an authorized repair shop. Then they reimburse you, no questions asked.
Click to expand...
Click to collapse
I kinda figured as much. They aren't in the business of fixing phones, so I guessed they either just farmed it out to a 3rd party company, or just paid up pretty easily. Credit cards (especially AmEx) also often cover things like lost luggage, travel insurance (cancelled flights, etc.) and I don't imagine they go through much hassle confirming that kind of thing either. They must figure that the extra business gained from offering their services (and yearly fees) outweighs the payouts they have to make.
Thanks for clarifying with your personal experience, probably useful to the OP.

Used RUU, screen doesn't turn on

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.

Questions about RMA

So I just discovered cracks on the corners of my tablet as well as the headphone port. I spoke to nvidia and they are going to send me another 1 but I have a question. I'm am rooted and unlocked bootloader, do I need to relock the bootloader? Is it even possible? What should I do?

Jaybenosa said:
So I just discovered cracks on the corners of my tablet as well as the headphone port. I spoke to nvidia and they are going to send me another 1 but I have a question. I'm am rooted and unlocked bootloader, do I need to relock the bootloader? Is it even possible? What should I do?
Click to expand...
Click to collapse
As far i read (Don't ask me where, can't remember. But some others has reported it too) root your device is not gonna prevent nVidia to RMA your defective tablet. Now, speaking about unlocking the bootloader is another history. They say you'll void your warranty by unlocking it, but they teach you how to do it just in case you want to go back to a previous version of your OS because the current one doesn't like you. It has to be proved that the damages on hardware were caused by your fault trying to install custom roms which stress your device; with that in mind you should be safe because the cracked edges are a well know problem, they probably will not even watch your tablet. As i saiud before, they said somewhere that cracked tablets or defective ones with hardware issues are gonna be replaced even with the bootloader unlocked.
Please let us know how it was at the end for knowledge base.

The Cracked Edges thread on NVidia forum says they will RMA "No questions asked".
And that means unlocked rooted tablets are fine.
Mine was unlocked and rooted and no issues. They know it has cracked edges and that is what they are replacing. It's not like the tablet is unable to boot.
I would factory reset the device before sending it back. I did. If you really want to, you can relock the bootloader, but they really don't seem to care.

I had an unlocked one RMA'ed for cracks. It looks like you won't instantly loose your warranty, just that if they think you broke it after unlocking you probably won't be getting the warranty replacement. Most of the time manufacturers will instantly kill your warranty and even track which devices get unlocked just to make sure they lose warranty. So being cautious is a good idea, but it doesn't look like nvidia is as unreasonable as most of the others.

Is there a way to relock the bootloader just to be safe?
Thanks for all the replies!

Jaybenosa said:
Is there a way to relock the bootloader just to be safe?
Thanks for all the replies!
Click to expand...
Click to collapse
Yes. Just get into the fastoobt/bootloader and type fastboot oem lock and you're done. But as far i know there is a flag displayed on your screen which says "You void your warranty" blah blah blah blah...