android-L5.0.2 boot problem?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

android-L5.0.2 boot problem?

4,656 Views
mrleo
Contributor IV

Hi,all

android L5.0.2 system  build in my vmware ubuntu 12.04 LTS.

I met a android-L5.0.2 boot problem in my custom imx6dl board?

It is boot in sdhc0.

Using android_L5.0.0_1.0.0-ga_tools mfgtool burning.

 

I  have not found the solution to the issues?

 

the logcat messages is below:

 

Freeing unused kernel memory: 340K (80e74000 - 80ec9000)                
type=1403 audit(1.710:2): policy loaded auid=4294967295 ses=4294967295  

type=1404 audit(1.720:3): enforcing=1 old_enforcing=0 auid=4294967295 ses=42945

init: /dev/hw_random not found                                          
Console: switching to colour dummy device 80x30                         
init: /dev/hw_random not found                                          
device-mapper: table: 254:0: verity: Data device lookup failed          
device-mapper: ioctl: error adding target to table                      

fs_mgr: Error loading verity table (No such file or directory)fs_mgr: Could no!

EXT4-fs (mmcblk0p4): Ignoring removed nomblk_io_submit option           

EXT4-fs (mmcblk0p4): mounted filesystem with ordered data mode. Opts: nomblk_ic

fs_mgr: __mount(source=/dev/block/mmcblk0p4,target=/data,type=ext4)=0   
EXT4-fs (mmcblk0p6): Ignoring removed nomblk_io_submit option           

EXT4-fs (mmcblk0p6): mounted filesystem with ordered data mode. Opts: nomblk_it

fs_mgr: __mount(source=/dev/block/mmcblk0p6,target=/cache,type=ext4)=0  

EXT4-fs (mmcblk0p7): mounted filesystem with ordered data mode. Opts: (null) 

fs_mgr: __mount(source=/dev/block/mmcblk0p7,target=/device,type=ext4)=0 
init: cannot find '/system/bin/logd', disabling 'logd'                  
init: cannot find '/system/bin/lmkd', disabling 'lmkd'                  
binder: 108:108 transaction failed 29189, size 0-0                      
init: cannot find '/system/bin/servicemanager', disabling 'servicemanager'
init: cannot find '/system/bin/vold', disabling 'vold'                  
init: cannot find '/system/bin/surfaceflinger', disabling 'surfaceflinger'

init: using deprecated syntax for specifying property 'ro.serialno', use ${namd

init: using deprecated syntax for specifying property 'ro.product.manufacturerd

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

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

init: using deprecated syntax for specifying property 'ro.product.model', use d

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

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

init: cannot find '/system/bin/netd', disabling 'netd'                  
init: cannot find '/system/bin/debuggerd', disabling 'debuggerd'        
init: cannot find '/system/bin/debuggerd64', disabling 'debuggerd64'    
init: cannot find '/system/bin/drmserver', disabling 'drm'              
init: cannot find '/system/bin/mediaserver', disabling 'media'          
init: cannot find '/system/bin/installd', disabling 'installd'          

init: cannot find '/system/bin/install-recovery.sh', disabling 'flash_recovery'

init: cannot find '/system/bin/keystore', disabling 'keystore'          
init: cannot find '/system/bin/rild', disabling 'ril-daemon'            
init: cannot find '/system/bin/app_process', disabling 'zygote'         
init: cannot find '/system/bin/sh', disabling 'wifi_mac'                
init: cannot find '/system/bin/sdcard', disabling 'sdcard'              
init: cannot find '/system/bin/magd', disabling 'magd'                  
android_usb: already disabled                                           
mtp_bind_config                                                         
binder: 108:108 transaction failed 29189, size 0-0
Who met this issuse? Or Anyone can  give me some advices to solve the problem?

The detail logcat message see attachment.

 

Thanks all,             

 

Leo            

Original Attachment has been moved to: log.txt.zip

0 Kudos
5 Replies

1,108 Views
mrleo
Contributor IV

Hi Carlos,

     I try your method,but my bootimge must rebuild in my custom board. so I use android_L5.0.0_1.0.0-ga_images_6qsabresd.tar.gz system.img.

    And the same error with me.

   But I also thank you for your advice?

Thanks,

Leo

0 Kudos

1,108 Views
mrleo
Contributor IV

HI,

yes,I use a Freescale BSP,android_L5.0.0_1.0.0-ga_core_source.gz.

How to solve this issues?

Thanks,

Leo

0 Kudos

1,108 Views
CarlosCasillas
NXP Employee
NXP Employee

Hi,

It seems to be some confusion. Are you using mfgtool from Android 5.0.0_1.0.0-ga package to download a compiled image from Android 5.0.2?

The latest Android release provided by Freescale for i.MX6 series is L5.0.0_1.0.0, so, could you please verify if the mentioned error also happens when booting a precompiled image from the following package:

android_L5.0.0_1.0.0-ga_images_6qsabresd.tar.gz


Hope this will be useful for you.
Best regards!
/Carlos

0 Kudos

1,108 Views
mrleo
Contributor IV

Hi all,

I found uboot should add  bootargs environment: androidboot.selinux=disabled androidboot.dm_verity=disabled.

It will be boot success.

I don't know why?

Thanks,

Leo

0 Kudos

1,108 Views
CarlosCasillas
NXP Employee
NXP Employee

Hi,

Are you using a Freescale BSP? Otherwise, the issue that you described may be caused by the following:

Validating SELinux | Android Open Source Project

Hope this will be useful for you.
Best regards!
/Carlos

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

0 Kudos