When I usb my gs3 into my macbook nothing happens whatsoever. Anyone fix/had this problem?
Turn on usb debugging and install Kies. The Mac can't read mtp devices natively.
Also try installing android file transfer from your Web browser. It allows your Mac to read your S3
gunnyman said:
Turn on usb debugging and install Kies. The Mac can't read mtp devices natively.
Click to expand...
Click to collapse
Did what you said and it's still not reading
CamFlawless said:
Also try installing android file transfer from your Web browser. It allows your Mac to read your S3
Click to expand...
Click to collapse
Also doesn't work
DarthDerron said:
Also doesn't work
Click to expand...
Click to collapse
What ROM are you on?
Kies air works but you can't update roms with it
DarthDerron said:
When I usb my gs3 into my macbook nothing happens whatsoever. Anyone fix/had this problem?
Click to expand...
Click to collapse
Try this. I got it from this other thread and it worked for me.
I had this problem too with my macbook pro then I found a solution tonight. Try this:
1. Install Kies if you haven't already, if you have make sure it's updated.
2. Connect your phone.
3. In Kies, click Tools, then Install Drivers (this will reinstall drivers
4. Download Android File Transfer.
Should work after this. Also make sure you have USB Debugging on and use PTP not MTP.
stbtigerr said:
Try this. I got it from this other thread and it worked for me.
I had this problem too with my macbook pro then I found a solution tonight. Try this:
1. Install Kies if you haven't already, if you have make sure it's updated.
2. Connect your phone.
3. In Kies, click Tools, then Install Drivers (this will reinstall drivers
4. Download Android File Transfer.
Should work after this. Also make sure you have USB Debugging on and use PTP not MTP.
Click to expand...
Click to collapse
This worked! Thanks so much. Thanks to everyone in this thread as well, appreciate all the help
DarthDerron said:
This worked! Thanks so much. Thanks to everyone in this thread as well, appreciate all the help
Click to expand...
Click to collapse
No problem, glad I could help. I had the same issue as soon as I updated to JB.
Related
Alright everyone I'm a EVO User but My friend is trying to root his Epic and is haveing problems we tried z4root and then tried to flash clockwork through rom manager with out a PC. When trying a PC it won't recognize the phone he is running a 64bit system and was going to try the one-click root that flashes Clockwork as well but since his PC won't recognize the phone he can't we have tried the 64bit drivers as well and nothing any help is greatly appreciated thank you
You need to try different USB cables and different USB ports on your PC. Usually on a desktop the USB port in the back is the best. Try to uninstall the epic drivers and then reinstall.them. this has worked.for.me before. And like you found out you can't use Tom manager to flash cwm on the stock kernel. Rom manager says it flashed it but it doesn't. Just try the tips I gave you and see if.it works. Good.luck
Sent from my Evo Killer!!!
your just better off get the one click clockwork mod and reinstalling your drivers. the samsung driver are a pain to get working
system155 said:
your just better off get the one click clockwork mod and reinstalling your drivers. the samsung driver are a pain to get working
Click to expand...
Click to collapse
I have windows 7 64 and have never had problems with the samsung usb drivers or one click root/cwm. When the first attempt fails, chances are you need to retrace your steps and redo them. Use the rear usb port and be sure to reboot after installing drivers. That always helps me.
sent from my brain telepathically :-D
Is usb debugging on?
Also when you plug it in just leave it alone
Then run the one click
Sent from my SPH-D700 using XDA App
A_Flying_Fox said:
Is usb debugging on?
Also when you plug it in just leave it alone
Then run the one click
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Yes it is and tried that when we run the exploit it just closes out a second later
Jbcarrera said:
Yes it is and tried that when we run the exploit it just closes out a second later
Click to expand...
Click to collapse
If you are having a driver issue (still) try installing PDAnet. I have Win7 Ultimate 64 bit and couldn't get any of the linked samsung drivers to install and correctly recognize my phone. I installed PDAnet, selected Samsung and viola... worky.
If that still doesn't work for you, try a different USB cable.
Once you get the drivers working properly, and have a good cable, the one click root/clockwork mod installer will work like a champ.
These steps should work for you.
I bought a new laptop and it's 64 bit running Windows 7. I'm trying to install the 64 bit USB driver & get it to recognize my phone but it simply won't work.
The following two things keep running and running with the words "installing driver software" after them:
CDC Abstract Control Model (ACM)
S3C6410 Android ADB
I have no idea how to get this to work so any advice is greatly appreciated!
ps - USB debugging is checked in my application settings.
There are lots of people having problems with 64 bit windows nit recognizing the epic. My suggestion is to try.another USB cable. I use my wife's evo cable and it works fine for me. Good luck man just keep trying. Try different ports, cables and also check.to.make sure the USB slot is clear from any obstructions.
Sent From My Evo Killer!
musclehead84 said:
There are lots of people having problems with 64 bit windows nit recognizing the epic. My suggestion is to try.another USB cable. I use my wife's evo cable and it works fine for me. Good luck man just keep trying. Try different ports, cables and also check.to.make sure the USB slot is clear from any obstructions.
Sent From My Evo Killer!
Click to expand...
Click to collapse
I've done all those things.
Install the 32-bit drivers even if you're on a 64 bit computer
iSaint said:
Install the 32-bit drivers even if you're on a 64 bit computer
Click to expand...
Click to collapse
I was going to try that but didn't want to screw anything up...so that should work then?
droid newb said:
I was going to try that but didn't want to screw anything up...so that should work then?
Click to expand...
Click to collapse
Yes, I have 64bit computer and mine works with 32bit drivers.
Doing the same thing with 32 bit that it does with 64 bit.
droid newb said:
Doing the same thing with 32 bit that it does with 64 bit.
Click to expand...
Click to collapse
Here is a link to the drivers I installed on my Win 7 Ultimate 64bit machine. (i put them on my google documents site)
https://docs.google.com/leaf?id=0B8DFupwiCOXyMGViMDJmY2MtMGU4YS00MGY5LWFkOGItNjkyMDY3MjkyNjgx&hl=en
I have had no issues using odin or mass storage.
Hope this helps, good luck
jdelano said:
Here is a link to the drivers I installed on my Win 7 Ultimate 64bit machine. (i put them on my google documents site)
https://docs.google.com/leaf?id=0B8DFupwiCOXyMGViMDJmY2MtMGU4YS00MGY5LWFkOGItNjkyMDY3MjkyNjgx&hl=en
I have had no issues using odin or mass storage.
Hope this helps, good luck
Click to expand...
Click to collapse
That's the same one I've been trying all this time. I just don't understand why this won't work.
The ACS Module has never installed for me but my device works fine
watermoore said:
The ACS Module has never installed for me but my device works fine
Click to expand...
Click to collapse
So would you be able to Odin back to stock if you needed to?
droid newb said:
That's the same one I've been trying all this time. I just don't understand why this won't work.
Click to expand...
Click to collapse
When you ran the setup for the driver, did you run it as administrator?
Right click on setup.exe and select that option from the menu.
Sorry you're having such a bad time, that has got to be mega-frustrating.
I've read also, that some people run the 32 bit drivers on win 7 64bit and they report that they work for them just fine.
hey man i feel your pain. I have been having the same exact problems as you. I also have tried the 64 bit/32bit drivers, uninstalling/reinstalling them, everything i can think of or have been told to do to no avail. It use to work fine until i got the first froyo update eb13 and ever since its been like this. My laptop keeps telling me to replace my device.
I did get on a computer at work with win XP and i plugged my phone into it and the device installed but im not sure about the drivers. Im limited to what i can do at work. So maybe it has something to do with windows 7 cause my laptop is brand new as most people having this problem are to.
Did the drivers change after the EC05 update. Neither of my computers will recognize my phone now after I updated the modem. I even tried reinstalling the links you have in this post and updating drivers and still a no go.
I just had this problem recently. It wasn't the drivers - instead, it was the USB port I was using. If you're on a desktop, try a usb port on the back of the pc. If you're on a laptop, give all the usb ports a go.
Sent from my SPH-D700 using XDA Premium App
I am on a laptop and i have repeatedly try all usb ports and still a no go. It really seems like something changed after EB13 cause i never had a problem before.
dazednconfused1144 said:
Did the drivers change after the EC05 update. Neither of my computers will recognize my phone now after I updated the modem. I even tried reinstalling the links you have in this post and updating drivers and still a no go.
Click to expand...
Click to collapse
Nope; I have a win7 ultimate 32 laptop and a win 7 ultimate 64 desktop. Both see my phone just fine. Same drivers from when I first rooted after xmas to DK28 from 2.1.
I have heard of people having an issue with something bent on the phone's usb connector, it stops from getting full connection.
I'm having the same issue, but I can connect when I uncheck USB debugging. With it checked, it won't connect. I'm trying to root with 2.5.5...
jerbeck24 said:
I'm having the same issue, but I can connect when I uncheck USB debugging. With it checked, it won't connect. I'm trying to root with 2.5.5...
Click to expand...
Click to collapse
That worked!!!!!!!!!!!
Wooooooooooooooooooo!!!!!!!!!!!!!!!!!!!
droid newb said:
That worked!!!!!!!!!!!
Wooooooooooooooooooo!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
No problem...problem for me is, it needs to be checked in order to root...
I'm just going to odin back to EB13 and CWM3 and restore my latest back up of ACS 1.0.2
When I connect my Nexus 7 to my windows 7 computer it is not recognized in MTP, but is when I change it to PTP. When I connect my 1st gen Nexus 7 to the same computer it is recognized fine and I am able to transfer files. I have all the drivers installed and adb works when I am in PTP I just cant transfer any files. Has anyone else experienced this problem or is there maybe something wrong with my Nexus?
Check out this thread. I was experiencing similar issues although I didn't test out PTP .
Sent from my Galaxy Nexus using xda app-developers app
Disregard. I figured it out. It was a driver issue after all.
How did you fix it? I have the same problem. Is root needed to view transfer files via USB?
My N7 2013 won't connect with my Macbook Pro. I already have the Android File Transfer app, which works fine with my Nexus 4, but it won't recognize the Nexus 7 2013. It charges, but no connection. Anyone have any ideas?
lucastmw said:
My N7 2013 won't connect with my Macbook Pro. I already have the Android File Transfer app, which works fine with my Nexus 4, but it won't recognize the Nexus 7 2013. It charges, but no connection. Anyone have any ideas?
Click to expand...
Click to collapse
Might be a silly question but did you enable USB debugging in developer tools.
Sent from my Galaxy Nexus using xda premium
jmileti said:
Might be a silly question but did you enable USB debugging in developer tools.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yes, I tried it with debugging on and off.
thaliagoo said:
How did you fix it? I have the same problem. Is root needed to view transfer files via USB?
Click to expand...
Click to collapse
Root is not needed to transfer files via USB. I just uninstalled the previous driver and updated to the latest and that worked for me.
No matter what, I always keep getting error code 10, device cannot be started when I install the new nexus 7 drivers Android ADB device (from the previous posts- Nexus 7 root). I'm not even trying to root, just trying to install drivers correctly.
thaliagoo said:
No matter what, I always keep getting error code 10, device cannot be started when I install the new nexus 7 drivers Android ADB device (from the previous posts- Nexus 7 root). I'm not even trying to root, just trying to install drivers correctly.
Click to expand...
Click to collapse
These are the drivers I used... http://developer.android.com/sdk/win-usb.html
fixed mine by just forcing it to reinstall the drivers.
fstbusa said:
fixed mine by just forcing it to reinstall the drivers.
Click to expand...
Click to collapse
How did you force it do that? I've actually never ran into this problem. Windows 8 is what I'm running.
dirtyfingers said:
These are the drivers I used... http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
It is definitely a driver issue. I had to uninstall my drivers and then manually install others, because I had a Nexus 7 2012. Those drivers were showing up as *up to date* according to windows, but the device was not working. Total clean install worked to correct it.
Xirix12 said:
How did you force it do that? I've actually never ran into this problem. Windows 8 is what I'm running.
Click to expand...
Click to collapse
In device manager, go to the properties of each android device. I had one near the top of the list and one lower under portable devices. Click update driver and navigate to your updated drivers folder.
It should update them. The device listed under portable devices had mtp as part of the title so I figured that one was the problem.
Sent from my Nexus 7 using xda app-developers app
To anybody who comes to this thread looking for help.
Go to device manager, and under devices remove the Google ADB Driver. This drove me nuts. All of my nexus devices wouldn't connect because they lacked an external SD.
Sent from my Nexus 7 using XDA Premium HD app
I've tried every suggestion in all of these threads so far & nothing worked. Even after I deleted the ADB drivers, windows 7 would automatically reinstall them. When I tried to update the drivers, win7 said they already had the best drivers (ADB).
Here's what worked for me:
I had to turn off USB debugging, delete the ADB drivers in Device Manager, then reboot the device while it's still plugged in. Windows recognized the device as an MTP device & installed the drivers before it even fully booted.
i installed the drivers from the link in this thread and still no luck, i am running the latest paranoid android rom, and tried it on 8 different computers with 23 different cables and no luck - would it help if i flashed a stock rom ? otherwise i dont know what to do - any help would be appreciated, thanks, chris
edit flashed a stock rom and now it is working again - came right up on my pc, i am selling it today to buy the 32gb and just wanted to get me twrp backups off it
golfinggino said:
i installed the drivers from the link in this thread and still no luck, i am running the latest paranoid android rom, and tried it on 8 different computers with 23 different cables and no luck - would it help if i flashed a stock rom ? otherwise i dont know what to do - any help would be appreciated, thanks, chris
edit flashed a stock rom and now it is working again - came right up on my pc, i am selling it today to buy the 32gb and just wanted to get me twrp backups off it
Click to expand...
Click to collapse
I have the same problem. When I was using stock ROM I could connect fine to my PC. When I installed CM10.2 I can not longer connect. i have no problem when I try it with my phone though.
huizingajm said:
I have the same problem. When I was using stock ROM I could connect fine to my PC. When I installed CM10.2 I can not longer connect. i have no problem when I try it with my phone though.
Click to expand...
Click to collapse
After helping someone with Paranoid ROM, I think the problem you are experiencing may be on the ROM/kernel side. Part of the problem is the custom ROM was sending out different USB IDs from stock. I was able to help them force the recognition of the MTP device from a driver standpoint on windows, but the MTP device wouldn't start up when windows tried to initialize it.
sfhub said:
After helping someone with Paranoid ROM, I think the problem you are experiencing may be on the ROM/kernel side. Part of the problem is the custom ROM was sending out different USB IDs from stock. I was able to help them force the recognition of the MTP device from a driver standpoint on windows, but the MTP device wouldn't start up when windows tried to initialize it.
Click to expand...
Click to collapse
I switched kernels to stock to jassy to tiny. None of them work so it has to be the ROM. I am just going to use WiFi transfer of files. Nothing major right now while everything is still new to 4.3.
Kies 3 saids it not supported for my device? Should i use kies 2.6? I have all the usb drivers and everything. Runing Windows 8.1 and cm11 rom and galaxy tab s 10.5. Help!
DUHAsianSKILLZ said:
Kies 3 saids it not supported for my device? Should i use kies 2.6? I have all the usb drivers and everything. Runing Windows 8.1 and cm11 rom and galaxy tab s 10.5. Help!
Click to expand...
Click to collapse
I had this issue, it was because I grabbed the wrong white USB cable! Added a tag to the correct one so it won't happen again!
flhthemi said:
I had this issue, it was because I grabbed the wrong white USB cable! Added a tag to the correct one so it won't happen again!
Click to expand...
Click to collapse
Well im using my stock usb cable that came with my tab s. It worked a month agoñ
Maybe try a different cable or USB port. I know sometimes I plug mine in to a USB hub and it starts installing the drivers again because I didn't use the same port...strange I know but it could be missing the drivers it needs. You can open the device manager in Windows and see if everything is being found....other than that this n00b is stumped because it's working on mine. So Kies 3 does work on this tablet.
flhthemi said:
Maybe try a different cable or USB port. I know sometimes I plug mine in to a USB hub and it starts installing the drivers again because I didn't use the same port...strange I know but it could be missing the drivers it needs. You can open the device manager in Windows and see if everything is being found....other than that this n00b is stumped because it's working on mine. So Kies 3 does work on this tablet.
Click to expand...
Click to collapse
I look into that, check the drivers, may I ask what is the driver called in the device manager? Shouldnt be usb andriod something?
DUHAsianSKILLZ said:
I look into that, check the drivers, may I ask what is the driver called in the device manager? Shouldnt be usb andriod something?
Click to expand...
Click to collapse
Here is my device manager with the S connected...but there are a lot of drivers that get installed and I don't think it wise to take the automatic install of Windows drivers. If you have Kies installed anytime it needs driver you should stop it from getting them from Windows Update and get them from C:\Program Files\SAMSUNG\USB Drivers. Keis has an option to reinstall the drivers. Might try that if something is missing. OR Download the driver package from Samsung Support and install it.
Thanks ill check if anything is wrong with the drivers or usb cable and will post back
Edit! Kies will not work on custom roms! Only stock rooted or stock based Roms will work. Thanks you all for helping me as I reverted back to see if it was the os. Cm11 doesn't have support for kies
After the update to Nougat, my PC does not recognize my OP3, doesn't even show any mobile device in Device Manager! Please suggest, tried resetting phone, restarting laptop, installed drivers also, nothing working
Update: So after starting from scratch, following the guide https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757 I reinstalled 4.0.2 and everything working smooth as ever, surprisingly, laptop recognizes phone in fastboot and adb, but not MTP.
What can be done? anyone
And of you boot into fastboot?
Puddi_Puddin said:
And of you boot into fastboot?
Click to expand...
Click to collapse
it doesn't recognise there also
Dipinn Verma said:
it doesn't recognise there also
Click to expand...
Click to collapse
It doesn't boot? Try unbrick method 2.
Puddi_Puddin said:
It doesn't boot? Try unbrick method 2.
Click to expand...
Click to collapse
no, the phone is working fine, and surprisingly works with any other laptop, but not the one through which I updated it to nougat, the one which I have always used it with
Dipinn Verma said:
no, the phone is working fine, and surprisingly works with any other laptop, but not the one through which I updated it to nougat, the one which I have always used it with
Click to expand...
Click to collapse
Hmm, and when you phone is on does it show something in the notification row?
Puddi_Puddin said:
Hmm, and when you phone is on does it show something in the notification row?
Click to expand...
Click to collapse
no nothing out of ordinary, even when I switch on mass storage, nothing, I have the verity-error also, can that be the problem? coz I lost my twrp and root when updated, should I do everything again from scratch ?
Dipinn Verma said:
no nothing out of ordinary, even when I switch on mass storage, nothing, I have the verity-error also, can that be the problem? coz I lost my twrp and root when updated, should I do everything again from scratch ?
Click to expand...
Click to collapse
DM verity should be a issue, I do recommend you to start from scratch..
Puddi_Puddin said:
DM verity should be a issue, I do recommend you to start from scratch..
Click to expand...
Click to collapse
thanks a ton for prompt reply ! I'll post here how it goes, it might help someone else
Dipinn Verma said:
thanks a ton for prompt reply ! I'll post here how it goes, it might help someone else
Click to expand...
Click to collapse
DM-verity is a non issue with MTP/fastboot/adb. It's usually related to the USB cable or port itself, or a driver issue (fastboot/adb or device).
When you connect and toggle the USB setting to MTP, toggle it to charge only then to MTP again. I've noticed in the past that it takes longer for the PC to recognize or it requires a second try.
Hw4ng3r said:
DM-verity is a non issue with MTP/fastboot/adb. It's usually related to the USB cable or port itself, or a driver issue (fastboot/adb or device).
When you connect and toggle the USB setting to MTP, toggle it to charge only then to MTP again. I've noticed in the past that it takes longer for the PC to recognize or it requires a second try.
Click to expand...
Click to collapse
okay, so this is strange, i did what you said, PTP mode is working, only pictures are accessible though, nothing else, so the problem seems to be with MTP only
It's from windows. I think youre on windows 10 and have updated without knowing. Then youre phone it's not recongnise by pc.
Reinstall windows.
null0seven said:
It's from windows. I think youre on windows 10 and have updated without knowing. Then youre phone it's not recongnise by pc.
Reinstall windows.
Click to expand...
Click to collapse
windows 8.1 only, hasn't changed. I'll try following this guide tomorrow : https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757
and start from scratch, please suggest if I should be following any other guide if there is one. Thanks.
Mate, i can't tell you what to do.
On my case, it was windows 10. How i know? I try co connect at work (windows 7) & it workt fine. Reinstal windows, all ok.
FIRST, i suggest to check on another PC. If it works, 100% it's youre windows.
Ok so this is what I did. I went to device manager > right click mtp > update driver software > browse my computer > let me pick > mtp USB device > happy me ??
Good for you buddy, the mtp option doesn't even come up in device manager, it used to earlier, but not anymore
Dipinn Verma said:
Good for you buddy, the mtp option doesn't even come up in device manager, it used to earlier, but not anymore
Click to expand...
Click to collapse
Then idk what to tell yu
It may sound stupid but my windows 7 couldnt detect my op3 as well ytd..
Then I restarted both my phone and pc and it worked.
No buddy, not at all stupid, though that didn't work for me