Database Info

[Solved] Any Possible way to have Magisk and any kind of data encryption in S7?

Hi,
I been searching for a way to encrypt the data partition with magisk and i didn't succeded at all. No matter if flash magisk in an already encrypted system (it says "using cache walkaround" but it gets stuck in the glowing samsung boot logo) or if i try to encrypt the terminal after having a magisk working system. I even tried to mark in magisk "Keep Forced Encryption" in MagiskManager with no success. It makes the system hang again in the boot secuence after reflashing magisk and rebooting.
I just want root in the stock firmware to be able to debloat and use titanium and a couple of apps.
Any way to have encrypted data and root in nougat?

Yes.
There are two requirements to support rooted stock firmware and encryption:
- You MUST use the stock kernel binary. Custom kernel binaries are blocked by TIMA, which handles encryption.
- You need to change "ro.config.tima" in the system build.prop to 0. This doesn't entirely disable TIMA, but seems to relax the encryption requirements a bit(less salting?) which will allow a modified ramdisk to work properly. It's slightly less secure, but still more secure than going unencrypted
Notes: You will need to wipe /data initially after making the build.prop change. You'll need to disable dm-verity after modifying /system. If you installed a custom kernel before you should reflash the entire firmware as the kernel installer likely deleted the TIMA trustlet binary. Some success was had before with getting custom kernels past TIMA by killing the TIMA service soon after boot, but this had the tendency to brick the data partition. Perhaps in future...
Edit: attached a flashable zip to make the build.prop change from TWRP

CurtisMJ said:
Yes.
There are two requirements to support rooted stock firmware and encryption:
- You MUST use the stock kernel binary. Custom kernel binaries are blocked by TIMA, which handles encryption.
- You need to change "ro.config.tima" in the system build.prop to 0. This doesn't entirely disable TIMA, but seems to relax the encryption requirements a bit(less salting?) which will allow a modified ramdisk to work properly. It's slightly less secure, but still more secure than going unencrypted
Notes: You will need to wipe /data initially after making the build.prop change. You'll need to disable dm-verity after modifying /system. If you installed a custom kernel before you should reflash the entire firmware as the kernel installer likely deleted the TIMA trustlet binary. Some success was had before with getting custom kernels past TIMA by killing the TIMA service soon after boot, but this had the tendency to brick the data partition. Perhaps in future...
Edit: attached a flashable zip to make the build.prop change from TWRP
Click to expand...
Click to collapse
Hey , thanks a lot for the info and the file . I learned more from it than 2 days on the internet struggling with this "issue"!
Actually I already tried another way and it worked!
I'll try to explain for the record.
I just installed TWRM and formated /data (not wiping. cause you have to write a file there afterwards) and from there I opened the terminal of TWRM and created /data/.magisk (as in magisk FAQ is explained) with KEEPFORCEENCRYPT=true in it . Then installed a rom (ambasadii's one with magisk 13.6 root ) and... that's it. it worked.
Afterwards i did a lot of automatic tasks of secure network daily backups since when you're encrypted it's kind of easy to f^ckup the system and lose everything and now I'm happy.
Probably i was lucky since the kernel probably is the stock one as you said in this ROM.
I still have to try more stuff to be sure everything is working and the data is safe (safe enough at least)
one question:
do you think it would work if i activate dm-verity or this firmware and or magisk modify the ramdisk (so it wont.) ?

forocarlos said:
Probably i was lucky since the kernel probably is the stock one as you said in this ROM.
I still have to try more stuff to be sure everything is working and the data is safe (safe enough at least)
one question:
do you think it would work if i activate dm-verity or this firmware and or magisk modify the ramdisk (so it wont.) ?
Click to expand...
Click to collapse
dm-verity likely won't work on a custom ROM(unless the ROM maker specifically re-signed it, but that's unlikely and bloody difficult). Making any changes to /system (including the build.prop tweak I mentioned!) will necessitate disabling it and there are a bunch of changes in custom Roms. Ambasadii's nougat ROM does indeed make use of the stock kernel and most likely has the TIMA prop already toggled. So an ideal setup I think. The data should be pretty solid provided the TIMA trustlet never goes missing(encryption keys basically self-destruct, which bricks the partition )
EDIT: You also might want to check in TWRP if the data was genuinely encrypted. Android generally won't complain if it isn't. If TWRP can mount it it isn't encrypted.

EDIT: You also might want to check in TWRP if the data was genuinely encrypted. Android generally won't complain if it isn't. If TWRP can mount it it isn't encrypted.
Click to expand...
Click to collapse
checked.
/data unmountable.
So wrapping things up:
- Magisk root
- CTC passed
- Encryption
- Custom Rom
- Lastest Nougat
:good::good::good::good::good:
the only thing left is figuring out how to update the rom without losing data or everything actually.

forocarlos said:
checked.
/data unmountable.
So wrapping things up:
- Magisk root
- CTC passed
- Encryption
- Custom Rom
- Lastest Nougat
:good::good::good::good::good:
the only thing left is figuring out how to update the rom without losing data or everything actually.
Click to expand...
Click to collapse
Hey, have you figured out a way of updating without losing data?

charliebigpot said:
Hey, have you figured out a way of updating without losing data?
Click to expand...
Click to collapse
Little late sorry, but if you keep the TIMA prop disabled you can flash the full firmware with HOME_CSC and it will keep the data. Just reflash twrp after it does the update(needs full reboot into stock recovery first to finish update) and flash the TIMA zip in this thread with a root zip.

Step-by-Step-Guide to a S7 with Nougat+Root+Magisk+Encryption
Hi there,
I am glad that there is a way to use Nougat, Root and Magisk on an encrypted S7. For the last months I have tried every so-called-solution (TWRP, CF-AutoRoot, reflash Stock boot.img, Helios' Stock kernel) but always ended up in bootloops or an unencrypted device.
Can someone provide me with a step-by-step-guide how to achieve a rooted-magisked-encrypted S7 running Nougat?f I am now running unrooted stock 7.0 with VIA CSC, Build G930FXXU1DQH9.
Thanks in advance!

A step by step for this would be great.
i tried several variations of the proposed methods and did not succeed in any way, please clarify
i tried these variations, and many many more:
flash stock
reboot
flash twrp
wipe system
format data
terminal: KEEPFORCEENCRYPT=true >> /data/.magisk
flash ambassadi rom, dirty flash, magisk root, wipe cache
reboot
set fingerprint & password + fast encrypt
bootloop
format data
wipe sys caches
terminal: KEEPFORCEENCRYPT=true >> /data/.magisk
flash ambassadi rom, clean, magisk root, wipe cache
reboot
set fingerprint & password
reboot
encrypt
bootloop
flash stock
reboot
set fingerprint&pw
reboot
flash twrp
tima
format data
magisk
no-veri opt enc
reboot
set up fingerprint + pw
reboot
encrypt
unsucessful but bootable
The most sucess i had with the stock rom, though i dont remember how exactly. I didnt take my password, which i suspect to be a verification error since the password was the right one
On the batman rom the ui hanged itself on first encrypted startup.
On ambassadi rom i got into bootloop every time.
Did i miss something??

Regarding stock rooted encryption there are some notes, in addition to the requirements in my post above(stock kernel etc):
- Samsung's encryption never handles post setup encryption that well. At least from my experience. You need to be encrypted from the get-go. This implies re-wiping data the moment you're finished flashing the custom ROM as TIMA won't encrypt unless the partition is blank(which it won't be with the leftover magisk config file).
- The TIMA prop must be changed before first boot. Data encrypted with prop in either state is incompatible with data encrypted during the other state. State "1" bootloops on rooting. State "0" allows it.
So for stock the step-by-step would be:
- Flash full stock and use CSC(NOT HOME_CSC), let it reboot to the initial setup screen. This is important to apply the CSC settings from the firmware package, which if not done will result in an unusable secure keyboard and cause various other issues.
- Flash TWRP
- Flash the TIMA prop zip in the post above
- Flash a verity disable zip which DOESN'T disable Force Encryption. For convenience I have attached a modified version which doesn't.
- Format /data
- Reboot into setup and run through the wizard.
- Reboot back to TWRP and flash a root solution like Magisk. Don't worry about force encryption now as the data partition should be encrypted already by this stage. Magisk should revert to the /cache workaround.
To update:
- Flash the latest full stock firmware package but this time use HOME_CSC
- Let it reboot into stock recovery and do the upgrade process.
- It should end up on the secure Startup page asking for your password. No password will work at this point because your data was encrypted in TIMA state "0".
- Reboot to download mode and flash TWRP.
- Reboot to TWRP
- Flash the TIMA prop and verity zips.
- Reboot into to Android (password should work now)
- Let it finish the upgrade.
- Reboot to TWRP and flash your root solution.
These are the basic processes which worked for me.

CurtisMJ said:
Regarding stock rooted encryption there are some notes, in addition to the requirements in my post above(stock kernel etc):
- Samsung's encryption never handles post setup encryption that well. At least from my experience. You need to be encrypted from the get-go. This implies re-wiping data the moment you're finished flashing the custom ROM as TIMA won't encrypt unless the partition is blank(which it won't be with the leftover magisk config file).
- The TIMA prop must be changed before first boot. Data encrypted with prop in either state is incompatible with data encrypted during the other state. State "1" bootloops on rooting. State "0" allows it.
So for stock the step-by-step would be:
- Flash full stock and use CSC(NOT HOME_CSC), let it reboot to the initial setup screen. This is important to apply the CSC settings from the firmware package, which if not done will result in an unusable secure keyboard and cause various other issues.
- Flash TWRP
- Flash the TIMA prop zip in the post above
- Flash a verity disable zip which DOESN'T disable Force Encryption. For convenience I have attached a modified version which doesn't.
- Format /data
- Reboot into setup and run through the wizard.
- Reboot back to TWRP and flash a root solution like Magisk. Don't worry about force encryption now as the data partition should be encrypted already by this stage. Magisk should revert to the /cache workaround.
These are the basic processes which worked for me.
Click to expand...
Click to collapse
when first reboot into TWRP wich option should get? "keep read only" or "allow modifications"?
if I select "allow mods" when I try to flash TIMA.prop file I get an error about mount\data
is it necesary to format data before?
thanks

xbizkuit said:
when first reboot into TWRP wich option should get? "keep read only" or "allow modifications"?
if I select "allow mods" when I try to flash TIMA.prop file I get an error about mount\data
is it necesary to format data before?
thanks
Click to expand...
Click to collapse
Actually the TIMA prop zip doesnt even need data. Not sure why I made it try to mount, but any error about mounting can probably be ignored. It modifies /system so you should swipe to allow.

CurtisMJ said:
Actually the TIMA prop zip doesnt even need data. Not sure why I made it try to mount, but any error about mounting can probably be ignored. It modifies /system so you should swipe to allow.
Click to expand...
Click to collapse
First of all, thanks for your reply and for your small guide
What I did was flash lastest full stock official rom from sammobile with odin and let it reboot to the initial setup screen
Reboot to download mode and then I flashed TWRP also with odin and reboot manually to recovery
When first time entered into recovery just selected "allow modifications"
After I flashed the TIMA prop zip and verity disable zip modified version
In both cases, I received error messages about mount/data on the screen but the installation seems to be complete
Finally format/data, reboot and complete the wizard and the installation
The last step, reboot again into recovery and flash magisk v14
At the end of this procedure, all seems ok, magisk is running, safetynet test is OK, superuser is OK and root apps with no problem
Also a couple of mods flashed with recovery (zero camera mod and sound mod by zubi) gave me error messages about format/data but both of them were done
So, the question is how can I check now if my phone encryption is OK and working ??
The only thing seems not work is the OTA firmware updates, it doesnt work, error message about modified phone
I tried to hide root with magisk for the apps in relation with the ota updates but no work for me
Is there any solution for that??
Thanks for all and very appreciated for your help
And sorry for my english hehe

xbizkuit said:
First of all, thanks for your reply and for your small guide
What I did was flash lastest full stock official rom from sammobile with odin and let it reboot to the initial setup screen
Reboot to download mode and then I flashed TWRP also with odin and reboot manually to recovery
When first time entered into recovery just selected "allow modifications"
After I flashed the TIMA prop zip and verity disable zip modified version
In both cases, I received error messages about mount/data on the screen but the installation seems to be complete
Finally format/data, reboot and complete the wizard and the installation
The last step, reboot again into recovery and flash magisk v14
At the end of this procedure, all seems ok, magisk is running, safetynet test is OK, superuser is OK and root apps with no problem
Also a couple of mods flashed with recovery (zero camera mod and sound mod by zubi) gave me error messages about format/data but both of them were done
So, the question is how can I check now if my phone encryption is OK and working ??
The only thing seems not work is the OTA firmware updates, it doesnt work, error message about modified phone
I tried to hide root with magisk for the apps in relation with the ota updates but no work for me
Is there any solution for that??
Thanks for all and very appreciated for your help
And sorry for my english hehe
Click to expand...
Click to collapse
If the recovery is giving errors about /data mount then the phone is encrypted. TWRP simply cannot work with Samsung encryption at all at the moment. Also: If there is no "Encrypt" option for the internal storage in the Security section of the settings app, then the device is encrypted(There may still be one for the external SD). There's no way I know of to fool OTA into working, I've always just fully flashed the latest firmware. Samsung firmware is really easy to get so I've never really looked into using OTAs to update. They'd probably fail horribly anyway due to the modified system in which case the OTA tool is probably correct to block the update. (Newer Android standard requires updates to be done via raw block writes so dm-verity remains intact. Could lead to corruption if done wrong...)

CurtisMJ said:
If the recovery is giving errors about /data mount then the phone is encrypted. TWRP simply cannot work with Samsung encryption at all at the moment. Also: If there is no "Encrypt" option for the internal storage in the Security section of the settings app, then the device is encrypted(There may still be one for the external SD). There's no way I know of to fool OTA into working, I've always just fully flashed the latest firmware. Samsung firmware is really easy to get so I've never really looked into using OTAs to update. They'd probably fail horribly anyway due to the modified system in which case the OTA tool is probably correct to block the update. (Newer Android standard requires updates to be done via raw block writes so dm-verity remains intact. Could lead to corruption if done wrong...)
Click to expand...
Click to collapse
OK so it seems my phone is finally encrypted and rooted!!!
anyway, I forgot about OTAs and I´ll continue installing updates manually,
so can I flash the full firmware with HOME_CSC without losing the data?
Only reflash TWRP after the update and flash the TIMA prop zip ???
Thank you very much for your help!!!

Thank you CurtisMJ! It finally works!

xbizkuit said:
OK so it seems my phone is finally encrypted and rooted!!!
anyway, I forgot about OTAs and I´ll continue installing updates manually,
so can I flash the full firmware with HOME_CSC without losing the data?
Only reflash TWRP after the update and flash the TIMA prop zip ???
Thank you very much for your help!!!
Click to expand...
Click to collapse
Whoops. Didn't see those were questions. Yes, full flash with HOME_CSC will keep data intact. The TIMA prop will need to be in state "0" to decrypt, so yes again, reflash TWRP and the TIMA and verity zips and you should be good. Just make sure to have "Auto Reboot" checked in Odin. It will do some stuff in stock recovery first (including a screen with "Erasing..." Don't worry! It's just cleaning up the working files in /cache ).

CurtisMJ said:
Whoops. Didn't see those were questions. Yes, full flash with HOME_CSC will keep data intact. The TIMA prop will need to be in state "0" to decrypt, so yes again, reflash TWRP and the TIMA and verity zips and you should be good. Just make sure to have "Auto Reboot" checked in Odin. It will do some stuff in stock recovery first (including a screen with "Erasing..." Don't worry! It's just cleaning up the working files in /cache ).
Click to expand...
Click to collapse
Thanks again mate!!!!!!

WyRM
Hello Guys
Do you think it would work also on Note8 ?
Im stuck on step when i flash 2 files via TWRP, it shows erros with cant mount Data because it is already encrypted somehow, it wouldnt be issue as you said as it does to system.
But when i finish the installation of the Firmware and came back to TWRP for flashing Root solution it is encrypted and cantbe flashed.
Any idea?

WyRmiE said:
Hello Guys
Do you think it would work also on Note8 ?
Im stuck on step when i flash 2 files via TWRP, it shows erros with cant mount Data because it is already encrypted somehow, it wouldnt be issue as you said as it does to system.
But when i finish the installation of the Firmware and came back to TWRP for flashing Root solution it is encrypted and cantbe flashed.
Any idea?
Click to expand...
Click to collapse
That sounds about right actually. The data is supposed to be already encrypted by the time you flash root. TWRP on the S7 and it appears any recent Samsung device cannot decrypt the stock ROMs encryption. The root solution should revert to using the cache workaround. Both Magisk and SuperSU support this setup. Just flash and ignore the /data mount errors.

decrypt /data

move fstab using official recovery ( adbpull /vendor/etc/fstab.kirin970 and fstab.kirin970.data - remove "avb" and encryption from userdata, replace the encryption line on data with 'encryptable')
format /data in unofficial recovery
install magisk in official recovery
for some reason it only works in that order, if you try and do it all in official or unofficial recovery it doesnt work and magisk recognizes encryption on data.
after each step reboot bootloader and flash respective recovery, then fastboot reboot unplug and hold power and vol up to go straight into recovery and continue, if you boot you have to start over)
when installing magisk zip you should see that it doesnt say keep force encrypt.
and if you go in settings you have the option to encrypt.

virtyx said:
move fstab using official recovery ( adbpull /vendor/etc/fstab.kirin970 and fstab.kirin970.data - remove "avb" and encryption from userdata, replace the encryption line on data with 'encryptable')
format /data in unofficial recovery
install magisk in official recovery
for some reason it only works in that order, if you try and do it all in official or unofficial recovery it doesnt work and magisk recognizes encryption on data.
after each step reboot bootloader and flash respective recovery, then fastboot reboot unplug and hold power and vol up to go straight into recovery and continue, if you boot you have to start over)
when installing magisk zip you should see that it doesnt say keep force encrypt.
and if you go in settings you have the option to encrypt.
Click to expand...
Click to collapse
Hi there
I´m struggling to get lineage 15.1 to install without google framework errors
You mention offical and unofficial recovery. I guess you are talking about twrp
when you say move fstab do you mean remove?
Could this encryption be my problem with lineage and gapps not installing as it should?

buenso80 said:
Hi there
I´m struggling to get lineage 15.1 to install without google framework errors
You mention offical and unofficial recovery. I guess you are talking about twrp
when you say move fstab do you mean remove?
Could this encryption be my problem with lineage and gapps not installing as it should?
Click to expand...
Click to collapse
After you install lineage format /data that should work
Totally irrelevant to OP

If i hadn't tried that i wouldn't ask here.
Not TOTALLY irrelevant, as my question is about the official and unofficial twrp having trouble mounting and wiping before flashing rom..
Please stop trolling

virtyx said:
move fstab using official recovery ( adbpull /vendor/etc/fstab.kirin970 and fstab.kirin970.data - remove "avb" and encryption from userdata, replace the encryption line on data with 'encryptable')
format /data in unofficial recovery
install magisk in official recovery
for some reason it only works in that order, if you try and do it all in official or unofficial recovery it doesnt work and magisk recognizes encryption on data.
after each step reboot bootloader and flash respective recovery, then fastboot reboot unplug and hold power and vol up to go straight into recovery and continue, if you boot you have to start over)
when installing magisk zip you should see that it doesnt say keep force encrypt.
and if you go in settings you have the option to encrypt.
Click to expand...
Click to collapse
If you format data, isn't the device going to be empty?
Only time I've done this before I had to copy a ROM via MTP in recovery and then flash with no Verity.
So forgive me if I'm wrong but if I format data, won't I end up with no operating system?

