yashsingh1/xdaforums huggingface dataset:
[SuperR Kitchen] Q9Nap:
That version throws an error just by calling it without any arguments:

Exception in thread "main" java.lang.UnsupportedClassVersionError: org/rh/smaliex/Main : Unsupported major.minor version 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:482)

Yeah I can't figure it out either; when I try to extract the sparse image, it just creates a META-INF folder and empty system folder.

Looks like it's not detecting it as a sparse image somehow:

Should we extract system.img to shamu-lyz28k? y/n y

Mounting system.img ...

[sudo] password for mhous33:
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

Copying files to system ...

The directory will be renamed to system if it is a system.img
cp: cannot stat ‘./output/*’: No such file or directory
umount: output/: not mounted

Preparing project directory ...
cat: /home/mhous33/android/superrs-kitchen/superr_shamu-lyz28k/system/build.prop: No such file or directory

Preparing updater-script ...
[SuperR Kitchen] SuperR.:
v0.8.9.0

Changes:

Greatly improved the debloat process and wildcards now work in the bloat_custom file

Example of the bloat_custom file wildcards:

system/app/Calculator*

will remove:

system/app/Calculator
system/app/Calculator.apk
system/app/Calculator.odex
system/app/Calculator/Calculator.apk
system/app/Calculator/arm/Calculator.odex
[SuperR Kitchen] SuperR.:
Will you please run the following command in terminal and paste the output?

cd /path/to/systemimg
file system.img

Thanks
[SuperR Kitchen] Androidwizzard:
I will upload both tonight - any preferences where to upload?
[SuperR Kitchen] Q9Nap:
Output is:

system.img: data
[SuperR Kitchen] Androidwizzard:
Before I upload - maybe for no reason - would this partition table for N920I be same helpful?
[SuperR Kitchen] SuperR.:
v0.8.9.1

Changes:

Fixed sparse img detection.

Added some status info in the debloat menu for the bloat_custom file.
[SuperR Kitchen] SuperR.:
Yes, could you also paste the contents of the superr_byname file located in /devices/codename ?

Thanks
[SuperR Kitchen] SuperR.:
I found some Note 5 firmware and I think I figured out the problem. The kitchen is looking for "by-name/system" in the ramdisk, and it finds "by-name/SYSTEM" which is not the same. I will make some adjustments and get it working :)
[SuperR Kitchen] SuperR.:
v0.8.9.2

Changes:

Fixed by-name detection on devices that use capital by-name partition names.
[SuperR Kitchen] nghia0423:
Help

Nifty tool. When extracting the system image, I'm getting the cat: pre_metadata: no such file or directory. Could you shed some light for me?

EDIT: Nvm, I the system.img was a sparse. Converted it and it now works.
[SuperR Kitchen] SuperR.:
What version of the kitchen are you running? As of v0.8.9.1 it should take care of the sparse to raw conversion on all systems.
[SuperR Kitchen] nghia0423:
I was on 8.9.0 first. I just updated to the latest version. I shall try again this time with the sparse img and see if the updated one works.
[SuperR Kitchen] Q9Nap:
Working now, thanks :)

Now the only issue afaict is fixing the set_metadata permissions option.

*Edit*

Oh yeah, also might be a good idea to recalculate symlinks and permissions in the updater-script prior to zipping.

I ran into an issue when I was manually removing bloat and one of the apps I removed had a symlink in the updater-script that caused the script to fail.
[SuperR Kitchen] SuperR.:
Using the following symlink example, which files are you removing that are causing the symlink issue?

symlink("/system/lib/libgoogle_speech_jni.so", "/system/priv-app/Velvet/lib/arm/libgoogle_speech_jni.so");

thanks :)
[SuperR Kitchen] enotar:
I finaly got a build booting with root but I have this Drive screen popping up every 2 seconds, just white screen
[SuperR Kitchen] SuperR.:
[MENTION=1345806]khomsn[/MENTION] - glad you got a working rom. the Built.with.SuperRs.Kitchen is fine the way it is and will not affect your rom booting. [MENTION=2682152]enotar[/MENTION] - glad you got a working rom. If Drive is causing you problems, I suggest you remove it and download it from the Play Store.
[SuperR Kitchen] Koognod:
Still trying to figure this out, if anyone has any suggestions I'd be eternally grateful.
[SuperR Kitchen] SuperR.:
Read the questions in post #4 and answer as many as possible. Additionally, paste your updater-script at pastebin.com or similar and link it.
[SuperR Kitchen] ashyx:
Look in your recovery log, it will tell you what failed.

In twrp it's under advanced.
[SuperR Kitchen] Koognod:
[MENTION=5787964]SuperR.[/MENTION] , sorry to make you repeat yourself so much I should have figured you would need information than that. Honestly the answer to my question is probably already been mentioned as well I have tried using the search function however due to my low skill lvl I was not able to figure out the solution on my own. Again I just want to apologize in advance for my uber noobness. here we go...

Kitchen version:0.9.4.3

ubuntu 15.04

samsung core prime g360t1

source was system extracted from stock aofa rom boot from trapkernel

lollipop 5.1.1

tried both metadata and perm not sparse

Rooted, Deodexed, added user app support built once with perm once with metadata asserts were added automatically i think it says cprimeltemtr added init.d support boot image insecure

no errors

system http://upple.it/52e8def58f0904a4/TM...=7qugldAJf1IgfQXyphSdKCcrbJMyIfFfP7u7jEOv4qk=

boot https://www.androidfilehost.com/?fid=24052804347817396

[MENTION=4899305]ashyx[/MENTION] I have sent my log to sd but nothing stood out to me how far back does the log go? I flashed one or two things after that and this was a couple days ago should I try flashing again ?

---------- Post added at 10:46 PM ---------- Previous post was at 10:44 PM ----------

[/COLOR [MENTION=718594]super[/MENTION]r also I have read recently you explained I should probably be using sparse_dat due to being on lollipop but is this enough to make it not flash in recovery?
[SuperR Kitchen] ashyx:
You have to flash the zip then save the log. The log is only for that session.
[SuperR Kitchen] SuperR.:
First off, you should update the kitchen.

The perm method should not prevent it from flashing, but sparse_dat may give you better results on L/M.

I am downloading your firmware now, but it will take a while because the upload site only allows 100kbps :(

Did you forget about linking to the updater-script contents on pastebin? :p
[SuperR Kitchen] Koognod:
I did forget O.0 Oops, sorry about that. Here it is: https://www.androidfilehost.com/?fid=24052804347817396
[SuperR Kitchen] SuperR.:
That is the link to the kernel again :p
[SuperR Kitchen] Koognod:
Wowww! Reawrry?? Let's try this one more time http://pastebin.com/KGJsdSJZ !!
[SuperR Kitchen] SuperR.:
Nothing stands out as a problem with the updater-script. Please send the recovery.log after flashing the rom as mentioned by [MENTION=4899305]ashyx[/MENTION] so we can see the errors.

edit: Have you tried wiping data and cache, then rebooting recovery from the recovery menu and flashing the rom? This has worked for many people using TWRP on many devices when getting update binary errors. May be worth a shot.
[SuperR Kitchen] Koognod:
http://pastebin.com/DJRPdw0X

---------- Post added at 05:55 AM ---------- Previous post was at 05:50 AM ----------

Recovery.log ^ [MENTION=4899305]ashyx[/MENTION] [MENTION=718594]super[/MENTION]r

I believe I tried wiping before flashing rom but I don't think I've tried rebooting from twrp than flashing as this is the first I'm hearing of this. I had someone else on the same device test the rom with the same results though, I don't know if that means anything
[SuperR Kitchen] SuperR.:
This log does not have the rom flash included. It may have gotten cut off or something due to pastebin character limits. Either way what you posted does not help. Make sure you include the part where you see the name of your rom show up and after.
[SuperR Kitchen] Koognod:
oh wow, it got cut off some how and I didn't even notice. my apologies.

---------- Post added at 06:33 AM ---------- Previous post was at 06:31 AM ----------

http://pastebin.com/RWiCXWqN here's the rest
[SuperR Kitchen] SuperR.:
I believe this is the problem:

I:Legacy property environment disabled.

Try set_metadata instead, and if it fails send me another recovery.log. Thanks
[SuperR Kitchen] Koognod:
metadata log: http://pastebin.com/SgyyTiRU

sparse log: http://pastebin.com/y1jLQ18j
[SuperR Kitchen] noobsgs2:
What Kitchen version? 0.9.4.6

What Linux are you running? Ubuntu 15.04

What device are you working on (make/model)? LeTV x800

What was the source you started from (system.img, system.ext4.tar, rom.zip, etc.) rom.zip

What Android version? 5.0.2

What perm method (set_perm, set_metadata, sparse_dat)? None

What did you do after extracting and before building? Nothing

Were there errors on the screen if you scroll up in the terminal?

Converting to system.img ...
Traceback (most recent call last):
File "/home/ubuntu/KITCHEN/tools/sdat2img.py", line 96, in <module>
main(sys.argv)
File "/home/ubuntu/KITCHEN/tools/sdat2img.py", line 77, in main
version, new_blocks, erase_block_set, new_block_set = parse_transfer_list_file(TRANSFER_LIST_FILE)
File "/home/ubuntu/KITCHEN/tools/sdat2img.py", line 36, in parse_transfer_list_file
trans_list = open(TRANSFER_LIST_FILE, 'r')
IOError: [Errno 2] No such file or directory: 'system.transfer.list'
[3;J

Can you send a link that does not require registration to the files you started with (nandroid, system.img, boot.img, etc)? Yes

Above my problem, im quite new to this. Sorry

Strange thing is that inside the zip file there is the system.transfer.list.dat

Update 1: If i extract the zip content when files are already present the kitchen holds on extracting system.new.dat, in the log file it seems it was waiting for the overwrite confirm even though the terminal whas not showing it. I then pressed A as [A]ll and it proceeded.
[SuperR Kitchen] Captain_Throwback:
FYI - That's not an error (just information) so it wouldn't be the cause of any issue. That line appears frequently when any zip is flashed.

These, however, are errors:

unmount of /system failed; no such volume
error: make_ext4fs: open: No such file or directory
[SuperR Kitchen] SuperR.:
I have no idea why you are having trouble after looking at your logs. Hopefully someone else can help. The only suggestion I have is to try as i mentioned before. Boot to recovery, wipe data/cache, reboot to recovery from recovery menu, flash rom.
[SuperR Kitchen] ashyx:
It seems the issue is that the system partition just isn't able to be mounted or unmounted.

Are the mount paths correct?

Can you post the mount points in the recovery.fstab?
[SuperR Kitchen] bcrichster:
I'd also try another style of recovery than TWRP cuz I had to go to CWM due to TWRP being so darn finnicky

Gratefully sent from my Rooted JollyRoger_B13
[SuperR Kitchen] SuperR.:
The mount points are correct. That is the first thing I checked. I verified in the stock boot.img, the custom boot.img, and the stock recovery.img. That is why I said I have no idea what is going on :(
[SuperR Kitchen] SuperR.:
v0.9.4.7

Changes:

Fixed csc not adding properly on Samsung devices if cache is included and the directories already exist in system dir.

Update to sepolicy-inject.

Minor UI fixes.
[SuperR Kitchen] enotar:
Thank for the best kitchen ever.
[SuperR Kitchen] Koognod:
[MENTION=2771334]BRichster[/MENTION] I would try another recovery but I believe this is the only one available for my device for the time being at least.

[MENTION=4899305]ashyx[/MENTION] I would post my fstab except I cannot find mine. :/ Is it on my device and/or in the rom? I've read that it's in etc but all i found was recovery.dat. there was an fstab.qcom in the previous folder (/) that I wasn't able to open (I don't think it's relevant, but I don't know). I had a feeling it had to do with the mount points as well because it seemed to happen in the beginning as it was mounthing the system. it gets to start wiping the system though I feel like cause after I've flashed the rom I've had to recover my system from a previous backup in order to boot again.

[MENTION=5787964]SuperR.[/MENTION] I will have to try wiping the data/cache next ...
[SuperR Kitchen] bcrichster:
Always, ALWAYS wipe data & caches before flashing a new ROM.. Been a rule of thumb for a long time

Gratefully sent from my Rooted JollyRoger_B13
[SuperR Kitchen] Koognod:
[MENTION=2771334]BRichster[/MENTION] Yeah I realize that, but I thought that because it was based off the rom I already running I maybe didn't have to. I'm pretty sure that the second time I flashed it I tried wiping first but then went directly to flashing rom which apparently I missed a reboot in between to counteract some sort of error in twrp that happens sometimes. So we shall see.

---------- Post added at 10:45 PM ---------- Previous post was at 10:37 PM ----------

[MENTION=5787964]SuperR.[/MENTION] So I tried it with the wipe and reboot to recovery before flash. Had a problem rebooting into recovery from recovery started trying to boot system so I used the hard buttons to reboot into recovery. Tried flashing rom same error occurred. Do you think the short time it had trying to boot the system affected the process? Or do you think It has to do with the mount points as [MENTION=4899305]ashyx[/MENTION] was saying?
[SuperR Kitchen] fhem:
[MENTION=5787964]SuperR.[/MENTION] I'm working on a N9 deodexed rom (MRA58N) and something weird going on. Not sure what's up. Please take a look. It's not building the rom?? Not sure why it unpacking my boot image didn't ask for that -- sepoloicy maybe. I always plug device in and let the kitchen grab what it needs.
[SuperR Kitchen] SuperR.:
I have no idea if it will fix your flashing problem, but yes with the workaround it is important to reboot recovery after wiping data/cache and then directly back into recovery to flash the zip. You could try wiping, power off, harware buttons back to recovery. Again, not sure if it will help you at all.

I can't say for sure if your mounts are correct, but I can tell you they are exactly the same as the ones found in the stock boot.img, stock recovery.img, and the custom kernel you linked. This means the kitchen is doing its job correctly and the only way the mounts are not correct is if you are using the wrong firmware.

It looks like gawk is either not installed or another awk is default. I will change all the "awk" commands to "gawk" to avoid this in the future.
[SuperR Kitchen] fhem:
I have gawk installed and no awk. Is this what is causing the syntax error on lines 220 -- 259 on the linked hastebin log?

Edit: I lied sorry I do have mawk and dpkg-awk installed as well as gawk.
[SuperR Kitchen] SuperR.:
Try this one and see if it clears up your issue.

v0.9.4.8

Changes:

Changed awk commands to gawk in case gawk is not the default awk.
[SuperR Kitchen] fhem:
OK ---- I recloned and started w/ fresh sys and boot images ---- gawk cleaned up but still not building please take a look same error as before. It doesn't like something about the partition sizes looks like it not geting the info from my device plus why is it unpaking my boot image?? Not sure what's changed since i did my n6p.
[SuperR Kitchen] Koognod:
[MENTION=5787964]SuperR.[/MENTION] Tried the workaround by power off through recovery then flashing again right afterwards, still no luck =(
[SuperR Kitchen] ashyx:
Can you post a screen shot of the flashing process after it fails in twrp.

To take the screenshot press POWER +VOL DOWN together.

Take note of where it saves.

Also can you pull out the META-INF folder from the rom and post it somewhere?
[SuperR Kitchen] SuperR.:
I think this version will sort you out. The difference was that the Nexus 9 uses APP and VNR instead of system and vendor in their by-name directories. The reason it is unpacking your boot.img is to get your file_contexts file.

v0.9.4.9

Changes:

Fixed detecting partition sizes on devices using APP/VNR instead of system/vendor.

Hide external boot extraction messages to be less confusing.

edit: hang on, i made a mistake. will post a new one in a few. sorry
[SuperR Kitchen] SuperR.:
v0.9.5.0

Changes:

Fix error in build_rom_zip
[SuperR Kitchen] Koognod:
[MENTION=4899305]ashyx[/MENTION] Thanks in advance for your time

meta inf zip : https://mega.nz/#!JI9SmaxC!WXysJi8gVkKfNF25NEUh598N_ese9ewpp1wIx9xmGzE

Screenshot: http://xdaforums.com/picture.php?albumid=12720&pictureid=51297
[SuperR Kitchen] sparks15:
Not working deodex, no errors, rom install fine but fails google play services on adding account. any idea?

With odexed runs fine.

What Kitchen version?

0.9.4.6

What Linux are you running?

Ubuntu 15.10 x64

What device are you working on (make/model)?

Nexus 6

What was the source you started from (system.img, system.ext4.tar, rom.zip, etc.)

system.img and boot.img

What Android version?

6.0 MRA58R

What perm method (set_perm, set_metadata, sparse_dat)?

set_metadata

Were there errors on the screen if you scroll up in the terminal?

None
[SuperR Kitchen] ashyx:
Ok so I have established that the update zip is working fine, as you can see it installs up to the permission changes where it fails, obviously as this script is not for my device.

The issue seems to be your system partition cannnot be mounted as it goes no further than that. Can you mount system in TWRP ok?

Do you have the read only box checked?

Have you got a link to your TWRP recovery? Have you tried the 2.8.7.1 version?
[SuperR Kitchen] Koognod:
[MENTION=4899305]ashyx[/MENTION] Wow, yes I see that you got much further then mine did. When I mount system via mount menu in twrp I don't see any notification let alone any errors. Would i have to export a log for something like that to show up? As for the read only box it remains unchecked. The recovery i got from this thread: http://xdaforums.com/showthread.php?t=3208853

---------- Post added at 09:31 AM ---------- Previous post was at 09:28 AM ----------

I've also tried getting a hold of the developer for this recovery earlier today to see if he might be able to help or had some sort of inpu , but I have not heard back from him yet.
[SuperR Kitchen] ashyx:
What is your exact device model?

Well heres the problem, the mount points are incorrect. These are the mount points in TWRP:

/boot emmc /dev/block/platform/soc.0/by-name/boot

/system ext4 /dev/block/platform/soc.0/by-name/system

/system_image emmc /dev/block/platform/soc.0/by-name/system

/data	ext4 /dev/block/platform/soc.0/by-name/userdata flags=encryptable=/dev/block/platform/soc.0/by-name/encrypt

/cache	ext4 /dev/block/platform/soc.0/by-name/cache

#/misc	emmc /dev/block/platform/soc.0/by-name/misc

/recovery emmc /dev/block/platform/soc.0/by-name/recovery flags=backup=1

/efs1 emmc /dev/block/platform/soc.0/by-name/modemst1 flags=backup=1;display=EFS

/efs2 emmc /dev/block/platform/soc.0/by-name/modemst2 flags=backup=1;subpartitionof=/efs1

/external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1

/usb-otg vfat /dev/block/sda1 /dev/block/sda flags=removable;storage;display=USB-OTG
[SuperR Kitchen] Koognod:
Thats kinda what I thought, weren't those extracted from my boot img or something though.

---------- Post added at 09:39 AM ---------- Previous post was at 09:38 AM ----------

G360t1

---------- Post added at 09:43 AM ---------- Previous post was at 09:39 AM ----------

I don't know how to say this without sounding needy, but, how do I fix this, lol?

---------- Post added at 09:44 AM ---------- Previous post was at 09:43 AM ----------

Do i have to edit the updater script?

---------- Post added at 09:45 AM ---------- Previous post was at 09:44 AM ----------

[/COLOR [MENTION=4899305]ashyx[/MENTION]

---------- Post added at 10:05 AM ---------- Previous post was at 09:45 AM ----------

OMG It worked!!!!!!!

---------- Post added at 10:07 AM ---------- Previous post was at 10:05 AM ----------

Thank you so much [MENTION=4899305]ashyx[/MENTION] for all of your help and thank you again to [MENTION=5787964]SuperR.[/MENTION] for the wonderful tool. And thank you both one more time for putting up with my noobness Xp
[SuperR Kitchen] ashyx:
No worries, you need to sort out why the mount points were wrong, was the boot.img correct?
[SuperR Kitchen] asc1977:
Short question

How you guys do extract a tar.md5 file from stock samsung firmware to become working files for superr kitchen with Ubuntu linux system?

I mean this ext4 files.

Btw its a great tool. Thx at the dev

Sorry for noob question.

Gesendet von meinem SM-G925F mit Tapatalk
[SuperR Kitchen] Koognod:
[MENTION=4899305]ashyx[/MENTION] it should have been, like I said I pulled it straight from the kernel. And after I flash the rom the shinyside kernel is showing up in androids settings. So I think that proves it. But I'm not sure, like I said I'm no expert.
[SuperR Kitchen] linuxct:
Hi, I think SElinux detection in kernel is not working fine. It says the kernel I'm working with doesn't have SElinux support (While I'm quite sure it does!). This is returning me an error at the time of compiling a full rom, of course, and compiling only apps and lib (?) is not a solution, for me. The kernel itself cannot be decompressed either because it's a Sony stock rom one, so, no android boot magic found (but I was already aware of this).

What Kitchen version?

0.9.5.0

What Linux are you running?

Ubuntu 15.10 x64

What device are you working on (make/model)?

Xperia M2

What was the source you started from (system.img, system.ext4.tar, rom.zip, etc.)

system.ext4.win

What Android version?

5.1.1 (Sony Stock Rom)

What perm method (set_perm, set_metadata, sparse_dat)?

sparse_dat (Obligated)

Were there errors on the screen if you scroll up in the terminal?

Nope.
[SuperR Kitchen] :
What I do is extract the odin file to a tar md5 file then right click it and mount the archive. Open it then drag and drop the files. Or you can use a tar command to extract it
[SuperR Kitchen] ashyx:
For Windows use 7zip, right click extract archive.

For ubuntu remove the md5 extension then right click and decompress with built in archive management tool.
[SuperR Kitchen] SuperR.:
I have added this device to the kitchen database since the by-name directory is incorrect in the stock boot.img, stock recovery.img, and the custom kernel. I checked all of them and I have no idea how it is possible lol. Anyway, it will be sorted out in the next version for anyone that has the SM-G360T1.

The issue is that you can't unpack the boot.img or the kitchen can't find what it needs after unpacking. You will need to extract the file_contexts file from the ramdisk one way or another to use set_metadata and sparse_dat. Once you get the file_contexts file, copy it into your 00_project_files directory and everything (other than boot tools) will work for you. You may also need to set up a device in /kitchen/tools/devices with your by-name/mmc. Look at some of the other devices in that directory as a guide.
[SuperR Kitchen] fhem:
Thank you again sir -- you are one of the best.
[SuperR Kitchen] bcrichster:
still says (0.9.4.4) does VERSION need updated or do I need a fresh pull? no problem either way, just need to know I didn't mess anything up
[SuperR Kitchen] SuperR.:
Not sure what you mean. The kitchen updater should get you updated.