yashsingh1/xdaforums huggingface dataset:
[SuperR Kitchen] C y a n i d e ~:
What Kitchen version? 0.9.7.8

What Linux are you running? Zorin OS 9 64bit Ubuntu Based

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

What was the source you started from (system.img, system.ext4.tar, rom.zip, etc.) Pulled Out from device using ADB

What Android version? Lollipop 5.1.1

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

What did you do after extracting?

Deodexed, debloated, applied init.d and insecure kernel, added some asserts.

I still don't know why it bootlooped :(
[SuperR Kitchen] C y a n i d e ~:
Ok I'll upload the full firmware now so I can post the link later, Thanks :good:
[SuperR Kitchen] SuperR.:
v0.9.7.9

Changes:

Updated SuperSU to BETA 2.65.

Added space when quiting so the command prompt gets its own line.

Added a few more devices to the device database.

[MENTION=1162986]Captain_Throwback[/MENTION] - I am going to deny your pull request, but I made the changes. The reason I did not accept is there were many places that needed this edit. Thanks for your help to make the kitchen better :)
[SuperR Kitchen] C y a n i d e ~:
Hi, SuperR this is the link for the full Rom zip https://drive.google.com/file/d/0B7cbsEYhU6-cYzYyaFRrOTExODA/view?usp=docslist_api
[SuperR Kitchen] SuperR.:
The only thing I notice is that your rom is using root and busybox from somewhere other than the kitchen. When I extracted I unrooted, and noticed the busybox symlinks were left behind. The version below fixes that.

Here are two things to try:

1. Update to the version below, extract your rom, unroot, re-root, add busybox, build your rom again.

OR

2. Try set_metadata

v0.9.8.0

Changes:

Fixed busybox symlinks not being removed when unrooting.
[SuperR Kitchen] OMJ:
changes between 9.7.8 & 9.8.0 are causing a unbootable ROM (for me anyways)....looks like a issue with selabels, both are set_metadata ROMs...see attachment & compare...I've edited the scripts to just show symlinks & perms.

9.7.8 - ROM boots fine

9.8.0 - ROM fails to boot, returns to recovery

thx
[SuperR Kitchen] SuperR.:
Try going to change perm type, and selecting sparse_dat again. I am not sure how that happened, but I can't seem to reproduce it here.

Sorry about that. I was trying something else and must have missed something in the cleanup. This should fix it again.

v0.9.8.1

Changes:

Reverted accidental changes to file_contexts when using set_metadata
[SuperR Kitchen] Androidwizzard:
FYI: I still find about 15 apps that seem not deodexed correctly without any reason or connection - both app and priv-app

Samsung Galaxy Note 5 N920 - no matter which exact device or firmware

EDIT:

\app

AdvSoundDetector2015

AllShareFileShare

AllShareFileShareServer

AllShareMediaShare

Bluetooth

NfcNci

PacProcessor

Panorama360Viewer_Zero

RootPA

SapaMonitor

SecDict2Noble

SPrintSpoolerLMR1

TuiService

\priv-app

DefaultContainerService

HealthService

OutOfFocusViewer_WQHD_K

SHealth4_3

VirtualTourViewer_WQHD_lightTheme
[SuperR Kitchen] oak:
Superr, I created roms for two devices Nexus 7, and Nexus 6. Both roms were Android 6.0.1. Both roms flashed and work perfectly. When creating the roms, on the Nexus 7, the script asked if I wanted to zip align. When creating the Nexus 6 rom, the script did not ask to zip align. I was just curious why this is. Your input would be appreciated.

I was using 0.9.8.0.

Thanks

On another topic, If anyone has trouble installing the xxd dependency, it can be satisfied by installing vim-common. Fedora repositories do not have xxd.
[SuperR Kitchen] SuperR.:
Is there an error when deodexing? Is there one or more classes.dex inside the apk after deodexing? Is it L or M?

If there is no error and there is a classes.dex inside the apk, then I don't have any suggestions. If there is no error and no classes.dex inside the apk, something is going wrong with the kitchen. If there is an error, you would need to create an issue in smali github for M or smaliex for L.

The Nexus 7 rom must be deodexed and the Nexus 6 rom must not be. The kitchen will only ask if you want to zipalign if the rom is deodexed.
[SuperR Kitchen] jazzespresso:
First, thanks SuperR for this tool!

Second, I am so close to create full blown ROM using totally your Superr Kitchen. I am only having one issue if I make boot.img insecure for root, all works...kernel is insecure, so does SuperSU works fine, etc...but (a big but), WiFi gone, can't turn it on. If I switch to stock boot.img,WiFi works all fine.

