Related
Hi all...
i have problem for My treo 750..
stuck in Alige screen...(toucscreen respon)
so, i want to reflash to Other ROM...Via PC.
But i download ROM not Include RUU and bla..bla...bla...Only CHEEIMG.nbh
Please any one give me Link to Download RUU Only...
thanks
hiks...no respone
A work around for the non responsive 750 touch screen
After taking my 750 appart several times I came accross a great little program that will let you install an application on your 750 from your pc while in guest mode in active sync. The program is "EveryWAN Remote Support Personal Edition" its a free download and works great. You will see your 750 on the screen of your pc and you can do wlmost everything. But you still won't be able to align the screen. but you can select running tasks on your 750 and stop the welcome application. this gets you past the only screen preventing you from using the 750 as a non touch screen phone. So far there are only two things I can't do without the stylis 1: set the alarm, 2: while running tcpmp I can't open a file not associated with the player.
Hope this helps.
hi....simply download this file http://www.sendspace.com/file/8ger2y
extract it c:\treotemp\ then simly delete RUU_signed.nbh and copy your CHEEIMG.nbh and rename it to RUU_signed.nbh. Now just start ROMUpdateUtility.exe and do the job ;-) ...no matter what picture says it's wm 6.5....it's rom that you copied ;-) enjoy....
Alrighty so here is the issue.
I got a new AT&T Fuze and tried to load "RaphaelHardSPL-Unsigned_190_1_3".
1) I load Windows Mobile Device Center
2) Run the aphaelHardSPL-Unsigned_190_1_3 exe
3)THe load bar comes up, HTC screen goes black and then the loader fails at %0.
4) It gives the 262 error
5) I take the battery out, turn on and phone is fine
What is the problem?
Ps...
This on on my Visa 64 sp2
ROM Development Thread
UndertoW said:
Alrighty so here is the issue.
I got a new AT&T Fuze and tried to load "RaphaelHardSPL-Unsigned_190_1_3".
1) I load Windows Mobile Device Center
2) Run the aphaelHardSPL-Unsigned_190_1_3 exe
3)THe load bar comes up, HTC screen goes black and then the loader fails at %0.
4) It gives the 262 error
5) I take the battery out, turn on and phone is fine
What is the problem?
Ps...
This on on my Visa 64 sp2
Click to expand...
Click to collapse
Have you searched in the Raphael ROM Development thread. I believe this is covered in that thread.
I did check the forum and an extensive google search with no useful information found......not that it's not there.....just that i could not locate it.
Any specifics or a link would be much appreciated.
thanks in advance
Rinse and repeat.
I occasionally get a an error when flashing a new ROM, Radio etc. just try again if that fails seek advice from the wiki/appropriate thread.
mcspikesky said:
I occasionally get a an error when flashing a new ROM, Radio etc. just try again if that fails seek advice from the wiki/appropriate thread.
Click to expand...
Click to collapse
I tired it about 4 or five times...all with the same error code.
do you know where i can find these appropriate threads?
thanks in advance
Still looking for some advice help bump
I am having the same problem with the same Vista set-up. I've even tried running the RUU and Windows Mobile Device Center in compatability mode, with no success.
Ok, I just figured it out. do not start the Mobile device center in Vista. Just make sure that the phone shows up as a device under my computer. took about 10 seconds to flash after that. (and I had the sim and sd card removed for good measure).
Thank you very much...i'm now up and running 4.5 and love it.
Thank you dkevinscott very much for you time and help!
how to flash my htf fuze.
hi, is anyone can get me a hand to flash my htc fuze, thankyou very much.
I'm still getting this error.... anyone have a work around? I have XP
i had same problem it came down to qualcomm drivers .no workaround for me just used vista
ITT: People who refuse to spend 10 minutes reading for themselves
Same problems
Hi there,
I have a Xperia X1 and i'm trying to upgrade to 6.5 aswell.
Everytime i launch the exe file (Kovsky customRUU) it'll give me a 262 error.
I'm running vista and didn't run mobile center.
The X1 appears in my explorer though.
But still. It's a nogo.
Pls help
HTC Touch Pro, Fuze HardSPL Error 262 FIX
Alright, this is how i fixed my 262 error after ripping out all my hair for a week.
- Plug your phone into any working usb port (make sure Active sync is up and running)
- Run RaphaelHardSPL-Unsigned_190_1_3.exe and on the first screen pop up, 9 files will be created in the directory you run the .exe from.
- Copy these 9 files to another folder because you will be clicking cancel on the pop up which will in turn erase the 9 files it created.
- Click cancel on the pop up.
- Go to the folder in which you copied these 9 files to.
- Run ROMUpdateUtility.exe and the same screen pop will appear as before.
- Follow the prompts and it should work.
i had this exact same error. this worked flawlessly. thanks!
xidesu said:
Alright, this is how i fixed my 262 error after ripping out all my hair for a week.
- Plug your phone into any working usb port (make sure Active sync is up and running)
- Run RaphaelHardSPL-Unsigned_190_1_3.exe and on the first screen pop up, 9 files will be created in the directory you run the .exe from.
- Copy these 9 files to another folder because you will be clicking cancel on the pop up which will in turn erase the 9 files it created.
- Click cancel on the pop up.
- Go to the folder in which you copied these 9 files to.
- Run ROMUpdateUtility.exe and the same screen pop will appear as before.
- Follow the prompts and it should work.
Click to expand...
Click to collapse
work!!
man i spend two days without sucess.this working .thnx
my friend wants to update to OS 6.5.
he changes the file name to "Kovsimg.nbh" and put it in Memory card.
he tries to update by following instructions.
after he sees 4 Color on screen, the screen shows "loading". but that Loading takes long time and nothing happen after that.
keep on showing "loading".
what should he do?
Have you done HARD Spl first?
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
Help required please. I want to HSPL my phone but i need an internet connection to do that. The problem is whenever i install activesync and connect my phone, the wireless internet on my laptop just don't work even after disconnecting my phone and i have to restore my windows to a time before i installed activesync in order to make my wireless connection work again. Please help me to solve this problem any setting in activesync i need to change to make it work? I will really appreciate your help.
Delete and recreate your sync relationship.
Make sure you select enable wireless connections while sync'd.
Regarding HSPL, have you tried thre manual install first? Otherwise it'll cost you.
Also, with the auto install or installing via RUU.exe active sync will disconnect and only USB connection will remain so it should be able to connect to the network during install.
I have resync many times but my internet doesnt work. It doesnt even work after removing the phone from active sync. The only way to make my connection work again is to restore my computer to a date before installing the activesync. Anyways i will try to connect it through my office computer if it didn't worked again.
And i am installing HSPL for the very first time so pls guide me on this, what's a manual install. I went through this thread
http://forum.xda-developers.com/showthread.php?t=520312
and going to install through this file " Topaz-HardSPL_V5_00R5_183HSPL.zip ". Am i doing it correct? And i dont have to install HSPL 1.33 before installing 1.83, i can start directly from 1.83 right??? And after that i will install the energy ROM through storage card method. Please confirm that i am doing it correctly. Any help regarding this will be highly appreciated.
Not sure about your ActiiveSync issue. So you instsall AS and you no longer can access internet from PC? What OS are you running? If its Vista, you use Windows Mobile Device Center, which replaced AS.
Regarding HSPL, I will be brief in my explanation and point you back to the thread and search for my posts as I have posted instructions there many times, they just get buried in the many pages.
There are 3 methods to flash;
1. Auto Install, where you download the Topaz-HardSPL_V5_00R5_183HSPL.zip and the enablenewrapi. cab, copy and install .cab to your device, sync to PC, then run .exe.
This method will ask you to donate and will not work unless you do.
2. Flash from SD card, you can rename any .nbh file to TOPAIMG.nbh, place in the root of your SD card, enter bootloader mode (search for instructions) and it will initiate the flash.
3. Custom RUU, find and download Topaz RUU.exe, place .nbh file in same folder as RUU.exe, sync your device to you PC and run the RUU.exe.
I use #3 exclusively and have never had an issue, others get stuck at 0% progress an have to soft reset.
I believe you need to flash 1.83, then flash to 2.51 but I am not 100% sure you can't flash directly to 2.51. Do not bother flashing 1.33.
I have provided tools for #2 and #3, #1 exe and cab are available in the HSPL thread.
If you thoroughly read all of my instructions and it does not work, your only option will be to pay through the auto install method and if you encounter issues open a ticket as instructed in the thread.
Thanks a lot. I will try the #3 method. And will post how it went. Thanks again.
I tried both the SD card and manual method and placed the "customRUU.exe" and the "1.83 nbh file" in the same folder in my PC and while activesynced i lauched the cutomRUU.exe but after going into that tri color screen and then into usb mode it just stucks at 0% and nothing happens. I waited for like 5 mins but it just got stuck at 0%. What should i do now?
BTW i have flashed my TD2 with the original ROM update of WinMo 6.5 before.
help
adnanbaig18 said:
I tried both the SD card and manual method and placed the "customRUU.exe" and the "1.83 nbh file" in the same folder in my PC and while activesynced i lauched the cutomRUU.exe but after going into that tri color screen and then into usb mode it just stucks at 0% and nothing happens. I waited for like 5 mins but it just got stuck at 0%. What should i do now?
BTW i have flashed my TD2 with the original ROM update of WinMo 6.5
At me too most
I do not know what to do help please
Click to expand...
Click to collapse
All,
for those who have Windows 7 and run with Office 2010 64bits it's not possible to sync your phone. The solution is to deinstall office 2010 and install office 2010 32 bits. You don't have to save your settings and files, after installing your system find everything incl. account setting
I still had sync problems; the second time i pluged in, my pc did not find my phone. Looking on internet i found the next solution and after trying i must say it works;
Same issues!
Here is what I have done:
Step 1: Connect my Samsung Omnia (SCH- i910) Touch Diamond II to the USB Port of PC. Windows automatically installed driver in device manager called "Microsoft Windows Mobile Remote Adapter." Windows Mobile Device Center automatically loaded.
Step 2: With WMDC running, I can browse all files on device, my storage, and storage card. I have options to add/delete programs. I can sync with Windows Media Player. I can also download all pictures and video files to the PC with a single click!
All this is great but the MOST important thing to me is to sync my Contacts with Microsoft Outlook. When I press "sync", if it hasn't tried to start automatically, the green icon in tray spins, everything looks like it's going to work but nothing. It just hangs there till I finally cancel and exit. Looking through other tips, I read something about windows firewall. I have enabled the recommended entries as well as disabling firewall completely with no results.
Further testing, I can sync mobile favorites if I uncheck all others but still can not sync Contacts. Need a fix!
All,
be also aware of remove hardware, then remove generic serial rejecten.
Regards, John
Windows 7 and Office 2010 can sync with Touch Diamond. First you must setup mail account in Outlook, and it must be default mail client, and then everything can be synchronized. Windows Mobile Device Center is prerequisite 32bit or 64bit version, depending of Windows 7 version
cheers rikee