yashsingh1/xdaforums huggingface dataset:
[SuperR Kitchen] DarkHeart Z:
here is the fastboot getvar all output :

(bootloader) max-download-size: 0x8000000

(bootloader) partition-size:metadata: 2000000

(bootloader) partition-type:metadata: raw data

(bootloader) partition-size:userdata: 17c000000

(bootloader) partition-type:userdata: ext4

(bootloader) partition-size:cache: 8000000

(bootloader) partition-type:cache: ext4

(bootloader) partition-size:system: 3e800000

(bootloader) partition-type:system: ext4

(bootloader) partition-size:expdb: 1060000

(bootloader) partition-type:expdb: raw data

(bootloader) partition-size: oem: 4000000

(bootloader) partition-type: oem: ext4

(bootloader) partition-size:logo: 800000

(bootloader) partition-type:logo : raw data

(bootloader) partition-size: para: 80000

(bootloader) partition-type: para: raw data

(bootloader) partition-size:secro: 600000

(bootloader) partition-type: secro: ext4

(bootloader) partition-size:recovery: a00000

(bootloader) partition-type:recovery: raw data

(bootloader) partition-size:boot: a00000

(bootloader) partition-type:boot: raw data

(bootloader) partition-size:bootloader: 60000

(bootloader) partition-type:bootloader: raw data

(bootloader) partition-size:seccfg: 40000

(bootloader) partition-type:seccfg: raw data

(bootloader) partition-size : protect2: a00000

(bootloader) partition-type : protect2: ext4

(bootloader) partition-size: protect1: a00000

(bootloader) partition-type: protect1: ext4

(bootloader) partition-size:nvram: 500000

(bootloader) partition-type:nvram: raw data

(bootloader) partition-size: proinfo: 300000

(bootloader) partition-type: proinfo: raw data

(bootloader) partition-size: preloader: 40000

(bootloader) partition-type: preloader: raw data

(bootloader) off-mode-charge: 1

(bootloader) warranty: yes

(bootloader) unlocked: no

(bootloader) secure: yes

(bootloader) version-baseband: MOLY

(bootloader) kernel: lk

(bootloader) product: Roar_A50

(bootloader) para-image-model: Roar_A50

(bootloader) para-image-date: 2014/12/21 12:19:29

(bootloader) version-preloader: 0.1.03

(bootloader) version-bootloader: 0.6.7

Even fastboot readouts said it's ext4 then why can't it be get extracted with ext4 utils ? :(
[SuperR Kitchen] bigrammy:
Device Specific

Ok since it seems SuperR is too polite to tell people on this thread some home truths so I will run the risk of saying it for him :o

First he is not here to solve everyone's problems for them!!!!

Some of you guys posting device specific stuff should know better as you are far from noobs :crying:

He has made a kitchen which does what it says on the tin. If you have a Sony or any other device and the tools don't unpack the boot.img userdata.img etc etc etc then research why!!!

Do not ask him to solve it for you :rolleyes:

When you have found how why and a solution then kindly ask if it can be incorporated into the Kitchen.... :silly:

I Have seen many great dev's like superR just simply give up because of people like these demanding stuff or saying it's crap because it doesn't work for their device!!!!

For the 1000th time xda DEVS is a DEV'S site and not a shop for people who want free stuff.
[SuperR Kitchen] shoey63:
+1

Also, userdata.img is totally unnecessary to be included. A full wipe of /data in recovery, and everything will be as it should on reboot.
[SuperR Kitchen] Er. Aditya:
hey bro i just tested latest kitchen and got the same issue of zipligning if i manually download kitchen and unpack in home folder , but somehow it went away when i cloned if directly

dont know what might have gone wrong
[SuperR Kitchen] tirta.agung:
Perhaps you can tune in to this post
[SuperR Kitchen] suku_patel_22:
[MENTION=718594]super[/MENTION]R Would it be possible to add an option to inject kcal color calibration values to the ramdisk, so that it can be applied on a system without root?
[SuperR Kitchen] dkionline:
No, this is device specific.

In most time, System + kernel is enough for a Rom.

Guys, kitchen should do only Settings there all devices can do. So only img and ext4, for the rest there are Tools to handle with it, please use them rather than write questions here.
[SuperR Kitchen] f1ux:
OK noob alert. Hope noone bites my head off :/

Trying to rebuild a rom but not having much luck.

METADATA MODE= flashes but wifi cant get IP

Sparse mode > Use ADB to find partition sizes > = zip only doesn't contain system files and is only 12mb

Sparse mode > Use directory =

When flashing>

Failed to open /dev/block/bootdevice/by-name/userdata/system

Error executing updater binary in zip

Forgive me if it's an obvious fix but i am still learning!

OS: Ubuntu 15.10

Device: Vodafone (ZTE) Smart ultra 6

Source: Rom update zip

Android 5.1.1

I get the same error before and after debloating the rom

Original ROM file :http://download.ztedevice.com/UpLoadFiles/product/552/5825/soft/2015112413504851.zip
[SuperR Kitchen] SuperR.:
v0.9.6.0

Changes:

Added silent rename of system.img.ext4 and system.ext4 to system.img.

Added ability to get by-name directory and file_contexts from kernel.elf.

Merged changes from [MENTION=753984]xpirit[/MENTION] for sdat2img.py to allow for M dat extraction.

NOTE: In order to get the by-name and file_contexts from kernel.elf, it must be named exactly kernel.elf. This should save you the step of renaming to boot.img and lets the kitchen know how to handle the file. For those of you who have no idea what I am talking about, it probably does not apply to you :)
[SuperR Kitchen] f1ux:
Just to add to my previous post up there ^^