dladz said:
If you format data, isn't the device going to be empty? J
Only time I've done this before I had to copy a ROM via MTP in recovery and then flash with no Verity.
So forgive me if I'm wrong but if I format data, won't I end up with no operating system?
Click to expand...
Click to collapse
/system is where the system lives
/data is userdata and applications
Noting wrong with formatting, you will lose all apps and data though

virtyx said:
/system is where the system lives
/data is userdata and applications
Noting wrong with formatting, you will lose all apps and data though
Click to expand...
Click to collapse
Legend, thanks for clearing that up.
:good:
I know off topic, but out of interest with the p20 pro, if you did find yourself with no OS how would you get back to a functional phone?
There's no custom ROMs to flash, just never been in this situation before.
Hypothetically

dladz said:
Legend, thanks for clearing that up.
:good:
I know off topic, but out of interest with the p20 pro, if you did find yourself with no OS how would you get back to a functional phone?
There's no custom ROMs to flash, just never been in this situation before.
Hypothetically
Click to expand...
Click to collapse
You can use hurupdater and download the firmware from firmwarefinder on your of
Happened a lot of times for me

Just as a headsup, you dont need to decrypt anything when you just wanna do some changes once and are proper admin level on your desktop machine, ive moved a whatsapp message history from previous phone (also taken from protected space there) to P20P just by attaching it to pc in file transfer mode and then adding myself as full control user in the security tabs of the several system folder properties i went in to, worked like a charm.
The point im trying to make: Android and Windows finally understand each others permission systems (not sure since how long as ive been away from android for a few years) so you can just attach it and use Windows perm system to give yourself access where needed, lots easier & faster then making a bunch of changes to your phone in effect disabling encryption, something you in most cases dont really want to do permanently anyway, so this is a nice workaround that doesn't touch your phone's encryption settings but still lets you mess about with system files.
Just my 2 cents.

virtyx said:
move fstab using official recovery ( adbpull /vendor/etc/fstab.kirin970 and fstab.kirin970.data - remove "avb" and encryption from userdata, replace the encryption line on data with 'encryptable')
format /data in unofficial recovery
install magisk in official recovery
for some reason it only works in that order, if you try and do it all in official or unofficial recovery it doesnt work and magisk recognizes encryption on data.
after each step reboot bootloader and flash respective recovery, then fastboot reboot unplug and hold power and vol up to go straight into recovery and continue, if you boot you have to start over)
when installing magisk zip you should see that it doesnt say keep force encrypt.
and if you go in settings you have the option to encrypt.
Click to expand...
Click to collapse
I did everything step by step, the encryption is gone and yet I still get that stupid permission denied error when I try to do a backup in TWRP. So. F*cking. Annoying.
Update: when I press the "Install" button in TWRP, it shows giberish, but if I go to Advanced>File Manager everything has it's proper name. WTF?!
Hmmm, If I don't tick "Vendor" in the backup, I get this error:
Can not create 'data/media/0/2021-01-20--07-26-51' folder (No such file or directory).
Failed to make backup folder.
Update on update: oof, now everything that's in the internal storage is gibberish, even in the OS.

Tutorial : Decrypt And Flash Any ROM [ Working on Android 10 ][No data loss]

{
"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"
}
FLASHING INSTRUCTION :
Warning : Always Backup Your Internal Storage For safer side
Points to be Noted :
1 : Dirty Flashing sometime works. But might have hidden bugs.
2 : Remove the pattern and also fingerprints before flashing the rom.
3 : Always you have to flash twrp zip file after flashing rom. Else you will loose twrp.
If you are on some other twrp versions, Kindly download Compatible TWRP recovery IMG file from download Section and Flash it in recovery.
TWRP installer zip by mauronofrio - Supports Android 10
This works Fine. I recommend all to use this recovery.
To Decrypt Your Device : [ For First Time ]
Step 1: Place the Full ROM zip file in internal Storage.
Step 2: Now Reboot the phone to TWRP Recovery.
Step 3: Wipe Dalvik cache ,Data , System and Cache.
Step 4: Now select Full ROM zip file and swipe to flash it and then flash the twrp zip file again
Step 5: Format DATA and reboot to recovery.
Step 6: Now in recovery flash magisk 20.4
Step 7: Now Flash the No-verity file - Pie Supported here and Android 10 Supported from here[Important]
Step 8: Reboot the phone.
Step 9: Voila !! Now your device is successfully decrypted and
Now To Flash OOS updates in Your Decrypted Device : - Works For Android 10 Based OOS
Step 1: Place the Full OOS ROM zip file in internal Storage.
Step 2: Now Reboot the phone to TWRP Recovery.
Step 3: Wipe Dalvik cache ,Data , System and Cache.
Step 4: Now Flash OOS Zip and twrp zip file and reboot to recovery.
Step 5: Now in recovery flash magisk 20.4 only
Step 6: Now Flash the No-verity file - Pie Supported here and Android 10 Supported from here[Important]
Step 7: Reboot the phone. Now both TWRP and Magisk will be there and still your device is decrypted too with android 10
To Flash CustoM ROMs in Your Decrypted Device :
Step 1: Place the Full Custom ROM zip file and required base version Rom zip file ( I.e., OOS BETA OR OOS STABLE) in internal Storage.
Step 2: Now Reboot the phone to TWRP Recovery.
Step 3: Wipe Dalvik cache ,Data , System and Cache.
Step 4: Now Flash OOS Zip and twrp and reboot to recovery and Flash oos zip and twrp again and reboot to recovery. Now select Full Custom ROM zip file and swipe to flash.
Step 5: Flash the twrp zip file again and reboot to recovery.
Step 6: Now in recovery flash magisk 20.4
Step 7: Now Flash the No-verity file - Pie Supported here and Android 10 Supported from here[Important]
Step 8: Reboot the phone.
Credits : @topjohnwu, @virtyx and others .
@mauronofrio for his TWRP.

Download Section :
Recovery:
Official TWRP ||
Blu_Spark TWRP || Unofficial TWRP by joemossjr || TWRP installer zip by mauronofrio - Supports Android 10
For Root :
Magisk
To Decrypt :
No Verity Mod for OP6 ​

HatRiGt said:
Download Section :
Recovery:
Official TWRP ||
Blu_Spark TWRP || Unofficial TWRP by joemossjr
For Root :
Magisk
To Decrypt :
No Verity Mod for OP6 ​
Click to expand...
Click to collapse
Please excuse the dumb questions, I am new to these parts (Device Delivery for Tomorrow), but other then Treble and if TWRP isnt decrypting, why else would you want to decrypt your Device? And finally, the No-Verity MOD is the last part of the instructions, so my question is does the device automatically encrypt when all said and done?

Unlocked.Devices said:
Please excuse the dumb questions, I am new to these parts (Device Delivery for Tomorrow), but other then Treble and if TWRP isnt decrypting, why else would you want to decrypt your Device? And finally, the No-Verity MOD is the last part of the instructions, so my question is does the device automatically encrypt when all said and done?
Click to expand...
Click to collapse
keeping your device decrypt will make you to switch between any roms easily. You dont need to wipe internal storage thereafter.
Flashing Untouched OOS ROM will make your device to get force encrypt, so to avoid that you need to flash no verity mod .

I'm running oos 1.5.11 rooted with magisk 17.1 and twrp 3.2.3-0. can I flash this zip now without starting everything over? Sorry if this has already been asked.
---------- Post added at 08:29 PM ---------- Previous post was at 08:28 PM ----------
Oops....5.1.11

mixlex said:
I'm running oos 1.5.11 rooted with magisk 17.1 and twrp 3.2.3-0. can I flash this zip now without starting everything over? Sorry if this has already been asked.
---------- Post added at 08:29 PM ---------- Previous post was at 08:28 PM ----------
Oops....5.1.11
Click to expand...
Click to collapse
If your device is encrypted, first take backup of your internal storage and follow the steps in op

mixlex said:
I'm running oos 1.5.11 rooted with magisk 17.1 and twrp 3.2.3-0. can I flash this zip now without starting everything over? Sorry if this has already been asked.
---------- Post added at 08:29 PM ---------- Previous post was at 08:28 PM ----------
Oops....5.1.11
Click to expand...
Click to collapse
Sadly no. Data format is required to decrypt phone

m8, I don't get step 4 of decrypting device.
I select Full ROM and at the same time we Format Data?
Thanks for the guide!:good:

refedit said:
m8, I don't get step 4 of decrypting device.
I select Full ROM and at the same time we Format Data?
Thanks for the guide!:good:
Click to expand...
Click to collapse
First flash the rom and then format the data.

HatRiGt said:
First flash the rom and then format the data.
Click to expand...
Click to collapse
After formatting data I'm having issues mounting, I tried fastbooting twrp to get mounted to get files over(any chance this would mess anything up?).
Should the no verity mod always be flashed last and does it require a reflash after say flashing a kernel?

snigor said:
After formatting data I'm having issues mounting, I tried fastbooting twrp to get mounted to get files over(any chance this would mess anything up?).
Should the no verity mod always be flashed last and does it require a reflash after say flashing a kernel?
Click to expand...
Click to collapse
1) Actually never use that twrp that has support for MTP. Always use normal twrp.
If you have got any mounting issue, just flash the fastboot rom and then again boot to twrp and then follow the steps in OP carefully.
2) Yes no verity should be always flashed in the last before you boot into the system .
even if you flash kernel / magisk, then you have to flash no verity.

Now ROMs in your decrypted device Flash
After instruction flashed restart always takes place again and again into the recovery
Is there a reason for that

saleappeal said:
Now ROMs in your decrypted device Flash
After instruction flashed restart always takes place again and again into the recovery
Is there a reason for that
Click to expand...
Click to collapse
could you explain it clearly about what you have done ?

give credit where credit is due
https://forum.xda-developers.com/oneplus-6/how-to/test-decryption-t3818775

virtyx said:
give credit where credit is due
https://forum.xda-developers.com/oneplus-6/how-to/test-decryption-t3818775
Click to expand...
Click to collapse
Done bro.

HatRiGt said:
1) Actually never use that twrp that has support for MTP. Always use normal twrp.
If you have got any mounting issue, just flash the fastboot rom and then again boot to twrp and then follow the steps in OP carefully.
2) Yes no verity should be always flashed in the last before you boot into the system .
even if you flash kernel / magisk, then you have to flash no verity.
Click to expand...
Click to collapse
I'm using blu_spark twrp(was recommended both in OP and for flashing pie OB1) and MTP worked fine. Up until formatting, that is.. it does say you might need to restart to use file system(I'm guessing either for mounting or decrypting filesystem after format?). It'll just show the device with no space total or used, and then times out if i try to create a folder or copy something over.. is the trick here to put the needed files on a partition that's not touched when formatting, if that's a thing?
I feel like I'm missing something, but I think my issue was just flashing kernel last.. I'm gonna look into the manual method at some point to get a better idea of what's what! Thanks a lot!:good:

I mean after formatting you end up with no twrp zip to flash and you cant transfer files in twrp…..
Or at least I couldn't at first. I was stuck with no os and an empty internal storage. My newer computer couldn't transfer files.
However after hooking it up to my old computer I was able to transfer files in twrp using blu spark twrp. I put the liquid remix rom, twrp, magisk, gapps and the no verity zip in internal.
flashed rom, flashed twrp, rebooted recovery, flashed gapps, magisk, then flashed no verity and rebooted system.
Pretty sure the only reason I was able to transfer those file is because liquid remix has adb debugging and mtp checked by default in developer settings.
And i'm still decrypted so all is good.

SelfElevated2 said:
I mean after formatting you end up with no twrp zip to flash and you cant transfer files in twrp…..
Or at least I couldn't at first. I was stuck with no os and an empty internal storage. My newer computer couldn't transfer files.
However after hooking it up to my old computer I was able to transfer files in twrp using blu spark twrp. I put the liquid remix rom, twrp, magisk, gapps and the no verity zip in internal.
flashed rom, flashed twrp, rebooted recovery, flashed gapps, magisk, then flashed no verity and rebooted system.
Pretty sure the only reason I was able to transfer those file is because liquid remix has adb debugging and mtp checked by default in developer settings.
And i'm still decrypted so all is good.
Click to expand...
Click to collapse
Actually u can also flash twrp file before formating data. Or format data and boot to recovery using Fastboot method.

In order overcome this file transfer problem after format data I used a USB flash drive and viola, problem solved, hope this helps. cheers.

HatRiGt said:
Actually u can also flash twrp file before formating data. Or format data and boot to recovery using Fastboot method.
Click to expand...
Click to collapse
Yeah but stock rom has USB debugging off by default. So someone that flashes stock wouldn't be able to use fast boot or file transfer. They would have to use the UNbrick tool. You may want to to change the order in instructions so less knowledgeable people don't run into problems.
Even if you flash TWRP before formatting, you still lose the no verity you put in internal storage. A fresh install of stock rom won't let you use fast boot commands as USB debugging is off by default
vtec303 said:
In order overcome this file transfer problem after format data I used a USB flash drive and viola, problem solved, hope this helps. cheers.
Click to expand...
Click to collapse
Yeah I just ordered one on eBay yesterday. I figured that would be a huge help as long as TWRP let's you access the other storage.
Sent from my OnePlus6 using XDA Labs

