About flashing latest Omnirom 5.1

its smooth.. the bigmem on adv. settings helps a lot.. troubled at first because of partitioning, using twrp it always saying E:\cant mount data.. return back to stock and used cwm to partition.. everythings fine.. but sometimes it soft reboots.. never know the reason..

heres my log..

bml_over_mtd.log

Quote:

+ export PATH=/:/sbin:/system/xbin:/system/bin:/:/sbin:/system/xbin:/system/bin:/tmp:/sbin + busybox cat + busybox date __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! ################################################## ###################################### # # Flashing boot image with bml_over_mtd on Mon Sep 7 05:22:35 CDT 2015 # ################################################## ###################################### + /tmp/bml_over_mtd scan boot /tmp/bml_over_mtd.sh: line 1: /tmp/bml_over_mtd: not found + status=127 + test 127 -eq 15 + echo Running flash_image... Running flash_image... + /sbin/flash_image boot /tmp/boot.img mtd: successfully wrote block at 0 mtd: successfully wrote block at 40000 mtd: successfully wrote block at 80000 mtd: successfully wrote block at c0000 mtd: successfully wrote block at 100000 mtd: successfully wrote block at 140000 mtd: successfully wrote block at 180000 mtd: successfully wrote block at 1c0000 mtd: successfully wrote block at 200000 mtd: successfully wrote block at 240000 mtd: successfully wrote block at 280000 mtd: successfully wrote block at 2c0000 mtd: successfully wrote block at 300000 mtd: successfully wrote block at 340000 mtd: successfully wrote block at 380000 mtd: successfully wrote block at 3c0000 mtd: successfully wrote block at 400000 mtd: successfully wrote block at 440000 mtd: successfully wrote block at 480000 mtd: successfully wrote block at 4c0000 mtd: successfully wrote block at 500000 mtd: successfully wrote block at 540000 mtd: successfully wrote block at 580000 mtd: successfully wrote block at 5c0000 mtd: successfully wrote block at 600000 mtd: successfully wrote block at 640000 wrote boot partition + exit

omni_bml.log

Quote:

+ check_mount /efs /dev/block/stl3 rfs + /tmp/busybox grep -q /efs /proc/mounts + /tmp/busybox mkdir -p /efs + /tmp/busybox umount -l /dev/block/stl3 umount: can't forcibly umount /dev/block/stl3: Invalid argument + /tmp/busybox mount -t rfs /dev/block/stl3 /efs + /tmp/busybox test -e /sdcard/backup/efs.tar + /tmp/busybox rm -f /sdcard/backup/efs.tar + /tmp/busybox rm -f /sdcard/backup/efs.tar.md5 + /tmp/busybox mkdir -p /sdcard/backup + cd /efs + /tmp/busybox tar cf /sdcard/backup/efs.tar imei nv.log root updated_filesystem + cd /sdcard/backup/ + /tmp/busybox md5sum -t efs.tar + /tmp/busybox test -n /sdcard/omni-5.1.1-20150831-galaxys4gmtd-HOMEMADE.zip + PACKAGE_LOCATION=/sdcard/omni-5.1.1-20150831-galaxys4gmtd-HOMEMADE.zip + /tmp/busybox echo /sdcard/omni-5.1.1-20150831-galaxys4gmtd-HOMEMADE.zip + /tmp/busybox echo install_zip("/sdcard/omni-5.1.1-20150831-galaxys4gmtd-HOMEMADE.zip"); + /tmp/busybox echo install /sdcard/omni-5.1.1-20150831-galaxys4gmtd-HOMEMADE.zip + /tmp/busybox rm -f /sdcard/clockworkmod/.settings + /tmp/busybox rm -f /sdcard/TWRP/.settings + /tmp/flash_image boot /tmp/boot.img + [ 0 != 0 ] + /tmp/busybox echo Successfully wrote kernel to boot partition Successfully wrote kernel to boot partition + /tmp/busybox sync + /tmp/busybox umount /sdcard umount: can't umount /sdcard: Device or resource busy + /tmp/busybox sleep 10 + /sbin/reboot

omni_mtd

Quote:

+ /tmp/busybox mkdir -p /radio + /tmp/busybox grep -q /radio /proc/mounts + /tmp/busybox umount -l /dev/block/mtdblock6 umount: can't forcibly umount /dev/block/mtdblock6: Invalid argument + /tmp/busybox mount -t yaffs2 /dev/block/mtdblock6 /radio + /tmp/busybox test -e /radio/modem.bin + /tmp/busybox umount -l /dev/block/mtdblock6 + /tmp/erase_image radio + /tmp/busybox mount -t yaffs2 /dev/block/mtdblock6 /radio + /tmp/busybox cp /tmp/modem.bin /radio/modem.bin + /tmp/busybox sync + /tmp/busybox umount -l /dev/block/mtdblock6 + /tmp/erase_image boot + /tmp/bml_over_mtd.sh boot 72 reservoir 4012 /tmp/boot.img + /tmp/busybox umount -l /system umount: can't forcibly umount /system: Invalid argument + /tmp/erase_image system + /tmp/busybox test -e /sdcard/omni.cfg + /tmp/busybox echo Updating from a BML rom. Format /cache and /data, and attempt to restore /efs Updating from a BML rom. Format /cache and /data, and attempt to restore /efs + /tmp/busybox rm -f /sdcard/omni.cfg + /tmp/busybox rm -f /sdcard/extendedcommand + /tmp/busybox rm -f /sdcard/openrecoveryscript + /tmp/busybox umount -l /cache + /tmp/erase_image cache + /tmp/busybox umount -l /data umount: can't forcibly umount /data: Invalid argument + /tmp/make_ext4fs -b 4096 -l -16384 -a /data /dev/block/mmcblk0p2 SELinux: Loaded file_contexts from /file_contexts Creating filesystem with parameters: Size: 1024188416 Block size: 4096 Blocks per group: 32768 Inodes per group: 7824 Inode size: 256 Journal blocks: 3906 Label: Blocks: 250046 Block groups: 8 Reserved block group size: 63 Created filesystem with 11/62592 inodes and 8162/250046 blocks + /tmp/buybox/umount -l /datadata /tmp/updater.sh: line 1: /tmp/buybox/umount: not found + /tmp/erase_image datadata mtd: not erasing bad block at 0x18b40000 + /tmp/busybox touch /cache/.startrecovery + /tmp/busybox test -e /sdcard/backup/efs.tar + /tmp/busybox umount -l /efs umount: can't forcibly umount /efs: No such file or directory + /tmp/erase_image efs + /tmp/busybox mkdir -p /efs + check_mount /efs /dev/block/mtdblock4 yaffs2 + /tmp/busybox grep -q /efs /proc/mounts + /tmp/busybox mkdir -p /efs + /tmp/busybox umount -l /dev/block/mtdblock4 umount: can't forcibly umount /dev/block/mtdblock4: Invalid argument + /tmp/busybox mount -t yaffs2 /dev/block/mtdblock4 /efs + cd /sdcard/backup/ + /tmp/busybox md5sum -c efs.tar.md5 efs.tar: OK + MD5RESULT=0 + /tmp/busybox test 0 + cd /efs + /tmp/busybox tar xf /sdcard/backup/efs.tar + /tmp/busybox umount -l /efs + exit 0

dont know how to attach :laugh: