• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Dual Boot

maximumhax

maximumhax

Newbie
Ok, I had an idea. The app boot manager allows some phones to boot multiple roms. My take of this is that it installs the roms on SD cards in their own folder, modifies your original boot.img to boot the rom on the SD card in foobar directory. Then if you want to boot another rom, it modifies your original boot.img again and flashes it to your phone so when you boot up it boots the modified boot.img to boot from the SD card.

Triumph can't use this boot manager app because our boot.img can only be replaced in "download mode" (VOL DOWN + PWR) and replace the boot.img and reboot again. The app "boot manager" can't do this. So my idea was that there is the ideos x6 touch recovery menu that allows you to select Stock recovery, CWM recovery touch, reboot, and shutdown.. which the touch recovery boots and some things work, but flashing a rom doesn't work for me.. anyways back on track..

Why not have an app that we copy our boot.img into sd card manually.. let an app modify it.. and we rename it boot-rom1.img ... boot-rom2.img.. etc.. then copy all the boot.img's to the boot loader manually.. and have a custom recovery where you can select.. CWMk recovery, rom1, rom2, rom3, reboot, etc..?? if you select rom1 then boot phone normally using boot.img...

if you select rom2 use boot-rom2.img that you already placed manually in boot loader..

now obviously the setting up part would be all manual, but after it's setup I could boot CM9, CM7 just by rebooting into recovery and selecting rom2 or rom1 etc...
 
We flash boot.img's and recovery.img's through recovery all the time. Its really easy. And the kernel boot.img isn't in the same one as the recovery.img that you do in download mode. Our kernels get flashed to mmcblk0p5, and the recovery.img (and a boot.img as well but this is not where you wanna change it at, I believe this is just a backup of the stock kernel) is in mmcblk0p1 which is a FAT formatted partition and it is what gets mounted as MOBILE in download mode.

Now to flash a kernel through recovery in a zip file you simply have the I install script extract the boot.img to mmcblk0p5.

To flash a recovery.img in recovery you make a zip for it and have it mount mmcblk0p1 as /sd-ext as a FAT partition, then extract the recovery.img to /sd-ext/image.

You can look at the install scripts for the kernel and recovery in the flashable zips in the forums for recoveries and kernels
 
Is there anyway to mount mmcblk0p5 within android. Or can I connect via USB to access and mount it within Linux? I see it is partition type 48 or I think that's what it was. Thanks for your help.
 
Ok well here is what I did..

This failed btw...

Copied boot.img from cm7 reloaded rom zip to bootmanager/phonerom since boot manager failed doing so

Opened bootmanager to rom1 and installed codename android rom to it..

Took the boot.img from rom1 and made a flashable zip since bootmanager fails to flash the boot.img as our boot loader is locked

Made a flashable zip of cm7 reloaded boot.img so I can flash it back when I want to boot into cm7

Flashed the zip containing the modified boot.img from rom1 hoping to reboot into rom1 (codename android)

Rebooted and got a battery icon that looked low on power and red half moons on each side. Nothing else happened.

Rebooted back to recovery and flashed the cm7 boot.img to reboot back into cm7.

Rebooted and here I am back on cm7..

What did I do wrong?

EDIT: Is the boot.img suppose to be the entire boot partition or just the boot.img in the boot partition? Maybe this is where I went wrong.
 
You must log in or register to reply here.
Back
Top Bottom