yashsingh1/xdaforums huggingface dataset:
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Magisk Stable is now at version 24.1, so I will no longer be providing any Magisk updates.

You can use any version of Magisk now - Stable, Beta, or Canary. as long as it is 23016 or newer.

Once again, if you want to switch versions of Maagisk, it is HIGHLY RECOMMENDED that you "Complete Uninstall" within Magisk before installing the new version. Multiple instances of Magisk can break root.

If you simply want to update Magisk, the best way to do so is from within the app.

Once the February update is out, I will perform some testing with installing to inactive slot, and if it works, I will update this guide.

Given the low activity on this thread, I will probably close it if everything goes well with the next update.

Thank you all for your testing and contributions.
[Google Pixel 5 Guides, News, & Discussion] a4abbas:
@V0latyle

I am currently rooted with your

Update and Root OTA Sideload

method. I forgot to use phone transfer tool before setting up the phone. AFAIK now to do that I need to factory reset my phone. What steps do I have to follow to get rooted again? . Please advice.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
That sucks, I was trying to find a way for you to transfer data without having to factory reset. I believe you might be able to do that using Swift Backup as long as you have root on both devices.

If you are currently rooted and perform a factory reset, it only wipes /data. It doesn't restore the factory boot image, so your existing boot image will still be patched; the only thing you should have to do to regain root is install Magisk. It shouldn't matter what version of Magisk you install, either, because a data wipe removes all the signatures and other "links" between the Magisk app and the boot image patch.
[Google Pixel 5 Guides, News, & Discussion] a4abbas:
Someone suggested me to try this method below. Is it safe to do so considering that I am rooted:

Run this adb command from your computer:
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Seems legit. Give it a try and let us know!
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Anyone else having trouble downloading the OTA? My phone keeps insisting that it's up to date.
[Google Pixel 5 Guides, News, & Discussion] Zanzibar:
My Pixel 5 also says it's up to date. However, a friend of mine with a Pixel 5 was able to download it after doing a manual check for updates. Mine doesn't have an update available yet.
[Google Pixel 5 Guides, News, & Discussion] proac:
First restore the original factory image, can you receive the ota update? It used to be so.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Yes, that is correct. It worked on my wife's 5a, but for some reason my 5 didn't think an OTA was available.
[Google Pixel 5 Guides, News, & Discussion] a4abbas:
Didn’t work

View attachment 5531847
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Sorry to hear that. The only other option I can think of is a factory reset.

If you're rooted you can use Swift Backup to minimize the pain of having to set everything up again.
[Google Pixel 5 Guides, News, & Discussion] thatsupnow:
Anybody have an issue where Google Play services doesn't stay in the deny list after a reboot?? A12 24.1
[Google Pixel 5 Guides, News, & Discussion] elong7681:
Yes it's not supposed to and if you are using the universal safety net fix you are covered
[Google Pixel 5 Guides, News, & Discussion] thatsupnow:
Okay cool cool. Yea I'm using the USNF so I guess I'm good to go
[Google Pixel 5 Guides, News, & Discussion] jnss98b:
I'm just writing this to share my experience. Since Android 12 came out, I have been using the OTA sideload method + booting patched boot image to update and keep root since I did not like the idea of having to wipe my Pixel 5 at all. I have been doing so pretty much for every monthly patch since it has been working well and I don't really need to restart my phone often or even at all and I didn't even know that a new magisk update has fixed the vbmeta issue until today. So I tried to use the same method today to update my Pixel 5 to the February patch but it did not work this time. Instead, after I sideloaded the OTA and booted the patched boot image, the phone boots once, unable to finish booting and just reboots into the system without root. I then tried to reboot to the bootloader and boot the patched image again and it worked. HOWEVER, when I checked in settings afterward, I'm still on the previous patch (January update in my case) somehow??? Just thought that would be an interesting experience to share. Oh and I forgot to mention, I actually tried to root this update with both Magisk 23 and 24, and both rooted successfully but without incrementing to the February patch. I will be trying to update and root the old way with Magisk 24.1 since the vbmeta issue is fixed now and will report back soon how it went.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Dirty flashing the factory image doesn't wipe your device, FYI.

