Hi,
I'm currently so confused as to why my Magisk isn't working. I'm currently running the last CM 13 snapshot for the Galaxy S5 (G900F, klte), and root and Xposed work fine via Magisk.
However, what isn't working is Magisk Hide, and I'm not sure why. However, I'm noticing that even though I fully unrooted cm-su (using SuperSU, in a way that means the only root I can select in Dev Options is ADB only), I'm still getting cm-su detected by Magisk.
I'm confused -- is there anyway I can remove it? I've tried looking through TWRP file manager, but whenever I do so, I can't even see /system/ files, and mounting only mounts to USB, but that's unrelated.
Thanks for any help!
intcompetent said:
Hi,
I'm confused -- is there anyway I can remove it? I've tried looking through TWRP file manager, but whenever I do so, I can't even see /system/ files, and mounting only mounts to USB, but that's unrelated.
Click to expand...
Click to collapse
I don't think SuperSU removes the in-built CM superuser. Use the UNSU zip by osmosis instead. https://forum.xda-developers.com/showthread.php?t=2239421
Also magisk hide will NOT hide Xposed. Yes not even systemless 87.1 Xposed.
SuperSU removed its own root only, CM root is unaffected.
Also, Magisk hide only works with Magisk's own phh root.
And, as far as I know, it can't successfully hide Xposed either. Doesn't matter if it is systemless or not.
Cheers for the replies.
I wasn't aware that Magisk Hide didn't hide Xposed, that's my bad.
As for the presence of CM-SU, SuperSU did do something, as the Developer Options root option is now ADB only while previously it offered the option to Apps too. I'll try unsu.
Here's what I'm meaning btw: imgur.com /a /yTOTw (sorry for the link bypass, there's no other way for me to simply demonstrate the issue) (as you can see in the first screenshot, Magisk detects "cm-su" along with phh. When phh was disabled before I removed cm-su, it only detected cm-su, hence leading me to believe cm-su remains).
e: tried unsu, still cm-su remains. At this point, I'll leave it -- I presume that it's permanently ingrained into the ROM. I've gotten around the restriction I was facing anyway, and I'll adjust. Thanks anyway!
intcompetent said:
Cheers for the replies.
I wasn't aware that Magisk Hide didn't hide Xposed, that's my bad.
As for the presence of CM-SU, SuperSU did do something, as the Developer Options root option is now ADB only while previously it offered the option to Apps too. I'll try unsu.
Here's what I'm meaning btw: imgur.com /a /yTOTw (sorry for the link bypass, there's no other way for me to simply demonstrate the issue) (as you can see in the first screenshot, Magisk detects "cm-su" along with phh. When phh was disabled before I removed cm-su, it only detected cm-su, hence leading me to believe cm-su remains).
e: tried unsu, still cm-su remains. At this point, I'll leave it -- I presume that it's permanently ingrained into the ROM. I've gotten around the restriction I was facing anyway, and I'll adjust. Thanks anyway!
Click to expand...
Click to collapse
If there are SU files in /system/bin and /system/xbin, then CM root was not removed. Not completely.
To actually remove it you have to delete those files.
Pwnycorn said:
If there are SU files in /system/bin and /system/xbin, then CM root was not removed. Not completely.
To actually remove it you have to delete those files.
Click to expand...
Click to collapse
@intcompetent Osmosis's unsu zip removes those files. If those files are still there after flashing the unsu zip, I'd ask in his thread.
knpk13 said:
@intcompetent Osmosis's unsu zip removes those files. If those files are still there after flashing the unsu zip, I'd ask in his thread.
Click to expand...
Click to collapse
Or just remove them manually, jeez. It's just two files.
I've been doing it manually for months and everything works as intended.
As an a closer, there's nothing there. I presume that Magisk is picking up something freaky from somewhere, or something's up, but I'm good guys. I won't need anymore help.
Cheers!
I found this zip around somewhere. I believe it works to remove all root (systemless as well) and I've always flashed it before rooting normally. It should also remove CM root afaik.
As a test, after flashing, check and see if you pass safetynet before installing magisk
intcompetent said:
As an a closer, there's nothing there. I presume that Magisk is picking up something freaky from somewhere, or something's up, but I'm good guys. I won't need anymore help.
Cheers!
Click to expand...
Click to collapse
I
L
Related
Intro
Expose your su to standard location /system/xbin/su systemless-ly.
Though it helps grant root permission to some apps, this trick breaks safetynet.
Just made a simple module try to solve the /sbin/su not detectable problem. This module will look for existing su binary, and create a link as /magisk/su_xbin_bind/system/xbin/su pointing to the real su. The link will also be mounted as /system/xbin/su systemless-ly later.
Installation
Flash it in Magisk manager or through recovery, then reboot. You will find a link /system/xbin/su. All the work is done systemless-ly.
Uninstallation
Open Magisk Manager, go to Modules, disable or uninstall the module called "Su xbin_bind". Then it will disappear after reboot.
su-xbin-bind on github
Changelog
v1.2 20170417
Add Magisk v12 support.
v1.1 20170323
- make it compatible with Magisk v11.5/11.6
Update 20170228
- Since a little syntax error in the mounting script from Magisk v11.0-v11.5, mounting links systemless-ly won't success. Hence we choose to copy but not to link the su binary for v11.0-v11.5. Don't worry, both methods are systemless.
Reserved.
Hi, will this not make safetynet fail?
kartikb said:
Hi, will this not make safetynet fail?
Click to expand...
Click to collapse
It will obviously. Because su is exposed to /system/xbin/su and will be detected.
laggardkernel said:
It will obviously. Because su is exposed to /system/xbin/su and will be detected.
Click to expand...
Click to collapse
Wouldn't magiskhide unmount that and therefore pass safetynet?
I used your module to fix TiBackup freeze when restorins apps.
TiBackup troubleshooting (http://www.titaniumtrack.com/kb/tit...l#tb-hangs-while-freezing-apps-restoring-apps) reports that this issue is connected with wrong su permissions in /system/bin and /system/xbin. Since these are not available due to systemless root, I though that your module would represent an elegant fix... and it did!
Thanks!
leonardus_magnus said:
I used your module to fix TiBackup freeze when restorins apps.
TiBackup troubleshooting (http://www.titaniumtrack.com/kb/tit...#tb-hangs-while-freezing-apps-restoring-apps) reports that this issue is connected with wrong su permissions in /system/bin and /system/xbin. Since these are not available due to systemless root, I though that your module would represent an elegant fix... and it did!
Thanks!
Click to expand...
Click to collapse
Does ur safety net fail with this module?
Xennet said:
Does ur safety net fail with this module?
Click to expand...
Click to collapse
Oh c'mon, you cannot be serious... On Xda forums you have threads with hundreds of pages and I would admit you did not read all of them... but your answer has already been replied on post n. 4 in this page... I can' believe it...
leonardus_magnus said:
Oh c'mon, you cannot be serious... On Xda forums you have threads with hundreds of pages and I would admit you did not read all of them... but your answer has already been replied on post n. 4 in this page... I can' believe it...
Click to expand...
Click to collapse
Yah i saw it lol....
But magisk usually dismounts xbin folder...
Then it unusual to get it detected unless it is physically present der...
So just wanted to confirm it before flashing...
Xennet said:
Yah i saw it lol....
But magisk usually dismounts xbin folder...
Then it unusual to get it detected unless it is physically present der...
So just wanted to confirm it before flashing...
Click to expand...
Click to collapse
Ok safety net not passed on my device... but it's not an issue at all for me...
Unfortunately, doesn't fix the Titanium Backup issue (freezing or restoring app) for me on Galaxy S6 Android 6.0. This also broke SafetyNet for me, even after uninstalling the module from Xposed and rebooted.
chaoscreater said:
Unfortunately, doesn't fix the Titanium Backup issue (freezing or restoring app) for me on Galaxy S6 Android 6.0. This also broke SafetyNet for me, even after uninstalling the module from Xposed and rebooted.
Click to expand...
Click to collapse
If you mean you are using xposed, obviously safetynet will be broken. MagiskHide couldn't hide xposed.
This module tries to fix the su detectable problem. If your titanium backup could get root permission after installing the module, it means the module worked.
My TB is working fine, but I have another app that can't detect it, will give it a test run, thanks for your work!
HI! Just a quick feedback: this module works with Helium Backup that now correctly asks for root permission! :good:
Thank you!
Thanks for the module!! It was the key for me getting Termux su working ?
Hello, I flashed this without error and titanium backup as well as ES file explorer both report I do not have root. Magisk v12 states i do have root.
nevermind...i realized Magisk SU isn't installed as it didn't auto install. I had installed phh's superuser r266-2.
proceeded to rewipe and reflash everything.
Nexus 6P
[ROM][6P][7.1.2_r8]★ Pure Nexus ★ Substratum | Fi | WiFi Calling ★[05/09/17]
ex 4.09
Magisk v13 beta
no issues and all superuser root requests appear.
Big big BIG THANK YOU to you. Fixed the most important app for custom ROMs- Kernel adiutor:highfive: (Both play store:good: and modded versions:laugh and secure settings tasker plugin
Please update the script for the new template v4 for Magisk v13!
:good:
If *enabled* in magisk 13, titanium backup can't get root.
I had to disable it.
Hi,
Work with Magisk Version 13.3 ???
Hello.
Unable to flash magisk modules.
! /data/adb/magisk_merge.img mount failed.
Even via twrp recovery is no possible to flash magisk modules, says something like error 1.
The device is a doogee mix 2.
I was forced to install the normal xposed framework just to use it.
Root works; only modules have problems.
Can some expert find a solution, please?
Thank you in advance to everyone gives good news!
MasterSheea said:
Hello.
Unable to flash magisk modules.
! /data/adb/magisk_merge.img mount failed.
Even via twrp recovery is no possible to flash magisk modules, says something like error 1.
The device is a doogee mix 2.
I was forced to install the normal xposed framework just to use it.
Root works; only modules have problems.
Can some expert find a solution, please?
Thank you in advance to everyone gives good news!
Click to expand...
Click to collapse
Hi, Can you attach logs while flashing ?? from both MM and recovery
MasterSheea said:
Hello.
Unable to flash magisk modules.
! /data/adb/magisk_merge.img mount failed.
Even via twrp recovery is no possible to flash magisk modules, says something like error 1.
The device is a doogee mix 2.
I was forced to install the normal xposed framework just to use it.
Root works; only modules have problems.
Can some expert find a solution, please?
Thank you in advance to everyone gives good news!
Click to expand...
Click to collapse
Known issue on some MTK devices. Loop mounting doesn't work.
There are lots of reports like this for Doogee... There's been some investigating into it in the beta thread, but as of yet there's no solution, I believe.
Hello!
Yes, of course!
Logs of magisk installer and TWRP recovery here:
https://drive.google.com/file/d/11vzWdbQfTtlmdc7VchaKxSGU4RkaOcog/view?usp=drivesdk
Ignore the crittografy error; I have tried to disable the crittografy and all is the same. Same problem.
In more, yesterday I had another annoying problem with magisk: before the options of the magisk app disappeared (there is the pic in the folder I attached. Then magisk is totally disappeared: magisk is not installed anymore in your device.
Tried to re-install magisk: nothing happens.
I have re-flashed the ROM and re- installed magisk: at moment is working.
Root files and SuperSU are not working.
I will open a new forum discussion for this problem.
Thank you in advance.
Greetings
MasterSheea said:
Hello!
Yes, of course!
Logs of magisk installer and TWRP recovery here:
https://drive.google.com/file/d/11vzWdbQfTtlmdc7VchaKxSGU4RkaOcog/view?usp=drivesdk
Ignore the crittografy error; I have tried to disable the crittografy and all is the same. Same problem.
In more, yesterday I had another annoying problem with magisk: before the options of the magisk app disappeared (there is the pic in the folder I attached. Then magisk is totally disappeared: magisk is not installed anymore in your device.
Tried to re-install magisk: nothing happens.
I have re-flashed the ROM and re- installed magisk: at moment is working.
Root files and SuperSU are not working.
I will open a new forum discussion for this problem.
Thank you in advance.
Greetings
Click to expand...
Click to collapse
The file is not accessible
Sorry.
Try now, please.
https://drive.google.com/file/d/11vzWdbQfTtlmdc7VchaKxSGU4RkaOcog/view?usp=drivesdk
MasterSheea said:
Sorry.
Try now, please.
https://drive.google.com/file/d/11vzWdbQfTtlmdc7VchaKxSGU4RkaOcog/view?usp=drivesdk
Click to expand...
Click to collapse
Looks like recovery can't decrypt /data, so that's likely an issue there. But it'd be easier to tell if you had provided the recovery log rather than a screenshot (Advanced - Copy log after trying to flash).
And, it would also be very useful if you had provided a Magisk log rather than only installation logs.
But, it's probably a moot point anyway. Like I said earlier, this is a known issue with loop mounting on Doogee devices (and other devices using Mediatek). No solution as of yet...
Didgeridoohan said:
Looks like recovery can't decrypt /data, so that's likely an issue there. But it'd be easier to tell if you had provided the recovery log rather than a screenshot (Advanced - Copy log after trying to flash).
And, it would also be very useful if you had provided a Magisk log rather than only installation logs.
But, it's probably a moot point anyway. Like I said earlier, this is a known issue with loop mounting on Doogee devices (and other devices using Mediatek). No solution as of yet...
Click to expand...
Click to collapse
Same here, provide good logs
Ok, thanks.
I will try to send you good logs.
About encryption, I have tried to disable encryption and to install all without encryption: nothing changes.
Before I must understand why magisk disappears from system, then I will collect logs about modules installation. Magisk is the only way to root this damned phone, SuperSU does not works.
Thank you in advance
MasterSheea said:
Ok, thanks.
I will try to send you good logs.
About encryption, I have tried to disable encryption and to install all without encryption: nothing changes.
Before I must understand why magisk disappears from system, then I will collect logs about modules installation. Magisk is the only way to root this damned phone, SuperSU does not works.
Thank you in advance
Click to expand...
Click to collapse
There was no need to start a new thread about that... You've already got this one going.
The screenshot of the Manager you provided simply showed a Manager without internet access. Completely normal.
About losing root completely, make sure you don't have any aggressive battery optimisation on the Manager. More here:
https://www.didgeridoohan.com/magisk/Magisk#hn_Randomly_losing_root
Ok, good, I close the other thread
Yes true, that is a normal screenshot of magisk offline. Yesterday I did formatted data to disable encryption and I lost all the other screenshots, but was like this: before all options disappeared, then magisk disappeared.
No, no aggressive battery optimization running, but I have installed greenify and amplify... Perhaps one of this app makes problem?
I wish to close the other thread, but I do not know how to do it.
How to do it, please?
MasterSheea said:
Ok, good, I close the other thread
Yes true, that is a normal screenshot of magisk offline. Yesterday I did formatted data to disable encryption and I lost all the other screenshots, but was like this: before all options disappeared, then magisk disappeared.
No, no aggressive battery optimization running, but I have installed greenify and amplify... Perhaps one of this app makes problem?
Click to expand...
Click to collapse
Make sure the Manager is removed from Battery optimisation and that it isn't selected I'm Greenify. It's not certain that this is the issue, but it's worth ruling out.
Other than that, a logcat of it happening, or even just a screenshot of the Manager when things aren't working. A Magisk log is also useful, of course.
MasterSheea said:
I wish to close the other thread, but I do not know how to do it.
How to do it, please?
Click to expand...
Click to collapse
Just let it be...
Oki.
I removed magisk from battery optimization.
I hope that at least the root will work.
But I seen in another thread that there is a solution known as f2fs workaround bug fixer. But is still not working. I hope that someone will fix it soon.
Anyhow, thank you for all
Move to thread https://forum.xda-developers.com/apps/magisk/guide-magisk-official-version-including-t3577875. Flash last zip. Move to magisk manager, install updated (2018.3.6) version. All modules should now install fine.
Hello.
Thank you for the answer.
I have tried to flash the zip without success.
No magisk installation found or installed version is not supported.
Error process 1.
The magisk version I have installed is v16. - 5.6.4(112).
The last one, suppose.
Any suggestions, please?
Thank you in advance ?
I made also the this attempt: I have flashed a magisk module using flashify.
The flashing was successful, but the module is not in the magisk list.
Can be a permission problem? Someone knows where is the folder of installed magisk modules, please? Perhaps is a permission problem and changing permissions will work...
Download f2fs-loopback-bug-workaround-2018.1.31.zip from the thread. Place it in Download folder of internal storage. Reboot to recovery. Flash zip in twrp. Reboot. Open magisk manager. F2FS Loopback Bug Workaround should be installed in modules. I hope any module can be installed from now on.
Dear Pragnan Saha,
Thank you for your answer.
I have tried to flash f2fs-loopback-bug-workaround-2018.1.31.zip, but without success.
TWRP says: No magisk installation found or installed version is not supported. Error process 1.
Some suggestions, please?
Thank you in advance
Didgeridoohan said:
There was no need to start a new thread about that... You've already got this one going.
The screenshot of the Manager you provided simply showed a Manager without internet access. Completely normal.
About losing root completely, make sure you don't have any aggressive battery optimisation on the Manager. More here:
https://www.didgeridoohan.com/magisk/Magisk#hn_Randomly_losing_root
Click to expand...
Click to collapse
What thread? And is it about exact the same error ! /data/adb/magisk_merge.img ... What this thread is about?
Do you know if there's a fix already? I'm on ext4 so f2fs loopback makes no sense for me
And @MasterSheea do you have a fix?
I've got exactly the same error with flashing modules, after clean flask is possible to install modules but after 1 reboot it fails
Could someone please point me at instructions on how to root LN14.
I've searched the HD/HD+ forums for 'root LN14' and 'rooting LN14' and got no results (which by itself is suspicious).
have you enabled Developer Options?
I, for one, had no luck with either SuperSu or addon su. The first would put the HD+ into a permanent boot loop necessitating a re-install from scratch,and the latter would install but the unit still indicated it was not rooted. Doing the Dev Op made no difference. A real mystery!
harryzee said:
I, for one, had no luck with either SuperSu or addon su. The first would put the HD+ into a permanent boot loop necessitating a re-install from scratch,and the latter would install but the unit still indicated it was not rooted. Doing the Dev Op made no difference. A real mystery!
Click to expand...
Click to collapse
The file addonsu-14.1-arm.zip in the main folder is the one to use. As I seem to recall, you might have to enable, disable, then re-enable, in order for root access to take effect.
digixmax said:
The file addonsu-14.1-arm.zip in the main folder is the one to use. As I seem to recall, you might have to enable, disable, then re-enable, in order for root access to take effect.
Click to expand...
Click to collapse
That is the one I flashed using 3.0.1.0 TWRP. Not clear on your second sentence: "...enable, disable,, then re-enable...". Forgive me for being lost as to what you physically/specifically mean. Please explain.
Thanks.
harryzee said:
That is the one I flashed using 3.0.1.0 TWRP. Not clear on your second sentence: "...enable, disable,, then re-enable...". Forgive me for being lost as to what you physically/specifically mean. Please explain.
Thanks.
Click to expand...
Click to collapse
I meant "enable, disable,, then re-enable" the root access option in "Developer Options".
Aha! Will give it a go. Thanks.
5/2/2018:
Okay: I d/l three android root checkers and titanium backup. The first root checker (Clivin Inc. with small green android robot graphic) told me I was not rooted both before following your above instructions and after. The other two (d/l after following the above) both say I am rooted. However, I was not and am still not able to get "TB" to run. It says "failed" and that I am not rooted.
Since the HD+ is running really well now in its stripped down mode, I can "leave well enough alone" or try to get "TB" working so I can remove anything not needed for my chosen minimal functionality (ereader, viewing videos, photo review/minor editing) that would further reduce unnecessary battery drain.
Thanks again for the above clarification and any additional thoughts.
I am having this same problem
- Root options *do* appear in my Developer settings, but no amount of toggling on/off/on seems to enable root
- I have flashed the Lineage SU addon, log shows successful in TWRP but no change after boot
- SuperSU from Play Store says "SU Binary occupied"
- Adaway says "Rooted Android required- Either the su binary could not be found or you did not allow root permission for Adaway" ie I believe I am indeed *not* rooted.
- SuperSU flashable zip is a broken link on their website.... http://www.supersu.com/download
Out of ideas here, anyone got anything else I can try?
Edit: I was able to obtain Root properly by flashing Magisk & installing the Magisk Manager APK from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
You got it. Use Magisk. Works wonders and way better than SuperSU or any other root permission tool I've came across. It's even akin to, and even has within it, xposed and other magical rooted modules for you to try out for a day or two and then decide you don't need it.
pchc_lx said:
I am having this same problem
- Root options *do* appear in my Developer settings, but no amount of toggling on/off/on seems to enable root
- I have flashed the Lineage SU addon, log shows successful in TWRP but no change after boot
- SuperSU from Play Store says "SU Binary occupied"
- Adaway says "Rooted Android required- Either the su binary could not be found or you did not allow root permission for Adaway" ie I believe I am indeed *not* rooted.
- SuperSU flashable zip is a broken link on their website.... http://www.supersu.com/download
Out of ideas here, anyone got anything else I can try?
Edit: I was able to obtain Root properly by flashing Magisk & installing the Magisk Manager APK from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
I'm new to Magisk, and one thing I'm confused about is the role of the various systemless modules.
1. Essentially, is there anything that I *can't* do normally with Magisk (that I would be able to do if it were rooted any other way) that I *have to* have a module for?
For example, when you have modules to have systemless hosts or systemless Busybox - does that mean that when you use Magisk, you *can't* install or work with these things without those modules, or does it mean that you still could do it normally, but the modules just give you an option to do it without actually modifying anything?
2. If the answer is that I can still do everything normally, but the modules just give me the *option* to do it without actually modifying /system, then why does it matter?
For example, I've never minded having an adblock application actually modify the hosts file when I've rooted in the past before Magisk, so what advantage is there to redirecting them to a fake hosts file? If anything, I would think it increases the chance that something will go wrong or that there will be an incompatibility somewhere along the way.
Everything that Magisk does systemlessly can be done in the old and normal way of modifying system files.
The main advantage for me to use Magisk modules is that all the modifications are still there after a system update (since they'll be in the Magisk image which is kept in /data/adb). I won't have to redo them like I used to before Magisk...
For those that care about updating their device through an OTA, systemless modifications will also make sure that will still work, sort of. You'll still have to keep a stock recovery and restore your stock boot image before updating, but with newer devices that's getting a lot easier. More details here: https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Didgeridoohan said:
Everything that Magisk does systemlessly can be done in the old and normal way of modifying system files.
The main advantage for me to use Magisk modules is that all the modifications are still there after a system update (since they'll be in the Magisk image which is kept in /data/adb). I won't have to redo them like I used to before Magisk...
For those that care about updating their device through an OTA, systemless modifications will also make sure that will still work, sort of. You'll still have to keep a stock recovery and restore your stock boot image before updating, but with newer devices that's getting a lot easier. More details here: https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Click to expand...
Click to collapse
Gotcha! It's not obvious for people new to Magisk whether using a systemless root forces you to do everything in a systemless manner afterwards or not, so I really appreciate your clarifying this.
Haphim said:
Gotcha! It's not obvious for people new to Magisk whether using a systemless root forces you to do everything in a systemless manner afterwards or not, so I really appreciate your clarifying this.
Click to expand...
Click to collapse
No worries. Just want to point out that systemless root isn't Magisk specific. SuperSU and phh's superuser are two examples of root solutions that were systemless long before MagiskSU was a thing...
Hi
I have magisk installed but my phone is reporting not rooted.
My setup:
Xiaomi Redmi Note 7
Ressurection remix
Magisk 23.0
Things I've tried:
Disabled battery optimisation for magisk app
Reinstalled magisk a couple of times from twrp
Other root requiring apps (no change)
I've attached the logs from Root Checker, magisk and snip of my magisk. Please let me know if there is more info I can provide.
Thanks in advance for any suggestions!
re-flashing latest stable magisk.zip with the custom recovery then reboot to system and open the magisk wait to downloading requested resources and see..
Hi
Thanks for your reply.
I just downloaded this and flashed it with twrp: https://magisk.me/
Rebooted and found the same issue. Any other ideas?
Cheers
Oliver
arahknxs said:
Hi
Thanks for your reply.
I just downloaded this and flashed it with twrp: https://magisk.me/
Rebooted and found the same issue. Any other ideas?
Cheers
Oliver
Click to expand...
Click to collapse
1 - Don't use that website. The only place for verified and safe Magisk downloads is on John's Github:
https://github.com/topjohnwu/Magisk
2 - Exactly what is it that's reporting that your device isn't rooted? Because Magisk quite clearly says it is, according to your screenshot...
Didgeridoohan said:
1 - Don't use that website. The only place for verified and safe Magisk downloads is on John's Github:
https://github.com/topjohnwu/Magisk
2 - Exactly what is it that's reporting that your device isn't rooted? Because Magisk quite clearly says it is, according to your screenshot...
Click to expand...
Click to collapse
Hi
Thanks for the reply.
Okay so I went to Git and downloaded this file https://github.com/topjohnwu/Magisk/releases/download/v23.0/Magisk-v23.0.apk I then renamed it to .zip and flashed it via TWRP. Is this correct?
When I reboot I find the same situation. Magisk appears installed correctly however no app can access root. No popup appears to accept/reject the su request and apps behave as if no root access. I've tried Root Checker, Titanium Backup and am happy to try any others.
Do you have any suggestions please on what else I can try?
Cheers
ara
Ah... So the problem is not that you do not have root access The problem is that there's no superuser prompt when an app requests root.
IIRC there's a Xiaomi settings to allow apps to display popup messages (should be under app permissions). The Magisk app also need to be allowed to auto start. Of course, this is for MIUI and you're using RR so I have no idea if there is such a setting on your device currently...
Could of course be something completely different though.
Didgeridoohan said:
Ah... So the problem is not that you do not have root access The problem is that there's no superuser prompt when an app requests root.
IIRC there's a Xiaomi settings to allow apps to display popup messages (should be under app permissions). The Magisk app also need to be allowed to auto start. Of course, this is for MIUI and you're using RR so I have no idea if there is such a setting on your device currently...
Could of course be something completely different though.
Click to expand...
Click to collapse
Yes I suspect this is the issue - the notification is being blocked somehow.
Under app settings -> Magisk, I believe the settings are right:
Battery optimisation = off
Notifications = all allowed
There are plenty of guides out there of using RR with Magisk and no mention of any special settings to make it work.
I am also using nova launcher, I wonder if this could affect the notification somehow?
All suggestions welcome!
Cheers
ara
I noticed in Magisk under the Superuser tab, it just says "no app has asked for superuser permission yet." So perhaps not a notification issue after all?
I downloaded another app, "root checker basic". It also generated no popup, said I do not have root, and nothing appeared in the Magisk logs.
I feel like I am doing something wrong here but missing what it is.
Cheers
ara
arahknxs said:
I noticed in Magisk under the Superuser tab, it just says "no app has asked for superuser permission yet." So perhaps not a notification issue after all?
I downloaded another app, "root checker basic". It also generated no popup, said I do not have root, and nothing appeared in the Magisk logs.
I feel like I am doing something wrong here but missing what it is.
Cheers
ara
Click to expand...
Click to collapse
One thought: make sure that nothing is restricting the Magisk app from autostarting and running in the background.
Also, have you checked with other users of your ROM? Might be a good place to get help for stuff like this...
This happened to me before. I had to rename the same zip to "uninstall.zip" and flash it, reboot, and then rename the zip to something else like Magisk.zip and flash again.
dsiva said:
This happened to me before. I had to rename the same zip to "uninstall.zip" and flash it, reboot, and then rename the zip to something else like Magisk.zip and flash again.
Click to expand...
Click to collapse
Thanks for the suggestion, I tried this but no change afterwards unfortunately.
Also good idea @Didgeridoohan, I will cross post this on the forum for RR.
extract the boot.img and copy to phone. in Magisk, install and pick boot.img. copy the result file to pc, and flash using fastboot flash boot magi....img
if unlocked bootloader, flash direct and reboot.
arahknxs said:
Hi
I have magisk installed but my phone is reporting not rooted.
My setup:
Xiaomi Redmi Note 7
Ressurection remix
Magisk 23.0
Things I've tried:
Disabled battery optimisation for magisk app
Reinstalled magisk a couple of times from twrp
Other root requiring apps (no change)
I've attached the logs from Root Checker, magisk and snip of my magisk. Please let me know if there is more info I can provide.
Thanks in advance for any suggestions!
Click to expand...
Click to collapse
Rename the file to uninstall.zip then flash the firmware then flash the magisk it will work for sure i was also facing the same problem