Let's bring some love to our google-phones!
[Reserved for feature meaningful content]
P.S. As of now, you may check my AFH folder with all my builds - https://www.androidfilehost.com/?w=files&flid=183895
[***Reserved***]
goodwin_c said:
Let's bring some love to our google-phones!
[Reserved for feature meaningful content]
P.S. As of now, you may check my AFH folder with all my builds - https://www.androidfilehost.com/?w=files&flid=183895
Click to expand...
Click to collapse
Where's the Magisk uninstaller for Pixel phones?
Haha called us fan boy's FML guess so..
Getting the 5min unroot like everyone else I guess.
Now that you have your own thread, any chance you'll be pushing to Git more frequently for those of use who can build it on our own?
I'd appreciate it if you could.
So the 13.3 will lose root with Magisk Hide enabled after a little bit. 13_10 (the previous version) should work, but will no longer pass Safety Net....is that the correct state of things?
skaforey said:
So the 13.3 will lose root with Magisk Hide enabled after a little bit. 13_10 (the previous version) should work, but will no longer pass Safety Net....is that the correct state of things?
Click to expand...
Click to collapse
Yes. Fix is on it's way. Hope i can publish it tomorrow.
admiralspeedy said:
Now that you have your own thread, any chance you'll be pushing to Git more frequently for those of use who can build it on our own?
I'd appreciate it if you could.
Click to expand...
Click to collapse
I'm trying my best. But it is pain in ass to merge official commits with my work. Sometimes it's hard to find time even to prepare new build. But i'll try to update github more offten
DodoGTA said:
Where's the Magisk uninstaller for Pixel phones?
Click to expand...
Click to collapse
It's second in my todo list. First i have to fix Hide crashes and installation issue (somehow magisk.img is not created properly on fresh installs). So, after that, i'll work on uninstall script
skaforey said:
So the 13.3 will lose root with Magisk Hide enabled after a little bit. 13_10 (the previous version) should work, but will no longer pass Safety Net....is that the correct state of things?
Click to expand...
Click to collapse
There's a temporary fix for 13_10 but it won't survive a reboot
Sent from my Pixel XL using Tapatalk
Soooperstar said:
There's a temporary fix for 13_10 but it won't survive a reboot
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
I'm using a Tasker profile to keep this working for the time being. If it's cool, I could create an apk in a few hours that will do the same thing.
raynan said:
I'm using a Tasker profile to keep this working for the time being. If it's cool, I could create an apk in a few hours that will do the same thing.
Click to expand...
Click to collapse
Yea that would be cool
Sent from my Pixel XL using Tapatalk
I thought you could place a file in the /magisk/.core/service.d/ folder (with 755 permissions) that gets ran on startup to do the same thing?
resetprop --delete init.svc.magisk_pfs
resetprop --delete init.svc.magisk_pfsd
resetprop --delete init.svc.magisk_service
resetprop --delete persist.magisk.hide
Looks like my last local build of 13.3 is working solid (finally!), but i forgot my usb cable at office, so can't debug why creation of magisk.img fails during flashing.
So, for now i'm uploading build without fixed install step. Check my AFH!
p.s. new package is Magisk-v13.3-Pixel-b1.zip
getting "magisk image mount failed" with 13.3 and 13.3-b1 on my Pixel XL. Do I need to be on the latest bootloader? I'm using April's at the moment. I just freshly installed Lineage by invisblek
jkashuba07 said:
getting "magisk image mount failed" with 13.3 and 13.3-b1 on my Pixel XL. Do I need to be on the latest bootloader? I'm using April's at the moment. I just freshly installed Lineage by invisblek
Click to expand...
Click to collapse
This is known issue if you are installing latest build and before you had no Magisk. You can wait day or two until i will fix this, or you can use workaround: install Magisk v13 (new10 suffix) and after that install latest 13.3-b1
apologies for dbl reply. i didnt catch your post goodwin.
p.s. thx for all your hard work.
Installed 13.3-b1 with no issue. Root present and working, but SafetyNet is failing (was working previously under 13.3). I tried rebooting, but this did not help. This does not require a new apk, does it?
skaforey said:
Installed 13.3-b1 with no issue. Root present and working, but SafetyNet is failing (was working previously under 13.3). I tried rebooting, but this did not help. This does not require a new apk, does it?
Click to expand...
Click to collapse
try to re-enable Magisk Hide and wait minute or two to give it to settle
P.S. Next release will come with uninstall script
goodwin_c said:
try to re-enable Magisk Hide and wait minute or two to give it to settle
P.S. Next release will come with uninstall script
Click to expand...
Click to collapse
I disabled it, then re-enabled it, then rebooted, and it didn't fix it.....do i need to reboot after I disable it?
Related
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.
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..
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
Hi.
I have a HTC 10 running LineageOS 14.1. In the past 4 days I have had to re install Magisk 16.3 at least 4 times daily as it keeps uninstalling itself. I have always had this issue with Magisk but it appears to have gotten worse instead of being solved.
Any suggestions as to what I can do to improve the situation?
It's likely not uninstalling itself, but something is killing the daemon. If you figure out what (aggressive battery saving might be a culprit), it would be good...
Magisk manager tells me that "Magisk is not installed" and that version 16.3 is available to install. However when I reboot it's there again so looks like you're right. Guess I'll have to have a look for what's causing it.. Thanks.
This is happening to me on OOS open beta 6. It's not really uninstalled because all my modules are present, but root does not work and the Magisk app is gone from my apps in settings and app drawer. I have to go into recovery and reflash it. This is happening on reboots at random.
it seems after the april update on stock orea 8.0 MIA1 Xiaomi this issues has become frequant.
manan001 said:
it seems after the april update on stock orea 8.0 MIA1 Xiaomi this issues has become frequant.
Click to expand...
Click to collapse
Some users are experiencing this, and I suspect it's a MagiskHide thing. You could help investigating by doing two things:
Install a beta release (use v16.3 because of the 64-bit issue with v16.4), and provide the magisk_debug.log after Magisk "uninstalls itself". You might have to grab it from recovery, since you're loosing root.
Disable MagiskHide and let it be disabled for a while to see if the issue still occurs (to confirm if it's MagiskHide or not).
Can be caused by Greenify?
I have the same problem magisk uninstalled after installing sdw hide root & sdw mock location through xposed installer
same issue but xposed included.
LG G6 Rootet Oreo Stock debloatet Magisk 17.2. same problem. deinstalling itself
kerpert said:
Can be caused by Greenify?
Click to expand...
Click to collapse
I installed greenify and this happened......probably it is the cause
m1l4droid said:
@Didgeridoohan adding Magisk as an exception in the MIUI battery saver didn't work. Not sure what to do.
Click to expand...
Click to collapse
Me neither...
There's a relatively active GitHub issue open about this issue, but there's been nothing definitive found about it yet.
The reports about this issue are so scattered, lacking in details and undefined that it's hard to say anything either way. Some users have success if disabling MagiskHide, some not so much, etc.
Someone that is experiencing the issue need to figure out what it's about. Until then there's not much to do...
It causes because of Busybox... uninstall busybox module fixed the problem for me
Didgeridoohan said:
... but something is killing the daemon. If you figure out...
Click to expand...
Click to collapse
Definition for daemon: https://www.linux.org/threads/android-services-and-daemons.10847/
How can one figure out?
kerpert said:
Can be caused by Greenify?
Click to expand...
Click to collapse
Nope. I've uninstalled greenify and magisk stopped anyway. So it's not related to greenify.
dan60 said:
How can one figure out?
Click to expand...
Click to collapse
Possibly by saving logs at the moment the daemon is killed off. Can be tricky...
If you don't want to, or don't have the skill to figure that out, you could try this meanwhile:
https://forum.xda-developers.com/apps/magisk/magisk-installed-workaround-t3908748
Would be interesting to know if it works for everyone.
Didgeridoohan said:
If you don't want to, or don't have the skill to figure that out, you could try this meanwhile:
https://forum.xda-developers.com/apps/magisk/magisk-installed-workaround-t3908748
Would be interesting to know if it works for everyone.
Click to expand...
Click to collapse
I should probably state that the module was made using a 17 template so min magisk ver. 17. There's really no telling what's killing the daemon. Also I note in the thread if magiskd is killed manually my module doesn't work. Don't know what all that is about... I've been playing around trying to kill it off manually and restart with no success using SSH as my root access. I don't expect this to work for everyone because I don't know how their daemon is dying. For some odd reason the module works for me when my daemon dies randomly so I'm happy with that. BTW I included logging which prints time and date script detects magisk not running and if it successfully restarted. The logs located in /data/local/tmp/magiskd-helper.log. I also have .pid in /data/local/run. Create dir if non-existent and . pid should be there.
Geofferey said:
I should probably state that the module was made using a 17 template so min magisk ver. 17. There's really no telling what's killing the daemon. Also I note in the thread if magiskd is killed manually my module doesn't work. Don't know what all that is about... I've been playing around trying to kill it off manually and restart with no success using SSH as my root access. I don't expect this to work for everyone because I don't know how their daemon is dying. For some odd reason the module works for me when my daemon dies randomly so I'm happy with that. BTW I included logging which prints time and date script detects magisk not running and if it successfully restarted. The logs located in /data/local/tmp/magiskd-helper.log. I also have .pid in /data/local/run. Create dir if non-existent and . pid should be there.
Click to expand...
Click to collapse
You could let the script also dump the current logcat buffer to a file (or cyclically save logcat to a file set to a certain size) when it detects the Magisk daemon not running. Might show why it dies...
Didgeridoohan said:
... try this meanwhile:
https://forum.xda-developers.com/apps/magisk/magisk-installed-workaround-t3908748
Would be interesting to know if it works for everyone.
Click to expand...
Click to collapse
Great initiative. I installed it yesterday, but sadly my oreo moto z play got unrooted again (same as if no Magiskd-helper had been flashed). But thanks for trying to help.
dan60 said:
Great initiative. I installed it yesterday, but sadly my oreo moto z play got unrooted again (same as if no Magiskd-helper had been flashed). But thanks for trying to help.
Click to expand...
Click to collapse
When you reboot does magisk come back? Could you post output of /data/local/magiskd-helper.log? I would like to see if it even attempted.
Google Pay has stopped working over a week ago and i was hoping for a fix but nothing has come? Did I do something wrong?
Running Android 6.1.6 Magisk Manager
Edit
There is also a bug with the manager? When i select apps for Magisk Hide it doesn't save and when i reload the list all that apps are unticked again??
Thanks in advance
Logs?
Didgeridoohan said:
Logs?
Click to expand...
Click to collapse
Magisk doesn't show any logs, where do I go to turn on Android logging?
JoshuaM765 said:
Magisk doesn't show any logs, where do I go to turn on Android logging?
Click to expand...
Click to collapse
There's your problem...
MagiskHide uses Android logging to detect when it needs to hide from an app or process.
Have you disabled logd? Used something like Kernel Adiutor to disable logs? Etc... Turn it back on and things will start working again.
[HIDE[/HIDE]
Didgeridoohan said:
There's your problem...
MagiskHide uses Android logging to detect when it needs to hide from an app or process.
Have you disabled log's? Used something like Kernel Adiutor to disable logs? Etc... Turn it back on and things will start working again.
Click to expand...
Click to collapse
I don't ever remember disabling logs or using a kernel adiutor. Would I need to edit to turn it on and how would I go about doing this?
Just to confirm, run this in a terminal emulator:
Code:
su -c magiskhide --enable
If it reports that logs are disabled, we can keep on this track.
The question is what happened "over a week ago" that caused things to change. Did you by any chance update Magisk? From v15.4 there was a change that for some devices wrongly disables MagiskHide because it can't detect that Android logging is running. That's been fixed and should be in the next release. You could try the unofficial snapshots by @kantjer, if you're impatient... Just be aware that they might not be built from release ready code.
Didgeridoohan said:
Just to confirm, run this in a terminal emulator:
Code:
su -c magiskhide --enable
If it reports that logs are disabled, we can keep on this track.
The question is what happened "over a week ago" that caused things to change. Did you by any chance update Magisk? From v15.4 there was a change that for some devices wrongly disables MagiskHide because it can't detect that Android logging is running. That's been fixed and should be in the next release. You could try the unofficial snapshots by @kantjer, if you're impatient... Just be aware that they might not be built from release ready code.
Click to expand...
Click to collapse
It was working then I got Xposed for Magisk but that put it in a boot loop so i factory reset and rerooted with Magisk and its now stopped working. When I do the terminal emulator i get "Logb is not running, cannot run logcat"
JoshuaM765 said:
It was working then I got Xposed for Magisk but that put it in a boot loop so i factory reset and rerooted with Magisk and its now stopped working. When I do the terminal emulator i get "Logb is not running, cannot run logcat"
Click to expand...
Click to collapse
Is logcat running? You can test this by using an app like Matlog. If it shows the log, it is a matter of the Magisk v15.4+ bug of detecting logging fully. Solution in that case would be to wait for the next release, test an unofficial snapshot linked above, or revert to a Magisk version prior to v15.4.
Didgeridoohan said:
Is logcat running? You can test this by using an app like Matlog. If it shows the log, it is a matter of the Magisk v15.4+ bug of detecting logging fully. Solution in that case would be to wait for the next release, test an unofficial snapshot linked above, or revert to a Magisk version prior to v15.4.
Click to expand...
Click to collapse
Yes Matlog works, where would i get an unoffical snapshot from?
JoshuaM765 said:
Yes Matlog works, where would i get an unoffical snapshot from?
Click to expand...
Click to collapse
I linked it a few posts ago...
Oh, sorry missed those.
Thanks for all the help, i will report back if it works.
Thanks so much, it was solved using the custom Magisk update link that you posted, Thanks again
JoshuaM765 said:
Thanks so much, it was solved using the custom Magisk update link that you posted, Thanks again
Click to expand...
Click to collapse
Thank you. That's the first confirmation I've seen of anyone with this issue having things working with the current code. That means the fix works...
Next official release (likely a beta) will have the fix included.
I'm also having trouble getting Google pay to work. The app also automatically gets disabled by my phone, and i have to search for it in the play store to re enable it. Magiskhide is enabled. Might it be because I'm in Mexico right now?
basily said:
I'm also having trouble getting Google pay to work. The app also automatically gets disabled by my phone, and i have to search for it in the play store to re enable it. Magiskhide is enabled. Might it be because I'm in Mexico right now?
Click to expand...
Click to collapse
Kindly Do The Following
- Clear Data&Cache Of Google Pay
- Disable Telephone Permission Of Google Play Services
- Try To Use Google Pay
Dreamer(3MF) said:
Kindly Do The Following
- Clear Data&Cache Of Google Pay
- Disable Telephone Permission Of Google Play Services
- Try To Use Google Pay
Click to expand...
Click to collapse
Thanks for the advice, but i tried it and same result.
basily said:
Thanks for the advice, but i tried it and same result.
Click to expand...
Click to collapse
Send The Full Logcat Of Google Pay & Inform Me About The Installed Version Of Magisk.
Didgeridoohan said:
Just to confirm, run this in a terminal emulator:
Code:
su -c magiskhide --enable
If it reports that logs are disabled, we can keep on this track.
The question is what happened "over a week ago" that caused things to change. Did you by any chance update Magisk? From v15.4 there was a change that for some devices wrongly disables MagiskHide because it can't detect that Android logging is running. That's been fixed and should be in the next release. You could try the unofficial snapshots by @kantjer, if you're impatient... Just be aware that they might not be built from release ready code.
Click to expand...
Click to collapse
I have the same issue as my Google Pay doesn't work now (after 16.3). Now I am on magisk 16.4.
I tried this Terminal command, su -c magiskhide --enable which returns that hide is already enabled.
My Google Pay was working normal now not working. By the way, SafetyNet test pass through.
smohanv said:
I have the same issue as my Google Pay doesn't work now (after 16.3). Now I am on magisk 16.4.
I tried this Terminal command, su -c magiskhide --enable which returns that hide is already enabled.
My Google Pay was working normal now not working. By the way, SafetyNet test pass through.
Click to expand...
Click to collapse
If you have MagiskHide working (passing SafetyNet), there's no need to mess with the enable command. That was just to confirm if the user has an issue where Magisk couldn't detect if logging was running (that's been fixed in v16.4).
Does Google Pay still work on Magisk v16.0? Or is it a matter of an update to Google Pay? What happens if you disable Telephone permissions for Google Play Services (like users of the Tez app have to do)? Or If you add all phone services you the Hide list?
Dreamer(3MF) said:
Send The Full Logcat Of Google Pay & Inform Me About The Installed Version Of Magisk.
Click to expand...
Click to collapse
Ok, I'm trying to get a logcat using terminal, but it keeps coming out at over 1mb, and xda won't let me attach a text file over 512kb. Shall i get it with adb with some filtering? I'm not very familiar with logcats, so your suggestion would be welcome.
I'm on the latest stable magisk: v16.0. For safetynet check, it successes, but ctsProfile, and basicIntegrity false.
I'm on a Nexus 6P, fully updated.