When you update via OTA, you MUST use an updated boot image as well. When the device reboots following OTA update, it expects to see a kernel version matching updated system. If you interrupt the boot process and boot an older boot image, the system assumes the update failed, and reboots into the original slot.

Due to this, the recommended ways to update are either delta OTA + install Magisk to inactive slot, or download factory image + patch the new boot image.
[Google Pixel 5 Guides, News, & Discussion] jnss98b:
I'm actually quite a paranoid person so I patch the boot image every single update. I have been dirty flashing the boot image before android 12 and I just sideloaded the ota because of the vbmeta issue/not knowing it got fixed recently. Will be trying the good old way soon when I have time. Still weird how this update just failed on me though
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Yeah, it seems the OTA has been giving people problems. Not sure why.
[Google Pixel 5 Guides, News, & Discussion] jnss98b:
Ok so I just finished updating to the February patch using the factory image + patched boot image and rooting, and I'm happy to report back that it works now. Kinda weird how using the OTA sideloading method gave me issues still tho. Oh and you should add the method where you just remove the -w in the flash-all file (optionally add --skip-reboot) and then run it to the main post as it's simpler and doesn't require you to check for bootloader and baseband versions since the files does that for you automatically. Also, you can run fastboot flash boot [patched_boot.img here] instead of doing direct install in the magisk app too I believe. That would save you from rebooting twice
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
I personally don't like using scripts, but yes this is one way of doing it.

Yes, if you have patched the new boot image. It's kind of a tradeoff - either you have to extract and patch the new boot image, then flash it after updating.... or you have to boot an older patched image for root, direct patch the new image, and reboot.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
So I see that the OTA and factory images are out for March, but for some reason my device doesn't think an update is available. Has anyone else managed to update via automatic OTA?
[Google Pixel 5 Guides, News, & Discussion] redsmith:
It's been my experience that as soon as I unlock the bootloader and root, I never get the automatic OTA (not even for weeks). Sadly I'm forced to update via factory image.

Quick question, can I update via OTA sideload if rooted?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Yep.

My wife's P5a tries to download the update but fails. Unlocked and rooted.
[Google Pixel 5 Guides, News, & Discussion] jnss98b:
That never works for me, even with the stock boot image restored through magisk. The only time it shows is when we jump to a new Android version (i.e. 11 to 12)
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Weird. Her device wouldn't install the OTA, kept failing. Had no trouble updating via the factory image.
[Google Pixel 5 Guides, News, & Discussion] Krsmqn:
I also am unlocked and rooted, and never receive OTA's. My process has been:

~Download latest OTA & Factory

~Extract boot.img from latest Factory

~Upload boot.img to phone & root it via magisk, return it to PC

~Sideload OTA, and let the phone update to completion

~Boot rooted boot.img and install magisk....

...and then I'm updated w/root.

I wish OTA was an option. T'would be so much easier, and less time consuming and less data.
[Google Pixel 5 Guides, News, & Discussion] Krsmqn:
Spoke too soon. With this latest OTA/Factory version, I'm getting this error when trying to boot patched image:

Sending 'boot.img' (98304 KB) OKAY [ 2.395s]
Booting (bootloader) boot.img missing cmdline or OS version
OKAY [ 1.405s]
Finished. Total time: 3.866s

... which when it reboots, it kicks me to recovery where the only options are to "try again" or "factory data reset"... I select "try again", of course, which boots the unrooted boot image.

thoughts?

**edit**

Worried it might be a magisk issue. I just updated to the most recent version (canary) right before the sideload update. I cannot get the patched boot.img to boot. I'm afraid to flash it if it's corrupted. Not sure if the right step is to try again with older version of magisk (which I cannot find), or to try and root via booting an older patched image. Or, flashing an older image. I don't know enough to determine which methods would work.
[Google Pixel 5 Guides, News, & Discussion] elong7681:
It seems Google changed something in the March update and if I'm not mistaken you have to factory reset to update to A12 L / 12.1 if you are rooted. I had the same problem.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
I updated to March (not the beta) without a problem using Canary 24201.
[Windows Mobile Development and Hacking General] Aegishua:
Is it possible to create a WM6 program which resembles the windows client and will allow for remote administration?

