yashsingh1/xdaforums huggingface dataset:
[SuperR Kitchen] jesus183095:
I create the zip but to flash when i choose install zip. the twrp recovery says:

installing '/externalsd/prueba.zip

checking md5 file...

skipping md5 check

this package is for "fortunave3g" devices;this is a samsung sm-g530h

E:Error executing updater binary in zip '/external_sd/prueba.zip

Error flashing zip '/external_sd/prueba.zip'

updating partition details.....

done

you can help me? :D
[SuperR Kitchen] SuperR.:
Start reading here

http://xdaforums.com/showthread.php?p=63338161&highlight=assert#post63338161
[SuperR Kitchen] Er. Aditya:
hey champ , little update the latest version still removes knox libs

libknoxvpnfdsender.so

libknox_encryption.so

libknox_km.so

libknox_legacy_ode_km.so

libknox_migration.so

and causes bootloops , may be replacing all of them causes bootloop or any 1 of them

il test and report tomorrow may be
[SuperR Kitchen] jesus183095:
i try to change klte,kltespr

but i dont found the superr_mmc in my kitchen device. and not found this rute. And i wathce the build.prop in my device in the line ro.product.device=fortunave3g

and the ro.product.model= SM-G530H

i very rare. and i not understand the stepts of change to fix this problem.

I need the edit the superr_byname? or other file and i have file name is this project_grand_prime and inside of this exist a archive call assert and says this:

assert(getprop("ro.product.device") == "fortunave3g" || getprop("ro.build.product") == "fortunave3g" ||

abort("This package is for "fortunave3g" devices; this is a "" + getprop("ro.product.device") + ""."););

what i change or what line is? i adjunt some pictures to explain more.

http://xdaforums.com/attachment.php?attachmentid=3512283&stc=1&d=1445289955

http://xdaforums.com/attachment.php?attachmentid=3512284&stc=1&d=1445289955

http://xdaforums.com/attachment.php?attachmentid=3512285&stc=1&d=1445289955

http://xdaforums.com/attachment.php?attachmentid=3512286&stc=1&d=1445289955
[SuperR Kitchen] ROBERT CM:
I can not use this tool I have ubuntu 15.04

p7zip and install JDK 7 and I get this error when I want to use

I need to install or am I doing wrong, I hope you can help me thanks
[SuperR Kitchen] SuperR.:
Please read post #3, Usage instructions. You are not running the script from the correct directory.
[SuperR Kitchen] Q9Nap:
[MENTION=5787964]SuperR.[/MENTION]

I'm testing out the kitchen on the new 5x fastboot files and want to point out that you might want to add support for vendor.img.

The kitchen is able to extract vendor.img to a directory, but doesn't include any updater-script code to extract the directory or create symlinks/permissions for it.

Thanks again for this great tool :)
[SuperR Kitchen] SuperR.:
v0.9.2.7

Changes:

Changed device by-name/mmc location from kitchen/devices/devicename/ to kitchen/tools/devices/devicename/.

Moved project files into project directories named 00_project_files now located in each project directory.

Debloated files and old_rom_files will now be located in the 00_project_files directory.

Each project now has its own logs.

Added 64-bit Linux check and a warning if running 32-bit.

Minor UI enhancements.

PLEASE READ CAREFULLY:

This update changes where files and directories are stored. I have created a script that will move all your existing files where they need to be.

Update the kitchen and close it.

Delete /kitchen/tools/devices

Download the attached file and extract it to your main kitchen directory

Run the script from the main kitchen directory the same way you start the kitchen.

Sorry for this, but it makes a lot more sense to have all the project files in the project directory and this is the easiest transition I could put together for you :)
[SuperR Kitchen] DarkHeart Z:
add compatibility

Bro will you add support for cygwin ? It meets all your depenencies by default and I have also apt-cyg installed . Though after doing some little tweaks I made it work in cygwin .

1. Commented out internet check in kitchen_update ( because there is no /sbin/ip in cygwin , it uses my windows ipconfig )

2. cygwin has all packages your kitchen needs in their repo's too . And also it meets all of your depenencies also .

