This script removes unnecessary files and adds the file
Script deletes files...
Code:
system/app/Apollo.apk");
system/app/Browser.apk");
system/app/Calculator.apk");
system/app/Calendar.apk");
system/app/CMWallpapers.apk");
system/app/Email.apk");
system/app/LatinIME.apk");
system/app/Term.apk");
system/app/VideoEditor.apk");
system/app/CMFileManager.apk");
system/app/Exchange2.apk");
system/app/Galaxy4.apk");
system/app/Gallery2.apk");
system/app/NoiseField.apk");
system/app/LiveWallpapersPicker.apk");
system/app/MagicSmokeWallpapers.apk");
system/app/PhaseBeam.apk");
system/app/VoicePlus.apk");
delete_recursive ("/system/media/audio/notifications");
delete_recursive ("/system/media/audio/ringtones");
system/media/audio/notifications
system/media/audio/ringtones
Leaves only one ringtone and notification
Sets the modified host file patched program AdFree
With this script you can free up about 100 mb
Installation: Flash file via recovery
Download v1.0 :http://d-h.st/6ew
Download v1.1 : http://d-h.st/IQR
For version 22.05.14 CM 11 use version v1.0 which does not remove the standard live wallpaper, without them off point wallpaper
Related
I have a shutdown sequence and some sounds I would like to turn in to a flashable .zip file. I checked out the CW forums, but that was more painful than informative. I have taken a look at some of the zip files I have found so far, but am not 100% sure about what I'm doing. Can anyone point me to a how-to or even in the general direction of some information to get me started?
Thanks guys!
Edit: Those interested can find all the information needed in the3dman's post and here:
http://www.londatiga.net/it/how-to-create-android-update-zip-package/
http://www.londatiga.net/general/how-to-sign-apk-zip-files/
I'd copy this guy
http://forum.xda-developers.com/showthread.php?t=795459
Thanks for the link. I had actually started there, and it's a great template if I just want to throw in my own files, but I was really looking for a how to so that I had more options for customizing, rather than being stuck with only the shutdown / startup sequence.
Sent from my SGH-T959 using XDA App
First you have to have your folder structure like this in the zip:
Main .zip
{
META-INF { com -> google -> android -> update-script } ( <- these are folders inside the META-INF except update-script this is a script file)
app (if the file you want to flash is an app it goes in this folder)
framework (if the file you want to flash is a framework file it goes in this folder)
system (if the file you want to flash is a system file (start up animations) it goes in this folder also make sure you put the correct subfolder inside this folder ie: if your file goes in system -> media make sure you put the file you wish to flash in a correctly named subfolder other wise it will flash into just the system folder and not into the correct folder within the system folder on your phone.)
}
After your folder structure is set up you must tell clockwork which folder or folders in the zip to flash. To do this open the update-script from the zip with a text editor and modify or add these lines with the correct folders.
copy_dir PACKAGE:framework SYSTEM:framework (use this for the framework folder)
copy_dir PACKAGE:app SYSTEM:app (use this for the app folder)
copy_dir PACKAGE:system SYSTEM:system (use this for the system folder)
Then sign your zip and flash.
Below is a picture of an example folder structure so show what I mean. Also I attached a zip with an example update-script in it.
the3dman said:
First you have to have your folder structure like this in the zip:
Main .zip
{
META-INF { com -> google -> android -> update-script } ( <- these are folders inside the META-INF except update-script this is a script file)
app (if the file you want to flash is an app it goes in this folder)
framework (if the file you want to flash is a framework file it goes in this folder)
system (if the file you want to flash is a system file (start up animations) it goes in this folder also make sure you put the correct subfolder inside this folder ie: if your file goes in system -> media make sure you put the file you wish to flash in a correctly named subfolder other wise it will flash into just the system folder and not into the correct folder within the system folder on your phone.)
}
After your folder structure is set up you must tell clockwork which folder or folders in the zip to flash. To do this open the update-script from the zip with a text editor and modify or add these lines with the correct folders.
copy_dir PACKAGE:framework SYSTEM:framework (use this for the framework folder)
copy_dir PACKAGE:app SYSTEM:app (use this for the app folder)
copy_dir PACKAGE:system SYSTEM:system (use this for the system folder)
Then sign your zip and flash.
Below is a picture of an example folder structure so show what I mean. Also I attached a zip with an example update-script in it.
Click to expand...
Click to collapse
Thank you very much! This was PERFECT for getting me started! This lead me to the following sites for more information on how-to's and even all the available syntax. For anyone looking to get into this (it's not difficult), check out these pages:
http://www.londatiga.net/general/how-to-sign-apk-zip-files/
http://www.londatiga.net/it/how-to-create-android-update-zip-package/
Hi community,
I recently started using SVN to download only revisions and not the whole 400mb ROM file. It's been great but recently I grew tired having to zip and copy 400MB to my phone. So I researched a way to export only the changes to a revision and to create a custom update-script file to flash the changes.
**From http://verysimple.com/2007/09/06/usi...odified-files/ **
-- Using TortoiseSVN, right-click on your working folder and select “Show Log” from the TortoiseSVN menu.
-- Click the revision that was last published
-- Ctrl+Click the HEAD revision (or whatever revision you want to release) so that both the old and the new revisions are highlighted.
-- Right-click on either of the highlighted revisions and select “Compare revisions.” This will open a dialog window that lists all new/modified files.
-- Select all files from this list (Ctrl+a) then right-click on the highlighted files and select “Export selection to…”
Once exported to your "Current" directory, you now have to create the custom update-script file so you can flash the changes. Lets say the revision changes were in the "system" folder (you'll notice this by looking at the exported files and see which folder they are under). Your update-script file would look like this (minus the borders):
***more in depth instructions are found here --> http://www.londatiga.net/it/how-to-create-android-update-zip-package/***
==========================================
show_progess 0.1 0
copy_dir PACKAGE:system SYSTEM:
show_progess 0.1 10
==========================================
a) show_progress 0.1 0 --> starts a progress bar
b) copy_dir PACKAGE:system SYSTEM: --> copies the contents of system (from your zip) to system (on your ROM)
c) show_progress 0.1 10 --> completes the progress bar
Again, name this file "update-script". Then place in your "Current" directory in folder ...\META-INF\com\google\android
Zip up the package as normal. To conclude, your zip file should have 1) the exported revision changes 2) the update-script file located in "Current"\META-INF\com\google\android
Hope this helps. Feel free to critique.
PS - remember to read the log from SVN. Sometimes, a full 400MB zip and push is needed.
I have flashed it on my Note, it works well.
I in no way created this, just thought it may be worth while.
The operation of this template is based on the VillainTheme System for the ROM VillainROM.
Link: http://www.villainrom.co.uk/forum/sh...inTheme-System
Credits and thanks to all XDA team that collaborated on the original script: Doctorcete, Stericson, Matt and Seshy
What is Universal Flasher Tool?
is a complete template that is used to create the simplest possible way a subject flashable from recovery without the need to include or edit files. apk.
This new method uses the file system implementation metamorph (just have to put files and folders on their respective routes), with the advantage that the system identifies and injected into their applications without the need for external application. The subjects are flashed directly from recovery.
What are the advantages of this method compared to metamorph or traditional flasheables issues?
Do not include. Apk complete, only the files you want to include in the subject.
A theme created with this template is valid for any rom, even among different phone roms (the tests have been performed with SGS2 and Nexus one).
Optionally, the template can include complete files if desired, can even be used to install applications not system.
Does not depend on external applications like metamorph because it flashes directly from recovery.
Operation of the template
at the end of the post are attached a number of considerations to take into account, but basically works like this:
Identify the applications that want to thematize and checks that exist in the rom. Once the check, the system compares folders that will be introduced as well as files and injects them into the apk as long as the new file exists within the apk. This has been thought well to avoid filling an apk with files that do not belong because they are from another rom or because you made a mistake when typing the name, for example.
Once injected the files takes a zipalign the apk to optimize RAM usage.
Alternatively, if the topic includes external files or copy them to install applications on your path.
At the same time to be using the item, the system will generate a backup of changed files and automatically creates a file. Zip flashable from recovery, in case something goes wrong or do not like changes to previous state.
Finally, it also generates a small log with the outcome of the whole process is recorded in SD to verify that all changes are properly implemented.
How to create and edit your own theme
Download the template from the attachment in this post or the link below.
Recommended Tools: 7zip to include files and browse the file system (you can also use winzip or winrar without problems) and Notepad + + or any other plain text editor to edit the name of the mod.
Once downloaded, open the template double-click will observe and folders inside a file in the root. Here's that are in each folder and how to create the theme.
MOD.config file: (new from version 3.0) is an editable text file (recommend Notepad + +) where in addition to establishing the name of the MOD to set different parameters of the template.
MOD_VERSION= Name (name of the mod to be displayed in the system properties after the name of the rom. Are cautioned not to put a name too long and try to avoid as far as possible in the blanks.
CLEAN_MORPHING = not (compare the new files before injection into the apk, only enter if the file already exists. Turning the option dramatically reduces speed)
V4_MORPHING = yes (support to manage compatibility with existing folders-v4 system in some applications).
DO_BACKUP = yes (enable or disable the creation of the flashable backup from recovery to restore the existing theme).
LOG_ENABLED = yes (enable or disable the creation of a log file with the results of the process).
SCREEN_LOG = yes (shows the process of recovery on the screen or not. important notices are always shown even if the option is disabled).
Optionally, you can set a different path for memory cards (no need to touch these lines in most cases, you should not touch):
default_internal_sdcard = / EMMC
default_external_sdcard = / sdcard
Optionally, you can add special commands to mount partitions (no need to modify these lines in most cases, you should not touch):
mount_system = mount / system
mount_data = mount / data
README.txt:
Includes some additional instructions on the operation and the license. Please read before using the template to create a theme (in English). Carteta / tools: is the folder where you have placed the scripts and binary files necessary to flash the issue and make subsequent restoration. You do not need to touch anything in this folder to edit the theme. From version 3.0 has been deleted because busybox binary is no longer involved in the process. folder / META-INF folder system which includes the signature file and the script to launch from recovery. It is recommended not to touch. Folder / MORPH: This is the template folder where files should be included with the theme. In turn, the folder is divided into two subfolders called / data (for applications theming system NO) and / system (for theming system and applications framework). In the / MORPH / system / app files are included for the applications and / MORPH / system / framework for the framework files. NOTE: NO application theming system in / MORPH / data / app / myapp.apk supposed to change the digital signature, so from that time can not be updated from the market or will you installed in the market (like if it had been installed by 'other means' non-statutory ...). Therefore, we do not recommend any downloaded application thematize the market. You are advised that the complaints do not come then ... For each application you want to thematize must open a new folder called / nombre.apk (eg / Contacts.apk if you want to change the system application Contacts.apk) . It is necessary to respect the use of upper / lower case. Within each of these folders you have to respect that there are logical paths within applications, so that the files would have to place them in folders named / res / drawable, res / drawable-hdpi, etc ... It is the same structure metamorph an issue, so any item is readily convertible metamorph simply dragging folders.
No need to create any control file or anything like . The system is responsible for reviewing the folders to see what applications you want tematitar.
Folder / Xtras / system:
in this folder is where, if desired, can include files or complete applications that you wish to flash in conjunction with the subject. For example, sound files, bootanimation, scripts, complete applications, etc ... Folder / Xtras / data: in this folder is where, if desired, can not add applications to be installed system during flashing. Folder / Xtras / sdcard: in this folder you can add files to make copied to the SD card, as packs of icons, sounds, videos, etc ... to take into account considerations
Always respect the use of uppercase / lowercase letters in the names of files or folders and logical paths located within the apps.
With this system the themes may be universal, although depending on the type of files a user input may cease to be:
If you only include image files theme is compatible with any rom from any phone.
If you also include. xml may only operate in one rom, but can still work on future updates of it.
If resources are included for translations (resources.arsc) the issue would only be valid for a particular rom.
The. Zip with the issue is not necessary for you to sign flashearse, and is valid for CW-Recovery and Recorevy-RA. If you do not have to remember signing off signature checking before flashing.
Original Thread:http://http://www.htcmania.com/showthread.php?t=258333
Also:http://forum.xda-developers.com/showthread.php?t=1474686
On the galaxy s 3 us version most of the recoverys are not reading the external sd so should I changed the mounts on the script?
Sent from my SGH-T999 using Tapatalk 2
Hi guys!
I have cooked my rom!
Deodexed - rooted and zipaligned!
I have tryed flash with recovery.. it's OK!
when the phone starts I get an error
"the application has stopped working "
what is the APK name of message?
How to solve this error?
I have Galaxy S3
Only thing I can suggest is grabbing a logcat and seeing what is crashing, you aren't giving a whole lot of info there.
how do I view the logcat?
After you have recorded it then just open it in a text editor.
Sent from my SCH-R760 using Tapatalk 2
how do i view logcat?
Click to expand...
Click to collapse
not sure if you ment how to open the logcat file
or how to actually get the logcat file.
heres how to get it.
use adb
best way to do it.
you need to have adb setup on your computer
connect device to computer
open terminal or cmd
Code:
adb
this will give you usage info about adb if not adb needs to be added to PATH
Code:
adb logcat -d > path/to/ desktop/logcat.txt
you can find market app that will save logcat to your sd card
if I remember correctly "alogcat"
This is my logcat
App "Message" crashed!
http://paste.ubuntu.com/1062350/
line 7777
Help please :'(
Did you remove CSC folder?
I never had a folder csc
Code:
[email protected]:~/Scrivania/ROM/WORKING_062512_024231/system$ ls
app cameradata framework media usr vsc
bin etc hdic preloaddata vendor wakeupdata
build.prop fonts lib tts voicebargeindata xbin
roxdragon said:
I never had a folder csc
Code:
[email protected]:~/Scrivania/ROM/WORKING_062512_024231/system$ ls
app cameradata framework media usr vsc
bin etc hdic preloaddata vendor wakeupdata
build.prop fonts lib tts voicebargeindata xbin
Click to expand...
Click to collapse
You didn't extract it , it's included on the "cache.img", we can work without it on sgs2 but it's a must on sgs3.
Code:
============================================================
Android Kitchen 0.196 - by dsixda (xda-developers.com)
============================================================
11 - Deodex files in your ROM
12 - Add task killer tweak for speed (stock ROM only)
13 - Add /data/app functionality
14 - Add Nano text editor + sysro/sysrw
15 - Add Bash (command shell)
16 - Add Apps2SD
17 - Add /etc/init.d scripts support (busybox run-parts)
18 - Add custom boot animation functionality
19 - Porting tools (experimental)
20 - Tools for boot image (unpack/re-pack/etc.)
21 - Unpack data.img
22 - Sign APK or ZIP file(s)
23 - Convert update-script or updater-script
24 - Miscellaneous options / Plugin scripts
99 - Build ROM from working folder
0 - BACK TO MAIN MENU
Enter option: 0
============================================================
Android Kitchen 0.196 - by dsixda (xda-developers.com)
============================================================
1 - Set up working folder from ROM
2 - Add root permissions
3 - Add BusyBox
4 - Disable boot screen sounds
5 - Add wireless tethering
6 - Zipalign all *.apk files to optimize RAM usage
7 - Change wipe status of ROM
8 - Change name of ROM
9 - Check update-script for errors
10 - Show working folder information
0 - ADVANCED OPTIONS
99 - Build ROM from working folder
u - Update/About kitchen
x - Exit
Enter option:
How to extract cache.img?
with kitchen?
i have execute this:
Code:
CREATE WORKING FOLDER FOR ROM
==============================
Ensure there is at least one ROM under the 'original_update' folder!
Select an option:
s - Show supported formats
x - Abort, don't create working folder
Or press Enter to continue
? s
----------------------------------------------------------------------
The format for each ROM must be one of the following:
- system.img + optional boot.img/lib.img (e.g. stock ROM or Nandroid)
- ZIP file for a custom ROM (e.g. update.zip)
- ZIP file containing *.img (e.g. stock rom.zip)
- ZIP file containing shipped ROM in SYSTEM + BOOT folder format
- Working folder made with this kitchen (e.g. WORKING_old_rom)
Other formats:
Samsung Galaxy S:
- factoryfs.rfs + optional cache.rfs/zImage
- PDA.tar.md5 + optional CSC.tar.md5/PHONE.tar.md5
- PDA.tar + optional CSC.tar/PHONE.tar
- TAR/ZIP file containing factoryfs.rfs + more
- TAR/ZIP file containing PDA.tar.md5/PDA.tar + more
Samsung Galaxy S Plus:
- system.img.ext4 + optional cache.img.ext4/boot.img
- TAR/ZIP file containing system.img.ext4 + more
Samsung Galaxy SII:
- factoryfs.img + optional cache.img/zImage
- system.img.ext4 + optional cache.img.ext4/boot.img
- TAR/ZIP file containing factoryfs.img/system.img.ext4 + more
- system.ext4.tar + optional boot.img (Nandroid backup)
Huawei:
- APP file from Huawei software update (e.g. UPDATE.APP)
----------------------------------------------------------------------
Press Enter to continue, or type 'x' to abort:
Available ROMs:
(1) system.img and boot.img
Enter selection number (default=1, cancel=0):
Found original_update/system.img
Found original_update/boot.img
The new working folder will be named WORKING_062712_171010
Change the name (y/n)? (default: n):
Creating working folder WORKING_062712_171010 ...
Copying boot.img ...
Copying system.img ...
Adding an update-script ...
"system.img" -> "../system.img.ext4"
Warning: No cache.img.ext4 found. You can unpack this file separately
by running the plugin script in the kitchen's Advanced menu options.
If your device doesn't use a CSC, then just ignore this message.
Analyzing system.img.ext4 ...
Compiling simg2img ...
simg2img successfully compiled
Converting system.img.ext4 into a format for unpacking ...
computed crc32 of 0xb9d9b0e7, expected 0x00000000
Mounting ext4_system.img to loopback device and then extracting files ...
..............
..........
...
N.B
Code:
Warning: No cache.img.ext4 found. You can unpack this file separately
by running the plugin script in the kitchen's Advanced menu options.
If your device doesn't use a CSC, then just ignore this message.
into my original_update have:
Code:
[email protected]:~/Scrivania/ROM/original_update$ ls
boot.img cache.img hidden.img modem.bin recovery.img system.img
Can you help me please? Thank u
roxdragon said:
Code:
============================================================
Android Kitchen 0.196 - by dsixda (xda-developers.com)
============================================================
11 - Deodex files in your ROM
12 - Add task killer tweak for speed (stock ROM only)
13 - Add /data/app functionality
14 - Add Nano text editor + sysro/sysrw
15 - Add Bash (command shell)
16 - Add Apps2SD
17 - Add /etc/init.d scripts support (busybox run-parts)
18 - Add custom boot animation functionality
19 - Porting tools (experimental)
20 - Tools for boot image (unpack/re-pack/etc.)
21 - Unpack data.img
22 - Sign APK or ZIP file(s)
23 - Convert update-script or updater-script
24 - Miscellaneous options / Plugin scripts
99 - Build ROM from working folder
0 - BACK TO MAIN MENU
Enter option: 0
============================================================
Android Kitchen 0.196 - by dsixda (xda-developers.com)
============================================================
1 - Set up working folder from ROM
2 - Add root permissions
3 - Add BusyBox
4 - Disable boot screen sounds
5 - Add wireless tethering
6 - Zipalign all *.apk files to optimize RAM usage
7 - Change wipe status of ROM
8 - Change name of ROM
9 - Check update-script for errors
10 - Show working folder information
0 - ADVANCED OPTIONS
99 - Build ROM from working folder
u - Update/About kitchen
x - Exit
Enter option:
How to extract cache.img?
with kitchen?
i have execute this:
Code:
CREATE WORKING FOLDER FOR ROM
==============================
Ensure there is at least one ROM under the 'original_update' folder!
Select an option:
s - Show supported formats
x - Abort, don't create working folder
Or press Enter to continue
? s
----------------------------------------------------------------------
The format for each ROM must be one of the following:
- system.img + optional boot.img/lib.img (e.g. stock ROM or Nandroid)
- ZIP file for a custom ROM (e.g. update.zip)
- ZIP file containing *.img (e.g. stock rom.zip)
- ZIP file containing shipped ROM in SYSTEM + BOOT folder format
- Working folder made with this kitchen (e.g. WORKING_old_rom)
Other formats:
Samsung Galaxy S:
- factoryfs.rfs + optional cache.rfs/zImage
- PDA.tar.md5 + optional CSC.tar.md5/PHONE.tar.md5
- PDA.tar + optional CSC.tar/PHONE.tar
- TAR/ZIP file containing factoryfs.rfs + more
- TAR/ZIP file containing PDA.tar.md5/PDA.tar + more
Samsung Galaxy S Plus:
- system.img.ext4 + optional cache.img.ext4/boot.img
- TAR/ZIP file containing system.img.ext4 + more
Samsung Galaxy SII:
- factoryfs.img + optional cache.img/zImage
- system.img.ext4 + optional cache.img.ext4/boot.img
- TAR/ZIP file containing factoryfs.img/system.img.ext4 + more
- system.ext4.tar + optional boot.img (Nandroid backup)
Huawei:
- APP file from Huawei software update (e.g. UPDATE.APP)
----------------------------------------------------------------------
Press Enter to continue, or type 'x' to abort:
Available ROMs:
(1) system.img and boot.img
Enter selection number (default=1, cancel=0):
Found original_update/system.img
Found original_update/boot.img
The new working folder will be named WORKING_062712_171010
Change the name (y/n)? (default: n):
Creating working folder WORKING_062712_171010 ...
Copying boot.img ...
Copying system.img ...
Adding an update-script ...
"system.img" -> "../system.img.ext4"
Warning: No cache.img.ext4 found. You can unpack this file separately
by running the plugin script in the kitchen's Advanced menu options.
If your device doesn't use a CSC, then just ignore this message.
Analyzing system.img.ext4 ...
Compiling simg2img ...
simg2img successfully compiled
Converting system.img.ext4 into a format for unpacking ...
computed crc32 of 0xb9d9b0e7, expected 0x00000000
Mounting ext4_system.img to loopback device and then extracting files ...
..............
..........
...
N.B
Code:
Warning: No cache.img.ext4 found. You can unpack this file separately
by running the plugin script in the kitchen's Advanced menu options.
If your device doesn't use a CSC, then just ignore this message.
into my original_update have:
Code:
[email protected]:~/Scrivania/ROM/original_update$ ls
boot.img cache.img hidden.img modem.bin recovery.img system.img
Can you help me please? Thank u
Click to expand...
Click to collapse
Use "24" option on Advanced options then "Extract_SGS2_CSC_from_cache.img", i think cache.img must be the root working folder, it will convert it to ext, then follow the displayed steps.
wanam said:
Use "24" option on Advanced options then "Extract_SGS2_CSC_from_cache.img", i think cache.img must be the root working folder, it will convert it to ext, then follow the displayed steps.
Click to expand...
Click to collapse
Code:
PLUGIN SCRIPTS
--------------------------------------
(1) Extract_SGS_CSC_from_cache.rfs
(2) Decompile_and_Compile_Deodexed_File
(3) Install_SGS2_CWM_Manager
(4) Batch_Deodex
(5) Sample
(6) Extract_SGS2_Kernel_Initramfs
(7) ReadMe
(8) Extract_SGS2_CSC_from_cache.img
--------------------------------------
0 - Exit r - Refresh list
Enter an option: 8
Samsung Galaxy S2 CSC Extractor
-------------------------------
This script will extract the CSC (Customer Software Customization)
from the cache.img of a stock Samsung Galaxy S2 firmware. The CSC
comes in a file called 'sec_csc.zip' which contains location and
carrier-specific configurations and software.
Proceed (y/n)? (default: y):
Creating folder /home/gianni/Scrivania/ROM/csc_062712_205036 ...
---> Place stock cache.img or cache.img.ext4 into the folder mentioned above <--
Press Enter to continue
Compiling simg2img ...
simg2img successfully compiled
Unpacking cache.img into a format for unpacking ...
computed crc32 of 0x20453d0a, expected 0x00000000
Mounting ext4_cache.img to loopback device and then extracting files ...
[sudo] password for gianni:
Finished! Your file is at csc_062712_205036/sec_csc.zip.
You can unzip this file and copy the contents of the 'system'
folder to your ROM's system folder.
I have a package "sec_csc.zip"
I have extracted sec_csc.zip and i have into *.zip
META-INF
system
i need copy all files into system to /WORKING_FOLDER/system? and META-INF?
now??
Solved thank u
Another quesyion..
How to remove default app during installation of custom rom?
MyTaxy.apk, videohub, rhs hotel .... etc...?
Sent from my GT-I9300 using xda app-developers app
Plugin Installation:
Open the Plugin Manager
Choose Install a Plugin
Choose the plugin you want to install
Choose Run a Plugin
Choose the Plugin you want to run
Enjoy!
NOTE: The usage instructions in each plugin description below assume you have already installed it. When the instructions end, that's when you run the plugin from the plugin manager.
SuperR's Kitchen Plugin Descriptions
SuperR Maintained Plugins:
add_placeholder
Only for system-as-root devices
Adds placeholder files to all empty directories in your project
add_remove_files
Add all apk files from a directory
Choose apk to import
Choose directory structure to import
Delete files from your ROM based on directory structure
NOTE: To use "Choose directory structure to import" and "Delete files from your ROM based on directory structure", your directory must be set up as the following example:
Code:
your_directory_name/system/anything_you_want
your_directory_name/vendor/anything_you_want
your_directory_name/cache/anything_you_want
your_directory_name/hidden/anything_you_want
your_directory_name/boot.img
The above is only an example. You can add anything you want as long as there is a "system" directory inside another directory. When choosing the directory, choose your_directory_name instead of system or it won't work. Think of the directory structure exactly like the kitchen project directory. When you import directory structure, your directory will be copied into your project directory and files will be overwritten if they already exist. When you remove a directory structure, you will choose your_directory_name again and the plugin will remove the same files it finds from your project directory.
amlogic_unpack
Unpack Amlogic firmware img
apktools
Choose an apk from your current rom directory.
Decompile the apk.
Build apk.
Sign apk with 3 options (use signapk.jar, copy original META-INF to new apk, or copy new classes.dex and resources.arsc to original apk).
Move apk back to where it came from.
Patch smali using .ptch files
Delete META-INF from all apk files
Delete SEC-INF from all apk files
Separate lib directory from all apk files
Zipalign apk files
aroma_install
Install Aroma in your existing ROM.
Create aroma-config using a menu.
Choose apk files to add to the option menu.
Usage:
Extract your ROM normally using ONLY set_metadata or set_perm.
autorom_config
Creates an AutoROM config file to automate the extraction process and many other tasks.
Currently supports perm type, vendor.img, rom name, custom signature, deodexing, root, su.d, and Busybox
buildprop_add
Adds lines from a file to build.prop.
concatimg
Combines partition_*.img files into a single img file
custom_zip
Create a flashable zip of one or more image files as long as you know the partition name where it should be flashed.
Create a flashable patch zip from directories that have matching fs_config and file_contexts3 files
Convert updater-script to update-binary script for use in the mods_install plugin
Usage:
Copy the partition images and/or directories you want in the zip into a new directory in your project.
In the kitchen main menu, choose Plugin Manager > Run a plugin > custom_zip
Choose the new directory from the list.
For img files in by-name devices, type the partition name from your device where it should be flashed (ex. aboot)
For img files in mmcblk devices, choose your block from the list (add it to the device superr_mmc file if needed first).
decrypt_htc
Decrypt ruu.exe and ruu.zip files stored in your current project directory.
Extract system.img & boot.img to the current project directory for extraction.
Usage:
Copy ruu.exe or ruu.zip to current project directory (ruu.zip must be named exactly ruu.zip).
gapps
Downloads and includes Open Gapps in your ROM.
Choice of aroma, super, stock, full, mini, micro, nano, or pico
Detects Android version and architecture from ROM to download the latest available version for your device.
If there is no ROM, it will allow you to choose Android version and architecture.
Remove gapps if it already exists.
gen_set_metadata
Generates set_metadata lines for every file in project directories that have matching fs_config and file_contexts3 files.
img_tools
Allows rebuilding ext4 img files that have been extracted by the kitchen even if there is not a complete ROM in the project.
Convert sparse img to raw img
Convert raw img to sparse img
Build super.img
Resize img
super.img Build Requirements:
All included img files must be built as sparse.
img file names must be either partition.img or partition_new.img.
super.img size must be in 00_project_files/srk.conf.
Example:
supersize=9437184000
The numeric value in the example above is the raw super.img file size in bytes.
The kitchen adds the super.img size when unpacking a super.img. If the kitchen did not unpack the super.img, you can enter the size in srk.conf manually.
Optional values metadata-size and metadata-slots can also be added to srk.conf. Defaults are listed below:
metadata-size=65536
metadata-slots=2
*This plugin will only work in v3.2.1.0 or higher*
lg_tools
Unpack LG kdz files
Removes rctd, ccmd, and triton from LG boot.img.
mods_install
Add any flashable zip to your ROM that uses an update-binary script instead of a updater-script
Remove mods
Shows the kitchen added mods you currently have installed
ozip_decrypt
Decrypt firmware.ozip files
payload_dump
Unpack payload.bin firmware
rockchip_unpack
Unpack Rockchip firmware img files
samsung_tools
Asks one-by-one if you want to add ro.config.tima=0, ro.config.knox=0, ro.securestorage.knox=false, ro.securestorage.support=false, ro.security.mdpp.ux=Disabled, and wlan.wfd.hdcp=disabled to ramdisk default.prop
Create tar.md5 from all img, mbn, ext4, and bin files in your ROM directory.
Create tar.md5 from all the above except system.img, system.img.ext4, boot.img, and recovery.img
Decode OMC/CSC
Deodex patch for Android 8.1+
Pack *_new.img files to lz4
sepolicy_injector
Converts sepolicy denials into allow rules, and optionally patches seplicy with the new rules.
Paste a denial
Read denials from 00_project_files/logcat.log
unsign_mtk_img
Removes MTK signature from img files
updateapp
Extract firmware.zip that contains UPDATE.APP
Extract img files from UPDATE.APP
Usage:
Place a firmware.zip or UPDATE.APP in your rom directory.
xiaomi_patch
Patches several things in Xiaomi firmware.
Usage:
Extract your firmware with the kitchen, then run the plugin.
xperia_unpack
Unpack Xperia firmware
Choose full firmware zip, an ftf file, or a sin file.
When choosing a sin file, all sin files in the project directory will be unpacked.
Respects the partition_extract_list variable from kitchen/tools/srk.conf
User Contributed Plugins:
None
Custom Plugins
The donate version has plugin support. This means you can integrate your own script into the kitchen. Each plugin must have its own directory inside the kitchen plugin directory, and it must be named the same as the plugin script.
Examples:
/kitchen/tools/plugins/example_bash/example_bash.sh (Linux, Mac)
/kitchen/tools/plugins/example_batch/example_batch.bat (Windows)
You can check the example plugins in the kitchen for more details and use them as templates for your own plugin.
There are 3 variables set in the example plugin to take note of:
bd = /path/to/kitchen
rd = /path/to/kitchen/superr_projectname
plugdir = /path/to/kitchen/tools/plugins/pluginname
NOTE: If you would like to contribute a plugin, please PM a link to the plugin for review.
This post contains the last working versions of all plugins that have lost native Windows support.
If you are running the kitchen in WSL, WSL2, Linux, or Mac you should use the kitchen plugin manager to get the latest versions of these plugins.