Froyo Dual-Boot - Leshak & CM

[Xmister]

Why is it limited to leshak`s froyo now?
According to the process it should be unified...

Yes, but for some reason CyanogenMod didn't start for me. Of course you can always try it out yourself

Dont you think that having image on fat32 would couse fs errors if device wont be shut down properly?

Because the system partition is not written, it should be fine. And the data partition will use an ext4 image, which has journaling.
And if any error occurs on system, you just need, to copy it again to your sd card

[ch33kybutt]

If someone wants to help, tell me why my script in /etc/init.d isn't executed at boot? If I run it from console, it works beautifully.

Answer to why your /etc/init.d scripts are not running at boot may be in XDA forum HERE and my post HERE

[Xmister]

Answer to why your /etc/init.d scripts are not running at boot may be in XDA forum HERE and my post HERE

Hmm, thanks, I will try it tonight

[DE_NISKA]

i have a problem with dual boot.
vold cannot mount fat partition when android booted from sd. so apps cannot access sdcard and connection to pc dont work

[Xmister]

i have a problem with dual boot.
vold cannot mount fat partition when android booted from sd. so apps cannot access sdcard and connection to pc dont work

SD card is always mounted, as the system files are on it, that's why you couldn't use pc mount(the system needs to be mounted all the time), but apps should have access to SD card...although I didn't try it yet, but I will soon. Exactly what app did you try?

[bboylalu]

Xmister, I think the dual boot is a brilliant idea. As something helpful (hopefully I'm not just spamming in the dev's section, as I hate people who do that), wouldn't it be a nice solution to make an app which modifies the boot script (after you manage to get over it) to run either FroYo or Eclair at the next boot? Say you once click on the app and a dialog box opens, asking you if you want to switch to the other OS version (if you're on FroYo it will boot Eclair next time and vice versa).

[rightstyle]

Xmister, I think the dual boot is a brilliant idea. As something helpful (hopefully I'm not just spamming in the dev's section, as I hate people who do that), wouldn't it be a nice solution to make an app which modifies the boot script (after you manage to get over it) to run either FroYo or Eclair at the next boot? Say you once click on the app and a dialog box opens, asking you if you want to switch to the other OS version (if you're on FroYo it will boot Eclair next time and vice versa).

its not that easy, the bootscript is in the kernel initramfs and to change it you would have to change kernel... One way would be to make the init.sh in the initramfs minimal and let it start the rest of the init.sh from the /system partition.

[Xmister]

Xmister, I think the dual boot is a brilliant idea. As something helpful (hopefully I'm not just spamming in the dev's section, as I hate people who do that), wouldn't it be a nice solution to make an app which modifies the boot script (after you manage to get over it) to run either FroYo or Eclair at the next boot? Say you once click on the app and a dialog box opens, asking you if you want to switch to the other OS version (if you're on FroYo it will boot Eclair next time and vice versa).

Of course it would be nice, but sadly we can't modify initramfs(which takes care of the boot process after the kernel core loaded) without flashing a new kernel. So it's not possible.

---------- Post added at 01:40 AM ---------- Previous post was at 01:27 AM ----------

its not that easy, the bootscript is in the kernel initramfs and to change it you would have to change kernel... One way would be to make the init.sh in the initramfs minimal and let it start the rest of the init.sh from the /system partition.

It will be one way IF our init.rc would support include, but sadly it isn't.

[rightstyle]

Of course it would be nice, but sadly we can't modify initramfs(which takes care of the boot process after the kernel core loaded) without flashing a new kernel. So it's not possible.

---------- Post added at 01:40 AM ---------- Previous post was at 01:27 AM ----------



It will be one way IF our init.rc would support include, but sadly it isn't.

Iam pretty sure that ive seen init.rc files that use the import command? Maybe its for a specific version of android, i dont know. A alternative would be to use the exec command instead and start a command/script that does the mounting.

[Xmister]

Iam pretty sure that ive seen init.rc files that use the import command? Maybe its for a specific version of android, i dont know. A alternative would be to use the exec command instead and start a command/script that does the mounting.

That's the other thing what our init doesn't support. Thank to Samsung that they gave us such useless init...


---------- Post added at 03:38 PM ---------- Previous post was at 03:35 PM ----------

Answer to why your /etc/init.d scripts are not running at boot may be in XDA forum HERE and my post HERE

This way didn't help, but my idea did.

service sysinit /xbin/busybox run-parts /mnt/sdcard/system/etc/init.d
    oneshot

Otherwise the scripts didn't start at all. And yes, this starts the scripts concurrently, but I had to do this, because I needed to mount /data early. So I moved and rewroteall the
data specific lines of init.rc to the shell script.


----------------

V2 released with loop mounted data image -> Your settings will be saved between reboots.