sorryDidn't change there anything. But I've tried now and that makes no difference.
I have only installed CrDroid, FlameGapps Basic and FlameGapps Search Addon.
No Magisk and no custom kernel...
Very strange thing...

sorryDidn't change there anything. But I've tried now and that makes no difference.
I have only installed CrDroid, FlameGapps Basic and FlameGapps Search Addon.
No Magisk and no custom kernel...
Very strange thing...
@Pumpino Thank You So Much...Do you mean that you can't boot the phone normally or just that you can't access recovery anymore?
Either way, if you can't access recovery, you'll need to turn off your phone and then start it in fastboot mode by holding the volume down and power buttons together until the fastboot logo appears. Then, from your computer, flash TWRP by entering fastboot flash recovery <twrp.img>. from the command line. You replace twrp.img with the filename of TWRP. You can download the latest TWRP from https://androidfilehost.com/?w=files&flid=329007&sort_by=date&sort_dir=DESC. Once you've done that, enter fastboot boot <twrp.img>.
I faced the same issue.Phone kept flashing twrp screen after flashing this ROM, what should I do I tried using Mi Flash Tool but this error kept popping up
View attachment 5614941
Can u please tell which version are u talking about I'm having a similar bootloop issue after flashing latest twrp IMG@Pumpino Thank You So Much...
The latest TWRP that you shared solved the issue.
Download the latest twrp-3.6.1_11-2-surya-22.05-fix.img from the link belowCan u please tell which version are u talking about I'm having a similar bootloop issue after flashing latest twrp IMG
hello @brigudav, please see this post and comment there or here on the new feature 'fake encryption' marked as (1) in the screenshot. what does it actually do? would i remain 'not encrypted' after using that feature? can it be used to avoid detection in momo, e.g.
Hi. It's just that many users turn off forced encryption, and "Fake encryption" will install a module for Magisk, which adds a flag to system.prop to falsely enable encryption. And the system thinks that encryption is enabled.hello @brigudav, please see this post and comment there or here on the new feature 'fake encryption' marked as (1) in the screenshot. what does it actually do? would i remain 'not encrypted' after using that feature? can it be used to avoid detection in momo, e.g.
btw, i used the options in (2) to first disable and the next time remove the last installed module, saving me from bootlop on both occasions. many thanks. when you release newer versions of twrp, it'd be nice if you give a small description about what the newly added features do. keep up the good work.![]()
thank you for your reply. i'm very wary of this encryption apsect; hence a few questions:Hi. It's just that many users turn off forced encryption, and "Fake encryption" will install a module for Magisk, which adds a flag to system.prop to falsely enable encryption. And the system thinks that encryption is enabled.
1: I believe you still have to flash the zip that disables encryption. The feature in the recovery just makes sure that the system thinks it is encrypted.thank you for your reply. i'm very wary of this encryption apsect; hence a few questions:
i) can i use this feature and actually be 'not encrypted'?
ii) is it that settings > security > encryption & credentials would show the phone is encrypted, but twrp would still display all files/folders cleanly?
iii) any precautions to take before using the feature? does one have to remove passwords/fingerprints beforehand?
iv) can it be used to avoid detection in momo, e.g.
v) how to revert the changes, if required?
folks who have used this feature, please share your knowledge/experience.
p.s.: i'd like to stay 'not encrypted'.
1 & 3 are worrisome. 5. how to disable fake encryption?1: I believe you still have to flash the zip that disables encryption....
3: You have to format data so everything will be gone anyway.....
5: ....If you want to disable fake encryption that's easy enough, but to actually encrypt your phone....
Are you currently encrypted? If yes then you have no choice but to delete everything and start over and this time flash dfe before booting. Using the feature in the recovery you then fake the encryption. To disable it is as simple as disabling the magisk module associated with the feature. And of course you'll stay unencrypted.1 & 3 are worrisome. 5. how to disable fake encryption?
i'm eager to try this recovery feature to see if i can avoid detection in momo. but, i wish i could hear from @brigudav (he's the author of the script/module, after all) on the procedure to be followed to use the feature and actually stay 'not encrypted'.
Hi. It's just that many users turn off forced encryption, and "Fake encryption" will install a module for Magisk, which adds a flag to system.prop to falsely enable encryption. And the system thinks that encryption is enabled.hello @brigudav, please see this post and comment there or here on the new feature 'fake encryption' marked as (1) in the screenshot. what does it actually do? would i remain 'not encrypted' after using that feature? can it be used to avoid detection in momo, e.g.
btw, i used the options in (2) to first disable and the next time remove the last installed module, saving me from bootlop on both occasions. many thanks. when you release newer versions of twrp, it'd be nice if you give a small description about what the newly added features do. keep up the good work.![]()
he has uploaded new mod version (common?) for A11 and 12.1.... dev (brigudav) appears to have deleted all of the files....
hello @brigudav, please see this post and comment there or here on the new feature 'fake encryption' marked as (1) in the screenshot. what does it actually do? would i remain 'not encrypted' after using that feature? can it be used to avoid detection in momo, e.g.
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned