How To Guide [GUIDE] Pixel 5a "barbet": Unlock Bootloader, Update, Root, Pass SafetyNet

[V0latyle]

The last couple of monthly updates I tried to remove Magisk, take the OTA, then re-install and it didn't work. The OTA stops after download but before install; to proceed click "Reboot" and then it installs and reboots in one go - no chance to patch. If instead I went to Magisk and patched the boot image then rebooted from Magisk with its install then the OTA didn't install. Returning to the OTA installer to reboot loses Magisk. Perhaps I did something wrong but as it is I don't see how to take the OTA and patch in one go. This isn't a problem because it is really easy to 1) uninstall Magisk, 2) take the OTA with reboot, 3) shut down and reboot into bootloader (could do 2+3 with fastboot), 4) boot into a patched image from a computer with USB, and 5) use Magisk to re-install (Magisk picks up on the situation and offers to patch). It is almost like a fresh install but I don't see anything easier. The July OTA was a bit over 15MB so much less downloading than the factory image.

Out of band patching seems broken again.

 

[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!):

1. Restore images in Magisk
2. Download and install the update
3. When prompted to reboot, do not attempt to patch alternate slot in Magisk; instead, just follow prompt to reboot normally
4. After system reboots, verify you're on the updated firmware (bottom of notification panel or Settings > About > Build Number)
5. Allow update to finish (there should be a notification and progress bar in the notification panel)
6. Reboot to bootloader
7. Live boot a previously patched Magisk image:

   fastboot boot <patched image>

8. When system boots, open Magisk and perform Direct Install.

 

[userwaldo]

Testing out the flow for July ... the OTAs are so slow to install. I think that the full images install faster over USB.

 

[userwaldo]

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!):

1. Restore images in Magisk
2. Download and install the update
3. When prompted to reboot, do not attempt to patch alternate slot in Magisk; instead, just follow prompt to reboot normally
4. After system reboots, verify you're on the updated firmware (bottom of notification panel or Settings > About > Build Number)
5. Allow update to finish (there should be a notification and progress bar in the notification panel)
6. Reboot to bootloader
7. Live boot a previously patched Magisk image:

   fastboot boot <patched image>

8. When system boots, open Magisk and perform Direct Install.

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.

 

[C00ljoe]

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

Update 6-20-22: Magisk 25.1 is recommended as this includes fixes for OTA updates.
Discussion thread for migration to 24.0+.

DO NOT use any version of Magisk lower than Canary 23016 as it does not yet incorporate the necessary fixes for Android 12 and your device.

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: Downloads

Pixel OTA Images
Pixel Factory Images
Magisk Stable, Magisk Canary - Magisk GitHub

Spoiler: Unlock Bootloader

1. Follow these instructions to enable Developer Options and USB Debugging.
2. Enable OEM Unlocking. If this option is grayed out, unlocking the bootloader is not possible.
3. Connect your device to your PC, and open a command window in your Platform Tools folder.
4. Ensure ADB sees your device:

   adb devices

   If you don't see a device, make sure USB Debugging is enabled, reconnect the USB cable, or try a different USB cable.
   If you see "unauthorized", you need to authorize the connection on your device.
   If you see the device without "unauthorized", you're good to go.
5. Reboot to bootloader:

   adb reboot bootloader

6. Unlock bootloader: THIS WILL WIPE YOUR DEVICE!

   fastboot flashing unlock

   Select Continue on the device screen.

Spoiler: Initial Root / Create Master Root Image

1. Install Magisk on your device.
2. Download the factory zip for your build.
3. Inside the factory zip is the update zip: "device-image-buildnumber.zip". Open this, and extract boot.img
4. Copy boot.img to your device.
5. Patch boot.img with Magisk: "Install" > "Select and Patch a File"
6. Copy the patched image back to your PC. It will be named "magisk_patched-23xxx_xxxxx.img". Rename this to "master root.img" and retain it for future updates.
7. Reboot your device to bootloader.
8. Flash the patched image:

   fastboot flash boot <drag and drop master root.img here>

9. Reboot to Android. Open Magisk to confirm root - under Magisk at the top, you should see "Installed: <Magisk build number>

Spoiler: Update and Root Automatic OTA

1. Before you download the OTA, open Magisk, tap Uninstall, then Restore Images. If you have any Magisk modules that modify system, uninstall them now.
2. Take the OTA update when prompted. To check for updates manually, go to Settings > System > System Update > Check for Update
3. Allow the update to download and install. DO NOT REBOOT WHEN PROMPTED. Open Magisk, tap Install at the top, then Install to inactive slot. Magisk will then reboot your device.
4. You should now be updated with root.

Spoiler: Update and Root OTA Sideload

1. Download the OTA.
2. Reboot to recovery and sideload the OTA:

   adb reboot sideload

   Once in recovery:
   

   adb sideload ota.zip

3. When the OTA completes, you will be in recovery mode. Select "Reboot to system now".
4. Allow system to boot and wait for the update to complete. You must let the system do this before proceeding.
5. Reboot to bootloader.
6. Boot the master root image (See note 1):

   fastboot boot <drag and drop master root.img here>

   Note: If you prefer, you can download the factory zip and manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
7. Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
8. Reboot your device. You should now be updated with root.

Note: You can use Payload Dumper to extract the contents of the OTA if you want to manually patch the new boot image. However, I will not cover that in this guide.

Spoiler: Update and Root Factory Image

Please note that the factory update process expects an updated bootloader and radio. If these are not up to date, the update will fail.

1. Download the factory zip and extract the contents.
2. Reboot to bootloader.
3. Spoiler: Update bootloader if necessary

   Compare bootloader versions between phone screen and bootloader.img build number

   fastboot flash bootloader <drag and drop new bootloader.img here>

   If bootloader is updated, reboot to bootloader.
4. Spoiler: Update radio if necessary

   Compare baseband versions between phone screen and radio.img build number

   fastboot flash radio <drag and drop radio.img here>

   If radio is updated, reboot to bootloader.
5. Apply update:
   

   fastboot update --skip-reboot image-codename-buildnumber.zip

   When the update completes, the device will be in fastbootd. Reboot to bootloader.
6. Boot the master root image (See note 1):

   fastboot boot <drag and drop master root.img here>

   Note: If you prefer, you can manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
7. Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
8. Reboot your device. You should now be updated with root.

Note: If you prefer, you can update using the flash-all script included in the factory zip. You will have to copy the script, bootloader image, radio image, and update zip into the Platform Tools folder; you will then have to edit the script to remove the -w option so it doesn't wipe your device.
The scripted commands should look like this:

fastboot flash bootloader <bootloader image name>
fastboot reboot bootloader
ping -n 5 127.0.0.1 > nul
fastboot flash radio <radio image name>
fastboot reboot bootloader
ping -n 5 127.0.0.1 > nul
fastboot update  --skip-reboot --slot=all <image-device-buildnumber.zip>

Once this completes, you can reboot to bootloader and either boot your master patched image, or if you patched the new image, flash it at this time.

Spoiler: Update and Root using PixelFlasher

PixelFlasher by @badabing2003 is an excellent tool that streamlines the update process - it even patches the boot image for you. Please note that root access is required to patch.

1. Download PixelFlasher and the factory image. You do not need to extract the factory image.
2. Open PixelFlasher. Point the Android Platform Tools directory (browse for your Platform Tools folder)
3. Point the Factory Image directory to the factory image package you just downloaded.
4. Connect your device via USB. Ensure it shows up under ADB Connected Devices.
5. Click the button to the right of the factory image Browse button (looks like a meat grinder). This will extract the boot image from the factory package.
6. When the boot image appears in the list, click on it and click Patch. A root request should pop up on your device; this is PixelFlasher requesting shell root access through ADB. Make sure you approve it.
7. PixelFlasher will automatically copy the boot image to your device, patch it in Magisk, then copy it back to your PC. The patched image should now appear in the boot image list.
8. Select the patched boot image, the desired flash mode (Keep Data), and click Flash Pixel Phone.
9. Pixel Flasher will automatically update bootloader, radio, system, then finally flash the patched boot image.
10. When your device boots, you should be updated with root.

Spoiler: Update and Root using the Android Flash Tool

1. Follow the instructions on the Android Flash Tool to update your device. Make sure Lock Bootloader and Wipe Device are UNCHECKED.
2. When the update completes, the device will be in fastbootd. Reboot to bootloader.
3. Boot the master root image (See note 1):

   fastboot boot <drag and drop master root.img here>

   Note: If you prefer, you can download the factory zip and manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
4. Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
5. Reboot your device. You should now be updated with root.

Spoiler: Pass SafetyNet

This is my configuration that is passing Safety Net. I will not provide instructions on how to accomplish this. Attempt at your own risk.

