yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Well hot damn! Congrats my friend! This P2XL is a finicky beast for sure! Myself, xdakos, AZ Biker, CyberpodS2, simplepioni177, clothednblack, and many others have used different methods to get, and maintain root with the monthly updates. However, it should be easier for you from now on. When the February patch comes out, this is my routine for what it's worth.....

Remove screen lock security and sub themes.

Fastboot the factory image with the -w removed to both slots, and let it boot up each time to the OS.

Fastboot into twrp

Flash twrp.zip

Flash kernel.zip

Flash magisk.zip

Boot up and you should be good.

This is not the only method that will work I'm sure, but it's what works for me. As always with the P2XL.....YMMV :cool:
[Google Pixel 2 XL Guides, News, & Discussion] Maclx:
Jo guys quick heads up for what helped me with rooting. I was struggling pretty hard and tried all combinations mentioned here - nothing worked. What it finally changed for me was to NOT install the TWRP app as the app suggested it to do.

Else I did:

fastboot into twrp

flash twrp

reboot

boot to twrp

flash magisk

reboot
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Never install the twrp app! That'll jack ya up sure as shootin! Glad you figured it out though :cool:
[Google Pixel 2 XL Guides, News, & Discussion] Jiggs82:
Hey guys don't know if this been asked already, but is there another way to root the Pixel 2 xl , like how NRT root kit was for the Nexuses? Because i always seem to have trouble using command's/fast boot on my pc :/ Thanks in advance.
[Google Pixel 2 XL Guides, News, & Discussion] andrewjt19:
Another question for you Nathan, when you say it wipes the entire phone, does that include the internal storage? Meaning, pictures, docs, etc.?
[Google Pixel 2 XL Guides, News, & Discussion] clothednblack:
Yes, wipes it back to factory, out of the box condition
[Google Pixel 2 XL Guides, News, & Discussion] Haz3:
I've been looking and haven't seen a definite answer so I guess I'll ask here... When going from a custom kernel to a different custom kernel is flashing the factory boot.img necessary? I'm currently running flash 1.07 magisk 14.5 and TWRP. Anytime/way I try to flash a different kernel I get the G loading screen and it just stays there. TIA
[Google Pixel 2 XL Guides, News, & Discussion] markp99:
Jiggs, skipsoft Unified Android Toolkit might suit your purposes. Does 90%+ of the work for you. Decent instructions for the manual pieces (installing ZIPs via twrp, etc.)

http://skipsoft.net/
[Google Pixel 2 XL Guides, News, & Discussion] Jiggs82:
Oh awesome I will check that out thanks??
[Google Pixel 2 XL Guides, News, & Discussion] v12xke:
I'm new to Pixels coming from a N6P so this a/b thing is new to me. I got my device the other day and thanks to this guide and others I was able to quickly unlock, root and apply flash kernel. The order in which I did that was boot TWRP, and then flash TWRP, flash kernel (zip), then flash Magisk. I rebooted and ran Magisk , hit install from within the app (because I saw an active install button) and rebooted again. Is this last step needed? All my root apps work and life is good..... until the next monthly update, so my question in a nutshell is what is the most efficient way to apply the monthly images? I never depended on OTA's before and always used the full images, so that is what I was planning on doing here. If I use Nathan's guide here and flash-all with the (-w) switch removed, THEN repeat boot TWRP, flash TWRP, flash kernel, flash Magisk, reboot, install Magisk reboot the correct way (or am I adding something I don't need)? I'm guessing FlashFire doesn't work, so my fool-proof method for the N6P won't work for me here, correct? I would LOVE it if someone said FF works just fine, but I haven't seen any discussion using FF with a full image on our Pixel 2's.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Your sequence looks like exactly what I'm planning on doing. About the only thing I might question is flashing a custom kernel until the devs get the source code for the next update. Other than that, I think your exactly right :good:
[Google Pixel 2 XL Guides, News, & Discussion] v12xke:
Thanks for your reply! Yes, well by update I meant the regular monthly updates using the 8.0 kernel. Kernels are one big reason I don't normally join betas. 8.1 will be here soon enough and we'll have an updated kernel by then. Cheers! :good:

