yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] tcables:
If I understand you correctly, there are just nandroid backup issues with most newer ROMs, otherwise flashing roms from TWRP works just fine, and you havent heard of any issues with that yet?

Also, thanks for the Pixel 2 review, that relieves my mind a bit :)
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Correct for the most part, TWRP has known issues with the Pixel 2 devices but flashing .zips works fine, and Nandroids will work on Pie ROMs (possibly 10 ROMs but IDK). I personally haven't gotten 10 Nandroids to work and restore (maybe others have, but I haven't). I am also running in an unencrypted /data model so I am a step ahead of most users. Most users are not even aware this happens and they let Android encrypt /data. If you use a Pie OS (CarbonROM is my dd), and start with Aprils 2019 firmware, then OTA to the required ROM version (last Pie firmware available from Google), then install MAGISK BEFORE it boots the first time, you will remain /data decrypted. This is the only way I am able to Nandroid and restore so keep it in mind.

I dont bother with Nandroids anymore, I simply setup fresh and use TiB to restore any app data I must have that doesnt come from the app's cloud save (which is VERY, few if any left, as most apps self-restore from their own cloud saves so Nandroids are less and less useful).

And hell yeah, I LOVE MY PIXEL 2XL from Google. Its blazing fast and far superior to my Pixel 3 XL (Verizon) mainly because I cannot write my own code and run my own OS for the 3 (locked BL). Outright buying my Pixel 2XL was a great decision, yes it hit the belt initially with a 300$ cost BUT I dont have to pay it off and its MINE and BL unlocked! Once my piece of trash Verizon 3XL is paid off (lease), it will be sold as-is (almost brand new, used 2 hours) then I will probably also sell the Pixel 2XL along with the 3XL and buy whatever is last year's model at the time. It will probably be the Pixel 4XL direct from Google for maybe 400$s, maybe more, maybe less, who knows in a year what's available BUT I will have NO payment plan or lease. I am ONLY buying outright directly from Google from now on, using the last flagship model (as they are faster than ever in history). There is truly NO NEED to EVER buy a flagship in this day and age of technology (its not like it used to be where the latest was SO much MORE powerful), not anymore, they pretty much flatline and the differences are minimal.

This is what I do for a living, senior sys architect so I know IT and how fast things change. Having the latest and greatest phone isnt always the best. Especially if its a newer Verizon piece of junk, verses last year's model of a Google Pixel 2XL. My 2XL BLOWS AWAY the verizon paperweight! Enjoy the 2XL, you WILL love it (assuming its not verizon junk).

I WILL NEVER LEASE FROM VERIZON again, it was a one time mistake that I learned from!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Alxoom33:
Well said!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Thanks
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] arh09:
I am trying to install Magisk via TWRP and it keeps failing. Anyone else have this issue, specifically failure to mount?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Neverfalter2015:
Check root status anyway. The mount failures happen even though the flash was successful.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Prey521:
That's a normal error, it installed fine.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] xunholyx:
I wouldn't call it normal because it isn't. It's not supposed to happen, but it is common.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Prey521:
Well normal since Android 10.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] arh09:
Well im not rooted so idk what the issue is
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] arh09:
This is what I'm getting
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Lughnasadh:
It looks like you're trying to install an ancient version of Magisk (v.14.4?). If that's so, try installing the latest stable, v. 20.4.

https://github.com/topjohnwu/Magisk/releases/tag/v20.4
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] arh09:
thanks for the response, I tried flashing 20.4 and the same thing happened
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Lughnasadh:
I see it also says ChromeOS boot image detected and that boot image was patched by other programs. What rom are you on and what else, if anything, have you installed that would modify the boot image?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] arh09:
I just flashed the April update for the pixel 2xl nothing else, I finally got magisk to stick but was only able to without flashing the twrp zip
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] t-ryder:
So you're on stock ROM on both slots and flashed a patched boot.img and have stock recovery?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] arh09:
Stock ROM both slots, looks like TWRP did stick finally but my root access is odd. I can't add folders or anything like that in root explorer and adaway keeps failing to enable. But magisk is working and says I have root
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Nergal di Cuthah:
Did you install the systemless hosts module for magisk to make adaway work
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] arh09:
No I did not I'll try that
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Nergal di Cuthah:
Yeah do that restart the phone and adaway will work
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] arh09:
It worked man thanks for the help!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Alxoom33:
Why is this thread labeled TWRP 3.2.1 for Pixel 2 XL when the latest TWRP for Taimen is 3.3.0?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
That threw me off in the beginning too when I first got my Pixel 2 XL back in December. I outright bought the Google P2XL in lieu of my Verizon paper weight, P3XL, so I only use my 2XL. When I first started, I was using 3.2.1 unknowing there was a newer version on the website, so I only use the website versions now (unless a dev makes a dev build).
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Reechings:
So is anyone able to do nandroids that restore properly on Android 10 or has that ship sailed for Pixel 2 XL?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] sirxdroid:
Even if you get past the TWRP decryption problem by removing your password and take a backup, I don't think restore works well. At least it did not for me. I tried it late last year, it restored and the phone sort of worked, but I was getting various app crashes and random reboots. I ended up just starting fresh and redoing all apps and it's been very stable since. It's getting harder and harder to be able to do what I could do with the Nexus 4, 5, 6P.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Reechings:
Yeah it's really annoying because I always liked to do a nandroid once in a while and try out some other ROMs but I don't like having to do a fresh setup unless the new room was worth it. It was also nice to have a recent backup kicking around just in case.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Prey521:
Yeah..... That ship has sailed.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Nikos2k:
Perhaps the adb backup could work:

BACKUP

-------------

adb devices

adb backup -apk -shared -all -f <filepath>/backup.ab

Tap on [Back up my data]

RESTORE

--------------

adb devices

adb restore <filepath>/backup.ab

Tap on [Restore my data]
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
If you are on Pie, and you run unencrypted /data, you can nandroid, I do it all the time, but the trick is unencrypted /data (which means you have to first apply April Pie firmware, then OTA to the last Pie ROM), or whatever the Pie dev calls for but it IS possible. I wrote the detailed steps on how to do this near the end of the CarbonROM Pie thread. I havent gotten it to work yet with 10 (LOS) because /data is encrypted, but if you dont mind using Pie, try CarbonROM and I will help you with the steps to remain unencrypted /data if you get stuck (so no PIN removal is required as /data isnt encrypted).

CR (Pie) was my daily driver for months, but I test each and every ROM when released so I use Nandroids (or I just let Google fill in the restores along with using TiB) but usually a Nandroid (unless 10 ROM). I havent been able to Nandroid 10 yet so I am currently trying to figure that out and to see if its possible, but I am running unofficial LOS which means its not signed. This is giving me trouble and IDK if I will ever be able to sort out the /data encryption with the current unofficial LOS, but I am working on it. I just wouldnt hold my breath for any 10 ROM Nandroids, 9/Pie, NP, but not 10, no (at least not yet).
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] srqrob:
Been quiet and elsewhere a while. Are these issues just on P2XL or on other later Pixels also?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
I also have a Pixel 3 XL (but its a verizon piece of trash) so honestly I don't know the answer to your question because its a locked BL, so no TWRP on my 3XL but my best guess, is yes. I would expect that /data would be encrypted mainly because most ROMs are for 10 and beyond, but not 9 for the 3XL. Do NOT hold me to that, its only a guess based on what I am reading, but NOT from real life experience.

My verizon 3XL is on a lease and it will be sold the very moment the lease is paid off. It is sitting on a shelf, in the box, brand new and unused. I HATE verizon so I would NEVER use this piece of junk BUT I had to get on a lease to move providers. This was the only way for the bundle deal my wife and her daughter needed, so I jumped from Sprint. It worked in my favor, because I had (at the time) a terrible LG G7 which I hated worse than the verizon piece of crap, SO I decided to break my lease with Sprint, move to verizon. The move to verizon forced me in to leasing a Pixel 3XL (or the 3 device bundle deal wouldnt work), so I got it. I figured either we would find an exploit to unlock BL, or to be sold the second I outright own it along with my Pixel 2XL (Google version) together. Either way, the 3XL will be sold (unless a BL hack is found). I will sell the verizon garbage 3 XL with my Google 2 XL together and will outright buy a new Pixel 4 XL (or whatever version is available from Google at the time I am ready).

I find, the 2XL out performs my 3XL, HANDS down, yes the 3XL is stock OS, with a locked BL, and my 2XL is running LOS, rooted and yeah, that's probably part of it, but I also think the 2XL was (and still is) a better physical device in my opinion. Others will argue me, but I find the 2XL blows away the 3XL, no questions about it. With the way the devices are currently made, they are so fast and powerful that last year's model is still way more than any user needs in reality with today's apps and software. I am a senior sys engineer / architect, and I develop ROMs and apps on the side so I use my device literally for everything, all day long so having a fast, reliable device is critical to me. I will no issues buying a year old (brand new) Google Flag Ship (whatever is available 4/5/6), who knows. I only buy brand new, so it tends to cost more, but I dont want someone elses junk so I will pay more but ONLY directly FROM Google! NO MORE verizon PIECES OF CRAP!

I know, sorry, I derailed off topic from your question. I just HATE verizon so much for locking BL's that I complain about it as often and loud as I can!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Reechings:
I asked some people with other phones and it sounds like nandroids work fine on 10 for them so that's why I asked.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Really good to know, thanks. I know there are some issues with the dual slots, but those may just be for the pixel line, IDK. I only have pixels now so I cant test anything else (except for my tablets).
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Reechings:
Sorry just want to confirm that even if you go back to April pie build and set up pin and have working decryption in TWRP, then dirty flash Android Q, you will lose working decryption as soon as you factory reset?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Prey521:
Correct
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Reechings:
Ok so no real point if I want to be able to switch between custom Q ROMs. I thought back in Pie and earlier days you could leave your pin set and factory reset in TWRP between flashing ROMs and it would remember your pin when you set up the new rom but maybe I am remembering wrong.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Prey521:
Sorry, I misunderstood you. You CAN factory reset within TWRP and switch between Rom's and still maintain decryption in TWRP. What you CAN'T do is to do a clean wipe using the factory image from Google.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Reechings:
That's great news. So let me know if this sounds ok:

Clean flash April pie factory image to both slots

Boot up and don't bother logging in to Google but set up pin security

Flash May Q factory image to both slots removing -w

Flash TWRP 3.3

Factory reset in TWRP and flash Q ROM and set up.

Reboot to TWRP with working pin decryption?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Piout:
I wasn't aware of this. Was just sent here from another post as THE SOLUTION to be able to decrypt data. Sweet! Thanks a bunch.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Edmontonchef:
April pie or anything before will do the trick
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Reechings:
Went back and did the April flashing expedition and now it is SO much nicer having TWRP being able to decrypt. Now I don't have to lose fingerprints and security every time I want to test an overlay or module. Let alone the one time you forget and get stuck in a bootloop.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Alxoom33:
Thank [MENTION=3293337]buffel0b1ll[/MENTION] for this solution!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bigbiff:
3.4 Test Image for Taimen

Hi all. I have been working on getting Taimen re-worked the last few days based on Dees_Troy's original tree. I have a patch on gerrit and once merged I can make a official download image.

In the meantime please test http://build.twrp.me/test/taimen/twrp-3.4.0-0-test1-taimen.img and let me know if everything is working.

I have tested backup/restore, decryption under keymaster 3 on stock android-10 for taimen and repacking boot.img works into ramdisk.

I am hoping someone can test the multi-user patch too. I will test it tomorrow.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] XeCuTioN:
I was successfully able to decrypt data with the test image with Android 10 and was able to flash Magisk & Custom ROM without issue.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Alxoom33:
I will test on Taimen running RPB1.2.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bigbiff:
Multi-user is working fine. I will be trying to target an official release in the next few days.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] buffal0b1ll:
Nice. Walleye gets same treatment?

Thanks
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Alxoom33:
Bill, nobody cares about Walley, it's all about the Bever!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bigbiff:
I don't have walleye for testing, but it might work if I just use the lineage tree. Please let me know if you are willing to try. Prepare for wiping and all other potential issues if you test anything.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] moonlite:
Testing

Hi. I tested with a clean factory install of taimen-qq3a.200605.001-factory-6829d5ff.zip and then unlocked boot loader.

I booted to bootloader and did fastboot boot C:/Android/twrp-3.4.0-0-test1-taimen.img and it booted into it fine.

I then tried to install a custom rom of Havoc-OS-v3.6-20200617-taimen-Unofficial

When installing I am getting "Could not mount /data and unable to find crypto footer." and also "failed to mount '/data' (invalid argument)

I rebooted but it seems to just get stuck and never boots up. I verified with the stock image that I did not have any PIN or password setup.

Is anyone else running into this?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Reechings:
Those unofficial havoc builds haven't booted since March.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] daedae1112:
I want to try to walleye:)
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bigbiff:
Hello, can you guys test https://build.twrp.me/test/walleye/twrp-3.4.0-0-test1-walleye.img

I pulled down the muskie/walleye tree from lineage, which should have the correct stuff to boot hopefully.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] buffal0b1ll:
Thanks for trying. Hangs on Google animation before TWRP comes up.

Here's my up to date device tree that I use to build ABCrom for walleye maybe it can help https://github.com/buffal0b1ll/abc_device_google_walleye
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bigbiff:
Hi, did you see if adb access was available and see if a reboot after booting TWRP via fastboot creates any logs in /sys/log/fs/pstore?

Also do you have 10 installed? What kernel do you use in your tree?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] buffal0b1ll:
During the hang at Google (before any animation) adb couldn't be accessed, but fastboot reboot bootloader worked to get back to bootloader.

I have Android 10 installed. The kernel I use for the walleye ABCrom is Unicorn Blood, this one https://github.com/ezio84/abc_kernel_google_wahoo + this commit https://github.com/buffal0b1ll/abc_...mmit/2622d225448a520550344a5cbbd42947e0137143
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bigbiff:
That is helpful. It says the ramdisk is too big. I will look into that.

Please test https://build.twrp.me/test/walleye/twrp-3.4.0-0-test2-walleye.img

I have compressed the ramdisk with LZMA.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Alxoom33:
Thank you for your work [MENTION=2638973]bigbiff[/MENTION]! I tested on my Taimen running RPB1.2 rooted with Magisk.

Therefore I booted up the test TWRP 3.4.0.img using fastboot. I did not try to flash the img, since it would be incompatible with Magisk.

The TWRP 3.4.0 recovery decrypted my data without issue, requiring entry of my pin. I was able to flash a custom kernel Aroma zip file, wipe and reboot. I was also able to access the custom wipe menue and the backup menue, although I did not make a nandroid or wipe any further partitions.

When I rebooted back to the Systom, I did not experience any unusual delay or hanging in the G boot image.

I hope this is helpful. Please let me know if there is anything in particular you would like me to test, or if you have any further updates to test. Thank you again for your work!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] daedae1112:
twrp boots!... but it only shows the first twrp logo... It can't go to the pages with 8 buttons.

adb was accessable. so I got a recovery.log and demsg
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bigbiff:
Thanks, it looks like keymaster-3 isn't starting correctly. Can you get the output of logcat over adb too and paste it here?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] daedae1112:
Here.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bigbiff:
Are you running a custom rom or stock android?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] daedae1112:
Stock android 10
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] moonlite:
Yes, I see that now. I am happy to report that using TWRP 3.4.0 test is working and I am able to use other ROMS onto my device. I still get the encryption error, but what I ended up doing to get it to work is:

1. Unlock device

2. Set a PIN on the device to encrypt it

3. Put device in bootloader

4. Booted to TWRP 3.4.0

5. Entered PIN and it decrypted

6. Wiped Dalvik/Art cache, System and Data

7. Pushed over other 3 ROMS I tested with. Those were Bliss-v12.8-taimen-OFFICIAL-20200617, PixelDust-X-aosp-taimen-20200604-1845 and AOSiP-10-Official-taimen-20200625

8. At the end of the install of the custom Rom I chose NOT to load TWRP into it. I don't know if this makes a difference or not

9. Booted up to new custom ROM successfully.

I hope others get good results as well.

Moonlite
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bigbiff:
In android over adb, can you get the results of ps -ef | grep keymaster?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] daedae1112:
you mean this?

walleye:/ $ ps -ef | grep keymaster

system 621 1 0 05:19:50 ? 00:00:00 android.hardware.keymaster@3.0-service-qti

shell 3620 3598 1 10:34:51 pts/1 00:00:00 grep keymaster
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Alxoom33:
This test version working well. Any updates or further testing needed on Taimen? I would be pleased to help.[emoji106]
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Davies_90:
I tried flashing this via the .IMG flasher in twrp.

But unfortunately it didn't take,I was stuck in a bootloop to the twrp splash and no farther.

Being I have no access to a computer shall I just wait for the zip installer?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bigbiff:
Which image did you flash?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bigbiff:
I think taimen is ready for an official build. I am still unsure why walleye keymaster3 is having trouble with configuring since it uses the same wahoo tree as taimen.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Davies_90:
I believe it was the first version you requested we test.

Luckily I had access to a of the other day to reflash the OS but no longer do.

I am however happy to wait for the official version,as all I want is the ability to backup without issues like I could on Android 9.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] sharkie405:
3.4.0.0 install zip was uploaded today: https://dl.twrp.me/taimen/
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] jlokos:
Working great. Thanks bigbiff.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Alxoom33:
Wow! It's finally official. 3.4.0. so far, so good!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] all43:
Thankyou soo much, going to flash later today as this looks like a game changer!:D
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Reechings:
Can I just flash 3.4 zip over existing 3.3 without removing screen lock?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] kvoolk:
To be safe, until you are actually on 3.4 I'd recommend removing security one last time.

Different question: for the taimen nandroid backup and restore, do you just go with the default partitions (boot and data) or should you also include system or anything else?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Davies_90:
Cheers bro,

I'll give it a go. [emoji106]
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Alxoom33:
Since you can't mount Vendor and System, you can't back them up. Just go with the partitions that you need and can mount. i.e., data and perhaps boot/
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] all43:
Backed up system ,boot,data and efs successfully, not tried to restore yet though.

So nice not having to remove security!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] jlokos:
In order to test the new twrp, I did not remove security, and it decrypted fine. I did a backup (of boot and data) and a successful restore (of Bliss).