Search results

Only way I was able to fix encryption issue was to fastboot flash the latest global rom, then fastboot flash the absolute latest Orangefox recovery, then flash Xiaomi eu rom....and yes, data is lost, so hope you have a nandroid data backup..

I can also confirm with Nayandey that the compass is a little borked... Magnetic sensor readings in CIT are also incorrect. Actual compass readings are way off and inconsistent. This is also affecting Here-WE-Go Maps app. not sure if this logcat will help, but sent it anyway. Redmi note 7...

Thanks for the directions... I found that after installing the latest rom on lavender, it encrypted my data partition. I had done a nandroid backup of my boot, recovery, and data partition before flashing the rom, however.... Upon discovering that my data partition was encrypted, I installed...

Beta testing Android 10.

I am unfortunately still randomly losing root. My research has led me to XDA and onto other sites all confirming that some rooted devices might experience random stopping of the magiskd daemon, usually caused by some kind of memory management or app management killing the daemon. A reboot...

Yup.. Had the same problem with Redmi note 7 dirty flashed 9.8.1... Magisk 19.3 would uninstall itself at random... Did a complete uninstall of magisk from within the app itself (didn't save anything), allowing it to restore the stock boot image. Then reinstalled it from TWRP. Been good for...

No problem seeing 5ghz networks here... 9.8.1beta on Lavender. Are you running on a clean installation or dirty flash??

Thank you very much

Thanks for the guide. I'm still waiting for the 360 hours to end. Im going to assume lazyflasher-no-verity-opt-encrypt is not required and xiaomi.eu can be flashed to the data partition while it is still encrypted. Am I correct on that, or is it still necessary to "format" data to remove...

Try this. It IS NOT a pdf file. You MUST RENAME it to .zip and flash it through recovery. It will increase the volume of the 3.5mm jack only by upping the mixer values in the mixer_paths.xml files. I've been using it for months and I flash it along with all beta rom updates that I decide to...

I had the same issue... Every version after 8.11.15. To fix it, Install the new rom, and then over-write the mms.apk in /system/priv-app/mms with the one from 8.11.15. Set the permissions and reboot... Solved the problem for me.

abl.elf hyp.mbn mdtpsecapp.mbn pmic.elf rpm.mbn tz.mbn xbl.elf These are the files that are removed from the .eu roms. Exactly which file, or combination of files are responsible for causing issues with arb, I do not know. The files that remain in the rom update specific hardware and do not...

I already have a copy of stable 10.0.1.0 downloaded. I checked the zip contents in the firmware directory and the files that update firmware that would cause any problem with arb have been removed. You are safe to update as it will not have any impact on your arb. This link is for the beta...

The full wipe and reload restored the missing settings so I could change the data plan information. Very thankful for Titanium Backup :cool: After 5 dirty flashes, it was good to reload fresh.

I can confirm this on Whyred for 8.11.8, 8.11.15 and 8.11.22. I upgraded my data package today, and went to settings to change the data limit on my device and the settings are simply no longer there. The old data limits are still present in the system as I have been dirty upgrading for several...

ingbrzy and the developers remove the files from the rom that update the bootloader for whyred devices. There is no ARB in these roms from Xiaomi.eu. If you were anti-3 before coming to this rom, you still are and will continue to be anti-3.

Well I finally got home and downloaded the update.... looked inside the firmware-update folder inside the zip file, and looked at the files within the firmware-update folder.... same files as 8.9.20, and 8.9.13.... since there was no anti-update within the previous 2 updates, I'm going to go...

Very sorry... Looked for the latest release early this morning before posting a reply and didn't find it... AFH was not showing it to me... Only 8.9.20. Was not aware that it was out. I'll be grabbing 8.10.11 this afternoon when I get home.

Interesting.... I'm on the last update and I'm still anti-3...

Read the chart in the very first post... Look at Vince and you will see that ARB protection has not been enabled for your device. But regardless of that, ingbrzy and the developers remove ARB from their roms...