[Guide] Root Pixel 4a (5G) with Magisk + Unlock Bootloader + Pass SafetyNet + More

Search This thread

egandt

Senior Member
Mar 25, 2008
410
133
"Open a Command Prompt in the folder you copied the patched boot.img to.
Type fastboot flash boot "name of patched boot".img without the quote marks at the Prompt and press enter.
Type fastboot reboot at the Prompt and press enter."


On Magisk 25.0 and Build bramble-sq3a.220605.009.a1, I can not boot the patched image as it shows google screen then fails then reboots tries again then fails a second time with a message try again or wipe data (which I can not do as I have no backup yet since I do not have root).

"fastboot flash boot boot.img --slot all" recovers the phone, but not root which I need to create a backup (stupid phone upgraded even though I had it disabled and lost root before I could backup using swiftbackup).

I personally use oneplus never have issues, every time I work on the pixels I have issues with rooting and with them updating when I have disabled it in developer options

ERIC
 

Homeboy76

Senior Member
Aug 24, 2012
3,445
1,999
Google Pixel XL
Google Pixel 7 Pro
"Open a Command Prompt in the folder you copied the patched boot.img to.
Type fastboot flash boot "name of patched boot".img without the quote marks at the Prompt and press enter.
Type fastboot reboot at the Prompt and press enter."


On Magisk 25.0 and Build bramble-sq3a.220605.009.a1, I can not boot the patched image as it shows google screen then fails then reboots tries again then fails a second time with a message try again or wipe data (which I can not do as I have no backup yet since I do not have root).

"fastboot flash boot boot.img --slot all" recovers the phone, but not root which I need to create a backup (stupid phone upgraded even though I had it disabled and lost root before I could backup using swiftbackup).

I personally use oneplus never have issues, every time I work on the pixels I have issues with rooting and with them updating when I have disabled it in developer options

ERIC
- Do you have SDK Platform-tools 3.3.0.2 installed on your PC.?
- boot Safe Mode
- After, Safe mode is fully booted
- Reboot
- flash the bramble-sq3a.220605.009.a1 magisk_patched boot.img
 

Flagger1975

New member
Jun 30, 2022
4
0
I have a work project that required a rooted Android device and managed to get a Bramble rooted. Now a new stumbling block has arisen, I need to a copy a file to the /etc directory.. and I can't. Looks like I don't have permissions to save the file based on the ADB result. Magisk shows the device is rooted, root checker confirms, I use Root Browser and can see the System directories, just can't save to them. Is there anyway around this or a way to unlock the directory I need further? Device is on Android 12... think the December build.
 

Flagger1975

New member
Jun 30, 2022
4
0
@Homeboy76
I'm using Root Browser Classic, root access mode is enabled.. when I open the app I receive a message from Magisk that it granted Superuser rights. Is there another file manager I should use? Ive tried a few and either they didn't work properly or were so insanely ad filled they were unusable.
 

Flagger1975

New member
Jun 30, 2022
4
0
@Homeboy76
I don't get it either, I've tried multiple file browsers and they all report the file system is a read only file system. Im not sure if this is something Google did with Android 12 or what but its infuriating as this pretty much stops any work I can do.

Im guessing what is tripping me is well.. Google:

Can't edit system files

From Android 9 a lot has changed in Android, and if you can't edit system files anymore it is not because root is broken or not fully working.