You don't know by chance whether starting Magisk and hitting the install button is redundant or required? I've noticed the button is still "active" now .....so flashing it from TWRP may be all that is required, and "installing" it with the button is just me being overly cautious?? dunno. :confused:
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
If magisk manager wants to update the app, then yes, go ahead. If it's prompting you to flash the zip, then I'd ignore it. I'm on magisk manager 5.4.3, which is the latest version.
[Google Pixel 2 XL Guides, News, & Discussion] simplepinoi177:
I don't know if this will mean anything substantial...but I did not click on the install button after running the zip from TWRP. I currently have full root, TWRP replaced stock recovery, TWRP version is 3.1.1 beta2, am running 8.1 developer's, used Magisk 5.4.3.
[Google Pixel 2 XL Guides, News, & Discussion] v12xke:
Thanks for taking the time to reply. I suspect flashing the zip is all that is required ( ala SuperSU) but since it was my first time using Magisk, I just hit the button and rebooted. Next time I'll follow your lead and then I will know for sure. I thought we were going to get the December update today, but so far it's not published. Thanks again.
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
If it's the same INSTALL request I am thinking of, it is to install the TWRP app, not TWRP itself, since TWRP was just installed. I unchecked it, and rebooted.
[Google Pixel 2 XL Guides, News, & Discussion] destiple:
I'm am among the sorry saps who unlocked the bootloader, rooted with Magisk, has used and customized the phone and now realizes I should have unlocked the critical section as well. What would be the best method for backing up and restoring apps and settings before wiping it to unlock the critical area?
[Google Pixel 2 XL Guides, News, & Discussion] Colchiro:
Just rip the band-aid off quickly.
[Google Pixel 2 XL Guides, News, & Discussion] burbank:
If it were me, and I had lots of important stuff in internal memory I would use something like Solid Explorer to copy the contents of internal memory to a USB flash drive (which I did today) and then Titanium backup to backup all user apps and data (which I did today) and then proceed with your updates. Those are the tools I use because I know them well. Your results may vary. Good luck.
[Google Pixel 2 XL Guides, News, & Discussion] destiple:
So I unlocked critical (which wiped my phone), flashed the latest factory image (8.1.0 (OPM1.171019.011, Dec 2017)) and was successful with all of that. However, now when I try to root with Magisk, everything proceeds like it was successful but I don't have root. I had root on the Nov. factory image with Magisk before.

Suggestions?
[Google Pixel 2 XL Guides, News, & Discussion] drewski_1:
are you using the latest Magisk v14.5? that worked for me on Dec build of 8.1
[Google Pixel 2 XL Guides, News, & Discussion] destiple:
Magisk Manager 5.4.3 (64)
[Google Pixel 2 XL Guides, News, & Discussion] bradputt:
Hi guys, one question, how do you know if your critical partition is unlocked?

Because i don't remember if i got issue the command when i just got the phone
[Google Pixel 2 XL Guides, News, & Discussion] Kalel Kent:
Dear nathanchance, Pixel 2 xl with unlocked bootloader, continues to receive system updates from Google?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Settings/developer options/turn off automatic updates. You will still get those if your not rooted with stock recovery.
[Google Pixel 2 XL Guides, News, & Discussion] Kalel Kent:
Thank you, but my question is this: i will still get automatic updates, if i unlock the bootloader?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Yes. However, if you root it and install a custom recovery, you may still get the updates, but they won't install.
[Google Pixel 2 XL Guides, News, & Discussion] Kalel Kent:
Ok, thank you. But if i root and remain with stock recovery, automatic updates will install, right?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Negative Ghost Rider.
[Google Pixel 2 XL Guides, News, & Discussion] Kalel Kent:
Thank you. Last question: if the device is unrooted and with stock recovery, but his bootloader is unlocked, it will install the automatic updates?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Yep. But then again, why bother unlocking the bootloader anyway? Unless you plan on modding, rooting, or installing a rom, it's best to just leave it locked.
[Google Pixel 2 XL Guides, News, & Discussion] Kalel Kent:
I'm thinking to unlock the bootloader, install magisk and root the device. When i want to install an automatic update, i unroot the device but i leave magisk still installed. It will works?

---------- Post added at 06:17 PM ---------- Previous post was at 06:16 PM ----------

