yashsingh1/xdaforums huggingface dataset:
[SuperR Kitchen] SuperR.:
You might be missing a dependency that I don't have in the list. Please open a terminal and do the following:

cd /YOUR_KITCHEN_DIRECTORY/tools/boot/mkbootimg
make

Please post the terminal output. Thanks

You can run "make clean" in the same directory to remove all the generated files.
[SuperR Kitchen] jenkins-84:
OK thanks I'll try again later see what happens

---------- Post added at 06:58 PM ---------- Previous post was at 06:20 PM ----------

Here you go [emoji1]
[SuperR Kitchen] SuperR.:
Please try the following in terminal:

cd /YOUR_KITCHEN_DIRECTORY/tools/source/mkbootimg
unset CROSS_COMPILE
make

If this works and you end up with mkbootimg and unpackbootimg binaries, move them into /YOUR_KITCHEN_DIRECTORY/tools/. Do the same with /YOUR_KITCHEN_DIRECTORY/tools/source/img_tools, and copy simg2img and img2simg into /YOUR_KITCHEN_DIRECTORY/tools/. Run the kitchen again.

You can run "make clean" in the same directory to remove all the generated files.

This might also help get the binaries compiled

sudo apt-get install build-essential

The 32/64-bit binaries are available in post #4 if you absolutely can't get it to compile. Just extract the zip, and copy the tools directory over the kitchen tools directory overwriting any files that may exist.
[SuperR Kitchen] Omel:
i also have this issue building my rom 5.1.1 for note edge
[SuperR Kitchen] :
Just updated with git clone opened the kitchen and got a missing dependencies error for lzop
[SuperR Kitchen] SuperR.:
sudo apt-get install lzop
[SuperR Kitchen] :
I know my friend is was just surprised, first time your excellent work has ever thrown my an error ?
[SuperR Kitchen] jenkins-84:
working now mate cheers thanks for the help :P
[SuperR Kitchen] SuperR.:
Could you please tell me what worked? Thanks :)
[SuperR Kitchen] jenkins-84:
Well I tried both I'll remove that files from zip and try that again to see if was package install or the files in zip later tonight.

The rom built with system.dat but didn't boot was stuck in boot animation.

I tried using

* Pulling system size via adb

* manually adding

* Using from system.IMG

The way I have normally done it is using the same method xpirt does on his thread works fine for me.
[SuperR Kitchen] Hamidreza2010:
[MENTION=5787964]SuperR.[/MENTION] dear i want to change set perm type to set_meta date but get this error:

mkbooting and unpacking could not be built

same result for making full rom zip

i,m on linux mint 17.2 and xperia z ( c6602 )
[SuperR Kitchen] SuperR.:
The kitchen uses xpirit's method so I am not sure what is going on.

http://xdaforums.com/showpost.php?p=63657384&postcount=769
[SuperR Kitchen] jenkins-84:
I'll run some more test builds tonight see can find out what the problem is
[SuperR Kitchen] Hamidreza2010:
thanks but get this error:

Your kernel does not appear to support selinux.

You will need to use set_perm.
[SuperR Kitchen] SuperR.:
Please send your boot.img and build.prop so i can have a look.
[SuperR Kitchen] Hamidreza2010:
Ok here you are.its for sony xperia z ( c6602 ):

http://d-h.st/YNpW

i,m wait for your help.

just a question: whats different between set_metadata & set_perm and sparse dat ?

thanks a lot
[SuperR Kitchen] SuperR.:
That is not a valid boot.img and is not unpacking. Get a valid boot.img for your device and everything should work.

Google is a good resource
[SuperR Kitchen] Hamidreza2010:
Its a stock kernel.how can provide a valid boot.img?

i extracted from .ftf file and i have other boot.img , get same result

i should tell this when i flashed this kernel every thing is ok
[SuperR Kitchen] SuperR.:
Not sure what to tell you. Try unpacking this boot.img with other tools. It will not work.

Your file:

superr@studio:~/android/SuperRs_kitchen/superr_sony$ file boot.img
boot.img: ELF 32-bit LSB executable, ARM, version 1, statically linked, stripped

