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

[V0latyle]

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: 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 <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 <<RECOMMENDED FOR NOVICES>>

PixelFlasher by @badabing2003 is an excellent tool that streamlines the update process - it even patches the boot image for you.
The application essentially automates the ADB interface to make updating and rooting much easier. However, it is STRONGLY recommended that you still learn the "basics" of using ADB.

For instructions, downloads, and support, please refer to the PixelFlasher thread.

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/Play Integrity

SafetyNet has been deprecated for the new Play Integrity API. More information here.

In a nutshell, Play Integrity uses the same mechanisms as SafetyNet for the BASIC and DEVICE verdicts, but uses the Trusted Execution Environment to validate those verdicts. TEE does not function on an unlocked bootloader, so legacy SafetyNet solutions will fail.

However, @Displax has modified the original Universal SafetyNet Fix by kdrag0n; his mod is able to force basic attestation instead of hardware, meaning that the device will pass BASIC and DEVICE integrity.

Mod available here. Do not use MagiskHide Props Config with this mod.

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:

• Universal SafetyNet Fix 2.3.1 Mod - XDA post

To check SafetyNet status:

• YASNAC - GitHub

To check Play Integrity status:

• Play Integrity Checker - NOTE: MEETS_STRONG_INTEGRITY will ALWAYS fail on an unlocked bootloader.

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

 

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

 

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

 

[mcwups1]

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.

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.

 

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

 

[V0latyle]

I'm currently using Magisk Canary build?
May I Install Magisk Beta and also Magisk Stable build to the latest November 2021 build?

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.

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.

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.

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

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.

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?

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.

 

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

 

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

 

[tintn00+xda]

I got my phone back into bootloader and followed your second method via fastboot. I also arrived at the same error.

 

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

 

[Rafiul Bari Chowdhury]

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.

This guide is for only Android 12. And you can't get your now at any cost.

 

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

 

[V0latyle]

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.

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.

That's a bummer. Guess there should be a disclaimer about going from Android 11 to 12. Good thing everything is backed up.

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

As many of you know by now, in order to run a patched boot image on Android 12 requires disabling Android Verified Boot.

Verified Boot on Android 12 devices, at least Pixels with the SD765G and Tensor, is tied to device encryption. Therefore, disabling Verified Boot requires a wipe, if it was not previously disabled.

This is why it's important to read the entire post, and ask questions if you don't understand something before you proceed.

 

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

 

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

 

[V0latyle]

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

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.

 

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

 

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

 

[schalacker]

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. This needs testing, make sure you back up your data and photos before you try this!

I will be updating the OP to reflect this.

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.

 

[V0latyle]

Someone want to test this?
Requirement: Pixel 4a, 5, 5a, 6, 6 Pro rooted with Magisk 23016

1. Reboot into bootloader and reflash vbmeta without flags.
2. Reboot to system.
3. Reboot to bootloader again, re-reflash vbmeta with disable flags.
4. Reboot to system. If you get the Rescue Party corruption message, just reboot to bootloader and reflash vbmeta without flags.

Report results here.