yashsingh1/xdaforums huggingface dataset:
[Google Pixel 4 XL Guides, News, & Discussion] jermzrdc:
I was able to unlock my bootloader with Tool All In One by Senerex from the whyred Mi Note5 Pro forum. I just set my phone to pixel 3 and clicked unlock bootloader and phone restarted and was wiped checked and OEM Unlocking is greyed out.

Original thread by mauronofrio

https://xdaforums.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711
[Google Pixel 4 XL Guides, News, & Discussion] Badger50:
No surprise if you don't have a true google variant device.
[Google Pixel 4 XL Guides, News, & Discussion] jermzrdc:
Are you saying my device isn't a true Google pixel 4? I beg to differ due to my purchasing from my mobile provider.
[Google Pixel 4 XL Guides, News, & Discussion] Badger50:
Not saying that at all. I'm saying that if you purchased the device from google, best buy, or wherever, and it's a bootloader unlockable device, then yes, you can unlock it. However, if you purchased it from a carrier, "phone company" as you stated, then it is likely it can't be unlocked until it's paid off, if even then. What carrier did you buy it from?
[Google Pixel 4 XL Guides, News, & Discussion] jermzrdc:
I'm in Canada where phones come carrier unlocked and my provider is Fido. Is it possible that that one script works for it due to some things being similar to the pixel 3? that program in a tool for a lot of devices.
[Google Pixel 4 XL Guides, News, & Discussion] jermzrdc:
Here are screen shots
[Google Pixel 4 XL Guides, News, & Discussion] Badger50:
Carrier unlocked is much different than bootloader unlockable. That tool you mentioned will likely not work on a pixel. If you can't manually toggle OEM unlocking, then you can't unlock the bootloader. You might want to talk to your carrier about the matter.

---------- Post added at 02:25 PM ---------- Previous post was at 02:11 PM ----------

Then judging from your screen shot, you were successful. And greyed out in the on position is a good thing :good:
[Google Pixel 4 XL Guides, News, & Discussion] jermzrdc:
I also went back to fastboot mode and saw the status as unlocked but couldn't take a screenshot.
[Google Pixel 4 XL Guides, News, & Discussion] dtroup64:
Re Locking

Probably missing something really obvious... but.

I always like to be ready for anything, so I've been trying to re-lock my bootloader in case I ever truly need to.

I followed the process listed in the OP. I completely wiped and factory reset.

After setting my device back up I entered fastboot mode

fastboot flashing lock

it asked me for confirmation. I used the power keys to accept.

I performed fastboot reboot

I get a message that there is no operating system and that I need to go to g.co/ABH.

I then have to re-unlock the bootloader to be able to reboot my device.

What am I missing? Thanks for any help!!
[Google Pixel 4 XL Guides, News, & Discussion] CraigUK87:
IS there any chance someone could make a stock back up img of the nov update. UK version. I need to update to Dec and i can't for the life of me find the boot.img from the OTA. I literally can not find it lol.... I want to unroot to update, 3 hours i've been trying to sort this :( wheres our TWRP when we need it.
[Google Pixel 4 XL Guides, News, & Discussion] Badger50:
You won't find a boot.img in an OTA. It's called payload.bin. Your best bet is to download the coinciding factory image from here...https://developers.google.com/android/images

Then extract the zip, then extract the residing image.zip, pull the boot.img out of that and use it as you wanted :good:
[Google Pixel 4 XL Guides, News, & Discussion] CraigUK87:
Mate, i'm a bloody idiot...I was downloading the OTA instead of the Factory img. ahahahaha, I literally feel like an idiot. Alll flashed and fixed now lol, just need to root. Thank you.
[Google Pixel 4 XL Guides, News, & Discussion] Badger50:
Meh...no worries mate, we all have the occasional brain farts here and there ???
[Google Pixel 4 XL Guides, News, & Discussion] CraigUK87:
Brain fart indeed, sir. I also managed to connect my phone to the rig. Had to update the MTP file in device manager. All good now. Thanks again mate, much appreciated.
[Google Pixel 4 XL Guides, News, & Discussion] eg1122:
All I can think of is that the phone is not at 100% factory state. Best bet would be to flash latest full firmware zip and then relock.
[Google Pixel 4 XL Guides, News, & Discussion] Falargi:
Correct image for unlocked pixel 4 XL

I just flashed the December image onto my Pixel 4 XL purchased from the google store. The issue I am having is with Face Unlock. It's not working. When I flashed November I ran into the same issue and someone pointed out about having flashed the incorrect image, which at that time I corrected and everything was fine.

How do I know which is the correct image I need to flash this time? I am coming from QD1A.190821.007.A3 (November).

Can someone point me to the correct image? I will appreciate your help.
[Google Pixel 4 XL Guides, News, & Discussion] Homeboy76:
https://support.google.com/pixelphone/thread/21769134?hl=en/
[Google Pixel 4 XL Guides, News, & Discussion] dtroup64:
Pretty sure that was the issue. Thanks.
[Google Pixel 4 XL Guides, News, & Discussion] localceleb:
Trying to flash patched boot.img after doing the dec update and keep getting this. Any ideas?
[Google Pixel 4 XL Guides, News, & Discussion] Badger50:
Did you try what I recommend in your other post?
[Google Pixel 4 XL Guides, News, & Discussion] localceleb:
I'm not seeing that suggestion, sorry. I am used to navigating through tapatalk and not the xda site.
[Google Pixel 4 XL Guides, News, & Discussion] Badger50:
Ok. Did you extract the factory image, and place the extracted contents in your platform-tools folder? If so, have you manually tried switching slots and flash it again?
[Google Pixel 4 XL Guides, News, & Discussion] localceleb:
I got the Dec factory image straightened out, but now it doesn't want to take the magisk patched boot file for some reason.
[Google Pixel 4 XL Guides, News, & Discussion] Badger50:
Did you try switching slots? Or, try flashing it to both slots with....

fastboot flash boot magisk_patched.img --slot=all

Hopefully one of 2 will work.
[Google Pixel 4 XL Guides, News, & Discussion] localceleb:
Sent you a PM
[Google Pixel 4 XL Guides, News, & Discussion] Badger50:
Didn't get it :confused:
[Google Pixel 4 XL Guides, News, & Discussion] localceleb:
This is what I get with those commands
[Google Pixel 4 XL Guides, News, & Discussion] Madjax2020:
Try another PC I had the same issue trying to restore my pixel 4 XL. Once I changed PC's ... worked like a charm.
[Google Pixel 4 XL Guides, News, & Discussion] localceleb:
Yes, I have tried 3 different computers now and I get the same result with each one. There has to be something that I'm overlooking, but I can't figure out what that would be....

\platform-tools> fastboot flash boot magisk_patched.img

target reported max download size of 268435456 bytes

sending 'boot' (32112 KB)...

OKAY [ 0.781s]

writing 'boot'...

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

finished. total time: 0.854s
[Google Pixel 4 XL Guides, News, & Discussion] Badger50:
Few more things I can think of. 1. Are your platform-tools on your desktop? If so, does it have administrator rights? 2. When you patched the boot.img, did you have AVB 2.0/dm-verity checked off? 3. Have you tried opening a command prompt directly on the platform-tools folder instead of typing in a pathway? 4. Did you get your platform-tools from here? https://developer.android.com/studio/releases/platform-tools.html
[Google Pixel 4 XL Guides, News, & Discussion] localceleb:
1. Yes they are on my desktop and they do have admin rights. 2 when I patched the my boot.img AVB was left unchecked--is this correct? 3. I always open a command prompt from the location itself. 4. Yes, I even redownloaded the platform tools this morning on all of my machines.

[emoji1745]
[Google Pixel 4 XL Guides, News, & Discussion] Homeboy76:
:eek::rolleyes::eek:

Just curious is fastboot.exe in c:\users\mike\desktop?
[Google Pixel 4 XL Guides, News, & Discussion] localceleb:
Here is everything currently living in the platform tools folder... Anything look out of place?
[Google Pixel 4 XL Guides, News, & Discussion] Badger50:
Then all I can think of is to patch the boot.img again with dm-verity checked on. If all else fails, here is a link to my stock December boot.img and patched.img. Another user had a similar issue to yours and this worked for him.

https://drive.google.com/file/d/18FqwDgmCE6zsiENxNTlrUqlEa35X64E7/view?usp=drivesdk
[Google Pixel 4 XL Guides, News, & Discussion] localceleb:
Your files didn't work either. I am getting this message whenever I try to flash any boot.img

FAILED (remote: Failed to write to partition Not Found)
[Google Pixel 4 XL Guides, News, & Discussion] Badger50:
Then like [MENTION=4810220]Homeboy76[/MENTION] stated a couple of posts before yours. Is fastboot.exe in your :C drive?
[Google Pixel 4 XL Guides, News, & Discussion] Homeboy76:
[MENTION=1889937]localceleb[/MENTION]

Is this your platform-tools folder, c:\users\mike\desktop?

If not, open a command prompt in the folder with fastboot.exe in (see #1) in this guide.
[Google Pixel 4 XL Guides, News, & Discussion] localceleb:
[MENTION=4810220]Homeboy76[/MENTION]

Yes, it was at the time of that screenshot. I have moved it around to different locations and have gotten the same result each time. Currently in c:/Android/platform-tools
[Google Pixel 4 XL Guides, News, & Discussion] Homeboy76:
Look at #1, #4 'Keep data', and #9 in the guide , and make sure your USB cord is not plugged in a 'charging' USB port on your computer.
[Google Pixel 4 XL Guides, News, & Discussion] localceleb:
[MENTION=4810220]Homeboy76[/MENTION] [MENTION=3730810]Badger50[/MENTION]

I would like to thank the few people that are in this thread that were helping me over the past couple of days. For whatever reason this process was giving me some trouble and I've been in the Android game for quite some time and usually am able to troubleshoot/research a fix. I was having issues flashing boot images and tried everything that I could think of and everything that all of the experienced users here were suggesting and nothing was working. Well this morning I figured it out. I was using Windows PowerShell command window (which I've used in the past with no issues) and I decided to try and use a basic cmd window and navigate to my platform-tools folder. That worked! I am all good and now I can focus on regrowing all of the hair that I pulled out. Thanks everyone!
[Google Pixel 4 XL Guides, News, & Discussion] Badger50:
Well done my friend. Persistence always pays off. I forgot about the dang power shell thing. Sorry we didn't think of that. Oh well, at least you know all the other tricks now! ????
[Google Pixel 4 XL Guides, News, & Discussion] Homeboy76:
:good: good job! :good::)

---------- Post added at 09:29 PM ---------- Previous post was at 09:28 PM ----------

We can't think of everything, that's why we have the XDA community:)
[Google Pixel 4 XL Guides, News, & Discussion] Badger50:
Shoot brother, I have a hard time just thinking period! ??
[Google Pixel 4 XL Guides, News, & Discussion] ceo.mtcl:
Hey Badger50 and others in the thread. I've read this thread and it's so useful. All you guys are so helpful, I really love the xda community!

I setup my pixel 4 XL without unlocking the bootloader. I really want to root but don't want to loose data. Sigh, that won't be possible. I see that most of you are able to use OTA month after month without losing data. Is there a guide to it? This is the scenario I'm talking about:

1. Bootloader unlocked

2. Rooted with magisk

3. All setup with Google accounts, WhatsApp, Facebook etc etc...

4. Currently on November update

5. I want to update to December OTA update without losing root and redoing tedious setup of all accounts in step 3.

What would be the most agreed upon way of doing this?

Thanks again guys for all the help.
[Google Pixel 4 XL Guides, News, & Discussion] CyberpodS2:
I've actually not done December yet but...

Personally I will remove any and all security (I guess it'll be the face thing too) then uninstall Magisk and any modules, substratum if it's installed, flash the full factory image (never did feel the need to use OTA ) with the -w removed then reboot and see if all it's good to go. If so I'll patch my own boot.ing so I have a backup if needed. If it does not work I'll try the one [MENTION=3730810]Badger50[/MENTION] uploaded.

If on the other hand the update flash does not go as planned I will be ready for a full restart from scratch. Far too many folks this week hit snags so I think maybe 2 hours of troubleshooting will be my threshold before I start over. Seems like this month was big enough to hurt. Lol

As for troubleshooting, flashing the image to both a and b will be my first step then manually flashing the stock boot and dtbo images to both sides them go from there.
[Google Pixel 4 XL Guides, News, & Discussion] Badger50:
It's like my buddy [MENTION=4565594]CyberpodS2[/MENTION] stated. Most of us regulars like fastbooting the monthly factory images vs the OTA's, why, because we think it's the most reliable way to update with the fewest problems, and easier to solve if problems arise. There is a way to update via OTA and maintain root, however, it seems as of late, the process has had some issues, I'll try and find that thread for you. Updating the monthly updates with your pc and factory images is not as complicated as you might think, and, you can maintain data month to month if you wish. The guide in the OP will definitely get you on the right path. Not to mention, if you run into trouble, there are many of us here to help :good::cool:
[Google Pixel 4 XL Guides, News, & Discussion] Homeboy76:
ROTFLMAO! The only problem I have is occasionally that CRS (Can't remember s#$t) disease will attack me.
[Google Pixel 4 XL Guides, News, & Discussion] Gloff:
This worked for me, I could not get --slot all to flash it CMD kept telling me that it wasn't a recognized command. I flashed to both slots. So if you're getting the below, flash the boot image using the command above.

target reported max download size of 268435456 bytes

sending 'boot' (32092 KB)...

OKAY [ 0.781s]

writing 'boot'...

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

finished. total time: 1.074s

PS C:\platform-tools-new>
[Google Pixel 4 XL Guides, News, & Discussion] Homeboy76:
Just curious

Did you have SDK Platform-tools r29.0.5 installed on your computer? When this command - fastboot flash boot magisk_patched.img --slot all - didn't work for you?
[Google Pixel 4 XL Guides, News, & Discussion] ecsnead69:
Has anyone here seen or heard of anyone running a custom rom on the 4 XL? I'm hearing people are sideloading them somehow. If so, can somebody point me to where to find them.. thanks
[Google Pixel 4 XL Guides, News, & Discussion] CyberpodS2:
Since you mentioned it here, can you please post the link to the latest minimal tools if you know it? My link I have is broken and my searches keep coming up with crappy 3rd party stuff instead of a Google url.
[Google Pixel 4 XL Guides, News, & Discussion] Badger50:
Here ya go bruh :good:

https://developer.android.com/studio/releases/platform-tools.html
[Google Pixel 4 XL Guides, News, & Discussion] CyberpodS2:
Thanks man. Looks like I was using some link that was shortened and it expired. This is exactly what I need!!
[Google Pixel 4 XL Guides, News, & Discussion] Homeboy76:
SDK Platform Tools.
[Google Pixel 4 XL Guides, News, & Discussion] Madjax2020:
hi all, I was playing with xposed and installing it. well now im trying to reflash the magisk_patched img file and it just stays at the G logo and wont finish the boot. I can flash the regular boot.img file and it will boot fine. ideas? maybe I can try and make slot A active since it shows b is active now?

help would be amazing.
[Google Pixel 4 XL Guides, News, & Discussion] Badger50:
Try fastbooting the patched boot.img to both slots first. If it's a no go, then try flashing the factory image to your inactive slot without the -w, then try fastbooting the patched boot.img again. I suspect that your exposed module is causing you some trouble.
[Google Pixel 4 XL Guides, News, & Discussion] Madjax2020:
I'm back to stock 100%. With the -w option.

Booted up and setup phone

Installed magisk

Used magisk to patch the boot.img file in the stock zip file.

Tried flashing the magisk_patched.img file and bootloops.

I'm still OEM unlocked and checked in fastboot flashing is unlocked.

Dev options enabled

What am I missing? Can not even root my pxl4
[Google Pixel 4 XL Guides, News, & Discussion] Badger50:
Are you by chance using Power Shell while trying to enter your fastboot commands, or opening your cmd directly on your platform-tools?
[Google Pixel 4 XL Guides, News, & Discussion] Madjax2020:
[MENTION=3730810]Badger50[/MENTION], you my friend are an effing rockstar with your very fast replies and insane knowledge. I have fixed my issue, I was patching with recovery enabled after flashing back to stock
[Google Pixel 4 XL Guides, News, & Discussion] Badger50:
While I appreciate the kind words, I did not fix your problem, you did my friend! I didn't even think that patching the boot.img with recovery enabled on the magisk app may cause a bootloop. Chalk another one up to the bag of tricks we need at times. Well done! :good::good:
[Google Pixel 4 XL Guides, News, & Discussion] Light1984:
Ok guys, been out of the game for awhile, coming from an HTC 10. I've got an Unlocked Pixel 4 coming straight from Google that I intend to use on Verizon. Do I still download the full firmware and patch the boot.img for the version that matches what comes on the unlocked phone or do I need to get a Verizon version of the firmware and patch? I saw someone talk about this a few pages back but I don't see a VZW version on the factory image page. Also curious how to get tethering working, saw that talked about briefly too, something about having to use a magisk module to do it systemlessly, but I couldn't find the module. TIA
[Google Pixel 4 XL Guides, News, & Discussion] Badger50:
I too am a Verizon custom, I used the .012.A1 version for the December update https://support.google.com/pixelphone/thread/21769134?hl=en

You will need to download the factory image, extract it, then extract the secondary image.zip in order to get the boot.img to patch with magisk, and then fastboot the patched image. I think I remember seeing a tethering thread in the Q & A section on the P4XL forums :good:
[Google Pixel 4 XL Guides, News, & Discussion] Light1984:
So you have an Unlocked phone from Google and you're on Verizon?
[Google Pixel 4 XL Guides, News, & Discussion] Badger50:
Correct. And WiFi calling works just fine as well :good:
[Google Pixel 4 XL Guides, News, & Discussion] Light1984:
Awesome, if you come across that tethering thread, please let me know. That's my main reason for root. Thanks
[Google Pixel 4 XL Guides, News, & Discussion] Madjax2020:
If I go to the link to update to dec I only use the OTA file for my build?

QD1A.190821.007

I'd use .. (QQ1B.191205.012.A1, Dec 2019)? That doesn't match by build .007, or is there no update to dec for me yet?
[Google Pixel 4 XL Guides, News, & Discussion] Badger50:
The builds do not match from month to month. What carrier you on should be your guide to your proper December update version :good:

https://support.google.com/pixelphone/thread/21769134?hl=en
[Google Pixel 4 XL Guides, News, & Discussion] Madjax2020:
Thank you my friend, I'm Verizon and I'm going to use the all other carriers. I'll tackle this today, after the vet, taking brownies to school for a party, and after replacing the 6 fuel injectors.
[Google Pixel 4 XL Guides, News, & Discussion] Badger50:
Yep, use the .012.A1 version for Verizon. I remember those days! That's why retirement is flippin awesome! ???
[Google Pixel 4 XL Guides, News, & Discussion] Gloff:
Good question, I'll have to check tonight, I may be on an older version

---------- Post added at 11:47 PM ---------- Previous post was at 11:44 PM ----------

I got you fam https://xdaforums.com/pixel-4-xl/how-to/how-to-native-tethering-rooted-pixel-4-t3993405
[Google Pixel 4 XL Guides, News, & Discussion] Light1984:
My man!!! Thank you.
[Google Pixel 4 XL Guides, News, & Discussion] Gloff:
Helps that I wrote it, so I always know where it is haha
[Google Pixel 4 XL Guides, News, & Discussion] Assafaviv:
After unlocking the bootloader and flashing the boot image from magisk, the device stoped recognize my face to unlock it, and after trying to flash the factory image, the lock screen is totally black, and the icons of the battery and the clock are flicking :( what should I do ? Thanks
[Google Pixel 4 XL Guides, News, & Discussion] Badger50:
Factory reset, then root it again :good:
[Google Pixel 4 XL Guides, News, & Discussion] Assafaviv:
Nothing helped :( it always returns to a situation that the lock screen is black, and the icons of the battery and clock are flicking
[Google Pixel 4 XL Guides, News, & Discussion] Badger50:
Then try fastbooting the factory image. I assume your on the December update?
[Google Pixel 4 XL Guides, News, & Discussion] Assafaviv:
I have tried all of them with no change ?
[Google Pixel 4 XL Guides, News, & Discussion] Badger50:
Ok. Then you have 2 choices. Either you do a full wipe, then fastboot back to the November update, then dirty fastboot to the December update. Or, wait for the January update :good:
[Google Pixel 4 XL Guides, News, & Discussion] Assafaviv:
What's the difference between dirty and not dirty? I don't want to make a mistake
[Google Pixel 4 XL Guides, News, & Discussion] Badger50:
Dirty simply means removing the -w from the flash-all.bat file so as not to wipe data :good:
[Google Pixel 4 XL Guides, News, & Discussion] Assafaviv:
Ok thanks I'll try it, but since all the facts till now, im very sceptical
[Google Pixel 4 XL Guides, News, & Discussion] Badger50:
It has been reported by other users that clean fastbooting the December update messed up face unlock and caused wonky status bar displays. I dirty flashed from November to December, and have no issues. Which is why I recommended what I did. Can't make any promises of course, however, the solution does seem plausible :good:
[Google Pixel 4 XL Guides, News, & Discussion] Assafaviv:
I did exactly what you suggested, when the device loaded it tells me that it can include two sims (not true), the face unlock still not possible to turn off, and again, when I am clicking on power button, and clicking again to awake the device, I see the battery and clock icons are flicking :(
[Google Pixel 4 XL Guides, News, & Discussion] Badger50:
Was everything ok on the November update?
[Google Pixel 4 XL Guides, News, & Discussion] Assafaviv:
Unfortunately no .... :eek:
[Google Pixel 4 XL Guides, News, & Discussion] Badger50:
Crap! Then, if your willing, and a factory reset didn't work, go back to October, then dirty flash forward. Did you by chance dirty flash to both slots with December?
[Google Pixel 4 XL Guides, News, & Discussion] Assafaviv:
sorry I didn't understand you ... BTW, there are 3 of october, how do I know which to choose?
[Google Pixel 4 XL Guides, News, & Discussion] Badger50:
Who's your carrier? And what didn't you understand?
[Google Pixel 4 XL Guides, News, & Discussion] Assafaviv:
my carrier is 012 Mobile in Israel. it on Partner's infrastructure... the device is Unlocked.

---------- Post added at 11:23 PM ---------- Previous post was at 11:22 PM ----------

by the way I just realised that the sensor of squeeze also doesnt work
[Google Pixel 4 XL Guides, News, & Discussion] Badger50:
Did face unlock ever work for you? I ask because soli doesn't work in all countries :confused:
[Google Pixel 4 XL Guides, News, & Discussion] Assafaviv:
Sure it worked great! but the radar doesnt work. so with root I have enforced it, and it also worked.

the sensors of pinch also worked