[ Windows / Linux / Mac ][DONATE] SuperR's Kitchen (v3.2.2.2 - 10-13-2021)

Search This thread
By:
Advanced…
aer0zer0

aer0zer0

Recognized Contributor
Sep 20, 2013
3,319
2,559
Cortland NY
Google Pixel 8 Pro
Google Pixel Watch 2
Alan-B said:
Hi,

I guess she's only in control! well if Viper has arrived there.
I did not find how to integrate 'vendor'.
The A / B parts serve for OTA and the recovery don does not normally give problems.
I do not have any contacts with Viper to know how to do it !!
PS:
I guess it takes a vendor image to flash at the same time? if you make a complete wipe the party 'vendor' is not there anymore !!
Click to expand...
Click to collapse

Get your boot, system, and vendor images from the ruu.

Create your build in kitchen

Dump the images in your build folder

Extract both system and vendor (I use raw img when prompted)

Deodex

Patch for deodex, since it's system as root, doesn't patch boot I'm going

Either create ext4 images or twrp.zip, it will rebuild the images.

That should be it. @JEANRIVERA anything I missed
 
  • Like
Reactions: SuperR.
JEANRIVERA

JEANRIVERA

Senior Member
Mar 30, 2007
3,049
1,503
42
Nazareth, PA
HTC U12+
ASUS ROG Phone 3
aer0zer0 said:
Get your boot, system, and vendor images from the ruu.

Create your build in kitchen

Dump the images in your build folder

Extract both system and vendor (I use raw img when prompted)

Deodex

Patch for deodex, since it's system as root, doesn't patch boot I'm going

Either create ext4 images or twrp.zip, it will rebuild the images.

That should be it. @JEANRIVERA anything I missed
Click to expand...
Click to collapse

to be exact this is the instructions I followed as per @SuperR. himself provided here https://xdaforums.com/showpost.php?p=77615967&postcount=2154

I am not sure why you are having this issue. I just used your firmware to create a raw_img rom and everything worked without issue. Here are the steps I took:
downloaded firmware
manually extracted system_image.emmc.win, vendor_image.emmc.win, and boot.emmc.win into project directory
renamed the above files to system.img, vendor.img, and boot.img, system_other.img
extract system.img from the main menu
say yes to extract and include vendor.img
choose raw_img perm type
go to the boot/recovery menu
remove dm-verity
remove forceencrypt
go to rom tools menu
choose deodex rom, say yes to all
go to the build menu
build full rom zip
say yes to zipalign
your choice to zipalign framework files
say no to convert to update-binary script
choose option #4 system.img when asked for system partition size
choose option #4 vendor.img when asked for vendor partition size
your choice on signing the rom zip
 
  • Like
Reactions: Sands207 and SuperR.
Alan-B

Alan-B

Senior Member
May 6, 2006
1,202
1,279
73
WAVRE
aer0zer0 said:
Get your boot, system, and vendor images from the ruu.

Create your build in kitchen

Dump the images in your build folder

Extract both system and vendor (I use raw img when prompted)

Deodex

Patch for deodex, since it's system as root, doesn't patch boot I'm going

Either create ext4 images or twrp.zip, it will rebuild the images.

That should be it. @JEANRIVERA anything I missed
Click to expand...
Click to collapse
Re hi,
thank you,
I will test that. I just have a hard time getting the iamge 'vendor'! with RRU decripte
 
dr.ketan

dr.ketan

Recognized Developer / Recognized Contributor
Apr 9, 2011
39,233
76,819
Gujarat, India
drketanrom.com
Samsung Galaxy Watch 4
Samsung Galaxy S22 Ultra
@SuperR.
Issue pulling system

TWRP

Code: 
adb: error: remote object '/system/build.prop' does not exist

Android (ADB debug enabled granted SU)

Code: 
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
/dev/block/sda18 on /system type ext4 (ro,seclabel,relatime,i_version,data=ordered)
/dev/block/sda18 on /sbin/.core/mirror/system type ext4 (ro,seclabel,relatime,i_version,data=ordered)
mount: bad /etc/fstab: No such file or directory
adb: error: failed to copy '/system/build.prop' to 'C:\Users\O\Desktop\SuperRs-Kitchen_Win-32_v3.1.6.5\superr_pullSYS/build.prop': open failed: Permission denied

