yashsingh1/xdaforums huggingface dataset:
[SuperR Kitchen] SuperR.:
The current bloat list intends to be a comprehensive list of apps that do not need to be on the device in order for it to run properly. I realize everyone has their own preference which is why the bloat_custom file exists. I suggest copying the contents of the bloat file to bloat_custom and modify bloat_custom to your preference. Yes, odex files will be removed if you follow the same syntax as you see in the bloat file for the existing apps.
[SuperR Kitchen] brainvision:
thanks..

It also seems to me that if I launched once custom debloat and then add other stuff there it will always says Already Debloated, wouldn't it?

Do you have any suggestion how to solve that? The Revert Debloat only works for default debloat..

EDIT: sorry I'm uploading my device info again because I did not used the integrated feature last time, I think it's pratically the same stuff btw..

EDIT2: SOLVED the custom debloating, sorry
[SuperR Kitchen] lonegolfs15:
Someone have problem with android 7.1.1, installs fine without error but setup wizard fc
[SuperR Kitchen] simo255:
Hello,

When i go to boot/recovery tools

I have 'checking status' and no reaction after that ! Please could anyone help me ??
[SuperR Kitchen] bcrichster:
Plz read post #4

Sent from CM12.1 *N9515*
[SuperR Kitchen] SuperR.:
I cracked open Android 7.1 Pixel firmware today. It seems most things will work in the kitchen already. A few things were a bit strange:

1. It appears the system.img and the boot.img both contain a ramdisk.

2. There is no recovery.img in the Pixel firmware and no by-name/recovery

3. There is a new partition layout using an a/b naming scheme, and I am not sure where to flash things yet.

4. Only framework is odexed

It is still early and there is no custom recovery for the Pixel yet, but I was curious :)
[SuperR Kitchen] allurba:
In version 2.1.2.0 build flasable boot does not work, sign the zip:

WARNING:

You May not Have enough ram to sign esta zip.

In the version v2.1.1.8 works perfect.
[SuperR Kitchen] Captain_Throwback:
Yeah - the boot.img is really just a recovery.img in disguise, and the system image "ramdisk" is what used to be the boot.img ramdisk. It's going to make rooting a bit more challenging/annoying, and require some sort of kernel patch just to make it boot.
[SuperR Kitchen] bcrichster:
The Horror of those MoFo's..!! [emoji90] I would bet there's not actual benefit in the programming except to create unnecessary hurdles.

Sent from CM12.1 *N9515*
[SuperR Kitchen] bigrammy:
1 and 2: That Sounds very much like the Sony way of doing things to me :confused:
[SuperR Kitchen] manotroll:
how to use these files in it?

http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=G530BT

for what went to see this and part of the source code bt530
[SuperR Kitchen] TheHiman:
I had some "no free memory" problems on phone everytime after deodexing a SM-G900F rom (CPI7/VIA).

For this rom only the framework needs to be deodexed, so i made some experiments with different oat2dex-Versions.

After first giving up, i made a deodex with this tool:

http://xdaforums.com/android/software-hacking/tool-batch-deodex-rom-t3313150

Here an older oat2dex.jar was used, and after success with the phone i used this oat2dex-version in the kitchen

and repeat the whole process. Finaly the phone hungs at the initial boot process.

I figured out, that the problem is NOT the deodexing process (the content inside the resulting files are identicly to the ODTRTA-Tool.)

The main reason is the 7z-packaging that is used! - With the ODTRTA-tool i used "aapt" instead 7z - and this is working.

So, my wish for the next update: please add aapt compression method beside 7z. and make it selectable in the menu.

A 32bit prebuild binary is included with the ODTRTA-Tool.
[SuperR Kitchen] hohassan444:
[MENTION=5787964]SuperR.[/MENTION]...please i noticed that in the latest versions of kitchen ; if i use metadata option the rom installer stuck at formating...it does not pass to extracting. however , there is no problem in sparse option.this problem does not occur in earlier versions (i have many of them).

N.B..i have lollipop 5.1

thanks in advance
[SuperR Kitchen] Mennpiko:
+1 It happens the same in 7.1.1

Enviado desde mi Nexus 6P mediante Tapatalk
[SuperR Kitchen] SuperR.:
Say yes anyway if you want to try. It might work fine. The kitchen tries to estimate how much ram you will need, but it is not perfect.

You don't. That is Android source code.

Very interesting. I will push an update as soon as I get time that uses aapt instead of 7z to add the classes*.dex into apk and jar files. It can't be worse than what we have now lol. It would be great if this ends up being the solution to the deodexing issues. Thanks for the suggestion :)

Nothing has changed in the latest versions regarding set_metadata. Compare your updater-script to one that works and and see where the difference is. If you are unsure how to do this, send them both and I will check them out.

Android 7.1.1 (if it exists) is not fully supported yet. As I mentioned in my last post, I just unpacked 7.1 pixel (sailfish) firmware for the first time and I am not even sure how to deal with some of the stuff. It will be supported at some point for sure :)
[SuperR Kitchen] SuperR.:
v2.1.2.1 (Donate version)

Changes:

Fixed issue where M and N twframework.jar and possibly others would not get deodexed using smali/baksmali and oatdump.

Use aapt to pack classes*.dex instead of 7-zip.

Ok, let's give it a try. There is no aapt/7z option in this version. It only uses aapt for apk/jar packing. If this works out I will update the standard version. If it does not work out, I will revert to the 7z method. Please let me know how it goes :)
[SuperR Kitchen] lonegolfs15:
Hi there, android 7.1.1 is developer preview NPF10C for nexus 6p and nexus 5x
[SuperR Kitchen] bcrichster:
Almost make me wanna buy a Samsung, to help out.. [emoji12]

Sent from CM12.1 *N9515*
[SuperR Kitchen] SuperR.:
I just unpacked 7.1.1 developer preview and it seems pretty much the same as 7.0 as far as directory structure, framework, etc. Can you list all the things you did in the kitchen before building the rom zip? Actually, all the questions at the top of post #4 would be good because I need to know what I am troubleshooting. "Setup wizard fc" is pretty slim info :)
[SuperR Kitchen] nightcrow:
Cooking as we speak with smali/baksmali on a stock Samsung 6.0.1 rom with Touchwiz! Will report my findings.

Edit: Succes!!! Tested and confirmed working. Deodexed (smali/baksmali) the rom with the kitchen and no errors while deodexing and after boot-up. This kitchen rocks. Definitely worth the donation! :good:
[SuperR Kitchen] nightcrow:
Thanks a lot for sharing this! Seems like it's the solution for the deodexing error mystery :good:

(On a Samsung stock 6.0.1 rom with Touchwiz)
[SuperR Kitchen] SuperR.:
v1.1.1.1 (Standard version)

Changes:

Fixed issue where M and N twframework.jar and possibly others would not get deodexed using smali/baksmali and oatdump.

Use aapt to pack classes*.dex instead of 7-zip.

You have no idea how happy I am to hear this :) Thanks for testing and reporting back.

Huge thanks to [MENTION=7098311]TheHiman[/MENTION] for the aapt suggestion :)
[SuperR Kitchen] TheHiman:
And now i have another challenge:

Firmware MM 6.0.1 for Samsung SM-J510FN (J510FNXXU1API4) INU

Copy the regulary oat2dex.jar from the ODTRTA-Tool to the kitchen (This is the version: 2.0.8-227f79ca-dirty).

By using ODTRTA-Tool only one .apk (Google Photos) can´t be deodexed. All others files are fine.

Including framework with aapt.

And now do the same with the kitchen and the SAME oat2dex.

Set The Heapsize manual to 4096 before to be sure you have enough ram.

...and then start the deodexing. Result: Nearly 14 .apk/.jars with errors !

By using smali/baksmali no errors so far.

Curious: Why has the same oat2dex.jar with the ODTRTA-Tool just one deodex-error, and

the kitchen many many files, by using exact the same oat2dex-file ?

Can you try with the firmware, named above, and compare booth tools and maybee with different

methods ? As i can see, there are problems with apks, which have 10-30 small .dex files in it.

(Like the Sec_Email.apk)

The special Problems with this firmwares are the Samsung xt9-keyboard and the Sec_Email-things.

At the framework side kitchen can´t repack 8 or more .jar files :(
[SuperR Kitchen] Ssbroly:
hi, I have a problem. When I flash my rom, everything goes well, but when I reboot, the recovery starts alone .. thank you for your help!
[SuperR Kitchen] SuperR.:
I suggest using oatdump or smali/baksmali for deodexing. oat2dex causes too many problems and now there are 2 other options that work better :)

Do you think you provided enough information for anyone to help you? (HINT: check post #4)
[SuperR Kitchen] russel5:
[MENTION=5787964]SuperR.[/MENTION] hello. I don't know why, but heapsize settings not working for me.

When i choose manual enter i only get this error:

ERROR:
Heapsize must be equal to or less than the amount of
physical ram installed.

Physical ram:

Press ENTER to return to the Misc Tools menu

As you see the kitchen can't detect my physical memory.

If i run

free -m

i get this

russel5@HomeBuild ~/develop/superrs-kitchen $ free -m
total used free shared buff/cache available
Память: 15971 770 9157 55 6043 15049
Подкачка: 0 0 0
russel5@HomeBuild ~/develop/superrs-kitchen $

OS - Linux Mint 18 Cinnamon 64
[SuperR Kitchen] Mennpiko:
-rom MPF10C 7.1.1

-perm type: sparse_dat

-root supersu

-boot.Img keep ramdisk,insecure,dm-verify,forcencrypt

-debloat rom

-build rom full,system.img

Compiling and installing the rom fine, but when you press start the wizard gives FC, thanks

Enviado desde mi Nexus 6P mediante Tapatalk
[SuperR Kitchen] SuperR.:
Ah, this is because the kitchen is looking for "Mem:" output from free and your version gives "Память:" instead. I will fix this in the next update. For now, if you want a custom heapsize you can create a new file.../kitchen/tools/heapsize and enter only the numeric value in MB (ex. 2048MB you would enter only 2048). Save the file and the kitchen will use it. Sorry for the trouble. The output language of free did not even occur to me.

Try using set_metadata. rimg2sdat is outdated and may not work well with 7.1.1. If that does not work, try without modifying your boot.img.
[SuperR Kitchen] _that:
"man free" says that it parses /proc/meminfo, doing the same in your script should be safer than trying to parse the output of "free".
[SuperR Kitchen] TheLogicalGamer:
I have a noobish question. Can the kitchen create a flashable zip of just the framework, app, and priv-app folders? Or would I need to modify the update script?
[SuperR Kitchen] bcrichster:
Yes, but get the donate version

Sent from CM12.1 *N9515*
[SuperR Kitchen] TheLogicalGamer:
[MENTION=5297774]bcrichster[/MENTION] Already done thanks :) could I pm I'm sorta having a problem unrelated to my previous post, and I'm not really sure where to post it.
[SuperR Kitchen] bcrichster:
Sure, No problem!

Sent from CM12.1 *N9515*
[SuperR Kitchen] orgulloso4202:
How can I get the system to support ext4 file system on an microSD card?
[SuperR Kitchen] bcrichster:
That may be kernel work, bro..

Sent from CM12.1 *N9515*
[SuperR Kitchen] orgulloso4202:
Thanks, I was afraid of that since my kernel we don't have the source code on the Verizon s7 edge.
[SuperR Kitchen] bcrichster:
Verizon itself will be your biggest block of all Carriers.. Starting to think Boost Mobile has become 2nd place this last year [emoji85] [emoji86] [emoji87]

Sent from CM12.1 *N9515*
[SuperR Kitchen] :
I don't get why people still buy phones from them, if you want ROMs and stuff don't buy from VZW it's not that difficult.
[SuperR Kitchen] _that:
Are there really any Android kernels out there that don't support ext4? At least /system and /cache use usually ext4.

However vold probably needs extra care to support ext4 on microSD cards.
[SuperR Kitchen] SuperR.:
v2.1.2.2 (Donate version)

Changes:

Reverted to /proc/meminfo for physical ram detection.

oat2dex for M: Removed option to keep framework when errors occur.

oat2dex for M: Check for errors after finished deodexing the entire rom and report problems all at once.

oat2dex for M: Updated framework deodex algorithm.

Updated smali/baksmali to latest commit.

v1.1.1.2 (Standard version)

Changes:

Reverted to /proc/meminfo for physical ram detection.

oat2dex for M: Removed option to keep framework when errors occur.

oat2dex for M: Check for errors after finished deodexing the entire rom and report problems all at once.

oat2dex for M: Updated framework deodex algorithm.

Updated smali/baksmali to latest commit.

I was originally using /proc/meminfo and somebody said it was not working, thus the change to free in the first place. I have reverted back now. Hopefully it will work :)
[SuperR Kitchen] Pyr0ball:
I'm having an issue (which I think I've figured out at least a workaround for) with being able to pull the system images from a rooted device that has very little internal storage. Currently the script only checks /sdcard and /data for locations to write and pull images to/from. A fair number of new devices have a small internal storage partition, but an sdcard slot that could be pulled from as well. For my own use, I've edited the pullimga function to write to my external SD card:

pullimga() {
banner
echo "$bluet$t_general_extracting $pullimg ...$normal"
echo ""
if [[ -f $base/tools/devices/$devicename/superr_mmc ]]; then
partbyname=$(grep "$pullimg" $base/tools/devices/$devicename/superr_mmc | gawk '{ print $1 }' | sed 's/\\//g')
$adb shell su -C "dd if=$partbyname of=/storage/sdcard1/$pullimg.img"
else
$adb shell su -C "dd if=$byname/$pullimg of=/storage/sdcard1/$pullimg.img"
fi
echo ""
echo "$bluet$t_general_extracting $pullimg ...$normal"
$adb pull /storage/sdcard1/$pullimg.img $romdir/$pullimg.img > $logs/main.log
$adb shell rm /storage/sdcard1/$pullimg.img
pullimg=""
}

I think with some tweaking I could add a function to specify the external sd card or OTG drive as a destination
[SuperR Kitchen] SuperR.:
Good idea :) I will add the option to choose or enter manually in the next version. If you send me all the device paths you want as options I will add them. Currently I have:

/sdcard

/storage/sdcard1

Enter manually
[SuperR Kitchen] lonegolfs15:
What Kitchen version? v2.1.2.2

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

What device are you working on (make/model)? nexus 6p and 5x

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

What Android version? 7.1.1

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

What did you do after extracting and before building? root, remove dm-verity and Remove forceencrypt

Were there errors on the screen if you scroll up in the terminal? none
[SuperR Kitchen] SuperR.:
I have no idea if root, dm-verity, or forceencrypt work on 7.1.1. Try without any modifications and see if it boots.
[SuperR Kitchen] _that:
Another idea that doesn't need temporary files at all:

adb exec-out su -c "cat /dev/block/mmcblk0p2" > p2.img
[SuperR Kitchen] SuperR.:
I have clearly not kept up with my adb commands :o This is a much better approach. Thank you for pointing it out :)

edit: except the resulting system.img will not mount :(

edit2: trying adb exec-out with dd now

edit3: no luck. Using cat and dd both produce an image the correct size, but neither of the img's will mount. I will keep researching.

edit4: [MENTION=4878287]_that[/MENTION] - Using the same commands, the generated img files from my Moto E 2015 mount perfectly but the Nexus 5X img files do not. Any ideas why this might be?
[SuperR Kitchen] xNako:
The default root of cm13 don't work on my customized cm13 build with this kitchen. Why? Should I root with supersu root? Thanks.
[SuperR Kitchen] bcrichster:
What did you change, in which order, what are your permission settings..??

Aka: Read post #4

Sent from CM12.1 *N9515*
[SuperR Kitchen] xNako:
What Kitchen version? Last

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

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

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

What Android version? 6.0.1

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

What did you do after extracting and before building? Delete some apps of cm.

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

Can you send a link that does not require registration to the files you started with (nandroid, system.img, boot.img, etc)? https://download.cyanogenmod.org/get/jenkins/184735/cm-13.0-20161023-NIGHTLY-piccolo.zip
[SuperR Kitchen] bcrichster:
OK.. Which apps did you delete? There are very few apps in a flashable Cyanogenmod ROM that can be removed without inducing significant problems, as the actual installation zip is barebones to begin with.. Also try set-metadata perms and see if the problem persists

Sent from CM12.1 *N9515*
[SuperR Kitchen] xNako:
Email, Eleven, CMupdater, Gallery, AudioFx, OneTimeInializer, Provision, Snap, CMFileManager, LockClock, Gello and Hexolibre.

And I want to add GApps manually without flashing but don't work. I add the apps of OpenGapps keeping default PackageInstaller of CM and deleting Provision but don't work. Thanks
[SuperR Kitchen] bcrichster:
Um.. You may need to also make sure of the correct perms for the app itself (rw-r--r--). Just moving an app don't work with the system apps. Make sure all folder perms are the same as well

Edit: disregard my post

Sent from CM12.1 *N9515*
[SuperR Kitchen] _that:
I've only quickly tested it with my Moto G and it produced a correct image. If your 5X image doesn't work, compare it with one obtained using the known good method.
[SuperR Kitchen] xNako:
In the kitchen?? The app folders of my project
[SuperR Kitchen] bcrichster:
Disregard my post

Sent from CM12.1 *N9515*
[SuperR Kitchen] Pyr0ball:
Of these options I think adding an option for /storage/sdcard0 would be good. Any chance of donig an ls of /storage to see if there are other possible mount points? I personally could just enter it manually, but it would be good to have the list of alternate mounts available as a list. As far as I'm aware, all USB OTG and SD card mounts are under /storage in 5.0.x+ roms.
[SuperR Kitchen] xNako:
Thanks Thanks Thank ;))))))
[SuperR Kitchen] SuperR.:
I am trying to sort out not needing the device storage at all when booted in Android. You already don't need it if you choose the booted to custom recovery option. OTG is /mnt/media_rw/RANDOM# on the Nexus 5X, not sure about other devices.

I just tested on my Moto G too, and it works correctly. The output of "file system.img" produces only "data" on the Nexus 5X img, and the normal Android system.img stuff on the Moto E and Moto G img's.

edit: [MENTION=4878287]_that[/MENTION] - I tested to see if the 5X img mounts when doing it the old way (dd to sdcard, adb pull to pc). It mounts perfectly. So the problem is with the command or the adb version. It mounts perfectly if I dd to sdcard and adb pull the img. It does not mount if I use the adb exec-out cat or dd. Strange behavior. If use adb version 1.0.32, the img is cut off before the end. If I use adb version 1.0.36, the adb output text is injected at the end of the img. I will keep digging and see if I can figure this out.
[SuperR Kitchen] Ssbroly:
Hello! I look for the way to the internal storage on my s7 edge. To put the apk files. it is / STORAGE / Emulated / O? Thank you!
[SuperR Kitchen] DarkHeart Z:
some zip mmc filters :)

Here is some new device filters . Though 1 of them are not complete . I will send you updated filters of that specific device .
[SuperR Kitchen] starbucks2010:
I installed the kitchen under cygwin64 but when I run ./superr I get the attached ss error. How can I fix it?

Thank you.
[SuperR Kitchen] morissio:
You have only install that dependency (7za,sudo,tune2fs). I don't know cygwin64 so I can't tell you the command line.

I suggest you to use a debian (ubuntu,mint ..)
[SuperR Kitchen] reefuge:
REF XT1068 Moto G 2nd Gen

adb shell su -C ls -al /dev/block/platform/msm_sdcc.1/info/by-name | grep system

returns nothing just back to cursor?................

this is what I get back if i drop info - sorry if i've got syntax wrong....!

adb shell su -C ls -al /dev/block/platform/msm_sdcc.1/by-name | grep system

lrwxrwxrwx root root 1970-01-29 03:14 system -> /dev/block/mmcblk0p36

but adb shell df gives this

1|shell@titan_umtsds:/ $ df
Filesystem Size Used Free Blksize
/dev 436.6M 64.0K 436.5M 4096
/sys/fs/cgroup 436.6M 0.0K 436.6M 4096
/sys/fs/cgroup/memory: Permission denied
/mnt/asec 436.6M 0.0K 436.6M 4096
/mnt/obb 436.6M 0.0K 436.6M 4096
/system 1.1G 1.0G 20.2M 4096
/data 5.5G 3.3G 2.3G 4096
/cache 525.7M 9.0M 516.7M 4096
/persist 4.9M 4.1M 792.0K 4096
/firmware 62.4M 46.5M 15.9M 4096
/pds 1.9M 1.0M 918.0K 1024
/fsg 638.0K 637.0K 1.0K 1024
/mnt/shell/emulated 5.5G 3.3G 2.3G 4096
/storage/emulated/legacy 5.5G 3.3G 2.3G 4096
/mnt/media_rw/sdcard1: Permission denied
/mnt/secure/asec: Permission denied
/storage/sdcard1 7.4G 4.7G 2.7G 32768
1|shell@titan_umtsds:/ $
[SuperR Kitchen] SuperR.:
You forgot the quotes around the shell command. It should be like this:

adb shell su -C "ls -al /dev/block/platform/msm_sdcc.1/by-name" | grep system

Thanks for trying this for me :)

edit: just noticed it actually did work properly even without the quotes. The info was part of the text you were supposed to replace with your actual by-name. Once you removed it we got the desired result. Sadly this leaves me confused why it is not doing this correctly in the kitchen for you since it is exactly the same. Are you sure detecting the partition size from your device does not work correctly?
[SuperR Kitchen] reefuge:
from option 1) through adb shell fails ---- all I get are 7.6mb zips of completed rom

option 2) get full 618mb rom that errors on install

option3) not tried!!
[SuperR Kitchen] hohassan444:
mine also unable to extract boot.img properly , no files in ramdisk folder. however, carliv image kitchen extract it properly.I have mt6752 64 bit lollipop rom.

thanks in advance.
[SuperR Kitchen] SuperR.:
Your device is not supported by mtk-tools which is how this kitchen unpacks MTK boot.img.

https://github.com/bgcngm/mtk-tools
[SuperR Kitchen] Er. Aditya:
as a user my feedback :

this is my first day on ubuntu so no expericne of linux or anything but this kitchen is amazing....superr kool and awesome

tomorrow il make a rom from this super kitchen and try flashing... have deodexed today

man awesome work , kudos to your skills ... ./superr

:D
[SuperR Kitchen] DarkHeart Z:
Search google for apt-cyg command and install it . It's the alternative of apt-get in linux and install tools recommended in the previous reply
[SuperR Kitchen] :
I switched from Windows to Linux mint 6 months ago, the best thing I ever did. Only time I ever use Windows now is for odin, don't know how to use heimdall lol
[SuperR Kitchen] fhem:
LOL --- Smart move I agree 100% --- Mint is great!!!!!!
[SuperR Kitchen] bcrichster:
Same here! SuperR talked me into Linux Mint (15) a cpl years ago since it started becoming New User friendly and I've not looked back. Was Dualbooting Mint 17.2 w/ Win7 until lately.. Lol. Point is, SuperR's recommendations always warrant merit and Linux became a blessing in software vs Wynn Doze! :cool: "Take Heed!" Lmao ;)

Gratefully sent from my Rooted Tesla N9510
[SuperR Kitchen] Er. Aditya:
lol after you said that word heimdall i have set it up but like you dont know how to use it :))

---------- Post added at 10:40 AM ---------- Previous post was at 10:11 AM ----------

dev's how to i extract csc ??

like windows do it with disk2integral

and also dev whats the default wipe status of rom

is it a full wipe or no wile ??
[SuperR Kitchen] SuperR.:
v0.9.2.1

Changes:

Re-wrote the Marshmallow deodex script to use baksmali/smali.

Changed boot tools to use Carliv Image Kitchen.

Fixed the kitchen updater so it will delete all unused files when updating without git.

Other things I can't remember.
[SuperR Kitchen] Danvdh:
good job on this mate