Anyone got any problem when upgrading Rom on WIndows Vista and using the Windows Mobile Device Center instead of the traditional ActiveSync? It won't seems to connect to the device again once the device is restarted into the RGB screen [after the starting the Rom upgrade process]. After a few seconds, it got the connection error code on your PC. I soft reset the device and no upgrade has been installed. Any ideas?
I try removing the connect via USB check box and use Mtty to check the connections to my device. But after I have done that, the PC won't connect my device to my computer at all... hence, I can't get use Mtty to check the connections.
So I have no idea why this is happening on Vista. It works fine when I am using my old XP computer when I upgrade to the test ROM. Any suggestions will be appriciated. Thanks a lot of your help in advance.
Pete
http://www.modaco.com/Upgrading-to-Vista-Be-aware-RUUs-wonand39t-work-t251768.html
Looking to upgrade to Windows Vista? You might just want to keep an XP partition on your machine, as ROM upgrades via the normal RUU client do NOT work from within Vista, due to changes in the way the OS accesses the device. This also prevents IMEI-check unlocks from working on Vista.
Click to expand...
Click to collapse
Problem lies with vista, but I have read somewhere a solution is underway, or allready here...
I was attempting to flash my ROM to wm6 crossbow, I used Lokiwiz 02b to CID unlock my G3 wizard. Then, I attemped to flash the rom using the RUU. The Shelltool .exe never finished flashing the rom (even after 1.5 hours), so I disconnected the USB and tried to re-sync Windows Mobile Device Center (using Vista 32) as per the directions, but it would not detect the phone. I then entered bootloader mode and tried to run the RUU that way, but vista crashed the program if no sync connection is found. So, I downloaded the latest t-mobile ROM, and flashed the phone through bootloader (curiously the flash seemed to work using t-mo's RUU) and it installed to 100%. However, the phone will not get past the white splash screen. This is what it displays:
IPL 2.26
SPL 2.26
GSM 02.25.11
OS 2.26.10.2
I tried to un-rar the tmobile exe to a new folder and replaced the nk.nbf file with the file from the crossbow ROM. The t-mo RUU wouldnt read it properly and it crashed. Now the phone is sitting on my counter with it's battery pulled out for fear it mat discharge completely. Since i can get into bootloader mode with the "USB" display at the bottom, I know the device isn't bricked, but what can I do to get it up and running and hopefully flashed to wm6 crossbow? Thanks for any help!
snootch said:
I was attempting to flash my ROM to wm6 crossbow, I used Lokiwiz 02b to CID unlock my G3 wizard. Then, I attemped to flash the rom using the RUU. The Shelltool .exe never finished flashing the rom (even after 1.5 hours), so I disconnected the USB and tried to re-sync Windows Mobile Device Center (using Vista 32) as per the directions, but it would not detect the phone. I then entered bootloader mode and tried to run the RUU that way, but vista crashed the program if no sync connection is found. So, I downloaded the latest t-mobile ROM, and flashed the phone through bootloader (curiously the flash seemed to work using t-mo's RUU) and it installed to 100%. However, the phone will not get past the white splash screen. This is what it displays:
IPL 2.26
SPL 2.26
GSM 02.25.11
OS 2.26.10.2
I tried to un-rar the tmobile exe to a new folder and replaced the nk.nbf file with the file from the crossbow ROM. The t-mo RUU wouldnt read it properly and it crashed. Now the phone is sitting on my counter with it's battery pulled out for fear it mat discharge completely. Since i can get into bootloader mode with the "USB" display at the bottom, I know the device isn't bricked, but what can I do to get it up and running and hopefully flashed to wm6 crossbow? Thanks for any help!
Click to expand...
Click to collapse
Well Friend I hate to say it but Using Vista is your problem... The drivers in WMDC are different from those of activesync and thus Vista cannot talk to your phone in bootloader.
Follow this thread here:
Updated!!(10/20/2007) UPGRADE YOUR PHONE WITH WINDOWS VISTA!!! PROVEN METHOD!
Once you complete the steps in that thread, flash the Official T-Mobile Rom. I will be online for the rest of the night so I will walk you through everything if you would like me to. My AIM, Yahoo, and MSN messenger addresses are all at the top of every one of my posts.
First off, let me thank you for your help, as well as the time you have put in the community helping people like me. I had updated the driver before, but I guess several attempted flashed had overwritten the driver. Just now, I followed the link you gave me, updated the drivers, and flashed the T-mobile 2.26 ROM. The problem still remains. The RUU goes to 100%, shows me the finish/exit screen, mu wizard restarts, but hangs at the white boot screen and does not go any further.
Anyone? Need to get this phone up quick, as I am starting a new job soon and need the capabilities. BTW, i'm going to put XP on this laptop in dual-boot and see if I can get the t-mobile ROM to load fully using XP.
snootch said:
Anyone? Need to get this phone up quick, as I am starting a new job soon and need the capabilities. BTW, i'm going to put XP on this laptop in dual-boot and see if I can get the t-mobile ROM to load fully using XP.
Click to expand...
Click to collapse
If you can manage that, you will be set. All you have to do is create a hard drive partition and install xp to that partition.(from what I know anyway)
OK, i'm gonna try that (my internet is dropping every 5-10 secs, so it'll take a little time) I do have one question though- Last time I used Loki's unlocker, I unlocked the SIM, then the CID unlocker. After the CID unlocker, it locked me out of the phone. The OS wouldnt load unless I provided an unlock code. Then i reflashed it, then the problems started. I think i didn't have it CID unlocked properly. Plus having my miniSD in the slot probably didnt help things either. I've read the directions several times, and I dont see what i'm doing wrong. Could you maybe shed some light on what i'm doing wrong? Thanks!
EDIT: Also, I forgot to mention that I tried to do a hard-reset (hold wireless manager + voive command buttons + soft reset) and when you press the send button, it tells me unable to format FAT volume or something like that. Upon reading around, it seems like i'm having the exact same problem as this poster: http://forum.xda-developers.com/showthread.php?t=338315
snootch said:
OK, i'm gonna try that (my internet is dropping every 5-10 secs, so it'll take a little time) I do have one question though- Last time I used Loki's unlocker, I unlocked the SIM, then the CID unlocker. After the CID unlocker, it locked me out of the phone. The OS wouldnt load unless I provided an unlock code. Then i reflashed it, then the problems started. I think i didn't have it CID unlocked properly. Plus having my miniSD in the slot probably didnt help things either. I've read the directions several times, and I dont see what i'm doing wrong. Could you maybe shed some light on what i'm doing wrong? Thanks!
EDIT: Also, I forgot to mention that I tried to do a hard-reset (hold wireless manager + voive command buttons + soft reset) and when you press the send button, it tells me unable to format FAT volume or something like that. Upon reading around, it seems like i'm having the exact same problem as this poster: http://forum.xda-developers.com/showthread.php?t=338315
Click to expand...
Click to collapse
Although,many have successfully flashed using vista,but I'll suggest in your condition flash through WinXP. Download the official carrier's Rom from it's website.
1. Disconnect your phone from the usb cable,shut down any firewall,disable any Anti virus,Reboot your PC.
2. On your Desktop PC, open Microsoft ActiveSync, then go to File >Connection Settings >Remove the Selection from “Allow USB Connection with this desktop computer”
3. On your PC Open windows Task Manager...>Tab Processes...>wescomm.exe...>End process
4. Power off the phone completely (Not stand-by,shut off completely),or you may take the battery out for few seconds
5. Make sure your phone is not Connected to the PC via USB cable and remove the dummy Sdcard or mini-Sd card
6. Get your phone into Bootloader mode (Multicolor screen) by pressing camera button + Power on button
7. Reconnect your phone to the Desktop PC using the USB Cradle and the Charger MUST be Connected to the Cradle (Be sure that your battery is charged over 70%)
8. "USB"will appear on the bottom of the screen of the Bootloader (Multicolor screen)
9. Run the Upgrade again and it will work fine without any problems.
10.Never use Bluetooth sync for the Upgrade
While upgrading, the ActiveSync program will not go on, however the upgrade is running.Please be patient when you're flashing your device, even if 98%. It can wait a little bit, 5 ~ 7 minutes.
Don't cancell the flash or get the phone off the usb cable till it confirms "Congratulations" or stops with an Error!!!
Hope it'll recover back to it's default status,good luck
I'm going to assume I don't have to CID unlock it until I want to switch from the T-mobile 2.26 ROM? I am about to install XP dual-boot shortly. I'll post my results when it's done. Thank you.
snootch said:
I'm going to assume I don't have to CID unlock it until I want to switch from the T-mobile 2.26 ROM? I am about to install XP dual-boot shortly. I'll post my results when it's done. Thank you.
Click to expand...
Click to collapse
As long as you are going to keep T-Mobile 2.26 on your device or are restoring T-Mobile 2.26, you do not have to CID unlock but should you decide to change to another Rom, you will need to CID unlock.
Good luck on the dual boot. There is a detailed tutorial in my Signature if you would like to take a look at it. After I can restore my crashed laptop, I am going to take care of the dual boot also.(I have to do it again... )
I really want to put WM6 on my wizard, and customize it the way I want it. Do you have any favorite WM6 ROM? All day yesterday I spent trying to add a WinXP partition to my Vista laptop. Not fun. First, I shrank the only partition on the drive (where Vista is installed) using Disk management, the Diskpart.exe to create a new 2.5Gb partition to install XP on. I rebooted the labtop with a XP disk, and installed XP on the partition. After the laptop restarted the first time, it did not come back up (black screen, no CD activity), So I changed the boot options in BIOS to HDD, and the Vista partition responded with "Error loading operating system" on a black screen. So now, i've got a laptop with a corrupted Vista install, A partition with partially installed XP on it, a XP disk that just quits working, and my wizard is shot. Normally something I can deal with if I had my desktop, but unfortunately my entire house is packed up in storage, i'm living in a hotel, and the laptop and phone are all i've got. SO, against my better judgement, I went to the store and bought a Vista home basic upgrade DVD to fix my vista partition, and now i'm back on the net- and going to try anothe XP disk. Whew- what a pain in the ass.
snootch said:
I really want to put WM6 on my wizard, and customize it the way I want it. Do you have any favorite WM6 ROM? All day yesterday I spent trying to add a WinXP partition to my Vista laptop. Not fun. First, I shrank the only partition on the drive (where Vista is installed) using Disk management, the Diskpart.exe to create a new 2.5Gb partition to install XP on. I rebooted the labtop with a XP disk, and installed XP on the partition. After the laptop restarted the first time, it did not come back up (black screen, no CD activity), So I changed the boot options in BIOS to HDD, and the Vista partition responded with "Error loading operating system" on a black screen. So now, i've got a laptop with a corrupted Vista install, A partition with partially installed XP on it, a XP disk that just quits working, and my wizard is shot. Normally something I can deal with if I had my desktop, but unfortunately my entire house is packed up in storage, i'm living in a hotel, and the laptop and phone are all i've got. SO, against my better judgement, I went to the store and bought a Vista home basic upgrade DVD to fix my vista partition, and now i'm back on the net- and going to try anothe XP disk. Whew- what a pain in the ass.
Click to expand...
Click to collapse
It's better if you use 'PartitionMagic' software to create partition and install WinXp,as it has much advanced features as compared to built-in Disk Management.It also has the option to create a partition in the same one partition to install new OS.
I tried that first, too bad it doesnt work in Vista.
Woo Hoo!!! Success!!
Alright! I got it fixed! What I did:
1- Spent $42 on a CID unlocker from: http://www.imei-check.co.uk/m3000unlock.php
After i recieved the files from the via email (about 10 minutes) I ran their unlocker program with the file they emailed me. This CID unlocked the wizard.
2- I flashed button's ROM: http://rapidshare.com/files/18212239/CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE.exe.html
I had to flash it twice until it showed a IPL/SPL of 1.01
3- Followed this post: http://forum.xda-developers.com/showthread.php?t=276963&highlight=splash+screen+freezing
(make sure you use a blank SD card, as it will require you to format the card to make it useable again after your'e done)
4- Remove battery, and restart phone, BOOM! Button's ROM works fine!
5- Now upgrade to any ROM you like (WM6 etc.)
snootch said:
Alright! I got it fixed! What I did:
1- Spent $42 on a CID unlocker from: http://www.imei-check.co.uk/m3000unlock.php
After i recieved the files from the via email (about 10 minutes) I ran their unlocker program with the file they emailed me. This CID unlocked the wizard.
2- I flashed button's ROM: http://rapidshare.com/files/18212239/CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE.exe.html
I had to flash it twice until it showed a IPL/SPL of 1.05
3- Followed this post: http://forum.xda-developers.com/showthread.php?t=276963&highlight=splash+screen+freezing
(make sure you use a blank SD card, as it will require you to format the card to make it useable again after your'e done)
4- Remove battery, and restart phone, BOOM! Button's ROM works fine!
5- Now upgrade to any ROM you like (WM6 etc.)
Click to expand...
Click to collapse
Congrats ! that's the easy way.....
Yeah, I got tired of screwing with it, and I did it all in Vista!
I've spent whole day reading through the froum and the trinityguides.info site but can't find any proposed solution to work for my situation.
Device info:
ROM version: 3.00.707.17 (WM6)
ROM Date: 6/29/07
Radio version: 1.46.00.11
I've tried using all 3 versions of hard-spl but they all end up with the same result. With active sync linked and ready, ran the "romupdateutility.exe" at the end the PDA prompts if I want to run the "enterbootloader.exe", the moment I press yes the active sync connection would drop and eventually the program timed out with error "260" while PDA stuck in the tri color screen displaying the following:
TRIN100
SPL-1.07.ds
I've found some similar problems in the forum but those users are using vista however I am running XP sp3 in this case. I've tried all other solutions in the FAQ areas but none of them works.
My unit came with the WM6 already but I just want to upgrade the radio and get some cooked ROM to get faster performance. What am I missing here?
Any help is appreciated.
Once it drops to the tri-colour screen and is in bootloader, run the RUU again. Should be all that you need.
I've tried running it over and over but on the bottom it just kept on saying "serial" when it suppose to say USB.
Anyways, problem solved and it turned out to be the cable. For some reason the cable is good for anything, except keeping the phone connected/recognized while in bootloader mode.
I think this should be listed as one of the FAQ in the trinityguide. This might be a rare problem but it surely took me a lot time to figure out.
on Vista
Hi,
I have similar problem but I'm using Vista (Business). Is there any workaround ?
Regards,
Daneal
Hi
I have the same problem
spl 1.20 Olipro display serial instead of usb
I tryed several usb cables and still the same
when trying to update the rom it refuse to connect the ppc and end displayng the 260 error no connection
My system is vista and the first time I upgrade everything was fine, I followed all tutorials and no problem at all.
Do you think that could be this new 6.1 Mobile device center I recent install the cause?
best regards
Inabox
The problem isn't the WMC as such more the fact its Vista. Find an XP PC and do it from there.
Hi there, I had the same problem just now and cured it(in Vista). Just upgrade the htc driver in device manager again with "wceusbsh.inf" previous file, then should be ok. It seem to be Vista replaced the driver during it switched to Tri color menu.....
Hi all,
Sorry if this has already been covered.
Can anyone tell me if they have sucessfully installed a new ROM when running Windows through Virtualbox? My current OS is Ubuntu and from what i have read there are only limited sync functions with Linux.
Also can i install a ROM on a sim locked handset? My handset is in Orange UK, and i plan on keeping the Orange SIM in it. The only other handset i installed a ROM on was a vanilla TYTN so sim lock wasn't an issue.
Thanks in advance
GF
GaelForce said:
Hi all,
Sorry if this has already been covered.
Can anyone tell me if they have sucessfully installed a new ROM when running Windows through Virtualbox? My current OS is Ubuntu and from what i have read there are only limited sync functions with Linux.
Also can i install a ROM on a sim locked handset? My handset is in Orange UK, and i plan on keeping the Orange SIM in it. The only other handset i installed a ROM on was a vanilla TYTN so sim lock wasn't an issue.
Thanks in advance
GF
Click to expand...
Click to collapse
Yes , I've mate bit in different setup i have Vista 64bit so i can't use it flash my TOuch HD so i used my vmware xp to flash my phone and it work fine
so i hope is should for virtual box too
If ActiveSync works in your virtual environment, then it should go smoothly. You can also flash your TouchHd without vbox. Just copy (in massive storage device mode which ubuntu should recognize straight away) blacimg.nbh on the memory card and restart phone pressing vol down button.
i think it should work
http://code.google.com/p/htc-flasher/
GaelForce said:
Hi all,
Also can i install a ROM on a sim locked handset? My handset is in Orange UK, and i plan on keeping the Orange SIM in it. The only other handset i installed a ROM on was a vanilla TYTN so sim lock wasn't an issue.
Thanks in advance
GF
Click to expand...
Click to collapse
Yes. If you run HardSPL or USPL you can install pretty much any cooked rom currently available to your phone. This bypasses all that locking crap
vinumsv said:
Yes , I've mate bit in different setup i have Vista 64bit so i can't use it flash my TOuch HD so i used my vmware xp to flash my phone and it work fine
so i hope is should for virtual box too
Click to expand...
Click to collapse
Why can't you use Vista 64bit to flash? Mine works perfectly.
Thanks for all your help. I've installed ActiveSync (WMDC) on the the Windows 7 beta but can't get it to recognise my handset through vBox. Possibly a Win7 issue or just my set up. I'll create a Vista box and try that.
@ Sidewinder - Can you run the HardSPL from flash or does it need ActiveSync?
Thanks again
I want to bring up the old topic because I have problems attaching my Touch HD to VirtualBox guest OS.
My host OS is Windows 7 and guest OS - Windows XP SP3.
HTC storage works pretty well I I'm selecting Disk Drive after connecting my device to PC.
ActiveSync also works well in my VBox. In that case I'm selecting Devices-> USB Devices -> Generic NDIS. The phone disappears from Host OS and appears in VirtualBox. Active Sync recognizes it and everything's OK.
But if I want to flash my phone I need to press vol down and then power on. After doing that I'm connecting my phone to PC. Host OS recognizes it as Qualcomm device. Serial changes to USB on my phone.
And then I'm trying to add that new USB device called "Qualcomm .. something" to vbox. When I'm doing it - vbox guest OS screen freezes and nothing happens.
Any ideas how to solve that? Do I need to install HTC drivers (modified drivers) for my Windows 7 host OS?
bullka said:
I want to bring up the old topic because I have problems attaching my Touch HD to VirtualBox guest OS.
My host OS is Windows 7 and guest OS - Windows XP SP3.
HTC storage works pretty well I I'm selecting Disk Drive after connecting my device to PC.
ActiveSync also works well in my VBox. In that case I'm selecting Devices-> USB Devices -> Generic NDIS. The phone disappears from Host OS and appears in VirtualBox. Active Sync recognizes it and everything's OK.
But if I want to flash my phone I need to press vol down and then power on. After doing that I'm connecting my phone to PC. Host OS recognizes it as Qualcomm device. Serial changes to USB on my phone.
And then I'm trying to add that new USB device called "Qualcomm .. something" to vbox. When I'm doing it - vbox guest OS screen freezes and nothing happens.
Any ideas how to solve that? Do I need to install HTC drivers (modified drivers) for my Windows 7 host OS?
Click to expand...
Click to collapse
maybe a strange question but why dont you just flash whit windows 7
miniterror said:
maybe a strange question but why dont you just flash whit windows 7
Click to expand...
Click to collapse
My PC is now mine. It is in domain and controlled by AD and GPO and bitlocker is ON. So I can't press F8 during boot to select "disable driver signatures". So the only option - flash it from Virtual machine in my case. Unless flash it from SD card (which I don't like).
Hello,
so my T-Mobile MDA III (german) = HTC Blue Angel ist not working any more. I tried to apply the latest update form T-Mobile but it failed.
Now I am stuck in the bootloader. It says: "Serial" above and "v2. 08" below. When I insert it into the cradle "Serial" changes to "USB".
I cannot hard or softreset the phone. It stays in the bootloader. When I connect the MDA III to Windows 2000 or Windows XP it is not recognized anymore by the device manager. In windows 2000 no driver is being installed and under windows XP (with SP3) "unknown device" is being installed. No chance to manually change to any other driver. Also tried new windows installation.
Tried with Active Sync 3.7 (original from t-mobile), 4.2 and 4.5.
Flash via SD Card is not possible, if I understood the posts correct. Further mtty does not detect anything at the usb port. BaUpgradeUt.exe and MaUpgradeUt_noID.exe fail.
Any help greatly appreciated.
Fixed mine....
Exactly the same problem with mine Thought I had blown it up. Left it for 5 mins then connected my USB(still no activesync connection and no lights or nuthin) but selected the MaUpgradeUt_noID.exe again and it just worked.
Hope yours works too.
No it doesn't help.
Hi! I know that it was long time ago, but how did you manage to solve the boot-loader problem?
I didn't.
Same problem with 2.06
Restart
It really helps. Restart and try again:good:
Had the same problem right now.
Reflashed MultilangROM - didn't help.
Reflashed Radio ROM - all's fine now