Database Users

CM 6.0.0 Apps Confirmed Working on G2 (Vision)

Disclaimer: I am not responsible if you hurt you phone... Only do this if you know what you're doing.
List of CyanogenMod Apps confirmed working:
Mms.apk
Music.apk
Calculator.apk
Click to expand...
Click to collapse
In order to install CM apps to the G2 you will need ROOT as these apps reside in /system/app
To install:
1. Root
2. Use Root Explorer to MOVE any system app (and corresponding .odex file if present) to /sdcard/backup
3. Reboot
4. Click on CM apk to install
5. Done!
All CM6 apps can be downloaded on the CyanogenMod Forum
Please try apps yourself and let me know if they work, I'll update this list!

Failed Apps
Apps not working (so far):
Calendar.apk
CalendarProvider.apk
Contacts.apk
ContactsProvider.apk
Click to expand...
Click to collapse
CAUTION: Even after restoring the above apps and odex files, I get constant FC's and Calendar and Contacts do not exist...

gravis86 said:
Disclaimer: I am not responsible if you hurt you phone... Only do this if you know what you're doing.
List of CyanogenMod Apps confirmed working:
In order to install CM apps to the G2 you will need ROOT as these apps reside in /system/app
To install:
1. Root
2. Use Root Explorer to MOVE any system app (and corresponding .odex file if present) to /sdcard/backup
3. Reboot
4. Click on CM apk to install
5. Done!
All CM6 apps can be downloaded on the CyanogenMod Forum
Please try apps yourself and let me know if they work, I'll update this list!
Click to expand...
Click to collapse
By doing this wont we lose the ability to receive future OTA's or manually update without jumping through a thousand hoops? .... like when Paul's app modified the system folders to remove goggles?

sinistersai4d4d said:
By doing this wont we lose the ability to receive future OTA's or manually update without jumping through a thousand hoops? .... like when Paul's app modified the system folders to remove goggles?
Click to expand...
Click to collapse
It doesn't matter too much now. Just wait and we will get all kinds of custom ROMs and you can flash whatever you want. After OTAs come out, usually you can get a custom deodexed version within hours. At least that's how it was on my N1. I'm pretty sure there are more G2s in peoples hands now than N1s, hence more interest? Just guessing...
Sent from my HTC Vision

sinistersai4d4d said:
By doing this wont we lose the ability to receive future OTA's or manually update without jumping through a thousand hoops? .... like when Paul's app modified the system folders to remove goggles?
Click to expand...
Click to collapse
Back then, we didn't have S-OFF so putting the app back after it was deleted was impossible. Now we do have S-OFF so we're all good, as long as you backed-up the apps prior to removing them.

do i have to delete the the original .apk and .odex files from the system/app after moving the originals to the sdcard/backup? or do i just move it, and leave the original stuff in the system app. and reboot. and then install the CM apk's?

dam legit!

donaliar said:
do i have to delete the the original .apk and .odex files from the system/app after moving the originals to the sdcard/backup? or do i just move it, and leave the original stuff in the system app. and reboot. and then install the CM apk's?
Click to expand...
Click to collapse
If you move them from one place to another, then they are only in the place where you moved the to, and are no longer in the place where you moved them from. Hence move not copy.

[Q] Own ROM issues?

Right.
So, when I open up .ext3 files in 7zip I notice they have "users" and "modes".
Things I'm curious of:
1. How can I remove apps in my ROM via .ext3 editing?
2. How can I install apps in my ROM (via .ext3 editing)?
3. Just simply removing the .apk for, let's say, the Phone app (BlurPhone.apk) and putting a different apk named Phone.apk, but with the same function and simply being a port from a different phone, will it be a issue?
4. GO Launcher EX/Go Locker - can it be installed in a ROM?...
Also, I got some issues regarding the MD5 Sum ("mismatched " but it actually is a duplicate ). Was it because I had a vanilla copy of my backup in the backup folder?..

Bump?...

Firtst if all, learn to make an cwm zip , its much easier to make changes that way.
To remove an app, just remove the apk file. Do the opposite when adding apps.
Any launcher can be added to rom.
Sent from my MB525 using xda app-developers app

This excellent instruction might help you with building from source:
http://forum.xda-developers.com/showthread.php?t=1593117

