yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] mistermojorizin:
I am mostly a very happy camper and I appreciate everyone that's given support and ideas to try. This is what I was looking for in a rom, a small community where you don't get lost in the crowed. The problems I'm having are relatively minor now.

here are the problems after update:

1. not a big deal - the android warning on boot. I didn't have that on 1.5 with magisk 16. I've been trying the fixes in the forum, like flashing the stock .img but they just bootloop. not a big deal though, like I said.

2. I can no longer change boot animations with substratum. It asks and gets root, but then says "failed"

3. This one is driving me nuts the most: the chronus widgets i had installed on home screen (nova pro) won't work after the update. "problem loading widget". same thing on stock pixel launcher, but they work on Apex launcher. Also, the Chronus widgets I didn't have on my home screen prior to the update work fine. I've tried uninstalling and reinstalling chronus and dashclock and the errors persist. I've cleared dalvik cache and I had *nothing* in the one arm64 dalvik folder OP mentioned. Any ideas on what to try with this?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] gargeya_369:
I agree, the widgets are not loading at all.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] danw_oz:
How I was able to install 16 was full magisk uninstall, boot rom confirm magisk manager gone and no root, boot twrp and then flash 16
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] TheUndertaker21:
i wasn't able to boot it up even with 14.5
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] danw_oz:
this worked fine for a day, then all started to lag again, and battery drain was very high. I think I am going to flash March using deuces script and root and leave it that, since it runs normally like that for me.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] mistermojorizin:
i'm finding out it's not just Chronus. My stock, calendar, mail and clock widgets won't load (and that's probably what was messing up chronus and dashclock - it was only the widgets with extensions that didn't work, those extensions were asking for data from calendar, mail, etc.).

I am thinking that whatever is on slot b (a rooted updated system in my case without RomAur) is messing with what's happening on Slot A. I'm gonna try to make a backup of A and restore it to B. Ideally I could just wipe B, but I'm afraid I don't know which partitions to wipe so that A is not effected.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] gargeya_369:
So, basically my google calendar and whatsapp widgets won't load and show a message as " cannot load widget" on the widget space.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] mistermojorizin:
what's even more strange is that some of the widgets work. For example, calendar has a calendar widget and an agenda widget. The calendar widget loads, the agenda widget times out and says cannot load widget.

Same thing with clock. Analog loads, but digital times out.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] danw_oz:
Flash deuce script, then flash twrp and magisk again
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] TheUndertaker21:
Lol I did.

Bootloop
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] mistermojorizin:
try this:

1. deuces

2. flash twrp permanently if it's gone

3. switch to B (reboot menu in TWRP) and reboot to recovery again, make sure you're still on B

4. magisk uninstall zip

5. rom

6. magisk 14.5

7. switch to A, reboot to recovery (make sure you're still on A)

8. magisk uninstall zip

9. rom

6. magisk 14.5

7. boot system

I've been troubleshooting widgets, so I factory reset the phone and had to reinstall romaur. I also reverted to a pre-march backup and reinstalled the update. These were basically the steps I had to follow for it to work. I've now done it 3 times. I think key is the magisk uinstall zip, and do it on both A and B. They somehow affect each other.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] ichibanpnoy:
Anyone else lose functionality of the "Swipe fingerprint for notifications" gesture? Anyone know of a fix? Current workaround is Fingerprint Action Pro app, but it is not as responsive as the stock gesture.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] mistermojorizin:
I can tell you it works here.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Beakhole:
I feel like I'm banging my head against the wall. I just got the Pixel 2 XL. I followed the above instructions and it still fails. I also followed these instructions and these instructions it still just goes to the corrupt boot message and constantly bootloops. I'm not even installing Magisk because I couldn't find a download for Magisk v14.5. I planned on just installing Magisk Manager and doing a direct install from there.

Anyway, can someone please enlighten me? What am I doing wrong here? Are all of the above instructions required when starting with a brand new phone on stock 8.1? Or am I supposed to be doing something different?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Bojesse:
So I can confirm that. I also have the Pixel 2 xl and have tried so many times, it always failed!

That's why I run stock now..
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] CyberpodS2:
Not to hijack this thread but there are a half dozen roms to choose from if you can't get this one going. Seems silly to just give up...
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] andrewjt19:
Has anyone had Viper4Android work when installing through the ROM Aroma Installer and actually seen it processing the audio? The drivers are installed, but I have not seen it processing the audio at all. Any help would be appreciated. Also is there anyway to use Magisk 15 or higher without breaking anything? There's a few modules I'd like to use but they only work with 15 or 16 Magisk Versions.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] mistermojorizin:
1. Viper works via magisk module for me

2. yes, install v16 as a module in magisk
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] hawgguy:
I noticed that after the March update I had all kinds of problems getting the red-text boot loop.

