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
Related
Dear Developers
This in to bring to your kind notice that I have MotoG-2014 [2nd Gen] with me.
I recently rooted it successfully using guide given on the XDA forum itself. Post the root, I did checked using Root Checker Basic application about the fact whether I did the process successfully or not.
I did get the message: Congratulations! Root Access is properly installed on this device.
Current Device : XT-1068
Android version: 5.0.2
Once i was done with all this, I tried installing Titanium Backup[Pro version 6.1.0] but post every individual and multiple installs whenever I tried opening the application, it checks for ROOT ACCESS, which I did give every time but here I get a error stating that :
Sorry, I could not acquire root privileges. This application will *not* work! Please verify that your ROM is rooted, and try again.
This attempt was made using the "/system/xbin/su" command.
Now i don't understand why does this happen with Titanium, when Root Checker Basic application shows me Rooted, and I can also install
"Viper4AndroidFX" application which too requires phone to be rooted at the very first place.
I do not wish to reinstall the ROM again, since I did it properly with full clean swipe & cache + data properly cleaned at the first place after i bricked the phone last night.
[ UPDATED POST ]
The problem of Titanium backup arrives only when I am on OS version Lollipop 5.0.2. The titanium despite having root access doesn't surpass the Error on this OS.
I am sure of this statement, since due to some minor issues, I had to revert my Firmware back to STOCK version 4.4.4 and on that i got both the Root access and even the titanium worked perfectly fine.
Last night i re-updated my phone again to Lollipop 5.0.2 and as soon as I tried installing the Titanium Backup, I encountered the same error.
I guess its because of the OS version.
I am in no mood of reverting back to STOCK OS because I love Lollipop UI but how to resolve this Titanium Backup issue.
Can you guys HELP me please. !
Waiting for a response.
Thanks & regards.
Check to make sure you have the Super SU app by Chainfire app installed. When you open Titanium are you getting a notification from Super SU to allow it root access? When you open Super SU app, in Settings is it set to prompt for apps requiring root?
Tel864 said:
Check to make sure you have the Super SU app by Chainfire app installed. When you open Titanium are you getting a notification from Super SU to allow it root access? When you open Super SU app, in Settings is it set to prompt for apps requiring root?
Click to expand...
Click to collapse
Yes Its from Chainfire since, its visible when i open the settings option in the application. Yes if i install titanium and then start it, SuperSu does ask me permission and I clearly do remember that I have always clicked on "GRANT". Still the error is same no matter what I do & no matter how many times I uninstall and reinstall TB.
See the below screenshots just for reference purpose:
{
"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"
}
Help me please.
Response awaited.
Thanks & regards.
Try installing the free busybox app from Play. When you first run it, you have to let it run through your system and then choose smart install. It may take a couple of minutes for it to finish scanning your system. Reboot after you install.
Tel864 said:
Try installing the free busybox app from Play. When you first run it, you have to let it run through your system and then choose smart install. It may take a couple of minutes for it to finish scanning your system. Reboot after you install.
Click to expand...
Click to collapse
Installed the free busybox application as you told me to do. Here is the supporting screenshot :
This screen (mentioned above) came when I simply installed and started the application, had not restarted the phone yet.
However, when I restarted my phone and then started this application, I get this screen(below) :
Is it still possible since I recheched with Root Checker again and I got this screen :
P.S. - I have ROM TOOLBOX LITE too installed on my phone, and if my memory serves me right, its an application that too requires a ROOT on the device
By any chance Is it a case of "SOFT ROOT " . . ?
I just read about this somewhere while searching for this issue. So I ask & what can be done in this issue. ?
I personally never experienced nor did hear about such kind of a problem. So please HELP. . .
Response awaited.
Thanks & regards
If it were me, I would make sure I had the latest SuperSU zip, boot into TWRP recovery, clear dalvik/cache, flash Super SU again, clear dalvik/cache and reboot.
I would do what @Tel864 posted.
About Titanium: There is a version 7 out (sry no link,forgot where I got it from),Titanium 6 neither worked on my phone after rooting.
Sent from my XT1068 using XDA Free mobile app
Tel864 said:
If it were me, I would make sure I had the latest SuperSU zip, boot into TWRP recovery, clear dalvik/cache, flash Super SU again, clear dalvik/cache and reboot.
Click to expand...
Click to collapse
Ok let me try this way, and if I am not wrong. SuperSu v2.46 is the latest one only since everywhere i see this only.
Hope it helps me. Its weird though to see such kind of an issue cropping up for the first time ever.
Will respond back soon.
UPDATE -
I still see the same errors. Root Checker Basic shows my phone as rooted. TB produces the same error [ as mentioned in previous posts]. Couldn't bypass even after clicking on "GRANT".
Now what should I do, please HELP ME...
Response is more than awaited now.
Thanks & regards
Wolfcity said:
I would do what @Tel864 posted.
About Titanium: There is a version 7 out (sry no link,forgot where I got it from),Titanium 6 neither worked on my phone after rooting.
Sent from my XT1068 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah bro, am too giving it a try for once.
the reason why am still stuck on v6 especially this one is that brother its a pro version which i found here on xda only( though I don't remember as to which thread it was), the day i find another latest version[Pro] for TB, i would start using that.
Yeah then please do have a look, you might find that.
Waiting for response.
Thanks.
Titanium Backup Root access Issue
After upgrading I'm facing same problem in my MOTO E. I Still not find any solution!!
Any1 knows the solution?
I dont have a custom recovery to be able to flash the installation .zip file.
I do have root access, I have tried to manually by push the files to the correct location with correct permissions.
but it results in a bootloop.
I currently trying it on my Meizu mx4 with lollipop 5.0.1.
It used how to work without issues on K.K
Im trying it with the xposed-sdk21-arm-20150430.zip
with Xpossed 3.0 alpha2
Things I have tried.
http://bbs.flyme.cn/thread-245435-1-1.html
http://bbs.flyme.cn/thread-240899-1-1.html
Anyone have any ideas on how to get this working please
Thank you.
Did a quick search and found this:
http://forum.xda-developers.com/meizu-mx/general/mx4-flashing-recovery-t3102402
Hope that helps!
Djlatino said:
Did a quick search and found this:
http://forum.xda-developers.com/meizu-mx/general/mx4-flashing-recovery-t3102402
Hope that helps!
Click to expand...
Click to collapse
I'm not asking for a custom recovery, I know about the situation of meizu and not being open source that way.
I'm asking for a way to install Xposed successfully without a custom recovery by manually pushing the files etc.
But thank you.
If you read that thread, you'll note that in order to flash anything to begin with, you're going to need the recovery emulator "FlashGordon".
http://forum.xda-developers.com/showthread.php?t=2250555
^Spoonfeedin'
Djlatino said:
If you read that thread, you'll note that in order to flash anything to begin with, you're going to need the recovery emulator "FlashGordon".
http://forum.xda-developers.com/showthread.php?t=2250555
^Spoonfeedin'
Click to expand...
Click to collapse
I appreciate the help, I knew a app was about that could flash .zips without recovery, I will try it out.
Unfortunately it didnt work, didnt change any files in /system
punkmonkey1984 said:
I appreciate the help, I knew a app was about that could flash .zips without recovery, I will try it out.
Unfortunately it didnt work, didnt change any files in /system
Click to expand...
Click to collapse
The alternative approach is manually copying and pasting the zip files to the appropriate folders but I don't know what permissions you have to set for each of them besides the standard 664, so I apologize for not finding a solution, but I have a tablet that is pretty much in ter same ballpark as the MX4 so I'll monitor this thread!
Djlatino said:
The alternative approach is manually copying and pasting the zip files to the appropriate folders but I don't know what permissions you have to set for each of them besides the standard 664, so I apologize for not finding a solution, but I have a tablet that is pretty much in ter same ballpark as the MX4 so I'll monitor this thread!
Click to expand...
Click to collapse
I have tried to do that also, its working on the mx4 pro, but that has a different cpu chip.
Watch the video on this thread :http://bbs.flyme.cn/thread-240899-1-1.html
It explains how to copy/paste to the correct places.
Hopefully it works for you.
punkmonkey1984 said:
I have tried to do that also, its working on the mx4 pro, but that has a different cpu chip.
Watch the video on this thread :http://bbs.flyme.cn/thread-240899-1-1.html
It explains how to copy/paste to the correct places.
Hopefully it works for you.
Click to expand...
Click to collapse
http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
Check out flashfire, it seems to be more active than flashgordon.
Thanks for the link btw.
Djlatino said:
http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
Check out flashfire, it seems to be more active than flashgordon.
Thanks for the link btw.
Click to expand...
Click to collapse
Seems to have better support, coming from Chainfire etc, but it just results in black screen without progress.
Will keep searching for a solution tomorrow.
Ok, can get it to show installed, but after I reboot it is just resulting in bootloops.
Anyone have a solution!
{
"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"
}
punkmonkey1984 said:
Ok, can get it to show installed, but after I reboot it is just resulting in bootloops.
Anyone have a solution!
Click to expand...
Click to collapse
Same, got it installed, but boot loops for days.
Thank you based rovo for the Safe Mode
Djlatino said:
Same, got it installed, but boot loops for days.
Thank you based rovo for the Safe Mode
Click to expand...
Click to collapse
I did manage to get it installed and working without issues.
Follow the guide here: http://bbs.flyme.cn/forum.php?mod=viewthread&tid=254959&page=1&extra=#pid3301122
Files link: http://pan.baidu.com/s/1hq1pPUs
Basic chinese-> English:
1: Extracting installation charm Andrews 5.0 toolkit installation kingroot4.0 Mobile, the phone root, generally a few minutes to resolve.
2: the tmp folder, RE Manager copied to the system root directory, modify ub.sh tick all permissions.
3: Install a terminal emulator, open a terminal emulator to enter expert mode, choose Terminal Emulation, SU checkbox ticked above,
After entering sh /tmp/ub.sh carriage return (later sh space), etc. output stop after a while you can exit the terminal emulator.
4: Install xposed installer.apk, installation charm toolbox, open frame - module check Charm toolbox restart into effect.
I got it installed by wiping my data and trying on a fresh install before doing anything else, hopefully you wont have to do that.
Try removing all xposed related apps/modules before trying and rebooting/ clear catches before.
I used superSU not King user. Ignore charm-toolbox, thats a meizu flyme related module like gravity-box.
Follow the guide, then install xposed installer, mine didnt install, so i pushed in manually to /data/app with correct permissions then rebooted. I think it rebooted first time.
But a couple of times i have had to reboot by holding the power button for 10s because its gone into bootloop when activating new modules, but after it comes back on.
I got it to work another way, but my device is completely different.
What I did was install the installer, but right after I followed these instructions:
n root browser:
go to the /data/data/de.robv.android.xposed.installer/ and create folder "conf" (permissions rwxrwxrwx)
in folder "conf" create the file "jit_reset_offset" (permissions rw-r--r--)
Download Terminal Emulator, install and open it. Then:
type "su"
type "echo 0x98 > /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset"
Reboot the tablet.
Open Xposed Installer, install framework, reboot.
Click to expand...
Click to collapse
I gave that offset a shot and it luckily worked on mine. Unfortunately, the only way of getting the "offset" code is by analyzing some lib file, which I have yet to find out how to do. That being said, you can always try 0x98 a try as it seems to work on many. The default AOSP is 0x78, and some even have it as 184.
This does, however, fix most of the issues with "unsupported" devices out there, that seems to be the solution from rovo all the time.
punkmonkey1984 said:
I did manage to get it installed and working without issues.
Follow the guide here: http://bbs.flyme.cn/forum.php?mod=viewthread&tid=254959&page=1&extra=#pid3301122
Files link: http://pan.baidu.com/s/1hq1pPUs
Basic chinese-> English:
1: Extracting installation charm Andrews 5.0 toolkit installation kingroot4.0 Mobile, the phone root, generally a few minutes to resolve.
2: the tmp folder, RE Manager copied to the system root directory, modify ub.sh tick all permissions.
3: Install a terminal emulator, open a terminal emulator to enter expert mode, choose Terminal Emulation, SU checkbox ticked above,
After entering sh /tmp/ub.sh carriage return (later sh space), etc. output stop after a while you can exit the terminal emulator.
4: Install xposed installer.apk, installation charm toolbox, open frame - module check Charm toolbox restart into effect.
I got it installed by wiping my data and trying on a fresh install before doing anything else, hopefully you wont have to do that.
Try removing all xposed related apps/modules before trying and rebooting/ clear catches before.
I used superSU not King user. Ignore charm-toolbox, thats a meizu flyme related module like gravity-box.
Follow the guide, then install xposed installer, mine didnt install, so i pushed in manually to /data/app with correct permissions then rebooted. I think it rebooted first time.
But a couple of times i have had to reboot by holding the power button for 10s because its gone into bootloop when activating new modules, but after it comes back on.
Click to expand...
Click to collapse
I have installed xposed today by a very similar way that I have made but I am not sure if xposed totally installed.
Do you think that it is really installed?
I also have tried with the method of the chinese forum and the result is the same (basicaly is the same as my procedure).
There is any module to check it is really working? As you see I dont use much xposed
iicc said:
I have installed xposed today by a very similar way that I have made but I am not sure if xposed totally installed.
View attachment 3324770
Do you think that it is really installed?
I also have tried with the method of the chinese forum and the result is the same (basicaly is the same as my procedure).
There is any module to check it is really working? As you see I dont use much xposed
Click to expand...
Click to collapse
Flyme tools still works.
Did you encounter any bootloops?
You could try this one if your having trouble (not tested myself)
http://bbs.flyme.cn/thread-258466-1-1.html
punkmonkey1984 said:
Flyme tools still works.
Did you encounter any bootloops?
You could try this one if your having trouble (not tested myself)
http://bbs.flyme.cn/thread-258466-1-1.html
Click to expand...
Click to collapse
No bootloops so far.
[emoji33] [emoji33] thats the cofface cwm, I thought it didnt worked and the project was abandoned
iicc said:
No bootloops so far.
[emoji33] [emoji33] thats the cofface cwm, I thought it didnt worked and the project was abandoned
Click to expand...
Click to collapse
I'm not sure, I think it's only temporary cwm, I think it reverts back to the stock one after a reboot.
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.
Magisk v16.4 (also tried v16.0)
I've hidden the app in the HIDE list, I repackaged Magisk, force stopped NemID, cleared cache and data, and the app still spots root. I've successfully hidden apps from root before using this method, so it's just this app here that somehow goes beyond the usual. Are there any further steps I can take to hide root from the app more thoroughly?
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"
}
Launchy21 said:
Magisk v16.4 (also tried v16.0)
I've hidden the app in the HIDE list, I repackaged Magisk, force stopped NemID, cleared cache and data, and the app still spots root. I've successfully hidden apps from root before using this method, so it's just this app here that somehow goes beyond the usual. Are there any further steps I can take to hide root from the app more thoroughly?
Thanks
Click to expand...
Click to collapse
I believe that the app detects root by any of the following things :-
1. Bootloader unlocked detection
2. Custom ROM detection
3. Presence of apps that require root
4. Reading log of root being used (which is very rare, but possible)
5. Some very private code that renders Magisk useless
Tested it, and the app looks for both Magisk and the Manager. With the app on the Hide list and the Manager repackaged I can open the app without issue. It doesn't seem to "remember" root. This is on stock OxygenOS and also NitrogenOS (both on Oreo).
The app might be detecting other properties of the ROM your using (if not stock) or other known root apps on your device. Try running a logcat when the app detects "root" to maybe see what it's detecting, or simply uninstall some root apps and try again.
It works for me aswell, im using custom rom 8.1, hide the app, repackage, reboot, open app
So if that doesnt work, you might wanna try another rom as mentioned above me
It seems the app changed its way of detecting root after their upgrade on 25/6. It also worked for me before by using Magisk Hide and repack Magisk manager, but not anymore.
It is a losing battle anyway, just a matter of time. So I do not expect this method will work for good.
yeah my nemid app also stopped working a few days ago. This is not good if its not possible to hide root from an app anymore
Since there are users reporting that they can open up the app with MagiskHide active for NemID and the Manager repackaged, it's very likely that the app is detecting some other thing on your device. It could be a property of a custom ROM you're using, it could be a root app, etc... Possible solutions: try a different ROM (as stock as possible), uninstall root apps, etc.
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
Ok I'm running Samsung s7 stock oreo w. Root. Knox is tripped
Removed all apps needing root, installed magiskhide props config module, disabled systemless hosts.
Still no go. It worked until before latest update
mbeltoft said:
Ok I'm running Samsung s7 stock oreo w. Root. Knox is tripped
Removed all apps needing root, installed magiskhide props config module, disabled systemless hosts.
Still no go. It worked until before latest update
Click to expand...
Click to collapse
What Magisk version do you have? If not on beta v16.4, the issue might be that the app has a sub-process that previous Magisk versions can't hide automatically. Scratch that... Just went back and saw that the OP has tested it on v16.4.
Or, if you're unlucky it's checking Knox...
Does it only check for root at the start, or is it other points as well? As stated before, I can open the app just fine on both my Oneplus 3T and Nexus 6.
AFAIK it's only checking at start-up. It shows it's load screen for a few seconds ( but longer than before when it was working) and then give the error screen OP posted.
If you leave the app and reenter it it will show the main screen but jump back to the error screen whenever a button is pressed
I tested this on a pixel 2 with stock rom in this order :
All root apps installed, no magisk or root : working fine
All root apps installed, no magisk or root, custom kernel: working fine
All root apps installed, root and magisk, magisk hidden+magisk hide: not working
No root apps installed, root and magisk, magisk hidden+magisk hide: not working
No root apps installed, root and magisk, magisk manager not installed+magisk hide: working
I then tried cloning the apk without changing the name: not working
I tried cloning the app but changing the name of Magisk Manager from "Magisk Manager" to just "Manager" and then Nemid worked again.
Could it be the Nemid app is just looking to see if there's an app called Magisk Manager installed and if there is, the app failes
Unfortunately the cloned app doesn't work. Maybe we could have the "Hide magisk" function rename the app name too?
//Peter
Just tried cloning an entirely different app and renaming it "Magisk Manager" - after this the nemid app failed, so I guess that confirms that nemid just checks the name.
//Peter
Nice detective work.
By uninstall the app (not unroot) NemID works. If you use magisk 16.6 you can just reboot phone to get the manager again or just install the apk.
But if being able to change magisk managers name to something generic (like manager) or a custom name could be a great solution (I would change name to NemID). Because if nemid can defeat magiskhide, others will follow
I posted the findings in the beta thread but I think it got removed during thread cleanup. Any other way to let the developers know?
peter_dk01 said:
I posted the findings in the beta thread but I think it got removed during thread cleanup. Any other way to let the developers know?
Click to expand...
Click to collapse
It's already on the to-do list.
Didgeridoohan said:
It's already on the to-do list.
Click to expand...
Click to collapse
Perfect! Thank you ?
Didgeridoohan said:
It's already on the to-do list.
Click to expand...
Click to collapse
Unfortunately, the change is not included in the latest 5.8.1 release.
kqueenc said:
Unfortunately, the change is not included in the latest 5.8.1 release.
Click to expand...
Click to collapse
Manager v5.8.1 was simply a bug fix. Stability is prioritised over new features. You'll have to wait, and that feature will be available when it's available. Not before that...
Didgeridoohan said:
Manager v5.8.1 was simply a bug fix. Stability is prioritised over new features. You'll have to wait, and that feature will be available when it's available. Not before that...
Click to expand...
Click to collapse
Is there any other workaround to change the name of Magisk Manager App in order to bypass the check? And will there be any other consequence (like root cannot be detected by other app)?
kqueenc said:
Is there any other workaround to change the name of Magisk Manager App in order to bypass the check? And will there be any other consequence (like root cannot be detected by other app)?
Click to expand...
Click to collapse
Until there is a feature like that, you can uninstall or freeze the Manager whenever you need to use whatever app detects it.
Hi guys.
For those of you that recently unlocked your bootloader and rooted your device with Magisk... If you don't already know, you can download a Magisk Module created by Didgeridoohan, called 'MagiskHide Props Config'. Basically this solves the issue of the ctsProfile failing in safetynet. What it does is it can change the device fingerprint to one that is certified, allowing safetynet to pass.
I lot of you probably already know this, but I've read a lot posts about ctsProfile issues.
With this module, you should be able to use ANY official huawei mate 20 pro firmware and safetynet should pass.
There is more info about this module in thread https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228
So what is the steps you need to follow?
I have u locked bootloader and safety et is failing. At cts.
Evert hing is stock and wiped.
Verstuurd vanaf mijn LYA-L29 met Tapatalk
First root the phone. Flash the patched recovery_ramdisk.img posted in this thread https://forum.xda-developers.com/mate-20-pro/how-to/guide-manual-updating-firmware-t3893171
Follow the Rooting intructions.
Once you've done that. Go into Magisk Manager and search for MagiskHide Props Config
Download and install it.
Reboot the phone.
Download Terminal Emulator from the google play store
Open it and grant root access by typing su
Run the command 'props'
Then just follow the instructions.
What if I don't want the root. Is it possible to get the ctf error false to fixed without rooting but having bootloader unlocked?
Verstuurd vanaf mijn LYA-L29 met Tapatalk
aygul12345 said:
What if I don't want the root. Is it possible to get the ctf error false to fixed without rooting but having bootloader unlocked?
Verstuurd vanaf mijn LYA-L29 met Tapatalk
Click to expand...
Click to collapse
Not that I know of. I know certain firmwares don't get the error so you could try out a few until you find one that passes safetynet.
eg. for me, I know the .183 passes safetynet without having to change the fingerprint or anything else.
DN38416 said:
First root the phone. Flash the patched recovery_ramdisk.img posted in this thread https://forum.xda-developers.com/mate-20-pro/how-to/guide-manual-updating-firmware-t3893171
Follow the Rooting intructions.
Once you've done that. Go into Magisk Manager and search for MagiskHide Props Config
Download and install it.
Reboot the phone.
Download Terminal Emulator from the google play store
Open it and run the command 'props'
Then just follow the instructions.
Click to expand...
Click to collapse
What am I doing wrong?
I've unlocked bootloader, rooted, installed the module you suggested, rebooted, installed terminal emulator and ran the 'props' command.
{
"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"
}
jfenlon01 said:
What am I doing wrong?
I've unlocked bootloader, rooted, installed the module you suggested, rebooted, installed terminal emulator and ran the 'props' command.
Click to expand...
Click to collapse
Did you follow the instructions and change the device fingerprint?
Reboot after that. Check the safetynet in Magisk and it should pass ctsProfile now.
(Unless your BasicIntegrity is also failing then this module won't work)
EDIT: Sorry.. the pic didn't load before.
Hmm... Looks like the module isn't installed properly if you have that error.
are you definitely in rooted state? (Hold volume up as you boot up)
Yep, definitely rooted.
jfenlon01 said:
Yep, definitely rooted.
Click to expand...
Click to collapse
That’s weird. I’m not sure what’s wrong then. I assume you tried rebooting again?
Maybe read through the documentation on the main thread and look in the troubleshooting section? Mine works as soon as I enter the props command.
What version of Magisk are you using? 18.1?
Yeah 18.1, downloaded from this forum. I tried to patch my own with magisk but it wouldn't boot. Still no joy.
jfenlon01 said:
What am I doing wrong?
I've unlocked bootloader, rooted, installed the module you suggested, rebooted, installed terminal emulator and ran the 'props' command.
Click to expand...
Click to collapse
First type "su" to grant root
jfenlon01 said:
Yeah 18.1, downloaded from this forum. I tried to patch my own with magisk but it wouldn't boot. Still no joy.
Click to expand...
Click to collapse
I noticed this in the documentation in the thread.
"MagiskHide Props Config v2.7.2 and earlier versions won't work on Magisk v18.1-d73127b1(18006) or later, due to internal changes in Magisk."
Does that apply to your situation?
Th3PorTuGa said:
First type "su" to grant root
Click to expand...
Click to collapse
OMG I can't believe I forgot about that. Yeah make sure it has root access first sorry. Typing su will bring up the prompt to grant root access. You might need to have Magisk Manager running in the background.
DN38416 said:
I noticed this in the documentation in the thread.
"MagiskHide Props Config v2.7.2 and earlier versions won't work on Magisk v18.1-d73127b1(18006) or later, due to internal changes in Magisk."
Does that apply to your situation?
Click to expand...
Click to collapse
I tried su already guys, it's in the first screenshot.
Also magisk props config v3.5.0 so that from the documentation shouldn't apply either.
Thanks for trying to help.
jfenlon01 said:
I tried su already guys, it's in the first screenshot.
Also magisk props config v3.5.0 so that from the documentation shouldn't apply either.
Thanks for trying to help.
Click to expand...
Click to collapse
do it again and make sure Magisk manager is running beforehand
Close both apps and start again. Open Magisk Manager, then open Terminal Emulator and type su, it should then come up with the prompt to grant root access.
Once it's granted THEN you can run the 'props' command
I tried also 'props' with the ' in case that's what was required. Just can't get it to work.
[edit]
I'm thinking it's because I didn't have the Magisk Busybox module by osm0sis, installing that and will try again.
---------- Post added at 02:48 PM ---------- Previous post was at 02:34 PM ----------
Still no joy
That’s strange. Not sure what’s wrong.
I’m outa ideas. Have you tried uninstalling and reinstalling MagiskHide props module?
DN38416 said:
That’s strange. Not sure what’s wrong.
I’m outa ideas. Have you tried uninstalling and reinstalling MagiskHide props module?
Click to expand...
Click to collapse
Yep, tried that twice. Most recently after installing Magisk Busybox.
Thanks for trying to help.
I'm getting the same issue unfortunately, no idea why "props" isn't found
Will I be able to run banking apps?
Sent from my LYA-L09 using Tapatalk