[Android] mafsi:
[MENTION=6350858]ASSAYYED[/MENTION]

I think there is an error on latest version on Aroma.

Bulding a ROM now freeez installation on 20% (Extracting data & system) showing no move of theprogression bar. Then it jumps to the end an the message:

"results scripts was: [instalation complete"

Here is the log (GT-I9505)

AROMA INSTALLER version 3.00
(c) 2013-2015 by amarullz.com

ROM Name : Miorita ROM
ROM Version : 1.0
ROM Author : Mafsi
Device : GT-I9505
Start at : Sat Sep 3 23:53:09 2016

************************************************
* Installing Miorita ROM
* For GT-I9505
* Running android Lollipop 5.0.1
* Developed by Mafsi
************************************************
-- Preparing device partitions
about to run program [/sbin/mount] with 4 args
mount: mounting /dev/block/mmcblk0p16 on /system failed: Device or resource busy
run_program: child exited with status 255
about to run program [/sbin/mount] with 4 args
mount: mounting /dev/block/mmcblk0p29 on /data failed: Device or resource busy
run_program: child exited with status 255
-- Backing up efs partition
about to run program [/tmp/efs_backup.sh] with 1 args
__bionic_open_tzdata: couldn't find any tzdata when looking for CST6CDT,M3.2.0,M11.1.0!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
mount: mounting /dev/block/mmcblk0p29 on /data failed: Device or resource busy
__bionic_open_tzdata: couldn't find any tzdata when looking for CST6CDT,M3.2.0,M11.1.0!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
mount: mounting /dev/block/mmcblk0p10 on /efs failed: Device or resource busy
tar: removing leading '/' from member names
-- Continue without safe format
-- Cleaning up all device partitions
-- Extracting system & data
-- Creating symbolic links
created [/system/etc/firmware/wcd9310]
created [/system/priv-app/SamsungLinkPlatform]
created [/system/priv-app/SamsungLinkPlatform/lib]
created [/system/priv-app/SamsungLinkPlatform/lib/arm]
created [/system/app/Bluetooth/lib]
created [/system/app/Bluetooth/lib/arm]
created [/system/app/RootPA/lib]
created [/system/app/RootPA/lib/arm]
created [/system/priv-app/DefaultContainerService/lib]
created [/system/priv-app/DefaultContainerService/lib/arm]
created [/system/app/SecEmail_K]
created [/system/app/SecEmail_K/lib]
created [/system/app/SecEmail_K/lib/arm]
created [/system/app/PacProcessor/lib]
created [/system/app/PacProcessor/lib/arm]
created [/system/app/NfcNci/lib]
created [/system/app/NfcNci/lib/arm]
created [/system/app/SPrintSpooler]
created [/system/app/SPrintSpooler/lib]
created [/system/app/SPrintSpooler/lib/arm]
created [/system/app/SBrowser]
created [/system/app/SBrowser/lib]
created [/system/app/SBrowser/lib/arm]
created [/system/app/SamsungIME/lib]
created [/system/app/SamsungIME/lib/arm]
-- Setting & fixing permissions
about to run program [/system/xbin/busybox] with 4 args
about to run program [/system/xbin/su] with 2 args
-- Flashing kernel image
about to run program [/tmp/flash_kernel.sh] with 1 args
17052+1 records in
17052+1 records out
8730896 bytes (8.3MB) copied, 1.343963 seconds, 6.2MB/s
17052+1 records in
17052+1 records out
8730896 bytes (8.3MB) copied, 1.235718 seconds, 6.7MB/s
17052+1 records in
17052+1 records out
8730896 bytes (8.3MB) copied, 1.258911 seconds, 6.6MB/s
-- Running rom configuration
about to run program [/tmp/ext4.sh] with 1 args
tune2fs 1.42.9 (28-Dec-2013)
tune2fs 1.42.9 (28-Dec-2013)
tune2fs 1.42.9 (28-Dec-2013)
tune2fs 1.42.9 (28-Dec-2013)
tune2fs 1.42.9 (28-Dec-2013)
tune2fs 1.42.9 (28-Dec-2013)
-- Finishing installation
Installation completed successfully
script succeeded: result was [Installation completed successfully]

Installer Sucessfull (Status 0)

End at : Sat Sep 3 23:56:42 2016

Later Edit: I downgraded and builded a new installer with 6.2 alpha. Everything was ok with the installer. The only bug was the reboot button that is not rebooting the device but it shutdown.

Also on the stable version somehow is inserting me the original recovery when the Rom is changing CSC. I dont know if this is from your Kitchen... With 6.2 alpha didn't happened this.

There is something wrong with the installer in 1.0 stabe version of the kitchen.

Thanks