How to install ADB Drivers and Fastboot mode drivers!!
So lately i've seen a thread where people are having trouble installing drivers but thanks to @xT29c for providing the drivers now we can use adb as well as fastboot mode
Credits to @xT29c
1. Downloading this: https://app.box.com/s/dy9mz30t6ejf0j03xunfxdnel1oeuqoi
2. Device Manager,
Right Click On Amazon Fire,
Properties,
Update Driver,
"Browse My Computer For Driver Software",
"Let Me Pick from a List of Device Drivers on my Computer
Have Disk
Browse to extracted files from the downloaded zip from step 1.
Next
and now ADB should find the Amazon Fire Tablet.
To install fastboot mode
1. First boot into Fastboot Mode (Volume Down + Power_
2. Connect your device
3. Do steps 1-2 except pick bootloader interface this time
Can you repost in General?
Sent from my KFFOWI using Tapatalk
does not download
......
Never mind found out how to get the drivers another way
a1yet said:
does not download
......
Never mind found out how to get the drivers another way
Click to expand...
Click to collapse
It's also available from
http://developer.android.com/sdk/win-usb.html#top
and http://forum.xda-developers.com/attachment.php?attachmentid=3527959&stc=1&d=1446439904
Vlasp said:
Can you repost in General?
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
A Moderator can move it to general, just use the report post button, that's what it's for.
sd_shadow said:
It's also available from ...
Click to expand...
Click to collapse
thanks mate
i had thought i had all the drivers till i tried to root
and figured out the drivers i was using did not install fastboot ADB drivers
your links would have made it easier. :highfive:
Awesomeslayerg said:
How to install ADB Drivers and Fastboot mode drivers!!
So lately i've seen a thread where people are having trouble installing drivers but thanks to @xT29c for providing the drivers now we can use adb as well as fastboot mode
Credits to @xT29c
1. Downloading this: https://app.box.com/s/dy9mz30t6ejf0j03xunfxdnel1oeuqoi
2. Device Manager,
Right Click On Amazon Fire,
Properties,
Update Driver,
"Browse My Computer For Driver Software",
"Let Me Pick from a List of Device Drivers on my Computer
Have Disk
Browse to extracted files from the downloaded zip from step 1.
Next
and now ADB should find the Amazon Fire Tablet.
To install fastboot mode
1. First boot into Fastboot Mode (Volume Down + Power_
2. Connect your device
3. Do steps 1-2 except pick bootloader interface this time
Click to expand...
Click to collapse
No matter what drivers I've tried, from this and various other threads, I can't get them to work on my Surface Pro 3 running Windows 10. I Click on Fire and update drivers and navigate to the location I've download and unzipped the driver file and windows says "Windows can't find driver software for your device." Any suggestions?
tjrhine said:
No matter what drivers I've tried, from this and various other threads, I can't get them to work on my Surface Pro 3 running Windows 10. I Click on Fire and update drivers and navigate to the location I've download and unzipped the driver file and windows says "Windows can't find driver software for your device." Any suggestions?
Click to expand...
Click to collapse
may need to disable driver signature enforcement
then install drivers
Sent from my KFFOWI using Tapatalk
---------- Post added at 05:57 PM ---------- Previous post was at 05:51 PM ----------
Don't worry if you see "failed to install MT65xx Preloader driver" errors every kffowi boots through that before fastboot mode.
If drivers are not selected automatically and selecting folder does not work
right click on android_winusb.inf file (latest_usb_driver_windows\usb_driver)
select install
Then manually select drivers
Open device manager Settings>Devices>Device Manager
Connect Kindle Fire
Enable USB debugging
(If Kindle is not listed as Android>Android Composite ADB interface)
select Other Devices>Fire
Right Click>Update Driver Software
Browse my computer for Driver Software
Let me pick from a list of drivers on my computer
select Android or Android Phone (or ADB Interface or Android Device)
Select Android Composite ADB interface for Stock rom or recovery/adb sideload
Select Android ADB interface for Fastboot mode
or Android Composite ADB interface
next
you may have to reboot pc
{
"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"
}
sd_shadow said:
may need to disable driver signature enforcement
then install drivers
Sent from my KFFOWI using Tapatalk
---------- Post added at 05:57 PM ---------- Previous post was at 05:51 PM ----------
Then manually select drivers
Open device manager Settings>Devices>Device Manager
Connect Kindle Fire
Enable USB debugging
(If Kindle is not listed as Android>Android Composite ADB interface)
select Other Devices>Fire
Right Click>Update Driver Software
Browse my computer for Driver Software
Let me pick from a list of drivers on my computer
select Android or Android Phone (or ADB Interface or Android Device)
Select Android Composite ADB interface
or Android Composite ADB interface
next
you may have to reboot pc
Click to expand...
Click to collapse
Thanks. That pointed me in the right direction and I finally got the drivers installed and working.
Hi, the driver are only for Windows 64bit?
In Windows 7 32bit i got an error installing driver.
Thanks
NEW: Maybe resolved.
NEW2: solved. Aaahhhh... My head!!!!!
yeah this isnt working for me. I have adb until i reboot to recovery then my device isnt listed in device manager therefore I cant adb sideload etc.
garzel14 said:
yeah this isnt working for me. I have adb until i reboot to recovery then my device isnt listed in device manager therefore I cant adb sideload etc.
Click to expand...
Click to collapse
Never mind got it. Needed to locate drivers whilst in fastboot
Sent from my KFFOWI using Tapatalk
I have to the drivers installed, adb devices just wont show the device, daemon is started and working, device manager says everything is okay, ahhhhh!!!
@ Awesomeslayerg
shiz0id said:
I have to the drivers installed, adb devices just wont show the device, daemon is started and working, device manager says everything is okay, ahhhhh!!!
@ Awesomeslayerg
Click to expand...
Click to collapse
Windows version?
tried toggling enable adb?
Windows 7 Ultimate 64bit adb is enabled in settings, adb just won't detect the device in fastboot, though adb works just fine when tablet is booted up in normal mode
Sent from my KFFOWI using Tapatalk
shiz0id said:
Windows 7 Ultimate 64bit adb is enabled in settings, adb just won't detect the device in fastboot, though adb works just fine when tablet is booted up in normal mode
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
You must use fastboot commands in fastboot mode
Sent from my KFFOWI using Tapatalk
sd_shadow said:
You must use fastboot commands in fastboot mode
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
The issue is that adb devices doesn't show the device in fastboot mode, although the device manager shows the driver as working, adb services does not.
Sent from my KFFOWI using Tapatalk
shiz0id said:
The issue is that adb devices doesn't show the device in fastboot mode, although the device manager shows the driver as working, adb services does not.
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
Code:
fastboot devices
Sent from my KFFOWI using Tapatalk
---------- Post added at 08:19 AM ---------- Previous post was at 08:17 AM ----------
http://forum.xda-developers.com/showthread.php?t=
Sent from my KFFOWI using Tapatalk
I apologize for wasting your time on something so obvious -_-
Sent from my KFFOWI using Tapatalk
Thanks for the drivers
sd_shadow said:
It's also available from
http://developer.android.com/sdk/win-usb.html#top
and http://forum.xda-developers.com/attachment.php?attachmentid=3527959&stc=1&d=1446439904
Click to expand...
Click to collapse
The other drivers were not working but I found the first link worked and then all of rootjunkie's tools worked great!
Related
OK, posted this in the Q&A section with several responses but no real answers. Figured I'd post it here before another section where it might get locked or moved.
Anyway, ADB was working fine until a few days ago. Now it says "error: device not found." Fastboot still works just fine. I've tried everything I can think of to get it working again. I've uninstalled and reinstalled the usb drivers, removed the Android SDK from my PC and reinstalled, wiped and reflashed my device, made sure Debugging is on, and tried getting ADB to work on all 4 of my PC's. All running either Windows XP or Windows 7. No dice. Can anyone help? Thanks in advance.
The other day it took me about an hour to remember to just turn on usb-debugging and plug it in to the usb drive. I kept going to the fastboot screen instead. Maybe that's your problem too?
UnderCoverLover said:
The other day it took me about an hour to remember to just turn on usb-debugging and plug it in to the usb drive. I kept going to the fastboot screen instead. Maybe that's your problem too?
Click to expand...
Click to collapse
Thanks for the reply. If you read my OP you'll see that I've made sure debugging is on. In fact, debugging is also enabled by default after a wipe and clean flash. Unfortunately my problem isn't as simple as enabling usb debugging.
Have you gone from one phone to another? When I made the switch from a tmo->att n1 I had to remove ALL drivers before installing them again in order for my phone to work.
Perhaps try removing ALL drivers and starting fresh?
In Envrionmental Variables, create a System variable:
variable name: devmgr_show_nonpresent_devices
variable value: devmgr_show_nonpresent_devices
With your phone not plugged into your pc, go to device manager and under the View menu, select "show hidden devices".
Remove everything under ADB. Remove anything in unknown devices that says Nexus1 or Android, or Google. Remove the Composite Devices under USB (they will be added back upon reboot if the system uses them) as well as the Mass Storage Devices.
Reboot your system. Plug your phone in and update/install your drivers for your phone.
I used both the drivers from the sdk and from http://forum.xda-developers.com/showthread.php?t=613217 to have fastboot and adb functional.
Good luck!
deprecate said:
Have you gone from one phone to another? When I made the switch from a tmo->att n1 I had to remove ALL drivers before installing them again in order for my phone to work.
Perhaps try removing ALL drivers and starting fresh?
In Envrionmental Variables, create a System variable:
variable name: devmgr_show_nonpresent_devices
variable value: devmgr_show_nonpresent_devices
With your phone not plugged into your pc, go to device manager and under the View menu, select "show hidden devices".
Remove everything under ADB. Remove anything in unknown devices that says Nexus1 or Android, or Google. Remove the Composite Devices under USB (they will be added back upon reboot if the system uses them) as well as the Mass Storage Devices.
Reboot your system. Plug your phone in and update/install your drivers for your phone.
I used both the drivers from the sdk and from http://forum.xda-developers.com/showthread.php?t=613217 to have fastboot and adb functional.
Good luck!
Click to expand...
Click to collapse
Thanks for the response. I'll give this a shot when I get home. FYI, I didn't change devices. Same Nexus One I've had for the past month. Just one question: When you say,
"In Envrionmental Variables, create a System variable:
variable name: devmgr_show_nonpresent_devices
variable value: devmgr_show_nonpresent_devices"
I don't know what this means. Where can I access this? Thanks!
Just a thought but are you remembering to boot up the phone as normal?
As in not into fastboot, etc.
This stumped me for a few hours.
I kept trying to "adb" while the phone was in fastboot or recovery.
Sorry if I'm teaching you to suck eggs.
markouk said:
Just a thought but are you remembering to boot up the phone as normal?
As in not into fastboot, etc.
This stumped me for a few hours.
I kept trying to "adb" while the phone was in fastboot or recovery.
Sorry if I'm teaching you to suck eggs.
Click to expand...
Click to collapse
Yeah, I've had the phone booted up normally. Thanks though.
{
"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"
}
MaximReapage said:
Click to expand...
Click to collapse
Thanks a lot.
deprecate said:
Have you gone from one phone to another? When I made the switch from a tmo->att n1 I had to remove ALL drivers before installing them again in order for my phone to work.
Perhaps try removing ALL drivers and starting fresh?
In Envrionmental Variables, create a System variable:
variable name: devmgr_show_nonpresent_devices
variable value: devmgr_show_nonpresent_devices
With your phone not plugged into your pc, go to device manager and under the View menu, select "show hidden devices".
Remove everything under ADB. Remove anything in unknown devices that says Nexus1 or Android, or Google. Remove the Composite Devices under USB (they will be added back upon reboot if the system uses them) as well as the Mass Storage Devices.
Reboot your system. Plug your phone in and update/install your drivers for your phone.
I used both the drivers from the sdk and from http://forum.xda-developers.com/showthread.php?t=613217 to have fastboot and adb functional.
Good luck!
Click to expand...
Click to collapse
Followed all of these directions, reinstalled the driver, and I still can't connect via adb. Still getting "error: device not found." Help!
Part Four said:
Followed all of these directions, reinstalled the driver, and I still can't connect via adb. Still getting "error: device not found." Help!
Click to expand...
Click to collapse
Try to download the latest Android SDK and have it installed again. Also download the USB drivers within that package...
myn1 said:
Try to download the latest Android SDK and have it installed again. Also download the USB drivers within that package...
Click to expand...
Click to collapse
Done and done, days ago. Still no dice. This is ridiculous.
Still having problems. Tried everything I can think of, and everything suggested to me by the XDA community. I don't know if this will help any of you guys help me, but when I type "adb devices" into a command prompt, it returns:
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
And then shows nothing. So effing frustrating! EVERY computer I have (I actually have tried it on 6 different laptops and PCs) returns the same error and cannot find my Nexus One. WTF happened!? HELP!
Part Four said:
WTF happened!? HELP!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=613217
pvillasuso said:
http://forum.xda-developers.com/showthread.php?t=613217
Click to expand...
Click to collapse
I'm sure you're trying to be helpful but, if you've read through this thread, you'd know that I've already done all of that. OBVIOUSLY, I've done all of that because, like I said, ADB STOPPED working. In order for it to stop, it must have, at some point, worked just fine. And it did. It worked perfectly until recently. So, yes, I've installed all the damn drivers I need. But, no, it's still not working. It's infuriating.
debugging mode os on? did you open adb, delete all htc drivers then reinstall them from the sdk. not just install them but delete and then reinstall.
also once in bootloader your good, some instructions say go into hboot, not for me, just right in bootloader, not hboot.
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
temperbad said:
debugging mode os on? did you open adb, delete all htc drivers then reinstall them from the sdk. not just install them but delete and then reinstall.
Click to expand...
Click to collapse
Yes. *Sigh*
Do you see this device ( pic ) @ device manager :
If you do , there is no reason for adb commands under DOS prompt for not workig well ... really weird
temperbad said:
also once in bootloader your good, some instructions say go into hboot, not for me, just right in bootloader, not hboot.
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
What do you mean, I'm "good?"
!!!THIS IS NOT A ROOTING GUIDE!!!
This pack contains everything you need to connect and use your nexus s on your pc
Will work on XP, Vista, 7
!!!HOWEVER 7 HAS THE BEST SUCCESS!!!
included:
* Fastboot
* ADB
* USB Drivers (32bit and 64bit)
Links:
SDK:
http://www.fileserve.com/file/RZqMfeC (sdk, fastboot, adb)
Mirror:
http://hotfile.com/dl/92897052/df7338b/SDK.rar.html
Direct Link - No wait, ads, popups:
http://mazodude.comze.com/ -down atm (have to reup)
DRIVERS:
http://www.fileserve.com/file/5bgRBX5 (PDAnet x86 and x64 which are the fastboot drivers plus android sdk drivers)
Mirror:
http://hotfile.com/dl/92897696/7ae5290/drivers.rar.html
Direct Link - No wait, ads, popups:
http://mazodude.comze.com/ -down atm (have to reup)
To be able to install drivers you have to have your phone booted into fastboot and connected via usb (Thanks to mmas0n)
How to force drivers to install:
Thanks to gravis86
WARNING: SELECTING THE WRONG DRIVER TO A DEVICE MAY BREAK THINGS...
1. Control Panel > Administrative Tools > Computer Management >Device Manager
2a. NS Right-Click "Android 1.0", and click "Update Driver Software..."
2b. NS4G Right-Click "Nexus s", and click "Update Driver Software..."
3. Click "Browse my computer for driver software"
4. Click "Let me pick from a list of device drivers on my computer"
5. Click "Have Disk..."
6. Browse to folder containing the driver, then click OK
7. It will show a list of drivers contained in that folder, select the appropriate one, and click next.
8. It might tell you the driver is unsigned / not verified to work / for the wrong device, etc. As long as you are sure it is the correct driver, then install it. Remember, you are smarter than Windows.
How to install ADB and Fastboot:
1. download and place in the root of your C:\ drive
2. extract here (not into a sub folder)
3. now open up control panel
4. find system
5. goto advanced settings
6. goto environmental variables
7. in the box that says "system variables" scroll down to find a variable "Path"
8. highlight it
9. click edit
10. add this to the end
;C:\android\tools
Click to expand...
Click to collapse
yes the ; is needed
11. click ok
Now when you open cmd (command prompt) you can use "adb" or "fastboot" anywhere with out locating the folder first
You should be able to do this:
{
"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"
}
If I have helped you please hit the thanks button
I have followed the directions to the letter and when I type fastboot devices it just goes back to command prompt. I tried typing fastboot oem unlock and it just said waiting on device. Adb devices typed produces "list of devices attached" I boot the phone into fastboot mode and and the usb is plugged in but I keep getting the same results. Am I preparing the phone incorrectly?The adb worked with my Vibrant but the fastboot failed there as well. I would greatly appreciate any and all help you may offer. As I am sure you can tell I am another one of those ignorant nubies.LOL
have you installed the usb drivers?
you will have to force them to install
mazodude said:
have you installed the usb drivers?
you will have to force them to install
Click to expand...
Click to collapse
Yes I have. adb works with my Vibrant but fastboot does not and neither one works with the Nexus s. I have read and reread and followed directions but nothing seems to work. Should I be looking to do something on the phone other than booting into fastboot mode? The Nexus S shows fastboot mode at the top of the screen and I have assumed that I just use the computer from there. On my Vibrant booting into recovery does not show anything about fastboot. I really do appreciate your help I am trying very hard to learn quickly so I can be of some help instead of a burden
I don't know how to force them to install. I went in an opened the folder and I assume they were installed. I do have usb debugging enabled
Edit Just copied usb drivers to C:\android and c:\android/tools and still the same results. I have done everything I can think of but i guess I am not getting the drivers installed properly.
to force them, go into control panel-> administrator tools->computer management
then goto device manager in the sidebar.
I cant remember what the device is called but you should know when you find it.
right click and hit update drivers.
hit browse for drivers and find the drivers in C:\android\google-usb_driver
Note: phone has to be in fastboot to be able to install the drivers
edit: I forgot the drivers opps
link:
http://www.fileserve.com/file/ZM9hbvH
edit: this video might help
http://theunlockr.com/2010/12/17/how-to-root-the-samsung-nexus-s/
I just downloaded the drivers and placed them in C:\android and then went into device manager and hit update drivers and then browse for drivers and it said no drivers found. I was in C:\android/google-usb drivers.
have a look in the post above i just posted a link to a vid
edit: are you using 64-bit?
no 32 bit I will look for the video. Thanks so much for your kind and patient help!!!
I think there is a trick in the video to get it to see the device in fastboot
edit: there are some drivers here
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
there is no video but I did read the directions and I believe I have done all that they state. Should my PC say installing drivers when I plug my phone in? It did and said one driver failed to install.
yea.
If you don't see a video (at the top) disable ad blocking
also the driver that failed try to force it (using previous method)
If anybody could help that would be great, then I will add it to the first post
Followed this guide and unlocked and rooted my friends Nexus S.
http://theunlockr.com/2010/12/17/how-to-root-the-samsung-nexus-s/
@shaolinmastr well that's good to hear
I still have no success installing the drivers. Are you sure that the drivers were in the last zip file? I have gone over and over it for the last 6 hours and am at the same place I started. NO adb and no fastboot on the Nexus S and adb working on Vibrant.but no fastboot . I guess it is time to take the Nexus S back and get a refund. It is not worth the lack of results with so much effort. Thanks for you help.
Save yourselfs the hassle and just install PDAnet and you should get the drivers to work.
I was having this same problem and used pdanet to get the correct nexus s drivers. You can dload pdanet to your PC and just plug your phone in via USB andfollow the directions.
So tmello56, pdanet worked for you?
If so I will extract the drivers and add them to the first post
WARNING: SELECTING THE WRONG DRIVER TO A DEVICE MAY BREAK THINGS...
Sometimes Windows needs to be forced to use a driver that we know works, but Windows thinks doesn't. This is similar to what mazodude posted, but is just a few steps further. To do this:
1. Control Panel > Administrative Tools > Computer Management >Device Manager
2. Right-Click "Unknown Device" or whatever it's called, and click "Update Driver Software..."
3. Click "Browse my computer for driver software"
4. Click "Let me pick from a list of device drivers on my computer"
5. Click "Have Disk..."
6. Browse to folder containing the driver, then click OK
7. It will show a list of drivers contained in that folder, select the appropriate one, and click next.
8. It might tell you the driver is unsigned / not verified to work / for the wrong device, etc. As long as you are sure it is the correct driver, then install it. Remember, you are smarter than Windows.
9. WIN!!!
@gravis86, very good explination will post in 1st post
Just wanted to post my results...
I was using the correct drivers, but was installing them while the phone was booted and connected. I could use ADB and mount the file system, but could not use fastboot. I then discovered that if I installed the drivers while the phone was booted into the bootloader and connected, it detected the device differently and fastboot worked.
Now rooted + custom recovery. Awesome.
Hi, I'm currently struggling to get kfu to work on my KF2, i've got access to the root thanks to Qemu but kfu keeps saying <waiting for device>.
I've read and read and read post after post and I'm pretty sure I'm confusing myself now,
I have the Android SDK software installed including the Kindle Fire drivers, in Windows 7 Device Manager I have "Kindle Fire > Android Composite ADB Interface" (Amazon 1.2 driver) and Portable Devices > Kindle" ( Microsoft 6.7.7600) after modifying "android_winusb.inf" and "adb_usb.ini"
Nothing I do seems to put it into fastboot mode, is there something i'm missing, do I need to copy something to to the kindle??
Thanks for any help in advance
Factory USB Cable
crankyy said:
Hi, I'm currently struggling to get kfu to work on my KF2, i've got access to the root thanks to Qemu but kfu keeps saying <waiting for device>.
I've read and read and read post after post and I'm pretty sure I'm confusing myself now,
I have the Android SDK software installed including the Kindle Fire drivers, in Windows 7 Device Manager I have "Kindle Fire > Android Composite ADB Interface" (Amazon 1.2 driver) and Portable Devices > Kindle" ( Microsoft 6.7.7600) after modifying "android_winusb.inf" and "adb_usb.ini"
Nothing I do seems to put it into fastboot mode, is there something i'm missing, do I need to copy something to to the kindle??
Thanks for any help in advance
Click to expand...
Click to collapse
You need a Factory USB Cable: http://forum.xda-developers.com/showthread.php?t=1392693
There is a link to purchase one.
Is there no other way?
Sent from my GT-I9100 using xda app-developers app
Kindle Fire 2 Fastboot
crankyy said:
Is there no other way?
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Maybe. If the Kindle Fire 2 has been rooted and you have the Android SDK Installed.
Try plugging the Kindle Fire 2 to USB:
Code:
adb kill-server
adb start-server
adb devices
adb shell
su
reboot bootloader
Respond with the results.
Well that got it into fastboot but in "Device Manager" it came up as "Otter2-Prod-04" with a yellow exclamation mark.
It couldn't find the correct drivers, what should it be displayed as in device manager?
Sent from my GT-I9100 using xda app-developers app
I've just reslised fbmode will not run ftom shell it comes up with an error
Sent from my GT-I9100 using xda app-developers app
Android Composite ADB Interface
crankyy said:
Well that got it into fastboot but in "Device Manager" it came up as "Otter2-Prod-04" with a yellow exclamation mark.
It couldn't find the correct drivers, what should it be displayed as in device manager?
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
If you have installed the correct driver, you will see Android Composite ADB Interface
In the Windows Device Manager. If you need a driver, here: https://dl.dropbox.com/u/54456659/usb_driver.zip is the latest ADB Composite Driver
Offered by Android SDK Community. This driver is Universal to over 1,000
Android Devices, including the Kindle Fire 2. If you do mind me asking
what are you trying to accomplish exactly?
---------- Post added at 03:39 PM ---------- Previous post was at 03:36 PM ----------
crankyy said:
I've just reslised fbmode will not run ftom shell it comes up with an error
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Yes, I see. This is due to two problems:
1) Your ADB Composite Driver is not installed: https://dl.dropbox.com/u/54456659/usb_driver.zip
2) You do not have Root Permissions Installed on the Kindle Fire 2 http://forum.xda-developers.com/showthread.php?t=2069117
I will try the drivers you suggested but my KF2 is definatly rooted
Sent from my GT-I9100 using xda app-developers app
I've made a little progress, I tried the drivers above but the only way I could make them install was to edit the android_winusb.inf but they detected the device as a Samsung Android Phone, I tested with KFU and still no joy, so I uninstalled.
I then decided to follow the Amazon step-by-step guide (https://developer.amazon.com/sdk/fire/connect-adb.html)
This gave me the newest drivers I've had, I then ran:
Code:
adb kill-server
adb start-server
adb devices
adb shell
su
reboot bootloader
My KF2 went into Fastboot and windows installed a driver so I then saw an ADB device in Device Manager.
However KFU still will not run fbmode and I definatly have root access as I have the ability to push files to the root/change permissions in system etc.
crankyy said:
I've made a little progress, I tried the drivers above but the only way I could make them install was to edit the android_winusb.inf but they detected the device as a Samsung Android Phone, I tested with KFU and still no joy, so I uninstalled.
I then decided to follow the Amazon step-by-step guide (https://developer.amazon.com/sdk/fire/connect-adb.html)
This gave me the newest drivers I've had, I then ran:
Code:
adb kill-server
adb start-server
adb devices
adb shell
su
reboot bootloader
My KF2 went into Fastboot and windows installed a driver so I then saw an ADB device in Device Manager.
However KFU still will not run fbmode and I definatly have root access as I have the ability to push files to the root/change permissions in system etc.
Click to expand...
Click to collapse
When you say "KFU“ I hope you do not mean kindle fire utility. That program/tool is for the original kindle fire, you are lucky you have not gotten it to work. It will definitely brick your device should you successfully run it.
Sent from my KFJWI using xda premium
Follow Up
crankyy said:
I've made a little progress, I tried the drivers above but the only way I could make them install was to edit the android_winusb.inf but they detected the device as a Samsung Android Phone, I tested with KFU and still no joy, so I uninstalled.
I then decided to follow the Amazon step-by-step guide (https://developer.amazon.com/sdk/fire/connect-adb.html)
This gave me the newest drivers I've had, I then ran:
Code:
adb kill-server
adb start-server
adb devices
adb shell
su
reboot bootloader
My KF2 went into Fastboot and windows installed a driver so I then saw an ADB device in Device Manager.
However KFU still will not run fbmode and I definatly have root access as I have the ability to push files to the root/change permissions in system etc.
Click to expand...
Click to collapse
crankyy,
This is why I keep asking "what are you trying to accomplish exactly"?
If I know, then we can give you exact step-by-step, thus get you back in
business. Onemeila is correct "I hope you do not mean Kindle Fire Utility....".
This utility will Brick your Kindle Fire 2, it was designed for the Kindle Fire HD 7"
ONLY. Do not attempt to PUSH the system.img from KFU, it will permanently
Brick your Kindle. So, what are you trying to accomplish, exactly?
i'm a noob, please go easy on me. (this is my first post)
i rooted my kindle 2 days ago with qemu and bin4ry root, then installed twrp recovery. being an idiot, i wiped the system before i put the cm10 zip on the kindle, so i had no os. i tried sideloading the cm10 file onto the kindle, but my computer would not recognize the ADB, even though it had drivers installed and was working previously when the kindle was in the normal boot mode.
i read in this thread (http://forum.xda-developers.com/showthread.php?t=2117224) that you can put your kindle into fastboot mode from the twrp command prompt, so i did that, thinking that the adb drivers would work if it was in fastboot mode. they did not.
i have tried installing the adb drivers through the kfu, the android sdk, and every other way i have seen. when my kindle is plugged in, device manager calls it "otter2-prod-4" i have the fastboot with the blinking green light. i do not have a fastboot cable, though one is on its way. if i could get it to show up in adb, i could at least get it to boot into recovery and start again from there, but none of the methods i've seen are working for adb driver installation. can anyone help?
p.s. i am running windows 8 x64
Drivers ok, ADB doesn't show my KF2
Hi, my KF2 is bricked and i'm using a fastboot cable, i think the driver is ok but running the command adb devices i don't see any device connected.
{
"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"
}
ktron said:
Hi, my KF2 is bricked and i'm using a fastboot cable, i think the driver is ok but running the command adb devices i don't see any device connected.
Click to expand...
Click to collapse
You are using a "fastboot" cable, aren't you? You may want to use fastboot commands as well.
Right Driver / no devices attached
soupmagnet said:
You are using a "fastboot" cable, aren't you? You may want to use fastboot commands as well.
Click to expand...
Click to collapse
I have the right driver but i don't see any device, how can you help me?
C:\Users\Admin\Desktop\KFFirstAide100>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\Users\Admin\Desktop\KFFirstAide100>
---------- Post added at 01:17 PM ---------- Previous post was at 01:11 PM ----------
prokennexusa said:
crankyy,
This is why I keep asking "what are you trying to accomplish exactly"?
If I know, then we can give you exact step-by-step, thus get you back in
business. Onemeila is correct "I hope you do not mean Kindle Fire Utility....".
This utility will Brick your Kindle Fire 2, it was designed for the Kindle Fire HD 7"
ONLY. Do not attempt to PUSH the system.img from KFU, it will permanently
Brick your Kindle. So, what are you trying to accomplish, exactly?
Click to expand...
Click to collapse
Hi, i have the Fastboot cable, right driver but when i run the command Adb Devices i don't see my KF2, how can you help me??
C:\Users\Admin\Desktop\KFFirstAide100>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\Users\Admin\Desktop\KFFirstAide100>
ktron said:
I have the right driver but i don't see any device, how can you help me?
C:\Users\Admin\Desktop\KFFirstAide100>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\Users\Admin\Desktop\KFFirstAide100>
---------- Post added at 01:17 PM ---------- Previous post was at 01:11 PM ----------
Hi, i have the Fastboot cable, right driver but when i run the command Adb Devices i don't see my KF2, how can you help me??
C:\Users\Admin\Desktop\KFFirstAide100>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\Users\Admin\Desktop\KFFirstAide100>
Click to expand...
Click to collapse
You quoted my post. Didn't you read it as well?
adb reboot bootloader
After I run adb shell su -c "reboot bootloader" it will put KF2 into fastboot mode and try to install usb drivers again and then fastboot can't find the device. The device is visible as a otter2-prod-04 in device manager. I've got windows 7 installed. Any idea appreciate it.
Thanks
If it still says otter2 then the drivers arent installed. Try updating the drivers to the ones in my signature, I believe I added kf2 support to them.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
If it still says otter2 then the drivers arent installed. Try updating the drivers to the ones in my signature, I believe I added kf2 support to them.
Click to expand...
Click to collapse
Thanks for that, I had to install drivers again when I was in fastboot mode and yours worked great. Appreciate your reply.
stunts513 said:
If it still says otter2 then the drivers arent installed. Try updating the drivers to the ones in my signature, I believe I added kf2 support to them.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Hi, this issue sounds just like the one I am having.
I have tried your drivers with no luck.
My KF2 shows up in device manager as OTTER2-PROD-04
And:
USB\VID_1949&PID_000A&REV_0100
USB\VID_1949&PID_000A
I took your drivers and copied them over the drivers in the programme files \ amazon \ drivers folder, rebooted and reconnected but still shows up as this OTTER2
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.
hi,
im having issues installing drivers for my oneplus 2 device.
here's what i've tried doing:
iv'e tried connecting the device with usb debugging and without. without usb debugging it finds the name of the device normally.
the first thing i've done is uninstall every driver that was resembled any phone, google or usb storage driver.
and tried to install the drivers from this tool: (which i think is the source of my problem i dont know how to remove this.)
{
"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"
}
it went ok with no problems, but it didn't find my device. (when i typed adb devices)
i've uninstalled the drivers again via programs and features and usbdeview tool (this time i've found older samsung device driver from regedit and removed it also).
rebooted (as every step of driver removal and install).
i've tried again with no luck.
so i've decided to install those drivers from the android sdk but when i've tried to install it from the device manager it shows up this:
i also tried downloading samsung drivers to see if it works. i saw in one of the threads that said it's ok to use them because they were universal too. (i removed it again from the regedit when i couldn't find the drivers)
i tried to use the oneplus one toolkit's for it's universal driver i thought maybe it will work
how can i fix this? i want to start over again clean. i can't find it in USBdeview or programs and features or regedit. what am i missing?
the photos are after trying to install the drivers from the sdk tool and uninstall it back with reboots several times now
+as im seeing in other threads, it supposed to be an android device and not adb interface.
+there is nothing else in the driver selection list that resembles any device
thanks to everyone who helps!
EDIT:
whatever i did i couldn't remove this marshall driver and i really don't know how i got it there. so i decided to format my pc. start over clean.
i've downloaded the sdk tools this time and before connecting my phone to the pc (maybe the windows 10 has to do anything with installing these marshall drivers.) i have installed these drivers from the sdk, rebooted the pc and connected the device. now everything works! the cmd find my device i type "adb reboot" to make sure everything works BUT when i go into fastboot mode (in order to unlock the bootloader)
the pc doesn't recognize the device. it says "android" with an question mark icon near it, ok so i just need to install the driver like in image #1 right? so i did, and it didn't show up this android adb interface driver. instead i've found this marshall driver AGAIN! i went inside it and i'm seeing marshall drivers and google inc drivers INSIDE this marshall driver selection (like image#2)
i really don't know from where this marshall london device is coming from
although setting it up as the marshall device, it works... but it's a marshall device not my oneplus 2
this doesn't make any sense to me. i never owned marshall product, beforehand i guessed it came from the toolkits i installed but this time i went clean and there's no way it came from those toolkits.
if im unclear about anytning im willing to share my teamviewer or screenshots.
this how it looks like:
EDIT2:
Q: what if i decide to ignore that marshall device? because it seems to find the device and im able to reboot from the commands. is it ok? should i ignore the name?
Hi, I used Universal ADB drivers.
I had to manually chose the .inf file with the have disk feature to make it work.
I used the Oneplus two toolbox to install my drivers.
forums.oneplus.net/threads/oneplus-2-how-to-unlock-bootloader-install-custom-recovery-root-efs-backup-more.345478
I didn't even bother with the 15 second ADB installer.
've found the problem.
apparently the drivers name was "marshall london device". i accidently clicked on it and there was an option to choose adb interface driver (like the image #2)
EDIT:
well it worked for the first try and it stopped working.
what is marshall london device? it seems to have a bunch of drivers like clockworkmod and marshall composite adb interface
Noahsoskha said:
i've found the problem.
apparently the drivers name was "marshall london device". i accidently clicked on it and there was an option to choose adb interface driver (like the image #2)
it works now
EDIT:
well it worked for 1 try and it stopped working.
what is marshall london device? it seems to have a bunch of drivers like clockworkmod and marshall composite adb interface
Click to expand...
Click to collapse
It's an Android phone design for Marshall (the music / sound gear company).
Theberge43 said:
It's an Android phone design for Marshall (the music / sound gear company).
Click to expand...
Click to collapse
i still don't get what that driver is doing in my pc
i can't install the inf file it tells me it's not supported.
for some retarded reason the usb drivers that i downloaded from google are being installed into marshall device. i don't know why but it's the second time my pc thinks my phone is a marshall device. it works if i type adb reboot, but only once. now i have to delete this marshall thingy that i don't even know how the hell it got there...
anything?
i really need help, i think i've made this problem as clear as possible.
Bump! same problem. This all happened as soon as i installed the latest version of OS. Oxygen 2.1 . Adb worked perfectly before i flashed this new OS. now windows wont read the devices with adb drivers. it keeps saying Marshall London Device.. sigh.. anybody? i tried all the same things in this thread to fix it. I also wiped all drivers using USBDeview and reinstalled to no avail.
Noahsoskha said:
anything?
i really need help, i think i've made this problem as clear as possible.
Click to expand...
Click to collapse
azenus said:
Bump! same problem. This all happened as soon as i installed the latest version of OS. Oxygen 2.1 . Adb worked perfectly before i flashed this new OS. now windows wont read the devices with adb drivers. it keeps saying Marshall London Device.. sigh.. anybody? i tried all the same things in this thread to fix it. I also wiped all drivers using USBDeview and reinstalled to no avail.
Click to expand...
Click to collapse
before that what did it detect? the device name? or adb interface?
are you running windows 10?
i managed to ignore the name of the driver because like the third image i posted says that inside the marshall driver there is "google inc" and then that the adb driver...
so i think it's windows 10 that's causing this. but i've tried ignoring it and adb commands are working for me. i don't know whether it's safe to unlock and such but i managed to make it reboot into recovery...
I am running windows 10. I tried another computer of mine with windows 7 which worked perfectly before the new OS update. That computer as well cannot detect any ADB devices. I managed to get windows to install the proper ADB Android drivers in windows 10 and 7 now. However, whenever I load One plus 2 into Fastboot Mode windows DOES detect the device but ADB wont connect to it.
I have made sure that i am in debugging mode and that I authorized the connection when prompted. any ideas?
Thank you
Noahsoskha said:
before that what did it detect? the device name? or adb interface?
are you running windows 10?
i managed to ignore the name of the driver because like the third image i posted says that inside the marshall driver there is "google inc" and then that the adb driver...
so i think it's windows 10 that's causing this. but i've tried ignoring it and adb commands are working for me. i don't know whether it's safe to unlock and such but i managed to make it reboot into recovery...
Click to expand...
Click to collapse
---------- Post added at 04:25 PM ---------- Previous post was at 04:12 PM ----------
Figured out why adb wouldnt connect. Even though usb debugging was on and permissions granted for some reason the Developer Mode toggle was hidden again. I enabled the toggle again, turned off usb debugging mode. Turned it back on 10 seconds later and it all works now. *sigh*
useranonymous said:
I used the Oneplus two toolbox to install my drivers.
forums.oneplus.net/threads/oneplus-2-how-to-unlock-bootloader-install-custom-recovery-root-efs-backup-more.345478
I didn't even bother with the 15 second ADB installer.
Click to expand...
Click to collapse
Thanks! Worked for me too!
Hi there,
my problem is very similar to this.
Suddenly all my android devices (OPO and OP2) are recognized as marshall london devices.
adb devices finds them but I am not able to get the authorization of my PC showing up on my phones.
adb tells me the device is not authorized.
I tried resetting the usb authorization from the development options, changing usb ports, changing cables, disabling and enabling of usb debugging, mtp mode and such.
Nothing works so far. The google adb drivers show up under the marshall london category like in the first post. It all startet after I rebooted the OP2 in fastboot once.
Any ideas?
Thanks
-howgie
Update:
I was able to get rid of the marshall london entry by removing it from the registry manually. But the problem of the unauthorized device remains...
I am also getting this error, I was able to select google devices before and had adb working but after it unlocked the bootloader and rebooted the phone it wasn't detecting anything correctly, just the marshal london device and adb doesn't detect anything, also on windows 10. Will try tomorrow on my windows 7 work machine.
Same Problem! Please Help!
For some reason "Marshall London Device>Marshall London Bootloader Interface" keeps installing itself every-time I hit Scan for hardware changes, after trying to uninstall it. ADB doesn't recognize my OPT even when my phone is in fastboot mode. Running Windows10
In windows 10 use manual choose driver from list, then choose proper driver.... If you can't find it I'll post screens tomorrow
Sent from my ONE A2005 using Tapatalk
cosmicsquid said:
Same Problem! Please Help!
For some reason "Marshall London Device>Marshall London Bootloader Interface" keeps installing itself every-time I hit Scan for hardware changes, after trying to uninstall it. ADB doesn't recognize my OPT even when my phone is in fastboot mode. Running Windows10
Click to expand...
Click to collapse
I have same problems. Have someone found a solution for this?
I deleted all drivers and it says unknown USB device (Device Descriptor Request Failed). I can't get it to install Oneplus2 drivers, Android ADB or Samsung drivers and be recognised.
Again I concur and think this is a Windows 10 issue, I am not using the official cable, are others using it and having the same issue??
I used a different cable and it worked, strange as I tried one unofficial and one official and in the end my new Anker one I just purchased worked okay.
howgie said:
Hi there,
my problem is very similar to this.
Suddenly all my android devices (OPO and OP2) are recognized as marshall london devices.
adb devices finds them but I am not able to get the authorization of my PC showing up on my phones.
adb tells me the device is not authorized.
I tried resetting the usb authorization from the development options, changing usb ports, changing cables, disabling and enabling of usb debugging, mtp mode and such.
Nothing works so far. The google adb drivers show up under the marshall london category like in the first post. It all startet after I rebooted the OP2 in fastboot once.
Any ideas?
Thanks
-howgie
Update:
I was able to get rid of the marshall london entry by removing it from the registry manually. But the problem of the unauthorized device remains...
Click to expand...
Click to collapse
where is it in the registry pls? (marshall london device)