Related
If I take a ROM in .ZIP format and unzip it on my PC into a folder with the same name...
Then delete any .APKs of programs I have no use for (Twidroid, facebook, etc) and then replace the boot.img with a different kernel of my choice and different SuperUser.apk...
Can I then ZIP this primary folder and load it as a ROM onto my MT3G?
Forgive me if this sounds really stupid, but I have no idea.
Would it need to be "cooked" before I can load it??
When you cook you need to make sure the gloves are on and you have the oven's temp turned up real nicely to fry that thing
I guess you didnt search or something? I need you to confirm that you cant/can see this at the top left corner of screen:
xda-developers > Dream > Dream Android Development
Press Dream then head to Q&A section please.Wait a sec...Thats not a Dream..You belong here for asking q's about your phone:
http://forum.xda-developers.com/forumdisplay.php?f=480
Just do a search for signing tool and it shows up.
rbrainard said:
If I take a ROM in .ZIP format and unzip it on my PC into a folder with the same name...
Then delete any .APKs of programs I have no use for (Twidroid, facebook, etc) and then replace the boot.img with a different kernel of my choice and different SuperUser.apk...
Can I then ZIP this primary folder and load it as a ROM onto my MT3G?
Forgive me if this sounds really stupid, but I have no idea.
Would it need to be "cooked" before I can load it??
Click to expand...
Click to collapse
its more complicated than it looks...
First u will have to know if removing those .apk will not cause any trouble...
Second u will have to sign the apks u r going to add, and signed the zip too...
about changing the boot.img has been tried before in another thread...
but most important u will have to search, search and read, read...
going to try and find some thread for u, before the mods closed this...
Need to have it resigned...once a zip file is open it breaks the signature but I would aslo like to kno if this is possible
ilostchild said:
Need to have it resigned...once a zip file is open it breaks the signature but I would aslo like to kno if this is possible
Click to expand...
Click to collapse
here its a thread about resigned:
http://forum.xda-developers.com/showthread.php?t=473580
read it all, has interesting stuff, but keep searching...
actually i would like to try this too...
if u ask devs, unless they want to teach u, great...
Wow...
You can open zips (roms/updates) and browse them without the need to resign them. If you change any of the contents in a zip (rom/update) file, as in remove or add, then you have to resign. You do not have to resign the apks you add to the zip (rom/update) file.
To do what you want to do, refer to the link about signing zips that was posted above. Remove the APKs, sign the zip (rom/update) file, and apply the update to your phone.
bring in the wrecking crew!
anyone know how to run this on a mac?
Ha people had post, but the one that make the thread, its no where...
Sweet! Thanks folks.
The "Search" function is the most important in any forum, but it does the user no good if they have absolutely positively no idea what to search for... lol
My goal is to take Manup's Eclair_2.1-v1.5 and remove all the .APKs I don't have any use for... Swap the boot.img for the eclair one with the 10MB hack, replace the SpareParts.APK with one that contains "Keep home app in memory" option, etc, etc, etc.
rbrainard said:
If I take a ROM in .ZIP format and unzip it on my PC into a folder with the same name...
Then delete any .APKs of programs I have no use for (Twidroid, facebook, etc) and then replace the boot.img with a different kernel of my choice and different SuperUser.apk...
Can I then ZIP this primary folder and load it as a ROM onto my MT3G?
Forgive me if this sounds really stupid, but I have no idea.
Would it need to be "cooked" before I can load it??
Click to expand...
Click to collapse
You've just described in detail what about 90% of roms out there really are: open zip, add/remove files, ..., profit!!!
As mentioned correctly by Moonspoon, all you'd need afterwards is to sign your package (just to ensure that there's no problems with the signature, delete the three files inside /META-INF (leave the folders alone)).
Also, as mentioned by ginatojr (kind of...), you have to know which files you're removing, for example, removing TelephonyProvider.apk, well, that should be obvious. One that's not so obvious is gtalkservice.apk. When I first started, I removed it because I though it was part of Google Talk, when in fact it's more closely related to GoogleApps and SubscribedFeedsProvider.
The only times you want to deal with signatures is if your roms come from two different sources (if you're using an AOSP test-signed core and want to toss in some release-singed Google apps), but for the most part it's unnecessary and mostly discouraged as it's a different can of worms.
So, yeah, that's basically "Rom Cooking 101", where most other people releasing roms are at "Rom Cooking 102", there's really nothing to it.
rbrainard said:
Sweet! Thanks folks.
The "Search" function is the most important in any forum, but it does the user no good if they have absolutely positively no idea what to search for... lol
My goal is to take Manup's Eclair_2.1-v1.5 and remove all the .APKs I don't have any use for... Swap the boot.img for the eclair one with the 10MB hack, replace the SpareParts.APK with one that contains "Keep home app in memory" option, etc, etc, etc.
Click to expand...
Click to collapse
The keep in home might not work on 2.1 roms yet.
If this works out... My future plans would include doing this to streamline and modify any ROM of my choice as they are released.
I have absolutely no intention of modifying ROMs for redistribution.
This will be for my own personal needs alone.
Can anyone tell me where the .APK files of Market downloads are stored on the handset?
rbrainard said:
Can anyone tell me where the .APK files of Market downloads are stored on the handset?
Click to expand...
Click to collapse
NEVERMIND!
Found them in /SDCard/BackupRoot/app directory.
The last time I looked, the only dump for the Captivate on xda was a JF6 version, posted a few weeks ago, and the OP had taken out a few AT&T apps prior to doing it, making it not a true stock. This morning I decided to rip out the content out of the factoryrfs.rfs files from each of the three firmwares we have. I am planning to poke around in these a bit and try my hand at some deodexing, but I have also uploaded them for anyone else to play with them, or to restore any files they might have inadvertently deleted:
Here are the links:
JF6
JH2
JH3
JH7
rajendra82 said:
The last time I looked, the only dump for the Captivate on xda was a JF6 version, posted a few weeks ago, and the OP had taken out a few AT&T apps prior to doing it, making it not a true stock. This morning I decided to rip out the content out of the factoryrfs.rfs files from each of the three firmwares we have. I am planning to poke around in these a bit and try my hand at some deodexing, but I have also uploaded them for anyone else to play with them, or to restore any files they might have inadvertantly deleted:
Here are the links:
JF6
JH2
JH3
Click to expand...
Click to collapse
What do JF and JH stand for?
freedonkey said:
What do JF and JH stand for?
Click to expand...
Click to collapse
They relate to the month in which they were built. F means june, h is august. Both of the jh roms are test roms and unfinished, but functional and snappier than the stock jf6 rom.
Sent from my Samsung SGH-i987
Thanks for this.
Aye... Thanx for the system dumps.
Anyone seen these for the i9000?
alphadog00 said:
Anyone seen these for the i9000?
Click to expand...
Click to collapse
Easy to get the files out yourself. Extract the factoryrfs.rfs file out of the firmware tar file, boot into linux and do:
sudo mount -o loop factoryrfs.rfs <any_directory_of_your_choice>
Then copy the files from the mounted location to another, and you have the raw system dump.
Pardon my ignorance but what do these dumps do/provide? How are they different from the firmware from Samsung Firmware?
glio1337 said:
Pardon my ignorance but what do these dumps do/provide? How are they different from the firmware from Samsung Firmware?
Click to expand...
Click to collapse
The firmware from Samsung Firmware contains the applications and default configuration settings packed into a factoryrfs.rfs (which itself is then inside a .tar file). That format is suitable for Odin to flash onto the phone, but you can't access the individual files inside the .rfs. What I did was to unpack the .rfs file, so that the individual files inside are available for whatever you want to do with them. These are not suitable for flashing on the phone as a whole, but someone could take something, modify it and push it to their phone, or make a custom ROM out of it. A simple example is the circle battery indicator mod, where someone modified the framework-res.apk to show percentage, and then made a custom ROM update.zip with it. Without access to the original file, this would not have been possible. Everyone has these files on the phone in one version or another (unless they manually edit or delete them). I just wanted all versions of the files ever released or leaked.
I dont know if this is the place to ask but how we can extract particular app to be able to install it as .apk
here is what i need
http://forum.xda-developers.com/showthread.php?t=776739
zagorka said:
I dont know if this is the place to ask but how we can extract particular app to be able to install it as .apk
here is what i need
http://forum.xda-developers.com/showthread.php?t=776739
Click to expand...
Click to collapse
All the apks are inside the zip files, stored the same way they would normally reside on your phone. I am pretty sure the stock Clock widget is a touchwiz widget, and will not work on your wife's Aria. Hell it won't even work on our own phone if you switch to a different launcher.
rajendra82 said:
All the apks are inside the zip files, stored the same way they would normally reside on your phone. I am pretty sure the stock Clock widget is a touchwiz widget, and will not work on your wife's Aria. Hell it won't even work on our own phone if you switch to a different launcher.
Click to expand...
Click to collapse
I am talking about ClockPackage not SamsungWidget_CalendarClock or SamsungWidget_StockClock. It's the one in applications not the widgets.
zagorka said:
I am talking about ClockPackage not SamsungWidget_CalendarClock or SamsungWidget_StockClock. It's the one in applications not the widgets.
Click to expand...
Click to collapse
Clockpackage is in the zip files. Here is the JH3 version for you. Not sure if it'll install. When I try to push to the Android 2.1 Emulator, I get:
adb install ClockPackage.apk
1404 KB/s (0 bytes in 2921292.002s)
pkg: /data/local/tmp/ClockPackage.apk
Failure [INSTALL_FAILED_MISSING_SHARED_LIBRARY]
Which tells me that the package is probably dependant on TouchWiz 3.0 or some other library already installed on the phone.
rajendra82 said:
Clockpackage is in the zip files. Here is the JH3 version for you. Not sure if it'll install. When I try to push to the Android 2.1 Emulator, I get:
adb install ClockPackage.apk
1404 KB/s (0 bytes in 2921292.002s)
pkg: /data/local/tmp/ClockPackage.apk
Failure [INSTALL_FAILED_MISSING_SHARED_LIBRARY]
Which tells me that the package is probably dependant on TouchWiz 3.0 or some other library already installed on the phone.
Click to expand...
Click to collapse
Yes, I was able to extract the .apk and .odex files but couldnt install them.
Probably you are right it is too much trouble. I'll look for some alternative.
Thank you
I think he zipaligned the system apk's too
designgears said:
I think he zipaligned the system apk's too
Click to expand...
Click to collapse
I am very new to android, so I am not sure of the implications of this. After further investigation, there is a newer version of the bat files (Auto_Deodexer_2.3), but that version does not do any zipaligning. I added my own bat file to do this after the deodexing, but is what the older version did (zip align every apk in the app directory) bad, and why? If that is the case, which of the apk files should I not zipalign?
On a similar note, the newer bat file asks me to give a bootclasspath. When I give it the values in the init.rc, it skipped deodexing few of the apks in the app directory. When I added twframework.jar to the bootclasspath ahead of framework.jar, it skipped fewer files. I am sure that the older version was buggy, and made mistakes. What should the proper bootclasspath be to not skip deodexing the following files, and to properly deodex the others:
BluetoothOPP.apk+odex
Camera.apk.odex
FactoryTest.apk+odex
MiniDIary.apk+odex
TouchwizCalendar.apk+odex
Figured out the bootclasspath to use. OP and the JH3 file updated. If you downloaded the deodexed JH3 version yesterday, please replace it with the newer version.
What exactly does deodexing and zipaligning do? I understand it makes it faster but how so?
Sent from my SAMSUNG-SGH-I897 using XDA App
frenchtoasted said:
What exactly does deodexing and zipaligning do? I understand it makes it faster but how so?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
All this is highly theoretical knowlege on my part, so if anyone has better information, feel free to correct me:
Deodexing:
Some of the apks and jar files on the default stock ROM have their code split between apk/odex and jar/odex pairs instead of in a single file. This is done by the developers to supposedly save space, and memory usuage, and to speed up the booting process. Unforunately having separate odex files means that replacing any part of the whole system is much harder. Deodexing the ROM puts the code from the odex files back into the apk and jar files so that every application and jar is self contained and could be replaced with an equivalent.
Zipaligning:
Zipaligning is an optimization of apk files to align all uncompressed data within them on 4-byte boundaries to reduce the memory usage. Since deodexing rebuilt the apks with the code from the odex files, they would have become unaligned. I realigned them to make them optimized again.
This is not necessarily a performance tweak at first, but once you are able to replace the slower parts of the system as a result of it, you should start to get more benefits out of it.
would it be possible to get the allshare package from the deodexed rom? will it work with any other device?
WHAT IS AN ODEX FILE?
In Android file system, applications come in packages with the extension .apk. These application packages, or APKs contain certain .odex files whose supposed function is to save space. These ‘odex’ files are actually collections of parts of an application that are optimized before booting. Doing so speeds up the boot process, as it preloads part of an application. On the other hand, it also makes hacking those applications difficult because a part of the coding has already been extracted to another location before execution.
THEN COMES DEODEX
Deodexing is basically repackaging of these APKs in a certain way, such that they are reassembled into classes.dex files. By doing that, all pieces of an application package are put together back in one place, thus eliminating the worry of a modified APK conflicting with some separate odexed parts.
In summary, Deodexed ROMs (or APKs) have all their application packages put back together in one place, allowing for easy modification such as theming. Since no pieces of code are coming from any external location, custom ROMs or APKs are always deodexed to ensure integrity.
HOW THIS WORKS
For the more geeky amongst us, Android OS uses a Java-based virtual machine for running applications, called the Dalvik Virtual Machine. A deodexed, or .dex file contains the cache used by this virtual machine (referred to as Dalvik-cache) for a program, and it is stored inside the APK. An .odex file, on the other hand, is an optimized version of this same .dex file that is stored next to the APK as opposed to inside it. Android applies this technique by default to all the system applications.
Now, when an Android-based system is booting, the davlik cache for the Davlik VM is built using these .odex files, allowing the OS to learn in advance what applications will be loaded, and thus speeds up the booting process.
By deodexing these APKs, a developer actually puts the .odex files back inside their respective APK packages. Since all code is now contained within the APK itself, it becomes possible to modify any application package without conflicting with the operating system’s execution environment.
ADVANTAGES & DISADVANTAGES
The advantage of deodexing is in modification possibilities. This is most widely used in custom ROMs and themes. A developer building a custom ROM would almost always choose to deodex the ROM package first, since that would not only allow him to modify various APKs, but also leave room for post-install theming.
On the other hand, since the .odex files were supposed to quickly build the dalvik cache, removing them would mean longer initial boot times. However, this is true only for the first ever boot after deodexing, since the cache would still get built over time as applications are used. Longer boot times may only be seen again if the dalvik cache is wiped for some reason.
For a casual user, the main implication is in theming possibilities. Themes for android come in APKs too, and if you want to modify any of those, you should always choose a dedoexed custom ROM.
Source From www.addictivetips.com
This looks to be a copy and paste from the description here.
If you are not the original author its usually a wise idea to acknowledge the original author/source.
And optimized dex files (odex files) may also depended on the framework classes interfaces. This means that you may end up with bootloops or FCs if you change the interface of framework files. The odex files have therefore been given a signature that all files must match.
Deodexed apks can on the other hand be used on several roms as they may only be depended on the resources in the framework-res.apk file.
So you can have an odexed framework with deodexed apks! But if you want to change the interfaces in the Framework then it is easier to deodex all instead of re-odex all.
Sent from my GT-N7000 using xda premium
Thanks for it! For me more clear now.
I need to verify this, So on an ODEXED STOCK ROM, Can I make changes like
editings png's inside System APK files,
Decompile and compile framework-res.apk,
Make changes to the framework-res.apk to enable crt screen effect ... ?
Clears another thing up for me...
Thank you for your post.
Sorry guys for posting a stupid question, but i'm not clear on one point.
I have the htc one S [s3]. How can I understand if /system/framework/framework-res.apk (and/or) framework-htc-res.apk are already deodexed? (in a practical manner)
I mean...since is an apk and I'm not seeing any framework-res.odex are they already deodexed?
Can I straightly modify it?
Thx in advance!
Hi... Cant cant i something? So what is better of them?
Sent from my GT-N7000 using xda premium
Emothic_Reagan said:
Hi... Cant cant i something? So what is better of them?
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Is not that one is better than the other. They have different characteristiocs. Odexed are smaller and faster while deodexed are easily customizable but needs more space.
Guys I still need somebody to answer my question...plz...anybody?
I'm in the process of deodexing the stock ROM (4.5.1-134_DFP-82) on my Defy+. I've tried a number of the deodexing tools posted around XDA and elsewhere but nothing would run anything like clean, so I've been building my own script to do it.
I've successfully deodexed everything in /system/framework/ and 151 out of 155 odexes in /system/app/. It has been quite interesting, tracking down the missing classes when something doesn't deodex clean first time with the default BOOTCLASSPATH files. Unfortunately, though, four of the .odexes in /system/app/ have got me beat.
The first one is Settings.odex. This is reporting:class Lcom/motorola/android/mirrorservice/IMirrorService; cannot be resolved.I can't locate that class anywhere. I've tried disassembling everything in both directories and searching the results but it just doesn't seem to be there. Settings seems rather too important to just allow baksmali to ignore the error.
The other three - DLNA.odex, MediaGallery.odex and VideoPlayer.odex - all display the same symptom. Trying to deodex with just the standard BOOTCLASSPATH files gives the error:class Lcom/motorola/android/extdispservice/IExtDispService; cannot be resolved.Adding /system/framework/com.motorola.blur.library.service.odex to the BOOTCLASSPATH files makes that go away, but instead gives the error:Could not find superclass Lcom/google/protobuf/GeneratedMessage$BuildeI've seen that one several times and the way to fix it has always been to add /system/framework/com.motorola.blur.library.utilities.odex to the BOOTCLASSPATH files. But in this case I end up with the error:class Lcom/motorola/android/extdispservice/IExtDispService; cannot be resolved.again. It's taking me round in circles! I've tried reversing the order of utilities and service but that doesn't fix it either.
Anyone able to suggest how I might get rid of these errors? The second one in particular is doing my head in!
OK, so I've done a bit more digging around online and it seems that both those classes are to do with the HDMI interface, which of course the Defy doesn't have. baksmali continues anyway and creates the out folder, so I'm assuming that it should be OK to zip those back in to the relevant apks and try those. Does that sound right?
Hi ejstubbs
thanks for starting this thread...i was wanting to start deodexing roms on my own. can you please help me with the apps needed and/or some link where i can get a thorough knowhow about deodexing roms for my Defy?
Questions go in the Q&A section, not the Dev section.
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!!!