After the update, i'll root the device again through magisk.
[Google Pixel 2 XL Guides, News, & Discussion] srqrob:
General topic on this phone. We still have almost two years of version and security updates and apparently many are still buying this phone as a new primary device. But I've noticed over many phones that the players change on these groups and then you notice people are missing who you've followed for help and advice. The core group (less Nathan) still pretty much remains here but I wonder what triggers will cause that group to move on. Can anyone define what will prompt them to go new? Incremental changes are getting smaller it seems. These phones cost more than a few very nice dinners.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Ok. Then I'd recommend you read this guide...https://xdaforums.com/pixel-2-xl/how-to/quick-2xl-upgrade-reference-8x-oreo-to-t3826330

You have 4 options to update the monthly security patches. The guide is probably the most popular amongst us old vets, using fastboot, and was created by my mentor [MENTION=4670411]Az Biker[/MENTION], with lots of input from the community.

You can also update like you stated, however, you will need full unroot and stock recovery.

You can update via side loading the OTA through stock recovery.

Or, you can flash the OTA zip via twrp. In all cases, you will still need to root the device again after you install the updates :good:
[Google Pixel 2 XL Guides, News, & Discussion] Digital DJ:
I am trying to root my GP2XL using this method. It is not a Verizon GP2XL, I bought it straight from Google. Anyway, I'm stuck on the first part:

1. Unzip the folder somewhere on your hard drive.

2. Go to the folder containing the adb and fastboot files and type "cmd" in the path bar at the top.

3. A command prompt should open with the current folder showing on the prompt.

4. Type the following commands:

Code;

adb --version

fastboot --version

You should see some information appear. If that is the case, you were successful!

So when in cmd I type that information exactly adb --version fastboot --version and I get the error message 'adb' is not recognized as an internal or external command, operable program or batch file.

I've searched thru this thread, but honestly, there are a couple hundred pages and I'm not finding a solution.

I'm on the latest Jan 5, 2019 sec patch. Would love some help.
[Google Pixel 2 XL Guides, News, & Discussion] TonikJDK:
That is a Windows error. ADB.exe is not in the directory where you opened you command prompt.

Or you are on Windows 10 and opened a PowerShell window instead of a command prompt. Is the window blue or black?
[Google Pixel 2 XL Guides, News, & Discussion] Digital DJ:
The window is black. It looks like a command prompt box. I haven't rooted in like 5 years so I'm a little rusty, but not a noob. It's starting to come back to me, just stuck on this part I guess. I've never rooted like this before. How can I fix this?
[Google Pixel 2 XL Guides, News, & Discussion] TonikJDK:
Take a screen shot or photo of the window where you typed cmd.

And one of the window that opens when you typed cmd.
[Google Pixel 2 XL Guides, News, & Discussion] Digital DJ:
Attached.View attachment 4696878
[Google Pixel 2 XL Guides, News, & Discussion] TonikJDK:
You need to drill down one more level into the platform tools folder and open the command prompt window there.

That folder is also where you will put TWRP and Magisk and the full factory image when you need that.
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
once you're in the platform tools folder (you have to unzip it twice and pull the contents from the second unzip and put them in the folder that has the fastboot application), and then you type CMD in the address line from that folder, it should open a command prompt window, with your device booted to the bootloader, type in:

fastboot devices

then hit enter... This should return a long serial number. If not, it's time to update SDK tools, change a USB cable or port.

In my sig is a step by step guide using fastboot commands. It's pretty simple to follow, with links to all the files needed, and some troubleshooting steps as well.

Good luck.
[Google Pixel 2 XL Guides, News, & Discussion] Digital DJ:
Thanks, I guess I should say that I'm using

the USB-C to USB-C cable that came with the device.
[Google Pixel 2 XL Guides, News, & Discussion] Digital DJ:
I'm sorry I am going into the platform tools folder.
[Google Pixel 2 XL Guides, News, & Discussion] Digital DJ:
here is what it looks like when I'm trying it.
[Google Pixel 2 XL Guides, News, & Discussion] post-mortem:
You're still in the wrong folder. Double-click on "platform-tools" and try again.

BTW, adb -- version and fastboot --version are 2 different commands, to be entered separately.
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
Still need to try a different cable. It's one of the oddities of the 2XL.

Sometimes thr same cable works after swapping it out with another one.

