Database Develop

[BUG] MagiskHide does not work on Hanabank app. (strace log attached)

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...

Bypass DBS banking App

Resently BDS banking app(India) is updated.is there any modules to make that work...

Aniruddhlr said:
Resently BDS banking app(India) is updated.is there any modules to make that work...
Click to expand...
Click to collapse
This isn't xposed, so probably not. As long as your passing safetynet and enabled magisk hide for that and rebooted, in theory you should be fine. The next thing you can try is force closing the app and in Magisk manager, tapping "hide magisk manager" but that's only a temporary fix, some apps now check to see if magisk is installed at all. This will fix that

manor7777 said:
This isn't xposed, so probably not. As long as your passing safetynet and enabled magisk hide for that and rebooted, in theory you should be fine. The next thing you can try is force closing the app and in Magisk manager, tapping "hide magisk manager" but that's only a temporary fix, some apps now check to see if magisk is installed at all. This will fix that
Click to expand...
Click to collapse
Magisk is installed and passes safety net.
Still many banking apps detected root like BHIM.
And is there any way to hide custom ROM?

Aniruddhlr said:
Magisk is installed and passes safety net.
Still many banking apps detected root like BHIM.
And is there any way to hide custom ROM?
Click to expand...
Click to collapse
You can make a script to change the build information in the rom to release-keys instead of test-keys, some apps detect that. Also make sure you tick your banking app in Magisk hide settings. I believe there is a module so ewhere on the forum to do this, I will link it if I see it. Also you can try universal safetynet bypass module

manor7777 said:
You can make a script to change the build information in the rom to release-keys instead of test-keys, some apps detect that. Also make sure you tick your banking app in Magisk hide settings. I believe there is a module so ewhere on the forum to do this, I will link it if I see it. Also you can try universal safetynet bypass module
Click to expand...
Click to collapse
Thank you.ill try and tell you results.

Aniruddhlr said:
Magisk is installed and passes safety net.
Still many banking apps detected root like BHIM.
And is there any way to hide custom ROM?
Click to expand...
Click to collapse
manor7777 said:
You can make a script to change the build information in the rom to release-keys instead of test-keys, some apps detect that. Also make sure you tick your banking app in Magisk hide settings. I believe there is a module so ewhere on the forum to do this, I will link it if I see it. Also you can try universal safetynet bypass module
Click to expand...
Click to collapse
MagiskHide already changes the prop to release-keys (and some other props). And since SafetyNet already passes there's no need for the Universal SafetyNet Fix module.
Only thing to do is to add the app to the Hide list (no module needed for that) and also hide the Magisk Manager (there's an option for that in the Manager settings). Also make sure to use the latest release (currently v14.6 beta) since there's often improvements being done.
It's also possible that the app detects things like Developer options and USB Debugging being enabled. That can't be hidden by Magisk, so try disabling those if they're enabled.

Didgeridoohan said:
MagiskHide already changes the prop to release-keys (and some other props). And since SafetyNet already passes there's no need for the Universal SafetyNet Fix module.
Only thing to do is to add the app to the Hide list (no module needed for that) and also hide the Magisk Manager (there's an option for that in the Manager settings). Also make sure to use the latest release (currently v14.6 beta) since there's often improvements being done.
It's also possible that the app detects things like Developer options and USB Debugging being enabled. That can't be hidden by Magisk, so try disabling those if they're enabled.
Click to expand...
Click to collapse
Yeah just now I saw that release keys in build prop.
I'm not on beta is it safe to install beta(magisk).
I'll try those debugging things.

It's saying runtime tampering.what does it mean?

Aniruddhlr said:
Yeah just now I saw that release keys in build prop.
I'm not on beta is it safe to install beta(magisk).
I'll try those debugging things.
Click to expand...
Click to collapse
Beta is safe... The worst that can happen (that I've seen so far) is a bootloop that can be fixed by flashing a clean boot image or an earlier release (v14.5).
There might also be problems with the su database, but that should be fixed by uninstalling the app (from within the Manager, press Uninstall and choose Uninstall App) and reinstalling it.
It's worth it, since the Hide feature is much improved in v14.6.
---------- Post added at 12:21 ---------- Previous post was at 12:21 ----------
Aniruddhlr said:
It's saying runtime tampering.what does it mean?
Click to expand...
Click to collapse
What is saying that?

https://i.imgur.com/e2rAlNI.png

Didgeridoohan said:
Beta is safe... The worst that can happen (that I've seen so far) is a bootloop that can be fixed by flashing a clean boot image or an earlier release (v14.5).
There might also be problems with the su database, but that should be fixed by uninstalling the app (from within the Manager, press Uninstall and choose Uninstall App) and reinstalling it.
It's worth it, since the Hide feature is much improved in v14.6.
---------- Post added at 12:21 ---------- Previous post was at 12:21 ----------
What is saying that?
Click to expand...
Click to collapse
I added a image.see

Aniruddhlr said:
I added a image.see
Click to expand...
Click to collapse
Hello again.
Yes, I saw the image... But, the only thing you could try is to update Magisk and use the improved hiding features.
There are a few issues with the latest stable v15.0. Many Samsung and Huawei users are experiencing bootloops and some users have had forced encryption issues. Don't think I've seen any issues mentioned for Xiaomi devices though... Just make sure to have a backup and the latest Magisk uninstaller zip available and you should be good to go.
If you're feeling unsure about updating, wait... The issues are under investigation.

Didgeridoohan said:
Hello again.
Yes, I saw the image... But, the only thing you could try is to update Magisk and use the improved hiding features.
There are a few issues with the latest stable v15.0. Many Samsung and Huawei users are experiencing bootloops and some users have had forced encryption issues. Don't think I've seen any issues mentioned for Xiaomi devices though... Just make sure to have a backup and the latest Magisk uninstaller zip available and you should be good to go.
If you're feeling unsure about updating, wait... The issues are under investigation.
Click to expand...
Click to collapse
Thanks for that warning.
I already updated to 15v and found forced encryption issue.
Does runtime tampering have anything to do with this root?

Aniruddhlr said:
Thanks for that warning.
I already updated to 15v and found forced encryption issue.
Does runtime tampering have anything to do with this root?
Click to expand...
Click to collapse
Have you gotten v15.0 up and running? If not you could try again and uncheck "Preserve forced encryption" in the Manager before updating, or if you're flashing from recovery you could run the following code in the recovery terminal first:
Code:
echo KEEPFORCEENCRYPT=false>>/data/.magisk
Runtime tampering is probably just DBS's way of saying your device is rooted.
After getting v15.0 running, add the app to the Hide list and hide the Manager (option in settings). You might also have to clear data for the DBS app.
Also make sure that MagiskHide is working by checking SafetyNet. If at least basic integrity passes we know it does. If it doesn't, toggle MagiskHide off and on in the Manager settings and try again.

Hi, I am also facing same issue. My device is Zuk Z2 and am on Dot-OS rom. Magisk passes SafetyNet, have enabled Magisk Hide but still this DBS bank app detects root.
I also tried after disabling Developer options. Same error. What extra can be done?

+1
I need access to this app too whilst rooted with Magisk

tomdot said:
+1
I need access to this app too whilst rooted with Magisk
Click to expand...
Click to collapse
https://forum.xda-developers.com/apps/magisk/guide-magisk-troubleshooting-t3641417

DBS banking app finally works with Magisk 16.0 (with Magiskhide)

Mine can't work.. there no error code appearing when opening the app but the app hangs at "log in " and "register" page.. anyone can help please
I'm using ressurectiin remix on redmi note 5

tomdot said:
DBS banking app finally works with Magisk 16.0 (with Magiskhide)
Click to expand...
Click to collapse
yes it's work for me,
1st i check it in my hide list
and then i hide my magisk
if only i did my 1st choice it still give some warning and force close the app
thanks

[HELP] Hide Magisk Manager (Repackage) upgrades the version over the internet

I have my Samsung A30 (SM-A305F) rooted with magisk canery (87de0e7a) by flashing patched boot img via odin. Now, If i try to hide magisk with random package , it demands internet connection and install the latest version (9348c5ba). BUT i don't want to upgrade as the updated version has weird bug of rejecting SU automatically (with a very brief pop-up). I then need to ---> uninstall the repackaged app ---> Reboot ---> install 87de0e7a version ---> then it become functional again. I don't have TWRP installed. Re-flashing new patched boot requires wiping data. i don't want to do factory reset
Now I want to hide magisk as PUBG MOBILE might be crashing due to root detection. Please help me achieve solution:
(1) hide magisk manager without updating
(2) update magisk manager without that BUG of rejecting SU automatically

1 - Hide the Manager and let it update fully, no way around that. Then replace /data/user_de/0/com.H3.nuhw6UY.GoCgl/dyn/current.apk with the apk of whatever Manager version it is you want to use (and don't forget to set the same permissions and owner).
Edit: replace the package name above with the one your Manager uses.
2 - Seems to be a similar issue reported here: https://github.com/topjohnwu/Magisk/issues/2944
If there's anything to be done about it, it will be eventually.
If you can get some proper logs showing the su rejection and add to the above linked issue that would be great.

Note: i previously managed to hide it successfully when there was no newer version. It would just download the same version from the internet and repackage itself with random package name. But some days ago, i restored original manager and now i can't get it to hide.

Didgeridoohan said:
1 - Hide the Manager and let it update fully, no way around that. Then replace /data/user_de/0/com.H3.nuhw6UY.GoCgl/dyn/current.apk with the apk of whatever Manager version it is you want to use (and don't forget to set the same permissions).
2 - Seems to be a similar issue reported here: https://github.com/topjohnwu/Magisk/issues/2944
If there's anything to be done about it, it will be eventually.
If you can get some proper logs showing the su rejection and add to the above linked issue that would be great.
Click to expand...
Click to collapse
Thanks for replying. I followed our steps (com.mkhirsnpiw.z.kkt was used instead of com.H3.nuhw6UY.GoCgl). But it again says the same thing, "Upgrade to full magisk to finish the setup. Download and install?". Clicking ok upgrades it again

Shihabus Sakib Rad said:
Thanks for replying. I followed our steps (com.mkhirsnpiw.z.kkt was used instead of com.H3.nuhw6UY.GoCgl). But it again says the same thing, "Upgrade to full magisk to finish the setup. Download and install?". Clicking ok upgrades it again
Click to expand...
Click to collapse
Did you place the new current.apk file in the same directory and give it the proper permissions (same owner and permission 600)? I just tested and had no issues downgrading the hidden Manager to 285 this way.

Didgeridoohan said:
Did you place the new current.apk file in the same directory and give it the proper permissions (same owner and permission 600)? I just tested and had no issues downgrading the hidden Manager to 285 this way.
Click to expand...
Click to collapse
yes with MiXplorer.
When Manager updated itself , i tried to update the magisk ( not the manager). But it bricked my phone as it won't start. i had to flash stock firmware via odin. It happened what i feared about. Now, i will try to patch boot img with new version.

UPDATE: I patched and flashed boot img using canary 290. after rebooting , this time there was not that Bug of rejecting SU automatically. Root was functional. But when it asked to do additional setups, it was stuck on setup operation forever and when i tried to hide manager, it showed "hiding magisk manager failed". so i uninstalled canary 290 and installed 7.5.1 (267) . This time additional setup was completed and rebooted automatically. But there was some problem with su access. so i uninstalled 7.5.1 (267) and installed canary 290. Root is now functional and it does not ask for additional setup anymore. (meaning setup was complete?). But still shows "hiding magisk manager failed" when try to hide manager. I don't know what is the problem . I was using canary 284 without any problem. PUBG mobile was runnig without problem. Now I am tired......

About hiding the Manager failing:
https://www.didgeridoohan.com/magisk/Magisk#hn_Cant_hide_the_Magisk_Manager

Didgeridoohan said:
About hiding the Manager failing:
https://www.didgeridoohan.com/magisk/Magisk#hn_Cant_hide_the_Magisk_Manager
Click to expand...
Click to collapse
Disabling Play Protect Worked !!!! Thank you Sir :angel:

Magisk appears to be installed but no root

Hi
I have magisk installed but my phone is reporting not rooted.
My setup:
Xiaomi Redmi Note 7
Ressurection remix
Magisk 23.0
Things I've tried:
Disabled battery optimisation for magisk app
Reinstalled magisk a couple of times from twrp
Other root requiring apps (no change)
I've attached the logs from Root Checker, magisk and snip of my magisk. Please let me know if there is more info I can provide.
Thanks in advance for any suggestions!

re-flashing latest stable magisk.zip with the custom recovery then reboot to system and open the magisk wait to downloading requested resources and see..

Hi
Thanks for your reply.
I just downloaded this and flashed it with twrp: https://magisk.me/
Rebooted and found the same issue. Any other ideas?
Cheers
Oliver

arahknxs said:
Hi
Thanks for your reply.
I just downloaded this and flashed it with twrp: https://magisk.me/
Rebooted and found the same issue. Any other ideas?
Cheers
Oliver
Click to expand...
Click to collapse
1 - Don't use that website. The only place for verified and safe Magisk downloads is on John's Github:
https://github.com/topjohnwu/Magisk
2 - Exactly what is it that's reporting that your device isn't rooted? Because Magisk quite clearly says it is, according to your screenshot...

Didgeridoohan said:
1 - Don't use that website. The only place for verified and safe Magisk downloads is on John's Github:
https://github.com/topjohnwu/Magisk
2 - Exactly what is it that's reporting that your device isn't rooted? Because Magisk quite clearly says it is, according to your screenshot...
Click to expand...
Click to collapse
Hi
Thanks for the reply.
Okay so I went to Git and downloaded this file https://github.com/topjohnwu/Magisk/releases/download/v23.0/Magisk-v23.0.apk I then renamed it to .zip and flashed it via TWRP. Is this correct?
When I reboot I find the same situation. Magisk appears installed correctly however no app can access root. No popup appears to accept/reject the su request and apps behave as if no root access. I've tried Root Checker, Titanium Backup and am happy to try any others.
Do you have any suggestions please on what else I can try?
Cheers
ara

Ah... So the problem is not that you do not have root access The problem is that there's no superuser prompt when an app requests root.
IIRC there's a Xiaomi settings to allow apps to display popup messages (should be under app permissions). The Magisk app also need to be allowed to auto start. Of course, this is for MIUI and you're using RR so I have no idea if there is such a setting on your device currently...
Could of course be something completely different though.

Didgeridoohan said:
Ah... So the problem is not that you do not have root access The problem is that there's no superuser prompt when an app requests root.
IIRC there's a Xiaomi settings to allow apps to display popup messages (should be under app permissions). The Magisk app also need to be allowed to auto start. Of course, this is for MIUI and you're using RR so I have no idea if there is such a setting on your device currently...
Could of course be something completely different though.
Click to expand...
Click to collapse
Yes I suspect this is the issue - the notification is being blocked somehow.
Under app settings -> Magisk, I believe the settings are right:
Battery optimisation = off
Notifications = all allowed
There are plenty of guides out there of using RR with Magisk and no mention of any special settings to make it work.
I am also using nova launcher, I wonder if this could affect the notification somehow?
All suggestions welcome!
Cheers
ara

I noticed in Magisk under the Superuser tab, it just says "no app has asked for superuser permission yet." So perhaps not a notification issue after all?
I downloaded another app, "root checker basic". It also generated no popup, said I do not have root, and nothing appeared in the Magisk logs.
I feel like I am doing something wrong here but missing what it is.
Cheers
ara

arahknxs said:
I noticed in Magisk under the Superuser tab, it just says "no app has asked for superuser permission yet." So perhaps not a notification issue after all?
I downloaded another app, "root checker basic". It also generated no popup, said I do not have root, and nothing appeared in the Magisk logs.
I feel like I am doing something wrong here but missing what it is.
Cheers
ara
Click to expand...
Click to collapse
One thought: make sure that nothing is restricting the Magisk app from autostarting and running in the background.
Also, have you checked with other users of your ROM? Might be a good place to get help for stuff like this...

This happened to me before. I had to rename the same zip to "uninstall.zip" and flash it, reboot, and then rename the zip to something else like Magisk.zip and flash again.

dsiva said:
This happened to me before. I had to rename the same zip to "uninstall.zip" and flash it, reboot, and then rename the zip to something else like Magisk.zip and flash again.
Click to expand...
Click to collapse
Thanks for the suggestion, I tried this but no change afterwards unfortunately.
Also good idea @Didgeridoohan, I will cross post this on the forum for RR.

extract the boot.img and copy to phone. in Magisk, install and pick boot.img. copy the result file to pc, and flash using fastboot flash boot magi....img
if unlocked bootloader, flash direct and reboot.

arahknxs said:
Hi
I have magisk installed but my phone is reporting not rooted.
My setup:
Xiaomi Redmi Note 7
Ressurection remix
Magisk 23.0
Things I've tried:
Disabled battery optimisation for magisk app
Reinstalled magisk a couple of times from twrp
Other root requiring apps (no change)
I've attached the logs from Root Checker, magisk and snip of my magisk. Please let me know if there is more info I can provide.
Thanks in advance for any suggestions!
Click to expand...
Click to collapse
Rename the file to uninstall.zip then flash the firmware then flash the magisk it will work for sure i was also facing the same problem

Magisk Manager shows "Modules" and "Superuser" grayed out

First, I hope this thread is in the right place and apologize if it is not.
I currently have the problem that the Magisk Manager shows the two categories "Superuser" and "Modules" grayed out at the bottom. In addition, it is also so that the settings of the manager is slimmed down (fewer functions than usual). For this I have 2 screenshots ready: (see attachment and sorry for the German language).
Root itself is still there though (the apps that ask for root still do).
But can imagine that this happened because of the Magisk Hide app. Because I had hid the manager under a different app name, then either accidentally deleted it or restored the original package (can't remember).
In any case, I have already tried to install the manager with an SD card with the TWRP (did not work) and to install Magisk Manager via the apps themselves (pressed install in the first screenshot). This has come the following error message:
Code:
- Target image: /dev/block/
- Device platform: arm64-v8a
- Installing: 24.1 (24100)
! Unable to check signature
! Installation failed
My current status is that this has already happened once with the manager - judging by the bug reports on Github. Can someone please explain me in simple steps how to get this fixed? Thanks!

Bump

JulianKlein said:
Bump
Click to expand...
Click to collapse
No need to bump, your post was only 7 posts down, and only one bump is permitted every 24 hours.
The issue is clear from your screenshots. You don't have root. On the Magisk screen, at the top under the Magisk section, if "Installed" shows "N/A", you do not have working root. Magisk is unable to load modules without root.

V0latyle said:
No need to bump, your post was only 7 posts down, and only one bump is permitted every 24 hours.
The issue is clear from your screenshots. You don't have root. On the Magisk screen, at the top under the Magisk section, if "Installed" shows "N/A", you do not have working root. Magisk is unable to load modules without root.
Click to expand...
Click to collapse
Sorry, didn't know that.
But I don't quite understand. Why should I have no root if apps like Lucky Patcher, Vanced Manager ask for root and I can verify these requests with the manager?

JulianKlein said:
Sorry, didn't know that.
But I don't quite understand. Why should I have no root if apps like Lucky Patcher, Vanced Manager ask for root and I can verify these requests with the manager?
Click to expand...
Click to collapse
I'm not sure. I think you can still manage root permissions if you don't have root but I'm not 100% on that.
I suggest re-rooting with the prescribed method for your device. On the Pixels, we just re-patch and flash the boot image.

i hace the same problem in sm a70, the apps request root acces and i press yes and work but if the same app need request more times for example unloking network , the request are send again and again and again

I just took the leap into Android 12 and we t through the process of patching the boot img and flashing it. I have the same issue as the op. I have patched, repatched, and flashed and reflashed at least 4 or 5 times now. No change.
Edit to note that I do in fact have root, regardless of what Magisk says (installed - N/A). Apps like AdAway have root access and are working properly.

I had the same problem on my (very) old J7 (2015).
Am on android 7, and was trying to update Magisk from v24.3 to v25.1
I had to completely remove Magisk, and restarted from scratch.
Flashed the v25.1 apk in TWRP.

Same problem with Magisk 52.2 on my LineageOS 19.1 (Android 12L) installed on GT-N8000 (Samsung Note 10.1). I already tried re-root, re-flash, re-install apk and nothing!

constrito said:
Same problem with Magisk 52.2 on my LineageOS 19.1 (Android 12L) installed on GT-N8000 (Samsung Note 10.1). I already tried re-root, re-flash, re-install apk and nothing!
Click to expand...
Click to collapse
Do you originally have magisk hidden as another app then install mm anew?

Nergal di Cuthah said:
Do you originally have magisk hidden as another app then install mm anew?
Click to expand...
Click to collapse
I'm not sure about it, but I tried a few versions of Magisk and none worked. I installed both boot.img and magisk.apk via TWRP. The app downloaded and installed by Android always forces an upgrade.

constrito said:
The app downloaded and installed by Android always forces an upgrade.
Click to expand...
Click to collapse
That's because you haveca newer boot than the magisk manager.
Let it upgrade
Then tap the uninstall button
Restore images
Then complete uninstall
Reboot
Install magisk
Reroot

Nergal di Cuthah said:
That's because you haveca newer boot than the magisk manager.
Let it upgrade
Then tap the uninstall button
Restore images
Then complete uninstall
Reboot
Install magisk
Reroot
Click to expand...
Click to collapse

I don't have an uninstall button. I put a print screen in the previous post.

Did you mean to post something if so you didn't
Not sure what to say about no uninstall but i guarantee that you have a double install. Look through your apps. Did you ever hide magisk with a different name, you've got to remember that at some time you did.

Nergal di Cuthah said:
Did you mean to post something if so you didn't
Click to expand...
Click to collapse
Sorry if there was some confusion, here is: https://forum.xda-developers.com/t/...nd-superuser-grayed-out.4409627/post-88379373.

constrito said:
Sorry if there was some confusion, here is: https://forum.xda-developers.com/t/...nd-superuser-grayed-out.4409627/post-88379373.
Click to expand...
Click to collapse
See my edit

Nergal di Cuthah said:
Did you mean to post something if so you didn't
Not sure what to say about no uninstall but i guarantee that you have a double install. Look through your apps. Did you ever hide magisk with a different name, you've got to remember that at some time you did.
Click to expand...
Click to collapse
I removed the Magisk via TWRP by flashing it with the uninstall.zip file. After installing the Magisk via flash with the Magisk.zip file and rebooting the tablet, I patched my boot.img, went back to TWRP, flashed the boot.img selecting the boot option and rebooted. I went back to the Magisk app and the same problem. I checked via
Code:
adb shell pm list packages | grep magisk
and it returns only
Code:
package:com.topjohnwu.magisk
it suggests I have only 1 app installed (none hidden).

Then I'm out of ideas sorry

Nergal di Cuthah said:
Then I'm out of ideas sorry
Click to expand...
Click to collapse
No problem and thank you.