Related
Here i'm offering you a RAR Archive* that contains the lastest drivers separated by folder with:
[*]ADB
[*]Flash Mode
[*]Fastboot
I see some guys with problems to get drivers and another issues.
This drivers works at least in Windows 8, tested and approved by me, but in Windows 8 you need to MANUALLY install the drivers.
If you like, say thanks.
Download Link - Uploaded.to
*RAR Archive: It can only be oppened by a RAR Decompressor like WinRAR.
Thanks, I've been waiting for that for ages!
Do not do this Linux Mint ?
Velcis Ribeiro said:
but in Windows 8 you need to MANUALLY install the drivers.
Click to expand...
Click to collapse
can you please tell us the process? thanks
hi
how to install this ADB drivers into arc??
heyy
how to install ADB into my arc?
question
Nice.
But I have a question (before:I come from germany,sry for my english :/).
Work Fastboot only on USB 2.0 ?When i connect my phone on the front of my PC (USB 1.0) then dont work,but when i try to connect on the rear side from my pc (USB 2.0) then it works.
Again sry for my english
Thanks for the nice package.
Sent from my Xperia Arc using XDA
Actually have been useful
thanks:d
masud7827 said:
can you please tell us the process? thanks
Click to expand...
Click to collapse
Pull up the Windows 8 Main Screen and type, System Configuration, or right-click at Computer. Go at Devices, found you Unrecognized device, right-click on it and Update... "" Than put manually installs... and select the folder.
eksen said:
Do not do this Linux Mint ?
Click to expand...
Click to collapse
idk, because i downloaded Windows FlashBoot, but i can make to you a pack for linux if you want.
doomsleed said:
how to install this ADB drivers into arc??
Click to expand...
Click to collapse
Drivers installs only at computer. You cant install THIS drivers in arc, only FOR arc. Arc drivers are named by .so or ko
xXMyKeyXx said:
Nice.
But I have a question (before:I come from germany,sry for my english :/).
Work Fastboot only on USB 2.0 ?When i connect my phone on the front of my PC (USB 1.0) then dont work,but when i try to connect on the rear side from my pc (USB 2.0) then it works.
Again sry for my english
Click to expand...
Click to collapse
I think USB 1.0 didn't have power to power on the arc cable. Idk so much with hardware, sorry.
THANKS FOR ALL GREETED MY POST.
Hi,
I'm trying to install these drivers on Windows 8 Release preview but I get an error "The third party inf does not contain digital signature information".
Any ideas?
EDIT: Never mind, just disabled signature checking Thanks for the upload!
Can u please let me know too how to doable the signature checking in win 8 ??? Please
Thanks
thank .. so good
thx
Windows 7 process help?
What's the difference with gordon's gate drivers package ?
(Just for my information)
PAVNEET101 said:
Can u please let me know too how to doable the signature checking in win 8 ??? Please
Thanks
Click to expand...
Click to collapse
As a new security measure in Windows 8, unsigned drivers are automatically blocked.
Happily, there’s a way round this problem too. If you go to the Advanced Startup app in Windows 8, you can choose to reboot the computer with Advanced Startup options enabled. You’ll then be given the opportunity to boot into various troubleshooting modes, including Safe Mode, Debugging Mode and the snappily-named “Disable Driver Signature Enforcement” mode.
Thanks.
ive been looking for this everywhere thank u.
Thanks, your are the first link returned by google when search "adb for windows download". :good:
ireun said:
As a new security measure in Windows 8, unsigned drivers are automatically blocked.
Happily, there’s a way round this problem too. If you go to the Advanced Startup app in Windows 8, you can choose to reboot the computer with Advanced Startup options enabled. You’ll then be given the opportunity to boot into various troubleshooting modes, including Safe Mode, Debugging Mode and the snappily-named “Disable Driver Signature Enforcement” mode.
Click to expand...
Click to collapse
It's not new as its present in Windows 7 64.
Sent from my CM9'd Arc
The MTP fix is ONLY for the STOCK ROM and handles the case
USB debugging disabled - MTP working
USB debugging enabled - MTP not recognized
If you cannot get MTP working at all, I suggest you
uninstall your current device drivers
using device manager/devmgmt.msc or Nirsoft USBDeview
you may want to
set devmgr_show_nonpresent_devices=1
prior to starting devmgmt.msc and
view hidden devices within devmgmt.msc
REBOOT
reinstall
The ADB fix is for getting ADB to work while in Recovery (tested on stock and twrp).
Google USB device drivers can be found here:
Driver info/download - http://developer.android.com/sdk/win-usb.html
Direct download - https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
Nirsoft USBDeview can be found here:
http://www.nirsoft.net/utils/usb_devices_view.html
use this to remove old driver assignments, sort by date and choose Nexus 7 entries
====
MTP mode (with USB debugging enabled)
I got tired of having to disable USB debugging to get the MTP device recognized.
This happens because the USB ID for the MTP device changes when USB debugging is turned on and isn't recognized by windows anymore. The particular problem is the compatible IDs list from the tablet is not advertising USB\MS_COMP_MTP when USB debugging is enabled and windows doesn't know to use the MTP drivers.
I created the following driver .inf file to fix the problem so you can have usb debugging enabled and still have MTP working.
I only tested it on Windows XP.
This ONLY fixes the problem where MTP works with USB debugging DISABLED, but stops working when you have USB debugging ENABLED.
If you can't get MTP working under any circumstance, you have some other problem. Try
double checking
Settings->Storage->3 dots->USB computer connection->Media device (MTP) is enabled
removing your drivers using Nirsoft USBDeview and rebooting
When you turn on USB debugging and windows asks for an MTP driver, just provide the following and it should install the driver hooks and start recognizing the MTP device from that point on.
Let me know if there are any issues and I'll try to address.
mtp_driver.zip is for USB debugging enabled and stock ROM
INFO: this same method of fixing the unrecognized IDs might not work for custom ROMs. I have forced the MTP USB ID for a custom ROM to be recognized and it does so successfully, but when the windows MTP driver tries to initialized the device, it fails. This indicates there may be additional issues with the MTP support on the custom ROM side.
====
ADB support (within Recovery)
I wanted to get adb working in TWRP and adb sideload working in stock recovery but adb wasn't recognizing the device.
Here we have the same problem as above. The USB IDs for the ADB interface change when you are running Recovery and are no longer recognized by the driver. You'll notice that when you are running TWRP you will see an unknown device called "flo". This is actually the ADB USB interfaced but windows doesn't know that.
I created a simple fix for this problem. Just download the official Google USB/ADB drivers from above. Then download android_winusb.inf.zip from the attachment. Unzip the Google drivers and replace the android_winusb.inf file in the Google drivers with the one in the attachment.
android_winusb.inf.zip - unzip this file to get android_winusb.inf. Replace the file of the same name in the Google USB drivers with the one in this zip file
If you feel replacing a file is too complicated, the following attached file has all the changes done for you. Just unzip to get the adb_driver folder, right-click on the "flo" device, choose install drivers, and point the driver install to the adb_driver folder
adb_driver.zip - if you want everything already done for you, this file includes the driver inf and the driver so you don't need to replace anything. This will work for adb within both Android and Recovery.
platform_tools.zip - this is adb 1.0.31 that supports RSA identification introduced in Android 4.2.2
====
Wow or strange should be more of the reply. I have done this before but it never worked. Thanks for the help. For anyone else needing help here is what I did. First opened the Nexus Tool Kit, then Full Driver Installation Guide, launched USBDeview, then - In particular look for devices with Vendor ID - "18d1" or... "04e8" - Simply right click these devices, and select the option to: - "Uninstall Selected Devices", final step unplugged the device and plugged it back in and it worked. Also MTP enabled USB Debug unchecked. Thanks again...
-AkWingnut
sfhub said:
This fix is ONLY for the STOCK ROM and handles the case
USB debugging disabled - MTP working
USB debugging enabled - MTP not recognized
If you cannot get MTP working at all, I suggest you uninstall your current device drivers (using device manager/devmgmt.msc) and reinstall.
Google USB device drivers can be found here:
Driver info/download - http://developer.android.com/sdk/win-usb.html
Direct download - https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
====
I got tired of having to disable USB debugging to get the MTP device recognized.
This happens because the USB ID for the MTP device changes when USB debugging is turned on and isn't recognized by windows anymore. The particular problem is the compatible IDs list from the tablet is not advertising USB\MS_COMP_MTP when USB debugging is enabled and windows doesn't know to use the MTP drivers.
I created the following driver .inf file to fix the problem so you can have usb debugging enabled and still have MTP working.
I only tested it on Windows XP.
This ONLY fixes the problem where MTP works with USB debugging DISABLED, but stops working when you have USB debugging ENABLED.
If you can't get MTP working under any circumstance, you have some other problem.
When you turn on USB debugging and windows asks for an MTP driver, just provide the following and it should install the driver hooks and start recognizing the MTP device from that point on.
Let me know if there are any issues and I'll try to address.
mtp_driver.zip is for USB debugging enabled and stock ROM
EDIT: I removed the following file since it appears the issue with MTP on Paranoid is on the ROM side. The USB IDs were different and the driver inf I provided was able to get the windows side to recognize the MTP device and associate the MTP drivers, but when the MTP driver tried to initialize the MTP device, it wasn't responding properly.
mtp_driver_ubdebug_paranoid.zip (experimental) is for USB debugging enabled Paranoid ROM
If you need it just let me know.
Click to expand...
Click to collapse
There is a easier way if your running Windows 8 go into device manager while the nexus 7 is plugged in it show Google adb interface something like that so click on it and find hardware updates then from there hit manual update it give youa search option and another just pick manual it show the adb one or mtp select the one for mtp and you should be okay I will post pictures later on so it makes it easier to understand my instructions
Sent from my Nexus 7 using xda app-developers app
dakunclear said:
There is a easier way if your running Windows 8 go into device manager while the nexus 7 is plugged in it show Google adb interface something like that so click on it and find hardware updates then from there hit manual update it give youa search option and another just pick manual it show the adb one or mtp select the one for mtp and you should be okay I will post pictures later on so it makes it easier to understand my instructions
Click to expand...
Click to collapse
Not sure if this is particular to newer versions of windows or you have installed some previous drivers which allow MTP to show up when you do the manual driver install but for winxp even though it has the MTP driver on the system it won't give you the option to use it when you click on Android phone/devices, Portable devices, or Imaging devices categories under the manual driver install option. It just says no compatible drivers.
I'm a little suprised if your win8 install is showing MTP as a compatible driver, why it didn't just auto-install this from the beginning w/o user intervention?
The problem some folks are encountering (at least on older windows) is that since the tablet no longer advertises USB\MS_COMP_MTP in the compatible ID list, windows doesn't know what type of device this is, thus it doesn't provide you with any device drivers to use.
Added support for ADB within Recovery (tested on stock and TWRP)
Wow!
Welcome back! Hope we held down the fort well enough while you've been away!
Sent from my SPH-L900 using Tapatalk 2
Thanks, been a while. Haven't been around to look at the fort yet. Have new toy to play with.
sfhub said:
Thanks, been a while. Haven't been around to look at the fort yet. Have new toy to play with.
Click to expand...
Click to collapse
Welcome back! It's good to see you deving again!
Stop by the Pub some time. There are plenty there that would love to say "Hi!" to you.
Bugging up my phone, so you don't have to!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Need help? [email protected] on GTalk or by Email
TrayLunch said:
Welcome back! It's good to see you deving again!
Stop by the Pub some time. There are plenty there that would love to say "Hi!" to you.
Bugging up my phone, so you don't have to!
Need help? [email protected] on GTalk or by Email
Click to expand...
Click to collapse
Say hi, pass him a round, and thank him for his work
Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
Great to see your work again SFhub! You've been missed.
Sent from my GT-I9505G using Tapatalk 4
notianag hovels
My New nexus 7 was connected to PC(windows7), USB debugging enabled:
I can see files from the PC.
But adb can't reach Nexus..
D:\>adb version
Android Debug Bridge version 1.0.29
D:\>adb devices
List of devices attached
while I connect my Galaxy SIII to PC, adb works:
D:\>adb devices
List of devices attached
cc05905f device
Anyone have any clue what happen to the Nexus7?
molo88 said:
My New nexus 7 was connected to PC(windows7), USB debugging enabled:
I can see files from the PC.
But adb can't reach Nexus..
D:\>adb version
Android Debug Bridge version 1.0.29
D:\>adb devices
List of devices attached
while I connect my Galaxy SIII to PC, adb works:
D:\>adb devices
List of devices attached
cc05905f device
Anyone have any clue what happen to the Nexus7?
Click to expand...
Click to collapse
You need adb versions 1.0.31 or greater. Earlier versions do not support the RSA identification introduced in android 4.2.2
I added platform-tools.zip to the first post which contains the adb version you need so you don't need to do large downloads.
thanks
work flawless
thank you very much
Worked perfectly with CleanRom 1.6
Many Thanks !!
shortyboy said:
Disable debugging in developer options or gotto this thread
http://forum.xda-developers.com/showthread.php?t=2391236
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Myster said:
Worked perfectly with CleanRom 1.6
Many Thanks !!
Click to expand...
Click to collapse
Just wondering how u did that? http://forum.xda-developers.com/showthread.php?t=2447839
I honestly do not know ...
I use an Outlook sync application called Android Sync ( http://www.android-sync.com ) which comes with the option to install universal android drivers and device specific drivers so maybe a driver from that package in combination with this mtp fix worked
debbuging mode
Hi,
im new to xda and this was the most similar topic to my issue with MTP i could find, so sorry if i'm posting it in wrong one.
Im having the opposite problem. Its not like i cant live with that, since i can move my files freely as long as i enable usb debbuging. But still, its bothering me.
I can connect my Nexus 7 only with debbuging mode enabled. When i disable usb debbuging, win7 wont recognize my nexus as MTP device (PTP works). I can see Nexus 7 in device manager as "other device" but windows isnt able to install drivers correctly.
I tried to fix it by uninstalling the old nexus drivers (both manually and with usbdeview) but after a reboot im having the same issue.
When i try to update the drivers manually, it wont let me use the drivers distributed by google and asus support.
Anyone had the same issue?
Thanks and sorry for my English
Similar problem. Driver was installed and working. USB debugging on and only PTP modus gave me access in Windows. MTP never works. After reboot no connection possible at all. Only for adb in fastboot modus connection was possible. Deinstalling, reinstalling do not fix the problem. Reimaging Windows solves the problem till I reboot Windows...
Thank you so much for the information!
I was trying to sideload kitkat when my computer stop recognizing my nexus in recover! Your modified ini did the trick!
Hi! This doesn't work in windows 8.1 pro 64 bit. I get this:
I tried two different downloads with the same result so the hash mismatch is not because corrupt files. I'm clueless.
Correction: the modified ini doesn't work, nor the adb driver or the original driver.
FIXED: You have to boot windows with driver signature enforcement disabled. This is something that got implemented in windows 8. The issue is that the driver isn't signed and in windows 8 you can't install unsigned drivers unless you do this advanced bootup.
Kind of frustrating, I can't seem to get my computer to recognize the Nexus 7. I'm running Windows 7 64bit. I do have the Android SDK installed with 4.3 updated to the latest already. Can't imagine what could be triggering this... hmmm
Use the SDK manager to download the Google USB drivers. Head to device manager on your windows, update the driver for the nexus 7 which has an exclamation mark, and select the android SDK folder to install the drivers.
Hope it works for you.. That solved it for me.
Sent from my Nexus 7 using xda app-developers app
You can get latest drivers here:
Description/Download
http://developer.android.com/sdk/win-usb.html
Direct download
https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
will this drivers works under win8 (64)?
They should.
meine12 said:
will this drivers works under win8 (64)?
Click to expand...
Click to collapse
It works PnP on my Win8-64
Sent from my Nexus 7 using xda premium
sWirL said:
Use the SDK manager to download the Google USB drivers. Head to device manager on your windows, update the driver for the nexus 7 which has an exclamation mark, and select the android SDK folder to install the drivers.
Hope it works for you.. That solved it for me.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
sfhub said:
You can get latest drivers here:
Description/Download
http://developer.android.com/sdk/win-usb.html
Direct download
https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
Click to expand...
Click to collapse
Hmmm unfortunately still nothing. When I browse either the usb_driver folder or my SDK folder (with the Google USB drivers), I still get a "Windows was unable to install your Nexus 7, Windows could not find driver software for your device." message.
So I've been scratching my head over this one. I tried USB debugging mode, reinstalling the drivers, etc. Basically with USB debugging and the SDK drivers, I can finally get something installed, I see the Android Composite ADB Interface, but MTP is still eluding me. So PTP works fine now, but MTP is so damn annoying...
Once I disable USB debugging, I'm back to square one, its no longer MTP that has the ! sign in device manager, but instead, Nexus 7 again. Searching the SDK folder yields nothing and not even PTP works once USB debugging is gone.
PharaohsVizier said:
So I've been scratching my head over this one. I tried USB debugging mode, reinstalling the drivers, etc. Basically with USB debugging and the SDK drivers, I can finally get something installed, I see the Android Composite ADB Interface, but MTP is still eluding me. So PTP works fine now, but MTP is so damn annoying...
Once I disable USB debugging, I'm back to square one, its no longer MTP that has the ! sign in device manager, but instead, Nexus 7 again. Searching the SDK folder yields nothing and not even PTP works once USB debugging is gone.
Click to expand...
Click to collapse
I created the attached MTP driver inf to see if it would address your issue.
If it works let me know which OS version you are running. I think you mentioned windows 7 64-bit, but sometimes people switch machines in the efforts of trying to get things working.
You can install by telling the driver install not to search and to look for the driver in the path you downloaded and EXTRACTED this zip file.
The other way to install is to right click on the ? question mark entry in devmgmt.msc and go to the tab with the update driver option.
sfhub said:
I created the attached MTP driver inf to see if it would address your issue.
If it works let me know which OS version you are running. I think you mentioned windows 7 64-bit, but sometimes people switch machines in the efforts of trying to get things working.
You can install by telling the driver install not to search and to look for the driver in the path you downloaded and EXTRACTED this zip file.
The other way to install is to right click on the ? question mark entry in devmgmt.msc and go to the tab with the update driver option.
Click to expand...
Click to collapse
Thank you! That worked fantastic, still running Windows 7 64-bit. Can I ask what you did to get this working?
EDIT: This works fine for USB Debugging Mode, but when I turn that off, the Nexus 7 will try and install this MTP driver and get a "this device cannot start" error (on Windows). Although I'm more than happy with this solution, just info for anyone browsing this thread later on.
PharaohsVizier said:
Thank you! That worked fantastic, still running Windows 7 64-bit. Can I ask what you did to get this working?
EDIT: This works fine for USB Debugging Mode, but when I turn that off, the Nexus 7 will try and install this MTP driver and get a "this device cannot start" error (on Windows). Although I'm more than happy with this solution, just info for anyone browsing this thread later on.
Click to expand...
Click to collapse
If you want, you can try the version in this thread:
http://forum.xda-developers.com/showthread.php?t=2391236
This driver inf only affects MTP under USB debugging and will defer to windows for MTP when USB debugging is turned off.
You'll need to go to devmgmt.msc and Portable Devices, find Nexus 7, right-click, find the option to uninstall drivers, choose that, righ-click on Nexus 7, remove device, reboot.
Then specify the new path for the driver install (the one from that thread is mtp_driver, instead of mtp_driver_all in this thread)
Also you may want to post your experiences on that thread so people can find it in the future.
Yep I can confirm this one works as well. Awesome!
PharaohsVizier said:
Yep I can confirm this one works as well. Awesome!
Click to expand...
Click to collapse
Do you still have the issue where it says device could not be started when you turn off usb debugging?
Not sure if I'm having the same problem or just similar.
With usb debugging mode enabled, the tablet appears as Nexus 7 with no drivers found.
Without usb debugging mode, the Nexus 7 doesn't appear at all, not even under "other devices" or as a .USB composite device.
First tried installing Google USB Driver Rev. 8 from the SDK manager, with no luck.
Trying to manually install the extracted WPDMTPNX.INF driver with "Include subfolders" checked gives "Windows was unable to install your Nexus 7" as a result.
ROM: ParanoidAndroid 3.93
Kernel version 3.4.0-g365a6e0
msilby said:
Trying to manually install the extracted WPDMTPNX.INF driver with "Include subfolders" checked gives "Windows was unable to install your Nexus 7" as a result.
Click to expand...
Click to collapse
I sent you a PM.
msilby said:
With usb debugging mode enabled, the tablet appears as Nexus 7 with no drivers found.
...
ROM: ParanoidAndroid 3.93
Kernel version 3.4.0-g365a6e0
Click to expand...
Click to collapse
I attached a modified driver inf for your setup in the referenced post. See if that works for you.
mtp_driver_usbdebug_paranoid.zip
http://forum.xda-developers.com/showthread.php?p=44253804#post44253804
I believe your USB IDs are different from stock because of the ROM you are running.
I don't think it will fix your problem of not seeing the device properly with usb debugging disabled (I think that is possibly a rom issue), but it should theoretically get your device visible with usb debugging enabled.
Right-click on Nexus 7 in start menu->run->devmgmt.msc and choose the tab that allows you to update drivers and specify a folder where you unzip'd the zip file.
sfhub said:
Do you still have the issue where it says device could not be started when you turn off usb debugging?
Click to expand...
Click to collapse
Nope, it works fantastic!
when i put the phone on my laptop its not showing, i picked storage or photo but its not showing any folder, nothing in my pc. Windows 10
It was working for about 5 min then it stoped again
Sorry if its been asked loads
Cheers guys
Drivers. Check different ports. Restart computer and phone. Make sure usb debugging is on. Basically troubleshoot.
Still not working, my nexus 6 works fine....
Is there a driver just for this phone or do you mean adb ? I just use the google universal drivers.
Can you link me to any other pages that might help please
Thanks
only works when i enable development mode
did you install Google Android SDK? i suggest install that, which wil solve most driver issues
Sorry my bad english.
I install OnePlus USB Drivers Setup/and USB Development, ADB Installer v1.4.3, Minimal ADB and Fastboot v1.2
Open OEM, USB debugging, Update Windows and follow medhod in (youtube) watch?v=3_HyIvVTTlM.
but is slove MTP not working
Image
https://imgur.com/a/lOZrt
https://imgur.com/a/iHoiy
asdasd888 said:
Sorry my bad english.
I install OnePlus USB Drivers Setup/and USB Development, ADB Installer v1.4.3, Minimal ADB and Fastboot v1.2
Open OEM, USB debugging, Update Windows and follow medhod in (youtube) watch?v=3_HyIvVTTlM.
but is slove MTP not working
Image
https://imgur.com/a/lOZrt
https://imgur.com/a/iHoiy
Click to expand...
Click to collapse
did you get it working ?
best to delete the driver that it has seen and then replug it back in, make sure it uses the correct one, otherwise nkthjtwill work.
there's a few walk throghs on XDA and the web.
1. Disable driver signature
2. Install Oneplus usb drivers
It won't work unless you have windows media player installed on your os which I guess is not there since it is "N " version of windows instead of standard.
idelnon said:
1. Disable driver signature
2. Install Oneplus usb drivers
Click to expand...
Click to collapse
not working
asdasd888 said:
not working
Click to expand...
Click to collapse
It doesnt work because Windows N has no media feature pack needed for MTP to work.
Download the windows 10 media feature pack and it will work.
All the above isnt completely true, just completely delete the driver for your found device, then install the driver as you've got from the web.
It'll install and be recognised, then just change from charging to MTP then it'll see the new driver, from that point you'll be in business, your interaction will make the difference.