Advice for proving RAZR Maxx is broken?

Advice for proving RAZR Maxx is broken? - Motorola Droid RAZR

I've got insurance for my cell phone through my credit card. If it breaks, they'll send me $250 to buy a new one. And my RAZR Maxx is definitely messed up.
The problem is, the problems are intermittent. And for me to make a successful claim, I have to get a technician to look at the phone and write a letter saying it's broken. I had to go through this process a couple of years ago with a Motorola Atrix that was clearly, obviously broken. And the technicians are always like, "what? what do you mean? what good is a letter like that going to do?" No matter how many times I try to explain to them. It's like they think I'm trying to trap them.
Anyway, is there anything short of throwing the phone off the top of my house that I can do to my phone that makes it easy to show to a technician and have him verify there are issues with it? I'd like not to destroy the phone in case my claim is denied. There are other criteria other than just proving phone is broken. And if the claim is denied, I may need to use the phone for a few more months till I can afford to buy a new one.
The phone is rooted. So I can install whatever software that needs the phone to be rooted. And I have asked in the past, rooting the phone does not cancel my insurance. The case is basically the cell phone insurance department doesn't seem very technologically savvy and don't have a lot of clauses you see when cell phone company's are describing cell phone warranties. Then they have other clauses that you would never see in a cell phone warranty.
If you want to know what's wrong with my phone, like occasionally, nothing it can do will it lock onto the GPS satellites, and I'm stuck somewhere trying to navigate my way to some place.. Occasionally it'll pop up on my screen saying "HDMI cable detected" and orient my screen sideways like if the phone were in a dock. It does this even though there's clearly no HDMI cable connected and I have turned HDMI detection off in the settings. Plus, the phone is just god awful slow a lot of times. Trying to use Chrome on the phone, a lot of times it'll hang and eventually I'll get the message "Chrome is not reponding", then I have options like do you want to wait for it, or go ahead and kill it.

levander said:
I've got insurance for my cell phone through my credit card. If it breaks, they'll send me $250 to buy a new one. And my RAZR Maxx is definitely messed up.
The problem is, the problems are intermittent. And for me to make a successful claim, I have to get a technician to look at the phone and write a letter saying it's broken. I had to go through this process a couple of years ago with a Motorola Atrix that was clearly, obviously broken. And the technicians are always like, "what? what do you mean? what good is a letter like that going to do?" No matter how many times I try to explain to them. It's like they think I'm trying to trap them.
Anyway, is there anything short of throwing the phone off the top of my house that I can do to my phone that makes it easy to show to a technician and have him verify there are issues with it? I'd like not to destroy the phone in case my claim is denied. There are other criteria other than just proving phone is broken. And if the claim is denied, I may need to use the phone for a few more months till I can afford to buy a new one.
The phone is rooted. So I can install whatever software that needs the phone to be rooted. And I have asked in the past, rooting the phone does not cancel my insurance. The case is basically the cell phone insurance department doesn't seem very technologically savvy and don't have a lot of clauses you see when cell phone company's are describing cell phone warranties. Then they have other clauses that you would never see in a cell phone warranty.
If you want to know what's wrong with my phone, like occasionally, nothing it can do will it lock onto the GPS satellites, and I'm stuck somewhere trying to navigate my way to some place.. Occasionally it'll pop up on my screen saying "HDMI cable detected" and orient my screen sideways like if the phone were in a dock. It does this even though there's clearly no HDMI cable connected and I have turned HDMI detection off in the settings. Plus, the phone is just god awful slow a lot of times. Trying to use Chrome on the phone, a lot of times it'll hang and eventually I'll get the message "Chrome is not reponding", then I have options like do you want to wait for it, or go ahead and kill it.
Click to expand...
Click to collapse
Have you tried returning the phone to bone stock with a stock recovery image and rsd lite? Be fore warned, you will lose root but, you can get it back. Afterwards it will be like a new phone(faster, a lot less buggy and force closes) unless it is truly a hardware issue. I have a motorola xoom that started having serious issues, I went through the whole process, and it was like a completely new tablet when was done, battery life I hadn't seen in over a year, very responsive, it was like I had just unboxed it from the store.
Truthfully the technicians probably DO think you are trying to trap them when you are talking about intermittent problems. Intermittent problems are hard to diagnose with anything unless you can tell them a specific action or pattern of actions that leads up to the problem. I am sure they get a lot of people all the time with "it doesn't work right" claims to try to get money for a new phone.
IMHO it would be worth the shot to see if it legitimately has a goofy problem, or can be easily fixed at home.

