yashsingh1/xdaforums huggingface dataset:
[SuperR Kitchen] _that:
Actually TWRP's limit should be 4 GB, the same as the "classic" ZIP file format, because somebody fixed/improved minzip for TWRP a while ago. But to install a ZIP > 2 GB, you need an update-binary in the zip that was compiled with the fixed minzip.

Also, my CM13 build was around 340 MB, what kind of bloat are you packing into your ROMs? ;)
[SuperR Kitchen] minz1:
it's not bloat; it's features. get your facts right
[SuperR Kitchen] SuperR.:
Nice, thanks :) Any idea how to get one of these update-binaries for use in the kitchen aside from compiling one?

Stock roms are pretty huge compared to cm and derivatives. I have seen stock roms larger than 2GB (Samsung I'm looking at you).
[SuperR Kitchen] Chrisis42069:
I love this idea. I an dying to try it. Currently im running Linux mint 16 as a host with multiple virtual machines. After trying to install jdk8 and failing,I think I found another way I have to try later, but I decided I'd try the Ubuntu.iso. it looked fine as it booted and then after the boot animation finishes, the screen goes into this crazy multicolor rainbow mess. Any ideas?
[SuperR Kitchen] SuperR.:
Update to Mint 18 and you should be good. You are running a 3 year old OS. Default jre is 8 in Mint 18 so it will likely fix your problem.
[SuperR Kitchen] _that:
Compiling is the usual way to obtain binaries. :)
[SuperR Kitchen] somadsul:
Hi does anyone solve this I am getting error while building rom

7-Zip [32] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21
p7zip Version 16.02 (locale=en_US.UTF-8,Utf16=on,HugeFiles=on,32 bits,4 CPUs Intel(R) Core(TM) i3-3120M CPU @ 2.50GHz (306A9),ASM)

Scanning the drive:
618 folders, 3473 files, 2292306565 bytes (2187 MiB)

Creating archive: KING_ROM_S5_G900H.zip

Items to compress: 4091

Scan WARNINGS for files and folders:

vendor : No more files
----------------
Scan WARNINGS: 1
[SuperR Kitchen] SuperR.:
Indeed :) However, I found the one [MENTION=2605798]nkk71[/MENTION] posted here and will add it to the kitchen in the next update.

There is nothing to solve. The command the kitchen uses to zip the files includes vendor, which you don't have in your rom. The warning is because we said to zip it and it does not exist. It will be skipped without issue.
[SuperR Kitchen] somadsul:
But my rom is having vendor folder, then why it is not found to kitchen?

Does script look inside folder that any file is missing? But there is no chance for missing any file because i have never changed anything except some apps then why its not zipped?

I have tried manuly zip but there is also not zip success, might something other problem cause error.
[SuperR Kitchen] SuperR.:
Yes. You could have one or more files that don't have permissions to be zipped. The kitchen usually handles these files but it is possible it was not able to get them all for some reason. You will need to find the problem file/files and either remove them if they are not important or adjust the permissions so they can be zipped.
[SuperR Kitchen] minz1:
[MENTION=5787964]SuperR.[/MENTION] one of the users of my ROM tried the version with phh's super user. it works, but there is an apk file that needs to be included. it's gotten from the google play store, but i just stuck it in a "phhsuperuser" folder and put it in system/apps/. it seems to work fine.

http://xdaforums.com/android/software-hacking/wip-selinux-capable-superuser-t3216394

^^ link again just in case
[SuperR Kitchen] SuperR.:
v2.1.0.8 (Donate version)

Changes:

Replaced the update-binary with one that supports flashing zip files larger than 2GB in TWRP v3.0.0-0 and higher (Thanks to [MENTION=2605798]nkk71[/MENTION] for creating the TWRP patch and providing a pre-compiled update-binary. Thanks to [MENTION=4878287]_that[/MENTION] for pointing me in the right direction).

Added compatibility for other flashable root zips such as phh's superuser.

Changed name of root directory in rom from supersu to rootzip.

Updated SuperSU to v2.78.

v1.0.9.7 (Standard version)

Changes:

Replaced the update-binary with one that supports flashing zip files larger than 2GB in TWRP v3.0.0-0 and higher (Thanks to [MENTION=2605798]nkk71[/MENTION] for creating the TWRP patch and providing a pre-compiled update-binary. Thanks to [MENTION=4878287]_that[/MENTION] for pointing me in the right direction).

Added compatibility for other flashable root zips such as phh's superuser.

Changed name of root directory in rom from supersu to rootzip.

Updated SuperSU to v2.78.

NOTE: If you would like to use something besides SuperSU, add the flashable zip to the /kitchen/tools/root/root_zips/ directory. Unroot if you already rooted, and root again. You will be asked which zip you want to use. That's it :)

NOTE2: Regarding phh's superuser apk, I have not included it so you will need to add it to your rom if you want it included or tell your users they need to install it from the play store after installation.

NOTE3: SuperSU v2.78 which is now included in the kitchen, is the first version released by the new owners.
[SuperR Kitchen] minz1:
Would you add a feature to automatically add apks to system/app/? I wouldn't care if it were on the donate version only as I'm going to donate soon anyway :D
[SuperR Kitchen] bcrichster:
Already in donate version

Sent from CM12.1 *N9515*
[SuperR Kitchen] minz1:
oh really? i saw an apk manager but wasn't sure if it added it to the rom
[SuperR Kitchen] SuperR.:
The apktools plugin allows you to decompile an apk already in your rom and recompile it. It does not add apk files to system/app as you are requesting.

Sorry I am a bit confused. How do you see this addition working? Do you want to add a bunch of apk files to a folder and have the kitchen create the proper directory structure in system/app? Or, are you wanting a file chooser to pick an apk and then have it magically added to system/app? Or am I missing your point entirely?
[SuperR Kitchen] not-i:
[MENTION=5787964]SuperR.[/MENTION] I can confirm the binary you have added to kitchen for roms +2gb works. Yet to update kitchen but I added the binary to my rom yesterday and booted no problem :)
[SuperR Kitchen] SpasilliumNexus:
If he does mean this, what I did was create a separate folder, with subfolders grouped of different additions, for example:

\---Stock ROM Enhanced for MPXE
|
\---[URL="http://pastebin.com/GL2PzwFu"]01-google_moto_apps[/URL]
|
\---[URL="http://pastebin.com/key7J8nG"]02-other_android_apps[/URL]
|
\---[URL="http://pastebin.com/Yu4745ev"]03-system_mods[/URL]
|
\---[URL="http://pastebin.com/bAxzjvgP"]04-viper4android_mod[/URL]
|
\---[URL="http://pastebin.com/HMSjQGxk"]05-adreno_drivers[/URL]
|
\---[URL="http://pastebin.com/8Jr1yUzW"]06-zip_output_inclusions[/URL]

each which contains everything I want in my ROM, matching the ROM's layout. Then I just copy/paste the system folder in each, to the root of my project.

And if I want to start with a clean ROM base, I use the custom bloat option to undo everything I merged from those folders: http://pastebin.com/kQWTQCUp

Hopefully this post makes sense.
[SuperR Kitchen] minz1:
The former. I'm going to be adding multiple apps, and that would be pretty useful. The latter would also be useful as well :D
[SuperR Kitchen] scrappy610:
[MENTION=5787964]SuperR.[/MENTION] donation sent. Thanks for your work.

confirmation # 1161-2391-0316-6341

gitlab user: scrappy610
[SuperR Kitchen] SuperR.:
Ok, I will make a plugin that does things related to copying files to system. It may take a while since there are several considerations based on Android version for directory structure. I will post when I have something put together :)

Added, thanks :)
[SuperR Kitchen] goran85:
Why dont the Plugins links on gitlab work on the first page?
[SuperR Kitchen] Chrisis42069:
thank u will upgrade tomorrow. Appreciate the support. Keep up the great work:good:
[SuperR Kitchen] goran85:
[MENTION=5787964]SuperR.[/MENTION]

Made my donation :)

01P262072N261414E

github user: unweptcloud
[SuperR Kitchen] SuperR.:
Plugins are for the donate version only.

Thanks :) However, you need a gitlab.com username, not github. Once you send it I will add you.

edit: never mind. I found you with your email. You have been added :)
[SuperR Kitchen] goran85:
Sorry, gitlab user: goran850730

Thx for the quick response
[SuperR Kitchen] spiderjuka:
Rooting problem.

Hello.

I built first own rom (for galaxy S5) based on your kitchen. It is very nice and good tool to do it.

It is working pretty well without only one things:

One application after flashing rom doesn't work in case new rom is rooted at your kitchen. This application is for watching TV "nc+ go".

There is only one way to run this application:

1. Make rom without root and flash it via TWRP, install nc+ go.

After that flash SuperSu.zip also via TWRP .

My question is what is difference between rooting rom inside your kitchen and standard rooting rom by flash SuperSu.zip via TWRP? Why application doesn't work when I use root at your kitchen?

