Hi,
adb doesn't detect my ZUK Z1 device.
I followed all instructions and tutorials I could find. I Enabled USB debugging and OEM unlocking, added vendor ID in
Code:
~/.android/adb_usb.ini
(My Galaxy Tab 3 is listed by adb when connected, btw.)
I would first like to know that it's not a hardware / OS / driver issue.
What I find odd is that it doesn't even charge when connected to the PC. Does this indicate a more general problem? (Charging only works with a power adapter with ~2A output.)
PC is a DELL Latitude E6540 which is supposed to have 4 USB 3.0 ports.
I'm running Elementary OS which is Ubuntu 16.04 based. It seems that it's not officially supported by Dell.
The USB cable was the issue.
I replaced it and everything worked like charm.
I didn't think the cable was the problem because it still worked for charging.
Related
I just upgraded "(downgraded") to a smaller case. i was using an Asus 170m plus motherboard. Now i have an Asus z170i mobo. On the old mobo my nexus was seen with no issue, however, i did have to utilize some device manager wizardary to get adb and fastboot to work. This time around on the ITX board, i had no issues getting ADB or Fastboot to work but it will not install the required drivers for my 6p.
I have updated the drivers with Android SDK. I've even went as far as downloading Huawei drivers, MTP drivers and Intel Android Drivers. I have tried different cables. No luck. I have searched this issue and found no one with the exact issue i have. No matter what i choose, PTP or MTP it will not install. I can uninstall drivers, and switch to charging and back to MTP/PTP - it will just not install.
For whatever reason the phone shows up under MTP portable devices, as well.
This phone works on my old build and my computer at work. I am stumped.
Anyone have any ideas or has seen this before?
Issue here:
http://imgur.com/a/Cf5wq
EDIT * i think this is a USB port issue.. Not sure why. I have plugged into 2.0, 3.0 and 3.1. Just went over to another computer in the house and it worked instantly.
The issue was resolved by entering this into cmd: net localgroup Administrators local service /add
Hey all,
Has anyone been able to successfully root from a MacBook Pro 2016 with USB Type C ports? Having problem getting adb to list my Shield. This is on:
2016 Macbook Pro w/ macOS Sierra 10.12.3
WAWPI USB 3.0 A Male to A Male Cable
Apple USB-C to USB Adapter
Android Debug Bridge version 1.0.36 (Revision 84e3321d5db3-android)
System Information -> USB shows Shield but adb devices does not. I was able to connect with adb connect <IP> but not USB. I've seen various threads pointing to a possible issue with Mac USB Type C/Thunderbolt 3 ports.
Any help would be appreciated.
EDIT: adb command works with about mentioned cable and adapter. The real issue is fastboot. It constantly freezes/crashes macOS. I think my Mac was in a funky state preventing adb command from listing devices. Unfortunately, this still prevents me from performing a complete root from this macbook. I was able to complete root with another macbook with USB ports. So does anyone have a fix or workaround for fastboot other than running a VM or bootcamp?
EDIT2: In case anyone is following this thread... There's an open bug for this and a fix is in QA. New release coming.
Thanks for this post.. I was confused about what the issue was.
Hello,
It's been a while since I have been facing the problem described in the title. Only now I've managed to get some time to investigate the issue. I'm using LineageOS 15.1.
I was using Lineage 14.1 before, and I had the following issues:
USB OTG was not working
MTP, PTP (and the rest) ALSO not working
After I flashed Android 8.1, USB OTG started working, but ADB, MTP and PTP still did not work. I realized it could be a hardware problem. So I tried connecting with several different USB Cables: did not work. It is also not a driver issue, since I tested in multiple computers (with Linux and Windows);
Then, I bought a new charging board (the one that also has the phone's mic.) and exchanged the old one. That did not help at all.
I was messing around with ADB over network and I happened to make the phone get recognized - about 3 times - using the setprop command:
setprop sys.usb.config adb,mtp,ptp
The problem, after the OS (Ubuntu 16.04) managed to recognize the phone, was that as soon as I unplugged the cable and then plugged it back in, the phone stopped being recognized again. Running dmesg on my PC returned this:
[15548.910595] usb 1-2: new full-speed USB device number 12 using xhci_hcd
[15549.730614] usb 1-2: device descriptor read/64, error -71
Click to expand...
Click to collapse
I also got a device not accepting address error (on dmesg), which I forgot to copy
When I boot into the bootloader (Fastboot Mode), the dmesg output is:
Bus 001 Device 008: ID 0b05:4daf ASUSTek Computer, Inc. Transformer Pad Infinity TF700 (Fastboot)
Click to expand...
Click to collapse
I appreciate your help. Any extra information needed, please ask.
Thank you.
I have the same problem with the rom lineage-14.1 and 15.1
Hello,
I have a oneplus2 - Lineage OS 15.1 Stable (Unofficial) . For the last several months I've noticed that my phone isn't detected AT ALL in any of th multiple modes I have tried. Listing a here :
Note that the phone charges fine.
This is also not about mounting, file storage access MTP/PTP modes etc
On Ubuntu Linux :
1. Does not show up at all on firing the lsusb command. (Nothing in the device listing)
2. No devices shown on the adb devices command.
3. Needless to say device is not detected in any file transfer modes
On Windows
Does not show up as unknown device etc in devices
In Lineage under Connected Devices the USB option shows as disabled. See screenshot.
USB debugging is on
USB modes have been set to MTP/PTP
The weird thing is that if I connect a OTG cable to the phone , and run lsusb on the terminal on the phone, 2 devices show up.
However if I connect the OTG to any device like a USB drive or a PC, it does not get detected on the phone terminal lsusb command as an additional device nor does it show up for mounting in TWRP or ES explorer on the phone.
So now the question is is my USB port fried ? If so how come the OTG gets detected on the phone ?
What's the best way to determine if it is a hardware issue ? If so where with the port or on the motherboard ? And before I shifted to this OS around from Lineage OS 14.1 I had taken USB based backups .. and I doubt this is a OS issue since it's also not detected in TWRP .
Any help would be appreciated !
Parth
coolparth said:
Hello,
I have a oneplus2 - Lineage OS 15.1 Stable (Unofficial) . For the last several months I've noticed that my phone isn't detected AT ALL in any of th multiple modes I have tried. Listing a here :
Note that the phone charges fine.
This is also not about mounting, file storage access MTP/PTP modes etc
On Ubuntu Linux :
1. Does not show up at all on firing the lsusb command. (Nothing in the device listing)
2. No devices shown on the adb devices command.
3. Needless to say device is not detected in any file transfer modes
On Windows
Does not show up as unknown device etc in devices
In Lineage under Connected Devices the USB option shows as disabled. See screenshot.
USB debugging is on
USB modes have been set to MTP/PTP
The weird thing is that if I connect a OTG cable to the phone , and run lsusb on the terminal on the phone, 2 devices show up.
However if I connect the OTG to any device like a USB drive or a PC, it does not get detected on the phone terminal lsusb command as an additional device nor does it show up for mounting in TWRP or ES explorer on the phone.
So now the question is is my USB port fried ? If so how come the OTG gets detected on the phone ?
What's the best way to determine if it is a hardware issue ? If so where with the port or on the motherboard ? And before I shifted to this OS around from Lineage OS 14.1 I had taken USB based backups .. and I doubt this is a OS issue since it's also not detected in TWRP .
Any help would be appreciated !
Parth
Click to expand...
Click to collapse
Disable secure boot on your PC. Though if you have Linux I'm assuming it's already disabled but sometimes secure boot can cause certain hardware to not be detected. It should be in your UEFI settings or you can try booting a Linux live cd in legacy bios mode and see if it works
Reason for this answer: oneplus driver for op2 is outdated and oneplus never invested the money to properly sign it so certain UEFI firmwares might reject the connection
Try a different PC, I'm assuming you tried a different usb cable already. The oneplus cable in the box can go bad over time
Yes secure boot is disabled. In fact tried it also on an old Linux desktop that doesn't have secure boot ..and yes tried multiple cables that are working for other phones..
coolparth said:
Yes secure boot is disabled. In fact tried it also on an old Linux desktop that doesn't have secure boot ..and yes tried multiple cables that are working for other phones..
Click to expand...
Click to collapse
Then I'm out of ideas for now
I've read the threads about unlocking bootloader in the redmi note 7, but none of them helped.
So the main problem is whenever I connect redmi into PC, it's recognized, but when I enter Mi Unlock app (miflash_unlock-en-3.5.1128.45), the phone is showing in left-up corner "..key to shutdown" (I can't see anything before key) and it's unmounting from PC.
I tried connecting it in many moments, but the result is the same. I tried also installing drivers from xiaomi, that you can install through the app itself, but it didn't change the results.
I've installed ADB app and drivers (as shown here: https://forum.xda-developers.com/showthread.php?t=2588979) and connected my device to mi account.
As in the thread on https://forum.xda-developers.com/redmi-note-7/how-to/one-redmi-note-7-unlock-bootloader-t3890751 I tried to check via ABS if my device is listed and there is the output:
C:\adb>fastboot devices
afd9005 fastboot
C:\adb>fastboot oem device-info
...
FAILED (command write failed (Unknown error))
finished. total time: 0.005s
Click to expand...
Click to collapse
And the device goes into that mode like from mi unlock app
I'm posting below the link to the screenshots of my phone's settings, os version and things that I've read could help (I don't know how to insert photos in the post other way).https://we.tl/t-O3Z7H6AABu
I've been fighting with it for too long... Maybe someone encountered this problem and/or is able to provide the fix.
You can see help here https://forum.xda-developers.com/redmi-note-7/help/fastboot-issues-t3964100
Should to try another PC or use a 2.0 USB HUB. I also have same problem with my laptop (core i3 with USB 3.0 port) but it's OK on an older PC (without USB 3.0)
Update: Hi, I found a better way to fix this problem. I did with my Dell 14 5447 (with Intel chipset and Windows 7). I uninstalled Intel(R) USB 3.0 eXtensible Host controler in Program and Features. And then download and install a newer driver from Intel (https://downloadcenter.intel.com/do...100-Series-and-Intel-C220-C610-Chipset-Family).
gazavn said:
You can see help here https://forum.xda-developers.com/redmi-note-7/help/fastboot-issues-t3964100
Should to try another PC or use a 2.0 USB HUB. I also have same problem with my laptop (core i3 with USB 3.0 port) but it's OK on an older PC (without USB 3.0)
Click to expand...
Click to collapse
Oh I didn't try with USB 2.0. I have one in Mobo, so on few hours I'm going to tell if it fixed the issue
gazavn said:
You can see help here https://forum.xda-developers.com/redmi-note-7/help/fastboot-issues-t3964100
Should to try another PC or use a 2.0 USB HUB. I also have same problem with my laptop (core i3 with USB 3.0 port) but it's OK on an older PC (without USB 3.0)
Click to expand...
Click to collapse
On my main PC plugging into a USB 2.0 on back panel didn't work, neither on my dad's PC, that have in the front panel USB 2.0.
So I opened the whole thing now on the laptop without USB 3.0 drivers installed. I installed win7 and I didn't have option in driver selection "Android", so I installed xiaomi drivers and just plugged the phone. AND IT WORKED! Now I just have to wait 102 hours XD
I have 2 modules inside my laptop that are connected to motherboard (1st include 2.0 usb, and 2nd 3.0, both on different sides of laptop), so they're in some way separated. I don't know how it would behave if I installed the drivers, but for now I'm not checking it.
Thanks you for help, I would never come up with that fix!
Just leaving the specs if it's caused by hardware and for someone who has the same:
i5-8400
B360M pro-vdh
Probably not improtant in this case, but just in case:
GTX 1060 3GB
16GB ram ballistix sport lt
=Terys;81704493]On my main PC plugging into a USB 2.0 on back panel didn't work, neither on my dad's PC, that have in the front panel USB 2.0.
So I opened the whole thing now on the laptop without USB 3.0 drivers installed. I installed win7 and I didn't have option in driver selection "Android", so I installed xiaomi drivers and just plugged the phone. AND IT WORKED! Now I just have to wait 102 hours XD
I have 2 modules inside my laptop that are connected to motherboard (1st include 2.0 usb, and 2nd 3.0, both on different sides of laptop), so they're in some way separated. I don't know how it would behave if I installed the drivers, but for now I'm not checking it.
Thanks you for help, I would never come up with that fix!
Just leaving the specs if it's caused by hardware and for someone who has the same:
i5-8400
B360M pro-vdh
Probably not improtant in this case, but just in case:
GTX 1060 3GB
16GB ram ballistix sport lt
My pleasure.