yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
8.0 Factory image, TWRP, Magisk, Flash Kernel easy steps

After flashing unlock and critical unlock (via fastboot)

flashing the Nov factory img (using Magisk patched_boot.img)

flashing FLASH kernel 1.01 (via fastboot, with Magisk pacthed_boot.img)

I finally installed TWRP and latest FLASH kernel (1.06) using these steps: (thanks to Nekromantik for the basic outline)

*this was used for 8.0, not sure if anything would be diff for 8.1

prep:

* put TWRP 3.1.1 beta 2 IMG in same folder as platform tool, for flashing in fastboot

* put TWRP 3.1.1 beta 2 ZIP in sdcard, for installing in TWRP

* put flash kernel 1.06 ZIP in sdcard for installing in TWRP

* put (Magisk 14.5-1456) in sdcard for installing in TWRP

Booted into TWRP using fastboot

(use TWRP IMG file placed in platform tools folder)

fastboot boot <twrp filename.img >

Flashed TWRP zip

(from within TWRP choose INSTALL and find the ZIP file placed on your sdcard)

rebooted to twrp

(deselect install TWRP app, reboot into recovery)

flashed flash kernel

(placed in sdcard, INSTALL in TWRP, be sure to use the ZIP version, if you use the IMG version you have to reinstall TWRP zip AFTER installing the kernel)

flashed magisk zip

(placed in sdcard, (use 14.5-1456) and it will install 5.4.3 Magisk Manager automatically)

reboot system

profit!

When you're ready to go to 8.1 go HERE
[Google Pixel 2 XL Guides, News, & Discussion] ikithme:
I'm going to take a wild guess and say you can't relock the bootloader completely after this process?

This is my first pixel device and I've had the nexus 6 before which after rooting I could relock, hence why I'm curious.
[Google Pixel 2 XL Guides, News, & Discussion] jrbxx7:
Yes u can, if you need to send in. You can't relock and keep root
[Google Pixel 2 XL Guides, News, & Discussion] ikithme:
Ah yeah that was my question, I know you can relock to send it in but on the Nexus 6 I had very specific procedures to have root and relock the bootloader.
[Google Pixel 2 XL Guides, News, & Discussion] myfeetitch:
"error: no devices/emulators found

After step "3 In your terminal, type the following command:

Code: adb reboot bootloader"

I get "error: no devices/emulators found"

What am i missing?
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
These are the commands I used:

fastboot devices (if this shows a serial number, it recognizes your device)

then:

fastboot reboot bootloader (to get you into the bootloader)
[Google Pixel 2 XL Guides, News, & Discussion] myfeetitch:
It blinked for a second then put the prompt back up, no serial number.
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
Do you have the latest platform tools installed?

If not, get the latest SDK tools

Are you using a USB 3.0 cable?

If so, try a USB 2.0
[Google Pixel 2 XL Guides, News, & Discussion] myfeetitch:
I only have the 6 inch usbc to usb cable that came with my nexus 6p. i had it plugged into an usb extension cord, just tried it without the usb extension, then again without extension after downloading sdk tools again from link in the guide. Same outcome from each try.
[Google Pixel 2 XL Guides, News, & Discussion] Schroeder09:
Idk if it's drivers or what but I was getting the same thing on one of my laptops. I spent a couple hrs messing with drivers, different cords, etc. I saved my ADB and fastboot took in a folder on a USB.

Finally I went and tried another computer. I popped the USB in, launched my fastboot commands from it, and everything worked. It saw the device. I did nothing different. This was after making sure it saw my device as a pixel 2 and selecting the USB synch type as file transfer.

Something in the two PCs was different. I couldn't figure it out and don't really intend to. I suggest trying another PC if you have access to one.
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
Willing to bet it is your cable. Seems like for some unknown reason, MANY users (myself included) have had issues using the 3.0 cables...

All the steps I suggested worked for me, so I blame the cable :D
[Google Pixel 2 XL Guides, News, & Discussion] drewski_1:
the Google ADB / USB drivers ;)
[Google Pixel 2 XL Guides, News, & Discussion] myfeetitch:
Using another pc worked like a charm, thanks for all your help.
[Google Pixel 2 XL Guides, News, & Discussion] marbertshere:
Hey Nathan, the first time I tried to unlock my device using the critical command, it just didn't take for whatever reason. The second time i tried doing it with the unlock command, it worked. I'm currently rooted and using your kernel. I plan on flashing twrp and other boot images./zips Long story short, do you advise that I relock the bootloader and unlock it using the critical command? Do i have to do anything (e.g., flash stock boot image) before relocking and unlocking the device?
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
You can run just the critical unlock command in fastboot even after being unlocked. It will erase your device though, so be prepared.

I did the same thing just the normal unlock, then a week or so later, did the critical unlock. No problems.
[Google Pixel 2 XL Guides, News, & Discussion] drothenberger:
My unlocked and rooted Pixel 2 XL is showing L1.
[Google Pixel 2 XL Guides, News, & Discussion] DJBhardwaj:
Is there something with the P2XL with OCT security patch and Magisk?

1) Booted TWRP

2) Flashed installer

3) Flashed custom kernel (Flash)

4) Rebooted into OS (Booted fine!)

5) Rebooted into TWRP and flashed Magisk (Tried both 17.1 and 17.3)

6) Bootloops into TWRP after about a minute :D

Anything I missed?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
You didn't miss anything my friend. It's just the bipolar nature of the P2XL. I used the same method as you did which worked fine. Here's a few things to try.

In twrp, flash the magisk uninstaller, then immediately flash magisk 17.1.

Or, flash the stock boot.img, then fastboot into twrp, then flash your kernel and magisk 17.1. If that sticks, then go back and install twrp if you want to.

Make sure your fastboot is up to date as well.

Let us know how it turns out :good:
[Google Pixel 2 XL Guides, News, & Discussion] DJBhardwaj:
Thanks for the reply!

So, I cross-checked and fastboot is up-to-date.

Attempt 1:

Boot TWRP, flash Magisk uninstaller, and then re-flash Magisk 17.1 -> Stuck at boot logo and reboots back to TWRP

Attempt 2:

Boot TWRP, flash kernel and Magisk 17.1, and reboot -> Same result

Okay. So, I am gonna start from scratch by flashing the factory image and will report how it goes.
[Google Pixel 2 XL Guides, News, & Discussion] DJBhardwaj:
Re-flashed the factory image and followed the same drill as earlier. Booted in a go! Again, thanks for your input. :highfive:
[Google Pixel 2 XL Guides, News, & Discussion] MrWhite0429:
Thanks for the guide! it was extremely simple to follow. I recieved my Pixel 2 XL in the mail today. I couldnt pass up the crazy sales. I took the phone out of the box, and updated to Pie. After that i was rooted in less than ten minutes.
[Google Pixel 2 XL Guides, News, & Discussion] Gordietm:
Since it was on a new bootloader, did you still unlock critical?
[Google Pixel 2 XL Guides, News, & Discussion] MrWhite0429:
Yes.

Installed fastboot and adb package,

Unlock critical

Reboot bootloader

Fastboot twrp Img

Installed magisk
[Google Pixel 2 XL Guides, News, & Discussion] MrWhite0429:
(xda app is not allowing me to edit original post).

Also just to add this in. The only hiccup I noticed was after twrp installation and magisk installation, my device kept telling me no SIM installed after the initial boot. After about three reboots it finally recognised my sim. All has been well since. I'm not sure what to attribute that bug to. However from what I've read about these phones is that they are temperamental at times so that's what I'm going with.
[Google Pixel 2 XL Guides, News, & Discussion] coolsid8:
Coming for a Nexus 6p, rooting Pixel is a mess. I dont why it is so complex. I lost root today when i just removed few magisk modules. Some kernels work directly and don't need rooting again, some don't. It's not consistent. I had to reflash stock again and then flash magisk to get root. Is this a issue because of its partition structure or is it a magisk bug ?
[Google Pixel 2 XL Guides, News, & Discussion] MrWhite0429:
I've found that you don't have to reflash stock. If your bootloader is unlocked and you lose root, just boot back into recovery and flash magisk zip again and it will restore root.
[Google Pixel 2 XL Guides, News, & Discussion] coolsid8:
Didnt work for me. I tried with Magisk 17.1. Had to reflash stock again.
[Google Pixel 2 XL Guides, News, & Discussion] MrWhite0429:
It's been stated in the thread that 17.1 doesn't work correctly for some reason. Try 16.7 and leave it on 16.7. I tried 17.1 and wound up boot looping. I flashed 16.7 and it works perfectly.
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
Why is no one trying 17.3? Because it's beta? The initial 17.3 was borked, and just didn't update, but I've been using the second 17.3 since it dropped with no issues.
[Google Pixel 2 XL Guides, News, & Discussion] jmtjr278:
hello all. i am attempting to flash factory images in fastboot. i downloaded the appropriate file and unzipped it. i am constantly getting this error message

fastboot: error: failed to open zip file 'image-taimen-ppr2.181005.003.zip': I/O error

i am also unable to unlock_critical. it tells me it failed because the bootloader is already unlocked. any help would be appreciated. thanks

---------- Post added at 12:24 PM ---------- Previous post was at 12:19 PM ----------

i was able to individually run the commands located inside the flash-all file and it seems to be working currently. just weird that the script wouldn't run
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
what was the flash all command you used? And was the flash-all.bat file in the same folder as your fastboot application?

If you were ale to flash all the individual files, you probably just missed something on the flash-all command.

Should be just: flash-all <enter>

Sometimes ppl put; flash flash-all, or add the .bat to the filename

You no longer need to run the unlock_critical command if your bootloader is version TMZ20a or later.
[Google Pixel 2 XL Guides, News, & Discussion] jmtjr278:
Much obliged. I did have the factory image in the same place. I just dragged and dropped the flash all into my terminal. Weird. At least I got it working.
[Google Pixel 2 XL Guides, News, & Discussion] xDakos:
It happend to me once that magisk and my root just vanished and I just had to fastboot twrp and flash magisk again no bootloops at all maybe just bad luck but after 2 months

At least all those bootloops problems got fixxed pretty much rooting the pixel on pie is so easy now and fast. It was way harder when pie was new
[Google Pixel 2 XL Guides, News, & Discussion] Bucika:
Hey guys!

I thought I know what I am doing.. but apparently I didn't. So I just brought new Pixel 2XL 128gb variant, in August 25.. got it last week.. and yesterday I've decided to unlock the bootloader.. I was not sure how to unlock.. normal or critical (tried both ways by now) And downloaded the latest image from google.. Press flash all.. first problem: My bootloader was to old (It came with 8.1. installed) so that was a bit of problem.. Anyways the flash went trough Can't determine partition type.

FAILED (remote: GetVar Variable Not found) that's what I always get.. Now every time I try to boot I get your device is corrupted.. and its stuck at google screen.. I don't have any more ideas how to solve this problem.. I've tried boot twrp, it boots, but then my computer dose not detect the phone so I cant install full twrp.img or any other zip as I can't transferee it..

---------- Post added at 11:00 AM ---------- Previous post was at 11:00 AM ----------

Hey guys!

I thought I know what I am doing.. but apparently I didn't. So I just brought new Pixel 2XL 128gb variant, in August 25.. got it last week.. and yesterday I've decided to unlock the bootloader.. I was not sure how to unlock.. normal or critical (tried both ways by now) And downloaded the latest image from google.. Press flash all.. first problem: My bootloader was to old (It came with 8.1. installed) so that was a bit of problem.. Anyways the flash went trough Can't determine partition type.

FAILED (remote: GetVar Variable Not found) that's what I always get.. Now every time I try to boot I get your device is corrupted.. and its stuck at google screen.. I don't have any more ideas how to solve this problem.. I've tried boot twrp, it boots, but then my computer dose not detect the phone so I cant install full twrp.img or any other zip as I can't transferee it..

Edit: I've re-locked the bootloader now the phone says cant find a valid or proper system..
[Google Pixel 2 XL Guides, News, & Discussion] clothednblack:
You can try this https://xdaforums.com/pixel-2-xl/development/tool-deuces-bootloop-recovery-flashing-t3704761

You will need to unlock the bootloader in order to fix your device either way. Sounds like you wiped your system off, have to start from scratch.
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
If you want a step by step guide, there's a link in my sig for going from 8x to 9x. Pretty much everything you need as far as links, fastboot commands etc.

Best of luck!
[Google Pixel 2 XL Guides, News, & Discussion] Bucika:
Thanks, it worked!

Poslano z mojega SM-T819 z uporabo Tapatalk
[Google Pixel 2 XL Guides, News, & Discussion] post-mortem:
Is there a reason why you can't use the latest version of the fastboot executable?
[Google Pixel 2 XL Guides, News, & Discussion] last_nooby:
"fastboot too old; please download the latest version at https://developer.android.com/studio/releases/platform-tools.html"

And I really don't know how to solve it!! (I mean..I downloaded it but no install file!! I copied it into /usr/lib/android-sdk/platform-tools/ I'm using fastboot --version 28.0.1-4986621 that's last..so I don't understand why it's too old!!)
[Google Pixel 2 XL Guides, News, & Discussion] last_nooby:
also:

./fastboot update image-taimen-pq1a.181105.017.a1.zip

extracting android-info.txt (0 MB) to RAM...

--------------------------------------------

Bootloader Version...: TMZ20k

Baseband Version.....: g8998-00253-1809191716

Serial Number........: 711ZPZK0674772

--------------------------------------------

Checking product OKAY [ 0.000s]

Checking version-bootloader OKAY [ 0.000s]

Checking version-baseband OKAY [ 0.000s]

extracting boot.img (40 MB) to disk... took 0.173s

archive does not contain 'boot.sig'

archive does not contain 'boot_other.img'

extracting dtbo.img (8 MB) to disk... took 0.026s

archive does not contain 'dtbo.sig'

archive does not contain 'dt.img'

archive does not contain 'odm.img'

archive does not contain 'product.img'

archive does not contain 'product-services.img'

archive does not contain 'recovery.img'

archive does not contain 'super.img'

extracting system.img (2208 MB) to disk...W/ziparchive(12663): Zip: unable to allocate 2315399472 bytes at offset 0: No space left on device

fastboot: error:

failed to extract 'system.img': I/O error

---------- Post added at 10:11 PM ---------- Previous post was at 10:11 PM ----------

I'm going to be crazy with this Pixel 2 XL..
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
I hope I'm not being redundant here, but make sure you are using the latest SDK toolkit, try changing USB cables from 2.0 to 3.0, and follow a few other troubleshooting methods found in the 9x 2 XL link in my sig.

Your bootloader and baseband looks like the latest versions, but the serial number looks off..

The links to the latest version of these are included, and I think the step by step will be helpful. It has helped a lot of users, it might provide useful to you as well.

Good luck!
[Google Pixel 2 XL Guides, News, & Discussion] ooemir:
Pls help. How to unlock bootloader Verizon Pixel 2xl. Realy so many search but not find solitions.

My Phone Buyer Code : VR1 Google_VRZ_128G
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
There is no solution my friend. There hasn't been a viable unlocking method available for the Verizon version since the device came out last year. Sorry man!
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
What a Debbie downer you are! What a purveyor of negativity you are! You could've at least..... you're such a meanie!!! :p
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Gotta drop the hammer once in a while Big Dog! ??
[Google Pixel 2 XL Guides, News, & Discussion] seadersn:
but, is it true, that after an certain amount of time (two years?) they are unlockable? i don't know anymore where and when i've read this, and for which model but... is it true, for the p2xl? #risinghope
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
You can judge for yourself my friend. The Verizon P2XL remains in bootloader lock down.

https://xdaforums.com/pixel-2-xl/how-to/true-verizon-pixel-2-xl-unlocked-t3763443
[Google Pixel 2 XL Guides, News, & Discussion] seadersn:
yay, k :good:
[Google Pixel 2 XL Guides, News, & Discussion] post-mortem:
If you buy a phone which is SIM locked to a carrier, they have their rules about getting the phone SIM unlocked. This is unrelated to being able to unlock the bootloader.
[Google Pixel 2 XL Guides, News, & Discussion] ooemir:
Please check the attached photo. This is my phone. could this model be unlockable.

as I have read on internet, some people could able to make their phone unlockable.

How do they achieve to make their phone unlockable. Or are they lying ?
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
Your best bet for an unlocked bootloader is to buy the device unlocked.

While some devices have had development that resulted in a method for unlocking the bootloader, many never do.

After a few years, no Dev is going to spend any time trying to unlock an older device's bootloader.

If your device is within the return period, I suggest returning it, and buying the unlocked version directly from Google. They have payment plans very similar to the carrier's.

If your device is older, maybe consider getting a unlocked Pixel 3 XL from Google, and sell the Verizon model on Swappa.

Good luck!
[Google Pixel 2 XL Guides, News, & Discussion] seadersn:
could really be that what i've read indeed was sim card unlocking related :good:

at this point of time i don't own it, but will, next week or so :) two p2xl: a verizon one and a default google version :good: both need a new screen, but then i have at least one phone to tinker with :D

thanks for info everyone! :)
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
The short answer to your question is no. It's a Verizon variant phone. Likely what you've read are the extremely rare cases where people have either received a google version phone through an RMA, or an error by google. Other than that, there is no viable, public unlock method.
[Google Pixel 2 XL Guides, News, & Discussion] MartyMacGyver:
Cannot root Pixel2 XL anymore now that I'm on the November Pie patch

I've had zero problems updating to new releases - until today.

Pixel 2 XL (direct from Google), stock everything, encrypted.

I flashed the latest November factory release today (moving from Oreo 8.1 to Pie 9.0).

Works great - if I don't try to root it.

If I root it with Magisk, via patching `boot.img` via the Magisk APP or directly running any of the Magisk installers within TWRP 3.2.3-1, it fails to boot (specifically, it loops, then says it can't mount the (encrypted) data partition).

If I then fastboot into TWRP and uninstall magisk, it all works just fine, data's all there - but of course with no root.

I have NOT messed with the B partition (nor have I in the past).

I've tried directly installing Magisk 16.7, 17.1 and 17.3 (via TWRP).

I've tried installing via the Magisk app (which seems to insist on the latest Magisk version), patching the boot.img manually and then flashing it manually.

I've diligently uninstalled Magisk (and its app) again and again.

So I ask you, why can't I root anymore? What Magisk-al incantation is supposed to work here? It's mystifying - this "just worked" before Pie.

(And again, as long as I don't install Magisk things work fine.)
[Google Pixel 2 XL Guides, News, & Discussion] greyhd:
I had the same issues as you but I was able to boot just didn't have root. Do you get any error messages when you flash Magisk? If you do, I would suggest you flash the google image and erase the data, then flash Magisk 17.1, once it boots up install the Magisk manager.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
I'm not sure your doing anything wrong my friend, it's the the P2XL being stubborn if you will. Had the same issue when I tried to root 9.0. Here's a few things to try.

1. Fastboot into twrp, flash twrp installer zip and a custom kernel, boot up to OS, then back to twrp to flash magisk 17.1 then hopefully boot up to OS.

2. Fastboot into twrp, flash custom kernel and magisk 17.1 and hopefully then boot to OS.

3. Fastboot into twrp, flash twrp installer zip, custom kernel, then reboot to twrp and flash magisk, then hopefully boot up to OS.

4. Best of luck to ya :good::good:
[Google Pixel 2 XL Guides, News, & Discussion] MartyMacGyver:
Erasing my data is an extreme last resort here - unless it's known you can't do this without destroying everything on the phone, I'd greatly prefer not to go down that highly destructive road. Restoring from whatever random backup Google may or may not have done is entirely useless. Right now it's perfectly fine without root so it's not broken - until I try to root it.

I didn't get any error messages flashing the patched boot, nor were there errors when running the magisk installer from TWRP. I even disabled security - didn't help, just failed a little faster since I wasn't typing a password in.

I also tried the mythical "1674" Magisk build. Didn't help a bit.

---------- Post added at 01:15 PM ---------- Previous post was at 01:07 PM ----------

I keep seeing this custom kernel mentioned in other very similar instructions I've read today, yet nobody says what custom kernel they're talking about.

Since you specifically mentioned it here repeatedly, what custom kernel are you referring to and is that required or will this work with the normal stock kernel? I have no reason to be changing kernels here unless it's required.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
I personally like Ex kernel. It works great and it's pretty darn close to stock as you can be.
[Google Pixel 2 XL Guides, News, & Discussion] MartyMacGyver:
That's nice - but is it required now? I didn't have a custom kernel in 8.1 and it rooted just fine.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
I'm just relaying info that helped me out. You can try the things I mentioned without the custom kernel and see what happens :good:
[Google Pixel 2 XL Guides, News, & Discussion] MartyMacGyver:
Has anyone gotten root to work without a custom kernel?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Several have. One other thing to try is to fastboot into twrp, flash magisk 17.1, then flash the magisk uninstaller, then flash magisk again.
[Google Pixel 2 XL Guides, News, & Discussion] last_nooby:
Did you try wipeing partitions using TWRP?
[Google Pixel 2 XL Guides, News, & Discussion] MartyMacGyver:
Which partitions do you propose I wipe? (Besides data of course, since we don't want to lose data, settings and so on when the phone is otherwise working perfectly fine.)

---------- Post added at 02:09 PM ---------- Previous post was at 01:58 PM ----------

That didn't work, nor did the other permutations of these steps previously mentioned.

(Note that actually installing TWRP adds a wrinkle to the process as it also modifies `boot.img`. I tried it at one point but it didn't help, just made things more complicated. )

It would be really good to understand what's actually going wrong here with Pie. I've updated and re-rooted this phone over a dozen times now and this is not normal.