Database Develop

[MODULE] App Systemizer for Magisk v9-v14 -- DEPRECATED

Instead of including the third party APK files in the magisk modules/repo, this module, developed by @loserskater and me, systemizes user-installed apps systemlessly thru magisk. Another benefit of systemizing the user-installed apps is that if you uninstall magisk, your settings for the apps will be retained. If you originally install any of the apps above thru an app-specific magisk module (like Pixel Launcher magisk module for example), then when magisk is uninstalled or disabled, app settings will be gone.
If you're on Oreo ROM, you will need this add-on developed by @yochananmarqos: https://forum.xda-developers.com/apps/magisk/module-privileged-permission-whitelist-t3670646
This module requires installation from Magisk Manager, not recovery.
This module might lead to your device stuck on logo or booting to recovery, I gather it might be a kernel issue -- the closer you're to stock firmware/kernel the more likely it is to work. If it fails, try the "Terminal App Systemizer" instead.
Important links:
README
AppSystemizer commits
Companion app commits
NOW IN OFFICIAL MAGISK REPO!
11.0.6: This is the last "classic/simple" version I could get from github, (11.0.6) which might fail on the larger APKs but doesn't include magisk partition resizing code which might cause problems. It also does NOT include a companion app.
12.0.5: This is the latest "stable" version with the companion app. Based on pre-"magisk 13" template (version 3), but seems to work with magisk 13.
14.0.0: This is the 12.0.5 version migrated to 1400 template (released with magisk 14). Not tested by me, so use at your own risk (but please post back wherever it does/does not work).
The source code (with history) is available here if anyone wants to continue development: https://github.com/stangri/AppSystemizer

So since the new apk for Pixel Launcher is available and it has a different signature than previously leaked apk files, here's the list of steps you need to take to replace your Pixel Launcher if used with this module:
1. Go to Magisk Manager and delete (or disable) the App Systemizer module.
2. Reboot.
3. After step 2 your Pixel Launcher should no longer be a system app and you should be able to uninstall old Pixel Launcher -- do so (with your favourite root uninstall app or thru System Settings -> Apps -> Pixel Launcher -> Uninstall).
4. Install the new Pixel Launcher.
5. Add again (or reactivate) the App Systemizer module.
6. Reboot TWICE.
7. The new Pixel Launcher should be active and working as a system app now.

ForceDoze

Playe said:
ForceDoze
Click to expand...
Click to collapse
Please try the attached ZIP after you have installed the app from the play store and remember to reboot twice. Post back if it works and why do you need it to be a system app.

Does this essentially make it a system app without it actually being in the system, or am I not understanding this correctly?
Sent from my Nexus 6 using XDA-Developers mobile app

pnwsr6 said:
Does this essentially make it a system app without it actually being in the system?
Click to expand...
Click to collapse
Precisely, it makes the user-installed app a system app without actually modifying the /system partition.

Can it support Cerberus anti-theft?
Sent from my Nexus 6 using XDA-Developers mobile app

pnwsr6 said:
Can it support Cerberus anti-theft?
Click to expand...
Click to collapse
It sure can, I'm not sure if the "magiskized" Cerberus would survive data reset tho. Can you try it out please? Just make sure to reboot TWICE after installing the attached module before the big reset.

OK. It will be this weekend before I can get to it. Doing all the research and downloading ahead of time. Figured I would try some of this systemless stuff out before upgrading to far. Not upgrading to N yet but is this systemmless stuff seem to be working OK with N?
Sent from my Nexus 6 using XDA-Developers mobile app

