I'd even take an explanation of how to do it, I could possibly figure it out from there.
You might wanna try this:-
https://forum.xda-developers.com/moto-z-play/how-to/how-to-enable-miracast-t3565852
How to enable Miracast | Moto Z Play - XDA Forums - XDA Developers
Sent from my Moto G3 Turbo Edition
Is there a way to do that with a Magisk module?
ird0 said:
Is there a way to do that with a Magisk module?
Click to expand...
Click to collapse
If it's just about changing a prop you can easily do that with a boot script, make a Magisk module, or use my MagiskHide Props Config to set a custom prop.
Didgeridoohan said:
If it's just about changing a prop you can easily do that with a boot script, make a Magisk module, or use my MagiskHide Props Config to set a custom prop.
Click to expand...
Click to collapse
Much appreciated, thanks.
Didgeridoohan said:
If it's just about changing a prop you can easily do that with a boot script, make a Magisk module, or use my MagiskHide Props Config to set a custom prop.
Click to expand...
Click to collapse
Just to make sure, did I do it right?
http://imgur.com/ZkE0tin
ird0 said:
Just to make sure, did I do it right?
http://imgur.com/ZkE0tin
Click to expand...
Click to collapse
Yup. If it doesn't work at first, try going to the script settings (currently menu option 6) and change the boot stage to post-fs-data.
Edit: NO! I looked again. You've done a typo, it's supposed to be "enable", not "enabled".
Didgeridoohan said:
If it's just about changing a prop you can easily do that with a boot script, make a Magisk module, or use my MagiskHide Props Config to set a custom prop.
Click to expand...
Click to collapse
Didgeridoohan said:
Yup. If it doesn't work at first, try going to the script settings (currently menu option 6) and change the boot stage to post-fs-data.
Edit: NO! I looked again. You've done a typo, it's supposed to be "enable", not "enabled".
Click to expand...
Click to collapse
Thanks for spotting that. I can't test it until I get home. Much appreciated
Didgeridoohan said:
If it's just about changing a prop you can easily do that with a boot script, make a Magisk module, or use my MagiskHide Props Config to set a custom prop.
Click to expand...
Click to collapse
Didgeridoohan said:
Yup. If it doesn't work at first, try going to the script settings (currently menu option 6) and change the boot stage to post-fs-data.
Edit: NO! I looked again. You've done a typo, it's supposed to be "enable", not "enabled".
Click to expand...
Click to collapse
Seems I can connect but then my phone does a UI restart. I guess it just doesn't work or I'm missing some kind of library or something.
I'm stuck at the same point on my P2XL. Did you ever figure it out?
Stuck here too. I can enable the menu but when I try to connect, I get a restart of the UI and I go back to the lock screen. Pixel 2 XL
I finally gave up.
I just saw a recent post on the Pixel forum with a guide to get it working (at least for the original Pixel.) Maybe this could prove useful:
https://forum.xda-developers.com/pixel/how-to/guide-how-to-enable-miracast-pixel-t3888780
Credit to sbjbs
Sent from my Pixel 2 using Tapatalk
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.
As title says i want to edit build prop, any modules or something?
@topjohnwu is currently implementing this into Magisk Manager. As for now you can use:
Code:
/data/magisk/resetprop build.prop.item value
loserskater said:
@topjohnwu is currently implementing this into Magisk Manager. As for now you can use:
Code:
/data/magisk/resetprop build.prop.item value
Click to expand...
Click to collapse
Ok im lost not sure how to do that? I need to make a module?
You can either make a module or a script that you put in /magisk/.core/post-fs-data.d. More details in the All-In-One wiki (stickied thread).
And as stated above, in upcoming versions you'll be able to change prop values in a GUI in the Magisk Manager. It's on the to-do list, but of course there's no ETA.
Didgeridoohan said:
You can either make a module or a script that you put in /magisk/.core/post-fs-data.d. More details in the All-In-One wiki (stickied thread).
And as stated above, in upcoming versions you'll be able to change prop values in a GUI in the Magisk Manager. It's on the to-do list, but of course there's no ETA.
Click to expand...
Click to collapse
Thanks, if i use magisk hide it will hide this too right?
Cheers
I added this:
/data/magisk/resetprop ro.product.model "Pixel XL"
/data/magisk/resetprop ro.opa.eligible_device true
/data/magisk/resetprop ro.product.brand "google"
/data/magisk/resetprop ro.product.manufacturer "Google"
In the post fs data of another module so i basically hacked in the build prop, but magisk hide fails (doesn't fail when i don't mess with the build prop)
metrize said:
I added this:
/data/magisk/resetprop ro.product.model "Pixel XL"
/data/magisk/resetprop ro.opa.eligible_device true
/data/magisk/resetprop ro.product.brand "google"
/data/magisk/resetprop ro.product.manufacturer "Google"
In the post fs data of another module so i basically hacked in the build prop, but magisk hide fails (doesn't fail when i don't mess with the build prop)
Click to expand...
Click to collapse
There's a module for activating Google assistant in the repo already. Have you tried that?
Didgeridoohan said:
There's a module for activating Google assistant in the repo already. Have you tried that?
Click to expand...
Click to collapse
I'm more interested in changing the device so that it thinks it's a pixel. It fails safetynet even with magisk hide when i do this though
metrize said:
I'm more interested in changing the device so that it thinks it's a pixel. It fails safetynet even with magisk hide when i do this though
Click to expand...
Click to collapse
Why?
I'm not sure about the details, but if your device doesn't match a profile Google have on their servers you won't get a CTS profile match. That might be why...
Can you pass basic integrity with the mods you made?
Didgeridoohan said:
Why?
I'm not sure about the details, but if your device doesn't match a profile Google have on their servers you won't get a CTS profile match. That might be why...
Can you pass basic integrity with the mods you made?
Click to expand...
Click to collapse
it's for google photos unlimited original backup (only on pixels)
Without the mods i did above I can pass safetynet and everything fine
With the mods nothing psses not even basic integrity.
Can build.prop be reset with magisk hide or is that functionality not possible on android?
If it could reset build.prop to the original build.prop then I would pass safetynet, but I'm not sure if magisk can do this? @topjohnwu maybe might know?
metrize said:
it's for google photos unlimited original backup (only on pixels)
Without the mods i did above I can pass safetynet and everything fine
With the mods nothing psses not even basic integrity.
Can build.prop be reset with magisk hide or is that functionality not possible on android?
If it could reset build.prop to the original build.prop then I would pass safetynet, but I'm not sure if magisk can do this? @topjohnwu maybe might know?
Click to expand...
Click to collapse
It's possible... You can edit the enable and disable files in /magisk/.core/magiskhide/ to do what you want.
Didgeridoohan said:
There's a module for activating Google assistant in the repo already. Have you tried that?
Click to expand...
Click to collapse
Didgeridoohan said:
It's possible... You can edit the enable and disable files in /magisk/.core/magiskhide/ to do what you want.
Click to expand...
Click to collapse
Thanks this seems promising, however i don't understand the syntax. If you have time could you tell me what to add with the build prop changes i wanted earlier in the thread. Thanks a lot for all the help
metrize said:
Thanks this seems promising, however i don't understand the syntax. If you have time could you tell me what to add with the build prop changes i wanted earlier in the thread. Thanks a lot for all the help
Click to expand...
Click to collapse
Look at how ro.debuggable, ro.secure and the other ro props are handled in the enable file. Match what you want to do to those and then add similar code with your other desired changes in the disable file.
It should be as simple as copying, pasting and changing variable names and props to match your desired setup.
Didgeridoohan said:
Look at how ro.debuggable, ro.secure and the other ro props are handled in the enable file. Match what you want to do to those and then add similar code with your other desired changes in the disable file.
It should be as simple as copying, pasting and changing variable names and props to match your desired setup.
Click to expand...
Click to collapse
Am I right in assuming when magisk hide is disabled the build prop will be changed back to the pixel one?
thanks
ok it's working just going to do the disable one
Okay, when I did the enable magiskhide and changed it, it passes safetynet but then when I changed the dsiable magiskhide file it fails safetynet now even when i enable magiskhide.. weird
core only works though with changes to both enable and disable so now im muffed
Dammit... Now you piqued my curiosity.
I'm heading to bed (shoulda done that 3 hours ago), but if you post your enable and disable files I'm sure someone can take a look at it. If not, I'm around again after a few hours of z and some breakfast.
Attached enable and disable.
(Renamed it to txt file otherwise wouldn't let it upload)
For the module it's just a system.prop module with the following lines;
# This file will be read by resetprop
# Example: Change dpi
# ro.sf.lcd_density=320
ro.product.model=Pixel
ro.product.brand=google
ro.product.manufacturer=Google
When I go core only mode, enable magisk hide then disable (to get the build prop change) then enable magisk hide again it works though. So I think it's something with the module that makes it fail
metrize said:
When I go core only mode, enable magisk hide then disable (to get the build prop change) then enable magisk hide again it works though. So I think it's something with the module that makes it fail
Click to expand...
Click to collapse
How about without the module installed and Core only mode disable?
Since you seem to have a working setup with the enable/disable scripts I'd consider just using those. You could even set up automation with Tasker or a similar app. Use the following code in a Run Shell action:
Code:
sh /magisk/.core/magiskhide/enable
And the same for the disable script.
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?
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
After some trial and error, I have found the secret sauce which allows you to disable EdXposed's app list mode and still pass SafetyNet. This means I am one step closer to having a fully customized & still-secure phone (bootloader re-locking is probably going to happen in the coming weeks - stay tuned ). But what it also means is that I can write a post to share this new knowledge with all of you!
I am sure this advice will become dated soon enough. However, right now, there is still a way to have proper system-wide EdXposed without tripping SafetyNet.
After installing the latest Riru, run touch /data/adb/riru/enable_hide and reboot. This will enable "hidden" mode, which... does something with /proc that I don't care to understand. The point is that now it is much easier for EdXposed to hide its presence, since the hooking framework it's using is now doing so properly.
Then, install the latest canary version of EdXposed YAHFA. SandHook only passes SafetyNet when all modules are disabled, however... YAHFA passes SafetyNet regardless. YAHFA simply doesn't care. That means if you have your MagiskHide set up correctly, and you're not using a module like HiddenCore which intentionally ****s with the response signature, you will have fully passing SafetyNet with EdXposed. You will NOT have to enable app list mode to blacklist Google services. That means XPrivacyLua (and other modules too) will work on them. Just be careful not to use any modules which intentionally screw with SafetyNet
If you're willing to take the slight performance hit that comes with using YAHFA over SandHook, it may be something to try. The 7 Pro is a pretty fast phone, and the second or two of delay when starting up a launcher for the first time (for example) is much more acceptable compared to the 10 seconds or so of "Phone is starting..." you have to endure on competing phones, even without EdXposed.
the enable_hide option in the riru folder is not available on my phone.
Auel Yakubu said:
the enable_hide option in the riru folder is not available on my phone.
Click to expand...
Click to collapse
What do you mean it's not available?
LoganDark said:
What do you mean it's not available?
Click to expand...
Click to collapse
When i go into the /data/adb/riru/ folder on my phone then i don't see the enable_hide file inside it.
Auel Yakubu said:
When i go into the /data/adb/riru/ folder on my phone then i don't see the enable_hide file inside it.
Click to expand...
Click to collapse
Yes, you're supposed to make one. That's what enables hide.
The touch command creates a blank file
Would you kindly provide further explanation !
how to run that
touch /data/adb/riru/enable_hide
mahaseno said:
Would you kindly provide further explanation !
how to run that
touch /data/adb/riru/enable_hide
Click to expand...
Click to collapse
Download Termux, run su to enter a root shell, and then run that touch /data/adb/riru/enable_hide
i did that
and give me : not found!
mahaseno said:
i did that
and give me : not found!
Click to expand...
Click to collapse
Could you provide a screenshot please?
i'm not using canary version by the way
mahaseno said:
i'm not using canary version by the way
Click to expand...
Click to collapse
Oh whoops. Hide is only supported in the new version of Riru, the one that says "Riru" instead of "Riru - Core".
screenshot
mahaseno said:
screenshot
Click to expand...
Click to collapse
You forgot the space after touch.
LoganDark said:
Oh whoops. Hide is only supported in the new version of Riru, the one that says "Riru" instead of "Riru - Core".
Click to expand...
Click to collapse
i'm sorry
what do you mean?
this what i have installed
mahaseno said:
i'm sorry
what do you mean?
this what i have installed
Click to expand...
Click to collapse
You have to remove EdXposed and reinstall the latest canary version (YAHFA version). You have v4 which doesn't support your version of Riru
link please ?
aha you mean from inside edxposed ?
mahaseno said:
link please ?
Click to expand...
Click to collapse
There are no links.
Here's what you do:
Go into Magisk Manager and remove your EdXposed module.
Reboot.
Open EdXposed Manager, and wait a few seconds. A Canary tab should appear on the top.
Go to the Canary tab. At the top, there should be a drop-down with two options: SandHook and YAHFA. Choose YAHFA and press install.
You will be redirected to your web browser which will download a zip file. This is a Magisk module you must install from storage. (Technically, this is a link, but please do not post it here as the EdXposed Manager will know the latest version automatically.)
After all that, your EdXposed should be up to date.
OK bro i will try it now
hope it will work
my phone stuck after booting
i will remove this version from recovery
thx for help bro