請教各位大大 android5.1.1若發生開機程序有下列的情況 這會是發生什麼事來導致的呢?

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

請教各位大大 android5.1.1若發生開機程序有下列的情況 這會是發生什麼事來導致的呢?

3,644 Views
陳冠儒
Contributor IV

Hi,All:

請教各位大大,在android5.1.1若發生開機程序有下列的情況 這會是發生什麼事來導致的呢?因為我一直停在左上角有android字樣的畫面上,卻無法進入系統內。

在麻煩大家幫忙一下了,感恩!!!

完整的訊息在附件中(.doc)以及開機停止的畫面(.jpg)。

訊息如下:  (請看紅色部份)

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): recovery complete

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): recovery complete

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

Unable to find swap-space signature

fs_mgr: swapon failed for /dev/block/zram0

init: cannot find '/system/bin/logd', disabling 'logd'

init: cannot find '/system/bin/lmkd', disabling 'lmkd'

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

rfkill: BT RF going to : off

random: init urandom read with 59 bits of entropy available

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

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

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

init: cannot find '/system/bin/debuggerd64', disabling 'debuggerd64'

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

fs_mgr: Cannot open file /fstab.

android_usb: already disabled

mtp_bind_config

root@android:/ # init: untracked pid 247 killed by signal 9

healthd: BatteryTemperaturePath not found

healthd: BatteryTechnologyPath not found

init: untracked pid 298 exited with status 0

random: nonblocking pool is initialized

init: untracked pid 324 killed by signal 9

init: untracked pid 354 killed by signal 9

init: untracked pid 382 killed by signal 9

init: untracked pid 408 killed by signal 9

init: untracked pid 435 exited with status 2

init: untracked pid 468 killed by signal 9

init: untracked pid 494 exited with status 0

init: untracked pid 526 killed by signal 9

init: untracked pid 549 killed by signal 9

init: untracked pid 576 killed by signal 9

init: untracked pid 605 killed by signal 9

init: untracked pid 631 killed by signal 9

init: untracked pid 657 killed by signal 9

init: untracked pid 683 killed by signal 9

init: untracked pid 706 killed by signal 9

init: untracked pid 730 killed by signal 9

init: untracked pid 789 killed by signal 9

init: untracked pid 815 killed by signal 9

binder: undelivered transaction 154

init: untracked pid 842 exited with status 2

init: untracked pid 871 killed by signal 9

init: untracked pid 897 killed by signal 9

init: untracked pid 921 killed by signal 9

init: untracked pid 944 killed by signal 9

init: untracked pid 971 killed by signal 9

init: untracked pid 1001 killed by signal 9

init: untracked pid 1026 killed by signal 9

init: untracked pid 1054 killed by signal 9

0 Kudos
Reply
2 Replies

2,378 Views
jimmychan
NXP TechSupport
NXP TechSupport

Would you tell me which BSP are you using?

this may help you.

https://community.nxp.com/thread/357712 

0 Kudos
Reply

2,378 Views
陳冠儒
Contributor IV

Hi,Jimmychan:

我使用的是android5.1.1的BSP(L5.1.1_2.1.0),只是build完code後開機會形成上述這樣的狀況,後來發現是build code的參數問題,因為預設下它會使用EMMC方式去build code,所以我用的是SD卡開機,故就會開機失敗,就算先做

移除 /out/target/product/sabresd_6dq/下的root 目錄跟 boot*.img.
以及移除/out/target/product/sabresd_6dq/下的recovery 目錄跟 recovery*.img.
再去build  boot.img 和 recovery.img :
make bootimage BUILD_TARGET_DEVICE=sd
make recoveryimage BUILD_TARGET_DEVICE=sd

最後再用下列指令:

make 2>&1

去整個build code,還是會出問題,一樣是開機失敗。

所以後來我採用的方式是:

1.先用這指令build code   -->    make 2>&1

2.再做移除 /out/target/product/sabresd_6dq/下的root 目錄跟 boot*.img.
以及移除/out/target/product/sabresd_6dq/下的recovery 目錄跟 recovery*.img.
再去build  boot.img 和 recovery.img :
make bootimage BUILD_TARGET_DEVICE=sd
make recoveryimage BUILD_TARGET_DEVICE=sd

然後4個(u-boot-imx6q.imx、boot-imx6q.img、system.img、recovery-imx6q.img)檔案就燒到SD卡上,結果就正常開機,那麼請教一下,那我可以一開始就設定好build code參數不用這樣麻煩嗎?

也就是 make 2>&1這指令  應該加哪種參數會比較適合build sd卡用的code呢?

再麻煩您幫忙一下了,感謝。

感恩!!!

0 Kudos
Reply