Draxin said:
Have you tried returning the phone to bone stock with a stock recovery image and rsd lite?
Click to expand...
Click to collapse
Yeah, thanks Draxin. I've tried restoring to a factory image. And it seems to work okay for a couple of days before small things start back up. A couple of months later, the phone is as flaky as it ever was. It could just be software, that is possible. But it's not like I can go in and fix the software myself or anything. And I think hanging around the internet, looking for tweaks and fixes any more than I already have is really an unreasonable request by the insurance company.
What you say about an easily repeatable pattern, that's what I was hoping to figure out by posting here.
But getting no responses, I think I'm just gonna start my claim and when it gets to the point of proving it's broken, I'm just gonna microwave the phone. Googling all over the Internet that's the only advice people seem to offer.
Basically as it is now, I'm gonna have to pay for a new phone and hope this clumsy phone insurance through my credit card company makes good on my claim. I know I meet the criteria because I've read the policy. It's just the hoops they put you through to prove you meet the criteria that I'm worried about.

levander said:
Yeah, thanks Draxin. I've tried restoring to a factory image. And it seems to work okay for a couple of days before small things start back up.
Click to expand...
Click to collapse
With a full wipe and stock motorola firmware? Or just a factory reset?
Either way wish you the best of luck

Yeah try using rsd to fully restore. I fixed a lot of my problems that way .
Sent from my XT912 using Tapatalk

tydiamond11 said:
Yeah try using rsd to fully restore. I fixed a lot of my problems that way .
Sent from my XT912 using Tapatalk
Click to expand...
Click to collapse
Very true. It is funny/sad. Spend some time on a site like this and it seems like everybody knows these things. Talk to your friend or the typical consumer of smartphones and it is foreign to them. They feed into the advertising that the newest and greatest will solve all their problems, not realizing they are falling into the same viscous circle. They will actually disbelieve you, cause... well come on, the phone is two years old! "The guy at my carriers store is surprised my phone still works. Sure he got the job two months ago, won't be there five from now and has no idea what a OTG cable is, or a independently powered usb hub but, still he works there.. so he must know what he is talking about! I am sure it has nothing to do with commission of sales!" (that was facetious, by the way)
I am curious how many people have thought that their smartphone was dying or to old because a factory reset didn't work(not talking about you lavender, I don't know what you have done to fix your device( guess I am semi-hijacking your thread)).
Motorola(or any device manufacturer for that matter) isn't going to tell the typical user that a firmware reflash is required to get a couple more years out of their device when they can sell a user (that won't waste the time to Google)another device. Certainly won't advertise it right next to their latest and greatest device. Really how many people outside of the power users or gamers REQUIRE a quad core processor with 1500-1800 mhz, or 2-3 gb of RAM. When typically, it will end up the same way in a years time, depending on how much they use it.
Porn doesn't require those specs!!!

Draxin said:
Very true. It is funny/sad. Spend some time on a site like this and it seems like everybody knows these things. Talk to your friend or the typical consumer of smartphones and it is foreign to them. They feed into the advertising that the newest and greatest will solve all their problems, not realizing they are falling into the same viscous circle. They will actually disbelieve you, cause... well come on, the phone is two years old! "The guy at my carriers store is surprised my phone still works. Sure he got the job two months ago, won't be there five from now and has no idea what a OTG cable is, or a independently powered usb hub but, still he works there.. so he must know what he is talking about! I am sure it has nothing to do with commission of sales!" (that was facetious, by the way)
I am curious how many people have thought that their smartphone was dying or to old because a factory reset didn't work(not talking about you lavender, I don't know what you have done to fix your device( guess I am semi-hijacking your thread)).
Motorola(or any device manufacturer for that matter) isn't going to tell the typical user that a firmware reflash is required to get a couple more years out of their device when they can sell a user (that won't waste the time to Google)another device. Certainly won't advertise it right next to their latest and greatest device. Really how many people outside of the power users or gamers REQUIRE a quad core processor with 1500-1800 mhz, or 2-3 gb of RAM. When typically, it will end up the same way in a years time, depending on how much they use it.
Porn doesn't require those specs!!!
Click to expand...
Click to collapse
You are right. Just the last part is not really relevant to this form by the way.
Sent from my XT912 using Tapatalk

Related

WARNING T-Mobile NOT helpful! BEWARE OF 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...

[Q] Need an expert's opinion/help

Hey guys, I came had the HTC Sensation, and I broke it VERY bad, and T-Mobile refused to give me a new one, so I bought the Amaze 4G on Amazon.
The phone worked okay for the first week, and about 10 days after I had it, it started to randomly freeze and I would have to lock and unlock the screen for it to work again.
Wasn't a big deal at first. It was almost as if the processor wasn't getting enough voltage for example, on my Sensation if I undervolted it too much it would freeze up and I would need to pull the battery.
Not as big of a deal though, but it is SO ANNOYING when trying to text or type something and having to go through the whole process.
But then the device was getting very slow when I had it on the charger, so I argued with Amazon to take it back and they said I would have to contact the private dealer.
I had no luck with the dealer, so I basically got screwed over out of 500 bucks.
BUT... I think the problem is fixable...
Correct me if I'm wrong, (and I probably am), I am NEARLY 100% positive this is a battery issue or a processor issue.
And maybe one of you phone geniuses will be able to help me out (You guys never dissapoint)
But before I drop 15 dollars on a battery, I want to know if one of you have had experience with a problem like this. Even after rooting, wiping, installing countless roms and apps, I have had no luck at all.

