Related
[FIXED]
For some reason Toolkit didnt work for me and i used this method to unlock bootloaders and root it.
http://forum.xda-developers.com/showthread.php?t=1362957
Also installed CWM recovery
------------------------------------------------------------------------
I installed my drivers and 1st time when I connected my phone in adb toolkit recognised it and showed his id. Next time when I connected it in adb it didnt recognise it in toolkit but windows recognise my phone and i can access it.
I've rebooted my pc every time and reinstalled couple of drivers:
-Naked samsung drivers
-Pda drivers
-Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0
Nothing worked.
1st time I used Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0 and i tried again and nothing.
I am on Windows 7 64bit version.
If anyone knows how to solve this please share the idea.
sukyman said:
I installed my drivers and 1st time when I connected my phone in adb toolkit recognised it and showed his id. Next time when I connected it in adb it didnt recognise it in toolkit but windows recognise my phone and i can access it.
I've rebooted my pc every time and reinstalled couple of drivers:
-Naked samsung drivers
-Pda drivers
-Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0
Nothing worked.
1st time I used Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0 and i tried again and nothing.
I am on Windows 7 64bit version.
If anyone knows how to solve this please share the idea.
Click to expand...
Click to collapse
I was facing lot of driver issues when connecting my GNex for the first time to the laptop on WinXP. Installing the drivers through the GNex Toolkit also did not work for me.
Finally what worked for me was, installing the latest version of Android SDK with the additional package of Google USB drivers, and then manually selecting the drivers after connecting my phone instead of asking Windows to look for drivers automatically.
I had trouble when first connecting my GNex too. However, these drivers worked for me (plus work with many many other android devices):
http://forum.xda-developers.com/showthread.php?t=1379875
If you have several android devices you'll find that you don't have to install multiple drivers for adb, fastboot, etc. for each of the devices.
Taken from post#3 of the ToolKit thread:
Note 1: If the driver doesnt install automatically then double click on the Android 1.0 item, then click on the driver tab and select 'update driver'. Select 'browse my computer' and then 'Let me pick from a list'. If no items appear in the list then untick 'Show compatible hardware' and find the Android adb driver or Samsung adb driver.
Try that as they may be on your pc and just not installing.
Mark.
Got them working now but i have problem when rooting, using GNex toolkit 5.6
It boots into android, i set usb debugging but when the phone is suppose to boot back to fastboot it gives error device not connected.
What type of drivers are there for the S3?
I understand that you need drivers installed on the computer for it to reecognize the S3
How many driver are there?
Are there any more aside from this?
Where can i download these drivers?
I think ADB has a driver for thisas well?
Thanks!
mikoal said:
What type of drivers are there for the S3?
I understand that you need drivers installed on the computer for it to reecognize the S3
How many driver are there?
Are there any more aside from this?
Where can i download these drivers?
I think ADB has a driver for thisas well?
Thanks!
Click to expand...
Click to collapse
Here is the link to the Driver package for i747 and i747m (AT&T/Bell/Rogers/Telus) With this, you don't need Keis...unless you want to use Keis. Also, TRY a WINDOWS UPDATE after installing this driver package.
I found their to be side issues on my Win7 and XP pc's....too long a story. If you have issues, I will send you a link.
themadproducer said:
Here is the link to the Driver package for i747 and i747m (AT&T/Bell/Rogers/Telus) With this, you don't need Keis...unless you want to use Keis. Also, TRY a WINDOWS UPDATE after installing this driver package.
I found their to be side issues on my Win7 and XP pc's....too long a story. If you have issues, I will send you a link.
Click to expand...
Click to collapse
Thanks mad producer. Is this driver package all the drivers I'll need?
I noticed these drivers are from the samsung site.
Are there any custom drivers or drivers for rooted phone, on custom roms etc?
Are there different kinds/type, I recall reading about ADB drivers or ADB connections.
Can you also send me the link to the issues with the drivers?
Thanks a bunch!
mikoal said:
Thanks mad producer. Is this driver package all the drivers I'll need?
I noticed these drivers are from the samsung site.
Are there any custom drivers or drivers for rooted phone, on custom roms etc?
Are there different kinds/type, I recall reading about ADB drivers or ADB connections.
Can you also send me the link to the issues with the drivers?
Thanks a bunch!
Click to expand...
Click to collapse
If/when you need ADB (I don't use it) then just look around for ADB. I don't have a link for that.
When I first connected my S3 to my Win7, XP, 2nd XP machine, each one had an issue with the MTP protocol. This is what's used to transfer files to and from phone internal and external storage. I did my homework and massive experimenting and solved the issues. (pretty pathetic really) I just don't have a turn key absolute solution but here are some tips. Try one or all of these till it works...and it WILL!
(Backup your PC before attempting and use at your own risk)
XP
- plug your Ss in via usb
- install the samsung drivers
- after any/each of these steps, unplug/replug usb S3 to PC
- check Device Manager in XP for any Yellow exclamation marks. If there are none, then go see if you can transfer large files (eg mp3) to your S3 and back via USB
- if you can then your done
- if not, download this and install
- if it's still not working, (which I doubt) then update windows. After the Samsung drivers are installed on some windows machines, windows updates provides a specific update that helps. I watched it happen/work on 2 machines.
- still not working, get ready....sounds crazy...but install Windows Media Player 11. It is tied into the MTP framework somehow. This is the version I used
Win7
- plug your Ss in via usb
- install the samsung drivers
- after any/each of these steps, unplug/replug usb S3 to PC
- check Device Manager in Win7 for any Yellow exclamation marks. If there are none, then go see if you can transfer large files (eg mp3) to your S3 and back via USB
- if you can then your done
- if it's still not working, (which I doubt) then update windows. (remember to unplug/replug usb after.
- install wmp11 or higher
- if it's still not working, try this file (sorry...can't elaborate on it)
- STILL NOT WORKING...doubt it...but last chance, download this file and place it into c/windows/inf directory and reboot.
I posted another thread with problems with odin and my ace 2. I uninstalled all the samsung driver's, I then reinstalled the samsung driver's and i get all these missing bluetooth driver's and 2 android driver's on my device manager. I can assume this is why odin is not working can anyone help please ? I have attached an image of my device manager. Also the samsung ADB interface driver only pops up when my device is plugged into my computer.
Thanks
Sam
samwage123 said:
I posted another thread with problems with odin and my ace 2. I uninstalled all the samsung driver's, I then reinstalled the samsung driver's and i get all these missing bluetooth driver's and 2 android driver's on my device manager. I can assume this is why odin is not working can anyone help please ? I have attached an image of my device manager. Also the samsung ADB interface driver only pops up when my device is plugged into my computer.
Thanks
Sam
Click to expand...
Click to collapse
I don't know about the bluetooth drivers but indeed Android adb driver should work. So here is what I suggest.
Go to the Samsung Android Phone tab, and uninstall these 2 drivers in there, restart laptop, then go and download the ace 2 drivers from here and see if it works, ah btw let the phone connected during the whole process.
Thanks for the advice i followed your advice, uninstalled both the samsung and ADB then restarted my computer. I then reinstalled the drivers you provided with my device plugged in, while they were installing. I got the bluetooth drivers popup again, Also theres a new thing under my portable devices tab i will post more screenshots this is really boggling me :/
Also this popped up when installing the drivers to do with the bluetooth.....
looks like MTP won't work either eh? Well let's see if it's the phone or the pc
Firstly follow those instuctions to do some troubleshooting.
1) Go to http://www.microsoft.com/en-us/downl....aspx?id=19153
3) Download the file
6) Run it
7) Follow the instuctions (NextNextNextNext)
That's it, now the MTP devices should work correctly.*
(ALSO Try de-selecting usb debugging)
If this won't work then I guess it's a problem with the phone.I read somewhere in a thread that some dude with the same problem on a samsung phone did factory wipe, wiped dalvik, and installed another ROM, then the usb drivers problem got fixed.
Good luck.
EDIT: Also check this site here it seems to have solution regarding the bluetooth peripheral thing.
none of those links work It has also stopped coming up as mtp it now just says GT-I8160. Also i noticed when i start up my computer it fails to start until i unplug it and plug it in again (attached pictures)
Also there is no android adb anymore its just the samsung one.... is this right? i appreciate your help
I am also using a 64bit version of windows 7 if that makes any difference.
Have you tried connecting the phone to some other pc just to know which one is the problem?
I've ran outta ideas...well the problem seems to be with the device itself and if not then it's probably the usb port,maybe insert to another port or try your luck on google, search for something like "windows failed to recognize android phone"or smth similar. I'll do some more research and try to help y'out tomorrow
Sent from my GT-I8160 using xda app-developers app
I tried disabling usb debugging also i tried the drivers on my netbook. I am having really strange problems on there with odin i plug it in and odin wont pick it up and as soon as i unplug it it says added then removed very weird :/ thats only when the phone is in download mode....
Im thinking its either the cable or the phone. Im not sure though..
Remove all Samsung related drivers.
Restart pc
Use cccleaner to clean the registry
Reboot pc
Use the drivers that i have provided in the s advance forum in my all in one guide. Install the drivers without connecting the phone.
After the drivers are installed, turn off internet connection and then connect the phone.
Sent from my GT-I9070 using xda premium
Thanks for the new idea shaaan I have succesfully followed steps 1 and 2. But I am struggling to find your all in one guide would one be kind to link me ? I did a forum search with no luck. Also I am using a galaxy GT-I8160 would using the s drivers matter? and thanks for the help mojito0 I would like to think it isn't the cable or phone, as I have literaly owned them for 8 days (just over a week). I can always see if i can borrow another cable of my friend today though
edit: I found your all in one guide I am now going to attempt what you said
After removing all the samsung related drivers and restarting I get all these devices come up? The device is not plugged in either.
I dont know if this helps atall, but I finished doing what you said ignoring the drivers.... Then went to flash using odin, Put the phone into download mode and noticed that after a couple of seconds of being stuck on setup connection. It then says the GT-I8160 cannot start, Also the mtp and adb android driver is still displaying that yellow explanation mark :/ I am a newbie to android here and dont know the difference betwene the samsung adb and the android one as listed do they both need to be working?
Remove all the displayed devices from other devices, also remove that Samsung adb thingy and also there will be one Samsung related device in the usb section! Remove them all and then follow my steps.
As for your driver query, the drivers are universal for a specific range of devices. The driver version 2.0+ should work for all devices which were released in 2012
Sent from my GT-I9070 using xda premium
It's my first try ever to install a new ROM. I was trying to install CM on my Note 2 (ATT) following the Install_CM_for_t0lte tutorial on cyanogenmod.
Everything was going smoothly until I try to push the CM build with ADB and find that ADB doesn't recognize any devices. I head over the Samsung to get the SGH-I317 USB drivers but the first driver (1.5.45.0) doesn't fix the problem. There's a second driver there (1.5.14.0) and I try it with no luck as well.
I've been searching for an hour and I still don't know what to do. Pretty much everyone says get drivers from Samsung, but they aren't working for me.
The Win7 Device Manager has an entry in "Other devices > SAMSUNG-SGH-I317" that says "The drivers for this device are not installed. (Code 28)".
Things I've tried:
- The drivers from Heimdall's zadig work for Heimdall, but apparently not ADB ("adb devices" is empty).
- I've tried both front and back USB ports with multiple cables.
- I've tried stopping and restarting the adb server
Without the drivers, ADB doesn't see my phone and I can't push a new build to my freshly wiped phone.
Please help!
I had previously rooted my OP3, but accidentally updated it with the OTA open beta update, losing twrp recovery. I'm finding it incredibly difficult to flash twrp again to reroot.
The bootloader is still unlocked, and USB debugging is on with OEM unlocked, but I keep getting FAILED messages when I attempt to flash. "fastboot devices" shows the device (as a series of numbers).
I've tried using the OnePlus3&[email protected]_radaideh, but when attempting to flash it shows the below and then fails:
error: no devices/emulators found
I couldn't get it to work on my computer at home (win10) and read about problems with the OP3 drivers being unsigned (even with driver enforcement off). I'm also struggling on win7 - for some reason, the driver is listed in the Device Manager under the hardware group TP-LINK Android Phone and I can't get it to work using the OnePlus Android Bootloader Interface (under OnePlus, Inc.) or the Android Bootloader Interface (under Google, Inc.).
Could anyone suggest anything I should try?
Win10, Update & Security, Recovery, extended Start, there disable driver signing and then do your thing. Don't reboot or signing is active again.
emuandco said:
Win10, Update & Security, Recovery, extended Start, there disable driver signing and then do your thing. Don't reboot or signing is active again.
Click to expand...
Click to collapse
Thanks for the reply! I tried that and couldn't get past the issues people complained about in a thread on Reddit about Kedacom drivers (can't link).
I'm at work on win7 which I believe should be easier, but still struggling with the problem as described in the post above
justmast said:
Thanks for the reply! I tried that and couldn't get past the issues people complained about in a thread on Reddit about Kedacom drivers (can't link).
I'm at work on win7 which I believe should be easier, but still struggling with the problem as described in the post above
Click to expand...
Click to collapse
Did you use the drivers coming with the phone on a emulated CD drive? These worked very well for me in the past.
EDIT: Yes, Kedacom problem is nice. But changing the driver to the unsigned one manually worked for me in the past.
emuandco said:
Did you use the drivers coming with the phone on a emulated CD drive? These worked very well for me in the past.
EDIT: Yes, Kedacom problem is nice. But changing the driver to the unsigned one manually worked for me in the past.
Click to expand...
Click to collapse
Yes, I have tried those drivers (the OnePlus, Inc. ones). They worked for me when I rooted originally, I'm having trouble now though
justmast said:
Yes, I have tried those drivers (the OnePlus, Inc. ones). They worked for me when I rooted originally, I'm having trouble now though
Click to expand...
Click to collapse
Yep I was here aswell. Boot into driver signature mode and install the proper drivers. If you connect your device you can change the drivers. I don't have a PC next to me so I can't give you exact steps. The unbrick tool has the proper drivers, just follow the first few steps of that instruction to get it to show up as Qualcomm or something else as long as it isn't Kedacom.