Database Develop

[MODULE] Nexus Assistant

This is a Magisk module to enable the assistant on existing Nexus devices
Github Repo:
https://github.com/kudiaborm/Nexus-Assistant

How soon? I'd like to try the assistant and I was thinking of doing the build.prop modification, but now that I saw this thread maybe I'll rather wait for this module.
Edit: Sweet module. Love it, worked as expected.

Make sure you're on a Google app version higher than 6.5.35.21. http://www.apkmirror.com/apk/google-inc/google-search/google-search-6-6-14-release/
Magisk Manager doesn't like cache mods so you have to flash in recovery. Make sure you wipe data for Google App after flashing.
This only sets the two build. prop variables. I didn't include any Google app apks or wipe data for Google app. You'll have to do that yourself.

flindaman said:
This is a Magisk module to enable the assistant on existing Nexus devices
Github Repo:
https://github.com/kudiaborm/Nexus-Assistant
Click to expand...
Click to collapse
Just so you're aware replacing the entire build.prop causes issues. It's best to replace the two individual lines. You can use my module as a guide.

loserskater said:
Make sure you're on a Google app version higher than 6.5.35.21. http://www.apkmirror.com/apk/google-inc/google-search/google-search-6-6-14-release/
Magisk Manager doesn't like cache mods so you have to flash in recovery. Make sure you wipe data for Google App after flashing.
This only sets the two build. prop variables. I didn't include any Google app apks or wipe data for Google app. You'll have to do that yourself.
Click to expand...
Click to collapse
Will this be a magisk module still? Can it be undone easily?

loserskater said:
Just so you're aware replacing the entire build.prop causes issues. It's best to replace the two individual lines. You can use my module as a guide.
Click to expand...
Click to collapse
Oddly enough no matter what I tried it didn't work/run properly from the post-fs script. I'll check your module. Maybe it has something to do with file encoding

flindaman said:
Oddly enough no matter what I tried it didn't work/run properly from the post-fs script. I'll check your module. Maybe it has something to do with file encoding
Click to expand...
Click to collapse
I couldn't get his to work. I probably am doing it wrong. But now on tap still shows up.

loserskater said:
Make sure you're on a Google app version higher than 6.5.35.21. http://www.apkmirror.com/apk/google-inc/google-search/google-search-6-6-14-release/
Magisk Manager doesn't like cache mods so you have to flash in recovery. Make sure you wipe data for Google App after flashing.
This only sets the two build. prop variables. I didn't include any Google app apks or wipe data for Google app. You'll have to do that yourself.
Click to expand...
Click to collapse
Flashed in TWRP on Nexus 6, no /cache/magisk was created and neither the properties have changed:
Code:
$ adb shell
shamu:/ $ getprop ro.product.model
Nexus 6
shamu:/ $ getprop ro.opa.eligible_device
shamu:/ $
Did it work on Nexus 6p?

loserskater said:
Make sure you're on a Google app version higher than 6.5.35.21. http://www.apkmirror.com/apk/google-inc/google-search/google-search-6-6-14-release/
Magisk Manager doesn't like cache mods so you have to flash in recovery. Make sure you wipe data for Google App after flashing.
This only sets the two build. prop variables. I didn't include any Google app apks or wipe data for Google app. You'll have to do that yourself.
Click to expand...
Click to collapse
This worked for me, thanks so much. Was wating for a way to do this in magisk
Flashed the file in twrp, rebooted, wiped all google app data, long pressed home and there it was. "ok google" command working great
My setup:
Nexus 6P
Stock NBD90X
Magisk v7
Magisk phh
Magisk V4A

Papote3 said:
This worked for me, thanks so much. Was wating for a way to do this in magisk
Flashed the file in twrp, rebooted, wiped all google app data, long pressed home and there it was. "ok google" command working great
My setup:
Nexus 6P
Stock NBD90X
Magisk v7
Magisk phh
Magisk V4A
Click to expand...
Click to collapse
Are you able to Download+Install modules through the Magisk Manager Downloads section? I'm on NBD90x with Magisk v7, Nexus 6P, Magisk phh, Magisk Manager 2, and I get an error for every module I try to install through the manager. If I could get at the zips and just flash them that would be awesome, but I can't.