Trust me, it's a known, weird, unexplained issue. Try different cables; usb 2, usb 3, diff ports, reboot pc.. It's like voodoo :p
[Google Pixel 2 XL Guides, News, & Discussion] simplepinoi177:
Alright...here's the easiest, most direct way to get the command prompt (cmd) in the proper directory...

- put platform-tools folder (reminder: make sure you have the most up-to-date version [r28.0.1]) on the desktop (unzip or copy/paste)

- open an explorer window where you can

actually see

the adb.exe and fastboot.exe programs (if you have extensions hidden, it would only show "adb" and "fastboot")

- click on an empty space next to where it shows "This PC > Desktop > platform-tools" or something to that effect (I'm not using Windows 10 so I'm basing it off of memory...). It should show you something along the lines of "C:\Users\[username]\Desktop\platform-tools", select that whole line and "cut" it...

- hold down the "Windows" button and tap "R" at the same time (this should work on any version of Windows...) and type "cmd" and press ENTER

- type "cd " (pay special attention to the space after) and right-click and paste what you had "cut" previous and press ENTER

- basically it should look similar to​

cd "C:\Users\[username]\Desktop\platform-tools\"

If you followed the directions correctly, you should properly be "pointing" into the directory and this is where you can run the "adb version" and/or "fastboot --version".

I hope everything works out from here on out, but, to make it as least complicated as possible, I didn't have you run "as Administrator", so hopefully you don't run into any potential issues there. Also, it's been widely known that utilizing a USB-C to USB-C port can cause nothing but issues and problems -- so beware...

If you need any more clarification, please don't hesitate to ask...good luck and hope this helps...
[Google Pixel 2 XL Guides, News, & Discussion] Digital DJ:
I have to head out but I wanted to let you know that I've tried going in one more folder and get the same result. I'm going to find my other cable USB3.0 to USB-C and try using it. I'll update later. Thanks for the help so far guys!

Update: Found the "other" cable, plugged it in and got this far. I actually don't have the time to start the process now, but this afternoon, I'm going to get it! Thanks again, guys!
[Google Pixel 2 XL Guides, News, & Discussion] jd1639:
Here's a tip to avoid the problem of what folder you're in. Go to windows environment variables and go to advanced. In there there is a PATH variable which you can edit to include the path to the folder your adb and fastboot are in. Once you do that it doesn't matter what folder you're in, your system will run adb and fastboot as if it's in the same folder you're working in.
[Google Pixel 2 XL Guides, News, & Discussion] Nikos2k:
The problem you had, had nothing to do with the cable
[Google Pixel 2 XL Guides, News, & Discussion] Digital DJ:
Yeah, I'm not sure if it was the cable or the port. Either way, I used a different cable on a different port and now my BL is unlocked. Easiest and fastest unlock ever. Thanks again!

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

I have another question now that my bootloader is unlocked. With regards to Flashing Factory Image, which option should I choose? Again, it's been a while since I have flashed. I was thinking the Clean Flashing a factory image, (wipe everything)?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
You can certainly do that. However, if you want to preserve data month to month, you can edit out the "-w" tag in the flash-all.bat script, then just run the script. You won't loose any data. Kinda like taking an OTA :good:
[Google Pixel 2 XL Guides, News, & Discussion] Digital DJ:
OK, so this part is new to me. I've never messed with script before but am willing to get my hands dirty. Where would I find this "-w" so I can remove it?

EDIT: ok I realized I had to right click then hit edit on the flash-all.bat file. I have removed the "-w" although it had no quotes around it.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
You can to the OP of this thread and find out all about it...https://xdaforums.com/pixel-2-xl/how-to/quick-2xl-upgrade-reference-8x-oreo-to-t3826330/post77530335

You can also flash the OTA zip in twrp, or side load the OTA via stock recovery and upgrade that way as well without wiping data :cool:
[Google Pixel 2 XL Guides, News, & Discussion] Digital DJ:
Ok in this pic, this is what I'm getting. I have followed the instructions:

Download the latest factory image from Google's website.

Reboot into the bootloader:

Code:

adb reboot bootloader

Unzip the factory image.

Inside you will see a bootloader image, a radio image, an image zip file, and a couple of flash scripts.

If you are on Windows, open the "flash-all.bat" file in a text editor. If you are on Mac or Linux, open the "flash-all.sh" instead.

