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
Hello, everyone.
Few days ago, I found Hanabank app (com.hanabank.ebk.channel.android.hananbank) detects Magisk hide. I ran strace against Hanabank app, and I got some suspicious openat(2) returns -EACCES and even some files are not filtered by Magisk Hide (returns file descriptor successfully)
Here are openat(2) calls which don't look good.
Code:
[pid 27855] openat(AT_FDCWD, "/sbin_orig/magisk", O_RDONLY|O_LARGEFILE) = 91
[pid 27855] openat(AT_FDCWD, "/dev/magisk/mirror/system", O_RDONLY|O_LARGEFILE) = -1 EACCES (Permission denied)
[pid 27855] openat(AT_FDCWD, "/magisk", O_RDONLY|O_LARGEFILE) = -1 EACCES (Permission denied)
[pid 27855] fstatat64(AT_FDCWD, "99-magisk.sh", {st_mode=S_IFREG|0755, st_size=2011, ...}, 0) = 0
Full strace log of Hanabank app:
Code:
https://pastebin.com/BUiViAbK
I think they should return -ENOENT to pass that magisk detection routine.
I'm using Magisk v14.0
BTW, why Magisk Github issue tracker is disabled?
Having the same issue but with another app.
https://forum.xda-developers.com/showpost.php?p=73968022&postcount=19348
How did you run strace? I used strace -f -p PID-o /sdcard/strace.txt but no reference to Magisk is shown.
olivercervera said:
Having the same issue but with another app.
https://forum.xda-developers.com/showpost.php?p=73968022&postcount=19348
How did you run strace? I used strace -f -p PID-o /sdcard/strace.txt but no reference to Magisk is shown.
Click to expand...
Click to collapse
First, sorry for late reply. I was on vacation.
I used this script to attach strace to fresh app process.
Code:
while true; do
while ! ps | grep -q -i $1; do :; done;
ps | grep -i $1 | while read a b c; do
strace -e open -f -e trace=file,ptrace -p $b 2>&1;
done;
done
For example, if you saved this script as /sdcard/strace.sh, The procedure I take to attach strace to the app is;
1. use killall command to kill all app process. Android pre-forks app, so we need to kill that first.
2. run script using sh /sdcard/strace.sh <app_process_name>. This will attach strace to the app and redirects strace's stderr output to stdout.
2-1. Do whatever you want (use tee or just redirect it to file, etc..) with stdout stream.
3. Analyze collected result.
That's all.
perillamint said:
First, sorry for late reply. I was on vacation.
I used this script to attach strace to fresh app process.
Click to expand...
Click to collapse
Hi
Just now I realised that I responded in the other thread. However your script never worked
I ran the script in a shell with root permission using
Code:
sh /sdcard/strace.sh com.barclays.android.barclaysmobilebanking
Unfortunately this is what I get when I try to run the script
Code:
/sdcard/strace.sh[5]: syntax error: 'done' unexpected
What have I done wrong?
EDIT: I've done this test on another device, a Nexus 5X stock 7.1.2 + Magisk v14. If I run strace it is not found, I have installed busybox but nothing! WAT??? I'll test with the other device later which has strace (Nexus 5).
EDIT2: Nope, I get the same error on the device which has strace.
olivercervera said:
Hi
Just now I realised that I responded in the other thread. However your script never worked
I ran the script in a shell with root permission using
Code:
sh /sdcard/strace.sh com.barclays.android.barclaysmobilebanking
Unfortunately this is what I get when I try to run the script
Code:
/sdcard/strace.sh[5]: syntax error: 'done' unexpected
What have I done wrong?
EDIT: I've done this test on another device, a Nexus 5X stock 7.1.2 + Magisk v14. If I run strace it is not found, I have installed busybox but nothing! WAT??? I'll test with the other device later which has strace (Nexus 5).
EDIT2: Nope, I get the same error on the device which has strace.
Click to expand...
Click to collapse
Hmm, I used sh which included in LineageOS.... I think Android's default sh couldn't handle that script's syntax properly. Default sh is quite crippled compared to GNU/Linux's one (bash, zsh, etc..)
Could you try running this script using bash instead of sh? If you don't have bash on your Android system, this Magisk module could inject bash binary into your system. https://forum.xda-developers.com/apps/magisk/module-magisk-bash-shell-t3609988
perillamint said:
Hmm, I used sh which included in LineageOS.... I think Android's default sh couldn't handle that script's syntax properly. Default sh is quite crippled compared to GNU/Linux's one (bash, zsh, etc..)
Could you try running this script using bash instead of sh? If you don't have bash on your Android system, this Magisk module could inject bash binary into your system. https://forum.xda-developers.com/apps/magisk/module-magisk-bash-shell-t3609988
Click to expand...
Click to collapse
Thanks for your suggestion. In the end I installed LOS on my test device and ran the script.
The funny thing is that I can't find a single reference to Magisk or Root...
The output is attached.
olivercervera said:
Thanks for your suggestion. In the end I installed LOS on my test device and ran the script.
The funny thing is that I can't find a single reference to Magisk or Root...
The output is attached.
Click to expand...
Click to collapse
Indeed. However the app dies shortly after reading the two property files:
/dev/__properties__/ubject_r:default_prop:s0
/dev/__properties__/ubject_r:logd_prop:s0
I would try to get the output of getprop with and without Magisk installed and see if there are any properties being leaked that could give a hint that Magisk is installed.
Fif_ said:
Indeed. However the app dies shortly after reading the two property files:
/dev/__properties__/ubject_r:default_prop:s0
/dev/__properties__/ubject_r:logd_prop:s0
I would try to get the output of getprop with and without Magisk installed and see if there are any properties being leaked that could give a hint that Magisk is installed.
Click to expand...
Click to collapse
You are the man! You definitely spotted the method being used by this app. Thanks.
I had to leave LOS ROM because even without Magisk it would not run, so I installed another ROM. I verified the app runs, got props, installed Magisk and got new props.
There are all changes:
1. [ro.build.selinux]: [1] is changed to [ro.build.selinux]: [0] when Magisk is installed
2. [ro.runtime.firstboot] shows different values but I believe it's fine
3. The following are entirely missing when Magisk is installed
[selinux.reload_policy]: [1]
[service.adb.tcp.port]: [-1]
[sys.retaildemo.enabled]: [0]
[init.svc.clear-bcb]: [stopped]
I have the feeling that [ro.build.selinux]: [1] and [selinux.reload_policy]: [1] are key elements and Magisk is not hiding them properly. I would suppose these elements show that SELinux is not enforcing anymore. I tried changing these values, but at reboot they don't change.
I know obviously Magisk does not enforce SELinux, but hides that got set to Permissive. System thinks that is enforcing, and using command getenforce i get as a result Enforcing, but Barclays (and possibly other apps) are reading that SELinux is not actually being enforced.
Interesting. Will post these finding in the main thread.
Do you have anything to add that could be helpful?
olivercervera said:
You are the man! You definitely spotted the method being used by this app. Thanks.
I had to leave LOS ROM because even without Magisk it would not run, so I installed another ROM. I verified the app runs, got props, installed Magisk and got new props.
There are all changes:
1. [ro.build.selinux]: [1] is changed to [ro.build.selinux]: [0] when Magisk is installed
2. [ro.runtime.firstboot] shows different values but I believe it's fine
3. The following are entirely missing when Magisk is installed
[selinux.reload_policy]: [1]
[service.adb.tcp.port]: [-1]
[sys.retaildemo.enabled]: [0]
[init.svc.clear-bcb]: [stopped]
I have the feeling that [ro.build.selinux]: [1] and [selinux.reload_policy]: [1] are key elements and Magisk is not hiding them properly. I would suppose these elements show that SELinux is not enforcing anymore. I tried changing these values, but at reboot they don't change.
I know obviously Magisk does not enforce SELinux, but hides that got set to Permissive. System thinks that is enforcing, and using command getenforce i get as a result Enforcing, but Barclays (and possibly other apps) are reading that SELinux is not actually being enforced.
Interesting. Will post these finding in the main thread.
Do you have anything to add that could be helpful?
Click to expand...
Click to collapse
If you use "resetprop ro.build.selinux 1" in a root shell, does the app start?
That will disappear at reboot of course, but it's easy to add to /magisk/.core/props to make it stick until Magisk is fixed.
Now, I don't think Magisk disables SELinux, why do you have it disabled?
Fif_ said:
If you use "resetprop ro.build.selinux 1" in a root shell, does the app start?
That will disappear at reboot of course, but it's easy to add to /magisk/.core/props to make it stick until Magisk is fixed.
Now, I don't think Magisk disables SELinux, why do you have it disabled?
Click to expand...
Click to collapse
Yes, Magisk changes SELinux to Permissive and hides this status.
Although my findings would be legit and those props should be hidden, in my Bank's case is not the issue.
I have discovered that if I uninstall Magisk Manager (but not uninstall root, just the app) my bank app works. However it does not work if I use "Hide Magisk".
Since the hidden app is called Unhide Magisk Manager, probably this app is looking for Magisk keyword.
For whatever reason when I run strace the app does crash and always reports that message (crash after reading prop).
I will post these findings in the support thread.
I don't know how to do it, but I would recompile Magisk Manager changing package ID and name, in theory should work.
I am having the same issue on my Galaxy S8 with the Barclays Mobile Banking app. I have tried using every option in Magisk but nothing seems to be working. In fact, the Barclays app actually asked for SU permissions when I first ran it which is odd to me.
Did anyone find a workaround for this? I read the posts in this thread but I am not savvy enough to understand all the codes and technical information written, so please excuse my ignorance in the matter. Is reverting to a completely stock ROM my only option at this point? I really need to start using this application as soon as possible.
Thank you.
Quick update guys!
The great Topjohnwu is working on a new update that includes a key feature for us: reinstalling Magisk Manager with a random package ID.
These changes are in his Github Repo. On this thread you can find unofficial versions of Magisk compiled from Github.
I have tested Magisk-v14.4-20171102-091345.zip: HELL IT WORKS!
In Magisk Manager: go to settings and you will have the option to reinstall Magisk Manager with a random package ID
Install Barclays from Play Store
Add Barclays to Magisk Hide
Open Barclays, it will behave correctly and will work!
This solves my problem, so I will be able to use the latest version of this app very soon (will wait for public beta).
On a side note, this update should als hide /Magisk partition, which was detected by @perillamint banking app, so might be worth trying it.
I have installed this Hanabank app (hopefully is the right one!) and added it to Magisk Hide. The app opens up correctly but I can't understand anything. I see some stuff moving on screen and on the upper left I see a lock icon (to login?)
If I don't add the app to Magisk Hide it shows an incomprehensible message and closes.
Hope you find this helpful.
Please see photos below.
@olivercervera
What are your exact steps? I installed the latest version from this thread, and added barclays to magisk hide, and then in settings, clicked in hide magisk manager. When I clicked in unhide magisk manager, it asked me for root permision for something with a random name, so I guess it worked, but I couldn't get the Barclays app to run. Is that a fresh install of your phone? I remember that if it detected your root once, it would be blocked forever, until you get a new ID. Did you call barclays to get your app working again?
On top of that, I clicked on hide magisk manager again, and now I can't unhide it, the app does nothing when I click on it... :crying:
Thanks for your help in any case, and thanks for the tip regading the new functionality!
mundodisco8 said:
@olivercervera
What are your exact steps? I installed the latest version from this thread, and added barclays to magisk hide, and then in settings, clicked in hide magisk manager. When I clicked in unhide magisk manager, it asked me for root permision for something with a random name, so I guess it worked, but I couldn't get the Barclays app to run. Is that a fresh install of your phone? I remember that if it detected your root once, it would be blocked forever, until you get a new ID. Did you call barclays to get your app working again?
On top of that, I clicked on hide magisk manager again, and now I can't unhide it, the app does nothing when I click on it... :crying:
Thanks for your help in any case, and thanks for the tip regading the new functionality!
Click to expand...
Click to collapse
Yes, a fresh start from a stock Nexus 5X I have at work. I did not register the app with my account during the test, all I needed to do was to get to the Welcome Screen: if Barclays detects root you don't get anything. Probably you need to reinstall Barclays App.
Once Magisk Manager is hidden with the new ID you can't go back to the original: you don't have any option. So if you still have it means there is a problem.
mundodisco8 said:
@olivercervera
What are your exact steps? I installed the latest version from this thread, and added barclays to magisk hide, and then in settings, clicked in hide magisk manager. When I clicked in unhide magisk manager, it asked me for root permision for something with a random name, so I guess it worked, but I couldn't get the Barclays app to run. Is that a fresh install of your phone? I remember that if it detected your root once, it would be blocked forever, until you get a new ID. Did you call barclays to get your app working again?
On top of that, I clicked on hide magisk manager again, and now I can't unhide it, the app does nothing when I click on it... :crying:
Thanks for your help in any case, and thanks for the tip regading the new functionality!
Click to expand...
Click to collapse
He's talking about a new Hide Manager feature that is much improved from the current implementation. It's not yet available officially, so you'll have to build yourself from the GitHub repo, or download from the unofficial snapshots thread that @olivercervera linked.
Didgeridoohan said:
He's talking about a new Hide Manager feature that is much improved from the current implementation. It's not yet available officially, so you'll have to build yourself from the GitHub repo, or download from the unofficial snapshots thread that @olivercervera linked.
Click to expand...
Click to collapse
I didn't even consider the possibility he didn't realise I was using the unofficial/self compiled version... I even linked it!!!
Thanks
olivercervera said:
I didn't even consider the possibility he didn't realise I was using the unofficial/self compiled version... I even linked it!!!
Thanks
Click to expand...
Click to collapse
It's actually quite apparent that he's talking about the current implementation, since the updated, unreleased, feature doesn't have anything named "unhide" to click.
With the new implementation you unhide the hidden Manager by reinstalling and opening it.
Hi guys,
Yes, I installed the latest version, following the link OliverCervera linked. I hid it using the usual method of going to options/hide magisk, and I got a new app, as usual. clicking on it to unhide prompted for root permissions for an app with a random ID (as expected). The next time, I wasn't that lucky, and the whole thing crashed. Anyway, it's a nightly, so I won't complain, and I will check it later, as sadly I don't have time to do it now.
In any case, my app was marked, because I opened it with the official release of Magisk and it detected root, and once it does, it keeps the "this phone is rooted" status until you do a factory reset. I think you can call them to tell them that it was a mistake, and they can unlock it but I'm not 100% sure about this last point.
Thanks for the work, anyway!
mundodisco8 said:
Hi guys,
Yes, I installed the latest version, following the link OliverCervera linked. I hid it using the usual method of going to options/hide magisk, and I got a new app, as usual. clicking on it to unhide prompted for root permissions for an app with a random ID (as expected). The next time, I wasn't that lucky, and the whole thing crashed. Anyway, it's a nightly, so I won't complain, and I will check it later, as sadly I don't have time to do it now.
In any case, my app was marked, because I opened it with the official release of Magisk and it detected root, and once it does, it keeps the "this phone is rooted" status until you do a factory reset. I think you can call them to tell them that it was a mistake, and they can unlock it but I'm not 100% sure about this last point.
Thanks for the work, anyway!
Click to expand...
Click to collapse
If you install the correct version of the Manager you won't have an unhide app after hiding the Manager. That's changed...
Your problem is probably that the unofficial Manager has a different signature, so it won't install over the official Manager. Solution: Uninstall the official Manager before installing the unofficial snapshot.
Have you tried just clearing all data for the app after it detects root? That usually works for an app that "remembers" root. But, I've never tested the app in question so...
Didgeridoohan said:
If you install the correct version of the Manager you won't have an unhide app after hiding the Manager. That's changed...
Your problem is probably that the unofficial Manager has a different signature, so it won't install over the official Manager. Solution: Uninstall the official Manager before installing the unofficial snapshot.
Have you tried just clearing all data for the app after it detects root? That usually works for an app that "remembers" root. But, I've never tested the app in question so...
Click to expand...
Click to collapse
I think they keep your signature and store it on their servers. Barclays is really focused when it comes to not allowing people to use their app on rooted phones, but as I said, I would need to double check. And I kind of get why they do it, as they went all the way to avoid to pay Android to use Android Pay and they developed their own platform to pay over NFC (not judging here, it's up to them if they think it's the best solution). At the end of the day, root is exploited through a security flaw, and "the bad guys could get your moneys", and even though they could display a message at launch that says "hey, you are rooted, the bad guys could get AAAALLL of the moneys, it's up to you" people would still want to sue them if they mess up... but it's funny that they allow you to get into the online banking web on a rooted phone, where the bad guys could see your password...
Hi,
i have an Moto Z with latest stock rom and magisk 14.2 installed via twrp.
The problem: When i tick an app in hide settings, the entry wasnt saved. When i leave magisk and open the hide setting again, the app wasnt enabled for hide, i can tick it again and gain but it wasnt save.
Can someone help, whats the problem ?
IIRC, the Moto Z is one of the devices with a broken f2fs implementation. The Magisk image can't be mounted, so there's no Hide list to save anything to...
IIRC again, you should be able to get it working if you enable Core Only Mode in the Manager settings, but any apps added to the Hide list will be reset on a reboot.
You could also take a look in your device's forum if there are any custom kernels available with a f2fs fix.
Thanks for the explanation. The Moto Z has unfortunately no good dev support. So i found out that after reboot i must untick the hide option in magisk setting and tick again, then i can tick my app for hide and it was remembered, until next boot.
Didgeridoohan said:
IIRC, the Moto Z is one of the devices with a broken f2fs implementation. The Magisk image can't be mounted, so there's no Hide list to save anything to...
IIRC again, you should be able to get it working if you enable Core Only Mode in the Manager settings, but any apps added to the Hide list will be reset on a reboot.
You could also take a look in your device's forum if there are any custom kernels available with a f2fs fix.
Click to expand...
Click to collapse
tasar said:
Hi,
i have an Moto Z with latest stock rom and magisk 14.2 installed via twrp.
The problem: When i tick an app in hide settings, the entry wasnt saved. When i leave magisk and open the hide setting again, the app wasnt enabled for hide, i can tick it again and gain but it wasnt save.
Can someone help, whats the problem ?
Click to expand...
Click to collapse
tasar said:
Thanks for the explanation. The Moto Z has unfortunately no good dev support. So i found out that after reboot i must untick the hide option in magisk setting and tick again, then i can tick my app for hide and it was remembered, until next boot.
Click to expand...
Click to collapse
I am using version 14.0 and have experienced the same problem.
Check the logs stored in the /cache folder to determine the cause.
solution:
Create a folder called /magisk/.core and create an empty file called hidelist in it.
shell command:
mkdir /magisk/.core
touch /magisk/.core/hidelist
I have the same idea but the file system is read only. How to make it rw?
I'm using stock Note 3 (N9005DXSGBQA1) and followed instructions for magisk manager. I got it rooted but magiskhide does NOT work - NOT SAVING ANY SELECTION.
I tried using "core only" and tried inserting a new hidelist but both failed. I badly need the hidelist feature. How can I make magiskhide work? Thanks
dknight178 said:
I'm using stock Note 3 (N9005DXSGBQA1) and followed instructions for magisk manager. I got it rooted but magiskhide does NOT work - NOT SAVING ANY SELECTION.
I tried using "core only" and tried inserting a new hidelist but both failed. I badly need the hidelist feature. How can I make magiskhide work? Thanks
Click to expand...
Click to collapse
Three years later... (I'm still using my Note 3 from 2013, btw)... and did you ever find a solution to this problem? I'm using Magisk 20.3 now, and it still does not keep the "Magisk Hide" option enabled after closing the app.
So enable it, I open the app and go to settings and enable it from there. I must then back out and close the app for the Magisk Hide option to become available under the menu. If I back out of the app again, whatever I had checked as hidden under the "Magisk Hide" menu becomes unchecked again. If I reboot the phone, I have to go back into settings to enable Magisk Hide again.
Any solution for this other than use another device?
Magisk Hide (Masking Magisk SuperUser) - 2 Problems w/ Magisk Hide being disabled after reboot or closing Magisk Manager.
If you are using Magisk Manager and Magisk Root and are experiencing difficulty with Magisk Hide (Masking Magisk's SU) not showing in the Manager's side-menu or remembering its status in settings, it occurs when a file is not automatically deleted and removed.
PROBLEM:
Open Magisk Manager, Settings >> Enable Magisk Hide, close Manager, re-open and Magisk Hide is disabled and not visible (hidden) in the left side-menu. i.e. Exit, Close, Stop, Re-Open & Reboot Reset's Magisk Hide's State to Disabled.
SOLUTION 1.
Force stopped Magisk Manager.
Backup then Delete file /data/property/persist.magisk.hide (0600).
Launch Magisk Manager.
Go to Settings >> Enable Magisk Hide.
Go back to Manager home screen. Swipe to reveal side-menu and check Magisk Hide menu is visible.
Close Magisk Manager or Force stop.
Reopen and Swipe side-menu and confirm Magisk Hide is still visible!
I hope this helps others also experiencing issues with Hiding Super User SU. Thanks Shak!
SOLUTION 2.
Another Fix someone else has also posted Dec 2017 was in regards to an error "fopen: /magisk/.core/magiskhide/hidelist failed with 2: No such file or directory"
The issue is due to Magisk Manager being unable to save the list of ticked Apps to hide from SU to /magisk/.core/hidelist.
Check the existence of the "/magisk/.core/hidelist" path.
Create the "/hidelist" directory.
CHMOD "/magisk/.core/hidelist" to 0644.
Thanks to Dunderball. :highfive:
.
Thanks a lot! I have been looking this issue up for almost a week now.
Solution 1 worked for me.
No worries mate. Appreciate the feedback.
Someone else had a similar issue for a few weeks and was unable to resolve it until upgrading to 16.4 beta. But this isn't viable for everyone due to issues w/ 16.4+.
Thanks!
monsterkrusher said:
Thanks a lot! I have been looking this issue up for almost a week now.
Solution 1 worked for me.
Click to expand...
Click to collapse
I would like to add to this thread that this doesn't work anymore with the newer versions of magisk. Eget did work for me though was to delete (and backup of course) /data/adb/magisk.db and then restart
tgcGlaDius said:
I would like to add to this thread that this doesn't work anymore with the newer versions of magisk. Eget did work for me though was to delete (and backup of course) /data/adb/magisk.db and then restart
Click to expand...
Click to collapse
which version you use ?
I use version 19.4, wont work if delete magisk.db.
LineageOs 17 on a Nexus 2013 Flo
Magisk 19.3
Magisk Manager 7.3.2
safetynet always fails after a reboot.
I tried renaming magisk.db and while magisk kept working generally, m-hide still fails the safetynet test after a reboot until I toggle hide.
kevin mitnick said:
which version you use ?
I use version 19.4, wont work if delete magisk.db.
Click to expand...
Click to collapse
michaelh99 said:
LineageOs 17 on a Nexus 2013 Flo
Magisk 19.3
Magisk Manager 7.3.2
safetynet always fails after a reboot.
I tried renaming magisk.db and while magisk kept working generally, m-hide still fails the safetynet test after a reboot until I toggle hide.
Click to expand...
Click to collapse
Download The Module Of MultiFunctions From This Thread https://forum.xda-developers.com/apps/magisk/module-multifunctions-bootloop-t3933386 For Getting The Ability To Use Either The Sub-Function Of Hide Keeper Or Hide Enabler.
Dreamer(3MF) said:
Download The Module Of MultiFunctions From This Thread https://forum.xda-developers.com/apps/magisk/module-multifunctions-bootloop-t3933386 For Getting The Ability To Use Either The Sub-Function Of Hide Keeper Or Hide Enabler.
Click to expand...
Click to collapse
I'll have to try that sometime in the future when I've got more time to experiment. I ended up going back to stock just to have a working tablet. I only use it for maps and streaming and since Netflix wouldn't work...
How to make a bakup?
Hey all,
Android 7.1.1, Magisk 20.4 (on Stable update channel), Magisk Manager is hidden (as "Manager", tried "MM" as well) and the updated Sony app was added to Magisk Hide list.
Data & Cache were cleared for the app as well.
https://play.google.com/store/apps/details?id=com.playstation.remoteplay
But on launch, it crashes with error 88001003, which seems to indicate root detection.
The previous version 3.0 has worked flawlessly on the same system with same settings.
Does anyone know a workaround, could the app now be checking the system for root-compatible apps and block from there ?
Any way to find out how the app detects root?
Any feedback is very welcome.
Full Manager obfuscation capabilities aren't available on Android versions lower than 9. Could be what's causing your issues...
For what it's worth I can start the app just fine on my Android 9 OP3T with Canary build 21004 and hidden Canary Manager 310.
Try uninstalling the Manager and see if that makes a difference.
Log Cat info :
Code:
[10-15 14:29:26.760 4218:4218 D/PRCNT_#RecentsModel#]
#createTaskStack# :: task=PS Remote Play, isTopRunningTask=false, isVisible=false, isLocked=false, isKnoxTask=false, isHideThumbnail=false, isLongLive=false
Didgeridoohan said:
Try uninstalling the Manager and see if that makes a difference.
Click to expand...
Click to collapse
Sadly no difference (and deleted app's data + cache of course). Would you have any other ideas?
Spartacus500 said:
Log Cat info :
Code:
[10-15 14:29:26.760 4218:4218 D/PRCNT_#RecentsModel#]
#createTaskStack# :: task=PS Remote Play, isTopRunningTask=false, isVisible=false, isLocked=false, isKnoxTask=false, isHideThumbnail=false, isLongLive=false
Click to expand...
Click to collapse
Thanks but I'm not sure how it's supposed to help?
Ps24u said:
Sadly no difference (and deleted app's data + cache of course). Would you have any other ideas?
Click to expand...
Click to collapse
Many things may trigger detection, not only Magisk:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
Thanks Didgeridoohan, after many hours I found 2 culprits that triggered root detection on my system.
For the Sony Remote Play app mentionned in this thread: SELinux set to permissive was the culprit.
After disabling the Magisk module for SElinux, the app runs normally, no crash, all good.
But it's pretty annyoing having to reboot to enable/disable SELinux just to run this app.
Would you know if there's a way to either toggle SElinux in realtime while the os is running or to have the Sony app always believe SElinux is set to enforcing ?
For the second app, it was dumb, it looked for "twrp" folder on internal storage. After I renamed the folder, the app launches and runs perfectly.
But again it's far from ideal to do it manually all the time. So for this case also, is there a way to hide the "twrp" folder from this app, either via magisk module, script or otherwise?
Thanks a lot for your tips and awesome site, probably the best ressource for all things Magisk. :bow:
Ps24u said:
Would you know if there's a way to either toggle SElinux in realtime while the os is running or to have the Sony app always believe SElinux is set to enforcing ?
Click to expand...
Click to collapse
That's just a simple terminal command (which is exactly what the module uses and runs at boot). You can run that whenever and it'll change selinux to the state you want on the fly, no need for a reboot.
Permissive:
Code:
setenforce 0
Enforcing:
Code:
setenforce 1
Needs to be run as su, of course (you could add "su -c" in front of the command to make it easy).
You could either set up a script with an app like Tasker or use an app that's made for toggling selinux (if you look around there should be a few available).
For the second app, it was dumb, it looked for "twrp" folder on internal storage. After I renamed the folder, the app launches and runs perfectly.
But again it's far from ideal to do it manually all the time. So for this case also, is there a way to hide the "twrp" folder from this app, either via magisk module, script or otherwise?
Click to expand...
Click to collapse
To hide the TWRP directory you could use an isolation app to stop the app from detecting what you have on your device. When it comes up the internal storage, Storage isolation is the most powerful.
Another option could be to set up a Tasker task (or similar) that renames the folder and then launches the app. Another Tasker profile could then keep track of when the app is running and rename the folder again once it's closed. Or it might be more reliable to run a task manually when you're done with the app. I'm just mentioning this to show some options. It's nowhere near as elegant as using an isolation app...
Thanks a lot for your tips and awesome site, probably the best ressource for all things Magisk. :bow:
Click to expand...
Click to collapse
No worries, I'm glad you found it useful and could get things figured out.
Didgeridoohan said:
That's just a simple terminal command (which is exactly what the module uses and runs at boot). You can run that whenever and it'll change selinux to the state you want on the fly, no need for a reboot.
Permissive:
Code:
setenforce 0
Enforcing:
Code:
setenforce 1
Needs to be run as su, of course (you could add "su -c" in front of the command to make it easy).
You could either set up a script with an app like Tasker or use an app that's made for toggling selinux (if you look around there should be a few available).
Click to expand...
Click to collapse
That strangely doesn't do the trick. If SElinux is set to permissive at boot via Magisk module, toggling to Enforcing afterwards doesn't allow the app to launch (crashes with same error 88001003, even after deleting data+cache).
It seems the app somehow knows if SElinux was set to permissive on boot and doesn't care if SElinux is switched to Enforcing afterwards.
Due to how my setup works I need Permissive at boot (mount cifs folders) so I'm in pinch.
I use selinux_permissive_v2.zip on Magisk 20.4.
I also tried to set SElinux to permissive via a script in /data/adb/service.d
Code:
#!/system/bin/sh
setenforce 0
But same results, toggling to Enforcing afterwards doesn't allow the app to launch.
I tried toggling with "su -c setenforce 1" in Termux, and with SELinux Toggler.
However, If the phone boots with Enforcing, and then I toggle to Permissive after boot and then back to Enforcing, the app launches without issues, strange!
There is a mystery going on here...
Didgeridoohan said:
To hide the TWRP directory you could use an isolation app to stop the app from detecting what you have on your device. When it comes up the internal storage, Storage isolation is the most powerful.
Click to expand...
Click to collapse
That worked straight away, awesome!
On my Samsung Galaxy S7 edge Custom Pie 9.0 Rom NFE root Magisk, this application does not work, keeps saying "something went wrong", I changed the twrp folder to aaaTWRPaaa but still the application won't work. I also changed selinux mode changer to permisive, but after this change also doesn't work, my antivirus screams selinux permisive is dangerous. Any ideas ?
Spartacus500 said:
On my Samsung Galaxy S7 edge Custom Pie 9.0 Rom NFE root Magisk, this application does not work, keeps saying "something went wrong", I changed the twrp folder to aaaTWRPaaa but still the application won't work. I also changed selinux mode changer to permisive, but after this change also doesn't work, my antivirus screams selinux permisive is dangerous. Any ideas ?
Click to expand...
Click to collapse
From my testing, PS Remote Play doesn't care about TWRP folder.
Spartacus, for now try to boot with SElinux to Enforced, and clear data/cache for the app.
I hope Didgeridoohan can help solve the SElinux pemissive at boot mystery.
Ps24u said:
I hope Didgeridoohan can help solve the SElinux pemissive at boot mystery.
Click to expand...
Click to collapse
Not really... I've no idea why the app would behave like that.
But I have a thought: how do you set up your cifs folders mounting? With a script? If so, could you temporarily set SELinux permissive only during that time? If you're lucky, it might be that's enough... I have no idea how cifs folder mounting works, so I'm just throwing ideas aimed at your head.
Ps24u said:
From my testing, PS Remote Play doesn't care about TWRP folder.
Spartacus, for now try to boot with SElinux to Enforced, and clear data/cache for the app.
I hope Didgeridoohan can help solve the SElinux pemissive at boot mystery.
Click to expand...
Click to collapse
I did as you said, deleted the TWRP folder from internal storage, also deleted the Titanium backup folder, no result, Selinux I have enforcing, the application still shows an error on startup
I also have a question, is your audit error the same as mine? Maybe there is a bug here
audit (error)
Code:
type=1400 audit(1603135249.830:2343): avc: denied { read } for pid=7381 comm="zCloudWorkerThr" name="enforce" dev="selinuxfs" ino=4 scontext=u:r:untrusted_app:s0:c212,c259,c512,c768 tcontext=u:object_r:selinuxfs:s0 tclass=file permissive=1 SEPF_SM-N935F_9_0001 audit_filtered
Code:
type=1400 audit(1603135249.830:2344): avc: denied { open } for pid=7381 comm="zCloudWorkerThr" path="/sys/fs/selinux/enforce" dev="selinuxfs" ino=4 scontext=u:r:untrusted_app:s0:c212,c259,c512,c768 tcontext=u:object_r:selinuxfs:s0 tclass=file permissive=1 SEPF_SM-N935F_9_0001 audit_filtered
Didgeridoohan said:
Not really... I've no idea why the app would behave like that.
But I have a thought: how do you set up your cifs folders mounting? With a script? If so, could you temporarily set SELinux permissive only during that time? If you're lucky, it might be that's enough... I have no idea how cifs folder mounting works, so I'm just throwing ideas aimed at your head.
Click to expand...
Click to collapse
In the context of Cifs, I need SELinux permissive during actual use, not only during the mounting phase, so it cannot be done unfortunately.
Spartacus500 said:
I did as you said, deleted the TWRP folder from internal storage, also deleted the Titanium backup folder, no result, Selinux I have enforcing, the application still shows an error on startup
I also have a question, is your audit error the same as mine? Maybe there is a bug here
audit (error)
Click to expand...
Click to collapse
I'm not sure what / how to "audit" ?
I'm back again, Samsung Galaxy S7 edge Custom Pie 9.0 Rom. Selinux enforcing, PS Remote Play 4.0.0 keeps crashing, I uninstalled Magisk root and PS Remote Play 4.0.0 app works fine on my S7, I reload Magisk root via TWRP and PS Remote Play 4.0.0 shows error again ...
You've added PS Remote Play to the "Magisk Hide" list already, right ?
If not, add it, then clear data/cache or Uninstall and reinstall the app but don't launch it, and reboot.
Ps24u said:
You've added PS Remote Play to the "Magisk Hide" list already, right ?
If not, add it, then clear data/cache or Uninstall and reinstall the app but don't launch it, and reboot.
Click to expand...
Click to collapse
Of course, right after installing Magisk I hid hide root for PS Remote Play 4.0.0 and also changed the name of Magisk manager to something else, cleaning the memory for this application does not help either, every time I open the application it says "something went wrong" and error code ... All I need to do is remove the Magisk root and the app works. I'm using Magisk 20400, tested 21000 and Canary 21005 version and on neither of these versions this app shows the same error
Sorry I can't help more. I'm on Magisk 20.4 and M.Manager 7.5.1, also on Android 7.1.1 official Sony rom.
I performed the test, removed the Magisk root, PS Remote Play 4.0.0 works, when I install only Magisk manager, then PS REMOTE PLAY 4.0.0 detects Magisk and shows an error, after removing Magisk manager, PS Remote Play 4.0.0 works again, but it's enough that I will upload root Magisk, hide root hide, remove Magisk manager then PS Remote Play 4.0.0 shows error ...
I've got the same issue, anyone find a workaround?
Same here. This app work in the past, now it doesnt open. I dont know why Sony now dont left we use it because of root. It thinks that we will hack something. Mas, if Sony continues to do this and **** the past generation with last updates I will left consoles for while.
Im using Android 8.1