Sunday, July 3, 2016

[BEST ANDROID ROMs EDITOR] ASSAYYED_KITCHEN

THE FULL ANDROID ROMs EDITOR FOR WINDOWS


Hello everyone this is the first post for me
and in this post i am proud to introduce my kitchen "ASSAYYED KITCHEN"

The kitchen features:
1- Extract android ROM from:
* Stock Samsung updates [tar.md5] or [tar]
* System image with kernel and cache and preload partition
for Samsung roms [system.img] [boot.img] [cache.img] [hidden.img]
* Stock Sony updates [ftf]
* Stock Sony files [system.sin] [kernel.sin]
* Old cooked rom [zip]
* Zip contents [sparse_chunks] like motorola
* System.yaffs2 and kernel
* System.ext4 converted or dumped using flashtool with kernel
* Zip contents system.img with kernel
* Zip contents system.new.dat with kernel
* Pull rom from any device EVEN IF THE DEVICE NOT ROOTED

We all know that android system built on linux and so
the support for android in windows is very weak BUT NOT WITH MY KITCHEN
The most important thing needs to support is symbolic links in the rom
that known as [Symlinks] and without them the android rom doesn't work
we know that we can unapck any system.img by converting it to raw ext4 type
then extracting all contents using some tools like [ext2explorer].......etc
but this method doesn't support the symlinks
In linux system we mount the image and copy the contents with
symlinks this is the correct way........AND I HAVE PORTED THE WAY TO WINDOWS :cool:
With my kitchen the windows will have all android support with symlinks
like the linux we mount the ext4 image after we add support to read,write,mount
ext4 partitions in windows using [Ext2fsd] and [OSFmount].....
And detect the symlinks using command [find -type l] same as linux system :cool:

Now about pulling the rom from device:
The adb binary can pull the system image from device
with dd command for the system file in device but we can't
use this command for un-rooted devices ALSO MY KITCHEN CAN PULL ANY ROM FROM ANY DEVICE EVEN WITHOUT ROOT
Yes! we can pull any rom with symlinks from device even if the device not rooted :)

2- With one deodex script can deodex all android roms from android 2.3 up to android 6+
and deodex for all apks in system folder in addition to knox apks and all apks
not in app or priv-app folder

3- Can zipalign all rom apks in addition to data apks and apks in other folders

4- The root [SuperSU] [2.67]: support add root to all devices and all archictures arm/mips/x86...32/64
and support add root installer during recovery flash for AOSP/CyanogenMOD ROMs
NEW FEATURE: the kitchen support two kinds of root FAST AND CLASSIC.....
FAST MODE: will add root without Supersuer.apk and this mode is faster during detect
from apps that need root
CLASSIC MODE: add root with Superuser.apk like all roms

5- busybox [1.24]: support add to all devices and all archictures arm/mips/x86...32/64

6- Building the rom for flashing:
the kitchen can build in 4 methods :)
* Normal mode [zip] support standalone installer and AROMA INSTALLER
* system.new.dat [zip] for all android versions
* raw ext4 system.img [zip] for all android versions
* The super feature: create same as Samsung official tar rom

The 4 method is same as samsung tar roms create sparse system.img
and support all devices sparse header 28bit and 32bit [the kitchen will explain how to do that]
and this method can create pre-rooted roms for devices that doesn't have any custom recovery :)

7- Add a lot of build.prop tweaks that improve rom performance in general
8- Add init.d run-parts support for rom itself without kernel [Credit to JustArchi]
9- Support to De-knox all samsung roms
10- Support to Debloat all roms and support manually and automatically debloating
The manually debloating will print all apks and give choice to user to remove selected apk

11- Unpacking the kernel: support 3 methods to unpacking the kernel and repacking it in one second
and very easy and convert kernel.sin [Sony] to boot.img

12- Enable adb insecure in kernel

13- Add sqlite & sysro & sysrw to scripts to rom

14- Can save project and restore it to work on it

15- Add init.d support in kernel

