Booting Android on the BeagleBone Black not working?

Run it from DC. Not USB. At least 1.5A.

Gerald

Hi I am also not able to boot the TI image, it is showing 2 led blink for some time after all led are blank. Can you let me know how you solved the problem?

Hi Andrew

I just got the BBB and wanted to run Android according to your description found on the forum. I have the problem that the boot process stops after some time (see listing below). I have configured the flash card with the image provided (BBB_JB_Android_3_8_13.img) and powered with external power supply as indicated. Below is the log on the serial terminal output. The boot process stops with the last message “[ 46.255879] init: sys_prop: permission denied uid:1003 name:service.bootanim.exit”
Do you have any advice, what may be the reason for this error?
Thanks anyway for the good description in your posts.
Regards,
Viktor

Log output:

[ 2.918519] davinci_mdio 4a101000.mdio: phy[0]: device 4a101000.mdio:00, driver SMSC LAN8710/LAN8720
[ 2.928396] Detected MACID = 90:59:af:63:ef:48
[ 2.933108] cpsw 4a100000.ethernet: NAPI disabled
[ 2.940251] omap_rtc 44e3e000.rtc: setting system clock to 2000-01-01 00:50:49 UTC (946687849)
[ 3.001621] tilcdc 4830e000.fb: timeout waiting for framedone
[ 3.019644] ALSA device list:
[ 3.022816] #0: TI BeagleBone Black
[ 3.589086] EXT4-fs (mmcblk0p2): recovery complete
[ 3.597328] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[ 3.605891] VFS: Mounted root (ext4 filesystem) on device 179:2.
[ 3.613893] devtmpfs: mounted
[ 3.617440] Freeing init memory: 292K
[ 3.657250] init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj instead.
[ 3.791028] init: cannot open ‘/initlogo.rle’
[ 4.533885] EXT4-fs (mmcblk0p3): recovery complete
[ 4.543675] EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: nomblk_io_submit,errors=panic
[ 4.580991] init: cannot find ‘/system/bin/sgx/rc.pvr’, disabling ‘pvr’
[ 4.599927] init: cannot find ‘/system/etc/install-recovery.sh’, disabling ‘flash_recovery’
[ 4.836830] init: untracked pid 100 exited
root@android:/ # [ 24.376216] warning: `zygote’ uses 32-bit capabilities (legacy support in use)
[ 36.043718] net eth0: initializing cpsw version 1.12 (0)
[ 36.051757] net eth0: phy found : id is : 0x7c0f1
[ 36.066149] libphy: PHY 4a101000.mdio:01 not found
[ 36.071281] net eth0: phy 4a101000.mdio:01 not found on slave 1
[ 36.083857] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 39.127327] libphy: 4a101000.mdio:00 - Link is Up - 100/Full
[ 39.136471] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 46.255879] init: sys_prop: permission denied uid:1003 name:service.bootanim.exit

Hello
Have you got the solution for this problem?

Hi Jain,

I am newbie to BBB platform. I am also facing same issue what you faced. I done following things my android image was not boot up from sdcard please please help me to solve this issue.

  1. I have beagle bone black
  2. I flashed android images to sdcard my using below command
    sudo dd if=bb.img of=/dev/sdx
  3. Inserted sdcard to bbb
  4. Before powering on device pressed boot button(Near to micro sdcard S2 switch) some sceonds
  5. But i didn’t see any leds are lighting while booting, i am facing this issue from last 2 days.

Please provide proper android image and steps to bring up bbb android please help me.

I connected to bbb 5v power supply and usb from bbb to Ubuntu PC.

Actually mine there is no problem only thing is in android image led indicators will not work if you still have doubts you can connect he I and check or use serial to sub cable and see o/p.

Note: you can use your arduino uno as serial cable. I used it for my bbb debugging.

Seems what worked for me was to NOT hold down the boot button prior to connecting power. In fact, I had to plug in power, and then very quickly (before normal boot process begins, which is indicated by flashing of the indicator LEDs) I held down the boot button for several seconds, at which time the LEDs all came on solid for 2-3 seconds, then turned off; at which time I released the boot button, and the flashing process began (as indicated by LEDs flashing, but not in the heartbeat pattern). Hope this helps!

-Darryl