Database Develop

New to Android or NAND?

I'm no longer keeping up with NAND on the vogue. So if anyone would like to keep me informed and email me or post me on any changes with NAND, ill be happy to add the news on the first post. The lock up issue with NAND has been fixed!
This is simply for any noobs or others who are having issues with Android and NAND.
IMPORTANT!!!
FOR VOGUE USERS ONLY
I am not responsible for any bricked or messed up devices. By continuing you are agreeing to my simple rule.
MY SIMPLE RULE: I owe you nothing.
I will help you through the way though if you bricked or need any sort of help.
How-to Video up NOW!!!
http://www.youtube.com/watch?v=3gTkJkOc7m4
​
First off, What is NAND?
To keep it simple...its your phones internal memory. Up untill recently we (Vogue Users) had to run Android off our SD cards using HARET. But thats another story.
What are the benefits of running from NAND? (based on what I have seen)
-Runs faster
-Longer Battery life
-faster boot up
-can be faster to put together.
-Easier to connect your vogue with android to your pc and sync
-Much more convenient.
So how do I start?
STEP1:
The Build
First you need to find a Build that is usable with NAND. Most Hero builds at this moment are not. Here are some links:
Donut 1.6
http://forum.xda-developers.com/showthread.php?t=591104
Hero
http://forum.xda-developers.com/showthread.php?t=603028
Cupcake 1.5
Method 1 from http://forum.xda-developers.com/showthread.php?t=593786
DO NOT DOWNLOAD ANYTHING JUST YET! I WILL TELL YOU WHEN A GOOD TIME WOULD BE
You may want to consider reading the rest...
STEP2:
Base Files (Most builds will supply these)
For all builds (Except the Link in Cupcake "instructions are givin in the download.) you will need a basic set of base files. The link below contains the 3 basic empty files for all builds and Systems.
http://cid-e5302e6abd554cb9.skydrive.live.com/self.aspx/XDA/Androidstuff.rar
IF
You are using Hero make sure you download hero.user.conf too:
http://cid-e5302e6abd554cb9.skydrive.live.com/self.aspx/XDA/hero.user.conf
-create a new folder called conf
-and place hero.user.conf in your new folder.
STEP3:
Rootfs
After you have the Base files you will need a rootfs. Depending on your Build, you may need a different type then the one I am going to supply you. Most builds will supply you with one. This one is DZO's rootfs.
http://cid-e5302e6abd554cb9.skydrive.live.com/self.aspx/XDA/rootfs.img
STEP4:
Prepare
-You need to clean out your storage on your SD. Make sure you delete everything.
-Create a file called android on your desktop.
-Download the base files, unzip, open folder, and place all 3 in your android folder
-Download the rootfs and place them in your android folder. Make sure you either download DZO's or the one your Build provides.
-Download a System.img. When you download a System most likely it will have a different name such as system-hero-123.img. You need to rename it system. So it should look like system.img . Then place it in your android folder.
-If you are using Hero place your conf folder in your android folder.
-Depending on your Build (mostly Hero) you may also need a Data file. The build you select should supply one. Download it and place it in your Android Folder
STEP5
Placing
Open up your android folder of all your collected files and select all, copy, and paste into your empty SD card.
STEP6
Unlocking
If you have never flashed a ROM before than you don't have HardSPL installed. So unlock your phone with...
http://forum.ppcgeeks.com/showthread.php?t=20370
Make sure you follow the forums directions.
STEP7
Method
Method1: The way I do it.
Download ROMUpdateUtility.rar
http://cid-e5302e6abd554cb9.skydrive.live.com/self.aspx/XDA/ROMUpdateUtility.rar
Extract to a newfolder
Download a kernel with your screen size
http://it029000.massey.ac.nz/vogue/files/?C=M;O=D
Don't know your screen size...check this out
http://forum.xda-developers.com/showthread.php?t=544906
After you have have gotten the kernel:
rename it to RUU_signed and place it in the ROMUpdateUtility folder you created.
NOW you need to plug your phone into your computer. Establish active sync. And run ROMUpdateUtility.
-Follow the Instructions on the screen.
Method 2 and 3 can be found here:
http://forum.xda-developers.com/showthread.php?t=593786
This also shows my method...but a little less detail. You can also find many other helpful things there.
If you fail OR think your bricked your phone.
You will need to download one of these depending on your carrier...Make sure you download the shipped gps rom. (If you are Verizon skip down)
http://forum.ppcgeeks.com/showthread.php?p=191607
Than you will put your phone in boot mode. Hold the Camera and Power button. While holding both of them...get a pen or something small and hit the little restart button on the bottom of your phone. You may have to hold it for like a second.
-you will see three color bars on your phone
-plug your phone into your computer
-run the backup
After your phone is all back to normal. Make sure you run internet explore on your phone. It will enable you to get data.
For Verizon follow the instructions here.
http://wiki.ppchaven.com/index.php?title=Pocket_PC_WIki:FIX_VERIZON_GPS
That is about it. I'm sure I forgot some stuff and will add on to this. Make sure you donate to the Devs for all their hard work.
DZO
http://forum.xda-developers.com/showthread.php?t=593786
jamezelle
http://forum.xda-developers.com/showthread.php?t=603028
plemen
http://forum.xda-developers.com/showthread.php?t=591104
vilord
http://forum.xda-developers.com/showthread.php?t=523692
They deserve it.

thank you this was very helpful

inphin1ty said:
thank you this was very helpful
Click to expand...
Click to collapse
No problem...

yea here is the md5sum: 9b08971e7f23619b6a9a4db9d52d857a

jamezelle said:
yea here is the md5sum: 9b08971e7f23619b6a9a4db9d52d857a
Click to expand...
Click to collapse
Whats that?

staud8469 said:
What are the benefits of running from NAND? (based on what I have seen)
1 Runs faster
2 Longer Battery life
3 faster boot up
4 can be faster to put together.
5 Easier to connect your vogue with android to your pc and sync
6 Much more convenient.
Click to expand...
Click to collapse
great thread. I've run both from nand and sdcard. i have not messed with ext2 on the sdcard.
I agree with 3 for sure. I would also add that there is a deep gratification in wiping win mo off the sdcard
6 is debatable, depends on which conveniences you want. changing lcd.density, changing resolution are all much faster running from the sdcard - no flashing or messing with build.prop, just edit default.txt and reboot (aside - if you have a non-sdhc card you can flash on the fly from the sdcard, but changing lcd.density still requires pulling and pushing files from the system, which is not as easy as changing the default.txt). also more convenient to back-up or revert to a data.img when running from sdcard. definitely booting straight into android is convenient, as is the new mass storage on boot method, as well as having a re-writable system (which you also have using ext2).
1 and 2, I honestly have not noted a significant difference in battery life. With a fast sdcard, I don't think there is a significant difference in speed either - dzo has said this in one of the non-vogue forums as well. i have not tried any sense builds from the sdcard though, and that's where you would notice the greatest difference in speed if there is any.
4 I agree with in general.
I think running from the nand is a huge advance, and great for everyone to try. but, running from the sdcard is still a decent way to use android. choosing between the two comes down to choosing which conveniences suit your usage style the most.
One last thing - please add vilord to your donate links (his google ion on vogue thread), he has been instrumental in developing the ril and advancing android on the vogue. srwalter also deserves mention for his reverse engineering of the libgps.so to bring gps first to cupcake and now to donut as well. jamezelle, plemen, mssmison, zenulator, enatefox, f00bar (no specific order) have all worked hard porting roms and working on things like compcache, swap, modem, etc, which has all been invaluable (zenulator and mssmison deserve special credit for spearheading the porting business). however the gruntwork of porting to the vogue has been done mainly by dzo who brought us the kernel and initial ril and now nand (he's just frickin amazing, he singlehandedly got the first functioning port to the vogue and others helped from there), then vilord who took the ril and really refined it. I guess suffice to say, there have been a lot of people involved along the way, thanks to all of them.

when i try to run android from both nand and haret i always get an error about not being able to mount sd card. does this mean i need to reformat the card? if so how do i do this?

Barogi44 said:
when i try to run android from both nand and haret i always get an error about not being able to mount sd card. does this mean i need to reformat the card? if so how do i do this?
Click to expand...
Click to collapse
When do you get this error? During linux kernel bootup?

Verizon users.
I just update a fix for Verizon users. Shows you how to get GPS too!

Also...there will be a video up soon. It seems that there are so many people having issues. So I will create a video from start to finish. Will be posted up late tonight/ tomorrow morning.

staud8469 said:
When do you get this error? During linux kernel bootup?
Click to expand...
Click to collapse
Yea.. i think i may need a new sd card. Can android boot from a 4gb card or is 2 the max?

Barogi44 said:
Yea.. i think i may need a new sd card. Can android boot from a 4gb card or is 2 the max?
Click to expand...
Click to collapse
i running with a 8gig PNY sdcard
it could theoretically run off of a 512, but you would be a little cramped on space
i guess android doesnt like some of them

so really it doesn't matter how big the card is? do they all have to be formatted to fat32?

Barogi44 said:
so really it doesn't matter how big the card is? do they all have to be formatted to fat32?
Click to expand...
Click to collapse
short answer, yes.

Hey guys...I will try my best to get that video up today. I am about to start recording it.

Am I correct in assuming that step 4-b is create a FOLDER name android on the desktop?
Can I delete those files from the SD when flashing is done?
THANK YOU for the N00B instruction, works great.

stopthebus said:
Am I correct in assuming that step 4-b is create a FOLDER name android on the desktop?
Can I delete those files from the SD when flashing is done?
THANK YOU for the N00B instruction, works great.
Click to expand...
Click to collapse
Yes that is correct, as for deleting the files...I would assume you could. But im not sure. Maybe they are still needed on boot. Never hurts to try though.

im not getting access to the internet after i flashed, am i suppose to edit anything?
im running the donut flash on my sprint vogue.

gigermunit said:
im not getting access to the internet after i flashed, am i suppose to edit anything?
im running the donut flash on my sprint vogue.
Click to expand...
Click to collapse
Wait...NVM you want data to work right?

If you are using donut...try to restart your phone one time. After it boots back up you should see a 3g symbol appear on the notification bar.
If that does not work...go to your apps and open modem. Click once on disconnect and then once more. Then click connect.
Tell me if that works...

2.1 voicekeyboard app on 1.6 or 2.0 android

My wife and I use haret to boot android 1.6 and android 2.0 respectively on her vogue and my touch pro. She is not ready to try the full 2.1 ports notwithstanding how amazing it is to have them available for vogue. Anyone know how to install the 2.1 voice to text keyboard on any haret booted android?
I tried the instructions below but no go with our read only system. I also tried adding the app to the android app folder as well as unsquishing, putting the file into the system and resquishing on ubuntu but my new system.sqsh was not mounted. I am way out of my amateur league. Can anyone install this killer app and let us know how they did it.
http://www.megaupload.com/?d=UQC37DJC
This will install the 2.1 keyboard with voice to text working (on any text input that uses the default keyboard).
The original keyboard will not be affected - you will simply have 2 Android Keyboards to choose from in Settings > Language and keyboard (plus Swype, if you have it or install it)
You need to be rooted (which only requires putting an update.zip file on your Droid and rebooting, basically - follow step 2 in that post to root).
To install the keyboard apk, unpack the file and put the VoiceSearchWithKeyboard.apk on your sdcard. Mount system r/w and put the VoiceSearchWithKeyboard.apk in the /system/app folder. chmod it 644 and mount system as r/o and reboot.
If you don't know how to do that, then follow these steps:
1. Put the VoiceSearchWithKeyboard.apk on your sdcard (if you used usb, unplug it when you're done)
2. Get Root Explorer from the Market.
3. Using Root Explorer, navigate to the sdcard folder and long press on the VoiceSearchWithKeyboard.apk and click "Move"
4. Navigate to the /system/app folder
5. Click the button up top that says "Remount as R/W"
6. Click the button on the bottom that says "Paste"
7. Now you need to set the permissions on that file (chmod 644): Long press on the VoiceSearchWithKeyboard.apk and click Permissions. Check User Read and Write, Group Read, and Others Read. Uncheck everything else and click Ok.
7. Click the button up top that says "Remount as R/O"
8. Reboot, you're done
After rebooting, in Settings > Language and keyboard, you will have Android Keyboard listed twice, and they'll both be checked/enabled.
The first one is the original and the second one is the one with voice search. Uncheck the first one. If you have Swype installed, it will still work if you select it (but you probably won't want to!).
It works great (major understatement). No issues that I know of

if you are running regular sd card you won't be able to do this. you need ext2 or nand to rw the system files. should be able to fix permissions using your new install menu (i think ?!?). i'll give it a try and post back, i've been interested in this for a while.

TaDa!
androidupdate.tar
Fixed (forgot to gunzip).
Doesn't work on 1.6.

Thx
I will give it a try. Thx

jnadke said:
TaDa!
androidupdate.tar
Fixed (forgot to gunzip).
Doesn't work on 1.6.
Click to expand...
Click to collapse
darn, was hoping this would work on 1.6

Still having trouble installing
tatnai,
In over head. If I put an ext3 partition on the card with the android files how do I get haret to boot.
If anyone gets it to work if you have time please write a brief idiots guide.
If too busy no big deal. I should be waiting for 2.1 touch pro and not bugging you guys anyway.

spb37 said:
tatnai,
In over head. If I put an ext3 partition on the card with the android files how do I get haret to boot.
If anyone gets it to work if you have time please write a brief idiots guide.
If too busy no big deal. I should be waiting for 2.1 touch pro and not bugging you guys anyway.
Click to expand...
Click to collapse
did you check out the FAQ in my sig? try the SD card install guide, if that does not help, post back in that thread and we'll go through what's not working. also, I don't know if there is any difference with ext3, but most of us have been using ext2 partitions. use two, both 300mb and you should be fine. they need to be after the fat32 partition (so you should have one fat32 with most of the space, followed by 2 x ext2 at around 300mb each). there are partitioning guides in the FAQs as well.

Thx again.
Will give it a try. Thx for your responses and providing the FAQ. Much appreciated.

Easiest Step-By-Step Android Tutorial for the Vogue (NAND Method/Internal Memory)

I have created this post because I was honestly baffled by the NAND install threads for the Vogue that I found, that claimed to be "straightforward" and simple, but the people who wrote them leave a lot of gaps that you have to figure out. Perhaps they have been doing it for so long now, that they just 'assume' you will know stuff, so here are step-by-step instructions for someone who has zero experience with Android, and all they know is that they have a Window mobile phone.
So, Here is the NAND install process (will install Android to your internal memory, which is much better than running from the SD card) for the HTC Vogue (240x320), CDMA or GSM. I believe this is the most straightforward tutorial on this entire site, and all files you need are provided in this post; no file-hunting necessary like with other tutorials. Keep in mind, this process will wipe your internal memory and replace it with Android, so you should backup any personal files you have stored on the phone. If you have a CDMA phone (Verizon, Sprint, etc.) then you should make sure to backup your Contacts using a 3rd party program. GSM phones however (ATT, T-Mobile, etc.), typically store their contacts to a SIM card, which is not altered by this process. You do not need to backup your SD card, since it is also not altered when installing Android.
Dependencies: This process works for any ROM release that provides an "androidinstall.tar" file in their download package.
First and foremost, make sure you have unlocked your phone ("2.31 CoKe" HardSPL for CDMA Vogues). If you have ever flashed a custom Windows ROM from this site or ppcgeeks.com, to your device, then you most likely already have an unlocked phone. If not, perform the steps HERE first, before continuing AND flash to a custom Windows Mobile ROM (non-stock) and make sure your phone is provisioned (you can get and receive calls), and that you can use data (if you have a data plan).
1. Wipe your SD card, and make sure it is formatted FAT32
2. Create a new folder in the root of the SD card called "andboot"
3. Download the ROM release package of your choice (for example, you can download the 240x320 version of Myn’s Warm Donut - [RLS 5 - 04/24/2010] HERE)
4. Extract files from STEP 3 and put ONLY the "androidinstall.tar" file in the andboot folder on the SD card, by itself (no other files are needed)
5. You are DONE putting files on your SD card. At this point, put the SD card into your phone.
6. Download the latest NBH file that begins with "voguimg-240x320-..." (needed for all Vogue Android ROMs): HERE
7. Download the RUU Update Utility (needed for all Vogue Android ROMs): HERE
8. Rename the NBH file to from STEP 6 to "RUU_signed.nbh" and place it inside the folder with all the other files from STEP 7
9. Now, put your Vogue in bootloader mode: Hold down power, camera, and the small reset hole (with your stylus), until you see the tri-color screen, and it says "Serial" at the bottom
10. Plug your phone into your computer, and the "Serial" text should change the "USB"
11. Now, run the "ROMUpdateUtility.exe" from STEP 7, and click the "Next" or "OK" buttons to go through the flash/ROM update process, until your phone shows a progress bar on its screen and is updating.
12. As soon as that progress bar finishes the phone will automatically reboot; at this point unplug the phone from the computer
13. Now, watch carefully during the Linux boot process...there will be a quick message that says "Hold down Volume Up or D Pad". Just press and hold the center D-Pad button until you see the screen change to the installer menu. If you happen to miss it, and it continues loading, then just use your stylus to press the reset button (it will not hurt the phone or any files to try again as many times as you need to.)
14. You will now see a black and white menu. Select option 1, to "Install..."
15. Select "Yes" on the recommended prompt that follows
16. Once it says the Install process is complete and it returns you to the menu, just reboot your phone with the reset button
17. At this point just WAIT. Do NOT press the volume up button again, and do not do anything until you see the Android desktop. You may get an error saying that it could not find a file or something like that, but just ignore it...do not get impatient! Pretty soon the Android progress bar will show on the screen (might take up to 5 minutes), then the Android desktop will load.
DONE. Enjoy Android on your Vogue! You can now delete all the files on the SD card if you wish...Android will recreate anything it needs on boot-up each time.
MASS STORAGE FIX (USB to PC): You can get the Mass Storage fix HERE so that your storage card will show up as a drive on your computer. This is a widget, and not ROM specific, so should work for any Android ROM.
KAISER WI-FI FIX (for the Kaiser phone ONLY!): Download the Wi-Fi fix HERE (intended for use with 'myn's Warm Eclair RLS1', linked in STEP 3)
I do not ask for donations, just say 'Thanks' if this helped you.
***
UPDATE: This Thread is now featured on Wired.com's News Site!! Link: http://www.wired.com/gadgetlab/2010/04/windows-mobile-android/
***

please elaborate on step 8. what are we extracting here

Great post. Just some clarifications I thought would be helpful.
1. reminder to all - you can use SDHC cards for this, those being greater than 2gb, but make sure you format them to FAT32.
5. in some instances there are androidupdate.tar files that go with the build too, in which case that too needs to be placed in the same andboot folder
8. clarification, you'll be replacing the RUU_signed.nbh file with the 320 nbh file you download. So, you'll have to delete the ruu_signed.nbh that came with the update utility, and rename your downloaded 320 nbh to ruu_signed.nbh and place it in the update utility folder so it uses that file instead.
9. to enter bootloader mode you have to press those 3 buttons down for about 2 seconds, not just a quick tap. This bootloader is your failsafe fallback to reinstall if your operating system goes funky.
13. If volume up isn't working for you, try holding down the button in the middle of the directional pad. The last nbh file I used required this instead of the awkward volume-up. Regardless, be sure to do this quickly as soon as the phone reboots itself.
16. After the install process is complete you'll be brought back to the same menu you arrived at by holding down the button on startup, you may then select "update" or "upgrade" from that same menu to activate the androidupdate.tar file you may have copied to your andboot folder. Once done, just select "exit" or reset.
17. He's not kidding, first boot can take a very long time.
If you run into problems and just need a functional phone for a bit, download the nfsfan rom (or any other custom roms), put phone into bootloader and run the nfsfan rom utility from your windows desktop. Don't reinstall a locked carrier-specific rom that you might have used to update your radios otherwise I understand your Coke bootloader gets wiped out and you'll have to do that again. Alternatively, there is an older, dummy-proof Android ION build that will install the entire ION build through the rom update utility to your nand at http://sourceforge.net/projects/androidhtc/files/2009-12-17/androidinstall.zip/download
I'm no super-expert so if I have any misinformation in my post, or there are other shortcuts, please feel free to edit it or let me know and i'll modify it.

MikeMurphy said:
Great post. Just some clarifications.
8. clarification, you'll be replacing the RUU_signed.nbh file with the 320 nbh file you download. So, you'll have to delete the ruu_signed.nbh that came with the update utility, and rename your downloaded 320 nbh to ruu_signed.nbh and place it in the update utility folder so it uses that file instead.
Click to expand...
Click to collapse
where is this file?

CasopoliS said:
where is this file?
Click to expand...
Click to collapse
You're looking for the vogue 320 files, not the vogue eclair 320 files unless you're installing an eclair (2.x) build.
The .nbh files are usually referenced on the build thread in the forums, but if they are not head over to http://sourceforge.net/projects/androidhtc/files/ and download the latest.
(NOTE: I suggest you run at least the Feb 23 build at http://it029000.massey.ac.nz/vogue/files/?C=M;O=D as it enables the openGL support)

MikeMurphy said:
You're looking for the vogue 320 files, not the vogue eclair 320 files unless you're installing an eclair (2.x) build.
The .nbh files are usually referenced on the build thread in the forums, but if they are not head over to http://sourceforge.net/projects/androidhtc/files/ and download the latest.
Click to expand...
Click to collapse
the latest isnt there its here
http://it029000.massey.ac.nz/vogue/files/?C=M;O=D

now now, gents, you're both right - dzo's latest are in one spot, vilord's latest are in the other, and they don't always contain everything the other does. vilord mentioned trying to get them in one spot but I don't know if there's been any progress on that.

it keeps hanging up at the progress bar and both stay at 0% it looks like the active sync is gone once in bootloader it goes gray and then its gone from tray in bottom right corner. it seems like once in bootloader mode i have no active sync connection it just hangs Then the updater goes into its recovery any help please

razorr69 said:
it keeps hanging up at the progress bar and both stay at 0% it looks like the active sync is gone once in bootloader it goes gray and then its gone from tray in bottom right corner. it seems like once in bootloader mode i have no active sync connection it just hangs Then the updater goes into its recovery any help please
Click to expand...
Click to collapse
go into bootloader before plugging your phone in by pressing and holding power button, camera button, and then use stylus to hit reset button.
once you get into bootloader, plug your phone in and then run the rom update

incubus26jc said:
go into bootloader before plugging your phone in by pressing and holding power button, camera button, and then use stylus to hit reset button.
once you get into bootloader, plug your phone in and then run the rom update
Click to expand...
Click to collapse
that is the way that i have been doing it as per the instructions, Any other suggestions? I just did a hard reset and restored the phone to out of the box if that helps out any.
thanks

razorr69 said:
that is the way that i have been doing it as per the instructions, Any other suggestions?
thanks
Click to expand...
Click to collapse
the only reason i said that is because active sync should have nothing to do with it. i dont think active sync should come up or shut down during this process. Do you have the RUU_signed.nbh named properly?

razorr69 said:
that is the way that i have been doing it as per the instructions, Any other suggestions?
thanks
Click to expand...
Click to collapse
Activesync has nothing to do with updates via the rainbow screen bootloader and will not sync.
You have already install the Coke bootloader? What OS are you running?

Thank you so much. Been needing something like this since the other NAND tutorials for Android didn't tell you what files to use or had outdated/non-working links.

MikeMurphy said:
Activesync has nothing to do with updates via the rainbow screen bootloader and will not sync.
You have already install the Coke bootloader? What OS are you running?
Click to expand...
Click to collapse
6.1. I followed the inst.
put the tar in andboot folder on sd
renamed the voug img file put it in the androidinstall folder on my desktop
put the rest of the files from myns donut into the androidinstall folder
then bootloader plug in usb then rom updater
everything goes fine intil it hangs on the progress bar at 0%

razorr69 said:
6.1. I followed the inst.
put the tar in andboot folder on sd
renamed the voug img file put it in the androidinstall folder on my desktop
put the rest of the files from myns donut into the androidinstall folder
then bootloader plug in usb then rom updater
everything goes fine intil it hangs on the progress bar at 0%
Click to expand...
Click to collapse
What OS are you running on your computer?
The ROM update utility really just installs the .nbh file which is somewhat of a front-end loader mechanism. Once that file is installed, then the phone resets, you hold down a button and you enter into the menu that lets you actually install android from the androidinstall.tar file in your andboot folder.
Here is a fail-proof method that I think will resolve your goofy androidinstall folder.
Download this
http://74.53.45.2/~evadmin/nfsfan/Public Releases/Vogue 6.5/ROMS/NFSFAN's WM6.5 1.00 FINAL ROM.rar
Then replace the .nbh file with the vogue 320 nbh. Then, run it when your phone is already in the bootloader screen.

Excellent post
I'm linking this from Warm Donut on the first post.

MikeMurphy said:
What OS are you running on your computer?
The ROM update utility really just installs the .nbh file which is somewhat of a front-end loader mechanism. Once that file is installed, then the phone resets, you hold down a button and you enter into the menu that lets you actually install android from the androidinstall.tar file in your andboot folder.
Here is a fail-proof method that I think will resolve your goofy androidinstall folder.
Download this
http://74.53.45.2/~evadmin/nfsfan/Public Releases/Vogue 6.5/ROMS/NFSFAN's WM6.5 1.00 FINAL ROM.rar
Then replace the .nbh file with the vogue 320 nbh. Then, run it when your phone is already in the bootloader screen.
Click to expand...
Click to collapse
Thank you will try it now. Running xp pro on my desktop

razorr69 said:
Thank you will try it now. Running xp pro on my desktop
Click to expand...
Click to collapse
XP Pro always worked well for me. I'm running Win7 x64 ultimate and recently my phone was recognized as a USB Sync Device in the bootloader mode which doesn't work for the rom update utility. This was occurring both with and without the installation of the MS Mobile Device Center app. To solve this I installed XP Mode and attached the usb device to the XP Mode and it recognized correctly as the Qualcomm MSM thing.
Just an FYI.

MikeMurphy said:
XP Pro always worked well for me. I'm running Win7 x64 ultimate and recently my phone was recognized as a USB Sync Device in the bootloader mode which doesn't work for the rom update utility. This was occurring both with and without the installation of the MS Mobile Device Center app. To solve this I installed XP Mode and attached the usb device to the XP Mode and it recognized correctly as the Qualcomm MSM thing.
Just an FYI.
Click to expand...
Click to collapse
when i go into my computer it just says mobile device

razorr69 said:
when i go into my computer it just says mobile device
Click to expand...
Click to collapse
same result error 262 update error. i dont get it this is so simple. 1 of the 4 steps is establish a connection with active sync dont know how to do that once im in bootloader mode it's like there is no connection but the phone shows the progress bar

Can't Access Installer

I have been trying to install android to NAND on my bell Vogue with no success. I had an early build of MYN's rom installed but I switched back to WM for a while because of battery life issues with android. Now that those issues have been taken care of I would like to switch back to android permanently.
I have been following all of the directions that I have read, but cannot seem to access the installer menu. I have tried holding down volume up, center d-pad and touching the middle of the screen and none of them will work.
I am coming from NFSFAN's latest WM rom with the radio fully updated. I am flashing the most recent Vogue images that I can find and it still doesn't seem to work.
Is there something that I am doing wrong? is there an alternative method to get a permanent install of android?
Thanks!

shabicht said:
I have been trying to install android to NAND on my bell Vogue with no success. I had an early build of MYN's rom installed but I switched back to WM for a while because of battery life issues with android. Now that those issues have been taken care of I would like to switch back to android permanently.
I have been following all of the directions that I have read, but cannot seem to access the installer menu. I have tried holding down volume up, center d-pad and touching the middle of the screen and none of them will work.
I am coming from NFSFAN's latest WM rom with the radio fully updated. I am flashing the most recent Vogue images that I can find and it still doesn't seem to work.
Is there something that I am doing wrong? is there an alternative method to get a permanent install of android?
Thanks!
Click to expand...
Click to collapse
So what do you see when it starts up? Do you see tux and scrolling text?

yes i see all the text, but after it tells me to hold the center button to enter the menu it just continues along and tries to load android (which is not yet installed) and so it fails.
thanks for the reply!

shabicht said:
yes i see all the text, but after it tells me to hold the center button to enter the menu it just continues along and tries to load android (which is not yet installed) and so it fails.
thanks for the reply!
Click to expand...
Click to collapse
try this - do a pinhole (soft) reset, then just after you feel the double buzz, give a good tap in the middle of the screen and hold it.

Ok, Will do. I will try that again... I have tried the middle of the screen before and I have tried holding from as early as right after boot to as late as right when it gives the hold message.

Still no luck... Does anybody else have any ideas as to what might be going wrong?
Also, would it be possible to run via haret and then install to nand somehow?

I tried to install to SD card and I still could not access the installer!
All of my buttons work, but for some reason they are not getting me into the installer. I think this issue started about the time they switched to holding center D-pad instead of volume up.
could I just use an old Vogue img file?
looking for any other ideas!
Thanks

shabicht said:
I tried to install to SD card and I still could not access the installer!
All of my buttons work, but for some reason they are not getting me into the installer. I think this issue started about the time they switched to holding center D-pad instead of volume up.
could I just use an old Vogue img file?
looking for any other ideas!
Thanks
Click to expand...
Click to collapse
What method of install are you using norootfs or the old way

I have been using norootfs. I have never used sqsh would it be possible to install that way?
EDIT: I am trying the SQSH method, but it seems like this is not a permanent install, is that correct? I would really like to be able to run android permanently.

shabicht said:
I have been using norootfs. I have never used sqsh would it be possible to install that way?
EDIT: I am trying the SQSH method, but it seems like this is not a permanent install, is that correct? I would really like to be able to run android permanently.
Click to expand...
Click to collapse
What files do have in the andboot folder

When I was trying to install to NAND all I had in the andboot folder was the androidinstall.tar
when trying the SD card install I used all of the files included in MYN's download.
i am using an 8gb microsd HC card formatted FAT32 which I think is what it is supposed to be.

shabicht said:
When I was trying to install to NAND all I had in the andboot folder was the androidinstall.tar
when trying the SD card install I used all of the files included in MYN's download.
i am using an 8gb microsd HC card formatted FAT32 which I think is what it is supposed to be.
Click to expand...
Click to collapse
you don't have haret or a nbh file in the andboot folder

when trying to install to NAND I have no Haret (I don't think it is required) and in that case the NBH is flashed to the phone, but not on the SD card
when trying to install to SD i have Haret in the andboot folder, but no NBH.

shabicht said:
when trying to install to NAND I have no Haret (I don't think it is required) and in that case the NBH is flashed to the phone, but not on the SD card
when trying to install to SD i have Haret in the andboot folder, but no NBH.
Click to expand...
Click to collapse
Well I have haret,zimage,default.txt,androidinstall.tar, and intrid for my SD install

yes, sorry i was unclear, I do have all of those files when I am trying the SD install (everything that is in MYN's download folder for warm donut REL 5)
thanks for all your help!

Try reformatting the card because I had that issue with my card before but back up the info on the card first

shabicht said:
yes, sorry i was unclear, I do have all of those files when I am trying the SD install (everything that is in MYN's download folder for warm donut REL 5)
thanks for all your help!
Click to expand...
Click to collapse
Your welcome

I did a full reformat as FAT32 and still am having no success

shabicht said:
I did a full reformat as FAT32 and still am having no success
Click to expand...
Click to collapse
Damn try downloading another version of haret to see if that will help

I have been trying all sorts of different versions. Most recently I have tried to install incubus26Jc's superfroyo RLS10 to no avail. Whatever I do I simply cannot get to the installer menu! I have tried holding center d-pad, volume up, camera and the middle of the touchscreen. none of these seem to work for me. Is there anything else I can try or does anybody know a reliable way of flashing to nand without the noMoRootFS method?
thanks!

Latest XDANDROID on CDMA Diamond how-to

Since MrPippy no longer seems to be maintaining the thread over here, I figured I'd bring the latest way to properly run xdandroid on Touch Diamond CDMA devices. This has been tested on my Sprint Touch Diamond (DIAM500), your device may vary.
Android 2.2.2 (Froyo) for CDMA Diamond
Instructions:
From this xda post, download the XDANDROID build (currently 7/05/11).
From the XDANDROID zip file, extract AndroidApps/, conf/, media/, zImage, haret.exe, system.ext2, initrd.gz, modules-*.tar.gz, and rootfs.img into a directory called /andboot/ directory of your Internal Storage. If you extract the folder FRXnn/ (where the nn is the build) you can rename the folder to andboot/.
If you are using DIAM500 (Sprint's CDMA), navigate to FRXnn/STARTUPS/DIAM/DIAM500 inside the zip file, and extract the file called startup.txt into /andboot/ of your Internal Storage. These contain the necessary instructions for Haret to start Android on the Diamond. There are several other types of Diamond config file to try inside the zip file if you are not using Sprint's Touch Diamond, and should be renamed startup.txt if named differently.
The list of files you should have inside the Internal Storage should now look like:
/andboot/AndroidApps/*
/andboot/conf/froyo.user.conf
/andboot/media/*
/andboot/zImage
/andboot/haret.exe
/andboot/system.ext2
/andboot/initrd.gz
/andboot/modules-*.tar.gz
/andboot/rootfs.img
/andboot/startup.txt
Click to expand...
Click to collapse
If you want the older way of having everything in / (root) of the Internal Storage, just move everything from /andboot/ and also delete the argument rel_path=andboot from startup.txt.
Unplug the Diamond from the computer, and run /Internal Storage/andboot/haret.exe to start XDANDROID. If you have not done the calibration, there will be a white square with a cross that you will have to click on a few times. On first boot, it will take time for the system to set up the correct APN for data (usually a few minutes). If you get an error saying that no connection can be made, wait until the 3G icon appears on top before doing anything that requires data (Marketplace, etc.)
---
Optional: Download the latest rootfs Zip file from here.
Extract and rename the file rootfs-*.img to rootfs.img, and replace the one already in your Internal Storage.
Optional: Download the latest kernel bzip file from the links in the xdandroid post (several are provided) using 7Zip. Extract the modules-*.tar.gz and zImage.* file to your Internal Storage. You must then rename the zImage-* file to zImage after renaming/deleting the existing one. If you do not do this, Haret will not use the latest kernel file.
Caveats:
If you are running any previous versions of XDANDROID, it is highly recommended that you delete your data.img. This will wipe all your existing apps and data, but you can save your downloaded apps by going into /data/app and/or /data/app-private and copying it to /sdcard, but you need a root-capable file explorer.
GPS takes a while to get a position fix. It is working, but since there seems to be no AGPS support, it may take up to 15 min for the AGPS chip to get a fix on ephemeral data. Running QuickGPS from WM and keeping it updated seems to help a lot.
If you enable smart backlighting in WM, XDANDROID is unable to set the backlight level. Hopefully this will be addressed soon, since other devices (Rhodium, etc.) now has backlight support working.
If you still have trouble running XDANDROID, then make sure you post at least the following: What type of Diamond you have (model #), the startup.txt you are using (open it in Notepad to see the mtype), the build of XDANDROID you are using (along with any rootfs/kernel updates if applicable), and the last thing it does that you can see (ie. Haret reboots WM instead of running XDANDROID). Without this information, it isn't helping you or the person trying to help in order to figure out what may be going wrong.
A lot of information that applied to Andriod 2.1 (Eclair) also applies to 2.2 (Froyo), with the exception of where the files are located (/ vs. /andboot on the Internal Storage). I've kept Eclair-related instructions below.
Android 2.1 (Eclair) for CDMA Diamond Instructions: (for historic reasons)
From this xda post, download the latest XDANDROID build (currently 6/21/10).
From the XDANDROID 7z file, extract AndroidApps/, media/, zImage, haret.exe, system.ext2, initrd.gz, modules-*.tar.gz, and rootfs.img into the root of your Internal Storage. You must use a computer to extract this, none of the WM/Android apps have enough memory to extract the 7z file correctly!
Create (don't copy) a directory called conf/ on the root of your Internal Storage. Now navigate to conf/Diamond inside the 7z file, and extract the file called eclair.user.conf into the conf/ directory. This is important, you should have a file named conf/eclair.user.conf, not conf/Diamond/eclair.user.conf.
If you are using DIAM500 (Sprint's CDMA), navigate to STARTUP CONFIG/DIAM500 inside the 7z file, and extract the file called STARTUP.TXT into the root of your Internal Storage. If you are having problems with Haret restarting WM instead of booting, you can try the one inside CONFIG/DIAMOND100 or rename CONFIG/DIAM-STARTUP.TXT to STARTUP.TXT. Each file has a different MTYPE, and is most likely the cause of failure to boot into XDANDROID. (DIAM500 mtype 2040, DIAM100 mtype 1805, the unknown DIAM-STARTUP one uses mtype 1910)
Unplug the Diamond from the computer, and run haret.exe to start XDANDROID. On first boot, you cannot connect to Google's server until you have entered an APN (regression bug from 6/12/10.) Skip the account stuff for now, go into Settings→Wireless&Networks→Mobile Networks→APN, and create an APN with Name: Internet and APN: Internet. Press the Home key (to bring up the menu), Save, and then select the APN. You should get the 3G icon in a few seconds.
-- Starfox

Hello, I followed instructions, but there is a loading bar saying booting linux and my diamond reboot, what can i do ?
Thanks

Daedelus87 said:
Hello, I followed instructions, but there is a loading bar saying booting linux and my diamond reboot, what can i do ?
Thanks
Click to expand...
Click to collapse
your not the only one im working on this myself im trying to recreate a zip with it working for diam 500 and the touch pro no matter where i get the files from haret has become a problem and i dont know why so i remaking the files using old haret

ok so i got it working tho got stuck at the sign in part entered my info and then it kept looping back asking for it again and again found the if you restart it youre all set as for gps got a fix in under 30 secs going to repack the files for anyone who wants it this will work for the sprint touch and touch pro if you want the files let me know be more than happy to email them

Good call on starting the new thread. Kind of strange that Mr. Pippy never said anything before he took off.
For pure convenience, it may be best for the OP to compile a weekly build with all necessary files. Noobs might fare better if babied along and that would also assist in keeping this thread focused on more pressing issues.

I keep running into: "failed to mount the Sd card"
Edit: NVM, found the solution

so ran the new droid all night no hiccups but noticed that the time isnt synced it was off by ten minutes tried out the nav. drove to work looked at the time again it was now off by almost 15 mins maybe someone can enlighten me on this issue or is it just me

The only error I am getting is a keyboard error.

I did all steps as described above but if I run on haret.exe it says something like starting linux... but it just restarts the mobile and windows is starting again...
do you have any glue whats wrong?

psg190 said:
Good call on starting the new thread. Kind of strange that Mr. Pippy never said anything before he took off.
Click to expand...
Click to collapse
I think I saw something about him getting an android phone so he wasn't gonna be continuing it, i might be wrong though.
beepme2479 said:
so ran the new droid all night no hiccups but noticed that the time isnt synced it was off by ten minutes tried out the nav. drove to work looked at the time again it was now off by almost 15 mins maybe someone can enlighten me on this issue or is it just me
Click to expand...
Click to collapse
This seems to be an issue check the xdandroid thread and search for "clock" (i think theres an app called ClockSync or something)
NoLeftHere said:
The only error I am getting is a keyboard error.
Click to expand...
Click to collapse
apparently this is common and its due to the lag at startup of transferring files from the sd card... just press wait and it shouldnt be an issue
Flohman said:
I did all steps as described above but if I run on haret.exe it says something like starting linux... but it just restarts the mobile and windows is starting again...
do you have any glue whats wrong?
Click to expand...
Click to collapse
wrong startup.txt? you'll needa post more info about the error probably

Fail?
i think its cuz its only diam 500 not all the other cdma´s like diam 100??
(i mean that fail about startup)

Has there been any progress on metro data yet? This is the only reason why i uninstalled it from my phone. There was progress porting the us cellular data which uses proxies like metropcs for the touch with the android. There have also been native droid devices ported to work on metro as well so in theory it should be possible if anyone wants to work on this drop me a pm or discuss it here.

ok there is a issue with haret i for one can vouch for it the new haret.exe does not boot properly i dont know why or what is wrong but i know the issue is around i have a old haret that i use and works great even the new build has the same problem now if i can only fix my clock sync issue ill be happy

Seannoxious said:
Has there been any progress on metro data yet? This is the only reason why i uninstalled it from my phone. There was progress porting the us cellular data which uses proxies like metropcs for the touch with the android. There have also been native droid devices ported to work on metro as well so in theory it should be possible if anyone wants to work on this drop me a pm or discuss it here.
Click to expand...
Click to collapse
this is all i'm waiting for too.

ok found a fix for the clock still no reboots up and running for 26 hours now been unplugs for 7 hours and im at 34 % battery talk time 27 mins and lets say 5 text messages id say thats damn good

Great How-To post, got it working on my Diamond without any issues at all. Learning how to actually use Android is another matter.
notes:
mapping doesn't work, I presume it's because the GPS stuff is not functional
some of the hardware buttons are a bit confusing, just a matter of experience but it will take some getting used to
the device EATS battery power, and gets crazy hot when you start playing with the browser and other Android apps'
lack of any USB connectivity (beyond charging) is sort of limiting, hopefully it will be improved
so far I'm so impressed with XDANDROID, not that I hate Windows mobile but it is a great way to preview Android, especially for people like me who've only use WM.

[*]mapping doesn't work, I presume it's because the GPS stuff is not functional
Click to expand...
Click to collapse
It works with the latest updates and navigation with sattelite view is awesome but yea battery is a big drawback... keep a charger handy lol
-------------------------------------
Sent via the XDA Tapatalk App
Ps. And I mean xda on your phone is great

How loud is everyone's in-call volume? Mine is so quiet I can barely hear the other person.

RE-alive xandroid HTC DIAMOND 500 CDMA
Starfox said:
Since MrPippy no longer seems to be maintaining the thread over here, I figured I'd bring the latest way to properly run xdandroid on Touch Diamond CDMA devices. This has been tested on my Sprint Touch Diamond (DIAM500), your device may vary.
Android 2.1 (Eclair) for CDMA Diamond
Click to expand...
Click to collapse
Thanks Starfox for taking again this development,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I will try again Xandroid and this forum seems to be the only resource for our HTC diamonds CDMA. Thanks a lot and thanks all the people helping each other here.

APN Setup: http://forum.xda-developers.com/showpost.php?p=6799315&postcount=8296