I'm using VAR-SOM-DUAL with SoloCustomBoard and a custom board. When I flash both Android 5 or 6 on the SOM board from devkit to play with SoloCustomBoard, flashing step seems to work well as Android boots.
I flashed Android 5 with the recovery image (v51) on SOM board from factory (with custom board). Android started with glitches on screen.
After, I flashed Android 6 (v70). Now, Android stop booting with following errors :
Code: Select all
init: write_file: Unable to open '/proc/sys/kernel/sched_tunable_scaling': No such file or directory
init: write_file: Unable to open '/proc/sys/kernel/sched_latency_ns': No such file or directory
init: write_file: Unable to open '/proc/sys/kernel/sched_wakeup_granularity_ns': No such file or directory
init: write_file: Unable to open '/proc/sys/kernel/sched_compat_yield': No such file or directory
init: write_file: Unable to write to '/dev/cpuctl/cpu.shares': Invalid argument
init: write_file: Unable to open '/proc/sys/abi/swp': No such file or directory
init: /dev/hw_random not found
init: FSTAB: using file: /fstab.freescale
fs_mgr: Failed to mount an un-encryptable or wiped partition on/dev/block/mmcblk1p5 at /system options: barrier=1 error: No such file or directory
fs_mgr: fs_mgr_mount_all(): possibly an encryptable blkdev /dev/block/mmcblk1p4 for mount /data type ext4 )
When I try to flash recovery image Android 5 (v51) on factory SOM, I get the message
Code: Select all
sfdisk error #1! Partition is locked
please reboot to unlock and try again
1 - How can I unlock partition ?
2 - The devkit SOM board has 4 GB of eMMC while factory SOM board has 8 GB eMMC. Do I have to change partition size ?