yashsingh1/xdaforums huggingface dataset:
[SuperR Kitchen] SuperR.:
v0.9.8.3

Changes:

If rom is already deodexed, you will not be allowed in to the deodex script.

More fixes to the kitchen updater.
[SuperR Kitchen] bcrichster:
Question for you Samsung guys, I deodexed a (Note3) system.img/ROM for someone and need to know if I'm supposed to deodex all the images (data, cache, hidden, vendor) or can I get away with just the system.img? Next Q: can't just the system and boot be made into a TWRP flashable without other stuff or should I try to repack as an Odin deal + if it needs Odin, will the deodexed/deKnoxed system.img cause a conflict with everything else? I'm doing this for someone else and want as little chance of messing them up as possible
[SuperR Kitchen] :
Don't know what you "need" but I always extract boot, system, cache and hidden. I deodex the full rom and usually use meta rather than sparse but both work. Try not to repack anything to a odin file unless absolutely necessary
[SuperR Kitchen] bcrichster:
That's EXACTLY what I needed to know. Ty- Sir!
[SuperR Kitchen] Androidwizzard:
I personally never include hidden except when I am asked for a special "carrier" rom. Providers often put their stuff in hidden.img
[SuperR Kitchen] SpasilliumNexus:
I've been using that method on Moto X Pure Edition and its been working flawlessly with the way I have it set up during ROM flashing.

What I do is place a file named "systemless" in the supersu folder of the kitchen, and inside of that file is "SYSTEMLESS=true" per Chainfire's instruction.

In updater-script, I've changed it so that file is copied to /data on my phone (can also be placed in /system if desired) and renamed as ".supersu", before SuperSU is flashed.

I'm not sure if changing "SYSTEMLESS=true" to "false" will force it to system install as I haven't tried it, but my guess would be that it would.

ui_print("-Installing SuperSU 2.65 beta (Systemless)");
run_program("/sbin/busybox", "mount", "/data");
package_extract_dir("supersu", "/tmp/supersu");
run_program("/sbin/busybox", "cp", "/tmp/supersu/systemless", "/data/.supersu");
set_metadata("/data/.supersu", "uid", 0, "gid", 0, "mode", 0666, "capabilities", 0x0, "selabel", "u:object_r:system_data_file:s0");
run_program("/sbin/busybox", "unzip", "/tmp/supersu/update-beta-supersu-2.65.zip", "META-INF/com/google/android/*", "-d", "/tmp/supersu");
run_program("/sbin/busybox", "sh", "/tmp/supersu/META-INF/com/google/android/update-binary", "dummy", "1", "/tmp/supersu/update-beta-supersu-2.65.zip");
[SuperR Kitchen] jugih:
I think there is something wrong with deodexing samsung A5 files (lollipop [5.0.2]).

I might be wrong and investigations are underway, but something to do with /system/app/samsungIME and its lib that belongs to /system/lib (libswiftkeysdk-java.so)

Also I get force close with /system/priv-app/SamsungLinkPlatform, so it must be deleted for ROM to work.

I'll gather up files and update more specific info on this, nut THANKS for this SUPERRRR kitchen :)

[edit]

ROM is built from system.img and boot.img

If I try to include cache.img, I get error during extraction something like "invalid location for output file.. etc"

Do I need cache.img for samsung non-branded ROM?
[SuperR Kitchen] jazzespresso:
my devices are Samsung, so I never include cache.img nor data.img nor hidden.img, I usually include system.img, boot.img, recovery.img in my working Supperr Kitchen's ROM folder.

Of course, some samsung phones that after extract firmware odin tar file, there's also modem included (this is usually the case for USA base firmwares, ATT, Verizon, etc..)

I am not sure about modem file, so I like to refer to [MENTION=1162986]Captain_Throwback[/MENTION] and others here to make some clarifications.
[SuperR Kitchen] Captain_Throwback:
[MENTION=5787964]SuperR.[/MENTION]

FYI (RE: Updated Busybox Installer)

---------- Post added at 10:06 AM ---------- Previous post was at 09:44 AM ----------

