yashsingh1/xdaforums huggingface dataset:
[SuperR Kitchen] bigrammy:
Hi,

I wasn't having a pop at you bro but just trying highlight that your BLU rom is a real one off even by Mediatek standards :laugh:

I am still not totally convinced that it's pure Lollipop as it has the smallest Lollipop "kernel" I have ever seen at just 3.8mb :eek: :laugh:
[SuperR Kitchen] tirta.agung:
Hi there, anyone here know how to add init.d capabilities to the latest CM 12.1 nightlies and all of it derivatives without the need of any apps that emulate it?

I found out that the necessary files are there, but it seem the latest CM 12.1 nightlies just prevent it from executing the sysinit.
[SuperR Kitchen] Q9Nap:
[MENTION=5787964]SuperR.[/MENTION]

Just tried the latest version of the kitchen (0.9.6.6) using the user app support feature for the first time.

Just fyi, I tried using it with just one apk and it wiped my data partition and caused a boot loop until i wiped data in recovery.

The option to install dependencies automatically is a nice addition though; keep up the good work :)
[SuperR Kitchen] SuperR.:
Sorry for being out of the loop for a while. Had a large project for work that demanded all my time.

[MENTION=1162986]Captain_Throwback[/MENTION] - Thank you for the detailed information.

The metadata appearing twice was fixed in a later version of the kitchen.

The blk_discard error is likely due to the size of the partition. The raw system.img should work but it does not always. If you can get the actual partition size in bytes and choose to enter the size manually it will probably work for you.

Please try test kitchen 4 posted at the bottom of this post. It may sort out the boot.img issues as the ramdisk is packed as root.

I added a check for addon.d before trying to copy it to eliminate the addon.d errors when flashing.

[MENTION=4505535]sefrcoko[/MENTION] - Thanks for the update. Kitchen test 4 below includes SuperSU v2.62-3

[MENTION=1665124]Macguyver1980[/MENTION] - Try test kitchen 4. It does not use sepolicy-inject

[MENTION=1567974]Q9Nap[/MENTION] - It is currently set to wipe the data partition on flash if you select user app support. I would consider adding a choice if you think it is neccesary. Maybe a question after you choose it like "would you like to wipe data on flash?". Not sure why you ended with a bootloop. If you figure out why and how to fix it please let me know.

v0.9.6.6-test_4

Changes:

Updated to SuperSU v2.62-3

Added a check for the addon.d directory before attemting to copy it during flash when using sparse_dat.

SuperRs_Kitchen_v0.9.6.6_test_4.zip

NOTICE: I need feedback on the test kitchen. I would realy like to merge the changes with the main branch and will do so without warning soon if I don't get any negative feedback :)
[SuperR Kitchen] Q9Nap:
I think that changing the updater script to extract /data/app to /data/app would fix the issue, but I haven't tried it.

I usually just make separate flashable files for apks I want to install.

Again, great work, very useful :good:
[SuperR Kitchen] Captain_Throwback:
Tried the boot.img tools, and that seemed to work. The set_metadata setup is still missing all of the symlinks I mentioned in my post, so I'm stuck using sparse_dat it seems.

I'll attempt a build on my A9 again shortly. That's the one with the real issues.
[SuperR Kitchen] SuperR.:
Currently if flashes /data to /data so if you have your directory structure correct /data/app will go to /data/app

Try this one:

v0.9.6.6-test_5

Changes:

Added missing metadata for [MENTION=1162986]Captain_Throwback[/MENTION] based on his post

SuperRs_Kitchen_v0.9.6.6_test_5.zip
[SuperR Kitchen] sebastiandg7:
[MENTION=5787964]SuperR.[/MENTION] there is a little error while Zipallinging. It sais it can not find "name.apk-2" (obviously)... Does it matters?

Once again: Thank you!
[SuperR Kitchen] JustZaphod:
I'm a n00b with this kitchen, my only experience is with ArchiKitchen, and I had great success with it in the past, however when I start SuperR it asks for Dependencies:

bison gperf build-essential zlib1g-dev zlib1g-dev:i386 g++-multilib libxml2-utils bzip2 libbz2-dev libbz2-1.0 libghc-bzlib-dev libsepol1-dev dpkg-dev

Installing dependencies ...

[sudo] password for justzaph:

touch: cannot touch ‘/home/justzaph/tools/depbuild’: No such file or directory

/home/justzaph/SuperR/superr: line 1541: /home/justzaph/superr: No such file or directory

I'm using Ubuntu 15-10, and I keep running into the same error each time, I have Java installed and everything else looks in order.. I have been scanning the forums, and i'm trying to figure out what I'm missing.. I'm not expecting a reply, but a little nudge and a point in the right direction and I can do the rest on my own..
[SuperR Kitchen] SuperR.:
I am not sure what is going on but another xda member had a similar problem on this thread somewhere and sorted it out.

I think you are not starting the kitchen from the correct directory. Follow the instructions in post #3.
[SuperR Kitchen] JustZaphod:
Its in the /home/user/kitchen/

./superr

Exactly where you said it should be..

Perhaps I misplaced it.. I'm a novice in the Linux Department.. Ill fiddle around until I get it right..

Edit: YES SUCCESS.. I really need to learn more about the Linux file structure...
[SuperR Kitchen] marcoperro74:
Hello everyone! First of all I congratulate to SuperR for the great work put in to create this kitchen and the excellent thread where I learned a lot ... I'm preparing to cook my first rom (or at least I try) and I have a notebook with 32-bit processor and Ubuntu 04.14 ... Can I be able to use in full the kitchen or I might get into trouble and then having to go to a 64-bit machine? Thanks for the answers ...

Inviato dal mio SM-G928F utilizzando Tapatalk
[SuperR Kitchen] SuperR.:
v0.9.6.7

Changes:

Merged kitchen test 1-5 to main branch

Updated to SuperSU v2.62-3 for systemless root on M and Samsung 5.1.1 devices.

Added a check for the addon.d directory before attempting to copy it during flash when using sparse_dat.

Added missing metadata for HTC One (M8) based on the post by [MENTION=1162986]Captain_Throwback[/MENTION].

Updated smali/baksmali/oat2dex to the latest commits.

Improved device name detection - will try ro.product.device and if it does not exist will use ro.product.name.

Fixed root and data not being added to updater-script when changing perm types.

User data is now automatically added to the rom if there is a /data directory in your project.
[SuperR Kitchen] Androidwizzard:
I don't wanna quote the whole text as the answer is - from my point of view - quite easy:

You are attempting to build a rom from a ready custom rom which makes no sense :confused:

(sparse/metadata/permissions/whatever already done in it)

All you need is a tool to unpack system.new.dat to a folder struture you wanna work on and in case - repack afterwards.

This isn't the intention of this kitchen - correct me if I'm wrong
[SuperR Kitchen] thgxda:
Hi,

well, you are correct, but my plan was to build a ROM to test if the building process works, before I do any modification to it.

My intention is, to get a working init.d, crond and sshd with CM13.0, any sugestions about it would be appreciated!

I thought I only have to modify the boot.img to get init.d working and also to get the other things I want. A modified init.rc or init.cm.rc in the ramdisk might solve my problems?

I don't have a "system.new.dat", I have my "system.img" and the unpacked "system"-directory.

I don't know.

Thanks a lot,

kind regards thgxda
[SuperR Kitchen] Androidwizzard:
CM isn't my battlefield but if you have system folder already then forget about the mentioned zip file to be extracted by the kitchen. Put boot.img, system and meta-inf in project folder and go ahead fom that.
[SuperR Kitchen] thgxda:
this is in my project folder, I think it is looking fine:

