Database Develop

issues with twrp (apparent file encryption)

Hi, im having a little bit of a problem here, i succesfully managed to unlock the bootloader of my chinese mi8, flashed and booted twrp, the issue is, my files seem to be encrypted, i can't copy anything to the device while on fastboot/recovery mode from the pc, tried booting to miui, allowing the transfer of files and booting to twrp again (for some reason i can't boot to twrp from the device itself, it has to be via fastboot with the command "fastboot boot ***") but all twrp shows me are folders with random characters, it seems to be some sort of auto-encryption, do you know how to solve it?

Miui auto encrypts the device, that is why your device is encrypted. You are unable to boot to twrp for two reasons: 1. Miui auto checks and rewrites over any custom recovery 2. Fastboot boot command does not install twrp, it only boots into it, from which u must install twrp again.
Upon booting into twrp, you need to FORMAT data, flash TWRP, flash this file https://zackptg5.com/android.php#disverfec (DM-verity and anti-encryption) this will prevent anti encryption when your freshly flashed ROM boots up.
Side note: DO NOT RELOCK YOUR BOOT LOADER IF YOUR MI 8 IS CHINA VARIANT AND YOU ARE INSRALLING GLOBAL ROM.
I HIGHLY SUGGEST YOU HEAD OVER ONTO THIS THREAD TO UNDERSTAND BETTER! https://forum.xda-developers.com/mi-8/development/rom-mi-8-miui-10-global-beta-8-8-7-t3826560/page7

achickennugget said:
Miui auto encrypts the device, that is why your device is encrypted. You are unable to boot to twrp for two reasons: 1. Miui auto checks and rewrites over any custom recovery 2. Fastboot boot command does not install twrp, it only boots into it, from which u must install twrp again.
Upon booting into twrp, you need to FORMAT data, flash TWRP, flash this file https://zackptg5.com/android.php#disverfec (DM-verity and anti-encryption) this will prevent anti encryption when your freshly flashed ROM boots up.
Side note: DO NOT RELOCK YOUR BOOT LOADER IF YOUR MI 8 IS CHINA VARIANT AND YOU ARE INSRALLING GLOBAL ROM.
I HIGHLY SUGGEST YOU HEAD OVER ONTO THIS THREAD TO UNDERSTAND BETTER! https://forum.xda-developers.com/mi-8/development/rom-mi-8-miui-10-global-beta-8-8-7-t3826560/page7
Click to expand...
Click to collapse
Ok, lets see if i got it right, just to be sure...
i boot to twrp
i format data in twrp (only data)
flash the twrp file from fastboot
flash the file for preventing encryption IN TWRP
flash my rom of choice

what i did was
1.flash global stable 9.5 via fastboot
2.Wait till it gets on
3.Restart the device
4.flash twrp via fastboot
5.install magisk 16.7 using twrp
6.install dm verity
7.format data
8.wait till it boots downgrade magisk to 16.0 via magisk manager

[SOLVED] TWRP bootloop after OTA update from Global V10.2.1.0 (PEAMIXM) with Magisk

