yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] TEFjLONjDON:
Thank you for the newer link it's working.

---------- Post added at 10:16 AM ---------- Previous post was at 09:31 AM ----------

You mentioned you "reflashed" in fastboot.

I believe we must still only "Fastboot boot twrp.......img " then flash TWRP.zip flashable from the fastbooted twrp recovery. Then without rebooting. Press home. Back on the twrp main menu select install (again) and flash Magisk 14.4.2 .... Then reboot to system...

You should now be able to "restart" from inside Android 8.0.(0-1) and hold power and volume down To get to bootloader. Then use volume buttons to select recovery.

Now back inside of "installed" Twrp recovery, Please report if your having issues with keyboard and screen wake-up? And what Android version your on? If you have custom kernals? And if u tried other root methods prior to Magisk?

Twrp will probably still have an issue with wipe due to cache directory now being /data/cache.

Just to be clear I do not have Working TWRP! Yet...

Im on the stock kernel, taimen 8.1 Dev beta, I am rooted with Magisk, I have substratum themes to disable first, and passwords, patterns, and pins to remove before I go further with twrp beta2..

Previously I have fastboot booted the twrp.beta.1.img earlier this week,. But without encryption support,. I did nothing.. I just booted back to system.

[IMG="settings about phone"]https://drive.google.com/file/d/1TTy4wcFINrNI5DCXxg0WHYs68dPCwkwv/view?usp=drivesdk[/IMG]

[IMG="Magisk rooted"]https://drive.google.com/file/d/0B9vb_iMmj8yhcS1QNHF6ZjNydFFwMTY3NUR4Qzg0Sjhia3RN/view?usp=drivesdk[/IMG]
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] ACiDxCHRiST:
TWRP Beta2 working here on 8.0 (November) Stock Kernel. These are the steps I followed.

booted into bootloader

flashed stock 8.0 (november) kernel

fastboot boot twrp.img

TWRP> flashed twrp.zip

TWRP> flashed magisk.zip (v14.4.2)

TWRP> clear dalvik/cache

TWRP> reboot system

I disabled lockscreen security and was on v8.0 (November) Stock Kernel rooted with Magisk before I did the above steps.

Pwr+VolUp from power off state did not work to boot into TWRP. I had to user Pwr+VolDwn to boot into bootloader and then selected Boot Recovery from there. That is not a big deal but this is the first phone I have had that I had to do that. In TWRP, I successfully made a backup of all partitions. I booted back to system and setup lockscreen security and fingerprints. I booted back to TWRP and after entering my password, it decrypted successfully.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] TEFjLONjDON:
Can we mount USB storage with full read/write? (I'm asking because of previous decryption issues).

Let me start off by saying thank you to Des Troy and to all of the devs here, you guys are doing lots of amazing work here thank you guys very much.

I am really​ hoping someone can tell me if from inside of a properly installed TWRPbeta2 recovery they have been able to mount USB (otg) and write/read to USB. Our device came with an adapter for easy transfer that allows any USB stick to be used as OTG..

If I can create a Proper Nandroid backup that I can restore without issue from "fastboot booted twrp" after I pull the "log cats" to the OTG USB if something goes wrong with testing. Then I will continue and test if TWRP beta 2 is working for anyone with my same configuration.

My Config is:

Google Pixel 2 XL Purchased from Google Store (non-Verizon), updated to running Taimen Android-O 8.1 Dev beta, Unlocked bootloader with fastboot unlock and fastboot unlock_critical, Still using stock kernel, Currently rooted with Magisk manager and Magisk 14.4zip.. after patching the stock 8.1 boot.img and flashing with fastboot. Magisk reports rooted.

PS...

This is my daily driver and I use it for work, it's critical we have restore options ASAP. I want to help because, Starting from scratch each time is not a viable option. ( there are so many variables to these new pixel 2's)

My plan is to:

1.) Remove my substratum themes (spectrum),

2.) Remove pin/pattern/passwords

