So when i use ptp i can use asus sync and adb, but as soon as i switch it to mtp none of that works? Why? And if those things are supposed to work does anyone know how i should fix it? (Im on ics unrooted...but trying to lol)
Edit: I fixed it by uninstalling the TP drivers than plugging it back in and re installing drivers for adb.
Related
Ok so im trying to connect the phone USB but it gives me only options like im connecting a camera photo and scan in windows lol? how do u access the phone so that you can transfer files i dont understand, never had a problem connecting a phone this way before.
I had this problem too.
I'm using XP and I had to install a driver for windows called MTP I think it was.
Once I restarted it worked. Make sure it is in MTP mode when plugged in via USB.
Probably worth trying
EDIT: Just realised I think what actually fixed it was installing the Samsung USB Driver for Mobile Phones (I installed 1.4.8.0 which I think was the latest)
Google it and download should do the trick
Thanks that did the trick installing USB drivers, i found them from here if anyone else has the same problem.
http://forum.xda-developers.com/showthread.php?t=961956&page=19
Is anybody else having problems with usb debugging mode not working? I have been trying to root with CASUAL all afternoon and I can NOT get usb debugging mode / adb mode to work. Any suggestions on what I could do to make it work?
Thanks guys/girls.
1stx2 said:
Is anybody else having problems with usb debugging mode not working? I have been trying to root with CASUAL all afternoon and I can NOT get usb debugging mode / adb mode to work. Any suggestions on what I could do to make it work?
Thanks guys/girls.
Click to expand...
Click to collapse
I'm having the same issue.. just bought it and this is driving me crazy! I'm i the process of removing drivers and crapware from verizon, and then figured I would try drivers direct from samsung.. I'll let you know if I have any luck.
travisn000 said:
I'm having the same issue.. just bought it and this is driving me crazy! I'm i the process of removing drivers and crapware from verizon, and then figured I would try drivers direct from samsung.. I'll let you know if I have any luck.
Click to expand...
Click to collapse
It's absolutely crazy isn't it? Please let me know if you figure out the problem. I don't consider myself a noob about rooting/romming/etc but this is making me feel like i just started today!
EDIT:::: I finnally got my phone to connect to my moms laptop but it still wont connect to mine. I got CASUAL to recognize the phone but I'm kind of scared to do it now since my first phone connected perfect the first time and when I started having other problems and needed to send it back and usb debugging WOULD NOT work. I don't want to leave it stock but I don't want to go through what I went through with the first phone again
Ok, I finally got my phone rooted, unlocked using casual. I had to use my moms laptop ( hp, windows 7, 32 bit ) to unlock it, our desktop ( windows xp 32 bit ) to use odin and my laptop to transfer music, vidoes, etc..... Now i absolutely hate installing drivers and windows in general. You would think being 1 of the top-of-line smartphones, **** like this wouldn't be so difficult.
It seems this is a driver issue.. I still couldn't get it to work. I'm guessing that either the old GNex drivers or maybe a windows driver. I recall having a similar issue with another device and I had to go through device manager and remove certain drivers and install others.. That doesn't explain the failure I had with linux thought.. perhaps my adb is out of date??
After updating adb removing/installing various drivers in an old XP install was able to get the phone to be recognized by CASUAL, but casual would would reboot the phone to a "Downloading" recovery screen, and just hang.. CASUAL seemed to be waiting for this screen, but could'nt tell that it had it ???
travisn000 said:
It seems this is a driver issue.. I still couldn't get it to work. I'm guessing that either the old GNex drivers or maybe a windows driver. I recall having a similar issue with another device and I had to go through device manager and remove certain drivers and install others.. That doesn't explain the failure I had with linux thought.. perhaps my adb is out of date??
After updating adb removing/installing various drivers in an old XP install was able to get the phone to be recognized by CASUAL, but casual would would reboot the phone to a "Downloading" recovery screen, and just hang.. CASUAL seemed to be waiting for this screen, but could'nt tell that it had it ???
Click to expand...
Click to collapse
Yep that's the same thing that happened on my windows xp based desktop, it would boot into download mode but it wouldn't recognize the phone. It's got to be a driver related issue though. I had similar issues with my gnex but that was nothing compared to this catastrophe.
Sent from my SCH-I605 using Tapatalk 2
I finally got mine done.. gave up on windows drivers and went back to linux.
I had to switch to a disto that used gksudo & dpkg in order for the CASUAL app to work properly (..my distro of choice is PCLinuxOS, but it doesn't use gksudo or dpkg).
I have the International (i9300) S3 and am running Temasek's ROM (v99.4), but I cannot connect it to my PC via USB. I am currently using AirDroid for all my Phone to PC transfers, but ADB is also not working and this will cause a problem in the future if I manage to brick my device. The only way to use ADB on my device currently is to boot into recovery (PhilZ Touch 5). This problem has been occurring for that last few months, but as I believe it is an isolated incident I didn't post about it. I decided to start this thread to see if anyone was having the same problem and to see if anyone found a work-around or fix for it.
Thanks in advance,
MiracleM4n
EDIT: Turns out it was my cord. For some reason the stock Samsung Micro-USB cable was not working correctly.
have you enabled debugging in developer options, or tried reinstalling all drivers
Thanks for the quick reply. Yes I have reinstalled all drivers and I do have it enabled in Developers Options. It does not show up in Device Manager as "Other devices" so this leads me to believe that it might be an issue with the device itself.
I have tried reinstalling using drivers from Faryaab's thread and it is still not working. I believe this might be an issue I am going to have to live with.
Ok, so I found a few older threads on this, but no tips in them seem to work in my case. I can't seem to get my S4 to see the PC/USB connection and prompt to select Media Device or the like. The USB icon never even appears in the notification bar. The PC recognizes connection (USB tone sounds) and shows device ready to use, but phone never gives the option. Doesn't seem to matter if USB Debugging is checked or not, or anything else that I can find so far. Here's the things I can generally eliminate:
2 different USB cables worked on wife's S4 on two different PCs. Neither cable or PC worked with my S4
Tried reinstalling Samsung USB drivers just to be sure
Cold booted phone
Tried unchecking and re-checking USB debugging (also tried with it unchecked)
So when we take in working fine on wife's S4, I'd generally guess that we can eliminate cable and PC from the potential problem list. Phone is currently on stock rom, but rooted. Outside of that and freezing VZ Support, Knox, and VZ Tones, no other modifications to the OS. At this point, I'm pretty stumped. Any suggestions on other steps to try?
The problem is your USB settings in the hidden dialers. Look for tutorials on how to enable them, and once found, type *#0808#, and a list of usb otions will come up. Pick any with MTP and they'll work again.
Worked perfect. Thanks muchly!
aidankiller4 said:
The problem is your USB settings in the hidden dialers. Look for tutorials on how to enable them, and once found, type *#0808#, and a list of usb otions will come up. Pick any with MTP and they'll work again.
Click to expand...
Click to collapse
Not to threadjack, but...
On a related issue, win update tried to update my samsung ADP, etc drivers and failed. Ever since, I cannot connect to the PC. The PC doesn't even notice that the phone is connected. I tried the above fix to no avail (it is set to MTP) I uninstalled and reinstalled kies, tried troubleshooting the usb connection, ect...
Please help.
Im_Gumby said:
On a related issue, win update tried to update my samsung ADP, etc drivers and failed. Ever since, I cannot connect to the PC. The PC doesn't even notice that the phone is connected. I tried the above fix to no avail (it is set to MTP) I uninstalled and reinstalled kies, tried troubleshooting the usb connection, ect...
Please help.
Click to expand...
Click to collapse
Try installing/reinstalling Kies, it comes bundled with all the samsung drivers you'll need
Tried that. Twice. To no avail.
But it is no longer a problem. I installed eclipse rom and it now works again.
Who knows what went wrong...
And now it's not working again. Reinstalled (dirty) the ROM without any change. Thoughts?
Hello,
I have my HTC EVO 3D with this ROM: http://forum.xda-developers.com/showthread.php?t=2526391 (CyanogenMod 11 - Android 4.4.3) and I cannot connect my phone with computer and use ADB. The reason is propably that when I connect my phone to PC it is shown as Mass Storage with name "HTC" (YES, I have USB debugging on). I have tried to reinstall drivers several times but it still says that my drivers are correct. I have the latest adb (1.0.31).
Thanks for help.
BUMP?
Hey man! My first thought was that you need to update adb but I see you've already done that. Assuming you're not having any driver issues, I want to say that the phone needs to be in charge only mode (not mass storage).
Now if that simple change doesn't help anything, and you're on the updated adb, it has to be a driver issue, cable issue or issue with some other software running on the computer.
HTC sync for example can interfere with fastboot/adb. Even if your drivers are okay.
Also, since jellybean; with the updated adb, there is an on-screen prompt as a newer security feature.
So make sure your screen is awake and check to see that you aren't getting a prompt to allow your computer to communicate with the device via adb.
My phone is in charge-only mode. In the computer my phone appears as a Mass Storage but I don't see it in "My Computer" as a device (only in Device Manager). I have tried to install HTC Sync, uninstall it and so on.. I'have also tried to connect my phone to another computer and it makes same things...
Noone knows?
Interesting fact is that HTC Sync also doesn't see my phone...
This might be far off but have you installed bluestacks or anything similar? It's known to mess with ADB and the like.
Also you could try a Ubuntu live cd as it should eliminate any driver issues.
Arthemedus said:
This might be far off but have you installed bluestacks or anything similar? It's known to mess with ADB and the like.
Click to expand...
Click to collapse
Well, I haven't.
What should I do with Ubuntu?
What version of windows are you running? 8.1? If so yo need to Disable driver security reinforcement (or whatever its called) then install drivers again.
Look here.
This is originally not dedicated to your phone but should work as well.
tom0769 said:
Look here.
This is originally not dedicated to your phone but should work as well.
Click to expand...
Click to collapse
This finally works! Thank you so much. I have no idea why this works because I have tried this several times. Now everything works just perfect!