Hi, Super. I'm trying to extract a recovery.img from a firmware of the Blu G8/V9, and using the free Linux version of SuperR Kitchen has brought out everything but that image, lol. What I'm trying to figure out is if the capacity to do so is paywalled behind your donate version (option 7?)—I'm a broke university student and $20 down the drain without actually getting results would be a super bad investment for me. I've unlocked the bootloader on this device and want to build Lineage on it, but Magisk definitely needs recovery.img for me to progress any further.Features:
*Extract and create ROM from:
*Create flashable zips of many varieties including:
- Rooted Device
- Custom Recovery
- Existing ROM zip
- system.img/boot.img (and cache.img on Samsung devices)
- system.ext4.win/boot.emmc.win (including multi-file .win000, .win001, etc)
- Moto and other factory firmware zips containing sparsechunk files
- cm12 + roms with sparse dat files
- Zips that contain system.img and boot.img
- Zips that contain payload.bin
- Samsung firmware zips that contain tar.md5 file
- Official Nexus/Pixel firmware tgz/zip
- Official Nexus/Pixel preview tgz/zip
- system directory that contains symlinks and boot.img
*Deodex the following:
- Full ROM
- Switch between set_perm, set_metadata (KitKat+), raw_img, and sparse_dat (Lollipop+)
- Kernel (including init.d if you added it with the kitchen)
- app, priv-app, and framework
- Android 10 ROMs
- Pie ROMs
- Oreo ROMs
- Nougat ROMs
- Marshmallow ROMs
- Lollipop ROMs
- KitKat and earlier ROMs
- Choose Magisk
- Choose SuperSU
- Add other root zips to /tools/root/root_zips directory
- Choose system OR systemless root for M+ and Samsung 5.1.1 roms
- Add/remove su.d support
*By-name auto-detection from:
- Unpack/repack boot/recovery img (Big Thanks to @osm0sis for Android Image Kitchen!!!)
- Add/remove insecure boot
- Remove dm-verity
- Add/remove forceencrypt
*mmcblk auto-detection from:
- Existing ROM
- **OR**...manually enter it
- View the last 3 changelogs when an update is available.
- Update to the latest version
- Option to check for updates when the kitchen starts
*Device database for mmcblk devices (currently very small, but will grow over time)
*Add devices to the assert
*Add custom asserts
*Custom Debloat list support
*Add/remove busybox (Big thanks to @osm0sis for his Busybox Installer)
*Add/remove user app support (/data/app)
*Cross-platform: Windows and Linux are fully supported
*Does not say Built with SuperR's Kitchen in the updater-script
*Does not replace ro.build.display.id with Built.with.SuperRs.Kitchen
*Allows you to create a custom entry in the updater-script below the ROM name
*Removes all the Place holders (#ASSERT, #SYM, #PERM, etc) from the updater-script before zipping.
*Option to convert updater-script to update-binary for all rom zips EXCEPT sparse_dat.
*Add custom directory to be included in and flashed with rom zip to location of your choice.
*Ability to choose an apk, decompile, modify it manually, recompile, sign, and move it back to where it came from.
*Plugin support - Add your own script to the /kitchen/tools/plugins directory and the kitchen will run it for you.
*AutoROM - Unattended ROM development using a config file.
If it is a new device, It is probably an F2FS file system like the S22.