yashsingh1/xdaforums huggingface dataset:
[SuperR Kitchen] Captain_Throwback:
So here's the update-binary built from the TWRP/OmniROM Android 7.1 source, with minzip >2GB patch included. Note that this binary doesn't support set_perm as that was deprecated several Android versions ago. Additionally, this binary may not be backwards compatible with previous Android versions (Marshmallow and older), but I'm just basing that on what [MENTION=912474]Dees_Troy[/MENTION]'s commit message here says (though I think he's just talking about building it, not using it for flashing).

So, testing will be required. I built the binary for arm so it should be compatible with both arm & arm64 devices (works fine on mine). There is a weird error at the end of the flash about an "unknown command," but it doesn't seem to affect anything. It happens after the flash is already done, so I'm not at all sure what causes it.

Here's some recovery log output for you:

I:operation_start: 'Flashing'
Installing zip file '/external_sd/05_ROM/PME_2.38.617.67_stock.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Update binary zip
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
[B]unmount of /system failed; no such volume[/B]

PME 2.38.617.6 stock Installer
Built with SuperR's Kitchen

about to run program [/tmp/install/bin/backuptool.sh] with 2 args
Extracting system...

performing update
blockimg version is 4
maximum stash entries 0
creating stash /cache/recovery/2bdde8504898ccfcd2c59f20bb8c9c25f73bb524/
222031872 bytes free on /cache (0 needed)
erasing 114114 blocks
writing 512 blocks of new data
...
writing 512 blocks of new data
zeroing 1024 blocks
...
zeroing 1024 blocks
zeroing 52 blocks
writing 512 blocks of new data
...
writing 512 blocks of new data
writing 411 blocks of new data
writing 512 blocks of new data
...
writing 512 blocks of new data
writing 1 blocks of new data
writing 512 blocks of new data
...
writing 512 blocks of new data
zeroing 1024 blocks
...
zeroing 1024 blocks
zeroing 622 blocks
wrote 864830 blocks; expected 864830
stashed 0 blocks
max alloc needed was 4096
bytes_written_system: 3542343680
bytes_stashed_system: 0
deleting stash 2bdde8504898ccfcd2c59f20bb8c9c25f73bb524
about to run program [/tmp/install/bin/backuptool.sh] with 2 args
Extracting boot image...

PME 2.38.617.6 stock Installed
script succeeded: result was [PME 2.38.617.67 stock Installed[B][COLOR=Red]E:unknown command [][/COLOR][/B]]

There also seems to be some redundant unmount /system lines in the sparse_dat script. Additionally, if you change the unmount("/system") lines all to

ifelse(is_mounted("/system"), unmount("/system"));

it'll prevent the log spam in the recovery console/log ;).
[SuperR Kitchen] SuperR.:
Very nice, thank you :)

I have already changed the unmount command to exactly that in the Pixel test kitchens (which will eventually be the normal kitchen) ;)

edit:

Everyone, please try the Pixel test kitchen and let me know how it works on other devices.
[SuperR Kitchen] xpirt:
fixed in img2sdat 1.1 version
[SuperR Kitchen] xNako:
I can't cook a snapshot version of CM13, system don't install.. Any solution?

Thxx
[SuperR Kitchen] _that:
You're doing it wrong. Solution: do it right.
[SuperR Kitchen] xNako:
Yes, but in nightlies versions work...
[SuperR Kitchen] SuperR.:
v2.1.3.9 (Donate version)

Changes:

Updated SuperSU to v2.79-SR1.

Added update-binary to support Nougat sparse_dat (Thanks [MENTION=1162986]Captain_Throwback[/MENTION]).

Updated img2sdat by [MENTION=5132229]xpirt[/MENTION] to v1.1.

Use the correct sparse_dat transfer list version for the ROM we are building.

Replaced set_perm with set_metadata in custom zip updater-script.

Use ifelse to unmount if mounted at the beginning of the updater-script.

v1.1.2.9 (Standard version)

Changes:

Updated SuperSU to v2.79-SR1.

Added update-binary to support Nougat sparse_dat (Thanks [MENTION=1162986]Captain_Throwback[/MENTION]).

Updated img2sdat by [MENTION=5132229]xpirt[/MENTION] to v1.1.

Use the correct sparse_dat transfer list version for the ROM we are building.

Replaced set_perm with set_metadata in custom zip updater-script.

Use ifelse to unmount if mounted at the beginning of the updater-script.

Happy Holidays!!!

The new sparse_dat update-binary has not been tested on M or L. If it does not work, I will add the old binary for older roms.

The Pixel test kitchens have also been updated. I still need to know if the Pixel test kitchens create roms that flash properly on non-Pixel devices.
[SuperR Kitchen] elektrik2001:
Thanks man...I'll try it out.
[SuperR Kitchen] elektrik2001:
Thanks Superr..that did the trick....now the next problem i'm having is that in your kitchen, when I enable root/su.d, the superuser app isn't installed, so It's basically just he same firmware as before...and I can't figure out why...
[SuperR Kitchen] SuperR.:
The kitchen does not install SuperSU into your rom. It sets up your rom to install SuperSU when you flash it.
[SuperR Kitchen] elektrik2001:
gotcha..I'm making it into a PhoenixSuit image....that explains it..so I have to figure out a different way to get it on there...
[SuperR Kitchen] Yzord:
I get this when i start Superr on Mac Yosemite:

Any idea how to run it on mac?
[SuperR Kitchen] monleylord:
Already donate. Gitlab user name is "monley". Many thanks for the amazing kitchen.
[SuperR Kitchen] AndroidTutorials:
Does it work with Windows?
[SuperR Kitchen] bcrichster:
[emoji49] Try READING the first 4 posts of this thread for your answer, it's there. [emoji49] Really.
[SuperR Kitchen] AndroidTutorials:
Ok
[SuperR Kitchen] SuperR.:
I am not sure as I have never tested on a Mac. The only things I am sure of, are to make sure you have Bash and the GNU versions of all the dependencies. The syntax is different for Mac versions of the same utilities so many things won't work properly unless you use the GNU equivalent.

Added, thanks :)

I think most things work in cygwin now, but I don't test on Windows.
[SuperR Kitchen] AndroidTutorials:
Ok I've installed lubunto but can I make a Rom for galaxy j5 lollipop?
[SuperR Kitchen] bcrichster:
Theoretically, Yes. [emoji16] The .tar.md5 plugin should work with ODIN/Heimdall unless you have TWRP, then just make a flashable zip.
[SuperR Kitchen] AndroidTutorials:
Ok so when I make a flashable zip which one do i press buddy ☺
[SuperR Kitchen] bcrichster:
"Build Full ROM"
[SuperR Kitchen] AndroidTutorials:
Ok thanx for the help bro I've been trying to do this last week
[SuperR Kitchen] bcrichster:
Some info needed for better assistance instead of just stating the obvious.. What are you trying to do, exactly and what are the issues? What are you using as your source files (where's the ROM coming from: mfgr FirmWare, TWRP backup, pulling images from device itself..)?? Do you have Root.. TWRP or Stock recovery?? [emoji41]
[SuperR Kitchen] AndroidTutorials:
Yes my phone is rooted and also has TWRP installed and I'm using the stock Rom ☺
[SuperR Kitchen] bcrichster:
What issues were you having, what are you trying to do/change?

Sent from my N9515 PAC-ROM
[SuperR Kitchen] AndroidTutorials:
I've been trying to make a custom Rom for my galaxy j500fn but when I flash it on the Rom does not boot only straight into recovery
[SuperR Kitchen] bcrichster:
OK.. You'll need to retrace and possibly document your steps in the kitchen, plus make & post a copy of the updater-script and TWRP log to compare

Sent from my N9515 PAC-ROM
[SuperR Kitchen] AndroidTutorials:
Ok I will do that
[SuperR Kitchen] robcore:
[MENTION=5787964]SuperR.[/MENTION]

First of, of course, thank you endlessly for this project, it is remarkable, and a great help to lazy people like me!

Two quick requests: First one -> I use Kali Linux and have been modifying your script to remove the check for root userid, but is it safe for me to be using it on this distro?

Secon done - > reodexing...pretty please? I understand if you are far too busy and ignore me!

Take care,

Rob.
[SuperR Kitchen] TheHiman:
[MENTION=5787964]SuperR.[/MENTION]

I have a problem on my I9505 with this and others S4-Firmwares: I9505XXUHPK2_I9505OXAHPK1_DBT to deodex completly without errors.

I use for this device at the moment the ODTRTA-Deodex-Tool, which is using an error-fallback method:

3 versions of oat2dex and as last resort: smali/baksmali. (or vice versa, not sure at the moment)

Replacing the files in your kitchen with the ones from ODTRTA-Suite don´t fix the problems for me right now.

My Questions:

- Can you reenable smali/baksmali-Method for API Level 21 for further tests ?

- Can you add script for selecting different smali/baksmali-Versions, same as for different oat2dex-versions ?

- Can you think about a "fallback-mode" when a single deodex-process results in an error, to use an alternative version of oat2dex or smali/baksmali ?

At the moment, different oat2dex versions produces more or less deodex errors, but no version entirely deodex the whole I9505-rom correctly :(
[SuperR Kitchen] SuperR.:
It is probably safe, but I can't confirm or deny all the features will work. I only test on Ubuntu 16.04 for the moment.

I don't know how to reodex, and can't think of a reason it would be needed.

No. It was never enabled to begin with. smali/baksmali does not work with Lollipop. It says so in the first paragraph here.

Yes, but I probably won't.

Possibly in the future

Have you tried deodex tool by [MENTION=6242674]svadev[/MENTION]? Many people have said is great for Lollipop Samsung roms
[SuperR Kitchen] texasaggie1:
Donated!

I just donated! My GitLab account is texasaggie1 and my paypal email is support@mytekrescue.com
[SuperR Kitchen] Svan987:
Hi SuperR,

Just donated 2 :D GitLab Username is same : Svan987.

Thanx a lot for this great project and Happy New Year 2017 in advance :highfive:
[SuperR Kitchen] Yzord:
So of course i have reads post 4, because my ROM zip is also small...but uhm....no answer in post 4?? Just the question.

So let me ask it here again, why is my ROM so small? Original is 1.6GB, but the new one from the kitchen is 460MB.
[SuperR Kitchen] bcrichster:
- What device are you working with?

- Did'ja forget to add certain things like the cache.img &/or Vendor.img (Samsung)?

- Plus, deodexing and debloating can significantly reduce ROM size as well.

Sent from my N9515 PAC-ROM
[SuperR Kitchen] SuperR.:
Added, thanks :)

Here is the relevant section in post #4
[SuperR Kitchen] Yzord:
Thanks for your answer.

I work with a Nexus 5X, but no matter what i try, i can't seem to finish my own custom ROM.

What did i do?

- Downloaded the Copperhead ROM and unzipped the zip to my kitchen's project folder.

- I select 4 to extract for a new ROM

- In the original zip file evrything is included, like cache, vendor, recovery, userdata etc... but it only asks me to use system.img and vendor.img

- I select 8 and use first option 1 for deodex the ROM

- Perm type is raw_img

- After that i debloat the ROM

- Then i take option 7 to the build menu

- And i take option 1 to build a full ROM zip

- After building i take the zip file and put it on my phone

- Reboot into custom recovery

- Wipe my phone and after that i install the zip file through the recovery

- And then it hangs on the Google startup image.

I tried this several times with several kitchens (AYYASSED kitchen for instance), but all the same problem.

The reason i use the Copperhead image is because it is hardened already and debloated. But i want to remove some more apps like Email, Calendar and Music for instance.

Because it is hanging on the Google boot image, i cannot connect it with usb to get some log of it. After building for almost a week now i am pretty desperate to get this right. It keeps hanging on the Google boot image. Also waited an hour (in case it needs to odex everything), but that also didn't work.

Reinstalling the stock ROM is no issue. But i want to install my own custom ROM :( so if anyone has a tip for me....please share if you want. I am also planning to donate for this kitchen, but i need a way to figure this out first.

Ah, i thought it was a new question because it was made bold. Sorry for the n00b question then :)
[SuperR Kitchen] bcrichster:
OK.. Good job documenting your steps, BTW. You may need to add the other files (cache & vendor) anyways but the kitchen usually needs a minimal of system & boot to function. If everything is pretty much the way you want it, just copy the meta-inf files from Copperhead over the ones in the new build. It may be helpful to [MENTION=5787964]SuperR.[/MENTION] if you posted the functioning updater from the Copperhead and the kitchen generated updater to compare and find the needed changes.. There are a few perms that may need to be changed or added to the raw.img method and this would help immensely in achieving that. And that, would also help anyone else building for the N5x on the kitchen.

~ By The Way: EVERYONE, don't forget to zip up your devices and post them so they can be added to the SuperR Kitchen device repo, it helps everyone!!

Sent from my N9515 PAC-ROM
[SuperR Kitchen] Yzord:
I tried it also by replacing the original boot.img (which is the same size though) and system.img in the original zip file of Copperhead, but that didn't work also. Is it possible they could have locked their ROM for editing?
[SuperR Kitchen] SuperR.:
When it asks you for the system partition size, choose the manual option and enter this "3221225472".

Vendor partition is "260034560".

Partition size info comes from:

https://github.com/TeamWin/android_device_lge_bullhead/blob/android-6.0/BoardConfig.mk

FYI, ctrl+shift+v allows you to paste in the terminal

Edit: If you still have problems, you might be adding more to the rom than the device can hold. You can only fit what the device can hold. The partition sizes I gave you are the maximum capacity of the partitions.

Edit2: I just downloaded, extracted, and built a raw_img rom from the latest Copperhead firmware. I chose option 4 when it asked how to get the partition sizes for system and vendor. No issues at all. Rom size 585MB
[SuperR Kitchen] Yzord:
Thanks for your time and help. I did the same. I placed the zip file named "image-bullhead-nmf26q.zip" into the projectfolder and choose 4 for extracting it. Did only a deoxed (and not adding any apk's to it). Ok, here are the new step i took after your above message.

- Deleted old project

- Made a new project

- Uploaded image-bullhead-nmf26q.zip to the projectfolder

- Took option 4

- Include vendor ROM i say YES

- Include the files of the vendor.img in my ROM i say YES

- Name of the ROM is simply TEST

- Which perm type i take option 4 = raw_img

- Right after that i am not changing anything of the ROM but build it again so i take option 8 (ROM tools menu)

- I take option 7

- Then i take option 1 (build full ROM zip)

- The i take option 3 and fill in 3221225472

- I take again option 3 and fill in 260034560

- It is building the ROM (ROM is 585MB)

- I do not sign the ROM

- Putting my phone into file transfer mode and send the TEST.zip into my Download folder of my phone

- Putting my phone into custom recovery

- Wipe all cache, data etc. in recovery menu

- Install the TEST.zip through the install option of the recovery menu

- And that also results in a hanging Google boot image. Not going further anymore. Need to force it into bootloader to push a Copperhead ROM into it.

So, something isn't right. Did not deoxed/debloat the ROM before i build it again.

edit: i did noticed when i tried it to flash it the way like Copperhead is doing (with the flash-all.bat) an error something with "Invalid sparse file format at header magi". After that it was still flashing it to the phone with the same outcome.
[SuperR Kitchen] boostermbkking:
why I have this issue? I'm not able to update the kitchen or download it from scratch, my account name is boostermbkking
[SuperR Kitchen] SuperR.:
I am not sure what is going on. If you figure it out and the kitchen is doing something wrong, please let me know.

I have been hearing this a lot lately. I am not sure what is going on with Gitlab. I deleted your user and added it again. Not sure if it will help but that is the best I can do.
[SuperR Kitchen] bcrichster:
Gitlab been making a lot of changes.. Check your emails since gitlab sent out notices to all the members these last cpl Wks

Sent from my N9515 PAC-ROM
[SuperR Kitchen] easymik:
Hi SuperR,

Just donated 2 GitLab Username is: easymik
[SuperR Kitchen] nightcrow:
Had the same problem. I logged in this morning in Gitlab and then tried to clone the kitchen again in the Oracle VM and it worked. So a log-in in Gitlab every now and then seems to solve this problem.
[SuperR Kitchen] boostermbkking:
thanks so much,this fix my issue!
[SuperR Kitchen] hedgehogmd:
GitLab Username is hedgehogmd

Thanks for all your hard work. :)
[SuperR Kitchen] Timei:
hello. after long tome inactive i start my VMWare, launch Kitchen and got this

"ERROR:

The Kitchen could not detect an internet connection.

Press ENTER to return to the Main Menu"

i press enter, but nothing happened. internet on VM working fine.

help please
[SuperR Kitchen] SuperR.:
You can try to clone the kitchen again. Since it has been a long time there have been many updates. If that does not work, hopefully someone else will be able to help as I don't use or test on VM.

If you want to use the old version you have, you can delete the file /kitchen/tools/updatecheck-yes and run the kitchen again. This will disable the check for updates when you start the kitchen which is the only thing using the internet.
[SuperR Kitchen] Timei:
i do that and now he work, but checking updes give the same error.

now i'm on latest version 1.1.2.9

thanks for help=)
[SuperR Kitchen] Svan987:
Started my testing and learning :silly:

No emergency but i noticed that when you choose to deodex with "smali/baksmali" we didn't get a choice for the old or new version. In repo (old version) need to update smali/baksmali to version 2.1.3.

Got trouble deodexing "SamsungIMEv3.apk" [set_metadata + oat2dex 0.86 (when using oat2dex lastest build got many errors on several files)] I am waiting an answer from someone who did deodexed Galaxy Tab s2 firmware 6 months ago.

PS : Error file text attached was with perm raw_img

Cheers.

View attachment 3983621
[SuperR Kitchen] SuperR.:
Glad you got it running. I still don't know anything about VMs, so hopefully some else can help with the no internet connection problem.

The older smali/baksmali is used for Android 4.4 and older. The latest smali/baksmali is used for everything else. It is possible the latest will work for older devices now, but there was a time when it did not. If you want to try the latest with a older device, copy it from /kitchen/tools/smali/current to /kitchen/tools/smali/old and remove the old versions. You should keep the old versions handy because the kitchen updater will not work if you change the files.

I can't do anything about deodex errors. You can open an issue on the oat2dex github if you want.
[SuperR Kitchen] Svan987:
I posted on github with files will see ;) Thanx you explained me about smali/baksmali versions. In "tools/root/root_zips" if i got extra "SuperSU.zip" with different names will not be a problem for the updater right ?

