yashsingh1/xdaforums huggingface dataset:
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] ax562:
You are going to have to temporary boot into twrp in fastboot mode with "fastboot boot TWRP.img". From there you will not have touchscreen capabilities but you can connect a usb mouse to the usb c port. I'm using an Anker usb c to a adapter to a logitech usb wireless adapter for my wireless mouse. From there you will see the mouse pointer and can use twrp. TWRP was asking me if I was sure I wanted to back up with pin code, so I'm pretty sure there might be a decryption issue so I backed up without any screen lock security(BACKUP EVERYTHING ALWAYS!!!). Once backed up I wiped dalvik/data and installed LOS 19.1 from twrp but had to reboot to LOS recovery to flash gapps (Magisk flashing in twrp and LOS recovery didn't work flashed magisk.apk once in LOS). Once that LOS system was good to go I booted back into twrp (fastboot boot TWRP.img) and backed that system up (I always wype dalvik art cache before backing up, BACKUP EVERYTHING ALWAYS!!!). Once that system was backed up I wiped dalvik art cache/data and restored my original system backup and boom...good to go. After first boot, another restart is required after restores. Hope that makes sense.

P.S. For whatever reason, I'm on a linux/gnu OS and fastboot stopped working for me. Not sure what happened (thinking OS kernel driver bug, will try differenent linux system soon. was haning on "sending boot img") but downloaded platformtools for windows and executed from dir in power shell terminal "./fastboot boot TWRP.img". Anyone seeing this bug in Linux based OS?

Edit: I added "BACKUP EVERYTHING ALWAYS!!!" per @GROOVYJOSHCLARK advice. For me, backing up everything is just a common thought but I get how someone new to this could make a mistake. Repeat BACKUP EVERYTHING ALWAYS!!!. :p
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
NICE! I did not know that part (kernel in recovery embedded in the latest TWRP), but it makes sense
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Nice layout of steps and explanations! This is what XDA is intended for, so I applaud this post! I, however, will wait it out for TWRP to mature but in all reality, I don't use TWRP (like I used to years ago), I ALWAYS had an updated NANDROID, but that's going back 5/6 years ago. I no longer need them, and at this point, I only boot a recovery to install ROM and/or wipe for a new ROM install, so I don't really use recoveries anymore. I also don't bother NANDROID'ng anymore with how often I switch ROMs to test/help others, but it's nice to see this type of post showing others a workaround and how-to do it if you chose to use TWRP and NAROID. I just backup my internal SD to PC (for pics and such) and use Carbonite SMS Backup for TXT/MMS's, and TiB for any apps I want to retain data, but otherwise, I setup fresh when making a new Daily Driver ROM (I.E., by daily ROM is LOS 19.1) so unless I am testing another ROM to help someone, I am on LOS 19.1 (so no need for TWRP anymore).

I LOVE this type of thinking though, you are outside the box thinking and that's EXACTLY the type of users we need here on XDA!!! Well done!! I always urge and encourage users to try new things, or things out of the box, or trying to figure out/fix things by tinkering (smartly) so you don't lose data, and this post was most definitely done that way, so well done, seriously (I am being 100% authentic).

My only comment would be to URGE users to BACKUP everything (as if they were to wipe and start over), just in case of data-loss (so they can recover from any type of disaster). Thats only the thing I would add to it, but otherwise I love this post and thought process!!

For me personally, EVERY TIME I skip a backup, I have an issue. This is even if it's just changing kernels or something very minimal (like applying an update, who knows but it shouldn't break anything), and yet, it always will end in some type of disaster, and I need my backups (I didn't take)! However, WHEN I backup, nothing ever happens. I am the type of engineer to ALWAYS prepare for the worst but hope for the best, and it's saved my butt many times in my career (senior sys architect/engineer).
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] xdadottts:
Thanks ax562.. I shall try

replicating

your steps.

TWRP has its own kernel and

boot.img

file too

FWIW, sideloading the twrp-installer-3.7.0_12-0-coral.zip WORKS, touchscreen and all, but you loose root. It boots into LOS19.1 and then you do the patched Magisk all over again to ROOT.

Installing the TWRP app gets error :

"

Unable to locate recovery

"

(post 711) and interestingly the app keeps continually crashing when selecting the option

"TWRP FLASH".

This was to try installing the twrp.img file from the phone so it would attach to the "recovery" menu..

Shall keep an eye out for updated versions of TWRP

.

Naturally, I shall keep an eye here on updated postings.

I shall update after trying

ax562. steps.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] MJPollard:
I don't think I'm the only one here who really wishes you'd stop changing font colors and styles every other sentence. It makes reading your posts headache-inducing (and the post I quoted is a prime example, because changing the text color to white effectively made half your post invisible). People who are irritated and annoyed will be less likely to want to help you. Food for thought.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] bigbiff:
It looks like only lineage-19.1 isn't working because they compiled all the touchdrivers into the kernel. I am looking at doing that now for coral and flame. It still works fine on stock 12.1.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] ax562:
Yup, tried fastbooting the latest 3.7 just for fun (didn't see much difference in github repo) and still no touch screen capabilities using LOS 19.1. I also forked your's and LOS repo just to start poking around. Let me know if you need anything else @bigbiff and ty for all your works!
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Nice, thanks bigbiff! Let me know if you need testers..
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] bigbiff:
I accidentally overrode the initial version instead of making a -1 release. However the fixed build for fastbooted twrp on lineage-19.1 will be up on twrp.me shortly.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Worked like a charm!
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] xdadottts:
Thanks bigbiff! ax562- your steps does work; &YES, no more font-colors

Question? After fastboot/twrp, the "Mount" screen is asking for a password. I put my PIN/Screen lock password, but get "failed to decrypt user". When I remove the PIN /reboot/renter fastboot twrp, its fine. I put the PIN back on and its a no-go.

Any suggestions?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] ax562:
@bigbiff Yoooooo! You're the real MVP. Works great on lineage 19.1!
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] ax562:
The Pin decrypt does work if you go into twrp without being restored from a backup. From my understanding decrypt isn't working if you flash a back up with a pin. I originally posted about this on my original post to you. I have backed up and restored multiple times without a pin set on backup's and they worked. TWRP was asking me "Are you sure you want to back up with a pin code?" which was a first and odd so I didn't backup with pin. I'm sure bigbiff can clarify.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] legend876:
An how you guys go about downloading this build
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] legend876:
For lineage os 19.1
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] bigbiff:
The problem isn't when you backup, but when you restore with pin enabled. Since new inodes have to be created when new files are created on a newly formatted or clean filesystem, it will break zygote, because zygote will be expecting the inodes to not change. There is no way around this, and why we want you to remove pin before restoring backups.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] ax562:
It's the latest releases for our google coral device. Bigbiff said he named it the same as the previous release, so it's going to be the latest and greatest.

DOWNLOAD:

Please go to https://twrp.me to download the recovery image.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] legend876:
I can confirm it works thanks man plus tried it on Android 13 latest works and everything touch included thanks 🙏👍 developer for your hard work respect my man 👍big up fam 💪
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] legend876:
Guys I got it to work on Android 13 with access to internal storage if you want to know just say although I bet most of you know how to already but still can try help 😁
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] legend876:
1.go to twrp page an download both .img and .zip

2.fastboot boot twrp.img in platform tools

3.go to twrp advance settings and go on adb sideload,after now adb sideload twrp installer.zip

4.reboot to recovery an there bammm you got internal storage access...

Your welcome hope you guys understand what I'm saying still kinda new to this but try something an it works haha now twrp my stock recovery 😁😁an everything's working fine thanks again to the awesome developer......hope it works
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] legend876:
An for those with android 13 😁
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] legend876:
That's the proof if you're guys not sure 😃😊
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Just a heads up, I fastboot boot the TWRP image, I do not install TWRP, I decrypt my /SDCard without an issue, I can (and do) mount my internal SD without any of those needed. I use LOS 19.1 official, with no kernels but also test A13 for others, I had no issues with the latest version on 13 official. Maybe I misunderstood your post.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] legend876:
I did not Install either but wasn't getting the access to my internal storage so I just adb sideload twrp.zip to patch both boot image caz I don't have an otg ATM but I will soon
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] legend876:
It also wasn't show my code at the beginning step of twrp either after I finished with the adb sideload it show after I rebooted into recovery back......
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
All good, I just wanted to point out my testing results landed the same end results without the extra steps/work. I like to do it the easiest/safest way for consistency so that's the only place its coming from but not an attack on the methods used.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] legend876:
Thanks man well appreciated 👍👌💯
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] digitalcircuit:
Heads up: if you have trouble decrypting FBE on an Android 12 ROM, removing your pattern/pin code/etc might work.

I've decided to make the jump from stock 12.1.0 (SQ3A.220705.003.A1, Jul 2022) to LineageOS 19.1 this evening, and I couldn't get twrp-3.7.0_12-0-coral.img to decrypt my user data despite confirming I had the correct pattern. Flashing the installer .zip and booting 3.6.2 didn't work, either.

