Dear Folks,
I want to access the diagnosis port on my Nexus 5x on Linux machine to run a python script to extract the UE logs. This is my first post in XDA Forum.
Do I need to have a driver if I am working on Linux environment? My phone is rooted and I can view the device shown when I ran adb devices. Does this mean that I have the correct drivers installed? I tried the command setprop sys.usb.config diag,adb and it was accepted without any errors.
Where can I find the drivers to enter into diagnostic mode on Nexus 5x on my Linux machine? After this, how can I find the correct diagnostic port on my device?
ashishkurian said:
Dear Folks,
I want to access the diagnosis port on my Nexus 5x on Linux machine to run a python script to extract the UE logs. This is my first post in XDA Forum.
Do I need to have a driver if I am working on Linux environment? My phone is rooted and I can view the device shown when I ran adb devices. Does this mean that I have the correct drivers installed? I tried the command setprop sys.usb.config diag,adb and it was accepted without any errors.
Where can I find the drivers to enter into diagnostic mode on Nexus 5x on my Linux machine? After this, how can I find the correct diagnostic port on my device?
Click to expand...
Click to collapse
You shouldn't need any drivers.
Since you're working eith USB comnectivity, you might need to make sure that you have libUSB and Udev rules properly setup for your device, but if you have adb and commands are working then you might have it all correct already.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
You shouldn't need any drivers.
Since you're working eith USB comnectivity, you might need to make sure that you have libUSB and Udev rules properly setup for your device, but if you have adb and commands are working then you might have it all correct already.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Thank you Droidriven, Can you then help me how I can identify the diagnostic port coming up on my machine?
ashishkurian said:
Thank you Droidriven, Can you then help me how I can identify the diagnostic port coming up on my machine?
Click to expand...
Click to collapse
I don't know the answer to that part, I'll try to find what you need.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Related
Ok I think im going crazy, I cant find anything about this.
Im trying to access my tab via ADB in OSX. My Evo works just fine, but I just cant find the gtablet. I see in Windows driver's ini has to be modded to include tegra device ID and vendor ID, but I dont see anything for osx and my device is not getting recognized!
Thanks for your help!
Click to expand...
Click to collapse
Ok so after some time, I just found the solution, I dont know why I need it, and some people didnt but anyway, for whoever is having the same problem as I did, this is the solution!
This steps are assuming you have ADB ready and installed!
First, open terminal (/Applications/Utilities/Terminal.app)
Run the command:
Code:
android update adb
Then you will get a adb_usb.ini file in your $HOME/.android directory. Open that file and you will have the following..
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
Add in the 4rth line the following (Device vendor code, this case NVIDIA 0x0955):
Code:
0x0955
Save the file and exit.
On terminal window type
Code:
adb kill-server
and then
Code:
adb start-server
Adb devices should now show up your device!, if by any reason you get "device offline" a re-plug fixed it!
thanks!
damn! bumping this thread, really nothing? I just want to know if anyone can ADB with osx??? Its just me? or what?! thanks
Works fine for me.
OSX is the only OS I've used (so far) to connect to my G-Tablet via ADB.
Make sure USB Debugging is on on the 'pad, and it's Plug and Play. No udev stuff like on Linux, no USB driver issues like on Winhose.
I have had troubles in the past connecting through USB hubs. I'm currently using the front connectors on a Mac Pro.
Just another trivia note on the subject:
adb remount
Works for me on ZPad, it does not on TnT Lite.
I have a hackintosh netbook, but I don't really use it in this space. Nor Windows. Sorry about that.
Linuxslate said:
Works fine for me.
OSX is the only OS I've used (so far) to connect to my G-Tablet via ADB.
Make sure USB Debugging is on on the 'pad, and it's Plug and Play. No udev stuff like on Linux, no USB driver issues like on Winhose.
I have had troubles in the past connecting through USB hubs. I'm currently using the front connectors on a Mac Pro.
Just another trivia note on the subject:
adb remount
Works for me on ZPad, it does not on TnT Lite.
Click to expand...
Click to collapse
Thanks for your reply, so...TnT Lite doesnt work for you?..mh that may be. I have not tried Zpad!
Will keep trying!
roebeet said:
I have a hackintosh netbook, but I don't really use it in this space. Nor Windows. Sorry about that.
Click to expand...
Click to collapse
no worries! Thanks for the reply man!
Fix posted on OP!
Hello,
I just got a new U11, hoping to use it to test/debug my Android apps. But I cannot get it connect to ADB reliably. I have tried everything I could, including
enabling developer options + USB debugging
adb kill-server, adb start-server and adb devices
revoking USB debugging authorizations
authorizing & remembering my PC
I've tried countless combinations of the above, but adb keeps showing unauthorized or offline. Very very occasionally adb shows "connected", but Android Studio freezes when I run my app. When I unplug, Android Studio immediately unfreezes. But again, when I plug my phone it becomes unauthorized/offline.
My other Android phone works without any issues. Is it a bug with the stock firmware?
The phone is running stock European firmware, with everything stock (including locked bootloader).
Could anyone please test/confirm this on their Linux laptop/desktop? Any fixes? Thanks a lot!
Strangely, it works on Windows. Maybe Ubuntu kernel update yesterday broke adb :crying:
I get my phone tomorrow and will update adb and try to connect. Have you tried starting the adb server as root?
sudo adb start-server
Sent from my XT1575 using Tapatalk
drzoo2 said:
I get my phone tomorrow and will update adb and try to connect. Have you tried starting the adb server as root?
sudo adb start-server
Click to expand...
Click to collapse
Yes, I did all adb commands after $ sudo -s
As it works without any problems on Windows, perhaps I should ask on a Linux forum?
For now I would use Windows until I found a solution
spolarbear said:
Yes, I did all adb commands after $ sudo -s
As it works without any problems on Windows, perhaps I should ask on a Linux forum?
For now I would use Windows until I found a solution
Click to expand...
Click to collapse
I have the same problem.
I have Debian in my computer (MSI GS40 6QE) and in my girlfriend's computer (Asus UX32V) . Same update state in both of them.
I'm unable to use adb or fastboot in my computer but it works correctly in my girlfriend's computer.
microcris said:
I have the same problem.
I have Debian in my computer (MSI GS40 6QE) and in my girlfriend's computer (Asus UX32V) . Same update state in both of them.
I'm unable to use adb or fastboot in my computer but it works correctly in my girlfriend's computer.
Click to expand...
Click to collapse
Haha, at least the issue is not unique to my phone (and laptop) :laugh:
I suspect Android SDK is most well tested on Windows, at least everything is already set up for you. But Linux allows you to run most dev tools in your HOME folder, so they don't mess things up.
Hopefully someone comes up with a fix.
My Xiaomi running LineageOS (basically AOSP) doesn't have any issue. Perhaps HTC Sense heavily modified some USB options?
spolarbear said:
Haha, at least the issue is not unique to my phone (and laptop) :laugh:
I suspect Android SDK is most well tested on Windows, at least everything is already set up for you. But Linux allows you to run most dev tools in your HOME folder, so they don't mess things up.
Hopefully someone comes up with a fix.
Click to expand...
Click to collapse
I have no problem with my M8 and my computer.
Android "is" Linux. By that, at least, tools like adb and fastboot must be very well tested under Linux :angel:.
Try to open you computer file browser and to browse or copy some files from/to your computer/phone. I'm unable to do that also.
I tried to root my phone in the same day I received it and I was getting really worried because I was unable to use fastboot (I by that I was thinking that my device was defective), even the simple "fastboot getvar all". Then I remembered to switch to another computer and voilà, everything was working perfectly.
Maybe HTC has something broken in the USB3.0 stack.
File transfer and fastboot don't work on my Ubuntu either.
spolarbear said:
File transfer and fastboot don't work on my Ubuntu either.
Click to expand...
Click to collapse
I don't know if it related with kernel (in computer side). I already tried version 4.9, 4.10 and 4.11 (the one I'm running right now).
microcris said:
I don't know if it related with kernel (in computer side). I already tried version 4.9, 4.10 and 4.11 (the one I'm running right now).
Click to expand...
Click to collapse
I tried 4.10 and 4.4, neither worked
I have same problem with Windows 10 64Bit.
All working fine here.
Sounds like udev. Have you followed the setting up usb access part of
https://source.android.com/source/initializing?
I have solved my problem. I have install Windows 10 new and now all working.
Flinny said:
All working fine here.
Sounds like udev. Have you followed the setting up usb access part of
https://source.android.com/source/initializing?
Click to expand...
Click to collapse
What Linux distro/version are you running? I've been trying to get this working with Arch and it's driving me nuts!
I run various flavours of Debian and Ubuntu across my machines and have ADB working on them all..
Flinny said:
All working fine here.
Sounds like udev. Have you followed the setting up usb access part of
https://source.android.com/source/initializing?
Click to expand...
Click to collapse
Flinny said:
I run various flavours of Debian and Ubuntu across my machines and have ADB working on them all..
Click to expand...
Click to collapse
Got it working by downloading adb straight from Google instead of using the Arch package.
I hope to open the Qualcomm diag port to modify the relevant files to support China Telecom 4g. Can the third-party ROM support it?
myyuanyu said:
I hope to open the Qualcomm diag port to modify the relevant files to support China Telecom 4g. Can the third-party ROM support it?
Click to expand...
Click to collapse
this is the development section for the pixel 2 and is reserved for ROM development and testing. any questions you may have need to be posted in the Q&A section of the pixel 2 and not here.
Sent from my Pixel 2 using Tapatalk
I am not even sure why you are spamming this forum after spamming the threads.
https://forum.xda-developers.com/showpost.php?p=78318905&postcount=98
I mentioned in my thread but you dont seem to listen or understand.
YOU DO NOT NEED A CUSTOM ROM TO ENABLE DIAG MODE. YOU NEED ROOT AND IT CAN BE DONE ON STOCK ROM.
why is it so difficult for you to google/baidu/yandex?
Code:
adb devices
adb shell
su (you will get pop up on your phone to give root authorization for ADB, authorize it)
setprop sys.usb.config diag,adb (this will open your phone diagnostic port)
Because I compiled two versions of the rom, 8.1 can open diag to modify the file but 9.0 can not open, do not understand the reasons, I would like to ask.
munchy_cool said:
I am not even sure why you are spamming this forum after spamming the threads.
https://forum.xda-developers.com/showpost.php?p=78318905&postcount=98
I mentioned in my thread but you dont seem to listen or understand.
YOU DO NOT NEED A CUSTOM ROM TO ENABLE DIAG MODE. YOU NEED ROOT AND IT CAN BE DONE ON STOCK ROM.
why is it so difficult for you to google/baidu/yandex?
Code:
adb devices
adb shell
su (you will get pop up on your phone to give root authorization for ADB, authorize it)
setprop sys.usb.config diag,adb (this will open your phone diagnostic port)
Click to expand...
Click to collapse
Hi
I try this method based on Pixel 2 with Android Pie magisk root, but failed to open diag port. Did you try it successfully? Thank you.
lycheejet said:
I am not even sure why you are spamming this forum after spamming the threads.
https://forum.xda-developers.com/showpost.php?p=78318905&postcount=98
I mentioned in my thread but you dont seem to listen or understand.
YOU DO NOT NEED A CUSTOM ROM TO ENABLE DIAG MODE. YOU NEED ROOT AND IT CAN BE DONE ON STOCK ROM.
why is it so difficult for you to google/baidu/yandex?
Hi
I try this method based on Pixel 2 with Android Pie magisk root, but failed to open diag port. Did you try it successfully? Thank you.
Click to expand...
Click to collapse
Can't open
I'm really having a hard time getting ADB drivers to work on Windows 7 so that I can connect my Android phone to my computer to run some ADB commands. I've tried three different packages; I guess the latest ADB MSI installer and another couple various packages. And I can't get any devices to show up when I type ADB devices. I need something simple if somebody can help treat me like a newbie although I have some experience with Linux and the command prompt but I really need something dead simple that will just install ADB on my computer so I can run a command on my phone. Any help would be greatly appreciated.
Wjbell said:
I'm really having a hard time getting ADB drivers to work on Windows 7 so that I can connect my Android phone to my computer to run some ADB commands. I've tried three different packages; I guess the latest ADB MSI installer and another couple various packages. And I can't get any devices to show up when I type ADB devices. I need something simple if somebody can help treat me like a newbie although I have some experience with Linux and the command prompt but I really need something dead simple that will just install ADB on my computer so I can run a command on my phone. Any help would be greatly appreciated.
Click to expand...
Click to collapse
While plenty of people know adb better than I do, I can try to help you where we need to start at the beginning I think, which is to state that there is nothing to "install" on either Android or Windows, other than the one adb.exe executable on Windows.
However, you do need to enable a few options in Android settings.
With that, you can get Windows to talk to Android over adb as shown in my screenshots below, whether over USB or completely over Wi-Fi.
My first question to you to help you is to ask a basic question.
Q: Did you turn on USB debugging in Developer options?
A: ?
Yes I have us debugging on on my Android phone. I've installed USB drivers before on an older phone to allow me to use my Android phone for an internet connection on my PC and it was pretty simple and word flawlessly.
I've been looking around for a way to enable ADB TCPIP mode without cable, and I just couldn't find something that works without rooting the device first. The Tasker trick is waaay too complicated, and I couldn't make it work on my Pixel 7 Pro.
When root is available, things look simple: run "setprop persist.adb.tcp.port 5555" or modify /system/build.prop to include a line to that effect. Assume that I go to the trouble of rooting my phone, and make the requisite change in /system/build.prop, will I be able to un-root afterward while keeping the change I made intact?
Edit: here's a wild thought: maybe I can actually tinker with the official Android factory image, hence add the requisite line to /system/build.prop in vitro, as it were, repackage the whole thing as a modified image, and then flash it onto my (unrooted) phone. Will that work? Or does the flashing process check the checksum before flashing?
Aqua1ung said:
I've been looking around for a way to enable ADB TCPIP mode without cable, and I just couldn't find something that works without rooting the device first. (...)
Click to expand...
Click to collapse
Does the simple method described in the thread below not work?
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
ze7zez said:
Does the simple method described in the thread below not work?
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
Click to expand...
Click to collapse
For one, my adb doesn't seem to know the "adb pair" command ("adb: unknown command pair"). Moreover, the IP address provided by the "Pair with device" menu is funny, along the lines of 100.xxx.xxx.xxx, hence it's not an usual 192.168.xxx.xxx. Finally, this doesn't really lend itself to scripting, as the pairing code changes all the time.
Aqua1ung said:
For one, my adb doesn't seem to know the "adb pair" command ("adb: unknown command pair"). Moreover, the IP address provided by the "Pair with device" menu is funny, along the lines of 100.xxx.xxx.xxx, hence it's not an usual 192.168.xxx.xxx. Finally, this doesn't really lend itself to scripting, as the pairing code changes all the time.
Click to expand...
Click to collapse
Are your tools up to date? What is the output of:
Code:
adb version
Code:
Android Debug Bridge version 1.0.41
Version 28.0.2-debian
Installed as /usr/lib/android-sdk/platform-tools/adb
Aqua1ung said:
Code:
Android Debug Bridge version 1.0.41
Version 28.0.2-debian
Installed as /usr/lib/android-sdk/platform-tools/adb
Click to expand...
Click to collapse
Update your tools, you should be on 33:
Code:
Android Debug Bridge version 1.0.41
Version 33.0.3-8952118
Installed as /usr/lib/android-sdk/platform-tools/adb
I have a script for that, I forgot to include it...
Edit: can't attach it for some reason, anyways, here's a link to my git: update_platform_tools
Thanks. This is what I am getting when attempting to pair:
Code:
[email protected]:~$ adb pair 100.78.124.214:32989
Enter pairing code: 521129
error: unknown host service
Aqua1ung said:
Thanks. This is what I am getting when attempting to pair:
Code:
[email protected]:~$ adb pair 100.78.124.214:32989
Enter pairing code: 521129
error: unknown host service
Click to expand...
Click to collapse
Do you have your phone and PC connected via wifi to the same router?
ze7zez said:
Do you have your phone and PC connected via wifi to the same router?
Click to expand...
Click to collapse
Same router, yes, though my PC is on a wired connection.
Aqua1ung said:
Same router, yes, though my PC is on a wired connection.
Click to expand...
Click to collapse
I checked on my Windows PC and it does not connect when the PC is connected via cable.
It works when both devices are connected via WiFi.
ze7zez said:
I checked on my Windows PC and it does not connect when the PC is connected via cable.
It works when both devices are connected via WiFi.
Click to expand...
Click to collapse
I was about to see if I could do that, lol, my box is wired as well
ze7zez said:
I checked on my Windows PC and it does not connect when the PC is connected via cable.
It works when both devices are connected via WiFi.
Click to expand...
Click to collapse
Thank you. Anyway, it may not be of much help, as this procedure needs to be repeated after each reboot, and is not scriptable. I, for one, am interested in writing a script. For now, it's easier for me to connect the phone via USB and run my script every time after reboot.
About the rooting/un-rooting questions I was asking in the OP, any opinions about those?
Aqua1ung said:
Thank you. Anyway, it may not be of much help, as this procedure needs to be repeated after each reboot, and is not scriptable. I, for one, am interested in writing a script. For now, it's easier for me to connect the phone via USB and run my script every time after reboot.
About the rooting/un-rooting questions I was asking in the OP, any opinions about those?
Click to expand...
Click to collapse
As for things you can do with root, I have nothing to offer, in fact, I am totally against it. It just causes unnecessary problems with the device.
However, you *may* be able to modify the stock rom with an Android ROM Kitchen, emphasis on the "may".
Aqua1ung said:
(...) then flash it onto my (unrooted) phone. Will that work? Or does the flashing process check the checksum before flashing?
Click to expand...
Click to collapse
So what's would the point of OTA file signatures if anyone could modify the original ROM with dangerous changes?
Aqua1ung said:
Thanks. This is what I am getting when attempting to pair:
Code:
[email protected]:~$ adb pair 100.78.124.214:32989
Enter pairing code: 521129
error: unknown host service
Click to expand...
Click to collapse
It worked fine for me after killing adb ($ adb kill-server)
Tasker and LADB app are working on my P7P perfectly, no cable required, no root - more info here.