Is there a CDMA Hero equivalent to HaRET for temporarily booting into a 2.x build to nondestructively play with it? I'd love to play with 2.1, but I don't want to completely give up having a camera.
Alternatively... if there's no way to do it from a (rooted) stock Sprint ROM, can a HaRET-like boot go in the OTHER direction? IE, flash an experimental 2.1 ROM onto a rooted CDMA Hero, then temporarily boot from IT into the stock Sprint ROM (or any other ROM that has camera working) on the uSD card?
miamicanes said:
Is there a CDMA Hero equivalent to HaRET for temporarily booting into a 2.x build to nondestructively play with it? I'd love to play with 2.1, but I don't want to completely give up having a camera.
Alternatively... if there's no way to do it from a (rooted) stock Sprint ROM, can a HaRET-like boot go in the OTHER direction? IE, flash an experimental 2.1 ROM onto a rooted CDMA Hero, then temporarily boot from IT into the stock Sprint ROM (or any other ROM that has camera working) on the uSD card?
Click to expand...
Click to collapse
Lots of people here are just using nandroid.
Make a nandroid backup of "good Phone" then load 2.1 when your done, throw your backup back on the phone. In other words, we don't have a virtualization thingy yet or even a really nifty boot loader.
2.1 is fun, but all the cool stuff is yet to come-- IE: Camera, Multi-touch, OPEnGL 3d stuff. It works as a phone, but thats about all its good for.
Hmmm. Is that just because nobody has had the time to write a program like HaRET for HeroC, or is there something fundamentally different about the way Android is flashed, boots, and runs on our phones compared to Windows Mobile that makes a HaRET-like program more or less impossible to pull off the same way?
It does seem like kind of a cruel irony that booting Android from a theoretically proprietary phone running WinMo is trivially easy, but our allegedly open phones won't give us the freedom to pull off the same trick to boot a newer build of the same theoretically open OS.
HaRet has been around a long time - and so has Windows CE, from which HaRet came. Android is relatively new, and flashing images back and forth is so easy there doesn't seem to be much need for that sort of tool.
miamicanes said:
Hmmm. Is that just because nobody has had the time to write a program like HaRET for HeroC, or is there something fundamentally different about the way Android is flashed, boots, and runs on our phones compared to Windows Mobile that makes a HaRET-like program more or less impossible to pull off the same way?
It does seem like kind of a cruel irony that booting Android from a theoretically proprietary phone running WinMo is trivially easy, but our allegedly open phones won't give us the freedom to pull off the same trick to boot a newer build of the same theoretically open OS.
Click to expand...
Click to collapse
Well, if you think about it, Nandroid is exponentially better than a HaRet counterpart. The major drawback to HaRet is that it loads on top of the already loaded OS, which strains the already stretched system resources. It was good for checking Linux out on a Windows Mobile OS, but we can basically do the same thing using Nandroid, but have the benefit of all resources being dedicated to the ROM we're testing out. So, I guess I always kinda thought of nandriod as a HaRet-like loader, but I guess it's all in how you look at it
I don't think there is anything that stops is from it,0other than no need. Also we have only been working on hero stuff for about 3 months on the cdma side, still have lots pa stuff we can do.
Related
I didn't think it belonged in Dream Android Development, so I'm putting it here. If it needs to be moved, move it.
Is it possible to boot anything other than Android on the Dream?
I've seen the Nokia N900 and its Maemo 5 firmware, and I'm absolutely drawn to it, thanks to its debian-based OS (sudo apt-get install anything), it's X-based graphics system (REAL linux GUI programs), and all the apps it already has (Native Gizmo > Hacky Sipdroid).
I've also taken a look at other Linux-based open phone firmwares.
What is keeping us from doing this? If it's drivers, do they exist for another similar Linux-based firmware?
Could we dual-boot Android and this other OS using a third-stage bootloader which loads as a kernel from within the BOOT: partition?
I've seen the (albeit extremely hackish) method of getting Debian on the G1, chrooting into a loop-mounted FS and using a loopback VNC to spring into a KDE/Gnome/LXDE UI, but it's slow, still has Android and its apps loaded into memory, and very hackish and unstable.
I'm more than willing to test anything firmware-wise on my phone as long as it doesn't mess with my SPL.
The possibilities are nearly limitless - WINE under Linux means true "Windows Mobile" without the WinCE kernel.
Or perhaps WinMo/WinCE can be booted on the Dream?
It's more of a question of whether or not it's possible right now than a concept or implementation, but once that's answered, I'll either throw some time into testing and porting, or kick back and enjoy the Android as it is.
For starters:
- How does the SPL hand off to the BOOT: partition and its kernel/initrd?
- What devices need what drivers? What should be thrown into the kernel?
- Do things need reverse-engineering or is it all straightforward and documented?
- How can we use the space provided without messing with the SPL? (use cache partition for OS? Modified recovery that doesn't depend on cache partition?)
- Is dual-booting between Android possible? Can this be switched and launched before Dalvik and the Android stuff loads on the Android kernel?
- Can this be done with other Android-powered, rooted devices?
Have you seen wiki.openmoko.org/wiki/OpenMoko_on_HTC-Dream or lists.openmoko.org/pipermail/community/2009-August/052529.html? (Crap, I can't post links) Looks promising since Angstrom is a very powerful embedded distro, but it's a one-man project now. I hope some people will join it or start a similar project.
G1 is a great device, however, I can see only a few people hacking on OS alternatives for it. You always got to have either an active community or a company in order to complete such a project.
The Android hackers community is very vibrant, however, people are not really interested in bringing a fully-featured Linux distro to G1 or other Android phones. Android is too trendy itself
The Debian/Ubuntu opportunity that we have now is nice, but it looks like an addition to the Android which takes a lot of memory and CPU.
I have just set up a small Ubuntu environment booting on my G1 together with Android. I combined the userspace prepared by Paolo Sammicheli (xdatap1.wordpress.com/2009/05/03/jaunty-under-android/) with Bayle Shanks's instructions (bayleshanks.com/wiki.pl?tips-computer-android-g1_debian_cyanogenMod). I am going to use it for mutt, vim, some coding. X11/VNC experience has been frustrating so far.
I am pretty sure though that there will be more people wanting to use alternative OSes on their phones: Moto Droid and Nexus are powerful enough for a full desktop environment.
vaskas said:
Have you seen wiki.openmoko.org/wiki/OpenMoko_on_HTC-Dream or lists.openmoko.org/pipermail/community/2009-August/052529.html? (Crap, I can't post links) Looks promising since Angstrom is a very powerful embedded distro, but it's a one-man project now. I hope some people will join it or start a similar project.
G1 is a great device, however, I can see only a few people hacking on OS alternatives for it. You always got to have either an active community or a company in order to complete such a project.
The Android hackers community is very vibrant, however, people are not really interested in bringing a fully-featured Linux distro to G1 or other Android phones. Android is too trendy itself
The Debian/Ubuntu opportunity that we have now is nice, but it looks like an addition to the Android which takes a lot of memory and CPU.
I have just set up a small Ubuntu environment booting on my G1 together with Android. I combined the userspace prepared by Paolo Sammicheli (xdatap1.wordpress.com/2009/05/03/jaunty-under-android/) with Bayle Shanks's instructions (bayleshanks.com/wiki.pl?tips-computer-android-g1_debian_cyanogenMod). I am going to use it for mutt, vim, some coding. X11/VNC experience has been frustrating so far.
I am pretty sure though that there will be more people wanting to use alternative OSes on their phones: Moto Droid and Nexus are powerful enough for a full desktop environment.
Click to expand...
Click to collapse
i really think it lies in what you want from your phone... i know you say you use your ubuntu env for things such as vim and mutt, but everything that vim and mutt can do, can already be done under android..
the biggest challenge is getting people to latch on to an alternate distro which offers MORE than android, which has yet to come to surface... ultimately this is a phone.. not a netbook...and for a phone android is pretty dam sweet...
although in terms of geek work, running ANY other os on non native hardware is cool....albeit not really worth it
anybody were successful by using the internal-memory-image from the openmoko wiki?
I always get kernel panic, when booting it. I flashed it with flash_image boot/system, does this matter? In the wiki they use fastboot.
scheich, I only tried the SD-card way (see my post in http://forum.xda-developers.com/showthread.php?t=624392)
It shouldn't really matter whether you use fastboot or flash the image. The kernel panic could occur due to the inability to find the root filesystem. Try reflashing the yaffs2.
By the way, why did you choose to put OpenMoko in the internal memory? Are you going to use it exclusively or as the primary OS on the device?
Some of what you suggest can be done, but not recommended.
1) Nokia/Maemo is a bad fit for a phone. It is a real HOG. It is also shoehorning (with a sledge hammer) a desktop OS into a phone. It just doesn't work right. Android exists because a totally new UI model was needed to work optimally with a phone's physical form.
2) WINE will NEVER work since the CPU in the phone is ARM and not x86. If you want to run windonkey programs (can't imagine why you would), you would have to run a PROCESSOR EMULATOR, and this will be REALLY REALLY REALLY slow and memory intense.
TylTru said:
I didn't think it belonged in Dream Android Development, so I'm putting it here. If it needs to be moved, move it.
Is it possible to boot anything other than Android on the Dream?
I've seen the Nokia N900 and its Maemo 5 firmware, and I'm absolutely drawn to it, thanks to its debian-based OS (sudo apt-get install anything), it's X-based graphics system (REAL linux GUI programs), and all the apps it already has (Native Gizmo > Hacky Sipdroid).
I've also taken a look at other Linux-based open phone firmwares.
What is keeping us from doing this? If it's drivers, do they exist for another similar Linux-based firmware?
Could we dual-boot Android and this other OS using a third-stage bootloader which loads as a kernel from within the BOOT: partition?
I've seen the (albeit extremely hackish) method of getting Debian on the G1, chrooting into a loop-mounted FS and using a loopback VNC to spring into a KDE/Gnome/LXDE UI, but it's slow, still has Android and its apps loaded into memory, and very hackish and unstable.
I'm more than willing to test anything firmware-wise on my phone as long as it doesn't mess with my SPL.
The possibilities are nearly limitless - WINE under Linux means true "Windows Mobile" without the WinCE kernel.
Or perhaps WinMo/WinCE can be booted on the Dream?
It's more of a question of whether or not it's possible right now than a concept or implementation, but once that's answered, I'll either throw some time into testing and porting, or kick back and enjoy the Android as it is.
For starters:
- How does the SPL hand off to the BOOT: partition and its kernel/initrd?
- What devices need what drivers? What should be thrown into the kernel?
- Do things need reverse-engineering or is it all straightforward and documented?
- How can we use the space provided without messing with the SPL? (use cache partition for OS? Modified recovery that doesn't depend on cache partition?)
- Is dual-booting between Android possible? Can this be switched and launched before Dalvik and the Android stuff loads on the Android kernel?
- Can this be done with other Android-powered, rooted devices?
Click to expand...
Click to collapse
vaskas said:
scheich, I only tried the SD-card way (see my post in http://forum.xda-developers.com/showthread.php?t=624392)
It shouldn't really matter whether you use fastboot or flash the image. The kernel panic could occur due to the inability to find the root filesystem. Try reflashing the yaffs2.
Click to expand...
Click to collapse
Tried reflashing the system image. Also the older image on the ftpserver. The same. I will try the sdcard installation.
vaskas said:
By the way, why did you choose to put OpenMoko in the internal memory? Are you going to use it exclusively or as the primary OS on the device?
Click to expand...
Click to collapse
Two reasons:
1. Thought that would be the faster way to get it work. I used BART to backup my android installation.
2. Thougt, I would get a bit more perfomance in using the internal memory.
I really would like to use SHR(or other) as primary OS, because I had an GTA02, depends on what is(could) work(ing) on the dream.
would it be possible to boot ubuntu netbook remix? it uses far less resources.
zenstitution said:
would it be possible to boot ubuntu netbook remix? it uses far less resources.
Click to expand...
Click to collapse
NBR is targeted at x86, but Ubuntu MID edition is installable. It's similar to the netbook remix. We'll have to wait before we have a proven/stable installation method though.
I would really like to see another OS on my Dream as well - just in addition to android
Che123 said:
I would really like to see another OS on my Dream as well - just in addition to android
Click to expand...
Click to collapse
Well, you can try the OpenMoko port (it's in the alpha stage now): http://forum.xda-developers.com/showthread.php?p=5521417
The more people get interested in the alternative OS, the sooner we'll get one.
vaskas said:
Well, you can try the OpenMoko port (it's in the alpha stage now): http://forum.xda-developers.com/showthread.php?p=5521417
The more people get interested in the alternative OS, the sooner we'll get one.
Click to expand...
Click to collapse
Really hot stuff - but i don't want to loose my recovery
But i will definetly keep an eye on it!
edit: Adding a bootmngr like grub for selecting boot OS (android/openmoko/recovery) would be really nice Or adding bootoptions to the current amon_ra Recovery would be a soloution too. But I'm no dev, so I don't even know if it is possible.
when we running Android on HD2, does WM still running "behind"?
and
is it possible to make Android a "real rom" for HD2.. I mean installing Android in our phone memory instead of in SDcard.
thanks for answering
1-no, haret kills all winmo processes, so you are only running android.
2-in the near future maybe, but for now you need winmo to run haret and boot android. still much work to do to be able to directly boot android from the bootloader.
hope this helps
1 - I read this a lot in the last replies here on xda, but can anybody actually comfirm this claim? I can definitely see differences in running android depending on applications running in windwos mobile, which makes no sense if wm really was shut down completly.
no, WM is not running.
but! last system state in WM can cause difference in Android behavior.
mostly because Android kernel code assume, that it's running on clear system, after bootloader.
thank you all for answering.
i am very looking forward to the Android ROM which can be directly booted
Cotulla said:
no, WM is not running.
but! last system state in WM can cause difference in Android behavior.
mostly because Android kernel code assume, that it's running on clear system, after bootloader.
Click to expand...
Click to collapse
thanks, good to know
I am a linux fan and I am using Linux for a long time.I bought the HTC HD2. I saw some youtube videos about Android Froyo on HD2.I want to try it but they were showing that you have to put the file on the micro sd card and you have run it from there.My question is if I do it can I run windows mobile after a new boot ?or it will boot android for all time?I just don't want to let windows go because may be i will switch back.Can any one please help me?
Yes, you can easily get into winmo, every time you shutdown android you have to load winmo first and then use haret to load android, so no worries .
mlhazan said:
I am a linux fan and I am using Linux for a long time.I bought the HTC HD2. I saw some youtube videos about Android Froyo on HD2.I want to try it but they were showing that you have to put the file on the micro sd card and you have run it from there.My question is if I do it can I run windows mobile after a new boot ?or it will boot android for all time?I just don't want to let windows go because may be i will switch back.Can any one please help me?
Click to expand...
Click to collapse
You can also get a boot loader from XDA and choose which you want to load at start up. windows or android...
HectiQ said:
Yes, you can easily get into winmo, every time you shutdown android you have to load winmo first and then use haret to load android, so no worries .
Click to expand...
Click to collapse
Thanks for quick reply.Do you know which devices will not work on HTC HD2 if I run Android?Cause little confused here .Some people says wifi does not work ,some says camera does not work.Do you know actually what does not work?
That was a loooong time ago^^
Now, EVERYTHING WORKS, unless:
- You have an inappropriate Kernel (some still have issues, but the latest one works flawlessly)
- You have an inappropriate ROM (there's been reports on CM6 not being ok with all Kernels, hence the 1°)
- You have an "Exotic" rom (Desire HD, Desire Z...) : these aren't fully supported ATM
However, there are known issues with:
- Tethering, especially Wifi, it's not yet always 100% ok
- Kernels, they are all being tweaked, but IMHO, go for it, I don't boot WinMo anymore
- And other small annoyances, but that depends on your device, rom, kernel, etc etc etc
FOR YOUR CONCERN:
- Booting from an SD card is far from a flaw (to me) : Copy aside your data.img, and copy a build over it. You'll never loose your personal data by flashing again
- Hence this : Don't ask for "the best Android rom", all you'll have will be personal opinions, and may not suit you. Try them, it's damn easy, you won't loose your personal data, it's a matter of days
- Ask about the really important stuff : Kernels and Radio, and things like that, but AFTER getting through the other post and thread. Nothing more annoying than a "noob" (and we've ALL been through there, but...) that didn't (at least) try looking for himself.
->Try asking questions, starting with "I've been looking for this, found this, understood this, but need help about that" and you'll see how people will be grateful ^^
mlhazan said:
Thanks for quick reply.Do you know which devices will not work on HTC HD2 if I run Android?Cause little confused here .Some people says wifi does not work ,some says camera does not work.Do you know actually what does not work?
Click to expand...
Click to collapse
To be honest, i just (finally) being able to install Froyo on my HD2, after a lot ROM changing, Radio ect....
I must say, is not really easy to finally find the perfect combination so u can use Froyo as your daily OS (at least for me)...but u will always got XDA, and from my opinion, all the hard work (flashing, changing rom/radio) is really worthed....
so far i dont have any problem running android on my HD2...
Sorry for my bad english....
I'm posting this in General as I don't have the knowledge to port this or develop a similar version for the Slide and I don't want to clutter up the Development forum.
Team ADX over in the Droid Eris forum came up with this gem; a dual boot Eclair Sense/2.2 AOSP ROM. http://forum.xda-developers.com/showthread.php?t=824072
I don't know if this can be done on our phones, but I thought it possible as you don't need to flash a custom recovery.
man this would awesome... the best of both worlds, run and "stock" ROM so we can still receive updates and still have CM.
i was actually thinking about dual boot just the other day! i dont feel like id be switching back and forth from 2 roms but itd be a great feature for those who do. unfortunately i dont think we have that much developers :/
I was reading the instructions for it and it looks like we'll have to wait for S-OFF before we can try it.
Part of the scripting is telling the phone how to partition the phone, sizes of those partitions, and so on. The slide is, generally speaking, un-brickable and it's the measures used to give us that luxury that also prevent us from doing so much like R/W on the system while in a non-recovery boot and changes we do make while booted are just wiped on reboot *sigh* man I love that ramdisk image.
Once we get S-OFF let's get this project started
KCRic said:
I was reading the instructions for it and it looks like we'll have to wait for S-OFF before we can try it.
Part of the scripting is telling the phone how to partition the phone, sizes of those partitions, and so on. The slide is, generally speaking, un-brickable and it's the measures used to give us that luxury that also prevent us from doing so much like R/W on the system while in a non-recovery boot and changes we do make while booted are just wiped on reboot *sigh* man I love that ramdisk image.
Once we get S-OFF let's get this project started
Click to expand...
Click to collapse
I don't think S-OFF is the issue. The partitioning instructions only refer to sdcard. This command:
Code:
mkpartfs primary fat32 0 3500 (can be adjusted to your needs. This partition will be used by the 2.1 rom and by recovery)
I think is only for the phone ROM storage and the for the recovery to find the boot scripts. According to the instructions, they're only partitioning the sdcard to run the AOSP ROM in it. They install the 2.1 Sense ROM to the phone, get it set up, run the boottosd script to boot into the 2.2 AOSP ROM on the sdcard, then set that up and run the boottophone script to go back to 2.1 Sense. They're running a ROM on the sdcard!
As I said before, I think something like this can work for our phones because it doesn't require flashing a recovery. The problem is we don't have the devs to do it.
heybobitsme said:
I don't think S-OFF is the issue. The partitioning instructions only refer to sdcard. This command:
Code:
mkpartfs primary fat32 0 3500 (can be adjusted to your needs. This partition will be used by the 2.1 rom and by recovery)
I think is only for the phone ROM storage and the for the recovery to find the boot scripts. According to the instructions, they're only partitioning the sdcard to run the AOSP ROM in it. They install the 2.1 Sense ROM to the phone, get it set up, run the boottosd script to boot into the 2.2 AOSP ROM on the sdcard, then set that up and run the boottophone script to go back to 2.1 Sense. They're running a ROM on the sdcard!
As I said before, I think something like this can work for our phones because it doesn't require flashing a recovery. The problem is we don't have the devs to do it.
Click to expand...
Click to collapse
I'll take a look. No promises as I'm an übernoob but I would love to have this.
Sent from my T-Mobile myTouch 3G Slide using XDA App
migueltherocker said:
I'll take a look. No promises as I'm an übernoob but I would love to have this.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
You won't be able to do a simple port. I posted about it more of as a proof of concept. Take the same idea, but obviously using our espresso sense and CM6.
heybobitsme said:
I don't think S-OFF is the issue. The partitioning instructions only refer to sdcard. This command:
Code:
mkpartfs primary fat32 0 3500 (can be adjusted to your needs. This partition will be used by the 2.1 rom and by recovery)
I think is only for the phone ROM storage and the for the recovery to find the boot scripts. According to the instructions, they're only partitioning the sdcard to run the AOSP ROM in it. They install the 2.1 Sense ROM to the phone, get it set up, run the boottosd script to boot into the 2.2 AOSP ROM on the sdcard, then set that up and run the boottophone script to go back to 2.1 Sense. They're running a ROM on the sdcard!
As I said before, I think something like this can work for our phones because it doesn't require flashing a recovery. The problem is we don't have the devs to do it.
Click to expand...
Click to collapse
Ok that makes sense. I thought it was pointing to the partitions on the phone telling it to format to a different size for some reason. Then what's preventing us from doing this? Just a lack of a proper script?
I have not poked around with how they are going about doing everything, but I was the one who got the ball rolling with my dual boot linux script. Conap took the basic setup and made some changes to just install them both on the phone and sdcard. Here is the basic of what it is doing....
The init.rc file found in boot.img has been modified for the froyo rom on the sdcard. The lines where it mounts [email protected] , [email protected], and [email protected] have been changed to the partitions on the sdcard (/dev/block/mcblk0px) The updater-script for froyo has been modified to flash the rom to the partitions on the sdcard. There are some gscripts which are ran from the phone that either modify or replace the boot.img for the rom you want to boot into.
The froyo ROM is running completely off the sdcard and the recovery is left untouched. The script that is required if you are using clockworks is because clockworks sbin and folder locations are setup a little different. I was running into some problems with froyo not recognizing the sdcard after making more than 4 partitions. Several had reported to me that their phones also did not recognize the sdcard, but the Eris phones somehow still did. I am working on something that should run from all android phones and allow you the option of installing whatever ROM you want.
One Last Thing..
Anyone is capable of learning how to do some development work. It just takes some patience and "Google". I had no knowledge of linux or any other scripting languages, except windows batch scripts, until 3 months ago.
There is not much activity on my thread, but once I get a working version finished it will be posted there-----Dual Boot Android
When you get it done and own working, post it in development. I only posted the thread in general because I knew I wasn't going to be the one to develop it. I'm a welder by trade and java and linux are a little beyond me. Although I am trying as I'm using Ubuntu as my main OS and starting reading java tutorials.
Sent from my CM6 Slide
heybobitsme said:
You won't be able to do a simple port. I posted about it more of as a proof of concept. Take the same idea, but obviously using our espresso sense and CM6.
Click to expand...
Click to collapse
If there was ever a reason to get a dev started on a project, this would be it. I would reconsider upgrading from the Slide if we had something this awesome.
unCoRrUpTeD said:
I was running into some problems with froyo not recognizing the sdcard after making more than 4 partitions. Several had reported to me that their phones also did not recognize the sdcard, but the Eris phones somehow still did. [/URL]
Click to expand...
Click to collapse
From what I understand, android can not *see* more than 4 partitions so they had to do something a bit different. Somewhere in the thread that's linked it states what they did to get it to work.
s off is tmobs response to....
KCRic said:
I was reading the instructions for it and it looks like we'll have to wait for S-OFF before we can try it.
Part of the scripting is telling the phone how to partition the phone, sizes of those partitions, and so on. The slide is, generally speaking, un-brickable and it's the measures used to give us that luxury that also prevent us from doing so much like R/W on the system while in a non-recovery boot and changes we do make while booted are just wiped on reboot *sigh* man I love that ramdisk image.
Once we get S-OFF let's get this project started
Click to expand...
Click to collapse
The "companies" wanted s-off due to the large number of brix getting returned for handest exchange and assurion claims, just to figure out somebody pooched sumthin up trying to be a HAXOR, if you haven't done anything like this before. Id suggest peeps get a g1 or some other root & rom-o-matic type for and play with it till you take on your brand new handset trying to install some bleenin edge hack...
You gotta learn to wank off before you can try it with somebody else in the room.
I remember my early days at xda, hacking my mda, xcaliber, and esato hacking SonyEricsson fones before they jumped the shark. People who had the ability to read and follow directions (emphasis on the read part) would study till they were sure they would still have a working fone at the end. Hung out and did great stuff with there handsets. And the noobs were wary enough to investigate before they just started mucking about.
So the handset manu. Had to do sumthin and now we have s-off.
the moral of my high and mighty rant an rave, if you don't know how to do sumthing or if you understand what to do but not the why, then keep reading, read more do less
KCRic said:
From what I understand, android can not *see* more than 4 partitions so they had to do something a bit different. Somewhere in the thread that's linked it states what they did to get it to work.
Click to expand...
Click to collapse
In the newest builds they have 2.1 system on the phones system partition and froyo system on the phones data partition. The data is moved to the SD. 2.1 and previous Rome had no problem with extra partitions on the sdcard.froyo changed the way it mounts the sdcard and could only see 4.
I am actually releasing a dual boot method very shortly that should work on any android phone with very little setup required on your part. I am in the process of finalizing it. Anyone interested in testing please let me know as I want to test on as many devices ad possible
Sent from my HERO200 using XDA App
i want to install android on my windows mobile phone on this htc xv6900 (touch), and i have no idea how to do it on a windows, in case if nothing works out on the flash with android i can always go back to windows.
thanks
I tried doing what your doing last night, i regret it so much... Its called NAND and it replaces windows mobile with android but my phone wont activate anymore :/ cant make calls or anything(using verizon). Im trying to get help with it but for now, unless you have a person guiding you through, i recommend doing it the microSD way for now.
First, i'd choose which android version you want, Froyo is a bit slow on the vogue but its usable.
Heres Froyo: http://forum.xda-developers.com/showthread.php?t=712310
Um if you want something faster but good(not as good as froyo) get myn's warm donut. Its the fastest android for the vogue. And the sd way, use this tutorial: http://techf1.blogspot.com/2010/04/coming-soon-installing-android-21-on.html
If you wanna risk your phone, go with NAND. Im not sure how to backup the phone files but find out from someone and to be safer, plug in your phone with activesync running and go to my computer and go to your phone and then copy the contents of the internal storage. Hope i helped you change your mind about that or at least cautioned you and showed you a safer way.