How to mod a stock kernel Tutorial (with Windows)
by: broodplank1337
In this tutorial I will explain how to unsecure a kernel and how to add init.d / custom bootanimation support to a stock kernel, in this tutorial we will be using Cygwin as shell, with Dsixda's Android Kitchen.
Requirements:
- Cygwin with Packages and Dsixda's Android Kitchen
- JRE or JDK
- Winrar
- A stock Kernel
- Some common sense
Chapters:
1. Getting the kernel
2. Setting up Cygwin
3. Setting up the Kitchen
4. Modifying the Kernel
5. Testing results
Chapter 1. Getting the Kernel
Since the kernel that you are going to use is a stock kernel, it can be found within the latest stock firmware. for example for the i9001, I have this Odin flashable: "I9001XXKQE_I9001ATOKP3_I9001XXKPL_HOME.tar.md5". Open this file with Winrar and you will see the boot.img in there, just extract it and your currently done. It may also be a zImage!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Chapter 2. Setting up Cygwin
The Cygwin package you downloaded needs to be extracted, the default folder of a Cygwin installation is: "C:\cygwin". This is recommended in most cases. Once unpacked navigate to the "home" folder. In this home folder you need to create a folder that has the same username as your current windows username. Once you made that folder you have to extract the contents of "kitchen.rar" to that folder. So you will get a folder structure like this: C:\cygwin\home\username\kitchen
Chapter 3. Setting up Kitchen
Go to the original_update folder (located in: C:\cygwin\home\username\kitchen) and open dummyrom.zip with Winrar, now move your own boot.img inside the zip and choose "Store" as compression, Press ok to update the archive. If you have an zImage instead, please remove the boot.img from the archive first. Now browse to the system folder inside the archive and replace the build.prop with a build.prop from your phone. Also choose "Store" as compression and update the archive.
Starting the Kitchen:
1. Open Cygwin (X:\Cygwin\Cygwin.bat)
2. Once loaded, enter: "cd kitchen" > Enter
3. now type "sh menu" The kitchen menu will now start...
Setting up a working folder:
1. Press 1 > Enter
2. Press Enter and wait...
3. Choose (1) dummyrom.zip > Enter
4. Choose "y" > Enter > Enter a new name (I chose WORKING_KERNEL) > Enter
(now wait until the zip is extracted)
5. Choose 2 > Enter
6. Enter to return to main menu
Chapter 4. Modifying the Kernel
Unsecuring the kernel (to use properly with ADB)
1. Press 2 > Enter (to add root permissions)
2. Press "s" > Enter (now wait until the process is done)
3. Press Enter to return to main menu
Adding init.d support (for using startup scripts in /system/etc/init.d)
1. Press 0 > Enter
2. Press 17 > Enter (to add init.d support)
3. Enter "y" > Enter (now wait until the process is done)
4. Press Enter to return to main menu
Adding custom bootanimation support
Since the bootanimation support is already inside the dummyrom.zip file, you don't need to add it again.
Chapter 5. Testing the results
Now you will find a working boot.img / zImage under: C:\cygwin\home\username\kitchen\WORKING_KERNEL\
You can copy this file directly to your phone but it won't have bootanimation support.
That's why you need to enter in the Kitchen menu:
1. Press 99 > Enter
2. Press 1 > Enter
3. Press "n" > Enter
4. Press "y" > Enter
5. Press "y" > Enter > "EnterANewZipName" > Enter
6. Now your cwm zip will be located at: C:\cygwin\home\username\kitchen\OUTPUT_ZIP
The zip that can be found in the directory above can be flashable in CWM. Ejoy your own stock kernel with init.d/bootanimation support!
Great tutorial! Btw, this works also with cm9 kernels?
Sent from my GT-I9001 using xda premium
Third post reserved for further use.
Just joking.You should make a tutorial to teach.us how to make an overclocked kernel and so on.
Btw nice tutorial from a great dev.
RyanJWZ said:
Great tutorial! Btw, this works also with cm9 kernels?
Sent from my GT-I9001 using xda premium
Click to expand...
Click to collapse
Thank you
And honestly I have no idea if it's working on CM9 kernels, I think it does work actually, you should give it a try
Costinutz32 said:
Third post reserved for further use.
Just joking.You should make a tutorial to teach.us how to make an overclocked kernel and so on.
Btw nice tutorial from a great dev.
Click to expand...
Click to collapse
lol hehe, I wish I knew how to do that, If I knew that I would have posted a tutorial for sure . I'm totally inexperienced with coding kernels unfortunately
and thanks btw ^^
edit: added screenshots
how to check init.d work?
kingsonwongs said:
how to check init.d work?
Click to expand...
Click to collapse
for example:
/system/etc/init.d/00test
Code:
#!/system/bin/sh
su -c "echo "pass" > /sdcard/pass"
If a file called "pass" will appear on your sdcard it's working
this is more a tutorial for how to make a rom flashable for cwm with kitchen
bootanimation with kitchen is not working for me, had to modify the init.rc manually in boot.img. but you can use the kitchen for extract the boot.img.
however, the headline of this thread is a bit confusing, the tutorial is ok.
i guess, it is not complete.
for set up working folder, you will need
system.ext4.tar
cache.ext4.tar
boot.img
from a nandroid backup of your rom
texten said:
this is more a tutorial for how to make a rom flashable for cwm with kitchen
bootanimation with kitchen is not working for me, had to modify the init.rc manually in boot.img. but you can use the kitchen for extract the boot.img.
however, the headline of this thread is a bit confusing, the tutorial is ok.
i guess, it is not complete.
for set up working folder, you will need
system.ext4.tar
cache.ext4.tar
boot.img
from a nandroid backup of your rom
Click to expand...
Click to collapse
Well actually, I've kept the dummyrom.zip so minimalistic that boot.img is fully compatible with the kitchen (it needed app/bin folder and build.prop), but all other things are basically removed.
And you don't need all those files, we are not trying to create a working rom here, and the bootanimation is idd not working correctly, that's why I added the AOSP bootanimation library to the dummyrom.zip
broodplank1337 said:
Well actually, I've kept the dummyrom.zip so minimalistic that boot.img is fully compatible with the kitchen (it needed app/bin folder and build.prop), but all other things are basically removed.
And you don't need all those files, we are not trying to create a working rom here, and the bootanimation is idd not working correctly, that's why I added the AOSP bootanimation library to the dummyrom.zip
Click to expand...
Click to collapse
ah, ok i didn't know about the dummyrom.zip
but only for extract boot.img and make the small changesfor init.d and bootanimation, you can use other methods, not the kitchen.
the setup for kitchen is much more work as needed for this.
you can also use the tool "disk internals linux reader" and change everything you want manually.
just my 2 cents.
maybe with alle that what you have done for this tutorial, you can change/expand it to "how to make a rom with kitchen"...
well whatever. do it as you want. good luck.
texten said:
ah, ok i didn't know about the dummyrom.zip
but only for extract boot.img and make the small changesfor init.d and bootanimation, you can use other methods, not the kitchen.
the setup for kitchen is much more work as needed for this.
you can also use the tool "disk internals linux reader" and change everything you want manually.
just my 2 cents.
maybe with alle that what you have done for this tutorial, you can change/expand it to "how to make a rom with kitchen"...
well whatever. do it as you want. good luck.
Click to expand...
Click to collapse
about that, you're right, it can be done allot easier, but the thing is, I never got any working kernel when I manually packed them (or with some scripts), so I'm very thankful to the kitchen, which allows me to make an actual working boot.img
Hey brood i tried this tutorial with my stock XXKG3 kernel and did it step by step
Then i flashed the output.zip and added the folder init.d in system/etc/ and the pass script you posted above but there isnt any pass file on my sdcard ):
what went wrong?
//edit: tried pushing a bootanimation (sanim.zip) to /system/media/ but after the reboot it shows the old galaxy s plus bootanimation );
EternalFame said:
Hey brood i tried this tutorial with my stock XXKG3 kernel and did it step by step
Then i flashed the output.zip and added the folder init.d in system/etc/ and the pass script you posted above but there isnt any pass file on my sdcard ):
what went wrong?
//edit: tried pushing a bootanimation (sanim.zip) to /system/media/ but after the reboot it shows the old galaxy s plus bootanimation );
Click to expand...
Click to collapse
hmm the init.d part should work. try it without "su -c" this time
the name of the bootanimation has to be "bootanimation.zip" instead of "sanim.zip"
broodplank1337 said:
hmm the init.d part should work. try it without "su -c" this time
the name of the bootanimation has to be "bootanimation.zip" instead of "sanim.zip"
Click to expand...
Click to collapse
also doesnt work without su -c and renamed to bootanimation.zip but theres still stock bootanim ):
isnt this tut working with 2.3.3 kernel?
BTW: here is my kernel:
www.hengelmueller.bplaced.net/OUTPUT_ZIP.zip
Sent from my GT-I9001 using XDA
EternalFame said:
also doesnt work without su -c and renamed to bootanimation.zip but theres still stock bootanim ):
isnt this tut working with 2.3.3 kernel?
Sent from my GT-I9001 using XDA
Click to expand...
Click to collapse
Hmm then I don't know atm what the problem, but about the bootanimation, did you build a zip from the working folder? Or did you just copy boot.img? Since it needs the bootanimation library which is included in dummyrom.zip
broodplank1337 said:
Hmm then I don't know atm what the problem, but about the bootanimation, did you build a zip from the working folder? Or did you just copy boot.img? Since it needs the bootanimation library which is included in dummyrom.zip
Click to expand...
Click to collapse
i have the bootanimation file in system/bin so that shouldnt be the problem ):
could you pls try with my kernel from the link i posted above?
it drives me nuts that i am not able to do such "easy" things ): ^^
btw: do i need something in init.rc or something which tells the system when it should execute the scripts?
Sent from my GT-I9001 using XDA
Search in the init.rc for system/bin/samsungani and replace it with system/bin/bootanimation.
This should work I guess. AT least this is what i did with my Stock Kernels.
Sent from my GT-I9001 using XDA
Does not work either ):
could you pls try with my kernel above?
Sent from my GT-I9001 using XDA
Tried also with skyhigh and feacore and init.d also doesnt work
could it be that they dont work with 2.3.3 ?
Sent from my GT-I9001 using XDA
EternalFame said:
Tried also with skyhigh and feacore and init.d also doesnt work
could it be that they dont work with 2.3.3 ?
Sent from my GT-I9001 using XDA
Click to expand...
Click to collapse
does your init.d folder and the scripts inside have the right permissions?
broodplank1337 said:
does your init.d folder and the scripts inside have the right permissions?
Click to expand...
Click to collapse
Which permissions do i need?
Sent from my GT-I9001 using XDA
Hi i had istalled the v6 supercharger kit in cm10 rc1, i would know the code for v6 supercharger script that i have to set...
Sent from my GT-S5670 using xda premium
biancoceleste.95 said:
Hi i had istalled the v6 supercharger kit in cm10 rc1, i would know the code for v6 supercharger script that i have to set...
Sent from my GT-S5670 using xda premium
Click to expand...
Click to collapse
Download this script...V6_SuperCharger_for_Android-Update9_RC11_Test_9.sh.pdf... from here http://forum.xda-developers.com/showpost.php?p=18703418&postcount=5021
then, Load script into Script Manager (Run As Root - the skull and crossbones icon which turns green when selected)
Follow instructions/user prompts & select what you want
for patching services.jar...
Download this to your PC...Ultimatic_Jar_Patcher_Tools_RC6_ALL_DEX_Windows.exe.zip... from here http://forum.xda-developers.com/showthread.php?t=1914159
then, remove the .zip extension...
and follow this....... use option A...
1. Run the NEWEST V6 SuperCharger script as always.
2. Patch and install services.jar by whichever method you like best.
Note: All options below (A, B and C) require Java to be installed on your computer - Click to Verify Java Installation
Option A) Use one of the attached -=Ultimatic Jar Patcher Tools=- (exe or zip) which DO EVERYTHING for you "Fully Ultimatically" on DEODEX & ODEX ROMS!
They do everything that is explained in this tutorial - from start to finish ie. Steps 1 to 9!
These will do both Deodex AND Odex ROMS too!
Includes:
Automation tools: ultimatic_jar_patcher_adb.bat (Windows) and ultimatic_jar_patcher_adb.sh (Linux/Mac OSX)
Ultimate Jar Power Tools RC5
latest smali/baksmali v1.4.0
adb (Windows/Linux/Mac OSX)
zip/unzip binaries by Info-ZIP (Windows)
dexopt-wrapper (used for ODEX roms)
Requirements:
For Android device: busybox, android debugging turned on, charge only mode when plugged into computer.
For Computer: Java installed (for baksmali/smali), device drivers
Usage:
Windows - use either the Ultimatic*.exe or the zip's ultimatic*.bat file - Windows exe is NOT zipped. Just remove the .zip extension!
Actually, if you have windows cygwin installed, you can even use the zip's ultimatic*.sh file lol
Linux or Mac OSX - use the zip's ultimatic*.sh file
Download attachment to your PC: zip file? - extract to a folder; exe file? - remove the zip extension
How to run -=Ultimatic Jar Patcher Tools=-
1. Connect your Android to your PC with Android Debugging ENABLED and Mass Storage DISABLED so your device has access to your sdcard. I just put it in Charge Only mode...
2. Windows: Run either the zip's *.bat or the attached *.exe
If running the exe, you can put a different ultimate jar power tools script version in the same folder and it will use that one otherwise it uses the embedded version!
If you have cygwin installed, you can even use the zip's *.sh file at the cygwin prompt.
Linux/Mac OSX: run the zip's *.sh file
Just be sure to read everything and answer Yes or No as is your preference.
Example: The script allows you to choose the level of your Launcher's Super Strength! (BulletProof, Die-Hard, or Hard To Kill)
And if you don't know how to run exes or batch files or shell scripts... then MOVE ALONG... please... god please do move along...)
3. Ultimatic Jar Patcher Tools will:
- pull services.jar/services.odex
- decompile services.jar/services.odex
- run Ultimate Jar Power Tools and apply the patches that you pick
- recompile services.jar with a new classes.dex (deodex roms)
- re-odex services.jar and make a new services.odex (odexed roms)
- install services.jar/services.odex to /system/framework and set permissions
4. Don't be stupid and READ what the hell is going on, OK?
Goto Step 3 if you did Option A!
3. SuperClean & ReStart! (ie. Wipe Dalvik Cache & Reboot)
How do I know if it worked?
Mod 1. Run the latest V6 SuperCharger script and it will tell you if your launcher is SuperCharged!
All credits goes to the developer.... zeppilenrox...... this is an excerpt from his thread......to make things simple......
noypi_101 said:
1. Run the NEWEST V6 SuperCharger script as always.
Click to expand...
Click to collapse
No!
The version after update 9 rc2 are optimized specially for ICS/JB only..you can install them but they won't make much of a difference.
Use only update 9 rc2
can any one give me the full procedure to get init.d and v6 on my mmx a110 v2 ....also i want 60fps without any bug i.e proximity and leds should work!!!!plzzz help!!!!!
abhijeetshankar said:
can any one give me the full procedure to get init.d and v6 on my mmx a110 v2 ....also i want 60fps without any bug i.e proximity and leds should work!!!!plzzz help!!!!!
Click to expand...
Click to collapse
Add init.d support:
1.copy 00test file in /system/etc/init.d folder(create the folder) http://goo.gl/bV745
2.install busybox using normal setup using this app http://goo.gl/CF6vJ
3.Also install terminal emulator http://goo.gl/QoQ0c
4.Reboot
5.Download the file.2. Place it in the root of your sdcard directory. http://goo.gl/vbWSF
6. Launch terminal emulator.
7. Type: su
8. Grant SuperUser access if prompted
9. Type: sh /sdcard/term-init.sh
10. The script will run and follow the instructions
Supercharge script file:
Boost your canvas2 with script as the stock kernel supports init.d
Details can be find here to supercharge 100% http://goo.gl/hsoHG
Advantages: smooth and ram optimization
For 60pfs - Install any of the Custom Rom or mods in the blog
LED - Stock V2 ROM has a better LED
Full coverage and any query on Nexi4Driod Blog http://dileepworld.blogspot.in/2012/11/micromax-a110-canvas-2-complete-coverage.html
Hi 00test file is removed from firum ....
Please put it...
Sent from my Micromax A110 using xda app-developers app
Yup it is removed.
NOTE:I AM NOT RESPONSIBLE FOR YOUR DEVICE
Proper root steps for cwm recovery
1. download kingoroot root with apk and restart
2. Download Replace_Kinguser_with_SuperSU.zip from https://forum.xda-developers.com/attachment.php?attachmentid=3926817&d=1478337705
3. Download prefered unzipping app and unzip to root of internel sd card
4.Download Terminal emulator from playstore
5. In terminal emulator run
HTML:
su
Then
HTML:
sh /sdcard/mrw/root.sh
6.wait for it to launch supersu then update using the normal option and reboot
To install cwm recovery simply follow this guide http://https://forum.xda-developers.com/showthread.php?t=2519432
P.s stay tuned to xda as i am working on a deodexed debloated stock rom for this device and possibly a cynogenmod port
Blu studio x8 hd ROM
Thank you... I've been staying tuned for the longest while now hopefully you didn't forget ;(
More detail please
Can you provide more detail for Step 1? I downloaded and installed the apk and then rebooted. When I get to Step 5, I get "su is not found" from the terminal.
Heterod0x said:
NOTE:I AM NOT RESPONSIBLE FOR YOUR DEVICE
Proper root steps for cwm recovery
1. download kingoroot root with apk and restart
2. Download Replace_Kinguser_with_SuperSU.zip from https://forum.xda-developers.com/attachment.php?attachmentid=3926817&d=1478337705
3. Download prefered unzipping app and unzip to root of internel sd card
4.Download Terminal emulator from playstore
5. In terminal emulator run
HTML:
su
Then
HTML:
sh /sdcard/mrw/root.sh
6.wait for it to launch supersu then update using the normal option and reboot
To install cwm recovery simply follow this guide http://https://forum.xda-developers.com/showthread.php?t=2519432
P.s stay tuned to xda as i am working on a deodexed debloated stock rom for this device and possibly a cynogenmod port
Click to expand...
Click to collapse