pnwsr6 said:
OK. It will be this weekend before I can get to it. Doing all the research and downloading ahead of time. Figured I would try some of this systemless stuff out before upgrading to far. Not upgrading to N yet but is this systemmless stuff seem to be working OK with N?
Click to expand...
Click to collapse
Smart move. Yeah, no major issues on Nexus 6 and released Nougat. DP5 was draining my battery, but that seems to have been fixed in the release build. There seems to be a problem with magisk CACHE modules (they don't install on Nexus 6) but these are far and few between.
BTW, OTAs which affect the boot partition will kill magiskized Cerberus until you reflash magisk.

stangri said:
Smart move. Yeah, no major issues on Nexus 6 and released Nougat. DP5 was draining my battery, but that seems to have been fixed in the release build. There seems to be a problem with magisk CACHE modules (they don't install on Nexus 6) but these are far and few between.
BTW, OTAs which affect the boot partition will kill magiskized Cerberus until you reflash magisk.
Click to expand...
Click to collapse
Should this make Cerberus show up as a system app in something like Titanium backup? I can't get Cerberus to turn on gps like it would if it was installed as a system app. Shouldn't this allow it to behave like a system app or am I wishing for to much?
FYI
I had Cerberus installed first
Ran the zip file in Magisk
rebooted after install
rebooted again
logged into my Cerberus Dashboard and tried to track my phone and it will not turn on my gps like it will if installed into the system
If this is a limitation that can't be avoided I understand. If I did something wrong or can try something else let me know. Also I did this on my nexus 6 running N. Supersu seems to work and Adaway is installed and seems to be working so far. Latest twrp is also installed, everything is systemless so far. Thanks for your time

pnwsr6 said:
Should this make Cerberus show up as a system app in something like Titanium backup? I can't get Cerberus to turn on gps like it would if it was installed as a system app. Shouldn't this allow it to behave like a system app or am I wishing for to much?
FYI
I had Cerberus installed first
Ran the zip file in Magisk
rebooted after install
rebooted again
logged into my Cerberus Dashboard and tried to track my phone and it will not turn on my gps like it will if installed into the system
If this is a limitation that can't be avoided I understand. If I did something wrong or can try something else let me know. Also I did this on my nexus 6 running N. Supersu seems to work and Adaway is installed and seems to be working so far. Latest twrp is also installed, everything is systemless so far. Thanks for your time
Click to expand...
Click to collapse
If you have a file manager which can browse system partition, can you verify that there's a folder /system/priv-app/CerberusAntiTheft and its permissions are the same as the other folders in /system/priv-app? If it's there and still Cerberus doesn't behave like a proper system app then I don't know what's wrong.
PS. I believe installing twrp prevents OTAs from being installed so kinda contradicts the whole systemless concept. I only boot twrp thru fastboot when needed (usually just once to install magisk/phh root).

stangri said:
If you have a file manager which can browse system partition, can you verify that there's a folder /system/priv-app/CerberusAntiTheft and its permissions are the same as the other folders in /system/priv-app? If it's there and still Cerberus doesn't behave like a proper system app then I don't know what's wrong.
PS. I believe installing twrp prevents OTAs from being installed so kinda contradicts the whole systemless concept. I only boot twrp thru fastboot when needed (usually just once to install magisk/phh root).
Click to expand...
Click to collapse
Do not see it.
Sent from my Nexus 6 using XDA-Developers mobile app

pnwsr6 said:
Do not see it.
Click to expand...
Click to collapse
That's weird, but now we found the reason Cerberus is not working as expected.
Can you please check if the following exist:
/magisk/AppSystemizer/system/priv-app/CerberusAntiTheft
/data/app/com.lsdroid.cerberus* (could be -1, -2, etc).
If there's no /data/app/com.lsdroid.cerberus* -- my module couldn't find the installed Cerberus. Can you find out what canonical package ID did they use then?

stangri said:
That's weird, but now we found the reason Cerberus is not working as expected.
Can you please check if the following exist:
/magisk/AppSystemizer/system/priv-app/CerberusAntiTheft
/data/app/com.lsdroid.cerberus* (could be -1, -2, etc).
If there's no /data/app/com.lsdroid.cerberus* -- my module couldn't find the installed Cerberus. Can you find out what canonical package ID did they use then?
Click to expand...
Click to collapse
So I found /magisk/AppSystemizer but no more folders after that. So /system/priv-app/CerberusAntiTheft is missing.
/data/app/com.Isdroid.cerberus-1 directory exists and has the lib and oat directories plus the base.a pk in it. Forgive my lack of knowledge on this but how do I find the canonical package ID?
Sent from my Nexus 6 using XDA-Developers mobile app

Ok, I sincerely hope you just grabbed the attachment from the first post (which I posted before I added Cerberus support) and not from my reply to you down in the thread. Was the ZIP file you installed named AppSystemizer.zip or AppSystemizer-Cerberus.zip?
I still don't want to update the original attachment, so could you please add the ZIP attached to this reply to magisk and then reboot twice.
PS. If you're reading this on mobile, I don't know how the attachments show up for you, but you need the most recent AppSystemizer-Cerberus.zip file from this thread.

OK, so I deleted the old zip, it was AppSystemizer-Cerberus.zip, and removed the module. Rebooted and verified that it was removed from the magisk directory, rebooted one more time, then installed the zip you just posted for me. Rebooted twice. Went through and looked for the directories you had me looking for earlier, and they are still not there. Let me know what else I can do.
Sent from my Nexus 6 using XDA-Developers mobile app

pnwsr6 said:
OK, so I deleted the old zip, it was AppSystemizer-Cerberus.zip, and removed the module. Rebooted and verified that it was removed from the magisk directory, rebooted one more time, then installed the zip you just posted for me. Rebooted twice. Went through and looked for the directories you had me looking for earlier, and they are still not there. Let me know what else I can do.
Click to expand...
Click to collapse
Just installed Cerberus app and got it converted to systemless with the module.
Can you PM me (or post here) the magisk log?
PS. Does magisk have root access?

stangri said:
Just installed Cerberus app and got it converted to systemless with the module.
Can you PM me (or post here) the magisk log?
PS. Does magisk have root access?
Click to expand...
Click to collapse
{
"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"
}
Magisk has root access. Or at least I get the toast notification saying it was granted and it shows up in the SuperSU logs. I'm sure I have done something wrong, or something didn't install correctly. Just not sure what.
Sent from my Nexus 6 using XDA-Developers mobile app

pnwsr6 said:
I'm sure I have done something wrong, or something didn't install correctly. Just not sure what.
Click to expand...
Click to collapse
I'm sure it's just MM vs N difference and nothing you didn't do. Thanks for sticking by. Can you please try replacing the module with the attached AppSystemizer-debug.zip, rebooting and posting/PMing the log. This version should print stuff to the magisk log file helping me figure out what's going on.
PS. No need to uninstall existing module, just add this ZIP over the old one.

Fail to login SnapChat -> MagiskHide Activated

I have activated MagiskHide
{
"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"
}
but SN has failed ... And i dosn't can connect
If you would know how to make everything green
Thx

https://www.didgeridoohan.com/magisk

Didgeridoohan said:
https://www.didgeridoohan.com/magisk
Click to expand...
Click to collapse
I have Delt Xposed but I am using it :/

1. Delete snapchat.
2. Install again.
3. Go to magisk hide and check snapchat
4. Try to login.
5. If it won't help, unroot phone, login to snapchat and root again.
Redmi Note 4X RR 6.0.0 Tapatalk

voxan24 said:
I have Delt Xposed but I am using it :/
Click to expand...
Click to collapse
Disable Xposed -> reboot -> Check SafetyNet (should be green) -> Login to Snapchat -> Enable Xposed -> reboot -> enjoy
Works for me.

worked for me too (last post )
on note 4 8.1.0 ustom rom with last version of magisk at the time of this post

I have the issue that I can not login on snapchat with magisk installed.
Magisk manager is hidden (as you can see a part of the package name in the 3rd line of the magisk manager part)
Snapchat is ticked in the magisk hide
You can see that safety net is passing and still I can not login on snapchat until I uninstall magisk.
I tried using a snapchat build from october 2018 (non beta) and it didn't let me log in either.

FPSUsername said:
I have the issue that I can not login on snapchat with magisk installed.
Magisk manager is hidden (as you can see a part of the package name in the 3rd line of the magisk manager part)
Snapchat is ticked in the magisk hide
You can see that safety net is passing and still I can not login on snapchat until I uninstall magisk.
I tried using a snapchat build from october 2018 (non beta) and it didn't let me log in either.
Click to expand...
Click to collapse
Did you fix it?

pixelgasm said:
Did you fix it?
Click to expand...
Click to collapse
Nope, just uninstall magisk, login and reinstall it. Use a secondary user account to login into other accounts, apparently you don't have magisk there, so it isn't being detected.

How to use Snapchat with magisk (After Ban)
FPSUsername said:
Nope, just uninstall magisk, login and reinstall it. Use a secondary user account to login into other accounts, apparently you don't have magisk there, so it isn't being detected.
Click to expand...
Click to collapse
Follow these steps to use Snapchat with magisk -
1.) Update to latest Magisk stable build v20.0 - https://github.com/topjohnwu/Magisk/...gisk-v20.0.zip
2.) After updating magisk, Go to Magisk Manager > Magisk Hide and check/enable Snapchat and Google Services (all services have to be marked).
3.) Hide Magisk Manager by it self, go to Magisk Manager > Settings and "Hide Magisk Manager" so it will repack Magisk Manager with random name.
4.) Delete "busybox" binary from /system/xbin directory and install BusyBox module from Magisk Manager > Downloads.
5.) Clear data and cache of Snapchat, try to login this time, it will work for sure, if it doesn't, login to this and click unlock my account - https://accounts.snapchat.com/accounts/login?continue=https://accounts.snapchat.com/accounts/welcome
I have tried this myself and it works, my first main account was permanent banned on magisk canary build, After that I deleted that account and started out with fresh new account.
Tested on -
Samsung Galaxy S9+
Rom - Ulitamte Rom v11.3
Magisk - v20.0 (Stable)
Kernel - ElementalX

