If you root your nexus via the "official" way, you're screwed if you have a hardware failure, because the warranty is null and void. We need to figure out a way to root that is similar to how we rooted the MyTouch and G1.
My suspicion is that the "official" unlock isn't in the spl. I think it is more like a sim unlock.
I think we should just leave it alone and learn how to root the G1 way. That way, if we have a hardware problem, we can revert the dang phone to factory specs.
Any ideas? I think a gold card may be a could place to start.
This message was deleted by its author
Given that Swetland has said the HTC should honour the hardware warranty if the flaw isn't causable by rooting, and even suggested that you message him if you get such things refused I think that most of us are pretty happy with that, certainly many of the main devs are.
Not that I'm suggesting you shouldn't do what you want to, just pointing out that you're unlikely to get the support that the G1 root had
This message was deleted by its author
t4tav said:
Plus, I would like to see a "non" official way. That way we are still not giving up our warranty.
Click to expand...
Click to collapse
It's been stated the HTC should honor the Hardware warranty.
If you are rooting, for any reason whatsoever, you are voiding your software warranty. And that's correct - you are well off the reservation and you should only root if you are aware of the risks and know what you are doing.
There is absolutely no reason you should expect to have your software warranty honored after you root.
While I can understand the desire for a sneaky backdoor root, it's really not to our advantage for such a thing to exist. Google managed to shipped this phone roootable out of the box. That is simply wonderful for the various people producing ROMs, it makes the phone a blast for hackers, it will spurn some serious innovation (and has done so already.) All good.
If people start backdoor rooting and making warranty claims, all of that may be spoiled and we may end up with a Nexus Two that is simply completely locked down.
Not good.
This message was deleted by its author
DebauchedSloth said:
It's been stated the HTC should honor the Hardware warranty.
If you are rooting, for any reason whatsoever, you are voiding your software warranty. And that's correct - you are well off the reservation and you should only root if you are aware of the risks and know what you are doing.
There is absolutely no reason you should expect to have your software warranty honored after you root.
While I can understand the desire for a sneaky backdoor root, it's really not to our advantage for such a thing to exist. Google managed to shipped this phone roootable out of the box. That is simply wonderful for the various people producing ROMs, it makes the phone a blast for hackers, it will spurn some serious innovation (and has done so already.) All good.
If people start backdoor rooting and making warranty claims, all of that may be spoiled and we may end up with a Nexus Two that is simply completely locked down.
Not good.
Click to expand...
Click to collapse
I completely agree with you. Look at the Droid Eris, for as long as it has been out, they are just starting to get an exploit that is working. They do not even have root yet.
I personally think that the people that most want to root without an unlocked bootloader are the people that will mess their phone by not understanding what they are doing to it fully. As stated above, you should be able to get your phone fixed if you have obvious defects that are not related to software.
While I think it would be interesting to have an alternative method to rooting, at the same time, I would view it as detrimental to what is trying to be done with this phone.
Just my small $0.01 (its not a full rant, trust me)
This message was deleted by its author
at first i thought it just a software, in any platform if you do anything to the software it will be ok, and the warranty still available like iphone or WM devices.
we need do small hacking to make this work, i don't know why xda-developer doesn't have any hacker, it should be easy.
This message was deleted by its author
t4tav said:
I think I got that :/
(Removed my idea - We need a passimg.nbh)
However, I am really holding out on someone from HTC or Google saying that all hardware faults will be covered even if the bootloader is unlocked.
As soon as that happens I will root my nexus
Edit - The other reason for (personally) look for another root method is that if you unlock the bootloader now, It wipes the system, all the apps and all the settings. I to be honest, I can't really be bothered to reinstall all of them, considering that the Market doesn't seem to track what I install/un-install.
Click to expand...
Click to collapse
This.
Like one of the above posters said everybody saying theres no need because they SHOULD replace hardware defects...I called HTC (haven't rooted) and asked them if I can repair hardware defects on a unlocked bootloader. The response "There is no warrenty if you have unlocked the bootloader."
This message was deleted by its author
t4tav said:
I think I got that :/
(Removed my idea - We need a passimg.nbh)
However, I am really holding out on someone from HTC or Google saying that all hardware faults will be covered even if the bootloader is unlocked.
As soon as that happens I will root my nexus
Edit - The other reason for (personally) look for another root method is that if you unlock the bootloader now, It wipes the system, all the apps and all the settings. I to be honest, I can't really be bothered to reinstall all of them, considering that the Market doesn't seem to track what I install/un-install.
Click to expand...
Click to collapse
if you are afraid to wipe then you shouldnt root your phone. i garranty that you WILL be wiping your phone many times in the future. i must have wiped my g1 more than 30 times and the nexus one 6 or 7 times already. but dont worry, there are always free backup apps like titanium backup
The Nexus is not like the G1 or mytouch in any way to root the Nexus is Different than any Htc Phone. The Porcessor is not the mt3g or g1. so to try to root it like the mytouch or g1 may bring more problems. Note No mather how you root it the warranty is still void unless you unroot it to send it back in.
This message was deleted by its author
t4tav said:
I must of wiped my G1 atleast 20+ times. I've also flashed around 20 Custom roms too (Since JF Rom's were all the rage).
I've found that mybackup works well. So I may purchase that. My Nexus is now happily rooted and running extremely fast
I'm not scared of wiping, it's just sometimes it can get sore
Click to expand...
Click to collapse
ive used backup for root users for ages(it seems like it). i seriously recommend you try titanium backup, it backs private apps up also.
simms22 said:
ive used backup for root users for ages(it seems like it). i seriously recommend you try titanium backup, it backs private apps up also.
Click to expand...
Click to collapse
Titanium seems to work well
Anyways, Let's move this topic back on track
That's my motivation
kingskidd268 said:
The Nexus is not like the G1 or mytouch in any way to root the Nexus is Different than any Htc Phone. The Porcessor is not the mt3g or g1. so to try to root it like the mytouch or g1 may bring more problems. Note No mather how you root it the warranty is still void unless you unroot it to send it back in.
Click to expand...
Click to collapse
We should have a way to "unroot."
I can see the other side to this too. If some yahoo roots their phone, then overclocks it to 2ghz or something and fries it... that SHOULDN'T be covered by warranty.
On the other hand, if I'm running one of cyanogen's roms and the speaker goes out, it should be covered.
Personally, if I fried a ROM because I overclocked it or something like that, I would NEVER send it in for warranty work. I would only send it in if the problem was clearly the manufacturer's.
Just my 2 cents
t4tav said:
Edit - The other reason for (personally) look for another root method is that if you unlock the bootloader now, It wipes the system, all the apps and all the settings. I to be honest, I can't really be bothered to reinstall all of them, considering that the Market doesn't seem to track what I install/un-install.
Click to expand...
Click to collapse
To be very clear, this behavior (data wipe on unlock) is intentional. Otherwise if your phone is lost or stolen, it would be trivial for somebody to unlock it, boot a custom kernel, and copy your contacts, email, etc from internal flash.
The Market should restore your installed apps automatically, and Settings Backup should be able to restore the bulk of your settings.
This message was deleted by its author
Related
Hey Guys, I'm new to Android. Had my G2 Touch on T-mobile for less than 7 days, not had time to play with it as such but so far so good.
I've read post after post in regard to 'rooting' It's clear that the advantages far out weighs the disadvantages but I would like to know what the risks are.
Apart from the odd 'lag' my phone seems to be fine. My main disappointment is not being able to store apps on the SD card and the other obvious one is the lack of Bluetooth capabilities. I believe rooting would correct this?
So far I have a perfect running phone. My concern is if I decide to root the phone, are there any risks and can I unroot afterwards
Thanks in advance and any feedback would be appreciated.
As far as I've read. (Havent rooted mine yet)
That if you don't do it correctly, you risk bricking your phone.
Ofc. you lose your warrenty.
But I think there is some good things out there for rooted phones. Market hack for people like me, unable to access pay-apps. And Apps2SD....
Siggaard said:
As far as I've read. (Havent rooted mine yet)
That if you don't do it correctly, you risk bricking your phone.
Ofc. you lose your warrenty.
But I think there is some good things out there for rooted phones. Market hack for people like me, unable to access pay-apps. And Apps2SD....
Click to expand...
Click to collapse
Thanks Siggaard,
I'll hold out for now and wait for the next software update.
To get to the point, people DON'T UPDATE YOUR VIBRANTS and T-MOBILE HANDLES THE ISSUE HORRIBLY! Obviously this is not a universal problem, but if you do happen to be one of the lucky ones that bricks their phone with the update there is no saving it (at least with the help of T-mobile).
I just got off of the phone with tech support and they were less than helpful. After the regular punching in numbers, talking to two different people, and trying to re-boots that everyone with half a brain have tried, they informed me that they would replace the phone but I had to PAY for shipping. While I realize this is a normal policy when it comes to random malfunctions, which may or may not have been the users fault, this is absolutely ridiculous when the problem is 100% their fault. Seriously, T-mobile ships a top of the line phone that has some major flaws and inactivated software (media hub), then breaks the phone with it's official update, and somehow this is MY responsibility to pay to get fixed? The rep even asked if I at this point wanted to add insurance so next time I wouldn't have to pay for shipping and if I wanted to pay extra for expedited shipping! They were trying to make an add-on sale while fixing an issue THEY caused!
That's not even the end of it, because I was so irritated they sent me to a "loyalty specialist" (who sounded like a used car salesman). He rambled on about how he would waive the shipping fee (he made it sound like he just saved my first born child). I told him I appreciated that but it didn't fix the fact that T-Mobile was not handling the issue well. When a large number of phones break from an issue originating from the provider they should either 1) have re-furbished phones (or even set aside new phones if necessary) to replace these broken phones as they come up or 2) offer free over night shipping of the replacement phone. He told me that these options were too expensive for T-Mobile, and that if I like I could sign up for either of their two insurance plans, as they would allow me to do an in-store replacement (he later noted that one of them was only available within the first 14 days of owning the phone...). I couldn't believe they were trying to another add-on sale! The best part being, I later called around to all my local T-Mobile owned stores and none of them have the Vibrant available for in-store replacement (and never have).
So the Cliff-Notes of my rant:
1) DON'T UPDATE YOUR VIBRANT
2) If you did brick your phone, make sure to complain and they should refund the ridiculous shipping charge
3) If you don't own a Vibrant and are thinking about it consider the following (Don't let it stop you, just consider it):
- Still on 2.1, when Nexus One has been on 2.2 for months (and the Galaxy S 2.2 official ROM has been leaked so it does exist in some form.) => Meaning updates are super scarce and extremely late.
- T-Mobile is selling a good phone with many flaws, and their first attempt to fix it bricked many phones (do a google search I am not the only one).
- While it may be better than other companies, T-Mobiles customer service is FAR from flawless
P.S. My phone was completely stock (so please don't mention how I did this with a lag fix, etc.). I waited at least 15 mins before I pulled the battery, before which I had noted the T-Mobile sound starting without the animation (seems like a timing issue or something). And finally, I realize this is a duplicate post to many others but I want people to find this info (not be at the bottom of a really long thread) to get the word out how T-Mobile deals with their errors.
I hate when people mess with their phones then get angry at a company for "breaking" their phone. Im running stock rom with root and also got bricked, but, I manned up and knew I was in the wrong and accepted what happened. I didn't put the blame on TMo, because completely untouched vibrants that I was aware of had no issues with this OTA. If you added functionality to it after the fact that it wasn't originally on there before when you initially purchased it; then its YOUR fault that it bricked, NOT T-mobiles. Take some responsibility and stop crying.
Had the same problem but this is a pretty fix using Odin.
If you install an update from an OTA T-Mobile should be held responsible
I don't know about you guys but when you have been a customer for 10+ years, T-Mobile will pretty much suck your balls.
Either way, if you guys rooted it, then that takes the fault from T-Mobile to you. You changed the phone. The update was designed for a pristine un-edited Samsung Vibrant, if you changed anything in the system by rooting or flashing it is your fault for changing the equation. T-Mobile is NOT at fault for your actions.
Yeah why warranty the phone when you can just ODIN and fix it yourself? Do a xda search. If you're gonna use xda to complain at least use it to solve your own problems as well. Unless your phone is hardware locked it is 100 % fixable.
Sent from my SGH-T959 using XDA App
starkiller86 said:
I hate when people mess with their phones then get angry at a company for "breaking" their phone. Im running stock rom with root and also got bricked, but, I manned up and knew I was in the wrong and accepted what happened. I didn't put the blame on TMo, because completely untouched vibrants that I was aware of had no issues with this OTA. If you added functionality to it after the fact that it wasn't originally on there before when you initially purchased it; then its YOUR fault that it bricked, NOT T-mobiles. Take some responsibility and stop crying.
Click to expand...
Click to collapse
P.S. My phone was completely stock (so please don't mention how I did this with a lag fix, etc.). I waited at least 15 mins before I pulled the battery, before which I had noted the T-Mobile sound starting without the animation (seems like a timing issue or something). And finally, I realize this is a duplicate post to many others but I want people to find this info (not be at the bottom of a really long thread) to get the word out how T-Mobile deals with their errors
Did you not read that part?
I bricked two stock Vibrants with the update. The second one failed during Mini-Kies update and was hardware locked.
It is a known issue according to the Tech guy that I spoke to while getting my replacement.
First phone wouldn't power on after failure, second phone was hardware locked so un-fixable.
No, no.
This happened to me, I had a rooted phone I had uninstalled the inflight internet, etc on it and hadn't overclocked or anything like that. Phone kills itself. I went to the tmo store and they only make you pay for shipping if you take the overnight option.
PROTIP - DON'T ASK FOR EXTRA SPEEDY SHIPPING AND THEY'LL PAY FOR IT.
so i guess we are just SOL for the data on the phone? I just lost an entire vacation of pictures. I had not had a chance to root this phone either. this is ****ing awesome.
dechire said:
so i guess we are just SOL for the data on the phone? I just lost an entire vacation of pictures. I had not had a chance to root this phone either. this is ****ing awesome.
Click to expand...
Click to collapse
I guess this is just an example of "store your pictures on the external SD card"
Then if you brick it you can still get your pictures back ....
watcher64 said:
I guess this is just an example of "store your pictures on the external SD card"
Then if you brick it you can still get your pictures back ....
Click to expand...
Click to collapse
Word. That's one of the first things I did when I got the phone and was playing with the features. Switched it from phone storage to memory card.
Sorry to hear you lost photos.
Protip: Pay the damn overnight shipping fee...it'll be deducted from your bill (flex pay) which makes it free: )
Sent from my SGH-T959 using XDA App
Here is the business side
If I am T mobile every time some person has a problem and I offered free shipping, the Every moron would be shipping the device back for Any problem. Way way costly, so that is not going to happen. If you Really believe the phone is factory defective then, pay the shipping and move on. If you messed with it at all then the burden to resolve is yours and be honest about that. Remember the reason people are in here is to customize the phone and improve it. Like the XDA mantra sez.......... It is not just the result... but the journey....
Like one of the other posts stated:
If you rooted it, then that takes the fault from T-Mobile to you. You changed the phone. The update was designed for a pristine un-edited Samsung Vibrant, if you changed anything in the system by rooting or flashing it is your fault for changing the equation. T-Mobile is NOT at fault for your actions.
Gr8gorilla said:
First phone wouldn't power on after failure, second phone was hardware locked so un-fixable.
Click to expand...
Click to collapse
There is a hardware lock fix now, you really should flash that before you do anything else. Yeah, you run the risk of bricking with the hardware unlock, but it's probably a safer bet than flashing away.
dechire said:
so i guess we are just SOL for the data on the phone? I just lost an entire vacation of pictures. I had not had a chance to root this phone either. this is ****ing awesome.
Click to expand...
Click to collapse
If you Odin it with the JI6 update, you might still be able to get a working system out of it. Worth a shot to see if you can get it without having to flash to stock first (which will wipe).
With all the time you spent with tech support, you could have found the thread that delineates how to fix your phone and update through odin. Its very easy and, frankly why be on a developers forum when you are not willing to tinker around a bit.
Sent from my SGH-T959 using XDA App
dechire said:
so i guess we are just SOL for the data on the phone? I just lost an entire vacation of pictures. I had not had a chance to root this phone either. this is ****ing awesome.
Click to expand...
Click to collapse
As long as the phone still powers on you can still use ADB Pull and save the data from the /sdcard folder. This update isn't a totally bricking the phone (at least it didn't mine) just making the display and inputs not work. To quote Billy Crystal: "He's only MOSTLY dead"
Odin was really simple to reflash the stock ROM and then I was able to do a nandroid restore from there.
The T-Mobile OTA update left my phone only booting to the vibrant screen, but it was a pretty simple fix with Odin. The hardest part was getting the proper drivers installed in windows!
Mini kies wouldnt even let me update,so I rooted and flashed bionix 1.8,works great.**** tmo.
Fyi to the people with hardware lock. I did the update on my gf's phone which was hardware locked and it failed. The phone would only boot to the vibrant screen. The good news is the ota update unlocks the hardware because her phone is able to get into recovery and download mode even thought the update failed. The point is don't worry if ota fail on you because you can just use odin to fix it since it unlocks the download mode.
Sent from my SGH-T959 using XDA App
mr2t32 said:
Fyi to the people with hardware lock. I did the update on my gf's phone which was hardware locked and it failed. The phone would only boot to the vibrant screen. The good news is the ota update unlocks the hardware because her phone is able to get into recovery and download mode even thought the update failed. The point is don't worry if ota fail on you because you can just use odin to fix it since it unlocks the download mode.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
If the update even gets that far...
Great. I, like a dumbass, decided to try and root my new phone without a backup plan. I have had no luck using the XDA video, and now I'm stuck with the "Please select recovery mode in Kies" screen. Kies doesn't recognize it, and I have no way to restore the stock ROM. Is my only option to wait until a stock firmware ROM is released, like it was for sprint?
Based on the information we're currently provided with, I think it'd be safe to say you're screwed for now. Why you would even try to root a device that doesn't currently have any rooting methods is beyond me. You should definitely read up before you try anything you're not sure of.
The only other option you'd have at this point is taking the phone into Verizon, showing them the screen and telling them that this is how it has looked since it came out of the box. Although it's a lie, and you bricked it out of your own neglect, the reps can't really turn you away.
Can you return it?
Sent from my SCH-I605 using xda premium
I did some research, and nobody had any negative things to say about the rooting process, especially with all the videos and forums on it. I searched for how to root the Samsung note 2, versus the model number, which is different for different carriers.
MedicMillan said:
I did some research, and nobody had any negative things to say about the rooting process, especially with all the videos and forums on it. I searched for how to root the Samsung note 2, versus the model number, which is different for different carriers.
Click to expand...
Click to collapse
Every carrier is different. You must be new here.
I am new. I have rooted phones before, but never had this problem. Would it be an option to install a custom rom like Cyanogen until there is a public release of the stock firmware?
MedicMillan said:
I am new. I have rooted phones before, but never had this problem. Would it be an option to install a custom rom like Cyanogen until there is a public release of the stock firmware?
Click to expand...
Click to collapse
You will need to wait until the boot loader is unlocked to flash a rom, only way I can think of.
MedicMillan said:
I am new. I have rooted phones before, but never had this problem. Would it be an option to install a custom rom like Cyanogen until there is a public release of the stock firmware?
Click to expand...
Click to collapse
At this point in time, you can't flash anything, you can't root, and there are no recovery images to return to stock with. You either have to wait it out, or try to exchange it at Verizon.
You can exchange, they will not know the difference
Sent from my SCH-I605 using Tapatalk 2
Just take it to Verizon play dumb and get it replaced. It's within the 14 days so it will be swapped on the spot. They wont/don't care what's wrong with it.
The suggestion of just return it to the store, they won't notice, is a really **** move and I'm not saying that in defense of Verizon. I'm saying it that it is things like that that in the end cause more harm to the end user than good. They up costs and add charges, create obscene policies, etc. It may not negatively impact you immediately, but when multiple people do this all over the country it adds up.
DaRkL3AD3R said:
The suggestion of just return it to the store, they won't notice, is a really **** move and I'm not saying that in defense of Verizon. I'm saying it that it is things like that that in the end cause more harm to the end user than good. They up costs and add charges, create obscene policies, etc. It may not negatively impact you immediately, but when multiple people do this all over the country it adds up.
Click to expand...
Click to collapse
I have to say I agree 100%. If people just used common sense, or read up a bit, situations like these could be entirely avoided.
MedicMillan said:
Great. I, like a dumbass, decided to try and root my new phone without a backup plan. I have had no luck using the XDA video, and now I'm stuck with the "Please select recovery mode in Kies" screen. Kies doesn't recognize it, and I have no way to restore the stock ROM. Is my only option to wait until a stock firmware ROM is released, like it was for sprint?
Click to expand...
Click to collapse
Check the development section. There is a leaked ODIN .tar file that you can flash. It is a prerelease, but at least you will have a functioning phone until a proper root/unlock solution is found.
bork.it.consulting said:
Check the development section. There is a leaked ODIN .tar file that you can flash. It is a prerelease, but at least you will have a functioning phone until a proper root/unlock solution is found.
Click to expand...
Click to collapse
This Odin file fails. It will not flash. Someone was trying to flash it last night with the same screen you are on.
just odin the stock image in the dev section and you will be back up and running...do not I repeat do not anybody try any root methods for the other gn2 variants!
http://samsung-updates.com/device/?id=SCH-I605
if it fails then your screwed until the latest odin image is release, which im sure wont be too long.
Nit3mare said:
I have to say I agree 100%. If people just used common sense, or read up a bit, situations like these could be entirely avoided.
Click to expand...
Click to collapse
I'm not saying that everyone should go flash happy, attempt to root without knowing what they are doing destroy their phones and take them back to Verizon then rinse and repeat the process. But there have to be a few that are a tempting to get root for everyone else there is bound to be some hard bricks. Should they be out 700, and that's kinda harsh.
Check out this link for a fixed brick....
http://forum.xda-developers.com/showthread.php?p=34862234#post34862234
mrlaigle said:
I'm not saying that everyone should go flash happy, attempt to root without knowing what they are doing destroy their phones and take them back to Verizon then rinse and repeat the process. But there have to be a few that are a tempting to get root for everyone else there is bound to be some hard bricks. Should they be out 700, and that's kinda harsh.
Click to expand...
Click to collapse
But with a little reading in the correct forum, people could avoid owning a $700 paperweight. It's really not that difficult, and any issues that arise from lack of research are due to their own ignorance. I can't feel sympathy for anyone who flashes blindly.
Nit3mare said:
But with a little reading in the correct forum, people could avoid owning a $700 paperweight. It's really not that difficult, and any issues that arise from lack of research are due to their own ignorance. I can't feel sympathy for anyone who flashes blindly.
Click to expand...
Click to collapse
I'm not disagreeing with you. If you do not know what you are doing or if this is your first time you shouldn't be attempting to root an un rooted device. But there will always be those guinea pigs...
Sent from my SCH-I605 using Tapatalk 2
This is exactly the reason why everyone else who follows commense is punished with locked bootloader.
IT'S A TRAP!
Well I just found out the hard way that VZW is even more evil than I thought.
Called about my G3 because of audio issue with the headphone jack, seeking an RMA.
Without my permission verizon ran some remote diagnosis on my phone and discovered root, right while I was on the call. Tier 2 support did this by the way.
Not sure how... I froze all the VZW bloat I could find in titanium.
Just wanted to let you guys know to watch your back. I'm not sure exactly when verizon got wind of my root. Whether it was right there while I was on call or the minute I rooted.
Verizon is literally the devil
Sent from my VS985 4G using XDA Free mobile app
What did they say once they discovered root on your phone? Just denied the RMA? Would they let you make an insurance claim at least?
The rep responded "after running diagnostics on your device I see your phone is rooted so your warranty is invalid"
Then he preceeded to try and give me instructions to call LG and get the flash tool to return to stock.
My issue with the audio jack is obviously a HW issue and not an issue with software/root
Sent from my VS985 4G using XDA Free mobile app
Always put your phone in Airplane Mode if you have to call them. If they say they need the phone turned on to run diagnostics, REFUSE, and tell them that you don't consent, or tell them that the phone is not near you, then continue talking and tell them that you're NOT calling about a software but hardware issue and there's no reason that they need to run a Software Diagnostic.
Someone else mentioned the same thing however from what I understand their system polls your phone every few hours so that may not help. Even if the phone was offline the system may still show root status regardless of the phones current state.
Couldn't hurt though...
Either way it's a little to late for me. I just hope that someone sees this thread before calling only to get a big fat middle finger from VZW.
Flash to stock and wait a bit on official software to make sure Verizon's system shows official software.
Sent from my VS985 4G using XDA Free mobile app
I woulda said root (software) has nothing to do with audio jack (hardware). Not that it wouldve really gotten you anywhere anyway.
Either way, Verizon doesnt really cover hardware warranty, they just send the phone over to LG, which the rep directed to you anyway. So sounds like youre gonna have to contact LG directly.
Or maybe you even get a do-over. You could flash back everything to stock, and then just walk into store and try the same thing. The reps at the store arent nearly as sharp as the phone reps.
Good to know tho, thx for the heads up!
Yeah but I got the phone on the VZW website on a black Friday deal. So that would leave me without a phone. I'm assuming they would have to ship it back and would not just exchange it on the spot.
Couldn't hurt though I call tomorrow and ask if they will swap it on the spot.
Sent from my VS985 4G using XDA Free mobile app
I had same exact audio jack prob on G2. They didnt take my phone or anything, they shipped me a new one and i sent back the old one afterwards. There's something like a 30 day grace period to ship your phone back before they charge you for it. Was easy peasy
---------- Post added at 06:01 PM ---------- Previous post was at 05:58 PM ----------
Oh and doesnt matter where you bought the phone , its a Verizon phone and youre a Verizon customer so they will help you no matter what. That G2 was from Ebay. If its under warranty by LG, its under warranty. Again, Verizon just assists yoh with the warranty as a customer service. The money comes out of LG's pocket, not theirs.
Yeah but their service department knows I have root. I'm pretty sure they will just tell me to screw off if I go to swap the phone. But it couldn't hurt to try. Thanks for the info.
Sent from my VS985 4G using XDA Free mobile app
True but you never know, give it a shot and let us know.
---------- Post added at 06:58 PM ---------- Previous post was at 06:36 PM ----------
Check out this article from Droid Life. Verizon actually saw tge article and made some clarifications in regards to root, warranty and what they consider void or not void.
Verizon Begins Charging Full Price of Warranty Phones if Rooted? (Updated)
What exactly should happen if you were to root your phone, play around with ROMs/hacks/etc., somehow manage to break it, and then send it in to Verizon for a warranty replacement? Should you be allowed to get a replacement or not? According to reports, you can get a replacement, but the rooting of your phone voids any warranty you had and gives Verizon permission to charge you for a new one if they determine that your broken phone was tampered with.
Our buddy @P3droid has apparently heard from a couple of friends who have run into the scenario that we described above and then been slapped with a pretty hefty and unannounced bill. Fair or unfair?
I’ll just say this – we’ve known that rooting your device voids your warranty since well back in the original DROID days, so it makes sense that Verizon would do this. As unpopular as this may sound, I can’t fault Big Red for going this route. If you decide to take your phone out of its original factory status, tinker with its guts, and break something, it shouldn’t be their responsibility to take care of you.
With that said though, a broken volume rocker, faulty screen, etc. has nothing do with rooting, so I’d hate to see someone get charged for something that they didn’t cause even if they decided to root. It’s an interesting topic, and one that I would love to hear all your opinions on.
Update: Our friends at Verizon saw this post and wanted to reach out to clarify everything immediately. First up, is the fact that their policy says absolutely nothing about checking for root on devices. When a phone is received, a phone is checked for three things and that definitely isn’t one of them. They check to see if the box that the device was sent in is damaged, if the outside of the phone looks awful, and if it powers on – satisfy all of those and they move on to the next phone. So basically, these reports of being charged for a rooted phone simply mean that these people were sending in garbage phone with defects.
So…sound off!
http://www.droid-life.com/2011/06/1...ging-full-price-of-warranty-phones-if-rooted/
Click to expand...
Click to collapse
I would take the word of a Verizon PR Rep over some call center dweeb. Just b/c he works there doesnt mean he's rhe end all be all.
I'll tell you what's up there. Worked for the company for a while and encountered this. Rooting does not really void a warranty, as the warehouse does not check for root, they just check if a phone has physical damage to it. Now if your phone is rooted, reps are advised to tell you that it can't be supported any longer by VZW. But that could happen with any company. If you modify a LG TV, LG might not want to support it either. If you are just rooted, it might be one thing, but different roms MIGHT affect different things. Yours probably is the hardware issue though. If you haven't been already taken care of, if you call back in, just let a rep know that you don't want anyone to remotely access your phone. That is not supposed to be done without your permission. I have had a few phones replaced under warranty that had been rooted. If nothing else, just return a phone to stock. But if you don't want to worry about any of that, just turn your phone off, and tell them that you tried to accept the most recent 12B update, and now your phone won't fully boot up, and leave the phone powered off the whole time.
subhelix said:
I'll tell you what's up there. Worked for the company for a while and encountered this. Rooting does not really void a warranty, as the warehouse does not check for root, they just check if a phone has physical damage to it. Now if your phone is rooted, reps are advised to tell you that it can't be supported any longer by VZW. But that could happen with any company. If you modify a LG TV, LG might not want to support it either. If you are just rooted, it might be one thing, but different roms MIGHT affect different things. Yours probably is the hardware issue though. If you haven't been already taken care of, if you call back in, just let a rep know that you don't want anyone to remotely access your phone. That is not supposed to be done without your permission. I have had a few phones replaced under warranty that had been rooted. If nothing else, just return a phone to stock. But if you don't want to worry about any of that, just turn your phone off, and tell them that you tried to accept the most recent 12B update, and now your phone won't fully boot up, and leave the phone powered off the whole time.
Click to expand...
Click to collapse
I would assume that because I have already been caught that they have the voided warranty on record... or is this not the case?
I thought that once they caught you, thats it, the jig is up and they put a note on your account that the phones warranty is void.
I think I might know what happened. I have noticed that when I first rooted my G3 (3 Days Ago) that the Verizon Mobile app asked for root permissions immediately upon rebooting for the phone. I accidentally gave it permissions and it went on about its ways. I later removed the permission and didn't worry about it any longer. Not thinking anything about it I think that once you give the Verizon app permission it will figure out your rooted and sync up with your account (which it does automatically during the setup process) by your phone number tied to the Sim card. I think that's exactly how they knew, and I think a warning goes out and is posted on the account phone number saying its a rooted device.
Possibility? Let me know.
Wow, now that I think of it, you might be right!
Same thing happened to me a few days ago. I had already granted it access before i even realized it was the actual Verizon app. Shrugged my shoulders after I realized it but thought it had something to do with the actual ROM im running (Jasmine 3.0).
That being said, if it were me, id still try the store. Things arent nearly as automated and recorded as you think they might or should be in the real world.
Not to mention, reps at the store are idiots and dont really know too much about smartphones outside of using the setup wizard. I cant tell you how many times tge in store reps have told me or someone else to call the hotline b/c they werent sure or didnt know. The physical store employees are the bottom od the Totum pole. Halfbof them are fresh out of High School
Its not just Verizon that does this by the way.. These phone companieshave this in place as a standard to protect themselves against people bricking phones, and crying out for a replacement. History has shown them that when people root, they tend to flash custom roms, and more dangerously, custom kernels.. As well, people attempt to change the way their CPU functions, and alter the phone to better its performance.. When these things are done, it changes the system hardware stability, and things can get weak or damaged.
So as a way of cutting you off from future complaints, they make it clear that if you root, your warantee is void.
NEVER tell them its rooted, never walk into a store with a rooted device and ask for help, and if you call for support, dont just put it in airplane mode.... PULL THE BATTERY!!! They are able to access your phone through GPS, wifi, bluetooth, and data connection
If the battery is in your device, it can be accessed... The Government has been doing it for years to track people...and contrary to common thought, I believe I read some documentation that "front facing" cameras were a Government idea...
Anyways, be safe, and be careful...youve just learned proof that someone is watching
JJT211 said:
Wow, now that I think of it, you might be right!
Same thing happened to me a few days ago. I had already granted it access before i even realized it was the actual Verizon app. Shrugged my shoulders after I realized it but thought it had something to do with the actual ROM im running (Jasmine 3.0).
Click to expand...
Click to collapse
Why on Earth would you grant something root privileges without verifying what was asking first? This is exactly the type of thing more senior folks in the modding community are constantly complaining about.
yes NEVER EVER GIVE MY VERIZON SU!!! this is what probably happened and it throws flag in their system if you call or request service
Its totally possible.
From what I understand the response from denying root access and the response from not having it at all have two different signatures.
Once I saw a VZW app requesting root I immediately denied it. But that right there could have been the dead giveaway.
I already tried flashing back to stock using the KDZ method. Still the problem of audio quality persists.
Either way, it's BS this is most definitely a hardware issue and should be covered under warranty.
Sent from my VS985 4G using XDA Free mobile app
Yes it's BS but it shouldn't really be a surprise. And it's nothing we haven't been warned of before
I suggest calling back in. If you are now back on stock, you should have no problem. I know it sucks ass, but representatives are just doing a job. What we were told, if someone was rooted, to try to suggest that they return to stock and then we can support the phone, and that is again no matter what the issue might be. Well, as long as it can boot up. So if you flashed back to stock using the KDZ method, root should not be detected anymore. And it might have been noted at that time that it was rooted, but it's a different story now since the phone is back to stock.
Hi
My LG G5 is just under 18 months old, so still covered by the 2 yr UK warranty in that sense. It has started to only accept a USB connection (for charging, data connection, anything) once before it needs rebooting to accept it again.
So, I sent it back to LG. They sent the phone back to say it is rooted and wouldn't fix it.
I have eventually got to someone at Head Office and they still say the same, that as the OS has been modified then they will not repair it (the warranty does state that they will not repair a fault CAUSED by a modification by the way)
So I ran the internal software check as mentioned here - https://forum.xda-developers.com/lg-g5/help/how-tell-g5-rooted-t3528248 - and it does indeed come up with a positive, it says that SUPERUSER (a rooting related app) was installed on 1/1/17. - see attached image
I well remember doing a full wipe and reinstall of the phone on new years day and Google Play installed all the apps on my account and I had to delete the ones that I didn't use anymore. I have rooted various devices and that is why Superuser was in my Google Play account. It did install on the phone that day and was uninstalled (never run) the same day. The phone has never been rooted (it has been mine since new, I know how to root phones and would know if I had! I have also had no reason to) and I have run Android Pay and the banking apps on it all the time.
I can actually get the phone repaired for £25 anyway so it's not so much the repair that is the issue right now, it's that I think LG shouldn't get away with treating customers like this and I want to make a point.
Before I go through the various public attempts to make the point (Twitter, Trading Standards, Tech mags) I do want to be 100% clear of the facts, so if I am mistaken then please do tell me.
The Head Office guy said that even though Android Pay etc still works, that they have different checks and that a program has been run that has modified the OS. Their own internal phone software tells me that this program is Superuser. My understanding is that superuser does nothing at all unless a phone is rooted. Then, on a rooted phone, it will act as a 'middle-man', intercepting anything that wants root access and asking for permission from the user.
Am I correct in saying (and LG incorrect) that Superuser makes NO change to the OS? All the version numbers in About in Settings are the current legit ones.
In my opinion, they are technically intelligent enough to know that there is no technical issue with my circumstances, they just want to get out of fixing the phone (which has already cost them me buying the next incarnation of the series at the end of my contract and my next TV too). Even if it had been modified, the app was installed on 1 Jan, the issue started a month ago, and LG happily fixed another fault (fingerprint sensor) on the phone back in April with no complaining about root! There could be no proof that the fault was caused by Superuser.
Any advice/ammunition to talk to them would be appreciated.
They don't know what they saying.. superuser app could not modify the os if it is not rooted and have not unlocked bootloader...
Exactly what I thought.
I should probably have posted this in the Superuser forum, is it possible to move it? I don't want to repeat post. If anyone could say what Superuser DOES do, that would be ideal..
Thanks
Thanks Gerciolst.. they have now agreed to repair it!