[RECOVERY] [OFFICIAL] OrangeFox Recovery Project [X01BD]

ORANGEFOX RECOVERY PROJECT
Asus Zenfone Max Pro M2 [X01BD]
[OFFICIAL]
Disclaimer
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed
If you point the finger at me for messing up your device, I will laugh at you. Hard. A lot
Instructions :
- Flash OFRP through any recovery (or recovery.img through fastboot and reflash the zip again)
- Reboot and enjoy
Notes:
Use only R11.1 to flash encrypted roms
Settings to disable force encryption is set by default
If you are flashing an encrypted rom and wish to move from :
Decrypted to Encryption / Encrypted to Encryption => untick disable force encryption from settings
Encrypted to Decryption / Decrypted to Decryption => tick disable force encryption from settings
: before flashing the rom
Wipe and format internal storage, if you are changing the encryption state
Changelog: R11.1
Add Support for terminal from filemanager
Add file manager option to edit selected file
Open Magisk apk as zip
Implement 'twrp format data' to format /data
Update the ZIP signature verification
Update the initd addon
Re-sign the internal zips
Addon to remove survival scripts
Flashable zip for backing up OrangeFox settings (/FFiles/OF_backup_settings.zip)
Many UI and other fixes and enhancements
Work-around for MTP issues after data format
Supports FBE encryption
Credits : @MrYacha, DarthJabba9
@adikri, @praveenpannu, t.me/Shrey2013 (testers)
Downloads :
R9, R10
R10.1, R11, R11.1
XDA:DevDB Information
OrangeFox Recovery Project, Tool/Utility for the Asus Zenfone Max Pro M2
Contributors
legacy07
Source Code: https://gitlab.com/legacy08/x01bd
Version Information
Status: Stable
Current Stable Version: R11.1-1
Stable Release Date: 2021-06-15
Beta Release Date: 2021-05-12
Created 2019-02-15
Last Updated 2021-06-15​

The king of recoveries
Edit: Does this have a password feature ? I think SHRP has...

Tyakrish said:
The king of recoveries
Edit: Does this have a password feature ? I think SHRP has...
Click to expand...
Click to collapse
Yep. It does

#ArtFuL said:
Yep. It does
Click to expand...
Click to collapse
Would it be possible to add password feature to PBRP ? Or will there be a stable official recovery with password support ?

Tyakrish said:
Would it be possible to add password feature to PBRP ? Or will there be a stable official recovery with password support ?
Click to expand...
Click to collapse
Pbrp doesn't support password protection as of now. Will make ofrp stable with R9 build

Changelog

This or pbrp?

What about future OTA ? Will it be possible ? (just flash stock recovery to get it ?

joshuaroilox123 said:
This or pbrp?
Click to expand...
Click to collapse
This better than PBRP

lit
the ui is just lit

Is there beta UI will coming up bro? Thanks for your contribution.

saktibimantara said:
Is there beta UI will coming up bro? Thanks for your contribution.
Click to expand...
Click to collapse
No. I will release only stable builds

Does decryption work?
Hi,
In OFRP I cannot mount the encrypted data partition with either stock Oreo ROM or RR 7.0. Of course I can reformat data partition but I just want to know if decryption works at all? Neither does TWRP.

ywliu said:
Hi,
In OFRP I cannot mount the encrypted data partition with either stock Oreo ROM or RR 7.0. Of course I can reformat data partition but I just want to know if decryption works at all? Neither does TWRP.
Click to expand...
Click to collapse
If you wanna access the existing encrypted data partition, you need to decrypt it first, no matter which recovery it is. Ofrp / pbrp decryption only works while flashing a new the rom

Thanks for the R10. UI is top-notch.

Just a heads up guys, don't forget to enable "Disable DM-Verity" and "Disable Forced Encryption" in Menu > Settings gear icon > OTA before you flash stock rom zip if you want to disable forced encryption in R10.

anagramgenius said:
Just a heads up guys, don't forget to enable "Disable DM-Verity" and "Disable Forced Encryption" in Menu > Settings gear icon > OTA before you flash stock rom zip if you want to disable forced encryption in R10.
Click to expand...
Click to collapse
Thanks for testing it thoroughly and reporting bugs...

Tyakrish said:
Thanks for testing it thoroughly and reporting bugs...
Click to expand...
Click to collapse
I'm so obsessed with disabling forced encryption with a standalone zip. I still wonder how changing a single word in fstab could disable it in Oreo while I tried flashing many scripts and still unable to disable it in Pie. I even tried the script method used by OFRP which is a modification of @wzsx150's script and I was unsuccessful.

If I disable force encryption, I don't have to flash decrypt.zip of Pie to decrypt my system partition after updating to Pie?
---------- Post added at 03:43 PM ---------- Previous post was at 03:31 PM ----------
anagramgenius said:
@legacy07, here are some differences in R9 and R10 I found wrt disabling forced encryption in stock rom.
R9 disables forced encryption in two cases without having to flash Magisk.
1) During fresh installation, i.e. I flashed extracted recovery.img in fastboot. And then I went to recovery mode and flashed the recovery zip. It rebooted automatically to recovery. After rebooting to recovery, it showed that it is fresh installation, and it disabled forced encryption. There was a text in green actually, which said it patched dm-verity and forced encryption. This was done without flashing stock rom zip. (Off topic. This doesn't happen in PBRP. It just disables forced encryption after flashing rom zip, but not after fresh installation. I don't know if it is intended to work this way)
2) It patches forced encryption after flashing stock rom zip by displaying a text in green.
R10 disables forced encryption in only one case, i.e. after fresh installation, provided if Magisk is flashed before booting into system.
1) During fresh installation, I followed same steps as I did with R9, but after it rebooted itself when I flashed recovery zip, it wouldn't patch forced encryption unless I flash magisk zip. It says
"Fresh OrangeFox installation - about to run the dm-verity/forced-encryption patches
Not patching boot image on X01BD. Flash magisk after this."
So I flashed magisk zip after fresh installation. Then it disabled forced encryption. But without flashing magisk zip, it doesn't patch forced encryption and it reverts back to stock recovery.
2) It doesn't patch forced encryption after flashing stock rom zip. It doesn't say anything about disabling forced encryption or flashing magisk after it has flashed stock rom. For my curiosity, I flashed magisk zip after flashing stock rom zip. But after booting to system, it started encrypting and forced encryption was never patched. But it didn't revert back to stock recovery as I had flashed magisk zip. If I don't flash magisk zip, it will revert back to stock recovery. But in both cases, it will not patch forced encryption after flashing stock rom.
To sum it up, R10 isn't patching forced encryption after flashing stock rom zip. It just patches forced encryption if I follow these steps:
1) Flash stock rom zip.
2) Flash OFRP recovery zip. (It reboots to recovery)
3) Flash magisk zip. (It says me to flash magisk to patch the boot image)
Just a heads up guys, don't forget to enable "Disable DM-Verity" and "Disable Forced Encryption" in Menu > Settings gear icon > OTA before you flash stock rom zip if you want to disable forced encryption in R10.
Click to expand...
Click to collapse
I am not getting you properly, why we require to flash OFRP recovery zip? I presume you flashed the stock ROM.zip with OFRP, ain't you? If you did, still you need to flash OFRP recovery zip after flashing stock ROM zip?
Secondly, if I disable DM-Verity and Disable Forced Encryption, before flashing stock ROM, I won't need to flash decrypt.zip of Pie, right? I am actually still on rooted Oreo and now I am planning to update my device to Pie.
@legacy07, please reply.

