yashsingh1/xdaforums huggingface dataset:
[SuperR Kitchen] baloo30310:
Hi super's! I have a problem with the kitchen and my Note 8. I compile a Rom and the Flash I hang on the Samsung logo. I had the problem with the Note 4 that had been solved but I do not remember how I made an idea for me

---------- Post added at 01:07 PM ---------- Previous post was at 12:52 PM ----------

Hi Super's! A small question would it be possible to reference the Note 8 SM-N950F in quote.

Peripheral: greatlte

Product: greatltexx

Processor: Exynos5 / Exynos8895.

Thank you !;)
[SuperR Kitchen] shoey63:
Did you unpack the boot.img and disable dm-verity?
[SuperR Kitchen] baloo30310:
Uh! No I took the original boot.img with the AP.tar and then the cache.img for the OMR file.

But thank you for your answer.:good:
[SuperR Kitchen] ale8530:
[MENTION=5787964]SuperR.[/MENTION] will the vdexextractor tool for the Oreo deodex be integrated into this version?
[SuperR Kitchen] baloo30310:
Hi Super! good i've always the problem that I rest block on the boot Samsung even after the DRM security. then I encounter a other problem cooking do extract not the whole system it stops at csc_contents an idea ?
[SuperR Kitchen] SuperR.:
v1.1.8.1 (Free Bash version)

Changes:

Updated md5 for Android Image Kitchen by [MENTION=4544860]osm0sis[/MENTION] to v3.1.

Use apk name for deodexing instead of app directory name in case the names are different.

General cleanup.

Send a fast link to the firmware that does not require registration and I will take a look.
[SuperR Kitchen] feyd2blak:
Hi

I'm trying to work with one of googles factory OTA builds.

Extracts great, but my question is; can I rebuild it to an adb sideload OTA zip??

Thanks
[SuperR Kitchen] baloo30310:
OK Thank you for your help! I upload the firmware of the N8 and I send you the links.:good:
[SuperR Kitchen] haqanguven:
Thansk :)
[SuperR Kitchen] dragos281993:
Any news about deodexing Oreo 8.1? I haven't seen any concrete/precise solution to deodex without errors since 8.1 came out.
[SuperR Kitchen] SuperR.:
Is this different than a rom zip? Sorry, never used adb sideload.

The donate version can deodex 8.1
[SuperR Kitchen] feyd2blak:
Thanks for the reply....I'm not sure to be honest. All I know is that the google OTA builds have a system.new.dat instead of the system.img

Perhaps I can zip the files like a standard build but have the content be the system.new.dat??

I'm just going to have to look deeper into your kitchen code to see how you build and hack it to work the way I need it to??
[SuperR Kitchen] SuperR.:
Choose sparse_dat perm type to build this type of ROM
[SuperR Kitchen] feyd2blak:
CHAMPION! Thank you, and will do!
[SuperR Kitchen] baloo30310:
Hi Super's! following your message I think you'll sent the link firmware for the note 8. thank you in advance.

Here : https://mega.nz/#!lF5wRJRY!UZjZFxSgWn40inl3eLLyKqww_uojSHeYn8o2e6r2TU8

Envoyé de mon SM-N950F en utilisant Tapatalk
[SuperR Kitchen] NYCHitman1:
Any plans to bring this to the free version?
[SuperR Kitchen] SuperR.:
Can you send a support.zip after you get this message? Or, tell me all the steps you took and choices you made when you extracted/built the rom. I need to make sure I can reproduce your issues or I won't be able to fix them.

edit: Just downloaded your firmware, extracted choosing set_metadata perm type, and built the rom with no issues in 64-bit Ubuntu 16.04.3. If you continue having issues, you can try Ubuntu4Kitchen or Mint4Kitchen linked in my signature.

At some point yes, but no eta. It is a time issue and the donate kitchen is always my top priority :)
[SuperR Kitchen] problemathic:
https://www.needrom.com/download/cherry-touch-xl-2/

Coukd you add my device heres my firnware link :)
[SuperR Kitchen] nobreak:
superr: can't execute: Permission denied..... [ROM][7.1.2][OFFICIAL], Lenovo k3. Have root....Where is the problem?
[SuperR Kitchen] SuperR.:
I do not download from sites that require registration. The kitchen creates it's own device support so as long as it works for you as it is you should be good.

Are you saying you fixed your problem by patching with magisk?

edit: your updater-script is missing symlinks. This will certainly break things.

I have no idea what this is. If you follow the instructions in the OP it will work for you. If you still have trouble, you can try Ubuntu4Kitchen or Mint4Kitchen linked in my signature
[SuperR Kitchen] problemathic:
also why sometimes the kitchen wont exttact zips? it will say there is no rom to extract something like that. or is not supported maybe? Example is Homtom Mod rom. Cant extract it with the kitchen when i create new project.
[SuperR Kitchen] baloo30310:
Hello Super's! Not exactly that it would be too good I always have the problem impossible to leave a Rom.

I have noticed that he misses symlinks.:crying:
[SuperR Kitchen] bcrichster:
What are you extracting the ROM from? [MENTION=5787964]SuperR.[/MENTION] recommends pulling from a system.img
[SuperR Kitchen] SuperR.:
The kitchen only extracts zips that it sees as rom or firmware zips. It checks the contents of the zip before unzipping. If it does not find one of the things it looks for you get an error message. I have no idea why it won't extract Homtom Mod rom because you did not provide a link that does not require registration.

The updater-script in the rom.zip you sent has been modified from what this kitchen creates. I do not take any responsibility for your edits. If you are starting with the firmware you sent and you are running in Linux, the kitchen generated updater-script would have symlinks for sure.
[SuperR Kitchen] problemathic:
Homtom Mod is for sure flashable rom. Its a custom rom for our device. Ported it and flashed succesfully its just the kitchen wont extract it. dont know why. i want to debloat it and deodex.
[SuperR Kitchen] KittyChampion:
I am sure SuperR can look it out for you if you provide a link that doesn't require registration.

Google Drive, Mega.nz, etc
[SuperR Kitchen] baloo30310:
Hi Super's I confirm that this is the Free version of Linux I redid a Rom and always the same bone does not install the partition system does not want this mount.

I join you screen with.

More links of the new Méta-Inf .

Thank's for Advance

[IMG="screen 1"]https://zupimages.net/up/18/03/0iki.png[/IMG]

[IMG="screen 2"]https://zupimages.net/up/18/03/w7gu.png[/IMG]

https://mega.nz/#!blJ3GIiA!-Fx5mIKDZvHFpPH53rSlgwuu2NRfYbfNpcM5gmh4a0o
[SuperR Kitchen] baloo30310:
Hi [MENTION=5297774]bcrichster[/MENTION]!

That's what I did but nothing happens
[SuperR Kitchen] SuperR.:
The problem is that these 2 apps have arm/*.odex and arm64/*.odex. This is the first time I have seen this and I don't know how to handle it properly or if it even matters. It is actually deodexing both apps, but it is using arm64/*.odex to do it. The reason it says it is still odexed is because the arm/*.odex still exists. The only option is to pick one if both exist and delete the other. Any idea which one should be picked?

You could do some testing to find out if they work properly. Here are links to those 2 deodexed apps in both arm and arm64. If you try them and one does not work, then we know how to handle them. Let me know the results so I can update the kitchen. Thanks :)

arm64 versions

arm versions
[SuperR Kitchen] Er. Aditya:
i am on windows currently and il try the deodexer available for windows and let you know the result

on how actually that deodexer works gimme few mins , il have to start from scratch
[SuperR Kitchen] SuperR.:
Thank you, but unfortunately that will not help me figure out which one should be used if they both exist :(
[SuperR Kitchen] Er. Aditya:
actually bro i dont have a note 5 :( i have a note 4 so it wont be possible

sorry for being of no help
[SuperR Kitchen] SuperR.:
No problem. Thanks for what you did :)

For now I will delete arm if both exist. It can be changed later if it causes issues. I guess that is another way to find out ;)
[SuperR Kitchen] Er. Aditya:
anytime mate , what your doing for is amazing

thankyou :)

il wait for the updated kitchen and report if i can get it to test soon :D
[SuperR Kitchen] SuperR.:
v0.9.3.3

Changes:

Fixed L and M deodex when an app or priv-app contains two arch directories.

Compiled and included the newest oat2dex.jar.

Other minor fixes
[SuperR Kitchen] fhem:
[MENTION=5787964]SuperR.[/MENTION] I think a recent update broke the deodexer. I'm working M roms for N6 and N9. All was doing ok but the kit doesn't deodex the apps and priv-apps anymore --- It sems like the tool is not reading the boot.oat/boot.art. Love your kitchen and your work. Thanks
[SuperR Kitchen] SuperR.:
Please provide more information. Check post #4 for a list of things that would be helpful to know.

I just deodexed the Nexus 9 and it works fine. Not sure what is causing your issue. Are you getting errors? What makes you think the app/priv-app are not getting deodexed?

boot.oat is not extracted in M like it is in L fyi.
[SuperR Kitchen] chuzpz:
[MENTION=5787964]SuperR.[/MENTION] I solve the problem to wifi. :D Thnx for your help and your kitchen.. Works fine for me. If you interested of the problem is because to my cellphone have a similar and big quantity of version of phone the Grand Prime have G530H, G531H, G530F, G530M and more many more. And the stock firmware not have a radio.img I believe this file contains the signals of wifi or i dont not what file contains the signals of wifi. well the problem solve installing the same rom first in odin and after making the wipes and everithing in the custom recovery and the wifi works.. :D It's very weird. but it worked.

Ok i hope my experience help him to get better yur kitchen. Is mi desire. :D and nothing that is all.. Thnx for your kitchen and your time and everithing i follow this post and i try to work always with this kitchen i like so much and i love this kitchen.. :D
[SuperR Kitchen] fhem:
Ok --- I extracted clean MM N6 and N9 images and retried. Yes the N9 appears to working fine but the N6 does not appear to working properly. Not sure what the issue is. I tried looking at the code for your latest commits but I'm not smart enough to figure it out. :confused::D. If I can do something to help please ask. Thanks for your support and hard work. FYI: Yes classes.dex in N9 deodexed apps No classes.dex in N6 deodexed apps.
[SuperR Kitchen] SuperR.:
You are correct and I see the problem. Will fix asap and update. Thanks for pointing this out :)
[SuperR Kitchen] SuperR.:
v0.9.3.4

Changes:

Fixed deodex L and M when there is only one arch
[SuperR Kitchen] SuperR.:
v0.9.3.5

Changes:

Really fixed deodex L and M when there is only one arch. Missed priv-app before.

Sorry for the trouble :o
[SuperR Kitchen] fhem:
LOL I just saw that. Thanks for your help and support. :good::good::good:
[SuperR Kitchen] hohassan444:
[MENTION=5787964]SuperR.[/MENTION]..thanks for your continuous and hard work. I have problem in updater-script file formation. I try to port rom to my device...building and installation go normally ...however :

1 - if i use set_metadata or set_perm...i have a problem in WIFI ( stuck in obtaining ip address).

2 - using sparse image ....no problem in WIFI

3 - Also in using sparse image...no root is added

thanks in advance
[SuperR Kitchen] rcunningham:
updater-script

So when I get the stock ROM and boot.img it looks like a full stock ROM, but when I look at the updater-script its empty. I used the extract ROM option. Not sure what I am doing wrong. I have done all the suggested things, tried all the methods for perms and still nothing.
[SuperR Kitchen] SuperR.:
I suggest you use sparse dat if it is not causing issues and the others do.

The kitchen does not add root files to the rom. Instead it adds a flashable SuperSU.zip to the rom zip which gets flashed after the rom.

Please check post #4 for questions I would like to have answers to.
[SuperR Kitchen] SpasilliumNexus:
Running 0.9.3.5 pulled from git, and it seems to have an issue with not finding system_new.img, which didn't happen on v0.9.2.6.

This is happening on a completely clean kitchen and factory image, which outputs system.img after setting up the project, and never see system_new.img even when beginning to build.

When trying to build, I get a 150MB size zip, which is not right at all. It has everything in it except the sparse files.

This is in main.log

Logs are attached if needed. Also if needed, kitchen settings:

Moto X Pure Edition

Deodex: Yes

Root: Yes

User app: Yes

Perm type: sparse_dat

Asserts: clark
[SuperR Kitchen] Androidwizzard:
I'd like to mention that this won't give root to many of the new Samsung devices and firmwares, which need ramdisk modifications too, kinda "root kernel".

Just for those users who aren't aware of Samsung's recent security updates.
[SuperR Kitchen] SuperR.:
I think the problem is with these lines in your updater-script:

format("ext4", "EMMC", file_getprop("/tmp/config", "byname") + "/system" + file_getprop("/tmp/config", "slotnum"), "0", "/system");
mount("ext4", "EMMC", file_getprop("/tmp/config", "byname") + "/system" + file_getprop("/tmp/config", "slotnum"), "/system");
package_extract_file("boot.img", file_getprop("/tmp/config", "byname") + "/boot" + file_getprop("/tmp/config", "slotnum"));

When I build using your firmware, those lines look like this:

format("ext4", "EMMC", file_getprop("/tmp/config", "byname") + "/SYSTEM" + file_getprop("/tmp/config", "slotnum"), "0", "/system");
mount("ext4", "EMMC", file_getprop("/tmp/config", "byname") + "/SYSTEM" + file_getprop("/tmp/config", "slotnum"), "/system");
package_extract_file("boot.img", file_getprop("/tmp/config", "byname") + "/BOOT" + file_getprop("/tmp/config", "slotnum"));

Notice the capital SYSTEM and BOOT. I don't know why yours is different.
[SuperR Kitchen] baloo30310:
I don't know ?

Envoyé de mon SM-N950F en utilisant Tapatalk

---------- Post added at 06:56 PM ---------- Previous post was at 06:48 PM ----------

Hi [MENTION=718594]super[/MENTION]'s ! Do you think it could come from that?

Envoyé de mon SM-N950F en utilisant Tapatalk
[SuperR Kitchen] SuperR.:
I would not have said I think it if I didn't.

I don't know why it's not using the capital SYSTEM and BOOT on your machine. They should be capital for your device (greatlte). They are capital when using 64-bit Ubuntu 16.04.3 which is all I test with. You could try Ubuntu4Kitchen or Mint4Kitchen (linked in my signature) which are set up for the kitchen. Or, you can replace the lines I provided in your updater-script manually and see how it goes.
[SuperR Kitchen] baloo30310:
Hi [MENTION=718594]super[/MENTION]! I made the changes as on the install script starts but hangs on Samsung bootanimation.

At the installation I do not see Magisk & Busybox settle.

bizzard:silly:
[SuperR Kitchen] SuperR.:
Please try flashing this ROM I just built using the firmware you sent (N950FXXU2BQKG_N950FOXM2BQKG_XEF.zip).

baloo30310_test_rom.zip

As you already know, this kitchen does not include/support Magisk so I used SuperSU for root.

These are the steps I took:

Extracted firmware zip using option #4, and chose set_metadata perm type

Added root, let SuperSU decide

Added Busybox

Unpacked boot.img and removed dm-verity and forceencrypt, repacked boot.img

Built full rom zip

The set_metadata permissions are different in this updater-script than what the kitchen currently provides. I am working on improving the updater-script so some of that is reflected here and will be in the next update.
[SuperR Kitchen] baloo30310:
Thank you I download and test and I'll let you know!
[SuperR Kitchen] lalitjoshi06:
how to select twrp backup system.ext4.win000 & system.ext4.win001 to extract.'

it select only one to extract. after that if i select another it moved old one to other place.

need help.
[SuperR Kitchen] SuperR.:
When you choose any system.ext4.win00*, all system.ext4.win00* files are extracted at the same time. When you chose the second one, the first extraction was moved to make room for the new one which is exactly the same as the first one.

Solution: only extract it once by choosing one of the system.ext4.win00* files :)
[SuperR Kitchen] lalitjoshi06:
thanx for reply.

I sucessfully make rom via stock firmware with superr kitchen.

but when i making it from twrp backup it is not flashing just rebooting to recovery while i select flash (just start and reboot to recovery).

can u help regarding this issue.
[SuperR Kitchen] Androidwizzard:
I've made quite a lot of roms from recovery images, namely dumps and then converted the images with cygwin.

Never tried with a kitchen though....

However - making a rom out of these sources will lack symlinks so I recommend to replace meta-inf folder by a working one (created from stock firmware) - easiest way :good:
[SuperR Kitchen] baloo30310:
Hi [MENTION=718594]super[/MENTION]!

Good test of your base test is ok.

But it's a shame I wanted to integrate Magisk good no problem.

I will remake the same with the deodexation plus the débloat.

I thank you for your patience and your help.:good:;)
[SuperR Kitchen] SuperR.:
If stock firmware contains a system.img, that is the reason it works better. When extracting a system.img all the original file permissions, capabilities, and contexts are used. When extracting from a TWRP win/tar backup a default set of permissions are used, which is not nearly as good.

Your TWRP should have a way of backing up img files instead of the default win format. These img backups will work as well as your stock firmware. You may need to rename to system.img and boot.img if they are not already named this way.

Glad the ROM worked :) FYI, the donate version of the kitchen supports Magisk :)
[SuperR Kitchen] baloo30310:
Hi Super!

I made the same Rom as you by adding the débloat more deodex.

I met again the problem of Meta-Inf: for SYSTEM & BOOT which is written in lowercase.

So the Rom is not happening.

I had to modify the script with note pad ++ and after Flas it passed like a letter to the post office.

Thank you again for your help.:good::cool:
[SuperR Kitchen] AL_IRAQI:
I keep getting this error when i try to excract system img

Mounting system.img ...
mkdir: cannot create directory ‘output’: File exists
[sudo] password for abdo:
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
missing codepage or helper program, or other error

In some cases useful info is found in syslog - try
dmesg | tail or so.

Copying files to system ...
cp: cannot stat 'output/*': No such file or directory
umount: output/: not mounted

Edit:

Already found other posts talking about it, ill take a look :D

Edit 2:

i cant install git-lfs, i already followed their guide :\

sudo apt-get install git-lfs
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package git-lfs
[SuperR Kitchen] bcrichster:
Try going into your software (pkg) manager and manually search for git & git-ifs.. There may be a similar package with a slightly different name you can use for your distro. Some distros change the names of the packages
[SuperR Kitchen] baloo30310:
Hi @ Super's!

I still have a problem I think it comes from deodexation.

SuperSu & Busybox does not launch.

So do not settle.

This does not stop the Roma from starting.

I did exactly the same manipulation as you.

It drives me crazy this story. :silly::silly:
[SuperR Kitchen] SuperR.:
You must not be mounting a valid raw ext4 system.img. I can take a look at it if you send a fast link that does not require registration.

The kitchen no longer uses or requires git-lfs, so no worries about installing it :) Did I forget to remove git-lfs instructions from somewhere?

I am not surprised that deodexing causes issues. You may have noticed the disclaimer when choosing to deodex. If you don't plan to modify apk/jar files, deodexing is not helpful anyway.

As I mentioned, the updater-script in the ROM I sent is different than what the current kitchen creates. This may be another reason mine worked properly and yours does not. Try using the updater-script from my build and see how it goes. The changes to the updater-script will be in the next update when I get time :)
[SuperR Kitchen] TheMisanthropist:
Good night!

I tried with a few roms and the ones that have an uncompressed /system work like a charm.

But the ones that have a system.new.dat won't boot after running through superr.

Few questions:

What kind of persistence should I use? (Does it matter?)

How to build the Rom zip and the underlying system.new.dat after edition?

Thanks!

Will donate in the morning. Project is excellent
[SuperR Kitchen] SuperR.:
This is most likely due to missing permissions/capabilities from make_ext4fs. It uses AOSP permissions and capabilities. The donate version will likely fix this for you, as it uses permissions/capabilities from the source image that was extracted when it builds the system.img.
[SuperR Kitchen] TheMisanthropist:
Thanks for answering Sir.

There is an announcement that version 3.1.1 has been released but my updater only took me to 1.8, is 3.1.1 just donate or am i doing something wrong?

Greetings
[SuperR Kitchen] SuperR.:
There are 2 completely separate programs.

The free version written in Bash for Linux uses v1.x.x.x

The donate version written in Python for Windows and Linux uses v3.x.x.x

You originally posted in the donate thread and I moved your post to the free thread (this thread). That may be why you are confused :)
[SuperR Kitchen] TheMisanthropist:
Thanks for the Answer Sir.

Please: i updated to 1.8.1 and now it creates a zip update that my cellphone tries to install but, it only runs about 20% of the progress bar, says that the update finished with success and then nothing happened when i reboot.
[SuperR Kitchen] NocDev:
Gitlab User: NocDev

P.S. sorry for my first post
[SuperR Kitchen] SuperR.:
v1.1.8.2 (Free Bash version)

Changes:

Massive improvements to set_metadata updater-script lines when extracting a system.img as the base.

Sort extract options alphabetically.

New kitchen launcher written in Python to prevent closing double-click to run window after keyboard interupt.

Added support for extracting roms that include system.new.dat.br.

Updated configure.sh to find full byname partition path on device.

Updated updater-scripts to reflect the new configure.sh changes.

Fixed adding /data support not replacing the partition placeholder and not working.

Removed some unused dependencies.
[SuperR Kitchen] haqanguven:
Thanks :)
[SuperR Kitchen] NYCHitman1:
[MENTION=5787964]SuperR.[/MENTION]

Just donated -- my GitLab account is jchasky

Confirmation -- 909566197675657.
[SuperR Kitchen] :
So far this looks promising on os x

I've got everything to make kitchen start now all I do is to change Linux binaries and it might run on os x this is great in one way but I don't expect support for it though

Just wanted to mention it since it's a great aio kitchen [emoji3]
[SuperR Kitchen] dataghost2014:
Thank you again

Still do not have enough posts to message you about the Amlogic device. ill make some posts so I can contact you, thank you.
[SuperR Kitchen] AL_IRAQI:
Hey buddy, i was trying to extract Moto G5s Plus ROM, they used sprase img, i had to convert it to .img then extract with the kitchen

you can find it here

you didnt forget it, i used search to find git-lfs stuff
[SuperR Kitchen] SuperR.:
I just downloaded and extracted the firmware you linked without issues. I chose the firmware.zip to extract from the kitchen menu. It extracted all the sparsechunk files and the boot.img. Then it converted to raw, fixed the ext4 img, mounted the new system.img and extracted all the files. Not sure why it did not work for you.
[SuperR Kitchen] AL_IRAQI:
Thanks for testing it out, i did convert sparsechunk files with other tool, maybe that is why it didnt work, ill try again using the kitchen only.

Edit:

[MENTION=5787964]SuperR.[/MENTION] so i did try again, it did extract it again with kitchen only this time, but many folder inside system like ( lib or framework) are empty