I don't take responsibility for any damage may happen to your device because of using this tool, USE AT YOUR OWN RISKA new generation of Android ROMs development...The ClassyKitchen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
About:
A new C++ Windows application that based on ASSAYYED KITCHEN to deal with the most of android ROMs (stock images, stock updates, running device ..... etc)
In addition to built-in apktool to easily decompile & recompile apk in the PROJECT
And with a friendly user interface with full mouse control just one click.
With static build feature and a new built-in windows tools feature (hex dump) that makes the whole working environment into one exe file only.
ROM editor features:
1 - Supported ROMs type for extract:
Any stock system[lz4] & boot[lz4] [cache | odm] images
All Samsung stock firmwares (TAR[.MD5]) with support for LZ4 compress
All Google stock firmwares (ZIP)
All Lineage stock ROMs (system.new.dat[br] & vendor - payload.bin)
Any other images dumped from other stock ROMs (Huawei - HTC.....etc)
Rooted device OR custom recovery (*With technology to dump boot & system & vendor images without need a space on device*)
2 - Supported ROM edits:
Pre-remove for Samsung RMM security
DeOdex for android [4.x.x] till [9.x.x]
ZipAlign for all APKs & JARs
Heavy DeBloat ROM with Re-Bloat
Full DeKnox ROM
Clean ROM from all CSC apks (in Samsung ROMs)
Support safe and powerful Build.prop tweaks
Support change Build Number text
Support add busybox into the ROM itself with all available symlinks in image
3 - Supported ROM build:
ZIP ROM contains sparse system [vendor & odm] dat
ZIP ROM for custom recovery flashing
ZIP images ROM for fastboot flashing
TAR images ROM for Samsung devices
Support compress Samsung images with original LZ4 format
4 - Supported boot image edits:
Support all boot images partitions names other than boot.img
Remove dm-verity with AVB & ForceEncryption
Enable ADB
Patch sepolicy (supports CIL) to supported deodexed Oreo
Add / Remove Magisk Root to boot image directly in windows
Support patch boot image to run scripts during boot that placed in /system/smart_scripts
5 - Supported Apktool:
Decompile single apk
Recompile single apk
Sign single apk
Support option to specify [New | Original] apk signature
Support use custom apktool.jar selected by user
Support Decompile - Recompile multi APKs in the same time
Support Decompile - Recompile JAR files (Support multi classes files)
6 - Supported On Device Features:
Support dump full device memory using (adb root) - supported (EMMC & UFS) Without need any space on device
Support dump specified partitions from device using (adb root) - (List to user and pick needed partitions)
General Features:
Quite simple user interface
Very safe when working with images ROM for files [modes, gid, uid, contexts, capabilities]
Read the exact EXT4 [symbolic links, full permissions] and re-apply them when building
Write full permissions for [fs_config, contexts, capabilities] when building an EXT4 image or in [updater-script]
Support fix the case sensitive problems with ROMs like (Samsung S8 / S8+)
Support save project and restore it when needing
Support [Added edits log] to allow the user to see all edits he made
Support add custom text during flash in recovery
Support save the system image and [odm] image sizes to rebuild them using the exact original size
Support allow user to change the build configs (size, sparse header, images ext)
Support custom debloat list
Support more that one connected ADB device and list them to user to pick one to pull ROM from
Pro Version:
The kitchen has two versions Free & Pro
And the Pro version requiring a small donation (20$) and it needs an authenticating code to run it on a specified PC,
If anyone need to use it just download and run then send to me the output code with a transaction ID to send the activation code that match the given code.
NOTE: The Pro version is to supporting my work only, and the Free version is enough to create a full modded flashable ROM
- The following features are only available in Pro version:
All On Device Features
Pull ROM from Rooted device or custom recovery
Change Build Number text
Build TAR images ROM for Samsung devices
Build ZIP images ROM for fastboot flashing
Add Magisk Root to boot image directly in Windows
Patch boot image to run script during boot
Decompile - Recompile multi APKs in the same time
Manual DeBloat as user wants
Download link:
- Latest Free Version: http://www.mediafire.com/file/7uch95enkpc7q2p/ClassyKitchen_Free_Beta_1.0.4.7z/file
- Latest Pro Version: http://www.mediafire.com/file/l62q85rj8d8lqu0/ClassyKitchen_Pro_Beta_1.0.4.7z/file
Changelog:
- Version: 1.0.4 - BETA:
Added support to build sparse dat images
Improved some props read in OnePlus devices
Added new tab On Device Features: Support dump Full device memory without need space on device & dump selected partitions without need space too (Pro Version)
Updated flash_kernel.sh script
Updated Magisk to version 18.0
- Version: 1.0.3 - BETA: Free Version - Pro Version
Added support to Decompile - Recompile multi apks in the same time (Pro Version)
Added support to manual DeBloat (list all ROM apks to user to pick one and remove) (Pro Version)
Updated DeKnox list
Improved dump ROM from device (skip search for ODM - VENDOR partitions if the device doesn't have them)
Added support to decompile & recompile JAR files
Added support to deal with boot images that have names other than boot.img
Added support to build ODM image in fastboot build option
ReCoded all Deodex codes to support ROMs that have symlinked 64 oat files like Huawei devices
Updated Magisk Root files and Magisk sources to v18
- Version: 1.0.2 - BETA: Free Version - Pro Version
Added support to ReCompress Samsung images to LZ4 during TAR building
Updated packing original APK signature during APK compiling
Updated Magisk to 17.3 (2018-11-22)
Added SmartScripts feature to easy run scripts as Root during system boot (Pro Version)
- Version: 1.0.1 - BETA: Free Version - Pro Version
Fixed bug happened when switch from system_root to system type ROM
Added support to vendor (build zip - build images - extract)
Updated building images codes (better size printing)
Added support to (vendor.new.dat[br])
Added support to pull vendor image from Rooted devices
- Version: 1.0.0 - BETA: Free Version - Pro Version
Initial release
Reports & Request features:
To report any issue Please provide a pic for the Error happened in the Kitchen and A link for the ROM used (Without them I can not provide any help) (Posting here not via PM please).
To request any features to add or any notes about exists features just post about them on this thread (Or via PM).
Credits:
- Cygwin Project: For base tools to deal with Linux symbolic links in Windows
- 7zip: For 7z binary to deal with EXT4 filesystem
- AOPS Platform Tools: For ADB tools
- And_pda: For ImgExtractor tool
- LZ4 Project: For sources to deal with lz4 compressed images
- AOSP Sources: For all android sources (sparse converting, simg2img, aapt, zipalign, brotli, cdex_convert_sources, readelf......etc)
- Cubinator: For his EXT4 images analyzing python sources
- testwhat: For oat2dex tool
- anestisb: For vdexExtractor tool
- Linus Yang: For compact_dex_converter tool
@topjohnwu: For Magiskboot tool sources
@JesusFreke: For his Smali & Baksmali
@xpirt: For sdat2img python tool
@iuss: For payload_dumper python tool
@iBotPeaches: For apktool tool
WoW , that was mind blowing . I Just got my Pro version, and i build my first tar rom and it was flashed successfully . Thank you sir.
Hello , Is this suitable to port roms , by repacking rom files , as i have a unpacked system folder need to repack to system.new.dat.br or system.new.dat
thank you
arvs47 said:
Hello , Is this suitable to port roms , by repacking rom files , as i have a unpacked system folder need to repack to system.new.dat.br or system.new.dat
thank you
Click to expand...
Click to collapse
Currently working with system folder is not supported due to hard get of correct permissions and image configs.
I will add support for that soon with creating system.dat*
AndroDef said:
Currently working with system folder is not supported due to hard get of correct permissions and image configs.
I will add support for that soon with creating system.dat*
Click to expand...
Click to collapse
ok i am trying to port asus zenfone 5 2018 zenui rom into Asus zenfone max pro m1
so does this app support manufacture rom port once you add system.dat support
arvs47 said:
ok i am trying to port asus zenfone 5 2018 zenui rom into Asus zenfone max pro m1
so does this app support manufacture rom port once you add system.dat support
Click to expand...
Click to collapse
No, Porting feature is not supported now
How do i create custom debloat lists?
Really great application! Made my first rom using it!
Sent from my dream2lte using XDA Labs
dr460nf1r3 said:
How do i create custom debloat lists?
Really great application! Made my first rom using it!
Sent from my dream2lte using XDA Labs
Click to expand...
Click to collapse
Create a (txt) file and write in it all items you want to remove (Names with extensions only without paths)
Then press on Debloat and select custom debloat list and select your txt file (File browser)
At samsung ruins, it would not be possible to include vendor.img.lz4 among the unpacked and repackaged
You also have to change things to get the better rom done
Thanks in advance
I have a N960F, downloaded the latest official firmware from sammobile. Size 4.85GB.
How come the final zip file to flash in recovery is only 2.71GB?
This is what I did to the rom:
removed verity/encryption
enabled adb
disabled rmm
zipaligned
deknox
added busybox
That's all. I didnt add neither remove anything else.
I installed the resulting rom and it installed fine but without detecting the SIM card, not detecting past wifi and bluetooth connections.
I used it previously for my tablet T835 and everything worked perfectly.
Any clues?
Sapiens said:
I have a N960F, downloaded the latest official firmware from sammobile. Size 4.85GB.
How come the final zip file to flash in recovery is only 2.71GB?
This is what I did to the rom:
removed verity/encryption
enabled adb
disabled rmm
zipaligned
deknox
added busybox
That's all. I didnt add neither remove anything else.
I installed the resulting rom and it installed fine but without detecting the SIM card, not detecting past wifi and bluetooth connections.
I used it previously for my tablet T835 and everything worked perfectly.
Any clues?
Click to expand...
Click to collapse
When downloading offical firmware there are lots of other images which are flashed via odin such as vendor etc. By using the kitchen only the system image is used.
Sent from my dreamlte using XDA Labs
dr460nf1r3 said:
When downloading offical firmware there are lots of other images which are flashed via odin such as vendor etc. By using the kitchen only the system image is used.
Sent from my dreamlte using XDA Labs
Click to expand...
Click to collapse
Thanks for the prompt answer. I didnt have a clue about that. Good to know.
Any idea why my SIM and radios got screwed up. No cellphone signal, didnt even ask for the SIM pin as if it didnt see it. The wifi didnt connect the usual network. Bluetooth kept asking me many times to confirm the connection code of my WearOs watch.
Sapiens said:
I have a N960F, downloaded the latest official firmware from sammobile. Size 4.85GB.
How come the final zip file to flash in recovery is only 2.71GB?
This is what I did to the rom:
removed verity/encryption
enabled adb
disabled rmm
zipaligned
deknox
added busybox
That's all. I didnt add neither remove anything else.
I installed the resulting rom and it installed fine but without detecting the SIM card, not detecting past wifi and bluetooth connections.
I used it previously for my tablet T835 and everything worked perfectly.
Any clues?
Click to expand...
Click to collapse
Before flashing any modded ROM with the kitchen flash the Full stock copy of the ROM first.
If this doesn't work try to flash a ROM by the kitchen but without any edits to know if the problem from edits or kitchen itself.
AndroDef said:
Before flashing any modded ROM with the kitchen flash the Full stock copy of the ROM first.
If this doesn't work try to flash a ROM by the kitchen but without any edits to know if the problem from edits or kitchen itself.
Click to expand...
Click to collapse
Do you mean flashing the full stock on Odin? That would make me lose TWRP. And the idea for me of using your very nice ROM creating tool was to remain official, rooted, without having to install custom recovery again.
It worked perfectly on my tablet.
Sapiens said:
I have a N960F, downloaded the latest official firmware from sammobile. Size 4.85GB.
How come the final zip file to flash in recovery is only 2.71GB?
This is what I did to the rom:
removed verity/encryption
enabled adb
disabled rmm
zipaligned
deknox
added busybox
That's all. I didnt add neither remove anything else.
I installed the resulting rom and it installed fine but without detecting the SIM card, not detecting past wifi and bluetooth connections.
I used it previously for my tablet T835 and everything worked perfectly.
Any clues?
Click to expand...
Click to collapse
Hello
Because it does not wrap the complete rom into tar, but only sytem.img, odm.img, and boot.img
he does not do anything else
rstwingo said:
Hello
Because it does not wrap the complete rom into tar, but only sytem.img, odm.img, and boot.img
he does not do anything else
Click to expand...
Click to collapse
Thank you for the explanation
Sent from my SM-N960F using Tapatalk
rstwingo said:
Hello
Because it does not wrap the complete rom into tar, but only sytem.img, odm.img, and boot.img
he does not do anything else
Click to expand...
Click to collapse
Sapiens said:
Thank you for the explanation
Sent from my SM-N960F using Tapatalk
Click to expand...
Click to collapse
I finished add support for vendor partition and will release the update soon.
AndroDef said:
I finished add support for vendor partition and will release the update soon.
Click to expand...
Click to collapse
Looking forward to testing that update!
Sent from my SM-N960F using Tapatalk
---------- Post added at 10:58 AM ---------- Previous post was at 10:18 AM ----------
AndroDef said:
I finished add support for vendor partition and will release the update soon.
Click to expand...
Click to collapse
Also, is it possible to have for the debloating option, a list based on the default list that you provide where one can tick and untick apps to select what to remove and what to keep?
I know this requires more programming. If not possible then to provide the default list that you use to debloat, so we can customize it please.
Thanks
Sent from my SM-N960F using Tapatalk
vendor.new.dat missed
Sapiens said:
Looking forward to testing that update!
Sent from my SM-N960F using Tapatalk
---------- Post added at 10:58 AM ---------- Previous post was at 10:18 AM ----------
Also, is it possible to have for the debloating option, a list based on the default list that you provide where one can tick and untick apps to select what to remove and what to keep?
I know this requires more programming. If not possible then to provide the default list that you use to debloat, so we can customize it please.
Thanks
Sent from my SM-N960F using Tapatalk
Click to expand...
Click to collapse
After debloat process you can navigate to (PROJECT_FILES/DEBLOAT) and delete what you want then restore the needed items by the kitchen, However I will add manual debloat feature and currently I attached the debloat list of the kitchen.
daxiaamu said:
vendor.new.dat missed
Click to expand...
Click to collapse
Send to me a link for a firmware contents that file.
Related
Disclaimer: I am not responsible for anything bad that may occur from the use of this kitchen, but I will take all the credit you can give me if it works for you
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please read the usage instructions in post #3 and the troubleshooting in post #4 below before asking for help. Thanks
Free Changelog
Download/Install
Donate version for Windows/Mac/Linux/WSL:
Dedicated thread found here
Free Kitchen (Linux terminal):
**NOTE: The free kitchen will not work in WSL**
Download the kitchen.zip from here. Extract to a new directory.
Enter the following commands one by one pressing ENTER after each line where "/location/of/kitchen" is the directory where the kitchen lives:
Code:
cd /location/of/kitchen
./superr
Dependencies:
Java 8 or higher (8 is recommended)
Python (to run the launcher (could be bypassed by running tools/source/superr in the terminal from the main kitchen directory))
Video tutorials by @chevycam94
Credits:
@osm0sis - For Busybox Installer and Android Image Kitchen
@Chainfire - For SuperSU
@JesusFreke - For [Bak]smali
@nkk71 - For creating the TWRP minzip patch
@Captain_Throwback - For providing a pre-compiled update-binary with the minzip patch and squashing bugs
@_riddle - For oat2dex
@iBotPeaches - For Apktool
@AOSP - For zipalign, adb, aapt, img2simg, simg2img, make_ext4fs
@xpirt - for img2sdat
@bcrichster - For extensive testing
XDA:DevDB Information
SuperR's Kitchen, Tool/Utility for the XDA Community Apps
Contributors
SuperR.
Version Information
Status: Stable
Created 2017-04-27
Last Updated 2020-07-24
Usage:
Run "superr" from it's location in terminal
Create new project using the menu
Copy ROM zip into the superr_NAME directory of this tool (NAME = the name of your new project).
OR
Copy system.ext4.tar and boot.img into the superr_NAME directory of this tool.
OR
Copy system.ext4.win and boot.emmc.win into the superr_NAME directory of this tool.
OR
Copy system.img and boot.img into the superr_NAME directory of this tool.
OR
Copy official Nexus tgz into the superr_NAME directory of this tool.
OR
Copy Samsung firmware zip into the superr_NAME directory of this tool.
OR
Copy Moto firmware zip into the superr_NAME directory of this tool.
OR
Leave superr_NAME directory empty to extract from rooted device or custom recovery
Extract for new ROM from the Main menu.
Enjoy!
Example:
In your terminal, type the following where "/home/user/kitchen/" is the directory where the kitchen lives:
Code:
cd /home/user/kitchen/
./superr
NOTE: the above code is 2 separate commands and requires ENTER to be pressed after each command
OR
Double-click the superr file and choose "Run in Terminal" if your OS supports it.
Add your own device support:
Create a new project in the kitchen.
Add your files to the project directory (system.img/boot.img, system.ext4.tar, win, zip, etc.)
Extract for new rom from the menu
When asked how to get your partitions, choose detect by-name from boot.img. If it gives you an error, put a recovery.img in your project directory and choose detect mmc from recovery.img.
Enjoy
Features:
*Extract and create ROM from:
Rooted Device
Custom Recovery
Existing ROM zip
system.img/boot.img (and cache.img on Samsung devices)
system.ext4.tar/boot.img
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
Samsung firmware zips that contain tar.md5 file
Official Pixel/Nexus firmware tgz
Official Pixel/Nexus preview tgz
SpreadTrum firmware that includes a pac file
system directory that contains symlinks and boot.img
*Create flashable zips of many varieties including:
Full ROM
Switch between set_perm, set_metadata (KitKat+), raw_img, and sparse_dat (Lollipop+)
Kernel
Recovery
Media
app, priv-app, and framework
*Deodex the following:
Pie ROMs
Oreo ROMs
Nougat ROMs
Marshmallow ROMs
Lollipop ROMs
KitKat and earlier ROMs
*Root features:
Root/unroot
Choose SuperSU or Magisk zip (add other versions to /tools/root/root_zips directory)
Choose system OR systemless root for M+ and Samsung 5.1.1 roms (SuperSU only)
*Boot features:
Unpack/repack boot/recovery img (Big Thanks to @osm0sis for mkbootimg source!!!)
Add/remove su.d support
Add/remove insecure boot
Remove dm-verity
Remove forceencrypt
*By-name auto-detection from:
Device
Existing ROM
boot.img
kernel.elf
**OR**...manually enter it
*mmcblk auto-detection from:
recovery.img
*Kitchen updater:
View the last 3 changelogs when an update is available.
Incremental update for updating the most recent previous version
Option to check for updates when the kitchen starts
*Create system.img
*Device database for mmcblk devices (currently very small, but will grow over time)
*Add devices to the assert
*Add custom asserts
*Zipalign apks
*Debloat ROM
*Custom Debloat list support
*Remove Knox
*Add/remove busybox (Big thanks to @osm0sis for his Busybox Installer)
*Add/remove user app support (/data/app)
*Sign zips
*Translatable with language files
*Donate version additional features:
Cross-platform - Windows, WSL, Macos, Linux
tarfs - Get original permissions, contexts, and capabilities from tar/win backups.
Create system.img with identical permissions, contexts, and capabilities as the original system.img or tar/win backup.
Plugins - Probably the best part! Currently over 20 extra features and growing
Root - Use a custom root zip (not the included Magisk or SuperSU)
Custom directory - can be included in your ROM and flashed to a specified partition
Custom Signature - No Built with SuperR's Kitchen, anywhere, plus add your own
Custom Build Display in About Phone, or leave it as default
AutoROM - Automation for ROM creatiion using a congig file (there's a plugin for that)
Convert updater-script to an update-binary script
No mounting img files. One less thing requiring your password and interrupting extraction.
Upload support.zips and device.zip directly from the kitchen for review
Download language files directly from the kitchen
Restore original boot.img after modifying and repacking
Remove asserts from the updater-script
Configurable compression level for packing zips
Remove all placeholder tags (#ASSERT, #SYM, #PERM, etc.) before packing the ROM
Create ext4 img file from any partition you include in your ROM.
zipalign without building ROM
Fix ext4.img files automatically if block count is higher than actual blocks
Troubleshooting/FAQ:
When asking for help, please provide as much of the following info as possible so I can help as easily as possible. I am a busy person and would prefer not to ask all of these questions every time someone has a problem. Thank you for understanding.
What Kitchen version?
What environment are you running the kitchen in (OS, 32/64-bit, cygwin, Bash on Windows, etc.)?
What device are you working on (make/model)?
What was the source you started from (system.img, system.ext4.tar, rom.zip, etc.)
What Android version?
What perm method (set_perm, set_metadata, sparse_dat, raw_img)?
What did you do after extracting and before building?
Were there errors on the screen if you scroll up in the terminal?
Send a recovery.log after flashing if you have problems flashing the ROM.
Send a link that does not require registration to the files you started with (nandroid, system.img, boot.img, etc)
Use the support option in the Misc Tools menu and attach the support.zip to your post.
Ubuntu4Kitchen
An Ubuntu 16.04 distro with all the things you need to get the kitchen working easily.
Visit the dedicated thread here
Language Files (translations)
English - Default/Included in the kitchen
Download additional language files here
Once the language zip has been downloaded, extract to /kitchen/tools/language and restart the kitchen.
Does this kitchen support Windows CYGWIN?
CYGWIN is not supported and will not work. Try the donate kitchen for Windows, Linux, and Mac.
WSL (Bash on Ubuntu on Windows)
WSL is not supported in the free kitchen and will not work. Try the donate kitchen for Windows, Linux, and Mac.
Which perm type should I choose?
Here is a very brief summary of set_perm, set_metadata, sparse_dat, and raw_img.
set_perm : The oldest of the 4. Sets file/directory permissions when flashing a rom. Not recommended for KitKat and above.
set_metadata: Also sets file/directory permissions when flashing a rom, but also adds file contexts. It was introduced with selinux in KitKat. Recommended for KitKat and above.
sparse_dat: The newest of the 4, and only works on Lollipop +. The permissions, symlinks, and file contexts are all added inside a sparse image. A sparse image is an image with a more efficient space usage. Only for Lollipop and above. The free kitchen uses AOSP permissions/capabilities when building system.img. If your device requires different permissions, this method will not work for you in the free kitchen.
raw_img: This is literally raw images that are flashed to your device. The permissions, symlinks, and file contexts are all added inside the raw image. Works for all Android versions. The free kitchen uses AOSP permissions/capabilities when building system.img. If your device requires different permissions, this method will not work for you in the free kitchen.
Flashing error:
This package is for "xxxxx" devices; this is a "yyyyy"
The problem is the asserts and it is easy to fix. In the kitchen menu, go to ROM Tools > Asserts > Add/Remove device asserts. At the bottom it will say "xxxxx". Edit the line to say "xxxxx,yyyyy" and press enter. Build your rom again and flash.
Why is my ROM zip so small?
blkdiscard failed: Invalid argument
These are generally due to the partition size detection method. You need the correct partition size for ALL partitions you are creating sparse dat and raw_img images for. The kitchen will ask for each one that is included in your rom when you choose to build the full rom zip. If none of the provided auto-detect methods work, you will need to find the partition size on your own and enter it manually in the kitchen.
Root problems?
You can replace the SuperSU.zip and Magisk.zip in the kitchen with any flashable SuperSU/Magisk version you want. It is located in kitchen/tools/root/root_zips. Delete the one that is there (if it exists) and add yours. Then, unroot, re-root and your replacement will be used.
Auto check for updates when kitchen starts
To enable the auto update check, go to "Check for updates" in the main menu. After it checks, you will be asked if you want to enable it.
I added root and busybox but there is no su or busybox in my project. Why?
The kitchen does not add Busybox or SuperSU/Magisk files to the project. Instead it adds flashable zips inside the rom.zip. There are many variables to deal with (Android version, device architecture, manufacturer, system/systemless, etc.). Flashing the zips with the rom accounts for all of these variables and there is no reason to re-invent the wheel.
Debloat and custom debloat
There are 2 options in the debloat menu (besides knox which is self explanatory):
1) Debloat ROM
This option removes all files included in the kitchens standard bloat list file - /kitchen/tools/root/bloat
2) Custom Debloat
This option removes all files included in the bloat_custom file - /kitchen/tools/root/bloat_custom OR kitchen/superr_project/00_project_files/bloat_custom
This file is empty by default and is there for you to add whatever you want to remove. You can either add everything you want to remove and use only option 2, or you can add new files here and use option 1 and 2.
I suggest you take a look at /kitchen/tools/root/bloat to see the format of the listed bloat files. Use the same format for the bloat_custom file.
When you use either option, the files are not deleted. Instead they are moved to the 00_project_files directory in case you want to restore them later.
Deodexing
Deodexing Samsung roms may or may not work. If your rom does not boot after deodexing, try it without. If it works and you must deodex your rom, try a different tool. I hear svadev deodex tool works well for Samsung roms.
boot.img errors
If the kitchen gives you errors about unpacking boot.img, there is a good chance I will not be able to help. I suggest you figure out how to unpack it using Linux commands/binaries and let me know how you did it. You may also find a tutorial about how to unpack your boot.img. If so, please send a link. It does not help me to know another tool works. I need the commands/binaries used in order to update the kitchen.
Feel free to upload your boot.img AND the build.prop from the same rom so I can check to see if I can fix it. I will ignore you if you don't upload both mentioned files
I do not answer support questions through PM. There are no exceptions. Post in the thread if you want help so others can give suggestions and learn from your solution
I will not answer questions if it is clear that you have not read the OP, the info posts after the OP, and searched the thread for answers. I do not have time to answer the same questions over and over. Many questions are already answered in this thread and if you want help, I expect you to try and solve it on your own before posting. If your question has not been answered in the thread, I am happy to assist in any way possible.
If I ask you to upload files, they need to be uploaded on a server that does not require registration for full speed downloads, or registration for downloads at all. Drive, Dropbox, AFH, and Mega are examples of acceptable servers. There are many other good ones, but I hope you get the point.
Thanks for understanding
reserved
Looks promissing, gonna try it asap :good:
I suppose it to work for many devices but are there any already tested for?
Looks great mate. Can't wait to give it a go
Its been an honor, testing this out! This deserves to be stickied!!
Sent from my N9510 using Tapatalk
---------- Post added at 04:51 AM ---------- Previous post was at 04:48 AM ----------
Androidwizzard said:
Looks promissing, gonna try it asap :good:
I suppose it to work for many devices but are there any already tested for?
Click to expand...
Click to collapse
Zte Concord 2
Zte Warp4G
Moto E 2015
LG Exceed 2
LG Realm
Still waiting on results from:
MediaTEK VKworld (VS6050S)
SuperR. said:
Disclaimer: I am not responsible for anything bad that may occur from the use of this tool, but I will take all the credit you can give me if it works for you
Sent from my N9510 using Tapatalk
Click to expand...
Click to collapse
Nice and finally something for Linux. To bad I'm out of town can't wait to test this...
Nice work
Sent from my SM-G928T using Tapatalk
bcrichster said:
Its been an honor, testing this out! This deserves to be stickied!!
Sent from my N9510 using Tapatalk
---------- Post added at 04:51 AM ---------- Previous post was at 04:48 AM ----------
Zte Concord 2
Zte Warp4G
Moto E 2015
LG Exceed 2
LG Realm
Still waiting on results from:
MediaTEK VKworld (VS6050S)
SuperR. said:
Disclaimer: I am not responsible for anything bad that may occur from the use of this tool, but I will take all the credit you can give me if it works for you
Sent from my N9510 using Tapatalk
Click to expand...
Click to collapse
Think it needs to be in xda portal as well
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
I'll give it a shot on Samsung Galaxy Note 5 - if there aren't any objections against @SuperR.
Is portal different than Chef Central?
Sent from my N9510 using Tapatalk
bcrichster said:
Is portal different than Chef Central?
Sent from my N9510 using Tapatalk
Click to expand...
Click to collapse
Xda portal is video review and goes on xda Facebook as well
Sent from my SM-N920C using Tapatalk
Androidwizzard said:
I'll give it a shot on Samsung Galaxy Note 5 - if there aren't any objections against @SuperR.
Click to expand...
Click to collapse
Right on, should have Knox removal as well. By all means, plz report back
Sent from my N9510 using Tapatalk
Good! I can test with a mtk6582 device with lollipop stock rom... sounds great!! SUPPORT!
Regarding MTK devices, I have never owned one so I am totally unfamiliar with special requirements they may need. I will add support for everything I can as issues come up
SuperR. said:
Regarding MTK devices, I have never owned one so I am totally unfamiliar with special requirements they may need. I will add support for everything I can as issues come up
Click to expand...
Click to collapse
I think you need to add mkbootimg ( https://github.com/osm0sis/mkbootimg ) for work with mtk based boot.img and maybe edit the img extraction of stock imgs.... I dont't now bro, you're the chef hahaha
Regards and support
duniel said:
I think you need to add mkbootimg ( https://github.com/osm0sis/mkbootimg ) for work with mtk based boot.img and maybe edit the img extraction of stock imgs.... I dont't now bro, you're the chef hahaha
Regards and support
Click to expand...
Click to collapse
This kitchen already uses Android Image Kitchen by osm0sis, which includes his mkbootimg. Maybe it will already work for MTK. Let me know if you encounter problems.
SuperR. said:
This kitchen already uses Android Image Kitchen by osm0sis, which includes his mkbootimg. Maybe it will already work for MTK. Let me know if you encounter problems.
Click to expand...
Click to collapse
Yes, It should work.
When I try with my device I'll tell you the results
Regards
Disclaimer: I am not responsible for anything bad that may occur from the use of this kitchen, but I will take all the credit you can give me if it works for you
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please read the troubleshooting in post #4 of the standard kitchen thread before asking for help.
Please indicate your OS when asking for help.
Please send a fast link to your firmware that does not require registration when asking for help.
Donate Release Thread
Donate Changelog
Donate version Info
See terms and conditions below.
Spoiler: Terms and Conditions
Terms and Conditions for SuperR's Kitchen Donate version:
Allowed:
An active kitchen account grants usage privileges of the donate kitchen and the sr-code.com website.
One kitchen account provides kitchen access to one user, on one operating system, on one personal computer.
Not allowed:
Sharing your kitchen account and/or privileges.
Transfer and/or resale of your kitchen account.
Suspicious activity.
Definition:
Suspicious activity - Decided exclusively by SuperR at the time of an incident.
Resolution:
If anything from the not allowed list occurs, your kitchen account will be disabled.
See this post for more details on the Single PC license.
Donation Options:
No longer accepting donations or new users.
EXISTING DONORS: GitLab is no longer used. See this post if you previously had GitLab access and are unable to download/update/install.
NOTE: The Plugin Repo is included in the Donate kitchen. If you wish to see a description of the available plugins, they can be found here.
Dependencies:
WINDOWS:
Java 8 or higher (Windows download)
LINUX/MAC:
Java 8 or higher
Python (to run the launcher (could be bypassed by running tools/source/superr in the terminal from the main kitchen directory))
Download/Install/Run:
Free version:
Found here
WSL2 (Windows 10):
WSL2 Help and information (Donate Version)
With the release of v3.2.1.0, there are many improvements to the Linux version of the kitchen compared to the native Windows version. WSL2 on Windows 10 is the perfect way to run the Linux kitchen on Windows. Installation takes a few more steps...
forum.xda-developers.com
Linux/Mac (Terminal):
Download the kitchen.zip from the download page sent through PM. Extract to a new directory.
Enter the following command where "/location/of/kitchen" is the directory where the kitchen lives:
Code:
/location/of/kitchen/superr
Windows:
NOTE: The native Windows version has reached end of life. Consider running the Linux kitchen in WSL2 using the guide above.
Download the kitchen.zip from the download page sent through PM. Extract to a new directory.
Make sure Java listed above is installed and in your system environment PATH (Check Google for the many guides on this if you need help)
Double click superr.exe in newly extracted kitchen directory.
NOTE: After you start the kitchen, it will ask you for your Kitchen username and password. Make sure you enter it correctly or it will not work. Thanks for the donation, enjoy
Known Issues/Limitations:
Does not unpack/repack f2fs file systems.
Linux:
None
WSL2:
None
WSL1:
Crashes with xattr not defined error when unpacking some img files due to a bug in the Python ext4 module.
Mac:
Does not use e2fsdroid for building img files as I am not able to compile it for Mac so far.
Windows:
No longer being updated. v3.2.1.3 is the last version. The Linux kitchen runs perfectly in WSL.
Does not use e2fsdroid for building img files as I am not able to compile it for Windows.
Crashes with xattr not defined error when unpacking some img files due to a bug in the Python ext4 module.
If you run Windows as administrator and have issues with the Boot Menu, please see this post.
If superr.exe gets removed by your antivirus program, whitelist the kitchen directory in your antivirus program.
If the kitchen can't find an internet connection, try whitelisting sr-code.com in your antivirus browsing security. If it still does not find a connection, try using a VPN.
The colors are not perfect due to Windows not supporting ASCII escape codes by default. If you want it to look more like Linux, you can run the Linux version in WSL (formerly known as "Bash on Ubuntu on Windows").
Video tutorials by @chevycam94
Credits:
@osm0sis - For Busybox Installer and Android Image Kitchen
@Chainfire - For SuperSU
@JesusFreke - For [Bak]smali
@nkk71 - For TWRP minzip patch, and make_ext4fs improvements
@Captain_Throwback - For providing a pre-compiled update-binary with the minzip patch and squashing bugs
@cubinator - For Python ext4 module
@_riddle - For oat2dex
@iBotPeaches - For Apktool
@AOSP - For zipalign, aapt, adb, img2simg, simg2img, make_ext4fs
@xpirt - for img2sdat & sdat2img
@yoanf_26 - For French translation
@anestisb - For vdexExtractor
@iuss - For payload_dumper.py
Contributors
SuperR.
Version Information
Status: Beta
Created 2018-11-16
USAGE:
Run the kitchen (instructions in OP)
Create new project using the menu
Copy ROM zip into the superr_NAME directory of this tool (NAME = the name of your new project).
OR
Copy system.ext4.tar and boot.img into the superr_NAME directory of this tool.
OR
Copy system.ext4.win and boot.emmc.win into the superr_NAME directory of this tool.
OR
Copy system.img and boot.img into the superr_NAME directory of this tool.
OR
Copy official Nexus tgz into the superr_NAME directory of this tool.
OR
Copy Samsung firmware zip into the superr_NAME directory of this tool.
OR
Copy Moto firmware zip into the superr_NAME directory of this tool.
OR
Leave superr_NAME directory empty to extract from rooted device or custom recovery
Extract for new ROM from the Main menu.
Enjoy!
Features:
*Extract and create ROM from:
Rooted Device
Custom Recovery
Existing ROM zip
system.img/boot.img (and cache.img on Samsung devices)
system.ext4.tar/boot.img
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
*Create flashable zips of many varieties including:
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)
Recovery
Media
app, priv-app, and framework
*Deodex the following:
Android 10 ROMs
Pie ROMs
Oreo ROMs
Nougat ROMs
Marshmallow ROMs
Lollipop ROMs
KitKat and earlier ROMs
*Root features:
Root/unroot
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
*Boot features:
Unpack/repack boot/recovery img (Big Thanks to @osm0sis for Android Image Kitchen!!!)
Add/remove insecure boot
Remove dm-verity
Add/remove forceencrypt
*By-name auto-detection from:
Device
Existing ROM
boot.img
kernel.elf
**OR**...manually enter it
*mmcblk auto-detection from:
recovery.img
*Kitchen updater:
View the last 3 changelogs when an update is available.
Update to the latest version
Option to check for updates when the kitchen starts
*Pack/Unpack super.img
*Create system.img
*Device database for mmcblk devices (currently very small, but will grow over time)
*Add devices to the assert
*Add custom asserts
*Zipalign apks
*Debloat ROM
*Custom Debloat list support
*Remove Knox
*Add/remove busybox (Big thanks to @osm0sis for his Busybox Installer)
*Add/remove user app support (/data/app)
*Sign zips
*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.
*Custom ro.build.display.id
*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.
Nice to see the windows version! Thx SuperR!
Sent from my unknown using XDA Labs
Got the notification from Gitlab
Bangin'! [emoji41]
shoey63 said:
Got the notification from Gitlab
View attachment 4139244
Click to expand...
Click to collapse
Me too. [emoji16]
Sent from my N9515 using Tapatalk
@SuperR.
I've been enjoying your free version greatly. It suites my needs just enough. But I still wanted to contribute to get the Pro version, just to Help Donate to you. The many lines of script you wrote are AMAZING!!! THANK YOU for your amazing work!!! :good:
Heres my GitLab username: aaron74xda
My 14.04 is also 64bit version maybe is better i update to the version that you offer in the other kitchen thread ?
https://forum.xda-developers.com/showpost.php?p=72066578&postcount=4 << on this post
gitlab username: OMJ
thanks again!
SuperR. said:
Thanks for the info. This project is still Beta as marked in the OP. Once we figure out how to solve all the small issues I will update the documentation and the kitchen to try and help everything along as much as possible.
Running as admin in windows brings up another point I forgot about. Apparently Windows can only create symlinks as admin, so if you need to create a system.img you will need to run as admin.
Click to expand...
Click to collapse
You could try creating a batch script that self escalates, and calls "python superr" as Admin. I'm not great with Python by any means. I have a bit more experience with batch.
---------- Post added at 03:28 PM ---------- Previous post was at 03:25 PM ----------
Is there no log file anywhere for errors? Tried to extract a 7.1.2 ROM, and it says there was a problem, but no info or anything.
@SuperR. Do you provide a Free version soon? Does we have to pay another $10 if we using version 2?
dkionline said:
@SuperR. Do you provide a Free version soon? Does we have to pay another $10 if we using version 2?
Click to expand...
Click to collapse
I believe he wants to hold off on a "free" release until more issues have been resolved. That leave those that paid for it with access (limited number of people) to help test it. Also sounds like it leaves those with a slightly more vested interest in it to help with input, as they paid for it, and therefore use it more than those that typically just have the free version.
At least in my case, the $10 I put up is all I needed. No additional money is (currently) required.
chevycam94 said:
You could try creating a batch script that self escalates, and calls "python superr" as Admin. I'm not great with Python by any means. I have a bit more experience with batch.
Click to expand...
Click to collapse
I don't know anything about batch scripts. If you want to write it to help out, I am sure some people would find it useful. I don't even know how to start cmd.exe as admin without right clicking lol
chevycam94 said:
Is there no log file anywhere for errors? Tried to extract a 7.1.2 ROM, and it says there was a problem, but no info or anything.
Click to expand...
Click to collapse
There is currently very limited logging. It is something that I would like to improve on for sure. Please send firmware as requested in the OP and I will have a look.
edit: I just downloaded and extracted the latest bullhead 7.1.2 release on Windows and Linux with no issues.
edit2: Just added the pip commands to the install instructions in the OP
dkionline said:
@SuperR. Do you provide a Free version soon? Does we have to pay another $10 if we using version 2?
Click to expand...
Click to collapse
There is already a free version of the kitchen https://forum.xda-developers.com/ap...chen-superr-s-kitchen-v1-1-50-v2-1-6-t3597434
There is no plan for a free Python version. The free version is Bash and the donate version is Python. Eventually, support for the Bash donate version will end. All donors have already been added to the Python repo. There is no need to donate again for access unless you want to
I'm going to donate again (it'll be later this weekend)...because WOW! thank you for the rewrite in Python! I might love you geeky bro man love.
@SuperR. Ok cool, but no access here on 3.0
name: dkionline
Edit: Im in i see, but no sources visible yet, think you not open before beta is done.
GraveDigger176 said:
I got this Error message when i want start the Kitchen and psutil is installed. I'm on ubuntu 14.04
Click to expand...
Click to collapse
I dont think basic psutils is enough
Might be overkill, but enter this in your terminal
Code:
sudo apt-get install psutils && sudo apt-get install python-psutil && sudo apt-get install python3-psutil && sudo apt-get install python3.5
I had the same error on Linux Mint 18 Sarah, but the kitchen fired straight up for me after I entered the command and received the updates.
Hello,
SuperR. said:
All donors have already been added to the Python repo. There is no need to donate again for access unless you want to
Click to expand...
Click to collapse
I have a small problem:
Code:
[email protected]:~/Documents$ git clone https://gitlab.com/superr/superrs-kitchen3.git
Clonage dans 'superrs-kitchen3'...
Username for 'https://gitlab.com': migascalp
Password for 'https://[email protected]':
remote: Not Found
fatal: repository 'https://gitlab.com/superr/superrs-kitchen3.git/' not found
[email protected]:~/Documents$
migascalp said:
Hello,
I have a small problem:
Click to expand...
Click to collapse
Do it again. It will eventually work.
Edit: Unless you haven't donated.
dkionline said:
Access was granted and notification is there, but source on gitlab not visible.
404 Page not found.
Click to expand...
Click to collapse
Just git clone again. It worked for me after a couple of attempts. Gitlab is unpredictable sometimes.
shoey63 said:
Do it again. It will eventually work.
Edit: Unless you haven't donated.
Click to expand...
Click to collapse
I am already a donor user
thank you for the answer
So, AMlogic have a horrible way of dropping support for their tools.
Decided to make a few of my own. More stable, more efficient and (no longer opensource)!
Also, with the versions of the tools, i decided to base it on the latest version of the amlogic tool and increment it by 1.
ALL DOWNLOADS ARE HERE IN A SINGLE PACKAGE(32.6mb)
BE SURE WINDOWS DEFENDER AND ANTIVIRUS DO NOT INTERFERE WITH THE PROGRAMS AND ALL ITS CONTENT!!!
The only thing i request is that my software is not mirrored or uploaded anywhere else
Wanna create your own ROM? Check out my Android guides on Youtube right Here
And there is also a guide on making a custom firmware with V6.0.0 Here
Feel free to check out my website RD Engineering
A donate version is now available so donate HERE and email [email protected] after you have donated to acquire the donate version
Click to expand...
Click to collapse
Donate version is now free - Visit my website for download link - http://rickydivjakovski.com/
Customization Tool
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Fixes/Features-
-Removed obsolete functions
-Better tool management
-More information displayed
-Fixed changing bootanimation
-Fixed bootanimation orientation
-Added bootanimation dimensions + FPS are now shown
-Fixed displaying wallpaper
-Fixed ability to change wallpaper
-Fixed ability to display bootlogo
-Apps tab now literally shows all apps.
-Added kernel/recovery tab
-Shortcuts to open certain kernel files added
-Shortcuts to open certain recovery files added
-Ability to convert recovery to TWRP recovery
-Option to open Generic.kl(keymap) file
-Ability to add init.d support(system hook)
-Abillity to compile into TWRP flashable zip
-Added option to choose wipe /data
-Added options to choose what files to write
-Faster EXT4 decompression
-Faster way of splitting update package
-Partition verification added
-Ability to save as project
-Repack to USB burn img
-Change bootvideo
-Enable boot video
-DTB editing
-Add/remove required keys for firmware flashing
-Enable adblocking(Donate version only)
-Full vendor partition support(Donate version only)
-Abillity to modify the internal partition table(Donate version only)
-Unpack/Repack the bootlogo
Much more i have forgot..
Bootloader ConsoleFixes/Features-
-Communicate with UBOOT
Burn Card Maker
Fixes/Features-
Formatting happens in the background(no P/Invoke)
Formatting done on seperate thread
Quicker extraction of aml_sdc_burn.UBOOT
Faster file processing
AMLogic Flash Tool
Fixes/Features-
Flash kernel
Flash recovery
Port recovery from device recovery
Port recovery from recovery.img
Port recovery from Upgrade package
Flash after completing port
Backup kernel/recovery to folder
Backup kernel/recovery to flashable.zip
Reboot
Reboot into recovery
Flash zip(coming soon)
Upgrade Info Tool
Fixes/Features-
Basically displaying all needed info about an AMLogic upgrade package
CHANGELOG
Code:
---------------------------->> v6.0.0 <<----------------------------
Built newest make_ext4fs from source
Built newest sparse utillities(simg2img, img2simg etc) from source
Built newest unpackbootimg from source
Built newest mkbootimg from source
Built newest mkbootfs from source
Built newest dtc from source
Newest cygwin libs
Removed the need for multiple copies of the same library
Automater program build system
Better backwards compatibillity support for microsoft windows
Full 5.x.x > 8.1 support(Soon 9.0 aswell)
Code has been cleaned
---[Customization Tool]---
Optimized gathering file contexts
Added support for unpacking/repacking vendor
Fixed 8.x compatibillity issues
Faster repacking
Removed DTB editing(still unpacks/repacks, just makes the tool too slow)
Fixed booting issues with vendor
Support for more launchers
Removed recovery converting
Partition lengths now read from DTB
Added automated debloating(Donate version)
Added abillity to block ads(Donate version)
Quick Unpacker(Donate version)
Added partition table modification(Donate version)
Appended full vendor support(Donate version)
---[Quick Unpacker]---
Initial release(serves the purpose of standard level2 unpack/repack)
---[Unpacker Class]---
Added vendor support
Fixed contexts issue
Fixed 8.x compatibillity issues
Added true timestamp
---[XML Decipher]---
Initial released
Abillity to split files by tags
Abillity to patch files by tags
---[AML Partition]---
Initial release
Abillity to generate simple partition table
---[AMLogger]---
Added more detailed logging
---------------------------->> v5.5.0 <<----------------------------
---[Customization Tool]---
Optimizations to the unpacking process
Fixed typo in packing tab
Fixed simg2img crash
Fixed not booting bug
Fixed SizeInflater creating 1bit bigger bug
Added abillity to repack logo
Fixed disabling tabs while packing
Added option to change bootlogo
---[Unpacker Class]---
Added repacking logo support
Redesigned Unpack logo class
All streams optimized and closed before disposed(freeing resources)
Added ResInjector class(Inject resources to a specific index) - never used in tools..
---[ResPack]---
Added support for unpacking AMLogic resource files
Added support for repacking AMLogic resource files
---[AMLSerialConsole]---
Communicate with the device via serial(UART)
---------------------------->> v5.3.1 <<----------------------------
---[Unpacker Class]---
Fixed contexts typo causing crash
---------------------------->> v5.3.0 <<----------------------------
Added AMLogic driver installer
---[Customization Tool]---
Fixed removal of old DTB combo box items
Removed logging of keys
Fixed double unpacking of bootlogo
Tool now checks for currupt bootlogo(bitmap)
Tool now checks if bootanimation exists
More launcher support(Minix)
---[Unpacker Class]---
Added logging of keys
Fixed detection of null raw image
Quicker EXT4 partition unpacking
Updated file context tool
---[AMLogic driver installer]---
Added worldcup driver to the installer
Added PL2303 driver to the installer
---[Bootloader console]---
Added icon for bootloader console
---------------------------->> v5.2.0 <<----------------------------
Fixed simg2img binary issue
Fixed simg2img binary incompatibillity issues(cygz.dll)
Added missing binary and libraries for bootloader console
---[Customization Tool]---
System is now converted to a raw ext4 img before unpack - longer process but more stable
---[Amlogic Bootloader Console]---
Fixed startup crash
---------------------------->> v5.1.5 <<----------------------------
---[Customization Tool]---
Fixed repack issue with platform configuration
Fixed key check on unpack
Added logging for required firmware keys
---------------------------->> v5.1.2 <<----------------------------
Added platform configuration as a resources
---[Customization Tool]---
Abillity to add platform configuration
Fixeed unpacking level3(logo) when only selected level2
---------------------------->> v5.0.9 <<----------------------------
Fixed startup issue
---------------------------->> v5.0.8 <<----------------------------
Updated context decompiler
---[Customization Tool]---
-Adjustments to logging
-Repaired recovery porting feature
-Fixed kernel replacement issue
-Fixed recovery replacement issue
---[Unpacker Class]---
-Dynamic link libraries are reset on start
-Resolved kernel output directory issue
---[Recovery Converter Module]---
-Preserves file context from previously converted recovery
---------------------------->> v5.0.0 <<----------------------------
Added bootloader console tool
Added Amlogic USB Api
Added AMLogger(My Amlogic tool logging class)
Added AMLUnpacker V2
Added RecoveryConverterModule
Updated CoolADB client
Tools now run COMPLETELY native
The source code is no longer released to the public
Included EOLUtil(my utillity to convert EOL chars between formats)
---[AMLogic Flash Tool]---
-Fixed ADB connectivity issues
-Fixed recovery porting issues
-Updated recovery converter
-Added recovery porting for S905W devices
---[Unpacker Class]---
-Splitting is now done with official binary
-Now includes kernel unpacking/repacking
-Now includes converting file_contexts
-Much quicker in operation
-Quicker method of checking CRC checksums
-Added abillity to split/append the DTB partition
-Added abillity to convert dtb files to and from text
---[Customization Tool]---
-Fixed clearing tmp folder crash
-Updated recovery converter
-Removed the need for JRE
-Fixed issues of unpacking kernel on some computers
-Cleaned up keernel unpacking/repacking
-Added background support for Tanix3
-Added background support for H96 Pro H3
-Fixed replacing recovery/kernel bug(not valid ramdisk)
-Fixed Saving/exporting/loading level 1 unpacks
-Support added for 5.x.x - 7.x.x
-Fixed system length(file size) issue
-Removed add init.d support(problematic for some Android versions)
-Removed port recovery from only this tool, flash tool still has it
-Fixed permissions issue
-Internal checks for successful kernel unpacking/packing added
-Internal checks for successful recovery unpacking/packing added
-Internal checks for successful system unpacking/packing added
-Internal checks for successful dtb unpacking/packing added
-Option to edit remote.conf
-Added support for unpacking meson1.dtb
-Added DTB tab
-Added DTB editor
-Auto DTB line conversion
-DTB editor with search capabillities
-DTB editor with Obsidian theme/syntax highlighting
-Tool now searched for suppoted preinstall directories
-Fixed replace recovery/kernel issue
-Fixed "No changes applied" issue with system
-Full windows 7 support now added
-Added oem partition unpacking support
-Added vendor partition unpacking support
-Updated way of repacking to zip file
-Fixed wallpaper apk still in use
-Added partial packing for upgrade package
-Added partial packing for upgrade zips
-Stronger compression method(avg pack time 1-3 - 4min, 5-7 - 10min, 8-9 - 20min+)
---------------------------->> v4.0.0 <<----------------------------
---[AMLogic Flash Tool]---
Fixed connection errors
Fixed the out of index bug
Adb now included
Custom CoolADB client added
---[Customization Tool]---
Added detection of bootvideo
Added abillity to repack to upgrade package
Added abillity to choose unpack level
Fixed error of not finding launcher
Added abillity to change bootvideo
Added abillity to enable bootvideo
Fixed FC/Error of unpacking
True permissios detected from file_contexts
---[Unpacker Class]---
Now generates image.cfg
Optimizations added to unpacking
Second method of unpacking being implemented
---------------------------->> v3.5.6 <<----------------------------
---[Customization Tool]---
Fixed flash bug preventing rom from being flashed
---------------------------->> v3.1.5 <<----------------------------
Added UpgradePackageInfo tool
Contributions added by Akwhite(jasonnimwegen)
---[AMLogic Flash Tool]---
Fixed connection force close tool bug
Fixed block backup typo
Tool now operates while disconnected
Some functions are now blocked if not connected
Added connection status bar
Fixed shows connected while not connected bug
Added abillity to allow flashing custom block paths
---[Customization Tool]---
Added wallpaper changing for other AML devices with different launchers
Fixed displaying of current file open
---[UpgradePackageInfo]---
Added abillity to show partition layout
Checks Upgrade package size compared to hex size
Abillity to see file sizes
Abillity to show file type
Abillity to show file names
Abillity to show start hex address
Abillity to show end hex address
Shows file count
Shows partition count
---------------------------->> v3.1.0 <<----------------------------
Added AMLogic flash tool
---[Unpacker Class]---
Removed support for commandline unpacking[EXE]
Perfected unpacking of all firmware
Completely unpacked via recognised hex algorithm
Completely generated head via hex algorithm
Option to list upgrade content added
Option to get partition information added
Option to unpack single partition added
Corrected logo unpacking
Extended to support unpacking of kernels/recoveries
Option to split Upgrade Package head(Input package, Output file)
Option to generate partition info(Input package, output txt)
---[Customization Tool]---
Updated TWRP recovery resources to 3.2.1-0
Removed inbuilt unpacking class
Removed inbuild kernel unpacking class
Tool now uses Unpacker Class
Tool now uses Kernel Unpacker class
Fixed SHA1 checking
Added Importing/Exporting project
Drag and drop on icon functionallity
Fixed bug copying update-binary
---[Burn Card Maker]---
Updated icon
---[AMLogic Flash Tool]---
Updated icon
Based on original AMLogic flash tool
Updated recovery resources
Fixes with connectivity
Added option to flash flash kernel or recovery zip(experimental)
Added option to port from upgrade package
Added option to port from recovery.img
Added option to pull recovery from device
Operations are handled on seperate thread
Includes Unpacker Class
Option added to backup kernel/recovery
Option to flash after porting
Rebased UI
Based on .net 4.5 to allow windows 7 compatibillity
Includes CoolADB Class library(also made by me)
---------------------------->> v3.0.2 <<----------------------------
---[Unpacker Class]---
Faster unpacking
SHA1sum verification added(VERIFY file, PARTITION file)
Abillity to unpack VERIFY files(SHA1 sum)
Near perfection of unpacking
---[Customization Tool]---
Fixed not including recovery or kernel while packing
Fixed file context error
Partition verification added
---------------------------->> v3.0.0 <<----------------------------
---[Unpacker Class]---
Used source from my old AML unpacker
Improved functionality and stability
Unpacked by algorithm rather than assuming struction
---[Customization Tool]---
Removed obsolete functions
Better tool management
More information displayed
Fixed changing bootanimation
Fixed bootanimation orientation
Added bootanimation dimensions + FPS are now shown
Fixed displaying wallpaper
Fixed ability to change wallpaper
Fixed ability to display bootlogo
Apps tab now literally shows all apps.
Added kernel/recovery tab
Shortcuts to open certain kernel files added
Shortcuts to open certain recovery files added
Ability to convert recovery to TWRP recovery
Option to open Generic.kl(keymap) file
Ability to add init.d support(system hook)
Abillity to compile into TWRP flashable zip
Added option to choose wipe /data
Added options to choose what files to write
Faster EXT4 decompression
Faster way of splitting update package
---[Burn Card Maker]---
Formatting happens in the background(no P/Invoke)
Formatting done on seperate thread
Quicker extraction of aml_sdc_burn.UBOOT
Faster file processing
XDA:DevDB Information
AMlogic tools, Tool/Utility for the Android Stick & Console Computers
Contributors
Ricky Divjakovski
Version Information
Status: Stable
Created 2018-05-07
Last Updated 2020-09-26
Waw thnnnnnnks
algdu83 said:
Waw thnnnnnnks
Click to expand...
Click to collapse
Ive basically got the Customization Tool finished,will be uploaded in a few hours with fixed functions
Current changelog(V3.0.0)
-playing/changing bootanimation, changing wallpaper, unpacking(Level 1, Level 2 and Level 3 - used for storing raw bootanimation, wallpaper and logo),
-fixed splitting logo.PARTITION
-Bootanimation playback now shows dimensions + FPS,
-More info is shown in the info tab
-unpacking is significately faster
-added pack to flashable .zip
I still havent decided
-if im gonna allow the tool to repack to an AMLogic upgrade package
-if im going to implement the option to convery the recovery.img to a TWRP ported recovery.img
Thnks for your work
possible to add the option for convert rom img to zip
algdu83 said:
Thnks for your work
possible to add the option for convert rom img to zip
Click to expand...
Click to collapse
Yes that is implemented already, just adding the repack kernel and recovery and the advanced tab and done
Super cool thnks
Customization Tool going up
Thread updated, CustomizationTool has been uploaded
And source code is available
Me again!!! Glad to subscribe to your second thread mate!
I dunno if I am happier about actually using the Poison ROM...... Or in fact, these tools here that let me get rid of amlogics cheap nasty undeveloped Asian $h!t ! ....I honestly don't know how THEY flash millions of units efficiently using their tool, i have always thought they must have there own tool at HQ or flash direct to chip before making there boxes!?
Anyways.... I no longer worry about that now! as I no longer dread plugging my amlogics into my PC anymore! (Usually a nervous time for ANYONE dealing with this software!) Thanks to this project!
I have been purely playing around now for last few hours since release..... My Verdict???
Sorry Ricky mate.... It ain't good...
Its f*%king GREAT!!!! WOW!!
I have been patiently waiting on the ROMS progress and thinking that's what I want!..."Hurry up with that bloody PC tool!" BUT... In fact, this has made me a lot happier! And I realise exactly how much this will shape the future for all amlogic users and how important this is to poison ROMs future!
This has twice the features I ever expected! I have realised how much work has gone into this project! I can only imagine! So when I get paid I will post a small donation for all this you give us, thank you!
*if only another 2 or 3 people would follow suit then Ricky can get another s912 unit sorted and help this guy develop the ROM we all enjoy* OH! AND actually let the poor guy use his own ROM!! Lol!
As I said on my first post on the other thread... I am a junior developer that discovered you and your work through googling ROM features I wanted/had planned to make, so I just wanted you to know that I hope to be the first ROM released using this software! (I have some great ideas!) (I'll have to PM the details over!)
And finally if there is ANYTHING I can do to help you or your projects move forward towards greatness...PLEASE let me know! Happy to test for you whilst you get the TV box sorted, I'm sure whiteteaks hands must be pretty full too!
THANK YOU!!!
P.S Im about to delete all amlogic programmes off of my PC!
ErbDroid said:
Me again!!! Glad to subscribe to your second thread mate!
I dunno if I am happier about actually using the Poison ROM...... Or in fact, these tools here that let me get rid of amlogics cheap nasty undeveloped Asian $h!t ! ....I honestly don't know how THEY flash millions of units efficiently using their tool, i have always thought they must have there own tool at HQ or flash direct to chip before making there boxes!?
Anyways.... I no longer worry about that now! as I no longer dread plugging my amlogics into my PC anymore! (Usually a nervous time for ANYONE dealing with this software!) Thanks to this project!
I have been purely playing around now for last few hours since release..... My Verdict???
Sorry Ricky mate.... It ain't good...
Its f*%king GREAT!!!! WOW!!
I have been patiently waiting on the ROMS progress and thinking that's what I want!..."Hurry up with that bloody PC tool!" BUT... In fact, this has made me a lot happier! And I realise exactly how much this will shape the future for all amlogic users and how important this is to poison ROMs future!
This has twice the features I ever expected! I have realised how much work has gone into this project! I can only imagine! So when I get paid I will post a small donation for all this you give us, thank you!
*if only another 2 or 3 people would follow suit then Ricky can get another s912 unit sorted and help this guy develop the ROM we all enjoy* OH! AND actually let the poor guy use his own ROM!! Lol!
As I said on my first post on the other thread... I am a junior developer that discovered you and your work through googling ROM features I wanted/had planned to make, so I just wanted you to know that I hope to be the first ROM released using this software! (I have some great ideas!) (I'll have to PM the details over!)
And finally if there is ANYTHING I can do to help you or your projects move forward towards greatness...PLEASE let me know! Happy to test for you whilst you get the TV box sorted, I'm sure whiteteaks hands must be pretty full too!
THANK YOU!!!
P.S Im about to delete all amlogic programmes off of my PC!
Click to expand...
Click to collapse
Happy to hear the great feedback, this is a big learning curve for me aswell, prior to this i had no idea on assuming programatically generated algorithms, programatically copying byte by byte from hex address to hex address..
but all i can say is what a turn out!
My next mission is to create USB Burning tool with a much better/safer way of flashing, and unlike AMLogics USB burning tool, you will be able to select what partitions to flash
But first i wanna release PoisonRom V3.0 as im more then likely going to brick my device(possibly to an unrecoverable state)..
But this will be a stepping stone towards innovating AMLogic devices
EDIT: as i still dont have a working TV, i havent tested the flashing process of the compiled ROM, so if you could, within custom recovery just flash the ROM(ofcoarse taking a backup prior) and let me know the result, also prior to compiling into a flashable zip, try the change wallpaper option and see if everything goes sweet
EDIT: everything works..
Ricky Divjakovski said:
Happy to hear the great feedback, this is a big learning curve for me aswell, prior to this i had no idea on assuming programatically generated algorithms, programatically copying byte by byte from hex address to hex address..
but all i can say is what a turn out!
My next mission is to create USB Burning tool with a much better/safer way of flashing, and unlike AMLogics USB burning tool, you will be able to select what partitions to flash
But first i wanna release PoisonRom V3.0 as im more then likely going to brick my device(possibly to an unrecoverable state)..
But this will be a stepping stone towards innovating AMLogic devices
EDIT: as i still dont have a working TV, i havent tested the flashing process of the compiled ROM, so if you could, within custom recovery just flash the ROM(ofcoarse taking a backup prior) and let me know the result, also prior to compiling into a flashable zip, try the change wallpaper option and see if everything goes sweet
Click to expand...
Click to collapse
Hello again Ricky,
Sorry for the seemingly late reply, timezones! UK to OZ!!!
Well done!
No problem at all mate, I'm all backed up as per usual and ready to test V3 using your tools whenever your ROM is ready!!
Before it rolls out i could record the flash process so you can see it!! And I'll log it too and send over.
Now... First flash, to test it, you reckon I should flash stock firmware for my device quickly as it came with (previously) incompatible build?:
* 2GB/16GB-7.1.2 * ?
If not I can try with newer stock firmware, the newer build is actually version 7.1.1 for the device I have in mind (AlfaWise H96 Pro dongle) that is how I got on PoisonRom.
Oh! And congrats on Aroma!! Yeahhhhbuddyyyy!
ErbDroid said:
Hello again Ricky,
Sorry for the seemingly late reply, timezones! UK to OZ!!!
Well done!
No problem at all mate, I'm all backed up as per usual and ready to test V3 using your tools whenever your ROM is ready!!
Before it rolls out i could record the flash process so you can see it!! And I'll log it too and send over.
Now... First flash, to test it, you reckon I should flash stock firmware for my device quickly as it came with (previously) incompatible build?:
* 2GB/16GB-7.1.2 * ?
If not I can try with newer stock firmware, the newer build is actually version 7.1.1 for the device I have in mind (AlfaWise H96 Pro dongle) that is how I got on PoisonRom.
Oh! And congrats on Aroma!! Yeahhhhbuddyyyy!
Click to expand...
Click to collapse
if your changing android version(eg. going from android 7.1.1 to 7.1.2) you must flash stock firmware with USB Burning tool or sd boot card maker, until i can find a way to bypass AMLogics ****ty security implemention(still unsure if bootloader or UBOOT or DTB)
I tested the flash option last night at my sisters house, seems like im getting the gist of this blind coding lol
it worked flawlessly
So in theory its as simple as using my customization tool to make your own custom ROM from stock firmware
Id still like to improve EXT4 FS handling a little better, i seen a good bunch of opensource tools for handling EXT4 FS in C#, only problem may be is that it has no documentation on if it supports compressed FS
not possibility to open zip rom?
i dont find it
algdu83 said:
not possibility to open zip rom?
i dont find it
Click to expand...
Click to collapse
will add it next update
Ricky Divjakovski said:
will add it next update
Click to expand...
Click to collapse
Thnkssss
Seems like my tools do it better, ill be updating CustomizationTool soon with big changes to the unpacker + the feature to verify if sha1 sums are correct on unpack
As you can see, my generates wayyyyy more files then standard customization tool
Im also gonna add re-pack to USB burn image and unpack update.zip(packed for recovery)
Updating in within the next hour
Changes
-Customization tool performs partition verification checks on unpack
-Much faster and unpacking in customization tool
-Optimized code for customization tool
-Added new opensource tool - AMLUnpacker(executable and C# class)
Im not adding the abillity to repack as im unable to see how the first 4 bytes of the file generate the .img files CRC32 hash
thanks good job for this tool :good:
zip please
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
WELCOME TO 420 ROM - MAGISK ROM FOR SAMSUNG GALAXY NOTE 20 ULTRA 5G N986B (EXYNOS)
Telegram-Group
Please bear in mind that things will be added as and when my learning and time permits (being a dad with a family and having ADHD myself means things get a lil gnarly) but i will aim to support this ROM as regularly as possible.
Ill usually release a test to one or two users before each release also - :cyclops:
CUSTOMIZABLE ONEUI EDITION MAGISK ROM FEATURES: - with Vol +/- keys
-Add YouTube Vanced - thanks to Vanced peeps github
-Add 3minit battery - thanks G Harrington - if online menus don't appear, install the apk that the module places on your internal storage in the 420rom folder. (PLEASE SEE KNOWN ISSUES FOR INSTALLATION)
-Add 3minit clock - thanks G Harrinton (PLEASE SEE KNOWN ISSUES FOR INSTALLATION)
-Add V4A
-Add custom 420rom bootanimation thanks to @chalmizzle
-Add SamsungSans fonts apk
-Add Goodlock
-Add SoundAssistant (for increased vol steps)
-Add Customized Secsettings (420 banner in every phone info screen) (coming soon)
-Add Custom wallpapers (coming soon)
-Remove Chrome
(further debloat options for stock rooted base)
-Remove Bixby
-Remove Netflix
-Remove kidshome
-Remove Facebook_stub
-Remove FBservices
-Remove Upday
-Remove Onedrive
CORE MAGISK ROM FEATURES
-installs custom secsettings
-Detects OMC code and ensures correct OMC folders and files installed (multi OMC support hopefully coming - thankfully OXM should be sufficient for now - please let me know if your N986B CSC isn't supported and ill see what i can do)
-detects base rom or rooted stock and presents relevant install features and aborts if attempted to be installed on anything else - should help keep non compatible setups intact
-Device detection as i'll will now be supporting several N20 variants
Enabled the following CSC fetures: (thanks @m8980
- Disable shutter sound menu
- AppLock Protection menu
- Support RealTime Network Speed in status bar - working
- Enable Camera during call
- Enabled call recording
- Data usage in quick panel - the feature displays but not the actual data used - if anyone knows a fix, let me know
- Block call number menu
GOOGLE EDITION FEATURES (FURTHER TO THOSE IN ONEUI EDITION MODULE ABOVE)
This Module is based on the main Main 420rom Rom Module but replaces some of the Samsung apps with Google ones. It is recommended to backup your Samsung apps 1st!!!
Installed with Module - Samsung App it replaces
--------------------------------------
Google Phone - Samsung Phone
Google Contacts - Samsung Contacts
Google Messages - Samsung Messenger
Google Chrome - Samsung Internet Browser
Google Calculator - Samsung Calculator
Google Calendar - Samsung Calendar
Google Clock - Samsung Clock
Google Drive - Samsung Cloud (stays installed)
Google Files - Samsung MyFiles
Google Fit - Samsung Health (can be reinstalled from Galaxy Apps)
Google Pay - Samsung Pay
Google Keep Notes - Samsung Notes
Google Photos - Samsung Gallery
Google Recorder - Samsung Recorder
Google TTS - Samsung TTS
Google Duo - n/a
Google News - n/a
Google Tasks - n/a
Google Sounds (Sound Picker) - n/a
Google Apo - n/a
Google Carrier Services (for RCS) - n/a
GBoard - Samsung Keyboard
GMail - Samsung Email
YouTube Music - Samsung Music
YouTube Vanced, Vanced Manager & Vanced MicroG - YouTube
Nova Launcher - OneUI Launcher
RECOVERY FLASHABLE BASE FEATURES
-Does away with warning on splash
-Debloated a fair whack but not too much
-rebased with each firmware update (when possible)
-rooted with magisk manager
-latest disabler from @ianmacd included (cheers for this and TWRP mate)
-flashes latest TWRP during Base flash
Changelog
v3.8 (3.7 unreleased)
- rebase to DUF8 - July patch
V3.6
- Main big change is that install options are now taken care of by the (now renamed) MASTER MODULE - you will be presented with your installation options on the first zip you install - these will then be picked up by the ROM MODULE that will automatically flash the relevant features selected in the MASTER MODULE flash.
- Rebased to DUDA - (next update will probably just be a rebase as new June firmware will be here v soon)
- Magisk v23 installed
- I have included the Audio Modification Library module for until they sort V4a out. The process to get v4a working is:
1 - Activate the AML module in magisk and reboot then when rebooted into system start v4a and install drivers (it will reboot)
2 - on reboot, disable the AML module and then reboot system once more
3 - when rebooted to system, start v4a and reinstall the drivers
4 - v4a should be functional after reboot
V3.5
This version brings a lot of automation to the install process. The mother module script will detect if the convertor has been flashed over that particular firmware and then make the convertor zip automatically if it is needed - in the case of reapplication of the rom or if i bring out an incremental update on the same firmware then this will mean that the convertor will be skipped by the mother module script and the rom module will be made only.
In short, the Mother module does my job by cooking the rom module and convertor mid flash
-Also rebased to DUD1 firmware
v3.4 Simple rebase to DUC8
- rebase to DUC8 firmware and most recent TWRP added
v3.3 no more disabler required after odin flash
- disabler files now added to odin files, no standalone disabler flash required anymore.
- rebased to DUC1 March patch
- workaround was required for wallpapers and will have this back to normal next time but end result is exactly the same. We're just using the DUB6 apk in this firmware no wallpapers were showing with DUC1 wallpaperres.apk
V3.2 another big update!!!! - in addition to the changes brought in recently, i have decided that patching system files instead of replacing them will be better going forward - the upshot for you guys is that the install process is even quicker now and the total package size has gone from 500mb to 240ish mb, yet the end result is exactly the same as any other release The convertor copies the relevant files from device and the rom module makes the amendments needed.
- fixes to backup and restore function
- tidied up script a bit
Now live in link in first post!!!
3.1- smallish update in comparison but still needed
- Home up added to goodlock package in rom - this incorporates task changer
- fixed Auto backup backing up previous rom options when new Rom Module selection option is selected (i.e no to restoring)
- Will now NOT install if any firmware version other than the one matching the rom is present
3.0- addition of Rom Module options backup/restore and rebase to OneUI 3.1:
- I have created a new Rom Module backup and restore function which will read the setup of the last rom module install (v2.6 onwards only) and ask you if you want to restore your previous install options. It will also backup any CSC features choices you make. This was not easy due to the complexity of my other function
-soundassistant updated
-some script optimisations and tidy ups
-completely rebased to DUB6 OneUI 3.1 - hence V3.0
-CTS fix working perfectly and is included as an install option
2.5 - big refinement on changes in 2.4
- module base convertor now installs the cts fix module automatically and systemlessly
- the Mother Module sends the convertor to internal/420rom which will then delete itself after flash and replace it with the rom module in internal/420. This is because it could be confusing with so many folders
- convertor now clears any old 420rom modules
- the convertor checks for old internal 420rom directory and clears it if detected then sets up a new one.
- more general automation and tidy ups in scripts applied
- advanced power mode app added for booting to recovery on the fly easier
2.4 - Big format change - see second post
2.3.2 - incremental update
- Added CTS safteynet fix by @kdrag0n - (huge thanks for your contribution to the community man!!!) - thread
2.2-2.3.1 (unreleased xmas testing)
Rom-module
- rebased files to CUA2 Jan firmware
- moved all install and extract code to functions which are each called when you select an install option for the magisk rom module features - main upshot is that it saves a **** load of time installing the module. The long boring extraction list before the install options is now a past nightmare
- tidying up the script big time - variables defined for mod extraction paths etc - makes debugging much easier haha
Module Base
- rebased to CUA2 Jan firmware
- Latest TWRP from Ianmacd included from now on - the base will automatically flash this.
- updated disabler included
- Magisk updated to V21.2
v2.1 (unreleased) & 2.1.1
- Full script rewrite for a big big change in cscfeatures implementation method
- csc features are now selectable should you not wish to install all of them
- updated source to CTL5
- CSC mod fixes
- bugs and performance fixes
v1.1/1.1.1
-changed default wallpaper
-compressed mods in module zip to save space
-added debloat to updater script - debloat is carried out after image flash (fixed issues in 1.1.1)
-general theme refresh
-fixed sound assistant not installing
v1-b6-b10
-added CTS fix
-added wallpapers
V1-b5
-implemented updated 3minit install procedure @starbucks2010 - cheers for the help and code for my flashable zip
-added updated YoutubeV manager etc - install youtubeV from manager is recommended
-tidied up install script
V1-b3&4
-unreleased, research mules for failed patch testing :laugh:
V1-b2
- initial xda release
what's next? & Known Bugs we can't do much about or will sort eventually
-N980F/N985F support
-Google edition of the module
-incorporation of further goodies into magisk rom and base
-if A SYSTEM APP hasn't been removed, try uninstalling it you should now be able to - any updates installed over an original system app remain as they are data apps following an update
CORE DEV TEAM
Myself - team owner and Rom Module chef
@abun880007 - team co-conspirator
Huge thanks to.................
@abun880007 for the legendary support and collab
@Zackptg5 for the brilliant MMT Extended zip
Rooted with Magisk - thanks @topjohnwu
@topjohnwu for magisk
@Winb33) for the samsungsans7.2 fonts
@superr for the kitchen
@starbucks2010 @ASHLEY117 & @ZonalRipper for showing me winrar was sh## and for all you help with getting around these invisible system.dat.br issues i was having! :good::laugh: link to Beyond Rom S20 Thread
@Team_DeWitt for the Awesome V4A 2.7 - a must have for audiophiles!!
G Harrington for the 3minit apps
Team Vanced for bringing us all youtube Vanced
@dr.ketan for the various pointers and sage advice
Finally, @m8980, thanks for letting me adapt your CSC features into my module. :good::good::good:
DOWNLOADS
MASTER MODULES
STOCK ROOTED ODIN FIRMWARE
XDA:DevDB Information
[MAGISK Rom & Base], ROM for the Samsung Galaxy Note 20 Ultra
Install procedure for V2.4 onwards has changed drastically as has the format of the module base itself
From now on N20U and soon on N10 and Tab, there will be no more 4gb zip files to flash (im sick of the time wasted waiting for copying and flashing lol) - the total size of files has gone from 4.5GB to 450mb but you will have exactly the same end result!!!!!!
I have created an "Mother Module" or "MM" which, when flashed in Magisk, places a (Magisk installed) Rom Module zip and a (TWRP flashable) Module Base Convertor zip into their own folder on internal/420.
The next thing to do is to go to TWRP and locate the Module Base Convertor zip and flash it. This will apply all debloat and This will also trigger a marker that will allow the rom module to be flashed.
Once the first zip is flashed, you can then go and install the rom module as normal in Magisk
I will be providing rooted stock firmware to start the whole thing off
BEFORE YOU START. DO NOT ATTEMPT TO FLASH THIS OVER A DIFFERENT DEVS ROM - IT WILL CAUSE ISSUES. BACKUP APPS AND DO A FRESH STOCK INSTALL FIRST - that's even if you get past the failsafe
Install process assuming you are on matching firmware to the released Rom and rooted
1, Flash the mother module in Magisk - reboot to TWRP
2, In TWRP, flash Module Base Convertor located in internal/420- this will apply all the modifications and debloat to your rom that i used to on the Old full size zips
3, reboot and install rom module in Magisk as normal- all done!!!
Install Process assuming you are coming from earlier 420rom:
1, Using the odin files i have provided, flash BL, Modded AP, CP and HOMECSC in Odin with AUTOREBOOT off
2, Keeping phone plugged in, hold vol down and power to exit download and immediately hold vol up and power to enter TWRP.
3, flash Multidisabler & reboot.
4, Flash the mother module in Magisk - reboot to TWRP
5, In TWRP, flash Module Base Convertor - this will install a few generic niceties seen on the module bases of old (No red text etc) and debloat a fair whack of crap out
6, reboot and install rom module in Magisk as normal- all done!!!
on a side note........................
How i patch and add TWRP to the Stock AP file - aka making stock rooted odin flashable files
Producing a stock rooted firmware is really easy and i would hope it would be part of people's standard updating process from now on & will take most people 10 mins if instructions on Xda are read through but I will make them nonetheless.
1, extract firmware zip so you have BL, AP, CP and HOMECSC visible (Put CSC aside)
2, copy AP to internal on phone and patch with Magisk (install -> select and patch file). Once done, copy the Modded AP file (also called magisk patched tar) that Magisk produced from /downloads on your phone's internal storage back to your firmware folder - call this one Modded AP or whatever.
3, get the latest TWRP and rename to recovery.img, drop the image into the magisk_patched.tar (delete recovery.img.lz4 if present)
4, extract the BL folder and delete vbmeta.img.lz4 in the extracted folder, pull out vbmeta.img from magisk_patched.tar and copy to the BL extracted folder - re-tar this BL folder using 7z. DO NOT REMOVE VBMETA.img from magisk_patched tar - call this one modded BL file or whatever.
5, you can now go ahead and flash Modded BL, Modded AP, CP and Homecsc in odin
Reserved
another
one more
Yes!!! Definitely rooting and flashing!
Sent from my [device_name] using XDA-Developers Legacy app
speedyjay said:
yes!!! Definitely rooting and flashing!
Sent from my [device_name] using xda-developers legacy app
Click to expand...
Click to collapse
hello maaaatttteeee!!!!
Hi, I just wanted to know, with this rom, can you edit and modify system apps? Because am unable to do it, when I try to remove a system app, it won't let me. With the s20 this is fixed installing the vbmeta_disabled file.
Looks nice
mcgomfer said:
Hi, I just wanted to know, with this rom, can you edit and modify system apps? Because am unable to do it, when I try to remove a system app, it won't let me. With the s20 this is fixed installing the vbmeta_disabled file.
Click to expand...
Click to collapse
Can you possibly point me to this? could find this very handy (if it's shareable)
Thanks for the work.
Need a detailed installation guide.
Hi, are there any instructions for flashing this rom, because am flashing, but when finished and rebooting, it goes into bootloop.
tuanduy7453 said:
Thanks for the work.
Need a detailed installation guide.
Click to expand...
Click to collapse
Yeah, a detailed installation guide would be great.
Install procedure in second post
Dex not working
Samsung DEX doesn't seem to be working, tried to connect it to Samsung tv, but won't work. Any idea how to fix this?
Play store crash... Goodlock navbar not supported
and i cant take screenshot everywere it says... U cant bcoz of security policy.....
Nice working rom waitin more updates
ok now i have gotten past a tonne of the quirks this new device is throwing out so will be releasing an updated base and module shortly.
- any users of 3minit wont have to install the apk manually - just flash a zip i will provide and then select the option in the module install steps - took me a while to get my head around the /system mounting lol
- add themed secsettings
- add wallpapers
- take a look at Dex issue - can anyone else confirm this issue?
exocetdj said:
ok now i have gotten past a tonne of the quirks this new device is throwing out so will be releasing an updated base and module shortly.
- any users of 3minit wont have to install the apk manually - just flash a zip i will provide and then select the option in the module install steps - took me a while to get my head around the /system mounting lol
- add themed secsettings
- add wallpapers
- take a look at Dex issue - can anyone else confirm this issue?
Click to expand...
Click to collapse
Dex working fine for me.
For me DEX isn't working won't connect with Samsung smart TV.
tbalden's
CleanSlate kernel
for Asus ZenFone 9
The User Experience Kernel leaning towards Stock Stability plus UX features.
Rock stable stock approach, performance smooth and issue free
"No-Root is a State of Mind"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As always tbalden is here to bring you authentic new features first in line, this year Asus ZF9.
No root elevation (magisk) needed for all functions and preference switches through CS Config App
Release Calendar
Version 2.4.0 - 13 of Dec 2022
Version 1.4.2 - 28 of Oct 2022
Version 1.0.0 - 29 of Aug 2022
Should work on official ROM bases 32.2050.2050.x+.
Features:
- Flashlight Notification/Call blinking (see video below)
- Vibrating Notification Reminder (DETAILS)
- Notification In-Pocket Booster boost notifications vibrations while phone is in pocket
- Haptic Type Tweak change haptic feedback waveform types
- K.AdAway adblocking built-in kernel only, All browsers, Apps web-ads, except YouTube / streaming / Facebook ads
- SafetyNet pass passes if using without Magisk/Rooting, flashing the boot img only, Google Pay should work
- Sweep to Sleep gestures - highly customizable
- DoubleTap & LongTap on corner area gestures - new way to pull down android Notification Area or screen off
- Sweep/Tap gesture to force close foreground app - DETAILS HERE
- Battery Saver cut back max CPU freqs, 3 levels + touch boost limiter options
- Face down screen off - put phone face down to turn screen off
- Kernel Log / Crash dump to internal storage/sdcard - no root/magisk needed, from Companion App use Kernel Log button
- CleanSlate Companion / Config - rootless app to configure
Facts:
- no root required, use /sdcard/uci_user.cfg file to configure 99% of the features without rooting. If you need tweak apps (e.g. EXKM / FK) you'll need rooting!
- built on top of kernel sources released by ASUS, 5.10.x
- built with standard toolchain for stability and efficiency
- built with Control Flow Integrity sec hardening from Android S versions onwards
- kept stable, no tweakings, just features
- stable and reliable, keeping close to stock except addition of Usability features
Requirements
- Unlocked ZF 9, stock or with magisk root
- BACKUP: make sure you have a stock image (boot img) from asus before installing this!
Installation Guide
Firstly install CleanSlate configuration and CleanSlate companion apps on your phone (both found down below in Download section). (On play store version: with Android 12 you need to join the Beta program for the correct app versions.) Set them up initially.
- Non-rooted method: 0. download the non-rooted boot img.zip, UNZIP it first!
Reboot to bootloader, and flash the images with these commands:
Code:
adb reboot-bootloader
fastboot flash boot full_img/boot.img
fastboot flash vendor_boot full_img/vendor_boot.img
fastboot flash dtbo full_img/dtbo.img
fastboot reboot fastboot
fastboot flash vendor_dlkm full_img/vendor_dlkm.img
fastboot reboot
.. reboot, enjoy
- Rooted method: 0. download the rooted installer zip
1. install magisk
2. use a Kernel Flasher to flash the installer zip
- For SafetyNet, Adblocking, after flashing you might need to restart the phone after the first boot, otherwise it might not work.
- For adblocking KAdaway switching on and off, you will need to Force Close browser app like Chrome to let it work in the given browser.
- For Play Integrity (with SafetyNet passing) you might need to Clean App Data in Google Play Store app to make it reevaluate Integrity
--- If you have magisk installed Play Integrity might be tripped. I only tested without Magisk, flashing CleanSlate 1.0.0 bootimage.
- If using Companion App for notification / gesture etc features, there's a setting in the app to Switch off Proximity sensor while Screen is on. This will prevent the flickering, but Face down screen off feature won't work
Known bugs
- None, please tell
- please disable magisk modules before reporting issues, and please provide logs if possible
Download
Android 13
Non rooted, Android 13 images
ZF9 non rooted installer images zipped - 33.2060.2060.65 WW - CS 1.4.2: https://forum.xda-developers.com/attachments/fastboot_cleanslate_s_zf9_240_imgs-zip.5784177/
Rooted installer zip, Android 13 images
ZF9 to flash from rooted phone with Kernel Flasher: CS 2.4.0: https://forum.xda-developers.com/attachments/cleanslate_s_zf9_240-zip.5784179/
Android 12
Non rooted, Android 12 images
ZF9 non rooted installer images zipped - 32.2050.2050.29 WW - CS 1.4.2: https://www.androidfilehost.com/?fid=14871746926876840958
Rooted installer zip, Android 12 images
ZF9 to flash from rooted phone with Kernel Flasher: CS 1.4.2: https://www.androidfilehost.com/?fid=14871746926876840957
Non rooted, Android 12 image
ZF9 boot image zipped - 32.2030.2030.26 WW - CS 1.0.0: https://www.androidfilehost.com/?fid=14871746926876840958
Config Applications
Companion App 3.3.x-- Donation premium on PlayStore:
You need to join the BETA program to get the working version for the kernel!
https://play.google.com/store/apps/details?id=org.cleanslate.csservice
Configuration App 3.2.x -- Donation premium on playstore:
You need to join the Beta program to get the working version for the kernel!
- additional features in premium app: App Themes, Profiles, Profile Switch QuickTiles
https://play.google.com/store/apps/details?id=org.cleanslate.csconfig
How to join beta program: https://forum.xda-developers.com/t/...ashlight-s2s-vib-dec-22.4281807/post-86171493
Android 12:
Companion App 3.3.9 -- Normal free download:
https://www.androidfilehost.com/?fid=15664248565197208875
Configuration App 3.2.11 -- Normal free download:
https://www.androidfilehost.com/?fid=14871746926876820727
Donation:
If you appreciate this, don't forget to hit the Thanks button, Vote 5 stars on Thread, or consider to Donate. Donations here
Thank you!
Donators Hall of Fame
Much appreciation and many thanks go to...
@velimirchek
@MarcoG:
@guidogsbn
@The Great Dane
@Whiskey103
@purple patch
@panosmdma
@sttw1fa
@jelive
@beartiger
@st_voss
@bigruss
@deagleone
@DroidIt!
@8bitbang
@Will972
@smallKING81
@mick_soul
@p50kombi
@K4Y3
@ dieter
@michaelbsheldon
@dioooi
@ali nz
@bstiti
@Oddvin94
@norgan
@lol8888
@twinnfamous
@cameljockey1
@Cryptycat7
@Pasqui1978
@4ntagonist
@turbo jjjang
@munkyvirus
@knopie
Special thanks to AnyKernel installer developer: osm0sis
To @Freak07 for all his work on XDA and help
To @Captain_Throwback
Sharing policy:
As this is all GPL licensed kernel source, you can use it in your code, but don't forget about proper credit.
Source Code: https://github.com/tbalden/android_kernel_asus_zf9_common-kernel
Readme's and howtos
Changelogs come here later
Be aware that in Battery Saver feature, there's CURRENTLY NO CAMERA APP FOREGROUND DETECTION! Please disable this feature when you use Camera apps (otherwise slow camera, video recording)!
Hopefully camera detection can come later, as still working on more features.
nice work!
great to see you here
Great develop
Thanks for sharing! If I have the patience to get the C version when it eventually releases, I'll give this kernel a try!
- Update Android 12 Stable - 1.4.0 -
Major CleanSlate feature update
- Build and repack to QGKI2 kernel format (boot, vendor_boot, vendor_dlkm, dtbo images) with new scripts
--- Thanks go to @Freak07 for the teamwork of many hours in getting to the bottom of this crooked path to build Qualcomm's new modular kernel format and make it work on the ZenFone 9
--- Thanks go to ASUS for providing the most complete sources zip for Qualcomm based QGKI kernels up to date by ANY vendor/OEM.
--- Thanks go to @osm0sis for his AK3 installer and @capntrips for his excellent tooling in AK3 and the tips help he lended in the process of getting things rolling
- Now all features possible to implement added to drivers
-- New:
---- Flashlight notifications
---- Vibrating Notifications reminder
---- Gestures Features: Sweep/Tap in corner gestures added
---- Fingerpint customization added:
----- FP: Possibility to let 4 types of Fingerpint event types to be mapped by third party mapper apps like Button Mapper
----- FP Possibility to set a Double tap to sleep mode on Fingerpint sensor (with possibility of keeping swipe up / down stock feature enabled/working)
---- Double Vibration feature on Phone Calls in DND or Silent mode
-- Updates
-- Hosts file for KAdaway
-- Safetynet + Play integrity still passes without Magisk
-- All features work with or without Magisk (tho flashing magisk will break safetynet until you use SafetyNet fix magisk modules)
Two types of installation methods provided.
- One installer ZIP for magisk rooted kernel flasher apps (like Kernel flasher or EXKM)
- One fastboot ZIP for solely fastboot based from command line with an example linux script to flash, for those who don't want to use Magisk. Be aware that if you flash by this fastboot method, vendor_dlkm flashing works, but will downsize the vendor_dlkm partition. So if you want to flash other kernels in rooted kernel flasher apps, you need to go to fastbootd, flash a stock vendor_dlkm.img (and then also flash in fastboot stock boot/vendor_boot/dtbo for a bootable state) to get back to the stock sized partition and then only after that you can flash AK3 installer zips.
CleanSlate S 1.4.0 Downloads:
Rooted installer zip:
CleanSlate S 1.4.0: https://www.androidfilehost.com/?fid=14871746926876820728
Non rooted, Android S images for fastboot based flashing (firmware wwe 31.2030.2030.26)
fastboot image zip CS 1.4.0: https://www.androidfilehost.com/?fid=14871746926876820729
Cleanslate config app version 3.2.11 needed for new features:
Free version download: https://www.androidfilehost.com/?fid=14871746926876820727
Premium version: https://play.google.com/store/apps/details?id=org.cleanslate.csconfig&hl=hu&gl=US
- rolled out to playstore Beta program
Read first post in thread for installation details.
Will it run with the latest fw update?
NisseGurra said:
Will it run with the latest fw update?
Click to expand...
Click to collapse
It actually runs, but new sources are up, and I'm updating the installers soon.
- Update Android 12 Stable - 1.4.1 -
CleanSlate asus sources update
-- sources updated to 2040.23
-- Hosts file for KAdaway
Two types of installation methods provided.
- One installer ZIP for magisk rooted kernel flasher apps (like Kernel flasher or EXKM)
- One fastboot ZIP for solely fastboot based from command line with an example linux script to flash, for those who don't want to use Magisk. Be aware that if you flash by this fastboot method, vendor_dlkm flashing works, but will downsize the vendor_dlkm partition. So if you want to flash other kernels in rooted kernel flasher apps, you need to go to fastbootd, flash a stock vendor_dlkm.img (and then also flash in fastboot stock boot/vendor_boot/dtbo for a bootable state) to get back to the stock sized partition and then only after that you can flash AK3 installer zips.
CleanSlate S 1.4.1 Downloads:
Rooted installer zip:
CleanSlate S 1.4.1: https://www.androidfilehost.com/?fid=14871746926876834460
Non rooted, Android S images for fastboot based flashing (firmware wwe 31.2040.2040.23)
fastboot image zip CS 1.4.1: https://www.androidfilehost.com/?fid=14871746926876834462
Read first post in thread for installation details.
Installed, seems flawless
2040.28 update is up, with sources. The new sources has no changes, tested, I'm using the .23 based cs kernel without issues.
- Update Android 12 Stable - 1.4.2 -
CleanSlate asus sources update
-- sources updated to 2050.29
-- Hosts file for KAdaway
Two types of installation methods provided.
- One installer ZIP for magisk rooted kernel flasher apps (like Kernel flasher or EXKM)
- One fastboot ZIP for solely fastboot based from command line with an example linux script to flash, for those who don't want to use Magisk. Be aware that if you flash by this fastboot method, vendor_dlkm flashing works, but will downsize the vendor_dlkm partition. So if you want to flash other kernels in rooted kernel flasher apps, you need to go to fastbootd, flash a stock vendor_dlkm.img (and then also flash in fastboot stock boot/vendor_boot/dtbo for a bootable state) to get back to the stock sized partition and then only after that you can flash AK3 installer zips.
CleanSlate S 1.4.2 Downloads:
Rooted installer zip:
CleanSlate S 1.4.2: https://www.androidfilehost.com/?fid=14871746926876840957
Non rooted, Android S images for fastboot based flashing (firmware wwe 31.2050.2050.29)
fastboot image zip CS 1.4.2: https://www.androidfilehost.com/?fid=14871746926876840958
Read first post in thread for installation details.
Is there any way to add vowifi or volte without rooting with a kernel like this?
Hello,
I recently buy this phone and wanted to increase the battery life of this phone.
This seem to be an good option, but have you information about battery life with this kernel ?
Thanks you.
Hi,
I don't know what I'm doing wrong but got into quite a bit of bootloops trying to install it, the non-rooted version.
Started by installing the files in the last post directly when in fastboot. This resulted in this message, followed by a bootloop at the ASUS logo :
Writing 'vendor_dlkm' FAILED (remote: '(vendor_dlkm_a) No such partition')
Then, to get out of it, downloaded the ASUS official image, uncompressed the individual files and flashed some of them according to an Internet post, which solved my problem and then the phone could boot again normally.
Then, I decided to flash the cleanstate img file in the first post, followed by the files in the last post, using the sequence described in the bash file. Again, bootloop! Resolved it this time by flashing the same cleanstate img file only and leave at that.
After OS booting, I see that the kernel is definetly there and it seems that ads are being blocked (my main reason to install it).
The kernel version is 5.10.81-cleanstate-100-android12-9.
So, my question is : what did I do wrong and what is the purpose of the new files since they no longer contain a cleanstate img file in the zip file?
Thanks in advance,
dragonii said:
Hi,
I don't know what I'm doing wrong but got into quite a bit of bootloops trying to install it, the non-rooted version.
Started by installing the files in the last post directly when in fastboot. This resulted in this message, followed by a bootloop at the ASUS logo :
Writing 'vendor_dlkm' FAILED (remote: '(vendor_dlkm_a) No such partition')
Then, to get out of it, downloaded the ASUS official image, uncompressed the individual files and flashed some of them according to an Internet post, which solved my problem and then the phone could boot again normally.
Then, I decided to flash the cleanstate img file in the first post, followed by the files in the last post, using the sequence described in the bash file. Again, bootloop! Resolved it this time by flashing the same cleanstate img file only and leave at that.
After OS booting, I see that the kernel is definetly there and it seems that ads are being blocked (my main reason to install it).
The kernel version is 5.10.81-cleanstate-100-android12-9.
So, my question is : what did I do wrong and what is the purpose of the new files since they no longer contain a cleanstate img file in the zip file?
Thanks in advance,
Click to expand...
Click to collapse
Hi, I'm not sure what's happening there, but the second zip with the example script does have all the images in a folder named full_img.
Sorry for the confusion, the installation guide in the first post isn't reflecting that structure, but it's all in there.
The commands to do are:
Code:
adb reboot-bootloader
fastboot flash boot full_img/boot.img
fastboot flash vendor_boot full_img/vendor_boot.img
fastboot flash dtbo full_img/dtbo.img
fastboot reboot fastboot
fastboot flash vendor_dlkm full_img/vendor_dlkm.img
fastboot reboot
tbalden said:
Hi, I'm not sure what's happening there, but the second zip with the example script does have all the images in a folder named full_img.
Sorry for the confusion, the installation guide in the first post isn't reflecting that structure, but it's all in there.
The commands to do are:
Code:
adb reboot-bootloader
fastboot flash boot full_img/boot.img
fastboot flash vendor_boot full_img/vendor_boot.img
fastboot flash dtbo full_img/dtbo.img
fastboot reboot fastboot
fastboot flash vendor_dlkm full_img/vendor_dlkm.img
fastboot reboot
Click to expand...
Click to collapse
So, according to you, I should just take the latest zip file and run the commands in fastboot mode even if I flashed already the cleanstate img file in the first post?
EDIT: did it already and no more error messages with version 1.4.2. Thanks !
Hi again,
How can I access these features? There are not showing up in the CleanSlate Configuration tool.
-- New:
---- Flashlight notifications
---- Vibrating Notifications reminder
---- Gestures Features: Sweep/Tap in corner gestures added
---- Fingerpint customization added:
----- FP: Possibility to let 4 types of Fingerpint event types to be mapped by third party mapper apps like Button Mapper
----- FP Possibility to set a Double tap to sleep mode on Fingerpint sensor (with possibility of keeping swipe up / down stock feature enabled/working)
---- Double Vibration feature on Phone Calls in DND or Silent mode
Thanks in advance,