Database Users

[Q] TF101 doesn't connect with PC through USB

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

[Q] USB Debugging Not Working

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

[Q] Computer not recognizing phone when in USB Debugging Mode

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

ADB Connection mysteriously lost

All along ADB was working fine. Now when I enabled it, nothing is detected on the computer. The phone went entirely missing. If I turn it off, the phone comes back. Anyone encountered this?
With ADB turned off
- Phone works in PTP Mode to PC
- Phone works in MTP Mode to PC
- Phone works in MIDI to PC
With ADB turned on
- No phone device detected at all. So I am not even able to change to any of the ADB drivers

mobileman88 said:
All along ADB was working fine. Now when I enabled it, nothing is detected on the computer. The phone went entirely missing. If I turn it off, the phone comes back. Anyone encountered this?
With ADB turned off
- Phone works in PTP Mode to PC
- Phone works in MTP Mode to PC
- Phone works in MIDI to PC
With ADB turned on
- No phone device detected at all. So I am not even able to change to any of the ADB drivers
Click to expand...
Click to collapse
What do you mean by "ADB turned off" and "ADB turned on"?
Are you talking about USB Debug?
Sent from my interstellar 6P

CyberZeus1977 said:
What do you mean by "ADB turned off" and "ADB turned on"?
Are you talking about USB Debug?
Sent from my interstellar 6P
Click to expand...
Click to collapse
Yes, USB debug in development menu, even turning it on/off, revoke does not seem to make it work again. it just does not show up on my PC.

Further tests done.
Fastboot works.
Adb works in recovery mode when booted into TWRP 3.0.2-3.
Think I need a way to reset the ADB /usb debug settings within the phone as it looks more and more to be an issue from the phone rather than Windows (v7 x64 sp1)

mobileman88 said:
Further tests done.
Fastboot works.
Adb works in recovery mode when booted into TWRP 3.0.2-3.
Think I need a way to reset the ADB /usb debug settings within the phone as it looks more and more to be an issue from the phone rather than Windows (v7 x64 sp1)
Click to expand...
Click to collapse
Not the way I read it. Sounds to me like the exact opposite.... a driver issue with your PC/OS, not the phone. In order for the phone to have adb/fastboot capabilities, the correct drivers need to be installed and actually working on the PC. Without going into detail, you could use a few different tools to REMOVE and install the correct PC drivers. Wug's NRT Toolkit has a very good step-by-step driver configuration guide with verification. I now just use the 15 second ADB installer here on XDA because it is minimalist, and just works. That being said, the NRT has a USB removal tool to rid your system of old USB entries that are likely causing your problem. Give it a whirl.

v12xke said:
Not the way I read it. Sounds to me like the exact opposite.... a driver issue with your PC/OS, not the phone. In order for the phone to have adb/fastboot capabilities, the correct drivers need to be installed and actually working on the PC. Without going into detail, you could use a few different tools to REMOVE and install the correct PC drivers. Wug's NRT Toolkit has a very good step-by-step driver configuration guide with verification. I now just use the 15 second ADB installer here on XDA because it is minimalist, and just works. That being said, the NRT has a USB removal tool to rid your system of old USB entries that are likely causing your problem. Give it a whirl.
Click to expand...
Click to collapse
Shall give it a whirl. Previously it was incorrect driver issue years ago but everything has been working fine on all my Android devices till yesterday when I can't seem to ADB to my 6P. I have the latest USB drivers installed via Android SDK Manager.

v12xke said:
Not the way I read it. Sounds to me like the exact opposite.... a driver issue with your PC/OS, not the phone. In order for the phone to have adb/fastboot capabilities, the correct drivers need to be installed and actually working on the PC. Without going into detail, you could use a few different tools to REMOVE and install the correct PC drivers. Wug's NRT Toolkit has a very good step-by-step driver configuration guide with verification. I now just use the 15 second ADB installer here on XDA because it is minimalist, and just works. That being said, the NRT has a USB removal tool to rid your system of old USB entries that are likely causing your problem. Give it a whirl.
Click to expand...
Click to collapse
Still no go. There's no device at all where I need to change/delete/update driver if I turn on ADB USB mode. Phone is only seen by Windows Device Manager when I turn off USB debugging in developer menu. I still feel it might well be something in the developer menu causing this issue.
I am checking on the folder /data/misc/adb . Permissions is rwxr-s--- . What's the permissions you have for this folder?
Using USBDeview (trying to compare between 2 sets of 6P, both with the December 7.1.1 roms)
6P that works over ADB
Reported VID and PID is 18d1 / 4ee2
6P that does not work over ADB
Reported VID and PID is 18d1 and PID is 4ee1, 4ee5 and 4ee8 depending on which mode (PTP/MTP/MIDI).
Nothing gets reported to be connected at all when I used USBDeview while the 6P that does not connect over ADB USB has USB debugging turned on.

Problem fixed. No idea what was the cause. Hopefully it will help someone else who gets this down the road.
Steps performed
- Clean up SU
- Reboot
- No go
- Reboot to Recovery
- Reflash EFS backup
- Reboot
- No go
- Reboot to recovery
- Clear cache, clear dalvik
- Reboot
- No go
- Reboot to fastboot
- Reflash System, Vendor, Boot
- Reboot
- Works
- Reflash Magisk and PHH
- Still works
Puzzling.

Glad you got it fixed.

v12xke said:
Glad you got it fixed.
Click to expand...
Click to collapse
Yeah, would have done a full factory reset if all else fails since the hardware was indeed able to connect to my PC properly. Glad the various flashing worked out.

Can't get ADB Working on PH-1

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.