yashsingh1/xdaforums huggingface dataset:
[SuperR Kitchen] obersteiner86:
Thx for the info i test it if i us it like your says i get to the chose language display and ther it freezet and if i install it with out the system_new.img i get Kernel is not SEANDROID Enforcing.
[SuperR Kitchen] SuperR.:
You could try using the latest adb and see it it works. If you are running the latest kitchen and have a 64-bit OS, try opening a terminal in /kitchen/tools and do:

./adb64 devices

I think it will stay the way it is for now. What is better about a white list than a black list (bloat_custom is basically a black list in your example)? Even in the most extreme cases, a black list will be smaller than a white list.

7.1.1 is still not fully supported.
[SuperR Kitchen] jaylence:
Thank you so much for all the help and suggestions guys.

I've finally made it to work by manually entering my device's key (adb_keys) on my phone's /data/misc/adb directory.

Got the keys from my computer's C:/users/username/.android/adbkey.pub
[SuperR Kitchen] obersteiner86:
I dont us android 7 is android 6.0.1 on my tab ther is not jet are android 7 out for the sm-t800
[SuperR Kitchen] JamBax:
How can I skip files for deodexing? :confused:
[SuperR Kitchen] bcrichster:
Remove files before deodexing then replace files afterwards

Sent from CM12.1 *N9515*
[SuperR Kitchen] SuperR.:
v2.1.2.4 (Donate version)

Changes:

Added a bunch of devices.

Fixed mmcblk devices not detecting properly from recovery.img if eol carriage returns are present in fstab.

Updated SuperSU to v2.78 SR2.

v1.1.1.4 (Standard version)

Changes:

Added a bunch of devices.

Fixed mmcblk devices not detecting properly from recovery.img if eol carriage returns are present in fstab.

Updated SuperSU to v2.78 SR2.

Sorry, I got a bit confused :o Hopefully a fellow Samsung user will be able to help you further :)

Apparently your recovery fstab was edited in Windows and contained carriage returns preventing the kitchen from working properly. I have fixed this issue and included your device in the kitchen. If you change perm types to something else and then back to what you want to use, everything will reset and the correct info should be in the updater-script. Sorry it took so long to respond. Hopefully this will get you sorted out :)
[SuperR Kitchen] luigimak:
superrs-kitchen2.git not found
[SuperR Kitchen] SuperR.:
It is working here. Make sure you entered your username and password correctly for the gitlab account that has access to the repo. It is also possible it was down earlier :eek:
[SuperR Kitchen] anttaz:
Delete
[SuperR Kitchen] Pyr0ball:
I did notice that when I was futzing with the recovery and trying to rebuild it. awesome! I'll give it another try with the original TWRP.

Edit: Well sad news is now the kitchen isn't recognizing when I've got the tablet plugged in on recovery :(

------------------------------------------------------
SuperR's Kitchen
by SuperR
------------------------------------------------------

** Plug in your device

xenial@Android-Kitchen:/kitchen/android/rom-tools/superrs-kitchen$ adb devices
List of devices attached
b7979bfd recovery
[SuperR Kitchen] SuperR.:
v2.1.2.5 (Donate version)

Changes:

Added check to see if the kitchen was really updated after an update.

Added color back to the kitchen versions on the update screen.

Fixed confusing screen after choosing to extract images from custom recovery.

v1.1.1.5 (Standard version)

Changes:

Added check to see if the kitchen was really updated after an update.

Added color back to the kitchen versions on the update screen.

Fixed confusing screen after choosing to extract images from custom recovery.

Thanks for pointing this out. It was actually waiting for you to push "y" for yes but did not ask the question first lol. Fixed now :)
[SuperR Kitchen] bluflight:
[MENTION=718594]super[/MENTION]R I'm [MENTION=4884393]luigimak[/MENTION] team mate, i had the same issue. If i try to clone git never found repository:

(login in gitlab.com with same user and password work good and all worked since previous update)

If i update from menù, insert user and password,start downloading update but always show 2.1.1.3 version :confused:
[SuperR Kitchen] SuperR.:
For some reason that user was removed. I have added blumak2000 to the repo again. Sorry for the inconvenience.
[SuperR Kitchen] bluflight:
No problem mate, thank you for quick reply and for your support to Android community [emoji106]

