Hello,
Is it normal that adb doesn't work in recovery mode?
My Windows (7 x64) install detects a USB device but it gives errors.
Adb works in Android, do I need special drivers for using it in CWM?
Thanks
I just upgraded my Laptop to Linux mint 17 cinnamon bu t i am not able to access my storage of my mi3 like that in windows.When i connect my mi3 to laptop only driver installation partion on mi3 appears(have attached screenshot) not the storage(In windows both appears).If you have solution please give it step by step ,i am new to linux
kaapro9 said:
I just upgraded my Laptop to Linux mint 17 cinnamon bu t i am not able to access my storage of my mi3 like that in windows.When i connect my mi3 to laptop only driver installation partion on mi3 appears(have attached screenshot) not the storage(In windows both appears).If you have solution please give it step by step ,i am new to linux
Click to expand...
Click to collapse
1) Install SDK and setup adb
simple script to setup sdk and adb on linux, tested on old version linux mint as im using Ubuntu 14.04 now http://forum.xda-developers.com/showthread.php?t=1459945
just in case the udev rules is not available on above link. http://rootzwiki.com/topic/258-udev-rules-for-any-device-no-more-starting-adb-with-sudo/
2) Add below code inside android 99rules
#Xiaomi
SUBSYSTEM==usb, SYSFS{idVendor}==2717, MODE=0368
3) Voila, u can now use mtp into linux
4) other than that, u can use ftp. It is built inside the mi file explorer and connect it using Filezilla or simply type the ftp host into web broser.
Hi guys,
my OnePlus 3t received an OTA to version 4.5.0 ( OxygenOS).
Since that day, when i connect it to PC I only see it in Device manager as "Unknown USB Device ( Device Descriptor Request Failed).
OS is win 10 x64, but i tried others also.
already reinstalled USB drivers.
Any thoughts?
- Uninstall all Oneplus related drivers (+ software)
- Restart windows
- Install Oneplus drivers and connect again
ivgenyr said:
Hi guys,
my OnePlus 3t received an OTA to version 4.5.0 ( OxygenOS).
Since that day, when i connect it to PC I only see it in Device manager as "Unknown USB Device ( Device Descriptor Request Failed).
OS is win 10 x64, but i tried others also.
already reinstalled USB drivers.
Any thoughts?
Click to expand...
Click to collapse
Fir3start3r said:
- Uninstall all Oneplus related drivers (+ software)
- Restart windows
- Install Oneplus drivers and connect again
Click to expand...
Click to collapse
Try using the tool USBDeview to uninstall/delete all USB drivers that appear to be related to Android. Reboot computer.
Install OnePlus drivers. Reboot computer.
Then connect the device and see what Windows recognizes it as.
Hello guys,
Is there anyone have nokia ADB driver for window 7 ? i have nokia 7 plus, i could not find adb driver on the internet,
thank for your help !
zenki1 said:
Hello guys,
Is there anyone have nokia ADB driver for window 7 ? i have nokia 7 plus, i could not find adb driver on the internet,
thank for your help !
Click to expand...
Click to collapse
Try here. There is a download link to ADB.
https://forum.xda-developers.com/nokia-7-plus/how-to/guide-switch-buttons-recent-apps-t3777021
i don't have Windows, but is not adb usb driver in adb release for Windows?
https://www.xda-developers.com/install-adb-windows-macos-linux
k3dar7 said:
i don't have Windows, but is not adb usb driver in adb release for Windows?
https://www.xda-developers.com/install-adb-windows-macos-linux
Click to expand...
Click to collapse
I have HiHonor suite installed on my PC for PC to recognize my Phone. I have honor 6 so I tried those drivers.
btw: you know this? when you connect Nokia 7 Plus via USB cable to PC, you see new two devices "Nokia 7 Plus" (this is MTP device for Media/Files Transfer) and "CDROM" (this is virtual CDROM with Windows drivers), if i unpack (on GNU/Linux, not try install on Windows) driver file, then inside in "inf" i see that driver is for 64bit and for 32bit XP and latter...
Follow this: https://forum.xda-developers.com/nokia-x/general/to-download-nokia-7-1-usb-drivers-t3963996
I just got hold of an xz2 for a bit of development work, and am trying to unlock the bootloader (yes, it's allowed, I've checked)
I'm connected to a usb2 port (same one I use for my mi mix 3 because that doesn't like usb3 for fastboot)
ADB works perfectly, however, fastboot lists no devices, and executing a command just causes <waiting for device> to show.
I've installed the drivers supplied by sony, though, the installation reported they installed but could not start.
I've never experienced this before, so, tell me if I'm doing something wrong.
ambitiousButRubbish said:
I just got hold of an xz2 for a bit of development work, and am trying to unlock the bootloader (yes, it's allowed, I've checked)
I'm connected to a usb2 port (same one I use for my mi mix 3 because that doesn't like usb3 for fastboot)
ADB works perfectly, however, fastboot lists no devices, and executing a command just causes <waiting for device> to show.
I've installed the drivers supplied by sony, though, the installation reported they installed but could not start.
I've never experienced this before, so, tell me if I'm doing something wrong.
Click to expand...
Click to collapse
Does it work with
Different cable
Different port
Different pc
Different OS like linux
?
If I remember correctly I had issues with windows drivers.
Tried different ports, same issue, not tried a different cable, but I know this cable works as I use it for fastboot on my mi mix 3.
I'll try Linux though, a few posts seem to say it works
ambitiousButRubbish said:
Tried different ports, same issue, not tried a different cable, but I know this cable works as I use it for fastboot on my mi mix 3.
I'll try Linux though, a few posts seem to say it works
Click to expand...
Click to collapse
I use Linux Mint Cinnamon for development
I am still happy with it
ambitiousButRubbish said:
I just got hold of an xz2 for a bit of development work, and am trying to unlock the bootloader (yes, it's allowed, I've checked)
I'm connected to a usb2 port (same one I use for my mi mix 3 because that doesn't like usb3 for fastboot)
ADB works perfectly, however, fastboot lists no devices, and executing a command just causes <waiting for device> to show.
I've installed the drivers supplied by sony, though, the installation reported they installed but could not start.
I've never experienced this before, so, tell me if I'm doing something wrong.
Click to expand...
Click to collapse
my same issue adb working but not fastboot on windows 10.
i solved using ubuntu on virtual machine. on windows i can't use fastboot but with ubuntu on oracle virtualbox all is work perfectly
yep, worked with linux, well, i just connected it to my mi mix 3, installed the adb/fastboot binaries in magisk and ran the commands from the terminal, looks like all my fastboot work is being done from another android device
ambitiousButRubbish said:
yep, worked with linux, well, i just connected it to my mi mix 3, installed the adb/fastboot binaries in magisk and ran the commands from the terminal, looks like all my fastboot work is being done from another android device
Click to expand...
Click to collapse
is it possible to install adb and fastboot from magisk and do it from another android device?
is it possible to do it with a 32 bit device? i have a galaxy note 4 as a second phone with snapdragon 805 32 bit
MartinX3 said:
I use Linux Mint Cinnamon for development
I am still happy with it
Click to expand...
Click to collapse
Arch linux only ?
Don't see why not, the binaries are just compiled for ARM, don't think they are architecture specific.
My mi mix 3 is ARMv8 (64 bit) sd845, and it worked fine, not sure about ARMv7, but as I say, I think the binaries are ARMv7 anyway.
So long as the device can host a USB connection it will work.
For anyone having problems with the,"Waiting for Device" in windows,
USB debugging enabled on the phone.
Connected to PC through USB data cable and Phone screen unlocked and File Transfers enabled.
In windows> Device Manager> Android device(or your device/phone) >ADB driver or similar > Properties> Driver> Update Driver > Browse Computer > Let me pick from a list of devices and Un-tick the show compatible devices and find one that works.
I've had to keep this general as there are quite a few variables with different phones makes/models but the problem is caused by Window's Device Mangler not getting the correct ADB driver installed/chosen and or too many varied ADB driver packages installed
HTH
First hit in google... so let me explain it again. (Yeah... fresh windows install ****ed me over... )
You need ADB/Fastboot.
Sony Drivers?: https://developer.sony.com/file/download/xperia-xz2-driver/
Google USB Drivers: https://developer.android.com/studio/run/win-usb
If you can't install it. Disable Driver signature enforcement (Hold Shift while you press the restart button with the mouse)
When ADB works but fastboot isn't recognized reboot into bootloader "ADB reboot bootloader" and then in Device Manager find the "Android!" device and manually select the Android Bootloader as driver.