Related
does any one know of any android 2.0 cabs for vogue
There is a port but it has very limited functionality. Also, it does not come in cab. You have to place a bunch of files on the root of your SD card and run a program called haret.exe which will load the root file system as well as the kernel to run the OS.
Go to the general vogue section. You will have all the necessary info there. This section is only for WM upgrades.
every time in try it that way it wont work and i follow the insructions exactly and i did find a cab and it worked i tryed switching out the files but every time i try to run it it says failed to find system.img even though it named right and on the root of my sd
The cab version is probably a year old now. The files that were in that version will no longer work with current roms. There isn't a current all-in-one installer that I've come across that will run current versions of Android.
The new system images come with a .sqsh extension.
As the previous poster mentioned, the Vogue general forum has more Android related information.
Also, in case you guys are interested, dzo just came out with a flashable version of Android for the Vogue. In other words, you will install Android to the NAND rather than the SD card and wipe out WM in the process.
http://forum.xda-developers.com/showthread.php?t=593786
It would be nice if someone were to come up with a cab that installed android
But unfortunately it would be a lot of work and instead you have to run it on an sd card via haret (though its not that much more difficult)
And zen just came out with a new android 2.0 (eclair) build so you should go check that out!
kiwilime said:
It would be nice if someone were to come up with a cab that installed android
But unfortunately it would be a lot of work and instead you have to run it on an sd card via haret (though its not that much more difficult)
And zen just came out with a new android 2.0 (eclair) build so you should go check that out!
Click to expand...
Click to collapse
Someone did make a cab. http://www.myhtcphone.com/Android120208.CAB from here http://www.myhtcphone.com/ it is old but it has been done and it does work.
Hello,
like the title says i'd like to know if it's possible to create a bootloader or somewhat which is able to boot the standard OS from the device and a second OS from the memory card?
Let's say - if you switch the device on, you could choose whether to boot from the device (WM) or the memory card (Android).
Is it possible? Let's say - for the HTC HD2 for example?
What i found so far, is this and this article, as well as several threads in this forum. At least some really good dev's made it and ported Android to Touch HD for example. A bootloader would be needed in order to select, what to boot.
Thanks in advance.
Sincerely, nitrate
What currently happens is WM gets booted and then Haret gets run which acts as a bootloader.
You could streamline the process, and have haret run sooner, but given Android is currently not that stable I'd want to boot to WM myself.
l3v5y said:
but given Android is currently not that stable I'd want to boot to WM myself.
Click to expand...
Click to collapse
What?? I switched to my Android phone from a WinMO and I am upset because I didn't do it sooner.
Android on non-android devices is a little unstable, native android devices are stable enough. As far as bootloaders go, what most would like to see is a way of getting Android off SD and into ROM, so that we could boot directly into Android without needing to involve WM at all.
However unless someone can rewrite something like the OpenHandHeld bootloader for use with HTC devices, Haret will be the only way to boot Android for the forseeable future, plus, with the lack of stability on non-android hardware, I like the option of having WM there, just to fall back on if needed.
zenity said:
Android on non-android devices is a little unstable, native android devices are stable enough. As far as bootloaders go, what most would like to see is a way of getting Android off SD and into ROM, so that we could boot directly into Android without needing to involve WM at all.
Click to expand...
Click to collapse
This is what i want to know as well. A bootloader which let's you choose between booting WM from the devices' internal space or Android from the microSDHC-card.
And of course this bootloader should boot at first, just before WM does - kinda a boot menu of a Desktop PC which has Windows and Linux installed.
If it were possible to run a boot loader on your WM* device and dual boot there would be one major draw back (in my opinion); the architecture of these devices, without a storage card, uses the available memory for RAM and storage. Unlike your home PC that has specific Memory Chips and a Hard Disk Drive used for RAM and Storage specifically (if we ignore virtual memory for a minute) which means you can pack the disk space pretty much full and not effect the performance of the system.
Mobile Devices use some sort of Eeprom/solid state memory with XXXmb of memory. The more data files that you put inside the XXXmb of memory (in storage) means that the software you are running (WM6.5 + HTC Sense etc.) have less RAM to do their work, and the system is noticeably slower.
So back to the original topic, dual boot would suggest two OS residing in the devices ROM / XXXmb and a drastic reduction in performance, regardless of the OS WinMo or Android (linux)...
Saying that i have Android on my HD, using Haret.exe... I don't use it often and it is buggy - but the fact I've got it there shows that I'm still on the fence.
Hello
On my home computer, I am successfully hexibooting [6 OSs] on the one hard-drive.
Yesterday I bought myself an 8GB MicroSD card (was using onboard only before), and was wondering if it'd be possible to tri-boot;
Windows Mobile 6.5
Google Android
Rhobuntu
If it's possible, how can I make this project work?
Else, would it be possible to multi-boot with any 2-3 Operating Systems on an HTC Touch Pro2?
Thanks in advance for any help given,
Chip D. Panarchy
look in the rom section... theres roms built with both android and windows... dual booting.
Sounds interesting, I'll look into that.
Also, is it possible to Tri-Boot WinMo, Android & Rhobuntu?
It's kind of possible to "tri-boot" all these different OSes. Basically, Rhobuntu and Android reside on the SD card, and each can be started from their respective HaRET.exe, which is a bootloader that unloads Windows Mobile from RAM and loads the Linux kernel (and then the userland, whether it be Rhobuntu or Android).
You can have Rhobuntu and Android installed side by side on your microSD card, and WM on the internal NAND memory, but you still have to boot Windows Mobile before you boot Android/Rhobuntu.
There is a utility somewhere, called Gen.Y dual boot, which is a WM program that loads early in the WM boot process and gives you the opportunity to choose Android (or any other Linux distro with modification), but that's as close to a true multiboot system as you can get. There isn't a way to have a GRUB like selection screen at boot, or anything nice like that.
Hmm, well that's unfortunate!
Thanks for your help though, I'll look into GenY-Dual.Boot
Panarchy
I was wondering if there is a way to start haret in android? the only version I can find is for WM, so maybe is there a type of emulation layer it could be loaded to? Even better if there was an android version we could use that to reboot an SD run android and also boot into different version without having to reboot the entire phone and load wm up again (and nand android could then "haret" a diff version through sd).
Not sure you actually understand what the difference between Haret and Nand is.
Haret is, ( and always has been), a WM program, in fact it would make no sense to have it running as an android program, what Haret does is allow a WM device to run a Linux OS, that is all it does.
I think what you want is a way to dual-boot, to run different builds, which is possible, using the installer menu to choose which one to run, as well as where it is installed.
How it works is this, install your main build to nand, sys on nand, data on nand.
Then install another build, sys on SD, data on SD.
Once installed you have 2 builds, one on SD, the other on nand, to switch, you must reboot, enter installer, change the target settings to SD or nand, and quit, it should now boot from the installed version you chose,
I think you may have to have 2 ext2 partitions on SD for this to work, not sure since I never tried it, but I do remember someone posting this idea on the forum some time ago.
basically I want to boot an sd build from within an sd build. This serves a few purposes, mainly no need to boot into a different os (wm in this case) just to boot a diff version, and to allow a type of reboot on an sd build. If this can be done in script that would work also but want an android app to kick the current build out of memory and load a new one in (or the same one reloaded) instead of it being wm based. This might be something we can do with the kernel to just dump the current gui and load the other gui onto it?
edit: BTW I am using a type of boot you are explaining but instead of installer in between I have wm with different "andboot" folders.
ghghgh14702 said:
basically I want to boot an sd build from within an sd build. This serves a few purposes, mainly no need to boot into a different os (wm in this case) just to boot a diff version, and to allow a type of reboot on an sd build. If this can be done in script that would work also but want an android app to kick the current build out of memory and load a new one in (or the same one reloaded) instead of it being wm based. This might be something we can do with the kernel to just dump the current gui and load the other gui onto it?
edit: BTW I am using a type of boot you are explaining but instead of installer in between I have wm with different "andboot" folders.
Click to expand...
Click to collapse
Interesting concept, and theoretically possible, since Android itself is a shell on the Linux core, it may be possible to do this, perhaps a remount of /system and /data, then a restart of the kernel, almost certainly requires some hardcore Linux knowledge, anyone up for this?
This posthttp://forum.xda-developers.com/showthread.php?t=594077 is for the dream.
We've been able to from internal or sdcard on vogue,kaiser, polaris for ages from boot.
The only other way is to use grub 'if possible'.
I think ghghgh14702 means that directly reboot Android. NOT shut down, then boot to wm, and then run haret.
In All the builds I've tried, the reboot menus all dont work. Most reboot meuns make the phone shut down.
I'm using a polaris, running Android in the sd card, and seems dont have a recovery mode.
I found sometimes Android stucks and reboots itself when I push the volume button to adjust the system volume. It is a DIRECTLY reboot, not reboots into wm.
So I think there is some way to reboot directly. Hope sb. can find it out.
Hello,
I need some help. Install its Android OS, but after he reset my Kaiser again charged WinMo OS. My question is whether it is possible to choose which OS to load first or with any program or edit the file to indicate to launch the first Android.
Sorry for my bad english :S Use Google translator
If you have installed Android to SD card and use Haret.exe then it will always reboot to WM.
You must install to nand if you wish to boot to Android only, which will wipe WM totally and replace it with Android.
The guide stickied at the top of the forum is a good tutorial in doing this
That does bring a good point to my mind though, we could create an exe that loads at startup of wm to auto load haret and startup if the user doesn't cancel in so many seconds (like grub). I keep WM on my phone so I can easily change my droid version and also I know everything works including opening office files (actually that's the biggest sticking point for me keeping it).
Thanks for support. Today I try to flash via NAND method.
Kind Regards
Lybomir
I flash my Kaiser with latest zImage-2.6.32-froyo-09-09-10_21 from here http://it029000.massey.ac.nz/vogue/files/?C=M;O=D and my device loading Android OS very slow, and big problem is : Phone go in screensaver and I try to unlock and screeen stay only in white light, no picture, no widgets... total block. Only solution is it a use Soft reset button or remove batery
Maybe you choose the wrong panel type?
I can read in your signature Duo Boot so I guess you installed onto the SD and use Haret to run Android.
If so, you have to edit the default.txt file locate in ANDBOOT folder and modify the value following htckaiser.panel_type.
You can specify 1, 2 or 3 (most Kaisers use panel type 2)
Wrong panel type may lead to awake problems or wrong colors...
The excessive slowness may be due to a slow SD. Which class is it? Use at least class 4 SD.
---- EDIT -----
In case you already flashed to NAND, to change the panel type you have to choose the right kernel (the kaisimg file) or you can edit the one you flashed following instructions and links you can find in #4 at http://forum.xda-developers.com/showthread.php?t=680518
obviously you have to reflash the kaisimg.nbh but you don't need to flash Android again
I try with 1,2 and 3 but every time show me a this problem, and now i run HaRET and in 2 from 3 times phone block and not response only Soft reset work, and if case phone load complete Android and again in screen seaver system not respond... ;(
I flash my phone with ext2 partition on my sd card/ class 4 8 GB SDHC/ and try with system and data on sdcard an again freez white screen/
Sorry for my bad english
dlink.bg said:
I try with 1,2 and 3 but every time show me a this problem, and now i run HaRET and in 2 from 3 times phone block and not response only Soft reset work, and if case phone load complete Android and again in screen seaver system not respond... ;(
I flash my phone with ext2 partition on my sd card/ class 4 8 GB SDHC/ and try with system and data on sdcard an again freez white screen/
Sorry for my bad english
Click to expand...
Click to collapse
May you try to install a different build and see if you fall into the same problem?
BTW, just after installing, don't start playing soon with the device: initially skip all settings (touch the android, don't set google account and so on) and leave the phone quiet for at least 10-15 minutes: some builds need to copy file to the cache and playing with the device may interfere with this operation leading to unpredictable effects...
Let we know...
It is slow because you installed it on sdcard.. both partition.. if you are on nand. Try install both partition on nand partition.. and try hawks soad rls 3 as me.. its fastest build for kaiser.. and I haven't ever problem with white screen ata awake.. try it in that haws soad ion build.. you can finf it in that forun.. just find it
Sent from my HTC Kaiser Ion using XDA App
I find a solution! Later I post how find solution
Thanks on every in this thread to help me!
dlink.bg said:
I find a solution! Later I post how find solution
Thanks on every in this thread to help me!
Click to expand...
Click to collapse
You're welcome
And I'm waiting to know
Don't suppose any of you have actually seen this thread?
Gen.Y DualBOOT v1.0.6.0
Should work fine on Kaiser, certainly works fine on other devices, such as Diamond, Blackstone etc
zenity said:
Don't suppose any of you have actually seen this thread?
Gen.Y DualBOOT v1.0.6.0
Should work fine on Kaiser, certainly works fine on other devices, such as Diamond, Blackstone etc
Click to expand...
Click to collapse
Hi Zenity... Yes, know that piece of software.
But as You have to boot WinMo (Yes, I Know, not all the services need to be running but system must be loaded and started, GUI must be running and so on) in order to DualBOOT can start, I can guess it's only a partial time-save... isn't it? Did You tried it?
Have not tried it on my Kaiser, since it is Nand flashed, but I think it is what was being asked for really, a way to boot either WM, or straight into Android on SD.
I don't think it will ever be possible for both WM and Android to co-exist on nand, since there simply is not enough room on the internal memory for both.
It is a time saver on other devices I have tried it on, Diamond, Blackstone, however since neither of these devices is nand-flashable this is more what Gen-Y's dual boot was intended for.
If it was possible to run WM from SD then we might be able to truly Dual Boot, in a similar fashion to Windows/Linux on PC, but as far as I know this is not possible either.
zenity said:
Have not tried it on my Kaiser, since it is Nand flashed, but I think it is what was being asked for really, a way to boot either WM, or straight into Android on SD.
I don't think it will ever be possible for both WM and Android to co-exist on nand, since there simply is not enough room on the internal memory for both.
It is a time saver on other devices I have tried it on, Diamond, Blackstone, however since neither of these devices is nand-flashable this is more what Gen-Y's dual boot was intended for.
If it was possible to run WM from SD then we might be able to truly Dual Boot, in a similar fashion to Windows/Linux on PC, but as far as I know this is not possible either.
Click to expand...
Click to collapse
Yes, of course we haven't enough NAND to have both OSes!!!
What I was thinking to (but I'm a lot far to inspect WinMo booting sequence...) is if may be possible to wedge a sort of bootloader running BEFORE the OS loads or in the early booting process and letting we choose to boot WinMo (in NAND) of Android (on SD).
At present moment I've Android running from SD but kernel NANDed (I've got problems running out of NAND and no time to solve them so I'm using the solid build previously installed on SD) so Kaiser boots quickly... and this confirms it's possible boot SD Android without having to load WinMo or Haret. The more relevant matter I can see is that we have to find a way to wedge the bootloader without have to manual modify the WinMo ROM (virtualization is far from be considered on such devices...)
I suppose this is just a "mind exercise" (Sorry, I don't know how to correctly translate an Italian common saying...
Mind exercise describes it perfectly
Not sure why you would run out of space on nand, unless you are loading a lot of apps, and there are ways to run android that may help with that, such as apps2sd, or data on SD partition.
If you must have WM then your only choice would be using Haret.exe, and the most efficient way to dual boot we have at the moment is the Gen-Y solution, which is not ideal, but does offer at least part of what you seek.
The Android bootloader we use (tinboot.s) is not flexible enough to allow dual booting, but may have some information that may be of some use in this
tinboot thread
See what you think anyway
Sorry, I was not able to be clear... I apologize for my English...
When I said "I've got problems running out of NAND" I intended to say "I've got problems - very bad performances - when Android was running from NAND"!!!
Maybe we are a bit OT...
BTW, I was far from software developing for a long while and never developed low level software for Linux/Unix... but in the past I messed up with Z80, 65xx, 68K and x86 platforms's assembly
Recently I need to approach software developing again (but at a really different level...)
I'd like to have spare time to start again, as this world attracts me more. Maybe I'll give it a chance...
Let me understand... tinboot is actually used bootloader?
BTW, just to be clear... I don't need WinMo and I'm giving Android a chance to revive my Kaiser. I'm looking for a fast and stable build and actually I'm running VaniljEclair RLS11 (Yes, I know, I'd try your Polymod 2.1D build... )
Tinboot is the bootloader we use to get android in nand, not being a coder my understanding in limited, however I did think that thread may have useful information for anyone interested in the low level workings of out devices.
I assumed you meant running out of space on nand, lol, i see now what you mean, no need to apologise for you english, it's fine
zenity said:
--- CUT ----
however I did think that thread may have useful information for anyone interested in the low level workings of out devices.
Click to expand...
Click to collapse
And you're right... it's a useful starting point and I'll read it accurately...
Unluckly, I need a lot of spare time (and I don't, at present) to build a solid knowledge base and to start developing for Android.
yes there should be plenty of room for both oses on Nand, I still have over 90 mb on my wm6.5 nand install with come extra apps in there. So if you stripped down both oses you could easily fit them both on nand and still some space left. But then you need to have a boot loader that will be able to load both oses. I think I heard someone say somewhere they are using grub to boot android from nand, that can boot windows also with the right configuration, that would be where to start.