3. for carliv's tools , I had to copy all win32 executables of kitchen to .bin folder ( only those you kept there ) . And changed unpack repack img , mtk img scripts first lines which have lines like e.g : unpackmtkimg=unpackmtkimg to unpackmtkimg.exe and lines like this one ( works properly on 32 bit environment , not sure about 64 bit ) .

4. The moment when the developer needs his hand on it : Done the same with repack_mtk_img ( only 1st lines , didn't mess with the rest ) . But whenever repacked boot.img , it doesn't repack it . Tried with pack boot.img , delete ramdisk and pack boot.img , keep ramdisk . It's still the same .

I am still sticking to your project just because your kitchen have all I need and even more . If you add support for cygwin it would be really helpful for us who have windows environment with cygwin installed . And I would be able to finish my projects in time . please add support . If any additional info is in need just let me know I will provide those too :)
[SuperR Kitchen] Er. Aditya:
cygwin .... how to add device support ? sometimes i need to use windows as well

also can i pm you for few stuff ?

thanks bro
[SuperR Kitchen] Captain_Throwback:
Sure, lol. There's still some bugs - but once those are worked out I'll be sure to mention it here.
[SuperR Kitchen] MoistPicklez:
Hey guys, I'm new to this amazing Kitchen, ( Major props to [MENTION=5787964]SuperR.[/MENTION] ) and I am attempting to build a TW based ROM for my S6. I just wanted to ask if signing the ROM zip is important, as my Laptop's RAM is not sufficient enough..
[SuperR Kitchen] Er. Aditya:
You would be fine even without signing the zip
[SuperR Kitchen] blueberry60:
I have created Stock Deodexed Rom from latest HTC10 2.41.401.3 system and boot.img with these options:

1-Set metadata perm type

2-Unpack and pack boot.img

3-Insecure boot.img

4-dm-verity and forceencrypt disabled

5-Deodexed with smali/baksmali

6-Rooted (Let SuperSU decide with SuperSU SR3)

7-Busybox and su.d support enabled

8-Deleted META-INF directory from all the apk files (Nougat uses APK Signature Scheme v2)

9-Debloated

10-Zipaligned all apk and other apk files in /framework before building and builded

Flashing process has completed successfuly without any error but device was stuck on htc boot screen.

There was an error on deodexing (framework.apk) just below that:

ERROR: No more files
/home/mberol/Masaüstü/superrs-kitchen/superr_M9_Nougat/system/app/framework/framework.apk

System ERROR:
Bilinmeyen hata -2147024872

... Deodexing framework

basename: ``find'' operandı fazla
Try 'basename --help' for more information.
Can't find file: /home/mberol/Masaüstü/superrs-kitchen/superr_M9_Nougat/system/app/framework/oat/arm64/framework.odex/
Exception in thread "main" java.lang.IllegalArgumentException: Cannot find file or directory "/home/mberol/Masaüstü/superrs-kitchen/superr_M9_Nougat/system/app/framework/oat/arm64/smali"
at org.jf.smali.Smali.assemble(Smali.java:82)
at org.jf.smali.AssembleCommand.run(AssembleCommand.java:96)
at org.jf.smali.Main.main(Main.java:99)
Unable to add '/home/mberol/Masaüstü/superrs-kitchen/superr_M9_Nougat/system/app/framework/oat/arm64/classes*.dex' to '/home/mberol/Masaüstü/superrs-kitchen/superr_M9_Nougat/system/app/framework/framework.apk': file not found
[SuperR Kitchen] Captain_Throwback:
Try without deleting META-INF folders from APK files. HTC APKs come pre-deodexed, so that step isn't necessary. Also, depending on what "bloat" was removed, it could be causing your issue. If neither of those works, you'll need to start from the beginning and only apply one change at a time to see where the issue is.

Also make sure you're using the latest TWRP for the 10, as a new unofficial version was released yesterday.
[SuperR Kitchen] blueberry60:
Thanks for your support, also I've been using your latest unofficial TWRP, I'll try on every process from the beginning as you told.
[SuperR Kitchen] minhnewpro:
Hello everyone. I want to try cook rom but i don't see some options like deodex rom, root,... even create file rom.zip.

