yashsingh1/xdaforums huggingface dataset:
[SuperR Kitchen] SuperR.:
The message is just what it says. The boot.img was not unpacked for one reason or another. I have no idea how to unpack a boot.img in cygwin other than using unpackbootimg.exe in the cygwin_binaries.zip which I have never used. Right now, the kitchen uses the same command in cygwin as it does in Linux with the exception of ".exe" appended to the back of unpackbootimg. If you figure out how to do it let me know :)
[SuperR Kitchen] adityaupreti:
Edit : Solved
[SuperR Kitchen] obersteiner86:
[MENTION=5844027]DarkHeart Z[/MENTION] try this tool https://www.dropbox.com/s/7bo1pqxth5yhgsk/bootimgtools.zip?dl=0

bootimg.exe --unpack-bootimg bootimg
[SuperR Kitchen] Hamidreza2010:
[MENTION=5787964]SuperR.[/MENTION] happy to you with Recognized Developer bro

keep up your work

thanks
[SuperR Kitchen] Thorvic777:
Well [MENTION=5248098]Thorvic777[/MENTION] here.. i will test your kitchen... maybe ill cook some good roms... Thunder_Universe maybe back... thanks [MENTION=5787964]SuperR.[/MENTION]

Enviado desde mi SM-G800H mediante Tapatalk
[SuperR Kitchen] DarkHeart Z:
Bro how about adding specific calls like when in linux unpackbootimg ; but when in cygwin unpackbootimg.exe . How about that ? Bgcngm's script also included that type of windows or linux specific calls . Or you can exclude the linux specific binaries in cygwin . Like when in cygwin linux binaries won't be included ; only cygwin specific binaries will . Can't you do that ?
[SuperR Kitchen] SuperR.:
Different binaries/commands are already used in cygwin. That's why you need the cygwin_binaries.zip to use cygwin. I do not have Windows so testing cygwin is not something I will be doing. If you want to figure out how to make everything work, do what you did with img extraction and I will sort out the details :)
[SuperR Kitchen] Sh0X31:
Hey guys,

which type of partition detection I need to use at Android Nougat?
[SuperR Kitchen] SuperR.:
by-name from boot.img will work if you are on the 5X or 6P. I am not sure about the Pixel devices.
[SuperR Kitchen] :
From experience I don't recommend it.

---------- Post added at 04:12 AM ---------- Previous post was at 03:16 AM ----------

From experience I don't recommend it.
[SuperR Kitchen] nikkali25:
Help me please!after deodexing using smali.i cant recieve sms..

Im in android 6 with arm64
[SuperR Kitchen] SuperR.:
If your ROM has a /system/plugin directory, try moving it out of the ROM before deodexing and move it back when it is finished. Other users have stated that deodexing /system/plugin can cause issues with receiving sms on some devices. If that does not help, provide the information at the top of post #4 and hopefully someone can help.
[SuperR Kitchen] KingRaheel:
Did u get any sort of error while deodexing? Remember if an app fails to deodex then ur rom might behave like a drunken monkey showing lots of FCs. So what i would suggest is not to deodex the messaging app. Before deodexing copy it to ur desktop, deodex ur rom and later at the time of building the rom paste it back in the project directory and then zip. You may also try dex2oat method using their latest github commits. :good:
[SuperR Kitchen] shadow25:
Hi SuperR, thanks for your great work. I have a problem with my OPPO device (R7 Plus). The kitchen can't read my partition table (by-name) nor by the boot.img or the recovery.img, idem if I plug my phone to the PC with debug USB. How can I resolve? And if I add it manually, how can do? Thanks
[SuperR Kitchen] SuperR.:
Please send your boot.img and build.prop and I will take a look
[SuperR Kitchen] shadow25:
Sent. Thanks
[SuperR Kitchen] nikkali25:
Dex2oat method gives me error in deodexing

---------- Post added at 06:29 AM ---------- Previous post was at 06:27 AM ----------

Thanks sir,your work help me a lot even im a beginner.Godbless sir.
[SuperR Kitchen] SuperR.:
v2.1.2.9 (Donate version)

