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

appro77

Senior Member
May 8, 2011
1,254
197
Mackay
Thanks so much for your guide. I've installed 12 and rooted. Everything running fine.

How do we handle Android 12 monthly updates and retain root or at least re-root if that is necessary?
 

Homeboy76

Senior Member
Aug 24, 2012
2,787
1,402
Thanks so much for your guide. I've installed 12 and rooted. Everything running fine.

How do we handle Android 12 monthly updates and retain root or at least re-root if that is necessary?
No one with a Pixel 4a 5(G) or Pixel 5, in any of the threads I've read, knows.

We are all hoping you just flash the factory image after removing the -w from the flash-all. bat file so you do not loose your data. Then flash the magisk_patched.img to reroot.

I guess we will find out when the November factory image drops.
 

appro77

Senior Member
May 8, 2011
1,254
197
Mackay
No one with a Pixel 4a 5(G) or Pixel 5, in any of the threads I've read, knows.

We are all hoping you just flash the factory image after removing the -w from the flash-all. bat file so you do not loose your data. Then flash the magisk_patched.img to reroot.

I guess we will find out when the November factory image drops.
Thanks for the reply. Just regarding the patched boot image.......does it need to be patched again each time from the boot image in the latest factory image or can the original patched boot image be used over and over again for updates as the arrive?
 

Homeboy76

Senior Member
Aug 24, 2012
2,787
1,402
Thanks for the reply. Just regarding the patched boot image.......does it need to be patched again each time from the boot image in the latest factory image or can the original patched boot image be used over and over again for updates as the arrive?
It should be patched with the boot image from the latest factory image.
 
Last edited:

roundaway

Senior Member
Dec 9, 2009
217
33
USA
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.
 

ballin2much

Member
Mar 3, 2014
9
1
Google Pixel 4a 5G
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.
 
  • Like
Reactions: roundaway

roundaway

Senior Member
Dec 9, 2009
217
33
USA
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.
Thank you for the tip. Worked like a charm. Going to do a factory reset/data wipe and flash A12 this week.

Edit - Used the guide in the Pixel 5 forum and encountered no problems flashing or using Magisk Stable to patch the boot.img. The Android Flash Tool was pretty cool!
 
Last edited:

appro77

Senior Member
May 8, 2011
1,254
197
Mackay
If I take today's update OTA will it just be a matter of downloading the factory image and patching the boot.img and install to get root back......same as I used to do on A11?
 

appro77

Senior Member
May 8, 2011
1,254
197
Mackay
Further to my above post, that didn't work. I patched the boot image from the newly downloaded image. Before I flashed it I used the command fastboot boot boot.img. That worked and the phone booted which usually indicates that the boot image is good.

I restarted the phone in fastboot mode and flashed the boot image using fastboot flash boot boot.img. It wouldn't boot when I restarted.

I then tried fastboot boot boot.img with the old unpatched boot image that I'd extracted from the downloaded image and that wouldn't boot either.

Then I flashed the old boot image using fastboot flash boot boot.img and the phone then booted. Problem is with the old unpatched image I don't have root.

Where to from here?

The boot error I was getting in the command window when the phone wouldn't boot was:

(bootloader) boot.img missing cmdline or OS version
 

Homeboy76

Senior Member
Aug 24, 2012
2,787
1,402
Further to my above post, that didn't work. I patched the boot image from the newly downloaded image. Before I flashed it I used the command fastboot boot boot.img. That worked and the phone booted which usually indicates that the boot image is good.

I restarted the phone in fastboot mode and flashed the boot image using fastboot flash boot boot.img. It wouldn't boot when I restarted.

I then tried fastboot boot boot.img with the old unpatched boot image that I'd extracted from the downloaded image and that wouldn't boot either.

Then I flashed the old boot image using fastboot flash boot boot.img and the phone then booted. Problem is with the old unpatched image I don't have root.

Where to from here?

The boot error I was getting in the command window when the phone wouldn't boot was:

(bootloader) boot.img missing cmdline or OS version
If this is the first time you updated the factory image to Android 12: (OP, Index, 4. Install/Update Factory Image keep data or wipe data)

If this is the second time you updated the factory image to Android 12 and you did not wiped data the first time: (OP, Index, 4. Install/Update Factory Image keep data or wipe data)

If this is the second time you updated the factory image to Android 12 and you wiped data the first time: (OP, Index, 4. Install/Update Factory Image keep data or wipe data)
 
Last edited:

appro77

Senior Member
May 8, 2011
1,254
197
Mackay
If this is the first time you updated the factory image to Android 12: (OP, Index, 4. Install/Update Factory Image keep or wipe data)

If this is the second time you updated the factory image to Android 12 and you did not wiped data the first time: (OP, Index, 4. Install/Update Factory Image keep or wipe data)

If this is the second time you updated the factory image to Android 12 and you ]U]wiped data[/U] the first time: (OP, Index, 4. Install/Update Factory Image keep or wipe data)
Thanks.
 

ballin2much

Member
Mar 3, 2014
9
1
Google Pixel 4a 5G
So just updated to Android 12 a few days ago with no issues. Got a notification for a Magisk update today, and ever since I updated, my phone will only work for a few minutes and then reboot all of the sudden. I flashed and patched the newest factory update, but it didn't fix the issue. Anyone know what might be going on?
 

Homeboy76

Senior Member
Aug 24, 2012
2,787
1,402
So just updated to Android 12 a few days ago with no issues. Got a notification for a Magisk update today, and ever since I updated, my phone will only work for a few minutes and then reboot all of the sudden. I flashed and patched the newest factory update, but it didn't fix the issue. Anyone know what might be going on?
Did you wipe your phone the first time you installed Android 12 on your Pixel 4a 5(G) phone?
 

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 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.1.1
    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.3installed.
      • 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. 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.
        3. If your phone was rooted, before flashing the factory image: disable all magisk modules, restore back Magisk app name if you hid it and reboot.
        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 23001 or Stable 23.0 App.
        3. Open Magisk App
        4. Depending on the version of Magisk App installed: Set the Update Channel to Beta, Canary or Stable.
        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 Magisk

        1. Canary 23001 or Stable 23.0

          • Download File(s)
            1. Canary 23001or Stable 23.0
              Universal SafetyNet Fix · 2.1.1
            2. Universal SafetyNet Fix · 2.1.2
              Note: This version only supports Riru
            3. Riru LSPosed
            4. XPrivacyLua
          • Install SafetyNetFix
            • 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.
          • Enable Magisk Hide
            • Open Magisk App
            • Tap the Setup icon.
            • Scroll down to Magisk - MagiskHide and enable it.
            • Tap Back arrow => tap Superuser icon => tap MagiskHide and enable (✓): Google Play Services and Google Play Store.
            • Close Magisk Manager.
          • Install Magisk Modules Riru, Riru - LSPosed and install XPrivacy Lua
            • Open Magisk
            • Tap Modules icon
            • Install Magisk module Riru-...zip
            • After it installs tap the Save icon to save the log
            • Reboot
            • Open Magisk
            • Tap Modules icon
            • Install Magisk module Riru_-_LSPosed-....zip
            • After it installs tap the Save icon to save the log
            • Reboot
            • Downloaded and install XPrivacy Lua module from: here
            • Reboot
            • Open LSPosed
            • Tap Modules
            • Enable XPrivacyLua module
            • Tap 3dots Menu (top-right)
            • Tap Hide
            • Uncheck System apps
            • Tap Google Play Services
            • Tap Setup icon (top-right)
            • Scroll down
            • Tap Google Play Services
            • Scroll down and enable/check (✓)
              1. Determine Activity
              2. Read identifiers
              3. Use analytics
              4. Use tracking
            • Reboot
            • Open Magisk
            • Test SafetyNet
          • Clear Google Play Services and Google Play Store Data
            • Turn Airplane mode on
            • Open Settings
            • Tap Apps & notifications
            • Tap see all...
            • Tap three dot menu
            • Tap Show system
            • Clear Cache and Storage for Google play Services and Google Play Store
            • Exit Settings
            • reboot
            • Turn Airplane mode off
          • Check Device Certification
            • Open Google Play Store app
            • Tap Menu - Circle top right
            • Tap Settings
            • Tap About
            • check Device certification.
        2. Canary 23013

          • Download File(s)
            1. Universal SafetyNet Fix · 2.2.0
            2. This version only supports Zygisk.
          • Enable Zigisk and Enforce DenyList
            1. Open Magisk
            2. Tap Setup icon
            3. Enable Zigisk
            4. Enable Enforce DenyList
            5. Tap back
          • Install SafetyNetFix
            1. Tap Modules icon
            2. Tap Install from storage
            3. Navigate to the SafetyNetFix file you downloaded
            4. Tap the SafetyNetFix file
            5. Tap the check mark (✓ at the bottom) to start the installation.
            6. After it installs tap the Save icon to save the log
            7. Tap Reboot.
          • Configure DenyList
            1. Open Magisk
            2. Tap Setup icon
            3. Tap Configure DenyList
            4. Tap 3 dot menu
            5. Tap Show system apps
            6. Select apps: Google Play Services, Google Play Store, etc.
            7. Reboot
          • Clear Google Play Services and Google Play Store Data
            1. Turn Airplane mode on
            2. Open Settings
            3. Tap Apps & notifications
            4. Tap see all...
            5. Tap three dot menu
            6. Tap Show system
            7. Clear Cache and Storage for Google play Services and Google Play Store
            8. Exit Settings
            9. reboot
            10. Turn Airplane mode off
          • Check Device Certification
            1. Open Google Play Store app
            2. Tap Menu - Circle top right
            3. Tap Settings
            4. Tap About
            5. check Device 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.