Database Develop

[TOOL] Nightly Updater | 1.5 | Make Your Nexus Perfect | Backup | AROMA | Mako

{
"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"
}
Make Your Nexus Perfect
WHAT'S NEW?
> VER 1.5 | SEPT 10 2013
-> Quick Install quickened to 4 clicks as opposed to 6
-> Backup/Restore Menu Added
-> Backup/Restore User Apps and be able to remove backups
-> Backup/Restore Anything using keep.txt and be able to remove backups
-> How To section updated with info on Backup/Restore Menu
-> junk.txt Updated with Media and Face Unlock files
-> On the horizon: App deletion in AROMA installer
PREREQS
Nexus Device that has a system app you do not want
Grade school diploma (i.e. ability to read)
THE SKINNY
WHAT IS NIGHTLY UPDATER
Nightly Updater is an AROMA installer for those that
yearn to have the cleanest device. Since I first
owned an HTC Droid Eris, I have been wiping bloatware
off of my device. Flash foward to my latest devices -
LG Nexus 4 and the 2013 Asus Nexus 7 and there ain't
much bloatware... But, all AOSP ROMs tend to come with
at least one or two apps that I can do without (and
sometimes a lot more). Nightly Updater is a simple
tool that allows users to remove unwanted system
applications in an easy manner. NU also allows users
to customize which apps are removed.
HOW DOES IT WORK
Nightly Updater works by relying on scripts that
read txt files. When customizing your script, the
installer looks for junk.txt in the "NU" folder of
your virtual (i.e. internal) SD card. Each line that
has not been "commented out" (i.e. does not have a
"#" at the front of it) or any terms (i.e. app
descriptions) that follow a "#" are removed from the
script. This leaves Nightly Updater with a clean text
file that only has the applications you want to remove.
Review:
Custom Script is called: junk.txt
Custom Script goes here: /sdcard/NU/junk.txt
#Chrome.apk -- NOT DELETED FROM DEVICE
Chrome.apk -- DELETED FROM DEVICE
Chrome.apk #Google Browser -- AFTER "#" IGNORED
HOW DO I ADD MY OWN APPS
You can add your own apps in three ways: [1] name (without
apk), [2] name (with apk), or [3] file path.
[1] Name (without ".apk")... Just type:
Code:
Chrome
The installer will automatically know it is looking for an apk and
delete Chrome.apk.
[2] Name (with ".apk")... Just type:
Code:
Chrome.apk
I think you know what it does.
[3] Full File Path... Now, you can get a little funkier and do the entire
file path like:
Code:
/data/app/Chrome.apk
This comes in
handy for files like pre-loaded wallpapers and
ringtones you may want to remove. Be cognizant of
where the files you are removing are located! This
will become very important when telling Nightly
Updater where to scan.
By the way, Nightly Updater also recognizes wildcards.
This is great for those user apps that end up having
unpredictable file names. For example:
Code:
/data/app/com.google.android.youtub*.apk
com.google.android.youtube*
These are both ways of erasing YouTube regardless of
the "-X" at the end of the file name.
WHAT'S UP WITH SCANNING
When using a Custom Script, Nightly Updater asks
where you would like to scan for apps. By default,
Nightly Updater recommends you only scan in the
System/App folder - which is where (shocker) system
apps are located. Remember, most junk apps are located
in System/App. However, Nightly Updater has also given
the option to scan Data/App. Some developers will put
apps in the Data/App folder, so it may be useful to
remove apps from there. But NORMALLY, these are only
the apps you chose to install. The final option is
to scan EVERYWHERE. Be very cautious with this command!
Remember that it is matching what you write in
junk.txt with the scan parameter. If you accidentally
wrote "system" as an app you wanted to remove instead
of SystemTuner.apk (with full scan on)... you would
erase your system folder... that's REALLY BAD!!!
Now, if you only check this option when you are using
full path and double check your junk.txt file so that
you did not make any mistakes... YOU ARE GOOD!!!
When in doubt, post your junk.txt here and I will
check it over for you
WHAT'S THE DEFAULT SCRIPT
If you download junk.txt from the OP at XDA, then
you have seen the Default Script. The Default
Script is meant to remove apps that MOST people
would consider expendable. If you are nervous to
tinker with your own Custom Script, try running
the Default Script first. If the script deleted
an app you need or did not delete at app you want
to destroy - hit me up and I will walk you
through the steps.
MORE DIRECTIONS ARE IN THE INSTALLER
DOWNLOADS
Check the "Downloads" Tab
NU-1.5.zip - Nightly Updater Installer
junk.txt - Customizable Removal Script
keep.txt - Customizable Backup Script
BUGS
Installer will occasionally hang when you press "< Back" - Reboot Device to fix temporarily
You tell me
HOW YOU CAN HELP
Give me feature ideas
Come up with more pre-loaded apps to be added to junk.txt
SPECIAL THANKS
Patrics83 and the whole ROM Cleaner team for the inspiration of this amazing tool!!! :good:​
XDA:DevDB Information
Nightly Updater, a Tool/Utility for the Google Nexus 4
Contributors
swagstr
Version Information
Status: Stable
Current Stable Version: 1.5
Stable Release Date: 2013-09-10
Created 2013-09-08
Last Updated 2013-09-10

WOW.... This looks great and very handy
EDIT:- Tested it on Carbon Beast v15 works good

SmOuuK said:
WOW.... This looks great and very handy
Click to expand...
Click to collapse
Please do post your results.
Sent from my Nexus 4 using Tapatalk 4

Just a quick bump for the Version 1.5 update. Lots of ideas brewing in the Flo/Deb thread for new features. Any ideas over in Mako land?

Hey y'all! Working on a sizable update that is trying include several things requested from different devices. Looking for a little help on the testing side. First few that hit me up will get it.
Sent from my Nexus 4 using Tapatalk 4

BIG WARNING! DO NOT use the Data Wipe in version 1.5 and below. The script does not exclude the "media" folder... As some of you know... That's the SD CARD! I just did it and it SUCKED lol It will be fixed in the next version along with many new updates
Sent from my Nexus 4 using Tapatalk 4

Yo. Working diligently on the backup/restore feature. Next update will be sick. Standby
Sent from my Nexus 4 using Tapatalk 4

Any chance you can put the files in a normal attachment to the post? However you've done it only works if the user has XDA 2013 beta defined as their forum theme.

famewolf said:
Any chance you can put the files in a normal attachment to the post? However you've done it only works if the user has XDA 2013 beta defined as their forum theme.
Click to expand...
Click to collapse
I will get right on that with the next update! I'm beginning to think this DevDB thing was a mistake. Good idea in theory but is hard for mobile users and those not wanting to use the latest theme. Hopefully the next update is right around the corner :fingers-crossed:

I don't see anything really N4 specific. Have you considered placing your tool in the general android apps forum for all to use? I just upgraded a nook hd+ to carbon rom and was planning to put the nightly updater on it so thought I'd double check in case I missed something.

[DEVS][APK][MOD]Easy OTA Updates for SafeStrap enabled Devices[DEVS][APK][MOD]

{
"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"
}
Samsung Galaxy S5 ATT and Verizon Developers can now easily add OTA capabilities to your ROMs without the need for dedicated servers or hosting, no need to hack OEM code to point to your servers. This package and the following instructions will show you how easy it is to implement an OTA solution with minimal impact on system applications and firmware.
Click to expand...
Click to collapse
Code:
[B][U][COLOR="Red"]The download package includes all of the following:[/COLOR][/U][/B]
1. Original untouched eclipse source code from [URL="https://github.com/OTAUpdateCenter/ota-updater-2.0"][B][COLOR="Red"]HERE[/COLOR][/B][/URL]
2. Original modified decompiled source V2.0.5 apk
3. Modified decompiled source (My Modifications) V2.0.8 apk
4. Example "rom.ota.prop"
5. Required "ota.prop" (For SafeStrap support)
6. Text file containing links required to be posted in your OP
Code:
[B]Required tools for successful build[/B]
1. VTS (Virtuous Ten Studio) or (Apk MultiTool v1.1.0)
2. If working with the untouched Eclipse Source Eclipse Juno and the current version of Gradle
3. A text editor capable of Unix/Linux encoding (Notepad++ recomended)
4. A tool for comparing files (Winmerge is the tool I use)
5. A Dropbox account or other file sharing account that allows for Direct download links (No landing pages)
Posting Requirements
1. Included in the download package is a text file that includes all links "REQUIRED" to be visible in your OP.
2. You may NOT remove any copyright notices on the about page, neither the originating copyright nor mine.
3. You may NOT change the Open Source licensing file however you may ADD to this file.
4. You may NOT remove any contributors from the contrib.txt but you may ADD yourself to this list.
Click to expand...
Click to collapse
Instructions​
Code:
1. Download the zip package [URL="http://forum.xda-developers.com/devdb/project/?id=6766#downloads"][B][COLOR="Red"]"Unity_OTA_Mod.zip"[/COLOR][/B][/URL] and extract to a working folder.
2. Using your tool of choice either VTS or Apk MultiTool decompile both included apk files
3. Using Winmerge or other diffing tool compare the decompiled sources
4. you can easily see the changes between 2.0.5 and 2.0.8 [B]pay close attention to the downloadsactivity.smali.[/B]
5. Once you have completed your changes/modifications recompile the APK.
6. Go [URL="https://www.otaupdatecenter.pro/"][B][COLOR="Green"]HERE[/COLOR][/B][/URL] and follow their instructions for setting up your ROM
7. Reboot your device to SS Recovery
8. Push your compiled APK to /system/app/OTA-Updater.apk
9. Push your "rom.ota.prop" and the included "ota.prop" to /system
10. Push "com.unityota.feature.xml" to /system/etc/permissions/com.unityota.feature.xml
11. Wipe cache and dalvik-cache and reboot
12. Verify application opens and contains all of your modifications
13. Once you have an OTA file setup for your ROM [B][COLOR="Red"](see step #6)[/COLOR][/B] test the application for download and flash.
[B][COLOR="Red"]Special NOTE: Remember to change the hypelinks in the code to point to your threads, do NOT however, change the hyperlink inside of "APIUtils$APITask.smali" that points to the otaupdatecenter site that checks for your OTA packages.[/COLOR][/B]
This does require direct download links (example for dropbox links below)
e.g the Sharing URL looks like https://www.dropbox.com/s/…../<filename>
now after replacing www.dropbox.com with dl.dropboxusercontent.com
the link becomes https://dl.dropboxusercontent.com/s/…../<filename>
this link starting with dl.dropboxusercontent.com is your direct download link!
Click to expand...
Click to collapse
!!THANKS!!​
Code:
@hashcode - for SafeStrap Recovery
@geohot - for root
[URL="https://www.otaupdatecenter.pro/"]otaupdatecenter.pro[/URL] - for the original source and OTA environment
Google - For Android
Virtuous Developers for VTS
github for providing source code control and open source access
!!!Disclaimer!!!​
KoolKit ROMs and Unity Development are not responsible if you blow up your house, your dog eats your
homework, the zombie apacolypse, your wife/husband divorcing you or if your device turns into an unrecognizable
smoldering pile of plastic. by reading this you agree to take all responsibility for any damage you do to the
universe, your device, your marriage or your failing grades in school or college.
Click to expand...
Click to collapse
XDA:DevDB Information
OTA-Updater, Device Specific App for the AT&T Samsung Galaxy S 5
Contributors
cstayton, https://www.otaupdatecenter.pro/
Source Code: https://github.com/OTAUpdateCenter/ota-updater-2.0
Version Information
Status: Stable
Current Stable Version: 2.0.8
Stable Release Date: 2014-11-20
Created 2014-11-20
Last Updated 2014-11-20

Reserved

Reserved

Bri needs to integrate this into Dynamic Kat!

Exelente ...amigo gracias x su duro trabajo
Enviado desde mi SM-G900F mediante Tapatalk

im a noob, wanted to know if i have to change anything like the instructions say to do, if i have stock rom. i have a gs5 with stock rom, just root. thanks in advance.

Noob or not, at least somebody replied to this damn thread lol

dabuddyhenry said:
im a noob, wanted to know if i have to change anything like the instructions say to do, if i have stock rom. i have a gs5 with stock rom, just root. thanks in advance.
Click to expand...
Click to collapse
I think this is more for developers bud. Unless you know how to do what was stated above. Unless your wanting to learn how to do it, this is not necessary for us who just flash roms.

dabuddyhenry said:
im a noob, wanted to know if i have to change anything like the instructions say to do, if i have stock rom. i have a gs5 with stock rom, just root. thanks in advance.
Click to expand...
Click to collapse
this is for devs not a mod you can add to your stock rom

[2020-01-27] ®FDE.AI - Ultimate Android Optimizer

{
"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"
}
Code:
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
backup your data before flashing it!
YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
Do everything at your own risk!
Intro:​Hello everybody. My name is Fera. I want to share this project with you for free. I made it myself from scratches once again. Please hit "thanks" button, rate this thread 5-star, or consider donating me to support my work. (Thanks!)
What's in:​FeraDroid Engine (simply FDE) - an All-in-One ultimate optimizer for all devices on Android OS. No settings/customization and rest 'headache' - all parameters are individual for EVERY device depending on it's hardware/software characteristics. All parameters are very balanced - you may gain performance without increase of power consumption AND reduce power consumption without losing performance. FDE is totally compatible with very wide range of devices and Android versions.
Installation requirements:​Supported CPU arch's:
ARMv7 (armeabi-v7a) (32bit)
ARMv8 (arm64-v8a) (64bit)
x64bit (x86_64)
Supported Android OS versions:
4.1 and higher
Detailed tech description:​FDE - very universal Android OS optimizer. Very wide-range settings of OS and Linux kernel are configured, still being cross-platform utility, maximally compatible with all devices. This means that it doesn't have any dirty hacks/hardcore and 3rd part binaries (except busybox) & config files. FDE applies configurations depending on It's hardware and software, so that in the end every device is configured individually.
New unique method of execution - all required FDE components are loaded directly to RAM and executed from there. System partitions are remounted RW only once while installation. This means high speed (the worst RAM will have at least ~500MB/s of I/O speed), no power consumption (no NAND memory I/O occurs) and security (system partitions are in read-only state). Also new-gen FDE is synced with OS boot process - so tweaks will be applied in correct time. All system partitions are trimmed and checked for errors after every OS boot with FDE onboard. Universal installer automatically detects what ROOT-method you use and how to auto-start. Finally, FDE is not only about optimization. It's also about security and feature-enabler.
See compacted list of most included features HERE.
Artificial Intelligence:
As you may notice from the name "FDE.AI" - can tell us that it has real AI inside. AI will learn how do you use your device, check out current usage scenario and adapt some system parameters real time to give you best usage experience. Details HERE.
Why to optimize?​First of all to make you happy with your device, to make it live longer & be snappy. Another reason is garbage. WTF? Yes. There is a world problem of e-garbage utilization, especially electronic devices & their toxic stuff like batteries..etc.. I'm not against progress - I'm against the selling politics of corporations, which add features slowly, to make people buy them. I'd say OKAY if it wasn't harmful, but in fact Africa became a toxic garbage continent - they need somewhere to put retarded e-devices & that's sad. It costs them cheaper to move toxic garbage to another country, rather then properly utilize it. You may say, how FDE can help with that, are you mad bro? Well, I hope that if you install FDE on your device, you'd use it for longer time, because of all optimizations. So that it will make you happy & you won't change it too frequent, in fact possibly reducing the amount of e-garbage. Thanks.
Installation:
WARNING! Don't use any other All-in-One tweakers or things may get much worse! I warned you!​
Make a backup just in case something goes wrong.
Download latest version of FDE and install it via custom recovery OR add zip in modules list if you are using Magisk systemless root.
After OS boot, you will get vibration and a log file /sdcard/Android/fde.txt will be created if FDE worked OK.
If you want to uninstall FDE simply remove module from Magisk Manager if you are on Magisk OR flash this zip in custom recovery.
Download:
FDE.AI-v7.3-20200127
About FDE APK
FAQ
Related Videos
Join my group in Telegram for 24/7 support.
Join my Facebook group.
Thread at 4PDA.
Fan-art​
Thanks to all guys, who contributed, helped, tested my work.. You all are wonderful, amazing, smart, super cool, beautiful people!
Consider donating me to support my project if you like it. Thanks!
XDA:DevDB Information
FDE.AI - Ultimate Android Optimizer, Tool/Utility for all devices (see above for details)
Contributors
FeraVolt
Version Information
Status: Stable
Current Stable Version: v8.0
Created 2019-03-10
Last Updated 2020-01-27

FDE.AI FAQ
Will it work on this or that device?
It will work on any device which runs Android OS.
Will it work along with this or that tweak/optimizer?
NO. Don't use any other All-in-One tweakers or things may get much worse!
Can I use this on custom kernel?
Yes, why not? It will work even better on custom kernel.
Does FDE has any configuration/logs?
No configurations. This is "flash & forget" optimizer. It will configure your system depending on you hardware/software automatically & individually. Log is available in /sdcard/Android/fde.txt
Is it worth to try FDE if I have a powerful flagship?
Yes, sure. FDE not only gives performance, but also increases power-saving.
Is there any difference between zip from Magisk module repo and zip provided here?
The difference is only in installer - zip provided here is universal, while one in Magisk repo is for Magisk root only.
I have ROOT, but don't have recovery. Can I do something?
You may try to install FDE via Flashfire app.
I have ROOT - not Magisk, and not SuperSU, and I don't have init.d support. What to do?
Try to emulate init.d support with app like Universal_Init.d_Support or similar.
Installation was successful, but no vibration. What does this mean?
Try to reboot device. Wait for a minute or two more. Maybe it will work, but a little later than expected. Also check for /sdcard/Android/fde.txt file. If still no luck, try to update your ROOT method (Magisk preferred). If you do have log and it says "all good" - then don't worry at all. Some rare devices doesn't support vibrations triggered by script. If still not working, read THIS post.
Do I need busybox?
No, FDE has a built-in one already. But if you already have one - they will not conflict.
Are project treble ROMs supported?
YES.
Flashed fine, but can't find icon for FDE. Huh?
This is not an Android apk and it has no interface yet.
Can I flash FDE right after ROM installation?
NO. Boot ROM first, then install FDE.
AI says '...turbo' is not supported. What can i do to make it work?
You may try to install another custom kernel. Those features are kernel dependent.
It's running fine, but i got a problem...
FDE.AI is under active development. Please attach any useful information such as log/screenshot, name of your device, ROM/recovery version. I am developer of FDE and I will help you to figure out the problem.

Nice mod, please check your git

Where is the download link???
来自我的 SM-G920F 上的 Tapatalk

There is a 'downloads' tab over main post

FeraVolt said:
There is a 'downloads' tab over main post
Click to expand...
Click to collapse
Error executing update-binary

Here is zip with fixed recovery installation. Forgot ';' in script...

No log file for me

I test your mod and I dont have any log, and any change in my device; galaxy tab pro 8.4 with SlimLP 5.1.1

russia101 said:
No log file for me
Click to expand...
Click to collapse
kioshio said:
I test your mod and I dont have any log, and any change in my device; galaxy tab pro 8.4 with SlimLP 5.1.1
Click to expand...
Click to collapse
Make sure you have mounted system partition in recovery before flashing.. This is beta version..being under development.. Also possibly it simply didn't run on boot. Please specify your device, android version and rom and i will try to check this out. I tested it from 2.3 till 5.1.1 android version..stock roms..

FeraVolt said:
Make sure you have mounted system partition in recovery before flashing.. This is beta version..being under development.. Also possibly it simply didn't run on boot. Please specify your device, android version and rom and i will try to check this out. I tested it from 2.3 till 5.1.1 android version..stock roms..
Click to expand...
Click to collapse
I'm using a s3 LTE and I'm currently on marshmallow 6.0.1

No log file. I Followed instructions. Stock Android 4.2.2
Still......noticeable improvement in loading of apps. Any other way to see if it flashed correctly?

Seems installed, let's see if it works. 5.1 OxygenOS. Here is my log: https://drive.google.com/file/d/0B1B_Q2k5VDqYUml1bTBJd2ZFMk0/view?usp=docslist_api
You should provide an Uninstaller, just in case. Cheers
Enviado desde mi ONE E1005 mediante Tapatalk

ChavitoArg said:
Seems installed, let's see if it works. 5.1 OxygenOS. Here is my log: https://drive.google.com/file/d/0B1B_Q2k5VDqYUml1bTBJd2ZFMk0/view?usp=docslist_api
You should provide an Uninstaller, just in case. Cheers
Enviado desde mi ONE E1005 mediante Tapatalk
Click to expand...
Click to collapse
Yes..it's working on your device fine. Do you notice any improvement? In case of high-end devices, most noticable should be a battery consumption decrease.
Will provide uninstaller asap.

hipocrazy said:
No log file. I Followed instructions. Stock Android 4.2.2
Still......noticeable improvement in loading of apps. Any other way to see if it flashed correctly?
Click to expand...
Click to collapse
Yes..via terminal emulator type:
su
sh /system/engine/as.sh
sh /system/engine/feradroid.sh
Then recheck log file..

FeraDroid-Engine-v0.19-beta2
FeraDroid-Engine-v0.19-beta2
Changes captured:
https://github.com/feravolt/FeraDroid-Engine/commits/master

Manuall FDE run
Here is a little instruction in case you couldn't install FDE on your device. Recovery doesn't install it well..or..FDE doen't autostart or you just don't have a recovery for your device (as in my case with china noname phone).
So:
-> Download latest FDE zip and extract it.
-> With any root explorer copy engine folder to /system/
-> Set 777 (check all tabs) permissions to whole engine folder and what is in there and in every folder content
-> Then get 'Terminal Emulator' app from Google Play store, run it and type:
Code:
su
-> Grant root permission then type:
Code:
sh /engine/as.sh
-> After that reboot your device and in 2 minutes, check log file on path: /sdcard/Android/FDE.txt
-> If there is no FDE.txt log then open Terminal Emulator again and type:
Code:
su
sh /system/engine/feradroid.sh
-> Wait it's completion, then check log file again. If it exists, please send it to me to deal with autostart issue for your device. You should run theese two commands every time you reboot your device..
Hope this will help you and you will be happy to see your device runnign fast. :fingers-crossed:

Log file
FeraVolt said:
FeraDroid-Engine-v0.19-beta2
My log file looks not like it's working correctly and this logfile only appears after I typed the command which you posted for terminal
View attachment FDE.txt
Click to expand...
Click to collapse

init.d start
russia101 said:
FeraVolt said:
FeraDroid-Engine-v0.19-beta2
My log file looks not like it's working correctly and this logfile only appears after I typed the command which you posted for terminal
View attachment 3598637
Click to expand...
Click to collapse
Thanks for feedback.It worked for you untill you reboot.
Here..try this zip with a try to be started at boot by init.d.. mount system partition..flash .zip and check log.(remove it beforeflashing this)
Click to expand...
Click to collapse

FeraVolt said:
russia101 said:
Thanks for feedback.It worked for you untill you reboot.
Here..try this zip with a try to be started at boot by init.d.. mount system partition..flash .zip and check log.(remove it beforeflashing this)
Click to expand...
Click to collapse
Ok did what you said and it looks Like everything works
View attachment FDE.txt
Click to expand...
Click to collapse

[MODULE] Secure Flag Patcher

{
"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"
}
Secure Flag Patcher - Magisk Edition
THIS TOOL HAS BEEN MERGED INTO SMALI PATCHER, ALL FUTURE UPDATES WILL BE MADE THERE.
​
DESCRIPTION ::
Allow screenshots/screensharing in secure apps.
PATCHING PROCESS ::
Decompiles JAR file.
Patch the nessisary files.
Recompile JAR file.
Download's the latest magisk module template from github.
Generate a magisk module .zip for you to flash in recovery !
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.
REQUIREMENTS ::
.NET Framework 4.6 or later installed.
Java JRE 1.8 or later installed.
Deodexed "services.jar", the patcher will do absolutely nothing if used on a odexed "services.jar".. Let me clarify, you can be running a odexed rom that is absolutely fine, however in order for the patcher to work you must target a deodexed "services.jar". If your running a odexed/stock rom and need to deodex I highly recommend using: Fulmics Deodexer.
Open Fulmic deodexer settings and set baksmali/smali.jar path.
Extract "/system" folder from rom zip installation file to your desktop.
Set /system path in fulmics deodexer and start deodex process.
You can also deodex using baksmali/smali:
Code:
java -jar baksmali.jar x services.odex -d framework\arm64 -o tmp
*** "framework\arm64" assuming your device is arm64 ***
*** otherwise try "framework\arm", if that also fails try just "framework" ***
java -jar smali.jar a tmp -o classes.dex
java -jar apktool.jar d services.jar
*** Cut and paste "classes.dex" into decompiled directory ***
java -jar apktool.jar b services.jar.out
If you don't want to use apktool, alternatively you can open the odexed "services.jar" with a zip archiver program (7zip, WinZip etc.) and add "classes.dex" to the JAR.
INSTRUCTIONS ::
Backup device.
Run "SecureFlagPatcher.exe", First startup will download the latest nessisary binary's.
Select your deodexed "services.jar". Easiest way to extract this file is by pulling it from your deodexed rom .ZIP file, you can find it in "/system/framework/".
Hit "Patch JAR".
Once the process has completed, magisk module will be generated in the same directory as "SecureFlagPatcher.exe".
Flash module in recovery.
CHANGELOG ::
0.1 ::
Initial release
CREDIT ::
edzamber
Cheers,

Great work! I was excited when I saw this.
Although, I get a "stopped working" during decompilation.
I went to the Mock Mock Locations patcher and saw APKTool had an issue with Nougat (though was apparently fixed?), is this the same issue here?
I apologize, I was unclear on it.

Ariac Konrel said:
Great work! I was excited when I saw this.
Although, I get a "stopped working" during decompilation.
I went to the Mock Mock Locations patcher and saw APKTool had an issue with Nougat (though was apparently fixed?), is this the same issue here?
I apologize, I was unclear on it.
Click to expand...
Click to collapse
Make sure your using the latest .NET framework & java framework.. a user reported that they were using a outdated java framework which was causing crashes..
Crashing when it begins decompiling sounds like a java framework issue to me..
I really should code in a framework version check, I've just been preoccupied with other projects lately tho.
I just had a thought.. I might consider merging the two projects if I find any other tweaks in services.jar that may be useful.. a single patcher, generating one module, with customizable tweaks.. I like it.

fOmey said:
Make sure your using the latest .NET framework & java framework.. a user reported that they were using a outdated java framework which was causing crashes..
Crashing when it begins decompiling sounds like a java framework issue to me..
I really should code in a framework version check, I've just been preoccupied with other projects lately tho.
I just had a thought.. I might consider merging the two projects if I find any other tweaks in services.jar that may be useful.. a single patcher, generating one module, with customizable tweaks.. I like it.
Click to expand...
Click to collapse
I am using Windows 10, the .NET framework is up to date (I even tried to install it again from the Microsoft website).
As for the JRE, I originally started off with the x64 JRE. That didn't work so I reinstalled it. That also didn't work.
I installed the x86 JRE alongside the x64 JRE and I am still getting the crash.
Any other ideas?
Attached is the deodexed services.jar I pulled from my ROM. I don't know if it's just that somehow? Is there anything else I could check?
Thanks for your reply!

Ariac Konrel said:
I am using Windows 10, the .NET framework is up to date (I even tried to install it again from the Microsoft website).
As for the JRE, I originally started off with the x64 JRE. That didn't work so I reinstalled it. That also didn't work.
I installed the x86 JRE alongside the x64 JRE and I am still getting the crash.
Any other ideas?
Attached is the deodexed services.jar I pulled from my ROM. I don't know if it's just that somehow? Is there anything else I could check?
Thanks for your reply!
Click to expand...
Click to collapse
Sound's like you did all the troubleshooting you can on your end..
I'll take a look after work.. could be the patcher just not playing nice with your jar.
Thanks for uploading that.. I'll keep you posted.
EDIT: @Ariac Konrel Seems to work fine for me.. no crash..
Try decompile it with apktool manually... you'll find "apktool.jar" in the folder named "bin", navigate a cmd prompt there (cd command) and enter the following:
Code:
java -jar apktool.jar -d services.jar

fOmey said:
EDIT: @Ariac Konrel Seems to work fine for me.. no crash..
Try decompile it with apktool manually... you'll find "apktool.jar" in the folder named "bin", navigate a cmd prompt there (cd command) and enter the following:
Code:
java -jar apktool.jar -d services.jar
Click to expand...
Click to collapse
That didn't work either. I actually didn't find the issue until Power Shell gave me a little bit of detail (I used to cmd and nothing was recognized).
It was something with Java's path not being set, although now this worked perfectly. Well, it says complete. It had a few things in the log such as:
Code:
I: Copying unknown files...
I: Copying unknown files/dir...
W: Could not find resources
Although, it seems to have decompiled and all fine.
I will leave the link to where I found my solution in this post just in case anyone else runs into the issue. Here it is.
Thanks for your help and a great tool. Also, I didn't reply to this earlier (I was really tired at the time of writing my original reply to it a few messages back), but I think merging the projects is an excellent idea. Keeps it as one tool with one support thread. Just seems cleaner, dunno. Either way, thanks a ton for your work.
EDIT: The patcher worked perfectly for my device, despite that logging.

Successfully patched my Zenfone 2 (Z00A) services.jar, thanks @fOmey for your tool.:good:

fOmey said:
Make sure your using the latest .NET framework & java framework.. a user reported that they were using a outdated java framework which was causing crashes..
Crashing when it begins decompiling sounds like a java framework issue to me..
I really should code in a framework version check, I've just been preoccupied with other projects lately tho.
I just had a thought.. I might consider merging the two projects if I find any other tweaks in services.jar that may be useful.. a single patcher, generating one module, with customizable tweaks.. I like it.
Click to expand...
Click to collapse
can it be used alongside mock mock locations?
Sent from my SM-G955F using Tapatalk

innit said:
can it be used alongside mock mock locations?
Sent from my SM-G955F using Tapatalk
Click to expand...
Click to collapse
Absolutely, just extract the services.jar from the mock locations module zip and patch that !
EDIT: @innit forgot to mention, if you extract the services.jar from the mock locations module you no longer need the mock locations module to be activated/installed as the generated secure flag patcher module will contain the mock locations patch also ! So make sure you uninstall the mock locations module.

fOmey said:
Absolutely, just extract the services.jar from the mock locations module zip and patch that !
EDIT: @innit forgot to mention, if you extract the services.jar from the mock locations module you no longer need the mock locations module to be activated/installed as the generated secure flag patcher module will contain the mock locations patch also ! So make sure you uninstall the mock locations module.
Click to expand...
Click to collapse
hi, thanks for the quick reply. will do as instructed [emoji106]
Sent from my SM-G955F using Tapatalk

@fOmey
Hey ! Thanks bro, good work [emoji2]

[Magisk Debloat Module] Moto G Power Sofia(p)(r)

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.