Inviato dal mio ONEPLUS A3003 utilizzando Tapatalk
[SuperR Kitchen] obersteiner86:
I get the rom working for my sm-t800 but no wlan,do need to but are wlan modul somewear or way its not working?

It ask me for to your whant disable wlan hdp no or yes i choose no on the message below but wlan is not working.

That is the message iam talking about wlan.wfd.hdcp=disabled
[SuperR Kitchen] The Sickness:
You want it disabled?
[SuperR Kitchen] obersteiner86:
no its disabled if i chose no
[SuperR Kitchen] The Sickness:
So you want it enabled?
[SuperR Kitchen] obersteiner86:
yes i can not switch it on if i go to settings
[SuperR Kitchen] The Sickness:
Add this to your build.prop

wlan.wfd.hdcp=Enabled
[SuperR Kitchen] obersteiner86:
Wlan

Its not working her is are screen from it i at what your say
[SuperR Kitchen] jaylence:
In some firmwares, flashing NON-HLOS.bin (if your device still has this in original firmware) fixes the wifi issue.
[SuperR Kitchen] obersteiner86:
Sorry i cant not find this file is not for android 6.0.1
[SuperR Kitchen] jaylence:
Maybe it's now included in the modem.bin? Just a thought.

Try reflashing your modem and see if it works.
[SuperR Kitchen] obersteiner86:
Ther is no modem file for the sm-t800 only are bl file or i can not found the modem file for it i search now on google for are modem file.
[SuperR Kitchen] Pyr0ball:
Aha, that'll do it :P

Also nice touch adding the bytes copied. Good feedback for the impatient.
[SuperR Kitchen] sharky481232:
Donated!

Gitlab - sharky481232
[SuperR Kitchen] Guizão BR:
Meta-inf

The meta-inf os super's kitchen not work in my device using TWRP, i use this other meta-inf
[SuperR Kitchen] bcrichster:
Might be useful to upload the meta-inf generated by SuperR's Kitchen for a comparison to locate changes/specifics

Sent from CM12.1 *N9515*
[SuperR Kitchen] Guizão BR:
Is here now ;)
[SuperR Kitchen] obersteiner86:
I found out that magisk is not working with the stock kernel i need to make are custom kernel
[SuperR Kitchen] SuperR.:
Added, thanks :)

The kitchen found a different by-name directory than the one you are using.

Kitchen detected:

/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name

The one you said works:

/dev/block/platform/mtk-msdc.0/by-name

I am not sure why they are different, but you can change your device file ( /kitchen/tools/devices/INFINIX-X600-H533-5M/superr_byname ) to reflect the correct by-name directory. Once finished you can change perm type to something else and then back to sparse_dat and it should work for you.

edit: I attached a new META-INF for you to try with the corrected by-name. Let me know if it works and I will add your device to the kitchen.

You might want to post about this on the Magisk thread :)
[SuperR Kitchen] Guizão BR:
Ok, I'll teste later, bacause my device is charging now, hahaha, and my deivce is Quantum MUV PRO(Q5) and not infinix x600, I port ROM of x600 to my device ;); I deleted the assert line ;)
[SuperR Kitchen] obersteiner86:
Ther i read that is only working for sm-t800 on are custom kernel.And on the rom iron rom is are stock kernel or are custom kernel includet and the zip magisk-6 and this two files UPDATE-Busybox.Installer.v1.24.2-ALL-signed BusyBox-Magisk-1.25 but i can not us it with your kitchen.
[SuperR Kitchen] SuperR.:
Unfortunately at this point, the kitchen is not psychic and does not know that you are porting a rom to a different device. It only has the ability to work with the information you give it. Since your build.prop is from the INFINIX-X600-H533-5M, the kitchen uses INFINIX-X600-H533-5M by-name and asserts. If you change the device name in build.prop and get the by-name from either the correct boot.img or from the device you are porting to, both of these issues will be solved :)

The kitchen can install Busybox, and UPDATE-Busybox.Installer.v1.24.2-ALL-signed is just the older version of what the kitchen installs. I don't think you need to install Busybox twice. It is possible you need only to install the Magisk Busybox and you are correct, the kitchen does not currently do this. I can write a plugin for it if you want :)
[SuperR Kitchen] Guizão BR:
Hm, ok, thanks, i 'll test it :)
[SuperR Kitchen] obersteiner86:
Yes if your can make this this would be create superR.

I see that is supersu not working with magisk that is way is us this:

#Root

if

file_getprop("/tmp/aroma/magisk.prop","root") == "su"

then

package_extract_dir("rootzip", "/tmp/rootzip");

run_program("/sbin/busybox", "unzip", "/tmp/rootzip/SuperSU-v2.78-SR2.zip", "META-INF/com/google/android/*", "-d", "/tmp/rootzip");

run_program("/sbin/busybox", "sh", "/tmp/rootzip/META-INF/com/google/android/update-binary", "dummy", "1", "/tmp/rootzip/SuperSU-v2.78-SR2.zip");

ui_print(" ");

#SUD

set_metadata_recursive("/system/su.d", "uid", 0, "gid", 0, "dmode", 0700, "fmode", 0700, "capabilities", 0x0, "selabel", "u:object_r:system_file:s0");

endif;

if

file_getprop("/tmp/aroma/magisk.prop","root") == "phhma"

then

package_extract_dir("rootzip", "/tmp/rootzip");

run_program("/sbin/busybox", "unzip", "/tmp/rootzip/phh-superuser-17-magisk.zip", "META-INF/com/google/android/*", "-d", "/tmp/rootzip");

run_program("/sbin/busybox", "sh", "/tmp/rootzip/META-INF/com/google/android/update-binary", "dummy", "1", "/tmp/rootzip/phh-superuser-17-magisk.zip");

ui_print(" ");

endif;

if

file_getprop("/tmp/aroma/magisk.prop","root") == "no"

then

ui_print("No root installed...");

endif;

ui_print(" ");

#XPOSED

package_extract_dir("xposed", "/tmp/xposed1");

run_program("/sbin/busybox", "unzip", "/tmp/xposed1/xposed-v86.5-sdk23-systemless.zip", "META-INF/com/google/android/*", "-d", "/tmp/xposed1");

run_program("/sbin/busybox", "sh", "/tmp/xposed1/META-INF/com/google/android/update-binary", "dummy", "1", "/tmp/xposed1/xposed-v86.5-sdk23-systemless.zip");

# Magisk

if

file_getprop("/tmp/aroma/magisk.prop","magisk") == "yes"

then

package_extract_dir("magisk", "/tmp/magisk");

run_program("/sbin/busybox", "unzip", "/tmp/magisk/Magisk-v6.zip", "META-INF/com/google/android/*", "-d", "/tmp/magisk");

run_program("/sbin/busybox", "sh", "/tmp/magisk/META-INF/com/google/android/update-binary", "dummy", "1", "/tmp/magisk/Magisk-v6.zip");

ui_print(" ");

endif;

if

file_getprop("/tmp/aroma/magisk.prop","magisk") == "no"

then

ui_print("No magisk installed...");

endif;

#Busybox

if

file_getprop("/tmp/aroma/magisk.prop","busybox") == "bbn"

then

package_extract_dir("busybox", "/tmp/busybox");

run_program("/sbin/busybox", "unzip", "/tmp/busybox/UPDATE-Busybox.Installer.v1.24.2-ALL-signed.zip", "META-INF/com/google/android/*", "-d", "/tmp/busybox");

run_program("/sbin/busybox", "sh", "/tmp/busybox/META-INF/com/google/android/update-binary", "dummy", "1", "/tmp/busybox/UPDATE-Busybox.Installer.v1.24.2-ALL-signed.zip");

endif;

if

file_getprop("/tmp/aroma/magisk.prop","busybox") == "bby"

then

package_extract_dir("busybox", "/tmp/busybox");

run_program("/sbin/busybox", "unzip", "/tmp/busybox/BusyBox-Magisk-1.25.zip", "META-INF/com/google/android/*", "-d", "/tmp/busybox");

run_program("/sbin/busybox", "sh", "/tmp/busybox/META-INF/com/google/android/update-binary", "dummy", "1", "/tmp/busybox/BusyBox-Magisk-1.25.zip");

endif;

if