Hello guys,
Yesterday I flashed my Mi 8 to get root permissions with Global V10.2.1.0 with Magisk 17.3, including Disable DM-Verity and Force Encrypt. Everything was working perfect, Magisk notified me about updating to v18, so I did, and MIUI notified me about an update (if I'm not mistaken, for 10.2.2.0).
MIUI downloaded the update and asked me to reboot to install it. It booted into TWRP and did the whole installation, apparently without issues, but then I restarted and it goes straight to TWRP.
I tried clearing cache/dalvik but nothing.
Every time I reboot and gets to TWRP, when I press the menu button to see the log, the last lines say:
Full SELinux support is present.
set_policy_failed:/datamisc
I don't know if this is relevant, but seeing a "failed" is not nice.
As an observation, the folder /data/system is full of folders, but the /system directly in root folder only has /usr/share/zoneinfo (I don't know if this is normal or not),
If the system updated to 10.2.2.0, would flashing to 10.2.1.0 set the ARB or it's safe for me to flash it again? Any ideas?
Thanks!

You need to flash Magisk again. Installing an OTA means you flash the stock boot.img so flash dm verity and magisk.

ArmedandDangerous said:
You need to flash Magisk again. Installing an OTA means you flash the stock boot.img so flash dm verity and magisk.
Click to expand...
Click to collapse
Thanks for the answer! Do I need to wipe DATA too?
EDIT: I just flashed DM-Verity and then Magisk and all good. No need to wipe data. Thanks!!

TWRP gets replaced by stock recovery

So I've used TWRP r16 and it throws an "Image not signed or corrupt" error as suggested by other users I ignored it, but everytime I reboot to system and try to get to recovery "no command" show's up meaning TWRP was replaced by stock recovery all help will be appreciated.
Thanks

Akash731 said:
So I've used TWRP r16 and it throws an "Image not signed or corrupt" error as suggested by other users I ignored it, but everytime I reboot to system and try to get to recovery "no command" show's up meaning TWRP was replaced by stock recovery all help will be appreciated.
Thanks
Click to expand...
Click to collapse
You need to flash Magisk after flashing TWRP
1. Flash Latest TWRP
2. Reboot to TWRP
3. Flash Magisk
If you boot in to system after flashing TWRP, TWRP will be removed

pradeeppk said:
You need to flash Magisk after flashing TWRP
1. Flash Latest TWRP
2. Reboot to TWRP
3. Flash Magisk
If you boot in to system after flashing TWRP, TWRP will be removed
Click to expand...
Click to collapse
Hey thanks that worked.
But everytime I boot to system and boot to twrp the data gets encrypted and I can't access the files do you happen to know any solution for this?

Akash731 said:
Hey thanks that worked.
But everytime I boot to system and boot to twrp the data gets encrypted and I can't access the files do you happen to know any solution for this?
Click to expand...
Click to collapse
If you are on stock Rom, according to my knoweldge it is not possible to remove encryption, if you format your date in twrp for removing encryption then reboot to system you can see that the phone is again encrypted.
But in custom roms this doesnt happen.

pradeeppk said:
You need to flash Magisk after flashing TWRP
1. Flash Latest TWRP
2. Reboot to TWRP
3. Flash Magisk
If you boot in to system after flashing TWRP, TWRP will be removed
Click to expand...
Click to collapse
pradeeppk said:
If you are on stock Rom, according to my knoweldge it is not possible to remove encryption, if you format your date in twrp for removing encryption then reboot to system you can see that the phone is again encrypted.
But in custom roms this doesnt happen.
Click to expand...
Click to collapse
I don't want to try custom rom's as this is my main device guess I'm stuck with the encryption then thanks for your help. :good:
Edit:-
Tried TWRP r20 it decrypts fine thanks

pradeeppk said:
You need to flash Magisk after flashing TWRP
1. Flash Latest TWRP
2. Reboot to TWRP
3. Flash Magisk
If you boot in to system after flashing TWRP, TWRP will be removed
Click to expand...
Click to collapse
You don't have to flash Magisk after flashing TWRP. The two are unrelated.
After flashing TWRP you have to boot into recovery, not system. Once TWRP was started, you can reboot into system. No need for Magisk (unless you want Magisk anyway).

gewe said:
You don't have to flash Magisk after flashing TWRP. The two are unrelated.
After flashing TWRP you have to boot into recovery, not system. Once TWRP was started, you can reboot into system. No need for Magisk (unless you want Magisk anyway).
Click to expand...
Click to collapse
It will not work in stock ROM, if you flash a custom rom there is no need to flash Magisk.
You should flash Magisk or custom kernel after flashing TWRP otherwise it will be erased.
Google about TWRP erasing after reboot you should get too many posts regarding this
This is one of them
https://forum.xda-developers.com/oneplus-3t/help/twrp-deleted-booting-t3769867

pradeeppk said:
It will not work in stock ROM, if you flash a custom rom there is no need to flash Magisk.
You should flash Magisk or custom kernel after flashing TWRP otherwise it will be erased.
Google about TWRP erasing after reboot you should get too many posts regarding this
This is one of them
https://forum.xda-developers.com/oneplus-3t/help/twrp-deleted-booting-t3769867
Click to expand...
Click to collapse
I am using stock ROM, and yes, also Magisk (installed later). IIRC Magisk is not needed for TWRP to work. When I receive the next OTA notification, I will test this.
The thread you are referring to is for a OnePlus 3T. For our device this is the thread: https://forum.xda-developers.com/moto-g5s-plus/development/recovery-twrp-3-1-1-r7-t3694910.
Since there is no official TWRP for the Moto G5S Plus, I took the following text from the TWRP page for the Moto G5S.
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Click to expand...
Click to collapse
Instead of that you can also use fastboot reboot-bootloader, and then from the bootloader start recovery.

pradeeppk said:
It will not work in stock ROM, if you flash a custom rom there is no need to flash Magisk.
You should flash Magisk or custom kernel after flashing TWRP otherwise it will be erased.
Google about TWRP erasing after reboot you should get too many posts regarding this
This is one of them
https://forum.xda-developers.com/oneplus-3t/help/twrp-deleted-booting-t3769867
Click to expand...
Click to collapse
Two days ago I received a notification for an OTA update, containing the August 2019 security patches.
After going back to stock ROM, installing all the updates up to the latest, I installed TWRP. After booting into recovery, and then into system, and recovery again, TWRP was gone. Strange, I don't remember this happening before. Maybe I always installed Magisk before booting into system.
Bottom line: you were right, I was wrong. Thanks for pointing it out.

gewe said:
Two days ago I received a notification for an OTA update, containing the August 2019 security patches.
After going back to stock ROM, installing all the updates up to the latest, I installed TWRP. After booting into recovery, and then into system, and recovery again, TWRP was gone. Strange, I don't remember this happening before. Maybe I always installed Magisk before booting into system.
Bottom line: you were right, I was wrong. Thanks for pointing it out.
Click to expand...
Click to collapse
As like you said this is the first time in my life i need to flash magisk to stick twrp.
I usualy doesn't use root or custom roms, install twrp, remove unnecessary apps from stock system, replace host files with adaway hosts, replace or edit gps config files. and continue using stock.
This is the main routine from Android 1.5
(Samsung spica (i think it was the first Android phone from Samsung)).
It may be due to security reason stock kernel or system delete twrp.
When installing magisk it patch stock boot image, that may be the reason of twrp remains after flashing magisk.

Working TWRP for Mi9T Pro on Android 10 (QFKEUXM) **SOLVED**

Now that we have finally got the update in the EU region I want to know if anyone has successfully flashed TWRP or any other recovery?
In case anyone wondering I have managed to get root with the latest magisk via patched boot image method.
**UPDATE**
I flashed the latest TWRP from this thread and all went smoothly. Also managed to get Viper4android working which was my biggest concern coming from Android 9. Happy days :victory:

_ray_ said:
Now that we have finally got the update in the EU region I want to know if anyone has successfully flashed TWRP or any other recovery?
In case anyone wondering I have managed to get root with the latest magisk via patched boot image method.
Click to expand...
Click to collapse
I'm currently on MIUI 10.3.4.0 Stable with OrangeFox Recovery installed, Going to attempt updating later since, afaik, OrangeFox has Support for OTA Updates.

Fatal_Scythe said:
I'm currently on MIUI 10.3.4.0 Stable with OrangeFox Recovery installed, Going to attempt updating later since, afaik, OrangeFox has Support for OTA Updates.
Click to expand...
Click to collapse
Good luck and please do post back the results :good:

Fatal_Scythe said:
I'm currently on MIUI 10.3.4.0 Stable with OrangeFox Recovery installed, Going to attempt updating later since, afaik, OrangeFox has Support for OTA Updates.
Click to expand...
Click to collapse
Waiting for your feedback, because my orangefox is ready for OTAs but i think because i forgot to check DM VERITY and FORCED ENCRYPTION it asks for password when rebooting for update and ruins it...this is my guess. So please share your feedback and it you checked the 2 options unlike me.
Sent from my Redmi K20 Pro using Tapatalk

I'm also interested in this. I want to keep TWRP and magisk post-upgrade to Android 10

I updated with no issued with the following steps:
1. Installed latest TWRP from here https://forum.xda-developers.com/k20-pro/development/recovery-unofficial-twrp-xiaomi-redmi-t3944363
2. Download latest Magsik
3. Download recovery zip for miui 11 rom
4. Reboot to recovery
5. Install rom zip ( do not reboot after install)
6. Install Magsik
7. Install TWRP img via recovery that you downloaded in step 1
8. Reboot into TWRP
9. Reboot to system

_ray_ said:
Good luck and please do post back the results :good:
Click to expand...
Click to collapse
ishaqtkr said:
Waiting for your feedback, because my orangefox is ready for OTAs but i think because i forgot to check DM VERITY and FORCED ENCRYPTION it asks for password when rebooting for update and ruins it...this is my guess. So please share your feedback and it you checked the 2 options unlike me.
Click to expand...
Click to collapse
Okay so, coming from 10.3.4.0 Stable, OFox Recovery and encrypted, the update ran through fine without any problems. Since I'm encrypted I had to enter my password first but after that it started installing the Update. as far as I remember, I've seen that Orangefox's script that prevents Orangefox from being overwritten after every update (it's called OTA.bak I think) already handles both DM-Verity and Force-Encrypt on it's own, at least I didn't had to take any further steps regarding Encryption and such stuff and after updating it booted into MIUI 11 just fine (which ofc since it's an Major Update took a little longer than usual but at least it eventually did)

desiresiscool said:
I updated with no issued with the following steps:
1. Installed latest TWRP from here https://forum.xda-developers.com/k20-pro/development/recovery-unofficial-twrp-xiaomi-redmi-t3944363
2. Download latest Magsik
3. Download recovery zip for miui 11 rom
4. Reboot to recovery
5. Install rom zip ( do not reboot after install)
6. Install Magsik
7. Install TWRP img via recovery that you downloaded in step 1
8. Reboot into TWRP
9. Reboot to system
Click to expand...
Click to collapse
So what do you do when you're on 10.3.4 pfkeuxm Rom and running with twrp and magisk installed?
Can't I install the miui 11 rom via twrp and then immediately flash magisk again?

Following the advice here, I've got the update installed with twrp and magisk working fine. The only problem I have is that I can't read/write the system partition so titanium backup isn't working. Any ideas how I could fix it?

Boot loop problem after updating magisk module.

Hello everyone,
Today I had a notification telling me that there is a new version of both magisk manager and module. Therefore I first updated the manager successfully and proceeded to update the module through in-app flash. After the flash completed, app prompted me to reboot. However, the reboot process never finished and the phone got stuck while booting. Since then I only tried factory reset which only booted the phone to let me enter my sim card password but after that, it rebooted itself to boot loop again. Some info about the phone:
TWRP installed and still working,
Latest xiaomi.eu from that won't boot anymore,
Only viper4droid and youtube vanced modules were installed.
AdAway for obvious reasons.
and that's it. Now I am planning on flashing crdroid ROM to make the phone work again but the installation process requires me to do:
Flash MIUI11 eea with miflash : min V11.0.8.0.QFAEUXM note : if already on v11.08.0 there's no need to redo
Flash vbmeta.img with "fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification" note : if already done there's no need to redo
Flash TWRP in fastboot and boot into TWRP
Click to expand...
Click to collapse
is there a step that I should skip? It's been 6 months since I handled the initial process to be able to flash xiaomi.eu from therefore I don't remember how I exactly did that as I have only been OTA updating the from since then. I don't remember or know how to flash V11.0.8.0.QFAEUXM nor vbmeta.img nor TWRP. I don't even know if I "should" flash those. I am open to any different suggestions or help to let me achieve my goal of flashing crdroid to get out of this mess.
Thanks in advance!