yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 XL Guides, News, & Discussion] humdrum2009:
Funny thing is the last December that unlocked Ogpixl waited until a sufficient number of us had root, before Verizon was alerted to the process and did an update.

Just to block bootloader unlock. But I wish you well and hope you make my pocket $100 lighter lol
[Google Pixel 2 XL Guides, News, & Discussion] Savoury:
I'm not sure where the error was hiding, but for some strange reason my Pixel didn't play any sound from the upper Speaker while rooted.

It also notified me to contact the Manufactor. . All i did was Flashing TWRP & Magisk afterward.. Which worked well.. Apart from the Speaker stuff.

Now i've reflashed the Stock image and everything is working again. Straaaaaange.
[Google Pixel 2 XL Guides, News, & Discussion] beartek:
I bought the "unlocked" one from the google store on [MENTION=481777]nov[/MENTION] 1 got the one they sent me on Nov 27.

Apparently got the vzw one, but have no idea how to tell... Any way they gave me permission to return it.

But I really wanted to be able to use it on straight talk verizon network. Grrr. Now i'm not sure if i want to

risk trying another one or maybe go with a galaxy 8 or something... Meantime I have my reliable N6P with 8.0.0

on ATT (but ATT is weak in Prescott....) Thanks for the reply!
[Google Pixel 2 XL Guides, News, & Discussion] simplepinoi177:
Mmmmm..I don't know about everyone else, but mine does say "ADB Bootloader Interface" instead of "Pixel 2 XL"...so maybe try right clicking on Pixel 2 XL, click "Update driver software", "Browse my computer for driver software", "Let me pick from a list....", I choose "Android Phone", and in the Manufacturer section -- make sure it says Google Inc. -- and choose "ADB Bootloader Interface". There's still a good chance that you may still experience the same issues as it's not too certain this does anything or mean anything good, but...hope this helps...

Mmmm...I dunno...I might not be getting what you're saying exactly, but when I plug in my 2XL when it's on, Device Manager says "Android ADB Interface", and when it's rebooted to bootloader (or "fastboot mode" as some call it; at least I'm under this impression) it actually changes to say "Android Bootloader Interface"...and/or when you do the command "fastboot --version", I would think that means fastboot mode is available...

It may be because I'm still on Windows 7 (Pro) or something...
[Google Pixel 2 XL Guides, News, & Discussion] Hyflex:
Hey,

So what would be the best way to backup all my apps, logins and everything that ice set-up so far? I'd rather not unlock my bootloader and have to login and set-up everything again. I've logged in over 35 apps and configured about 50.

I know Google can download all my apps but not the configurations/logins...
[Google Pixel 2 XL Guides, News, & Discussion] xflowy:
[MENTION=6842057]nathanchance[/MENTION] well **** i just erased my operation system somehow. i wanted to relock the bootloader since im sending back the device and did the following:

1. fastboot flashing lock_critical

2. fastboot flashing lock

now i get the message "no valid operation system found".

what do i do? im about to reflash the factory image (and hope this fixes it) but therefore i needed to unlock again. how do i lock proper? :/
[Google Pixel 2 XL Guides, News, & Discussion] nathanchance:
Did you factory reset before locking the device? I don't know outside of that.
[Google Pixel 2 XL Guides, News, & Discussion] freddienuxx:
[MENTION=6842057]nathanchance[/MENTION] how can i update to dec stock rom if im rooted with magisk and twrp? fyi you have the best guides. thx for your great work
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
I'm not trying to derail the answer your looking for from Nathan, he's a tech Jedi to say the least. I'll just tell you how I did it without any problems at all.

1. Both, unlock and unlock_critical have been performed.

2. Your SDK and drivers are up to date.

3. Remove all lock screen security, and set it to swipe. And uninstall all themes if you have any.

4. Download, and extract the latest factory image, and place it's contents in your SDK platform tools folder.

5. Edit the flash-all.bat file, and remove the -w in the last line of code, and save the changes. This will NOT wipe your data. (I'm using windows notepad to do this)

6. Double click the flash-all.bat file to begin the process. It'll take a little while, so be patient.

7. Once it's done, let it boot up. You'll be on 8.1, but not rooted.

8. Boot back into bootloader mode.

9. Fastboot the latest twrp.img.

10. Once in temporary twrp, flash the twrp.zip, then custom kernel.zip(optional) then flash the magisk zip. I'm using the 5.4.3 version.

11. Reboot your device. Before you enter your device, you'll see a warning about a problem with your device(or something like that) it's no big deal, so ignore it, it's a magisk thing.

12. Add your lock screen security back in, and any themes, and your done. :good:
[Google Pixel 2 XL Guides, News, & Discussion] freddienuxx:
Awesome thank you

Sent from my Pixel 2 XL/Magisk
[Google Pixel 2 XL Guides, News, & Discussion] ManImCool:
Sigh. I got all the way to the end and was in temporary TWRP. Flashed permanent TWRP. Flashed Magisk 14.5 Rebooted. Now I'm stuck in the white Google loading screen with the moving loading bar. Please tell me I didn't brick my device. Am I close? Do I have to start over? Can this even be fixed?

FWIW I was one of those guys that did an OTA to 8.1 before trying any of this.

Edit: i was able to reboot successfully holding the power button, but now when it boots up, it displays a pop-up message:

Android System: There's an internal problem with your device. Contact your manufacturer for details.

Any ideas? This pops up every time I reboot.
[Google Pixel 2 XL Guides, News, & Discussion] inffy:
That pop up comes from Magisk patching the dtbo.img. I think it is already fixed in the Magisk source so should be in the next update. Or you can install a unofficial version to get rid of it.

You can just ignore the error
[Google Pixel 2 XL Guides, News, & Discussion] Tone Capone:
Magisk Update

I got a notification that there was an update to Magisk. When I updated however, I ended up with two Magisk icons in the app drawer, and neither of them worked. They both would just close right after I tried opening them. I uninstalled the new version (5.5) but that did not clear up the problem. I tried clearing app cache and app data on the remaining version, but still no joy. I then tried uninstalling and reinstalling the previous (5.4) version and it still does not work. Anyone have any suggestions?

---------- Post added at 10:31 PM ---------- Previous post was at 10:17 PM ----------

I bet this is because I hid Magisk when I first installed it...

Do not know how to fix my situation though. :(
[Google Pixel 2 XL Guides, News, & Discussion] CyberpodS2:
Um, am I missing something??
[Google Pixel 2 XL Guides, News, & Discussion] Legend_dimebag:
for the "internal problem error message" this is the solution on the OP magisk thread:Q: After flashing Magisk, my device will show a scary popup saying "There's an internal problem with your device. Contact your manufacturer for details"

A: This is caused by dtbo image patched to remove AVB 2.0 of the vendor partition. This is required for allowing you to mount vendor to rw and make modifications

If you never plan to modify the vendor partition, in Magisk Manager, "Uninstall > Restore Images" to restore the images, check "Preserve AVB 2.0/dm-verity" box in Advanced Settings, then reinstall Magisk via the app.
[Google Pixel 2 XL Guides, News, & Discussion] FloRida1999:
https://imgur.com/oASepsG

This phone was a gift and i don't know how to tell if it is from Google or Verizon. (OEM Unlock) is greyed out and I suspect Verizon, but the product name is Taimen. I am currently using it on tmobile.

Question 1-- Can you tell which one (variant) it is by the attached picture?

Question 2-- Should I unlock? critical unlock? or if its verizon do nothing?

Thank you
[Google Pixel 2 XL Guides, News, & Discussion] Felosis:
You have to go to the main Magisk thread and download the Magisk Uninstaller script and run it in recovery. Uninstall the Magisk Managers you have installed before running the script. This will completely remove Magisk from your phone in which case you can do a clean install of the latest version. I think he mentioned in his update post you might need a clean install. I did this as well and its working great. :)

Note that since it's a a clean install you'll have to re-hide your apps and reinstall any modules you had.
[Google Pixel 2 XL Guides, News, & Discussion] v12xke:
Can't tell from the picture, but agree it sounds like a Verizon variant. If a Verizon SIM was ever in it during setup, the phone will d/l certain Verizon specific apps. These should be pretty obvious to find. Maybe punch in your IMEI into THIS and see if it gives you some additional information. Mine is listed as GOOGLE_OPEN_64GB under buyer name. On your second question- you can do nothing. You aren't going to be able to unlock the bootloader, therefore will not be able to flash anything to the device. Sorry. Post a screenshot of your readout and I'll compare with mine.
[Google Pixel 2 XL Guides, News, & Discussion] FloRida1999:
Phone model-- Pixel 2 XL G011C

Buyer Code-- VR1

Buyer name-- GOOGLE_VRZ_128G

Blacklist status-- CLEAN
[Google Pixel 2 XL Guides, News, & Discussion] v12xke:
I was afraid of that. My buyer code is USX. Well at least you found your answer. Not everyone is into unlocking and rooting their phone, so it may not be that bad. It was a gift as well! At least the phone is not carrier locked so you can move around.
[Google Pixel 2 XL Guides, News, & Discussion] zohaibshafijutt:
I want to flash stock image from google and there are two files given on their website.

One zip says telus only and other one says nothing...

I have no idea which one to flash....

My bootloader is unlocked.....

Would someone please tell me about my phone and which image to download from the given screenshot...

1st image:. 8.1.0 (OPM1.171019.011, Dec 2017)

2nd Image:. 8.1.0 (OPM2.171019.012, Dec 2017, Telus Only)View attachment 4367602View attachment 4367603
[Google Pixel 2 XL Guides, News, & Discussion] an21281:
The first one without Telus... Unless you are using Telus as your cell phone provider?(although I am sure the first one will still work for telus too)
[Google Pixel 2 XL Guides, News, & Discussion] zohaibshafijutt:
Nope, not using telus and no idea what a telus is...

I am in Pakistan and bought it with unlocked bootloader...

And thanks for quick reply much appreciated....
[Google Pixel 2 XL Guides, News, & Discussion] RampageRR:
Hoping someone can help me out here. I tried unsuccessfully to set up v4a on my 2 XL, and I think I'm going to try going back to a clean system without these audio files left everywhere. That way I can start fresh and maybe get it working.

That being said, what's the proper way to get the OEM system dirty flashed via TWRP? Are there any files out there I can do this with, and if so, what's the proper way to do it? I'm so out of the loop on newer versions of Android ?
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
I don't recall seeing anyone flash a factory image in TWRP yet.

Everything I have read still shows flashing the factory images via fastboot.

These are the steps I took for a fresh install of the latest and greatest.

Magisk and TWRP have newer versions out, and those files are readily available
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Have you read the OP?? He has a pretty good guide on how to flash factory images :good:
[Google Pixel 2 XL Guides, News, & Discussion] RampageRR:
Awesome, so I'll just have to do it the old fashioned way. That's fine, just wanted to see if there was a way to do it via TWRP.

So from your post, I can remove the -w at the end of the script, run the flash-all.bat, and I'll still have all my data but my /system files will be back to where they were pre-v4a madness, right? Thanks so much!
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
Yep... Removing the -w keeps your internal from being wiped.
[Google Pixel 2 XL Guides, News, & Discussion] zohaibshafijutt:
Guys, I do not have "flash-all.bat" file in adb folder as it is by name "flash-all"..

I used command flash-all.bat and there was an error "the term flash-all.bat is not recognized as the name of a cmdlet,......."

What should I do ?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
The flash-all.bat file is part of the factory image once you've extracted it. Then move that file to the SDK platform tools folder. Double click the file to start the installation process.
[Google Pixel 2 XL Guides, News, & Discussion] zohaibshafijutt:
I have placed all the files of factory image in the folder...

Command is to be used through powershell or just double click the flash-all file ?View attachment 4367687
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Just double click it :good:
[Google Pixel 2 XL Guides, News, & Discussion] hitman03:
it is stuck at "waiting for any device"
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
Try typing CMD in the address bar when in tge platform tools folder, that's how I flashed my flash-all.bat filein fastboot
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
I don't know what power shell is or how to use it. I just put all the files from the extracted factory image into my SDK platform tools folder, then double click the flash-all.bat file and away it goes. Your in bootloader mode correct??

---------- Post added at 04:57 AM ---------- Previous post was at 04:56 AM ----------

Dang ninja's! :laugh:
[Google Pixel 2 XL Guides, News, & Discussion] hitman03:
yes bootloader mode...

I have only setupd adb and fastboot...

when i execute command fastboot devices it just says list of devices and no name or numbers....
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Then your pc isn't recognizing your phone properly. What cable are you using?
[Google Pixel 2 XL Guides, News, & Discussion] zohaibshafijutt:
adb devices command is working

Note 8 cable
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Interesting. Yet, it doesn't work in bootloader fastboot mode. I've read that only certain cables will work. I'm using my old nexus 6p USB-A to USB-C cable. It's worked perfect since day one.on my P2XL. Try another cable if you can.

Make sure your drivers and SDK are up to date as well.
[Google Pixel 2 XL Guides, News, & Discussion] zohaibshafijutt:
No other cable....[emoji52]
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Then I don't know what else to tell you my friend :rolleyes:
[Google Pixel 2 XL Guides, News, & Discussion] zohaibshafijutt:
Allright this is strange...

I just installed drivers from google and it shows adb interface in device manager....

I believe it was missing...

I try fastboot command and report back....View attachment 4367713
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Hope it works for ya :good:

Reboot pc before trying though.
[Google Pixel 2 XL Guides, News, & Discussion] zohaibshafijutt:
It worked...

I am on 8.1...

Should I lock my bootloader as I do not intend to root ?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
NO..NO..NO!!! You'll need it unlocked for the next monthly security update. And the subsequent ones to follow. Very glad you got it working though :good::good:

Not to mention that now you'll always have the ability to flash factory images if something goes awry! :cool:
[Google Pixel 2 XL Guides, News, & Discussion] Tone Capone:
Thanks. Does that mean the latest version of the Manager and the zip file? Or do I just use the dtbo zip?
[Google Pixel 2 XL Guides, News, & Discussion] Felosis:
Correct, the dtbo patching was fixed in the latest version. Basically, uninstall Magisk Manager, run the uninstall script in TWRP, then install the latest Magisk 14.6 zip in TWRP, reboot back to system and setup Magisk and modules again. :)

To play it safe, flash the zip of whatever Kernel you're using in TWRP before Magisk too. That will make sure you have a clean install of a dtbo before the Magisk install so you don't get that error after every boot up.
[Google Pixel 2 XL Guides, News, & Discussion] Tone Capone:
Magisk 14.6 zip? How come I only get 14.0 when I click the "latest" link?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Are you on beta channel in magisk settings?
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
FWIW, I upgraded from 14.5 to 14.6 by flashing 14.6 in TWRP like this:

Flashed 14.6

Reflashed Flash kernel 2.04,

Reflashed masgisk 14.6

Reboot

Profit

No more 'internal problem' warning at bootup, and no other issues.
[Google Pixel 2 XL Guides, News, & Discussion] nldxda:
When doing this step, I get the error "Target Magisk version doesn't support boot image file patching" :confused:

Somebody please help me get past this step. Thanks. :fingers-crossed:
[Google Pixel 2 XL Guides, News, & Discussion] nathanchance:
Are you on the beta channel? You should be prompted to install 14.6.
[Google Pixel 2 XL Guides, News, & Discussion] nldxda:
Ok that's the problem then.. Thanks, I'll play with this later when I can..
[Google Pixel 2 XL Guides, News, & Discussion] andrewjt19:
[MENTION=6842057]nathanchance[/MENTION] Thanks for your help previously first of all. I was wondering though if maybe you could incorporate into this guide how to install TWRP along with Magisk. Furthermore, could you post the commands to fastboot the following images from stock downloads:

Boot image

DTBO image

System image

And whatever the factory recovery/bootloader file maybe.

I read on XDA somewhere that the recovery and bootloader are merged into one file. I again tried to install Magisk and TWRP and have received all sorts of errors. Trying to use your guide to unlock and install Magisk while using other guides to install TWRP things don't always end well. I'm not sure why my phone is so temperamental, but it's been very difficult to get everything working. I've been doing kind of stuff since the first Android phones... This phone has been challenging. Regardless, thank you for your contribution to the community!
[Google Pixel 2 XL Guides, News, & Discussion] nathanchance:
Installing TWRP is fairly easy with the instructions on their website: https://twrp.me/google/googlepixel2xl.html

Installing Magisk just involves flashing the zip after you install TWRP. I'll see if I can get around to incorporating that here soon. Main reason I haven't done it yet is because the state of TWRP has fluctuated a lot. It's stable enough to add to this guide I think so I'll add it to my to-do list.
[Google Pixel 2 XL Guides, News, & Discussion] taranfx:
I followed all steps (I had to update to v5.5) and flashed mofiied boot.img just fine.

when I rebooted and launched Magisk, device wasnt rooted. Still stays magisk not installed.
[Google Pixel 2 XL Guides, News, & Discussion] kennypasatrain:
I am having a similar issue. I noticed when I booted back into the bootloader, it says "Device State: Locked." Does yours say this as well?

---------- Post added at 04:07 AM ---------- Previous post was at 04:05 AM ----------

I followed the appropriate steps to unlock the bootloader, followed all the prompts, but anytime i try to flash something, it says device state is locked. So i try to re-unlock, and it says device already unlocked.

Any ideas?
[Google Pixel 2 XL Guides, News, & Discussion] v12xke:
I think this is a dangerous state to be in. Make sure your adb/fastboot binaries are the latest, and that you are using a known good USB-A to USB-C data cable. From the bootloader fastboot flashing get_unlock_ability and see what it returns. Whatever you do- do not relock the bootloader. Did you get successful returns for both "unlock" and "unlock critical commands" ? If you didn't unlock critical you should do it now.
[Google Pixel 2 XL Guides, News, & Discussion] kennypasatrain:
I am using the new fastboot released by Google as a mobile version. What version number should it be? I'll check.

---------- Post added at 02:38 PM ---------- Previous post was at 02:22 PM ----------

Here is the return: (bootloader) get_unlock_ablitiy: 1
[Google Pixel 2 XL Guides, News, & Discussion] v12xke:
Both my fastboot and adb binaries are version 27.0.0-4455170. They are the Windows standalone version found HERE. You did not say whether you got a "success" in unlocking critical. You have to unlock both, with two separate commands. You may want to run through that unlocking process again with a different cable/ PC.
[Google Pixel 2 XL Guides, News, & Discussion] Waxillium:
Pixel XL 2: Thanks for this guide! I followed the steps, and encountered no issues up to the point where I attempted to boot from the patched_boot.img. Now I'm getting a boot loop with "No command". Any advice on how to continue? I'm a little worried because the adb command prompt doesn't see the device... at least it isn't listed under connected devices.

Edit: I managed to get into recovery mode and re-install the OPD1.170816.010 image and it boots fine, phew
[Google Pixel 2 XL Guides, News, & Discussion] pvtjoker42:
so, followed the steps, and tried to flash the patched boot.img and i get "FAILED (remote: flashing is not allowed in Lock State)

Yet if i try and run the fastboot flashing unlock_critical, it comes back saying device already unlocked.

update.. so apparently i had to fastboot flashing unlock, for it to register as unlocked (and redo everything on my phone again) so i'll get back to where i was and see if i'm able to flash from there.
[Google Pixel 2 XL Guides, News, & Discussion] Jchap808:
Unlock Bootloader

Currently unable to unlock the bootloader.

I get stuck at fastboot flashing unlock

Its prompting my a Failed unlock. Any fix?

Looked around seems to be associated with the OEM Unlocking being greyed out.
[Google Pixel 2 XL Guides, News, & Discussion] Golf c:
Verizon phone? Cannot be unlocked.
[Google Pixel 2 XL Guides, News, & Discussion] mackentosh:
Followed all steps and I rebooted, it's staying on the boot screen "G" and it's acting like it's loading but it's been on the G screen for 20 mins now. Is that normal?
[Google Pixel 2 XL Guides, News, & Discussion] nathanchance:
Which steps? There are a lot in the OP lol.
[Google Pixel 2 XL Guides, News, & Discussion] bajasur:
This usually means you haven't enabled OEM unlocking developer options first
[Google Pixel 2 XL Guides, News, & Discussion] cmexec:
I did the fastboot flashing unlock and have been using the P2XL unlocked for a couple of weeks, including Nov update sideloaded. In order to use the procedure in OP to Root, will I have to do fastboot flashing unlock_critical, which will wipe the phone (factory reset)?

-Paul
[Google Pixel 2 XL Guides, News, & Discussion] nathanchance:
If you only plan to sideload OTAs, you don't need to unlock_critical.
[Google Pixel 2 XL Guides, News, & Discussion] krash2k:
Hey everyone, when I try to patch

taimen-opd1.170816.010-factory-c796ddb4.zip

with Magisk Manager it just keeps crashing. It gets to the black screen with the outputs, says "extracting files", then "use boot image: ....", then Magisk Manager keeps stopping [close app].

Tried uninstalling everything, re-downloading the img, clearing the data/cache of magisk, same problem every time.
[Google Pixel 2 XL Guides, News, & Discussion] mackentosh:
You have to extract "taimen-opd1.170816.010-factory-c796ddb4.zip" and find the boot.img then place it on your internal sd
[Google Pixel 2 XL Guides, News, & Discussion] krash2k:
Yep yep that makes more sense now. That worked.. I flashed the patched_boot.img but now it just hangs at the white "G" screen with the moving progress bar on booting. Doh. ;/ :confused:
[Google Pixel 2 XL Guides, News, & Discussion] Cowbell_Guy:
What are the downsides of unlocking critical?