This is my trick: Save Magisk APK directly inside /data partition. This folder isn't encrypted and you can find it inside your phone each time you flash a new OTA update. Yes, you have to do this manually each time, but you have the file easy to find and use.I have two noob questions guys
1. Why are recoveries no longer able to request password decryption and show files normally?
2. I don't want to use DFE I prefer to stay encrypted. I flashed Magisk right after the ROM using ofox official recovery.
but now that i am no longer able to decrypt files in recovery mode, will i lose magisk/root if i do OTA update? Does that mean a rooted phone will require a clean flash with every update?
As far As I understood, when you are encrypted you need to Format data und use dfe in order to prevent encryption. Is this correct? So with the latest 2 Releases, encryption cannot be enabled anymore?
If you format data, data is automatically encrypted. That's why I keep reminding people to ONLY use DFE if totally necessary.As far As I understood, when you are encrypted you need to Format data und use dfe in order to prevent encryption. Is this correct? So with the latest 2 Releases, encryption cannot be enabled anymore?
Just asking because I am using this Rom As a daily driver and prefer having encryption, dmverity etc. enabled.
I use elixir unencrypted and google pay does work. Are you sure ?I know for a fact that Google Pay will not work on a decrypted phone wihout Magisk & SafetyNet. So I do everything at 1 go. Install ROM, DFE, Magisk and then SafetyNet. Go to SafetyNet to change settings for Google Pay before I add credit card to Google Pay.
I have not tested Google Pay on a decrypted phone without Magisk & SafetyNet. So I am not sure about error messages.
When I first get this phone, I have to unlock bootloader to install the global official ROM. With bootloader unlocked, I cannot even add credit card to Google Pay.
It's format DATA partition, not wipe/clean option. It does make a difference.Hello, I have a problem, I installed the latest rom with correct data cleaning and orangefox, I put all the apps on my device and everything worked but when I reboot the device, the screen to enter the pin turns on and off the screen several times and returns me to orangefox.
Is it a bug?
install app in working rom
So if you formated Data partition, flashed ROM, DFE and reboot. Do not restore any backup afterwards.. Run setup as a fresh device and see how it behaves. If all goes well and there's no issue, format Data again, reboot and setup device wih backup, but uncheck System settings - do not restore that. And see how it goes.
Wow, if I turn off the device and wait 5 minutes it starts up, if I do a restart it fails in the pin, now I'm with the device workingSo if you formated Data partition, flashed ROM, DFE and reboot. Do not restore any backup afterwards.. Run setup as a fresh device and see how it behaves. If all goes well and there's no issue, format Data again, reboot and setup device wih backup, but uncheck System settings - do not restore that. And see how it goes.
No, you're not. Only when the certain build bootloops and won't boot with a clean flash.
I appreciate users like this. They actually take the time to appreciate the work instead of nitpicking the minor issues that don't even affect their daily activities. Users like you are the ones that ACTUALLY keep developers motivated to keep improving their old devices.I don't really have anything to add, just wanted to say a good old thank you for this great rom.
Works flawless for me and breathes life into a device with good hardware that was just let down by its manufacturers software support.
It is fantastic to have people like you who work on this for free. I sent some coffeemoney via paypal. Well done.
1. MIUI camera isn't even supposed to be included in the first place but was added due to demand. Any issues that come along with it, including issues with instantaneous access via lockscreen, will be ignored.I get your frustration, but a bug report is a bug report and not nitpicking. Just because you may or may not be able to replicate it, it doesn't make it nitpicking but it's a courtesy to let you know of that issue and ask the community of any workarounds, until you may find the time and priority to fix the issue.
My suggestion: have you thought of an issue tracker (e.g. issues in GitHub)? This way it's easier to keep an overview. I don't think spamming everything in one thread is a good idea, especially not personal installation issues.
/* * Your warranty is void. Or valid, probably? * * I am not responsible for bricked devices, dead SD cards, Ebolation X, * thermonuclear war, or the current economic crisis caused by you following * these directions. YOU are choosing to make these modifications, and if * you point your finger at me for messing up your device, I will LMAO at you. */