Last ota update is from Nov. 2017 Update keeps saying phone is up to date. Google is no help. They have told me that they don't know why my phone won't update. I am on Google fi. Been told by others that I just need to sideload the latest update and it might kickstart the phone into accepting ota updates. Never done this so am concerned about mucking up my stock phone.
Anyone have any suggestions?
Was the phone in the Beta program? If so, that ended for the 6P as it isn't part of Android P beta and you won't get any further updates, even by coming out of the beta program.
Sideloading the OTA should fix it and you can do it without losing any app and personal data.
Link with OTA's and instructions from Google is at https://developers.google.com/android/ota
Nope, no beta program.
Still trying to decide if it is worth the risk for me to try the sideload......
Related
I notice on my phone that there is a software update coming thru. Wanted to know if this update will effect my chances of rooting in the future? Is this a good update? Should I update?
There is root now for PE1
The new update is PF2.
deleted
The PF2 update shows security patch level is July 1 on my phone.
yes, you are correct. I thought I took the update but the update failed. Don't know why.
Same thing happened to me this morning. Been trying to install it, but all I get is a 402 error message.
If anyone can let us know if root is still available after the update, that would be awesome!
Was able to root SGS7 on PF2 using guide on XDA Vz S7 Forum...
"Same thing happened to me this morning. Been trying to install it, but all I get is a 402 error message."
Try to install Smart Switch and update using it. I updated successfully by doing that.
Root works fine on PF2, I took the update and then rooted with no issues. Just use the general debloat script not the VZW specific one. However I had to use the samsung/verizon software to install the update, the OTA kept failing at 32%
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.
I want to ask a few things, I'm trying to get this phone all working on the latest things and I can't seem to find concrete answers for why its not working when searching around.
So the first issue is that I'm stuck on 7.0. I enrolled in the beta program and all, but it starts to try to download the update and then suddenly kicks off and goes 'you are up to date' even though I've still only got 7.0. What does that mean? I'm not sure what I'm doing wrong.
Second, I really, really want to use the google assistant. If I do this OTA update will I be unable to root the phone. If I root the phone, can I update to the final release of 7.1 when it comes out in december? And, as I am unfamiliar with this sort of thing, if I change the build.prop to be of a Pixel so I can use google assistant, will that adversely affect anything else on the phone?
Do I even use the OTA update method when I root the phone with TWRP or do I now have to flash things manually?
Hi I have an unrooted 6p I have never messed with the software but I am on the dp program I usually get the updates within hours of it being announced. But for some reason I have not gotten the 7.1.1 stable with December security patch which is odd but anyway I tried side loading the OTA and it gets to 40% and then says installation aborted. I have the and setup right and all that I can reboot into bootloader does anyone know why it would be doing this? When I was at work today I thought maybe if I disable the allow seamless update option in developer options maybe that will allow it. Any thoughts?
Ok I feel like an idiot. I tried again when I got home from work and it seems that the file I am trying to flash is from November 1 which I already have installed. It is the last one one the Google OTA page. So is it not out yet for the 6p? I'm confused can anyone help me out please
I believe you'll need to unenroll from the beta program first before attempting to sideload the OTA image. The latest OTA image is NMF26F, which includes the December security patch. And make sure you boot into recovery, and not the bootloader to install the update using adb.
redduc900 said:
I believe you'll need to unenroll from the beta program first before attempting to sideload the OTA image. The latest OTA image is NMF26F, which includes the December security patch. And make sure you boot into recovery, and not the bootloader to install the update using adb.
Click to expand...
Click to collapse
Ok if I unenrolled from the dp program I should just get the OTA then I won't have to side load is what I'm guessing. It seems that Google had the stable build done before they released the last dp because the file says November 1 build and I got mine on November 5 that is why it won't allow it.
My pixel4 is bootloader unlocked (safetynet cts profile is false), can I receive google play system update?
I haven't received it since May 1.
Security updates are fine as they use factory images.
Latest play update is may 2020.
So there is nothing available yet.
Thanks for telling me the latest version.
Looks like they distributed the July update but I haven't received it yet.
Is it randomly distributed to users?
You can manually update if it doesn't do it automatically
I kept deleting and rebooting the data and before I knew it, it was installed.