[Guide] Pixel 4 XL (Unlocked from Google Store) - Root and Bootloader Unlocking

[Bologner]

Pixel 4 XL bought from T-Mobile here.

Anytime I flash magisk_patched.img, when my phone boots into system, I can see the lock screen, but the touch screen is completely unresponsive. I have tried this with both the March and June factory images, on different computers, with different versions of Magisk, and the result is always the same.

Do I need to boot into fastbootd instead to successfully flash the boot file?

EDIT: i5l338bit's verison (https://forum.xda-developers.com/pixel-4-xl/how-to/update-root-guide-jun-2020-qq3a-200605-t4109099) works fine. I do not understand why that version works, but uploading the stock boot.img to my phone, flashing Magisk onto it, and then flashing that boot image results in a stuck screen. I've been flashing ROMs for 6+ years now, so this is not a new procedure for me.

 

[kickenwing13]

Pixel 4 XL bought from T-Mobile here.

Anytime I flash magisk_patched.img, when my phone boots into system, I can see the lock screen, but the touch screen is completely unresponsive. I have tried this with both the March and June factory images, on different computers, with different versions of Magisk, and the result is always the same.

Do I need to boot into fastbootd instead to successfully flash the boot file?

EDIT: i5l338bit's verison (https://forum.xda-developers.com/pixel-4-xl/how-to/update-root-guide-jun-2020-qq3a-200605-t4109099) works fine. I do not understand why that version works, but uploading the stock boot.img to my phone, flashing Magisk onto it, and then flashing that boot image results in a stuck screen. I've been flashing ROMs for 6+ years now, so this is not a new procedure for me.

Just followed some instructions and did this process and got the same result . Was up till 4am trying to get out of bootloop and did the flash-all script for most recent Android 11 to fix ...

---------- Post added at 04:29 PM ---------- Previous post was at 04:23 PM ----------

I just installed coral-rpp4.200409.015. After patching the boot.img on MM Canary 284, to install Magisk 20409. Patching goes fine. When I flash the magisk_patched.img and reboot, goes into bootloop. I tried flashing to both slots and I am unable to boot. I have to go back to the stack boot.img to boot.

Got root working, safety net does not pass, not an issue foe me. I have not installed any modules. I have root after several reboots
Thanks

Keep reading and I forgot to HIDE Magisk. After reboot all functioning as expected

What solved your issue ? I was unlocked on .020 and patched via magisk. Moved to cou. Flashed via fastboot and bootlooped last night ... Panicked. Tried flashing the stock boot img and still didn't work, so I flashed back to stock .

 

[fbr79]

I followed the procedure with Android 10. Everything ok but the unlocking with the face no longer works ... I tried everything.
Can you help me?

 

[joseph168]

Adb sideload Telstra OTA, It will fix face unlock issue.

 

[Spunkybob]

I'm having a few issues with my latest wipe.
I factory reset and flash latest factory, patch and install the boot.img fine and everything works...

Except I cannot get safety net to pass and root YouTube Vanced to install.

I'm doing everything exactly the same as last time (few months ago) but these two things no longer work.. any ideas?

Do I need to go to an older factory image? Did Google change something?

Edit: it says ctsprofile = false
Does that matter?

My issue is I cannot disable signature verification for the app to install.

 

[Lughnasadh]

I'm having a few issues with my latest wipe.
I factory reset and flash latest factory, patch and install the boot.img fine and everything works...

Except I cannot get safety net to pass and root YouTube Vanced to install.

I'm doing everything exactly the same as last time (few months ago) but these two things no longer work.. any ideas?

Do I need to go to an older factory image? Did Google change something?

Edit: it says ctsprofile = false
Does that matter?

My issue is I cannot disable signature verification for the app to install.

Yes, Google changed something. https://twitter.com/topjohnwu/status/1277474811220910080

You should still be able to install Vanced. I personally use the non-rooted version on my rooted 4 XL.

 

[Spunkybob]

Yes, Google changed something. https://twitter.com/topjohnwu/status/1277474811220910080

You should still be able to install Vanced. I personally use the non-rooted version on my rooted 4 XL.

Fu*k... The reason I use android is to do what I want.
I can install non rooted Vanced but I hate having the standard YouTube there also.
Also YouTube links sent always open in standard YouTube not Vanced.

 

[Lughnasadh]

Fu*k... The reason I use android is to do what I want.
I can install non rooted Vanced but I hate having the standard YouTube there also.
Also YouTube links sent always open in standard YouTube not Vanced.

I disabled the Play Store YouTube version and set YouTube Vanced to open YouTube links and it works fine.

 

[Spunkybob]

I disabled the Play Store YouTube version and set YouTube Vanced to open YouTube links and it works fine.

I literally did the same thing just now but after setting Vanced to always open and disable store version they just open in chrome now.

Might reboot but only 1% battery left.

 

[Lughnasadh]

I literally did the same thing just now but after setting Vanced to always open and disable store version they just open in chrome now.

Might reboot but only 1% battery left.

Try clearing Chrome's Open by default. I have no defaults set in Chrome for link opening.

 

[Spunkybob]

Try clearing Chrome's Open by default. I have no defaults set in Chrome for link opening.

Not working.. oh well.
I reflashed my phone with an older build and still can't install root Vance's or disable verification with (Mod Edit: Reference to Warez removed)

This might be my last pixel.

 

[xtravbx]

Does anyone have Google Pay (CTS Profile Passing) with Pixel 4XL now?

For the life of me I can't get it to pass.... is that it? Are we stuck?

---------- Post added at 05:20 PM ---------- Previous post was at 05:20 PM ----------

Does anyone have Google Pay (CTS Profile Passing) with Pixel 4XL now?

For the life of me I can't get it to pass.... is that it? Are we stuck?

 

[CyberpodS2]

Not working.. oh well.
I reflashed my phone with an older build and still can't install root Vance's or disable verification with (Mod Edit: Reference to Warez removed)

This might be my last pixel.

For what it's worth, you'll not be getting any help with (Mod Edit: Reference to Warez removed) here. If anything you might be warned about pirate talk.

 

[Badger50]

Deleted.

 

[DrunkUncas]

Magisk without TWRP?

Just got my Pixel. Unlocked the bootloader, and installed Manager

Directions for installing are:
Open Magisk Manager, click "Advanced" >> "Recovery Mode"
Click the top "Install" button

But the Manager doesn't have an "advanced", "recovery mode", or "install" options. Just less useful stuff like download path, dark mode, etc under the hamburger and settings

What am I missing?

 

[Lughnasadh]

Just got my Pixel. Unlocked the bootloader, and installed Manager

Directions for installing are:
Open Magisk Manager, click "Advanced" >> "Recovery Mode"
Click the top "Install" button

But the Manager doesn't have an "advanced", "recovery mode", or "install" options. Just less useful stuff like download path, dark mode, etc under the hamburger and settings

What am I missing?

See my response in the Magisk thread where you posted the same question.

 

[Jake81345]

I am really having a tough time getting this phone rooted.
bootloader unlocked, latest compatible boot img patched with magisk, when it was time to flash I kept getting a error to do with the boot slot and nothing being found, I ended up spending 6 hours getting out of boot loop. I'm kinda a noob and would greatly appreciate any available help. I feel like I am about to pull my hair out.

 

[Lughnasadh]

I am really having a tough time getting this phone rooted.
bootloader unlocked, latest compatible boot img patched with magisk, when it was time to flash I kept getting a error to do with the boot slot and nothing being found, I ended up spending 6 hours getting out of boot loop. I'm kinda a noob and would greatly appreciate any available help. I feel like I am about to pull my hair out.

Here is a good guide... https://forum.xda-developers.com/t/guide-root-pixel-4-xl-android-11-r.4160441/

Basically:
1. Make sure your platform tools are up-to-date
2. Extract the stock boot image you are currently on and place it in your internal storage.
3. Patch that boot image with Beta Magisk (set update channel to Beta in Magisk Manager).
4.Flash the patched boot image with fastboot: fastboot flash boot magisk_patched.img
5. Boot up

 

[Jake81345]

Here is a good guide... https://forum.xda-developers.com/t/guide-root-pixel-4-xl-android-11-r.4160441/

Basically:
1. Make sure your platform tools are up-to-date
2. Extract the stock boot image you are currently on and place it in your internal storage.
3. Patch that boot image with Beta Magisk (set update channel to Beta in Magisk Manager).
4.Flash the patched boot image with fastboot: fastboot flash boot magisk_patched.img
5. Boot up

Im about to give this another go. I just updated the platform tools and magisk then patched the boot.img. should I fatory reset before trying to flash. and do I need to specify wich boot slot? Also I greatly appreciate all help and advice

 

[Lughnasadh]

Im about to give this another go. I just updated the platform tools and magisk then patched the boot.img. should I fatory reset before trying to flash. and do I need to specify wich boot slot? Also I greatly appreciate all help and advice

Not knowing how you got out of your bootloop or what caused your bootloop in the first place, in my opinion it would be a good idea to either factory reset or fastboot flash the latest factory image so you can start fresh (back up any files you need to save first). After doing that you shouldn't have to specify which slot, it should flash the patched boot image to the slot you are on automatically.

Since the Beta Magisk was updated yesterday to 21.2 make sure you when you enter the command "fastboot flash boot <name> that you use the name of the patched boot image. When I updated yesterday the name of the patched boot image found in the downloads folder after patching changed from "magisk_patched.img" to "magisk_patched_aE2Jx.img". So double check to make sure you use the actual name of whatever you ended up with. Not sure if this was this case for others who updated.

So for instance, yesterday I had to use the command "fastboot flash boot magisk_patched_aE2Jx.img" (without the quotes).

EDIT: Apparently their was a commit added to Beta 21.2 where the name of the patched boot image will change every time you patch your stock boot image.