Database Develop

Installing OTAs on the Pixel 3 XL with Magisk Installed

Hello all,
On my new Pixel 3 XL, I installed Magisk immediately after doing the initial setup. I then tried taking the January 2019 OTA update (the phone was running the original build from September 2018) and installing the update using the instructions here for devices with A/B partitions: https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
This however did not work and the update still failed to install. I ended up doing the upgrade manually via the bootloader but I would like to ask about how to handle this process for future updates. I am running the latest stable version of Magisk.
Thank you

Is it possible that /system or /vendor have been altered in some way? That would cause the OTA to fail...

Didgeridoohan said:
Is it possible that /system or /vendor have been altered in some way? That would cause the OTA to fail...
Click to expand...
Click to collapse
I still pass SafetyNet though. Wouldn't modifying either of those cause it to fail?

David B. said:
I still pass SafetyNet though. Wouldn't modifying either of those cause it to fail?
Click to expand...
Click to collapse
As a rule, you can do quite heavy modifications to both /system and/vendor and still pass SN. So, not necessarily...

Didgeridoohan said:
As a rule, you can do quite heavy modifications to both /system and/vendor and still pass SN. So, not necessarily...
Click to expand...
Click to collapse
Well I do use the Internal Audio Plugin which may write stuff to /system and/or /vendor. I am not sure though. I do not remember if I had it installed at that point though. I do have it installed now though. If it turns out that the app is the reason it's not working, hopefully I will be able to uninstall it when trying the OTA again.

Hi all. I have searched for information and have seen a lot and varied. I come to confirm more than anything and to know if you have a clear idea.
I have my 3XL pixel rooted with Magisk.
First question: With the root of magisk the system does NOT detect the new monthly update updates. Is this normal? I understood that I would detect it but that it would NOT let me update it.
As a result of that question I found this other ...
https : // topjohnwu. github.io/Magisk/tutorials.html (sorry, there are spaces)
I'm not sure if this tutorial is valid for the Pixel 3XL. I have reproduced it and ... or something I have not done well or is not compatible with our device.
The objective of all this is to know if, with the rooted phone, OTAs can be detected and, in case the answer is no, to know if there is any method like the one that Magisk proposes without having to download the OTA, install by the recovery and re-root with twrp.
I have not used any magisk module, but I do have Es File Explorer installed with root viewer, titanium backup and Swift Insaller. I do not think this has modified / system or / vendor.
Thanks and best regards!

ciltocruz said:
Hi all. I have searched for information and have seen a lot and varied. I come to confirm more than anything and to know if you have a clear idea.
I have my 3XL pixel rooted with Magisk.
First question: With the root of magisk the system does NOT detect the new monthly update updates. Is this normal? I understood that I would detect it but that it would NOT let me update it.
As a result of that question I found this other ...
https : // topjohnwu. github.io/Magisk/tutorials.html (sorry, there are spaces)
I'm not sure if this tutorial is valid for the Pixel 3XL. I have reproduced it and ... or something I have not done well or is not compatible with our device.
The objective of all this is to know if, with the rooted phone, OTAs can be detected and, in case the answer is no, to know if there is any method like the one that Magisk proposes without having to download the OTA, install by the recovery and re-root with twrp.
I have not used any magisk module, but I do have Es File Explorer installed with root viewer, titanium backup and Swift Insaller. I do not think this has modified / system or / vendor.
Thanks and best regards!
Click to expand...
Click to collapse
Hello,
The issue that you are describing is identical to what I observed during the February OTA update. It was not showing up on my phone. Supposedly if you wait long enough it will be detected, but I got impatient with waiting and just did it manually. It is worth noting however that when I got my Pixel 3 XL (I got it in January), I rooted it immediately before installing the January patches, and the behavior that you described as what should have happened is what I observed: the update was detected, but I could not install it. The odd thing about it was that even after uninstalling Magisk, I still could not get it to install and therefore ended up manually sideloading that update as well. It is worth noting that as part of that sideload, I chose to wipe the phone so that whatever modifications I must have made to /system or /vendor would be gone.
I am sorry that I could not provide any real help for this issue since I have been sideloading as a workaround. If you come up with a real solution to this, please let me know. Otherwise, you may want to just sideload manually.

David B. said:
Hello,
The issue that you are describing is identical to what I observed during the February OTA update. It was not showing up on my phone. Supposedly if you wait long enough it will be detected, but I got impatient with waiting and just did it manually. It is worth noting however that when I got my Pixel 3 XL (I got it in January), I rooted it immediately before installing the January patches, and the behavior that you described as what should have happened is what I observed: the update was detected, but I could not install it. The odd thing about it was that even after uninstalling Magisk, I still could not get it to install and therefore ended up manually sideloading that update as well. It is worth noting that as part of that sideload, I chose to wipe the phone so that whatever modifications I must have made to /system or /vendor would be gone.
I am sorry that I could not provide any real help for this issue since I have been sideloading as a workaround. If you come up with a real solution to this, please let me know. Otherwise, you may want to just sideload manually.
Click to expand...
Click to collapse
I see that there is no other option than to do it manually and reinstall magisk later every month ...

ciltocruz said:
I see that there is no other option than to do it manually and reinstall magisk later every month ...
Click to expand...
Click to collapse
Well at this point I will not have a chance to test this belief out until March.

David B. said:
Well at this point I will not have a chance to test this belief out until March.
Click to expand...
Click to collapse
I rerooted the phone with Magisk and it's perfect.
Unfortunately, with the March update, my 3LX pixel will not notify me of this update and I will have to install it manually with adb.
Then I will have to manually re-root magisk. I can not find a way to make the magisk tutorial work so I do not have to do this manual process. I believe that Magisk modifies /vendor and /system and "to uninstall magisk with the boot_patched", to the new pixel 3 or to Android Pie does not matter to him because he knows what is happening.

ciltocruz said:
I rerooted the phone with Magisk and it's perfect.
Unfortunately, with the March update, my 3LX pixel will not notify me of this update and I will have to install it manually with adb.
Then I will have to manually re-root magisk. I can not find a way to make the magisk tutorial work so I do not have to do this manual process. I believe that Magisk modifies /vendor and /system and "to uninstall magisk with the boot_patched", to the new pixel 3 or to Android Pie does not matter to him because he knows what is happening.
Click to expand...
Click to collapse
I am confused. How can you know what is going to happen with the March update when it has not been released yet?

David B. said:
I am confused. How can you know what is going to happen with the March update when it has not been released yet?
Click to expand...
Click to collapse
Nooooo Sorry, maybe I explained wrong.
I want to say that, like in January and February, when the March update is released, the Pixel 3XL, as it is rooted, will not recognize it. It will not give me the notice of a new update.
Better like that?

ciltocruz said:
Nooooo Sorry, maybe I explained wrong.
I want to say that, like in January and February, when the March update is released, the Pixel 3XL, as it is rooted, will not recognize it. It will not give me the notice of a new update.
Better like that?
Click to expand...
Click to collapse
Oh I understand. I suppose we'll just have to wait and see. ?

David B. said:
Oh I understand. I suppose we'll just have to wait and see.
Click to expand...
Click to collapse
I installed the March update via recovery. No problem. Then I have reinstalled Magisk with the TWRP image.
I still do not know how to make this tutorial for Pixel 3 work
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Has anyone succeeded? The objective is:
- That the rooted phone detects the OTA.
- To be able to uninstall the root with the Magisk Manager application.
- To be able to install the OTA like any normal user.
- Be able to reinstall the root via Magisk Manager.
All without the need of adb, sideload, recovery, TWRP or anything "technical".
Greetings!

ciltocruz said:
I installed the March update via recovery. No problem. Then I have reinstalled Magisk with the TWRP image.
I still do not know how to make this tutorial for Pixel 3 work
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Has anyone succeeded? The objective is:
- That the rooted phone detects the OTA.
- To be able to uninstall the root with the Magisk Manager application.
- To be able to install the OTA like any normal user.
- Be able to reinstall the root via Magisk Manager.
All without the need of adb, sideload, recovery, TWRP or anything "technical".
Greetings!
Click to expand...
Click to collapse
I also had to install the update via recovery, as the option to use the built-in updater was not detecting that the update was available again. Perhaps it's time we ask @topjohnwu Magisk Queries/ @topjohnwu about this?

