Related
Hi all,
In this thread, I will try to share the knowledge I have on deodexing, making custom ROMs, modifying initramfs, building kernel and much more.
Please check the below posts for each of these tutorials.
Hope this opens doors to many new ROM and Kernel developers.
NOTE: THESE TUTORIALS ARE WRITTEN FOR GT-I9100. WILL NOT WORK ON OTHER DEVICES. I DON'T TAKE ANY RESPONSIBILITY IF YOU MESS UP AND BRICK YOUR DEVICE OR ANYTHING ELSE. USE AT YOUR OWN RISK.
Deodexing Stock Rom
For GINGERBREAD ROMS:
What you need to have:
xUltimate v2.3.3 - you can download it HERE (Thanks and Credits to Xeudoxus for this awesome app)
Rooted kernel with busybox
JDK installed on your Windows system
If adb is not available in your windows PC, in xUltimate folder open "jar" folder. You'll find adb there.
Extract stock app & framework folders and Deodex:
Connect your device to computer.
Start xUltimate (double-click on Main.exe)
Select option 1. (Pull /system/app)
Once option is done, select option 2. (Pull /system/framework)
In the same folder, now you'll see two new folders (origi_app, origi_frame)
Select option 3 in Main menu (Deodex /system/app)
Once its done, select option 4 in Main menu (Deodex /system/framework)
DONE!!
NOTE: If any apk/odex gives issues while deodexing, remove that corresponding apk and odex from origi_app folder and deodex again. (Mostly the apps which can be downloaded from play store might give errors.. ex: Maps, Voice search etc.)
Now you'll see two new folders done_app and done_frame.
Push deodexed app and framework to device:
Connect your device to PC in USB debugging mode.
Copy done_app and done_frame folders to root of sdcard (/sdcard).
Open Windows command prompt and type the below commands.
Code:
[LIST]
[*]adb shell
[*]su
[*]stop
[*]mount -o remount,rw /dev/block/mmcblk0p9 /system
[*]rm /system/app/*.odex
[*]rm /system/framework/*.odex
[*]busybox cp /sdcard/done_app/* /system/app/
[*]busybox cp /sdcard/done_frame/* /system/framework/
[*]chmod 644 /system/app/*
[*]chmod 644 /system/framework/*
[*]mount -o remount,ro /dev/block/mmcblk0p9 /system
[*]sync
[*]reboot recovery
[/LIST]
In Recovery, Wipe Cache and Wipe Data/Factory reset.
Reboot.
Now you've deodexed app and framework.
For ICS ROMS:
For ICS Roms, the process is quite easy. (Thanks and Credits to jaydvn.)
Download the attached zip file.
Extract it on your windows PC.
Copy your /system/app to _app folder
Copy your /system/framework to _framework folder.
Run AutoDEOToolMain.bat
Follow the instructions.
deodexed jars and apks will be found in deodexed_APK and deodexed_JAR.
Push deodexed app and framework to device:
Connect your device to PC in USB debugging mode.
Copy deodexed_APK and deodexed_JAR folders to root of sdcard (/sdcard).
Open Windows command prompt and type the below commands.
Code:
[LIST]
[*]adb shell
[*]su
[*]stop
[*]mount -o remount,rw /dev/block/mmcblk0p9 /system
[*]rm /system/app/*.odex
[*]rm /system/framework/*.odex
[*]busybox cp /sdcard/deodexed_APK/* /system/app/
[*]busybox cp /sdcard/deodexed_JAR/* /system/framework/
[*]chmod 644 /system/app/*
[*]chmod 644 /system/framework/*
[*]mount -o remount,ro /dev/block/mmcblk0p9 /system
[*]sync
[*]reboot recovery
[/LIST]
In Recovery, Wipe Cache and Wipe Data/Factory reset.
Reboot.
Done.
Enjoy.
Building kernel
Okay. Let's learn how to build kernel for GT-I9100. There are many ways to build. I am just presenting here the way I build and make kernel.
NOTE 1: Follow the instructions exactly.
NOTE 2: Kernel is opensource. If you make any changes to it, you're expected to share your source. (Usually people share it over github )
NOTE 3: FLASHING KERNEL IS RISKY AND DANGEROUS. BE CAREFUL. BUILD AND FLASH ON YOUR OWN RISK.
What you need to have:
Ubuntu 10.04 and above (I use 10.04 )
ARM tool chain (Download HERE. Click on IA32 GNU/Linux TAR under Advanced Packages)
Samsung's opensource kernel for GT-I9100 (Download HERE. Go to Mobile->Mobile Phone-> Select I9100 (update 3 for Gingerbread and update 4 for ICS) and download the zip)
Setting up toolchain:
Extract the tar you downloaded(Suggestion: Extract to one folder where you can have everything. In my case /home/superatmos/build_kernel).
After extracting, you'll see a folder named arm-2010q1. Inside there will be many folders (ex. bin, lib and so on.)
Folder structure will be: /home/<your_name>/build_kernel/arm-2010q1
Setting up kernel:
Extract the zip you've downloaded from samsung's opensource.
You'll find two zips.
Extract GT-I9100_Kernel.tar.gz to /home/<your_name>/build_kernel/
Folder structure: /home/<your_name>/build_kernel/GT-I9100_Kernel
Setting up initramfs:
Samsung's zImage is divided into two parts: Opensource kernel (which you downloaded from samsung's website) and initramfs (which is root file system to boot up the device).
You can extract initramfs from your zImage using the below mentioned links (Credits and Thanks to Chenglu) Original Thread: HERE
To extract initramfs from Gingerbread zImage: HERE
To extract initramfs from ICS zImage: HERE
Folder structure: /home/<your_name>/build_kernel/initramfs
Now the entire setup is ready. Let's start modifying kernel configuration.
Setting up kernel config:
For Gingerbread:
Go to /home/<your_name>/build_kernel/GT-I9100_Kernel/arch/arm/configs folder.
Copy c1_rev02_defconfig file and paste it in kernel root folder (/home/<your_name>/build_kernel/GT-I9100_Kernel/).
Rename c1_rev02_defconfig to .config in kernel root folder.
Now open Makefile which is in your kernel root folder(/home/<your_name>/build_kernel/GT-I9100_Kernel/).
Modify the below lines (I guess line 195 and 196).
For ICS:
Go to /home/<your_name>/build_kernel/GT-I9100_Kernel/arch/arm/configs folder.
Copy u1_defconfig file and paste it in kernel root folder (/home/<your_name>/build_kernel/GT-I9100_Kernel/).
Rename u1_defconfig to .config in kernel root folder.
Now open Makefile which is in your kernel root folder(/home/<your_name>/build_kernel/GT-I9100_Kernel/).
Modify the below lines (I guess line 195 and 196).
Code:
ARCH ?= arm
CROSS_COMPILE ?= /home/<your_name>/build_kernel/arm-2010q1/bin/arm-none-linux-gnueabi-
Save and close.
Modifying kernel configuration:
Now open .config file(which you renamed). If its not seen, it might be hidden. Go to View->Show hidden files and there you go.
Do the below things:
Adding local version:
Change CONFIG_LOCALVERSION=" " to anything you like. I add this way:
CONFIG_LOCALVERSION="-I9100-superatmos"
Adding initramfs path:
You need to let kernel know the path from which it needs to take initramfs.
Change CONFIG_INITRAMFS_SOURCE=" " to ../initramfs (In this tutorial it's the path. If you had copied anywhere else, give the path properly).
Enough for now. Once you get experience, you can modify many configurations as per your liking and save. This configuration can be changed by GUI too with the command make menuconfig.
The Important part: Building the kernel:
For Gingerbread:
Open terminal.
Go to path /home/<your_name>/build_kernel/GT-I9100_Kernel/
Type make.
For ICS:
Open terminal.
Go to path /home/<your_name>/build_kernel/GT-I9100_Kernel/
Type export USE_SEC_FIPS_MODE=true
Type make.
THAT'S ALL. YOUR zImage is ready and is available in /home/<your_name>/build_kernel/GT-I9100_Kernel/arch/arm/boot/zImage.
Install the zImage on the device:
Go to the path where zImage is present and type the below line in command line.
Code:
tar cvf I9100_kernel.tar zImage
Flash the tar using odin.
DONE. CONGRATULATIONS. NOW YOU'VE YOUR OWN KERNEL.
Give me your feedback so that I can improve this tutorial. And post here about how your build went. All the best.
Making custom ROM
Let's move on to make a custom ROM.
Inputs/Feedback/Suggestions are more than welcome. Lets improve this tutorial together for the betterment of the android community.
Steps involved in making a custom ROM:
Getting the system dump from the device.
Deodexing app and framework folders.
Creating various mods by modifying framework and system files.
Modifying build.prop and adding tweaks.
Making META-INF folder and writing an updater-script (edify scripting).
Signing the ROM and making a flashable zip.
Folder Structure:
Before going forward, let's follow the below structure folder to make the tutorial more understandable.
Let our ROM name be CustomROM. The folder structure will be C:\Users\<your name>\CustomROM.
Let's move step by step. Are you ready??
Getting the system dump from the device
Click to expand...
Click to collapse
Make sure USB debugging is ON and connect your device to the PC.
Open command prompt on your windows PC and go to CustomROM folder path.
Type adb devices. You should be able to see the device detected. (If not check environmental variables whether adb is in system path or not. If not present, add the adb path.)
Type the below command to get the dump of system folder.
Code:
adb pull /system system/
Now inside the folder CustomROM, you should be able to see system folder with many folders like app, etc, framework etc inside.
Done with first step.
Deodexing app and framework folders
Click to expand...
Click to collapse
Look HERE how to deodex app and framework folders. Copy the app and framework folders to xUltimate folder, rename them to origi_app and origi_frame and follow the given link to deodex.
NOTE: After deodexing, merge origi_app folder with app folder under C:\Users\<your name>\CustomROM\system\app and origi_frame with framework folder under C:\Users\<your name>\CustomROM\system\framework.
Creating various mods by modifying framework and system files
Click to expand...
Click to collapse
Okay. This the section where your hardwork, innovation and talent comes in. You can use the mods available already, create your own mods, port various mods from other devices and so on.
Below is a list of various mods which can be ported on to GT-I9100. All the credits go these respective thread owners. Thanks to them.
Lidroid 14 toggle mod
Extended power menu with/without header
CRT Off Animation & SIP Over LTE/HSPA
Swipe to remove notifications
NOTE: Let me know more mods with links so that I can add here.
Modifying build.prop and adding tweaks
Click to expand...
Click to collapse
Okay. This is one of those files where you name your ROM(to be visible in settings. ) and add many tweaks.
To name your ROM (to be visible in settings), change the below code.
Code:
ro.build.display.id=CustomROM v1.0
Check the below links for many other tweaks. All credits go to respective thread owners. Thanks to them.
build.prop tweaks by TheFrankenstain
build.prop tweaks by dhlalit11
Making META-INF folder and writing an updater-script (edify scripting)
Click to expand...
Click to collapse
Once you're done with all the modifications, mods and additions, its time to create META-INF folder and make the updater script. Once the user flashes the ROM zip, this is the script that runs and does everything written inside the script. PLEASE BE CAREFUL WITH THIS. TAKE REFERENCE FROM OTHER (SAME DEVICE) ROMS' UPDATER-SCRIPT. (In this case, take reference from other GT-I9100 roms.)
Check the below links for tutorial and how-to on writing edify script and making updater script. All credits go to respective owners of the threads. Thanks to them.
Edify Scripting, Making Flashable ZIPs, ZIP Signing & Key Creation
Edify Scripting Notes
How to Write an Updater-Script with Edify Code
Edify Installation Script Syntax's
NOTE: system folders path, boot/kernel partition path, modem partition path and so on are COMPLETELY DIFFERENT for DIFFERENT DEVICES. Check the partitions for your device properly, carefully and then work on updater-script. TAKE HELP OR REFERENCE FROM OTHER ROM DEVELOPERS FOR YOUR DEVICE.
Lets move on to last step. Making a signing and making a flashable zip.
Signing the ROM and making a flashable zip
Click to expand...
Click to collapse
Make sure, now you should be able to find two folders (META-INF and system) inside C:\Users\<your name>\CustomROM.
Check in THIS thread for test signing your ROM. It WORKS with GT-I9100.
or Check THIS thread to create your own signing key and certificate.
Now you're done with making a custom ROM. Hope to see more custom ROMs from many users.
Give me your feedback so that I can improve this tutorial. And post here about how your custom ROM making went. All the best.
last one
i don't see any tutorials just links to a diff thread and a rom that won't work on i9100
buster041284 said:
i don't see any tutorials just links to a diff thread and a rom that won't work on i9100
Click to expand...
Click to collapse
You're quite fast Updated Deodexing and Building kernel section..
Great thread Superatmos. I'll definately have a go at this.
Quick question ? Am i right in assuming that although your tutorial says to connect your device this line from xUltimate seperceeds that ?
"Alright xUltimate has been updated to v2 What this means is that you do not need your phone connect to your computer to deodex. So you can just manually place the .odex files in (\origi_frame\) and (\origi_app\) and it will deodex. You can also transfer the .odex files from your phone like the last version."
where do I get the zImage to extract the initramfs from? I can't seem to find the zImage on my phone or in the source anywhere.
Great
Very useful.. Added to my favorite.
Thank's man, i'll read that
puccini said:
Great thread Superatmos. I'll definately have a go at this.
Quick question ? Am i right in assuming that although your tutorial says to connect your device this line from xUltimate seperceeds that ?
"Alright xUltimate has been updated to v2 What this means is that you do not need your phone connect to your computer to deodex. So you can just manually place the .odex files in (\origi_frame\) and (\origi_app\) and it will deodex. You can also transfer the .odex files from your phone like the last version."
Click to expand...
Click to collapse
Connect your device to the PC and double click Main.exe inside xUltimate folder. Follow the instructions you see from then. Its quite self explanatory.
If you already have origi_app and origi_frame folders, then just double click on Main Skip.bat.
dmp450 said:
where do I get the zImage to extract the initramfs from? I can't seem to find the zImage on my phone or in the source anywhere.
Click to expand...
Click to collapse
Use ktool (available on market.. compatible with I9100) and click on Dump current kernel. You'll find it on sdcard.
One more way is when you download firmware from sammobile.com, just extract the file and you'll find zImage inside it.
Nice thread,
I m waiting from long time.
Thanks for your work.
Sent from my GT-I9100 using XDA
Making custom ROM section updated
Hi all,
Please find updated custom rom section HERE.
Feedback and suggestions welcome.
Thanks for the kernel part, will come in handy
Enviado desde mi GT-I9100 usando Tapatalk 2
Good tutorial, thanks.
How do you guys sign the rom if you are on Linux (ubuntu for me)
hi superatmos
thanks for this handy thread...may i ask your for a help here?why in my every deodexing always gives error result?
I attach the screenshots.
Many thanks in advance
tks mate will try to pack my own kernel following this method
Sent from my GT-I9100 using Tapatalk 2
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
Hey Ace Users,
I am going to provide you all the guide to create your own CWM Flashable zip file.
The Best Part of this guide is that you wont need your computer to create the CWM Flashable zip file as this guide will teach you all how to create the CWM Flashable Zip file with the help of the Root Explorer App.
The things you will need for this guide are:-
1.Root Explorer App.
2.Your Ace.
3.A little patience.
So without much ado,Lets start the guide.
STEPS:-
1.Download and install the Root Explorer App.
2.Open the Root Explorer App and Navigate to the Root of your SD Card.
3.Create a Folder and name it whatever you like or whatever name you want to give to your Zip File(I will be reffering to the folder as "Main Folder" throughout this guide)
4.In the Main Folder,you will need to have Two Sub-Folders which are as "META-INF" And "system".
5.The META-INF Folder consists of various files and they should be untouched(The only file in the META-INF folder which we are going to edit is the updater-script).
6.The system folder which you put in the Main Folder contains the apps or various other mods which you want to apply to your ace.
Steps on How to Edit the updater-script:-
1.Go to the META-INF Sub-Folder in the Main Folder.
2.open the com folder which you will find in the META-INF Sub-Folder.
3.Then you will see google folder as soon as you enter "com" folder,enter the google folder,now you will see "android" folder,open it.
4.In the android folder,you wll see two files named as update-binary and updater-script.
5.Open the updater-script file by selecting it.
6.You will see various options.
7.Select the Text Editor option and then the updater-script will open in the text editor.
8.Now we need to type some code so as to have the following functions.
Editing the updater-script:-
So once the updater-script is opened in the text editor,you will need to type some code so as to have the following functions.
CODE:-
Case 1:-
To Display the information of the particular Mod when you select to flash it in CWM Recovery(It is the display you see when you flash a particular Flashable zip file. For Example:- if you are flashing beats mod then when you select to flash the zip file and when the flashing starts you see some infomation like "Beats For Ace" and when the flashing is over you can see that the display shows flashing is done and it tells to reboot phone and stuff)
CODE:-
ui_print("The Text you want to display");
For Example if you want to display "beats Mod for Ace" then you must enter the code as ui_print("Beats Mod for Ace");
NOTE:-
semi-colon and the double quotes in the above code are to be put as they are compulsary to execute the code.
Case 2:-
If You want the updater-script to mount the /system partition,then the code is:-
CODE:-
run_program("/sbin/busybox", "mount", "/system");
NOTE:-
semi-colon and double quotes are compulsary.
Case 3:-
Now we need to put the apps in the /system partition and for that we need to type the code as:-
CODE:-
package_extract_dir("system", "/system");
NOTE:-
semi-colon and double quotes are compulsary.
Case 4:-
After typing the mount /system code you will also need to unmount the /system partition and to unmount the /system partition the code is:-
CODE:-
run_program("/sbin/busybox", "unmount", "/system");
NOTE:-
Semi-colon and double quotes are compulsary.
Special Case:-
After each case we need to have a special code.
At the start of updating the updater-script,we mostly write the introduction of the mod/script etc. in the ui_print.
so before you add the name & info of the mod in the ui_print you need to write show_progress(0.500000, 0);
and after writing the name/info of the mod,you will be mostly writing the code to mount the system partition,so after writing the code to mount the system partition,you need to write show_progress(0.500000, 20)
Now once you are done writing the code to mount the system partition the next thing you will be doing is extracting the package from the system partition by writing the code for extracting the system partition contents,so after you are done writing the code for extracting the system partition contents,you need to write show_progress(0.500000, 40)
Now after this,you will be writing the code to unmount the system partition so after writing that code you need to write show_progress(0.500000, 60)
After finishing writing the code to unmount the system partition,
you will add some more lines in the ui_print as for example Done flashing mod,so after writing that lines in the ui_print you will need to write show_progress(0.500000, 80)
After that you will probably write some more lines in the ui_print to notify the user to reboot his/her phone so after you write that code you will need to write show_progress(1.000000, 0)
Basically the show_progress command indicates the progress of the installation of the mod.
Sample of the whole updater-script codes in short:-
ui_print("Battery Mod For SGA");
ui_print("|-----by XYZ-----|");
ui_print("10% starting installation");
show_progress(0.500000, 0);
ui_print("20% mounting /system");
run_program("/sbin/busybox", "mount", "/system");
show_progress(0.500000, 20);
ui_print("40% Extracting Files");
package_extract_dir("system", "/system");
show_progress(0.500000, 40);
ui_print("60% unmounting /system");
run_program("/sbin/busybox", "unmount", "/system");
show_progress(0.500000, 60);
ui_print("|---Mod Flashed Successfully---|");
show_progress(0.500000, 80);
show_progress(1.000000, 0);
ui_print("Please Reboot Your Phone");
If you don't understand the show_progress procedure then check this link:-
http://rootzwiki.com/topic/6761-show...me-flashables/
NOTE FOR CM7 USERS:-
IF THE ABOVE CODE FOR MOUNTING AND UNMOUNTING THE /SYSTEM PARTITION DOESNT WORK FOR YOU,THEN YOU CAN MANUALLY MOUNT /SYSTEM BEFORE FLASHING AND THEN MANUALLY UMMOUNT IT(IF YOU WANT TO) AFTER FLASHIMG.
NOTE:-
AFTER SAVING THE CHANGES DONE TO THE updater-script,A FILE WILL BE CREATED AS "updater-script.bak".DELETE "updater-script.bak" file.
Okay so we are almost done.
Now some information about the system Sub-folder in the Main Folder.
The system Sub-folder contains another Sub-folder(s) like:-
For example if you want to add an app's apk file then the system sub-folder will contain "app" sub-folder and that app folder contains the apk file(s) that you want to put in the system partition of the ROM.
If you want to Put Framework Mods then the system sub-folder will contain "framework" sub-folder and the "framework" sub-folder wil contain the framework Mod(mostly the Framework mods are in Framework-res.apk file.)
If you want to put libs then the subfolder in the system subfolder will be "lib" and it will contain the libs.
If you want to put bin files then the subfolder in the system subfolder will be "bin" and it will contain the bin files.
If you want to add scripts then the subfolder in the system subfolder will be "etc" subfolder and in that "etc" subfolder there will be another subfolder as "init.d" and in the init.d subfolder there you can put the scripts.
After doing all that(i.e editing the updater-script and putting the files in the subfolders in the system subfolder) go back to the directory where you created the Main Folder and in Root explorer long press the Main Folder and you will get various options.
scroll down and select "zip this folder" and after the folder is zipped you can go to /SD Card/speed software/zip and find the flashable zip there.
Here ends my guide
Download Links:-
Sample file dl link
Screenshots of guide
Good..!!Helpful for lot of people:thumbup:
side_effect said:
Good..!!Helpful for lot of people:thumbup:
Click to expand...
Click to collapse
Helpful. Thanks
Sent from my GT-P6200 using Tapatalk 2
great guide :good::good::good:
but AFAIK guides are supposed to b in general...EET will move this soon
-RDR- said:
great guide :good::good::good:
but AFAIK guides are supposed to b in general...EET will move this soon
Click to expand...
Click to collapse
No they are meant to be in Development section.
I have seen many guides in development section of many phones.
Nope. Guides should be in General Section. Guides are not developing project.
This was sent from my impulses, not my Galaxy Ace.
Moving to General
Well we will have to remember alot of things before making a zip..
It will not be so easy
Really great guide....................
Sent from my GT-S6102 using Tapatalk 2
thanks for sharing
helpful
for
newbies
.......
i will try this when i get time.
thanks for this man!!
Sent from my GT-S5830 using xda premium
Thx!!!!!
Thx a lot man !!
Depuis mon Galaxy Ace GT-S5830-SGSII v9 modifié !!!
@Ace King 34
Hahaha...i think that you have forgot of put some things in this guide, and then about the command show_progress i think that you not have understood really how works.
Sent with my Evil GT-S5570 from Hell
EVIL THOR said:
@Ace King 34
Hahaha...i think that you have forgot of put some things in this guide, and then about the command show_progress i think that you not have understood really how works.
Sent with my Evil GT-S5570 from Hell
Click to expand...
Click to collapse
You Surely don't know how to read.
Read the Special Case in the OP Carefully.
It has got the show_progress.
and btw read the OP carefully next time before posting such replies.
Ace King 34 said:
You Surely don't know how to read.
Read the Special Case in the OP Carefully.
It has got the show_progress.
and btw read the OP carefully next time before posting such replies.
Click to expand...
Click to collapse
Surely you don't know read because i know read better than you Ace Chick, at least you know what do the value 40 in the command show_progress? your guide has only some commands copied from others updater-scripts but you don't know not even what they do...pfff...
Sent with my Evil GT-S5570 from Hell
@ EVIL THOR Thanks for Reporting me the issue mate.
I have changed the OP a bit.
Have a Look.
Ace King 34 said:
@ EVIL THOR Thanks for Reporting me the issue mate.
I have changed the OP a bit.
Have a Look.
Click to expand...
Click to collapse
Yes ok but the last show_progress should be 100 not 0 if not the bar of progress show only 80% and then go back to 0%.
Sent with my Evil GT-S5570 from Hell
EVIL THOR said:
Yes ok but the last show_progress should be 100 not 0 if not the bar of progress show only 80% and then go back to 0%.
Sent with my Evil GT-S5570 from Hell
Click to expand...
Click to collapse
mate I have changed the 0.500000 to 1.00000 and then I have written 0 so it changes the progress from 0.500000 to 1.000000 and I have tested it mate
it worked flawlessly.
[Disclamer: Use the following at your own risk, I take no responsibility for the unrecoverable loss of any data as a direct consequence of using anything attached]
The following patcher(s) will modify the nand ramdisk for various functions, primarily enabling NativeSD support:--------------------------------------------------------------------
#1 NativeSD SD ramdisk to NativeSD nand ramdisk patch
#2 NAND (Non NativeSD) to NativeSD patch
#3 Boot.img (/also clk) patcher
#4 other devices ???
#5 FAQ
---------------------------------------------------------------------
NativeSD SD ramdisk to NativeSD NAND ramdisk
Things resolved by using nand ramdisk over sd ramdisk
Bluetooth issues
Changing rom name to whatever you want prior to install i.e for testing purposes (just need to change rom_name in install.sh and the one in the ramdisk will mirror it)
...
...
Instructions.
Removed the old zips, have attached just one, should run on linux, on device and during installation, needs a install.sh file with at least ROM_NAME=rom_name in it, and a copy of the nand ramdisk to be added into NativeSD folder or copied to /tmp (i.e during ROM _installation ) and to execute nativesd.sh (a copy of which is currently attached as well as being in the zip). Should work with nilfs2 and ext4 and should allow for easy adjustments and modifications to be made to the mount commands carried out in init.rc and/or mountfs.sh
Add a copy of nativesd.sh.txt saved as nativesd.sh to the downloaded and unzipped NativeSD folder and add to rom zip.
During ROM installation the NativeSD folder needs to be emptied to /tmp along with a nand ramdisk and /tmp/nativesd.sh needs to be run.
package_extract_dir("NativeSD", "/tmp");
set_perm(0, 0, 0777, "/tmp/nativesd.sh");
run_program("/tmp/nativesd.sh");and either send nand ramdisk to /tmp/ or add a copy to the NativeSD folder before installation.
The set up at the moment will leave the default NativeSD in tact and add two others, just rename them (or edit nativesd.sh to do so).
If using nilfs2 again two addition ramdisks will be added, the two created ones which will boot to nilfs2 and the original which won't boot as it's set to ext4, you may also need to edit install.sh (or mount_NativeSD.sh) so that it reads "mount auto" or "mount nilfs2" rather than "mount ext4".
Legacy Instructions:
Code:
NANDtoNativeSD.zip (will add another version)
[INDENT]This is a CWM(/recovery) zip, instructions are similar to Combi:
need to change install.sh to have the right rom_name at the top, and add the nand ramdisk to the NativeSD folder and install via recovery[/INDENT]
Combi
[INDENT]The zips marked ext4 and nilfs2 should make both sc and v versions and should work during installation and from running build (although that may need one line change). They should create initrd-nilfs-sc.gz and initrd-nilfs-v.gz or initrd-ext4-sc.gz and initrd-ext4-v.gz accordingly and thus can't be booted from until you rename them to initrd.gz.
[B]During ROM installation:[/B]
[INDENT]Copy the nand ramdisk (it should be ~200kb) into the NativeSD folder and copy NativeSD into the ROM zip
Edit the updater script by adding:
[B]package_extract_dir("NativeSD", "/tmp");
set_perm(0, 0, 0777, "/tmp/nativesd.sh");
run_program("/tmp/nativesd.sh");[/B][/INDENT]
before [B]package_extract_dir("system", "/system");[/B]
no other change needed so this should be universal
[B]During running ROM:[/B]
[INDENT]Copy NativeSD folder to sdcard, copy in nand ramdisk and create a text file called [B]install.sh[/B] with the words [B]ROM_NAME=writeROMname[/B] writing the rom name after =.
Open terminal cd into NativeSD folder and run script:
[B]su
chmod 777 nativesd.sh
./nativesd.sh[/B][/INDENT]
Let me know if there is a problem as I might need to change a few lines to get it to run on device - This is completely untested
(will also run on linux after a few minor changes i.e changing sbin to bin on first line and removing/changing the [B]cp initrd*.gz /boot*[/B] lines, will properly comment this in next version if/when the current ones need fixing
[/INDENT]
Modifying during Installation
[INDENT]1. Download the attached NativeSD.zip or NativeSD-sc.zip and have original NativeSD-ROM.zip to be modified
2. Unzip it and open nativesd.sh
3. Add the romname to the start of the script (the same romname that's in install.sh)
3. Add the NativeSD folder to a current NativeSD-ROM.zip
4. Edit the updater-script, by changing the following:
[B]ui_print("@ Installing System");
package_extract_dir("kernel/bootsd", "/boot");
package_extract_dir("kernel/kernel", "/boot");
package_extract_dir("kernel/bootsd", "/boot_dir");
package_extract_dir("kernel/kernel", "/boot_dir");
package_extract_dir("sdcard", "/sdcard");
package_extract_dir("system", "/system");[/B]
to
[B]ui_print("@ Installing System");
package_extract_dir("kernel/boot", "/boot");
package_extract_dir("kernel/kernel", "/boot");
package_extract_dir("kernel/kernel", "/boot_dir");
package_extract_dir("NativeSD", "/tmp");
set_perm(0, 0, 0777, "/tmp/nativesd.sh");
run_program("/tmp/nativesd.sh");
package_extract_dir("sdcard", "/sdcard");
package_extract_dir("system", "/system");[/B]
[I][SIZE="1"](this will vary slightly by rom)[/SIZE][/I]
5. Copy rom to sdcard and install via recovery[/INDENT]
Modifying during running NativeSD ROM
[INDENT]1. Download nativesd.sh.txt and nativeSDv1.1 attached
2. Obtain nand ramdisk from the NativeSD-ROM.zip (kernel/boot/initrd.gz for example)
3. Unzip NativeSDv1.1.zip
4. Rename nativesd.sh.txt to nativesd.sh and copy over the one in the NativeSD folder
5. Copy the nand ramdisk (initrd.gz) into the NativeSD folder
6. Copy NativeSD folder to device for example to /sdcard/Downloads/
7. Open terminal and run the following
[B]su
cd /sdcard/Downloads/NativeSD
ROM_NAME=AddRomNameHere
chmod 777 nativesd.sh
./nativesd.sh
exit
exit[/B]
This should modify the ramdisk and copy it to /sdcard/NativeSD and will leave the one in the romfolder as is, if it works great if not, replace the initrd.gz in /sdcard/NativeSD with the one in /sdcard/NativeSD/ROMNAME/
[/INDENT]
(If using nilfs2, you will also need to look in install.sh and change ext4 to auto)
Details
Confirmed working:
Booting to ext4
Booting to nilfs2 (using nilfs2 zips)
Untested:
Modifying from running build
Tested Working ROMs:
NexusHD2-ICS
PACman
MIUIJB
PA-HD2
sundawg
CM9ite 1.1 (QMA version won't work)
Versions
Releases with v will be based on marco.palumbi's method - adding mounts to init.rc
Releases with sc will be based on securecrt's method - using an additional script
Changelog -beta 1
nilfs2 and ext4 tested with same rom, nativesd.sh file removed from zip (as the other files with remain unchanged for the time being)
-------------------------------------
-nilfs-ext4-sc-v
Stripped down andcombined to the one zip
-------------------------------------
-ext4(4) and -nilfs2(4)
sc fixed
-------------------------------------
-ext4(3) and -nilfs2(3)
Bug fixes
-------------------------------------
-ext4(2) and -nilfs2(2)
Fix initrd.gz names with ext4 version,
tmp file copied into NativeSD (hopefully) for debugging purposes
------------------------------------
-ext4 and -nilfs2 versions
Seperate zips for the two file systems for now
Hopefully removed the need to have to manually change the rom_name by reading from install.sh (confirmed)
Completely untested
-------------------------------------
sc1.2
Should now be fixed and work with ext4 (and nilfs2 after removing some lines)
--------------------------------------
sc1.1
Tidy up and fixing issue reported here
--------------------------------------
v1.1
Tidy up
--------------------------------------
sc1 (NativeSD-sc1) :
Based on securecrt's code
EXT4 support
--------------------------------------
v1 (NativeSD.zip) :
Based on marco.palumbi's code
EXT4 and (untested) basic NILFS2 support
Credits: securecrt, Xylograph, marco.palumbi, ph03n!x, Kokotas,
Testers: Robbie P and jerrysue (for testing the alpha builds)
NAND (Non NativeSD) to NativeSD patch
Have attempted with BBCM7 (as I thought the updater script would be simple) but to no avail.
Also attempted with (the now pulled) SlimICS
Theoretically should just require: adding:
package_extract_file("kernel/install.sh", "/tmp/install.sh");
set_perm(0,0, 0777, "/tmp/install.sh");
run_program("/tmp/install.sh");
if file_getprop("/tmp/nfo.prop","NativeSD") == "true"
then
ui_print("@ Installing System");
package_extract_dir("kernel/bootsd", "/boot");
package_extract_dir("kernel/kernel", "/boot");
package_extract_dir("kernel/bootsd", "/boot_dir");
package_extract_dir("kernel/kernel", "/boot_dir");
package_extract_dir("NativeSD", "/tmp");
set_perm(0, 0, 0777, "/tmp/nativesd.sh");
run_program("/tmp/nativesd.sh");
package_extract_dir("sdcard", "/sdcard");
package_extract_dir("system", "/system");
to the start and adding the below to the end
endif;
delete("/tmp");
unmount("/ext4p");
unmount("/system");
unmount("/data");
modifying according to ROM, removing any yaffs/format references, and adding in a NativeSD folder (#1) and an install.sh
Boot.img (/also clk) patcher
Once NAND is done should be able to integrate mkbootimg scripts and allow flash boot and sboot
Other devices ???
Anyone willing to try let me know.
FAQ
Fixes Required:
NILFS2
NILFS2 support is currently attempted to be implemented by the following code:
Mount_Type=`mount | grep "nilfs2" | cut -d ' ' -f 5`
if [ "$Mount_Type" == "nilfs2" ]
then
sed -i 's/auto/nilfs2/1
/(NativeSD)/a \mkdir /nilfs\
mount nilfs2 /dev/block/mmcblk0p2 /nilfs' ns/init.rc
else
sed -i 's/auto/ext4/1' ns/init.rc (or ns/mountfs.sh with sc)
Have tried various combinations and added in other lines, to no avail.
Running mount | grep "nilfs2" | cut -d ' ' -f 3 on a running nilfs2 rom will return:
nilfs2
nilfs2
nilfs2
(there might be a fourth (can't recall), due to system, data and NativeSD being mounted as nilfs2)
Is there something I've overlooked? (Have tried with busybox mount | busybox grep | busybox cut)
Or can anyone see the mistake, it runs fine but $Mount_Type wont be reported as nilfs2.
I will post a workaround for nilfs2 but would rather have it integrated.
Edit not the workaround I was thinking of but if using nilfs2 changing == to != should make it work. doesn't seem to runon android
Current workaround is to remove the lines posted above leaving just:
sed -i 's/auto/nilfs2/1
/(NativeSD)/a \mkdir /nilfs\
mount nilfs2 /dev/block/mmcblk0p2 /nilfs' ns/init.rc (or ns/mountfs.sh if using sc)
Remove the need for changing ROM_NAME in nativesd.sh
I must be doing something wrong here.
Tried securecrt's zip on mokee and nilfs, reboot after htc screen.
Tred v zip on qsea v2 and ext4, reboot after htc screen.
Tried v zip on nexusHD2 ics and ext4 and it worked.
Tried v zip on pacman and ext4 and reboot.
It seems i am having trouble editing updater script when the rom has separate folders for initrd.gz and zImage. Each time the nand ramdisk appears in folders but is not edited.
Can you post your working edited updater script for pacman rom so that i can see where i have gone wrong.
Robbie P said:
I must be doing something wrong here.
Tried securecrt's zip on mokee and nilfs, reboot after htc screen.
Tred v zip on qsea v2 and ext4, reboot after htc screen.
Tried v zip on nexusHD2 ics and ext4 and it worked.
Tried v zip on pacman and ext4 and reboot.
It seems i am having trouble editing updater script when the rom has separate folders for initrd.gz and zImage. Each time the nand ramdisk appears in folders but is not edited.
Can you post your working edited updater script for pacman rom so that i can see where i have gone wrong.
Click to expand...
Click to collapse
PAC changes with full script attached:
ui_print("@ Installing System");
package_extract_dir("kernel/boot", "/boot");
package_extract_dir("kernel/kernel", "/boot");
package_extract_dir("kernel/kernel", "/boot_dir");
package_extract_dir("NativeSD", "/tmp");
set_perm(0, 0, 0777, "/tmp/nativesd.sh");
run_program("/tmp/nativesd.sh");
package_extract_dir("sdcard", "/sdcard");
package_extract_dir("system", "/system");
as far as I recall I used the attached v1 so should be no problems there, just make sure to change rom_name.
Have tried modifying nand updater-scripts (BBCM7 and SlimICS) but not working at the moment.
Will also post modified scripts to change the ramdisk from a running build (which datagr shouldn't have any problems incoporating into his app).
In terms of nilfs2, have you tried that with v1? Will have a look through sc to see if it's running correctly
In your instructions first post, the code is inserted after "package_extract_dir("system","/system");"
But the working script has it before this. That seems to be where it went wrong for me, because now pacman 1.1 on v with ext4 boots Edit; track forwards/backwards now working too.
The instructions worked for NexusHD2 ics 2.7 though, with the initrd.gz and zImage in the same folder.
Tried nativesdsc1.1 on nilfs with != on pac1.1 -stuck on magldr gogogo. Native sd folder initrd.gz 915.1Mb, NativeSD/PAC folder initrd.gz 168.3Mb
BTW i didn't see a nilfs2 file in sc1.1, does this matter.
BTW2 i have got a working rom on nilfs, but installed it via diff files on post3 fs superthread
Robbie P said:
Tried nativesdsc1.1 on nilfs with != on pac1.1 -stuck on magldr gogogo. Native sd folder initrd.gz 915.1Mb, NativeSD/PAC folder initrd.gz 168.3Mb
BTW i didn't see a nilfs2 file in sc1.1, does this matter.
BTW2 i have got a working rom on nilfs, but installed it via diff files on post3 fs superthread
Click to expand...
Click to collapse
No I incorporated nilfs2 into the nativesd script as it's only two lines. It seems != doesn't work on android, another workaround then that should work is to remove the lines
Mount_Type=`mount | grep "nilfs2" | cut -d ' ' -f 5`
if [ "$Mount_Type" == "nilfs2" ]
then
else
sed -i 's/auto/ext4/1' ns/init.rc altogether
And haven't tested sc at all yet, have been trying to made a text driven script for the on device one.
If your getting that with sc then the script isn't running at all, there'll be a mistake somewhere
Edit. fixed now (sc1 was more right than 1.1)
Just tried sc1.2 on pac1.1 nilfs changed ROM_NAME in install.sh and nativesd.sh and auto in install.sh-hangs on white htc screen
tried deleting everything in between # changing auto to ext4 or nilfs2 and # fixing permissions (and auto to nilfs2 in install.sh), and it hangs on black htc screen.
Edit; just found out i had wrong kernel in my zip.....
Did these two tests again-both times hangs on black htc screen. have attached DMESGs. (i had edited updater-script for these, did not mention this above).
tried pacman 1.1te with v1.1 on ext4 -working
will post initrd.gz on pacman thread
Robbie P said:
Just tried sc1.2 on pac1.1 nilfs changed ROM_NAME in install.sh and nativesd.sh and auto in install.sh-hangs on white htc screen
tried deleting everything in between # changing auto to ext4 or nilfs2 and # fixing permissions (and auto to nilfs2 in install.sh), and it hangs on black htc screen.
Edit; just found out i had wrong kernel in my zip.....
Did these two tests again-both times hangs on black htc screen. have attached DMESGs. (i had edited updater-script for these, did not mention this above).
Click to expand...
Click to collapse
Between # changing auto to ext4 or nilfs2 and # fixing permissions in v you need to leave
sed -i 's/auto/nilfs2/1
/(NativeSD)/a \mkdir /nilfs\
mount nilfs2 /dev/block/mmcblk0p2 /nilfs' ns/init.rc (or ns/mountfs.sh with sc).
Still hanging on htc screen m8.
Will give v1.1 a go.
Edit; Tried v1.1 on pac1.1te on nilfs using working ext4 build as it seemed like it might work-hangs on boot.
Edited as post above (already auto in install.sh), aroma says installed ok, but it took a few seconds. no initrd.gz created.
Just tried cmtight beta v1.0 with nativesd-ext4(2) and it boots with normal initrd.gz
it also boots with v initrd.gz
But with sc initrd.gz it just hangs on htc screen
tmp folder created in NativeSD/CMTight folder, but is empty (on pc)
There seems to be a problem with bt on this ROM, doesn't want to send sound, but skipping tracks works (on v). Saw a post in the nand thread about bt not working.
Will try again with sundawg's cm7 but no luck so far.
Robbie P said:
Just tried cmtight beta v1.0 with nativesd-ext4(2) and it boots with normal initrd.gz
it also boots with v initrd.gz
But with sc initrd.gz it just hangs on htc screen
tmp folder created in NativeSD/CMTight folder, but is empty (on pc)
There seems to be a problem with bt on this ROM, doesn't want to send sound, but skipping tracks works (on v). Saw a post in the nand thread about bt not working.
Will try again with sundawg's cm7 but no luck so far.
Click to expand...
Click to collapse
Thanks, again for testing these, have pulled and readded those zips, the tmp folder should copy now and have changed the sc side based on marco's suggestions (thought I'd already done that).
Should have my phone at the very least in a condition where I can install zips, so will get some testing done myself soon enough.
(Have posted ramdisk for Sundawg-CM7 in the other thead if you haven't seen it, will add another in a few mins)
tried latest on miuijb
tmp folder is full
normal initrd boots
v initrd reboots almost immediately
sc initrd reboots almost immediately
Do you need me to post anything as i am off to bed soon.
Robbie P said:
tried latest on miuijb
tmp folder is full
normal initrd boots
v initrd reboots almost immediately
sc initrd reboots almost immediately
Do you need me to post anything as i am off to bed soon.
Click to expand...
Click to collapse
The init.rc's if you wouldn't mind (off soon myself) and is there a rom_name.txt?
Edit: The init.rc's should be in NativeSD/tmp/ns2 (and ns3) if the folders copied correctly, I take it that there are no folders in tmp then.
Edit. Opened those ramdisks and they just have bin folders (and mountfs.sh with sc); did you remember to add the nand ramdisk to the NativeSD folder in the zip?
That explains why you can't find any init.rc files
couldn't find init.rc, found initrcmod, renamed it to .txt
Edit; doh! they are in these, sorry. Night
ooh, just tried to DL from market using cmtight and initrd-ext4-v.gz from before, and can't DL (error 101). It works ok using normal initrd.gz. No bootloop though, as gtbluesky got in nativesd thread.
Also perhaps miuijb was not best choice for last test, as got the same results as gtbluesky.
---------- Post added at 02:27 PM ---------- Previous post was at 02:12 PM ----------
HypoTurtle said:
did you remember to add the nand ramdisk to the NativeSD folder in the zip?
That explains why you can't find any init.rc files
Click to expand...
Click to collapse
Sorry m8, just checked and no ramdisk.
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.