Develop Bugs

My oneplus3 seems to be in system encrypt itself, kick me out of system, brick,help!

I live in Taiwan and order my oneplus3 from China, but not from the official seller
Jindong or oneplus site but form 3rd party seller on Taobo, which is in Shenzhen.
Thay have sold hundreds of oneplus3 and have most high praise in Taobo- Shenzhen
My oneplus3 take over 7 days shipping to my hand.
While I 1st unbox my oneplus on 9/6 , it has already bootloader unlock and TWRP 3.2.0 installed. As you know, the 3 party seller sold me the used device, but it's not fake, it has full package and correct IMEI with it, I also cheked IMEI on oneplus official site.
I have no choice but jut to accept a used device with new-one price.
I immediately update to official TWRP 3.2.1 and install freedomOs CB 1.6, XPOSED, rooted, everything looks fine.
But after 4 days uesd, while I change system font with ifont and it won't boot to system, jut stuck at 1+ boot screen, after
a dozen of secnods , automatically boot into TWRP , it even can't boot into TWRP , just hang on TWRP logo,
Fastboot flash other version of TWRP, still can't boot into both system and TWRP.
After fastboot flash stock recovery, it can boot into recovery, and then flash TWRP -> boot in TWRP. But still can't mount system/data/cache, some boots even unable to mount internal storage.
(While on stock recovery, ADB sideload OTA.zip from official site always stuck at 47%)
Fastboot erase usersdata and TWRP format still don't work, no lucky, can't mount system/data/cache.
I ask my colleague hand carry my oneplus3 during his business trip, return it to the 3rd party seller. The 3rd party seller only took 3 days to ship to oneplus to fix it and return to them, and .. return to my colleague.
While my colleague got the phone, it work fine with bootloader lock, Chinese H2 OS for more then one week.=>( So that it's not the hardware issue, not internal SD Corrupt?)
I ask he to test it as he can, after 2weeks. He come to Taiwan and bring it to me. He dose not find any problem with daily use on bootloader locked H2 OS.
When I got the "return" oneplus 3 ,
fastboot unlock booloader->
Decrypt follow this: Decrypt OxygenOS without losing data
i also see this:SOLVED][TWRP]Unable to Decrypt Storage
I think is might be CB rom Unstable and encryption issue.
So I install FreedomOS 1.6 and decrypt data this time.
But guess what happen!?
It have happen again and again more then 5 times -
no flash anything, no reboot, just in system used-> got lag->got black screen-> got reboot->unable to reboot system-> unable to mount/wipe/restore data/system/cache in official TWRP.
The only solution seems to "fastboot format users data" , then I can mount/restore/format data/cache/system , till now, i am confused, I don't know if its software or hardware issue, I just spent too many hours on it!
Please help, any advise is welcome...and.. sorry for my English, tried my best.

This issue is really weird.
Can you share the logs given by TWRP, with the kernel log of your twrp recovery.
To do:
Code:
adb shell
dmesg > /tmp/dmesg.log
exit
adb pull /tmp/recovery.log <path_on_your_computer>
adb pull /tmp/dmesg.log <path_on_your_computer>
All theses things needs to be done directly in twrp, adb is needed.

If you want to boot into system after decrypting it, you have to flash supersu, otherwise OOS will encrypt itself at next boot, causing a brick. Also try the modded version of twrp.

NevaX1 said:
This issue is really weird.
Can you share the logs given by TWRP, with the kernel log of your twrp recovery.
To do:
Code:
adb shell
dmesg > /tmp/dmesg.log
exit
adb pull /tmp/recovery.log <path_on_your_computer>
adb pull /tmp/dmesg.log <path_on_your_computer>
All theses things needs to be done directly in twrp, adb is needed.
Click to expand...
Click to collapse
Dear Sir,
Done it Immediately, thank you!!

ArisLi said:
Dear Sir,
Done it Immediately, thank you!!
Click to expand...
Click to collapse
I can't see any errors here, can you try to capture the log after you get the same error in your twrp.