[IMG="Menu"]http://sv1.upsieutoc.com/2017/02/07/Untitled27435.png[/IMG]
[SuperR Kitchen] Captain_Throwback:
Options 6-8 have submenus...
[SuperR Kitchen] minhnewpro:
Here is 6-8 menu. i extract system folder from system.ext4.win000 system.ext4.win001 system.ext4.win002 (TWRP Backup) and i copy to project folder.

[IMG="8"]https://uphinhnhanh.com/images/2017/02/07/15c663.png[/IMG]

[IMG="6"]https://uphinhnhanh.com/images/2017/02/07/Untitledfd541.png[/IMG]
[SuperR Kitchen] Captain_Throwback:
The yellow colored items all have submenus. Keep looking through the menus until you find what you're looking for ;).
[SuperR Kitchen] minhnewpro:
i try every yellow option but only can edit boot.img (Option 7 Boot/Recovery tools). 6 and 8 not show anything

Ok, thank you. i try to copy all 3 files system.ext4.win000 system.ext4.win001 system.ext4.win002 and extract again by super kitchen and now I see more option ^_^

---------- Post added at 11:24 PM ---------- Previous post was at 11:09 PM ----------

i try deodex but it show "basename missing operand", how i can fix it?
[SuperR Kitchen] ShinySide:
Delete- Xda labs why you fail me lol
[SuperR Kitchen] minhnewpro:
Ok, i found empty build.prop @@. seem extract error or something. i copy build.prop and now it deodexing

---------- Post added 8th February 2017 at 12:02 AM ---------- Previous post was 7th February 2017 at 11:55 PM ----------

i get this error, should i worry about it?

[IMG="Error"]https://uphinhnhanh.com/images/2017/02/08/Untitledc58a0.png[/IMG]
[SuperR Kitchen] bcrichster:
Ignore it then see if the ROM flashes and functions correctly when installed. If it works, then you're fine with the ROM. If not, return with more information and go from there..

Sent from my PAC 6.0 N9515
[SuperR Kitchen] minhnewpro:
this error cause by missing file. because i give virtual disk not enough memory. after create new virtual with 20GB memory. everything is good now.
[SuperR Kitchen] bcrichster:
Good catch!
[SuperR Kitchen] tanish2k09:
I think the kitchen doesn't calculate how much space would the rom-building require.

Many times, while building roms, I ran out of space while the ROM was in the middle of building process.

Result was that I got a zip file of 200MB. My source ROM was itself 950MB in size. So the build had to be at least 900MB.
[SuperR Kitchen] russel5:
Hello [MENTION=5787964]SuperR.[/MENTION]

Found little bug.

Perm type set to raw_img - choose build full rom got this error

ERROR:
You need an img for this process.
Press ENTER to continue

Ok, press enter got this

ERROR:
You need a boot.img for this process.

But boot.img exist in folder.

Ok, first choose unpack boot.img, after build full rom - all works.

This ^^ is because i'm don't had a file_contexts in project_files, but why your script fail when it must unpack boot.img before building full rom i'm don't know.

P.S. and i'm know about unpackimg.sh "bug" with img's path.
[SuperR Kitchen] andy_zhang:
ERROR:

There was a problem unpacking your boot.img
[SuperR Kitchen] russel5:
Fix unpackimg.sh in tools/boot/AIK folder like THIS
[SuperR Kitchen] SuperR.:
I will take a look asap

edit: [MENTION=4688377]russel5[/MENTION] - Found the problem, thanks for pointing it out :) Will get it fixed as soon as I can. In the meantime, your workaround will be fine. You don't even need to repack the boot.img. You can unpack and delete the bootimg directory after. file_contexts is picked up when the boot.img is unpacked if it's not already in your 00_project_files directory.

Maybe AIK doesn't work with your boot.img. send it along with your build.prop and I will take a look.

The version of AIK included in the kitchen has already been patched.
[SuperR Kitchen] SuperR.:
v2.1.5.3 (Donate version)

