yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Scottay5150:
Update: after pulling my hair out with the lack of customer service at Chase Bank I've decided to cease my relationship with them.

There was a block or flag on the card I could not add to Google Pay. They could not see it for some unfortunate reason. As soon as I went to order a new card they canceled the one I had in my possession which was technically still good. And then said they couldn't issue a new one until I went to a location. Now I'm without card, grr.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
I had a feeling...all the way back a week ago...

Wow, that is a terrible amount of issues from a "block or flag"... The similar experience I had gone through with Citibank was resolved without that much difficult...but then again I had went to a physical location, and even there, the bank agent had a hellllluva time getting things answered by the various departments (fraud even!) and resolved (still took "1 or 2 business days")...It's regrettable that, if you had wished to keep the card as it "...was technically still good", this information (or what had worked for me) might've helped beforehand...

In any case, sorry you've had all those issues...
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] muyela:
No option to select boot image

Please disregard
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] thundercattt:
hmm
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] me_droid:
Thanks, got it rooted. Now regarding TopJohnWu's OTA installation tutorial, have you or anyone else had that actually work? The step by step is straightforward enough but I've never been able to make it work.

https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md

1. Disable automatic system updates in developer options.

2. When OTA is available go to Magisk Manager - Uninstall - Restore Images.

3. After applying OTA via settings - system - system update, do not press "restart now" or "reboot". Go to Magisk Manager - Install - Install to inactive slot.

4. When done, press the reboot button.

Step 3 doesn't seem to work for me - it appears as though it's preparing the update but then reverts back and reports that the system is up to date. No matter how many times I recheck, it always comes back up to date with last month's update. So I eventually rebooted the phone and got the LoadImageAndAuth Failed: No Media error. I had to flash the full image to get access to the phone again.

Is it a matter of timing - if the phone detects there's an update and you haven't restored images in time then will it block your phone from receiving the OTA?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
...Yeah...it doesn't seem that an OTA can be done with the stock Android System Updater when rooted (w/ Magisk) -- I was under the impression before that, as long as you didn't "write" to a partition via installing a custom recovery or kernel, you should be able to un-rooted, but I have since learned that that isn't the case... actually, I just now read something to the contrary, so I'm not really sure. I may be getting confused with TWRP and Magisk (as I use both), but as far as I can remember, I believe I remember seeing many who have stock recovery and are rooted and still unable to get the OTA through the stock updater to work...-- but, if you insist, you can install an OTA update manually; The step by step method I thought of (and was written out by another user) can be found

HERE

, but in my (and most experts here on XDA) opinion, if you are going to do this, you are best off simply flashing the Full Factory image instead of the OTA as it will completely flash over the /system and other pertinent partitions (and therefore potentially taking care of the bugs in said system) rather than the OTA which is more of an add-on and modifies the system and other partitions (and therefore would just build upon anything that may be "buggy")... *note: be sure to make a (preferably nandroid) backup whenever running fastboot or "flashing" anything, it's best to...

Other than that, I don't believe you can successfully use the stock updater unless you have a locked bootloader (WARNING: Unless for very particular and/or extreme conditions, it is best to never relock the bootloader...There are

so

many stories of fully bricking the device with no hope of recovery...)

Hope this helps...
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] me_droid:
Thanks, this confirms what I thought about the tutorial's method not working. I'll just go back to flashing the full update and rerooting each time. I was just hoping magisk manager could handle it all. Agree with you that it's probably better to flash the full update rather than the ota and probably doesn't take much more time,if at all.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
Yeah...definitely OTA < Full Factory image; I mean, you lose root and custom recovery/kernel (if you employ them) anyway and will have to re-install them after either image, you're less likely to retain anything buggy and giving the /system a good refresh, you're gonna have to go through the trouble of going to the website and downloading the .zip file(s) regardless (especially if you have to involve a computer "medium"), and -- if anything goes wrong -- you'd already have access to the boot image file and/or the files you would need if you were in need to use Deuce's script...
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] failax:
I flashed the ota zip and the patched boot image always from adb, but it remains stuck in the opening of the OS. Only reflashing the original boot.img make the Android restarts.

Before trying to flash Magik zip from TWRP as suggested from other users, it is normal that the main procedure doesn't work?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] CyberpodS2:
I believe flashing the OTA is the same as flashing a custom ROM in the sense that it switches from A>B or B<A on reboot. So if you do your rooting in the same session you are in essence patching the wrong side... So if you just reboot back to TWRP in between the OS and Magisk you should be good to go.

Unless I'm missing your question and then someone will be happy to correct me. Lol
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bballer182:
Neither of the magisk patching methods are working on my Pixel 2 after the May 5th security update
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] chazall1:
Issues with installing the Magisk-v19.1.zip?

I am on may and have no issues with Magisk-v19.1 stock
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] saham424:
I had the same issue on PIXEL 2 XL. Flashed OTA via TWRP. Flashed Sultan May kernel then TWRP.zip then MAGISK. would not finish opening the os. it tries to open and gets to the white google icon loading screen vibrates but then reboots. Tried different kernels and that didn't work. Flashed uninstallMagisk.zip and boots up fine. I didn't have an issue with the April update last month only May.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] CyberpodS2:
Lot of folks having issues on May update with latest Magisk and or TWRP. Couple things mentioned around here so far.

-Updating from April keeps decryption working on TWRP where a clean install blows it up. Also, folks with the 3.3 have had failures where 3.2.3-1 is working.

Folks who have not loops on 19.1 and 19.2 seem to have some success with 18.x versions...

Just thought this would give a place to start if you have issues...
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] StunnerDude:
To everyone having issues on Pixel Devices with the May update, here's an official response from [MENTION=4470081]topjohnwu[/MENTION]: https://github.com/topjohnwu/Magisk/issues/1432

I used the latest uninstaller zip after flashing the OTA, then rebooted back to system. After making sure it booted, I rebooted to TWRP (using 3.3.0-0) and flashed Magisk. Then reinstalled whatever modules I had that were also in the official repository. Finally I booted with Magisk installed. I used the Canary build, but stable should work as well.

The module that I think caused the bootloop for me was USB Policy Patcher.

Cheers ;)
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] CyberpodS2:
Cool man thanks
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Will008:
I haven't had any issues with the may update. A big top would be booting into system every step of the way to make sure ur last step didn't mess something up. Here's my sequence:

- Wipe data on EXKM app

- Boot into fastboot

- Flash the latest May stock image (remove the -W)

- Boot into system

- Go to fast boot boot into twrp and flash twrp (3.3.0)

- Wipe dalvic

- Reboot into twrp

- Wipe dalvic

- Reboot into system

- Reboot into twrp

- Flash your kernel of choice ( in my case EX)

- Wipe dalvic

- Reboot into system

- Reboot into twrp

- Flash magisk (19.1)

- Wipe dalvic

- Reboot into system

Overly cautious I know but this way I would know which step messed up and work on fixing it directly. Hope all this helps.

Cheers
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bballer182:
Got 19.1 magisk working on the May update on my Pixel 2.

I think there is some sort of incompatibility issue with TWRP 3.2.3 and 19.1. I was able to get Magisk 19.0 to boot with TWRP 3.2.3 but when I upgraded to 19.1 after I got it to boot with 19.0 I lost TWRP and the boot. Reflashed my stock boot.img and all was well again. Upgraded my TWRP to the current release and was able to flash right into 19.1 without going from 19.0 to 19.1.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] saham424:
I figured it out! Latest May update breaks TWRP 3.2.3-1. I Updated it to TWRP 3.3.0.0 and flashed Magisk 19.2. Booted up perfectly!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
It's funny you say that. Couldn't get twrp 3.3.0-0 to fastboot, so I used the previous version which worked fine. Gotta love the unexpected variety that the P2XL offers from time to time! ???
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Az Biker:
My life is so busy right now with selling a house, buying a new one, moving and setting things up, I haven't updated ANYTHING since March security update and EX 2.15 :p

With all the shenanigans going on with latest security update, TWRP, and Magisk, looks like I'll stay right where I am for another few weeks until I have some time to sit down and digest all the changes and pitfalls :D

[MENTION=3730810]Badger50[/MENTION] I expect you to have this all sorted out, with a detailed, step by step guide posted that I can use when I get back in the saddle in a few weeks :p
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
Hahahahahaha...it was pretty simple for me ol friend. Did the May update just like always with fastboot to both slots without the -w, and let it boot up twice without issues. Then, Twrp 3.3.0-0 didn't fastboot for me for whatever reason despite multiple downloads, but, twrp 3.2.3-1 worked fine. Then magisk 19.1 would boot up, so went back to twrp, flashed magisk uninstaller, rebooted to twrp, then flashed magisk 18.1, and I was golden!

Funny thing is, others had no problems with twrp 330-0 and 19.1 provided they dirty fastbooted the May update. But hey, this is the P2XL, so anything unexpected, is to be expected. I swear this phone is just like my wife of 32 years....still allowed to change her mind at any time! ???

Where you moving to bro? :laugh:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] CyberpodS2:
Mine booted fine too but when I went to install a zip for a magisk mod it could not get access to /system. Going back to 3.2.3-1 fixed the issue.

---------- Post added at 03:31 AM ---------- Previous post was at 03:28 AM ----------

Cool man. April of 1988 for us. Lol
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] murphyjasonc:
I updated to the May release and flashed Magisk 19.1 with a custom kernel and got a bootloop. I tried the Magisk uninstaller, reflashed my boot img and tried without a custom kernel and still got a bootloop. I tried again with the canary version with the same results. I read that some people had luck with the 18.1 version so I tried that. It booted after I flashed it but Magisk wasn't installed. I was about to pull my hair out at this point. Thought I had tried about every possible combination then as I was scrolling through my files I saw Magisk 19.0 just sitting there and I figured what the hell. I flashed it and it booted right up. After that I booted back into TWRP and flashed a custom kernel and rebooted. Then I updated to Magisk 19.1 with direct install from within the app without a hitch. I have no idea why version 19 worked while none of the others did for me but I'm rooted again.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] clothednblack:
Yep, got all screwed up after taking the may update, tried and tried and finally gave up rooting and twrp and took the plunge for beta Q instead. Not a bad idea as I need to get use to not having root come August/September, I will be leaving the pixel phone behind
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] srqrob:
Curious what's luring you away if not personal?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] clothednblack:
Well, it's a few things.

1. I've been doing this long enough

2. I kinda miss the days of just letting my phone update when it was ready.

3. I don't really need root much anymore, things have changed in the android world and I've been on stock for almost a year now (other than BlackenedMod) not really flashing anything, just letting this pixel do it thing other than monthly security updates.

4. This is the biggest reason..... The Note 10 is coming and it's going to be a beast! Had the N3 and loved it, it time. Been reading all the leaks and rumors, I'm ready to go full stock and leave all the crazy flashing days behind me. Not sure what I will do with all my free time now lol.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] srqrob:
Thanks. Samsung is one of the companies I love to hate. Probably occasionally shoot myself in the foot. :D
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] clothednblack:
Yeah, they all have ups and downs, pros and cons for sure. My work phone is the S8 and my wife just got a S10+, oldest son has the S8 edge or something like that. My daughter has my old pixel xl, and I've got the XL2. Been through a lot of phone's and ever since the Droid X, I was always making sure that the next phont was going to be able to be rooted. I'm tired of making my purchases based on just that factor. Getting to old for all that ?. I certainly have met a ton of people and became a mod in a few forums through the years. Ready to retire and see what it's like again to just let the phone run its course without my influence ?.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Az Biker:
I absolutely believe that you are not alone in this line of thinking.

If it wasn't something I really enjoy doing, I wouldn't see the need to root much either.

It does get frustrating having to choose your new device based on the ability to root or the amount of dev support it's getting, but I do like the idea of having the "option" of doing whatever I want with my device "should" I decide to do something that requires root.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
Got a feeling i'll still you around from time to time my friend. Oh...and your not old, just busy is all! [MENTION=4670411]Az Biker[/MENTION] and I are old, and busy, but it's cool man, my Mrs. loves her N9, and the screen and speakers are so much better than mine, which is definitely a plus. I'll have a look see when the N10 and P4XL comes out, then make a decision. I still like rooting and all that, but trying something new is always fun. :good::laugh:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] clothednblack:
Oh yeah, I'll still be around from time to time and who knows, maybe the N10 will have root, I've seen some crazy things in my years ?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Rydian:
Having an issue with the phone unable to finish booting.

Pixel 2

- Unlocked bootloader, let it wipe.

- On the May 2020 update, so I downloaded the original from Google, confirmed the numbers matched, and copied the bootloader image to the phone.

- Installed Magisk Manager 7.5.1 (from the github releases).

- Ran it, patched bootloader-walleye-mw8998-002.0081.00.img, pulled the resulting magisk_patched.img back to the PC.

- Ran "fastboot flash boot magisk_patched.img" and it appeared to succeed and I told the phone to reboot, but it won't finish booting now.

When I try to turn the phone on normally it gets to a Google logo with an unlocked icon underneath it, but displays no changes even if I wait a while.

Turning the phone on while holding volume down gives me a menu with the below options.

Start - Unable to finish booting like usual.

Restart bootloader - Returns to this same menu.

Download mode - Returns to the same menu, but adds a highlighted line at the bottom stating "ERROR: Operation Denied".

Recovery mode - Unable to finish booting like usual.

Barcodes - Displays some information and tells me to press power to go back.

Power off - What it says on the tin.

At no point does adb list the device, but while in the menu fastboot does.

I'm unsure how to proceed from here, any advice?

EDIT: Okay so it wasn't specifically the bootloader I had to re-flash, I ran flash-all.bat from the stock image download to do all of them and that seems to have worked, I'm back to stock and it functions but no root/magisk.

EDIT 2: Just ended up installing TWRP from the official site instructions and then flashing Magisk, worked great, rooted and all I didn't even know Android could boot off a temporary image nowadays.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] deedeedee12:
Good Evening,

