So I've been using my phone to sync my music for a long time and today I updated to Verizon's new security patch and suddenly I'm getting a 'USB device not recognized' error when trying to connect my phone to my computer.
Anyone else having this problem? Any solutions?
I read the previous posts when this has happened so yes, the drivers are installed. I just hooked my phone up yesterday and it worked. Fast charging works on it and my PC charges the phone just fine so it's not the micro USB port.
Skynx72 said:
So I've been using my phone to sync my music for a long time and today I updated to Verizon's new security patch and suddenly I'm getting a 'USB device not recognized' error when trying to connect my phone to my computer.
Anyone else having this problem? Any solutions?
I read the previous posts when this has happened so yes, the drivers are installed. I just hooked my phone up yesterday and it worked. Fast charging works on it and my PC charges the phone just fine so it's not the micro USB port.
Click to expand...
Click to collapse
Did you make sure USB debugging is still on? A security update might turn that off
Yeah, that's actually the first thing I checked. Same result either way. I'm just trying to transfer media without having to take the SD card out and it just will not work no matter what I have tried, including re-installing the drivers on my computer and restarting both multiple times.
Skynx72 said:
Yeah, that's actually the first thing I checked. Same result either way. I'm just trying to transfer media without having to take the SD card out and it just will not work no matter what I have tried, including re-installing the drivers on my computer and restarting both multiple times.
Click to expand...
Click to collapse
I've had it happen a couple of times with my Note 5, I think the only way I fixed it was to use a completely different computer and ever reinstalled windows. It's like something got screwy on the computer.
BurnedDrake said:
I've had it happen a couple of times with my Note 5, I think the only way I fixed it was to use a completely different computer and ever reinstalled windows. It's like something got screwy on the computer.
Click to expand...
Click to collapse
Well, I did confirm it works on my other computer but Android Auto in my car no longer works. I'm pretty pissed off because the Verizon update definitely messed up things here. It's the only thing that changed and I had just used Android Auto the day before the updated too. I didn't even think about it until I had to use navigation today and it didn't work.
I just factory reset the phone and tried it and the computer and Android Auto still do not work. Verizon's updates are such garbage and I've been trying to wait for the Galaxy S10 to upgrade my phone.
So I found a (very stupid) fix for this. The reason it was only working on one computer of mine was because that is a desktop that I use a USB hub to connect to. What I found was if I use that USB hub to connect to my laptop AND my car for Android Auto both devices work as they did before. For now I have that USB hub out in my car so I can use Android Auto.
Obviously this is very dumb but it seems to work so if any of you have this issue with your Galaxy S7 Edge this may work for you. The USB hub I'm using is an Anker USB 3.0 4-port Hub that is no longer made and couldn't find it for purchase now but it's possible any hub or their newer ones will work.
Skynx72 said:
Well, I did confirm it works on my other computer but Android Auto in my car no longer works. I'm pretty pissed off because the Verizon update definitely messed up things here. It's the only thing that changed and I had just used Android Auto the day before the updated too. I didn't even think about it until I had to use navigation today and it didn't work.
I just factory reset the phone and tried it and the computer and Android Auto still do not work. Verizon's updates are such garbage and I've been trying to wait for the Galaxy S10 to upgrade my phone.
Click to expand...
Click to collapse
I did a little searching and came across other people having the same sort of problem, here's what they did to get it working:
(I also saw mentiond about deleting the phone from the car's list of Android Auto devices before the following steps)
1. Turn USB debugging ON on the phone. (Under developer options. If you don’t have developer options available in settings, it can be turned on by going to Settings -> System -> About Phone and taping on “Build Number” several times until a message appears saying that you are ‘now a developer’.)
2. Forget the Bluetooth pairing between my phone and my car on both the phone and the car.
3. Clear data for Android Auto app on my phone.
4. Restart Phone.
5. Turn car off-and-on.
That order was important, as I’d tried several combinations of those steps without effect until I hit on this combination. Steps 1, 2, and 3 may be able to be switched around with each other, but it seems they both had to be done before steps 4 and 5 (which seemed to need to be done in that specific order).
Also, if I start the car with the phone already connected, the car tends not to notice the phone. I have to plug the phone in after the car is started and the entertainment system ready to go.
If you want to start over without a factory reset you can do this so it will be like you just did (as far as what we are dealing with here)
---------- Post added at 05:07 PM ---------- Previous post was at 05:03 PM ----------
Skynx72 said:
Well, I did confirm it works on my other computer but Android Auto in my car no longer works. I'm pretty pissed off because the Verizon update definitely messed up things here. It's the only thing that changed and I had just used Android Auto the day before the updated too. I didn't even think about it until I had to use navigation today and it didn't work.
I just factory reset the phone and tried it and the computer and Android Auto still do not work. Verizon's updates are such garbage and I've been trying to wait for the Galaxy S10 to upgrade my phone.
Click to expand...
Click to collapse
Remove Settings
BurnedDrake said:
I did a little searching and came across other people having the same sort of problem, here's what they did to get it working:
(I also saw mentiond about deleting the phone from the car's list of Android Auto devices before the following steps)
1. Turn USB debugging ON on the phone. (Under developer options. If you don’t have developer options available in settings, it can be turned on by going to Settings -> System -> About Phone and taping on “Build Number” several times until a message appears saying that you are ‘now a developer’.)
2. Forget the Bluetooth pairing between my phone and my car on both the phone and the car.
3. Clear data for Android Auto app on my phone.
4. Restart Phone.
5. Turn car off-and-on.
That order was important, as I’d tried several combinations of those steps without effect until I hit on this combination. Steps 1, 2, and 3 may be able to be switched around with each other, but it seems they both had to be done before steps 4 and 5 (which seemed to need to be done in that specific order).
Also, if I start the car with the phone already connected, the car tends not to notice the phone. I have to plug the phone in after the car is started and the entertainment system ready to go.
If you want to start over without a factory reset you can do this so it will be like you just did (as far as what we are dealing with here)
---------- Post added at 05:07 PM ---------- Previous post was at 05:03 PM ----------
Remove Settings
Click to expand...
Click to collapse
Yeah, I tried that multiple times and have seen the article you copied here. I even did a factory reset and tried all of that again but it didn't work.
With the way I have it working right now USB Debugging is actually off too (it works with it on or off). Before the recent Verizon update I hadn't even enabled Developer Mode so USB Debugging was always off when it was working. Something screwed up with the way the phone identified itself via USB in the software update and the USB hub seems to fix it.
An official Samsung cable might work (and I have one on the way) but since I bought this phone used without the official cable that hasn't been an option.
Thanks though!!
Related
I have a tmobile MDA Vartio2 and I have numerous problems with it and need to upgrade soon but this one I cant sort.
I can't connect via usb to sync with my laptop. If I set up a new connection it will sync but as soon as I reattach to sync it wont recognise the device so I can't keep everything up to date. it isn't the cables - power is fine and they work for other things.
I am runing it as I bought it 17 months ago - no upgrades or cooked roms or changes of any kind.
Can anyone help.
I want to upgrade to something else but I always sell my old ones so I want to sort the issue first obviously even if I sell it.
mobilecat said:
I can't connect via usb to sync with my laptop. If I set up a new connection it will sync but as soon as I reattach to sync it wont recognise the device so I can't keep everything up to date. it isn't the cables - power is fine and they work for other things.
Click to expand...
Click to collapse
Try turning off the 'advanced network functionality':
Start -> Settings -> Connections tab -> USB to PC
That's what I had to do to get that hack called activestin...^WActiveSync to work reliably via USB.
Really, I've not noticed any difference between having it on and off as far as functionality goes, so really, I have no idea what the RNDIS mode stuff is even good for.
I have just tried your suggestion but now it isn't recognising the device at all. It is seeing it as far as power goes - its charging over USB but activesync isn't seeing it.
mobilecat said:
I have just tried your suggestion but now it isn't recognising the device at all. It is seeing it as far as power goes - its charging over USB but activesync isn't seeing it.
Click to expand...
Click to collapse
Check activesync itself:
File -> Connection Settings
Make sure "Allow USB connections" is checked.
If that still doesn't work, I'd try the uninstall, reboot, reinstall activesync dance and see if that helps any, provided that you are using activesync under XP.
I'd also be suspecting the sync cable. Recharging a device and getting a data connection are two different things. I have a blue angel that wouls charge via the USB sync cable, but would not sync, XP kept complaining about an unknown device. Turned out it was a broken wire in the cable.
Done all of these already I'm afraid - I have 4 or 5 cables and none of them work for this - and I know they are all absolutely fine.
OK, let's take stock of things. I'm assuming that you are using XP.
Hermes with the advanced network functionality turned off doesn't show up at all when you plug it into USB. So, we have a lower level driver issue going on.
Provided that you have not turned off all sounds in your current sound scheme, does the computer make any noises when you plug the phone in? If the data side of the connector on the phone is in order, the computer will make some kind of beep noise when you plug in a USB device.
Also, have you looked at device manager when the phone is plugged in? With advanced network functions turned on, a network adapter should appear. With out the network bits, it should show up as an HTC USB Sync device.
To eliminate something on the phone software-side (I know, you said that you have not touched anything, but try it anyway, this is windows, the environment that gave rise to the term bit-rot), put the phone into boot loader and plug it in to see if the computer sees it. It should appear as a HTC USB Sync.
If it still doesn't show up, I'd be popping over to another computer and checking to see if the phone will be recognized by that system.
For the past few weeks when I plug in I get references to acquiring network addresses (like a wifi network) but then it does nothing. Now I get nothing at all when I connect apart form power.
I have already tried re-installing active sync (just done it again in case I did something wring too)
I refuse to beleive its my cables at this point because I have 3 in front of me that all worked perfectly before everthing suddenly went wrong. Unless someone had cut all of them at the same time - this couldn't have happenned.
I am going to try and plug into the pc and see what happens (as apposed to the laptop which should have the connection.
I think this is good news (on the part of my laptop) because its the same story on the pc.
mobilecat said:
I think this is good news (on the part of my laptop) because its the same story on the pc.
Click to expand...
Click to collapse
Double edged sword there...
So we have potentially eliminated the computers (good), this leaves the phone itself (non-good).
Hard reset?
Otherwise, I'd start to suspect the USB connection on the phone itself.
I would say that my chances of rescuing this phone rather than getting a new one are getting slimmer
I think it is probably the port itself and I can't do anything about that one
Anyone want to buy one with non usb syncing functionality ?
Weird problem - when I plug my phone into my PC via the USB cable, it charges (i can see the red light and the plug in icon) but the PC via WMDC doesnt see it. Nor can I see it when I view Computer. I have since did a factory HD2 reset and also uninstalled WMDC (twice) and reinstalled. Anyone know what the prob here is or how to fix? Thanks.
Have you flashed any ROMs recently? I had this problem when I flashed a new ROM. My front USB ports were very slow, I don't even think they're 2.0 half the time as Windows tells me to plug stuff in faster ports but, to solve your problem I think you need to change how your phone acts when connected via USB to PC.
Go to Settings, Other and USB to PC and make sure its set to ActiveSync.
MrMagicMushroom said:
Have you flashed any ROMs recently? I had this problem when I flashed a new ROM. My front USB ports were very slow, I don't even think they're 2.0 half the time as Windows tells me to plug stuff in faster ports but, to solve your problem I think you need to change how your phone acts when connected via USB to PC.
Go to Settings, Other and USB to PC and make sure its set to ActiveSync.
Click to expand...
Click to collapse
That's not a solution it's a workaround and a crap one at that because all it is doing is disabling the usb rndis driver in favour of the much older and slower usb serial driver
Weird problem - when I plug my phone into my PC via the USB cable, it charges (i can see the red light and the plug in icon) but the PC via WMDC doesnt see it. Nor can I see it when I view Computer. I have since did a factory HD2 reset and also uninstalled WMDC (twice) and reinstalled. Anyone know what the prob here is or how to fix? Thanks.
Click to expand...
Click to collapse
I had this problem with my leo all last week. Then i went to my brothers place for thursday through saturday and had the same problem on his pc which runs windows xp pro sp3 (mine is windows 7 pro).
Turns out it was the phone itself. There seemed to be a problem with the tcpip stack, the rndis driver or the tcpip cache. Not sure which but a hard reset solved it and now everything is fine. Although thinking about it i only got the problem after enabling the tcpip cache tweak in bsbtweaks 1.6....... curious!
Don't plug your phone to the front usb, instead plug it to the usb ports on the back of your computer which directly goes to the m/b.
Flashing new ROMS has nothing to do with this phenomenon.
Bad USB cable or bad usb port could sometimes cause this, too.
I have not flashed the ROM at all w this phone. I did do 2 hard Leo resets but still have the problem. Running Win 7 Pro, checked the USB settings on the phone and its all good. USB plugged into the back of the PC and have tried multiple ports. Dang. Any ideas?
I had the same problem, I tried to connect it to several other PCs with no success, at the end hard reset solved it...
if a hard rest doesn;t fix it then task 29 the phone and reinstall the rom
ZoNoMo said:
I have not flashed the ROM at all w this phone. I did do 2 hard Leo resets but still have the problem. Running Win 7 Pro, checked the USB settings on the phone and its all good. USB plugged into the back of the PC and have tried multiple ports. Dang. Any ideas?
Click to expand...
Click to collapse
Trust me, the prob is not with your phone, something to do with your PC. Any firewall program running, maybe?
BumAround said:
Trust me, the prob is not with your phone, something to do with your PC. Any firewall program running, maybe?
Click to expand...
Click to collapse
Sorry mate but your wrong. The PC is fine. It is actually the phone that is at fault.
My experiences last week prove this and with no modification to my PC but only a hard rest on the phone everything is now working fine. The same with my brothers machine. No modifications made to it just my phone and that works fine now too.
Both PC's are completely different including the operating system yet both displayed the same problem last week and both now work fine with only the phone being worked on. Combine this with the other comments here that confirm this and you still think the pc is at fault? i'd like to see some proof or some form of methodology.
Although i personally had never seen this problem before over the many winmo devices i've had i'm pretty confident that my IT systems diagnostics training is serving me well here but if you can prove otherwise i'll gladly admit i'm wrong.
sorry for the newbie question but how do you hard reset? i know how to soft reset via "clear storage". i don't have access to the manual right now. out of office.
ZoNoMo said:
sorry for the newbie question but how do you hard reset? i know how to soft reset via "clear storage". i don't have access to the manual right now. out of office.
Click to expand...
Click to collapse
using clear storage is performinf the software version of a hard reset. it's not a soft reset.
the prefered way of performing a hard reset is to hold down both volume keys (make sure you do it firmly so both make contact) and then quickly tap the power button (do no hold it down at all) then hold the volume buttons until you see a warning. the rest will be obvious (printed on the phone screen)
M3PH said:
Sorry mate but your wrong. The PC is fine. It is actually the phone that is at fault.
My experiences last week prove this and with no modification to my PC but only a hard rest on the phone everything is now working fine. The same with my brothers machine. No modifications made to it just my phone and that works fine now too.
Both PC's are completely different including the operating system yet both displayed the same problem last week and both now work fine with only the phone being worked on. Combine this with the other comments here that confirm this and you still think the pc is at fault? i'd like to see some proof or some form of methodology.
Although i personally had never seen this problem before over the many winmo devices i've had i'm pretty confident that my IT systems diagnostics training is serving me well here but if you can prove otherwise i'll gladly admit i'm wrong.
Click to expand...
Click to collapse
Sorry mate, *perhaps* your IT systems diagnostics training is serving you most complicated solutions, whereas *maybe* there's more simple solutions : (1)check if there's a firewall program running that block the phone's RNDIS driver to be "seen" by the PC, or (2)a case of bad USB cable, and then (3)your *methodology-proven* trouble-shooting method.
I can say that because it happened to me, where after I take care of the firewall program, the phone gets detected immediately.
Cheers, mate.
BumAround said:
Sorry mate, *perhaps* your IT systems diagnostics training is serving you most complicated solutions, whereas *maybe* there's more simple solutions : (1)check if there's a firewall program running that block the phone's RNDIS driver to be "seen" by the PC, or (2)a case of bad USB cable, and then (3)your *methodology-proven* trouble-shooting method.
I can say that because it happened to me, where after I take care of the firewall program, the phone gets detected immediately.
Cheers, mate.
Click to expand...
Click to collapse
First, most modern firewall programs actually have application detection and notifiction systems. Now in cases where the rndis connection has been working and no modifications have been made software wise this is instantly ruled out. In your case i would look at replacing your firewall with something a little better
Next, (and we will use my personal case for this as i'm sure it will be global for this thread) i have one usb cable for my leo - one - and considering, as i said above, after i hard reset and using the very same cable as before i have proven it to work. so moving on.
my method of testing is a pretty standard method. The training is only of any use for tracking the fault diagnosis. Being able to this do allows for an accurate analysis of what is going on at each stage of the connection process.
Seeing as the op has hard reset the device we will see if it is really the PC or not. i'm positive it is the phone that is not working correctly in this case but we will soon see.
Interestingly I have two notebooks, one for work one for home both run WIN7 Pro (Work one is a SOA standard operating architecture). My work notebook did see my HD2 for a while then stopped, my home notebook still syncs without an issue using the same cable. I can only assume by proccess of elimination that it is not the HD2 and that the problem lies with something on my Work notebook.
SOLVED: It was the stupid cable. I did a factory hard reset and plugged in. No dice. Do I grabbed my spare cable and presto. Fired up immediately. Thanks everyone.
So I can't get my desktop OR laptop running XP Pro 32 to even recognize the phone. As in no audio plays and nothing appears in the system tray. Tried with/without debugging mode, installed the samsung drivers etc. The phone doesn't even show up in device manager at all- not even as something unrecognizable. Its as if the port is dead. The phone does 'ding' though and charge ok so it is receiving power... though nothing at all appears in the android notification tab when connected. Any ideas or anyone know of any apps on the pc or android side to take a closer look at whats happening on the bus?
The only way that I can get it to work is to put it in media mode. It shows up as a media device in Win7. If I put it on, "ask every time" or whatever it doesn't work and in mass storage mode it shows up as two unreadable drives, they are grayed out in Explorer... Basically...don't use the "ask every time" for USB function.
This function seems like such a simple thing, not sure why Samsung has so many issues with it considering they have been making media devices for a long time.
Anyway... do you have access to a newer OS to at least rule that out as a cause. Not saying it shouldn't work with XP 32 but just something to check out.
I was having similar issues at first. I take it adb doesn't work either? Well my fix was to delete my whole Android SDK folder, then I redownloaded it (though I just kept the "tools" folder this time). Then I downloaded "USBDeview" (google it) to delete every USB driver that had to do with android (basically just left the printers, HID, and my Sansa drivers), restarted, then I downloaded the samsung drivers from the thread on here, plugged my phone in and manually pointed the driver search to the drivers.
ADB and Mass Storage has been working fine since. All I can tell you is to keep checking cause there's something you're missing, I also thought to myself "what the heck else can I do?" since I had done each one of those steps previously, but maybe I just had to do them all together. Good luck.
another possible solution is to change cables if you're not using the samsung provided cable - some cables are charger only (no data) - some of the motorola cables are charger only and we've already had one poster that had that issue
I couldn't get it to work at first either. I more or less did this.
I plugged in my phone. I did not enable mass storage mode on my phone. Walked away and let my PC think for a while. I came back and I noticed I had two new drives. I then enabled mass storage mode and could connect.
Two of my machines I had to do this. I'm not sure why it wasn't instant, but it just took a bit of patience and walking away from the machine to let it think for a while before I guess it installed the drivers and made its peace with the fact it wasn't the G1 any more.
Say into voice dialer "Open SD card" -> check "Enable USB mass storage". That works if port on PC is OK.
If it's a driver issue, open device manager and uninstall the usb ports. Unplug everything from usb and when you reboot the computer it will automatically reinstall the usb ports.
Sent from my Vibrant
I ran into the same issue. It was a problem with the USB cable I was using. As soon as I tried a different cable it worked fine.
larryccf said:
another possible solution is to change cables if you're not using the samsung provided cable - some cables are charger only (no data) - some of the motorola cables are charger only and we've already had one poster that had that issue
Click to expand...
Click to collapse
I second this, I forgot my sammy cable at work on Friday and on way home stopped at T-Mo and picked up a charger w/cable and realized right away this was just a charging cable as soon as I connected it to my PC. I'm returning the cable back to T-Mo tonight. At least I was able to charge my phone over the weekend.
UPDATE: You guys are right, it is the goddamn cables! I bought an extra wall charger + cable at the t-mobile store and was using that at home. I had left the original in-box cable at work. Tried the cable at work today and now the drives pop up. Still don't appear writeable but I can look into that when I have time, probably the typical driver issue. As far as I can tell those separate cables are power only! $15 for a two wires + dc adapter. Thanks Samsung. Grr.
i suspect the mfgrs have gone to charge only cables to help keep folks from tethering - just a suspicion
if the "drives" are popping up, have you "mounted" the phone (pull down notification bar, clik on USB connected and it should give you a window asking to mount the cards or drive)
FYI....The Rocketfish cables you get from Best Buy do not work. They are only capable of charging.
@larryccf...I don't think certain manufacturers are implementing this on purpose so we can't tether. I think their just being cheap.
Where I got my cables on the cheap! and my problem.
I got my cable at monoprice.com. Check it out that is a 10 foot usb cable for $1.69 and it works for me. They have different lengths and even some colors. Now my Mass Storage issue . . .
My Mass Storage via USB works fine unless I enable "USB Debugging" which one of my apps needs to work. Once debugging is enabled I loss the ability to see my sd card and internal storage on my XP netbook. any ideas????
Same Problem
I have the exact issue, tried many things have'nt found a fix yet. Any help would be greatly appreciated!!!
Thanks,
crx
larryccf said:
if the "drives" are popping up, have you "mounted" the phone (pull down notification bar, clik on USB connected and it should give you a window asking to mount the cards or drive)
Click to expand...
Click to collapse
this worked for me Thanks
Yes phone is mounted, and can be seen w/o usb debugging enabled. However with usb/debugging on it does not read the phone being connected. Meaning that I cannot connect to ADB which is my main concern.
thanks for response tho,
crx
crxforya said:
Yes phone is mounted, and can be seen w/o usb debugging enabled. However with usb/debugging on it does not read the phone being connected. Meaning that I cannot connect to ADB which is my main concern.
thanks for response tho,
crx
Click to expand...
Click to collapse
This is my issue exactly, and I haven't found a fix either. Called T-Mobile and they thought turning off debugging was the only fix I needed.
Most of them, sorry to say are half retarded. They think a data reset is the cure-all
crxforya said:
Most of them, sorry to say are half retarded. They think a data reset is the cure-all
Click to expand...
Click to collapse
Ain't that the truth!
If you are running windows (x86 or x64), it would be wise to install the samsung drivers. I was having this exact problem, but as soon as I installed the drivers from samsung, viola!
I had the latest drivers from google, and they did not work for me.
Here is a link to the thread containing the links to the drivers, thanks to TGA_Gunnman:
http://forum.xda-developers.com/showthread.php?t=728929
Hopefully this belongs in this forum, I do have a focus, so I assume so.
So when I cget into connect to PC mode and plug in the usb cord, it does not truly connect with the computer, meaning the red sign thing that means don't disconnect does not appear, the screen just shows the screen with an arrow pointing the usb to the computer.
Would this be a hardware issue?
I've tried my two usb cords on different ports on my laptop.
Any advice?
I've tried more or less every other fix, but there really is no fix online for this issue, can barely find anything.
Use the USB cable that came with the phone. Other ones do not work with the Focus.
Same problem, even when I'm using original cable.
Yeah, I've tried both of my cables, and nothing works.
Kind of nice to know that I'm not alone though. Heh
Same exact problem. Samsung Focus. Original cable that came with that very phone.
I can't get the frigging updates to install because when the phone reboots in Connect to PC mode, the system doesn't recognize that it's been reconnected.
And when I try to use the WP7 support tool, which ALSO requires the phone to be in Connect to PC mode, the computer doesn't know the phone exists.
This is for C2PC mode ONLY. Recognizes fine in normal mode, but update won't complete in normal mode.
same thing intially happened to me. But when in pc download mode you have to make sure that you give your pc 5 mins while connected to your phone. The pc will eventually recognize it! I freaked out too but I did wait for it and it connected. This applies to the windows phone recovery tool, which i ran, and the updates alike. I highly suggest running the recovery tool because I tried updating without it at first and i received the timeout error. Also, make sure you empty in settings histories in the following sections, ie mobile, maps, and search.
You guys and gals are going to LOVE this.
Nothing worked, and of course, my obedient ass was using only the cable that came with my Samsung Focus.
So on a hunch, I decide to borrow my wife's cable from her HTC Surround. The damn thing has "HTC" stamped right on it.
And it worked. PC recognized connection in the Connect to PC state, which it absolutely would not do with the Samsung Focus cable.
As to siralex241's comment, good advice: when you use the Windows Phone 7 Support Tool, after it checks System Requirements, it will say nothing -- not even that it's trying anything, and no hard drive activity -- for a long time. Then it succeeds in one second. The message I saw was that installing updates had taken over 450 seconds.
Jay
Solution for update error 800705B4
Same thing happened to me. Kept getting error code 800705B4. Followed steps here and it worked fine. http://support.microsoft.com/kb/2530409.
I'm on to the March 2011 update. Been creating the backup for a LONG time now.
Well to be specific I have been getting error 8018121C1 (Something close to that) and all the KB articles say is to use the microsoft fixit tool, but that never works. It mentions that its a problem with the driver installing, and I've read online that when in connect to PC mode, Zune times out the update because it is looking for the drivers for too long. Along with that, other people have said that the device isn't being recognized as the right device. I've checked and so far I've seen that it recognizes as Windows Mobile or Zune. I don't think any of those are the right formats to have the update go through smoothly.
I have given up on updating the phone as of now. That is, until I can find a working solution.
I don't think I should contact Microsoft or AT&T about it either, simply because I think that Microsoft will just give me the KB articles, and AT&T... welll.. its AT&T.
@ jayinatlanta I have yet to try connect to PC with a different cable though.
Im aware that one or two other threads have been created with this same general question but one thing they didnt ask is what to do if you cant fix it?
As the thread topic states my Nexus 7 will not connect to my PC via USB (It is not seen at all, its not a driver issue I've tried). It will not charge when turned on but it was charging when turned off last night. When I checked this morning it said I had a full battery but after turning the tablet on it said I only had 60% battery. All the started happening after I charged it with a battery pack at work the other day because I forgot my charger at home (some people have had similar problems after using car chargers). It will let me connect a flash drive to it via USB-OTG. I have tried 3 different cables on 2 different PCs (One running Windows 7 and the other running Windows 8). I really dont know where to go for help anymore as Ive spent the past 2-3 days googling like a mad man trying to find an answer and noone seems to have one.
I would love for someone to really help me out and get some steps that could fix this, however, if its not fixable how do I RMA it? I cant lock the bootloader and I cant flash a factory image.
You say it is not a driver issue, but your symptoms indicate it is. I would start over with the removal and re-installation of the proper drivers.
Groid said:
You say it is not a driver issue, but your symptoms indicate it is. I would start over with the removal and re-installation of the proper drivers.
Click to expand...
Click to collapse
I've uninstalled them. Every time I go to manually install them the guides always say to find where the nexus is and my nexus never shows up. If it was drivers it would still charge when its on. So how can drivers cause the tablet not to charge from the ac adapter?
Try Wugfresh's program. I had issues w/o it.
Sent from my SCH-I535 using Tapatalk 2
dennyjones said:
Try Wugfresh's program. I had issues w/o it.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thats the toolkit I have installed. Its also the "guide" I am following when it comes to drivers. I tried to see if I could make the nexus connect to the pc while in fastboot and nothing happened then either. Everything he says to do involves the PC actually seeing the nexus :/
Ive changed it from mtp to ptp, toggled debugging, went to different back ups, flashed a new rom, etc etc. I really feel like Ive tried just about everything. Someone mentioned in one thread about some specific code in the nexus being wrong and possibly changing it could fix it but I do not know how I would go about doing that.
I also originally used the Wugfresh toolkit and had problems getting the drivers installed properly on Win7-64. Ultimately, I think I installed pda.net on my computer and on the N7 and was able to connect after that. Haven't had a problem connecting since. Re-read some of the Wugfresh posts about driver problems. You should be able to get it sorted out.
Groid said:
I also originally used the Wugfresh toolkit and had problems getting the drivers installed properly on Win7-64. Ultimately, I think I installed pda.net on my computer and on the N7 and was able to connect after that. Haven't had a problem connecting since. Re-read some of the Wugfresh posts about driver problems. You should be able to get it sorted out.
Click to expand...
Click to collapse
I sent you a PM but I really dont think this is an issue with drivers. I have been able to connect the N7 to my PC perfectly before the other day. Never a problem at all. Now I have uninstalled/reinstalled the drivers as best as I could (currently I have the samsung drivers because they are the only ones that will install without having to verify that the phone is connected via ADB and I had them left over from my Fiance's GNex so they have been here all along when the N7 was actually connecting).
The N7 is not connecting to the PC at all. It does not show up in device manager. You cannot make an ADB connection to it. It has already been rooted and it is running the latest version of Paranoid Android. On top of that the AC adapters will not charge the N7 while it is turned on. Its like the N7 turns away any usb connection other than a USB-OTG cable while it is on.
Also I really do appreciate the help. This has just been really frustrating for me.
Hello,
Since yesterday, I have exactly same issue with my Nexus 7 3g.
Everything is working perfectly but computer doesn't see Nexus at all (nothig works Bootloader, ADB, MTP,PTP).
Charging is fine (looks like), USB HDDs, pendrives are working as before.
Reinstaling drivers, changing to PTP, switchin on/off USB debugging didn't help.
Checked : other Nexus connects to the computer without problems, so its not drivers issue.
I assume it happened after Nexus was connected to my car charger.
Does anybody have solution/fix for that ?
Unfortunately my Nexus comes from USA, can I RMA it in Europe ?
I feel badly for everyone having these issues. I feel very lucky I'm not having them. It sounds as if the microusb port may have been altered/damaged by certain kinds of connections, like the battery pack or car charger. I don't know why this would happen and my own car charger (Moto oem for my Bionic) has worked fine on the N7. I did pick up the usb cable attached to my pc one day and created a static shock to the connector. Since then, that bank of 4 usb ports will not show either my N7 or bionic, but my usb mouse, keyboard, and printer work with them. The other bank still works, as does the pci port expansion card and my front ports. If I do have a glitch with the pc connection, I restart both the computer and the N7 and then it works. Sorry I don't have a solution.
I also assumed a damaged/fried USB post on the Nexus 7. There are 2 data lines and 2 power lines in the charging socket I think. If the power lines are damaged, usb otg may still be working. Its also tying in with the use of a power pack.
davidoff59 said:
I also assumed a damaged/fried USB post on the Nexus 7. There are 2 data lines and 2 power lines in the charging socket I think. If the power lines are damaged, usb otg may still be working. Its also tying in with the use of a power pack.
Click to expand...
Click to collapse
Have you tried switching between MTP and PTP and seeing if that works? If I used the PTP setting for the USB it shows up, I can then move files onto the PICTURE folder and once there move to another folder while using the Nexus.
-AkWingnut
Wow or strange should be more of the reply. I have done this before but it never worked. Thanks for the help. For anyone else needing help here is what I did. First opened the Nexus Tool Kit, then Full Driver Installation Guide, launched USBDeview, then - In particular look for devices with Vendor ID - "18d1" or... "04e8" - Simply right click these devices, and select the option to: - "Uninstall Selected Devices", final step unplugged the device and plugged it back in and it worked. Also MTP enabled USB Debug unchecked. Thanks again...
-AkWingnut
Tried this and haven't had any luck so far. I'm going to try pdanet or samsung drivers again later today and post results.
Sent from my Nexus 7 using xda app-developers app
Have exactly the same trouble. I'm with you guys. USB host works, no reaction in device manager. Did your nexus was unlocked? Rooted?
xxut said:
Have exactly the same trouble. I'm with you guys. USB host works, no reaction in device manager. Did your nexus was unlocked? Rooted?
Click to expand...
Click to collapse
Bump!
I'm experiencing similar issues with my Nexus 5. This is the only thead I can find that has a similar problem. My Nexus 5 worked on SlimKat, I flashed stock L Preview, now my device won't charge when it is powered into the OS. Bootloader works fine and charges when turned off. I upgraded to 5.0 which came out today (Yay!) and the problem persists.
Have any of you lads or ladies had any updates?
nintennuendo said:
Bump!
I'm experiencing similar issues with my Nexus 5. This is the only thead I can find that has a similar problem. My Nexus 5 worked on SlimKat, I flashed stock L Preview, now my device won't charge when it is powered into the OS. Bootloader works fine and charges when turned off. I upgraded to 5.0 which came out today (Yay!) and the problem persists.
Have any of you lads or ladies had any updates?
Click to expand...
Click to collapse
In my case it was a hardware trouble. Fixed by motherboard replacing in official service centre.