hi, all, I am trying to boot Android on N810 directly. I have done following things:
1. partition my MMC into 4 parts (each with 500M bytes): the first is for VFAT, second for Android m5 file system, third for a copy of the maemo root file system, the last for Android m3 file system. I want to try boot into the m3 partition before trying to boot into the m5 partition. I tried to boot into the maemo part and everything is ok. Before trying android things, I flash the kernel with the "--set-rd- flags=no-lifeguard-reset" option (is this necessary?). 2. start maemo normally, and then start Android m3 file system by chrooting into it. Android starts and runs quite well. This means that my m3 file system is ok. 3. modify the "bootmenu.sh" file in maemo's init_flasher (ref http://maemo.org/community/wiki/Flasher_tool_usage/) package to add boot options for my android and maemo-copy partitions, and then re- flash. 4. reboot N810 and try to boot into m3 partition. I found N810 hangs, with the Nokia logo shown. 5. to investigate what is wrong in the boot process, I modified the file "linuxrc" (in file initfs.osso-RX-44.2007-44.tgz), adding several "print" like commands in order to trace which command results in the block. 6. after reboot, I found "chroot <root_of_m3_filesystem> /sbin/init" blocked. 7. To know further what makes init hang, I modify the linuxrc file again and save all info in file /dev/log/main in m3 system to a file (and even save strace info to flash by "/strace -ff -F -tt -s 200 -o / strace.log /init &"). Unfortunately Android hangs again after reboot. I checked the log and found following report: [EMAIL PROTECTED]::detach [EMAIL PROTECTED]: waiting for service SurfaceFlinger >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<< [EMAIL PROTECTED]: unable to find service SurfaceFlinger [EMAIL PROTECTED] waiting for surface flinger... [EMAIL PROTECTED]: unable to find service SurfaceFlinger [EMAIL PROTECTED] waiting for surface flinger... [EMAIL PROTECTED]: unable to find service SurfaceFlinger [EMAIL PROTECTED] waiting for surface flinger... I viewed strace info for process 1045, and found following things: 00:00:33.730804 execve("/system/bin/app_process", ["/system/bin/ app_process", "-Xzygote", "/system/bin", "--zygote"], [/* 8 vars */]) = 0 ...... 00:00:34.596466 open("/system/lib/libpixelflinger.so", O_RDONLY| O_LARGEFILE) = 3 ...... 00:00:35.235321 writev(3, [{"\3", 1}, {"AndroidRuntime\0", 15}, {"\n>>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<< ...... 00:00:38.631774 bind(12, {sa_family=AF_FILE, [EMAIL PROTECTED], 17) = 0 ...... 00:00:40.960723 open("/system/usr/share/zoneinfo/zoneinfo.dat", O_RDONLY|O_LARGEFILE) = 15 00:00:40.962341 lseek(15, 0, SEEK_CUR) = 0 00:00:40.962890 lseek(15, 126128, SEEK_SET) = 126128 00:00:40.963470 read(15, "TZif \0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0\1\0\0\0\4\0\0 00:00:40.966217 close(15) = 0 00:00:40.966979 close(14) = 0 00:00:40.973632 mprotect(0x4108e000, 8192, PROT_READ|PROT_WRITE) = 0 00:00:40.998413 brk(0xec000) = 0xec000 00:00:41.017150 brk(0x104000) = 0x104000 00:00:41.026580 --- SIGBUS (Bus error) @ 0 (0) --- 00:00:41.027282 sigaction(SIGUSR1, {SIG_IGN}, {SIG_DFL}, 0) = 0 00:00:41.028167 gettid() = 1045 00:00:41.028625 socket(PF_FILE, SOCK_STREAM, 0) = 14 00:00:41.029205 connect(14, {sa_family=AF_FILE, [EMAIL PROTECTED]:debuggerd}, 20) = 0 00:00:41.032104 write(14, "\25\4\0\0", 4) = 4 00:00:41.033111 read(14, 0xbebc34c4, 1) = ? ERESTARTSYS (To be restarted) 00:00:41.044708 +++ killed by SIGKILL +++ The problems are: 1) booting into the m3 file system is also done thru "chroot" (by initfs code), which is similar to chroot from maemo. But the result is quite different. what reason? Does maemo do something special in init? 2) why process "app_process" receives a SIGKILL signal? (I checked this several times and this always remains)?who sends the signal? Does anybody know the answer? or did anyone BOOT into Android m3 or m5 file system successfully, and how did you do it? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Internals" group. To post to this group, send email to android-internals@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-internals?hl=en -~----------~----~----~----~------~----~------~--~---
