yashsingh1/xdaforums huggingface dataset:
[SuperR Kitchen] jinconstantine:
Have you tried a clean install like suggested

As stated by Master SuperR. in previous post it works with java 7 and i use java 8 and it also works fine :)

I switched it to java 8 and DID NOT use auto just select 1 or 2, and just switch back at will whenever necessary :)

type in terminal:

sudo update-alternatives --config javac

There are 2 choices for the alternative javac (providing /usr/bin/javac).

Selection Path Priority Status

------------------------------------------------------------

* 0 /usr/lib/jvm/java-7-openjdk-amd64/bin/javac 1071 auto mode

1 /usr/lib/jvm/java-7-openjdk-amd64/bin/javac 1071 manual mode

2 /usr/lib/jvm/java-8-openjdk-amd64/bin/javac 1069 manual mode

Press enter to keep the current choice[*], or type selection number:
[SuperR Kitchen] SuperR.:
v1.0.4.1

Changes:

Initial support for deodexing N Preview roms.

Updated oat2dex.

NOTE: Some things will need to be changed once we know the api level of N and the version number, but this should work for all the preview versions. I have not tested a rom that uses this deodex method so use at your own risk. However, the deodex process goes through with only a few errors (Maps, Youtube, Photos) so hopefully it will work :)
[SuperR Kitchen] asc1977:
Only want to report that on V1.0.4.0 the new oat2dex also not working 10ü% on samsung S6 roms. I see you updated now oat2dex again inV1.0.4.1

Is this right? Than i try again on this version.

Btw i choose everytime option1 for deodexing in your tool
[SuperR Kitchen] SuperR.:
Yes, oat2dex was updated again in v1.0.4.1. It adds things needed for N deodexing.

Have you tried smali/baksmali method?
[SuperR Kitchen] asc1977:
No because didnt work any time. Only oat2dex was working. But i can give it a try also mext time if i update base. I let you know
[SuperR Kitchen] ambasadii:
delete
[SuperR Kitchen] sparks15:
hi will you add support for preview N_ i got this when trying make rom,zip

ERROR:

Either your kernel does not support selinux, or

the kitchen can't find what it needs. If you are sure

your device supports selinux, you can copy the file_contexts

file from the ramdisk to your 00_project_files directory

to use this feature.
[SuperR Kitchen] jinconstantine:
What linux are u using
[SuperR Kitchen] xxRaynexx:
Thank you for the great tool. This is by far the best kitchen I've used. I have made many personal changes to the Nexus 6 using it. Recently I ran into a problem. I tried to flash my already built system.img created in your kitchen to a different N6 with the same build and it sticks at the google boot screen. I built the symlinks with adb from a N6 with the exact same bootloader, radio, etc. The only difference I can find is being rooted. Any ideas how I can flash the same system.img to multiple devices?
[SuperR Kitchen] toheedasad:
How Can I Tweak My Kernel Using This Kitchen, How Can I Change My Kernel From Enforcing To Permissive?
[SuperR Kitchen] :
You may have to compile from source especially if it's a Samsung kernel
[SuperR Kitchen] toheedasad:
Thank you for your reply sir, so you mean to say i have to compile a rom from this tool and use another tool to compile the kernel?

If yes, then howa can i link both of them together?

Can't i just extract the stock kernel and tweak it?
[SuperR Kitchen] bcrichster:
Umm.. No. This tool does not "compile" anything, it makes flashable zips and allows minor modifications.

Not really able to tweak stock kernels much anymore, other than adding init.d and making insecure.

Yes, you'll need to compile another kernel some other way
[SuperR Kitchen] :
To compile a kernel you need the source code. I don't know if your kernel can be made permissive with ramdisk edits or not (probably not) but this thread is first for a rom kitchen and I think this is better discussed in a different thread myself
[SuperR Kitchen] toheedasad:
Thank you sir for your reply, sir can you help me with the kernel thing i said before, like any guide or if you can help me personally?

---------- Post added at 01:27 AM ---------- Previous post was at 01:27 AM ----------

Ok thank you sir
[SuperR Kitchen] osm0sis:
[MENTION=5787964]SuperR.[/MENTION], for your next version I've got a new busybox zip up that fixes all known issues with my builds. :)
[SuperR Kitchen] SuperR.:
I am guessing here, but maybe you need to also flash the corresponding vendor.img and boot.img. The root could also be causing issues if it is Marshmallow.

