yashsingh1/xdaforums huggingface dataset:
[SuperR Kitchen] AndroidGX:
It's the stock generated updater-script generated by your kitchen, nothing modified :good: (but when I go to build tools : "There is no ROM to work on.")

Btw, I just tested your latest 0.9.7.3 and now it' s getting worse here :( :

- if I press 1) : "This ROM is NOT KitKat or beyond." ----> isn't Marshmallow beyond kitkat ? :p (this selection was working in previous version btw)

- if I press 3) : "This ROM is NOT Lollipop+ or you are running 32bit Linux." ----> here also, marshmallow is much over lollipop and I'm usng Ubuntu 64bits (this selection was working in previous version btw)

- if I press 4) : it brings back to home menu without doing anything, and system.img is not extracted at all.

so the only solution if 2) which is of course not recommanded for marshmallow (set_perm).

:(
[SuperR Kitchen] enotar:
No root with latest 0.9.7.3

Metadata and busybox installed

Something is missing in Updater script
[SuperR Kitchen] SuperR.:
I suggest starting with a fresh kitchen (delete the old one and reclone or unzip a fresh one). Delete the 00_project_files directory and everything but the original rom source, then extract whatever you are starting with again from the kitchen main menu.

That does not provide any info. Paste the updater-script at the very least. Root has not changed in the newest version, but it is possible the new busybox changes affect it somehow.

To everyone...I did say the latest version was experimental :p

EDIT:

v0.9.7.4

Changes:

Many bug fixes for raw_img, changing perms, and busybox that were introduced in the last version.

Set_perm and set_metadata no longer format /data when user apps are enabled (still working on sparse_dat and raw_img options)

I have tested everything other than flashing a rom to a device (no more time). Everything should be working much better now. Keep in mind, the Busybox installer is still completely untested in the Kitchen as far as I know so I need feedback. Thanks
[SuperR Kitchen] enotar:
Updater script uploaded for no root.

Another thing, I tried putting apps in Data/app before creating the zip, after creating the zip and that never works. The Rom dont flash anymore when doing one or the other. Message display about metadata issues. Before putting apps the rom was flashing and booting fine
[SuperR Kitchen] SuperR.:
Try v0.9.7.4. You are experiencing some of the bugs that should now be fixed.
[SuperR Kitchen] enotar:
Still no root at all
[SuperR Kitchen] SuperR.:
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)

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.

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.

Beyond that, I don't even know if the new SuperSU works for your device. 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.
[SuperR Kitchen] AndroidGX:
Already tried 4 times, but same problem :crying:

I tried your recent 0.9.7.4, but I'm facing same problem as my previous post.

I tried to start from whole new zip but same problem as before then.

Strangely when I updated from your v0.9.7.3, I was able to get back set_metadata and sparse dat methods.
[SuperR Kitchen] enotar:
I am on 0.9.7.4 and I flash supersu 2.64 beta with twrp and it works well.

I think busybox is the issue. I will try recreate the rom avoiding busybox for now. Keep you posted and if still no root I will post new updater script.

But I am suprise on busybox instalation messing root install...

Maybe it would be better to install busybox first and root after...Not sure.
[SuperR Kitchen] SuperR.:
There were many ugly bugs on 0.9.7.3 so it is not strange that 0.9.7.4 fixed some problems. If you are still having problems with specific firmware, send me a link to the source you are starting with and I will have a look. Please, no registration required links :)

The new Busybox installer by [MENTION=4544860]osm0sis[/MENTION] needs to detect the root method so it must be done after root.
[SuperR Kitchen] AndroidGX:
Thank you for your help, appreciated :good:

Here is the firmware folder source I'm trying to make a rom from.

or direct links :

system.img (ziped so you'll have to extract it)

boot.img

modem.img (not necessary)

Stay me tuned when you can please :highfive:

Cheers'

AGX
[SuperR Kitchen] SuperR.:
Everything seems as it should. In the kitchen, I created a new project called "lg". I downloaded the zip and the boot.img to /kitchen/superr_lg directory. I extracted the system.img from the zip manually into the same directory. In the kitchen, I chose "Extract for new ROM" and selected "system.img". I did not get any errors and the resulting updater-script is pasted here.

http://hastebin.com/qiwunehaqe.coffee

edit: Forgot to mention that when asked, I chose get by-name from boot.img. No problems there either as you can see in the updater-script.
[SuperR Kitchen] Captain_Throwback:
[MENTION=5787964]SuperR.[/MENTION]

http://xdaforums.com/showthread.php?p=64443574
[SuperR Kitchen] dkionline:
I cant see SuperSU extraction zip on on this script. But it should work properly with latest updates.

Maybe u should try the direct method and unpack SuperSU to system and set symlinks to updater script.
[SuperR Kitchen] SuperR.:
Thanks for the heads up :)

I did not add root to the G4 rom, just extracted it. I did add root after reading your post and it worked without issue. I am not able to flash it since I don't have the device but the updater-script looks correct.

v0.9.7.5

Changes:

New feature - Extract a zip that contains system.img, boot.img, and vendor.img and continue with system.img extraction.

Removed another duplicate entry from metadata-data.

Updated to latest Busybox installer by [MENTION=4544860]osm0sis[/MENTION].
[SuperR Kitchen] enotar:
Still no root even without busybox. Will post the updater script later
[SuperR Kitchen] Captain_Throwback:
[MENTION=5787964]SuperR.[/MENTION]

I seem to be having an issue with the boot.img on one of my Lollipop ROMs. The previous update you made to unpack as root worked for one of my Marshmallow boot images, but on two others (one Marshmallow, one Lollipop), the unpacking/modifying of the boot image has resulted in my builds booting, but being stuck indefinitely at the end of the boot animation.

Replacing the boot.img in the ROM zip with a stock, untouched one, or one unpacked normally with Android Image Kitchen allows the boot to fully initialize and complete. I'm not exactly sure what you can do about that besides make unpacking the boot image as root a menu option? That way it only needs to be used if the "standard" way causes an issue?

Also, I just built a zip using a combination of sparse dat for system and set_metadata for /data, and it worked okay. So maybe that can be an option at some point as well.

I've found that I often need to make some minor adjustments to the zip and updater-script after the Kitchen finishes the build. For example, I need /data support, but not /data/app, as I have a "preload" folder that gets included on stock ROM flashes. I have to add the metadata for this manually, but if I do it before building, it gets erased by the build. Additionally, I remove any lines from the updater-script that mount or unmount /data, because on devices that use emulated storage, /data will always be mounted (at least in TWRP, which is the preferred custom recovery for my devices). But after figuring out the boot.img thing, most of my device builds are going well. I have to try out the one that wasn't booting for me before and see if that one works now too. I'll also try to test the one where sparse_dat was getting stuck on the flash and report back.

P.S. Since the new busybox method was added, none of my finished zips have included a busybox folder, even though it's there in my working folder - I've had to add it manually.
[SuperR Kitchen] SuperR.:
There is definitely something wrong. 11MB is way too small, but system.patch.dat is supposed to be 0 bytes and is unrelated to the issue you are having.

Does it create the system_new.img first? Are there any errors during dat creation if you scroll up in your terminal?

edit: system.new.dat is the actual system image and it should be fairly large
[SuperR Kitchen] not-i:
So with my Moto X files I have successfully unpacked, deodexed, done some minor mods and its repacked system_new.img and its the same size as original system/img so looks promising.

I'm guessing now I "created rom zip" and thats when system.new.dat is created?
[SuperR Kitchen] SuperR.:
If you are trying to create a sparse dat rom, there is no need to build system.img first. Simply choose sparse dat when extracting or use the change perms menu option to choose it, then build full rom zip. If you are wanting just the system.img, then choose the build system.img option.
[SuperR Kitchen] SuperR.:
Is there a custom recovery (cwm, twrp, philz) for your device? If so, please post a link to it. Thanks
[SuperR Kitchen] SuperR.:
I think this might solve your problem

http://xdaforums.com/showpost.php?p=58637219&postcount=128
[SuperR Kitchen] ferbulous:
The rom itself was quite clean, almost zero bloatware there.

---------- Post added at 02:29 AM ---------- Previous post was at 02:27 AM ----------

For the Boot Tools menu

2) Build boot flashable <-- Do I have to setup anything for this, or could I just skip this and build the deodexed zip right away?
[SuperR Kitchen] bcrichster:
No carrier branded bloat?
[SuperR Kitchen] nghia0423:
Ok now I am trying for a different device. I downloaded 5.1.1 for SM-J700F and I was going to try the sparse dat method again and not it says "This rom is not lollipop or beyond.
[SuperR Kitchen] SuperR.:
Sounds like your build.prop either reports the rom as less than Lollipop or the build.prop line is different than all others I have ever seen. Please post it so I can take a look.

