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
WMDC was working fine for me until I upgraded to RC1 of Windows 7. It did tell me as I upgraded that WMDC wasn't compatible. The only thing I have installed which isn't in fact. Windows own mobile device centre is the only thing not compatible that I had!?!?!?
Anyway, I guess I'll try a reinstall, but does anyone know how I can get it WMDC working again?
(I'm using Dutty's 3.3 and W7 RC1 64bit)
Hi. Now I'm using Windows 7 Ultimate RC Evaulation copy. Build 7100 and everything is working fine. Even rom upgrades working with no poroblem.
hey guys - I'm using RC1 too but the 64-bit - never tried to use it to flash my device though (dual boot with XP)
its the last piece of the puzzle I need in order to migrate completely to W7 and wave goodbye to WinXP.
can you both confirm which versions you are using please? and if 64-bit did you have to install the vista 64-bit driver found on these forums or did it work 'straight out of the box'?
thanks
I have 32-bit version of Windows 7 RC. I just connect mine HTC TOUCH HD to PC and Windows install the drivers and Windows Mobile Device Center install automaticly. Now everything is working. cheers
As I said, I have 64 bit and WMDC wont even start for me
I have Win 7 RC1 64bits, and Duttys HD V2,4
You need to uncheck Enable faster data sync in Settings/Connections/USB to PC..
That dit the trick for me...
Hi! I have 2 notebooks, one with win7 rc1-32bits, the other with win7 rc1-64 bits. I connect my Touch HD on both, succesfully.
Htc Touch HD Aka Blackstone
Windows 7 RC (Build7100)
Everything works GREAT!!!
Flashing, synchronizing!
Must be your config
Windows 7 RC x64 here, can flash without problems, after downgrading HTC-USB drivers to active sync drivers
Windows 7 here X6. Everything works perfect
I'm using Windows 7 RC1 64BIT without any problem.
Have you upgraded from Windows 7 Beta to the RC?
Than you must uninstal WMDC before. After the upgradeprocess reinstall WMCD again.
krillesbox said:
I have Win 7 RC1 64bits, and Duttys HD V2,4
You need to uncheck Enable faster data sync in Settings/Connections/USB to PC..
That dit the trick for me...
Click to expand...
Click to collapse
This fixed it for me. Thanks
You shouldn't need to disable faster data connections. The reason that this method works is that it detects a new device and installs new drivers.
There are a few things to do, I am not sure which in particular does it, but I'vbe upgraded Windows 7 many times and some combination has always worked.
Reinstall WMDC 7.1
Manage partnerships and delete them all.
When you plug in your phone go to device manager, find your phone (if faster data connections is shown, it will be listed as a portable device and a Lan connection)
click "uninstall" on these items, and delete drivers if this option is available.
unplug phone. Wait
Plug it back in.
Let it install drivers
If this still doesn't work. Click on the devices (network connection and portable device) selelct "upgrade drivers" on each, searching the internet.
You shouldn't need to disable faster data connections. The reason that this method works is that it detects a new device and installs new drivers.
There are a few things to do, I am not sure which in particular does it, but I'vbe upgraded Windows 7 many times and some combination has always worked.
Reinstall WMDC 7.1
Manage partnerships and delete them all.
When you plug in your phone go to device manager, find your phone (if faster data connections is shown, it will be listed as a portable device and a Lan connection)
click "uninstall" on these items, and delete drivers if this option is available.
unplug phone. Wait
Plug it back in.
Let it install drivers
If this still doesn't work. Click on the devices (network connection and portable device) selelct "upgrade drivers" on each, searching the internet.
To be honest, now it works I'm not going to mess with it unless I have to. Will it be a slower transfer to the HD?
Hi all,
I had similar trouble with Windows 7 RC, however I followed the instructions posted at: http://capitalhead.com/articles/ena...synchronization-on-windows-7-x64-and-x86.aspx and that did the trick.
If I'm not mistaken, Windows 7 is supposed to download WMDC automatically, however it never did that for me. Hope it helps someone else.
Mike
w7-64bit RC1 here....
WMDC works fine (stock install) - use it both at home and at work, and i flash by renaming and copying rom image to SDcard\blacimg.nhb
Unistall
Try to uninstall WMDC and download and install another one from the internet! It work for me and i had the same problem...
W7 and Blackstone here. Flashing Syncing ... works great.
I know this thread is old but I am having this problem and none of the suggestions I have found out on the internet have solved it. I am basically having the same issue as most people in this thread have had but the REAL problem is that Windows Mobile Device Center will NOT install no matter what I try. I run the setup for it and it looks fine until it gets to 1 second left on the progress bar. Then it sits...and sits...and sits...until finally the bar rolls backward and the installation quits. No error messages, no nothing and no WMDC. I am running Win7RC x64. I will never get syncing working if I can't get WMDC actually installed in the first place. I did look in the event log and it seems there is an error related to VSS every time I attempt an install on this app. Anyone have any ideas?
This is intended for people which run KIES and device is not seen, neither the message "connecting..." appear on KIES, and MTP application does not start on Samsung galaxy.
If you moved com.android.* and com.sec.android.* into some path which is not /data/data you may have this problem. At least this is what happend to me, after I moved file back MTP start and Kies recognize the device.
never moved anything it simply does not work on Windows 7 32bit.
no magic helped ... no formating internal sd nor anything else ... i've read whole fracking day on the web how to deal with this issue and none of the solution worked.
SGS GT-i9000 ECLAIR.XFJM3 rooted
disabling launcherpro fixed it for me.
im told other launchers cause issues too
Eh, really, problems on Win 7 32bit? Haha that's so strange because it works almost flawlessly on Windows 7 64bit. Perhaps the first time there's better support for 64bit than 32bit.
Yes, you MUST run TWlauncher (standard launcher in Touchwiz) and if you got Windows 7, you might wanna download some third party drivers.
I'm on Windows 7 64bit and I downloaded the win7 x64 samsung galaxy s drivers form softpedia.
well the mtp driver doesnt install on my 64 bit computer.
It works on windows 7 32 and 64 bit just fine
No third party drivers and no magic. It's all down to individual system config otherwise it would be the same for everybody.
Incidentally, there is an update out for Kies taking it to version 1.5.1.10074_45
g0c said:
never moved anything it simply does not work on Windows 7 32bit.
no magic helped ... no formating internal sd nor anything else ... i've read whole fracking day on the web how to deal with this issue and none of the solution worked.
SGS GT-i9000 ECLAIR.XFJM3 rooted
Click to expand...
Click to collapse
have you googled for FileSearcherforKiesFix and tried that? the only thing that fixed it for me.
Strange. Kies works fine on my both computers: Win7 x64 and WinXP. Had some issues before, but new Kies works without any issues.
hello all,
i got the gt-i9000 like 2 months back the kies s/w was workin fine for the first few days now the app itself fails to lauch even if the fone is not connected.
I have uninstalled and reinstalled kies s/w like a million times.
The installation is always successful but when i click on the kies icon to start the program nuthin happens :s
Please help.
Oh yeah i am running Win7 32bit legit.
BronzedDroid said:
Eh, really, problems on Win 7 32bit? Haha that's so strange because it works almost flawlessly on Windows 7 64bit. Perhaps the first time there's better support for 64bit than 32bit.
Click to expand...
Click to collapse
Works fine for W7 32bit flawlessly to. Also for me on 2.2 it works under launcher pro as well, added bonus of not having to use home switcher (or the like) every time I connect the phone
rocketpaul said:
well the mtp driver doesnt install on my 64 bit computer.
Click to expand...
Click to collapse
It works fine on my copy of Windows 7 64bit, but I have to switch to touchwiz, and go to driver recovery in the kies menu.
I use XP at home and at work.
From home with JP6 and Kies 1.5.3.10093_82 I can connect fine using a cheap USB cable and with phone having Samsung Kies as default running LauncherPro.
At work Kies cannot connect to the phone... it just says connecting, please wait.... all the time, its wierd...
I guess I have to remove all the USB hubs on the work computer.... Will install Windows 7 Pro 64 bit at work soon so... maybe ill just wait until then...
Kies not working with LauncherPro. You have to create a shortcut to MTP Application, when you connected the phone and selected Kies need to start with this shortcut.
This is the only way to connect Kies with LauncherPro.
Somewhere I read about this, LaucherPro not recognised like TW.
Hope this helps.
The only way I have ever ever gotten kies was following these steps:
1. Completely close kies
2. Connect your phone
3. Open up device manager, find I9000 (should be under portable devices), right-click and disable (if device manager lags after you click disable then unplug the phone)
4. Replugin the phone and wait for it to say connected on the phone's screen
5. Re-enable I9000 in device manager
6. Fire up Kies and it should connect
These steps have worked every time for me
ps: I'm on Windows 7 x64
http://arvindgaba.com/computer/sams...o-install-for-samsung-galaxy-s-kies-resolved/
Not tested but seems to be approved
I'm on linux so i never used kies. Jusi odin all the way and i have nothing to complain about
This issue has become rediculous. Samsung fail so much with this usb ****. I run Win 7 32 bit and kies previously worked and even when it occassionally wouldn't I used odin.
Now unfortunately the phone just isn't recognised even after various driver and spftware reinstallations and registry deletions etc... etc... etc....
Hi friends, I follow you every day and I love you!
I have a very big problem with my Note 10.1 2014 edition, that I can't solve. When I connect it to the computer (I tried 5 computers with different windows versions) it only charge the battery, but it's not recognised by kies or Odin. In Windows 8.1 it is shown as "unrecognised usb driver", in windows 7 too and it isn't seen at all in windows xp. I tried reinstalling kies, factory reset the tab, but without success. What can I do? I'm thinking about sending it in assistance.
Thank you and excuse me for my bad English!
Rick080194 said:
Hi friends, I follow you every day and I love you!
I have a very big problem with my Note 10.1 2014 edition, that I can't solve. When I connect it to the computer (I tried 5 computers with different windows versions) it only charge the battery, but it's not recognised by kies or Odin. In Windows 8.1 it is shown as "unrecognised usb driver", in windows 7 too and it isn't seen at all in windows xp. I tried reinstalling kies, factory reset the tab, but without success. What can I do? I'm thinking about sending it in assistance.
Thank you and excuse me for my bad English!
Click to expand...
Click to collapse
When you plug in the tablet does it ask you (on the tablet screen) if you want to connect as a media device or charge only? Check your developer settings that you don't have debug mode set.
No, it doesnt ask anything...
Rick080194 said:
No, it doesnt ask anything...
Click to expand...
Click to collapse
Have you confirmed that you are NOT in USB debug mode?
Also make sure drivers are installed on computer. Sometimes it can take a few minutes to install drivers. When I first put mine on computer at work I had to manually install driver's.
mikep2323 said:
Also make sure drivers are installed on computer. Sometimes it can take a few minutes to install drivers. When I first put mine on computer at work I had to manually install driver's.
Click to expand...
Click to collapse
Yes, i reinstalled drivers through kies application, but nothing
I have the same issue. I have been searching for a fix. I want to root but PC will not recognize it or pop up with anything, tablet only charges nothing else up on tablet. I have search and searched but nothing. I am also running windows 8.1.
*****
I have now tried a 2nd PC using all USB plugs. Installed Kies nothing, uninstalled and installed only driver still nothing. Clicked version 6 times on build number to get Developer options. I enabled USB debugging.
I am starting to get upset, I just want to Root for a few functions. It shouldn't be this difficult.
Anyone have any thoughts? It could be a simple thing we are over looking.
Change cable
Also try rebooting your PC .
My laptop stops finding USB devices after about 2 weeks.
Solved
I solved selling the tablet for 430$!
For those who are still having the problem, this solution worked for me on Windows 7.
I installed the first "Download" Link from here.
http://forum.xda-developers.com/showthread.php?t=961956
Hello guys
I have a problem with my HTC 10 : I cannot connect it to the computer. I am using the original cable that came in the box but is not working. When I connect the phone to the computer, I can hear the sound that a device was connected but then nothing happens: I cannot see any usb device on the windows tray, I cannot even see it in Device Manager. There is nothing. -this is what happens on the computer . On my phone, after I connect it to the pc, it starts charging, then after 5 seconds it disconnects and connects again to the pc and I get the Slow Charging error on the screen.
This is what I tried so far:
-restart the phone
-restart the computer
-install the htc usb drivers
-install htc sync
-install android sdk dev kit
-enabled usb debugging
-enable oem unlock
-uninstalled udates from gplay and gplay services, restart and try again
-use another cable
All these steps did not changed anything. Still nothing in windows tray, and nothing in device manager.
I did not tried to reset to factory settings tho' . This might be the last resort
I am running Android 7.0, Stock ROM, Neverlocked device.
I am using Windows 8.1 x64 with latest updates.
Is this the first time you connected to the pc?
There seemed to be an issue with HTC driver & Windows 10 (what I am on), but may apply to 8.1 as well. <I got the same problems you had when I first tried messing with an HTC phone a couple years back ..... It is possible Windows or HTC had got this sorted out since.>
What I had to do (a couple years ago now) to get HTC drivers working was this:
1. Install HTC sync, then uninstall it. This leaves the HTC driver on the pc, but without HTC software. HTC sync + android dev kit (adb & fastboot) seemed to cause problems.
2. There was an issue with HTC phone being recognized over USB in Win 10. I have to edit the registry by adding this key:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\0BB40FF00100]
"SkipBOSDescriptorQuery"=hex:01,00,00,00
<Open RegEdit, navigate to folder 0BB40FF00100 using path in square brackets, then add the key in second line with the proper hex value. You might want to make a copy of the registry and set a restore point before you mess with the Registry in case things got messed up.>
This had worked for me ever since. <Did that to connect the original ONE, and the 10 connected without any change to the pc.>
Thanks for the answer man. I tried to follow your steps but it seems that I do not have the folder 0BB40FF00100 in [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\usbflag
I do not really know how to proceed next.
Sorry, I missed a step. I have to go back to my old post to figure out what I did.
My problem was Win 10 not recognizing HTC devices in fastboot without a registry change. This may or may not be related to your problem.
Since you cannot see the phone in device manager, there may be a broader USB issue. Before you go down my route, I would suggest that:
1. If possible see if you can connect with another computer.
2. Try Windows USB troubleshooter, and uninstalling Window USB driver and reinstalling.
3. Try uninstalling all HTC drivers, and reinstalling using just HTC sync. <Installing HTC sync should install the drivers as well, without having to install some standalone HTC drivers from unknown source.> See if you can see the 10 from HTC sync.
The Registry change idea comes from : https://forum.xda-developers.com/htc-wildfire-s/general/driver-finally-how-to-fastboot-to-t2857536
which does mention that this is a Win 8.1 problem, but not a problem in win 8.0
The thread points to the instructions here: https://www.android-hilfe.de/forum/...windows-ab-version-8-1-aktivieren.601686.html
This is in German, and a similar xda thread here: https://forum.xda-developers.com/htc-wildfire-s/general/driver-finally-how-to-fastboot-to-t2857536
To edit the registry, you navigate to ....\usbflag,
then you create a key 0BB40FF00100 [ Edit -> New-> Key ]
That creates the key folder, then within the folder, you create a new entry as per the 2nd line. [ Edit -> New -> Binary Value ]