Got one more quetion if i need to remove dm-verity and forceencrypt :

- Menu 7 : Boot/Recovery tools

- Menu 1 : Unpack boot image

Check if 5 and 6 are in status "disabled"

-Menu 2 : Pack boot image (keep ramdisk work directory) ---> Boot image is signed too ?

Is that correct ?

Cheers.
[SuperR Kitchen] SuperR.:
You can add as many root zips as you want to tools/root/root_zips and you will be asked which one you want to use. The kitchen updater will still work as long as you keep the one that comes with the kitchen in there.

disabled is good for forceencrypt and dm-verity.

boot.img is not signed

You can delete the ramdisk work directory if you want. It is just the work directory in your rom directory.
[SuperR Kitchen] janjan:
Hi there. Is it possible to build boot.img from a zImage-dtb? Or from zImage to boot.img. Anyway to perform this task? Thanks.
[SuperR Kitchen] Captain_Throwback:
zImage(-dtb) is only part of a boot.img (the kernel part). You still need a ramdisk for a complete boot.img. So unless you already have a ramdisk laying around, it's not possible to build a boot.img with just a kernel/dtb.
[SuperR Kitchen] janjan:
Actually I usually use zImage with with Anykernel2 script. Since I need to test my kernel in Asus ZenWatch 3 I need to compile a boot.img to test by fastboot boot boot.img.

Is it possible to build from kernel source? I always end up with zImage and zImage-dtb. The way I build is followed as.

# Exports

export PATH=~/android/arm-eabi-4.8/bin:$PATH

export ARCH=arm

export SUBARCH=arm

export CROSS_COMPILE=arm-eabi-

export CROSS_COMPILE=/home/xxxxx/android/arm-eabi-4.8/bin/arm-eabi-

# Make

echo "Starting compilation.."

make clean

make swift_defconfig

make -j `getconf _NPROCESSORS_ONLN`

# Copy kernel

cp "arch/arm/boot/zImage-dtb" ../zImage-dtb
[SuperR Kitchen] Captain_Throwback:
You need to extract the boot.img from your device and replace the kernel portion, and then repack it. But I'm not sure how that relates to this Kitchen?
[SuperR Kitchen] janjan:
Since this Kitchen is able to extract the boot.img so maybe possible to replace the kernel portion and repack it back as a boot.img
[SuperR Kitchen] Captain_Throwback:
Yes, you can do that - just replace the extracted kernel with the one you built.

P.S. But that's only if you're extracting it as part of a ROM build. If all you want to do is extract a boot.img, just use Android Image Kitchen. You don't need this Kitchen just to do that.
[SuperR Kitchen] jonniehere:
ive extracted system.img and recompiled it but the phone wont boot and i have made no changes to it are the permisions going wrong?

its an mtk6737t device.
[SuperR Kitchen] Yzord:
Same problem here....loaded a rom into the kitchen and build right after that a new ROM. Keeps hanging on Google image.
[SuperR Kitchen] jonniehere:
kitchen

does yours work if you do it as an update zip?
[SuperR Kitchen] tanish2k09:
[MENTION=5787964]SuperR.[/MENTION]

Software looks awesome. I got a problem (before you say, I have read the OP properly).

I use windows 10.

I am porting cm14.1 to my device (Lenovo A7000-a)

The problem :

-----------------------

1) I extract the zip file.

2) There is a "file-contexts.bin" instead of the normal file with no extension. This is common in nougat Roms as I have read in previous few posts.

3) I have system partition in system.new.dat, so I use MTK extractor 2.6.3 to make a system.img

4) It says "file_contexts" not found. Because it doesn't exist. What exists is the file with ".Bin" extension.

5) Now how do I get into the system folder for replacing files??

Unable to follow your usage guide.
[SuperR Kitchen] SuperR.:
Look at the top of post #4, provide more information, and someone may be able to help you

Look at the top of post #4, provide more information, and someone may be able to help you

The kitchen handles extracting system.new.dat and file_contexts.bin. Try letting the kitchen extract the zip for you using option 4 from the main menu. If that does not work look at the top of post #4, provide more information, and someone may be able to help you
[SuperR Kitchen] JRapsky:
Hi,

I tryed the SuperR Kitchen for the first time. Everything went well so far, but now I don`t know how to install my signed and zipped ROM. There is at the moment no custom recovery for my device. Is there a way to install my ROM with spflash tool for MTK device?

kind regards

Joern
[SuperR Kitchen] jonniehere:
Use fast boot flash that how I got mine to work as I don't have adb or root if you use flash tool but get error open config ini andd change ROM size in there

---------- Post added at 11:39 PM ---------- Previous post was at 11:36 PM ----------

It's not a zip I'm extracting it's a system.img I used the kitchen in packed it then edit system folder jar libs etc rebuilt but SP flash wouldn't have it so I used fast boot n it worked