However, booting into Android 12, removing my pattern in Settings, then booting into TWRP 3.7.0 worked.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Samg381:
Is this project dead? I am unable to decrypt my data on Android 13 using the latest TWRP.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] tlongren:
Afaik it's still active. Did you try removing the lock screen pin and then booting to twrp?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Samg381:
Yes I did. I tried using no password, long-password and a PIN. I am running android 13 on a 4XL with Magisk+Zygisk.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] musp7:
Please...give steps to flash twrp, and how to install a rom without loosing data(internal storage)
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] jtmo7:
I flashed LIneage 20 first. Then rebooted to bootloader. Booted the TWRP image. Then pushed the TWRP image to my phone's storage. Then flashed the image using the Recovery Ramdisk option. Everything works.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] musp7:
Thanks but I wan know....like suppose I'm already using twrp but I wanna switch from LOS to Evox how to do that without loosing my data(music, pics, docs)?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Magnufire2:
Noice! Well played.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Magnufire2:
I didn't look to see if anyone else posted about using magisk manager to flash twrp installer .zip so forgive me if I'm offering week information (last week. Hahah!) so you can use Magisk to flash TWRP and it flashes to both slots. Also, and another apology if this against the rules for asking about a different subject, is Pixel 4XL always on slot B or is slot B the "dominant" slot cause my 4XL is always active on Slot B, however I did soft brick it once switching slots with TWRP.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
No, slot B is not dominant. It's whatever slot is running android boot. It could be A or B, doesn't matter, and it changes when every ROM/android OTA update. What I do is set SLOT A when I'm building my device, then the next OTA will move to B, then A, and so on. You probably soft bricked because SLOT A wasn't updated or had corruption in the system.

I only set the slot on build, then I let the system maintain the boot slot priority or you could soft brick. Let android handle the slot order (boot) and you'll be perfectly fine!
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Magnufire2:
Thanx dude. Much appreciated.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] ponichia:
TWRP 3.7.1 Released​

anyone tried its?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] SanyokFI:
How to install? Where can I find clearly manual?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] febry_valdy:
fastboot boot the img then install to ramdisk to preserve the twrp
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] denzel09:
I am on stock rom with kirisakura kernel. I tried many version of twrp and never maked backup or restore but the data decrypt fails always. Obviously it's a non sense delete the pin especially if you are trying magisk modules and the phone goes in bootloop with pin set. What is the sense to use a modded recovery in this way?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Santarosa 503:
Same here. backed up successfully and finally was able to flash pixeldust that was giving issues to sideload on stock recovery ?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] dave5777:
Do we still have to flash the corresponding boot.img with the ROM?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Santarosa 503:
Yes. Why tho? me too I also backed up successfully and actually flashed pixeldust booted up successfully as well.

---------- Post added at 11:22 PM ---------- Previous post was at 11:05 PM ----------

No we do not. But I guess is worth to mention that you need to switch sloths before restarting cause if you pay attention to the scrip it will tell you that is flashing to the inactive one
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] wgrant:
Does this mean we don't need to patch the boot image for magisk either and can just switch slots, flash and be good?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Santarosa 503:
I will try it Ina a few I haven't root the pixeldust rom yet but I did root the stock room with magisk using the test2 twrp but that wasn't letting me flash costume ROMs yes and I didn't patch it flash it just like that

Yep flashed magisk just fine without switching sloths but you gotta keep in mind that I had already flashed and booted my rom prior to this.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] bigbiff:
I looked closer and realized you had backed up tar files to external but not super. I saw the fd for the super image was not permitted for writing and not the entire storage. I am not entirely sure why this would be the case. I will have to replicate it with an OTG device and figure it out.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Daisymae:
I made a TWRP data backup and then restored it to my device without wiping data on the device. All went well except now face unlock is broken again even with the magisk module fix in place. (Tried Android 11 which breaks face unlock when going back to 10. Magisk module "fix face unlock" circumvents that problem and it was working fine untill I restored the data backup). I wiped the data partition and did a fresh install of AOSiP using adb side load then rooted it and loaded the magisk face unlock module but it's still broken. The TWRP data backup that I restored seems to have altered something that persists even with fresh install and the Magisk module. Not sure what to do now.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] bigbiff:
You can try a format data in TWRP. Sometimes the first one does not work. If the device does not boot after the first format data in TWRP, the second time it does. You can also use stock recovery to format data. I will look into the face unlock issue.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Daisymae:
Thanks for looking into it. I did format data using stock recovery when doing the fresh install of the ROM as well as the side load. But the problem persisted. Wierd.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] bigbiff:
Hmm. A format of userdata should nuke everything. I would try flashing a full stock zip through fastboot.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Daisymae:
Thanks. Will do that in AM.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] wrongway213:
Face Unlock data on this device is stored in the Titan M chip, which thus far we have only been able to wipe via factory reset from within stock recovery.

