Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I decided to continue @PunchyStick's Magisk module and keep it updated as F-Droid releases updates. You can generally expect updates the day after if not the day of F-Droid updating the extension.
What to know:
-Please make sure you're running at least F-Droid 0.103
-Disable auto app updates from within F-Droid. F-Droid Privileged Extension will automatically update and succeed, and I don't know how this will affect SafetyNet and/or the Magisk Module. (This is because the extension doesn't update like a normal app by placing updates in the data partition, it overwrites the apk in system directly).
Changelog:
v1
- Private release
- Privileged Extension 0.1
- Based directly on PunchyStick's extension
v2
- Private release
- Privileged Extension 0.2
v3
- Private release
- Privileged Extension 0.2.2
v4
- First public release
- Privileged Extension 0.2.3
v5
-If you installed the zip on the XDA thread, please remove that module before installing this version.
-Privileged Extension 0.2.4
v6
-Privileged Extension 0.2.5
-Please update F-Droid to version 0.103 if you have not already.
v7
-Updated to template 4
v8
-Update to template 1400
-Please update to Magisk 14.0 if you have not already
v9
-Privileged Extension 0.2.6
v10
-Privileged Extension 0.2.7
-Template 1410
-Only install this if you are on Magisk 14.1, a zip for Magisk 14.0 can be found attached.
I removed the module zip from this thread as it is obsolete and my module is in the Magisk Module Repo now (and thus can be installed via Magisk). Also, as per the changelog, if you installed the zip on this thread please uninstall that module before upgrading to v5.
Reserved
Mine 2.0
Please correct me if I'm wrong, but this module is not using the latest module template. Yes, it has the "template" tag in module.prop, but everything else seems old, very old. As an example: There's still tags for cache modules (removed in Magisk v9) in config.sh and the update-binary file used seems to be of a similar age...
An update on my last post.
It's this commit that by mistake (obviously) reverted all the changes from module template v3 (and then some).
Didgeridoohan said:
Please correct me if I'm wrong, but this module is not using the latest module template. Yes, it has the "template" tag in module.prop, but everything else seems old, very old. As an example: There's still tags for cache modules (removed in Magisk v9) in config.sh and the update-binary file used seems to be of a similar age...
Click to expand...
Click to collapse
I will look into that, but I synced this straight from the Magisk Template repo then rebuilt from there so the legacy code should be gone. I use multiple devices so I might have accidentally fudged something up. Also, do note that this repo is the one I will be updating now that it has been accepted into the Magisk module's repo, and on that one I think I fixed my little screwup.
Sent from my Nexus 6P using XDA Labs
ryaniskira said:
I will look into that, but I synced this straight from the Magisk Template repo then rebuilt from there so the legacy code should be gone. I use multiple devices so I might have accidentally fudged something up. Also, do note that this repo is the one I will be updating now that it has been accepted into the Magisk module's repo, and on that one I think I fixed my little screwup.
Sent from my Nexus 6P using XDA Labs
Click to expand...
Click to collapse
Nice. That's the repo I was looking at, yes, and after a (very) quick look it does look like it's been fixed.
Lol i like that mine thing! Thanks for the work. I'll check it out later as I've been overwhelmingly busy as of late
Miras77 said:
Zuk z2
Click to expand...
Click to collapse
??
Uhmm.. excuse me if this sounds like a dumb question, but what is F-Droid? And what does it do?
---------- Post added at 08:42 AM ---------- Previous post was at 08:32 AM ----------
CryonicCore said:
Uhmm.. excuse me if this sounds like a dumb question, but what is F-Droid? And what does it do?
Click to expand...
Click to collapse
Nevermind. I was smart and looked it up. Looks interesting though.
CryonicCore said:
Uhmm.. excuse me if this sounds like a dumb question, but what is F-Droid? And what does it do?
---------- Post added at 08:42 AM ---------- Previous post was at 08:32 AM ----------
Nevermind. I was smart and looked it up. Looks interesting though.
Click to expand...
Click to collapse
Alternate app store for stuff, you add repositories to it to have more apps listed, also it can update your currently installed apps from there too if you decide to manually update apps
Does this make the privileged extension work on newer Android versions? Like Nougat?
viggy96 said:
Does this make the privileged extension work on newer Android versions? Like Nougat?
Click to expand...
Click to collapse
Yes. It actually works just fine on all of my devices, all of which are running Nougat.
Bootloop on Sony Xperia X Compat Nougat 7.0
Fresh, fully working Magisk v. 12.0 with Magisk Manager 4.3.3, F-Droid v.103, after installinf F-Droid Privileged Extension Magisk Module, ended in bootloop. Disabling module through recovery causes device to boot, but SystemUI.apk crashes, removing module through recovery (empty remove file in module directory) causes the same.. Uninstalling Magisk using Magisk Uninstall doesn't help either, had to flash my system new....
ondrejvaroscak said:
Fresh, fully working Magisk v. 12.0 with Magisk Manager 4.3.3, F-Droid v.103, after installinf F-Droid Privileged Extension Magisk Module, ended in bootloop. Disabling module through recovery causes device to boot, but SystemUI.apk crashes, removing module through recovery (empty remove file in module directory) causes the same.. Uninstalling Magisk using Magisk Uninstall doesn't help either, had to flash my system new....
Click to expand...
Click to collapse
Odd, I will have to look into that. All the module does is place the privileged extension in the privileged app directory, so if you do not mind, can you make a backup of system and then use Terminal Emulator App Systemizer and place an app in /system/priv-app? Also, is it possible you managed to collect the logs from Magisk?
ryaniskira said:
Odd, I will have to look into that. All the module does is place the privileged extension in the privileged app directory, so if you do not mind, can you make a backup of system and then use Terminal Emulator App Systemizer and place an app in /system/priv-app? Also, is it possible you managed to collect the logs from Magisk?
Click to expand...
Click to collapse
Hm, may there be a glitch that I am using Magisk to have my system partition intact, so writing anything to /system/priv-app is actually not what I wanted? Also, puting a backup of system partition did not help, SystemUI crashed still. Only wiping /data helped...
I am afraid that collecting logs may not be possible, since I can't get into system after crash anymore... unless I can somehow acccess the Magisk logs from recovery...
ondrejvaroscak said:
Hm, may there be a glitch that I am using Magisk to have my system partition intact, so writing anything to /system/priv-app is actually not what I wanted? Also, puting a backup of system partition did not help, SystemUI crashed still. Only wiping /data helped...
I am afraid that collecting logs may not be possible, since I can't get into system after crash anymore... unless I can somehow acccess the Magisk logs from recovery...
Click to expand...
Click to collapse
It does not actually place the app in /system/priv-app, it just uses Magisk to spoof it there like any other magisk module does. So it is as if the app is actually there, but your system partition remains untouched.
ryaniskira said:
It does not actually place the app in /system/priv-app, it just uses Magisk to spoof it there like any other magisk module does. So it is as if the app is actually there, but your system partition remains untouched.
Click to expand...
Click to collapse
I thought so, becuase otherwise it would not make any sense
ondrejvaroscak said:
I thought so, becuase otherwise it would not make any sense
Click to expand...
Click to collapse
The reason I asked you to use that module to place an app in /system/priv-app is that some devices [when running stock] do not like things being placed in that directory, and with Magisk it is just as if that app is actually in that directory even though it really isn't so the device will react just how it would if you actually placed it on the system partition for real. Some devices can just have really odd glitches too, for example I have an LG-K330 from a friend, and some Magisk modules that work just fine on my other devices cause it to lose its IMEI (it is not actually gone, but the OS does not see that there is one and it will refuse to connect to a mobile network), and it causes really odd battery issues too.
{
"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"
}
First Ever Android 8.1 for Nexus 5 [Every Month Update]
This is my new project dedicated to all Nexus 5 users!
The goal is to reproduce the Google Pixel 2 system.
It is based on unofficial Unlegacy Android Project 8.1 Beta.
This UBR contains some useful tools that can be easily uninstalled.
What does UBR stand for?
The letters UBR stand for Update By Recovery - a very non conventional way of flashing.
This backup does not contain the EFS partition which holds your personal IMEI number,
that's why you can use it on any Nexus 5 phone!
Why you should install this ROM?
+ Really easy flash by swiping only one button in TWRP!
+ Quick Installation (it usually takes 3 minutes)
+ It works instantly after reboot
+ If the phone is not damaged it will always work
+ It looks like Google Pixel 2 from the box (in 99%)
+ It has extra functions that can be uninstalled (Magisk etc)
– It has a 4 times larger installation file than standard flashable ROM
– Other applications from your Google account will need to be installed manually
Why is it so BIG?
This UBR contains: ROM (298 MB) + OpenGApps Nano (141 MB) + Other Modules/Mods+ Other Google apps.
After installation you can remove all unwanted apps including Magisk (Unroot).
What works:
Almost everything.
What doesn't work:
Trusted face (from Smart Lock)
Fast (Quick) Charging
WakeBlock (wait for the update)
Things to improve:
Xposed Framework (with Pixel NavBar module) breaks the SafetyNet.
If you want to use apps that require the SafetyNet be passed, uninstall Xposed (the navigation bar will return to the AOSP version).
Requirements:
All you need is Google Nexus 5 16/32GB smartphone with TWRP 3.2.1-1 (Team Win Recovery Project) installed.
Download: - You can find the latest version on <Mod Edit> Link removed
Download the First Ever Android 8.1 for Nexus 5: Direct, Dropbox, Mega, Google Drive, OneDrive, Magnet, Torrent.
Installation Guide - make sure you follow all the instructions carefully, without skipping any steps!
FAQ - if you have a problem with my UBR please read the answers to frequently asked questions.
Please download the latest version from official page - use Google to find it.
I will not continue my project here, until this thread is removed.
Do not worry, this project is still being developed (but not here).
THANK YOU FOR YOUR SUPPORT!
First Ever Android 8.1 for Nexus - Battery Life Test
- No Google account
- WiFi Connected
- No Sim Card
- Old battery
My result: 6 DAYS!!!
If you are experiencing bad battery life, please blame your apps like Facebook etc.
Nice, but why starting a new thread?
BIade said:
Nice, but why starting a new thread?
Click to expand...
Click to collapse
I asked the moderator to remove (delete) my previous thread, not to close it.
Did you basically backup the unlegacy rom after editing it? But you can not take the system and simply create an update script flashable ?
miseusegau said:
Did you basically backup the unlegacy rom after editing it? But you can not take the system and simply create an update script flashable ?
Click to expand...
Click to collapse
How do you want to update partitions from ext4 to f2fs by using flashable ZIP?
My UBR (Update By Recovery) is the best solution for beginners, because most people do not read the instructions.
Example (last comment on my website): WiFi doesn't work - please help/fix it!
This is not a bug, you have not updated the TWRP Recovery to version 3.2.1-1 = you have not read the instructions!
You can have the pixel navbar w/o xposed: https://chromloop.com/2016/11/guide-how-to-port-pixel-navigation-bar-animation-to-your-phone/. I'm not sure if it will work with oreo since the guide is for 7.1.2.
CalebQ42 said:
You can have the pixel navbar w/o xposed: https://chromloop.com/2016/11/guide-how-to-port-pixel-navigation-bar-animation-to-your-phone/. I'm not sure if it will work with oreo since the guide is for 7.1.2.
Click to expand...
Click to collapse
Thanks, I will try it, but now I am using Xposed module for Pixel Navbar, unfortunately it breaks the SafetyNet.
You can choose between Pixel Navbar and SafetyNet. To pass the SafetyNet open Xposed Installer app and uninstall it.
KDCloudy's review on YouTube - thanks!
How to enable notification dots:
Go to: Settings -> Apps & notifications -> open Pixel Launcher app -> press the Gear icon -> Notification dots -> Change settings -> On -> Allow
Please download the latest version from official page - use Google to find it.[/COLOR]
I will not continue my project here, until this thread is removed.
Do not worry, this project is still being developed (but not here).
FirstEver said:
I asked the moderator to remove (delete) my previous thread, not to close it.
Click to expand...
Click to collapse
I don't think XDA or most of the forums have an option to delete any post or thread they can only close it. Any reason for deleting the thread? But cause of that you shouldn't stop posting it here.
Issues I have been facing after using it for a week:
1. Poor Bluetooth call quality
2. Random apps crashing (Google Maps/Twitter/Kindle)
3. Random slowness & lags
4. Volume/sound is very low
How do I turn off mobile data without unlocking my lock screen?
---------- Post added at 15:07 ---------- Previous post was at 15:04 ----------
@FirstEver How will we know when new update is available and what are the changes done?
Lag every second.
Excellent!
I've just recovered an old nexus 5 that was in bootloop and installed this rom, and I've never seen this phone working with such a charm, the only downside is the battery, I don't know if disabling automatic brightness is making a big difference, but I see a little gain in it.
Only question I have is how do you update to the newest version? I have the January version and wanted to update to the February without erasing any of my data of course.
Thanks a lot for the easy install and for this amazing rom!
Ps: I have to admit it does crash some apps sometimes, but nothing to worry.
it looks awesome i will try soon
great rom I would like to know how you do to change the font to this rom, since it is not the default one. could you tell me?
How's the in-call volume? Last time I tried an oreo rom in-call volume was non-adjustable and very quiet. In Most of N5 oreo rom volume is super quiet.
It should be fine by default, not ask us to fix it ourselves.
What about Substratum support?
Is NFC working? May quick charge be achieved with flashing DU kernel?
Can anyone post download links please?
Download link
Hi, use this link to download the file
Mod Edit
join the link together
Jack_Forst said:
Hi, use this link to download the file
Mod Edit
join the link together
Click to expand...
Click to collapse
Mod Edit
When the [OP] is ready , he will put a direct link on XDA
Thank you
malybru
Senior Moderator
Guys as this phone is a legend, but the battery sucks.. Did you guys find a battery with close performance as the original one ?
{
"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"
}
Hello
There is a simple module that contain:
Wallpapers from ASUS for their Android phones
ASUS ROG Phone Live Wallpaper app
ASUS ROG Phone Theme app
All credit @linuxct for having shared the ASUS suite tools (original XDA thread).
This module is just a portage of that.
Compatibility:
Magisk (last stable version at least)
An Android phone (oh really ? )
5 minutes of your time
(download, install, reboot and set the wallpaper take too much of your time? REALLY ? )
This should works on any Android Device
Enjoy :good:
Download link:
v1 https://mediafire.com/file/m8ux9e1ac824266/ASUS-Style-Suite.zip/file
v2 https://www.mediafire.com/download/ug5vvm094jwtd4o
Addon
Rog gaming mode profiles link - for Tasker
-----------------------------
Changelog
v2 added - AsusCamera app and some props added, thanks to @gloeyisk
NOTE: All wallpaper are saved on your internal storage.
Thanks for this port.but rog componion controller not work here,force close. Using rr v6.2.1
Sent from my Redmi 5 Plus using XDA Labs
psychoela said:
rog componion controller not work here,force close. Using rr v6.2.1
Sent from my Redmi 5 Plus using XDA Labs
Click to expand...
Click to collapse
Have u try with profiles for Tasker ?
Not workin ROG Companion facing FC, using mido ArrowOS 9.0
arsaam khan said:
Not workin ROG Companion facing FC, using mido ArrowOS 9.0
Click to expand...
Click to collapse
Same as my previous reply https://forum.xda-developers.com/showpost.php?p=77830413&postcount=5
Doesn't Work
So far doesn't work for me either.... Miui 9.6.5 & AEX (tried both) just crashing
Darkstar_Prime said:
So far doesn't work for me either.... Miui 9.6.5 & AEX (tried both) just crashing
Click to expand...
Click to collapse
What's won't works ?
App does not open on DotOS 8.1 axon 7
Rom said:
What's won't works ?
Click to expand...
Click to collapse
My bad... I was vague in describing... I'm using Redmi 4x.... The ROG companion app shows white screen and instantly closes... Tried in Miui 9.6.5, Dot OS 2.5, AEX 5.6 and Bootleggers ROM 3.0(unofficial).. But, the camera app works for normal, HDR and pro modes(video recorders crashes the app)
If boot Caused system UI to crash
If not,the phone is bootloop(restarting the phone is the only solution)
Sent from my OnePlus 3 using XDA Labs
There's a problem with camera on my mi5 (lineageOS), the flash lamp is not synced with snapshot.. it's flashing to short and photo is underexposed
Rom said:
NOTE: All wallpaper are saved on your internal storage.
Click to expand...
Click to collapse
How can I move them to a different folder while still letting the app detect the wallpapers? Right now the magisk module didn't work for me and the controller kept crashing. Installing them normally worked like a charm just extracted them and installed.
Only issue is it doesn't detect the rest of the wallpapers. Although it didn't detect them when I installed it through magisk too. Any resolution to it?
Peter1212 said:
How can I move them to a different folder while still letting the app detect the wallpapers? Right now the magisk module didn't work for me and the controller kept crashing. Installing them normally worked like a charm just extracted them and installed.
Only issue is it doesn't detect the rest of the wallpapers. Although it didn't detect them when I installed it through magisk too. Any resolution to it?
Click to expand...
Click to collapse
Hi,
I just refined the module on the repository and added the function you requested: once you download the update and install it, a small menu will be accessible via any terminal application like Termux for example (root access rights required).
Once your device is restarted, all you have to do is launch the terminal and type:
su
ASUS-Style-Suite-Mover
You will then be asked to provide a new location where the wallpapers will then be moved to (the validation of the new location is done by pressing ENTER).
I therefore advise you to browse your folders via an explorer to the desired folder, then copy the full path to paste it into your terminal (if your temrinal supports this function, termux for example allows this).
As for the application crash problem, not being the developer of the application in question, I only update the apk if a new one is released. If any time an update would be released as a ghost, feel free to indicate the link, I will update the apk file as soon as possible.
Rom said:
Hi,
As for the application crash problem, not being the developer of the application in question, I only update the apk if a new one is released. If any time an update would be released as a ghost, feel free to indicate the link, I will update the apk file as soon as possible.
Click to expand...
Click to collapse
Hey thanks for the quick response. I'll try this out in some but the issue with the app crash is only while I install the magisk module. I extracted the apk files from the module and installed the apps normally and there wasn't any crash at all.
Peter1212 said:
Hey thanks for the quick response. I'll try this out in some but the issue with the app crash is only while I install the magisk module. I extracted the apk files from the module and installed the apps normally and there wasn't any crash at all.
Click to expand...
Click to collapse
How ok sorry i didn't understand it like that, will take a look soon ?
Rom said:
Hi,
I just refined the module on the repository and added the function you requested: once you download the update and install it, a small menu will be accessible via any terminal application like Termux for example (root access rights required).
Once your device is restarted, all you have to do is launch the terminal and type:
su
ASUS-Style-Suite-Mover
You will then be asked to provide a new location where the wallpapers will then be moved to (the validation of the new location is done by pressing ENTER).
I therefore advise you to browse your folders via an explorer to the desired folder, then copy the full path to paste it into your terminal (if your temrinal supports this function, termux for example allows this).
As for the application crash problem, not being the developer of the application in question, I only update the apk if a new one is released. If any time an update would be released as a ghost, feel free to indicate the link, I will update the apk file as soon as possible.
Click to expand...
Click to collapse
Doesn't do anything when I type in commands
RougeCompanion app force closing on my OnePlus 2
Please refer these logs
Camera App is very good please fix the following bugs
1.Exposure is very high when pics are taken with flash
2.In fixed torch is on and taking a pic, the pic is taking with flash off
3.flash is not firing when focussing ( even in dark )
All bugs in camera is associated with flash only, please fix these bugs
This is my Moto G Power debloating module. It works on the original ROM. It's still a work in progress, but I've been using it for a while on my Moto G Power 2020 (XT2041-4, US model) and it seems pretty stable. It may work for all Moto G8/G9 as well.
Requirements:
- Root
- Magisk
- Should be flashed only in Magisk (via Modules tab)
Recommendations:
- Make a full backup before installing this module
- Copy the module to your internal storage because if something goes wrong you may have to flash it from inside TWRP
- Since I'm removing YouTube, I suggest installing YouTube Vanced, which removes ads and add some cool features
How to use it:
- Copy the zip module to your internal storage
- Open Magisk
- Go to Modules tab
- Click on 'Install from storage' and find the zip file
- After the installation a reboot button should appear, so click on it and that's it
Troubleshooting:
If you don't like the result, you can open Magisk, go to Modules tab and either disable or remove the module.
If after flashing this module your device gets into boot loop, don't panic. There are at least 2 ways to reverse it without having to factory reset or lose any data.
1- Official way: https://forum.xda-developers.com/7t-pro/how-to/guide-remove-magisk-modules-twrp-t3995677
2- I find this easier, although it enables all the apps that my module tries to remove: boot into TWRP, install my module and reboot.
What this module does:
It basically uses Magisk to replace a bunch of APKs, RCs and Zips with dummy files (0 kb) so Android cannot load them anymore. This seems the only way to change Android 10 file system because it's read-only. Here's the list of things it removes:
Code:
/system/app/BasicDreams
/system/app/BluetoothMidiService
/system/app/BookmarkProvider
/system/app/Bug2GoStub
/system/app/BuiltInPrintService
/system/app/CarrierDefaultApp
/system/app/com.motorola.android.nativedropboxagent
/system/app/CompanionDeviceManager
/system/app/CtsShimPrebuilt
/system/app/DeskClockGoogle (this is not the clock app!)
/system/app/EasterEgg
/system/app/facebook-appmanager
/system/app/GooglePrintRecommendationService
/system/app/LiveWallpapersPicker
/system/app/MotoAppForecast
/system/app/MotoDolbyV3
/system/app/MotoSignatureApp
/system/app/MotoTimeZoneDataStub
/system/app/PacProcessor
/system/app/PartnerBookmarksProvider
/system/app/PlayAutoInstallConfig
/system/app/PrintSpooler
/system/app/SimAppDialog
/system/app/Traceur
/system/app/WallpaperBackup
/system/app/YTMusic
/system/preinstall/facebook.apk
/system/priv-app/3c_devicemagement-binary
/system/priv-app/3c_notification
/system/priv-app/AmazonAppManager
/system/priv-app/BackupRestoreConfirmation
/system/priv-app/CallLogBackup
/system/priv-app/CtsShimPrivPrebuilt
/system/priv-app/DemoMode
/system/priv-app/DynamicSystemInstallationService
/system/priv-app/EmergencyInfo
/system/priv-app/facebook-installer
/system/priv-app/facebook-services
/system/priv-app/GuideMe
/system/priv-app/InputDevices
/system/priv-app/LMIRescueSecurity
/system/priv-app/LocalTransport
/system/priv-app/ManagedProvisioning
/system/priv-app/MotoHelp
/system/priv-app/MotoSystemServer
/system/priv-app/ONS
/system/priv-app/ProxyHandler
/system/priv-app/SharedStorageBackup
/system/priv-app/TagGoogle
/system/product/app/com.amazon.mShop.android.shopping
/system/product/app/datastatusnotification
/system/product/app/Drive
/system/product/app/Duo
/system/product/app/DynamicDDSService
/system/product/app/embms
/system/product/app/GoogleLocationHistory
/system/product/app/MotoDemoModeFWProxy
/system/product/app/remoteSimLockAuthentication
/system/product/app/remotesimlockservice
/system/product/app/Republic
/system/product/app/talkback
/system/product/app/TimeWeather
/system/product/app/Tycho
/system/product/app/uceShimService
/system/product/app/uimgbaservice
/system/product/app/Videos
/system/product/app/YouTube
/system/product/priv-app/3c_ota
/system/product/priv-app/AMXGlobalContainer
/system/product/priv-app/AndroidAutoStub
/system/product/priv-app/BRApps2
/system/product/priv-app/CarrierConfig
/system/product/priv-app/ConfigUpdater
/system/product/priv-app/CQATest
/system/product/priv-app/daxService
/system/product/priv-app/EasyPrefix
/system/product/priv-app/FilesGoogle
/system/product/priv-app/GoogleFeedback
/system/product/priv-app/GooglePartnerSetup
/system/product/priv-app/GoogleRestore
/system/product/priv-app/HiddenMenu
/system/product/priv-app/ims
/system/product/priv-app/InvisibleNet
/system/product/priv-app/LenovoId
/system/product/priv-app/LifetimeData
/system/product/priv-app/MotoActions
/system/product/priv-app/MotoAppUIRefresh
/system/product/priv-app/MotoCare
/system/product/priv-app/MotoCareInt
/system/product/priv-app/MotoDisplayV6
/system/product/priv-app/myCC
/system/product/priv-app/PAKS
/system/product/priv-app/SlpcSystem
/system/product/priv-app/TelcelContainer
/system/product/priv-app/Turbo
/system/product/priv-app/Velvet
/system/product/priv-app/WallpaperCropper
/system/product/priv-app/Wellbeing
/system/vendor/app/OneApp
/system/vendor/app/SSGTelemetryService/SSGTelemetryService.apk
/system/etc/init/[email protected]
/system/etc/init/[email protected]
/system/etc/init/apexd.rc
/system/etc/init/art_apex_boot_integrity.rc
/system/etc/init/ashmemd.rc
/system/etc/init/atrace.rc
/system/etc/init/audioserver.rc
/system/etc/init/blank_screen.rc
/system/etc/init/bootanim.rc
/system/etc/init/bootstat.rc
/system/etc/init/bpfloader.rc
/system/etc/init/cameraserver.rc
/system/etc/init/[email protected]
/system/etc/init/drmserver.rc
/system/etc/init/dumpstate.rc
/system/etc/init/flags_health_check.rc
/system/etc/init/gatekeeperd.rc
/system/etc/init/gpuservice.rc (scary, but user foobar66 gave the idea)
/system/etc/init/gsid.rc
/system/etc/init/heapprofd.rc
/system/etc/init/hwservicemanager.rc
/system/etc/init/idmap2d.rc
/system/etc/init/incidentd.rc
/system/etc/init/installd.rc
/system/etc/init/iorapd.rc
/system/etc/init/keystore.rc
/system/etc/init/lmkd.rc
/system/etc/init/logd.rc
/system/etc/init/lpdumpd.rc
/system/etc/init/mdnsd.rc
/system/etc/init/mediadrmserver.rc
/system/etc/init/mediaextractor.rc
/system/etc/init/mediametrics.rc
/system/etc/init/mediaserver.rc
/system/etc/init/mtpd.rc
/system/etc/init/netd.rc
/system/etc/init/perfetto.rc
/system/etc/init/perfservice.rc
/system/etc/init/racoon.rc
/system/etc/init/recovery-persist.rc
/system/etc/init/recovery-refresh.rc
/system/etc/init/rss_hwm_reset.rc
/system/etc/init/servicemanager.rc
/system/etc/init/statsd.rc
/system/etc/init/storaged.rc
/system/etc/init/surfaceflinger.rc
/system/etc/init/tombstoned.rc
/system/etc/init/traceur.rc
/system/etc/init/update_engine.rc
/system/etc/init/update_verifier.rc
/system/etc/init/usbd.rc
/system/etc/init/vdc.rc
/system/etc/init/vold.rc
/system/etc/init/wait_for_keymaster.rc
/system/etc/init/wfdservice.rc
/system/etc/init/wifi-events.rc
/system/etc/init/wificond.rc
/system/etc/security/otacerts.zip
Future work:
If you have any suggestion, please feel free to help us. For instance, I still haven't found a way to remove these apps:
- Motorola Message Service
- Motorola Services Main
- Files (not GoogleFiles) it turns out that Files is needed by any app that has to browse files, so not a good idea to remove it
Also, if you want to adapt this module to better address your needs, it's pretty easy to do it. Let's say you don't want to remove YouTube:
- Extract the zip module to a folder
- Go to system/product/app/ and remove YouTube folder
- Create a zip file from inside the main folder (the one that contains common, META-INF, system, etc)
- Install the module again from inside Magisk (you don't need to remove the previous one because it will replace all the settings anyway)
Tip: if you want to change this module, don't try to remove GameMode because you'll end up in a boot loop -- yes, I tried
Thanks to foobar66 for providing some ideas of things that are safe to remove:
[ROM][magisk-based]*** GoogleWiz *** {Pixelize your OnePlus 7T pro}
*** Wiz *** Pixelize your OnePlus 7T pro "Extreme debloat: Go where OnePlus has never gone before" You thought that OnePlus phones were pretty stock Android? Hmmm .... think again ... there's still lots of stuff on these phones that you actually...
forum.xda-developers.com
fulalas said:
This is my Moto G Power debloating module. It works on the original ROM.
Click to expand...
Click to collapse
Very nice! Seems that we share a similar philosophy when it comes to what apps "need" to be on a phone.
I'm currently, and happily, using Resurrection Remix so have no need for this rn, but surely appreciate that I'll have this if I have to go back to stock.
EDIT: I also want to say that I appreciate the thorough explanation of how to modify the debloat.
@TiTiB, thanks for your kind words!
Regarding Resurrection Remix, I haven't tried it yet. Is it as good as the original one regarding battery time? I remember trying some alternative ROMs (like this) on my old Moto G4 Plus and everything was nice, except that the battery didn't last much
fulalas said:
@TiTiB, thanks for your kind words!
Regarding Resurrection Remix, I haven't tried it yet. Is it as good as the original one regarding battery time? I remember trying some alternative ROMs (like this) on my old Moto G4 Plus and everything was nice, except that the battery didn't last much
Click to expand...
Click to collapse
I don't use my phone enough to have any valid input about battery life.
Updated.
Included the following APKs to be removed:
Code:
/system/app/PrintSpooler
/system/priv-app/LMIRescueSecurity
/system/product/priv-app/CQATest
/system/product/priv-app/HiddenMenu
/system/product/priv-app/InvisibleNet
/system/product/priv-app/LifetimeData
/system/product/priv-app/MotoDisplayV6
/system/product/priv-app/PAKS
/system/product/priv-app/SlpcSystem
Past experiences have given me around 13h of screen on time with a custom rom which was around an hour more than stock at the time
Updated.
-Fixed a missing Google Drive file removal.
-Included the following APKs to be removed:
Code:
/system/preinstall/facebook.apk
/system/product/app/Republic
/system/vendor/app/OneApp
/system/vendor/app/SSGTelemetryService/SSGTelemetryService.apk
Crush Moto Action. Can you fix it?
@Ozzrak, I'm not sure what you mean. Could you be more specific?
@fulalas , after applying your module it stops working Moto Actions. Or did you specifically delete it?
@fulalas , thanks, I already figured it out myself.
Updated.
-Included the following APKs to be removed:
Code:
/system/priv-app/3c_devicemagement-binary
/system/priv-app/MotoSystemServer
Does this module remove all core gapps? If so, would installing microG via nanodroid magisk module be able to replace the core gapps?
It removes some of non-critical Google apps, like Duo, YouTube, etc. But It doesn't remove Google Play and Maps, for instance. Take a look at the full list in the first post.
Excellent work! Thanks for sharing it!
I followed the instructions and installed the debloat module in Magisk as described. Upon rebooting I still have icons for Google Duo and YouTube. These are supposed to be removed, correct?
I'm running the original shipped ROM, 10(QPMS30.80-63-6-8-5). Rooted with Magisk. Phone model is XT2041-4. Date on box is 2021-03-18.
Everything was working perfect except I can't make or receive calls. I am on Visible. What would I need to correct to fix that?
I noticed that when I install this module I lose access to my Mobile Network settings. So what typically looks like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Looks like this instead:
Huh, something must be up, more than I initially realized, with the unbloater active I seemingly can't reliably send and receive text messages. They seemingly only come in for the first 30 seconds after I've booted my phone.
@danny8, this is really odd. They shouldn't appear anymore indeed. Are you able to open them normally? What about all the others that shouldn't appear after installing this module, like Google Drive, LiveWallpaper, etc?
@BariB523 and EvergreenMetal, I'm afraid you're going to do some trial and error. I would begin removing from the module (read the instruction in the first post) the ones with suspicious names, like CarrierDefaultApp and CarrierConfig, for instance. Sorry for not being able to give a better answer, since I don't have this problem with my carrier.
Universal SafetyNet Fix [MOD]
Magisk module
Hello. This is my modification [FORK] of the original Universal SafetyNet Fix module from @kdrag0n.
Created for the (temporary?) restoration of working capacity in the conditions of constant change of verification algorithms from Google.
If you can`t wait for update original kdrag0n`s project - feel free to use my little "experimental sandbox"
Usage:
1. Delete/disable/reset MagiskHidePropsConfig (if installed).
2. Just install it over old Universal SafetyNet Fix (if present) and reboot device.
3. You may be needed to wipe GMS data (not cache) if there is no result immediately.
4. Make sure that your SELinux mode sets to Enforcing! Otherwise, run the setenforce 1 command.
Сhecking the results:
Play Integrity API: https://play.google.com/store/apps/details?id=gr.nikolasspyr.integritycheck
SafetyNet API: https://play.google.com/store/apps/details?id=rikka.safetynetchecker
Changelog:
Spoiler
v2.4.0-MOD_1.3
* Fix "stat /sys/fs/selinux" access time reading. Also removed archaic MIUI cross-region shenanigans. Thanks to PR by aviraxp!
* Ignore props changing on Xiaomi.eu. This fixes randomly attestation failings. So strange ROM...
* Added Riru version back. Remember that is need old MagiskHide support (and adding com.google.android.gms/com.google.android.gms.unstable to HideList) !
* Added microG version. Note there is some strange behavior that GMS can crash while run SN attest more than 2 times in one session. Just do not do this. This behavior should not affect applications in real life.
v2.4.0-MOD_1.2
* Fix crash and endless tests loop/failing on Android < 9.0 (bug from original version 2.4.0).
* Do not unpatch (revert) changes. To prevent possible tests failing after a while on some ROMs (cross conflicts).
v2.4.0-MOD_1.1
* Fix KeyStore hook desynchronization (tests randomly failing problem).
v2.4.0-MOD_1.0
* It is now based on top of original v2.4.0 codebase instead of v2.3.1, with adding new hiding algorithm for current realities and some code refreshing.
Downloads: at the bottom of this post or GitHub Releases
Source code: GitHub
It worked on magisk delta, evolution x, zygisk. Thank you
Thank you for helping out and finding a solution to this problem!! v2.4.0-MOD_1.1 seemed to do the trick for me to get Google Wallet back in action on my Pixel 6 Pro! I'll try out MOD_1.2 later as well. You're a rock star!
Goat.
Thx for your unique work!
Yesterday I upgraded to Feb 2023 both security patches and Play System.
Even if I'm still on v2.3.1-MOD_3.0, so far everything works fine. I only had an unusual increase in Google Play Services usage, but seems it was just momentary. I'll stay on this former Mod until it works.
Pixel 6a TQ1A.230205.002
Magisk 25.2
Xiaomi 13 Pro with v2.4.0-MOD_1.2 installed. NFC defaults back to Embedded Secure Element after some time.
Every time I need to change payment to Google Wallet. When I do so, it works fine
You should also consider updating update.json so updates can be seen by the Magisk app of one's choosing
Gigobaito said:
You should also consider updating update.json so updates can be seen by the Magisk app of one's choosing
Click to expand...
Click to collapse
I didn't change the update channel in the module on purpose so that everyone can upgrade to the new official version automatically without any problems.
Work. Thanks
Was having issues with my fingerprint reader misbehaving on the main 2.4.0 branch on my OnePlus 7T running OOS 12.
Working perfectly with this MOD. Thanks!
CTS was failing on my Poco X3 Pro-installed magisk, installed this, enabled zygisk-CTS passes perfectly now. Thank you so much!
Used 2.3.1-MOD_3.0 without problems. Using v2.4.0-MOD_1.2 now and working fine too. Payed several times today. Thank you (Samsung A70, Android 11)
Using 2.4.0 mod 1.2 on my Pixel and all seems well. Play integrity passes right after boot and so far haven't noticed the tests failing after some time like what used to happen on 1.1. All seems good now, thanks a lot for your hard work!
It worked for me too, thanks.
2.4.0 mod 1.2 working great on my Pixel 4a running latest Feb 2023 OTA.
Could this module have anything to do with Visual Voicemail not activating? After upgrading to A13 I have not been able to get VV to activate (it worked without issue on A12).
creeve4 said:
Could this module have anything to do with Visual Voicemail not activating?
Click to expand...
Click to collapse
Google Phone's VVM can be touchy any time with or without root. Lately there's a bug causing late messages which happens to me sometimes. Unless you changed SIMs it's hard to say why your VVM deactivated after upgrading to 13. To get it working again try turning off wi-fi so that you're only connected to the mobile network. It may not activate right away but should eventually. Other threads about this topic may have better suggestions.
I tried a lot on the new S23 Ultra
Shamiko, MagiskHide, Safetynet 2.4.0 and mod
LSPosed for KnoxGuard but with that gpay wont work.
Theres one point that let Safetynet fail instanly
{
"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"
}
com.google.android. gms.unstable
Marianxs said:
I tried a lot on the new S23 Ultra
Shamiko, MagiskHide, Safetynet 2.4.0 and mod
LSPosed for KnoxGuard but with that gpay wont work.
Theres one point that let Safetynet fail instanly
View attachment 5839905
com.google.android. gms.unstable
Click to expand...
Click to collapse
If using Magisk Delta (you mentioned MagiskHide) then better don't use Shamiko
Also, afaik, GPS for AR are not needed in DenyList/MagiskHide
I mean MagiskHidePropsConf
But that have no key for the new S23
No need for other Google apps
ok i know, but i dont thrust Google
What if Google in future update wallet and other Services that use GMS to check root?
you go shopping, try pay and that wont work. I got this several times on my Note20 in the past
Xiaomi Mi10T Lite 5G (Gauguin), DotOS5.0. 2.4 mod 1.2 works like a charm. I owe you a beer, kind sir!