thanks, but sadly I'm not going to develop 4.0/4.1 stuff, only 2.3 skins for the moment. Thanks for the help tho
Another (kinda random, but hey): how's the lockscreen app named?...Or is it a sub-part of a motoblur app?

Building first ROM for G900V

Good day, all!
I've been working on [my first] ROM for Verizon S5 and everything seems to be going great! I've cleaned out as much Samsung/Verizon/Google trash as I can, applied some tweaks to build.prop, changed some default apps to (IMHO) better replacements, and anything that is left (functions correctly) has been moved to /data/app so they can be Uninstalled fully (not just Turned Off). Just a few quick questions:
1) How can I "bake-in" app data? I have replaced the normal, crap launcher with Holo Launcher and cannot seem to get correct permissions when the ROM is installed thru SS. I believe the issue is permissions for /data/data/ get screwed up or not set correctly. I have looked and looked and tried to determine the correct permissions, but still no joy. I've tried to fix /data/data permissions in the updater-script, but it seems like each subfolder/file has different permissions making me think I'll have to go thru them one-by-one.
I have a work-around in place using a OneTimeInit script that does work, but it seems like that's not really the best approach?
2) Kind of ties into question number 1, I patched the framework-res.apk in to allow WiFiHotspot, but without being able to install the system settings data properly, there is not a "Quick Shortcut". Again, I've resolved the problem using the OneTimeInit to update Sqlite DBs after the system is up.
3) How do I de-odex the stock ROM? Using Android Kitchen doesn't seem to do it right. It works mostly but I still seem to get various FCs. I tend to believe that some things just cannot (should not) be De-Odex'd?
I've also discontinued Zip-Aligning because it sometimes produces errors on my ROM. Is it not advised to use Android Kitchen to do these tasks or is there some trick to getting it to work just right?
Bonus Question) I was going to share my ROM on XDA but it says I'm not allowed to post in Development. I assume because of my low post count. Any way I can get an over-ride or should I just make a few more posts and then do it?
Thanks again guys!
I appreciate all the help as always!
Jake

jake5253 said:
Good day, all!
I've been working on [my first] ROM for Verizon S5 and everything seems to be going great! I've cleaned out as much Samsung/Verizon/Google trash as I can, applied some tweaks to build.prop, changed some default apps to (IMHO) better replacements, and anything that is left (functions correctly) has been moved to /data/app so they can be Uninstalled fully (not just Turned Off). Just a few quick questions:
1) How can I "bake-in" app data? I have replaced the normal, crap launcher with Holo Launcher and cannot seem to get correct permissions when the ROM is installed thru SS. I believe the issue is permissions for /data/data/ get screwed up or not set correctly. I have looked and looked and tried to determine the correct permissions, but still no joy. I've tried to fix /data/data permissions in the updater-script, but it seems like each subfolder/file has different permissions making me think I'll have to go thru them one-by-one.
I have a work-around in place using a OneTimeInit script that does work, but it seems like that's not really the best approach?
2) Kind of ties into question number 1, I patched the framework-res.apk in to allow WiFiHotspot, but without being able to install the system settings data properly, there is not a "Quick Shortcut". Again, I've resolved the problem using the OneTimeInit to update Sqlite DBs after the system is up.
3) How do I de-odex the stock ROM? Using Android Kitchen doesn't seem to do it right. It works mostly but I still seem to get various FCs. I tend to believe that some things just cannot (should not) be De-Odex'd?
I've also discontinued Zip-Aligning because it sometimes produces errors on my ROM. Is it not advised to use Android Kitchen to do these tasks or is there some trick to getting it to work just right?
Bonus Question) I was going to share my ROM on XDA but it says I'm not allowed to post in Development. I assume because of my low post count. Any way I can get an over-ride or should I just make a few more posts and then do it?
Thanks again guys!
I appreciate all the help as always!
Jake
Click to expand...
Click to collapse
1: All I had to do was place apk in /system/app or /system/priv-app and thats it. Make sure when you add your apks you dont unzip the archive. basically use kitchen and build your base rom then simply open the archive and make your edits. I also used the updater script from beans base build and only edited the ui print.. Messing with the updater script i wouldnt recommend as it could be causing some of your issues.
2: If using beans base theres no reason for you to edit anything as the hotspot is already baked in.. you must have borked it.. If you are not using beans base then maybe you should copy his files for the native hotspot as its already done properly. I wouldnt mess with framework or settings apks unless you know what your doing. Id work on gettin the fcs n other issues sorted first as you might b doin too much too fast.. work on learning how to make your apks work first before making edits to framework n settings apks.
3: The kitchen is best to deodex and zipalign.. also these two things should not cause fcs or errors if done properly. zipalign should help more than anything.. i just like workin with deodex bcuz its easier and only one set of files instead of .apk and .odex for just bout everything..
Again, if you are not using beans bases id recommend to do so.. his bases are already deodexed have hotspot zipaligned read/write to ext sd etc.. so you wouldnt have to do all from scratch and have so many issues..
Sent from my SM-G900V using XDA Premium HD app

elliwigy said:
1: All I had to do was place apk in /system/app or /system/priv-app and thats it. Make sure when you add your apks you dont unzip the archive. basically use kitchen and build your base rom then simply open the archive and make your edits. I also used the updater script from beans base build and only edited the ui print.. Messing with the updater script i wouldnt recommend as it could be causing some of your issues.
2: If using beans base theres no reason for you to edit anything as the hotspot is already baked in.. you must have borked it.. If you are not using beans base then maybe you should copy his files for the native hotspot as its already done properly. I wouldnt mess with framework or settings apks unless you know what your doing. Id work on gettin the fcs n other issues sorted first as you might b doin too much too fast.. work on learning how to make your apks work first before making edits to framework n settings apks.
3: The kitchen is best to deodex and zipalign.. also these two things should not cause fcs or errors if done properly. zipalign should help more than anything.. i just like workin with deodex bcuz its easier and only one set of files instead of .apk and .odex for just bout everything..
Again, if you are not using beans bases id recommend to do so.. his bases are already deodexed have hotspot zipaligned read/write to ext sd etc.. so you wouldnt have to do all from scratch and have so many issues..
Sent from my SM-G900V using XDA Premium HD app
Click to expand...
Click to collapse
Thank you for the response!
It seems perhaps I didn't quite make clear what I've done versus what I'm trying to accomplish.
Firstly, I wouldn't go so far as to say I'm "having so many issues". Everything in my ROM is in perfectly fine working order. I just have these few quirks that I would like to address both so I can learn, and to make this and future projects better.
While I appreciate the recommendation to use bean's base, I have taken a look at his and there seems to be nothing in his which copies data into /data/data/com.whatever.package (or at least there's nothing in his zip in the /data/data folder -- not sure if his ROM has the toggle activated?)
I have the Apps working correctly in my ROM -- they just go in /data/apps, /system/app or /system/priv-app, respectively.
What I need, is to get /data/data/com.whatever.package/ copied With Correct Permissions when the ROM is installed; I do not want a second zip to update things after install, especially for a toggle and a couple shortcuts, seems silly.
For instance, when you boot your phone up with the default [stock] samsung launcher, it has a list of default apps and widgets on the first screen you see such as phone, messages, a clock widget, etc, etc. Since I've replaced the stock launcher with Holo Launcher HD and some other default apps have also been replaced, there's very few shortcuts on the main launcher screen.
** Holo Launcher does have a list of default apps it adds to your main page, but many of those have been removed in my rom.
The solution I've come up with basically waits for the system to boot up to the point that Holo Launcher actually creates the default (mostly blank) /data/data/com.mobint.hololauncher.hd/databases/launcher.db and then my script uses sqlite3 to update the DBs with a list of different shortcuts -- ones to apps that actually exist.
The Hotspot Toggle is the same way as above.. Hotspot works fine in my rom if you go through settings!
I just cannot add the notification panel pull-down toggle to /data/data/com.android.providers.settings/database/settings.db until after the system boots up at least ONE time, and then update the DB to include WiFiHotspot in notification_panel_active_app_list and notification_panel_active_app_list_for_reset
As for the zipalign and deodexing, I will have to try those again now that I have a fairly stable rom.
****EDIT****
I think I figured it out. I can just use busybox to kill the systemui after I update the databases during the first boot. I also figured out how I can add the SetupWizard without it locking up on activation.
Thanks anyways, guys.
Look for my rom, coming soon!
=P

Please add support for more languages
I found a mod for Motorola latest 4.4 please port it
Sent from my SM-G900T using XDA Free mobile app

[MOD] Remove unnecessary built-in APKS

Hello friends this is my first contribution to this forum, this file removes unnecessary built-in apks present in, /system/app & /system/priv-app.
I will miss the applications removed?
No, because a current copy of them is running on /data/app
Goal
Remove unused applications by the system
Free up space in the device memory
Compatibility
Nexus 5 android 6.0.1 must have root and twrp
How to use
Installed the android 6.0.1, get in playstore and update all applications, now just flash the zip via TWRP.
Removal list click to see
delete_recursive("/system/app/Chrome");
delete_recursive("/system/app/Books");
delete_recursive("/system/app/CloudPrint2");
delete_recursive("/system/app/Drive");
delete_recursive("/system/app/EditorsDocsStub");
delete_recursive("/system/app/EditorsSheetsStub");
delete_recursive("/system/app/EditorsSlidesStub");
delete_recursive("/system/app/FitnessPrebuilt");
delete_recursive("/system/priv-app/GCS");
delete_recursive("/system/app/PrebuiltNewsWeather");
delete_recursive("/system/app/NewsstandStub");
delete_recursive("/system/app/Maps");
delete_recursive("/system/app/PrebuiltBugleStub");
delete_recursive("/system/app/Photos");
delete_recursive("/system/app/PlusOne");
delete_recursive("/system/priv-app/GoogleContacts");
delete_recursive("/system/app/PrebuiltDeskClockGoogle");
delete_recursive("/system/priv-app/GoogleDialer");
delete_recursive("/system/app/PrebuiltGmail");
delete_recursive("/system/app/GoogleCamera");
delete_recursive("/system/priv-app/Velvet");
delete_recursive("/system/app/PrebuiltKeepStub");
delete_recursive("/system/app/talkback");
delete_recursive("/system/app/Music2");
delete_recursive("/system/app/PlayGames");
delete_recursive("/system/app/Hangouts");
delete_recursive("/system/app/GoogleTTS");
delete_recursive("/system/app/Videos");
delete_recursive("/system/app/WebViewGoogle");

This is a system partition
The deletion is useless because you can't use this space and you won't appreciate any differences
Read here, it is very very important
http://forum.xda-developers.com/showpost.php?p=64208563&postcount=3393
Personally I prefer to disable unnecessary apps
Pay attention

I do not like duplicate files, disabling an app the same will continue in the system, the idea is to not disable an app.
If I have the upgraded chrome in data\app I will not want an unusable copy of it on \system\app. My list does so with 30 Apps, if they are all updated on DATA I see no utility in maintaining obsolete unusable in the SYSTEM, and we still have the possibility to uninstall those we dislike.

ivn888 said:
This is a system partition
The deletion is useless because you can't use this space and you won't appreciate any differences
Read here, it is very very important
http://forum.xda-developers.com/showpost.php?p=64208563&postcount=3393
Personally I prefer to disable unnecessary apps
Pay attention
Click to expand...
Click to collapse
If you read that post he clearly says that to modify system you need to delete things from it to be safe. He is pointing out that it is an unknown. He said even to make small changes you would need more space. I see no reason to leave unneeded files in system. Maybe you want to run an app as system app and these unneeded files are getting in the way. Nothing wrong with getting rid of them.

We can use some root enabled file app managers (like es explorer, solid explorer) to uninstall the system apps.
I just want to know if is it safe or not?
And is it different than using flashable script?

parag60288 said:
We can use some root enabled file app managers (like es explorer, solid explorer) to uninstall the system apps.
I just want to know if is it safe or not?
And is it different than using flashable script?
Click to expand...
Click to collapse
File explorers with root function can enable manual removal of system apps, but it is laborious and tedious remove as many apps, It is safe if you know what you are removing, because the system is running if you give problem can fall into a bootloop... my flash file is safe removal of 30 apps, all with updated copies of the same in DATA folder so I ask you to enter the play store and update it before you use it, nothing is lost only copies obsolete and useless are removed.
The advantage here is not to miss anything, remove enough waste Rom, and return the power to uninstall what you do not want. I do not use play books, play movies, keep, Drive, Hangouts... so without losing any, then after the flash zip i have the freedom to uninstall what I want.

Debloating/Deknoxing a Stock ROM and creating one

I assume that you already have TWRP setup on your phone so I will not go through that process here.
Android version and Phone model
My tests are based off the latest stock ROM of the Canadian SM-G920W8 SIM unlocked model. The latest supported version of Android for the Samsung Galaxy S6 is Nougat version 7.0. Versions higher than that have serious camera issues, and yes, I tried MANY ROMs. Activating API2, trying other camera apps. They all sum up to be pretty much all the same with their different sets of problems. This is why I chose the latest v7.0 stock ROM. I have not fell on any v7.1.1 ROMs and v7.1.2 have camera issues too. So, I took the latest that does not come with camera issues.
Hardware key combinations to remember
Urgent/Bootloop shutdown and reboot: Volume DOWN + Home + Power
Enter TWRP: Volume UP + Home + Power
Assayyed Kitchen: XDA Thread
This tool is the best and easiest one I have found for Windows. I just do not use the debloat and deknox options as I do it myself with a personal webserver in PHP I wrote for myself. Assayyed Kitchen uses 3 main folders for working. PLACE, WORK and READY.
PLACE: You put there a zipped ROM or any Stock files in there. Assayyed will do all the unzipping for you.
WORK: Once Assayyed has done it's magic, you should see your needed files there where "system" is the most important one we will focus on here.
READY: That's where your final zip file is created for you to copy on your phone and install.
You do not need to use the PLACE folder if you already have a full uncompressed "system" folder. Simply copy and paste the "system" folder inside the WORK folder and use Assayyed skipping the #1 step of creating a project.
I will answer these questions:
Which files do I need to delete to remove KNOX, also known as deknox the rom?
Which files and apps can I safely remove to boot my phone with a clean Android system also known as debloat?
Now, debloating is still in a work in progress on my side because I have a very ambitious debloating project, like many. The aim of this debloation is to:
Remove all Google apps,framework and libs
Remove all useless Samsung apps that do not interfere with proper working equipement.
Remove all other additional apps
All I want is to keep the barebones of a functionning Android system while maintaining some needed functionalities such as a photo gallery, calendar and the camera.
Many ROM creators have their very own definition of DEBLOAT. They not only debloat the ROM but REBLOAT them with their own personal bloatwares INCLUDING magisk and sql lite and other hacks and apps for advanced configs. The goal of my ROM is to be able to install ON MY OWN Magisk, Open GApps and other stuff if I want AND not limited to versions that are included in the ROM. ROMs with Magisk, for example, use Magisk version uploaded at the time but Magisk evolves with time and newer version become available. So I hated to have all that stuff to take care about. It's the very basic stock rom debloated with nothing more than what stock offered. No kernels, no additional software, just a pure debloated and deknoxed ROM.
Here are the lists of what I have successfully debloated with a successfull boot for now. Note that I did not add the ".apk" because those files are usually inside their respective folders BUT, should you have no folders inside the app or priv-app folder, then simply add ".apk" at the end of the name. Other thing to mention, the root directory is "system". SInce my server works with the "system" folder directly, I did not add the "system/" at the beginning of every line. The complete lists are files and folders contained inside the "system" folder. Note that some files have no extentions too and should not be mistaken for folders.
Remove KNOX or comonly said DEKNOX
// ====
// Knox
// ====
app/KNOXStub
app/KNOXStore
app/KnoxAttestationAgent
app/KNOXAgent
app/KLMSAgent
app/ContainerAgent
app/ContainerEventsRelayManager
app/KnoxFolderContainer2
app/KnoxRemoteContentsProvider
app/KnoxAppsUpdateAgent
app/KnoxFolderContainer
app/KnoxSetupWizardClient
app/KnoxSwitcher
app/MyKNOXSetupWizard
app/KnoxMigrationAgent
app/KnoxSetupWizardStub
app/SamsungDLPService
app/BBCAgent
app/SecurityLogAgent
priv-app/MyKNOXSetupWizard
priv-app/KLMSAgent
priv-app/SPDClient
priv-app/SKMSAgent
container
tima_measurement_info
framework/knoxsdk.jar
framework/knoxvpnuidtag.jar
etc/secure_storage/com.sec.knox.store
etc/secure_storage/com.sec.knox.store!dex
// ==========================================================
// Phone will FAIL to boot if the following files are deleted
// ==========================================================
//etc/permissions/knoxsdk_edm.xml
//etc/permissions/knoxsdk_mdm.xml
//lib/libknox_encryption.so
//lib/libknox_km.so
//lib/libknox_legacy_ode_km.so
//lib/libknox_migration.so
//lib/libknoxvpnfdsender.so
//lib64/libknox_encryption.so
//lib64/libknox_km.so
//lib64/libknox_legacy_ode_km.so
//lib64/libknox_migration.so
//lib64/libknoxvpnfdsender.so
//framework/arm64/boot-knoxsdk.art
//framework/arm64/boot-knoxsdk.oat
//framework/arm64/boot-knoxvpnuidtag.art
//framework/arm64/boot-knoxvpnuidtag.oat
//framework/arm/boot-knoxsdk.art
//framework/arm/boot-knoxsdk.oat
//framework/arm/boot-knoxvpnuidtag.art
//framework/arm/boot-knoxvpnuidtag.oat
Incomplete but functional Samsung apps safe to remove
// =======
// Samsung
// =======
app/SamsungSans
app/VirtualTour_N_OS
app/VideoTrimmer_Dream
app/VideoEditorLite_Dream_N
app/VideoCollage_Grace_N
app/SlowMotion_Dream_N
app/EasterEgg
app/EasyOneHand3
app/GameOptimizer
app/WallpaperBackup
app/Weather2017_SE
app/WeatherWidget2017_SE
app/SmartRemote_zero
app/SmartSwitchAgent
app/SmartcardService
app/SecFactoryPhoneTest
app/SecurityProviderSEC
app/STalkback
app/OneNote_Compact_Samsung
app/GearManagerStub
app/SecMemo3
app/AllshareFileShare
app/AllshareMediaShare
app/SBrowser_5.0
app/SPrintSpooler7
app/CloudGateway2017
priv-app/GalaxyAppsWidget_Phone
priv-app/SamsungPayStub
priv-app/SamsungBilling
priv-app/GalaxyApps_3xh
priv-app/GalaxyCare
priv-app/GalaxyThemes
priv-app/PowerPoint_SamsungStub
priv-app/SamsungAccount_Dream
priv-app/SamsungCloud
priv-app/HealthService
priv-app/LegacySmartManagerProvider
priv-app/SamsungPass_1.1
priv-app/VoiceNote_5.0
priv-app/Word_SamsungStub
priv-app/ThemeCenter
priv-app/SecLiveWallpapersPicker
priv-app/SHealth5
priv-app/SmartManager_v5
priv-app/SmartManager_v5_DeviceSecurity
priv-app/EasyLauncher2_Zero
priv-app/SVoicePLM
priv-app/SmartcardManager
priv-app/SVoiceLang_EnglishPack_US_1.0
priv-app/SVoiceLang_FrenchPack_1.0
priv-app/SamsungMagnifier3
priv-app/SecEmail_N
priv-app/SecureFolderStub
priv-app/EasySetup
priv-app/GameHome
priv-app/GameTools
priv-app/OneDrive_Samsung_v2
etc/sysconfig/samsungaccount.xml
etc/sysconfig/samsungauthframework.xml
etc/sysconfig/samsungemail.xml
etc/sysconfig/samsungfidouafasm.xml
etc/sysconfig/samsungfidouafclient.xml
etc/sysconfig/samsungpushservice.xml
framework/gamemanager.jar
// ================================================
// Phone will have an EmergencyModeService has stopped
// if only the Launcher is removed and bootloop if the other
// 2 are removed so might as well keep them all.
// ================================================
// app/EmergencyLauncher
// app/EmergencyModeService
// priv-app/EmergencyInfo
Audio files debloat
These are extra Audio files that are not necessary for the phone to boot and like most people, you will probably customize your own ringtones. I kept a few basic ringtons and sounds so the phone can have something to work with on startup, but these files, to me are extras and unecessary.
media\audio\ringtones\A_Rustling_in_the_Trees.ogg
media\audio\ringtones\Basic_Bell.ogg
media\audio\ringtones\Basic_Tone.ogg
media\audio\ringtones\Beep_Once.ogg
media\audio\ringtones\Beginning.ogg
media\audio\ringtones\Bunny_Hopping.ogg
media\audio\ringtones\Chimes.ogg
media\audio\ringtones\Crossing_a_River.ogg
media\audio\ringtones\Dance_Party.ogg
media\audio\ringtones\Day_by_Day.ogg
media\audio\ringtones\Drifting_Downstream.ogg
media\audio\ringtones\Ecliptic.ogg
media\audio\ringtones\First_Light.ogg
media\audio\ringtones\Fresh_Morning.ogg
media\audio\ringtones\Mystic_Tone.ogg
media\audio\ringtones\Ocean_Voyage.ogg
media\audio\ringtones\One_Step_Forward.ogg
media\audio\ringtones\Prelude.ogg
media\audio\ringtones\Scampering_Tone.ogg
media\audio\ringtones\Somewhere.ogg
media\audio\ringtones\Ticktac.ogg
media\audio\ringtones\Warm_Greetings.ogg
media\audio\notifications\Beep_Once.ogg
media\audio\notifications\Good_Time.ogg
media\audio\notifications\Run.ogg
media\audio\notifications\S_Harmonics.ogg
media\audio\notifications\S_Opener.ogg
media\audio\notifications\S_Temple_Bell.ogg
media\audio\notifications\Sweet_Favour.ogg
media\audio\notifications\Whisper.ogg
media\audio\notifications\Hello.ogg
media\audio\notifications\Peanut.ogg
media\audio\notifications\S_Bubbles.ogg
media\audio\notifications\S_Charming_Bell.ogg
media\audio\notifications\S_Dew_drops.ogg
media\audio\notifications\S_Knock.ogg
media\audio\notifications\S_Tickety_Tock.ogg
WIP - Revove all Google framework and apps
I went through the entire apk, framework and lib folders from a full Open GApps zip file and tried to remove all of what it installs and I get a Bootloop, So working on trying to figure out what causes this.
I found some answers at these links concerning files that makes the phone fail to boot and other usefull information.
Project-Deep-Clean
Remove all Google apps from an android phone
Other lists to come soon when I am able to get my phone to boot with my removed apps...
In the mean time...
ROOTED phones: Removing unwanted apps WITHOUT using TWRP
So, I came upon a few things for the brave amongst you who wish to debloat their phones with root access but without using scripts in TWRP. Here is what you need to know.
Paths at the root of the phone, NOT sdcard...ROOT
/data/user/0 : This is where your installed apps are BUT they are saved under their package name and not their APK names. If you delete anything in this folder, you need to reboot after you are done cleaning in here.
/system/app : These apps re-install on phone reboot if not present
/system/priv-app : Same as above, these apps re-install on reboot if not present
File browser with ROOT access
I use Total Commander which can be downloaded from the Google Play Store. Once you open it, you need to enable root access by going into the app's settings using the "Configure..." option in it's menu. The scroll down to the bottom and check the box "Root functions everywhere". If you installed Magisk, the root permissions granting popup should appear for you to grant forever. Now, you can explore the entirety of your phone to delete those pesky apps.

Great guide! I've been meaning to get into making my own ROMs, particularly now that development for the S6 has all but stopped.
However, when I unpacked Assayyed my AV scanner Immunet (which uses CISCO's AV database) pinged up that there were 4 instances of "Andr.Dropper.Slocker::apk.agent.talos". These were in Superuser.apk, CLASSIC.zip, ASSAYYED.exe and FAST.zip.
Now, maybe this trojan is part of how the software operates - I could certainly see that as a possibility with things related to MicroG - but really a tool meant to remove things from a ROM, a tool you run in Windows oustide of Android, shouldn't be adding stuff like that back in.

TWeaKoR said:
Great guide! I've been meaning to get into making my own ROMs, particularly now that development for the S6 has all but stopped.
However, when I unpacked Assayyed my AV scanner Immunet (which uses CISCO's AV database) pinged up that there were 4 instances of "Andr.Dropper.Slocker::apk.agent.talos". These were in Superuser.apk, CLASSIC.zip, ASSAYYED.exe and FAST.zip.
Now, maybe this trojan is part of how the software operates - I could certainly see that as a possibility with things related to MicroG - but really a tool meant to remove things from a ROM, a tool you run in Windows oustide of Android, shouldn't be adding stuff like that back in.
Click to expand...
Click to collapse
Finding a WINDOWS tool to create a ROM is already not easy. On my side, I have not had any issues in running Assayyed. But I agree that the devs should AT LEAST try to make their apps AV detection free or at least warn people as to why they've incorporated those codes inside their app. BUT, that left asside, all the scripts used to do the work are available and one can simply make their own scripts or bat files and never use Assayyed as they simply launch commands from their scripts. Thank you for this information though!!!