Zygisk + DenyList enabled
All subcomponents of these apps hidden under DenyList:

• Google Play Store
• GPay
• Any banking/financial apps
• Any DRM media apps

Modules:

• MagiskHide Props Config 6.1.2 (automatically installed) - MHPC GitHub and XDA Thread
• Universal SafetyNet Fix 2.2.1 - USNF GitHub and XDA Thread

To check SafetyNet status:

• YASNAC - GitHub

I do not provide support for Magisk or modules. If you need help with Magisk, here is the Magisk General Support thread. For support specifically with Magisk v24+, see this thread.

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 @ipdev , @kdrag0n , @Didgeridoohan , and last but not least, @topjohnwu for all their hard work!

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.

 

[V0latyle]

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?

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.

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.

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.

Gladly donate if you can, my brain fog and ADHD making comprehending things impossible at times. Thanks.

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.

 

[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.

 

[CarinaPDX]

I updated a couple of weeks ago with no problems. I have given up on using the OTA update or trying to preserve root. I downloaded the factory image to my computer, extracted boot.img and transferred it to my 5a, then patched it with Magisk and transferred it back to my computer and then uninstall/restore images in Magisk. Then I removed the "-w" from the script and ran it to update the OS. Reboot. Use fastboot to boot with the patched boot image, run Magisk and patch directly the boot.img. Reboot and your finished.

I think some of the problems experienced relate to the fact that this update includes updates to the bootloader and the radio (modem), which needs to be done before the OS update. The included script does that; updating the OS before the other updates is likely to cause problems. And failure to update the radio can easily cause connection problems as the OS expects to be working with the new firmware, not the old.

There are two scripts included, one a shell script. Just be certain that you remove the "-w" in the script you are using before proceeding: -w wipes your disk and you don't want to lose your Home data I presume.

 

[CarinaPDX]

I just updated with the October security patch and everything seemed to go smoothly. I removed Magisk, took the OTA, then after reboot I shut down and used fastboot boot with a patched image to start the phone, and finished with a Magisk direct install. Just one problem: no internet access. I can connect to 5G or WiFi but have no internet availability. I will flash the full factory image and hope that works. Very strange...

 

[V0latyle]

I updated a couple of weeks ago with no problems. I have given up on using the OTA update or trying to preserve root. I downloaded the factory image to my computer, extracted boot.img and transferred it to my 5a, then patched it with Magisk and transferred it back to my computer and then uninstall/restore images in Magisk. Then I removed the "-w" from the script and ran it to update the OS. Reboot. Use fastboot to boot with the patched boot image, run Magisk and patch directly the boot.img. Reboot and your finished.

I think some of the problems experienced relate to the fact that this update includes updates to the bootloader and the radio (modem), which needs to be done before the OS update. The included script does that; updating the OS before the other updates is likely to cause problems. And failure to update the radio can easily cause connection problems as the OS expects to be working with the new firmware, not the old.

This has been covered in the OP. I don't use the script but it is important to ensure the bootloader and radio are updated if necessary. The system image checks the bootloader and radio versions.

There are two scripts included, one a shell script. Just be certain that you remove the "-w" in the script you are using before proceeding: -w wipes your disk and you don't want to lose your Home data I presume.

I actually recommend against using the script, because of the importance of learning how to use ADB and fastboot. Complacency is a good way to make a mistake.

I just updated with the October security patch and everything seemed to go smoothly. I removed Magisk, took the OTA, then after reboot I shut down and used fastboot boot with a patched image to start the phone, and finished with a Magisk direct install. Just one problem: no internet access. I can connect to 5G or WiFi but have no internet availability. I will flash the full factory image and hope that works. Very strange...

That is odd. Do you happen to have custom DNA servers set, or something else associated with your connection such as a VPN?

 

[CarinaPDX]

The first two quotes were for the 12>13 upgrade, which I see that I failed to mention. Version upgrades are typically more complex and I think it best to just install a factory image, however one chooses to do it.

I thought a simple security update would not cause problems but that is not the case it seems. I have not messed with the DNS settings AFAIK (I can't even find them); on previous phones I have used an app for using custom DNS servers. I change the DNS servers at my gateway so that DHCP provides them to all connected devices. I also have used VPNs in the past but not on this phone - I am using wireguard on my computer and have yet to learn how to set up WG on Android.

 

[V0latyle]

The first two quotes were for the 12>13 upgrade, which I see that I failed to mention. Version upgrades are typically more complex and I think it best to just install a factory image, however one chooses to do it.

The "safest" way is always via OTA.

I thought a simple security update would not cause problems but that is not the case it seems. I have not messed with the DNS settings AFAIK (I can't even find them); on previous phones I have used an app for using custom DNS servers. I change the DNS servers at my gateway so that DHCP provides them to all connected devices. I also have used VPNs in the past but not on this phone - I am using wireguard on my computer and have yet to learn how to set up WG on Android.

Speaking of OTAs, try sideloading the update, see if that fixes your issue. Not sure if it will TBH...failing that, the only thing I can really suggest is a data wipe

 

[CarinaPDX]

I downloaded the factory image and used "fastboot update <system image>" (which restored internet access). Then patched the boot.img with Magisk (25205) and lost internet access again. I tried a couple of times and it is repeatable. I can't imagine what else could be the problem other than Magisk. Am I the only one that has internet access problems with the October security plot and Magisk? I guess I will have to live without root for awhile...

 

[V0latyle]

I downloaded the factory image and used "fastboot update <system image>" (which restored internet access). Then patched the boot.img with Magisk (25205) and lost internet access again. I tried a couple of times and it is repeatable. I can't imagine what else could be the problem other than Magisk. Am I the only one that has internet access problems with the October security plot and Magisk? I guess I will have to live without root for awhile...

Magisk Canary is basically the test channel. Try Stable 25.2 and see if it works.

Also, double check your Magisk modules. What modules are you using? Are you using private DNS or anything?

 

[CarinaPDX]

Last night I realized that it might be the AdAway module (I normally don't even think about it being there - it just works). It directly affects the DNS process. So I will be removing AdAway and re-installing Magisk and see if that works. It would be disappointing as I really appreciate not being inundated with ads, but first I have to narrow it down before it can be fixed.

 

[V0latyle]

Last night I realized that it might be the AdAway module (I normally don't even think about it being there - it just works). It directly affects the DNS process. So I will be removing AdAway and re-installing Magisk and see if that works. It would be disappointing as I really appreciate not being inundated with ads, but first I have to narrow it down before it can be fixed.

Do you mean systemless hosts?

You can toggle AdAway on or off, and you may want to consider disabling host lists as well as using custom DNS just in case the DNS servers you're trying to use are blacklisted. I personally use CloudFlare: 1.1.1.1 and 1.0.0.1. Not quite as fast or reliable as Google (8.8.8.8, 8.8.4.4) but DNS requests are not logged or stored.

I am using 4 lists:

• AdAway official hosts
• Energized Spark
• Pete Lowe blocklist
• Steven Black unified hosts

I don't have any problems with Internet connectivity. Try using a custom DNS server and just the AdAway official host list and see if you still have the same problem. Also, test to see if it's specific sites you have a problem with. Try a VPN as well.

 

[MattsyGravy]

Are the steps the same for Android 13? Had to RMA my phone and Google sent me the phone with 13 installed. I see guides for the 6 with 13, just want to make sure there aren't any issues when I get home to get everything set back up again.

 

[V0latyle]

Are the steps the same for Android 13? Had to RMA my phone and Google sent me the phone with 13 installed. I see guides for the 6 with 13, just want to make sure there aren't any issues when I get home to get everything set back up again.

Everything is exactly the same. Don't try to use an older version of Magisk. No special instructions for barbet.

 

[xmsjshou]

Everything is exactly the same. Don't try to use an older version of Magisk. No special instructions for barbet.

Thanks for the guide! I followed all the steps, and it worked on well my device for Android 13.

Yet I got an issue - whenever I reboot my device I lose my Magisk root.
In this case, I have to go back into the bootloader and boot with the patched image again...

Is there any solution to the "root lost issue after reboot"?
(for the same device I remember when it's Android 12, no issue after reboots)

 

[V0latyle]

Thanks for the guide! I followed all the steps, and it worked on well my device for Android 13.

Yet I got an issue - whenever I reboot my device I lose my Magisk root.
In this case, I have to go back into the bootloader and boot with the patched image again...

Is there any solution to the "root lost issue after reboot"?
(for the same device I remember when it's Android 12, no issue after reboots)

Sounds to me like you've just been live booting the patched image, instead of flashing it. This is fine, but if you want root to persist after a reboot, you need to launch Magisk, tap Install, then Direct Install.

This was outlined in the OP.