Second question is if it possible to put in your kitchen additional mods as zip files which will automatically install during flashing rom at TWRP?

Thnak you.

Best Regards.
[SuperR Kitchen] SuperR.:
I hope you saw my edit last night, you were added to the repo :)

There should not be any difference with flashing SuperSU from inside the rom or manually from TWRP. If you have issues with root, you should post on the SuperSU thread.

You can add any flashable zip to your ROM as long as it uses an update-binary instead of an updater-script when it flashes. Use the same syntax as SuperSU and Busybox to add it to your updater-script.

New Plugin for the donate version :)

Add/Remove Files

by [MENTION=5787964]SuperR.[/MENTION]

Add all apk files from a directory

Choose apk to import

Choose directory structure to import

Delete files from your ROM based on directory structure

NOTE: To use "Choose directory structure to import" and "Delete files from your ROM based on directory structure", your directory must be set up as the following example:

your_directory_name/system/anything_you_want
your_directory_name/vendor/anything_you_want
your_directory_name/cache/anything_you_want
your_directory_name/hidden/anything_you_want
your_directory_name/boot.img

The above is only an example. You can add anything you want as long as there is a "system" directory inside another directory. When choosing the directory, choose your_directory_name instead of system or it won't work. Think of the directory structure exactly like the kitchen ROM directory. When you import directory structure, your directory will be copied into your ROM directory and files will be overwritten if they already exist. When you remove a directory structure, you will choose your_directory_name again and the plugin will remove the same files it finds from your ROM directory.

Usage:

In the kitchen main menu, choose Misc Tools > Run a plugin > add_remove_files

[MENTION=5083335]Spasticdroid[/MENTION] - The remove files based on directory structure option should save you the trouble of creating a bloat_custom file when you want to remove the files you added :)
[SuperR Kitchen] :
New owners: Cheetah Mobile :rolleyes:
[SuperR Kitchen] SuperR.:
Coding Code Mobile Technology LLC (CCMT) is the new owner. Here is Chainfire's post about it for anyone who is not familiar.

I don't want this thread to turn into a discussion about this, but as far as I can tell there is no evidence the new company is bad or the new SuperSU is bad. However, there are lots of people assuming it is bad and posting all kinds of bad things about the change in ownership. Only time will tell, and we have other options if we choose to use them. SuperSU is still the easiest and the most compatible root option. For now, it will stay in the kitchen unless/until there is a reliable source showing why it should not :)
[SuperR Kitchen] salwan1996521:
please some one tell me how can I download the latest version :)

please some one tell me how can I download the latest version :)
[SuperR Kitchen] _that:
git clone https://bitbucket.org/superr/superrs-kitchen.git

(source: first post in this thread - try reading it)
[SuperR Kitchen] chevycam94:
I was referred here by a fellow developer. Im not new to Linux scripting, but for SOME reason, this script fails to work.

I extracted it into its own folder, and opened a terminal from within that folder. Ran the command "./superr" but all it does it flash blank really fast, resets the terminal to a single line (clear command basically), and thats its. It never actually runs or anything.

Ran on a 100% clean install of Linux Mint 18 in a VM (under Windows 10). I can even add the command "read –n1" just above the first banner() call and it will run that just fine, but as soon as you pass the read command, it does the same behavior, and skips everything, cleans the terminal, and exits (almost instantly).

Any clue as to what is going on?

UPDATE: It runs on Ubuntu 12.04, but not on Linux Mint. Weird. Whatever. But there is a problem. liblz4-tool doesnt exist anymore, and I have found no suitable way to replace it with something similar that will work. Using the built-in downloader in the script, it asks for sudo permissions, then to download, then permissions, and repeats forever, never actually TRYING to download anything.
[SuperR Kitchen] SuperR.:
These issues are why I created Ubuntu4Kitchen. If you are not able to satisfy the dependencies in another Linux distro, I suggest using the one built for the kitchen :)
[SuperR Kitchen] NYCHitman1:
[MENTION=5787964]SuperR.[/MENTION] Disregard.
[SuperR Kitchen] JonathanRAZ:
Delete
[SuperR Kitchen] beta.0:
[MENTION=5787964]SuperR.[/MENTION] Can I use this tool to build roms for Amlogic Android devices?

I'm trying to rebuild a ROM for MXQ Pro S905 but the system partition is limited to 1024MB and I can't figure out how to increase the size. I'm thinking maybe this kitchen can help me get the job done?

Does anyone know where partition sizes and offsets are stored in full aml_upgrade_package.img firmware files? I know I'll have to do some hex to binary conversion to recalculate offsets, shouldn't be a problem as long as I can find out where each value is stored.
[SuperR Kitchen] SuperR.:
Probably, but I have never tried. Let us know :)

The kitchen will not help you re-partition your device. I am sure there are guides, but be careful.

Seems like you need to get a hold of the AMLogic Customization Tool to extract the partitions from the aml firmware package. Then the kitchen can help you make roms.
[SuperR Kitchen] beta.0:
I'm downloading Ubuntu4Kitchen now. :) I will give it a shot soon and let you guys know for sure!

Forgive my ignorance on the topic, but I was thinking there is something similar to the cmdline in RockChip firmware (parameter.txt in that e.g.) which specifies the partition sizes and offsets. All of the guides and tools I have found are for working directly on the device and this could work in theory by dumping the system partition afterword resizing and then repacking with AML Customization Tool, but all these guides are for either phones, Mediatec or RockChip family SoC.

I've been using the customization tool for a while now. It's not perfect yet, a beta I think but it's still very handy to have. It does actually have a section to change the partition size but it's just random gibberish instead of partition labels, sizes and offsets for AML S905+ roms (tool needs updating). So where does it try to read that info from and where should it be reading it from? The bootloader? Maybe it's locked?

With certain roms you can only put up to 1024MB of data in the system partition or the repack will fail. You can see in the log it's creating a 1024MB partition even if you have over 1024MB of data in the folder:

Aml_make_ext4fs.exe -l 1024m -s -a system ./tmp/level1/system.PARTITION ./tmp/level2/system/

With other roms if I go over 1024MB this is what's usually logged:

Aml_make_ext4fs.exe -l 1280m -s -a system ./tmp/level1/system.PARTITION ./tmp/level2/system/

I'll bake system and boot in your kitchen tonight or tomorrow and see how that works out.
[SuperR Kitchen] chudy_85:
I have problem with cust file for mate7. I try added pre-installed app but they can install.

I use this command to install:

ui_print("Installing Cust... ");

mount("ext4", "EMMC", "/dev/block/platform/hi_mci.0/by-name/userdata", "/data");

delete_recursive("/cust");

package_extract_dir("cust", "/cust");

symlink("/cust/hw/eu", "/data/cust");

symlink("/cust/preinstalled/public/app", "/data/dataapp");

symlink("/cust/preinstalled/public/lib", "/data/datalib");

symlink("/cust/preinstalled/public/lib64", "/data/datalib64");unmount("/userdata);

That same I have error when try unmount system and try install xposed added

This it's for xposed:

ui_print("Installing Xposed v86 ");

package_extract_dir("xposed", "/tmp/xposed");

run_program("/sbin/busybox", "unzip", "/tmp/xposed/xposed86.zip", "META-INF/com/google/android/*", "-d", "/tmp/xposed");

run_program("/sbin/busybox", "sh", "/tmp/xposed/META-INF/com/google/android/flash-script.sh", "dummy", "1", "/tmp/xposed/xposed86.zip");

send from ? if I help you you can buy me ?
[SuperR Kitchen] SuperR.:
The kitchen will not help with partition resizing. Perhaps there are other threads that can help. Good luck :)

You are mounting /data, but trying to delete from and extract to /cust. Try mounting /cust if it is a partition. If it is not a partition but rather a directory under /data, then you need to extract cust to /data/cust. This is not a kitchen issue however.

Official Xposed framework cannot be flashed from within the rom. You can only flash the unofficial systemless Xposed using this method. This is also not a kitchen issue.
[SuperR Kitchen] albertmurcia:
Any guide for kernel permissive

Enviado desde mi SM-T805
[SuperR Kitchen] Tkkg1994:
Yes building custom kernel ?

Sent from my SuperMan powered SM-G930F
[SuperR Kitchen] Mysteryagr:
[MENTION=718594]super[/MENTION]R

How I can get the right symlinks? Kitchen only make set metadata and leave symlink part empty.
[SuperR Kitchen] SuperR.:
Send a link to the firmware you are starting with so I can take a look.
[SuperR Kitchen] Mysteryagr:
Here it is

http://bit.ly/2cl3XLA

Btw I should provide some info.. the system.img is a simg, when I try to extract it via kitchen it fails, although ImgExtractor.exe can extract it and it says that there is 92 symlinks inside system.img

To extract this firmware using your kitchen I have to convert it from simg to raw image first, then unpack it using kitchen, this works, however no symlinks are written to the updater-script when I try to build the rom.
[SuperR Kitchen] SuperR.:
I did not have any trouble extracting the firmware in the kitchen. My guess is that you are using the pre-built binaries from the kitchen repo in a system that is missing dependencies to run them properly. I suggest you either figure out how to satisfy the dependencies for building the binaries from source on your machine, or try a different Linux distro. May I suggest Ubuntu4Kitchen? :)

In case that is not an option for you, I have attached the symlinks file the kitchen created from your firmware. Extract it to the 00_project_files directory of your ROM and change perm type in the kitchen to set_metadata (even if you are already using set_metadata). It will populate the new symlinks into your updater-script.
[SuperR Kitchen] Mysteryagr:
I guess you're right, I'm using kitchen on lubuntu because my laptop is single core processor with 1 GB ram, Ubuntu runs so slow on it.

Thanks a ton for symlinks, that was really helpful :D
[SuperR Kitchen] stang5litre:
Works fine on Ubuntu here. [emoji48] [emoji106]

Sent From My stang5litre Edition 5.0 s7e
[SuperR Kitchen] boester:
[MENTION=5787964]SuperR.[/MENTION]

Donation is on its way.

My Gitlab Name: Boester

Thank you
[SuperR Kitchen] matamata15c:
Hi I have a question as to again convert system.img system.new.dat ? Thank you

Enviado desde mi hi6210sft mediante Tapatalk
[SuperR Kitchen] engineerchad:
I donated today, my gitlab ID is engineerchad.
[SuperR Kitchen] orgulloso4202:
[MENTION=718594]super[/MENTION]R I have installed Ubuntu4Kirchen in a virtual box. But I can extract anything from my S7 edge. Not sure if not support? I'm also new at this and thus will be my first time trying to build my own rom. I also couldn't make a share folder work between virtual box and my windows 10. To import the system.ext4.img and the cache.ext4.img , boot.img. Thanks and if you have any advice or how to build a rom post, videos, etc that would make this easier for me I would appreciate it. Like I mentioned I'm very very extremely green, but eager to learn. One last thing, does the donated version also come in Ubuntu4Kirchen?
[SuperR Kitchen] SuperR.:
Unfortunately I can't help with this as I do not use a virtual machine. It sounds like VirtualBox may be having trouble finding your device. I am sure there are threads on how to get VirtualBox to recognize Android devices and once that is set up you should be able to extract your images from your device using the kitchen. I am sure there are also threads about sharing storage between VirtualBox and Windows. I would start there.

Alternatively, you could set up a dual-boot with Windows and Linux so you can choose which to boot when you power on your pc. Better yet, ditch windows altogether. There are threads for both of these too.

Neither of the kitchen versions come pre-installed in Ubuntu4Kitchen. There is an icon on the desktop and when you double-click it you will be asked which version you want to download/install.

Good luck :)
[SuperR Kitchen] bcrichster:
(In my honest Opinion) Dualboot is the way to go.. That way you get everything of both worlds and has been a blessing in itself [emoji41]

Sent from CM12.1 *N9515*
[SuperR Kitchen] orgulloso4202:
Thanks, will look into dual boot.
[SuperR Kitchen] scrappy610:
Did you enable the guest services in virtual box? Without enabling that you wont be abke to access your shared folder. As for the usb you have to select it in virtual box settings basically giving it permission to use the ports. I've used vb, dual boot and finally i just installed mint on my laptop as the only os. You will get more features and less headache with a dual boot until you get used to Linux. After that, you'll want to get rid of Windows too ha.
[SuperR Kitchen] orgulloso4202:
Thanks will double check when I get home.
[SuperR Kitchen] JamFan05:
I'm trying to build Nougat for my Nexus 6P. I'm trying to build a full ROM zip using adb shell and keep getting the error saying check partition size "something went wrong". I used the kitchen several times before with marshmallow and never had this problem. Any suggestions?
[SuperR Kitchen] SuperR.:
I am not sure why you are getting an error. I may need to make some changes for finding the partition sizes while running Nougat. For now, you can enter it manually. According to the angler device tree found here, the system partition size in bytes is 3221225472 :)
[SuperR Kitchen] DragonXz:
SuperRs Really A Great Tool

This Tool Helped Me Doing Such A Work That I Couldn't Imagine I Would Do

It Made A Great Impact And Made It Easier For Beginners And Learners :D

Really I Appreciate Your Hard Work :cool::laugh:

Thanks Bro From Egypt