Changes:

Use aapt.exe if it exists in tools dir for repacking apk and jar during deodexing on cygwin, otherwise error message.

Fix device name not being recognized if there are more than one ro.product.device lines in build.prop.

v1.1.1.9 (Standard version)

Changes:

Use aapt.exe if it exists in tools dir for repacking apk and jar during deodexing on cygwin, otherwise error message.

Fix device name not being recognized if there are more than one ro.product.device lines in build.prop.

NOTE: The kitchen will not even attempt to deodex on cygwin unless you have aapt.exe in /kitchen/tools directory. I don't have aapt.exe to include in cygwin_binaries.zip yet so I temporarily disabled it to avoid errors.

This version will fix your issue :)
[SuperR Kitchen] shadow25:
Oh thanks mate, I will test it! :fingers-crossed:

P.S. Work well, really thanks SuperR! :good:
[SuperR Kitchen] Guizão BR:
[MENTION=5787964]SuperR.[/MENTION]

I've tested now the zip with stock boot.img and the zip not work, the meta-inf recognize my device Q5 how Q2 and didn't mount system partition :(

And its possible put to zipaling option when i build system.img?

Thanks fir attetion and sorry for my bad english ;)
[SuperR Kitchen] SuperR.:
Use the Asserts menu to change your device asserts from Q5 to Q2.

The donate version has the option to zipalign separate from a full rom build.
[SuperR Kitchen] Guizão BR:
I did this, but the zip ROM not install
[SuperR Kitchen] SuperR.:
Send your recovery.log after flashing so I can see what is going on. Also send your updater-script.
[SuperR Kitchen] Thorvic777:
Installation loop, dependencies!!!

Hello [MENTION=5787964]SuperR.[/MENTION] , I am having this issue in Linux mint code Sarah the latest, I do all the steps for the first use, but is stuck in the dependencies screen, i did install all of them separate and are already, but still asking that to be install, what should i do!!!!:D
[SuperR Kitchen] ShinySide:
Log out and log back in. Sometimes some crap takes a log out to be recognized
[SuperR Kitchen] Thorvic777:
I tried all that still the same ... any idea.. it happens in both... de standard and donate version... any information or help???

Enviado desde mi SM-G800H mediante Tapatalk
[SuperR Kitchen] SuperR.:
Ubuntu4Kitchen is all set up and ready to go. You can find it in post #4 :)
[SuperR Kitchen] Thorvic777:
Mate.. i dont want to use it in VM or add other partition for this.. ill try to fix this issue... maybe deleting the option that send the order asking about dependencies add the startup..

Enviado desde mi SM-G800H mediante Tapatalk
[SuperR Kitchen] Thorvic777:
Tell me... someone having same issue?? Still stuck here..

Enviado desde mi SM-G800H mediante Tapatalk
[SuperR Kitchen] ShinySide:
http://xdaforums.com/showpost.php?p=69025403&postcount=4270
[SuperR Kitchen] SuperR.:
Say yes to the screen you posted which is asking if you want to install the dependencies to compile the binaries. When that fails, it asks if you want to download and install the binaries. Say yes again. That should get you going. If that does not work, download the appropriate 32/64-bit binaries from the bitbucket repo, unzip, and manually add them to /kitchen/tools/ and start the kitchen again.
[SuperR Kitchen] Thorvic777:
Hello dear, installing the 64bit binaries did the trick!!! thanks so much!!!
[SuperR Kitchen] Guizão BR:
[MENTION=5787964]SuperR.[/MENTION]

Here is the meta-inf of superr's kitchen has created and my meta-inf and the recovery log
[SuperR Kitchen] Thorvic777:
I has to change the permissions also on the main folder.. to make it work.. you are doing a great job..

Enviado desde mi SM-G800H mediante Tapatalk
[SuperR Kitchen] SuperR.:
Looks like you have one of those strange devices where recovery by-name is different than Android by-name. If you change your device file (/kitchen/tools/devices/devicename/superr_byname ) from this:

\/dev\/block\/platform\/mtk-msdc.0\/11230000.msdc0\/by-name

to this:

\/dev\/block\/platform\/mtk-msdc.0\/by-name

it should work for you.

You should not have to change permissions on anything, but glad it is working for you now :)
[SuperR Kitchen] bigrammy:
It also depends on the custom recovery.

I have seen both used depending on TWRP/CWM version used some use the 11230000.msdc0 and some do not.

Coincidence that we discussed that :laugh:
[SuperR Kitchen] geiti94:
[MENTION=5787964]SuperR.[/MENTION] can you add support for newest backsmali and smali? because the newest one supports nougat and so is otadump not needed. because i tryed to deodex sammy s7 nougat with otadump but he dont adds the meta-inf folders in the apks and so phone dont boots
[SuperR Kitchen] SuperR.:
Make sure you are running the latest kitchen :) The newest smali/baksmali is already supported and included for M and N. You just need to choose smali/baksmali deodex method.

oatdump and smali/baksmali both ask if you want to remove META-INF after deodexing. Just say no if you want to keep META-INF in the apk files.
[SuperR Kitchen] geiti94:
yes i see it now. i pressed update on the kitchen and it said is updated but was not so :eek: now i deleted the old one and recloned it from bitbucket and worked :D
[SuperR Kitchen] ROBERT CM:
Hi [MENTION=5787964]SuperR.[/MENTION]

a bit question..

Where or How I can to get donate version?

Thanks!
[SuperR Kitchen] Thorvic777:
In the op is the explanation.. donate him $10 and inform that here... or PM... then open a gitlab account and give it to [MENTION=5787964]SuperR.[/MENTION]...then follow the process in the OP for the kitchen2 ...

Enviado desde mi SM-G800H mediante Tapatalk
[SuperR Kitchen] zoko:
Hello, dev

I extract a stock Samsung S5 rom, and build without any modifications and realize that when extract the rom the csc files dont appear on system folder. When I boot the rom after build the device came without CSC... any help. Iḿ working on the last stock build TPH.
[SuperR Kitchen] ShinySide:
Csc is found in the cache.img
[SuperR Kitchen] SuperR.:
csc files on Samsung come from cache.img. If you have a cache.img in your project directory when you extract, the kitchen will ask if you want to extract cache.img and then ask if you want to include it in your rom. Make sure you say yes to both. If you don't have a cache.img and your rom does not contain csc files, the kitchen does not magically generate them so make sure cache.img is there when you extract.
[SuperR Kitchen] zoko:
Ok,thanks for help. it works thankś for the help both
[SuperR Kitchen] DarkHeart Z:
[MENTION=5787964]SuperR.[/MENTION] Please check your pm bro . And I founf out the issue of boot.img extraction . You just need to rework on the unpackbootimg utilization . It does recognize unpackbootimg.exe . i seen it creating a bootimg directory on the project folder . then in the middle of the way it suddenly shows errors . i tested the the binaries personally . They are working fine .
[SuperR Kitchen] Hedi.Karray:
hi , i was wondering if this can work on Windows , and if not odes it work on Ubuntu ? and if not also then which OS i should be running ? thanks
[SuperR Kitchen] bcrichster:
Windows --> Cygwin? Not yet, being worked on.

Ubuntu? Yes, any Linux will do.

Sent from my N9515's cm12.1
[SuperR Kitchen] DarkHeart Z:
Adb and aapt still needs some test . But cygwin compatibility issues are almost fixed . You can try it on cygwin if you want .
[SuperR Kitchen] Hedi.Karray:
I can deodex a stock MM TW rom with cygwin ?
[SuperR Kitchen] DarkHeart Z:
[MENTION=5787964]SuperR.[/MENTION] Bro Please check your pm . i sent you some fixes for cygwin . And I'm onto aapt and adb now .
[SuperR Kitchen] Hamidreza2010:
+1

if we can use this excellent kitchen on windows , its bee very nice.because im not linux user :(

how can we did it?

thanks
[SuperR Kitchen] DarkHeart Z:
It's been a lot of hassel . But yep that worth the effort .
[SuperR Kitchen] SuperR.:
v2.1.3.0 (Donate version)

Changes:

Updated Busybox Installer by [MENTION=4544860]osm0sis[/MENTION].

Added a support option in Misc Tools to create a small zip of things that help me when you have an issue.

cygwin - Added aapt.exe and updated most of the binaries thanks to [MENTION=5844027]DarkHeart Z[/MENTION].

cygwin - Fixed not being able to choose sparse_dat.

v1.1.2.0 (Standard version)

Changes:

Updated Busybox Installer by [MENTION=4544860]osm0sis[/MENTION].

Added a support option in Misc Tools to create a small zip of things that help me when you have an issue.

cygwin - Added aapt.exe and updated most of the binaries thanks to [MENTION=5844027]DarkHeart Z[/MENTION].

cygwin - Fixed not being able to choose sparse_dat.

Honestly I have no idea, but with this new version you will at least have a chance since all the tools are there.

I don't recommend cygwin so far as it has not been fully tested. [MENTION=5844027]DarkHeart Z[/MENTION] is working on figuring out what does not work and helping to get it all working. Hopefully at some point someone will write a tutorial on how to install cygwin, install all the dependencies, install and run the kitchen, etc.
[SuperR Kitchen] Hamidreza2010:
thanks bro for your hard working

yes its excellent if some one fully test it and make tut for it

your kitchen is excellent but some buddy arent linux kitchen ( its our poor ) but if we have this on windows , we can use this tool without any problem
[SuperR Kitchen] simo255:
Hello

I cant unpack my boot.img via the kitchen why?

It gives me *** mount: wrong fs type, bad option, bad superblock on /dev /loop 1, missing codepage or helper program, or other error In some cases useful info is found in syslog try dmesg tail or so** and after I have 'here was a problem extracting your rom'

My device is p9 lite

PS : I have this problem only with boot.img and cust.img , but system.img no !
[SuperR Kitchen] bcrichster:
Read post #4 & provide more detailed information to achieve better assistance

Sent from my N9515's cm12.1
[SuperR Kitchen] SuperR.:
What [MENTION=5297774]bcrichster[/MENTION] said, and also use the support option in the misc tools menu in the newest kitchen version. Attach the support.zip and your boot.img to your post. Thanks :)
[SuperR Kitchen] simo255:
https://mega.nz/#F!MtEmUKhZ!Tlv6loJlmcJ57fE2aBIzaQ

Thank u
[SuperR Kitchen] ambasadii:
[MENTION=5787964]SuperR.[/MENTION]

latest beta nougat firmware for s7/S7 edge got different permissions for this files to wifi work

edit:

in your kitchen is set like this:

set_metadata("/system/etc/init.goldfish.sh", "uid", 0, "gid", 2000, "mode", 0550, "capabilities", 0x0, "selabel", "u:object_r:system_file:s0");
set_metadata("/system/etc/init.sec.boot.sh", "uid", 0, "gid", 2000, "mode", 0550, "capabilities", 0x0, "selabel", "u:object_r:sec-sh_exec:s0");

should be:

set_metadata("/system/etc/init.goldfish.sh", "uid", 0, "gid", 2000, "mode", 0550, "capabilities", 0x0, "selabel", "u:object_r:system_file:s0");
set_metadata("/system/etc/init.sec.boot.sh", "uid", 0, "gid", 2000, "mode", [COLOR="Red"]0644[/COLOR], "capabilities", 0x0, "selabel", "u:object_r:sec-sh_exec:s0");
[SuperR Kitchen] SuperR.:
You sent the wrong zip. I asked for the support.zip created from the newest kitchen version released today. However, I am pretty sure your problem is that your BOOT.img needs to be renamed to boot.img. I was able to unpack it with no issues.

I will make the change in the next version. Hopefully it won't cause problems with older versions since I do not currently have a way to separate metadata from different Android versions. If I need to write this I will, but for now I will just make the change globally and see what happens. Thanks for letting me know :)
[SuperR Kitchen] minz1:
[MENTION=5787964]SuperR.[/MENTION] I donated. http://imgur.com/a/SV1Wz My gitlab username is: minz1
[SuperR Kitchen] minz1:
Yo, SuperR, I'm not too sure why this is, but whenever I create a version of my ROM, the APN or whatever is broken. My device should connect to Boost Mobile, but instead is connected to Sprint, and I'm not sure how to fix it. I've tried everything; including ROMs and such but I'm still not sure. I don't know where else to turn regarding this issue.

What Kitchen version? Latest Donator version.

What environment are you running the kitchen in (OS, 32/64-bit, cygwin, Bash on Windows, etc.)? Ubuntu4Kitchen

What device are you working on (make/model)? J7 (2015) J700P

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

What Android version? 6.0.1

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

What did you do after extracting and before building? Removed some apps, deodexed, zipaligned.

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

Send a recovery.log after flashing if you have problems flashing the ROM. No problems flashing.

Send a link that does not require registration to the files you started with (nandroid, system.img, boot.img, etc) LINK

Use the support option in the Misc Tools menu and attach the support.zip to your post. LINK
[SuperR Kitchen] SuperR.:
First of all, thank you so much for providing all the info I asked for when reporting an issue :)

Unfortunately, I don't think the kitchen is responsible for your device connecting to the wrong carrier and I don't have any good advice to fix it. Have you tried building a completely unmodified rom and see if it connects to Boost? If it does, maybe something you removed is required. If you find out the kitchen is messing something up, please let me know and I will fix it right away. Good luck :)
[SuperR Kitchen] ShinySide:
Boost is sprint and runs on sprint and sprints lte if available lol
[SuperR Kitchen] minz1:
you don't understand the problem; it does run on sprint, but it's still separate from sprint. all boost uses is sprint's towers. if i can't connect to boost itself, i can't use data
[SuperR Kitchen] bcrichster:
The stock browser on Boost Mobile devices open to Sprint anyways, just change your Homepage. Sprint/Boost uses same APN for data as well.

Sent from my N9515's cm12.1
[SuperR Kitchen] minz1:
I really don't understand how this would work. Are you saying that the problem is with the browser? I removed Google chrome and chrome customizations, could that have anything to do with it?
[SuperR Kitchen] bcrichster:
Maybe you should list every file removed and do a comparison. There's generally a "safe debloat" list with most devices once ppl have achieved Root. But a newer device?

That makes you "patient #0", be careful:

- document everything you do to the ROM so you can backpedal and fix when there's issues like yours.

- replace all apps & reZip, then boot once installed & see if your problem persists. One missing wrong app can make life miserable.

- when using a Kitchen you need to narrow down what went wrong yourself thru trial & error. If you unpacked the tar, repacked it with NO changes and still messed up.. THEN let SuperR know the issue (might be permissions) to look into.

Sent from my N9515's cm12.1
[SuperR Kitchen] DarkHeart Z:
Can anyone please test the kitchen's detect by-name from device during 1st setup on cygwin ? Any help will be appreciated .
[SuperR Kitchen] smd0bidaoui:
Good but complex
[SuperR Kitchen] terroboy k9:
Thanx for this useful utility.

Appreciate your work !!
[SuperR Kitchen] SuperR.:
v2.1.3.1 (Donate version)

Changes:

Updated smali/baksmali to the latest commit.

Changed init.sec.boot.sh permissions to 0644.

Added kitchen version to the support.zip.

cygwin - Improved the speed of converting symlinks during extraction.

cygwin - Fixed error about symlinks.orig.

v1.1.2.1 (Standard version)

Changes:

Updated smali/baksmali to the latest commit.

Changed init.sec.boot.sh permissions to 0644.

Added kitchen version to the support.zip.

cygwin - Improved the speed of converting symlinks during extraction.

cygwin - Fixed error about symlinks.orig.
[SuperR Kitchen] bcrichster:
Sweet!

Sent from my N9515's cm12.1
[SuperR Kitchen] bluflight:
[MENTION=5787964]SuperR.[/MENTION] newest deodex method oatdump work fine for OnePlus3, rom had no problem, but one issue to memory: always show popup about storage space running out, but checking with titanium have enough space:

I do not understand why, deodex related or something else? :confused:
[SuperR Kitchen] SuperR.:
Try smali/baksmali
[SuperR Kitchen] bluflight:
we tried one week ago but rom be very laggy and same problem to memory. With new method no more lag but yet memory issue
[SuperR Kitchen] SuperR.:
I have heard about this problem before on N but unfortunately I don't know what is causing it. If you find out please let me know.

Have you tried with and without removing META-INF from apk files? Have you tried with and without zipalign?
[SuperR Kitchen] :
Then don't deodex? Odex is faster (apparently).
[SuperR Kitchen] bcrichster:
Some ppl deodex for theming purposes or using GravityBox (Xposed)

Sent from my N9515's cm12.1
[SuperR Kitchen] bluflight:
We give a try to all options [emoji106]

Yes odex is little more faster, but for some mod to framework we need all deodex

Inviato dal mio ONEPLUS A3003 utilizzando Tapatalk
[SuperR Kitchen] smd0bidaoui:
I will try
[SuperR Kitchen] brainvision:
hi there again guys..

I'm trying to deodex a new tablet, CPU is Mediatek 8163, ARM 64..

I extracted the system.img and navigate it to see what's inside; found something weird, that I never saw before! Many apps have two deodex arch files, both ARM both ARM64!

Somethng like that

system/app/AtciService$ tree -hal
.
├── [4.0K] arm
│** └── [160K] AtciService.odex
├── [4.0K] arm64
│** └── [204K] AtciService.odex
└── [3.0K] AtciService.apk

2 directories, 3 files

what's happening here? Is that normal?
[SuperR Kitchen] Thorvic777:
I think it is because of the architecture... to get both 64 & 32bit compatibility... :)

There is a main apk and then to odex files... one for arm64 and the other for arm(32bit)

Enviado desde mi SM-G800H mediante Tapatalk
[SuperR Kitchen] Er. Aditya:
as of now what i have understood

1. extract system from ext4

2. then extract csc when this step is done kitchen automatically moves all system extracted files outside this main folder and name it to old stuff

3. so after then we gotta place them manually into the defined folders

it would be good if kitchen does it automatically
[SuperR Kitchen] SuperR.:
I am happy to add this feature to the kitchen, but first you should understand that i have no idea what csc is. If you help me understand or link me to a guide (for linux) it would be very helpful. Thanks
[SuperR Kitchen] SuperR.:
I found an error in my script responsible for all the priv-app errors on the N6. Will get the update posted asap.

Regarding the already deoedexed apps, the reason it says that is because the apk already contains classes.dex. In the past this has always meant it was deodexed. Something may have changed on M so someone will need to test to see if those apps fail once installed. I don't have an M device to test on.
[SuperR Kitchen] SuperR.:
Please only send the mmc devices once they are complete and known to be working. Otherwise I won't know which ones are not complete and I don't have time to go through and try to figure it out. Thanks
[SuperR Kitchen] fhem:
Thanks --- I will give those a test and let you know --- I did notice they already contained classes.dex but they also have odex files associated with them so...............not sure what's going on LOL
[SuperR Kitchen] :
I'm so sorry I meant to write cache.img. On Sammy roms there is normally boot.img system.img cache.img and hidden.img. The cache and hidden img normally contain csc files (carrier specific code) plus some carrier apps/bloatware. It's quite useful to have as some of the apps are sometimes needed. On archi litchen when you select the cache.img during extraction it does both cache and hidden img as I think they are connected
[SuperR Kitchen] Er. Aditya:
CSC is the Carrier specific Code. It contains the files for customisation for specific networks, so will have the APN settings, maybe custom ringtones or backgrounds, and can have programs too. Some CSC files contain a lot more than others, hence the file size differences.The CSC firmware file contains a list of definitions for determining which network you are connected to.

its availabe in cache.img.ext4 inside rom.tar zip file its a very important feature

now adding the way to include this in your amazing work bro , i am totally unaware of

on windows cygwin disk2integral did the trick