I've already asked the company which produces the application and they will not be producing a client for Windows Mobile. The reason for me requesting this app is because i often use my netlimiter client on my PC to occasionally restrict my brother's usage(god, he downloads so much random stuff at the worst times! >_<) and it would be more convenient to do it via my pda.

Btw, if you dont know what Netlimiter is, it is a windows program designed to limit connection speeds on specific applications or processes. It allows for remote administration which basically lets you manipulate or monitor other computers connections and apply restrictions where necessary. (See Link!! its a good app XD)

http://www.netlimiter.com/
[Google Pixel 5a] V0latyle:
Official updates for this device will end August 2024.

If you are looking for my guide on a different Pixel, find it here:

Pixel 3

Pixel 3XL

Pixel 3a

Pixel 3aXL

Pixel 4

Pixel 4XL

Pixel 4a

Pixel 4a (5G)

Pixel 5

Pixel 6

Pixel 6 Pro

For best results, use the latest stable Magisk release.

Discussion thread for migration to 24.0+.

Note: Magisk prior to Canary 23016 does not incorporate the necessary fixes for Android 12+.

WARNING: YOU AND YOU ALONE ARE RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE. THIS GUIDE IS WRITTEN WITH THE EXPRESS ASSUMPTION THAT YOU ARE FAMILIAR WITH ADB, MAGISK, ANDROID, AND ROOT. IT IS YOUR RESPONSIBILITY TO ENSURE YOU KNOW WHAT YOU ARE DOING.

Prerequisites:

Latest SDK Platform Tools - if Platform Tools is out of date, you WILL run into problems!

USB Debugging enabled

Google USB Driver installed

I recommend using Command Prompt for these instructions; some users have difficulty with PowerShell.

Make sure the Command Prompt is running from your Platform Tools directory!

Android Source - Setting up a device for development

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

Points of note:

The boot image is NOT the bootloader image. Do not confuse the two - YOU are expected to know the difference. Flashing the wrong image to bootloader could brick your device.

While the Magisk app is used for patching the boot image, the app and the patch are separate. This is what you should see in Magisk for functioning root:

"Installed" shows the version of patch in the boot image. If this says N/A, you do not have root access - the boot image is not patched, or you have a problem with Magisk.

"App" simply shows the version of the app itself.

If you do not have a patched master boot image, you will need to download the factory zip if you haven't already, extract the system update inside it, then patch boot.img.

If you prefer updating with the factory image, you can also extract and manually patch the boot image if desired.

Some Magisk modules, especially those that modify read only partitions like /system, may cause a boot loop after updating. As a general rule, disable these modules before updating. You are responsible for knowing what you have installed, and what modules to disable.

Credits:

Thanks to @badabing2003 , @pndwal , @Displax , @Az Biker , @ipdev , @kdrag0n , @Didgeridoohan , and last but not least, @topjohnwu for all their hard work!
[Google Pixel 5a] Rafiul Bari Chowdhury:
Thank you so so much! I've successfully updated from October 2021 build to November 2021 build without any issues by following your guide. Bunch of thanks again.
[Google Pixel 5a] Rafiul Bari Chowdhury:
I'm currently using Magisk Canary build?

May I Install Magisk Beta and also Magisk Stable build to the latest November 2021 build?
[Google Pixel 5a] mcwups1:
Coming from the Pixel 3XL, which bricked out of the blue. I did every update on that phone, but never got to do 12 before the magical brick. I want to update this phone (5a, which I just realized is different than the 5?), but this seems to be missing quite a few steps. Shouldn't there be 4 different files added to your SDK folder and flashed, or has it completely changed, and I need to do more digging? Thanks.
[Google Pixel 5a] EXV:
Is there any way to do this after already updating? Or do I have to wait for the next update (I prefer flashing factory images).

