Related
can someone make me a flashable zip for making my /system partition mounted into RW on boot?
Newbie here Will appreciate every help thanks
ChanSilvers said:
can someone make me a flashable zip for making my /system partition mounted into RW on boot?
Newbie here Will appreciate every help thanks
Click to expand...
Click to collapse
You need to have root and any terminal installed.
Start terminal and type
Code:
su
mount -o rw,remount /system
It will be remounted RW without any zip flashing and rebooting, realtime.
fehhner said:
You need to have root and any terminal installed.
Start terminal and type
Code:
su
mount -o rw,remount /system
It will be remounted RW without any zip flashing and rebooting, realtime.
Click to expand...
Click to collapse
thanks man! ? I tried that but my phone reboots after i entered the command and my phone is rooted ?
Sorry for the dig up but i am also interrested in this.
I am using an app (NFC Card Emularo) which requires access to /vendor/etc/libnfc-nxp.conf but cannot access it -> the partition is reported to be "read only" by the app. I was able to use the mount command but i am not sure it changes anything since the partition doesnt seem to be writable anyway.
My rig : OnePlus 3T / Oreo (Resurrection Remix OS) / Magisk 16 (also tried 16.2)
Error on remount /system
/system permission can't get full permission
Hi I am using the same app and facing the same problem you have. I have a moto Z 2016 and using the app well, on moto Z2 ,the same problem as you are having. I tried to create file in the dest folder where the app need to modifiy file and success. Still digging into that.
Has anyone been able to solve this? I too use NFC Card Emulator and it's been working fine for a while but then I got the same problem. I don't know what caused it, either an update to the app, LineageOS, Magisk or TWRP. I'm using a OnePlus 5T.
Since Magisk is mounting it's systemless mask over /system and /vendor, directly modifying/mounting these as rw can be an issue...
If you're not using any Magisk modules, you should be able to make it work by just enabling Core Only Mode in the Manager settings.
Otherwise, I would try by taking whatever file it is that the app is trying to modify and make a Magisk module out of it. This way the app should have full write access to the file, and you'll have the benefit of keeping your system untouched.
Didgeridoohan said:
Since Magisk is mounting it's systemless mask over /system and /vendor, directly modifying/mounting these as rw can be an issue...
If you're not using any Magisk modules, you should be able to make it work by just enabling Core Only Mode in the Manager settings.
Otherwise, I would try by taking whatever file it is that the app is trying to modify and make a Magisk module out of it. This way the app should have full write access to the file, and you'll have the benefit of keeping your system untouched.
Click to expand...
Click to collapse
There is an option to generate a Magisk module from the app and that's actually what I used until things broke. After some testing, going back to the March 5 build of LineageOS 15.1 and getting version 3.0.9 of NFC emulator from Aptoide made it work again, but any version 3.1.0 or up doesn't and 3.0.9 does not work on latest LineageOS (March 26 because f that April fools crap). I also tried all the latest LineageOS/TWRP/NFC Emulator on my old Nexus 6P and there, everything works as expected.
So what I get from this is that the fault is either in LineageOS or the app and it's device specific.
An update to this. LineageOS version does not matter as I was able to get NFC Card Emulator version 3.0.9 running on the latest LineageOS. If you download version 3.0.9 from Aptoide it will work once and then stop working, later versions won't work at all. So the best current solution is to use version 3.0.9 of the app and on each reboot after the first install, clear data for the app and it will work again.
Limero said:
An update to this. LineageOS version does not matter as I was able to get NFC Card Emulator version 3.0.9 running on the latest LineageOS. If you download version 3.0.9 from Aptoide it will work once and then stop working, later versions won't work at all. So the best current solution is to use version 3.0.9 of the app and on each reboot after the first install, clear data for the app and it will work again.
Click to expand...
Click to collapse
I can confirm this.
I was having problems with the lastest version of NFC Card Emulator, so I downloaded and installed version 3.0.9 and everything works fine.
Thanks for the tip!
same problems.
I have xiaomi with miui10 beta and magisk with a module installed.
The nfc say to me that the vendor partition is read only and I must reboot the boot everytime
Aight! I think I've found a solution!
DAVIZINHO said:
same problems.
I have xiaomi with miui10 beta and magisk with a module installed.
The nfc say to me that the vendor partition is read only and I must reboot the boot everytime
Click to expand...
Click to collapse
I'm using MI6 with all in one magisk module enabling camera2 api and some other stuff.
Today morning I f**up my phone trying to solve this problem and found a solution, by accident.
Here it is:
Don't install magisk module mentioned above
szaman8666 said:
I'm using MI6 with all in one magisk module enabling camera2 api and some other stuff.
Today morning I f**up my phone trying to solve this problem and found a solution, by accident.
Here it is:
Don't install magisk module mentioned above
Click to expand...
Click to collapse
The problem in my case is that i need the module "magiskhide props config" for pass the safety check.
If i uninstall this module, maybe not works?
I dont know if i can uninstall the module and work, i will try
DAVIZINHO said:
The problem in my case is that i need the module "magiskhide props config" for pass the safety check.
If i uninstall this module, maybe not works?
I dont know if i can uninstall the module and work, i will try
Click to expand...
Click to collapse
Checked the module You've mentioned, Nfc Card Emulator works fine but it may depend on Miui ROM, mine is 8.5.8 beta.
szaman8666 said:
Checked the module You've mentioned, Nfc Card Emulator works fine but it may depend on Miui ROM, mine is 8.5.8 beta.
Click to expand...
Click to collapse
I need this module, if I uninstall not works the safetynet check.
And with this module, nfc card emulator give me the error I use miui 10 beta
Didgeridoohan said:
Since Magisk is mounting it's systemless mask over /system and /vendor, directly modifying/mounting these as rw can be an issue...
If you're not using any Magisk modules, you should be able to make it work by just enabling Core Only Mode in the Manager settings.
Otherwise, I would try by taking whatever file it is that the app is trying to modify and make a Magisk module out of it. This way the app should have full write access to the file, and you'll have the benefit of keeping your system untouched.
Click to expand...
Click to collapse
In theory, if I temporarily disable all of my modules and enable Core Only Mode, would I be able to access the system as RW?
rodken said:
In theory, if I temporarily disable all of my modules and enable Core Only Mode, would I be able to access the system as RW?
Click to expand...
Click to collapse
That is a two and a half year old post you're quoting. A lot have happened in that time...
Core only mode is being removed from Magisk and there are plenty of devices that have permanently ro partitions.
https://www.didgeridoohan.com/magisk/Magisk#hn_Cant_edit_system_files
So the answer to your question would be a definite maybe.
Didgeridoohan said:
That is a two and a half year old post you're quoting. A lot have happened in that time...
Core only mode is being removed from Magisk and there are plenty of devices that have permanently ro partitions.
https://www.didgeridoohan.com/magisk/Magisk#hn_Cant_edit_system_files
So the answer to your question would be a definite maybe.
Click to expand...
Click to collapse
im on android 10 DirtyUnicorns and i want to completely replace the media folder with my own mod. how can i do this? im not able to do it on my pixel 3 yet i just did it on my pixel 2 xl running the same ROM.
Hola yo lo único que quiero es montar sistema como lecturas escritura y ya como puedo hacer android 8
My banking app (NAB Mobile Banking), like most, doesn't like it if my phone doesn't pass CTS or if it's rooted when setting up tap-and-pay.
Since I've started using Magisk I've had lots of trouble getting this banking app to work properly.
This is how I have learnt to set it up .
1. Install Magisk. I'm using 15.3.
2. Wipe the app's data in Settings>Apps. But *do not* start the banking app!
3. Hide the app in Magisk.
4. Reboot the phone.
5. Set up the banking app.
At this stage it's usable but in order to be able to survive reboots and restoring from backups I do the following:
6. Hide Magisk Manager. If I don't do this the app will lose the tap-and-pay capability on reboot.
(Thanks @Didgeridoohan for the suggestion)
Old
6. Backup the app using Titanium Backup (TB).
7. Freeze the app using TB before rebooting the phone for whatever reason. If I don't do this the app will lose the tap-and-pay capability.
I take my backups in this state.
Once the phone has rebooted I then:
8. Defrost the app in TB.
9. Make the app the default for tap-and-pay as this gets lost by the freeze/defrost process.
If I have forgotten to freeze the app across reboots then tap-and-pay won't work. However I can:
10. Use TB to restore the app's data, set it as the default for tap-and-pay and I'm good to go.
End Old
The following actions will break the tap-and-pay function and require me to go through the setup process all over again:
a. Setting a new lock screen password, even it's the same as the previous one.
b. Wiping /data in TWRP because even though I restore the backup the lock screen password gets broken requiring me to do the following:
i. Run the following commands in TWRP Terminal to remove the current password before rebooting the system:
Code:
cd /data/system
rm gatekeeper.* locksettings.*
ii. Set a new lock screen password (see point (a) above).
My details:
Phone: OnePlus 3T
OS: OxygenOS 5.0.1
Root: Magisk 15.3, Magisk Manager 5.5.5
Banking app: https://play.google.com/store/apps/details?id=au.com.nab.mobile
Security: Password set and required on start up; fingerprint setup
You don't mention anything about hiding the Manager. Does that make a difference?
Didgeridoohan said:
You don't mention anything about hiding the Manager. Does that make a difference?
Click to expand...
Click to collapse
I never considered that.
I may try that to see if it makes a difference.
Sent from my OnePlus3T using XDA Labs
BillGoss said:
I never considered that.
I may try that to see if it makes a difference.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
For some apps it makes all the difference...
If you haven't checked it out already, there's a bunch of tips like that in the troubleshooting guide.
Different but somewhat related: Since I'm on a custom ROM, Magisk Hide doesn't properly enable passing SafetyNet. The only way I could get it to work was to enable Magisk Hide for specific apps and to install the Universal SafetyNet Fix module (https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431). Maybe you could try that module too and see if it helps.
Didgeridoohan said:
For some apps it makes all the difference...
If you haven't checked it out already, there's a bunch of tips like that in the troubleshooting guide.
Click to expand...
Click to collapse
So, I tried hiding Magisk Manager and now I can reboot the phone without causing issues for the banking app. Thanks very much for the suggestion!
I did read [some of ] the installation and trouble shooting guide but, even now, I wouldn't have tried hiding the manager because my app can be set up properly without issues. It's only the reboot that caused problems. And hiding the manager has fixed this.
I've updated the OP to reflect this.
Sent from my OnePlus3T using XDA Labs
I am curious if anyone has gotten Chase Pay working with Magisk installed. I have turned off xposed ( which is known to fail safetynet), turned on magisk hide, did Magisk random package regeneration, and passed safetynet, but Chase Pay still gives me the error of having root on my phone. My Android Pay is working just fine since I pass SafetyNet, but Chase Pay doesn't.
c19932 said:
I am curious if anyone has gotten Chase Pay working with Magisk installed. I have turned off xposed ( which is known to fail safetynet), turned on magisk hide, did Magisk random package regeneration, and passed safetynet, but Chase Pay still gives me the error of having root on my phone. My Android Pay is working just fine since I pass SafetyNet, but Chase Pay doesn't.
Click to expand...
Click to collapse
You may have skipped a step. At this point, try clearing the Chase Pay app data, reboot, then run and sign into Chase Pay again. That is, once it has "seen" Magisk, it remembers it until you clear its stored data.
At least, that works for me. The only thing that doesn't work is fingerprint sign-on. When I enable that in Chase Pay, it complains that the devices is rooted, and will not enable this feature. The rest of the app seems to work, however. If anyone finds a solution to that issue, please share.
I also have no issues with Android/google pay but chase pay is giving the root error.
I have done steps 1-6 without chase pay working properly. Is there any way to check the chase pay error log and see where it is getting stopped?
I don't think I have ever rooted my Galaxy S7 and I don't even know how.
But I am getting rooted/Malware error with Chase Pay ( I can login but does not let me pay)
I checked with couple applications such as root checker and safteynet and both say that I am not rooted and my phone pass the safety test. Anyone know what the problem is? and how to fix it?
Chase Pay is also saying my phone is rooted. I get beyond the intro so Magisk hide is working to some degree. After that when tapping the pay button is when I get the error.
Tuxedo.Bond said:
Chase Pay is also saying my phone is rooted. I get beyond the intro so Magisk hide is working to some degree. After that when tapping the pay button is when I get the error.
Click to expand...
Click to collapse
Did you hide Magisk Manager (in Magisk Manager>Settings) before setting up Chase Pay?
Screenshot of the settings after hiding by the Manager attached.
Sent from my OnePlus3T using XDA Labs
Yes, hiding Magisk Manager did the trick. Thanks!
BillGoss said:
Did you hide Magisk Manager (in Magisk Manager>Settings) before setting up Chase Pay?
Screenshot of the settings after hiding by the Manager attached.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
Hi
So I am about to try the same path for the NAB app. From reading the thread I need to
Magisk Manager
Hide for the app
hide the manager
clean the nab app data/cache
reboot
then start the NAB app'
tried that but app keeps crashing on attempting to create nab pay
EDIT
tried removing data/cache again - seemed to work.
So what happens if I unhide magisk manager ???
KeyzerSuze said:
Hi
So I am about to try the same path for the NAB app. From reading the thread I need to
Magisk Manager
Hide for the app
hide the manager
clean the nab app data/cache
reboot
then start the NAB app'
tried that but app keeps crashing on attempting to create nab pay
EDIT
tried removing data/cache again - seemed to work.
So what happens if I unhide magisk manager ???
Click to expand...
Click to collapse
If you unhide the manager, then NAB pay will stop working if you reboot.
I've also found that even with everything hidden, NAB pay will stop working after some time (a week?).
I've switched to Google Pay which works a lot better and doesn't require hiding the manager.
Sent from my OnePlus3T using XDA Labs
Didgeridoohan said:
You don't mention anything about hiding the Manager. Does that make a difference?
Click to expand...
Click to collapse
Thank you!
This is annoying the hell out of me. I can't get Chase Pay to work. I've gone into Titanium backup and deleted the data for the app. Went into app settings and deleted the storage & cache for the app. Made sure the app is hidden in Magisk and made sure Magisk is hidden. Rebooted phone and still says the app is detecting root. What am I doing wrong?
defens23 said:
This is annoying the hell out of me. I can't get Chase Pay to work. I've gone into Titanium backup and deleted the data for the app. Went into app settings and deleted the storage & cache for the app. Made sure the app is hidden in Magisk and made sure Magisk is hidden. Rebooted phone and still says the app is detecting root. What am I doing wrong?
Click to expand...
Click to collapse
Are you on Magisk 17.1 and have your removed the Magisk folder from your user storage (/sdcard)?
Sent from my OnePlus3T using XDA Labs
BillGoss said:
Are you on Magisk 17.1 and have your removed the Magisk folder from your user storage (/sdcard)?
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
Yes. I'm on 17.1. No I didn't delete the folder. I'll try that.
defens23 said:
Yes. I'm on 17.1. No I didn't delete the folder. I'll try that.
Click to expand...
Click to collapse
Delete the folder, delete the Chase app storage, reboot.
Sent from my OnePlus3T using XDA Labs
My device is xperia xz1 running android 9.0.
magisk manager 7.3.2
Kernel are modified with Magisk 19.4.
My bank app has worked with magisk (magisk repacked and hide) But a few days ago the app was updated and it will not run. It prompt me that phone is rooted.
So the app has ben changed and now it will not work even if magisk hide is activated and magisk app are repacked.
I have tried uninstalling the app and deleted cahce and data but nothing seems to work.
This app has always ben a pain to get working when magisk are installed but has ben working until last update.
I have 2 other bank apps that works fine and witout any issues.
Anyone have any ideas to trick the app
link to the app
https://play.google.com/store/apps/details?id=dk.bec.android.mb1.b00369.prod&hl=en_US
kind regards Torben5247
Probably using the ridiculous UDS & stat detection. Until @topjohnwu updates MagiskHide for that (he's already got a method, just needs the time to implement it) there is a workaround that you can find if you just search the forum here.
I had a problem with a local banking app. Running magisk in core only mode solved it.
Sent from my SM-N950F using Tapatalk
This app has been working again since we got the ability to repackage the manager under a different name. That is until now with the most recent update where it detects root once again.
I am using magisk hide, changed package name, and use core only mode and it still detects it. Any help?
I have tested the latest version 6.11.1-34. I was able to bypass root detection . You need to hide all root apps using SudoHide.
Hi, I've been trying to move an app to system priv app but I keep on failing. I rooted my phone with magisk with TWRP and then tried to move the app using Lucky Patcher but it gives me Error: Not enough space in internal memory. I downloaded Link2SD and looked into my internal storage and it showed full with 0 free space. I tried to remove some apps that I don't care about and then move my app to system, but when it reboots, the phone stucks in MI screen and never turns on. I tried going into recovery and restore a back up but it also gives me Error and doesn't turns on. Can anyone help me?
Pd: I also tried moving the app directly from the recovery, and happens the same, the phone doesn't turns on.
Verdo95 said:
Hi, I've been trying to move an app to system priv app but I keep on failing. I rooted my phone with magisk with TWRP and then tried to move the app using Lucky Patcher but it gives me Error: Not enough space in internal memory. I downloaded Link2SD and looked into my internal storage and it showed full with 0 free space. I tried to remove some apps that I don't care about and then move my app to system, but when it reboots, the phone stucks in MI screen and never turns on. I tried going into recovery and restore a back up but it also gives me Error and doesn't turns on. Can anyone help me?
Pd: I also tried moving the app directly from the recovery, and happens the same, the phone doesn't turns on.
Click to expand...
Click to collapse
There's a magisk module to convert user apps to system apps. I think it was called systemizer
Its easy on android 9 you copy the apk to a new folder in priv-apps like so -
-priv-app/FolderName/FolderName.apk
( FolderName-FolderName.apk must have the same name ) (duplicate R/W + ownership permissions from any other folder in priv-app for the FolderName and FolderName.apk if your File manager doesn't do it automatically = FolderName(0755) , FolderName.apk(0644) , both group and owner set to root , reboot
or use app systemizer
On Android 10 read the above post app systemizer , very easy to use , install directly from magisk manager repo , reboot then you will need teminal emulator to run :
su
systemize
sidenote , MIUI doesn't like its system partition beeing modified very easy to get stuck at boot screen , be very careful
also not all apps work well as system apps
app systemizer is safer
I have MIUI 11 with Android 10. Thanks for your answers, can you give me a guide to use that systemizer module or where to get it?
Verdo95 said:
I have MIUI 11 with Android 10. Thanks for your answers, can you give me a guide to use that systemizer module or where to get it?
Click to expand...
Click to collapse
I've never used that magisk module. But I think that in the module description you could get more info about how to use it. To install it you just go to Magisk Manager > Modules > Search > systemizer > tap on the module to read more, or to install, tap on the download button. That's it
ffpp.2003 said:
I've never used that magisk module. But I think that in the module description you could get more info about how to use it. To install it you just go to Magisk Manager > Modules > Search > systemizer > tap on the module to read more, or to install, tap on the download button. That's it
Click to expand...
Click to collapse
Thanks for your advices, I'm gonna try it
This is my only financial app that won't work. BDO is a Philippines bank. My US banking apps all open fine.
I'm on EU 12.5.7 Stable. Flashed to 12.5.7 around ~2 weeks ago.
Anyway around this? BDO is possibly the worst banking app on earth - so I'm not entirely surprised it appears to be drunk here.
Thanks in advance!
Move to union bank or metro
You need to root and use Magisk...... then enable Magisk Hide and rename Magisk Manager. That is the only way if you unlocked the bootloader.
dhwalker6 said:
This is my only financial app that won't work. BDO is a Philippines bank. My US banking apps all open fine.
I'm on EU 12.5.7 Stable. Flashed to 12.5.7 around ~2 weeks ago.
Anyway around this? BDO is possibly the worst banking app on earth - so I'm not entirely surprised it appears to be drunk here.
Thanks in advance!
Click to expand...
Click to collapse
Delete the twrp folder using a file explorer app ( it will be empty and safe to delete) and the message goes away and you can install. I tried this for another user.
Sathelp said:
Delete the twrp folder using a file explorer app ( it will be empty and safe to delete) and the message goes away and you can install. I tried this for another user.
Click to expand...
Click to collapse
This worked - ty!
What's the path of that folder?
It is just in the normal storage, like where you download and documents folder sit.
You mean SD Card (internal)root directory? I have no TWRP folder in that directory.
BDO Digital Banking app opens but can't log-in, BDO Online app opens then close after the popup of Poterntial suspicious activity
I refer to the Xiaomi EU ROM. This has an open bootloader but shows as locked. If you are using a different ROM, then may be it won't work the same. If you have never installed twrp, then you won't have the folder.
I've had a lot of trouble with the BDO app, but I just got it working, on a Note 10 pro, running MIUI 12.5.9, unlocked and rooted. I'm not sure if all of these things were necessary, but this is what I did.
1. Delete the TWRP folder on the phone
2. Changed the name of Magisk in it's settings (I used Mi Cloud).
3. Added the BDO app to the DenyList, with Enforce DenyList on.
4. Added the Universal SafetyNet Fix module to Magisk.
SafetyNet passes, and DRM Info shows Widevine L1, and Netflix also works, for what it's worth.
Doesn't work for me. I even unroot my phone (Poco F1, EU ROM) but still got the error.
Will just use their website instead
BDO is so sht. Deleting the TWRP folder worked for me. Thanks!
With magisk you can hide root from apps
Since the BDO app update on Nov. 21, 2022, it's been broken again. Even with Magisk 25.2, Universal SafetyNetFix 2.4.0, with the app on the DenyList (enforced). I had a backup of the old app v6.2, so I restored that, and that's what I've been using. It only works for quick balance now, though, they disabled full access.
It may not be Magisk. In the past, if it detected a TWRP folder, that would do it. It could be something like that again, but not sure what. There's no TWRP folder, of course. v6.2 doesn't complain.
How to Hide Root from Apps via Magisk DenyList [Android 13]
In this comprehensive guide, we will show you the steps to hide root from apps and games using Magisk Denylist on Android 12.
www.droidwin.com
And all is good
That Is done already, and YASNAC passes. The new BDO app v6.3 still fails.
Tested both BDO banking and BDO online out of curiosity. Got the jailbreak/rooted device message at first.
After i deleted TWRP folder, tried again and can get to login screen , no more warnings.
I'm on xiaomi.eu V14.0.6 TKACNXM , not rooted.BDO app tested is v6.3.
Interesting. I did more testing with it today, but still no luck with it. I'm also running xiaomi.eu, but rooted, which I need for other things.
I do notice, under the DenyList, in addition to:
www.mobile.bdo.com.ph
There's a second entry for v6.3 that isn't there on v6.2:
www.mobile.bdo.com.ph_zygote
Both are checked, though. I also checked again to make sure there weren't any twrp folders I could find anywhere, so I don't think it's that.
I finally got the BDO app working with magisk and xiaomi.eu (I'm on 14.0.1.0 now, android 13), by using Magisk Delta, which is not official magisk.
[Discussion] Magisk Delta - Another unofficial third-party Magisk fork
This is not an officially supported topjohnwu project. If you are looking for official Magisk source, please go to this page Introduction Custom Magisk fork by HuskyDG. Sync with official Magisk adding back MagiskHide...
forum.xda-developers.com
It works with Magisk Delta, Zygisk, and SuList.
I could not get it to work with official Magisk v25.2. It may work with the later canary builds, but I haven't tried it. Also, to be clear, the BDO app works with xiaomi.eu without a problem if I'm not using magisk. Either way, though, you need to delete any TWRP folders.