[Defy Android Development] N34S:
multiboot 0.5.5 fail several times. 1st i have rebooted CM9 when I booted it successfully (so slow), and it gives me background error screen, and this errors :

04-21 19:50:40.921: D/MULTIBOOT(2194): patching init.rc...
04-21 19:50:50.913: D/MULTIBOOT(2852): Loading environment...
04-21 19:50:50.929: I/MULTIBOOT(2856): Patching devtree...
04-21 19:50:50.937: A/libc(2857): Fatal signal 13 (SIGPIPE) at 0x00000b29 (code=0)
04-21 19:50:50.937: D/MULTIBOOT(2859): Setting up loop-devices...
04-21 19:50:50.944: A/libc(2860): Fatal signal 13 (SIGPIPE) at 0x00000b2c (code=0)
04-21 19:50:50.968: D/MULTIBOOT(2865): Replacing partition /dev/block/mmcblk1p1 with loop8 with image '/multiboot/.nand/mmcblk1p1.img'...
04-21 19:50:50.976: A/libc(2866): Fatal signal 13 (SIGPIPE) at 0x00000b32 (code=0)
04-21 19:50:50.976: D/MULTIBOOT(2868): replace node...
04-21 19:50:50.983: A/libc(2869): Fatal signal 13 (SIGPIPE) at 0x00000b35 (code=0)
04-21 19:50:50.999: E/MULTIBOOT(2872): Error: 127
04-21 19:50:51.007: A/libc(2873): Fatal signal 13 (SIGPIPE) at 0x00000b39 (code=0)
04-21 19:50:51.390: I/ARMAssembler(2876): generated scanline__00000077:03545405_00000000_00000000 [ 36 ipp] (50 ins) at [0x407511e8:0x407512b0] in 213623 ns
04-21 19:50:51.460: I/ARMAssembler(2876): generated scanline__00000077:03545405_00000A05_00000000 [ 37 ipp] (58 ins) at [0x407512b8:0x407513a0] in 152588 ns
04-21 19:50:51.640: I/ARMAssembler(2876): generated scanline__00000077:03545405_00000A08_00000000 [ 37 ipp] (59 ins) at [0x407513a8:0x40751494] in 152588 ns

retrying for 2nd time, and i am stuck to bootanimation, it takes lot of time, continues to repeat this with no progress :

04-21 20:27:05.351: W/IMediaDeathNotifier(3459): Media player service not published, waiting...
04-21 20:27:05.851: I/ServiceManager(3459): Waiting for service media.player...
04-21 20:27:05.937: I/ServiceManager(3459): Waiting for service media.audio_policy...
04-21 20:27:06.851: I/ServiceManager(3459): Waiting for service media.player...
04-21 20:27:06.937: W/AudioSystem(3459): AudioPolicyService not published, waiting...
04-21 20:27:07.437: I/ServiceManager(3459): Waiting for service media.audio_policy...
04-21 20:27:07.851: I/ServiceManager(3459): Waiting for service media.player...
04-21 20:27:08.437: I/ServiceManager(3459): Waiting for service media.audio_policy...
04-21 20:27:08.851: I/ServiceManager(3459): Waiting for service media.player...
04-21 20:27:09.437: I/ServiceManager(3459): Waiting for service media.audio_policy...
04-21 20:27:09.851: I/ServiceManager(3459): Waiting for service media.player...
04-21 20:27:10.437: I/ServiceManager(3459): Waiting for service media.audio_policy...

retrying for the 3rd time, it is restarted by itself ...

retrying for the 4th time, yeah! has started! ...

... no, restarted itself, just when I saw the lockscreen. now no longer receiving anything from the log. it takes a lot of time and is locked on bootanimation.

retrying for the 5th time, it booted successfully, here the warn log.

I would not say obscenities about the 0.5 release of the multi-boot, but I feel compelled to reject it, for the moment. I had to restart it many times before it can restart. All this patching makes multiboot slow and unlikely to use. I would prefer to to start only a ROM in multiboot rather than not being able to exploit as desired.