Database Develop

Decrypt OxygenOS without losing data

Hello there!
Today, after a bit of tinkering around I managed to get my OnePlus 3 in a decrypted state without losing data!
However, this is NOT a method where your data will remain on the phone, it requires you to copy a backup to your PC and then copy everything back + fix permissions. In this guide you'll completely wipe/reset your phone prior to restoring everything.
FAQ:
Q: Why do I need an undecrypted phone?
A: So far (as of today, 06.07.2016) multiboot will not work on encrypted phones. That's probably the only reason why you'll ever want to decrypt your phone.
Q: Will updating the ROM force encryption again?
A: If you're using OxygenOS (or another encryption forcing ROM), yes. However if you flash the Full ROM ZIP and immediately after that SuperSU (DO NOT USE SYSTEMLESS OR IT WILL ENCRYPT AGAIN!!!) WITHOUT REBOOTING it'll not encrypt the device again. (Thanks to @JumboMan)
Q: I've followed your guide but my phone got encrypted again!
A: You've probably used the Systemless SuperSU version which does indeed not prevent your device from being encrypted again. Use the normal version available HERE.
You'll need:
A PC (obviously)
Unlocked OnePlus 3 (will probably work on other OnePlus phones, not tested!)
TWRP Recovery (follow THIS LINK for a guide)
About 50 GB of free space on your PC (depends on how much data you have on the phone)
ADB and Fastboot drivers installed on your PC (to get those connect your OP3 to your PC, as storage choose MTP, open the emulated OnePlus CD-Drive and install those drivers)
(Optional) 15 Seconds ADB Installer
A bit of time, roughly 30 minutes to 1 hour
!!!DISCLAIMER!!!
I'M NOT RESPONSIBLE FOR ANYTHING YOU'RE ABOUT TO DO HERE, THIS GUIDE IS PURELY WRITTEN "OUT OF MY HEAD" AND I CANNOT CONFIRM ANY OF THE FOLLOWING STEPS ANYMORE!!!!
ONLY DO THIS IF YOU KNOW HOW TO RECOVER FROM A HALF-INSTALLED OR COMPLETELY WIPED SYSTEM!!!​
How To:
READ AND ACKNOWLEDGE THE DISCLAIMER ABOVE!
Done? Are you really sure? ... Okay!
If you don't need your data backed up simply start at Step 10 and ignore the restore parts after that.
Still on OxygenOS (or any other ROM) make sure you've enabled ADB in Developer Options and connected + allowed your PC at least one time, else ADB in TWRP will not work.
If you have Titanium Backup, create a backup of all your apps before starting. Just in case, you never know...
Once done boot into TWRP (see above for an installation guide)
Create a normal TWRP backup
Type in "adb devices" to check if you're allowed to use ADB inside TWRP. If it says "unauthorized" refer to Step 1 again.
Once done open up a CMD on your PC and cd to the directory you want all your backup-files to be (or navigate via Windows Explorer to the folder, hold "Shift", right-click and choose "Open command window here...")
Type in "adb pull /data/media" and wait. Depending on the size this can take a few minutes.
After that's done make sure all your files are here and ADB is not reporting any skipped files.
Checked all your files? Okay!
In TWRP choose "Reboot" and "Bootloader". This will put your phone into Fatboot mode.
Type in "fastboot devices" to check if your phone is recognized. If not go into device manager, find the Google Bootloader drivers and install those.
NOW IS YOUR LAST CHANCE TO MAKE SURE EVERYTHING'S BACKED UP AND THERE!
Next type in "fastboot format userdata" and hit enter. This will completely wipe your device.
Boot back into TWRP by using the volume rocker and the Power Button.
ADB is probably not working now (will only report "unauthorized"), MTP however still works. Copy the TWRP folder we backed up earlier onto the device again.
Once copying finished restore the backup and reboot into recovery again. You're now able to use ADB due to the adbpub.key being present again. (You could've done this earlier but it's easier that way.)
Copy the rest back onto the device with "adb push / /data/media". (I'm not really sure if this command is right, beware!)
Now type "adb shell chown -R media_rw:media_rw /data/media" to fix issues later in the ROM.
You're basically finished now! Simply reboot and wait till it boots up again. If you're getting stuck at a "Wrong PIN" or "Wrong Pattern" screen SEE THIS COMMENT I made in another thread.
Finished!
As said, I'm not sure if I forgot something here or not. However I think I got everything covered

Thank you. This was a much needed guide for all of us
Sent from my ONEPLUS A3003 using Tapatalk

Nice

Noob questions: is the decrypted OS faster? Performances of the phone are the same? What about updates (any update will crypt it again?
Thanks for any feedback!
Sent from my OnePlus3 using XDA Labs

IlD4nX said:
Noob questions: is the decrypted OS faster? Performances of the phone are the same? What about updates (any update will crypt it again?
Thanks for any feedback!
Sent from my OnePlus3 using XDA Labs
Click to expand...
Click to collapse
Performance is about the same.
I have no idea if updates will crypt it again, I think not tho? Not sure.

ota updates might encrypt it again if you're on stock. depending if there's a new kernel. the kernel I think forces encryption. so we need a modified boot img to disable forced encryptions. or use a custom kernel that disables force encryption.
If you're on a custom rom based on aosp/cm. most of them doesn't force encryption. so there's no need to worry.
Sent from the moon and back

Thanks for the guide, will this wipe my internal storage?

daavid1995 said:
Thanks for the guide, will this wipe my internal storage?
Click to expand...
Click to collapse
Yes, however the guide shows you how to get a backup of ALL your files before anything gets wiped.
Ajo, und servus aus Österreich

IlD4nX said:
Noob questions: is the decrypted OS faster? Performances of the phone are the same? What about updates (any update will crypt it again?
Thanks for any feedback!
Sent from my OnePlus3 using XDA Labs
Click to expand...
Click to collapse
Yes. updates will encrypt data again.
if you want to remain non encrypted after update then following procedure.
1. download full rom zip (not ota zip)
2.flash full update zip
3.without rebooting after flashing update just flash SuperSU zip. SuperSU will patch your boot img to remain in non encrypted state.
Proof- myself tried it on 3.2.0 update and it works without any problem

JumboMan said:
Yes. updates will encrypt data again.
if you want to remain non encrypted after update then following procedure.
1. download full rom zip (not ota zip)
2.flash full update zip
3.without rebooting after flashing update just flash SuperSU zip. SuperSU will patch your boot img to remain in non encrypted state.
Proof- myself tried it on 3.2.0 update and it works without any problem
Click to expand...
Click to collapse
Added to the OP Thanks for testing!

Thanks, i will try
Dere haha :fingers-crossed::good:
EpicLPer said:
Yes, however the guide shows you how to get a backup of ALL your files before anything gets wiped.
Ajo, und servus aus Österreich
Click to expand...
Click to collapse

maybe stupid questions, but not clear for me:
is there a negative point decrypting the phone or are there any risks?
will decrypting have an effect on the security of the phone?

odooo said:
maybe stupid questions, but not clear for me:
is there a negative point decrypting the phone or are there any risks?
will decrypting have an effect on the security of the phone?
Click to expand...
Click to collapse
As long as you're not an "international searched criminal" where the FBI tries to break into your phone then, no
I'd say it is a bit less secure but who cares, anyone who wants access to your phone somehow gets it anyways, TWRP isn't helping here either since anyone can simply boot into recovery and recover all files from there nonetheless.
Decryption risks are only when you're not good at backing up your data, else there are no risks of doing so.

@EpicLPer:
17. Copy the rest back onto the device with "adb push / /data/media". (I'm not really sure if this command is right, beware!)
Click to expand...
Click to collapse
"adb push / /data/media" doesnt work for me. Can somebody help? I restored the TWRP-Backup and only need to copy the rest on the device.
Edit: I did it in another way, copied all files manually.

Can someons dcrypt this
IzpG+nubzE2m3krvbos0lVDLANkIkiekZt209MYU12Vzny8WNOS7o4JGNoVAm41e/44IYPHmh
0Y7NnLW1JghbWJwbzL1WIpQw7nkzQoH9dEwvTiloTg5BI1u9TYRExzLGQEDUqN2hjq1G5cn
CqDmYoQnMs2bMiuajZweq9ZDC7gLruq6dse0L96gzZFoC/33lF0h1mEh7SBgW3FrcsjhRQ==
Sent from my SM-N910P using XDA-Developers mobile app

Worked, Thanks

How can I check if my device is decrypted or encrypted?

odooo said:
How can I check if my device is decrypted or encrypted?
Click to expand...
Click to collapse
Go to Settings > Device Security and check if it says encrypted or if it gives you the option to encrypt. If second, you know it's decrypted.

Can somebody do some benchmarks? I am really curious whether it makes a difference or not.
from what I've heard it makes a big difference in sequential rw speeds, which are actually pretty important on android.

Will it wipe my rom too?? Or just internal storage??
---------- Post added at 04:03 PM ---------- Previous post was at 03:31 PM ----------
EpicLPer said:
Hello there!
Today, after a bit of tinkering around I managed to get my OnePlus 3 in a decrypted state without losing data!
However, this is NOT a method where your data will remain on the phone, it requires you to copy a backup to your PC and then copy everything back + fix permissions. In this guide you'll completely wipe/reset your phone prior to restoring everything.
FAQ:
Q: Why do I need an undecrypted phone?
A: So far (as of today, 06.07.2016) multiboot will not work on encrypted phones. That's probably the only reason why you'll ever want to decrypt your phone.
Q: Will updating the ROM force encryption again?
A: If you're using OxygenOS (or another encryption forcing ROM), yes. However if you flash the Full ROM ZIP and immediately after that SuperSU WITHOUT REBOOTING it'll not encrypt the device again. (Thanks to @JumboMan)
You'll need:
A PC (obviously)
Unlocked OnePlus 3 (will probably work on other OnePlus phones, not tested!)
TWRP Recovery (follow THIS LINK for a guide)
About 50 GB of free space on your PC (depends on how much data you have on the phone)
ADB and Fastboot drivers installed on your PC (to get those connect your OP3 to your PC, as storage choose MTP, open the emulated OnePlus CD-Drive and install those drivers)
(Optional) 15 Seconds ADB Installer
A bit of time, roughly 30 minutes to 1 hour
!!!DISCLAIMER!!!
I'M NOT RESPONSIBLE FOR ANYTHING YOU'RE ABOUT TO DO HERE, THIS GUIDE IS PURELY WRITTEN "OUT OF MY HEAD" AND I CANNOT CONFIRM ANY OF THE FOLLOWING STEPS ANYMORE!!!!
ONLY DO THIS IF YOU KNOW HOW TO RECOVER FROM A HALF-INSTALLED OR COMPLETELY WIPED SYSTEM!!!
How To:
READ AND ACKNOWLEDGE THE DISCLAIMER ABOVE!
Done? Are you really sure? ... Okay!
If you don't need your data backed up simply start at Step 10 and ignore the restore parts after that.
Still on OxygenOS (or any other ROM) make sure you've enabled ADB in Developer Options and connected + allowed your PC at least one time, else ADB in TWRP will not work.
If you have Titanium Backup, create a backup of all your apps before starting. Just in case, you never know...
Once done boot into TWRP (see above for an installation guide)
Create a normal TWRP backup
Type in "adb devices" to check if you're allowed to use ADB inside TWRP. If it says "unauthorized" refer to Step 1 again.
Once done open up a CMD on your PC and cd to the directory you want all your backup-files to be (or navigate via Windows Explorer to the folder, hold "Shift", right-click and choose "Open command window here...")
Type in "adb pull /data/media" and wait. Depending on the size this can take a few minutes.
After that's done make sure all your files are here and ADB is not reporting any skipped files.
Checked all your files? Okay!
In TWRP choose "Reboot" and "Bootloader". This will put your phone into Fatboot mode.
Type in "fastboot devices" to check if your phone is recognized. If not go into device manager, find the Google Bootloader drivers and install those.
NOW IS YOUR LAST CHANCE TO MAKE SURE EVERYTHING'S BACKED UP AND THERE!
Next type in "fastboot format userdata" and hit enter. This will completely wipe your device.
Boot back into TWRP by using the volume rocker and the Power Button.
ADB is probably not working now (will only report "unauthorized"), MTP however still works. Copy the TWRP folder we backed up earlier onto the device again.
Once copying finished restore the backup and reboot into recovery again. You're now able to use ADB due to the adbpub.key being present again. (You could've done this earlier but it's easier that way.)
Copy the rest back onto the device with "adb push / /data/media". (I'm not really sure if this command is right, beware!)
Now type "adb shell chown -R media_rw:media_rw /data/media" to fix issues later in the ROM.
You're basically finished now! Simply reboot and wait till it boots up again. If you're getting stuck at a "Wrong PIN" or "Wrong Pattern" screen SEE THIS COMMENT I made in another thread.
Finished!
As said, I'm not sure if I forgot something here or not. However I think I got everything covered
Click to expand...
Click to collapse
Will it wipe my rom too?? Or just internal storage??

I might need some assistance. (EVA-L19)

After unlocking the bootloader, installing TWRP recovery and rooting my phone with SuperSU (v2.82), I was preparing to install a custom ROM (more specifically the Resurrection Remix 7.1.2.) all in all, things ended up going out of hand and I accidentally deleted my internal storage, losing every single bit of my existing ROM, not to mention the RR ROM file as well. Now when I try to wipe, I can't, it usually says "Failed to mount '/data' (Device or resource busy) and "Unable to mount storage".
I tried using ADB sideload but to no success, only the same message. What I can understand is that the previous data is gone, I tried changing the format of data, system and cache to FAT & exFAT but it still did not resolve my issue.
I'm out of options here, I don't want to have to give up this phone because of my stupidity.
I also tried flashing the LineageOS 14.1 ROM to see if anything was different, here is what it said:
Installing zip file '/sideload.package.zip'
Target: HUAWEI/EVA-L09/HWEVA:7.0/HUAWEIEVA-L09/C432B361:user/release-keys
detected filesystem ext4 for /dev/block/bootdevice/by-name/system
detected filesystem exfat for /dev/block/bootdevice/by-name/userdata
mount: failed to mount /dev/block/bootdevice/by-name/userdata at /data: Device or resource busy
unmount of /data failed; no such volume
Patching system image unconditionally...
detected filesystem ext4 for /dev/block/bootdevice/by-name/system
Script succeeded: result was [1.000000]
Although it said succeeded it clearly did not work and I am sitting without a ROM. I'm not smart when it comes to these things please help a guy out.
(Is there a way to going back to completely stock EMUI 5.0?)
Cheers.

EMUI 5.01 requires encryption, which you obviously removed.
Search for DC Unlocker, it can probably fix it for 25 Euros

zgfg said:
EMUI 5.01 requires encryption, which you obviously removed.
Search for DC Unlocker, it can probably fix it for 25 Euros
Click to expand...
Click to collapse
I know this is awkward to ask and all, but how exactly do I go about this, I'm pretty lost and I have minimal experience with this stuff..

I never had to use it but here is their portal (with download info, prices, instructions, etc)
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
If you search on XDA or search on Google for eg XDA Huawei DC Unlocker you will find threads with first hands experience (I've seen them several tines but didn't save to Favorites)

zgfg said:
I never had to use it but here is their portal (with download info, prices, instructions, etc)
If you search on XDA or search on Google for eg XDA Huawei DC Unlocker you will find threads with first hands experience (I've seen them several tines but didn't save to Favorites)
Click to expand...
Click to collapse
I'm terribly sorry for being THIS stupid. As I'm looking into this even more, I'm conflicted about the credit amount I need, been scrolling through the list and I can't really find my problem involving firmware I suppose.

People usually buy for 15 Euros. It may help you, Chrome will automatically translate from German
https://www.android-hilfe.de/forum/...-wiederherstellung-mit-dc-phoenix.818669.html

I'm not educated about DC Unlocker but that is NOT neccesary here. You can easily repair the /data partition by flashing the stock recovery via fastboot, formatting data with that stock recovery and then flashing TWRP again. After that TWRP should be able to read the data partition again.
You can easily go back to stock completely and even restore your bootloader by doing a "rollback" to Android 6. (dload method). After that you can normally upgrade from there though EMUI to the latest version of stock.

christopherpfister said:
I'm not educated about DC Unlocker but that is NOT neccesary here. You can easily repair the /data partition by flashing the stock recovery via fastboot, formatting data with that stock recovery and then flashing TWRP again. After that TWRP should be able to read the data partition again.
You can easily go back to stock completely and even restore your bootloader by doing a "rollback" to Android 6. (dload method). After that you can normally upgrade from there though EMUI to the latest version of stock.
Click to expand...
Click to collapse
I've tried using eRecovery to format the data but to no success, I can't even use the touch screen for some reason, (I know about the volume keys, but when it comes to selecting the Wi-Fi, there is no success whatsoever). If you do know a fix for this, could you possibly walk me through this?

Hexagonal said:
I've tried using eRecovery to format the data but to no success, I can't even use the touch screen for some reason, (I know about the volume keys, but when it comes to selecting the Wi-Fi, there is no success whatsoever). If you do know a fix for this, could you possibly walk me through this?
Click to expand...
Click to collapse
UPDATE: I flashed the stock recovery image and it showed me the wipe cache partition and factory data and system reset, I tried both, only the cache one succeeded, the other one failed. I saw a post that directed you to flash boot.img, recovery.img, recovery2.img and then system.img, I did that, but I couldn't boot into my phone - the good thing is however! That I can use my touchscreen in the recovery now.
Obviously the second time booting into EMUI recovery it prompts me to 'Download latest version and recovery', I try to connect to my Wi-Fi, seems okay but then it suddenly fails. More specifically it says 'Getting package info failed'. Save me please :crying:

So this "erecovery" never worked in any way for me (the one which offers you to download the latest version).
Instead you need the normal recovery you already used. Formatting failed for me the first time too, try it again and then it will try to format "low-level" which worked for me.
Go directly into fastboot from that, flash TWRP and go directly into TWRP.
After that should be able to use /data in TWRP. As soon as you are able to start TWRP without any error messages (like "Device busy" or something) go to Wipe and then format data.
Important: check which partition type you have! For EMUI you need "f2fs" and for lineage you need "ext4". You can see and change that in TWRP under Wipe -> "change or repair filesystem".
If you have any more questions, just ask.

christopherpfister said:
So this "erecovery" never worked in any way for me (the one which offers you to download the latest version).
Instead you need the normal recovery you already used. Formatting failed for me the first time too, try it again and then it will try to format "low-level" which worked for me.
Go directly into fastboot from that, flash TWRP and go directly into TWRP.
After that should be able to use /data in TWRP. As soon as you are able to start TWRP without any error messages (like "Device busy" or something) go to Wipe and then format data.
Important: check which partition type you have! For EMUI you need "f2fs" and for lineage you need "ext4". You can see and change that in TWRP under Wipe -> "change or repair filesystem".
If you have any more questions, just ask.
Click to expand...
Click to collapse
So what you're saying is, as soon as I get my data sorted and my partition set to the right one I should be able to install the custom ROM. I could use data and even formatted it, tried installing Lineage but I must've had the storage on the wrong type, now I'm back with the same issue, I'll try to fix it and post my results here. Thank you!

Hexagonal said:
So what you're saying is, as soon as I get my data sorted and my partition set to the right one I should be able to install the custom ROM. I could use data and even formatted it, tried installing Lineage but I must've had the storage on the wrong type, now I'm back with the same issue, I'll try to fix it and post my results here. Thank you!
Click to expand...
Click to collapse
Update: It did NOT work, tried flashing LineageOS through ADB sideload, it was going fine before the bar completely filled up around 50% of the way done, it said 'detected filesystem ext4 for /dev/block/bootdevice/by-name/system' and in the next line it said 'script succeeded: result was [1.000000]'
Help me, I'm begging you, at the moment I don't have an access to a microSD that has the capacity to hold the stock files to do the dload method, therefore this is my only hope.

Hexagonal said:
Update: It did NOT work, tried flashing LineageOS through ADB sideload, it was going fine before the bar completely filled up around 50% of the way done, it said 'detected filesystem ext4 for /dev/block/bootdevice/by-name/system' and in the next line it said 'script succeeded: result was [1.000000]'
Help me, I'm begging you, at the moment I don't have an access to a microSD that has the capacity to hold the stock files to do the dload method, therefore this is my only hope.
Click to expand...
Click to collapse
Whats the error? Why doesn't it work? What happens when you try to boot?

christopherpfister said:
Whats the error? Why doesn't it work? What happens when you try to boot?
Click to expand...
Click to collapse
That's what I'm trying to figure out, when I try to boot in it's just stuck on a boot loop. Unfortunate..

Remember that you have to what *a while* for the first boot. Only if you see no change after 5-8 minutes or so something is definitely wrong.
Have you checked in TWRP if your /data partition is ext4?

christopherpfister said:
Whats the error? Why doesn't it work? What happens when you try to boot?
Click to expand...
Click to collapse
christopherpfister said:
Remember that you have to what *a while* for the first boot. Only if you see no change after 5-8 minutes or so something is definitely wrong.
Have you checked in TWRP if your /data partition is ext4?
Click to expand...
Click to collapse
I know, but it was flashing the Huawei logo and the unlocked bootloader warning continuously. It was set on EXT4 but as I was saying, it said script succeeded at 50%.

Hexagonal said:
'detected filesystem ext4 for /dev/block/bootdevice/by-name/system' and in the next line it said 'script succeeded: result was [1.000000]'
Click to expand...
Click to collapse
That just said that /system partition is ext4. That is default even for stock I believe. You need to check for /data.

christopherpfister said:
That just said that /system partition is ext4. That is default even for stock I believe. You need to check for /data.
Click to expand...
Click to collapse
I deliberately set the data partition to EXT4 before installing

Hexagonal said:
I deliberately set the data partition to EXT4 before installing
Click to expand...
Click to collapse
Can you check in TWRP if it actually says /data is ext4?
Which lineage are you trying to install? Don't you need a vendor.zip for some of them?

/data is indeed on EXT4, and I was installing the one that was on the room section.

(Guide) Get TWRP Working with Data Access on Stock [UPDATED]

Thanks to @seadersn and @SGCMarkus, Markus's new TWRP makes things extremely simple now.
What you need:​SGCMarkus's TWRP
fstab.judypn with forceencrypt set to encryptable.
magisk
and the .magisk file​
Instructions:​
1. Follow the instructions to boot and install TWRP on SGCMarkus's TWRP thread
2. While you're still in TWRP, mount vendor and push the fstab.judypn with:
Code:
adb push path/to/fstab.judypn /vendor/etc
3. Format data via TWRP.
4. Push the .magisk to /data (For dm-verity reasons. It will restore the fstab.judypn with forceencrypt enabled) with:
Code:
adb push path/to/.magisk /data
5. Flash Magisk.
You're done! No bootloops this time. XD

i want to try this at some point. When i did before, the screen was black. Thanks for the guide!

I need to get US pie on my device but will be doing this

i got some issues..
i cant mount system_root and i saw there is no /system_root/system/priv-app folder... so i took modified LGSettings.apk to sd card and i put it to /system/system/priv-app/LGSettings... then i format userdata in fastboot,i got twrp loop.....

dreamss29 said:
i got some issues..
i cant mount system_root and i saw there is no /system_root/system/priv-app folder... so i took modified LGSettings.apk to sd card and i put it to /system/system/priv-app/LGSettings... then i format userdata in fastboot,i got twrp loop.....
Click to expand...
Click to collapse
Flash the magiskpatched boot img included in the files

I just had my bootloader unlocked. I am trying to install TWRP, but if I flash stockpiemagisk.img or TWRP-judypn-2019-07-01.img then use the buttons to choose a factory reset I just get bootloops. I select yes both times, just like normal and it loops until going to a fastboot screen. I can then flash the original magisk_patched.img I got from the guy who unlocked my bl, but no TWRP. Even he wasn't sure why this is happening. Any ideas anyone?
Also, in case its related, I lost download mode and can't get that back even by flashing an original backup of laf_b or the lgup compatible laf. I had download mode and flashed Pie before the bl unlock...
Edit: I got download mode back. Turns out when he was unlocking the bootloader he flashed abl_b incorrectly. Once I flashed it correctly DL mode works... Now for TWRP...
NVM.... found the problem...

I have an issue. After clearing the userdata procedure, this attached images is what I get. It's a reddish boot-up screen. The Active Slot also defaulted to B (as opposed to A). I have a fastboot-loop. I am wondering where I went wrong. I completed a successful procedure on another device hours ago. LGUP does not function as well. The phone defaults to Fastboot.

I am able to get to TWRP but the fastboot-loop has changed. The image attached is what I get. I suppose in my attempt to remedy, the wrong Laf files have been flashed. It's V405UA20a

Hello mister
Actually is it possible to flash this stockpie.img on a V406EBW ?
Regards
Fred

avaie said:
I have an issue. After clearing the userdata procedure, this attached images is what I get. It's a reddish boot-up screen. The Active Slot also defaulted to B (as opposed to A). I have a fastboot-loop. I am wondering where I went wrong. I completed a successful procedure on another device hours ago. LGUP does not function as well. The phone defaults to Fastboot.
Click to expand...
Click to collapse
I have exactly the situation you described (fastboot loop + pink letters screen when I try to get into DL mode). If you've managed to rectify this, can you please give me directions. Thanks.

crubbish said:
I have exactly the situation you described (fastboot loop + pink letters screen when I try to get into DL mode). If you've managed to rectify this, can you please give me directions. Thanks.
Click to expand...
Click to collapse
Hi - I eventually lost root and the system factory-reset after an attempt to boot into TWRP. I have scheduled to have VLAD reflash the entire phone. My bootloader is unlocked though but don't think much can be done. There might be other variables that might be affected.
If there is a guide to using Octoplus, it will be appreciated. It also seems telegram is the new medium for development.

avaie said:
I have scheduled to have VLAD reflash the entire phone. .
Click to expand...
Click to collapse
That's what I plan to do as well. Thanks for responding!

crubbish said:
That's what I plan to do as well. Thanks for responding!
Click to expand...
Click to collapse
All the best.

will try out to follow up this info

When I follow step 3 "Format data via TWRP", at the end of the format it says:
"Updating partition details...
...done
Full SELinux support is present.
WTP Enabled
Formatting Data using mke2fs...
Done.
You may need to reboot recovery to be able to use /
data again.
Updating partition details...
...done
UNABLE TO MOUNT STORAGE, DECRYPTION NEEDED FIRST"
I don't think that's good... Or is it?

Please Clarify/Help
I have managed to get TWRP installed and working but did not notice to do this. I went ahead and used Android already only to find that I need to do this.
I have booted into TWRP but cannot select vendor to mount it. Everything except system and vendor (and USB-OTG because there is not attached) will let me check them. But not vendor.
Do I have to go all the way back and re-install TWRP and to this before I do ANYTHING else? Do I have to do this while I am still in TWRP loaded from the image on my PC?
I realize this will loose all I have done within Android and that is the price I pay for not reading in detail. But I want to make sure this is the last time.
Thanks!

Not What I Expected - Decryption Failed!
I went ahead and re-installed TWRP from fastboot per the Markus thread After rebooting back into TWRP I then followed instructions in the 1st post here.
I could not mount vendor but I saw messages saying it was busy. So I assumed it was not unmounted and went ahead with the push to /vendor/etc. It reported successful from adb. And in TWRP file manager I can see a file named /vendor/etc and in the terminal I can cat its contents which look like what I see on my PC.
I then wiped the /data only using advanced wipe and it used makefs, not format.
I then pushed .magisk to /data and it too reported successful from adb.
I then flashed magisk and that seemed successful as well. Inside to TWRP's file manager, I was able to see the .magisk and various folders under /data. This seemed promising enough.
I finally rebooted to system and got shown what is in the attached screenshot. At that point, I had no option but to agree to the reset. When I touched that button, I was returned to TWRP. So I powered off from TWRP and tried to restart the phone. Once again I get the same decryption unsuccessful.
So I seem to be in a TWRP loop. How to proceed? Thanks

whitedavidp said:
I went ahead and re-installed TWRP from fastboot per the Markus thread After rebooting back into TWRP I then followed instructions in the 1st post here.
I could not mount vendor but I saw messages saying it was busy. So I assumed it was not unmounted and went ahead with the push to /vendor/etc. It reported successful from adb. And in TWRP file manager I can see a file named /vendor/etc and in the terminal I can cat its contents which look like what I see on my PC.
I then wiped the /data only using advanced wipe and it used makefs, not format.
I then pushed .magisk to /data and it too reported successful from adb.
I then flashed magisk and that seemed successful as well. Inside to TWRP's file manager, I was able to see the .magisk and various folders under /data. This seemed promising enough.
I finally rebooted to system and got shown what is in the attached screenshot. At that point, I had no option but to agree to the reset. When I touched that button, I was returned to TWRP. So I powered off from TWRP and tried to restart the phone. Once again I get the same decryption unsuccessful.
So I seem to be in a TWRP loop. How to proceed? Thanks
Click to expand...
Click to collapse
Well, as they say, if at first... I went through the steps here again. I made sure I hit the format button instead of wipe. And I made triple sure that everything was where it seemed to need to be and looked right. When I finally rebooted to system, I am now in Android setup as expected. To see if there is still encryption (ie, TWRP can see and backup /data) remains to be seen. Cheers

whitedavidp said:
Well, as they say, if at first... I went through the steps here again. I made sure I hit the format button instead of wipe. And I made triple sure that everything was where it seemed to need to be and looked right. When I finally rebooted to system, I am now in Android setup as expected. To see if there is still encryption (ie, TWRP can see and backup /data) remains to be seen. Cheers
Click to expand...
Click to collapse
Sadly, once finished with a minimal Android setup I went back into TWRP and /data shows nothing. In backing up, it shows /data as 0 bytes. So I presume this means I am still encrypted. Is there no way out of this hell? Thanks

whitedavidp said:
Sadly, once finished with a minimal Android setup I went back into TWRP and /data shows nothing. In backing up, it shows /data as 0 bytes. So I presume this means I am still encrypted. Is there no way out of this hell? Thanks
Click to expand...
Click to collapse
Here's the thing I would try. Load up LGUP and reload a stock kdz. Make sure that before you begin futzing with the phone, you are booting from Slot A.
Then retrace all the steps carefully. And don't set up anything on the phone until you have reached nirvana (bootloader unlocked, unencrypted, Magisk installed).
You'll get there.
[NG]Owner

[RECOVERY][TWRP 3.3.1][9.0] Galaxy J5 (2017) [26.05.2020]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP 3.3.1-0 by Blue Dogerino​
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
FEATURES:
built from Pie kernel source
built in full 64bit mode
updated TWRP source to 3.3.1 (9.0 version)
Full F2FS Support
fully compatible with all Oreo and Pie roms
WORKING:
Boots
Backup
Restore
All Wipes
Supports unconditional flashing
File manager
Brightness Slider
Flashing
chmod
MTP
Broken:
Nothing for the moment, but if you notice anything please do let me know
Downloads:
Get IMG
Get TAR
Installation:
1. If you have TWRP already:
Boot into TWRP recovery
Select Install, Install IMG
Select TWRP-3.3.1-j5y17lte-26052020.img
Swipe to flash
Restart your phone to recovery and you have new recovery.
Alternative method
Boot into download mode.
Get ODIN
select AP in Odin and select TWRP-3.3.1-j5y17lte-26052020.tar and click start.
To use stock rom, you need to wipe data partition, otherwise the phone will bootloop.
Kernel Source : https://github.com/Doge-Jxy17lte/kernel-exynos7870
XDA:DevDB Information
[RECOVERY][TWRP 3.3.1][9.0] Galaxy J5 (2017) [26.05.2020] , Tool/Utility for the Samsung Galaxy J5
Contributors
bluedogerino, ananjaser1211, corsicanu
Source Code: https://github.com/bluedogerino/twrp-j5y17lte
Version Information
Status: Stable
Current Stable Version: 3.3.1-0
Stable Release Date: 2020-05-26
Created 2020-05-26
Last Updated 2020-05-29

Very good to have an updated version that supposedly takes into account the newer security updates!
Thank you a lot for your efforts!
Any trick needed after downloading from Odin?
RMM-state bypass, no-verity, some cache to wipe?...
Or does it simply need plain Odin download?
I'd like just to know before embarking against Pie security...
Every time I try something, it's popping out a new nightmare...
Some other known problem while then flashing Magisk?
I'm aiming at LOS17.1 and letting Google crap behind me...

Well...
I take the lack of replies as an affirmation that there aren't neither installation problems nor ancillary programs to install.
Let's hope there are no bad surprises, and go on.

:crying:After trying to install this TWRP on Android Pie 9 J530FXXU6CSK9_J530FITV6CSL1_ITV I have to report that it fails.
Install trials report follows.
Installation started on downloading TWRP-3.3.1-j5y17lte-26052020.tar by Odin (Auto-reboot unticked) and then entering into TWRP recovery.
All normal. Having anything to install nor to control, I jumped to reboot session and made a system reboot. That reboot failed into infinite reboot.
I then stopped it and came back to download page from Odin, to control the status of the various flags.
They all were good: Current binary: Custom(0xC), KG State: Checking, FRP LOCK: Off, OEM LOCK: Off, Secure download: enabled, warranty void: 1 (0x0500), AP SW REV: B:6 K:4 S:4.
Restarted and went into TWRP recovery. Mount : Data cannot be mounted, System unmounted (not ticked) and same for cache, EFS, USB OTG. MicroSD mounted (ticked). Tried to mount System (ticked) and rebooted to system. Infinite reboot again.
PWR OFF, then recheck of Odin download page, that remained as before. Reenter in TWRP, check mount: system unticked. Try to format Data (yes), had back the following messages: "Unable to mount '/Data' and unable to find crypto footer Failed to mount '/data' (invalid argument) Unable to recreate /Data/media folder Updating partition details... Failed to mount '/data' (invalid argument)... done. Full SELinux support is present Unable to move to /data/media/TWRP/.twrps. MTP enabled Formatting Data using mk2efs... Done You may need to reboot recovery to be able to reuse /Data again Updating partition details... Done."
PWR OFF, then reboot into TWRP. Now on Mount, Data, Cache, MicroSD are mounted, NOT system. Force system mount.
Reboot to system: infinite loop.
Reboot to Odin screen: same data as before.
Reboot to TWRP: wipe Dalvik, cache, etc...
Force system mount then reboot to system. Infinite loop.
SURRENDER AND REINSTALL PIE FROM ODIN. :crying: :crying:
Edit: After reinstalling Pie from Odin PC file I have discovered that the nasty b...d reverted AGAIN KG STATE TO PRENORMAL. GRRR! I HATE PIE SECURITY!

Alvin50 said:
:crying:After trying to install this TWRP on Android Pie 9 J530FXXU6CSK9_J530FITV6CSL1_ITV I have to report that it fails.
/snip/
Edit: After reinstalling Pie from Odin PC file I have discovered that the nasty b...d reverted AGAIN KG STATE TO PRENORMAL. GRRR! I HATE PIE SECURITY!
Click to expand...
Click to collapse
At last I succeeded in installing this TWRP, but as an upgrade of the former TWRP-3.3.0-j5y17lte-20190417.tar.
I had to before install it with Odin, then followed the procedure indicated at this old post of mine:
https://forum.xda-developers.com/showpost.php?p=80223502&postcount=82
then, from that recovery, installed TWRP-3.3.1-j5y17lte-26052020.img, that I previously loaded into my external SD, selecting to flash recovery.:victory:
I didn't reinstall RMM and no-verity after having them installed with the first TWRP.
At a first sight all appears to be well.:highfive::highfive:
But I stress that it appears to be impossible to directly install it from Odin. I'm presently too stressed to keep up with testing, but it would be interesting re-tarring this image and then re-trying direct install by Odin.:fingers-crossed:

Alvin50 said:
:crying:After trying to install this TWRP on Android Pie 9 J530FXXU6CSK9_J530FITV6CSL1_ITV I have to report that it fails.
Install trials report follows.
Installation started on downloading TWRP-3.3.1-j5y17lte-26052020.tar by Odin (Auto-reboot unticked) and then entering into TWRP recovery.
All normal. Having anything to install nor to control, I jumped to reboot session and made a system reboot. That reboot failed into infinite reboot.
I then stopped it and came back to download page from Odin, to control the status of the various flags.
They all were good: Current binary: Custom(0xC), KG State: Checking, FRP LOCK: Off, OEM LOCK: Off, Secure download: enabled, warranty void: 1 (0x0500), AP SW REV: B:6 K:4 S:4.
Restarted and went into TWRP recovery. Mount : Data cannot be mounted, System unmounted (not ticked) and same for cache, EFS, USB OTG. MicroSD mounted (ticked). Tried to mount System (ticked) and rebooted to system. Infinite reboot again.
PWR OFF, then recheck of Odin download page, that remained as before. Reenter in TWRP, check mount: system unticked. Try to format Data (yes), had back the following messages: "Unable to mount '/Data' and unable to find crypto footer Failed to mount '/data' (invalid argument) Unable to recreate /Data/media folder Updating partition details... Failed to mount '/data' (invalid argument)... done. Full SELinux support is present Unable to move to /data/media/TWRP/.twrps. MTP enabled Formatting Data using mk2efs... Done You may need to reboot recovery to be able to reuse /Data again Updating partition details... Done."
PWR OFF, then reboot into TWRP. Now on Mount, Data, Cache, MicroSD are mounted, NOT system. Force system mount.
Reboot to system: infinite loop.
Reboot to Odin screen: same data as before.
Reboot to TWRP: wipe Dalvik, cache, etc...
Force system mount then reboot to system. Infinite loop.
SURRENDER AND REINSTALL PIE FROM ODIN. :crying: :crying:
Edit: After reinstalling Pie from Odin PC file I have discovered that the nasty b...d reverted AGAIN KG STATE TO PRENORMAL. GRRR! I HATE PIE SECURITY!
Click to expand...
Click to collapse
u need to wipe the data, after installing twrp, as the system is encrypted and twrp doesnt support that.
After wiping the data, the system will boot up fine! :highfive:

bluedogerino said:
u need to wipe the data, after installing twrp, as the system is encrypted and twrp doesnt support that.
After wiping the data, the system will boot up fine! :highfive:
Click to expand...
Click to collapse
I did it in the first trials, and it didn't work, while it worked for the former TWRP version 3.3.0 I then used to update to your 3.3.1. I presently dislike to repeat the trial as it took me a lot of useless time. Maybe I try again in the future.
Anyway thank you for your work again.
Kind regards

Hi,
i installed this recovery image without any problem.
One thing is strange: If i go to reboot and i choose "to system" it wait for a second and before swiping to the right it reboots...
Is that expected?
And the STOCK ROM does not boot, but i think this is related because i did not install Magisk and dm-no-verify, or?
kind regards

jaggedN said:
Hi,
i installed this recovery image without any problem.
One thing is strange: If i go to reboot and i choose "to system" it wait for a second and before swiping to the right it reboots...
Is that expected?
And the STOCK ROM does not boot, but i think this is related because i did not install Magisk and dm-no-verify, or?
kind regards
Click to expand...
Click to collapse
Works fine for me with magisk installed

Hi, noob here.
Is there any way i can just boot and not flash this recovery? I need adb shell once to get some data, but i can't afford to wipe the device..
LE: i have no root, no unlocked bootloader

axross said:
Hi, noob here.
Is there any way i can just boot and not flash this recovery? I need adb shell once to get some data, but i can't afford to wipe the device..
LE: i have no root, no unlocked bootloader
Click to expand...
Click to collapse
What do you mean with "just boot"?
A phone boots up every time it's switched on, if it doesn't boot, it's bricked someway.
Can you please better detail?
Why can't you unlock the bootloader?
Please also tell which model is your phone and with which OS.
Kind regards

Alvin50 said:
What do you mean with "just boot"?
A phone boots up every time it's switched on, if it doesn't boot, it's bricked someway.
Can you please better detail?
Why can't you unlock the bootloader?
Please also tell which model is your phone and with which OS.
Kind regards
Click to expand...
Click to collapse
What I meant to say was if i can use TWRP just once to access adb shell, then somehow revert to stock recovery, because as far as i saw, i cannot flash a custom recovery without unlocking the bootloader and wiping the data, and that's not what i'm aiming for . USB debugging is disabled and i cannot enable it, as the phone is password locked (it belonged to a deceased relative and i tried every possible combination i could think of)
The phone is a Samsung Galaxy j5 2017 duo with android 9.0 (i think)
Sorry for being ambiguous in the previous message and thanks for the reply

axross said:
What I meant to say was if i can use TWRP just once to access adb shell, then somehow revert to stock recovery, because as far as i saw, i cannot flash a custom recovery without unlocking the bootloader and wiping the data, and that's not what i'm aiming for . USB debugging is disabled and i cannot enable it, as the phone is password locked (it belonged to a deceased relative and i tried every possible combination i could think of)
The phone is a Samsung Galaxy j5 2017 duo with android 9.0 (i think)
Sorry for being ambiguous in the previous message and thanks for the reply
Click to expand...
Click to collapse
You can find the exact version of your OS if you go to settings ->"about phone" and look for "Android version". I'm not quite sure of it, because I presently am not on stock ROM and there are possible differences.
You can use ADB shell independently of TWRP, also from the standard custom recovery, But I cannot figure why you would do this way. If you simply want to see the internal storage of your phone, it's enough to have it connected to your PC via USB, then you'll see its internal and SD storage like they were added disks. If, by other hand, you want to install some program, TWRP is the surest and easiest way. Anyway, also to get control of your USB, you have to enable the developer's options, that can also lead to bootloader unlocking. That can be done looking on system to find "build number" and then tapping ten times over it.
I' ll stay waiting for your reply, to better understand
Kind regards

Alvin50 said:
You can find the exact version of your OS if you go to settings ->"about phone" and look for "Android version". I'm not quite sure of it, because I presently am not on stock ROM and there are possible differences.
You can use ADB shell independently of TWRP, also from the standard custom recovery, But I cannot figure why you would do this way. If you simply want to see the internal storage of your phone, it's enough to have it connected to your PC via USB, then you'll see its internal and SD storage like they were added disks. If, by other hand, you want to install some program, TWRP is the surest and easiest way. Anyway, also to get control of your USB, you have to enable the developer's options, that can also lead to bootloader unlocking. That can be done looking on system to find "build number" and then tapping ten times over it.
I' ll stay waiting for your reply, to better understand
Kind regards
Click to expand...
Click to collapse
I mentioned above, the phone is password locked and i don't know the password.
So... No way to activate developer options/usb debugging. It's a challenge i face for some days now
I can't risk flashing TWRP and wiping the data, because i want to recover that data...

axross said:
What I meant to say was if i can use TWRP just once to access adb shell, then somehow revert to stock recovery, because as far as i saw, i cannot flash a custom recovery without unlocking the bootloader and wiping the data, and that's not what i'm aiming for . USB debugging is disabled and i cannot enable it, as the phone is password locked (it belonged to a deceased relative and i tried every possible combination i could think of)
The phone is a Samsung Galaxy j5 2017 duo with android 9.0 (i think)
Sorry for being ambiguous in the previous message and thanks for the reply
Click to expand...
Click to collapse
You can find the exact version of your OS if you go to settings ->"about phone" and look for "Android version". I'm not quite sure of it, because I presently am not on stock ROM and there are possible differences.
You can use ADB shell independently of TWRP, also from the standard custom recovery, But I cannot figure why you would do this way. If you simply want to see the internal storage of your phone, it's enough to have it connected to your PC via USB, then you'll see its internal and SD storage like they were added disks. If, by other hand, you want to install some program, TWRP is the surest and easiest way. Anyway, also to get control of your USB, you have to enable the developer's options, that can also lead to bootloader unlocking. That can be done looking on system to find "build number" and then tapping ten times over it.
I' ll stay waiting for your reply, to better understand
Kind regards
---------- Post added at 02:17 PM ---------- Previous post was at 02:01 PM ----------
axross said:
I mentioned above, the phone is password locked and i don't know the password.
So... No way to activate developer options/usb debugging. It's a challenge i face for some days now
I can't risk flashing TWRP and wiping the data, because i want to recover that data...
Click to expand...
Click to collapse
No, you didn't mention it... That's clearer now.
I faced similar problem some years ago, but my needs were simpler as I only had to unlock a phone I bought,whose old owner made a bad factory reset, forgotting to first delete his Google account. So my need wasn't on saving phone data. I found some help on youtube videos that, installing some apparently harmless software exploited a way to reset this Google account. But It was on Oreo, now Pie is harder to fool. If I well remember it began allowing touch control and then, through it, gaining Internet access, but I cannot imagine a way to overcome the passsword lock. Maybe you are lucky looking on Youtube.
Edit: please look there, maybe you succeed:
https://thedroidguy.com/how-to-unlo...ou-forget-the-pin-pattern-or-password-1092270
Kind regards

Alvin50 said:
You can find the exact version of your OS if you go to settings ->"about phone" and look for "Android version". I'm not quite sure of it, because I presently am not on stock ROM and there are possible differences.
You can use ADB shell independently of TWRP, also from the standard custom recovery, But I cannot figure why you would do this way. If you simply want to see the internal storage of your phone, it's enough to have it connected to your PC via USB, then you'll see its internal and SD storage like they were added disks. If, by other hand, you want to install some program, TWRP is the surest and easiest way. Anyway, also to get control of your USB, you have to enable the developer's options, that can also lead to bootloader unlocking. That can be done looking on system to find "build number" and then tapping ten times over it.
I' ll stay waiting for your reply, to better understand
Kind regards
---------- Post added at 02:17 PM ---------- Previous post was at 02:01 PM ----------
No, you didn't mention it... That's clearer now.
I faced similar problem some years ago, but my needs were simpler as I only had to unlock a phone I bought,whose old owner made a bad factory reset, forgotting to first delete his Google account. So my need wasn't on saving phone data. I found some help on youtube videos that, installing some apparently harmless software exploited a way to reset this Google account. But It was on Oreo, now Pie is harder to fool. If I well remember it began allowing touch control and then, through it, gaining Internet access, but I cannot imagine a way to overcome the passsword lock. Maybe you are lucky looking on Youtube.
Edit: please look there, maybe you succeed:
https://thedroidguy.com/how-to-unlo...ou-forget-the-pin-pattern-or-password-1092270
Kind regards
Click to expand...
Click to collapse
Thanks for the idea, but Android device manager and Samsung find my device were not previously configured for the phone

HELP!!!
Guys my phones stuck in bootloop , after trying to root it .
IT's running on pie ((SM-J530F/DS)
What do i do?
Should i install a stock rom?
And it wont even go into recovery mode!!!
Ps: I still wanna root it
:crying::crying:

Malong24 said:
Guys my phones stuck in bootloop , after trying to root it .
IT's running on pie ((SM-J530F/DS)
What do i do?
Should i install a stock rom?
And it wont even go into recovery mode!!!
Ps: I still wanna root it
:crying::crying:
Click to expand...
Click to collapse
Please detail better...
1) Have you yet installed TWRP? Which version?
2) Can you go to Odin download screen and report the status messages in the first rows of that page?
3) How did you try to have root?
My first suggestion is that you revert to your stock ROM by Odin, and regain your phone control.
Then restart the rooting process, caring of details: "The Devil hiddens himself into details"...
Kind regards

Malong24 said:
Guys my phones stuck in bootloop , after trying to root it .
IT's running on pie ((SM-J530F/DS)
What do i do?
Should i install a stock rom?
And it wont even go into recovery mode!!!
Ps: I still wanna root it
:crying::crying:
Click to expand...
Click to collapse
You should reflash stock using odin, install TWRP again, format data, install a new ROM and root that using magisk.

Hey, I hope this thread is not dead, but I can't get out of the bootloop after flashing TWRP. I install it normally with Odin (as AP), then I immediatly enter recovery and it seems fine. When I try to wipe Data it gives me errors, that i can't wipe, the only option is to format data. After this i can wipe Data, but when rebooting it's stuck in a bootloop. I can still access TWRP and Download mode though. I'm running stock Android Pie, but I'm going to try it with stock 8.1 too.
Spoiler: Error
Code:
Could not mount /data and unable to find crypto footer.
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder.
Updating partition details...
Failed to mount '/data' (Invalid argument)
...done
Unable to mount storage.
Failed to mount '/data' (Invalid argument)
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
MTP Enabled
Failed to mount 'data' (Invalid argument)
unable to wipe /data.
Updating partition details...
Failed to mount '/data' (Invalid argument)
...done
Unable to mount storage
EDIT: Well I guess I 'fixed' it on my own. I tried what happens if I try to root it with the magisk.zip et voilá it booted just fine

Advanced advice for internal storage recovery after attempted flash to LineageOS 17

Hi everyone. Got a puzzle for you forensic data recovery guys out there. I am a fool having a bad day today. For the first time in 10 years of screwing with Android, I backed up my ROM with twrp and also backed up my sms and calls, but then managed to somehow forget to copy those files off the internal storage before trying to flash my phone to LineageOS and botching the internal storage. Here is what happened.
0) Before state: Rooted (I think) and for sure running OxygenOS 5.0.3, flashed via TWRP. TWRP version 3.2.1-0. 128 GB OnePlus 3T
1) Backed up System, data, etc to backup on internal storage via TWRP. Booted into OS and backed up SMS and calls to .xml file.
2) Wiped data, system, cache and dalvik/art cache.
3) Downloaded LineageOS w/ microG via zip in TWRP and attempted to install. Received error that I needed to update the modem to at least 9.0.3.
4) Mounted storage from TWRP and copied in Stable9.0.3+Firmware+Modem_OnePlus+3T.zip. Ran the install and was successful.
5) Installed lineage-17.1-20200826-microG-oneplus3.zip via TWRP. Left prompt to install TWRP checked and booted into OS.
6) Upon boot, saw the message: "Decryption unsuccessful" The password that you entered is correct but unfortunately your data is corrupt.
7) Rebooted back into TWRP to mount storage. Could not get anything to mount because it would not accept my decrypt passcode.
8) Figured TWRP bug, flashed twrp-3.4.0-0-oneplus3.img via fastboot. Could decrypt now with passcode but all storage read 0MB
9) Flashed modem back to OnePlus3T_5.0.3-25-05-18-FIRMWARE-flashable.zip via adb sideload method which is what I assume I was running before since that was the OS version. Rebooted
10) Booted back into TWRP, discovered I still couldn't see files. Downgraded TWRP back to 3.2.1-0 via fastboot.
11) Unable to decrypt from TWRP or even install zips. No change at any point in the OS. Flashed TWRP back to 3.4.0.0.
12) Ran adb shell twrp decrypt XXXXXX (where XXXXXX is my pin) which gave me this message:
Attempting to decrypt data partition or user data via command line.
(then it returned to shell so I assume it worked)
13) Ran an ADB pull command (adb pull /dev/block/dm-0 backup.img). There is obviously something there because it downloaded 111 GB worth of .img file (which I'm 99% certain was the amount of space I had used on the phone). Tried to open the .img file with multiple EXT4 programs and they all said the file/partition was corrupt.
14) Tried to wipe data via TWRP. Failed to wipe because it couldn't be mounted. Followed this:
https://************/how-to-fix-twrp-unable-to-mount-storage-internal-storage-0mb/
15) Ended up with MTP mount of 101 GB free space. Everything seems to be lost on the phone at present. No programs I use to recover the data off the MTP mount (just doing a raw file scrape) can see it as a OnePlus in Windows.
After finding a better guide on XDA, it sounds like this is a known issue that happens when you go from 5.0.x to 9.x on this phone where your encryption breaks and you lose all files. Unfortunately I saw that about 15 minutes after step 14...
My next thoughts would be to:
a) downgrade everything (ROM, firmware, etc) and then try to push the 111 GB .img file back to the phone via ADB, then flash a stock OnePlus 5.0.3 ROM over it to see if I could get the internal storage to mount again. Don't even need to boot into the OS--just to get the internal storage mounted again through TWRP.
--OR--
b) convert the .img file to a .raw and then possibly a .vhd and use Recuva or something to scan the image of the phone and see if I can find those .xml files and maybe a twrp backup if I'm lucky. Although if the entire .img contents is still encrypted and not actually just a corrupt android filesystem, I think I am hosed on this option.
I would prefer option a) but I didn't know if anyone had any insight on this. I thought maybe there would be a way for me to get into the filesystem via ADB maybe and clear out some botched encryption cache or keystore/etc in order to get it to mount again. I'm also not sure if you're able to downgrade the firmware or modem either from 9 to 5 (even though I never got errors on downgrade). Thoughts? Am I just royally hosed?

Tried option b. Nothing but garbage. I made a backup of the .img file this time... so still would be willing to try option a) unless anyone thinks that this is impossible.
Edit: yep... may be too late... https://forum.xda-developers.com/on...-9-0-3-5-0-8-firmware-barrier-t3941164/page18

To my knowledge the data partitions content is unrecoverable lost after the reboot from 5) to 6). The img contains the messed up (and still encrypted) dm0 container but without the enctyption footer which is "outside" the dm0 container in sda15 (aka userdata) partition. To decrypt the img you are missing the device dependent key (an encrypzed partition can be decrypted only on the device the enctyption has been done on) as well as the encryption footer (which is messed up after the reboot).
Format data (not only wipe!) and start over.

Thanks for the reply. That makes sense and is what I was afraid of.
I wonder if it would be possible to regenerate the crypto footer by doing something like this to get the HMAC keys and then flashing a rom to recreate the cryptofooter and then editing the key values to reflect the old cryptofooter values based on the KeyMaster extraction via this exploit.
http://bits-please.blogspot.com/2016/06/extracting-qualcomms-keymaster-keys.html?m=1
It might depend on how much of the cryptofooter is left and whether or not 5.0.3 is vulnerable to these CVEs...
I’m not sure if I know enough about the KeyMaster structure to know how to rebuild it even if I were able to retrieve the HMAC keys.
I also know TWRP now supports EDL so perhaps there is something with a Qualcomm tool I could yse to assist.
Obviously this would mean security issues for everyone on these older builds if I am able to regenerate the crypto footer.
Are you aware of adb commands or likewise that I could run to survey the KeyMaster damage?

As stated: to my knowledge the data is lost after the first reboot with the 9.0.x bootloader.
If you search the official los thread (don't remember if 17 or 16) you'll find some detaled postings on restoring the keys after updating the bl from 5.0.x to 9.0.x. The user, who has examined that has failed, but perhaps it helps to shine some light on your questions.