I've seen (and commented in) at least 4 previous threads reporting the same issue with OTA updates and none of them have been taken seriously or prompted any kind of further investigation. Oh well, 5th time lucky perhaps?
Anyway, I have exactly the same issue with my Pixel 2; I used to receive notifications for OTA updates back when I was running on Oreo with Magisk, but after updating to Pie in September 2018 I haven't received a single new OTA notification.
Pie was installed from the factory image, including a device wipe, so it was a completely fresh start. I've also tried reflashing system.img and vendor.img just in case those partitions somehow got modified at some point, but it made no difference. My device simply will not detect new OTA updates, so my only option is to sideload the update and reflash magisk every month.
As per a previous post of mine, I found other reports of the same issue on Reddit and the common factors seemed to be Pixel devices, Pie and Magisk.

nogaff said:
I've seen (and commented in) at least 4 previous threads reporting the same issue with OTA updates and none of them have been taken seriously or prompted any kind of further investigation. Oh well, 5th time lucky perhaps?
Anyway, I have exactly the same issue with my Pixel 2; I used to receive notifications for OTA updates back when I was running on Oreo with Magisk, but after updating to Pie in September 2018 I haven't received a single new OTA notification.
Pie was installed from the factory image, including a device wipe, so it was a completely fresh start. I've also tried reflashing system.img and vendor.img just in case those partitions somehow got modified at some point, but it made no difference. My device simply will not detect new OTA updates, so my only option is to sideload the update and reflash magisk every month.
As per a previous post of mine, I found other reports of the same issue on Reddit and the common factors seemed to be Pixel devices, Pie and Magisk.
Click to expand...
Click to collapse
What's odd about my situation is that when I first got the phone and rooted the image that it came with (September 2018), I did get the OTA notification. I just could not get it to install even after following the Magisk uninstallation steps provided in the official Magisk tutorial. It's only a minor inconvenience and I can live with it, but the fact that it happens still bothers me.

David B. said:
What's odd about my situation is that when I first got the phone and rooted the image that it came with (September 2018), I did get the OTA notification. I just could not get it to install even after following the Magisk uninstallation steps provided in the official Magisk tutorial. It's only a minor inconvenience and I can live with it, but the fact that it happens still bothers me.
Click to expand...
Click to collapse
This happened to me too. I put the root and the first OTA did arrive but, because I had root, I could not install. I had to do it manually with adb.

ciltocruz said:
This happened to me too. I put the root and the first OTA did arrive but, because I had root, I could not install. I had to do it manually with adb.
Click to expand...
Click to collapse
Did you try using the tutorial as well?

David B. said:
Did you try using the tutorial as well?
Click to expand...
Click to collapse
Yes, but with my rooted device the notification of NEW UPDATE does not appear. I know I can not INSTALL it, but is there also no update notice? This is what I need. An update notice.
With that warning I will be able to patch the boot image with magisk and then I will be able to download and install the OTA. Then re-rooted and ready.

OTA not yet received - QD1A.190821.007, magisk installed

Hi,
This is the first time I'm using magisk, I understand that since the system partition is not changing that I should be able to receive OTA regularly (subject to the official guide)
I have an unlocked pixel 4 xl and I'm still on October 5 security patch.
Anyone knows if this situation is normal?
Thanks

Pixeling said:
Hi,
This is the first time I'm using magisk, I understand that since the system partition is not changing that I should be able to receive OTA regularly (subject to the official guide)
I have an unlocked pixel 4 xl and I'm still on October 5 security patch.
Anyone knows if this situation is normal?
Thanks
Click to expand...
Click to collapse
https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md

In a simple way.
You have to flash the stock boot.img of your current OS, then update, then patch magisk if you want to.

Pixeling said:
Hi,
This is the first time I'm using magisk, I understand that since the system partition is not changing that I should be able to receive OTA regularly (subject to the official guide)
I have an unlocked pixel 4 xl and I'm still on October 5 security patch.
Anyone knows if this situation is normal?
Thanks
Click to expand...
Click to collapse
Just download the factory image and flash it manually in fastboot. Remember to edit the flash-all.bat file my taking the -W out first though or it will wipe your phone. This has always been easier and faster for me.

I wanted to do so (flash factory image) but wasn't sure which version to pick. I ended up going with 007.A3. Thanks.
I am already familiar with the OTA guide I just didn't receive the OTA for some reason.

murphyjasonc said:
Just download the factory image and flash it manually in fastboot. Remember to edit the flash-all.bat file my taking the -W out first though or it will wipe your phone. This has always been easier and faster for me.
Click to expand...
Click to collapse
Thank you I loved it this method ⁦[emoji1360]⁩
Sent from my Pixel 4 XL using Tapatalk

Pixel 4 "FLAME" March 2020 QQ2A.200305.003 boot.img - Stock and Magisk v20.4 Patched

Pixel 4 "FLAME" March 2020 QQ2A.200305.003 boot.img - Stock and Magisk v20.4 Patched
Hey all, I just updated my wife's P4 to Magisk 20.4 as of yesterday and have had no issues so far on the new version (nor on my P4XL). Here are the stock and recently newly updated Magisk patched (v20.4) boot images. I couldn't direct install the update on either of the phones via Magisk Manager, so I figured I would share these images.
Stock March 2020 boot image: https://www.androidfilehost.com/?fid=4349826312261757144
Magisk Patched (v20.4) March 2020 boot image: https://www.androidfilehost.com/?fid=4349826312261757143
Remember, these are ONLY for those on QQ2A.200305.003 firmware already. Don't flash if you don't know what you're doing.

Hey i5lee8bit,
Thanks for posting the p4 OTA boot files. worked perfectly. I have a p4xl as well. How do I extract the boot image from the device? I can not find the new boot image online from google or anything.

Which method did you use to flash? I've tried it a few different ways and they don't work. I'm thinking on factory resetting and trying again but I don't want to do if I don't have to. I've had no problem rooting my pixel 4 on any of the other updates but for some reason I can't root the March update. It looks like things flash fine but when the phone reboots it gets to a black screen and just stays there. I know it can take a while during app optimization so I let it set over night. Still on a black screen the next morning.

falawefulwaffle said:
Hey i5lee8bit,
Thanks for posting the p4 OTA boot files. worked perfectly. I have a p4xl as well. How do I extract the boot image from the device? I can not find the new boot image online from google or anything.
Click to expand...
Click to collapse
I'm not sure, I just grab them from the factory images (https://developers.google.com/android/images#coral). If it's not there, I wouldn't know. I came from years of HTC devices, but even then we either used TWRP or RUU decryption tool / firmware zips. Not sure if there's a way to extract directly from the device using dd or adb commands, but even then that was done using TWRP. Not sure if there's an alternate method; I'm not the right person to ask either, sorry. Tulsadiver's thread that I linked to for the other guy mentions a boot.img extractor, but I've never used it.
But if the boot file I provided worked perfectly for you, I would assume that means you are using the USA Unlocked model, and it should be available on the developers.google.com link I posted.
Spookymyo said:
Which method did you use to flash? I've tried it a few different ways and they don't work. I'm thinking on factory resetting and trying again but I don't want to do if I don't have to. I've had no problem rooting my pixel 4 on any of the other updates but for some reason I can't root the March update. It looks like things flash fine but when the phone reboots it gets to a black screen and just stays there. I know it can take a while during app optimization so I let it set over night. Still on a black screen the next morning.
Click to expand...
Click to collapse
From bootloader, just the simple fastboot flash boot name_of_boot_image.img
It sounds like you OTA'd to the March build? And you previously had it Magisk rooted on a prior firmware version? It could be a module not playing nice. Maybe try booting into Magisk Core mode, see Tulsadiver's thread: https://forum.xda-developers.com/pixel-4/how-to/magisk-modules-disabler-booting-magisk-t3991739
Sorry for the delayed responses btw. Quarantine + work + school + new baby = wtf.

