yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] 73sydney:
As menioned by me and a mod here: https://xdaforums.com/showpost.php?p=83639287&postcount=38

There are a few niggles with Android 11 (in general). For me it was not having the google assistant working hands free and my fave backup app Migrate not working due to some as yet unidentified changes in Android 11. Neither of which were attributable to the 11 version of this ROM. You may experience the odd ap that doesnt like to work under it. Just giving you a disclaimer, that if you have an issue, its likely to be the underlying Android 11, than the ROM.

Other than that fill your boots with either 10 or 11 based LOS

Usual disclaimer applies, this is an early build - but so far very very stable (the dev does great work), whereas the 10 based one is of course better tested and more road tested by users

The flash instructions in the OP of this thread are easy enough, and reocmmended for most people, pay special attention to the fact it includes a data wipe, so backup anything you love on your internal memory to PC first, and be prepared to copy it back afterwards. If you dont relish reconfiguring all your apps beforehand (Not all apps data is backed up by google, contrary to what most people think), use a backup solution to backup both user apps and user app data - Migrate is currently the best free backup option or a paid backup solution like MyBackUp Pro will do the job. Be aware that as i have experienced and noted earlier, Migrate currently has issues with Android 11. I have no knowledge of whether MyBackUp Pro does as i havent used it since moving to Migrate. So be prepared that some apps may need setup from scratch if you flash from 10 to 11.

Migrate/MyBackup Pro will get geenrally you a working backup/restore from any ROM ive ever tested personally from Android 8 to 10.

You can also find an alternate and less fiddly way that i and others pefer to flash it (since youre at the command prompt doing the data wipe, its really just exploiting already being there and involves less to and fro, manually copying files to and from the device and picking it up to do flashing etc, you can literally cable your device to the PC and then run through the commands, and only touch it again to unplug at the final reboot to go through the setup wizad, magisk enabled) here: https://xdaforums.com/showpost.php?p=83626593&postcount=30

Its just an alternate way of doing whats suggested in the OP and a suggestion you may like to consider. Its pretty much how i flash most ROMS, that dont have their own specific instructions/quirks

If in doubt, follow the install info in the OP
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] thomasck:
[MENTION=9317193]73sydney[/MENTION] Thanks for your answer. I'm going with the build based on A10 then. Even cause after upgrading from A10 to A11 the phone lost transfer files connection with the PC, it will connect fine to flash something but not to transfer files using explorer etc. The last phone I fiddled around with roms etc was a LG G3, long time ago. Many thanks for your answer. I just hope I won't have problems with online banking apps, like Barclays, which was the reason I did not install a custom rom in the PXL2 as soon as I got it. Thanks again.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] 73sydney:
No worries.

Your file copy issue under 11: i dont want to assume you overlooked it, but did you look in the notification pull down while under Android 11 to change the USB mode from Charge to File Transfer? sorry for asking, just being thorough :)

If you have issues with banking apps on a custom ROM, magisk can be made to work around it msot of the time, and im not up to speed on Barclays but theres a thread here (latest one i could find in 5 seconds): https://xdaforums.com/apps/magisk/barclays-banking-app-t3955900

It has posts by one of the nicest people i know on XDA Didgeridoohan (who maintains a knowledge base on magisk matters), between him and the other magisk rogues i know a solution can be found for most things. If youre also looking to use Google Pay, well then as luck would have it, i have a magisk module for that (link in my signature below), with very up to date instructions (plus some code contributions from the Didgeridoohan) that gets it working for most folks :)

Technically both the Barclays and Google Play fixes/hacks are Android version agnostic, aka those solutions should work under either 10 or 11 for you, if that helps to widen your choices regarding trying this 11 version :)

Im lucky in that my bank only checks for root, so i can just go to Magisk, and then MagiskHide Settings and toggle it for my banks app, thereby hiding root from it. Barclays it looks like scans for packages it identifies as being present on a rooted ROM, so needs a little bit more fiddling to hide...

Feel free to PM me, as well as post back in the relevant threads, if you get stuck
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] thomasck:
[MENTION=9317193]73sydney[/MENTION] Yes, sure I did! I've tried all options in the notification pull down and none of them worked. I've tried new drivers, new cables, other usbs, another PC and another laptop. That brought me back to the gold times with the curved Nexus S :D I will read the link about Barclays and Magisk, many thanks for pointing me that. Would you please name the main reason you are using BlissRom now instead of Lineage?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] 73sydney:
Okay, cool to know youve tried all those things, but thats weird it would stop working under 11

The reason im currently using BlissROM as opposed to LOS 17? Easy, it was the very first ROM i tried, after stock, when i moved from my previous device (Note 4) only recently, and due to being time poor i havent had time to try the LOS 17.1 build, the time i did have free i put towards trying the stock 11 upgrade and then the LOS 18 build. I do have the LOS 17.1 and AOSiP ROMS (all by [MENTION=9116297]Eamo5[/MENTION]) downloaded and in the queue to try. Just been a bit busy with documentation and other updates in my own projects here and elsewhere. I also admin a number of sites full of wifi (i have 32 years in IT, now mostly spent in networking), which as you can imagine with everyone being home due to COVID, keeps me rather busy, gotta keep the kids in Netflix.... Tiger King or whatever theyre now streaming :)

From what i can gather any work by [MENTION=9116297]Eamo5[/MENTION] is solid as!

So, short answer, just time :)
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] thomasck:
[MENTION=9317193]73sydney[/MENTION] Wow, nice! I've just started studying IT with Computer's Science, I literally had my first tutorial yesterday after 12 years away from the book. I've studied Electrical Engineering before, but now I work as a chef, my hearth walked towards the kitchens instead to engineering. And now I'm again up to this new challenge, maths, everything again :D

Well, right now I just booted into LineageOS, got couple of signature errors while flashing gapps and magisk but after allowing through the mobile itself looks like it installed correctly. TWRP it's bit different now too. I'm getting "no sim card" and some more errors related to it like "Sim maganer keeps stopping". Gonna Google around!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] 73sydney:
You shouldnt be getting any signature errors

Be aware that theres 2 ROM zips available for each device Pixel 2 (walleye) or 2 XL (taimen), one with and one without g-apps

Which did you download? and how did you flash exactly?

You may be getting those errors if (theoretical until i know what and how you flashed):

youve flashed gapps on a ROM zip that already had g-apps in it

Update: off to bed, its 5am here, ill follow up when i surface later, had a long day yesterday, somehow merged into today :)

Update #2: Poster is flashing LOS 17.1 and using that thread now
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] friedsonjm:
Project Fi Compatibility?

How is Fi compatibility with this ROM, in particular, wi-fi calling?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] dbroer91884:
So I'm running LOS 17.1 on my pixel 2 xl. The method for flashing roms was to just flash the zip using adb, which also flashed the LOS recovery. Can I just flash this ROM using the LOS recovery since I'm already on LOS 17.1 or do I need to reflash TWRP, wipe everything, then flash this ROM?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Eamo5:
Lineage OS 18.0 (10/10/20)

October ASB

Added music, recorder and updater apps

Added per app wifi data, cellular data, background data and vpn data control

Added Lineage Customiser (font, status bar icon, accent colour selection)

Enabled conversations support for supported apps (thanks kdrag0n)

Added black theme support to Settings

Added system profiles support

Added status bar brightness control

Added network traffic monitor to status bar

Added custom charging sounds

Added volume panel location option

Added Trust HAL

Fixed 3rd party app fingerprint authentication (thanks kdrag0n again)

Updated pinner service configs from coral and tweaked for better memory management (thanks kdrag0n.. again)

Added 3 row QS when no media is playing

Updated AOSP webview to 86.0.4240.75

Fixed settings search breaking when taking an update

Fixed settings crash when rotated and searching

