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

[Guide] Root Pixel 4 XL Android 12

Search This thread

madmuthertrucker

Senior Member
Jan 4, 2013
195
75
Tucson, Az
I installed 12 and I can't pass safteynet to save my life. What am I doing wrong? I tried every version of Magisk there is. I passed it for a second and then it failed a minute later.
 

bradical711

Senior Member
Aug 26, 2017
431
267
Google Pixel 4 XL
@madmuthertrucker

Link To Universal Safetynet Fix Thread

You need the "universal safetynet fix" magisk module. XDA thread link is posted above, actual download is hosted on GitHub.

In order to install the "universal safetynet fix" module in magisk though, you'll also need to install the "riru" module. You can find the "riru" module in magisk's repo by searching for "riru". Finally, you'll need to enable magisk hide for Google Play Services, specifically only "com.google.android.gms" & "com.google.android.gms.unstable" need to be ticked. Afterwards, reboot and you should be passing safetynet. Once you're passing safetynet again, don't forget to clear the data for Google Play Store as well and reboot a 2nd time. That'll make sure the Google Play Store certifies your device as "official" in the Play Store after you start passing safetynet again. Optionally, hiding the magaisk manager itself isn't necessary in passing safetynet, but can help you with accessing mobile versions of banking apps, (gpay) etc.
 
Last edited:
  • Like
Reactions: madmaverickmatt

madmuthertrucker

Senior Member
Jan 4, 2013
195
75
Tucson, Az
@madmuthertrucker

Link To Universal Safetynet Fix Thread

You need the "universal safetynet fix" magisk module. XDA thread link is posted above, actual download is hosted on GitHub.

In order to run the "universal safetynet fix" module in magisk though, you'll also need to install the "riru" module. You can find the "riru" module in magisk's repo by searching for "riru". Finally, you'll need to enable magisk hide for Google Play Services, specifically only "com.google.android.gms" & "com.google.android.gms.unstable" need to be ticked. Afterwards, reboot and you should be passing safetynet. Once you're passing safetynet again, don't forget to clear the data for Google Play Store as well and reboot a 2nd time. That'll make sure the Google Play Store certifies your device as "official" in the Play Store after you start passing safetynet again. Optionally, hiding the magaisk manager itself isn't necessary in passing safetynet, but can help you with accessing mobile versions of banking apps, (gpay) etc.
I followed your instructions to the letter and it worked just fine! No problems. It was almost to easy. I have been over complicating it. I'm following Safetynet Fix thread now. Thanks for the help.
 
  • Like
Reactions: bradical711

bradical711

Senior Member
Aug 26, 2017
431
267
Google Pixel 4 XL
I'm passing Safetynet and device is certified. But GPay is still fighting me. Did any of you guys get it working?
I can access gpay just fine on A12. I have it installed and just checked myself. I'm passing safety net myself and have the magisk app hidden (renamed). What do you mean by gpay fighting you.? Does it happen when making a purchase or just opening the app on A12.? I had gpay on A11 and it worked fine for me when I used it. Upgraded to 12 via OTA, no change in my setup and I can access it still. I haven't tried to make a purchase with it yet though.
 

madmuthertrucker

Senior Member
Jan 4, 2013
195
75
Tucson, Az
I can access gpay just fine on A12. I have it installed and just checked myself. I'm passing safety net myself and have the magisk app hidden (renamed). What do you mean by gpay fighting you.? Does it happen when making a purchase or just opening the app on A12.? I had gpay on A11 and it worked fine for me when I used it. Upgraded to 12 via OTA, no change in my setup and I can access it still. I haven't tried to make a purchase with it yet though.
I did a clean install from A11 to 12. I can sign into GPay but I can't add payment card. If I open wallet it says "Unable to load your payment info". The first time it said this may be because your device is rooted. I selected GPay in MagiskHide. I also renamed Magisk. I cleared cache and storage but I still can't add payment cards. That has always been my test, after clearing storage usually it asks me to re add payment cards. I cleared storage force stop and this is what pops up.

Google Pay can't be used on
this device
Sorry, your device isn't passing Google Pay's security checks. This may be because your device is rooted, or is running an uncertified or custom 0S build.
As a result, Google can't confirm that your device meets Google Pay's security standards.
 
Last edited:

bradical711

Senior Member
Aug 26, 2017
431
267
Google Pixel 4 XL
I did a clean install from A11 to 12. I can sign into GPay but I can't add payment card. If I open wallet it says "Unable to load your payment info". The first time it said this may be because your device is rooted. I selected GPay in MagiskHide. I also renamed Magisk. I cleared cache and storage but I still can't add payment cards. That has always been my test, after clearing storage usually it asks me to re add payment cards. I cleared storage force stop and this is what pops up.

Google Pay can't be used on
this device
Sorry, your device isn't passing Google Pay's security checks. This may be because your device is rooted, or is running an uncertified or custom 0S build.
As a result, Google can't confirm that your device meets Google Pay's security standards.
Interesting... If I go to gpay and open wallet I get no error message. I also tried adding another card and was able to do so with no issue either.... I've never had to add gpay to magisk hide so I know that's not it. You said you were passing safetynet as well as Play Store Certified along with magisk hidden so my last guess would be to ask if you have any variant of Xposed installed (Edxposed or LSposed). I think having Edxposed would trigger gpay since it hooks all apps unless you have specifically excluded gpay itself in Edxposed 'blacklist'. I'm not sure what else it could be though cause you pass all the other checks for gpay. Maybe and I mean maybe, it could be a TWRP folder/leftover magisk files in /sdcard/ ... No idea otherwise if none of those are it though.
 
Last edited:

madmuthertrucker

Senior Member
Jan 4, 2013
195
75
Tucson, Az
Interesting... If I go to gpay and open wallet I get no error message. I also tried adding another card and was able to do so with no issue either.... I've never had to add gpay to magisk hide so I know that's not it. You said you were passing safetynet as well Play Store Certified along with magisk hidden so my last guess would be to ask if you have any variant of Xposed installed (Edxposed or LSposed). I think having Edxposed would trigger gpay since it hooks all apps unless you have specifically excluded gpay itself. I'm not sure what else it could be though.
Well now I checked & I'm failing Safetynet. I'm still Play certified. I'm running LSPosed, XPrivacyLua. Just like in the guide. I don't get why I originally passed SafetyNet and now I don't. I'm going to start over with a clean install I guess. I'm running Canary. I'm at a loss.
 

bradical711

Senior Member
Aug 26, 2017
431
267
Google Pixel 4 XL
Well now I checked & I'm failing Safetynet. I'm still Play certified. I'm running LSPosed, XPrivacyLua. Just like in the guide. I don't get why I originally passed SafetyNet and now I don't. I'm going to start over with a clean install I guess. I'm running Canary. I'm at a loss.
Hmmm, I double checked my safetynet and I'm still passing with the same setup. I double checked with 'root checker' app and magisk alike. I'm running stable version 23 of magisk along with 9 modules. None of which include the Xposed variants. Maybe try again with the clean install but don't install LSposed/xprivacylua. First work on passing safetynet again with just those 2 modules you need, and then we can go through the process of elimination.
 

madmuthertrucker

Senior Member
Jan 4, 2013
195
75
Tucson, Az
Hmmm, I double checked my safetynet and I'm still passing with the same setup. I double checked with 'root checker' app and magisk alike. I'm running stable version 23 of magisk along with 9 modules. None of which include the Xposed variants. Maybe try again with the clean install but don't install LSposed/xprivacylua. First work on passing safetynet again with just those 2 modules you need, and then we can go through the process of elimination.
That's a good idea. I was passing Safetynet with just Riru & Safetynet Fix. Okay I'm going to try it.
 

madmuthertrucker

Senior Member
Jan 4, 2013
195
75
Tucson, Az
Hmmm, I double checked my safetynet and I'm still passing with the same setup. I double checked with 'root checker' app and magisk alike. I'm running stable version 23 of magisk along with 9 modules. None of which include the Xposed variants. Maybe try again with the clean install but don't install LSposed/xprivacylua. First work on passing safetynet again with just those 2 modules you need, and then we can go through the process of elimination.
Okay just for giggles I uninstalled LSPosed, XPrivacyLua and I'm passing Safetynet again now. Still not able to add payment to GPay. So you were right about that module being the culprit.
 

bradical711

Senior Member
Aug 26, 2017
431
267
Google Pixel 4 XL
Okay just for giggles I uninstalled LSPosed, XPrivacyLua and I'm passing Safetynet again now. Still not able to add payment to GPay. So you were right about that module being the culprit.
Awesome! I was gonna say it has to be the Xposed variant but didn't wanna call it out without any confirmation first. Now in terms of not being able to add a payment method still, now I'd try clearing the data of gpay again, rebooting, and trying to add a payment method again. I think that should clear up the issue and if not, maybe a complete uninstall/reinstall of gpay if clearing the data and rebooting didn't work.
 

Homeboy76

Senior Member
Aug 24, 2012
2,803
1,414
Anyone, who has a rooted Android 12 Pixel 4XL that has Google Pay working. Please, share the instructions. I'll update the OP and list you in the Credits for sharing the solution.
 

bradical711

Senior Member
Aug 26, 2017
431
267
Google Pixel 4 XL
Anyone, who has a rooted Android 12 Pixel 4XL that has Google Pay working. Please, share the instructions. I'll update the OP and list you in the Credits for sharing the solution.
You don't need anything special to get gpay working. I'm on A12 Pixel 4XL currently using gpay with no issue. You simply need to pass safetynet and NOT have ANY Xposed variant installed. As far as I'm aware and confirmed yesterday with @madmuthertrucker, Xposed WILL trip gpay. I'll repost my instructions that I posted yesterday to pass safetynet as that's all that's required to use gpay.

Link To Universal Safetynet Fix Thread

You need the "universal safetynet fix" magisk module. XDA thread link is posted above, actual download is hosted on GitHub.

In order to install the "universal safetynet fix" module in magisk though, you'll also need to install the "riru" module. You can find the "riru" module in magisk's repo by searching for "riru". Finally, you'll need to enable magisk hide for Google Play Services, specifically only "com.google.android.gms" & "com.google.android.gms.unstable" need to be ticked. Afterwards, reboot and you should be passing safetynet. Once you're passing safetynet again, don't forget to clear the data for Google Play Store as well and reboot a 2nd time. That'll make sure the Google Play Store certifies your device as "official" in the Play Store after you start passing safetynet again. Optionally, hiding the magaisk manager itself isn't necessary in passing safetynet, but can help you with accessing mobile versions of banking apps, (gpay) etc.
 
  • Like
Reactions: Homeboy76

bradical711

Senior Member
Aug 26, 2017
431
267
Google Pixel 4 XL
Screenshot_20211023-103840.png
Screenshot_20211023-103932.png
Screenshot_20211023-104248.png
Screenshot_20211023-104034.png
 

Attachments

  • Screenshot_20211023-104128.png
    Screenshot_20211023-104128.png
    190.1 KB · Views: 19
  • Like
Reactions: Homeboy76

Homeboy76

Senior Member
Aug 24, 2012
2,803
1,414
You don't need anything special to get gpay working. I'm on A12 Pixel 4XL currently using gpay with no issue. You simply need to pass safetynet and NOT have ANY Xposed variant installed. As far as I'm aware and confirmed yesterday with @madmuthertrucker, Xposed WILL trip gpay. I'll repost my instructions that I posted yesterday to pass safetynet as that's all that's required to use gpay.
Thanks! :)
Pass Safety Net - Updated
 
Last edited:
  • Like
Reactions: bradical711

madmuthertrucker

Senior Member
Jan 4, 2013
195
75
Tucson, Az
Awesome! I was gonna say it has to be the Xposed variant but didn't wanna call it out without any confirmation first. Now in terms of not being able to add a payment method still, now I'd try clearing the data of gpay again, rebooting, and trying to add a payment method again. I think that should clear up the issue and if not, maybe a complete uninstall/reinstall of gpay if clearing the data and rebooting didn't work.
This worked for me. I completely uninstalled GPay. Then reinstalled it. Oddly it didn't work right away. At first I couldn't add a card. But then the next day I opened it and it was asking for a payment card. I tried using it and it's working. Thanks for getting us all sorted out here.
 
  • Like
Reactions: bradical711

bradical711

Senior Member
Aug 26, 2017
431
267
Google Pixel 4 XL
This worked for me. I completely uninstalled GPay. Then reinstalled it. Oddly it didn't work right away. At first I couldn't add a card. But then the next day I opened it and it was asking for a payment card. I tried using it and it's working. Thanks for getting us all sorted out here.
My pleasure, I'm glad you got everything sorted out and working again! I'm happy I could be of help! Enjoy your device and have a great rest of your weekend!
 
  • Like