# ls -lh SuperRs_Kitchen/superr_cm13_peregrine_151215tg/
insgesamt 788M
drwxr-xr-x 3 root root 4,0K 16. Dez 11:40 00_project_files
-rw-r--r-- 1 root root 6,3M 28. Feb 2008 boot.img
-rw-r--r-- 1 root root 5,9M 16. Dez 11:42 cm-13.0-20151215-NIGHTLY-peregrine_tg.zip
-rw-r--r-- 1 root root 276M 16. Dez 00:06 cm-13.0-20151215-NIGHTLY-peregrine.zip
drwxr-xr-x 3 root root 4,0K 16. Dez 11:35 install
drwxr-xr-x 3 root root 4,0K 16. Dez 11:35 META-INF
drwxr-xr-x 16 root root 4,0K 16. Dez 11:40 system
-rw-r--r-- 1 root root 1,1G 16. Dez 11:35 system.img

And the content of the system folder also looks quite fine:

# ls -lh SuperRs_Kitchen/superr_cm13_peregrine_151215tg/system
insgesamt 1,5M
drwxr-xr-x 2 root root 4,0K 16. Dez 11:35 addon.d
drwxr-xr-x 52 root root 4,0K 16. Dez 11:35 app
drwxr-xr-x 2 root root 12K 16. Dez 11:42 bin
-rw-r--r-- 1 root root 5,3K 16. Dez 11:40 build.prop
drwxr-xr-x 15 root root 4,0K 16. Dez 11:35 etc
drwxr-xr-x 2 root root 12K 16. Dez 11:42 fonts
drwxr-xr-x 2 root root 4,0K 16. Dez 11:35 framework
drwxr-xr-x 6 root root 16K 16. Dez 11:42 lib
drwx------ 2 root root 4,0K 16. Dez 11:35 lost+found
drwxr-xr-x 3 root root 4,0K 16. Dez 11:35 media
drwxr-xr-x 41 root root 4,0K 16. Dez 11:35 priv-app
-rw-r--r-- 1 root root 1,4M 16. Dez 11:35 recovery-from-boot.p
drwxr-xr-x 3 root root 4,0K 16. Dez 11:35 tts
drwxr-xr-x 8 root root 4,0K 16. Dez 11:35 usr
drwxr-xr-x 5 root root 4,0K 16. Dez 11:35 vendor
drwxr-xr-x 2 root root 4,0K 16. Dez 11:42 xbin

And the extraction was done automaticly by the kitchen, not by me.

Am I correct that "Build full ROM Zip" should do all the work an build a complete ROM?

Thanks a lot,

regards thgxda
[SuperR Kitchen] Androidwizzard:
As I've said - not my case - someone else could jump in for details BUT

sizes irritate me:

1,1 GB system on a CM :confused:

extracted system subfolders seem much too small
[SuperR Kitchen] jazzespresso:
hey bro, nice to see you here. I could able to setup Superr kitchen, took me some time, but it looks like setup working, however, can't able to build a rom using it.

it extracts system.img and then boot.img (under superr_romname) and when I tried build ROM zip, it creates blank updater.script, plus it complains there's no META-INF folder all that...
[SuperR Kitchen] thgxda:
well looks "funny", so might be s.th. is going wrong, I'll test the "manual way again later":

# ll -h superr_cm13_peregrine_151215tg/total 788M
drwxr-xr-x 3 root root 4.0K Dec 16 15:10 00_project_files
drwxr-xr-x 3 root root 4.0K Dec 16 15:09 META-INF
-rw-r--r-- 1 root root 6.3M Feb 28 2008 boot.img
-rw-r--r-- 1 root root 276M Dec 16 00:06 cm-13.0-20151215-NIGHTLY-peregrine.zip
-rw-r--r-- 1 root root 5.9M Dec 16 15:10 cm-13.0-20151215-NIGHTLY-peregrine_tg.zip
drwxr-xr-x 3 root root 4.0K Dec 16 15:09 install
drwxr-xr-x 16 root root 4.0K Dec 16 15:10 system
-rw-r--r-- 1 root root 1.1G Dec 16 15:09 system.img

# du -h --max-depth=1 superr_cm13_peregrine_151215tg/system
6.2M	superr_cm13_peregrine_151215tg/system/tts
25M	superr_cm13_peregrine_151215tg/system/usr
12K	superr_cm13_peregrine_151215tg/system/addon.d
12M	superr_cm13_peregrine_151215tg/system/bin
63M	superr_cm13_peregrine_151215tg/system/vendor
4.0K	superr_cm13_peregrine_151215tg/system/lost+found
5.6M	superr_cm13_peregrine_151215tg/system/etc
32M	superr_cm13_peregrine_151215tg/system/fonts
18M	superr_cm13_peregrine_151215tg/system/media
72M	superr_cm13_peregrine_151215tg/system/lib
32M	superr_cm13_peregrine_151215tg/system/framework
152M	superr_cm13_peregrine_151215tg/system/app
6.9M	superr_cm13_peregrine_151215tg/system/xbin
57M	superr_cm13_peregrine_151215tg/system/priv-app
480M	superr_cm13_peregrine_151215tg/system
[SuperR Kitchen] JustZaphod:
Really? I was able to build a rom from just the System.img, and boot.img, however I had to modify the Update script and remove some lines of code, so I did not get an install error in TWRP.. and then I had to reflash the boot.img, and for the life of me.. even if everything boots fine.. Iose Wifi calling altogether.. There is likely one line that is missing completely and I have to find it.. All the DEVs I can see on the Galaxy S6 are on their Holiday Hiatus and we just got a small update so I wanted to create something for myself.. It works fine, I just lose Wifi calling..

I'll figure it out, the SuperR install was too easy I messed it up at first.. I just have to go back to the DOS days before Windows 3.1.. Oh have I missed the command line, so the Linux Terminal made me feel right at home..
[SuperR Kitchen] jazzespresso:
i don't think Superr plays nice with Samsung devices...at least my experience with this tool last couple days...
[SuperR Kitchen] Er. Aditya:
as for note 4/5 samsung devices its been awesome

havnt had a chance to test the lastest version
[SuperR Kitchen] yunuskk:
Same with my Note4 N910C

No wifi. It is disabled.

Something has to do with the kernel.

After flash Semax kernel wifi is on.

Later try to build with latest SuperR.
[SuperR Kitchen] JustZaphod:
I did, and I do have Wifi working, its the T Mobile Wifi Calling that I lose, other than that everything looks spot on..

Just rough around the edges and the updater script needs to be tweaked..
[SuperR Kitchen] SuperR.:
[MENTION=7144757]thgxda[/MENTION] - Try entering the system partition size manually instead of using adb detection. Use this number I retrieved from the cm peregrine repo for the system image size: 1157627904

Does the zip you extracted contain a system.img? If so, you will need to manually extract the system.img and the boot.img from the zip and then use the kitchen to extract the system.img.

What are you editing in the updater-script? My guess is the assert line at the top. It would be better to add the correct assert rather than deleting the assert line. The kitchen makes it easy. Just look at the error in twrp. It will tell you something like. This rom is for a "some_name". This is a "some_other_name". You want to add the "some_other_name" to the asserts and the kitchen has an option for that.

Try sparse_dat with no boot.img modification.
[SuperR Kitchen] thgxda:
Hi SuperR,

thank you very much for your answer!

I will do so later and report if I had success!

Kind regards,

thgxda
[SuperR Kitchen] jazzespresso:
It has. Here's high level what I have done and unsuccessful so far - I am not asking full-support anything, just thought maybe some others can give me some idea:

so I created folder and put Superr files under here:

cd /home/user/kitchen/

I fire up ./superr --> all good, then from menu, select option 1.

and give name t350, so it created folder called superr_t350...

and then I downloaded firmware for sm-t350 (sammobile's site), extracted, got system.img, boot.img, recover.img

and then I copied these files to under /home/user/kitchen/superr_t350/

and from superr menu, select option 4 for extract system.img

it extracts system.img, creates a folder called system and puts all extracted files in there

and then superr prompts me choose perm type, I choose set_metadata (tried set_perm), and then it fails with error:

/home/user/kitchen/superr_t350/META-INF/com/google/android: No such a file or directory

grep: updater.script: no such a file or directory

.

.

.

even go thru Build ROM option, it fails because of above error...

I was kind of under impression that superr kitchen should create META-INF folder (with update binary and creates updater.script) with all dependencies for building the ROM

At this point, all I got using this tool is extracted system.img, which i can do that easily on my windows 10 PC without going thru all these hassle (setting up Virtual Machine, installing Ubuntu..etc).

Not that I did not appreciate this useful tool, so thank you again...it is possible I may be missing something stupid simple step here....
[SuperR Kitchen] SuperR.:
It seems that something is missing, but I am not sure what. The kitchen does exactly what you thought it does. Create a full rom from system.img and boot.img including META-INF and updater-script. I am not able to reproduce the problem you are having and you are the first to have it. Not sure what is going on :(
[SuperR Kitchen] enotar:
Good for me with Samsung P600 and sparse datas but not with metadata (Still no Wifi!)

Only hip... Drive app give me hard time after boot , I think it is the Drive app deodexing so I took it of and add the app to /data/app in Rom.

Anyway anybody knows where I can edit the Samsung script that launch Drive, Evernote, Samsung login etc..... I want to boot clean without removing apps.

Thanks for 0.9.6.7
[SuperR Kitchen] :
Hmm glad you mentioned it, the n910c is exactly the same. Had to remove drive myself but there was no deodexing error on it which was strange
[SuperR Kitchen] SuperR.:
I can't fix the deodexing (if it is even broken or the thing causing the problem), but we can probably get the wifi thing for set_metadata nailed down if you post an updater-script that allows wifi to work.

The problem is almost certainly an selinux issue and you are probably missing metadata for something in the kitchen generated updater-script. If you post an updater-script that uses set_metadata and wifi works, I can find the missing pieces and add them to the kitchens metadata database. sparse_dat working perfectly while wifi is broken using set_meatadata is exactly an indication of this being the problem.

Out of curiosity, why the desire to use set_metadata? It is older, not designed for L or M roms, and clearly causes more issues in the kitchen :p
[SuperR Kitchen] :
It was by no means a criticism of your work and really hope you didn't take it that way. It was just an observation that I had the exact same issue with drive constantly popping up with a fc making it impossible to set up and there not being any deodex errors. Facebook and maps are usually the culprits for bad deodexing but you get the error logs.

For metadata I guess it's just inertia lol, it's pretty much all us Sammy guys have ever used so we are still getting used to sparse_dat that's all. People tend to be unwilling to try something new lol
[SuperR Kitchen] thgxda:
Hi SuperR,

that was working, thank you very much!

By image is building, 6 MB smaller than the original one, but this might be no a problem.

So I transfered it to my mobile, booted into TWPR and tried to install it.

Unfortunately I get an error quite at the begining:

...
[COLOR="Red"]B:Error executing updater binary in zip '/sdcard/cm-13.0-20151215-NIGHTLY-peregrine_tg.zip'[/COLOR]
Error flashing zip '/sdcard/cm-13.0-20151215-NIGHTLY-peregrine_tg.zip'
Updating partition details...

The former installation still is working, so it seems that it even does not begin to flash the device.

Any idea how to get around this?

Kind regards,

thgxda
[SuperR Kitchen] Androidwizzard:
I see you've never entered the Samsung universe - no1 who builds custom roms for Samsung devices leaves a kitchen with a ready flashable zip - on the contrary: after using the comfort of the kitchen the fun or anger begins by fixing Samsung bugs and then after hours or days you finally zip your rom in windows - sure we could return into kitchen and use sparse but I think no1 does.
[SuperR Kitchen] SuperR.:
I did not take it as criticism at all :) The kitchen is following the correct process for deodexing all apps so if there is a problem, that file just has issues for one reason or another. Issues can be reported to JesusFreke for M or testwhat for L but with no error it will be very difficult to diagnose.

I will remove the "not recommended for samsung" warning next to sparse_dat for the next release. Maybe that is the deterrent lol

You have not provided enough information. Please flash the rom again. This time, before flashing another rom or doing a restore, copy the recovery log to your sdcard from twrp menu and paste the contents at pastebin.com or similar.
[SuperR Kitchen] jazzespresso:
no worries..I guess I will figure out eventually...after going all trouble setting up virtual machine on windows 10, installing ubuntu into it, etc...not able to make this tool work going to be a shame :p

if time allows, I will start over again.. ArchiKitchen no longer maintained nor supported, so I really need get this working :D
[SuperR Kitchen] SuperR.:
Is it that obvious? lol I am trying to be as accommodating to Samsung users as possible, but this wifi problem with set_metadata is escaping me. If you or anyone else has a wifi functional metadata updater-script you would like to share with me, we might be able to sort it out :)
[SuperR Kitchen] thgxda:
I didn't reflashed an other ROM, the old one was still intact. Anyway I made an other try to get a new log.

Never used pastebin before, but seems to work:

http://pastebin.com/km87YzH1

I haven't seen anything wrong here, but I'm not experienced in this at all.

EDIT: Seems that my last log was not "that" informative, so an other one here:

http://pastebin.com/5z4DT8yy

Thank you very much,

regards thgxda
[SuperR Kitchen] SuperR.:
The problem is just the asserts. In the kitchen menu, go to ROM Tools > Asserts. At the bottom it will say "cm_peregrine". Edit the line to say "cm_peregrine,peregrine" and press enter. Build your rom again and flash.
[SuperR Kitchen] Androidwizzard:
Here I have one - not mine as I am still working on - who knows ;)
[SuperR Kitchen] thgxda:
Hi SuperR,

so in my last log, I had to wipe "Devalik and Cache" to get it, there was an error:

script aborted: This package is for "cm_peregrine" devices; this is a "peregrine".
This package is for "cm_peregrine" devices; this is a "peregrine".

I don't know from where this information came, but I created a new project and changed it to "peregrine" under "ROM Tools" - "Asserts ..." and build a new ROM, already with a slightly modified "init.cm.rc". In with that ROM I was able to install and my modification still was there :)

Small "issue" I have now, my "root"-access is gone, I can enable/disable it in the CM dev-settings, but it does not change anything. The command "su" still is available, but does not work, in the SSR-Kitchen "ROM Tools Menu" it said "Root/Unroot ROM (CURRENT: Rooted)".

I even can not install SuperSU anymore, it says that my device it not rooted.

What is the "User app support" ment for? It says that you should place your apps in ".../data/app", in what format they have to be, apk or zip? How and when they will be installed, are they visible in the app settings? Will they be removable?

Would it be possible to include SuperSU with this even in CM? Normally installing SuperSU via TWPR will result in a boot-loop with CM13, but installing it via the SuperSU-app might work.

Thanks a lot,

kind regards,

thgxda
[SuperR Kitchen] SuperR.:
You can try to root with the kitchen. You would need to let the kitchen remove root and then add it again. Oh, and Chainfire says it will break things if you let TWRP add root when it says it is not rooted. So don't do that. This goes for all M and Samsung 5.1.1 devices using systemless root.
[SuperR Kitchen] Androidwizzard:
Congrats, you ruined a working CM 13 rom which has root enabled by default - did you add root through kitchen?

If yes, why? Maybe some1 could enlighten where this is going to :confused:

At the end some1 will build the CM for your device instead? [MENTION=5787964]SuperR.[/MENTION] you maybe? ;) I admire your patience :highfive:
[SuperR Kitchen] yunuskk:
Ok will try.

if no boot.img modification how to get init.d support.

I always remove the assert line on updater script. If not error executing binary or something like that.
[SuperR Kitchen] papampi:
Thnx a lot for your awesome tool,

I made a deodexed debloated deknoxed custom (app,framework and priv-app) zip for my galaxy tab s2 T815 every thing goes without any errors

Flashing the custom zip gives no error as well

But It does not deodex it and when I try to install xposed for Samsung deodexed by arter97 from this post TWRP gives error that rom is not deodexed.

Does the flash updater script clean the system/app,framework and priv-app ?

Or I should add any thing to the file? Or do anything before flash?

Any helps would be much appreciated