[ Windows / Linux / Mac ][DONATE] SuperR's Kitchen (v3.2.1.2 - 1-14-2021)

[BiuTone]

@SuperR.
I am a user of the donation version of your kitchen.

I usually use the windows version, but because of the error when unpack the vendor.img of Android 11, so that I try switched to the Linux version;

Unfortunately, I did not check the new PC authorization rules, I first reset the PC authorization on Windows, and tried to switch to the WSL(Ubuntu), but it still unable to unpack; And then I reset the authorization on WSL and prepared to go back to the Windows version, but told me "This PC was previously reset".

Until I found in your post about the change of PC authorization rules.
So, can I apply to restore my PC authorization? Many thanks！

BTW, The username of the kitchen is the same as the XDA forum.

 

[SuperR.]

I can confirm that your updated script fixes the issue. Thank you. Config file now contains this after being populated.


byname=/dev/block
sysmnt=/system_root
system=/dev/block/system
vendor=/dev/block/vendor
data=/dev/block/userdata
system_ext=/dev/block/system_ext
version=/dev/block/version
product=/dev/block/product
optics=/dev/block/optics
prism=/dev/block/prism
cust=/dev/block/cust
oem=/dev/block/oem
odm=/dev/block/odm
odm=/dev/block/ODM
recovery=/dev/block/recovery
recovery=/dev/block/RECOVERY
ramdisk=/dev/block/ramdisk
ramdisk=/dev/block/RAMDISK
kernel=/dev/block/kernel
kernel=/dev/block/KERNEL
kernel=/dev/block/Kernel
boot=/dev/block/boot

Not sure if the multiple hits/matches for odm, recovery, ramdisk etc will cause any issues, but seems to work perfectly fine here. Thanks again for the excellent Kitchen Super R

That is great news! Thank you for letting me know

Hi SuperR I donated $ 20 to you on paypal and I registered on your site SuperR's Kitchen Registration.

I tried to contact you by MP on XDA but I could not find a place to write you a private message.

If you could leave me a private message, I will answer you as soon as possible by providing you with username and email and even a screenshot of my paypal account to confirm my transaction.

Thank you! PM sent

@SuperR.
I am a user of the donation version of your kitchen.

I usually use the windows version, but because of the error when unpack the vendor.img of Android 11, so that I try switched to the Linux version;

Unfortunately, I did not check the new PC authorization rules, I first reset the PC authorization on Windows, and tried to switch to the WSL(Ubuntu), but it still unable to unpack; And then I reset the authorization on WSL and prepared to go back to the Windows version, but told me "This PC was previously reset".

Until I found in your post about the change of PC authorization rules.
So, can I apply to restore my PC authorization? Many thanks！

BTW, The username of the kitchen is the same as the XDA forum.

Fixed. As stated in the OP, please send authorization issues by PM and not in the kitchen thread. Thanks.

 

[alucke]

SuperR Kitchen root menu #2 busybox add/remove, I get an error "The Download Tools Failed"

 

[SuperR.]

SuperR Kitchen root menu #2 busybox add/remove, I get an error "The Download Tools Failed"

This is because Busybox was being downloaded from an XDA link that no longer resolves due to the recent changes. I will sort this out for the next update. Thanks for pointing it out

 

[SuperR.]

v3.2.1.0 is now available

Release posts have been moved to a dedicated releases thread to keep things more organized and easier to find.

All development discussion will remain in this thread. I will continue to post here with a link to the release post when there is a new update. I will also continue to change this thread title according to the latest release version and date

Native Windows users: If you have not already, please see this post and follow the instructions before updating. This is not needed for a fresh install.

I hope everyone is staying safe out there. Happy holidays!

 

[ananjaser1211]

I hope everyone is staying safe out there. Happy holidays!

Thanks for the update, will migrate my kitchen to WSL2 asap, and happy holidays

 

[tutibreaker]

got this issue after update to v3.2.1.0 ( clean install)
Copiando archivos a system ...
NameError: name 'j' is not defined
[1164] Failed to execute script superr
when i try to unpack a samsung firmware ( A70MN )

 

[SuperR.]

got this issue after update to v3.2.1.0 ( clean install)
Copiando archivos a system ...
NameError: name 'j' is not defined
[1164] Failed to execute script superr
when i try to unpack a samsung firmware ( A70MN )

Thank you for pointing this out. This issue will only affect native Windows and WSL1 users.

I have now uploaded new v3.2.1.0 zips that fix the issue.

 

[edzamber]

French language updated by @Yoanf_26 is up.

 

[JavixKGD]

@SuperR. Hey bud I just updated the kitchen and I am now getting this error

Loading ...Traceback (most recent call last):
File "superr.py", line 22, in <module>
File "<frozen importlib._bootstrap>", line 971, in _find_and_load
File "<frozen importlib._bootstrap>", line 955, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 665, in _load_unlocked
File "d:\documents\srkcomp2\venv\lib\site-packages\PyInstaller\loader\pyimod03_importers.py", line 493, in exec_module
File "pbin_dump.py", line 8, in <module>
File "<frozen importlib._bootstrap>", line 971, in _find_and_load
File "<frozen importlib._bootstrap>", line 955, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 665, in _load_unlocked
File "d:\documents\srkcomp2\venv\lib\site-packages\PyInstaller\loader\pyimod03_importers.py", line 493, in exec_module
File "update_metadata_pb2.py", line 10, in <module>
File "<frozen importlib._bootstrap>", line 971, in _find_and_load
File "<frozen importlib._bootstrap>", line 955, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 665, in _load_unlocked
File "d:\documents\srkcomp2\venv\lib\site-packages\PyInstaller\loader\pyimod03_importers.py", line 493, in exec_module
File "google\protobuf\descriptor_pb2.py", line 718, in <module>
File "google\protobuf\descriptor.py", line 546, in __new__
KeyError: "Couldn't find field google.protobuf.FieldDescriptorProto.proto3_optional"
[24976] Failed to execute script superr

Any ideas? Nothing has changed in my laptop and it was working before the update. Thank you!

 

[SuperR.]

@SuperR. Hey bud I just updated the kitchen and I am now getting this error

Loading ...Traceback (most recent call last):
File "superr.py", line 22, in <module>
File "<frozen importlib._bootstrap>", line 971, in _find_and_load
File "<frozen importlib._bootstrap>", line 955, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 665, in _load_unlocked
File "d:\documents\srkcomp2\venv\lib\site-packages\PyInstaller\loader\pyimod03_importers.py", line 493, in exec_module
File "pbin_dump.py", line 8, in <module>
File "<frozen importlib._bootstrap>", line 971, in _find_and_load
File "<frozen importlib._bootstrap>", line 955, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 665, in _load_unlocked
File "d:\documents\srkcomp2\venv\lib\site-packages\PyInstaller\loader\pyimod03_importers.py", line 493, in exec_module
File "update_metadata_pb2.py", line 10, in <module>
File "<frozen importlib._bootstrap>", line 971, in _find_and_load
File "<frozen importlib._bootstrap>", line 955, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 665, in _load_unlocked
File "d:\documents\srkcomp2\venv\lib\site-packages\PyInstaller\loader\pyimod03_importers.py", line 493, in exec_module
File "google\protobuf\descriptor_pb2.py", line 718, in <module>
File "google\protobuf\descriptor.py", line 546, in __new__
KeyError: "Couldn't find field google.protobuf.FieldDescriptorProto.proto3_optional"
[24976] Failed to execute script superr

Any ideas? Nothing has changed in my laptop and it was working before the update. Thank you!

As stated in the release post here, native Windows kitchen users need to follow the instructions on this post before updating. Too late for you now. You must do a fresh install of v3.2.1.0.

edit: I suggest installing WSL2 and running the Linux kitchen instead

 

[JavixKGD]

As stated in the release post here, native Windows kitchen users need to follow the instructions on this post before updating. Too late for you now. You must do a fresh install of v3.2.1.0.

edit: I suggest installing WSL2 and running the Linux kitchen instead

Too late indeed. I Fresh installed. I got the prompt on the kitchen to update as before and did, but did not work this time. So, I downloaded and did a fresh install and have everything already up and running. Thanks for the reply though. Have a good one and keep on rocking this awesome kitchen my friend!

 

[vn_mobile]

Update 3.2.1.0 build system failed (odm, product, vendor build success) extract from super.img (M315F). But old version 3.2.0.9 build system, product, vendor succsess (odm build failed) please check.

system.img: build failed. Check the img_build.log for details.

[INFO] Building sparse system_new.img

Running: mke2fs
mke2fs 1.45.4 (23-Sep-2019)
Creating filesystem with 1047841 4k blocks and 262144 inodes
Filesystem UUID: fdb6eca4-22ad-4fa9-a9d0-45ca6f3b222e
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736

Allocating group tables: 0/32 done
Writing inode tables: 0/32 done
Writing superblocks and filesystem accounting information: 0/32 done


Running: e2fsdroid
[] not found in fs_config, using defaults
failed to alloc 132112384
loaded 5027 fs_config entries
Created filesystem with 5037/262144 inodes and 1013425/1047841 blocks

 

[vn_mobile]

Try more other model same problem system.img: build failed. Check the img_build.log for details.

Working it linux version pc freezer when build file...

 

[HassanMirza01]

@SuperR. i have came across an issue, relating contexts of files you add in unpacked directory, like i added adreno.prop named file in system/system/ here, now it should have system_file context when packed but it has rootfs contexts making it not readable, 2nd, i added a folder in priv-app, that folder also got rootfs contexts, why this happening ?? due to new thing or i noticed it now ??

edit: i also have a solution, all latest roms comes with context files in them, kitchen should first find that file as it has proper way of applying contexts and it cover fine everything, either kitchen copy contexts from that location or kitchen should use a generic contect for all possible directories and apply previous dir contexts to new files in them,,,,

edit2: Confirmed working fine.... contexts are fine as i put plat_contexts file inplace of system's context made by kitchen and after repacking, all contexts seems okay

 

[SuperR.]

Update 3.2.1.0 build system failed (odm, product, vendor build success) extract from super.img (M315F). But old version 3.2.0.9 build system, product, vendor succsess (odm build failed) please check.

system.img: build failed. Check the img_build.log for details.

Try more other model same problem system.img: build failed. Check the img_build.log for details.

Working it linux version pc freezer when build file...

Please send a link to the firmware, and the steps I can take to reproduce the issue.

For now, you can revert to using make_ext4fs if you want. Open kitchen/tools/srk.conf, and add the line use_make_ext4fs=Yes. Save the file and build your img files again. No need to restart the kitchen after adding this line.

@SuperR. i have came across an issue, relating contexts of files you add in unpacked directory, like i added adreno.prop named file in system/system/ here, now it should have system_file context when packed but it has rootfs contexts making it not readable, 2nd, i added a folder in priv-app, that folder also got rootfs contexts, why this happening ?? due to new thing or i noticed it now ??

edit: i also have a solution, all latest roms comes with context files in them, kitchen should first find that file as it has proper way of applying contexts and it cover fine everything, either kitchen copy contexts from that location or kitchen should use a generic contect for all possible directories and apply previous dir contexts to new files in them,,,,

edit2: Confirmed working fine.... contexts are fine as i put plat_contexts file inplace of system's context made by kitchen and after repacking, all contexts seems okay

I will look into this. For now, you can do what you did to fix it if that is working for you.

You could also place your plat_contexts in 00_project_files, and rename it to file_contexts_custom. This will be used as the backup file_contexts file if the context is not found in file_contexts3-system.

You could also add an entry in file_contexts3-system for all files/directories you add.

You could also do as mentioned above and switch back to make_ext4fs, which has some fixes since v3.2.0.9.

 

[andy_zhang]

The latest version of the kitchen, I've been waiting to download/install.

 

[vn_mobile]

@SuperR. here the rom : https://drive.google.com/u/0/uc?id=1GLDXzJGxdqttmyxvQKywoFjCHXmVkNn_&export=download

 

[SuperR.]

@SuperR. here the rom : https://drive.google.com/u/0/uc?id=1GLDXzJGxdqttmyxvQKywoFjCHXmVkNn_&export=download

I did not have any problems building the system.img in this firmware. I did not make any changes, just unpack/repack. All went well. I run the Linux kitchen in Ubuntu 18.04.

 

[vn_mobile]

I did not have any problems building the system.img in this firmware. I did not make any changes, just unpack/repack. All went well. I run the Linux kitchen in Ubuntu 18.04.

Yes use ext4fs can