Database Info

Stock: Install official OTA and keep root

Just learned of this method from a Reddit user - https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
Sharing here.

Neffy27 said:
Just learned of this method from a Reddit user - https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
Sharing here.
Click to expand...
Click to collapse
I also followed this guide a couple days ago. Running OPW28.2 with Magisk 16.0 Still working on getting Xposed to work without bootloop.

Neffy27 said:
Just learned of this method from a Reddit user - https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
Sharing here.
Click to expand...
Click to collapse
Will modifiying build.prop will make error

Did you follow the option for Devices that have A/B partitions?
So basically, all I need to do is go into magisk, uninstall, restore images. Then apply OTA update. Once the update displays "step 2", go back into Magisk and Install to second slot?

I tried this method, but when I hit "Restore Images" it says "Stock backup does not exist!". Is there a way of putting a stock boot.img for my current FW in the proper location for it to recognize it as a backup? I tried looking this up but got no helpful solution.

I think if you installed Magisk via Recovery like I did it won't keep a backup of the boot.img. I think it does that only if you install Magisk outside of Recovery, which requires that you have a copy of the original boot.img.
Just get a copy of the firmware for your version, extract and write back the original boot.img via Fastboot and then update the OTAs (assuming you made.no changes to your system partition). Then reinstall the custom Recovery if you want and then Magisk again.

I have tried flashing just boot.img, but it didn't work. Could be adaway changing hosts file? Anyhow I just end up flashing back to stock
(minus clearing userdata) taking a few OTA's then re-reooting. Have been able to keep my data no issues. Takes a while but it's what it takes.

I could not get this to work either.
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
OTA could not be applied..
I tried to uninstall Magisk completely, and I boot-looped.

Get March OTA without having to re-install Magisk/TWRP

I read some stuff about doing an OTA update with Magisk (v18) on my Pixel 3 (Feb 2019), but I still have a few questions about doing it. I'd rather avoid re-installing TWRP and Magisk from recovery again, and I'd like to be able to do this all without my computer if possible (see planned process below).
1. From what I've read, I should be able to restore a stock boot image to the inactive boot partition (from within Magisk Manager) , then install the Update (both steps 1 and 2), then reinstall Magisk Manager to the inactive boot partition.. And then reboot, and I should have the update, and keep TWRP and Magisk, right? (just looking for confirmation of the process)
2. I never provided a stock image to Magisk when I installed it originally, and I don't have one right now. How do I extract the boot image from the stock image on the Android website?
3. And do I need to indicate to Magisk that I have a boot image, or will it ask me when I go in to restore non-root?
4. Are OTA updates cumulative, or do I need to update the stock boot image each update?
Thanks!

madhattr999 said:
I read some stuff about doing an OTA update with Magisk (v18) on my Pixel 3 (Feb 2019), but I still have a few questions about doing it. I'd rather avoid re-installing TWRP and Magisk from recovery again, and I'd like to be able to do this all without my computer if possible (see planned process below).
1. From what I've read, I should be able to restore a stock boot image to the inactive boot partition (from within Magisk Manager) , then install the Update (both steps 1 and 2), then reinstall Magisk Manager to the inactive boot partition.. And then reboot, and I should have the update, and keep TWRP and Magisk, right? (just looking for confirmation of the process)
2. I never provided a stock image to Magisk when I installed it originally, and I don't have one right now. How do I extract the boot image from the stock image on the Android website?
3. And do I need to indicate to Magisk that I have a boot image, or will it ask me when I go in to restore non-root?
4. Are OTA updates cumulative, or do I need to update the stock boot image each update?
Thanks!
Click to expand...
Click to collapse
Although what you described works for some devices it won't on the pixel. To update and have twrp and root you'll need a pc. If the ota would flash when you have twrp and root, it won't, it would overwrite twrp and the patched boot image. So you're back to needing a pc to get twrp and install magisk.
For your other questions, if you extract the factory image you'll find another zip file in there. That's were the image files are and you need to extract that zip. And, ota's are cumulative so you don't need install previous ones. But specifically to the boot image, a previous months boot image may or may not be the same as the current one, etc.

jd1639 said:
Although what you described works for some devices it won't on the pixel. To update and have twrp and root you'll need a pc. If the ota would flash when you have twrp and root, it won't, it would overwrite twrp and the patched boot image. So you're back to needing a pc to get twrp and install magisk.
Click to expand...
Click to collapse
I'm confused then. Isn't the method I described specifically for a phone with two boot partitions?
The instructions I am trying to reference:
Devices with A/B Partitions
Due to the fact that these devices have two separate partitions, it is possible to have the OTA installed to the inactive slot and have Magisk Manager to install Magisk onto the updated partition. The out-of-the-box OTA installation works seamlessly and Magisk can be preserved after the installation.
After restoring stock boot image, apply OTAs as you normally would (Settings → System → System Update).
Wait for the installation to be fully done (both step 1 and step 2 of the OTA), do not press the restart button!! Instead, go to (Magisk Manager → Install → Install to Inactive Slot) and install Magisk to the slot that the OTA engine just updated.
After installation is done, press the reboot button in Magisk Manager. Under-the-hood Magisk Manager forces your device to switch to the updated slot, bypassing any possible post-OTA verifications.
After the reboot, your device should be fully updated, and most importantly, Magisk is still installed to the updated system!
Click to expand...
Click to collapse

madhattr999 said:
I'm confused then. Isn't the method I described specifically for a phone with two boot partitions?
The instructions I am trying to reference:
Click to expand...
Click to collapse
It is, but it doesn't work on the pixel. Google's security, probably the M chip, but I may be wrong, prevents it from working. In theory, magisk should be able to patch a boot image on your device and you shouldn't need the magisk zip but that doesn't work either. You can certainly try what you're describing but backup at least your data partition with twrp and have it off your device before you try. Get the contents of your internal sdcard to if you have stuff there you don't want to lose.
Most likely restoring the stock boot image and trying to install the ota will just not work, but you never know.

jd1639 said:
It is, but it doesn't work on the pixel. Google's security, probably the M chip, but I may be wrong, prevents it from working. In theory, magisk should be able to patch a boot image on your device and you shouldn't need the magisk zip but that doesn't work either. You can certainly try what you're describing but backup at least your data partition with twrp and have it off your device before you try. Get the contents of your internal sdcard to if you have stuff there you don't want to lose.
Most likely restoring the stock boot image and trying to install the ota will just not work, but you never know.
Click to expand...
Click to collapse
Thanks, I'll back up my files and try that.

Well, as far as I know twrp backups only work for data (with verity and all that). Always bootloop on a vendor or system restore. Back up your data a million times and go for it. Worse thing that happens is back to zero. Wait, you said no computer? Well, put it on a free cloud saving service, have your data backed up out there. Not advertizing for any service in particular, but backing up data is something everyone should be thinking about.
I am about to go for broke on this device for the 4th time. Non boot several times, flashing, flashing, building, flashing. I have the added benefit of figuring out if cell service works as the vendor.img always breaks it. Good times mate.

I might be missing something here, so please clarify if there is a way to "Get March OTA without having to re-install Magisk/TWRP", and how. Wondering about exactly that. Thank you.

madhattr999 said:
I'm confused then. Isn't the method I described specifically for a phone with two boot partitions?
The instructions I am trying to reference:
Click to expand...
Click to collapse
What you have quoted works fine for me. I did both February and March update with this method on my P3 and no problems.
The only thing i noticed is that it takes more than 20 minutes to do step 2 of the instalation (optimizing apps)
But to be on the safe side, please backup.
Another thing: i don't have TWRP recovery, just Magisk root

fronten said:
I might be missing something here, so please clarify if there is a way to "Get March OTA without having to re-install Magisk/TWRP", and how. Wondering about exactly that. Thank you.
Click to expand...
Click to collapse
There is no way to do so. Either side loading the OTA, or fastbooting the factory image, will still require you to install root and twrp. Which, really isn't a big deal at all :good:

Badger50 said:
There is no way to do so. Either side loading the OTA, or fastbooting the factory image, will still require you to install root and twrp. Which, really isn't a big deal at all :good:
Click to expand...
Click to collapse
But the person above you said he was able to do it on both recent updates...

madhattr999 said:
But the person above you said he was able to do it on both recent updates...
Click to expand...
Click to collapse
He doesn't have twrp and if you do have twrp the ota won't work for sure. So you're welcome to try if you're only rooted, no twrp. But patching the boot image and installing it from magisk hasn't worked, but maybe it does now. Let us know.

dracushor87 said:
What you have quoted works fine for me. I did both February and March update with this method on my P3 and no problems.
The only thing i noticed is that it takes more than 20 minutes to do step 2 of the instalation (optimizing apps)
But to be on the safe side, please backup.
Another thing: i don't have TWRP recovery, just Magisk root
Click to expand...
Click to collapse
@dracushor87, can you confirm that the process described by @madhattr999 worked correctly? I have a Pixel 3, rooted with Magisk, without TWRP. I would like to apply the monthly updates as easily as possible: without wiping data, uninstall/reinstall Magisk, etc.
Specifically:
madhattr999 said:
1. From what I've read, I should be able to restore a stock boot image to the inactive boot partition (from within Magisk Manager) , then install the Update (both steps 1 and 2), then reinstall Magisk Manager to the inactive boot partition.. And then reboot, and I should have the update, and keep TWRP and Magisk, right? (just looking for confirmation of the process)
Click to expand...
Click to collapse
I looked through Magisk Manager, and don't see a way to "restore a stock boot image to the inactive boot partition".
In the installed state, I don't see any functions for patching or installing boot images within Magisk Manager.

timg11 said:
@dracushor87, can you confirm that the process described by @madhattr999 worked correctly? I have a Pixel 3, rooted with Magisk, without TWRP. I would like to apply the monthly updates as easily as possible: without wiping data, uninstall/reinstall Magisk, etc.
Specifically:
I looked through Magisk Manager, and don't see a way to "restore a stock boot image to the inactive boot partition".
In the installed state, I don't see any functions for patching or installing boot images within Magisk Manager.
Click to expand...
Click to collapse
Yes, i confirm. Before you start, please check if there is an update available. If there is, restore image, update, reinstall magisk and then reboot. If you reboot without reinstalling magisk, you will lose root. To install on the inactive slot, just click install in magisk manager and then you will be asked what method to use. If what i said is unclear, just requote me

dracushor87 said:
Yes, i confirm. Before you start, please check if there is an update available. If there is, restore image, update, reinstall magisk and then reboot. If you reboot without reinstalling magisk, you will lose root. To install on the inactive slot, just click install in magisk manager and then you will be asked what method to use. If what i said is unclear, just requote me
Click to expand...
Click to collapse
Used this method after the May update finally arrived for me yesterday. Backed up everything just in case, but it worked flawlessly.

October image is up

I've always wanted to post one of these
https://developers.google.com/android/images

How do we flash the update and not lose data and root? All the guides are still for 9.0 for updates

Androider4Life said:
How do we flash the update and not lose data and root? All the guides are still for 9.0 for updates
Click to expand...
Click to collapse
There's a link to a how-to for 10 in the stickied how-to for 9 - https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117.
But without twrp I don't think there's a way to retain root, I think you'll need to go the route of patching the boot image with Magisk. But for data just remove the -w switch from flash-all, that should be the same.

kerobrat said:
There's a link to a how-to for 10 in the stickied how-to for 9 - https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117.
But without twrp I don't think there's a way to retain root, I think you'll need to go the route of patching the boot image with Magisk. But for data just remove the -w switch from flash-all, that should be the same.
Click to expand...
Click to collapse
I was looking thru that post and didnt wanna risk wiping the device. I just had to wipe a few days ago due to Edxposed bootloop issue lol

Ha, yeah, I feel your pain there, wiping is way too much of a pain to do that frequently

Androider4Life said:
How do we flash the update and not lose data and root? All the guides are still for 9.0 for updates
Click to expand...
Click to collapse
You can also flash the OTA file in stock recovery and not lose data.

spotmark said:
You can also flash the OTA file in stock recovery and not lose data.
Click to expand...
Click to collapse
Will it retain root or do you mean - https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation

Androider4Life said:
Retain root or have to re-root
Click to expand...
Click to collapse
Have to re-root using the Magisk method. Put stock boot on phone, patch boot with Magisk, put modded boot back on computer, and flash in fastboot. AFAIK, there is no way to retain root. Every time you flash the latest monthly patch, it flashes a new stock boot. Therefore, no root.

kerobrat said:
There's a link to a how-to for 10 in the stickied how-to for 9 - https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117.
But without twrp I don't think there's a way to retain root, I think you'll need to go the route of patching the boot image with Magisk. But for data just remove the -w switch from flash-all, that should be the same.
Click to expand...
Click to collapse
There's a way with taking the ota through settings I found out how from a user on here which is:
Once received the ota , go to magisk first uninstall/restore images then download/install ota then DONT REBOOT, go back to magisk install magisk to inactive slot from the app then reboot and all should work with new ota update and have root still.

What is this update 4.3mb

Once again, my phone got bricked. I wanted to sideload, so I tried to get it into recovery, it wouldn't, so I tried a few times, and decided screw it. Now my phone bootloops. So, download the image and try flashing, it won't go into fastboot and fails. No matter what I do, I can't seem to save it. Can anyone help me with this? I'm trying a different computer in a sec, but, not sure if that will work either.
Edit: The different computer doesn't see it... FML

gettinwicked said:
Once again, my phone got bricked. I wanted to sideload, so I tried to get it into recovery, it wouldn't, so I tried a few times, and decided screw it. Now my phone bootloops. So, download the image and try flashing, it won't go into fastboot and fails. No matter what I do, I can't seem to save it. Can anyone help me with this? I'm trying a different computer in a sec, but, not sure if that will work either.
Edit: The different computer doesn't see it... FML
Click to expand...
Click to collapse
Just flash the factory image or ota thru flash.all bat file after you do/did the necessary steps like extract the images etc to platform tools folder on ur pc
Or visit here for more help/steps
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117

gm007 said:
What is this update 4.3mb
Click to expand...
Click to collapse
Its just a security patch, we already had the updated rom in september, this just adds the latest security patch. Even though its only 4.3mb, its taking ages to patch, 10 mins still installing.

Jiggs82 said:
Just flash the factory image or ota thru flash.all bat file after you do/did the necessary steps like extract the images etc to platform tools folder on ur pc
Or visit here for more help/steps
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117
Click to expand...
Click to collapse
You missed the part where I did try flashing the image. I've done this a hundred times, so, I did it right.
Anyway, I got it. I didn't realize my work computer had a USB-C port, so, I grabbed one and tried flashing the image with that. Worked! Thank God... I guess sdk tools doesn't like a USB 1 to C cable, and my phone doesn't like going into recovery...

Androider4Life said:
How do we flash the update and not lose data and root? All the guides are still for 9.0 for updates
Click to expand...
Click to collapse
kerobrat said:
There's a link to a how-to for 10 in the stickied how-to for 9 - https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117.
But without twrp I don't think there's a way to retain root, I think you'll need to go the route of patching the boot image with Magisk. But for data just remove the -w switch from flash-all, that should be the same.
Click to expand...
Click to collapse
If you are rooted flash the boot.img of the factory image you are currently on to both slots:
Code:
fastboot flash boot --slot all boot.img
Then Do #4 'keep Data'

Homeboy76 said:
If you are rooted flash the boot.img of the factory image you are currently on to both slots:
Code:
fastboot flash boot --slot all boot.img
Then Do #4 'keep Data'
Click to expand...
Click to collapse
I am starting to feel more and more like a lot of the bootloop issues are being caused by OTAs swapping slots on install. Besides the --slot all patched boot, it might help to run the OTA twice to get it to install to both slots completely. Preferably though, quit using OTAs and work with -w removed flash-all installer (and even then possibly installing to both slots with an active slot swap in between and before rooting). The double install is common when installing custom ROMs, and the process for OTA sideloads is pretty similar.

Performance improvement, feels smooth and responsive. Glad i dont need to root this phone, ppl are having so many problems.

boe323 said:
Its just a security patch, we already had the updated rom in september, this just adds the latest security patch. Even though its only 4.3mb, its taking ages to patch, 10 mins still installing.
Click to expand...
Click to collapse
My download was 1.3 gb and took forever to install. That's more than just the security patch.. Build number is different too.
Sent from my Pixel 3 XL using Tapatalk

Worked exactly the same as the 10 and .C3 builds for me. Flash-all (minus -w) and patched boot in Magisk. No issues. It was not just security this month. See the functional patches in the bulletin.
https://source.android.com/security/bulletin/pixel/2019-10-01

is there new platform tools too?

Question Fingerprint Reader Non-existent Broken Failure Not Working Since Android 13

Halp! 🫠
I have all the correct partitions, but my fingerprint reader hasn't worked since I successfully got to Android 13 with root. Literally everything else works with the phone. I've tried a lot, but haven't been successful so hoping someone could point me in the right direction.
OnePlus 9
LE2115
Global (US)

I guess none of my sensors work? Audio and camera are fine... 🫠

Try flashing the rom again. A lot of people including me having weird bugs like missing stock apps and status bar missing. In your case is finger print. I would try flashing the rom and try rooting again. You should be able to obtain boot.img and gain root from there. Or just install to inactive slot.

Nhatlienhoan said:
Try flashing the rom again. A lot of people including me having weird bugs like missing stock apps and status bar missing. In your case is finger print. I would try flashing the rom and try rooting again. You should be able to obtain boot.img and gain root from there. Or just install to inactive slot.
Click to expand...
Click to collapse
My phone just got this OTA, but it's not showing up on oxygen updater?
LE2115_11.F.17_ 2170_202211231112
See attachments. In order to complete your suggestion, what are my steps but to upgrade to the newest version (listed above)?
-Remove password unlock on phone
-Back up everything 15 times
Remove/uninstall magisk modules
-Download latest Ota (listed above) either via oxygen updater or somehow through normal Ota process but *not* rebooting after completing
-Uninstall magisk
-Install Ota (listed above) and *don't* reboot
-Open magisk and install to inactive slot and reboot
-Check Magisk and root status
-Re-add magisk modules and password unlock, etc.
-Reboot, back everything up again as fresh upgrade- bobs your uncle, no chance, that's never how it actually goes down
Do I have that process more or less correct? At any point in that process should I backup partitions or extract fastboot anything? I'd like to complete your suggestion but now since there's an Ota I'd like to kill 2 birds 1 stone (if possible ).

fhedeitx said:
My phone just got this OTA, but it's not showing up on oxygen updater?
LE2115_11.F.17_ 2170_202211231112
See attachments. In order to complete your suggestion, what are my steps but to upgrade to the newest version (listed above)?
-Remove password unlock on phone
-Back up everything 15 times
Remove/uninstall magisk modules
-Download latest Ota (listed above) either via oxygen updater or somehow through normal Ota process but *not* rebooting after completing
-Uninstall magisk
-Install Ota (listed above) and *don't* reboot
-Open magisk and install to inactive slot and reboot
-Check Magisk and root status
-Re-add magisk modules and password unlock, etc.
-Reboot, back everything up again as fresh upgrade- bobs your uncle, no chance, that's never how it actually goes down
Do I have that process more or less correct? At any point in that process should I backup partitions or extract fastboot anything? I'd like to complete your suggestion but now since there's an Ota I'd like to kill 2 birds 1 stone (if possible ).
Click to expand...
Click to collapse
Usually, with previous ota updates do you have problem updating and regaining root like uninstall magisk/restore image: error in this step or error in the download of the ota? Because for some reason, this usually the case for me, and even with my completely uninstall magisk still error to download ota. But after msm (because I did some stupid thing) then I don't even need to restore image ib magisk to download ota.
As long as you be able to download ota, then install to inactive slot then reboot and you're good.
But incremental update usually has problem to retain magisk. I still suggest reflash the F16 to see if the finger print issue resolved. You always can flash the new incremental later any way.

Nhatlienhoan said:
Usually, with previous ota updates do you have problem updating and regaining root like uninstall magisk/restore image: error in this step or error in the download of the ota? Because for some reason, this usually the case for me, and even with my completely uninstall magisk still error to download ota. But after msm (because I did some stupid thing) then I don't even need to restore image ib magisk to download ota.
As long as you be able to download ota, then install to inactive slot then reboot and you're good.
But incremental update usually has problem to retain magisk. I still suggest reflash the F16 to see if the finger print issue resolved. You always can flash the new incremental later any way.
Click to expand...
Click to collapse
No matter what I do or how many times I read the directions, something still always goes wrong lol. How might one download a fresh LE2115_11_F.16 image? I used Oxygen Updater to get the file but I want to "re-download" the image- I can't with Oxygen Updater since I'm on LE2115_11_F.16 currently.
edit- this file?
Can you please spell it out for me using my sudo steps above? Download F.16 from above and put it in platform tools > adb fastboot reboot > fastboot set_active=? > fastboot boot F.16bootpatched.img > fastboot flash boot F.16boot.img > reboot > install magisk, etc.

fhedeitx said:
No matter what I do or how many times I read the directions, something still always goes wrong lol. How might one download a fresh LE2115_11_F.16 image? I used Oxygen Updater to get the file but I want to "re-download" the image- I can't with Oxygen Updater since I'm on LE2115_11_F.16 currently.
edit- this file?
Can you please spell it out for me using my sudo steps above? Download F.16 from above and put it in platform tools > adb fastboot reboot > fastboot set_active=? > fastboot boot F.16bootpatched.img > fastboot flash boot F.16boot.img > reboot > install magisk, etc.
Click to expand...
Click to collapse
I'm uploading the full ota f16. But the steps are:
Download full ota file (>4GB)
Install via local updater for android 12 apk
Don't reboot
Magisk/install to inactive slot
Reboot
I found that flashing only boot.img didn't change anything, so the whole package of ota was needed in my case. Will edit and update the full OTA file here after the uploading done.

Nhatlienhoan said:
I'm uploading the full ota f16. But the steps are:
Download full ota file (>4GB)
Install via local updater for android 12 apk
Don't reboot
Magisk/install to inactive slot
Reboot
I found that flashing only boot.img didn't change anything, so the whole package of ota was needed in my case. Will edit and update the full OTA file here after the uploading done.
Click to expand...
Click to collapse
Thanks! Followed your steps. Got back to... Right where I was haha. None of my sensors work nor does fingerprint

fhedeitx said:
Thanks! Followed your steps. Got back to... Right where I was haha. None of my sensors work nor does fingerprint
Click to expand...
Click to collapse
Lol. It was fine on android 12? Weird, really. Maybe try doing the same steps again. If not, I don't have anything else to add. Hopefully someone else knows more could help.

Question Migisk boot.img or magisk.zip

Hello all
I've used the boot.img and found it to be inconvenient as id have to redo this with every ota update, instead I use adb magisk.zip and keep root after ota updates, is this incorrect as I've not seen the method I am currently using spoken about at all and everyone directs to use .IMG or at least all the root guides I've come across

mlolz93 said:
Hello all
I've used the boot.img and found it to be inconvenient as id have to redo this with every ota update, instead I use adb magisk.zip and keep root after ota updates, is this incorrect as I've not seen the method I am currently using spoken about at all and everyone directs to use .IMG or at least all the root guides I've come across
Click to expand...
Click to collapse
What do you mean by "adb magisk.zip"?

V0latyle said:
What do you mean by "adb magisk.zip"?
Click to expand...
Click to collapse
Apologies, in recovery mode send the zip to install

mlolz93 said:
Apologies, in recovery mode send the zip to install
Click to expand...
Click to collapse
With the stock recovery? As far as I know this shouldn't work because the stock recovery will only accept official signed images.

V0latyle said:
With the stock recovery? As far as I know this shouldn't work because the stock recovery will only accept official signed images.
Click to expand...
Click to collapse
Sorry no with lineage recovery
Definitly have root, can use several tools that show as much. So I just find it odd that with all tutorials that I have come across, the ones for custom ROMs will say to use boot.img and that doesn't make a lot of sense considering that it'll loose root after an update.
Anyway I'm left wondering why people default to boot.img which takes more steps and is overall more inconvenient.. Or is there a trade off that I am missing

mlolz93 said:
Sorry no with lineage recovery
Definitly have root, can use several tools that show as much. So I just find it odd that with all tutorials that I have come across, the ones for custom ROMs will say to use boot.img and that doesn't make a lot of sense considering that it'll loose root after an update.
Anyway I'm left wondering why people default to boot.img which takes more steps and is overall more inconvenient.. Or is there a trade off that I am missing
Click to expand...
Click to collapse
Because that's how to root the Pixels - you have to patch the boot image. There are a number of ways to do this: you can manually patch it in Magisk; you can live boot a previously patched image and use temporary root to perform Direct Install in Magisk; you can live boot a custom recovery (if on the stock ROM) and install Magisk that way; or you can sideload Magisk in custom recovery.
The reason why updating breaks root is because the boot image gets overwritten with a "clean" unpatched image. This will happen regardless of the method you use to root, so you'll have to re-root every time you update.

V0latyle said:
Because that's how to root the Pixels - you have to patch the boot image. There are a number of ways to do this: you can manually patch it in Magisk; you can live boot a previously patched image and use temporary root to perform Direct Install in Magisk; you can live boot a custom recovery (if on the stock ROM) and install Magisk that way; or you can sideload Magisk in custom recovery.
The reason why updating breaks root is because the boot image gets overwritten with a "clean" unpatched image. This will happen regardless of the method you use to root, so you'll have to re-root every time you update.
Click to expand...
Click to collapse
Side loading the .zip is way easier and I've not lost root after updating so to me seems like the better method.
because I've not seen it used in guides I was concerned that they're was a trade off.
I will assume side loading the .zip is the better method.
Cheers @V0latyle

Same here, I used adb when rooting only with custom recovery, lineage update with no problem, flash it to inactive slot before rebooting to finished update, make sure you disable the magisk modules that you have to prevent bootlooping

mlolz93 said:
Side loading the .zip is way easier and I've not lost root after updating so to me seems like the better method.
because I've not seen it used in guides I was concerned that they're was a trade off.
I will assume side loading the .zip is the better method.
Cheers @V0latyle
Click to expand...
Click to collapse
For LOS, yeah it would be easier.
You actually do lose root after updating, but when you sideload Magisk, you're patching the new boot image

V0latyle said:
For LOS, yeah it would be easier.
You actually do lose root after updating, but when you sideload Magisk, you're patching the new boot image
Click to expand...
Click to collapse
Nope, mine is still rooted when I updated on 04/08.

imna357 said:
Nope, mine is still rooted when I updated on 04/08.
Click to expand...
Click to collapse
I disabled all my modules, start the updater and after ready to install I went to Magisk and install it to inactive slot, then reboot.

imna357 said:
Nope, mine is still rooted when I updated on 04/08.
Click to expand...
Click to collapse
I'd retained root for 2 update but with the last one I had to reinstall to inactive slot