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

Search This thread

Bologner

Member
Nov 19, 2009
31
9
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.
 
Last edited:
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

Member
Dec 11, 2007
46
10
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? :( :(
 
  • Like
Reactions: farfegnugen

Spunkybob

Senior Member
Oct 1, 2010
165
38
Kariong
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.
 
Last edited:

Lughnasadh

Senior Member
Mar 23, 2015
3,324
3,292
Google Nexus 5
Huawei Nexus 6P
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.
 
Last edited:

Spunkybob

Senior Member
Oct 1, 2010
165
38
Kariong

Spunkybob

Senior Member
Oct 1, 2010
165
38
Kariong
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.
 
Last edited by a moderator:

xtravbx

Senior Member
Aug 23, 2010
130
14
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

Senior Member
Mar 27, 2012
2,814
1,240
NE Pennsylvania Boonies
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.
 
Last edited by a moderator:
  • Like
Reactions: Badger50

DrunkUncas

Senior Member
Aug 14, 2008
667
190
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

Senior Member
Mar 23, 2015
3,324
3,292
Google Nexus 5
Huawei Nexus 6P
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

Member
Oct 23, 2020
14
2
LG V40
Samsung Galaxy A32 5G
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

Senior Member
Mar 23, 2015
3,324
3,292
Google Nexus 5
Huawei Nexus 6P
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

Member
Oct 23, 2020
14
2
LG V40
Samsung Galaxy A32 5G
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

Senior Member
Mar 23, 2015
3,324
3,292
Google Nexus 5
Huawei Nexus 6P
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.
 
Last edited:
  • Like
Reactions: Jake81345

Top Liked Posts

  • There are no posts matching your filters.
  • 38
    Anyone root the Pixel 4 XL from Google Play store yet?

    Can the Pixel 3 XL Android 10 root method be used for Pixel 4 XL Android 10 root?

    *Update2 (10/24/2019 6:00PM): Factory Images have been released! :)
    They are available at below links. Multiple users say they have root working now.

    *Note: Multiple images are listed. For my Pixel 4 XL 128GB purchased directly from Google Play store, the image is the first one "10.0.0 (QD1A.190821.007, Oct 2019)". You can verify in "Settings" >> "About Phone"... near bottom you will see "Build Number"
    1. Factory: https://developers.google.com/android/images#coral
    2. OTA: https://developers.google.com/android/ota#coral

    According to @Samg381 the method to gain root is to follow the guide outlined here: https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
    Below are steps I personally followed:
    1. Download latest Magisk Manager - https://github.com/topjohnwu/Magisk/releases/download/manager-v7.3.5/MagiskManager-v7.3.5.apk
    2. Install Magisk manager on my Pixel 4 XL
    3. Download latest factory image with build number that matches my phone's version from this URL: https://developers.google.com/android/images#coral
    4. Extract the zip file contents
    5. You will see one more zip file, extract those contents
    6. Copy the boot.img file to your phone (you can plugin USB to your PC and put it in your "Downloads" folder
    7. Open Magisk Manager, click "Advanced" >> "Recovery Mode"
    8. Click the top "Install" button
    9. When prompted click Install again, then "Select and Patch a file" >> Select the boot.img file you copied to your pixel 4 xl earlier.
    10. it will create a new file "/storage/emulated/0/Download/magisk_patched.img"
    11. Plugin your phone to your PC again via USB, copy this new file in same folder as your adb sdk files.
    12. open cmd prompt type:
    13. adb devices
    14. *Note: unlock your phone and approve ADB access if prompted
    15. adb reboot bootloader
    16. fastboot devices
    17. fastboot flash boot magisk_patched.img
    18. If it works you should get somthing like
      fastboot flash boot magisk_patched.img
      target reported max download size of 268435456 bytes
      sending 'boot_a' (32092 KB)...
      OKAY [ 1.167s]
      writing 'boot_a'...
      OKAY [ 0.325s]
      finished. total time: 1.494s
    19. Reboot your phone, open Magisk manager again, and verify it shows you now have root! :)


    I would recommend everyone who plans to root unlock their bootloader NOW as it does wipe your data just like other Pixel phones have when unlocking bootloader... I already unlocked my bootloader.

    FYI, the process to unlock Pixel 4 XL bootloader is easy:
    1. Boot Pixel 4 XL, go through initial setup guide (do not bother adding account as you will wipe data shortly)
    2. "Settings" >> "About Phone" >> Tap "build number" about 10 times till "You are a developer"
    3. "Settings" >> "System" >> "Advanced" >> "Developer Options"
    4. Check "OEM unlocking"
    5. If "OEM Unlocking" is greyed out, either "Bootloader is already unlocked", or you need to do factory reset, then go through steps 1-4 again. On my phone I had to wipe data once, then OEM Unlock
    6. Check "USB Debugging"
    7. Connect Pixel 4 XL to your PC with SDK tools installed
    8. adb devices
    9. unlock your Pixel 4 XL... you will see a prompt asking for ADB permissions, say yes
    10. adb reboot bootloader
    11. fastboot devices
    12. fastboot flashing unlock
    13. Pixel 4 XL will now ask if you want to unlock bootloader, press volume up or down once... then power button once to confirm. WARNING it will wipe all your data...
    8
    Lol, must be a noob

    ---------- Post added at 02:09 AM ---------- Previous post was at 02:08 AM ----------

    Looks like the process is fairly straightforward for this device as well. about as easy as any other unlocked device, I would say

    Be humble.
    4
    Yeah, I saw that also. So we should wait to sideload OTA? I'm less familiar with the scene and how fast these things develop.

    Keep checking the Google Factory Images page. The Pixel 4 should be listed in a day or so.
    When Pixel 4 images become available, check John Wu's Twitter and the Magisk forum.
    When John or a trusted user confirms Magisk as working for the Pixel 4, you can follow the Magisk boot image Installation Method.
    In the meantime, make sure your bootloader is unlocked, and you have a PC with ADB/Fastboot prepared once Magisk is ready.
    3
    No luck unlocking my Verizon XL. With a quick glance at the VZ 3 XL posts - I'm assuming I shouldn't hold my breath?

    People on the Verizon pixel 2 and P2XL are still holding their breath....so yeah! :(
    3
    Potential fix for people with AdAway troubles, here's what got mine to work:
    1) Kill AdAway, clear cache + wipe data.
    2) Uninstall AdAway.
    3) In Magisk, enable systemless hosts
    4) Install (or reinstall) busybox
    5) reboot phone
    6) Re-install and open AdAway, enable adblocking. (you won't have any hosts, this is fine)
    7) add one of your hosts, and then apply.
    Fixed it for me. You should now be able to add the rest of your hosts.
    @aNYthing24