One more attempt with Android, pulled images with 1KB each

Code: 
Traceback (most recent call last):
  File "superr.py", line 7299, in ext4Xtract
  File "ext4.py", line 555, in __init__
  File "ext4.py", line 619, in read_struct
  File "ext4.py", line 362, in _from_buffer_copy
ValueError: Buffer size too small (0 instead of at least 1024 bytes)
7-Zip 17.01 beta (x86) : Copyright (c) 1999-2017 Igor Pavlov : 2017-08-28

Scanning the drive for archives:
1 file, 80 bytes (1 KiB)

Extracting archive: system.img
ERROR: system.img
Can not open the file as archive


Can't open as archive: 1
Files: 0
Size:       0
Compressed: 0
Traceback (most recent call last):
  File "superr.py", line 7299, in ext4Xtract
  File "ext4.py", line 555, in __init__
  File "ext4.py", line 619, in read_struct
  File "ext4.py", line 362, in _from_buffer_copy
ValueError: Buffer size too small (0 instead of at least 1024 bytes)
7-Zip 17.01 beta (x86) : Copyright (c) 1999-2017 Igor Pavlov : 2017-08-28

Scanning the drive for archives:
1 file, 80 bytes (1 KiB)

Extracting archive: system.img
ERROR: system.img
Can not open the file as archive


Can't open as archive: 1
Files: 0
Size:       0
Compressed: 0
 
Last edited:
Alan-B

Alan-B

Senior Member
May 6, 2006
1,202
1,279
73
WAVRE
Alan-B said:
Re hi,
thank you,
I will test that. I just have a hard time getting the iamge 'vendor'! with RRU decripte
Click to expand...
Click to collapse
Hi,
With RUU decrypts -F there are all .img files including 'vendor' actually.
Just see how Super R integrates it into the META-INF / updater-script ?
PS: I used -s that does not give the image 'vendor'
I will test the method mentioned by 'JEANRIVERA'

Thank you for help ..
 
Last edited:
bcrichster

bcrichster

Senior Member
Jun 6, 2013
1,220
837
If all else fails, just try to pull an mmcblk0 (maybe @SuperR. has made a plugin..?? :hint-hint, Lol: ) and use the kitchen to unpack into their corresponding images and just use the images ya need. Stash the others away for future usage (like aboot1 & 2, or the modems for example)

Sent from my Moto E (4) Plus using Tapatalk
 
SuperR.

SuperR.

Recognized Developer
Mar 23, 2014
2,646
8,816
Invisible
Moto E 2015
LG Nexus 5X
dr.ketan said:
@SuperR.
Issue pulling system

TWRP

Code: 
adb: error: remote object '/system/build.prop' does not exist

Android (ADB debug enabled granted SU)

Code: 
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
/dev/block/sda18 on /system type ext4 (ro,seclabel,relatime,i_version,data=ordered)
/dev/block/sda18 on /sbin/.core/mirror/system type ext4 (ro,seclabel,relatime,i_version,data=ordered)
mount: bad /etc/fstab: No such file or directory
adb: error: failed to copy '/system/build.prop' to 'C:\Users\O\Desktop\SuperRs-Kitchen_Win-32_v3.1.6.5\superr_pullSYS/build.prop': open failed: Permission denied

One more attempt with Android, pulled images with 1KB each

Code: 
Traceback (most recent call last):
  File "superr.py", line 7299, in ext4Xtract
  File "ext4.py", line 555, in __init__
  File "ext4.py", line 619, in read_struct
  File "ext4.py", line 362, in _from_buffer_copy
ValueError: Buffer size too small (0 instead of at least 1024 bytes)
7-Zip 17.01 beta (x86) : Copyright (c) 1999-2017 Igor Pavlov : 2017-08-28

Scanning the drive for archives:
1 file, 80 bytes (1 KiB)

Extracting archive: system.img
ERROR: system.img
Can not open the file as archive


