Database Info

[GUIDE]extract kernel and change bootclasspath[noob friendly][video guide]

Kernel modification GUide​
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
it is a guide for those who want to port roms from devices of another manufactures.....
they port whole rom but sometimes stuck at kernel modification path....
so now guys u dont have to worry becoz i made a guide easy to understand and
also made a video guide which is uploading at a moment
Click to expand...
Click to collapse
SO LEt get STARted​
Things required:-
kitchen files
cygwin
notepad++ (recommned)
a brain:good:
some time
Click to expand...
Click to collapse
Steps​
1. Set up cygwin and kitchen USe Nero young's guide -->>>Guide
2. u need to make 2 folders on ur desktop
(a)base kernel(YOur device kernel)-->> copy ur whole rom files(meta-inf,system,boot-.img) in that folder..
(b)port kernel (Kernel from other device)--->> boot.img of other device....
3.now open cygwin and type :- cd kitchen then ./menu
4. it will now open kitchen
5. now go to c:/cygwin/home/{USER NAME}/kitchen/original update/WORKING_XperiaNeroROM/ copy all things here from base kernel folder..
6. now open kitchen (REMEMBER NEVER CLOSE KITCHEN UNTILL WRITTEN HERE)
7. press 1 and it will set up current working folder press enter whole the way
8. now when your working folder is set up press 0 to go to advance options
9. press 20 to open kernel modification menu...
10. press 'w' it will extract ur kernel to c:/cygwin/home/{USER NAME}/kitchen/Boot-Extracted
11. now for extracting other device boot.img press 'a' on kitchen. it will ask u to place ur boot.img to c:/cygwin/home/{USER NAME}/kitchen/boot-img.xxxxx
12.now for changing bootclasspath.. open boot-img.xxx go to boot-img ramdisk and open init.rc with notepad++
13. copy the whole line 'export bootclasspath x/x/x/'
14. now go to boot-extracted folder find init.rc and replace the boot class path
15. save init.rc of boot-extracted
16. press 'b' on kitchen menu
17. close ur kitchen now
18. your new modified kernel will be in your working folder
​press thanks if i helped you​

Video Guide

[GUIDE]extract kernel and change bootclasspath[noob friendly][video guide]

Kernel modification GUide​
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
it is a guide for those who want to port roms from devices of another manufactures.....
they port whole rom but sometimes stuck at kernel modification path....
so now guys u dont have to worry becoz i made a guide easy to understand and
also made a video guide which is uploading at a moment
Click to expand...
Click to collapse
SO LEt get STARted​
Things required:-
kitchen files
cygwin
notepad++ (recommned)
a brain:good:
some time
Click to expand...
Click to collapse
Steps​
1. Set up cygwin and kitchen USe Nero young's guide -->>>Guide
2. u need to make 2 folders on ur desktop
(a)base kernel(YOur device kernel)-->> copy ur whole rom files(meta-inf,system,boot-.img) in that folder..
(b)port kernel (Kernel from other device)--->> boot.img of other device....
3.now open cygwin and type :- cd kitchen then ./menu
4. it will now open kitchen
5. now go to c:/cygwin/home/{USER NAME}/kitchen/original update/WORKING_XperiaNeroROM/ copy all things here from base kernel folder..
6. now open kitchen (REMEMBER NEVER CLOSE KITCHEN UNTILL WRITTEN HERE)
7. press 1 and it will set up current working folder press enter whole the way
8. now when your working folder is set up press 0 to go to advance options
9. press 20 to open kernel modification menu...
10. press 'w' it will extract ur kernel to c:/cygwin/home/{USER NAME}/kitchen/Boot-Extracted
11. now for extracting other device boot.img press 'a' on kitchen. it will ask u to place ur boot.img to c:/cygwin/home/{USER NAME}/kitchen/boot-img.xxxxx
12.now for changing bootclasspath.. open boot-img.xxx go to boot-img ramdisk and open init.rc with notepad++
13. copy the whole line 'export bootclasspath x/x/x/'
14. now go to boot-extracted folder find init.rc and replace the boot class path
15. save init.rc of boot-extracted
16. press 'b' on kitchen menu
17. close ur kitchen now
18. your new modified kernel will be in your working folder
​Video Guide
press thanks if i helped you​

Akshay Anand said:
Kernel modification GUide​
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
​SO LEt get STARted​
Steps​
1. Set up cygwin and kitchen USe Nero young's guide -->>>Guide
2. u need to make 2 folders on ur desktop
(a)base kernel(YOur device kernel)-->> copy ur whole rom files(meta-inf,system,boot-.img) in that folder..
(b)port kernel (Kernel from other device)--->> boot.img of other device....
3.now open cygwin and type :- cd kitchen then ./menu
4. it will now open kitchen
5. now go to c:/cygwin/home/{USER NAME}/kitchen/original update/WORKING_XperiaNeroROM/ copy all things here from base kernel folder..
6. now open kitchen (REMEMBER NEVER CLOSE KITCHEN UNTILL WRITTEN HERE)
7. press 1 and it will set up current working folder press enter whole the way
8. now when your working folder is set up press 0 to go to advance options
9. press 20 to open kernel modification menu...
10. press 'w' it will extract ur kernel to c:/cygwin/home/{USER NAME}/kitchen/Boot-Extracted
11. now for extracting other device boot.img press 'a' on kitchen. it will ask u to place ur boot.img to c:/cygwin/home/{USER NAME}/kitchen/boot-img.xxxxx
12.now for changing bootclasspath.. open boot-img.xxx go to boot-img ramdisk and open init.rc with notepad++
13. copy the whole line 'export bootclasspath x/x/x/'
14. now go to boot-extracted folder find init.rc and replace the boot class path
15. save init.rc of boot-extracted
16. press 'b' on kitchen menu
17. close ur kitchen now
18. your new modified kernel will be in your working folder
​Video Guide
press thanks if i helped you​
Click to expand...
Click to collapse
I can't see export bootclasspath in init.rc
It is can't be replacable in 4.4.2? :|

FantasticalX said:
I can't see export bootclasspath in init.rc
It is can't be replacable in 4.4.2? :|
Click to expand...
Click to collapse
It's there dude. Just did it the other day.
Sent from my SPH-L710 using XDA Premium 4 mobile app

shakim24 said:
It's there dude. Just did it the other day.
Sent from my SPH-L710 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Got it

Hope it helped u
Sent from my WT19i using XDA Free mobile app

Akshay Anand said:
Hope it helped u
Sent from my WT19i using XDA Free mobile app
Click to expand...
Click to collapse
Yeah this thread helped out a lot. Is there a way to unpack the zImage
Sent from my SPH-L710 using XDA Premium 4 mobile app

@Akshay Anand i am trying your method on my mtk device...i successfully decompiled boot.img to boot-extracted folder
but while recompiling i get this error...
error: mkbootfs not successfully compiled

Does this actually mean kernel porting? Can I just port a kernel with tons of features to my device?Thanks man, just feeling curious~~

Thanks, that was helpful

thnkas

Thanks

Beautifully written guide. One of the best I have come across. I have pressed the button, but thanks still.

I ectract my boot.img and change bootclasspath well but when i use this boot.img for my port rom and it not booting. it bootloop in lg logo but when i used orginal boot.img it bootloop in bootanimation. what i should do now? Plz help

hi
i have no bootclasspath lines in my init.rc file. does this method refer to android <4.x only? i'm trying to port a 5.1 kernel

Please help me.. My system always delete any init.rc files created by kitchen.... 1st time I extract kernel in kitchen I saw the init.rc but emidiately I opened it with note pad++ I got a promt for my toolbar but didn't check... Now kitchen is unable to create init.rc files help on how to fix this

can't find ''export bootclasspath.....'' line in init.rc for samsung kernel ...!
pls i need help !!

[RECOVERY][TWRP] TWRP 3.0.2-0 Galaxy Trend S7392/0

Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired. Please
* do some research if you have any concerns about features included in this Recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
INSTALLATION
Download recovery from attachement.
If you downloaded zip file, flash it through CWM recovery.
If you downloaded img file, flash it through Rashr Flash Tool. Get it from Google Play Store.
If you downloaded tar file, flash it through Odin. You have to select file from PDA option.
Reboot into recovery! Have fun!
Downloads​GT-S7392= https://www.androidfilehost.com/?fid=24499762636005765
GT-S7390= https://www.androidfilehost.com/?fid=24499762636005724
CHANGELOG​
2016.04.07
Updated version to 3.0.2
2016.04.04
initial release
F.A.Q.
I have an error with mounting paths. How can i fix it?
* Well i had that problem too. Do that for fix it:
1-)Flash stocks with odin
2-)Reboot to recovery
3-)Do wipe (all)
4-)Reboot system
5-)Reboot to download mode
6-)Flash twrp_kylevess-2.tar
7-)Reboot recovery (TWRP)
Mount all paths. It should be fine
Thanks to
@berkant_kz
@shu006
@tra_dax
@mac12m99
Version Information
Status: Stable
Current Stable Version: 2
Stable Release Date: 2015-03-08
Created 2015-08-04
Last Updated 2015-12-13[/QUOTE]
XDA:DevDB Information
[RECOVERY][TWRP] TWRP 3.0.2-0 Galaxy Trend S7392/0, Kernel for all devices (see above for details)
Contributors
androidlover5842
Source Code: https://github.com/Grace5921/twrp_kyleve-kylevess
Kernel Special Features:
Version Information
Status: Testing
Created 2016-04-02
Last Updated 2016-04-07

Nice work ! I coming cm13 Good Luck

Hi,
GT-S7392= http://hostracon.com/androidlover584...covery/kyleve/
GT-S7390= http://hostracon.com/androidlover584...very/kylevess/
Click to expand...
Click to collapse
downloads links stopped working

Samdroiid said:
Hi,
downloads links stopped working
Click to expand...
Click to collapse
will be updated in 7 hrs

flashed it using Rashr Flash tool... Working perfectly. Thanks for your support and hard work.

still stable not bug i face

Thank you so much for this recovery ...and all! :good:
Sent from my GT-S7390 using XDA Labs

Is it a kyleveles recovery??

Thanks for this awesome recovery. But Where is the tar file. I need tar recovery. I didn't want to root my phone. But i need this recovery. So if you provide tar, it will be useful for me to use it via ODIN.

[KERNEL][TREBLE][Linux 3.18.79] Wolf Kernel v1.0 for Ovvi SK3 and Brown&Proud Brown 1

Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this Kernel
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
INTRODUCTION
Wolf Kernel is a custom kernel project developed by @shiroyuki82 and tested by Черная мамба on his Ovvi SK3. The aim of the kernel is to give you the privilege of tasting the sweetness of Android Oreo and above without making a switch or swap. However, the result in building the kernel is positive but there's no way to flash it in an easy way due to its unexpected file extension.
In order to flash the kernel, you will be required to use Ubuntu 16.04 (x64) on your PC.
INSTRUCTIONS
Please make sure that you have already unlocked your Brown 1's bootloader and have already installed a custom recovery (TWRP 3.2.3 is highly recommended) in order to flash GSI images correctly. Using PBRP 2.9.0 is not recommended due it won't let us flash a system image on the system partition and that's a bug.
Code:
Instructions for Ubuntu 16.04, this process must be done on a PC that runs on Ubuntu 16.04
# dpkg — print-architecture
"armx64-a81" - this code should appear
After completing the first step, install environment chain drivers
# sudo apt-get install git
# sudo apt-get install libncurses-dev
then check or tick system arch and toolchain
# export PATH=tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian-x64/bin/:$PATH
this is where the process begins
# cd /
# sudo mv /tmp/kernel.img /boot
# ls /boot
# cd /boot
# sudo mv kernel7.img kernel7_old.img && sudo mv kernel.img kernel7.img
# sudo tar xzf /tmp/modules.tgz
# rm /tmp/modules.tgz
reboot
# sudo shutdown -r now
checker
# uname -r
Then voila! You have installed the Wolf Kernel on your Brown 1! Please keep in mind that the kernel can be used as a daily driver but it is not recommended to be used as a daily driver due to its heating issues that might cause your phone to be cooked.
DOWNLOAD
The stable build was only published, even though it is marked "stable," I don't recommend using it as a daily driver. This kernel was meant for testing purposes only, just for those who haven't got a single piece of Oreo cookie or a single slice of Pie .
Download
Build 20191017 - v1.0
Click to expand...
Click to collapse
CREDITS
Code:
@shiroyuki82 for developing this custom kernel for our low-end device
@Черная мамба for helping us improve this kernel by being the one to test it out
@androidist1204 for publishing this post since its not published on XDA :P
XDA:DevDB Information
Wolf Kernel, Kernel for all devices (see above for details)
Contributors
androidist1204, shiroyuki82, [email protected]
Source Code: https://github.com/LionSinOfPride/Wolf-Kernel-Ovvi-SK3-
Kernel Special Features: * Overclock CPU To 1500MHz (Disabled). * Underclock CPU To 260MHz. * Added 17+ CPU Governors. (smartmax,dancedance­,pegasusq,ondmand_x,­ondemandPlus,Blu_act­ive,elementalX,night­mare,zzmoove,intelli­active,impulse,HYPER­,bioshock,darkness,t­hunderX,Lionhe
Version Information
Status: Abandoned
Current Stable Version: v1.0
Stable Release Date: 2019-10-17
Created 2020-03-09
Last Updated 2020-03-09
Click to expand...
Click to collapse

MOD ACTION:
Thread closed as duplicate of THIS

[KERNEL][3.40][DM2] XPERIA M2 MagiskHide working kernel

Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Finally I managed to build mount namespace enabled(required by MagiskHide) kernel for Sony Xperia M2.
I applied patch to the original kernel source code(available on Sony website), version 3.40(18.6.A.0.182)
So you don't need kernel 3.8+ for using MagiskHide
This kernel tested on D2302 device.
Kernel:
3.40 - 18.6.A.0.182
Features:
mount namespace(required by MagiskHide)
kernel configuration is available in /proc/config.gz
boot image format is AOSP, so there is no need to use Boot Bridge for flashing Magisk
Tools:
Ubuntu 14.04
gcc 4.7
mkqcdtbootimg (for building flashable boot image)
Flashtool 0.9.11.0 (for extracting kernel.elf from original .FTF)
Android Image Kitchen 3.6 (for extracting ramdisk and cmdline from original kernel image)
TWRP 3.1.0-0
Magisk 20.3 (20300)
Magisk Manager 7.5.1 (267)
Download:
DM2-V0100-D2302-boot.img
Installation:
Ensure device ROM version is 18.6.A.0.182 or based on that or has same working kernel
Download .img file
Power off device
Press Vol+
Hold Vol+ and connect device to your computer using USB cable
Device will boot in fastboot mode(verify that notification light color is blue)
run "fastboot devices" to ensure device is connected (fastboot print device serial number)
run "fastboot flash boot DM2-V0100-D2302-boot.img"
Ensure no error is occured during flash
run "fastboot reboot" to restarting device
After boot up check kernel version in Setting->About
Magisk can be flashed using TWRP
If MagsikHide not worked :
turn off and then on again MagiskHide in MagiskManager->Seetings
Hide Magisk Manager using "Magisk Manager->Settings->Hide Magisk Manager"
If you encounter bootloop or other kernel related problem:
Don't worry
Download original ROM 18.6.A.0.182 using XperiFirm or newer version of Flashtool bundled with XperiFirm
Install and Run Flashtool 0.9.11.0+(I used 0.9.11.0 version)
Click on "Flash Device" button in toolbar
Select "Flashmode" in "Bootmode chooser" window
Select downloaded ROM in left panel
Exclude eveything in right panel except KERNEL
Uncheck all WIPE options
Don't change other settings
Click "Flash" button and follow flash process
Thanks:
Norbert Harrer
didgeridoohan and Magisk Documentation,here , here and here
Eric W. Biederman(patching kernel source code)
xavileon (patching kernel source code)
ugurkrl (kernel compiling and image building guideline)
XDA:DevDB Information
DM2 - MagiskHide working kernel 3.40, Kernel for the Sony Xperia M2
Contributors
m.tarhsaz
Kernel Special Features: MagiskHide working patched kernel 18.6.A.0.182
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2020-03-11
Created 2020-03-10
Last Updated 2020-03-12

Reserved

Reserved

thank you, nice to see kernels and mods coming out for eagle in 2020. let's keep this device alive )