I've googled and searched everywhere for this, but no luck. I got the S4 yesterday (AT&T) and i went through the steps to turn on developer options for the new 4.2.2 jellybean to get access to the USB debugging option. I turn USB debugging on and hook it up to my computer and it will not install the ADB interface driver (needed for PDAnet). The phone connects as if USB debugging is not turned on saying "connected as a media device" and keeps giving me the option on the computer to access storage. Anyone or everyone else having this problem?
urn357 said:
I've googled and searched everywhere for this, but no luck. I got the S4 yesterday (AT&T) and i went through the steps to turn on developer options for the new 4.2.2 jellybean to get access to the USB debugging option. I turn USB debugging on and hook it up to my computer and it will not install the ADB interface driver (needed for PDAnet). The phone connects as if USB debugging is not turned on saying "connected as a media device" and keeps giving me the option on the computer to access storage. Anyone or everyone else having this problem?
Click to expand...
Click to collapse
Did you install the drivers? Did you have the phone connected when you enabled it? If so disconnect and reconnect.
urn357 said:
I've googled and searched everywhere for this, but no luck. I got the S4 yesterday (AT&T) and i went through the steps to turn on developer options for the new 4.2.2 jellybean to get access to the USB debugging option. I turn USB debugging on and hook it up to my computer and it will not install the ADB interface driver (needed for PDAnet). The phone connects as if USB debugging is not turned on saying "connected as a media device" and keeps giving me the option on the computer to access storage. Anyone or everyone else having this problem?
Click to expand...
Click to collapse
I did the same thing and it worked for me tho..
Also, you may want to check your phone's screen after you connect it to the computer. I had to "accept" my computer's RSA key before adb could detect the device.
crawrj said:
Did you install the drivers? Did you have the phone connected when you enabled it? If so disconnect and reconnect.
Click to expand...
Click to collapse
I've done everything and tried everything I know to. I have restarted the computer, the phone, enabled and disabled usb debugging while it's connected to the pc and no conncected. I've installed the drivers PDAnet says to, but still my phone connects as if usb debugging is not on (says connected as media and pc doesn't recognize and install the adb driver). Is there anything I'm missing?
Dare{D}evil said:
I did the same thing and it worked for me tho..
Click to expand...
Click to collapse
Did you do anything different besides just turn on usb debugging?
urn357 said:
I've done everything and tried everything I know to. I have restarted the computer, the phone, enabled and disabled usb debugging while it's connected to the pc and no conncected. I've installed the drivers PDAnet says to, but still my phone connects as if usb debugging is not on (says connected as media and pc doesn't recognize and install the adb driver). Is there anything I'm missing?
Did you do anything different besides just turn on usb debugging?
Click to expand...
Click to collapse
All I did was install install the S4 drivers from Samsung. Enabled USB Debugging. Plugged it into the computer. Waited for the drivers to finish setting up. Disconnected and reconnected again just to make sure drivers were loaded. And launched ADB. Nothing else.
Edit: Oh almost forgot. I got a message on the phone saying something about a computer trying to connect do you allow it. I hit always allow or something. Sorry don't remember exactly was too long ago. That is probably it because if you weren't watching the screen you wouldn't see it.
Edit2: LOL just saw captawsm's post. Yes what he said.
captawsm said:
Also, you may want to check your phone's screen after you connect it to the computer. I had to "accept" my computer's RSA key before adb could detect the device.
Click to expand...
Click to collapse
crawrj said:
All I did was install install the S4 drivers from Samsung. Enabled USB Debugging. Plugged it into the computer. Waited for the drivers to finish setting up. Disconnected and reconnected again just to make sure drivers were loaded. And launched ADB. Nothing else.
Edit: Oh almost forgot. I got a message on the phone saying something about a computer trying to connect do you allow it. I hit always allow or something. Sorry don't remember exactly was too long ago. That is probably it because if you weren't watching the screen you wouldn't see it.
Edit2: LOL just saw captawsm's post. Yes what he said.
Click to expand...
Click to collapse
You guys on AT&T? I never got that message. I know nothing ever popped up like that. Did you get the actual driver from Samsung website for your phone? I just tried installed the one pdanet offered.
urn357 said:
You guys on AT&T? I never got that message. I know nothing ever popped up like that. Did you get the actual driver from Samsung website for your phone? I just tried installed the one pdanet offered.
Click to expand...
Click to collapse
I did not install any other drivers tho..it was all default but it did ask me to confirm the computer's RSA key
Hallelujah! I finally got it working! It must of been a driver install quirk on my pc. For anyone else with this prob who used a previous phone with pdanet on the same pc like I did ( I used a samsung infuse prior). I went and uninstalled the samsung drivers that were already on my pc and then went to the samsung site and installed the newest ones they had. Hooked the phone back up and after about 6 or 7 seconds (have no idea why it took so long) the drivers on the pc started installing again and cha ching usb debugging was working correctly. The RSA thing popped up after that.
Thanks guys for assuring me it was only my problem and not a mass-wide problem to make me troubleshoot further.
I've been having the same problem but can't seem to find the drivers on the Samsung website. Could you please post the link?
Drivers
http://www.sammobile.com/kies/
http://www.samsung.com/us/support/owners/product/SGH-I337ZKAATT
If your computer recognized (and installs drivers) when your S4 is connected via usb (not in developer mode) but does NOT recognize your S4 when connected with USB debugging this is what you might need to do. It took me 2.5 hours to find this.
Remember to have your phone set to MTP + ADB mode.
to do this:
in phone mode type *#0808#
Choose : AP on upper part and
for USB Setting, choose : MTP.
http://forums.androidcentral.com/samsung-galaxy-s4/282817-pc-cant-detect-galaxy-s4.html
Related
Hey guys, just got my Tab a few days ago, its unlocked and its working great. I want to root, but my PC wont recognize it (running win7) and it says the USB device has malfunctioned... wth? I searched through some threads about the drivers, and ive tried 4 different ones, restarted my PC, AND my Tab, with no luck. No, USB Debugging is not enabled. (not a noob, just, simply not working)
Any ideas? I would appreciate it
I just got my tab 3hours ago. I got it to work.
Here are what i've done
1.go to control panel and see if samsung usb driver is there. If it is, uninstall it.
2.disable usb debugging on the tab
3.connect the tab to the computer.
Thats wht worked for me. Hope it helps. And yes, samsung has really got to work on the usb thing.
Unzip and run the attached file. Delete any old unused USB device and delete any Android, Samsung or other related device then reinstall Samsung drivers.
NovaFox238 said:
Hey guys, just got my Tab a few days ago, its unlocked and its working great. I want to root, but my PC wont recognize it (running win7) and it says the USB device has malfunctioned... wth? I searched through some threads about the drivers, and ive tried 4 different ones, restarted my PC, AND my Tab, with no luck. No, USB Debugging is not enabled. (not a noob, just, simply not working)
Any ideas? I would appreciate it
Click to expand...
Click to collapse
This helped me: my computer tower has front and back USB ports. Back USB ports are directly embedded in the motherboard, front USB ports are a wire run from the case plugged into the motherboard, but the front USB ports are on a different chip.
When I first tried using the ADB debugger with Android, ADB would not even find my device if I plugged the device into the front USB ports. If I move the cord to the back USB ports, everything works properly. Maybe this is your issue?
Thanks guys, I believe I got it working.
Hi guys,
After upgrading to ICS I've been unable to connect my pad to the PC. This is usually not a problem, but last night I needed adb to re-root it. Nothing worked, nothing connected. Tried installing drivers and the Asus sync, but no luck.
Is this a known problem? Anyone got a solution? I doubt it's the hardware as I connected a few days before upgrading...
Found a solution. Went into Settings->Storage and turned MTP off and back on.
tiwas said:
Found a solution. Went into Settings->Storage and turned MTP off and back on.
Click to expand...
Click to collapse
THANK YOU! Everytime I plug in my ET4G to the dock to charge it that stupid MTP crap always comes up. Had no idea I could disable it. Thanks!
yeah, this doesn't always help... I had the same problem when i first got my TF101, and i tried all the tricks, the one mentioned here with mtp, enabling and desabling debug mode, turning off and on with usb plugged in, and some others i can't remember... nothing.
In case anyone else is looking for the answer and the quick tips don't work, what did it for me was installing Android Revolution HD rom. I've read that this problem could also be bootloader related.
Anyways, cheers.
How to connect an ICS device to your computer
Step 1. Connect device to computer via USB
Step 2. Set USB connection as Media Device (MTP) (p.s. if you use a Mac you need to download Android File Transfer)
Step 3. Disable USB debugging if enabled
I hope this helped.
when you need turn off MTP it mean your computer doesn't have driver.
If you need using MTP go to asus page and download driver. it's easy to install driver ^^...
recently I can't understand why same file but the computer at my office can't install that file instead other computers working normal... maybe my work place using old windows version...
Like I wrote earlier - mine was actually in MTP mode, but I had to switch to camera mode and back to MTP for it to start working. Thanks for the replies, though. Hopefully it will help some other people with the same problems
I'm not sure when this problem first appeared. For whatever reason, my phone doesn't show up at all when connected to either of my two PCs. It must have when I first rooted the phone (to load ChainSU) but I'm not sure if the problem is recent or occurred immediately thereafter.
USB debugging is disabled. When I plug my phone into a computer, it attempts to install the MTP Driver and fails. When I uninstall my device, it disappears and I'm unable to manually install the driver's I've downloaded from other threads. When I load into the Bootloader, my device is recognized by Fastboot.
I'm hesitant to factory reset as this will leave me unable to root if the problem persists, which is important to me as I can get rid of the yellow tint on this screen.
Any thoughts?
Edit: $10 via Paypal for anyone who successfully helps me to a solution!
Are you definitely sure usb debugging is disabled? The phone should install as a portable device on your pc. Also ensure to enter your password onto your phone when connected otherwise the phone will not show up its contents.
Make sure for windows media player to be updated to the latest, for the windows mtp driver.
duraeas said:
I'm not sure when this problem first appeared. For whatever reason, my phone doesn't show up at all when connected to either of my two PCs. It must have when I first rooted the phone (to load ChainSU) but I'm not sure if the problem is recent or occurred immediately thereafter.
USB debugging is disabled. When I plug my phone into a computer, it attempts to install the MTP Driver and fails. When I uninstall my device, it disappears and I'm unable to manually install the driver's I've downloaded from other threads. When I load into the Bootloader, my device is recognized by Fastboot.
I'm hesitant to factory reset as this will leave me unable to root if the problem persists, which is important to me as I can get rid of the yellow tint on this screen.
Any thoughts?
Edit: $10 via Paypal for anyone who successfully helps me to a solution!
Click to expand...
Click to collapse
There are a few things you can try. Have you tried uninstalling the drivers completely then reinstalling from the toolkit? In the past, I've had issues where the phone wouldn't be accessible in some way on one computer but would be fine on another, so maybe try a different computer to try to narrow down the problem as to whether it's an issue with the phone or the computer? Also, this may sound a bit ridiculous, but simply switching USB cables and / or ports has fixed detection issues for me in the past as well--something to consider.
Sent via Morse code from my Nexus 4
Remove any existing drivers (while phone is connected), do the same for other android devices if you have any, then reboot and install Universal Naked Drivers. Have always had success with this driver pack.
Rizy7 said:
Are you definitely sure usb debugging is disabled? The phone should install as a portable device on your pc. Also ensure to enter your password onto your phone when connected otherwise the phone will not show up its contents.
Click to expand...
Click to collapse
100% sure on both counts.
I have this same issue with my rooted nexus 4, I've tried 3 different computers and several cables and it never connects to the PC and only charges the phone. It doesn't even give me option to choose media files.
I've had this issue before, my Nexus/Computer was acting in complete stupidity. When connecting the phone to your computer you will see a notification saying "Connected as a media device" on your phone, just touch it, and change it to "Camera (PTP)". It might access the camera for you, but It actually accessed the storage for me.
YeledKaki said:
I've had this issue before, my Nexus/Computer was acting in complete stupidity. When connecting the phone to your computer you will see a notification saying "Connected as a media device" on your phone, just touch it, and change it to "Camera (PTP)". It might access the camera for you, but It actually accessed the storage for me.
Click to expand...
Click to collapse
Thats not the problem, it doesn't give any option. It doesn't show up on the computer at all and only charges. It's the same for every computer.
yuriorkis said:
I have this same issue with my rooted nexus 4, I've tried 3 different computers and several cables and it never connects to the PC and only charges the phone. It doesn't even give me option to choose media files.
Click to expand...
Click to collapse
I'm thinking we've screwed something up with the phone's side of the MTP protocol - mine is totally independent of the cord/computer used. All the correct drivers installed.
Have you tried Factory Resetting? I'm really hoping this is a workable option.
If you have a recovery back up the current Rom and flash stock and see if it's working
Sent from my KFTT using xda premium
if the phone is locked with a pin/password/pattern unlock it.
I had same problem on my pc yesterday. Even if the drivers installer showed up that installation was successful, somehow for a mtp mode system was using some other Microsoft driver. Correct one was only used in ptp mode. So when I connected n4 in mtp mode storage wasn't available, when I switched to ptp mode everything was fine. Turn on your usb debug, switch on mtp and connect. Go to device manager in system, find your nexus there and rmb on it and manually reinstall driver. After this my n4 is visible in system in mtp mode again.
Sent from my Nexus 7 using Tapatalk HD
my screen is cracked and phone is useless now (replacement coming tomorrow) can i connect it and wipe it back to factory before i have to send it out?
K0v4L said:
I had same problem on my pc yesterday. Even if the drivers installer showed up that installation was successful, somehow for a mtp mode system was using some other Microsoft driver. Correct one was only used in ptp mode. So when I connected n4 in mtp mode storage wasn't available, when I switched to ptp mode everything was fine. Turn on your usb debug, switch on mtp and connect. Go to device manager in system, find your nexus there and rmb on it and manually reinstall driver. After this my n4 is visible in system in mtp mode again.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
The problem is that even if I switch between MTP and PTP it still does nothing, I have tried multiple cables, computers and have reflashed the ROM and wiped the device but it still does not connect with the PC. This is frustrating.
yuriorkis said:
The problem is that even if I switch between MTP and PTP it still does nothing, I have tried multiple cables, computers and have reflashed the ROM and wiped the device but it still does not connect with the PC. This is frustrating.
Click to expand...
Click to collapse
Is yours able to connect during Bootloader/Recovery? Fastboot/ADB have no trouble recognizing my device.
It's really odd that if these things work, meaning your USB connection is fine, replacing the all of software fixed nothing... unless MTP occurs at a much lower level of the OS (maybe kernel is corrupted?)
I've got a similar problem that others have posted - PCs not detecting my N4. I got it last Friday (2/1) from Google and after the registering process and updating to 4.2.1, I connected it to my Win7 laptop and it showed on the PC as a drive. But since I couldn't copy/paste Office docs to that drive and had to do that through Dropbox, I didn't bother trying to reconnect until Monday, at which time the PC didn't detect it. Neither will one other Win7 nor two XP (both with WMP10) PCs. Have tried multiple cables, all of which work with other Android devices (pre 3.0). I've seen several suggestions on this and other threads, but one major issue I'm having is that some of the fixes require enabling USB Debugging. For the life of me I can't find that option in the N4's Settings. Unlike my other phones, there is no Applications subcategory under Settings on my N4 (4.2.1, Build JOP40D). Can anyone help me find that option? TIA.
Edit - Found answer. Click on Build in About Phone setting 7 times. That activated Developer options. Now to try the fixes which require USB Debugging mode turned on.
I am trying to install the ADB drivers but my phone is not appearing in the device manager at all for some reason. I have USB Debugging mode turned on but all that pops up when I plug my phone in is the auto play that asks me if I want to open the device to view files. I have no android device listed in my device manager to install drivers to. I have tried on two different computers and my phone is not recognized.
I have the google edition on 4.3
have you tried a different usb cable?
jedinegotiator said:
I am trying to install the ADB drivers but my phone is not appearing in the device manager at all for some reason. I have USB Debugging mode turned on but all that pops up when I plug my phone in is the auto play that asks me if I want to open the device to view files. I have no android device listed in my device manager to install drivers to. I have tried on two different computers and my phone is not recognized.
I have the google edition on 4.3
Click to expand...
Click to collapse
Uninstall and then reinstall Kies and try again bro, that should work bro.
Try a different cable. Had an issue was GNex where it charged fine, connected to the computer okay, but couldn't get adb or use odin. Spent hours trying to figure it out, uninstslling, reinstalling, and rebooting everything under the sun. Then thought maybe, just maybe it might be the cable. Swapped it out, and it worked like a charm.
Sent from my SCH-I545 using Tapatalk 4
Kind of a noob question. But I have enabled USB debugging, installed ADB and Android SDK, downloaded PH-1 drivers, switched from Charge Only, to MTP, to Camera. Nothing I do get's the Notification to allow access on my phone. Anyone had this issue? Thanks
chrisradcliffe23 said:
Kind of a noob question. But I have enabled USB debugging, installed ADB and Android SDK, downloaded PH-1 drivers, switched from Charge Only, to MTP, to Camera. Nothing I do get's the Notification to allow access on my phone. Anyone had this issue? Thanks
Click to expand...
Click to collapse
Yes the same issue, but I don't the notification mtp or other, only I have a charge
chrisradcliffe23 said:
Kind of a noob question. But I have enabled USB debugging, installed ADB and Android SDK, downloaded PH-1 drivers, switched from Charge Only, to MTP, to Camera. Nothing I do get's the Notification to allow access on my phone. Anyone had this issue? Thanks
Click to expand...
Click to collapse
I haven't connected my essential phone to PC, but which cable are you using? If you are using C to C cable that came with the phone, try to use USB A to C cable.
chrisradcliffe23 said:
Kind of a noob question. But I have enabled USB debugging, installed ADB and Android SDK, downloaded PH-1 drivers, switched from Charge Only, to MTP, to Camera. Nothing I do get's the Notification to allow access on my phone. Anyone had this issue? Thanks
Click to expand...
Click to collapse
Assuming you're using Windows, open device manager, plug and unplug your device to see which one it is and with device plugged in, right click on it and uninstall. Then unplug and plug your device back in, and let it do its thing to install the driver.
Instead of uninstalling, you can also right click to update the driver and then choose from drivers installed on your computer and select the right one. I find from my experience, if you uninstall and then manually update if there's an issue works better.
Or start with trying another cable first just in case.
mrcooter said:
Assuming you're using Windows, open device manager, plug and unplug your device to see which one it is and with device plugged in, right click on it and uninstall. Then unplug and plug your device back in, and let it do its thing to install the driver.
Instead of uninstalling, you can also right click to update the driver and then choose from drivers installed on your computer and select the right one. I find from my experience, if you uninstall and then manually update if there's an issue works better.
Or start with trying another cable first just in case.
Click to expand...
Click to collapse
This!
When you plug the cable into the phone it should say in debugging mode.
Got it everyone. Reinstalled ADB and works like a charm.