I flashed the Nov factory image but forgot to disable the verified boot. Is there any way I can disable it so i can flash the magisk patched boot?
[Google Pixel 5a] V0latyle:
I honestly don't know. I've used Magisk 22.1, 23.0, Canary 23001 through 23011, all have worked for me.

The caveat is that Magisk 23010+ is Zygisk, which means that some legacy modules won't work anymore until they're updated - Universal SafetyNet Fix for example.

You don't have to add any files to your SDK folder, you can always drag and drop them into the command line window. We are only working with two files here: vbmeta.img and boot.img.

You can do this as many times as you want. The critical point to remember is that if you allow Android to boot after not disabling verity/verification, you will have to wipe the next time you disable it.

Yes...but you're going to have to wipe data. Extract vbmeta.img, and reflash it:

fastboot flash vbmeta --disable-verity --disable-verification <drag and drop vbmeta.img here>

Then, reboot your device. You will end up in Rescue Party, with the option to "Try again" or "Factory data reset". Choose the factory reset.

The best way to make sure you don't have to wipe your data is to always use --disable-verity --disable-verification when updating via the factory image.
[Google Pixel 5a] nijel8:
Updated to November build with no problems, didn't like the new security patch - file managers targeting API 26 and below can no longer display/access other's apps data directories, hole is plugged, so went back to October build and had to wipe data to boot. So downgrading within same Android version also requires data wipe.

No more updates for me, sticking with October build...
[Google Pixel 5a] tintn00+xda:
I was on latest version of Android 11, rooted. I followed your third method using Android Flash Tool, and had both disable verity and verification checked. The Android flash tool says I may disconnect the phone. The phone is now stuck during boot, saying cannot load android system, data may be corrupt, may need to perform factory data reset and erase all user data, or try again. Trying again causes the boot loop. Any suggestions? Prefer not to perform factory data reset.
[Google Pixel 5a] tintn00+xda:
I got my phone back into bootloader and followed your second method via fastboot. I also arrived at the same error.
[Google Pixel 5a] tintn00+xda:
I tried the same thing on my wife's pixel 5a as well. Same errors.

I selected factory data reset and my phone boots up fine. Guess I had to reset my phone anyway, despite this guide. Hoping I don't have to reset my wife's phone. It's currently stuck at boot, but I can get into fastboot.
[Google Pixel 5a] Rafiul Bari Chowdhury:
This guide is for only Android 12. And you can't get your now at any cost.
[Google Pixel 5a] tintn00+xda:
That's a bummer. Guess there should be a disclaimer about going from Android 11 to 12. Good thing everything is backed up.
[Google Pixel 5a] V0latyle:
This guide was intended for updating, not for root.

If it wasn't clear in the guide, you will have to wipe data when you disable verity and verification, if they were not already disabled.

It's at the very top of the post...

This is why it's important to read the entire post, and ask questions if you don't understand something before you proceed.
[Google Pixel 5a] ssdd28561:
Thanks a lot! This is my first device with verified boot / encryption linked - after crosshatch, and I have almost messed things up (just manually typed commands from memory), until I remembered this post.

Updated, everything is great.

