[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] pfavayi:
==

There is some miss information here.

You can check your DFE zip to make sure what its doing....

==

This is not misinformation. Where did you see any misinformation ? please copy/ paste it here.

I always check the contents of DFE files and that's why I came to the conclusion that many of them are more likely malware than legitimate files.

==

This .zip I have attached does exactly what you're saying and I would have to argue it's a better implementation of your method. Also its only 177.6 KB, not 4.5MB.

see fix.sh in TMP directory of zip

==

I looked at the zip.

Besides fix.sh, there is the updater-script and the updator-binary. You cannot read the contents of the updater-binary.

Why do you need an updater binary? cant you execute the script from the shell? That becomes suspicious to me.

It's not a better implementation of my method. it's an automatic implementation of my method with the possibility of introducing malware just like with any other DFE script.

The effect that its smaller in size is a good sign but that's doesn't eliminate the possibility that it is malware.

And if you think it's a hassle to do things manually -well, I guess mannual is not for you.

==

It also checks for three keywords not just one to change to "encryptable"

==

The other words are not necessary for the pocophone F1 and they don't exist in the pocophone F1 fstab.qcom. this is a script so it covers anything possible even if it's not probable.

==

You don't need to go through all that hassle when you can just flash this after vendor,

==

This is true for any DFE file out there... which is what I am trying to avoid. You can just flash any DFE file and you don't have to do anything manually.

==

this zip accomplishes the exact same thing you purposed but better and more thoroughly...

==

What does it's do better? It just changes forceencrpt to encryptable, just like I can do manually.

It's one word you are changing - what thoroughness are you looking for?

==

But I think its silly to have Magisk bundled with DFE, that makes no sense to me this one does NOT have that

==

Maybe so...

But that's why you have to look into the script and see what it does... you may not understand everything but you can get a pretty good idea. Of course you will not have any idea when it comes to the binary bundled with the script.

You should ask the author of the the script why they included magisk.

And that's why my manual method is clean clear and malware free...

But if someone hates doing things manually I suppose they can hunt around for the many DFE scripts available.

Edit:

I changed to AOSiP for the moment and I have vendor firmware 9.2.25.

My phone is not encrypted. I downloaded and installed firmware 9.3.7, looked at fstab.qcom and saw that it had not changed ( I had edited when I installed 9.2.25). I successfully booted it into my rom. ( no boot loops or freezes) . If I wasn't doing things manually I would live installed DFE I gained.

---------- Post added at 09:24 PM ---------- Previous post was at 09:19 PM ----------

Flash any DFE file you want. They range in size from about 200k to 5mb. Over 80% of them are malicious. You might be lucky and find a file in the 20%.

When you do it manually there is 0% chance of you getting malware.

But I suppose it depends on the person. I just gave an alternative.

---------- Post added at 09:26 PM ---------- Previous post was at 09:24 PM ----------

I have never posted anything separately.... I really have to Google to find out how - unless you want to provide the link.

The method is valid. I was testing all this weekend.

---------- Post added at 09:30 PM ---------- Previous post was at 09:26 PM ----------

Of course you can ...

They are many DFE files ranging in size from 200k to 5 mb. Choose any one you want and install it.

The chances you'll get a virus or some other form of malware with one of those files is 80%. Take your chances.

I provide an alternative Manual method that is 100% free of malware.