yashsingh1/xdaforums huggingface dataset:
[Google Pixel 4 XL Guides, News, & Discussion] mattwheat:
In the pic that I'm uploading did your command not have to be written like this

Fastboot flash boot --slot all magisk_patched.img
[Google Pixel 4 XL Guides, News, & Discussion] Reliables2k:
How would one lock the bootloader?

How would one lock the bootloader after unlocking it?

Im assuming the command would be something like:

fastboot flashing lock

Many thanks,

Relaibles2k
[Google Pixel 4 XL Guides, News, & Discussion] CBMC:
Make sure you flash the Google stock image before locking bootloader. If you don't you can brick your phone assuming you have rooted or have a custom rom. But yes, with the 4xl you would use the fastboot flashing lock after flashing the stock image.
[Google Pixel 4 XL Guides, News, & Discussion] madmuthertrucker:
I got my Pixel 4XL today and oem unlock was greyed out. I factory reset it 3 times, no joy. I was about to send it back to Google. For giggles I updated it from December patch to March and that did it. OEM unlock is now in black. I don't see how that makes a difference. Unlocked should be unlocked, regardless of what security patch it's on.
[Google Pixel 4 XL Guides, News, & Discussion] Alexkidd85:
Hi guys. i bought my device from a store that didn't specify that the device could have been verizon.

Sure wasn't the google store, but I'm pretty sure it's a European device. or so they say.

But when i try to flash booting image i receive:

Sending 'boot_a' (32152 KB) OKAY [ 0.219s]

Writing 'boot_a' FAILED (remote: 'Fastboot command (flash:) is not allowed when locked')

fastboot: error: Command failed

what do you tell me? Some idea?

Thanks
[Google Pixel 4 XL Guides, News, & Discussion] Badger50:
Your bootloader is locked. You have to unlock it to fastboot anything. Having said that, if you can't toggle OEM unlocking, then I'm afraid your sunk ?
[Google Pixel 4 XL Guides, News, & Discussion] Alexkidd85:
Thanks, But maybe I had misunderstood, That I could have rooted without unlocking the bootloader.

As in the past! Very Past ?

What do you mean when you say "your sunk"? Is there a possibility that I may not be able to unlock the bootloader?
[Google Pixel 4 XL Guides, News, & Discussion] Badger50:
If you go to settings/system/advanced/Developer options and look for "OEM unlocking" you'll see the toggle switch. If you can turn it on, you can root. If it's grayed out, and can't turn it on, then you can't root, hence, your sunk ?
[Google Pixel 4 XL Guides, News, & Discussion] Alexkidd85:
Yes I can. But if I switch to on, can i root without unlock bootloader? ?
[Google Pixel 4 XL Guides, News, & Discussion] Badger50:
Unfortunately, no. You still have to unlock the bootloader, which in turn, will wipe your device.
[Google Pixel 4 XL Guides, News, & Discussion] marbertshere:
[MENTION=3730810]Badger50[/MENTION] thanks you your help in this thread. If I'm on stable magisk and I want to start using Canary builds, do I need to just select Canary in MM, update, and repatch the stock boot image? Or can I skip any of these steps?
[Google Pixel 4 XL Guides, News, & Discussion] Homeboy76:
Update: SDK Platform-Tools: r30.0.0
[Google Pixel 4 XL Guides, News, & Discussion] dcasun:
thanks

got stuck on my pixel 4xl and saw your answer for p3xl and helped me out thanks :)
[Google Pixel 4 XL Guides, News, & Discussion] Zepzer:
Hello. Thank you OP and everyone else who put help/effort into this thread. With your help I rooted my Pixel 4 X. Now to look up and see what I can do with this root.

Hope you all have a good week
[Google Pixel 4 XL Guides, News, & Discussion] loskiq:
why fastboot flashing boot_b, not boot_a?

is there any difference?

now my pixel 4 xl is in bootloop
[Google Pixel 4 XL Guides, News, & Discussion] chazall1:
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
[Google Pixel 4 XL Guides, News, & Discussion] Homeboy76:
Update: SDK Platform-Tools: r30.0.1
[Google Pixel 4 XL Guides, News, & Discussion] CraigUK87:
Does anyone have an Android 11 patched img they can share?
[Google Pixel 4 XL Guides, News, & Discussion] chazall1:
You should be able to patch. When the pixel 4 xl came out we had to select under settings in magisk when patching the recovery selection.

Do not select the recovery, just the default. You need to hide Magisk for safety net to pass.

Good luck
[Google Pixel 4 XL Guides, News, & Discussion] vanydotk:
Today around 10-11AM PST
[Google Pixel 4 XL Guides, News, & Discussion] Badger50:
When it's ready! ???
[Google Pixel 4 XL Guides, News, & Discussion] TheDude:
Good one Badger :good: :rolleyes:
[Google Pixel 4 XL Guides, News, & Discussion] murphyjasonc:
If it's like the pixel 2 installing the factory image will not wipe your data if you remove the -w in flash-all.bat file.
[Google Pixel 4 XL Guides, News, & Discussion] igknight:
They are up, but there are multiple.
[Google Pixel 4 XL Guides, News, & Discussion] vanydotk:
The factory images are up!
[Google Pixel 4 XL Guides, News, & Discussion] jruizdesign:
https://developers.google.com/android/images#coral
[Google Pixel 4 XL Guides, News, & Discussion] GohanBurner:
Hell yeah! Factory images are up and I'm beating a dead horse, gonna ROOOOOOOOOT!
[Google Pixel 4 XL Guides, News, & Discussion] igknight:
All rooted, time to play!
[Google Pixel 4 XL Guides, News, & Discussion] MicroMod777:
Wow, u guys beat me. I'm at work. Ugg.
[Google Pixel 4 XL Guides, News, & Discussion] gmillz:
Root
[Google Pixel 4 XL Guides, News, & Discussion] gris1016@gmail.com:
Whats the difference between the three ?

---------- Post added at 06:48 PM ---------- Previous post was at 06:45 PM ----------

whats the difference between the three?
[Google Pixel 4 XL Guides, News, & Discussion] aNYthing24:
You should probably use the one that corresponds to your build number on your phone. Or you can update to the latest – which I'm assuming is D1A.190821.011.C4.
[Google Pixel 4 XL Guides, News, & Discussion] MicroMod777:
So after patching image with root

, I just do fastboot flash boot boot.img?

This is my first Pixel rooting only.
[Google Pixel 4 XL Guides, News, & Discussion] JakeDHS07:
Am I missing something or aren't they labeled wrong? I could have sworn "flame" should be the XL and "coral" should be the regular? Are the images swapped as well? Don't want to try and use the wrong one.
[Google Pixel 4 XL Guides, News, & Discussion] gettinwicked:
All you that have rooted, did you grab the latest Magisk canary? Or are you using something different?
[Google Pixel 4 XL Guides, News, & Discussion] aNYthing24:
Is anyone else's system root folder completely full? I'm unable to install AdAway because of this.
[Google Pixel 4 XL Guides, News, & Discussion] ridobe:
Huh. I thought so too. But, all other devices list XL first so go by that.
[Google Pixel 4 XL Guides, News, & Discussion] ifly4vamerica:
Removed double post
[Google Pixel 4 XL Guides, News, & Discussion] Tulsadiver:
Yes, fastboot flash boot magisk_patched.img
[Google Pixel 4 XL Guides, News, & Discussion] 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://xdaforums.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.
[Google Pixel 4 XL Guides, News, & Discussion] kickenwing13:
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 ----------

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 .
[Google Pixel 4 XL Guides, News, & Discussion] 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? :( :(
[Google Pixel 4 XL Guides, News, & Discussion] joseph168:
Adb sideload Telstra OTA, It will fix face unlock issue.
[Google Pixel 4 XL Guides, News, & Discussion] 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.
[Google Pixel 4 XL Guides, News, & Discussion] Lughnasadh:
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.
[Google Pixel 4 XL Guides, News, & Discussion] Spunkybob:
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.
[Google Pixel 4 XL Guides, News, & Discussion] Lughnasadh:
I disabled the Play Store YouTube version and set YouTube Vanced to open YouTube links and it works fine.
[Google Pixel 4 XL Guides, News, & Discussion] Spunkybob:
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.
[Google Pixel 4 XL Guides, News, & Discussion] Lughnasadh:
Try clearing Chrome's Open by default. I have no defaults set in Chrome for link opening.
[Google Pixel 4 XL Guides, News, & Discussion] Spunkybob:
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.
[Google Pixel 4 XL Guides, News, & Discussion] 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?
[Google Pixel 4 XL Guides, News, & Discussion] CyberpodS2:
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.
[Google Pixel 4 XL Guides, News, & Discussion] Badger50:
Deleted.
[Google Pixel 4 XL Guides, News, & Discussion] 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?
[Google Pixel 4 XL Guides, News, & Discussion] Lughnasadh:
See my response in the Magisk thread where you posted the same question.
[Google Pixel 4 XL Guides, News, & Discussion] 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.
[Google Pixel 4 XL Guides, News, & Discussion] Lughnasadh:
Here is a good guide... https://xdaforums.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
[Google Pixel 4 XL Guides, News, & Discussion] Jake81345:
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
[Google Pixel 4 XL Guides, News, & Discussion] Lughnasadh:
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.
[Google Pixel 4 XL Guides, News, & Discussion] Jake81345:
All is done and everything went perfectly that time, I appreciate it man. I'm thinking I wasn't properly updated before. either way Hell Yea!!
[Google Pixel 4 XL Guides, News, & Discussion] Lughnasadh:
Great! Glad you got it going (y)
[Google Pixel 4 XL Guides, News, & Discussion] Jake81345:
One last question. Is there anything special I need to do now when system updates come in?
[Google Pixel 4 XL Guides, News, & Discussion] Lughnasadh:
My preferred method for updating is as follows:

1. Turn off "Automatic system updates" in Developer options

2. Disable all Magisk Mods and Substratum overlays

3. Fastboot flash the new factory image with the -w removed from the flash-all.bat file to keep data

4.Patch the new stock boot image with Magisk

5. Fastboot flash the patched boot image

Here is a good guide: https://xdaforums.com/t/guide-root-pixel-4-xl-android-11-r.4160441/
[Google Pixel 4 XL Guides, News, & Discussion] 100kaa:
I have lost GooglePay yesterday. Does anyone knows or have experienced the same? I have tried to do same thing which helped me first time after rooting the phone, but none of the settings are changed. :rolleyes:
[Google Pixel 4 XL Guides, News, & Discussion] Lughnasadh:
Check over in the new safetynet fix thread. Google made some server-side changes the other day and you probably need to flash the safetynet fix mod as well as clearing cache/data from Google Pay and Google Play Services. https://xdaforums.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/
[Google Pixel 4 XL Guides, News, & Discussion] 100kaa:
@Lughnasadh

Thanks a lot. It should be working now. :)
[Google Pixel 4 XL Guides, News, & Discussion] madmartian:
First time I went through the process last year it worked great. But I forgot to turn off automatic updates. No biggy, I thought, I'll just patch the boot img of the new version and I'll be back to working. Nope. I get the "G" screen with endless loading animation. I have tried both of the following commands (on different tries):

fastboot flash boot magisk_patched.img

fastboot flash boot --slot all magisk_patched.img

Same endless load screen either way. I know I am using the correct boot img and when I flash the phone with the unpatched boot img to get my phone working again, it boots just fine. I still get the warning message on boot that my bootloader is unlocked so I know my bootloader is still unlocked.

Note that I also tried removing magisk modules via adb as some people advised:

adb wait-for-device shell magisk --remove-modules

Sadly, that stops the phone from booting entirely (keeps booting back to bootloader) and I have to reflash the patched module. Which then gets stuck on the G screen as usual.

Any idea what I can do to get root working again? I definitely have the latest Canary build of Magisk, loaded just yesterday. Stock ROM I am working with is 11.0.0 (RQ1A.210105.003, Jan 2021). I've been rooting and playing with custom ROMs for more than a decade and this is the first time I've been stumped.
[Google Pixel 4 XL Guides, News, & Discussion] Lughnasadh:
Recently someone had a similar problem and solved it by using PowerShell instead of Command prompt. Worth a try. Also, they mentioned they ran it either as administrator or not as administrator (can't remember which one), so may be worth trying it both ways as well.

EDIT: Additionally, make sure your Platform Tools are up-to-date. If the above doesn't work may have to try fastboot flashing the factory image or doing a factory reset and then trying again.

EDIT 2: Are you using the new name of the patched boot image in the command instead of magisk_patched.img ? There is now a suffix added.
[Google Pixel 4 XL Guides, News, & Discussion] madmartian:
Yes, I am using the full name with the suffix. Just left it off the post for simplicity. Platform tools are the latest. Culprit is likely allowing the factory update to happen without first clearing all the modules. I will try Powershell with the module removal command and see if it makes a difference. The problem with starting over with a clean wipe is I can't use Titanium Backup until it's rooted again. :)
[Google Pixel 4 XL Guides, News, & Discussion] madmartian:
I FIXED IT!!!

So the command "adb wait-for-device shell magisk --remove-modules" continued to cause the same problem, even after the February update and a new version of Magisk Manager. I read something about booting in safe mode automatically telling Magisk to disable all modules AND THAT WORKED!!!

So, once you experience the module-induced boot freeze at the G screen, do the following:

Hold the power button until the screen blacks

If it reboots into fastboot, boot again. If you can't get out of fastboot, flash the magisk patched file again and reboot

As soon as the Google logo appears, press and hold Volume Down. Keep it pressed until the "safe mode" logo appears in the lower left.

Wait for boot to finish. Give it an extra minute to be sure. Now reboot.

This time it will boot normally. Turn off airplane mode!

Run Magisk Manager and you will see all modules have been disabled.

Make sure you have the latest version of each module.

Enable one at a time and reboot until booting hangs again.

You have found the module causing the problem,. Repeat the safemode thing and remove the bad module.

Yippee! Problem solved! Root works again!
[Google Pixel 4 XL Guides, News, & Discussion] mattwheat:
my bootloader is unlocked but im still getting this

target reported max download size of 268435456 bytes

sending 'boot' (65536 KB)...

OKAY [ 1.491s]

writing 'boot'...

FAILED (remote: Failed to write to partition Not Found)

finished. total time: 1.570s

why
[Google Pixel 4 XL Guides, News, & Discussion] mattwheat:
Ive extracted the boot.img from the exact build that my phone is on. I transfered it to my phone from my pc. Then opened Magisk and patched it. Then transfered back to my pc. Then did the

"fastboot flash boot magiskpatchedboot.img"

I didn't actually type magiskpatchedboot.img. I typed the name that Magisk named it after it patched it.

But I keep getting an error failed to write to remote to partition. Not found.

Any help would be greatly appreciated.
[Google Pixel 4 XL Guides, News, & Discussion] madmuthertrucker:
Some of these guys know a lot more than me. Are you on canary version? I would flash stock boot.img to both slots then come back and try again. I say that because that is all that I know to try. But it's worth a shot.

fastboot flash boot boot.img --slot all
[Google Pixel 4 XL Guides, News, & Discussion] Lughnasadh:
First thing would be to make sure your platform tools are up-to-date.
[Google Pixel 4 XL Guides, News, & Discussion] mattwheat:
Yeah I didn't have the correct rooted boot.img. I still had an older patched version on my phone from when I rooted a while back. And was pulling that one from my phone to flash thru adb. I had to just clean up my inventory from all the old stuff and start over to ensure I was using all the up to date recently patched .img's. Thanks for the replies.
[Google Pixel 4 XL Guides, News, & Discussion] madmuthertrucker:
I clear out all my old factory images and patched files before I start so I don't get mixed up. Glad you got it straightened out.
[Google Pixel 4 XL Guides, News, & Discussion] elotan:
Hi all

Since it has been 2 years since the guide was published:

1. Does root (Pixel 4 XL) require opening the bootloader?

2. Does opening the bootloader erase / format the device and all its data?
[Google Pixel 4 XL Guides, News, & Discussion] Lughnasadh:
If by "opening" you mean unlocking, then...

1. Yes

2. Yes
[Google Pixel 4 XL Guides, News, & Discussion] elotan:
This was what I meant, yes (bad English).

Thank you very much for your answer. Unfortunately, I'm afraid it means no root for me. I'm 18 months with the device and cannot (or at least don't want to) start from scratch after a complete wipe / factory reset.
[Google Pixel 4 XL Guides, News, & Discussion] MySelf_v1:
I've installed LineageOS without rooting. Is there any way to root while on LOS?

edit: just answered by myself. YES. Download the Factory Image, Extract, Patch and Flash
[Google Pixel 4 XL Guides, News, & Discussion] Homeboy76:
Magisk Beta/Stable Update

Magisk-v26.4

[MagiskBoot] Don't pad zeros if signed boot image is larger

[MagiskPolicy] Fix genfscon and filename_trans

[MagiskPolicy] Fix bug in libsepol

[Zygisk] Fix and simplify file descriptor sanitization logic

[App] Prevent OOM when patching AP tarfiles

[App] Fix bug in device configuration detection

[Daemon] Fix certificate parsing of APKs

[General] Fix logging errors from C++ code being ignored

Magisk Canary Update

app-release (0352ea2c) (26302).

Sync with public release

Diffs to v26.4

N/A

Download

Tap app-release.apk

Tap the three dot menu across from

Code

Blame

Tap Download
[Google Pixel 4 XL Guides, News, & Discussion] ifly4vamerica:
I cant remember exact steps but that fix is on adaway FAQ.
[Google Pixel 4 XL Guides, News, & Discussion] Tulsadiver:
Yes, I used the canary magisk manager to patch boot.img

---------- Post added at 02:27 PM ---------- Previous post was at 02:23 PM ----------

Here you go!

https://mega.nz/#!lco3hQbA!5HtqftolKOHPw0iCFmBgbbFin8sfh1_UAZB9pFwJB_0
[Google Pixel 4 XL Guides, News, & Discussion] ifly4vamerica:
Sorry replied to wrong post Initially Tulsadiver would you be so kind as to share the stock boot.img? On a plane and DL for all of the image is now up to 5 hours..