Did you buy it used?

Iscreaman2311 said:
Did you buy it used?
Click to expand...
Click to collapse
Yea it was "Certified Refurbished" by the company, but they said that there was no way to prove it was like that when it left their shop, so basically I got screwed out of everything. I tried contacting HTC also and they said a standard repair could range up to 100 dollars, and I really don't want to spend that unless I have to, but I am almost positive it's the battery that doesn't give the phone enough power. I will take it up to T-Mobile and see if they have a tester battery I could use. Very weird problems though, it makes me wonder if it's more than the battery.

Thaxtonator said:
Yea it was "Certified Refurbished" by the company, but they said that there was no way to prove it was like that when it left their shop, so basically I got screwed out of everything. I tried contacting HTC also and they said a standard repair could range up to 100 dollars, and I really don't want to spend that unless I have to, but I am almost positive it's the battery that doesn't give the phone enough power. I will take it up to T-Mobile and see if they have a tester battery I could use. Very weird problems though, it makes me wonder if it's more than the battery.
Click to expand...
Click to collapse
I think we need more info before we can think of possible reasons for the problem.
Are you rooted?
What software version are you using?
Did you do the factory reset?
What apps are running background?
Did you try different sd card?
Did you get logs (logcat, etc.)
etc. etc.
It may be purely hardware issue like you say, but as you say, software can cause similar problems, too. Especially, if you can remedy the problem by going in to the lockscreen and back, I think it is software related.
EDIT: Wait a minute! You're the same guy asking about s-off'ing the phone with ICS leak, aren't you? Probably you didn't flash the original ICS RUU before flashing a custom ROM? Mismatched firmware can cause tons of problems and there's no easy solution to it rather than to flash the firmware. But then, if you're not s-off'ed, you can't flash firmware to begin with. What a mess you are in.

Also if you think it's a battery problem plug the thing in problem still there not the battery. It will get full power plugged in even with a bad battery.
Sent from my HTC_Amaze_4G

[Q] Phone won't turn on?

Hi, uh I started another thread on making sure things got backed up. Which I did properly and everything was good. So today I haven't done anythign and was waiting for the new slim rom to make it's debute hopefully this week sometime as that is the one that appeals to me the most. Anyways, today my phone just got super hot, far hotter than before and it decided to die on me...I think. it shut off and I haven't been able to turn it on. Could this be a side effect of installing twrp/unlocking the bootloader/rooting? Or would it be a defective unit? One concern I had was getting a defective unit so i waited out my 30 days before even considering doing all this. So yea my 30 days from att is up. Would there possibly be a way to get a new phone from att or does anyone have any tricks on getting it back online? I personally think it was an overheating issue, but my phone is now cooled down.
So i went to the att store and of course they won't do anything. They told me to call some number they gave me. If I return it will they know it was boot unlocked and rooted? I can't turn it on at all. Using a power source or connecting to my computer nor my car charger...

blamster said:
Hi, uh I started another thread on making sure things got backed up. Which I did properly and everything was good. So today I haven't done anythign and was waiting for the new slim rom to make it's debute hopefully this week sometime as that is the one that appeals to me the most. Anyways, today my phone just got super hot, far hotter than before and it decided to die on me...I think. it shut off and I haven't been able to turn it on. Could this be a side effect of installing twrp/unlocking the bootloader/rooting? Or would it be a defective unit? One concern I had was getting a defective unit so i waited out my 30 days before even considering doing all this. So yea my 30 days from att is up. Would there possibly be a way to get a new phone from att or does anyone have any tricks on getting it back online? I personally think it was an overheating issue, but my phone is now cooled down.
So i went to the att store and of course they won't do anything. They told me to call some number they gave me. If I return it will they know it was boot unlocked and rooted? I can't turn it on at all. Using a power source or connecting to my computer nor my car charger...
Click to expand...
Click to collapse
Ok, so, im not sure if by return you mean, return for an exchange or simply a return as ATT will probably only send you a reman unit for yours and not allow an actual return. If you havent called them yet, i would recommend it. I have dealt with them many times in the past and one thing that has always shocked me is that they never have asked me about, or even commented on, how rooting or unlocking prevents them from exchanging it. Even during the disclaimer, they have never once said that if the device has been modified they wont allow the exchange.
I say all of this because should they not mention anything like that, and you send it back, im fairly sure you can claim you didnt know and werent told, and they will take care of it. Also, i say this because i personally sent back 3 bricked GS2s and an lg nitro as defective and got my reman units and every single one of them were rooted and such. So, i would feel safe. As long as they dont ask, and you dont lie to them, then there shouldnt be an issue. I wouldnt lie to them, i just dont mention it. AGAIN DO NOT lie to them or attempt to decieve them, i would never encourage that, but if its something they dont ask about, then, it, in my opinion, is not something that they are too concerned with.

