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.
Related
Deprecated - Use the New ViPER4Android v2.7:
GO TO THE THREAD LINKED ABOVE. You don't need to flash any zips. Just install it as a regular apk, allow it to install the drivers, and you're good to go.
For magisk users: I made a zip on the repo that includes the original vdc's and my profile converter (will convert your old profiles to the new and better format).
For rootless users: I made a zip to install drivers and such
Zips can be found here
ALL SUPPORT QUESTIONS FOR 2.7 SHOULD BE AT THE THREAD ABOVE.
This is ViPER4Android FX and Xhifi Unity installers
These installers utilize my Unified installer that can install on Magisk OR System if Magisk is not detected (with Pixel support).
Credits of Originality:
- @zhuhang (Official Thread)
- @Osm0sis
- Viper's Audio (Official blog)
- @ViPER520
- @Team_DeWitt
Special Instructions:
If you already know which original v4a you want to use, just add 'old' for 2.3.4.0, 'mid' for 2.4.0.1, 'new' for 2.5.0.5, or 'mat' for material to the zipname prior to flashing.
If you already know if you want it installed as a user or system app, add "uapp" for user app or "sapp" to system app to zipname.
If you already know if you want to apply the libstdc++.so lib workaround, add "lib" or "nlib" to zipname (note that there are some devices that are already known to require it and so they'll apply workaround regardless of choice)
If you already know if your device/rom requires the v4a open/close/fc audioserver workaround, add "ocw" to zipname. Otherwise, add "nocw" to zipname
To skip volkeys (if your device isn't compatible with them), add "novk" to the zipname. Note that if you don't specify the above, defaults will be applied which are: sapp, new
Make sure there are no spaces in the zipname
Audio Mod Troubleshooting Guide
Downloads
XDA:DevDB Information
ViPER4Android FX Legacy/XHiFI [Unity], App for the XDA Community Apps
Contributors
ahrion, Zackptg5
Version Information
Status: Stable
Current Stable Version: v4.4
Stable Release Date: 2019-08-11
Created 2019-01-18
Last Updated 2020-01-01
great!
Hi, tried your two modules you've posted on my Nexus 6P stock ROM. March update. Both causing bootloop and using the uninstaller provided doesn't help. Have to use mount Magisk then go to file explorer in TWRP recovery and delete the modules from Magisk folder.
kartikb said:
Hi, tried your two modules you've posted on my Nexus 6P stock ROM. March update. Both causing bootloop and using the uninstaller provided doesn't help. Have to use mount Magisk then go to file explorer in TWRP recovery and delete the modules from Magisk folder.
Click to expand...
Click to collapse
Hmm. This is probably a kernel or magisk limitation with your rom. Are you running 11.6? Try to run it without the deep_buffer Remover because this is probably what bootloops your phone. It's only necessary when you've NEED it, otherwise it may cause adverse effects. Just install V4A and see if it works.
Currently magisk still has limited boot.img compatibility which causes so.e mods to not work properly or bootloops when it's not the mod itself.
ahrion said:
Hmm. This is probably a kernel or magisk limitation with your rom. Are you running 11.6? Try to run it without the deep_buffer Remover because this is probably what bootloops your phone. It's only necessary when you've NEED it, otherwise it may cause adverse effects. Just install V4A and see if it works.
Currently magisk still has limited boot.img compatibility which causes so.e mods to not work properly or bootloops when it's not the mod itself.
Click to expand...
Click to collapse
Hi, I'm on 11.6. I've tried both modules on their own and they both have caused boot loops unfortunately.
Thanks anyway..
kartikb said:
Hi, I'm on 11.6. I've tried both modules on their own and they both have caused boot loops unfortunately.
Thanks anyway..
Click to expand...
Click to collapse
Magisk limitation. @topjohnwu is always improving magisk. I do recommend may e trying another kernel for your device which may help compatibility.
Gave this module a go, and: it's a no go... Will not boot on my Nexus 6 running Vanilla ROM 7.1.1_r26, Franco Kernel r65 and Magisk v.11.6 - MagiskSU.
After flashing uninstaller the device still doesn't boot. Had to manually remove audmodlib from /magisk in TWRP to make it boot again. And it's in audmodlib the problem is. I did a quick test where I removed audmodlib after installation (kept v4afx in place) and it booted right up (with a non-functioning module, obviously).
Attaching installation and uninstallation recovery logs. Unfortunately I'm not at a computer with ADB, otherwise I would have captured a logcat of boot for you. Maybe later...
Didgeridoohan said:
Gave this module a go, and: it's a no go... Will not boot on my Nexus 6 running Vanilla ROM 7.1.1_r26, Franco Kernel r65 and Magisk v.11.6 - MagiskSU.
After flashing uninstaller the device still doesn't boot. Had to manually remove audmodlib from /magisk in TWRP to make it boot again. And it's in audmodlib the problem is. I did a quick test where I removed audmodlib after installation (kept v4afx in place) and it booted right up (with a non-functioning module, obviously).
Attaching installation and uninstallation recovery logs. Unfortunately I'm not at a computer with ADB, otherwise I would have captured a logcat of boot for you. Maybe later...
Click to expand...
Click to collapse
The only real thing in audmodlib is could be is service.sh or system.prop otherwise it would be the vendor file, which would mean that for some reason 11.6 is bugged for vendor file mounting. Try installing and remove those ONLY and and see if it fixes it.
If that fixes it then it's one of those two. And if you're cool can you see which one it is exactly.
ahrion said:
The only real thing in audmodlib is could be is service.sh or system.prop otherwise it would be the vendor file, which would mean that for some reason 11.6 is bugged for vendor file mounting. Try installing and remove those ONLY and and see if it fixes it.
If that fixes it then it's one of those two. And if you're cool can you see which one it is exactly.
Click to expand...
Click to collapse
There has been an issue with vendor mounting in Magisk, but I believe that was for devices with separate vendor partitions (Nexus 6P, Nexus 5X, etc). I haven't seen any commits on GitHub about it though (although I haven't been keeping that close attention), so I don't know if it's been fixed.
I did find the culprit though: it's system.prop. With that file removed from /magisk/audmodlib my device booted up just fine.
kartikb said:
Hi, I'm on 11.6. I've tried both modules on their own and they both have caused boot loops unfortunately.
Thanks anyway..
Click to expand...
Click to collapse
If you wanna try this is my module for Nexus phones. I use this in my Nexus 5X Stock and PureNexus
https://www.androidfilehost.com/?fid=529152257862713260
Sry ahrion for use your thread
Seyaru said:
If you wanna try this is my module for Nexus phones. I use this in my Nexus 5X Stock and PureNexus
https://www.androidfilehost.com/?fid=529152257862713260
Sry ahrion for use your thread
Click to expand...
Click to collapse
You are literally advertising your mods in everyone's threads. Stop this and make your own thread.
This is a magisk forum, not a system mod forum.
Didgeridoohan said:
There has been an issue with vendor mounting in Magisk, but I believe that was for devices with separate vendor partitions (Nexus 6P, Nexus 5X, etc). I haven't seen any commits on GitHub about it though (although I haven't been keeping that close attention), so I don't know if it's been fixed.
I did find the culprit though: it's system.prop. With that file removed from /magisk/audmodlib my device booted up just fine.
Click to expand...
Click to collapse
I will remove it with next release. Thank you man. This **** only started happening with 11.6. this was the reason Atmos was boot looping as well so I removed system.prop in Atmos.
Can you do me a favor and remove a few lines to see if it's just the specific lines? I think that certain lines don't play nice with your phone.
Remove the first part, low power audio tweaks, reboot and see if it works. If it doesn't then that's the culprit. If not then remove the first two on the other audio tweaks.
Seyaru said:
If you wanna try this is my module for Nexus phones. I use this in my Nexus 5X Stock and PureNexus
https://www.androidfilehost.com/?fid=529152257862713260
Sry ahrion for use your thread
Click to expand...
Click to collapse
Hi there, thanks for the suggestion. I've tried it already and it didn't work. Asked for drivers to be installed when I opened the app after installing the module and restarting the phone.
kartikb said:
Hi there, thanks for the suggestion. I've tried it already and it didn't work. Asked for drivers to be installed when I opened the app after installing the module and restarting the phone.
Click to expand...
Click to collapse
Enable permissive.
Turn off audiofx
ahrion said:
Enable permissive.
Turn off audiofx
Click to expand...
Click to collapse
I'll try again when I get a chance to. Thanks for the suggestion.
[UPDATED] ViPER4Android FX <2.5.0.5>
v1.1:
- Updated to Audio Modification Library (Magisk) v1.1
This should fix the boot loop issues seen in only Magisk v11.6
Download: Link - Mirror
Previous Changelogs (Unified installer):
HTML:
V1.0:
- Initial release
- Smali edits to automatically enable storage permissions
- Audio Modification Library v1.0 is included
- Unified installer that will install mod for both Magisk and System
- Pixel support included
- Magisk Template v3 support
kartikb said:
Hi, I'm on 11.6. I've tried both modules on their own and they both have caused boot loops unfortunately.
Thanks anyway..
Click to expand...
Click to collapse
Didgeridoohan said:
There has been an issue with vendor mounting in Magisk, but I believe that was for devices with separate vendor partitions (Nexus 6P, Nexus 5X, etc). I haven't seen any commits on GitHub about it though (although I haven't been keeping that close attention), so I don't know if it's been fixed.
I did find the culprit though: it's system.prop. With that file removed from /magisk/audmodlib my device booted up just fine.
Click to expand...
Click to collapse
Try 1.1.
ahrion said:
Try 1.1.
Click to expand...
Click to collapse
Thanks, I'll give it another go and report back.
Update: my phone reboots into Android fine now however it doesn't process audio on phone speaker.
kartikb said:
Thanks, I'll give it another go and report back.
Update: my phone reboots into Android fine now however it doesn't process audio on phone speaker.
Click to expand...
Click to collapse
Flash my deep buffer remover. Look in the magisk forum.
ahrion said:
Flash my deep buffer remover. Look in the magisk forum.
Click to expand...
Click to collapse
Thanks, it all finally works on my Nexus 6P. Now to try on my OnePlus 3..
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?
Here I got a very simple fix
Go find a root explorer
Go to /magisk
Check every module.prop in every module
Make sure at the end it have an extra empty line. If not, change it .
Lunch app again . Everything should be fine now.....
It seems to be the mistake maked by some module's dev
I can't install any module ?, already tried to flash module with magisk manager and twrp, still not success..
raymondsanusi said:
I can't install any module , already tried to flash module with magisk manager and twrp, still not success..
Click to expand...
Click to collapse
You dont flash modules... You go to the modules section of magisk manager, and hit the + sign. Then it will open a file manager, you simply just tap and hold on the zip file containing the module, and hit open in the top right. Your module will then be installed and a simple reboot will activate it. Flashing with twrp does nothing lol
That fix worked great.
Thanks!
( If it is not clear: you can find /magsik in your root folder, you need a root filemanager)
Thanks, it worked, adfree youtube module had a missing blank line
https://forum.xda-developers.com/apps/magisk/module-adfree-youtube-template-t3532753
TCUofficial said:
You dont flash modules... You go to the modules section of magisk manager, and hit the + sign. Then it will open a file manager, you simply just tap and hold on the zip file containing the module, and hit open in the top right. Your module will then be installed and a simple reboot will activate it. Flashing with twrp does nothing lol
Click to expand...
Click to collapse
you sure about that? I've been flashing my modules through TWRP and after booting up I can see them in MagiskManager
Unified Hosts Adblock and Universal Deep Buffer Removal doesn't have that blank line. By fixing them, now I'm able to use Magisk Manager 5.1.0 . Thank you.
Sent from my bullhead using XDA Labs
TCUofficial said:
You dont flash modules... You go to the modules section of magisk manager, and hit the + sign. Then it will open a file manager, you simply just tap and hold on the zip file containing the module, and hit open in the top right. Your module will then be installed and a simple reboot will activate it. Flashing with twrp does nothing lol
Click to expand...
Click to collapse
That's just completely wrong... You install modules through the Manager OR by flashing in TWRP. Whatever floats your boat.
Didgeridoohan said:
That's just completely wrong... You install modules through the Manager OR by flashing in TWRP. Whatever floats your boat.
Click to expand...
Click to collapse
sorry, I have been installing Modules in Magisk Manager, I didn't know you could in twrp. Mistakes have been made today, and again, I am sorry.
Ha, amazing fix! Now can someone explain why that happens?
thanks for this! couldn't figure out why it was a perfect install, but after adding modules it would hang... this fixed it for me!
TCUofficial said:
You dont flash modules... You go to the modules section of magisk manager, and hit the + sign. Then it will open a file manager, you simply just tap and hold on the zip file containing the module, and hit open in the top right. Your module will then be installed and a simple reboot will activate it. Flashing with twrp does nothing lol
Click to expand...
Click to collapse
See this...
raymondsanusi said:
See this...
Click to expand...
Click to collapse
As I said earlier, I didnt know you could flash modules in twrp. I have no clue why that error happens.
Silkeyway said:
Ha, amazing fix! Now can someone explain why that happens?
Click to expand...
Click to collapse
Because some dev forgot a basic rule (to leave an empty line in the end) when making their modules
Come on devs ... Even the Github will give you a warning when this happens... Did you guys never check it again?:silly:
yurishouse said:
Because some dev forgot a basic rule (to leave an empty line in the end) when making their modules
Come on devs ... Even the Github will give you a warning when this happens... Did you guys never check it again?:silly:
Click to expand...
Click to collapse
Sure, but why do you need that?
Just asking because I'm learning bash and Python and now I wonder about things like that :angel:
5.1.1 fixed this issue, so.
You guys don't need to do it now.:good:
Silkeyway said:
Sure, but why do you need that?
Just asking because I'm learning bash and Python and now I wonder about things like that :angel:
Click to expand...
Click to collapse
Is a Linux rule, if not blank line, is like the file have not end.
Deic said:
Is a Linux rule, if not blank line, is like the file have not end.
Click to expand...
Click to collapse
Yep you are right.. I just read the update:good:
Hi there,why after updating my magisk manager,every timed force closes my magisk manager,I try clear dalvik and cache still not fix,any idea?Thanks
I'm on magisk 15.1. Almost modules that have been downloaded from repo can't be installed.
Check attached log for sure.
@topjohnwu
exodius48 said:
I'm on magisk 15.1. Almost modules that have been downloaded from repo can't be installed.
Check attached log for sure.
@topjohnwu
Click to expand...
Click to collapse
Since the DNS module has a different error than the others in the install log, could you post recovery logs for the other modules as well?
Edit: I forgot: your Magisk log as well, please.
Didgeridoohan said:
,..could you post recovery logs for the other modules as well?
Click to expand...
Click to collapse
Its ok if i install from recovery
Didgeridoohan said:
Edit: I forgot: your Magisk log as well, please.
Click to expand...
Click to collapse
I already attached magisk log from installed module above
exodius48 said:
Its ok if i install from recovery
Click to expand...
Click to collapse
Thank you, that confirms a suspicion...
I already attached magisk log from installed module above
Click to expand...
Click to collapse
No, you didn't. Those are the install logs. I asked for the Magisk log (or if you're using the beta release of v15.1 the magisk_debug.log would be even better).
Didgeridoohan said:
No, you didn't. Those are the install logs. I asked for the Magisk log (or if you're using the beta release of v15.1 the magisk_debug.log would be even better).
Click to expand...
Click to collapse
Check attached file. I'm using 15.1 stable.
Yesterday i used magisk on android 7.1.2 , now updated to 8.1.0 and i get same error.
i got same problem 2 days ago, so here is the fix i found.
go phone settings --> app permission, be sure you let installation permission to magisk from there, otherwise magisk always fails
chazarss said:
i got same problem 2 days ago, so here is the fix i found.
go phone settings --> app permission, be sure you let installation permission to magisk from there, otherwise magisk always fails
Click to expand...
Click to collapse
That's interesting. What device do you have? I do not have a installation permission on any of my devices...
chazarss said:
i got same problem 2 days ago, so here is the fix i found.
go phone settings --> app permission, be sure you let installation permission to magisk from there, otherwise magisk always fails
Click to expand...
Click to collapse
Did you mean storage permission? It already granted on my device.
exodius48 said:
Did you mean storage permission? It already granted on my device.
Click to expand...
Click to collapse
Had same issue .... uninstall magisk from recovery, then install magisk 14 and install any module (Viper4Android for e.g.) it should install properly and then update to 15.1 . all modules will work from then on.
andromodgod said:
Had same issue .... uninstall magisk from recovery, then install magisk 14 and install any module (Viper4Android for e.g.) it should install properly and then update to 15.1 . all modules will work from then on.
Click to expand...
Click to collapse
If so, the issue is from magisk 15.1 i think
exodius48 said:
If so, the issue is from magisk 15.1 i think
Click to expand...
Click to collapse
not really. i mean my device is qmobile Noir E2 (Chinese Phone Rebrand) and its operating system is from the Panasonic Eluga A3, which i modified to not encrypt internal storage and such. so it might be a problem with generic devices and not with magisk.
Didgeridoohan said:
That's interesting. What device do you have? I do not have a installation permission on any of my devices...
Click to expand...
Click to collapse
@exodius48
I have OnePlus 5 - On android Oreo it asks spesific permission for apps to install mods or apks
Use these kw to search on settings`Install unknown apps`
chazarss said:
@exodius48
I have OnePlus 5 - On android Oreo it asks spesific permission for apps to install mods or apks
Use these kw to search on settings`Install unknown apps`
Click to expand...
Click to collapse
Ah... Then I understand. That has nothing to do with the Managers ability to install modules only with it's built-in update feature. And there's no need to manually enable it. If an app needs that permission, you'll get a message that it needs to be activated.
Didgeridoohan said:
Ah... Then I understand. That has nothing to do with the Managers ability to install modules only with it's built-in update feature. And there's no need to manually enable it. If an app needs that permission, you'll get a message that it needs to be activated.
Click to expand...
Click to collapse
No it doesn`t show message, i just found it by mistaken then enabled and all problem solved, till then i have searched so much on internet
chazarss said:
No it doesn`t show message, i just found it by mistaken then enabled and all problem solved, till then i have searched so much on internet
Click to expand...
Click to collapse
Hm... It's not supposed to show a message when installing modules though, only when updating the Manager or otherwise installing an apk manually.
I find it interesting that installing modules wouldn't work unless you enable that option... Could you record a logcat when install a module with the setting off and then when it's on?
Didgeridoohan said:
Hm... It's not supposed to show a message when installing modules though, only when updating the Manager or otherwise installing an apk manually.
I find it interesting that installing modules wouldn't work unless you enable that option... Could you record a logcat when install a module with the setting off and then when it's on?
Click to expand...
Click to collapse
sorry it was like nightmare so i just dont want to risk it and break anything again. but i remember that everytime i tried to install any mod, magisk fails and says "Unable to extract zip", it is kinda phone doesnt let it to use storage and make installation, but after gave the permission everything solved.
Edit. Ss attached from my setting
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.