[MultiROM] [LINUX] [How-to] Rom installers for sdcard - Nexus 7 Original Development

This is an (hopefully) updated collection of all roms (not android based, but other linux OS, like ubuntu, archlinux, fedora...) for nexus 7 (grouper and tilapia) available using the MultiROM system.
MultiROM is an amazing hack (I want to thank again its author, Tasssadar) that permits to boot different OS (multiboot) and different android roms. It starts between kernel and rom init, showing a sort of bootloader dialog to choose which system to boot.
It supports installing (and booting, of course) roms to USB drives.
To use MultiROM you need multirom installation zip , a modified TWRP recovery and kernels with kexec support. Relax, is not hard or long to do this.
More information and installation (of MultiROM, recovery and kernels) --> [ MULTIROM ]
PS: I need to specify I coded nothing, my only work was helping with issues, repacking roms, make them work. I want to say thank you to all devs are developing for Nexus 7, I'm doing this because I appreciate their work and I want MultiROM to rise. It deserves to.
HOW TO INSTALL A ROM.
Tasssadar provided also a zip template (see the [ WIKI ] for more info) that is incredibly easy to use.
To install a linux os to sdcard, you just need to download the zip and flash it like a normal update.zip.
It won't replace your internal rom, because it is going to install in /sdcard, not in /system or /data. And it WON'T wipe anything.
Remember that flashing ubuntu or android rom is DIFFERENT from flashing those zips. To flash ubuntu or another android rom you need to use MultiROM menu under ADVANCED voice in recovery (again, see wiki or multirom thread if you need more information).
ROM PACKS.
In the next post I'll share links for rom zips. If you have other zips or if you have built other zips, please share them. They will be (hopefully) added to the list. If not, please pm me. I can't read all posts.
If you want to share a zip, please try it first. I don't know if I'll be able to test everything real-time, and I don't want anyone to see his sdcard erased or strange things like this. MultiROM has a percent of risk, but nobody has lost his data till now. So please share zips consciously.

ROM LIST (DOWNLOADS)
* [NEW] PLASMA ACTIVE 4.0 (20140121)
mirror: http://d-h.st/Khh
old version: https://docs.google.com/file/d/0B9ZvdqAbuJi2blQ0TDgweFFKTlU/edit
description: KDE for embedded devices. Very cool and interesting. 4.0 version is more stable, video codec is working as well. Little slow booting.
* BODHI LINUX 20130109
old version: INITIAL RELEASE
notes: old version passwd for root and armhf user is trustno1 (sorry for that, is my fault. In new release it is again bodhilinux)
description: Ubuntu with E17 (Enlightenment) with mobile GUI. Pretty stable and... veeery fast.
*ArchLinux 20130113-2
old version: -
description: ArchLinux. Simply. Not designed for basic users. Really powerfull, with already packed KDE, Gnome-shell, LXDE, XFCE, Enlightenment environments (and many others probably). Needs testing, and some love, as it's initial release.
*WebOS ALPHA
old version: http://www.mediafire.com/?3m58uuvysxiwypw
description: still in alpha stage, unstable. Interesting project. Needs love.
* [MANUAL INSTALL] Ubuntu Touch Tablet DEVELOPER PREVIEW
old version: -
description: developer preview, android-based, with the new Ubuntu Touch UI.
[NEW] Use MultiROM app to install the latest version in the easiest way
ROMS TO BE PACKED/MADE WORKING:
fedora4nexus7?

PAY ATTENTION: NEW MULTIROM CHANGED THE ROM ZIP STRUCTURE!
NEW STRUCTURE HERE.
I GUESS YOU CAN USE OLD ZIPS, BUT I CAN'T TRY AND IT'S BETTER TO USE NEW METHOD (REPACK NEEDED)
STEPS TO CREATE A NEW ROM ZIP (EASY-WAY):
* first, download the template (reworked by me)
* then, unzip the template, put the root.tar.gz and rom_info.txt inside rom folder (if you don't know what I'm talking about, read again the wiki - link above)
* edit rom name inside of scripts/extract.sh script (it's the only thing you have to edit, unless you want it to do something else, but be careful in that case)
* select the 3 folders (META-INF, rom, scripts) and zip them in a zip called <DISTRONAME>-MultiROM-Installer-<VERSION>.zip (I think it's a good standard, if you don't like simply name it another way, but I reckon that using a standard would be a very good thing)
*when the zip is finished, upload your zip somewhere (I use google drive now, but I hope I'll have my storage sometime in the future) and share the link here. I will add it to the list.
If I don't, pm me.
[EDIT] new packing method for webos available https://github.com/Tasssadar/webos_multirom_packer [/EDIT]

MORE INFORMATION.
PLASMA ACTIVE.
known bugs: https://wiki.merproject.org/wiki/Community_Workspace/Tegra3/Nexus7/PA_Known_Issues
username/password : mer/mer, root/mer
Interesting features : Plays 720p movies full screen with sound and 1080p full screen down scaled with sound.
BODHI LINUX.
known bugs: http://forums.bodhilinux.com/index.php?/forum/40-nexus-7/
username/password: armhf/bodhilinux
useful page (customization, add software, guides): http://wiki.bodhilinux.com/doku.php
ARCHLINUX.
armv7h images: http://os.archlinuxarm.org/os/ (see tegra directory)
username/password: arch/arch, root/root
useful link (bible): https://wiki.archlinux.org/
infos: needs an OTG keyboard or to use "sudo screen /dev/ttyACM0 115200" to connect via usb.
While you are connected you need to configure wifi. I use a script that simply uses iwconfig, wpa_supplicant.conf and dhcpcd to get a wifi connection.
The rest is up to you.
Enlightenment is preinstalled in build 20130113-2.
UBUNTU TOUCH.
infos: use MultiROM Manager app to install it.
GENERAL.
lintz said:
Recomended "fixes" after first install (Mer, Plasma ndr) :
Install custom keyboard (write this comands in terminal start with su and after the password for root by default mer)
1. zypper ar -G http://repo.pub.meego.com/home:/won...wonko:branches:Project:KDE:Trunk:Testing.repo
2. zypper up maliit-active libmaliit-quick
3. killall -9 maliit-server
Update the system (use su and root password first)
zypper ref && zypper up
Install GUI package manager (same here su and root password)
zypper in apper
Click to expand...
Click to collapse
Thanks to lintz for the suggestions.

LATEST HOT NEWS.
-updated with latest Plasma version.
-updated with Ubuntu Touch
-updated with latest Plasma & WEBOS version (repacked for new MultiROM structure)
-updated with Ubuntu Touch Dev Preview
-updated OP with arch infos.
-Making zip for new BodhiLinux version, that now has correct passwd
Code:
bodhilinux
as it should be.

xela92 said:
Making zip for new BodhiLinux version, that now has correct passwd
Code:
bodhilinux
as it should be.
Click to expand...
Click to collapse
thx xela, I'm still having trouble creating a zip with the template. perhaps you could post the steps you took to create the new bodhi release

bonzer2u said:
thx xela, I'm still having trouble creating a zip with the template. perhaps you could post the steps you took to create the new bodhi release
Click to expand...
Click to collapse
Steps how-to done
Later (when upload ends) I'll share Bodhi new version installer link

Nice thread. Can't wait to try some other distro's.

xela92 said:
ROM LIST (DOWNLOADS)
* PLASMA ACTIVE 20130109
old version: -
description: KDE for embedded devices. Very cool and interesting, but still an alpha.
* BODHI LINUX (uploading new version)
old version: INITIAL RELEASE
notes: old version passwd for root and armhf user is trustno1 (sorry for that, is my fault. In new release it is again bodhilinux)
description: Ubuntu with E17 (Enlightenment) with mobile GUI. Pretty stable and... veeery fast.
Click to expand...
Click to collapse
Needs more info.
Add following kategories
Plasma Active
Bugs : https://wiki.merproject.org/wiki/Community_Workspace/Tegra3/Nexus7/PA_Known_Issues
Username passwords : mer/mer, root/mer
Recomended "fixes" after first install :
Install custom keyboard (write this comands in terminal start with su and after the password for root by default mer)
1. zypper ar -G http://repo.pub.meego.com/home:/won...wonko:branches:Project:KDE:Trunk:Testing.repo
2. zypper up maliit-active libmaliit-quick
3. killall -9 maliit-server
Update the system (use su and root password first)
zypper ref && zypper up
Install GUI package manager (same here su and root password)
zypper in apper
Features : Plays 720p movies full screen with sound and 1080p full screen down scaled with sound.
Same thing for Bodhi. But I dont know the detales about it since I don't use it.
PS as it is now this thread feels as a start to a redundant thread to what is written in Tassadars first 3 posts in the MultiRom thread. Better if you focus on the current distros that don't have any "real" maintener here on xda.

I will add those categories later

lintz said:
Needs more info.
Add following kategories
Plasma Active
Bugs : https://wiki.merproject.org/wiki/Community_Workspace/Tegra3/Nexus7/PA_Known_Issues
Username passwords : mer/mer, root/mer
Recomended "fixes" after first install :
Install custom keyboard (write this comands in terminal start with su and after the password for root by default mer)
1. zypper ar -G http://repo.pub.meego.com/home:/won...wonko:branches:Project:KDE:Trunk:Testing.repo
2. zypper up maliit-active libmaliit-quick
3. killall -9 maliit-server
Update the system (use su and root password first)
zypper ref && zypper up
Install GUI package manager (same here su and root password)
zypper in apper
Features : Plays 720p movies full screen with sound and 1080p full screen down scaled with sound.
Same thing for Bodhi. But I dont know the detales about it since I don't use it.
PS as it is now this thread feels as a start to a redundant thread to what is written in Tassadars first 3 posts in the MultiRom thread. Better if you focus on the current distros that don't have any "real" maintener here on xda.
Click to expand...
Click to collapse
thanks
this solved my onscreen keyboard problem (not working over browser) ... now only gui glitches was left (multitasking bar )

xela92 said:
STEPS TO CREATE A NEW ROM ZIP (EASY-WAY):
* first, download the template (reworked by me)
* then, unzip the template, put the root.tar.gz and rom_info.txt inside rom folder (if you don't know what I'm talking about, read again the wiki - link above)
* edit rom name inside of scripts/extract.sh script (it's the only thing you have to edit, unless you want it to do something else, but be careful in that case)
* select the 3 folders (META-INF, rom, scripts) and zip them in a zip called <DISTRONAME>-MultiROM-Installer-<VERSION>.zip (I think it's a good standard, if you don't like simply name it another way, but I reckon that using a standard would be a very good thing)
*when the zip is finished, upload your zip somewhere (I use google drive now, but I hope I'll have my storage sometime in the future) and share the link here. I will add it to the list.
If I don't, pm me.
Click to expand...
Click to collapse
Hi xela,
I understand the process except for creating the 'root.tar.gz' file from a compressed image (.img or .raw) file. Do you need to extract the image file to the /root folder and then recompress with a command similar to:
sudo tar --numeric-owner -zpcf root.tar.gz ./*

Nice Topic, i've tried your first Bodhi Zip and it seems very fast and stable to me. A few bugs, but nothing major.
I'm waiting for the new Version to finish uploading

bonzer2u said:
Hi xela,
I understand the process except for creating the 'root.tar.gz' file from a compressed image (.img or .raw) file. Do you need to extract the image file to the /root folder and then recompress with a command similar to:
sudo tar --numeric-owner -zpcf root.tar.gz ./*
Click to expand...
Click to collapse
I couldn't find out how to mount those IMG files. I thought they were ext4 fs but they aren't. I tried to use dd to flash them on a drive but failure again. So to extract rootfs I install them with standard procedure (Ubuntu) and the repack roofs to tar.gz. It could be useful to find out how to directly extract rootfs, because it's the same method used by Ubuntu. With the difference that Ubuntu uses zsync to permit fast upgrade...!

xela92 said:
I couldn't find out how to mount those IMG files. I thought they were ext4 fs but they aren't. I tried to use dd to flash them on a drive but failure again. So to extract rootfs I install them with standard procedure (Ubuntu) and the repack roofs to tar.gz. It could be useful to find out how to directly extract rootfs, because it's the same method used by Ubuntu. With the difference that Ubuntu uses zsync to permit fast upgrade...!
Click to expand...
Click to collapse
I could never get it mounted as well.... Is this why your having a delay in uploading the new bodhi release?

bonzer2u said:
Hi xela,
I understand the process except for creating the 'root.tar.gz' file from a compressed image (.img or .raw) file. Do you need to extract the image file to the /root folder and then recompress with a command similar to:
sudo tar --numeric-owner -zpcf root.tar.gz ./*
Click to expand...
Click to collapse
If you can get the files from the .img files, you really dont need the zip to install it, just creat a dir with the name for the OS, then inside create a dir called root, then inside extract the .img
For the rom_info.txt file, just make the changes needed and put them on the same dir that ../root is and restart and you should be able to boot form it.

Rafase282 said:
If you can get the files from the .img files, you really dont need the zip to install it, just creat a dir with the name for the OS, then inside create a dir called root, then inside extract the .img
For the rom_info.txt file, just make the changes needed and put them on the same dir that ../root is and restart and you should be able to boot form it.
Click to expand...
Click to collapse
Unfortunately we have been unable to mount/extract anything from the image although it appears it may install via the multirom/ubuntu method

bonzer2u said:
I could never get it mounted as well.... Is this why your having a delay in uploading the new bodhi release?
Click to expand...
Click to collapse
I'm not at home right know, but in 30 minutes I'll post it

shared the latest bodhi linux version get the link in OP

bonzer2u said:
Unfortunately we have been unable to mount/extract anything from the image although it appears it may install via the multirom/ubuntu method
Click to expand...
Click to collapse
I think zip solution is the best and most "standard". When I make a zip I know it will work, because it's the final, multiROM surely compatible, version. And I can test it immediately, fix it, reflash, and try without messing the world up. I think update zips are the most user-friendly way too. But that's only MHO.

Related

[Tool][TLC]UpdatezipCreator

The Team Lambent Corrosion member presents:
UpdatezipCreator​
Some of you remember my old app UpdateThemeCreator. I've found some time to build a new app that can create updates (as zip archive flashable via recovery).
Changes/Improvements since the last version of ThemeUpdateCreator:
-new interface
-adding files to other folders than system/framework and system/app
-new algorythms
-editing update-script (saving, loading, making default etc)
-saving settings
I hope that app will work without any bugs
Changelog:
1.0.0.1
-adding update-binary to edify scripts (possibility of choosing own update-binary)
-added default scripts for edify scripts
-settings not stored in my documents
1.0.0.2
-Adding folders
-Drag&Drop
-Signing single zip archive
1.0.0.3
-Fixed bug with the wrong name of edify scripts
1.0.0.4
-Not signed archive is kept in temporary directory
-Functions library (inserting functions)
1.0.0.5
-Problem with update_ont_signed path solved (I hope so)
1.0.0.6
-Log mode
1.0.0.7
-Signing bug fixed
1.0.0.8
-Handling linux newline character in scripts
DOWNLOAD:
Rar archive - about 500 kb
Source code - about 1,3 MB - Visual Studio C#
Windows installer (source included) - about 830 kb
I'll use it tomorow for my theme
Sent from my GT-I5800 using CM 6.2 Cyanbread themed
Looks cool
Maybe you can add an option to switch between amend (all cwm versions before 3.x - what we currently use ) and edify (3.x + - like in cm7 and apollo's dual/tri boot kernel)
Then it'ld be universal
Thank you.
cdesai said:
Looks cool
Maybe you can add an option to switch between amend (all cwm versions before 3.x - what we currently use ) and edify (3.x + - like in cm7 and apollo's dual/tri boot kernel)
Then it'ld be universal
Click to expand...
Click to collapse
Yeah, it's already done
Waiting for a permission for use update-binary.
I haven't made phone databes for mounting points, I think that everyone who will be using edify scripts will change it manually in script-editor.
benzyniarz1 said:
Yeah, it's already done
Waiting for a permission for use update-binary.
I haven't made phone databes for mounting points, I think that everyone who will be using edify scripts will change it manually in script-editor.
Click to expand...
Click to collapse
I replied to your email... (same link as the email contained)
Also if you'd like to utilize the database xml from my amend2edify project, feel free to (someone is already using it in a market app).
Your tool looks nice and simple, I've considered doing something similar in the past, never got around to doing it, and now looks like I don't have to. Good work.
Also, maybe this could be moved to a more general section, as it's not restricted to Galaxy 3 devices. (Suggestion, you could add in zip signing to better support more devices.)
=]
nubecoder said:
I replied to your email... (same link as the email contained)
Also if you'd like to utilize the database xml from my amend2edify project, feel free to (someone is already using it in a market app).
Your tool looks nice and simple, I've considered doing something similar in the past, never got around to doing it, and now looks like I don't have to. Good work.
Also, maybe this could be moved to a more general section, as it's not restricted to Galaxy 3 devices. (Suggestion, you could add in zip signing to better support more devices.)
=]
Click to expand...
Click to collapse
Thanks a lot!
Zip signing is available and it's executed automatically (unless JRE is not available)
I'll post the thread in General Android Development and try to impelement your PhoneDatabase
So, app updated. Changes:
-adding update-binary to edify scripts (possibility of choosing own update-binary)
-added default scripts for edify scripts
-settings not stored in my documents
Thanks so much
Ability to sign already made update.zips(with some other tool or manually) would be nice!
EDIT:
Just tried it with folders and it wont work
aka
i can manually add all files and add path(bt tat'ld be a pain)
So how about selecting whole folders?
Drag and drop would be a nice option!
Version 1.0.0.2, changelog:
-Adding folders
-Drag&Drop
-Signing single zip archive
benzyniarz1 said:
Version 1.0.0.2, changelog:
-Adding folders
-Drag&Drop
-Signing single zip archive
Click to expand...
Click to collapse
Very nice (and fast) improvements.
I'll be sure to test this on Ubuntu under Mono sometime and lat ya know how it goes.
=]
Nice app ......nice share
nubecoder said:
Very nice (and fast) improvements.
I'll be sure to test this on Ubuntu under Mono sometime and lat ya know how it goes.
=]
Click to expand...
Click to collapse
It'd be nice, but I think that there are some changes in code neccessary.. the main: replacing executting "cmd.exe" to "adb", in ProccesStartInfo variables, so also parameteres are need to be changed (it's necessay to remove "adb" from parameters). I will probably install Linux in a few weeks on the virtual machine, so I'll have the environment to testing the code.
In the meantime, new version - fixed the wrong name of update-script for edify (changed to "updater-script" for edify, and left "update-script" for amend)
benzyniarz1 said:
In the meantime, new version - fixed the wrong name of update-script for edify (changed to "updater-script" for edify, and left "update-script" for amend)
Click to expand...
Click to collapse
aah, good update
benzyniarz1 said:
It'd be nice, but I think that there are some changes in code neccessary.. the main: replacing executting "cmd.exe" to "adb", in ProccesStartInfo variables, so also parameteres are need to be changed (it's necessay to remove "adb" from parameters). I will probably install Linux in a few weeks on the virtual machine, so I'll have the environment to testing the code.
Click to expand...
Click to collapse
What are you using adb for this app? It's just flash-able zip creation correct?
I can't think of a reason you would need to use adb for this (or how adb would be useful for this other than pushing to the phone's SD card).
Just curious, I haven't bothered to look at the sources.
=]
nubecoder said:
What are you using adb for this app? It's just flash-able zip creation correct?
I can't think of a reason you would need to use adb for this (or how adb would be useful for this other than pushing to the phone's SD card).
Just curious, I haven't bothered to look at the sources.
=]
Click to expand...
Click to collapse
ADB is used only for pushing created file to SD card, nothing more.
thanx a lot..... it helped me very much and saved me from full rom flash.....
Updated to new version. Changelong in the 1st post. Enjoy
awesome!thnx a lot!!! its really easy
edit:not tha easy as i thought can someone tell me the script i need to use to copy and maybe replace system apps?
edit1:figured it out

[EOL] [KITCHEN] ArchiKitchen - Android Kitchen [Linux]

{
"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"
}
ArchiKitchen - Brand new Android Kitchen
Commits/Changes -> https://github.com/JustArchi/ArchiKitchen/commits/master
Source -> https://github.com/JustArchi/ArchiKitchen
TODO list -> https://github.com/JustArchi/ArchiKitchen/issues?state=open
Download. Of course you can also clone my repository to stay up to date.
[SIZE="+1"]Features:[/SIZE]
Compatible with every Linux, which provides bash shell (every available distro nowadays)
Full ARM/X86 support for all included android binaries (Root, Busybox)
Dynamic permissions - A generic list of all available permissions, with proper filter for your local build and device
Dynamic symlinks - A generic list of all available symlinks, with proper filter for your local build and device. Additionaly if you're building from stock image, support for including symlinks from image itself, which results in best 1:1 copy
FS-friendly method of flashing - ROMs created with ArchiKitchen are fully compatible with every available partition, which means that they don't reformat /system partition during flashing. This is extremely important for dual-FS support for example for EXT4 and F2FS on SGS3.
Kernel repacking - Powered by mkbootimg, repacking a kernel never was easier. With one click you're extracting the kernel along with ramdisk to the proper folder, and with the second you repack it back
Deodexing - With one click you can easily deodex your whole ROM. With multi-threaded process and automatic API detection, this never was easier as well.
ArchiDroid Init.d - Forget about relying on kernel's ramdisk. Implement init.d in your ROM, not the kernel!
Latest [Bak]smali
Latest SuperSU
Latest Busybox
Latest Zipalign
And many more in the unique shell ktichen
[SIZE="+1"]Credits:[/SIZE]
@osm0sis - For mkbootimg
@Chainfire - For SuperSU
@Stericson - For BusyBox
@JesusFreke - For [Bak]smali
@bgcngm - For MTK-Tools
AOSP - For Zipalign
ArchiKitchen Tutorial
Part 1 - Setting up Linux & ArchiKitchen on Windows
https://www.youtube.com/watch?v=ktedmhWHz2M
By watching above step-by-step video, you'll learn:
1. How to install Debian on your VirtualBox machine
2. How to connect Windows with Linux through a shared VBox folder
3. How to install ArchiKitchen
4. How to create your first custom ROM, with built-in Root and Busybox
Extra information:
- You can use any virtualization method you want. I suggest using VirtualBox, as it's very easy, flexible and free virtualization solution.
- You can use nearly any Linux distro. I suggest either Debian or Ubuntu, as both of them have excellent support and are very easy to install and use, compared to some other ones. However if you feel fine in Linux environment, you can install nearly any distro you like.
Mini.iso link
Weekly Debian Testing.iso link
Installing virtualbox additions: apt-get install virtualbox-guest-dkms
Installing required tools: apt-get install zip unzip openjdk-7-jdk
Mounting a shared VBox folder: mount -t vboxsf yourName /path/to/yourFolder
Tutorials made by other developers: @bigrammy
Part 1. Prepare for linux Installation https://www.youtube.com/watch?v=aDsQTcDvSMY
Part 2. Install Linux (Ubuntu/Zorin) https://www.youtube.com/watch?v=KwnIjCXXM5Y
Part 2.5. Edit Winows bootloader to boot Linux: https://www.youtube.com/watch?v=gNpQucQxcFQ
Part 3. Work as Root Mod & Install ArchiKitchen https://www.youtube.com/watch?v=T_ad7uML8QM
Part 4. How to add your device locally to the Kitchen: http://youtu.be/YXNDcmf6GhI
ArchiKitchen Questions & Answers
Q: What is this "ArchiKitchen"?
A: A Linux-based kitchen, with a main objective of converting stock ROM drops in .img, .tar.md5 or similar formats to CWM-flashable .zip.
Q: So I can create my own custom ROM based on stock ROM with it?
A: Exactly.
Q: Is it for Linux only? Why windows is not supported?
A: Let's face it, Android is based on Linux kernel and we could call it a mobile UNIX fork. It's hard to work with Linux-based things on Windows, in fact, Windows doesn't even offer Bash (Bourne-again shell), which is absolutely core for ArchiKitchen. Working with windows is painful, for example - .img mounting. I can very easily mount any filesystem image on Linux with just one command, while doing so on Windows usually requires a massive convertion of whole image to .zip file, then extracting a single files. Also, Windows doesn't support symbolic links, and this makes it impossible to create 1:1 copy of the image "translated" to zip file. Therefore, making a Windows port would require lots of more work and solving issues, and even with that it would still cause some core features to be unavailable. However, launching Linux on Windows is very easy thanks to VirtualBox and other virtualization software, so you don't need to reformat your PC or stick purely with Linux. In fact, this is the proposed way of using ArchiKitchen - Installing a native Linux distro (suggested: Debian or Ubuntu) and then installing ArchiKitchen on it. Take a look at tutorial to see how easily you can install and run ArchiKitchen in Linux VBox.
Q: Is Cygwin supported?
A: No. Cygwin IS NOT supported and it's not planned to add such support. Reason is nearly the same as above one. However, ArchiKitchen is open-source project and I'm open for all pull requests, so perhaps somebody will add support for Cygwin in the future. Until then, ArchiKitchen is compatible ONLY with Linux, and if you use it on Cygwin you're on your own with the issues that may happen.
Q: Which phones are supported?
A: ArchiKitchen contains a local "database" of devices, which includes a kernel/modem blocks to be used. However, as long as you know the partition layour of your device (kernel block), ArchiKitchen works with every phone and every Android variant. I'm trying to make it as universal as possible, so even if your device does not exist in our local database, it should work.
Q: How can I add my own phone to the local database?
A: If it doesn't exist yet, take a look at "product" folder. Inside you can notice various devices with name based on their models. ArchiKitchen will detect your ROM's model and check inside if it exists, if it does, then some properties for this model will be loaded, if it doesn't exist, then ArchiKitchen will ask user for them. Probably the best idea is to copy one of the already available models (for example "m0" - Samsung Galaxy S3), then rename new copied folder to your model name and finally edit files inside.
Q: What is "NULL" text found for example in some MODEM files in the database?
A: Some phones have a possibility to flash modem directly from CWM, others don't. "NULL" text indicates that this model does not support flashing modem.bin, so even if ArchiKitchen finds and recognizes it, it will pop up an error telling you that it unfortunately can't be used.
Q: Where is SYSTEM block?
A: System block is not being used at all, as it's a valid partition and should be located in "fstab" file in recovery already. ArchiKitchen mounts system automatically through "mount" binary, with automatic filesystem and /system path. I consider providing a system block as something obsolete, because it's only required when you're formatting a partition, and even during flashing, a wipe - delete_recursive() function is enough. Therefore, ArchiKitchen does NOT require providing a /system block.
ArchiKitchen Troubleshooting
Q: It looks like something is wrong with zipalign command. I can notice errors like "./zipalign: No such file or directory"
A: This is because zipalign is x86 binary (32-bit), while you have amd64 (64-bit) Linux. Therefore, we must install some missing core packages to properly support x86 binaries. This will do the trick:
Code:
apt-get install lib32stdc++6 lib32z1
[SIZE="+1"]ArchiDroid Init.d[/SIZE]
ArchiDroid Init.d is an innovative method for including init.d support in the ROM itself, and not in the kernel. ArchiKitchen supports adding ArchiDroid Init.d to any Android ROM.
ArchiDroid Init.d is based on two files. A core - debuggerd hook, and a check part - simple init.d script.
Init.d script is named 00ARCHIDROID_INITD, and it only creates a special file to notify the core that init.d has been already executed, therefore it can't conflict with anything and it's completely safe.
The core is a hook for special /system/bin/debuggerd binary, which is normally called once during initial boot. Therefore, when it's called, ArchiDroid Init.d firstly waits a specified amount of time (default: 5 seconds), in case if user has already a kernel with init.d support. This is required because otherwise all init.d scripts would be executed twice - by kernel and our init.d. After specified time, if init.d is still not executed, our hook executes all scripts in alfabetical order. Lastly, when we're done, hook is executing original debuggerd binary (default: debuggerd.real) and shares the environment, arguments and everything. This is a perfect method for implementing init.d in the ROM itself, because we don't need to trust the kernel that it supports and executes init.d properly. We give it a 5 seconds to execute it, and eventually we do the job if kernel is not interested in that. This way we can support both custom kernels with native init.d support (we wait initial delay, if kernel executes init.d, all is fine and we don't have to do so), and also pure stock kernels without init.d support (we wait initial delay, kernel doesn't care about init.d, so we're executing it).
I think that such hook works far better than relying on the kernel and modyfing stock ramdisks. Also we're sure that even if user changes kernel to any custom one, we still have reliable init.d support, regardless if custom kernel supports init.d or not.
Reserved.
JustArchi said:
It's a bit quiet in here, I was expecting more noise
Click to expand...
Click to collapse
Me too!
THX for your work!!!
If i get my new Laptop next few days i will dl and test it!
Gesendet von meinem GT-I9505 mit Tapatalk 2
Harris_xx said:
Me too!
THX for your work!!!
If i get my new Laptop next few days i will dl and test it!
Gesendet von meinem GT-I9505 mit Tapatalk 2
Click to expand...
Click to collapse
Looking forward.
i really appreciate your work, like every time
In general whole kitchen needs a magic touch more or less but firstly I'll want to make it fully usable (and modern!) then eventually rework it.
As for now it's more or less up-to-date. Also added Note3 variant.
Thanks for your work and projekt!
I will download and test it with the new Galaxy Note 10.1 2014 :good: (Android 4.3)
Feel free to test it, but keep in mind that it's still work in progress .
Today I've added new experimental method for *better* handling setting up rom directory. As for now it supports only system.img in sgs format, however it automatically extracts it (if needed) from any tar/zip package, also with properly detecting cache.img. This is the main feature I was missing in original kitchen.
https://github.com/JustArchi/Android-Kitchen/commit/cf025ebf6573d23e5d2b7cfde258d9b7c36abd29
Just please don't track "wip" branch, as it's rebased often and merged into master when ready .
This is great, as I love the kitchen it is awesome that you've updated it. I'll be trying it out tonight. Thanks for your work.
Sent from my XT1032 using XDA Premium 4 mobile app
Great work :good:
Tested New device LG G2
Looks very good, thanks for updating the kitchen.
Got an error when using the kitchen:
Code:
-----------------------------------------------------------------
BusyBox is an executable file that combines tiny versions of
many common UNIX utilities. It is required for some root-enabled
applications.
-----------------------------------------------------------------
Add BusyBox (y/n)? (default: y):
Found ./system/xbin/su
Found /system/xbin
Working folder already has /system/xbin/busybox
Replace with BusyBox 1.21.1 (y/n)? (default: y):
Replacing /system/xbin/busybox
Adding /system/xbin/busybox
Error: No update-script found!
Press Enter to continue
Due to that I converted the update-script to edify.
Perka said:
Got an error when using the kitchen:
Code:
-----------------------------------------------------------------
BusyBox is an executable file that combines tiny versions of
many common UNIX utilities. It is required for some root-enabled
applications.
-----------------------------------------------------------------
Add BusyBox (y/n)? (default: y):
Found ./system/xbin/su
Found /system/xbin
Working folder already has /system/xbin/busybox
Replace with BusyBox 1.21.1 (y/n)? (default: y):
Replacing /system/xbin/busybox
Adding /system/xbin/busybox
Error: No update-script found!
Press Enter to continue
Due to that I converted the update-script to edify.
Click to expand...
Click to collapse
Actually kitchen can work only with update-script, although it converts it to updater-script when building rom.
This is on my todo but it's a bit complicated (many dependencies), so it needs major rework.
As for now I suggest avoiding conversion before final build.
JustArchi said:
Actually kitchen can work only with update-script, although it converts it to updater-script when building rom.
This is on my todo but it's a bit complicated (many dependencies), so it needs major rework.
As for now I suggest avoiding conversion before final build.
Click to expand...
Click to collapse
Thanks.
Also
1. with koush rooting theres no deamonsu in xbin, is this right?
2. when rooting the kernel is still ro.adb.secure=1 should be 0 or?
3. would be great if the kitchen adds a modded adbd in ramdisk/sbin (to get root directly in adb)
Again thanks
Perka said:
Thanks.
Also
1. with koush rooting theres no deamonsu in xbin, is this right?
2. when rooting the kernel is still ro.adb.secure=1 should be 0 or?
3. would be great if the kitchen adds a modded adbd in ramdisk/sbin (to get root directly in adb)
Again thanks
Click to expand...
Click to collapse
1. That's right, koush doesn't have direct support for su daemon.
2. User should be able to modify this, on todo with many other things...
3. I think we can do it, soon .
JustArchi said:
1. That's right, koush doesn't have direct support for su daemon.
2. User should be able to modify this, on todo with many other things...
3. I think we can do it, soon .
Click to expand...
Click to collapse
Sounds good
---------- Post added at 03:50 PM ---------- Previous post was at 03:44 PM ----------
Donation made
4T106212CC7164407
i worked with planty firmwareswith the latest kitchen for my devices but anytime the SuperSu after installation was saying something like "there is a SuperSu, but not Supersu binary installed". that thing was gone after i flash the SuperSu update binary. Does your kitchen gonna give me SuperSu from the start (instalation)?

[Mini-Howto] Layers Management via Init.d script

Like many of you, I like to keep my Android system rootless and true to stock as much as possible. However, I like to be able to enjoy the native support of layers for better look n feel. I wrote the script attached to help me with it however, it doesn't come easy without root access. There are some work cut out for you, read below.
Prerequisites:
Have extracted theme from layers theme app from Play Store. No, I'm not talking about the main theme app which is used by Layers Manager. Rather, it's the apks that go into the /vendor/overlay. I tried to extract respective apks out of the main one without using Layers Manager. However, my attempts yielded no success as I'm getting FCs all over, so I must be missing something. I current have a Nexus 9 which is rooted with Layers Manager, I use N9 for testing out and bring the /vendor/overlay/*.apk onto my N6P under /sdcard for my script to process. If you know of a better way, by all means share.
Of course, kernel which support INIT.D.
TWRP installed for root access via recovery, a MUST.
Busybox installed via flashable zip
Install:
- Download the script attached
- Rename .txt to .sh
- Have all extracted themed apks in one directory. For instance, I like fa and art layers, so my directory on sdcard as such /sdcard/0flash/layers/fa/fa_*.apk
- Change up the first few lines to match your environment
- Boot into twrp, mount /system if needed
- Drop the script into /system/etc/init.d
- chmod 755 /system/etc/init.d/01layersmanager.sh
- Create a file named ".current_theme" in /sdcard/
- In the above file (.current_theme), put the name of theme you want init.d to install. Example, if I want to install "fa" then I'll just have a line of text fa in it (same goes to art, coalesce,etc). IMPORTANT: no trailing new line.
- Reboot and test it out
- If theme successfully installed, you'll see it.
- Also, the /sdcard/.current_theme file will be updated with "current" to avoid theme installation on next reboot if you don't want to install new themes.
Troubleshoot:
See /sdcard/debug.txt for info. If you want additional information dumped, edit the init.d script to echo out more.
O bio hnki
vboyz103 said:
Like many of you, I like to keep my Android system rootless and true to stock as much as possible. However, I like to be able to enjoy the native support of layers for better look n feel. I wrote the script attached to help me with it however, it doesn't come easy without root access. There are some work cut out for you, read below.
Prerequisites:
Have extracted theme from layers theme app from Play Store. No, I'm not talking about the main theme app which is used by Layers Manager. Rather, it's the apks that go into the /vendor/overlay. I tried to extract respective apks out of the main one without using Layers Manager. However, my attempts yielded no success as I'm getting FCs all over, so I must be missing something. I current have a Nexus 9 which is rooted with Layers Manager, I use N9 for testing out and bring the /vendor/overlay/*.apk onto my N6P under /sdcard for my script to process. If you know of a better way, by all means share.
Of course, kernel which support INIT.D.
TWRP installed for root access via recovery, a MUST.
Busybox installed via flashable zip
Install:
- Download the script attached
- Rename .txt to .sh
- Have all extracted themed apks in one directory. For instance, I like fa and art layers, so my directory on sdcard as such /sdcard/0flash/layers/fa/fa_*.apk
- Change up the first few lines to match your environment
- Boot into twrp, mount /system if needed
- Drop the script into /system/etc/init.d
- chmod 755 /system/etc/init.d/01layersmanager.sh
- Create a file named ".current_theme" in /sdcard/
- In the above file (.current_theme), put the name of theme you want init.d to install. Example, if I want to install "fa" then I'll just have a line of text fa in it (same goes to art, coalesce,etc). IMPORTANT: no trailing new line.
- Reboot and test it out
- If theme successfully installed, you'll see it.
- Also, the /sdcard/.current_theme file will be updated with "current" to avoid theme installation on next reboot if you don't want to install new themes.
Troubleshoot:
See /sdcard/debug.txt for info. If you want additional information dumped, edit the init.d script to echo out more.
Click to expand...
Click to collapse
Yt? Bird :
Sent from my Nexus 6P using XDA-Developers mobile app

[SCRIPT FOR STOCK] AutoScripts

AUTOSCRIPTS​
Hi Everybody!
That's my first work for the Moto X Style & Pure (ported from my work on Moto X Play) so I hope You'll appreciate it.
It's simply an automatic flash script, just in case You won't have to remember all these shi*ty codes.
It's personally created and tested by me, so I'm sure it works, but I don't assume any responsibility for damaged devices.
!!REMEMBER! I DON'T PROVIDE ANY STOCK ROM!!
My script (as you'll see) works both with Ubuntu (and derivates), Fedora (yes, both with dnf and yum installer), ArchLinux (and derivates) and Windows.
If you have any question/suggest feel free to post it here and if I helped you feel free (too) to hit thank and maybe buy me a coca (I don't really like alchoholic drinks).
HOW TO​1) Download it from THE DOWNLOAD TAB.
2) Put on your Home Folder (or anywhere You want).
3) Unzip it (You'll see a file called flash.sh, for linux users, and some files for windows users).
4) Open a terminal and cd the folder where you have saved flash.sh.
5) Copy the code below (for Linux) or simply double-click on flash.bat (for Windows. It doesn't request administrator privilegies).
Code:
$ chmod +x flash.sh
$ ./flash.sh
6) Follow the instructions on screen.
7) Enjoy.
BUGS​All the Scripts is tested personally by me before any upload so I'm sure they'll work. Anyway if you encounter any problems please post it in bug's tab HERE!
VERSIONS​AutoScript Linux
First Version
Added support for ArchLinux (both with pacman and yaourt)
BugFix
AutoScripts Windows
First Version
Added ability to relock the device
BugFix
F.A.Q.​1) Why it doesn't work with device XYZ?
It's because my AutoScripts is developed only for Moto X Play, Pure & Style.
2) The Scripts have only formatted my device. You piece of sh*t!!1!11!
Have you downloaded the ROM and put the files on the Flash's folder? You can find it HERE FOR STYLE and HERE FOR PURE.
3) When do you upload an update?
I'll do it as soon as possible. Don't hassle me with that unuseful quest please.
4) Thank man, your work is fantastic!
Please hit thank button, don't write a post for that.
5) I've read your work and the codes is fuc*ing ugly and long.
I know. If you have a suggestion please tell me and I'll see if i can do anything.
XDA:DevDB Information
AutoScripts, Tool/Utility for the Moto X Style (Pure)
Contributors
ScardracS
Version Information
Status: Stable
Current Stable Version: 2016-10-04
Created 2016-10-04
Last Updated 2016-10-25

[LINUX][FREE] SuperR's Kitchen (v1.2.1.5 - 01/08/2022)

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

Categories

Resources