Related
Just a query really more than anything.
I've got my Nexus 5 rooted using cf-auto root, TWRP recovery and got xposed framework installed.
Now whenever the next update for android comes out what would I need to do?
Do I have to disable xposed modules and then just flash the update and supersu zip?
or do I need to do more now I have got xposed.
Cheers guys.
brichardson1991 said:
Just a query really more than anything.
I've got my Nexus 5 rooted using cf-auto root, TWRP recovery and got xposed framework installed.
Now whenever the next update for android comes out what would I need to do?
Do I have to disable xposed modules and then just flash the update and supersu zip?
or do I need to do more now I have got xposed.
Cheers guys.
Click to expand...
Click to collapse
Xposed has nothing to do with Android updates. With root & TWRP you will have to flash the OTA update file then root again.
This guide should help you.
Ah fair enough, just wasn't sure due to xposed framework changing system files.
Primokorn said:
Xposed has nothing to do with Android updates. With root & TWRP you will have to flash the OTA update file then root again.
This guide should help you.
Click to expand...
Click to collapse
from the thread you linked:
Note: Literally any modification will break the OTA. Xposed, DPI, build.prop, volume mod, etc. ANYTHING!
Click to expand...
Click to collapse
Q: I have Xposed Framework installed. Do I need to uninstall it before the OTA?
A: Yes. It needs to be uninstalled and in some cases system files need to be replaced.
Click to expand...
Click to collapse
I imagine removing the modules and uninstall xposed I would be able to update then resume installing xposed and the modules again?
brichardson1991 said:
I imagine removing the modules and uninstall xposed I would be able to update then resume installing xposed and the modules again?
Click to expand...
Click to collapse
Hi,
Yes, and in Xposed framework you need to restore the original files by using "Uninstall (Restore app_process before)" before uninstall the app itself. The system file "app_process" is modified (/system/bin/app_process).
It will not hurt...
gian569 said:
from the thread you linked:
Click to expand...
Click to collapse
You have to do it ONLY IF you want to go back to stock. However you can simply flash the OTA update from a custom recovery.
As mentioned by El Daddy "In order for the OTA to apply successfully without intervention; you must be completely stock".
Primokorn said:
You have to do it ONLY IF you want to go back to stock. However you can simply flash the OTA update from a custom recovery.
As mentioned by El Daddy "In order for the OTA to apply successfully without intervention; you must be completely stock".
Click to expand...
Click to collapse
no, just no. if you want to the take the OTA, you must not have any modified /system/ files, which xposed modifies /system/ files.
xposed modifies the system and if you want to install the OTA through the stock recovery or even a custom recovery, you must uninstall the modules and framework.
Ok well that's useful to know.
Cheers all
Zepius said:
no, just no. if you want to the take the OTA, you must not have any modified /system/ files, which xposed modifies /system/ files.
xposed modifies the system and if you want to install the OTA through the stock recovery or even a custom recovery, you must uninstall the modules and framework.
Click to expand...
Click to collapse
Well... that's not what some people told me and the section B explains that:
Section B: Flashing in a Custom Recovery (TWRP- CWM)
1) Download the OTA.zip and copy to your phone.
2) Boot into recovery.
3) Flash the OTA just like you would a ROM.
4) Reboot.
Click to expand...
Click to collapse
However I'm always on custom ROMs so I never tried OTA update.
Maybe removing Xposed stuff is mandatory. I trust you if you are 100% sure.
Primokorn said:
Well... that's not what some people told me and the section B explains that:
However I'm always on custom ROMs so I never tried OTA update.
Maybe removing Xposed stuff is mandatory. I trust you if you are 100% sure.
Click to expand...
Click to collapse
what you quoted has to do if you made no system mods but have a custom recovery. The OTA checks the system files to make sure they are as expected.
i am 100% sure you need to uninstall xposed framework/modules before you can even think of flashing the OTA.
Zepius said:
what you quoted has to do if you made no system mods but have a custom recovery. The OTA checks the system files to make sure they are as expected.
i am 100% sure you need to uninstall xposed framework/modules before you can even think of flashing the OTA.
Click to expand...
Click to collapse
Thanks for the clarification.
Framework yes! MUST be uninstalled as this is in /system. You can then flash the ota manually via recovery but not before.
Xposed modules however do not modify /system. They are basic /data/app apks that use "existing" (xposed framework) /system resources. They do not further modify /system so I would doubt they need to be uninstalled
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
rootSU said:
Framework yes! MUST be uninstalled as this is in /system. You can then flash the ota manually via recovery but not before.
Xposed modules however do not modify /system. They are basic /data/app apks that use "existing" (xposed framework) /system resources. They do not further modify /system so I would doubt they need to be uninstalled
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Click to expand...
Click to collapse
This may be dumb questions. If they are, I accept your scorn. When people say uninstall, that just entails going into the Xposed Installer app and hitting "Uninstall" under the Framework menu, right? There's really no need to uninstall the installer from the phone altogether, or is there? And finally, since the modules don't really modify /system, I take it it doesn't really matter whether we uncheck them or leave them checked when we uninstall the xposed framework?
charesa39 said:
This may be dumb questions. If they are, I accept your scorn. When people say uninstall, that just entails going into the Xposed Installer app and hitting "Uninstall" under the Framework menu, right? There's really no need to uninstall the installer from the phone altogether, or is there? And finally, since the modules don't really modify /system, I take it it doesn't really matter whether we uncheck them or leave them checked when we uninstall the xposed framework?
Click to expand...
Click to collapse
That should be the case. Xposed installer is just a /data/app to install and manage the actual framework in /system. It's the framework that runs the modifications the modules provide, which is the whole point. Run system mods without Modding system... except the small mod of adding the framework itselfn.
One mod to rule them all
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
charesa39 said:
This may be dumb questions. If they are, I accept your scorn. When people say uninstall, that just entails going into the Xposed Installer app and hitting "Uninstall" under the Framework menu, right? There's really no need to uninstall the installer from the phone altogether, or is there? And finally, since the modules don't really modify /system, I take it it doesn't really matter whether we uncheck them or leave them checked when we uninstall the xposed framework?
Click to expand...
Click to collapse
I think what @viking37 said is true - you need to go into the Xposed installer and select the option to uninstall and restore the original app_process.
Uninstalling the modules is really not needed. Keeping the modules "should" actually make sure that you don't have to worry about re-setting up the module the way you want it after you reinstall the XPosed Framework. (settings should get carried forward)
Re,
Yep, just use uninstall inside Xposed Framework, it will restore the original app_process located in /system/bin/app_process. When you use install inside Xposed Framework it will modifie the "app_process" file and create a backup of this file named "app_process.orig" then this file will be restored when using the uninstall option in Xposed Framework. You need, obviously to reboot.
In my previous post I said use "Uninstall (Restore app_process before)" because I have an older version (it was this name), now it's just "Uninstall", all is fine.
It seems that just uninstall Xposed Framework via settings/apps doesn't restore the original app_process. Just tested it's the case, if you uninstall Xposed Framework only via settings/apps, the "app_process" file is not restored, so the system file is still modified...
as a user, i can validate this.....
trying to flash OTA using custom recovery will fail if exposed is left alone
as long as you "Uninstall (Restore app_process before)"...... then the OTA will flash fine
viking37 said:
It seems that just uninstall Xposed Framework via settings/apps doesn't restore the original app_process. Just tested it's the case, if you uninstall Xposed Framework only via settings/apps, the "app_process" file is not restored, so the system file is still modified...
Click to expand...
Click to collapse
I dont think you can uninstall the "xposed framework" from settings > Apps. Only the "xposed framework installer", although really old versions didn't use the installer at all either.
Re,
Hum... I just tested with the last version available in the Xposed thread, xposed.installer_v25_36
What I mean is that you need to first use the "uninstall" option in Xposed to have your "app_process" file restored other than that just uninstall Xposed from settings/apps keeps the "app_process" modified (you can see with the date of the modification in /system/bin with a file explorer and file zize too, not the same) and "app_process.orig" so t's not restored.
Hello everyone I currently have an issue to install some banking apps and MobileIron.
I cant use google pay, postfinance TWINT and Mobileiron (because of root getting detected or not passing safetynet or xposed.)
I am not passing Safetynet unless I check "only use core functions" in magisk.
I am hiding MobileIron with MagiskHide and I am also hiding Xposed Installer from MobileIron with suhide.
I already tried having another app block root and xposed detection for MobileIron (uncheck)
What can I do to get it to work?
Please don't tell me to just "unroot" or go back to stock.
Have a great day!
Uninstall xposed , Nothing else i can say
I now the issue well with Postfinance Twint on my rooted Samsung Galaxy S5.
Uninstalling xposed will show no effect, because your phone is locked with a root detection. The only solution I've found was to install the old version 1.1.16.0, the last version before root detecting. This works fine for me (except the QR-Scanner which shows "Error 13: The Scandit SDK license validation failed", but you can use the code input instead).
If someone knows a better solution: post it!
Reading this I stopped my thoughts about rooting. I'm using many banking apps, most of all SEQR for nfc payments. I see myself running into problems getting my finance apps to work once rooted...
lucajasonmiani said:
Hello everyone I currently have an issue to install some banking apps and MobileIron.
I cant use google pay, postfinance TWINT and Mobileiron (because of root getting detected or not passing safetynet or xposed.)
I am not passing Safetynet unless I check "only use core functions" in magisk.
I am hiding MobileIron with MagiskHide and I am also hiding Xposed Installer from MobileIron with suhide.
I already tried having another app block root and xposed detection for MobileIron (uncheck)
What can I do to get it to work?
Please don't tell me to just "unroot" or go back to stock.
Have a great day!
Click to expand...
Click to collapse
did you try "Hide Magisk Manager" option in Magisk Manager?
maybe your bank app is looking for Magisk Manager package too.
I'm not using app that you mention but you can try .
No problems with new version 2.0.20.0 (PostFinance Twint) on rooted Samsung Galaxy S5
I had a similar problem with my banking app. I solved it by installing island app. It basically creates an "island" where you can separate specific apps from the rest of your phone apps. When I put my banking app in the island it worked perfectly (also used magisk hide).
You'll have two versions of the same app when you do this. Just remember to always run the island version of the app not the normal version. There will be a small icon indicating which is which.
Hope it works with you!
lo2ay said:
I had a similar problem with my banking app. I solved it by installing island app. It basically creates an "island" where you can separate specific apps from the rest of your phone apps. When I put my banking app in the island it worked perfectly (also used magisk hide).
You'll have two versions of the same app when you do this. Just remember to always run the island version of the app not the normal version. There will be a small icon indicating which is which.
Hope it works with you!
Click to expand...
Click to collapse
Even with the island app, tez app is not working.
Hi everyone,
I'm curious if anyone has gotten the SuperSU root method running on this phone. I know that magisk exists but snapchat has problems with magisk for some reason so I would prefer to use SuperSU instead. I already have the latest twrp installed if that helps at all. Flashing the SuperSU zip doesn't seem to do anything so I'm hoping somebody has figured this out already.
Thanks,
TomatoesOnBluRay
TomatoesOnBluRay said:
Hi everyone,
I'm curious if anyone has gotten the SuperSU root method running on this phone. I know that magisk exists but snapchat has problems with magisk for some reason so I would prefer to use SuperSU instead. I already have the latest twrp installed if that helps at all. Flashing the SuperSU zip doesn't seem to do anything so I'm hoping somebody has figured this out already.
Thanks,
TomatoesOnBluRay
Click to expand...
Click to collapse
just realized i put this in guides instead of questions and answers. Is there a way to move it? Serious noob here.
Do not think anyone has used SuperSU in a few years really. What is wrong with Snapchat and rooted with Magisk?
Snapchat wont get along with Supersu either. At least you could try to hide Magisk from Snapchat
I'm abit curious now, why would you prefer having supersu when magisk works the same way but even better?
schmeggy929 said:
Do not think anyone has used SuperSU in a few years really. What is wrong with Snapchat and rooted with Magisk?
Click to expand...
Click to collapse
it seems like supersu hasn't been updated in a couple years now, so you're absolutely correct. Snapchat keeps locking me out of my account for "using a third party app" even though I haven't been using a third party app. My guess is that it's detecting root somehow even when I have magisk hide enabled, magisk changed to manager, and xprivacylua restricting snapchat's access to files. I even tried using parallel space to copy snapchat into an isolated environment, but it doesn't even log in. It might have something to do with Oxygen OS, but I'm not sure. Although it's unlikely, I'm trying to see if there is a way to install SuperSU on this phone because I know snapchat works as it did on my old phone (if you log in before you root, of course). If it's not possible, I'll just have to figure something out.
TomatoesOnBluRay said:
it seems like supersu hasn't been updated in a couple years now, so you're absolutely correct. Snapchat keeps locking me out of my account for "using a third party app" even though I haven't been using a third party app. My guess is that it's detecting root somehow even when I have magisk hide enabled, magisk changed to manager, and xprivacylua restricting snapchat's access to files. I even tried using parallel space to copy snapchat into an isolated environment, but it doesn't even log in. It might have something to do with Oxygen OS, but I'm not sure. Although it's unlikely, I'm trying to see if there is a way to install SuperSU on this phone because I know snapchat works as it did on my old phone (if you log in before you root, of course). If it's not possible, I'll just have to figure something out.
Click to expand...
Click to collapse
You need to Magisk hide Snapchat. Go to menu(top left, 3 lines) click Magisk Hide. Scroll to Snapchat and check it. Clear data for Snapchat. Log back in.
schmeggy929 said:
You need to Magisk hide Snapchat. Go to menu(top left, 3 lines) click Magisk Hide. Scroll to Snapchat and check it. Clear data for Snapchat. Log back in.
Click to expand...
Click to collapse
I did this but it didn't work, it still locks my account. Snapchat seems to have some weird form of detection that can't be worked around.
TomatoesOnBluRay said:
I did this but it didn't work, it still locks my account. Snapchat seems to have some weird form of detection that can't be worked around.
Click to expand...
Click to collapse
Weird, never had an issue with Snapchat and was always rooted.
I used to have the same issue with snapchat until I started using the Magisk Beta versions, since then I haven't had that issue at all. Which version of Magisk are you using?
TomatoesOnBluRay said:
I did this but it didn't work, it still locks my account. Snapchat seems to have some weird form of detection that can't be worked around.
Click to expand...
Click to collapse
Get it up and running, create a backup with titanium and when you are on magisk, restore the data.
Thats how i used to do it when it wouldnt let me log in. But I havent had the issue for years with magisk. Ensure you are using the current and ensure you pass safety net.
Due to mounting issues with the current root solution on Android 10, Adaway doesn't seem to be able to either write to the hosts file or modify it. Has anyone found a solution?
Thanks....
floepie said:
Due to mounting issues with the current root solution on Android 10, Adaway doesn't seem to be able to either write to the hosts file or modify it. Has anyone found a solution?
Thanks....
Click to expand...
Click to collapse
Really? Mine is working exactly as in Pie. I am rooted with magisk 19.3 and have systemless hosts module installed. Adaway has no issue writing to this hosts file.
clcdev said:
Really? Mine is working exactly as in Pie. I am rooted with magisk 19.3 and have systemless hosts module installed. Adaway has no issue writing to this hosts file.
Click to expand...
Click to collapse
Thanks! Got it working. There is no module any longer, as it is a setting in the app itself - a setting which you just tap with no dialog, only a "toasted" confirmation.
floepie said:
Thanks! Got it working. There is no module any longer, as it is a setting in the app itself - a setting which you just tap with no dialog, only a "toasted" confirmation.
Click to expand...
Click to collapse
When I click that checkbox, I got the confirmation on the bottom that says Adaway was granted Superuser rights, but the box doesn't actually check, and nothing changes. Am I missing something stupid?
Go to setting in magisk and enable this module, restart, and then adaway should work.
I've tried that. Got all messages showing up that it's fine. Rebooted and still see ads in certain pages.
Unfortunately best solution thus far is the AdGuard app but that's VPN and draining juice.
wbgenetic said:
I've tried that. Got all messages showing up that it's fine. Rebooted and still see ads in certain pages.
Unfortunately best solution thus far is the AdGuard app but that's VPN and draining juice.
Click to expand...
Click to collapse
Just to make sure; you also checked the systemless mode in AdAway?
(after reboot to enable magisk systemless module)
If it blocks most ads you may want to add another hosts source.
Mother_Teresa said:
Just to make sure; you also checked the systemless mode in AdAway?
(after reboot to enable magisk systemless module)
If it blocks most ads you may want to add another hosts source.
Click to expand...
Click to collapse
I have the same problem. Pixel 2 XL, Android 10. Magisk works, safetynet works. Adaway doesn't. The systemless hosts module in magisk shows as enabled, the tick box on adaway doesn't work (when I tap it nothing happens). When I select enable adblocking in Adaway it starts building the hosts file and ends with an error message "remount failed. Remounting the partition as read/write failed!".
airmark said:
I have the same problem. Pixel 2 XL, Android 10. Magisk works, safetynet works. Adaway doesn't. The systemless hosts module in magisk shows as enabled, the tick box on adaway doesn't work (when I tap it nothing happens). When I select enable adblocking in Adaway it starts building the hosts file and ends with an error message "remount failed. Remounting the partition as read/write failed!".
Click to expand...
Click to collapse
Are you using the latest AdAway? Maybe you need to update the app itself.
Hmmm can I add other stuff to the hosts file? Sort of like easy lists for different languages like adblocker on chrome for PC? This might do the trick if possible.
hunfatal said:
Are you using the latest AdAway? Maybe you need to update the app itself.
Click to expand...
Click to collapse
Version 4.2.9. F-droid says it's the latest
wbgenetic said:
Hmmm can I add other stuff to the hosts file? Sort of like easy lists for different languages like adblocker on chrome for PC? This might do the trick if possible.
Click to expand...
Click to collapse
Yes, checks settings
So most ads get blocked but not all?
adaway forum to get latest version and gossip.
I also had issues getting AdAway running on Android 10, but managed to get it going eventually. I had the same issues as the others: "Enable systemless mode" checkbox was "toasting" but not checking in AdAway, despite tapping the "Systemless hosts" item in Magisk and getting successful-looking toast notifications.
Steps that worked for me:
Take note of any settings you have in AdAway, as they are about to go away
Completely uninstall AdAway. This means Force Stop, Clear Cache, Clear Data, then Uninstall
Reboot
Open Magisk Manager --> Settings --> Tab the "Systemless hosts" item. You should get the toast notification.
Install the latest version of AdAway (v4.2.9 as of now, as others have mentioned)
Open AdAway --> Preferences. With luck, you'll see that Enable systemless mode is checked already (pretty sure mine was). If not...maybe try checking it now.
AdAway should work now. Make sure to poke around and add back any customizations you used to have.
Hope that helps!
I stopped using adaway in favor of DNS66 for about two years now. Might be worth a shot if you're still having issues with Adaway
https://f-droid.org/en/packages/org.jak_linux.dns66/
HypromanGT said:
I also had issues getting AdAway running on Android 10, but managed to get it going eventually. I had the same issues as the others: "Enable systemless mode" checkbox was "toasting" but not checking in AdAway, despite tapping the "Systemless hosts" item in Magisk and getting successful-looking toast notifications.
Steps that worked for me:
Take note of any settings you have in AdAway, as they are about to go away
Completely uninstall AdAway. This means Force Stop, Clear Cache, Clear Data, then Uninstall
Reboot
Open Magisk Manager --> Settings --> Tab the "Systemless hosts" item. You should get the toast notification.
Install the latest version of AdAway (v4.2.9 as of now, as others have mentioned)
Open AdAway --> Preferences. With luck, you'll see that Enable systemless mode is checked already (pretty sure mine was). If not...maybe try checking it now.
AdAway should work now. Make sure to poke around and add back any customizations you used to have.
Hope that helps!
Click to expand...
Click to collapse
FIXED : Did same twice didn't work untill i gave permission of storage to the app before launching it
driss.sadok said:
FIXED : Did same twice didn't work untill i gave permission of storage to the app before launching it
Click to expand...
Click to collapse
I have done step by step and doesnt work, i've got android 9, but it doesnt metter still cant make it work. Root works, hosts i've checked with file menager is also full, updated sources. Checked with 3 browsers and i still see alot of ads...
smile20 said:
I have done step by step and doesnt work, i've got android 9, but it doesnt metter still cant make it work. Root works, hosts i've checked with file menager is also full, updated sources. Checked with 3 browsers and i still see alot of ads...
Click to expand...
Click to collapse
have you enabled systemless hosts in magisk?
gvsukids said:
have you enabled systemless hosts in magisk?
Click to expand...
Click to collapse
Yes, in magisk manager, restarted system, then installed adaway, gave permission to storage before first turn on, then checked systemless host setting in Adaway menu, but it was already on, downloaded sources, restarted system and now it supposed to wotk, but it doesn....There was just one reason i've rooted system, and it doesnt work...
Try enabling the hosts before installing adaway. Are you using the fdroid version?
gvsukids said:
Try enabling the hosts before installing adaway. Are you using the fdroid version?
Click to expand...
Click to collapse
This is how i've done . First enabled in magisk manager, then installed Adaway. I've downloaded direct Adaway apk from frdroid site.
I'm trying to bypass the SafetyNet chore by using MagiskHide and tools like this one.
I have yet to have success.
I have read lots of information about the topic, but most seems irrelevant and obsolete.
I use a custom ROM with Root enabled.
Can anyone please point me in the right direction of solving this issue?
Thank you.
It would help if you stated which ROM or Android version you are on...
pnin said:
It would help if you stated which ROM or Android version you are on...
Click to expand...
Click to collapse
Android 11, Octavi OS.
I see... can't really help, no experience.
Magisk, Universal SafetyNetFix and MagiskHideProps
robogo1982 said:
Magisk, Universal SafetyNetFix and MagiskHideProps
Click to expand...
Click to collapse
Of course, I have that installed and working according to tutorials, already...
Still, not working.
"Fixed" it by appending `LEGACY_MIFARE_READER=1` to `/system/vendor/etc/libnfc-nci.conf`.
However, this breaks my SIM service. Not sure, how those features are related, but here we are.
Another reboot seems to have fixed the SIM service issue.
Is this really it? Is the NFC problem really fixed after such a long time?
I cannot believe it.
I will test this for some time, just to be sure....
Did you force basic attestation in props?
I'm using ArrowOS 12 (ArrowOS 11 before that) and never had problems with SafetyNet.
Using latest Magisk, Zygisk and DenyList enabled. As for modules, I use GPay SQLite Fix and Universal SafetyNet fix. No other fixes or modules were necessary
if it's for banking apps, just check "Google services" on DenyList (first of all click the dots on right upper corner and check system apps). I was fighting that some time ago.
there's no need to install modules or do anything else, just check all apps U need on DenyList but the main app to deny is still "Google Services"
xSokol said:
if it's for banking apps, just check "Google services" on DenyList (first of all click the dots on right upper corner and check system apps). I was fighting that some time ago.
Click to expand...
Click to collapse
Enabled DenyList, checked Google Play Services and it stays checked. Checking Google Services Framework gets reverted each time I visit DenyList. There is no "Google services".
I found `*.gservices` as a sub-category of Google Services Framework. Disabled. Rebooted several times, after trying out multiple possibilities, but none did work. One time, even basic attestation was broken, which needed another reboot to fix.
no, sorry for my rush, it was about Google Play Services. I have never "denied" Google Services Framework.
what I would do is uninstall modules like "safetynet fix" and reboot to twrp, there's a fix for zygisk, install that one.
then reboot to system, clear all the data of an disobedient app, then go to Magisk DenyList and look for the app, check all services and search for Google Play Services again (I have to check it aftet every reboot somehow).
I just have had similar issue an hour ago with Revolut app because I crashed my system and had to dirty flash what swiped Magisk.
just be patient, it's not hard or complicated work
xSokol said:
there's a fix for zygisk, install that one.
Click to expand...
Click to collapse
Which one? Where? How?
xSokol said:
clear all the data of an disobedient app, then go to Magisk DenyList and look for the app, check all services
Click to expand...
Click to collapse
Check the app or what services? What exactly?
ok, then..
if You go in TWRP to "advanced" and then to "magisk" (sorry if the name isn't correct, I don't focus on names of options) and there are options like "install magisk 24..." or "uninstall magisk 24...", under that there are fixes, so You should find it, it's under "SafetyNet Fix". You need Zygisk, so get fix for Zygisk.
I was about the app that's not working, if You click on the bar with the name it will show its services. in standard Magisk denies only the main service of an app, but some apps require checking all of them.
hello @Aki-to , did U manage?
xSokol said:
hello @Aki-to , did U manage?
Click to expand...
Click to collapse
I did not dare to go into TWRP, because I am not absolutely sure if data or storage encryption works perfectly fine with TWRP on Android 11. I don't want to boot into TWRP and have everything encrypted and therefore unusable.
I did so many flashes and some of them had this problem, but I cannot remember if it was because of a failed flash or because it actually did not work.
I also do not want to remove encryption in Android Security Settings every single time I visit TWRP.
Posts like the following also sound very concerning.
[FIXED] How to remove data encryption in TWRP
Users of TWRP 3.1 on Doogee Mix (including myself) faced the mammoth problem of an encrypted storage after unlocking the bootloader and flashing the custom recovery. This problem is not peculiar to the Doogee Mix, any other device with TWRP 3.1+...
forum.xda-developers.com
there's no need to remove encryption, nothing abiut that.
I just have changed MIUI to 13 today, didn't change anything on TWRP, just installed Magisk from TWRP and checked all the bank apps, GPay and Google Play Services
Aki-to said:
"Fixed" it by appending `LEGACY_MIFARE_READER=1` to `/system/vendor/etc/libnfc-nci.conf`.
However, this breaks my SIM service. Not sure, how those features are related, but here we are.
Click to expand...
Click to collapse
Hi, could you share your Magisk module?
Haobin said:
Hi, could you share your Magisk module?
Click to expand...
Click to collapse
Sure, wanted to do that, anyway, but forgot about it.