cloudraker said:
Ok, so, im not sure if by return you mean, return for an exchange or simply a return as ATT will probably only send you a reman unit for yours and not allow an actual return. If you havent called them yet, i would recommend it. I have dealt with them many times in the past and one thing that has always shocked me is that they never have asked me about, or even commented on, how rooting or unlocking prevents them from exchanging it. Even during the disclaimer, they have never once said that if the device has been modified they wont allow the exchange.
I say all of this because should they not mention anything like that, and you send it back, im fairly sure you can claim you didnt know and werent told, and they will take care of it. Also, i say this because i personally sent back 3 bricked GS2s and an lg nitro as defective and got my reman units and every single one of them were rooted and such. So, i would feel safe. As long as they dont ask, and you dont lie to them, then there shouldnt be an issue. I wouldnt lie to them, i just dont mention it. AGAIN DO NOT lie to them or attempt to decieve them, i would never encourage that, but if its something they dont ask about, then, it, in my opinion, is not something that they are too concerned with.
Click to expand...
Click to collapse
Okay, thanks for the response. Sorry I was in a bit of a panic when I wrote that. But I have called ATT and they didn't ask me or mention in any disclaimer that if it's rooted or unlocked it won't qualify. I didn't mention it and so that does make me feel a lot better. Hasn't been physically damaged or come in contact with water so i'm pretty sure I'm safe. Thanks again.

blamster said:
Okay, thanks for the response. Sorry I was in a bit of a panic when I wrote that. But I have called ATT and they didn't ask me or mention in any disclaimer that if it's rooted or unlocked it won't qualify. I didn't mention it and so that does make me feel a lot better. Hasn't been physically damaged or come in contact with water so i'm pretty sure I'm safe. Thanks again.
Click to expand...
Click to collapse
They may or may not check when you return the phone. I returned my S3 a few months ago in exchange for a different phone but I forgot to unroot it and uninstall Superuser. The representative at AT&T didn't even turn the phone on. I didn't have anything to hide though, if they told me I couldn't return it because it was rooted then I would have sold it and purchased something else. I think the manufacturer is the one to worry about with these things. LG would definitely know if it were unlocked and they would be able to determine if rooting and unlocking the phone caused the problems you described.

johnbyebye said:
They may or may not check when you return the phone. I returned my S3 a few months ago in exchange for a different phone but I forgot to unroot it and uninstall Superuser. The representative at AT&T didn't even turn the phone on. I didn't have anything to hide though, if they told me I couldn't return it because it was rooted then I would have sold it and purchased something else. I think the manufacturer is the one to worry about with these things. LG would definitely know if it were unlocked and they would be able to determine if rooting and unlocking the phone caused the problems you described.
Click to expand...
Click to collapse
Well if they can turn it on I will gladly take it back due to them not accepting. I couldn't turn it on by anymeans, even plugging it in there is no lights to signifying it is receiving power. But i heard this phone had overheating issues in the first wave (or two) so it's probably for the best to get a new one. They are currently mailing me a new one and so I should receive it next week sometime hopefully.

blamster said:
Well if they can turn it on I will gladly take it back due to them not accepting. I couldn't turn it on by anymeans, even plugging it in there is no lights to signifying it is receiving power. But i heard this phone had overheating issues in the first wave (or two) so it's probably for the best to get a new one. They are currently mailing me a new one and so I should receive it next week sometime hopefully.
Click to expand...
Click to collapse
Sounds like everything worked out.

im in the same boat as you... completely dead phone. But I did open it to see of the battery pull would work. Do you think that theyll check and refuse my warranty because I opened it? the phone on the outside is NEW. Btw do you have a contract/account with ATT? I bought mine off ebay and used it on tmo...

I have the exact same problem! Totally dead phone that the charging light won't even turn on for. Unfortunately there is a small crack in the bottom left of the phone that was caused months prior so ATT wont give me a new one...

send it for repairs! I had rooted and unlocked mine so ATT didnt cover my warranty, but I only paid 50 bucks for the repairs and now I have my phone back!

Attempting a Swap for a Non-VRUAME7 S4

Hey guys, so I recently picked up the S4 as I had an upgrade and chose this phone specifically for it's support by developers here on XDA. Strictly due to my own aloofness, and not having checked the forums for a few weeks before walking into the store (fail), I ran the update as it popped up immediately and I figured "why not" (I KNOW, I went full-retard and expected something useful from a Verizon OTA... they screwed me last time with an OTA too ).
Anyway, I still have about ten days before my "Worry-free Guarantee" runs out, and I'm really considering going back and claiming a warranty replacement on my phone in an attempt to receive a non-VRUAME7-equipped phone (as I said, the 16GB versions in stock there didn't have the update initially). If I attempt to claim the phone as defective, do you think I could avoid the $35 restocking fee, considering I'd swap for the exact same model of phone?
I'm not sure what to expect when going back there. Some CSR's seem much more technical than others, so I don't know if I'd be drilled about the issue I'm claiming. Any advice here? Would focusing on a 'bad battery' or 'device overheating' raise any red flags? Should I bring it in drained of battery life? I've kept excellent care of the phone; it's in mint condition without a scratch or blemish, non-rooted, and fully updated.
Even if I have to pay the $35 fee, I would do it for a non-updated phone. I'm just worried that by chance the CSR that gives me my replacement would decide to run the upgrade, as it will pop up immediately. Also, any tips on ensuring I avoid the upgrade until I back up the phone and root it? Just yank out the SIM until it's good to go?
Thanks for any advice you may have. I'm new here so flame me relentlessly for any rules I may have broken . And yes, I know, ultimately I'm complaining about having an S4 (read: kinda being a *****).

I stopped the update by turning off WiFi and data until I had it rooted and ROMed
Sent from my SCH-I545 using xda premium

My understanding of the guarantee is that it can be returned for any reason. I can't tell from a quick Google search, but it sounds like you might have a shot at no restocking fee if you're exchanging for the same model.
Given those tidbits, I'd tell them you want to exchange the phone due to reduced functionality after the update, and leave it at that. If they offer to troubleshoot, you can then say "sure, remove the update", which they can't do. I think this approach will give you the best chance of leaving the store with an un-updated phone and no fee. No CSR is going to take the OTA after having to deal with the guy who really hates the update for nonspecific reasons.
Sent from my SCH-I545 using xda premium

TheJ0hnman said:
My understanding of the guarantee is that it can be returned for any reason. I can't tell from a quick Google search, but it sounds like you might have a shot at no restocking fee if you're exchanging for the same model.
Given those tidbits, I'd tell them you want to exchange the phone due to reduced functionality after the update, and leave it at that. If they offer to troubleshoot, you can then say "sure, remove the update", which they can't do. I think this approach will give you the best chance of leaving the store with an un-updated phone and no fee. No CSR is going to take the OTA after having to deal with the guy who really hates the update for nonspecific reasons.
Sent from my SCH-I545 using xda premium
Click to expand...
Click to collapse
Interesting point, TheJ0hnman. I think turning window animations to something atrocious will help me have something that seems effed upon a cursory check, as well as some other developer options that undoubtedly make you think "wtf" if you don't know better, like flash on update etc. (wish I could then rehide the developer menu). Do you really think blaming the update would work well? I think I'd rather feign ignorance and say that the update "screwed with everything, battery life and runs slow", and act as if I'm unfamiliar with technical operation of android.

I don't think user error is covered under the 14 day WFG .

Why not keep it simple by saying you just want to swap colors. Whichever is less popular (white?) might have a bigger stock backlog & thus be more likely to have MDK firmware. Then either be bold and ask them not to update OTA, or be in a terrific hurry to get somewhere else and tell them you'll activate and set the phone up yourself.

cantare said:
Why not keep it simple by saying you just want to swap colors. Whichever is less popular (white?) might have a bigger stock backlog & thus be more likely to have MDK firmware. Then either be bold and ask them not to update OTA, or be in a terrific hurry to get somewhere else and tell them you'll activate and set the phone up yourself.
Click to expand...
Click to collapse
That makes a lot of sense, cantare. Only thing is I might end up paying the restocking fee. I think I'll try the warranty replacement first. Imagine me going through all this just to get another VRUAME7'd phone!

soad1789 said:
Hey guys, so I recently picked up the S4 as I had an upgrade and chose this phone specifically for it's support by developers here on XDA. Strictly due to my own aloofness, and not having checked the forums for a few weeks before walking into the store (fail), I ran the update as it popped up immediately and I figured "why not" (I KNOW, I went full-retard and expected something useful from a Verizon OTA... they screwed me last time with an OTA too ).
Anyway, I still have about ten days before my "Worry-free Guarantee" runs out, and I'm really considering going back and claiming a warranty replacement on my phone in an attempt to receive a non-VRUAME7-equipped phone (as I said, the 16GB versions in stock there didn't have the update initially). If I attempt to claim the phone as defective, do you think I could avoid the $35 restocking fee, considering I'd swap for the exact same model of phone?
I'm not sure what to expect when going back there. Some CSR's seem much more technical than others, so I don't know if I'd be drilled about the issue I'm claiming. Any advice here? Would focusing on a 'bad battery' or 'device overheating' raise any red flags? Should I bring it in drained of battery life? I've kept excellent care of the phone; it's in mint condition without a scratch or blemish, non-rooted, and fully updated.
Even if I have to pay the $35 fee, I would do it for a non-updated phone. I'm just worried that by chance the CSR that gives me my replacement would decide to run the upgrade, as it will pop up immediately. Also, any tips on ensuring I avoid the upgrade until I back up the phone and root it? Just yank out the SIM until it's good to go?
Thanks for any advice you may have. I'm new here so flame me relentlessly for any rules I may have broken . And yes, I know, ultimately I'm complaining about having an S4 (read: kinda being a *****).
Click to expand...
Click to collapse
Unfortunately it's yourself that screwed you. Not the OTA.
Root users know NEVER to take an OTA.

Hi Everyone. I just upgraded to the S4 last Sunday and while I was in the store and they were activating the phone, it started the update. I did not realize that this update locked everything down.
So, I decided that I would wait it out and see when the new update would be cracked. That was a couple days ago and I was having flash withdrawals. This morning I figured I would go to the Verizon store near work and just ask straight up ask if I could return my phone because of the new update....and as soon as the words update came out of my mouth, the girl interrupted me and said "Yes, we are having all kinds of issues with the new update and have replaced phones all weekend. We will get you a new phone".
5 mins later, new phone in hand with MDK software. AND the whole store told me not to take the update that another one is in the works. Can't wait to get home and root this thing and get Andy's Bone Stock ROM running.

anyone know the status on refurbs with the update?
i might have to get mine replaced due to brightness problems on my buttons and curious how well people are doing with the refurbs

kaos2569 said:
Hi Everyone. I just upgraded to the S4 last Sunday and while I was in the store and they were activating the phone, it started the update. I did not realize that this update locked everything down.
So, I decided that I would wait it out and see when the new update would be cracked. That was a couple days ago and I was having flash withdrawals. This morning I figured I would go to the Verizon store near work and just ask straight up ask if I could return my phone because of the new update....and as soon as the words update came out of my mouth, the girl interrupted me and said "Yes, we are having all kinds of issues with the new update and have replaced phones all weekend. We will get you a new phone".
5 mins later, new phone in hand with MDK software. AND the whole store told me not to take the update that another one is in the works. Can't wait to get home and root this thing and get Andy's Bone Stock ROM running.
Click to expand...
Click to collapse
Wow. I hope I have a similar experience! kaos2569, you got a black 16gig this morning and it was pre-ME7? This truly gives me hope.

Yes, I went to the store, and it was swapped out no problem. I didn't try to scam, or make up anything up. I just said what I posted and she stopped me mid sentence and knew about the update and how it was messing people's phones up and grabbed a brand new pre-updated one.
I just finished up rooting, installed a recovery, and installed Bone Stock. Everything went flawless.

kaos2569 said:
Yes, I went to the store, and it was swapped out no problem. I didn't try to scam, or make up anything up. I just said what I posted and she stopped me mid sentence and knew about the update and how it was messing people's phones up and grabbed a brand new pre-updated one.
I just finished up rooting, installed a recovery, and installed Bone Stock. Everything went flawless.
Click to expand...
Click to collapse
my phone should be here weds, so ill give this a try this weekend. unless the doodoo brown ones come pre-update.

kaos2569 said:
Yes, I went to the store, and it was swapped out no problem. I didn't try to scam, or make up anything up. I just said what I posted and she stopped me mid sentence and knew about the update and how it was messing people's phones up and grabbed a brand new pre-updated one.
I just finished up rooting, installed a recovery, and installed Bone Stock. Everything went flawless.
Click to expand...
Click to collapse
Wow do I feel sly! My experience was not quite as straightforward as yours, kaos2569, but I pulled it off! I had to convince two CSRs, one who actually also owned an S4 and was clearly no n00b (though he said he had the ME7 update so I guess not an XDA regular). I used one of the update screens in developer options to trick the first lady, who then restarted my phone and had me wait to be seen. While waiting, I went back and turned on developer options again, then turned them off, realizing beforehand that open apps will retain the "screwy" look even with the options off. The guy proceeded to investigate my phone for what must've been 20 minutes. I kept insisting the problem was intermittent and hinting at the possibility that the update played a role in the problem. After some skepticism (he noticed the developer options were off but the menu was available; I played dumb, saying I let a gadget-freak friend look at it for a bit), he finally offered me a free(!) replacement and I took it. I was waiting for a while once he got the new phone out, and was getting nervous that he might've been installing the update. He said "I'm downloading the update now, I'll run through it here to make sure there are no issues" so I immediately told him I had to be somewhere in ten minutes. He handed my phone back to me, I turned it off immediately, pulled the battery, and went home. Pulled the SIM card and booted-- still MDK indeed! Wow. It was a process but it was worth it. Can't wait to get some custom ROMs on this!
I can understand the animosity some people might have over doing something like this, but I was scarred by Verizon for nearly the entirety of the two years I had had my old phone, due to another damn OTA update, which didn't lock me out, but installed Gingerbread and made the phone basically impossible to use (legit, 12 seconds to open the ****** dialer). I just couldn't let Verizon lock me down again without a fight. And I will *SURELY* remember that guy the next time an upgrade comes along.
Thanks again kaos! You gave me the confidence to believe it could be done, and that it wasn't too late!