Can't open as archive: 1
Files: 0
Size:       0
Compressed: 0
Traceback (most recent call last):
  File "superr.py", line 7299, in ext4Xtract
  File "ext4.py", line 555, in __init__
  File "ext4.py", line 619, in read_struct
  File "ext4.py", line 362, in _from_buffer_copy
ValueError: Buffer size too small (0 instead of at least 1024 bytes)
7-Zip 17.01 beta (x86) : Copyright (c) 1999-2017 Igor Pavlov : 2017-08-28

Scanning the drive for archives:
1 file, 80 bytes (1 KiB)

Extracting archive: system.img
ERROR: system.img
Can not open the file as archive


Can't open as archive: 1
Files: 0
Size:       0
Compressed: 0
Click to expand...
Click to collapse
No clue unfortunately. Without having your device in hand, the best I can do is try to fix the crash with an error message.

Alan-B said:
Hi,
With RUU decrypts -F there are all .img files including 'vendor' actually.
Just see how Super R integrates it into the META-INF / updater-script ?
PS: I used -s that does not give the image 'vendor'
I will test the method mentioned by 'JEANRIVERA'

Thank you for help ..
Click to expand...
Click to collapse
Why not use the decrypt_htc plugin? It does everything for you including vendor if it exists.
 
Lost_Animal

Lost_Animal

Member
Dec 22, 2010
42
38
Patras
xiaomi-miui.gr
SuperR. said:
@Lost_Animal - in your firmware, there is no sepolicy in the boot.img. Instead it is located:
vendor/etc/selinux/precompiled_sepolicy

You also have these files which are used to create a new sepolicy when magisk is flashed.
system/etc/selinux/plat_sepolicy.cil
vendor/etc/selinux/nonplat_sepolicy.cil

The reason the patch fails is because it everything is already patched the way the kitchen patches them. For example, in vendor/etc/selinux/nonplat_sepolicy.cil:
(allow zygote_27_0 dalvikcache_data_file_27_0 (file (execute)))

and in system/etc/selinux/plat_sepolicy.cil (execute was added):
(allow zygote dalvikcache_data_file (file (ioctl read write create getattr setattr lock append map unlink rename open execute)))

Keep in mind that I have no idea if this is correct, but the kitchen is doing what it is currently being told to do. Since the patch already exists you get a message saying so and no action is taken.

If you are wondering why the line says zygote_27_0 instead of zygote, it is because that is the name this file uses to reference zygote. Again, no clue if this is correct but it is what I have told it to do. Search the file for zygote and use the name that already exists.

If you know what I am doing wrong, please let me know. I am not an sepolicy expert. It would be a stretch to even call me a novice lol


What @aer0zer0 said :) Should already work.
Click to expand...
Click to collapse

My friend superr,

maybe I found the reason of fails on Selinux Deodex patch.
As I told you before, on your free version works ok but fails on paid version.

I made a search and found that in your paid version, even if you select to proceed for selinux deodex patch, nothing changed.
Maybe you get the message that Patch is already applied or that Patch is applied successfully, but all files remains untouched (with the same time).
All files on vendor/etc/selinux/precompiled_sepolicy & system/etc/selinux/plat_sepolicy.cil & vendor/etc/selinux/nonplat_sepolicy.cil remains original and nothing patched.
The opposite is on free Version....
All of those 3 files are patched correctly and marked with new time.

I saw that in system/etc/selinux/plat_sepolicy.cil no need for any patch in original file because all commands are existing ...
Code: 
(allow zygote dalvikcache_data_file (dir (ioctl read write create getattr setattr lock rename add_name remove_name reparent search rmdir open)))
(allow zygote dalvikcache_data_file (file (ioctl read write create getattr setattr lock append map unlink rename open)))
(allow zygote dalvikcache_data_file (lnk_file (ioctl read write create getattr setattr lock append map unlink rename open)))

If your script first checks the system/etc/selinux/plat_sepolicy.cil and if founded as patched, then maybe abandon all the other patches because thinks that no patch needed, which leads to fail, and ROMs have incorrect selinux patch and lagging like a hell...

In free version you have other script logic for the test ?
Because in your free version all Selinux deodex patches are working perfectly ....

Can you confirm this and fix it ?

Thanks in advance for your attention ..... :good:
 
Last edited:
  • Like
Reactions: kevintm78, godofsalt and bcrichster
SuperR.

SuperR.

Recognized Developer
Mar 23, 2014
2,646
8,816
Invisible
Moto E 2015
LG Nexus 5X
Lost_Animal said:
My friend superr,

maybe I found the reason of fails on Selinux Deodex patch.
As I told you before, on your free version works ok but fails on paid version.

I made a search and found that in your paid version, even if you select to proceed for selinux deodex patch, nothing changed.
Maybe you get the message that Patch is already applied or that Patch is applied successfully, but all files remains untouched (with the same time).
All files on vendor/etc/selinux/precompiled_sepolicy & system/etc/selinux/plat_sepolicy.cil & vendor/etc/selinux/nonplat_sepolicy.cil remains original and nothing patched.
The opposite is on free Version....
All of those 3 files are patched correctly and marked with new time.

I saw that in system/etc/selinux/plat_sepolicy.cil no need for any patch in original file because all commands are existing ...
Code: 
(allow zygote dalvikcache_data_file (dir (ioctl read write create getattr setattr lock rename add_name remove_name reparent search rmdir open)))
(allow zygote dalvikcache_data_file (file (ioctl read write create getattr setattr lock append map unlink rename open)))
(allow zygote dalvikcache_data_file (lnk_file (ioctl read write create getattr setattr lock append map unlink rename open)))

If your script first checks the system/etc/selinux/plat_sepolicy.cil and if founded as patched, then maybe abandon all the other patches because thinks that no patch needed, which leads to fail, and ROMs have incorrect selinux patch and lagging like a hell...

In free version you have other script logic for the test ?
Because in your free version all Selinux deodex patches are working perfectly ....

Can you confirm this and fix it ?

Thanks in advance for your attention ..... :good:
Click to expand...
Click to collapse
Confirmed. The issue is the 64-bit bootimg binary not working. If you replace it with the 32-bit version from the free kitchen it will work. I will switch it out for the next update.

Linux bootimg binary location in both kitchen versions:

kitchen/tools/linux_tools/bootimg
 
  • Like
Reactions: kevintm78, djb77, sekaiacg and 1 other person
aer0zer0

aer0zer0

Recognized Contributor
Sep 20, 2013
3,319
2,559
Cortland NY
Google Pixel 8 Pro
Google Pixel Watch 2
SuperR. said:
My friend superr,

maybe I found the reason of fails on Selinux Deodex patch.
As I told you before, on your free version works ok but fails on paid version.

I made a search and found that in your paid version, even if you select to proceed for selinux deodex patch, nothing changed.
Maybe you get the message that Patch is already applied or that Patch is applied successfully, but all files remains untouched (with the same time).
All files on vendor/etc/selinux/precompiled_sepolicy & system/etc/selinux/plat_sepolicy.cil & vendor/etc/selinux/nonplat_sepolicy.cil remains original and nothing patched.
The opposite is on free Version....
All of those 3 files are patched correctly and marked with new time.

I saw that in system/etc/selinux/plat_sepolicy.cil no need for any patch in original file because all commands are existing ...

Confirmed. The issue is the 64-bit bootimg binary not working. If you replace it with the 32-bit version from the free kitchen it will work. I will switch it out for the next update.

Linux bootimg binary location in both kitchen versions:

kitchen/tools/linux_tools/bootimg
Click to expand...
Click to collapse

Does this affect Windows version?
 
Lost_Animal

Lost_Animal

Member
Dec 22, 2010
42
38
Patras
xiaomi-miui.gr
SuperR. said:
Confirmed. The issue is the 64-bit bootimg binary not working. If you replace it with the 32-bit version from the free kitchen it will work. I will switch it out for the next update.

Linux bootimg binary location in both kitchen versions:

kitchen/tools/linux_tools/bootimg
Click to expand...
Click to collapse

Thank you my friend.
Already made this and is fine now. :good:

To help you more, I think this problem affects more the roms without Sepolicy in kernel (boot.img) and placed in vendor.img as vendor/etc/selinux/precompiled_sepolicy :D
 
Alan-B

Alan-B

Senior Member
May 6, 2006
1,202
1,279
73
WAVRE
JEANRIVERA said:
to be exact this is the instructions I followed as per @SuperR. himself provided here https://xdaforums.com/showpost.php?p=77615967&postcount=2154

I am not sure why you are having this issue. I just used your firmware to create a raw_img rom and everything worked without issue. Here are the steps I took:
downloaded firmware
manually extracted system_image.emmc.win, vendor_image.emmc.win, and boot.emmc.win into project directory
renamed the above files to system.img, vendor.img, and boot.img, system_other.img
extract system.img from the main menu
say yes to extract and include vendor.img
choose raw_img perm type
go to the boot/recovery menu
remove dm-verity
remove forceencrypt
go to rom tools menu
choose deodex rom, say yes to all
go to the build menu
build full rom zip
say yes to zipalign
your choice to zipalign framework files
say no to convert to update-binary script
choose option #4 system.img when asked for system partition size
choose option #4 vendor.img when asked for vendor partition size
your choice on signing the rom zip
Click to expand...
Click to collapse

Hi,
I followed this method well, but!
Problem with partition 'vendor' message in TWRP. impossible to mount the partiton!
This boot, but the camera apk does not install! I guess 'vendor' is not erased and not reinstalled!
For the deodex this seems to work.
Is it better to take the 'vendor' stock partition? or that of the TWRP backup?
 
JEANRIVERA

JEANRIVERA

Senior Member
Mar 30, 2007
3,049
1,503
42
Nazareth, PA
HTC U12+
ASUS ROG Phone 3
Alan-B said:
Hi,
I followed this method well, but!
Problem with partition 'vendor' message in TWRP. impossible to mount the partiton!
This boot, but the camera apk does not install! I guess 'vendor' is not erased and not reinstalled!
For the deodex this seems to work.
Is it better to take the 'vendor' stock partition? or that of the TWRP backup?
Click to expand...
Click to collapse
I use stock vendor
 
Alan-B

Alan-B

Senior Member
May 6, 2006
1,202
1,279
73
WAVRE
JEANRIVERA said:
I use stock vendor
Click to expand...
Click to collapse
Re Hi,
This is 'vendor' stock that I used, but I do not know why the installation of .zip, the partition 'vendor' does not want to be mounted?
The META-INF seems fair to me!


#MOUNT
ifelse(is_mounted("/vendor"), "", mount("ext4", "EMMC", file_getprop("/tmp/config", "vendor"), "/vendor"));
ifelse(is_mounted("/system"), "", mount("ext4", "EMMC", file_getprop("/tmp/config", "system"), "/system"));
ui_print("Extracting system...");
ui_print(" ");
package_extract_file("system_new.img", file_getprop("/tmp/config", "system"));
ui_print("Extracting vendor ..."); ui_print(" ");
package_extract_file("vendor_new.img", file_getprop("/tmp/config", "vendor"));
set_progress(0.700000);
ui_print(" "); ui_print("Extracting boot image..."); ui_print(" ");
package_extract_file("boot.img", file_getprop("/tmp/config", "boot"));
set_progress(0.800000);
 
JEANRIVERA

JEANRIVERA

Senior Member
Mar 30, 2007
3,049
1,503
42
Nazareth, PA
HTC U12+
ASUS ROG Phone 3
Alan-B said:
Re Hi,
This is 'vendor' stock that I used, but I do not know why the installation of .zip, the partition 'vendor' does not want to be mounted?
The META-INF seems fair to me!


#MOUNT
ifelse(is_mounted("/vendor"), "", mount("ext4", "EMMC", file_getprop("/tmp/config", "vendor"), "/vendor"));
ifelse(is_mounted("/system"), "", mount("ext4", "EMMC", file_getprop("/tmp/config", "system"), "/system"));
ui_print("Extracting system...");
ui_print(" ");
package_extract_file("system_new.img", file_getprop("/tmp/config", "system"));
ui_print("Extracting vendor ..."); ui_print(" ");
package_extract_file("vendor_new.img", file_getprop("/tmp/config", "vendor"));
set_progress(0.700000);
ui_print(" "); ui_print("Extracting boot image..."); ui_print(" ");
package_extract_file("boot.img", file_getprop("/tmp/config", "boot"));
set_progress(0.800000);
Click to expand...
Click to collapse
Just do not try to flash vendor img, it will stay intact
 
I

Incredy

Member
Jun 25, 2017
9
2
How do I patch sepolicy for Oreo deodex if it's not in boot.img but in vendor.img?
My device is lagging even after applying the patch, and after reading some posts here, I think it's because my sepolicy is located in vendor/etc/selinux

My device is a note 9 stock rom
 
  • Like
Reactions: kpirnie
SuperR.

SuperR.

Recognized Developer
Mar 23, 2014
2,646
8,816
Invisible
Moto E 2015
LG Nexus 5X
Incredy said:
How do I patch sepolicy for Oreo deodex if it's not in boot.img but in vendor.img?
My device is lagging even after applying the patch, and after reading some posts here, I think it's because my sepolicy is located in vendor/etc/selinux

My device is a note 9 stock rom
Click to expand...
Click to collapse
Place vendor.img in project directory when you extract your system.img. When it asks if you want to extract and include vendor, say yes. When you Patch sepolicy for Oreo deodex, it will patch all sepolicy and all .cil files that exist in your project directory. This includes vendor.
 
  • Like
Reactions: kpirnie, Sands207 and Incredy
You must log in or register to reply here.

Similar threads

SuperR.
[LINUX][FREE] SuperR's Kitchen (v1.2.1.5 - 01/08/2022)
Replies
7K
Views
338K
A
Akse_o
SuperR.
  • Locked
  • Sticky
SuperR's Kitchen Releases (Donate Version)
Replies
221
Views
17K
SuperR.
SuperR.
SuperR.
  • Locked
[DISCONTINUED][OS] Mint4Kitchen - A Kitchen ready version of Linux Mint 19
Replies
28
Views
19K
SuperR.
SuperR.
SuperR.
  • Locked
[DISCONTINUED][OS] Ubuntu4Kitchen - A Kitchen ready version of Ubuntu 18.04.3
Replies
52
Views
31K
Rustdroid
Rustdroid
chevycam94
Tutorial videos for SuperR's kitchen
Replies
4
Views
13K
Abrahamjolly
Abrahamjolly

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 180
    SuperR.
    SuperR.
    Disclaimer: I am not responsible for anything bad that may occur from the use of this kitchen, but I will take all the credit you can give me if it works for you :D

    main_donate_linux.png


    main_windows1.png


    Please read the troubleshooting in post #4 of the standard kitchen thread before asking for help.
    Please indicate your OS when asking for help.
    Please send a fast link to your firmware that does not require registration when asking for help.

    Donate Release Thread
    Donate Changelog

    Donate version Info
    See terms and conditions below.

    Terms and Conditions for SuperR's Kitchen Donate version:

    Allowed:
    • An active kitchen account grants usage privileges of the donate kitchen and the sr-code.com website.
    • One kitchen account provides kitchen access to one user, on one operating system, on one personal computer.

    Not allowed:
    • Sharing your kitchen account and/or privileges.
    • Transfer and/or resale of your kitchen account.
    • Suspicious activity.

    Definition:
    Suspicious activity - Decided exclusively by SuperR at the time of an incident.

    Resolution:
    If anything from the not allowed list occurs, your kitchen account will be disabled.

    See this post for more details on the Single PC license.

    Donation Options:
    No longer accepting donations or new users.

    EXISTING DONORS: GitLab is no longer used. See this post if you previously had GitLab access and are unable to download/update/install.

    NOTE: The Plugin Repo is included in the Donate kitchen. If you wish to see a description of the available plugins, they can be found here.

    Dependencies:

    WINDOWS:
    LINUX/MAC:
    • Java 8 or higher
    • Python (to run the launcher (could be bypassed by running tools/source/superr in the terminal from the main kitchen directory))

    Download/Install/Run:

    Free version:

    WSL2 (Windows 10):

    Linux/Mac (Terminal):
    1. Download the kitchen.zip from the download page sent through PM. Extract to a new directory.
    2. Enter the following command where "/location/of/kitchen" is the directory where the kitchen lives:
      Code: 
      /location/of/kitchen/superr

    Windows:

    NOTE: The native Windows version has reached end of life. Consider running the Linux kitchen in WSL2 using the guide above.​
    1. Download the kitchen.zip from the download page sent through PM. Extract to a new directory.
    2. Make sure Java listed above is installed and in your system environment PATH (Check Google for the many guides on this if you need help)
    3. Double click superr.exe in newly extracted kitchen directory.

    NOTE: After you start the kitchen, it will ask you for your Kitchen username and password. Make sure you enter it correctly or it will not work. Thanks for the donation, enjoy :)

    Known Issues/Limitations:
    Does not unpack/repack f2fs file systems.

    Linux:
    • None
    WSL2:
    • None
    WSL1:
    • Crashes with xattr not defined error when unpacking some img files due to a bug in the Python ext4 module.
    Mac:
    • Does not use e2fsdroid for building img files as I am not able to compile it for Mac so far.
    Windows:
    • No longer being updated. v3.2.1.3 is the last version. The Linux kitchen runs perfectly in WSL.
    • Does not use e2fsdroid for building img files as I am not able to compile it for Windows.
    • Crashes with xattr not defined error when unpacking some img files due to a bug in the Python ext4 module.
    • If you run Windows as administrator and have issues with the Boot Menu, please see this post.
    • If superr.exe gets removed by your antivirus program, whitelist the kitchen directory in your antivirus program.
    • If the kitchen can't find an internet connection, try whitelisting sr-code.com in your antivirus browsing security. If it still does not find a connection, try using a VPN.
    • The colors are not perfect due to Windows not supporting ASCII escape codes by default. If you want it to look more like Linux, you can run the Linux version in WSL (formerly known as "Bash on Ubuntu on Windows").

    Video tutorials by @chevycam94

    Credits:

    @osm0sis - For Busybox Installer and Android Image Kitchen
    @Chainfire - For SuperSU
    @JesusFreke - For [Bak]smali
    @nkk71 - For TWRP minzip patch, and make_ext4fs improvements
    @Captain_Throwback - For providing a pre-compiled update-binary with the minzip patch and squashing bugs
    @cubinator - For Python ext4 module
    @_riddle - For oat2dex
    @iBotPeaches - For Apktool
    @AOSP - For zipalign, aapt, adb, img2simg, simg2img, make_ext4fs
    @xpirt - for img2sdat & sdat2img
    @yoanf_26 - For French translation
    @anestisb - For vdexExtractor
    @iuss - For payload_dumper.py


    Contributors
    SuperR.

    Version Information
    Status:     Beta

    Created 2018-11-16
    View
    64
    SuperR.
    SuperR.
    Features:

    *Extract and create ROM from:
    • Rooted Device
    • Custom Recovery
    • Existing ROM zip
    • system.img/boot.img (and cache.img on Samsung devices)
    • system.ext4.tar/boot.img
    • system.ext4.win/boot.emmc.win (including multi-file .win000, .win001, etc)
    • Moto and other factory firmware zips containing sparsechunk files
    • cm12 + roms with sparse dat files
    • Zips that contain system.img and boot.img
    • Zips that contain payload.bin
    • Samsung firmware zips that contain tar.md5 file
    • Official Nexus/Pixel firmware tgz/zip
    • Official Nexus/Pixel preview tgz/zip
    • system directory that contains symlinks and boot.img
    *Create flashable zips of many varieties including:
    • Full ROM
    • Switch between set_perm, set_metadata (KitKat+), raw_img, and sparse_dat (Lollipop+)
    • Kernel (including init.d if you added it with the kitchen)
    • Recovery
    • Media
    • app, priv-app, and framework
    *Deodex the following:
    • Android 10 ROMs
    • Pie ROMs
    • Oreo ROMs
    • Nougat ROMs
    • Marshmallow ROMs
    • Lollipop ROMs
    • KitKat and earlier ROMs
    *Root features:
    • Root/unroot
    • Choose Magisk
    • Choose SuperSU
    • Add other root zips to /tools/root/root_zips directory
    • Choose system OR systemless root for M+ and Samsung 5.1.1 roms
    • Add/remove su.d support
    *Boot features:
    • Unpack/repack boot/recovery img (Big Thanks to @osm0sis for Android Image Kitchen!!!)
    • Add/remove insecure boot
    • Remove dm-verity
    • Add/remove forceencrypt
    *By-name auto-detection from:
    • Device
    • Existing ROM
    • boot.img
    • kernel.elf
    • **OR**...manually enter it
    *mmcblk auto-detection from:
    • recovery.img
    *Kitchen updater:
    • View the last 3 changelogs when an update is available.
    • Update to the latest version
    • Option to check for updates when the kitchen starts
    *Pack/Unpack super.img
    *Create system.img
    *Device database for mmcblk devices (currently very small, but will grow over time)
    *Add devices to the assert
    *Add custom asserts
    *Zipalign apks
    *Debloat ROM
    *Custom Debloat list support
    *Remove Knox
    *Add/remove busybox (Big thanks to @osm0sis for his Busybox Installer)
    *Add/remove user app support (/data/app)
    *Sign zips
    *Cross-platform: Windows and Linux are fully supported
    *Does not say Built with SuperR's Kitchen in the updater-script
    *Does not replace ro.build.display.id with Built.with.SuperRs.Kitchen
    *Allows you to create a custom entry in the updater-script below the ROM name
    *Removes all the Place holders (#ASSERT, #SYM, #PERM, etc) from the updater-script before zipping.
    *Custom ro.build.display.id
    *Option to convert updater-script to update-binary for all rom zips EXCEPT sparse_dat.
    *Add custom directory to be included in and flashed with rom zip to location of your choice.
    *Ability to choose an apk, decompile, modify it manually, recompile, sign, and move it back to where it came from.
    *Plugin support - Add your own script to the /kitchen/tools/plugins directory and the kitchen will run it for you.
    *AutoROM - Unattended ROM development using a config file.
    View
    43
    SuperR.
    SuperR.
    USAGE:

    1. Run the kitchen (instructions in OP)
    2. Create new project using the menu
    3. Copy ROM zip into the superr_NAME directory of this tool (NAME = the name of your new project).
      OR
      Copy system.ext4.tar and boot.img into the superr_NAME directory of this tool.
      OR
      Copy system.ext4.win and boot.emmc.win into the superr_NAME directory of this tool.
      OR
      Copy system.img and boot.img into the superr_NAME directory of this tool.
      OR
      Copy official Nexus tgz into the superr_NAME directory of this tool.
      OR
      Copy Samsung firmware zip into the superr_NAME directory of this tool.
      OR
      Copy Moto firmware zip into the superr_NAME directory of this tool.
      OR
      Leave superr_NAME directory empty to extract from rooted device or custom recovery
    4. Extract for new ROM from the Main menu.
    5. Enjoy!
    View
    10
    SuperR.
    SuperR.
    Er. Aditya said:
    Same **** here but i guess it wont happen till the dev wants and he aint around now
    Click to expand...
    Click to collapse
    I privately responded the the message you quoted the same day it was sent and got them sorted out.

    In your case, you can reset your PC authentication from the website as it states when you attempt to log in to the kitchen.

    Additionally, I have stated several times that authentication issues should be addressed privately.

    I am around, I just don't have time for new development lately.
    View
    10
    SuperR.
    SuperR.
    Update on Android Pie deodex:

    anestisb has finished Android P support for vdexExtractor. Android Pie introduced a new dex format, Compact Dex (cdex). anestisb created a new tool to convert cdex to standard dex which is required for Android Pie deodex. Unfortunately, the new tool will not currently work on Windows as it requires many AOSP dependencies and Google does not support compiling AOSP on Windows. It will only work on Linux and Mac. There are many Windows kitchen users, and I have no idea what to do about it.

    More information can be found here.

    If anyone can help, please do. Thanks :)

    EDIT: The Windows aapt.exe binary was not functioning properly. I have reverted to the previous aapt.exe that works. The win_tools package has been updated on the server. Sorry for the inconvenience.

    If you are on Windows and have already updated to v3.1.6.3, you can find the working aapt.exe here. Replace kitchen\tools\win_tools\aapt.exe with the one in the zip.
    View

New posts