NevaX1 said:
I can't see any errors here, can you try to capture the log after you get the same error in your twrp.
Click to expand...
Click to collapse
Sure, I believe it will happen during this weekend or on Monday.
aadityarulez said:
If you want to boot into system after decrypting it, you have to flash supersu, otherwise OOS will encrypt itself at next boot, causing a brick. Also try the modded version of twrp.
Click to expand...
Click to collapse
For more information: I didn't try to decrypt data before my oneplus3 return to China, I did decrypt it after it return form China, and I only flash freedom OS 1.6 with systemless SU t and stock (patch) kernel, than flash EX kernel, i believe both of them is patched, disable force decrypting.
My decrypt sequence: Unlock bootloader->fastboot format users data-> flash freedom1.6 with systemlessSU let it boot without configuration ->work fine for 3 days and brick after 4 days used with serval times of booting.(less then 5 times)
Every time before my oneplus3 get this type of in-system-used-brick, I see some root access issue or permission issue, that is V4A driver lost, I have no permission to move my files in media storage( for example, move some files from download folder to XpoasedInstaller folder), or Dolby atom crash....
The latest brick, I used my phone on bed for more than 2 hours with no issue, suddenly Dolby ATOM crash, unable to open it and V4a lost its driver, then I try to boot into TWRP to make a boot/system/data backup, but it fail to mount data and system partition.
Even on system-mode SU, It still happen two times of in system brick.
So now i set SELunx permission and do frequently TWRP and Ti-back, I believe It would brick again few days later. At least after many times of Try/error, I can confirm "format uesers data then I can use TWRP for system/data partition.

NevaX1 said:
I can't see any errors here, can you try to capture the log after you get the same error in your twrp.
Click to expand...
Click to collapse
It happen again while this morning I get up and updating two apps,
It freeze then reboot to recovery, unable to mount system/data again.
I have the latest nandroid data/system/boot backup last night, i believe it finally would be brick again.
Here is the log.
I will keep it in the state, please help, I won't "fastboot format usersdata" this time, till we know the cause, and have your instruction.
EDIT： upload the video, you can see it unable to boot in sysytm, in TWRP can't mount system/data/cache , unable to back/restore/install anything
https://youtu.be/KM4gX16sEHQ

What happened when you went completely stock?

aadityarulez said:
What happened when you went completely stock?
Click to expand...
Click to collapse
My friend test with completely stock/ bootloader lock for more one week in Chian (oneplus
service Centre in Shenzhen recoverey it ), every thing is fine just without google service.
Yesterday,I just re-flash freedom 1.6.1 on cleanest status, fastboot formate userdata-> TWRP format (without this both nandroid or new flas rom won't boot up)-- BOOT
After two days used, every things is fine, but just half hours ago my phone brick with all cache/system/data partition encryption while I am in system uesing , I will report detail at night while I have time, i believe I have found the root cause.

Follow this guide
http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-decryption-ultimate-guide-t3497940

Nexus stuck in boot loop - unrooted - Backing up photos from bootloader or recovery

Hi.
Apologies if this is a very naive question, I am not particularly familiar with mods, roms and so forth.
I have rooted another phone in the past, but that is all.
The situation:
- Samsung Galaxy Nexus
- Not rooted/unlocked. Stock android automatically updated to the latest Android version supported
- Android developer option NOT set in settings
- Stuck in a boot loop: boots to android and then after a few seconds reboots, so no time to do anything
- Not sure how it happened, I had it for years, it was in my pocket and suddenly started doing that.
- Android fastboot and recovery loads up no problem
- I have tried anything I could find online to fix it: deleted cache, rebooted in safe mode, removed battery for 10 hours
- Nothing seems to fix it, it keeps rebooting
- I want to try a factory reset, but my family photos are in the phone
- Google synch seems to have stopped functioning for this device a year ago, all my 2016-17 photos and videos are locked in the phone.
Admitting there is nothing to do about the loop problem:
Is there any way I can copy photos and videos via usb while in recovery mode?
After I will reset the phone via recovery menu, hoping it will fix it. IF that does not fix it, I will flash another rom in. But I really do not want to wipe my data before backing them up.
I am assuming the answer is no, you cannot access the internal memory in fastboot/recovery unless your phone is rooted.
But I would like an expert opinion before I resolve to wipe one year of photos and videos which I will regret losing.

@mcaldo DON'T DO FACTORY RESET, EVERYTHING WILL BE LOST
which recovery are you using..?
if it's TWRP, then it's easy..
- boot into TWRP recovery
- go to "Mount" tab
- find "enable/disable MTP" button at lower options.. (enable it )
then connect your phone to that PC, where you always connected in past, ( to eliminate driver installation stage, all drivers will be preinstalled )
Regards

____Mdd said:
@mcaldo DON'T DO FACTORY RESET, EVERYTHING WILL BE LOST
which recovery are you using..?
if it's TWRP, then it's easy..
- boot into TWRP recovery
- go to "Mount" tab
- find "enable/disable MTP" button at lower options.. (enable it )
then connect your phone to that PC, where you always connected in past, ( to eliminate driver installation stage, all drivers will be preinstalled )
Regards
Click to expand...
Click to collapse
Thanks for your reply!
By recovery, I meant 'android system recovery'
It gives me the following options:
reboot system now
apply update from ADB
apply update from USB drive
wipe data/factory reset
wipe cache partition
Is any of the above useful?
Unfortunately, I do not have any alternative recovery software available
Edit: Googling I found this: "Apply update from ADB: The Android Debug Bridge allows you to plug your device into your PC and issue commands from there. "
If I can issue commands through ADB, perhaps there is a command to copy data from my phone to my computer?

mcaldo said:
Thanks for your reply!
By recovery, I meant 'android system recovery'
It gives me the following options:
reboot system now
apply update from ADB
apply update from USB drive
wipe data/factory reset
wipe cache partition
Is any of the above useful?
Unfortunately, I do not have any alternative recovery software available
Edit: Googling I found this: "Apply update from ADB: The Android Debug Bridge allows you to plug your device into your PC and issue commands from there. "
If I can issue commands through ADB, perhaps there is a command to copy data from my phone to my computer?
Click to expand...
Click to collapse
Yes, you can copy through adb commands..
Get and extract Minimal ADB and Fastboot from here: https://forum.xda-developers.com/showthread.php?t=2317790
From PC, run CMD to extracted folder directory.
Connect phone to PC, go to update from ADB(in recovery),
Type "adb device" , it will show serial number and connected..
Then "adb pull /sdcard " (if you know particular directory of data then write it like /sdcard/photos,, otherwise writing /sdcard will copy all folders from your phone. )
it will start copying to same adb folder ..

____Mdd said:
Yes, you can copy through adb commands..
Get and extract Minimal ADB and Fastboot from here: https://forum.xda-developers.com/showthread.php?t=2317790
From PC, run CMD to extracted folder directory.
Connect phone to PC, go to update from ADB(in recovery),
Type "adb device" , it will show serial number and connected..
Then "adb pull /sdcard " (if you know particular directory of data then write it like /sdcard/photos,, otherwise writing /sdcard will copy all folders from your phone. )
it will start copying to same adb folder ..
Click to expand...
Click to collapse
Thanks for the advice.
I followed the instructions closely, and nearly got there.
adb devices returns
#serialnumber sideload
so all good
but adb pull /sdcard returns
adb: error connect failed: closed
I tried several other commands with no success
kill-server and start-server work fine but do not solve the problem
adb usb returns
error closed
So, I am starting thinking that the problem is in the bootloader being locked.
However, if I unlock it, it will be wipe all my data, I understand?
Googling about it, I found this:
The behavior is status-by-design. Your stock recovery is not designed to grant shell access. Your only choice here is to somehow manage to flash a custom recovery. – Firelord Dec 30 '15 at 14:19
3
To achieve something similar to what @FireLord suggested: TWRP can be booted on many devices without being installed. For that, find a matching image, then boot to the bootloader and run fastboot boot twrp.img. Btw: you can check with fastboot devices resp. adb devices whether a device is visible to the corresponding tool. – Izzy♦ Jul 8 '16 at 19:40
So I understand one could boot TWRP without installing it, but I am not sure if that means I could do that with the bootloader locked?
I found WugFresh nexus root toolkit which seems to do that, among many other things, but again it warns that the phone must be unlocked (using the android build "Android *.* Any", I did not know what else to choose, not sure if that makes any difference as for locked/unlocked requirements)
EDIT: my fastboot screen reads "FASTBOOT STATUS - Failbootloader locked" as the last line, when trying to run TWRP without installing.

Yes, unlocking bootloader will wipe everything..
What actually you did ? Why it went into bootloop ???
I have also read that about boot into TWRP without installing.. and it worked for many one without unlocking bootloader... Don't know why not on GNex.

____Mdd said:
Yes, unlocking bootloader will wipe everything..
What actually you did ? Why it went into bootloop ???
I have also read that about boot into TWRP without installing.. and it worked for many one without unlocking bootloader... Don't know why not on GNex.
Click to expand...
Click to collapse
What actually you did ? Why it went into bootloop ???
Click to expand...
Click to collapse
A very good question, to which I have no answer, unfortunately.
The phone was used by my wife for 2 years and then by me for other 2. I recently changed the battery.
Never rooted or unlocked. No unusual apps installed. I am a very basic user, as you might have guessed, and being my only phone at the moment, I really would not risk experimenting with it.
It went very slow over the last 4 months, so I was planning to reset it.
I put in my coat pocket for a few hours, when I took it out it had a train ticked stuck to the screen and was quite warm and on the lock screen. It froze, so I took the battery out and restarted it. From then on it is stuck in a loop, not sure why really.
I have also read that about boot into TWRP without installing.. and it worked for many one without unlocking bootloader... Don't know why not on GNex
Click to expand...
Click to collapse
That's good to know. I'll research more than.
It seems there might be a problem with the fastboot drivers on my computer, even selecting them from device manager did not work. Win7 refuses to install. The ADB drivers in theory work fine though.

If you have done nothing modification to system, then wiping data should work, but i have doubt if it also wipes personal data too, on TWRP it wipes data excepting /data/media/ which contains all personal data.. but don't know about wiping on stock recovery...
I hope you will find solution as soon as possible..
Regards.
PS. I can install stock recovery and try wiping /data.. and check what things get wiped.. but i need little time for that experiment...

____Mdd said:
If you have done nothing modification to system, then wiping data should work, but i have doubt if it also wipes personal data too, on TWRP it wipes data excepting /data/media/ which contains all personal data.. but don't know about wiping on stock recovery...
I hope you will find solution as soon as possible..
Regards.
PS. I can install stock recovery and try wiping /data.. and check what things get wiped.. but i need little time for that experiment...
Click to expand...
Click to collapse
Thanks so much.
Looking at google's documentation on the nexus:
You can remove data from your Pixel phone or Nexus device by resetting it to factory settings. Resetting to factory settings is also known as formatting the device or doing a "hard reset".
If you're factory resetting your device to fix an issue, make sure that you've tried all other troubleshooting options first. Find out how to troubleshoot your issue.
Important: Performing a factory reset will erase all data from the device.
Click to expand...
Click to collapse
It would seem that indeed all data will be removed.
This point, I will research a bit more into drivers, in case that is what it's preventing adb pull from working.
I really need a working phone, so if that fails I will hard reset, then unlock, root, flash in an alternative bootloader and perhaps a rom, and put ubuntu touch in dual boot. That will hopefully prevent me from loosing data in the future.
Sorry, this is out of topic to my question, but, , could you suggest any stable, solid rom for the nexus?
I read good things of CM12, and I ran into one which seemed to do to quite well with split windows, but I do not remember the name right now.
EDIT: I remember the name of the rom now, it's https://omnirom.org/about/

A last question if you can..
I tried to solve my boot loop problem by sideloading an update from google (maguro yakju yakju-jwr66y-factory-4cadea65.zip)
It loaded it fine but then failed because the installation it says it is not signed.
Basically, being a stock bootloader recovery from Samsung, it will only sideload OTAs from samsung, not the stock ones from google..
I cannot find the samsung ones anywhere, not for the nexus anyway, just the newer devices..
By any chance do you know where I could download proper Samsung OTA zip updates for the nexus?

Well, I talked with an android developer who confirmed that, unless you have a friend working in criminal forensic technology or similar, there is no way to get around a lock on this phone to pull data out.
So, sadly, I have wiped my phone by unlocking it, flashed TWRP and then omnirom with gapps.
My photos are gone, including a bunch of stuff my kid had made and asked me to photograph for safeeping. Very safe indeed
He kept asking me why they make the lock like that, instead of allowing some kind of password, perhaps he has a point.
So, it is quite unlikely that somebody who knows as little as I did will ever read this *before* finding themselves in the same situation.
But if you do, back up your data, unlock and flash TWRP, clockworks or some alternative, and thank yourself if and when disaster strikes..

@mcaldo wiping data/factory reset in STOCK RECOvERY will wipe everything... There is very few chances to get backup...
And yeah i found something interesting..
You can flash system.img.. only system files will be corrected not anything else..
Get appropriate zip from here : https://developers.google.com/android/images
Now take system.img to ADB/Fastboot folder ( i assume you know how it works )
Just go "Fastboot flash system system.img"
It will rewrite system partition..
Another one:
See downloads on this thread..
One says NON-WIPE, if you want me to try that zip, i will again require time for that. See here : https://forum.xda-developers.com/galaxy-nexus/general/guide-restore-to-stock-unbrick-galaxy-t2065470
---------- Post added at 11:12 AM ---------- Previous post was at 11:09 AM ----------
I don't saw your reply, it was on next page.. its sad... Sorry i am late..

Really need help, google flash gone bad

At first I tried to update my existing TWRP (3.2.1-0) to the 3.2.1-2 variant. It flashed ok, but then the phone would only boot to TWRP (reason for upgrade is that 3.2.1-0 would hang). I was attempting initially to put myself on the path to a "custom rom". When this failed, I manually flashed the latest google firmware from their page and it still will not do anything other than fastboot mode. No recovery, no firmware load. When I try to do the flash-all.bat method now, all I get after it loads the archive contents is "error: Cannot generate image for userdata. Guess I got a $1000 brick at this point?? Image from the PC screen included.

See if this thread helps.
https://forum.xda-developers.com/pi...ory-image-flashing-fails-t3715350/post7649698

I am going to have to find another way to look at that thread. My ipad is getting directed to some HTC desire article about and orange and black theme.
I have tried so far very unsuccessfully to wipe everything by booting to twrp via fastboot method. Then I used the dueces script to reflash everything completely (both partitions). No matter whether I flash complete stock or flash magisk and verizon radio files, it just hangs on the white google screen now and that is as far as I have gotten. Left it at home in this mode hoping it will clear.

JoeNeckbone said:
See if this thread helps.
https://forum.xda-developers.com/pi...ory-image-flashing-fails-t3715350/post7649698
Click to expand...
Click to collapse
That link is bad. Three devices are going to an htc desire theming page.

remove the -w from the update line in flash-all.

I have got the same problem since yesterday and search for a solution.

ctradio said:
That link is bad. Three devices are going to an htc desire theming page.
Click to expand...
Click to collapse
Not sure what happened with link, https://forum.xda-developers.com/pi...ry-image-flashing-fails-t3715350/post74751631

new adb dont help for me. I cannot flash slot a and change to b and got the error message that no slot is supported.

Still need help? Have you tried Skipsoft? Sure its not been updated but it might beable to help ..
Where fastboot flashing failed for me one time it got me out of a hole....
Otherwise i can try and remote and help... BTW its not finding the userdata file in the fastboot side... Something isnt right hence why it cant create the userdata file...

I try to boot with skipsoft to temp twrp but stuck on boot.img loading. the flashed twrp stuck on twrp logo and before I have changed from slot b to a inside twrp i can boot. now I cannot flash inside fast boot or delete anything.

Have you guys tried Deuces Bootloop Recovery & Flashing Script? I'd imagine you'd run into the same issues as the script runs a lot of the same fastboot commands...but it has worked wonders for many other users so......
I also might try re-downloading the factory image and comparing the Checksums to make sure you have a whole exact download just in case that's getting in the way of properly generating the userdata image. I'd also suggest making sure you have more than 4GB of space on your C drive; I was getting similar messages about not finding or not generating system images because they couldn't be fully extracted (temporarily) because I didn't have sufficient temp space on my C drive.
But I had encountered this issue before. It was either userdata or system_other partition. I did attempt to fastboot erase and fastboot format those partitions and other tweaks; even messed with changing the size of the partition (you might have better luck). What I seemed to conclude is that I was flashing the wrong month's Full Factory image; i.e. I was manually flashing system_other image from February when the whole phone was still on January. But I believe what I ended up doing was flashing a Full Factory image with the "-w" intact; therefore, if you still have access, you should copybackcup (via TWRP or adb pull) your internal storage (/sdcard and-or /data/media) and simply flash a Full Factory image with wipe option enabled...
Just some thoughts and suggestions...hope this helps...

I figured it out finally. Even though my ADB/Fastboot tools were a later creation date than the ones posted online, the ones online worked great. Even used the dueces script to ensure the junk is gone. Thanks all! Hate pesky gotchas like that!!

Mi Max 3 6/128 SoftBrick - What to Do?

Hello,
I have a Mi Max 3 6GB/128GB which I got from the UK which arrived unlocked and with Global Stable ROM installed which actually updated to V10.3.3.0.PEDMIXM by OTA - I tested.
fastboot getvar anti shows failed, so I assume no Anti Rollback Protection, which I thought a little strange, it being MIUI 10 with (after OTA) June 2019 security patch.
I spent the last couple weeks setting up the phone to my liking (I have 300 apps installed) and finally finished yesterday.
Then I wanted to uninstall some Google/Facebook/Xiaomi bloatware using the excellent "Xiaomi ADB/Fastboot Tools".
I was pretty careful in my opinion to only remove the safe ones (the tool claims to only show you the safe ones) like Music, Video, MiPay, MiCloud, MiForum, MiSIM and all Facebook in the ADB section of the tool.
The I switched in fastboot and thought it would be a good idea to wipe Cache (nothing else).
Upon restart the Mi Max 3 first shows the black boot screen with unlock written at the bottom, then changes to the normal boot boot screen with MIU and the points at the bottom showing that it is busy booting. It stayed there for a while and I thought maybe it was rebuilding the cache and it took that long, but after 30 min still no luck.
Then I fired up the "Xiaomi ADB/Fastboot Tools" on my PC again and it told me the phone was in ADB mode, I could reboot into system mode, where the same thing happened - no progress in booting.
I cannot turn off my phone either, but I can switch from sastem boot (which gets stuck) into fastboot mode via ADB.
Would someone know what's wrong and what I can do to get my phone out of that bootloop while hopefully maintaining all my data and setups, on which I worked for weeks?
Thank you so much for your help!
P.S .: In case it could help: I could read out the phone properties of the Mi Max using the "Xiaomi ADB / Fastboot Tools" while it was softbricked, meaning the ro. init. persist. sys. and dalvik. values of the smartphone. I am happy to post them here, if requested.

Hi,
Do you have an SD card? If so, remove it, because as you cleared the cache, I think it might be a problem with encryption (lost reference).
In your case, I believe a reset will work again, but you will lose application configuration data. Via ADB you can backup files only.
If you do not have unlock bootloader, be very careful as you will not be able to flash TWRP or others.
Good luck!

Thanks, the phone came from the vendor with Global Stable ROM and unlocked. It may be an unofficial unlock, though I was able to install OTAs.
I don't have SDCard.
How can I do ADB backup?
I was able to flash official TWRP just a few minutes but it couldn't access data, maybe because it is encrypted. Now I think I will try and install latest Orange Fox r10 stable, which I think should be able to handle decryption, so that maybe I will be able to get at my date.
Any other advice?

Hi,
Now that you have TWRP, clear cache / dalvik from TWRP and try starting again, maybe start system.
About copy via adb follows a link below:
https://www.lifewire.com/use-minimal-adb-and-fastboot-4582201
in step 2
"
The command to move files from your computer to your phone is adb push.
To move files from your phone to your computer the command is adb pull.
"
Through TWRP you may also be able to back up. Go to (mount partitions) and select all partitions.
Make sure the TWRP MTP option is on, it will allow the device to be mounted via usb on your computer.
I use TWRP I use nijel8, it works very well.
https://forum.xda-developers.com/mi-max-3/development/recovery-twrp-3-2-3-1-nitrogen-t3866084
If you can't launch system, you will have to reinstall the Rom.
Good luck!
PS.
More help for adb.
https://forum.xda-developers.com/android/help/adb-fastboot-commands-bootloader-kernel-t3597181

Thanks for your advice!
I first used the official TWRP and I was able to flash it and start it.
But then the wipe of cache and dalvik failed.
And I could not mount data etc..
When I tried to repair the file system with TWRP I got error 255 - unable to repair data from fsck.f2fs.
Then I saw in your signature that you use nijel8's TWRP and I read that thread, and I started to understand, that my TWRP errors most likely originate from TWRP not being able to decrypt my partitions.
However, towards the end of the thread it seemed that nijel8 stopped working on that project and then Xiaomi once again changed the encryption in MIUI 10/Pie and so it was recommended first to use an obscure Chinese TWRP and then to move on to Orange Fox Recovery Project, which supposedly can handle the decryption better. So that's what I got and I am just about to install it and see if I can rescue or even repair anything.
If you have any other tips for me, I would be very grateful.

You have explored the possibilities well, at the moment I dont have more options regarding current system recovery / backup.
The encryption error resolves you by formatting the user partition by TWRP, in the option to format f2fs plus the installation of a custom Rom or Xiaomi.eu.
Look for tutorials and other reviews before testing these procedures.
Remember that there is a big achance of your ARB model as well.
Good luck.
PS. You can try dirty flash. Find an recovery Rom same version, and flash via TWRP.

"Your device is corrupt. It can't be trusted and may not work properly." Pixel 2 XL

I'm about 4 hours of reading in on this matter, and I still don't have a proper answer. I've run through countless threads with similar titles, and found some helpful tidbits, but nothing the resolves or fully explains what is going on here.
I just made the jump from Android 9.0.0 (latest) rooted to Android 10.0.0 (latest.) Here were my steps:
Download the latest Platform Tools & unzip
Download the latest Android 10.0.0 Factory image for Pixel 2 XL & unzip into the platform tools folder
Download the latest USB drivers & install
Hook up my phone to the computer (Windows 10) and verify that ADB & Fastboot are working properly via command prompt
Execute the flash-all.bat (left the -w flag in so that it wiped my data) -- it appeared to be only flashing the one slot except for a couple mentions of the other slot's system towards the end of the commands
The phone booted just fine and I went through and installed TWRP and Magisk 23 and so on
Here's where I encountered the error:
As I was rebooting out of TWRP, I realized I'd never used the "Slot A" or "Slot B" buttons, so I picked one, and it started rebooting the phone. The normal screen with the yellow text about phone being unlocked came up, then switched to the white background with the 'G' as expected. The expected next step would've been the 'G' spinning into a circle for a second, and then going to the homescreen, but instead what happened was the screen went black, and then a screen that said "Your device is corrupt. It can't be trusted and may not work properly." showed. It looked similar to the one when the phone first boots with the yellow text about the bootloader, but this text was red. I attempted to use the power button to bypass it, and when I did, it switched the the normal yellow-text-about-bootloader screen, and then switched to the 'G' with the white background again, but there it stayed, just frozen.
I was still able to boot to bootloader by using the power + down button, and could then boot to the stock recovery, but that was it. After a bit of reading, I discovered the following command:
fastboot set_active a
or
fastboot set_active b
and also fastboot getvar all
The set_active command chooses which Slot is being used, and the getvar command shows all the fastboot variables, one of which shows the "current_slot." Once I set the other Slot to be the active one and rebooted, the phone booted normally. Buuut, now I'm concerned that someone is screwed up with my phone, and it's going to fail at some point when I don't have my computer handy, so I went back to work trying to resolve the error when I booted out of the one slot.
Here's what I've tried:
Run the flash-all.bat file in one slot, let the phone reboot, boot to bootloader, switch slots, reboot to bootloader, flash-all.bat in the other slot.
Same as above, but without the -w flag.
Manually flash the bootloader, radio and image zip on both slots
Install the TWRP while booted into the adb-loaded TWRP img (this seems to write to both slots based on the output)
Install and uninstall Magisk both via recovery and via the patched stock boot image.
After every single attempt, the one slot would work just fine, and the other slot would exhibit the behavior I mentioned. Depending on which Slot is flashed first, the Slot that fails to boot properly does change (ie. it's not always Slot A or Slot B that fails.)
Untested methods:
Screwing with dm-verity -- I saw one thread that gave a few fastboot commands to disable dm-verity, and a couple people reporting success with it. After searching around and doing a bit of reading on dm-verity, I still don't understand what it does, whether disabling it would have any negative repercussions, and whether disabling it would fix the issue legitimately, or just kinda mute it.
Using Deuce's bootloop recovery tool -- again, I don't really know what that thing is running, it hasn't been maintained in quite some time as far as I can tell, and there are several threads indicating that it runs a bunch of haphazard stuff that could cause more problems. Some reports indicated it worked for them, but I'm concerned about what else it might be doing that may negatively affect things down the road.
Re-locking the bootloader -- I saw this one mentioned several times, but I also saw several people warning that you could brick your phone if you do it wrong. I also saw one or two folks who seemed like they couldn't get back to being unlocked after re-locking. I don't want to screw with this option given those risks.
Can anyone give me any more tips on how to resolve this? I'm pretty sure that the Pixels are supposed to run equally well from both slots, so I'd really like to get the matter resolved so I don't have to worry about what would happen if my phone moved me over to the other Slot for some reason. Any insight and explanations are appreciated!

People say that you cannot install both TWRP and magisk (I haven't tried it myself). So start again with a flash-all, and then, instead of installing TWRP, run it using fastboot boot whenever you need it.

The OP needs to flash a factory image first or the corruption message will never disappear. While he's at it he should make the jump to Android 11...latest radios and all that. If he doesn't want to lose data he can edit flash-all.bat in the factory image and remove the -w flag in that batch file.
From there he can flash anything he wants. If he plans on rooting however he cannot install TWRP, only boot it using ADB. The combination of Magisk and TWRP causes a bootloop.

runekock said:
People say that you cannot install both TWRP and magisk (I haven't tried it myself). So start again with a flash-all, and then, instead of installing TWRP, run it using fastboot boot whenever you need it.
Click to expand...
Click to collapse
The problem presents with even the stock boot image though.

Strephon Alkhalikoi said:
The OP needs to flash a factory image first or the corruption message will never disappear. While he's at it he should make the jump to Android 11...latest radios and all that. If he doesn't want to lose data he can edit flash-all.bat in the factory image and remove the -w flag in that batch file.
From there he can flash anything he wants. If he plans on rooting however he cannot install TWRP, only boot it using ADB. The combination of Magisk and TWRP causes a bootloop.
Click to expand...
Click to collapse
Understood on the magisk / twrp thing, but regarding the factory image, that is exactly what I was going. The problem presents even after doing that. That's why it's so puzzling.
Edit: it's admittedly a very long post, but if you look at the section that's numbered, you'll see I'm grabbing the latest factory image for Android 10 and flashing it. Then in the section labeled "Here's What I've Tried" (aka my attempts to troubleshoot) the very first thing I did was flash the factory image (including the wipe) to both Slots and then trying to boot from one slot and then from the other.

Grab an Android 11 package and don't remove the -w flag when installing. The corruption may be persisting because user storage isn't being wiped.
The factory image - NOT OTA - is the only way to fix this short of sending the device to Google for service.

Strephon Alkhalikoi said:
Grab an Android 11 package and don't remove the -w flag when installing. The corruption may be persisting because user storage isn't being wiped.
The factory image - NOT OTA - is the only way to fix this short of sending the device to Google for service.
Click to expand...
Click to collapse
Why would it be any different when I wipe with Android 10 or Android 11? I flashed the latest Android 10 factory image to the phone *with* the -w flag as mentioned in my "here's what I tried" section. I even went so far as to force the phone to Slot A with the "set_active" command, and then set_active Slot B and flashed the factory image (not the OTA) again. After doing that, the one slot will boot just fine while the other gives the error. If I change it up and flash Slot B first and then Slot A the same thing occurs, just in reverse (the slot that booted before throws the error while the slot that threw the error before now boots.)

My initial post explains why I recommended an Android 11 ROM (updated radio). Any of them will of course work, but that's beside the point. Try using ADB to format the partitions and see if that resolves the issue. Otherwise contact Google, as I can't think of anything else that would be blocking you.

I had this same issue and Flashing Android 11 on both partitions (without removing the -w command) resolved it.
I first booted into Recovery Menu and wiped both slots. Then downloaded the factory image (not ota) and flashed each slot separately wiping the device after each flash in recovery menu. it's the only way to fix this just like user @Strephon Alkhalikoi
If that doesn't resolve it then you have an issue that's more serious and will require a repair of some sort (not necessarily hardware).