yashsingh1/xdaforums huggingface dataset:
[SuperR Kitchen] jesus183095:
Of this

---------- Post added at 12:31 PM ---------- Previous post was at 12:30 PM ----------

i try to change klte,kltespr

but i dont found the superr_mmc in my kitchen device. and not found this rute. And i wathce the build.prop in my device in the line ro.product.device=fortunave3g

and the ro.product.model= SM-G530H

i very rare. and i not understand the stepts of change to fix this problem.

I need the edit the superr_byname? or other file and i have file name is this project_grand_prime and inside of this exist a archive call assert and says this:

assert(getprop("ro.product.device") == "fortunave3g" || getprop("ro.build.product") == "fortunave3g" ||

abort("This package is for "fortunave3g" devices; this is a "" + getprop("ro.product.device") + "".")￼;

what i change or what line is? i adjunt some pictures to explain more.

http://xdaforums.com/attachment.php?attachmentid=3512283&stc=1&d=1445289955

http://xdaforums.com/attachment.php?attachmentid=3512284&stc=1&d=1445289955

http://xdaforums.com/attachment.php?attachmentid=3512285&stc=1&d=1445289955

http://xdaforums.com/attachment.php?attachmentid=3512286&stc=1&d=1445289955

Of this..
[SuperR Kitchen] SuperR.:
There is no need to mess with the files. Go to rom tools, asserts, add the devices you want, press enter.

edit: you don't need an mmc file because your device supports by-name.
[SuperR Kitchen] svandasek:
Very nice tool [MENTION=5787964]SuperR.[/MENTION]R !!!! Yesterday I managed to modify my ROM in just 3h!!! Couldn't believe, how easy it was. Today I will see, if it boots.

I would like to have the donated version too, but unfortunately I don't have PayPal as I don't have a credit card and I am not 18. Is there any other way I could get it?

Thanks for your work:svetius::)
[SuperR Kitchen] nightcervant:
Here the firmware used:

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

you have a tool to suggest?
[SuperR Kitchen] SuperR.:
Unfortunately I don't have another donate option at the moment. Sorry and thanks for trying :)

I was able to extract the system.img and boot.img from your UPDATE.APP using the updateapp plugin. The system.img extracted with no issues. I don't know what is going on with your setup, but I uploaded the system.img and boot.img from your firmware here. Hopefully that will get you going :)

The only thing I noticed is that your boot.img does not use by-name directories so I was not able to get the by-name from boot.img.
[SuperR Kitchen] ladislav.heller:
Sorry for late response, yes, exactly that was the solution.

But now, after I created/flashed a new ROM on Sammy device, the USSD codes stopped working from dialer app.

I can't even get the IMEI number using *#06#
[SuperR Kitchen] svandasek:
So I built my ROM, flashed and rebooted. The boot animation came up so I thought that it will boot! But then I put my fingers on my phone and it was ****ing hot.. i was unable(!!) to let my fingers on the top of the device. So I switched the device off.

And when I booted into recovery, it asked for decrypting password. Because I forgot to flash su after the ROM, it started encrypting when booting, but I switched the device off while booting, so the /data partition was corrupted and unable to mount. So this is how I had to wipe my phone (including some not backed up photos) and set it up at 11pm....

I don't know if I will continue to do this :(
[SuperR Kitchen] nightcervant:
Hey [MENTION=5787964]SuperR.[/MENTION] , I downloaded your version of Ubuntu and tried to do it all over again, and like magic the extraction has been successful, I think it was something corrupt in my old distro
[SuperR Kitchen] 曦颜XY:
hey,friend,I'm come from China,I like your kitchen,but your tool is not Chinese, so I translated the language files in “tools/language” ,How do i contact you and give it to you?
[SuperR Kitchen] AnonVendetta:
[MENTION=5787964]SuperR.[/MENTION]: I decided to make a donation for your cause. My GitLab account name is AnonVendetta, "John Doe" is the name on my profile but it isn't my username. Please add me so I can access your private repo.

Thanks!
[SuperR Kitchen] SuperR.:
Hopefully another Samsung user can help out.

Sorry you had a bad experience.

You can zip and attach the language file here.

Added, thanks :)
[SuperR Kitchen] vincom:
ur probably missing the test codes apks, there somwhere in the app, priv-app folders, and might be in one of the .img files samsung has like hidden.img, u might have to extract all the img files that are in stock fw.

here is an example of mine for s5, theres more than one apk, service codes, test codes etc

https://www.androidfilehost.com/?fid=745425885120712141
[SuperR Kitchen] 曦颜XY:
when you see that link page,you can see "下载（27kb）",you should click it to download.

LINK: ht "deleteme" tps://pan. "deleteme" baidu.com/s/1qXQnFJ2 , "deleteme" means that you should delete it so that you can normal to see link page
[SuperR Kitchen] ladislav.heller:
Wow, thanks for suggestions, I'll try hidden.img
[SuperR Kitchen] tomatolei:
SuperRs_Kitchen_v1.1.4.4 has a bug

Samsung SM-G9350 QC1 7.0 Nougat ，Get set_metadata has some bug，Will cause VOLTE HD can not use

and Camera setting open Dynamic photos has fc
[SuperR Kitchen] genuine55:
[MENTION=5787964]SuperR.[/MENTION] Can I use this to build a oxygen os ROM on my one plus 3 ? Thanks in advance
[SuperR Kitchen] bcrichster:
This Kitchen is meant to modify preexisting files, not build ROMs from source
[SuperR Kitchen] genuine55:
Thanks trying to figure it out
[SuperR Kitchen] bcrichster:
Figure what out, building from source? This kitchen does everything else you could possibly want except that. I'd install this Kitchen anyways (I do), especially the donate version since it's still very useful and most or all the dependencies required to run this Kitchen will also be required to build from source.
[SuperR Kitchen] genuine55:
Ok thanks will do I will download it also :good:
[SuperR Kitchen] {_KeNJi_}:
donated! _kenji_ at gitlab
[SuperR Kitchen] SuperR.:
Unfortunately I have not developed the ability to read minds over long distances, but as soon as you tell me what the bug is and how to fix it I certainly will :)

As [MENTION=5297774]bcrichster[/MENTION] said, you could use an existing Oxygen OS rom with the kitchen. You can extract, modify, rebuild etc but you can't build a rom from source code using the kitchen.

Added, thanks :)
[SuperR Kitchen] {_KeNJi_}:
Sorry, but i get

remote: Not Found

fatal: repository 'https://gitlab.com/superr/superrs-kitchen2.git/' not found
[SuperR Kitchen] SuperR.:
Send me a PM (private message) with the email address you used to sign up for gitlab.
[SuperR Kitchen] :
Hello! It seems that i cant access the ROM Tools menu, where you can root and deodex your ROM.

When i press (5) nothing happens. The kitchen's version is the latest. I'm trying to port C9 Pro rom (6.0.1) to my Galaxy J5.

If you need any logs feel free to ask.

Thanks

EDIT: Forgot the OS, i am running a virtual machine with Ubuntu 16.04.2 LTS on it.

EDIT AGAIN: dumb me forgot to set perm types :P
[SuperR Kitchen] TheHiman:
[MENTION=5787964]SuperR.[/MENTION]: I found a new Permissions-Bug:

In the last kitchen Versions the file-permissions after deodexing are not correct for nearly all directorys:

Dirs: app/framework/priv-app/etc all files and became 664/775 instead 644 or 755.

Please check with an actual samsung 6.0.1 image and compare with the original image file ;)
[SuperR Kitchen] micr0g:
Hi

Anyone with a succesfull cook for sailfish/marlin here?I need some help.

