Related
NanoDroid
NanoDroid is a installer for various OpenSource related things, most noticably microG and F-Droid. It supports direct /system installation, both devices with or without A/B partition scheme, aswell as Magisk Mode (module) installation. It also includes several tools (eg. GNU Bash, shell utilities, more), scripts, fonts, sounds and additional features (system debloating, init scripts, automatic logcat creation), aswell as a companion F-Droid Repository.
Furthermore it allows the user to do fine-graded installations using configuration files, which allow to choose what to install, or if several alternatives are available, which of them, see "Alter Installation" in the full documentation (link at the end of this post).
In order for full microG experience NanoDroid contains a modified Play Store which allows (in-)app-purchases with microG, which would normally not be possible. It also tries to remove all previously installed GApps on it's own. For ROMs without builtin signature spoofing support NanoDroid includes an on-device Patcher which tries to patch your ROM from TWRP.
Versions until 15.1 were called NanoMod, starting with 16.0 they're called NanoDroid.
NanoDroid does now have a companion F-Droid Repository for easy updates of Play Store (patched with (in-)app-purchase support) and MPV builds Repository Info-Page
Current Release
Stable: 23.1.1.20210117 "BusyCompat"
Beta: --- (---)
Nanolx: latest stable and beta releases
Snapshot: read the documentation in the git repository on how to create a snapshot build
Supported Android Versions
NanoDroid officially supports the following Android versions:
4.4 / SDK 19 (KitKat)
System Mode only (Magisk does not support KitKat)
5.0 / SDK 21 (Lollipop)
5.1 / SDK 22 (Lollipop)
6.0 / SDK 23 (Marshmallow)
7.0 / SDK 24 (Nougat)
7.1 / SDK 25 (Nougat)
8.0 / SDK 26 (Oreo)
8.1 / SDK 27 (Oreo)
9.0 / SDK 28 (Pie)
Patchers works, if you've previously manually deodexed services.jar
Deodex Instructions
10.0 / SDK 29
Patchers works, if you've previously manually deodexed services.jar
Deodex Instructions
11.0 / SDK 30 (R)
Patcher does not work from TWRP
Patcher works from Magisk if your ROM's services.jar already contains classes.dex
Deodex Instructions
earlier versions will never officially be supported (you may still report bugs, though).
Future versions will be officially supported, eventually.
Summary
NanoDroid can be installed as a Magisk Module or directly to /system, though a bit functionality is only available with Magisk. It must be installed from TWRP!
NanoDroid includes
microG and it's companions
on-device framework-patcher for microG support (signature spoofing)
F-Droid and it's privileged extension
modified Play Store to allow (in-)app-purchases with Magisk
alternatively Aurora Store can be installed instead
custom init scripts
pseudo-debloat feature
disables applications systemless-ly
pre-configured default settings
several Open Source applications
include replacements for the pseudo-debloated applications
full list of included applications
Packages
Magisk Modules
Module packages, flashing through TWRP recommended, flashing through Magisk Manager possible starting with version 22.6.91 (22.7-beta2).
NanoDroid: includes
everything mentioned in the Summary
NanoDroid-microG: includes
microG and it's companions
GNU Bash
pseudo-debloat feature
app stores
NanoDroid-fdroid: includes
F-Droid and it's privileged extension
NanoDroid-BromiteWebView: includes
Bromite WebView
NanoDroid-OsmAnd: includes
OpenStreetMap for Android (OsmAnd+)
Extras
Extra packages, flashing through TWRP recommended, flashing through Magisk Manager possible starting with version 22.6.91 (22.7-beta2).
NanoDroid-pacher: includes
on-device framework-patcher (signature spoofing support)
NanoDroid-systest: includes
System Test script which generates a log to aid issue reporting
NanoDroid-uninstaller: includes
uninstalls all NanoMod/NanoDroid Magisk Modules
uninstalls NanoMod/NanoDroid installed in System Mode
uninstalls NanoMod/NanoDroid-Patcher addon.d environment
The GitLab repository contains the full documentation with infos about
more detailed info what's included
detailed installation instructions
setup instructions for microG
list of known Issues (and fixes/workarounds)
more
>> Full Documentation
ChangeLog
https://gitlab.com/Nanolx/NanoDroid/blob/master/ChangeLog.md
List of known issues (and fixes)
https://gitlab.com/Nanolx/NanoDroid#issues
Can we pass safetynet with xposed. with microg?
purval6300 said:
Can we pass safetynet with xposed. with microg?
Click to expand...
Click to collapse
No difference between GApps and microG.
In the github repository you'll find the following changes for upcoming 5.1 (no ETA)
updated Magisk to beta.13.170405 (which fixes the issues I had with 12.0 on Moto X Play and Galaxy S6)
improved nanomod-overlay script
the script does now have better output for -l/--list parameter (which lists all pseudo-debloated system apps)
the script does now have -s/--show parameter which shows all non-pseudo-debloated system apps with both apkname and label (label = the name that shows up in launcher)
there's no 'column' command on android, so the output is not pretty aligned, but well
Screenshots attached.
Suggestion
Add this for microG set up
Disable Battery Optimization, if you use Android 6 (Marshmallow) or above. Ensure that it is disabled for microG Services Core in System Settings > Battery > Menu > Battery optimization. Note that this is the case for the original Play Services, as it is required to keep a stable background connection.
atendedor_de_boludos said:
Suggestion
Add this for microG set up
Disable Battery Optimization, if you use Android 6 (Marshmallow) or above. Ensure that it is disabled for microG Services Core in System Settings > Battery > Menu > Battery optimization. Note that this is the case for the original Play Services, as it is required to keep a stable background connection.
Click to expand...
Click to collapse
I mentioned to ensure everything is set in 'Self Check', but I consider will re-word that paragraph to be more clear.
Hi. I got "updater process ended with signal 4" when tried to flash this.
Using galaxy s3, with RR 5.8.2.
djedjy said:
Hi. I got "updater process ended with signal 4" when tried to flash this.
Using galaxy s3, with RR 5.8.2.
Click to expand...
Click to collapse
After flashing in TWRP connect your phone to pc and use adb to grab a log from recovery
Code:
adb pull /tmp/recovery.log
Then post recovery.log (rename to recovery.txt) file here.
Will this work on my Galaxy S7 using stock ROM? I'm interested in installing microG to satify apps dependant on Google Play Services, but I couldn't get it because it needs signature spoofing, and the mods it recommended needed a deodexed ROM, which mine is not.
CyanogenLover said:
Will this work on my Galaxy S7 using stock ROM? I'm interested in installing microG to satify apps dependant on Google Play Services, but I couldn't get it because it needs signature spoofing, and the mods it recommended needed a deodexed ROM, which mine is not.
Click to expand...
Click to collapse
If your ROM is not deodexed you can't patch services.jar, so microG won't work. Anything else in the package would work, though.
Setialpha said:
If your ROM is not deodexed you can't patch services.jar, so microG won't work.
Click to expand...
Click to collapse
Is there a way to deodex the stock ROM without bricking my S7? It sounds complicated, and I'm sure it is, but there must be a way! :fingers-crossed:
Setialpha said:
After flashing in TWRP connect your phone to pc and use adb to grab a log from recovery
Code:
adb pull /tmp/recovery.log
Then post recovery.log (rename to recovery.txt) file here.
Click to expand...
Click to collapse
Here:
Code:
I:operation_start: 'Flashing'
Installing zip file '/sdcard/NanoMod-5.0.20170405.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
<>> <<>
<>> <<>< NanoMod 5.0.20170405 >
< NanoMod 5.0.20170405 > <<> <>>
<<> <>>Updater process ended with signal: 4
I:Legacy property environment disabled.
I:Install took 0 second(s).
Error installing zip file '/sdcard/NanoMod-5.0.20170405.zip'
Updating partition details...
I:Data backup size is 71MB, free: 4441MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
...done
I:Set page: 'flash_done'
I:operation_end - status=1
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'filemanagerlist'
Truncating string cache entries.
I:Set page: 'filemanageroptions'
I:Set page: 'choosedestinationfolder'
I:Set page: 'filemanagerconfirm'
I:Set page: 'filemanageraction'
I:operation_start: 'Command'
I:Running command: 'cp "/tmp/recovery.log" "/sdcard"'
djedjy said:
...
Click to expand...
Click to collapse
You either have MD5/signature check for zip files active in TWRP, then disable it, or your TWRP is buggy,. Because it fails early, ar that stage the updater-script sets the progrssbar to 10% and mounts partitions.
Do you have the latest TWRP installed for your device?
FYI on AFH you can now find a microG only Magisk Module, too. framework-patcher.sh in github repo was updated to support both modules. You can also use 'mod.sh microg' to create the microG only zip from git repo.
Link: https://www.androidfilehost.com/?a=show&w=files&flid=150729
The microG only module does support
Code:
nanomod.reinstall
nanomod.play
configuration parameters, like the full package.
version 5.1.20170408 released
Version 5.1.20170408 released, with the following changes since 5.0.20170405:
Code:
5.1.20170408:
- Internal Changes
* only copy DroidGuard.apk to /sdcard if
'nanomod.microg' is '1' in 'nanomod-setup'
configuration file
* add new option 'nanomod.zelda' to 'nanomod-setup'
configuration file, allows to control whether to
install or not install Zelda ringtones and sounds
* 'nanomod.play=0' now actually works and does not
install any app store
- Variants
* full package: microG, F-Droid & apps, pseudo-debloat
feature, Zelda ringtones & sounds, GNU Bash, GNU Nano,
aapt utility
* microG package: microG only
* framework-patcher.sh updated to support both modules
- Removed files / features
* Effect_Tick Zelda sound
- I admit, that one was too annoying
* Magisk installation
* unsu Script
- Read: NanoMod is now only the Module, no longer
includes Magisk itself
- nanomod-overlay Script Changes
* parameter '-l', respectively '--list' now has
properly formatted output
* parameter '-r', respectively '--remove' now
only removed exact matches from config file
* parameter '-a', respectively '--add' now
properly formats config file
* new parameter '-s', respectively '--show' which
shows all non pseudo-debloated system applications
* new paramter '-d', respectively '--delete' which
will remove all overrides and thus re-enable all
applications, unlike '-r' / '--remove' this will
not change the config file, so you can re-debloat
using '-u' / '--update' again
- Updates
* Play Store (7.7.09.O)
* VLC (2.1.4~beta)
* GNU Nano (2.7.5)
* Substratum (631)
- Added applications
* F-Droid Privileged Extension (0.2.2)
- allows installation of apps using F-Droid
without enabling 'Unknown Sources' in the
security settings of your device
I also changed a few things in the README/first post here (for example paragraph "Installation" with download links is now almost at top, instead of bottom). Magisk is no longer installed, so this is now really a Magisk Module on it's own.
This work is exactly what the community needs to help move novices like me into an open-source-ONLY ecosystem. Thank you!!!
Setialpha said:
FYI on AFH you can now find a microG only Magisk Module, too. framework-patcher.sh in github repo was updated to support both modules. You can also use 'mod.sh microg' to create the microG only zip from git repo.
Link: https://www.androidfilehost.com/?a=show&w=files&flid=150729
The microG only module does support
Code:
nanomod.reinstall
nanomod.play
configuration parameters, like the full package.
Click to expand...
Click to collapse
I installed this version, but I cannot get Phonesky (play store) to have the correct signature. System is spoofing signature correctly, but somehow play store doesn't. Every tick in self check section is there, except the "Play Store (Phonesky) has correct signature" tick. The play store works fine signing in and downloading. However apps like gmail do not work. Maybe it needs to be put in priv-app?
Running Crdroid 7.1.1 (supports spoofing signature) oneplus one, latest nanomod package 0408, magisk v12
f41lbl0g said:
FYI on AFH you can now find a microG only Magisk Module, too. framework-patcher.sh in github repo was updated to support both modules. You can also use 'mod.sh microg' to create the microG only zip from git repo.
Link: https://www.androidfilehost.com/?a=show&w=files&flid=150729
The microG only module does support
I installed this version, but I cannot get Phonesky (play store) to have the correct signature. System is spoofing signature correctly, but somehow play store doesn't. Every tick in self check section is there, except the "Play Store (Phonesky) has correct signature" tick. The play store works fine signing in and downloading. However apps like gmail do not work. Maybe it needs to be put in priv-app?
Running Crdroid 7.1.1 (supports spoofing signature) oneplus one, latest nanomod package 0408, magisk v12
Click to expand...
Click to collapse
Phonesky ie play store works normally as a user app. I am using it that way (I am on normal gapps) and I have no problems.
{
"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"
}
Smali Patcher
WHAT THE HELL IS THIS THING? ::
To sum things up this is an application I developed that pulls the android framework from your device, applies what I (or other users) consider useful patches to the sourced files and then finally generates a magisk module applying the patches system-lessly.
The unique thing about Smali Patcher is it sources the framework files from your device, in an attempt to provide maximum compatibility across the entire android device family.
While I have your attention I wanted to throw out a massive thank you to all the people who have provided support to the project and the thread over the years, you guys are absolute champions. I can't thank you enough and couldn't have done it without you, here's to ya!
PATCHES ::
Mock locations - Hide mock locations status, allowing apps like Pokemon GO to treat them as genuine location updates.
Mock Providers: Allow creation of mock providers without mock permissions.
GNSS updates: Disable all GNSS (GPS) location updates.
Secure flag - Allow screenshots/screensharing in secure apps.
Signature verification (as-is, legacy support only) - Disable signature verification allowing modification/execution of signed system apps.
Signature spoofing (as-is) - Enable signature spoofing app permission.
Recovery reboot - Reboot directly back into recovery from powermenu.
Samsung Knox (as-is, legacy support only) - Bypass Samsung Knox trip protection, only confirmed working for secure folder.
High volume warning - Disable high volume popup dialog.
Any patches marked "as-is" are no longer maintained and only kept in for legacy device support only, not recommended to be used on newer android versions (10/11).. use at your own risk.
GPS SPOOFERS / FUSEDLOCATION / RUBBERBANDING NOTICE ::
FusedLocation API GPS spoofers are NOT compatible with the mock location patch.. your required to use a traditional GPS spoofer! Spoofed location updates will be fed into fusedlocation all the same, meaning you don't need to disable the service.. which means while your not spoofing you still gain the benefit of fusedlocation which is all around more accurate location updates!
REQUIREMENTS ::
PC with at least 3GB+ of RAM.
.NET Framework 4.7.1 or later installed
Java installed
Android device running 6.0 or above.
INSTRUCTIONS (ADB METHOD/AUTOMATED - RECOMMENDED):
COMPATIBLE WITH BOTH ODEX & DEODEXED ROMS! WILL AUTOMATICALLY DEODEX REQUIRED FILES IF NECESSARY.
Backup device.. safety first kids.
Enable USB debugging in developer settings on your device and connect via USB to your PC.
Authorise USB debugging connection on your phone.. example of popup.
Run "SmaliPatcher.exe", First startup will automatically download the latest necessary binary's.
Select your desired patches.
Hit "ADB PATCH" button (yes without browsing for a .jar file).
Once the process has completed, magisk module will be generated in the same directory as "SmaliPatcher.exe" named: "[email protected]".
Install the generated magisk module either in recovery mode or from the magisk app.
Enable smali patcher module in magisk.
INSTRUCTIONS (ALTERNATIVE METHOD - FOLLOW ONLY IF ADB METHOD FAILS) ::
Backup device.
Enable USB debugging in developer settings on your device and connect via USB to your PC.
Authorise USB debugging connection on your phone.. example of popup.
Run "SmaliPatcher.exe", First startup will download the latest necessary binary's.
Browse to your "/system/framework" directory. Easiest way to obtain these files is from your rom img/zip.
Select your desired patches.
Hit the "PATCH" button.
Once the process has completed, magisk module will be generated in the same directory as "SmaliPatcher.exe".
Install the generated magisk module either in recovery mode or from the magisk app.
Enable smali patcher module in magisk.
YOU ARE STILL REQUIRED TO HAVE A DEVICE CONNECTED TO YOUR PC IF YOU USE THIS METHOD.. THE PATCHER WILL NOT PROGRESS OTHERWISE.
A ADB DEVICE IS REQUIRED TO EXTRACT CDEX FILES.. IF YOU'RE PARANOID/SAVY ENOUGH, YOU CAN USE A ANDROID EMULATOR.
BEFORE REPORTING ANY ISSUES ::
You have tried running the patcher as administrator.
You have accepted the USB debugging connection & ticked "Always allow from this computer".
You have tried running the patcher with phone booted in recovery mode with /system mounted.
shoey63 said:
Adb method works flawlessly on android 8.1 for Sony AOSP roms on X and XZ premium. The trick is to run the program in recovery (with system mounted obviously), to avoid permission issues.
Awesome tool!
Click to expand...
Click to collapse
UPDATING MODULE INSTRUCTIONS:
Disable/uninstall any active smali patcher modules before generating a new one! If you generate a module with a older version active there's a chance the outdated patches will carry over to the new module.. I do my best efforts to prevent this, but it may still happen. Before reporting issues, make sure you have tried this.
CHANGELOG ::
7.4
Modified patch - GNSS updates: now correctly handles protected methods.
7.3
First pass of android 11 patch updates: mock provider, gnss update & secure flag patch updated.
7.2
Modified patch - Secure flag: revert a change I made, should solve issues on some devices.. hopefully.
7.1
New patch - GNSS updates: Disable all GNSS (GPS) location updates.
Modified patch - Secure flag: tested & working on Samsung devices running android 10.
7.0
New patch - Mock Providers: Allow creation of mock providers without mock permissions.
6.9
Allow devices booted in recovery mode through ADB check.
6.8
Made patches "compatible" with the latest android 11 beta (pixel).. none of which have been tested on android 11. BACKUP! BACKUP! BACKUP!
6.7
Removed "magisk-module-template" dependency.
6.6
Fixed patch - Magisk reboot: was not being applied when selected.
"Magisk reboot" patch renamed to "Recovery reboot".
6.5
Updated patch - Magisk reboot: now compatible with Samsung One UI 2.0 (android Q).
6.4
New patch - Samsung Knox: Bypass samsung knox trip protection, only confirmed working for secure folder.
6.3
ADB error checking: require a ADB device to be present even while patching "browsed" for framework dumps.
Framework error checking: display an error if no odex, vdex or oats are found.. incomplete framework dump.
Display hints for common mistakes made by users, hopefully reduces the amount of "error" reports by people that don't follow instructions.
6.2
ADB error checking: unauthorized ADB device check.
6.1
Error handling - Verify required files are found during deodex process.
6.0
Fixed index out of bounds crash.
Revert mock location patch to the original.
5.9
Mock location patch updated. Reverted patch back to the original, new patch failed.
Adapted back end functions to support multi-file patches.
Browse for .jar has now been changed to browse for "/system/framework" directory.. no longer requires a deodexed file to be targeted, will deodex necessary files if required.
5.8
Check if patcher is being ran with administrator privileges, otherwise display a warning.
Fixed a possible false positive error during cdex extraction.
5.7
Error handling - verify classes.dex is found during cdex extraction.
Added few more status updates to assist error checking.
5.6
Changed binary download percentage behaviour: avoid users reporting false "stuck on XYZ percent".
Updated mock location patch to support android 10/Q.
Updated reboot behaviour patch to support android 10/Q.
Save/restore selected patches when browsing for a JAR.
5.5
Fixed force close during vdex extraction.
5.4
Modified secure flag patch - need testing & feedback.
Modified java detection to allow more runtime environments.
5.3
Suppress false positive "magisk download failed" errors.
Verify patched APK's have been generated before creating module.
5.2
Modified secure flag patch.
Added paypal donation button.
5.1
Removed signature verification "class not found" error report, false positive on legacy android versions.
5.0
Adapted backend functions to support multi-file patches.
Require at least one patch to be enabled before proceeding.
Fix download percentage status updates.
Popup explorer window to output directory on completion.
Modified signature verification patch (android P).
When browsing for a JAR only display compatible patches (preparation for multi-file patches, services.jar must be named "services.jar" from this point onward for verification purposes.. otherwise no patches will be displayed).
New patch - disable high volume warning popup.. this has annoyed me so much recently! I was only able to test this on android P, if you find the patch does not work on your device please supply a deodexed services.jar so I can investigate further.
4.9
Fixed a crash when applying magisk reboot patch to a already patched target.
Improved magisk reboot patch, removed the potential to not reboot back into magisk.
Redirect output for certain binary functions with working status indicators.
Fix mock location patch that I broke in the most stupid way possible.. if you're updating from 4.8, make sure you disable/remove any installed smali patcher magisk modules before updating.
4.8
Display command line window until inbuilt patcher status updates are fixed to prevent user confusion.
4.7
Secure flag patch update (based off 9.0).
Signature verification patch update (based off 9.0).
4.6
Dynamically calculate base directory.
Modify output loop to ensure all output is displayed.
Magisk reboot patch (Galaxy S10 only).
4.5 [UNTESTED - I OWN A S10 WHICH CURRENTLY IS NOT MAGISK COMPATIBLE.. USE AT YOUR OWN RISK]
Force unix config formatting.
4.4 [UNTESTED - I OWN A S10 WHICH CURRENTLY IS NOT MAGISK COMPATIBLE.. USE AT YOUR OWN RISK]
Magisk "installation failed" fix.. (I shouldn't have been lazy and read all the module documentation.. probably could of avoided this).
4.3 [UNTESTED - I OWN A S10 WHICH CURRENTLY IS NOT MAGISK COMPATIBLE.. USE AT YOUR OWN RISK]
Magisk v19.0 compatible (magisk template download failed fix).
4.2 [TESTING]
Potential slowdown fix?
4.1
Allow the patcher to run without having any patches selected for testing purposes.
Force a single classes.dex to be generated when applying signature spoofing patch.. (potential slowdown fix?)
Remove irrelevant debug output.
4.0
Modified ADB error checking function to fix false error reports.
3.9 ::
ADB error checking: verify a single ADB device is connected before proceeding.
Added few more status updates to assist error checking.
Updated magisk template & URL.
3.8 [TESTING] ::
Potential slowdown fix?
3.7 ::
Modified java detection.
3.6 ::
Added some more error checking.
3.5 ::
Verify Java is installed & detected before proceeding.
3.4 ::
Amend legacy dummy file to generated magisk module config.sh.
3.3 ::
Create dummy file in magisk module (legacy devices).
3.2 ::
Fixed a issue calculating file paths on legacy devices.
3.1 ::
Added "/system/system" path to dumping functions.
Added output filter to avoid user confusion when spitting out harmless errors.
3.0 ::
Updated dependencies.
Reworked some core functions to attempt to fix unknown caused crash for certain users.
2.9 ::
Reworked some functions, made them dynamically detect file names to avoid potential issues.
2.8 ::
Verify dexpatcher patches are found, otherwise re-download.
Change patch button text to indicate patching mode.
Error handling - verify classes.dex is found before recompiling.
Error handling - verify services.jar is found before recompiling.
Error handling - verify input files are not dummy's.
Conditional dead end bug fix while patching multi-class jar's.
2.7 ::
Re-added signature spoofing patch.
Added dexpatcher as a dependency.
2.6 ::
Added support for Android P.
Modified binary download function to prevent crashes.
2.5 ::
Added support for multi-classes.dex.
2.4 ::
Improved binary download function - verify binary size, will attempt to re-download if necessary.
Improved binary URL grabber function - should now fetch correct address.
2.3 ::
Improved de/odex detection function - should now allow generating a module with no mods selected (debugging purposes)
Improved error checking & reports.
2.2 ::
Android 8.0-8.1 compatibility.
2.1 ::
Corrected missing variables in config.sh for magisk module (lollipop bootloop fix) - full credit to @Eng.Raman
2.0 ::
Prevent false "detected api" message.
Play's nice with android lollipop - full credit to @Eng.Raman
1.9 ::
Potential fix for random crash aka. dumping framework freeze/crash.
1.8 ::
Handle "permission denied" error when pulling build.prop.
1.7 ::
Improved framework base directory detection.
1.6 ::
Framework base directory detection.
1.5 ::
Improved error checking - added more debug info which hopefully will make diagnosing bugs a little easier.
Proper API detection using rom build.prop.
Improved a search function used for locating framework files.
1.4 ::
Improved error checking - verify's services.odex size detecting if module already active.
Potential fix for "magisk download failed" that certain user's are experiencing.
1.3 (BETA) ::
Added in ADB libary which allows us to now pull/push files to the device.
Added in smali & baksmali which allows us to now deodex.
One click function to pull all the required files from the device, deodex (if necessary), patch and finally generate a magisk module! (I plan to code in a function that pushes the module to the device upon completion in the future - fully automated baby woohoo)
If you would like to use the adb method of patching, make sure you have "USB debugging" enabled in developer options otherwise it simply won't work.. you obviously need to plug in your phone to the PC and authorize the USB connection on your device.
1.2 ::
Updated to Magisk v15.
Improved error checking & reports.
1.1 ::
Removed signature spoofing for the time being - causing bootloop for some users, need to rework the patch when I have time.
1.0 ::
Improved patching function: should now be compatible with even more unique service.jar's.
Improved patching function: now reports errors for each independent patch, should make diagnosing patch errors a little easier.
Fixed some debug code I left from previous release which may have prevented patch process from completing. (whoops.. sorry about that!)
0.9 ::
Added new patch: signature spoofing.
0.8 ::
Improved patching function.
0.7 ::
Merged projects together - Mock locations, secure flag & signature verification.
Assembly version used as module version and in generated module zip name.
Fixed minor bug when selecting a JAR named something other than "services.jar".
0.6 ::
Error handling for failed downloads of magisk module template.
Updated to Magisk v14.0.
0.4 / 0.5 ::
Potential spaces in file path error fix - unsure as I have been unable to reproduce this issue, so it's been very difficult to fix.
0.3 ::
Increased default Java memory heap size - fixes "out of memory" error on lowend PC's.
0.2 ::
Simplified patching process.
Fixed reboot issue with certain GPS spoofers.
Verify's target JAR is deodexed before proceeding with patch.
0.1 ::
Initial release
Cheers,
Honorable mention to @Eng.Raman & @A30NI_Y, who has been kind enough to patch service.jar's for tons of users who lack the knowledge to deodex (despite my best efforts of writing out clear instructions!)... the smali patcher user base thanks you for your service!
PRECAUTIONS / TERMS OF USE ::
You must backup your device prior to flashing the module, I am not responsible or providing support to recover any devices stuck in bootloops.. if for what ever reason you find yourself in this situation, simply uninstall magisk and reinstall.. doing this will reset your installed modules.
PLEASE READ FAQ IN POST 2 & SEARCH THE THREAD BEFORE ASKING QUESTIONS, CHANCES ARE THEY HAVE BEEN ANSWERED ALREADY AND YOU CAN FIND YOUR ANSWER IMMEDIATELY.
Rather then making mirrors of the download link, please redirect traffic to this thread to ensure they are always using the latest version! Oh hi reddit.
DOWNLOAD MIRRORS
Google drive
FAQ
HELP! I'M STUCK IN A BOOTLOOP, HOW DO I UNINSTALL ::
Boot into TWRP
Advanced -> File Manager
Navigate to: data -> adb -> modules -> select the module directory (in this case "fomey.smalipatcher") -> Folder icon (bottom right of screen) -> Delete
Alternatively you can just uninstall/reinstall magisk to clear all your modules.
MAGISK TEMPLATE DOWNLOAD FAILED ::
Run the patcher as administrator, may not have read / write access to drive.
Verify you have a active internet connection.
Verify firewall is not blocking the patcher.
Verify your not running a outdated .NET framework.
MOCK LOCATION RUBBER BANDS TO REAL LOCATION ::
Set device only in location method settings (Settings -> Location -> Location method).
Disable improve location accuracy settings (Settings -> Location -> Improve accuracy).
If you are still experiencing rubber banding after trying everything above, try a different spoofer.
INVALID OR CORRUPT JAR FILE BIN ::
Delete the "bin" directory and restart the patcher to re-download the binary files.
Corruption is caused by a unreliable internet connection.
HOW DO I CLEAR A MOCK LOCATION WHILE USING A GPS SPOOFER ::
Exit the app by pressing the "back" key, you may have to press this a few times. Any good spoofer should clean up after itself, by removing any mock providers on exit.
MAGISK TEMPLATE FAILED TO DOWNLOAD ::
Make sure you're using the LATEST release of the patcher.
If you are using the latest version already.. a update will be available shortly to fix this issue.
UNSUPPORTED MAJOR.MINOR VERSION XX.X ::
Use the Java Uninstall Tool to clean up out-of-date java versions and reinstall the latest java release.
W: COULD NOT FIND RESOURCES ::
This is a harmless warning, you can safely ignore it.
!!! ERROR: BASE DIRECTORY NOT FOUND ::
You did not accept the USB debugging permission popup on your phone.. the patcher can't do anything without this permission (example of popup).
The permission popup should be displayed after hitting the "ADB PATCH" button.. or as soon as you connect your phone to your PC.
If you can't see the permission popup: go to settings -> developer options -> revoke usb debugging authorisations.. disconnect and reconnect your phone and try again.
Make sure you tick "always allow from this computer".. otherwise you may have to confirm the popup multiple times during a single patch.
!!! ERROR: XYZ CLASS NOT FOUND ::
The patch is most likely not compatible with your android version/device, if a patch is marked "as-is" no further support is provided.
If you are browsing for a services.jar - it's most likely not deodexed.. try the "ADB METHOD".
If you are using the "ADB METHOD" and you receive this error, post a reply to this thread including as much information as you can. Useful information: android version, patcher log and the directory named "adb" in the patcher folder (upload this directory to google drive).
Reserved 3
Thank you very much for your smali patcher. I am using your mock location for a while now. Will it be compatible with Android Oreo?
flyfire04 said:
Thank you very much for your smali patcher. I am using your mock location for a while now. Will it be compatible with Android Oreo?
Click to expand...
Click to collapse
I have not tried it with a oreo services.jar, test it out let me know how you go.. if you run into issues please upload your deodexed services.jar.
Hey, could you make it just a zip that would do all the patches? I don't have a windows machine but I really want the screenshot thing I... Also I can do any testing that you want on the Oreo.
Thank you mate!!!
Awesome! Thank you!
Hi devs, sorry for interrupt. I have some problems while patching it here. I choose all three patch and run the patcher, However it suddenly stops and saying jar is not deodexed. When im untick all 3 patch and run the patcher, it runs well until completed. The problems only happens when I choose all or either one of the patches.
Im using samsung note 4 with custom deodexed rom :crying:
TheBuduLord said:
Hi devs, sorry for interrupt. I have some problems while patching it here. I choose all three patch and run the patcher, However it suddenly stops and saying jar is not deodexed. When im untick all 3 patch and run the patcher, it runs well until completed. The problems only happens when I choose all or either one of the patches.
Im using samsung note 4 with custom deodexed rom :crying:
Click to expand...
Click to collapse
Has anyone tried this on the Google pixel XL? Also when I download it and try to open it it tells me it can not be open ed
@fOmey Sir, when Smali Patcher on Linux and Android devices?
um, is this tool still not compatible with nougat's services.jar?
The patch button doesn't do anything at all.
Edit: nvm, restarting the program fixed it
HI !
When I extract my zip rom, I don't see any "system" folder ... (It's pixel ROM for nexus 5)...
Any ideas ?
Thanks.
AvisAile said:
HI !
When I extract my zip rom, I don't see any "system" folder ... (It's pixel ROM for nexus 5)...
Any ideas ?
Thanks.
Click to expand...
Click to collapse
This thread will help you out: https://forum.xda-developers.com/an.../how-to-conver-lollipop-dat-files-to-t2978952
rawimagee said:
Hi, i took my "services.jar" from my framework folder (OnePlus 5) and it says it is not deodexed. I have tried programs that will make the jar file to work in your flasher but it still does not work. Can you like write a little tutorial to me? Thanks
Click to expand...
Click to collapse
Copy the systems folder from your smartphone. (I copy it to the download folder, zip it, copy it and unzip it on the computer).
use Fulmics Deodexer (xda), download smali and baksmali from here https://bitbucket.org/JesusFreke/smali/downloads/ point fulmics deodexer to those files in the settings. Look for your systems folder with fulmics deodexer and only tick the frameworks box (the other ones are unneccesary for this task). then proceed with the smali patcher
@fOmey
I can not start your program. Can you make this pacher for me on my services.jar file so that I can put it into the framework system? My file with S7 edge nougat 7.0 Stock.
https://files.fm/u/j388jjj5
Tested on Oreo and it works great
The app crashes after i hit the start making path button on windows 10.. any help ??? Got the bins downloaded and my services.jar loaded in youre app/program.
rawimagee said:
I did that and but it still seems to not work, it said that it processed the "services.jar" file but it still says the same in the patcher;(
edit: do i pick the normal "services.jar" file from the normal folder or do the "edited" file get placed somewhere else?
Click to expand...
Click to collapse
OP5 is on Nougat, so I don't think this will work.
Sent from my OnePlus3 using XDA Labs
This worked for me on latest build of havoc os, might work for other Roms too.
Step 1 :
Open Magisk manager, download and install both
MagiskHide Props Config (link) and Busybox for android NDK modules from downloads, after installing reboot your phone.
Step 2:
Install terminal emulator from playstore(link)
Step 3:
open terminal emulator
enter command :
Code:
su
Grant superuser access when prompted
Step 4:
type in command:
Code:
props
Step 6 :
and follow the on screen options
select option 1 - edit device fingerprint
by typing : 1
then type in f to Pick a certified fingerprint
from the list pick your mobile manufacturer
select your mobile model
select the latest available android version
finally reboot your phone by typing in
Code:
reboot
this should fix the ctsProfile issue,
to use banking or wallet apps, hide magisk by using magisk hide option and select the app you want to hide root access from
thanks to this awesome dev Didgeridoohan for making this possible
https://forum.xda-developers.com/member.php?u=4667597
for people who want a video to look at the process here is the video
credits :
Thread link for magisk hide props config module: https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228
DEV for magisk hide props config module : Didgeridoohan
you can donate him at : https://www.paypal.me/didgeridoohan
does it affect the fingerprint?
is it safe?
this process works to solve cts Profile check, but banking apps still doesn't work
Doesn't work for me.
I used:
Google Pixel XL (Android 10)
Magisk 20.4
Magisk Manager 7.5.1
Edit: Enable "Magisk Hide" in the Settings -> reboot -> now it works.
Doesn't work for me either.
Pixel 4
It didn't give me an option to select an Android version.
I managed to make banking apps to work by disabling usb debugging.
Enviado desde mi F8331 mediante Tapatalk
I did exactly as it described above but still ctsprofile: false. Google pay sees root on my Poco F2 Pro.
Unfortunately does not work for Google Pixel 4 XL (Android 10)
For everyone that's struggling with trying to pass CTS:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Unlocked_bootloader_3
Google seemed to do something, i.e. Google Pay has been working for a long time. But when I was sleeping, Google sneaked in to my bedroom and made so that ctsProfile returned false in Magisk when I wake up.
A new unknown and uninvented method needs to be done? A Magisk update?
Vantskruv said:
Google seemed to do something, i.e. Google Pay has been working for a long time. But when I was sleeping, Google sneaked in to my bedroom and made so that ctsProfile returned false in Magisk when I wake up.
A new unknown and uninvented method needs to be done? A Magisk update?
Click to expand...
Click to collapse
Ha!
I concur!
did the whole process with my Mi A3 with Android 10 and my device is stuck on Mi logo. how to fix?
Interesting. Woke up jul 8th as well with as notification that Google pay cannot be used any more. Seems like they flipped a switch.... I tried unroofing until I realized I had to do a factory reset to relock the bootloader. So back on root without Google pay. I hope for a quick solution though
Heh...
I have tried this method. It was suprising that Mi 10 is not on the props list...
The best thing in my phone is that the CTS is false (for - as I can remember - three weeks) but GP payements work.
Banking apps not working even though hided in the magisk. Any fix for it?
Not working with Magisk 20.4
Try disabling usb debugging and/or magisk hidding
Enviado desde mi F8331 mediante Tapatalk
vamsi209 said:
This worked for me on latest build of havoc os, might work for other Roms too.
Step 1 :
Open Magisk manager, download and install both
MagiskHide Props Config (link) and Busybox for android NDK modules from downloads, after installing reboot your phone.
Step 2:
Install terminal emulator from playstore(link)
Step 3:
open terminal emulator
enter command :
Code:
su
Grant superuser access when prompted
Step 4:
type in command:
Code:
props
Step 6 :
and follow the on screen options
select option 1 - edit device fingerprint
by typing : 1
then type in f to Pick a certified fingerprint
from the list pick your mobile manufacturer
select your mobile model
select the latest available android version
finally reboot your phone by typing in
Code:
reboot
this should fix the ctsProfile issue,
to use banking or wallet apps, hide magisk by using magisk hide option and select the app you want to hide root access from
thanks to this awesome dev Didgeridoohan for making this possible
https://forum.xda-developers.com/member.php?u=4667597
for people who want a video to look at the process here is the video
credits :
Thread link for magisk hide props config module: https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228
DEV for magisk hide props config module : Didgeridoohan
you can donate him at : https://www.paypal.me/didgeridoohan
Click to expand...
Click to collapse
Hi!
At the end of the tutorial my phone was not there (redmi note 8 pro) so what i need to do if my phone is not to the list????
roberto_1986 said:
Hi!
At the end of the tutorial my phone was not there (redmi note 8 pro) so what i need to do if my phone is not to the list????
Click to expand...
Click to collapse
Pick whatever device on the list that's closest, or help with finding a working, certified print for your device.
Didgeridoohan said:
Pick whatever device on the list that's closest, or help with finding a working, certified print for your device.
Click to expand...
Click to collapse
its safe??? because it change my phone fingerprint....
---------- Post added at 02:04 AM ---------- Previous post was at 01:09 AM ----------
roberto_1986 said:
its safe??? because it change my phone fingerprint....
Click to expand...
Click to collapse
also for get fingerprint u need to have both CTS profile and basic integrity set to true (not in my case because CTS is set to false)
so someone can get his finger pring from a redmi note 8 pro???
Magisk Module Systemless Debloater
Download:
GitHub - zgfg/SystemlessDebloater: Select and systemlessly debloat preinstalled system apps. Supporting up to System As Root (SAR), Dynamic partitions and Android 13. Module must be installed through Magisk app, not TWRP
Select and systemlessly debloat preinstalled system apps. Supporting up to System As Root (SAR), Dynamic partitions and Android 13. Module must be installed through Magisk app, not TWRP - GitHub - ...
github.com
GitHub - Magisk-Modules-Alt-Repo/SystemlessDebloater: Select and systemlessly debloat preinstalled system apps. Supporting up to System As Root (SAR), Dynamic partitions and Android 13. Module must be installed through Magisk app, not TWRP
Select and systemlessly debloat preinstalled system apps. Supporting up to System As Root (SAR), Dynamic partitions and Android 13. Module must be installed through Magisk app, not TWRP - GitHub - ...
github.com
Wiki pages by @ipdev:
ConfigScript
Guide for the Systemless Debloater Module. Contribute to mModule/guide_sDebloater development by creating an account on GitHub.
github.com
with his examples of apps that can be debloated (Android, Google, Oppo, Samsung, Xiaomi, LineageOS):
CommunityList
Guide for the Systemless Debloater Module. Contribute to mModule/guide_sDebloater development by creating an account on GitHub.
github.com
*** Yet another System(less) debloater, how and why?
- Systemless means that all changes made are active only when Magisk is loaded and module is enabled.
For OTA or anything, just disable the module (or boot without Magisk) and your system partitions are no more affected
- For Android up to 9 and/or 10 (depending on devices), system partitions were read-write, hence hard-debloating by use of eg TWRP, Titanium, etc (to delete the pre-installed system apps) was possible
This is no more possible for the phones released with Android 10 and higher.
System (System As Root, Dynamical partitions) becomes read-only on the file-system level and stock apps could be debloated (the same holds for any changes on the system partitions) only by the systemless approach - by use of Magisk to dynamically overlay the required changes at boot time
Hence, this module also uses the Magisk REPLACE mechanism and dynamical mounting through the module's service.sh script
- The module debloates only (stock) apps pre-installed to the system partitions, traditionally named as /system, /system-ext, /product, /vendor and /apex; plus additionally on A12 and A13 devices, variably named system partitions like /india, /my_bigball, etc
Hence sorry, to debloat user apps installed to /data, please use the other methods (first of all, just simply uninstall them or at least uninstall their updates)
- Originally I started development with Xiaomi Mi 9T (MIUI 10-12.5, Android 10-12) and later continued with Xiaomi 11 Lite 5G NE (MIUI 12-13, Android 11-12). However, the module relies on the common Magisk overlay mechanism and the list of apps to be 'debloated' is configurable hence there are many users who successfully use this module on the various other devices (like Pixel, Samsung, One Plus, etc.), with the stock or custom ROMs, and with up to Android 13
- Original, default list coming when the module is installed will be empty - user must define then himself which apps should be debloated, depending on his device, ROM and preferences
To (re)configure the list of apps for debloating, simply edit the (textual) /Download/SystemlessDebloater.cfg config file on Internal memory.
Module automatically installs the config file with instructions inside but with the empty list
(Re)configure your list of system apps you want to debloat, reinstall the module (always through the Magisk Manager, not TWRP) and reboot - to take your changes in effect
You only need to provide the proper names (not package names) for the preinstalled system apps, the module will find their exact System paths
- However, the user bears the risks and responsibility himself (device may no more boot when certain system apps are removed/debloated) but the Troubleshooting section below provides instructions how to recover, even from the bootloop cases
Nevertheless, whenever you want to 'debloat' some service or app you are not familiar with, please google first to find what that app is really about and is it generally safe to be debloated (on your but also on the other phones and even by other methods, it doesn't matter)
Don't be afraid of the module and debloating, but be cautious what are you going to debloat
*** Installation
- Download the latest module from GitHub - scroll down, open Assets and find the latest v1.5.3 zip:
https://github.com/zgfg/SystemlessDebloater/releases/tag/153
- In Magisk app (manage), open Modules tab and take Install from storage, navigate to the downloaded SystemlessDebloater.zip (as is, do not unzip)
Read what Magisk prints while installing and find the module's log in /Download/SystemlessDebloater.log file on Internal memory
To finish the installation (it applies to all Magisk modules), reboot the phone
- First time the module will not debloat anything - it will just create the input/config file /Download/SystemlessDebloater.cfg on Internal memory
Open that config file, read the instructions in the file and fill your own list of app names for debloating - look at the commented examples you will find in that config file
- Save the config file, reinstall the module and reboot.
Inspect the log and consult the Troubleshooting section below if needed
- To find what system apps you have on your phone and what are their exact names, scroll down through the SystemlessDebloater.log to the "System apps, not debloated" section
Find e.g. a line:
/system/app/Email (com.android.email)
Then copy/add just the Email name (supposed that you want to debloat the built-in Email app) into the SystemlessDebloater.cfg config file
Repeat for the other apps you want to debloat. Then reinstall the module (only on the reinstallation, module processes the config file) and reboot
Fine tune your list of apps for debloating but every time reinstall the module and reboot
- Last but not the least: Once debloated, apps can no more be found (until you reconfigure, disable or uninstall the debloater) under the Settings / Apps
Hence, if you want to delete their cache or data, do Clear cache/data before debloating the apps
Moreover, before trying to debloat any app, look first if you could simply Uninstall that app (ie, if it was a user and not the system app) from Settings / Apps
If Uninstall is not available for that app, try to Uninstall updates: updates are also installed to Data while SystemlessDebloater 'debloats' only from the System - hence the app's update on Data may still remain there
*** Troubleshooting
- What if I eg have configured the app EMail to debloat, but the app is still present?
Check if you have missed to perform Uninstall / Uninstall updates from Settings, Apps - perform, reboot and test again
Check if you have miss-spelled the application name - correct in the config file SystemlessDebloater.cfg, save, reinstall the module and reboot
App names are cases sensitive - eg, the correct name might be Email, not EMail
- To help yourself, use eg Package Manager app (from Playstore) where you can search for all the apps/services, find their exact names and installation paths (to see are them System or User apps)
- What if I change my mind and I want to un-debloat and use Email, but to debloat now eg, Chrome browser?
No problem, reconfigure the list in SystemlessDebloater.cfg, save, reinstall the module and reboot
- What if after a week or so, I realize that some functionalities on the phone were affected?
Sorry, you had decided to debloat the 'wrong' apps/services
Google about which app(s) are safe to debloat or not, reconfigure your list in the config file, reinstall the module and reboot
Or disable the module and reboot, to figure out was the problem really due to debloating
- Oops, what if I have a bootloop (phone does no more boot since the 'wrong' apps were debloated)?
If you have TWRP with the read/write access to Data, navigate to /data/adb/modules/SystemlessDebloater and by using Advanced / File explorer from TWRP, create a dummy file named disable (without extension) in that folder
Reboot and Magisk will boot but with the debloater disabled - hence, all the previously debloated apps will be un-debloated now (to see if debloating was really responsible for the bootloop)
Instead of dummy file named disable, put the remove dummy file to trigger Magisk to uninstall that module on the next reboot (all that applies to any module possibly causing your bootloops)
If the proper TWRP is not available for your device and ROM, boot to the Android Safe Mode - google for a key-combo to boot in, for my Xiaomi it takes (re)booting with Vol+ and Vol+ pressed simultaneously
Don't do anything in Android Safe mode but reboot then to 'normal' mode - Magisk will boot now with all the modules disabled (this method does not work for Magisk v20.4 or earlier)
You will have to re-enable MagiskHide/DenyList (don't worry, your list of apps to hide the Magisk from was not lost), re-enable the other modules, correct SystemlessDebloater.cfg, reinstall debloater and reboot
There is also a third method (adb wait-for-device shell magisk --remove-modules), but search yourself and read about from the Wiki Documentation on the Magisk GitHub page
*** Enough for the theory, install now and practice debloating
IMPORTANT
Since the version v1.5.1, SystemlessDebloater module supports a new SystemlessDebloater.cfg config file - thanks to @ipdev
Update will create the new config file and transfer your DebloatList
Please delete then your old SystemlessDebloaterList.sh input file and read and use the new config file instead
---
For more info about the SystemlessDebloater.cfg config file, please see: Wiki pages from @ipdev:
ConfigScript
Guide for the Systemless Debloater Module. Contribute to mModule/guide_sDebloater development by creating an account on GitHub.
github.com
and his examples what apps can be debloated (Android, Google, Oppo, Samsung, Xiaomi, LineageOS):
CommunityList
Guide for the Systemless Debloater Module. Contribute to mModule/guide_sDebloater development by creating an account on GitHub.
github.com
On my Xiaomi Mi 9T, eea Stable QFJEUXM 12.0.2 I safely debloat the following apps:
Code:
DebloatList="
AnalyticsCore
AntHalService
BasicDreams
BookmarkProvider
CatchLog
Chrome
CneApp
EasterEgg
facebook-appmanager
facebook-installer
facebook-services
FileExplorer_old
GlobalFashiongallery
GlobalMinusScreen
Gmail2
GoogleFeedback
GooglePartnerSetup
HybridAccessory
HybridPlatform
IdMipay
InMipay
Joyose
MiBrowserGlobal
MiBrowserGlobalVendor
MiCreditInStub
MiDrop
MiLinkService2
MiPicks
MiPlayClient
MiRcs
MiRecycle
MiService
MiuiBrowserGlobal
MiuiBugReport
MiuiDaemon
MSA-Global
Netflix_activation
Notes
PartnerBookmarksProvider
PaymentService
PhotoTable
Stk
TouchAssistant
Traceur
Turbo
uceShimService
Velvet
VsimCore
wps_lite
YellowPage
Zman"
E.g., I debloat YouTube and install Vanced YT root.
Similarly, I debloat GMail, Wellbeing, Netflix, Facebook, Turbo, etc - inspect and exclude from the list those apps you want to keep
Also, DebloatList I used for Mi 9T but Xiaomi.eu weekly 20.9.17 (MIUI 12, Android 10):
Code:
DebloatList="
AndroidAutoStub
AntHalService
BookmarkProvider
Browser
BTProductionLineTool
Calculator
CatchLog
CneApp
EasterEgg
Email
GoogleFeedback
GooglePartnerSetup
Health
Joyose
Lens
MiMover
MiPlayClient
MiRecycle
MiService
MiuiBugReport
MiuiDaemon
Notes
PaymentService
Stk
TouchAssistant
Traceur
uceShimService
Velvet
VsimCore
WebViewGoogle
wps_lite"
and for Xiaomi.eu Stable 12.0.6:
Code:
DebloatList="
AndroidAutoStub
AntHalService
BookmarkProvider
Browser
BTProductionLineTool
Calculator
CatchLog
CneApp
EasterEgg
Email
GoogleFeedback
GooglePartnerSetup
Health
Joyose
Lens
MiMover
MiPlayClient
MiRecycle
MiService
MiuiBugReport
MiuiDaemon
Notes
PaymentService
Stk
TouchAssistant
Traceur
uceShimService
Velvet
VsimCore
WebViewGoogle
wps-lite"
You may exclude e.g., Calculator,Email, Health or Lens, if you want to use them.
You can expect most of these apps also on the other MIUI firmwares. Installation folders on System may vary, but module will find their paths
EDIT:
SystemDebloaterList.sh and DebloatList were used in the module versions v1.5.0 and earlier, since v1.5.1 the module uses SystemDebloater.cfg
Thanks a lot to @ipdev for discussing and sharing ideas, encouraging and for successful testing on Xiaomi Poco F2 (debloater found most of the same MIUI apps as above) and OnePlus 5T
Also, thanks for your successful test on Pixel 3aXL with Android 11:
ipdev said:
Works on Pixel 3aXL. (Stock Android 11. Magisk canary.)
Attached the SystemlessDebloater.log from 3aXL.
And the SystemlessDebloaterList.sh I use for testing. (remove the .txt)
Click to expand...
Click to collapse
Reserved
Over the weekend when I have time to fix any potential bricking or boot loops, I'm going to try this on my A/B device (One Plus 7Pro, GM1917, OOS 10.3.5) ... unless before then anyone indicates that this is not even likely to work on my phone.
If I end up doing this, I'll report my results.
.
HippoMan said:
Over the weekend when I have time to fix any potential bricking or boot loops, I'm going to try this on my A/B device (One Plus 7Pro, GM1917, OOS 10.3.5) ... unless before then anyone indicates that this is not even likely to work on my phone.
If I end up doing this, I'll report my results.
.
Click to expand...
Click to collapse
It does not matter if it system-as-root or a slot device.
By time modules are run, system paths are set.
The active slot partition is running, and (if needed) switch root has happened.
Root directory is set to / and system directory is set to /system
curious about OxygenOS, do not run it very much so I am not sure what should/could be removed.
Cheers.
PS.
Works on Pixel 3aXL. (Stock Android 11. Magisk canary.)
Attached the SystemlessDebloater.log from 3aXL.
And the SystemlessDebloaterList.sh I use for testing. (remove the .txt)
Quick edit.
Since the back-side move for xda is still going, there are some errors while in transition.
Since attachment is not working at the moment. GoogleDrive - Link
ipdev said:
It does not matter if it system-as-root or a slot device.
By time modules are run, system paths are set.
The active slot partition is running, and (if needed) switch root has happened.
Root directory is set to / and system directory is set to /system
curious about OxygenOS, do not run it very much so I am not sure what should/could be removed.
Cheers.
PS.
Works on Pixel 3aXL. (Stock Android 11. Magisk canary.)
Attached the SystemlessDebloater.log from 3aXL.
And the SystemlessDebloaterList.sh I use for testing. (remove the .txt)
Click to expand...
Click to collapse
OxygenOS isn't as bad, bloat-wise, as some other OS's, such as what comes with Samsung. But there are still things that I don't want, such as the OnePlus camera and a few other items.
I'll report back here after I try this.
.
ipdev said:
It does not matter if it system-as-root or a slot device.
By time modules are run, system paths are set.
The active slot partition is running, and (if needed) switch root has happened.
Root directory is set to / and system directory is set to /system
curious about OxygenOS, do not run it very much so I am not sure what should/could be removed.
Cheers.
PS.
Works on Pixel 3aXL. (Stock Android 11. Magisk canary.)
Attached the SystemlessDebloater.log from 3aXL.
And the SystemlessDebloaterList.sh I use for testing. (remove the .txt)
Click to expand...
Click to collapse
Thank you for testing on A11.
Log cannot be downloaded, 404?
zgfg said:
Thank you for testing on A11.
Log cannot be downloaded, 404?
Click to expand...
Click to collapse
Looks like some more hiccups on xda back-side again.
Will be nice once the transition is complete, xda will be fast and stable again. :fingers-crossed:
Updated my prior post with a gDrive Link.
If you look at the log, you will notice chrome is not debloated.
The stub is debloated, Chrome (Think it is in product/app) is a gzip version of the Chrome apk.
Chrome is automatically installed into /data/app/HashStringOrSomething/com.android.chrome-HashStringOrSomething/Chome.apk
I have not taken time to look into that change.
Cheers.
ipdev said:
Looks like some more hiccups on xda back-side again.
Will be nice once the transition is complete, xda will be fast and stable again. :fingers-crossed:
Updated my prior post with a gDrive Link.
If you look at the log, you will notice chrome is not debloated.
The stub is debloated, Chrome (Think it is in product/app) is a gzip version of the Chrome apk.
Chrome is automatically installed into /data/app/HashStringOrSomething/com.android.chrome-HashStringOrSomething/Chome.apk
I have not taken time to look into that change.
Cheers.
Click to expand...
Click to collapse
Interesting - what happens when you debloat Chrome-Stub from Product and leave Chrome on Data, does it still run?
Btw, I do use Chrome (because of the integrated translator, making me easy to sometimes read worldwide forums if needed) and I didn't want to debloat originally. However, my preinstalled version on Product was not the latest, and Google Play was offering me to update, but updating Chrome was always failing.
I downloaded the apk from ApkMirror but installation had also failed
Then I debloated (at that time, prior to this debloater I used to manually create my system folder given to Magisk to overlay, and with dummy apk instead of with .replace file) and only then I was able to install Chrome apk (ofc to Data) and since then, to regularly update it through Playstore
One more thing. I've found some people claiming that Chrome breaks to run if Playstore shows Device is not certified.
But back in the spring when Google started to play with enforcing CTS Profile Hardware attest, and prior than @Displax invented ro.product.model spoofing (to force Basic attest and to pass CTS/SafetyNet, to get Device certified), my CTS was failing and Device was not Certified but I had no problems using Chrome on daily basis
---
Also, you have PrebuiltGmail and Music2, I had Gmail2 and FileExplorer_old (I had to use Package Manager to find that Gmail was installed as Gmail2/Gmail2.apk and similarly the Android FileExplore as FileExplorer_old.apk)
Btw all Mi* and Miui* stuff apply only for debloating Xiaomi
In your input list you have lite and wps (both are not found in the log), mine was wps_lite (WPS preinstalled to Vendor) - please check
zgfg said:
Interesting - what happens when you debloat Chrome-Stub from Product and leave Chrome on Data, does it still run?
Btw, I do use Chrome (because of the integrated translator, making me easy to sometimes read worldwide forums if needed) and I didn't want to debloat originally. However, my preinstalled version on Product was not the latest, and Google Play was offering me to update, but updating Chrome was always failing.
I downloaded the apk from ApkMirror but installation had also failed
Then I debloated (at that time, prior to this debloater I used to manually create my system folder given to Magisk to overlay, and with dummy apk instead of with .replace file) and only then I was able to install Chrome apk (ofc to Data) and since then, to regularly update it through Playstore
One more thing. I've found some people claiming that Chrome breaks to run if Playstore shows Device is not certified.
But back in the spring when Google started to play with enforcing CTS Profile Hardware attest, and prior than @Displax invented ro.product.model spoofing (to force Basic attest and to pass CTS/SafetyNet, to get Device certified), my CTS was failing and Device was not Certified but I had no problems using Chrome on daily basis.
Click to expand...
Click to collapse
PlayStore issues are weird at best.
Hit or miss, depends on the device and/or setup.
Certificataion does not seem to play a big part over all.
If it does then Google's has more issues than fixing SafetyNet to worry about.
Sometimes it is just a Google being Google.
I will look into Chrome tomorrow.
I normally use Chrome Dev PlayStore - Link.
More so now, Brave Browser PlayStore - Link.
zgfg said:
Also, you have PrebuiltGmail and Music2, I had Gmail2 and FileExplorer_old (I had to use Package Manager to find that Gmail was installed as Gmail2/Gmail2.apk and similarly the Android FileExplore as FileExplorer_old.apk)
Btw all Mi* and Miui* stuff apply only for debloating Xiaomi
In your input list you have lite and wps (both are not found in the log), mine was wps_lite (WPS preinstalled to Vendor) - please check
Click to expand...
Click to collapse
No harm checking for apps that do not exist on the device.
It may cause extra lines in the log file and one or two seconds of install time.
My bad.
Must have split wps_lite when I was adjusting the list. Then when sorting, it just put lite and wps in the correct order.
---
I re-flashed and/or reverted a few phones tonight and added them to the gDrive Link.
The files listed as _pfile.list (preinstalle files) are a list of files located in app and/or priv-app of system, product and vendor.
I use a shell scripts for this kind of stuff, [ because I am lazy ] primarily with adb shell.
I adjusted the one I use to make the pfile list.
list_pfiles.sh - Still needs to be run as root.
list_pfiles.sh needs to be located in a writable directory. (sdcard/Download | data/local/tmp | ...)
It still uses a static NAME= variable that you will want to change.
I added a few things to make it run from a root file manager like fx or mix.
With the addition (work from a file manager app/or called from a diferent directory), if you rename the script file, you will also have to adjust the SCRIPT= variable to match.
Cheers.
Edit:
2021.Aug.21
I updated the list_pfiles script.
To Use:
Copy this script to the device.
Recommended to use the /sdcard/Download/ directory.
Run from adb shell (or a terminal app) using the sh command.
sh list_pfiles.sh
Run from a file manager that is able to execute a script file.
Note: May or may not work depending on file manager..
ipdev said:
PlayStore issues are weird at best.
Hit or miss, depends on the device and/or setup.
Certificataion does not seem to play a big part over all.
If it does then Google's has more issues than fixing SafetyNet to worry about.
Sometimes it is just a Google being Google.
I will look into Chrome tomorrow.
I normally use Chrome Dev PlayStore - Link.
More so now, Brave Browser PlayStore - Link.
No harm checking for apps that do not exist on the device.
It may cause extra lines in the log file and one or two seconds of install time.
My bad.
Must have split wps_lite when I was adjusting the list. Then when sorting, it just put lite and wps in the correct order.
---
I re-flashed and/or reverted a few phones tonight and added them to the gDrive Link.
The files listed as _pfile.list (preinstalle files) are a list of files located in app and/or priv-app of system, product and vendor.
I use a shell scripts for this kind of stuff, [ because I am lazy ] primarily with adb shell.
I adjusted the one I use to make the pfile list.
list_pfiles.sh - Still needs to be run as root.
list_pfiles.sh needs to be located in a writable directory. (sdcard/Download | data/local/tmp | ...)
It still uses a static NAME= variable that you will want to change.
I added a few things to make it run from a root file manager like fx or mix.
With the addition (work from a file manager app/or called from a diferent directory), if you rename the script file, you will also have to adjust the SCRIPT= variable to match.
Cheers.
Click to expand...
Click to collapse
Pixel comes with only G stuff but interestingly, without Wellbeing
Velvet.apk, what is the package name (you should still be able to find the name on /data/data)?
When you have Velvet (Poco F1, F2 and One+ 5T), do they also have Google.apk = com.google.android.googlequicksearchbox?
Btw, if you use MiXPlorer and choose Tools, App Remnants, you can see /data/data folders for debloated apps (and you can remove them)
HippoMan said:
Over the weekend when I have time to fix any potential bricking or boot loops, I'm going to try this on my A/B device (One Plus 7Pro, GM1917, OOS 10.3.5) ... unless before then anyone indicates that this is not even likely to work on my phone.
If I end up doing this, I'll report my results.
Click to expand...
Click to collapse
I did it just now, and it worked wth no problems on my device! For my initial test, I used SystemlessDebloater to remove GooglePartnerSetup, and it was indeed removed. No bootloops, no problems.
Good work on this module!
zgfg said:
...
Btw, if you use MiXPlorer and choose Tools, App Remnants, you can see /data/data folders for debloated apps (and you can remove them)
Click to expand...
Click to collapse
Well, in my case, GooglePartnerSetup doesn't appear anywhere among MiXPlorer's "App Remnants", even though other /data/data items are indeed being displayed there. But this is not causing any kind of issue on my device, so I am not concerned.
.
zgfg said:
Pixel comes with only G stuff but interestingly, without Wellbeing
Click to expand...
Click to collapse
Don't worry, Google would not forget to bundle it.
Digital wellbeing is named WellbeingPrebuilt.
package: name='com.google.android.apps.wellbeing'
I just did not add it to the debloat list.
zgfg said:
Velvet.apk, what is the package name (you should still be able to find the name on /data/data)?
When you have Velvet (Poco F1, F2 and One+ 5T), do they also have Google.apk = com.google.android.googlequicksearchbox?
Click to expand...
Click to collapse
Velvet is Google.
package: name='com.google.android.googlequicksearchbox'
As far as I know, Velvet is the bundled and/or GApps name used.
Cheers.
HippoMan said:
I did it just now, and it worked wth no problems on my device! For my initial test, I used SystemlessDebloater to remove GooglePartnerSetup, and it was indeed removed. No bootloops, no problems..
Click to expand...
Click to collapse
Just a short question - you have A11 on your OnePlus 7Pro?
zgfg said:
Just a short question - you have A11 on your OnePlus 7Pro?
Click to expand...
Click to collapse
One Plus 7Pro, GM1917, OOS 10.3.5 ... as I mentioned above OOS 10.x is A10.
.
zgfg said:
Interesting - what happens when you debloat Chrome-Stub from Product and leave Chrome on Data, does it still run?
Btw, I do use Chrome (because of the integrated translator, making me easy to sometimes read worldwide forums if needed) and I didn't want to debloat originally. However, my preinstalled version on Product was not the latest, and Google Play was offering me to update, but updating Chrome was always failing.
I downloaded the apk from ApkMirror but installation had also failed
Then I debloated (at that time, prior to this debloater I used to manually create my system folder given to Magisk to overlay, and with dummy apk instead of with .replace file) and only then I was able to install Chrome apk (ofc to Data) and since then, to regularly update it through Playstore
Click to expand...
Click to collapse
Still have to test some more.
So far only on my Pixel aOS 11.
This is a little tricky to explain my testing/findings.
- Long post, truncated it for now. -
Not logged into Google. (PlayStore)
With Chrome stub active, Chrome is treated as a system app.
Even though the full version is in data it can not be uninstalled only disabled.
PlayStore shows an available update for Chrome.
If stub is removed (debloated), Chrome is treated as a user app.
You have the option to uninstall.
PlayStore does NOT show an update for Chrome.
Did not matter if I cleared cache and/or data on PlayStore or re-scan with with PlayProtect.
This is odd, since Google should still want to update even if it is just a user app.
I'll have to dig though the user agreement again.
Might be automatic update only when Google apps are included (system app) when not logged in.
--
As soon as I logged in, Google immediately updated some back-end.
Chrome is now available for an update and it updated fine.
This is also where some oddities came in.
--
<TRUNCATE>
--
Still have to double check everything.
Seems to be an issue distinguishing between system and user apps.
Should have time this weekend to redo and verify every step I used for testing.
As of now, I would suggest the same as you did it.
Debloat Chrome (stub)
Uninstall Chrome (should be considered a user app after the debloate.)
Install from another source (if need be then update from PlayStore.) or just install from PlayStore.
Cheers.
Btw, released v1.3.5 through the OP post #1 - just to log to the logfile the Android version, is it SAR and is it A/B - would be nice if you can test does it log correctly when you have time and A/B device.
Unfortunately, still unable to resolve a miss-communication with the bot to successfully submit to Repo
Can somebody dhare his debloat app list? Or the best, .sh file? İt would be great
I'm NOT a gapps user so I will NOT be participating in this thread. I'm not supporting or answering any gapps project questions.
This thread is for users who want/need to run gapps with 19.1 on exynos5433 devices like SM-T710 and SM-T810
I opened this thread as a courtesy for users who want/need gapps.
At last count there were 5 gapps projects and they are in various states of "working" wrt to 19.1. It's your responsibility to put in some hours of research to find out what gapps works for you.
All I can say is that some testers report that NikGapps 12.1L arm64 core (May 1, 2022) work. Despite the arm64 name, that version WILL work on exynos5433. Your mileage may vary.
https://sourceforge.net/projects/nikgapps/files/Releases/NikGapps-SL/01-May-2022/
Reserved.
I can confirm that I have successfully installed NikGapps Core along with @retiredtab's T170 and T810 LOS19.1 ROMs. I have my complete set of Google Play Apps available to me on the tablet after installing them, including sensitive ones such as Peacock, Netflix, Disney+, etc. All Apps run normally, and when I check Google Play/Settings and scroll to the bottom, I see “Device is certified”.
I've tried to install BitGapps pico + Flamegapps basic (both ARM and ARM64 versions).
NikGapps64 finally worked.
pflyaz said:
I can confirm that I have successfully installed NikGapps Core along with @retiredtab's T170 and T810 LOS19.1 ROMs. I have my complete set of Google Play Apps available to me on the tablet after installing them, including sensitive ones such as Peacock, Netflix, Disney+, etc. All Apps run normally, and when I check Google Play/Settings and scroll to the bottom, I see “Device is certified”.
Click to expand...
Click to collapse
Installed the ROM on clean wipe on Galaxy Tab S2 T810. Then NikGapps Full thru Basic in different tries.
1. With NikGapps Full to Basic there is no onscreen keyboard that comes up to set up wifi or PIN. Only a Google Voice typing error shows up. How is this solved?
2. After set up without Wifi, the tablet says "Tablet starting....." and does not go further.
Any ideas welcome....
chappatti said:
Installed the ROM on clean wipe on Galaxy Tab S2 T810. Then NikGapps Full thru Basic in different tries.
1. With NikGapps Full to Basic there is no onscreen keyboard that comes up to set up wifi or PIN. .....
Click to expand...
Click to collapse
Did you "format data"?
That solved it on mine (with the 2nd flash) testing the prealpha build.
I took only core instead of basic.
I had this in my 19.1 msm8916 post #1, but forgot to add it to exynos5433 post #1. The following is now added to 19.1 T710 and T810 post #1. This would also apply to things like wifi password, etc, not just bluetooth pin.
keyboard bug workaround. When prompted to enter something like a Bluetooth pin, sometimes the keyboard is not shown on the screen or off screen. The workaround is to bring up the built in browser, touch the url panel where the http address is and then press the number key when the keyboard pops up. Leave this browser open like that, then press the home button and try your Bluetooth pairing again.
This keyboard bug is a LineageOS bug as per
https://review.lineageos.org/c/LineageOS/android_packages_inputmethods_LatinIME/+/325438
chappatti said:
Installed the ROM on clean wipe on Galaxy Tab S2 T810. Then NikGapps Full thru Basic in different tries.
1. With NikGapps Full to Basic there is no onscreen keyboard that comes up to set up wifi or PIN. Only a Google Voice typing error shows up. How is this solved?
2. After set up without Wifi, the tablet says "Tablet starting....." and does not go further.
Any ideas welcome....
Click to expand...
Click to collapse
I figured this out and everything runs good.
I used two files (one file in attachment). The zip file is flashed from TWRP. I also installed the Gboard apk from :
Gboard - the Google Keyboard 12.1.06.463429027-beta (arm-v7a) (nodpi) (Android 6.0+) APK Download by Google LLC - APKMirror
Gboard - the Google Keyboard 12.1.06.463429027-beta (arm-v7a) (nodpi) (Android 6.0+) APK Download by Google LLC - APKMirror Free and safe Android APK downloads
www.apkmirror.com
and apk was installed normally. Gboard gets installed and all is good. I think the apk alone should do it, but I did not try that alone. (For some reason attaching the apk file to this post fails). Once this is done and the Wifi is set up one can then download any other keyboard they want from app store.
Also, I don't recommend using NikGapps above "basic", on Tab S2 T810. A Gapp keeps crashing and the tablet is stuck on "Tablet starting.....".
I downloaded Basic NikGapps from here: https://sourceforge.net/projects/nikgapps/files/Releases/NikGapps-SL/09-Jul-2022/
retiredtab said:
I had this in my 19.1 msm8916 post #1, but forgot to add it to exynos5433 post #1. The following is now added to 19.1 T710 and T810 post #1. This would also apply to things like wifi password, etc, not just bluetooth pin.
keyboard bug workaround. When prompted to enter something like a Bluetooth pin, sometimes the keyboard is not shown on the screen or off screen. The workaround is to bring up the built in browser, touch the url panel where the http address is and then press the number key when the keyboard pops up. Leave this browser open like that, then press the home button and try your Bluetooth pairing again.
This keyboard bug is a LineageOS bug as per
https://review.lineageos.org/c/LineageOS/android_packages_inputmethods_LatinIME/+/325438
Click to expand...
Click to collapse
Please see my post above.
I struggled with Installing Gapps on the latest Nov 11, 2022 release.
Tried:
NikGapps NikGapps-core-arm64-12.1-20220908-signed.zip and NikGapps-basic-arm64-12.1-20220908-signed.zip - both installs without issues in TWRP but no Play store or any other apps in the system.
BiTGApps-arm64-12.1.0-v1.7_signed.zip - fails with error "unsupported platform"
BiTGApps-arm-12.1.0-v1.7_signed.zip - installed and Play Store is visible. Get it here https://bitgapps.github.io/download.html
Pawel_ said:
I struggled with Installing Gapps on the latest Nov 11, 2022 release.
Tried:
NikGapps NikGapps-core-arm64-12.1-20220908-signed.zip and NikGapps-basic-arm64-12.1-20220908-signed.zip - both installs without issues in TWRP but no Play store or any other apps in the system.
BiTGApps-arm64-12.1.0-v1.7_signed.zip - fails with error "unsupported platform"
BiTGApps-arm-12.1.0-v1.7_signed.zip - installed and Play Store is visible. Get it here https://bitgapps.github.io/download.html
Click to expand...
Click to collapse
I installed NikGapps-omni-arm64-12.1-20220709-signed.zip from twrp and it is working well. I have the play store.
I was surprised to see that it is an arm64 version even though ( I thought that) the t710 (exynos) has an arm32 processor.