3.) Fastboot boot TWRP_beta_2.img.

4.) Then flash the new TWRP_beta_2.zip then without rebooting flash Magisk_14.4.2_zip,

5.) Reboot back to recovery to test Nandroid backup to (otg) USB

6.) Reboot to system

7.) Pull log cats,

8.) Test in Android for any issues.

9.) Report findings back here.

---------- Post added at 11:31 AM ---------- Previous post was at 11:26 AM ----------

Can you test if otg mounted USB properly allows file transfers.?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Deuces:
If you don't have a backup device to throw your sim in, it's pretty early beta stages to be doing any flashing or modding of a mission critical device.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bryantjopplin:
You will still want to use the apk topjohnwu posted tho
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] ACiDxCHRiST:
I could not get TWRP to mount or even detect USB OTG.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] TEFjLONjDON:
Very true.. I gave my old S5 to my son. I suppose if I had to I could always restore a TWRP backup to that. I have already made it back up his setup an accounts

Thank you for clearing that up. I wasn't sure if I should look for a newer version until your post.

That's precisely what I was afraid of. (OTG takes time) Perhaps if I manage to make a good ABD backup, and I have a day off with time to start fresh I'll continue as planned.

I'm sure by Monday there will be more progress.

Again, I'd like to say thank you to everyone here, and to the countless developers working behind the scene. Most especially Dees_Troy for all the amazing work being done here.

Good luck with all the testing. Now it's off to work for me for my 20 hour work day.

(I wish ADB backups could include hole partitions like Nandroid. I have Titanium Backup pro for apps and data. I can't pay for Carbonite® Online Backup yet. It doesn't restore hole partitions any how.)
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bryantjopplin:
I'll compile a new one later.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] alsip1023:
Can we fastboot boot twrp and then install SuperSU from there for root now?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] abuttino:
No. SuperSu was not built for this phone. Only Magisk

Sent from my Pixel 2 XL
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] murphyjasonc:
Working perfectly for me on 8.1 dp.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Alxoom33:
Thank you! I will try again following your instructions when I get home from work tonight.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bryantjopplin:
To fix the notification just reinstall then magisk that tjw posted. 5.4.1 apk
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] clothednblack:
just tried this, stuck on the G screen loading, even did a clean start, wiped everything, no mods,no substratum, no lockscreen or password or pin. Gets stuck on the G screen everytime.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bryantjopplin:
Which update you on?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] clothednblack:
8.0 Nov
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bryantjopplin:
Hmm you did clean install?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] clothednblack:
yes, did the flash-all method, restored my phone and tried again. I just tried again but left the option of flashing the kernel and it worked. I guess I will stick with the stock kernel for now, that is what was causing the phone to stick on loading.

Edit: upon reboot, I am not rooted. This is very strange
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bryantjopplin:
What kernel are you using????
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] dmarden:
While helping another dev troubleshoot, I factory reset on Android 9 (a couple times). I didn't and don't have any trouble decrypting.

I don't install/flash TWRP (I only boot it).

Bummer, I just wanted to voice that if your thought is a factor... it's not the only one.

Good luck guys.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Battlehero:
You performed the factory reset using TWRP?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] dmarden:
No, sorry for the lack of clarity. From within Android (via Settings). I also did one full clean install via fastboot (i.e. left the wipe flag in place).
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Battlehero:
That is strange, I guess all we can do is wait or just use the workarounds (Disabling the lock-screen security when you want to use TWRP or place the files in /data partition).
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] D-m-x:
Yeah, this is the only way for now. The workaround is okay for the time being but I don't really like the fact that you are unable to do anything if it's bootlooping. As a precaution I'm always removing Lockscreen Security if I'm about to flash some Magisk Module or are going to do some edits.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Reechings:
Yeah I'm in the same boat, did a clean flash of 9 and now can't decrypt with a pin being used. Actually had a systemui bootloop I couldn't recover from without flashing the factory image without the W. I usually disable security before going into TWRP but this one caught me off guard. So is the fix that I should do a clean flash of 8.1 and set it all up then dirty flash 9 or what?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] brendan802:
I dirty flashed 9 too and the decryption bug is present for me. I have password plus finger print and the password contains upper and lower characters. I thought people that didn't dirty flash have had better luck with TWRP decryption???
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] clever_man:
[MENTION=3018620]brendan802[/MENTION], after clean install I have same problem. You must disable pass and then reboot into recovery.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] brendan802:
Yeah I know but thanks though I appreciate it. I wonder what is causing this??? I see people have problems using pins too so it's not only passwords that cause the problem.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
Hey all!

