can anyone make 5.1 or 6.0 ROM with orginal Samsung look and status bar and etc...

Can anyone make this ROM ....a port or some thing have every thing like Samsung ROM based on android 5.1 or 6.0 not based on 4.2 like s5 ROM or s6 rom
???? :confused:

ZTE v987 cannot mount /system etc. possible eMMC damage

Hello,
I got stuck and I need some help.
The phone is ZTE v987. There was bgcngm's ROM V4.0B0MOD inside.
I pulled-out-&-pushed-in the battery and after boot there was a prompt that my data needed to be erased. (I'm not excatly sure what it was). I freaked out. Turned off and boot into recovery mode (vol up + power). Performed factory reset and tried to restore backup. It didn't work. I got messages:

Quote:

Can't mount /system! Can't mount /data! Can't mount /cache!

So I tried to format all of the above. Then I tried to restore individually /system, /data, /cache. All the same.
When I enter the Recovery I get errors like here:

Quote:

E: Can't mount /cache/recovery/command E: Can't mount /cache/recovery/log E: Can't open /cache/recovery/log E: Can't mount /cache/recovery/last_log E: Can't open /cache/recovery/last_log

There are mentioned some apps like Heimdall but I couldn't find a version for my device and I'm not exactly sure what I should do.
What's more, I found info about eMMC damage and followed the link to check if my eMMC was good or bad.
I typed the command and the output was empty:

Quote:

adb shell ~ # dmesg | grep mmc0 dmesg | grep mmc0 ~ #

I read somewhere it's possible that I don't have grep installed (maybe because I wiped the data).
So I tried another command to list the eMMC-chip partition info:

Quote:

~ # fdisk -l /dev/block/mmcblk0 fdisk -l /dev/block/mmcblk0 Warning: ignoring extra data in partition table 5 Warning: ignoring extra data in partition table 5 Disk /dev/block/mmcblk0: 3853 MB, 3853516800 bytes 1 heads, 16 sectors/track, 470400 cylinders Units = cylinders of 16 * 512 = 8192 bytes Device Boot Start End Blocks Id System /dev/block/mmcblk0p1 65 64 2147483647+ 5 Extended Partition 1 does not end on cylinder boundary /dev/block/mmcblk0p2 1665 2944 10240 83 Linux Partition 2 does not end on cylinder boundary /dev/block/mmcblk0p3 2945 4224 10240 83 Linux Partition 3 does not end on cylinder boundary /dev/block/mmcblk0p4 5825 6592 6144 83 Linux Partition 4 does not end on cylinder boundary /dev/block/mmcblk0p5 8385 91584 665600 83 Linux /dev/block/mmcblk0p6 238785 64 2145573887+ 83 Linux ~ #

I also tried to mount /system and /data in adb but it failed:

Quote:

~ # mount /system mount /system mount: mounting /emmc@android on /system failed: Invalid argument ~ # mount /data mount /data mount: mounting /emmc@usrdata on /data failed: Invalid argument

I've also downloaded the ROM and tried to install from SD.


I've saved the log and here are bottom lines:

Quote:

Updating kernel open emmc partition "boot" contents of partition "boot" didn't match EMMC:boot:4941824:a63fb5e2f91e9c21ae76325d15d98fd3 6c50c41b:4941824:a63fb5e2f91e9c21ae76325d15d98fd36 c50c41b file "EMMC:boot:4941824:a63fb5e2f91e9c21ae76325d15d98fd 36c50c41b:4941824:a63fb5e2f91e9c21ae76325d15d98fd3 6c50c41b" doesn't have any of expected sha1 sums; checking cache failed to stat "/cache/saved.file": No such file or directory failed to load cache file Flashing partition: BOOT script aborted (no error message) script aborted (no error message) Installer Error (Status 7)

Also I've got recovery.log but it's a long one and can paste here if it is needed.

I didn't try to flash trough SP Flash Tool anything because I didn't want to make things worse.
That's all the info I could gather. I don't know if it is helpful at all but I've run out of clues.
I'd be very grateful for any help.

PS. Right now I'm not able to charge the battery. For one second the red light blinks and then the screen with battery with red strip at the bottom appears and I don't believe it's charging.