EDIT: Official fix is out, please follow this link: https://forum.xda-developers.com/showpost.php?p=73079059&postcount=25
Good evening,
since Google broke all our beloved SafetyNet passing phones I decided to have a look at it. Turns out they have extended their property scanning.
There is an easy fix BUT: I have no idea how this fix interferes with Magisks internal behavior. @topjohnwu Why are properties used for magisk internals?
SafetyNet checks now for these properties, so we have to delete them:
Code:
[init.svc.magisk_pfs]: [stopped]
[init.svc.magisk_pfsd]: [stopped]
[init.svc.magisk_service]: [stopped]
[persist.magisk.hide]: [1]
EDIT: @dimon222 had a look at magisk source and answered my question why these properties even exist:
BTW, I shortly check'd source of Magisk, it seems 3 of those flags are related to exit code after start of Magisk services on boot. Basically, they're automatically set by Android when service with such name is started.
I guess dev will probably rename those services to avoid detect or hide it somehow.
https://github.com/topjohnwu/Magisk/blob/master/scripts/init.magisk.rc
And the last flag is some internal for Magisk.
It feels like something serious, but I don't know if its only used during boot. Maybe if u reset it after boot, it won't be automatically reloaded by Magisk, and it will continue to use hide.
https://github.com/topjohnwu/Magisk/search?utf8=✓&q=MAGISKHIDE_PROP
Worth to check if SafetyNet apps are still working after that, not just SafetyNet check itself. Its quite possible that it won't hide, if it gets this property from global variable at realtime.
Click to expand...
Click to collapse
How to fix this:
1. This fix is only a temporary fix. You will have to apply it after every reboot.
2. Use a Terminal emulator app or adb to enter these commands.
3. Use resetprop to delete the properties - again: I have no idea how this interferes with magisk behavior!!!! Do this at your own risk:
Code:
su
resetprop --delete init.svc.magisk_pfs
resetprop --delete init.svc.magisk_pfsd
resetprop --delete init.svc.magisk_service
resetprop --delete persist.magisk.hide
Using Magisk Core mode? also execute this command:
Code:
resetprop --delete ro.magisk.disable
4. Optional/Not recommended: If you want to make this temporary fix more permanent, add all the required resetprop calls to a .sh file inside /magisk/.core/service.d/ and let magisk automatically execute the script for you every startup.
Troubleshooting if this didnt work:
Still doesnt work? Try this: https://forum.xda-developers.com/showpost.php?p=73056617&postcount=65
Check for other magisk properties using "getprop | grep magisk" and delete them as well (at your own risk!)
After deleting the properties SafetyNet check will pass again
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What kind of functionality do you still have after this? Does magisk manager crash? Do modules work? Does su work?
Can you please explain in detail that how to do it.
Thanks
Would these persist through a flash-all without wiping the device? I still couldn't get safety net to pass after that.
ali.ahmad said:
Can you please explain in detail that how to do it.
Thanks
Click to expand...
Click to collapse
Looks like you just need adb shell or a terminal emulator on your phone, and su/root.
ali.ahmad said:
Can you please explain in detail that how to do it.
Thanks
Click to expand...
Click to collapse
Yes please, I'm a little lost too
ali.ahmad said:
Can you please explain in detail that how to do it.
Thanks
Click to expand...
Click to collapse
Type it into a terminal on your phone.
No luck
It worked for me, thank you.
Enviado desde mi SM-N930F mediante Tapatalk
Interesting. I'm curious, how were you able to detect what safety net is actually detecting?
I haven't tried your fix as it's not super imperative for me to get safetynet passing for myself just curious what you are using to find this stuff out.
Either way thanks for the work
Then, is these sure? I don't have a computer here to unbrick my phone.
Jolt420 said:
What kind of functionality do you still have after this? Does magisk manager crash? Do modules work? Does su work?
Click to expand...
Click to collapse
SU still works, Magisk hide seems to work as well (safetynet passes, so magiskhide has to work)
I don't use many modules, only AppSystemizer and this one still works
ali.ahmad said:
Can you please explain in detail that how to do it.
Thanks
Click to expand...
Click to collapse
You need to enter the commands either in a Terminal Emulator app on your phone or use adb to connect to your phone and then enter the commands.
Also keep in mind that the fix is only temporary, you need to apply the fix after every reboot.
Astur13 said:
Then, is these sure? I don't have a computer here to unbrick my phone.
Click to expand...
Click to collapse
It is only temporary. After every reboot you have to apply the fix again. So if it doesnt work/bug your phone simply reboot
Test_subj said:
No luck
Click to expand...
Click to collapse
please provide the output of
Code:
getprop | grep magisk
after applying the fix
Is there a way to load commands from a txt or something like that? It's a bit of a bother to manually enter it every time we reboot.
[email protected] said:
Good evening,
since Google broke all our beloved SafetyNet passing phones I decided to have a look at it. Turns out they have extended their property scanning.
There is an easy fix BUT: I have no idea how this fix interferes with Magisks internal behavior. @topjohnwu Why are properties used for magisk internals?
SafetyNet checks now for these properties:
Code:
[init.svc.magisk_pfs]: [stopped]
[init.svc.magisk_pfsd]: [stopped]
[init.svc.magisk_service]: [stopped]
[persist.magisk.hide]: [1]
How to fix this:
1. This fix is only a temporary fix. You will have to apply it after every reboot.
2. Use a Terminal emulator app or adb to enter these commands.
3. Use resetprop to delete the properties - again: I have no idea how this interferes with magisk behavior!!!! Do this at your own risk:
Code:
su
resetprop --delete init.svc.magisk_pfs
resetprop --delete init.svc.magisk_pfsd
resetprop --delete init.svc.magisk_service
resetprop --delete persist.magisk.hide
After deleting the properties SafetyNet check will pass again
Click to expand...
Click to collapse
Worked for me! Thanks!
ivanes82 said:
Is there a way to load commands from a txt or something like that? It's a bit of a bother to manually enter it every time we reboot.
Click to expand...
Click to collapse
You could store it in a .sh file on sdcard and execute the .sh file. (dont forget chmod +x)
It also might work to put the .sh file in /magisk/.core/service.d to let magisk automatically execute the script at startup, but im not sure if thats too early
Worked for me on the 6P. Magisk and root seem good so far.
[email protected] said:
You could store it in a .sh file on sdcard and execute the .sh file. (dont forget chmod +x)
It also might work to put the .sh file in /magisk/.core/service.d to let magisk automatically execute the script at startup, but im not sure if thats too early
Click to expand...
Click to collapse
Thank you very much. It is only as a temporary solution.
Worked for me on HTC 10, Magisk 13.2
Related
I dont have a custom recovery to be able to flash the installation .zip file.
I do have root access, I have tried to manually by push the files to the correct location with correct permissions.
but it results in a bootloop.
I currently trying it on my Meizu mx4 with lollipop 5.0.1.
It used how to work without issues on K.K
Im trying it with the xposed-sdk21-arm-20150430.zip
with Xpossed 3.0 alpha2
Things I have tried.
http://bbs.flyme.cn/thread-245435-1-1.html
http://bbs.flyme.cn/thread-240899-1-1.html
Anyone have any ideas on how to get this working please
Thank you.
Did a quick search and found this:
http://forum.xda-developers.com/meizu-mx/general/mx4-flashing-recovery-t3102402
Hope that helps!
Djlatino said:
Did a quick search and found this:
http://forum.xda-developers.com/meizu-mx/general/mx4-flashing-recovery-t3102402
Hope that helps!
Click to expand...
Click to collapse
I'm not asking for a custom recovery, I know about the situation of meizu and not being open source that way.
I'm asking for a way to install Xposed successfully without a custom recovery by manually pushing the files etc.
But thank you.
If you read that thread, you'll note that in order to flash anything to begin with, you're going to need the recovery emulator "FlashGordon".
http://forum.xda-developers.com/showthread.php?t=2250555
^Spoonfeedin'
Djlatino said:
If you read that thread, you'll note that in order to flash anything to begin with, you're going to need the recovery emulator "FlashGordon".
http://forum.xda-developers.com/showthread.php?t=2250555
^Spoonfeedin'
Click to expand...
Click to collapse
I appreciate the help, I knew a app was about that could flash .zips without recovery, I will try it out.
Unfortunately it didnt work, didnt change any files in /system
punkmonkey1984 said:
I appreciate the help, I knew a app was about that could flash .zips without recovery, I will try it out.
Unfortunately it didnt work, didnt change any files in /system
Click to expand...
Click to collapse
The alternative approach is manually copying and pasting the zip files to the appropriate folders but I don't know what permissions you have to set for each of them besides the standard 664, so I apologize for not finding a solution, but I have a tablet that is pretty much in ter same ballpark as the MX4 so I'll monitor this thread!
Djlatino said:
The alternative approach is manually copying and pasting the zip files to the appropriate folders but I don't know what permissions you have to set for each of them besides the standard 664, so I apologize for not finding a solution, but I have a tablet that is pretty much in ter same ballpark as the MX4 so I'll monitor this thread!
Click to expand...
Click to collapse
I have tried to do that also, its working on the mx4 pro, but that has a different cpu chip.
Watch the video on this thread :http://bbs.flyme.cn/thread-240899-1-1.html
It explains how to copy/paste to the correct places.
Hopefully it works for you.
punkmonkey1984 said:
I have tried to do that also, its working on the mx4 pro, but that has a different cpu chip.
Watch the video on this thread :http://bbs.flyme.cn/thread-240899-1-1.html
It explains how to copy/paste to the correct places.
Hopefully it works for you.
Click to expand...
Click to collapse
http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
Check out flashfire, it seems to be more active than flashgordon.
Thanks for the link btw.
Djlatino said:
http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
Check out flashfire, it seems to be more active than flashgordon.
Thanks for the link btw.
Click to expand...
Click to collapse
Seems to have better support, coming from Chainfire etc, but it just results in black screen without progress.
Will keep searching for a solution tomorrow.
Ok, can get it to show installed, but after I reboot it is just resulting in bootloops.
Anyone have a solution!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
punkmonkey1984 said:
Ok, can get it to show installed, but after I reboot it is just resulting in bootloops.
Anyone have a solution!
Click to expand...
Click to collapse
Same, got it installed, but boot loops for days.
Thank you based rovo for the Safe Mode
Djlatino said:
Same, got it installed, but boot loops for days.
Thank you based rovo for the Safe Mode
Click to expand...
Click to collapse
I did manage to get it installed and working without issues.
Follow the guide here: http://bbs.flyme.cn/forum.php?mod=viewthread&tid=254959&page=1&extra=#pid3301122
Files link: http://pan.baidu.com/s/1hq1pPUs
Basic chinese-> English:
1: Extracting installation charm Andrews 5.0 toolkit installation kingroot4.0 Mobile, the phone root, generally a few minutes to resolve.
2: the tmp folder, RE Manager copied to the system root directory, modify ub.sh tick all permissions.
3: Install a terminal emulator, open a terminal emulator to enter expert mode, choose Terminal Emulation, SU checkbox ticked above,
After entering sh /tmp/ub.sh carriage return (later sh space), etc. output stop after a while you can exit the terminal emulator.
4: Install xposed installer.apk, installation charm toolbox, open frame - module check Charm toolbox restart into effect.
I got it installed by wiping my data and trying on a fresh install before doing anything else, hopefully you wont have to do that.
Try removing all xposed related apps/modules before trying and rebooting/ clear catches before.
I used superSU not King user. Ignore charm-toolbox, thats a meizu flyme related module like gravity-box.
Follow the guide, then install xposed installer, mine didnt install, so i pushed in manually to /data/app with correct permissions then rebooted. I think it rebooted first time.
But a couple of times i have had to reboot by holding the power button for 10s because its gone into bootloop when activating new modules, but after it comes back on.
I got it to work another way, but my device is completely different.
What I did was install the installer, but right after I followed these instructions:
n root browser:
go to the /data/data/de.robv.android.xposed.installer/ and create folder "conf" (permissions rwxrwxrwx)
in folder "conf" create the file "jit_reset_offset" (permissions rw-r--r--)
Download Terminal Emulator, install and open it. Then:
type "su"
type "echo 0x98 > /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset"
Reboot the tablet.
Open Xposed Installer, install framework, reboot.
Click to expand...
Click to collapse
I gave that offset a shot and it luckily worked on mine. Unfortunately, the only way of getting the "offset" code is by analyzing some lib file, which I have yet to find out how to do. That being said, you can always try 0x98 a try as it seems to work on many. The default AOSP is 0x78, and some even have it as 184.
This does, however, fix most of the issues with "unsupported" devices out there, that seems to be the solution from rovo all the time.
punkmonkey1984 said:
I did manage to get it installed and working without issues.
Follow the guide here: http://bbs.flyme.cn/forum.php?mod=viewthread&tid=254959&page=1&extra=#pid3301122
Files link: http://pan.baidu.com/s/1hq1pPUs
Basic chinese-> English:
1: Extracting installation charm Andrews 5.0 toolkit installation kingroot4.0 Mobile, the phone root, generally a few minutes to resolve.
2: the tmp folder, RE Manager copied to the system root directory, modify ub.sh tick all permissions.
3: Install a terminal emulator, open a terminal emulator to enter expert mode, choose Terminal Emulation, SU checkbox ticked above,
After entering sh /tmp/ub.sh carriage return (later sh space), etc. output stop after a while you can exit the terminal emulator.
4: Install xposed installer.apk, installation charm toolbox, open frame - module check Charm toolbox restart into effect.
I got it installed by wiping my data and trying on a fresh install before doing anything else, hopefully you wont have to do that.
Try removing all xposed related apps/modules before trying and rebooting/ clear catches before.
I used superSU not King user. Ignore charm-toolbox, thats a meizu flyme related module like gravity-box.
Follow the guide, then install xposed installer, mine didnt install, so i pushed in manually to /data/app with correct permissions then rebooted. I think it rebooted first time.
But a couple of times i have had to reboot by holding the power button for 10s because its gone into bootloop when activating new modules, but after it comes back on.
Click to expand...
Click to collapse
I have installed xposed today by a very similar way that I have made but I am not sure if xposed totally installed.
Do you think that it is really installed?
I also have tried with the method of the chinese forum and the result is the same (basicaly is the same as my procedure).
There is any module to check it is really working? As you see I dont use much xposed
iicc said:
I have installed xposed today by a very similar way that I have made but I am not sure if xposed totally installed.
View attachment 3324770
Do you think that it is really installed?
I also have tried with the method of the chinese forum and the result is the same (basicaly is the same as my procedure).
There is any module to check it is really working? As you see I dont use much xposed
Click to expand...
Click to collapse
Flyme tools still works.
Did you encounter any bootloops?
You could try this one if your having trouble (not tested myself)
http://bbs.flyme.cn/thread-258466-1-1.html
punkmonkey1984 said:
Flyme tools still works.
Did you encounter any bootloops?
You could try this one if your having trouble (not tested myself)
http://bbs.flyme.cn/thread-258466-1-1.html
Click to expand...
Click to collapse
No bootloops so far.
[emoji33] [emoji33] thats the cofface cwm, I thought it didnt worked and the project was abandoned
iicc said:
No bootloops so far.
[emoji33] [emoji33] thats the cofface cwm, I thought it didnt worked and the project was abandoned
Click to expand...
Click to collapse
I'm not sure, I think it's only temporary cwm, I think it reverts back to the stock one after a reboot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
INTRODUCTION
I know, pressing the home button to unlock your phone it's very annoying. This module allows you to unlock your device without pressing the home button. The fingerprint scanner will remain always-on to allow that.
REQUIREMENTS
- Magisk 15.0+
- Any device
FEATURES
- Unlock your device without pressing the home button
- Works for sure with FPC fingerprints
CHANGELOG
- Updated module template to 1500
DOWNLOAD
AOF v1.4
INSTALLATION
Flash trough TWRP recovery and reboot.
SOURCE CODE
GitHub
CREDITS
- @Psy_Man (For this module)
you left kenzo sir?
no more firmware updates...
sorry for #OT
xN00Bx said:
you left kenzo sir?
no more firmware updates...
sorry for #OT
Click to expand...
Click to collapse
Yup. I've switched to MI Note 2.
Will alwyas on FP consume more battery and reduce the lifespam of the scanner? Thanks for the nice modules!
lsl640 said:
Will alwyas on FP consume more battery and reduce the lifespam of the scanner? Thanks for the nice modules!
Click to expand...
Click to collapse
I have it enabled in my phone and no battery drain for me.
I am going to flash it on my Mi note 2....Hope there wont be any battery drains.
Edit: It's working....Need to check battery drains....
Hi @Psy_Man,
I'm having issue on this module with my mi5 (128gb with global rom 8.1.4.0). After flashed it, Google Play and Google Play services crashed (keep pop-up error "has stopped") Do your module have any log for me to trace it?
cutesniper22 said:
Hi @Psy_Man,
I'm having issue on this module with my mi5 (128gb with global rom 8.1.4.0). After flashed it, Google Play and Google Play services crashed (keep pop-up error "has stopped") Do your module have any log for me to trace it?
Click to expand...
Click to collapse
Can not be related to this module. Wipe cache and dalvik cache and than reboot.
Stuck during boot on Mi5 64gb, Tried on MIUI 8 Global Beta 7.7.20 and MIUI 9 Global Beta 7.8.24. Magisk 13.6 Beta.
Psy_Man said:
Can not be related to this module. Wipe cache and dalvik cache and than reboot.
Click to expand...
Click to collapse
Yup, I did that before. No longer happened if I removed this module. (Google play store/services back to normal after restarted )
Reinstall this module again ... crashing is coming back again ~
cutesniper22 said:
Yup, I did that before. No longer happened if I removed this module. (Google play store/services back to normal after restarted )
Reinstall this module again ... crashing is coming back again ~
Click to expand...
Click to collapse
I will add logs to the next version
I've installed it on gemini miui8 7.6.29dev & magisk 13.3
I'm experiencing Play Services crashing after activating your module (it works flawlessly, tbh).
The solution for me was to uninstall the safetynet fix beta5.
My opinion is that a conflict happens between the two post-fs-data.sh files
edit: i've inserted the aof patch into the safetynet fix module and everything is working fine. Remove aof module and safetynet, reboot, then reboot to recovery and flash this file or add this module via magisk manager
Not working on Mi Note 2 with 8.5.2.0 China stable -
Stuck at mi logo and not boot on miui 9
MI 5 cihazımdan Tapatalk kullanılarak gönderildi
Does not work on Mi Note 2 MIUI 8.2.6.0
No side issues, just simply does not work.
When after booting I check /sys/devices/soc/soc:fpc_fpc1020/enable_wakeup it is still 0
The module was installed through Magisk and is marked active.
Thanks.
Flawless
Work flawlessly in a MI 5, running MIUI 9 latest xiaomi.eu version
mikhailmv said:
Does not work on Mi Note 2 MIUI 8.2.6.0
No side issues, just simply does not work.
When after booting I check /sys/devices/soc/soc:fpc_fpc1020/enable_wakeup it is still 0
The module was installed through Magisk and is marked active.
Thanks.
Click to expand...
Click to collapse
even manual execution of something like:
su
echo 1 >> /sys/devices/soc/soc:fpc_fpc1020/enable_wakeup
cat /sys/devices/soc/soc:fpc_fpc1020/enable_wakeup
gives:
0
mikhailmv said:
even manual execution of something like:
su
echo 1 >> /sys/devices/soc/soc:fpc_fpc1020/enable_wakeup
cat /sys/devices/soc/soc:fpc_fpc1020/enable_wakeup
gives:
0
Click to expand...
Click to collapse
This is strange! Try to chmod it first, so: chmod 777 /sys/devices/soc/soc:fpc_fpc1020/enable_wakeup
Than: echo 1 > /sys/devices/soc/soc:fpc_fpc1020/enable_wakeup
Psy_Man said:
This is strange! Try to chmod it first, so: chmod 777 /sys/devices/soc/soc:fpc_fpc1020/enable_wakeup
Than: echo 1 > /sys/devices/soc/soc:fpc_fpc1020/enable_wakeup
Click to expand...
Click to collapse
It does not help
I can set up any permissions on this file I want
And I do not get any error messages regarding "Permission denied"
And by the way the chmod sets the permissions properly: -rwxrwxrwx
But the result of cat /sys/devices/soc/soc:fpc_fpc1020/enable_wakeup is still 0
Thanks
Max Biaggi said:
I've installed it on gemini miui8 7.6.29dev & magisk 13.3
I'm experiencing Play Services crashing after activating your module (it works flawlessly, tbh).
The solution for me was to uninstall the safetynet fix beta5.
My opinion is that a conflict happens between the two post-fs-data.sh files
edit: i've inserted the aof patch into the safetynet fix module and everything is working fine. Remove aof module and safetynet, reboot, then reboot to recovery and flash this file or add this module via magisk manager
Click to expand...
Click to collapse
Thanks! This is working well for me!
Hi guys.
For those of you that recently unlocked your bootloader and rooted your device with Magisk... If you don't already know, you can download a Magisk Module created by Didgeridoohan, called 'MagiskHide Props Config'. Basically this solves the issue of the ctsProfile failing in safetynet. What it does is it can change the device fingerprint to one that is certified, allowing safetynet to pass.
I lot of you probably already know this, but I've read a lot posts about ctsProfile issues.
With this module, you should be able to use ANY official huawei mate 20 pro firmware and safetynet should pass.
There is more info about this module in thread https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228
So what is the steps you need to follow?
I have u locked bootloader and safety et is failing. At cts.
Evert hing is stock and wiped.
Verstuurd vanaf mijn LYA-L29 met Tapatalk
First root the phone. Flash the patched recovery_ramdisk.img posted in this thread https://forum.xda-developers.com/mate-20-pro/how-to/guide-manual-updating-firmware-t3893171
Follow the Rooting intructions.
Once you've done that. Go into Magisk Manager and search for MagiskHide Props Config
Download and install it.
Reboot the phone.
Download Terminal Emulator from the google play store
Open it and grant root access by typing su
Run the command 'props'
Then just follow the instructions.
What if I don't want the root. Is it possible to get the ctf error false to fixed without rooting but having bootloader unlocked?
Verstuurd vanaf mijn LYA-L29 met Tapatalk
aygul12345 said:
What if I don't want the root. Is it possible to get the ctf error false to fixed without rooting but having bootloader unlocked?
Verstuurd vanaf mijn LYA-L29 met Tapatalk
Click to expand...
Click to collapse
Not that I know of. I know certain firmwares don't get the error so you could try out a few until you find one that passes safetynet.
eg. for me, I know the .183 passes safetynet without having to change the fingerprint or anything else.
DN38416 said:
First root the phone. Flash the patched recovery_ramdisk.img posted in this thread https://forum.xda-developers.com/mate-20-pro/how-to/guide-manual-updating-firmware-t3893171
Follow the Rooting intructions.
Once you've done that. Go into Magisk Manager and search for MagiskHide Props Config
Download and install it.
Reboot the phone.
Download Terminal Emulator from the google play store
Open it and run the command 'props'
Then just follow the instructions.
Click to expand...
Click to collapse
What am I doing wrong?
I've unlocked bootloader, rooted, installed the module you suggested, rebooted, installed terminal emulator and ran the 'props' command.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
jfenlon01 said:
What am I doing wrong?
I've unlocked bootloader, rooted, installed the module you suggested, rebooted, installed terminal emulator and ran the 'props' command.
Click to expand...
Click to collapse
Did you follow the instructions and change the device fingerprint?
Reboot after that. Check the safetynet in Magisk and it should pass ctsProfile now.
(Unless your BasicIntegrity is also failing then this module won't work)
EDIT: Sorry.. the pic didn't load before.
Hmm... Looks like the module isn't installed properly if you have that error.
are you definitely in rooted state? (Hold volume up as you boot up)
Yep, definitely rooted.
jfenlon01 said:
Yep, definitely rooted.
Click to expand...
Click to collapse
That’s weird. I’m not sure what’s wrong then. I assume you tried rebooting again?
Maybe read through the documentation on the main thread and look in the troubleshooting section? Mine works as soon as I enter the props command.
What version of Magisk are you using? 18.1?
Yeah 18.1, downloaded from this forum. I tried to patch my own with magisk but it wouldn't boot. Still no joy.
jfenlon01 said:
What am I doing wrong?
I've unlocked bootloader, rooted, installed the module you suggested, rebooted, installed terminal emulator and ran the 'props' command.
Click to expand...
Click to collapse
First type "su" to grant root
jfenlon01 said:
Yeah 18.1, downloaded from this forum. I tried to patch my own with magisk but it wouldn't boot. Still no joy.
Click to expand...
Click to collapse
I noticed this in the documentation in the thread.
"MagiskHide Props Config v2.7.2 and earlier versions won't work on Magisk v18.1-d73127b1(18006) or later, due to internal changes in Magisk."
Does that apply to your situation?
Th3PorTuGa said:
First type "su" to grant root
Click to expand...
Click to collapse
OMG I can't believe I forgot about that. Yeah make sure it has root access first sorry. Typing su will bring up the prompt to grant root access. You might need to have Magisk Manager running in the background.
DN38416 said:
I noticed this in the documentation in the thread.
"MagiskHide Props Config v2.7.2 and earlier versions won't work on Magisk v18.1-d73127b1(18006) or later, due to internal changes in Magisk."
Does that apply to your situation?
Click to expand...
Click to collapse
I tried su already guys, it's in the first screenshot.
Also magisk props config v3.5.0 so that from the documentation shouldn't apply either.
Thanks for trying to help.
jfenlon01 said:
I tried su already guys, it's in the first screenshot.
Also magisk props config v3.5.0 so that from the documentation shouldn't apply either.
Thanks for trying to help.
Click to expand...
Click to collapse
do it again and make sure Magisk manager is running beforehand
Close both apps and start again. Open Magisk Manager, then open Terminal Emulator and type su, it should then come up with the prompt to grant root access.
Once it's granted THEN you can run the 'props' command
I tried also 'props' with the ' in case that's what was required. Just can't get it to work.
[edit]
I'm thinking it's because I didn't have the Magisk Busybox module by osm0sis, installing that and will try again.
---------- Post added at 02:48 PM ---------- Previous post was at 02:34 PM ----------
Still no joy
That’s strange. Not sure what’s wrong.
I’m outa ideas. Have you tried uninstalling and reinstalling MagiskHide props module?
DN38416 said:
That’s strange. Not sure what’s wrong.
I’m outa ideas. Have you tried uninstalling and reinstalling MagiskHide props module?
Click to expand...
Click to collapse
Yep, tried that twice. Most recently after installing Magisk Busybox.
Thanks for trying to help.
I'm getting the same issue unfortunately, no idea why "props" isn't found
Will I be able to run banking apps?
Sent from my LYA-L09 using Tapatalk
Attached is a reasonably simple script which disables (or enables) a number of services for application analytics, application measurement, facebook ads, firebase performance monitoring and a few more. The amount of services disabled depends on the applications which you have installed. In my case 430+ services were disabled when running the script. This will increase security and possibly improve battery life a bit.
You must be rooted to use the script. The script code is pretty simple, have a look.
Download the attached file, rename and remove the ".txt" extension.
Instructions to install/use:
Code:
# push the script to your phone using adb
> adb push dss /sdcard/
# go onto your phone
> adb shell
# switch to root
% su
# mount /system as read-write
% mount -o remount,rw /system
# copy the script to the /system/bin/ directory
% cp /sdcard/script /system/bin/
# make sure it is executable
% chmod 755 /system/bin/dss
# execute the script
% dss disable
# output printed to the screen
% reboot
To enable the services again just run the script with argument "enable".
Alternatively, flash the attached magisk module from within the Magisk app. It will achieve the same effect.
Note that the magisk module will run for quite some time in the background whilst your phone is already fully booted.
To check what the module is doing, do:
Code:
> adb shell
% su
% tail -f /data/adb/modules/dss/log
When it has finished you will see "-- done" in the log.
Welkom :good:
I suggest to make a magisk module of this script to make it user friendly.
Keep up the good work old friend
Great to see you again, good idea to make it into a module. Will look at it tomorrow.
Good to see! Look forward to the module, Cheers
Can't you just run the script using EXKM?
For the ones who want to see if you have any of those apps (basically see if you need it/ if the custom kernel or Magisk module already hasn't disabled them).
Run this in Minimal ADB or whichever ADB tool you prefer:
Bash:
- adb shell
- su
- PLIST=`/system/bin/cmd package list packages | grep -v Swift | sort | sed 's/package://g'`
for i in $PLIST; do
echo "$i"
done
This will list all packages you've installed, see if it has any of the packages mentioned above.
OK, I looked into making this a magisk module ...
Problem is that you only have to run the script once (with disable).
So it is not really something which needs to run upon every boot.
Therefore, a magisk module is a bit pointless IMHO.
Anyway, the magisk module is attached if you want to try it.
@foobar66
Is this safe to try on the 6T?
..Cory.. said:
@foobar66
Is this safe to try on the 6T?
Click to expand...
Click to collapse
Yes, no problem.
foobar66 said:
Yes, no problem.
Click to expand...
Click to collapse
Thanks brother, will try shortly!
can anyone report their findings on this? does it improve things?
best way to know is try it make backup to feel safe
So I just need to flash magisk module, reboot so it will be activated and then I can remove it?
I do not know if it improve anything but i had to reboot twice. After the first reboot nothing worked as expected. Now it seems to work normal
Updated OP with the magisk module.
Thanks a LOT - very good addition to AFWall
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------- Post added at 20:38 ---------- Previous post was at 20:29 ----------
foobar66 said:
OK, I looked into making this a magisk module ...
Problem is that you only have to run the script once (with disable).
So it is not really something which needs to run upon every boot.
Therefore, a magisk module is a bit pointless IMHO.
Anyway, the magisk module is attached if you want to try it.
Click to expand...
Click to collapse
Well, can I just delete the Magisk module after running it once?
---------- Post added at 20:56 ---------- Previous post was at 20:38 ----------
ATTENTION ANDROID 10 Users: not working on Q-Beta 4
does this play nice if I have oxytweaker module which already disables some of the logging and analytic stuff?
Thanks. Look forward to trying this. If we want to reverse the module do we just delete it from Magisk? Thanks
carro_d said:
does this play nice if I have oxytweaker module which already disables some of the logging and analytic stuff?
Click to expand...
Click to collapse
i would say it does the same, its just another approach
and oxytweaker also changes some build prop stuff, so this is like the "light" version, thats focussed on the analytic stuff
Would this break safety net? Thanks!
Please see the posted screenshot image for the problem. I just got a brand new OnePlus 8 Pro today, updated the firmware (it's current and running Android 11), unlocked the bootloader, installed my data, and rooted it. Since there is no TWRP for Android 11 for this device, I had to manually extract the current boot.img and patch it myself with Magisk Manager to root this device.
On the first boot after root, I launched Magisk Manager. The countdown timer was so fast, I did not have a chance to grant Magisk Manager root permissions. Now Magisk Manager is being denied Superuser permissions, and there are no buttons at the bottom of Magisk Manager to set Magisk Hide settings or set what apps are allowed Superuser/root.
I have googled as well as searched this forum for relevant help, and have found nothing helpful (really, I may have missed something, but I did try). How can I reset the apps allowed root permissions so that I can grant Magisk Manager the Superuser permissions it needs to function?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any help is greatly appreciated!
I already tried force stopping Magisk Manager and clearing the storage for Magisk Manager (which did nothing to solve the problem).
https://www.didgeridoohan.com/magisk/Magisk#hn_Magisk_Manager_was_denied_superuser_access
Didgeridoohan said:
https://www.didgeridoohan.com/magisk/Magisk#hn_Magisk_Manager_was_denied_superuser_access
Click to expand...
Click to collapse
Thank you for the reply. I found this article earlier (or a variant of it), and it does not appear to solve the issue. I don't have two different Magisk Managers installed. I just accidently denied the one Superuser access by not granting it Superuser access quickly enough.
The Magisk app does not need to ask for superuser access. It is the one that grants it... In other words, one way or the other Magisk is looking for a hidden Magisk app with a package name that doesn't match the one you're using.
Try deleting /data/adb/magisk.db. It'll reset everything (including granted superuser requests, etc) and you can reinstall the app and start over.
Didgeridoohan said:
The Magisk app does not need to ask for superuser access. It is the one that grants it... In other words, one way or the other Magisk is looking for a hidden Magisk app with a package name that doesn't match the one you're using.
Try deleting /data/adb/magisk.db. It'll reset everything (including granted superuser requests, etc) and you can reinstall the app and start over.
Click to expand...
Click to collapse
Thank you. This is no longer an issue (I have a new issue that is unrelated to this thread, so I'll search for the solution to it).
chriv said:
Thank you. This is no longer an issue (I have a new issue that is unrelated to this thread, so I'll search for the solution to it).
Click to expand...
Click to collapse
Just out of curiosity, did you solve it be deleting the database file?
Didgeridoohan said:
Just out of curiosity, did you solve it be deleting the database file?
Click to expand...
Click to collapse
I wish I could say, yes, but no. Long story short, I started over from a clean phone install. Unfortunately, (this part is off topic), I accidently upgraded to 11.0.4.4.IN11AA with an OTA after starting over (the version almost nobody has yet), didn't realize it, and patched a stock 11.0.2.2.IN11AA boot.img and flashed it to the boot partition. Magisk and root worked great, but WiFi and phone calls were broken. Now I'm stuck waiting to get the 11.0.4.4.IN11AA full package (Global/NA/US version of 11.0.4.4) to fix everything (by extracting the boot.img from a payload dumper).
So you mean that deleting the database file didn't work, or that you never tried it?
Sorry if I was unclear. I didn't try it. My phone was already in a state where I could not try it (and this no longer applied) before I saw this message. I am very grateful for the assistance/information.
I have the same problem. can you help me?
kas001 said:
I have the same problem. can you help me?
Click to expand...
Click to collapse
Have you already checked to see if this is the cause? https://www.didgeridoohan.com/magisk/Magisk#hn_Magisk_Manager_was_denied_superuser_access. It's definitely the best starting point.
Just for anyone else finding this thread having this issue and forgetting they told Magisk to change it's APK name to stay hidden like I did. Look for a second "Settings" app on your phone. That's what Magisk changes itself to.
SparJar said:
Just for anyone else finding this thread having this issue and forgetting they told Magisk to change it's APK name to stay hidden like I did. Look for a second "Settings" app on your phone. That's what Magisk changes itself to.
Click to expand...
Click to collapse
Yeah, I did forgot that I have changed magisk name to "settings" and magisk is working fine right now.
aleep123 said:
Yeah, I did forgot that I have changed magisk name to "settings" and magisk is working fine right now.
Click to expand...
Click to collapse
Can you please explain?
ivanov_16 said:
Can you please explain?
Click to expand...
Click to collapse
There's a setting in the Magisk app where you can rename it with a random package name, to hide it and make the app harder to detect. This will give it a generic Android icon and give it the same "Settings" (previously it would name the repackaged app "Manager").
OK I missed the prompt to grant access to the ADB shell. Where's the settings for all the applications permission grants? So that I can untick the "deny" for ADB shell. I've changed the setting from prompt to grant, and tried again. But the toast just says Shell denied superuser access.
Thanks.
--Chris
EDIT:
OK I just installed a terminal app and nuked
/data/adb/magisk/magisk.db
which allowed me to start the permission process over.
This sure seems like a brutal approach to grant/permission management. It also requires starting the whole process from scratch.
SparJar said:
Just for anyone else finding this thread having this issue and forgetting they told Magisk to change it's APK name to stay hidden like I did. Look for a second "Settings" app on your phone. That's what Magisk changes itself to.
Click to expand...
Click to collapse
You are a superstar!! I have been tearing my hair out for acouple of days now trying to work out why i could not reinstall magisk, this was exactly the solution to the problem i was facing, therefore i give you my gratitude.
I have the same issues after updating to v24.1 how can I Access to delete the duplicate apps of Magisk. It was naming to Settings.
After the 25206
Didgeridoohan said:
So you mean that deleting the database file didn't work, or that you never tried it?
Click to expand...
Click to collapse
I on the other hand tried it. Not sure if it works or not. After the 25206 to 25207 disaster, 25208 is finally normal except it can't hide itself anymore. Any solutions there? Many thanks. F Droid file explorer/Network Signal Guru also lost super user rights. Rootchecker now says it's not properly rooted
I tried deleting /data/adb/magisk/magisk.db with Termux but can't even access it as I get "permission denied" and am still seeing SuperUser and Modules greyed out. Tried sudo, was prompted to install 'tsu' package and it failed as it appears the host no longer exists