• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

MagiskHide, and other options, are not available in v23.0

Search This thread
Jan 9, 2013
28
2
Hi,

I installed Magisk.zip v23 into the system through TWRP, and Magisk.apk v23, on my Samsung Galaxy J5 (2016) Nougat 7.1.1
The phone is clearly rooted as some of the tested apps request root, which I gave.
I noticed that something is not quite alright when I open the Magisk app (see attached image)
In the image, the second part is about the App and shows the latest verion 23.0, so that looks OK.
The first part shows the value of the settings A/B, SAR, Ramdisk and the Installed version (=N/A) .
The setting Installed should show the Magisk version 23.0 instead of N/A, and that is clearly wrong.

Also, clicking the settings cogwheel (top/right) should show a long list of settings, including MagiskHide.
However, that is not the case and the options are just a few.

There is clearly something wrong with the installation of Magish.apk, but what?

So, how can that be fixed?
How do I get back all the missing settings, including MagiskHide.

Help would be very much appreciated.

thanks
Screenshot_20210922-224354.jpg
 
Hi,

I installed Magisk.zip v23 into the system through TWRP, and Magisk.apk v23, on my Samsung Galaxy J5 (2016) Nougat 7.1.1
The phone is clearly rooted as some of the tested apps request root, which I gave.
I noticed that something is not quite alright when I open the Magisk app (see attached image)
In the image, the second part is about the App and shows the latest verion 23.0, so that looks OK.
The first part shows the value of the settings A/B, SAR, Ramdisk and the Installed version (=N/A) .
The setting Installed should show the Magisk version 23.0 instead of N/A, and that is clearly wrong.

Also, clicking the settings cogwheel (top/right) should show a long list of settings, including MagiskHide.
However, that is not the case and the options are just a few.

There is clearly something wrong with the installation of Magish.apk, but what?

So, how can that be fixed?
How do I get back all the missing settings, including MagiskHide.

Help would be very much appreciated.

thanks
View attachment 5416439
Search for kdragon safety net fix
 

Didgeridoohan

Senior Moderator / Dev Committee / Dev Relations
Staff member
May 31, 2012
12,137
14,081
Gothenburg
Google Nexus 4
Nexus 6

Didgeridoohan

Senior Moderator / Dev Committee / Dev Relations
Staff member
May 31, 2012
12,137
14,081
Gothenburg
Google Nexus 4
Nexus 6
John Wu, the main contributor to Magisk, now works for Google in their Android Platform Security department. So now his job is to prevent MagiskHide to work, and now it seems he removed it from Magisk.
But that will have no effect on Magisk v23, that the OP is talking about. And, if you take a quick peek on GitHub and the commits over the past month (or follow the conversations in the general Magisk thread) you'll see that MagiskHide still exists, but in the new form of the deny list. Exactly how that'll work will have to wait until John releases the next Canary.
 

Didgeridoohan

Senior Moderator / Dev Committee / Dev Relations
Staff member
May 31, 2012
12,137
14,081
Gothenburg
Google Nexus 4
Nexus 6
Actually it does be the new zip I told him to get ere3nables magisk hide and repo....
The latest release of USNF (currently v2.1.1) adds back a few of the props that MagiskHide currently changes, apart from disabling hardwarebacked key attestation. That is not relevant for the OP, since Magisk v23 still has all of that. The issue here is something else...

And it sounds like you're talking about the unofficial Alpha Magisk releases rather than the SafetyNet Fix, since the latter doesn't include anything that has to do with the soon to be removed modules repo.
 
Jan 9, 2013
28
2
Thanks for the reply.

I unstalled Magisk with uninstall.zip. That worked fine, rootchecker said that root was gone and banking and ID apps were working again.

Then I installed Magisk.zip again through TWRP, and that went well too.

Following reboot there was some sort of little Magisk app in the app folder (see first image). I double clicked it and it installed the full version of Magisk app (13MB), also that went well.

But the problem persists as before with Magisk app, that is: Installed=N/A and the important Settings, like Magiskhide and the Modules part, are missing, which means btw that Universal SafetyNet Fix cannot be installed anyhow.

My device is from 2016 (design 2015), so I have very strong doubts my device supports any hardware-backed attestation.

The Magisk core elements work flawlessly, Root Checker shows root, root apps like VPN hotspot work fine, and the banking and ID apps .... well, they detected root and refuse to continue working. So root is clearly OK.

Somehow the Magisk app in the user/data partition does not/cannot communicate with the Magisk core elements (sitting in the boot ramdisk I presume).

So, is there any app, tool or software to analyze, study or have a closer look at the communication between the app and the core elements?

If this doesn't work out with v23, then I won't have much of a choice but to install lower versions, v22, v21, ... until I come across a version that works, but that is really my last resort as my preference is v23.

Any suggestions ....



Screenshot_20210924-123012.jpg
Screenshot_20210924-125246.jpg
 
Last edited:
The latest release of USNF (currently v2.1.1) adds back a few of the props that MagiskHide currently changes, apart from disabling hardwarebacked key attestation. That is not relevant for the OP, since Magisk v23 still has all of that. The issue here is something else...

And it sounds like you're talking about the unofficial Alpha Magisk releases rather than the SafetyNet Fix, since the latter doesn't include anything that has to do with the soon to be removed modules repo.
 

Attachments

  • Screenshot_20210924-084728.jpg
    Screenshot_20210924-084728.jpg
    592.1 KB · Views: 29

Didgeridoohan

Senior Moderator / Dev Committee / Dev Relations
Staff member
May 31, 2012
12,137
14,081
Gothenburg
Google Nexus 4
Nexus 6
Thanks for the reply.

I unstalled Magisk with uninstall.zip. That worked fine, rootchecker said that root was gone and banking and ID apps were working again.

Then I installed Magisk.zip again through TWRP, and that went well too.

Following reboot there was some sort of little Magisk app in the app folder (see first image). I double clicked it and it installed the full version of Magisk app (13MB), also that went well.

But the problem persists as before with Magisk app, that is: Installed=N/A and the important Settings, like Magiskhide and the Modules part, are missing, which means btw that Universal SafetyNet Fix cannot be installed anyhow.

My device is from 2016 (design 2015), so I have very strong doubts my device supports any hardware-backed attestation.

The Magisk core elements work flawlessly, Root Checker shows root, root apps like VPN hotspot work fine, and the banking and ID apps .... well, they detected root and refuse to continue working. So root is clearly OK.

Somehow the Magisk app in the user/data partition does not/cannot communicate with the Magisk core elements (sitting in the boot ramdisk I presume).

So, is there any app, tool or software to analyze, study or have a closer look at the communication between the app and the core elements?

If this doesn't work out with v23, then I won't have much of a choice but to install lower versions, v22, v21, ... until I come across a version that works, but that is really my last resort as my preference is v23.

Any suggestions ....

Did you check if the app has been installed to external/adoptable storage? That would cause this exact behaviour...

Also, did you previously have Magisk installed with the app repackaged with a random name? If so, that app might still be present and could be the source of your problem. If so, you can uninstall that app and try again (but you might also have to uninstall and reinstall the regular Magisk app as well).
https://www.didgeridoohan.com/magisk/Magisk#hn_There_are_two_Magisk_apps
 
Jan 9, 2013
28
2
Did you check if the app has been installed to external/adoptable storage? That would cause this exact behaviour...

Also, did you previously have Magisk installed with the app repackaged with a random name? If so, that app might still be present and could be the source of your problem. If so, you can uninstall that app and try again (but you might also have to uninstall and reinstall the regular Magisk app as well).
https://www.didgeridoohan.com/magisk/Magisk#hn_There_are_two_Magisk_apps
No, at the last install there was not any external SD card present.

No, never installed Magisk under any another name, neither did I try to hide it or so.

However, ... I did install the app Magisk.apk first a few days ago at first contact with Magisk, and then later I installed Magisk.zip through TWRP while there was an external SD present. So, .... maybe there is some remnant code laying around in the system.

I could uninstall.zip Magisk again and then look for remnants in the system and delete those. If there are any remnant left, those should probably have "magisk" in their name. Do you have any idea where to look for Magisk remnants after uninstallation?

Remember the device is a Samsung Galaxy J5 (2016) and I am not all too sure if Odin is really the most handy tool to look for code remnants. I got ADB and Fastboot installed that I used before for testing my Asus tablets. Also Terminal in TWRP I can use. If I only knew what exactly and where to look for the stuff ....
 
Last edited:
Jan 9, 2013
28
2
Here is an update.

As my device is still rooted by Magisk I checked out the filesystem starting from root with Solid Explorer File Manager (SE).

I found folders and files from Magisk in /root/data/adb/magisk (folder), /root/data/adb/modules (empty folder) and the file /root/data/adb/magisk.db

I uninstalled Magisk by installing uninstall.zip (from Magisk.zip) through TWRP.

And as SE needs root, I installed SuperSU-v2.82-SR5.zip through TWRP, which then worked fine.

With SE I removed magisk.db and any magisk folder at /root/data/adb/

Next thing I did was to remove, uninstall and unroot SuperSU through its own settings.

But after having clean-installed Magisk.zip again from TWRP, having installed the Magisk app using the Magisk preinstaller app in the apps folder and rebooting the device a few times, the problem hasn't gone!

And so the Magisk app pane still shows Installed = N/A, and MagiskHide, Modules and the other options are also still missing from Settings.

Any suggestions for a next move would be welcome.

thanks
 
Jan 9, 2013
28
2
What does this mean? What's a preinstaller?
If one performs a clean installation of Magisk.zip -- so there is no Magisk on the phone anywhere -- through TWRP, not only the core elements are installed, but also in the /data part some little Magisk app is installed that shows up in the apps folder, which I call a (pre)installer. See first image #9. Double clicking that will install the full Magisk app in the user or /data part.
So all looks ok during the installation, and rooting definitely works, but that annoying problem just persists.
I would be glad to hear any suggestions...
 

Didgeridoohan

Senior Moderator / Dev Committee / Dev Relations
Staff member
May 31, 2012
12,137
14,081
Gothenburg
Google Nexus 4
Nexus 6
Ah... Now I get it. It sounded like you were using some custom unofficial stuff, and that would definitely have been a possible source of issues.

I have no suggestions, but you haven't posted any Magisk log, have you? Might be a good idea, to see if anything shows up in there. First it would be good if you could install the Canary release though, since it has more verbose logging.
 
Jan 9, 2013
28
2
Ah... Now I get it. It sounded like you were using some custom unofficial stuff, and that would definitely have been a possible source of issues.

I have no suggestions, but you haven't posted any Magisk log, have you? Might be a good idea, to see if anything shows up in there. First it would be good if you could install the Canary release though, since it has more verbose logging.
I just had a look for those log files but couldn't find any. Any idea where to look for? In /root/data/adb/ there are no log files.
 
Jan 9, 2013
28
2
The Magisk log is in /cache.
So this is what I have in the log.

01-05 19:43:01.276 262 262 I : Magisk 23.0(23000) daemon started
01-05 19:43:01.281 262 262 I : * Device API level: 25
01-05 19:43:01.296 262 264 I : ** post-fs-data mode running
01-05 19:43:01.297 262 264 I : * Mounting mirrors
01-05 19:43:01.298 262 264 I : mount: /sbin/.magisk/mirror/system
01-05 19:43:01.298 262 264 I : mount: /sbin/.magisk/mirror/data
01-05 19:43:01.299 262 264 I : link: /sbin/.magisk/mirror/cache
01-05 19:43:01.299 262 264 I : link: /sbin/.magisk/mirror/persist
01-05 19:43:01.299 262 264 I : link: /sbin/.magisk/mirror/vendor
01-05 19:43:01.299 262 264 I : * Initializing Magisk environment
01-05 19:43:02.901 262 264 I : * Running post-fs-data.d scripts
01-05 19:43:02.906 262 264 I : * Running module post-fs-data scripts
01-05 19:43:02.906 262 264 I : * Loading modules
01-05 19:43:07.207 262 538 I : ** late_start service mode running
01-05 20:43:07.209 262 538 I : * Running service.d scripts
01-05 20:43:07.227 262 538 I : * Running module service scripts
09-25 19:09:50.969 262 2470 I : ** boot_complete triggered
09-25 19:31:29.395 262 12576 W : su: request rejected (10166)
09-25 19:31:41.551 262 12618 W : su: request rejected (10166)
09-25 19:31:53.716 262 12667 W : su: request rejected (10166)
09-25 19:32:05.877 262 12707 W : su: request rejected (10166)
 
  • Like
Reactions: galaxys

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    I just had a look for those log files but couldn't find any. Any idea where to look for? In /root/data/adb/ there are no log files.
    The Magisk log is in /cache.
    1
    The Magisk log is in /cache.
    So this is what I have in the log.

    01-05 19:43:01.276 262 262 I : Magisk 23.0(23000) daemon started
    01-05 19:43:01.281 262 262 I : * Device API level: 25
    01-05 19:43:01.296 262 264 I : ** post-fs-data mode running
    01-05 19:43:01.297 262 264 I : * Mounting mirrors
    01-05 19:43:01.298 262 264 I : mount: /sbin/.magisk/mirror/system
    01-05 19:43:01.298 262 264 I : mount: /sbin/.magisk/mirror/data
    01-05 19:43:01.299 262 264 I : link: /sbin/.magisk/mirror/cache
    01-05 19:43:01.299 262 264 I : link: /sbin/.magisk/mirror/persist
    01-05 19:43:01.299 262 264 I : link: /sbin/.magisk/mirror/vendor
    01-05 19:43:01.299 262 264 I : * Initializing Magisk environment
    01-05 19:43:02.901 262 264 I : * Running post-fs-data.d scripts
    01-05 19:43:02.906 262 264 I : * Running module post-fs-data scripts
    01-05 19:43:02.906 262 264 I : * Loading modules
    01-05 19:43:07.207 262 538 I : ** late_start service mode running
    01-05 20:43:07.209 262 538 I : * Running service.d scripts
    01-05 20:43:07.227 262 538 I : * Running module service scripts
    09-25 19:09:50.969 262 2470 I : ** boot_complete triggered
    09-25 19:31:29.395 262 12576 W : su: request rejected (10166)
    09-25 19:31:41.551 262 12618 W : su: request rejected (10166)
    09-25 19:31:53.716 262 12667 W : su: request rejected (10166)
    09-25 19:32:05.877 262 12707 W : su: request rejected (10166)