Database Develop

[Q]Lollipop - Viper4Android

Hello.
So I installed a custom recovery, flashed lollipop fw and installed supersu.
Today I was trying to install Viper4Android but, unfortunately, it does not work.
I also installed the drm restore patch (audio clear + is working).
Is there any fix ? Is Viper working for someone here?
Thanks in advance.

Interested too, have a z3c too and have found a few threads describing the installation in 2 steps, flashing via recovery and installing an .apk but nothing specific for z3c.
will update this thread once I have a full nandroid backup and am ready to play around.

I was in the same situation as you guys and couldn't live without V4A.
You/we forgot 1 step
You need to set SELinux mode to permissive and then install V4A driver:
Use this simple app:
https://play.google.com/store/apps/details?id=com.mrbimc.selinux

Amy more advice? Tried that, then set it back, yet viper doesn't seem to be getting used although the driver is installed, where do I select viper as the processor for audio?

ovizii said:
Amy more advice? Tried that, then set it back, yet viper doesn't seem to be getting used although the driver is installed, where do I select viper as the processor for audio?
Click to expand...
Click to collapse
You don't, I was also looking for that for a while, but PowerAmp picks that up automatically and so I guess the entire OS
Sent from my D5803 using XDA Free mobile app

Dsteppa said:
I was in the same situation as you guys and couldn't live without V4A.
You/we forgot 1 step
You need to set SELinux mode to permissive and then install V4A driver:
Use this simple app:
https://play.google.com/store/apps/details?id=com.mrbimc.selinux
Click to expand...
Click to collapse
any idea what happened that google play store link is no longer valid? shall I chose another one or restore from backup?

ovizii said:
any idea what happened that google play store link is no longer valid? shall I chose another one or restore from backup?
Click to expand...
Click to collapse
Nope, seems like they removed it from the store

I've had a backup with TItaniumBackup but I was just curious what happened there...

Did as Dsteppa sayed. Worked for 10 sec. closed music app and viper and start again. Same thing. Btw I have force enable V4A. Then i went to viper settings and changed FX compatible mode to compatible and restart phone. Works perfectly! Thanks so much!

The solution is disable or froze "Sound Enhancement" app, and that's all, V4A is going to work fine without need of change the option to "Compatible Mode".

iFlasher said:
The solution is disable or froze "Sound Enhancement" app, and that's all, V4A is going to work fine without need of change the option to "Compatible Mode".
Click to expand...
Click to collapse
Thank i try now
MrPingle

Also make sure that Equalizer (in settings, not Viper) is set to Off mode.

I try to install V4A (through Apk) but when i install the drivers, a message says: "Driver install failed: the busybox installation on you device does not work... etc."
I have just installed the last version of busybox in /system/xbin and set Selinux permissive.
How can i resolve it?
I get root with Kingroot e after change binaries to Supersu's binaries.

How to install Viper4android Fx on Moto X Android 6

Hi guys, I could not run Viper4android application on my device (android 6) . I haved installed apk then install driver . But Not thing change in sound effect. I tried to search and did not find out any error?
I need some help to run app with effect sound when play music!
Thank inadvance!

Well mine has problem of installing the sound driver.
通过我的 XT1096 上的 Tapatalk发言

duongnv1996 said:
Hi guys, I could not run Viper4android application on my device (android 6) . I haved installed apk then install driver . But Not thing change in sound effect. I tried to search and did not find out any error?
I need some help to run app with effect sound when play music!
Thank inadvance!
Click to expand...
Click to collapse
How did you install the viper4android via apk or you flashed from recovery?

duongnv1996 said:
Hi guys, I could not run Viper4android application on my device (android 6) . I haved installed apk then install driver . But Not thing change in sound effect. I tried to search and did not find out any error?
I need some help to run app with effect sound when play music!
Thank inadvance!
Click to expand...
Click to collapse
In order to install ViPER4Android, you'll need your system to be properly rooted, BusyBox must be installed, and SELinux Mode must be "Permissive".
I recommend this BusyBox installer, and you can get SELinux Mode Changer from here.
Then, after everything is properly set up, you must also disable your ROM (e.g. CyanogenMod-based ROMs' AudioFX)and/or player (e.g. Poweramp's equalizer)'s built-in equalizer, and switch ViPER4Android's FX Compatible mode from "Normal" to "Compatible".

