yashsingh1/xdaforums huggingface dataset:
[SuperR Kitchen] nightcrow:
Thanks for the update! Just updated the kitchen and there seems to be a problem with the desktop shortcut that comes with the Ubuntu image-file you posted, I can't use that shortcut anymore to run the kitchen. So I opened a terminal in the kitchen folder and followed your instructions:

git clone https://gitlab.com/superr/superrs-kitchen2.git

cd superrs-kitchen2

./superr

and then I can run the kitchen from the kitchen-folder. However when I add a new shortcut to the desktop it doesn't work. Strange :confused:

PS tried the new smali/baksmali deodexing on my S7 ROM with android 6.0.1 but still getting an error 'unfortunately samsung keyboard has stopped' when it boots so I can't make it through the set-up properly
[SuperR Kitchen] SuperR.:
The shortcut on the desktop in Ubuntu4Kitchen is not a shortcut actually, it is a script. I just tried it and it seems to be working here. You can download the latest script and manually extract it to your desktop if you want to try again. Just make sure it is executable after extraction. It will be if you extract in Linux, but it will not be if you extract in Windows and copy it to Linux.

Thanks for reporting back about the new M smali/baksmali on the S7. That is unfortunate news. I was hoping this would work since I did not get any errors at all while deodexing :(
[SuperR Kitchen] serch826:
Thanks @SuperR

As always i tested the Kitchen with the new updates and can say that now is working again the Deodexing on "N" roms, i used the Smali-baksmali and selected to remove the META-INF and signed the modified SystemUI with the original apk and it worked fine.

Thanks again for your work.:good:
[SuperR Kitchen] nightcrow:
Sorry to bring the bad news and it might be that I'm doing something wrong, however when I flash an odexed ROM everything is working fine. Using svadev's tool deodexing isn't that much of an effort. Although it would be great to be able to debloat and doedex using your kitchen.

Which, even without the deodexing part, rules bigtime. So keep up the good work, the script you posted is working well! :good:
[SuperR Kitchen] SuperR.:
Sadly, I have no idea why Samsung deodexing is different. It seems like Samsung requires another step the kitchen does not do. If I knew what that step is I would add it, but I am clueless.

Regarding debloat, if you send a list of files that are considered by the majority to be bloat I will add them to the debloat list. I am unaware of the bloat other carriers add so feel free to contribute :) Additionally, there is a "bloat_custom" file in /kitchen/tools/root directory and you can add anything you want to it. You should avoid editing the "bloat" file, but you can copy it to "bloat_custom" and/or use it as a guide to create your own. Then you can use the custom option to debloat and get exactly what you want removed.
[SuperR Kitchen] Georgiafan1969:
gitlab.com Georgiafan1969 1CD82226HA789764V
[SuperR Kitchen] nightcrow:
Thanks man, debloating works like a charm using the bloat_custom file. I have an S7 with stock Android 6.0.1 and Touchwiz and I'm using the attached list to copy into the bloat_custom file to debloat with your kitchen. However this is a pretty long list and of course it's my personal preference. So I can't tell if the majority of S7-users think this is all bloat as well. But feel free to do with it whatever you like :good:

About the deodexing: it's always the same error after the boot-up telling me that 'unfortunately, samsung keyboard has stopped' so it might be that specific app that's causing the trouble. I'll have to take a closer look at it too.
[SuperR Kitchen] SuperR.:
If some others take a look at your list and come to a consensus, I will add it to the list. Thanks for sending it :)

Do you get that keyboard error if you deodex without removing anything? Not saying you did, but it is possible that removing something else may cause the keyboard to break. Grasping at straws here :p
[SuperR Kitchen] nightcrow:
Hmm good question, can't remember to be honest if I always debloated the ROM's after I tried deodexing them with the kitchen. I'll give it a try as soon as I've got some spare time on my hands :)
[SuperR Kitchen] Chrisis42069:
alright i need some advice. i updated my linux mint distro to 18 (sarah), and now i can run the ubuntu4kitchen and your awesome tool using vbox! progress!! now i tried installing the kitchen in my host os , mint 18, and was greeted by an error stating certain tools couldn't be built or something to that effect and that installing a list of dependencies may help. so naturally i chose to install said dependencies but to no effect and am still getting the same error message. running on vbox is okay and gets **** done but both my computers only have 4 gigs ram so things tend to move a little slow sometimes. i plan on upgrading that soon. i also considered dual booting it but couldn't get the computer to even recognize the disc or the bootable usb image i made. ive set up dual boot in a few computers so including this one so im kinda stumped. any input is appreciated.thanks again. once i upgrade my ram to 8 gigs vbox should run a little quicker and be somewhat tollerable but really id love to install this directly to a hard drive. thanks again.
[SuperR Kitchen] scrappy610:
Installing with vbox is not too hard. And im sure you have it installed correctly, however one thing i noticed with vbox and mint, you have to install the guest tools for vbox too in order to get the right permissions for folder manipulation. Also, theres a list of deoendencies for the kitchen, i believe in the op, if not there post 2 or so. Copy paste those in terminal to make sure they are up to date and installed, i had to force install two. If you notice any not installing try force installing.

If your running windows 10, my bet with it not recognizing the cd/usb is uefi. It gave me fits too, finally found a site with decent info to figure it out

sites.google.com/site/easylinuxtipsproject

Ypu can pm me if ya need more specific help.

---------- Post added at 03:21 PM ---------- Previous post was at 03:15 PM ----------

Samsungs notorious for being a pain. Give me about 30 minutes and ill try deodexing my s7 edge completely stock, then I'll try everything except the keyboard.
[SuperR Kitchen] SuperR.:
In Mint and Ubuntu, you may need to enable the universe and multiverse repositories. Some of the dependencies come from there. I think this will do it for you:

sudo add-apt-repository universe
sudo add-apt-repository multiverse
sudo apt-get update

Once they are enabled, let the kitchen try to install the dependencies again. Hopefully you will have better luck :)
[SuperR Kitchen] s.sunfeihu@gmail.com:
Hello buddy! I just deodex n9300 caused a lack of storage tips in the notification bar, and each restart are optimized applications, you can help me solve it, if you can help me solve, I will donate you!
[SuperR Kitchen] Frankbrazillian:
Thank you very much for the update SuperR! I already have deodexed with another tool, and everything worked perfectly! But tried again with your tool updated and this time, no issue with storage and everything worked perfectly, even the japanese Samsung Keyboard, with i got fc with all tools i have tested untill now. The only fc i got is with the Health, but no problem with that. Thanks to you, now i can do all work on linux. :)
[SuperR Kitchen] s.sunfeihu@gmail.com:
Hello friends! You use SuperR tool odex choose that? Oat2dex / oatdump / baksmali! "Another tool" can recommend to me to try!
[SuperR Kitchen] Frankbrazillian:
Deodex

Hi buddy! I have deodexed my TW Marshmallow rom with the latest version of the SuperR Kitchen! The SuperR have updated the Baksmali/Smali method on the latest version... This is what i have choosed and worked perfectly for me. If even the latest version won't work for you, you may give an try with the svadeodexer tool, like suggested by some users... Worked for me with one rom, but not with another one.... The svadeodexer tool is under Windows platform and have 2 versions (32 and 64 bits). Hope one of this two, can help you.... :)
[SuperR Kitchen] s.sunfeihu@gmail.com:
Thanks buddy!I use the sva deodexer tool and the old superb tool, but the notification bar prompts the storage is insufficient and each restart are optimized 300+ applications!
[SuperR Kitchen] Frankbrazillian:
So, unfortunatelly i can't help you... Sorry Buddy! Only with these 2 tools, i get it to work.
[SuperR Kitchen] s.sunfeihu@gmail.com:
Thank you very much, bye!
[SuperR Kitchen] Frankbrazillian:
You're welcome ! :)
[SuperR Kitchen] nightcrow:
Just tested it and I only deodexed the ROM without debloating it. Boot-up brings me even more errors (smart card manager, keyboard and some others). So I'm afraid it has something to do with the deodexing :(

No problem since svadev's tool works fine for me. Couldn't you implement his script in your kitchen?
[SuperR Kitchen] magdeoz:
I'm trying to create a rom debloated, but when you install the wifi does not work.

some help plz
[SuperR Kitchen] ShinySide:
I say over clock the flux capacitor from 1.21 jigowatts to 1.22 jigowatts. Should force a wifi scan. If the power supply isn't available for that tho you might need to download a Mr. Fusion.

P.S. you really need to give people more to work with than just "wifi don't work". Like a log or at least what you deleted
[SuperR Kitchen] :
Hi, I am using Arch Linux with all the dependencies installed and this just shows up. Can someone help me with this? I've tried reinstalling Superr's Kitchen and its still the same.
[SuperR Kitchen] magdeoz:
I think I said "debloated" simply bone I used that option and I have not done anything more, I think you should read carefully before responding stupid. really do not understand how you can lose wifi just remove some apps
[SuperR Kitchen] ShinySide:
I use it on it on Arch but had to change the default shell from zsh to bash in order for the script to run. Might be your problem as well.
[SuperR Kitchen] scrappy610:
Thats actually not that difficult. But we do need more info to help, did you lose wifi totally? Or do you only lose it on reboot? It may have nothing to do with apps you remove and instead to do with another file somewhere.
[SuperR Kitchen] ShinySide:
Could be because system apps/jars, which debloating means deleting system apps and/or jars, is what makes you capable of turning on/off / control things such as hardware features such as......wifi. kinda like delete your display drivers,etc and boom blank screen. But seriously at least a log is needed because where is anyone supposed to start to help you?
[SuperR Kitchen] :
My default shell is bash, I don't even have zsh installed. It is stuck how the screenshot is with blinking terminal cursor and it stayed like that for 20 minutes. Is there anything else I can do to try and fix it?
[SuperR Kitchen] SuperR.:
Try removing the space between "Android Hacking" in your kitchen path.
[SuperR Kitchen] ShinySide:
Can you run chsh -l and post the output
[SuperR Kitchen] :
omg thanks lol I'll just have a underscore instead of a space

---------- Post added at 03:07 AM ---------- Previous post was at 03:02 AM ----------

Already fixed but here is the output anyway.
[SuperR Kitchen] TMG1961:
When i try to built my Nougat rom i choose option 1 (Device through adb shell (recommended)) but i keep getting message something went wrong try another detection mode. Never had this problem before.
[SuperR Kitchen] BlueFlame4:
FYI the $SHELL check is not reliable. When launching bash within zsh it will still tell me that zsh is used. Better use $0 or $BASH (which is only set in bash obviously).

Thanks for your work!
[SuperR Kitchen] SuperR.:
You must have an older kitchen version. I changed the recommended method to be boot/recovery image a while back. In any case, getting by-name from the boot.img seems to be the most reliable for most devices.

Agreed, thanks for pointing it out :) Will make the change for the next update.
[SuperR Kitchen] TMG1961:
I am using kitchen version 2.1.1.4 and got a Nexus 6

The Rom that i am trying to build is stock android 7, only rooted and debloated.

These are the steps i take to create my own rom:

- I start the kitchen and choose n to start a new project

- Then i move the system and boot.img from the downloaded factory image to the project folder

- In the main menu i choose option 4 to extract the system.img and choose perm type Sparse dat

- After the image is extracted i root and debloat the rom

- After rooting and debloating i choose option 8 in the main menu and then option 7 in Rom Tools Menu

- In Build Menu i choose option 1 to build full rom zip

- Then i choose option 1 (Device through adb shell)

- Then i choose y to continue and get the message something went wrong press enter to choose another detection method

This is how i always have build my rom and never had any problems

Maybe its something on my site, using Linux Lite 3.0
[SuperR Kitchen] bcrichster:
Have you tried using a full Linux distro? I only ask because some bare bones OS's may lack some fundamental programs (I'm unsure of) &/or dependencies needed..

Sent from CM12.1 *N9515*
[SuperR Kitchen] TMG1961:
I am using the kitchen for some time on Linux Lite, it has always worked without a problem. Did built several marshmallow roms with it for own use. Today i started all over again, did a complete fresh install of the kitchen. When i set perm type to sparse_dat i get a error, but when i use set_metadata then the rom builds without any errors. but it doesnt boot.

Edit: Will do some more testing later today
[SuperR Kitchen] SuperR.:
I am not sure why the adb shell option is not working, but you can use 2147483648 to enter the system partition size manually for the Nexus 6, or you can use the system.img to get the correct size. That should get it building. Keep in mind that you may also need the matching vendor.img from the firmware included in your rom or you may have issues. The kitchen will extract everything you need from the firmware if you choose the full firmware package from the extract menu.

I will do some testing on my 5X to see if I can figure out why it is not detecting the partition sizes on N.
[SuperR Kitchen] TMG1961:
Never needed vendor.img I got a nexus 6, always flashed the roms i built without the need for a vendor.img.

Wouldnt even know were to find one, it is not in the factory download
[SuperR Kitchen] SuperR.:
v2.1.1.5 (Donate version)

Changes:

Changed bash check to use $BASH instead of $SHELL.

Fixed M and N smali/baksmali and oatdump deodex methods leaving stray dex files in framework and not creating jar files that do not already exist.

Path without spaces error is now English only due to the language file not being loaded before the error.

Fixed partition size detection using adb shell on N devices.

Updated smali/baksmali and oat2dex to the latest commits.

v1.1.0.4 (Standard version)

Changes:

Changed bash check to use $BASH instead of $SHELL.

Fixed M and N smali/baksmali and oatdump deodex methods leaving stray dex files in framework and not creating jar files that do not already exist.

Path without spaces error is now English only due to the language file not being loaded before the error.

Fixed partition size detection using adb shell on N devices.

Updated smali/baksmali and oat2dex to the latest commits.

NOTE: Thanks to [MENTION=7098311]TheHiman[/MENTION] for pointing out the stray dex files on his Samsung ROM. This update may help Samsung deodexing using smali/baksmali and oatdump, so please let me know how it goes :)
[SuperR Kitchen] alex.deveaux:
v1.1.0.4 (Standard version)

SHELL ERROR:

Bash is required to use this kitchen.

The kitchen is currently running in /bin/bash.
[SuperR Kitchen] russel5:
This is because kitchen used not right $BASH string

if [[ ! $(echo "$BASH") = "bash" ]]; then

for me (and you) $BASH is "/bin/bash" and we are need some changes

if [[ ! $(echo "$BASH") = "[COLOR="Red"]/bin/bash[/COLOR]" ]]; then

and all will work :p
[SuperR Kitchen] SuperR.:
Sorry about that. I had already fixed this in the donate version but forgot to make the change in the standard.

v1.1.0.5 (Standard version)

Changes:

Fixed bash check.

edit:

Updated apktool.jar to the latest commit in apktools plugin.

Updated autorom_config plugin to include the new deodex methods.
[SuperR Kitchen] Fap4k:
Need Help

Hey please help me it was working earlier on my system but now its not working.

it is asking me again and again to install default-jre which is already installed.
[SuperR Kitchen] SuperR.:
You need java 8 as the error tells you. You have java 7 as your screenshot tells you. Your default-jre is 7, so you need to update your OS, or figure out how to install java 8.
[SuperR Kitchen] lugiank:
Hi guys, I have a little problem.

I'm trying to cook something just for myself, but my s7 edge (exynos) is not helping me.

I tried some different configurations:

set_metadata -> doesnt boot and goes back to twrp

raw_img -> boots but wifi doesn't work (wtf?)

now trying sparse_dat......... -> doesnt boot and goes back to twrp

(zip not signed)

I already made a custom rom for myself for this device (older firmware) and everything went good, has anyone had a similar problem ?

Some more details:

-Odexed

-Partitions by system.img (set_metadata doesn't ask for it, i dont know if it is supposed to)

-rooted

-busybox added

-a little of debloat

-latest kitchen version

-latest Ubuntu4Kitchen
[SuperR Kitchen] xNako:
First, thanks for the kitchen !! How to add suhide?
[SuperR Kitchen] SuperR.:
I suggest trying without any modifications and see how it goes. If it boots properly, then start adding mods until you find what is causing the issues. Other than that, I won't be able to help much. Hopefully a Samsung user can help further.

According to [MENTION=631273]Chainfire[/MENTION] in the first post of the suhide thread:

Which means, it should not be flashed with the ROM and will not be added to the kitchen for now.
[SuperR Kitchen] nightcrow:
I'm afraid I can't update the donated version of the kitchen. It tells me there's an update at startup and it seems to install it but the version doesn't change and when I choose the option to update the kitchen the update is there again :confused:

---------- Post added at 04:02 PM ---------- Previous post was at 03:59 PM ----------

What kind of file did you use as a base for the ROM? And did you unpack and repack the boot.img?
[SuperR Kitchen] SuperR.:
You could try manually updating. Open a terminal to the main kitchen directory, and type:

git pull

If that does not work, you can always clone the kitchen again and move your projects to the new one.

edit: git pull will fail if you have modified any files git keeps track of. The updater uses git pull so that may be why the update is failing.
[SuperR Kitchen] xNako:
Wrong post.
[SuperR Kitchen] lugiank:
I tried doing nothing at all and doesnt boot.

Stock unbranded italian zip, latest version

Yesterday i didn't touched boot.img, but today i tried and failed:

I tried set_metadata + unpack boot and set dm-verity off, and both repack boot img methods give a boot to twrp

i'm now trying raw_img permissions

EDIT: I pinpointed the problem to be related to boot partition: if i restore the boot from an older twrp backup it boots
[SuperR Kitchen] allurba:
gitlab.com

user: allurba

3Y336378LW5635929
[SuperR Kitchen] devilmaycry2020:
Hi all

I'm on standard v1.0.8.8 then i've tried to upgrade to 1.1.0.5 successfull but the program still show 1.0.8.8. I've tried to reboot the linux machine then upgrade again but the program still on 1.0.8.8. Please help. how can i reinstall new superr-kitchen ?
[SuperR Kitchen] raheelkhattal:
Delete the existing kitchen files. Then git pull the new kitchen files :good:
[SuperR Kitchen] allurba:
Hello, I have the donate version if I press the option "Build full ROM Zip" I get this error:

MISSING FILES:

Make sure you have system, META-INF, and boot.img in Stock_b390

in the standard version works for me.
[SuperR Kitchen] SuperR.:
Just reinstall. The first post has instructions.

Do you have at least system, META-INF, and boot.img in Stock_b390?
[SuperR Kitchen] allurba:
Yes

Enviado desde mi HUAWEI RIO-L01 mediante Tapatalk

---------- Post added at 08:12 PM ---------- Previous post was at 08:07 PM ----------

Enviado desde mi HUAWEI RIO-L01 mediante Tapatalk
[SuperR Kitchen] allurba:
Already solved, missing me system.ext4..win001

Sorry.
[SuperR Kitchen] KaMyKaSii:
Hello. I am suffering with bootloop to deodex one marshamallow rom and want to take some questions:

1. Any changes to deodex is made only in "/system". Nothing in boot.img, right?

2. After deodex, create system_new.img, install on device, wipe dalvik cache/cache, still i need to wipe data? Because I realized the existence of "/data/app/packagename/oat/arm64/packagename.odex"
[SuperR Kitchen] scrappy610:
Yes you have to wipe data in order to remove remnants of the previously installed rom. Usually you would wipe before installing the rom that way its like a fresh device.
[SuperR Kitchen] KaMyKaSii:
So do not wipe data may be the cause of bootloop? If so, I will return to functional odexed rom, backing up my apps with Titanium Backup, reinstall deodexed system_new.img and boot to Android. After setting all, I can restore my apps normally, right?
[SuperR Kitchen] matamata15c:
[MENTION=5787964]SuperR.[/MENTION] Hello I have the latest version of the kitchen (Free version for the moment) but I have a question I should add here to advance the .zip file to create the custom ROM? PS: My device is a processor with P8 Lite Kirin Thanks

Enviado desde mi hi6210sft mediante Tapatalk
[SuperR Kitchen] scrappy610:
It could be the cause. Its worth trying. It has caused bootloops for me in the past. It could be an issue with deodexing too. Have you tried just building the functional odexed rom and seeing if it boots first?

If you restore your apps i wouldnt restore the data, just the apps. I personally have never had good luck with restoring data from titanium backup, so i no longer use it. Hopefully someone else can chime in and help.
[SuperR Kitchen] bcrichster:
Same here with Titanium Backup. [MENTION=5787964]SuperR.[/MENTION] has pointed me to Nandroid Manager (I use & recommend Pro) and it's a damn versatile blessing for restoring anything.

https://play.google.com/store/apps/details?id=com.h3r3t1c.bkrestore

Sent from CM12.1 *N9515*
[SuperR Kitchen] KaMyKaSii:
I also always had trouble restore only apps data of nandroid backups, then restored my rom and made the conventional backup. Then I came back in recovery, I wipe data/dalvik cache/cache, installed system_new.img and restarted. Unfortunately, bootloop. I tested all three methods of deodex: oat2dex, smali and oatdump. No work, although not logged errors during the process. It is a known problem can not deodex mtk Marshmallow roms?

If someone is willing to take a look at rom, I can up
[SuperR Kitchen] scrappy610:
Pm me the link ill take a look. What recovery and device?
[SuperR Kitchen] KaMyKaSii:
I'm uploading, as my internet is slow, it will take +/- 3h :crying:

My device is a Quantum GO 4G, a national version of Infinix Zero 2 LTE. And TWRP 3.0.2, but as my device has no source released (aka MTK devices), I am using an unofficial port

When upload is finished, I'll edit my post and add the link
[SuperR Kitchen] scrappy610:
Ok sounds good. Ill take a look.
[SuperR Kitchen] devilmaycry2020:
How to delete existed kitchen files ?
[SuperR Kitchen] SuperR.:
You should get by-name from the boot.img if possible. If not, try using the adb shell method. If not, send me your boot.img so I can see what is going on. Entering it manually is the last resort.

Clone the kitchen again and move your projects from the old to the new.

If you are using Ubuntu4Kitchen, rename the old kitchen to /home/username/android/superrs_kitchen_old, and run the script on the desktop. Then move the project files from /home/username/android/superrs_kitchen_old into /home/username/android/superrs_kitchen and delete /home/username/android/superrs_kitchen_old.