Google just released Factory Image 5.0.2 (LRX22G) for Nexus 10. (and 7 Wifi(2013))
https://developers.google.com/android/nexus/images
I noticed that as well. Any reason why it's not alerting me to update? I can always d/l the link, but that does a full wipe and don't really feel like setting things back up again.
Any reason why it's not doing the update on it's own?
tclarkey said:
Any reason why it's not doing the update on it's own?
Click to expand...
Click to collapse
Google does staged rollouts with OTA of new Android versions, so at first only 1% of devices receives the new update (source: Droid-Life).
As soon as someone gets the OTA url and publishes it, it will appear on this thread and you can sideload it without having to do a factory reset. Alternatively, you could apply the Factory Image without the "-w" flag, but that's a little more risky (although with the minor update from 5.0.1 to 5.0.2 it should be fine, I did it on my Nexus 5 from 5.0 to 5.0.1 and it runs fine).
BorgKing said:
Google does staged rollouts with OTA of new Android versions, so at first only 1% of devices receives the new update (source: Droid-Life).
As soon as someone gets the OTA url and publishes it, it will appear on this thread and you can sideload it without having to do a factory reset. Alternatively, you could apply the Factory Image without the "-w" flag, but that's a little more risky (although with the minor update from 5.0.1 to 5.0.2 it should be fine, I did it on my Nexus 5 from 5.0 to 5.0.1 and it runs fine).
Click to expand...
Click to collapse
Or alternatively unpack and flash only system.img, that will preserve your data.
is that fixed?
http://forum.xda-developers.com/nexus-10/help/android-5-0-sound-problem-charging-t2939672
perfect_ said:
is that fixed?
http://forum.xda-developers.com/nexus-10/help/android-5-0-sound-problem-charging-t2939672
Click to expand...
Click to collapse
No
Related
Now Available!! 5.0.1!!!
Go get your lollipop ON!!!
Hopefully this will result in some bugs squashed with CM12. I am hoping for a better modem and better Bluetooth.
Queuing up downloads now, I have two of them pending for my device
are you able to capture the updates
I was able to capture the first update because im rooted. But i dont want to lose it if i update it. I hope the developers can find a way to keep root for the first update. if they can. I will happily capture the second update to get lollipop.
http://forum.xda-developers.com/showpost.php?p=60435732&postcount=54
dgutierrez04 said:
I was able to capture the first update because im rooted. But i dont want to lose it if i update it. I hope the developers can find a way to keep root for the first update. if they can. I will happily capture the second update to get lollipop.
http://forum.xda-developers.com/showpost.php?p=60435732&postcount=54
Click to expand...
Click to collapse
you could try taking it, then flashing the nc5 kernel through odin, and then (if someone's able to do this) get the kernel from nk4 and flash that
dgutierrez04 said:
I was able to capture the first update because im rooted. But i dont want to lose it if i update it. I hope the developers can find a way to keep root for the first update. if they can. I will happily capture the second update to get lollipop.
http://forum.xda-developers.com/showpost.php?p=60435732&postcount=54
Click to expand...
Click to collapse
How many updates are there? What does it mean 1st update? are there more updates?
meazz1 said:
How many updates are there? What does it mean 1st update? are there more updates?
Click to expand...
Click to collapse
apparently this is a 2-part update
part 1 is a build where the last three characters are NK4. this is a kitkat ROM that was likely used to prepare for lollipop
part 2 is the actual lollipop build, OC1. i think it's 5.0.1 but i'm seeing conflicting things from the internet
for some reason verizon likes doing major updates this way (i dont think they did it for jelly bean to kitkat though). but i've had a few of their phones, they've been doing two-part updates since the original galaxy s in 2010 lol
Hey everyone! Has anyone solved the mystery of the lollipop update fail? Seems alot of us are getting the first update without any issues, but the lollipop update is failing. It gives error 402, which one person at Vz told me was an error thrown due to having root. ( I don't have root ) Any suggestions appreciated!
gsmitchell said:
Hey everyone! Has anyone solved the mystery of the lollipop update fail? Seems alot of us are getting the first update without any issues, but the lollipop update is failing. It gives error 402, which one person at Vz told me was an error thrown due to having root. ( I don't have root ) Any suggestions appreciated!
Click to expand...
Click to collapse
My update is failing as well.
I've wiped cache in recovery, wiped data and cache in download manager...
Still fails.
I was rooted at one time - not rooted anymore.
I do still get the "custom" boot screen with the padlock though...
Can someone that has taken the OC1 ota update test to see if the 4.4.2 kernel has been blacklisted by:
1. Flash the I545_NK4_Stock_Kernel.tar.md5 using Odin. The device will not boot after flashing but we are just interested to see if the kernel will successfully flash.
2. To go back to normal flash the I545_OC1_Stock_Kernel.tar.md5 also in Odin.
This is the first test to determine if a downgrade workaround will be available for those that took the OC1 ota update.
muniz_ri said:
Can someone that has taken the OC1 ota update test to see if the 4.4.2 kernel has been blacklisted by:
1. Flash the I545_NK4_Stock_Kernel.tar.md5 using Odin. The device will not boot after flashing but we are just interested to see if the kernel will successfully flash.
2. To go back to normal flash the I545_OC1_Stock_Kernel.tar.md5 also in Odin.
This is the first test to determine if a downgrade workaround will be available for those that took the OC1 ota update.
Click to expand...
Click to collapse
Nope, it fails to flash
Here is the short log from the screen:
Code:
START [224, 1440]
SYS REV CHECK FAIL[K] : Refer 1 > Binary 0
SECURE MAGICCODE CHECK FAIL : boot
Is there a stock Odin TAR for this yet?
xdabens said:
Nope, it fails to flash
Here is the short log from the screen:
Code:
START [224, 1440]
SYS REV CHECK FAIL[K] : Refer 1 > Binary 0
SECURE MAGICCODE CHECK FAIL : boot
Click to expand...
Click to collapse
Not good. The 4.4.2 kernel has been blacklisted. Thx for testing.
Successful update (in two part harmony) yesterday. Stock system. Fox-Fi still works over Wi-Fi so I'm happy. No issues except 2nd update took a loooonngg time on the red Verizon screen. Make sure your battery is full or you are plugged in. No comments on battery life as I've been able to stay charged today. Getting used to it.
Hey everyone! If you getting the 402 Error, there is a thread that might have the fix. Go to the Error 402 when updating to Lolipop? thread. I am going to try it when I get home tonight.
dgutierrez04 said:
I was able to capture the first update because im rooted. But i dont want to lose it if i update it. I hope the developers can find a way to keep root for the first update. if they can. I will happily capture the second update to get lollipop.
http://forum.xda-developers.com/showpost.php?p=60435732&postcount=54
Click to expand...
Click to collapse
Thanks! Muniz_ri mentioned that you also captured the OC1 OTA package. I searched a lot but did not find it. Could you provide the link? Thanks again!
danielzink said:
My update is failing as well.
I've wiped cache in recovery, wiped data and cache in download manager...
Still fails.
I was rooted at one time - not rooted anymore.
I do still get the "custom" boot screen with the padlock though...
Click to expand...
Click to collapse
I had the same custom boot screen--even after unrooting. Tried using Triangle Away to reset the binary count, but the count was already at 0. So ultimately I had to re-flash the NC5 kernel via Odin to get things truly back to being recognized as stock.
Then updates started rolling in for NG6, then NK1. Finally the two-part update for Lollipop.
Sent from my SCH-I545 using XDA Free mobile app
People getting tthe 40 error did you at one time have safestrap installed? ??
---------- Post added at 09:42 AM ---------- Previous post was at 09:40 AM ----------
I've always found taking out sd card then a fresh Odin back to stock then doing my updates lead me to a flawless update process every time
Guys I'm on NC5 only rooted by towelroot what do I do please?!
Has anyone received thus OTA yet? Google posted the images for 5.1.1 online 29 days ago, but I haven't received it yet.
Germany lte version using 5.1.1 since ca. 2 weeks or so
Translated with my own brain to English
I still have not received the Android 5.0.2 update to upgrade
I still have not received the Android 5.0.2 update to upgrade to Android 5.1.1
I have a Nexus 9 LTE that I purchased from Google. I have emailed many times. Disappointing.
stock not rooted lte nex 9 -- received the ota to 5.1.1 over two weeks ago i think - los angeles
swcampbell said:
I still have not received the Android 5.0.2 update to upgrade to Android 5.1.1
I have a Nexus 9 LTE that I purchased from Google. I have emailed many times. Disappointing.
Click to expand...
Click to collapse
Where did you email? I called them and got double-talk. So, I'll email them. It probably takes X number of calls/emails from disappointed customers before they bother to look into it.
I never got 5.02. When I initially booted the device last December, it automatically OTA'd 5.01. I was hoping I'd get an OTA that would take from to 5.1.1 from 5.01.
DonDerham said:
Where did you email? I called them and got double-talk. So, I'll email them. It probably takes X number of calls/emails from disappointed customers before they bother to look into it.
I never got 5.02. When I initially booted the device last December, it automatically OTA'd 5.01. I was hoping I'd get an OTA that would take from to 5.1.1 from 5.01.
Click to expand...
Click to collapse
Guys, this is XDA. It's pretty easy to update yourself with the factory image. No need for the ota. Just flash the bootloader, system and boot images. No lose of data either.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Guys, this is XDA. It's pretty easy to update yourself with the factory image. No need for the ota. Just flash the bootloader, system and boot images. No lose of data either.
Click to expand...
Click to collapse
No loss of data assume the bootloader is already unlocked. In my case, it's still locked. Obviously, I can back up everything and flash, but part of the reason for buying a Nexus device includes prompt OTAs.
The device downloaded and installed 5.0.2 without a hitch. On reboot, it downloaded the 5.1.1 OTA, but errored on installation. I cleared the cache, rebooted and it repeated the process with the same error result. Nexus tech support, when they hear OTA, pretty much say "we know nothing."
So, I'll backup the device as best I can, do a factory reset and try the OTA again.
Now, I can unlock the device and ADB the images manually. Why not do so? You'd have to be married to understand. This is my wife's tablet. If I unlock the bootloader or root it or do anything other than "normal" Google stuff and anything ever goes amiss, my lovely wife will complain that my tinkering has caused her Candy Crush and Facebook to malfunction.
I flashed 4.5.2 Apollo on my 8.9 HDX from CM11 now Im stuck it doesnt update just says update failed I removed the recovery didnt fix the problem either. Is there a flashable 4.5.5.1 apollo zip? I tried changing the bin to a zip and flashing didnt work said apollo_full instead of apollo as error. Anyone know how to fix it just downloads the update fully then says update failed...
DroidDogg said:
I flashed 4.5.2 Apollo on my 8.9 HDX from CM11 now Im stuck it doesnt update just says update failed I removed the recovery didnt fix the problem either. Is there a flashable 4.5.5.1 apollo zip? I tried changing the bin to a zip and flashing didnt work said apollo_full instead of apollo as error. Anyone know how to fix it just downloads the update fully then says update failed...
Click to expand...
Click to collapse
Be happy 4.5.5.1 didn't take when SafeStrap recovery was installed; device would have bricked. Assume you used the Safestrap compatible variant of 4.5.2 (here). After flashing that (stock slot only; never use secondary slots in SS v4) reboot device and remove Safestrap recovery via SS app. Power down and boot into stock recovery via <power>+<vol-up> and perform a factory reset (you'll loose all apps/data). Reboot again and initialize FireOS. It should then accept OTA updates.
Be 100% sure Safestrap recovery is uninstalled prior to doing a factory reset.
Curious - why to you want 4.5.5.1? Offers no advantage over 4.5.2 if running custom ROMs. Nor will it automatically update to FireOS v5 as Amazon has no plans to release a v5 update for 3rd gen devices.
Ok I went back to 4.5.2 > installed kingroot > went to safestrap > uninstalled recovery > rebooted to stock recovery and factory reset . Its still doing the same thing it downloads to 100 and doesnt do anything...
I might be selling the device and going to a Nexus 9 so I have to make sure it can update or Im going to lose money on the sale.
DroidDogg said:
Ok I went back to 4.5.2 > installed kingroot > went to safestrap > uninstalled recovery > rebooted to stock recovery and factory reset . Its still doing the same thing it downloads to 100 and doesnt do anything...
Click to expand...
Click to collapse
DroidDogg said:
I might be selling the device and going to a Nexus 9 so I have to make sure it can update or Im going to lose money on the sale.
Click to expand...
Click to collapse
IDK - should work. You can try downloading the latest version of FireOS here; installation instructions here. Also verify OTA apk is installed and properly named (here).
It's likely 4.5.x is the terminal release of FireOS for 3rd gen devices; potential buyers will not be severely disadvantaged on 4.5.2.
OK I tried to update to 4.5.5.1 from 4.5.2 (said it was invalid update) do I need to update sequentially like 4.5.3 first?
Update 1: Tried 4.5.3 said update file not valid again. I'm beginning to think this restore file I found on here that was Safestrap 4.5.2 might be the wrong zip for this device even though it installs...
Update 2: Tried another TWRP 4.5.5, it installed, then I did the same thing again removed SafeStrap. Then factory reset...
Why can't I update to 4.5.5.1 after returning from CM11 this is so frustrating.
DroidDogg said:
OK I tried to update to 4.5.5.1 from 4.5.2 (said it was invalid update) do I need to update sequentially like 4.5.3 first?
Update 1: Tried 4.5.3 said update file not valid again. I'm beginning to think this restore file I found on here that was Safestrap 4.5.2 might be the wrong zip for this device even though it installs...
Update 2: Tried another TWRP 4.5.5, it installed, then I did the same thing again removed SafeStrap. Then factory reset...
Why can't I update to 4.5.5.1 after returning from CM11 this is so frustrating.
Click to expand...
Click to collapse
As previously posted - IDK and I do not think anyone else does either. What I do know is every flash (some which appear questionable) presents another failure opportunity that could yield an unrecoverable device. Keep experimenting and posting results; others will learn from your efforts. Just recognize the risk and know when to say 'good enough'. Pushing from 4.5.2 to 4.5.5.1 buys you no additional capability/functionality/stability at this time.
DroidDogg said:
OK I tried to update to 4.5.5.1 from 4.5.2 (said it was invalid update) do I need to update sequentially like 4.5.3 first?
Update 1: Tried 4.5.3 said update file not valid again. I'm beginning to think this restore file I found on here that was Safestrap 4.5.2 might be the wrong zip for this device even though it installs...
Update 2: Tried another TWRP 4.5.5, it installed, then I did the same thing again removed SafeStrap. Then factory reset...
Why can't I update to 4.5.5.1 after returning from CM11 this is so frustrating.
Click to expand...
Click to collapse
Do you checked if the DeviceSoftwareOTA.apk is there? (which @Davey126 mentioned above).
I was in the same situation and had to rename it back, which I'd renamed before as described in the OTA blocking tutorial. http://forum.xda-developers.com/showpost.php?p=59160158&postcount=1
DroidDogg said:
OK I tried to update to 4.5.5.1 from 4.5.2 (said it was invalid update) do I need to update sequentially like 4.5.3 first?
Update 1: Tried 4.5.3 said update file not valid again. I'm beginning to think this restore file I found on here that was Safestrap 4.5.2 might be the wrong zip for this device even though it installs...
Update 2: Tried another TWRP 4.5.5, it installed, then I did the same thing again removed SafeStrap. Then factory reset...
Why can't I update to 4.5.5.1 after returning from CM11 this is so frustrating.
Click to expand...
Click to collapse
did you ever figure this out? i'm in the same boat right now, except i don't even know how to remove the recovery. i'm running safestrap 4.01 and fire rom 4.5.2. I saw another post here http://forum.xda-developers.com/showpost.php?p=49687774&postcount=9 but i'm not quite sure if it will work ( i just don't want to brick my kindle). I got it unrooted but that is about it
mzk1 said:
did you ever figure this out? i'm in the same boat right now, except i don't even know how to remove the recovery. i'm running safestrap 4.01 and fire rom 4.5.2. I saw another post here http://forum.xda-developers.com/showpost.php?p=49687774&postcount=9 but i'm not quite sure if it will work ( i just don't want to brick my kindle). I got it unrooted but that is about it
Click to expand...
Click to collapse
Ignore that post; dangerous to futz with build.prop on this device. Try the following:
- reroot (yes, this is necessary)
- browse to /system/priv-app/ and search for DeviceSoftwareOTA.???, where '???' is likely 'bak' but could be any series of characters
- rename above file to DeviceSoftwareOTA.apk (this is the app {likely one of several} that handles OTA updates on FireOS v4)
- reboot again
- verify device is registered with Amazon
- check every 10-15 min for availability of OTA update; it will almost certainly be 4.5.5.1; allow the update to proceed
Davey126 said:
Ignore that post; dangerous to futz with build.prop on this device. Try the following:
- reroot (yes, this is necessary)
- browse to /system/priv-app/ and search for DeviceSoftwareOTA.???, where '???' is likely 'bak' but could be any series of characters
- rename above file to DeviceSoftwareOTA.apk (this is the app {likely one of several} that handles OTA updates on FireOS v4)
- reboot again
- verify device is registered with Amazon
- check every 10-15 min for availability of OTA update; it will almost certainly be 4.5.5.1; allow the update to proceed
Click to expand...
Click to collapse
Thanks for the steps but I've tried that already. The kindle does find the update but only to 4.5.3. It downloads it and then does nothing. just stays there. It might give an error after a while and go back to where it checks for updates. I tried to side load the newest rom which I have manually downloaded from amazon, the tablet recognized it at first but then gave me an error. Is it crucial to remove the recovery in order to obtain the update?
mzk1 said:
Thanks for the steps but I've tried that already. The kindle does find the update but only to 4.5.3. It downloads it and then does nothing. just stays there. It might give an error after a while and go back to where it checks for updates. I tried to side load the newest rom which I have manually downloaded from amazon, the tablet recognized it at first but then gave me an error. Is it crucial to remove the recovery in order to obtain the update?
Click to expand...
Click to collapse
If you are referring to Safestrap v4 recovery then absolutely yes. The app itself can stay but recovery must be removed (uninstalled). Lucky you didn't score a brick trying to update FireOS with Safestrap recovery installed.
Davey126 said:
If you are referring to Safestrap v4 recovery then absolutely yes. The app itself can stay but recovery must be removed (uninstalled). Lucky you didn't score a brick trying to update FireOS with Safestrap recovery installed.
Click to expand...
Click to collapse
I got to the step where everything is ready to go. the device has been reset to factory default, safestrap recovery has been uninstalled. the device got registered in amazon store and found an update 4.5.3 but it still can't flash it after downloading. I copied the newest 4.5.5 bin file to the tablet, but when i tried to hit update I got a message: unable to complete update because the update file is not valid. please try downloading file again. Right now I'm on the 13.4.5.2 rom which I got here http://forum.xda-developers.com/kindle-fire-hdx/development/hdx-stock-images-pre-rooted-updates-t2911954. Is there any other ideas on how to make update to work?
should I just edit buildprop for downgrade? i will need root for that. Can you advise, please
mzk1 said:
I got to the step where everything is ready to go. the device has been reset to factory default, safestrap recovery has been uninstalled. the device got registered in amazon store and found an update 4.5.3 but it still can't flash it after downloading. I copied the newest 4.5.5 bin file to the tablet, but when i tried to hit update I got a message: unable to complete update because the update file is not valid. please try downloading file again. Right now I'm on the 13.4.5.2 rom which I got here http://forum.xda-developers.com/kindle-fire-hdx/development/hdx-stock-images-pre-rooted-updates-t2911954. Is there any other ideas on how to make update to work?
should I just edit buildprop for downgrade? i will need root for that. Can you advise, please
Click to expand...
Click to collapse
Four choices:
- Modify build.prop, attempt a downgrade and brick your device. Go ahead, I'll wait ...
tip: relying on uncollaborated guidance in a three year old post is rarely best practice
- Root, reinstall Safestrap v4 + CM/Nexus and leave well enough alone. Your device works. Upgrading is not all it's cracked up to be. Kinda like that sweet looking honey/hunk in the bar on a foggy Saturday night.
- As above but reflash the Safestrap compatible (no other) version of FireOS 13.4.5.2. Possible something didn't go well the first time around which is preventing OTAs from being processed correctly. AFAIK - OTA is the only path to 4.5.5.1 as Amazon only offers 4.5.5 for download.
- Attempt a rollback to 3.2.8 followed by an immediate upgrade to 13.4.5.2 as documented here. This path is both the riskiest and the one most likely to clear whatever is blocking OTA updates. If you choose this option be sure to follow instructions exactly including linked files (not others you may have lying around). It is essential WiFi remain off (airplane/flight mode engaged) during the brief window your device is on 13.3.2.8. If an OTA update arrives on this version the device will hard brick with NO possible recovery.
Davey126 said:
Four choices:
- Modify build.prop, attempt a downgrade and brick your device. Go ahead, I'll wait ...
tip: relying on uncollaborated guidance in a three year old post is rarely best practice
- Root, reinstall Safestrap v4 + CM/Nexus and leave well enough alone. Your device works. Upgrading is not all it's cracked up to be. Kinda like that sweet looking honey/hunk in the bar on a foggy Saturday night.
- As above but reflash the Safestrap compatible (no other) version of FireOS 13.4.5.2. Possible something didn't go well the first time around which is preventing OTAs from being processed correctly. AFAIK - OTA is the only path to 4.5.5.1 as Amazon only offers 4.5.5 for download.
- Attempt a rollback to 3.2.8 followed by an immediate upgrade to 13.4.5.2 as documented here. This path is both the riskiest and the one most likely to clear whatever is blocking OTA updates. If you choose this option be sure to follow instructions exactly including linked files (not others you may have lying around). It is essential WiFi remain off (airplane/flight mode engaged) during the brief window your device is on 13.3.2.8. If an OTA update arrives on this version the device will hard brick with NO possible recovery.
Click to expand...
Click to collapse
thanks for the solutions. I figured since it is such a pain to get it to work I'll just stick with Nexus ROM now.
mzk1 said:
thanks for the solutions. I figured since it is such a pain to get it to work I'll just stick with Nexus ROM now.
Click to expand...
Click to collapse
Yep - that would be my choice too. Take note there are two Nexus builds, one for devices that have a 4.5.5.1 kernel, the other for older kernels. Try the former first as it as actively maintained and has a broader feature set. Links below:
old: http://forum.xda-developers.com/kindle-fire-hdx/development/rom-hdx-nexus-v4-0-1-t3125808
new: http://forum.xda-developers.com/kindle-fire-hdx/orig-development/rom-fire-nexus-rom-ktu84q-t3322931
Hi,
my version of Android doesn't want to update. I get no OTA updates. I tried to install these two updates manually (using dload folder):
[BETA][6.0][EMUI4.0] PLK-L01 B312(WEU) [OTA FULL UPDATE B140]
[STB][5.0][EMUI3.1] PLK-L01 B130(WEU) [OTA UPDATE B121]
On screens the updates seems working fine (it goes till 100% and says upgrade was successful), but after reboot the version is still the same.
Any idea please?
Thank you,
Sebastien.
sebastien_be said:
Hi,
my version of Android doesn't want to update. I get no OTA updates. I tried to install these two updates manually (using dload folder):
[BETA][6.0][EMUI4.0] PLK-L01 B312(WEU) [OTA FULL UPDATE B140]
[STB][5.0][EMUI3.1] PLK-L01 B130(WEU) [OTA UPDATE B121]
On screens the updates seems working fine (it goes till 100% and says upgrade was successful), but after reboot the version is still the same.
Any idea please?
Thank you,
Sebastien.
Click to expand...
Click to collapse
Enter in Hicare and try to request the update.
I actually did not understand much what you want but if you want to install MM, just install B330b manually.
longtime Nexus / Pixel owner, and sometime in the last several months on this P6 ( or possibly since the beginning of this phone?), my OTA's are failing. They hit the 'resume when phone isn't being used screen', but despite swipe closing apps, laying the phone flat and untouched, plugging in charger, nothing will get the OTA update to continue.
I am rooted, otherwise vanilla A13, but this goes back to A12 versions too.
I am forced to sideload updates each month.
Not sure what's blocking the updates.
Anyone else having this experience?
deusfaux said:
longtime Nexus / Pixel owner, and sometime in the last several months on this P6 ( or possibly since the beginning of this phone?), my OTA's are failing. They hit the 'resume when phone isn't being used screen', but despite swipe closing apps, laying the phone flat and untouched, plugging in charger, nothing will get the OTA update to continue.
I am rooted, otherwise vanilla A13, but this goes back to A12 versions too.
I am forced to sideload updates each month.
Not sure what's blocking the updates.
Anyone else having this experience?
Click to expand...
Click to collapse
You're rooted so you're failing the pr-OTA block verifications, thus the OTA is failing, is the likely scenario.
Is that a feature newer to later Pixels or Android versions? Didn't have that issue in the past. Maybe the difference is I could still download and *attempt* to install an OTA even b4 removing root, but now it checks in advance before even downloading? Next OTA I'll test this theory and remove root b4 even starting the download.
deusfaux said:
Is that a feature newer to later Pixels or Android versions? Didn't have that issue in the past. Maybe the difference is I could still download and *attempt* to install an OTA even b4 removing root, but now it checks in advance before even downloading? Next OTA I'll test this theory and remove root b4 even starting the download.
Click to expand...
Click to collapse
I normally manually flash updates with fastboot.
Only use OTA update on one or two devices.
You have to restore the original boot image.
Run the update and patch the new boot image with Magisk.
Normally the steps are something like this.
1. Open the Magisk app and restore images.
--- Do not reboot ---
2. Open the OTA Updater
- Download and install the OTA -
--- Do not reboot to continue ---
3. Open the Magisk app and install to inactive slot (after OTA).
4. Switch back to the OTA updater and select reboot to continue.
Cheers.
You could use PixelFlasher to make the process a little easier If you don't want to do everything manually each month.