Related
Hello everyone ... Yesterday i tried to take screensot with DDMS.bat like usually... But after launch ddms.bat and plug DHD into PC ERRORs appears.
First is adb.exe stopped working http://screenshooter.net/2759574/gjoqvjp
Second: Microsoft Visual C++ Runtime Error http://screenshooter.net/2759574/sqhiuql
third: TODO: <File description> .... http://screenshooter.net/2759574/pxrrsbs
if i connect DHD without run ddms my adb.exe is working fine i think (adb devices recognize SN of my device) but afterrun ddms adb is crashing and other errors appear :/
Log in cmd window looks like:
12:39:39 E/adb:
12:39:39 E/adb: This application has requested the Runtime to terminate it in an unusual way.
12:39:39 E/adb: Please contact the application's support team for more information.
12:39:44 W/DeviceMonitor: Failed to connect to client '4505': timeout
12:39:47 E/DeviceMonitor: Adb connection Error:
12:39:47 W/DeviceMonitor: Failed to connect to client '4795':
12:39:48 W/DeviceMonitor: Failed to connect to client '4808': Connection refused: connect
12:39:48 E/DeviceMonitor: Connection attempts: 1
12:39:48 E/DDMS: Connection refused: connect
java.net.ConnectException: Connection refused: connect
at sun.nio.ch.Net.connect(Native Method)
at sun.nio.ch.SocketChannelImpl.connect(SocketChannel Impl.java:507)
at java.nio.channels.SocketChannel.open(SocketChannel .java:146)
at com.android.ddmlib.AdbHelper.executeRemoteCommand( AdbHelper.java:367)
at com.android.ddmlib.Device.executeShellCommand(Devi ce.java:276)
at com.android.ddmuilib.SysinfoPanel.loadFromDevice(S ysinfoPanel.java:159)
at com.android.ddmuilib.SysinfoPanel.deviceSelected(S ysinfoPanel.java:126)
at com.android.ddmuilib.SelectionDependentPanel.devic eSelected(SelectionDependentPanel.java:52)
at com.android.ddms.UIThread.selectionChanged(UIThrea d.java:1666)
at com.android.ddmuilib.DevicePanel.notifyListeners(D evicePanel.java:752)
at com.android.ddmuilib.DevicePanel.notifyListeners(D evicePanel.java:740)
at com.android.ddmuilib.DevicePanel.access$1100(Devic ePanel.java:56)
at com.android.ddmuilib.DevicePanel$1.widgetSelected( DevicePanel.java:357)
at org.eclipse.swt.widgets.TypedListener.handleEvent( Unknown Source)
at org.eclipse.swt.widgets.EventTable.sendEvent(Unkno wn Source)
at org.eclipse.swt.widgets.Widget.sendEvent(Unknown Source)
at org.eclipse.swt.widgets.Display.runDeferredEvents( Unknown Source)
at org.eclipse.swt.widgets.Display.readAndDispatch(Un known Source)
at com.android.ddms.UIThread.runUI(UIThread.java:492)
at com.android.ddms.Main.main(Main.java:98)
12:39:49 W/DeviceMonitor: Failed to connect to client '4818': Connection refused: connect
12:39:49 E/Logcat: Connection refused: connect
java.net.ConnectException: Connection refused: connect
at sun.nio.ch.Net.connect(Native Method)
at sun.nio.ch.SocketChannelImpl.connect(SocketChannel Impl.java:507)
at java.nio.channels.SocketChannel.open(SocketChannel .java:146)
at com.android.ddmlib.AdbHelper.executeRemoteCommand( AdbHelper.java:367)
at com.android.ddmlib.Device.executeShellCommand(Devi ce.java:284)
at com.android.ddmuilib.logcat.LogPanel$3.run(LogPane l.java:527)
12:39:50 E/DeviceMonitor: Connection attempts: 2
12:39:50 E/EventLog: Connection refused: connect
java.net.ConnectException: Connection refused: connect
at sun.nio.ch.Net.connect(Native Method)
at sun.nio.ch.SocketChannelImpl.connect(SocketChannel Impl.java:507)
at java.nio.channels.SocketChannel.open(SocketChannel .java:146)
Click to expand...
Click to collapse
I was looking for solution everywhere ... Reinstalled JDK (Java), SDK (revision 9), .NET Framework 4, Microsoft Visual 2010 ... What else can i do?
I`m using Windows 7 Ultimate x64, and on DHD ROM: Android Revolution 2.0.9 (but it is not ROM related... i flashed stock 1.32 and the same) However ... few weeks ago ddms was working fine without any errors :/
PLEASE for ANY help.
MOD:
Sorry if in wrong seciotn but didn`t know where can i ask for it.
The new SDK has a different path to adb.exe and its DLL files, so you might want to include:
c:\android-sdk-windows\platform-tools\
to your global PATH variable.
jkoljo said:
The new SDK has a different path to adb.exe and its DLL files, so you might want to include:
c:\android-sdk-windows\platform-tools\
to your global PATH variable.
Click to expand...
Click to collapse
Thanks for reply But i`ve already added this to PATH ... Forgot to write about it.
I wrote above ADB separately works fine ... but via ddms, adb is crashing.
Try to install new HTC Sync and copy files from platform-tools to tools.. After that & adding platform-tools to PATH my DDMS started working, and still works fine. I updated my SDK to the newest version.
Normally the path to adb in PATH is c:\android-sdk-windows\tools, as you may know, so I just added platform-tools path after it.
What do you mean when U say new HTC sync? I got sync for desire HD from SD.
Sent from my Desire HD using Tapatalk
Ok found newer version of HTC Sync ... installed it ... added again PATH/ copied files from platform-tools to tools ... but still the same :/ Anybody? Any ideas? It drives me crazy :/ Wrrrrr Now i`m not sure if any operation with adb, fastboot are safe for me For example radio flashing... With errors like this i`m afraid of bricking my device during radio flash...
New HTC Sync from HTC website. And you do not need a working SDK to flash a radio, just get the radio flash package from flashing guide.
You could try to remove the whole SDK and install SDK starter package from Android website.
I'm a developer experiencing the same issue, Htc Desire HD and adb work properly outside eclipse, but with eclipse it crashes. I have too Win7 64 bit and the newest version of SDK. I think something went wrong in the last update. I'm going to install latest skd in a XP to check what happens, before trying to reinstall eclipse and the SDK on my win7 machine.
Did you add C:\android-sdk-windows\platform-tools to your global PATH variable as suggested earlier in this thread? It fixed adb for me, and I use eclipse, too.
jkoljo said:
Did you add C:\android-sdk-windows\platform-tools to your global PATH variable as suggested earlier in this thread? It fixed adb for me, and I use eclipse, too.
Click to expand...
Click to collapse
As Jkoljo has said it has fixed my problem when new SDK was released.
Putting the path to the platform-tools and ddms worked after that.
Or try: cd "C: \ your SDK directory \ tools \ ddms.bat
If ddms is in platform-tools then: cd "C: \ your SDK directory \ platform-tools \ ddms.bat
I have the same problem. My ADB and HTC sync just works fine but when I run DDMS to capture a screenshot adb always crashes. I added both directories to the path variable. My system is XP 32bit.
With the old version of the sdk I didn't had any problems at all.
Any suggestions?
Mav3ric144 said:
I have the same problem. My ADB and HTC sync just works fine but when I run DDMS to capture a screenshot adb always crashes. I added both directories to the path variable. My system is XP 32bit.
With the old version of the sdk I didn't had any problems at all.
Any suggestions?
Click to expand...
Click to collapse
I gave up Didn`t solve it It still drives me crazy :/:/ The strangest thing is that ddms was working fine few (3) weeks ago. Suddently i connected to capture a screen and? buuuu :/ didn`t work -> adb.exe error :/
I DO NOT TALK HERE ABOUT NOT WORKING ADB
My ADB is working fine until i run ddms.bat. After that adb error appears :/
Hi again,
(Yes I have added the PATH variable)
I have been working in different machines to check if it was a room (AR HD 2.0.9), system or HDH itself problem.
I installed for the first time eclipse+SDK+ADT on a XP 32 bit and I got the same problem I have in my W7 64 bit. Impossible to connect.
Then I installed eclipse+SDK+ADT on a ubuntu 10.10 32 bit and all worked fine after I realised that once I started eclipse I had to open the console with root user, kill adb server and restart the adb server again. After that I had no problem debuggin my applications on the HDH with eclipse and ddms.
So I came back to my Win 7 64 bit and I did the same procedure. Now ddms seems to connect properly with the HDHD but when I try to debug anything I got a new error:
Failed to install myapp.apk on device 'HT0BHRX00568': Unable to open sync connection!
[2011-02-08 00:15:09 - xxx] java.io.IOException: Unable to open sync connection!
[2011-02-08 00:15:09 - xxx] Launch canceled!
I think there has to be something related with the windows installation and the sdk recently update.
Anyone has any new clues??
Thanks
Same here. It's driving me crazy. The funny thing is that it does work intermittently and then just stops again. Rebooting the PC and/or the phone doesn't fix it.
Please post if you find the issue.
I gave up Didn`t found any solution for this WRRRRRR thats the worst :/ There must be a way to fix it !
I'm still trying to solve it. As a temporary solution (I hope!) I'm developing using Eclipse on Ubuntu 10.10
I'm using Windows and not going to change my OS just for ddms ... Arrrrggg it was working on windows and must work again ;(
Tapnąłem z HTC Desire HD.
DDMS error
This seems to be related to and update (either Java, Android SDK or both)
The Java library is not handling IPv6 sockets.
In Linux, sudo "echo -n 0 > /proc/sys/net/ipv6/bindv6only" will turn off the IPv6 binding.
I am not sure what the equivalent method in Windows is.
for reference: http://stackoverflow.com/questions/...ent-ddms-from-command-line-not-seeing-devices
I think Java ... Cuase i didn`t update SDK until this error occured :/
Maybe Windows or Java updater did the update and voila ...ddms suddently stopped working. Maybe someone will find solution for Win users ...
Hi, I have disabled ipv6 on win7 as you suggested and nothing changed. Maybe in August was, but right now, I don't think It's ipv6 related because Eclipse works properly on a Ubuntu 10.10 fully updated with ipv6 running.
Thanks any way
i already set up adb and the sdk
now i need help setting up udev.
can anyone please explain it to me in a way a noob can understand?
teh5abiking said:
i already set up adb and the sdk
now i need help setting up udev.
can anyone please explain it to me in a way a noob can understand?
Click to expand...
Click to collapse
Here you go.
Yeah, I tried that tutorial.
Didn't work for me.
Sent from my T-Mobile G2 using XDA App
I installed 11.04 recently and ADB seemed to work right out of the box.
Have you tried:
Code:
adb devices
I grepped the rules.d directory for 0bb4 and came up with this, in 40-usb-media-players.rules
Code:
ATTRS{idVendor}=="0bb4" , ATTRS{idProduct}=="0c94" , ENV{ID_MEDIA_PLAYER}="htc_vision"
"lsusb" returns (among other devices)
Code:
Bus 002 Device 007: ID 0bb4:0c91 High Tech Computer Corp.
Note that the product ID is different.
For 10.10, I think I had to update the udev files, but support for the vision might already be baked into 11.04. If "adb devices" returns a serial number, you're all set. If it doesn't let us know what pops up.
I found this:
http://eddieringle.com/udev-rules-for-adb-in-ubuntu-11-04-natty-narwhal/
I'm not sure what to say? I don't have the 99-android rules and adb works fine. Maybe you didn't have enough permissions to change the udev files when you installed ADB/SDK?
maybe reboot or restart udev or unplug/plug your device?
Code:
sudo service udev restart
I don't see how it didn't work. That tutorial worked for me just fine.
Sent from a Western Union telegram.
You need to reboot your computer for it to work.
Sent from my HTC Vision using XDA Premium App
Well, I did get adb to work just fine on my Acer Aspire One.
I had to mix the tutorial on the Cyanogenmod wiki with a tutorial that was for the G1/Magic/Droid/N1/i7500.
It's working great.
The one on the android dev page didn't work for me because of some deep internal stuff that was going on with my laptop. as explained by my good friend Chris who's actually a registered Android developer. I forgot exactly what it was, but it had to do with the security features of Ubuntu that collide with something that's in my laptop.
For others looking for info with adb on natty, the SYSFS is deprecated (if you are following the tutorial on the android site). You should be using ATTRS instead. Also, the rule can be 51 or 99.
Here is mine (i have an nvidia pad and an htc phone):
Code:
[email protected]:/etc/udev/rules.d$ cat 51-android.rules
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0955", MODE="0666"
And don't forget to restart udev. Unplug the device, do the command below and then plug back in. HTH.
Code:
sudo /etc/init.d/udev restart
Hi all,
I've been tinkering around trying to get mtpfs to work properly and get mtp services working in Ubuntu for my Xperia ZL (Bell C6506 4.2.2 android)
Here's where I'm at so far:
Linux can recognize the device and automatically mounts it now.
Rhythmbox can detect it, but I haven't tested sync features, but I did notice it couldn't automatically detect my music libraries. It obviously doesn't autodetect their locations and is possibly only looking for them in a certain place.
I'm also worried if I try to sync with rhythmbox, that it will erase data on the SD or worse, the internal.
Don't give me credit for any of this, I pulled all my info from various sources online, mostly from webupd8.
My steps:
Create a directory that we can mount the device to. Open up a terminal and type:
Code:
sudo mkdir /media/xperiazl
I never had to use chmod, but if you wanna make sure permissions are right, do a quick google search on how to set permissions with chmod. I think it's more important if you have multiple users on the one computer, but I'm the only user on my PC.
Next, install go-mtpfs through the ppa provided by webupd8
go-mtpfs is a Ddebian package that manages the filesystem used by the mtp protocols. It should work on any Debian distro, but I only work in Ubuntu 13.04 so I haven't tested anything else.
Code:
sudo add-apt-repository ppa:webupd8team/unstable
sudo apt-get update
sudo apt-get install go-mtpfs
But go-mtpfs isn't enough on it's own, because it doesn't autmoatically detect the Xperia ZL (it is supposed to detect nexus devices, etc. automatically though)
Next you need to edit a script file in the udev folders, to tell linux how to recognize the phone; or theoretically any other MTP devices.
If you want to know about udev and the files you're editing, go to /etc/udev/rules.d/ and look for the readme document inside.
Code:
sudo gedit /etc/udev/rules.d/51-android.rules
I use the code below to set the parameters for recognizing the Xperia ZL, specifically while it's in MTP, with USB debugging enabled.
With debugging disabled you have a different product ID (labelled "ID_VENDOR_ID" in the code below). You could just duplicate the code and have two entries then, one for usb debugging on, one for when it's off.
FOR NON C6506 / Xperia ZL device users:
When looking at the below code, notice the idVendor tag and the idProduct tag in the first unhashed line of code. These numbers are specific for the Xperia ZL (possibly specific to the C6506, I never looked into it). If you're setting up auto-mount for another device, use the following function in the terminal:
lsusb
lsusb gives you a readout of all the usb devices attached to your computer (that linux can detect). The readout looks kind of like this:
Bus 002 Device 055: ID 0fce:5189 Sony Ericsson Mobile Communications AB
That's the readout at this time for my Xperia ZL. The 0fce is meant to be handled by idVendor or ID_VENDOR. The 5189 is meant to be handled by idProduct or ID_VENDOR_ID. Again, remember that your idProduct or ID_VENDOR_ID is different when usb debugging is off / on.
Ok, we're almost there! C6506 users, just copy the code below and replace YOUR_USERNAME with... well, your username.
All other users must replace the product ID and Vendor ID with their own device's values.
Code:
# Sony XperiaZL idProduct="0189" for usb debug off, and idProduct="5189" for usb debug on
SUBSYSTEM=="usb", SYSFS{idVendor}=="0fce", ATTR{idProduct}=="5189", MODE="0777" #MTP media, USB debug on
# Xperia ZL MTP mode under JB 4.2+ : automatic mount & unmount whel plugged (usb debug on & off)
SUBSYSTEM=="usb", ENV{ID_VENDOR}=="0fce", ENV{ID_VENDOR_ID}=="5189", ACTION=="add", RUN+="/usr/bin/sudo -b -u YOUR_USERNAME /usr/bin/go-mtpfs -allow-other=true /media/xperia"
You will often run into errors and other random problems if you try to mount with the screen off (or at lockscreen). If you're gonna do lots of file transfers, I suggest jumping into your phone's developer options and turning on "stay awake" so the screen stays on while it's charging. That'll prevent loss of permissions in the middle of a file sync.
If there are any linux experts, could you help point out any faults in my code? I'm pretty sure its all good actually and that all the rough edges are linux issues with mtp, since it's not supported as well as it could be.
Anyways, thanks for reading, I know I'm not the best at teaching this but hopefully this helps someone else out who's been struggling with linux and MTP protocol.
EasyAI said:
Hi all,
I've been tinkering around trying to get mtpfs to work properly and get mtp services working in Ubuntu for my Xperia ZL (Bell C6506 4.2.2 android)
Here's where I'm at so far:
Linux can recognize the device and automatically mounts it now.
Rhythmbox can detect it, but I haven't tested sync features, but I did notice it couldn't automatically detect my music libraries. It obviously doesn't autodetect their locations and is possibly only looking for them in a certain place.
I'm also worried if I try to sync with rhythmbox, that it will erase data on the SD or worse, the internal.
Don't give me credit for any of this, I pulled all my info from various sources online, mostly from webupd8.
My steps:
Create a directory that we can mount the device to. Open up a terminal and type:
Code:
sudo mkdir /media/xperiazl
I never had to use chmod, but if you wanna make sure permissions are right, do a quick google search on how to set permissions with chmod. I think it's more important if you have multiple users on the one computer, but I'm the only user on my PC.
Next, install go-mtpfs through the ppa provided by webupd8
go-mtpfs is a Ddebian package that manages the filesystem used by the mtp protocols. It should work on any Debian distro, but I only work in Ubuntu 13.04 so I haven't tested anything else.
Code:
sudo add-apt-repository ppa:webupd8team/unstable
sudo apt-get update
sudo apt-get install go-mtpfs
But go-mtpfs isn't enough on it's own, because it doesn't autmoatically detect the Xperia ZL (it is supposed to detect nexus devices, etc. automatically though)
Next you need to edit a script file in the udev folders, to tell linux how to recognize the phone; or theoretically any other MTP devices.
If you want to know about udev and the files you're editing, go to /etc/udev/rules.d/ and look for the readme document inside.
Code:
sudo gedit /etc/udev/rules.d/51-android.rules
I use the code below to set the parameters for recognizing the Xperia ZL, specifically while it's in MTP, with USB debugging enabled.
With debugging disabled you have a different product ID (labelled "ID_VENDOR_ID" in the code below). You could just duplicate the code and have two entries then, one for usb debugging on, one for when it's off.
FOR NON C6506 / Xperia ZL device users:
When looking at the below code, notice the idVendor tag and the idProduct tag in the first unhashed line of code. These numbers are specific for the Xperia ZL (possibly specific to the C6506, I never looked into it). If you're setting up auto-mount for another device, use the following function in the terminal:
lsusb
lsusb gives you a readout of all the usb devices attached to your computer (that linux can detect). The readout looks kind of like this:
Bus 002 Device 055: ID 0fce:5189 Sony Ericsson Mobile Communications AB
That's the readout at this time for my Xperia ZL. The 0fce is meant to be handled by idVendor or ID_VENDOR. The 5189 is meant to be handled by idProduct or ID_VENDOR_ID. Again, remember that your idProduct or ID_VENDOR_ID is different when usb debugging is off / on.
Ok, we're almost there! C6506 users, just copy the code below and replace YOUR_USERNAME with... well, your username.
All other users must replace the product ID and Vendor ID with their own device's values.
Code:
# Sony XperiaZL idProduct="0189" for usb debug off, and idProduct="5189" for usb debug on
SUBSYSTEM=="usb", SYSFS{idVendor}=="0fce", ATTR{idProduct}=="5189", MODE="0777" #MTP media, USB debug on
# Xperia ZL MTP mode under JB 4.2+ : automatic mount & unmount whel plugged (usb debug on & off)
SUBSYSTEM=="usb", ENV{ID_VENDOR}=="0fce", ENV{ID_VENDOR_ID}=="5189", ACTION=="add", RUN+="/usr/bin/sudo -b -u YOUR_USERNAME /usr/bin/go-mtpfs -allow-other=true /media/xperia"
You will often run into errors and other random problems if you try to mount with the screen off (or at lockscreen). If you're gonna do lots of file transfers, I suggest jumping into your phone's developer options and turning on "stay awake" so the screen stays on while it's charging. That'll prevent loss of permissions in the middle of a file sync.
If there are any linux experts, could you help point out any faults in my code? I'm pretty sure its all good actually and that all the rough edges are linux issues with mtp, since it's not supported as well as it could be.
Anyways, thanks for reading, I know I'm not the best at teaching this but hopefully this helps someone else out who's been struggling with linux and MTP protocol.
Click to expand...
Click to collapse
Hey i did everything as you said, but still cannot mount my ZL C 6502...is there anything else that i could do?
I'm trying to get my system back to where it was before I lost everything. My files, notes, tools, etc. were gone but I've managed to get about 80% of it up again. In order to get my computer to talk to my VK815, I'm pretty sure I need a good udev rule. I think there's also a modeswitch script that needs to run when it's plugged in but that info was lost in the disaster. I have the linux development setup back to where I can compile AOSP and I get the tools like adb and fastboot as compilation products, but can't get the VK815 and computer to talk to each other. Any and all help is most welcome.
Thanks,
Jim
I guess there's some good news here. I was able to reconstruct two udev rules; one to modeswitch (which may or may not be necessary) and the other to symlink to ttyUSB0. With the phone in the normal (not download) mode, dmesg shows it initially as idProduct 6292 (where it attempts to feed the Micro$oft drivers) and then it changes to 6293 and symlinks ttyUSB0. After this completes, 'adb devices' shows a blank list. I'm in the developer mode on the tablet with USB Debugging enabled and the Build Version is LRX22G.
Ideas anyone?
edit: Be sure to turn on USB tethering in Wireless Networks -> More
Turns out that the usb_modeswitch rule wasn't needed. Here's the rule I put into /lib/udev/rules.d/51-vk815.rules
# LG G-Pad 8.3
SUBSYSTEM=="usb", ATTR{idVendor}=="1004", MODE="0666", GROUP="plugdev"
After adding this rule, restart udev the way your version of linux wants you to.
Plug in the USB cable and wait for the VK815 to finish loading the Windoze drivers and change idProduct to 6293.
Now, adb devices "should" show you the device ID. It did on mine.
This can easily be made harder than it should be.
Still can't get the VK815 to become a ttyUSB device when it's in the download mode. Tried adding SYMLINK+="ttyUSB%n" to the udev rule without success. Gotta have this to squirt and image.
When this is done and working, I plan on making a step-by-step for future reference.
Jim
I've tried everything to my knowledge including doing multiple google searches but I can't figure this out. I recently switched to Linux Mint 19 from Ubuntu 18.10 and I'm having issues getting my device to properly work using ADB. I have created the proper rules (to my knowledge) in /etc/udev/rules.d/51-android.rules and also added vendor id in ~/.android/adb_usb.ini. The main issue I seem to be having here is that after I revoke USB debugging authorizations from developer settings, I do not get the pop up on my device to allow authorization. I've tried restarts of my phone and PC but it still shows as unauthorized when typing adb devices. Any help would be appreciated. Also, just noticed I was missing some spaces in 51-android.rules I fixed but that did not fix it.
Triscuit said:
I've tried everything to my knowledge including doing multiple google searches but I can't figure this out. I recently switched to Linux Mint 19 from Ubuntu 18.10 and I'm having issues getting my device to properly work using ADB. I have created the proper rules (to my knowledge) in /etc/udev/rules.d/51-android.rules and also added vendor id in ~/.android/adb_usb.ini. The main issue I seem to be having here is that after I revoke USB debugging authorizations from developer settings, I do not get the pop up on my device to allow authorization. I've tried restarts of my phone and PC but it still shows as unauthorized when typing adb devices. Any help would be appreciated. Also, just noticed I was missing some spaces in 51-android.rules I fixed but that did not fix it.
Click to expand...
Click to collapse
Try this
sudo apt-get install android-tools-adb
sudo apt-get install android-tools-fastboot
If after that you type adb devices and you don't see your serial number type
echo 0x2717 >> ~/.android/adb_usb.ini
Just something I googled...
Tulsadiver said:
Try this
sudo apt-get install android-tools-adb
sudo apt-get install android-tools-fastboot
If after that you type adb devices and you don't see your serial number type
echo 0x2717 >> ~/.android/adb_usb.ini
Just something I googled...
Click to expand...
Click to collapse
The first two commands are to install adb and fastboot, which I've done. The third command is to add a new product id in adb_usb.ini which I got "permission denied" so I entered it manually for ****s and giggles but it didn't help. Thank you though!
I was finally able to get the device to authorize, I did a few things but I'm not sure which one corrected the problem, first. I deleted the adbkey file from /home/.android folder, I also changed permissions of the folder to rw-rw-rw and finally I hit "Revoke USB debugging authorizations" under development settings WHILE the phone was plugged into the computer. Every other time I had done it after unplugging the device. Not sure which one worked but it did, now I can get back to flashing again!
Sent from my Pixel 2 XL using XDA Labs
I had to go back in time to find this.. but this was how I originally was able to get things going in Ubuntu... It's very dated but I'm sure some of this may work?
https://forum.xda-developers.com/showpost.php?p=39144762&postcount=2
jbarcus81 said:
I had to go back in time to find this.. but this was how I originally was able to get things going in Ubuntu... It's very dated but I'm sure some of this may work?
https://forum.xda-developers.com/showpost.php?p=39144762&postcount=2
Click to expand...
Click to collapse
Yep I honestly think my problem was that I was unplugging my device before revoking authorizations..... Silly me haha
Sent from my Pixel 2 XL using XDA Labs