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

Root [Boost Mobile] Dual boot

deathtrap8675 said:
How complicated would it be to make a script that would move the contents of /system to a clone folder of a different name, leaving the system folder open for another Rom?
Click to expand...

Hmmm... Not very... Its plausible actually... Write an updater script that moves the contents of /data, /system, and /cache and kernel to the sdcard and replaces it with a second set of /folders already located on the sdcard... But honestly... Its basicly the same thing as backup and restore...
 
Ah!!! I think I have an idea... Partition the sdcard with an ext4 partition to allow symlinks (a big one at that... Least a few gbs)... Move your current roms partitions to it... (/cache, /data, /system, kernel)... Flash another ROM... Write a script that recursively hides all files and folders on the newly installed rom by adding a "." In front of them... Then recursively symlink every file of the original ROM that's located on the sdcard into the current partitions (again that's /cache, /system, and /data)... Swap kernels through normal methods within the script... Bam! Dual boot!!! And of course to switch ROMs you'd have to create a script that reverses the process... By doing it this way there is 100% no moving around files... So it wouldn't take very long to do... Only renaming and symlinking... However... No USB mounting through the ROM on the sdcard... Since its located on the sdcard :banghead::banghead::banghead: also I'd imagine that you'd need a fast sdcard... Very fast... Also this assumes that by adding a "." In front of file names on the partitions that it prevents them from being read as if in normal startup... Maybe it'll work... Maybe it won't... Just brainstorming *shrugs shoulders*
 
jetx2x said:
Ah!!! I think I have an idea... Partition the sdcard with an ext4 partition to allow symlinks (a big one at that... Least a few gbs)... Move your current roms partitions to it... (/cache, /data, /system, kernel)... Flash another ROM... Write a script that recursively hides all files and folders on the newly installed rom by adding a "." In front of them... Then recursively symlink every file of the original ROM that's located on the sdcard into the current partitions (again that's /cache, /system, and /data)... Swap kernels through normal methods within the script... Bam! Dual boot!!! And of course to switch ROMs you'd have to create a script that reverses the process... By doing it this way there is 100% no moving around files... So it wouldn't take very long to do... Only renaming and symlinking... However... No USB mounting through the ROM on the sdcard... Since its located on the sdcard :banghead::banghead::banghead: also I'd imagine that you'd need a fast sdcard... Very fast... Also this assumes that by adding a "." In front of file names on the partitions that it prevents them from being read as if in normal startup... Maybe it'll work... Maybe it won't... Just brainstorming *shrugs shoulders*
Click to expand...

Well, hey, sounds like we're at least getting somewhere lol

If there was a way to successfully set up Code::Blocks to compile Android binaries (as are found in /system/bin, not what goes inside an APK) I might be able to look into this.
 
mercury0x000d said:
Well, hey, sounds like we're at least getting somewhere lol

If there was a way to successfully set up Code::Blocks to compile Android binaries (as are found in /system/bin, not what goes inside an APK) I might be able to look into this.
Click to expand...
Code::blocks? I know how the binaries in /system/bin are built and where their source lies if that helps... You can easily create another binary and add it to the build process

Edit: Ah... I see... Its an IDE
 
jetx2x said:
Code::blocks? I know how the binaries in /system/bin are built and where their source lies if that helps... You can easily create another binary and add it to the build process

Edit: Ah... I see... Its an IDE
Click to expand...

Yes, what would I need to compile a that style of binary? If I could get that going under Windows (I know, I know lol) that'd be great! I just figured Code::Blocks could most likely do it best since it's already semi-multi-compiler aware.
 
mercury0x000d said:
Yes, what would I need to compile a that style of binary? If I could get that going under Windows (I know, I know lol) that'd be great! I just figured Code::Blocks could most likely do it best since it's already semi-multi-compiler aware.
Click to expand...

Probably can build using cygwin... I'll look into this further when I'm near my pc

Edit: the source for the /system/bin binaries are here https://github.com/Team-Osiris/android_frameworks_base... I'll have to look through androids overly complex build scripting to see how they are compiled and with what

Edit: oops... Navigate to the cmds sub folder for the source
 
What ever happened to this? I don't frequent the coding communities much anymore, so I apologize if it was addressed or the conversation moved elsewhere.
 
It's always been in the back of my mind... I could grasp the concept of making a new bootloader for the N860 that would have some extra hardware buttons... like bootloader mode and boot from sd... but that would only give us the ability to have two roms on our phone. I would like to run ubuntu or mint on this phone but those configurations require a loop kernel as they run as virtual machine... but if we have dual boot then we still need a kernel with loop on the sd card so it's not getting us any closer...
 
So, after thinking long and hard and flashing a hundred rooms back and forth, I have come to the most logical conclusion that dual booting a Warp would be the single greatest thing I could ask for.

What would be required? Is this the majority? Is this feasible?

-partitioning capabilities
-bootloader capable of selecting between partitions
-flashable zips that don't overwrite other partioned spaces
 
https://play.google.com/store/apps/details?id=com.drx2.bootmanager.lite

Works pretty well. Just note that it has been abandoned so it hasn't been updated in awhile. I recently heard that someone else was going to pick up development on it.

It's not compatible with jellybean roms. You can have a jellybean rom as your phone rom but the app can't flash a jellybean rom as the dual boot. Also it can't handle the aroma installer for roms that use that.

Here's more information at their website:
http://init2winitapps.com/stories/BMManual.html

With the paid version you can have 4 or 5 roms set up if you're so inclined.
 
anmire said:
So, after thinking long and hard and flashing a hundred rooms back and forth, I have come to the most logical conclusion that dual booting a Warp would be the single greatest thing I could ask for.

What would be required? Is this the majority? Is this feasible?

-partitioning capabilities
-bootloader capable of selecting between partitions
-flashable zips that don't overwrite other partioned spaces
Click to expand...

Theoretically possible, but we don't really have solid, working code on this yet. Check this out for more discussion on the topic.
 
That's a really great find. Thank you. However, it says that the N860 is unsupported. Is this incorrect?
 
This would be the greatest thing to complete. Run alliance and woem or droidsmith or halo etc. It would be incredibly helpful to testers as well! Ah well, just a poor man's dream for now xD
 
mercury0x000d said:
Most definitely it's possible, I'm just not sure how much effort it would take. At least we'd have the benefit of having existing Linux-based multiboot software such as Grub off of which to base such a thing.
Click to expand...


First time lookiing at this thread and the first thing I thought was some sort of grub port. Good to know we are all on the same page.
 
smartmanvartan said:
I think finding a way to open up mbn files could give us a way... i was thinking of a new hardware button in the bootloader like vol+ an camera for boot from sd...
Click to expand...

That would be awesome! Like the old BIOS screens: "Press <camera> to boot from SD card, <Vol Up> for recovery."
 
You must log in or register to reply here.
Back
Top Bottom