Related
Hey all,
I just got a replacement g tab from Woot today and I charged it an turned it on....it is at version 3389 and I can not get it to update to 3588. I have wifi connected and can access the web, etc... I've tried rebooting 5 times now and have tried the manual updating in the app tray and it says its up to date with 3389. Any ideas what is going on? I'm hoping maybe just viewsonics site that supplies the updates is down but not sure how I can verify that. I'm really hoping I don't have another g tab with issues....
barcod21 said:
Hey all,
I just got a replacement g tab from Woot today and I charged it an turned it on....it is at version 3389 and I can not get it to update to 3588. I have wifi connected and can access the web, etc... I've tried rebooting 5 times now and have tried the manual updating in the app tray and it says its up to date with 3389. Any ideas what is going on? I'm hoping maybe just viewsonics site that supplies the updates is down but not sure how I can verify that. I'm really hoping I don't have another g tab with issues....
Click to expand...
Click to collapse
Search for homebrew on the site here as it has all the stock ROMs
I had the same issue with a replacement I got today. Just used the stock one from the Dev forum. Do not know what is going on. Probably just a down server.
clintre said:
I had the same issue with a replacement I got today. Just used the stock one from the Dev forum. Do not know what is going on. Probably just a down server.
Click to expand...
Click to collapse
Hmm... down update server? Could it be viewsonic is gearing up for its next OTA? Rumor has it pegged for arround this time.
Thanks for the fast replies. Do you think that this problem is not a hardware issue? I wouldn't think this is hardware related and lean toward a problem with viewsonics servers as we'll, but I don't want to keep this tablet if it has a issue..... I see the stock Rome when I search for homebrew so that's easy enough to flash if nobody thinks this tablet has any hardware problems.
Possibly a new udpdate? Wouldn't THAT be nice.
Time to test that theory! Going back to stock to see what happens with the OTA.....
EDIT: INTERESTING. I just dropped 2967 on mine (nvflash) and it says there's no update. That should not be the case. Methinks there's something going on.....
EDIT2: Nothing on 3588 stock either (no updates). But will leave my device that way, for now.
I just got 2 gtabs from woot today and both are doing the same thing, stuck at 3389 and will not update. Even tried volume + and power on. Did not help. Thought maybe was cuz I am in Canada.
I guess the good news is it sounds like I don't have a hardware issue! I'll keep my fingers crossed for a new update from VS.
roebeet said:
Possibly a new udpdate? Wouldn't THAT be nice.
Click to expand...
Click to collapse
Yes it would then maybe Adam from VS could move on with his quest for a developer involved movement as requested last month? This would be the best place instead of starting a new place on VS web page
But for bandwidth usage they should use there service.
Reflashed mine back to stock 2967 earlier today and it wouldn't wouldn't do the OTA either. Kept saying it was up to date and never had that problem until today. Hope they are planning something nice for us.
I actually just got mine and it has 1.0-2638 and it's saying it's up to date
so having not done an OTA update, can I still install Vegan 5.1?
just got my Gtab from woot. for some strange reason, I didnt't get the whole setup screen on plugging it in and turning it on, mor did I get notice of an OTA update after getting the wifi going.
can I go ahead and load Vegan 5.1 anyway with the 3389 on it?
also, but perhaps tangential to this thread, which Kernel if any should I install on the Vegan 5.1? Clemsyn? Pershoot?
after the Vegan is installed, will it do a setup all over again? I'd like that.
my first post!
thanks!
My guess is that everybody that got their Gtab today from the woot is trying to download the update and it might have crashed the viewsonic update servers. Guessing Viewsonic wasn't expecting thousands of peeps trying to download updates all on the same day and didn't prepare. Or..........I could be totally wrong and they are getting the server ready for a Honeycomb realease?
I think most of them were received last week, there shouldn't be a huge number of new users.
Barcod - did you have to send your old tab back first before woot send out the new one? I ordered a replacement and really hope it doesn't have the same sound issues.
kaffeesnob said:
Barcod - did you have to send your old tab back first before woot send out the new one? I ordered a replacement and really hope it doesn't have the same sound issues.
Click to expand...
Click to collapse
Nope, Woot sent me an advanced replacement and shipped it out the day they received my email about the audio problem. They were a pleasure to deal with. I still have the old tab to send back to them which they provided a shipping label for that as well.
This is pretty annoying, I cant even manually update using the thread located here.
agentstatic said:
I actually just got mine and it has 1.0-2638 and it's saying it's up to date
Click to expand...
Click to collapse
Was that a Woot one or a Tiger Direct one? I would call VS Customer Service TODAY and ask them to please have them ask TapnTap Inc to fix the OTA updater ASAP. 2638 is probably the original firmware and it is NASTY bad. Buggy as all hell.
If they can't do anything, you should at least do a stock update via the instructions here: http://forum.xda-developers.com/showthread.php?t=842000.
idivorceyou said:
just got my Gtab from woot. for some strange reason, I didnt't get the whole setup screen on plugging it in and turning it on, mor did I get notice of an OTA update after getting the wifi going.
can I go ahead and load Vegan 5.1 anyway with the 3389 on it?
also, but perhaps tangential to this thread, which Kernel if any should I install on the Vegan 5.1? Clemsyn? Pershoot?
after the Vegan is installed, will it do a setup all over again? I'd like that.
my first post!
thanks!
Click to expand...
Click to collapse
3389 should be safe to use as a baseline.
I cant get the recovery firmware thing to work, (i am a noob at this)
I managed to get 2967 on but I didn't think it would work but it did.
agentstatic said:
I cant get the recovery firmware thing to work, (i am a noob at this)
I managed to get 2967 on but I didn't think it would work but it did.
Click to expand...
Click to collapse
That's our old homebrew one. You can use that command file with the newer zips on the link. Just rename the newer zip to "update.zip".
Given the number of new systems being shipped recently, this is pretty irresponsible of TapnTap and they really need to fix that ASAP. Their OTA updater is the ONLY "official" way to get updates, and it's been down since last night.
Maybe they have given up on our beloved g-tabs
Swyped from my St0n3d VEGAn 1.0 Beta 5.1.1 G-Tab
Update Failure from 45.2.7 to 45.3.6 SOLVED!!!!
LOTS of people who purchased NEW Photons in the past few weeks have phones that shipped with a faulty image from the factory. These phones shipped with Software Version 45.2.7, but are ABSOLUTELY UNABLE to upgrade to 45.3.6. Anytime you try to update, the installation stops at 30% and quits. The common error message has something to to with the AccountAndSyncSettings.apk file.
I've figured out a FIX to the update failure. It may seem like it's a bit risky, but if you're on the last day of the 14 after initial purchase when you can swap out the phone no questions asked, it's worth a try. Actually, it's pretty simple without a lot of heavy lifing. Keep in mind, the phone this worked on had very few apps installed and was NOT rooted. I work in the IT field, but have NEVER done any modding - and I found it quite easy to do.
Some Background: My phone was purchased NEW direct from Sprint on 10/08/2011. It came with software version 45.2.7. When attempting to upgrade to 45.3.6, I received the now infamous error that has something to do with the AccountAndSyncSettings.apk file. Tried EVERYTHING the first few days with the phone - no upgrade success (about 15 factory resets). Made multiple posts on this board and read all of the responses for days. NO UPDATES from Sprint or Motorola. So, I took the phone back to a Sprint store for a 'no questions asked within 14-days exchange'. Never activated email, didn't even sync my contacts. Just went straight to the update. The new phone was also a 45.2.7 Software Version phone, and as you can probably guess, Update Failed on the 2nd phone as well. Went to THREE Washington, DC area Sprint authorized repair facilities to see if they can 'manually' update the phone, or even re-image the phone. Sprint was USELESS!!! Not only did the 'technicians' (and I use that word VERY loosely) not know anything about our problem, they had NO means to manually apply an update or write a new base SBF (system boot file) to the phones. Finally, after sitting in traffic coming home from work today, I had reached my breaking point.
The Fix: After days of scouring websites and phone calls to Motorola and Sprint (those were nothing more than a waste of cell minutes), I figured maybe I could mess with it myself. I had been hesitant because I was afraid of 'bricking' the Photon and then I'd have nothing more than a $200 paperweight. Then it hit me. What if it was already 'bricked'? Somebody has had to have done it to their Photon already. If they had, they must have looked for a solution. If there was a 'recovery solution' for a bricked Photon, maybe that fix may solve the problems we are all having with our BRAND NEW Photons.
Searching last night, I found a link from a few months ago. As a new member, I'm not allowed to post the link. But if Google these exact words, the VERY FIRST return is a page from the AddictiveTips website.
Came home from work, poured myself a cocktail and I went to work. First I downloaded the SBF. Now this takes the phone back to the version PRIOR to 45.2.7 (sorry, forgot to write that down when taking my notes). When you follow the link to download the SBF, there are a bunch of link options. Some have been taken down, others are still working. The file you want to download is 471MB and has this filename:
1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-154_5-CM-release-keys-signed-Sprint-US
Then I downloaded the RSDLite software and drivers. I used a 32-bit Windows 7 laptop and installation went without a hitch. There are 64-bit drivers, but I'm not sure how they work. I did read where 'some' people had problems with the 64-bit varieties, so that's why I made a point of doing it on a 32-bit PC. From there, the instructions on the above listed link worked PERFECTLY.
There are a few things to keep in mind. BE PATIENT. This does take a while, and there were a few times that I wondered if something went wrong. It may hang at some stages for a few minutes, be patient.
Once I flashed the phone with the SBF and it was done installing and rebooting, (much to my amazement) all of my apps and customizations were in tact. I pulled my SD card to be safe, but I suspect it wouldn't have messed up my SD card. I would pull it prior to flashing just to be safe. If you want to take one extra step just to ensure success, you could do a factory Reset PRIOR to doing the flashing. I didn't have to, but it probably wouldn't hurt.
Literally seconds after it booted into the OS for the first time post SBF flashing, I was alerted to a software update: Update 45.2.7 (6.5MB). Downloaded rather quick and promted me to install now or later. I pressed install and away it went. Once again, be patient. It takes a few minutes. The progress bar moves rather steadily until it reaches 75%. Then it appears to stall/hang there for a few minutes. Then, the install progress bar vanishes and the OS boots up. A few seconds later, I got the message "Software update was successful. Your phone has been upgraded to 45.2.7". I went to SETTINGS, ABOUT PHONE, SYSTEM UPDATES and queried for additional updates. Sure enough, 45.3.6 was available. Forgot to document the file size. Downloaded and clicked INSTALL. Much like the previous update, progress moved steady till about 75%. Then progress bar and Android character vanished and the phone booted into the OS. About a minute later, the words I have been looking for for over a week:
"Software update was successful. Your phone has been upgraded to 45.3.6"
Queried software update again, and it said your phone was UP TO DATE. Yipee!!!!
I was getting NO SOUND. I think it was beause I inserted the SD card while the phone was still powered on. So, I rebooted the phone and EVERYTHING works perfectly.
If you want to wait for Mark (forum manager) to come up with a fix, I understand. In fact, it's probably the right thing to do. But if you're beyond frustrated (like I was) in the lack of information and lack of solutions from Sprint or Motorola; and want to take matters into your own hands; this worked for me.
do u happen to have a link for the 64 bit drivers ?
I'm unable to locate one.
Thanks for your help.
daddymikey1975 said:
do u happen to have a link for the 64 bit drivers ?
I'm unable to locate one.
Thanks for your help.
Click to expand...
Click to collapse
See here.
http://forum.xda-developers.com/showthread.php?p=18642169
This method has been on XDA for some time. The sbf of 198_6 was even posted way before Motorola started to push it out. Just takes a peek into the dev section.
Glad you got it working.
Thanks!
This has worked for me.
I just followed the instructions.
@OP - Thank you so much! I had a slow, laggy Photon with the "Sleep of Death", and needed to get it to update so that I wouldn't experience that issue anymore.
I followed your instructions, and got the phone working again. At one point, I wanted to throw the phone at a wall.
Now, I love my MoPho.
Thanks for making me fall in love with my phone all over again!
By the way, you are a Junior Member, this is your first post, and I gave you your first thanks. You are very intelligent, I must say! I am very proud of you. Your first post, and you did something this amazing! I must say, you are a genius! You will make a great Senior Member, it takes time to become a Senior Member, and you will make a great one! Very proud of you. Thanks a lot! I really appreciate it !!!
Motorola has re-issued the 198_6 build to address this problem. Also, 198_7 is available in the MoPho dev subforum
tbhausen said:
Motorola has re-issued the 198_6 build to address this problem. Also, 198_7 is available in the MoPho dev subforum
Click to expand...
Click to collapse
Well for me it does not fix....still the same old fail at about 30% install
Sent from my MB855 using XDA App
After failing 4 dozen times, I can happily report that the update FINALLY works!
HAPPY HAPPY JOY JOY!!
Riggy
I'm glad that it works. I used the same method, had a few issues but eventually got it to work.
Fyi...the NEW ota still did not work for me....spoke to sprint who spoke to moto tech support....moto wanted me to send them the phone (and be without a phone for week while they played around...sad moto..very sad)
Sprint is replacing my phone for free..good on Sprint
As for moto..this will be my LAST! moto phone..their service on this whole issue has been bad...and the joke of a support forum and "Mark" motos party line [email protected]%$!!!!...kiss my
... bye
Sent from my MB855 using XDA App
For some reason, my TFP canot find the update; it keeps telling me that "There is no update available for your device currently."
Any ideas?
Do you have a serial number on your unit?
I couldn't get updates and I think it was b/c I didn't have a s/n showing in my unit. I returned it and bought a new one. All is good now.
http://forum.xda-developers.com/showthread.php?t=1426881
I'm not sure if check update is actually the same thing. I just got a notification after waiting - whenever I tried to poll manually, i got no update. Who can tell...
NeoteriX said:
For some reason, my TFP canot find the update; it keeps telling me that "There is no update available for your device currently."
Any ideas?
Click to expand...
Click to collapse
My daughter is having the same issue. Her firmware is only at .27 and when she checks for updates in settings, there is nothing. She also has not gotten the ICS upgrade. Should she wait or manually download the firmware update?
This is our first exposure to Android, so any advice would be appreciated.
Since there seems to be a fairly high chance that the update introduces some stability issues, take the time to get used to android and don't worry too much about the update - it's fairly minor improvements. Anything you install should be kept during the update.
You should check that you have a serial number though (settings, about - at the bottom of the list)
Well, I can ask about her serial number, but my serial number is not listed and my Prime firmware and OS was upgraded without issue. It's not a big deal for her to wait, but I am wondering what is the catalyst that triggers the automatic upgrades? Is it done over a certain amount of time? (She got hers a week after I got mine.)
Does anyone know?
jonalisa said:
Well, I can ask about her serial number, but my serial number is not listed and my Prime firmware and OS was upgraded without issue. It's not a big deal for her to wait, but I am wondering what is the catalyst that triggers the automatic upgrades? Is it done over a certain amount of time? (She got hers a week after I got mine.)
Does anyone know?
Click to expand...
Click to collapse
Go into the SETTINGS in your PRIME then click on STATUS. If it says "Serial Number Unknown" then your sister will not be able to update to any of the firmwares, including ICS Android 4.0 or any updates Asus released before ICS.
I would guess yours actually shows a Serial Number if you are getting updates. Otherwise, there would be no way to get OTA updates.
Also, if your sister updates manually, she will always have to update manually. And that is a pain. Asus doesn't put up the actual firmware files for many days after they are sent OTA. For example, you still cannot download ICS Android 4.-0 from Asus' website, although it was release a few days ago.
3rdamention,
I did not know to look under status...mine is fine, but I will have her check hers. So, if the SN is missing, what is the resolve? I got hers at Office Depot which has been a nightmare of incorrect charges.I hope I won't have to deal with them again.
So far, no fix at all. Mine is going back to Best Buy!
If you have this problem, you cannot run certain applications, one I believe is Google Video. You cannot do OTA Firmware Updates, and you cannot root the tablet if you ever wanted to.
There is no fix right now, and Asus hasn't been any help whatsoever.
Here is a nearly 20 page thread about it if you need some friends or shoulders to cry on if you find your sister's has this issue. Plus this thread may be a decent read to acclimate you to this bug.
http://forum.xda-developers.com/showthread.php?t=1426881&highlight=serial+number
I'm having a similar issue... My TPrime has a serial number in the status, and on the 9th I got a notification that there was a firmware update available, so I hit update, TPrime rebooted, but the install messed up and just had an android guy with a yellow triangle with an exclamation mark. Once it rebooted, it reverted back to Honeycomb, and now I can't find the update again. I've even gone so far to wipe my TPrime, which took it back to .27, and had to manually update to .33, since it wouldn't even find that update...
I called Asus about it, and they said that the update had been recalled, and I should get it whenever they re-release it.
Anyone else have anything like this?
Check this thread
jonnybsay said:
I'm having a similar issue... My TPrime has a serial number in the status, and on the 9th I got a notification that there was a firmware update available, so I hit update, TPrime rebooted, but the install messed up and just had an android guy with a yellow triangle with an exclamation mark. Once it rebooted, it reverted back to Honeycomb, and now I can't find the update again. I've even gone so far to wipe my TPrime, which took it back to .27, and had to manually update to .33, since it wouldn't even find that update...
I called Asus about it, and they said that the update had been recalled, and I should get it whenever they re-release it.
Anyone else have anything like this?
Click to expand...
Click to collapse
There is a whole thread / solution listed here:
http://forum.xda-developers.com/showthread.php?t=1437607&highlight=yellow+triangle
Or try this guide (better) for Failed ICS Update:
http://forum.xda-developers.com/showthread.php?t=1437285
jonnybsay said:
I'm having a similar issue... My TPrime has a serial number in the status, and on the 9th I got a notification that there was a firmware update available, so I hit update, TPrime rebooted, but the install messed up and just had an android guy with a yellow triangle with an exclamation mark. Once it rebooted, it reverted back to Honeycomb, and now I can't find the update again. I've even gone so far to wipe my TPrime, which took it back to .27, and had to manually update to .33, since it wouldn't even find that update...
I called Asus about it, and they said that the update had been recalled, and I should get it whenever they re-release it.
Anyone else have anything like this?
Click to expand...
Click to collapse
That is crazy, the previous 3 days they have denied that it was ever released. Now they say it is recalled? How could it be recalled if it was never released? Asus is cracking me up!!
SmartAs$Phone said:
There is a whole thread / solution listed here:
http://forum.xda-developers.com/showthread.php?t=1437607&highlight=yellow+triangle
Click to expand...
Click to collapse
I tried that solution, and the one linked from that thread too. Those basically tell you to re-install the .33 firmware, then update to ICS (without specifying how, but I'm assuming it would just show up for them), and are aimed mainly for people who were rooted and had deleted bloatware. I wasn't rooted or hadn't deleted anything, and still can't find the update again.
I'm one of the no serial number people and cannot get updates. I noticed i wasn't getting updates right after Christmas and called Asus as soon as .33 came out, and they gave me the same bullcrap about it having been recalled even though everyone else was getting it. I think that's just their standard response to shut you up and get you off the phone.
Munkee Boy said:
I'm one of the no serial number people and cannot get updates. I noticed i wasn't getting updates right after Christmas and called Asus as soon as .33 came out, and they gave me the same bullcrap about it having been recalled even though everyone else was getting it. I think that's just their standard response to shut you up and get you off the phone.
Click to expand...
Click to collapse
So you have been on Stock Firmware now since you owned it in December? Sorry brother, that really stinks. At least for me it has only been this week.
That is one of my biggest complaints. You see people saying they haven't' been able to update since before Christmas. Now here we are on January 12th, Asus hasn't helped anyone, they tell them there have been no firmware updates. I seriously think they are buying time. Either they are close to a "Serial Problem Unknown" fix, or they want you to hold it past the return date so you have to send it to Asus, they keep your money, and they can just ship you a replacement.
There is a 20 page thread of people all considering taking their Primes back because of "Serial Number Unknown", but nobody from Asus is trying to help, PMing them, or anything.
jonnybsay said:
I've even gone so far to wipe my TPrime, which took it back to .27
Click to expand...
Click to collapse
I find that hard to believe. wipe doesn't usually touch /system
tshoulihane said:
I find that hard to believe. wipe doesn't usually touch /system
Click to expand...
Click to collapse
Now that I think about it, I'm not too sure about that either... I was assuming it did since after I wiped all data, I had the .33 firmware on my microsd card, the tablet recognized it saying there was an update available, and reinstalled that firmware. But either way, the check update keeps telling me there is no update available when I'm with .33.
3rdamention said:
So you have been on Stock Firmware now since you owned it in December? Sorry brother, that really stinks. At least for me it has only been this week.
That is one of my biggest complaints. You see people saying they haven't' been able to update since before Christmas. Now here we are on January 12th, Asus hasn't helped anyone, they tell them there have been no firmware updates. I seriously think they are buying time. Either they are close to a "Serial Problem Unknown" fix, or they want you to hold it past the return date so you have to send it to Asus, they keep your money, and they can just ship you a replacement.
There is a 20 page thread of people all considering taking their Primes back because of "Serial Number Unknown", but nobody from Asus is trying to help, PMing them, or anything.
Click to expand...
Click to collapse
The funny thing about my prime is that was originally on 8.8.3.23. I haven't seen anyone else with that firmware revision, the lowest i've seen anyone else at is .27. I have manually updated to .29 with an sd card, but have held off on .33 because of the troubles others have had.
You're right, I haven't seen anything about ASUS working to solve this problem, and more and more people are cropping up with this issue. Where is Gary King from Asus on this one? He seems to be PM'ing people on the site about different issues to get resolved, but nobody with this issue has been contacted by him. I don't think it's high on their priority list, which sucks because none of us can get ICS. They obviously monitor these boards, yet we continue to be ignored.
OP: this happened to me last night.
But about half and hour later it started downloading the new update and then was ready to install. :/
Havnt had any issues since.
Dont have my prime with me atm, so i cant list serial, fw version etc.
Will post up later
So after my wife complaining how annoyed she is with the OTA request popping up every 12 hours, i decided to get her phone to accept. She was on a 4.0 version of AOKP, so i safeboot restored her stock rom and uninstalled safeboot.
the update went well but now she has no 4g and cannot send any emails. Is there a fix for this? I found one thread where people said there is no fix as somehow the hardware got corrupted (apparent happened to a lot of people). Some people were lucky and were still under warranty and others just bought a new phone or got one from ebay. Well shes just over a year so the warranty is out of the question, and we cant really afford a new phone at the moment.
This is kinda bull**** as she had an LG ally before this that broke with an OTA and verizon refused to do anything about it.
Hopefully there is some workaround.
vaeevictiss said:
So after my wife complaining how annoyed she is with the OTA request popping up every 12 hours, i decided to get her phone to accept. She was on a 4.0 version of AOKP, so i safeboot restored her stock rom and uninstalled safeboot.
the update went well but now she has no 4g and cannot send any emails. Is there a fix for this? I found one thread where people said there is no fix as somehow the hardware got corrupted (apparent happened to a lot of people). Some people were lucky and were still under warranty and others just bought a new phone or got one from ebay. Well shes just over a year so the warranty is out of the question, and we cant really afford a new phone at the moment.
This is kinda bull**** as she had an LG ally before this that broke with an OTA and verizon refused to do anything about it.
Hopefully there is some workaround.
Click to expand...
Click to collapse
my friend can you try doing rsd lite with fastboot files again like a clean install of the jb update using fastboot files and see if that helps or not. sometimes the ota is corrupted but the fastboot install fixes them. try and let me know thanks
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: