yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Can you enable OEM unlocking under settings/system/developer options? If not, you likely have a Verizon variant phone.
[Google Pixel 2 XL Guides, News, & Discussion] theansible:
nope, i can't even get to the home screen.

so is there anything i can do from here? there's no other way to unlock the bootloader? or to install another ROM?

i just need the phone to think that its new again...
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
If you didn't enable OEM unlocking before this all started, or if you could at all, then there's no way to unlock the bootloader, or flash a factory image or rom with fastboot or twrp. You could try side loading an OTA via stock recovery and adb to see if it'll boot up. Or, go to stock recovery and do another factory reset and see if it helps.
[Google Pixel 2 XL Guides, News, & Discussion] Xihexa.io:
Does the root only method work on a VZW Pixel 2 XL running the latest version of Oreo/P Beta 5 ? Fastboot fails to unlock flashing or the bootloader even if I toggle OEM unlocking in developer settings.
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
Unfortunately, if you have a VZW 2 XL variant, you will not be able to unlock the bootloader, or root.

If you are within your turn in period, I suggest returning it, and getting an unlocked version from Google. They offer 0% financing for 2 years which is very similar to the 2 yr plan on VZW.
[Google Pixel 2 XL Guides, News, & Discussion] Xihexa.io:
I'm sort of strapped for cash so I doubt that I could afford one from Google as of this moment. Rooted or not, it's a really good phone so I'll find a way to unlock the bootloader and root it myself if I have to.

If not, I'm fairly certain that somebody may come up with a method eventually.

Thanks for the reply though! I'll just stick to the Aristo 2 for rooted stuff for now.
[Google Pixel 2 XL Guides, News, & Discussion] srqrob:
Listen to the man. Easy to move your number and have all options on your new phone. Verizon is not a low cost carrier. That's why carrier provided phones are sometimes locked.
[Google Pixel 2 XL Guides, News, & Discussion] Toonlinkmaster25:
Not sure if this is the right place to ask but I rooted my pixel 2xl back in March, I'm on Flash Kernal 2.24, and stock build number OPM1.171019.021 how would I go about updating to the latest build safely?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Disable screen lock security and substratum themes. Fastboot the July factory image with the -w removed from the flash-all.bat file. Let it boot up once, then fastboot into twrp, flash the twrp installer zip, then your Flash kernel, then the magisk zip. Reboot and done :good:
[Google Pixel 2 XL Guides, News, & Discussion] Toonlinkmaster25:
Great, thank you! Will this wipe my data?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Nope. That's why we remove the -w from the script. However, always a good idea to back everything up of course before you begin :cool:
[Google Pixel 2 XL Guides, News, & Discussion] Towmastersteve:
Hello all I'm a noob at this but I have follow xda guides before and rooted my htc one m8 and converted it to gpe I also rooted a htc 10 I just upgraded to the pixel 2 xl and I know it's a bit more complicated to root but I have been following the xda guides and I can't get the patched-boot.img to flash it says file to large I also cannot get twrp to boot when I try to boot twrp nothing happens fastboot say booting downloading img but nothing ever happens after I've tried 4 different data cables and different USB ports everything else seems fine with adb and fastboot so a little advise or maybe some truble shooting hints would be greatly appreciated if pixel 2 xl is from Google and it's a unlocked version and up to date with Android update with July security patch thanks again for any advice
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Are your SDK/platform-tools up to date as well?

When your in fastboot mode, and run the command...fastboot devices....do you see your phone ID displayed? If so, then do you have your twrp.img in your platform-tools folder? If so, what happens when you run...fastboot boot twrpxxxxxx.img? And...have you ran both bootloader unlocking commands?
[Google Pixel 2 XL Guides, News, & Discussion] gpmartinson:
I just want to verify what I have read prior to doing anything. I want to root my phone(I think). For me the main advantages would be:

1. Ad Blocking on a system level

2. The ability to back up

3. Customizations and tweaks

I'm not likely to ROM my phone but I think having the option in case something crazy awesome appears that I need to try.

The potential downsides from rooting(from my understanding of this thread include):

1. No OTA updates. Flash updates going forward.

2. The distant chance that my Pixel goes FUBAR.

So if that's the case my steps would include:

1. Download and install developer tools on my Mac

2. activate developer menu, turn on adb and unlock

3. Critical unlock

4. Re-set up my phone

4. Download both the TWRP image and zip installer from the official site.

5. Temporarily boot the TWRP image.

6. Install Magisk

Is this correct? The last phone I messed around with was the G7.
[Google Pixel 2 XL Guides, News, & Discussion] srqrob:
There are a lot of us who stay on stock after rooting with the same attractions and concerns you express. And there are flashaholics also doing developer previews and beta installs with addiction. Nathan's step by step guide in post 1 of this thread will walk you through whatever you decide you want to do.. All important is having up to date adb and fastboot tools and establishing solid communication with your phone. From your history, you probably know enough to be careful. Enjoy your new phone.
[Google Pixel 2 XL Guides, News, & Discussion] Towmastersteve:
here is my cmd from trying today

hope this will help

Microsoft Windows [Version 10.0.17134.167]

(c) 2018 Microsoft Corporation. All rights reserved.

C:\Users\towma\OneDrive\Desktop\android root tools\platform-tools_r28.0.0-windows\platform-tools>adb version

Android Debug Bridge version 1.0.40

Version 4797878

Installed as C:\Users\towma\OneDrive\Desktop\android root tools\platform-tools_r28.0.0-windows\platform-tools\adb.exe

C:\Users\towma\OneDrive\Desktop\android root tools\platform-tools_r28.0.0-windows\platform-tools>adb devices

List of devices attached

adb server version (31) doesn't match this client (40); killing...

could not read ok from ADB Server

* failed to start daemon

error: cannot connect to daemon

C:\Users\towma\OneDrive\Desktop\android root tools\platform-tools_r28.0.0-windows\platform-tools>adb devices

List of devices attached

adb server version (31) doesn't match this client (40); killing...

could not read ok from ADB Server

* failed to start daemon

error: cannot connect to daemon

C:\Users\towma\OneDrive\Desktop\android root tools\platform-tools_r28.0.0-windows\platform-tools>adb devices

List of devices attached

adb server version (31) doesn't match this client (40); killing...

* daemon started successfully

710KPJP0368980 device

C:\Users\towma\OneDrive\Desktop\android root tools\platform-tools_r28.0.0-windows\platform-tools>adb reboot bootloader

adb server version (31) doesn't match this client (40); killing...

could not read ok from ADB Server

* failed to start daemon

error: cannot connect to daemon

C:\Users\towma\OneDrive\Desktop\android root tools\platform-tools_r28.0.0-windows\platform-tools>adb reboot bootloader

adb server version (31) doesn't match this client (40); killing...

* daemon started successfully

C:\Users\towma\OneDrive\Desktop\android root tools\platform-tools_r28.0.0-windows\platform-tools>fastboot version

fastboot: usage: unknown command version

C:\Users\towma\OneDrive\Desktop\android root tools\platform-tools_r28.0.0-windows\platform-tools>fastboot devices

710KPJP0368980 fastboot

C:\Users\towma\OneDrive\Desktop\android root tools\platform-tools_r28.0.0-windows\platform-tools>fastboot boot twrp-3.2.2-0-taimen.img

Downloading 'boot.img' FAILED (status read failed (Too many links))

Finished. Total time: 95.324s

C:\Users\towma\OneDrive\Desktop\android root tools\platform-tools_r28.0.0-windows\platform-tools>fastboot flashing unlock

FAILED (remote: Device already : unlocked!)

Finished. Total time: 0.003s

C:\Users\towma\OneDrive\Desktop\android root tools\platform-tools_r28.0.0-windows\platform-tools>fastboot flashing unlock_critical

FAILED (remote: unknown command)

Finished. Total time: 0.002s

C:\Users\towma\OneDrive\Desktop\android root tools\platform-tools_r28.0.0-windows\platform-tools>
[Google Pixel 2 XL Guides, News, & Discussion] gpmartinson:
Everything worked until step 5. I boot TWRP and get nothing but the Title screen. I have turned off all device protection because I read that this can be a problem. I also read that it needs to be rooted before you can install TWRP. Is this accurate? if so, I missed this on the first post. I can't install TWRP or root my phone unless I try adb pushing things and I am hesitant to make things worse.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
You do not need to be rooted before fastbooting twrp. What errors do you get on your screen when in fastboot mode and you try to install twrp? For you also see your device ID when you run...fastboot devices?
[Google Pixel 2 XL Guides, News, & Discussion] gpmartinson:
I see the device from fast boot:

712KPWQ1032617	fastboot

Variables on the fastback screen:

Product_name taimen

variant MSM UFS:samsung (64G) DDR: Samsung

Baseband Version g8998-00253-1805232234

Secure boot yes

Device State unlocked

part console disabled

HW Version rev_10

This is the TWRP Command:

fastboot boot twrp-3.1.1-beta1-taimen.img

Downloading 'boot.img' OKAY [ 0.865s]

booting OKAY [ 0.001s]

Finished. Total time: 0.899s

I see two an image of two arrows (up and down in a blue circle) and the word teamwin

and then the phone is unresponsive and hangs on this screen.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Why are you using an old twrp version. Get the new ones from here.....https://dl.twrp.me/taimen/

And, try removing your screen lock security before you fastboot it again.
[Google Pixel 2 XL Guides, News, & Discussion] gpmartinson:
The problem was the old version. Thanks.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
With your phone plugged in to your pc, and the phone set to MTP, can you transfer data? If not check under your device manager and look for your device and see if the driver needs needs to be updated. If it's ok, then try opening a command prompt directly on your platform-tools folder while in bootloader/fastboot mode and try fastbooting twrp again.
[Google Pixel 2 XL Guides, News, & Discussion] Towmastersteve:
yes i can transfer files and see the folders

i also took the step today to wipe my pc for a clean start just incase someting was interfering with adb/fastboot here is my cmd after that

thank you for taking the time to help me

Microsoft Windows [Version 10.0.17134.191]

(c) 2018 Microsoft Corporation. All rights reserved.

C:\Users\towma\OneDrive\Desktop\root tools\platform-tools_r28.0.0-windows\platform-tools>adb devices

List of devices attached

710KPJP0368980 device

C:\Users\towma\OneDrive\Desktop\root tools\platform-tools_r28.0.0-windows\platform-tools>adb reboot bootloader

C:\Users\towma\OneDrive\Desktop\root tools\platform-tools_r28.0.0-windows\platform-tools>fastboot devices

710KPJP0368980 fastboot

C:\Users\towma\OneDrive\Desktop\root tools\platform-tools_r28.0.0-windows\platform-tools>fastboot flash boot patched_boot.img

fastboot: error: Failed to identify current slot

C:\Users\towma\OneDrive\Desktop\root tools\platform-tools_r28.0.0-windows\platform-tools>fastboot flash boot patched_boot.img

Sending 'boot' (25896 KB) FAILED (remote: unknown command)

Finished. Total time: 0.000s

C:\Users\towma\OneDrive\Desktop\root tools\platform-tools_r28.0.0-windows\platform-tools>fastboot flash boot patched_boot.img

fastboot: error: Failed to identify current slot

C:\Users\towma\OneDrive\Desktop\root tools\platform-tools_r28.0.0-windows\platform-tools>fastboot devices

710KPJP0368980 fastboot

C:\Users\towma\OneDrive\Desktop\root tools\platform-tools_r28.0.0-windows\platform-tools>fastboot boot twrp-3.2.2-0-taimen.img

Downloading 'boot.img' FAILED (status read failed (Too many links))

Finished. Total time: 188.582s

C:\Users\towma\OneDrive\Desktop\root tools\platform-tools_r28.0.0-windows\platform-tools>adb --version

Android Debug Bridge version 1.0.40

Version 4797878

Installed as C:\Users\towma\OneDrive\Desktop\root tools\platform-tools_r28.0.0-windows\platform-tools\adb.exe

C:\Users\towma\OneDrive\Desktop\root tools\platform-tools_r28.0.0-windows\platform-tools>fastboot --version

fastboot version 28.0.0-4797878

Installed as C:\Users\towma\OneDrive\Desktop\root tools\platform-tools_r28.0.0-windows\platform-tools\fastboot.exe

C:\Users\towma\OneDrive\Desktop\root tools\platform-tools_r28.0.0-windows\platform-tools>
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Can you post a pic of your platform-tools folder? You may have to use Android suite vs just the basic platform tools. It's what I've used the past 4 years without fail. Some folks have had problems with basic platform tools on Windows 10 machines.

Btw...can you transfer data in mtp mode like I asked?
[Google Pixel 2 XL Guides, News, & Discussion] CyberpodS2:
I'm quoting this post instead of the op to continue the sentiment...

Let's get one thing out of the way right up front. Do both unlock commands right from the start. Some folks forego the unlock critical only to find out later they needed to and have to shoulder wiping the phone again. Also, in light of several updated platform tools over the last 10 months, I religiously download a new copy of the files every month when I do the next update. That way it'll never be a possible snag when things go wrong. Lastly, if you have a quality usb-a to usb-c cable, I would use that for your fastboot functions.
[Google Pixel 2 XL Guides, News, & Discussion] Towmastersteve:
Yes I can transfer from PC to pixel

https://drive.google.com/file/d/15-YsbRXvSCZLj8_IqrA8uks1qWUJy1Re/view?usp=drivesdk

I tried to upload with the app but doesn't seem to be working so I will give Google drive Link and try to upload ss with app again
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
It's ok, I saw the pic. Everything looks appropriate, I'm thinking you might have to go the SDK android suite route, or possibly try Deuces recovery script. You may even try switching USB A to USB C cables again. My best guess is the SDK version and Windows 10 compatibility. Can't tell you why exactly, just my opinion. Once you get _critical unlocked, you'll be fine.
[Google Pixel 2 XL Guides, News, & Discussion] Towmastersteve:
Deuces recovery script how can I find that would I just search the fourm for it and I an also _critical unlocked and I do have 2 new USB to USB 3 cables on the way as well I'll also look into sdk thank you for your time and help
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Here ya go :cool: https://xdaforums.com/pixel-2-xl/development/tool-deuces-bootloop-recovery-flashing-t3704761
[Google Pixel 2 XL Guides, News, & Discussion] sikorskyovich:
Greetings!

I have a Pixel 2 XL. I unlocked the bootloader when I got it about 8 months ago. If I install TWRP then use TWRP to install Magisk, will my device retain all current data and apps?
[Google Pixel 2 XL Guides, News, & Discussion] CyberpodS2:
No you will not lose anything data wise. I would however also install Flash Kernel of you intend to keep twrp installed. Besides just being a solid product, it will avoid the touch issues in red over that the stock kernel has.
[Google Pixel 2 XL Guides, News, & Discussion] Towmastersteve:
Hello again I was finally able to get twrp to boot with a new cable I got in yesterday and surprising enough useing the USB 3.0 port so I'm rooted and good to go well almost I do seem to have a strange problem now it seems that every other boot it won't boot it just tries and then will boot into recovery and ask if I won't to try again or do a factory recovery I choose try again and it boots up I did eddit my build .prop as well as change a setting to enable teathering following another xda post that is working as expected now I don't have any need to do reboots but I was wondering about getting a ota how that would effect things if I read correctly I would loose root and would have to redo the rooting process but I don't believe it would effect the build.prop or the change in system settings and that was the primary reason for root as well as getting Gpay working without having to lock the bootloader any insight would be very helpful

And thank you once again for helping me out with problem
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Those darn USB cables strike again! This phone is very picky with those things, especially on Windows 10 it seems. You won't be able to take OTA's due to root and custom recovery. However, it's really easy to do monthly updates with the factory images and fastboot. Or, you can flash the factory OTA in twrp. Yes, you will lose root and twrp, and likely your build prop edit. It's not too hard to get them back though. Glad you finally got it up and running though. Persistence definitely pays off :good::cool:
[Google Pixel 2 XL Guides, News, & Discussion] Bluekross:
Has anyone confirmed if the current versions of TWRP and Magisk will work with Android 9 'PIE'?

Also, is is it recommended to do a clean install or will the dirty upgrade (remove -w from batch file) work?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
I dirty fastbooted 9.0 over 8.1 with the -w removed. Twrp is working ok without screen lock, but having a hard time getting root back. Several others have it working, but I'm not having much luck atm :(
[Google Pixel 2 XL Guides, News, & Discussion] OneNutShort:
Just dirty flashed Android 9 successfully, runs great. Am attempting to root using Magisk, but every time I go through the process of patching the boot image, and flashing the patched boot image, I end up on the boot screen with the G logo and the progress bar permanently loading. I've seen some talk about using build 1674 of Margisk, and have even downloaded a zip of it, but I'm not really sure how to go about installing it. Is it something you need to install through ADB? Would really appreciate if anyone has any insight into this.
[Google Pixel 2 XL Guides, News, & Discussion] Bluekross:
I upgraded using the method in this thread: https://xdaforums.com/showpost.php?p=74772300&postcount=296

Did -w on flash-all and removed my password/fingerprint before I flashed.

OS came up just like normal. From there I booted to TWRP and installed the TWRP zip and rebooted. Installed the Magisk 16.7-4 from TWRP and everything is working fine. Using the tether module and it works perfect.

Edit: I've upgraded 2 Pixel 2 XLs using the method above and both came through flawlessly.
[Google Pixel 2 XL Guides, News, & Discussion] simplepinoi177:
installation of the Magisk installation .zip is done through/via a custom recovery (most usually TWRP in Pixel 2's case...)...

note: if you're not interested in permanently installing and overriding the stock recovery with a custom recovery, you can always temporarily boot into the custom recovery via ADB through the command:

fastboot boot twrp-boot-image.img

instead of "fastboot flash custom-recovery.img boot" (or some derivation of that; running off of memory at the moment)...

hope this helps...
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Did the same without difficulties coming from 8.1. However, after installing magisk 1674 via twrp, I get stuck at the G screen. Did you come from 8.1 or DP5??
[Google Pixel 2 XL Guides, News, & Discussion] Bluekross:
I was on 8.1 July Patch. When I did the flash-all on reboot it stayed at the G logo for about 3-5 minutes before it went to the home screen. Everything else worked like a normal upgrade for me.
[Google Pixel 2 XL Guides, News, & Discussion] chazall1:
I came from P beta 5

adb sideload the OTA.zip

I had the same issue on the first boot.

I did a hard reboot, Press and hold the power button until the phone reboots.

Everything loaded as expected and not having any issues
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
I'm glad users are still finding this little guide helpful :D

I didn't see you mention flashing a cust kernel, did you not flash one?
[Google Pixel 2 XL Guides, News, & Discussion] Bluekross:
Yep probably the best guide I've seen that keeps it simple for folks who might not flash things very often. At one point my wife was on a Pixel and I was on an HTC so the root/upgrade methods were completely different and I would always confuse myself. I've had your guide bookmarked since last year when I got the phone because it's the easiest guide to use and come back to for each patch if I forget one of the steps.

And no, I don't use a custom kernel, just using stock.
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
Thanks for the kind words. I'm super glad you find it helpful!

[MENTION=3730810]Badger50[/MENTION], could the his lack of flashing a cut kernel have anything to do with his success?

Are you flashing a cust kernel in your process? Just thinking out loud.

EDIT: Disregard, I saw that you figured it out uninstalling Magisk via TWRP... :good:
[Google Pixel 2 XL Guides, News, & Discussion] Ghisy:
Hi,

A little OT for the ones who upgraded to Pie: if you use another launcher (like Nova), does the recents screen return to its Oreo form (vertical) or stays horizontal like in the Pie betas?
[Google Pixel 2 XL Guides, News, & Discussion] Prattham:
I'm on Nov build

After unlocking with both commands do i need to flash factory image? If yes then which one? Or just reboot and setup the device and boot back to flash twrp and magisk?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
No need to flash anything after you unlock. Just set the beast up :good:
[Google Pixel 2 XL Guides, News, & Discussion] uofirob:
I think you can change the guide to mention that you no longer have to patch a boot image with Magisk. When you flash the latest version of magisk.zip from the main thread and flash from within TWRP, it automatically patches the boot.img for you. I'm getting that I'm rooted without needing to extract/patch the boot.img.

My steps:

1) Unlock Bootloader (both regular and critical to install TWRP)

2) Fastboot into TWRP

3) Flash TWRP

4) Flash Magisk

5) Restart and setup phone

6) Install module to allow Tethering

7) Profit!
[Google Pixel 2 XL Guides, News, & Discussion] Prattham:
What if i want to install flash kernel then what would be the steps?
[Google Pixel 2 XL Guides, News, & Discussion] drewski_1:
2.5 flash kernel of choice
[Google Pixel 2 XL Guides, News, & Discussion] Prattham:
Not sure i followed i want to install flash kernel

What would be the steps to install that? In the op of says to patch boot img using magisk

Do i have to do that considering i have magisk now
[Google Pixel 2 XL Guides, News, & Discussion] Haz3:
2.5 means between steps 2 and 3 I believe.

Edit and I believe the flash kernel has a flashable zip that doesn't require the patched boot img
[Google Pixel 2 XL Guides, News, & Discussion] nathanchance:
Next release will have both images and zips to flash
[Google Pixel 2 XL Guides, News, & Discussion] drewski_1:
Yes between steps 2 & 3.

If you're flashing Magisk in Twrp, it should patch the boot.img during the process.
[Google Pixel 2 XL Guides, News, & Discussion] SonicCloud:
If I have previously patched my boot.img with magisk without TWRP, how do I go about installing TWRP and magisk again?
[Google Pixel 2 XL Guides, News, & Discussion] an21281:
In bootloader fastboot boot (NOT FLASH) twrp.img, then flash twrp.zip once in twrp followed by Magisk. If flashing a new kernel flash that first in TWRP then twrp.zip and magisk...
[Google Pixel 2 XL Guides, News, & Discussion] bradputt:
Delete, found my answer.