I own a Google Pixel 2 XL(32 GB) (Verizon as my service carrier) and I have recently updated to android 10 updates, rooted and bootloader unlocked. I recently tried to reformat the device to its original state because the device was stuck in a boot loop. Using twrp 3.0, I mistook by pressing wipe in the system while in twrp. And due to this I am unable to load into system recovery mode, nor would the system turn on. And I keep getting this error. It says with a red warning sign, "Your device is corrupt. It cannot be trusted and may not work properly. Visit this link on another device: g.co/ABH

Hope you'll help me.

Thank You
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
Have you tried clean fastbooting the factory image you were on? You'll completely wipe the device, but then again, it sounds like you've already done that.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] deedeedee12:
I tried to but the computer unable to detect the device through cmd
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Sui77:
You have to boot into bootloader, just like you used to boot into twrp, but without starting recovery

Than run the .bat in the factory image (after removing the -w in the.bat with an editor)
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Az Biker:
Also make sure you have a few diff USB cables handy and the 2 XL can sometimes be finicky and act diff with a diff USB cable.

There's a detailed step by step in my sig if you need any help along the way :good:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Alxoom33:
Make sure you have the latest adb/fastboot files downloaded from Google's Android.Developer's website.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Alxoom33:
Why would you follow a suggestion on a Pixel 3 thread, on a Pixel 2 XL??

My suggestion, is to download and flash the full Factory image for the Pixel 2 XL, either the latest Android 10 or RPB1.2 from Google's Android Developer's website. Back up your data, wipe, flash and then restore.

Then you can start clean.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] romanticnutan:
i already flashed facctory image by both methode by running flashall.bat and flash from website. every process complete succesfully but when i boot system it goes back to fastboot and after some time it stuck on google logo forever.

is there ant other way to clean flashh factry image??
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Alxoom33:
Yes, dl the full factory image from the Android Developer's website, extract and flash it without removing the -w. Will wipe your device clean and you will start from scratch. Be sure to back-up your internal storage on your computer to restore later.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] romanticnutan:
i did that already. download full factory image extract it and run flashall.bat all process completed but when i boot it iether goes back to fastboot mode or stuck at google logo
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Alxoom33:
Which factory image did you use? I recommend that you download the April 2019 Android Factory Image. Then update using OTAs to latest Android 10 or R beta.

You may also want to use stock recovery to wipe or fastboot format user-data. Both worked for me when I needed the nuclear (last resort) option.

If that doesn't work you may want to RMA the device.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] skyliner129:
Can Magisk be used to root a pixel 2 XL already on Android 10?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Lughnasadh:
Yes
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] skyliner129:
The pixel 2 XL is already on Android 10 and the bootloader is locked, also the phone has never been rooted. If it is still possible to root and possibly unlock bootloader, kindly recommend the right tool to use, preferably a link. Thanks in advance
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Lughnasadh:
As long as you don't have a Verizon variant you can unlock the bootloader so you can root with Magisk. I suggest you read these guides thoroughly before doing anything...

https://xdaforums.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418

https://github.com/topjohnwu/Magisk
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Alxoom33:
Go to the Android developers website, download and set up latest Google adb/fastboot files on your computer. Then look at the Android Developers website for rooting instructions using adb. But first go to Settings/Developers Settings and flip the toggle to enable OEM unlocking and enable adb debugging. Then proceed to unlock your bootloader and boot into TWRP using the fastboot boot command.

Also read the above guide by Nathan Chancellor, nickname "the Flash"[emoji16][emoji106]
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] chadhoard:
Everything was going smoothly until I ran the "fastboot flash boot patched_boot.img". I received a "FAILED (remote: Flashing is not allowed in Lock State)". I had already went in and turned on OEM unlocking. What am I missing??
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] joetheshmo:
Did you actually unlock your bootloader?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] chadhoard:
It was my understanding that did unlock the bootloader. Looks like I was missed informed. Where do I unlock the bootloader??
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Fenny:
For those wanting to try this on the 8.1 beta, here is a stock boot image: boot.img.8.1.OPP5.tar.gz. Just extract it and patch with magisk.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] cwalker0906:
Updates are live on googles site
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] jointfull:
November Update Published

It has just been published on Google's Factory Images page..

Direct link: taimen-opd1.170816.025-factory-907c4030.zip

:good:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] joetheshmo:
You need to use the command fastboot flashing unlock and then fastboot flashing unlock_critical

These commands will wipe your device as they unlock the bootloader!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Fenny:
Sadly, it looks like they did not include beta 8.1 firmware images. If you need that, the kernel is posted above, and I can confirm that this Magisk build works on 8.1 as well.