LELBOT said:
Follow these steps to use Snapchat with magisk -
1.) Update to latest Magisk stable build v20.0 - https://github.com/topjohnwu/Magisk/...gisk-v20.0.zip
2.) After updating magisk, Go to Magisk Manager > Magisk Hide and check/enable Snapchat and Google Services (all services have to be marked).
3.) Hide Magisk Manager by it self, go to Magisk Manager > Settings and "Hide Magisk Manager" so it will repack Magisk Manager with random name.
4.) Delete "busybox" binary from /system/xbin directory and install BusyBox module from Magisk Manager > Downloads.
5.) Clear data and cache of Snapchat, try to login this time, it will work for sure, if it doesn't, login to this and click unlock my account - https://accounts.snapchat.com/accounts/login?continue=https://accounts.snapchat.com/accounts/welcome
I have tried this myself and it works, my first main account was permanent banned on magisk canary build, After that I deleted that account and started out with fresh new account.
Tested on -
Samsung Galaxy S9+
Rom - Ulitamte Rom v11.3
Magisk - v20.0 (Stable)
Kernel - ElementalX
Click to expand...
Click to collapse
I hope you realize that it's an old post of mine. Ofc things changed in the past months. It seems to work fine if you just add snapchat to magisk hide. None of the other steps you mentioned are needed. I haven't tried it without the magisk hide, but I think that it will work as well.

Hello there,,
I am stuck in the same problem .. I did every step mentioned above and Safetynet check is always green & successful .. but still Snapchat is able to identify that I have Root on my device..
I can't find any real useful way that works 100% to hide the root. Snapchat allows me to login without problems but after like 2 - 3 days it send me a message that it will lock my account because of the " use of third-party app " ! .. Now my account is locked for 2 weeks and I read that it could be permanently locked !
I really need help .. I'm using ported samsung Note 7 fan edition ported Light Rom

aimmhr said:
Hello there,,
I am stuck in the same problem .. I did every step mentioned above and Safetynet check is always green & successful .. but still Snapchat is able to identify that I have Root on my device..
I can't find any real useful way that works 100% to hide the root. Snapchat allows me to login without problems but after like 2 - 3 days it send me a message that it will lock my account because of the " use of third-party app " ! .. Now my account is locked for 2 weeks and I read that it could be permanently locked !
I really need help .. I'm using ported samsung Note 7 fan edition ported Light Rom
Click to expand...
Click to collapse
Same problem here, I'm on Magisk v20.4 and i can't find a way to hide root to the latest Snapchat build with Android 9 even with Magisk hide activated on Snapchat and Google services.
As far as i remember, i never had this problem on Android 8 with Magisk v19.3 and Magisk hide activated.

Natizyskunk said:
Same problem here, I'm on Magisk v20.4 and i can't find a way to hide root to the latest Snapchat build with Android 9 even with Magisk hide activated on Snapchat and Google services.
As far as i remember, i never had this problem on Android 8 with Magisk v19.3 and Magisk hide activated.
Click to expand...
Click to collapse
Sad to know that you got the same problem..
Even the latest Magisk did not provide a solution for this issue.
For me the only way to use snapchat is to use a non rooted rom.. It works .. but Android phone without root is not interesting ..