For rom standalone installer [META-INF]:
can add script to wipe data before installing the rom
and script to backup efs partition for samsung devices
and script to convert system,data,cache partitons to journal write back
using tun2fs and add slim~~~.bin data/cfw files
16- Add a lot of system/etc/init.d tweaks

17- Support to change [Build number] string in build.prop

18- Push ready roms to external or internal storage in device

Now the super feature in this kitchen:
kernel path and devices databases.....
The kitchen support all devices in the world without know any path using :cool:
a script that detect the kernel path during the installation in recovery
in addition to detect and format and mount system,data,cache,preload partitions
automatically before installing using a bash shell script

The normal updater-script contents:
package_extract_file("boot.img", "/dev/block/~~~~~~~~~~");
But in my kitchen use:
package_extract_file("boot.img", "/tmp/boot.img");
run_program("/tmp/auto.sh", "image");
in this way the script [auto.sh] can flash any kernel to correct path without need
to detect kernel path :)

The build method using raw ext4 and system.new.dat needs to detect system path
and unfortunately i don't know what recovery command using to flash system.new.dat or
flash system.img directly from the zip file so the kitchen needs to detect system path
and this is not a problem the kitchen can detect the path from:
boot.img, recovery.img, from device throw adb, and allow to user to write it manually

The build method using raw ext4 and system.new.dat and tar needs to detect system size
and this is very easy the kitchen allow to user to write the size if know its
in general the kitchen detect the system folder size not device system size and
in this way the rom will work without errors, however the kitchen also can detect
the device system size from adb in recovery mode or normal mode when device boot up

In the rom recovery installer the kitchen detects two kinds of permissions
set_perm & set_metadata

the set_perm is written for roms that android versions is lower than jeally bean 4.2.2-
and the set_metadata is written for roms that android versions is higher than jeally bean 4.3+
that have file_contexts in the kernel and the kitchen automatically detects the android version
and set the correct permissions

I have tested the kitchen on windows-64 on:
galaxy: s3 s4 s7 j1/2/7/5 grand prime. and many more.....
I haven't test it on sony roms

And in the end i hope from anyone to give his Experience in this kitchen
and post any problems here to fix it

How to use:
Downloaad the kitchen from the link:
Note: copy and past the link in your browser
http://ift.tt/29otWnx
then extract the ziped file you will get [TOOLS] folder and [ASSAYYED.EXE] file
run [ASSAYYED.EXE] in the first run time the kitchen will create these folders:
PLACE: The folder you will put rom to cook in
READY: The folder contents the final ready roms
WORK: The folder that the kitchen use it during rom cook
now put the rom you want to cook in place folder
Note: you can put unlimited count of roms in place folder from different kinds
like: tar & zip & system.img with boot.img & system.sin with kernel.sin..........
then start command 1 and the kitchen will continue to print all roms with numbers
and all what you need is to select a number for your rom [same as dsixda kitchen]

Credits:
Cygwin: For linux tools
AOSP: For android image tools [simg2img, make_ext4fs, adb......etc]
howellzhu: For rimg2sdat
JesusFreke: For smali & Baksmali
_riddle: For oat2dex
osm0sis: For kernel tools and Busybox
Chainfire: For SuperSU
cofface: For bootimg [kernel extractor]
And_pda: For imgextractor.exe http://ift.tt/29hHMVI
Ext2fsd Project: ext2fsd.com
OSFmount Project: http://ift.tt/1Mz4JRn
thomas_polaert: For cecho command
Igor Pavlov: For 7zip binary
xpirt: For sdat2img
Sorry if forget anyone



In smaller explain FULL AND COMPLETE ALL ANDROID ROM EDITOR AND FULL SUPPORT IN WINDOWS LIKE LINUX AND
ABILITY TO COOKING ANY ROM AND ALL AVAILABLE FEATURES WITH ONE CLICK.......


SORRY FOR BAD ENGLISH
BEST WISHES


from xda-developers http://ift.tt/29hI0Mv
via IFTTT

1 comment: