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!
Related
Anyone's Google Play Services update recently? If you're suddenly experiencing dreadful battery life due to Google Play Services (see pic below) then this fix might be right for you.
Background: Recently, an update to Google Play Services (ver. 7.0.97) was released and reports flooded the internet with complaints of battery life issues. People had battery graphs similar to this:
{
"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"
}
I also experienced this issue. After checking my frequency tables in my kernel tweaker, I noticed that my phone was NEVER going into Deep Sleep, and, instead, was sitting at 300mhz even when the screen was off. After some Googling and reading some comments on GitHub, it seemed apparent that the problem was one Service in particular "SystemUpdateService".
The Problem: Without going into much detail SystemUpdateService is basically Google's OTA update service, and when it detects that your phone need and update while running a Custom ROM, it fails and re-runs this check over and over again. It's this wakelock that drains your battery.
The Solution: Enabling the service. You read that correctly. For whatever reason, enabling the service actually prevents the wakelock from occurring. I, along with a few testers, have been using our phones for hours now after having run the script and the wakelock and battery drain is completely gone.
Method #1: init.d Script
For those of you with custom ROMs that support init.d scripts, simply unzip and place this script in the /etc/init.d folder (as root) and set permissions to 755. The service becomes disabled again as soon as the phone reboots. We place this script in the init.d folder so the script runs automatically every time the phone boots. If your Custom ROM does NOT support init.d scripts skip over to Method #2 or 3.
DOWNLOAD SCRIPT HERE: View attachment fixUpdateService.zip
Permissions Screenshot:
The source code to this script (Edited slightly, Credit to Oreganoian on Reddit):
Code:
echo "Disabling SystemUpdateService Battery Drain"
su -c pm enable com.google.android.gms/.update.SystemUpdateActivity
su -c pm enable com.google.android.gms/.update.SystemUpdateService
su -c pm enable com.google.android.gms/.update.SystemUpdateService$ActiveReceiver
su -c pm enable com.google.android.gms/.update.SystemUpdateService$Receiver
su -c pm enable com.google.android.gms/.update.SystemUpdateService$SecretCodeReceiver
su -c pm enable com.google.android.gsf/.update.SystemUpdateActivity
su -c pm enable com.google.android.gsf/.update.SystemUpdatePanoActivity
su -c pm enable com.google.android.gsf/.update.SystemUpdateService
su -c pm enable com.google.android.gsf/.update.SystemUpdateService$Receiver
su -c pm enable com.google.android.gsf/.update.SystemUpdateService$SecretCodeReceiver
echo "Script Execution Successful"
Method #2: Manually Running the Script
This method works best if you like working in the terminal or file explorer. Or if you would rather just do things yourself. Place the script above in the /etc/init.d directory and set permissions to 755. This time, however, you must run the script yourself EVERY TIME THE PHONE BOOTS. You can do this by using your file explorer, if it supports executing scripts (see output below) or running the script via Terminal.
Terminal: Run this command as root (type "su" and hit enter):
Code:
./etc/init.d/fixUpdateService.sh
File Explorer: I personally use FX (File Explorer), which is a wonderful app by the way, so the output in the screenshot below may be styled different but generally should appear the same:
Method #3: Enabling SystemUpdateService via App
Now, if you're a no frills kinda person, or just don't feel comfortable rummaging around in your filesystem or terminal, there is an app you can download called Disable Service which lets you do the same thing, just with a nice GUI. YOU MUST DO THIS EVERY TIME YOU REBOOT YOUR PHONE.
Steps:
Once installed, launch the app.
Then click the "System" tab on the top right.
Scroll down and select "Google Play services"
Scroll down to "SystemUpdateService" and CHECK the box.
Done!
There you have it! Hope this helps!
Great!
Method 1 doesn't work on hammerheadcaf 20150318 but Method 3 is working like a charm and the battery drain issue seems to be gone!
And CyanogenMod is going to deal with this issue before long:
http://review.cyanogenmod.org/#/c/91579/
http://review.cyanogenmod.org/#/c/91021/
Hello...
This only occurs in custom roms or it happens also in Stock Rom?
Thank you...
blackzigong said:
Great!
Method 1 doesn't work on hammerheadcaf 20150318 but Method 3 is working like a charm and the battery drain issue seems to be gone!
And CyanogenMod is going to deal with this issue before long:
http://review.cyanogenmod.org/#/c/91579/
http://review.cyanogenmod.org/#/c/91021/
Click to expand...
Click to collapse
Interesting, I'll try to see if I can edit the script to get it to work right. Make sure you enable the service with that app every time you reboot your phone.
Also, I've been reading those CyanogenMod discussions. Very interesting. Hopefully they tackle the issue soon and the solution makes its way into other ROMs
Kc_Nirvana said:
Hello...
This only occurs in custom roms or it happens also in Stock Rom?
Thank you...
Click to expand...
Click to collapse
As far as I know, this bug only affects custom ROMs.
Method 1 didn't work but method 2 and 3 worked. I believe the permissions for the script
should be 755 instead of 744.
Update : changing permissions didn't help either.
755 or 744? Screenshot shows 744 but instructions say 755. Assuming 744 is correct.
soundneedle said:
755 or 744? Screenshot shows 744 but instructions say 755. Assuming 744 is correct.
Click to expand...
Click to collapse
Permissions for init.d scripts should;d be 755. I'll update the picture to reflect that. Thank you for pointing that out.
Kc_Nirvana said:
Hello...
This only occurs in custom roms or it happens also in Stock Rom?
Thank you...
Click to expand...
Click to collapse
I'm experiencing the battery drain with stock HTC sense on my M8 and GP services 7.0.97. The battery usage is very high for GP services (e.g. 38% for screen off!) and the "awake" bar shows the phone awake even during periods of low usage--too many awake intervals.
Will init.d scripts work on CM11s?
CM fixed this a couple days ago with 2 commits. Hopefully all the ROM teams will incorporate it into their builds.
http://review.cyanogenmod.org/#/c/91579/
http://review.cyanogenmod.org/#/c/91021/
AndrasLOHF said:
CM fixed this a couple days ago with 2 commits. Hopefully all the ROM teams will incorporate it into their builds.
Click to expand...
Click to collapse
CM11s may not get another update though. I can confirm that the shell script doesn't work at startup on CM11S.
Edit: sorry didnt realise this was posted in the Nexus 5 section
Does this also effect cm11s?
Pretty important to add that for that 3rd Method to work you also have to enable that same SystemUpdateService in Google Services Framework. (In addition to enabling it in Google Play Services).
At least, that's what I've read on other posts/Google+ pages. I'm trying it now so do this at your own risk =)
Thanks for the script. Works for me, but only manually. I can't get it to work in the init.d at startup. It's in the folder, permissions 755. I'm not that into scripts - anyone who got it working mind for some tips?
humba80 said:
Thanks for the script. Works for me, but only manually. I can't get it to work in the init.d at startup. It's in the folder, permissions 755. I'm not that into scripts - anyone who got it working mind for some tips?
Click to expand...
Click to collapse
Your ROM may not support init.d. Mine doesn't and so I'm using tasker to run the script at boot.
Sandman-007 said:
Your ROM may not support init.d. Mine doesn't and so I'm using tasker to run the script at boot.
Click to expand...
Click to collapse
Tasker! Didn't think of it. Thank you!
Script works for me, but it doesn't solve battery drain: I have to use privacy guard to remove both keep awake and wake up...
Why you try these hard to stop the Systemupdate Wakelock??
See my guide here.Its simple as you like.No scripts included:http://forum.xda-developers.com/showthread.php?t=3060548
This is a permanent fix.No need to redo after reboots
vaisakh7 said:
Why you try these hard to stop the Systemupdate Wakelock??
See my guide here.Its simple as you like.No scripts included:http://forum.xda-developers.com/showthread.php?t=3060548
This is a permanent fix.No need to redo after reboots
Click to expand...
Click to collapse
Yup, but checking after the script mod, only keep awake permission was denied and I still got more than 8000 wake locks
gpvecchi said:
Yup, but checking after the script mod, only keep awake permission was denied and I still got more than 8000 wake locks
Click to expand...
Click to collapse
Did you try my fix?
I've attached screenshots there.
Tapped from my furious ZR
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
{
"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 everyone, I made a simple module for my own needs and I figured I'd share it here as well.
This module enables "insecure adbd" on Pixel devices, which allows you to restart adbd in root mode via "adb root" and push/pull to/from the /data partition among other things.
Note it was only tested on latest stock Pie with November security patches on a Pixel 2 XL, but I took a look at the Pie images of other Pixel devices and it should work for them too. No guarantees about other devices, although if "adbd" is located in /system/bin (the actual binary, not the symlink) rather than in /sbin, it's an arm64 device and it runs Pie, chances are it'll work.
If anyone is curious about how it works, it replaces /system/bin/adbd systemlessly with one from an userdebug AOSP ROM, modified to remove the check for ro.debuggable (as that would be bad for SafetyNet passing) and to use magisk's SELinux context, and it adds sepolicy rules for adbd taken from the AOSP source to make it actually work on stock.
Download:
View attachment insecureadbdv2.zip
View attachment 0001-Insecure-adbd-stuff.patch
You should remove /system/bin/adbd from the replace list in config.sh. That list is used to remove directories systemlessly, not replace files with the ones already in the module... Details here: https://topjohnwu.github.io/Magisk/guides.html#remove-folders
Didgeridoohan said:
You should remove /system/bin/adbd from the replace list in config.sh. That list is used to remove directories systemlessly, not replace files with the ones already in the module... Details here: https://topjohnwu.github.io/Magisk/guides.html#remove-folders
Click to expand...
Click to collapse
Fixed, I also realized the SELinux setup wasn't anywhere near complete (adb install wouldn't work, etc), and rather than hunting down all the changes necessary to make u:r:su:s0 workable with root I modified adbd to use u:r:magisk:s0 which is already setup by Magisk for use with root and I compiled it from latest AOSP, and I removed all u:r:su:s0 rules. Works flawlessly now.
Curious to try
Phoenix Wright said:
Hi everyone, I made a simple module for my own needs and I figured I'd share it here as well.
This module enables "insecure adbd" on Pixel devices, which allows you to restart adbd in root mode via "adb root" and push/pull to/from the /data partition among other things.
Note it was only tested on latest stock Pie with November security patches on a Pixel 2 XL, but I took a look at the Pie images of other Pixel devices and it should work for them too. No guarantees about other devices, although if "adbd" is located in /system/bin (the actual binary, not the symlink) rather than in /sbin, it's an arm64 device and it runs Pie, chances are it'll work.
If anyone is curious about how it works, it replaces /system/bin/adbd systemlessly with one from an userdebug AOSP ROM, modified to remove the check for ro.debuggable (as that would be bad for SafetyNet passing) and to use magisk's SELinux context, and it adds sepolicy rules for adbd taken from the AOSP source to make it actually work on stock.
Download:
View attachment 4650649
Click to expand...
Click to collapse
This work for OnePlus 6? Or be editable?
I'm magisk rooted, just no adb insecure,
Have even decompiled the kernel, made prop edits.
Tried chainfire insecure method (decompile app, use 17.png as adb) both fail.
Build.prop loads correct edits on boot. No adb root :-/
Figured this would be an easy edit as I already have root... Maybe I'm missing something simple
Yamaha169 said:
This work for OnePlus 6? Or be editable?
I'm magisk rooted, just no adb insecure,
Have even decompiled the kernel, made prop edits.
Tried chainfire insecure method (decompile app, use 17.png as adb) both fail.
Build.prop loads correct edits on boot. No adb root :-/
Figured this would be an easy edit as I already have root... Maybe I'm missing something simple
Click to expand...
Click to collapse
If /system/bin/adbd is a binary and not a symbolic link I'd try it. You need to be on Pie of course.
As an explanation, to get adb "insecure" to work you need a few things:
- an "adbd" binary from an "userdebug" build of AOSP (stock roms are "user" builds) for your Android version/CPU architecture. There's no way around this, "user" builds of adbd lack the necessary code. This module has a Pie userdebug adbd for aarch64 SoCs (so you should be fine on Pie as I said).
- ro.debuggable set to 1 or adbd will say that "adb root can't be used on production builds". This check was removed from the adbd binary I compiled because it messes up Safetynet, so it doesn't care about ro.debuggable.
- adbd needs to have a SELinux context that's appropriate for root. Clean adbd uses "u:r:su:s0" which is correctly configured in SELinux in userdebug builds. However, configuring it on user builds is a chore, but as it turns out we already have a SELinux context that's good for root execution with magisk, aka u:r:magisk:s0. So I changed the adbd code to transition to u:r:magisk:s0. I also have a post-fs-data script that grants adbd permission to transition to that context.
Phoenix Wright said:
If /system/bin/adbd is a binary and not a symbolic link I'd try it. You need to be on Pie of course.
As an explanation, to get adb "insecure" to work you need a few things:
- an "adbd" binary from an "userdebug" build of AOSP (stock roms are "user" builds) for your Android version/CPU architecture. There's no way around this, "user" builds of adbd lack the necessary code. This module has a Pie userdebug adbd for aarch64 SoCs (so you should be fine on Pie as I said).
- ro.debuggable set to 1 or adbd will say that "adb root can't be used on production builds". This check was removed from the adbd binary I compiled because it messes up Safetynet, so it doesn't care about ro.debuggable.
- adbd needs to have a SELinux context that's appropriate for root. Clean adbd uses "u:r:su:s0" which is correctly configured in SELinux in userdebug builds. However, configuring it on user builds is a chore, but as it turns out we already have a SELinux context that's good for root execution with magisk, aka u:r:magisk:s0. So I changed the adbd code to transition to u:r:magisk:s0. I also have a post-fs-data script that grants adbd permission to transition to that context.
Click to expand...
Click to collapse
the file you reffer in system/bin is a real .BIN no symlinks.
so i will try this method report back
---------- Post added at 07:22 PM ---------- Previous post was at 07:08 PM ----------
Phoenix Wright said:
Hi everyone, I made a simple module for my own needs and I figured I'd share it here as well.
This module enables "insecure adbd" on Pixel devices, which allows you to restart adbd in root mode via "adb root" and push/pull to/from the /data partition among other things.
Note it was only tested on latest stock Pie with November security patches on a Pixel 2 XL, but I took a look at the Pie images of other Pixel devices and it should work for them too. No guarantees about other devices, although if "adbd" is located in /system/bin (the actual binary, not the symlink) rather than in /sbin, it's an arm64 device and it runs Pie, chances are it'll work.
If anyone is curious about how it works, it replaces /system/bin/adbd systemlessly with one from an userdebug AOSP ROM, modified to remove the check for ro.debuggable (as that would be bad for SafetyNet passing) and to use magisk's SELinux context, and it adds sepolicy rules for adbd taken from the AOSP source to make it actually work on stock.
Download:
View attachment 4650649
Click to expand...
Click to collapse
Which partition is this script dealing with?
Ill do backup and test.
(Systemless kinda rules out /system)
Yamaha169 said:
the file you reffer in system/bin is a real .BIN no symlinks.
so i will try this method report back
---------- Post added at 07:22 PM ---------- Previous post was at 07:08 PM ----------
Which partition is this script dealing with?
Ill do backup and test.
(Systemless kinda rules out /system)
Click to expand...
Click to collapse
It uses magisk to replace adbd without actually changing /system
South
Phoenix Wright said:
It uses magisk to replace adbd without actually changing /system
Click to expand...
Click to collapse
Shouldn't crash me... But say it does...
I'm guessing this similar to a init.D script through magisk?
Reflash magisk if crash to fix ?
Or find your script in. ?? /sbin/.magisk/img/.core/post-fs-data.d
Delete from folder?
Srry I'm away for next 20. But I will try it .. have twrp backups too already...
Just want know what I'm flashing to fix easiest
---------- Post added at 07:46 PM ---------- Previous post was at 07:40 PM ----------
Also, these are both real files.... Hmmm... Messed up symlink in recovery?
{
"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"
}
Vs /bin
My worry
Yamaha169 said:
Shouldn't crash me... But say it does...
I'm guessing this similar to a init.D script through magisk?
Reflash magisk if crash to fix ?
Or find your script in. ?? /sbin/.magisk/img/.core/post-fs-data.d
Delete from folder?
Srry I'm away for next 20. But I will try it .. have twrp backups too already...
Just want know what I'm flashing to fix easiest
Click to expand...
Click to collapse
Deleting /data/adb/magisk.img from TWRP should do
Yamaha169 said:
Shouldn't crash me... But say it does...
I'm guessing this similar to a init.D script through magisk?
Reflash magisk if crash to fix ?
Or find your script in. ?? /sbin/.magisk/img/.core/post-fs-data.d
Delete from folder?
Srry I'm away for next 20. But I will try it .. have twrp backups too already...
Just want know what I'm flashing to fix easiest
---------- Post added at 07:46 PM ---------- Previous post was at 07:40 PM ----------
Also, these are both real files.... Hmmm... Messed up symlink in recovery?
Vs /bin
My worry
Click to expand...
Click to collapse
It's a real file.
I know this is from 2018, but your module works on my LG V40 on Android Pie! Thank you for making such a useful tool! Magisk too? I REALLY appreciate you making this!
I'm having a hard time finding a version of adbd which is ARM 32-bit, but 64-bit won't work on my device. Any ideas?
Rooted my phone (Galaxy S21 Ultra) recently, used Magisk, it seems to be working ok (ver. 25.1), although initially it seemed I couldn't install Modules from outside the app. I am unable to pass SafetyNet. Super User authorizations working fine.
After some helping from others and plenty of research, I installed Fox MMM and was able to install two modules. Now it seems I can't install modules from storage because the files themselves aren't being recognized as proper modules.
As you can see in this image, the icon itself is different from the ones recognized although they are all *.zip files. Safetynet and Shamiko are greyed out, while MagiskHide and Liboencrypt aren't - these two I can and did install.
Initially I thought it could be something to do with names, as the latter have underscores instead of dashes, but renaming them didn't work.
Neither Magisk nor Fox MMM recognize these files as modules, and they were all downloaded from GitHub.
I'm really stumped by this.
What could I do?
-- This is the image in the link, for easier access:
{
"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"
}
If the modules are correct then you can try this:
adb shell > su
magisk --install-module module.zip
If this returns error then post screenshot here.
NextGenMagisk said:
If the modules are correct then you can try this:
adb shell > su
magisk --install-module module.zip
If this returns error then post screenshot here.
Click to expand...
Click to collapse
Where do I type this?
wbane said:
Where do I type this?
Click to expand...
Click to collapse
Any terminal emulator (to skip using the adb shell command), like Termux, OR via ADB on a PC
If someone in the future finds this thread, I've got this solution:
Have you tried using Samsung's file manager? On the top left of your screenshot press the sandwich menu icon and select Samsung's file manager and try to select the module from there.I tried the above and it worked!
NextGenMagisk said:
If the modules are correct then you can try this:
adb shell > su
magisk --install-module module.zip
If this returns error then post screenshot here.
Click to expand...
Click to collapse
I was stuck on Android 13 having "installation failed" message, but running this from the shell worked.
It seems like you're encountering issues with installing modules on your rooted Galaxy S21 Ultra using Magisk. Despite successfully rooting your phone and having Super User authorizations working fine, you're unable to pass SafetyNet. Additionally, you've tried installing modules from storage, but they aren't being recognized as proper modules.