Explanation: Wiping data with fastboot -w in flash-all script does not wipe/fix Face Unlock, but factory reset via stock recovery does wipe/fix Face Unlock.

All of this is from how we've been operating via fastboot & adb, but unless TWRP can someone access encrypted Titan M chip, I imagine that'll remain the case for Face Unlock.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] bigbiff:
Thanks. That makes sense. When you do a format data in TWRP it will execute the titan m wipe. I am wondering if a factory reset should run it as well.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] wrongway213:
Factory reset does absolutely wipe Titan Mso long as it's run from recovery - there's no other way we've found yet to wipe Titan M, as a matter of fact.. Glad to hear Titan wipe works/will on TWRP. Thanks again for getting this up and running - test3 worked perfectly for decrypting & backing up super & data on my custom kernel, fsociety and latest official AOSiP with no issues at all. :good:
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Daisymae:
Well looks like I'm at a dead end now. I did fresh install of stock 6/4 image to both slots, entered recovery and factory reset wiping Titan M then reinstalled AOSiP then rooted and used Magisk fix for face unlock. Still broken. TWRP restore did something that I can't seem to fix. Do you have any other ideas? Also tried wipe from within TWRP. No luck. (BTW I know you're busy--thanks if you have time to look into this.)
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] bigbiff:
Does it work on the stock install from Google?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Daisymae:
Didn't try that but I will.

---------- Post added at 12:05 PM ---------- Previous post was at 11:43 AM ----------

Not on factory image either. Still broken.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] wrongway213:
My advice would be to try wiping data via stock recovery to see if it indeed has access to Titan M where TWRP does not.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Daisymae:
Oh I did that. Twice. Still broken. I even went back and installed Android 11. Still broken. This TWRP restore seems to have screwed my device. No ones fault except mine. I knew this could happen when I started. I was warned. But if if can't fix this I'll have to return my device. That is if they will exchange it. Help!!
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] bigbiff:
You aren't doing any twrp restores after wiping right?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Daisymae:
No. I'm not.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] bigbiff:
After an attempt at enrolling can you capture logcat for analysis?

So far in attempt to replicate I did the following,

I still have AOSiP installed, enrolled a face. Then I rebooted to recovery and did a data backup, factory reset and data restore.

Rebooted to AOSiP and face unlock was working for me.

I then rebooted into TWRP via fastboot and did a factory reset, rebooted into AOSiP and my original pin was needed, but the setup application was invoked since data was wiped. I was able to enroll and use a face..

OK, I did a format data, rebooted into the ROM and had the white G screen. This is a known issue for me, so I rebooted back into TWRP through fastboot. I couldn't mount data with encryption since all the keys are gone. I then formatted data again, and rebooted into the ROM. This time it executed setup. I was able to assign a pin and enroll a new face.

I then rebooted into TWRP and took a backup of data, then did a factory reset, then restored the data backup. I rebooted into the ROM and was able to enter my pin and after that face unlock was still working for me.

Hopefully logcat will shed some light onto the issue.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Daisymae:
Really appreciate you help. I'll have to reinstall 10 and then will get logcat for you.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] cultofluna:
..

This issue looks similar to 8 pro devices..

After a wipe or try to relock bootloader. .

Persist img getting wiped and fp sensor doesn't work anymore, no matter what you're trying to do for restoring..

Only option to get FP back, is to restore this persist img file..from a previous backup....
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Daisymae:
Captured it but XDA won't let me upload because it exceeds size limit? It's 2.14 MB? I just tried to enroll face unlock then issued: adb logcat > log and that's what I got.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] wrongway213:
Copy & paste to del.dog or pastebin and send the URL to the paste instead of an attachment.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Daisymae:
Hate to be so ignorant but I don't know anything about del.dog or paste bin. Sorry.

ADD: Found pastebin but cant seem to paste the logcat to it. Dummy. I know you don't have time for this. Guess I'll just send it back tomorrow.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] murphyjasonc:
Have you tried doing a factory reset from settings/system/reset options instead of doing it from recovery? When my face unlock was broken this was the only thing that fixed it. A factory reset or wipe from any other method was a no go.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Daisymae:
Thanks. Tried it. No luck.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] FlatOutRU:
Seems like i`ve found an issue. Data backups are being splitted by 1.5gb, while "super" backup is a whole one 9gb piece (in my case).

My external usb stick is formatted in fat32. (stock pixel rom doesn't support exfat/ntfs)