Hi all.
before anything :
- this tool is for especialy for dualbooters because i havent tested in 1rst rom. but updater-script manage kernel flashed. prepare odin in case of bad flash, you're advised.
- always make nandroid before use and flash with my tool.
I saw that ppl have many trouble to install 4.4.2 kitkat roms on their device.
it seems that we have manu such "error status 7" , and these were about setting persmissions during flash.
so i decide to make an aroma to avoid this error.
if you flash an original 4.4.2 Kitkat rom and have the error, no need to flash another compatible recovery kernel to re-try, just use my aroma flasher with the steps i descride below. In the aroma advanced MENU, you will choose set_perm commands compatible flash instead of set_metadata commands persmission to see if flask process will work in fine
Sure, at end of process, a kernel will be flashed, dorimanx branch 8 i have put in pach you went to donwload, or another you have put instead like i describe in extra step 6 below too.
so, AROMA structure details is like this :
pach/AROMA
---------backupEFS <------- useful script, no need to touch.
---------KERNEL <------- place here your boot.img file. (original rom or other)
---------maliv2
-------------system/lib/egl/ <-------- maliv2 .so libs contents, no need to touch.
pach/data/app <--------- you can put som apks here, moved from /system/app/ (i often move in latinIME.apk from /system/app/ and then i free 40Mo on /system/ partition, its good for GAPPS)
pach/META-INF/....../ <--------- no need to touch.
the available download pach i use for some months now , is here :
UniversalAROMAinstallerFOR-4.4.2-ROMs-DefinitivePach.rar - 8.53 MB
how to use it
1 - download any kitkat 4.4.2 ROM your want to install I9100.
2 - try it normaly, and see if you have error on flash.
3 - when you got it, on PC, make a safe copy ot it somewhere, and open it with WINRAR. Then delete META-INF and other boot.img file. just let system folder in ZIP.
4 - uncompree my AROMA somewhere.
5 - drag and drop the 3 "bolded" folders (in aroma structured details) in ZIP rom you still have opened.
extra step 6 : in AROMA/KERNEL/ folder, you will find dorimanx branch 8 version (new @StanTRC recovery inside) i have put. You can replace it with any boot.img you want , even those from original rom zip you have safely somewhere on your PC. just extract boot.img from it and replace with in you new aroma installer rom zip you went to manage in steps 3, 4 and 5 .
aroma choice you will have :
"Compatibility of your Recovery Kernel",
"Your Kernel is compatible for set_metadata commands"
"Your Kernel ONLY understand set_perm commands"
"choose your based KK similar rom",
"AOSB BEANSTALK C-ROM EHNDROIX"
"CARBON"
"CM11 JELLYBAM"
"SABER PAC"
"PA"
"Resurrection Remix"
"SLIM SPIRIT"
"NEATROM AICP"
"SOKP"
"Backup EFS",
"Backup your EFS folder before flash"
"Skip"
"Kernel to flash at end of process",
"DorimanX 8 and MaliV2"<---------- option that serve to flash MALIV2 for dorimanX branch 8 users, dualbooters.
"any other kernel"
EXTRA TOOL : .db qulite bases "wiper" , it delete some .db files in some /data/data/com.android........../databases/ folders, usefull when we flash from <> based 4.4.2 roms, CM11 , RR , PAC , SLIM, PA....sometimes worked fines for me.
"Delete some SQlite .db files in ROM",
"YES ","Delete some SQlite .db from you installed rom to avoid com.android.phone FC or other FCs"
"NO thanks we can FLASH the ROM"
again, this is just for test and fun , dualbooters will like more that "normal" users. no risk to flash kernel in 2nd rom, but remember need maliv2 during AROMA....and i always afraid someone that try my work on 1rst rom will brick its device.....so i advertise everyone that before upload my "daily" works, i'm not always flashing them on my 1rst rom.
thanks.
before anything :
- this tool is for especialy for dualbooters because i havent tested in 1rst rom. but updater-script manage kernel flashed. prepare odin in case of bad flash, you're advised.
- always make nandroid before use and flash with my tool.
I saw that ppl have many trouble to install 4.4.2 kitkat roms on their device.
it seems that we have manu such "error status 7" , and these were about setting persmissions during flash.
so i decide to make an aroma to avoid this error.
if you flash an original 4.4.2 Kitkat rom and have the error, no need to flash another compatible recovery kernel to re-try, just use my aroma flasher with the steps i descride below. In the aroma advanced MENU, you will choose set_perm commands compatible flash instead of set_metadata commands persmission to see if flask process will work in fine
Sure, at end of process, a kernel will be flashed, dorimanx branch 8 i have put in pach you went to donwload, or another you have put instead like i describe in extra step 6 below too.
so, AROMA structure details is like this :
pach/AROMA
---------backupEFS <------- useful script, no need to touch.
---------KERNEL <------- place here your boot.img file. (original rom or other)
---------maliv2
-------------system/lib/egl/ <-------- maliv2 .so libs contents, no need to touch.
pach/data/app <--------- you can put som apks here, moved from /system/app/ (i often move in latinIME.apk from /system/app/ and then i free 40Mo on /system/ partition, its good for GAPPS)
pach/META-INF/....../ <--------- no need to touch.
the available download pach i use for some months now , is here :
UniversalAROMAinstallerFOR-4.4.2-ROMs-DefinitivePach.rar - 8.53 MB
how to use it
1 - download any kitkat 4.4.2 ROM your want to install I9100.
2 - try it normaly, and see if you have error on flash.
3 - when you got it, on PC, make a safe copy ot it somewhere, and open it with WINRAR. Then delete META-INF and other boot.img file. just let system folder in ZIP.
4 - uncompree my AROMA somewhere.
5 - drag and drop the 3 "bolded" folders (in aroma structured details) in ZIP rom you still have opened.
extra step 6 : in AROMA/KERNEL/ folder, you will find dorimanx branch 8 version (new @StanTRC recovery inside) i have put. You can replace it with any boot.img you want , even those from original rom zip you have safely somewhere on your PC. just extract boot.img from it and replace with in you new aroma installer rom zip you went to manage in steps 3, 4 and 5 .
aroma choice you will have :
"Compatibility of your Recovery Kernel",
"Your Kernel is compatible for set_metadata commands"
"Your Kernel ONLY understand set_perm commands"
"choose your based KK similar rom",
"AOSB BEANSTALK C-ROM EHNDROIX"
"CARBON"
"CM11 JELLYBAM"
"SABER PAC"
"PA"
"Resurrection Remix"
"SLIM SPIRIT"
"NEATROM AICP"
"SOKP"
"Backup EFS",
"Backup your EFS folder before flash"
"Skip"
"Kernel to flash at end of process",
"DorimanX 8 and MaliV2"<---------- option that serve to flash MALIV2 for dorimanX branch 8 users, dualbooters.
"any other kernel"
EXTRA TOOL : .db qulite bases "wiper" , it delete some .db files in some /data/data/com.android........../databases/ folders, usefull when we flash from <> based 4.4.2 roms, CM11 , RR , PAC , SLIM, PA....sometimes worked fines for me.
"Delete some SQlite .db files in ROM",
"YES ","Delete some SQlite .db from you installed rom to avoid com.android.phone FC or other FCs"
"NO thanks we can FLASH the ROM"
again, this is just for test and fun , dualbooters will like more that "normal" users. no risk to flash kernel in 2nd rom, but remember need maliv2 during AROMA....and i always afraid someone that try my work on 1rst rom will brick its device.....so i advertise everyone that before upload my "daily" works, i'm not always flashing them on my 1rst rom.
thanks.
Last edited:
