Update LMY48T really messed up my phone so I reverted back to LMY48M via a TWRP backup. There is a new security update being released soon, and I would like to give it another try. Do the factory image security updates include all previous updates as well, or does each one need to be installed in sucession and therfore would not work?
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.
There have been 4 OTA updates, not including the Nougat update, since I last received one. The last update I received was in July (baseband version G930AUCU2APG1.) It isn't rooted but it's encrypted. It says everything is up to date when I check for updates on the phone. AT&T tried to push an update last night and they told me they were unable to contact my phone. I tried wiping it and checking for updates but that didn't work either. Is there a way to manually install these updates?
RustyWedges said:
There have been 4 OTA updates, not including the Nougat update, since I last received one. The last update I received was in July (baseband version G930AUCU2APG1.) It isn't rooted but it's encrypted. It says everything is up to date when I check for updates on the phone. AT&T tried to push an update last night and they told me they were unable to contact my phone. I tried wiping it and checking for updates but that didn't work either. Is there a way to manually install these updates?
Click to expand...
Click to collapse
Download the Odin pk1 files and flash with odin. After that you should be able to take the nougat update. I'm not sure if you have to decrypt your phone though or not to Odin
Hello all,
My phone downloaded but did not install the 4BQG1 security update via OTA. Since my phone was already rooted, I thought it would be best to revert back to stock firmware with Odin, which I did. I reverted back to firmware build QE1 without incident. Did not have any problems. However, when I tried to manually update the phone to latest security update, G930AUCU4BQG1, it says I have current software, which I obviously don't.
What should I do? Thanks in advance for your help.
- Josh
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