Changes:

Fixed file_contexts not being grabbed before unpacking boot.img manually.

Fixed vendor and extra partitions being added to the updater-script more than once.

v1.1.4.3 (Standard version)

Changes:

Fixed file_contexts not being grabbed before unpacking boot.img manually.

Fixed vendor and extra partitions being added to the updater-script more than once.
[SuperR Kitchen] SuperR.:
I am not sure why you posted all that prop info. Try the hide feature next time lol

Your boot.img unpacks with no issues in the kitchen using the new included AIK 2.5 for Linux. I am not sure what is going on with your machine.
[SuperR Kitchen] Mezabaru:
did super kitchen 2 move from gitlab?
[SuperR Kitchen] tanish2k09:
There is one boot image that isn't getting unpacked properly. And neither repacked.

I can send you that sample.

another question [MENTION=5787964]SuperR.[/MENTION] :

If I make a few modifications in my system folder, and build with set-metadata option, will the kitchen auto-update the symlinks and permissions?

Or will I need to try raw-img perm method?
[SuperR Kitchen] andy_zhang:
My pc is Ubuntu 16.4 ×64

China user
[SuperR Kitchen] SuperR.:
No

Send the boot.img and build.prop if you want, but if it does not unpack/repack there is not much I can do about it. You could post on the AIK thread since the kitchen uses the latest unmodified AIK for Linux

It will not add new metadata lines when you make changes, but it will remove lines if the corresponding files no longer exist. Just try and see how it works.

Still not sure what to tell you. I did not have any problem unpacking your boot.img. Make sure you are on the latest kitchen version. You could try Ubuntu4Kitchen linked in post #4.
[SuperR Kitchen] tanish2k09:
Well yes, the problem is in unpacking and repacking. I try contacting devs on that thread.

The meta-data didn't work for me. Raw image method was fine. Thanks though.
[SuperR Kitchen] SuperR.:
Were you able to unpack/pack the same boot.img before I switched to AIK?
[SuperR Kitchen] tanish2k09:
Didn't try before.
[SuperR Kitchen] SuperR.:
I cleaned up the bitbucket repo as it was getting fairly large. The good news is that cloning will be much faster. The bad news is that the kitchen updater might not work now. If you get a strange screen asking you to add a commit message, you can exit out of it with ctrl+x. I am not sure what will happen after that. If you have trouble, you can always clone a fresh copy of the kitchen to fix it. I forked the kitchen before cleaning it to avoid losing all the older versions/commits.

I will be cleaning the Gitlab repo shortly as well. Sorry for the inconvenience.

Ok Thanks
[SuperR Kitchen] Sh0X31:
[MENTION=5787964]SuperR.[/MENTION] why the Kichten can't extract the NVIDIA Image?

https://mega.nz/#!9pETiLaC!lY6Is86hnVcd1mq0qEH3WmCtvBvb_s-g9PMoOIE-bg4
[SuperR Kitchen] andy_zhang:
Okey, i try ur Ubuntu

China user
[SuperR Kitchen] SuperR.:
I will fix this in the next update.

The problem is only the file name. It contains the word "recovery" and the kitchen was removing these results. Rename your zip removing "recovery" and it will work for you.
[SuperR Kitchen] Hamidreza2010:
[MENTION=5787964]SuperR.[/MENTION] bro would you please give me , download link of last version?

i cant download from bitbucket.org at all

not with browser , not OTA , not ....

its related with my Isp

( bro sometimes to sometime i,ll put this post again for give link of new version , because cant download from above link.sorry for that )

thanks
[SuperR Kitchen] tanish2k09:
[MENTION=5787964]SuperR.[/MENTION]

Is it possible to downgrade the kitchen?
[SuperR Kitchen] shoey63:
Why do that? Surely moving forward is the way to go.
[SuperR Kitchen] tanish2k09:
I know sir. But I'm having some trouble with the latest clones. The last time I had a perfect version was somewhere around 1.1.2

Though I think the problems I have are not caused by the kitchen. They are probably from my side, and I am trying to find it. So I wanted the previous version just to make sure whether the kitchen was buggy or something else.
[SuperR Kitchen] Sh0X31:
[MENTION=5787964]SuperR.[/MENTION]
[SuperR Kitchen] SuperR.:
here is v1.1.4.3

This is a Bitbucket link, but give it a try.

When downloading kitchen zips, you will not be able to use the kitchen updater.

here is v1.1.4.2

When downloading kitchen zips, you will not be able to use the kitchen updater.

Is the by-name line shown correct for your device? If you send a recovery.log after flashing we might be able to see more of what is going on.
[SuperR Kitchen] Growtopia Jaw:
The perfect and up to date kitchen for beginners:good:
[SuperR Kitchen] walfree:
Hi [MENTION=5787964]SuperR.[/MENTION],

Unless i 'm missing something obvious, i think there is a bug (v1.1.4.3): If the name of the zipped ROM contains spaces, the kitchen returns the error/warning "Τhis zip does not contain anything the kitchen can extract".

Renaming does the trick.

Thanks.
[SuperR Kitchen] Er. Aditya:
i am not able to sideload rom zip created by kitchen mate

edit : also at the end it defines zip file is corrupted ...here's log if it can help
[SuperR Kitchen] Hamidreza2010:
Again i cant download :(
[SuperR Kitchen] bigrammy:
Did you use the update-binary method to flash a .img :confused:

I once had a similar issue where system was under system eg: /system/system

So just do a quick check using TWRP's Advanced/File browser and check the /system folder for another /system ;)

---------- Post added at 10:09 PM ---------- Previous post was at 09:44 PM ----------

Disable MTP from TWRP's mount menu and also check data is unmounted then try sideload the rom again. :fingers-crossed:

It seems you have problems getting access to data which maybe because it's in use by the above or it's maybe encrypted. :confused:
[SuperR Kitchen] SuperR.:
You would be better off talking to the person who created a zip for Linux/Android with spaces ;)

Starting with v1.1.4.3, you can find standard kitchen version zips here:

https://s.basketbuild.com/devs/SuperR/SuperRs_Kitchen

They will be posted every time the kitchen gets updated from now on :)
[SuperR Kitchen] walfree:
So, that's the "obvious something" I was missing -I was a bit hesitant about reporting it/couldn't believe I was the first one encountering it.

Given that kitchens are linux-based collections of tools (at least, according to my newbie's understanding), is it safe to assume that such a zipped ROM was ported using a "kitchen-less" method? (I 'm aware that it's a beginner's question, but I doubt that i can find a proper answer by searching XDA, because of its specificity.)

Anyway, keep up the good work. Given the opportunity, I 'll donate.
[SuperR Kitchen] tanish2k09:
[MENTION=5787964]SuperR.[/MENTION]

Considering the previous reported problem that if ROM name contains spaces, kitchen doesn't extract it...

Well, I don't know much about coding in Linux, but maybe data types are globally the same.

Question : which data type do you use to read zip name? String? Array of char?

See if you can implement a stream as a buffer to get all the letters of the zip, including white spaces. I have tried it in c++ successfully. I don't know how that code should be framed for the kitchen.

You can pm me for further explanation or help.

Edit : I just noticed that I can read the code of the kitchen by clicking "display" option instead of "open with terminal"...
[SuperR Kitchen] _that:
It's just a matter of correctly quoting all file names in all shell scripts:

http://unix.stackexchange.com/quest...oke-on-whitespace-or-other-special-characters
[SuperR Kitchen] tanish2k09:
Precisely. Agreed.
[SuperR Kitchen] Hamidreza2010:
Its excellent bro

i will download new version from above link from today

thanks again
[SuperR Kitchen] Lefteris Fragiadakis (Frago):
Bug,, after installing new update when i trying to pull system from recovery or from android Rooted always i have a msg it lack permissions and i can't extract for creating new rom,, before was always already working
[SuperR Kitchen] SuperR.:
Yes, it is absolutely possible and correct to properly handle file names with spaces in the Linux terminal.

I will not change this (with the exception of possibly adding an error telling you to remove the spaces) so rename your zips :) See below for more info.

I use variables containing file names in strange ways on occasion and it makes quoting them a pain. It is not good practice to ignore files with spaces, agreed, but this is the first case I have had where it was an issue since I started this kitchen. It is also not good practice to name files with spaces if you intend on using them in Linux/Android. Perhaps I am old school lol

It has been a while since anything changed in the kitchen regarding pulling img's from your device. If you used the kitchen updater to update within the last 2 days there could have been issues. Try doing a fresh clone and see if that fixes the issue.
[SuperR Kitchen] Lefteris Fragiadakis (Frago):
Tried clean install, but nothing, device is sony xz using latest 7.0.1
[SuperR Kitchen] SuperR.:
Which kitchen version works properly?
[SuperR Kitchen] Lefteris Fragiadakis (Frago):
1.3.3.4 or 1.1.137 as i remember had before
[SuperR Kitchen] SuperR.:
Here is v1.1.3.7. Give it a try again and let me know how it goes. Thanks

edit: here is v1.1.3.4 for good measure :)
[SuperR Kitchen] Lefteris Fragiadakis (Frago):
So yes,i was correct,in both versions its working like a charm!now u should send me all the versions from 1.1.3.7 to see where it breaks
[SuperR Kitchen] SuperR.:
v1.1.3.8

v1.1.3.9

v1.1.4.0

v1.1.4.1

v1.1.4.2

v1.1.4.3 (current)

Thanks :)
[SuperR Kitchen] Ammaar884:
Sir i wanted to extract system.img it shows error that " there was a problem extracting your rom" i even correctly extracted the whole firmware
[SuperR Kitchen] Lefteris Fragiadakis (Frago):
So my friend,,,v1.1.3.8 is the last working version,after that one all the others are not working

---------- Post added at 11:11 AM ---------- Previous post was at 10:54 AM ----------

@SuperR. Just found another serious bug!i just want to check again the versions,if im correctly after v1.1.34 when i build a rom

the rom isnt working right,,,drm fix for xperia isnt working and most times i have unknown baseband,,from yesterday i thought it was kernel problem,i did build multiple kernels but nothing,so what i did,i deleted from my previous v3 rom which i made it i think with v1.1.3.4 for xperia xz,the system folder and kernel which base was .374 and i replaced it with base .417 which is the latest for this device and voila!!!everything are working excelent,,,i dont know how and why,both times data was wiped and in both version v1.1.3.4 and the others i didnt change somethin in updater script,i will make more test to confirm
[SuperR Kitchen] Lefteris Fragiadakis (Frago):
So yes. After v1. 1.3.4 something bricks,,

http://www.mediafire.com/?5st0ncorblrj4gl

Meta-inf from 1.1.34 which install the rom excellent, after this version drm fix for xperia is not working and i get baseband unknown errors, i don't know why
[SuperR Kitchen] baloo30310@gmail.com:
Hello Super!

It's been a while since I was trying to compile a Rom for the Note4 (SM-N910F) snapdragon (trltexx-trlte).

Compile this fact well with the deodex ok.

The flash goes well I just edit in the update script (trltexx) so that it goes to flash with TWRP 3.0.2.0.

Except once I arrive on the desk of the Note I have an insufficient saturated memory message remains 250MB.

I have dump the dump file with the code # 9900 # to have access to the small hide.

But without success .

I send you my META-INF file.

Waiting for a reply cordially.

Excuse me for my English.

https://www.androidfilehost.com/?fid=529152257862702535
[SuperR Kitchen] Ammaar884:
I extracted the system.img and boot.img and can't extract it in the kitchen
[SuperR Kitchen] SuperR.:
Check post #4 and provide all the info at the top if you want help.

Please send the updater-script for the later versions that don't work, as well as a recovery.log after flashing the ones that don't work.

The problem sounds like a deodex issue I have seen when using oatdump method. If you deodexed with oatdump, try using smali/baksmali instead or try without deodexing. If that does not help, check post #4 and provide all the info at the top.