Seemed to be related to Slot choice for booting.

Became very familiar with the: fastboot --set-active=_x command to resolve.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] cdnsnOw:
For the life of me I cannot get this rom to work always bad frimware
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] liver20:
Thanks for your work... Waiting april update... Thanks

Enviado desde mi Pixel 2 XL mediante Tapatalk
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] mistermojorizin:
Thanks for the quick update. Can't wait to try it out.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] hawgguy:
Thanks for the April update. Seems a little sluggish and I have had the UI crash once. May be just getting settled in, will wait and see.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] mistermojorizin:
Update went fine. No sluggishness here. Here are the steps I did (I was on 1.6).

1. deuces (april, no wipe data)

2. boot from twrp image and flash twrp zip permanently

3. switch to B (reboot menu in TWRP) and reboot to recovery again, make sure still on B

-for some reason it wouldn't boot into recovery on B for me, so I booted from the recovery image, without flashing it, on A, then used the reboot menu to switch it to B, did not reboot yet, but flashed TWRP zip again. Then it finally let me reboot into recovery on B.

4. magisk uninstall zip

-it's ok to get an error here saying that you don't have magisk installed, so it can't uninstall it.

5. rom

6. magisk 14.5

7. switch to A, reboot to recovery (make sure still on A)

8. magisk uninstall zip

-it's ok to get an error here saying that you don't have magisk installed, so it can't uninstall it.

9. rom

6. magisk 14.5

-here I kept getting an error - something about no digest. I just rebooted back into recovery and tried again and it flashed it without a problem.

7. boot system
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] danw_oz:
I had huge number of issues when I was first trying this rom, for me it wasn't until I used the old 3.1.1 twrp image to boot and flash that I was able to get this all to work, was very frustrated because it was the most problem I have every had and for the longest time trying to troubleshoot, don't get me wrong it's not the ROM, but the new google slot design more than anything else. I have been using ROMs from this developer for many years with many Sony phones which is what me persevere getting this working once they released them for this phone.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] egren58:
I'm stock rooted. March update. I'm trying to understand the flashing procedure but I'm so lost... Can someone clarify also what's this deuce method?..
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] danw_oz:
https://xdaforums.com/pixel-2-xl/development/tool-deuces-bootloop-recovery-flashing-t3704761

It ensures that both slots have exactly the same version running
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] hawgguy:
I spoke too soon. Settled in I guess. Fast, smooth & stable for past 24 hours.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] kcteun:
Tried this. Can't boot recovery on slot B no matter what I do. Keep getting corrupted bootloop. I'm beginning to thing there is a hardware issue with my slot B. Is that a thing? Stock works on slot A. I can root and twrp. Nothing works on slot B. I tried fastboot switching slots before deuce flash-all, no good. Says recovery flash to B without error, but just hangs at twrp splash screen.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] mistermojorizin:
I doubt it's hardware. This slot A slot B system is a freaking pain - namely it's hard to keep track of what gets flashed to the slot you're on and what get's flashed to both slots or just the other slot. So I try to flash everything to every slot multiple times and it works eventually usually.

So to get into Slot B, I'd suggest

1. get to the bootloader (fastboot flash bootloader, adb reboot bootloader); I'm assuming you're on slot A

2. fastboot boot TWRP.img (where that image is on your computer and your are just booting TWRP, not flashing yet)

3. Flash TWRP.zip

4. In the TWRP that you're int, hit home, hit reboot, hit Slot B,

[it'll refresh itself and it'll be on B for most purposes, but not for ALL. Specifically, if you flashing UninstallMagisk it would still only affect Slot A. (I hate this BS!)]

5. Flash TWRP.zip again

6. adb reboot bootloader

[so now you should be in bootloader, but on B]

7. fastboot boot TWRP.img (where that image is on your computer and your are just booting TWRP, not the TWRP you flashed)

[hopefully, god willing, it will boot into TWRP on B. Go back to the Reboot menu in TWRP that you're on B]

Sorry, best I can offer. Other than that, just keep trying. Flashing uninstall magisk before starting over.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] ichibanpnoy:
Unable to install any custom kernels after successfully flashing this rom version. Results in red corruption screen and bootloop. Anyone else have this issue?

EDIT: seems to take if you flash magisk 14.5 right after in recovery rather than masgisk 16.0. Updated to magisk 16 after booting via magisk manager.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] mistermojorizin:
1.7 is running really well for me, better than 1.6 in fact. But there is one weird problem I didn't have on 1.6 - After setting trusted face, I can do "improve face matching" while trusted face is still in RAM, but a few minutes later, without even rebooting, "improve face matching" just says "can't start face recognition." Only workaround in to remove trusted face, create a new trusted face and then I'm able to do improve matching for a little while after that.

Has anyone else dealt with this?

was just gonna reply to tell you that. BTW, you can update to 16.3 too.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] mustbevick:
I had quick question if anyone can help me

options to unlink ringtone and notification volume?

if not - what are people doing for this.

Thanks - !
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
They're probably using xposed. However, most rom Devs won't condone the use of that since it can have a adverse affect on the rom. So your kinda on your own if you want to use it.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] doctorew:
Once in rom, can one update to latest magisk?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] mistermojorizin:
Yep, I'm using 16.3. You can't ever flash anything other than 14.5 in recovery, though. But once booted you can install via the manager.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Nirvana Rules:
Great Rom, no issues and at all. I loved your Roms when I had the Xperia Z5 Premium.

When I use album (downloaded from app store) I get app stopped responding. Is there a fix for it?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] auras76:
Sony album not working.its checking for drm.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] SwimDrewid:
Hrmm. twrp hanging on slot b for me:

adb reboot bootloader

fastboot boot twrp

installed twrp via twrp

slot b

reboot recovery (via twrp)

hang

adb reboot bootloader

fastboot getvar current-slot (returns b)

fastboot boot twrp

hang

adb reboot bootloader

fastboot --set-active=_a

fastboot boot twrp

twrp

slot b

installed twrp via twrp

reboot recovery (via twrp)

hang

adb reboot bootloader

fastboot --set-active=_a

fastboot boot twrp

twrp

reboot system

hang

adb reboot bootloader

deuces apr

Any ideas?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] mistermojorizin:
[MENTION=2784777]SwimDrewid[/MENTION]

I'm assuming you're on 1.6 trying to update to 1.7?

Try this (it's bascially what you already tried but with a couple slightly different steps**):

adb reboot bootloader

fastboot --set-active=_a

fastboot boot twrp

*install twrp via twrp*

twrp

slot b

install twrp via twrp

*adb reboot recovery*

Also try to give it a little longer to load.

I think this is what I had to do. But yea, this whole two slot thing is just such a pain and I really don't understand why after we flash recovery on both slots it should fail to boot recovery. I'd really like to have a good explanation of how and why this two slot system behaves this way.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] draymond1987:
I'm bowing my head in defeat. I have tried following the OP's instructions, along with other's suggestions.

I have reflashed the factory images and tried installing on slot A, but I get a "your device is corrupt" message. So I tried the opposite slot, but it just hangs, OR it leds me with the same result, of the ROM not booting at all.

Edit: got it to boot by manually flashing A and B (stock firmware). When I first boot up into the system though, it states there is an internal issue with my device. I ignored it, but don't know if it's a bug?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] draymond1987:
Okay, I lied. I got the ROM to boot, so I was like "let me flash a new kernel." Well, Slot B didn't want to work. So I decided to flash on slot A and then it refused to boot up. I did make a backup beforehand! I tried to restore it, but it kept saying that the device was corrupt and would throw me back into the bootloader. I must have flashed the official FW a few times, flashed the ROM and got the same results.

I just know flashed an AOSP ROM and it booted up without the red warning.

I am so confused with this ROM slot thing, and I don't mean to be a pain in the ass.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] mistermojorizin:
The red device is corrupt message isn't as big a deal as it seems. It just means you couldn't boot one time. It stays there even after you boot successfully. The only way I know to get rid of it is to get it to a point where you can boot successfully on both slots, even if it's the stock image on b, or on both for that matter. Then boot b, message will be gone, boot A where you hopefully have the rom working.

The internal problem message after boot is how it is supposed to be. It means you flashed magisk 14.5 at some point in recovery and I don't know Amy way to get rid of it.

To flash kernel. First get everything working.without kernel. Then go to recovery, flash kernel on a, flash magisk 14.5. BOOT. If that doesn't work, flash magisk uninstall before flashing kernel them flash 14.5.

With backups, it has to be the same kernel, rom and magisk version as what you are trying to recover from, or you can do magisk uninstall, restore backup, magisk 14.5, BOOT, as long as it's the same Rom version.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] draymond1987:
Very interesting, I must say. I have gotten the message to go away by flashing another ROM, or doing a complete "format data" in TWRP, to start over.

Off Topic but, I can't seem to get into Slot B, and I must have flashed the stock firmware a few times. Slot A and B, manually.

I also noticed I can't restore a backup from before. I was on Android P, copied the backup to the PC, then "assumed" that I could just flash that firmware, stick the backup in TWRP's folder, and bam!

OP can delete because I know this isn't related.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] mistermojorizin:
Yea it's all a big pain with these a/b devices. I think it's mostly just the pixel devices that use it, which also makes it hard to flash certain things in recovery that flash fine on other devices.

About backup: you can wipe the device (save the sd card storage first or don't wipe that portion) and get it running on stock P again, with the same magisk that you were using on P, if any, then you do what you planned to: go into TWRP flash the old backup over the working P. Should work.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] draymond1987:
Awesome! I'll definitely give this a shot when I can. It's crazy how we need to be so precise to flash things without everything breaking. Now that I think about it, when I did flash stock, I would boot up and install my info, fastboot TWRP and flash TWRP. I glanced at the TWRP thread, and I believe that will break things.

I'm all for learning new things! :) This is my first Pixel device, and I absolutely love it, regardless of the learning curve.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] mistermojorizin:
I know that rebooting to installed version of TWRP and then flashing a new TWRP will make it so you cannot reboot to anything but TWRP (from personal experience and reading). I thought the correct way to permanently flash TWRP or update TWRP version was to fastboot boot into TWRP than flash TWRP (as opposed to rebooting into the installed copy). I could be wrong.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] piyush7243:
something peculiar. I am on stock. I wiped data. installed romaur and reboot. Comes with stock only. no change than stock. No errors at all. so in short. even if i am flashing Romaur. i am getting stock.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] auras76:
Check if you installed on the same slot when booting.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] piyush7243:
checking that now. with a fresh install
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] draymond1987:
I wanna thank you for your help!! I was about to flash kernel, root and drop my Android P backup into TWRP!

BUT I still cannot get slot B to work! ;/

Like I said before, I flashed 8.1's firmware and Android P's firmware. I just can't boot up into that partition. I know SOME ROMs on 8.1, you need to switch to slot B, for root (i think). I have done the fastboot --set-active=b then fastboot boot, but nothing.

Both slots DID work, and I also did have this issue before. I just can't remember how I fixed it.

Again, if this is off topic, please tell me! I respect everybody on this thread.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] draymond1987:
Just a quick question, and I forget if I asked:

Whenever I boot into this ROM, I always get an error about my device having an internal problem.

It doesn't happen with any other ROMs. Is this a bug?

It's not DURING boot. It's when you're setting the ROM up.

Thanks guys!!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
Probably just the patched dtbo.img warning. Really doesn't affect anything. If you flash Flash kernel, it'll likely go away :good:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] draymond1987:
Can I ask what kernel runs flawlessly on this ROM? I'm sure I am being impatient, but things seem slow during setup.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
It's always good to give the stock kernel a little time settle in. However, your most popular suggestion will likely be Flash kernel. It works beautifully outa the gate :good:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] draymond1987:
The beta or the stable version?

Again, I thank you, and everybody that has been helping me!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
Stable version works very well :good:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Namolas:
Question, step #1 says MAKE A FULL WIPE IF YOU WANT but then step #7 says DO NOT WIPE SYSTEM OR DATA. Just want to make sure I'm doing it right. So which is it? I prefer to wipe if possible...
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
As I understand it, when you do a twrp factory reset, or full wipe, as some call it. That will only wipe data, ART/cache. Wiping "system" on the P2XL can cause well documented problems ?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Namolas:
Thanks Badger. I know wiping system is a no-no nowadays. My question was more regarding the inclusion of DATA (in all caps) in that line. Its all good though, I factory reset before installing and it booted fine.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] auras76:
You can make full wipe only on stock firmware.

Until now I don't find a way to sign property systemui.apk.

If you wipe data with romaur installed systemui it's crashing.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] mistermojorizin:
I'm running Elemental EX. But it generally ran pretty lag free with the included kernel. Only exception was when I tried clearing some dalvik cache. I just restored a backup from before when the cache was cleared. You can search this thread for "cache" and see where the devleoper tlaks about the tweaks he's done with dalvik/art handling.

EDIT: The warning after boot is still there with EX. The comment you quoted said "flash Flash kernel" - so that should tell you the name of the kernel: there is a kernel called "Flash kernel" for the 2xl that you can flash, if you will.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] quinejh:
I decided to come back to RomAur after quite a few months. But I noticed that my viper isn't processing. Any idea why? I'm running on a new system imagebinstall with stock kernal.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] shooterlgk:
How did u install this?, I kept trying last night and kept getting stuck on google logo screen
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] quinejh:
It took a while to boot. But if you are on the April bootloader and complete stock and on slot A it should install. Just give it time to boot.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] shooterlgk:
And just flash on twrp?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] quinejh:
Yes, use twrp and I forgot to mention u have to use the magisk that's posten on the first page
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] shooterlgk:
I can update it afterwards right?.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] quinejh:
Yes
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] auras76:
Try to pause the music and play again.

Should work.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] shooterlgk:
for the life of me i cant get this rom to boot, ive tried flashing back to stock and no luck