yashsingh1/xdaforums huggingface dataset:
[SuperR Kitchen] jaylence:
If I'm remembering it correctly, SP Flash Tool let's you create you're own CWM recovery using your stock recovery.

Then flash your newly created cwm recovery using Mobile Uncle Tools.

After that, you'll be able to flash your custom rom.

I've done this method multiple times on my MTK devices before.
[SuperR Kitchen] JRapsky:
Don't know how to flash with fast boot. Could you please guide me step by step?

Gesendet von meinem Y6 Max mit Tapatalk 2

---------- Post added at 07:20 AM ---------- Previous post was at 07:10 AM ----------

The MTKDroid Tool is not working with the 67xx SoC. So I guess thus methode is outdated.

Gesendet von meinem Y6 Max mit Tapatalk 2
[SuperR Kitchen] jonniehere:
How do you do that with recovery then?

Jrapsky, you would need to install android SDK

Then Google search the commands I haven't got enough time to type it all out for you sorry. And this is for his kitchen.
[SuperR Kitchen] KaMyKaSii:
Just make your modifications in boot.img and repack, choose perm as "raw img" (to generate the system.img). Then install both by SP FlashTool.

By the way, what's your Android device and version? Could you send me your stock recovery?
[SuperR Kitchen] JRapsky:
My device is a Doogee Y6 Max, Android version is Android 6.0 (dido OS V7.0). The stock recovery is larger then the limit for the file upload. Please take this one here
[SuperR Kitchen] SuperR.:
v2.1.4.0 (Donate version)

Changes:

ROM will now detect active slot on Pixel devices and flash to it (thanks to [MENTION=5169465]mdalexca[/MENTION] for the slot detection method and support).

Prevent using sparse_dat on Pixel devices since it won't work.

Hopefully added Pixel device support for cygwin.

Fixed set_metadata perm type being chosen automatically when extracting a new rom.

Updated SuperSU to v2.79-SR2.

v1.1.3.0 (Standard version)

Changes:

ROM will now detect active slot on Pixel devices and flash to it (thanks to [MENTION=5169465]mdalexca[/MENTION] for the slot detection method and support).

Prevent using sparse_dat on Pixel devices since it won't work.

Hopefully added Pixel device support for cygwin.

Fixed set_metadata perm type being chosen automatically when extracting a new rom.

Updated SuperSU to v2.79-SR2.

NOTE: I did not get any feedback about the Pixel test kitchens working on non-Pixel devices so it is all incorporated into the main kitchen. Maybe now I will hear about it if it does not work :)
[SuperR Kitchen] tanish2k09:
Thank you so much [MENTION=5787964]SuperR.[/MENTION] For this awesome tool.

This tool is the reason I could port cm14.1 to my device, being the first person on my forum to boot it using MM-kernel.

Giving 99% of all credit to you ;)

I promise to mention your name the first if I ever post the ROM to my forum.
[SuperR Kitchen] Guizão BR:
I tryng compile Miui 8 but i get the error:

"Make sure your partition size is correct and

that the directory is not too big to fit."

But others ROMs like cm13 work very well... I using the last version 1.1.3.0

edtit: link of original ROM http://www.needrom.com/wp-content/uploads/2016/12/MIUI8_1.zip
[SuperR Kitchen] ShinySide:
Am I missing something or is there a reason why people are "cooking" cm/aosp/miui roms? Lol
[SuperR Kitchen] nightcrow:
Updated the kitchen this morning to 2.1.4.0 (donate version) and cooked a stock Samsung 6.0.1 rom, odexed and debloated, and getting an error 7 while flashing in recovery. Seems to be something wrong with the asserts, however I haven't changed a thing in the asserts section in the kitchen.
[SuperR Kitchen] Svan987:
Same here i was becoming crazy thinking was on my side until i did identical build than with Kitchen 2.1.3.9 and got same error :eek:
[SuperR Kitchen] Captain_Throwback:
[MENTION=5787964]SuperR.[/MENTION]

Looks like a slot selector error, which I guess is Pixel related?
[SuperR Kitchen] SuperR.:
v2.1.4.1 (Donate version)

Changes:

Hopefully fixed the /tmp/slotsel error when flashing.

v1.1.3.1 (Standard version)

Changes:

Hopefully fixed the /tmp/slotsel error when flashing.

edit: I recommend deleting all files in your project and extracting your ROM again to make sure all the new parts get added. If you don't want to do this, you can change perm types to something else and back to whatever you want. Then you will need to replace /kitchen/superr_project/config/slotdetect.sh with /kitchen/tools/updater/config/slotdetect.sh. If you are working on a Pixel rom, also delete /kitchen/00_project_files/file_contexts and /kitchen/00_project_files/file_contexts2 before changing perm types.
[SuperR Kitchen] Svan987:
Thanx a lot for the fast patch ;)

Working again, but got a matter :laugh:

I am using "Mods Install" plugin. The mod i am using has only an update-binary file in "META-INF" tree. When i flash the mod alone i can see all the job in the log.

When the mod is in the rom script i see nothing in the log when flashing.

Do you think the mod need a dummy updater-script ?

Thanx.

Cheers.
[SuperR Kitchen] Tkkg1994:
Hey dear [MENTION=5787964]SuperR.[/MENTION]

I've found an interesting busybox which is much more updated and also supports magisk, you may want to take a look and eventually include it to your kitchen by default:

Multi-Arch busybox
[SuperR Kitchen] SuperR.:
The mods install plugin only works with zips that use an update-binary script rather than updater-script and update-binary. You could ask the mod maintainer to create this type of zip.

I am pretty sure the current Busybox installer by [MENTION=4544860]osm0sis[/MENTION] works with Magisk. It certainly works as systemless and he normally keeps it updated. Maybe he will chime in :)
[SuperR Kitchen] nightcrow:
Rebuild the rom with the latest patch but still an error when flashing in twrp recovery, this time it can't mount /system :confused:
[SuperR Kitchen] lonegolfs15:
where i can dowload v2.1.3.9 donate version?
[SuperR Kitchen] SuperR.:
Did you delete everything in the project directory and extract your rom again, or follow the instructions I posted with the update?

SuperRs_Kitchen_v2.1.3.9
[SuperR Kitchen] chevycam94:
[MENTION=5787964]SuperR.[/MENTION], I'm having a bit of a problem now:

What Kitchen version?

- v1.1.3.0

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

- 64-bit Linux (guest system in VirtualBox)

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

- Nexus 6P (angler)

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

- Google factory image (N4F26J) for the Nexus 6P

What Android version?

- 7.1.1

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

- set_metadata

What did you do after extracting and before building?

- Extract for new ROM, selected set_metadata (as I have before). Once I name the zip, as soon as I hit enter, I see an error Ive never seen before.

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

- Preparing updater-script ...

7004 blocks

cp: cannot stat '/home/noah/android/kitchen/superrs-kitchen/tools/boot/file_contexts': No such file or directory

I don't know if this is the cause of my ROM not booting, but this is the first time I've gotten an error, and also the first time my builds don't boot. I've built all my previous builds (up to v1.1.2.8) the exact same way, on the same system. Not sure why this is happening. Might also have something to do with the new lines in updater-script that were for Pixel compatibility (slots).
[SuperR Kitchen] osm0sis:
If you think because I didn't have 1.26.0 I'm "not up-to-date" that's incorrect. 1.x.0 releases are always labeled unstable so I only release the ones labeled stable. Simple.

As YDS himself will tell you, our busybox builds are different because he builds with uClibc and I build with the Android NDK. Both have their advantages and their drawbacks. :)

Magisk support really doesn't matter for SuperR Kitchen-based ROMs since it'll just install to system (if there's no systemless root detected) and that should be fine, but I am looking into adding Magisk support to the installer probably next week when I'm going to do the bring-up to busybox 1.26.1 for my NDK patch repo:

https://github.com/osm0sis/android-busybox-ndk

I've had systemless SuperSU su.img installation support since that became a thing. ;)
[SuperR Kitchen] SuperR.:
The latest update should fix your issue. Make sure you read the instructions I posted with the update.

Thank you, looking forward to it :)
[SuperR Kitchen] TheLogicalGamer:
I'm getting this in twrp while trying to flash a custom app, priv-app zip

Checking config...

Mounting System...

file_getprop: failed to stat "/tmp/slotse1":No such file or directory

Updater process ended with ERROR: 7

I completely deleted the project & extracted again as per instructions in update post. I'm on Ubuntu 16.04 LTS. My device is an LG G3 D851. Using Kitchen v2.1.4.1. Thanks for any help. :)
[SuperR Kitchen] nightcrow:
Yep, I deleted the whole project, created a new project and extracted the rom again like your said. I'll also switch back to 2.1.3.9 for now.
[SuperR Kitchen] tanish2k09:
[MENTION=5787964]SuperR.[/MENTION]

After extracting everything, I wanted to make changes to the boot.img to change the kernel.

I didn't find any file "boot.img-kernel" to replace it with the kernel I want...

Is that one of the tricks of the kitchen?:confused:
[SuperR Kitchen] bcrichster:
The boot.img IS the kernel. [emoji41]

Sent from my N9515 PAC-ROM
[SuperR Kitchen] Captain_Throwback:
No it isn't....in INCLUDES the kernel, though ;).

Once the boot.img is unpacked, I think the file [MENTION=5913332]tanish2k09[/MENTION] is looking for is boot.img-zImage.
[SuperR Kitchen] bcrichster:
Oh OK!

Sent from my N9515 PAC-ROM
[SuperR Kitchen] tanish2k09:
Yes, boot.img itself is not the kernel.

And thanks for replying, but can you be more certain about the file "boot.img-zImage"?? I need to be sure. You wouldn't want the wrong file to be replaced :D
[MENTION=5787964]SuperR.[/MENTION]

Any light?
[SuperR Kitchen] Captain_Throwback:
Not sure why you don't believe me? I've done it plenty of times. Once you unpack the boot.img, in the split_img folder, the kernel is the file ending in zImage. Or don't believe me, whatever.
[SuperR Kitchen] tanish2k09:
Actually, I paid too much attention on your words "I think" in the previous post. Of course I believe you (by looking at your title).

And maybe you can help me more... I have boot.img-zImage in the extracted folder, but the kernel of my choice is in boot.img-kernel:confused:
[SuperR Kitchen] Captain_Throwback:
So rename it.
[SuperR Kitchen] SuperR.:
This one is my fault. I forgot to include the config directory in the custom zips. Will fix as soon as I can.

Can you check your zip to see if it has a config directory? If not that is the problem. If so, can you make sure the slotdetect.sh file inside has an "else" statement (just look for the word else)?

As mentioned in the 2.1.4.0 update, nobody provided feedback on the Pixel test kitchens so we are doing the testing in the main kitchen. It is the only way I have found to get feedback. Asking for it does not get results :(

Yes. Listen to [MENTION=1162986]Captain_Throwback[/MENTION] ;)
[SuperR Kitchen] Danvdh:
Just created a ROM out of the official 7.1.1 factory image for the Nexus 6 with the donate version.

sparse doesn't work at all, started from scratch again and used metadata and all worked perfectly so far, no complaints. so is this the perm type you recommend SuperR?
[SuperR Kitchen] SuperR.:
set_metadata is probably the most stable option for most devices, although I was hoping the new sparse_dat changes might change that. Could you provide a recovery.log from flashing the sparse_dat rom?

Which kitchen version are you running?
[SuperR Kitchen] Danvdh:
I was using the latest kitchen as of yesterday. The ROM flashed fine however there was setup wizard force closes
[SuperR Kitchen] nightcrow:
Checked the zip and I don't see a config directory. Should this be a file/folder in the zip or do I have to look for it in for example the system folder? Of course I already had a quick glance and searched for it but no luck.

And don't worry about the public testing part, I'm pretty sure we all appreciate your work a lot and I know you'll be able to solve these hick-ups somehow. I'll be glad to help locating the issue. Jus let me know if I can look for other things!
[SuperR Kitchen] SuperR.:
v2.1.4.2 (Donate version)

Changes:

Fixed config directory not being added to all zips.

Fixed custom zips updater-script.

v1.1.3.2 (Standard version)

Changes:

Fixed config directory not being added to all zips.

Fixed custom zips updater-script.

Please give this one a try. Update the kitchen, change perm types to something else and back to whatever you want, and build your zip again. Check before flashing and make sure there is a config directory in the root of the zip.
[SuperR Kitchen] paddy01:
Donation sent - 9VL56708P20664006 - gitlab user paddy_2 :)
[SuperR Kitchen] chevycam94:
OK, even on v1.1.3.2, I still cant get a zip built from a factory ROM to boot. No errors anymore in Kitchen, but it doesnt boot past the Google logo still. Is there some way I can get the source as of v1.1.2.9 (or some other specific version)?
[SuperR Kitchen] oak:
Thanks

Keep up the good work, SuperR. 1UF73708F3576544X
[SuperR Kitchen] SuperR.:
SuperRs_Kitchen_v1.1.2.9

Please keep me updated if it boots properly when built with v1.1.2.9. Thanks :)

You are already in the repo. Thank you so much for your extra support :)
[SuperR Kitchen] chevycam94:
Thanks. I took a few extra steps and finally got it. But I'll keep that link handy. Ive been hacking away at this for quite a while, and I think it may not just be the Kitchen. It appears that after building the ROM zip, and including the vendor image (extracted and included), that somehow the vendor image doesnt get copied over correctly. I now have to flash the same factory image in TWRP (image flashing option) directly after the ROM zip is flashed.

If I just reboot after flashing the ROM, its stuck at the Google logo forever. But as soon as I flash the vendor.img in TWRP (image option) and reboot, the ROM boots right up.

In v1.1.2.9 (last version I used before the update to v1.1.3.0 (and newer)), the vendor flashed just fine, and everything booted as expected. Both ROMs are based on 7.1.1, and are only 1 month apart in official releases from Google. I cant imagine anything major changed in the Google factory images, so I'm thinking its something in Kitchen. Sounds like the issues started when you updated to v1.1.3.0 (Pixel slot support).

I'll gladly test as much as I can.
[SuperR Kitchen] SuperR.:
Thanks for the information :) Can you send the updater-script and a recovery.log after flashing the problem zip?
[SuperR Kitchen] chevycam94:
Here you go. To be fair, this was the zip that was built on v1.1.2.9.
[SuperR Kitchen] SuperR.:
When you say this was the zip that was built on v1.1.2.9, do you mean the recovery.log? I ask because the updater-script is from v1.1.3.0 or later. Does the zip built on v1.1.2.9 boot properly or do you have the same problem as v1.1.3.0-v1.1.3.2?

I don't see anything strange in the updater-script or the recovery.log, so I am not sure what is going on. Vendor appears to have flashed without errors
[SuperR Kitchen] nightcrow:
Tried it and there is a config directory now in the zip. The slotdetect.sh file inside has an else statement:

However when I flash the zip in twrp recovery I get the following error when it tries to format system:
[SuperR Kitchen] apkbpkcpk:
great for the ubuntu4kitchen iso, works great, i would suggest on also creating a Dockerfile, many people use it now-a-days
[SuperR Kitchen] chevycam94:
With this new factory image, built on v1.1.2.9 through v1.1.3.2, all fail to boot. I'm still required to flash the vendor.img right after the ROM zip for the ROM to boot.

I'll try more things today.
[SuperR Kitchen] SuperR.:
Looks like the config part is working, so that's good at least.

The error you posted has a mistake in the by-name line. Not sure if you typed it wrong or if that is the exact error. If you typed it wrong no problem, but if that is what the kitchen thinks your by-name is that is your problem.

This:

/dev/block.platform/155a0000.ufs/by-name/system

should be

/dev/block/platform/155a0000.ufs/by-name/system

Can you send the updater-script and recovery.log after flashing?

I may look into this
[SuperR Kitchen] chevycam94:
[MENTION=5787964]SuperR.[/MENTION] OK, here is a pure factory image processed through v1.1.2.9 with the link you gave me. I didnt update any part of kitchen. I only disabled verity, rooted.

Still having the failure to boot past the Google logo. Flashed on TWRP 3.0.3-0
[SuperR Kitchen] AndroidTutorials:
Love your new update ?
[SuperR Kitchen] SuperR.:
It seems the problem is not caused by the new update, as the results are the same with v1.1.2.9 and 1.1.3.2. This is good news for me, not so good for you lol. The recovery.log you sent did not include the flash so it does not help to diagnose the issue. I imagine it will show the same thing the last one did, which is vendor flashing with no error. The new v1.1.2.9 updater-script you sent also looks correct. We may be missing a permission somewhere that is causing it not to boot. If you figure out the problem please let me know so I can update the kitchen.
[SuperR Kitchen] Svan987:
Hi there :victory:

Coming to share a .zip and i am gonna give u some work too :D

When i build a full rom with Root and Busybox, at the end of the updater-script there is an "unmount system" error log. I think those tools umount partition at the end of flash.

Cheers.

View attachment 3994769
[SuperR Kitchen] celoxocis:
:laugh:

So i finally got some time to get back to this and answer a few questions.

I started from scratch to see what the problem is.

As you said you implemented motorolas systemchunk unpack feature.

I went ahead and tried it.

I placed all the files from the archive into the project directory and hit ""Option 4"":

I get:

Extract Options:

1) systemchunk3.img
2) systemchunk0.img
3) systemchunk2.img
4) systemchunk5.img
5) systemchunk8.img
6) preload.img
7) cache.img
8) systemchunk4.img
9) systemchunk7.img
10) systemchunk10.img
11) systemchunk12.img
12) systemchunk9.img
13) systemchunk11.img
14) systemchunk1.img
15) userdata.img
16) systemchunk6.img
m = Main Menu
q = Quit

I selected the first chunk file which is "systemchunk0.img"

i received

Converting sparse chunks to system.img

a short while after that i receive

ERROR:
There was a problem extracting your ROM.

Press ENTER to return to the Main Menu

when i exit superr to check the system folder, its empty and all system chunk files are gone(deleted?)

and im left with these extract options for (obviously):

Extract Options:

1) preload.img
2) cache.img
3) userdata.img
m = Main Menu
q = Quit

i checked the main.log in 00_project_files/logs contains:

dd: invalid number: ‘0’

maybe its just the naming schematic?

if i use the tool described in my previous post it works.

it is available here: https://xdaforums.com/moto-x-2014/general/guide-how-to-extract-files-stock-t2917124

i placed a copy for you of the mentioned archive on my mega-mirror here: https://goo.gl/JTCwKj

i have changed the bat like this:

@echo off

set wf=C:\Sparse-to-Img\Cygwin\

if exist system.img (echo File system.img exist, please delete it... & goto ret)

echo Create system.img Please wait...
(for %%a IN (systemchunk*.img) DO %wf%sparse2img %%a system.img )
echo.
if exist system.img echo Create system_motoX2.img successful...

:ret
echo.
pause

to make it work.

let me know if you need any further information
[SuperR Kitchen] Svan987:
Hi,

Tried editing my last post but can not add a file on it hosted by xda.

So here we go.

Cheers.

View attachment 3995586
[SuperR Kitchen] tanish2k09:
[MENTION=5787964]SuperR.[/MENTION]

Quick problem :

I can't build the ROM zip without a boot.img

But I want to restore the boot partition from twrp backup, so I don't want/need to include it in the zip.

Also, if I build system.img, it is bigger than my system partition size.

The only thing I do now is to manually compress the META-INF and SYSTEM folders into a zip archive and flash that.

Can you please make ammend your kitchen to ask the user whether boot.img is to be included or not.

If the user enters a "n", then remove the boot.img flash from updater-script. Just a suggestion/request.:fingers-crossed:
[SuperR Kitchen] bcrichster:
Umm.. Just use TWRP to manually flash the boot.img or use the boot/recovery option in kitchen to make that flashable zip.

Sent from my N9515 PAC-ROM
[SuperR Kitchen] Has.007:
[MENTION=5787964]SuperR.[/MENTION] Hi, I've been using your kitchen for a while now nd it is definitely amazing! :) However I've an issue which I started facing since you updated SuperSu to 2.79. The SuperSu zip doesn't get copied to the Zip Builld, the rootzip stays empty. Tho I manually transfer my own zip nd modify the updater-script.

Also, How can I know if the init.d is working properly if I implement it in the boot.img.

I've a Samsung Galaxy Grand Prime, extra information.

Thank you very much! :)
[SuperR Kitchen] tanish2k09:
[MENTION=5787964]SuperR.[/MENTION]

When the kitchen asks for obtaining system partition details, the option that works for me is to detect it via adb.

However, if my device is in recovery (twrp) then kitchen doesn't detect it. When I boot to my ROM, only then does the kitchen move to the next step.

This creates a problem when I have no ROM installed. I always have to restore my nandroid first.
[SuperR Kitchen] SuperR.:
v2.1.4.3 (Donate version)

Changes:

Fixed unmount errors after flashing SuperSU and/or Busybox.

Added support for Motorola systemchunk files extraction.

Added a couple devices to the device repo.

Allow building ROM with no boot.img after confirmation.

v1.1.3.3 (Standard version)

Changes:

Fixed unmount errors after flashing SuperSU and/or Busybox.

Added support for Motorola systemchunk files extraction.

Added a couple devices to the device repo.

Allow building ROM with no boot.img after confirmation.

NOTE: As stated above, this update will allow building a ROM with no boot.img. You still need file_contexts which is found in the boot.img so you may still get errors about requiring boot.img. All you need to do is add the correct file_contexts or file_contexts.bin file to /kitchen/superr_projectname/00_project_files and the boot.img errors will stop.

I am not able to reproduce this issue. When I add root to all ROMs my project directory contains a rootzip directory with the SuperSU.zip inside. I only test on Ubuntu 16.04 so maybe something is different about your OS.

Should work now, but read the NOTE above :)

Figure out your system partition size in bytes and use the manual option. Alternatively, tell me how to figure it out using adb while booted into recovery on your device and I will add it to the kitchen.

Should be fixed now :)

Should be fixed now :)