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

[Guide] Root Pixel 3 XL Android 12

Search This thread

Homeboy76

Senior Member
Aug 24, 2012
2,796
1,412
OP Updated
Index, • Open a Command Prompt on Computer

What changed and Why?

The Option to open powershell was restored.

I made a mistake. :(

I forgot to enable USB debugging before booting fastboot mode (bootloader) on my phone.

After, I corrected my mistake, I opened a powershell command prompt: Opened File Explorer ==> clicked the platform-tools folder ==> clicked the folder icon (left side of address bar) to highlight it typed powershell and pressed enter.

Then I typed ./fastboot devices at the powershell command prompt and pressed enter. It worked.
 
Last edited:

tabemasu88

Senior Member
Jul 4, 2012
109
3
I just took over my wife pixel 3 XL with android 11 as the system, I realized it's not DSDS, will I used this method to root my phone and able to get DSDS after rooted?
 

kenfly

Senior Member
Dec 22, 2009
749
56
      1. Install Magisk Modules Riru, Riru - LSPosed and install XPrivacy Lua
        • Open Magisk
        • Tap Modules icon
        • Install Magisk module Riru-...zip
        • After it installs tap the Save icon to save the log
        • Reboot
        • Open Magisk
        • Tap Modules icon
        • Install Magisk module Riru_-_LSPosed-....zip
        • After it installs tap the Save icon to save the log
        • Reboot
        • Downloaded and install XPrivacy Lua module from: here
        • Reboot
        • Open LSPosed
        • Tap Modules
        • Enable XPrivacyLua module
        • Tap 3dots Menu (top-right)
        • Tap Hide
        • Uncheck System apps
        • Tap Google Play Services
        • Tap Setup icon (top-right)
        • Scroll down
        • Tap Google Play Services
        • Scroll down and enable/check (✓)
          • Determine Activity
          • Read identifiers
          • Use analytics
          • Use tracking
        • Reboot
        • Open Magisk
        • Test SafetyNet
      2. Clear Google Play Services Data
        • Open Settings
        • Tap Apps & notifications
        • Tap see all...
        • Tap three dot menu
        • Tap Show system
        • Scroll down to Google Play Services
        • Tap it
        • Tap Storage & cache
        • Tap Clear storage
        • Exit Settings
        • reboot
      3. Check Device Certification
        • Open Google Play Store app
        • Tap Menu - Circle top right
        • Tap Settings
        • Tap About
        • check Device certification.
I installed XPrivacyLua and unhide services. but tapping Google Play Services only checks or unchecks the box. I don't get options to
  • Scroll down and enable/check (✓)
    • Determine Activity
    • Read identifiers
    • Use analytics
    • Use tracking
 

deusfaux

Senior Member
Dec 12, 2010
143
19
is a custom kernel like kirisakura still needed to fix the "f2fs-stable bug" from using the systemless hosts module in magisk?

or has that been fixed by Android 12?
 

Homeboy76

Senior Member
Aug 24, 2012
2,796
1,412

After, reading several threads and @Lughnasadh post, there are no special requirements to root Android 12 for the Pixel 4 XL or the Pixel 3 XL.​


So, that means the instructions in the OP, Index, #7 are sufficient for rooting the Pixel 4XL and Pixel 3 XL phones.

Thanks, Lughnasadh! :)
 
Last edited:

Lughnasadh

Senior Member
Mar 23, 2015
2,377
1,811
Google Nexus 5
Huawei Nexus 6P

After, reading several threads and @Lughnasadh post there are no special requirements to root Android 12 for the Pixel 4 XL or the Pixel 3 XL.​


So, that means the instructions in the OP, Index, #7 is sufficient for rooting those phones.

Thanks, Lughnasadh! :)
No problem. Thanks for keeping the guide up for all of us!

Oops. Meant for this to be in the 4XL thread 😋
 

deusfaux

Senior Member
Dec 12, 2010
143
19
Is there a kernel manager playing nice with android 12? Exkm and fkm both haven't been updated since release Android 12
 

icanrule

Senior Member
May 11, 2011
60
10
is a custom kernel like kirisakura still needed to fix the "f2fs-stable bug" from using the systemless hosts module in magisk?

or has that been fixed by Android 12?
I have been living with this problem for 9 months and your telling me all I needed was a custom kernel? I've asked forum after forum to find a solution to this problem. Using the pixel 3 has been a living nightmare. Thank you for this tip. If it happens in Android 12 after root I'll know to use a different kernel.
 
  • Like
Reactions: deusfaux

deusfaux

Senior Member
Dec 12, 2010
143
19
I have been living with this problem for 9 months and your telling me all I needed was a custom kernel? I've asked forum after forum to find a solution to this problem. Using the pixel 3 has been a living nightmare. Thank you for this tip. If it happens in Android 12 after root I'll know to use a different kernel.
It was a bug report in magisk acknowledged by topjohnwu for a long while, and then freak wrote there what was causing it and also provided a solution. The other solution was to disable the systemless hosts module in magisk but that means no superior adblocking. Anyways. Report back if you can do it all on Android 12
 
  • Like
Reactions: Homeboy76

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    So when we do this, we disable modules module, update to 23013, and make sure that we do not use the Riru module at all?
    Yes, disable the modules and set the update channel to Canary, if it is not already set to Canary.
    - When you see update in the app section of Magisk update the App.
    - Patch the boot.img
    - flash the magisk-patched_...img
    fastboot flash boot magisk-patched_...img
    - Then go to the OP, Root/Reroot with Magisk and Pass SafetyNet, Pass Safety Net with SafetyNet Fix 2.2.0, 3. Settings for Magisk Canary 23015
  • 11
    [Guide] Root Pixel 3 XL Android 12 Unlock/Lock Bootloader + Install Stock Images/Systemless Root2021
    Android Security Bulletin—October 2021
    Pixel Update Bulletin—October 2021

    Introduction
    1. This Guide is for Pixel 3 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 3 XL'.
    2. This Guide also works for Pixel 3 owners: If, they download the Pixel 3 files.

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


    Update(s)
    1. Factory/OTA Images - 10/19
    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 v4.0.0 S 10/21
      • Elemental X - check the Elemental X Kernel Manager for updates
    9. Custom ROMs
      • Waiting for Android 12 ROMS

    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 3 XL phone with an unlocked bootloader.
    2. The latest Android 12 Factory or OTA Image: "crosshatch" for Pixel 3 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 Pixel XL Guides

    Credits/Thanks/Recognitions
    1. bradical711 - Instructions to Pass Safety Net
    2. @sliding_billy - His help editing this thread.
    3. 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

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

        1. Do not lock the bootloader until you have returned the phone to stock. Failure to do so causes bricked phones.
        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 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 with the -w (Wipe Data).
        2. Always verify you have the latest version of SDK Platform-Tools installed on your computer before installing the Factory Image: Pixel 3 XL - crosshatch.
        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 when flashing the image, 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 3 XL - crosshatch to your Computer.
        7. Extract the factory Image to a folder.
      • Flash Factory Image Keep Data

        • Open the folder with the extracted the Factory Image and Edit the flash-all.bat file with a file editor i.e., Notepad. Remove -wfrom this command: fastboot -w update image-crosshatch-aa9a.999999.999.zip
          Note: If you do not remove the -w your Internal Storage will be wiped.
        • Copy/Move these files to the Platform-tools folder:
          1. bootloader-crosshatch-....img
          2. flash-all.bat
          3. image-crosshatch-....zip
          4. radio-crosshatch-....img
        • At the Command Promp type: flash-all and press enter.
        • System will reboot when flashing is complete.
        • Do #7 to root/reroot.
      • Flash Factory Image Wipe Data

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

      • Stock Recovery
      • Custom Recovery - TWRP

        • Important notes:
          1. Charge your device.
          2. Enable USB Debugging on your phone.
          3. Install the latest version of SDK Platform-tools on your computer.
        • Open a command prompt in the computer's ADB folder: the folder with ADB.exe in it.
        • Put the (flashable zip) file you want to sideload in the computer's ADB folder.Copy the Zip file you want to install on your device to the ADB folder.
        • Connect your device to your computer using a USB cable.
        • Boot T.W.R.P.
          1. T.W.R.P installed: Boot fastboot mode ==> use volume buttons up/down until you see Recovery mode ==> press power botton.
          2. T.W.R.P. not installed: Boot T.W.R.P: Put twrp.img file in the computer's ADB folder ==> open a command prompt in ADB folder ==> at the prompt type fastboot flash boot "Name of twrp file.img" without the quotation marks.
        • When T.W.R.P boots tap Advanced ==> ADB Sideload.
        • ✓ the wipe Dalvik cache box
        • Swipe to start
        • On your Computer: Enter the following command at the command prompt. adb sideload <filename.Zip> i.e., adb sideload myfile.zip
        • You will see the progress of the sideloaded file.
        • When the file finishes sidloading, reboot your device.
        • Done!
    6. Extract/Flash boot.img

      • Extract boot.img

        • Download the latest Factory image to your phone.
        • Extract the Factory Image file (crosshatch-pda1a.999999.999-factory-99a9a99a.zip) to a folder.
        • Open the folder and, extract the Image file (image-crosshatch-aa9a.999999.999.zip).
      • Flash boot.img

        1. Note: Flashing this file 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. At the Command Prompt type: fastboot flash boot --slot all boot.img
        6. Reboot
    7. Root/Reroot with Magisk and Pass SafetyNet.

      • 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 menu icon > Settings > 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/MagiskManager/logs/install_log_
        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

          • None
        3. Unofficial

          • None
    10. Mods/Scripts/Themes
    11. T.W.R.P. Backup/T.W.R.P Update

      • Waiting for Android 12 T.W.R.P.
    3
    Hello Pixel Community,

    We have provided the monthly Android/Pixel update for December 2020. All supported Pixel devices running Android 11 will receive these software updates as part of the December 2020 update, which begins rolling out to users today. We encourage you to check your Android version and update to receive the latest features.

    Overview:

    • Software versions:
      • Global:
        • Pixel 3 (XL): RQ1A.201205.003
        • Pixel 3a (XL): RQ1A.201205.003
        • Pixel 4 (XL): RQ1A.201205.008
        • Pixel 4a: RQ1A.201205.008
        • Pixel 4a (5G): RQ1A.201205.011
        • Pixel 5: RQ1A.201205.011
      • Verizon:
        • Pixel 3 (XL): [Update: Rolling out week of 12/14]
        • Pixel 4a (5G): [Update: Rolling out week of 12/14]
        • Pixel 5: [Update: Rolling out week of 12/14]
      • AT&T:
        • Pixel 4 (XL): RQ1A.201205.008.A1
        • Pixel 4a (5G): RQ1A.201205.010
        • Pixel 5: RQ1A.201205.010

    3

    After, reading several threads and @Lughnasadh post, there are no special requirements to root Android 12 for the Pixel 4 XL or the Pixel 3 XL.​


    So, that means the instructions in the OP, Index, #7 are sufficient for rooting the Pixel 4XL and Pixel 3 XL phones.

    Thanks, Lughnasadh! :)
    2
    It's not clear to me if the verizon version is for the verizon variant phones only or for both verizon and unlocked variants on verizon service


    Well thanks, but I think it is pretty clear it would apply to the verizon variant. It's the unlocked variant I'm curious about.

    You want the Verizon varient, it is for both the VZ varient and the unlocked. These occasional forks are always radio or network changes needed for best performance on a carrier. They will mege back into one in a moth or two. It's a pretty common event.
    2
    Did anyone tried using the patched.img provided by a user on the first page?, I don't want to waste data by downloading stock boot.img

    Hi,

    Don't use it, it is an old one. You want the stock January boot.img? There are two factory images this month: international / Verizon.

    Cheers...

    Sébastien.