aimmhr said:
Sad to know that you got the same problem..
Even the latest Magisk did not provide a solution for this issue.
For me the only way to use snapchat is to use a non rooted rom.. It works .. but Android phone without root is not interesting ..
Click to expand...
Click to collapse
I've finally found a way to make it working again !
This is what i've done :
1) Log-in to snapchat.
2) Root with magisk.
3) Magisk Hide: Snapchat, Google, Google Play Store, Google services framework, Google Play services.
4) Install Magisk module "MagiskHide Props Config" (needed to pass SafetyNet control: ctsProfile + basicintegrity).
5) Install Magisk module "HARDWARE OFF" (needed to reset SafetyNet evalType from HARDWARE to BASIC) : https://forum.xda-developers.com/showpost.php?p=83028387&postcount=40658.
6) Go to Magisk options and select 'Hide Magisk Manager' to repack magisk with a new name (needed to completely hide the root).
7) Make sure Signature Verification is not disable and that no patches have been installed to android via "LuckyPatcher".
8) If installed, pleas uninstall "RIRU" Magisk module and any "riru"-related modules.
9) If installed, please make sure to uninstall Xposed Framework or any variant (systemless_Xposed, EdXposed, etc...) and all modules from it.
10) Make sure to uninstall LuckyPatcher if you have it and delete all residual files.
11) If installed, please uninstall Busybox and re-install it systemless-ly via the magisk module.
12) Now run this script in termux to fix snapchat root-detection (this will clean up your system file structure so it'll not return any false positives) : https://pastebin.com/haHtch32
If everything is done correctly, you should be able to use snapchat again without any issues and also without to worry about being banned again. At least for now ^^
Hope this can help.
Btw, sorry for my bad english, it's not my native language.

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.

Hiding Magisk Manager wont work 100% correctly

Hey,
I have the problem that if I install Magisk and repack the App with a different name, the app will be duplicated after reboot. If I do not reboot, the app will start (Without hiding Magisk Manager self and only the app, not) One says that I have to install manager app, and the other stuck on splash screen.
Here is a screenshot of the "hidden" magisk manager, after reboot I dont have root access to make another screenshot cause there is now "hey, here is root acquired prompt"
{
"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"
}
I really need this feature for using an important app. Without the magisk manager hide function it will be dedected (Magisk Hide for app is active)
Using Honor 8x wit EMUI 8.2, Android 8.1 and Magisk v17.1 (stable)
Hope anyone have a solution.
Regards
Schmand

Schmand said:
Hey,
I have the problem that if I install Magisk and repack the App with a different name, the app will be duplicated after reboot. If I do not reboot, the app will start (Without hiding Magisk Manager self and only the app, not) One says that I have to install manager app, and the other stuck on splash screen.
Here is a screenshot of the "hidden" magisk manager, after reboot I dont have root access to make another screenshot cause there is now "hey, here is root acquired prompt"
I really need this feature for using an important app. Without the magisk manager hide function it will be dedected (Magisk Hide for app is active)
Using Honor 8x wit EMUI 8.2, Android 8.1 and Magisk v17.1 (stable)
Hope anyone have a solution.
Regards
Schmand
Click to expand...
Click to collapse
First of all, download latest Magisk version (17.3 as of now). Then uninstall Magisk from TWRP by using the uninstaller zip. Reboot your device, then reboot back to recovery and install the latest Magisk version again. Reboot and open Magisk Manager, then re-install Magisk with a different package name. Open Magisk Manager again and use the Magisk Hide option to select Google Play Services as well as Google Play Store in addition to the app that shouldn't detect Magisk. Reboot your device again and check if everything works as intended.

Portgas D. Ace said:
First of all, download latest Magisk version (17.3 as of now). Then uninstall Magisk from TWRP by using the uninstaller zip. Reboot your device, then reboot back to recovery and install the latest Magisk version again. Reboot and open Magisk Manager, then re-install Magisk with a different package name. Open Magisk Manager again and use the Magisk Hide option to select Google Play Services as well as Google Play Store in addition to the app that shouldn't detect Magisk. Reboot your device again and check if everything works as intended.
Click to expand...
Click to collapse
Hey, which services exactly? Just fingind the google play store app. But not the other one you mentioned. If I just hide them (with the app) it doesnt work )=

Schmand said:
Hey, which services exactly? Just fingind the google play store app. But not the other one you mentioned. If I just hide them (with the app) it doesnt work )=
Click to expand...
Click to collapse
Magisk hides itself from Google Play Service by default, forgot about it. Did you also re-install Magisk Manager with a different package name? You also might want to try deleting the Magisk Manager folder on your internal storage and reboot.

Portgas D. Ace said:
Magisk hides itself from Google Play Service by default, forgot about it. Did you also re-install Magisk Manager with a different package name? You also might want to try deleting the Magisk Manager folder on your internal storage and reboot.
Click to expand...
Click to collapse
Hey, that doesnt work, too. After I hide magisk most of the time it say, that I dont have magisk installed. If I remove the hided app and install normal magisk manager app. Everything works fine, but without the app I need (cause will detected that magisk installed). Testet also with RR rom. Same result ._.
//SmallEditAgain
If I dont reboot now, anything work. Until I reboot => Brocken

@Schmand
I had the same "Magisk not installed" issue when re-installing Magisk with a different package name. I then just rebooted my device again and the "new" Magisk Manager app showed up. When I opened it, it said "Magisk installed" and everything was working from there on.
By the way, what's the app that you are trying to hide Magisk from?

Portgas D. Ace said:
@Schmand
I had the same "Magisk not installed" issue when re-installing Magisk with a different package name. I then just rebooted my device again and the "new" Magisk Manager app showed up. When I opened it, it said "Magisk installed" and everything was working from there on.
By the way, what's the app that you are trying to hide Magisk from?
Click to expand...
Click to collapse
Hey, thats not working for me )= Tried many times.
The app I want to hide is "Sparkasse pushTAN" now I just deinstall Magisk every time I need a tan. But that is verry stupid work ._.

Have you tried the latest Canary build? The issue described by the OP is caused by magisk.db issues, and those should have been taken care of with some recent commits.

Didgeridoohan said:
Have you tried the latest Canary build? The issue described by the OP is caused by magisk.db issues, and those should have been taken care of with some recent commits.
Click to expand...
Click to collapse
Latest canary build? What did you mean, downloaded and installed magisk 17.3 (Beta)
//EDIT
Set up the custom repository to canary build and updated magisk manager and patched boot image. Now I hide the app and will see whats happening
//UPDATE
It worked for me. Thank you a lot :good::highfive::highfive:

Magisk Manager: Manager was denied Superuser rights (and buttons missing)