Did you install the package I linked above?
[SuperR Kitchen] SuperR.:
If you want to build a flashable boot.img, you should build boot flashable. If you want to build a full rom, you should build a full rom. If you want to build a flashable zip with deodexed files you should choose build custom and choose the option you want.
[SuperR Kitchen] ferbulous:
I took the first option (build full rom zip) after deodexing.

Is it good enough or do I still need to select specific custom zip to build?
[SuperR Kitchen] SuperR.:
It depends on what you want to end up with. If you only want the full rom zip then full rom is good. If you want more zips with different contents, make more :)
[SuperR Kitchen] nghia0423:
Edit: The prop says it is 5.1.1

https://mega.nz/#!GURQQADK!ujhHvu1XJ7F9BNz8cgBSclKMGilcP6fYLetub82zLzU
[SuperR Kitchen] SuperR.:
This is the line we are looking for:

ro.build.version.sdk=22

and it says it is Lollipop for sure. I am not sure why it is telling you that. Are you sure you are working on the correct project?
[SuperR Kitchen] Q9Nap:
How did you unpack the moto x system image with this kitchen?

I just tested the moto x vzw 5.1 system image with no luck.

Many moto firmwares use an encrypted sparse format (MOTO.W›.MOT_PIV256).

I am able to use imgextractor (windows) to dump the image and list of symlinks, as well as get image info, but I haven't found any linux utilities that can handle this format.
[SuperR Kitchen] Androidwizzard:
At one point I got to plug-in my device - so far, so clear, but what if I make a rom for a device I don't have :confused: ;)
[SuperR Kitchen] SuperR.:
You only need to plug in your device if you are ripping the img's from it. Normally you can get the by-name info from a boot.img. If the device does not use by-name you will need to create an mmc file and still don't need to plug in the device.
[SuperR Kitchen] Jamie_Bowen:
fyi

ok well then, for the record....

the program does not like functioning with a linux emulator :)
[SuperR Kitchen] SuperR.:
v0.9.0.2

Changes:

When entering Boot/Recovery Tools, recovery no longer takes precedence. You will be presented with a choice of which to work on if boot.img and recovery.img both exist in the project directory.
[SuperR Kitchen] SuperR.:
The kitchen should only be repacking as root if it is an M boot.img so I am not sure what is going on with the L boot.img. You could try removing the sudo and see how it goes on all M roms. I was told it is not needed and just the -R 0.0 is needed so you could give it a shot. Sadly, I don't have an M device to test on. If you want to try it without, do the following:

In main kitchen directory, open the superr file in gedit or other Linux text editor. Assuming you are using v0.9.7.6 (the new version mentioned below), look for lines 247 and 273. Change the beginning of the line from this:

( find . | sudo cpio -o -H

To this:

( find . | cpio -o -H

Save the file and restart the kitchen. Let me know how it goes :)

I am planning to ask which you want when adding user data support. I think I might remove the auto-add of user app if /data exists. It will be too complicated to have both.

If you add your custom metadata above the #PERM placeholder it will not get removed unless you change perm types. Then it will all get removed.

My bad here. Sorry about that. I guess it would help to have the zip in the rom if we are trying to use it :eek:

v0.9.7.6

Changes:

Fixed busybox not being added to the rom zip.
[SuperR Kitchen] enotar:
No Root

Updater Script

0.9.7.5

Samsung Device

No busybox selected

Kitchen don’t root anymore
[SuperR Kitchen] SuperR.:
I don't see anything wrong with your updater-script. Try v0.9.7.2 again and see if the problem persists. If it works, then compare the updater-scripts to see if there is a difference.

Any other Samsung users care to chime in? Anyone else having root issues in the latest release?
[SuperR Kitchen] C y a n i d e ~:
This package is for problem

0.9.7.4

Zorin OS Ubuntu Based

Alcatel Flash 2

ADB Pull

5.1.1 L

sparse_dat

Added init.d support, insecure boot.img, deodexed rom, debloated

No errors, it compiled succesfully

TWRP can't flash the ZIP, and it's giving me E:error executing updater binary blah blah.

Edit:

I fixed the package error by editing the assert in kitchen now twrp is giving me this:
[SuperR Kitchen] SuperR.:
Take a look at post #4. Just updated it to include your 2 errors :)

v0.9.7.7

Changes:

User app support is no longer automatically added when /data dir exists.

Removing user app support no longer deletes /data from your project.

Deleting the /data directory from your project manually will remove user app support.

If you enable user app support and are using sparse_dat or raw_img, you will now be asked if you want to use set_metadata or the current perm type for data.

The status indicator for user app support now shows what perm type it is using.
[SuperR Kitchen] AndroidGX:
Thanks for testing it, but what I would like working is by set_metadata method, and not having a system.img.

Can you please try with "set_metadata" method and "Build full ROM Zip", you will see that the final zip stucks at ~350MB and nothing happened next.

Btw, about your previous test with raw system.img, where did you grabbed your updater-script ? because mine is very poor content and no symlinks nor permissions on it.

Cheers' :good:
[SuperR Kitchen] dkionline:
Data app should be activated everytime without data.img if u want a custom app inside your rom. [MENTION=5787964]SuperR.[/MENTION] would u change the script to deodex a little faster?
[SuperR Kitchen] shoey63:
There is nothing wrong with the deodex script, get a faster PC.

Flashing images only requires one or two lines in the the updater script - no symlinks or permissions required.

But seriously guys, can you hold back on the feature requests? SuperR is not your xda slave. If you can come up with a better way of doing things, send a pull request to his repo. Or alternatively give him a decent donation as compensation for the extra time you are asking him to put into his project.
[SuperR Kitchen] Leavard:
I ran the deodexing script on my bioinformatics workstation today (12 core cpu, 24Gb RAM) and it still takes a while, mostly due to the fact that it is moving around a huge amount of data. It is not a processing speed or script efficiency problem.

Go and have a cup of tea while it runs.

Or get a SSD.
[SuperR Kitchen] Captain_Throwback:
[MENTION=5787964]SuperR.[/MENTION]

I noticed an inconsistency with one of the metadata perms I asked you to add to the kitchen:

set_metadata("/system/bin/qmi-framework-tests/qmi_test_mt_client_init_instance", "uid", 0, "gid", 2000, "mode", 0755, "capabilities", 0x0, "selabel", "#CONTEXT");

That appears in file_centexts like this (which might not be getting detected because of the period):

/system/bin/qmi-framework-tests/qmi_test.* u:object_r:qmi_test_service_exec:s0

Is there a way to make those lines match up?

If not, that line can probably just be removed, as I doubt it's going to completely break anything, but thought I'd mention it in case there is a way for them to be matched. Thanks again for all your work on this - it's really a great tool and is almost to the point where I don't have to edit anything to build a fully complete and working ROM! :)

---------- Post added at 08:39 AM ---------- Previous post was at 08:37 AM ----------

One more thing -

Can you add a blank ui_print(" "); in the Installing SuperSU and Busybox sections (for consistency)? I noticed those are the only two portions without an extra line, so it gets crowded in the recovery console during the flash ;).
[SuperR Kitchen] enotar:
I retry with 0.9.7.7 and still no root

Another thing data/app instalation still does not work and trying to add anything in this folder make the rom not flashable, script cannot execute updater binary.
[SuperR Kitchen] dkionline:
Then i try with 1 more gig in Virtualbox. Archikitchen goes faster i dont know.
[SuperR Kitchen] SuperR.:
Fixed in the version posted below :)

The problem is that there were 2 files that were not readable so zipping the rom would hang. I added a check for this and chmod the problem files to 400 so the build can finish.

The updater-script I posted was with set_metadata. You are using sparse_dat which includes the symlinks and metadata in the images so they are not in the updater-script. Just change perm type to set_metadata to get the updater-script I posted.

Done :)

If you are not going to do what I suggested I am not sure how to help.

Feel free to use Archi Kitchen :)

v0.9.7.8

Changes:

Removed /system/bin/qmi-framework-tests/qmi_test_mt_client_init_instance from metadata.

Fixed rom build hanging if there are non-readable files in the rom.

Added blank ui_print line after busybox and supersu headers.
[SuperR Kitchen] bigrammy:
Massive respect to you bro :highfive:

Totally amazing what you have accomplished :cool:

You also have the patience of a saint :laugh:
[SuperR Kitchen] AndroidGX:
Good job, and thanks for your patience, very appreciated! :highfive:

Zip now finishes correctly, but when I'm trying to flash it, there is an error in the generated updater-script, here is it when trying to flash:

E:Error executing updater binary in zip '/sdcard...........xxxxx.zip'
Error flashing zip '/sdcard...........xxxxx.zip'

:crying: :highfive:

fixed by replacing auto detected in boot.Img : "/dev/block/platform/soc.0/f9824900.sdhci/by-name/system"

by /dev/block/platform/by-name/system

Thanks you very much for your efforts, appreciated!

Merry christmas :)
[SuperR Kitchen] C y a n i d e ~:
Thank you so much SuperR for the fast response! :good:

But I don't know what partition you are referring to in that solution.

sorry I'm just a beginner.
[SuperR Kitchen] SuperR.:
You need the correct partition size for ALL partitions you are creating sparse dat images for. The kitchen will ask for each one that is included in your rom when you choose to build the full rom zip.
[SuperR Kitchen] travis82:
more debloating for you

system/app/WhatsApp*

system/app/Maps*

system/app/Flipboard*

system/app/FlipboardBriefing*

system/app/FBAppManager*

system/app/FBInstagram_stub*

system/app/FBMessenger_stub*

system/app/FBPagesManager_stub*

system/app/Evernote*

system/app/Dropbox*

system/app/Chrome*
[SuperR Kitchen] C y a n i d e ~:
Thanks! :good:, I managed to successfully flash the rom through recovery but was stuck in a bootloop :(

and is it also normal that I get an error on unpacking recovery.img?
[SuperR Kitchen] bcrichster:
I think Chrome is already on that list, but I'd truly leave Maps alone.. [emoji6]

But... YOU can personally add those apps to the Bloat list in SuperR Kitchen on ur PC
[SuperR Kitchen] travis82:
you can get google maps from the play store and no google chrome was still there after debloat.
[SuperR Kitchen] bcrichster:
With all due respect, there's ppl that actually WANT maps without extra downloads but you can just make yourself a custom bloat list within the kitchen so that SuperR's Kitchen doesn't screw anyone else over just because of your specific preference. That's WHY he made the Custom Bloat list. Good idea to make use of it instead of jipping everyone else that may wanna keep it. There's things on the debloat list I like to keep, so I just edit my debloat list instead of making SuperR change it

Chrome browser in the debloat list is labeled as "Chrome with browser".. Is it written as something else in ur system/priv-app?
[SuperR Kitchen] jazzespresso:
boot.img

A quick question related to boot.img:

After unpack, it unpacks the boot.img, and then, you are in Boot / Recovery Tools Menu

from there, we have 4 options;

1. Pack boot img, delete ramdisk

2. Pack boot img, keep ramdisk

3. Add/Remove int.d support (Current: yes)

4. Insecure/Secure boot.img (Current: Yes)

Of course, idea here is making boot.img (kernel) insecure so that it can be rootable using superSU. so I choose option 4, and made it insecure.

Now, when I need to re-pack my insecure, int.d supported boot img, should I pick option 1 (delete ramdisk) or option 2 (keep ramdisk)?

what would be the recommendation here?

Bunch of thanks!
[SuperR Kitchen] SuperR.:
[MENTION=5297774]bcrichster[/MENTION] is correct. You should add anything you want removed to the bloat_custom file instead of the main bloat file. If you want everything debloated with one menu entry, copy all lines from the bloat file to the bloat_custom file and add your lines to it. Then just use the custom debloat option in the kitchen. FYI, your list can be condensed to the following and still get the same result:

system/app/WhatsApp*
system/app/Maps*
system/app/Flipboard*
system/app/FB*
system/app/Evernote*
system/app/Dropbox*
system/app/Chrome*

There could be many reasons you get a bootloop after flashing. It is not normal to get an error when unpacking recovery.img. If you want further support, read post #4 and answer as many of the blue questions as possible. Particularly the link to the firmware you are starting with will be helpful.

It really depends on your preference. If you plan to make further edits you can keep the ramdisk for your your convenience. Otherewise, deleting the ramdisk is fine.
[SuperR Kitchen] jazzespresso:
thanks. I will go with option 2 then, just in case if I need to do further edit, since keeping it has no harm too.

also updating SuperRs_Kitchen_v0.9.7.7.zip to SuperRs_Kitchen_v0.9.7.8.zip, I just need to delete all my folder SuperRs_Kitchen_v0.9.7.7 stuff, and unpack SuperRs_Kitchen_v0.9.7.8..right?
[SuperR Kitchen] fhem:
FYI