Added AOD, caffeine, sync, heads up notifications, sync, volume panel, ambient display, USB tethering, reading mode, VPN and profiles QS tiles

Added QS auto-brightness and brightness slider options

Lots of minor bug fixes and improvements
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] DrupadSachania:
can someone please let me know the issues in this ROM, other than that are mentioned in OP.

Thank You
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] sfpcservice:
I flashed the Rom and now I'm using adb to flash TWRP but TWRP cannot decrypt my phone even with the right password. Is this a known issue or am I doing something wrong?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Nixin Victis:
Lookin good so far, thank you. How much work would it be to post a microg variant along with the basic one and the gapps one? i noticed the "Lineage for Microg" team has a lineage 18 dev branch. that would be so slick if you could do that. if its a little too much work, i got 5 on it, or should i just wait for them to do it? but they don't typically do any bells or whistles <3
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] sfpcservice:
Disregard I solved it.

---------- Post added at 12:04 AM ---------- Previous post was at 12:03 AM ----------

Next question, Trying to flash magisk for root but it causes a boot loop. What do I need to do?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] sfpcservice:
https://github.com/topjohnwu/magisk_files/blob/canary/magisk-debug.zip

How does this work? If I flash via TWRP I get a boot lootp.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] almahix:
Loving this ROM. Thank you so much!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] 73sydney:
Do NOT install TWRP, just fastboot to it if needed

Installing TWRP and flashing magisk ends in bootloop

How i do it is here: https://xdaforums.com/showpost.php?p=83626593&postcount=30

Things to try, to avoid (hopefully) redoing everything again:

Easiest to fiddliest...

a) TWRP -> Advanced -> Fix Recovery Bootloop (has worked for a few)

b) Flash Magisk uninstaller zip - should restore original boot image, if not, or instead...

c) Flash original boot image manually

1) Boot (or fastboot) TWRP

2) Look under /data for a folder beginning magisk_backup

3) In this folder will be boot.img.gz, copy somewhere easy to navigate in TWRP terminal, like /sdcard

4) Unzip this file in TWRP -> Advanced -> Terminal -> gunzip /sdcard/boot.img.gz

5) TWRP -> Install -> Tap Install Image (in lower right)

6) Locate /sdcard/boot.img and flash to boot

6) Reboot
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] dbroer91884:
Hey so I'm not sure I did this exactly right. I ended up using ADB inside of TWRP to flash the ROM. Things seem fine doing it that way. My question is I seem to have an issue with the keyboard crashing everytime I try swipe typing. Anyone else have this and know how to fix it?

Otherwise, this is great. Thanks for the ROM.

EDIT: Nevermind, I just installed Google's Keyboard and there are no issues with that.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
AOSP keyboard doesnt work with swipe (FCs), Google's keyboard is the best free option in my opinion.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] sfpcservice:
I'm using Google Fi, noticed the Google text app is only sending via sms and wifi calling isn't working.

Is there a way I can get this working or is it not compatible with this rom?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Eamo5:
This will be fixed in the next build. Thanks for pointing this out.

Fi, RCS and WiFi calling should work. Fi and esim generally won't work on the gappless build. I can't personally test but feel free to grab a logcat and PM it to me. Can anyone else confirm this issue?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] sfpcservice:
I am using the Gapps build and a physical sim. I'll try for the logcat.

Should I logcat via adb or an app?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] friedsonjm:
So, Fi is working on Taimen with Gapps and an esim?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Eamo5:
Lineage OS 18.0 (9/11/20)

November ASB

Switched to gappsless builds

Added Seedvault (open source backup / restore tool)

Added QuickWallet support (thanks kdrag0n)

Added more Trebuchet launcher settings

Fixed SetupWizard bugs when flashing gapps

Added the ability to hide the gesture navigation bar

Fixed power button torch controls

Added expanded volume panel

Fixed AOSP keyboard crashes

Various updates to AOSP dialer, messaging, contacts, clock, camera and keyboard

Lots of bug fixes and improvements

CTS will fail again because of fingerprint mismatch this month. Either use another device fingerprint or set the platform security patch back to October.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Cydras:
Awesome for hiding navigation gesture bar!

Will flash it end of the week :)

Should I update before flashing to Android 11 Stock Firmware first? I am on 10
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] amandeepparmar:
How do we set the platform security patch back to October? Steps?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Eamo5:
Taken from los 17.1 thread and amended to reflect android 11 builds.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Sorry I forgot to reply to this user. I haven't tested the latest 18 release (this version) but it should work.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] gogol:
DELETED ...
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Eamo5:
For those of you who use Android Auto and were having crashes, [MENTION=614507]razorloves[/MENTION] has created an unofficial opengapps package with this issue fixed!

https://sourceforge.net/projects/ra...0-nano_with_androidauto-20201031.zip/download
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] thekwijibo:
I'm excited about this project, and willing to explore a bit more. Now that my stock Pixel2 won't receive security updates in the future, I'm looking to flash LineageOS. Trying to decide between 17.1 or 18.0. Are there any significant reasons I should go with one over the other, or is that discussion mostly stability/feature related? Mostly wondering if I'm going through the trouble of doing a full wipe, should I go 17.1 or 18? Do OTA updates work on both of these ROMs?

Also, if I flash 18.0(unofficial) will updating to a future official 18 ROM be rather seamless, or would one likely need to do a full wipe again?

Thanks!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Personally I have used both, and both works flawlessly for the most part. Right I am now on LOS17 but only because I was testing something for another user otherwise I would probably be on an 11 ROM (either LOS or another 11 ROM). Either one works, LOS17 is updated more often, and is maybe is a little more stable with bugs (although I haven't found any showstoppers in 18), but 18 is newer so more likely, it will have more bugs than an older running and older maintained OS. 17 is official, 18 is unofficial but again, both work well so it all depends on what you are looking to accomplish, you need to ask yourself, do you like unofficial, do you want more updates quicker, things like this are the real questions on what one to use? Only you can answer these questions, as both ROMs work as daily drivers in my opinion.

I cant answer on the unofficial/official release question, but most likely the OTA will work and would flash unofficial to official unless the dev notes otherwise. I wouldnt try to go from 17 official to 18 unofficial though so choose one or the other, than stick with it. If you are worried about the unofficial stuff, stick with 17. Its official and rock solid.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] thekwijibo:
Awesome. Thanks for the reply. That's pretty much what I was hoping to hear.

One more question about LOS18... are the updates pushed through the built-in updater, or does one have to flash those through TWRP?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] palimatix:
Not yet. The built-in updater works once LOS goes official. So for now LOS17.1 has it, and 18 will be in near future hopefully.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Correct, 18 is unofficial so manual updates. 17 is official and thus receives official updates from LOS service. 17 uses the built-in official updater and checks in for you to notify on new updates and works on its own (no recovery needed). It really comes down to what you're end goal desire is when choosing between the two. Both are excellent in my opinion, both are stable, the 17 is official so it's great and has everything working but is a 10 ROM. 18 is an 11 ROM but has the risk of unknown or not found bugs yet and manual updating process. Each ROM has plusses but one is 10 and official, the other is 11 and unofficial. It comes down to your personal preference choice on what is important to you. Personally I go back and forth between the two, mainly to test and help others (I also have the pixel 3 XL) so I can use either ROM on my 2XL and not matter because of having a second device. If I run into issues in my 2XL, I just switch to my 3XL. By having a second phone allows me to thoroughly test everything on the 2XL but I do not lose my number or availability for mobile service (for kids, work, etc.), so technically I'm never offline. This is why I can toggle between so many ROMs and not care. I'm only mentioning this to you so you know why I'm switching so much, it's not a ROM related reason, but simply to test and help others. My 3 XL offers me that freedom.

-EDIT sorry quoted the wrong user, this was meant for the OP on the question
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] wmhaganjr1013@gmail.com:
kernel ???

Sorry i wanted to know can Sultan-Kernel-R-10-10-20 be flashed to this or is it already included
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] :
When to expect Pixel 2/2 XL LOS 18 Official Release

Any idea when the official versions of these ROMs might be available?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
NO ETAs ever, it annoys the devs who do this for free, on our own free time. It will be released when its released if the dev plans on it or it may never be released, you are free to build the ROM from code yourself if you want it sooner. No one is stopping anyone fro building their own flavors, so wait it out and be patient please or build the newer ROM from code on your own.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] mariospizza:
In a device with root permissions, is there a way to boot TWRP (without flashing it) from Android itself, on-demand, without the need for a PC with fastboot? It would be handy when having to upgrade LOS.

Alternatively, would it be possible to flash this ROM and then Magisk via the Lineage Recovery, avoiding the TWRP + Magisk bootloop issue?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] svaethier:
so when flashing this rom do I use the sideload option in twrp or is there a way to flash the rom from internal storage?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] legaldexter:
- Flash latest factory images for walleye from Google, boot

- adb reboot bootloader

- fastboot boot twrp-3.3.0-0-walleye.img

- Wipe data/factory reset inside TWRP

- adb push [LOS18] /sdcard/Download

- adb push Magisk-v21.1.zip /sdcard/Download

- Install [LOS18] inside TWRP

- Install Magisk-v21.1.zip inside TWRP

- From TWRP Reboot->Power Off

- Power on Pixel 2
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Deltafox79:
hi I have two question

1) how to fix magisk ctfprofile error on this rom?

I have try also magisk hide props module whitout succes after restart some voice of build.propr is restored..

2) how to avoid at each restart that the rom deletes the twrp recovery and inserts its?

Thank's for the reply
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] jukolein:
1) Do you use "hardware" or "basic" as checking-method? It needs to be basic, you can change it via a terminal-emulation, first becoming supersuser, then typing "props" and following the instructions. Besides the "basic"-check (second in menu) you also need to get an other fingerprint (first in menu). Both combined worked to pass SafeNet.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Deltafox79:
Thanks for the Info..
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
If you go back a few pages, you will see my simple steps to reset the security using a boot script. This works much easier and is cleaner than props. I prefer not to use MAGISK props or modules as I find they tend to mess up other areas so I prefer the cleanest method. This only involves 2 lines of code, a permission set, and to store in the service.d folder. Once you reset the security and hide MAGISK (enable MAGISKHIDE) you will pass safetynet. Nothing fancy with it, just a simple script that tricks the system into having a matching security date.

I am unsure what you are asking about the deletion f files, are you saying your build.prop is reset at every boot? Mine didnt do that, so please explain. I set certain code in build.prop that didnt change on my reboot so I am not sure what you mean. I wouldnt bother installing TWRP as a recovery, leave the default and just ADB when its needed.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Deltafox79:
Thanks for the reply, ok I'll take a further look at your post and yes my build file is recovery was being restored on every reboot

Inviato dal mio Pixel 2 XL utilizzando Tapatalk
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] legaldexter:
When will it be getting official and updated to December patch?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Strephon Alkhalikoi:
When the developer decides to. Bad form here to ask a developer for an update.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] calsurferpunk:
Quick question: Has anyone else had issues with Google Maps crashing/force closing right after opening? I don't know if it's related to the ROM, OpenGapps I used (latest from link on first page, 11/16 I believe), or something else. It was working for me using the standard AOSP version prior to switching (now that our device is officially unsupported). It might just be me, but I thought I'd ask. I've tried uninstalling, clearing data, and clearing google play services cache/stopping/restarting.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Eamo5:
This is a bug with opengapps. I thought they'd released a new test build with this fixed but seemingly not. For now you can use these gapps by razorloves.

https://sourceforge.net/projects/razorloves-lineage/files/gapps/open_gapps-arm64-11.0-nano-20201121.zip/download