[APP][9/23/11] RunDroid-dual boot to (multi) Android [SD] or WM6
- Thread starter Pop45398
- Start date
i spoke to soon . After try out the apps 'v2.01' It crash my 2nd Android
1)MCCM GB V2.1.1 -with no problem
2)MCCM HD V4.0- crash build
i had to fresh install back the build to get the build get going again . Hope OP can work this out . Hope to have fully function dual boot SOON. Thanks for the hard work .
Works great on my HD2 with W6.5 and Android (running from Desire_DL folder). Both os are Dutch .
To run on Dutch HD2 just edit the AppFolder name in RunDroid.mscr, than let Rundroid create the desired shortcut(s) and then move (with file explorer) the shortcuts from \windows\startup to \windows\opstarten and from windows\startmenu to \windows\start menu
Thanks
To run on Dutch HD2 just edit the AppFolder name in RunDroid.mscr, than let Rundroid create the desired shortcut(s) and then move (with file explorer) the shortcuts from \windows\startup to \windows\opstarten and from windows\startmenu to \windows\start menu
Thanks
i spoke to soon . After try out the apps 'v2.01' It crash my 2nd Android
1)MCCM GB V2.1.1 -with no problem
2)MCCM HD V4.0- crash build
Thanks for the hard work .
I have no clue how it could crash a build as it does nothing to the files besides renaming the folder then running CLRCAD and HaRET just as if they were run from a file explorer. When another build is selected the previous is renamed back to original before the new build folder is renamed to Android. By the way, after you get a build up and running you should copy the data.img (or whatever that build calls it) somewhere so if a crash occurs you can copy the original files plus your saved data.img back so your settings will be restored. Doing this weekly or whenever you make changes or additions is a good idea.
I did find a couple of bugs, one I'm not certain was in the last release or something I broke later, that caused a build not to run on the next running after renaming the folder to Android. The other occurred very occasionally, mostly after having to pull the battery after a build hung on the boot screen, where RunDroid would show as not found upon boot-up due to the SD card not being initiated before trying to start RunDroid. To fix the latter bug installation to the device is now possible, in fact preferred over installing to the SD card as that way it will wait for the SD card to be initiated before going any further.
I have sent everyone who posted their desire for the multi-build version a link to the latest version; however, there was one who only PMed me who I don't remember. If the version was installed via the .cab file, you should first remove the previous version via All Settings> System> Remove Programs then run the latest .cab to install (future versions should automatically uninstall v2.1.1 and above). Read the latest documentation or at least the captions for the screenshots.
Thanks for the tips . Will try the new version and give feedback .
Edit : ok few time of testing i can confirm the New version v2.1.1 Works! The build that i test on my SD Card .MCCM GB V2.1.1 and MCCM HD V4.5 after install the app. i change the build name to Android and Android [1] . Great work man . Thanks again for your hard work
cheers
Last edited:
Thank you for version 2.1.1
It works perfectly))
I have only one question/suggestion
Is there a way to block phone process like you did with HTC Sense.
My first app to open is Phone PIN Code screen blocking me from the boot options. I need to either press cancel or type my pin to get to the choice of OS's.
Any ideas how to give priority to your app over phone app?
Thx
It works perfectly
))I have only one question/suggestion
Is there a way to block phone process like you did with HTC Sense.
My first app to open is Phone PIN Code screen blocking me from the boot options. I need to either press cancel or type my pin to get to the choice of OS's.
Any ideas how to give priority to your app over phone app?
Thx
Last edited:
Hi -- would you please send me the link to your latest? Thanks!
P.S. I am sure that I have missed it, but why not simply post it?
P.S. I am sure that I have missed it, but why not simply post it?
Thank you for version 2.2.1
It works perfectly
I have only one question/suggestion
Is there a way to block phone process like you did with HTC Sense.
My first app to open is Phone PIN Code screen blocking me from the boot options. I need to either press cancel or type my pin to get to the choice of OS's.
Any ideas how to give priority to your app over phone app?
Thx
It's been a while since I messed with WinCE devices. I have an idea and will look into it.
Last edited:
Hi -- would you please send me the link to your latest? Thanks!
P.S. I am sure that I have missed it, but why not simply post it?
PM sent. I have my reasons for not simply posting.
Besides, v1 has been downloaded over 1100 times and only 10 have asked for the multi-build version.![[Krueger]Dr.Stein](/data/avatars/s/219/219301.jpg?1600602948){kind=avatar}
Understood and thanks.PM sent. I have my reasons for not simply posting.
Yep, my bad. I meant 2.1.1
And thanks for looking into my little problem
So far the best dual booter out there. I tried Android Dual Boot Loader By MSKIP, SmartBoot, Exceller Multiple Build and Android Windows Boot and RunDroid is simply THE BEST
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
50I've created an app for dual booting automatically to Android or WM6. V2.3.2 can boot multiple version of Android on a single SD card and can be customized for text content and language. See post #2 for documentation and screenshots.
The "lite" version is a replacement for using a file explorer to run CLRCAD then HaRET, allowing Android to be started with a single tap on an icon. To install the lite version, simply un-RAR the contents to your Android folder then use a file explorer to create a Start Menu shortcut.
Please leave feedback and suggestions/questions.
French translation:http://xdaforums.com/showpost.php?p=13123392&postcount=15116Documentation and Screenshots
RunDroid app v2.3.2 for HTC HD2 by Pop45398 (@ XDA Developers)
This app can start Android on an SD card automatically on boot-up or with a single tap, thus allowing for an easy dual boot to Android or Windows Mobile, and should be compatible with all versions run with CLRCAD/HaRET. It features a setup menu which allows for user customization including setting the timeout before the default OS is started, thus allowing time to access the setup menu or select a non-default OS. It is actually a MortScript and corresponding MortRunner with a custom icon. It may work on other WM6 devices.
CHANGES:
Version 2.3.2 added a new subroutine to rename the Android folder back to its original name when “Enable Builds” is selected if RunDroid had renamed the folder to Android. This eliminates the folder being renamed to Android[1]. (Thanks to crazycranky!)
Version 2.3.1 features language/text customization. By editing RunDroid.ini with a text editor the user can now change all text for desired content and language (with exception of button text, i.e. Ok/Cancel, Yes/No). There is no longer a need to edit the script for non-English ROMs where the SD card is not called “Storage Card”, a directory tree will appear for the user to locate the SD card’s root.
Version 2.2.1 features some minor changes over v2.1.1. A StartUp shortcut is no longer used for auto-launching at boot-up, instead it is launched during the init process before StartUp programs, hence the elimination of creating and deleting shortcuts from the Setup Menu. A new option to Enable Sense has been added so that Sense can be easily re-enabled if somehow not properly re-enabled during script execution. A setup.dll is now used to run Install and Uninstall scripts.
Version 2.1.1 represents a major overhaul from version 1 and features the ability to boot to a basically unlimited number of Android builds and a guided setup that walks through the setup process on initial running. It will scan all folders in the SD card's root for Android builds, indicated by the presence of HaRET.exe. It asks whether to use each build then asks if it requires renaming the folder to Android in order to run (some builds don't require being in the Android folder). A .cab file is used for installation which is now in the RunDroid folder in the root of the device. The folder name is used for displaying the build's name in RunDroid, with one caveat: if there is more than one build and one of them is named Android, that folder will be renamed to Android[1] so that the selected build folder can be renamed to Android (which is renamed back to original when another build is selected), hence descriptive folder names should be used.
INSTALLATION:
Simply copy the .cab file to the SD card and run it with a file explorer to install. Version 2.3.1 MUST be installed to the device due to hard coded addresses required for auto-launching. This also eliminates the occasional possibility of the SD card not being initialized before RunDroid is started during boot-up. If during installation the SD card is not found by the default name “Storage Card” (usually due to a non-English ROM) a directory tree will appear for choosing the correct SD card root, not Android folder (see screenshots below for an example).
OPERATION:
Start RunDroid with the Start Menu icon. On initial running, a guided setup will walk through the settings. Menus are self-explanatory (see screenshots). Selection is done by double-tapping an entry or tapping once then tapping OK. Only the main (Boot Selection) menu is timed for auto-selecting. If auto-running at boot-up is NOT desired, select “Disable AutoStart” during initial setup or later from the Setup Menu. The Timeout Delay may be adjusted to suit the user and system (see ISSUES section below). Whenever another build is added or deleted, one is no longer desired to be run, or a folder name changed, Enable Builds must be selected from the setup menu which will once again walk through the setup of builds and default OS selection (but not other settings). Builds are displayed in alphabetical order and can only be rearranged by renaming folders, like by adding a number at the beginning of folder names.
ISSUES:
Startup programs, including HTC Sense and Notifications, etc, can briefly interfere with the ability to make selections, causing the default OS to be started before menu selections can be made. To combat this, if enabled and not already started, Sense is disabled then re-enabled on app exit. The Timeout can be adjusted to help with this. If the Timeout is set too low and selecting the Setup Menu or Boot to Windows is not possible, simply re-install the .cab. If unable to boot to Windows because Android starts before the menu appears, power off the device, remove the SD card, then power on the device; if not already at the menu, start RunDroid and go to the Setup Menu and adjust the Timeout to allow more time to access the menu, then power down and re-insert the SD card.
CUSTOMIZATION:
The user interface can be customized for text size, font type, language, and size of menu selection entries by editing RunDroid.ini with a (pure text) editor such as Notepad. Once RunDroid is installed, locate the .ini file in the RunDroid folder in the root of the device (not SD card) and open or copy to PC then open.
The following variables control the font and size of menu entries:
FontSize=23
EntryScale=1.3
FontType=Tahoma
Increase or decrease FontSize to make menu selection text larger or smaller. EntryScale controls the size of menu selections, larger size makes selections easier to make. The scale is in percentage of the font size, i.e. 1.3 equals 130% of the font size. To use a different FontType than Tahoma, the desired font must be installed on the device.
In addition to descriptive variable names, to make RunDroid.ini easier for editing text content and language certain conventions are used:
Variables containing “Sel” are for menu selection entries.
......WMsystemSel=Windows Mobile
Variables Containing “Hint” are for the text that appears in the upper portion. Note that “Setup Menu” is preceded by a period and several spaces. The spaces are to center the text; the period is required because leading spaces will otherwise be ignored and the text will begin on the left instead of centered.
......SetupMenuHint=. Setup Menu
Variables containing “Txt” are for messages and questions which pop-up in new windows.
......NoBuildsMessTxt=There were no Android builds using HaRET.exe found on this SD card.
Do not change the actual variable names, for example “TimeoutMessHint=”, only the text following the “=” sign as these names are hard coded into the script and the new text will not appear.
Editing prior to completing the initial setup is preferred. Once editing is complete, copy the modified file to \RunDroid, overwriting the original. A copy of the modified RunDroid.ini file should be saved somewhere besides \RunDroid because if RunDroid is reinstalled or a newer version installed the entire folder will be deleted along with the modified file. Once reinstalled, copy the modified file to \RunDroid before completing the initial setup.22New Version
I've uploaded a new version (v2.3.2). It corrects an oversight on my part. When "Enable Builds" was selected, if RunDroid had renamed a folder to Android it was renamed to Android[1]. In v2.3.2, when "Enable Builds" is selected, if a folder has been renamed to Android it will now be renamed back to original instead of Android[1].
All credit and kudos for this change go to crazycranky!