Nexus 6 boot.img:

superr@studio:~/android/SuperRs_kitchen/superr_nexus6$ file boot.img
boot.img: Android bootimg, kernel (0x8000), ramdisk (0x2000000), page size: 2048, cmdline (console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidbo)

Samsung Note 4:

superr@studio:~/android/SuperRs_kitchen/superr_note4$ file boot.img
boot.img: Android bootimg, kernel (0x10008000), ramdisk (0x11000000), page size: 2048

Notice how your file does not say Android bootimg

edit: if you can get it unpacked somehow, copy the file_contexts file from the ramdisk into your 00_project_files directory. Then you will be able to use set_metadata and sparse_dat.
[SuperR Kitchen] Hamidreza2010:
ok i,ll try and come back to you

thanks
[SuperR Kitchen] jenkins-84:
[MENTION=5787964]SuperR[/MENTION] the fix for the mkbootimg issue was the sudo apt-get install build-essential. I also managed a boot with build zip but had to make a new_system.img from my ext4 system file and manually add system partition size before full rom.zip too
[SuperR Kitchen] SuperR.:
How did you get the system partition size that you manually entered?
[SuperR Kitchen] DarkHeart Z:
I tested your new 32 bit support for boot/recovery utils under my 32 bit linux ubuntu . I tested it with jelly bean 4.2.2 bootimg , kitkat 4.4.2 bootimg and lollipop 5.1 bootimg and a few recoveries too . But all are mtk and it works flawlessly . 1st I thought there is issue with device detection but later i got that you moved those under tools now . But I think they were better before in the kitchen root folder . Anyways your boot/recovery section works now for 32 bit linux and that solved all my stuck issues now :)
[SuperR Kitchen] SuperR.:
v0.9.3.9

Changes:

Added another format to detect for recovery.fstab when detecting mmc from recovery.img.

simg2img and img2simg are now compiled from source.

New tools/source directory where all source will live.

Added unset CROSS_COMPILE command before compiling.

Added a suggestion if compiling fails.

All binaries will be compiled on first run after a kitchen update. If the binaries are not compiled you will be forced to exit the kitchen and fix the problem. I plan to collect 32-bit binaries (i already have the 64-bit) and post them separately for those who give up on compiling them. For most, compiling should work without issue.
[SuperR Kitchen] PaulPizz:
I keep getting this error even after build-essential installed...??
[SuperR Kitchen] DarkHeart Z:
I am on it right now . and posting the compiled binaries soon :)
[SuperR Kitchen] SuperR.:
This tells me we are missing something when setting metadata. I may redo the way the kitchen gathers the metadata for the updater-script. It will take some hours but may be worth it in the end.

Regarding your system.img, it worked without issues for me. It first converted sparse to raw, then mounted the raw, copied the files, and continued on. This leaves me confused :o
[SuperR Kitchen] jtash01:
custom debloat fails

The wild cards don't work. Get tons of stat failures. having folders only in the debloat list does not work either. The custom debloat ends up placing the entire system folder into the debloat folder in the device folder.

Should I send you my debloat list to test?
[SuperR Kitchen] Androidwizzard:
Honestly, debloating is a thing which developers do manually and may not be defined commonly, as it depends on personal preferences and sometimes deeper knowledge.
[SuperR Kitchen] reefuge:
Like I said IDIOT error - just tried again on ubuntu15.04 with a system.img pulled from rooted phone that i choose every option to remove stuff debloat etc and it loaded but hung at boot

- then tried with a sytem.ext4.tar / extracted and un altered just repacked as a flashable zip and it worked.

one of the problems was in TWRP2.8.5.0 i was deleteing / formatting everything which causes zipped rom to not even start to install (guessing you cant format a non existant /system partition - but just wiping data/cache/dalvik before install allowed rom.zip to flash

will play more..... Think I've found my new toy of the week!
[SuperR Kitchen] BigBot96:
Awesome. Works fine building a ROM for galaxy tab s2 9.7 wifi (sm-t810). So far the only problem is deodexing. The deodex operation doesn't report any errors but the ROM bootloops after flash. Any logs I can attempt to gather for you to assist in the deodex bootloop?

Thanks man

EDIT: here's the deodex log for you.

http://pastebin.com/sFg5uRPr
[SuperR Kitchen] SuperR.:
Looks like your deodex issue is one that I am not able to fix. oat2dex.jar encounters an error on your framework.jar:classes2.dex. The only thing I can suggest is to try the newest oat2dex.jar found here. I have no idea if it will work for you, but it may be worth a try. Just download it and replace the current version in the kitchen tools directory. Make sure you store the original somewhere in case it breaks completely. Good luck :)
[SuperR Kitchen] BigBot96:
I'll give that a try, thanks man.

So, is it safe to assume that it's encountering errors on each of the files that give me a: Unresolved INVOKE_VIRTUAL_RANGE...?
[SuperR Kitchen] SuperR.:
Honestly, your guess is as good as mine on this one. I am no expert in oat2dex.jar and have not encountered these errors on any of the 5.x.x roms I have worked on. There may be a way to contact testwhat, the developer of oat2dex.jar, and ask about these errors as I am certain he would know more than I do. I wish I could help more.
[SuperR Kitchen] BigBot96:
No problem. I appreciate the feedback.
[SuperR Kitchen] SuperR.:
v0.8.8.9

changes:

Added app/lib and priv-app/lib symlinks to the custom zip if they exist and if those directories are part of the custom zip chosen.

Changed kitchen updates to only be available when a new zip is uploaded. This way, git cloned kitchens won't grab updates that are not completely tested by accident. Of course you can still manually git pull if you want to update anyway.
[SuperR Kitchen] mirosaw2:
great work,

but one question, can i use this kitchen to compile alcatel roms which can be found HERE ??,

if the answer is no, then how can i compile this rom and make it ready for flashing ?

thx in advance.
[SuperR Kitchen] bcrichster:
Your link keeps giving a "501 error".

As for compiling a ROM with this kitchen: I may be misunderstanding your intent, but this kitchen is a kitchen to "Cook" ROMs, not a compilation environment that builds from source. However if you have a this device and it's Rooted, then you can plug device up to PC and extract a ROM to work with from the device itself.. [emoji41]
[SuperR Kitchen] nghia0423:
New to linux and kitchens

I can't seem to get past this point. I've tried on ubuntu and debian. Could someone help me?

http://postimg.org/image/m9m87611p/

EDIT: I extracted the zip and put the files into a folder called Superr. Maybe the location is the problem?
[SuperR Kitchen] mirosaw2:
this is what i get when i try to choose 6) ROM tools, and is you can see this is the files extracted from the file i've downloaded,

it's for Alcatel OT-993 not 993D and i can't find any custom or stock rom for this model, only found that source code which has to be compiled first so i can be able to flash via custom recovery,

i've been searching around for any guide or tut for compiling it but i couldn't find any,

so, if there is someone knows how to do that, please let me know.
[SuperR Kitchen] SuperR.:
I could be wrong, but that looks a lot like source file directories to me. This kitchen is not capable of compiling Android from source.
[SuperR Kitchen] mirosaw2:
first of all, thank you trying to help me,

second of all, it's an Alcatel OT-993 (not 993D), and i have the device, but it's not booting anymore cuz i flashed it with 993D rom,

third of all, i don't know about building from source code, but i have this files and i know it need to be compiled,

File name: OT_993_ICS_20130130.tar.xz

Content:

-Folders:

external kernel system

--External:

bison dbus genext2fs jpeg qemu
blktrace dnsmasq grub libffi quake
bluetooth e2fsprogs hostap libpcap webkit
bluez elfutils iproute2 libpng wpa_supplicant
chromium esd iptables ppp wpa_supplicant_6

--Kernel:

AndroidKernel.mk crypto init MAINTAINERS samples virt
arch Documentation ipc Makefile scripts
block drivers Kbuild mm security
chromeos firmware Kconfig net sound
COPYING fs kernel README tools
CREDITS include lib REPORTING-BUGS usr

--System:

arith.c

If you can help me compile these files, that would be much appreciated,

and i've tested the link and it's working.
[SuperR Kitchen] bcrichster:
Unfortunately neither myself or this kitchen can do that (yet) but maybe someone (@EarlyMon , [MENTION=2708182]unforgivin[/MENTION], [MENTION=416534]mikedt[/MENTION]?) over in Alcatel Root section may be able to assist..
[SuperR Kitchen] nghia0423:
Derp thanks for the reply. I thought we just select the number and it opens the script, I just came from Ricky's Rom kitchen. It works now, gonna test it out.
[SuperR Kitchen] Androidwizzard:
From my point of view the kitchen shouldn't abort or deny repacking kernel only because of missing kernel path as it can be added at any stage before flash the package. Just a thought...
[SuperR Kitchen] mirosaw2:
Thank you anyway guys .. :)
[SuperR Kitchen] SuperR.:
As of now, the only ones that are compiled are :

mkbootimg

unpackbootimg

simg2img

img2simg

Thanks :)

Oh, and make sure you are on v0.9.3.9, otherwise you are not getting the simg2img and img2simg binaries we need.
[SuperR Kitchen] DarkHeart Z:
It is done . just remove .img extension from them and they are good to go . All the 32 bit binaries are ready now and attached here :)

P.S: Xda didn't added support for linux binary that's why i had to put .img in the end . It will not create issues I tested it .
[SuperR Kitchen] SuperR.:
32-bit and 64-bit binaries have been packaged and added to post #4. Thanks [MENTION=5844027]DarkHeart Z[/MENTION] for uploading the 32-bit.

I strongly recommend you figure out how to get them to compile on your machine, because you will need to add them back every time you update the kitchen otherwise. I did it this way so if the source changes you are forced to compile new binaries on every update.
[SuperR Kitchen] Dior DNA:
[MENTION=4638690]ferbulous[/MENTION] : Which device did you try? I tried jiayu s3 LP (a while ago) and also could not receive SMS.

I will soon try again, but, l am curious to know if the issue meanwhile got resolved for your device.
[SuperR Kitchen] hohassan444:
on ubuntu 64 , cannot compile though i have build essential.
[SuperR Kitchen] SuperR.:
Check this post

http://xdaforums.com/showpost.php?p=63657384&postcount=769
[SuperR Kitchen] PaulPizz:
[MENTION=5787964]SuperR.[/MENTION]

Thank you!
[SuperR Kitchen] jenkins-84:
You can get the partition size of the actual size of the ext4 file in properties, mines 2.1GB (2126376960) bytes. My rom size ATM after I removed unwanted files is 986MB compression size is 562MB but I always use the same size has the original Ext4 system file size even when files are removed...
[SuperR Kitchen] DarkHeart Z:
bro you can give a check arguements for the precompiled binary . such as if the kitchen checks for which which linux bit I am on it will always redirect to the 32bit binary directory . If the ubuntu is 64 bit it will redirect to the 64 bit directory . I think that can do the trick . And it's a good idea . At least source changing will not be a burden now :)
[SuperR Kitchen] hohassan444:
thanks [MENTION=5787964]SuperR.[/MENTION]....but :

1 - mkbootimg......no problems

2 - image_tools.....give me this error ..........fatal error: zlib.h: No such file or directory
[SuperR Kitchen] PaulPizz:
wc -c system.img
[SuperR Kitchen] jenkins-84:
Eh? Lol

Sudo mount -t ext4 -o loop system.ext4 output/

Then

With SU command

.make_ext4fs -T O -S file_contexts -l 2126876960 -a system system_new.img output/

That's how I get my new_system.img
[SuperR Kitchen] Dior DNA:
OK thanks.

here is a similar logcat I saved upon SMS reject.

D/PowerManagerService( 783): acquireWakeLockInternal: lock=75067800, flags=0x1, tag="GsmInboundSmsHandler", ws=null, uid=1001, pid=1671
D/PowerManagerNotifier( 783): onWakeLockAcquired: flags=1, tag="GsmInboundSmsHandler", packageName=com.android.phone, ownerUid=1001, ownerPid=1671, workSource=null
V/ActivityManager( 783): Broadcast: Intent { act=android.provider.Telephony.SMS_REJECTED flg=0x10 (has extras) } ordered=false userid=0 callerApp=ProcessRecord{1fe9627c 1671:com.android.phone/1001}
D/ActivityThread(21054): BDC-Calling onReceive: intent=Intent { act=android.provider.Telephony.SMS_REJECTED flg=0x10 cmp=com.android.mms/.transaction.SmsRejectedReceiver (has extras) }, receiver=com.android.mms.transaction.SmsRejectedRe ceiver@1fd8170c
D/Mms/Txn (21054): SmsRejectedReceiver: onReceive() intent=Intent { act=android.provider.Telephony.SMS_REJECTED flg=0x10 cmp=com.android.mms/.transaction.SmsRejectedReceiver (has extras) }
D/Mms/Txn (21054): Sms Rejected, reason=2
D/ActivityThread(21054): BDC-RECEIVER handled : 0 / ReceiverData{intent=Intent { act=android.provider.Telephony.SMS_REJECTED flg=0x10 cmp=com.android.mms/.transaction.SmsRejectedReceiver (has extras) } packageName=com.android.mms resultCode=-1 resultData=null resultExtras=null}
D/PowerManagerService( 783): releaseWakeLockInternal: lock=75067800 [GsmInboundSmsHandler], flags=0x0, total_time=3019ms
D/PowerManagerNotifier( 783): onWakeLockReleased: flags=1, tag="GsmInboundSmsHandler",
packageName=com.android.phone, ownerUid=1001, ownerPid=1671, workSource=null
[SuperR Kitchen] PaulPizz:
That command will give you your total bytes. Should have been more clear. Sorry.
[SuperR Kitchen] jenkins-84:
You don't need a command to get the size I said its in properties, just right click on ext4 file and click properties tells you there...
[SuperR Kitchen] SuperR.:
Please download the attached zip, extract it, cd to the extracted directory in terminal, and run make. Let me know if this one builds the binaries for you. Thanks
[SuperR Kitchen] SuperR.:
Sadly, I do need a command to get the size in the kitchen. For some reason the method I am currently using does not seem to get it right for your image. Would you mind opening a terminal in the directory where your system.img is and running these commands? It will be helpful to know if either of them produces the same number you entered manually to get the kitchen to build. Thanks

wc -c system.img | awk '{ print $1 }'

bsize=$(tune2fs -l system.img | grep "Block size" | awk '{ print $3 }'); bcount=$(tune2fs -l system.img | grep "Block count" | awk '{ print $3 }'); sysimgsize=$(($bcount *$bsize)); echo "$sysimgsize"
[SuperR Kitchen] SuperR.:
I will not be able to help with the sms issue. If you figure it out and there is something that can be changed in the kitchen to fix it, let me know.

I got the impression from a previous post that the odexed rom worked with sms. If that is the case, don't deodex ;)
[SuperR Kitchen] eskamhl:
Hi, first of all thank you for this great tool but I have some problems.

I have no issues with building the rom, but with sparse_dat method my phone remains stuck at the bootlogo and with the metadata method I get no modem ( I tried to flash it through fastboot but even after that it's still "unknown" ).

This happens even if I don't make any modification with the kitchen, I tried to build it right after the extraction and it doesn't work.

I'm with a moto x play xt1562 and I started from a stock firmware, does anyone knows if something else is needed in order to make a custom rom for a motorola phone?

PS: I'm on ubuntu 15.04 ( 64 bit ) and I tried all kitchen's versions from the 0.9.3.5 till now
[SuperR Kitchen] SuperR.:
If you are having trouble with the kitchen not compiling binaries, you can try installing these packages. There are probably more packages here than you need, but this should cover most compile issues.

Paste into terminal, press enter, type your user password and press enter:

sudo apt-get install lzop bison gperf build-essential zlib1g-dev zlib1g-dev:i386 g++-multilib libxml2-utils bzip2 libbz2-dev libbz2-1.0 libghc-bzlib-dev dpkg-dev make
[SuperR Kitchen] hohassan444:
unfortunately...it also fails (cannot find -lz )....but after installing above packages....compiling running well now.

thanks a much for your help and support.
[SuperR Kitchen] SuperR.:
Try installing the packages from the post above your last one, then try to compile in the kitchen again. If you added the binaries already, just delete them from /kitchen/tools and open the kitchen again.
[SuperR Kitchen] SuperR.:
Thank you for the feedback. I have added this issue and solution to post #4 for easy access :)
[SuperR Kitchen] zameer_yus:
need help

i modify system.img to add some additional apps into /system/app/ directory i did modification then build a new system.img after flashing phone with new system.img the app was appear in menu but once i am trying to open it gives me error (com.xxxxxx.andriod) stopped working then i execute ls -Z command in /system/app/ directory to see the different and i realize that the new app i copied in system/app/ directory it has a different label than others

so i tried to change .apk file label to (u: object_r:system_file:s0) using chcon command but failed

chcon: Could not label u: object_r:system_file:s0

can you please guide me how to do it ?
[SuperR Kitchen] SuperR.:
v0.9.4.0

Changes:

Changed system.img size detection to use wc instead of tune2fs.

make_ext4fs is now compiled in kitchen.

Added the package install list from post #4 to the compile error page for easy access.

edit: Can someone running 32-bit Linux zip/upload the following binaries located in the tools directory after running this version?

simg2img

img2simg

make_ext4fs

Thanks
[SuperR Kitchen] not-i:
Working on Nexus 6P firmware. Just cooked a rom and successfully deodexed it on marshmallow. Boots fine and all seems good. Thanks for your hard work with the kitchen mate :)
[SuperR Kitchen] DarkHeart Z:
Bro no worries I am here and ready to do it . Sending the compiled binary right to you :)

Edit : something else is wrong bro . Kitchen is saying it's up to date . Not updating anymore . I tried updating 0.9.3.9 to 0.9.4.0 it's not updating :(
[SuperR Kitchen] SuperR.:
The updater should work now :)

v0.9.4.1

Changes:

Fixed kitchen updater when there are zips in the repo that are not Kitchen zips
[SuperR Kitchen] DarkHeart Z:
learnt something from you about how to become faster . I attached the 32 bit binaries as you requested . just remove .img entensions and you are good to go :)
[SuperR Kitchen] Er. Aditya:
your a super being , awesome work man
[SuperR Kitchen] albertmurcia:
leave this to me and not to go out, I do?

Enviado desde mi SM-T805
[SuperR Kitchen] SuperR.:
sudo apt-get install gawk
[SuperR Kitchen] albertmurcia:
Thanks you [MENTION=718594]super[/MENTION]R

Enviado desde mi SM-T805

---------- Post added at 09:43 PM ---------- Previous post was at 09:26 PM ----------

when I put on file and boot.img system.img?

Enviado desde mi SM-T805
[SuperR Kitchen] SuperR.:
Read post #3 for usage instructions
[SuperR Kitchen] SuperR.:
v0.9.4.2

Changes:

Fixed a bug in the updater that will not allow you to update if ping fails.

Fixed an error about make_ext4fs after updating.

Added a check for rimg2sdat dependencies since it is a 64-bit binary and closed source so we can't build it. Now you will get a warning that sparse_dat will not work correctly on 32-bit.
[SuperR Kitchen] DarkHeart Z:
That means working on lollipop rom will be unavailble for now ? looking for a source too . Will let you know I get any available :(
[SuperR Kitchen] bcrichster:
LP and above is 64 bit.. always has been. Makes sense.. A lot of newer PC's are 128 bit and higher now. So 32 bit is gonna be continually harder to work with being as its becoming so obsolete

Gratefully sent from my Rooted JollyRoger_B13
[SuperR Kitchen] george0884:
How add support for G900H?

Enviado desde mi SM-G900H mediante Tapatalk
[SuperR Kitchen] enotar:
Can Samsung SM-P600 suported? Thank you
[SuperR Kitchen] DarkHeart Z:
got it bro . All phone is becoming 64 bit either . sigh!!!!! :rolleyes: