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

[Guide] Root Pixel 3 XL Android 12

Search This thread

majorfigjam

Member
Jul 15, 2011
28
18
Anyone, who has a rooted Android 12 Pixel 3 XL that has Google Pay working. Please, share the instructions. I'll update the OP and list you in the Credits for sharing the solution.
I have a rooted Pixel 3XL, with all the necessary mods to pass safetynet etc.and followed the instructions very carefully.

I just downloaded Google Pay, and it seems to work fine - without needing to add to the MagiskHide list, or the XPrivacyLUA options.

Maybe I got lucky?
 

Attachments

  • Screenshot_20211024-123117.png
    Screenshot_20211024-123117.png
    185.1 KB · Views: 66
  • Screenshot_20211024-123053.png
    Screenshot_20211024-123053.png
    163.8 KB · Views: 65
  • Screenshot_20211024-123117.png
    Screenshot_20211024-123117.png
    185.1 KB · Views: 52
  • Screenshot_20211024-123053.png
    Screenshot_20211024-123053.png
    163.8 KB · Views: 64
  • Like
Reactions: Homeboy76

rossmurray

Member
Nov 27, 2010
10
9
London
LG G6
Google Pixel 3 XL
New Pixel 3 XL user here. Google Pay was not working after rooting but after following those helpful steps from majorfigjam I can confirm I now too have it working under rooted A12 (SP1A.210812.015, Oct 2021) running Magisk (23000), Universal SafetyNet Fix (v2.1.1) and ElementalX-P3-4.05 kernel. It is handy though not a deal breaker for me. That said, I'm still excited it's back and don't need to remember to carry my payment card.

EDIT: I am NOT having to hide Google Pay in MagiskHide. It's working without doing so. With that seemingly running solid I'm now testing Magisk Canary (23010) and report no issues so far on reboot. Everything seems to be running as expected. Even after reboot with Zygisk toggled on. In case this makes a difference to anyone following along: received handset running A11, updated OTA to A12, and only then started the rooting process in OP (Precisely following my required steps including Flash FACTORY image keep data).
 
Last edited:

basily

Senior Member
Oct 4, 2008
477
75
Oaxaca
www.BikeMexico.com
Pixel 3xl here. Just installed Android 12 (not clean), booted up fine, patched boot.img using beta channel, but after flashing, stuck at the G logo. Is there something I have to do different from the previous month to month updates under android 11?
 

majorfigjam

Member
Jul 15, 2011
28
18
Pixel 3xl here. Just installed Android 12 (not clean), booted up fine, patched boot.img using beta channel, but after flashing, stuck at the G logo. Is there something I have to do different from the previous month to month updates under android 11?
Did you unhide, remove all modules, and remove Magisk completely first, before doing the upgrade?

If so, which version of Magisk? The latest 23100 changes a lot of things, removes Hide list etc, so best to stick with 23001 unless you're very brave.

Anyway, if you stick on G logo, go back and install original 12 boot image, make sure it all works as expected, then start again from the beginning, after deleting all Magisk leftovers.
 

basily

Senior Member
Oct 4, 2008
477
75
Oaxaca
www.BikeMexico.com
Did you unhide, remove all modules, and remove Magisk completely first, before doing the upgrade?

If so, which version of Magisk? The latest 23100 changes a lot of things, removes Hide list etc, so best to stick with 23001 unless you're very brave.

Anyway, if you stick on G logo, go back and install original 12 boot image, make sure it all works as expected, then start again from the beginning, after deleting all Magisk leftovers.

Thanks for the reply. You'd think that after years of removing Magisk before flashing updates every month, it would be a habit - well, I forgot to do it this time.

Anyway, I was able to boot normally after first booting in safe mode, but whenever I'd install systemless hosts on Magisk, I'd be stuck at boot again. So, anyway, went again from the start and all seems fine.

Using 2300 and everything seems fine, including google pay and gpay (I only had to hide them from root).
 

CosmicDan

Senior Member
Jun 19, 2009
5,890
7,736
34
Sydney
Google Pixel 3 XL
Xiaomi Poco X3 Pro
Alright, full rundown time.

1) Did a 'flash-all.bat' on my Pixel 3 XL - with wipe. Only thing not original now is the bootloader was kept unlocked.

2) Setup the phone like a normal person. Restored from a Google backup, installed a few apps from Play Store:
- EX Kernel Manager
- FX File Manager
- Material Terminal
- SafetyNet Helper Sample (SafetyNet `attest`)
...also restored all other stuff like device settings and such. Also Left every other setup thing on default (max tracking/background stuff baby yeah :p). Set a fingerprint, and continued with full setup. Didn't turn on Assistant or Squeeze nor Pay (yet) nor AOD.

3) Changed navigation to gesture mode, and enabled the best setting in A12 I've seen yet: System > Developer Options > Display cutout > Render apps below cutout area.

4) Checked Play Store, did an update of most things. Skipped stuff like "Sounds" and "YouTube" that aren't essential right now, still took a while. Settings were already sync'd by this stage though (Dark was enabled, DPI was 484, Wifi was on, etc.). Restarted phone.

5) ... wow, such restart speed.... (maybe 6 seconds on bootanimation). Unlocked with pin, Restarted to bootloader (held Vol- on Restart) and did a fastboot --disable-verification --disable-verity --slot all flash vbmeta vbmeta.img then fastboot reboot.

6) Ran SafetyNet `attest`, CTS false because of unlocked bootloader... figures.

7) Downloaded latest Magisk Canary apk on phone (app-debug.apk from magisk-files branch canary), installed. Copied boot.img to Phone, patched boot.img, copied back, fastboot again now, yada yada yada.... basically flashed patched Magisk canary boot.img. Command: fastboot flash boot boot_magisk-canary_23011_VE2JR.img

8) Started Magisk, enabled Zygisk, Enforce Denylist, searched for "Play" with all filters enabled and denied all results. Include Play Store and gms. Also denied SafetyNet `attest`.

9) Restarted. Ensured Zygisk was enabled in Magisk - yeah. Ran SafetyNet `attest` again: CTS profile mismatch. Hrrr.

So, yeah root works - but idk how to pass SafetyNet. I read somewhere that apparently this isn't a big deal... I'm yet to setup Google Pay.

Small FYI re custom kernels - they often have a custom DBTO, you might need to also flash back stock DTBO for OTA to work. Guess we can see.


Basically, we need to determine if it matters when you flash vbmeta. Here's what needs to be tested:
- Factory flash Android 12 with a wipe; do NOT disable verity and verification
- Set up and use your device
- After everything is set up (download all your apps) attempt to reflash vbmeta with verity and verification disabled, as well as a patched boot image.

If this is successful, this means we shouldn't have to wipe every time we take a monthly update.
Yes, this works. But maybe you need to flash back stock vmbeta, along with stock dtbo (if you flashed a custom kernel) and stock boot.img for OTA to work.
 

V0latyle

Forum Moderator
Staff member
Alright, full rundown time.

1) Did a 'flash-all.bat' on my Pixel 3 XL - with wipe. Only thing not original now is the bootloader was kept unlocked.
I don't believe disabling verity or verification is necessary on the Pixel 3/3XL. Maybe on the 3a but most reports I've seen of having to do this have been with the Pixel 4 and up. See if you can reflash vbmeta without flags (keep your patched boot image) and see if it still boots.
Ensured Zygisk was enabled in Magisk - yeah. Ran SafetyNet `attest` again: CTS profile mismatch. Hrrr.

So, yeah root works - but idk how to pass SafetyNet. I read somewhere that apparently this isn't a big deal... I'm yet to setup Google Pay.
To get CTS to pass on Magisk 23010, you have to use MagiskHide Props Config as well as pre-Riru Universal SafetyNet Fix (v1.2.0).

I went back to Magisk 23001 after discovering this and have CTS OK with MagiskHide, Riru+USNF 2.2.0.
 

CosmicDan

Senior Member
Jun 19, 2009
5,890
7,736
34
Sydney
Google Pixel 3 XL
Xiaomi Poco X3 Pro
This thread (Index, #7, Pass Safety net) :
[Guide] Root Pixel 3 Android 12
If you use Magisk Canary to patch your boot image use Magisk Canary 23001. Otherwise, use Magisk Stable.
Indeed, thank you!

I found out Magisk Canary 23001 is identical to current stable. And it works a treat with latest USNF 2.x - everything passes.

So that's the solution, just stick to stable if you don't care about developing. Hopefully Zygisk is the start of something wonderful though!
 

Homeboy76

Senior Member
Aug 24, 2012
2,804
1,415
Indeed, thank you!

I found out Magisk Canary 23001 is identical to current stable. And it works a treat with latest USNF 2.x - everything passes.

So that's the solution, just stick to stable if you don't care about developing. Hopefully Zygisk is the start of something wonderful though!
I could be wrong, but I don't think Zygisk is necessary on the Pixel 3.
 

phoenixpb

Senior Member
Dec 18, 2010
101
21
Hi guys

I have sucessfully updated my android 11 rooted to android 12
phone is not rooted for the moment
i have patched the android 12 boot.img with magisk canary no problem

i only have a small question to flash the patched boot.img

which command do i have to use ? (because i see the 2 versions in the forum)

fastboot flash boot --slot all boot.img
or
fastboot flash boot.img

thanks

have a nice day
 
Last edited:

Homeboy76

Senior Member
Aug 24, 2012
2,804
1,415
Hi guys

I have sucessfully updated my android 11 rooted to android 12
phone is not rooted for the moment
i have patched the android 12 boot.img with magisk canary no problem

i only have a small question to flash the patched boot.img

which command do i have to use ? (because i see the 2 versions in the forum)

fastboot flash boot --slot all boot.img
or
fastboot flash boot.img

thanks

have a nice day
fastboot flash boot magisk_patched.img
 

phoenixpb

Senior Member
Dec 18, 2010
101
21
Magisk is installed in android 12 but i can't install modules
adaway doesn't work
root explorer doesn't work
pixel launcher mod doesn't work
su in terminal works
i have magisk canary 23011 installed

thanks
 

i928

Member
Aug 18, 2019
44
1
Moto G4
Moto G4 Plus
Magisk is installed in android 12 but i can't install modules
adaway doesn't work
root explorer doesn't work
pixel launcher mod doesn't work
su in terminal works
i have magisk canary 23011 installed

thanks
I use 23.0 stable, can install module. AdAway, root explorer works.
I had trouble restoring Netflix from Titanium backup, cannot find Netflix from play store. I resolved by installing from Netflix website. I can find Netflix from playstore after installing Netflix.
 

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.