ANDROID-5.0.2 LOLLIPOP NOT BOOTED

[chandrasekharma]

I got one issue regarding booting of android - 5.0.2 lollipop in sabresd-imx6q board.

init: cannot expand '$ro.product.manufacturer' while writing to '/sys/class/android_usb/android0/iManufac'

init: using deprecated syntax for specifying property 'ro.product.model', use ${name} instead

init: property 'ro.product.model' doesn't exist while expanding '$ro.product.model'

init: cannot expand '$ro.product.model' while writing to '/sys/class/android_usb/android0/iProduct'

android_usb: already disabled

read descriptors

read strings

mtp_bind_config

binder: 147:147 transaction failed 29189, size 0-0

binder: 147:147 transaction failed 29189, size 0-0

binder: 147:147 transaction failed 29189, size 0-0

binder: 147:147 transaction failed 29189, size 0-0

binder: 147:147 transaction failed 29189, size 0-0

This binder: 147:147 transaction failed 29189, size 0-0 message keep on occur in my serial terminal but in sabresd board dispaly i didn't get anything...

help me to solve this one thanks in advance

Original Attachment has been moved to: boot-log-sabresd.txt.zip

[chandrasekharma]

Thank you igor,

Yes BSP was from Freescale Official web page. How can we enable ldo mode? Is there any patches to apply this ldo mode in SABRE SD board? Thanks in advance

[chandrasekharma]

Hi igor,

Thank you for your reply but here I flashed prebuilt images of sabresd  imx6 quad board also. But this is also give same binder issue. Here in lollipop 5.0 there is no vold.fstab file and fstab.boundary files. I checked difference between log files of them. In prebuild log partitions mounted with return 0. But in my build log file partitions mounted with failure return -1. But in both i got binder issue help thanks in advance

[igorpadykov]

could you try image with ldo_enable mode ?

Also what BSP are you using, is it from FSL i.MX6 Android official web page ?

Android OS for i.MX Applications Processors|Freescale

~igor

[chandrasekharma]

Thank yo igor,

We tried boot-imx6q-ldo.img and recovery-imx6q-ldo.img but got same binder issue. How can i solve this..?? and please find the error failed to mount file system for your reference. Thanks in advance

fs_mgr: __mount(source=/dev/block/mmcblk3p5,target=/system,type=ext4)=-1

fs_mgr: Failed to mount an un-encryptable or wiped partition on/dev/block/mmcblk3p5 at /system options: by

fs_mgr: __mount(source=/dev/block/mmcblk3p4,target=/data,type=ext4)=-1

fs_mgr: fs_mgr_mount_all(): possibly an encryptable blkdev /dev/block/mmcblk3p4 for mount /data type ext4)

fs_mgr: __mount(source=/dev/block/mmcblk3p6,target=/cache,type=ext4)=-1

fs_mgr: Failed to mount an un-encryptable or wiped partition on/dev/block/mmcblk3p6 at /cache options: noy

fs_mgr: __mount(source=/dev/block/mmcblk3p7,target=/device,type=ext4)=-1

fs_mgr: Failed to mount an un-encryptable or wiped partition on/dev/block/mmcblk3p7 at /device options: (y

init: fs_mgr_mount_all returned an error

init: fs_mgr_mount_all returned unexpected error 255

[igorpadykov]

"android - 5.0.2 lollipop" - sorry there is no such BSP on

Android OS for i.MX Applications Processors|Freescale

i.MX6Q|i.MX 6Quad Processors|Quad Core|Freescale

for ldo enable one needs to use images with *ldo* name, like

zImage--3.10.53-r0-imx6q-sabresd-ldo-20150105054653.dtb

Best regards

igor

[chandrasekharma]

Thank you igor,

We tried boot-imx6q-ldo.img and recovery-imx6q-ldo.img but got same binder issue. How can i solve this..?? and please find the error failed to mount file system for your reference. Thanks in advance

fs_mgr: __mount(source=/dev/block/mmcblk3p5,target=/system,type=ext4)=-1

fs_mgr: Failed to mount an un-encryptable or wiped partition on/dev/block/mmcblk3p5 at /system options: by

fs_mgr: __mount(source=/dev/block/mmcblk3p4,target=/data,type=ext4)=-1

fs_mgr: fs_mgr_mount_all(): possibly an encryptable blkdev /dev/block/mmcblk3p4 for mount /data type ext4)

fs_mgr: __mount(source=/dev/block/mmcblk3p6,target=/cache,type=ext4)=-1

fs_mgr: Failed to mount an un-encryptable or wiped partition on/dev/block/mmcblk3p6 at /cache options: noy

fs_mgr: __mount(source=/dev/block/mmcblk3p7,target=/device,type=ext4)=-1

fs_mgr: Failed to mount an un-encryptable or wiped partition on/dev/block/mmcblk3p7 at /device options: (y

init: fs_mgr_mount_all returned an error

init: fs_mgr_mount_all returned unexpected error 255

[igorpadykov]

please use IMX6-L500-100-ANDROID-DEMO-SD-BSP (REV L5.0.0_1.0.0)

Android OS for i.MX Applications Processors|Freescale

[igorpadykov]

Hi chandrasekhar

error may be caused by using wrong image as described on

android booting problem with binder issue on imx6 sabrelite

one can follow sect.3.3 Downloading board images attached Quick Guide

and program image using MFG Tools

Programmers (Flash, etc.) (10)

IMX-L5.0.0-MFG-TOOL (REV L5.0.0_1.0.0)

http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=i.MX6Q&nodeId=018rH3ZrDRB24A&fpsp=1&t...

Best regards

igor

-----------------------------------------------------------------------------------------------------------------------

Note: If this post answers your question, please click the Correct Answer button. Thank you!

-----------------------------------------------------------------------------------------------------------------------