Related
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.
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.
December images for Android 8.1 Oreo
Official factory images
Official full OTA images
Build OPM1.171019.011 - non-operator-specific
i am currently running stock recovery + unlocked bootloader + snoke kernel. Can I flash OTA without losing any data? I have not applied magisk or TWRP recovery yet.
just tried it anyway and it worked. but does not pass safetynet anymore due to unlocked bootloader.
Any idea what Pixel 2 build OPD1.170816.025 is specific to? It's not one of the factory images or OTA zips provided by Google. I'm on AT&T, not in the beta program, and received it OTA via settings -> system -> update around 5:30pm EST today.
vivamahalo said:
Any idea what Pixel 2 build OPD1.170816.025 is specific to? It's not one of the factory images or OTA zips provided by Google. I'm on AT&T, not in the beta program, and received it OTA via settings -> system -> update around 5:30pm EST today.
Click to expand...
Click to collapse
Probably specific to AT&T network and radio settings. It's a non-operator specific build, so I'd guess they just tacked on their radio, modem and whatever else is proprietary for them.
---------- Post added at 10:18 PM ---------- Previous post was at 10:10 PM ----------
023 for November on Verizon. Updated by using system update in settings.
vivamahalo said:
Any idea what Pixel 2 build OPD1.170816.025 is specific to? It's not one of the factory images or OTA zips provided by Google. I'm on AT&T, not in the beta program, and received it OTA via settings -> system -> update around 5:30pm EST today.
Click to expand...
Click to collapse
Looks like .025 is rolling out for unlocked models. It brings the saturated option in display -> colors. Which is a bit more poppy and marginally better at crushed blacks.
It has the nov. 5th security patch though, not the nov. 6th.
To get .025 you need to get the ota from the phone - system updates, as it's not on Google's OTA site.
petrus764 said:
Looks like .025 is rolling out for unlocked models. It brings the saturated option in display -> colors. Which is a bit more poppy and marginally better at crushed blacks.
It has the nov. 5th security patch though, not the nov. 6th.
To get .025 you need to get the ota from the phone - system updates, as it's not on Google's OTA site.
Click to expand...
Click to collapse
Also brings a navy bar which fades to grey after a few seconds in most apps (but not on the homescreen, at least not with Nova - not tested with Pixel Launcher).
Tried the saturated colours and it made my photos look completely unlike the real colours. Should keep Samsung fans happy then.
petrus764 said:
Looks like .025 is rolling out for unlocked models. It brings the saturated option in display -> colors. Which is a bit more poppy and marginally better at crushed blacks.
It has the nov. 5th security patch though, not the nov. 6th.
To get .025 you need to get the ota from the phone - system updates, as it's not on Google's OTA site.
Click to expand...
Click to collapse
I don't see anything when I run the check for updates in the system settings.
cb474 said:
I don't see anything when I run the check for updates in the system settings.
Click to expand...
Click to collapse
Weird, you are on the september build, right? Not running the 8.1 beta?
I sideloaded the OTA update and it seems to have gone fine, phone boots. But at the end of the process I got this message from adb:
Code:
* failed to read command: Success
Is that normal? Seems like a weird message, "failed" and "success."
*
Also, weirdly, the first couple times I restarted the phone after updating I got notifications for a bazillion old text messages, all in a row.
---------- Post added at 01:37 AM ---------- Previous post was at 01:35 AM ----------
petrus764 said:
Weird, you are on the september build, right? Not running the 8.1 beta?
Click to expand...
Click to collapse
Yes, just on the build that came with the phone. I was reading elsewhere that it can take a few days to a week or more, before people get the OTA pushed to their phone, after it goes up on the developer website. You can see I went ahead and sideloaded .018. I wonder if I'll still eventually see a update for .025 on my phone. I don't see the saturated option you mention. Also, I'm one of the people with the clicking noise and .018 did not fix that. But I see some people on the Google product forums saying they got an update and it did fix it. I wonder if they got .025.
cb474 said:
I sideloaded the OTA update and it seems to have gone fine, phone boots. But at the end of the process I got this message from adb:
Code:
* failed to read command: Success
Is that normal? Seems like a weird message, "failed" and "success."
*
Also, weirdly, the first couple times I restarted the phone after updating I got notifications for a bazillion old text messages, all in a row.
---------- Post added at 01:37 AM ---------- Previous post was at 01:35 AM ----------
Yes, just on the build that came with the phone. I was reading elsewhere that it can take a few days to a week or more, before people get the OTA pushed to their phone, after it goes up on the developer website. You can see I went ahead and sideloaded .018. I wonder if I'll still eventually see a update for .025 on my phone. I don't see the saturated option you mention. Also, I'm one of the people with the clicking noise and .018 did not fix that. But I see some people on the Google product forums saying they got an update and it did fix it. I wonder if they got .025.
Click to expand...
Click to collapse
If you sideloaded .018 you'll probably not get .025. I'm guessing you'll have to downgrade first if you want it. Make sure to update your ADB and Fastboot versions to the newest, as you'll end up with a bad flash with older versions, resulting in having to flash each file inside the image file manually.
petrus764 said:
If you sideloaded .018 you'll probably not get .025. I'm guessing you'll have to downgrade first if you want it. Make sure to update your ADB and Fastboot versions to the newest, as you'll end up with a bad flash with older versions, resulting in having to flash each file inside the image file manually.
Click to expand...
Click to collapse
I wondered about that. Apparently .018 does not have the November 6 security patch, which seems to include the patches for the Krack vulnerability. It's weird that Google is pushing .025 to some devices, but posted .018 on the website at the same time. And I read the 2 XL is getting updates pushed to it, even though there are no November OTA images on the developer website.
So it's okay to flash an older OTA image over a newer one?
cb474 said:
I wondered about that. Apparently .018 does not have the November 6 security patch, which seems to include the patches for the Krack vulnerability. It's weird that Google is pushing .025 to some devices, but posted .018 on the website at the same time. And I read the 2 XL is getting updates pushed to it, even though there are no November OTA images on the developer website.
So it's okay to flash an older OTA image over a newer one?
Click to expand...
Click to collapse
In theory it should since Googles OTAs are full system images in fact. But as I said, you need the latest fastboot/adb, and it's on your own risk. I haven't tried it.
You could also see if you find the .025 OTA URL from google, but I have no idea if that can be flashed over the .018 build without issues.
Fyi the .025 build is also on nov 5, not nov 6 security patch and the saturated mode sucks. So I wouldn't bother if I were you.
petrus764 said:
In theory it should since Googles OTAs are full system images in fact. But as I said, you need the latest fastboot/adb, and it's on your own risk. I haven't tried it.
You could also see if you find the .025 OTA URL from google, but I have no idea if that can be flashed over the .018 build without issues.
Fyi the .025 build is also on nov 5, not nov 6 security patch and the saturated mode sucks. So I wouldn't bother if I were you.
Click to expand...
Click to collapse
Yes, I saw what you said about adb/fastboot. Thanks. I'm up to date on that.
I thought I read somehwere that .025 is Nov 6. Hmm, oh well. This article says it's the Nov 6 security patch that fixes Krack: https://9to5google.com/2017/11/06/android-november-17-security-patch-nexus-pixel/ Hard to believe Google still hasn't patched Krack in .018 or .025.
My main reason for wanting .025 is that it sounds like it might fix the clicking issue that some people have. On the Google product forms some people are reporting the update fixes the issue, others are saying it does not. I'm wondering if the difference is that some people sideloaded .018 and other got the .025 update pushed to them.
---------- Post added at 03:07 AM ---------- Previous post was at 02:44 AM ----------
Well, I tried to downgrade, by sideloading the older OTA image and I got this message:
Code:
E: Update Package is older than the current build, expected build newer than timestamp 1508187794 but package has time tamp 1504244601 and downgrade not allowed.
Installation aborted.
I wonder if I can flash the factory image? But then will that disable future OTA updates on my phone?
cb474 said:
Yes, I saw what you said about adb/fastboot. Thanks. I'm up to date on that.
I thought I read somehwere that .025 is Nov 6. Hmm, oh well. This article says it's the Nov 6 security patch that fixes Krack: https://9to5google.com/2017/11/06/android-november-17-security-patch-nexus-pixel/ Hard to believe Google still hasn't patched Krack in .018 or .025.
My main reason for wanting .025 is that it sounds like it might fix the clicking issue that some people have. On the Google product forms some people are reporting the update fixes the issue, others are saying it does not. I'm wondering if the difference is that some people sideloaded .018 and other got the .025 update pushed to them.
---------- Post added at 03:07 AM ---------- Previous post was at 02:44 AM ----------
Well, I tried to downgrade, by sideloading the older OTA image and I got this message:
Code:
E: Update Package is older than the current build, expected build newer than timestamp 1508187794 but package has time tamp 1504244601 and downgrade not allowed.
Installation aborted.
I wonder if I can flash the factory image? But then will that disable future OTA updates on my phone?
Click to expand...
Click to collapse
You can flash the factory image and it won't disable future OTA's but for factory images you need to have your bootloader unlocked. If it's locked now unlocking it will wipe your device.
Mine just recieved the .025 patch and i can comfirm its November 5th.
petrus764 said:
You can flash the factory image and it won't disable future OTA's but for factory images you need to have your bootloader unlocked. If it's locked now unlocking it will wipe your device.
Click to expand...
Click to collapse
Thanks. Yeah, I unlocked a while ago, so I would be able to root when that became available, without having to wipe my device. And I'm hoping there will be a version of Lineage OS for this device, so I can get away from the nightmare that is Google's update process and other ridiculousness.
Anyway, I'm downloading the factory image now, but I guess I might wait a couple days first to see if .025 does get pushed to my phone. All I can say is, WTF Google? Also, did you notice that there was a spelling mistake in that error code the OTA sideload output, "time tamp"? Brilliant.
cb474 said:
Thanks. Yeah, I unlocked a while ago, so I would be able to root when that became available, without having to wipe my device. And I'm hoping there will be a version of Lineage OS for this device, so I can get away from the nightmare that is Google's update process and other ridiculousness.
Anyway, I'm downloading the factory image now, but I guess I might wait a couple days first to see if .025 does get pushed to my phone. All I can say is, WTF Google? Also, did you notice that there was a spelling mistake in that error code the OTA sideload output, "time tamp"? Brilliant.
Click to expand...
Click to collapse
Remember to remove -W from the flash-all.bat script or else it will wipe your device.
I doubt google will push .025 as it's not the first time they've done something like this.
petrus764 said:
Looks like .025 is rolling out for unlocked models. It brings the saturated option in display -> colors. Which is a bit more poppy and marginally better at crushed blacks.
It has the nov. 5th security patch though, not the nov. 6th.
To get .025 you need to get the ota from the phone - system updates, as it's not on Google's OTA site.
Click to expand...
Click to collapse
Large Hadron said:
Also brings a navy bar which fades to grey after a few seconds in most apps (but not on the homescreen, at least not with Nova - not tested with Pixel Launcher).
Tried the saturated colours and it made my photos look completely unlike the real colours. Should keep Samsung fans happy then.
Click to expand...
Click to collapse
The .025 build also cleared up my pesky clicking noise issue, in addition to the new color settings (Boosted, Natural, and Saturated) and fading grey nav buttons.
petrus764 said:
Remember to remove -W from the flash-all.bat script or else it will wipe your device.
I doubt google will push .025 as it's not the first time they've done something like this.
Click to expand...
Click to collapse
Well, I became impatient/stupid and decided to try to downgrade to .010 by flashing the factory image (since the adb sideload of the OTA image did not work). Wow, that was an extreme mistake.
First, it turned out I did not have the newest version of fastboot, even though I was sure that I did (so much for Arch Linux being "bleeding edge"). After I flashed .010 all my phone would do was boot the the bootloader (it wouldn't even from there go to the recovery or power off). I thought the problem was .010, so I decided to try to reflash .018 with the factory image of that. That's when I discovered my fastboot problem, because with .018 it actually quits and warns you that you don't have the right version. Once I got the right fastboot, I flashed .018 and it booted up fine. Having not learned my lesson, I tried .010 again, with my updated fastboot. This time it booted to the "G" screen and then just got stuck with the progress bar endlessly looping. It was hard to get it to boot back to the bootloader, using the key combination, but finally I got it. Then I flashed .018 again and everything seems fine (fingers crossed).
So downgrading seems to not be an option by any avenue.
Weirdly both with the older fastboot and the newer one, even when flashing .018 that worked, I got an error message everytime:
Code:
sending 'bootloader_a' (38728 KB)...
OKAY [ 2.095s]
writing 'bootloader_a'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 2.099s
Don't know what that "command flash error" is. Not very reasurring. But doesn't seem to be a problem at least with .018 factory image. I don't know if the bootloader really failed to be flashed, since .010 and .018 come with the same bootloader version. Or it's just something else that failed with "updating: partition:0."
So a lot of trouble to end up back where I started. I'm super annoyed if I won't get .025, since it seems to fix the clicking issue. I can't believe Google posts one OTA update online and pushes a different one. That is just so stupid.
How do you force the OTA or use the image on a stock Pixel 2 unlocked from Google
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!
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