Related
I've recently run into a problem with my phone being recognized by my computer... basically it just doesn't work anymore. This happened after upgrading from Midnight ROM 5.3 to ACS Frozen 1.2. At this point, when I plug my phone into the computer, it only charges and does not enter into usb connected mode. On the computer I get a pop-up message saying that the USB Device is not recognized. After searching through these forums and others, I have tried uninstalling / reinstalling drivers, installing PDANet, switching USB ports, and Switching USB cables... All multiple times. The best I've gotten out of the process is immediately after certain tries, I am able to get the usb mode activated, but only once. When I try to boot the phone into download mode because I'm trying to upgrade to EF02, it is no longer recognized, and then when I do a regular boot, it is still no longer recognized.
Any help would be appreciated.
Thanks,
Greg
I've also toggled USB debugging multiple times...
Which OS is your PC running?
Sent from my SPH-D700 using XDA App
Try downloading the android sdk and updating all its files and repo's? I had to do that for my w7 x64 pc to see my epic
Posted by some phone named the Epic.
Your drivers crapped out or your cable is flaky. Try a different cable. Also turn on USB debugging and go into Device Manager in system in control panel. Go to the unknown USB device (may say Samsung Android) and hit update driver and let it search Windows update for drivers, will take a long time for all the drivers. Then reboot and should work.
Are you using the cable that came with your phone? Mine stopped working and I had to buy a new cord off amazon.
Sent from my SPH-D700 using XDA App
Win 7 x64 is the OS...
I've found a temporary workaround by pulling the battery, plugging the device into the usb, starting it into download mode, and then replacing the battery, but thats not really practical for storage purposes, only for the one time install of EF02. I have used 4 different cables and reinstalled the drivers multiple times. I am going to try reinstalling the sdk and see if that helps, as well as searching drivers using Win 7 Device Manager.
treblesum81 said:
I've recently run into a problem with my phone being recognized by my computer... basically it just doesn't work anymore. This happened after upgrading from Midnight ROM 5.3 to ACS Frozen 1.2. At this point, when I plug my phone into the computer, it only charges and does not enter into usb connected mode. On the computer I get a pop-up message saying that the USB Device is not recognized. After searching through these forums and others, I have tried uninstalling / reinstalling drivers, installing PDANet, switching USB ports, and Switching USB cables... All multiple times. The best I've gotten out of the process is immediately after certain tries, I am able to get the usb mode activated, but only once. When I try to boot the phone into download mode because I'm trying to upgrade to EF02, it is no longer recognized, and then when I do a regular boot, it is still no longer recognized.
Any help would be appreciated.
Thanks,
Greg
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1042746
Try this had the same problem this worked for me trust me it works
Sent from my SPH-D700 using XDA App
The device acts as if it is being charged.
Steps I have taken so far:
-uninstalled T-mo Samsung mobile drivers and reinstalled
-deleted (uninstalled) ALL recognized USB devices via USB deview
-tried to connect without Samsung drivers installed and all USB devices uninstalled
-tried to connect with Samsung drivers installed and all USB devices uninstalled
-tried to connect without Samsung drivers and other devices installed
-tried to connect using safe mode, both with drivers installed and not
---**these are both trying with the current one provided on Samsung's site (1.5.14.0) and with the one found here on XDA from 25apr2013 (1.5.23.0)
-tried to connect using different USB ports
-tried to connect using a different USB port on a different USB controller altogether
The kicker:
Device is recognized instantly... on my laptop.
This means:
-It is not the USB cable I am using (even though I have tried 3 different cables altogether regardless, including the one that came with the phone)
-It is not the device itself
Possible: Windows issue? Last time this happened was long ago when I had gotten a MyTouch 3G Slide. I eventually just reinstalled Windows since I had been meaning to then. I don't want to do it now though because I have too many things installed on here to start a fresh install... but I suppose if nothing else works, that's what I'll have to do.
Before that though, I would love to hear any other suggestions from anyone here.
Some time the fault cud be the cable itself... I had same issue months ago my original samsung UsB cables didn't worked... It olwyz show the msg UsB not recognized... Then I tried with a different UsB cable (i had a Nokia UsB cable) and it worked...
Try it...
Cheers!!!
Sent from battery killer Jellybean GT-I9100 :-\
rjsmer said:
Some time the fault cud be the cable itself... I had same issue months ago my original samsung UsB cables didn't worked... It olwyz show the msg UsB not recognized... Then I tried with a different UsB cable (i had a Nokia UsB cable) and it worked...
Try it...
Cheers!!!
Sent from battery killer Jellybean GT-I9100 :-\
Click to expand...
Click to collapse
As stated, I have tried to use two other USB cables aside from just the one that came in the package.
Since all cables work on the laptop, but not this computer, I have pretty much singled it out to be a windows or a driver issue. :\
What are the specs of your desktop and the specs of your laptop? You claim it is a windows issue so I assume your laptop (that recognizes the phone) is not windows? Do you have Kies on the PC? If so, try to uninstall it completely and then install the individual drivers. Also, maybe just try updating Kies. You wouldn't need to install it, just download to your PC should work. As far as that goes, does Kies recognize the phone when plugged in at all? Does ODIN recognize the phone when plugged in? Maybe some of this will help you to find out if it is a driver issue or not. Good luck.
scott14719 said:
What are the specs of your desktop and the specs of your laptop? You claim it is a windows issue so I assume your laptop (that recognizes the phone) is not windows? Do you have Kies on the PC? If so, try to uninstall it completely and then install the individual drivers. Also, maybe just try updating Kies. You wouldn't need to install it, just download to your PC should work. As far as that goes, does Kies recognize the phone when plugged in at all? Does ODIN recognize the phone when plugged in? Maybe some of this will help you to find out if it is a driver issue or not. Good luck.
Click to expand...
Click to collapse
PC is i7 920, 12GB DDR3, Intel x58
Laptop is i5 2430M, 6GB DDR3, Sandy Bridge
Both are Win7 Pro, neither have Kies (I always just downloaded the drivers themselves) but I'm downloading it now to give it a try. As of now, nothing recognizes the phone on PC.
Kies method didn't work either
I did "Troubleshoot connection error", which I guess reinstalled the driver, but it still didn't work.
Getting ready to dig out that Win7 Pro CD at this point... :\
Shuurei said:
Kies method didn't work either
I did "Troubleshoot connection error", which I guess reinstalled the driver, but it still didn't work.
Getting ready to dig out that Win7 Pro CD at this point... :\
Click to expand...
Click to collapse
Samsung Kies isn't yet compatible with the sgh-m919. Samsung rep told me soon last night
Have you unlocked developer options yet and checked usb debugging? That might be your problem....
SBERG117 said:
Have you unlocked developer options yet and checked usb debugging? That might be your problem....
Click to expand...
Click to collapse
Enabling dev options and USB debugging was the first thing I did once I turned on the phone. Tried it both with and without, still not recognized either way. Still recognized on laptop.
I've also reinstalled windows altogether, since that fixed my issue last time around, but it's no good this time still. Clean install, formatted. No good. Previous steps from first post also taken, still no good. Tried the PDAnet method as well, no good.
At this point I am wondering if it might be an x58 issue, which would really suck, but it's the only thing I can think of given all the steps I have taken.
Okay... so what's the trick on getting Windows 7 x64 to recognize this device in Download Mode?
I have enabled USB Debugging. Tried several different ports on my Maximus V Extreme motherboard. I have tried using the PDANet drivers. Nothing works.Windows will prompt me with the "Device Driver software was not successfully installed" message. Anyone know a trick?
EDIT: FIGURED IT OUT. The last Android device I owned was the Galaxy S2. Now, back then it was understood that one should avoid Kies like the plague. However, in this case, it solved my problem. It installed all necessary drivers and I was able to communicate with ODIN. Cheers.
x58 issue
luckyduck69 said:
Okay... so what's the trick on getting Windows 7 x64 to recognize this device in Download Mode?
I have enabled USB Debugging. Tried several different ports on my Maximus V Extreme motherboard. I have tried using the PDANet drivers. Nothing works.Windows will prompt me with the "Device Driver software was not successfully installed" message. Anyone know a trick?
EDIT: FIGURED IT OUT. The last Android device I owned was the Galaxy S2. Now, back then it was understood that one should avoid Kies like the plague. However, in this case, it solved my problem. It installed all necessary drivers and I was able to communicate with ODIN. Cheers.
Click to expand...
Click to collapse
I might have pinpointed the issue!
I tried Kies again, uninstalled, reinstalled, updated. No go. I did Kies by air and got a connection! So It's gotta be something with the USB.
Although I thought it was weird, I think it might be an x58 issue, I decided to pursue that anyways.
I found out that USB issues are common with x58 (per this forum: http://www.evga.com/forums/tm.aspx?m=159610 ) and will be trying a fix located here: http://www.evga.com/forums/tm.aspx?m=442244&mpage=1
I'll report back once I try this out. Hopefully it fixes it.
If not, I just ordered another USB 3.0 controller (completely unrelated, it doesn't need to be USB 3.0, just a different controller altogether, but USB 3.0 is backwards compatible anyways. I just needed one for blackmagic) which was PCI-e x1 (still dependent on x58, so it wouldn't have mattered, check diagram on fix link), which I WAS going to install in my PCI-e x1 slot, but that would have not worked! Going to install in a PCI-e x16 and hope for the best.
I'll reply back once I test that out too.
Confirmed x58 and S4/general USB connectivity issues
Shuurei said:
I might have pinpointed the issue!
I tried Kies again, uninstalled, reinstalled, updated. No go. I did Kies by air and got a connection! So It's gotta be something with the USB.
Although I thought it was weird, I think it might be an x58 issue, I decided to pursue that anyways.
I found out that USB issues are common with x58 (per this forum: http://www.evga.com/forums/tm.aspx?m=159610 ) and will be trying a fix located here: http://www.evga.com/forums/tm.aspx?m=442244&mpage=1
I'll report back once I try this out. Hopefully it fixes it.
If not, I just ordered another USB 3.0 controller (completely unrelated, it doesn't need to be USB 3.0, just a different controller altogether, but USB 3.0 is backwards compatible anyways. I just needed one for blackmagic) which was PCI-e x1 (still dependent on x58, so it wouldn't have mattered, check diagram on fix link), which I WAS going to install in my PCI-e x1 slot, but that would have not worked! Going to install in a PCI-e x16 and hope for the best.
I'll reply back once I test that out too.
Click to expand...
Click to collapse
In case anyone was wondering or stumbles upon this later, I have a few updates.
I got the USB controller today and plugged it into the PCI-e x16 slot, plugged in the S4 and it worked completely fine.
I also contacted EVGA about the issue and will get an RMA, so perhaps it's just a faulty unit. However, this seems rather common (refer to previous linked threads) in x58 chips.
I imagine it has something to do with power distribution with the controller, which is why upping the ICH voltage fixes it for some people. The USB controller is powered via 4pin, not dependent on Southbridge. I guess the S4 has higher voltage(?) requirements for it to be recognized. It seems rather strange since my other devices are still recognized, but well, that's what I managed to come up with.
Cheers.
Shuurei said:
In case anyone was wondering or stumbles upon this later, I have a few updates.
I got the USB controller today and plugged it into the PCI-e x16 slot, plugged in the S4 and it worked completely fine.
I also contacted EVGA about the issue and will get an RMA, so perhaps it's just a faulty unit. However, this seems rather common (refer to previous linked threads) in x58 chips.
I imagine it has something to do with power distribution with the controller, which is why upping the ICH voltage fixes it for some people. The USB controller is powered via 4pin, not dependent on Southbridge. I guess the S4 has higher voltage(?) requirements for it to be recognized. It seems rather strange since my other devices are still recognized, but well, that's what I managed to come up with.
Cheers.
Click to expand...
Click to collapse
Here's my craziness.
USB connection was working yesterday. Today, it is not.
I have uninstalled/reinstalled the Samsung Windows drivers/Kies
I have even adjusted my southbridge voltage to 1.2V in my BIOS
Still, no joy.
Curiously, when I boot the phone into download/ODIN mode and connect it, ODIN recognizes the connection. Reboot back into normal mode, and no USB connection is recognized. It is not showing up in my Device Manager as an unrecognized device. It just doesn't know it is there (unless phone is in download mode).
UPDATE: Solved. I had installed this ROM (http://forum.xda-developers.com/showthread.php?t=2261013). Reading back over the thread, it provided instructions for re-enabling the USB recognition of the phone. Had to re-enable the developer options and reset USB debugging. Makes sense now.
HI
I'm facing this issue today, I've tried two different laptops, both have Windows 7 x64 installed. I've tried every USB port on the two machines, I've tried with three different cables, I've downloaded and installed every USB driver there is. no use!
I'm out of options here and I can't think where to look further.
any help please?
shuurei said:
the device acts as if it is being charged.
Steps i have taken so far:
-uninstalled t-mo samsung mobile drivers and reinstalled
-deleted (uninstalled) all recognized usb devices via usb deview
-tried to connect without samsung drivers installed and all usb devices uninstalled
-tried to connect with samsung drivers installed and all usb devices uninstalled
-tried to connect without samsung drivers and other devices installed
-tried to connect using safe mode, both with drivers installed and not
---**these are both trying with the current one provided on samsung's site (1.5.14.0) and with the one found here on xda from 25apr2013 (1.5.23.0)
-tried to connect using different usb ports
-tried to connect using a different usb port on a different usb controller altogether
the kicker:
Device is recognized instantly... On my laptop.
This means:
-it is not the usb cable i am using (even though i have tried 3 different cables altogether regardless, including the one that came with the phone)
-it is not the device itself
possible: Windows issue? Last time this happened was long ago when i had gotten a mytouch 3g slide. I eventually just reinstalled windows since i had been meaning to then. I don't want to do it now though because i have too many things installed on here to start a fresh install... But i suppose if nothing else works, that's what i'll have to do.
Before that though, i would love to hear any other suggestions from anyone here.
Click to expand...
Click to collapse
很想帮你啊 可是英文水平比较拙计
ok so now I'm guessing it is not windows, I tried on another machine with Windows Vista and got the same error.
any thoughts, anyone?
Did a factory reset for the phone
no it works!
don't know why
I just picked up this phone a couple days ago and last night tried to get the USB to work with no luck. I've tried everything I can think of. It does work in PTP mode but not MTP mode. I was able to use odin to on it though, so I was able to root it.
I've tried both in linux and on windows xp. I've never had an issue with any phone on linux and have installed/removed drivers numerous times on XP.
Tried 3 different cables, Factory reset with and without USB installed, tried pretty much everything I could find while googling similar problems (removing old registry entries, installed media player, etc)
I have adb installed on my linux box and even with debugging enabled I can't even get adb to connect to the phone.
Definitely something strange going on. Maybe I'll switch to cm10.1 to see if that makes a difference
I cant get my computer (windows 7) to connect with the phone when the phone is on, and was hoping some one might have found a fix.
This might fix it...
Shuurei said:
The device acts as if it is being charged.
Steps I have taken so far:
-uninstalled T-mo Samsung mobile drivers and reinstalled
-deleted (uninstalled) ALL recognized USB devices via USB deview
-tried to connect without Samsung drivers installed and all USB devices uninstalled
-tried to connect with Samsung drivers installed and all USB devices uninstalled
-tried to connect without Samsung drivers and other devices installed
-tried to connect using safe mode, both with drivers installed and not
---**these are both trying with the current one provided on Samsung's site (1.5.14.0) and with the one found here on XDA from 25apr2013 (1.5.23.0)
-tried to connect using different USB ports
-tried to connect using a different USB port on a different USB controller altogether
The kicker:
Device is recognized instantly... on my laptop.
This means:
-It is not the USB cable I am using (even though I have tried 3 different cables altogether regardless, including the one that came with the phone)
-It is not the device itself
Possible: Windows issue? Last time this happened was long ago when I had gotten a MyTouch 3G Slide. I eventually just reinstalled Windows since I had been meaning to then. I don't want to do it now though because I have too many things installed on here to start a fresh install... but I suppose if nothing else works, that's what I'll have to do.
Before that though, I would love to hear any other suggestions from anyone here.
Click to expand...
Click to collapse
Here's a link with a list of things to try what you may not have tried to fix your problems.
A small number of devices I have worked on have a weird thing, that the first time I plug the cable into the computer, it connects but won't show up on the screen. unplugging the USB cable from the machine for maybe 3 seconds, and reinserting makes the connection work... go figure! :>)
Aloha and Good Luck!
http://forum.xda-developers.com/showthread.php?p=32906335#post32906335
Hello all!
First: I promise I searched the forums and google as hard as I could!
I'm running AOKP JB with CWM, although the problem was present on stock ICS from T-Mobile.
Symptoms: Computer and phone will refuse to acknowledge any connection (nothing shows up in Device Manager), except the phone will still charge. If I do the "remove the battery with USB plugged in" trick, the first time I do it, it will recognize an unknown device, but kies and adb won't recognize it. If I unplug it and plug it back in, it'll go back to not acknowledging any connection.
I previously programmed it (when I was still running stock ROM) via ADB via WiFi, but I need to be able to use ADB via USB. Besides, I can't seem to get ADB over WiFi anymore.
When I plug it into a different computer (Win7), it will, however, recognize my phone.
Earlier this year, before I ever tried programming via WiFi, it connected to my Win8 machine with no problem. I don't think it's a problem with the wifi setup though because the ROM was reinstalled and of course I've restarted ADB in USB mode in the months since...
What I've tried:
Reinstalling Kies
Reinstalling Samsung USB drivers
[^]Restarting the ADB server
Updating ADB
Trying different USB cables
Trying different USB ports
Toggling USB debugging
Toggling MTP mode
The UART thing from the dialer
Restarting the phone and the computer (of course)
Checking to see if my computer's USB drivers need to be updated
The android terminal command "setprop persist.sys.usb.config mass_storage,adb"
Pulling and replacing the battery while connected via USB
Crying in a corner
If anyone can help me, it'd be greatly appreciated! I'm all out of ideas and Google is no longer helpful =/
try to uninstall the drivers that are present anything samsung related to your drivers ... then connect the phone and let the process do its thing if you have the samsung drivers saved on your PC and the drivers still aint working update the drivers and then manually click where the drivers are to install them and hopefully it will work and when you tried MTP is it the only option it gives you no storage or anything ??... and is usb debugging on when you are trying all this ??
krazierokz said:
try to uninstall the drivers that are present anything samsung related to your drivers ... then connect the phone and let the process do its thing if you have the samsung drivers saved on your PC and the drivers still aint working update the drivers and then manually click where the drivers are to install them and hopefully it will work and when you tried MTP is it the only option it gives you no storage or anything ??... and is usb debugging on when you are trying all this ??
Click to expand...
Click to collapse
I tried on my work computer that didn't have any samsung drivers and when the "unknown device" dialog popped up it didn't do anything or install anything, nor did it show up in Device Manager. Unplugging and replugging it back in did not reproduce the dialog box. Togged USB Debugging and still no dialog box saying it recognized it.
The thing with the samsung drivers is that they're self installing so even if it popped up in Device Manager, I wouldn't be able to manually update the drivers =/
I tried MTP both with and without USB Debugging, although it also gives the option for PTP.
At this point do you think I should unroot and go back to stock? It's not been recognized on three computers now! =[
Are you using the stock cable? My computer wouldn't recognize mine without it.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
foltz61 said:
Are you using the stock cable? My computer wouldn't recognize mine without it.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
Both the stock cable and a generic cable.
Similar problem
Similar problem as the OP. And hi guys, it's nice to be on these forums.
My device, when I plug it in using the stock cable, doesn't even charge. It doesn't show up in device manager, nor does it give me a notification, or say it's unsupported and bear that yellow icon. I have tried using different USB ports, I have tried the toggling USB debugging, I have tried restarting phone, computer, and taking out battery. I have tried that PDA/MODEM dialer trick. I am using 4.1.2 Jellybean, not rooted. (that WAS my goal,, until I hit this roadblock) I have not connected it to the computer in the past, it's relatively new. I'm thinking the cable is bust.
Any suggestions would be appreciated. It charges fine through a wall outlet plug, be it generic or stock.
so guys ive come to a conclusion i think its something in the samsung usb cables try getting yourself a blackberry usb cable , TRUST ME !!! ever since i got my phoness etc... tablet and yadi yadi samsung usb cables have always seemed to give me problems i think its because they are multi data/charging cables and when using the blackberry usb cable i have never ever once encountered a problem with any of my phones sd/storage problems do yourself a favor and pick up one of those cables and you will be golden !! if not then i guess im the only lucky one :LOL here you go http://www.amazon.com/Blackberry-Travel-Adapter-Micro-Cable/dp/B004VMVSYK/ref=pd_sim_cps_2 5 bucks!
Edit also one more test boot into recovery and click in the advanced menu and see if mount usb works for you in recovery mode ??
FIX (try using a generic cable)
I actually solved it on my own! After borrowing a generic cable from a friend it booted up! The Samsung cable was just not doing its thing.
yeah im telling you those cables they provide are JUNK!!! i only use my samsung to charge because they do that well but data they are str8 CRAP!! glad you got it up and going
OP
Hope OP will have the same luck as me...pray to the Android gods...
Lol:thumbup:
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
So my phone was mounting fine on my pc, and then all of a sudden it wasn't. My Nexus 7 still mounts properly and accepts developer commands, but the m8 won't (yes developer settings is on).
I tried wiping and flashing a rom clean and it still doesn't work, charges fine though. Any advice?
Subscribed
I'm having the same issue. Stock non rooted and it will not connect. I have tried it on other computers cables ports everything.
Art2Fly said:
So my phone was mounting fine on my pc, and then all of a sudden it wasn't. My Nexus 7 still mounts properly and accepts developer commands, but the m8 won't (yes developer settings is on).
I tried wiping and flashing a rom clean and it still doesn't work, charges fine though. Any advice?
Click to expand...
Click to collapse
You might try a different cord.
Open Device Manager in Windows and then plug the phone in. Do you see it in the list with a little yellow triangle? Do you see Android USB Devices listed?
OP after literally messing with various driver files, 8 usb ports and 2 laptops, I dug out my old box of cables and found a taped up, on its last limb OEM HTC EVO 4g (not lte the original) cable. This thing has been through the ringer. But its exactly what It needed. I figured with the 3 cable I had already tried this wasn't the issue, but have you tried using an OEM cable? I guess that is all that works. Good Luck
beamer1341 said:
OP after literally messing with various driver files, 8 usb ports and 2 laptops, I dug out my old box of cables and found a taped up, on its last limb OEM HTC EVO 4g (not lte the original) cable. This thing has been through the ringer. But its exactly what It needed. I figured with the 3 cable I had already tried this wasn't the issue, but have you tried using an OEM cable? I guess that is all that works. Good Luck
Click to expand...
Click to collapse
Still trying to get it to work, have tried 4 cables myself. I might just end up having to return the phone.... Fastboot works in bootloader
Art2Fly said:
Still trying to get it to work, have tried 4 cables myself. I might just end up having to return the phone.... Fastboot works in bootloader
Click to expand...
Click to collapse
Uninstall all HTC drivers and HTC Sync. Then connect the phone. DO NOT choose the option to automatically install any drivers.
Open Device Manager, find the phone. Select the option to manually pick the driver, and select the generic MTP device driver.
This is what worked for me, after countless attempts at re-installing various HTC drivers, different cables and ports, etc.
Bump. Still looking for answer to this. I have RUU'ed both to Sense and Google Phone editions and the problem still persists, the phone does not detect its connected to a computer and change to mtp accordingly. Only way I was able to get the RUU in there was through fastboot, which is again the only time I can access the phone through usb. Adb is no luck in either android or recovery.
Art2Fly said:
Bump. Still looking for answer to this. I have RUU'ed both to Sense and Google Phone editions and the problem still persists, the phone does not detect its connected to a computer and change to mtp accordingly. Only way I was able to get the RUU in there was through fastboot, which is again the only time I can access the phone through usb. Adb is no luck in either android or recovery.
Click to expand...
Click to collapse
Have you tried revoking the USB debugging authorization and then accepting the RSA fingerprint key again when connecting to PC?
Obviously it can't be an USB cable problem if you can connect to it in bootloader mode and use fastboot commands.
To clarify, the phone just charges when connected, it does not detect that it is connected to PC so debugging doesn't even trigger, neither does mtp. I don't even get the slow charging notification
Does it do the same when you plug it in and reboot the computer to "pick up" during boot up process? Or if you run a live CD? I never had an issue like that with my phone but I did have a similar problem with the USB external blu ray drive I bought some time ago. The pc just didn't detect it at all not on any of the ports until I rebooted my PC with the drive already plugged it and for some reason it picked it up. <Not a solution as I don't know what caused it to not be detected in the first place but still...
Not sure if it's an issue with the device(Phone for you, blu ray drive for me) or if it's a problem with the PC even though other things might still work for you as it definitely did for me(phone, headset, mouse, keyboard, usb extender + all the external hard-drives connected to it)...
Problem exists in all computers, Mac, pc, linux
Did you try what I suggest in Post #6 above?
This worked for me when I had the same issue. adb and fastboot would work, but it would not mount MTP.
And just in the last day or 2 I helped someone else with the same issue and fix.
The phone doesn't show up in device manager.
Have you modify the Kernel? (Applying some settings for example)
I browsed over the web for this issue and found some people with the same problems. They solved by removing the settings applied on the kernel or flashing a new one.
I've flashed various kernels and ruu, still same result
Still looking for help
Friends,
I've searched through all the threads here and on zentalk but still no good.
I have a ze551 with Superzen, phone works fine however I cannot get it to detect in Windows.
Nothing shows up in device manager, I've tried USB Debugging, MTP and PTP. I've tried 3 different computers (2 x W10 and 1 x W7) and still no good.
The only detection I manage to get is a split second of MOOREFIELD showing up when powering the phone on.
I want to flash MM but cannot adb sideload due to this USB detection issue, any ideas?
What drivers did you install? When I first connected the phone to a pc I installed the Asus drivers but nothing worked. Everything began to work after installing the Intel drivers
h0mbre_au said:
Friends,
I've searched through all the threads here and on zentalk but still no good.
I have a ze551 with Superzen, phone works fine however I cannot get it to detect in Windows.
Nothing shows up in device manager, I've tried USB Debugging, MTP and PTP. I've tried 3 different computers (2 x W10 and 1 x W7) and still no good.
The only detection I manage to get is a split second of MOOREFIELD showing up when powering the phone on.
I want to flash MM but cannot adb sideload due to this USB detection issue, any ideas?
Click to expand...
Click to collapse
try to revoke all usb debugging authorizations from developer options. then disable usb debugging and disable developer option and enable again. now enable usb debugging again. now connect to computer. now run command "adb devices" and authorize from phone.if u still have issue try changing usb cable.
I've tried the Intel drivers., the problem is the phone doesn't even get detected by windows, there's nothing showing up in device manager.
I do however get charging from USB.
I've tried USB 2.0 and 3.0 ports in 3 different computers, no detection.
It used to work fine, now it has just stopped working. Maybe the USB chip is fried or something.
h0mbre_au said:
I've tried the Intel drivers., the problem is the phone doesn't even get detected by windows, there's nothing showing up in device manager.
I do however get charging from USB.
I've tried USB 2.0 and 3.0 ports in 3 different computers, no detection.
It used to work fine, now it has just stopped working. Maybe the USB chip is fried or something.
Click to expand...
Click to collapse
may or may not. may be usb cable broke down data wire, may be connector issue. have you tried above said tips?
Hey,
I got the same problem, and the quick charging takes 7 hours or so, but I should mention previously that in my case the USB port was damaged, so I changed the whole dock. After change tried all other cables including the Asus official cable, still no joy. It looks like some updates made a big fuss in the phone or ... the motherboard is burnt? I tried on different computers with and without Android Intel USB drivers installed, but the problem is the computer cannot see the phone - I'm getting the message that the phone is not sending its designator. I have not rooted my zennfone, but when I try adb to see if the phone is mounted it's not. I was planing to root it now, but it looks like I cannot do anything. I'm affraid that there is something wrong with the hardware. I did started also SMMI test and it loops testing bluetooth, so definitely there is something wrong, but yet I have not figured out.
sukhwant717 said:
try to revoke all usb debugging authorizations from developer options. then disable usb debugging and disable developer option and enable again. now enable usb debugging again. now connect to computer. now run command "adb devices" and authorize from phone.if u still have issue try changing usb cable.
Click to expand...
Click to collapse
Hey mate, thanks for the tip.
I tried this and it did not work.
Still only getting MOOREFIELD if I hold volume down+power but no other detection what so ever
h0mbre_au said:
Hey mate, thanks for the tip.
I tried this and it did not work.
Still only getting MOOREFIELD if I hold volume down+power but no other detection what so ever
Click to expand...
Click to collapse
did you installed intel isoc driver??? if so uninstall it and install intel android usb driver
sukhwant717 said:
try to revoke all usb debugging authorizations from developer options. then disable usb debugging and disable developer option and enable again. now enable usb debugging again. now connect to computer. now run command "adb devices" and authorize from phone.if u still have issue try changing usb cable.
Click to expand...
Click to collapse
sukhwant717 said:
did you installed intel isoc driver??? if so uninstall it and install intel android usb driver
Click to expand...
Click to collapse
I have tried all drivers, the phone was working fine on my windows install and suddenly stopped.
I believe this is not a driver issue, it is hardware issue with the port or with the rom (superzen).
I will try to flash other rom as I have custom recovery and see if it fixes otherwise the port is busted.