Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,812,702 Members 45,820 Now Online
XDA Developers Android and Mobile Development Forum

FIREFIREFIRE with dualboot/multiboot support

Tip us?
 
three-p-o
Old
#1  
Senior Member - OP
Thanks Meter 28
Posts: 100
Join Date: Apr 2012
Default FIREFIREFIRE with dualboot/multiboot support

Hoping someone from the dev thread
reads this. Only reason I can't post there is I am "new".

I'm running into an issue booting using the alternate boot option.
My primary boot is Stock rooted 6.3
My alternate is Pure AOKP ICS with Hashcode 3.0 Kerne

This is my partition table.
Code:
~ # parted /dev/block/mmcblk0 print
parted /dev/block/mmcblk0 print
Model: MMC MMC08G (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number  Start   End     Size    File system  Name        Flags
 1      131kB   262kB   131kB                xloader
 2      262kB   524kB   262kB                bootloader
 3      524kB   11.0MB  10.5MB               dkernel
 4      11.0MB  212MB   201MB                dfs
 5      212MB   229MB   16.8MB               recovery
 6      229MB   296MB   67.1MB  ext4         backup
 7      296MB   307MB   10.5MB               boot
 8      307MB   312MB   5243kB               splash
 9      312MB   849MB   537MB   ext4         system
10      849MB   2241MB  1392MB  ext4         userdata
11      2241MB  2369MB  128MB   ext4         cache
12      2369MB  5750MB  3381MB  fat32        media       msftres
13      5750MB  5761MB  11.0MB               boot2
14      5761MB  6298MB  537MB   ext4         system2
15      6298MB  7690MB  1392MB  ext4         userdata2
16      7690MB  7818MB  128MB   ext4         cache2
This is from my init.omap4430.rc file
Code:
on fs
    log "==  init.omap4430.rc: on fs ------------------------"
    mount ext4 /dev/block/mmcblk0p14 /system wait ro
    mount ext4 /dev/block/mmcblk0p15 /data wait noatime nosuid nodev errors=continue
    mount ext4 /dev/block/mmcblk0p16 /cache wait noatime nosuid nodev errors=continue
    mount ext4 /dev/block/mmcblk0p8 /dropbox wait noatime nosuid nodev errors=continue
And this is my update-script
Code:
format("ext4", "EMMC", "/dev/block/platform/mmci-omap-hs.1/by-name/system2", "0");
mount("ext4", "EMMC", "/dev/block/platform/mmci-omap-hs.1/by-name/system2", "/system");
......
package_extract_file("boot.img", "/dev/block/platform/mmci-omap-hs.1/by-name/boot2");
The install works fine, and everything seems to go to its correct place. But when I select the alternate boot option it sits indefinitely on the selection screen.
 
eldarerathis
Old
#2  
Senior Member
Thanks Meter 308
Posts: 154
Join Date: Jun 2010
What recovery are you using? Many people are reporting that ClockworkMod seems to have trouble with ROMs using the 3.0 kernel, making them unbootable even on a stock boot layout. TWRP doesn't have issues with it, so I would try that if you're currently using CWM.

If that's not the issue, then try using the "/dev/block/mmcblk0p#" style to specify the partitions in the updater-script. I had some difficulty getting it to play nicely with the "by-name" style for whatever reason, especially with the boot images (I'm not really sure why, though).

Got an Android question? Stop by Android Enthusiasts!
 
three-p-o
Old
#3  
Senior Member - OP
Thanks Meter 28
Posts: 100
Join Date: Apr 2012
Quote:
Originally Posted by eldarerathis View Post
What recovery are you using? Many people are reporting that ClockworkMod seems to have trouble with ROMs using the 3.0 kernel, making them unbootable even on a stock boot layout. TWRP doesn't have issues with it, so I would try that if you're currently using CWM.

If that's not the issue, then try using the "/dev/block/mmcblk0p#" style to specify the partitions in the updater-script. I had some difficulty getting it to play nicely with the "by-name" style for whatever reason, especially with the boot images (I'm not really sure why, though).
I'm used TWRP 2.0 and 2.1, neither "worked".
The rom installed, that doesn't seem to be the issue, unless I am completely off base.
I was unable to install gapps because moding its install script to goto the mmcblk0p14 caused it to fail, I think it was because it was signed, and I modded it making the md5 invalid. I need to work on that, but that shouldn't cause an issue with booting.
The only thing I can think of is that your boot2 is on p16 while mine is on p13?? would that be the issue?
 
three-p-o
Old
#4  
Senior Member - OP
Thanks Meter 28
Posts: 100
Join Date: Apr 2012
Changed to
Code:
format("ext4", "EMMC", "/dev/block/mmcblk0p14");
mount("ext4", "EMMC", "/dev/block/mmcblk0p14", "/system");
.......
package_extract_file("boot.img", "/dev/block/mmcblk0p13");
and
Code:
on fs
    mount ext4 /dev/block/mmcblk0p14 /system wait ro
    mount ext4 /dev/block/mmcblk0p15 /data wait noatime nosuid nodev errors=continue
#    mount ext4 /dev/block/platform/mmci-omap-hs.1/by-name/cache /cache wait noatime nosuid nodev errors=contin$
    mount ext4 /dev/block/mmcblk0p8 /dropbox wait noatime nosuid nodev errors=continue
This time I am trying to put the 6.3 rooted version on the alternate.
The install occurs with no issue. It just gets stuck at the Alternate Boot menu.
I'm using 0.1, not sure if there is another version of the loader.
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes