Related
I tried to upgrade my rom but the process crashed. The utility mtty doesn't work because when I connect the universal, boatloader mode by the cable, to the pc, it says "USB not recognized" (sometimes when I connect the computer is frozen till I disconnect the cable of the universal)
Please, I tried to have some solutions in the forum but all the posts indicates is needed previously the usb connection.
Do you know if should be possible to run the flash of the rom in other way, for example using a serial cable connected into the miniusb of the universal, because the boatloader screen says "Serie, v.1.01"
I apprecite what you can say please, I'm really in a hole.
Try this...
Try taking out the battery for a few minutes (10-30mins) and reboot your PC then repeat upgrade process. Hope that helps. Good luck!!!
I have the same problem on my PC at work, it's caused by a poor USB chipset in the PC, or trying to connect through a USB hub.
The only thing I found that worked was to try a different PC, then it was fine...
sl9 said:
I have the same problem on my PC at work, it's caused by a poor USB chipset in the PC, or trying to connect through a USB hub.
The only thing I found that worked was to try a different PC, then it was fine...
Click to expand...
Click to collapse
In my case it still happening in other computers. Conclussion: some piece of the software in the universal has been lost. The screen shows "Serial" that means on some way that is opened to comunication but not USB.
My questions are:
- should be possible to put some starting software in SD and do the universal boot on it.
- do you know how to connect to the computer COM! port from the usb miniport of the Universal.
I appreciate, I was not planning to replace now the Universal...
beginner said:
sl9 said:
I have the same problem on my PC at work, it's caused by a poor USB chipset in the PC, or trying to connect through a USB hub.
Now works.... I still thinking windows is so stupid software made for distroy our mind ....
Solved after install drivers for a converter usb -rs232 ( I was looking for the way to connect from rs232 the universal)
I'm happy again and I promise don't try to change rom again (at least for a while)
If some person is interested in what brand of software/hardware I installed, send me a mail...
Thanks hearing me ...
Click to expand...
Click to collapse
Click to expand...
Click to collapse
i have the same problem with my friend's uni
does it mean that you don't have to own any adapter, just have to install drivers for USB to RS232 adapter
if yes, where to find it?
thanx
respectfully
ZeD
zedino said:
i have the same problem with my friend's uni
does it mean that you don't have to own any adapter, just have to install drivers for USB to RS232 adapter
if yes, where to find it?
thanx
respectfully
ZeD
Click to expand...
Click to collapse
I want to say that is running after doing some things and obviously some of it solved my problems. I made:
- unistall last version of activesync and go back to version 4.0
- delete all the applications using ports usb.
due the connection still not running (windows message: device not recognized) and because in the screen of universal I saw: "COMM1" I tried to connect from computer port rs232. By that I purchased some special cable, name: hama brand, rs232 serial, 9 pin - usb.
As you can imagine all the steps I followed were followed by the typical restart of windows. In this sense is important to say that the universal, after connect, need to do a soft reset each time (again windows....)
Other comment is that I unmark the option to connect by usb in activesync and mark the connection by com1.
and after all was done, connecting by usb the unniversal, kill wcescomm, windows said "NEw usb device, sync device". I started mtty and now appears the USB option, great! same time the screen in universal changed from comm1 to usb, more great....
and that's all.
does it mean you solve your problem using special USB 2 RS232 connector?
ZeD
PS: it was my first idea , but i still believe i can solve the problem using USB port
zedino said:
does it mean you solve your problem using special USB 2 RS232 connector?
ZeD
PS: it was my first idea , but i still believe i can solve the problem using USB port
Click to expand...
Click to collapse
I think my english wording was not fine. I mean I solved my problem after install the sofware -drivers- of the rs232 connector, but connecting to the universal by usb as on standard way I was syncronizing previous the crack with activesync.
OK, where to get this driver?
thanx
?????????? NOTHING ?????????????
zedino said:
OK, where to get this driver?
thanx
Click to expand...
Click to collapse
Try here.
http://www.hama.de/portal/type*3/action*1026/searchMode*1/q*039703
I have had the same problem several times now (search the forum for the thread).
I tried three different PC's/laptops and three different USB cables all with the same error as yourself.
Eventually I got a connection but the laborious process of trying - failing, restarting windows and soft resetting the phone, trying - failing........... until it finally worked. I did nothing differently the time that it worked but the strange thing is that it has worked every time since! Maybe the USB driver the phone has a bug in it that causes it to get 'stuck' in a mode where it will no longer correctly operate but once you have managed to 'kick' it into action it seems toi then carry on working.
It was also a ROM upgrade that caused my USB phone driver to stop functioning. Maybe the fact that the phone has a slightly diffferent software configuration after the upgrade but exactly the same hardware fingerprint causes the driver to fail.
Every time that I have had this problem it is after an upgrade but once I have gotten it to work once with the new ROM, it always continues to function - until the next upgrade.
shrubbery said:
I have had the same problem several times now (search the forum for the thread).
I tried three different PC's/laptops and three different USB cables all with the same error as yourself.
Eventually I got a connection but the laborious process of trying - failing, restarting windows and soft resetting the phone, trying - failing........... until it finally worked. I did nothing differently the time that it worked but the strange thing is that it has worked every time since! Maybe the USB driver the phone has a bug in it that causes it to get 'stuck' in a mode where it will no longer correctly operate but once you have managed to 'kick' it into action it seems toi then carry on working.
It was also a ROM upgrade that caused my USB phone driver to stop functioning. Maybe the fact that the phone has a slightly diffferent software configuration after the upgrade but exactly the same hardware fingerprint causes the driver to fail.
Every time that I have had this problem it is after an upgrade but once I have gotten it to work once with the new ROM, it always continues to function - until the next upgrade.
Click to expand...
Click to collapse
not works, probably is this device lost forever, i have restarted device and PC almost hundred times, still the same result, uni stuck in Bootloader screen top of page "Serial" bottom of page "v1.00"
nothing changed, even if i connect to USB port
if someone have some solution to this s*it pls let me know
thanx
i have had the same. my device wast recognized by my pc, bur i used maupgradeno_id and installed a other rom, even installed the original rom from qtek (latest) then after i was finished it started then i tried the other rom and it was working. ( pc did see a unknown device ) hope you have the same and its working also.
good luck
mrijnvis said:
i have had the same. my device wast recognized by my pc, bur i used maupgradeno_id and installed a other rom, even installed the original rom from qtek (latest) then after i was finished it started then i tried the other rom and it was working. ( pc did see a unknown device ) hope you have the same and its working also.
good luck
Click to expand...
Click to collapse
no, my problem persist, hundred times i tried to recover friends device using upgrade by original shipped ROM but the device is not recognized by system so there is allways connection error, so this kind of reliving this UNI is not usable
anyway, thanx for raply and suggestion
ZeD
mrijnvis said:
i have had the same. my device wast recognized by my pc, bur i used maupgradeno_id and installed a other rom, even installed the original rom from qtek (latest) then after i was finished it started then i tried the other rom and it was working. ( pc did see a unknown device ) hope you have the same and its working also.
good luck
Click to expand...
Click to collapse
If you're stuck in bootloader mode only, visit www.buzzdev.netand look for ExitBootloader utility written by the great Buzz. Just follow his instructions or scroll thru' Universal's forum here and there for problems relating to "stuck in bootloader"
hope this helps
no device is not recognized by PC so any trying to use exitbl is not available, anyway this option was one of the first what i have tried
thanx anyway
ZeD
i had the same problem with the QTEK of my principal after I upgraded his ROMs.
(after the hard reset, the pocket remained in bootloader mode).
you can solve this problem in a very simple way:
you have to launch the bootloader installation (BL1.01_RUU_UNI_V.1.2.EXE) from the PC (still connected with the PPC through USB) while the PPC is in bootloader mode (on your display you see "USB > Serial 1.01" or something like that).
then you do a SOFT reset and the pocket boot normally.
very simple.
i hope to be helpful to someone.
zedino said:
no device is not recognized by PC so any trying to use exitbl is not available, anyway this option was one of the first what i have tried
thanx anyway
ZeD
Click to expand...
Click to collapse
I had some problem. After uninstall all usb applications in the pc and install the software for cable usb -rs 232, doing some softreset in the pda connected, it turned the screen message "Com" by "Usb"
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
As the title states: Why does some computer fail to recognize the Universal via USB on bootloader mode?
I recently reformatted my computer, which I usually do once a year. After installing all my apps back and running windows update on my computer, I installed active sync. Performed a normal reset on my computer, attached my Universal and active sync worked.
Here comes the problem: I decided to roll back to my old AKU 2 QTEK ROM. Of course, I know how to use the Ma_Upgrade No ID file. The problem is my computer now fails to recognize my Universal no matter what I do on bootloader mode. To make it worst, I am now stuck at the bootloader mode with my computer not recognizing it. Any suggestions as to why my computer failed to recognize my Universal?
OK, I was able to get the ROM upgrade going again, by removing my SIM Card and 4GB SD Card. I'll post back if I was able to revive my Universal.
So it seems that my computer failed to recognize my Universal because either the SIM Card or SD Card is causing the conflict.
I had the same problem.... I have two computers one with Win Vista (with the same problem) and another with XP sp1. This computer recognize my pda in boot loader, doesn't matter if still SD card and SIM inside....
Sorry for my english and I didn't tell you a solution...
Hi,
i had the same (very annoying) problems but i always was able to get the Universal back into Windows Mobile.
It was very strange because i started the ROM update and than e.g. it did not go in the Bootloader but back in Windows Mobile so i started it again and than it stucked in the Bl. Hardreset and putting the device again into Bl did not help and i was already very annoyed. I tried to plug in and out the USB-cable but it was always telling me SERIAL and not USB and Windows showed this ****ing popup that one device is not recognized or something like that. I tried a trick to let the cable plugged in USB and than reset and it showed me USB but wheter MA_Upgrade (No ID of course) nor mtty were able to find the device. After several trys and resetting and resetting again i was able to bring it into USB but MA_Upgrade did not work.
The only way to bring back the device from the Bl is the method described in XDA-Wiki (http://wiki.xda-developers.com/index.php?pagename=Instructions for those stuck on Boot Screen)
The problem is that this method does work only half. I did the steps until the command "set 14 0" and started MA_Upgrade BUT it always told me that the device is not connected, it never worked. I was already frustrated so i did again the reset and what happend? It started back into Windows Mobile!
So what i think that after using the command set 14 0 AND running MA_Upgrade reactivated the start of Windows Mobile. I tried the steps very often because i tried to find a solution for the contacts between WM5 and AKU 3.2 or higher but the only way is to ActiveSync them. This really works and this is for sure the guaranteed way to get (at least my) the Universal back to Windows.
Btw for the people who are to lazy to use the search function:
The damn ROM upgrade does NOT work on Vista until now! Even not with the Windows Mobile Device Connection Center (or how it's called). I tried several steps on the RTM Vista but it never worked. Don't waste your time on it!
So far from my side, i hope these experience will help some people
I Got It To Work!!!
I was so worried. Wheeeeew! Anyway back to normal again. I got it to work.
My observation is: My computer failed to recognize my Universal because I was using Active Sync Version 4.5 Beta 2 to update my Universal. The solution is to completely uninstall active sync using the windows remove program under control panel, and manually deleting the active sync folder from the hard drive. I then installed Active Sync Version 4.1 and all was well again.
So my next question to all the guys/gals who had problems with upgrading their device because the computer FAILED to recognize their Universal via USB is: ARE YOU USING THE BETA VERSION OF ACTIVE SYNC?
Actually when you try to upgrade with SD card inserted - only then you will get this error - I spend so many hours of GOD prays for my Universal - and after that I just remove a SD card and everything is back to normal
agisofttm said:
Actually when you try to upgrade with SD card inserted - only then you will get this error - I spend so many hours of GOD prays for my Universal - and after that I just remove a SD card and everything is back to normal
Click to expand...
Click to collapse
What is the size of the SD Card you are using? Because when a 2 GB SD Card is inserted, it works just fine. But I experience the error with my 4 GB SD Card.
Unfortunately, i don't share the same luck with all of you.
I've already take out both SD and SIM and try thousand times with ActiVeSync 4.1, 4.2 and 4.5 beta, softreset, hardreset, mtty'ing, but what i got? BIG ZERO.
So my pc always recognise my ppc as "Unknown Device" and there is no, even some slim chance, to get it to work.
Any idea for reviving my uni from black slumber of bootloader screen?
Any help would be appreciated.
DuLanTus said:
Unfortunately, i don't share the same luck with all of you.
I've already take out both SD and SIM and try thousand times with ActiVeSync 4.1, 4.2 and 4.5 beta, softreset, hardreset, mtty'ing, but what i got? BIG ZERO.
So my pc always recognise my ppc as "Unknown Device" and there is no, even some slim chance, to get it to work.
Any idea for reviving my uni from black slumber of bootloader screen?
Any help would be appreciated.
Click to expand...
Click to collapse
use MTTY with "task 28 55aa", "set 14 0", "set 14 9, "set 14 10" and "set 14 20" as described. bootloader screen may be replaced with a blank one, boot it on bootloader mode by "Backlight+Power+Reset"
http://wiki.xda-developers.com/index.php?pagename=Universal_Resets
now upgrade as usual, then If you stuck on the bootloader again after upgrading, try to upgrade the bootloader itself
go to
http://forum.xda-developers.com/showpost.php?p=1255206&postcount=52
i have done all this... but there is something with vista... they do not recognised it when it is on bootlad screen... what should i do can anyone help me??
moixalakix said:
i have done all this... but there is something with vista... they do not recognised it when it is on bootlad screen... what should i do can anyone help me??
Click to expand...
Click to collapse
Hi, yes you could be bang on in saying there is a problem with vista, my machine did that as well, I really thought I'd turned the phone into a brick, luckily I've got an xp machine that let me connect with the tools that everybody else is talking about here, the one I used was UNI_ExitBootloader.exe (from this site somewhere) which sends all the codes for you and it only worked from the xp machine, it totally failed on the vista machine.
Tried all suggestions, but no luck
So a failed upgrade has left my Uni stuck in bootloader mode saying "Serial" and "v1.00". When I plug the thing into my Windoze XP machine with Active Sync 4.5 one of three things happens seemingly at random:
1. My mouse stops working
2. It tells me that the USB device is malfunctioning and cannot be recognized
3. Nothing happens
In all cases the Uni still shows the same "Serial" message.
The Uni has no SD or SIM cards in it. I have tried hard resetting it. I've removed and reinstalled Active Sync. I've rebooted this windoze pile of crap about a thousand times.
Anyone got any ideas?
Thanks,
Saline
Welcome to forums
Have a read here:
http://wiki.xda-developers.com/index.php?pagename=Uni_Stuck_Bootloader_Serial
Hope it helps,
Hi. Thanks for the quick reply. Unfortunately I have already tried the suggestions on that page (that's how I found this thread). As I mentioned above, the device has no similar nor SD in it.
Have you tried to reflash from SD card?
instructions on the link on my sig
I wanted to root my phone and flash a costum rom... unfortunately my DHD (2.2.1) is T-Mobile branded, so i had to create a goldcard in order to downgrade from 1.75.111.2 to 1.32. When it came to temproot it manually with cmd i had to plug my DHD into my PC in load only mode, usb debugging activated.
I knew already that my DHD wont recognize my PC or the other way round (i somehow broke it when i deleted the htcsync drivers.exe from my sd card), but i thought maybe it would somehow work in usb debugging mode.
Well, it didnt(phone not found).
i then focused on repairing my usb connection, so i tried it on 2 other pcs (mine is w7, the other ones are xp and win7) but it all failed
(xp asked for drivers, which i installed directly from htc.com today(on all pcs(plus i removed and reinstalled them all properly))/win7 did nothing/mine said that it fails to connect and that i should use a usb 2.0 port(well all ports are usb 2.0, i also tried usb3.0))
evertime i plugged my DHD in i was asked which connection i want to use, none worked, i also restarted my phone several times (usb connected and without) when i type in #7284# (or *#7284# i tried both) it says: connection failure or invalid mmi code
Finally i resetted my phone and did it all again! But it wont work!
please help me!
Hi...It looks like a driver issue...
If your drivers are installed correctly, in your win-7 Device manager it will show DHD.
I would suggest to Re-install HTC Sync from HTC website - Run it again and give it a try
doesnt work either.... win7 says the device does not run properly, my phone does nothin unusual...
i wonder if htc could fix the issue... this would be my last option
however i believe in you guys at xda!
how did you reset your phone?
Did you install the android SDK? Does adb recognize your phone? (run "adb devices", if your device is listed, everything should be fine)
On my win7-machine, the HTC-Software gives me an error message (along the lines of "phone doesn't respond" or something like that) but adb works nonetheless.
thank you for your answer but im afraid it didnt work... i installed the usb driver pack on sdk but i couldnt find it under sdk/usb driver..., however i found some files -> android/android-sdk/extras/google/usbdriver/amd64 -> usbdrivercoinstall2.dll... i tried to install this driver in hardware manager, and i tried to install an adb.exe which i found in my downgrade folder as a driver. but win7 said no driver installation is necessary the "best" drivers are already installed (win7 aint gonna install anything)
also my dhd is found under unkown device, -this device is deactivated because it made errors- "Dieses Gerät wurde angehalten, weil es Fehler gemeldet hat. (Code 43)"
well i deinstalled it and searched for new hardware, he now says the drivers are installed properly please restart however i neither see my sd card nor my devices name (instead unkown device with this little yellow triangle)
btw. for reset i used my android reset (settings -> sdcard -> reset)
It is normal, the HTC Sync turns on the USB debug?
Have the same issue. My DHD can be connected to the PC no other way than charge mode, no matter is usb debugging turned on or off. Tried 2 PCs with W7 and 1 PC with Ubuntu 10.04. This trouble appeared several days ago. Wipe didn't help. Thinking of re-installing firmware, but it seems like hardware problem. An engineer in our service center said it might be motherboard malfunction.
Some ways of solving this problem are described here: http://goo.gl/2eMcP But none of those solutions helped me. If anyone can help, please advise.
UPD: re-installing the firmware had no success - connection with PC failed. 95% hardware problem, will take it to service center.
Guys I know it's a stupid advice, but I had same problems (suddenly my connection with pc didn't work anymore): did you try to change usb cable?
giegi_dc said:
did you try to change usb cable?
Click to expand...
Click to collapse
tried 3 cables and 3 PCs
i just found a solution for me : i tried a forth pc (win7) freshly installed htcsync + android sdk + !downloaded! (not properly installed) adb drivers (which i surprisingly did not need) well i plugged my DHD in and he installed all drivers, but never asked for an adb driver. instead he had problems installing 7 different bluetooth drivers for my DHD (???)^^
it just worked for me this way (also worked for debugging mode + load only mode (for radio s-off/hboot s-off))
:|)
well it's not exactly a permanent solution just a temporal way to root my phone, but in worst case i think its nessesary to reinstall win7 on your pc....
Good day,
I'm having problem with my DHD unable to be recognized in my Win 7 PC. I have already install HTC Sync and also tick on "Ask Me" for Connect To PC setting. I'm running on stock 3.13.707.4 ROM with S-ON and unrooted. Even restart to Fastboot my PC still unable to recognized my DHD.
From Googling it shows many Desire having USB-Brick problem, does this problem also applied to DHD? Is it my phone is hit by USB-Brick? Any guide to solve this problem? I've tried flashing older ROM via Bootloader and PD98IMG.zip but it won't allow saying something like the ROM is older version.
I just bought this used phone for about a week so I'm still not sure on how to solved this problem. any helps is much appreciated.
are you using the original cord that came with the phone? just any old usb cable won't work
also you can't flash a new rom without rooting and gaining S-OFF, you're unrooted and S-ON, that's why you get the "version is older" message
maatsby said:
are you using the original cord that came with the phone? just any old usb cable won't work
also you can't flash a new rom without rooting and gaining S-OFF, you're unrooted and S-ON, that's why you get the "version is older" message
Click to expand...
Click to collapse
I bought the phone and it came with 1 cord (with HTC label) that can be connected to the charger, I guess there are only 1 cord for charging and connect to PC? This is the cord that I use. In addition to that I have also tried Motorola, Sony Ericsson (both also for Android phone) and Nokia cord but all can't.
The ROM is actually older version stock ROM from RUU.exe. I saw from few Desire thread they were using this method to restore the ROM to before the USB Brick condition so I thought to try it.
BUMP!
Anyone know what should I do to resolve this problem?
Are you running the very latest HTC Sync on your PC? I'm using 3.0.5606. You can get it here: http://www.htc.com/www/help/
Also, connect your phone and go into Device Manager on your PC. Check to see if you have an entry for Android USB Devices and that the phone shows up. See attached screenshot for how mine looks. This is the best place to check to see if your PC has installed the drivers correctly.
In answer to your question about the cable, yes it's the same cable that attaches to the PC or to the mains charger. I've sometimes had connection problems caused by a dodgy cable, but I've used others apart from the HTC one without issues.
Edit: Also, when you install HTC Sync it should warn you to disable Antivirus software during the installation. This can be really important! I ignored it the first time around, thinking it was just a silly precaution, and had loads of problems with the phone not being recognised. Had to uninstall, temporarily disable AV, and re-install HTC Sync. Once it has finished installing, you can turn your AV back on.
Thank you for your reply preacher6.
Yes, I'm using the latest HTC Sync, v3.0.5606, just downloaded yesterday and reinstall everything.
When my phone connected to the PC it didn't appear as Android USB Device on my Device Manager, it only appear as Unknown Device in USB Controller:
So I guess I can rule out the cable as I have tried about 4 cables already.
For the installation part, I have disable the anti virus and also running the setup program as administrator. When installing there is no problem whatsoever that crop out.
Another point is, even on Fastboot it appear as Unknown Device in the PC.
I would try to update the driver manually - right click on the Unknown device, go to "install driver" or "update driver", then browse to the "Program Files\HTC\HTC Driver" folder. See if it picks up and installs the correct driver.
I've tried manually update the driver as per your advise but it says there is no compatible driver in that folder even though androidusb.inf is in that folder.
I'm running Win 7 64bit. does the driver also work for 64bit OS?
Should do, yes, I'm on Win7 64 bit myself. There is this folder on my PC:
C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Win7_x64
Is the unknown device present when the phone isn't connected? Just to make sure that is actually the phone - if it's still there when the phone isn't connected, it's some other device.
Otherwise try uninstalling the unknown device and then rebooting the PC, then forcing the installation of the drivers again.
The folder is same as yours.
The unknown device does not present when my DHD is not connected, so I'm certain it is the phone that appear as unknown device.
I have tried uninstalling the unknown device > reboot PC > installing the driver but it still won't install.
Another thing is, I check on the Device Manager > Unknown Device properties > Details" for it's Hardware Ids and it shows as USB\UNKNOWN. I think it should show a strings of the device id? Correct me if I'm wrong.
Yep, there should be a proper device ID string, on charge mode mine shows a hardware ID of USB\VID_0BB4&PID_0CA2&REV_0226&MI_01.
At this point the best thing I can suggest is to try on another PC. If it works, your drivers are screwed up and you'll need to strip them and reinstall. But if it doesn't work on another PC, it's possible you have a hardware problem with the phone.
xb360 said:
Good day,
I'm having problem with my DHD unable to be recognized in my Win 7 PC. I have already install HTC Sync and also tick on "Ask Me" for Connect To PC setting. I'm running on stock 3.13.707.4 ROM with S-ON and unrooted. Even restart to Fastboot my PC still unable to recognized my DHD.
From Googling it shows many Desire having USB-Brick problem, does this problem also applied to DHD? Is it my phone is hit by USB-Brick? Any guide to solve this problem? I've tried flashing older ROM via Bootloader and PD98IMG.zip but it won't allow saying something like the ROM is older version.
I just bought this used phone for about a week so I'm still not sure on how to solved this problem. any helps is much appreciated.
Click to expand...
Click to collapse
Hi. This thread is pretty old but I'm wondering if you ever resolved the issue? I'm having exactly the same problem with my HTC One s and I can't seem to find a solution anywhere.
THanks
dmastman83 said:
Hi. This thread is pretty old but I'm wondering if you ever resolved the issue? I'm having exactly the same problem with my HTC One s and I can't seem to find a solution anywhere.
THanks
Click to expand...
Click to collapse
Yes. Holla if you still need help
marknoll said:
Yes. Holla if you still need help
Click to expand...
Click to collapse
I need help too (HTC Desire Z device)
Is it hardware problem? (I already purchased new system board).
For me it looks like hardware problem, because device does not accept bus address, do not show USB strings/VID/PID (Tried different cables/PCs/OSes (I have OpenSUSE linux, but phone does not connect to usb on any PC, Windows PCs even do not understand that something plugged in)).
No problems with USB-connector (checked resistance), but I do not see pull-down resistance with my tester.
But all other functions work well.
UPD. Tried to connect from FASBOOT/HBOOT/Android - the same result, device does not accept bus adress. Additionally it charges without problems, but when I connect phone to USB no pop-up/information at top bar appears.
FossaFX said:
I need help too (HTC Desire Z device)
Is it hardware problem? (I already purchased new system board).
For me it looks like hardware problem, because device does not accept bus address, do not show USB strings/VID/PID (Tried different cables/PCs/OSes (I have OpenSUSE linux, but phone does not connect to usb on any PC, Windows PCs even do not understand that something plugged in)).
No problems with USB-connector (checked resistance), but I do not see pull-down resistance with my tester.
But all other functions work well.
UPD. Tried to connect from FASBOOT/HBOOT/Android - the same result, device does not accept bus adress. Additionally it charges without problems, but when I connect phone to USB no pop-up/information at top bar appears.
Click to expand...
Click to collapse
I am trying to understand what exactly are you asking me . are you asking me if the PC can recognize your device ?
marknoll said:
I am trying to understand what exactly are you asking me . are you asking me if the PC can recognize your device ?
Click to expand...
Click to collapse
Sorry, it looks like I explained my question wrong (I'm Russian, and English do not native to me). Let me try reformulate:
You said "Yes. Holla if you still need help" so I believe that you were able to fix "Device not recognized" problem. So I'm asking - how did you do it? Did problem was hardware or software?
For me (look at symptoms at my previous message) it looks like dead USB controller in phone. But maybe it very strange software problem (USB-controller firmware damaged)?
Did I explain it clear now?
Install the SDK on PC and update all android versions.
Well guys it was just my PC, i made a system backup for four days and that was all the problem(the USB port of my PC)
FossaFX said:
Sorry, it looks like I explained my question wrong (I'm Russian, and English do not native to me). Let me try reformulate:
You said "Yes. Holla if you still need help" so I believe that you were able to fix "Device not recognized" problem. So I'm asking - how did you do it? Did problem was hardware or software?
For me (look at symptoms at my previous message) it looks like dead USB controller in phone. But maybe it very strange software problem (USB-controller firmware damaged)?
Did I explain it clear now?
Click to expand...
Click to collapse
After installing and updating SDK...go into platform folder and open it. Hold mouse in field and hold shift and right click mouse. Chose "open cmd here"..that will open a cmd prompt window. In regular mode on phone,type "adb devices" should return numbers (ex: hta3829g)..if in bootloader mode,type "fastboot devices" should return numbers.
This SDK helps PC see your phone when its plugged in. Especially handy when a PC won't install drivers for your phone
Sent from my ATRIX HD
Are you also stating that your device will no longer charge when plugged in?
Sent from my ATRIX HD