[MENTION=5787964]SuperR.[/MENTION]

There's an issue with the dm-verity/forceencrypt patcher, which is an issue I also had with SuperSU when it started incorporating a patcher into the zip. I'm not sure how the kitchen determines what file to patch, but in my ramdisk, I have 4 files with fstab in the name: fstab.goldfish (which is old and pointless), fstab.htc_hiae (this file is a symlink to the real fstab), fstab.qcom (this is the real fstab) & fstab.ranchu (another useless one). The kitchen is overwriting the symlink as a real file somehow, and not touching the real fstab. Is there a way to have the kitchen ignore the symlink when patching, so that the correct file gets patched?

P.S. I just tried packing the boot.img and deleting the ramdisk, and it keeps it instead - is that a bug?

P.P.S. The above issue only seems to happen if I first repack and choose to keep the ramdisk. After that, if I make another change to it and choose to delete it on repack, it keeps it anyway.
[SuperR Kitchen] Captain_Throwback:
Hope you didn't miss my PS's on my previous post. Requested files attached.
[SuperR Kitchen] SuperR.:
v0.9.8.4

Changes:

Fixed fstab not being detected properly when there is an fstab symlink.

Updated Busybox installer by [MENTION=4544860]osm0sis[/MENTION].

Fixed repack ramdisk not deleting if keep was chosen previously.
[SuperR Kitchen] Captain_Throwback:
[IMG="@SuperR."]http://treasure.diylol.com/uploads/post/image/542029/resized_the-most-interesting-man-in-the-world-meme-generator-you-sir-are-a-gentleman-and-a-scholar-637218.jpg[/IMG]
[SuperR Kitchen] jimsmith80:
Outstanding work as always SuperR. Your kitchen handles boot.img edits nicely
[SuperR Kitchen] bdorr1105:
This looks really awesome, even though I am 100 percent cluelessm I am kinda of understanding, but the steps to create a full ROM, I have no idea if I am doing it right, I put existing ROM zips in there, trying to get all the ROM images, if anyone has a video or the time to help out, I would appreciate it, just not sure how to know if you are building correctly.

OP, this thing is awesome, great work
[SuperR Kitchen] goodman_east:
I downloaded your roms(HIAE_UL_ATT_1.27.502.5_ROOTED_CPTB-deodex.zip and HIAE_DEV_EDITION_1.55.617.4_ROOTED_CPTB-deodex.zip), and tested on my htc a9.

the first one got stuck and cannot boot into system. the second one turned out normally, but the battery percent shows 3705%.

can you help me?
[SuperR Kitchen] Captain_Throwback:
Not sure what you want me to do. All I did was run the ROM through the kitchen.
[SuperR Kitchen] goodman_east:
all the two deodex roms have problems. have you tested on HTC A9?
[SuperR Kitchen] bdorr1105:
When you build ROM zip, does it take like 30 seconds? Do you have to drag the system folder into the zip? Not sure what I am doing wrong, everything extracts, but when I hit option one to build ROM, it takes no time at all, I guess I am confused
[SuperR Kitchen] sun_dream:
我只提示:目前没有工具能够合并出正常的A9 6.0 framework service& wifi service,(你只能合成一个错误无法启动的dex,因为有大量的代码丢失被替换为nop).

而A9 6.0.1的service可以通过，但是Wi-Fi service依然会有部分nop.虽然我没有a9，但我很早之前就知道这一点。因为我在 A9 port to M8的时候已经遇到这个问题，我只有重写全部的丢失smali才让系统开机。

All tools not compatible a9 (6.0 in particular)
[SuperR Kitchen] Captain_Throwback:
I only confirmed that the ROM booted and that all the apps worked. It's possible your issue is related to firmware and has nothing to do with the ROM. Again, there really isn't anything else I can do.

---------- Post added at 10:33 PM ---------- Previous post was at 10:30 PM ----------

I extract full images and build the ROM with the kitchen. The ROMs build fine.

Then why does the deodexed ROM boot and function on my (and other's) A9?
[SuperR Kitchen] bdorr1105:
OK, So I extract the whole system.img as well, then when I hit build, the zip is like 45 MB/s even though the whole system folder is sitting there and it doesn't include it in the zip. So Not sure why that is occurring, I have a LG V10. I can tell you exactly the buttons I hit or make a video and you can tell me what I am doing wrong if you are up to it, makes no sense to me
[SuperR Kitchen] goodman_east:
battery percent is incorect.

wifi cannot work, so does mobile data
[SuperR Kitchen] sun_dream:
Only boot for 6.0.1 dex(not with 6.0)
[SuperR Kitchen] Captain_Throwback:
This will be my last post on this. I don't know what to tell you. WiFi works fine on mine. I don't recall any issue with battery. Ask one of the users in the A9 forum that's using it. I don't think we need to derail this thread.
[SuperR Kitchen] bdorr1105:
Thank you for the reference but that doesn't make sense. I used the same img through the whole process and auto detect worked, it said it worked so I guess I don't get it.

Edit... I don't understand the tool guess that is half the battle. You really don't get any confirmation you are doing it right... I used adb to auto detect which was recommended and it worked according to the tool... I used a Deodexed ROM zip and extracted that. As I am going through I have no way to know what is working.
[SuperR Kitchen] SuperR.:
v1.0.0.0

Changes:

Absolutely nothing useful :p

Changed to v1.0.0.0 to bring in the new year.

Happy New Year!
[SuperR Kitchen] glennsamuel32:
LOL :good:

Wish you the same :p
[SuperR Kitchen] enotar:
Thank you SuperR for new version. 0.9.8.4

I want to report success on this versión root and wifi OK with Samsung SM-P600.......

-deodex

-debloat lightly

-root

Still looking at the Busybox, init.d or deknox that prevent root but this is a big step forward.

I will trigger exactly which one is the guilty one.

Update: definitely no Knox removal or init.d related 2 to go, forgot /data add

Happy New Year
[SuperR Kitchen] bcrichster:
Whoo!! You too!!
[SuperR Kitchen] enotar:
So here it is the guilty one for unrooted rom is adding /data support on Samsung Roms

I attach the 2 updater-script:

-8 is rooted

-9 is not rooted

Except this all is perfect
[SuperR Kitchen] enotar:
Yes that is weird but I tested many times and this is what I get. I will investigate further.

Thank you
[SuperR Kitchen] Captain_Throwback:
I know before we had talked about not formatting /data when adding data/app support - did you ever add that option? In TWRP, unmounting and formatting data will leave it in an unstable state (TWRP leaves it to Android to initialize the partition), which might explain why root doesn't work, since SuperSU needs to install files to /data for everything to work. In TWRP, when /data is formatted, it recommends to reboot recovery so that emulated storage can be remounted, etc.

Formatting /data causes more problems than it fixes, from what I can see.

[MENTION=2682152]enotar[/MENTION]

Try removing the line that formats /data from the script and wipe it manually in TWRP prior to flashing and see if that works.
[SuperR Kitchen] enotar:
I will try and report tomorrow.
[SuperR Kitchen] SuperR.:
I removed /data format a while back and it is not in the updater-script he is using so that is not the issue.

v1.0.0.1

Changes:

Fixed extract data and data metadata not being added to the updater-script.

Fixed user data not showing as enabled.

Removed holiday greeting
[SuperR Kitchen] Captain_Throwback:
It's in the one he attached :confused:

format("ext4", "EMMC", "/dev/block/mmcblk0p21", "0", "/data");

(the one he said where root wasn't working)
[SuperR Kitchen] SuperR.:
You are correct, my bad. He must be using an old version of the kitchen then because that has been removed.

[MENTION=2682152]enotar[/MENTION] - It is possible now that I fixed the user data stuff you will need to remove and re-add user data support. The data format may be leftover from a previous kitchen version.
[SuperR Kitchen] enotar:
I will clean install 1.0.0.1 and start fresh to make sure no left over and report
[SuperR Kitchen] pikachukaki:
Can someone help me with this??

superr: line 2854: java: command not found

When im trying to deodex a MM rom!!
[SuperR Kitchen] pikachukaki:
Yeah I figure it out... Lol

Also something else.. It detects my phone as g3 but it need to be d855 if i change this it ask me then to type me devices arch whatever i type it didn't take it a correct...

and also this

UNEXPECTED TOP-LEVEL EXCEPTION:
java.lang.RuntimeException: Cannot find file or directory "/home/pikachukaki/Downloads/SuperRs_Kitchen_v1.0.0.1/superr_MM/system/framework/oat/arm/smali"
at org.jf.smali.main.main(main.java:202)
[SuperR Kitchen] enotar:
Fresh bake with 1.0.0.1.

At the end of flash process "Unable to mount /data"

Rom is not rooted........

I post the updater-script
[SuperR Kitchen] SuperR.:
Not sure where you are changing the name but I suggest you change it back. I assume you mean you need it to be d855 when you flash because that is what the recovery says your device is and you get a flashing error otherwise. As I have explained many times and as it is written in the troubleshooting post #4, just add the assert you need using the asserts menu under ROM Tools.

This could be your java version or it could be something in the rom smali/baksmali doesn't like. There is nothing I can do about the latter.
[SuperR Kitchen] Captain_Throwback:
Try removing the unmount and mount /data lines.

EDIT: Wait, there still a format /data line in there. [MENTION=5787964]SuperR.[/MENTION]?
[SuperR Kitchen] pikachukaki:
ok i will leave it as g3 and change it later...

the error is occuring when trying to deodex my rom newest MM LG rom the sure think is that the rom didnt have any backsmali file inside any oat folder...just *.odex
[SuperR Kitchen] enotar:
Just saw that.....

This is definitely not a leftover and I tried removing mount and unmount, no change (no root) except now Apps set prior to flash in /data are not installed anymore.
[SuperR Kitchen] Captain_Throwback:
Did you at least try flashing without that line to see if you have root?
[SuperR Kitchen] SuperR.:
This will fix the problem. Thanks [MENTION=1162986]Captain_Throwback[/MENTION] and [MENTION=2682152]enotar[/MENTION] for helping to squash another bug :)

v1.0.0.2

Changes:

Added option to check for kitchen updates every time the kitchen starts.

Fixed data format happening when the device uses mmcblk.

NOTE: To enable the auto update check, go to "Check for updates" in the main menu. After it checks, you will be asked if you want to enable it. If you change your mind later, you can navigate to the /kitchen/tools directory and rename the updatecheck-yes or updatecheck-no files accordingly. Alternatively, you can delete the updatecheck-yes/no file and you will be asked again next time you check for updates.
[SuperR Kitchen] enotar:
Was working on it

Root is fine without that line

Thanks for 1.0.0.2, will try right away

Update: GOOD NOW, all working Thank you, great job.
[SuperR Kitchen] sebastiandg7:
Thank you for the improvements!!!!! Do not forget to update the Thread title according to the latest kitchen version.
[SuperR Kitchen] F_R_I_T_Z:
mount("ext4", "EMMC", "/dev/block/mmcblk0p21", "/data", "/data", "");

Something is wrong here no?
[SuperR Kitchen] SuperR.:
Yes, something is wrong. I am not able to reproduce it, but you could try removing user app support and re-adding it.

It should be

mount("ext4", "EMMC", "/dev/block/mmcblk0p21", "/data", "");
[SuperR Kitchen] bdorr1105:
Where do you guys see this at, how can I get myself spun up better so I can ask more intelligent questions as well as learn how to do this. Thanks
[SuperR Kitchen] :
In the updater script in the met-inf folder. There's a thread somewhere on xda that explains the updater script I'll try and find it
[SuperR Kitchen] sebastiandg7:
Problem in v1.0.0.2

Cannot extract any ROM zip for a new project.

When I select option 4) to extract a rom zip it goes to a new menu with two options:

1) To extract rom zip, system.img... bla bla bla

2) To extract via adb and root from current rom in device.

When I press 1 it does nothing. [MENTION=5787964]SuperR.[/MENTION] :D
[SuperR Kitchen] bdorr1105:
Thanks for taking the time
[SuperR Kitchen] :
Here you go, it might help you

http://xdaforums.com/showthread.php?t=2377695

[TUTORIAL] The updater-script completely explained
[SuperR Kitchen] bdorr1105:
I am having the same problem you are, I am going to post screen shots of it for what is happening on my end

Thanks a lot
[SuperR Kitchen] bdorr1105:
I am unable to pull my ROM from my phone. I will explain what I did and attach screen shots

1. Hit 1 to create new project

2. Entered LG_V10_Deodexed for the project name

3. Chose Option #4 to Extract ROM

4. Hit Option #2 to pull it from phone

5. Granted Root Access when prompted

SuperSU gave toast notifications saying it granted root permissions, however it failed to pull. Please see the screen shots. I am using v1.0.0.2
[SuperR Kitchen] SuperR.:
The kitchen uses the only two ways I am aware of to try to grab your system.img from the device. If you figure out how to do that for your device, please let me know and I will update the kitchen. Since I don't have your device, I will not be able to help with this.
[SuperR Kitchen] F_R_I_T_Z:
Yes. After a clean install from the kitchen disapear but now I have another problem

Where is the supersu?

After build the rom and install I cant see it.

We dont need it anymore for busybox?

run_program("/system/xbin/busybox", "--install", "-s", "/system/xbin");
[SuperR Kitchen] bdorr1105:
What or where is the script that does the pull, I want to help if possible, just dont know where to look for the script responsible pulling the system.img
[SuperR Kitchen] sebastiandg7:
I am 100% sure the rom zip is placed in the project folder... What to do?
[SuperR Kitchen] SuperR.:
SuperSU is not installed in the ROM by the kitchen. Instead the kitchen adds the SuperSU flashable zip to your rom and it is flashed when the rom is flashed. Same with Busybox. Both are in their own directories inside your project directory after you add them. No, you don't need the busybox install line.

I am not suggesting you edit the script. I am suggesting that you figure out how to pull a system.img from your device using adb shell and tell me how you did it.

Nothing has changed in a very long time regarding the code responsible for your issue. You must be doing something wrong. I would suggest installing a fresh kitchen, add one project, add your zip to that project, and try to extract. Or, use an older version of the kitchen if you think that works better for you. I am not able to reproduce your issue so I will not be able to help any further. If you figure out the problem and it is something wrong with the kitchen, please let me know.
[SuperR Kitchen] dkionline:
build with root rights and open folder as admin.
[SuperR Kitchen] bdorr1105:
Here is how you get it for the LG_V10

ls -la /dev/block/platform/f9824900.sdhci/by-name/
[SuperR Kitchen] bcrichster:
Might help to "zip all devices" and upload to SuperR so he can add it it and adjust the Kitchen
[SuperR Kitchen] bdorr1105:
Not sure I follow, I am just asking about the LG V10
[SuperR Kitchen] SuperR.:
This command will not pull a system.img from your device. It will only list the by-name directories.
[SuperR Kitchen] bdorr1105:
location

/dev/block/bootdevice/by-name/

/dev/block/mmcblk0p51

to view

ls -la /dev/block/bootdevice/by-name
[SuperR Kitchen] SuperR.:
This command will write a system.img that is on your sdcard to your system partition. The kitchen uses the reverse of this command which pulls a system.img from your device and places it on the sdcard. Please try the commands you are posting before posting. Once you get a system.img pulled to your sdcard, let me know how you did it.

My guess is that the kitchen is doing its job but your sdcard does not have enough room for the img.
[SuperR Kitchen] bdorr1105:
Ok, working it now
[SuperR Kitchen] SuperR.:
v1.0.0.3

Changes:

Creating a new project is now much faster when you have many projects.

Added busybox and vendor directories to the move old rom files list.

We will now use the correct mount command if perm type is raw_img.

Updated SuperSU to v2.66.
[SuperR Kitchen] bdorr1105:
These Commands Both Worked

dd if=/dev/block/mmcblk0p51 of=/sdcard/system.img

or

dd if=/dev/block/bootdevice/by-name/system of=sdcard/system.img
[SuperR Kitchen] SuperR.:
Check the device superr_byname file in the kitchen. It is located in /kitchen/tools/devices/devicename/superr_byname

If it is different than the block in both of the commands above, that may be the issue but maybe not. Many devices have 2 ways of using by-name. The second one you posted is the newer of them and is normally a symlink to the main one which in your case is probably /dev/block/platform/f9824900.sdhci/by-name. The kitchen uses the exact same command as you posted and uses whatever is in the superr_byname file as the block device. So, if you can do it manually it should work in the kitchen unless the superr_byname file contains the wrong info.
[SuperR Kitchen] bdorr1105:
Ok thanks for the assistance, I will let you know know how it works out. Thanks

---------- Post added at 10:42 PM ---------- Previous post was at 09:43 PM ----------

If you added it, I do not see the device name that contains the superr_byname....what did you name the device?

pplus? Think I found it
[SuperR Kitchen] Leavard:
On my LG G4, the phone needs to be in download mode in order to pull or push a system image. Are you in download mode or booted up normally?
[SuperR Kitchen] bdorr1105:
I can do it form recovery with adb shell
[SuperR Kitchen] bdorr1105:
Deleted
[SuperR Kitchen] jugih:
Is this kitchen supposed to be able to extract /system from Samsung's system.img.ext4 image?

For me it doesn't work and I have to manually convert system.img.ext4 with simg2img.

Thanks
[SuperR Kitchen] :
If I download a Samsung 5.1.1 firmware then drop all the .img files in the kitchen it works fine. Might be worth renaming the system.imgext4 to just system.img
[SuperR Kitchen] jugih:
I believe it doesn't work, by just simply renaming it. FW is 5.0.2 from Samsung Galaxy A5.

[EDIT] sorry, now it works just renaming it! I swear it didn't work couple versions earlier :D
[SuperR Kitchen] Macguyver1980:
Yet issues...

I tried last version and not yet working, files yet created with information as file corrupted created and seems the applications added not working and properly created. Tried metadata method and Sparse one...
[SuperR Kitchen] albertmurcia:
a guide of cooking kernel?

Enviado desde mi SM-T805 mediante Tapatalk
[SuperR Kitchen] Rydah:
Here's the script. Fixes are in the #PERMS area. Thanks bro!!!

http://pastebin.com/0GjV8Sim
[SuperR Kitchen] Macguyver1980:
I did more tests. Once I want to add the applications support it creates a corrupted file (from phone view) if it's with metadata method and doesn't even seems to see any application neither include them in the Parsing method. It's on Lollipod ROM for my Ulefone from original files and system one. I checked about the access property to files, not coming from this. I'm working under Linux Ubuntu 14.04.
[SuperR Kitchen] SuperR.:
This may have already been fixed because I don't see any metadata entries in your updater-script that are not already in the metadata database.

I have no idea what is going wrong. Make sure your directory structure is correct in your project /data directory. Also make sure any libs that need to be included with the apps are there and in the correct place. Other than that, if you figure out the problem let me know and I will update the kitchen.
[SuperR Kitchen] Rydah:
Really? Specifically the permissions that are set and the owner of some.

Sent From My LG V10
[SuperR Kitchen] SuperR.:
Yes, all the permissions and file owners are the same as in the database and the contexts come from the boot.img which will be correct. Try again and let me know how it goes. If it still has issues, send me the kitchen generated updater-script.
[SuperR Kitchen] Rydah:
Will do, thanks. I will say though, for some reason it didn't add the correct contexts to begin with, but I will try again soon. Thanks again!

Sent From My LG V10
[SuperR Kitchen] SuperR.:
v1.0.0.4

Changes:

Added option to pull images while booted in custom recovery.

Added a check for available space on device before pulling images through adb when booted in Android.

Fixed harmless but ugly errors when finding device name.

Added k3g device to repo.

[MENTION=1195110]bdorr1105[/MENTION] - Give the new version a try and do the img extract from recovery :)