Hi, I have a mini210s module with a 4.3 touch screen. I have made a SD card with this structure : Superboot210.bin burn with SD-Flasher. Fat32 partition with : images / FriendlyARM.ini Superboot210.bin Android / rootfs_android-mlc2.img zImage All works perfectly. The system is OK. Now, I try to rebuild the Android 4.0.3 image from the rootfs. I use mkyaffs2image-mlc2 utility under Unbuntu. #./mkyaffs2image-mlc2 ./rootfs_android4.0.3/ rootfs_android-mlc2.img The new image seems to be good. I have copy the new rootfs image on my SD card and burn the mini210s. Burn have no error. At startup, from the console, the system can't load Android. This is the console logs : [ 3.012428] FIMC0 registered successfully [ 3.017105] FIMC1 registered successfully [ 3.020162] FIMC2 registered successfully [ 3.022974] S5PC1XX TVOUT Driver, (c) 2009 Samsung Electronics [ 3.029129] s5p-tvout s5p-tvout: hpd status is cable removed [ 3.040799] Freeing init memory: 1452K [ 3.048086] yaffs: dev is 32505860 name is "mtdblock4" rw [ 3.048135] yaffs: passed flags "" 1Wire touchscreen OK [ 11.967088] init: cannot find '/sbin/ueventd', disabling 'ueventd' [ 16.490577] init: Timed out waiting for /dev/.coldboot_done [ 16.854131] init: cannot execve('/system/bin/servicemanager'): Permission denied [ 16.854782] init: cannot execve('/system/bin/drmserver'): Permission denied [ 16.855667] init: cannot execve('/system/bin/surfaceflinger'): Permission denied [ 16.856245] init: cannot execve('/system/bin/mediaserver'): Permission denied [ 16.861698] init: cannot execve('/system/bin/dbus-daemon'): Permission denied [ 16.869018] init: cannot execve('/system/bin/keystore'): Permission denied [ 16.941143] init: cannot execve('/system/etc/init.mini210.sh'): No such file or directory The system seems to access to a bad directory (a bad root files system ?). I have try multiple tests but it don't work. Do you have an idea ? Thank you very much for your help. Laurent.
Android 4.0.3 mkyaffs2 image on mini210s
It seems there is something slightly wrong with your method somewhere along the line, How are you getting the rootfs in the first place? If it's by unpacking the provided rootfs, then make sure you are root when you do it, otherwise the files will be created with you as the user/group which will break android :) Examine the sd card on the ubuntu PC, ls /media/<SDrootfs>/system/bin -alh Obviously change SDrootfs to whatever the name of your rootfs partition is on the SD card.
Hi, Thank you very much. I have unzip the rootfs on Windows and user/group is bad. Now, I have untar the rootfs directly on Linux (with root) and it's work.