shinobi26 said:
Are you able to Download+Install modules through the Magisk Manager Downloads section? I'm on NBD90x with Magisk v7, Nexus 6P, Magisk phh, Magisk Manager 2, and I get an error for every module I try to install through the manager. If I could get at the zips and just flash them that would be awesome, but I can't.
Click to expand...
Click to collapse
Yes I can download, install and reboot from the manager. But this mod needs to be flashed in recovery FYI.
Try and flash them from recovery. There's a folder where magisk manager downloads the zip files. It's in the root of the SD and I think its named magiskmanager

Papote3 said:
Yes I can download, install and reboot from the manager. But this mod needs to be flashed in recovery FYI.
Try and flash them from recovery. There's a folder where magisk manager downloads the zip files. It's in the root of the SD and I think its named magiskmanager
Click to expand...
Click to collapse
Yes, there is. Unfortunately immediately after the zips are downloaded, when the install fails, it removes the zip and I can't get at it. I've gone completely back to full stock NBD90X and installed everything, gone into Magisk Manager and am still unable to install any of the modules from there. It's so frustrating, haha.

shinobi26 said:
Yes, there is. Unfortunately immediately after the zips are downloaded, when the install fails, it removes the zip and I can't get at it. I've gone completely back to full stock NBD90X and installed everything, gone into Magisk Manager and am still unable to install any of the modules from there. It's so frustrating, haha.
Click to expand...
Click to collapse
Does magisk manager have storage permission?

loserskater said:
Does magisk manager have storage permission?
Click to expand...
Click to collapse
It does. It's the only permission in fact.

If there's any Nexus 6 (so far the only arm and not arm64 phone to get Nougat, right?) owner who have this module or any other cache-module working, please post here. I suspect something cache-module related is broken on the arm phone(s).

stangri said:
If there's any Nexus 6 (so far the only arm and not arm64 phone to get Nougat, right?) owner who have this module or any other cache-module working, please post here. I suspect something cache-module related is broken on the arm phone(s).
Click to expand...
Click to collapse
You could try my mod. Instead of replacing the whole buld.prop file it just adds the two properties
Code:
ro.product.model=Pixel
ro.opa.eligible_device=true
to it.
Edit:
Forgot to mention it's still a cache mod so let me know how it works out.
And remember you need to flash it via recovery. Magisk Manager won't install it correctly.
Edit2:
As you can see below, loserskater already posted the same thing in post 3.
So yeah ...

TAM1m said:
You could try my mod. Instead of replacing the whole buld.prop file it just adds the two properties
Code:
ro.product.model=Pixel
ro.opa.eligible_device=true
to it.
Edit:
Forgot to mention it's still a cache mod so let me know how it works out.
And remember you need to flash it via recovery. Magisk Manager won't install it correctly.
Click to expand...
Click to collapse
This is exactly like my module in post 3 of this thread.

loserskater said:
This is exactly like my module in post 3 of this thread.
Click to expand...
Click to collapse
Oh man I didn't see that.. Sorry! Didn't want to take anything from you

TAM1m said:
Oh man I didn't see that.. Sorry! Didn't want to take anything from you
Click to expand...
Click to collapse
No worries, just merely pointing it out.

TAM1m said:
Oh man I didn't see that.. Sorry! Didn't want to take anything from you
Click to expand...
Click to collapse
Thanks for trying to help, but you probably missed this: http://forum.xda-developers.com/showpost.php?p=69088754&postcount=8 too.
Again, if anyone with Nexus 6 (or arm platform in general) got any cache modules working, please let me know.

Magisk (MagiskSU) - Busybox won't install, says "Systemless root is not configured".

Magisk (MagiskSU) - Busybox won't install, says "Systemless root is not configured".
I've installed/flashed the latest stable Magisk version: v13.2. (Since version v13.1 I believe the bundled busybox included with Magisk was removed because it caused a lot of issues)
I've tried to install BusyBox to "/su/xbin" but it always throws up the error "Systemless root is not configured".

