[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
EDIT From the logs I see the mbtool is mounting in /raw/extsd may be that's the reason.

[MENTION=4277844]chenxiaolong[/MENTION] The r60 build fixed the sdcard corrupted on primary and data slot, but I didn't have a chance to try the extsd slot as it's giving me 5 vibrations at boot. Same result on K6000 Pro and K3 Note. Installing in twrp I also noticed the message "Failed to switch to target rom. Continuing anyway..." While on K3 Note this issue could be due to an old ramdisk version, on K6000 Pro the ramdisk is updated and working fine. Installing in twrp from usb otg if that matters, I used that combo many times without problems.

One more thing: for some reason the backup process is freezing on K6000 Pro mainly when backuping /data or cache. Can you look at the logs please? Thanks. According to the kernel log on the Oukitel, it can't mount the card with output "invalid media value ". [MENTION=4277844]chenxiaolong[/MENTION] Did you noticed that I have a fsck_msdos_mtk in /system/bin? May be this needs to be disabled also?

<7>[ 10.675318] .(0)[0:swapper/0][sd][name:sd&]Card insert<1> Block bad card<0>
<11>[ 10.677553] .(4)[1:init]mblog: /default.prop contains fuse-exfat override: false
<11>[ 10.678512] .(4)[1:init]mblog: Using fuse-exfat: 0
<11>[ 10.679217] .(4)[1:init]mblog: Failed to mount /dev/block/mmcblk1 (exfat) at /raw/extsd: No such device
<3>[ 10.680959] .(4)[1:init]FAT-fs (mmcblk1): invalid media value (0x01)
<6>[ 10.681776] .(4)[1:init]FAT-fs (mmcblk1): Can't find a valid FAT filesystem
<11>[ 10.682758] .(4)[1:init]mblog: Failed to mount /dev/block/mmcblk1 (vfat) at /raw/extsd: Invalid argument
<3>[ 10.684482] .(4)[1:init]EXT4-fs (mmcblk1): VFS: Can't find ext4 filesystem
<11>[ 10.685514] .(6)[1:init]mblog: Failed to mount /dev/block/mmcblk1 (ext4) at /raw/extsd: Invalid argument
<11>[ 10.686762] .(6)[1:init]mblog: Failed to mount /raw/extsd
<11>[ 10.687512] .(6)[1:init]mblog: Failed to mount fstab

On K3 Note I'm getting the "out of range" error. The rom I'm trying was working before, only sdcard corrupted issue, but now 5 vibrations at boot. May be I was running out of space, as only 416mb free on the extsd after /system.img was instaled? Wasn't an issue before. May be the card needs error checking as earlier today while flashing in twrp the screen timeout kicked in and then the phone rebooted lol! I disabled the screen timeout now.

<4>[ 1.894828]<1> (4)[1:init][EXFAT] sector_read: out of range error! (sec = 149727)
<5>[ 1.894925]<1> (4)[1:init]type=1400 audit(1477413509.890:3): avc: denied { mounton } for pid=1 comm="init" path="/system" dev="rootfs" ino=77 scontext=u:r:kernel:s0 tcontext=u:object_r:rootfs:s0 tclass=dir permissive=1
<5>[ 1.894971]<1> (4)[1:init]type=1400 audit(1477413509.890:4): avc: denied { sys_admin } for pid=1 comm="init" capability=21 scontext=u:r:kernel:s0 tcontext=u:r:kernel:s0 tclass=capability permissive=1
<4>[ 1.895040]<1> (4)[1:init][EXFAT] sector_read: out of range error! (sec = 149727)
<11>[ 1.895103]<1> (4)[1:init]mblog: /raw/extsd/multiboot/extsd-slot-sd4/system.img: Failed to mount image: No such file or directory
<11>[ 1.895131]<1> (4)[1:init]mblog: Failed to mount ROM directories and images