file_getprop("/tmp/aroma/magisk.prop","busybox") == "no"

then

ui_print("No busybox installed...");

endif;
[SuperR Kitchen] Pyr0ball:
[MENTION=5787964]SuperR.[/MENTION]

Ok I may need a little extra help with this device. Should I start a new thread or just post here?

What I did:

manually debloated the stock rom using root adb shell

did a factory reset

booted to recovery

did an image pull using superrs-kitchen2

perm: set_metadata

made NO other changes

rebuilt full ROM zip / signed

factory wipe using TWRP

installed new zip

Stuck on device logo on boot, no ADB, have to hard power cycle and restore from nandroid to get it working again
[SuperR Kitchen] SuperR.:
I will create a magisk_mod_mods plugin to allow installing any Magisk mod zip you add to the plugin.

Try removing root in the kitchen, then adding it back and build your rom again.
[SuperR Kitchen] obersteiner86:
[MENTION=3562224]Pyr0ball[/MENTION] set_metadata is only for kitekate and i dont thing that your device is kitekate android?
[SuperR Kitchen] bcrichster:
set_metadata works for Lollipop+ as well

Sent from CM12.1 *N9515*
[SuperR Kitchen] Pyr0ball:
Okipokey giving that a try now. Uploaded the last zip in case anyone needed to take a look: https://www.androidfilehost.com/?fid=312968873555011011
[SuperR Kitchen] Sh0X31:
do someone try it on Elementary OS Loki? Any issues?
[SuperR Kitchen] ShinySide:
1. I don't know why people ask these types of questions. And wait hours for an answer when thry could of found out in 2 minutes by downloading it and trying it.

2. Try it and find out. Worse case scenario no. Not like there's any chance it'll cause any harm to your os nor hardware.

3. Realistically can run it on any Linux distro if you satisfy it's needs. And considering elementary os is based off Ubuntu and SuperR builds tests it on Ubuntu....... think you already have your answer.....
[SuperR Kitchen] SuperR.:
v2.1.2.6 (Donate version)

Changes:

Added mods_install plugin requirements.

Cleaned up the way we look for and move old rom files to the 00_project_files directory when extracting.

Move bootimg and recoveryimg directories to 00_project_files when extracting new.

v1.1.1.6 (Standard version)

Changes:

Cleaned up the way we look for and move old rom files to the 00_project_files directory when extracting.

Move bootimg and recoveryimg directories to 00_project_files when extracting new.

Mods Install Plugin

by [MENTION=5787964]SuperR.[/MENTION]

Add any flashable zip to your ROM that uses an update-binary script instead of a updater-script

Remove mods

Shows the kitchen added mods you currently have installed

Usage:

Download the mod zips of your choice into the mod_zips directory inside the plugin.

In the kitchen main menu, choose Misc Tools > Run a plugin > mods_install

NOTE: This plugin basically obsoletes the xposed_systemless and gapps plugins, but I will leave them up in case anyone prefers them :)
[SuperR Kitchen] ingbrzy:
Great tool!
[SuperR Kitchen] obersteiner86:
Now i get wlan on but i dont come across the frist screen ther is see errors like com.android.phone is stoped and this messages contuis for all aps like samsung.framework and so on used set_metadata and rom is debloadet.

I us your plugin that your posed to include magi-busybox
[SuperR Kitchen] FeedlyPawns:
Donated

Gitlab - feedlypawn5
[SuperR Kitchen] bigrammy:
Hi [MENTION=5787964]SuperR.[/MENTION]

I know your busy with noobs. :(

Did you take on board/see about my suggestion of uuid for the partitions? Plugin maybe also add .sin flash. (.sin flash is Sony specific uuid could be general) or are they none starter?
[SuperR Kitchen] SuperR.:
The problem with by-num in the kitchen, is that we need to find the correct number for the mmcblk we want to work with. One way (the easiest imho) is to compare it to by-name to get this info, but at that point we may as well use by-name. Can you explain the benefit of using by-num over by-name? Perhaps I am not fully understanding what you mean.

edit: Is ".sin flash" a utility? If so, can you link it? Thanks :)
[SuperR Kitchen] obersteiner86:
I thing he mean this util Flashtool for sony models

I found only this file http://www.flashtool.net/downloads.php

Now my rom is fully working thx superR for this Great tool.
[SuperR Kitchen] bigrammy:
Thought I linked to it before Here old age I guess :laugh:

EDIT: Main thread is here for the Windows Tool

A Little background:

Reason I would like to incorporate this as a plugin is so I have some flexibility because the Tool as is seems to default to qualcomm's layout (or least it did last time I tried it) while I have a MediaTek device.

So I would like to flash a hybrid of files Example: custom-boot.img custom-oem.img custom-recovery.img system-sin lk-sin secro-sin other-sin's

Using sgdisk to create the partition links is a good idea imho as we do not need to mess with the by-name stuff.

Example: Some of my devices have different by-name locations depending on android version, booted to system, booted to recovery the pfr script creates the links based on the gpt

root@E5303:/ # sgdisk --print /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 30535680 sectors, 14.6 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 98101B32-BBE2-4BF2-A06E-2BB33D000C20
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 30535646
Partitions will be aligned on 1024-sector boundaries
Total free space is 35773 sectors (17.5 MiB)

Number Start (sector) End (sector) Size Code Name
1 1024 5119 2.0 MiB FFFF ta
2 5120 11263 3.0 MiB FFFF proinfo
3 11264 21503 5.0 MiB FFFF nvram
4 21504 41983 10.0 MiB FFFF protect1
5 41984 62463 10.0 MiB FFFF protect2
6 62464 63487 512.0 KiB FFFF seccfg
7 63488 65535 1024.0 KiB FFFF lk
8 65536 98303 16.0 MiB 8300 ltalabel
9 98304 180223 40.0 MiB FFFF fotakernel
10 180224 262143 40.0 MiB FFFF boot
11 262144 274431 6.0 MiB FFFF secro
12 274432 275455 512.0 KiB FFFF para
13 275456 291839 8.0 MiB FFFF logo
14 291840 312319 10.0 MiB FFFF expdb
15 312320 322559 5.0 MiB FFFF tee1
16 322560 332799 5.0 MiB FFFF tee2
17 332800 398335 32.0 MiB FFFF metadata
18 398336 400383 1024.0 KiB FFFF gen
19 409600 425983 8.0 MiB 8300 apps_log
20 425984 933887 248.0 MiB 8300 oem
21 933888 1343487 200.0 MiB 8300 cache
22 1343488 25247743 11.4 GiB 8300 userdata
23 25247744 30477311 2.5 GiB 8300 system
24 30477312 30510079 16.0 MiB FFFF flashinfo

so I can use

mount("ext4", "EMMC", "/dev/block/anysoc-or-place/by-name", "/system");

I hope that kinda makes sense :eek:
[SuperR Kitchen] DarkHeart Z:
[MENTION=5787964]SuperR.[/MENTION] Whenever I'm tried extracting a zip with lollipop+ sparse mode the following issues kept occuring in cygwin x86 .

i guess cygwin has a slight different mount options than linux . But the binaries you provided are working like a charm . It did converted the sparse dat to raw image . And it's perfectly intact . i tried 7zip archiver and I could browse through all the files inside system.img . And p7zip is installed inside already . So maybe instead of using mount option ; it can utilize p7zip to extract the files from system.img . What do ya say bro ? Is it possible ?

Edit : I manually tried extracting with 7z command ( not the kitchen's one ; cygwin's actually ) . And I tried with 7z x system.img -osystem and voila ! It did extract .
[SuperR Kitchen] ShinySide:
I haven't used windows in years yet alone cygwin but you use to not be able to mount file system images only windows directories/disks. Dunno if that's changed over the years
[SuperR Kitchen] SuperR.:
The problem is the symlinks. Extracting with 7zip loses the symlinks. If anyone knows how to get around this, I can implement this for cygwin.
[SuperR Kitchen] DarkHeart Z:
Actually ; i think I did . i don't know if it's correct or not . but i tried manually with "7z x system.img -osystem" and it did extract the whole system image and also a new file [SYS] was under it .

Edit : Got it . ext2explore . it can extract the system.img ; without breaking it's integrity . But for symlink I think there'll be in need of another symlinks.txt file to preserve the links ; so that it can be restored later on . What do ya say ?
[SuperR Kitchen] SuperR.:
There is no question p7zip can extract system.img. The problem is the symlinks. Check /system/bin. You will see text files where symlinks should be, or nothing at all (sorry can't remember which). I may be able to use the info the text file provides to create symlinks, but it has been a while since I tried so I am a bit foggy. I will look into it further.

edit: dsixda uses a 3rd party app called explore2fs.exe. I am not sure if this app still works or if it extracts symlinks. Feel free to try extracting the system.img using that tool or another and then move the extracted system directory into your project directory.
[SuperR Kitchen] DarkHeart Z:
Found an alternatives . Ext2explore . it can explore the system.img and also save it under the working rom directory . the symlinks can be preserved under a txt file . It will be collected before extracting the image . What do ya say ? or imgextractor .
[SuperR Kitchen] SuperR.:
xpirit's method is already being used, but it is only for converting dat to img. rimg2sdat.exe is included in the cygwin binaries.

Can you send the symlinks.txt file that Ext2explore generated?
[SuperR Kitchen] DarkHeart Z:
Thats the problem . i am not exactly sure if it extracts the symlinks or not .

Edit : Ok ; I'm trying and letting you know in a bit .
[SuperR Kitchen] DarkHeart Z:
it says no symlinks found under /system/bin and /system/xbin .
[SuperR Kitchen] DarkHeart Z:
[MENTION=5787964]SuperR.[/MENTION] Got your answer . Imgextractor . This time I'm 200% sure . it did extract the system.img correctly and also preserved all the permissions , gid , uid and didn't break a single symlink . Looks like i finally found you your way around for this i attached both system_statfile.txt with all info you asked for and also the magic tool created by And_pda from 4pda.ru . i attached the imgextractor here also . Hope it'll be helpful . :)
[SuperR Kitchen] Tigerstown:
I used that imgextractor tool. If you still need these answer hit me up just throwing that out there.
[SuperR Kitchen] DarkHeart Z:
Please check your pm bro . And I'm up for sending the files you asked me for too . in pm of course .
[SuperR Kitchen] SuperR.:
Thanks for the offer. I have almost everything written. Still need to know:

Does the system_statfile.txt name change to vendor_statfile.txt if you extract a vendor.img?

Those files would answer 1-3 so they would be helpful, thanks :)

edit: The list is down to 1 :)
[SuperR Kitchen] DarkHeart Z:
i already sent them in pm . And also the rom link which i tried extracting . happy to help :)

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

Everything is covered now . Looks like you got what you're looking for . infact you can do a lot more than this with imgextractor . if you mess with it a bit more you know ;)
[SuperR Kitchen] Tigerstown:
No problem glad you got it it took me longer to figured out how to use my kids windows PC then it did anything else. Seems like the person who posted that tool has it under control for you.
[SuperR Kitchen] SuperR.:
v2.1.2.7 (Donate version)

Changes:

Updated SuperSU to v2.78-SR3.

Alpha test for cygwin img extract.

v1.1.1.7 (Standard version)

Changes:

Updated SuperSU to v2.78-SR3.

Alpha test for cygwin img extract.

NOTE: You will need to grab the cygwin_binaries.zip again from the bitbucket repo to extract img files in cygwin. WARNING: This is untested so use at your own risk :)

Big thanks to [MENTION=5844027]DarkHeart Z[/MENTION] for finding this solution and explaining it to me :)
[SuperR Kitchen] DarkHeart Z:
The kitchen stuck at 'mounting system.img....' . IT doesn't go any furthur . Waited for a few moments ; But now I think it's an issue actually . Can you take a look at this :
[SuperR Kitchen] SuperR.:
v2.1.2.8 (Donate version)

Changes:

Fixed cygwin img extraction.

v1.1.1.8 (Standard version)

Changes:

Fixed cygwin img extraction.

NOTE: There are still many things that do not work in cygwin. At least being able to extract img files is a step in the right direction :)

Thanks to [MENTION=5844027]DarkHeart Z[/MENTION] for testing :)
[SuperR Kitchen] DarkHeart Z:
Bro please check your pm . I've something special for you ;)

Edit : Bro can you look into this problem called "ERROR : There was a problem extracting your boot.img" . Is it missing zlib ? or what ?