Thanks
[SuperR Kitchen] SuperR.:
It seems like you got it sorted out. Let me know if you are still having problems.

Please explain better what you are trying to do and the problem. What perm type? OS? Does it only happen when you deodex? Is it a full rom, system.img, custom zip, etc? What exact steps can I take to reproduce the problem? Link to firmware?

Help me help you :)

You are more likely to get help if you explain the problem :)
[SuperR Kitchen] :
[MENTION=718594]SuperR[/MENTION] yeah i sorted it out! Thank you for this amazing kitchen! <3
[SuperR Kitchen] TheHiman:
I do the following:

using G900F-complete image, unpacking -> rom-tools -> debloating -> deodexing with smali/baksmali -> main-menu -> Extras -> zipalign (without /framework folder).

The content inside the system-dir is then compared to the original system.img "rwrwr " instead "rw r r" for the files in app/framework/etc/priv-app.

Directory mode is changed from 0755 to 0775 chmod. All original files in /etc folder are touched (and became a net timestamp).

A Question by the way: when you copy the entire image content to the work folder... Can you keep the untouched original date for all files and folders, which are

not modified in any way to have in the final image the same timestamps ?

In my case i directly use the resulting files in the "system"-folder, not using your integrated scripting for makeing a flashable zip in the kitchen itself.

So the half-way process needs a manual chmod every time.
[SuperR Kitchen] kevintm78:
I may be misunderstanding what you're saying but I have Note 4 with 6.0 and I've built 2 roms on the latest build with the last 2 firmwares that Sammy released. I haven't had any permission issues using set_metadata. If you're not using an updater script that the kitchen is generating then whatever script you're using is setting the permissions. I suggest just letting the kitchen build your zip it hasn't let me down yet. Is there a reason that you don't want to use the generated updater script?
[SuperR Kitchen] vincom:
also using g900f, idont have that problem

heres snippet of script made by superr kitchen:

set_metadata_recursive("/system", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0644, "capabilities", 0x0, "selabel", "u:object_r:system_file:s0");
set_metadata_recursive("/system/bin", "uid", 0, "gid", 2000, "dmode", 0755, "fmode", 0755, "capabilities", 0x0, "selabel", "u:object_r:system_file:s0");
set_metadata("/system/bin/ATFWD-daemon", "uid", 0, "gid", 2000, "mode", 0755, "capabilities", 0x0, "selabel", "u:object_r:atfwd_exec:s0");
set_metadata("/system/bin/PktRspTest", "uid", 0, "gid", 2000, "mode", 0755, "capabilities", 0x0, "selabel", "u:object_r:diag_exec:s0");

set_metadata("/system/etc/bluetooth/bt_did.conf", "uid", 0, "gid", 0, "mode", 0644, "capabilities", 0x0, "selabel", "u:object_r:system_file:s0");
set_metadata("/system/etc/bluetooth/bt_stack.conf", "uid", 0, "gid", 0, "mode", 0644, "capabilities", 0x0, "selabel", "u:object_r:system_file:s0");
set_metadata_recursive("/system/etc/dhcpcd", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0644, "capabilities", 0x0, "selabel", "u:object_r:dhcp_system_file:s0");
set_metadata("/system/etc/dhcpcd/dhcpcd-hooks", "uid", 0, "gid", 0, "mode", 0755, "capabilities", 0x0, "selabel", "u:object_r:system_file:s0");
set_metadata("/system/etc/dhcpcd/dhcpcd-run-hooks", "uid", 1014, "gid", 2000, "mode", 0550, "capabilities", 0x0, "selabel", "u:object_r:system_file:s0");
set_metadata("/system/etc/event-log-tags", "uid", 0, "gid", 0, "mode", 0644, "capabilities", 0x0, "selabel", "u:object_r:event_log_tags_file:s0");
set_metadata_recursive("/system/etc/firmware", "uid", 0, "gid", 2000, "dmode", 0755, "fmode", 0644, "capabilities", 0x0, "selabel", "u:object_r:system_file:s0");
[SuperR Kitchen] TheHiman:
ah ok, guys. You talk about the "final" results which are produced by the kitchen with all the scripts and "permission-files".

I was talking about the creating of the "system" folder inside the kitchen (Where the unpacked files go in and the deodexed results are build).

THIS directory contains, compared to the original extracted image-files, the wrong linux-file permissions (chmod 775/664 instead 755/644!).

Personaly i only use the content from this "working"-dir after deodexing/zipaligning and make further processing by copying the resulting content

to my own final buildprocess with other image-scripting things ;)
[SuperR Kitchen] SuperR.:
This is a feature request, not a kitchen bug.

Changing the following lines may get what you want:

${usesudo2}cp -R output/* ${extractimg}/
${usesudo2}chown -hR $myuser:$myuser $romdir/${extractimg}
${usesudo2}chmod -R ug+rw $romdir/${extractimg}

Change them to:

${usesudo2}cp -PR output/* ${extractimg}/
# ${usesudo2}chown -hR $myuser:$myuser $romdir/${extractimg}
# ${usesudo2}chmod -R ug+rw $romdir/${extractimg}

This will leave the files as close to original as possible. Note that you will have trouble working with these files unless you are root and you will likely get errors in the kitchen after the extraction.
[SuperR Kitchen] TheHiman:
Ah, this was because on non-root usage. In my case i always use a modified kitchenscript and disabled the uid=0 check, so i´am using root since first

usage of the kitchen. Never had any problems with this ;)
[SuperR Kitchen] _that:
Of course it's convenient to run as root. Until one day your script will run into a line like "rm -rf /$stuff" and due to some weird bug, $stuff isn't set.
[SuperR Kitchen] :
Heya.

Some gcc update on Arch probably borked the stat workaround. Here's the error i get now.
[SuperR Kitchen] Manjot xda:
This tool is not working. getting this error every time:crying:. After pressing Y in some time again this error msg shown
[SuperR Kitchen] JonathanRAZ:
Y wont work is y
[SuperR Kitchen] Hamidreza2010:
Press Y not solve problem

you should download these:

gawk

lz4

lzop

then run kitchen again
[SuperR Kitchen] triggz881:
I'm having some trouble with the kitchen. I previously used the free version and it worked perfectly for me. A few months have passed since and now I can't create a working rom.

What Kitchen version?

2.1.5.4 paid

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

ubuntu4kithchen 64bit

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

lg k550

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

tried multiple sources, the free kitchen previously used to pull from my phone without a problem. Now I get an error.

ERROR:

Something went wrong. Most likely you lack permission to

pull images from your device, or you don't have enough

space on your device to store the images.

I have an empty internal memory of about 8gb free and a memory card with about 30gb free

What Android version?

6.1

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

set_metadata when it used to work

What did you do after extracting and before building?

i can manually extract my system and boot images from official lg kdz's but even when I dont alter the rom, and just rebuild, the installer fails

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

see above

Send a link that does not require registration to the files you started with (nandroid, system.img, boot.img, etc)

I'm experiencing internet problems at the moment I will try update the post if i can get them uploaded.

Use the support option in the Misc Tools menu and attach the support.zip to your post.

Today I created a fresh install of ubuntu4kitchen, fully updated it, installed the paid version of the kitchen. I managed to use the sys and boot images pulled from stock kdz to create a few images

1) stock image - says it installs but 'flashes' in less than a second

2) stock image with aroma (used plugin) - fails with syntax error after starting aroma

'SYNTAX ERROR!!! aroma-config on line 155 col 4'

updater ended with error 1.

3) debloated image with aroma - aroma starts fine i can select my options but when it goes to flash it takes less than a second and says it is complete.

my internet is unreliable at the moment and extremely slow, im told it should be fixed 2 days ago so when it finally does get fixed i can upload anything you need

edit: I downloaded previous version of the paid kitchen (2.1.3.2) and that version will pull files from my phone, so something seems to have broken in between.
[SuperR Kitchen] bcrichster:
sudo apt-get install gawk lz4 lzop [Code]
[SuperR Kitchen] PaulPizz:
I'm trying to put a rom together for the pixel XL. I keep getting the error shown in the attached pic using twrp. It seems it an updater script issue. Any ideas?? View attachment 4078401
[SuperR Kitchen] Captain_Throwback:
Recovery log...
[SuperR Kitchen] bcrichster:
sudo apt-get install lz4

sudo apt-get install lzop

sudo apt-get install update

sudo apt-get install upgrade

Then try again
[SuperR Kitchen] SuperR.:
I think I found the problem, and it will be fixed in the next update. Busy lately so I don't have as much time to play :(

Not sure how to deal with this yet. Have you tried installing libselinux/libsepol and using the standard stat binary? I have no idea if this is possible without an selinux enabled kernel but it is worth a try. Alternatively, you could try getcon from the setools package. Again, not sure if your system needs to be selinux enabled to use it. These are things I can't test easily since my system is selinux enabled. If you figure out how to get the file contexts without having an selinux enabled system, pleas let me know.

First, lz4 is not needed by the kitchen anymore since AIK includes it so it will be removed from the tools/dependencies list in the next update. You can delete it now to help you get started if you want. lzop may be in another package called something else. You will need to find it and get it installed. You can also take a risk and remove it from the dependencies list to get the kitchen started. However, you may have trouble unpacking/repacking your boot.img if it is lzop compressed.

I will try to see what the difference is. Are you attempting to extract images while booted in Android or recovery? Try the other one if you have not already.

The Pixel devices are still somewhat of a mystery to me as I don't own one. I was told the kitchen works on Pixel devices though, so I am not sure. There are a couple Pixel users around here somewhere, hopefully they will help us :)
[SuperR Kitchen] bcrichster:
[MENTION=1162986]Captain_Throwback[/MENTION] . I thought I read somewhere that you and some others us Arch Linux.. Is there a different pkg list you guys use for the installation of this Kitchen? I have a buddy having trouble installing on Manjaro..
[SuperR Kitchen] ShinySide:
Step 1- delete manjaro

Step 2- install arch

Step 3- problems how? Lol
[SuperR Kitchen] bcrichster:
[emoji23]

Already tried that approach.. He just likes pacman, Lmao. It keeps giving him grief about default-jre but I told him to manually install it and manually switch from 7 to 8.. Am I the one confused?
[SuperR Kitchen] ShinySide:
Pacman is default package manager for arch lol

Manjaro *should* already have a Java installed as they're like the Linux mint of arch lol if not install with pacman for openjxx or use yaourt for Oracle

Run

archlinux-java status

Then set with

archlinux-java set <java package name you got from status>
[SuperR Kitchen] bcrichster:
Thanks Mang! [emoji41]
[SuperR Kitchen] corp769:
SuperR: I just donated to you within the previous half hour or so, my nickname on gitlab is electrohead. Thanks for taking the time to make this!
[SuperR Kitchen] bcrichster:
Sent PM
[SuperR Kitchen] vincom:
[MENTION=718594]super[/MENTION]r i cant get this script to state "not" even when theres not enough free space in the data partition. i changed values to even exceed what the actual space is but it always outputs "free"

#!/sbin/sh

# EDIT value for your system.img size in bytes
imgsize="4399104"

#DO NOT EDIT unless you know what you are doing
free=$(df /data | grep /$ | tr -s ' ' | cut -d' ' -f4)
free=$(($free - $imgsize))

if [ $free > '20971520' ]; then
result='free'
else
result='not'

echo "available=$result" > /tmp/config
[SuperR Kitchen] arkansawdave74:
Why on Earth would anyone downgrade from Manjaro to Arch, lol. But I saw the problem. Said missing dependency in dark red block and I missed the Open Jdk8 in dark red print just below it. I thought default-jre was the dependency it was talking about (suprisingly not available in the AUR unless it was renamed). As soon as I spotted the jdk8 I had it up in no time. I blame it on my dark red theme and background and 50% opacity terminal that makes dark red hard to spot. I also blame it on me not listening to [MENTION=5297774]bcrichster[/MENTION]. Thanks for the great program!!

See what I mean?? Lol.
[SuperR Kitchen] SuperR.:
You are using the script where I forgot the fi. It should be:

#!/sbin/sh

# EDIT value for your system.img size in bytes
imgsize="4399104"

#DO NOT EDIT unless you know what you are doing
free=$(df /data | grep /$ | tr -s ' ' | cut -d' ' -f4)
free=$(($free - $imgsize))

if [ $free > '20971520' ]; then
result='free'
else
result='not'
fi

echo "available=$result" > /tmp/config

If it still does not work, make sure your device has the df utility available because it won't work without it. Most modern Android should have it.

edit: Here is the latest test I made for this https://www.androidfilehost.com/?fid=817550096634750831
[SuperR Kitchen] vincom:
i pasted from wrong code, the one ive been playing with is this where result must = "not" but always ="free" even though i only have 500mb free on sdcard.

ive tried various number combinations but result always =free even to the point where twrp errors itself out of not enough space after this script passes as free, in config its always available=free

in twrp in terminal df posts values of my partitions and even tried the mmcblk0p25 name of my data

#!/sbin/sh

# EDIT value for your system.img size in bytes
imgsize="2597322752"

#DO NOT EDIT unless you know what you are doing
free=$(df /dev/block/mmcblk0p25 | grep /$ | tr -s ' ' | cut -d' ' -f4)
#free=$(($imgsize - $free))
free=$(($free - $imgsize))

if [ $free > '2220971520' ]; then
result='free'
else
result='not'
fi
echo "available=$result" > /tmp/config

i pasted from wrong code, the one ive been playing with is
[SuperR Kitchen] :
Speak for yourself.

I'd hate if a distro force me to use some custom DE that changes every release.

Plus it has it's own repo, both which negates the point of building from scratch on Arch anyway.

Solved by compiling coreutil with selinux.

Package is available on AUR, but current version fails some test. Workaround is available on the cooments there, but it should be fixed on the next release,
[SuperR Kitchen] SuperR.:
v2.1.5.5 (Donate version)

Changes:

Fixed KitKat and older deodex not finding the correct smali/baksmali.

Combined L-N deodex functions eliminating ~1500 lines of code.

Added error checking to smali/baksmali deodex method.

Updated smali/baksmali to the latest commits.

Create set_metadata lines for all /system/bin and system/vendor/bin files when extracting system.img.

v1.1.4.5 (Standard version)

Changes:

Fixed KitKat and older deodex not finding the correct smali/baksmali.

Combined L-N deodex functions eliminating ~1500 lines of code.

Added error checking to smali/baksmali deodex method.

Updated smali/baksmali to the latest commits.

Create set_metadata lines for all /system/bin and system/vendor/bin files when extracting system.img.
[SuperR Kitchen] droidvoider:
Am I missing the install instructions or are there not any specific install instructions? This is my second installation because the first time I made the mistake of using the software updater to install a couple of the things listed and it crashed my libusb1.0.0 out so heimdall wouldn't work. (then i purged and so here I am after reinstall)

I get the the instructions for the tools but are there any specifics ways for installing things? Like the SDK, NDK, paths, Java 1.7 for aosp.. I am doing this all the old school way either deb or ppa
[SuperR Kitchen] bcrichster:
You need openjdk8 & jre8 installed to operate the kitchen. Manually switch Javas when necessary