Remove the "-w" flag before the fastboot command towards the end of the file. This will prevent fastboot from formatting your device.

Run the flash all script! Open a command prompt, navigate to the folder with the script, and run one of the following commands:

Windows:

Code:

flash-all

I think I'm in the right folder where the script is.
[Google Pixel 2 XL Guides, News, & Discussion] Digital DJ:
Ok according to the rooting instructions I'm following, I haven't even gotten to twrp yet. Did I miss something? Here is what I've done so far:

1. Succesfully installed fastboot and adb

2. I've succesffuly unlocked my bootloader

3. In flashing factory images, I've downlaoded and unzipped the factory image from Google's website for January 2019 "taimen" for Pixel 2 XL (9.0.0 (PQ1A.190105.004, Jan 2019)	Link	1fa0246a1e4aa38fbf4aee0a635721ea278c9edf7f554c184626eb22f376ff54

That's as far as I have gotten. When I try the command I get nowhere.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Do have the latest version of platform-tools? If so, those files you extracted from the factory image NEED to be in the platform-tools folder. Then open up a command prompt ON the platform-tools folder and type: fastboot flash-all. Or you can just double click the flash-all.bat file as well to start the process.
[Google Pixel 2 XL Guides, News, & Discussion] Digital DJ:
Yes I believe I have the latest version. R28.0.1-windows. I'll try sticking those in that folder now.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
You have too. That's the interface between your phone and pc to allow you to update your decuceb:good::good:
[Google Pixel 2 XL Guides, News, & Discussion] Digital DJ:
Ok I have put those in the platform-tools folder and I'm now getting this (shown in pic). It looks promising at first, but then gets the error...
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
You've almost got it. Remove the factor image zip file from the platform-tools folder. Within the factory image file should be another zip folder that contains the boot, vendor, dtbo, and all the other stuff. That file needs to remain zipped, and placed in the platform-tools folder. Then you should be good :good:
[Google Pixel 2 XL Guides, News, & Discussion] Digital DJ:
You were right, I had my cable plugged into the damn graphics card. lol I feel dumb.

---------- Post added at 08:14 PM ---------- Previous post was at 08:11 PM ----------

Ok, did I miss all these instructions somewhere? I feel EXTREMELY stupid having to ask for step-by-step directions....
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Meh...no biggie bruh. I've been looking at stupid in the mirror for 60 years. Did you go to the OP of the thread I linked you to? The guide is in there :cool:
[Google Pixel 2 XL Guides, News, & Discussion] Digital DJ:
I did briefly and did some reading, then the kids needed dinner, then I got back on, then the kids had to go to bed, then I finally flashed the image! Then the kids got out of bed, I put them back and now I'm here getting ready to start the next step.

EDIT: Just realized I forgot to delete the "-w". I guess I can do it again????

EDIT 2: Ok jumped back in and deleted the "-w" from the flash-all.bat file and am running the flash image again. All looks good so far.

---------- Post added at 08:47 PM ---------- Previous post was at 08:35 PM ----------

Badger, what do you mean (Fastboot the image with the -w removed to both slots, and let it boot up each time. Or use the Dueces script if you prefer. ) by "both slots"? I only saw one "-w"
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Atta boy Pop! Oh I remember that so well. Now I get to do it with grand kids...except, they go home! :laugh::good:
[Google Pixel 2 XL Guides, News, & Discussion] Digital DJ:
Badger, what do you mean (Fastboot the image with the -w removed to both slots, and let it boot up each time. Or use the Dueces script if you prefer. ) by "both slots"? I only saw one "-w"
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
That's just my method of fastbooting the factory image to both our A and B slots. In essence, I do the whole procedure twice. You have to manually switch your slots with a fastboot command. But you really don't need to worry about that in most cases. Unless one of your slots becomes corrupted :good:
[Google Pixel 2 XL Guides, News, & Discussion] Digital DJ:
[MENTION=3730810]Badger50[/MENTION] Ok next question, how do I flash into twrp? I'm reading both your insturctions and Nathans, but I'm not getting it. I'm close man, real close.
[Google Pixel 2 XL Guides, News, & Discussion] Digital DJ:
Here is a pic of what I'm doing.

I feel like the <path_to_twrp_image> is where I'm supposed to type the actual path..lol