Develop Bugs

USB Device Not Recognised on Bootloader

I have a problem. My Exec is stuck on the bootloader screen. All I see is Serial at the top, and v1.00 at the bottom.
When I connect my exec via USB, the screen continues to say Serial (rather than switching to USB) and the PC I connect to 'installs' the device as 'unknown device' in device manager.
I've seen mention of the problem elsewhere on the site, but the only solution I can find seems to be to keep trying, and eventually it's recognised. So far, after three days of trying, it has not been recognised.
I am aware of Buzz tool to get the device out of bootloader mode, but that required a connection to be established, which at the moment, I can't do.
Has anyone got any experience of this, or any ideas as to what's causing this, or how this can be fixed? I have tried uninstalling the 'unknown device' from device manger, restarting the PC (and hard reset of the Exec) then reconnecting, but the same thing happens every time.
Any ideas would be appreciated, as I'm currently staring at a rather expensive paper weight.

Try this it shld work
hdubli said:
This is based on my experience with two UNis..one Exec and other JASJAR..both had same problem...this is how I solved :
-Put yr device in bootloader Mode
-Disable USB in Active Sync
-Now connect woth USB cable and open mtty utility
-Select the "WESUSB... " port
-You shall see a blank white screen..press Enter to get "USB>"
-Then type ( as BUzz has informed) set 14 0
(here I wud like to inform that after doing the above I did not get success so I typed set 14 10,then set 14 9 for two three times)
-Then I ran the ROM Upgrade directly(After enbabling the USB)
-I then followed the procedure as informed on the COngratulations Screen that is hold the two "-" buttons and soft reset and then pressed 0
-I got them back to normal..
I hope this helps to all my friends...Pls feel free..pls do not trouble our Buzz..he might be busy in inventing something more to our devices
Click to expand...
Click to collapse

Guru Meditation said:
I have a problem. My Exec is stuck on the bootloader screen. All I see is Serial at the top, and v1.00 at the bottom.
When I connect my exec via USB, the screen continues to say Serial (rather than switching to USB) and the PC I connect to 'installs' the device as 'unknown device' in device manager.
I've seen mention of the problem elsewhere on the site, but the only solution I can find seems to be to keep trying, and eventually it's recognised. So far, after three days of trying, it has not been recognised.
I am aware of Buzz tool to get the device out of bootloader mode, but that required a connection to be established, which at the moment, I can't do.
Has anyone got any experience of this, or any ideas as to what's causing this, or how this can be fixed? I have tried uninstalling the 'unknown device' from device manger, restarting the PC (and hard reset of the Exec) then reconnecting, but the same thing happens every time.
Just noticed your user name, I was a big Amiga fan a few years back, still fire up Amiga forever occasionally on my PC when I feel the need.
Any ideas would be appreciated, as I'm currently staring at a rather expensive paper weight.
Click to expand...
Click to collapse
Try it with a different USB cable or in a different USB port (don't go through a hub and if you've been using a laptop then try it on a desktop PC since some laptops have hubs built into them). If that doesn't work then you're out of luck as your Universal isn't detecting that you've connected to your PC and its time to send it in for repair.

Thanks Niketkumar - unfortunately it's the step before your suggestion kicks in thats the problem - the device won't connect to the PC, so when using mtty WESUSB..... isn't an option, only COM1 and COM2.
Shuflie, I've tried with three separate USB cables on a laptop and desktop (neither through a hub, and the same device has worked fine on both laptop and desktop before).
I fear a trip to the doctors is in order ...
Very frustrating because the PC sees a device, but installs it as unknown device. Anyone know if theres a Windows CE device driver that I could try and install as an overide (i.e. in device manager on the PC go to update driver and browse to a WinCE.inf or equivalent?)
Failing this, has anyone got any clue what needs to be fixed? Or how much it might cost?

i am stuck on the same problem and wondering the forum for almost 3 days now with no luck.... please help my device is in boot loader mood but not turning the serial to USB ......... please HELP.......

solution
Guru Meditation said:
Thanks Niketkumar - unfortunately it's the step before your suggestion kicks in thats the problem - the device won't connect to the PC, so when using mtty WESUSB..... isn't an option, only COM1 and COM2.
Shuflie, I've tried with three separate USB cables on a laptop and desktop (neither through a hub, and the same device has worked fine on both laptop and desktop before).
I fear a trip to the doctors is in order ...
Very frustrating because the PC sees a device, but installs it as unknown device. Anyone know if theres a Windows CE device driver that I could try and install as an overide (i.e. in device manager on the PC go to update driver and browse to a WinCE.inf or equivalent?)
Failing this, has anyone got any clue what needs to be fixed? Or how much it might cost?
Click to expand...
Click to collapse
Please follow the steps:
1. Plug in ur usb cable in bootloader mode while it is showing 'serial' and version 'x.xx'.
2. Soft reset by pressing Backlight+power+reset pin WHILE KEEPING THE USB CABLE CONNECTED
3. your phone will now reboot into 'usb' mode. Don't remove the usb cable yet.
4. Remove the Memory card while keeping the usb cable still connected and VOILA,your pc starts recognising your phone as Microsoft usb sync.
5. Do whatever you want to do now (upgrade)
Hope it solves the problem now.
Press thanks if it does.

Something else to try
Having had a few issues with my G3 Uni, I've been through my fare share of Uni bootloader issues. When I find that I can't get the 'serial' to go to 'USB', I normally find it's because I haven't taken the memory card or the SIM card out (usually the memory card).
Make sure your memory card is out, then try to enter the bootloader and see if this cures it. If it does, then use mtty and the command 'set 14 0'
This tells it to reboot on reset. if you were to use 'set 14 1' it would go back to the bootloader on reset.

my Htc hd2 t-mobile won't recognize usb on boot-loader mode
hey guys i have a big problem!!!! my Htc hd2 t-mobile won't recognize usb on boot-loader mode. Here is the story my phone was running android 2.3.7 cyanogen 7 but i wanted to update it to ics android 4.0.4, So to do that i restarted my phone while holding down the down volume button and the boot-loader with the three colors came-on saying serial but when i connect my usb cable it won't show usb. even when i tried to run the dft.exe it shows an error saying usb connection failed. BY the way it lets me access the sd card using the usb cable on my pc, so i don't know what the problem is. PLEAS HEALP i am begging u guys pleas!!!!!!!!!!!!!!

kaleb2954 said:
hey guys i have a big problem!!!! my Htc hd2 t-mobile won't recognize usb on boot-loader mode. Here is the story my phone was running android 2.3.7 cyanogen 7 but i wanted to update it to ics android 4.0.4, So to do that i restarted my phone while holding down the down volume button and the boot-loader with the three colors came-on saying serial but when i connect my usb cable it won't show usb. even when i tried to run the dft.exe it shows an error saying usb connection failed. BY the way it lets me access the sd card using the usb cable on my pc, so i don't know what the problem is. PLEAS HEALP i am begging u guys pleas!!!!!!!!!!!!!!
Click to expand...
Click to collapse
you have the wrong forum friends! This Htc Universal section
to update Android on HTC HD2, you can use the Clock Work Mod Recovery !! for more details should refer to this thread http://forum.xda-developers.com/showthread.php?t=1021837

I-MATE JASJAR hung
Guru Meditation said:
Thanks Niketkumar - unfortunately it's the step before your suggestion kicks in thats the problem - the device won't connect to the PC, so when using mtty WESUSB..... isn't an option, only COM1 and COM2.
Shuflie, I've tried with three separate USB cables on a laptop and desktop (neither through a hub, and the same device has worked fine on both laptop and desktop before).
I fear a trip to the doctors is in order ...
Very frustrating because the PC sees a device, but installs it as unknown device. Anyone know if theres a Windows CE device driver that I could try and install as an overide (i.e. in device manager on the PC go to update driver and browse to a WinCE.inf or equivalent?)
Failing this, has anyone got any clue what needs to be fixed? Or how much it might cost?
Click to expand...
Click to collapse
Hi every one,
i have a serious problem with my HTC I-MATE JASJAR what's blocked in white screen (Serial / USB) and i cannot do anything on it, no boot, no reset soft, no reset Hard, no upgrade.
The issue is related to:
I tried to upgrade Radio ROM from 1.09.00 to 1.12 and i'm using Windows 7 Pro and when starting Flash, my PC shutdown because an electrical issue and since that, i cannot boot my device, i cannot flash or reset, my device is hung on white screen with Serial when no USB cable bluged in the PC and USB when Cable is pluged.
I Tried many times to boot it but no response, it's still hung and nothing can move on it.
I Just have one detail: when i plug the USB cable in my PC, the device is reconised but when starting upgrade or flash, i have error 101, no connexion.
Plz someone help me

bechir2013 said:
Hi every one,
i have a serious problem with my HTC I-MATE JASJAR what's blocked in white screen (Serial / USB) and i cannot do anything on it, no boot, no reset soft, no reset Hard, no upgrade.
The issue is related to:
I tried to upgrade Radio ROM from 1.09.00 to 1.12 and i'm using Windows 7 Pro and when starting Flash, my PC shutdown because an electrical issue and since that, i cannot boot my device, i cannot flash or reset, my device is hung on white screen with Serial when no USB cable bluged in the PC and USB when Cable is pluged.
I Tried many times to boot it but no response, it's still hung and nothing can move on it.
I Just have one detail: when i plug the USB cable in my PC, the device is reconised but when starting upgrade or flash, i have error 101, no connexion.
Plz someone help me
Click to expand...
Click to collapse
look here
http://forum.xda-developers.com/showpost.php?p=5456317&postcount=6
the first point...

A lot easier than to root this device

Device not connecting to computer!

Hey there.
Ok I have a problem. I have had my touch pro 2 for about 6 months now and i am really happy with it, but recently i have ran into a problem.
My phone won't connect to my computer anymore! Not just my computer... no computer at all. Not just activesync, no, it doesn't recognise it at all, not even as a disk drive.
I doubt its the cable because it does charge, and i have tried another cable (not a htc cable but its a cable with the same plug, its from my external harddrive) and it still didn't work.
I also tried a hard-reset on my phone, but still... nothing.
Ive read somewhere that you should push the usb connector a bit up, i did that, but nothing (now the usb connector seems wiggly... glad it still charges though) i have no idea what it could be and i thought i'd post here first before going back to the dealer with it. Because without usb connection i can't install costum roms and that we wouldn't want that, do we?
Well, hope one of you guys can help!

That's very strange I have had it once, but that was due to the rom I used. I flashed another rom and it worked again.
What you could try is to download a new rom and put it on your sd car using this:
http://www.julien-manici.com/windows_mobile_wifi_remote_access/
This let's you put stuff on your mobile using wifi. It's worth a try.

But you have to install roms directly from your pc to your phone, while being connected to USB right? The standards htc roms for example can only be installed that way i think... or can you also copy the .exe to your device and run that?
i'll give it a go when i get home. Thanks =]

I am having the same issue here. All of a sudden my PC or Laptop doesn't see the phone at all but it does charge with no issues. When I plug it in I don't even get the sound that the PC knows something was jut plugged into it.

go to settings - connection - usb to pc - untick the enable faster synchronization box
that should do it

As long as you have Hard SPLed your Rhodium you should be able to use the sd card method to install a rom instead of using the PC and usb connection.
You copy the rhodium.nbh file to the root directory of an sd card formatted FAT32 and then boot into bootloader - volume down and power button when off.
Follow the onscreen prompts...
Cheers...

This sounds familiar - http://forum.xda-developers.com/showthread.php?t=741406

Lennyz1988 said:
That's very strange I have had it once, but that was due to the rom I used. I flashed another rom and it worked again.
Click to expand...
Click to collapse
What's interesting with my Tilt2 (not the OP) was that I wanted to flash my ROM with the new AT&T "unofficial" ROM and that's when I found out I couldn't tether. I basically just wanted to tether my phone so I could put that new ROM onto the phone to see if I could make it more reliable and faster. Sigh.

it actually might be the cord...
The same exact thing happened to me... my phone charged with the cord but no computer recognized it...
I bought a new usb cable from radio shack and viola it worked again... so I advise u just trying a new one and if it doesn't work take it back... but try the unchecking the "check for faster sync" box first like someone said bc that do stop it from being recognized sometimes...

mr_sheen said:
go to settings - connection - usb to pc - untick the enable faster synchronization box
Click to expand...
Click to collapse
Yes, this has (almost) always fixed the issue for me. Somehow WDC becomes blind to new device inserts after you plug-unplug them several times.
Slow but stable is better.

Helpful notes from someone who has been attempting root for days

