I still haven't gotten the ota for nexus 7 2013. Anyone else see it yet? It has been out for over a month now.
I did get the 5.1.1 update about 4 months after google released it. Now that 6.0 is officially out I expect it to be about 4 months before I see 6 with VZW track record.
Same situation here. Verizon upgraded some of their Nexus 7 (2013) LTE's to Lollipop 5.0.2, then heard about problems and stopped that OTA rollout, I hear from the rumour mill.
Now they went and rolled an OTA in August to update KitKat to Lollipop 5.1.1.
But they have seem to have abandoned those of us on 5.0.2, since it is now October and they haven't upgraded 5.0.2 to 5.1.1 yet.
This poor customer and technical support makes me think I need to move all my services to T-Mobile or AT&T.
One could try manually installing the update. It is available.
I'm most definitely NOT a VZW employee. If a post answered your question, please mark it as the answer.
@Ann154
At 65 years old, I don't think I want to learn how to sideload an OTA that is supposed to be available Over-The-Air, and run the risk of bricking my Nexus 7 LTE 2013 purchased directly from Verizon. They should provide the support for it, rather than ignoring their customers. I am in the same boat as the folks above, stuck at 5.0.2, and Verizon will not provide the 5.1.1 update Over The Air.
Additionally, I understand that not all OTA's for this model are the same: some are uniquely for T-Mobile models and some for Verizon models of the same tablet. The OTA I need over the air is the Verizon approved one which Verizon had Google customize.
Maybe trenton2008 is right. Time to move all my service from Verizon to T-Mobile... Very frustrating.
OTA has the same risks as sideloading. It's actually safer to sideload than OTA.
@tidbits
My money too was paid to Verizon for it. The tablet has their logo on it. They have an obligation to support what they sell. Wonder how many people are affected? Enough for a class action lawsuit?
You paid Google for it even it was through Verizon. They don't make money off devices like you think they do.
I ended up sideloading the OTAs from LRX22G(5.0.2) up to LMY48L(5.1.1) the day before 6.0 started rolling out. I immediately received an OTA to LMY48P after that, but haven't gotten LMY48U (5.1.1 security patch) or MRA58K (6.0) OTA yet. I'll wait for a 6.0 OTA for a bit, then sideload again if it doesn't show up fairly soon. I don't mind leaving a little time for any major issues to show themselves.
The sideload process is pretty simple, and there are at least a few easy to follow guides for doing it. You just need to have right OTA update file that is for your existing build number, which is easy to see on your device. And the Nexus builds are now unified, meaning that the 6.0 builds don't have carrier-specific versions.
I did just get the security patch for 5.1.1 yesterday
I got the latest 5.1.1 (LMY48U) earlier today. But no 6.0 for either my Nexus 6 or 7. I've not even received the monthly security update for my phone.
That should be with the security update as 5.1.1 is what I'm on and have been on for about a month, But I did get a system update 2 days ago. The LMY58U is the version I'm on now
The LMY58U update is the more recent version before the 6.0 OTA
I'm most definitely NOT a VZW employee. If a post answered your question, please mark it as the answer.
Odd way to force some OTA's to update your Nexus 7 LTE 2013 successfully employed:
Had read on another forum (XDA? Howard Forums? Google? - I just don't remember) that putting another carrier's SIM card in the Nexus 7 can automatically initiate OTA updates, so I purchased a T-Mobile internet data LTE SIM which I installed after removing the Verizon SIM. The tablet immediately on boot found Android OTA update to upgrade 5.0.2 to 5.1, which I installed. Reboot, and 5.1.1 OTA found available, so I installed it. After that, 3 small bug fix/security updates have been installed via OTA. My tablet is now at 5.1.1 LMY48U. No sideloading, no rooting, no factory reset needed.
Personally, I think Verizon, who sold me this tablet, should have known and been working on a solution to tablets they sold with Verizon SIM cards which were stuck at old OTA versions Unfortunately, Verizon's lack of customer support has been extremely disappointing. Why would Verizon's active SIM prevent OTA updates beyond 5.0.2, yet swapping the Verizon SIM for a $0.99 T-Mobile one, allows OTA updates, is something Verizon should have discovered by now and advised the community of Verizon subscribers.
I am now debating if I should move my cellular business to another carrier due to Verizon's poor performance. But in the mean time, I am glad to provide this OTA update work-around to anyone who can use it.
I think that should work without using another SIM. Just remove the Verizon SIM and connect via wifi only. The tablet is fully functional with no SIM installed, it just won't have mobile data service.
The SIM swap/removal is certainly more convenient (especially for the non-tech savvy) than sideloading. Though sideloading the OTAs isn't as bad as installing the full factory images. It has a few less steps and doesn't require unlocking the bootloader or wiping the device. Getting windows to properly see the device in recovery mode is likely the trickiest part of the process.
The entire situation is really sad. There is no excuse for Verizon to have left customers on the 5.0.2 build they stopped rolling out. All they had to do was approve the OTA update from the problem 5.0.2 build to 5.1, in addition to the 4.4.4 to 5.1 OTA. Stopping that rollout was the right call to prevent people from bricking their tablets, but you can't simply act like no one installed that build and ignore approving any updates to it.
@trenton2008
@mr_stealth
Kudos to @trenton2008 for the creative solution he posted above which by-passes Verizon's negligence. I went today to a local T-Mobile store and bought a 3 in 1 data sim. Went home and tried the steps he laid out and "shazzam!" I am now running Android 5.1.1 (LMY48U). Thank you very much! NO SIDELOADING, NO FACTORY RESET, NO BACKUP RESTORE, NO LOSS OF ANY DATA!
@mr_stealth posts an interesting question about just removing the Verizon sim without swapping in the T-Mobile one, but I didn't think to try that, not having seen his post until now. Maybe someone can try that. I did try to boot my tablet without any sim just to see if I could get the OTA for LMY58U that @Ann154 mentions, but nothing Over-The-Air was received either with or without any sim for that build.
After this bad experience with Verizon, I too need to decide if I should move onto another provider, even if it is one that uses Verizon's network like PagePlus Cellular, Selectel Wireless, or PuppyWireless, which will at least reduce the $$$ I give Verizon.
The update after LMY58U is MRA58K (6.0), which should still be going through rollout stages from Google. I don't know if anyone with a Verizon device/SIM has received that one yet. MRA58K was the end of carrier-specific builds, so it's hard to tell how that will impact Verizon's approval process for rollouts.
I haven't even received the 6.0 OTA yet on my wifi only Nexus 7 tablet.
I'm most definitely NOT a VZW employee. If a post answered your question, please mark it as the answer.
Losing a long time customer is heartbreaking, TatankaHota. We want to repair our damaged relationship. Was the issue with receiving the newest software the reason you want to leave, or are there other issues that are unresolved? Please tell us more.
LynnD_VZW
Follow us on Twitter @VZWSupport
If my response answered your question please click the �Correct Answer� button under my response. This ensures others can benefit from our conversation. Thanks in advance for your help with this!!
I think it's the same issue that this thread was created tor. The fact that Verizon's update approval process greatly delays, and in many cases completely blocks, users from receiving updates. If this can be worked around for those experiencing severe delays (even long after Verizon has approved/rolled out updates), support really should inform users of temporarily removing the device's SIM to accomplish that.
The absolute worst case of this was how Verizon handled build LRX22G (5.0.2) for the Nexus 7. I understand that the build had some major issues, and that its rollout needed to be stopped. But many customers (like myself) did receive that update during its brief availability. When 5.1.1/LMY48L did roll out in mid August, the only customers receiving it were those still on 4.4.4. Anyone that had installed 5.0.2/LRX22G was stuck on that build unless they sideloaded or removed/swapped their SIM card. Verizon completely failed to approve/push the updates to get from 5.0.1/LRX22G to 5.1.1/LMY48L, leaving us stranded on a build that was known to potentially render devices useless.
Making this entire situation worse, is the fact that his all happened during a time when the series of Stagefright exploits were still being patched. So not only were customers stuck on a build that had the potential to brick their device, but were stuck on a build that had major known security vulnerabilities that Verizon was preventing them from patching.
Verizon's current rollout process for Google's monthly security updates does seem to be much improved over other update rollouts. But there is still much work to be done to insure that those updates get approved for all builds that customers could potentially be running. I did receive build LMY48U quite promptly after Google released it, but only because I had forced my tablet (via sideloading multiple OTAs) to update from LRX22G to LMY48L. Had I not done that, I would have been stuck on LRX22G indefinitely.
Last night I received OTA 6.01 on my Nexus 7 LTE 2013
I got that as well about 2 weeks ago
Start a new topic or ask questions in the open forum.