all i did was take it back within first 14 days... before i did though i went into app settings and disabled all apps including play store so they were not visible in app drawer. i told him it was freezing and soft booting itself after i updated the phone.. then i told him i called in and spoke with a tech n did a factory reset and everything dissappeared including my apps and i cant dl apps since my play store is gone.. he was lookin at it for a bit and was like wow thats weird! i told him the tech said since i was within 14 days he told me to go back to the store and exchange for a new one that wasnt updated.. worked like a charm! i told him not to update it that ill decline it until they come out with a new update n that was it! rooted n installed twrp soon as i got home been flashin every rom on here since! currently on hyperdrive n lovin it!
Sent from my SCH-I545 using xda app-developers app

soad1789 said:
Wow do I feel sly! My experience was not quite as straightforward as yours, kaos2569, but I pulled it off! I had to convince two CSRs, one who actually also owned an S4 and was clearly no n00b (though he said he had the ME7 update so I guess not an XDA regular). I used one of the update screens in developer options to trick the first lady, who then restarted my phone and had me wait to be seen. While waiting, I went back and turned on developer options again, then turned them off, realizing beforehand that open apps will retain the "screwy" look even with the options off. The guy proceeded to investigate my phone for what must've been 20 minutes. I kept insisting the problem was intermittent and hinting at the possibility that the update played a role in the problem. After some skepticism (he noticed the developer options were off but the menu was available; I played dumb, saying I let a gadget-freak friend look at it for a bit), he finally offered me a free(!) replacement and I took it. I was waiting for a while once he got the new phone out, and was getting nervous that he might've been installing the update. He said "I'm downloading the update now, I'll run through it here to make sure there are no issues" so I immediately told him I had to be somewhere in ten minutes. He handed my phone back to me, I turned it off immediately, pulled the battery, and went home. Pulled the SIM card and booted-- still MDK indeed! Wow. It was a process but it was worth it. Can't wait to get some custom ROMs on this!
I can understand the animosity some people might have over doing something like this, but I was scarred by Verizon for nearly the entirety of the two years I had had my old phone, due to another damn OTA update, which didn't lock me out, but installed Gingerbread and made the phone basically impossible to use (legit, 12 seconds to open the ****** dialer). I just couldn't let Verizon lock me down again without a fight. And I will *SURELY* remember that guy the next time an upgrade comes along.
Thanks again kaos! You gave me the confidence to believe it could be done, and that it wasn't too late!
Click to expand...
Click to collapse
And you are proud of this? It's because of people like you returning non defective products that the rest of the consumers have to suffer. tl;dr guess you have a total lack of integrity and morals to just accept your screw up. You sir are a douche bag.

Reading to learn about your device. Crazy, Who would of known.
Sent from my SCH-I545 using Tapatalk 2

zetsumeikuro said:
And you are proud of this? It's because of people like you returning non defective products that the rest of the consumers have to suffer. tl;dr guess you have a total lack of integrity and morals to just accept your screw up. You sir are a douche bag.
Click to expand...
Click to collapse
hexitnow said:
Reading to learn about your device. Crazy, Who would of known.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
You guys are certainly entitled to your opinions, and I really don't disagree. I have egg on my face from the whole event. After all, it was my fumbling that screwed me over in the first place. However, I'm curious as to your feelings about Big Red itself. Like I said, this phone enticed me exactly for it's support by this community, and Verizon obviously realized that if they in turn locked the phone down with an update. What of that?
zetsumeikuro; this device will quickly be determined a Certified Like-New Replacement. I took pristine care of the phone, didn't screw around with the internals at all, and even kept the touchscreen under the manufacturer-issued screen protector the entire time I had the phone. If someone (due to their own bumbling) drops their phone in water, loses it, etc. They will end up with that phone and be very happy with it, unless they expected to luck out on a replacement and receive a pre-ME7 phone as well. I'm sorry, I can't say I see the harm in that, or how any other consumer suffers outright. I could've gotten a replacement within my 14 days for almost any reason. Yes-- I got out of a restocking fee and got a pre-update phone; what if I just paid $35 and got a Droid instead?
hexitnow, absolutely. I goofed up, that's for sure. I could attempt to excuse that by saying how I've been working 65-hour weeks and attempting to orchestrate a move into a new apartment lately, but I'm sure nobody really cares about that. Yes, I was negligent, having read up on the phone in early June thinking our upgrade was sooner than it actually was (and being treated oh-so-rudely by a CSR when we thought our upgrades were available back then), but ultimately it was me being stupid. I believe I learned a lesson here, and you rightly may resent me and people like me for our stupidity, but people make mistakes. This isn't my first or last one, either. Ultimately, it's just a phone update, I screwed nobody in doing what I did except arguably Verizon, who I managed to avoid paying yet another $35 to. I... I just don't feel that bad. I've felt wronged by them at every turn, and honestly I feel worse sticking with them as my carrier then I do taking advantage of my "Worry-free Guarantee" (assuming you don't worry about $35 fees).
Note that I am known to be a "whimsical douchebag", however.

