I suppose I'll update this whenever there's a new driver version at https://developer.samsung.com/android-usb-driver.
Samsung Android USB Driver for Windows v1.7.56
(37.29MB)|May 25, 2022
Related
Motorola USB Drivers (for Windows®)
This USB Driver is used for connecting your Motorola Mobile Device or tablet to a Windows® computer via a USB cable in order for the computer to recognize the device.
Supported Products
This USB Driver supports most Motorola Android, Motorola OS, Motorola Linux OS, Motorola iDEN, Motorola Symbian/UIQ, Motorola Windows Mobile® and Motorola i-mode devices. In addition, this USB driver now supports the Motorola XOOM™ tablet.
System Requirements
A 32-bit or 64-bit version of Windows 2000®, Windows XP®, Windows Vista® or Windows 7® Operating system.
You must have Administrator permission to install this driver.
Notes
We recommend you reboot the system after installing the USB Driver.
Download Motorola 5.4.0 Driver with MotoHelper here
Click to expand...
Click to collapse
Wait, does the phone not just change normally when connected? I have never had an issue with that on my old phones...
I have a Kinde fire HD 7" that I rooted for a neighbours son which he managed to brick within 20 Mins of getting it back, I think the battery died on him when he was installing something. Now when I plug the Kindle into my system which runs Linux I get the following in the logs.
Feb 13 15:01:05 kernel: [ 161.419037] usb 1-5: new high speed USB device using ehci_hcd and address 5
Feb 13 15:01:05 kernel: [ 161.533760] usb 1-5: New USB device found, idVendor=0451, idProduct=d010
Feb 13 15:01:05 kernel: [ 161.533767] usb 1-5: New USB device strings: Mfr=33, Product=37, SerialNumber=0
Feb 13 15:01:05 kernel: [ 161.533772] usb 1-5: Product: OMAP4440
Feb 13 15:01:05 kernel: [ 161.533775] usb 1-5: Manufacturer: Texas Instruments
Feb 13 15:01:05 mtp-probe: checking bus 1, device 5: "/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-5"
Feb 13 15:01:05 mtp-probe: bus: 1, device: 5 was not an MTP device
Feb 13 15:01:08 kernel: [ 164.534204] usb 1-5: USB disconnect, address 5
Feb 13 15:01:08 kernel: [ 165.305041] usb 1-5: new high speed USB device using ehci_hcd and address 6
Feb 13 15:01:09 kernel: [ 165.419856] usb 1-5: New USB device found, idVendor=0451, idProduct=d010
Feb 13 15:01:09 kernel: [ 165.419863] usb 1-5: New USB device strings: Mfr=33, Product=37, SerialNumber=0
Feb 13 15:01:09 kernel: [ 165.419868] usb 1-5: Product: OMAP4440
Feb 13 15:01:09 kernel: [ 165.419871] usb 1-5: Manufacturer: Texas Instruments
Feb 13 15:01:09 mtp-probe: checking bus 1, device 6: "/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-5"
Feb 13 15:01:09 mtp-probe: bus: 1, device: 6 was not an MTP device
Feb 13 15:01:12 kernel: [ 168.420300] usb 1-5: USB disconnect, address 6`
Click to expand...
Click to collapse
This repeats ad infinitum, well at least 30 times I unplugged it after that.
My question is this, will I be able to to restore the Kindle using the Factory cable from SkOrPn or is this a case where I need to send it back to Amazon ??
Any help would be much appreciated.
JBDegriz said:
I have a Kinde fire HD 7" that I rooted for a neighbours son which he managed to brick within 20 Mins of getting it back, I think the battery died on him when he was installing something. Now when I plug the Kindle into my system which runs Linux I get the following in the logs.
This repeats ad infinitum, well at least 30 times I unplugged it after that.
My question is this, will I be able to to restore the Kindle using the Factory cable from SkOrPn or is this a case where I need to send it back to Amazon ??
Any help would be much appreciated.
Click to expand...
Click to collapse
Is the device still able to comunicate with ADB? If it can then you do not need a fastboot cable. If it does not then yes you will need one to restore it..
lacoursiere18 said:
Is the device still able to comunicate with ADB? If it can then you do not need a fastboot cable. If it does not then yes you will need one to restore it..
Click to expand...
Click to collapse
No ADB never sees the device any more as the USB just keeps reconnecting and disconnecting. The same thing happens in windows where I keep getting the sound when you connect a usb device over and over again and windows looks for a device driver for an OMAP4440, which I believe is the CPU in the Kindle.
So I need to know that in a situation like this that the Factory cable would actually help, I'm sure I read somewhere that fastboot mode needs a working bootloader and I'm not sure that this kindles bootloader is still there.
Thanks
JBDegriz said:
No ADB never sees the device any more as the USB just keeps reconnecting and disconnecting. The same thing happens in windows where I keep getting the sound when you connect a usb device over and over again and windows looks for a device driver for an OMAP4440, which I believe is the CPU in the Kindle.
So I need to know that in a situation like this that the Factory cable would actually help, I'm sure I read somewhere that fastboot mode needs a working bootloader and I'm not sure that this kindles bootloader is still there.
Thanks
Click to expand...
Click to collapse
Yea it doesn't sound like it's in working order, so yes, a fastboot cable would be need to get the device back in action..
Hi, I have the same problem, did you manage to cure it with the skorn cable, I am asking because I have made a factory cable myself but its giving the same problem.
lacoursiere18 said:
Yea it doesn't sound like it's in working order, so yes, a fastboot cable would be need to get the device back in action..
Click to expand...
Click to collapse
devilxmax said:
Hi, I have the same problem, did you manage to cure it with the skorn cable, I am asking because I have made a factory cable myself but its giving the same problem.
Click to expand...
Click to collapse
No I'm afraid not. If your device is being recognised as an OMAP4440 then your out of luck as there are no drivers for this yet. I had to send my device back to Amazon who replaced it no questions asked.
A good thread to check is http://forum.xda-developers.com/showthread.php?t=2096888 post a few details of your problem on that thread and you will get a helpful response.
Good luck
quick info:
Drivers: 4.2.0.001
ROM: Android Revolution HD 31.0
Windows 7
Android API SDK installed 14, 17, 18, 19
I'm trying to make/debug a program, but my none of the android tools/monitors pick up my phone. I'm unable to push to and debug on my phone. I've rebooted both my phone and computer multiple times. Enabled, and disabled USB debugging, and Developer options with every different combanation with rebooting.
I've done all I can think of besides installing a different ROM. Does anyone have any ideas?
1 thing I noticed, CDC Serial Drivers fail to install?
Ive got a small problem if any 1 can help i have this bat file i made and cant get it to work properly...it simply chmod's files on the system to 0777 permissions please help......i have a syntax error somewhere please help
check attachments
MOD EDIT:
file removed, as it is not a .bat, it is showing as a .exe
Annon420 said:
Ive got a small problem if any 1 can help i have this bat file i made and cant get it to work properly...it simply chmod's files on the system to 0777 permissions please help......i have a syntax error somewhere please help
check attachments
Click to expand...
Click to collapse
Discovered:
April 2, 2003
Updated:
February 13, 2007 11:45:10 AM
Also Known As:
Backdoor.GrayBird [KAV], BackDoor-ARR [McAfee]
Type:
Trojan Horse
Systems Affected:
Windows 2000, Windows 95, Windows 98, Windows Me, Windows NT, Windows XP
Backdoor.Graybird is a back door Trojan Horse that gives its creator unauthorized access to your computer. The existence of the file, Svch0st.exe, is an indication of a possible infection. Backdoor.Graybird is a Delphi application.
Antivirus Protection Dates
Initial Rapid Release version April 2, 2003
Latest Rapid Release version December 20, 2013 revision 006
Initial Daily Certified version April 2, 2003 revision 007
Latest Daily Certified version December 20, 2013 revision 008
Initial Weekly Certified release date April 2, 2003
Click here for a more detailed description of Rapid Release and Daily Certified virus definitions.
Threat Assessment
Wild
Wild Level: Low
Number of Infections: 0 - 49
Number of Sites: 0 - 2
Geographical Distribution: Low
Threat Containment: Easy
Removal: Moderate
Damage
Damage Level: Medium
Distribution
Distribution Level: Low
Writeup By: Serghei Sevcenco
If any mods could Delete his zip. That would be great.
Your file has been removed, as it was not a .bat file
Please adjust your thread name for more than "help"
You could say something like, I need help with a .bat file
Thank you
TonyStark
Hello,
Trying to get Nexus 7 (2013) Lollipop to operate with Android Studio v1.0.2 on a Windows 7 platform.
minSdkVersion 8
targetSdkVersion 21
When Run/Choose Device is displayed, and a real device is selected, I get the following error:
Error: minSdk(API 8) > deviceAdk(API 1)
These are my settings for the SDK/Extras:
I cannot locate any setting for the deviceSdk level, so I have concentrated on the ADB driver itself and currently have the latest_usb_driver_windows.zip - Google 32/64 ADB Driver - "Android Composite ADB Interface" installed. This driver is dated 8/28/2014.
A previous driver http://www.koushikdutta.com/post/universal-adb-driver
from ClockworkMod had been installed with the same results. ClockworkMod, Android Device, "Google Nexus ADB Interface"
Several system restarts have been done after ADB drivers have been changed.
Can someone please direct me to the answer for the deviceSdk API level error?
Thank-you.
It appears to be FIXED! I confirmed the functionality only yesterday.
Not sure exactly what the issue was, but I noticed that jre1.8.0_31 kept wanting to load an update. Apparently the JDK/JRE pairing was in error.
Removed JDK/JRE7; reinstalled JDK/JRE8 for Win64.
Environment Variables
ANDROID_SDK_ROOT
C:\Users\<name>\AppData\Local\Android\sdk
JAVA_HOME
C:\Program Files\Java\jdk1.8.0_25
With this configuration I can now use an AVD and can use the Debug facilities (Breakpoint, Step, StepOver).
caprock said:
Hello,
Trying to get Nexus 7 (2013) Lollipop to operate with Android Studio v1.0.2 on a Windows 7 platform.
minSdkVersion 8
targetSdkVersion 21
When Run/Choose Device is displayed, and a real device is selected, I get the following error:
Error: minSdk(API 8) > deviceAdk(API 1)
These are my settings for the SDK/Extras:
I cannot locate any setting for the deviceSdk level, so I have concentrated on the ADB driver itself and currently have the latest_usb_driver_windows.zip - Google 32/64 ADB Driver - "Android Composite ADB Interface" installed. This driver is dated 8/28/2014.
A previous driver http://www.koushikdutta.com/post/universal-adb-driver
from ClockworkMod had been installed with the same results. ClockworkMod, Android Device, "Google Nexus ADB Interface"
Several system restarts have been done after ADB drivers have been changed.
Can someone please direct me to the answer for the deviceSdk API level error?
Thank-you.
Click to expand...
Click to collapse