duongnv1996 said:
Hi guys, I could not run Viper4android application on my device (android 6) . I haved installed apk then install driver . But Not thing change in sound effect. I tried to search and did not find out any error?
I need some help to run app with effect sound when play music!
Thank inadvance!
Click to expand...
Click to collapse
I was able to make V4A work on my Moto X 2014 with a fix.
If you do not have Busybox or permissive SELinux, follow the instructions our mate's posted above:
KazuhiroYasei said:
In order to install ViPER4Android, you'll need your system to be properly rooted, BusyBox must be installed, and SELinux Mode must be "Permissive".
I recommend this BusyBox installer, and you can get SELinux Mode Changer from here.
Then, after everything is properly set up, you must also disable your ROM (e.g. CyanogenMod-based ROMs' AudioFX)and/or player (e.g. Poweramp's equalizer)'s built-in equalizer, and switch ViPER4Android's FX Compatible mode from "Normal" to "Compatible".
Click to expand...
Click to collapse
After Busybox installed and SELinux on permissive, you flash the Viper zip and install the driver. Right after that you open a root enabled file manager and find system>vendor>etc. You'll see an audio_effects.conf.
(I suggest making a safe copy of this file).
Rename the original audio_effects.conf to audio_effects.bak.
Save and reboot. Now try using v4a again.

brunoperissotti said:
I was able to make V4A work on my Moto X 2014 with a fix.
After Busybox installed and SELinux on permissive, you flash the Viper zip and install the driver. Right after that you open a root enabled file manager and find system>vendor>etc. You'll see an audio_effects.conf.
(I suggest making a safe copy of this file).
Rename the original audio_effects.conf to audio_effects.bak.
Save and reboot. Now try using v4a again.
Click to expand...
Click to collapse
Was this procedure required for V4A to work on your Victara? Mine worked in every ROM I tested (all Marshmallow-based) by following the steps you quoted.

KazuhiroYasei said:
Was this procedure required for V4A to work on your Victara? Mine worked in every ROM I tested (all Marshmallow-based) by following the steps you quoted.
Click to expand...
Click to collapse
Yes. I was only able to enjoy v4a after this procedure.

It's worth pointing out that V4A is going to F up your Moto Voice

Popping into this thread real quick to provide some info,
Using compatibility mode with V4A is bad news, causes extra battery drain and problems with some apps.
For every single rom and device I've used 5.0+ I've followed the same procedure to install V4A, without using compatibility mode, without having to delete a file every time, etc.
Flash the "lolliviper" zip attached to this OP.
Followed by the "Build.Prop-Tweaks" and "Soundfix-LibFiles" attached to this post.
You'll also need a way of setting selinux to permissive after every boot if you're using CM or something else with selinux set to enforced. Something like SELinuxModeChanger available here will work.
If you don't have busybox installed, V4A will tell you and help you install it.
The V4A version included in the "lolliviper" zip is not the newest , you'll need to "Check Update" via the 3 dot menu and install the latest apk.
After all this, install the driver via the V4A app, reboot, and you're golden.

Flipz77 said:
It's worth pointing out that V4A is going to F up your Moto Voice
Click to expand...
Click to collapse
Didn't know that. I was only able to set v4a on a custom ROM, so that ship was long gone hahaha
it just stops working?

brunoperissotti said:
Didn't know that. I was only able to set v4a on a custom ROM, so that ship was long gone hahaha
it just stops working?
Click to expand...
Click to collapse
Actually it still "works" because it detects your launch phrase, but after that, half of the time it just hangs without hearing your command. Sometimes it'll randomly work, but it was too much of a botch to keep it that way. I've now resorted to Noozxoide Pro: it's still a system-wide mod with modes for headset, speaker and BT, but it's installed as a "standard" app, it doesn't mess with your system and it sounds boss!

I ran across this link on a similar search on the google machine, and it made V4A installation a breeze. No manual messing with kernel settings and whatnot: http://forum.xda-developers.com/android/software/viperaudio-viperatmos-3-8-sq-driver-t3289075
Battery life has been fine running this for about a week. I don't use Moto Voice so can't comment on that.

THANKS
brunoperissotti said:
I was able to make V4A work on my Moto X 2014 with a fix.
If you do not have Busybox or permissive SELinux, follow the instructions our mate's posted above:
After Busybox installed and SELinux on permissive, you flash the Viper zip and install the driver. Right after that you open a root enabled file manager and find system>vendor>etc. You'll see an audio_effects.conf.
(I suggest making a safe copy of this file).
Rename the original audio_effects.conf to audio_effects.bak.
Save and reboot. Now try using v4a again.
Click to expand...
Click to collapse
Thanks a lot, I was already discouraged, tried several versions of viper, on diferent roms, this was the only solution, but is necessary to remember that for this file to appear in the folder, you need to open the application and save a profile, even if empty, without it you can not find the file audio_effects

If u root ur device using magisk, u can install viper magisk module...it works fine on android 6.0 with selinux enforcing..
Sent from a Motobot

Viper4Arise Install Guide

Hi everyone, I was wondering if there is a composite install guide for Oneplus 3T devices for all ROM's for Viper4Arise. I really love that Mod. I am currently on RR 5.3.8 and I find that the installation via Magisk is very buggy and leads to FC almost all apps and the phone freezes after a few minutes of installation. I had no such issues installing Viper4Android though. I am a noob so find the current install method on the thread very complicated. Is there a zip file which makes it easier regardless of ROM or if there is anything specific to RR roms which can be used?

Don't know of any such guide, but it's a good idea to have one (although the request for a guide "for all ROMs" may be a tall order).
I was reading through the following sounds mods thread yesterday, and it was confusing as heck, and seems like some folks have varying results: https://forum.xda-developers.com/oneplus-3t/help/best-sound-mods-t3555160
I can't speak to RR, but what I can say, is that I easily installed ARISE on stock rooted ROM (rooted with SuperSU) with one of the AROMA versions; and ARISE works flawlessly. Did not need SELinux permissive or Busybox. I also skipped all of the options in the AROMA installer, since honestly, I don't know what most of them are, and they aren't critical for the "core" ARISE experience.

Happy to report that I was able to fix this. What I did was a little bit of sacrifice but I think I care about sound quality on my phone more than anything else. What I did was replace magisksu with supersu. While the convenience of magisk would be missed, I am happy that now I have arise numbers Module with dolby atmos installed. :good:

cluttered_butter said:
Happy to report that I was able to fix this. What I did was a little bit of sacrifice but I think I care about sound quality on my phone more than anything else. What I did was replace magisksu with supersu. While the convenience of magisk would be missed, I am happy that now I have arise numbers Module with dolby atmos installed. :good:
Click to expand...
Click to collapse
Did you just flash supersu over magisk or was the installation more involved? I was thinking of testing this but wasn't sure if it would work. My plan currently is:
1) Remove all magisk modules
2) Flash SuperSU from Recovery and reboot
3) Reapply magisk modules (V4A Included)
4) Reboot
Was this essentially all you did on your end?

I have tried what you are about to embark on since if I had it my way, I would stick to magisk. Here's what I did, I rooted my phone with SuperSU after uninstalling magisk completely (remove all modules and uninstall using the magisk uninstall zip), I downloaded the magisk manager and tried to rely on the supersu for root access. Magisk did say the phone was rooted after seeking rights from supersu, but eventually just hung the system. Post which it was kind of futile coz it just won't work. If you flash the magisk zip you will cause bigger issues since supersu and magisk would conflict for libraries and that's not good either.
Feel free to try it anyway and see if you get somewhere. Take a backup of course:fingers-crossed:

For me arise works flawless on rr with magisk. And i didnt need any magisk module or extra zip. Only flashed simple modular installer.

cluttered_butter said:
If you flash the magisk zip you will cause bigger issues since supersu and magisk would conflict for libraries and that's not good either.
Click to expand...
Click to collapse
I just wanted to chime in and say that this information isn't correct. Magisk has been designed to work with SuperSU (systemless) as well as MagiskSU.

Instructions
nadejo said:
For me arise works flawless on rr with magisk. And i didnt need any magisk module or extra zip. Only flashed simple modular installer.
Click to expand...
Click to collapse
Can you share the link for installer or instructions for the specific arise installation you did? It'll help me try the same.

Didgeridoohan said:
I just wanted to chime in and say that this information isn't correct. Magisk has been designed to work with SuperSU (systemless) as well as MagiskSU.
Click to expand...
Click to collapse
Was just sharing my experience. Didn't mean to say that my information was correct.

cluttered_butter said:
Can you share the link for installer or instructions for the specific arise installation you did? It'll help me try the same.
Click to expand...
Click to collapse
1.First put this (my custom prop with dolby atmos and viper arise you can further customize it if you want)
https://drive.google.com/open?id=0B5cs9MEMO2MrNGo3eGJJVFdxemc
On sd card (dont rename it and dont put it in any folder) it must be at same place where all your folders are. Like downloads... Pictures...
2.Then go to rr settings and switch to selinux permissive
3.Now flash this file in twrp https://www.androidfilehost.com/?fid=529152257862724645
And reboot.
Have fun

Will give it a shot tonight! Thank you so much!

So this isn't for V4ARISE but rather for the Viper4Android module in Magisk (still using MagiskSU). I was able to get Viper4Android in Magisk to work without setting SE_Linux to permissive or doing anything crazy. My steps were below:
1) Install Magisk
2) Enable Magisk BusyBox
3) Install the Viper4Android module
4) Install the Viper4Android APK
5) Reboot the phone
6) Copy the audio_effects.conf file from:
\ROOT\MAGISK\V4A\SYSTEM\ETC\audio_effects.conf
to
\ROOT\MAGISK\V4A\SYSTEM\VENDOR\ETC\audio_effects.conf
7) Reboot
8) Test...Successful!
Step 5 was probably not needed but I took it as an extra measure. I can't remember the thread that I read step 6 at but immediately after doing that and rebooting my module was working.

Worked like a charm ??thanks so much. Don't know what I was doing wrong all this time

trentonite said:
So this isn't for V4ARISE but rather for the Viper4Android module in Magisk (still using MagiskSU). I was able to get Viper4Android in Magisk to work without setting SE_Linux to permissive or doing anything crazy. My steps were below:
1) Install Magisk
2) Enable Magisk BusyBox
3) Install the Viper4Android module
4) Install the Viper4Android APK
5) Reboot the phone
6) Copy the audio_effects.conf file from:
\ROOT\MAGISK\V4A\SYSTEM\ETC\audio_effects.conf
to
\ROOT\MAGISK\V4A\SYSTEM\VENDOR\ETC\audio_effects.conf
7) Reboot
8) Test...Successful!
Step 5 was probably not needed but I took it as an extra measure. I can't remember the thread that I read step 6 at but immediately after doing that and rebooting my module was working.
Click to expand...
Click to collapse
I have tried Viper4Android but I think Viper4Arise+Dolby is way better. The sound through the speakers is so much louder and with a lot of clarity. If you have a good pair of headphones then its just audio nirvana. Just a personal preference I guess.
Are you using any IRS/Profiles which have worked well for you? Do let me

trentonite said:
So this isn't for V4ARISE but rather for the Viper4Android module in Magisk (still using MagiskSU). I was able to get Viper4Android in Magisk to work without setting SE_Linux to permissive or doing anything crazy. My steps were below:
1) Install Magisk
2) Enable Magisk BusyBox
3) Install the Viper4Android module
4) Install the Viper4Android APK
5) Reboot the phone
6) Copy the audio_effects.conf file from:
\ROOT\MAGISK\V4A\SYSTEM\ETC\audio_effects.conf
to
\ROOT\MAGISK\V4A\SYSTEM\VENDOR\ETC\audio_effects.conf
7) Reboot
8) Test...Successful!
Step 5 was probably not needed but I took it as an extra measure. I can't remember the thread that I read step 6 at but immediately after doing that and rebooting my module was working.
Click to expand...
Click to collapse
I have tried Viper4Android but I think Viper4Arise+Dolby is way better. The sound through the speakers is so much louder and with a lot of clarity. If you have a good pair of headphones then its just audio nirvana. Just a personal preference I guess.
Are you using any IRS/Profiles which have worked well for you? Do let me know

cluttered_butter said:
I have tried Viper4Android but I think Viper4Arise+Dolby is way better. The sound through the speakers is so much louder and with a lot of clarity. If you have a good pair of headphones then its just audio nirvana. Just a personal preference I guess.
Are you using any IRS/Profiles which have worked well for you? Do let me know
Click to expand...
Click to collapse
For my IRS profile I'm using DTS Mode Z128k. I had tried dolby pro logic 2/3 but the way it boosted the volume was just too much. DTS Mode has worked out well so far. What about you?

trentonite said:
For my IRS profile I'm using DTS Mode Z128k. I had tried dolby pro logic 2/3 but the way it boosted the volume was just too much. DTS Mode has worked out well so far. What about you?
Click to expand...
Click to collapse
I typically stick to dolby irs. But the main difference in sound is made by the profiles in viper4arise. I love the Audiophile X profile. Amazing fidelity on rock songs.

trentonite said:
So this isn't for V4ARISE but rather for the Viper4Android module in Magisk (still using MagiskSU). I was able to get Viper4Android in Magisk to work without setting SE_Linux to permissive or doing anything crazy. My steps were below:
1) Install Magisk
2) Enable Magisk BusyBox
3) Install the Viper4Android module
4) Install the Viper4Android APK
5) Reboot the phone
6) Copy the audio_effects.conf file from:
\ROOT\MAGISK\V4A\SYSTEM\ETC\audio_effects.conf
to
\ROOT\MAGISK\V4A\SYSTEM\VENDOR\ETC\audio_effects.conf
7) Reboot
8) Test...Successful!
Step 5 was probably not needed but I took it as an extra measure. I can't remember the thread that I read step 6 at but immediately after doing that and rebooting my module was working.
Click to expand...
Click to collapse
Is it possible to flash after the procedure above -Viper4Arise?

Hi guys, I just bought my 3T, rooted and installed TWRP. Now I`m trying to install V4Arise, but with no success. I tried Freedom ROM... In this ROM V4Arise works fine, but the cell battery drains too fast. I returned to stock ROM... But I dont know how to install V4Arise in stock ROM. Could you help me?

Rooting LN14????

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

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