Hey everyone! Not a huge poster here however, I've been watching the threads in this forum for the past week or so awaiting root and attempting root myself. After days of attempts I have finally achieved root! I will lay down some of the specifics of what I was working with here and then give some helpful tips that will hopefully help others.
Computer OS - Windows 7 64bit (Installed HTC Sync previously and SDK)
Phone - Hboot .77 (Installed OTA accidently last week) w/ Kingston 2gb microsd
For days I had been trying every single method that I had come across and here is what had worked for me.
**Combined methods from other XDA forum members**
Power off phone with usb plugged in (usb debugging enabled previously)
Ran a batch file called root.bat that I made to run in command prompt consisting of the following (I ran this file before I turned on the phone)
:hello
adb shell
GOTO Hello
Click to expand...
Click to collapse
Hold the optical trackpad button while powering on
Press power once to enter fastboot
Wait for the fastboot to check the sdcard
Press volume down to highlight recovery
Press power to select recovery
Clicked the sdcard in and out
Eventually I entered the recovery screen on the incredible and the command window running my root.bat kept saying
- exec '/system/bin/sh' failed: No such file or directory (2) -
Click to expand...
Click to collapse
I pressed control-C then Y to end the batch file and continued on with the methods listed here
androidforums.com/all-things-root-incredible/98180-prs-complete-rooting-guide.html
Click to expand...
Click to collapse
**KEY NOTES**
I had been cracking at this for the past few days and had plugged the usb from my incredible into the BACK of the computer instead of the front and the FIRST TIME I had done this I was able to obtain root and adb recovery had worked (These are usb ports that are DIRECTLY connected to the mobo and this might have been a huge impact in my success)
Also, I kept running across my drivers detecting my phone in recovery as disk drives so I used the method here
addictivetips.com/windows-tips/how-to-disable-automatic-driver-installation-in-windows-vista/
Click to expand...
Click to collapse
To uninstall the disk drives and the USB Mass storage device and prevent them from automatically installing everytime I uninstalled. Then I went ahead and did a "Update driver manually" and pointed it to the drivers in SDK\USB

One trick I just did that seemed to work was I booted the phone and went into recover (black screen with the red logo). At that point, Device Manager showed two HTC devices listed under 'disk drives'. I uninstalled both of those devices, pulled the battery, popped it back in and went in with down arrow+power. At that point Windows loaded the 'Android 1.0' driver unsuccessfully. Uninstalled that from Device Manager, then did the down arrow + power (and held it down) to go into the black recover screen and *poof* it loaded.
I'm using Windows 7 32bit.

quagmire0 said:
One trick I just did that seemed to work was I booted the phone and went into recover (black screen with the red logo). At that point, Device Manager showed two HTC devices listed under 'disk drives'. I uninstalled both of those devices, pulled the battery, popped it back in and went in with down arrow+power. At that point Windows loaded the 'Android 1.0' driver unsuccessfully. Uninstalled that from Device Manager, then did the down arrow + power (and held it down) to go into the black recover screen and *poof* it loaded.
I'm using Windows 7 32bit.
Click to expand...
Click to collapse
WOW. N1. Proof that worrying about drivers is pointless!

rynosaur said:
WOW. N1. Proof that worrying about drivers is pointless!
Click to expand...
Click to collapse
I think that to an extent it doesn't matter.
It seemed to refuse to work with me if the drivers were being loaded at disk drives. Therefore if the drivers weren't loaded at all and there was nothing installed it could work and if the CORRECT drivers were installed then it would work. But again, for me in my experience it was refusing to work if it had the disk drives were installed as the drivers for recovery.

kentoe said:
I think that to an extent it doesn't matter.
It seemed to refuse to work with me if the drivers were being loaded at disk drives. Therefore if the drivers weren't loaded at all and there was nothing installed it could work and if the CORRECT drivers were installed then it would work. But again, for me in my experience it was refusing to work if it had the disk drives were installed as the drivers for recovery.
Click to expand...
Click to collapse
Ok, but if you look at Unrevoked's newest DIY post, they show a logcat which starts at a card check and ends at adb starting, a five second gap. This is internal stuff, not going to the host/usb -- at least not listed in the logcat. If this exploit depended on host intervention at all, I'm guessing someone would have written a linux or windows script/program to talk to the DI. Rather, all the PC can do is try to open an adb session, it's like knocking at a door -- you can't make the person home no matter how well or correctly you knock, you just hope they'll answer.
When I obtained adb shell, had all three devices show up in Device Manager: ADB Composite (I used the API 8 driver), Generic Volume G:\ and Generic Volume H:\ -- drive letter specific to my windows install, of course. All hands were on deck. The glitch happens between the software, hardware and sdcard.
In any case, I'm glad you were successful!

rynosaur said:
Ok, but if you look at Unrevoked's newest DIY post, they show a logcat which starts at a card check and ends at adb starting, a five second gap. This is internal stuff, not going to the host/usb -- at least not listed in the logcat. If this exploit depended on host intervention at all, I'm guessing someone would have written a linux or windows script/program to talk to the DI. Rather, all the PC can do is try to open an adb session, it's like knocking at a door -- you can't make the person home no matter how well or correctly you knock, you just hope they'll answer.
When I obtained adb shell, had all three devices show up in Device Manager: ADB Composite (I used the API 8 driver), Generic Volume G:\ and Generic Volume H:\ -- drive letter specific to my windows install, of course. All hands were on deck. The glitch happens between the software, hardware and sdcard.
In any case, I'm glad you were successful!
Click to expand...
Click to collapse
Ahh, okay. Well whatevs, yeah I'm glad I'm rooted now! =D It was probably the connection with the front usb ports vs the back usb ports on my computer since the back are directly on the mobo. It worked the first time I switched it to the direct USB ports.
So glad I got lamppu, wifi tether, and removed city id along with obtaining titanium backup!

I was also trying to get root for a few days and had some issues. I eventually got in on my 4th MicroSD card try- which was a junky 1GB that wasn't even labeled for speed...
I tried a16GB Class 2, 8GB class 4, 4GB class 4 and none would stay with 'device not found'- even after trying for 20+ times on each. My next step was to buy a class 6, but a random 1GB I had laying around worked. It connected after the 1st attempt with the 1GB card.
Another note- I got the '/system/bin/sh' message about 30 seconds after it went into recovery mode- not right at the start as I see it happening in the videos.
Easiest way is to yank the battery and start over if you don't get it; I used the vol down + power start up option.

Nothing worked for me. Tried all methods with lots of cards.
Stock SanDisk 2gb C4
Lexar 8gb C4
Lexar 8gb C6
DaneElec 4gb C4 (same as PNY 4/4 and Kingston 4/4)
As I was about to put my Inc for sale on Ebay. NiX threw out a suggestion on IRC. I tried it w/ the DaneElec and it worked.
It worked first try and every try since. Tried it with the stock sandisk 2/2 and no go. Haven't tried the Lexars.
Give it a shot. Good luck.
loop shell / Vol- + Power. / Hboot / wait for 4secs / insert card / highlight recovery / hit power + count to 3 or 5 and insert usb / wait till 10secs after /!\

Thanks OP - Using the oldest/slowest card I have (old 1gb Corsair card formatted Fat32), enabling the driver local policy you mentioned, pulling the battery while phone was on, and the eject method described above - I finally got in. I have no idea if it was pure luck or if it had anything to do with the above, but yours was the last thread I read so you get a thanks.
**EDIT**
After trying to get back in after realizing I needed to remove any apps before rebooting, I once again have zero luck getting in... so I'm leaning towards the complete chance/luck idea.

seanmcd72 said:
Thanks OP - Using the oldest/slowest card I have (old 1gb Corsair card formatted Fat32), enabling the driver local policy you mentioned, pulling the battery while phone was on, and the eject method described above - I finally got in. I have no idea if it was pure luck or if it had anything to do with the above, but yours was the last thread I read so you get a thanks.
Click to expand...
Click to collapse
You're welcome! I'm glad my information has helped!

[Q] WinMo wont connect via USB since new Froyo installed.

I was trying to put the hum/hiss sound fix on my sd card and I cannot get my pc to connect via USB...
My wife has a TP2 and it connects fine...
I have tried with/without the sd card in, rebooted the pc and phone, rebooted the phone while connected to the pc.... nothing...
wtf...
anyone else with this problem?
PS... NRGZ28 had posted a very basic rom for booting to android back in Feb and it is now gone from hotfile. Anyone know of a quick boot into android?

