binder error after booting with image Lollipup v5.1.1

[vikaskolapudi]

Hi All,

I have downloaded Android Lollipup v5.1.1 for i.MX6 Sololite, and flashed it  on to the card and booted, I observed that some binder is failing.

PFA by name error_after_booting.jpg, and while flashing the card it says /dev/sdb5 is not a block special device  PFA  by name while_flashing.png.

This issue is not seen while flashing with Android 4.4.3 earlier.

Please help me to proceed further.

Thanks and Regards,

Joseph vikas.

[vikaskolapudi]

Please find the image for the above post in which command line is not accessible.

Thanks & Regards,

Joseph Vikas.

[aravinthkumarja]

Hi vikas,

System image is not mounted.

This is my log:

Below 2 line is not coming in your log.

EXT4-fs (mmcblk3p5): mounted filesystem with ordered data mode. Opts: barrier=1
fs_mgr: __mount(source=/dev/block/mmcblk3p5,target=/system,type=ext4)=0
EXT4-fs (mmcblk3p4): Ignoring removed nomblk_io_submit option
EXT4-fs (mmcblk3p4): mounted filesystem with ordered data mode. Opts: nomblk_io_submit,noauto_da_alloc,errors=panic
fs_mgr: __mount(source=/dev/block/mmcblk3p4,target=/data,type=ext4)=0
EXT4-fs (mmcblk3p6): Ignoring removed nomblk_io_submit option
EXT4-fs (mmcblk3p6): mounted filesystem with ordered data mode. Opts: nomblk_io_submit
fs_mgr: __mount(source=/dev/block/mmcblk3p6,target=/cache,type=ext4)=0
EXT4-fs (mmcblk3p7): mounted filesystem with ordered data mode. Opts: (null)
fs_mgr: __mount(source=/dev/block/mmcblk3p7,target=/device,type=ext4)=0
init: Starting service 'logd'...

Hope above information is helpful for you!

Regards,

Aravinth

[vikaskolapudi]

Hi All,

I have generated binaries by building the android lollipup source v5.1.1. When I flashed them on to sd card and booted, I
can get access to GUI, but I am unable to access command line. I have tried the prebuilt images also which resulted the same.
I am using MFG tool to flash the images on to the sd card.

Please help me to move forward.

Thanks and Regards,
Joseph Vikas.