yashsingh1/xdaforums huggingface dataset:
[SuperR Kitchen] bdorr1105:
When I tried building the ROM zip it built it with ppus, so I had to add h901 since it did the build.prop check and would not allow me to flash, I added the folder in devices and I was good to go after that. I will try to pull the system.img in recovery with the kitchen, learn new stuff daily and I built a Rom with this kitchen. Thanks I also mentioned the kitchen
[SuperR Kitchen] bdorr1105:
Did a successful pull in recovery, thanks for all the hard work man, great kitchen!!!!!!!!!!!! I am playing with it daily. Linux Mint is very android friendly
[SuperR Kitchen] bdorr1105:
Was Working, dont know what happened? I installed APK took for linux mint, not sure that effects anything considering the APK tool for this kitchen is contained in the tools folder

Edit: I tried to move it into a folder called "ROM Kitchen" to keep the desktop clean, however, it will not work from inside that folder, only can be on the desktop, not understanding why that occurs, I will check permissions of the folder and report back, its pulling right now so I am going to let it run
[SuperR Kitchen] KingpinZero:
Ok ive got a question.

My phone hasnt got a custom recovery, therefore im able only to edit the system.img and flash it back. Ive succesfully flashed a few mods, but i dont understand how i can pre-root my system.img and boot.img.

The program gives me options to add both SuperSu and Busybox to it, but when i build my system.img i cant find them anywhere. What i do wrong?

And what can i do without a custom recovery? Is it possible to integrate SuperSU in it? Thanks.
[SuperR Kitchen] SuperR.:
Linux terminal does not like spaces in file/directory names, unless you escape them which is annoying. Just rename your directory to "ROM_Kitchen" or "ROM-Kitchen" and you will be all set.

The kitchen does not add root to the system directory anymore due to the different requirements for all the different platforms. It adds SuperSU.zip to the rom zip to be flashed with the rom from a custom recovery.

I suggest you get a custom recovery for your device. If there isn't one available, try to build one yourself or start a thread in your device forum requesting one. If you are not able to do either of these things, you can read other threads regarding adding root to your rom.

Alternatively, if your device is currently rooted, you can extract the system.img from it as a base and it will still be rooted when you build the new system.img.
[SuperR Kitchen] bdorr1105:
Thanks, worked like a charm, didnt even think about it lol
[SuperR Kitchen] sebastiandg7:
[MENTION=5787964]SuperR.[/MENTION] Extraction error was my bad, sorry. Just a question.... what adb command does the kitchen uses to detect the system partition size?

Thank you a lot for this project!
[SuperR Kitchen] KingpinZero:
Ok thank you for your amazing reply.

So im stuck in this situation: theres no custom recovery for it and no one seems interested to help me out into building One (i guess no One likes mediatek MT6735).

So my question is, giving the right specifications would it be possible to manually add root to it?

Its a standard 5.1.1 build, arm64. Ive put SU in xbin, SuperSU in priv-app, the .sh recovery script in etc.

Now im left with another .sh "daemon" and a file that starts with 99 , but i dunno where to put them.

Could yoi just lend me an hand, or point me toward a guide or tutorial where to put those files?

Inviato dal mio XT1254 utilizzando Tapatalk
[SuperR Kitchen] :
Bigrammy is your best bet for mediatek devices. He's one of the most helpful people on xda and follows this thread. I know he's compiled a custom recovery for someone else with a mediatek device
[SuperR Kitchen] KingpinZero:
I hope he saw my message, i would like some form of help.

Or at least someone who could point me to tutorials or guides.

Inviato dal mio XT1254 utilizzando Tapatalk
[SuperR Kitchen] :
This thread may help you with custom recovery.

http://xdaforums.com/showthread.php?t=2748169

Easy Magic PhilZ Touch Installer for MediaTek Devices ONLY (Developers ONLY)

Sorry for the ot SuperR
[SuperR Kitchen] bigrammy:
Hi I am very busy with work and my new Xperia C4 which I just managed to unlock and build a recovery for. :laugh:

Give me a shop link to your actual device or gsmarena so I get see all the specs make model etc

:laugh: Just seen your PM give me a while.
[SuperR Kitchen] KingpinZero:
Thank you but the tool works only with rooted phones :)

Inviato dal mio XT1254 utilizzando Tapatalk

---------- Post added at 10:40 PM ---------- Previous post was at 10:39 PM ----------

No worries man! Hope you can help or tell me what i have to do :) i love learning!

Inviato dal mio XT1254 utilizzando Tapatalk
[SuperR Kitchen] bigrammy:
It doesn't work very well with the newer mt67xx 64bit SoC sadly nor does MTKDroidTools :crying:

So for now we must do things Manually :laugh:

[MENTION=4602121]KingpinZero[/MENTION]

Just ported this from my Siswoo C55 it should work Mijue_T200_Carliv_CWM.img on Copy.com

[MENTION=5787964]SuperR.[/MENTION]

I will be giving your kitchen a workout on my Sony Xperia C4 ROM (mtk6752) now I finally broke in. :D
[SuperR Kitchen] KingpinZero:
Man thank you, gonna test and report back. If you got a sec could you send me a PM with general directions on what you did to port it?

I really want to learn about it, i have the knowledge but obviously im missing something.

I know im asking alot but please, it does really matter to me. Thank you again :)

Inviato dal mio XT1254 utilizzando Tapatalk
[SuperR Kitchen] bigrammy:
Done :)
[SuperR Kitchen] bdorr1105:
I am at a loss here. Could use some really smart people who could possibly help, I been racking my brain, so far I am the only one with this issue that appears unsolvable using ROMs that other people are not having issues with, not sure how this can only be device related, most annoying thing I have ever experienced period....I don't see how it could have happened during the ROM build, please redirect or PM if there is a way to fix this. Thanks

edit* I place the screenshot because I am unable to find a /storage/emulate/0 directory when in adb shell, weird, is that possible to be deleted? dont get it - nvm I see it in root explorer*

Information is here with Logcat
[SuperR Kitchen] Rydah:
Completely unrelated to the kitchen but factory reset your device and reflash system.

Sent From My LG V10
[SuperR Kitchen] SuperR.:
v1.0.0.5

Changes:

Added vendor to the list of images pulled from the device if it exists.

Pulling images should work on mmcblk devices now if there is a superr_mmc file.

Fixed set_perm duplicating perms when updating project.

NOTE: Pulling mmcblk images from custom recovery is untested, but I think it will work. Please let me know if you try it.
[SuperR Kitchen] C y a n i d e ~:
Hi SuperR, I'm still getting a bootloop after following your advices (set_perm to set_metadata; and unroot and rooting the rom)

Btw I'm using 1.0.0.3 in Zorn OS Ubuntu Based.

any other suggestions? Thanks!
[SuperR Kitchen] SuperR.:
Since you did not paste your updater-script, I have pasted the one generated from your firmware after adding root and busybox. Please compare it to yours. If they are different, try updating your kitchen and starting over with a fresh project. They should be identical. If they are identical, you will need to figure out how to fix the bootloop on your own. After you figure it out, I will update the kitchen.

http://hastebin.com/epiqoxoqan.coffee
[SuperR Kitchen] bigrammy:
Which phone and firmware version is it only thing I can find after a quick google for Loin 5 is v4.4.2 :confused:
[SuperR Kitchen] SuperR.:
5.1

Here is the build.prop

http://hastebin.com/ucujoxefox.avrasm
[SuperR Kitchen] JonathanRAZ:
i get permission denied when deodexing 5.1.1 cokc from note 5 tmo [MENTION=718594]super[/MENTION]R
[SuperR Kitchen] ROBERT CM:
Try

Set_metadata
[SuperR Kitchen] JonathanRAZ:
Still same bro thanks but its not deodexing
[SuperR Kitchen] manojpy:
[MENTION=5787964]SuperR.[/MENTION] Tried to build a rom for Samsung Galaxy S5 (k3g). Extracting system.img ends abruptly. Tried perm and meta option. It notifies that this is not Kitkat and beyond rom. The firmware is 5.0 lollipop. Can upload boot and system img if required.

Have had no issues building for Nexus 6.
[SuperR Kitchen] SuperR.:
No clue. Send firmware.

Yes, please send firmware.
[SuperR Kitchen] guitardoc64:
Looks very nice. I guess I'm going to have to dust off my Linux install and give it a go.
[SuperR Kitchen] nghia0423:
Deleting everything in the old_rom_files folder and running the script with root fixed the other problems. The package in the link fixed 11mb zip file it keeps creating as it did not create a raw system image at first. Thanks for your quick responses.
[SuperR Kitchen] SuperR.:
v0.9.0.3

Changes:

If there is only one project when you open the Kitchen, skip the menu and open the project.

Added a menu option in the Boot/Recovery Tools menu to go to the Boot/Recovery Tools menu. This will allow you to easily switch between boot and recovery if you have both in your project directory. (NOTE: you can't switch while there is an unpacked ramdisk)

Minor UI changes.
[SuperR Kitchen] SuperR.:
v0.9.0.4

Changes:

Much faster bloat restore

UI changes - q = Quit on all menus now
[SuperR Kitchen] Methamphetadreams:
There is not, no. That's one problem I always run into while using unknown brands. The phone itself is extremely well crafted and certainly deserves more recognition. Sadly, it has none due to being foreign to my country. I was hoping I would be able to circumvent the need for a custom recovery and be able to flash Cyanogenmod from the stock recovery as a pseudo-update. I suppose that is not the case?
[SuperR Kitchen] SuperR.:
No it is not. You would need the private signing key in order to flash from stock recovery. If your device is rooted, you could dd a system.img but this is not safe unless you have a custom recovery. If the system.img is corrupt you will not be able to boot to your device and will not be able to dd your old system.img back. If it were my device I would avoid this disaster waiting to happen :)

edit: unless you have access to fastboot and an unlocked bootloader, then you could fastboot flash your new system.img and if it fails fastboot flash your original system.img back.
[SuperR Kitchen] Methamphetadreams:
I know that I am able to build a custom recovery from my recovery directly on clockworkmod's webpage. Is there any alternative ways to getting my recovery and boot images outside of your kitchen? I've already attempted to do all the raw adb stuff myself but I can not seem to obtain either, despite knowing they do exist.

Here is a very poor photo of my phone in recovery. I realized it was possible to boot into it through adb. I'm unsure as to why it is so tough to get this. I've tried all the usual booting hardkey combos. Further info, it shows 'Erasing...' as it boots and then says 'No command.' after a moment. I can't access the text menu until I tap the power button. It's all very strange to me.

http : // i . imgur . com / uP5gf3s . jpg

(Broken link due to xda not allowing new members to link.)

I am able to boot into fastboot through adb, but I'm unsure about the bootloader!
[SuperR Kitchen] SuperR.:
If the only way to get to fastboot is through adb from your booted device, it is still not safe. If you can find a way to get to fastboot from power off you could do some experimenting, but if not I would avoid it or you may end up with a brick.
[SuperR Kitchen] Methamphetadreams:
Eh, I'm looking for an excuse to buy myself the Mi 4, anyway. Do you have any suggestions on how to boot into fastboot outside of adb? No matter how sketchy.

Also, thank you for all of your assistance. I know you must be doing a lot.
[SuperR Kitchen] :
Just tried building a rom for the note4 exynos (n910c ) from latest stock tar download. So far everything seems to be fine just got to flash it now. So much easier being able to extract and deodex all in one place again
[SuperR Kitchen] SuperR.:
Thanks for the positive comment :)
[SuperR Kitchen] Methamphetadreams:
If I have comprehended correctly, I am unable to flash a custom ROM because:

• There is no custom recovery or bootloader for my device.

• Your tool is unable to grab my boot or recovery images.

• Romdump does not dump my boot or recovery images.

• I can not seem to locate or dump my images using the cat commands.

• I need my boot image to make a custom recovery through Clockworkmod.

Where do you suggest going from here? I am willing to do work for myself, but I must know what to do.
[SuperR Kitchen] nghia0423:
Smooth

Sparse dat zip installation went smoothly. Will definitely be using this kitchen from now own. Just wanted to let you know and thanks for all your help Superr.
[SuperR Kitchen] aravpathak:
nice i'll try
[SuperR Kitchen] STEVE_MARS:
Sorry, but my english is awful. I don´t understand this post, and I have same problem, my update.zip is only 11 Mb. How I can fixed it?.

Thanks a lot.
[SuperR Kitchen] stamilselvan:
Hey,, thanks for your work,,

Does this kitchen support huawei devices for building custom rom from stock system.img and boot.img ( also having cust.img)

I ve tried dsixda's kitchen and archi kitchen, but archi kitchen said "compilation terminated, all stages failed" and for dsixda's, he told that newer huawei devices arent supported in his thread.

Please i am hoping only on your kitchen...

Thank you

Sent from my MediaPad T1 8.0
[SuperR Kitchen] SuperR.:
Check post #4 of this thread.
[SuperR Kitchen] SuperR.:
Try it and let us know. If you have trouble, post links to all the img files so I can have a look.
[SuperR Kitchen] bcrichster:
The terminal command - is that only for 64bit Linux? I'm only asking due to still running 32 bit Linux here, Lol
[SuperR Kitchen] SuperR.:
make_ext4fs is a 32bit binary and requires these 32bit libs to run so they must be installed on a 64bit Linux. 32bit Linux should already have these core libs so it should work fine.

I will add this info to post #4 so less people will be confused. Thanks for pointing it out :)
[SuperR Kitchen] Mestreian:
Good job and thank you for providing.
[SuperR Kitchen] JonathanRAZ:
I got it i did an extra step while it was copying system files all i did was copy paste to a folder then moved it to system on project
[SuperR Kitchen] Captain_Throwback:
[MENTION=5787964]SuperR.[/MENTION]

Now that the functions are all working well and an output zip can be produced without needing to make any modifications after built, have you thought about adding an option to sign the zips? That helps end users to ensure they have good, valid downloads and is better than simple md5 verification for validation of uncorrupted zips. It should just be a matter of adding signapk.jar and the Google test-keys to the Kitchen files and running

java -jar signapk.jar -w testkey.x509.pem testkey.pk8 input_file output_file

to sign the zip.
[SuperR Kitchen] SuperR.:
I have now :)

v1.0.0.6

Changes:

Added option to sign your rom.zip after it is built.
[SuperR Kitchen] :
Got to say you must be the quickest, politest and most helpful dev on xda
[SuperR Kitchen] bdorr1105:
I have to agree, especially with some of the noobish comments by me, well I guess this is noobish territory for me as well
[SuperR Kitchen] bigrammy:
+1 to that. :good:
[SuperR Kitchen] josito_theDH:
Thank you my friend for this awesome tool

Working perfect on Ubuntu

Now I can debloat the stock rom and add root because this is all I want

Can't wait to learn more....

Can I add an app to system/app/ ?
[SuperR Kitchen] SpasilliumNexus:
That's the purpose. You extract the ROM so you can do things like debloat and add to it before rebuilding, then flashing.
[SuperR Kitchen] enotar:
All woks well her but I have a request:

For Samsung 5.1.1anyway to have selinux permissive instead of enforcing?

Thank you
[SuperR Kitchen] SuperR.:
That is beyond the scope of the kitchen. However, you can add init.d support in the kitchen and add this script to /etc/init.d to get permissive mode.
[SuperR Kitchen] enotar:
Did not work but tkz anyway
[SuperR Kitchen] C y a n i d e ~:
I've seen some diferrences and seen 3 lines added to my new builded rom.

But I'm bad with this, can you help me?

https://drive.google.com/file/d/0B7cbsEYhU6-cSGc3UUs5VEMtZEE/view?usp=docslist_api

Thank you for the fast response ever since :D
[SuperR Kitchen] SuperR.:
Your problem is almost certainly because you have xposed framework installed in your rom source. Xposed will not work if it is pre-installed. It must be flashed after the rom. Start with the system.img you sent me and you should be fine.
[SuperR Kitchen] sebastiandg7:
+1 surely!

---------- Post added at 04:20 AM ---------- Previous post was at 04:18 AM ----------

@SuperR. I'm giving support of my rom to an other device I do not have, can you tell me how do the Kitchen determine the system size (What adb/shell command you use) so I can make the device owner to give me the system partition size and enter it manually when building the rom zip. Thank you!
[SuperR Kitchen] SuperR.:
It depends on whether the device uses by-name or mmcblk. If it uses by-name, you need to first find out which mmcblk system is (replace "/dev/block/bootdevice/by-name" with correct by-name directory for the device):

adb shell su -C "ls -al [COLOR="Red"]/dev/block/bootdevice/by-name[/COLOR]" | grep system | awk '{ print $8 }' | cut -d"/" -f4

Once you know that, you can use the following command to get the size (replace "/dev/block/mmcblk0p15" with the output from the first command):

echo $(($(adb shell "cat /proc/partitions" | grep "[COLOR="red"]/dev/block/mmcblk0p15[/COLOR]" | awk '{ print $3 }') * 1024))

If you need more help with this, I suggest you use Google or tell your users to download the Kitchen.
[SuperR Kitchen] manojpy:
Here it is:

https://www.androidfilehost.com/?fid=24352994023707487

Thanks in advance.
[SuperR Kitchen] SuperR.:
It extracted without issue for me so I am not sure what is going on.

Here is a rom zip with the extracted system including cache. It is untouched so extract it with the kitchen and do what you want :)

manojpy.zip
[SuperR Kitchen] manojpy:
Thanks for this. I just can't figure out what could be going wrong. I extracted system and boot img and put them in the project folder. Tried to extract using set_meta and set_perm , but no go. Is there any other file that needs to be added in the project folder? If you could briefly explain the process you implemented. I am on 32bit Linux, hence cannot use system.img. Thanks
[SuperR Kitchen] SuperR.:
1. you CAN create and extract system.img on 32-bit Linux. sparse_dat is the one only available on 64-bit Linux.

2. if you use the zip I uploaded, do not extract it manually. Put the zip in the project directory and choose it from the extract menu in the kitchen. It would be best to delete everything in the project directory including 00_project_files before extracting. The only thing that should be in the project directory is manojpy.zip.
[SuperR Kitchen] manojpy:
Sorry my last line should have read - cannot use sparse_dat due to 32 bit

Got your second part, but still would like to know how you did it, else you will be asked to do it for me every three months (sometimes updates take longer with Samsung) [emoji6]

I am not facing any problems with Nexus 6, so I can't figure out what is going right there and wrong here.
[SuperR Kitchen] Captain_Throwback:
[MENTION=5787964]SuperR.[/MENTION]

I tried the zip signing feature, but when I enable signature verification in recovery, the zip fails verification. I had this same problem before, and the only solution I found was using the "Sign-em!" script found here (along with the corresponding signapk.jar. I did make same minor modifications to the script for my personal use (I even tried creating my own signature, but that always failed too), and since doing that, signing has worked. I'm not sure what files you used, but maybe look into what's in that thread and it'll help get it working. Thanks!
[SuperR Kitchen] shoey63:
[MENTION=718594]superR[/MENTION]

You need to replace the signapk.jar in your signapk folder with the one attached.

The command needed to "whole sign" the zip is

java -jar signapk.jar [COLOR="Red"]-w[/COLOR] testkey.x509.pem testkey.pk8 <name>.zip <name>-signed.zip

Did a test run in your signapk folder with the substituted signapk.jar and above command and the zip passed signature verification.

Reference :http://wiki.rootzwiki.com/Signing
[SuperR Kitchen] C y a n i d e ~:
Hi [MENTION=5787964]SuperR.[/MENTION] after uninstalling Xposed, I tried to build the rom again from the start, now I'm getting again the "E:error executing the updater binary blah blah".

updater-script: http://hastebin.com/ewowosixug.coffee

Thanks! :)
[SuperR Kitchen] Captain_Throwback:
Using "-Xmx1024m" breaks signing for me. Just adding -w (as I stated in my original post) works, and the zip still passes verification.
[SuperR Kitchen] shoey63:
You are right. Just tried it, and it's not required. I'll edit my post :p
[SuperR Kitchen] SuperR.:
I did the usual. Created new project, added the system.img cache.img and boot.img to the project directory, chose option 4 to extract system.img, chose set_metadata.

Hopefully the signapk.jar I have added to the new version below along with the -w will work. The one you linked has been modified to change the cert names which I am not fond of. If I need to use that jar so be it but I am pretty sure this one will work fine.

The blah blah part of your post is the only info I could have used it were there. I am guessing you need to add your device assert. Look at post #4 for more info.

edit: actually, your by-name info is wrong somehow.

This:

mount("ext4", "EMMC", "/dev/block/platform/mtk-msdc.0/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/system", "/system");

should be:

mount("ext4", "EMMC", "/dev/block/platform/mtk-msdc.0/by-name/system", "/system");

Delete /kitchen/tools/devices/Lion-5 and update the kitchen. Then change perm type to raw_img, then change perm type back to set_metadata. This should fix your issue.

v1.0.0.7

Changes:

Hopefully fixed signing zips.

Added a check to be sure the signed zip exists after signing.

Remove existing RSA, SF, and MF files from META-INF when extracting rom zips.
[SuperR Kitchen] Androidwizzard:
Last night I've put an MM system.img (SM-N920T Samsung Galaxy Note 5) into working folder (just for testing purpose) and when it comes to extract options I got only 2+4, cause my system isn't KK or beyond :eek: Kinda bad surprise, right?

Any kind of request or need for help from me - just mentioning, as any1 else could have such prob.

btw: No output choosing option 2 (perm) - not tried 4.
[SuperR Kitchen] SuperR.:
Can you link the firmware?
[SuperR Kitchen] Captain_Throwback:
The version of signapk.jar you included in v1.0.0.7 works fine :good:. Thanks!
[SuperR Kitchen] SuperR.:
v1.0.0.8

Changes:

Added option to sign custom zips.

Added option to sign boot/recovery zips.

Fixed zip names when building boot/recovery zips.

The zip name now shows while building custom and boot/recovery zips.

General cleanup.
[SuperR Kitchen] Captain_Throwback:
[MENTION=5787964]SuperR.[/MENTION]

Thanks for the update!

I just had an issue with the boot.img modifying for Marshmallow again. I still don't think that the boot.img is being unpacked as root in every case where needed, even if it's being repacked as root. As a result, some of my files lost the proper permissions after editing (actually, I think it's just init.environ.rc) and after repacking (even though done as root), the resulting image fails to boot the device. However I've also had the issue with boot images from other devices where unpacking/repacking as root appears to cause permission issues and also results in a no boot situation. So it's difficult to help determine how best to solve this issue.