yashsingh1/xdaforums huggingface dataset:
[SuperR Kitchen] bcrichster:
No hate.. Was there, actually. I refused to bump my Linux from 32bit to 64 until SuperR's kitchen required it, since 80% of devices were KK or older OS, Lol! He also showed me that 64 bit can do all the 32 bit stuff AND MORE!

Gratefully sent from my Rooted JollyRoger_B13
[SuperR Kitchen] Melchizedekz:
你们好
[SuperR Kitchen] Dior DNA:
I'll try to figure out. And yes, it seems MTK specific. Thanks for kind support. Maybe I can find out which files to not deodex.
[SuperR Kitchen] bcrichster:
For us less curious and possibly educated individuals.. While although it certainly isn't required, Could you plz let us know the general phone model too?? Are those Galaxy Exhibits something? Most ppl look for "Samsung Galactic Turd" (for example) instead of "MF - POS.123".. Those are just hahah-funny example names, no offense intended tho.

Gratefully sent from my Rooted JollyRoger_B13
[SuperR Kitchen] Er. Aditya:
better write in english for dev and community to understand , thankyou
[SuperR Kitchen] george0884:
I do not understand, my Englishman is limited. My model is S5 G900H, thanks
[SuperR Kitchen] bcrichster:
Perfect! Ty- ..the S5 you mentioned = Samsung Galaxy S5? This helps give better ideas as to which models are being worked on. [emoji41]

Gratefully sent from my Rooted JollyRoger_B13
[SuperR Kitchen] george0884:
If he forgives, Samsung Galazy S5 G900H Exynos, info osf partitions is BOOT mmcblk0p9, RECOVERY mmcblk0p10, RADIO mmcblk0p13, EFS mmcblk0p3, USERDATA mmcblk0p21, CACHE mmcblk0p19 and SYSTEM mmcblk0p18, thanks
[SuperR Kitchen] bcrichster:
Right on! The next part ( info osf partitions is BOOT mmcblk0p9, RECOVERY mmcblk0p10, RADIO mmcblk0p13, EFS mmcblk0p3, USERDATA mmcblk0p21, CACHE mmcblk0p19 and SYSTEM mmcblk0p18) only needs be posted when requested by OP

Gratefully sent from my Rooted JollyRoger_B13
[SuperR Kitchen] SuperR.:
See post #3 for usage instructions.
[SuperR Kitchen] SuperR.:
You can still work on Lollipop roms. Use set_metadata or set_perm. You can try sparse_dat but I am pretty sure it will not work. The kitchen warns you about it after update, but does not prevent you from trying.
[SuperR Kitchen] Er. Aditya:
for me set_metadata works very well
[SuperR Kitchen] DarkHeart Z:
yeah I know that either . but not currently in the state of moving to a 64 bit platform because I currently don't have one and can't afford one for now even after wanting it badly can't migrate to a 64 bit machine and os :(
[SuperR Kitchen] bcrichster:
Yeah.. It's actually LP that's kicking you

Gratefully sent from my Rooted JollyRoger_B13
[SuperR Kitchen] DarkHeart Z:
yeah . I hope so . As well as android is open-source but a lot of manufacturer's unfair decision's causing a lot more painful route of development than anybody else . I hope rimg2sdat source will be available soon . Just to let you know android 6 marshmallow source is released for all android one device's and so do google's source trees are updated too . I wish I had an android one device . Could help ypu get deeper more info's about this project . Will get one soon .

---------- Post added at 07:35 PM ---------- Previous post was at 07:32 PM ----------

got that right been roaming around for a while to get a working source code just to compile a new kernel for my device . But couldn't dew to incomplete source code's of mt6572 chipset's . If you ever find a helpful link's or so please let me know that would be grateful :)
[SuperR Kitchen] zameer_yus:
how to change a file or directory label to u: object_r:system_file:s0

in selinux
[SuperR Kitchen] SuperR.:
Change it in your file_contexts file if you want to. If it is not listed in file_contexts, the kitchen automatically considers it a system_file
[SuperR Kitchen] zameer_yus:
i dont understand can you please explain

and it will be great if you guide me to do it without kitchen

because i am not using kitchen and even i m not sure if this kitchen has support to make .img file
[SuperR Kitchen] bcrichster:
If you're not using his SuperR Kitchen, then how do you expect him to help you? [emoji33] This thread is related to his SuperR Kitchen, which has very many functions, even as far up in Android OS's as the new Marshmallow 6.0.. [emoji87] If you don't want to use his Kitchen, then try the deprecated ArchiKitchen, dsixda Kitchen, or Android Image Kitchen: almost all functions of all previously mentioned kitchens are duplicated and kept currently functional AND IMPROVED by SuperR with his Kitchen in this thread OP. Try the dang SuperR Kitchen, bro! [emoji12]

Gratefully sent from my Rooted JollyRoger_B13
[SuperR Kitchen] ashyx:
Unfortunately deknoxing on Samsung tab A running 5.0.2 causes it to hang on boot animation.

Tried exactly same settings with and without knox. Boots fine with knox.
[SuperR Kitchen] SuperR.:
If there is a universal list of removable knox stuff, I am happy to use it. I don't own a samsung device so I can't do any testing. Let me know if you figure out what the kitchen removes when deknoxing that causes your issue. Thanks
[SuperR Kitchen] enotar:
I think I have the same issue

deodex and deknox hang Samsung device at boot P600 tablet
[SuperR Kitchen] Er. Aditya:
if you have searched the thread..... after removing knox place back the libs files into rom zip and then try
[SuperR Kitchen] SuperR.:
The kitchen removes all these:

system/lib/libknox*

Are those the files you are moving back?

on the note 4, they are:

system/lib/libknox_encryption.so

system/lib/libknox_km.so

system/lib/libknox_legacy_ode_km.so

system/lib/libknox_migration.so

system/lib/libknoxvpnfdsender.so
[SuperR Kitchen] Er. Aditya:
bro these are the files that cause bootloop , i dint had the time to test if its just one of these or all of these but at the moment i know that placing all these files back stops bootloop

system/lib/libknox_encryption.so

system/lib/libknox_km.so

system/lib/libknox_legacy_ode_km.so

system/lib/libknox_migration.so

system/lib/libknoxvpnfdsender.so
[SuperR Kitchen] SuperR.:
It is easy to not remove them, just not sure if this problem applies to all samsung devices. Any idea?
[SuperR Kitchen] Er. Aditya:
probably as if i remember [MENTION=1097804]sawdoctor[/MENTION] said that archi kitchen dsnt removed these libs...so i assume this might probably cause problems to most sammy devices , even on my wife's note 3 running custom rom has these libs into it , after i publish my update / by this week end il let you know if its exact 1 file or all :)
[SuperR Kitchen] SuperR.:
v0.9.4.3

Changes:

Do not remove knox libs when removing knox.
[SuperR Kitchen] Er. Aditya:
your simply awesomr bro
[SuperR Kitchen] Androidwizzard:
Well. I am too late in this case but may confirm:

Removing Knox means deleting Knox related apps and not more - so I assume everything's ok now. Good job :highfive:
[SuperR Kitchen] ashyx:
[MENTION=5787964]SuperR.[/MENTION]

Just want to confirm new version with knox modification is working fine now, no issues.

However might I make a suggestion regarding the menu item for removing knox as it's a little confusing at first.

Rather that the menu stating Remove Samsung Knox (Current: Yes) it would be better to actually use 'Present' and 'Removed' as it can be a little confusing as to what state 'CURRENT' refers to.

For instance Knox installed: Remove Samsung Knox (Current: Present)

Knox removed: Remove Samsung Knox (Current: Removed)

Apart from that the kitchen is working spot on and is the kitchen of the moment. Keep up the excellent work. :good:

---------- Post added at 02:48 PM ---------- Previous post was at 02:42 PM ----------

Knox can be totally removed. It has been done by Tamirda for the Tab S. Under KNOX version in About device there is nothing at all listed for KNOX.
[SuperR Kitchen] Er. Aditya:
removing that detail is a smali edit , not by replacing apks
[SuperR Kitchen] Androidwizzard:
True, and I have made a mistake:

Users of this kitchen with Samsung devices running latest 5.1.1 must be careful:

As soon as stock kernel detects any kind of modification like root it will loop - so use this kitchen with caution.
[SuperR Kitchen] SuperR.:
How are these mods being made successfully outside this kitchen?
[SuperR Kitchen] Er. Aditya:
on 5.1.1 you will need a permissive kernel to be able to root and boot , just placing Su zip into your rom zip with stock kernel will make it bootloop
[SuperR Kitchen] SuperR.:
Wow, really? Nice work Samsung lol

Would an init.d script that sets permissive load fast enough to prevent the bootloop or does it need to be a source built permissive kernel?
[SuperR Kitchen] Androidwizzard:
I have sent you the correct boot.img modification for Note 5 some time ago and we have talked about sepolicy. You surely remember.
[SuperR Kitchen] SuperR.:
Yes, and you surely remember that I don't have a proper method to modify sepolicy in Linux for use in the kitchen. Unfortunately your reply leaves my question unanswered. Will an init.d script that sets permissive load fast enough to prevent the loop?
[SuperR Kitchen] Er. Aditya:
haha sammy and its **** ..... this i figured many days back with 5.1.1

i havnt tested the script thing , as i couldnt find a script thats working on 51.1 to set se permissive...but yes surely have tested the kernel built in set to permissive way and thats the only way to boot a 5.1.1 rooted rom
[SuperR Kitchen] ashyx:
Not true, using Supersu v2.50+ (not v2.56) and some modifications to the ramdisk is all that is required to boot a stock kernel and root on LL 5.11.

I have done this mod on the Tab S2.
[SuperR Kitchen] Er. Aditya:
thanku i just shared the method i know , can you explain what modifications ?
[SuperR Kitchen] SuperR.:
The kitchen currently includes SuperSU 2.5.2. Regarding the ramdisk mods, are they the same ones [MENTION=5564860]Androidwizzard[/MENTION] posted that require sepolicy modification? If not, please share the ramdisk mods. Thanks

edit: just realized why I stopped testing the sepolicy mods. I need someone to test things. I made a boot.img a while back with these mods and it looped. I am still not sure if that was the method I was using to unpack/repack or the mods themselves.

Can someone running one of these 5.1.1 Samsung devices verify that upack/repack with no mods still boots properly? It is important that this is tested using kitchen version 0.9.3.8 or higher as the boot tools have changed. Once that is confirmed working, please send me a stock boot.img and I will modify and upload for testing. Thanks

edit2: in the meantime, if someone wants to test with a permissive init.d script, I have attached one here. In the kitchen, go to boot tools, unpack boot.img, add init.d support, repack boot.img, extract the attached zip into system/etc/init.d/, add root to the rom, build rom zip, and test. Thanks
[SuperR Kitchen] ashyx:
Yes the Sepolicy needs to be modified in the Ramdisk to overcome samsungs rooting restriction policy in 5.1.1 kernels.

Pretty much anyone can do this once they have extracted sepolicy from the ramdisk and rooted a device with supersu v2.50+

Any script is unlikely to succeed as the kernel will simply refuse to boot the rom if it detects root.
[SuperR Kitchen] ashyx:
It would be quite easy to create a script that simply pushes SEpolicy to a connected device and patch it via ADB commands then pull the policy back into the unpacked ram disk. The only caveat is that the device has to be rooted and be connected to the PC.

Seeing as you already have this function built into the kitchen for pulling images its just a simple menu item to add.

Here's the script, it simply needs modifying to use the correct directories:

adb push sepolicy /data/local/tmp/sepolicy

adb shell su -c "supolicy --file /data/local/tmp/sepolicy /data/local/tmp/sepolicy_out"

adb shell su -c "chmod 0644 /data/local/tmp/sepolicy_out"

adb pull /data/local/tmp/sepolicy_out sepolicy_out
[SuperR Kitchen] SuperR.:
I agree it would be easy, however it requires the user to have a SuperSU 2.50+ rooted device on hand and not everyone has this. I am currently working on sepolicy mods without this requirement using a Linux binary called sepolicy-inject. This will suit the kitchen much better if I can get it working.
[SuperR Kitchen] ashyx:
Yes 'm aware of it. looked at it once or twice myself. I suppose you will need to find out what gets patched by supolicy, chainfire is a bit quiet on this for some reason and won't spill the beans.

However I think its would just be a case of dumping the contents of sepolicy with supolicy before and after patching then using sepolicy-inject.

Good luck with it, I hope you have success . It's great what you have done so far ;)
[SuperR Kitchen] SuperR.:
This has already been done. Posted the results several pages back. Here are the differences if you are interested :)
[SuperR Kitchen] ashyx:
Thanks, looks like it should be easy enough to patch if you can get your head around it.
[SuperR Kitchen] enotar:
Just tried ne version but versus last one this one don't run.

Give me error "simg2img,img2simg, or make _ext4fs could not be built

Libraries already install before....

Any idea

Edit: works now, changed directory
[SuperR Kitchen] SuperR.:
Glad to hear it :)
[SuperR Kitchen] SuperR.:
Here is a test boot.img for the SM-N920I. I have made all the required changes in the ramdisk, and the sepolicy is modified in Linux with sepolicy-inject. I hope someone will test it with root to see if it works. If it does, I will update the kitchen.

SM-N920I_test_boot.zip

From build.prop where this boot.img came from:

ro.build.display.id=LMY47X.N920IDVU2AOJ4

ro.build.version.incremental=N920IDVU2AOJ4
[SuperR Kitchen] enotar:
Is it possible to include in the zip file recovery.img from TWRP with boo.img patched to work with 5.1.1 on my tablet?

If yes what should I do?

I have both files

Thank you
[SuperR Kitchen] Androidwizzard:
Loops, sorry to say :(
[SuperR Kitchen] SuperR.:
Thanks for testing. Would you mind unpacking/repacking/flashing a boot.img in the kitchen that is known working? I want to make sure unpack/pack is confirmed working so we are sure the sepolicy mods are the issue.
[SuperR Kitchen] blockbuilder643:
Trying

I'll try this.
[SuperR Kitchen] Androidwizzard:
Sure, I'll report asap (soon).
[SuperR Kitchen] ashyx:
Might I make a suggestion.

Not sure what device you own, but if it's Exynos you should be able to use that as a reference device to modify Sepolicy with Supolicy for the n920i.

Then repack the boot.img.

At least this way you will know if the Sepolicy modifications do actually work for that device. I'm pretty sure they do.

Its then just a case of tweaking sepolicy-inject to make the right changes.
[SuperR Kitchen] Androidwizzard:
Done and looping too, so ...
[SuperR Kitchen] ashyx:
Is that looping with or without root? It needs to be a clean system.
[SuperR Kitchen] Androidwizzard:
It is with rooted rom - otherwise I got to make a clean one first
[SuperR Kitchen] SuperR.:
rooted rom yes, but also with a modified boot.img that works with rooted roms, right?
[SuperR Kitchen] Androidwizzard:
correct. KetanRom has stock kernel with sepolicy modified. LINK (just for info)
[SuperR Kitchen] ashyx:
Well it will never work then. As SuperR states it needs to be a working boot.img in the first place.

If the Sepolicy has already been modified to work in that boot.img then there is no reason why the unpack/repack shouldn't work as that is what would have been done in the first place.
[SuperR Kitchen] Androidwizzard:
Correct me if I'm wrong: I unpacked and repacked that working stock kernel and it looped, so there seems to be an issue while packing
[SuperR Kitchen] ashyx:
Yep must be, see edited post above.
[SuperR Kitchen] enotar:
good news I have boot here with SM-P600 5.1.1
[SuperR Kitchen] SuperR.:
There seems to be a problem with the unpacking/repacking for sure. Now someone just needs to tell me what is wrong, because it works on most other devices as it is. I don't have a device that does not work to test on :(
[SuperR Kitchen] Androidwizzard:
Size has changed - 8 KB bigger now
[SuperR Kitchen] ashyx:
I wish I could assist but unfortunately I don't have a 5.1.1 device.

---------- Post added at 12:05 AM ---------- Previous post was at 12:00 AM ----------

I take it you're using the kitchen to unpack/repack?
[SuperR Kitchen] Androidwizzard:
That's what I should test ;)

BTW: Samsung's not to blame to implement all security they can gain to make Samsung pay safe(r).
[SuperR Kitchen] bcrichster:
Wooooowww!!! Bahahahah! Poor terminal.. Lol
[SuperR Kitchen] enotar:
Samsung SM-P600 boot perfectly after creating the zip rom from stock, deodex rooted, Knox free. Only problem, I cannot get wifi but rom is rooted

I create rom from Samsung stock 5.1.1 deodex, rooted and get rid of Knox only from Superr Kitchen

Any idea what could be wrong for the wifi?

thanks for this fantastic tool
[SuperR Kitchen] bcrichster:
[MENTION=718594]SuperR[/MENTION]!! Our Warp4G's!! We have AOSP & CM12.1 ROMs. I'd go with TESLA
[SuperR Kitchen] bcrichster:
Sorry... 5.1.1 kernels.. Or are we only dealing with Samsungs at the moment?

Edit: My bad.. Needed do more reading. Carry on, Lol.
[SuperR Kitchen] albertmurcia:
at samsung galaxy tab LTE t805 You split, putting the bookshops knox that in my case is four, with script that generates the kitchen.

The only thing that has not installed the file is put the extra apps.

I appreciate it very much.
[SuperR Kitchen] ashyx:
I'm the only one who feels like they've dropped on to another planet here?

I don't understand anything from the last 2 posters! :what:
[SuperR Kitchen] bcrichster:
Sorry.. [MENTION=4899305]ashyx[/MENTION] I was being excited and oblivious last night, please disregard last night's posts
[SuperR Kitchen] enotar:
Wifi problem

Any idea why wifi cannot turn on after flashing

Sorry to bother with that

Thank you
[SuperR Kitchen] sefrcoko:
Edit your build.prop to change securestorage support to "false" and reboot...that should fix wifi.
[SuperR Kitchen] enotar:
Thank you but that doesn't work, when I try to turn on wifi after few seconds it turn off, Bluetooth works

Any idea?
[SuperR Kitchen] albertmurcia:
ROM created for the galaxy tab.

the applications of the folder data, can not install them

Enviado desde mi SM-T805
[SuperR Kitchen] Er. Aditya:
Which apps ?? Make sure the package names are correct else it wont install them
[SuperR Kitchen] SuperR.:
I am nearly certain I have the sepolicy being modded correctly and completely now using sepolicy-inject. Need to figure out how to get the boot.img unpacked/packed properly and we should be good. [MENTION=5564860]Androidwizzard[/MENTION] First thing I will look at is why the size is changing. That may very well be the problem. Thanks for pointing it out.
[SuperR Kitchen] fhem:
[MENTION=5787964]SuperR.[/MENTION] thank you sir. Your kitchen is the best!!!!!
[SuperR Kitchen] SuperR.:
I think I figured out the issue with unpack/pack on the Note 5 and probably many others. Please try this boot.img on a rooted N920I and let me know how it goes. It has all the ramdisk mods, including sepolicy, all done by the test kitchen. If it boots, I will push the update. Thanks :)

SM-N920I_test_boot_2.zip
[SuperR Kitchen] Androidwizzard:
Nope, again loop :crying:
[SuperR Kitchen] SuperR.:
I wonder if I am using the correct boot.img lol. Remember when you sent me the rooted and stock unpacked boot.img'sfor comparison? Is that stock the correct one for your device? I did not use that one but i will give it a try if it is the correct one. I used one from another stock firmware for the SM-N920I. Let me know and thanks for testing :)

edit: never mind. It is the same img :( Are there any tools you have used to unpack/repack this boot.img with success?
[SuperR Kitchen] Androidwizzard:
Please wait - I have found a problem that could have caused my last loops, must check what's wrong.
[SuperR Kitchen] Androidwizzard:
I had to setup my device with a clean installation first and then your kernel WORKS :highfive:

FYI I've been running a custom permissive kernel when I flashed yours and that failed - no idea why :confused:
[SuperR Kitchen] SuperR.:
v0.9.4.4

Changes:

Added support for rooting Samsung 5.1.1 roms.

Changed current knox status to be more friendly.

Fixed unpack/pack boot.img for Samsung and probably others.

edit: There is one new package that needs to be installed to compile sepolicy-inject so you may get the notice that it did not compile. The only one that is new in v0.9.4.4 is "libsepol1-dev". You can run the following to get it installed on Debian based systems:

sudo apt-get install libsepol1-dev

I will need the 32-bit sepolicy-inject binary once the kitchen compiles it for someone running 32-bit Linux. Thanks
[SuperR Kitchen] ashyx:
Excellent work. :thumbup:

---------- Post added at 06:25 AM ---------- Previous post was at 06:12 AM ----------

Rooted too?
[SuperR Kitchen] Androidwizzard:
Yes, of course :good:
[SuperR Kitchen] SuperR.:
A note/question about rooting Samsung 5.1.1 roms:

Currently, the kitchen will perform the sepolicy and ramdisk mods on EVERY 5.1.1 Samsung device when choosing to root the rom. Is this correct or should there be more conditions ( ie. ro.board.platform = exynos5 ) ?
[SuperR Kitchen] ashyx:
Nothing needs to be done except for the modifications to sepolicy in the Ramdisk and in any case will still happily boot with this mod even if the device is not rooted.

AFAIK from what I've gathered from the supersu thread all samsung 5.1.1 and android 6.0 devices need this patch with stock kernels.
[SuperR Kitchen] albertmurcia:
the data / app, do not install it. it may be for the script?

https://www.dropbox.com/s/fb3lmazujiytsxu/updater-script?dl=0

Enviado desde mi SM-T805 mediante Tapatalk
[SuperR Kitchen] SuperR.:
Are you sure nothing else needs to be modified in the ramdisk? Here are the specific posts detailing what the kitchen is currently doing besides the sepolicy changes.

http://xdaforums.com/showpost.php?p=63209803&postcount=9

http://xdaforums.com/showpost.php?p=63225712&postcount=17

If these additional ramdisk changes are not required I can certainly remove them.

To clarify, are you saying that in addition to Samsung 5.1.1 roms, ALL Android 6.0 roms need the sepolicy changes and not just Samsung? Just want to be sure before I make that change. Thanks :)
[SuperR Kitchen] enotar:
Tested 3.4.4 Samsung SM-P600 deknox, deodex, rooted; rom boot but black screen, it looks like a framework issue. UI don't load only the status bar icons at the top.
[SuperR Kitchen] ashyx:
Tbh I couldn't attest to the other modifications on other Samsung devices, whether required or not.

For me sepolicy modification only was required.

According to Chainfire's post here and the info gleaned from the supersu thread it seems all android 6.0 devices require the mod.

http://xdaforums.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
[SuperR Kitchen] enotar:
Yeap /app/data apps don't install for me too and still issue with Wifi not turning on, getting me crazy, maybe the modem...??
[SuperR Kitchen] SuperR.:
[MENTION=5564860]Androidwizzard[/MENTION] What are your thoughts on these additional ramdisk changes? They are present in the rooted SM-N920I boot.img you sent a while back for comparison.

[MENTION=4899305]ashyx[/MENTION] What device are you working on that only requires the sepolicy mod?
[SuperR Kitchen] bcrichster:
Request, [MENTION=5787964]SuperR.[/MENTION]? In the extract menu, I was wondering about a full flash.img extraction option (instead of just System, boot, recovery) to pull everything for in case ppl need to mess with modems, aboot stuff, whatever for a device? ..PLZZZ? Lol

Gratefully sent from my Rooted JollyRoger_B13
[SuperR Kitchen] Androidwizzard:
From my point of view only ramdisk changes are required (beside SuperSu 2.50+) - this is already tested on most Note 5 devices.