Android showing "first run" screen on every boot

[mukelarvin]

I have a board booting into Android but it is showing the "Make yourself at home" welcome page on every boot. Could someone help me figure out why?

It is a custom iMX6DL board based on the RIoTboard using their Android 4.4.2 distribution. (imx-manifest/embest_android_kk4.4.2_1.0.0 at master · embest-tech/imx-manifest · GitHub)

I'm booting from a usd card with a 4-bit connection on SD3.

Here's a paste showing the boot log, mount, dmesg, fstab, and an ls of the root.

Boot, mount, dmesg, fstab, ls - Pastebin.com

One thing I'm not sure about is the first line of the fstab, is this for mounting an additional external SD card? This shouldn't be my boot sd card right? It didn't seem to matter either way.

/devices/platform/sdhci-esdhc-imx.2/mmc_host/mmc0 /mnt/media_rw/extsd vfat defaults voldmanaged=extsd:auto

Another suspicious thing is that I can't access /sdcard it just says:

root@RIoTboard_6solo:/ # cd sdcard

/system/bin/sh: cd: /sdcard: No such file or directory

Happy New Year.

[CarlosCasillas]

Hi Luke,

For RIoT board related questions, you could post your threads on the RIoT space:
RIoTboard

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

[mukelarvin · Accepted solution]

The RIoTboard forum is a bit too user-focused for this kind of problem.  We've made a relatively bare-bones IMX6DL board using the RIoTboard and the IMX6Rex (REX - Freescale i.MX6 - Open Source, FREE Schematic & PCB) as design references. Our internal codename for the board is RiotRex. It's catchy. :smileycool:

The good news is that we solved the problem. Here's the solution in case anyone else runs into the same situation. An incorrectly stuffed resistor was keeping the uSD card's Write Protect pin high.

Selection from dmesg with Write Protect Low (correct):

<7>SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts
<6>EXT4-fs (mmcblk0p5): mounted filesystem with ordered data mode. Opts: (null)
<7>SELinux: initialized (dev mmcblk0p5, type ext4), uses xattr
<6>EXT4-fs (mmcblk0p4): recovery complete
<6>EXT4-fs (mmcblk0p4): mounted filesystem with ordered data mode. Opts: nomblk_io_submit,noauto_da_alloc,errors=panic
<7>SELinux: initialized (dev mmcblk0p4, type ext4), uses xattr
<6>EXT4-fs (mmcblk0p6): recovery complete
<6>EXT4-fs (mmcblk0p6): mounted filesystem with ordered data mode. Opts: nomblk_io_submit
<7>SELinux: initialized (dev mmcblk0p6, type ext4), uses xattr
<6>EXT4-fs (mmcblk0p7): mounted filesystem with ordered data mode. Opts: (null)
<7>SELinux: initialized (dev mmcblk0p7, type ext4), uses xattr
<3>init: /dev/hw_random not found
<5>type=1400 audit(87357.949:4): avc:  denied  { entrypoint } for  pid=2147 comm="init" path="/sbin/healthd" dev=rootfs ino=1422 scontext=u:r:healthd:s0 tcontext=u:object_r:rootfs:s0 tclass=file
<3>init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'

Selection from dmesg with Write Protect High (incorrect):

<7>SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts
<6>EXT4-fs (mmcblk0p5): mounted filesystem with ordered data mode. Opts: (null)
<7>SELinux: initialized (dev mmcblk0p5, type ext4), uses xattr
<7>SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
<3>fs_mgr: Cannot mount filesystem on /dev/block/mmcblk0p6 at /cache
<3>init: fs_mgr_mount_all returned an error
<3>init: /dev/hw_random not found
<5>type=1400 audit(86448.340:4): avc:  denied  { entrypoint } for  pid=2127 comm="init" path="/sbin/healthd" dev=rootfs ino=1428 scontext=u:r:healthd:s0 tcontext=u:object_r:rootfs:s0 tclass=file
<3>init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'