Is there a limit to the number of times Sprint will push an OTA update to a specific phone?
I'm not receiving the MDL update anymore, and manually checking says I'm up-to-date, but I'm not being at MDC. I received it the first time and installed it, but as we all know, it broke root access and closed the motochopper exploit. So I reflashed the stock ROM and wiped everything, got the update again but ignored it. Well, I reset my phone again, and now that I actually want to install the update, Sprint doesn't seem to want to push it to my phone anymore.
Edit #1: Saw this thread: New Update is here! Here is how to force pull an OTA update. But I am still curious why Sprint isn't sending it to me automatically if anyone knows.
Edit #2: Woke up this morning and the update had been downloaded. *shrug*
Hey guys,
I have a tmobile note 4 with COD6 and was wondering I'd it would be safe to update to COG2 and keep my root without any issues? I'm going to have to update via kies, which I have never done before due to the OTA option stating that since I made unauthorized changes to my device I will have to do a manual update. Have any of you already done this and had/experienced any improvement's or issues?
Long story short, my Nexus 6P will not update to 7.0. I just got the OTA update notification today but when I downloaded it and waited forever for it to optimize my apps, my phone boots into 6.0.1. I tried getting 7.0 from the android developer program about a month ago and I was able to download it then too, but again, the phone just goes back to 6.0.1 for some reason. I decided to just wait until I get the OTA but the problem has still persisted. Any ideas on why its stuck on 6.0.1? Any way to fix this?
Also, I bought this phone about 1 and a half months ago used from eBay. It has been working perfectly fine. Just wanted to put that info out there.
It's possible you bought the phone rooted and/or with a custom ROM or recovery? If you aren't completely stock, an OTA update will fail. This isn't necessarily a single 'right' answer question, but you should probably flash the factory image for a completely fresh install. Grab the factory image at https://dl.google.com/dl/android/aosp/angler-nrd90u-factory-7c9b6a2b.zip and follow the guide, section 14 at http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 and you should be able to update.
I just got the 7.0 OTA myself completely stock and when it rebooted it's still on 6.0.
Nobody else is having this problem?
I think you've both misread the update info. I received MTC20L update yesterday, which said that it contains September security patches and also prepares the device for Android 7.0.
The update never claimed that your device will update to Android 7.0. But don't worry, we'll get it soon, at least I hope so!
MTC20L is the Aug security update and the factory image has been posted for 1.5 months, so odd that you're getting it now. Most people would have been receiving N OTA updates. The only way for us to guess what is going on with the OP is if he edits it to include the build number.
I also just got MTC20L yesterday.6.0.1. No idea why no 7.0. Waiting sucks..........It's been a month since "rollout".
It's true I didn't read what the update was yesterday, but I'm 95% sure it had something with "7.0" on there. How do I know what I installed yesterday? I'm on 6.0.1, with the Sept 6 security patch, and MTC20L.
MTC20F was the August update, MTC20L is September one, released 6.9.
I took the developer preview (mistake as it was a hassle that I had to fix) but remember guys, Android N updates in the background, so while it reboots to update, it doesn't take forever with the whole "android is upgrading" screen. I got the NRD90T OTA yesterday (wierd because the NRD90U is on the webpage) and later in the day I gave it a reboot just the set it straight again. I forget the actual wording but there is a secondary partition for updates so they do it in the background, and then revert back after a reboot.
After my rooting issues, (which I'm still having) I had missed the OTA update required for Naugat. I'm still on February, and, when I try to get the stock rom to unroot, the modem breaks and wifi doesn't work.
I got a c432B160 ss and I still only have a bad update and ive tried firmware finder, it does not work for me and neither does TWRP flashing how can Huawei screw up this bad with an update not not fix it when users simply cannot update without getting totally screwed by them.
I sent a message to me regarding with the update issues (about ,5-6 weeks ago).
They said that if you obtain the bootloader unlock code, your phone can be detected and no longer receive updates.
My friend who took his bootloader code is stuck on marshmallow since a year, even checking the updater app and nothing.
He has VNS-L21, just like mine. I guess i was lucky when my motherboard was changed twice and had a new IMEI.
So just try to sabotage your phone by installing a corrupted firmware and lock your bootloader. Then go to the warranty and tell them that you received an update and you left it overnight with the charger plugged in. Profit.
Why would they believe? Some huawei devices have a change (3.5%) to have their software corrupted when updating their firmware (from MM to N)