• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
Search This thread

Homeboy76

Senior Member
Aug 24, 2012
2,789
1,404
Hello all, Pixel 4a5G on Xfinity Mobile. I was perfectlty rooted on v11 but decided to install the latest v12.0.0 (SP1A.211105.002.A1) Nov 2021 Verizon, Verizon MVNOs>
Tried to root via Magisk only to fail multiple times. I thought I bricked my phone as it was stuck in recovery but got int to boot again. I tried doing it like I did in V11 but have discovered that this no longer works
Installed Magisk
Extracted Boot.img
Patched Boot.img with Magisk and renamed to magisk_patched_boot.img
Extracted vbmeta.img
Placed both files in on PC in my ADB folder
Disabled AVB and DM Verify via fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Flashed patched boot.img via fastboot flash boot magisk_patched_boot.img
Rebooted and it is stuck in bootloader

What am I doing worng. Does it have to do anything with the Nov 2021 security updates. At this point I'm thinking about going back to 11.
Thanks in advance
BB
The first time you upgrade to Android 12 you must wipe your phone in addition to disabling verity and permission to root it.

Read the Notes in #4, then do #4 'Wipe data'.
 
Last edited:
  • Like
Reactions: Bad Bimr

Bad Bimr

Senior Member
Dec 29, 2010
189
23
The first time you upgrade to Android 12 you must wipe your phone in addition to disabling verity and permission to root it.

Read the Notes in #4, then do #4 'Wipe data'.
The first time I tried to upgrade I did not wipe the data nor did I disable Magisk. I downloaded the latest build, extrated the boot.img file, patched it with Magisk and re-insertedit the now patched boot.img inside the zip and did a flash-all.bat without wipe (removed -w inside the bat file). That's what started this big Ol' mess. This method worked before but not today, thanks google, LOL!
Regardless I am currently on the latest build. I just did a fresh install via adb flash-all.bat WITH wipe.
Again I never disabled Magisk but that was like 2 or 3 flashes ago.
Should I be good now or do I need to do something more.
Thanks
BB

EDIT: I noticerd in part 4 it says:
change fastboot -w update image-bramble-aa9a.999999.999.zip
to fastboot -w --disable-verity --disable-verification update image-bramble-sp1a.999999.999.zip
I did NOT change this command
Can I just run fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Or should I do another flash. If I do another flash should I do wipe again or not?
Thanks
 
Last edited:

Homeboy76

Senior Member
Aug 24, 2012
2,789
1,404
The first time I tried to upgrade I did not wipe the data nor did I disable Magisk. I downloaded the latest build, extrated the boot.img file, patched it with Magisk and re-insertedit the now patched boot.img inside the zip and did a flash-all.bat without wipe (removed -w inside the bat file). That's what started this big Ol' mess. This method worked before but not today, thanks google, LOL!
Regardless I am currently on the latest build. I just did a fresh install via adb flash-all.bat WITH wipe.
Again I never disabled Magisk but that was like 2 or 3 flashes ago.
Should I be good now or do I need to do something more.
Thanks
BB

EDIT: I noticerd in part 4 it says:
change fastboot -w update image-bramble-aa9a.999999.999.zip
to fastboot -w --disable-verity --disable-verification update image-bramble-sp1a.999999.999.zip
I did NOT change this command
Can I just run fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Or should I do another flash. If I do another flash should I do wipe again or not?
Thanks
You need to change this line in the flash-all.bat file:
[B]fastboot -w update image-bramble-sp1a.999999.999.zip[/B]
to this:
[B]fastboot -w --disable-verity --disable-verification update image-bramble-sp1a.999999.999.zip[/B]

Wiping the phone is necessary if you want to root your phone.

You do not need to flash the vbmeta.img: [B]fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img[/B]

Just flashing the vbmeta.img will not allow you to root your phone.
 
Last edited:
  • Like
Reactions: Bad Bimr

Bad Bimr

Senior Member
Dec 29, 2010
189
23
You need to change this line in the flash-all.bat file:
fastboot -w update image-bramble-sp1a.999999.999.zip
to this:
fastboot -w --disable-verity --disable-verification update image-bramble-sp1a.999999.999.zip

Wiping the phone is necessary if you want to root your phone.

You do not need to flash the vbmeta.img: fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img

Just flashing it will not allow you to root your phone.
Thank you.
One more question. After doing the above (fastboot -w --disable-verity --disable-verification update image-bramble-sp1a.999999.999.zip)and then install Magisk, when I need to flash the patched boot.img do I do it as normal or do I first need to flash the vbmeta.img:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Thanks Again.
BB
 

Homeboy76

Senior Member
Aug 24, 2012
2,789
1,404
Thank you.
One more question. After doing the above and install Magisk when I need to flash the patched boot.img do I do it as normal or do I first need to flash the vbmeta.img:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Thanks Again.
BB
Normal:
fastboot flash boot magisk_patched_...img
fastboot reboot

You do not need to flash the vbmeta.img.
 
Last edited:
  • Like
Reactions: Bad Bimr

Bad Bimr

Senior Member
Dec 29, 2010
189
23
You need to change this line in the flash-all.bat file:
[B]fastboot -w update image-bramble-sp1a.999999.999.zip[/B]
to this:
[B]fastboot -w --disable-verity --disable-verification update image-bramble-sp1a.999999.999.zip[/B]

Wiping the phone is necessary if you want to root your phone.

You do not need to flash the vbmeta.img: [B]fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img[/B]

Just flashing the vbmeta.img will not allow you to root your phone.
One week on 12 with Magisk root and all was fine until yesterday. Phone boots for about 1 1/2 minuets, and freezes. The touchscreen does not respond to input and buttons do not work as well. The phone restart in about a minuet or so. but it's goes straight to the Google bypassing a the bootloader in unlocked,press to pause screen. Restarting the phone in safe mode the phone works fine. I assume it's a rouge app but I don;t know which one. I downloaded and ran a Malwarebytes scan that took forever because of the rebooting and it did find and remove a "threat" however that did not fix things.
I guess I will need to reset the phone.
Considering I have Magisk installed, I need to remove magisk first. Can I then use ADB to push the image or do I need to do a full wipe first before ADB.
Do I need to do this again? fastboot -w --disable-verity --disable-verification update image-bramble-sp1a.999999.999.zip
Please advise. Thanks in advance.
BB
 

Homeboy76

Senior Member
Aug 24, 2012
2,789
1,404
One week on 12 with Magisk root and all was fine until yesterday. Phone boots for about 1 1/2 minuets, and freezes. The touchscreen does not respond to input and buttons do not work as well. The phone restart in about a minuet or so. but it's goes straight to the Google bypassing a the bootloader in unlocked,press to pause screen. Restarting the phone in safe mode the phone works fine. I assume it's a rouge app but I don;t know which one. I downloaded and ran a Malwarebytes scan that took forever because of the rebooting and it did find and remove a "threat" however that did not fix things.
I guess I will need to reset the phone.
Considering I have Magisk installed, I need to remove magisk first. Can I then use ADB to push the image or do I need to do a full wipe first before ADB.
Do I need to do this again? fastboot -w --disable-verity --disable-verification update image-bramble-sp1a.999999.999.zip
Please advise. Thanks in advance.
BB
"Do I need to do this again? fastboot -w --disable-verity --disable-verification update image-bramble-sp1a.999999.999.zip"
Yes.
 

Bad Bimr

Senior Member
Dec 29, 2010
189
23
"Do I need to do this again? fastboot -w --disable-verity --disable-verification update image-bramble-sp1a.999999.999.zip"
Yes.
Not sure if it is Android 12 or my particular phone but I've never been so frustrated. Uninstalled Magiisk, rebooted device, did a factory data reset from within the OS, rebooted, set-up fresh device, enabled usb debugging, flashed latest build with the above commands added into the flash-all,bat file. Rather then profit I would up with a brick. It would boot strait into the bootloade. Going to recovery and trying to do a factory reset resulted in failure. The only solution was to I reboot my PC, change USB ports, and adb sideload the factory OTA. reboot, set-up,enable usb debugging and flash again with falsh-all and the above commands and finally rooted with Magisk. The phome is working again but I am seriously frustrated. If the phone crashes again in a week, I'm going back to 11.
 

Homeboy76

Senior Member
Aug 24, 2012
2,789
1,404
Not sure if it is Android 12 or my particular phone but I've never been so frustrated. Uninstalled Magiisk, rebooted device, did a factory data reset from within the OS, rebooted, set-up fresh device, enabled usb debugging, flashed latest build with the above commands added into the flash-all,bat file. Rather then profit I would up with a brick. It would boot strait into the bootloade. Going to recovery and trying to do a factory reset resulted in failure. The only solution was to I reboot my PC, change USB ports, and adb sideload the factory OTA. reboot, set-up,enable usb debugging and flash again with falsh-all and the above commands and finally rooted with Magisk. The phome is working again but I am seriously frustrated. If the phone crashes again in a week, I'm going back to 11.
What version of Magisk and Safety net Fix are you using?

I'm assuming you have SDK Platform-tools r31.0.3 installed on your computer?
 

Bad Bimr

Senior Member
Dec 29, 2010
189
23
What version of Magisk and Safety net Fix are you using?

I'm assuming you have SDK Platform-tools r31.0.3 installed on your computer?
Currently Canary 23015 and Safety Net Fix 2.2.0
Something weird though is that the modules installed are showing but the modules you can choose and search for are not showing in Magisk. I only run 3 modules that I have backups for so no issue for me at least not yet.

EDIT: Oh crap I WAS on Platform Tools 30.0.5, Oops I wonder if that was the issue for all the problems.
PLEASE tell me I don;t have to do this again, LOL!
I have a spare P3aXL that I am going to do put 12 on. See if it will go smoother with the new Platform Tools

EDIT: I think I have found the issue. Again I wiped the phone and set it up with a fresh install of 12. After some issues I got it to boot on Friday 11-26. I rooted and all was well until last night 11-27 when the same thing started to happen, constant reboots after a the phone was on for a few minuets. Before wiping the phone again and reverting to 11 I thought about everything I did with the phone since Friday 9not much). After some thinking I remembered that although installed via backup/restore I never used the Greenify app untill late Saturday when I opened the app and gave it root privileges. Could this be my problem? I uninstalled the Greenify app and low and behold the phone is back to normal, at least for now. I don't know what it is doing but I assume Greenify is hibernating a vital system app that is causing the phone to freeze and reboot. For now the phone is working good.
 
Last edited:

Homeboy76

Senior Member
Aug 24, 2012
2,789
1,404
Currently Canary 23015 and Safety Net Fix 2.2.0
Something weird though is that the modules installed are showing but the modules you can choose and search for are not showing in Magisk. I only run 3 modules that I have backups for so no issue for me at least not yet.

EDIT: Oh crap I WAS on Platform Tools 30.0.5, Oops I wonder if that was the issue for all the problems.
PLEASE tell me I don;t have to do this again, LOL!
I have a spare P3aXL that I am going to do put 12 on. See if it will go smoother with the new Platform Tools
An old SDK Platform-tools definitely was part of the problem.

If you want to install modules, install this:
Fox Magisk Module Manager: 0.1.2 (FoxMmm-0.1.2.apk. 2.59 MB)
- A new module manager for Magisk Alpha/Canary
 
Last edited:
  • Like
Reactions: Bad Bimr

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Pixel 4a 5g. Took the OTA from A11 to A12 without wipe. Am now on temporary root. In preparation for an eventual data wipe I'm trying to grab my TitantiumBackup folder and copy it to my desktop. Dumb folder permission issues. Any one have an idea how to download the folder so the stuff that Google Backup doesn't have doesn't get wiped? The TB Sync to Google Drive always gives a network error message.

    THank you.
    I had this exact same problem. What I eventually had to do was go to menu > preferences > backup folder location. From there I selected a location with the "DocumentProdiver" storage option. I had to delete and redo all the backups, but afterwords I was able to copy onto my PC no problem.
    1
    News flash
    #4 Install/Update Factory Image keep data or wipe data has been updated: @creezalird discovered the Pixel 4a 5(G) and Pixel 5 upgrading to Android 12 or updating Android 12 process by flashing the factory image does not require flashing vbmeta.img (fastboot flash --disable-verity --disable-verification --slot=all. vbmeta vbmeta.img).
    To clarify:

    If you flash the factory image like this (and you should)
    Code:
    fastboot update --disable-verity --disable-verification image-device-buildnumber.zip
    Then reflashing vbmeta is redundant and unnecessary.

    If you update by sideloading the OTA, you MUST reflash vbmeta IMMEDIATELY following:
    Code:
    fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
    1
    The OP #4 has been updated with this information about upgrading/updating Android 12 via the factory image. Thanks, for the information on how to update Android 12 via OTA. :)
    I had two extra pennies that I wanted to share.
    1
    So I need to re-root my fathers phone as he did not listen and allowed it to install android 12: Since it is on 12 I can not even back up the phone so that is very-very bad!

    I patched the boot.img, but I can not boot it as I get:

    Using Canary 23012 (latest), I can boot this image using fastboot

    > fastboot boot magisk_patched-23012_nqilw.img

    However if I try to patch the image using magisk (prefered), then it stops at the fastboot prompt, same if I manually flash the boot image

    > fastboot flash boot magisk_patched-23012_nqilw.img

    I get stuck at fastboot prompt and can not get to teh OS.

    If I run:

    > fastboot flash boot boot.img

    Then it boots, but is not rooted. I'm at a loss how to flash a rooted boot images as both possible methods fail to succeed in booting. Yet fastboot boot <magisked image> works. So it makes no sense.
    The only way to root it is flash the Factoy image with the -w (wipe). See #4 wipe data.
    1
    Hello all, Pixel 4a5G on Xfinity Mobile. I was perfectlty rooted on v11 but decided to install the latest v12.0.0 (SP1A.211105.002.A1) Nov 2021 Verizon, Verizon MVNOs>
    Tried to root via Magisk only to fail multiple times. I thought I bricked my phone as it was stuck in recovery but got int to boot again. I tried doing it like I did in V11 but have discovered that this no longer works
    Installed Magisk
    Extracted Boot.img
    Patched Boot.img with Magisk and renamed to magisk_patched_boot.img
    Extracted vbmeta.img
    Placed both files in on PC in my ADB folder
    Disabled AVB and DM Verify via fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
    Flashed patched boot.img via fastboot flash boot magisk_patched_boot.img
    Rebooted and it is stuck in bootloader

    What am I doing worng. Does it have to do anything with the Nov 2021 security updates. At this point I'm thinking about going back to 11.
    Thanks in advance
    BB
    The first time you upgrade to Android 12 you must wipe your phone in addition to disabling verity and permission to root it.

    Read the Notes in #4, then do #4 'Wipe data'.
  • 21
    [Guide] Root Pixel 4a (5G) Android 12 Unlock/Lock Bootloader + Systemless ROOT
    Android Security Bulletin—November 2021
    Pixel Update Bulletin—November 2021

    Introduction
    This Guide is for Pixel 4a 5(G) owners that want to Root their phone, and enjoy the benefits of rooting it without installing a Custom ROM. However, for those that just can't live without a Custom ROM, take a look at 'Custom ROMs for Pixel 4a 5(G)'.

    New
    1. Magisk Modules for Magisk Alpha/Canary
    2. Magisk Alpha (vvb2060)


    Update(s)
    1. Factory/OTA Images - 11/01
    2. Magisk Stable - Magisk-23.0 05/12
    3. Magisk Beta - Magisk-23.0 05/12
    4. Magisk Canary - Magisk-23013 11/07
    5. TWRP - Waiting for T.R.W.P. for Android 12
    6. SafetyNet - SafetyNetFix v2.2.0
    7. SDK Platform-tools - r31.0.3 08/18
    8. Custom Kernels
      • Waiting . . .
    9. Custom ROMs
      • ProtonAOSP[12] 11/01

    Disclaimer
    1. I assume no responsibility for the malfunctioning/bricking of your phone.
    2. The order of listed items i.e., Custom Kernels, Custom ROMS, etc. Does not indicate my preference for them. It is your responsibility to do the research before selecting an item.

    Prerequisites
    1. A Pixel 4a 5(G) phone with an unlocked bootloader.
    2. The latest Android Factory or OTA Image: "bramble" for Pixel 4a 5(G)

      Factory Image

      OTA Image
    3. A Computer with the latest SDK Platform-Tools: r31.0.3 installed.
      • Important: Update Platform Tools, regularly, for optimal performance.

    Other Guides

    Credits/Thanks/Recognitions
    1. @creezalird- Flash Android 12 factory image.
    2. Those I may have, inadvertently, forgotten.

    Index
    (NOTE: Numbers 1-11 are not steps, they are individual sets of instructions).
    1. Open a Command Prompt/Boot Fastboot Mode/Boot Recovery

      • Open a Command Prompt on Computer
        1. Open File Explorer, click the platform-tools folder ==> click the folder icon (left side of address bar) to highlight it type cmd and press enter.
        2. Open a Powershell Command Prompt on Computer: Open File Explorer, click the platform-tools folder ==> click the folder icon (left side of address bar) to highlight it type powershell and press enter.
        3. Notes:
          • Enable USB Debugging, on your phone: Settings ==> System ==> Advanced ==> Developer options ==> Scroll down to USB debugging and enable it.
          • When using the Powershell Command Prompt Commands must be preceeded with ./: i.e, ./fastboot devices
          • If you do not want to open a Command Prompt every time you want to use the fastboot command, add the path to the Platform-tools folder to Windows environment variables.
      • Boot fastboot mode (bootloader):
        • Power off phone, press and hold the power and volume down buttons until you see Start.
      • Boot Recovery
        • Power off phone, press and hold the power and volume down buttons until you see Start. Use volume up/down button until you see Recovery mode. Press power button.
    2. Test fastboot

      • Enable Developer Options - Tap Settings > About phone > Build number 7 times or until you should see 'you are a Developer'.
      • Enable USB Debugging - Tap Settings > System > Advanced > Developer options >
        Enable USB Debugging.
      • Open a Command Prompt on your computer in the Platform-tools folder.
      • Boot fastboot mode on your phone (#1)
      • Connect the phone to the Computer.
      • At the prompt type: fastboot devices to verify communication with phone. It should return your phone's serial number.
    3. Unlock Bootloader/Return Phone to Stock/Lock Bootloader

      • Unlock Bootloader

        1. This will erase all user data from the device!
        2. Backup your data
        3. Activate Developer Options: Tap Settings > About Phone > Tap Build Number 7 times or until you see you are a Developer. Tap back > System > Advanced > Developer Options. Enable OEM Unlock and, USB Debugging.
        4. Boot fastboot mode
        5. Connect the phone to the Computer with USB cord.
        6. Open a Command Prompt on your computer and type fastboot flashing unlock and press enter.
        7. You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
        8. Allow the process to complete and then type fastboot reboot at the Command Prompt and press enter.
        9. When your phone reboots disconnect your usb cable.
          Notes: After unlocking your bootloader, you'll see a warning: The bootloader is unlocked and... You will see this warning until, you relock the bootloader.
          Do not relock your bootloader until you have returned the device to Stock.
      • Return Phone to Stock

        1. Backup your data/Internal storage
        2. Settings > System > Advanced > Reset Options > Erase all data (factory reset)
        3. Log in
        4. Set up phone
      • Lock Bootloader

        1. Return the phone to Stock before locking the bootloader, failure to do so could brick your phone
        2. This will erase all user data from the device!
        3. Boot fastboot mode
        4. Open a Command Prompt and type this at the Prompt: fastboot flashing lock
        5. You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
        6. Allow the process to complete, then type this at the Command Prompt: fastboot reboot
        7. Enable Developer Options: Settings > About phone > Tap Build number 7 times or until you see 'you are a developer'.
        8. Tap Back > Developer options and toggle OEM Unlock off.
    4. Install/Update Factory Image keep data or wipe data

      • Important Note(s):
        1. If you are upgrading your phone to Android 12 a wipe is, absolutely necessary, if you want to root your phone after the upgrade. Subsequent factory image updates do not require a wipe.
        2. If you are updating your phones firmware (factory image) and your phone was rooted: Disable all magisk modules and restore back Magisk app name if you hid it and reboot. Why? The magisk modules you are using may need updating to work with the updated firmware. Incompatiable modules cause bootloops. :(
        3. Always verify you have the latest version of SDK Platform-Tools installed on your computer before installing the Factory Image: Pixel 4a 5(G) - bramble.
        4. If you get an error: while flashing, try one of these options:
          • Change the USB port to a non charging USB port.
          • Change the USB cord.
          • Change Computers.
        5. Backup your data
        6. Download the latest Factory Image: Pixel 4a 5(G) - bramble to your Computer.
        7. Extract the factory Image to a folder.
      • Flash Factory Image Keep Data

        • Open the folder you extracted the Factory Image to and Edit the flash-all.bat file with a file editor i.e., DroidEdit app.
          1. Change this line: fastboot -w update image-bramble-aa9a.999999.999.zip
          2. to this: fastboot --disable-verity --disable-verification update image-bramble-sp1a.999999.999.zip
          3. Note: If you do not remove the -w your internal storage will be wiped.
        • After, you have edited the flash-all.bat file. Copy/Move these files to the Platform-tools folder:
          1. bootloader-bramble-....img
          2. flash-all.bat
          3. image-bramble-....zip
          4. radio-bramble-....img
        • Open a Command Prompt on your computer in the Platform-tools folder and type: flash-all at the Command Prompt and press enter.
        • The phone will reboot when flashing is complete.
        • Go-to 7. Root/Reroot with Magisk and Pass SafetyNet, • Patching the boot.img - to root/reroot.
      • Flash Factory Image Wipe Data

        • Open the folder you extracted the Factory Image to and Edit the flash-all.bat file with a file editor i.e., DroidEdit app.
          1. Change this line: fastboot -w update image-bramble-aa9a.999999.999.zip
          2. to this: fastboot -w --disable-verity --disable-verification update image-bramble-sp1a.999999.999.zip
          3. This will wipe your phone's Internal Storage.
        • Open the folder you extracted the Factory Image to and Copy/Move these files to the Platform-tools folder:
          1. bootloader-bramble-....img
          2. flash-all.bat
          3. image-bramble-....zip
          4. radio-bramble-....img
        • Open a Command Prompt on your computer in the Platform-tools folder and type: flash-all at the Command Prompt and press enter.
        • The phone will reboot when flashing is complete.
        • Setup phone
        • Enable Developer Mode and USB Debugging
          1. Setup => About phone => Tap Build number 7 times or untill you see you are a 'Developer'.
          2. Setup => System => Developer options => Enable Developer options => enable USB Debugging
        • Go-to 7. Root/Reroot with Magisk and Pass SafetyNet, • Patching the boot.img - to root/reroot.
    5. ADB Sideload

    6. Extract/Flash boot.img

      • Extract boot.img

        1. Download the latest Factory image to your phone.
        2. Extract the Factory Image file (bramble-r2d1a.999999.999-factory-99a9a99a.zip) to a folder.
        3. Open the folder and, extract the Image file (image-bramble-aa9a.999999.999.zip) into the folder.
      • Flash boot.img

        1. Flashing the boot.img removes root.
        2. Open the folder you extracted the 'image...zip' file to and copy the boot.img file to your computer's platform-tools folder or to the folder that has fastboot.exe in it.
        3. Boot fastboot mode
        4. Connect the phone to the Computer
        5. Open a Command Prompt and type the following command at the prompt:
          fastboot flash boot --slot all boot.img
        6. Reboot
    7. Root/Reroot with Magisk and Pass SafetyNet.

      • Android 12

        1. Upgrading to Android 12 and rooting your phone
          • OP, Index, 4. Install/Update Factory Image keep data or wipe data
        2. You wiped your phone when upgraded to Android 12. You want to update the factory image and re-root it.
          • OP, Index, 4. Install/Update Factory Image keep data or wipe data
      • Patching the boot.img - to root/reroot.

        1. Do #6 - Extract boot.img
        2. Install Magisk Canary 23015
          Note: Tap 3 dot menu across from canary => Download, app-debug.apk
        3. Open Magisk Canary App
        4. Set the Update Channel Canary.
        5. Tap Install (next to Magisk)
        6. Tap, Select and Patch a File
        7. Select the boot.img file you extracted from the latest factory image.
        8. Tap the ✓ (Check Mark)
        9. Tap Let's Go
        10. When you see done, the boot.img has been patched (magisk_patched_xxxxxx.img), and stored in the download folder.
        11. Reboot
        12. Copy the patched boot.img file to your computer's Platform-tools folder or the folder that has fastboot.exe in it.
        13. Boot fastboot mode
        14. Connect the phone to the Computer with USB cord.
        15. Open a Command Prompt in the folder you copied the patched boot.img to.
        16. Type fastboot flash boot "name of patched boot".img without the quote marks at the Prompt and press enter.
        17. Type fastboot reboot at the Prompt and press enter.
        18. Important Notes: If your phone boot loops try one of the following options:
          • Flash the 'stock' boot.img to both slots: fastboot flash boot boot.img --slot all
          • Boot Safe Mode - Press Power Off button ==> Press Power Off until you see boot Safe Mode ==> Press Ok.
      • Pass Safety Net with SafetyNet Fix 2.2.0

        1. Download File(s)
        2. Install SafetyNet Fix 2.2.0
          • Open Magisk
          • Tap Modules icon
          • Tap Install from storage
          • Navigate to the SafetyNetFix file you downloaded
          • Tap the SafetyNetFix file
          • Tap the check mark (✓ at the bottom) to start the installation.
          • After it installs tap the Save icon to save the log
          • Tap Reboot.
        3. Settings for Magisk Canary 23015
          • Open Magisk App
          • Tap the Setup icon.
          • Scroll down to App and set the Update Channel to Canary.
          • Scroll down to Check Updates and enable it.
          • Scroll down to Magisk and enable Zygisk and Enforce DenyList.
          • Tap Configure DenyList => Tap 3 Dot Menu => Check ✓ Show system apps => Check ✓ Google Play Store, Google Pay, etc.
          • Scroll down to Superuser and enable Enable Biometric Authentication.
        4. Get Device Certified Clear Google Play Services, Google Play Store, Google Pay, etc. data
          • Turn Airplane mode on
          • Open Settings
          • Tap Apps & notifications
          • Tap see all...
          • Tap three dot menu
          • Tap Show system
          • Scroll down to Google Play Store
          • Tap Storage and Cache
          • Tap Clear storage
            Note: Repeat the 3 steps above for Google Play Services, Google Pay, etc.
          • reboot
          • Turn Airplane mode off
        5. Check Device Certification
          • Open Google Play Store app
          • Tap Menu - Circle top right
          • Tap Settings
          • Tap About
          • Check Play protect certification.
    8. Set Magisk App Update Channel/Update Magisk

      • Set Magisk App Update Channel

        • Open Magisk App > Tap Settings icon > Update Channel > Select Stable, Beta, Canary or Custom.
      • Update Magisk

        1. When Magisk App notifies you of an update:
        2. Tap install.
        3. Select, Direct Install (Recommended)
        4. When it finishes installing
        5. Tap, Save Log
        6. Log location: /storage/emulated/0/Download
        7. Tap, Reboot
        8. Done!
    9. Custom ROMs

      • Need help with a Custom ROM?
        • First, read and follow the Installation Instructions. The installation instructions are in the OP.
        • Second, if you have a problem Installing it, Search the thread of the Custom ROM you are trying to install for a solution to problem: If you don't find a solution post your request for help on the thread.
      • ROMs
        • Alpha/Beta

          • None
        • Official
        • Unofficial

          • None
    10. Apps/Mods/Scripts/Tethering/Themes
    11. T.W.R.P. Backup/Restore

      • Waiting for Android 12 T.W.R.P.
    3
    hi @Homeboy76 ,
    maybe i'm wrong, but in your
    Prerequisites

    1. A Pixel 4a 5(G) phone with an unlocked bootloader.
    2. The latest Android 11 (R) Factory or OTA Image: "bramble" for Pixel 4a 5(G)
    3. Factory Image
    also at:
    4. Install/Update Factory Image keep or wipe data
    Just checked
    It is pointing to the Pixel 4a 5(G) bramble factory image.

    Download the latest Factory Image: Pixel 5 - bramble to your Computer. --> pixel 5 (only text)? Fixed!
    3
    Provided you are not on Verizon:
    Try reinstalling the stock boot.img from the update, flash the OTA, or perform another clean install. After first boot and performing any necessary setup (if clean install), power off phone, remove sim card, reboot. Creat a new patched boot.img, install it and reboot. Turn phone off, reinstall sim card, reboot as normal. Should fix the issue. Make sure you are using the latest magisk (I prefer stable of canary personally but it's your call).
    If you are on verizon, do not install the April update in this thread, as it is stated "All carriers EXCEPT Verizon."

    However, there is an OTA update on the official frimware website that does work on Verizon. I just flashed it myself. Maybe Homeboy76 could update thread?
    :( Do not repeat do not follow these instructions. The information is only partially correct. :(

    I just checked the Factory image and the OTA image pages the only change was the All carriers EXCEPT Verizon has been removed from the images description.

    The OP has been updated to reflect the change.

    These images work on Verizon Pixel 4a 5g phones.
    3
    Thanks for the write-up. Just got one of these as I dropped my old phone, and I was due anyways. So question regarding Safetynet. I went ahead and went with the latest Feb factory image, patched the boot and rooted with Magisk, then tried the safety net and attestation fails. Anybody have the feb patch and passing safetynet? if so what was the sequence you used? thanks
    - Root with Magisk patched img
    - Open Magisk Manager install SafetyNet module
    - Reboot
    - Open Magisk Manager Enable Magisk hide
    - Hide Google Play store, Google pay, etc
    - Clear cache and storage for the above apps
    - Reboot
    2
    Thanks for the write-up. Just got one of these as I dropped my old phone, and I was due anyways. So question regarding Safetynet. I went ahead and went with the latest Feb factory image, patched the boot and rooted with Magisk, then tried the safety net and attestation fails. Anybody have the feb patch and passing safetynet? if so what was the sequence you used? thanks

    You need Universal Safetynet fix v 1.1.1 Magisk module.