yashsingh1/xdaforums huggingface dataset:
[SuperR Kitchen] mwilky:
Right, found the problem. After flashing, system/lib/libGLESv2.so gets symlinked to libGLESv3.so which is correct, you can see this file if you go to file explorer in recovery.

Once booted up, you try and locate the file and it has gone, cannot find it in rootexplorer, trying to pull it you get file not found.

Reboot back to recovery the file is there again, boot back to os it is gone...

Temp fix is to delete the symlink line from updater, make a copy of the libGLESv2.so and rename it to libGLESv3.so.

Maybe you want to take this as the standard method in your kitchen until we've found a solution?

Will find a proper solution in the next few days once i have some free time.

The lib64 variant is visible fine once booted.

Slightly worrying lol, god knows how many other issues this will have caused.
[SuperR Kitchen] tdunham:
I have the same exact problem with the Note 5 and did the same workaround with that symlink.
[SuperR Kitchen] SuperR.:
Good catch [MENTION=3699616]mwilky[/MENTION]. I have no clue why this is happening. Is there something the kitchen can look for common to all roms this workaround is required for? Samsung 5.1.1 or higher for example...or only the ____, ____(enter device code names here).
[SuperR Kitchen] ROBERT CM:
[MENTION=5787964]SuperR.[/MENTION] What is the difference with these methods for deodexed system.img

and which method is best for you..

- oat2dex with smali/backsmali as backup

- smali/backsmali

Thanks
[SuperR Kitchen] mwilky:
Yeah it was a weird one. I literally have no idea of which devices are affected, not sure if there's any others.

Really don't think it's a problem related to your kitchen though so I wouldn't worry about it, leave that to the rom devs you've done enough hard work :p
[SuperR Kitchen] elxufas:
I installed virtualbox , and I'll use Ubuntu.

The kitchen working.

Thanks for your work.

Best regards, Elxufas .

Enviado desde mi SM-G900F mediante Tapatalk
[SuperR Kitchen] tdunham:
I tried a different installer binary with the same result on the one symlink.

Agreed that while this is unusual, i don't believe it can be an issue with the kitchen.
[SuperR Kitchen] Seraph08:
[MENTION=5787964]SuperR.[/MENTION] throw OnePlus2 on the list for compatible. Worked on OxygenOS too

:)
[SuperR Kitchen] Omel:
A noob question

I have build a samsung Rom 5.1.1 to my note edge with success but if want to flash a new kernel afterwards I loose root why and how to avoid this

I also discovered that the secure agent needs to be stopped or deleted to avoid Knox alarms

Thanks for a great tool
[SuperR Kitchen] tdunham:
You must be flashing a true stock kernel that requires some modification or it wont work on a custom flashable rom.

Easiest way out is to flash (or reflash) SuperSU systemless root manually right after installing the kernel.

Current beta version is 2.68 which is the one included in the SuperR Kitchen.

You will need to download the full flashable version.
[SuperR Kitchen] bcrichster:
Good to see ya again [MENTION=5213176]Seraph08[/MENTION] !!

Plz use the Kitchen's "zip all devices" option after working on new devices with kitchen and upload so it can be added to the "by-name" device bank that gets updated with each zip uploaded/linked here. Then anyone who DL's & uses the kitchen can automatically generate updater scripts for the OPO ROMs.

Sent from my Gummy N9515
[SuperR Kitchen] SuperR.:
oat2dex option uses oat2dex.jar to deodex the files, and if a file fails it tries to use smali/baksmali on that file. The other option only uses smali/baksmali. Not sure which is best. It seems to depend on the device. You will need to test it for the device you are working on to see if one or both work for you.
[SuperR Kitchen] Seraph08:
will do
[SuperR Kitchen] Seraph08:
[MENTION=5787964]SuperR.[/MENTION] [MENTION=5297774]bcrichster[/MENTION]

View attachment 3702221
[SuperR Kitchen] HoochieMamma:
Hello All

I have been working on a project at my work here and would like to find out why certain things are happening. These are my findings;

-We have custom built Android Tablets using Intel SOCs, they are model number T705B product name anzhen4_mrd7 if that means anything.

-We have been provided with an updated version of these tablets running Android 5.1 which are not enrolling into our MDM software Airwatch. I have requested the ROM from manufacturer so I have them in a VM.

-Airwatch believes the tablets are rooted even though they are not from what I can see or run app wise which tells you if it's rooted or not.

-When I extract the ROM (system.img and boot.img) it says IT IS rooted in the kitchen app. I specify it to not be rooted in ROM tools menu and rebuild the system.img.

