DEVELOPING OF ASSAYYED KITCHEN HAS STOPPED DUE TO PERSONAL REASONSTHE FULL ROMs & APKs & FILE_SYSTEMs EDITOR FOR WINDOWS V1.82
{
"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"
}
Hello everyone, i want to introduce a new kitchen for windows (ASSAYYED KITCHEN)
Features:
Supports these types of Roms:
Stock samsung updates (tar) or (tar.md5)
Stock image files (system.img, boot.img, cache.img)
Stock sony updates (ftf)
Stock sony rom files (system.sin, kernel.sin)
Zip contents multi tar files
Zip contents ftf files
Zip contents normal system folder
Zip contents sparse_chunks like Motorola roms
System.yaffs2 with kernel
System.ext4 with kernel (converted using flashtool)
Zip contents ext4 system.img with kernel
Zip contents system.new.dat with transfer.list and kernel
Support remove extra header for motorola roms
Any system folder placed in work folder in the kitchen
Supports get valid rom with kernel from:
Rooted/Unrooted device booted to
Device booted to custom recovery
Supports to pull symlinks from device using (ls -Rl /system) command even without root
Supports deodeox process:
All version from first up to the last
All devices manufactures (Sony, samsung, lg......)
All devices architectures (arm, mips, x86)
All devices cpus (32, 64) bit
Fast and simple process with show count of apks deodexing
Supports add root SuperSU last version:
All version up to last
Add root installer for CM/AOSP roms
Add root for 5.1.1/6.0.1+ in system-less or system mode with patch sepolicy
Supports these types of rom recovery installer (META-INF):
Build standalone installer
Build aroma installer
Full Support for FlashFire
Compatible with all partitions (ext4, F2FS)
Support dual booting
Set correct permissions for all version
Set (set_perm) permission for version 4.2.2-
Set (set_metadata) permission for 4.3+
Detect files contexts from kernel
Set all permission for all files in file_contexts in kernel that not listed in the kitchen list
Detect all LOCAL symlinks in the rom
Detect symlinks from stock images (system.img) using (find -type l) same as linux
Detect all symlinks from updater-script for old cooked rom and fix them
Extract file_contexts automatically from boot.img or from work folder or from kernel.elf
Add efs backup for installer for samsung roms
Add script to wipe data before installing
Add script to tuning device filesystems into ext4 journal_writeback
Contents file include more than 550 symlinks for rom that doesn't content local symlinks
Supports these type of building:
Normal zip contents system folder
Zip contents ext4 system.img
Zip contents system.new.dat with transfer.list
Sign zip file created whatever the size is big
Tar rom same as samsung official updates contents sparse image
Support sparse header 28 and 32 bit and build (img) or (ext4) extension
Detect valid system folder size automatically
Detect device system partition size from adb
Allow user to write the size in Bytes or Kbytes or Mbytes
Detect the system block path from kernel or write from user or from adb
Supports these types of debloating the rom:
Remove samsung knox completely
Remove a lot of apps and folders to debloat the rom automatically
Print all rom apks to user and give choice to select an apk number to remove it (manually debloating)
Remove all samsung csc apks
Cleaning up all rom apps to remove broken apks
Support custom debloat list
Very easy to edit the original debloat/deknox menus
Supports unpacking/repacking kernels/recoveries:
Support 3 methods to unpacking and repacking the kernel/recovery
Support the kernels that built using linux toolchain
Support extract ramdisk packed using (lz4, lzop, lzma, gzip, xz and bzip2)
Make adb insecure in default.prop
Add init.d support in init.rc in the kernel
Add adbd to (ramdisk/sbin) to make adb run in root mode
Remove dm-verity
Remove force-encrypt
Patch sepolicy using device
Convert kernel.elf to boot.img
Fix kernel/recovery is not SEANDROID enforcing
Supports converting between file_systems images (separate menu):
Extracting files from (cache.img/hidden.img/userdata.img)
Extracting files from TWRP recovery backups
Convert between [sfs] and
[*]Convert between [dat] and [img]
[*]Convert between [ext4] and [sprase_28_32]
[/LIST]
[B][SIZE="3"][U]Supports apktools:[/U][/SIZE][/B]
[LIST]
[*]Apktool includes (last & 1.5.2 versions) for new and old versions
[*]And support print all apks, jars and dexs in rom then select apk to decompile and recompile
[*]Decompile apk, dex, jar files automatically
[*]Signing selected apks with install sources framework apks
[/LIST]
[B][SIZE="3"][U]Supports these extra features:[/U][/SIZE][/B]
[LIST]
[*]busybox last version
[*]Sqlite version 3
[*] sysro and sysrw to mount system read,write during adb connection
[*] Custom bootanimation for all versions
[*]A lot of build.prop tweaks and some init.d tweaks
[*]init.d support in rom itself without kernel
[*]Add su.d support
[*]Add custom zips to install with the rom in the recovery like (busybox, xposed......etc)
[*]Change build number as the user wants
[*]Add personal info in installer (Aroma and stanalone)
[*]Add changelog.txt and license.txt in aroma installer
[*]Push ready roms to the phone to external or internal storage
[*]View installer information
[*]Unlimited count of roms and projects and support save project and restore it
[/LIST]
[B][SIZE="5"][COLOR="Blue"][B]Design:[/B][/COLOR][/SIZE][/B]
[LIST]
[*][B]The kitchen uses 7zip (last version) to extract ext4 images (support extract symlinks on FAT32 and NTFS)[/B]
[*]Compiled into exe file with administrator manifest for better working
[*]Support all windows versions and 64/32 bit
[*]Easy usage with main menu list support
[*]Using linux tools compiled into busybox.exe
[*][B]For kernel path and the databases the kitchen supports all devices in the world[/B]
[*][B]Auto detect for kernel path using shell script in recovery and flash the kernel to the correct path[/B]
[*][B]This means you don't need to worry about detect the kernel block path, the kitchen will automatically detects the kernel path and flashes it to the correct path during installation[/B]
[*]Support to update all binaries by the user
[*]Separate menu to work with kernel/recovery without existing any project
[*]Separate menu to work with file_systems converter without existing any project
[/LIST]
[B][SIZE="5"][COLOR="Blue"][B]User guide:[/B][/COLOR][/SIZE][/B]
[B][SIZE="3"][U]How to update to new version:[/U][/SIZE][/B]
[HIDE]Open [TOOLS] folder and remove everything except [projects] and [tmp] folder
Then back to the main path and delete [ASSAYYED.exe]...
And extract the new update to the main path[/HIDE]
[B][SIZE="3"][U]Usage:[/U][/SIZE][/B]
[HIDE]Download the kitchen from the link above then extract the (ASSAYYED_KITCHEN.7z)
you will get (TOOLS) folder and (ASSAYYED.exe) file.
After first run for the kitchen will create (PLACE, WORK, READY FOLDERS)
Now we can put unlimited count of roms and from different types (example):
10 tar file, 20 zip file, system.img with boot.img, system.sin with kernel.sin, system.yaffs2 with kernel
Then press command 1 in the kitchen and the kitchen will print all your roms with number and all what you need is to type the number for the rom you want (same as dsixda kitchen)[/HIDE]
[B][SIZE="3"][U]How to update binaries:[/U][/SIZE][/B]
[HIDE]Go to "TOOLS/txt_files/tools_versions.txt" and open it
you will find all binaries need to update with their versions & links
press on each link to check a specified binary if need to update or not
download the new version and replace it with original [/HIDE]
[B][SIZE="3"][U]How to add custom debloat/deknox lists:[/U][/SIZE][/B]
[HIDE]You could edit the original lists for the kitchen to add your items
to edit debloat open "TOOLS/txt_files/bloat.txt"
then add what you want to debloat like this:
if you want to remove folder or file just add its name without any paths
example (file): to remove "WORK/system/vendor/app/nfc.apk" just add "nfc.apk"
example (folder): to remove "WORK/system/etc/sound/headset" just add "headset"
and to edit the knox menu do the same steps for "TOOLS/txt_files/knox.txt"
And to add your custom debloat menu add your file in "TOOLS/txt_files"
and name it as you want without spaces and make extension ".txt"[/HIDE]
[B][SIZE="5"][COLOR="Blue"][B]Download:[/B][/COLOR][/B][/SIZE] [SIZE="4"][url]https://mega.nz/#!fAIkBZKQ!aS-9yNL9GKgVzgJd9C5DWJtjD_fNM6bHTiz-1KnsydA[/url][/SIZE]
[B][SIZE="5"][COLOR="Blue"][B]Releases and changelog:[/B][/COLOR][/SIZE][/B]
[B][SIZE="3"][U]VERSION 1.82 STABLE:[/U][/SIZE][/B]
[LIST]
[*]Fixed bootloop after deodex for Nougat
[/LIST]
[B][SIZE="3"][U]OLD VERSIONS:[/U][/SIZE][/B]
[HIDE][B][SIZE="3"][U]VERSION 1.81 STABLE:[/U][/SIZE][/B]
[LIST]
[*]Improved remove "META-INF" contents for 7 ROMs during deodex process
[*]Updated NotePad++ To version 7.2.2
[*]Updated SuperSU to version 2.78 SR5
[/LIST]
[B][SIZE="3"][U]VERSION 1.78 STABLE:[/U][/SIZE][/B]
[LIST]
[*]Fixed sign apk files
[*]Added new [signapk.jar] binary
[*]Updated SuperSU to version 2.78 SR4
[*]Updated NotePad++ to version 7.2
[/LIST]
[B][SIZE="3"][U]VERSION 1.74 STABLE:[/U][/SIZE][/B]
[LIST]
[*]Fixed deodex old lollipop ROMs
[/LIST]
[B][SIZE="3"][U]VERSION 1.73 STABLE:[/U][/SIZE][/B]
[LIST]
[*]Updated kernel init.d support to [url]http://.xda-.com/showpost.php?p=69427878&postcount=595[/url]
[/LIST]
[B][SIZE="3"][U]VERSION 1.72 STABLE:[/U][/SIZE][/B]
[LIST]
[*]Added support for [ftf] files in zip file
[*]Fixed add zip to rom installler
[/LIST]
[B][SIZE="3"][U]VERSION 1.70 STABLE:[/U][/SIZE][/B]
[LIST]
[*]Re-wrote all the kitchen codes completely
[*]Optimized deodex codes and fixed all bugs like: [RAM space, bootloop, and limited storage]
[*]Added support for multi tar files in zip file
[*]Added Support to add custom init.d tweaks
[*]Updated [apktool] to: 2.2.1
[*]Updated [smali/baksmali] to: 2.2b4
[*]Updated [7zip] to: 16.04
[*]Updated [mksquashfs] to: 1.8
[*]Updated [ busybox] to: 1.25.1
[*]Updated [notepad++] to: 7.1
[*]Updated [SuperSU] to: 2.78 SR1
[*]Updated info in [tools_version.txt]
[/LIST]
[B][SIZE="3"][U]VERSION 1.58 STABLE:[/U][/SIZE][/B]
[LIST]
[*]Updated [oat2dex] to latest release (including baksmali/smali 2.2b3)
[*]Updated deodex codes and improved deodex N speed significantly (using [oat2dex] instead of smali/baksmali)
[/LIST]
[B][SIZE="3"][U]VERSION 1.56 STABLE:[/U][/SIZE][/B]
[LIST]
[*]Restored the original [rimg2sdat]
[*]Re-writed all kitchen's codes completely with a lot of optimization
[/LIST]
[B][SIZE="3"][U]VERSION 1.54 STABLE:[/U][/SIZE][/B]
[LIST]
[*]Added fully support to deodex N
[*]Fixed color issue in aroma installer
[*]Updated [baksmali & smali] codes in apktool
[*]Updated [baksmali & smali & oat2dex] to latest version
[*]Added support to zipalign all [jar] files (maybe help with bootloop)
[*]Re-writed and optimized all deodex's process codes
[/LIST]
[B][SIZE="3"][U]VERSION 1.48 STABLE:[/U][/SIZE][/B]
[LIST]
[*]Fixed "apktool" bugs with compiling "jar" files
[*]Improved check for "file_contexts" file before extract it
[*]Improved "add-on" zip feature during the recovery
[/LIST]
[B][SIZE="3"][U]VERSION 1.45 STABLE:[/U][/SIZE][/B]
[LIST]
[*]Updated decode "file_contexts.bin" codes
[*]Updated fixing kernel header codes
[*]Update "flash_kernel.sh" script to support all new devices like: Google Nexus *
[*]Improved get symlinks from "updater-script" & "kernel_file_contexts" from kernel for build rom or installer
[*]Optimized all building roms codes
[*]Updated deodex codes and improved N support ([COLOR="Red"]NOT COMPLETELY[/COLOR])
[/LIST]
[B][SIZE="3"][U]VERSION 1.39 STABLE:[/U][/SIZE][/B]
[LIST]
[*]Added support to rom zip contents sparse "system.img" like: Nexus ROMs
[*]Added support to "cache.img" included in the same ROMs
[*]Fixed bugs happened during unpack the kernel in third method
[*]Added support to detect the kernel header if not standard and fix it (also from Nexus ROMs)
[/LIST]
[B][SIZE="3"][U]VERSION 1.35 STABLE:[/U][/SIZE][/B]
[LIST]
[*]Updated Building codes to optimize get file_contexts
[*]Added 3 oat2dex file (0.83, 0.86, 0.87) to fix all deodex errors
[*]Updated odin to version 3.12.3
[*]Updated build rom for "dat" method
[*]Added supprot for "file_contexts.bin" for N roms
[*]Updated random contexts list for new versions
[*]Added "baksmali & smali" as a option to deodex if all oat2dex failed to support N
[*]Updated tools_version.txt to improve update tools by user
[*]Updated busybox to 1.24.2
[*]Added support to add custom bootanimation to N
[*]Updated apktool to 2.2.0
[*]Updated checking tools needed
[*]Replaced closed source "rimg2sdat" to open source "img2sdat" from latest commit and ported from .py script to exe
[*]Updated "sdat2img" from latest commit and ported from .py script to exe
[*]Optimized getting rom name for "sdat" Building
[/LIST]
[B][SIZE="3"][U]VERSION 1.20 STABLE:[/U][/SIZE][/B]
[LIST]
[*]Fixed all file_system converter bugs
[*]Updated zipalign process & added counting as deodex
[*]Added support to push files to external sdcard on 6
[*]Added kushan deblaot list to the debloater (Thanks to: [user=5804776]@Kushan02[/user] for his list and this thread: [url]http://.xda-.com/galaxy-s4/i9505-develop/s4-touchwiz-lollipop-rom-debloater-t3047634[/url])
[/LIST]
[B][SIZE="3"][U]VERSION 1.16 STABLE:[/U][/SIZE][/B]
[LIST]
[*]Improved the speed of checking project information significantly
[*]Added support for all [bootanimation*.zip] files (bootanimation-encrypt.....)
[/LIST]
[B][SIZE="3"][U]VERSION 1.14 STABLE:[/U][/SIZE][/B]
[LIST]
[*]Updated restore symlinks lines in updater-script during restore bloatware
[*]Fixed debloat status if the rom already debloated
[*]Removed [du.exe] binary
[*]Improved counting files during deodex for HTC roms
[/LIST]
[B][SIZE="3"][U]VERSION 1.10 STABLE:[/U][/SIZE][/B]
[LIST]
[*]Updated kill adb server for whole adb commands
[*]Updated update-binary and updated aroma binary and restored the progress bar moving with extracted files (Thanks to: [user=2605798]@nkk71[/user])
[/LIST]
[B][SIZE="3"][U]VERSION 1.08 STABLE:[/U][/SIZE][/B] (Thanks to: [user=6089271]@mafsi[/user])
[LIST]
[*]Added detect if sepolicy already patched before root
[*]Added support to detect sizes on old windows version
[*]Added support to remove symlinks commands for debloated/deknoxed files
[*]Added adb kill-server after each adb process
[/LIST]
[B][SIZE="3"][U]VERSION 1.04 STABLE:[/U][/SIZE][/B]
[LIST]
[*]Updated detecting system folder size
[*]Created new order for the progress bar in aroma installer
[*]Updated supersu to 2.78
[*]Removed oem.sin support (adding support for it is a mistake)
[/LIST]
[B][SIZE="3"][U]VERSION 1.00 STABLE:[/U][/SIZE][/B]
[LIST]
[*]Updated [update-binary] to latest support the block_image_update to avoid error 3 in twrp recovery that happened because of huge zip size more than 2G (fixing in minzip function allow up to 4G especially for new sony big roms like: Z5P)
[*]Changed all set_perm for small script to set_metdata (supported by two binaries)
[*]Improved gawk (print) command to detect contexts that placed in third column by detecting last column automatically (fixed detect some xperia roms for "-d" second column like "odex.*fs")
[*]Removed protecting exploring using 7z for ASSAYYED.exe (faster during extract the source and starting the kitchen)
[*]Changed some print commands strings
[*]Added support to oem.sin from ftf or alone with system.sin
[*]Improved updater-script codes to avoid duplicate during mounting and umounting commands (fixed error message like: invalid arguments. Or: device or resource busy)
[*]Added code to use edify detect "/proc/mounts" partitions before mount
[*]Use old update-binary that supports set_perm and set_metadata to use on old versions to avoid error 6 during installation because of removing set_perm from the new update-binary
[*]Now the installer will support sizes for devices that don't released yet like S8
[*]Improved minzip function to work with aroma even if the permissions is not set_perm with protect from error message with un-dead feature
[*]Replaced update-binary-installer in aroma too (this will support aroma in flashfire)
[*]Optimized stability codes to avoid closing the kitchen suddenly (the stable version)
[/LIST]
[B][SIZE="3"][U]VERSION 6.3 ALPHA:[/U][/SIZE][/B]
[LIST]
[*]Replaced all sign rom codes and binaries with dsixda kitchen to avoid new testing and errors
[*]Changed project name entry
[*]Improved build exe file & removed UPX compress for better security (maybe help with trojan detect)
[/LIST]
[B][SIZE="3"][U]VERSION 6.2 ALPHA:[/U][/SIZE][/B]
[LIST]
[*]Fixed patch sepolicy in recovery
[*]Fixed deleted create project command
[*]Fixed detect supolicy in recovery
[*]Fixed detect supolicy in system-less mode
[*]Fixed continue root in system mode if patch sepolicy failed
[*]Fixed remove unpacked kernel if patch sepolicy failed
[/LIST]
[B][SIZE="3"][U]VERSION 6.1 ALPHA:[/U][/SIZE][/B]
[LIST]
[*]Optimized all codes
[*]Added support to add project name for better work
[*]Improved tools names and updates
[*]Fixed some prints commands
[*]Changed auto debloat command string
[*]Rebuild exe file with better assembling
[/LIST]
[B][SIZE="3"][U]VERSION 6.0 ALPHA:[/U][/SIZE][/B]
[LIST]
[*]Updated signapk.jar binary
[*][B]Added support to sign any zip file whatever its size was big and whatever the RAM is small[/B]
[*]Updated style and design
[*]Improved detect contexts from file_contexts completely
[*]Changed color from blue to white
[*]Added full support for sony [ftf, sin, elf, ext4] with instruction to use flashtool
[*]Added support for [boot.sin, kernel.sin, boot.img, kernel.elf] in PLACE folder with pick one for the rom
[*]Improved security and powerful for exe file
[*]Updated deodex codes
[*]Added full explain to "TOOLS/tmp/deodex_log.txt" after the end of the process
[*]Added remove dm-verity
[*]Added remove/add force-encrypt
[*]Added separate kernel/recovery menu
[*]Fixed working with kernel.sin codes
[*]Improved detect fstab
[*]Added custom bootanimation status
[*]Added option to fix KERNEL/RECOVERY IS NOT SEANDROID ENFORCING
[*]Added separate images file_systems convert menu
[*]Added sign zip after build it
[*]Added su.d support with status
[*]Added custom debloat menu support
[*]Fixed efs backup script
[*]Added support for all zip in cache.img like "sec_omc.zip"
[*]Added ability to update binaries by user
[*]Improved installer to work with all devices and make it compatible with all partitions types (ext4, F2FS) and support dual boot
[*]Added fully support for FlashFire
[*]Improve deodex process and added counting apps during it
[*]Replace NO ODEX FOUND with green NOT NEEDING
[*]Installer info always show
[*]Removed installer maker and permissions type from installer info
[*]Added patch sepolicy (separate in kernel menu or before rooting)
[*]Added adding custom zip installation to updater-script to install it with the rom like (busybox, xposed)
[*]Added convert elf to img [COLOR="Red"]---NOT TESTED YET---[/COLOR]
[*]Added sony boot.sin detect support
[*]Fixed detect ASSAYYED.exe as virus
[/LIST]
[B][SIZE="3"][U]VERSION 5.3 BETA:[/U][/SIZE][/B]
[LIST]
[*]Fixed deodex process on architecture (32) in the roms that have 64 and 32 architectures
[/LIST]
[B][SIZE="3"][U]VERSION 5.2 BETA:[/U][/SIZE][/B]
[LIST]
[*]Now automatically zipalign apks after deodex finished
[*]Fixed some apks like (SamsungIME) FC after deodex
[*]Updated zipalign binary to latest from SDK-build-tools v24.0.1
[*][B]Now the apks get very high speed after zipalign using (Align stored shared object files in the apk)[/B]
[/LIST]
[B][SIZE="3"][U]VERSION 5.1 BETA:[/U][/SIZE][/B]
[LIST]
[*]Updated deodex to remove oat folders completely
[*]Fixed lost .so files from app, priv-app folders after deodex
[*]Updated deodex process to integrate all classes*.dex into apks (more than 3 -- unlimited)
[*]Fixed bootloop on some roms after deodex because of lost apks's symlinks after the process
[/LIST]
[B][SIZE="3"][U]VERSION 5 BETA:[/U][/SIZE][/B]
[LIST]
[*]Updated deodex process and fixed deodex 64 and 32 bit
[*]Fixed pull roms from recovery and mount /system for read, write
[*][B]Fixed WIFI disabled on some devices after flashing[/B]
[*]Optimized builds roms codes
[*]Improved extract file_contexts from kernel
[*]Fixed detect files contexts from file_contexts
[/LIST]
[B][SIZE="3"][U]VERSION 4 BETA:[/U][/SIZE][/B]
[LIST]
[*]Optimized codes
[*]Fixed pull symlinks from all locations in addition to use "su" if the device rooted
[*]Updated detect root in device in system-less & system modes
[*]Updated detect system size from device
[*]Added kitchen version in the title
[*]Optimized exe file & reduced size
[*]Added administrator manifest to exe file for better work
[*]Added support to work in all windows versions up to windows 10 64x bit
[*]Updated detecting kernel during pull rom from device
[*]Improved pull rom for protected files as root permisison because of [su.img] (root in system-less mode)
[*]Updated deodoex process to remove [oat] folders from the /system/app & /system/priv-app after the process
[*]Added root installer for roms that have version 6.x.x+ to install root in system-less mode
instead of add it directly in system especially in tar roms to avoid bootloop
[*]Note: tar build method doesn't include root installer because odin doesn't support zip files
and instead of that you can create tar file contents Self-auto_root
[/LIST]
[B][SIZE="3"][U]VERSION 3 BETA:[/U][/SIZE][/B]
[LIST]
[*]Replaced image mount with extract directly using 7zip so now supports size up to 160000000000GB and supports all windows version up to 10
[*]Fixed build rom in image type [dat & raw] for sizes bigger than 5GB
[*]Updated & fixed deodex process & added log for its
[*]Fixed rename system.img to ext4 in build 28bit method
[*]Added apktool for all versions supports edit jar & apk & dex files
[*]Added adbd for run adb in root mode directly
[*]Added option to add custom bootanimation
[*]Optimized codes & improved root permissions codes
[*]Improved & fixed info to build 28 and 32 bit system.img for odin flash
[*]Removed data/cfw files feature [useless]
[*]Added option to remove csc apks in debloat command [samsung]
[*]Fixed remove some /bin/** files after deodex [Thanks to [B]jackq[/B]]
[*]Now will add root installer for roms 6.x.x+
[*]Fixed pull rom from device rooted in system-less method
[*]Updated debloat & deknox menus
[*]Improved work with motorola roms
[*]Updated root to v2.76 beta
[*]Fixed bootloop after flash image in recovery or odin
[*]Fixed memory leak during deodex process on some WINDOWS
[*]Now the kitchen extracts [file_contexts] automatically from [kernel.elf]
[/LIST]
[B][SIZE="3"][U]VERSION 2 BETA:[/U][/SIZE][/B]
[LIST]
[*]Fixed lost cyg****.dll files
[*]Fixed remove extra header for motorola stock roms
[*]Added more symlinks [for ROM doesn't content local symlinks] to support motorola roms
[/LIST]
[B][SIZE="3"][U]VERSION 1 BETA:[/U][/SIZE][/B]
[LIST]
[*]Initial release
[/LIST][/HIDE]
[B][SIZE="5"][COLOR="Blue"][B]Credits:[/B][/COLOR][/SIZE][/B]
[B][URL="https://www.cygwin.com/"]Cygwin[/URL]: For linux tools
[URL="https://-review.googlesource.com/"]AOSP[/URL]: For image tools [simg2img, make_ext4fs, adb......etc]
[URL="http://www.miui.com/space-uid-29574096.html"]cofface[/URL]: For bootimg [kernel extractor]
[URL="http://4pda.ru//index.php?showtopic=218799"]And_pda[/URL]: For imgextractor.exe
[URL="http://www.codeproject.com/Articles/17033/Add-Colors-to-Batch-Files"]thomas_polaert[/URL]: For cecho command
[URL="http://www.7-zip.org/"]Igor Pavlov[/URL]: For 7zip binary
[user=4723245]@Jertlok[/user]: For this thread [url]http://.xda-.com/note-4/-apps/flashable-zip--m-bootanimation-t3194291[/url]
[user=6262977]@howellzhu[/user]: For rimg2sdat
[user=5161352]@JustArchi[/user]: For init.d support in the rom
[user=3924617]@iBotPeaches[/user]: For apktool
[user=1299419]@JesusFreke[/user]: For smali & Baksmali
[user=6258761]@_riddle[/user]: For oat2dex
[user=402300]@amarullz[/user]: For Aroma installer
[user=2117836]@michfood[/user]: For kernel tools
[user=4544860]@osm0sis[/user]: For kernel tools and Busybox
[user=631273]@Chainfire[/user]: For SuperSU
[user=5132229]@xpirt[/user]: For sdat2img
[user=2976903]@A.S._id[/user]: For this thread [URL="http://.xda-.com/showthread.php?t=2600364"]http://.xda-.com/showthread.php?t=2600364[/URL][/B]
[B][SIZE="5"][COLOR="Blue"][B][CENTER]I hope this program works fine and remember to make a backup for your rom if you decide to use it[/CENTER][/B][/COLOR][/SIZE][/B]
Error
Hi! I've got error "cygcc_s-1.dll is missing…" during the project creation. How to deal with it?
dFrem said:
Hi! I've got error "cygcc_s-1.dll is missing…" during the project creation. How to deal with it?
Click to expand...
Click to collapse
SORRY FOR THAT
Download this attachment and extract it
then you will get 4 *.dll files put them in "TOOLS/bin"
folder of the kitchen directory
hope this help
I'm gonna test it.
This looks interesting. I'll have to try it out.
Hello
ca has prometeur area . is it possible to have a link other than 4shared ? please
thank you
pendor24 said:
Hello
ca has prometeur area . is it possible to have a link other than 4shared ? please
thank you
Click to expand...
Click to collapse
I have created a new link to mediafire
Download here
thank you
you are the best .
I get "status 7" error when flashing
I can't even flash ext4 with odin.
xdecoy said:
I get "status 7" error when flashing
I can't even flash ext4 with odin.
Click to expand...
Click to collapse
Working with odin is not easy you need to know
what the extension of tar file that samsung named it "system.img.ext4" or "system.img"
and the hardest part is to know what the device sparse header 28 or 32 bit
if you want to know what the extension it is easy download any stock
tar rom for your device and look for the extension of the system file is "ext4" or "img" and select in the kitchen.
and for sparse header this need to be a developer to deal with it, however create both files 28 and 32 and test them.
the "status 7" error is not from the kitchen try to update or change you recovery.
if you want more help tell me what your device model and upload the updater-script please
Error!
Hey, Just downloaded to give this a try. I used a stock tar Rom for Sprint Note 4 and got the following error:
It unpacked it but failed to mount! Pic attached.
aaron74 said:
Hey, Just downloaded to give this a try. I used a stock tar Rom for Sprint Note 4 and got the following error:
It unpacked it but failed to mount! Pic attached.
Click to expand...
Click to collapse
This problem from Ext2fsd mount windows program
It is work on windows xp/7/8/8.1 but doesn't work on windows 10 i will try to fix this problem in the next few weeks
If you want to extract the system.img extract it from tar file
Using 7zip and move the extracted system.img to work folder
And copy "tools/bin/imgextractor.exe" to work folder
Then drag system.img to the exe file and wait to finish and then rename the last folder to "system" and delete all files from work folder except system and boot.img then run the kitchen
Thank you for feedback for this windows problem i was waiting for
ASSAYYED said:
This problem from Ext2fsd mount windows program
It is work on windows xp/7/8/8.1 but doesn't work on windows 10 i will try to fix this problem in the next few weeks
If you want to extract the system.img extract it from tar file
Using 7zip and move the extracted system.img to work folder
And copy "tools/bin/imgextractor.exe" to work folder
Then drag system.img to the exe file and wait to finish and then rename the last folder to "system" and delete all files from work folder except system and boot.img then run the kitchen
Thank you for feedback for this windows problem i was waiting for
Click to expand...
Click to collapse
OK, I was just testing it out.
Maybe you can look into this link below from thier website and implement it into your project!
http://www.ext2fsd.com/?p=182
I dont know if it works.
Or put a script to detect if host pc is running windows 10 and default to 7zip extract!
Hope that helps! :fingers-crossed:
aaron74 said:
OK, I was just testing it out.
Maybe you can look into this link below from thier website and implement it into your project!
http://www.ext2fsd.com/?p=182
I dont know if it works.
Or put a script to detect if host pc is running windows 10 and default to 7zip extract!
Hope that helps! :fingers-crossed:
Click to expand...
Click to collapse
Yes! i know this solution and i will fix it but now i have windows 7 on my PC and and these days
i'm very busy to do this big work [formatting PC and installing windows 10........etc]
but after one or two weeks i will fix it don't worry, fixing problems is my hoppy
and about extract directly using imgextractor.exe this method was using in very old version of my kitchen before uploading to xda
but this method doesn't support new roms that have size more than 4GB like s7 rom so i replaced it with mounting.
and the fix will come soon
I try a compilation from a stock rom note 4 mm 910F on Windows 7 no erreure like aaron 74. I have to bugs in the deodex share the ca blow deodex not an idea ?
http://image.noelshack.com/fichiers/2016/27/1468079845-20160709-175425.jpg
http://image.noelshack.com/fichiers/2016/27/1468080708-20160709-175303.jpg
pendor24 said:
I try a compilation from a stock rom note 4 mm 910F on Windows 7 no erreure like aaron 74. I have to bugs in the deodex share the ca blow deodex not an idea ?
http://image.noelshack.com/fichiers/2016/27/1468079845-20160709-175425.jpg
http://image.noelshack.com/fichiers/2016/27/1468080708-20160709-175303.jpg
Click to expand...
Click to collapse
There are two reasons for
1- the file services.jar needs very huge ram from your pc
Maybe need more free ram my pc has 4gb ram and deodex
Without errors
2- the oat2dex file used to deodex need to update i will test
This rom you are working on with my pc
Thanks for feedback
ASSAYYED said:
Yes! i know this solution and i will fix it but now i have windows 7 on my PC and and these days
i'm very busy to do this big work [formatting PC and installing windows 10........etc]
but after one or two weeks i will fix it don't worry, fixing problems is my hoppy
Click to expand...
Click to collapse
No problem. I know its a lot of work. I didn't mean anything by it. Was just being helpful. Thank you for your work!
yet my pc has 16gb of ram. I tested on the Roma note 4 910F AP : XXS1DPF3
CP: XXU1DPD1
pendor24 said:
yet my pc has 16gb of ram. I tested on the Roma note 4 910F AP : XXS1DPF3
CP: XXU1DPD1
Click to expand...
Click to collapse
Ok i will check oat2dex scripts codes and fixing it
thank you very much
Related
Another port of my custom recovery.
For the aroma file manager option to work you have to flash the zip at least once as the zip file will put aroma in the correct place on your sdcard.
Download ------> cwm6032touch_v15.0.2_m7.zip
Thanks to :
gweedo767 (for creating the original touch recovery)
koush (for creating CWM)
PhilZ (for his amazing improvements and help with applying universal touch code) BIG THANKS!
htc-msm8960 for their device tree
PREVIOUS VERSIONS:
Code:
v1:
[CODE]initial release
v2:
Code:
- updated to latest version of clockworkmod
- add reboot download option
- add reboot recovery option
- add power off option
- change font size
- add various internal/external sdcard options from cwm 5.5.0.4 touch recovery
- change order of internal/external sdcard so internal comes first on backup/restore/install
v3:
Code:
- add support for phones that sdcard mounts as external_sd
- fix the line below the menu to actually be below the menu
- clean up the "andy the android" picture. (if you make a backup you will see that the picture in the background has been poorly edited. there are bits of black spots around him)
- JellyBean Background
v4:
Code:
- fixed missing slash that was not allowing installs from external sdcard
v5:
Code:
- update to latest version of CWM 6.0.0.8
v6:
Code:
- updated to latest version of CWM 6.0.0.9
- added ability to delete nandroids from recovery (in backup and restore menu)
- changed order of internal/external so external comes first
- fix timestamp creation on backups
v7:
Code:
- updated to latest version of CWM 6.0.1.0
- fixed bug that would not allow backup of /system
v8:
Code:
- update to latest version of CWM 6.0.1.1
- allow customization of backup format (dedupe/tar)
- use minizip tool instead of e2fsck, etc.
- more....
v9:
Code:
- update to latest version CWM 6.0.1.2
- fixed bug where backing up to external wouldnt backup /emmc/.android_secure
- ADDED DUAL LUNFILE SUPPORT! (thanks to topprospect for this!)
-- what this does is when you mount USB storage you
will see both of your sdcards mount at the same time
- various /emmc fixes (recovery now looks for all clockworkmod "." files in /emmc instead of /sdcard)
- this is useful for people who dont use an external sdcard at all
v10:
Code:
- grabbed latest commits to official CWM 6
- added new extras menu (look in 2nd post for info)
- some other stuff i dont remember
v11:
Code:
- fixed hide nandroid progress bug (it now works)
- added sk8's fix permissions option (logging is disabled so it runs faster and it also clears stale data directories)
- fixed bug where normal fix permissions wouldnt create a log to correct location
- cleaned up some syntax
v12:
Code:
- added darkside wipe/super wipe built in
- added aroma file manager built in
- added ability to backup/restore the /efs partition
- cleaned up oneconfirm/hidenandroidprogess features to be one menu item
- more......
v12.5:
Code:
- fixed bug where darkside cache scripts wouldnt work
- added option to create a custom zip (read 2nd post)
v13:
Code:
- report log gets copied to /emmc instead of /sdcard
- add support for roms without busybox (stock roms) to create a custom rom zip
- add support for openrecoveryscript (read [URL="http://forum.xda-developers.com/showpost.php?p=31093552&postcount=344"]THIS[/URL])
- add support to choose a custom created openrecoveryscript
- use goo-manager to flash roms and create openrecoveryscripts
- now detects where android_secure is automatically
- fix ors-mount.sh to work even if 'sdcard' is in the path
- misc code cleanups.....
v13.1
Code:
- bug fixes
- android_secure fixes
v13.2
Code:
- that pesky android_secure - bugfixes for restoring android_secure
v13.3
Code:
- updated to latest 6.0.1.4
- some bugfixes
- added option to select where android_secure lives (hopefully this is the last time. i promise)
v13.4:
Code:
- updated aroma file manager to latest version
v13.5:
Code:
- add initial support for whole-device encryption (thanks topprospect)
v14:
Code:
- updated to latest CWM 6.0.1.5
- fixed some mtdutils issues
- added a bootanimation changer
v14.1:
Code:
- not released
v14.2:
Code:
- added bootanimation change selection from external sdcard
- added newest aroma filemanager w/ console support (you can use terminal in recovery)
- updated to latest changes of official CWM
- added support for Android 4.2
- zip file now installs updater.sh to your internal sdcard
- updated updater.sh to fix typo
v14.2.1:
Code:
- openrecoveryscript automatically runs if script is found in /cache/recovery/
- this is good for using my updater.sh or goomanager
v14.3
Code:
- skipping this number to keep in line with my other devices
v14.3.1
Code:
- lots and lots of under the hood improvements
- re-wrote OpenRecoveryScript and efs backup/restore code
- these work alot better now (thanks so much to PhilZ for his amazing help)
- add option to backup/restore boot.img from sdcard
- now using latest stable kernel
- completely re-wrote the touch code for some improvements
- now to select you tap anywhere on the screen
- fixed some typos
- made my source code universally compatible with all phones using ICS or greater
- compiling in jellybean base recovery code now
Code:
v14.4
- fixed soft keys (virtual keys on bottom) (credit to PhilZ for this)
- reverted back to swipe to select
- tweaked some features in the extras menu
Code:
v14.4.1
- messed up on the mount points so i fixed them now
- added some buffer to fix ability to accidentally select wrong item
Code:
v14.4.5
- skipped some versions because they were made for other phones
- re-wrote the create custom backup feature to be universal now with all phones/roms (thanks to PhilZ for the help)
- added new settings menu
- add ability to change timezone
- added /preload support [B](must go and enable it in misc nandroid settings)[/B]
- add rom name to nandroid names
- more i just cant remember now....
Code:
v14.4.6
- added exFAT support
- some under the hood optimizations
Code:
v14.4.7
- added extras>>misc nandroid settings>>disable assert check
- removed black space in error icons
- some under the hood optimizations
- added updater.sh script
Code:
v15.0.0
- updated to latest cwm source
- added HTC One into the group
Code:
v15.0.1
- fix zip file
[/CODE]
Current Version:
v15.0.2
- update to latest cwm official changes
Click to expand...
Click to collapse
How touch works:
UP - swipe finger up on screen
DOWN - swipe finger down on screen
SELECT - swipe finger from left to right
BACK - swipe from right to left
SOURCE: https://github.com/sk8erwitskil/touch_recovery_cm10.1
This is what the new dedupe format does. This is a direct quote from the original creator of clockworkmod:
Code:
ClockworkMod Recovery now deduplicates files between builds. This results in way smaller backups.
Don't delete /sdcard(or emmc)/clockworkmod/blobs
Overview
I've gotten a few questions about how this works, so I figured I'd make a post on it.
Basically, here's what happens:
The files being backed up are hashed (sha256, not that it matters). Then it checks for a file with the name of the hash in
/sdcard/clockworkmod/blobs
So, if the hash of the file was c5273884b90d490134e7737b29a65405cea0f7bb786ca82c6337ceb24de6f5ed, it looks for /sdcard/clockworkmod/blobs/c5273884b90d490134e7737b29a65405cea0f7bb786ca82c6337ceb24de6f5ed
If the hash file is found, it continues on to the next file. Otherwise, it copies the file to the blobs directory with the file name being the hash.
ROMs and user data, for the most part, do not change too much between builds and backups. So, your APKs, system files, etc, are generally only stored once. This saves a ton of space. Especially between incremental backups.
Some of you may be thinking "well, how do I delete a backup?".
First, never delete the blobs directory. This would actually delete all your backups by rendering them unusable.
Simply delete the usual backup directory, and the next time you run a backup, all the unused hash files will be automatically delete (a process known as garbage collection). The recovery will show "Freeing space..." while this is happening.
Sk8! Glad to see you deving here! You did such a great job with the skyrocket... Are you getting this phone/do you have it?
Sent from my SGH-I927 using xda premium
spitfire2425 said:
Sk8! Glad to see you deving here! You did such a great job with the skyrocket... Are you getting this phone/do you have it?
Sent from my SGH-I927 using xda premium
Click to expand...
Click to collapse
yah my work bought it for me so ive been doing a little dev work on the side for it
sk8erwitskil said:
yah my work bought it for me so ive been doing a little dev work on the side for it
Click to expand...
Click to collapse
sk888888888888888888888888888888888888888888 let's do some work on the beast of an htc one I've got the Canadian one
Awesome man. Just the more reason to get this phone. Just 3 more weeks....
Sent from my SGH-I927 using xda premium
Glad to see you here sk8, great work!
heh this thread is like a little reunion.
this was the easiest phone to port my recovery too. only think i need to fix is the offset for the battery display in the right top corner.
sk8erwitskil said:
heh this thread is like a little reunion.
this was the easiest phone to port my recovery too. only think i need to fix is the offset for the battery display in the right top corner.
Click to expand...
Click to collapse
Yeah. I noticed that. No biggie. Aroma seems to work great on this recovery. The display actually looks correct.
Now to get my stock rooted backup converted to CWM format as a failsafe in case I have to go back to stock due to the lack of AT&T RUU images.
tiny4579 said:
Yeah. I noticed that. No biggie. Aroma seems to work great on this recovery. The display actually looks correct.
Now to get my stock rooted backup converted to CWM format as a failsafe in case I have to go back to stock due to the lack of AT&T RUU images.
Click to expand...
Click to collapse
i dont think there is a way to convert from twrp to cwm atm. if you need that backup you can just make a backup of your current rom on cwm, then flash back to twrp, restore that stock rom, flash cwm then backup the stock rom, then restore your custom rom.
Been waiting for an update for this much underrated recovery. I like the gestures in this one over the click on item to select it.
literally working on it as i type this
There's a pesky bug in my code. New release is going to be delayed a day
Sent from my HTC One using xda app-developers app
Dude, this recovery is insane! You might have just swayed me from twrp.
Great job!
any update for this sk8?
Important notes for Developers / Chefs !!!
This ROM is NOT based on any other custom ROM. My work contains many original ideas and innovations that I introduced as the first in the ROM development (see "Changelist" in post #2). Of course, it does not mean that I do not need to thank anyone - there are a lot of people who helped / inspired me anyhow (see "Credits").
I will risk the statement that at this moment my "DevBase" is the most tuned and nuanced custom ROM available at XDA Forum
I agree to use any part of my work to create other custom ROMs, but it would be great if you add me to the credits
Hello
I have decided to create a pure base, which can be a pattern for ROM Chefs (not only for beginners) ROM is initially safe de-bloated (read below what does it exactly mean), but all features are present and works!
ROM can be installed by normal users as well. If you like a little de-bloated ROMs, clean, but with all working features - there is no better alternative I think
ROM contains my extended CSC package, which I called N910FAXX (this is a combination OXX, OXA + some additional). Final list of available CSC is as follows:
ATO, AUT, BAL, BTU, CYO, DBT, ETL, EUR, H3G, ILO, ITV, LUX, MEO, MET, NEE, ORX, PHE, PHN, ROM, SEE, SIO, VGR, VIA, TPD, TPH, XEF, XEH, XEO (underlined - VoLTE support)
NEW !!! I present you new, unique option: "Keep current CSC", so you can install my DevBase keeping your original CSC even if it is not listed above! Note that in such case this option has some limitations, so read carefully informations below.
How does it work? Normally, if your current CSC is listed above (contained in my DevBase), this option detects it and automatically applies during install. However, if the detected CSC is not contained in my DevBase, then my new script makes a copy of all known contents associated with CSC (except so-called "CSC bloatware" placed in /system/app & priv-app, e.g brand and/or country specific apps), then installer cleans /system partition as usual, then it flashes new ROM base and then it restores backed up CSC contents instead of my multi CSC pack. It seems to be easy, but was rather laborious - I have analyzed almost all multi CSC packs and most of single CSC packs available in the world (designed to work with N910FXX... base) to make this script as accurate as possible.
As you probably noticed - in such case your CSC pack will be as complete as it was before, thus if you are currently using any custom ROM - BEFORE the first installation of my DevBase I highly recommend you to flash the latest original stock ROM released for your country, then perform "wipe data" using stock recovery and then CHECK your CSC (chage it if necessary - more information below).
For further updates you do not need to repeat it every time. You can flash directly the next (newer) version of my DevBase with "Keep current CSC" option untouched in /options.prop - you can repeat such update procedure for a long time. As you probably noticed again - if your CSC is not contained in my DevBase, then your CSC pack will not be updated until you flash a newer original stock ROM for your country. But don't worry - CSC updates usually bring nothing (usually the only updated thing in CSC pack is the whitelist of LTE networks). I'm not trying to say "CSC updates are completely unnecessary". It's good idea to update it occasionally (especially if you noticed that major Android update for your country has been released). When you will decide to do it - just flash temporarily again the newest original stock ROM containing your CSC, and then you can return to my the newest DevBase (this time wipe data will not be necessary).
NOTE: Do not use so called "Superwipes" and/or additional /system "formats", otherwise "Keep current CSC" option may not work properly (e.g. if detected CSC is NOT included in my multi CSC package, then it will not be possible to keep detected CSC, as there is no CSC related content to backup / restore).
How can I check my current CSC?
Install Phone INFO app from Play Store and check your CSC. If you are using stock ROM and everything is ok with your CSC - all CSC fields in Phone Info app should display the same CSC, as below (otherwise, you probably forgot about wipe data when you were installing ROM with another CSC).
{
"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"
}
How can I change my current CSC?
Q: Recently I tested several ROMs, in result of it my CSC has changed. I would like to install your DevBase, but first I want to restore my country's original CSC. What should I do?
Case 1: Your country's original CSC is available in my DevBase
No special/additional steps are needed. Just install my DevBase with edited options.prop file placed on internal sdcard or extSdCard -> type CSC=[your_csc] instead of CSC=KCSC. Remember to perform "Wipe data" in the recovery before install. Note that sometimes additional reboot is required after completing pre-configuration steps to display your CSC correctly in Phone Info app).
Case 2: Your country's original CSC is not available in my DevBase. Your original ROM contains single CSC pack (ommiting parts with model name and incremental version - name of CSC package is same as product code = CSC)
Example:
Code:
Model: SM-N910F
Model name: GALAXY Note 4
Country: Montenegro
Version: Android 4.4.4
Changelist: 3311829
Build date: Mon, 17 Nov 2014 05:21:39 +0000
Product Code: [COLOR="Red"]TMT[/COLOR]
PDA: N910FXXU1ANK4
CSC: N910F[COLOR="red"]TMT[/COLOR]1ANK1
MODEM: N910FXXU1ANK4
In this case you need to flash your original ROM using PC Odin, then perform wipe data using stock recovery and then check your CSC in Phone Info app (note that sometimes additional reboot is required after completing pre-configuration steps to display your CSC correctly in Phone Info app).
Now you can install my DevBase - just leave "Keep current CSC" option untouched in /options.prop (it's good idea to perform "Wipe data" again from recovery to remove potential "garbage" from /data partition like e.g app data created by CSC bloatware and CSC bloatware updates).
Case 3: Your country's original CSC is not available in my DevBase. Your original ROM contains multi CSC pack (ommiting parts with model name and incremental version - name of CSC package differs from product code and usually begins with the letter "O")
Example:
Code:
There is no good example for SM-N910F at the date of writing this guide
There is no good example for SM-N910F at the date of writing this guide. The only multi CSC package not contained in my DevBase is Vodafone N910FVFG.... but it is BRANDED! Therefore, I recommend to change it to unbranded, from DevBase's supported list (steps same as Case 1). If you really want to know what should you do in such case (in theory) - please read related DevBase threads for Note 3 or S5
ALEXNDR.N910FXXU1DRF1:
1. Base:
- Odexed (original stock files) + stock kernel
- Multi CSC OXM (list of natively supported CSC as above) (*)
- Removed SecurityLogAgent.apk (annoying on rooted phones)
- Removed Rlc.apk (to avoid "OEM unlock issue")
- Rooted systemlessly (Magisk v16.7 or SuperSU 2.82 SR5) (*)
- All original features are present and works (except KNOX related apps)
- No visual changes (100% stock look)
2. CscFeature MOD (enabled some built-in, hidden features):
- Added shutter sound menu in Camera app
- Sending/receiving MMS without data on
- Show SMS/MMS sending time instead of receiving
- Added "Call/Message block" option in Settings
- Added "LTE Only" network mode (NOTE: voice calls may not work in this mode)
- 4G/3G network support in any CSC (master/slave SIM, applies to dual SIM variants)
- Call Recording (via "Record" button or "Auto record calls" option)
- Enabled "Recent App Protection" feature
3. Xposed framework & Xposed Installer app [optional] (*)
4. Virtual / physical Safe De-Bloat (more info below) (*)
What does it mean and why is it called "safe"?
- ONLY apps available in stores are removed from DevBase, so you can easy (re)install any of these app if you like
- ONLY pre-installed system apps are removed, DevBase installer never touch any updated app nor app installed manually from store
Thus, the following conclusions can be drawn:
1. If you install my DevBase directly over stock ROM without performing "Wipe data" - in most cases almost all these apps will remain untouched, because almost all apps have been updated already (stored on /data). But then you will be able to remove any useless app using the "Application manager", like any other app. Removed manually app will not appear again until you use my DevBase while updating.
2. If you perform "Wipe data" while installing my DevBase - then all apps listed below will be removed. If you would like to use any of these apps - just install it manually from appropriate store. Installed manually app will not be removed during the next DevBase update.
Removed apps list:
Chrome
Drive
Dropbox
Evernote
Facebook
FB Messenger
FB Pages Manager
Flipboard
Google+ / Photos
Hangouts
Instagram
PEN.UP
Play Books
Play Games
Play Movies
Play Music
Play Newsstand
Smart Remote
WhatsApp
(*) - these options can be controlled by editing options.prop file (you can find such file in ZIP's root directory). Just place modified options.prop file (use e.g. Notepad++ to edit) in the root directory of internal emulated scdard (/data/media/0) or extSdCard (recommended if you plan to format internal emulated sdcard) and then start the installation. More info below:
#
# DevBase by ALEXNDR (_alexndr @ XDA)
#
# Configuration file to allow customize the installation.
#
# File inside the ZIP installer is just for reference - please DO NOT modify it!
# If you want to change some options listed below - edit the copy of this file, then place
# modified options.prop file in the root directory of internal emulated scdard (/data/media/0)
# or in the root directory of extSdCard (recommended if you plan to format internal emulated
# sdcard) and then start the installation.
#
# TIP: You do not need to repeat this step every next update I will release. As long as your
# customized options.prop file is present in the (ext)SdCard - future DevBase installers will
# "read in your mind" that you want to install with such options again.
#
# NOTE: All below variables and values are case sensitive!
# Enable root access with the selected method. Allowed values:
# magisk - install Magisk & MagiskSU as root solution (default)
# supersu - install SuperSU as root solution, without Magisk
# noroot - do not root device
root=magisk
# Install Xposed framework matched to the ROM (there is also a possibility to detect Xposed profile
# automatically, but auto-detection will not work if user will perform wipe /system). Allowed values:
# auto - detect Xposed profile automatically
# true - force Xposed framework installation
# false - do not install Xposed framework
xposed=auto
# CSC Selection. Allowed values:
# KCSC - Keep current CSC, recommended in most cases (automatic selection or copy your current CSC contents).
# You can force the use of natively supported CSC by typing (use UPPERCASE!): ATO, AUT, BAL, BTU, CYO, DBT,
# ETL, EUR, H3G, ILO, ITV, LUX, MEO, MET, NEE, ORX, PHE, PHN, ROM, SEE, SIO, TPD, TPH, VGR, VIA, XEF, XEH, XEO
CSC=KCSC
# Custom CSC Features. Allowed value in each line: <Example_line>value</Example_line>
<CscFeature_Sip_EnableSymbolInSecondary>en_GB;en_US;az;ca;cs;da;de;et;es;eu;el;fr;gl;ka;hr;it;is;kk;lv;lt;hu;nb;nl;pl;pt;ru;ro;fi;sr;sk;sl;sv;tr;uk;ko;hy;bg;ar;fa;ur;zh_CN;</CscFeature_Sip_EnableSymbolInSecondary>
<CscFeature_Sip_ConfigOpBranding>SPR</CscFeature_Sip_ConfigOpBranding>
<CscFeature_Common_SupportWcdmaInSlave>true</CscFeature_Common_SupportWcdmaInSlave>
<CscFeature_VoiceCall_ConfigRecording>RecordingAllowed</CscFeature_VoiceCall_ConfigRecording>
<CscFeature_Setting_EnableMenuBlockCallMsg>true</CscFeature_Setting_EnableMenuBlockCallMsg>
<CscFeature_Setting_CustNetworkSelMenu4>LTEONLY</CscFeature_Setting_CustNetworkSelMenu4>
<CscFeature_Setting_SupportRealTimeNetworkSpeed>true</CscFeature_Setting_SupportRealTimeNetworkSpeed>
<CscFeature_SmartManager_DisableAntiMalware>true</CscFeature_SmartManager_DisableAntiMalware>
<CscFeature_SystemUI_SupportRecentAppProtection>true</CscFeature_SystemUI_SupportRecentAppProtection>
<CscFeature_Contact_EnableCallButtonInList>true</CscFeature_Contact_EnableCallButtonInList>
<CscFeature_Message_DisplaySmsTimeAs>server</CscFeature_Message_DisplaySmsTimeAs>
<CscFeature_Message_DisplayMmsTimeAs>server</CscFeature_Message_DisplayMmsTimeAs>
<CscFeature_Camera_ShutterSoundMenu>true</CscFeature_Camera_ShutterSoundMenu>
<CscFeature_Web_AddOptionToTerminate>true</CscFeature_Web_AddOptionToTerminate>
<CscFeature_Web_EnablePromptToExit>true</CscFeature_Web_EnablePromptToExit>
<CscFeature_RIL_ForceConnectMMS>true</CscFeature_RIL_ForceConnectMMS>
# Custom physical debloat list. Allowed value in each line: path to app's directory in /system.
# (NOTE: wildcards are allowed here)
/system/app/SecurityLogAgent
# Custom virtual debloat list. Allowed value in each line: exact app name with .apk extension.
# (NOTE: without app's path/directory, wildcards are NOT allowed here!)
Books.apk
Chrome.apk
Drive.apk
Dropbox_zero.apk
Evernote.apk
Facebook_latest.apk
FBAppManager.apk
FBInstaller.apk
FBInstagram_stub.apk
FBPagesManager_stub.apk
Flipboard.apk
Hangouts.apk
Music2.apk
Newsstand.apk
PENUP.apk
Photos.apk
PlayGames.apk
PlusOne.apk
SmartRemote_T.apk
Videos.apk
WhatsAppDownloader.apk
NEW !!! Starting from DevBase v3.0 there is a new customization method - you can change frequently switched root options just by renaming installer's ZIP file name (instead of editing options.prop file). Currently supported "strings" in the file name: "magisk", "supersu", "noroot", "rescue", "xposed", "CSC_xxxx.zip":
Case 1 (default) - install the ROM with Magisk & MagiskSU as root solution
(just flash ZIP file "as it is")
Case 2 - install the ROM with SuperSU as root solution, without Magisk
(place "supersu" string anywhere in the ZIP file name, e.g. "N910Fxxx_DevBase_v5.x_supersu.zip")
Case 3 - do not root device (NOTE: you will get not rooted ROM!)
(place "noroot" string anywhere in the ZIP file name, e.g. "N910Fxxx_DevBase_v5.x_noroot.zip")
In DevBase v4.5+ there is a "rescue" option, which may be especially helpful in case of encrypted device if you experienced bootloop caused by e.g. systemless mod/module/xposed stored on /data (without access to /data from TWRP). In case of bootloop just place "rescue" string anywhere in the ZIP file name, e.g. "N910Fxxx_DevBase_v5.x_rescue.zip" and then (re)install the ROM - should help in case of (probably) all possible bootloop reasons. In addition to the normal (re)installation of the ROM (thus restoring the original /system, kernel, modem, etc.) this option will also force "Core Only Mode" in Magisk and will move all SYSTEMLESS DevBase modifications to /data/devbase/system/.backup, before performing bind mounts, so original files will be used.
In DevBase v4.6+ there is a possibility to force CSC by renaming ZIP file name - this is the only case-sensitive variable which have to be put at the beginning of ZIP file name and must be folloed by "_" (due to the fact that there is a high risk that ZIP file name may contain CSC code accidentally). Example (to force CSC DBT): "DBT_N910FXXU1xxxx_DevBase.zip"
In DevBase ROM v5.6+ there is "xposed" option which allows you to force Xposed framework installation. It is NOT forced by default - you need to force it manually while installing ROM with Xposed first time, renaming ZIP's file name to e.g. "N910Fxxx_DevBase_v5.x_xposed.zip". Next ROM's updates will detect and apply Xposed profile automatically, unless you wipe /system - then auto detection is not possible.
Installation:
CWM / TWRP recovery (KNOX 0x1) - open file using "Install (Zip)" option and confirm operation. If you want to perform "clean install' - perform "wipe data/factory reset" BEFORE flashing Zip! I highly recommend you to update bootloader/modem also to the newest versions available in post #3, to avoid potential bugs/issues.
Wipe data is NOT required if you are coming from stock ROM or a previous version of my DevBase (if you leave "Keep current CSC" option untouched in /options.prop or if you choose same CSC as you are currently using). In other cases - wipe data is highly recommended!
I do not recommend using any additional superwipes or formats before install my DevBase (my installer cleans your system well enough!).
Credits:
@Chainfire for systemless SuperSU and a lot of inspiration
@topjohnwu for Magisk, Xposed, another inspiration
@rovo89 & @wanam for Xposed framework & Xposed Installer app
@amarullz for Aroma Installer used in older DevBase versions
@svadev & @_riddle for deodexed tools/binaries used in older DevBase versions
Hit Thanks button if you like my work. If you really appreciate my work - feel free to buy me a beer
DOWNLOADS
Download ROM
>> N910FXXU1DRF1_DevBase_v5.9.zip << (Android 6.0.1, updated Aug-11-2018, more info in post #3455)
>> Recent ROM versions for SM-N910F <<
Note:
Check MD5 sum BEFORE flash (useful TOOL), because flashing damaged or incomplete ZIP files could (soft) brick your phone! Correct MD5 sum is shown on the AndroidFileHost website while downloading.
Changelog
v5.9 (starting from N910FXXU1DRF1 DevBase):
- Changed device detection method to bootloader's prefix (instead of ro.product.*)
- Improved support for applying custom mods automatically at each ROM's install/update, introduced in v5.6 (added support for etc, fonts, media & usr directories in {storage}/devbase/system)
- Added support for custom {storage}/devbase/post-installation.sh script
v5.8 (starting from N910FXXU1DRD1 DevBase):
- Improved unzip_flash function in the installer to detect properly more flashing errors (e.g. EXT4 partition mismatch)
- Changed /odm flashing method to file based due to potential /odm partition mismatch (applies to carrier branded treble devices)
- Minor optimizations/improvements in the installer (this time mainly to improve installation speed)
- Busybox has been removed from /system/xbin to run properly some banking apps
v5.7 (not released for N910F):
- Improved/expanded built-in RMM lock prevention (thanks to @jesec for idea of overriding properties via factory.prop)
- OEM unlock status will always be displayed correctly in Developer options (to avoid confusion) with stock kernel included in the DevBase ROM
v5.6 (not released for N910F):
- Added "App Lock" feature (Settings -> Advanced features)
- Added Xposed framework as installation option (it is NOT forced by default - you need to force it manually while installing with Xposed first time, e.g. by "xposed" string in ZIP's file name, but next ROM's updates will detect and apply Xposed profile automatically, unless you wipe /system - then auto detection is not possible)
- Added support for applying custom mods automatically at each ROM's install/update by placing modded apps in {storage}/devbase/system/(priv-)app or placing modded framework files in {storage}/devbase/system/framework (where {storage} may be: /sdcard, /external_sd or /usb-otg)
v5.5 (not released for N910F):
- Added support for flashing optional, CSC related partitions ($OMR, $PRELOAD)
- Added possibility to update recovery (optional, performs update if exists $NAME/images/recovery.img)
- Return to using only the original XML files in the CSC package (thanks to @fei-ke for omc-decoder)
- Partition(s) may be wiped only by writing new block's image
- Minor optimizations / improvements in the installer
v5.4 (not released for N910F):
- Big step forward in DevBase ROM customization ability - almost all current ROM features (hidden up to v5.3) have been moved to options.prop (you will be able to easy add new or remove current feature)
- Return to dm-verity-opt-encrypt boot patcher if necessary (wherever it works well, there are still devices which need "no_verity" function introduced in v5.1)
- Initial support for forcing (changing) CSC in case of devices with /odm as CSC location
- Minor optimizations / improvements in the installer
v5.3 (not released for N910F):
- Improved algorithm of search & change "ro.security.vaultkeeper.feature" property to 0 (/system & /vendor)
v5.2 (not released for N910F):
- Added support for devices with /odm as CSC location
- Added support for flashing $ODM, $VENDOR, $KEYSTORAGE, $DQMDBG images
- Added support for custom debloat list and custom CscFeature list in options.prop
- options.prop file format has been changed to CR/LF (Windows) - more noob-proof solution, user can edit a copy of options.prop file even in Windows Notepad (the installer still supports ANY text format of options.prop file - Win/Unix/MAC)
v5.1 (not released for N910F):
- Created new "no_verity" function in the installer, compatible with Samsung's Oreo, based on @Chainfire's patch tool (no-verity-opt-encrypt has been removed). In case of Oreo & Magisk as root solution - "no_verity" function will be used as additional support for patching fstab* (as long as Magisk does not do it correctly)
v5.0 (not released for N910F):
- SYSTEMLESS DevBase has been removed due to the fact, that in case of modern devices/firmwares we need to perform many changes physically in /system anyway, so it loses the sense of use here. If you liked it - you can still install it separately from HERE (it does not need to be re-installed after ROM update as it is installed in /data)
- Added "skipblcp" option to let users skip BL/CP update (additionally it disables auto-reboot when the installer finished work as it is just not necessary then)
- Added "phydebloat" option to let users choose beetween virtual and physical debloat (to get more space in /system)
- Other (minor) optimizations & improvements
v4.6 (starting from N910FXXU1DQL2 DevBase):
- Initial support for devices with /system/omc as CSC location
- SYSTEMLESS DevBase updated to v2.0 (see changelog HERE)
- Added possibility to force CSC by renamig ZIP filename. Due to the fact that trere are many different CSC and it is possible that $ZIPNAME may contain a CSC accidentally - to force CSC you need to put CSC in $ZIPNAME at the beginning and CSC must be followed by "_". Example $ZIPNAME (to force CSC DBT): "DBT_N910FXXU1xxxx_DevBase.zip"
- Added auto efs-backup during install. Installer will create first backup (efs_backup.img.gz) and recent backup (efs_recent.img.gz). The installer will prefer external storage as default backup location (/external_sd or /usb-otg) due to encryption support. MD5 sum and restore command will be stored in efs_backup.txt or efs_recent.txt file
- Other (minor) optimizations & improvements, e.g. added more error messages in case of something went wrong during install
v4.5 (not released for N910F):
- Added new "rescue" option (readable only as string in ZIP file name due to the fact, that we will need this option rarely). It can be a potentially very helpful option in case of bootloop @ encrypted device, caused by a systemless mod/module/xposed stored on /data (without access to /data from TWRP) - more info in post #1
- SYSTEMLESS DevBase updated to v1.14 (see changelog HERE)
v4.4 (not released for N910F):
- Added new "encrypt" option (readable only as string in ZIP file name due to the fact, that we need to do it only once). Now you can easy encrypt all data in your device, just during the ROM upgrade (without data loss) - unfortunately, it does not work in older devices (like G900F/N910F and older), it is just a new unified installer's feature
- SYSTEMLESS DevBase updated to v1.13 (see changelog HERE)
v4.3 (starting from N910FXXU1DQF7 DevBase):
- "root.supersu" & "root.magisk" variables in the options.prop file have been replaced by one "root" variable (dropped possibility to install both -
SuperSU & Magisk - due to the fact that Magisk v13+ does not support SuperSU as root solution)
- SYSTEMLESS DevBase updated to v1.9 v1.10 (see changelog HERE)
v4.2 (starting from N910FXXU1DQC7 DevBase):
- Added possibility to add systemlessly NEW apps to /data/devbase/system/(priv-)app (up to 5 apps in "app" & 5 apps in "priv-app"). The only condition is that you need to rename its directories to CustomApp[1...5] (e.g. CustomApp1, CustomApp2, etc..). These apps will remain even if you flash a new DevBase as corresponding dummy directories will exist in future DevBase updates
- In case of DevBase update or re-installation - installer will not remove your custom entries in /data/devbase/system/build.prop and in *.xml files placed in /data/devbase/system/csc
- SYSTEMLESS DevBase updated to v1.6 v1.8 (see changelog HERE)
v4.1 (starting from N910FXXS1DQC3 DevBase):
- Added full Magisk support - MagiskSU is now default root solution (ROM should pass SafetyNet with Magisk Hide enabled in settings)
- Since systemless Xposed does not need to be re-installed every new DevBase I will release (in case of using the same root solution) - it makes no sense to keep it anymore as installation option
- SYSTEMLESS DevBase updated to v1.5 (see changelog HERE)
v4.0 (starting from N910FXXS1DQC3 DevBase):
- A huge step in the systemless direction! DevBase installer now installs pure odexed stock ROM (just slightly debloated), then systemless SuperSU, then systemless DevBase, then (optionally) systemless Xposed
- All Knox related applications are available again (except SecurityLogAgent, to prevent annoying security alerts)
- Fake KNOX 0x0 status (check it in PhoneINFO app) - most of Knox related apps should work again, like in case of untouched KNOX flag
- All mods known from previous DevBase versions (up to v3.x) now are applied systemlessly - all modified files (including modded apps) are placed in /data/devbase/system instead of physical /system partition. Mods section (#4) has been updated to install mods to /data/devbase/system/(priv-)app if systemless DevBase has been detected (otherwise will be installed as usual, to /system)
- Deodex on-the-fly feature has been removed. If you really need deodexed ROM - you can install someone else's deodexed ROM, then systemless DevBase as an overlay
- Init.d support has been removed as it is deprecated (use su.d instead)
v3.8 (starting from N910FXXU1DPH2 DevBase):
- Added hexpatch to root_from function (support for SM-N930x, thanks to @Chainfire)
v3.7 (starting from N910FXXS1DPF3 DevBase):
- Another major improvement/bugfix in deodex_from function (full support for 64 bit OS)
v3.6 (starting from N910FXXU1DPE1 DevBase):
- Major improvement/bugfix in deodex_from function (added "-g" switch to zip command - finally no issues in case of deodexed Android 6.0.1)
v3.5 (starting from N910FXXU1DPE1 DevBase):
- Improved root_from function (Android 5.1+) - added "setprop selinux.reload_policy 1" removal from init.rc (thanks to @Chainfire)
- Fixed bug in new alghoritm for checking whether stock recovery should be installed or not (introduced in v3.4)
- Added new functionality - installer will store a copy of patched stock kernel in /data for those who flashed custom kernel but for some reasons want to revert to the stock kernel (Android 5.1+)
v3.4 (starting from N910FXXU1DPE1 DevBase):
- Completely changed alghoritm for checking whether stock recovery should be installed or not (it applies to FlashFire users). Now it depends on previously used recovery (instead of checking KNOX flag which was not 100% reliable across devices/recoveries)
v3.32 (not released for N910F):
- Updated set_csc, kcsc_backup, kcsc_restore functions to support more devices
- Updated partition detection algorithm to support more devices
- Fixed path to options.prop file placed in external sdcard in case of updating Marshmallow while using FlashFire
- Minor intaller's optimizations/bugfixes
v3.31 (starting from N910FXXU1DPD3 DevBase):
- Potential fix for reported problems with root (rare cases)
v3.3 (not released for N910F):
- Improved method of reading options from ZIP file name (previous was directory/path sensitive also)
- Added support to mod_csc function for other than UNIX text format (it's a little ridiculous, but in case of some CSCs - original /system/csc/other.xml file has Windows or MAC text format!)
- Initial support for options.prop file in CRLF text format (DOS/Windows)
v3.21 (starting from N910FXXS1CPD1 DevBase):
- Fixed installer's issue if there is a [space] present in ZIP filename or a directory containing DevBase (see #1728)
v3.2 (not released for N910F):
- Another improvements in add_initd function (details - see v1.3)
- Improvements in set_perm, set_perm_rec and root_from functions (recovery-independent structure)
- Improvements in deodex_from function related to Android MM
- New get_con function in the main sh script (useful for devs)
- BusyBox updated to 1.22.1 (bionic) [no, this is NOT a mistake!]
- Minor intaller's optimizations/bugfixes
v3.1 (starting from N910FXXS1CPC5 DevBase):
- Significantly improved "add_initd" function in the update-binary shell script. Added support for (probably) all available Samsung's platforms (e.g. Exynos) and all available firmwares (based on Android 4.4+)
- In case of installation with Xposed framework installer checks if Xposed Installer app is present in /data/app and installs it automatically if necessary
- Minor intaller's optimizations/improvements
v3.0 (starting from N910FXXS1CPC1 DevBase):
- Entire installer has been re-written from the scratch! All "magic" moved to update-binary which is a shell script. It opens up new possibilities never possible before!
- Introduced new customization method - you can change most frequently switched options just by renaming installer's ZIP file name. Currently supported "strings" in the file name:
"noroot" (means "do not root"), "deodex", "xposed", "initd" (no other comments are required, I hope..)
- Starting from v3.0 init.d support is disabled by default
v2.3 (not released for N910F):
- Added option to install suitable Xposed framework in one step while installing DevBase (for maximum comfort). There is a new xframework.sh script - device independent structure and full Android 5.1+/6.0+ support. Backup method is compatible with well known Xposed uninstallers (tested with @wanam's)
v2.2 (not released for N910F):
- Significantly improved root_supersu.sh script - device independent structure and full Android 5.1+/6.0+ suport including on the fly kernel/ramdisk/sepolicy patching if necessary. SU binaries are still copied to /system as it is the best choice in case of custom ROMs
- Changed order of performed operations in the updater-script due to new root_supersu.sh script advantages
- Installer wipes partitions designated for RAW content (e.g. kernel / recovery image) before writing to them
- Minor additions in dex_injector.sh script related to Android 6.0+
v2.11 (not released for N910F):
- Fixed some minor installer's issues ("set_perm" function in set_csc.sh did not work correctly while using wildcards in the path (it was exclusively FlashFire issue! no problem with TWRP / CWM). Fortunately - only /system/etc/csc_*.txt were really "affected" - it didn't cause real issues as these files are empty)
v2.1 (starting from N910FXXU1POK1 DevBase):
- As some people felt a bit disapointed / worried about DevBase v2.0 ROM file size - finally I have decided to debloat stock system.img (in same way as in v1.x => "Safe De-Bloat") and remove option to install all available bloatware. ROM file size has been reduced from about ~2GB to about ~1.6GB. Note for Devs / Chefs: Do not use Windows tools - you need Linux with "selinux" package installed (to handle SELinux contexts) to mount (rw) system.img safely. If you want to add / change any system content this way - remember about proper chown/chmod/chcon
- Added device check during install as flashing directly to EMMC block is potentially more risky for "other" devices. Installer will abort installation if device is not N910F (trlte(xx)). If you want to try this ROM on other N4 devices - you need to remove this check manually from updater-script (it is more conscious procedure)
v2.0 (starting from N910FXXS1COK2 DevBase):
- Completely new concept of ROM development that makes it easy to build most tuned and nuanced custom ROMs. No more arduous manual analysis or (often) invalid permissions / SELinux contexts taken from a kitchen. The main idea is to flash original, stock /system image as EMMC block (in same way as PC Odin does) instead of extracting ZIP's contents to mounted partition, then setting permissions, then creating symlinks, etc. However, it requires more knowledge related to sh scripts as ALL necessary changes need to be done on the fly, while installing (e.g. by injecting modified classes.dex and/or modified images/xmls to /res/../* into an apk). There are no limits, all depends on your creativity!
- One common ZIP installer for Odexed and Deodexed ROM - you can control it by new "deodexed.rom" entry in options.prop (there is new dex_injector.sh script which can deodex on the fly the whole ROM using previously processed classes.dex files)
- ROM is still Safe De-Bloated by default but removing bloatware during install is not mandatory - you can control it by new "safe.debloat" entry in options.prop (there is new protection included to avoid overfilling /system in case of large size of additional MODs and/or large multi CSC package)
- Major improvements in csc_detect.sh script - it is able to detect previous CSC even in cases of flashing over e.g. CM based ROM and/or previously formatted system partition. However, if detected CSC is NOT included in my multi CSC package, in both mentioned cases it is still not possible to keep detected CSC (as there is no CSC related content to backup / restore)
- Improvements in all sh scripts - additional "metadata" entries in updater-script (related to processed contents) are not required
- Improvements in root_supersu.sh script - it is suitable for 32 and 64 bit OS
- Added full zip support from the command line
v1.x (initial version, further improvements, up to N910FXXU1COJ3 DevBase):
- Built without using a kitchen. All set_metadata* / symlink entries are result of arduous manual analysis. For more info about the method - see hidden content for Devs / Chefs in THIS thread.
- New customization method without using Aroma (options.prop)
- Many useful scripts for easy installation: CSC applying/autodetection, backup/restore of security files, backup/restore of existing CSC package, XML modding on the fly, root, init.d support
- Many small changes and improvements "in the meantime" which I simply do not remember...
- Safe De-Bloated (see post #1 for details)
DOWNLOADS
Useful PC Odin flashable files
>> Recent bootloader versions for SM-N910F <<
>> Recent modem versions for SM-N910F <<
>> Recent kernel versions for SM-N910F <<
(suitable kernel is already included in my ROM)
Note:
To update bootloader and/or modem you have to power off the phone, wait min 10 seconds and then go directly to Download Mode using Vol_down+Home+Power key combination. Load bootloader using BL button and/or modem using CP button in PC Odin. Push "Start".
DOWNLOADS
Optional MODs
I put some of my favorite MOD's - especially for normal users who want to use my rom - as it is. These modifications I have done personally using (bak)smali tools - these are NOT "borrowed" from other custom rom, nor from someone else's thread (thanks to @majdinj & @tdunham for their excellent modding guides). All files are TWRP / CWM / FlashFire flashable ZIPs:
1. Modified Camera app:
- Full functionality of the Camera app in low battery
2. Modified Phone app:
- Disabled increasing ringtone
3. Modified Messages app:
- Disabled SMS to MMS auto-converting
- Increased SMS/MMS recipient limit (10 -> 1000)
- Increased SMS/MMS hour limit (100 -> 1000)
- Disabled SMS / MMS log history in call logs
- Disabled SMS delivery notifications (*)
(*) If you long press a message you can still check if the message has been delivered or not, we do not need to see and hear notifications for every sms. It's annoying to me!
>> MODs for N910F (Marshmallow) <<
>> MODs for N910F (Lollipop) <<
In case of MODs installed to /system - you can restore original apk using backup stored in /data/backup/alexndr
First to wish you good luck, i'll try flashing this and get back to you
thx a lot for modem and bl!!!
So just flashed the ROM now and i can tell that you have done a great job there, kudos for that
and good luck
Pleasure to see you here my friend! Built the metadata using your method the day before yesterday! No kitchen anymore for that! You're absolutely amazing! And yes we're already building custom mod installer. On note 4 it's a must!
Thank you again much!!!
Welcome..Great work, lovely build, thank you. :good:
I wonder how it has to be installed. via Odin or CWM?
mkozlowski said:
I wonder how it has to be installed. via Odin or CWM?
Click to expand...
Click to collapse
It's a recovery flashable zip with odexed stock. To be used as a daily driver as prerooted rom or as dev base for rom cooks.
great to see you here too :good:
A pleasure that you moved!
So I'll give it a shot in few minutes.Hope everything goes fine.
Hello,this rom is stock look?
alexanter the great said:
Hello,this rom is stock look?
Click to expand...
Click to collapse
yes
Welcome
Great to see you here Alexndr ..
alex , thanks for your work again , the best , as always , but lot of people report this build Lollipo 5.0.1 has a very quick battery draining , do you note that ? Thank you !
_Alexndr I flashed your rom. Everything is working great. Only issue is S Health (it stoped). Any idea to fix it? Thanxs in advance.
radiobicho said:
_Alexndr I flashed your rom. Everything is working great. Only issue is S Health (it stoped). Any idea to fix it? Thanxs in advance.
Click to expand...
Click to collapse
did you clear cache and data ? updated ?
radiobicho said:
_Alexndr I flashed your rom. Everything is working great. Only issue is S Health (it stoped). Any idea to fix it? Thanxs in advance.
Click to expand...
Click to collapse
Happened to me after flashing stock. I cleared data to S health and Health Services. After that, peachy
Sent from my SM-G900F using Tapatalk
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
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.
Welcome to SuperR's Kitchen Donate version!
This thread is intended to organize release posts. All discussion regarding this kitchen can be found in the thread linked below.
[ Windows / Linux / Mac ][DONATE] SuperR's Kitchen (v3.2.2.2 - 10-13-2021)
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 :D Please read the troubleshooting in post #4 of the standard kitchen thread...
forum.xda-developers.com
v3.0.0.1
Changes:
Download and extract Android Image Kitchen (Linux) directly from the XDA thread.
Fixed extracting tar.gz files.
Fixed crash if the main tools download/extract fails.
Fixed crash in Linux when updating the kitchen launcher.
Fixed crash when running the updater if there is no update available.
Added logging to img extract operations.
Fixed crash if Java 8 is not installed on Linux.
Added check for proper java installation on Windows.
Fixed language files other than English.
v3.0.0.2
Changes:
Fixed extracting Pixel firmware.
v3.0.0.3 (Donate version)
Changes:
Fixed custom zips on Pixel devices.
Removed attempts to pip install packages from within the kitchen.
Added logging to adb operations.
v3.0.0.4
Changes:
Require kitchen restart after updating.
Fixed duplicate unmount commands in updater-script when extracting extra img files.
Fixed some language file checks from crashing.
Added official Windows launcher (superr.exe).
The kitchen should install psutil (win/linux) and colorama (win) packages now if they are not already installed.
Thanks to @Xennet for the launcher idea. It makes running the kitchen in Windows a lot easier
NOTE: You should restart the kitchen manually after the update. This will be the last time you will have to remember on your own
v3.0.0.5
Changes:
Fixed Windows kitchen trying to update the Linux launcher.
Fixed cyfile errors.
Fixed system.img.ext4 not being renamed automatically if not in an archive.
Added dialog informing we are getting the plugin list when installing a plugin.
Check for and show error message when trying to run Bash plugins in Windows.
Remove all set_metadata lines with a context of "?".
Add all files in /system/bin to the updater-script.
edit: I forgot to reset the language file in this update, so if you update you will get an error when you try to install a plugin.
Easy fix after update (fresh installs do not need this):
Misc tools >> Reset language - After restart no more error
v3.0.0.6
Changes:
Hopefully fixed crash after signing zips when checking for update-binary script.
Updated Imgextract.exe to 1.3.7.
v3.0.0.7
Changes:
Ignore commented lines in build.prop.
Do not create set_metadata lines for files/directories that do not exist.
Do not use fstab with nodata in the name.
Removed duplicate /system/vendor/firmware set_metadata line.
Fixed tar creation for future use.
v3.0.0.8
Changes:
Minor improvement to set_metadata generation in Windows.
Fixed Android O rom not building due to lack of xbin.
v3.0.0.9
Changes:
zipalign - check to make sure files exist before renaming and record in main.log.
Fixed assert getting broken when building rom.
Fixed line endings in updater-script when running in Windows (thanks to @chevycam94 for pointing it out).
NOTE: You may need to change perm types to something else and back to whatever you want to get the line endings sorted out. Fresh extract will all be good now
NOTE2: If you go to ROM Tools >> Asserts Menu >> Reset asserts to default you will get your assert back to normal if it was broken.
v3.0.1.0
Changes:
Fixed crash when choosing main menu from root zip options menu.
Fixed crash when getting by-name through adb.
v3.0.1.1
Changes:
Fixed crash in Windows when checking for app_chimera at the start of deodexing N and O.
Fixed crash when finishing deodex on M and L.
Fixed crash and show error message when entering the wrong syntax for custom asserts.
Fixed boot/AIK still being part of the repo and causing Windows tools install failure after resetting tools and boot extraction failure on Linux.
Fixed crash removing knox in Windows.
Fixed crash deleting plugins if example does not exist.
Heapsize errors now return you to heapsize options instead of Misc Tools.
Added confirmation when deleting projects.
Tried to fix META-INF1 remaining after builing rom.
Thanks to @chevycam94 for testing like a mad man
v3.0.1.2
Changes:
Fixed logs crash when check for updates on start is enabled.
v3.0.1.3
Changes:
Change root status to rooted when adding Magisk using the plugin.
v3.0.1.4
Changes:
Display root type instead of Rooted.
Fix error during deodex cleanup on L and M.
Fix crash when removing knox.
v3.0.1.5
Changes:
Disable sepolicy-inject root method for Windows.
Fixed sepolicy-inject root method for Linux.
Fixed some debloat/knox checks.
Updated smali/baksmali to v2.2.1.
v3.0.1.6
Changes:
Fix crash when signing zips that use an update-binary script in Windows.
Log zip signing in sign.log.
Fixed update-binary conversion on roms that do not use by-name.
Make a copy of *_statfile.txt after extracting img files in Windows.
Add *_statfile.txt to support zip.
Add META-INF directory to support.zip.
Fixed Downloading/installing screen that disappeared.
v3.0.1.7
Changes:
Fixed manually signing zip when there are more than one to choose from.
Added ability to convert all flashable zips to update-binary script when building.
Added per-project option in Misc Tools for update-binary script - Always convert, Never convert, Ask every time.
Added check for delete_recursive when converting to update-binary script.
Fixed mount command not getting converted to update-binary script if rom does not use by-name.
NOTE: The default of the new update-binary conversion switch is "Ask every time". Remember, this is per project so you will need to change it for all projects if you want it changed globally.
v3.0.1.8
Changes:
Windows: Use 7-zip (included) to extract img files instead of Imgextractor.
Windows: Fixed missing symlinks in updater-script.
Windows: Fixed many file contexts not being set correctly.
Windows/Linux: Fixed system/SYSTEM on devices that use SYSTEM.
Linux: Do not create metadata lines for symlinks.
I think this will fix most of the flashing problems. Let me know how it goes
WINDOWS NOTE: It is important that the tools get updated. The updater should take care of it, but if you get errors that 7z is not found, go to Misc tools > Reset tools.
IMPORTANT: Start your rom fresh and extract from system.img again. Make sure you delete 00_project_files directory if you are reusing an existing project.
v3.0.1.9
Changes:
Windows: Fixed b key press not being recognized.
Added a Back option to the root method options.
Only allow key presses that correspond to menu options.
Fixed project name adding an extra superr_ when creating new project from the project selection menu.
Set permissions of configure.sh to 777 instead of /tmp to 755.