yashsingh1/xdaforums huggingface dataset:
[SuperR Kitchen] lost101:
Updating within Kitchen deletes 'superr' - I had to manually install the Kitchen again.
[SuperR Kitchen] SuperR.:
Did you git clone or download the zip and extract?

edit: never mind, found the problem :)
[SuperR Kitchen] Fuze310:
I own a Lg Ttibute 2 and im new to the rooting World i accidently flashed my recovery and bootloader every time i power it on its stuck on a bootloop when i try to set it in recovery it says error 1003 i need help please
[SuperR Kitchen] bcrichster:
Don't take this the wrong way, but this isn't the thread for that kind of problem. This is a "Kitchen" for Android Development, not a "fix my boo-boo" support line. Go to the LG Tribute 2 forums and see if they can help. [emoji41]

Sent from my Gummy N9515
[SuperR Kitchen] SuperR.:
Fixed the harmless but ugly errors :)

The update below should sort you out :)

The update below fixes the updater issue. You will still need to manually download this one but future updates will work as expected :)

v1.0.3.0

Changes:

Fixed kitchen updater.

Added option to use the M deodex method from v1.0.2.6 by adding an empty file named deodex_m2 in the 00_project_files directory.

Fixed more harmless but ugly errors.

NOTE: If you want to use the deodex method from v1.0.2.6, simply add an empty file "deodex_m2" as shown below:

/kitchen/superr_project/00_project_files/deodex_m2

You can create an empty file using your file manager and name it deodex_m2, or you can do the following in a terminal:

cd /kitchen/superr_project/00_project_files/
touch deodex_m2

[B][COLOR="Red"]OR[/COLOR][/B]

touch /kitchen/superr_project/00_project_files/deodex_m2

Of course you will need to replace "/kitchen/superr_project" with the actual path to the project you are adding the file to.

You will need to add this file to every project you want to use the older method for. If you want to go back to the newer method, delete the file you just added :)

edit: I added this info to post #4 for future reference
[SuperR Kitchen] Er. Aditya:
started having this strange issue with latest kitchen 1.0.3.0

note 4

5.1.1

find: `./output/lost+found': Permission denied
[SuperR Kitchen] SuperR.:
It is harmless but if you tell me when it happens I will fix it.
[SuperR Kitchen] Er. Aditya:
first when i extract cache.img and after that when i deodex bro
[SuperR Kitchen] Androidwizzard:
This folder is always empty - no content from my experience since KK times, that might be the reason for this error - just in case it matters.
[SuperR Kitchen] JochenP:
it works and generated without error a running ROM for A9 :good:

please add (at row 3239) if deodex_m2 resides for better user control something like:

read -n 1 -p "Would you like to continue deodexing 3 (deodex_m2)? y/n "
[SuperR Kitchen] Er. Aditya:
i dont think latest kitchen extracted my cache.img properly
[SuperR Kitchen] SuperR.:
I have made some changes already. I am getting rid of the file adding and asking which method to use each time when deodexing M roms. I think the file adding is too complicated. Was tired when I did it lol

This has not changed in a long time so it must be something different with the cache.img you are using. Different firmware maybe? If so, please send a link so I can have a look.

The easiest way is to grab the info from a device tree for your device if it exists as someone else has already figured it out. If not, I am sure there are guides that explain how to do it. If you figure out how to do it using adb shell, please post the method and I will add it to the kitchen if it is different than what it already does.
[SuperR Kitchen] JochenP:
:highfive: haha - no, it is not too complicated - only i miss feedback if it goes the right direction :D

I'm tired of saying thank you :laugh:
[SuperR Kitchen] SuperR.:
Assuming that is the BoardConfig.mk for your device, yes. Manually enter the number next to BOARD_SYSTEMIMAGE_PARTITION_SIZE in the kitchen when you build the rom.
[SuperR Kitchen] Darkapolo:
Hi SuperR. Thanks for your great work. Is possible to set an specific name to rom. For example : "X ROM built with SuperR kitchen", not only built with SuperR kitchen. So, if we make a nandroid backup, and let the automatic name, we can identify different ROMS backups. Thanks again.

Enviado desde mi Aquaris M5 mediante Tapatalk
[SuperR Kitchen] bcrichster:
Just make a new project folder with a different name [emoji6]

Sent from my Gummy N9515
[SuperR Kitchen] JochenP:
A question about partitions info: should i not be prompted for partitions info every time after unpacking for a new rom?

Kitchen asks only one time after starting from a fresh extracted copy of kitchen.

Sometimes after 'deleting' a project there resides some root files and kitchen cannot delete truely this project. (cannot reproduce this - something fails)

EDIT: ramdisk/res and ramdisk/sbin
[SuperR Kitchen] SuperR.:
It should only ask you once until you delete the kitchen and start over. The device info is stored in /kitchen/tools/devices. The recently fixed kitchen updater performs the update and preserves the devices you have stored locally.

This will be fixed in the next version. Thanks for pointing it out :)

Do you get any errors on your screen? You can always scroll up in the terminal to see all the previous screens and any errors that may have occured. If you see an error it would be helpful to know what it said right before the error as well as the error itself. Thanks

edit: Is it possible your zip would be larger than 4GB? As far as I know 4GB is the maximum size for a zip file.
[SuperR Kitchen] jivany:
Guys my terminal keep asking for binaries. I dl them were do i extract them into what folder .........edit; nvrmind im a jackass i installed 32bit time to start from scratch this time with a 64 bit lol
[SuperR Kitchen] SuperR.:
v1.0.3.1

Changes:

Added a choice when deodexing M roms and eliminated the empty file addition.

Fixed a few more potential harmless but ugly errors.

Fixed projects not deleting if M bootimg or recoveryimg directory exists.

Fixed ugly text layout if you say no to trying to sign after ram warning.

NOTE: If deodexing M, you will be given two choices - oat2dex or smali/baksmali. smali/baksmali is the method used in v1.0.2.6 and earlier. oat2dex is the method used in v1.0.2.7 and later. If one of the methods causes problems, try the other.

HINT: it seems like Samsung roms like the oat2dex method so far.
[SuperR Kitchen] bcrichster:
Will there possibly be another deodex choice (Plz?) for KK since the very early kitchens done KK ROMs just fine and seems the newer versions are jacked when dealing with KK or did you get that squared away?

Sent from my Gummy N9515
[SuperR Kitchen] SuperR.:
I was not aware KK deodexing is broken. Just deodexed the Warp 4G 4.4.2 with no errors and everything seems correct. What exactly is going wrong? Can you send a link to the problem firmware?

The only thing I can think of that would be different from earlier kitchen versions is the version of smali/baksmali. You can replace the ones that are currently in the kitchen with any version you want as long as the file name is the same format as the ones in the tools directory.

Example:

The kitchen currently has the following file

/kitchen/tools/baksmali-2.1.1-b12d4e9e.jar

You can replace the file above with any version of baksmali. Any of the following file names will work fine

/kitchen/tools/baksmali-2.0.8.jar
/kitchen/tools/baksmali-2.0.8-blah-blah-blah.jar
/kitchen/tools/baksmali.jar
/kitchen/tools/baksmali-randomtext.jar

As you can see, the only important part is that "baksmali" be the first part of the file name. Replace smali with the same version as baksmali and try the deodexing again.

edit: Oh, and make sure you delete or move the original files out of the tools directory to be sure the new ones are used.

edit2: I should also mention that older versions of smali/baksmali will not support M deodexing. It may have unexpected results if you try to deodex M roms while the older versions are there. You have been warned :)
[SuperR Kitchen] bcrichster:
Ty- Sir. I had the issue with my Warp Sync ROM (unmodified) 4.4.2, Kitchen v9.6.6, mentioned it & gave link to full backup in our "Kitchens" PM starting about post #1250 or so. Sadly had to break out bongofwars kitchen to do that deodex Job. SuperR Kitchen deodexed without errors but refused to boot while bongs was 100% (somehow). If you still need that link I'll repost it. I believe I mentioned it another time but ppl gimme sh!t about working with an old KK OS when LP & MM was the "in thing" at the moment so that KK wasn't really important for anyone anymore cuz ur kitchen was geared towards LP+, making JB/KK obsolete. Was just hoping you (by now) possibly had insight or was gonna add an "obsolete" deodexing option for us messing with 4.1.2 - 4.4..?? [emoji28]

Sent from my Gummy N9515
[SuperR Kitchen] SuperR.:
My only suggestion is as above. Try an older version of smali/baksmali. Just remember to use the newer versions if you need to deodex M roms.

Here are the smali/baksmali downloads. I would try 2.0.6 and 2.0.8 and see how it goes.
[SuperR Kitchen] bcrichster:
Ty- Sir. No way to make a smali/backsmali Automatic switcher option based on OS? I ask because I'm sure I'm not the only one using KK and under..?? Lol. [emoji89]

Sent from my Gummy N9515
[SuperR Kitchen] SuperR.:
I could easily do it, but the kitchen would grow by a couple MB. Not sure if that is a big deal. Let me know which one works and we can decide from there :)
[SuperR Kitchen] bcrichster:
Ty- Sir, I'll check bong's tomorrow and let ya know which it is that worked

Sent from my Gummy N9515
[SuperR Kitchen] SuperR.:
It would be the best if you try swapping the jar files downloaded from smali downloads in this kitchen, deodex, build rom, flash and test to be sure everything works and the problem is solved.

The oldest kitchen version I still have is v0.9.1.6 and it uses smali/baksmali 2.1.0. Hope that helps.

edit: just looked back at the commits and the first smali/baksmali I used in the kitchen was 2.0.6

edit2: bong kitchen used 2.0.6
[SuperR Kitchen] asc1977:
[MENTION=5787964]SuperR.[/MENTION]

I tried now many tgings with your tool and other tools to deodex MM Samsung beta but with no sucess on some files. The files deodexed without problems but forceclose in phone. I speak with some devs and they told me that they deodex with sucess and without any problems with the SVA tool V4. I looked in that tool and see its only oat2dex inside. Which oat2dex i dont know. I am not the genius in that. I hope that can help you so solve the problem to deodex MM roms from Samsung. I tgink you only need the right oat2dex version. Please respond to me

Gesendet von meinem SM-G925F mit Tapatalk
[SuperR Kitchen] SuperR.:
Feel free to test the various oat2dex versions. You can use the same method I described a few posts back to replace smali/baksmali.

Short term memory loss? lol

I will change this for next version.

I have no idea what you mean.

I am not responsible for java errors as I did not write java or any of the java apps included with the kitchen. However, I have not gotten those errors. The error says you are running Ubuntu 14.04.3 (Mint is based on Ubuntu). I suggest updating and I also suggest running a native Linux environment. I don't support Windows anything.
[SuperR Kitchen] JochenP:
okay - ./00_project_files/logs/main.log have to be zero byte (empty) if project succeeds - otherwise there must be an error and superr is able to visualize it...

just an idea because my projects has sometimes trouble and flashing rom fails of course :(

(I have no idea why superr generates the temporary output folder locked / LOCK-Symbol sometimes)

Yes - native is better - i will install dualboot...
[SuperR Kitchen] SuperR.:
What you are saying is not true. Many things are logged to main.log, not just errors, so this won't always be a good solution. If you tell me what the errors are when you get them I may be able to fix them.

The kitchen creates the "output" directory when you extract an img file. It shows as locked because it is created as root and you are looking at it as a normal user. It should be deleted when the process is finished, if not I am not sure what is going on.
[SuperR Kitchen] bcrichster:
Right on! Now that you're sure as to which smali/baksmali was used, will you be adding the switch option for us 4.x.x users? PLEEEEEASE?! Lmao [emoji28]

Sent from my Gummy N9515
[SuperR Kitchen] SuperR.:
As soon as you test the kitchen with 2.0.6, and flash/boot the rom successfully, I will add 2.0.6 to the kitchen for deodexing older roms. Just want to be sure that solves the problem before I do it :)
[SuperR Kitchen] SuperR.:
[MENTION=5297774]bcrichster[/MENTION] - nevermind :p

v1.0.3.2

Changes:

Added M deodex method status in Rom Tools menu.

Zipalign now asks if you want to zipalign framework files before doing anything.

Deodexing KK and below will now use smali/baksmali v2.0.6.
[SuperR Kitchen] bcrichster:
OMFG!! [emoji33] You are Tha F'n MANN!! Ty- Sir! The kitchen deodexing is now safe for 4.x.x ROMs again. So SWEET!! [emoji41] Thanks again, [MENTION=5787964]SuperR.[/MENTION]

Sent from my Gummy N9515
[SuperR Kitchen] navcar:
I had a jarfile not found error with v1.0.3.2 when the kitchen was deodexing - I had to change the line:

oat2dex=$(ls $tools/smali/current | grep oat2dex)

to the following:

oat2dex=$tools/smali/current/
oat2dex+=$(ls $tools/smali/current | grep oat2dex)

I'm not sure if it was due to my own linux set up, but this is my first time using this kitchen - great work by the way! :)
[SuperR Kitchen] SuperR.:
Thanks for pointing this out. I changed the location of oat2dex.jar in v1.0.3.2 and forgot all about L deodex lol. Fixed now :)

v1.0.3.3

Changes:

Fixed oat2dex.jar missing when deodexing L.
[SuperR Kitchen] JochenP:
another little bug: debloat flag should be resetted (and corresponding files/folder deleted) if rom is extracted a second time - it stays Debloated an have to be restored manually...

i hope i am right - i's too late in the night :eek:
[SuperR Kitchen] andy_zhang:
Renew fast ！up!

vs985 China user
[SuperR Kitchen] not-i:
Yes that works for N910C

---------- Post added at 08:51 AM ---------- Previous post was at 08:49 AM ----------

Yeah mine won't boot either. This could be the issue as I'm running the same Ubuntu. I'll try your solution thanks
[SuperR Kitchen] nghia0423:
Did you ever get past the T-Mobile splash screen. I can't seem to get past it even though the kitchen succeeded with SM-J700F.

Edit: I am running a debian linux and it has gawk installed, and not mawk, so I don't think that is the problem.
[SuperR Kitchen] SuperR.:
Please provide more information such as Android version, type of perms chosen, etc. Thanks

NOTE: if you are building a Lollipop ROM, I recommend sparse dat.

edit: I also suggest trying to build the zip with an unmodified stock boot.img to be sure something is not going wrong with unpack/repack boot.img
[SuperR Kitchen] frequentc:
Yeah, I also had the same problem even after switching to gawk instead of mawk. The system wouldn't go past the t-mobile logo. I tried with and without deodexing.

I ended up using ArchiKitchen. Everything works except the deodexing on lollipop, so do everything except deodexing. For deodexing, I used SVADeodexerForArt, and it worked fine with lollipop.

Hopefully superR can figure out what was wrong with our devices. It would be nice to have an all-in-one solution and not need multiple programs.

Good luck.

Edit:

When using superr's kitchen, I used sparse dat and the stock kernel.
[SuperR Kitchen] nghia0423:
I was using 5.0 firmware (which is the latest one for our device). I was using sparse dat and the full build option.
[SuperR Kitchen] SuperR.:
Sounds like the problem is in the deodexing. Can you send me /kitchen/tools/logs/main.log after deodexing the rom? Thanks
[SuperR Kitchen] frequentc:
I had the t-mobile logo boot problem both with and without deodexing. I also was using root, deknox, and zipalign. No noticeable error messages on the screen.

This was all with the latest bootloader, modem, and CSC files. TWRP 2.8.7.0 recovery.

Samsung Galaxy Note 3 (N900T)

Stock Lollipop 5.0 (N900TUVUFOB6)

Edit: btw.. the phone was very hot while it was at the t-mobile logo, so it was definitely doing something, but I let it sit for like 45 minutes.
[SuperR Kitchen] SuperR.:
Did you unpack/repack the stock boot.img before building the rom? If not, I am clueless.
[SuperR Kitchen] dkionline:
Take a look in ArchiKitchen's Repo.

Did you implement to unpack repack boot.img with every Rom? Can you Combine Archi's init.d to yours?
[SuperR Kitchen] bcrichster:
Why put Archi's init.d in a kitchen that already has perfect init.d support? It's phenomenal You can also unpack/repack images at will.. Did I miss something?
[SuperR Kitchen] frequentc:
No, I didn't touch the boot.img at all.
[SuperR Kitchen] SuperR.:
Will you send me a link to the ROM that works properly and to the files you are starting with?
[SuperR Kitchen] SuperR.:
This kitchen also sets those things up if you choose set_metadata or set_perm. Sparse dat does not need this as it is all included in the dat.

Thanks for the link to the files. I will take a look
[SuperR Kitchen] :
Does sparse.dat work with twizz roms?
[SuperR Kitchen] SuperR.:
I have no idea. I have never owned a Samsung device so I need a lot of help to get it working if there are special needs for them.

edit: but that is a good point. [MENTION=4710301]frequentc[/MENTION], would you mind building/testing a rom using set_metadata or set_perm?
[SuperR Kitchen] :
I've never seen a twizz rom use that format that's why I asked. Every twizz rom I've seen hasn't but it may be because it's new.
[SuperR Kitchen] dkionline:
I use that with my rom, its the best method for all devices.
[SuperR Kitchen] frequentc:
Yes, I'll try to do another build later today.

In case you want it, here's the working rom that was cooked with ArchiKitchen (deodexed, rooted, deknoxed):

http://xdaforums.com/devdb/project/dl/?id=14615

As I mentioned before, the deodexing was done with SVADeodexerForArt, since I don't think ArchiKitchen supports deodexing lollipop.

---------- Post added at 12:15 PM ---------- Previous post was at 12:10 PM ----------

Which method do you use? sparse dat?
[SuperR Kitchen] dkionline:
Set_perm and _set metadata, is better if u want do some changes by yourself.
[SuperR Kitchen] SuperR.:
If you are extracting again, you must be deleting the system directory first. When you do that, delete the 00_project_files directory too. Problem solved :)

edit: unless you are letting the kitchen move the old files. Even so, just delete the 00_project_files directory and you will be "resetting" the project.
[SuperR Kitchen] JochenP:
I'm not able to generate 2 identical ROM.zip

md5sum differs each time -> 2 folder, identical steps, same rom name.

What is the reason for this? Timestamp differs or ... what?

Thank you
[SuperR Kitchen] SuperR.:
Many things could be slightly different, but nothing that will cause problems. If you are truly interested, you could extract both roms that you are comparing and do a diff to see what is not the same.

edit: meld is a nice gui diff application for Linux. It even does directory comparison which would be the easiest way to see all the differences.
[SuperR Kitchen] hardwork07:
Boot loop

After recompiling boot.img from MT6582 v5.02 Lollipop 0S, my phone got stuck on logo even after formatted it twice.
[SuperR Kitchen] störte:
Hello

Compliment to your kitchen. It is straight forward. I just have one Question.

I try to make my first MM ROm for the S6 Edge. When i build it asks for the partition via adb. When i connect my phone (rooted and USB debugging) it is stucked and nothing happen for more than half an hour.

How can i solve the problem please
[SuperR Kitchen] SuperR.:
I have no experience with MTK devices, aside from what the kitchen already supports. It seems it does not support your boot.img. If you figure out how to make it work let me know and I will try to add it to the kitchen if possible.

This question is asked a lot. It would be great if you would help me figure out how to make it work on your device so I can stop getting this question so often. The kitchen uses a pretty standard method to determine this info using adb shell. Here are the steps using the by-name directory for the zerolte (not sure if it is the same as the edge. If not you will need to use the correct by-name directory for your device):

adb shell su -C "ls -al /dev/block/platform/15570000.ufs/by-name" | grep SYSTEM | gawk '{ print $8 }' | cut -d"/" -f4
adb shell "cat /proc/partitions" | grep "output-from-first-command" | gawk '{ print $3 }'
echo $((output-from-second-command * 1024))

Please try this manually and see where the problem occurs. Remember to use the correct by-name directory for your device, and to replace "output-from-first-command" and "output-from-second-command" with the actual output from those commands.

If this method does not work, please try to find one that does and let me know so I can update the kitchen to work with more devices. Thanks.

If you don't want to help, you can always use the enter it manually option and get your system partition size from an s6 edge device tree.
[SuperR Kitchen] störte:
Surely i like to help. I will try as you said.. As far as i know the G925F is zeroltexx

---------- Post added at 19:43 ---------- Previous post was at 18:51 ----------

These are my finding.

First i needed some things to install like adb tools.

After i type the first command you wrote and it says error device offline. USB debugging is on (MTP). So unfortunaetly i cant passed that. Will try some more things
[SuperR Kitchen] SuperR.:
You can first try "adb devices" to see if your device is detected. Once you get passed that part, the kitchen may work for you as it is.
[SuperR Kitchen] störte:
Strangely now it isnt detected. I will research a little to find the solution
[SuperR Kitchen] The Sickness:
Do you have adb installed on your pc??? If its not installed then that error will pop up
[SuperR Kitchen] edzamber:
VirtualBox+Linux mint+adb mate [emoji6]
[SuperR Kitchen] störte:
Yes i have it installed. Sometimes it shows offline and sometimes not detected

---------- Post added at 08:44 ---------- Previous post was at 08:43 ----------

I tried it with Zoran Linux from a Window Pc as Dual boot and as well from a Imac with Parallels Desktop and Linux Mint. Just now i also tried it with Ubuntu via Parallels with same result.

I think that is the reason why my Rom is not booting. I use instead of adb the system.img because i dont know what to enter when using manual
[SuperR Kitchen] JochenP:
VMware desktop also doesn't work errorfree for me (ubuntu, Mint). Oracle VM and Mint works error-free and generated roms are functional.

Parallels i have not tested yet. try Oracle is my tip (on your windows PC)

-instead of adb i use boot.img
[SuperR Kitchen] störte:
Thanks. I will try that. Which boot. img do you use ? The original or the custom ? I try to make it from Korean Firmware (925L) to use on 925F MM
[SuperR Kitchen] JochenP:
i use decrypt RUU By Captain_Throwback for HTC - this tool extracts all files from a flashable file for me, but your device is S6 and i have no idea how that works, sorry.

I think you have no extracted flash-roms and have to pull it from your device instead
[SuperR Kitchen] störte:
I will try now Oracle and Mint-kde. Maybe it works.

Sorry same result.
[SuperR Kitchen] edzamber:
I'm waiting to official MM Rom to do mine for G925F.

What i can say is to do Rom in system.img format and do updater-script manually to mount and extract with devblock.
[SuperR Kitchen] störte:
It will take time i guess. The point is that others made it run so why not me. This is now personal to linux :)
[SuperR Kitchen] pendor24:
Hello

everything works for me

I use the original file of Roma stock , I go up the system and copied the boot img in the working folder . works on 2,3,4 and s5 note. .with linux zorain
[SuperR Kitchen] störte:
Thanks . The bootloader and modded TWRP i have already so that isnt the problem. Anyway i give up for the time being