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

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
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

DiracDeBroglie said:
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
Click to expand...
Click to collapse
Search for kdragon safety net fix

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.

@DiracDeBroglie since your Magisk app doesn't recognise that you have Magisk installed, none of the options you're mentioning will be available.
First thing I would check is if the Magisk app is installed to the internal storage. If it isn't, things won't work correctly.
https://www.didgeridoohan.com/magisk/Magisk#hn_Magisk_not_installed

Revolver said:
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.
Click to expand...
Click to collapse
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.

toolhas4degrees said:
Search for kdragon safety net fix
Click to expand...
Click to collapse
OP has a device from 2016. I very much doubt that it uses hardware backed key attestation... Besides, that has nothing to do with the described issue.

Didgeridoohan said:
OP has a device from 2016. I very much doubt that it uses hardware backed key attestation... Besides, that has nothing to do with the described issue.
Click to expand...
Click to collapse
Actually it does be the new zip I told him to get ere3nables magisk hide and repo....

toolhas4degrees said:
Actually it does be the new zip I told him to get ere3nables magisk hide and repo....
Click to expand...
Click to collapse
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.

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

Didgeridoohan said:
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.
Click to expand...
Click to collapse

DiracDeBroglie said:
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 ....
Click to expand...
Click to collapse
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

@toolhas4degrees I'm not sure what you mean by that screenshot, but it just shows exactly the same thing I was talking about in the post you quoted.

Didgeridoohan said:
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
Click to expand...
Click to collapse
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 ....

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

DiracDeBroglie said:
installed the Magisk app using the Magisk preinstaller app in the apps folder
Click to expand...
Click to collapse
What does this mean? What's a preinstaller?

Didgeridoohan said:
What does this mean? What's a preinstaller?
Click to expand...
Click to collapse
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...

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.

Didgeridoohan said:
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.
Click to expand...
Click to collapse
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.

DiracDeBroglie said:
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.
Click to expand...
Click to collapse
The Magisk log is in /cache.

Didgeridoohan said:
The Magisk log is in /cache.
Click to expand...
Click to collapse
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)

Related

Cant find Enable Busybox in Magisk settings and ctsProfile not succesfull