I just wanted to add in my experience if it helps try and narrow down this bug and its issues....

I'm coming from July update with Flash Kernel, TWRP 3.2.1-2, and Magisk 16.4 using a pattern & fingerprint screenlock. Actually, both my phone (XL/taimen) and my gf's phone (non-XL/walleye) is set up in this exact same way and done to both phones; both with complete success.

Basically, I just followed the

great

Az Biker's post/thread guide here.

Here are the key different things I did (some may surprise you):

I

never

disabled my screen lock (pattern & fingerprint)

- I actually just wanted to see if I'd run into issues or not

I never let the OS boot

- After the flash-all (because it automatically boots the system), instead of unlocking, I let it sit pre-unlocked (pattern) and used the adb command to reboot back into bootloader

I used the absolute latest/beta direct from their website/Github (key points: TWRP 3.2.3, Magisk 16.7, Flash 3.0.2 beta)

When rebooting from inside TWRP, when directed to reboot to recovery again, I would instead reboot to bootloader and then to recovery from there

- I doubt this did anything and/or made a difference, but it is something different I did...

In the end, I never had an issue with decryption via pattern on both my XL and my gf's walleye. I know many have had to resort to more stable versions of the programs, but I specifically wanted to load the latest beta just to see if I would run into any issues and/or if it would actually help things more successfully. But I never had any bootloops or infinite loading.

I find this bug very particular and confusing as it seems randomly affecting random devices. I actually went about it pushing the established protocols to see if it would give me any issues, and it has given me none (I know I have to count myself lucky).

In the end, I hope this helps in the "littlest" bit, please feel free to ask any questions on my set up, and hope everyone else is as lucky....

UPDATE

There is one thing I forgot to mention. I am not able to install any Magisk module; something about "mount failed"...so that might be a drawback or I may have not done something completely correctly

I just realized something! Although I went to Magisk's Github page and everything, I didn't actually use the most latest version (1674)! I accidentally used 1671...I wonder if that makes any difference......:confused:

UPDATE #2

Also, it seems that I accidentally used the TWRP image 3.2.2 instead of the newest 3.2.3....it's something; though I doubt it would be much difference specifically in terms of decryption...
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
Hey Simple Man! Good to see you again. You are one lucky dude to have twrp decrypting your data. This thing has no rhyme or reason it seems. However we are grateful for any additional info that may help out with a viable solution. Congrats my friend :laugh:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Az Biker:
First; thanks for the kind words about the guide, but really they go to [MENTION=3730810]Badger50[/MENTION] for figuring out the main process, I just made it user friendly by adding links and whatnot.

Second; since you made it through to where very few have gone, now I'M gonna have to try it, and I just know I'll get stuck along the way and be frustrated that I can't join the few elite users in that highly vaunted place of unencryptionville.... And then I'll have to remove you from my Christmas list. It's serious stuff now! :p
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
Shots fired! ?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] jlokos:
So I came from the same setup as you; I didn't disable pattern or fingerprint. I used Deuce"s Script to "dirty flash" pie. I then re-booted to stock; Power and volume down to bootloader; fastbooted twrp 3.2.3-0 image; flashed twrp installer; re-booted to recovery; flashed 3.0 flash kernel and magisk 1674 and rebooted. I did not have any issues with decryption.

This is such a strange device. I was setting up my old shamu for my son and marveled at how simple it is to flash roms and kernels. Oh for the old days....:)
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
Heh...yeah...I've not been as active, but I've been around here and there...But yea -- good to be back i guess :shrugs: But yea, that's why I waited a full week for as many kinks and established methods to form...but it does seem to have "no rhyme or reason"... But I do feel the "congrats" cuz I do count myself lucky...

LOL...I hear a "challenge accepted" out of this ;):p

But that's essentially the mindset I went in doing this -- I figured I'm gonna have a verrryyy loooong night running into issues and undoing all the crap i'm pushing, but I wanted to try and help and see what issues I might run into so I could post them here. But I really do wanna stay on that Christmas list so.....blame Google and take

THEM

off the list; not me!!!

right...? "Challenge Accepted"...though, from the feedback of so many out there...it might be more "Mission Impossible"....

Oh we...the "lucky ones"...although I might've hesitated and froze when seeing you used Deuce's... I think his script is GREAT and AWESOME for recoveries...but in updating and "dirty flashing", if you look at the script/code, what he does/sets up is to manually flash each and every partition and image! That scares me a bit (although I see the logic and reasoning for recovery purposes) and I (personally) would trust the flash-all script and commands therein (therein the stock .zip that holds the rest of the images and other flashing commands) than a custom one...

But man, after seeing all this from last week, it really is hard to believe that this is all happening and that an established pattern or set up hasn't emerged to make things clearer....:shrugs:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] jlokos:
The A/B partition is way too confusing for me. The script has saved me many times when I thought my phone was gone. However, someone suggested its use for updating and so I've been using it for the monthly updates since that time. It is simple, easy and I've yet to screw anything up!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Alxoom33:
Tried the simple man method, did not work for me. TWRP did no decrypt my data. Did not recognize my pin.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Az Biker:
This will be me... I just know it! Thank God for nands!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
haha Oh dudes! That's what you guys meant!

I

never

intended for my post to be a "guide" or "method". I merely put it up and inputted all that stuff for process of elimination as to what the heck might be "triggering" this bug...

But honestly....I'm thinking it's a good idea to

not

load up the system -- meaning no unlocking in the system -- and booting/rebooting

straight

to the bootloader as well as maybe

not

removing your pin/pattern to begin with -- although it may seem counter-intuitive since that's the safest most advised point given since TWRP 3.2 and March (I could be wrong; i honestly can't remember which month) update debacle ! It seems that a lot of people who "update like usual" (or keyword "update") seem to have no hitches; maybe being on an older TWRP (3.2.2), older android version (8.1) and, although unlikely to affect anything, an older kernel, confirm your pin decrypts in TWRP,

and then

updating over existing settings helps "carry" the decryption "stuff" over to the new TWRP and Pie -- versus removing any/all security and screen locks and only installing TWRP after inputting a screen-lock...

Just my thoughts...but my whole point being -- I doubt my post is any good for a "guide" or "method". If anything, this prevous paragraph ^^ is more my theory than anything...
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
I actually forgot something relevant and updated my original post...

you can see it here:

https://xdaforums.com/showpost.php?p=77335533&postcount=2390
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bigv5150:
Has anyone ran into an issue with being able to set a screen lock after a nandroid backup. Today I booted into twrp but turned off pattern and fingerprint. Nandroid went fine booted back up fine but it would not let me set any lock and if you can't set that up you can't input fingerprint. I had to flash the system again and all was fine. I could set pattern and fingerprint. I'm using latest twrp.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] chopt51:
Does nandroid backup work yet? Say I try to backup, wipe and flash CR 9.0. can do restore the Google image of 9.0? Last time I tried Oreo it was broke
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] jamiejames:
I restored twice yesterday with 3.2.3-0 on 9.0 with no issues. I used the options pre-selected when backing up and restoring.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] josephpalozzi:
I have that exact same problem, but it's after installing magisk through TWRP 3.2.x.

If I install stock factory image, i can set a lock screen. If i try to boot into TWRP it won't recognize the the lock pattern.

If I remove the lock pattern, I can boot into TWRP and install magisk, but I cannot enable a lock after that (pattern, pin, or password). I can go through the motions, but it won't "stick"
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] peterlee928:
i had this exact issue. i had to do a clean install (ie run flash-all.bat file WITH "-w") in order to solve this problem.

google p2xl
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
Are you using magisk 16.7(4) specifically for the P2XL?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Nergal di Cuthah:
can you link to this I haven't before seen that there's a particular magisk for P2XL never mind found it
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
Here ya go. It's actually in the Flash kernel thread if you need it again. https://drive.google.com/file/d/106ZiqeQxNYtCHkOEc6niuHRcWiCzG_eA/view?usp=drivesdk
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] burjuano:
Turn off your phone, then turn it on pressing Power + Vol up + Vol down, all 3 at the same time. Good luck

---------- Post added at 01:35 AM ---------- Previous post was at 01:30 AM ----------

Turn off your phone, then turn it on pressing Power + Vol up + Vol down, all 3 at the same time. Good luck
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] SyCoREAPER:
Mine flashed fine from the beta thread and the lock worked after. Where did that version come from?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] SirVilhelm:
I flashed using the beta channel in the magisk app and it worked
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] mac796:
he's got a brand new version out that fixed that safety-net error working good for me
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] SirVilhelm:
Got a link? Been fighting the incorrect pin error all night
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] mac796:
https://nathanchance.me/downloads/magisk/

Also I'm using the last version of TWRP 3. 2. 2 and I've always had the best luck setting up fingerprint and a pattern.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] azpatterson3:
You ever figure it out? I still can't get safety net to work. Still says invalid. My twrp pin also never works.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] SirVilhelm:
No, might be sticking to stock for a while
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Intelli69:
Why does TWRP always boot to TWRP after I flash the zip once I use fastboot boot /sdcard/TWRP.img ???
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
running the command "fastboot boot ...." is meant to "boot" whatever image is stated after the word "boot" -- which is, considering what you've stated, the TWRP.img. This is the reason you would be booting into TWRP after entering such a command...

probably the most likely reason this all is might be because you aren't supposed to be flashing the TWRP image from your phone...

you are supposed to be running fastboot from your computer from the (usually/"defaultly") platform-tools folder...

and, while we're at installing TWRP and its installation, the .zip is not made for fastboot flashing (as I understand it), but from "flashing" within the TWRP "environment" (so to say)....

So, in the end, if you meant to install TWRP as your custom recovery, you need to install using the .zip file from within the TWRP environment. If you meant to "install" the .zip and accidentally was using fastboot to do it, you shouldn't be "fastboot-ing" from inside your phone to do it (but from a computer and using platform-tools [usually]); and if you meant "fastboot flash boot /sdcard/twrp.img" for some reason, that would mean you had replaced the phone's stock boot image to TWRP image's which, although it's meant as a custom recovery, would merely mean that your phone would be booting into a custom recovery image instead :eek::eek::eek:

Hope this explains some and helps...
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Intelli69:
No no in was intoxicated that night..I know what to do I meant this. 1. I boot into twrp only (w/o flash) then run the flash all scripts for factory IMG, then reboot and sideload the ROM, reboot, flash Magisk, reboot, flash twrp.zip finally, then reboot and instead of going to the home screen like normal, it loads twrp the same WAY AS it DID when I originally booted into twrp ... That is what I meant, and that is my question. Why does it load twrp after I do everything correctly (or so I thought...) I'm on DU ROM fine right now but i would like to somehow flash the twrp.zip correctly so I can flash .zips when I'm away from my laptop. Thank you!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Alxoom33:
I find that if I flash a custom kernel after flashing the Magisk.zip it will boot up to the System UI.