- Try a different computer
- Try a hard reset
That are the first thing you should do.

Tried hard reset...
Dif PC is not an option at the moment... I have rebooted...

Just flashed the ROM (NRGZ newest, thank goodness I had it on my SD card) and I still cant get it to sync...
I have attached the USB error I am getting... (Win7, new install)
The phone is not asking if I want to active sync or use as storage???? wtf...

FarBeyond said:
Just flashed the ROM (NRGZ newest, thank goodness I had it on my SD card) and I still cant get it to sync...
I have attached the USB error I am getting... (Win7, new install)
The phone is not asking if I want to active sync or use as storage???? wtf...
Click to expand...
Click to collapse
Reboot your PC? lol bet your tried that already...
Try this:
settings > connections > usb to pc > and disable Faster Data Sync then try. This way uses the generic usb drivers and maybe it will connect.

That did not work...
How do I get my Win7 laptop to see the phone with Android on it?

FarBeyond said:
That did not work...
How do I get my Win7 laptop to see the phone with Android on it?
Click to expand...
Click to collapse
dont think thats working yet

Ya I don't think that works yet, it's tied to Android software drivers and the use of the USB port, since there is no drivers to control the port only to charge battery. Windows thinks there is something there, but the phones USB can't communicate back....I think this is the issue or at lease after playing around with it on my phone anyway

Not that it's a huge amount of help but might troubleshoot down to the hardware level...if you go into bootloader mode on the phone and connect to USB does it connect?

I don't think you should go that deep and dirty. My touch pro 2 works only with only 1 (non-HTC) cable of the 10 i have at home, all are the "standard" mini-USB but only one works flawlessly for communicating/flashing/syncing, the other cables either do the same error - device not recognized - or windows says that the device could communicate faster - and only copies files slowly.
All in all: you should simply check with another USB cable or if you have the factory HTC cable try it with that. I noticed that the cable i am using other than the HTC one is a very good quality thick (low-resistance and double-shielded) USB cable and it never failed on me.
One other thing you should definitely watch for: plug the USB cable into the motherboard USB port directly (on the back of the PC where you plug the keyboard, mouse etc.), sometimes PC cases with front panel USB outputs simply die, or are wrongly attached to the motherboard USB header and it can cause the aforementioned problems too, not to mention if it is wrongly attached it could harm your phone too.

[q] • • • DONATING TO WHOEVER SOLVES MY PROBLEM • • •

[q] • • • DONATING TO WHOEVER SOLVES MY PROBLEM • • •
My device is stuck at Serial - v1.01 screen
• Bootloader mode (backlight+power+reset) doesn't work
• SOFT KEYS + RESET give 2 options (press 0 or X)
• My Windows 7 recognizes the device, although as an Unknown Device.
• I can enter MTTY through COM1 port but I can't type anything (ENTER key doesn't work, normal letters don't work, CTRL + V works, DELETE works - idk whats the problem).
• Can't flash - different errors occur (some ROMs give 101 connection error, some 112 error)
• I have browsed this forum for 4 days and found many tips - none of them worked
• Device starts blinking Serial/USB when entering USB cord (sometimes blinks and stays at USB)
PS: I found an interesting thread about win7 and its drivers - it was said to update my Mobile Device driver to XP one but the problem is, I don't see Mobile Device in my Device manager. I only see Unknown Device at Serial Bus Controllers.
WILLING TO DONATE TO THE ONE WHO SOLVES MY PROBLEM AND GETS MY DEVICE UP & RUNNING

Welcome to forums
I would suggest using a Windows XP machine to perform flashing and perhaps a Doc format
Good luck,

paulsrik said:
My device is stuck at Serial - v1.01 screen
• Bootloader mode (backlight+power+reset) doesn't work
• SOFT KEYS + RESET give 2 options (press 0 or X)
• My Windows 7 recognizes the device, although as an Unknown Device.
• I can enter MTTY through COM1 port but I can't type anything (ENTER key doesn't work, normal letters don't work, CTRL + V works, DELETE works - idk whats the problem).
• Can't flash - different errors occur (some ROMs give 101 connection error, some 112 error)
• I have browsed this forum for 4 days and found many tips - none of them worked
• Device starts blinking Serial/USB when entering USB cord (sometimes blinks and stays at USB)
PS: I found an interesting thread about win7 and its drivers - it was said to update my Mobile Device driver to XP one but the problem is, I don't see Mobile Device in my Device manager. I only see Unknown Device at Serial Bus Controllers.
WILLING TO DONATE TO THE ONE WHO SOLVES MY PROBLEM AND GETS MY DEVICE UP & RUNNING
Click to expand...
Click to collapse
When i am home i can help you!