However, why not create a rom using sparse_dat or set_metadata instead of a system.img? The kitchen can unroot your rom and add SuperSU.zip to be flashed at the end.
[SuperR Kitchen] sparks15:
ubuntu 15.10
[SuperR Kitchen] andy_zhang:
i unpack my boot.img ,then repack ,flash my lgg3,but ,bootloop.
[SuperR Kitchen] SuperR.:
v1.0.4.2

Changes:

Updated to the newest Busybox installer by [MENTION=4544860]osm0sis[/MENTION].

Added support for extracting system.img, vendor.img, and boot.img from official Nexus firmware tgz.
[SuperR Kitchen] andy_zhang:
[MENTION=5787964]SuperR.[/MENTION]

vs985 China user
[SuperR Kitchen] syztemlord:
Hi guys,

I'm new at ROM mods via a kitchen but I've been trying this the last few days. I just have a question regarding packing the ROM. I'm building as sparse but when it build I only have install directory, META-INF, boot.img, file_contexts, system.new.dat, system.patch.dat and system.transfer.list

Is there an option to pack with recovery, logo, bootloader images etc?

I've had a look through the options but can't seem to find anything.
[SuperR Kitchen] Silassi1:
After deodexing and modding certain jars, is there a way to reodex with this tool? Thanks
[SuperR Kitchen] bcrichster:
No. You'll have to use something else like LuckyPatcher.apk and reodex each one separately
[SuperR Kitchen] Silassi1:
Thanks
[SuperR Kitchen] SuperR.:
LG has some strange things. You may need to bump it. As stated in post #2, the kitchen has support for open_bump.py. Just download it, put it in /kitchen/tools directory, make it executable, and unpack/repack again. I am not sure if it will fix your issue but look into special requirements LG boot.img needs to boot properly and you may find your answer.

No need to double post. It is only irritating and not helpful.

There is currently not support for this. Most roms do not include these images.

What device is giving you this error? I have only unpacked the Nexus 5X and did not have this issue.

In the future, please read post #4 to get an idea of the types of things I need to know to help you. Both OS and device have been on this list since the beginning along with many other things. Asking you each question one by one is time consuming and I just don't have the time to give :)
[SuperR Kitchen] andy_zhang:
I know lg phone Need bump, but....,bootloop, I use other tool to unpack boot(your kitchen repacked ), prompt ERROR, in file no ramdisk.

vs985 China user
[SuperR Kitchen] SuperR.:
I was able to unpack/pack the boot.img you uploaded with no issues. The kitchen also bumped it with no issues. If you continue to have issues either tell me how to fix it or use another tool. No time to figure everything out for you.
[SuperR Kitchen] supercowz:
hello superr, first thanks for your great tools

i succesfully cooked rom for Letv x900 phone (great phone) with your kitchen and official rom zip, working great.. no problem

now if i extract the rom (system.img.. etc) from the phone manually or with superr and phone booted to twrp ... then build rom zip, the zip file is 18mb (but system.img or system folder is the right size)

do you know where to dig to fix this problem ?
[SuperR Kitchen] SuperR.:
It could be a couple things.

1) You and the kitchen are not managing to get the system.img from the device correctly.

2) You used sparse_dat or raw_img perm type and did not get the system partition size correct.

My guess is #2. If this is the case, make sure you get the correct size of your system partition. Worst case you enter it manually.
[SuperR Kitchen] SuperR.:
v0.9.0.6

Changes:

Lollipop deodex change that allows maps to complete on XT1526, and hopefully others

Changes to set_metadata

Cleaned up dependency check
[SuperR Kitchen] lalitoSGSII:
No flash SM-N910F trltexx

Hello everyone. Might Superr trltexx support. SM-N910F. sorry for my English
[SuperR Kitchen] SuperR.:
Please provide more information such as:

What Kitchen version?

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)?

What did you do after extracting and before building?

What have you tried that did not work?

Were there errors on the screen if you scroll up in the terminal?

Thanks
[SuperR Kitchen] NMonster69:
Maps doesn't blow up like it did before on deodexing. Your fix worked for me. Before I would have to delete it before de-odexing. Using this on a sammy tablet.
[SuperR Kitchen] lalitoSGSII:
Kitchen Version: 0.9.0.6

Device: Samsung Galaxy note 4 SM-N910F

Source: N910FXXU1COI3_N910FOXA1COI3_N910FXXU1COI3_HOME.tar

Android Version: 5.1.1 lollipop

perm metohd: sparse_dat

What did you do after extracting and before building:I did everything correctly but when trying to flash my device not flas that is trltexx ..... this device is not trlte end trltexx

What have you tried that did not work: never begins to flash that is trltexx

Were there errors on the screen if you scroll up in the terminal: no errors terminal trlte says no flash for this device is trtlexx

Thank you for your quick response took 3 days but does not work on trying and always the same mistake this device is not trlte is trltexx :good::good::good::rolleyes::rolleyes::rolleyes::rolleyes:
[SuperR Kitchen] SuperR.:
In the kitchen, go to ROM Tools, Asserts: Add/Change devices, then add trltexx to the list, and rebuild rom. Make sure you follow the on-screen example formatting. Should work out for you.
[SuperR Kitchen] lalitoSGSII:
flash now but when you start charging the Samsung logo without sound 30 seconds and restarts. Boot-loop and not by modem or by CSC are Flashed with Odin. Thank you and sorry for the inconvenience
[SuperR Kitchen] frequentc:
Sparse dat may be causing the problem on Samsung phones, so you may want to try doing both of the other methods. I've never seen a Samsung rom use the sparse dat method.

It also wouldn't boot on my Galaxy note 3.
[SuperR Kitchen] SuperR.:
v0.9.0.7

Changes:

Fixed restore bloat. Was not moving all the files.

Added a not recommended for Samsung tag on sparse dat option and it will no longer ask you if you want to use sparse dat if your device is Samsung. You can still choose sparse dat if you want however.
[SuperR Kitchen] nghia0423:
I have one built with set_metadata. Going to test it now.

Edit: Tried both set_metadata and set_perm. Metadata gets stuck at T-Mobile splash while set_perm gets stuck at the Samsung Galaxy Note 3 splash for me anyways.
[SuperR Kitchen] dkionline:
On actual builds you have more sets to include, just look on other custom roms for including this.
[SuperR Kitchen] lalitoSGSII:
does not work in Note 4 SM-910F

does not work for galaxy note 4. Tested with the two methods ... samsung logo set_metadata start (no sound) 30 seconds and restart the same logo ... no sound set_perm restart.
[SuperR Kitchen] :
N910f or n910c? I know you probably already know but if it's the n910f you have to odin the non hlos bin from the same rom or it won't boot
[SuperR Kitchen] lalitoSGSII:
Thank you for your clarification TLF is 910F and has both the bootloader Flashed as the modem of the CI3. I have a custom rom the sd (kyubi rom v6) and runs smoothly. I just try to help SuperR in your Work [emoji106] [emoji106] [emoji106] [emoji106]

Enviado desde mi SM-N910F mediante Tapatalk
[SuperR Kitchen] ferbulous:
Hi, I tried deodexing my 5.1 stock rom (vk6050s)

It was done by [MENTION=5297774]bcrichster[/MENTION] before this

Problem is when I'm building the zip file, it's incomplete (0 bytes on system.img)

Anything I'm missing here? Not sure if I can post error logs or something and I'm using vm linux
[SuperR Kitchen] SuperR.:
Have you checked Post #4?
[SuperR Kitchen] ferbulous:
I tried installing it, but it's unable to locate the package? I'm on 32bit ubuntu btw
[SuperR Kitchen] SuperR.:
Are you on the newest kitchen? I ask because it now checks to make sure you have all the other dependencies met. If you are running the newest kitchen and you are on 32-bit Ubuntu, I have no idea what is going on. Are there any errors in the terminal if you scroll up after building the zip?
[SuperR Kitchen] Androidwizzard:
Whatever rom I have made, I've never let the kitchen zip it as normally there is so much more to do before packing (tweaking. making changes in framework eg extended reboot menu, decompiling apps aso.) - kitchen is the first step towards development.
[SuperR Kitchen] SuperR.:
v0.9.0.8

Changes:

Added support for multi-file twrp backups such as .win000 .win001.

Cleaned up extract code.
[SuperR Kitchen] supercowz:
hum, im not expert but using tune2fs -l on system.img 2.7gb raw (using official rom zip system.spare.dat converted with supperr)

i got :

655360 x 4096 = 2684354560

now dump system.img 2.7gb with superr under Twrp, tune2fs :

655320 x 4096 = 2684190720

trying with both still lead me to 18mb zip file ...

thanks for your help anyway ... just idk what to do ...
[SuperR Kitchen] sparks15:
[MENTION=5787964]SuperR.[/MENTION]

What Kitchen version? 1.04.1

What Linux are you running? ubuntu 15.10

What device are you working on (make/model)? nexus 6

What was the source you started from (system.img, system.ext4.tar, rom.zip, etc.) system.img

What Android version? preview n

What perm method (set_perm, set_metadata, sparse_dat, raw_img)? all

Were there errors on the screen if you scroll up in the terminal?

ERROR:

Either your kernel does not support selinux, or

the kitchen can't find what it needs. If you are sure

your device supports selinux, you can copy the file_contexts

file from the ramdisk to your 00_project_files directory

to use this feature.
[SuperR Kitchen] SuperR.:
If you are running 32-bit Linux, rimg2sdat (the binary that creates sparse_dat images) will not work so that may be the issue. Otherwise, the issue must be that you have more data in the system directory than can fit in the size you (or the kitchen) are using for your system partition.

This issue is due to the file_contexts.bin file the new N preview switched to. Previously, this was a flat file called file_contexts and the flat file is what the kitchen is looking for. It does not exist so you get the error. I need to figure out how to read this new file_contexts.bin file to make it work. If anyone knows how to do this please post. Most of the info appears to be readable with a hex editor, but that is about as far as I have gotten so far. Will keep looking.
[SuperR Kitchen] SuperR.:
v1.0.4.3

Changes:

Added support for extracting system.img, vendor.img, and boot.img from official Nexus preview tgz.

Added support for the new file_contexts.bin format found in N preview.

[MENTION=6987991]sparks15[/MENTION] - This should fix your issue. Thanks for pointing it out :)
[SuperR Kitchen] krowley3:
Just built and booted shamu n preview using your kitchen. Thanks for the great tool .
[SuperR Kitchen] manojpy:
Did you build it with supersu 2.70 or flashed it later.
[SuperR Kitchen] krowley3:
I didn't root. Didn't see any need since I can make changes before building and any other operations can be done in TWRP.
[SuperR Kitchen] enotar:
last version doesnt work on linux, cannot be run as root.....?

edit, all OK sorry
[SuperR Kitchen] toheedasad:
For Samsung Devices, do i have to extract both system.img and cache.img?
[SuperR Kitchen] Er. Aditya:
yup all csc features are in your cache
[SuperR Kitchen] fitosanitarium:
I had the same issue with nexus 7

I discovered that my system partition was full, so adding things like supersu, busybox or other things without debloating the rom, resulted in a /system partition that exceed the max size for my device.

Solution for me was then debloating the device!
[SuperR Kitchen] SuperR.:
v1.0.4.4

Changes:

Added option to choose SuperSU version when adding root if more than one zip is in /kitchen/tools/root/supersu.

cache.img is now extracted with Samsung firmware zips that contain tar.md5 files.

Added a check to make sure images exist before building a rom zip to prevent tiny zip files and provide info how to fix it.

Updated README.md
[SuperR Kitchen] Er. Aditya:
your awesome , please add a option to view change logs as well bro :)
[SuperR Kitchen] SuperR.:
Not sure what you mean. There is a link in the OP to see the changes/commits. If you click the link and hover over the message you can see a pop-up with all the changes for that version. If you want a more detailed view, you can click on a commit and see the message and the changes to the code.
[SuperR Kitchen] jaylence:
Feedback

Samsung Galaxy A5 2016 (SM-A510Y)

Lollipop 5.1.1

Ubuntu 15.10 64bit

SuperR's Kitchen v1.0.4.4

TWRP 3.0.0

Images used (from Stock Firmware .tar.md5):

boot.img

system.img

cache.img

Changes made to working folder:

enabled root

perm used:

set_metadata

result: WORKING. Flashed successfully.

** I tried adding more changes to my working folder like deodexed, busybox, app support. Deodexing errors on the following apps: MAPS, SHEALTH_4_3, SERVICES.JAR.

I replaced these files with the one I deodexed using Joeldroid's tool.

Rebuilt the rom using SET_METADATA.

RESULT: BOOTLOOP. It did managed to get past the boot animation. Optimized all apps and notified "Boot Complete / Opening Applications". Phone's display turned off and rebooted again and again.

Any hints guys?

Thanks in advance.
[SuperR Kitchen] osm0sis:
Worked around TWRP3's issue of slow flashing (only happens on some devices) for my busybox installer if you want to update it again in your kitchen [MENTION=5787964]SuperR.[/MENTION] :)
[SuperR Kitchen] sparks15:
Thanks for your hard work [MENTION=5787964]SuperR.[/MENTION]
[SuperR Kitchen] Er. Aditya:
thanks bro but what i ment was to add another option if someone is not accesing xda then they can view the latest kitchen change logs via kitchen itself...but thats just not that important ...again latest kitchen is working super awesome like always bro great work

---------- Post added at 01:00 PM ---------- Previous post was at 12:56 PM ----------

apk's has nothing to do with the bootloop...try placing stock service,jar n try again
[SuperR Kitchen] bcrichster:
Then they can just sign up to XDA... [emoji41]
[SuperR Kitchen] SuperR.:
v1.0.4.5

