[Guide] Root Pixel 4a (5G) with Magisk Android 12.1

Search This thread
By:
Advanced…
A

appro77

Senior Member
May 8, 2011
1,257
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?
 
H

Homeboy76

Senior Member
Aug 24, 2012
3,160
1,722
Google Pixel XL
appro77 said:
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?
Click to expand...
Click to collapse
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.
 
A

appro77

Senior Member
May 8, 2011
1,257
197
Mackay
Homeboy76 said:
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.
Click to expand...
Click to collapse
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?
 
H

Homeboy76

Senior Member
Aug 24, 2012
3,160
1,722
Google Pixel XL
appro77 said:
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?
Click to expand...
Click to collapse
It should be patched with the boot image from the latest factory image.
 
Last edited:
R

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

ballin2much

Member
Mar 3, 2014
10
1
Google Pixel 4a 5G
roundaway said:
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.
Click to expand...
Click to collapse
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
R

roundaway

Senior Member
Dec 9, 2009
217
33
USA
ballin2much said:
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.
Click to expand...
Click to collapse
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:
A

appro77

Senior Member
May 8, 2011
1,257
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?
 
A

appro77

Senior Member
May 8, 2011
1,257
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
 
H

Homeboy76

Senior Member
Aug 24, 2012
3,160
1,722
Google Pixel XL
appro77 said:
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
Click to expand...
Click to collapse
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:
A

appro77

Senior Member
May 8, 2011
1,257
197
Mackay
Homeboy76 said:
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)
Click to expand...
Click to collapse
Thanks.
 
B

ballin2much

Member
Mar 3, 2014
10
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?
 
H

Homeboy76

Senior Member
Aug 24, 2012
3,160
1,722
Google Pixel XL
ballin2much said:
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?
Click to expand...
Click to collapse
Did you wipe your phone the first time you installed Android 12 on your Pixel 4a 5(G) phone?
 
You must log in or register to reply here.

Similar threads

L
Module to enable 5G/VoLTE/VoWIFI on Pixel4a 5G/Pixel5
Replies
104
Views
36K
F
fuadhdmini
drdionysius
Updating your rooted Pixel 4a 5G on Windows
Replies
54
Views
9K
K
kokofrank
T
  • Locked
[CLOSED][SHARE] Lineage 18, Android 11 for Pixel 4a Sunfish
Replies
50
Views
10K
Macusercom
Macusercom
V0latyle
[GUIDE] Pixel 4a (5G) "bramble": Unlock Bootloader, Update, Root, Pass SafetyNet
Replies
74
Views
6K
Z
zubblwump
V
Howto - Root your bramble with Magisk
Replies
97
Views
12K
A
angrox

Top Liked Posts

24 Hours 30 Days All time
  • There are no posts matching your filters.
  • 1
    H
    Homeboy76
    zubblwump said:
    So currently no root on phone. ADB/Fastboot not available. Is there any way to reboot to inactive slot without root or PC to send commands? Any way to flash modified boot image?
    Click to expand...
    Click to collapse
    If there is a way to flash a modified boot.img, I don't know how to do it.
    View
  • 23
    H
    Homeboy76
    [Guide] Root Pixel 4a (5G) with Magisk Android 12.1
    Android Security Bulletin—May 2022
    Pixel Update Bulletin—May 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

      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.
    2. 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: r33.0.1 installed.
      4. Important Notes:
        a. Update Platform Tools, regularly, for optimal performance.​
    3. Update(s)

      1. Factory/OTA Images - 02May
      2. Magisk Alpha - 71e9c044-alpha 06May
      3. Magisk Beta - 24.3 10Mar
      4. Magisk Canary - (756d8356) (24312) 15May
      5. Magisk Stable - 24.3 10Mar
      6. TWRP - Waiting for T.R.W.P. for Android 12
      7. SafetyNet - SafetyNetFix v2.1.3 (Riru) v2.2.1 (Zygisk) 22Dec
      8. SDK Platform-tools - r33.0.1 06Apr
      9. Custom Kernels
      10. Custom ROMs
        a. ProtonAOSP[12] 01Nov​
        c. [ROM] [UNOFFICIAL] LineageOS 19.0 - microG Edition 18Dec​
        d. [ROM][12][bramble] PixelExperience [AOSP][OFFICIAL]​
    4. NEW

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

      1. @creezalird- Flash Android 12 factory image.
      2. Those I may have, inadvertently, forgotten.
    ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~
    1. 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.
        10. 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.
    2. Install/Update Factory Image keep data or wipe data

      • Important Note(s):
        1. When doing a Major Upgrade Android 12 (12.0.0) to Android 12.1 (12.1.0), I recommend doing a Clean Install: Do Flash Factory Image Wipe 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
          • force Safe Mode by continually pressing volume down button during boot animation.
          • After the system boots into safe mode you can reboot your device to boot up normally (since all modules will be disabled).
          • Thanks @Typhus_ for the instructions to force Safe Mode.
        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

        • 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 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
        • 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

      • All the credit for this set of instructions goes to @topjohnwu for writing the instructions: Install Magisk to Inactive Slot , use Magisk Beta, Stable 24.3.
      • NOTE: If you had a Custom Kernel installed, after you Open Magisk and Restore Images. Do the following to return your phone to Stock:
        • fastboot flash dtbo dtbo.img
        • fastboot flash vendor_boot vendor_boot.img
        • There may be more .img files you need to flash. Please check the OP of the Custom Kernel thread you install for instruction to remove the Custom Kernel and return your phone to Stock. Additionally, if you installed Mods 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
        • force Safe Mode by continually pressing volume down button during boot animation.
        • After the system boots into safe mode you can reboot your device to boot up normally (since all modules will be disabled).
        • Thanks @Typhus_ for the instructions to force Safe Mode.
    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 12

        • Upgrade to Android 12: 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
          Note: Tap 3 dot menu across from canary => Download, app-debug.apk
          or
          Magisk 24.1 Beta/Stable App - Under Downloads
        3. Open Magisk Beta/Canary/Stable App
        4. Set the Update Channel Beta/Canary/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/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 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.1

        1. Download File(s)
        2. Install SafetyNet Fix 2.2.1
          • 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
          • 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.
    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

        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
      • Update Modules

        1. Open Magisk
        2. Tap the Modules icon
        3. You, will see the Modules that have Updates.
        4. Tap the Module you want to update.
        5. Tap install.
        6. After it installs, tap the Disc Icon to save the install log.
        7. 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

    2. Mods
    3. T.W.R.P. Backup/Restore

      • Waiting for Android 12 T.W.R.P.
    View
    3
    H
    Homeboy76
    thomas.raines said:
    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?
    Click to expand...
    Click to collapse
    :( 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.
    View
    3
    H
    Homeboy76
    lu270bro said:
    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
    Click to expand...
    Click to collapse
    - 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
    View
    3
    H
    Homeboy76
    dlewando said:
    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
    Click to expand...
    Click to collapse
    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!
    View
    2
    gladi8r
    gladi8r
    lu270bro said:
    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
    Click to expand...
    Click to collapse

    You need Universal Safetynet fix v 1.1.1 Magisk module.
    View

New posts