i5lee8bit said:
I'm not sure, I just grab them from the factory images (https://developers.google.com/android/images#coral). If it's not there, I wouldn't know. I came from years of HTC devices, but even then we either used TWRP or RUU decryption tool / firmware zips. Not sure if there's a way to extract directly from the device using dd or adb commands, but even then that was done using TWRP. Not sure if there's an alternate method; I'm not the right person to ask either, sorry. Tulsadiver's thread that I linked to for the other guy mentions a boot.img extractor, but I've never used it.
But if the boot file I provided worked perfectly for you, I would assume that means you are using the USA Unlocked model, and it should be available on the developers.google.com link I posted.
From bootloader, just the simple fastboot flash boot name_of_boot_image.img
It sounds like you OTA'd to the March build? And you previously had it Magisk rooted on a prior firmware version? It could be a module not playing nice. Maybe try booting into Magisk Core mode, see Tulsadiver's thread: https://forum.xda-developers.com/pixel-4/how-to/magisk-modules-disabler-booting-magisk-t3991739
Sorry for the delayed responses btw. Quarantine + work + school + new baby = wtf.
Click to expand...
Click to collapse
Thanks for the reply. I ended up getting it to work using the "payload_dumper-win64" method i found in another thread to extract the boot.img from the payload.bin file. Turns out the OTA file was online from google.
To updatePixel 4 xl with "coral-ota-qq2a.200305.003-3b25765d" MAach update OTA software:
- uninstalled Magisk
-updated software
-reinstalled magisk
-patched the boot img from payload.bin
-pushed modified boot to device
-Done
Everything seems to be working well. I got to use python for the first time, so that was kind of fun. I was a flashing machine back around the galaxy s4.

I got root working. Spent so much time trying different things and all I had to do was factory reset my phone. There must have been some file or module interfering with the process. Once I reset my phone the root process went without error. ?*

General [IMG] Boot + magisk patched boot images

Hi, I have decided to gather boot images and magisk patched images to one thread for now. I will try to edit this thread to be up-to-date. You can let me know what could you want next or if anything is wrong etc.
Stock boot.img files (direct links): ​
EU NE2213_11_A.12​
Stock boot.img - link
EU NE2213_11_A.10​
Stock boot.img - link
​Magisk patched boot.img are here a file that can be downloaded (I am using magisk canary usually, but in Magisk, you can change the channel from the canary to stable etc.) - names as the versions come. ​
Below this there are those magisk patched files which you just flash (or boot and then flash directly from the Magisk app) via fastboot ​

Reserved

Don't you need to patch vendor_boot.img as well like OnePlus 9 pro ?

HessNL said:
Don't you need to patch vendor_boot.img as well like OnePlus 9 pro ?
Click to expand...
Click to collapse
Apparently not. I have patched that stock boot via magisk, then via fastboot boot <patchedimage.img> booted (and also tested if it actually boots) and when it booted, via magisk app I did "Direct install (recommended)", rebooted and done.

Oh okay you had a temporary boot we that's good to know well it works that's the most important thing ain't it

Noob question I been on locked bootloader for years so haven't been in the root scene, but I have US model NE2215 I'm guessing I need to wait for the firmware to be available to get the boot img? Did I just got my phone too early? Already oem unlocked now just waiting for twrp and root info. I always wanted a OnePlus phone because the community is big, but doesn't seem like much people upgraded from 9 pro.

HessNL said:
Oh okay you had a temporary boot we that's good to know well it works that's the most important thing ain't it
Click to expand...
Click to collapse
Yes, because this is probably and currently the most secure option to root it as we haven't got twrp available yet.
BuBbLeFIZzY said:
Noob question I been on locked bootloader for years so haven't been in the root scene, but I have US model NE2215 I'm guessing I need to wait for the firmware to be available to get the boot img? Did I just got my phone too early? Already oem unlocked now just waiting for twrp and root info. I always wanted a OnePlus phone because the community is big, but doesn't seem like much people upgraded from 9 pro.
Click to expand...
Click to collapse
That's not that you have it early. The phone itself is early in spite of rooting and doing things like rooting, custom recoveries, ROMs etc. I currently can't find boot img for your model, but once I do, I will post it here for you with patched one.

Thank you kouzelnik3 for this thread !
I was going to dl original firmware and patch it myself but found your thread in time with all ready to flash
Rooted OP10 pro done, now i can't wait to see some TWRP and roms in the future

fozzy056 said:
Thank you kouzelnik3 for this thread !
I was going to dl original firmware and patch it myself but found your thread in time with all ready to flash
Rooted OP10 pro done, now i can't wait to see some TWRP and roms in the future
Click to expand...
Click to collapse
You're really welcome, I wanted to unite those currently quite hard rooting stuff!
And yes, I can't wait to see twrp too!

Is there a known stock boot.img of the NE2215_11_A.10? I assume I shouldn't use the 2213_11_A.10.

GeekMcLeod said:
Is there a known stock boot.img of the NE2215_11_A.10? I assume I shouldn't use the 2213_11_A.10.
Click to expand...
Click to collapse
Not yet unfortunately. Or I don't know about it yet. :/

kouzelnik3 said:
Not yet unfortunately. Or I don't know about it yet. :/
Click to expand...
Click to collapse
Yeah.. I googled a lot last night once I got my phone trying to find it to root it. I need me that extra bit of customization.
Is there a way I can get it from my phone?

what am i doing wrong here rooted for 7+ years and some reason can't get this working.
Just moved over from ColorOS to Oxygen - when i try to flash the boot.img (patched one) all i get is this

Johnstan725 said:
what am i doing wrong here rooted for 7+ years and some reason can't get this working.
Just moved over from ColorOS to Oxygen - when i try to flash the boot.img (patched one) all i get is this
Click to expand...
Click to collapse
Ignore me but for anyone else that tries looks like i had to reboot bootloader and flash the img via bootloader...
thought it's normally flashed via fastboot?! weird phone

Johnstan725 said:
Ignore me but for anyone else that tries looks like i had to reboot bootloader and flash the img via bootloader...
thought it's normally flashed via fastboot?! weird phone
Click to expand...
Click to collapse
You should wipe the phone and start all over or else you won't be able to take ota updates. Never flash the patched boot image since you bypass the magisk backup feature. You have to wait for the full update package to update if you flash the boot. Ppl have previously had update issues after flashing.

g96818 said:
You should wipe the phone and start all over or else you won't be able to take ota updates. Never flash the patched boot image since you bypass the magisk backup feature. You have to wait for the full update package to update if you flash the boot. Ppl have previously had update issues after flashing.
Click to expand...
Click to collapse
Wiped the phone already, what difference would it make if i remove root or flash stock boot then flash ota and reflash boot?

Johnstan725 said:
Wiped the phone already, what difference would it make if i remove root or flash stock boot then flash ota and reflash boot?
Click to expand...
Click to collapse
Not sure what else magisk does during the backup process, but doing what you’re describing didn’t work for users on 8T and they usually ended up soft bricking. Everyone who flashed it vice installing from magisk app had to wait for op to post the full rom or for someone to post a repacked fastboot rom to update.
You do what you need to do, I’m just giving you some experience and recommendations since you just wiped and flashed the boot.

g96818 said:
Not sure what else magisk does during the backup process, but doing what you’re describing didn’t work for users on 8T and they usually ended up soft bricking. Everyone who flashed it vice installing from magisk app had to wait for op to post the full rom or for someone to post a repacked fastboot rom to update.
You do what you need to do, I’m just giving you some experience and recommendations since you just wiped and flashed the boot.
Click to expand...
Click to collapse
Interesting.
I moved over from ColorOS to oxygen OS, wiped the device then just booted a patched boot img, and installed direct.
I assume I flash ota and go onto magisk and do inactive slot? Where does the issue lie what method should I have gone down?

Johnstan725 said:
Interesting.
I moved over from ColorOS to oxygen OS, wiped the device then just booted a patched boot img, and installed direct.
I assume I flash ota and go onto magisk and do inactive slot? Where does the issue lie what method should I have gone down?
Click to expand...
Click to collapse
Hmmm. Well you should be fine if you patched the boot and let magisk do the install. I only suggested wiping since you said you flashed the img from the bootloader.
You might run into the same problem I have with the 9RT. I too upgraded from color to oos and couldn’t update at all, even though I rooted from the magisk app. I had to wait for someone to make a fastboot rom. I had no problems updating color following my method, but not oos after switching. Hopefully that’s not the case for you.

Question Updating after root

I have my pixel 7 rooted and I cannot get automatic updates. What would be the best way for me to get updates on my system? Going by the name I'd guess the pixelflasher is used, but I honestly just don't want to brick my Christmas gift so I'm asking for any guidance I can get.

scuzzo500 said:
I have my pixel 7 rooted and I cannot get automatic updates. What would be the best way for me to get updates on my system? Going by the name I'd guess the pixelflasher is used, but I honestly just don't want to brick my Christmas gift so I'm asking for any guidance I can get.
Click to expand...
Click to collapse
You can update any way you want. You might find sideloading the OTA to be easiest.
The only way you can "accidentally" brick your device is if you break the bootloader by flashing the wrong image...but if you're not sure what that means, you probably shouldn't be attempting this anyway.

.

I'm pretty familiar with rooting and updating. If you look at my post history you can verify I've been working with root since Droid x2. I'm currently typing this on a one plus 7 pro I converted to gm1925. However, each platform has its specific issues and every new version of Android can be different. I don't have twrp to backup and I want to make sure I don't brick what, to me, is a significant financial investment. I'm just asking to understand what other individuals feel is best practices.

scuzzo500 said:
I'm pretty familiar with rooting and updating. If you look at my post history you can verify I've been working with root since Droid x2. I'm currently typing this on a one plus 7 pro I converted to gm1925. However, each platform has its specific issues and every new version of Android can be different. I don't have twrp to backup and I want to make sure I don't brick what, to me, is a significant financial investment. I'm just asking to understand what other individuals feel is best practices.
Click to expand...
Click to collapse
I personally update using PixelFlasher and the factory image each month. Others prefer sideloading the OTA. Yet others restore the boot image and take automatic OTAs.
It's completely up to you. Again, the only way you'll brick your device is by doing something stupid such as flashing the wrong image to the bootloader partition. As long as the bootloader functions and you can interact with the device via ADB, it's not bricked and is recoverable

V0latyle said:
I personally update using PixelFlasher and the factory image each month. Others prefer sideloading the OTA. Yet others restore the boot image and take automatic OTAs.
It's completely up to you. Again, the only way you'll brick your device is by doing something stupid such as flashing the wrong image to the bootloader partition. As long as the bootloader functions and you can interact with the device via ADB, it's
Click to expand...
Click to collapse

I still haven't put the phone into regular use because I want to make sure I can keep root while updating. I just cannot stand ads. I'll start reading up on pixelflasher and get a good feel for it. Thank you for the help.

I definitely bet on Pixelflasher. It is idiotproof and very handy.

I like sideloading OTA's when I'm stock. A couple commands from any device with current platform tools and it's done. It's also arguably the documented "Google way". Different strokes for different folks I guess...

Thank you to everyone. I've muddled through pixel flasher and I have updated to TD1A.221105.001. Now I'll jump in the pixelflash thread and ask a few questions.

H
scuzzo500 said:
I have my pixel 7 rooted and I cannot get automatic updates. What would be the best way for me to get updates on my system? Going by the name I'd guess the pixelflasher is used, but I honestly just don't want to brick my Christmas gift so I'm asking for any guidance I can get.
Click to expand...
Click to collapse
I have just updated mine without problems:
1.Open magisk an disable modules.
2.Press uninstall magisk - restore images (DO NOT REBOOT)
4.Install the ota in settings.
5. IMPORTANT, once finished DO NOT REBOOT, open magisk again and press install- (install to inactive slot (after OTA).
Then reboot and open magisk to enable the modules again. (maybe this is not necessary, to disable and enable, but it´s safer.
NOTE: I have done this with december update, for unknown reason it was impossible to me with november. I that case i had to complete uninstall magisk, use pixel flasher and then flash init_boot
patched again.

oscarcam said:
H
I have just updated mine without problems:
1.Open magisk an disable modules.
2.Press uninstall magisk - restore images (DO NOT REBOOT)
4.Install the ota in settings.
5. IMPORTANT, once finished DO NOT REBOOT, open magisk again and press install- (install to inactive slot (after OTA).
Then reboot and open magisk to enable the modules again. (maybe this is not necessary, to disable and enable, but it´s safer.
NOTE: I have done this with december update, for unknown reason it was impossible to me with november. I that case i had to complete uninstall magisk, use pixel flasher and then flash init_boot
patched again.
Click to expand...
Click to collapse
There is no problem if you install the last update without having installed the previous updates?

alsansan said:
There is no problem if you install the last update without having installed the previous updates?
Click to expand...
Click to collapse
If It's an OTA, i supose there is no problem. If the system gives you the option. Otherwise you can avoid previous justo using flasher. If you keep your init_boot patched It's easy to root again once used the flasher.

oscarcam said:
H
I have just updated mine without problems:
1.Open magisk an disable modules.
2.Press uninstall magisk - restore images (DO NOT REBOOT)
4.Install the ota in settings.
5. IMPORTANT, once finished DO NOT REBOOT, open magisk again and press install- (install to inactive slot (after OTA).
Then reboot and open magisk to enable the modules again. (maybe this is not necessary, to disable and enable, but it´s safer.
NOTE: I have done this with december update, for unknown reason it was impossible to me with november. I that case i had to complete uninstall magisk, use pixel flasher and then flash init_boot
patched again.
Click to expand...
Click to collapse
Just followed your instructions and it worked flawlessly. I totally forgot this and figured I would need to reflash each time.

oscarcam said:
H
I have just updated mine without problems:
1.Open magisk an disable modules.
2.Press uninstall magisk - restore images (DO NOT REBOOT)
4.Install the ota in settings.
5. IMPORTANT, once finished DO NOT REBOOT, open magisk again and press install- (install to inactive slot (after OTA).
Then reboot and open magisk to enable the modules again. (maybe this is not necessary, to disable and enable, but it´s safer.
NOTE: I have done this with december update, for unknown reason it was impossible to me with november. I that case i had to complete uninstall magisk, use pixel flasher and then flash init_boot
patched again.
Click to expand...
Click to collapse
Followed your steps. It was easy and worked well.
Thank you

scuzzo500 said:
I still haven't put the phone into regular use because I want to make sure I can keep root while updating. I just cannot stand ads. I'll start reading up on pixelflasher and get a good feel for it. Thank you for the help.
Click to expand...
Click to collapse
I don't understand rooting the phone just to block ads.
Just use Adguard which surpasses any root adblocking abilities.

oscarcam said:
H
I have just updated mine without problems:
1.Open magisk an disable modules.
2.Press uninstall magisk - restore images (DO NOT REBOOT)
4.Install the ota in settings.
5. IMPORTANT, once finished DO NOT REBOOT, open magisk again and press install- (install to inactive slot (after OTA).
Then reboot and open magisk to enable the modules again. (maybe this is not necessary, to disable and enable, but it´s safer.
NOTE: I have done this with december update, for unknown reason it was impossible to me with november. I that case i had to complete uninstall magisk, use pixel flasher and then flash init_boot
patched again.
Click to expand...
Click to collapse
I thought the problem here was that the patching from magisk doesn't back up the boot_init (Yet). If I recall correctly pixel flasher ensured the backup being there.
That would mean next time the attempt to restore images might fail again. Unless if this issue of magisk has already been addressed. I didn't check.

fivefour said:
I don't understand rooting the phone just to block ads.
Just use Adguard which surpasses any root adblocking abilities.
Click to expand...
Click to collapse
That's because you don't root just to block adds.

oscarcam said:
That's because you don't root just to block adds.
Click to expand...
Click to collapse
I know plenty of other uses of root, I have developed several root apps and maintained various kernels over the years.
Read what I quoted.

I read, but I didn't understand the same. Sorry.