soad1789 said:
You guys are certainly entitled to your opinions, and I really don't disagree. I have egg on my face from the whole event. After all, it was my fumbling that screwed me over in the first place. However, I'm curious as to your feelings about Big Red itself. Like I said, this phone enticed me exactly for it's support by this community, and Verizon obviously realized that if they in turn locked the phone down with an update. What of that?
zetsumeikuro; this device will quickly be determined a Certified Like-New Replacement. I took pristine care of the phone, didn't screw around with the internals at all, and even kept the touchscreen under the manufacturer-issued screen protector the entire time I had the phone. If someone (due to their own bumbling) drops their phone in water, loses it, etc. They will end up with that phone and be very happy with it, unless they expected to luck out on a replacement and receive a pre-ME7 phone as well. I'm sorry, I can't say I see the harm in that, or how any other consumer suffers outright. I could've gotten a replacement within my 14 days for almost any reason. Yes-- I got out of a restocking fee and got a pre-update phone; what if I just paid $35 and got a Droid instead?
hexitnow, absolutely. I goofed up, that's for sure. I could attempt to excuse that by saying how I've been working 65-hour weeks and attempting to orchestrate a move into a new apartment lately, but I'm sure nobody really cares about that. Yes, I was negligent, having read up on the phone in early June thinking our upgrade was sooner than it actually was (and being treated oh-so-rudely by a CSR when we thought our upgrades were available back then), but ultimately it was me being stupid. I believe I learned a lesson here, and you rightly may resent me and people like me for our stupidity, but people make mistakes. This isn't my first or last one, either. Ultimately, it's just a phone update, I screwed nobody in doing what I did except arguably Verizon, who I managed to avoid paying yet another $35 to. I... I just don't feel that bad. I've felt wronged by them at every turn, and honestly I feel worse sticking with them as my carrier then I do taking advantage of my "Worry-free Guarantee" (assuming you don't worry about $35 fees).
Note that I am known to be a "whimsical douchebag", however.
Click to expand...
Click to collapse
Don't see the harm in falsifying issues with a non defective device? I'm sure Samsung and Verizon will beg to differ. Yeah your device will probably get turned into a CLNR but clearly someone will be taking a hit for the brand new device you got. I mean the whole issue here that you seem to not see is the utter lack of integrity/honesty on your part. You screwing with developer options to make it look like the phone is having intermittent software issues to some untrained CSR. What you did there just reeks of desperation of you not willing to accept a mistake you made. I'm not going to go into the whole Verizon/Sammy locking down the device debacle, as there is the developer edition of the device. I'm not trying to defend Verizon and their ways.. Simply put it I'm disgusted with the lengths/measure you took to get a replacement device.

zetsumeikuro said:
Don't see the harm in falsifying issues with a non defective device? I'm sure Samsung and Verizon will beg to differ. Yeah your device will probably get turned into a CLNR but clearly someone will be taking a hit for the brand new device you got. I mean the whole issue here that you seem to not see is the utter lack of integrity/honesty on your part. You screwing with developer options to make it look like the phone is having intermittent software issues to some untrained CSR. What you did there just reeks of desperation of you not willing to accept a mistake you made. I'm not going to go into the whole Verizon/Sammy locking down the device debacle, as there is the developer edition of the device. I'm not trying to defend Verizon and their ways.. Simply put it I'm disgusted with the lengths/measure you took to get a replacement device.
Click to expand...
Click to collapse
As I said, you're entitled to your opinions. I could've swapped the phone for any reason, even if I just "didn't like it", as per Verizon's policy. Even if I paid$35 and swapped for an iPhone both Verizon and Samsung would've taken the same "hit". I just managed to avoid the restocking fee. But as you imply, I'm sure Verizon and Samsung will gather in a circle and weep.
They can take that $35 from the device upgrade fees they failed to mention in store. But I'm expected to maintain my full integrity.gotcha.
You sound like my father :laugh:

Word of warning before calling Verizon

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.

Better Mobile App

welcome