Database Users

unlocked bootloader - warranty replacement story- FYI

I have a AT&T Nexus one (rooted) which developed trackball issues. The trackball got stuck and would keep throwing me into fastboot upon reboot. I could plug it in and fastboot reboot via PC, but then it would only boot into safe mode.
So I called it in, asked for a device exchange....did not discuss bootloader status (was not asked, did not volunteer). Got my replacement the next day! (awesome). Put stock recovery and ROM and Shipped back the old one - checked status on service site - it was initially set to we have received it, to now it says
Status: We have completed your case. If you can help us improve our service, or would like to comment, please contact HTC customer service representatives.
Service Type: Repair
Service Model: C4-On site exchange
Failure Description: cx track ball isnot working properly.
So looks like HTC honored the warranty. the whole process was extremely painless. A+ customer service, if you ask me!
Anyway, thought I would paste it here for people who are a) in a dilemma to unlock the bootloader or not or b) are in the same boat I was in.

Just rooted my AT&T Nexus one, and I hope that if anything does happen, I can have it replaced as seamless as yours!

I have yet to see a single person on any website with a legitimate hardware issue fail to get warranty coverage. Not saying it hasnt happened but I have been heavily searching these forums and others recently as I made up my mind to buy in and I have not seen it. Some have had to revert to Google but overall it seems to me Google should get kudos for what appears to be a reasonable and fair look at the problems and acting accordingly.

And that makes sense, rooting your phone wont cause your trackball to get stuck.
Again, you did agree to voiding the warranty when unlocking the phone. But im glad google/HTC are reasonable enough to honor hardware failures like that even if its rooted. Thanks for the FYI.

how do you check for the status? i can't find the website any where

the link was in the email they sent confirming the receipt of the old phone.
you need an HTC ticket no and can check it here
http://tracking.e2e.asia.htc.com/ViewTicket.aspx
how do you check for the status? i can't find the website any where
Click to expand...
Click to collapse
Sent from my Nexus One using Tapatalk

krabman said:
I have yet to see a single person on any website with a legitimate hardware issue fail to get warranty coverage. Not saying it hasnt happened but I have been heavily searching these forums and others recently as I made up my mind to buy in and I have not seen it. Some have had to revert to Google but overall it seems to me Google should get kudos for what appears to be a reasonable and fair look at the problems and acting accordingly.
Click to expand...
Click to collapse
HTC denied me warranty service at first due to the unlocked bootloader. A forum member that works for the Google sales team helped me out and got them to reverse the $196 charge for excessively dusty screen.

Important Safety Tip For Hardware Locked Vibrants!

This might come off as me preaching here, but I hope I don't come across as high-handed...
If you have a hardware button sequence locked Vibrant you really need to think long and hard about whether or not you should be messing with custom firmwares, ESPECIALLY NOW.
The last few leaked firmwares (JI2, JI4, JI5) are ALL RUNNING A NEW KERNEL. One that is not compatible with JFD derived builds. Furthermore these great new custom kernels provided by our awesome dev's (Voodoo, JAC, Kingclick, etc...) are not compatible with these new leaked builds. So the likelihood of you ending up staring at a really scary screen on your phone is skyrocketing, unless you have reliable methods to deal with that scary screen.
I've ran across numerous posts here today, with all the fervor over the JI5 Kies leak, where people have Clockwork Recovered themselves into a nightmare because they simply didn't understand these points. Even simpler MOD's (like a few posts I found today where people were installing the JFD version of the MobileAP mod on JIx builds and screwing their phones up) can lead to grief if you don't do your homework.
If you cannot reliably get into recovery *AND* download mode, please please be sure you understand the risks your taking if you fail to be careful and read the information that is already here. Granted, I know few people can keep up with some of us and our ability to soak up info like a sponge. Still there is a process of risk assessment YOU MUST BE RESPONSIBLE FOR when you realize you are doing things that you probably shouldn't be.
This doesn't mean I won't continue trying to be helpful. I just want to make it clear to some of you that you really need to think things through more thoroughly before you let your excitement drive you into a corner.
I vote for the following statement to be made a sticky in this and the Q&A Forum...
"If you are updating firmware on a phone, and you've already hacked this and that, tweaked this and that, modified this and that...whatever the case may be you should be prepared to have to Odin your way back to stock.
If you are not prepared to Odin your way back to stock (don't know how, have a hardware button locked phone, etc...) then you should really be asking yourself whether or not you should be customizing your phone to the degree that you are.
It's just about risk assessment. Most risks are known, but some are not. Furthermore there can be bad synergies between multiple tweaks, mods, and/or hacks that no one can easily predict ahead of time. So it's not about anyone trying to be elitist. The best way to help people is to help them avoid making critical mistakes."

actually if u have a hardware locked phone, what you SHOULD do is call tmobile right now and complain that ur phone is defective and they'll send u a new one... keep doing this till u get a working phone, i did and i now have a phone that isn't HL'ed... only took one try

ookas said:
actually if u have a hardware locked phone, what you SHOULD do is call tmobile right now and complain that ur phone is defective and they'll send u a new one... keep doing this till u get a working phone, i did and i now have a phone that isn't HL'ed... only took one try
Click to expand...
Click to collapse
Indeed!!!
The hardware locked Galaxy S thing appears to be a bootloader bug affecting more than just our Vibrants (some other batches of Galaxy S phones are affected) rather than a real hardware issue, so T-Mobile should be able to get these fixed readily. Not like we should care about T-Mobile here, but what this means also is that T-Mobile shouldn't be making a huge deal about swapping these out either.
I'd encourage everyone with a button-sequence screwed Vibrant to simply go to T-Mobile and get it replaced.

Admittedly, I was one of those fools who installed the wrong MobileAp and also tried to go back to a nandroid that didn't work (different kernel - or so I have learned.) Bricked the phone. But I wasn't hardware locked so I was able to get everything back thanks to some really helpful people here on the forum.
I agree that all hardware locked phones should be returned. If mine were locked then I'd still be staring at a dead phone.
I would like to add that I am new to the android thing. But, I am not a software noob (i did software testing for a living). The thing is that I am sometimes impulsive and that leads to mistakes. Thankfully, I have a way to get out of the mistakes (ODIN and non-hardware locked phone.) I always know the risk I am taking and take full responsibility for anything I screw up.

How can I tell if I have a hardware-locked phone, without attempting to flash a ROM, I mean?
Thanks

aad4321 said:
i have a hardware locked phone that i unlocked and have a custom recovery on. I have only accessed the recovery through rom manger. is there any other way to access it with hardware locked? If so can someone post details. it will be good to know when i mess up my phone and it dosent boot preventing me from accessing rom manager to get to the recovery
Click to expand...
Click to collapse
you didn't unlock the hardware. You just simply rooted your phone. Hardware lock can not be unlocked and that's what this thread is trying to address. I have tried exchanging my phone from tmo once and the exchange phone they sent me still had the same problem, so i haven't bother with it. I wonder if i can just walk into a store and do an exchange since i got my phone from tmo online. Anyways, if you have a hardware locked phone, stick with roms that will flash through clockworks. That is the safest way, but keep in mind that there is still a slight chance of failure.

BruceElliott said:
How can I tell if I have a hardware-locked phone, without attempting to flash a ROM, I mean?
Thanks
Click to expand...
Click to collapse
Never mind; I figured it out.

Man, I'm glad I read your post on hardware-locked problems. I didn't even realise this was a problem until after I dicked around with my phone a bunch, and then ended up reflashing with odin back to stock. I could have messed up big time.
My problem is that I can't replace my phone at all. I purchased a T-Mobile Samsung Vibrant online, brand new, unopened and locked for use here in Canada on the Wind Mobile network.
After hearing about this defective hardware I called T-Mobile, they said I have no warranty with them since it wasn't a T-mobile store purchase. Alright I guess. So they give me the number to Samsung USA,USA transfers me to Canada, I get transferred back again and this is what I'm stuck with.
My new phone has NO warranty, in either country. Both refuse to honour any sort of warranty, and refer to the other for support. I didn't think I'd get this sort of run around from Samsung.
USA says that because I live in Canada, I voided the warranty.,
Canada says that because it's a USA device, and I didn't purchase an international warranty, they won't touch it.
I'll just have to be careful what I install on my phone, and avoid Samsung products in the future.
Thanks for the warning

I wouldn't say your lack of warranty is any surprise. I don't know about Canada, but in the US, phone warranty is normally tied to the carrier, which means if you're not an active customer using the phone on the account that it was first activated on, you will have no warranty. Nothing special about Samsung here, all brands are the same.
Sent from my SGH-T959 using XDA App

cwoodworth said:
Man, I'm glad I read your post on hardware-locked problems. I didn't even realise this was a problem until after I dicked around with my phone a bunch, and then ended up reflashing with odin back to stock. I could have messed up big time.
My problem is that I can't replace my phone at all. I purchased a T-Mobile Samsung Vibrant online, brand new, unopened and locked for use here in Canada on the Wind Mobile network.
After hearing about this defective hardware I called T-Mobile, they said I have no warranty with them since it wasn't a T-mobile store purchase. Alright I guess. So they give me the number to Samsung USA,USA transfers me to Canada, I get transferred back again and this is what I'm stuck with.
My new phone has NO warranty, in either country. Both refuse to honour any sort of warranty, and refer to the other for support. I didn't think I'd get this sort of run around from Samsung.
USA says that because I live in Canada, I voided the warranty.,
Canada says that because it's a USA device, and I didn't purchase an international warranty, they won't touch it.
I'll just have to be careful what I install on my phone, and avoid Samsung products in the future.
Thanks for the warning
Click to expand...
Click to collapse
Other companies will do the same thing. Warranties are country specific, no?

I don't know how it works with mobile phones, but whenever I've purchased computer parts, the country of origin has never been a problem. Maybe I've just been lucky.
Still have gripes about GPS, and lack of 2.2 though.
Don't misunderstand me though, I love this phone. Just surprised about the hardware issues.

I called Samsung today after tmobile rep gave me a number for warranty. After complaining and speaking to a supervisor, they said i could send it in and they would "fix" it. This is what they sent in the email.
Product Symptoms : Technical Inquiry/Internal Menu/Software Reflash - FOC/No fee. The Samsung Rep said a technician would look at it.
I got a shipping label and everything.
I have one question. How should i go about reflashing to stock? can i just factory reset + remove superusers. please help.

cwoodworth said:
I don't know how it works with mobile phones, but whenever I've purchased computer parts, the country of origin has never been a problem. Maybe I've just been lucky.
Still have gripes about GPS, and lack of 2.2 though.
Click to expand...
Click to collapse
PC parts aren't as tightly controlled as mobile phones. That's the difference.
GPS and Froyo should be coming soon. I doubt if Samsung would let their best mobile phones fall behind by much. From the leaked firmwares popping up, it shows they're working on it.

Latest and greatest for atrix?

My phone has been half broken for the better part of 3 months because i partitioned the internal sd and lost half my touch screen and the buttons on the bottom of the phone. So i got it fixed thanks to kermit and bongd and now im on 4.1.5.7 and I didn't do the newer update yet. My question is now what's the latest and greatest for the atrix as far as roms go. I used gingerblur in the past but its been 3 months so im wondering what you guys are using now
Sent from my MB860 using XDA App

moto 2.3.4

+1
lsxrx7 said:
moto 2.3.4
Click to expand...
Click to collapse
Sent from my MB860 using XDA App

Start here:
http://forum.xda-developers.com/showthread.php?t=1142674

I just can't see losing the warranty on my phone..

They never said it would. Just that it MAY.

ChumleyEX said:
I just can't see losing the warranty on my phone..
Click to expand...
Click to collapse
Lol, sux to be you then.
Sent from rooted Atrix on 2.3.4 with unlocked bootloader using xda premium app.

Can always go stock if u need to have the phone fixed through moto. I thought I read that the leaked 2.3.4 wasn't necessarily made for atrix and alot of things didn't work fully? And thanks for the info
Sent from my MB860 using XdA App

4.1.83 is the last official build for att, has been out for awhile and is very stable, no reason not to go to that.
Soon the 2.3.4 update will be out officially, tell then we can just wait.
and the same players are pretty much the same, higher version numbers but gingerblur, grayblur, gladiatrix are still the favorites.

My thoughts on warranty are that unless its obvious that its been tampered with (specifically that it says unlocked when first powered on), then warranty would not be an issue. All reports ive seen say that when flashing back to a stock 1.8.3 sbf, that unlocked disappears, even though the bootloader may still be partially unlocked. On top of that, in most cases, if the phone is damaged beyond the ability to repair with a sbf flash, its probably not going to be functional enough for the unlocked status of the bootloader to be determined in the first place. there is always a chance, but imo its very minimal.
In regards to "whats best" 1.8.3 with gingerblur imo is the best option if you arent willing to do some tweaking and play with the unlocked bootloader and 2.3.4. If you are however, then unlocked, rooted, 2.3.4 is the shiznit.

Conversation is winding up on the Motorola forums, and one of the forum managers, Mark, has indicated a survey will go out very soon, (soon being in the next few days), for soak testing the 2.3 update.
Looks like they may aim for very early July, if not end of this week, to start pushing out soak test beta updates.

pyro254750 said:
My thoughts on warranty are that unless its obvious that its been tampered with (specifically that it says unlocked when first powered on), then warranty would not be an issue. All reports ive seen say that when flashing back to a stock 1.8.3 sbf, that unlocked disappears, even though the bootloader may still be partially unlocked. On top of that, in most cases, if the phone is damaged beyond the ability to repair with a sbf flash, its probably not going to be functional enough for the unlocked status of the bootloader to be determined in the first place. there is always a chance, but imo its very minimal.
Click to expand...
Click to collapse
Unlock does disappear when you flash back, but where do you think all the refurb phones come from?
They go back to Moto, who run diagnostic software and tools to determine what, if anything, needs to be repaired before they send the phones back out as refurbs. They will see right away it is unlocked, and if it voids your warranty, expect a bill from them, or your carrier, after the fact. This happened to an ex of mine a couple of years ago where she was billed the full value of the replacement phone by AT&T after they found she had messed with the one she sent back. That was a Moto phone also.
Sure, if you run over your phone with your car you will be ok, but what if it's something simple like the screen goes out, power button stops working, etc.?
If people are worried about voiding their warranties, they have every right to not risk their warranties, and also to not listen to stupid advice telling them they, (Moto, AT&T, whoever), will probably never know!

CaelanT said:
Unlock does disappear when you flash back, but where do you think all the refurb phones come from?
They go back to Moto, who run diagnostic software and tools to determine what, if anything, needs to be repaired before they send the phones back out as refurbs. They will see right away it is unlocked, and if it voids your warranty, expect a bill from them, or your carrier, after the fact. This happened to an ex of mine a couple of years ago where she was billed the full value of the replacement phone by AT&T after they found she had messed with the one she sent back. That was a Moto phone also.
Sure, if you run over your phone with your car you will be ok, but what if it's something simple like the screen goes out, power button stops working, etc.?
If people are worried about voiding their warranties, they have every right to not risk their warranties, and also to not listen to stupid advice telling them they, (Moto, AT&T, whoever), will probably never know!
Click to expand...
Click to collapse
As i stated in my post, that was just my opinion, i never deemed it to be fact. Id also like to add, that i was referring to att tech support, and replacement being done under att insurance, NOT motorola direct.

pyro254750 said:
As i stated in my post, that was just my opinion, i never deemed it to be fact. Id also like to add, that i was referring to att tech support, and replacement being done under att insurance, NOT motorola direct.
Click to expand...
Click to collapse
Yup, and AT&T doesn't just junk them. They return them for evaluation/repair. Doesn't matter if your replacement is through insurance. They still repair and sell as refurbs if possible.

ceo.mtcl said:
Lol, sux to be you then.
Sent from rooted Atrix on 2.3.4 with unlocked bootloader using xda premium app.
Click to expand...
Click to collapse
How so, I love my phone? I won't suffer in the least from whatever I'm not doing.. lol
I don't have to have the latest and greatest hack or mod that's going around so that I can impress people.. My phone does everything I've needed of it so far (with rooting) and saving whatever money I can if it breaks within the warranty period is a no brainer.. Yes maybe it could look cooler or run just a tiny bit faster (I also can wait for the official at&t update for some of that) but nothing looks cooler than a working phone and $400 in my pocket..

CaelanT said:
Yup, and AT&T doesn't just junk them. They return them for evaluation/repair. Doesn't matter if your replacement is through insurance. They still repair and sell as refurbs if possible.
Click to expand...
Click to collapse
im sure they do. My opinion is based on my experiences with insurance in the past, specifically a phone that was returned due to water damage, but the water sensors did not trip (clearly damage that voids warranty), and yet it was replaced and i never heard anything from HTC or att regarding the water damage. It was inspected by a low level tech support representative to determine it could be replaced under warranty, the inspection consisted of removing the back panel and checking the water markers and determining the phone wouldnt power on. a more thorough investigation by htc would have revealed water damage, so either they did not inspect it, but rather just junked it, or they did not pursue reimbursement for the phone once they determined it was not warrantable. two different comanies, two different problems, but same concept. Just because its not warrantable, doesnt mean it wont be replaced under warranty. I would never suggest someone rely on this happening of course, just pointing out that it DOES happen.

Warranty claims are handled by the carrier. If the phone is deemed to be abused/damaged/hacked during the replacement process, you will be billed for the replacement handset's cost. If they don't find the cause during this process, the phone is grouped according to the level of damage and sent off to be refurbished/parted out/recycled, and you are in the clear.
The insurance process is handled by a third party, and covers pretty much ANYTHING that you could do to your phone. They don't care what you've done to it, because by that time you've already paid for the refurbished replacement via your monthly fee & deductible.
That being said.. I'm not encouraging anyone to commit fraud, nor do I guarantee results, but I work in the industry and have a lot of experience with thes issues. IMO, if you're trying to get a warranty replacement for your bricked phone, you're abusing the system. You knew what you were getting into when you started flashing/hacking/modding, and therefore the problem is clearly not a 'manufacturer's defect', which is what warranties cover.
Insurance on the other hand, is there to cover anything. If you're allowed to plunge your phone into the toilet, or toss it out of a moving vehicle, and still get a replacement, then flashing & bricking are certainly deserving of coverage as well. I have a feeling with all these manufacturers releasing unlocked bootloaders we'll see some more fine print added to our policies in the near future.
Just my experience & 2 cents. Personally i'm waiting for the official GB att release, because at least then when I unlock my phone I'll be doing it with the blessing (and testing) of the manufacturer, and therefore much less likely to screw myself with an incompatible version of GB

zoso28 said:
Personally i'm waiting for the official GB att release, because at least then when I unlock my phone I'll be doing it with the blessing (and testing) of the manufacturer, and therefore much less likely to screw myself with an incompatible version of GB
Click to expand...
Click to collapse
Not to mention the 30+ threads at the moment with people complaining about problems with their Hong Kong 2.3.4 build, and looking for solutions!

CaelanT said:
Not to mention the 30+ threads at the moment with people complaining about problems with their Hong Kong 2.3.4 build, and looking for solutions!
Click to expand...
Click to collapse
Exactly!! I'm just beginning to learn about android development and definitely not ready for such an experimental build. It amazes me how many people are willing to mess with their ROMs without knowing what they're doing. I'm taking the time to read everything I can find on here before I start experimenting with adb/rsd/fastboot/etc.. Hopefully i'll be ready to go when the official build is released.

zoso28 said:
Exactly!! I'm just beginning to learn about android development and definitely not ready for such an experimental build. It amazes me how many people are willing to mess with their ROMs without knowing what they're doing. I'm taking the time to read everything I can find on here before I start experimenting with adb/rsd/fastboot/etc.. Hopefully i'll be ready to go when the official build is released.
Click to expand...
Click to collapse
One can always flash back to 4.1.8.3. Are you willing to mess with CWM on Froyo?

[Q] Can Google tell if device rooted remotely?

Hi all,
I just got off the phone with Google support... I phoned them because my nexus definitely has heat issues when I fire up need for speed it gets like a furnace...
When I was on the phone though they told me the warranty was void as it had been rooted (<3 TB)... how can they tell?
Does this mean my nexus is permanently ear marked?
Thanks.

Did they ask you to read out any info from the about screen?

juDGEY2k10 said:
Did they ask you to read out any info from the about screen?
Click to expand...
Click to collapse
Serial number...
But surely they can't just remote onto device like that. probably in the T&C. FML.

dont know mate was it new when u got it?
If not just tell them nope i dont know what your talking about, root wtf is root???

juDGEY2k10 said:
dont know mate was it new when u got it?
If not just tell them nope i dont know what your talking about, root wtf is root???
Click to expand...
Click to collapse
Yeah brand new. Straight from Gplay.
That's exactly what I did... still wouldn't process repair or anything sent me Samsung contact details for out of warranty repair. :S

Keep calling mate say they are wrong, keep at it mate just say i want to talk to a manager bla bla, keep pushing them

That's really strange. If they don't budge then contact Samsung directly using the contact info in the warranty that shipped with the phone for a warranty repair or replacement.

problaze said:
Yeah brand new. Straight from Gplay.
That's exactly what I did... still wouldn't process repair or anything sent me Samsung contact details for out of warranty repair. :S
Click to expand...
Click to collapse
I'm new to all this stuff so PLEASE do not do anything based on my flimsy idea, ... just thought it might help send you down a different thought/investigative path.
I installed a toolkit that had a re-lock and un-root option thinking that if I ever got into a similar warranty situation, I would just kinda go "backwards in time" and after using TWRP to backup my tablet, do a full factory wipe, and re-lock then un-root (or whichever comes first) THEN report the problem.:fingers-crossed:
You may have let the cat out of the bag by calling first though
It seems you need to find out how they know,erase the evidence,re-lock un-root and then as juDGEY2k10 says- DENY DENY DENY- you know, like "Dexter" does:laugh: .
But wada I know. Keep us posted on your progress.

Im no expert but I don't see how they can tell unless when you get new apps or update apps from the play store they pulling information from the units. Hopefully they arent doing that.
G●Note~2 {Jedi X5}

I have never seen root voiding warranty of a nexus device before, even though it says so.
I've noticed their bug report tool, built in, attempts to call su, so perhaps they do check now.
I'd prefer to see a root method where the app hides the binary under a unique name so they can't call it to find out.
Sent from my GT-I9300 using Tapatalk 2

If Google is doing that, hopefully they won't share that info with manufacturers.
G●Note~2 {Jedi X5}

problaze said:
Hi all,
I just got off the phone with Google support... I phoned them because my nexus definitely has heat issues when I fire up need for speed it gets like a furnace...
When I was on the phone though they told me the warranty was void as it had been rooted (<3 TB)... how can they tell?
Does this mean my nexus is permanently ear marked?
Thanks.
Click to expand...
Click to collapse
Let's assume what the OP is saying is true, which it probably isn't. Many states provide additional consumer protection, even if there was a clause in the warranty which reduces your rights. (There is no clause which explicitly removes your right to root in the Nexus 10 warranty, but IANAL.)
The manufacturer is still responsible for physical defects.
However, I cannot imagine that someone would call Google and receive that answer and not be angry, mentioning the rep by name he talked to, and asking to make sure that the rep's claim was accurate.
Perhaps the OP is not telling the whole story, (e.g. he called and proclaimed that he was an advanced user, gave the rep attitude, rep came back with "oh yeah well you're rooted, we don't have to support you". Anyone who has done customer service or help desk knows what I'm talking about.) or just plain making the whole thing up, since I have never heard of any company refusing to service a rooted device unless there was a problem user with multiple returns.
I do acknowledge that the OP may not be full of crap, but if that is the case, I strongly advise OP not to take what a single rep said as gospel and keep calling back and asking for a supervisor until it's resolved.
However, there's another issue:
If the OP rooted, installed a custom kernel, found his device ran too hot, then called Google complaining without first reverting to stock and testing to make sure it wasn't the custom kernel causing the overheating, the OP's brain is the thing needing a warranty exchange.

I contacted Google about my nexus 10 dropping wifi randomly a few days ago.
The guy who I spoke to was quite nice and told me to do a factory reset. I told him I had already done that and I had also tried CM10, AOKP as some people have said that fixes any kernel/rom issues and I said the problem remains on everything I do so it had to be the device.
I was offered a refund outside the 15 day period and I chose a replacement which was shipped today.
If I spoke to someone who said that they couldn't help me because I'm rooted, I'd hang up and try again. Although if you are having problems a full restore to stock will be helpful if you ring up and speak to them.

ZanshinG1 said:
Let's assume what the OP is saying is true, which it probably isn't. Many states provide additional consumer protection, even if there was a clause in the warranty which reduces your rights. (There is no clause which explicitly removes your right to root in the Nexus 10 warranty, but IANAL.)
The manufacturer is still responsible for physical defects.
However, I cannot imagine that someone would call Google and receive that answer and not be angry, mentioning the rep by name he talked to, and asking to make sure that the rep's claim was accurate.
Perhaps the OP is not telling the whole story, (e.g. he called and proclaimed that he was an advanced user, gave the rep attitude, rep came back with "oh yeah well you're rooted, we don't have to support you". Anyone who has done customer service or help desk knows what I'm talking about.) or just plain making the whole thing up, since I have never heard of any company refusing to service a rooted device unless there was a problem user with multiple returns.
I do acknowledge that the OP may not be full of crap, but if that is the case, I strongly advise OP not to take what a single rep said as gospel and keep calling back and asking for a supervisor until it's resolved.
However, there's another issue:
If the OP rooted, installed a custom kernel, found his device ran too hot, then called Google complaining without first reverting to stock and testing to make sure it wasn't the custom kernel causing the overheating, the OP's brain is the thing needing a warranty exchange.
Click to expand...
Click to collapse
I totally understand where you're coming from.
I used to work behind the genius bar so I know what you're getting at.
The full story is that I phoned up first and arranged a swap but realised that they would send to university address and not home phoned back again to change address and that's when the guy tried some extra steps with me and then asked for serial etc, you know the rest.
I get his word isn't stone but was shocked that they could definitely tell, wanted to share exp.
In all honesty the reason I didn't act rationally was that he ultimately called me out and I was major surprised since I'd never heard of anything similar before aka remote sense of root.
This is literally the third android device I've had and I'm only getting into the scene now, there's no custom kernel on my nexus. I run it stock.
FYI this was UK. Oh and CS didn't deny service they just referred me to someone else. Will try again post hols.
Hope explains!
?? Has anyone else experienced major heat on NFS:MW ??

alias_neo said:
I'd prefer to see a root method where the app hides the binary under a unique name so they can't call it to find out.
Click to expand...
Click to collapse
you mean like the way a rootkit does it

?? Has anyone else experienced major heat on NFS:MW ??
Mine do to and lag in a lot of games because of throttling

Root and insurance: my experience

This covers an issue that I've seen asked time and time again with no definitive answer given.
I suppose this isn't an answer but merely my experience
Last monday my note 2 fell out of my pocket and my screen subsequently was destroyed, not just cracked but full on chunks of glass missing. I am insured by Halifax who like most banks in the UK (Barclays, TSB, Nationwide, co-op etc) use Lifestyle Services Group Limited (LSG) to deal with their insurance.
My device was rooted with CM11 and I was using CWM recovery, after searching for an answer to would this affect my insurance, i found nothing that really helped me with LSG, in fact the only things I did find were 100s of general complaints about them trying to get around doing repairs, they didn't fill me with hope.
so biting the bullet I notified them of the damage, made a Nandroid, did a factory reset and sent my phone away on Tuesday :fingers-crossed: .
On Wednesday evening I received an email saying my phone was being returned to me and a tracking number but nothing else. Upon arrival I found a letter saying my "device has been repaired and updated" and a brand new Note 2
after installing CWM again and restoring my phone is perfect again. So if anyone out there has similar concerns to those that I had about root and insurance I hope this gives you a bit of peace of mind. :highfive:

mbloomer04 said:
This covers an issue that I've seen asked time and time again with no definitive answer given.
I suppose this isn't an answer but merely my experience
Last monday my note 2 fell out of my pocket and my screen subsequently was destroyed, not just cracked but full on chunks of glass missing. I am insured by Halifax who like most banks in the UK (Barclays, TSB, Nationwide, co-op etc) use Lifestyle Services Group Limited (LSG) to deal with their insurance.
My device was rooted with CM11 and I was using CWM recovery, after searching for an answer to would this affect my insurance, i found nothing that really helped me with LSG, in fact the only things I did find were 100s of general complaints about them trying to get around doing repairs, they didn't fill me with hope.
so biting the bullet I notified them of the damage, made a Nandroid, did a factory reset and sent my phone away on Tuesday :fingers-crossed: .
On Wednesday evening I received an email saying my phone was being returned to me and a tracking number but nothing else. Upon arrival I found a letter saying my "device has been repaired and updated" and a brand new Note 2
after installing CWM again and restoring my phone is perfect again. So if anyone out there has similar concerns to those that I had about root and insurance I hope this gives you a bit of peace of mind. :highfive:
Click to expand...
Click to collapse
Does the Note 2 have KNOX? and what did you flash counter say?

dangerousbadger said:
Does the Note 2 have KNOX? and what did you flash counter say?
Click to expand...
Click to collapse
Stock android on the note 2 does have KNOX yes, however obviously when I rooted and installed CM11 it no longer did.
the flash counter changed to 1
The phone I received back from them was back on stock android, and the flash counter read as 0 again

dangerousbadger said:
Does the Note 2 have KNOX? and what did you flash counter say?
Click to expand...
Click to collapse
so aye they did repair it even with my flash counter having been tripped

I imagine that it was an easy decision for them to make because the screen breakage had nothing to do with whether the phone was rooted or not. If they'd refuse to repair it and you'd taken them on, it would have been very hard for them to defend themselves.
However, if your phone dies because of a software/hardware issue and it's rooted and/or has a custom ROM installed, they might argue that your actions (i.e. rooting, etc) led to the device failing. And they might then enforce their "warranty void" policy. So people just need to be careful in that situation, and not be too disappointed if their claim is rejected.
Glad you had good luck tho!

apuntigam said:
I imagine that it was an easy decision for them to make because the screen breakage had nothing to do with whether the phone was rooted or not. If they'd refuse to repair it and you'd taken them on, it would have been very hard for them to defend themselves.
However, if your phone dies because of a software/hardware issue and it's rooted and/or has a custom ROM installed, they might argue that your actions (i.e. rooting, etc) led to the device failing. And they might then enforce their "warranty void" policy. So people just need to be careful in that situation, and not be too disappointed if their claim is rejected.
Glad you had good luck tho!
Click to expand...
Click to collapse
aye, the whole warranty void issue was where I believed they could turn me down.
in the past I've claimed on the warranty twice (still using stock) and both times have only at the last minute remembered to swap the back panel to the original as the one at the time had a palm stone wireless charging plate in it which I'm sure would have resulted in them sending it back untouched