Have done several upgrades with vista in the past. Had to format the hard drive and re-install vista. Old drivers that I dowloaded (wceusbsh.inf) will not work. Get a message problem with driver. Have tried re-downloading the driver and same problem. Any help would be greatly appreciated.
Now have gotten the drivers to load o.k. but still no luck in a connect to the device
After spending a couple of hours screwing with everything I could think to try, I have got the Hermes to update again.
# 1 After following Mr Vanx's directions for the Vista upgrade prosses
http://www.mrvanx.org/cms/index.php?option=com_content&task=view&id=23&Itemid=27
# 2 DO NOT place the unit into bootloder mode, start the Windows Mobile device center (WMDC), plug the usb connection into the unit and wait for the WMDC to show connected, NOW you can run any of the RUU update files.
As Always Mr. Vanx is the man!
Bootloader Mode - Will it Erase Data
I have been having similar problems since I got a new computer that runs VISTA. I have tried everything, and the Device Manager, Portable devices has never given an indication my Mogul 6800 is present. I read the guide that captainrick747 referrs. I am concerned that going into Bootloader mode my system will lose all data and get reset to the original configuration. Should I be worried?
Related
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
Ok so I'm kind of new to the flashing process (especially when it comes to HTC phones) and I decided to try and put PDAVIET's rom on my phone... Big mistake.
Something went wrong during the install and now my Wing is bricked. I can get to the bootloader, so all is not lost - I hope.
I've gotten a hold of the RUU for the Wing, but I'm having some trouble getting it to flash the device. The problem is that when I connect my phone in bootloader mode, Windows XP doesn't recognize it... (it recognizes that the device is connected, but does not have drivers) After that, I try and run the RUU installer, but to no avail. (260 Connection Error)
I'm kind of stuck on this one, so if somebody could help me with this, (I must be doing something wrong ) It would be greatly appreciated.
Thanks in advance, Jon
I've found Windows Vista Active-Sync Drivers for Bootloader Mode here.
Driver Signature reads 'Chicago', so give it a try:
http://forum.xda-developers.com/attachment.php?attachmentid=33662&d=1169888879
Just don't pair your device (remove pairings) and choose 'guest' as partnership.
The Update should work fine (if battery is > 50% ^^)
That did the trick, thanks! Just out of curiosity, what does is the relevance of Chicago?
Jaquers said:
That did the trick, thanks! Just out of curiosity, what does is the relevance of Chicago?
Click to expand...
Click to collapse
Chicago was the Codename for Windows 95, It was used to differentiate between Windows 95 and Windows 3.1 drivers.
I need some help!
After days of tearing my hair out and swearing a lot, I have managed to get my i780 to connect to the PC (the data cable was at fault and kept causing 'unrecognised USB device' errors).
I have followed the official Samsung update, i.e. installed the modem drivers and then run the update. The update has worked fine on the PDA part of the phone, but has failed on the phone part and the phone just alternates between flight mode and invalid SIM.
I have tried to re-flash the phone with the same result, it failed on the phone part again. I have uninstalled and re-installed the modem drivers and WMDC (I'm using Vista) but the update will still not complete the phone part.
Is there any way to flash the phone part again so that it works?
Please help! I love the new threaded texts and the new opera browser and most of all the fact that wifi now works properly! For some reason the phone worked for an hour or so and now has stopped working.
Thanks,
A
Try to upgarde on from another PC. And dont forget to install Modem drivers before flashing.
I advice to upgarde onder XP or Win7.
Or try this if you already dont.
xp upgade http://uk.samsungmobile.com/pmgmvst.do?visitgbn=10970112&coflag=0
vista upgrade http://uk.samsungmobile.com/pmgmvst.do?visitgbn=10970111&coflag=0
modem xp http://uk.samsungmobile.com/pmgmvst.do?visitgbn=10970110&coflag=0
modem vista http://uk.samsungmobile.com/pmgmvst.do?visitgbn=10970109&coflag=0
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....
Hi,
I'm having some issues where the MTP driver fails to load. Tried all the obvious stuff and did a lot of reading of forums and stuff but can't find a fix. Could anyone help me to fix it please?
Here's what hardware I have and what I've tried so far:
Tab Pro 8.4 16gb wifi UK model, rooted.
Connected via cable to Dell XPS 17, latest USB drivers installed, win 7 x64.
First of all, I enabled USB debugging and windows installed drivers for all except MTP.
Tried installing the Samsung driver package, same problem. Uninstalled at present.
Installed kies, didn't work, wouldn't even connect to the device. Uninstalled.
Followed the instructions on the wiki but the suite software installs the driver succesfully but then windows won't accept the driver. Tried the workarounds in the wiki but still no luck.
Tried rebooting the tablet and leaving the cable connected.
Tried wiping the cache.
Tried restarting both the tablet and laptop after reinstalling software and drivers, still no luck.
Found several workarounds on my travels, one was a command line for windows to add to usergroup ( it's on the laptop downstairs, will add it to the post tomorrow).
One post said to change a registry entry...really? Tried that, and another registry trick, but still no.
Using the same laptop, I had similar problems trying to flash a custom rom onto an s4, but the CM installer worked first time. I've done a fresh install of win 7 since then.
Can anyone shed any light on this for me please? Is there any kind of workaround? Running out of ideas!
Thanks
Fixed this, well, kind of. Here's a quick rundown of what I did, for people like me who are struggling with connection problems.
I thought I had tried everything, was going to dump the whole thing and then remembered that I'd fixed some previous USB problems (sound card) by doing a clean boot.
First, remove Kies.
The only other thing that is required are the samsung mobile drivers from their website. I tried with and without and this would only work with them installed.
Restart your tablet, make sure MTP is selected.
You can find out how to do a clean boot for you version of windows here.
Leave your device connected via USB cable. Once you have clean booted into windows, windows will attempt to install the drivers from windows update, let it do this. It can take a minute or two to complete. You should then see a green tick in the notification area rather than the dreaded red cross.
If, for some reason, the driver doesn't install first time, you can unplug and then plug back in the USB cable and this should do the trick.
What I did find, is that the connection wasn't consistent, I could restart either my laptop or tablet and then it wouldn't connect, so I'd have to go through the above process again to get it to connect.
Doing this allowed me to flash the Clockworkmod recovery with odin 3.09, but for whatever reason, I was still unable to use the recommended Eimdall suite to flash cyanogenmod.
In the end, I downloaded the CM11 zip file to my tablet (via http) and then used ES file manager to move it to the SDCard root and then clockworkmod picked it up from there.
Also, once CM was installed, there were no connection problems at all, as far as I can see.
Hopefully this will help others in the same predicament.