Related
(Found this tool in a youtube description box)
Basically this tool is used to uninstall any bloatware through adb, doesn't requires root access, doesn't block OTAs
Requirements: 1) This Tool - https://goo.gl/6qtRKR 2) ADB : https://forum.xda-developers.com/showthread.php?t=2588979 3) USB DEBUGGING ENABLED 4) ES FILE EXPLORER (optional)
Just after setting up with usb debugging (tapping build number 7 times, going to developer options, enabling usb debugging), connect your phone to pc ensuring that adb setup is installed on your pc. Run the tool, enter the package name (of that apk) (using es file explorer)
Credits: Respected DEVELOPER(S) :good:
Tool doesn't need ADB separately as it is bundled with it.
For those who are suspicious about exe, download the BAT file(command script) from attachment. Place it in ADB folder and run it to get same functionality as the tool.
If we're removing bloat from /system, doesn't that mean we're messing with the ability to flash OTAs as the OTA checks for /system integrity and if it has been modified or not, doesn't it?
Please do correct me if I'm wrong
psychopac said:
If we're removing bloat from /system, doesn't that mean we're messing with the ability to flash OTAs as the OTA checks for /system integrity and if it has been modified or not, doesn't it?
Please do correct me if I'm wrong
Click to expand...
Click to collapse
You are disabling apps. It doesn't affect OTA unless you make the system crash....
Arugakeerthi said:
You are disabling apps. It doesn't affect OTA unless you make the system crash....
Click to expand...
Click to collapse
Disabling or removing because we can also disable apps from the Settings as well but if this is something different, please let me know
psychopac said:
Disabling or removing because we can also disable apps from the Settings as well but if this is something different, please let me know
Click to expand...
Click to collapse
You can disable any app. Even System UI
Well, I have this Moto G5 with LineageOS 16, Magisk 19.3 and TWRP 3.2.3-2-cedric-arm64 and unlocked bootloader.
When I test SafetyNet with Magisk Manager It says to me
SafetyNet check passed
ctsProfile: false
basicIntegrity: false
I have hidden Magisk Manager and changed the device fingerprint with the MagiskHide Props Config (I chosed the Moto G5 7.0 fingerprint)
What should do I do to get them both to true?
Srry for bad english
P.S. I'm having problems with Pokémon GO, this is why I'm doing this
If you flash the magisk uninstall zip and restart the device and run a safetynet check (use a 3rd party app from playstore) does basic integrity pass?
If so try an older version of magisk or try the canary build - if basic integrity still fails and you have tested it again after a clean flash then try a different rom
TheFixItMan said:
If you flash the magisk uninstall zip and restart the device and run a safetynet check (use a 3rd party app from playstore) does basic integrity pass?
If so try an older version of magisk or try the canary build - if basic integrity still fails and you have tested it again after a clean flash then try a different rom
Click to expand...
Click to collapse
I've uninstalled Magisk and checked safety net, it still gives both false.
So I should change rom?
OnionMaster03 said:
I've uninstalled Magisk and checked safety net, it still gives both false.
So I should change rom?
Click to expand...
Click to collapse
If it doesn't pass with a clean flash then yes
OnionMaster03 said:
I've uninstalled Magisk and checked safety net, it still gives both false.
So I should change rom?
Click to expand...
Click to collapse
Los16 doesn't support safetynet on our device, you can use the magisk safetynet Modul that fixed your problem.
OnionMaster03 said:
Well, I have this Moto G5 with LineageOS 16, Magisk 19.3 and TWRP 3.2.3-2-cedric-arm64 and unlocked bootloader.
When I test SafetyNet with Magisk Manager It says to me
SafetyNet check passed
ctsProfile: false
basicIntegrity: false
I have hidden Magisk Manager and changed the device fingerprint with the MagiskHide Props Config (I chosed the Moto G5 7.0 fingerprint)
What should do I do to get them both to true?
Srry for bad english
P.S. I'm having problems with Pokémon GO, this is why I'm doing this
Click to expand...
Click to collapse
I had the same problem, the ONLY thing that worked was installing the Magisk module "SafetyNet Fix" (you can find it the "Downloads" section of Magisk). The issue with that is that it creates a conflict with the "key" so you can an error message every time you start your phone, but you can ignore/clear it.
Tiki Thorsen said:
I had the same problem, the ONLY thing that worked was installing the Magisk module "SafetyNet Fix" (you can find it the "Downloads" section of Magisk). The issue with that is that it creates a conflict with the "key" so you can an error message every time you start your phone, but you can ignore/clear it.
Click to expand...
Click to collapse
If you try copying the fingerprint key from the system build.prop into the vendor build.prop replacing the existing value it should solve that issue
Not tried it as don't own device
Tiki Thorsen said:
I had the same problem, the ONLY thing that worked was installing the Magisk module "SafetyNet Fix" (you can find it the "Downloads" section of Magisk). The issue with that is that it creates a conflict with the "key" so you can an error message every time you start your phone, but you can ignore/clear it.
Click to expand...
Click to collapse
I have the same problem. When I install SafetyPatch, the phone hangs in an bootloop.
I choose pixel 2xl fingerprint. Its working fine for me
Attached is a (simple) Magisk module which allows you to disable:
- app measurement
- app analytics
- app firebase tracking
- app crashlytics
In short, each APK (system app or user app) may have background services to do all sorts of tracking and ad handling. Module allows you to disable (or enable) those services.
You must obviously be rooted and have a working Magisk.
How to install:
Code:
a) download attached zip file
b) push the zip file to your /sdcard folder (use: adb push dss.zip /sdcard)
c) open Magisk
d) in the panel at the bottom, tap the "modules" icon
e) at the top, select "install downloaded module"
f) navigate to your /sdcard folder
g) select dss.zip
h) tap the reboot button
After installation:
The script must be run manually using the command line. First, open a shell using adb:
Code:
> adb shell
$ su
#
The script has the following syntax:
Code:
dss {disable|enable} {user|system} <package-name>
You must provide 2 or 3 arguments to the script:
a) first argument is "disable" or "enable" (by default Analytics/Firebase/etc services are enabled)
b) second argument is "user" or "system" (use "user" for any app wich you installed using an APK or installed from play store; use "system" for apps which come as part of the official Google image, e.g. contacts/dialer/messaging)
c) the third argument is optional and - if present - contains the name of a specific package (e.g. com.banking.mybankapp)
Examples:
1) disable analytics/firebase/etc for ALL user apps
Code:
# dss disable user
2) enable analytics/firebase/etc for ALL system apps (this is the default)
Code:
# dss enable system
3) disable analytics/firebase/etc for Feedly
Code:
# dss disable user com.devhd.feedly
The script will show you output of the services which get disabled, for example for the Feedly case:
Code:
Component {com.devhd.feedly/com.facebook.internal.FacebookInitProvider} new state: disabled
Component {com.devhd.feedly/com.google.android.gms.analytics.AnalyticsJobService} new state: disabled
Component {com.devhd.feedly/com.google.android.gms.analytics.AnalyticsReceiver} new state: disabled
Component {com.devhd.feedly/com.google.android.gms.analytics.AnalyticsService} new state: disabled
Occasionally it can happen that after disabling Analytics/Firebase/etc, the app no longer works. Then just "enable" again. Apps should - in principle - be resilient but some are not coded properly. Alternatively, you can try to figure out exactly which of the services causes the crash and (manuall) re-enable that service (but you will need to look into the source code a bit). When you run this on Feedly for example, you will find that it crashes afterwards (reason is that the script disabled com.devhd.feedly/com.facebook.internal.FacebookInitProvider). You can re-enable that service individually using:
Code:
pm enable com.devhd.feedly/com.facebook.internal.FacebookInitProvider
or just do:
Code:
# dss enable user com.devhd.feedly
(that will re-enable all the services previously disabled)
You can also disable stuff for system apps, e.g. com.android.contacts (Contacts), com.android.vending (Play store app), etc ...
However, one BIG WARNING. If you disable this for system apps, make sure to re-run the script with the 'enable system' argument BEFORE running a Play-systemupdate otherwise that may bootloop. So, to be on the safe side, if you have used the script to disable services in system APKs, then run:
Code:
# dss enable system
before doing the Play-systemupdate.
I you want to check the source code (simple sh script), just unzip the dss.zip in a new directory and check out the file system/bin/dss. It's not complicated ...
This will save you (a tiny litte bit) of battery, but more importantly, a lot of nasty "tracking" (which you don't need).
Changes are persistent across reboots.
github: https://github.com/foobar66/dss
Notes:
When I run this for the user apps on my phone, I have ~189 background services that get disabled.
If you want to know more about firebase, look here: https://firebase.google.com/
And here is some detail about app analytics: https://developers.google.com/analytics/devguides/collection/android/v4
If you want to know the name of your APKs/packages, do:
Code:
# pm list packages -f
Looks like a brillant tool, I'll test it, thanks a lot for this very user-friendly and efficient tool!
Yes brilliant tool thanks for this!
I'll third, I run this on my device at the moment on user apps. Great tool and does what it says it will do. Thank you for this!
Great tool.
Thanks for the effort and sharing.
Great share
wow, thanks OP
I did disable analytics/firebase/etc for ALL user apps and scrolling facebook on Chrome no longer jittery.
Flashed and disabled analytics on ProtonAOSP. Thank you for the tool.
This would be great on the Pixel 5
207 user packages got disabled.
Do I have to also run "dss enable system" after the initial "dss disable user"?
Will I have to re-run this after an app updates?
Will I have to re-run this after a monthly android update?
Really useful tool, mate! Will be trying on my device once I get Magisk to work.
Utini said:
207 user packages got disabled.
Do I have to also run "dss enable system" after the initial "dss disable user"?
Will I have to re-run this after an app updates?
Will I have to re-run this after a monthly android update?
Click to expand...
Click to collapse
Also:
You should implement that the module saves the output of the disabled packages.
That way you can easily (and safer) restore those packages e.g. when uninstalling the module?
Same goes for all your other modules:
They tinker with the system but how can I safely restore the original form and uninstall the module?
Utini said:
Also:
You should implement that the module saves the output of the disabled packages.
That way you can easily (and safer) restore those packages e.g. when uninstalling the module?
Same goes for all your other modules:
They tinker with the system but how can I safely restore the original form and uninstall the module?
Click to expand...
Click to collapse
Well, as this is commandline based its basically all there in OP
BTW saving the output is easy, just expand the commandline by "> filename.log" (without the "")
And the safe way back before uninstalling is just dss enable user / dss enable system
s3axel said:
Well, as this is commandline based its basically all there in OP
BTW saving the output is easy, just expand the commandline by "> filename.log" (without the "")
And the safe way back before uninstalling is just dss enable user / dss enable system
Click to expand...
Click to collapse
What I was trying to say is that the module should use the output for when restoring / enabling.
If you have looked at the source code of the module, then you will see that it basically works by creating an array of queried packages to disable/enable. I could imagine that due to what ever fault / later update / package changes / ... the "enable query" might look different than the "disable query" that was run months before. Meaning that there is a chance that not everything that got disabled will get enabled again.
Looks amazing so far, not just for Pixel 6 but good for other phones too
Utini said:
207 user packages got disabled.
Do I have to also run "dss enable system" after the initial "dss disable user"?
Will I have to re-run this after an app updates?
Will I have to re-run this after a monthly android update?
Click to expand...
Click to collapse
1. No, your own choice if you want to disable the services for system packages
2. No
3. No
Utini said:
What I was trying to say is that the module should use the output for when restoring / enabling.
If you have looked at the source code of the module, then you will see that it basically works by creating an array of queried packages to disable/enable. I could imagine that due to what ever fault / later update / package changes / ... the "enable query" might look different than the "disable query" that was run months before. Meaning that there is a chance that not everything that got disabled will get enabled again.
Click to expand...
Click to collapse
Indeed ... that would be a very good improvement ... I´ll have a look at implementing that.
Thanks for the suggestion.
MrRob0t said:
This would be great on the Pixel 5
Click to expand...
Click to collapse
Will work on any phone.
foobar66 said:
Indeed ... that would be a very good improvement ... I´ll have a look at implementing that.
Thanks for the suggestion.
Click to expand...
Click to collapse
It would also be useful for re-running the module after installing some new apps.
E.g. re-running dss disable user will try to disable all user apps even if 90% of them was disabled previously already.
If there was a "file" or "log" to compare what was disabled already, then it could only care about what is now newly installed
This is a copy of my question on SO.
I want to remove Google apps and services on a new Fairphone 4 (Android 11, now rooted using Magisk. No TWRP build available yet.).
To this end, I am trying to use microG. In the Prerequisites for its usage, signature spoofing and deleting files in `system/priv-app` are listed. For signature spoofing, I followed the *XPosed solution for Android 11 and 12* listed here, i.e. using Magisk + riru + LSPosed + a FakeGApps fork. Not sure, whether or not this worked. All individual steps reported success, but the Signature Spoofing Checker says it didn't work.
Anyway, I'm definitely stuck at the second step, because I don't seem to be able to delete any files in `system_ext/priv-app`. I tried the solutions proposed here and here.
If I try
Code:
adb shell
su
# then confirm on the phone, then
mount -o rw,remount /
I get '/dev/block/dm-0' is read-only. Similar error (with dm-1) if I try mounting /system_ext.
adb root or adb disable-verity don't work, because it's a user build: adbd cannot run as root in production builds, verity cannot be disabled/enabled - USER build.
I even tried to write a Magisk module to replace the directories in question with empty ones, by putting the following in the customize.sh:
Code:
REPLACE="
/system_ext/priv-app/GoogleFeedback
/system_ext/priv-app/GoogleOneTimeInitializer
/system_ext/priv-app/GoogleServicesFramework
/system_ext/priv-app/SetupWizard
/system/system_ext/priv-app/GoogleFeedback
/system/system_ext/priv-app/GoogleOneTimeInitializer
/system/system_ext/priv-app/GoogleServicesFramework
/system/system_ext/priv-app/SetupWizard
"
I think /system/system_ext and /system_ext are hard linked, but not sure whether that matters. After loading that module and rebooting, the contents of those folders are still the same when checking with adb shell.
Any ideas?
For adb I'm using my desktop with Ubuntu 21.10.
Hello,
It's way easier than you can imagine. I did a tutorial there : https://forum.fairphone.com/t/tutorial-install-microg-on-fairphone-os/80016
But as you are quite advanced, the only thing you have to do is to install NanoDroid-MicroG with Magisk : https://downloads.nanolx.org/NanoDroid/Stable/
Just install the Zip and eventually update MicroG on the official website (version packed in NanoDroid is 17, newest one is 22...). This will erase all old Gapps.
PS :signature check spoofer don't work, the package you mentionned (which is the one I use also) only fake signature for Gapps, which is a good thing...
Thanks a ton! Looks like it worked, and it really wasn't more than installing that one module
Better use an ungoogled OS like LeOS-S. It's Android12L and works great an FP4
See https://leos-gsi.de
I have installed Lineage 18.1 GSI and trying to install gapps. I have rooted and using franko to flash opengapps pico and get an error 70 that there is not enough space on /system. What is the way to get this done? Thanks in advance!
I would like to know that as well.
Tried to flash via stock recovery but that aborted because signature verification failed.
Apps like Flashify, Flash Gordon, Flashfire or Rashr didn't work either.
With MagiskGapps-basic-module from wacko1805 the playservice framework always crashed.
I think the easiest and best way would be to flash opengapps via TWRP.
@ada12 seems to have a TWRP build that still has some bugs, but can be used to flash unsigned zip files.
Maybe he can share this with us.
I feel like this should not be a collasal effort, but it has become one. I have spent the whole day trying to figure it out. I want to use Lineage OS 18.1 with gapps from Andyyan, not any other rom.
psychofaktory said:
I think the easiest and best way would be to flash opengapps via TWRP.
Click to expand...
Click to collapse
I suspect that Magisk should be able to do whatever TWRP is doing (which is just putting some files in certain places, for the most part). Have you tried to find a Magisk module with OpenGapps? Or you can try making your own (but be warned that lzip is not available by default on any Android or Linux).
Edit: nevermind, I see you found a LiteGapps Magisk module.
Thanks @wirespot
The hint with the linked script to create a custom Magisk module on the preferred OpenGapps bundle was worth gold!
Now I have another problem that comes from installing the OpenGapps via Magisk.
For passing SafetyNet I have to add com.google.android.gms and com.google.android.gms.unstable to the deny list.
But when restarting Magisk all modules are reloaded. So also the OpenGapps module.
As a result, the adjustments to the deny list for the Google Play services are discarded again with every restart and the SafetyNet check fails.
How can I prevent that the two entries are no longer removed from the deny list?
Or how can I ensure that the entries are automatically added to the deny list on restart?
Edit:
It seems that this is what Magisk intended and com.google.android.gms and ...gms.unstable are automatically added to the deny list.
But now I have the question, how can I pass the SafetyNet test?
wirespot said:
I suspect that Magisk should be able to do whatever TWRP is doing (which is just putting some files in certain places, for the most part). Have you tried to find a Magisk module with OpenGapps? Or you can try making your own (but be warned that lzip is not available by default on any Android or Linux).
Edit: nevermind, I see you found a LiteGapps Magisk module.
Click to expand...
Click to collapse
Yes, but there is an issue with litegapps, the google contacts sync is broken unfortunately...
psychofaktory said:
It seems that this is what Magisk intended and com.google.android.gms and ...gms.unstable are automatically added to the deny list.
But now I have the question, how can I pass the SafetyNet test?
Click to expand...
Click to collapse
The deny list only lets you pass Basic check. To also pass CTS you need the USNF module (Universal SafetyNet Fix) and possibly other modules too. More details in this thread (check the end of the post), but try with just deny list and USNF first.
Neither the basic integrity check, nor cts profile match are passed.
Besides the denial list, I tried the modules "Shamiko", "Universal SafetyNet Fix" and "MagiskHide Props Config".
With the latter I have also tried various combinations, unfortunately unsuccessful in each case.
It looks like the deny-list does not work.
I suspect here also a connection with the message together that Magisk displays with each call:
Code:
An "su" command that does no belong to Magisk is detected. Please remove the other unsupported su
I have already been able to disable Phh-su with these commands:
Code:
adb shell
phh-su
mount -o remount,rw /
mount -o remount,rw /system
remount
mount -o remount,rw /
mount -o remount,rw /system
/system/bin/phh-securize.sh system.img
But the message in Magisk still appears.
Yeah passing SafetyNet with a custom ROM may be tricky. Didgeridoohan has a few more tips on their website you can try.
OK, I am already a big step closer to the solution.
After installing Magisk regularly, I first installed the Franco Kernel Manager.
Through this I was then able to flash UnSu.zip, which completely removed phh-su.
This also removed the message "An "su" command that does no belong to Magisk is detected" from Magisk.
Magisk had to be set up again afterwards, since it was also cleaned up by the UnSu script.
YASNAC now already showed "Basic integrity -> Pass".
But now I have not found a way to pass the CTS-profile match.
Does anyone here know what settings to set via MagiskHideProps Config?
And could someone send me the fingerprint of the stock rom (62.0.A.9.11)?
Code:
getprop ro.build.fingerprint
After some tests I discovered a big disadvantage with the variant to flash OpenGapps via Magisk.
Push notifications do not seem to work.
I use too many services that rely on Google Push notifications, so I can't do without them.
Compared to the "normal" variant of flashing OpenGapps via recovery before the first boot, the Magisk variant seems to be missing important dependencies and permissions that are only set during the first boot of the rom.
Therefore, the only useful variant is to flash GApps via recovery.
I really hope that we will soon have the possibility to flash unsigned zip files here!
Another approach:
Opengapps-zip files cannot be flashed via the stock recovery because it fails signature verfication.
The GSI roms can be flashed via the stock recovery. So they seem to be signed correctly.
Would it be possible to sign the Opengapps-Zip files with the same signature keys as the GSI-Roms to be able to flash them via the stock recovery?
Aren't GSI ROMs flashed through fastboot? Since they're partition images not zip installers like OpenGapps.
Of course. You are right.
Would it be possible to merge a GAPPS zip file into a GSI image and then flash the image with fastboot?