Related
I recently had a problem (see here) with SuperSU, so I decided to give MagiskSU a try. As it turns out, it seems to have the same issue. When I run a process that requires su, it stalls for a while. In the case of MagiskSU, I then get "Permission denied" after about 20 seconds.
Here's what I get with a few basic commands:
Code:
[email protected]:/ $ su
Permission denied
Code:
[email protected]:/ $ su -v
8:MAGISKSU (topjohnwu)
Code:
[email protected]:/ $ su -V
8
Additionally, when I view the log with adb logcat, I see the following message attributed to su:
Code:
exec am failed with 2: No such file or directory
It looks like this is a message produced here, related to loading am.jar. Unlike in my SuperSU situation, this error happens regardless of whether Magisk is set to "prompt" or "grant".
Any idea how I can debug this? Thanks in advance.
Just to make sure: Have you updated the Magisk Manager so that it's just not the stub installed by the Magisk zip?
And if so, does the Manager report you're properly rooted?
I figured it out. In a previous cleanup attempt, I failed to restore the link named /system/bin/app_process that points to /system/bin/app_process64. This fixed it:
From the TWRP terminal:
Code:
mount /system
cd /system/bin
ln -s app_process64 app_process
Frankly I'm surprised this didn't render my phone unbootable! Nothing else was noticeably affected.
I have the same problem, just logcat says:
W/Magisk: su: request rejected (2000->0)
I found a solution that worked for me, go to Magisk Manager and install "ADB & Fastboot for Android NDK" module, then reboot.
I found in the Magisk app under Superuser that "shell" had the toggle turned off. Once I turned it on, su worked in ADB.
Lletfrix said:
I found a solution that worked for me, go to Magisk Manager and install "ADB & Fastboot for Android NDK" module, then reboot.
Click to expand...
Click to collapse
You are my Hero...
:good::good::good:Thank You Very Much brooo... :good::good::good:
Hi all,
I have Magisk v18.1 and I'm also trying to get root access from shell. When I run 'su' in a terminal emulator, I get the message 'Permission denied'.
I did install "ADB & Fastboot for Android NDK" as suggested above. I also checked the root options in the magisk app (v7.0.0) and they are all the default, nothing unusual there.
Could you kindly advice if there is anything I can do in order to get root access from the shell with Magisk?
Thanks a lot in advance
I have a same issue on kitkat
Oh boy, I have *absolutely no idea* what I did but it works now. Well, what I did was that I removed the adb & fastboot module and rebooted. When I ran 'su' again in the terminal, I got a request from magisksu to grant authorization. Not sure what's going on, but it works!
geo909 said:
Oh boy, I have *absolutely no idea* what I did but it works now. Well, what I did was that I removed the adb & fastboot module and rebooted. When I ran 'su' again in the terminal, I got a request from magisksu to grant authorization. Not sure what's going on, but it works!
Click to expand...
Click to collapse
Why did you install the ADB and fastboot module? That's for using that device to control ADB and fastboot of another device as if the device with the module were a computer.
madbat99 said:
Why did you install the ADB and fastboot module? That's for using that device to control ADB and fastboot of another device as if the device with the module were a computer.
Click to expand...
Click to collapse
Honestly, that was a classic case of not knowing what I'm doing and just blindly following what other people tried. But good to know what the purpose of that module was, I was wondering!
Hint: Perfdump is the adb shell program, do not disable SU for it
I add my hint: after getting this error message, I checkd the list of apps in Magisk SU: it turned out that I had disabled the "Perfdump" app, because I did not know what it was. It is the adb shell indeed!
I had exactly the same problem on my Android 6.0 with Magisk v19.3 + Magisk Manager v7.3.1. I tried everything, what you wrote (enabled, disabled the "ADB and fastboot" stuff, checked the symlink, ...), but nothing helped me. FYI: previously, I used LineageOS 16 (Android 9.0) on the same phone with this latest Magisk without any problem (but I decided to turn back to the original OS version to avoid instabilities). But now I'm fighting with this dragon.
My wife has Android 6.0 also w/ Magisk, but she got Magisk v18.0 and this works well now... I tried this at me, and surprisingly, that was worked well. Now, I decided to find out, which is the last working version, where is the bug.
The results:
* the Magisk v18.0 with the bundled Magisk Manager - GOOD
* the Magisk v18.0 with the latest Magisk Manager v7.3.2 - GOOD
* the Magisk v18.1 with the latest Magisk Manager v7.3.2 - GOOD
* the Magisk v19.0 with the latest Magisk Manager v7.3.2 - BAD
* the Magisk v19.1 with the latest Magisk Manager v7.3.2 - BAD
* the Magisk v19.2 with the latest Magisk Manager v7.3.2 - BAD
* the Magisk v19.3 with the latest Magisk Manager v7.3.2 - BAD
I don't know, the freshest working Magisk v18.1 + Magisk Manager v7.3.2 is a good combination for all cases, but looks working.
Lletfrix said:
I found a solution that worked for me, go to Magisk Manager and install "ADB & Fastboot for Android NDK" module, then reboot.
Click to expand...
Click to collapse
Yup thanks it still works up to date
Solved
i had the same problem on my redmi note 7 and the most easiest way is unistall your magisk 20.xxx and install a older one 19.xxx and that should do it but remember bouth zip file (flashibile zip) and magisk apk has yo be older than 20.xxx becouse the devs has made a mistake in the coding( or at leat this is what i think hope im wrong)
just update the magisk manager and install automatically the boot and reboot the phone it will be okay
Solution that works for me GalaxyS9 (starlte)
### restart adbd as root
adb root
### then
adb shell
### WORKS.
### I see '#' in prompt, `whoami` responses: 'root'
### My Magisk version. Reported by `su -v`
23.0:MAGISKSU
[Mudule] Root Call SMS Manager Patch
THIS MODULE ITSELF IS NOT A CALL BLOCKER, It is patch to work this Root call manager properly with Magisk
Introduction :
Basically I was not using Magisk for two purposes (Even though there were many good aspects to have magisk, but ultimately it's matter of priorities)
1.Broken Dumpsys
2.Root level call blocker was not working which is must app for me. (I know about two root call blocker available on play store)
Since Magisk V15 bring dumpsys so finally thought to look into root call manager so I can use Magisk with it's awesome Magisk hide functions.
Module :
Root call SMS Manager available on play store have mentioned some work around to use with magisk but didn't worked for me.
I have looked into it and sharing here a module which I have made for me and working fine on my Samsung Galaxy Note8. I believe it should work on more devices as well so sharing here.
Installation :
1.Download attached RCM Patch 1.1.apk and Install as regular app
2.Clcik on app icon from drawer
3.Grant su permission
4.Keep patience while it activate module.
App is self destructive and will get uninstalled once module get activated.
Reboot device when asked/app get uninstalled.
Un-Installation :
Magisk Manager - Module - Root call manager Patch - Delete from here
Tips for RCM
- In System setting, you should set proper "submode' according your device
- Wait after reboot option recommended to keep 0 but if you need to increase, better keep below 20 sec.
Disclaimer :
I am not owner of Root Call Manager app, Just made a module and shared here to work application correctly with magisk root. Any query regarding RCM should go to proper channel and not here.
Can somebody confirm, what version of Magisk you are using?
From my end the apk is not working with the Magisk 18.1. Please, can you updated it?
Thanks you
It Is Now A Part Of The Main Module Of MultiFunctions & Its Thread https://forum.xda-developers.com/apps/magisk/module-multifunctions-bootloop-t3933386.
Click to expand...
Click to collapse
Introduction:
Simple Module To Clear The Data Of Google Play Store & Google Play Services.
- One Of The Methods To Solve/Fix The Battery Draining & Re-Check PlayStore Device Certification Status
- After The Installation & 1st Reboot, It Clears The Data Of PS-GMS & Disables Itself
- After Doing Its Functionality, Check PlayStore Device Certification Status (Google PlayStore --> Settings --> Play Protect/Device Certification) Which Should Be Hidden For A While During Getting Its Status From Google
- Enabling The Module = Doing Its Functionality & Disabling Itself (Next Reboot)
Current Version: 1.0.3.3
- The Module Is Just A Step To Solve/Fix The Battery Draining & Re-Check PlayStore Device Certification Status Which Means Maybe You Need To Do Additional Steps To Solve The Issue
- For Magisk Users, Disable Magisk Core Only Mode From The Section Of Settings In Magisk Manager Which Is Required As An Essential Step To Activate The Functionality Of ClearPlayStoreWithServicesData
- For Activating The Functionality Of ClearPlayStoreWithServicesData, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> PlayStoreWithServicesData --> Copy The File Of Disable To The Folder Of Inactive --> Reboot
Created: May.13.2018
Updated: May.09.2019
Download Link: Click Here
- For The Module Which Is Ended Its Name With v1300, It Supports Magisk v13.1(1310) To v13.6(1360)
- For The Module Which Is Ended Its Name With v1400, It Supports Magisk v14.0(1400) To v15.3(1531)
- For The Module Which Is Ended Its Name With v1500, It Supports Magisk v15.0(1500) To v17.3(17300)
- For The Module Which Is Ended Its Name With v17000, It Supports Magisk v17.0(17000) To v17.3(17300)
- For The Module Which Is Ended Its Name With v18000, It Supports Magisk v18.0(18000) To v18.1(18100)
- For The Module Which Is Ended Its Name With v19000, It Supports Magisk v19.0(19000) To The Latest Version
- For The Module Which Is Ended Its Name With Unity, It Supports Any-Rooting-Tool Such As SuperSU, Lineage-AddOnSU & Magisk
Installation:
- Magisk Manager --> Modules --> Add (+) --> Choose The Downloaded File --> Reboot
- Or Flash It Thru TWRP Recovery
- Or Flash It Thru ADB Sideload --> adb sideload Module.zip --> Reboot
- Or Using A Flash-Tool (Flasher) Such FlashFire, Flashify Or Rashr --> Flash ZIP File (Flash A Flashable ZIP File) --> Choose The Downloaded File --> Reboot
General Info:
- To Disable The Module For Magisk Users, Open Magisk Manager --> Modules --> The Module --> Tap On The Check Box/The True Icon --> Reboot
- To Enable The Module For Magisk Users, Open Magisk Manager --> Modules --> The Module --> Tap On The Uncheck Box --> Reboot
- To Uninstall The Module For Magisk Users, Open Magisk Manager --> Modules --> The Module --> Tap On The Bin Icon --> Reboot
- To Disable The Module For All Users [Non-Magisk Users & Magisk Users], Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> The Module --> Copy The File Of Disable To The Folder Of Active (Or Delete The File Of Disable From The Folder Of Inactive) --> Reboot
- To Enable The Module For All Users [Non-Magisk Users & Magisk Users], Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> The Module --> Delete The File Of Disable From The Folder Of Active (Or Copy The File Of Disable To The Folder Of Inactive) --> Reboot
- To Uninstall The Module For All Users [Non-Magisk Users & Magisk Users] (Unity), Reflash The Module
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Installing/Configuring An App, Download SafeMode4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-safe-mode-bootloop-bootscreen-t3847422 Then Flash It
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Adding App/Activity/Process To Magisk Hide, Download ClearHideList4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-hide-list-bootloop-bootscreen-t3849208 Then Flash It
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Flashing A Module, Download CoreOnlyMode4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-core-mode-bootloop-solver-modules-t3817366 Then Flash It
Click On Thanks Button If The Module/Post Is Useful (Dreamer(3MF))
>>> Sharing A Good Thought Is Gold <<<
----------------------------------------------------------------------------------------------------------------
SELinux Mode Inverter - Clear Dalvik Cache - Core Only Mode - Other Modules
----------------------------------------------------------------------------------------------------------------
Reserved for News/Updates #1
I'm confused about this.... Is it the same as clicking clear date in app settings?
yung40oz84 said:
I'm confused about this.... Is it the same as clicking clear date in app settings?
Click to expand...
Click to collapse
Yes, But One Of Its Advantages Is Giving The System An Opportunity To Detect The Change At The Booting Stage.
yung40oz84 said:
I'm confused about this.... Is it the same as clicking clear date in app settings?
Click to expand...
Click to collapse
Did You Try The Module?
For Magisk v1400, Download ClearPlayStoreWithServicesData4Magisk-v1.0.0(v1400)(3MF).zip
Dreamer(3MF) said:
For Magisk v1400, Download ClearPlayStoreWithServicesData4Magisk-v1.0.0(v1400)(3MF).zip
Click to expand...
Click to collapse
Link is dead. Can you relink please
edit. got off internet site
---------- Post added at 05:07 PM ---------- Previous post was at 04:15 PM ----------
Is 1400 newest?
mattie_49 said:
Link is dead. Can you relink please
edit. got off internet site
---------- Post added at 05:07 PM ---------- Previous post was at 04:15 PM ----------
Is 1400 newest?
Click to expand...
Click to collapse
I Relinked The Title With The File Again. You Can Also Download The Module From OP(The 1st Post) Under The Attached Files Section.
Kindly Be Informed That
- For The Module Which Is Ended Its Name With v1400, It Will Support Magisk v14.0(1400) To v15.3(1531)
- For The Module Which Is Ended Its Name With v1500, It Will Support Magisk v15.0(1500) To The Latest Version Which Is Currently v16.4(1642)
Dreamer(3MF) said:
Kindly Be Informed That
- For The Module Which Is Ended Its Name With v1400, It Will Support Magisk v14.00(1400) To v15.3(1531)
- For The Modules Which Is Ended Its Name With v1500, It Will Support Magisk v15.0(1500) To The Latest Version Which Is Currently v16.4(1642)
Click to expand...
Click to collapse
That explains why 1400 was causing madness on Oreo with 16.4 Magisk. Should just be one. Everyone has surely updated to latest haven't they?
mattie_49 said:
That explains why 1400 was causing madness on Oreo with 16.4 Magisk. Should just be one. Everyone has surely updated to latest haven't they?
Click to expand...
Click to collapse
No, I Hope That The Latest Version Of Magisk To Be Suitable For All Devices But It Relies On Many Factors Such As Boot Image, Kernel, Rom & Magisk Itself.
Are you sure that a SafetyNet infection is not more complicated?
I would really appreciate your input on this, as my Galaxy S5 on stock 6.0.1 is infected by SafetyNet. I re-flashed to stock and am about to flash Magisk 16.4. I am trying to decide whether a dreaded factory reset to wipe /data is necessary to get rid of the SafetyNet failed state. What I am afraid of is that there may be a cross-infection between /data/data (gapps) and installed apps that cooperate closely with SafetyNet.
In particular in my case, for example, an app "NOAA Weather" reports frequently back to Google and warned me to to update Play Services after I restored Play Services to a stock version. Poking around in Play Services SqLite databases in /data/data (...gms) I found an unencrypted database listing the NOAA Weather app executable name. I am afraid that the NOAA Weather app's data may also have my device blacklisted. And who knows where else in /data the SafetyNet failed state may be flagged?? What is your opinion about this?
Thank you!
BruceElliott said:
I would really appreciate your input on this, as my Galaxy S5 on stock 6.0.1 is infected by SafetyNet. I re-flashed to stock and am about to flash Magisk 16.4. I am trying to decide whether a dreaded factory reset to wipe /data is necessary to get rid of the SafetyNet failed state. What I am afraid of is that there may be a cross-infection between /data/data (gapps) and installed apps that cooperate closely with SafetyNet.
In particular in my case, for example, an app "NOAA Weather" reports frequently back to Google and warned me to to update Play Services after I restored Play Services to a stock version. Poking around in Play Services SqLite databases in /data/data (...gms) I found an unencrypted database listing the NOAA Weather app executable name. I am afraid that the NOAA Weather app's data may also have my device blacklisted. And who knows where else in /data the SafetyNet failed state may be flagged?? What is your opinion about this?
Thank you!
Click to expand...
Click to collapse
Kindly Do The Following
- Did You Install BusyBox/Xposed? And If So, Disable/Uninstall BusyBox/Xposed --> Reboot
- Enable WiFi --> Send The Screenshot Of PlayStore Device Certification Status (Google PlayStore --> Settings --> Device Certification)
- Install RootBeer Sample From PlayStore --> Send Its Screenshots Before Adding This App To Magisk Hide & After Adding This App To Magisk Hide
- Magisk Manager --> Tap To Start SafetyNet Check --> Send Its Screenshot
- Install SafetyNet Helper Sample From PlayStore & Send Its Screenshot
- Magisk Manager --> Modules --> Send Its Screenshots
- Magisk Manager --> SuperUser --> Send Its Screenshots
- From Settings --> About Phone --> SELinux Status --> Send Its Screenshot
- Complete Info About The Device, The Used Rom & The Used Kernel
- Send Full Logcat (Download Logcat Extreme From PlayStore) & Magisk Log (Magisk Manager --> Log --> Magisk & SuperUser)
- Install Terminal Emulator From PlayStore --> Open It --> Write su --> Click On Enter --> Write which busybox --> Click On Enter --> Send Its Screenshot
- Use Terminal Emulator From PlayStore --> Open It --> Write su --> Click On Enter --> Write magiskhide --ls --> Click On Enter --> Send Its Screenshot
- Use Terminal Emulator From PlayStore --> Open It --> Write su --> Click On Enter --> Write which su --> Click On Enter --> Send Its Screenshot
- Use Terminal Emulator From PlayStore --> Open It --> Write su --> Click On Enter --> Write getenforce --> Click On Enter --> Send Its Screenshot
- Use Terminal Emulator From PlayStore --> Open It --> Write su --> Click On Enter --> Write sestatus --> Click On Enter --> Send Its Screenshot
General Steps For Passing The SafetyNet & Certifying The Device:
- Download ClearPlayStoreWithServicesData4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-google-playstore-services-data-t3789498 & Flash It Thru Magisk Manager Then Reboot
- Wait About 15-30 Min. Then Check PlayStore Device Certification Status & Try To See Netflix/Pokemon-Go From PlayStore
- If It Didnot Work, Did You Install BusyBox/Xposed? And If So, Disable/Uninstall BusyBox/Xposed --> Reboot
- Check Again The SafetyNet, PlayStore Device Certification Status & Try To See Netflix/Pokemon-Go From PlayStore
- If It Didnot Work, Download SELinuxModeInverter4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/selinux-mode-inverter-t3775271 & Flash It Thru Magisk Manager Then Reboot
- Check Again The SafetyNet, PlayStore Device Certification Status & Try To See Netflix&Pokemon-Go From PlayStore
- If It Didnot Work, Download DeviceSpoofingTool4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/qa-want-to-install-modules-magisk-v13-3-t3800435 & Flash It Thru Magisk Manager Then Reboot
- Wait About 15-30 Min. Then Check Again The SafetyNet, PlayStore Device Certification Status & Try To See Netflix/Pokemon-Go From PlayStore
- If It Didnot Work, Download ClearDalvikCache4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-dalvik-cache-t3787264 & Flash It Thru Magisk Manager Then Reboot
- Wait About 15-30 Min. Then Check Check Again The SafetyNet, PlayStore Device Certification Status & Try To See Netflix/Pokemon-Go From PlayStore
General Steps For Using Netflix:
- Uninstall Netfilx If Installed
- Download ClearPlayStoreWithServicesData4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-google-playstore-services-data-t3789498 & Flash It Thru Magisk Manager Then Reboot
- Wait About 15-30 Min. Then Check PlayStore Device Certification Status & Use Netflix From PlayStore
- If It Didnot Work, Did You Install BusyBox/Xposed? And If So, Disable/Uninstall BusyBox/Xposed --> Reboot
- Check Again The SafetyNet, PlayStore Device Certification Status & Use Netflix From PlayStore
- If It Didnot Work, Download Netflix Enabler From This Thread https://forum.xda-developers.com/apps/magisk/module-netflix-enabler-enable-netflix-t3708126 & Flash It Thru Magisk Manager Then Reboot
- Check Again The SafetyNet, PlayStore Device Certification Status & Use Netflix From PlayStore
- If It Didnot Work, Disable Netflix Enabler From Magisk Manager
- Download Liboemcrypto Disabler From This Thread https://forum.xda-developers.com/apps/magisk/magisk-liboemcrypto-disabler-drm-t3794393 & Flash It Thru Magisk Manager Then Reboot
- Check Again The SafetyNet, PlayStore Device Certification Status & Use Netflix From PlayStore
- If It Didnot Work, Download SELinuxModeInverter4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/selinux-mode-inverter-t3775271 & Flash It Thru Magisk Manager Then Reboot
- Check Again The SafetyNet, PlayStore Device Certification Status & Use Netflix From PlayStore
- If It Didnot Work, Download DeviceSpoofingTool4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/qa-want-to-install-modules-magisk-v13-3-t3800435 & Flash It Thru Magisk Manager Then Reboot
- Wait About 15-30 Min. Then Check Again The SafetyNet, PlayStore Device Certification Status & Use Netflix From PlayStore
- If It Didnot Work, Download ClearDalvikCache4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-dalvik-cache-t3787264 & Flash It Thru Magisk Manager Then Reboot
- Wait About 15-30 Min. Then Check Again The SafetyNet, PlayStore Device Certification Status & Use Netflix From PlayStore
Jvirg said:
Magisk manager?
Click to expand...
Click to collapse
Dreamer(3MF) said:
Kindly Do The Following
- Did You Install BusyBox/Xposed? And If So, Disable/Uninstall BusyBox/Xposed --> Reboot
- Install RootBeer Sample From PlayStore & Send Its Screenshot
- Install SafetyNet Test From PlayStore & Send Its Screenshot
- Send The Screenshot Of PlayStore Device Certification Status
Thanks for the assistance, Dreamer. Screenshots attached below. Note that I:
**Used adb to query for device fingerprint, created the text file with fingerprint and placed it at root of internal sdcard per Didgeridoohan's instructions on github for his MagiskHide Props Config module. I ran the module, selected "2" I believe (the selection to enhance hiding). It seemed to work without throwing errors, but it doesn't give much feedback so its hard to know.
Thank you!
Click to expand...
Click to collapse
BruceElliott said:
Dreamer(3MF) said:
Kindly Do The Following
- Did You Install BusyBox/Xposed? And If So, Disable/Uninstall BusyBox/Xposed --> Reboot
- Install RootBeer Sample From PlayStore & Send Its Screenshot
- Install SafetyNet Test From PlayStore & Send Its Screenshot
- Send The Screenshot Of PlayStore Device Certification Status
Thanks for the assistance, Dreamer. Screenshots attached below. Note that I:
**Used adb to query for device fingerprint, created the text file with fingerprint and placed it at root of internal sdcard per Didgeridoohan's instructions on github for his MagiskHide Props Config module. I ran the module, selected "2" I believe (the selection to enhance hiding). It seemed to work without throwing errors, but it doesn't give much feedback so its hard to know.
Thank you!
Click to expand...
Click to collapse
Regarding busybox, I did not install one specifically; however Titanium installs with its own. I believe that there may also be a system busybox, but not sure.
Click to expand...
Click to collapse
BruceElliott said:
Dreamer(3MF) said:
Kindly Do The Following
- Did You Install BusyBox/Xposed? And If So, Disable/Uninstall BusyBox/Xposed --> Reboot
- Install RootBeer Sample From PlayStore & Send Its Screenshot
- Install SafetyNet Test From PlayStore & Send Its Screenshot
- Send The Screenshot Of PlayStore Device Certification Status
Thanks for the assistance, Dreamer. Screenshots attached below. Note that I:
**Used adb to query for device fingerprint, created the text file with fingerprint and placed it at root of internal sdcard per Didgeridoohan's instructions on github for his MagiskHide Props Config module. I ran the module, selected "2" I believe (the selection to enhance hiding). It seemed to work without throwing errors, but it doesn't give much feedback so its hard to know.
Thank you!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
According To The Sent Screenshots, PlayStore Device Certification Status Is Certified & Your Device Passed The SafetyNet. Is There Anything Else You Want To Check?
BruceElliott said:
BruceElliott said:
Regarding busybox, I did not install one specifically; however Titanium installs with its own. I believe that there may also be a system busybox, but not sure.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Install Terminal Emulator From PlayStore --> Open It --> Write su --> Click On Enter --> Write which busybox --> Click On Enter --> Send Its Screenshot
Dreamer(3MF) said:
Install Terminal Emulator From PlayStore --> Open It --> Write su --> Click On Enter --> Write which busybox --> Click On Enter --> Send Its Screenshot
Click to expand...
Click to collapse
I believe that I am good on this thread, Dreamer; thank you!
This is an excellent script and did what I struggled to do manually.
I feel there's a noticeable difference in the battery consumption post this script as I'm being a bit more conscious about what Google options to permit this time around.
Great work.
Sent from my SM-N910F using Tapatalk
-------------------------------------------------------------------------------------------------------------------------
Hi,
I'm having a problem with Magisk 18.1. When I open Magisk Manager, I see the "Magisk is not installed" error message with the X in a red circle. However, Magisk Manager is up to date. I also get toast messages that say that "Manager was denied superuser rights". However, I'm able to get root in adb shell and entering "su".
If I refresh Magisk Manager by pulling down and releasing, then the following message:
Code:
Requires Additional Setup
Your device needs additional setup for Magisk to work properly. It will download the Magisk setup zip, do you want to proceed now?
Choosing "YES" will produce a "Setup failed." toast message. However, I see that now, "Magisk is up to date".
Despite this, I don't see the full set of Magisk settings (such as Magisk Hide, etc). Also, if I kill the process and reopen Magisk, I will get the same error message again.
I've tried downloading the Magisk v18.1 zip file and reflashing it in TWRP, but still no go.
Device: Nexus 5X with Android 6.0.1
Magisk: v18.1 (18100)
Magisk Manager: v7.0.0
Reflash stock rom and try to reflash if not work wait an update or try to downgrade version
Envoyé de mon ONEPLUS A6003 en utilisant Tapatalk
Sounds like you've ended up with two conflicting Magisk Managers installed (one repackaged, one not). Like this: https://www.didgeridoohan.com/magisk/Magisk#hn_Updating_from_v18.0_to_v18.1
Didgeridoohan said:
Sounds like you've ended up with two conflicting Magisk Managers installed (one repackaged, one not). Like this: https://www.didgeridoohan.com/magisk/Magisk#hn_Updating_from_v18.0_to_v18.1
Click to expand...
Click to collapse
Thanks! That was exactly it!
I'm running into the same problem. No dual install of manager, either.
Happens on a fresh from-scratch install of v18.1 on a Moto X Pure
Same here, clean install of v18.1 on Mi Max 3 (MIUI 10.2.1.0)
FWIW the problem still exists in v19, with it happening multiple times a day now in 19.3
---------- Post added at 01:31 PM ---------- Previous post was at 01:19 PM ----------
Check out this thread, esp. reply #14 (updated version) :
https://forum.xda-developers.com/apps/magisk/magisk-installed-workaround-t3908748
error as well v20.3 on Pocophone, Download and Install zip..installation error
go to settings>apps>magisk manager>allow storage permission.
Magisk update installation failed
I'm also having same problem with the latest update v20.4. I tried installing via Magisk app but it failed. I also tried flashing through recovery but same response.
I also had a similar issue, on a wiped phone. Magisk manager showing magisk not installed. However, using su from adb brought up a superuser request dialogue. I granted it, it hung for a minute, then when I reopened magisk manager it showed that magisk was successfully installed.
Solution
goister said:
Hi,
I'm having a problem with Magisk 18.1. When I open Magisk Manager, I see the "Magisk is not installed" error message with the X in a red circle. However, Magisk Manager is up to date. I also get toast messages that say that "Manager was denied superuser rights". However, I'm able to get root in adb shell and entering "su".
If I refresh Magisk Manager by pulling down and releasing, then the following message:
Code:
Requires Additional Setup
Your device needs additional setup for Magisk to work properly. It will download the Magisk setup zip, do you want to proceed now?
Choosing "YES" will produce a "Setup failed." toast message. However, I see that now, "Magisk is up to date".
Despite this, I don't see the full set of Magisk settings (such as Magisk Hide, etc). Also, if I kill the process and reopen Magisk, I will get the same error message again.
I've tried downloading the Magisk v18.1 zip file and reflashing it in TWRP, but still no go.
Device: Nexus 5X with Android 6.0.1
Magisk: v18.1 (18100)
Magisk Manager: v7.0.0
Click to expand...
Click to collapse
Just install Disable_Dm-Verity_ForceEncrypt_12.27.2019.zip via TWRP
Can get it from here https://4pda.ru/forum/index.php?s=&showtopic=774072&view=findpost&p=97675211
Can't download this DM verity can't find it (used Google translator from Russian to English).
My problem is magisk manager says denied superuser so I can't use magisk hide since I can't reach it(limited options) but my fone is rooted and the new apps get grant or refuse and I can grant them superuser but need magisk hide for banking apps and all. On the latest magisk. Check attachment.
Please help please.
Cheers,
Roger
TheKicKer69 said:
Can't download this DM verity can't find it (used Google translator from Russian to English).
My problem is magisk manager says denied superuser so I can't use magisk hide since I can't reach it(limited options) but my fone is rooted and the new apps get grant or refuse and I can grant them superuser but need magisk hide for banking apps and all. On the latest magisk. Check attachment.
Please help please.
Cheers,
Roger
Click to expand...
Click to collapse
Check here:
Magisk - Installation and troubleshooting:Magisk and MagiskHide Installation and Troubleshooting guide
www.didgeridoohan.com
tried EVERYTHING except clean ROM install. not working still says Magisk Manager denied superuser rights and magisk hide and all missing
TheKicKer69 said:
tried EVERYTHING except clean ROM install. not working still says Magisk Manager denied superuser rights and magisk hide and all missing
Click to expand...
Click to collapse
Uninstalled the Magisk Manager, and possibly also the hidden Manager (named "Manager" or whatever name you gave it) with the generic Android icon? And if you uninstalled both of them, installed the apk again manually?
nothing worked - wiped fone and reinstalled - magisk up and running again
phone: Redmi 6A
magisk manager version : latest version
magisk version: latest verion
xposed installer : 3.1.5
Andoid version: 8.1.0
MIUI Version: 10.3.4 stable OCBCNXM
I have installed magsik and xposed installler, but install framework failed on the xposed installler . It shows the following error：
Code:
failed to get root access
make sure you device is rooted properly and you have bot blocked shell command
I known I can grant root previlege to xposed via super user function on the magisk. but xposed apply for root access can not show up on the super user .
I make sure my phone gets root and other applications can show up on the super user, I can grant other app root previlege.
My issue is the same as this post
https://forum.xda-developers.com/oneplus-6/help/xposed-root-access-t3817346
if I search xposed framework in the magisk download . it will be download file error occurred. maybe in the China, some domain name can not access, so download failed. if u have xposed_framewok-v90-beta3(9030).zip ( about 106MB) files. could you share to me?
forgive my English level pls. because English not my first language.
Thank you in advance!!!
xsstest said:
phone: Redmi 6A
magisk manager version : latest version
magisk version: latest verion
xposed installer : 3.1.5
Andoid version: 8.1.0
MIUI Version: 10.3.4 stable OCBCNXM
I have installed magsik and xposed installler, but install framework failed on the xposed installler . It shows the following error：
I known I can grant root previlege to xposed via super user function on the magisk. but xposed apply for root access can not show up on the super user .
I make sure my phone gets root and other applications can show up on the super user, I can grant other app root previlege.
My issue is the same as this post
https://forum.xda-developers.com/oneplus-6/help/xposed-root-access-t3817346
if I search xposed framework in the magisk download . it will be download file error occurred. maybe in the China, some domain name can not access, so download failed. if u have xposed_framewok-v90-beta3(9030).zip ( about 106MB) files. could you share to me?
forgive my English level pls. because English not my first language.
Thank you in advance!!!
Click to expand...
Click to collapse
I don't own your model of phone so maybe not much help.
Xposed and root are two separate things.
Xposed by it self ( plus modules ) does not require root access ( installation is another thing ) They provide different functionality.
Using xposed installer app root access maybe required for things like logging access. Not for installing apps or running them.
Xposed apps installed requiring root access should ask for it.
Using rovo's versions
https://dl-xda.xposed.info/framework/
Using magisk version try this
https://github.com/Magisk-Modules-Repo/xposed/blob/master/README.md
You will the right installer app to use as well.
Edit:
Other option with Xposed framework is to use through magisk ( since Android 8 i believe ) is to use Riru core module + Edxposed module.
Still need the right installer modules thought.