bseos said:
I've installed/flashed the latest stable Magisk version: v13.2. (Since version v13.1 I believe the bundled busybox included with Magisk was removed because it caused a lot of issues)
I've tried to install BusyBox to "/su/xbin" but it always throws up the error "Systemless root is not configured".
Click to expand...
Click to collapse
Install Osm0sy's BusyBox zip on twrp (it's a magisk module as well). It works here.
You can find it at his official thread below:
https://forum.xda-developers.com/showthread.php?t=2239421

double_post

abacate123 said:
Install Osm0sy's BusyBox zip on twrp (it's a magisk module as well). It works here.
You can find it at his official thread below:
https://forum.xda-developers.com/showthread.php?t=2239421
Click to expand...
Click to collapse
Tried adding it as a module to Magisk however it reports it's not a magisk module "this zip is not a magisk module".
Flashed it with TWRP and it installed in su/xbin. Thanks :good:

abacate123 said:
Install Osm0sy's BusyBox zip on twrp (it's a magisk module as well). It works here.
You can find it at his official thread below:
https://forum.xda-developers.com/showthread.php?t=2239421
Click to expand...
Click to collapse
I flashed that zip in my Xperia XA and I'm still having the "systemless root is not configured". I need to install busybox in su/bin or su/xbin/ to make Viper4android work. Can u help me?

https://forum.xda-developers.com/android/software-hacking/tool-busybox-flashable-archs-t3348543

aocboe said:
https://forum.xda-developers.com/android/software-hacking/tool-busybox-flashable-archs-t3348543
Click to expand...
Click to collapse
But which do I install?

Evedammo said:
But which do I install?
Click to expand...
Click to collapse
Install "Busybox-1.27.1-YDS-ARM.zip" in the Magisk Manager

aocboe said:
Install "Busybox-1.27.1-YDS-ARM.zip" in the Magisk Manager
Click to expand...
Click to collapse
I've installed that. In the magisk modules it doesn't appear I flashed from TWRP, and I'm still having the "systemless root" message in busybox.

Evedammo said:
I've installed that. In the magisk modules it doesn't appear I flashed from TWRP, and I'm still having the "systemless root" message in busybox.
Click to expand...
Click to collapse
If you want to use it as a Magisk module, maybe you should install it from the Magisk Manager instead of flashing from TWRP.
Besides, I didn't catch your meaning. You mean the busybox app notice? Now that busybox is installed, you don't have to mind that notice.

Why are you guys trying to install to /su? Unless you're still on Magisk v12, you shouldn't be using SuperSU...

Rain X
I'm new, so I can't post links, but a youtuber named Rain X may have a solution. I tried his method and it worked for me:good:

Soumy1234 said:
I'm new, so I can't post links, but a youtuber named Rain X may have a solution. I tried his method and it worked for me:good:
Click to expand...
Click to collapse
What method would that be? No, I'm not gonna go hunting for some random Youtuber...
If the aim is to get a functioning busybox up and running, the easiest way is to just install @osm0sis busybox module from the downloads section in the Manager. No other apps needed...

He installed busybox in system/xbin
He made a folder called "Viper4Android" in the "system/priv-app" folder and copied a Viper4Android APK in there
He set the permissions of said APK to -rw-r--r-- (I set to -rwxrwxrwx for good measure)
He went to "system/vendor/etc" ("system/etc" if it's not there) folder, made a copy of the "audio_effects.conf" file
He renamed the "audio_effects.conf" file in the etc folder to "audio_effects.conf.bak"
He pasted the original "audio_effects.conf" file back in the "etc" folder, so now he has a "audio_effects.conf" and a "audio_effects.conf.bak" file in the "etc" folder
He changed the permissions of the "audio_effects.conf" file to "-rw-r--r--"
He rebooted, opened V4A, installed drivers, then rebooted
Hope this helped.

Didgeridoohan said:
What method would that be? No, I'm not gonna go hunting for some random Youtuber...
If the aim is to get a functioning busybox up and running, the easiest way is to just install @osm0sis busybox module from the downloads section in the Manager. No other apps needed...
Click to expand...
Click to collapse
I tried that,but it didn't work for me. If it doesn't work for you, I've already written some instructions on what the YouTuber did... Hope that helps.

Soumy1234 said:
I tried that,but it didn't work for me. If it doesn't work for you, I've already written some instructions on what the YouTuber did... Hope that helps.
Click to expand...
Click to collapse
That busybox module works perfectly for me.
And I'm using Magisk partly because it makes system modifications like V4A systemless. Therefore I would not follow those instructions...
I do have V4A working though, with this Magisk module and by utilising this workaround until the module has been updated. Nice and systemless...
The above mentioned workaround hasn't worked for everyone, but several other ways of getting it to work have been discussed in that thread.

Didgeridoohan said:
That busybox module works perfectly for me.
And I'm using Magisk partly because it makes system modifications like V4A systemless. Therefore I would not follow those instructions...
I do have V4A working though, with this Magisk module and by utilising this workaround until the module has been updated. Nice and systemless...
The above mentioned workaround hasn't worked for everyone, but several other ways of getting it to work have been discussed in that thread.
Click to expand...
Click to collapse
Oh, okay. Can you at least tell me how much the BusyBox zip work for you? I tried installing it through Magisk and TWRP, but it gave some errors.

Soumy1234 said:
Oh, okay. Can you at least tell me how much the BusyBox zip work for you? I tried installing it through Magisk and TWRP, but it gave some errors.
Click to expand...
Click to collapse
You'll need to provide some details for that... After flashing the module in TWRP, can you save the recovery log (Advanced - Copy log) and attach it to a post here.
And I forgot to say, but for the V4A module I linked, I don't even need busybox installed. YMMV...

Didgeridoohan said:
You'll need to provide some details for that... After flashing the module in TWRP, can you save the recovery log (Advanced - Copy log) and attach it to a post here.
And I forgot to say, but for the V4A module I linked, I don't even need busybox installed. YMMV...
Click to expand...
Click to collapse
Funny. It seemed to work this time. The last time I tried it literally said it failed.

Soumy1234 said:
Funny. It seemed to work this time. The last time I tried it literally said it failed.
Click to expand...
Click to collapse
Doesn't look like it succeeded when looking at the log...
What's the error message when you install through the Manager?

! /data/adb/magisk_merge.img mount failed

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

Magisk appears to be installed but no root

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

Magisk Manager shows "Modules" and "Superuser" grayed out

First, I hope this thread is in the right place and apologize if it is not.
I currently have the problem that the Magisk Manager shows the two categories "Superuser" and "Modules" grayed out at the bottom. In addition, it is also so that the settings of the manager is slimmed down (fewer functions than usual). For this I have 2 screenshots ready: (see attachment and sorry for the German language).
Root itself is still there though (the apps that ask for root still do).
But can imagine that this happened because of the Magisk Hide app. Because I had hid the manager under a different app name, then either accidentally deleted it or restored the original package (can't remember).
In any case, I have already tried to install the manager with an SD card with the TWRP (did not work) and to install Magisk Manager via the apps themselves (pressed install in the first screenshot). This has come the following error message:
Code:
- Target image: /dev/block/
- Device platform: arm64-v8a
- Installing: 24.1 (24100)
! Unable to check signature
! Installation failed
My current status is that this has already happened once with the manager - judging by the bug reports on Github. Can someone please explain me in simple steps how to get this fixed? Thanks!

Bump

JulianKlein said:
Bump
Click to expand...
Click to collapse
No need to bump, your post was only 7 posts down, and only one bump is permitted every 24 hours.
The issue is clear from your screenshots. You don't have root. On the Magisk screen, at the top under the Magisk section, if "Installed" shows "N/A", you do not have working root. Magisk is unable to load modules without root.

V0latyle said:
No need to bump, your post was only 7 posts down, and only one bump is permitted every 24 hours.
The issue is clear from your screenshots. You don't have root. On the Magisk screen, at the top under the Magisk section, if "Installed" shows "N/A", you do not have working root. Magisk is unable to load modules without root.
Click to expand...
Click to collapse
Sorry, didn't know that.
But I don't quite understand. Why should I have no root if apps like Lucky Patcher, Vanced Manager ask for root and I can verify these requests with the manager?

JulianKlein said:
Sorry, didn't know that.
But I don't quite understand. Why should I have no root if apps like Lucky Patcher, Vanced Manager ask for root and I can verify these requests with the manager?
Click to expand...
Click to collapse
I'm not sure. I think you can still manage root permissions if you don't have root but I'm not 100% on that.
I suggest re-rooting with the prescribed method for your device. On the Pixels, we just re-patch and flash the boot image.

i hace the same problem in sm a70, the apps request root acces and i press yes and work but if the same app need request more times for example unloking network , the request are send again and again and again

I just took the leap into Android 12 and we t through the process of patching the boot img and flashing it. I have the same issue as the op. I have patched, repatched, and flashed and reflashed at least 4 or 5 times now. No change.
Edit to note that I do in fact have root, regardless of what Magisk says (installed - N/A). Apps like AdAway have root access and are working properly.

I had the same problem on my (very) old J7 (2015).
Am on android 7, and was trying to update Magisk from v24.3 to v25.1
I had to completely remove Magisk, and restarted from scratch.
Flashed the v25.1 apk in TWRP.

Same problem with Magisk 52.2 on my LineageOS 19.1 (Android 12L) installed on GT-N8000 (Samsung Note 10.1). I already tried re-root, re-flash, re-install apk and nothing!

constrito said:
Same problem with Magisk 52.2 on my LineageOS 19.1 (Android 12L) installed on GT-N8000 (Samsung Note 10.1). I already tried re-root, re-flash, re-install apk and nothing!
Click to expand...
Click to collapse
Do you originally have magisk hidden as another app then install mm anew?

Nergal di Cuthah said:
Do you originally have magisk hidden as another app then install mm anew?
Click to expand...
Click to collapse
I'm not sure about it, but I tried a few versions of Magisk and none worked. I installed both boot.img and magisk.apk via TWRP. The app downloaded and installed by Android always forces an upgrade.

constrito said:
The app downloaded and installed by Android always forces an upgrade.
Click to expand...
Click to collapse
That's because you haveca newer boot than the magisk manager.
Let it upgrade
Then tap the uninstall button
Restore images
Then complete uninstall
Reboot
Install magisk
Reroot

Nergal di Cuthah said:
That's because you haveca newer boot than the magisk manager.
Let it upgrade
Then tap the uninstall button
Restore images
Then complete uninstall
Reboot
Install magisk
Reroot
Click to expand...
Click to collapse

I don't have an uninstall button. I put a print screen in the previous post.

Did you mean to post something if so you didn't
Not sure what to say about no uninstall but i guarantee that you have a double install. Look through your apps. Did you ever hide magisk with a different name, you've got to remember that at some time you did.

Nergal di Cuthah said:
Did you mean to post something if so you didn't
Click to expand...
Click to collapse
Sorry if there was some confusion, here is: https://forum.xda-developers.com/t/...nd-superuser-grayed-out.4409627/post-88379373.

constrito said:
Sorry if there was some confusion, here is: https://forum.xda-developers.com/t/...nd-superuser-grayed-out.4409627/post-88379373.
Click to expand...
Click to collapse
See my edit

Nergal di Cuthah said:
Did you mean to post something if so you didn't
Not sure what to say about no uninstall but i guarantee that you have a double install. Look through your apps. Did you ever hide magisk with a different name, you've got to remember that at some time you did.
Click to expand...
Click to collapse
I removed the Magisk via TWRP by flashing it with the uninstall.zip file. After installing the Magisk via flash with the Magisk.zip file and rebooting the tablet, I patched my boot.img, went back to TWRP, flashed the boot.img selecting the boot option and rebooted. I went back to the Magisk app and the same problem. I checked via
Code:
adb shell pm list packages | grep magisk
and it returns only
Code:
package:com.topjohnwu.magisk
it suggests I have only 1 app installed (none hidden).

Then I'm out of ideas sorry

Nergal di Cuthah said:
Then I'm out of ideas sorry
Click to expand...
Click to collapse
No problem and thank you.