yashsingh1/xdaforums huggingface dataset:
[SuperR Kitchen] arkansawdave74:
Oh, my bad. I guess I was talking about the other Manjaro. The one that has a barebones net install as one of its 3 official versions and comes with no desktop at all, and whose stable repo keeps your system from breaking every other update. I don't know how I got confused because I actually Google stuff before talking about something I know nothing about. Thanks for filling me in. I'm not surprised you know more, as much as you have to fix stuff. So stay proud. You can say you run the most exclusive (almost) Linux around. That's way cool! If I had a biscuit, I'd give it to you, for sure!
[SuperR Kitchen] :
Eeh, no need to feel bad. Now that I've read what I posted again, I think I sounded like a major elitist ****.

Also, I wouldn't say Arch is exclusive. It's pretty popular and also easy if you dont mind doing a lot of reading.
[SuperR Kitchen] arkansawdave74:
Wow! I opened Chrome earlier and saw the "Submit Reply" button still sitting there, so I thought I had forgotten to send that last comment, and I was glad. Now I feel like the ****. I call Arch exclusive because I'm not welcome to seek any help in the Arch Forums being a Manjaro user. I have actually installed Arch twice in a virtualbox, but both times I removed it because I think Xfce4 and the Xfce4-goodies group installs wouldn't work, but later I tried in Antergos and got the same error so I think it was an Xfce issue upstream. It's so easy to do I couldn't have messed it up lol. Next time I will leave it up and join the Arch Forum so I won't feel excluded... Don't know why I didn't think of that before. Nice to see you're a nice guy and I apologize for my childish response. We should definitely be able to pick on each other's distros in good nature. I like any Linux to be honest and Linux users are my kinda peoples. Pleasure to meet you, [MENTION=3194357]iddeen[/MENTION].
[SuperR Kitchen] bcrichster:
Right on, Lmao! [emoji41] Hey.. I almost had you on Mint tho.
[SuperR Kitchen] arkansawdave74:
Ew.
[SuperR Kitchen] bcrichster:
[emoji23]

I did say ALMOST..
[SuperR Kitchen] arkansawdave74:
I must say, I appreciated it a lot more than that time you tried to make me install Windows...?
[SuperR Kitchen] mdiaz33685:
I have been making roms for many years, since HTC One V and M7 then switched to Samsung S2, S3, Note2, Note3, Note4 and got stuck with Marshmellow roms, so for about a year trying to install Ubuntu and trying the kitchen here and there month by month, and found it difficult. since I was used to [MENTION=673068]dsixda[/MENTION] kitchen for windows...

but yesterday is my first rom for my Tmo Note 4... on Marshmellow firmware... using the Ubuntu16.04 kitchen you have.. made it perfect rom on my first try in less than 30 minutes I had my Stock Odex Rom, the way I always make it..

Nice automation for the creation of the rom...

edit:.. thank you for your time... :D Transaction ID3XM16579TV064744H and Transaction ID: 3V980561GT2222034
[SuperR Kitchen] zengfu94:
[MENTION=5787964]SuperR.[/MENTION]

8K658111F3996121F

gitlab: zengfu94
[SuperR Kitchen] alnazef34:
hi sir

i used SuperR's Kitchen to unpack boot.img of N920v and repacked it without chinge

but it fail when flash it Odin
[SuperR Kitchen] bcrichster:
Did you make a zip or a tarball?

Sent from my Custom N9515
[SuperR Kitchen] alnazef34:
yes i make .tar by 7-zip
[SuperR Kitchen] mdiaz33685:
months ago I tried making a BL and CP-modem tar file for ODIN using 7-zip I didn't work and others told me that is how they did it, I booted into win7 and win10 with no luck... I did not work anymore or for me... :rolleyes:

after so much search I found and am using a program called peazip-v6.1.0

hope that helps... :D
[SuperR Kitchen] mauronofrio:
[MENTION=5787964]SuperR.[/MENTION] Thank you for add me to plugin repository
[SuperR Kitchen] chevycam94:
I tried to use the most recent version to make a flashable zip of Android O DP1 for the Nexus 6P. I got an error message saying "cat:...". It flashed by too fast to read the line. And when zipping it all up it said I was missing files and wouldn't proceed. Is there an error log or something? Everything else worked perfectly. Just that missing files error.
[SuperR Kitchen] bcrichster:
Deleted
[SuperR Kitchen] SuperR.:
I have not looked into O yet. The only thing I know for sure is that deodexing will fail due to the new *.vdex files. Hopefully smali/baksmali will get an update to handle them. Once that happens I will add support. O is very new and we need time to get all the changes sorted out.

Regarding the error going away too fast, you can scroll up in your terminal to see all output :)
[SuperR Kitchen] bigrammy:
Hi [MENTION=5787964]SuperR.[/MENTION]

Device = Mediatek :o

Type = system.ext4.win (TWRP backup.)

Kitchen Version = v2.1.5.5

Android Version = 6.0

I am working on a ROM with a /system/CDA/ folder which has odd permissions and needs root to access it.

The kitchen cannot seem to create a system.dat or system.img due to one or two problems.

1. root permission needed. (But not asked for by the kitchen)

[COLOR="Blue"]Creating system.img ...[/COLOR]
find: ‘system/CDA’: Permission denied

2. Partition size detection (The size of 3145728 for system is correct according to the /proc/partitions)

Determining partition size for system ...
/home/bigrammy/Desktop/srk5/superr: line 4213: 204800
3145728 * 1024: syntax error in expression (error token is "3145728 * 1024")

I am unsure what size format the kitchen expects to find there :confused:

Finally it ends with

ERROR:
Something went wrong building the image.

Make sure your partition size is correct and
that the directory is not too big to fit.

Press ENTER to return to the Main Menu
[SuperR Kitchen] zengfu94:
Kitchen version: 2.1.5.5 [MENTION=5787964]SuperR.[/MENTION]

I am trying to build off Android O preview factory image, extracted zip, didn't change anything and selected build.

I get this message:

ERROR:

Something went wrong building the image.

Make sure your partition size is correct and

that the directory is not too big to fit.

Press ENTER to return to the Main Menu

after selecting system.img detection method

Also tried adb detection while device was in TWRP and it was over 5 minutes so I canceled.

Attached are two screenshots, I looked through the script and it seems like it gives the error message because system_new.img is not found.
[SuperR Kitchen] chevycam94:
[MENTION=718594]super[/MENTION]R, this is what I'm getting in the terminal...

"Copying files to system ...

cat: /home/noah/Desktop/KITCHEN/superrs-kitchen/superr_AndroidO/00_project_files/cap_test: No such file or directory"

And yes, "cap_test" is missing from that folder.

Then when trying to build the full zip:

"MISSING FILES:

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

Press ENTER to return to ROM Tools menu"

All of those files/folders exist. Cant tell if its looking for a specific file, or its just confused.
[SuperR Kitchen] bcrichster:
Read post #5553

Sent from my Custom N9515
[SuperR Kitchen] PaulPizz:
[MENTION=5787964]SuperR.[/MENTION] Any chance of getting payload.bin option in the perm type menu? The pixel uses these. I believe they're somewhat like Ota updates.
[SuperR Kitchen] zengfu94:
You don't seem to realize that it's not just O, #5553 is explaining why deodexing does not work. O is still a system.img, a system folder and boot.img that the kitchen fails to compile. chevycam did get a zip built using the kitchen and it was O, I will download N to prove to you that it's not just O.
[SuperR Kitchen] bcrichster:
Maybe I should have highlighted the sentence "I haven't looked into O yet.." By SuperR? That statement still applies to the OS you're working with regardless of your intentions or objective