I realised that the kitchen seems to think it should be

/dev/block/bootdevice/by-name/userdata/system

instead of

/dev/block/bootdevice/by-name/system

If i manually edit the updater-script after build and remove the userdata, it seems to flash.

I deleted the device profile from the device folder to start fresh.

Made a new project, put in my stock update.zip, unpack and a profile reappears with /dev/block/bootdevice/by-name/userdata/system again.

When i choose sparse build type my only option to look for partition is

1) Device through adb shell (recommended)

2) Project system directory (BETA)

3) Enter manually

*confused!
[SuperR Kitchen] hohassan444:
[MENTION=5787964]SuperR.[/MENTION]..please i have problem in unpacking boot.img , though it is unpacked without problem with CarlivImageKitchen ( using option 1 ).
[SuperR Kitchen] SuperR.:
I found the problem with your by-name and have fixed it locally. You can easily fix it until I push another update by manually editing /kitchen/tools/devices/msm8916_32/superr_byname as follows:

Change this:

\/dev\/block\/bootdevice\/by-name\/userdata

To this:

\/dev\/block\/bootdevice\/by-name

When I extracted the update.zip included in the zip you posted, all the by-name stuff was correct in the resulting updater-script but the by-name file was wrong. I suggest you modify the file above, delete the 00_project_files directory, and extract the update.zip again.

Please send your build.prop, thanks

Never mind. The new version should sort you out.
[SuperR Kitchen] SuperR.:
v0.9.6.1

Changes:

Bug fix - If system.ext4 and system.ext4.tar exist in your project dir the tar would show up twice.

Bug fix - When extracting a ROM zip, if the original updater-script mounted /data before /system the by-name detection would be incorrect.

Bug fix - Properly handle MTK devices that contain the MTK magic but still need to be unpacked the traditional way.

Improved checks for ramdisk compression types.

v0.9.6.2

Changes:

Fixed the kernel.elf by-name detection that just broke in the last version.
[SuperR Kitchen] Koognod:
[MENTION=5787964]SuperR.[/MENTION] Hey there have a quick question for the time being. Just wondering if you might be able to help me figure something out. For some reason the rom I've created is having issues connecting to wifi calling. It's a metro pcs device so it's practically the same as a t-mobile device (they run on the same network).I don't have a whole lot of information lined up for you here right now I'm working on getting it all together suffice to say I've pulled a lot of stuff from the rom other than what your kitchen pulled automatically as far as bloatware and I may have pulled a necessary component for this to work properly(Although I tried to be very careful believe me). So anyway from what I've read wifi calling should have been in the stock rom connection settings. It's been a while since I used the stock so I am having someone confirm for me that this is in fact in the base rom I started out with(I'm pretty sure it is). However I am not seeing a spot for it anywhere in the settings menu in the baked rom. I also have left the "wifi calling settings" apk in the rom, because as far as I could tell this was all that was needed(please correct me if you know otherwise)Did you by chance use a different settings menu than stock? Or Could you think of anything that the kitchen could have pulled considering it bloatware that might have affected this? Any help you could provide or maybe if even [MENTION=4899305]ashyx[/MENTION] could lend a hand once again I would greatly appreciate it as usual.

This is the Window I am looking for
[SuperR Kitchen] bigrammy:
When your done with superR do you think you could send him around to my place so he can cook me a dinner, fit a new hallway carpet and fix my rattling exhaust on the car I am sure he won't mind. Cheers :rolleyes:
[SuperR Kitchen] Koognod:
Sorry if I'm overstepping my boundaries, or squashing anybody's toes. I wasn't trying to offend anyone, I was serious when I said I appreciated any help I could get. The only reason I had posted here was because Superr. and Ashyx had been so awesome to help me with a previous issue regarding my rom I had used this kitchen to build. I didn't think the two questions I had asked were all that crazy either, just could use a little help was all. Sorry if it seemed I was being rude. I thought this tool was supposed to be noob friendly I must have made a mistake in assuming the thread would follow along the same lines.
[SuperR Kitchen] bigrammy:
Are you really so naive :confused:

Can you imagine the size of this thread if superR even thought to respond to such requests and how OT it would become in a matter of hours :eek:

You're not such a noob as you claim because you seem to have your "donate button" all set up nicely :laugh:

I find google search and researching things helpful and if you can't solve it ask here http://xdaforums.com/general/help maybe someone can help you there.

PS: a quick search found this T-Mobile Wifi calling thread
[SuperR Kitchen] Koognod:
My request really didn't need a large in depth answer a yes or no would have been fine perhaps another sentence at the most. It certainly would have taken up less space if you didn't have to go and make such a big deal about it. Also, I don't see how my questions would be better in a general questions thread when they were specifically regarding superr. 's Kitchen and how it does what it does. Lastly I don't see how setting up a paypal and dropping the link into my profile settings qualifies me as any sort of professional, it's not like I had to figure out the code or something and even if I had what does that have to do with the device at hand (android).

Ps Trust, it's not like I haven't been putting in my fair share of the work, I have seen and read through the article you have posted along with quite a few others. I was just asking to see if someone more qualified then me would be willing to throw a dog a bone. I thought maybe I was making it more difficult than it needed to be or maybe there was just an easy answer I was missing. I was just looking for a hand up not a beatdown.
[SuperR Kitchen] ziddey:
I scratched my head on this one for a bit. http://xdaforums.com/showpost.php?p=64107936&postcount=6
[SuperR Kitchen] shoey63:
MM kernels need to be unpacked and repacked AS ROOT to accommodate the rwx permissions on some of the files in the stock ramdisk. I use linux AIK by [MENTION=4544860]osm0sis[/MENTION] and don't have issues.

Edit: fstab has to have "verify " removed from /system line as well as a patched sepolicy.
[SuperR Kitchen] SamuriHL:
OHHHHH nice.
[SuperR Kitchen] SuperR.:
v0.9.6.3

Changes:

Added more error checking for unpacking boot.img.

Fixed unpack/repack taking you to the wrong place when finished.

Added support for removing verify from /system when rooting M roms.

Added sudo command when unpacking and repacking ramdisk on M roms.

NOTE: I need someone to test root on an M rom that is not samsung. Let me know how it goes :)
[SuperR Kitchen] Er. Aditya:
does root work for 5.1.1 sd varients now ?? on stock kernel ??
[SuperR Kitchen] Rydah:
is there a way to disable asserts completely? I know I can edit the script and remove it but I'd like to be able to turn it on/off. Also, not sure why but when I build my rom, it adds updater-script~ also. Any clues as to why?

Thanks
[SuperR Kitchen] SuperR.:
No clue. Someone with one of those devices will need to answer. The only root stuff I changed in v0.9.6.3 is for 6.x devices.

I am not sure why you get an extra file. Maybe some system backup setting when files are edited? In any case, the extra file should not cause problems.

Regarding removing asserts, for now you will need to remove them manually. It is not safe practice to flash roms without asserts and I am afraid that making this option available will result in bricked devices. If every device used by-name it would be much safer, but we are not there yet.
[SuperR Kitchen] Rydah:
Ahh, so sorry, you are correct. Gedit editor was saving backup files. And for asserts, I guess manually removing them is fine. I'm having issues with my rom not flashing, it says error 7. I thought this was due to asserts, mind checking out my log?

Thanks for all you do. This kitchen is simple and has all features needed.
[SuperR Kitchen] bigrammy:
Just to confirm that it's the text editor backup file updater-script~ I used to get them when I used Zorin OS (ubuntu)

You can safely delete them and they seem to get removed automatically when you shut down unless they are included in a .zip or .img in which case they seem to remain for obvious reasons.

Other examples will be build.prop and build.prop~ among others.

As superR says they do not seem to affect the rom other than it been a little untidy. ;)

Edit: you already replied above I guess I should've hit my refresh button LOL
[SuperR Kitchen] Rydah:
Yup, my post above confirmed that it was my editor making a "safe" backup. I don't know why my zip won't flash (it previously did) and I noticed that the updater-script~ was new since my last build and had old assert info it. Hoping removing the backup file fixes the flash issue otherwise, I'm lost. Lol my log is in my post above if you wanna take a look. TWRP is reporting error #7

Sent From My LG V10
[SuperR Kitchen] SuperR.:
Looks like you modified your updater-script so I will not be able to help with it. Here is the relevant part from your 6.8MB recovery.log. Hope you get it sorted :)

http://hastebin.com/zetacaribe.vhdl
[SuperR Kitchen] bigrammy:
Yes Sorry you must of posted as I replied :laugh:

I should of hit refresh first :o
[SuperR Kitchen] SamuriHL:
Thank you, sir! Much appreciated. I'll not get to try it out til tomorrow but I will definitely do so on my Nexus 6 boot img.
[SuperR Kitchen] tirta.agung:
Hi SuperR, here is some solutions on how to extract >=5.1.1 roms that use CM's Transparent Compression V.2 by default.
[SuperR Kitchen] SuperR.:
Since this is not a kitchen issue but does affect some kitchen users, I suggest you post a "how-to" in this thread or somewhere else and I will link to it in post #4 :)
[SuperR Kitchen] bcrichster:
that's phenominal work!! I hope [MENTION=5787964]SuperR.[/MENTION] can use the info as well, looks very promising!

---------- Post added at 01:39 PM ---------- Previous post was at 01:33 PM ----------

this isn't something that can be automated into the kitchen? I ask cuz I'm just clueless about the ridiculousness that LP & M causes..
[SuperR Kitchen] SuperR.:
It requires you to download the kernel source for your Linux distro, patch the kernel source with code from cm, compile the Linux kernel, and boot your pc with the new kernel. This is a bit beyond the scope of the kitchen.

It would be nice to have a how-to for people that want to do it though. The only thing you gain is being able to extract certain cm roms where the dev used TARGET_TRANSPARENT_COMPRESSION_METHOD.
[SuperR Kitchen] Rydah:
Hey [MENTION=718594]super[/MENTION]R, I just wanted to say I finally got my rom to flash and booted. I might have an issue with user app being being enabled while perms are set at sparce_dat. Should that be an issue?
[SuperR Kitchen] SuperR.:
It is possible. I have not tried that combo. Maybe we need to create sparse dat data images when using sparse dat with user apps enabled. I will look into it. Meanwhile, set_metadata should work.
[SuperR Kitchen] Rydah:
Yeah that'd be nice. I kinda had concluded that that was what was causing my flashing issues. Looking forward to sparce data partitions.

Sent From My LG V10
[SuperR Kitchen] Hamidreza2010:
[MENTION=718594]super[/MENTION]R, please add change log to first page.for newer version we should search for chnage log on last pages and its a bit difficult
[SuperR Kitchen] theincognito:
[MENTION=5787964]SuperR.[/MENTION] and anyone else who can help me : Hi. I installed VirtualBox on my pc,Windows 10 (64 bit).

On that,I installed Lubuntu 15.10(64 bit).

So the issue I am facing is,I can't install a single package using apt-get. :( Pls help.

Here is an example:

ags@ags-VirtualBox:~$ sudo apt-get install p7zip-full gawk
[sudo] password for ags:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package p7zip-full is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'p7zip-full' has no installation candidate
E: Unable to locate package gawk
[SuperR Kitchen] Ram121:
Check Internet working on virtual machine
[SuperR Kitchen] SuperR.:
Screenshot from first post:

It seems like your virtual machine is not getting an internet connection. Look at the VirtualBox forums or Google search for help.
[SuperR Kitchen] theincognito:
No,no.. Its getting internet connection. I posted that message using the Lubuntu! :P

Anyways,thank you for your suggestions. I got it working by:

sudo apt-get update && sudo apt-get dist-upgrade

Its fine now :)
[SuperR Kitchen] Rydah:
I hate to be one to bug but is there any issues with deodexing on the latest kitchen build? It goes really quickly now and does delete all odex files but doesn't actually add classes.dex to my apks. I setup the kitchen on another laptop and same issue. It worked two days ago.
[SuperR Kitchen] SuperR.:
Link me to the firmware you are trying to deodex and I will take a look. It is working for me with the few I just tested.
[SuperR Kitchen] Rydah:
Here it is https://www.androidfilehost.com/?fid=24269982086988331

I know there are some errors with 2 apks (LGWeatherService and LGEasyHome)
[SuperR Kitchen] hohassan444:
[MENTION=5787964]SuperR.[/MENTION].please , i have problem that some roms ( based on sparse_dat ) fail to install.... i noticed that in these cases , there is failure to build sparse image ...ALWAYS SYSTEM.TRANSFER.LIST is empty ( 0 byte). any ideas ?
[SuperR Kitchen] SuperR.:
This rom is deodexing without issue for me. I have no idea why yours stopped working.

system.trasfer.list should not be 0 bytes, that is for sure. I am not sure why. Is it this way on all roms or just some?
[SuperR Kitchen] Rydah:
I appreciate your response. Is there any packages or anything I need installed for it to work? I'm very confused why it worked and now doesn't, although I did have to re-configure my laptop but I am sure I set it up the same as before. I'll film what it does as I can't copy and paste it since it works too fast and cleans up when finished.

Edit: [MENTION=718594]super[/MENTION]r I figured it out. Terminal was going too fast for me to see it with my bare eyes, but taking a picture I was able to see what the error was and got it fixed up. Java apparently uninstalled itself on my computer.
[SuperR Kitchen] hohassan444:
just some...even stock ones.
[SuperR Kitchen] bcrichster:
scroll up in terminal when finished, as it actually is still in terminal above last screen. [MENTION=5787964]SuperR.[/MENTION] done a dang good job of making the window hide everything that isn't a direct option/selection from the SuperR Kitchen. It LOOKS gone,but still there when ya scroll up
[SuperR Kitchen] SuperR.:
v0.9.6.4

Changes:

Bug fix - When rooting and using set_metadata, the metadata would double itself and remove the busybox install line.

Added sparse dat data creation when user apps are enabled and sparse_dat is chosen.

Much better handling of changing perm types.

Many code optimizations.
[SuperR Kitchen] ANDjROID:
error making some tools.

i downloaded and installed kitchen. when i tried to run it seemed to start up right. but then instantly gave error of unable to make some tools. it then suggested i run this -sudo apt-get install lzop 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 make

i did and it said already installed. still getting error even after reboot. also i made sure i installed all the codes you had at op. am dying to try this kitchen and hope you can help me solve this issue please. lol. also, remember, am total noob to linux. (and android, kinda) just downloaded and reinstalled update ver. and still same prob.
[SuperR Kitchen] SuperR.:
I am just guessing but maybe the system partition size is incorrect. It could prevent the system.img to build and then there would be nothing to transfer and maybe then the system.transfer.list would be empty. Other than that I am not sure.

The only suggestion I have is to delete your whole kitchen and start over fresh. Sorry, but I can't reproduce the issue so it is difficult to fix it.

If you are using the newest kitchen, it will ask you if you want to install the packages. Say yes (even though you already did it). If it still does not build after that it will ask you if you want to install the binaries. Say yes. That should get you going.
[SuperR Kitchen] bcrichster:
[MENTION=5787964]SuperR.[/MENTION] I found this poor guy stumbling around the Archi thread needing help so I pointed him here..

[MENTION=5156655]ANDjROID[/MENTION] ..Follow [MENTION=5787964]SuperR.[/MENTION] 's advice even if it sounds odd... he knows stuff about things we're still clueless of. When reporting issues, follow his directions to the letter to give as much info as possible (as stated in the first few posts) so he's not doing unnecessary guesswork and can pinpoint issues quicker to get you on the right track
[SuperR Kitchen] ANDjROID:
got it running. no errors

would like to say thank you, after my error post i installed a screenrecorder and and recorded the install. the kitchen was printing so fast i couldnt read the error completely. as i said im a noob. so after watching the vid i could see it was saying dir. does not exist. i forgot, linux is not windows simple. i had to create dir. now its running no errors. thanks for being patient with my linux illiteracy. lol.
[SuperR Kitchen] randomblame:
not doing so well on mm still cant boot an unpack repacked boot.img :'(
[SuperR Kitchen] SamuriHL:
Me either.
[SuperR Kitchen] ziddey:
Works fine as root:
[SuperR Kitchen] SamuriHL:
I'm pretty sure it didn't repack as root. Might be a bug. If I get a chance I'll play with it tomorrow.
[SuperR Kitchen] randomblame:
i ran superr with sudo and got a broken boot.img also so ...
[SuperR Kitchen] SuperR.:
I don't have an M device to test on so if anyone figures out what is wrong please let me know. I guess adding sudo commands to the ramdisk unpack and repack was not enough :(
[SuperR Kitchen] SamuriHL:
It did sudo in unpack but for me it didn't on repack. But it's late here and I can't test anymore til tomorrow.