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

Search This thread
By:
Advanced…
A

alkhaled

Member
Apr 17, 2023
5
0
How to solve this problem in the developer options The OEM Unlocking option is closed (connect to the internet or contact your carrier)
 
A

alkhaled

Member
Apr 17, 2023
5
0
please help me How to solve this problem in the developer options The OEM Unlocking option is closed (connect to the internet or contact your carrier)
 
Last edited:
H

Homeboy76

Recognized Contributor
Aug 24, 2012
4,133
2,511
Google Pixel 7 Pro
alkhaled said:
How to solve this problem in the developer options The OEM Unlocking option is closed (connect to the internet or contact your carrier)
Click to expand...
Click to collapse

alkhaled said:
please help me How to solve this problem in the developer options The OEM Unlocking option is closed (connect to the internet or contact your carrier)
Click to expand...
Click to collapse

alkhaled said:
I did all the steps mentioned in the post, but I did not succeed in unlocking the bootloader or oem
Click to expand...
Click to collapse

@badabing2003 is correct if your carrier locked the carrier or the bootloader, only they can unlock it. When you get the bootloader unlocked, you can enable OEM Unlocking.
 
Last edited:
H

Homeboy76

Recognized Contributor
Aug 24, 2012
4,133
2,511
Google Pixel 7 Pro
OP Changes
I added additional notes to the OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~,
5. Root/Reroot with Magisk and Pass SafetyNet.,
• Patching the boot/init_boot.img - to root/reroot.,
1 & 2.
 
J0kker

J0kker

Senior Member
Mar 15, 2012
438
202
Amazon Fire TV
Google Pixel 4a 5G
badabing2003 said:
On the download page, switch the language to English and you would see it.
I don't know why but April release doses not show up on many other languages.
Click to expand...
Click to collapse
I've just spent the last 4 hours to try to get out of a boot-loop from May update, no way to flash back the latest available fullf irmware from french page (february) without full wipe, but sideloading the may OTA (which is available in the french page) would result in a booting phone, but no way to get magisk/root, even trying with a payload.bin dump to get the boot.img from OTA zip !
Thanks for pointing out that the full firmware is available in english page... could have searched a few more hours... or maybe got mad and flash a custom rom 🙃
Downloading the full may firmware right now and let's hope patching the boot.img from that file will do the magic 🤞
 
badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
3,036
4,694
J0kker said:
I've just spent the last 4 hours to try to get out of a boot-loop from May update, no way to flash back the latest available fullf irmware from french page (february) without full wipe, but sideloading the may OTA (which is available in the french page) would result in a booting phone, but no way to get magisk/root, even trying with a payload.bin dump to get the boot.img from OTA zip !
Thanks for pointing out that the full firmware is available in english page... could have searched a few more hours... or maybe got mad and flash a custom rom 🙃
Downloading the full may firmware right now and let's hope patching the boot.img from that file will do the magic 🤞
Click to expand...
Click to collapse
If extracting boot.img from OTA that you flashed, and creating a patch from it is giving your problems, then your problems are not with firmware.
Explain exactly what is happening.
 
J0kker

J0kker

Senior Member
Mar 15, 2012
438
202
Amazon Fire TV
Google Pixel 4a 5G
badabing2003 said:
If extracting boot.img from OTA that you flashed, and creating a patch from it is giving your problems, then your problems are not with firmware.
Explain exactly what is happening.
Click to expand...
Click to collapse
So here i am, after extracting boot.img from the full firmware, i compared the MD5 checksum and noticed it was the same as the one i dumped from payload.bin, so the resulat was the same, obviously.
So i simply replaced Magisk Delta which i was using for some time now, and switched to Magisk Canary as it is advised in OP, patched my boot.img with it and all went fine... So all my troubles were because of a wrong magisk fork :)
 
  • Like
Reactions: Homeboy76 and badabing2003
H

Homeboy76

Recognized Contributor
Aug 24, 2012
4,133
2,511
Google Pixel 7 Pro
SDK Platform-tools Update
SDK Platform-tools r. 34.0.3, was released May 22, 2023.

@badabing2003 reported a problem when using it.
https://forum.xda-developers.com/t/...7-pro-cheetah-safetynet.4502805/post-88571575

@Lughnasadh, suggested a fix.
https://forum.xda-developers.com/t/...7-pro-cheetah-safetynet.4502805/post-88571601

@badabing2003, confirmed the suggested fix works.
https://forum.xda-developers.com/t/...7-pro-cheetah-safetynet.4502805/post-88571617

If you use Linux or Windows SDK Platform- tools r. 34.0.3. You must set the environment variable:
Linux

Windows

Note: If you have any problems with SDK Platform-tools 34.0.3. You can get SDK Platform-tools 33.0.3 here.
 
Last edited:
  • Like
Reactions: Lughnasadh and badabing2003
saecv

saecv

New member
May 28, 2023
1
0
badabing2003 said:
This is typically due to multiple Magisk managers being installed, if at any point, Magisk Manager was hidden, and then another Magisk manager was installed, you'd face issues as this.
@dadnammit you should first do is, uninstall all Magisk managers, hopefully you can find the hidden one, or at least you know the package name, if you did not rename the application when you hid, then it should be named settings.
If you have already applied patched boot, then reboot and just install Magisk Manager. and it should detect root.
You can confirm that you're rooted by doing
Code: 
adb shell
su
if you get su, you're rooted.

If you are on stock, then just install Magisk Manager and flash the patched boot.
Whatever you do make sure you only have a single instance of Magisk manager.
Click to expand...
Click to collapse
thanks
 
You must log in or register to reply here.

Similar threads

V0latyle
[GUIDE] Pixel 4a (5G) "bramble": Unlock Bootloader, Update, Root, Pass SafetyNet
Replies
123
Views
20K
V0latyle
V0latyle
L
Module to enable 5G/VoLTE/VoWIFI on Pixel4a 5G/Pixel5
Replies
124
Views
68K
zirack
zirack
drdionysius
Updating your rooted Pixel 4a 5G on Windows
Replies
55
Views
12K
drdionysius
drdionysius
V
Howto - Root your bramble with Magisk
Replies
97
Views
14K
A
angrox
T
  • Locked
[CLOSED][SHARE] Lineage 18, Android 11 for Pixel 4a Sunfish
Replies
50
Views
11K
Macusercom
Macusercom

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 23
    H
    Homeboy76
    [Guide] Root Pixel 4a (5G) with Magisk + Unlock Bootloader + Pass SafetyNet + More
    Android Security Bulletin—September 2023
    Pixel Update Bulletin—September 2023    ​

    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.
      • If you choose to use a Custom Kernels, Custom ROM, etc. You should read the Installation Instructions in their thread before using this guide or attempting to install them. Additionally, 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 them.
    2. Prerequisites

    3. NEW

      • Patching the boot.img using the image...zip file extracted from the Google Factory image file and Magisk. (see - OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~, 2., 3., or 4.)
    4. Update(s)

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

      • @topjohnwu - Magisk.
      • @badabing2003 - Creating Pixel Flasher, discovering how to make both slots bootable, and for his many helpful contributions to this thread.
      • @Lughnasadh - for testing badabing2003 make both slots bootable, and his many helpful contributions to this thread.
      • @Shoey - for discovering and testing patching the boot.img using the image...zip file extracted from the Google Factory image file and Magisk.
      • 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. Use the Android flash tool:
          select Wipe => Force Flash Partitions => Lock Bootloader.
      • Lock Bootloader

        1. If your phone is not 100 percent stock do Return Phone to Stock. If you don't you may brick your phone.
        2. This will erase all user data from the device!
        3. Boot fastboot mode
        4. Open a Command Prompt in the SDK Platform- tools folder, 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. Manually Install/Update Factory Image keep data or wipe data

      • Important Note(s):
        1. If you haven't updated your phones Factory image in a while. It is not necessary to flash all the missed images in succession. Flash the latest Factory image.
        2. If your phone was previously rooted, open Magisk manager and disable all Magisk modules. If you hid the Magisk manager app the default name for the hidden Magisk app is settings.
        3. Always verify you have the latest working version of SDK Platform-Tools installed on your computer.
        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. If your phone boot loops try one of the following options:
          • Flash the 'stock' boot.img to both slots to remove root: fastboot flash init_boot boot.img --slot all
          • Boot Safe Mode to remove Magisk Modules
            1. When booting, press and hold your phone's volume down button. Keep holding it until the animation ends and your phone starts in safe mode.
            2. Then reboot and magisk modules should be disabled. (Thanks Lughnasadh)
          • Boot fastboot mode to remove Magisk Modules
            1. Press the Power button until the phone turns off.
            2. Press the Power and Volume Down to boot fastboot mode.
            3. Open a Command Prompt in the 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
        6. Backup your data
        7. Download the latest Factory Image: Pixel 4a5(G) - bramble to your Computer.
        8. Go to Part II - INSTRUCTIONS => 5. Extract files from the Factory Image.
      • Flash Factory Image Keep Data

        • Upgrading Android 13
          * E D I T - flash-all.bat file *
          Flash to current/Active Slot.
          @Echo off
          PATH=%PATH%;"%SYSTEMROOT%\System32"
          fastboot flash bootloader bootloader-bramble bramble-aaaaaa-9.9-9999999.img
          fastboot reboot-bootloader
          ping -n 5 127.0.0.1 >nul
          fastboot flash radio radio-bramble bramble-a9999a-999999-999999-a-9999999.img
          fastboot reboot-bootloader
          ping -n 5 127.0.0.1 >nul
          fastboot update image-bramble-aa9a.999999.999.zip
          Note:The -w is removed to Keep Data.
          echo Press any key to exit...
          pause >nul
          exit
          Note: It is a good idea to flash the Google factory image to both slots (A & B) when Upgrading to a new Android Version.
          See Flash Other Slot bat file... below, to flash to the other/inactive slot.
          * * * * E N D - Edit * * * *
        • Updating Android 13
          Flash to Other/Inactive Slot.
          Note: See Flash Other Slot bat file... below.
          * * * * * E N D * * * * *
        • Flash Other Slot bat file - Save as flash-other.bat
          Note: To run this file type flash-other at the Command Prompt.
          ECHO OFF
          PATH=%PATH%;"%SYSTEMROOT%\System32"
          echo This is the slot you are currently on.
          fastboot getvar current-slot
          echo Press any key to continue...
          pause >nul
          fastboot --set-active=other
          fastboot reboot-bootloader
          ping -n 5 127.0.0.1 >nul
          echo This is the slot you switched to.
          fastboot getvar current-slot
          echo Press any key to continue...
          pause >nul
          flash-all
          exit
          * * E N D - Creating File * *
        • 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 completed.
        • Go-to Part II - INSTRUCTIONS => 6. 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 Data/Internal Storage.
        • Do not edit the flash-all.bat file.
        • If you need to disable Verity and Verification: See Disabling Verity and Verification below.
          Disabling Verity and Verification
          * E D I T - flash-all.bat file *
          @Echo off
          PATH=%PATH%;"%SYSTEMROOT%\System32"
          fastboot --set-active=other
          fastboot reboot-bootloader
          fastboot flash bootloader bootloader-bramble-aaaaaa-9.9-9999999.img
          fastboot reboot-bootloader
          ping -n 5 127.0.0.1 >nul
          fastboot flash radio radio-bramble-a99999-999999-999999-a-9999999.img
          fastboot reboot-bootloader
          ping -n 5 127.0.0.1 >nul
          fastboot - w update --disable-verity --disable-verification image-bramble-AA1A.999999.999.A9.zip
          echo Press any key to exit...
          pause >nul
          exit
          Notes:
          1. The first time you Disable Verity and Verification it will wipe your Data/Internal Storage.
          2. When doing Subsequent updates and disabling Verity and Verification, the -w flag can be removed to Keep Data.
          3. Once you start Disabling Verity and Verification you should continue doing it. If you skip disabling one time. The next time you Disable Verity and Verification it will wipe your phone.
          4. Some kernels require Disabling verity and verification
          5. To flash the Factory image to both slots (A & B) see Flash Other Slot bat file... above.
          * * * * E N D - Edit * * * *
        • 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 until you see you are a 'Devloper'.
          2. Setup => System => Developer options => Enable Developer options => enable USB Debugging
        • Go-to Part II - INSTRUCTIONS => 6. Root/Reroot with Magisk and Pass SafetyNet, • Patching the boot.img - to root/reroot.
      • If you are uncomfortable manually flashing the factory image, use PixelFlasher by @badabing2003
    3. (NEW) Manually Install/update the OTA image keep data and root/re-root your phone

      • Important Note(s):
        1. If you haven't updated your phones OTA image in a while. It is not necessary to flash all the missed OTA images in succession. Flash the latest OTA image.
        2. If your phone was previously rooted, open Magisk manager and disable all Magisk modules. If you hid the Magisk manager app the default name for the hidden Magisk app is settings.
        3. Always verify you have the latest working version of SDK Platform-Tools installed on your computer.
        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. If your phone boot loops try one of the following options:
          • Flash the 'stock' boot.img to both slots to remove root: fastboot flash boot boot.img --slot all
          • Boot Safe Mode while booting to remove Magisk Modules
            1. When booting, press and hold your phone's volume down button. Keep holding it until the animation ends and your phone starts in safe mode.
            2. Then reboot and magisk modules should be disabled. (Thanks Lughnasadh)
          • Boot fastboot mode by turning phone off to remove Magisk Modules
            1. Press the Power button until the phone turns off.
            2. Press the Power and Volume Down to boot fastboot mode.
            3. Open a Command Prompt in the 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
        6. Backup your data
        7. Download the latest OTA Image: Pixel 6 - bramble to your Computer.
      • Patch the boot.img

        • Open Magisk (next to Magisk)
        • Tap Install
        • Tap Select and patch a file
        • Navigate to the Google OTA.zip file
        • Tap it then tap the check mark (✓)
        • Tap Lets go
        • When you see done the boot.img has been patched (magisk_patched_xxxxxx.img), and stored in the download folder.
        • Tap the disc icon (upper right corner) to save the log file.
        • Reboot
        • Copy/Move the magisk_patched_xxxxxx.img file to your computer's Platform-tools folder, the folder that has fastboot.exe in it:
          1. Copy it to a USB drive and transfer it to your computer.
          2. Move it to your computer using adb push
      • Sideload the Google OTA image file and Root it

        1. With the device powered on, booted, USB debugging enabled, and the phone connected to the computer. Type adb reboot sideload
        2. Type:
          adb sideload bramble-ota-aa9a.999999.999-aaaa9999.zip at the command prompt and press Enter.
        3. When sideloading finishes, type adb reboot bootloader at the command prompt and press Enter.
      • Root this slot - Flash the Magisk_patched....img

        1. Type: fastboot flash boot magisk_patched-99999_aA99a.img at the command prompt and press Enter.
        2. When it finishes flashing, type fastboot reboot at the command prompt and press Enter.
        3. Disconnect the phone from the computer.
        4. Note: This slot is bootable and rooted.
    4. (NEW) Make Both Slots Bootable: Manually, Flash the OTA Image to Both Slots - One bootable and rooted, the other slot bootable without root.

      • Before you start

        1. On the Phone
          • Backup your data
          • Make sure that there is no pending OTA update, by going to Settings > About phone > System updates, which should say Your system is up to date.
          • Download the latest OTA image for your device.
          • Verify the checksum of the OTA image. The last portion of the filename is the first 8 digits of its SHA-256 checksum; the full SHA-256 checksum is shown next to the download link.
          • Patch the boot.img:
            1. Note: Before patching the boot.img disable all Magisk modules.
            2. Open the Magisk (Alpha/Beta/Canary/Delta/Stable) App and set the Update Channel to the version of Magisk app you installed.
            3. Open Magisk (next to Magisk)
            4. Tap Install
            5. Tap Select and patch a file
            6. Navigate to the Google OTA.zip file
            7. Tap it then tap the check mark (✓)
            8. Tap Lets go
            9. When you see done, the boot.img has been patched (magisk_patched_xxxxxx.img), and is stored in the download folder.
            10. Tap the disc icon (upper right corner) to save the log.
            11. Tap Reboot
            12. Copy/Move the magisk_patched....img file to your computer's Platform-tools folder or the folder that has fastboot.exe in it.
            13. Connect the phone to the computer.
        2. On your Computer
          • Enable Developer Options: Tap Settings > About Phone > Tap Build Number 7 times or until you see you are a Developer.
          • Enable USB Debugging: Tap Settings > System > Advanced > Developer Options. Enable USB Debugging.
          • Open a Command Prompt in the Platform-tools folder.
      • (Optional): Verify your computer sees your device.

        1. With the device powered on, booted, USB debugging enabled, and the phone connected to the computer.
          Note: If you see the Allow USB Debugging prompt when you connect the phone to the computer, Tap Allow.
        2. Type adb devices at the command prompt and press Enter. You should see your device's serial number.
      • Sideload the Google OTA image file

        1. With the device powered on, booted, USB debugging enabled, and the phone connected to the computer.
          Note: If you see the Allow USB Debugging prompt when you connect the phone to the computer, Tap Allow.
        2. Type adb reboot sideload at the command prompt and press Enter.
        3. Type: adb sideload bramble-ota-aa9a.999999.999-aaaa9999.zip at the command prompt and press Enter.
        4. When sideloading finishes, type adb reboot at the command prompt and press Enter.
        5. Note: This slot is bootable and not rooted
      • Sideload the Google OTA image file to the other slot and Root it.

        1. With the device powered on, booted, USB debugging enabled, and the phone connected to the computer. Type adb reboot sideload
        2. Type:
          adb sideload bramble-ota-aa9a.999999.999-aaaa9999.zip at the command prompt and press Enter.
        3. When sideloading finishes, type adb reboot bootloader at the command prompt and press Enter.
        Root this slot - Flash the Magisk_patched....img
        1. Type: fastboot flash boot magisk_patched-99999_aA99a.img at the command prompt and press Enter.
        2. When it finishes flashing, type fastboot reboot at the command prompt and press Enter.
        3. Disconnect the phone from the computer.
        4. Note: This slot is bootable and rooted.
        5. Done! :)
    5. Extract files from the Factory Image

      1. Download the latest Factory image to your phone.
      2. Extract the Factory Image file (cheetah-a9a9a.999999.999-factory-99a9a99a.zip) to a folder. The, stock, flash-all.bat file should be in this folder.
      3. Open the folder you extracted the Factory image to and extract the Image file (image-cheetah-aa9a.999999.999.zip) into the folder. The flash-all bat and, the stock boot.img file should be in this folder.
    6. 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. Important Notes
          • If your phone was previously rooted, DO NOT repeat DO NOT install another Magisk Manager app. Do this before you patch the boot.img:
            1. Open the Magisk Manager app and disable all Magisk modules.
            2. If you hid the Magisk manager app the default name for the hidden Magisk app is settings. If you gave it a different name and you've forgotten the name. Use TB checker to find the name of the hidden Magisk Manager:
              • Open the TB Checker app
              • Tap Run Xposed check
              • Scroll down to Magisk Random Package Name: to see Magisk's hidden name.
                You can also use TB Checker to check if you have more than one Magisk Manager app installed.
          • If your phone boot loops try one of the following options:
            • Flash the 'stock' boot.img to both slots to remove root: fastboot flash boot boot.img --slot all
            • Remove Magisk Modules
              1. Boot Safe Mode
                • When booting, press and hold your phone's volume down button. Keep holding it until the animation ends and your phone starts in safe mode.
                • Then reboot and magisk modules should be disabled. (Thanks Lughnasadh)
              2. Command Prompt
                • Press the Power button until the phone turns off.
                • Press the Power and Volume Down to boot fastboot mode.
                • Open a Command Prompt in the Platform-tools folder or the folder that has adb.exe in it, and type adb wait-for-device shell magisk --remove-modules
                • fastboot Reboot.
          • If the Magisk Manager app has the Superuser and Module buttons grayed out: Read @badabing2003 post
        2. Extract the image-bramble-aa9a.999999.999.zip file from the Factory Image.
          • Download the latest Factory image to your phone.
          • Extract the Factory Image file (bramble-a9a9a.999999.999-factory-99a9a99a.zip) to a folder.
          • Open the folder you extracted the Factory image to, the Image file (image-bramble-aa9a.999999.999.zip) file should be in this folder[/U].
        3. Install Magisk Canary - Download app-release.apk
          or
          Magisk Beta/Stable App
        4. Open Magisk Beta/Canary/Stable App
        5. The Update Channel should be set to Beta/Canary/Stable, depending on the version you Installed.
        6. Tap Install (next to Magisk)
        7. Tap, Select and Patch a File
        8. Select the image-bramble-aa9a.999999.999.zip file you extracted from the latest factory image.
        9. Tap the ✓ (Check Mark)
        10. Tap Let's Go
        11. When you see done the boot.img has been patched (magisk_patched_xxxxxx.img), and stored in the download folder.
        12. Tap the disc icon (upper right) to save the log file.
        13. Reboot
        14. Copy/Move the magisk_patched_xxxxxx.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
        15. Boot fastboot mode
        16. Connect the phone to the Computer with USB cord.
        17. Open a Command Prompt in the Platform-tools folder.
        18. Type fastboot flash boot "magisk_patched...img" (name of patched.img file) without the quote marks at the Prompt and press enter.
        19. Type fastboot reboot at the Prompt and press enter.
      • Pass Safety Net with SafetyNet Fix

        1. Download File(s)
        2. Install Displax's safetyNet Fix
          • Open Magisk
          • Tap Modules icon
          • Tap Install from storage
          • Navigate to the Displax's SafetyNet Fix file you downloaded.
          • Tap the Displax's SafetyNet Fix 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.
          • Enable Denylist
          • Tap Configure DenyList => Tap 3 Dot Menu => Check ✓ Show system apps => Check ✓ Google Play Store, Google Pay, Google Wallet etc.
          • (Optional) Scroll down to Superuser and enable Enable Biometric Authentication.
        4. Get Device Certified
          • Turn Airplane mode on
          • Open Settings
          • Tap Apps & notifications
          • Tap see all...
          • Tap three dot menu
          • Tap Show system
          • Scroll to Google Play Store
          • Tap Storage and Cache
          • Tap Clear storage
            Note: Repeat the 3 steps above for any app that needs Device Certification i.e., Google Play Services, Google Pay, Google Wallet, 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
          • It may take 24 hours for Device Certification to be updated.
        6. Note: If after completeting Get Device Certified and Check Device Certification you've waited 24 hours your Device is not Certifed or your Device is Certified and certain Google Store apps (Google Pay, NetFliks, etc.) are not working. Use the Play Integrity API Checker app or the TB Checker - Safetynet and Root app to verify you are passing Play Integrity.
    7. 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!
    8. Install/Update Magisk Modules

    9. 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.
    10. 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.
    11. 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
        1. Google Pixel 4a5(G) ROMs, Kernels, Recoveries, & Other
        2. Other Custom ROMs
    2. Themes, Apps, and Mods
    3. T.W.R.P. Backup/Restore

      • Waiting for Android 13 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
    badabing2003
    badabing2003
    Homeboy76 said:
    Uninstalling and reinstalling the Magisk Manager apps should have fixed the superuser and module buttons greyed out problem.

    Maybe @badabing2003 can help you use the Pixel Flasher tool to fix the superuser and module buttons greyed out problem.
    Click to expand...
    Click to collapse
    This is typically due to multiple Magisk managers being installed, if at any point, Magisk Manager was hidden, and then another Magisk manager was installed, you'd face issues as this.
    @dadnammit you should first do is, uninstall all Magisk managers, hopefully you can find the hidden one, or at least you know the package name, if you did not rename the application when you hid, then it should be named settings.
    If you have already applied patched boot, then reboot and just install Magisk Manager. and it should detect root.
    You can confirm that you're rooted by doing
    Code: 
    adb shell
su
    if you get su, you're rooted.

    If you are on stock, then just install Magisk Manager and flash the patched boot.
    Whatever you do make sure you only have a single instance of Magisk manager.
    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

New posts