Develop Bugs

Need a little help, please ....

I rebooted in to recovery (B partition) from custom ROM , ran Migrator Magisk module twice (as directions say-second run does FDR), booted into A partition of my Pixel XLto flash new ROM and for some reason EVERYTHING is encrpyted (do not have screen lock or pin applied) ..... I remember seeing something like this when I first got the device but cant recall how to deal with it.
Every attempt to adb sideload, adb push , etc not working ....

C.Hatfield said:
I rebooted in to recovery (B partition) from custom ROM , ran Migrator Magisk module twice (as directions say-second run does FDR), booted into A partition of my Pixel XLto flash new ROM and for some reason EVERYTHING is encrpyted (do not have screen lock or pin applied) ..... I remember seeing something like this when I first got the device but cant recall how to deal with it.
Every attempt to adb sideload, adb push , etc not working ....
Click to expand...
Click to collapse
So, I take it you were trying to 'migrate' to another ROM?
My suggestion is this, use this guide: https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-9-0-pie-unlock-t3825866/
- Start fresh
- Do #4 'wipe data'

was just using the magisk migrator module - it backed up all my files on 1st run, then 2nd run it did FDR .... I would REALLY prefer not wiping my internal/sdcard ..... everything is still there but encrypted, unusable for the moment - hoping there is a workaround bc Ihave sooo much data that I havent backed up externally/cloud for a month or 3 .... got nothing I can boot from as well as no access to ALL the tons of stuff stored on my phone to flash .... was thinking to use Factory image but removing the [-w] from the bat file ..... would that work to keep my data integrity ?

Honestly, im wondering how things got encrypted when the process (xc for what im unsure the mod did extra besides FDR) is practically, if not identical, to the normal protocol for wiping>flashing for PIXEL XL

C.Hatfield said:
was just using the magisk migrator module - it backed up all my files on 1st run, then 2nd run it did FDR .... I would REALLY prefer not wiping my internal/sdcard ..... everything is still there but encrypted, unusable for the moment - hoping there is a workaround bc Ihave sooo much data that I havent backed up externally/cloud for a month or 3 .... got nothing I can boot from as well as no access to ALL the tons of stuff stored on my phone to flash .... was thinking to use Factory image but removing the [-w] from the bat file ..... would that work to keep my data integrity ?
Click to expand...
Click to collapse
...would that work to keep my data integrity ? Yes

will the modded flash-all.bat actually work with all the contents of the internal drive being encrypted?
I only ask bc of all the research Ive been doing for the last 4 hours, I had no idea that the current TWRP [3.2.3.1] made decryption on PIe possible .... I not ref to the PIN/lockscreen/Fingerprint decrypt either > more like decrypting the System partition like with Shamu/N6
**Also** found this during my harried research:
Encrypting does not completely delete the files, but the factory reset process gets rid of the encryption key. As a result, the device has no way it can decrypt the files and, therefore, makes data recovery extremely difficult.

C.Hatfield said:
will the modded flash-all.bat actually work with all the contents of the internal drive being encrypted?
I only ask bc of all the research Ive been doing for the last 4 hours, I had no idea that the current TWRP [3.2.3.1] made decryption on PIe possible .... I not ref to the PIN/lockscreen/Fingerprint decrypt either > more like decrypting the System partition like with Shamu/N6
**Also** found this during my harried research:
Encrypting does not completely delete the files, but the factory reset process gets rid of the encryption key. As a result, the device has no way it can decrypt the files and, therefore, makes data recovery extremely difficult.
Click to expand...
Click to collapse
Yes!
Yes, twrp-3.2.3-1 decrypts.
"**Also** found this during my harried research:
Encrypting does not completely delete the files, but the factory reset process gets rid of the encryption key. As a result, the device has no way it can decrypt the files and, therefore, makes data recovery extremely difficult."
Where did you find that? Link please.

Homeboy76 -
Very much appreciate the feedback !! This is the longest downtime I've experienced, likely-ever but I just couldn't make another move until I was certain it was the correct one.
Here is the link where I found the above info you asked about:
https://android.stackexchange.com/questions/149219/android-decrypt-sd-card-after-factory-reset?rq=1

C.Hatfield said:
Homeboy76 -
Very much appreciate the feedback !! This is the longest downtime I've experienced, likely-ever but I just couldn't make another move until I was certain it was the correct one.
Here is the link where I found the above info you asked about:
https://android.stackexchange.com/questions/149219/android-decrypt-sd-card-after-factory-reset?rq=1
Click to expand...
Click to collapse
Edit: Wrong link, it happens.

this is what it shows me:
It is in the default factory reset state ( like a new device ). You can't decrypt the device even if you wish to as the encryption password (generated from a combination of user lock screen PIN and encryption algorithm ) is lost
From Android's Factory Reset Does Not Wipe Your Data: Here's The Solution
Encrypting does not completely delete the files, but the factory reset process gets rid of the encryption key. As a result, the device has no way it can decrypt the files and, therefore, makes data recovery extremely difficult.

C.Hatfield said:
this is what it shows me:
It is in the default factory reset state ( like a new device ). You can't decrypt the device even if you wish to as the encryption password (generated from a combination of user lock screen PIN and encryption algorithm ) is lost
From Android's Factory Reset Does Not Wipe Your Data: Here's The Solution
Encrypting does not completely delete the files, but the factory reset process gets rid of the encryption key. As a result, the device has no way it can decrypt the files and, therefore, makes data recovery extremely difficult.
Click to expand...
Click to collapse
Yes, if you use this url: https://www.techtimes.com/amp/artic...oes-not-wipe-your-data-heres-the-solution.htm but that is not the url that was in your previous post. This is, https://android.stackexchange.com/questions/149219/android-decrypt-sd-card-after-factory-reset?rq=1
I think it is out dated: Android's Factory Reset Does Not Wipe Your Data: Here's The Solution By Anu Passary | May 27, 2015 11:07 PM EDT

hey homeboy76 tried the flash-all bat [-w removed] and the process went through w/o any issues but it immediately rebooted itself and within 30 seconds landed on the stock recovery & it said file may be corrrupt, TRY AGAIN or FDR ....
Do I have any other recourse to save my 100 GBs of data ??? or do I onlly have the unmoddded flash-all -w to do at this point ?

C.Hatfield said:
hey homeboy76 tried the flash-all bat [-w removed] and the process went through w/o any issues but it immediately rebooted itself and within 30 seconds landed on the stock recovery & it said file may be corrrupt, TRY AGAIN or FDR ....
Do I have any other recourse to save my 100 GBs of data ??? or do I onlly have the unmoddded flash-all -w to do at this point ?
Click to expand...
Click to collapse
Did you check the SHA256 of the March 2019 factory image?
I don't think it would hurt to try again. If it doesn't work you can try FDR or flash-all with [ -w] both will erase your internal storage.

Homeboy76 said:
Did you check the SHA256 of the March 2019 factory image?
I don't think it would hurt to try again. If it doesn't work you can try FDR or flash-all with [ -w] both will erase your internal storage.
Click to expand...
Click to collapse
Soooo, check this out .... I finally got a flash-all {no -w] to work and my phone booted - buuuuut it is STILL ENCRYPTED .... opening the root//file explorer I was horrified to see that everything is still encrypted .... it's soooo bizarre. apps from PS are restoring but I cannot get screenshots to save nor can I move any files from my laptop to my Pixel Xl. I wanted screeenshots so bad to show/post this bizarreness but -no- ....
I havent tried to boot into recovery yet or anything else .... so I dont even have root to look any deeper into the partitions. I was wondering if Titanium Backup would run and populate with proper app names, etc
Any more ideas from this unprecedented point bro >? BTW, the SHA256 was good/clean/proper.
BTW, when you flash a factory image, which facking partition (A or B) -should it- be flashed to or flashed "from" - I've let myself get quite confused >???? I have researched & read sooo much, my brain hurts (& is literally fried) .... I figured I would ask you so I could possibly get some firsthand clarification.

C.Hatfield said:
Soooo, check this out .... I finally got a flash-all {no -w] to work and my phone booted - buuuuut it is STILL ENCRYPTED .... opening the root//file explorer I was horrified to see that everything is still encrypted .... it's soooo bizarre. apps from PS are restoring but I cannot get screenshots to save nor can I move any files from my laptop to my Pixel Xl. I wanted screeenshots so bad to show/post this bizarreness but -no- ....
I havent tried to boot into recovery yet or anything else .... so I dont even have root to look any deeper into the partitions. I was wondering if Titanium Backup would run and populate with proper app names, etc
Any more ideas from this unprecedented point bro >? BTW, the SHA256 was good/clean/proper.
BTW, when you flash a factory image, which facking partition (A or B) -should it- be flashed to or flashed "from" - I've let myself get quite confused >???? I have researched & read sooo much, my brain hurts (& is literally fried) .... I figured I would ask you so I could possibly get some firsthand clarification.
Click to expand...
Click to collapse
I can't help you with the file encrypted problem. I've never read about anything like the problem you're having with encryption. TB might work. If your files are backed up on your computer, FDR.

https://forum.xda-developers.com/showpost.php?p=79273902&postcount=481
@C.Hatfield, continuing the discussion...
Topics
1) Forced encryption
2) Output of ls /data/misc/vold/*
3) Advanced approach

VR25-
First, I'll start with a sincere Thank You - I know you're busy with school & life, so I appreciate that you take the time to create such beneficial tools like Migrator. Having used Android OS since it's inception, I've learned a whole lot & seen a whole lot buuut not this craziness. I was unable to get any actionable help within the 2 weeks that I held out doing a full FDR ....
alas, I finally relented & did a full FDR with a full on flash-all.bat & ironically, it was only a couple hours before your response. I didn't read the response until now because I was afraid you'd posted an A, B, C unencryption method for me - in a small way, I'm glad it isn't that lol ....
As for the "did you..." questions you asked in Migrator thread, I followed my usual protocol & did not vary at all, except running the Migrator script 2x's before trying to install new ROM.

no signal - a2lite 4gb

Hi,
I did something wrong with my A2 Lite, i've updated the Magisk boot file from the Magisk app. Caused my phone to stop booting Android.
So i tried reflashing it with Mi Flash in EDL mode. That worked but i don't have any signal when i put a SIM in.
It shows my provider in settings so it recognizes the SIM but doesn't do anything with it.
Tried 10.0.13.0 manually and via Mi Flash = no signal
Tried 10.0.2.0 via Mi Flash = no signal
Loaded TWRP, switch A/B = no effect
Does anyone have a clue what i can do now?
Looks like the IMEI numbers are 0.

terrorsource said:
Looks like the IMEI numbers are 0.
Click to expand...
Click to collapse
I don't know how you got here, but it looks like some important stuff was overwritten.
The mobile network is probably blocking you due to the invalid IMEI...
This is typically something that is stored only in the phone's flash. I'm not sure you'll be able to recover the phone.

a1291762 said:
I don't know how you got here, but it looks like some important stuff was overwritten.
The mobile network is probably blocking you due to the invalid IMEI...
This is typically something that is stored only in the phone's flash. I'm not sure you'll be able to recover the phone.
Click to expand...
Click to collapse
Is it possible to write back the IMEI's if i have them?

terrorsource said:
Is it possible to write back the IMEI's if i have them?
Click to expand...
Click to collapse
It might be. In theory. You'd need to know the format of whatever was overwritten.

You can't rewrite the IMEI, I've have that issue before and I created a guide on how to fix it
https://forum.xda-developers.com/mi...-to-fix-efs-corruption-sim-card-t3928910/amp/
Enjoy ?
You can download the latest rom and install it (ignore the rom that's in the guide it is outdated, but the rest of the guide stays the same).

Noam5651 said:
You can't rewrite the IMEI, I've have that issue before and I created a guide on how to fix it
https://forum.xda-developers.com/mi...-to-fix-efs-corruption-sim-card-t3928910/amp/
Enjoy
You can download the latest rom and install it (ignore the rom that's in the guide it is outdated, but the rest of the guide stays the same).
Click to expand...
Click to collapse
Thanks, will check it out the next couple of days.
I do see some websites/youtube video's of people/apps claiming it is possible by re-writing the QCN file...
I do know where i made a mistake, i tried to manually install all files in an image folder, including flashing a not-so-good QCN file...

terrorsource said:
Thanks, will check it out the next couple of days.
I do see some websites/youtube video's of people/apps claiming it is possible by re-writing the QCN file...
I do know where i made a mistake, i tried to manually install all files in an image folder, including flashing a not-so-good QCN file...
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a2-lite/how-to/sim-network-solution-alternatively-t3914161
if this doesn't work ,pm me

nikoman1987 said:
https://forum.xda-developers.com/mi-a2-lite/how-to/sim-network-solution-alternatively-t3914161
if this doesn't work ,pm me
Click to expand...
Click to collapse
Works partially!
I cannot install the latest "QPST_2.7.453" due to "Installation errors".
If i try "QPST_2.7.422" i can restore the created QCN but i cannot select "Enable Multi-SIM" and it only restores IMEI-1

nikoman1987 said:
https://forum.xda-developers.com/mi-a2-lite/how-to/sim-network-solution-alternatively-t3914161
if this doesn't work ,pm me
Click to expand...
Click to collapse
Works now! both IMEI's are now shown in the settings.
IMEI SV is still at 0 though.
Your manual needs some work though.
Latest QFI: https://androidmtk.com/download-qualcomm-flash-image-loader-qfil
Enable Multi-SIM is not in all versions. I've used v2.0.1.9
Restoring QCN with this version can take a while. DO NOT USE PC until done!
8. daisy_sprout:/ $ su
/system/bin/sh: su: not found
127|daisy_sprout:/ $ setprop sys.usb.config rndis,diag,adb
setprop: failed to set property 'sys.usb.config' to 'rndis,diag,adb'
16. is not "QPST.exe" but "QFIL.exe"
20. 21. 22. not needed. directly went to 23 from 19.
stopped at 27, rebooted phone, IMEI's are back. Did not proceed with the manual any further.

terrorsource said:
Works now! both IMEI's are now shown in the settings.
IMEI SV is still at 0 though.
Your manual needs some work though.
Latest QFI: https://androidmtk.com/download-qualcomm-flash-image-loader-qfil
Enable Multi-SIM is not in all versions. I've used v2.0.1.9
Restoring QCN with this version can take a while. DO NOT USE PC until done!
8. daisy_sprout:/ $ su
/system/bin/sh: su: not found
127|daisy_sprout:/ $ setprop sys.usb.config rndis,diag,adb
setprop: failed to set property 'sys.usb.config' to 'rndis,diag,adb'
16. is not "QPST.exe" but "QFIL.exe"
20. 21. 22. not needed. directly went to 23 from 19.
stopped at 27, rebooted phone, IMEI's are back. Did not proceed with the manual any further.
Click to expand...
Click to collapse
We'll I have never had an issue with losing my IMEI , the manual is not mine ,I'm glad that it worked!

No SIM recognition after OOS 10.0.1 update - EFS problem??

Hi,
I have my 5T rooted with Magisk and TWRP recovery.
I've upgrated from OOS 9 to official OOS 10.0.1 flashing with TWRP as usual. I did a full nandroid backup before.
Everything went fine until I noticed that during the booting of the phone after the flashing, it didn't ask for the SIM code as it used to. And once the mobile had fully restarted, I could see 2 new icons on top of the screen picturing the 2 sim cards that can be contained in a OnePLus 5T. They were striken through, as if not present, when I had My SIM in Slot 1. And so, no mobile signal, no data network.
I tried switching Sim cards with another mpbile. My SIM worked fine in the other mobile and the other SIM was not recognized by my mobile.
I've read that I could be facing problems of damaged EFS. So I tried restoring through TWRP the EFS partition from the Nandroid I had done before. Nothing. Same thing with the modem partition. Nothing.
I tried then to restore the EFS from a safety backup that I had using Fastboot. Nothing.
I could still try to restore the full nandroid backup done at the beginning, but I forgot to take out pin protection code before taking the Nandroid, and I've read somewhere that it could be an issue after restoring the system. I might not be able to restart the phone and be obliged to factory reset, witch I would really like to avoid. And anyway, if restoring with Fastboot did not work, I wonder if the full restore would change anything.
Anyway, anybody has a magic idea about might be happening? A little help please??

Same problem!
I'm having the same problem. I have my 5T rooted with Magisk and TWRP recovery.
I've upgrated from OOS 9 to official OOS 10.0.1 flashing with TWRP as usual. I did a full TWRP backup before, including my EFS partition.
I'm seeing this too:
>"once the mobile had fully restarted, I could see 2 new icons on top of the screen picturing the 2 sim cards that can be contained in a OnePLus 5T. >They were striken through, as if not present, when I had My SIM in Slot 1. And so, no mobile signal, no data network."
I did the same thing and had the same no result.
>I've read that I could be facing problems of damaged EFS. So I tried restoring through TWRP the EFS partition from the Nandroid I had done >before. Nothing. Same thing with the modem partition. Nothing.
I'm looking for a solution too.
I came across this: https://forum.xda-developers.com/oneplus-5t/help/baseband-imei-lost-t3834334 and this: https://www.getdroidtips.com/how-to-repair-and-fix-imei-baseband-on-oneplus-5t-a5010/
I've been reluctant to try and rebuild the QCN file, but it might work.

Working on this
So I'm working on reprogramming the IMEI using the Qualcomm tools. I was able to use them to back up my phone and see the it still has the correct MEID.
However, the .gcn file linked to below isn't accepted, with a weird error: "The file model MSM8998 does not match the phone model MSM8998. Please select a file for the MSM8998."
I'm not sure what it isn't liking. In theory, I think I could just put the IMEI numbers into the QPST programming tool, but I'm not certain where they would go and the correct format for them (with the chksm at the end or not?).
This is as far as I've gotten. I'm looking for an alternate .qcn or .qcnx (which is the kind the tool generates when saving files).
rootlessabroad said:
I'm having the same problem. I have my 5T rooted with Magisk and TWRP recovery.
I've upgrated from OOS 9 to official OOS 10.0.1 flashing with TWRP as usual. I did a full TWRP backup before, including my EFS partition.
I'm seeing this too:
>"once the mobile had fully restarted, I could see 2 new icons on top of the screen picturing the 2 sim cards that can be contained in a OnePLus 5T. >They were striken through, as if not present, when I had My SIM in Slot 1. And so, no mobile signal, no data network."
I did the same thing and had the same no result.
>I've read that I could be facing problems of damaged EFS. So I tried restoring through TWRP the EFS partition from the Nandroid I had done >before. Nothing. Same thing with the modem partition. Nothing.
I'm looking for a solution too.
I came across this: https://forum.xda-developers.com/oneplus-5t/help/baseband-imei-lost-t3834334 and this: https://www.getdroidtips.com/how-to-repair-and-fix-imei-baseband-on-oneplus-5t-a5010/
I've been reluctant to try and rebuild the QCN file, but it might work.
Click to expand...
Click to collapse

Hi
I've found a code (*#06#) in a page that gives you the MEID. It worked for me. Hopefully, I have the correct MEID too. The code for the IMEI did not show anything. I'll check the lynks you posted later today.
Thanks for sharing!!
PS. I can not include the lynk to codes page as I'm too junior a member and XDA forums won't let me.
rootlessabroad said:
So I'm working on reprogramming the IMEI using the Qualcomm tools. I was able to use them to back up my phone and see the it still has the correct MEID.
However, the .gcn file linked to below isn't accepted, with a weird error: "The file model MSM8998 does not match the phone model MSM8998. Please select a file for the MSM8998."
I'm not sure what it isn't liking. In theory, I think I could just put the IMEI numbers into the QPST programming tool, but I'm not certain where they would go and the correct format for them (with the chksm at the end or not?).
This is as far as I've gotten. I'm looking for an alternate .qcn or .qcnx (which is the kind the tool generates when saving files).
Click to expand...
Click to collapse

So I've tried te rebuild the QCN file. But my issue is that I can't make the ADB comunicate with my mobile. It is as the mobile was not plugged in?? The usb debugging is activated. I can browse the mobile memory from the computer. But the ADB doesn't lynk with the mobile; when you type adb devices, it says List of devices attached and nothing after. Any idea what might be happening?
What about you rootlessabroad? could you fix it?
rootlessabroad said:
So I'm working on reprogramming the IMEI using the Qualcomm tools. I was able to use them to back up my phone and see the it still has the correct MEID.
However, the .gcn file linked to below isn't accepted, with a weird error: "The file model MSM8998 does not match the phone model MSM8998. Please select a file for the MSM8998."
I'm not sure what it isn't liking. In theory, I think I could just put the IMEI numbers into the QPST programming tool, but I'm not certain where they would go and the correct format for them (with the chksm at the end or not?).
This is as far as I've gotten. I'm looking for an alternate .qcn or .qcnx (which is the kind the tool generates when saving files).
Click to expand...
Click to collapse

Wait until your device is fully rebooted before opening apps [REWARDED]

Hello friends!
I need a lot help.
If I fail to repair the operating system and work as before, I am impetuously interested in recovering at least the data on the /sdcard (internal phone storage) because I HAVE NO BACKUP and I need that data lke the air.
I have a Xiaomi Redmi Note 8 (Ginkgo) with stock ROM MIUI India/Global (11.0.6.0.PCOINXM), TWRP (3.3.1.0) and Magisk (v20.1 or 20.3 - I don't remember exactly).
About two days ago Revolut no longer allowed me to use the application because the phone is rooted. I needed to make an immediate transfer, so I started playing with Magisk because it didn't pass the SafetyNet test. Until then I had installed only Magisk, I updated to the latest version v21.2, I also installed two modules: MagiskHide Props Config (latest version) and Universal SafetyNet Fix v1.1.0. Plus the latest version of TWRP (3.5.0_9-0).
After running "props" in the terminal, I followed the steps (1, f, Xiaomi, 71 ...) and selected my phone from the list I managed to pass the SafetyNet test, but Revolut still did not work.
After that I tried to disguise the Magisk application with another name to hide it (that's how I saw it through some tutorials), but without success because I didn't activate install applications via USB (something like that).
I left the phone for about half an hour, and then the PROBLEMS BEGUN.
For each application I want to launch I receive the following message "wait until your device is fully rebooted before opening apps". I restarted the phone countless times and nothing. I noticed that TWRP does not decrypt user 0 or 999, so I changed TWRP to the previous version, uninstalled Magisk, deleted the modules from /data/adb/modules, upgraded to MIUI v11.0.6.0 and then MIUI v12.0.1.0 - and the problem persists.
I mention that using TWRP File Manager all the content from /data/data and /sdcard is encrypted (files and folders have unintelligible names). The rest of the files are ok.
Although developer mode is enabled, I don't have USB debugging enabled, and the default USB connection is set to charging and as I constantly get the error "wait until your device is fully rebooted before opening apps" I can't change them.
When I open the phone, at the lockscreen, I have a pattern that I successfully insert and the phone opens. The same pattern in TRWP does not decrypt the data.
Given the fact that it accepts the pattern password, I think that if I had a USB connection I would have managed to recover decrypted content from the internal storage space of the phone. Or is the error I receive exactly due to the fact that the applications no longer have access to the content because it is encrypted?
If so how can I recover all the encryption keys to backup them and then how can I try to fix this problem? Or if the keys have been altered, can they still be generated again (if the phone is the same, as well as the IMEI or serial number, etc)?
I understand that if I solve this problem I will either recover my phone as before or at least I can decrypt and access the data and make a backup.
It is very frustrating to see that the necessary information is still there, but I cannot access it.
Because I have access to the system with TWRP, I think I can attach logs.
I hope no one feels offended, but I am so desperate that I am willing to pay a reward.
Please help me!

Here is my video for a better understanding.
https://www.dropbox.com/s/ob235116jpnbj/ginkgo.mp4?dl=0

When I used MagiskHide, it changed my default.prop
Is it possible that the above problem is due to this fact?
How can I copy default.prop (original from wife's phone - same model) from SD card to phone?
Nothing changes with TWRP File Manager copy/paste. Can a script be used to be flashed with TWRP?

Any prop changes that were made with MagiskHide or MagiskHide Props Config did not touch any of your actual prop files. Your default.prop (and any other prop files) are going to be exactly as they were before enabling MagiskHide or changing prop values with MagiskHide Props Config.
Magisk does these things systemlessly, which means it doesn't actually alter the files. This (default.prop) is not your issue... How did you come to the conclusion that Magisk had changed your prop file anyway?
Since you've uninstalled Magisk and the modules, and even updated your OS and the problem still persists it is unlikely that it's directly related to Magisk. I know very little of MIUI though, so I'll leave the rest of the troubleshooting to those that do.

Thanks for the help and for the reply!

Didgeridoohan said:
Any prop changes that were made with MagiskHide or MagiskHide Props Config did not touch any of your actual prop files. Your default.prop (and any other prop files) are going to be exactly as they were before enabling MagiskHide or changing prop values with MagiskHide Props Config.
Magisk does these things systemlessly, which means it doesn't actually alter the files. This (default.prop) is not your issue... How did you come to the conclusion that Magisk had changed your prop file anyway?
Since you've uninstalled Magisk and the modules, and even updated your OS and the problem still persists it is unlikely that it's directly related to Magisk. I know very little of MIUI though, so I'll leave the rest of the troubleshooting to those that do.
Click to expand...
Click to collapse
I see a difference between my file and my wife's, although the phones are identical and had the same version of the operating system.
Originel - ro.bootimage.build.fingerprint=xiaomi/ginkgo/ginkgo:9/PKQ1.190616.001/V11.0.2.0.PCOINXM:user/release-keys
Actual - ro.bootimage.build.fingerprint=Xiaomi/omni_ginkgo/ginkgo:16.1.0/PQ3B.190801.002/5:eng/test-keys
Maybe I'm wrong, I'm trying different options...
In the end, I'm only interested in being able to access the decrypted content from /data and /sdcard (the internal phone storage) to backup them. Later I will reinstall everything.
Please help me with some tips, ideas, what else can I do?

If I reinstall the same version of MIUI, TWRP and use the same pattern can I decrypt the data (If I finally manage to backup them).

I'm already trying without success for about 2 days, do you think there is any chance to recover the DATA and/or internal storage (most important)?
Or to transfer it encrypted and then set the same pattern and eventually restore the data after I format and reinstall everything?
If I reinstall the same version of MIUI, TWRP and use the same pattern can I decrypt the data?

Adi H. said:
I see a difference between my file and my wife's, although the phones are identical and had the same version of the operating system.
Originel - ro.bootimage.build.fingerprint=xiaomi/ginkgo/ginkgo:9/PKQ1.190616.001/V11.0.2.0.PCOINXM:user/release-keys
Actual - ro.bootimage.build.fingerprint=Xiaomi/omni_ginkgo/ginkgo:16.1.0/PQ3B.190801.002/5:eng/test-keys
Maybe I'm wrong, I'm trying different options...
In the end, I'm only interested in being able to access the decrypted content from /data and /sdcard (the internal phone storage) to backup them. Later I will reinstall everything.
Please help me with some tips, ideas, what else can I do?
Click to expand...
Click to collapse
That fingerprint wasn't set by Magisk... Looks to me like you've been running a third-party/custom ROM and then didn't do a clean install of MIUI when going from the custom ROM. If so, that's a very likely source of the issues. I'm just guessing wildly though...

Didgeridoohan said:
That fingerprint wasn't set by Magisk... Looks to me like you've been running a third-party/custom ROM and then didn't do a clean install of MIUI when going from the custom ROM. If so, that's a very likely source of the issues. I'm just guessing wildly though...
Click to expand...
Click to collapse
Until 14.01.2021 when Revolut no longer worked on rooted phones, I had the MIUI India 11.0.2.0 version installed. Nothing else. Later in trying to make it work I kept switching between various official versions 11.0.2.0 / 11.0.6.0 and 12.0.1.0, flashed thru TWRP or Mi Flash (with save user data method).
It worked perfectly until I made those settings described in the original post. The problem is elsewhere, I think.

Based on the information in the attached file are the system encryption keys generated based on software or hardware?
Because if is hardware, I still have a chance to recover something, but if it's software, the fact that I tried to switch between versions decreases my chances to recover something.
What do you think?

Didgeridoohan said:
That fingerprint wasn't set by Magisk... Looks to me like you've been running a third-party/custom ROM and then didn't do a clean install of MIUI when going from the custom ROM. If so, that's a very likely source of the issues. I'm just guessing wildly though...
Click to expand...
Click to collapse
After I upgraded to MIUI 12.0.1.0 with MiFlash now I can't downgrade to 11.0.2.0. In logs everything seems to be ok, but the phone don't boot entering in recovery.
Trying to flash any other custom ROM, do you thing may be a solution? Or I will make things worse?

How can I resolve this situation?
If the fingerprint is the problem of FBE decrypting, how to restore the correct prop.default file?
Is any recovery that allow me to edit this file like text?
I have a copy of original prop.default.

Hey, did u mange to find a workaround? Im having the same issue, so frustrating!

Dead Sensors in Redmi Note 8 Help please!

I have changed from Rom from Android 11 to Android 10, and in the process the connection with the cell phone sensors has been lost. Investigating in Telegram groups about the RN8 I came up with the solution that was the following:
Code:
Fix for dead sensors
You might encounter the "Dead Sensors" bug when you flash a rom, DO NOT FLASH "persist.img" FILE!
But instead, do this workaround to fix the sensors without flashing anything.
INSTALL BUSYBOX FIRST
1) Open any Terminal Emulator app.
2) Type "su" to give it root permissions.
3) Copy and paste below command, apply it then reboot.
chcon -R u:object_r:sensors_persist_file:s0 /mnt/vendor/persist/sensors
4) Sensors should be working now, and this has been tested and it's working.
My problem is that since I made that rom change, the command files are not found so that I can solve the problem because those files have been deleted on my system.
I wanted to ask if someone would be so kind as to pass me the files of this root location:
/mnt/vendor/persist/sensors

same with me！i format all partions with some recovery，which i forget which one，since i tried all……
suddenly，sensors about display abnormal。
i tried fastboot mode to flash official ROM back，but do nothing to the dead sensor，very wired。
i thought i mistake formating some partion

Had the same problem almost a month ago.
*Spoiler* flashing the stock rom doesn't help.
The best way I found to fix it, was to use this solution.
[Guide] About repairing/fixing the persist partition
Disclaimer: I am not responsible for the results of any of these operations. Everyone knows that the persist partition is responsible for sonsors and carrier network etc. Once this partition is failed or lost, your phone will go wrong. I just...
forum.xda-developers.com

To make sure that something is wrong, run the CIT test.
If you don't know how to access it tell me