Database Users

My 6P WILL NOT update to 7.0

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.

Stuck on Dec 2016 Update

I bought my 6p directly from Google, and it isn't unlocked or rooted. It seems to be stuck on the Dec 2016 (NMF26F) update. Forcing it to check for updates says it is up to date even today, Feb 13 2017. Any ideas?

ericstephani said:
I bought my 6p directly from Google, and it isn't unlocked or rooted. It seems to be stuck on the Dec 2016 (NMF26F) update. Forcing it to check for updates says it is up to date even today, Feb 13 2017. Any ideas?
Click to expand...
Click to collapse
Enable "Android (or USB) Debugging" in Developer Options then follow the instructions to adb sideload a full OTA image:
https://developers.google.com/android/ota
This OTA image does not require an unlocked bootloader.
Sent from my Nexus 5X using Tapatalk

Yeah I would side load like it says above.
For some reason my phone doesn't receive OTA updates either. Idk what happened but ever since the stable 7.0 I wasn't able to receive. So decided to side load which is super easy to do.

Thanks for the suggestions. I was considering manually loading the update while I wrote the post. I'll try it tonight.

Mi A1 Oreo 170623.026.7.12.29 Encountered Bugs

Hi Guys,
I did not receive OTA for Oreo on my Android One and had to reset my phone to get the OTA update. After that once I installed Nougat Fastboot Rom and it was on August 2017 patch and wasnt receiving OTA again so I flashed Oreo Fastboot Current Rom and later locked the bootloader through fastboot oem lock command. I thought it was only me who is not getting the latest January Patch. Following are my questions:
1. Are we going to get Oreo 8.1 or any patch for january? I am not a beta tester.
2. How do I know if my phone is still receiving OTA?
Bugs encountered, please let me know if any one has the similar bugs.
1. Sudden crash of google chrome, android web view or some other apps like ventura wealth etc.
2. Camera doesnt start sometimes.
3. Battery Drain.
4. Phone rings but there is no caller id when phone is locked.
5. Multiple Contacts for various apps can be seen in native contact apps which makes it difficult to select the required contact.
6. No Fingerprint Gesture control.
7. Mi Remote not able to put shortcuts on desktop and no option to grant permission too.
8. No Flash Notification.
Please let me know something useful.
I have got Nougat Rom of December patch. Is it wise to use that?

So I just flashed Nougat December patch official fast boot rom.
I am not being shown any ota for oreo or for any thing.
Is this normal.

rajputz said:
So I just flashed Nougat December patch official fast boot rom.
I am not being shown any ota for oreo or for any thing.
Is this normal.
Click to expand...
Click to collapse
Yeah, I did a fastboot flash last night. Just got the update. Just wait.
The update rolls out in batches so you just have to wait your turn

KalolParty said:
Yeah, I did a fastboot flash last night. Just got the update. Just wait.
The update rolls out in batches so you just have to wait your turn
Click to expand...
Click to collapse
What you mean is that as soon as I put official fastboot rom, I wont immediately get the OTA. I will have to wait. For eg. I am trying with August Patched Official Tissot rom now.

rajputz said:
What you mean is that as soon as I put official fastboot rom, I wont immediately get the OTA. I will have to wait. For eg. I am trying with August Patched Official Tissot rom now.
Click to expand...
Click to collapse
Stay with the December update since you'll only get OTA if you're on December update.
Just be patient. It may take a day or two or even a week but you'll get it.
Installing a fastboot ROM helps improve your chances but doesn't guarantee anything

Best path to Pie upgrade?

Picked up a Moto 6 Plus (XT1926-7, retla) last month and have been running the latest 8.0 (8.0.0_OPWS27.113-89-5) with unlocked bootloader and Magisk. Working flawless. :good:
Decided to take the plunge to Pie last night, which ended up with me have to do a full restore of a 8.0.0_OPWS27.113-89-5, then taking the OTA to 9.0
Upon successful OTA to 9.0, I then rebooted and used fastboot TWRP to try to take a clean nandroid backup. I could backup all partitions except Data (fork failure to make the rar).
I then rebooted again (still stock, no Magisk install yet), and noticed that I was getting a "dm-verity disabled" warning on my bootup screen and then a warning under System Update check that says "Updates are disable for this device due to compromised system integrity".
Have others tried the same yet? Is this "compromise" due to the unlocked bootloader, or did TWRP trip something? Is it possible to run Pie with Magisk and still be a google certified device?

Just tried again:
* Clean wipe and install to 8.0 (89-5)
* Bare bones phone config.
* enable USB Debug
* Accepted OTA Update and reboot
* Successful update to 9.0 (PPW29.116-11, patch level Dec 1, 2018)
* Play Store version 13.0.23-all [0] [PR] 227930514
* enable USB Debug
* reboot
* following warning on the blue/yellow bootup screen: "Verity mode is set to disabled"
* System Update page: "System Integrity is Compromised", "As your device system integrity is compromised, it is no longer eligible for software updates. Please contact customer service to re-program the device with official software."
EDIT:
* Magisk rooting still works: https://forum.xda-developers.com/g6-plus/how-to/3-how-to-install-root-aka-magisk-t3854244
* TWRP installer works: https://forum.xda-developers.com/g6-plus/how-to/twrp-installer-zip-evert-t3875657

Can you share wich files do you use to upgrade? (Screenshot)
Sent from my Motorola moto g(6) plus using XDA Labs

RokCruz said:
Can you share wich files do you use to upgrade? (Screenshot)
Sent from my Motorola moto g(6) plus using XDA Labs
Click to expand...
Click to collapse
I used the files below to return to stock 8.0 prior to upgrade. I did not use files to upgrade to 9.0, I used the OTA system updater.
https://mirrors.lolinet.com/firmware/moto/evert/official/RETLA/

thump said:
* TWRP installer works: https://forum.xda-developers.com/g6-plus/how-to/twrp-installer-zip-evert-t3875657
Click to expand...
Click to collapse
Hmm. I would not use the twrp installer, since I haven't heard anywhere that it would work flawless with evert. Skip that and use fastboot boot twrp.img to access recovery. Do not flash. Boot.

May i ask you a question kind sir. I have the same model (G6 plus) de same oppw thingy (8.0.0_OPWS27.113-89-5) and when i hit the update button did not get any OTA. It says i have the latest version and still in november security patch. How did you trigger the OTA? Or you sideload it? Thanks kind sir

Nice to see that you had an OTA to Pie. I was about to ask where you live, because I don't have the OTA here in Belgium yet. But then I saw you have a RETLA device, so I guess I will have to wait some more!
Is the phone working well on Pie?

weazie said:
Hmm. I would not use the twrp installer, since I haven't heard anywhere that it would work flawless with evert. Skip that and use fastboot boot twrp.img to access recovery. Do not flash. Boot.
Click to expand...
Click to collapse
I've used both, but the installed one worked identically so far for backing up and installing Magisk.
The_Pacifier said:
May i ask you a question kind sir. I have the same model (G6 plus) de same oppw thingy (8.0.0_OPWS27.113-89-5) and when i hit the update button did not get any OTA. It says i have the latest version and still in november security patch. How did you trigger the OTA? Or you sideload it? Thanks kind sir
Click to expand...
Click to collapse
I'm on the retla software channel, which I believe is the first to get the Pie OTAs.
knevelsg-j said:
Nice to see that you had an OTA to Pie. I was about to ask where you live, because I don't have the OTA here in Belgium yet. But then I saw you have a RETLA device, so I guess I will have to wait some more!
Is the phone working well on Pie?
Click to expand...
Click to collapse
Yep.. purchased on Amazon in the US (I don't think they ever officially released G6+ model direct to US). So far, working smooth. Haven't found any bugs.
Should also note that even with the Verity and "not update eligible" issues, and now rooted with Magisk, it does still show as Play Store Certified.

@thump i am in the retla too. I did not get the pop up update neither via security o update section. I have the same OPWS as yours too ??

The_Pacifier said:
@thump i am in the retla too. I did not get the pop up update neither via security o update section. I have the same OPWS as yours too
Click to expand...
Click to collapse
Weird. Mine badgered me every hour with a "Software Update is Available" notification for the past week. Even when I did the clean stock reflash to 89-5, it notified me a few minutes after clean reboot, before I even got around to checking System Updates. Maybe rolling it out in staggered waves of some type?

thump said:
Weird. Mine badgered me every hour with a "Software Update is Available" notification for the past week. Even when I did the clean stock reflash to 89-5, it notified me a few minutes after clean reboot, before I even got around to checking System Updates. Maybe rolling it out in staggered waves of some type?
Click to expand...
Click to collapse
Yes maybe... latin america is pretty wide...going to keep pressing the update button or in the case a factory reset may help or not?

thump said:
Weird. Mine badgered me every hour with a "Software Update is Available" notification for the past week. Even when I did the clean stock reflash to 89-5, it notified me a few minutes after clean reboot, before I even got around to checking System Updates. Maybe rolling it out in staggered waves of some type?
Click to expand...
Click to collapse
@thump Hello kind sir!! Remember me? Yes the updates are released in staggered waves, just got prompted the Android Pie update!! ?? Appreciate your help.

The_Pacifier said:
@thump Hello kind sir!! Remember me? Yes the updates are released in staggered waves, just got prompted the Android Pie update!! ?? Appreciate your help.
Click to expand...
Click to collapse
Excellent. Good luck!

December 2020 Security Update now available

Hy,
December Update out now.
Greets

got it too, can't see any fixes though. on the plus side they dont seem to have broken anything either. can call this a "win" i guess

Wondering if people stuck on September version can finally update without resetting data.
Please let us know if you're in this group.

laviniu_c said:
got it too, can't see any fixes though. on the plus side they dont seem to have broken anything either. can call this a "win" i guess
Click to expand...
Click to collapse
I would say the same. Can't expect anything better than this from these system updates.

until when mi a2 will receive updates? will this be the last?

Mi A1 was released with August 2017 security patch and received its last update on August 2020, something similar should happen for Mi A2 too.

birdflesh said:
Mi A1 was released with August 2017 security patch and received its last update on August 2020, something similar should happen for Mi A2 too.
Click to expand...
Click to collapse
thanks for the info! Mi A2 security patches until Aug 2021 (Mi A2 release August 2018)

Since that update my battery drains way faster.

Since that update my battery drains way faster.
+1

I'm still in the September update.
Has anyone with the bootloader unlocked updated their phone? If yes, what were your steps to update it?

ota should work with an unlocked bl, IF you have not changed the system. unlocking means you could change it, it doesnt in itself deny ota updates

salmonthefish said:
I'm still in the September update.
Has anyone with the bootloader unlocked updated their phone? If yes, what were your steps to update it?
Click to expand...
Click to collapse
I´m also waiting for anyone that reported that made the update. I have Setember Update with bootloader unlocked because of camera2api, i don´t made any system changes, and i get all the updates until september without problemes. After that i get Bootloop on October and don´t update anymore. If anyone upgrade from setember with sucess please report.

ki69 said:
because of camera2api
Click to expand...
Click to collapse
you answered your own question. if you've unlocked AND made ANY changes to the system ota can bootloop ofcourse.

With unlocked bootloader factory reset is needed once and only once when updating from any version < 11.0.15.0 (October patch) to any version >=11.0.15.0 regardless of update method (OTA or fastboot reflashing). I suspect that Xiaomy made breaking changes to /vendor and/or other system partitions in 11.0.15.0.
So if you want to fastboot flash 11.0.19.0 over 11.0.14.0 or 11.0.5.0 you will need to make factory reset or just flash with "flash_all.bat/sh".
I've seen reports here that factory reset was also required on fully stock phones when receiving 11.0.15.0 October OTA, and I am really sorry for those users, as they had no chance to update with full recovery of user data.
Those having unlocked bootloader can make full recovery of user data after reset using TWRP backup of /data partition, guide is here:
October 2020 Security Update now available
October Security Update just released today.
forum.xda-developers.com

Aerobatic said:
With unlocked bootloader factory reset is needed once and only once when updating from any version < 11.0.15.0 (October patch) to any version >=11.0.15.0 regardless of update method (OTA or fastboot reflashing). I suspect that Xiaomy made breaking changes to /vendor and/or other system partitions in 11.0.15.0.
So if you want to fastboot flash 11.0.19.0 over 11.0.14.0 or 11.0.5.0 you will need to make factory reset or just flash with "flash_all.bat/sh".
I've seen reports here that factory reset was also required on fully stock phones when receiving 11.0.15.0 October OTA, and I am really sorry for those users, as they had no chance to update with full recovery of user data.
Those having unlocked bootloader can make full recovery of user data after reset using TWRP backup of /data partition, guide is here:
October 2020 Security Update now available
October Security Update just released today.
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you.
A question, if i unlock the bootloader afterwards will the same issue pop up again?

salmonthefish said:
A question, if i unlock the bootloader afterwards will the same issue pop up again?
Click to expand...
Click to collapse
I believe neither Xiaomi nor Google can answer this question.
Anyway,
1) right now factory reset for unlocked MiA2 is needed only once when updating from any previous ROM version to any currently available ROM version >= 11.0.15.0;
2) having unlocked phone one is sure that his data can be restored in any future mishap;
3) unfortunately unlocked phone prevents usage of most of banking apps unless Magisk + Riru + edXposed installed with MagishHide On and GooglePlayServices in Blocked List (SafetyNet issue).
So everyone decides himself whether to
a) keep phone untampered (with risk of loosing data with next OTA bootloop),
b) or unblock phone and then stay with updating stock (spending some time to get root, make SafetyNet passable, remove annoying settings suggestions, customize UI, etc.) ,
c) or unblock phone and then revert to Android 9 10.0.17.0 (disabling updates),
d) or unblock phone and then escape to a Custom ROM.
I personally prefer option (b) since my first Android gadgets (never bought a phone/tablet which had problems with rooting).

19Gerhard85 said:
Since that update my battery drains way faster.
Click to expand...
Click to collapse
19Gerhard85
after updating "Google Find my Device" app battery holds like before all ok now but i never use that app not even logged in calendar app also updated at same time but i don't thin it was calendar