On some system-as-root (SAR) devices you can no longer mount the system partition as read-write and doing systemless modifications through Magisk is an easy way of getting around that. If you do want to do actual edits of the system, and if it is even possible (from Android 10 it's actually impossible on some devices), you need to mount the root directory, /, as rw and not /system. You can also try editing the partition mirrors that Magisk keeps in /sbin/.magisk/mirror, but this should be the last resort since it might be tricky mounting them rw.

From v20.0, Magisk is also following the design laid down by Google, which is why you might suddenly start to experience this "issue" after updating from earlier Magisk versions.

Question is.. how do I mount the root directory as rw versus not /system?
 
Last edited:

Flagger1975

New member
Jun 30, 2022
4
0
@Homeboy76

I did and get plenty of responses including lots of things involving linux which have nothing to do with this particular situation. I was really hoping to get help for this particular use case versus Ubunta version whatever, or IBM operating system or whatever other results come back. Im trying not to brick this device as this was the only one we have I was able to get rooted thanks to Android OEM's. I very little linux knowledge and just as much knowledge on Android (so yeah, not much).
 

OneNutShort

Senior Member
Mar 29, 2010
213
43
Huntington Beach
Really appreciate the thorough guide. Looking to upgrade from rooted android 12 to rooted android 13, is there anything new or specific I need to look out for before updating? I see that the title for your guide references android 13, but the instructions still reference 12, and I know sometimes there are some special instructions or things to be aware of before flashing an updated OS.

Thanks again!
 

Homeboy76

Senior Member
Aug 24, 2012
3,445
1,999
Google Pixel XL
Google Pixel 7 Pro
Really appreciate the thorough guide. Looking to upgrade from rooted android 12 to rooted android 13, is there anything new or specific I need to look out for before updating? I see that the title for your guide references android 13, but the instructions still reference 12, and I know sometimes there are some special instructions or things to be aware of before flashing an updated OS.

Thanks again!
You're right about there still being references to Android 12. I'm working on fixing that problem.

A large number of XDA members are upgrading to Android 13 without wiping their phone. They are flashing the Factory Image (keep data) successfully with no problems.

If you decide to not wipe your phone and your phone is rooted, please remember to uninstall Magisk or remove all the modules from Magisk before you start upgrading to Android 13.
 
Last edited:
  • Like
Reactions: OneNutShort

OneNutShort

Senior Member
Mar 29, 2010
213
43
Huntington Beach
You're right about there still being references to Android 12. I'm working on fixing that problem.

A large number of XDA members are upgrading to Android 13 without wiping their phone. They are flashing the Factory Image (keep data) successfully with no problems.

If you decide to not wipe your phone and your phone is rooted, please remember to uninstall Magisk or remove all the modules from Magisk before you start upgrading to Android 13.

Thank you, really appreciate the quick response and the information.

Cheers.
 
  • Like
Reactions: Homeboy76
Mar 29, 2022
41
19
@Homeboy76
I don't get it either, I've tried multiple file browsers and they all report the file system is a read only file system. Im not sure if this is something Google did with Android 12 or what but its infuriating as this pretty much stops any work I can do.

Im guessing what is tripping me is well.. Google:

Can't edit system files

From Android 9 a lot has changed in Android, and if you can't edit system files anymore it is not because root is broken or not fully working.

On some system-as-root (SAR) devices you can no longer mount the system partition as read-write and doing systemless modifications through Magisk is an easy way of getting around that. If you do want to do actual edits of the system, and if it is even possible (from Android 10 it's actually impossible on some devices), you need to mount the root directory, /, as rw and not /system. You can also try editing the partition mirrors that Magisk keeps in /sbin/.magisk/mirror, but this should be the last resort since it might be tricky mounting them rw.

From v20.0, Magisk is also following the design laid down by Google, which is why you might suddenly start to experience this "issue" after updating from earlier Magisk versions.

Question is.. how do I mount the root directory as rw versus not /system?
Did you find any solution Chief?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 22
    [Guide] Root Pixel 4a (5G) with Magisk + Unlock Bootloader + Pass SafetyNet + More
    Android Security Bulletin—November 2022
    Pixel Update Bulletin—November 2022

    Introduction
    This Guide is for Pixel 4a 5(G) owners that want to Root their phone, and enjoy the benefits of rooting it. The Guide is divided into three parts: Information, Instructions, and Other.

    ~ ~ ~ Part I - INFORMATION ~ ~ ~
    1. Disclaimer

      • I assume no responsibility for the malfunctioning/bricking of your phone.
      • 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.
    2. Prerequisites

    3. Update(s)

    4. NEW

    5. My Other Guides
    6. Credits/Thanks/Recognitions

      • @creezalird- Flash Android 12 factory image.
      • Those I may have, inadvertently, forgotten.
    ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~
    (The Instructions listed below are not steps, they are individual sets of instructions.)

    1. Unlock Bootloader/Return Phone to Stock/Lock Bootloader

      • Unlock Bootloader

        1. Notes:
          • This will erase all user data from the device!
          • Backup your data
        2. 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.
        3. Boot fastboot mode
        4. Connect the phone to the Computer with USB cord.
        5. Open a Command Prompt on your computer and type fastboot flashing unlock and press enter.
        6. You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
        7. Allow the process to complete and then type fastboot reboot at the Command Prompt and press enter.
        8. When your phone reboots disconnect your usb cable.
        9. 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. Open Settings, tap System > Advanced > Reset Options > Erase all data (factory reset)
        3. Note: If you are selling or trading in the phone stop here.
        4. Log in
        5. Set up phone
      • Lock Bootloader

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

      • Important Note(s):
        1. If you want to Upgrade to Android 13 or update the Factory Image without wiping your phone and your phone is rooted. Open Magisk and delete all the modules or uninstall Magisk. Do Flash Factory Image Keep Data (below).
        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 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.
        4. If you phone bootloops
          • Press the Power button until the phone turns off.
          • Press the Power and Volume Down to boot the bootloader.
          • Open a Command Prompt in the SDK-Platform-tools folder or the folder that has adb.exe in it, and type adb wait-for-device shell magisk --remove-modules
          • fastboot Reboot
        5. Backup your data
        6. Download the latest Factory Image: Pixel 4a 5(G) - bramble to your Computer.
        7. Go to Part II - INSTRUCTIONS => 4. Extract Files from the FactoryImage/Flash boot.img and extract the flash-all.bat file.
      • Flash Factory Image Keep Data

        • Navigate to the folder you extracted the Factory Image to and open the flash-all.bat file with a file editor i.e., Notepad app and edit the flash-all.bat file:
          1. Change this line: fastboot -w update image-redfin-aa1a.999999.999.zip
          2. to this: fastboot update image-redfin-tp1a.999999.999.zip
          3. Note: This removes the -w so your Internal Storage will NOT be wiped.
          4. Add these lines after: PATH=%PATH%;"%SYSTEMROOT%\System32":
            fastboot --set-active=other
            fastboot reboot-bootloader
            ping -n 5 127.0.0.1 >nul
            but before:
            [/ICODE]fastboot flash bootloader bootloader-bramble-a9-9.9-9999999.img[/ICODE]
        • After, you have edited the flash-all.bat file. Copy/Move these files to the [U[Platform-tools[/U] folder:
          1. bootloader-bramble-....img
          2. flash-all.bat
          3. image-bramble-....zip
          4. radio-bramble-....img
        • On your phone: Boot the bootloader (Power off the phone => Press the Power and Down buttons until you see Start)
        • Connect your phone to the computer.
        • 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 Part II - INSTRUCTIONS => 5. Root/Reroot with Magisk and Pass SafetyNet, • Patching the boot.img - to root/reroot.
      • Flash Factory Image Wipe Data

        • 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
        • On your phone: Boot the bootloader (Power off the phone => Press the Power and Down buttons until you see Start)
        • Connect your phone to the computer.
        • 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 Part II - INSTRUCTIONS => 5. Root/Reroot with Magisk and Pass SafetyNet, • Patching the boot.img - to root/reroot.
    3. Take the OTA Update and Maintain Root

      • This set of instructions was written by @topjohnwu: Install Magisk to Inactive Slot , use the latest Magisk Canary, Beta or Stable.
      • NOTE: After you Open Magisk and Restore Images. If you had a Custom Kernel installed, Please check the OP of the Custom Kernel thread you install for the instruction to remove the Custom Kernel and return your phone to Stock. Additionally, if you had Mods installed, Please check the OP of the Mod thread you installed for instruction to remove the Mod and return your phone to Stock before you download the OTA.
      • If you phone bootloops
        • Press the Power button until the phone turns off.
        • Press the Power and Volume Down to boot the bootloader.
        • Open a Command Prompt in the SDK-Platform-tools folder or the folder that has adb.exe in it, and type adb wait-for-device shell magisk --remove-modules
        • fastboot Rebootp
    4. Extract Files from Factory Image/Flash boot.img

      • Extract Files from Factory Image

        1. Extract flash-all.bat and boot.img file
        2. Download the latest Factory image to your phone.
        3. Extract the Factory Image file (bramble-r2d1a.999999.999-factory-99a9a99a.zip) to a folder. The, stock, flash-all.bat file should be in this folder.
        4. Open the folder you extracted the Factory image to and, extract the Image file (image-bramble-aa9a.999999.999.zip) into the folder. The, stock, boot.img file should be in this 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
    5. Root/Reroot with Magisk and Pass SafetyNet.

      • Android 13

        • Upgrade to Android 13: OP, Part II - INSTRUCTIONS, 2. Install/Update Factory Image keep data or wipe data, Keep data
      • Patching the boot.img - to root/reroot.

        1. Go to Part II - INSTRUCTIONS => 4. Extract Files from the FactoryImage/Flash boot.img and extract the boot.img file.
        2. Install Magisk Canary - Download app-release.apk
          or
          Magisk Beta 25.0/Stable 24.3 App
        3. Open Magisk Beta/Canary/Stable App
        4. The Update Channel should be set to Beta/Canary/Stable, depending on the version you Installed.
        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/Move the patched boot.img file to your computer's Platform-tools folder or the folder that has fastboot.exe in it:
          • Copy it to a USB drive and transfer it to your computer.
          • Move it to your computer using adb push
        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: 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
          • Remove Modules
            1. Press the Power button until the phone turns off.
            2. Press the Power and Volume Down to boot the bootloader.
            3. Open a Command Prompt in the SDK-Platform-tools folder or the folder that has adb.exe in it, and type adb wait-for-device shell magisk --remove-modules
            4. fastboot Reboot.
      • Pass Safety Net with SafetyNet Fix

        1. Download File(s)
        2. Install Displax/safetynet-fix-v2.3.1-MOD_2.0.zip
          • Open Magisk
          • Tap Modules icon
          • Tap Install from storage
          • Navigate to the Displax/safetynet-fix-v2.3.1-MOD_2.0.zip file you downloaded
          • Tap the Displax/safetynet-fix-v2.3.1-MOD_2.0.zip file
          • Tap the check mark (✓ at the bottom) to start the installation.
          • Note: You do not have to disable/remove SafetyNet Fix.
          • After it installs tap the Save icon to save the log
          • Tap Reboot.
        3. Settings for Magisk Canary
          • 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.
          • Do not enable Denylist
          • Tap Configure DenyList => Tap 3 Dot Menu => Check ✓ Show system apps => Check ✓ Google Play Store, Google Pay, Google Wallet etc.
          • Scroll down to Superuser and enable Enable Biometric Authentication.
        4. Get Device Certified Clear Google Play Services, Google Play Store, Google Pay, Google Wallet, etc. data[/B]
          • 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, Google Wallet, etc.
          • reboot
          • Turn Airplane mode off
        5. Check Device Certification, I may take 24 hours for Device Certification
          • Open Google Play Store app
          • Tap Menu - Circle top right
          • Tap Settings
          • Tap About
          • Check Play protect certification.
    6. 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!
    7. Install/Update Magisk Modules

      • Download Modules
      • Install Modules from Storage

        1. Open Magisk
        2. Tap the Modules icon
        3. Tap Install from storage
        4. Navigate to the folder with the Module you want to install.
        5. Tap the Module to highlite it and tap Select.
        6. After it installs, tap the Disc Icon to save the install log.
        7. Tap Reboot
      • Install Modules from Fox2Code/Fox Magisk Module Manager

        1. Open Fox2Code/Fox Magisk Module Manager
        2. Tap the Modules icon
        3. Locate the Module you want to install
        4. Tap Install
        5. After it installs, tap the Disc Icon to save the install log.
        6. Tap Reboot
      • Update Modules

        1. Open Fox2Code/Fox Magisk Module Manager
        2. You, will see the Modules that have Updates.
        3. Tap the Module you want to update.
        4. Tap install.
        5. After it installs, tap the Disc Icon to save the install log.
        6. Tap Reboot
    8. 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.
    9. 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
      • 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.
    10. ADB Sideload

    ~ ~ ~ Part III - Other ~ ~ ~
    1. Custom ROMs

      • Need help with a Custom ROM?
        1. If you are you are trying to install or have installed a Custom ROM, read and follow the Installation Instructions in the OP of the Custom ROM thread.
        2. Search the thread of the Custom ROM you are trying to install or have installed for answer(s)/solution(s) to your question(s)/problem(s): If you don't find a answer(s)/solution(s) to your question(s)/problem(s). Post your question(s)/request(s) for help in the Custom ROM thread you are trying to install or have installed.
        3. If you are trying to install a Addon(s) {Custom Kernel, Magisk, etc.} to the Custom ROM you installed: Search the thread of the Custom ROM you installed or the thread of the Addon you want to add to your Custom ROMfor answer(s)/solution(s) to your question(s)/problem(s). If you don't find an answer(s)/solution(s) to your question(s)/problem(s). Post your question(s)/request(s) for help in the Custom ROM or Addon (Custom Kernel, Magisk, etc.) thread.
      • ROMs
    2. Mods
    3. T.W.R.P. Backup/Restore

      • Waiting for Android 13 T.W.R.P.
    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
    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!
    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.