yashsingh1/xdaforums huggingface dataset:
[SuperR Kitchen] ale8530:
[MENTION=718594]super[/MENTION]R if you just can kindly explain to me how to get the donate version

---------- Post added at 11:25 PM ---------- Previous post was at 11:13 PM ----------

---------- Post added at 11:27 PM ---------- Previous post was at 11:25 PM ----------

[MENTION=5787964]SuperR.[/MENTION] i have donate my account username ale8530
[SuperR Kitchen] bluflight:
Thanks for the fast reply :good: i tried just now with new file but without success :crying: after full wipe, phone boot, select language and after always stuck on "wait a few seconds" page. Stay on this page and no go away.

So with the same new file i did the same process on mm firmware, and here no problem at all, phone boot and no one problem on first inizalization.

So really I do not understand what the problem may depend... Maybe on this openbeta N firmware, now i think we have only to wait final/official release to try again.

PS: if file is not set right on executable, building process will be stopped by kitchen right?
[SuperR Kitchen] SuperR.:
Added, thanks :)

If the binary is not executable, the image will not be built.
[SuperR Kitchen] ale8530:
[MENTION=5787964]SuperR.[/MENTION] Thanks

Is possibile use this autorom_config without GUI?
[SuperR Kitchen] :
I git cloned the kitchen when it was first released but the check for updates option doesn't seem to be working anymore. It keeps telling me 9.2.0 is the latest version
[SuperR Kitchen] SuperR.:
That is strange. Try doing "git pull" from the main kitchen directory in the terminal. That should get you updated and hopefully sort out the issue with the updater.
[SuperR Kitchen] :
Unless I did something wrong I get unable to access. The requested url returned error 500
[SuperR Kitchen] SuperR.:
This may be why:

http://status.bitbucket.org/
[SuperR Kitchen] :
Thank you my friend and thank you for your continual support. Your hard work and helpfulness is really appreciated
[SuperR Kitchen] SuperR.:
Thank you. Very nice to hear :)

I added a temporary alternate download for the newest version in the OP ;)

edit: just noticed this thread has a built-in downtime monitor for the downloads. If the main image in the OP does not load, the downloads are down :p
[SuperR Kitchen] fhem:
N6 stock.

Deodexing seems to be working except for the few that already have classes.dex and odex. I'm not sure what's up with those. I will have to take a look at those. I have tried several times making a flashable zip before deodexing (no adds or mods) but the rom won't boot - quits after first splash --- so maybe we need to wait for xpirit ????? I will push some deodexed apk's to a stock odex build and report back. Thanks for the support and great work --- it is much appreciated.
[SuperR Kitchen] SuperR.:
I asked [MENTION=1299419]JesusFreke[/MENTION] about the apk's that contain classes.dex and he agrees it should be ok to delete the odex files, same as in the past.
[SuperR Kitchen] sparks15:
hi there someone who can help me with this

/home/spark/SuperRs_Kitchen_v0.9.2.3/tools/boot/carliv/scripts/unpack_img: line 99: /home/spark/SuperRs_Kitchen_v0.9.2.3/tools/boot/carliv/.bin/unpackbootimg: cannot execute binary file: Exec format error

ubuntu 32 bits

unpacking boot.img nexus 5
[SuperR Kitchen] DarkHeart Z:
Ok bro but everyone of them are complete except the w67 . because I was studying that rom's structure . But that not my device's filter others are complete . I have done that myself .
[SuperR Kitchen] DarkHeart Z:
help for 32 bit

Bro I just found out that carliv's kitchen has been based on 64 bit . I contacted with him and he said that . that means there is no problem inside the my system or your kitchen . the main fact is the mtkbootimg binaries doesn't work under 32 bit environment . All my project will now be on vain . Can you keep bgcngm's tools too in your kitchen . i would test the kitchen under cygwin . Wanna see if it works :(

P.s. : the windows version of his kitchen works without any errors .
[SuperR Kitchen] SuperR.:
[MENTION=5186178]carliv[/MENTION] built the binaries for MTK-Tools by [MENTION=455439]bgcngm[/MENTION] and they are also 64-bit. That is why you were having problems before too. Not sure what to do about this yet.
[SuperR Kitchen] SuperR.:
v0.9.2.4

Changes:

Added a check for bitbucket.org to make sure it up before trying to update.

Kitchen updater now removes the old kitchen before extracting the new one when not updating through git.

Added the abiltiy to unpack cache, hidden, data, and generic img's without the ROM being moved to old rom files.

Added ping to the dependencies list.

NOTE: The generic.img can be anything unpackable, and must be named generic.img. This is just a way to unpack a custom img without the kitchen doing anything to the current project other than unpacking the img into a directory named generic.
[SuperR Kitchen] DarkHeart Z:
confused

i tried bgcmgm's tools with cygwin . they worked without any problems . Maybe modifying the executables can solve this . and the most strange thing is I tried bgcmgm's tools again and boot.img extracted properly . But failed to repack same problem : elf : not found . If it gets extracted properly why it doesn't get repacked ? (bgcngm's tools) :confused:
[SuperR Kitchen] jtash01:
correct asserts for kltespr and lollipop rom?

I have a SM-G900P (kltespr) that superr kitchen fails to generate a installable rom for. I have tried extracting from a rooted stock OG1, and also from the system.ext4.img with boot.img information. The installs always fail because it aborts saying the device is klte and not kltespr. I have removed the asserts line from the meta information but the rom installs but then gets stuck in bootloop.

How can I fix this?

If I manually need to install the asserts,I need to know what the 3 values are that need to be added in the asserts window in the kitchen.

Thanks for your feedback to get past this wall.
[SuperR Kitchen] SuperR.:
Regarding the assert problem, you don't need 3 values. There are 3 in the example but you can have as many as you want. I suggest keeping the auto-generated one making your line to enter as this:

klte,kltespr

This will not fix the boot loop problem however. There are so many reasons this could happen. A recovery log would be a good place to start to see if there are any errors during flashing.
[SuperR Kitchen] sparks15:
What Kitchen version?

0.9.2.4

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

Nexus 5

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

system.img and boot.img

What Android version?

6.0

What perm method (set_perm, set_metadata, sparse_dat)?

set_metadata

What did you do after extracting and before building?

Deoxeding,rooting

What have you tried that did not work?

zipalign

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

this in all apks

Zipaligning BasicDreams.apk ...

mv: cannot stat ‘BasicDreams.apk-2’: No such file or directory

Zipaligning Bluetooth.apk ...

mv: cannot stat ‘Bluetooth.apk-2’: No such file or directory

Zipaligning BluetoothMidiService.apk ...

mv: cannot stat ‘BluetoothMidiService.apk-2’: No such file or directory
[SuperR Kitchen] SuperR.:
Are you running 32-bit or 64-bit Linux?

Can you do the following in terminal:

cd /path/to/kitchen/tools
ldd zipalign

Please paste the output here. Thanks
[SuperR Kitchen] sparks15:
hi. superr im on 64 bit ubuntu

linux-gate.so.1 => (0xf77cd000)

librt.so.1 => /lib32/librt.so.1 (0xf7795000)

libz.so.1 => not found

libstdc++.so.6 => /usr/lib32/libstdc++.so.6 (0xf76a0000)

libm.so.6 => /lib32/libm.so.6 (0xf7653000)

libgcc_s.so.1 => /usr/lib32/libgcc_s.so.1 (0xf7636000)

libc.so.6 => /lib32/libc.so.6 (0xf747d000)

libpthread.so.0 => /lib32/libpthread.so.0 (0xf7460000)

/lib/ld-linux.so.2 (0xf77ce000)

fixed with apt-get install lib32z1, thanks anyway superr...Regards
[SuperR Kitchen] jtash01:
I did some exploring for the partition layout for the kltespr and generated the superr_mmc containing:

\/dev\/block\/mmcblk0p15 /boot

\/dev\/block\/mmcblk0p16 /recovery

\/dev\/block\/mmcblk0p23 /system

\/dev\/block\/mmcblk0p26 /data

and the superr_byname containing:

mmc

I placed these files in superr/devices/kltespr

I will manually add the asserts and see how it goes.
[SuperR Kitchen] SuperR.:
No. As I mentioned before, there are no command line options for the kitchen.
[SuperR Kitchen] aaron74:
oh cool. Never knew. I've been doing it the hard way. :D

Thanks.
[SuperR Kitchen] ale8530:
[MENTION=5787964]SuperR.[/MENTION]

Autorom does deodex not work, I tried various settings "AR-config", I attached the log

Whit GUI deodex baksmali/smali android 7 worked
[SuperR Kitchen] SuperR.:
v2.1.3.6 (Donate version)

Changes:

Replaced rimg2sdat with img2sdat.py by [MENTION=5132229]xpirt[/MENTION].

Removed 32-bit sparse_dat restriction.

Updated sdat2img.py by [MENTION=5132229]xpirt[/MENTION].

Updated SuperSU to v2.78-SR5.

Fixed deodexing when using AutoROM.

v1.1.2.7 (Standard version)

Changes:

Replaced rimg2sdat with img2sdat.py by [MENTION=5132229]xpirt[/MENTION].

Removed 32-bit sparse_dat restriction.

Updated sdat2img.py by [MENTION=5132229]xpirt[/MENTION].

Updated SuperSU to v2.78-SR5.

I am pretty sure this is fixed now, but I did not have time to test it. Let me know if you have more trouble.
[SuperR Kitchen] Sh0X31:
[MENTION=5787964]SuperR.[/MENTION] succesful build rom for Pixel but it not boot :(.

In TWRP it dont flash busybox & supersu. The folder structure is not correct.
[SuperR Kitchen] syztemlord:
Hi,

I'm using the donate version and in the latest update when I build my ROM it's only making a zip with about 320kb in size. I've checked the main log and it says

Any ideas why?
[SuperR Kitchen] ale8530:
[MENTION=502013]superrr[/MENTION]. now ok autorom deodex thanks :)
[SuperR Kitchen] SuperR.:
v2.1.3.7 (Donate version)

Changes:

Fixed img2sdat.py missing error.

I am not understanding what the problem is. Will you correct the updater-script the kitchen generated with the correct information and post it? Thanks

The files did not commit properly for some reason. Should work after this update.
[SuperR Kitchen] KingRaheel:
I have found a bug in the latest kitchen version. i just built a samsung rom and found out that the zip doesnt contain boot.img . I tried building the rom twice and both the times it didnt copy the boot.img in the zip file. Anyways thanks for your work buddy :good:
[SuperR Kitchen] Sh0X31:
And all the files in musst ne in system/system_root its the second partition. I'm current on system_b.
[SuperR Kitchen] celoxocis:
any way to debug this?

ERROR:
There was a problem extracting your ROM.

i just want to extract an system.img
[SuperR Kitchen] SuperR.:
v2.1.3.8 (Donate version)

Changes:

Fixed system/default.prop detection when building a rom zip.

v1.1.2.8 (Standard version)

Changes:

Fixed system/default.prop detection when building a rom zip.

Currently, the kitchen looks for /kitchen/project/system/default.prop. If it exists, the kitchen assumes your device is a Pixel or another device with the new partition layout. I am not sure if this is the best method, but I have never seen another rom that has default.prop in this location so that is what I went with. I am under the impression that we should not flash boot.img with the rom on these devices. If your device does not have /kitchen/project/system/default.prop and you are still not getting the boot.img in the zip, or if you do have /kitchen/project/system/default.prop and still need the boot.img, please send your firmware.

edit: I found the problem. Will update asap

edit2: Should be fixed now

Are you saying we should format and mount both system_a and system_b when the rom flashes? Are you also saying we should flash to system_root instead of system_a like this?

package_extract_dir("system", "/system_root");

Your system.img may not be ext4 which is the only filesystem the kitchen mounts currently. If you send a link I will take a look.
[SuperR Kitchen] Sh0X31:
Flash, we have to flash it on both partitions (system_a & system_b).

I want to flash this mod on my Pixel and I try so overwrite the SystemUI. But I always get force close so I can't set permissions and than I try so switch to slot a. But it won't boot, because I change b (my theory).

And I'm on slot_b (system_root) and I flash it on slot_a (system).
[SuperR Kitchen] SuperR.:
I still don't understand what the kitchen needs to do to make it work. There is a thread over in the Pixel section for help getting the kitchen working on Pixel devices. I just posted the current updater-script generated by the kitchen hoping someone will modify it to make it work. Let's move all the Pixel talk over there to keep it tidy :)

http://xdaforums.com/pixel-xl/help/help-to-superrs-kitchen-pixel-pixel-xl-t3519301/page2
[SuperR Kitchen] elektrik2001:
Howdy. I apologize if the .txt file isn't in the 'correct' format. For whatever reason I wasn't able to have permission (despite running sudo) to write directly to the txt file so I scraped the text from the terminal session.View attachment 3974905
[SuperR Kitchen] celoxocis:
I've actually figured out the extract problem.

The system.img was an motorola system_chunk#.img merged into an system.img.

Superr's Kitchen can't read those and couldn't extract it. Any way to add a check for those spare_chunk images?

Maybe even add the option to properly merge them?

I found a tool online by a Russian dev that fixed the merge of those system_chunk files and converted it into an proper system.img which Superr's Kitchen was able to read and extract.
[SuperR Kitchen] SuperR.:
Do a search for "sgs2toext4.jar" and I think you will find your answer.

Glad you got it sorted out :) The kitchen is able to extract older Moto chunk files (Moto G), but maybe they have changed some things since then. Send a link to the firmware and I will take a look. Please also link the tool you found if it is for Linux and/or open-source. Thanks
[SuperR Kitchen] elektrik2001:
Thanks superr!! I have NO IDEA what to do with the file but I did find it..hehe.
[SuperR Kitchen] dilnix:
Fedora compatibility

Hello SuperR.

I'v used your kitchen a lot of times in my Fedora 24 linux, made a lot of mods.

But now, when i moved to new pc with newly installed Fedora 25 i did a fresh clone of your kitchen and it can't start fully.

After a fresh clone i have launched a binary and got this:

------------------------------------------------------
SuperR's Kitchen
by SuperR
------------------------------------------------------

ERROR:
One or more tools could not be built.

Installing the following packages may help:

bison gperf build-essential zlib1g-dev zlib1g-dev:i386 g++-multilib libxml2-utils bzip2 libbz2-dev libbz2-1.0 libghc-bzlib-dev libsepol1-dev dpkg-dev make ccache automake squashfs-tools schedtool

Would you like to install now? y/n

Did a check of most of these packages mentioned that they are installed in my linux OS, may be just few of them i didn't found in OS repositories like "grepf" and "g++-multilib". But i have "grep" installed for sure and "gcc-c++".

When i choosed to answer "Y" to question above kitchen was asked me for password to use sudo and tried to "apt-get" some packages. As "apt-get" not exist in my system OS, so next screen i saw was:

------------------------------------------------------
SuperR's Kitchen
by SuperR
------------------------------------------------------

ERROR:
One or more tools could not be built.

NOTE: You should only install the binaries if you can't get the
kitchen to build them. It is recommended to have the kitchen
build the binaries if possible

Would you like to install the binaries anyway? y/n

Answered "y".

Kitchen downloaded some zip with binaries, noticed that they have been installed and offered to press ENTER to return Main Menu.

Pressing ENTER did a relaunch of kitchen with same checking of tools and same error appears as last i mentioned.

And whatever i answered it closes itself or redownloading same zip with binaries and doing nothing with next relaunch and same error appear.

Can you please suggest me, what exact me to do or check to make kitchen possible to work???

Thanks.
[SuperR Kitchen] KingRaheel:
Try installing the binaries zip manually. Or Perhaps try to install the missing dependencies one by one. Someone had asked this earlier as well, a few pages back and this solved his problem.
[SuperR Kitchen] dilnix:
A few pages back i found an answer that somebody found a solution in a changing owner of files from root to own user... But i'm doing all from own user and checked that all files are mine not owned by root.

About dependencies... I did a check for dependencies and all of them that have same package name in Fedora as in Ubuntu are already installed. Another few packages i found that have different names in above mentioned OSs i already found and have installed. But still have a problem.

It's all!

Thanks for attention. Found that one simple little package was not installed in my OS from group [MENTION=2496497]development[/MENTION]-tools.

Now all works good.

For future Fedora 24/25 users. Please do not forget to install:

1) All [MENTION=2496497]development[/MENTION]-tools group by "sudo dnf install [MENTION=2496497]development[/MENTION]-tools".

2) Package list: "lzop xxdiff xxdiff-tools vim-common bison gperf zlib zlib.i686 gcc-c++ libxml2 bzip2-libs bzip2 bzip2-devel ghc-libraries libsepol-devel dpkg-dev make ccache automake squashfs-tools schedtool kernel-tools kernel-cross-headers kernel-modules-extra kernel-tools-libs-devel".

May be some of these packages are not required, but i simply did an installation of all of them and kitchen works good.
[SuperR Kitchen] SuperR.:
I have posted test kitchens for the Pixel devices here. If you are a Pixel/PixelXL owner and would like to help get the kitchen working, please test and report in that thread. Thanks :)

I would also like some feedback about non-Pixel devices using the test kitchen, so everyone can help :)

Try something like this:

java -jar sgs2toext4.jar orig_system.img system.img

This assumes your terminal is open to the directory that contains your original system.img (named orig_system.img) and the sgs2toext4.jar file. In theory you will end up with a file called system.img that will extract in the kitchen. I have never used this jar before. Try first without sudo, then try with sudo if you get permission errors. Use at your own risk :)
[SuperR Kitchen] Mumang:
What"s happen? Update error and gitlab empty repo.

Username for 'https://gitlab.com': Mumang

Password for 'https://Mumang@gitlab.com':

remote: Not Found

fatal: repository 'https://gitlab.com/superr/superrs-kitchen2.git/' not found
[SuperR Kitchen] SuperR.:
Gitlab is the home of the donate version. You received that error because your Gitlab user does not have access to the repo.

Try the Bitbucket instructions for the standard version in post #1.
[SuperR Kitchen] TheLogicalGamer:
I am having the same problem as well trying to get a fresh clone of the donate version. I have donated and my name is on the list. Maybe gitlab is having problems?

Just in case you need to readd my gitlab is the same as my username here on xda. :)

Edit: Nevermind very sorry typo in password. I feel like a dummy.
[SuperR Kitchen] jtash01:
repository not found

Hi SuperR. I am trying to do a clean install of the kitchen but I get the following error after entering my ID and password:

remote: Not Found

fatal: repository 'https://gitlab.com/superr/superrs-kitchen2.git/' not found

I was trying this because the previous update was giving an error and said to try a fresh install.
[SuperR Kitchen] SuperR.:
My guess is that either you are entering the wrong credentials, or Gitlab is experiencing issues. Unfortunately I can't do anything about either. I just checked the repo... it still exists and your username is still active :)
[SuperR Kitchen] Lefteris Fragiadakis (Frago):
Mistake,,
[SuperR Kitchen] pendor24:
Hello

I use the donor version

After installation of kitchen ghit lab no found

an idea ?
[SuperR Kitchen] SuperR.:
It seems there must be some problem since you are the 3rd or 4th person to say something like this recently. However, the kitchen clones and runs with no issue for me so I will say what I said 2 posts ago.

My guess is that either you are entering the wrong credentials, or Gitlab is experiencing issues. Unfortunately I can't do anything about either. I just checked the repo... it still exists and your username is still active
[SuperR Kitchen] ShinySide:
Look 2 posts above yours......................
[SuperR Kitchen] pendor24:
The worry must come from ghit lab

By pressing back I had access to your deposit.

Thanks for your precisions
[SuperR Kitchen] Captain_Throwback:
[MENTION=5787964]SuperR.[/MENTION]

FYI, the HTC Decrypt Tool is up to version 3.1.0 - I just noticed the Kitchen still has 3.0.2 - Might be time to update it :).
[SuperR Kitchen] Captain_Throwback:
Also [MENTION=5787964]SuperR.[/MENTION], just tried the latest version of the Kitchen (v2.1.3.8) and the new sparse_dat setup, and came across this issue when trying to flash the resulting ROM in TWRP:

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.
unmount of /system failed; no such volume

PME 2.38.617.67 stock Installer
Built with SuperR's Kitchen

minzip: Extracted 2 file(s)
about to run program [/tmp/install/bin/backuptool.sh] with 2 args
performing update
Extracting system...

[B]unexpected transfer list version [4][/B]
about to run program [/tmp/install/bin/backuptool.sh] with 2 args
Extracting boot image...

PME 2.38.617.67 stock Installed
script succeeded: result was [PME 2.38.617.67 stock Installed]I:Updater process ended with RC=0

Not sure what "unexpected transfer list version [4]" means, but I do know it means the ROM won't flash :(. Any idea on how to fix it? I'm assuming there's some code missing from TWRP to handle the updated sparse_dat code?

EDIT: I think it means we need an updated update-binary for the sparse_dat ROMs - that's where this code lives.
[SuperR Kitchen] SuperR.:
I will get it updated as soon as I have a chance, thanks :)

This is the same error mentioned here.

1) If your rom is Nougat, the transfer list should be version 4 and TWRP may need an update.

2) If your rom is Marshmallow, the transfer list should be version 3 and this seems like a question for [MENTION=5132229]xpirt[/MENTION]. I was under the impression img2sdat automatically determines the transfer list version, but maybe not

if 2 is true, you can try opening your *.transfer.list files and change the first line from 4 to 3. If this works, I can manage this change in the kitchen if needed.
[SuperR Kitchen] Captain_Throwback:
The problem is update-binary. I swapped the one in the zip out with one from a CM14.1 ROM I had around and it worked fine. So it has nothing to do with TWRP ;).

EDIT: I'm not sure whether Nougat update-binary is backwards compatible with Marshmallow (or older Android versions) though. But it was nice to see a sparse_dat ROM install properly on my device (finally)!
[SuperR Kitchen] SuperR.:
Nice :) Would you mind posting the update-binary that worked?
[SuperR Kitchen] Captain_Throwback:
I was going to build one from the latest TWRP source to make sure > 2GB zips are allowed/working, but sure, in the meantime, here's the one I used.
[SuperR Kitchen] SuperR.:
Even better! Thanks :)

edit: once this is working properly, sparse_dat may become the best option for roms built with this kitchen. I really appreciate your help :)