[Guide] Root Pixel 3 XL Android 12

[Homeboy76]

Silly question: After fighting my way through post #1, I got Magisk installed with safetynet, etc. My LG ThinQ app now runs after checking it off in the DenyList. When I do the next Lineage rom update via OTA, will my root 'stay' or do I have to do more steps? Thanks, Dylan

I do not know if you will lose root if you update via the ota, I usually update this way:

Update lineage 19-1 ROM with lineage 19-1 Recovery (see Index Custom ROMS).

1. Download the latest latest lineage 19-1 nightly ROM, lineage 19-1 Recovery, GApps (pico/nano) and Magisk and place
   them in the platform-tools folder on your computer.
2. Install lineage 19-1 Recovery:
   • Boot bootloader
   • Open a Command Prompt in the Platform-tools folder on your computer.
   • At the prompt type: fastboot flash boot lineage-19.1-99999999-recovery-crosshatch.img
   • After, it installs use volume up/down button until you see Recovery mode
   • Press power button to boot the lineage recovery.
3. Sideload the lineage 19-1 ROM:
   • On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
   • On the host machine (computer), sideload the package: adb sideload lineage-19.1-99999999-nightly-crosshatch-signed.zip
4. Reboot Recovery:
   • Tap the back arrow => Tap Advanced => Tap Reboot Recovery (don't reboot the phone before installing GApps or you may have to Factory Reset).Rebooting to Recovery switches to the makes other slot.
5. Sideload Gapps:
   • On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
   • On the host machine (computer), sideload the package:
     adb sideload MindTheGapps-12.0.0-arm64-99999999_999999.zip
     Note: If prompted that signature doesn't match, on the phone, select 'Yes' to continue.
6. Sideload Magisk:
   • On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
   • On the host machine (computer), sideload the package:
     adb sideload app-debug-canary_23016.zip
     Note: If prompted that signature doesn't match, on the phone, select 'Yes' to continue.
7. Reboot System
8. You should have the new version of LOS 19-1 with gapps and Magisk.

 

[faheyd]

Thank you, I've copied that to my cheat sheet for the next update I do. Really appreciate that info! Dylan

 

[trlkly]

So what's the conclusion with systemless hosts? Do you need a customer kernel in Android 12 (October update) to get it to work? If so, what would be the best way to get that and install it?

@icanrule @deusfaux

 

[deusfaux]

Yes custom kernel still needed. I installed freak's kirasakura with FKM. Easy. Solved

 

[Homeboy76]

Two New Android 12 Pixel 3 XL Custom ROMS (see Index Custom ROMS).

 

[trlkly]

In order to get fastboot to communicate with my PC, I had to do something I don't see mentioned here: install Google's ADB drivers for my Pixel 3XL. Without that, Windows would not recognize my phone was connected when I was in fastboot mode.

Get the Google USB Driver | Android Developers

The Google USB Driver is required for Windows if you want to perform adb debugging with Google devices.

developer.android.com

I apologize if I missed this instruction.

 

[Homeboy76]

In order to get fastboot to communicate with my PC, I had to do something I don't see mentioned here: install Google's ADB drivers for my Pixel 3XL. Without that, Windows would not recognize my phone was connected when I was in fastboot mode.

Get the Google USB Driver | Android Developers

The Google USB Driver is required for Windows if you want to perform adb debugging with Google devices.

developer.android.com

I apologize if I missed this instruction.

OP, Prerequisites 2: SDK Platform-tools

 

[trlkly]

In order to get fastboot to communicate with my PC, I had to do something I don't see mentioned here: install Google's ADB drivers for my Pixel 3XL. Without that, Windows would not recognize my phone was connected when I was in fastboot mode.

Get the Google USB Driver | Android Developers

The Google USB Driver is required for Windows if you want to perform adb debugging with Google devices.

developer.android.com

OP, Prerequisites 2: SDK Platform-tools

I already have that. I downloaded that from the link you provided. But that did not include the USB drivers. That's just the programs, like fastboot.exe, adb.exe, etc. I'm talking about the drivers I had to install using Device Manager, from the link I provided.

Before I installed those, Windows wouldn't even detect my phone if I had it in fastboot mode, and fastboot devices showed no devices. After installing the driver, Windows showed an icon to say I had connected my phone, and fastboot devices showed my phone.

 

[Homeboy76]

I already have that. I downloaded that from the link you provided. But that did not include the USB drivers. That's just the programs, like fastboot.exe, adb.exe, etc. I'm talking about the drivers I had to install using Device Manager, from the link I provided.

Before I installed those, Windows wouldn't even detect my phone if I had it in fastboot mode, and fastboot devices showed no devices. After installing the driver, Windows showed an icon to say I had connected my phone, and fastboot devices showed my phone.

You're right, when I saw "install Google's ADB drivers for my Pixel 3XL..." and not Google USB drivers (In your original post.). I stopped reading and reacted, my apologies.

 

[contevo]

Hello, I'm a bit confused with getting root on my pixel 3 xl I read op but steps bit confusing. I wanna flash this kernel on to the stock rom,
kernel: Kirisakura_Bluecross_S_4.0.0
stock rom build number : SP1A.210812.016.A2
Which recovery do I use to sideload Magisk ? I read all 15 pages some people say not to use TWRP. I downloaded Magisk from their telegram: 558710bb-alpha-2.zip.
I know gotta patch boot.img with Magisk to get root, according to the kernel dev description the safetynet bypass already build in. Do I flash kernel with Magisk app manager after sideloading it or specific kernel manager? this step I need clearity because instruction bit all over the places.

 

[Homeboy76]

Hello, I'm a bit confused with getting root on my pixel 3 xl I read op but steps bit confusing. I wanna flash this kernel on to the stock rom,
kernel: Kirisakura_Bluecross_S_4.0.0
stock rom build number : SP1A.210812.016.A2
Which recovery do I use to sideload Magisk ? I read all 15 pages some people say not to use TWRP. I downloaded Magisk from their telegram: 558710bb-alpha-2.zip.
I know gotta patch boot.img with Magisk to get root, according to the kernel dev description the safetynet bypass already build in. Do I flash kernel with Magisk app manager after sideloading it or specific kernel manager? this step I need clearity because instruction bit all over the places.

You want to install this outdated Google Factory Image 12.0.0 (SP1A.210812.016.A2, Oct 2021); Kirisakura_Bluecross_S_4.0.0 kernel (October 21, 2021).

It seems, to me, you want to install this particular kernel to pass SafetyNet: "according to the kernel dev description the safetynet bypass already build in"

The instruction in the OP, 6. tell you how to Patch the boot.img and pass SafetyNet.

Further, you want to use Magisk alpha (558710bb-alpha-2.zip) to patch the boot.img you are going flash to get root: fastboot flash boot magisk_patched...img, but you want to sideload Magisk alpha.

This version of Magisk is for "mavericks only" (extremely knowledgable of Magisk) it is not noobs (inexperienced with Magisk).

Suggestions

1. Take a look at the OP: Updates, 9. and install a Custom ROM with updated Security Patches on your Pixel 3 XL.
2. If you reject 1. above: Go to the OP Updates, 8. tap the Kirisakura_Bluecross_S_4.0.0 kernel link and post your entire post on that thread.

 

[contevo]

You want to install this outdated Google Factory Image 12.0.0 (SP1A.210812.016.A2, Oct 2021); Kirisakura_Bluecross_S_4.0.0 kernel (October21, 2021).

It seems, to me, you want to install this particular kernel to pass SafetyNet: "according to the kernel dev description the safetynet bypass already build in"

The instruction in the OP, 6. tell you how to Patch the boot.img and pass SafetyNet.

Further, you want to use Magisk alpha (558710bb-alpha-2.zip) to patch the boot.img you are going flash to get root: fastboot flash boot magisk_patched...img, but you want to sideload Magisk alpha.

This version of Magisk is for "mavericks only" (extremely knowledgable of Magisk) it is not noobs (inexperienced with Magisk).

Suggestions

1. Take a look at the OP: Updates, 9. and install a Custom ROM with updated Security Patches on your Pixel 3 XL.
2. If you reject 1. above: Go to the OP Updates, 8. tap the Kirisakura_Bluecross_S_4.0.0 kernel link and post your entire post on that thread.

Thank you for your reply. I'll just wait till LOS19 is more stable and I'll switch and have my fun than

 

[phoenixpb]

I posted a link about the last Pixel 3 / Pixel 3 XL update in the OP New section.

Well my Pixel 3 XL is dead after 3 years of great service
Doesn't turn on any more

I have ordered a pixel 6 to be my next device

I will continue to take a look to this thread anyway
if i can help, it always will be a pleasure

Have a nice day

 

[Homeboy76]

Well my Pixel 3 XL is dead after 3 years of great service
Doesn't turn on any more

I have ordered a pixel 6 to be my next device

I will continue to take a look to this thread anyway
if i can help, it always will be a pleasure

Have a nice day

I have a Pixel 6 thread.

 

[Homeboy76]

Update!
Magisk Canary 23017

 

[EtherealRemnant]

Holy heck that was a whole lot more

than the old SuperSU flashing haha! (I was on iOS from 2017 til August and I'm only just now getting around to messing with custom ROMs and root)

That said, thank you for the amazing guide. I flashed PixelDust, installed the alpha branch of Magisk, followed the instructions here, and I appear to be passing SafetyNet seeing how the Chase app works fine and the tool I downloaded (Yet Another Safety Net Attestation Checker) shows it passing basic integrity, CTF, and basic attestation.

Edit: Just got done setting all my apps up. Had to use the Deny List with most of my banking apps. One of them doesn't work even with Magisk hidden and the Deny List. Kind of shocking that Security Service Federal Credit Union has that kind of security considering how outdated their technology is... I even tested Pokemon Go and the McDonalds app since I've seen people complain about those and they work fine but somehow SSFCU is still detecting it. Not a big deal, I can just use a web shortcut to manage that credit card.

Working:

Citi Mobile (I had to download https://play.google.com/store/apps/details?id=net.accelf.devoptshide&hl=en_US&gl=US to hide the developer options because it was detecting those)
Navy Federal
Discover
Capital One
PNC Mobile
FirstBank Mobile Banking
AOD Mobile
AOD Card Controls
Amex
Affinity Federal Credit Union
U.S. Bank Mobile
Elan Credit Card
DCU Mobile Banking
Alliant Mobile Banking
Service CU Mobile Banking
Ent Mobile Banking
Langley FCU
Wells Fargo Mobile
PenFed

(yes, I know I have way too many finance apps but I can't resist credit card sign up bonuses lol - at least only one of them doesn't work).

Edit2: It actually looks like Chase does detect root. There is a whole convoluted way of fixing it that I'm just not interested in doing so I'm going to go without the app.

 

[Homeboy76]

Update
Magisk Canary 23018

 

[LampShade4]

Hello. I am really new to this so please bear with me. My Pixel 3XL recently updated from Android 11 to Android 12 and I lost root. I still have Magisk on it, so I was able to to extract and patch boot.img. However, when I go into Fastboot mode on my phone, it seems that my computer loses the connection. When I use the command fastboot flash boot *******.img, the cmd prompt just says "waiting for any device."

I'm not sure what I am missing or if I need do something drastically different. Any help would be greatly appreciated. Thank you.

 

[Homeboy76]

Hello. I am really new to this so please bear with me. My Pixel 3XL recently updated from Android 11 to Android 12 and I lost root. I still have Magisk on it, so I was able to to extract and patch boot.img. However, when I go into Fastboot mode on my phone, it seems that my computer loses the connection. When I use the command fastboot flash boot *******.img, the cmd prompt just says "waiting for any device."

I'm not sure what I am missing or if I need do something drastically different. Any help would be greatly appreciated. Thank you.

@LampShade4
<Edit> Index, 4 was missing from OP
- It has been restored.

 

[LampShade4]

- Did you check if the computer you are using is communicating with your phone before trying to flash the magisk_patched...img?fasboot devices

- Did you enable USB Debugging on your phone?

- Is your SDK platform-tools the latest version (r31.0.3)?

- Did you try changing USB Cords or Computers?

I do have the latest SDK platform-tools. When the phone is on and in the OS, I can plug the phone into the computer and run "adb devices" and see the serial number. If I run "fastboot devices" nothing is returned. This is true before and after flashing.

I just tried with a new USB cable and nothing changed. I'll try running it on a different computer right now.