d-two said:
When i am home i can help you!
Click to expand...
Click to collapse
My MSN - MOD EDIT: REMOVED EMAIL

orb3000 said:
Welcome to forums
I would suggest using a Windows XP machine to perform flashing and perhaps a Doc format
Good luck,
Click to expand...
Click to collapse
I have tried on 2 XP machines - laptop and PC both
Maybe the problem is that its COM1 port that works and mtty doesn't let me type anything.
How could I get USB port to work ?

paulsrik said:
I have tried on 2 XP machines - laptop and PC both
Maybe the problem is that its COM1 port that works and mtty doesn't let me type anything.
How could I get USB port to work ?
Click to expand...
Click to collapse
I am now Home but it is too late... Sorry, tomorrow i am back home earlier...

i wrote instruction here about flashing with windows 7. update your "unknown device" driver like it was described. do you have x86 or x64 edition? and have you removed sd and sim card?

Forgetting to remove the SD card is usually the problem. You really need to do that, it's not optional. If it's not the SD card, select the unknown device in device manager, right click, delete the device and reboot. Then try the usual instructions on flashing under Win7. Disable USB connections in WMDC. Put device in bootloader mode and connect it. When Mobile Device appears in device manager, update to the correct drivers. Try rebooting between steps if you get stuck. My drivers seem to get corrupted from time to time for whatever reason and this works for me. You need to see and select the USB option in mtty, it won't work otherwise.

l2tp said:
i wrote instruction here about flashing with windows 7. update your "unknown device" driver like it was described. do you have x86 or x64 edition? and have you removed sd and sim card?
Click to expand...
Click to collapse
I only see Unknown device, not Mobile Device or something else.
Unknown device driver can not be updated.
I have removed both cards, SIM and SD.
onurdndar said:
Forgetting to remove the SD card is usually the problem. You really need to do that, it's not optional. If it's not the SD card, select the unknown device in device manager, right click, delete the device and reboot. Then try the usual instructions on flashing under Win7. Disable USB connections in WMDC. Put device in bootloader mode and connect it. When Mobile Device appears in device manager, update to the correct drivers. Try rebooting between steps if you get stuck. My drivers seem to get corrupted from time to time for whatever reason and this works for me. You need to see and select the USB option in mtty, it won't work otherwise.
Click to expand...
Click to collapse
Removed both cards, I've seen that tip around.
As I said my device stays at Serial/v1.01 screen when pressing BACKLIGHT+POWER+RESET. Only Soft buttons + reset work, brings 2-option screen with white background (0 and X).
As I also said, I have tried same thing over and over in 3 different computers: laptop with XP, PC with XP and another PC with WIN7(current).
Installed ActiveSync from original SPV M5000 CD to both XPs, still doesn't flash and mtty still opens only COM1 port (COM4 for laptop).
I think if I could get MTTY to work, I'd be okay. But how can I get USB port working ?

If you've done everything offered here, the remaining options are faulty USB cable and faulty USB socket.
By the way, this is not the kind of thing people donate for around here. I'm personally not trying to help for any theoretical reward.

onurdndar said:
If you've done everything offered here, the remaining options are faulty USB cable and faulty USB socket.
By the way, this is not the kind of thing people donate for around here. I'm personally not trying to help for any theoretical reward.
Click to expand...
Click to collapse
I am very frustrated and willing to do whatever it takes to save my device.
Now are you saying its both, USB cable and socket that are incorrect or just one of them. Please give me an example which cable do you use.
Thanks

If at the beginning you were able to see your device from W7,than your cable and every thing is ok.
your stock with a device with no rom,so i think this is why your W7 don't see your wince phone.(it could be to a rom error or fault of manipulation done by you!!!battery for example,etc...).
solution:
1)go to a close htc support technician close to you and he will load a Rom to your phone Board.
2) PM me to sell and chip you my HTC Universal,,