December patch has brought bootanimation with different colours (Material You blahblah), made me freak out a little bit - I thought something went wrong.
[Google Pixel 5a] EXV:
I was always used to updating factory images (removing the -w) via ADB so none of my data would be wiped. But since the methods listed above don't include removing the -w from the zip, will any of those methods wipe my data while applying the update? I wanted to try the Android Flash Tool but got a bit paranoid since I didn't want my data wiped (I know there was a checkbox option to wipe the data, but I just want reassurance since with my luck, it'll probably brick my phone for no reason).
[Google Pixel 5a] V0latyle:
Are you already rooted?

I personally don't use the flashall.bat method; I'm "old fashioned" and prefer to type the commands myself.

If you do use the script, just edit the "fastboot update" command to omit -w and include --disable options:

fastboot update image-barbet-buildnumber.zip --disable-verity --disable-verification

If you patch the boot image beforehand, you can add --skip-reboot, then once the update finishes, reboot to bootloader and flash the patched image.
[Google Pixel 5a] imagesdecieve:
Followed directions for recommended Android Flash Tool and everything worked flawlessly. If you've already rooted your phone once then you have somewhat of an idea of what you're doing. Just read everything twice and follow the directions. Thank you OP for such a clear path to update and root!
[Google Pixel 5a] V0latyle:
Magisk Canary was updated to 23016 last night. This includes a fix for the vbmeta header issue, meaning that disabling verity/verification should no longer be required, and we should be able to root as we did before.

I will be updating the OP to reflect this.
[Google Pixel 5a] schalacker:
Just updated my wifes 5a-5G (non-root, verity/vbmeta enabled) to Dec update. Was able to root via flashing the patched boot.img with v23016 without a factory reset! Great news that John is still working on this tool and making all of our lives easier.
[Google Pixel 5a] V0latyle:
Someone want to test this?

Requirement: Pixel 4a, 5, 5a, 6, 6 Pro rooted with Magisk 23016

Reboot into bootloader and reflash vbmeta without flags.

Reboot to system.

Reboot to bootloader again, re-reflash vbmeta with disable flags.

Reboot to system. If you get the Rescue Party corruption message, just reboot to bootloader and reflash vbmeta without flags.

Report results here.
[Google Pixel 5a] V0latyle:
Out of band patching seems broken again.
[Google Pixel 5a] V0latyle:
Announcement:

It appears that the July update has broken out of band update patching on the 765G devices (4a 5g, 5, and 5a).

For the time being, you can either use an alternate update method (factory image, sideload OTA, etc), or you can update and re-root following these instructions (you will temporarily lose root!):

Restore images in Magisk

Download and install the update

When prompted to reboot, do not attempt to patch alternate slot in Magisk; instead, just follow prompt to reboot normally

After system reboots, verify you're on the updated firmware (bottom of notification panel or Settings > About > Build Number)

Allow update to finish (there should be a notification and progress bar in the notification panel)

Reboot to bootloader

Live boot a previously patched Magisk image:

fastboot boot <patched image>

When system boots, open Magisk and perform Direct Install.
[Google Pixel 5a] userwaldo:
Testing out the flow for July ... the OTAs are so slow to install. I think that the full images install faster over USB.
[Google Pixel 5a] userwaldo:
This is basically what I had done last release (June) and I did it again (July) and root is working again.

Thanks for always testing and verifying the flow.
[Google Pixel 5a] C00ljoe:
Can you add an updating magisk app/patch section? Can i overwrite an older patch (25.1) with 25.2 or do i pull a new fresh boot.img and patch that and flash to update the patch? Also an installing ROM section, some guides use TWRP flashed perm, some temp twrp to sideload and some just say to use the ROMS custom recovery. Gladly donate if you can, my brain fog and ADHD making comprehending things impossible at times. Thanks.
[Google Pixel 5a] V0latyle:
Update Magisk from within the Magisk app. Depending on the update channel, Magisk will prompt you to update the app. Once you do, you can update the patch; Magisk performs on the fly.

This is strictly for the stock firmware. I do not develop nor do I provide any support for any custom firmware.

TWRP on the Pixel series is pretty pointless in my opinion, at least as far as the stock firmware is concerned. Pixels do not have a recovery partition; recovery lives in the boot image, and in my experience TWRP cannot coexist with Magisk; this results in a boot loop, so installing TWRP is out of the question. All partitions can be flashed from fastboot as it is.

While TWRP can sideload the OTA package, this ability is already present in stock recovery, so why would you want to boot a TWRP image when you can simply command a reboot to recovery? I don't know if TWRP can install the factory image; if it can, then conversely one could use fastboot update to install custom firmware.

I can relate to the brain fog. I don't have any way to accept donations, and with the exorbitant taxes I already pay on our house, our cars, and our income, I don't want to deal with any complications.
[Google Pixel 5a] userwaldo:
I keep getting bugged to migrate to Android 13. Looking around it seems there are still some bugs to be worked out.

Wondering if anyone has tried root with Magisk yet.