-When I flash the updated system.img the tablet refuses to boot. Even if I just decompile and then compile the system.img without any modification it still will not work. Just stays on the Intel logo forever.

I was wondering what could cause this from happening, I would have thought decompiling and recompiling the system.img wouldn't cause any issues? I also noticed the system.img rebuilt is much larger than the original but about 400MB. Might this be the issue?

Thanks
[SuperR Kitchen] SuperR.:
If the kitchen says it's rooted, it has some sort of root. It may not be setup to be used as is (possibly similar to what cm does), but there is something there. It checks many things so without having the rom it is hard to say what it found.

Unfortunately I have no experience with Intel based Android devices, but it is no surprise the new system.img is larger than the original. The original is probably sparse, and the new one is raw. If you are using fastboot to flash it that may be the problem. You can try the attached binary to make the new system.img sparse if you are running 64-bit Linux. If you are running 32-bit Linux or cygwin, you will need to find the correct img2simg binary for those systems.

Usage:

img2simg <raw_image_file> <sparse_image_file> [<block_size>]

Usage example:

./img2simg system_new.img system.img 4096
[SuperR Kitchen] crizalid8:
Which perm type should I choose? I wan to edit my updater-script after

config: galaxy s6 android 6.0.1
[SuperR Kitchen] störte:
Hi

I just updated to the latest version when i started your program. When it ask me to choose which perm to use for extracting i choose perm and after 2 or 3 seconds it is completed and the system folder is empty. did i mess something up ?

I tried now version 1.45 , 1.48 and 1.49 without sucess.

I changed now from Linux Mint to Xubuntu 15.10 and now the kitchen works again.
[SuperR Kitchen] jtash01:
error when running custom debloat

Hello. When I run a custom debloat command this error appears:

mv: cannot move ‘/home/jtash/superr/superr_S5_OK4/.’ to ‘/home/jtash/superr/superr_S5_OK4/00_project_files/debloated_files/./.’: Device or resource busy

What is the issue and how to resolve it?

Thanks.
[SuperR Kitchen] ROBERT CM:
set_metadata
[SuperR Kitchen] HoochieMamma:
Hello SuperR

It seems it must be rooted in some way or has been and not fully unrooted. I need the ROM to be fully unrooted for the MDM to not show these devices as compromised.

I have the system.img/recovery.img/boot.img here would it be too much to ask for you to be able to look at it for to find out WHY it's considered rooted? Every time I try and unroot it and rebuild the package it's a no deal on booting up. I would have gotten the manufacturer to unroot it for us but they are VERY bad in communication the whole no english thing is problematic.

If I make the image sparse could this help in making it boot?

Thanks so much.
[SuperR Kitchen] SuperR.:
Look at post #4. If you read the whole thing you may not have to ask questions that have already been answered in the future :)

It might help it boot to make it sparse depending on how you are flashing it. If you have a custom recovery you could build a rom instead. May have better luck. If you upload your images I will take a look but I can't make any promises other than finding what the kitchen sees as root.
[SuperR Kitchen] HoochieMamma:
OK, lets see what happens when I make it sparse. I'm still learning about ROM cooking etc so this tool you made has helped my understanding a fair bit.

The entire ROM is in this ZIP. I have to put the unit into DNX mode and run the bat file which seems to do everything via fastboot when I'm flashing it. The ZIP attached is the unmodified ROM direct from them

https://drive.google.com/file/d/0B4V3YNxX7QzrZmExUTBGSFdYTEk/view?usp=sharing

Thanks so much.
[SuperR Kitchen] SuperR.:
/system/xbin/su exists. Certainly rooted. I think you are not able to run root apps because you don't have a superuser app to grant root rights. The kitchen can remove all traces of all the rooted devices I have come across so far, so it will probably work for yours as well.

Regarding the boot issue, it is possible that something in your bootloader verifies the files in your system and no matter what you do it will fail to boot.

I looked at the bat file and it is strange how it works. First, it uses fastboot to boot droidboot.img, then proceeds to use fastboot to flash the partitions. I have not seen this before so I will not be much more help to you. Hopefully converting to sparse will solve the problem.
[SuperR Kitchen] bigrammy:
[MENTION=5787964]SuperR.[/MENTION]

Funny but sadly true Full explanation here http://www.urbandictionary.com/define.php?term=Noob
[SuperR Kitchen] tdunham:
Oh, now that's a good read. :sly:
[SuperR Kitchen] SuperR.:
4 5ur3 s0m LoL! 5h66t 13371337
[SuperR Kitchen] bigrammy:
I want to go on Holiday now seeing where you live :laugh:

I think your Thanks Meter must be broke BTW :eek:

I have no idea what that means but I am sure it's funny "LoL"

I will have my son translate it tomorrow and yes he actually understands this stuff :crying:

Don't let em grind you down bro your work is truly awesome. :highfive:

It seems the CIA FBI etc etc wasted there money taking Apple to court thinking the iPhone was encrypted when they should of just got a "noob" to read the text messages instead. :laugh:
[SuperR Kitchen] crizalid8:
when I flash my rom I have Error with update-binary
[SuperR Kitchen] tdunham:
What is the error and did you check your installer script in the completed zip to make sure it has the correct paths to the partitions yet?
[SuperR Kitchen] Er. Aditya:
i guess you have some permissions error or asset error , as i couldnt think of any other reason this awesome kitchen would have caused error
[SuperR Kitchen] freeover:
ERROR:

There was a problem unpacking your boot.img.

Press ENTER to continue
[SuperR Kitchen] Er. Aditya:
i am sure u have heard about the post 4 of the thread ?

[MENTION=5787964]SuperR.[/MENTION]

bro can you see why the zip failed ?

What Kitchen version? :

1.0.4.9

What Linux are you running (OS and architecture (32/64-bit))?

ubuntu 15.10 64 bit

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

samsung note 4

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

system.img

What Android version?

5.1.1

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

set_metadata

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

------------------------------------------------------

SuperR's Kitchen

by SuperR

------------------------------------------------------

ERROR:

Something went wrong. Check the zip.log for errors.

attached is the zip log

edit 2 :

sorry bro it got sorted, lack of space was the issue :)
[SuperR Kitchen] Er. Aditya:
[MENTION=5787964]SuperR.[/MENTION] bro indeed the latest kitchen adds some symlinks that cause error for me as well to flash the rom zip file

i have the working updater script so il manager but cant there be any work around about these symlinks ?
[SuperR Kitchen] SuperR.:
It would be helpful if you post the "symlinks" you are referring to as I have never added symlinks. The kitchen finds existing symlinks and converts them to entries in the updater-script. I assume you mean set_metadata entries, and if so please post them. The only thing I changed that may be causing you issues is the following:

-[COLOR="Red"]set_metadata[B]_recursive[/B]("/system/bin/dhcpcd", "uid", 0, "gid", 2000, "mode", 0755, "capabilities", 0x0, "selabel", "#CONTEXT");[/COLOR]
[COLOR="SeaGreen"]+set_metadata("/system/bin/dhcpcd", "uid", 0, "gid", 2000, "mode", 0755, "capabilities", 0x0, "selabel", "#CONTEXT");[/COLOR]

I don't think this change is your issue though.
[SuperR Kitchen] Er. Aditya:
when recovery starts to flash rom and it prints " ui_print("Creating symlinks...");

the errors shows right up there so there has to error in symlinks

these are the differences i found in my working script and new one created by kitchen

+ symlink("/system/lib/libapa_jni.so", "/system/app/SapaMonitor/lib/arm/libapa_jni.so");
+ symlink("/system/lib/libcommonpawrapper.so", "/system/app/RootPA/lib/arm/libcommonpawrapper.so");
+ symlink("/system/lib/libDioDict3EngineNativeFrame.so", "/system/app/SecDict2/lib/arm/libDioDict3EngineNativeFrame.so");
+ symlink("/system/lib/libdioiculemma.so", "/system/app/SecDict2/lib/arm/libdioiculemma.so");
+ symlink("/system/lib/libjma.so", "/system/app/SecDict2/lib/arm/libjma.so");
+ symlink("/system/lib/libjni_emailencryption.so", "/system/app/SecEmail_K/lib/arm/libjni_emailencryption.so");
+ symlink("/system/lib/libnltk.so", "/system/app/SecDict2/lib/arm/libnltk.so");
+ symlink("/system/lib/libprintspooler_jni_mr1.so", "/system/app/SPrintSpoolerLMR1/lib/arm/libprintspooler_jni_mr1.so");
+ symlink("/system/lib/libSecFileClientUnit.so", "/system/priv-app/SamsungLinkPlatform/lib/arm/libSecFileClientUnit.so");
+ symlink("/system/lib/libSLPF_scone_stub.so", "/system/priv-app/SamsungLinkPlatform/lib/arm/libSLPF_scone_stub.so");
+ symlink("/system/lib/libSLPF_security.so", "/system/priv-app/SamsungLinkPlatform/lib/arm/libSLPF_security.so");
+ symlink("/system/lib/libSLPF_transcoder_jni_kk.so", "/system/priv-app/SamsungLinkPlatform/lib/arm/libSLPF_transcoder_jni_kk.so");
+ symlink("/system/lib/libSLPF_transcoder_jni_ll.so", "/system/priv-app/SamsungLinkPlatform/lib/arm/libSLPF_transcoder_jni_ll.so");
+ symlink("/system/lib/libstlport_shared.so", "/system/app/SecDict2/lib/arm/libstlport_shared.so");
[SuperR Kitchen] SuperR.:
Every one of those symlinks exists in the system.img you extracted. The kitchen does not invent symlinks or use a list of common ones. It only converts existing ones to updater-script entries. Feel free to delete them and see if it fixes your problem. I think there is a problem somewhere else but so far have no idea where.
[SuperR Kitchen] Er. Aditya:
when i used my old working script it worked and rom flashed correctly...any other way i could get these working correctly

and also bro see on note 4 there are 2 varients 910F thats trltxx and 910G that trltdt so can kitchen create assert that has both cases checked at single line ?

this rom is for trltxx && trltdt
[SuperR Kitchen] SuperR.:
If you figure out what is causing the flashing problem and it is kitchen related, let me know. Check the differences between the 2 besides symlinks. The kitchen has always behaved the same way regarding symlinks. It does not add them if they don't already exist.

For your 2 variants, just go to ROM Tools > Asserts > Add/Remove Device asserts and add both "trltxx,trltdt"

edit: You can also take a look at your recovery.log for more information about the error.
[SuperR Kitchen] tdunham:
[MENTION=3699616]mwilky[/MENTION]

I have the Gear VR working finally. I really think its a combination of things, cant say definitively but after all the fixes you posted and updating the flashable rom to SU 2.71 beta the orientation seems to be working just fine now. So I'm still leaning toward our issue being a kernel issue and the latest SU kernel patch got it working for me.

[MENTION=5787964]SuperR.[/MENTION]

Suggesting a pretty simple addition to the kitchen due to the way systemless root modifies the kernel...

I always PREFER to have a custom modified stock based kernel to include in any rom I release and so the kernel patch routine built into SuperSU isn't really necessary and makes me cringe a little because what if it creates problems for us on a heavily modified rom. Let's face it, the users do enough to break stuff on their own without putting that into the equation. :rolleyes:

Cruising through Chainfire's SU thread he added a way to disable the kernel patch fairly easily, just flash a file called .supersu to data.

This is just a text file containing the line: SYSTEMLESS=false and it must exist before flashing systemless root.

An example file (not flashable) is attached.

So flash that to the root of the Data partition and add your custom kernel and the systemless root does its thing without interfering with an already perfectly fine custom kernel modified from source.

Not a big deal if its not added. It's a pretty simple solution for us to add on our own anyway but I thought I'd point it out in case others didn't know about it too.
[SuperR Kitchen] Alan-B:
delet
[SuperR Kitchen] SuperR.:
I just reviewed the update-binary in SuperSU 2.71. You can add /system/.supersu or /data/.supersu. Since adding this file is opting for a system install rather than systemless, it would be a lot easier to add /system/.supersu (no flashing to the data partition). I will add this option in the next release.

From the SuperSU update-binary:

# Overridable variables (shell, /system/.supersu, /data/.supersu):
# SYSTEMLESS - Do a system-less install? (true/false, 6.0+ only)
[SuperR Kitchen] SuperR.:
v1.0.5.0

Updated SuperSU to BETA 2.71.

Added option for system or systemless root for M+ and Samsung 5.1.1 roms.

Zip new devices to share now only zips the devices not already included in the kitchen.

Added OnePlus2 to device database.
[SuperR Kitchen] popito93:
hi, thanks you for your jobs

i have this problem : you may not have enough to sign this zip

help me please

galaxy note 5 N920S
[SuperR Kitchen] :
If I remember correctly if your rom is too big it can't be signed
[SuperR Kitchen] popito93:
thanks

thanks you for your reply
[SuperR Kitchen] SuperR.:
The error is exactly this "You may not have enough ram to sign this zip."

Get more ram ( and read the errors I spent time writing :p ) ;)
[SuperR Kitchen] popito93:
Okay, thanks you for your help and your time.
[SuperR Kitchen] Phant0m3rr0r:
can somebody help me,

when i try to extract the CM13 zip rom

i get the error

WARNING:

This zip does not contain an updater-script

and will not create a valid ROM base.

sorry, im new in android development..
[SuperR Kitchen] bcrichster:
Lmao.. Umm, I think the ROM needs to come from the device cuz a lot of new ROM's zips have multiple files that compile on installation (like the kernel) and needs partition layouts from the compiled kernel or actual device to do anything. Also.. I think sparce DAT zips don't have a normal updater-script anyways, if that's what your zip is..??

Sent from my Gummy Sync N9515
[SuperR Kitchen] SuperR.:
Please send a link to the rom so I can have a look
[SuperR Kitchen] NYCHitman1:
Wow. What an amazing tool. Thanks for this! :highfive:
[SuperR Kitchen] Phant0m3rr0r:
nevermind, i just fix it

my mistake when try to install the kitchen...;)
[SuperR Kitchen] russel5:
[MENTION=5787964]SuperR.[/MENTION] please enable sepolicy-injector back again on MM roms, because on Sony's phone we don't have "recovery" partition and we use custom boot.img with ramdisk.cpio and ramdisk-recovery.cpio. On this boot.img SuperSU installation will fail and not patching sepolicy proper, no matter systemless or not-systemless methode i'm will use. As a result i have bootloop or endless boot on my phone. Before in earlier versions your kitchen patching sepolicy proper and i can use this file on my custom boot.img whitout any problem. Thanks again.
[SuperR Kitchen] SpasilliumNexus:
MS announced bash support in a preview build of Windows. The first thing I did was boot into it, opted into the preview, updated, installed Bash and Git, and tried the kitchen.

Now, before anyone asks:

At least not yet, as it's in beta phase.

As soon as you run Bash from Command Prompt, it logs you in as root, with no way out of it AFAIK.
[SuperR Kitchen] SuperR.:
I may create an addon for devices that require this if you can tell me how to know if it is required. Any information such as "if this file exists, we need this mod", or "if the device is a sony running M", or anything else the kitchen can check for to be sure it is required. The problem with this sort of thing is that most devices are better off letting SuperSU do the mods so we need to be certain the SuperSU mods won't work before injecting sepolicy changes. Additionally, the sepolicy changes were a huge pain to figure out and I am not sure I am willing to do this again when new policy changes need to be added for future versions of Android (N for example is right around the corner). An alternative would be to use the old kitchen version that worked for this step, and move the modified sepolicy to the new kitchen project directory. If you know which kitchen version worked, and if I still have a copy, I could also create a standalone tool to accomplish this task.

Please run this command in Windows bash and post the resulting text:

uname -s

If it does not give you an error, it will give me info to change the behavior when running in bash on Windows. I will give you an easy script modification to try based on the result. No clue if the kitchen will work, but at least you will be able to get it to run.
[SuperR Kitchen] mrpascal:
Hello sir i am trying to use your kitchen with cygwin but its giving me error like "gawk not found" and many other errors !:crying:

please help me sir i want to use your kitchen

Thanks in advance :good:

SORRY FOR BAD ENGLISH

---------- Post added at 04:50 PM ---------- Previous post was at 04:40 PM ----------

repo is not downloading right file showing 124.4 mb and downloading 16.2 mb file !!

please help me:(:good:

thanks in advance
[SuperR Kitchen] SuperR.:
I assume you missed this part of my post you quoted:

edit: The 16.2MB file is the entire kitchen. The 124.4 is how big the repo is with all the changes still included. It has backups of all the old versions of SuperSU, Busybox, binaries, etc. No need to download the entire repo.

edit2: git clone the repo, or download the latest zip in the downloads section of the repo (linked in the OP)
[SuperR Kitchen] awadh730:
that's great man
[SuperR Kitchen] russel5:
[MENTION=5787964]SuperR.[/MENTION] you can add check sepolicy inject by name in boot.img like d5803, Aries, z3c. Something like this + mm rom. And addod would be great.
[SuperR Kitchen] SuperR.:
v1.0.5.1

Changed the text for system/systemless root option to be more accurate.

Added framework for inject-sepolicy addon.

NOTE: The inject-sepolicy addon is available in the downloads section of the kitchen repo linked in the OP. Extract it into the tools directory of the kitchen. When you go to root, you will be given a 3rd root type option "3) Inject sepolicy changes and system install". That's it :)
[SuperR Kitchen] SuperR.:
v1.0.5.2

Fixed not allowing to choose root option 2 if inject-sepolicy addon exists.
[SuperR Kitchen] :
Just made a rom with the new 910c 6.01 base. I got no errors with deodexing at all but a few apps fc. I used sva deodexer in windows to deodex the rom and got no fc at all. Not sure what is actually going on as I'm little more than a chef but it seems the latest oat2 and baksmali aren't deodexing 6.01 Sammy roms properly. Other than that couldn't be happier, kitchen works excellently