Related
Should I unroot my Eris...sending it back to Verizon on Monday. Do they check for that, considering the number of people receiving replacements, has anyone ever had a problem with that?
mswilson2007 said:
Should I unroot my Eris...sending it back to Verizon on Monday. Do they check for that, considering the number of people receiving replacements, has anyone ever had a problem with that?
Click to expand...
Click to collapse
Most people attempt to. There have been reports from people in the past that went both ways - some reporting getting charged, and some reporting having returned a rooted phone with no problems.
Hopefully if someone got popped for it recently, they will speak up - a lot of times people are reluctant to talk about negative experiences.
In any event, there is a newly released ROM that makes unrooting the same level of effort as installing any other ROM - give it a shot and report back your results.
bftb0
I sent my rooted Eris to Verizon a few weeks ago because my old one had the trackball issue, Verizon didn't say anything about it. I think it might depend on what type of problem your phone has. My guess would be that there's more of a chance for them to say something about it if you have a software issue rather than a hardware issue, just a thought.
I've sent two back so far, one rooted and one un-rooted. I sent the rooted one back a couple of months ago and never heard anything about it. I would have to agree that it would depend on if it was a hardware or software issue.
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...
Hey guys, it's deedscreen. The creator of the MoPho XDA Fan Group, facebook, Twitter, and Google+ page, and you may also know me as the one with the problems with the Photon who constantly nags, and rants with issues.
I just want to know if anyone has these issues too.
I have to deal with the phone being slow, constantly freezing, and the sleep of death, even after the latest update.
For the longest, I couldn't update the Photon, I found a thread on how to fix it by 'SBFing. So, I SBF'd it, it worked fine, updated to the latest software.
It was working fine, now I am back to the same issues, plus I cannot install any applications, nor update any applications. It will just say "INSTALLING" for literally hours, and never installs.
I have had the worst luck with this phone, I am going to 'SBF it back to stock, because a factory reset will not get rid of the battery icon modification.
I'm gonna return it to Sprint for a new one. I HAVE HAD IT WITH THIS PHONE!!! Why is it only me with this bad luck? It feels like no one else has these issues on the forums, I am always the one posting with these problems, myself alone! This phone is bad luck for me. I love it, when it works.
///RANT
PLEASE NOTE:
If you have a problem with this thread, keep your trap shut. I will have this thread closed if anyone insults me again, like the last time I had major issues. I am just experiencing bad luck. I need to know if anyone has similar issues. Sorry if I offended anyone.
Are you having similar issues?
Have u tried a completely stick photon...not modded and none of ur market Apps installed? ?
Sent from my MB855 using XDA App
deedscreen said:
I'm gonna return it to Sprint for a new one. I HAVE HAD IT WITH THIS PHONE!!! Why is it only me with this bad luck? It feels like no one else has these issues on the forums, I am always the one posting with these problems, myself alone! This phone is bad luck for me. I love it, when it works.
///RANT
Click to expand...
Click to collapse
Dude, you are definitely NOT alone. I love this phone too when it is working properly. These are my two main issue:
Random Reboots
Keyboard locks up - When this happens, the phone will not dial out. (Reboot required)
* This is my 2nd MoPho and I had the same issues with my first one. *
Factory defects with hardware do happen. Replace if you can.
Sent from my Motorola Electrify using XDA App
The reason why I am not quoting you guys, is because misleads users to think that I already have enough replies, so here we go.
@lucidvtec - I have tried stock options, that doesn't work always, not having any applications from the market installed is like asking me to jump off a bridge.
@sjamie - I do get random reboots ocassionally, but my keyboard, (no matter which one I use), constantly locks up. I get the "Sleep of Death" all of the time, and Constant Freezing. Please vote at the page here, on the forums to poll your results for issues with the Motorola Photon 4G MB855.
@Rapidlayout - You are correct.
-----------------------------
@lucidvtec, @sjamie, @ Rapidlayout: I am on my fifth Photon.
Mine was the same. Bricked it a few weeks ago and got this new one. Its perfect. There must be a bad batch of them, get it replaced bc no software is gonna fix it.
Sent from my MB855 using XDA App
I just completed a MSL reset, a full wipe, and flashed the latest 198_7 sbf. Let's see if this resolves my rebooting and keyboard problems. If not, I'll try out one of joker's roms. If that still doesn't work, I'll go in for Photon #3.
@deedscreen: I'm sorry to hear you are on your 5th Photon. That is not encouraging to me.
DWake014 said:
Mine was the same. Bricked it a few weeks ago and got this new one. Its perfect. There must be a bad batch of them, get it replaced bc no software is gonna fix it.
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
All of the same issues as myself? Now when you replaced it, did you have a problem upgrading to the latest software with the replacement?
sjamie said:
I just completed a MSL reset, a full wipe, and flashed the latest 198_7 sbf. Let's see if this resolves my rebooting and keyboard problems. If not, I'll try out one of joker's roms. If that still doesn't work, I'll go in for Photon #3.
@deedscreen: I'm sorry to hear you are on your 5th Photon. That is not encouraging to me.
Click to expand...
Click to collapse
Just to let you know ahead of time, the Full Wipe, MSL Reset, and latest 198_7 sbf, will appear to work, it will work perfectly fine for about a month and a half, like mine, and you will have the same issues all over again.
Just to let you know.
I'm about to go to the Sprint Customer Advantage Repair Center Store, for my 6th Motorola Photon 4G device. Motorola has supposedly fixed the problem. WE SHALL SEE.
I just have to do an SBF before I go to the Store. I did a battery modification and I want it reset to stock values.
Sorry to hear. It sucks to hear of others having such problems with the Photon. Myself and others have been lucky to just have the "normal" issues all smartphones have in common.
If I was in your shoes, each time I got a new phone it would be run stock for at least a week or two with no apps whatsoever installed (I know, I know...what is the point right?) just to see if the issues exist straight out of the box.
I hate to say it but I would have probably swapped the phone a few times and then moved to something else. At some point it just isn't worth it anymore.
Wonder if it is some type of voltage issue. Have you talked to Motorola about it and if so, what has been said?
deedscreen said:
Just to let you know ahead of time, the Full Wipe, MSL Reset, and latest 198_7 sbf, will appear to work, it will work perfectly fine for about a month and a half, like mine, and you will have the same issues all over again.
Just to let you know.
I'm about to go to the Sprint Customer Advantage Repair Center Store, for my 6th Motorola Photon 4G device. Motorola has supposedly fixed the problem. WE SHALL SEE.
Click to expand...
Click to collapse
Okay... that's really not encouraging!
However, I've never gone a full month with no problems so at least that would be progress for me!
Please let us know what happens with your 6th phone. Fortunately, I've never had a problem flashing SBFs. It will be interesting to see if you have that problem with your 6th phone.
CCallahan said:
Sorry to hear. It sucks to hear of others having such problems with the Photon. Myself and others have been lucky to just have the "normal" issues all smartphones have in common.
If I was in your shoes, each time I got a new phone it would be run stock for at least a week or two with no apps whatsoever installed (I know, I know...what is the point right?) just to see if the issues exist straight out of the box.
I hate to say it but I would have probably swapped the phone a few times and then moved to something else. At some point it just isn't worth it anymore.
Wonder if it is some type of voltage issue. Have you talked to Motorola about it and if so, what has been said?
Click to expand...
Click to collapse
I am devoted to the Photon, I love it's features, style, (MAINLY, I've puchased a bunch of accessories, and Sprint said that I can only get the HTC EVO Design 4G, or the Optimus, they are supposed to allow me to get a phone that is of equivalent specifications which is the Epic Touch SII Galaxy, which Sprint refused to give me.
Motorola says "We have never heard of anything like this, what are you talking about? This cannot be true!"
Those reps are quite frankly put, "stupid" in regards to the Photon and its technical difficulties. (Sorry if I offended any reps on the site.)
Sprint is trying to do the old "bait and switch on me"
I am willing to pay up to $100 price in differance, but I have put too much effort in the Photon and the Photon Forums here at XDA. After all, I am the creator of the Photon Fan Club Group here at XDA, (if you are not a member, look at my signature and join below.), I have created the Twitter, Google+ and facebook pages for this phone.
You know what I'm saying?
(By the way, I just SBF'd my phone without taking my microSD card out, and the SIM card, and I wanted to move all of my data before I sbf'd it. darn it. hope my sd card didn't get erased, I will be mad with myself if I did.)
well I just bought my photon 20 days ago from a guy on craigslist and yes it was brand new, never activated everything sealed for 250.
And so far the only thing I wasn't able to do was the update which a lot of people couldn't get their phones to update but I used the 198_7 SBF and that was it.
So far I only had 2 reboots (and that was when I was messing around with root explorer replacing some apks in the system folder)
But besides that I haven't had any problems that aren't normal on any android phone.
I read a few posts in other forums about bad batteries causing some of the problems we are facing. Therefore, I called Motorola and they are sending me a new battery for FREE! I pray this fixes everything. (fingers crossed)
sjamie said:
I read a few posts in other forums about bad batteries causing some of the problems we are facing. Therefore, I called Motorola and they are sending me a new battery for FREE! I pray this fixes everything. (fingers crossed)
Click to expand...
Click to collapse
Read the same thing. Motorola sent me a brand new battery, for free, but that did not fix the problem for me.
deedscreen said:
All of the same issues as myself? Now when you replaced it, did you have a problem upgrading to the latest software with the replacement?
Click to expand...
Click to collapse
New one came with 198_6 so I had no reason to update
Edit: yes mine was plagued with all the same issues
Sent from my MB855 using XDA App
deedscreen said:
Read the same thing. Motorola sent me a brand new battery, for free, but that did not fix the problem for me.
Click to expand...
Click to collapse
Damn, man! You are shattering all of my dreams today! jk
sjamie said:
Damn, man! You are shattering all of my dreams today! jk
Click to expand...
Click to collapse
I understand that I am literally shattering your dreams, (no need for saying joking).
It is actually true.
I am sorry about that.
EDIT: On the bright side you will have an extra battery! See now I made one dream come true at no charge to you. (LOL! Hey, that rhymed.) Hehe
Well, since 198_7 isn't official, isn't flashing that SBF actually taking you away from a stock experience?
Never had one random reboot. Maybe some apps or a not 100% working root you guy's applied to the phone? Mine is flawless.
Sent from my MB855 using XDA App
My phone began having issues with touch behavior. It has over time gotten worse to the point where my phone seems to have a mind of its own. I took it in to a sprint repair center because I have read that the digitizer is a common failure with the Evo 3D. Anyway the repair guy told me that the issue was because I am rooted, that root corrupts files necessary for correct touch input. I have never herd this before and wanted to ask if anyone can either confirm or deny this. I would like to specifically read some developers perspective on this.
IXKastling said:
My phone began having issues with touch behavior. It has over time gotten worse to the point where my phone seems to have a mind of its own. I took it in to a sprint repair center because I have read that the digitizer is a common failure with the Evo 3D. Anyway the repair guy told me that the issue was because I am rooted, that root corrupts files necessary for correct touch input. I have never herd this before and wanted to ask if anyone can either confirm or deny this. I would like to specifically read some developers perspective on this.
Click to expand...
Click to collapse
Completely untrue. Rooting voids warranty and so that's why he came up with that excuse. Just unroot (this guide is good), and then take it to the sprint store again and don't say anything about root. they should give either a replacement or replace the digitizer. Then you can just root the new phone or root again.
Well the surprising thing is he gave the phone back to me and said he had ordered a replacement phone and that they'd call me when it arrived. This is why I asked, because I wanted to know whether to root my new phone when it came in.
He gave the phone back to you and ordered you a new one at no cost to you because that's just a trick reps play..
Root had no effect on screen wear and tear or digitizer failure..
Sent from my PG86100 using XDA
This just goes to show that you should read and research before modifying your device. No root has no effect on hardware.
#Root-Hack_Mod*Always\
I started having serious screen errors after flashing the VM firmware. I tried the fix, and it didn't work for me. Looking at a multi-touch test, it's showing four touch points in the middle when I'm only touching it once at the top.
flomexico said:
I started having serious screen errors after flashing the VM firmware. I tried the fix, and it didn't work for me. Looking at a multi-touch test, it's showing four touch points in the middle when I'm only touching it once at the top.
Click to expand...
Click to collapse
Unfortunately that's what happens when people flash hacked/leaked firmware. Rooting itself doesn't cause hardware problems, but flashing things like this does. Hopefully someone will come up with a fix to fully reverse it. If not, hopefully you have insurance.
mreyesems said:
He gave the phone back to you and ordered you a new one at no cost to you because that's just a trick reps play..
Root had no effect on screen wear and tear or digitizer failure..
Sent from my PG86100 using XDA
Click to expand...
Click to collapse
Do you mean that I could get billed? Or what would be the purpose of the trick?
IXKastling said:
Do you mean that I could get billed? Or what would be the purpose of the trick?
Click to expand...
Click to collapse
They could bill you for service w/out warranty but only if you tell them to.
Sometimes they say things like that because they don't want to go through the hassle of ordering a new phone for you, especially since they don't earn any commission for that kind of help.
Also, technically if you are rooted your warranty IS voided, even though a lot of the time hardware problems aren't related to root at all. I guess what I'm trying to say is they technically aren't aloud to replace a non-warrantied item so they make up a reason why they can't in order to keep the customer at least somewhat understanding.
sitlet said:
Unfortunately that's what happens when people flash hacked/leaked firmware. Rooting itself doesn't cause hardware problems, but flashing things like this does. Hopefully someone will come up with a fix to fully reverse it. If not, hopefully you have insurance.
Click to expand...
Click to collapse
Yup, my impatience screwed me over. I'm probably gonna end up bricking it.
In relation to the thread, rooting doesn't do anything. So yeah, you got got.
Yea, I had the same problem and the store said the same thing. Like others said, it's untrue. The stores will try to avoid the issue but phones should be replaced.
Sent from my EVO 3D on ICS using XDA
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: