{
"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"
}
Team FAH-Q Presents....
Hey guys the following tutorial is for any thinkerers of Stock Samsung Kernel for Samsung Note 8(n5110/n5100)
*Most kernels work the same way but my guide is using this source
Step One:
Download the samsung kernel source for your device
- www.opensource.samsung.com
- search for your device(in this case I'm using n5110)
- now download source(in this case MI1 source)
- download Beastools as you will need them later.
Step Two:
After source is downloaded you will have a giant zip file
- unzip GT-N5110_SEA_JB_Opensource_Update2.zip
- next you need to unzip the Kernel.tar.gz file(any zip manager should work)
Step Three:
Now you have your source to build your zImage(kernel) so lets get the toolchain!
- get Toolchain from android git server , codesourcery and etc ... arm-eabi-4.4.3
Step Four:
Lets edit the Makefile so it uses the toolchain.
- edit Makefile
edit "CROSS_COMPILE" to right toolchain path(You downloaded).
Ex) CROSS_COMPILE=/usr/local/toolchain/arm-eabi-4.4.3/bin/arm-eabi- // check the location of toolchain
Step Five:
To build the kernel follow these steps.
- Open a terminal
- cd to the location of your kernel source
- exceuted the following two commands:
make kona_01_defconfig
make
- give it some time as it can take up to hours to build depending on your build machine.
Step Six:
Once zImage and modules are built get them together with the ramdisk.
- the following are the locations where to find kernel and modules:
kernel/drivers/scsi/scsi_wait_scan.ko
kernel/drivers/net/wireless/bcmdhd/dhd.ko
kernel/arch/arm/boot/zImage
Step Seven:
Lets extract the ramdisk from a stock boot.img or a recovery.img file.
*use the beastools.zip file attached to this post to complete the following.
- unzip my beastools.zip and place boot.img in the same extracted folder.
- open a terminal and cd to the extracted beastools
- run this command to split ramdisk and zImage:
./split_boot boot.img (if using recovery.img just replace boot.img with recovery.img)
*I have included a script by the name of Unpack_kernel.sh that can save you the last step by just running this command:
./Unpack_kernel.sh (this is if you're lazy lol)
Step Eight:
With your ramdisk extracted make whatever changes you want to it(such as making kernel insecure or whatever)
- grab modules and place them in the ramdisk: ramdisk/lib/modules/ (replace old modules or wifi wont work).
- after modules are placed and ramdisk changes are done continue to step nine.
Step Nine:
Place the ramdisk and zImage in the same beastools unzipped folder
- to repack kernel you can use the script I included called pack_kernel.sh by running( ./pack_kernel.sh)
or
- run the commands on your own:
#Ramdisk Repacking
./mkbootfs ramdisk | gzip > ramdisk-new.gz
cd ramdisk
find . | cpio -o -H newc | gzip > ../newramdisk.cpio.gz
cd ../
#Boot.img repacking
./mkbootimg --kernel zImage --ramdisk newramdisk.cpio.gz -o new_boot.img
Step 10:
You will now have your new kernel named new_boot.img
- rename it to boot.img and flash it through heimdall or make it into a flashable for CWM/TWRP.
My Kernel using these steps and making boot.img insecure/enabling init.d access.
Link: Proton_test_kernel
DISCLAIMER:
As always I am not held responsible for anything that happens with your device by flashing anything I make/guide you through making youself.
I am not responsible if flashing my file makes girls more attracted to you either. lol
Hope you guys found this tutorial useful, if so please hit the thanks/donate buttons
In case some of you notice there's an extra file I didn't use in the beastools, boot_info (this file will be used in another little guide but in short it helps you check the following things:
- page size
- base address
- ramdisk address
- cmdline
for those that didn't notice that was in there, shame on you! lol jk kinda.
Post 2,3 and 4 will be taken by me as i will post other guides such as how to make boot.img insecure and how to properly flash boot.img/recovery.img to our Note 8.0 with heimdall as I've yet to see anyone flash anything with heimdall to this tablet.
** Guides will be leaned toward making your kernel from samsung sources, making a zip file to flash it, how to flash through heimdall, and changes you can make yourself to the ramdisk. I like to keep guides that are about the same aspect of modding in the same thread.
mine! lol
30 seconds is too long of a wait to win the post lol
this post smells lol
Pretty cool how about a guide on porting a touch wiz ROM all guide I seen before only show porting from devices that have the same chipset or same android version I'd love to learn to port
DLM2583 said:
Pretty cool how about a guide on porting a touch wiz ROM all guide I seen before only show porting from devices that have the same chipset or same android version I'd love to learn to port
Click to expand...
Click to collapse
My time is limited full time work and full time school :/
I have a couple of projects including this one to work on for the note 8.
After that, for sure I'll put a guide up just know theres no generic way to port touchwiz as every rom is different and theres alot of kernel dependencies for it to work.
Sent from my SCH-I605 using xda app-developers app
Beastmode said:
Team FAH-Q Presents....
Hey guys the following tutorial is for any thinkerers of Stock Samsung Kernel for Samsung Note 8(n5110/n5100)
*Most kernels work the same way but my guide is using this source
Step One:
Download the samsung kernel source for your device
- www.opensource.samsung.com
- search for your device(in this case I'm using n5110)
- now download source(in this case MI1 source)
- download Beastools as you will need them later.
Step Two:
After source is downloaded you will have a giant zip file
- unzip GT-N5110_SEA_JB_Opensource_Update2.zip
- next you need to unzip the Kernel.tar.gz file(any zip manager should work)
Step Three:
Now you have your source to build your zImage(kernel) so lets get the toolchain!
- get Toolchain from android git server , codesourcery and etc ... arm-eabi-4.4.3
Step Four:
Lets edit the Makefile so it uses the toolchain.
- edit Makefile
edit "CROSS_COMPILE" to right toolchain path(You downloaded).
Ex) CROSS_COMPILE=/usr/local/toolchain/arm-eabi-4.4.3/bin/arm-eabi- // check the location of toolchain
Step Five:
To build the kernel follow these steps.
- Open a terminal
- cd to the location of your kernel source
- exceuted the following two commands:
make kona_01_defconfig
make
- give it some time as it can take up to hours to build depending on your build machine.
Step Six:
Once zImage and modules are built get them together with the ramdisk.
- the following are the locations where to find kernel and modules:
kernel/drivers/scsi/scsi_wait_scan.ko
kernel/drivers/net/wireless/bcmdhd/dhd.ko
kernel/arch/arm/boot/zImage
Step Seven:
Lets extract the ramdisk from a stock boot.img or a recovery.img file.
*use the beastools.zip file attached to this post to complete the following.
- unzip my beastools.zip and place boot.img in the same extracted folder.
- open a terminal and cd to the extracted beastools
- run this command to split ramdisk and zImage:
./split_boot boot.img (if using recovery.img just replace boot.img with recovery.img)
*I have included a script by the name of Unpack_kernel.sh that can save you the last step by just running this command:
./Unpack_kernel.sh (this is if you're lazy lol)
Step Eight:
With your ramdisk extracted make whatever changes you want to it(such as making kernel insecure or whatever)
- grab modules and place them in the ramdisk: ramdisk/lib/modules/ (replace old modules or wifi wont work).
- after modules are placed and ramdisk changes are done continue to step nine.
Step Nine:
Place the ramdisk and zImage in the same beastools unzipped folder
- to repack kernel you can use the script I included called pack_kernel.sh by running( ./pack_kernel.sh)
or
- run the commands on your own:
#Ramdisk Repacking
./mkbootfs ramdisk | gzip > ramdisk-new.gz
cd ramdisk
find . | cpio -o -H newc | gzip > ../newramdisk.cpio.gz
cd ../
#Boot.img repacking
./mkbootimg --kernel zImage --ramdisk newramdisk.cpio.gz -o new_boot.img
Step 10:
You will now have your new kernel named new_boot.img
- rename it to boot.img and flash it through heimdall or make it into a flashable for CWM/TWRP.
My Kernel using these steps and making boot.img insecure/enabling init.d access.
Link: Proton_test_kernel
DISCLAIMER:
As always I am not held responsible for anything that happens with your device by flashing anything I make/guide you through making youself.
I am not responsible if flashing my file makes girls more attracted to you either. lol
Hope you guys found this tutorial useful, if so please hit the thanks/donate buttons
In case some of you notice there's an extra file I didn't use in the beastools, boot_info (this file will be used in another little guide but in short it helps you check the following things:
- page size
- base address
- ramdisk address
- cmdline
for those that didn't notice that was in there, shame on you! lol jk kinda.
Post 2,3 and 4 will be taken by me as i will post other guides such as how to make boot.img insecure and how to properly flash boot.img/recovery.img to our Note 8.0 with heimdall as I've yet to see anyone flash anything with heimdall to this tablet.
** Guides will be leaned toward making your kernel from samsung sources, making a zip file to flash it, how to flash through heimdall, and changes you can make yourself to the ramdisk. I like to keep guides that are about the same aspect of modding in the same thread.
Click to expand...
Click to collapse
Nice 1.
I'll try this method for build different model.
Beastmode said:
Team FAH-Q Presents....
Hey guys the following tutorial is for any thinkerers of Stock Samsung Kernel for Samsung Note 8(n5110/n5100)
*Most kernels work the same way but my guide is using this source
Step One:
Download the samsung kernel source for your device
- www.opensource.samsung.com
- search for your device(in this case I'm using n5110)
- now download source(in this case MI1 source)
- download Beastools as you will need them later.
Step Two:
After source is downloaded you will have a giant zip file
- unzip GT-N5110_SEA_JB_Opensource_Update2.zip
- next you need to unzip the Kernel.tar.gz file(any zip manager should work)
Step Three:
Now you have your source to build your zImage(kernel) so lets get the toolchain!
- get Toolchain from android git server , codesourcery and etc ... arm-eabi-4.4.3
Step Four:
Lets edit the Makefile so it uses the toolchain.
- edit Makefile
edit "CROSS_COMPILE" to right toolchain path(You downloaded).
Ex) CROSS_COMPILE=/usr/local/toolchain/arm-eabi-4.4.3/bin/arm-eabi- // check the location of toolchain
Step Five:
To build the kernel follow these steps.
- Open a terminal
- cd to the location of your kernel source
- exceuted the following two commands:
make kona_01_defconfig
make
- give it some time as it can take up to hours to build depending on your build machine.
Step Six:
Once zImage and modules are built get them together with the ramdisk.
- the following are the locations where to find kernel and modules:
kernel/drivers/scsi/scsi_wait_scan.ko
kernel/drivers/net/wireless/bcmdhd/dhd.ko
kernel/arch/arm/boot/zImage
Step Seven:
Lets extract the ramdisk from a stock boot.img or a recovery.img file.
*use the beastools.zip file attached to this post to complete the following.
- unzip my beastools.zip and place boot.img in the same extracted folder.
- open a terminal and cd to the extracted beastools
- run this command to split ramdisk and zImage:
./split_boot boot.img (if using recovery.img just replace boot.img with recovery.img)
*I have included a script by the name of Unpack_kernel.sh that can save you the last step by just running this command:
./Unpack_kernel.sh (this is if you're lazy lol)
Step Eight:
With your ramdisk extracted make whatever changes you want to it(such as making kernel insecure or whatever)
- grab modules and place them in the ramdisk: ramdisk/lib/modules/ (replace old modules or wifi wont work).
- after modules are placed and ramdisk changes are done continue to step nine.
Step Nine:
Place the ramdisk and zImage in the same beastools unzipped folder
- to repack kernel you can use the script I included called pack_kernel.sh by running( ./pack_kernel.sh)
or
- run the commands on your own:
#Ramdisk Repacking
./mkbootfs ramdisk | gzip > ramdisk-new.gz
cd ramdisk
find . | cpio -o -H newc | gzip > ../newramdisk.cpio.gz
cd ../
#Boot.img repacking
./mkbootimg --kernel zImage --ramdisk newramdisk.cpio.gz -o new_boot.img
Step 10:
You will now have your new kernel named new_boot.img
- rename it to boot.img and flash it through heimdall or make it into a flashable for CWM/TWRP.
My Kernel using these steps and making boot.img insecure/enabling init.d access.
Link: Proton_test_kernel
DISCLAIMER:
As always I am not held responsible for anything that happens with your device by flashing anything I make/guide you through making youself.
I am not responsible if flashing my file makes girls more attracted to you either. lol
Hope you guys found this tutorial useful, if so please hit the thanks/donate buttons
In case some of you notice there's an extra file I didn't use in the beastools, boot_info (this file will be used in another little guide but in short it helps you check the following things:
- page size
- base address
- ramdisk address
- cmdline
for those that didn't notice that was in there, shame on you! lol jk kinda.
Post 2,3 and 4 will be taken by me as i will post other guides such as how to make boot.img insecure and how to properly flash boot.img/recovery.img to our Note 8.0 with heimdall as I've yet to see anyone flash anything with heimdall to this tablet.
** Guides will be leaned toward making your kernel from samsung sources, making a zip file to flash it, how to flash through heimdall, and changes you can make yourself to the ramdisk. I like to keep guides that are about the same aspect of modding in the same thread.
Click to expand...
Click to collapse
Thanks. I have looked for something like this for a while. Do you think this would work for a Galaxy Note 3? I am not asking for an exact answer; rather do know of any reason it would not? Should I use a different tool? Any gotchas? etc.
Beastmode said:
Step Seven:
Lets extract the ramdisk from a stock boot.img or a recovery.img file.
*use the beastools.zip file attached to this post to complete the following.
- unzip my beastools.zip and place boot.img in the same extracted folder.
Click to expand...
Click to collapse
Hi and thank you for the great post. I have been able to ceate the image and modules for a Note 3 device. I am not sure which boot.img you are referting to. Where do I get this? I did a search on my machine, and I don't have it. Do I need to get this file somewhere else online since I am working on a different device? I really appreciate your advice.
Code:
[email protected]:~/Kernel$ make kona_01_defconfig
HOSTCC scripts/kconfig/conf.o
SHIPPED scripts/kconfig/zconf.tab.c
SHIPPED scripts/kconfig/zconf.lex.c
SHIPPED scripts/kconfig/zconf.hash.c
HOSTCC scripts/kconfig/zconf.tab.o
HOSTLD scripts/kconfig/conf
drivers/usb/gadget/Kconfig:1107:warning: leading whitespace ignored
drivers/motor/Kconfig:38:warning: type of 'BCM_SS_VIBRA' redefined from 'boolean' to 'tristate'
arch/arm/mach-hawaii/Kconfig:272:warning: choice value used outside its choice group
arch/arm/mach-hawaii/Kconfig:277:warning: choice value used outside its choice group
arch/arm/mach-hawaii/Kconfig:282:warning: choice value used outside its choice group
arch/arm/mach-hawaii/Kconfig:304:warning: choice value used outside its choice group
arch/arm/mach-hawaii/Kconfig:287:warning: choice value used outside its choice group
arch/arm/mach-hawaii/Kconfig:331:warning: choice value used outside its choice group
arch/arm/mach-hawaii/Kconfig:336:warning: choice value used outside its choice group
***
*** Can't find default configuration "arch/arm/configs/kona_01_defconfig"!
***
make[1]: *** [kona_01_defconfig] Error 1
make: *** [kona_01_defconfig] Error 2
PLEASE HELP
Hi
is this method can change the SElinux status ? ( I want to change it to permissive )
Disclaimer: I am not responsible for anything bad that may occur from the use of this kitchen, but I will take all the credit you can give me if it works for you
{
"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"
}
Please read the usage instructions in post #3 and the troubleshooting in post #4 below before asking for help. Thanks
Free Changelog
Download/Install
Donate version for Windows/Mac/Linux/WSL:
Dedicated thread found here
Free Kitchen (Linux terminal):
**NOTE: The free kitchen will not work in WSL**​
Download the kitchen.zip from here. Extract to a new directory.
Enter the following commands one by one pressing ENTER after each line where "/location/of/kitchen" is the directory where the kitchen lives:
Code:
cd /location/of/kitchen
./superr
Dependencies:
Java 8 or higher (8 is recommended)
Python (to run the launcher (could be bypassed by running tools/source/superr in the terminal from the main kitchen directory))
Video tutorials by @chevycam94
Credits:
@osm0sis - For Busybox Installer and Android Image Kitchen
@Chainfire - For SuperSU
@JesusFreke - For [Bak]smali
@nkk71 - For creating the TWRP minzip patch
@Captain_Throwback - For providing a pre-compiled update-binary with the minzip patch and squashing bugs
@_riddle - For oat2dex
@iBotPeaches - For Apktool
@AOSP - For zipalign, adb, aapt, img2simg, simg2img, make_ext4fs
@xpirt - for img2sdat
@bcrichster - For extensive testing
XDA:DevDB Information
SuperR's Kitchen, Tool/Utility for the XDA Community Apps
Contributors
SuperR.
Version Information
Status: Stable
Created 2017-04-27
Last Updated 2020-07-24
Usage:
Run "superr" from it's location in terminal
Create new project using the menu
Copy ROM zip into the superr_NAME directory of this tool (NAME = the name of your new project).
OR
Copy system.ext4.tar and boot.img into the superr_NAME directory of this tool.
OR
Copy system.ext4.win and boot.emmc.win into the superr_NAME directory of this tool.
OR
Copy system.img and boot.img into the superr_NAME directory of this tool.
OR
Copy official Nexus tgz into the superr_NAME directory of this tool.
OR
Copy Samsung firmware zip into the superr_NAME directory of this tool.
OR
Copy Moto firmware zip into the superr_NAME directory of this tool.
OR
Leave superr_NAME directory empty to extract from rooted device or custom recovery
Extract for new ROM from the Main menu.
Enjoy!
Example:
In your terminal, type the following where "/home/user/kitchen/" is the directory where the kitchen lives:
Code:
cd /home/user/kitchen/
./superr
NOTE: the above code is 2 separate commands and requires ENTER to be pressed after each command
OR
Double-click the superr file and choose "Run in Terminal" if your OS supports it.
Add your own device support:
Create a new project in the kitchen.
Add your files to the project directory (system.img/boot.img, system.ext4.tar, win, zip, etc.)
Extract for new rom from the menu
When asked how to get your partitions, choose detect by-name from boot.img. If it gives you an error, put a recovery.img in your project directory and choose detect mmc from recovery.img.
Enjoy
Features:
*Extract and create ROM from:
Rooted Device
Custom Recovery
Existing ROM zip
system.img/boot.img (and cache.img on Samsung devices)
system.ext4.tar/boot.img
system.ext4.win/boot.emmc.win (including multi-file *.win000, *.win001, etc)
Moto and other factory firmware zips containing sparsechunk files
cm12 + roms with sparse dat files
Zips that contain system.img and boot.img
Samsung firmware zips that contain tar.md5 file
Official Pixel/Nexus firmware tgz
Official Pixel/Nexus preview tgz
SpreadTrum firmware that includes a pac file
system directory that contains symlinks and boot.img
*Create flashable zips of many varieties including:
Full ROM
Switch between set_perm, set_metadata (KitKat+), raw_img, and sparse_dat (Lollipop+)
Kernel
Recovery
Media
app, priv-app, and framework
*Deodex the following:
Pie ROMs
Oreo ROMs
Nougat ROMs
Marshmallow ROMs
Lollipop ROMs
KitKat and earlier ROMs
*Root features:
Root/unroot
Choose SuperSU or Magisk zip (add other versions to /tools/root/root_zips directory)
Choose system OR systemless root for M+ and Samsung 5.1.1 roms (SuperSU only)
*Boot features:
Unpack/repack boot/recovery img (Big Thanks to @osm0sis for mkbootimg source!!!)
Add/remove su.d support
Add/remove insecure boot
Remove dm-verity
Remove forceencrypt
*By-name auto-detection from:
Device
Existing ROM
boot.img
kernel.elf
**OR**...manually enter it
*mmcblk auto-detection from:
recovery.img
*Kitchen updater:
View the last 3 changelogs when an update is available.
Incremental update for updating the most recent previous version
Option to check for updates when the kitchen starts
*Create system.img
*Device database for mmcblk devices (currently very small, but will grow over time)
*Add devices to the assert
*Add custom asserts
*Zipalign apks
*Debloat ROM
*Custom Debloat list support
*Remove Knox
*Add/remove busybox (Big thanks to @osm0sis for his Busybox Installer)
*Add/remove user app support (/data/app)
*Sign zips
*Translatable with language files
*Donate version additional features:
Cross-platform - Windows, WSL, Macos, Linux
tarfs - Get original permissions, contexts, and capabilities from tar/win backups.
Create system.img with identical permissions, contexts, and capabilities as the original system.img or tar/win backup.
Plugins - Probably the best part! Currently over 20 extra features and growing
Root - Use a custom root zip (not the included Magisk or SuperSU)
Custom directory - can be included in your ROM and flashed to a specified partition
Custom Signature - No Built with SuperR's Kitchen, anywhere, plus add your own
Custom Build Display in About Phone, or leave it as default
AutoROM - Automation for ROM creatiion using a congig file (there's a plugin for that)
Convert updater-script to an update-binary script
No mounting img files. One less thing requiring your password and interrupting extraction.
Upload support.zips and device.zip directly from the kitchen for review
Download language files directly from the kitchen
Restore original boot.img after modifying and repacking
Remove asserts from the updater-script
Configurable compression level for packing zips
Remove all placeholder tags (#ASSERT, #SYM, #PERM, etc.) before packing the ROM
Create ext4 img file from any partition you include in your ROM.
zipalign without building ROM
Fix ext4.img files automatically if block count is higher than actual blocks
Troubleshooting/FAQ:
When asking for help, please provide as much of the following info as possible so I can help as easily as possible. I am a busy person and would prefer not to ask all of these questions every time someone has a problem. Thank you for understanding.
What Kitchen version?
What environment are you running the kitchen in (OS, 32/64-bit, cygwin, Bash on Windows, etc.)?
What device are you working on (make/model)?
What was the source you started from (system.img, system.ext4.tar, rom.zip, etc.)
What Android version?
What perm method (set_perm, set_metadata, sparse_dat, raw_img)?
What did you do after extracting and before building?
Were there errors on the screen if you scroll up in the terminal?
Send a recovery.log after flashing if you have problems flashing the ROM.
Send a link that does not require registration to the files you started with (nandroid, system.img, boot.img, etc)
Use the support option in the Misc Tools menu and attach the support.zip to your post.
Ubuntu4Kitchen
An Ubuntu 16.04 distro with all the things you need to get the kitchen working easily.
Visit the dedicated thread here
Language Files (translations)
English - Default/Included in the kitchen
Download additional language files here
Once the language zip has been downloaded, extract to /kitchen/tools/language and restart the kitchen.
Does this kitchen support Windows CYGWIN?
CYGWIN is not supported and will not work. Try the donate kitchen for Windows, Linux, and Mac.
WSL (Bash on Ubuntu on Windows)
WSL is not supported in the free kitchen and will not work. Try the donate kitchen for Windows, Linux, and Mac.
Which perm type should I choose?
Here is a very brief summary of set_perm, set_metadata, sparse_dat, and raw_img.
set_perm : The oldest of the 4. Sets file/directory permissions when flashing a rom. Not recommended for KitKat and above.
set_metadata: Also sets file/directory permissions when flashing a rom, but also adds file contexts. It was introduced with selinux in KitKat. Recommended for KitKat and above.
sparse_dat: The newest of the 4, and only works on Lollipop +. The permissions, symlinks, and file contexts are all added inside a sparse image. A sparse image is an image with a more efficient space usage. Only for Lollipop and above. The free kitchen uses AOSP permissions/capabilities when building system.img. If your device requires different permissions, this method will not work for you in the free kitchen.
raw_img: This is literally raw images that are flashed to your device. The permissions, symlinks, and file contexts are all added inside the raw image. Works for all Android versions. The free kitchen uses AOSP permissions/capabilities when building system.img. If your device requires different permissions, this method will not work for you in the free kitchen.
Flashing error:
This package is for "xxxxx" devices; this is a "yyyyy"
The problem is the asserts and it is easy to fix. In the kitchen menu, go to ROM Tools > Asserts > Add/Remove device asserts. At the bottom it will say "xxxxx". Edit the line to say "xxxxx,yyyyy" and press enter. Build your rom again and flash.
Why is my ROM zip so small?
blkdiscard failed: Invalid argument
These are generally due to the partition size detection method. You need the correct partition size for ALL partitions you are creating sparse dat and raw_img images for. The kitchen will ask for each one that is included in your rom when you choose to build the full rom zip. If none of the provided auto-detect methods work, you will need to find the partition size on your own and enter it manually in the kitchen.
Root problems?
You can replace the SuperSU.zip and Magisk.zip in the kitchen with any flashable SuperSU/Magisk version you want. It is located in kitchen/tools/root/root_zips. Delete the one that is there (if it exists) and add yours. Then, unroot, re-root and your replacement will be used.
Auto check for updates when kitchen starts
To enable the auto update check, go to "Check for updates" in the main menu. After it checks, you will be asked if you want to enable it.
I added root and busybox but there is no su or busybox in my project. Why?
The kitchen does not add Busybox or SuperSU/Magisk files to the project. Instead it adds flashable zips inside the rom.zip. There are many variables to deal with (Android version, device architecture, manufacturer, system/systemless, etc.). Flashing the zips with the rom accounts for all of these variables and there is no reason to re-invent the wheel.
Debloat and custom debloat
There are 2 options in the debloat menu (besides knox which is self explanatory):
1) Debloat ROM
This option removes all files included in the kitchens standard bloat list file - /kitchen/tools/root/bloat
2) Custom Debloat
This option removes all files included in the bloat_custom file - /kitchen/tools/root/bloat_custom OR kitchen/superr_project/00_project_files/bloat_custom
This file is empty by default and is there for you to add whatever you want to remove. You can either add everything you want to remove and use only option 2, or you can add new files here and use option 1 and 2.
I suggest you take a look at /kitchen/tools/root/bloat to see the format of the listed bloat files. Use the same format for the bloat_custom file.
When you use either option, the files are not deleted. Instead they are moved to the 00_project_files directory in case you want to restore them later.
Deodexing
Deodexing Samsung roms may or may not work. If your rom does not boot after deodexing, try it without. If it works and you must deodex your rom, try a different tool. I hear svadev deodex tool works well for Samsung roms.
boot.img errors
If the kitchen gives you errors about unpacking boot.img, there is a good chance I will not be able to help. I suggest you figure out how to unpack it using Linux commands/binaries and let me know how you did it. You may also find a tutorial about how to unpack your boot.img. If so, please send a link. It does not help me to know another tool works. I need the commands/binaries used in order to update the kitchen.
Feel free to upload your boot.img AND the build.prop from the same rom so I can check to see if I can fix it. I will ignore you if you don't upload both mentioned files
I do not answer support questions through PM. There are no exceptions. Post in the thread if you want help so others can give suggestions and learn from your solution
I will not answer questions if it is clear that you have not read the OP, the info posts after the OP, and searched the thread for answers. I do not have time to answer the same questions over and over. Many questions are already answered in this thread and if you want help, I expect you to try and solve it on your own before posting. If your question has not been answered in the thread, I am happy to assist in any way possible.
If I ask you to upload files, they need to be uploaded on a server that does not require registration for full speed downloads, or registration for downloads at all. Drive, Dropbox, AFH, and Mega are examples of acceptable servers. There are many other good ones, but I hope you get the point.
Thanks for understanding
reserved
Looks promissing, gonna try it asap :good:
I suppose it to work for many devices but are there any already tested for?
Looks great mate. Can't wait to give it a go
Its been an honor, testing this out! This deserves to be stickied!!
Sent from my N9510 using Tapatalk
---------- Post added at 04:51 AM ---------- Previous post was at 04:48 AM ----------
Androidwizzard said:
Looks promissing, gonna try it asap :good:
I suppose it to work for many devices but are there any already tested for?
Click to expand...
Click to collapse
Zte Concord 2
Zte Warp4G
Moto E 2015
LG Exceed 2
LG Realm
Still waiting on results from:
MediaTEK VKworld (VS6050S)
SuperR. said:
Disclaimer: I am not responsible for anything bad that may occur from the use of this tool, but I will take all the credit you can give me if it works for you
Sent from my N9510 using Tapatalk
Click to expand...
Click to collapse
Nice and finally something for Linux. To bad I'm out of town can't wait to test this...
Nice work
Sent from my SM-G928T using Tapatalk
bcrichster said:
Its been an honor, testing this out! This deserves to be stickied!!
Sent from my N9510 using Tapatalk
---------- Post added at 04:51 AM ---------- Previous post was at 04:48 AM ----------
Zte Concord 2
Zte Warp4G
Moto E 2015
LG Exceed 2
LG Realm
Still waiting on results from:
MediaTEK VKworld (VS6050S)
SuperR. said:
Disclaimer: I am not responsible for anything bad that may occur from the use of this tool, but I will take all the credit you can give me if it works for you
Sent from my N9510 using Tapatalk
Click to expand...
Click to collapse
Think it needs to be in xda portal as well
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
I'll give it a shot on Samsung Galaxy Note 5 - if there aren't any objections against @SuperR.
Is portal different than Chef Central?
Sent from my N9510 using Tapatalk
bcrichster said:
Is portal different than Chef Central?
Sent from my N9510 using Tapatalk
Click to expand...
Click to collapse
Xda portal is video review and goes on xda Facebook as well
Sent from my SM-N920C using Tapatalk
Androidwizzard said:
I'll give it a shot on Samsung Galaxy Note 5 - if there aren't any objections against @SuperR.
Click to expand...
Click to collapse
Right on, should have Knox removal as well. By all means, plz report back
Sent from my N9510 using Tapatalk
Good! I can test with a mtk6582 device with lollipop stock rom... sounds great!! SUPPORT!
Regarding MTK devices, I have never owned one so I am totally unfamiliar with special requirements they may need. I will add support for everything I can as issues come up
SuperR. said:
Regarding MTK devices, I have never owned one so I am totally unfamiliar with special requirements they may need. I will add support for everything I can as issues come up
Click to expand...
Click to collapse
I think you need to add mkbootimg ( https://github.com/osm0sis/mkbootimg ) for work with mtk based boot.img and maybe edit the img extraction of stock imgs.... I dont't now bro, you're the chef hahaha
Regards and support
duniel said:
I think you need to add mkbootimg ( https://github.com/osm0sis/mkbootimg ) for work with mtk based boot.img and maybe edit the img extraction of stock imgs.... I dont't now bro, you're the chef hahaha
Regards and support
Click to expand...
Click to collapse
This kitchen already uses Android Image Kitchen by osm0sis, which includes his mkbootimg. Maybe it will already work for MTK. Let me know if you encounter problems.
SuperR. said:
This kitchen already uses Android Image Kitchen by osm0sis, which includes his mkbootimg. Maybe it will already work for MTK. Let me know if you encounter problems.
Click to expand...
Click to collapse
Yes, It should work.
When I try with my device I'll tell you the results
Regards