Reactions: madmuthertrucker

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    For those on latest Canary 23014 (Zygisk with GPay added to deny list),to pass safetynet and enable contactless payments

    1) Clear data for both GPay and Google Play Services. Unfortunately this also meant adding cards back in GPay app (basically reverify already added cards in your GPay profile)

    2) Apply SafetyNet fix 2.2.0 (latest).

    On the bright side no longer need Riru, Riru core, LSPosed etc. etc. Just SNF 2.2.0 + Systemless hosts like old times.
  • 9
    [Guide] Root Pixel 4 XL Android 12 Unlock/Lock Bootloader + Systemless ROOT
    Android Security Bulletin—December 2021
    Pixel Update Bulletin—December 2021

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

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


    Update(s)
    1. Factory/OTA Images - 06/12
    2. Magisk Stable - Magisk-23.0 05/12
    3. Magisk Beta - Magisk-23.0 05/12
    4. Magisk Canary - Magisk-23015 24/11
    5. TWRP - Waiting for T.R.W.P. for Android 12
    6. SafetyNet - SafetyNetFix v2.2.0
    7. SDK Platform-tools - r31.0.3 08/18
    8. Custom Kernels
      • Kirisakura v8.0.0 08/12
      • ElementalX - Check ElmentalX Kernel Manager for Updates
      • CleanSlate R2.7.13/S3.7.13 6/11
    9. Custom ROMs
      • ProtonAOSP[12] 11/01

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

    Prerequisites
    1. A Pixel 4 XL phone with an unlocked bootloader.
    2. The latest Android 12 Factory or OTA Image: "coral" for Pixel 4 XL

      Factory Image

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

    Other Guides

    Credits/Thanks/Recognitions
    1. bradical711 - Instructions to Pass Safety Net
    2. Those I may have, inadvertently, forgotten.

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

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

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

      • Unlock Bootloader

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

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

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

      • Important Note(s):
        1. When doing a major upgrade i.e., Android 11 to Android 12: I recommend doing a clean install. What is a clean install?
          • Doing a Factory reset prior to installing, major, update.
          • Using flash-all.bat file without removing the -w (#4. Wipe Data).
        2. Always verify you have the latest version of SDK Platform-Tools installed on your computer before installing the Factory Image: Pixel 4XL - coral.
        3. If your phone was rooted, and you want to 'Keep Data'. Do this first open Magisk ==> unhide Magisk App (if you hid it) ==> Disable/Remove all modules ==> then Uninstall Magisk - Restore images prior flashing the Factory image. Why? The changes in the New factory image may cause Magisk modules to fail. This will cause boot loops. Additionally, before Enabling/Installing the modules you Disabled/Removed check with the Dev of the module to ensure it was updated to work with the latest factory image.
        4. If you get an error while flashing, try one of these options:
          • Change the USB port to a non charging USB port.
          • Change the USB cord.
          • Change Computers.
        5. Backup your data
        6. Download the latest Factory Image: Pixel 4XL - coral to your Computer.
        7. Extract the factory Image to a folder.
      • Flash Factory Image Keep Data

        • Open the folder you extracted the Factory Image to and Edit the flash-all.bat file with a file editor i.e., Notepad. Remove the -w from this command: fastboot -w update image-coral-aa9a.999999.999.zip
          Note: If you do not remove the -w your data and internal storage will be wiped.[/B]
        • After, you have edited the flash-all.bat file. Copy/Move these files to the Platform-tools folder:
          1. bootloader-coral-....img
          2. flash-all.bat
          3. image-coral-....zip
          4. radio-coral-....img
        • Open a Command Prompt on your computer in the Platform-tools and type: flash-all at the Command Prompt and press enter.
        • System will reboot when flashing is complete.
        • Do #7 to root/reroot.
      • Flash Factory Image Wipe Data

        • This will wipe your phones Internal Storage.
        • Open the folder you extracted the Factory Image to and Copy/Move these files to the Platform-tools folder:
          1. bootloader-coral-....img
          2. flash-all.bat
          3. image-coral-....zip
          4. radio-coral-....img
        • Open a Command Prompt on your computer in the Platform-tools folder and type: flash-all at the Command Prompt and press enter.
        • The phone will reboot when flashing is complete.
        • Do #7 to root/reroot.
    5. ADB Sideload

    6. Extract/Flash boot.img

      • Extract boot.img

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

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

      • Important Note(s):

        1. When doing a major upgrade i.e., Android 11 to Android 12: I recommend doing a clean install. What is a clean install?
          • Doing a Factory reset prior to installing, major, update.
          • Using flash-all.bat file without removing the -w.
        2. If your phone was rooted. Do this first unhide Magisk App (if you hid it) then Uninstall Magisk - Restore Images. Why? The changes in the Factory image may cause Magisk modules to fail. This will cause boot loops.
      • Download files:

        1. Magisk App - Download to your phone
          1. Magisk Beta/Stable App
          2. Magisk Canary App
        2. Custom kernels - Download to your phone - install with Kernel Manager
          • Important Note(s): Unless otherwise directed by Kernel Devloper, Flash the Kernel after Magisk.
          1. ElementalX see EXKM for updates.
          2. [KERNEL] CleanSlate R2.7.13/S3.7.13 |S2S|Gamma|KCal|AdBlock|VIB|WrGrd [Nov 6] by tbalden
          3. [Kernel][08.12.2021][4.14.256][A12] Kirisakura 8.0.0 for Pixel 4/XL aka FLORAL by Freak07
        3. Kernel Manager - Download to your phone
      • Patching the boot.img - to root/reroot.

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

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

      • Set Magisk App Update Channel

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

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

      • Need help with a Custom ROM?

        1. Read and follow the Installation Instructions. The installation instructions are in the OP of the Custom ROM thread.
        2. If you have a problem Installing the ROM, Search the thread of the Custom ROM you are trying to install for a solution to problem: If you don't find a solution post your request for help in the thread.
      • ROMs

        1. Alpha/Beta

          • None
        2. Official
        3. Unofficial

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

      • Android 12 T.W.R.P.
    4
    @Homeboy76 Just wanted to give you a heads up. With the latest Magisk Beta (21.2) that came out yesterday, the patched output file is no longer named "magisk_patched.img". He added a suffix to the name so each time you patch the stock boot image a different output name will result. Thought you might want to modify #7 to address this change (y)
    3
    Is rooting Android 12 with stable magisk actually possible? or do i need the beta or canary version?
    Yes, it's fine. I've been using Stable version 23.0 since the first beta was released and am currently using it on yesterdays official release of Android 12 stable. Everything is fine for me.

    People on other Pixels, specifically the Pixel 5 (and maybe others) have reported that they have to disable dm-verity (and maybe another thing or two) before rooting or it will just land you in the bootloader when trying to boot. However, on my Pixel 4 XL I did not have to do anything. Just patched the boot image as usual and everything is fine for me.

    Of course, your mileage may vary.
    3
    So, I've been out of the flashing game for a long minute but I had to do something about all the ads I was getting. Blockada seemed to work okay but always left something to be desired. I missed Adaway, so....

    I had a hard time getting Magisk installed in Android 11 on my Pixel 4xl. I followed this well written tutorial to a tee but when I flashed magisk_patched.img to boot, then "fastboot reboot," it would kick me back to fastboot after the "G" screen and spit out the error "no valid slot to boot." Three times in a row after clean flashing the factory image too!

    I did end up getting it working. What I ended up doing was instead of "fastboot flash boot magisk_patched.img --slot all" I "fastboot flash boot magisk_patched.img" and for whatever reason that seemed to work.

    I did not take the OTA update if it matters. I had intended to wipe the device with a clean install of Android 11, then Magisk (just for ad blocker) from the get so, I'm guessing slot b wasn't used? I'm honestly not really sure how it works.

    Even then though, I had some trouble getting the order right from flashing the factory image to being rooted, so this is also what I found.

    First, unlock the bootloader of your device, then clean install Android 11 and get it set up. Download Magisk manager canary, then adb push the boot.img from your computer to your device. Use Magisk manager to patch it, then adb pull magisk_patched.img back to your computer. From there, fastboot flash boot your magisk_patched.img and you're golden. Fastboot reboot should put you back in to Android and then Magisk manager will recognize root.

    I had tried several times to use a boot.img I had already patched some days earlier but it never seemed to work. It would boot okay, once I figured out not to "--slot all," but Magisk would never recognize it was rooted unless Magisk manager patched it and I flashed that particular patched file. If I tried to flash any other patched file, Magisk manager wouldn't recognize root. Even recently patched boot.img's that were flashed to the device (not the days old one I had pre-prepped) wouldn't work. Magisk manager only seemed to recognize patched boot.img's that were made by it in that particular install. If I tried to use a boot.img from any other Magisk Manager install it wouldn't recognize it. Weird? I dunno, but, I got it up and running!

    Thanks Homeboy76 for making this tutorial. Without it I would have been lost. :good:
    2
    U da man Homeboy76. Really appreciate all the work you did putting this together. Thanks.