Sent from my Custom N9515
[SuperR Kitchen] zengfu94:
Thanks for wasting my time, I'll go download N and post the same exact issue
[SuperR Kitchen] bcrichster:
It's not wasting your time, it's called READ the statement. Changing the question around isn't always going to give you a different answer but yes, try N. This Kitchen has no claim to O yet being as Google doesn't even know what THEY're gonna be doing to it yet. That's like asking for a complete breakdown manual for a car that hasn't been released except for a few conceptual pics

Sent from my Custom N9515
[SuperR Kitchen] lonespeaker:
hi, just donated 3TD306115R637820Y my gitlab username is lonespeaker

thanks
[SuperR Kitchen] SuperR.:
If you send a link to the firmware, I will take a look :)

I have not looked into O yet. I will when I get a chance. If you have the same problem on N, send a link to the firmware and I will take a look :)

I have not looked into O yet. I will when I get a chance :)

I have no idea how to unpack payload.bin, much less how to build it. If I get time someday I will look into it. I was hoping [MENTION=5132229]xpirt[/MENTION] would take a look since it seems to be the new sparse_dat and he did a wonderful job with that :)

Added, thanks :)
[SuperR Kitchen] chevycam94:
Not just that, I'm NOT trying to deodex or anything else. Just extract from factory image, then zip into a flashable zip. That's all (for now)
[SuperR Kitchen] bigrammy:
One TWRP backup I already uploaded for someone test which worked fine for him.

https://mega.nz/#!jFIV2LjI!1bjOAG1bqEwP5D_s6MjwZpiLHIXXbDIfY9mwXkmU3WE

If you need the complete stock ROM it's Here

https://mega.nz/#!bARDWLZA!oYOYo9LtRECvPYgsediBm8RAh9WKhqz7vLZw3pzLVl4

I found an old 5.0 oem update zip which used set_metadata and this is what I found for /system/CDA notice the 0111 :eek:

set_metadata_recursive("/system/CDA", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0644, "capabilities", 0x0, "selabel", "u:object_r:cda_res_files:s0");
set_metadata("/system/CDA", "uid", 0, "gid", 0, "mode", [COLOR="Blue"]0111[/COLOR], "capabilities", 0x0, "selabel", "u:object_r:cda_res_files:s0");
set_metadata_recursive("/system/CDA/items", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0644, "capabilities", 0x0, "selabel", "u:object_r:system_file:s0");

A little more background info probably OT :laugh:

The ROM is very complicated with linking going on all over the place in various partitions like /cda /hidden /system/CDA and has taken me months to get my head around whats going on :silly:

I thought it was me doing something wrong as I normally build using set_metadata and never got any errors from the kitchen but the missing CDA contents explains why the ROM's would never boot after I did any mods in the kitchen. :silly:

A little insider info:

The Infocus ZM1 is Focaltech Industries own device (Manufacturer of the iPhone among many others it also seems a new budget Nokia is also going to be made by them too using a Mediatek mt6737 cpu or variant of the link we have to the oem dev of the ZM1 roms has been turned over to the dev of this new device which is a big loss for us. Sadly there is no source code for either device on the storage/server)
[SuperR Kitchen] zengfu94:
here's a little help with O [MENTION=5787964]SuperR.[/MENTION]

Downloaded latest N factory for 6P, choose sparse dat, created zip no problems.

Downloaded O preview for 6P, choose sparse dat, received "not a full rom! check if boot.img, system folder and meta-inf folder are there" went in the the superr script and removed that error check (isfullrom boolean) after removal it goes to the bytes menu like normal, choose system.img fails, choose system folder fails, choose adb and it hangs, choose manual and it fails. Then I switch from sparse dat to set metadata, everything builds fine but bootloop. I think it bootloops because something gets incorrect permission. There's also something about removeattr on a vendor lib error. I'll look into getting the isfullrom to pass later tonight.

N wasn't working on my original install of Linux so I switched to the ubuntu4kitchen and it works perfectly.
[SuperR Kitchen] SuperR.:
The fullrom build error is because of the missing xbin dir. The failed system.img i think is because of file_contexts. They are all messed up. Will update asap
[SuperR Kitchen] SuperR.:
v2.1.5.6 (Donate version)

Changes:

Updated img2sdat.

Updated sdat2img.

Use ls instead of stat to determine file contexts (thanks to [MENTION=4544860]osm0sis[/MENTION] for the tip).

All menus are now ENTER free unless there are more than 9 options.

Added support for /system/CDA (hopefully).

Fixed some local permission issues building system.img/sparse_dat roms.

Check to be sure files/directories exist before writing metadata line when extracting system.img.

Initial support for Android O.

Prevent deodexing Android O until it works.

v1.1.4.6 (Standard version)

Changes:

Updated img2sdat.

Updated sdat2img.

Use ls instead of stat to determine file contexts (thanks to [MENTION=4544860]osm0sis[/MENTION] for the tip).

All menus are now ENTER free unless there are more than 9 options.

Added support for /system/CDA (hopefully).

Fixed some local permission issues building system.img/sparse_dat roms.

Check to be sure files/directories exist before writing metadata line when extracting system.img.

Initial support for Android O.

Prevent deodexing Android O until it works.
[SuperR Kitchen] bigrammy:
And just like that it's done :eek:

You absolutely astound me and make me feel so inadequate all at the same time. :o

Thanks so much :highfive:
[SuperR Kitchen] zengfu94:
Just wondering, how did you get around no file_contexts?
[SuperR Kitchen] SuperR.:
O and N both use file_contexts.bin, but they changed the format slightly in O. The kitchen was pulling the wrong data from file_contexts.bin so the file_contexts file was messed up causing system.img creation to fail. Now we pull the correct data and it works :)
[SuperR Kitchen] zengfu94:
Glad you got it working, I looked at JesusFrekes smali and he said to pass API 26 when using O. I'm going to test and see if it works or not.
[SuperR Kitchen] zengfu94:
[MENTION=5787964]SuperR.[/MENTION] One more thing for O.

When extracting an image, a cat: /romdir/cap_test no such file or directory flashes across the screen. I found it in the bottom of the imgextract function but could not figure out what it does.
[SuperR Kitchen] SuperR.:
v2.1.5.7 (Donate version)

Changes:

Updated smali/baksmali to the latest commits.

Fixed cap_test error in Android O.

Enabled Android O deodexing (Alpha).

Removed oatdump deodex method for M and N.

v1.1.4.7 (Standard version)

Changes:

Updated smali/baksmali to the latest commits.

Fixed cap_test error in Android O.

Enabled Android O deodexing (Alpha).

Removed oatdump deodex method for M and N.

NOTE: oatdump has been removed because I won't keep up with it. Each Android version has a different oat version, and needs different binaries. I have already missed 7.1, 7.1.1, and 7.1.2 binaries and now O is out. RIP oatdump :)
[SuperR Kitchen] TheHiman:
[MENTION=5787964]SuperR.[/MENTION]

Can you please add the older smali/baksmali 2.2b4 back as 2nd option ?

Please try a deodexing session with the final 2.2-Version on G900F-ROM (CQC2 as sample)

The deodexing process showed up with 2 errors and quit. The oat-files from the odexed rom are completly deleted and

the entire framework folder is not deodexed. So with this update deodexing on samsung 6.0.1 is no longer

working. Not tested older versions for now.

Eventualy the latest 2.2-Version need some extra switches or something else when called with your script ?

Changed command-line parameters ? i get no errors logged to any logfile, so i can´t tell you more at the moment.
[SuperR Kitchen] SuperR.:
I see there is a problem using the latest smali/baksmali to deodex anything other than O. I did not expect this kind of regression. I will post an issue on the smali github about it when I get a chance. For now you can add the older versions to the tools/smali/current directory and the kitchen will give you an option of which to use. I have attached the older versions below.

edit: Issue submitted
[SuperR Kitchen] zengfu94:
[MENTION=5787964]SuperR.[/MENTION] sorry to bother again but O deodexing on boot.oat throws an error because explained here. I have added the -a 26 in the framework deodexing section and it works flawlessly. One other thing is it seems like PrebuiltGmsCore has more apks in its folder that show up as the following odex files are still in your ROM.
[SuperR Kitchen] boostermbkking:
edit, wrong message
[SuperR Kitchen] KoSett:
Man,

For windows os?

Please make for windows .
[SuperR Kitchen] SuperR.:
All will be fixed in the next update :)

Stay tuned ;)
[SuperR Kitchen] SuperR.:
v2.1.5.8 (Donate version)

Changes:

Added api to smali command.

Set api to 26 before deodexing Android O.

Deodex PrebuiltGmsCore/app_chimera with the rest of the ROM.

Updated smali/baksmali to latest commit to fix deodexing on pre O roms.

v1.1.4.8 (Standard version)

Changes:

Added api to smali command.

Set api to 26 before deodexing Android O.

Deodex PrebuiltGmsCore/app_chimera with the rest of the ROM.

Updated smali/baksmali to latest commit to fix deodexing on pre O roms.
[SuperR Kitchen] zengfu94:
You're the man
[SuperR Kitchen] tomatolei:
[IMG="error"]https://img2.brain3.photobox.com/75955295941cc7ce178b836a147db248fec5a40b0bb9a846cb0828ad40d770187ab22a61.jpg[/IMG]

v1.1.4.8 deodex G9350 QC4 7.0 has a error，

System ERROR:
未知的错误 -2147024872

... Deodexing framework

basename: 额外的操作数 "find"
Try 'basename --help' for more information.
Can't find file: /home/leilei/superrs-kitchen/superr_9350/system/app/framework/oat/arm64/framework.odex/
Exception in thread "main" java.lang.IllegalArgumentException: Cannot find file or directory "/home/leilei/superrs-kitchen/superr_9350/system/app/framework/oat/arm64/smali"
at org.jf.smali.Smali.assemble(Smali.java:82)
at org.jf.smali.AssembleCommand.run(AssembleCommand.java:96)
at org.jf.smali.Main.main(Main.java:99)
Unable to add '/home/leilei/superrs-kitchen/superr_9350/system/app/framework/oat/arm64/classes*.dex' to '/home/leilei/superrs-kitchen/superr_9350/system/app/framework/framework.apk': file not found
[SuperR Kitchen] SuperR.:
Send a link to the firmware and I will take a look. Make sure the link is fast and does not require a login for downloads.
[SuperR Kitchen] Hamidreza2010:
Bro is automatically sign and zipalined .apk and .jar files after deodex or not ?

thanks
[SuperR Kitchen] SuperR.:
The kitchen does not sign apk's and zipalign happens when you build the rom. There is an apktools plugin that will sign apks and there is an option to zipalign anytime you want in the donate version.
[SuperR Kitchen] tomatolei:
G9350ZCU2BQC4.zip download

https://drive.google.com/open?id=0B_2pC_8DfT-GSGpxYW1nVVA4emM

You try deodex，thanks！
[SuperR Kitchen] SuperR.:
v2.1.5.9 (Donate version)

Changes:

Added support for deodexing system/vendor/framework.

v1.1.4.9 (Standard version)

Changes:

Added support for deodexing system/vendor/framework.

Fixed :)
[SuperR Kitchen] msuki:
thanks for this kitchen.
[SuperR Kitchen] Hamidreza2010:
Did kitchen support for deodexing system/vendor/app ?

for sony roms
[SuperR Kitchen] SuperR.:
I think so, don't remember actually. Let me know
[SuperR Kitchen] Hamidreza2010:
thanks

for now i dont have linux

when i install it in vmware , i will test it
[SuperR Kitchen] Captain_Throwback:
https://bitbucket.org/superr/superr...ster&fileviewer=file-view-default#superr-2455

Don't see system/vendor/app listed there, if that's where it would be...
[SuperR Kitchen] SuperR.:
That is where it would be. system/vendor/app should be included, I just don't remember testing it specifically. The line:

odextmp=$(find system vendor -name *.odex 2>/dev/null | grep -v "system/framework/oat/\|system/framework/$arch/\|system/framework/$arch2/\|system/app/\|system/priv-app/\|system/framework/oat\|system/vendor/framework/oat" | rev | cut -d"/" -f4- | rev | sort -u)

Looks for all odex files in /system and /vendor (if it exists), and removes everything listed after the grep -v. Since /system/vendor/app is not removed, it should be moved and deodexed :)
[SuperR Kitchen] TheLogicalGamer:
In general how much space is needed to decompile a system & boot img? Only reason I ask is I'm trying on a vm I gave the vhd 40 gigs, and then used 4gigs as a swap partition. Would that be enough to decompile, or would I need upwards of 100 gigs?
[SuperR Kitchen] SpasilliumNexus:
40GB - 4GB (Swap) - ~5GB (Linux install) - ~1GB for essentials (kitchen dependencies + Java) = ~30GB free space

More than enough to decompile a ROM and rebuild a new one.

+100GB is for downloading a ROM source like CM and building it.
[SuperR Kitchen] millo1978:
Hi!

thanks for this wonderful work! :)

I downloaded the last version and I have a Huawei P9 lite (L21).

I' m able to deodex, root, disable ForceEncrypt, etc...

but I can't disable DM Verity...

why?

DM Verity is always enabled (says the Kitchen).

There is a "manual" way to disable it?
[SuperR Kitchen] millo1978:
I downloaded it with Firmware Finder ...

but I found it here also:

http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1164/g104/v78140/f1/full/update.zip

:)
[SuperR Kitchen] SuperR.:
It says dm-verity is still enabled because your /cust also has it enabled along with /system. I am not sure if the kitchen should disable dm-verity on /cust also, or only report /system dm-verity so I am not sure which change to make. Even though it still says enabled, it is actually disabling it for /system fyi
[SuperR Kitchen] dkionline:
Disable verity in boot.img fstab is enough.
[SuperR Kitchen] SuperR.:
Both /system and /cust in fstab have dm-verity enabled:

system /system ext4 ro,barrier=1 wait,verify
cust /cust ext4 ro,barrier=1 wait,verify

The kitchen looks for "verify" and if it finds it the dm-verity status is enabled. When we choose to disable it, it only disables /system (currently) so we end up with:

system /system ext4 ro,barrier=1 wait
cust /cust ext4 ro,barrier=1 wait,verify

The kitchen still finds "verify" so it still says enabled.

The question is, should the kitchen also remove "verify" from /cust in fstab or should it only check for and remove /system dm-verity?
[SuperR Kitchen] millo1978:
You Guys are great!

I don't know... that's first time that I find so much parts of rom...

with my Samsung S3 I worked always only with system and boot...

But in my new Huawei P9 lite there are:

SHA256RSA, CRC, CURVER, VERLIST, EFI, MODEMNVM_UPDATE, SENSORHUB, FW_HIFI, CUST, SYSTEM, XLOADER, FASTBOOT, FW_LPM3, TEEOS, TRUSTFIRMWARE, MODEM_FW, BOOT, RECOVERY, RECOVERY2, DTS, CACHE

Do I have to put in kitchen CUST.img also, or not?

What do you think about?
[SuperR Kitchen] dkionline:
We usually remove all verity flags in fstab. MM roms didnt bootup, so we delete it. Theres a little more in N to remove, but dont know if needed, cause rooting by SuperSU removes it anyway.

yes, boot, system, cust and proper data like hw/eu if needed.
[SuperR Kitchen] theimpulson:
How to build back system.new.dat file for flashing?