any recommendation or suggestions? I am not sure what I missed...I do appricated for any feedback or suggestions.

thanks and HAPPY NEW YEAR!
[SuperR Kitchen] Captain_Throwback:
Have you tried NOT making the boot image insecure with the kitchen and seeing if WiFi works? Because if it does, that means your issue has nothing to do with the kitchen.
[SuperR Kitchen] jazzespresso:
if making boot image insecure, it is almost the same using untouched stock boot image, so when I flashed stock boot.img, it works.

also wasn't it entire idea make it insecure boot image, so that it can be rootable using superSU?

here's high-level steps what I did;

got the firmware sm-p350 samsung galaxy tab A sm-p350 (5.0.2), extracted, droped system.img and boot.img to superr_sm-p350 folder in where my superr kitchen folder is.

extracting system.img, deodexing system all good...then unpack boot.img and then made it insecure, and then re-pack boot.img...and final step added supersu, and creating build ROM zip..

all good, superr kitchen did not throw any error...so I got superr_sm-p350.zip, and flashed....flashed perfectly fine...and then when (during the setup) tried to turn on WiFi, it did not.

I know it has something to do with boot.img....i don't know what...still digging, here's what I am doing; unpacked stock boot.img and then comparing with superr's unpacked boot.img insecure...see anything pops up..
[SuperR Kitchen] Captain_Throwback:
The boot.img being insecure has nothing to do with the ability to root (at least not on any of my devices). But it may have something to do with your Wi-Fi issue. Your issue might be out of the kitchen's control, is my point.
[SuperR Kitchen] jazzespresso:
thanks Captain_Throwback!,You probably right on that. I do believe there's some misconception/misunderstanding on boot.img being insecure so it can be rootable, at least a lot of Samsung ROM threads mentions that, in fact some developers say you need to make kernel to be insecure in order to root it. That's where I am coming from. I have to admit, I truly never understand "how to make kernel, so it can be rootable" concept. In most cases, usually developers post rootable kernel, so we can grab that and use our own ROM, but when device is not wildly popular (or new) and you need to somehow make kernel rootable...

I wish there's some good documentations in XDA. Yes I know there are a few here and there, pretty much spread out..

Again, bunch of thanks Captain_Throwback and very much appreciated for reponds, quite useful.
[SuperR Kitchen] Androidwizzard:
I remember first attempt to root or pre-root 4.4.2 Samsung firmware was to insecure kernel. With new SuperSu it isn't needed any more.
[SuperR Kitchen] jazzespresso:
..had the same issue with Samsung Galaxy Tab SM-P350, so what I did was used SVADeodexerForArtx32/ or Artx64 deodexer tool to deodexed.

basically, I let Superr Kitchen extract firmware system.img, which creates system folder...once it finishes extract, I copied system's app, priv-app, and framework folder from SVADeodexerForArtx32 deodexer tool and then continue build Superr Kitchen ROM options...

some reason i had better success deodexing using SVADeodexerForArtx32

---------- Post added at 05:38 PM ---------- Previous post was at 05:31 PM ----------

in addition abive; deodexing Google Drive causing issue once boots up....so I removed Drive from system\app folder before flashing, in fact even if google apps deodexed fine, I remove the ones that can be downloadable thru Google play,
[SuperR Kitchen] Androidwizzard:
No error and classes.dex included so, I suppose it will work anyway. In those app folders remain empty \lib folders - see in screenshot - deleting them will remove that "graphical glitch"
[SuperR Kitchen] Androidwizzard:
Correct, it just looks kinda strange - as I don't test it practically, I can only trust my eyes ;):highfive::good:
[SuperR Kitchen] Er. Aditya:
just made a fresh rom with latest kitchen dev , but i am facing a wiered issues

if i try ti initiate a shell command and make a directory

mkdir /sdcard/xyz

its not working i dont know what can be the issue just installed fresh rom and nothing else
[SuperR Kitchen] jazzespresso:
Interestingly enough, after I updated from v0.9.7.X to v0.9.8.X version and went thru creating the ROM, when I flashed to my tablet, it gave me update binary error, did not flashed.

switched back to v0.9.7.X, all good...

maybe v0.9.8.X all good other devices, but maybe not so good for Samsung device? just making wild guess...

---------- Post added at 11:05 AM ---------- Previous post was at 11:04 AM ----------

what's that app you using to compare? it looks nice...I am using KDiff3 app
[SuperR Kitchen] Androidwizzard:
It is called "Beyond Compare" an outstanding program :good:

With this one you may find out who is using eg this kitchen or copying other's work ;)
[SuperR Kitchen] :
It's beyond compare, it's available for Linux but I think it's paid. Meld is another good one for Linux as well and is free
[SuperR Kitchen] enotar:
Sorry was away for few days.

The same here, with Sparse, if I try metadata it flash good but Rom is not rooted (I can root after flashing manualy in TWRP last SuoerSu 2.6.5 so new SuperSu is not the issue) and wifi now works but /data dont mount. What I find out is that the updater script is somehow missing info on mounting partitions. Supersu is not extracted or there is no place to extract it. I had some weird message that I have to put the mount partition myself in the updater script, where? All is detected by the unit as this is not working with Recovery.img or Boot.img. I even tried a simple rom with no tweak, just creat the zip from stock, no root.

Definitively not working on Samsung devices.

I tried everything in previous post, went back to previous versions, With previous I have root but no wifi and with new I have wifi but no root. I compare updater scripts and they are small differences but for Root all is the same:

"Here are some things to try assuming you are now using v0.9.7.4 (guessing here since you did not send a new updater-script) Sent previously and you mention nothing was wrong

Change perm type to raw_img, then back to set_metadata and flash again. This will basically delete the old and generate an entirely new updater-script. Same no root

Remove busybox and flash again. Once again, I am still not sure the busybox implementation is good yet and I do not know how it affects root with the new SuperSU. Same no root and the same with 0.9.8.1

Beyond that, I don't even know if the new SuperSU works for your device I can assure you it works as I flash it afterwards and rom is rooted). If not, you can always remove the new SuperSU zip and add the older one if it work better for you. It is located /kitchen/tools/root/supersu. Literally delete the zip that is there and put the one you want in. From the kitchen menu, remove root and add it again Done No root."

I can use the rom and flash after the SuperSu but I think this is not the goal.

I will continue to test but I am out of ideas.

Sorry one more time for the bad news
[SuperR Kitchen] Er. Aditya:
after whole flashing day i have founf busy box was at fault
[SuperR Kitchen] Captain_Throwback:
[MENTION=5787964]SuperR.[/MENTION]

Kitchen Version: 0.9.8.1

I decided to try deodexing a Marshmallow ROM for the first time today, and for the most part, everything went well. The good news is, I was able to get a fully functioning ROM out of the process. The bad news is, it still required some manual intervention due to some errors in the script.

I started out with a fully working ROM folder with an odex system. I chose the option to deodex, which asked me to confirm some parameters, which we all correct. I hit enter to proceed, and saw some progress on the screen. Some of the framework files threw the below error:

UNEXPECTED TOP-LEVEL EXCEPTION:
java.lang.RuntimeException: Cannot find file or directory "/home/throwback/android/SuperRs_Kitchen/superr_HIAE_DEV_EDITION_1.55.617.4/system/framework/oat/arm64/smali"
at org.jf.smali.main.main(main.java:202)

This, however, didn't appear to negatively impact anything, so I guess that part is okay.

The issues began when I went to build the ROM after deodexing. After entering the build menu, I shose the option to build a full ROM (using set_metadata, as sparse_dat gets stuck in recovery during flash on this device), and chose yes to zipalign the APKs, since I'd just deodexed. The ROM build proceeds, but when I look in my updater-script, there are no symlinks. The section looks like the below:

set_progress(0.500000);
ui_print("Creating symlinks...");
ui_print(" ");
#SYM
set_progress(0.600000);
ui_print("Setting Permissions...");
ui_print(" ");
#PERM

If I scroll up in the terminal, while the build is proceeding, I see these errors:

Preparing updater-script ...
cp: cannot stat ‘symlinks.orig’: No such file or directory
grep: symlinks: No such file or directory
grep: symlinks: No such file or directory
sort: cannot read: symlinks: No such file or directory

There were symlinks there previously, as this same folder built a fully functioning odex ROM with no issues. When I look in the "symlinks" file in the project folder, it's blank, when I know there was content there previously. Any idea what happened to the symlinks after deodexing/zipaligning?
[SuperR Kitchen] SuperR.:
Can you expand on this? For example, does everything work properly if you flash the rom that does not include busybox, then flash the busybox installer manually? The new busybox implementation is still largely untested as far as I know. I have not heard any feedback about it and I have not had time to test it properly.

If you did not extract your source files from a system.img, sparse dat image, nandroid backup, or existing rom.zip in the project you are working on, you will not get symlinks. The kitchen does not magically create them, it has to get them from somewhere. If you want to start with already extracted files that already have the symlinks removed, you can copy the symlinks.orig file from the odexed project 00_project_files dir into your deodexed project 00_project_files dir and it will work.

I am not sure why you got the framework errors. Glad it works ok anyway.
[SuperR Kitchen] Captain_Throwback:
I didn't create a new project for the deodexed ROM - I just deodexed the existing project, so I'm not sure what you mean. I didn't delete any symlinks. The symlinks.orig got deleted at some point but I don't know how - I guess that's the issue. Must just be a fluke/freak accident.
[SuperR Kitchen] Er. Aditya:
i am really sorry i was just testing again and not busy box but latest su is at fault , i tried older v 2.52 and everything is fine again

edit : i am still not sure about the latest method of busybox implemntation , i used my old ways to install busybox , not sure if everything will work with the latest methods in this awesome kitchen
[SuperR Kitchen] SuperR.:
Is there a symlinks.orig file in your 00_project_files directory? If so is it blank? The only possible time it could end up blank is if you unroot, and even then it is unlikely. The kitchen does not contain any code that could delete it, other than deleting the project which is clearly not the case here. I have no idea what happened honestly. If you figure out exactly when it happens please let me know.
[SuperR Kitchen] SuperR.:
You can replace the SuperSU.zip in the kitchen with any version you want. It is located in /kitchen/tools/root/supersu. Delete the one that is there and add yours. Then, unroot, re-root and your replacement will be used.
[SuperR Kitchen] Er. Aditya:
yes bro i did that only , making a choice between 2 different su is possible ??

i mean the last stable one by chainfire and systemless root ?
[SuperR Kitchen] Captain_Throwback:
The entire file was missing. I'm going to assume I accidentally deleted it at some point and caused this issue. I've tried to reproduce it but haven't been able to. So I guess we're all good. Kitchen is working flawlessly - I've built fully working ROMs for several devices with it and haven't found any issues since the permissions got worked out. I'm just going to give up on sparse_dat on my 64-bit device for now.

---------- Post added at 02:43 PM ---------- Previous post was at 02:39 PM ----------

One option you could offer is to force system or systemless root, using the flag [MENTION=631273]Chainfire[/MENTION] specifies here.
[SuperR Kitchen] Captain_Throwback:
[MENTION=5787964]SuperR.[/MENTION]

One last feature that would be useful from a boot image modification perspective would be to have a provision for disabling forced encryption and/or dm-verity. Since ROMs built with a kitchen will never pass a verity check, the latter is really a necessity. The one unrooted ROM I built with the kitchen wouldn't boot because I forgot to disable dm-verity, so it might be nice to automate that process, and just offer the user a Y/N confirmation that they're okay with it (or maybe just offer to back up their stock fstab file).
[SuperR Kitchen] SuperR.:
Is the modification the same on all devices that require it? If so, send me an unmodified and modified so I can see what we are changing and what we are changing to and I will add it.
[SuperR Kitchen] Captain_Throwback:
I can tell you exactly what changes (and the changes are universal, though in the case of dm-verity, a partition may or may not be specified):

For forced encryption, in fstab,

forceencrypt changes to encryptable

and for dm-verity,

verify or verify=<partition-name-here> just needs to be removed. If at the end of a line, like (wait,verify), the preceding comma will also need to be removed.

Attached are before and after fstabs from a ROM I'm building now.
[SuperR Kitchen] Macguyver1980:
Coming back to test again the kitchen

Hi

Tried with last version of kitchen and when deodexing, had errors like:

... Deodexing wifi-service

/home/michael/Bureau/Super/superr: ligne 2300: java : commande introuvable

mv: impossible d'évaluer «/home/michael/Bureau/Super/superr_Miketrix/system/framework/arm64/wifi-service.dex»: Aucun fichier ou dossier de ce type
[SuperR Kitchen] bcrichster:
Deodexed a Note3 5.0 ROM with ZERO errors today, gotta check the Kitchen version tho.. Pretty sure it was latest version
[SuperR Kitchen] SuperR.:
v0.9.8.2

Changes:

New feature - Remove dm-verity from boot.img.

New feature - Remove forceencrypt from boot.img.

Kitchen updater changes to prepare for new version numbers.
[SuperR Kitchen] jazzespresso:
I did figure out my issue. I am working on two Samsung ROMs, one is SM-T350 and other is SM-P350, they both tablets are actually quite identical. Anyway, looks like all build ROMs stuff, troubleshooting, etc...it kinda mixed up the stuff (my fault!), so when I flashed ROM, it say "This package is for "gt5note8wifi" devices; this is a "gt5wifi". I know updater.script's assert piece on top checks and reads build.prop, but even if build.prop's from gt5note8wifi, suprised it did not flash it, I guess something else is being also checked....Not that i am complain, glad that it did not flash it, but just curious...

---------- Post added at 06:41 PM ---------- Previous post was at 06:40 PM ----------

nice, this is getting better.....one day, we may have "one click, done!" hah hah hah hah :)

excellent support and improvement...
[SuperR Kitchen] SuperR.:
The assert checks what your recovery says the device is, not the build.prop. It would defeat the purpose if the rom assert checks the build.prop in the rom, and normally we wipe /system before flashing so build.prop will rarely exist. Comparing the rom assert to the recovery is the best way, and that is why it would not flash.

Keep in mind that you can change the rom asserts from the rom tools menu to anything you want :)
[SuperR Kitchen] jazzespresso:
ohh so actually assert checks reads the recovery on the device, not build.prop, that's how it nows, so when I tried to flash SM-P350 ROM on SM-T350 tablet device, it tells me this is wrong device..

actually the new ROM I am working on should be working on both devices SM-P350 and SM-T350, so maybe in final build, I should remove assert check, so both SM-P350 and SM-T350 users can able to flash it without giving any error...hmmm...
[SuperR Kitchen] SuperR.:
It would be better to add both devices to the assert, than to remove the asserts. In the kitchen, go to rom tools, asserts. At the bottom you see the current assert. just add a comma and the other device

gt5note8wifi,gt5wifi

Then press enter. Now it will flash on both devices and still have asserts to prevent from flashing on other devices :)
[SuperR Kitchen] SimmoF:
I'm trying to make a rom for an SC-01F, Galaxy Note 3 from Japan.

I can make the rom zip, it flashes, but I get stuck in a boot loop.

I have tried everything including just extracting then making a zip without any changes.

I've tried set_metadata and set_perm.

I'm using the firmware SC01FOMUGOI4 which is 5.0 Lollipop.

Do you have any advice so I can get it to work?
[SuperR Kitchen] marcoperro74:
I would like to thank SuperR for his great work! I just cooked a base rom for a Samsung Galaxy Note 3 n9005 extracting system.img and boot.img from the original firmware samsung deodex and zipaligned it... I put root and busybox and take off only some app ... The rom have booted at the first attempt! Congrats!

Inviato dal mio SM-G928F utilizzando Tapatalk
[SuperR Kitchen] goodman_east:
the deodexed HTC A9 framework jars were wrong with this tool.

there are lots of NOPs in smali files . you cannot boot into system with this deodexed framework files.
[SuperR Kitchen] Captain_Throwback:
I'm able to boot into system fine with the deodexed files :confused:?
[SuperR Kitchen] goodman_east:
with superr? did you modify the jars?
[SuperR Kitchen] Captain_Throwback:
Yes, with SuperR's Kitchen. And no, I didn't modify anything.

---------- Post added at 09:01 AM ---------- Previous post was at 08:56 AM ----------

@SuperR.

Can you make an easy way to back out of a prompt for input that we may have entered by accident, without having to Ctrl-C to kill the script completely? Like an option to type "quit" or some key combo to allow us to back out? For example, on the deodexing screen, if you choose that option after the ROM is already deodexed, how are you supposed to get out of that menu? Or even allowing enter to be pressed with zero input to automatically go back to the previous screen?
[SuperR Kitchen] goodman_east:
I deodexed framework jars of HTC A9 . then replaced the original jars with the deodexed jars and deleted arm, arm64 and oat folders on my A9. it got stuck after reboot.
[SuperR Kitchen] Captain_Throwback:
I used the kitchen to deodex from a stock system. I didn't replace or delete anything manually.
[SuperR Kitchen] goodman_east:
you misunderstood what i said.

i deodexed framework from a stock system.img with this superr tool.

But i didnot make a new system.img or a full rom.

just replaced stock framework jars with deodexed jars, this operation is done on my htc a9.
[SuperR Kitchen] Captain_Throwback:
And I DID make a full, flashable ROM. I didn't replace anything on the device manually.
[SuperR Kitchen] goodman_east:
thanks, i will try it.
[SuperR Kitchen] SuperR.:
I fixed the deodex one. I did not realize that was happening so thanks for pointing it out. Is there anywhere else that has caused you problems before I push the update?
[SuperR Kitchen] Captain_Throwback:
Hm, nowhere that I can recall currently. If I come across any others I'll let you know :).

Thanks again for your great work here. I mentioned you over in the A9 forum and linked to this thread. Hopefully it'll get more exposure for HTC users, as we haven't had a working kitchen in a long time.