Changes:

Updated to the latest Busybox installer by [MENTION=4544860]osm0sis[/MENTION].

Added option to view changelog for the last 3 versions when an update is available.
[SuperR Kitchen] janjan:
Thanks for your great work. Love your great work. Any possibility to add root inside a system.img. I mean possibility to add Supersu.apk and other files inside system.img. Properly one for 32bit and one for 64bit. Inject root inside system.img.

Thanks
[SuperR Kitchen] SuperR.:
Not very easily, if at all. Root is not what it used to be. You can't just toss some files in and expect it to work. There are many different requirements for different devices, Android versions, etc. You can however try to extract a system.img from your rooted device (if it is not systemless) and unpack it. Then you can make your changes and repack and it should still be rooted. Keep in mind that if you are building Samsung 5.1.1 and/or any 6.0+ roms, more mods will be required than just in /system. Another option is to create a raw_img rom and add root. After the images are flashed SuperSU will be flashed to provide root. Not sure what your goal is so that is about all the help I can provide at this point.
[SuperR Kitchen] xdadroidabc:
I am getting lz4 missing dependencies error

when I say yes to install missing dependencies, It throwing error message - unable to locate package liblsz-tool

Ubuntu 12.04 64bit Kitchen version 1.0.4.5

Thank you.
[SuperR Kitchen] asc1977:
[MENTION=718594]superR[/MENTION]

I am now figuared out why some problems. If somebody first install ubuntu he cant install depencies on superr tool. It wont work. I have this problem today because i must install ubuntu new. Before superr tool can install depencies i have to do three things manual in terminal.

Sudo app-get install gawk

And same for lzop and lz4

For safety i installed also java7 from software center.

After that the first start of superr kitchen work and it installs depencies.

Hope that helps a little and hope you can integrate this steps in yout tool for all others who have also that problem
[SuperR Kitchen] Er. Aditya:
lol thanks bro but when SuperR. is here requests gets fulfilled
[SuperR Kitchen] tdunham:
Ok, I'm stuck.

I can get to the extract image phase but even creating a project, I nearly always get the error in this line for permission denied on Ubuntu:

./superr: line 6023: /home/troy/superr/superr: Permission denied

Edit:

Not always this line but it seems to occur when folders are getting created. I cant be completely certain. The program bails and I can let a little further each time until I get to the set_perm portion:

./superr: line 5127: exec: /home/troy/superr/superr: cannot execute: Permission denied

Update:

Installing Ubuntu 15.xx 64 bit version and will give it another go. If anyone has any ideas for the above issues, please let me know.
[SuperR Kitchen] bcrichster:
Make absolutely sure your Linux installation iso isn't corrupted to begin with.. I went round & round with this kitchen once before and it was actually my iso being corrupted that caused all my grievances to begin with. Just a thought.. [emoji41]
[SuperR Kitchen] tdunham:
Thank you. My old install has suited me well so far but no success with Archi Kitchen for Marshmallow and I heard this one was the way to go. :)

The new amd/64bit install seems to be working.

So far the only error that popped up was that output folder couldn't be created or didn't exist, I cant remember that one exactly. It is building now so I wont know for sure until later on.
[SuperR Kitchen] heliusjing:
when I create a new project, I don't know which directory I should put the base ROM in ? in addition, sometimes, must I create a new project? ------------------------------------------come from China
[SuperR Kitchen] SuperR.:
The problem is that your OS version does not contain the repo for lz4. Look for a ppa for your OS that contains this package or better yet, update your OS.

The kitchen tries to first install missing dependencies, then tries to build the Android tools from source. If the source build fails, then it will download and install prebuilt binaries of those tools. It uses the same command to install the dependencies as you stated...sudo apt-get install so I am not sure why you have to do it manually. I have not heard this problem yet and can't reproduce it.

It sounds like your sudo is not getting called when needed for some reason. I am not able to reproduce this issue.

Glad to hear you are making progress. If you get that error again, please let me know the exact steps to reproduce it. Thanks

If you create a new project called "test", that project will be in /kitchen/superr_test and this is where your base rom should go. You can create as many projects as you want.
[SuperR Kitchen] :
Hello SuperR

i'm trying to modify a cyanogen 5.1.1 rom file. Everything go fine but i have a problem with root.

When i extract the rom.zip it says is already rooted (true, cyanogen is already rooted). If i change the permission to sparse.dat (as suggested) when building the ROM it put SuperSU drawer in..

cyanogen don't need superSU installed because it already have his superuser integrated.

I tried flashing the resulting rom but it asks "your phone is not rooted, wanna install supersu?"