Please see the posted screenshot image for the problem. I just got a brand new OnePlus 8 Pro today, updated the firmware (it's current and running Android 11), unlocked the bootloader, installed my data, and rooted it. Since there is no TWRP for Android 11 for this device, I had to manually extract the current boot.img and patch it myself with Magisk Manager to root this device.
On the first boot after root, I launched Magisk Manager. The countdown timer was so fast, I did not have a chance to grant Magisk Manager root permissions. Now Magisk Manager is being denied Superuser permissions, and there are no buttons at the bottom of Magisk Manager to set Magisk Hide settings or set what apps are allowed Superuser/root.
I have googled as well as searched this forum for relevant help, and have found nothing helpful (really, I may have missed something, but I did try). How can I reset the apps allowed root permissions so that I can grant Magisk Manager the Superuser permissions it needs to function?
{
"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"
}
Any help is greatly appreciated!
I already tried force stopping Magisk Manager and clearing the storage for Magisk Manager (which did nothing to solve the problem).

https://www.didgeridoohan.com/magisk/Magisk#hn_Magisk_Manager_was_denied_superuser_access

Didgeridoohan said:
https://www.didgeridoohan.com/magisk/Magisk#hn_Magisk_Manager_was_denied_superuser_access
Click to expand...
Click to collapse
Thank you for the reply. I found this article earlier (or a variant of it), and it does not appear to solve the issue. I don't have two different Magisk Managers installed. I just accidently denied the one Superuser access by not granting it Superuser access quickly enough.

The Magisk app does not need to ask for superuser access. It is the one that grants it... In other words, one way or the other Magisk is looking for a hidden Magisk app with a package name that doesn't match the one you're using.
Try deleting /data/adb/magisk.db. It'll reset everything (including granted superuser requests, etc) and you can reinstall the app and start over.

Didgeridoohan said:
The Magisk app does not need to ask for superuser access. It is the one that grants it... In other words, one way or the other Magisk is looking for a hidden Magisk app with a package name that doesn't match the one you're using.
Try deleting /data/adb/magisk.db. It'll reset everything (including granted superuser requests, etc) and you can reinstall the app and start over.
Click to expand...
Click to collapse
Thank you. This is no longer an issue (I have a new issue that is unrelated to this thread, so I'll search for the solution to it).

chriv said:
Thank you. This is no longer an issue (I have a new issue that is unrelated to this thread, so I'll search for the solution to it).
Click to expand...
Click to collapse
Just out of curiosity, did you solve it be deleting the database file?

Didgeridoohan said:
Just out of curiosity, did you solve it be deleting the database file?
Click to expand...
Click to collapse
I wish I could say, yes, but no. Long story short, I started over from a clean phone install. Unfortunately, (this part is off topic), I accidently upgraded to 11.0.4.4.IN11AA with an OTA after starting over (the version almost nobody has yet), didn't realize it, and patched a stock 11.0.2.2.IN11AA boot.img and flashed it to the boot partition. Magisk and root worked great, but WiFi and phone calls were broken. Now I'm stuck waiting to get the 11.0.4.4.IN11AA full package (Global/NA/US version of 11.0.4.4) to fix everything (by extracting the boot.img from a payload dumper).

So you mean that deleting the database file didn't work, or that you never tried it?

Sorry if I was unclear. I didn't try it. My phone was already in a state where I could not try it (and this no longer applied) before I saw this message. I am very grateful for the assistance/information.

I have the same problem. can you help me?

kas001 said:
I have the same problem. can you help me?
Click to expand...
Click to collapse
Have you already checked to see if this is the cause? https://www.didgeridoohan.com/magisk/Magisk#hn_Magisk_Manager_was_denied_superuser_access. It's definitely the best starting point.

Just for anyone else finding this thread having this issue and forgetting they told Magisk to change it's APK name to stay hidden like I did. Look for a second "Settings" app on your phone. That's what Magisk changes itself to.

SparJar said:
Just for anyone else finding this thread having this issue and forgetting they told Magisk to change it's APK name to stay hidden like I did. Look for a second "Settings" app on your phone. That's what Magisk changes itself to.
Click to expand...
Click to collapse
Yeah, I did forgot that I have changed magisk name to "settings" and magisk is working fine right now.

aleep123 said:
Yeah, I did forgot that I have changed magisk name to "settings" and magisk is working fine right now.
Click to expand...
Click to collapse
Can you please explain?

ivanov_16 said:
Can you please explain?
Click to expand...
Click to collapse
There's a setting in the Magisk app where you can rename it with a random package name, to hide it and make the app harder to detect. This will give it a generic Android icon and give it the same "Settings" (previously it would name the repackaged app "Manager").

OK I missed the prompt to grant access to the ADB shell. Where's the settings for all the applications permission grants? So that I can untick the "deny" for ADB shell. I've changed the setting from prompt to grant, and tried again. But the toast just says Shell denied superuser access.
Thanks.
--Chris
EDIT:
OK I just installed a terminal app and nuked
/data/adb/magisk/magisk.db
which allowed me to start the permission process over.
This sure seems like a brutal approach to grant/permission management. It also requires starting the whole process from scratch.

SparJar said:
Just for anyone else finding this thread having this issue and forgetting they told Magisk to change it's APK name to stay hidden like I did. Look for a second "Settings" app on your phone. That's what Magisk changes itself to.
Click to expand...
Click to collapse
You are a superstar!! I have been tearing my hair out for acouple of days now trying to work out why i could not reinstall magisk, this was exactly the solution to the problem i was facing, therefore i give you my gratitude.

I have the same issues after updating to v24.1 how can I Access to delete the duplicate apps of Magisk. It was naming to Settings.

After the 25206
Didgeridoohan said:
So you mean that deleting the database file didn't work, or that you never tried it?
Click to expand...
Click to collapse
I on the other hand tried it. Not sure if it works or not. After the 25206 to 25207 disaster, 25208 is finally normal except it can't hide itself anymore. Any solutions there? Many thanks. F Droid file explorer/Network Signal Guru also lost super user rights. Rootchecker now says it's not properly rooted

I tried deleting /data/adb/magisk/magisk.db with Termux but can't even access it as I get "permission denied" and am still seeing SuperUser and Modules greyed out. Tried sudo, was prompted to install 'tsu' package and it failed as it appears the host no longer exists