Hello.
After many many reinstall of magisk I still cant find "Enable Busybox" in Magisk settings
I have "magisk core only mod" , "Magisk Hide" and "Systemless Host" BUT "Enable Busybox" is missing/not visible in my settings of Magisk.
I also got error when Safety Net check. Only bacisintegry is successfull. ctsProfile do not pass the test.
But, I can still download and update payed and free apps from Google Play Store.
Anyone what to do for getting "Enable Busybox" to be visible in my Magisk settings?
And, since ctsProfile not pass safetyscheck..can that be because for that missing "Enable Busybox" in settings?
Running lineageOS 14.1 and samsung J5 ( 2016 ) , SM-J510FN
Magisk 14.0
Regards
Rolf
Busybox: There is no toggle like that (hasn't been for some time). There's a Busybox module in the Downloads section of the Manager. Use that.
The failed ctsProfile check doesn't have anything to do with Busybox. Take a look here for more info on passing SafetyNet: https://forum.xda-developers.com/apps/magisk/guide-magisk-troubleshooting-t3641417
You don't need to pass SafetyNet to be able to download and install most apps. There are a few who use the Certified status in the Play store (Netflix) and some that won't function if you don't pass SafetyNet (Android Pay).
Didgeridoohan said:
Busybox: There is no toggle like that (hasn't been for some time). There's a Busybox module in the Downloads section of the Manager. Use that.
The failed ctsProfile check doesn't have anything to do with Busybox. Take a look here for more info on passing SafetyNet: https://forum.xda-developers.com/apps/magisk/guide-magisk-troubleshooting-t3641417
You don't need to pass SafetyNet to be able to download and install most apps. There are a few who use the Certified status in the Play store (Netflix) and some that won't function if you don't pass SafetyNet (Android Pay).
Click to expand...
Click to collapse
Thanks for responding and a celearly anwer Didgeridoohan
I will check that link about safetynet. Thanks
Anyway, I guess there are no point/neccesary installing Busybox module in Magisk when I already have Bysybox Pro installed on my device?
I have noticed that my Netflix will not load so hope I got that safetyNet up running in Magisk.
Regards
Rolf
[email protected] said:
Thanks for responding and a celearly anwer Didgeridoohan
I will check that link about safetynet. Thanks
Anyway, I guess there are no point/neccesary installing Busybox module in Magisk when I already have Bysybox Pro installed on my device?
I have noticed that my Netflix will not load so hope I got that safetyNet up running in Magisk.
Regards
Rolf
Click to expand...
Click to collapse
SafetyNet Fixed by doing this:
https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431
BUT, still Netflix Error/not compatibel vs my device when download from Google Play. Got a message in that error message downloading Netflik from Netflix's site. Doing that..and Netflix up running
Thanks again Didgeridoohan for pointing me in the right direction
Regards
Rolf
I thought with the newest version of magisk, busy box is integrated already? I ran a test and it states I have it and it's active but certain apks tell me it's not present in device when installing. Should I setup module in magisk also? Don't want to double stack anything.
SlimPickens89 said:
I thought with the newest version of magisk, busy box is integrated already? I ran a test and it states I have it and it's active but certain apks tell me it's not present in device when installing. Should I setup module in magisk also? Don't want to double stack anything.
Click to expand...
Click to collapse
There is a busybox integrated into Magisk, for use by Magisk...
If you wan't busybox for the rest of your system, install the busybox module from the Magisk repo.
Didgeridoohan;73790549There's a Busybox module in the Downloads section of the Manager. Use that.
The failed ctsProfile check doesn't have anything to do with Busybox. Take a look here for more info on passing SafetyNet: [url said:
https://forum.xda-developers.com/apps/magisk/guide-magisk-troubleshooting-t3641417[/url]
You don't need to pass SafetyNet to be able to download and install most apps. There are a few who use the Certified status in the Play store (Netflix) and some that won't function if you don't pass SafetyNet (Android Pay).
Click to expand...
Click to collapse
Actually, in my case, the ctsProfile check does correlate with the busybox module. I am trying a new ROM on my galaxy s7 which doesn't contain a busybox, thus Viper4Android does not want to install its driver (and Busybox checker says "no"). ctsProfile did pass. After I downloaded the BusyBox module in Magisk Manager, cts doesn't pass, but basic integrity still does.
Peter.1997 said:
Actually, in my case, the ctsProfile check does correlate with the busybox module. I am trying a new ROM on my galaxy s7 which doesn't contain a busybox, thus Viper4Android does not want to install its driver (and Busybox checker says "no"). ctsProfile did pass. After I downloaded the BusyBox module in Magisk Manager, cts doesn't pass, but basic integrity still does.
Click to expand...
Click to collapse
If you only need busybox for Viper4Android, try the awesome ViPER4Android FX module (available in the Magisk repo). It doesn't need busybox...
Yup, only vor Viper. I already installed this module (and also the seperate one for Magisk 14.0+), but the Viper app always wants to install the driver on its own again..
Peter.1997 said:
Yup, only vor Viper. I already installed this module (and also the seperate one for Magisk 14.0+), but the Viper app always wants to install the driver on its own again..
Click to expand...
Click to collapse
Judging from your two posts, I'd say something's wrong with your Magisk installation... Magisk log and magisk_debug.log (from /data) might show something interesting.
Jumping onto that thread as it seems to fit quite well.
If a Moderator feels the need for a new topic pls let me know.
Facts:
Android 6 with Magisk 12 and SuperSu 2.79/2.82 and Xposed 87 running fine for quite a time.
Only Magisk manager was updated inbetween a few times
Now with a few free days after christmas and all the new releases out, i went for an update session.
- cleaned supersu with 0smosis unSu
- TWRP flashed clean stock boot.img
- TWRP flashed Magisk 15.1. All good and seemed to work
Then i wanted to update to xposed v89.
The installer failed with "updater process ended with error 1"
Dug into the TWRP-Logs and found the following:
Code:
/tmp/updater: line 91: /data/adb/magisk/busybox: not found
! Unable to extract zip file!
Now it was time to inspect the Magisk-Log:
Code:
12-29 23:56:59.699 269 269 I Magisk : * Setting up internal busybox
12-29 23:56:59.700 273 273 E Magisk : execvpe failed with 2: No such file or directory
Interesting.
As i knew about the changes from 12->15 regarding internal busybox, i cleaned the Magisk Manager Cache as recommended somewhere
and wanted to go for the official module "Busybox for Android NDK 1.27.2".
After installing it showed up as "not available - please reboot"
I went for the logs again and found the following:
Code:
Installing Busybox_for_Android_NDK-1.27.2.zip
Busybox Installer Script by osm0sis @ xda-developers
Mounting...
Extracting files...
update-binary[109]: unzip: not found
Also a quick check of /data/magisk showed no signs of busybox.
Any hints where to dig deeper to get busybox (and unzipping in TWRP back ??
Time, a few Skills and Tools available.
Didnt attach the logs, cause those above are imho the only relevant facts.
If somebody needs sth specific to rule sth out, i will of course happily deliver them.
Thank everybody and keep up the good work !!
Sebastl said:
Jumping onto that thread as it seems to fit quite well.
If a Moderator feels the need for a new topic pls let me know.
Facts:
Android 6 with Magisk 12 and SuperSu 2.79/2.82 and Xposed 87 running fine for quite a time.
Only Magisk manager was updated inbetween a few times
Now with a few free days after christmas and all the new releases out, i went for an update session.
- cleaned supersu with 0smosis unSu
- TWRP flashed clean stock boot.img
- TWRP flashed Magisk 15.1. All good and seemed to work
Then i wanted to update to xposed v89.
The installer failed with "updater process ended with error 1"
Dug into the TWRP-Logs and found the following:
Code:
/tmp/updater: line 91: /data/adb/magisk/busybox: not found
! Unable to extract zip file!
Now it was time to inspect the Magisk-Log:
Code:
12-29 23:56:59.699 269 269 I Magisk : * Setting up internal busybox
12-29 23:56:59.700 273 273 E Magisk : execvpe failed with 2: No such file or directory
Interesting.
As i knew about the changes from 12->15 regarding internal busybox, i cleaned the Magisk Manager Cache as recommended somewhere
and wanted to go for the official module "Busybox for Android NDK 1.27.2".
After installing it showed up as "not available - please reboot"
I went for the logs again and found the following:
Code:
Installing Busybox_for_Android_NDK-1.27.2.zip
Busybox Installer Script by osm0sis @ xda-developers
Mounting...
Extracting files...
update-binary[109]: unzip: not found
Also a quick check of /data/magisk showed no signs of busybox.
Any hints where to dig deeper to get busybox (and unzipping in TWRP back ??
Time, a few Skills and Tools available.
Didnt attach the logs, cause those above are imho the only relevant facts.
If somebody needs sth specific to rule sth out, i will of course happily deliver them.
Thank everybody and keep up the good work !!
Click to expand...
Click to collapse
Sounds like your TWRP isn't up to the job... It's probably too old (info which would have been in the log ) or otherwise missing some features...
Updating TWRP or letting the Manager patch a boot image that you then flash manually are two possible solutions.
Thank you very much for the quick reply Didgeridoohan.
That is of course water on the mills of the "always include logs" - people. Apparently for a reason
TWRP Version is/was 3.02.
After you suggested patching the image from Magisk Manager, i tried that and got a quick and dirty "Failed".
But i realized that now the option "Direct Install (recommended)" was available.
It wasnt when i did the initial setup.
As i had nothing to loose, i tried that to reinstall and after the next reboot -
Bingo! Now the busybox binary is/was available and therefore the Busybox Module and consequently also Xposed respective everything which depends on unzipping/busybox works.
Strange - but somehow problem solved.
I didnt see anything in the TWRP changelogs from 3.02 up to 3.2.1 - but hey...
Hope that helps someone.
Greetings and a nice 2018 !

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

ctsprofile: false and basicIntegrity: false magisk hide error

I am on a honor 8 running Android 7.0 and magisk v16. I Uninstalled xposed through custom recovery, didn't do anything. anyone have any ideas? when I run the SN check both ctsprofile: and basicIntegrity: show as false.
https://forum.xda-developers.com/apps/magisk/guide-magisk-troubleshooting-t3641417
Didgeridoohan said:
https://forum.xda-developers.com/apps/magisk/guide-magisk-troubleshooting-t3641417
Click to expand...
Click to collapse
I have read through this, and I'm not sure if I'm missing something but I do not see anything that applies to the problem I am experiencing.
T0blerone said:
I have read through this, and I'm not sure if I'm missing something but I do not see anything that applies to the problem I am experiencing.
Click to expand...
Click to collapse
Really? There's quite a lot of tips on how to get MagiskHide to work and SafetyNet to pass in the wiki linked from that thread. What have you tried so far? And where are your logs?
Didgeridoohan said:
Really? There's quite a lot of tips on how to get MagiskHide to work and SafetyNet to pass in the wiki linked from that thread. What have you tried so far? And where are your logs?
Click to expand...
Click to collapse
I'm brand new to rooting. I rooted my first device yesterday so to be quite honest I'm kind of lost at this point. I haven't tried anything from the forum because I didn't see anything that mentioned how to get the basicIntegrity working. I saw methods that helped the other one if you have basic integrity working but I don't know how to fix that, or anything really.
T0blerone said:
I have read through this, and I'm not sure if I'm missing something but I do not see anything that applies to the problem I am experiencing.
Click to expand...
Click to collapse
Kindly Do The Following
- Install RootBeer Sample From PlayStore --> Send Its Screenshots Before Adding This App To Magisk Hide & After Adding This App To Magisk Hide
- Install SafetyNet Helper Sample Or SafetyNet Test From PlayStore & Send Its Screenshot
- Send The Screenshot Of PlayStore Device Certification Status (Google PlayStore --> Settings --> Device Certification)
Dreamer(3MF) said:
Kindly Do The Following
- Install RootBeer Sample From PlayStore --> Send Its Screenshots Before Adding This App To Magisk Hide & After Adding This App To Magisk Hide
- Install SafetyNet Helper Sample Or SafetyNet Test From PlayStore & Send Its Screenshot
- Send The Screenshot Of PlayStore Device Certification Status (Google PlayStore --> Settings --> Device Certification)
Click to expand...
Click to collapse
I actually can't. as im so new I have less than 10 posts I'm not allowed to upload images. the root beer sample showed checks except four red x's on su binary, su exists, root native, and on root cloaking apps. SafetyNet failed with success on the request but said "fail (response payload validation failed)" and my device Certification is uncertified. hope that helps.
T0blerone said:
I actually can't. as im so new I have less than 10 posts I'm not allowed to upload images. the root beer sample showed checks except four red x's on su binary, su exists, root native, and on root cloaking apps. SafetyNet failed with success on the request but said "fail (response payload validation failed)" and my device Certification is uncertified. hope that helps.
Click to expand...
Click to collapse
For Passing The SafetyNet, Check This Post https://forum.xda-developers.com/ap...playstore-services-data-t3789498/post76682978.
Magisk-v16.4 Is Not Suitable For Most Of Us To Use Due To Many Issues So That Flash Its Replacement Magisk-v16.3.1(ThePatchedBinary) From This Link https://androidfilehost.com/?fid=962339331458996616 Or Magisk-v16.3 (Instead Of Magisk-v16.4).
T0blerone said:
I actually can't. as im so new I have less than 10 posts I'm not allowed to upload images. the root beer sample showed checks except four red x's on su binary, su exists, root native, and on root cloaking apps. SafetyNet failed with success on the request but said "fail (response payload validation failed)" and my device Certification is uncertified. hope that helps.
Click to expand...
Click to collapse
If you add the Rootbeer app to the MagiskHide list in the Manager and check again, we'll know of MagiskHide works on your device or not. With the app on the Hide list, all checkmarks should be green.
If it doesn't seem to work, the first thing to try is to toggle MagiskHide off and on in the Manager settings.
Didgeridoohan said:
If you add the Rootbeer app to the MagiskHide list in the Manager and check again, we'll know of MagiskHide works on your device or not. With the app on the Hide list, all checkmarks should be green.
If it doesn't seem to work, the first thing to try is to toggle MagiskHide off and on in the Manager settings.
Click to expand...
Click to collapse
I added it and nothing changed. I then toggled it off and on and ran the test a third time and got the same results.
T0blerone said:
I added it and nothing changed. I then toggled it off and on and ran the test a third time and got the same results.
Click to expand...
Click to collapse
Which means MagiskHide isn't working properly on your device. Or you have remnants of previous root stuff (if you were playing around with something else before flashing Magisk), or possibly stuff left over from Xposed. Have you uninstalled the Xposed Installer app?
If you can save the Magisk log to Pastebin and then post the id for that paste, we can at least take a look at that. If you then can install the beta release of Magisk (or an unofficial snapshot, since they're more up-to-date) and provide the magisk_debug.log, that would be even better.
Didgeridoohan said:
Which means MagiskHide isn't working properly on your device. Or you have remnants of previous root stuff (if you were playing around with something else before flashing Magisk), or possibly stuff left over from Xposed. Have you uninstalled the Xposed Installer app?
If you can save the Magisk log to Pastebin and then post the id for that paste, we can at least take a look at that. If you then can install the beta release of Magisk (or an unofficial snapshot, since they're more up-to-date) and provide the magisk_debug.log, that would be even better.
Click to expand...
Click to collapse
I removed the xposed installer app and the root cloaking checkmark went green.
Didgeridoohan said:
Which means MagiskHide isn't working properly on your device. Or you have remnants of previous root stuff (if you were playing around with something else before flashing Magisk), or possibly stuff left over from Xposed. Have you uninstalled the Xposed Installer app?
If you can save the Magisk log to Pastebin and then post the id for that paste, we can at least take a look at that. If you then can install the beta release of Magisk (or an unofficial snapshot, since they're more up-to-date) and provide the magisk_debug.log, that would be even better.
Click to expand...
Click to collapse
although that's green safetynet is still failed both in the magisk app and the separate safetynet test
T0blerone said:
although that's green safetynet is still failed both in the magisk app and the separate safetynet test
Click to expand...
Click to collapse
same as mine,but i use custom rom. device redmi note 2
RR, Viper, couldnt work to pass basic integrity and cts, i have tried flash safetynet fix but stillnothing
I have the same issue. But sometimes the checks fail and sometimes they dont
Same issue here
I am having the same problem. I tried everything, every possible option on the internet I could find. Managed to get "basicIntegraty: true" probably from uninstalling Xposed but I still am unable to fix "ctsProfile: false". Here are the screens from RootBeer Sample and SafetyNet:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Click to expand...
Click to collapse
zbysogi said:
I am having the same problem. I tried everything, every possible option on the internet I could find. Managed to get "basicIntegraty: true" probably from uninstalling Xposed but I still am unable to fix "ctsProfile: false". Here are the screens from RootBeer Sample and SafetyNet:
Click to expand...
Click to collapse
Busybox shouldn't have an impact on SafetyNet, but if you want to make sure that other apps don't defect it, uninstall the currently installed Busybox and install from the Magisk Manager instead.
For passing the CTS profile check you can use my MagiskHide Props Config module. Details here:
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228
Didgeridoohan said:
Busybox shouldn't have an impact on SafetyNet, but if you want to make sure that other apps don't defect it, uninstall the currently installed Busybox and install from the Magisk Manager instead.
For passing the CTS profile check you can use my MagiskHide Props Config module. Details here:
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228
Click to expand...
Click to collapse
Yeah. Im in the middle of sorting out the problem with modules not working. They show up in the modules tab in Magisk but dont work :/ Thus Magisk is not working properly. I can not even change the fingerprint using the Terminal Emulator :/ cause it doesnt even recognise Magisk being installed :/
EDIT:
half a day but its sorted. Thx
T0blerone said:
I am on a honor 8 running Android 7.0 and magisk v16. I Uninstalled xposed through custom recovery, didn't do anything. anyone have any ideas? when I run the SN check both ctsprofile: and basicIntegrity: show as false.
Click to expand...
Click to collapse
You can get both to pass. Here are the steps...
1. From your magisk, install these 2 modules: Riru - Core, and Riru - EdXposed (Sandbox or Yahfa is okay]
2. Reboot your device to activate both modules.
3. Install Xposed Installer APK by DVDandroid. You can get it here: https://dl-xda.xposed.info/modules/de.robv.android.xposed.installer_v33_36570c.apk
4. Reboot to activate the Xposed Installer app
5. Inside Xposed Installer app, go to downloads and install the HiddenCore Module.
6. Reboot and go back to Magisk and test the SafetyNet.
7. Boom! Everything passes now.

Magisk Hide Still Detected Fix

Disclaimer :
1.this tutorial is based on AOSP ROM Android 10,,, some member report that this most likely not working on Android 11,, so if you on Android 11 and above, don't expect too much, but still, good luck.
2.since official magisk drop the "MagiskHide",you need to find older version of magisk canary somewhere else.
its start from some banking app still detect root after i update it, and even i hide Magisk from that banking app and hide magisk with custom pkg id ( setting > Hide the Magisk App ) the banking app still detected.
so, here is the fix
1. install magisk canary
( if you alreay hide magisk with random package ID, restore it first )
download magisk canary from here : https://github.com/topjohnwu/Magisk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. after reinstall magisk with canary app, go to Magisk setting, and change Update Channel to Canary. and then back to Magisk Home, and install the magisk again ( not the app )
for the Option, just klick Next, and for the Method, choose Direct Install. and Reboot.
3. download Riru module from here : https://github.com/RikkaApps/Riru/releases
4. after download Riru module, Open Magisk, go to Module tab, choose Install From Storage and locate the Riru module, flash and Reboot.
5. Now, download Riru Unshare, from here : https://github.com/vvb2060/riru-unshare
6. after download Riru_Unshare.zip module, Open Magisk, go to Module tab, choose Install From Storage and locate the Riru_Unshare.zip, flash and Reboot.
Done ! open magisk and rehide the app that previously still detect root and its should be able to open as normal without Root warning.
i hope this will help you, if so, please press the thanks button, cheers.
Nope, are you 11 or 10?
Also, was told unshare already implemented in magisk
Lu5ck said:
Nope, are you 11 or 10?
Also, was told unshare already implemented in magisk
Click to expand...
Click to collapse
Iam on 10, well idk if it already implement on magisk, but even i update to latest version of magisk, the root still detected, and at this moment, using unshare is fix my problem,,, because android user is vary between OS and devices, iam sure some people will get the same problem.
not working with "STC Pay"
the only solution for now is to delete magisk app, it will appear after a reboot.
bayu elf sabayonz said:
its start from some banking app still detect root after i update it, and even i hide Magisk from that banking app and hide magisk with custom pkg id ( setting > Hide the Magisk App ) the banking app still detected.
so, here is the fix
1. install magisk canary
( if you alreay hide magisk with random package ID, restore it first )
download magisk canary from here : https://github.com/topjohnwu/MagiskView attachment 5323957
2. after reinstall magisk with canary app, go to Magisk setting, and change Update Channel to Canary. and then back to Magisk Home, and install the magisk again ( not the app )
View attachment 5323961
for the Option, just klick Next, and for the Method, choose Direct Install. and Reboot.
3. download Riru module from here : https://github.com/RikkaApps/Riru/releases
4. after download Riru module, Open Magisk, go to Module tab, choose Install From Storage and locate the Riru module, flash and Reboot.
5. Now, download Riru Unshare, from here : https://github.com/vvb2060/riru-unshare
6. after download Riru_Unshare.zip module, Open Magisk, go to Module tab, choose Install From Storage and locate the Riru_Unshare.zip, flash and Reboot.
Done ! open magisk and rehide the app that previously still detect root and its should be able to open as normal without Root warning.
i hope this will help you, if so, please press the thanks button, cheers.
Click to expand...
Click to collapse
Cheers for this, id avoided using Riru until now, but my banks latest app update wreaked havoc on my Pixel 2XL and i suddenly couldnt add my card to google Pay. The banks app detecting root and then sending false data to Google Pay when i tried to verify killed my google Pay account. Then it killed my bank account, to the point i had to order a new card.
Then i still couldnt add the new one...until i caved in and tried Riru and Riru Unshare
Once i did all the steps, and rehid Magisk, i was fine
at android 11 bank app detect root .
Bofahad said:
at android 11 bank app detect root .
Click to expand...
Click to collapse
Some ROMS can still expose root via props etc
Case in point, after my win above, i flashed a different (new) ROM and while Google Play worked fine, my bank app and Samsung pay detected root, using the same setup as above, and the exact same Migrate backup
I reverted back to the ROM i used above and had no issues again
Sometimes you just cant win
Bofahad said:
at android 11 bank app detect root .
Click to expand...
Click to collapse
Might be because the app is scanning for known root apps
You could try xprivacylua via lsposed to block app requests for that app.
You can also use "shelter" to isolate what the apps can see
You can also use "app manager" to disable the isolated service
Last but not least, many apps are not updated to work with 11 flawlessly thus some solution might fail at times
Personally, I had to run shelter but sometimes it will fail, due to where i run the app from
My run of my banking app working with the above fix ended after 3 days
Still trying to figure out why
For sure is a problem with hidding magisk on android 11 to use some bank apps. I got this here too. C6 bank's app works with magisk hide and changed magisk manager name in android 10 but with no working with this same process on android 11.
Will back to android 10 and wait for another fix or way to get it.
bayu elf sabayonz said:
its start from some banking app still detect root after i update it, and even i hide Magisk from that banking app and hide magisk with custom pkg id ( setting > Hide the Magisk App ) the banking app still detected.
so, here is the fix
1. install magisk canary
( if you alreay hide magisk with random package ID, restore it first )
download magisk canary from here : https://github.com/topjohnwu/MagiskView attachment 5323957
2. after reinstall magisk with canary app, go to Magisk setting, and change Update Channel to Canary. and then back to Magisk Home, and install the magisk again ( not the app )
View attachment 5323961
for the Option, just klick Next, and for the Method, choose Direct Install. and Reboot.
3. download Riru module from here : https://github.com/RikkaApps/Riru/releases
4. after download Riru module, Open Magisk, go to Module tab, choose Install From Storage and locate the Riru module, flash and Reboot.
5. Now, download Riru Unshare, from here : https://github.com/vvb2060/riru-unshare
6. after download Riru_Unshare.zip module, Open Magisk, go to Module tab, choose Install From Storage and locate the Riru_Unshare.zip, flash and Reboot.
Done ! open magisk and rehide the app that previously still detect root and its should be able to open as normal without Root warning.
i hope this will help you, if so, please press the thanks button, cheers.
Click to expand...
Click to collapse
THANK YOU SO MUCH!!!! I was looking for a way to get Epic Seven (game) to work and this finally fixed it.
I did add a folder named isolated to the folder they noted
GitHub - canyie/Riru-MomoHider: A Riru module tries to make Magisk more hidden.
A Riru module tries to make Magisk more hidden. Contribute to canyie/Riru-MomoHider development by creating an account on GitHub.
github.com
Note: Since 0.0.3, all features are disabled by default, you need to create a file named /data/adb/(lite_)modules/riru_momohider/config/<config name> to enable it
Config nameDescriptionisolatedApply Magisk Hide for isolated process and app zygotes. This feature is deprecated because it will unmount Magisk modified files for every isolated processes, and the unmounting time cannot be well controlled, which may cause some modules to not work. For almost apps, Magisk Alpha or the latest Magisk canary + Riru-Unshare is enough.setnsFaster new way to hide Magisk in isolated processes. Requires config "isolated" is enabled.app_zygote_magicMake a app named "Momo" cannot detect Magisk hide is running.initrcHide the modified traces of init.rc
Cryptonite26 said:
THANK YOU SO MUCH!!!! I was looking for a way to get Epic Seven (game) to work and this finally fixed it.
I did add a folder named isolated to the folder they noted
GitHub - canyie/Riru-MomoHider: A Riru module tries to make Magisk more hidden.
A Riru module tries to make Magisk more hidden. Contribute to canyie/Riru-MomoHider development by creating an account on GitHub.
github.com
Note: Since 0.0.3, all features are disabled by default, you need to create a file named /data/adb/(lite_)modules/riru_momohider/config/<config name> to enable it
Config nameDescriptionisolatedApply Magisk Hide for isolated process and app zygotes. This feature is deprecated because it will unmount Magisk modified files for every isolated processes, and the unmounting time cannot be well controlled, which may cause some modules to not work. For almost apps, Magisk Alpha or the latest Magisk canary + Riru-Unshare is enough.setnsFaster new way to hide Magisk in isolated processes. Requires config "isolated" is enabled.app_zygote_magicMake a app named "Momo" cannot detect Magisk hide is running.initrcHide the modified traces of init.rc
Click to expand...
Click to collapse
Hi can you be more specific in detailing exactly what you did pls. I'm trying to get this same game Epic Seven to work on my rooted phone.
just enable zygisk and its done .
I know its old topic, but did you use busybox of any kind? Try uninstall it. Mine was this sucker, even using shimoko didnt give good result. U
I uninstall that, BOOM! settled....

Downgrading from 23010 to any lower version–stock boot.img doesn't seem to get patched

Phone: Android 11 stock running on Pixel 4XL
The canary came out of the coal mine yesterday and I gladly accepted 23010 without realizing the implications of doing so. The update broke, and Magisk ceased working. I reinstalled the apk and got a patched boot image out of it and all was well, until I saw that MagiskHide is gone–I am not yet ready for that.
So, I tried to downgrade. I have the stock boot.img (and prior patched images I'd saved for my current version of Android). I tried to flash the patched image for 23000 and 22100 in fastboot, and even attempted flashing the old 21.4 zip file in recovery. Still, when I boot my device, it always ends up as lacking a Magisk installation unless I use 23010.
Any ideas?
You have to uninstall from the magisk app, reboot, install old magisk 23 then fastboot flash the patched boot img from that version of magisk.
That did the trick. Thanks mate! Glad to be back in the green :')
The fix for me was to remove "magisk.db" from /data/adb/. When I downgraded, magisk crashed (as seen in log) and wasn't recognized in app. Only after removal of .db, the older v23000 was correctly started.
davidmoore0 said:
Phone: Android 11 stock running on Pixel 4XL
The canary came out of the coal mine yesterday and I gladly accepted 23010 without realizing the implications of doing so. The update broke, and Magisk ceased working. I reinstalled the apk and got a patched boot image out of it and all was well, until I saw that MagiskHide is gone–I am not yet ready for that.
So, I tried to downgrade. I have the stock boot.img (and prior patched images I'd saved for my current version of Android). I tried to flash the patched image for 23000 and 22100 in fastboot, and even attempted flashing the old 21.4 zip file in recovery. Still, when I boot my device, it always ends up as lacking a Magisk installation unless I use 23010.
Any ideas?
Click to expand...
Click to collapse
I had exactly same issue, so I am going to try uninstall magisk from app now.
toolhas4degrees said:
You have to uninstall from the magisk app, reboot, install old magisk 23 then fastboot flash the patched boot img from that version of magisk.
Click to expand...
Click to collapse
This helped me. I am now back on Magisk 23000 with MagiskHide feature.
Newest alfa builds still have MagiskHide if you decide not to use Zygisk. So this change is going to canary and stable versions. Module repository is definitely gone.
At this point I'm using https://github.com/Fox2Code/FoxMagiskModuleManager app, that checks module updates from
https://github.com/Magisk-Modules-Alt-Repo
https://github.com/Magisk-Modules-Repo
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi, I rooted my Pixel 6 (non pro) but also have the issue with "magisk hide" which disappeared.
I understood I had to :
1) through magisk app, click on "uninstall magisk", then reboot system
2) reboot fastboot and flash unpatched boot.img
3) install magisk v23 ? and patch boot.img
=> This step fails : "Unable to unpack boot image, installation failed"
=> Am I using the right magisk version ??? If not, where can I retrieve the correct one ?
4) reboot fastboot and flash patched boot.img
Thanks or your help
wiz.wiz said:
Hi, I rooted my Pixel 6 (non pro) but also have the issue with "magisk hide" which disappeared.
I understood I had to :
1) through magisk app, click on "uninstall magisk", then reboot system
2) reboot fastboot and flash unpatched boot.img
3) install magisk v23 (here : https://magiskapp.com/apk/) ? and patch boot.img
=> This step fails : "Unable to unpack boot image, installation failed"
=> Am I using the right magisk version ??? If not, where can I retrieve the correct one ?
4) reboot fastboot and flash patched boot.img
Thanks or your help
Click to expand...
Click to collapse
That's not an "issue", it's by design. And v23 won't work on the Pixel 6, you need build 23010 or newer.
A couple of options are available. Stay on the current official Canary and following releases, or use one of the custom unofficial Magisk releases that are available with MagiskHide added back in (you can find them if you look through the general support thread).
As far as I've seen, Deny list is just about as useful for hiding root as MagiskHide (but there are of course differences).
Never use any other source for downloading Magisk other than John's Github (or whatever unofficial build you want to use). That link you're providing/using is not an official source and if you're really unlucky you'll be downloading and installing malicious files...
Didgeridoohan said:
That's not an "issue", it's by design. And v23 won't work on the Pixel 6, you need build 23010 or newer.
A couple of options are available. Stay on the current official Canary and following releases, or use one of the custom unofficial Magisk releases that are available with MagiskHide added back in (you can find them if you look through the general support thread).
As far as I've seen, Deny list is just about as useful for hiding root as MagiskHide (but there are of course differences).
Never use any other source for downloading Magisk other than John's Github (or whatever unofficial build you want to use). That link you're providing/using is not an official source and if you're really unlucky you'll be downloading and installing malicious files...
Click to expand...
Click to collapse
Hi, thanks a lot for the explanations !
not having Magisk Hide is actually an issue for me. I understood that it's been removed "on purpose" by the author (since he's been hired by Google, strange coincidence no ?), but not having it prevents a few apps from working (Revolut banking app), and the deny list seem not to operate with that app at least.
I will remove the link of my post not to lead other people to that same unofficial source.
I will also look at the unofficial releases, is there one you would recommend ?
wiz.wiz said:
Hi, thanks a lot for the explanations !
not having Magisk Hide is actually an issue for me. I understood that it's been removed "on purpose" by the author (since he's been hired by Google, strange coincidence no ?), but not having it prevents a few apps from working (Revolut banking app), and the deny list seem not to operate with that app at least.
I will remove the link of my post not to lead other people to that same unofficial source.
I will also look at the unofficial releases, is there one you would recommend ?
Click to expand...
Click to collapse
Of course it's not a coincidence that the nature of MagiskHide changed when John joined the Google security team. Changing MagiskHide to the Deny list was already well underway before that though...
I tested the Revolut app on my device right now, and as soon as I added it to the Deny list it stopped complaining about root and started without issue.
I don't use any unofficial builds, so I have nothing to recommend...
Didgeridoohan said:
Of course it's not a coincidence that the nature of MagiskHide changed when John joined the Google security team. Changing MagiskHide to the Deny list was already well underway before that though...
I tested the Revolut app on my device right now, and as soon as I added it to the Deny list it stopped complaining about root and started without issue.
I don't use any unofficial builds, so I have nothing to recommend...
Click to expand...
Click to collapse
maybe I missed something yesterday when I tested it.
I tried again, but my Revolut version (installed from local apk) is too old : I can't install/update as the phone is "not certified" on play store.
I have to look at how to workaround it. There was "magikhide props config" I think, but not sure it is going to work with this magisk version.
Edit : the app "mywellness" seem to detect root despite magiskhide (on my wife's previous phone), but works fine with the deny list
wiz.wiz said:
maybe I missed something yesterday when I tested it.
I tried again, but my Revolut version (installed from local apk) is too old : I can't install/update as the phone is "not certified" on play store.
I have to look at how to workaround it. There was "magikhide props config" I think, but not sure it is going to work with this magisk version.
Edit : the app "mywellness" seem to detect root despite magiskhide (on my wife's previous phone), but works fine with the deny list
Click to expand...
Click to collapse
If you're on the stock Google firmware you're not going to need MagiskHide Props Config. You will most likely need the Universal SafetyNet Fix though, and more specifically the v2.2.0 release (or newer, but that's the latest release as of writing this). Currently only available to the developer's Patreon supporters, but should become publicly available in a not too distant future. That is likely the only way you're going to pass SafetyNet and the your Play Store certified (unless you use some of the experimental unofficial Magisk releases so that you can use earlier releases of the Universal SafetyNet Fix).
Note: to get the Play Store certified once you pass SafetyNet you likely will have to clear data for the Play Store.
Didgeridoohan said:
If you're on the stock Google firmware you're not going to need MagiskHide Props Config. You will most likely need the Universal SafetyNet Fix though, and more specifically the v2.2.0 release (or newer, but that's the latest release as of writing this). Currently only available to the developer's Patreon supporters, but should become publicly available in a not too distant future. That is likely the only way you're going to pass SafetyNet and the your Play Store certified (unless you use some of the experimental unofficial Magisk releases so that you can use earlier releases of the Universal SafetyNet Fix).
Note: to get the Play Store certified once you pass SafetyNet you likely will have to clear data for the Play Store.
Click to expand...
Click to collapse
Thank you for all this explanation. I will wait for the public availability I think.
Did you use this module to install "Revolut" app, as you tested it ?
I tried to download the apk through a web apk downloader, but it came as a zip file, which I've not been able to install (with pm install, no matter renaming it to .apk or .xapk)
wiz.wiz said:
Thank you for all this explanation. I will wait for the public availability I think.
Did you use this module to install "Revolut" app, as you tested it ?
I tried to download the apk through a web apk downloader, but it came as a zip file, which I've not been able to install (with pm install, no matter renaming it to .apk or .xapk)
Click to expand...
Click to collapse
Try renaming it to an apks extension, rather than apk or xapk. It could be a split app. Open the zip first and see if there are apk files with "split" in the name. I use Total Commander or Split APK Installer for these.
It's also possible that it's failing to install because it's not "correct" for your CPU architecture. Like, you can't install arm64 split APKs on a 32 bit only arm device.
AnonVendetta said:
Try renaming it to an apks extension, rather than apk or xapk. It could be a split app. Open the zip first and see if there are apk files with "split" in the name. I use Total Commander or Split APK Installer for these.
It's also possible that it's failing to install because it's not "correct" for your CPU architecture. Like, you can't install arm64 split APKs on a 32 bit only arm device.
Click to expand...
Click to collapse
no "split" in the name.
I tried with mixplorer and adb shell pm install (and even copying the apks in /data/local/tmp/) :
[email protected]:/media/Donnees/Telephonie/apk$ adb shell pm install com.revolut.revolut_0_apps.evozi.com.apks
Error: Unable to open file: com.revolut.revolut_0_apps.evozi.com.apks
Consider using a file under /data/local/tmp/
Error: Can't open file: com.revolut.revolut_0_apps.evozi.com.apks
Exception occurred while executing 'install':
java.lang.IllegalArgumentException: Error: Can't open file: com.revolut.revolut_0_apps.evozi.com.apks
at com.android.server.pm.PackageManagerShellCommand.setParamsSize(PackageManagerShellCommand.java:572)
at com.android.server.pm.PackageManagerShellCommand.doRunInstall(PackageManagerShellCommand.java:1337)
at com.android.server.pm.PackageManagerShellCommand.runInstall(PackageManagerShellCommand.java:1303)
at com.android.server.pm.PackageManagerShellCommand.onCommand(PackageManagerShellCommand.java:193)
at com.android.modules.utils.BasicShellCommandHandler.exec(BasicShellCommandHandler.java:97)
at android.os.ShellCommand.exec(ShellCommand.java:38)
at com.android.server.pm.PackageManagerService.onShellCommand(PackageManagerService.java:24612)
at android.os.Binder.shellCommand(Binder.java:950)
at android.os.Binder.onTransact(Binder.java:834)
at android.content.pm.IPackageManager$Stub.onTransact(IPackageManager.java:4818)
at com.android.server.pm.PackageManagerService.onTransact(PackageManagerService.java:8506)
at android.os.Binder.execTransactInternal(Binder.java:1184)
at android.os.Binder.execTransact(Binder.java:1143)
[email protected]:/media/Donnees/Telephonie/apk$ unzip -l com.revolut.revolut_0_apps.evozi.com.apks
Archive: com.revolut.revolut_0_apps.evozi.com.apks
Length Date Time Name
--------- ---------- ----- ----
106860349 1980-00-00 00:00 com.revolut.revolut.apk
ApkPure.com
30411 1980-00-00 00:00 icon.png
ApkPure.com
2961817 1980-00-00 00:00 config.en.apk
ApkPure.com
2576899 1980-00-00 00:00 config.de.apk
ApkPure.com
2548227 1980-00-00 00:00 config.es.apk
ApkPure.com
2527747 1980-00-00 00:00 config.it.apk
ApkPure.com
2556419 1980-00-00 00:00 config.pt.apk
ApkPure.com
24570011 1980-00-00 00:00 config.xxxhdpi.apk
ApkPure.com
2691587 1980-00-00 00:00 config.fr.apk
ApkPure.com
2658819 1980-00-00 00:00 config.ja.apk
ApkPure.com
3142147 1980-00-00 00:00 config.ru.apk
ApkPure.com
57116466 1980-00-00 00:00 config.arm64_v8a.apk
ApkPure.com
2109 1980-00-00 00:00 manifest.json
ApkPure.com
--------- -------
210243008 13 files

Categories

Resources