nice_guy75 said:
If I disable force encryption, I don't have to flash decrypt.zip of Pie to decrypt my system partition after updating to Pie?
---------- Post added at 03:43 PM ---------- Previous post was at 03:31 PM ----------
I am not getting you properly, why we require to flash OFRP recovery zip? I presume you flashed the stock ROM.zip with OFRP, ain't you? If you did, still you need to flash OFRP recovery zip after flashing stock ROM zip?
Secondly, if I disable DM-Verity and Disable Forced Encryption, before flashing stock ROM, I won't need to flash decrypt.zip of Pie, right? I am actually still on rooted Oreo and now I am planning to update my device to Pie.
@legacy07, please reply.
Click to expand...
Click to collapse
Seems you're using XDA Forums app. If you use a browser to see my post, you'll see I have struck the methods which are redundant. My actual post starts from "Just a heads up guys..."
So you don't have to flash OFRP recovery zip again after flashing stock rom zip. You just have to enable those two options which I mentioned above before flashing stock rom zip.
decrypt.zip isn't working in Pie. OFRP or PBRP are the only two recoveries which are able to disable forced encryption in stock Pie rom. So you don't have to flash decrypt.zip after flashing stock rom zip when you use PBRP or OFRP to flash stock rom.

warning dont upgrade new version of magisk 20.2

came out today. bricked my lg v20 h918
come up showing red text with number of times bootloader is unlocked and will not boot further..
tried direct install.
had to hold button down like going into recovery then select yes twice then getg into twrp then restore boot and lafs etc.
then when all working i tried to install the same version via twrp install same issue. apparently installing to wrong partition..
reinstalling the older 20.1 (hopefully you have it downloaded) from twrp worked fine.

Thanks for the info! Little late for me. Just wanted to post the last known good Magisk for anyone that needs it.
Search for download-magisk-20-1-stable

What did you do after booting into TWRP?

same issue, unfortunately, saw this post too late

same and now im screwed how can we recover this?
it says warranty void !!
number of times bootloader unlocked : 2 (in red
*Welcome to Fastboot mode:
* HOW TO EXIT fastboot mode
use 'fastboot reboot' command if the fastboot is available
i tried to install magisk 18 and then 20.1. they install but im still bricked at this same issue above.
HELP
h918

I was able to get up and running again by flashing H91820h.zip in TWRP, then flash Magisk-v20.1.zip and finally TWRP 3.3.1-0 2019-05-17 .img
Phone booted normally after this process. Hope this helps!

Similar situation. Fortunately, I did a nandroid backup first, so I restored it to get the phone up and running again.

My Success Story
For those of you who, like me, didn't have a known good backup to work with, here's what I did:
Determine ROM version installed if you don't know what it is (I was able to check the /system/build.prop file from TWRP under ro.lge.swversion)
Grab the appropriate ROM .zip file (I got my h910-10r zip file from the H910 Root Post)
Unzip the ROM file
Grab the "boot" file from the ROM and place on an SD card as boot.img
Flash boot.img to the boot partition using the TWRP install function (you'll have to toggle it to show Images in the install screen)
Reflash Magisk v20.1 (you can download it from github)
Wipe Dalvik and Cache
Reboot
Wait for the LONG boot process which will go through the nerve-wracking android is staring screen with the percentage bar as it rebuilds the Dalvik cache (I think that's what it's doing)
As a note, this did not clear any of my data.
Good luck, YMMV.

For anyone with this issue run the latest magisk uninstaller in twrp and restart the phone. If that doesn't work boot back into twrp and install magisk 20.1

---------- Post added at 08:47 PM ---------- Previous post was at 08:45 PM ----------
James.ptrsn said:
For those of you who, like me, didn't have a known good backup to work with, here's what I did:
Determine ROM version installed if you don't know what it is (I was able to check the /system/build.prop file from TWRP under ro.lge.swversion)
Grab the appropriate ROM .zip file (I got my h910-10r zip file from the H910 Root Post)
Unzip the ROM file
Grab the "boot" file from the ROM and place on an SD card as boot.img
Flash boot.img to the boot partition using the TWRP install function (you'll have to toggle it to show Images in the install screen)
Reflash Magisk v20.1 (you can download it from github)
Wipe Dalvik and Cache
Reboot
Wait for the LONG boot process which will go through the nerve-wracking android is staring screen with the percentage bar as it rebuilds the Dalvik cache (I think that's what it's doing)
As a note, this did not clear any of my data.
Good luck, YMMV.
Click to expand...
Click to collapse
Thanks so much, you really saved me. I was panicking for sure. These directions need to be stickied!
---------- Post added at 08:49 PM ---------- Previous post was at 08:47 PM ----------
BadToThePhone said:
For anyone with this issue run the latest magisk uninstaller in twrp and restart the phone. If that doesn't work boot back into twrp and install magisk 20.1
Click to expand...
Click to collapse
Tried didn't work, but thanks, the one above worked for sure, no lost data

lgkahn said:
came out today. bricked my lg v20 h918
come up showing red text with number of times bootloader is unlocked and will not boot further..
tried direct install.
had to hold button down like going into recovery then select yes twice then getg into twrp then restore boot and lafs etc.
then when all working i tried to install the same version via twrp install same issue. apparently installing to wrong partition..
reinstalling the older 20.1 (hopefully you have it downloaded) from twrp worked fine.
Click to expand...
Click to collapse
Unfortunately i wasn't lucky with this.. got stuck in fastboot, my sd and internal storage are both wiped, Rip years of data on that sd.. Can't get a system on the SD or internal storage, Fastboot isn't helping, ADB sideload won't load in twrp, LG Bridge won't detect my phone Am i screwed with this? I can boot to twrp but thats about it

texas7412 said:
Unfortunately i wasn't lucky with this.. got stuck in fastboot, my sd and internal storage are both wiped, Rip years of data on that sd.. Can't get a system on the SD or internal storage, Fastboot isn't helping, ADB sideload won't load in twrp, LG Bridge won't detect my phone Am i screwed with this? I can boot to twrp but thats about it
Click to expand...
Click to collapse
TWRP on my US996 automatically made the phone a usb drive when it got plugged in. Have you looked for it as a usb drive? also have you checked your usb drivers?

James.ptrsn said:
For those of you who, like me, didn't have a known good backup to work with, here's what I did:.......................
Click to expand...
Click to collapse
Fortunately there is even more easy way to recover.
My H990DS has been also affected by Magisk update. Luckily I discovered that Magisk itself makes a backup of the boot image during update from previous Magisk version. It is located in the /data/magisk_backup_<very long sequence of characters and digits>. The name of the backup archive file is boot.img.gz
So I booted to TWRP, unziped the file boot.img from the above archive and flashed it to the boot partition using TWRP. Then rebooted to system.
And that's all folks! No data loss, no need to look for original ROM.zip, no need to look for and re-flash Magisk 20.1 (the system has been restored automatically to Magisk 20.1), no need to wipe Dalvik and Cache!
I think that this solution is the most simple and easy, so need to be in sticky post.

I'm in the TWRP Recovery file manager and I can't see magisk backup folder.

pendgy said:
Fortunately there is even more easy way to recover.
My H990DS has been also affected by Magisk update. Luckily I discovered that Magisk itself makes a backup of the boot image during update from previous Magisk version. It is located in the /data/magisk_backup_<very long sequence of characters and digits>. The name of the backup archive file is boot.img.gz
So I booted to TWRP, unziped the file boot.img from he above archive and flashed it to the boot partition using TWRP. Then rebooted to system.
And that's all folks! No data loss, no need to look for original ROM.zip, no need to look for and re-flash Magisk 20.1 (the system has been restored automatically to Magisk 20.1), no need to wipe Dalvik and Cache!
I think that this solution is the most simple and easy, so need to be in sticky post.
Click to expand...
Click to collapse
Thank you. This helped a lot. Can't remember ever being without my phone for this long. Very stressful. This worked for my LG V20. Few things to add. I was super nervous to boot into twrp using the hardware "factory reset" option. Normally it just asks to wipe data once before booting into TWRP but after this happened, it asked two times. Was worried the magisk "update" wiped out my twrp and I was going to actually wipe all of my data using the recovery option. After unsuccessfully trying multiple ways to install twrp via fastboot as a safety net, I bit the bullet and did the double factory reset. Thankfully, it brought me to TWRP. Those of you worried, hope this helps ease your mind that twrp is intact after this debacle.
Next, using @pendgy help, I found the boot.img.gz but was unable to unzip in twrp. I copied the file to the internal sd so I could view on my pc. Connected to pc while in twrp and unzipped the boot.img.gz folder. Then extracted the boot.img into the internal sd. Was then able to install image to boot partition. Rebooted and everything was exactly as it was 17 hours ago when my heart sank. Yay!

Thanks to everyone for the reports and warnings. I saw the update to Magisk Manager yesterday on my Shield K1 and allowed that to update. I didn't update Magisk itself because I don't trust the direct install method through Manager. I saw the notification on my sandbox V20 this morning and dismissed it. My daily V20 hasn't received an update notification yet, but I think I disabled status bar notifications for Magisk on my daily. I'll be sure to not install 20.2 on either phone.
Magisk Manager's update notifications are pretty annoying to be honest. My devices are already rooted. An updated version of Magisk isn't going to make them rooted better.

Oh boy. Learning a lot of hard lessons this morning.
Apparently my TWRP install has been broken/corrupted for who knows how long. I'm now several hours into restoring my phone from basically scratch (had to retry a bunch of times because I'm a dumbdumb and haven't poked around at Android recoveries in ages).
Moral of the story: BACK UP EARLY and BACK UP OFTEN. If you don't have a backup (any kind of backup), the day will inevitably come when you wish you did. Sigh.
Oh well, maybe my phone will run a bit smoother now. Good luck everyone.

pendgy said:
Fortunately there is even more easy way to recover.
My H990DS has been also affected by Magisk update. Luckily I discovered that Magisk itself makes a backup of the boot image during update from previous Magisk version. It is located in the /data/magisk_backup_<very long sequence of characters and digits>. The name of the backup archive file is boot.img.gz
So I booted to TWRP, unziped the file boot.img from the above archive and flashed it to the boot partition using TWRP. Then rebooted to system.
And that's all folks! No data loss, no need to look for original ROM.zip, no need to look for and re-flash Magisk 20.1 (the system has been restored automatically to Magisk 20.1), no need to wipe Dalvik and Cache!
I think that this solution is the most simple and easy, so need to be in sticky post.
Click to expand...
Click to collapse
How did you unzip the archive with TWRP?
Edit: Nevermind, copied the archive to external SD und unzipped it with 7z on my computer.

fatappel said:
...............................
Next, using @pendgy help, I found the boot.img.gz but was unable to unzip in twrp. I copied the file to the internal sd so I could view on my pc. Connected to pc while in twrp and unzipped the boot.img.gz folder. Then extracted the boot.img into the internal sd. Was then able to install image to boot partition. Rebooted and everything was exactly as it was 17 hours ago when my heart sank. Yay!
Click to expand...
Click to collapse
In fact I did the same I didn't menioned all the stuff with connecting to PC, copying files to PC, extracting archives and copying back to the phone the boot.img file for subsequent flashing via TWRP. This is because I know the forum members here are experienced guys
The lesson learned is that TWRP is rock solid and we shall trust to it
---------- Post added at 23:37 ---------- Previous post was at 23:36 ----------
Attila17 said:
How did you unzip the archive with TWRP?
Click to expand...
Click to collapse
See my last post. I didn't. I used a PC to do that.

I got really ****ed by magisk.
Did the recommended update and now I`m stuck at the fastboot screen
I can fastboot reboot but nothing else
how do I boot into twrp (power vol button down only brings fastboot)
I tried flashing twrp via fastboot but i get failed remote (unknow command)
any help please ?