Hi all,
I am trying to connect my Nexus 4 device to my computer via USB. I am currently running Ubuntu 12.10 with the latest Android SDK installed.
The problem is that I can't seem to properly connect the Nexus 4 so that I can see the device in the devices list of adb (using ./adb devices).
An entry to the USB rules list has already been added, which is this one:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee5", MODE="0666"
The file is named "99-nexus4.rules" and properly chmodded.
The output of lsusb is:
Code:
Bus 002 Device 012: ID 18d1:4ee5 Google Inc.
I have already tried to restart the adb server several times, but with no success. Starting the server as root didn't help either. I choose to mount the phone as MTP device on the phone itself.
Currently I am lost about what the problem is in this case. I would love to hear some feedback from you guys.
Thanks in advance!
Is adb enabled on your phone ?
Did you restart udev or rebooted ?
btw, saw this and work allot better than standard 12.10 mtp
http://www.webupd8.org/2013/01/upgrade-to-gvfs-with-mtp-support-in.html
lvandam said:
Hi all,
I am trying to connect my Nexus 4 device to my computer via USB. I am currently running Ubuntu 12.10 with the latest Android SDK installed.
The problem is that I can't seem to properly connect the Nexus 4 so that I can see the device in the devices list of adb (using ./adb devices).
An entry to the USB rules list has already been added, which is this one:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee5", MODE="0666"
The file is named "99-nexus4.rules" and properly chmodded.
The output of lsusb is:
Code:
Bus 002 Device 012: ID 18d1:4ee5 Google Inc.
I have already tried to restart the adb server several times, but with no success. Starting the server as root didn't help either. I choose to mount the phone as MTP device on the phone itself.
Currently I am lost about what the problem is in this case. I would love to hear some feedback from you guys.
Thanks in advance!
Click to expand...
Click to collapse
nardusg said:
Did you restart udev or rebooted ?
Click to expand...
Click to collapse
Yes, every time after I changed something in the rules list I restarted udev and rebooted as well.
Do you have java installed properly? Here is the post I used to get adb working on Ubuntu 12.10 (its post #62 the OP was for Ubuntu11). It didn't work till I set the proper permissions as stated in the post under editing the udev rules (line in post where it shows sudo gedit /etc/udev/rules.d/99-android.rules). I did a 64-bit install and it worked perfectly. Basically what you are doing is manually entering the Nexus 4 into the list of devices as its not there by default.
http://forum.xda-developers.com/showthread.php?p=19446284
That solution worked for me! Many thanks.
Related
I am fairly new to linux so I could be missing something simple but when I type adb devices i get a blank reply. It doesn't say "no devices" or anything, it just doesn't show anything. But if I run adbwireless from my phone, i can run adb connect ip adress :5555 and connect just fine. I have also noticed that the only time ubuntu will see my phone at all is if usb debugging is off. I'm not sure if those two are related or not. any suggestions?
4nic8 said:
I am fairly new to linux so I could be missing something simple but when I type adb devices i get a blank reply. It doesn't say "no devices" or anything, it just doesn't show anything. But if I run adbwireless from my phone, i can run adb connect ip adress :5555 and connect just fine. I have also noticed that the only time ubuntu will see my phone at all is if usb debugging is off. I'm not sure if those two are related or not. any suggestions?
Click to expand...
Click to collapse
WORKS FOR EPIC 4G!!!!!
This worked for my BH2 but it may need some tweaking on the rules file to make it work, but I will double check it when I get home.
After downloading the SDK, I moved the adb to the (in my pc is like this) ~/android/tools/ folder and ran the chmod a+rwx adb command.
After this, I took the rules file (attached) and I moved it to the /etc/udev/rules.d/ folder (logged as root). After doing this, I ran the following commands:
su [then placed the password]
chmod a+x 51-android.rules
chown root:root 51-android.rules
Once done, I restarted the PC and its working 100%, I ran the lsusb command to confirm the connection of the device and then a ./adb devices an I got positive return!
Note: Attachment updated!
Thank you for the suggestion. I ran the commands as you said, using the 51-android.rules that i already had and i still get a blank response when running
Adb devices.
However, since running those commands, its mounting my sd on the desktop with or without usb ebugging. So the commands you provided did fix something, just not adb!
Sent from my SPH-D700 using XDA App
4nic8 said:
Thank you for the suggestion. I ran the commands as you said, using the 51-android.rules that i already had and i still get a blank response when running
Adb devices.
However, since running those commands, its mounting my sd on the desktop with or without usb ebugging. So the commands you provided did fix something, just not adb!
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I will tune the Rules file and test and let you know. Most of the time, when it doesn't work, its the rules file who has the problem.
4nic8 said:
Thank you for the suggestion. I ran the commands as you said, using the 51-android.rules that i already had and i still get a blank response when running
Adb devices.
However, since running those commands, its mounting my sd on the desktop with or without usb ebugging. So the commands you provided did fix something, just not adb!
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
FIXED!!!! download this file and it will work 100%!
Also, please follow my instructions above in the same order.
megabiteg said:
FIXED!!!! download this file and it will work 100%!
Also, please follow my instructions above in the same order.
Click to expand...
Click to collapse
thank you for the suggestion dude, but i think that actually took me back a step, now my sd wont mount anymore. i had a 51-android.rules file already and i deleted it. maybe i will just have to still with adbwireless =(
4nic8 said:
thank you for the suggestion dude, but i think that actually took me back a step, now my sd wont mount anymore. i had a 51-android.rules file already and i deleted it. maybe i will just have to still with adbwireless =(
Click to expand...
Click to collapse
mmmm..
I've tested this with several other friends that use Ubuntu 10.10 and it works fine for them. Are you following step by step on my OP?
Also are you on a desktop or laptop? Please note that while you have USB Debugging on the option to mount your SD card will not be prompted.
If your using a Desktop, please refrain of using front side USB ports. If you need additional help, let me know, I'll be glad to help you getting it working.
send me what the lsusb command dumps if you can, that can help me tweak the rules file for you.
Thanks! after some trial and error..the zip file in the first post worked for me!
FYI, you can just run this command instead of restarting your computer:
Code:
sudo udevadm control –reload-rules; sudo reload udev; adb kill-server; adb devices
Same problem
Hello, I have the same problem, adb don't detect my tablet. I do it from my laptop and this is the lsusb exit:
[email protected]:~$ lsusb
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 007: ID 18d1:0001 Google Inc.
Bus 001 Device 002: ID 174f:a311 Syntek 1.3MPixel Web Cam - Asus A3A, A6J, A6K, A6M, A6R, A6T, A6V, A7T, A7sv, A7U
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[email protected]:~$ adb devices
List of devices attached
[email protected]:~$
Click to expand...
Click to collapse
Is it possible that the integrated webcam generates the conflict? how can I disable it on Ubuntu 10.10?
Thanks
One thing I've noticed is that my phone will come right up (with debugging turned on) on certain usb ports but won't on others. Might be worth trying different USB ports just to see if it makes a difference.
Was this way on both my desktop and my netbook (both running Ubuntu 10.10).
Thanks flatspin, I have tried all my 4 usb ports without luck.
Solved, I forgot to put the tablet on adb mode at boot time.
Hello everyone,
So I've installed ACER's adb drivers, but when I connect the tablet to my computer it shows up as an MTP device. I've tried updating the driver and manually browsing to the driver's location, but windows says that driver is not compatible with my device? BTW: I am running a fresh install of Windows 7 64-bit.
Any tips would be appreciated.
Thanks!
I'm having the same issue. It seems like everyone else's Iconia "just worked" with adb.
I've tried installing the acer drivers. It puts a folder in my Program Files directory...but I don't see what I'm supposed to do there. There's "EUUDriverInstaller" but when I click on it nothing (seems to) happens.
When I plug the device in it uses some generic Microsoft driver to show the device contents but composite adb doesn't show up at all like it does for my Droid.
I've reboot several times on both device and laptop. I've uninstalled / reinstalled the application that made that driver directory.
I opened an application in the driver directory under the x64 folder and it opened up the windows driver installer and installed some drivers...but still no composite adb when I plug it in.
It was called "dpinst" and installed:
Linux Developer Community Net
Acer, Inc (androidusb) USB
Google, Inc (WindUSB) USB
then a couple others about a modem and ports
It is on usb debugging and I've toggled it on and off.
It's running 3.1 stock and I'm on x64 Windows 7
Both command prompt adb devices is empty under "List of devices attached" and Eclipse devices is empty.
My sdk is fully updated.
Curiously it appears Acer hides the driver if you specify Honeycomb 3.1
If you're going to be playing around with development, I highly recommend installing a Linux distribution. Android is built upon Linux, and there are quite a few development tools which just work better under it. Anyway, if you try Linux, the udev rules for the iconia are:
UBSYSTEMS=="usb", ATTRS{idVendor}=="0502", ATTRS{idProduct}=="3325", MODE="0666", OWNER="user" #ACER
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0502", ATTRS{idProduct}=="3341", MODE="0666", OWNER="user" #ACER
where you replace "user" with your username, but keep it in quotes.
apapousek said:
If you're going to be playing around with development, I highly recommend installing a Linux distribution. Android is built upon Linux, and there are quite a few development tools which just work better under it. Anyway, if you try Linux, the udev rules for the iconia are:
UBSYSTEMS=="usb", ATTRS{idVendor}=="0502", ATTRS{idProduct}=="3325", MODE="0666", OWNER="user" #ACER
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0502", ATTRS{idProduct}=="3341", MODE="0666", OWNER="user" #ACER
where you replace "user" with your username, but keep it in quotes.
Click to expand...
Click to collapse
I appreciate the suggestion, but I'd rather not install another partition just to adb connect this tablet.
Some additional differences I've noticed.
It seems like the tablet is going straight to mounting if that means anything. Connecting my Droid doesn't bring up the Autoplay menu while connecting the tablet automatically asks me how I want to access the data in the autoplay menu. It does *say* usb debugging is on, but no "ACER composite ADB interface" appears in my device manager.
Edit:
It seems like my situation is comparable to this guy in regards to the device just being treated like a flash drive. forum.xda-developers.com/showthread.php?t=734139 He says the rom was the problem...but I can't see why this stock rom should have an issue.
I had the same problem on my Windows 7 computer.
The solution is simple. Just go into Devices and Printers or whatever it's called (the one where you see the printers, cameras,...). My version of Windows is in my native language so I don't know the exact name but you'll find it. You won't see the option in Device Management so don't search there. I found the proper location by accident.
Then you'll see the Acer icon and mine had an exclamation mark on it. So I right clicked on it and updated drivers (point the new drivers to Acer driver directory that holds adb drivers). Acer has to be in USB debugging mode (option under settings).
ADB then worked for me and it was a lot less hassle that I had with using ADB on my HTC Desire.
I'm used to all the different quirks when using computers but I do agree that Linux always worked best with ADB. So far I had to think of creative ways to set ADB on my Windows computer. No Android device ever installed drivers in the same way or even worked until I messed with it a little.
I'm too on Windows 7 64bits and for the drivers I go to http://support.acer.com/us/en/product/default.aspx
If you want I have re-upload the drivers on my 4shared
Just extract and launch the setup
have a good day.
PS : Sorry for my poor English
bpivk said:
I had the same problem on my Windows 7 computer.
The solution is simple. Just go into Devices and Printers or whatever it's called (the one where you see the printers, cameras,...). My version of Windows is in my native language so I don't know the exact name but you'll find it. You won't see the option in Device Management so don't search there. I found the proper location by accident.
Then you'll see the Acer icon and mine had an exclamation mark on it. So I right clicked on it and updated drivers (point the new drivers to Acer driver directory that holds adb drivers). Acer has to be in USB debugging mode (option under settings).
ADB then worked for me and it was a lot less hassle that I had with using ADB on my HTC Desire.
I'm used to all the different quirks when using computers but I do agree that Linux always worked best with ADB. So far I had to think of creative ways to set ADB on my Windows computer. No Android device ever installed drivers in the same way or even worked until I messed with it a little.
Click to expand...
Click to collapse
I don't seem to have another icon. I have this one referring to the Iconia Tab, but when I right click on it it just treats it like a flash drive.
I can't link the picture yet (need to have 8 posts), but there is on "Acer Iconia Tab" in Devices and Printers, but there's no yellow exclaimation mark and when I right click it it just has the option to browse files, it treats it like a flash drive.
It's under "Unspecified"
EVEALEX62 said:
I'm too on Windows 7 64bits and for the drivers I go to
EDIT : [Had to remove URLS to quote]
Just extract and launch the setup
have a good day.
PS : Sorry for my poor English
Click to expand...
Click to collapse
I've downloaded those drivers, unzipping them, and ran the setup several times =/.
EDIT:
I feel like a tool, someone at stack overflow suggested I switch to a different port (not just unplugging / re-plugging it into the same one), I guess that finally told windows to reanalyze it. Should have figured it would have been something silly for such a basic problem, shame on me for keeping all my other ports full.
Thanks for the help everyone!
Sorry I have forget to say :
1) click right on the "!" and choose uninstall. (on device manager)
2) Unplugg the USB
3) Install the setup (post above)
4) replugg the USB and wait for Windows install the drivers ...
EVEALEX62 said:
Sorry I have forget to say :
1) click right on the "!" and choose uninstall. (on device manager)
2) Unplugg the USB
3) Install the setup (post above)
4) replugg the USB and wait for Windows install the drivers ...
Click to expand...
Click to collapse
That worked! Thanks.
Figured it out
Hey guys,
Thanks for all of your suggestions, but none of them worked. I ended up having to disable automatic driver installation, then went into Windows\System32\DriverStore\FileRepository and deleted the folders corresponding to the drivers that windows kept on insisting I wanted. After that everything worked great!
Hi,
Need latest adb and fastboot under linux which works for andriod 4.2.2. Whenever i tried to connect it says. I solved on windows by downloading the latest adb from xda site.
List of devices attached
0062bdd0d056b091 offline
Regards,
Lokesh
lokeshv said:
Hi,
Need latest adb and fastboot under linux which works for andriod 4.2.2. Whenever i tried to connect it says. I solved on windows by downloading the latest adb from xda site.
List of devices attached
0062bdd0d056b091 offline
Regards,
Lokesh
Click to expand...
Click to collapse
Same issue, any help would be great... the sdk says up to date.
I've attached the adb and fastboot binaries from the latest Android SDK for Linux. Also make sure you check the phone for the popup to confirm adding the PC's signature to the device's whitelist.
I assume you're using Ubuntu in which case android-tools is in the Ubuntu Repository for 12.10.
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
If you want a more update ADB and Fastboot use this ppa http://www.webupd8.org/2012/08/install-adb-and-fastboot-android-tools.html
I have the one from Ubuntu repository installed on 13.04 and it works fine with my 4.2.2 devices.
Also, like tuxdude said, make sure you have your PC whitelisted so it is able to connect via adb. New security feature in 4.2.2
Try disabling and re-enabling usb debugging while plugged in. It's the only way i got the rsa verification on osx, which before i had the offline device output message.
I had a same problem, and I found the solution.
If the adb the newest, and RSA windows doesn't appear on phone, check the .android directory (in your Home directory) ownership and permission. Mine was wrong, root was the owner.
So here's a curious issue I'm having today. I flashed Euroskank's latest Jellybro build, based on CM10.2. Clearly, I expected issues. However, I'm having the most curious problem connecting over ADB now!
Overview of my setup:
OS: Linux Mint 15 x86-64
Updated Platform Tools (ADB Version is strangely the same as it was before though: 1.0.31)
Enabled Developer Settings and ADB on Device
Code:
~ $ adb devices
List of devices attached
00310d2453155029 unauthorized
This isn't surprising. Factory settings and all. But I seem to remember previously, the authorization dialog popped up on my phone at this step. Not today.
Code:
~ $ adb shell
error: device unauthorized. Please check the confirmation dialog on your device.
This is the obvious result on that side. However, the confirmation dialog is not present at all on the device.
Anyone else have issues authorizing a computer for ADB? If you're working fine, any tips?
Do you have the USB rules for Mako set up?
CMNein said:
Do you have the USB rules for Mako set up?
Click to expand...
Click to collapse
I apologize, but may I ask you to be more verbose? Thanks for the reply, by the way.
EDIT: I should mention that I had no problems using ADB immediately before flashing the new rom. Indeed, I used ADB Pull to pull my nandroid backups onto my computer (then sadly, removed them from the device).
No worries; on Ubuntu I add the follow to /etc/udev/rules.d/99-android.rules
Code:
# Google Nexus 4 16 Gb
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee1", MODE="0666", OWNER="your-login" # MTP media (multimedia device)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee2", MODE="0666", OWNER="your-login" # MTP media with USB debug on(multimedia device)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee5", MODE="0666", OWNER="your-login" # PTP media (camera)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee6", MODE="0666", OWNER="your-login" # PTP media with USB debug on (camera)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee0", MODE="0666", OWNER="your-login" # Bootloader
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="d001", MODE="0666", OWNER="your-login" # Recovery
---------- Post added at 09:42 AM ---------- Previous post was at 09:40 AM ----------
dotvezz said:
I apologize, but may I ask you to be more verbose? Thanks for the reply, by the way.
EDIT: I should mention that I had no problems using ADB immediately before flashing the new rom. Indeed, I used ADB Pull to pull my nandroid backups onto my computer (then sadly, removed them from the device).
Click to expand...
Click to collapse
Hmmm....I'm on CM10.2 (my own compile, not Skank however). No issues with ADB on the windows side, I'll try from the Linux side later.
CMNein said:
No worries; on Ubuntu I add the follow to /etc/udev/rules.d/99-android.rules
[...]
Hmmm....I'm on CM10.2 (my own compile, not Skank however). No issues with ADB on the windows side, I'll try from the Linux side later.
Click to expand...
Click to collapse
I did not have any udev rules set up for the device before, but I did copy your sample and it unfortunately did not work. No change from before.
CMNein said:
Do you have the USB rules for Mako set up?
Click to expand...
Click to collapse
Apologies..But I am also having the same issue with ADB ..i.e. getting an error message even after updating Android SDK on my Windows 7 Laptop
List of devices followed by serial number and unauthorized.
Sometimes, my phone also gives an error message : System UI has stopped. Been struggling from the last 3 days with this. I am on 4.2.2 (MoDaCo Custom ROM) and tried to flash the OTA for 4.3 that came a few days back in UK. But was unable to flash the same as the phone gave an error message while trying to install. Hence, thought of using efrant's guide..
Any pointers would be appreciated..Else I was thinking that probably taking a backup through Titanium and reflashing stock might be the best bet?
sam_htc_touch said:
Apologies..But I am also having the same issue with ADB ..i.e. getting an error message even after updating Android SDK on my Windows 7 Laptop
List of devices followed by serial number and unauthorized.
Sometimes, my phone also gives an error message : System UI has stopped. Been struggling from the last 3 days with this. I am on 4.2.2 (MoDaCo Custom ROM) and tried to flash the OTA for 4.3 that came a few days back in UK. But was unable to flash the same as the phone gave an error message while trying to install. Hence, thought of using efrant's guide..
Any pointers would be appreciated..Else I was thinking that probably taking a backup through Titanium and reflashing stock might be the best bet?
Click to expand...
Click to collapse
No issues for me on any of my Windows machines, kind of forgot to test it on Linux
sam_htc_touch said:
Apologies..But I am also having the same issue with ADB ..i.e. getting an error message even after updating Android SDK on my Windows 7 Laptop
List of devices followed by serial number and unauthorized.
Sometimes, my phone also gives an error message : System UI has stopped. Been struggling from the last 3 days with this. I am on 4.2.2 (MoDaCo Custom ROM) and tried to flash the OTA for 4.3 that came a few days back in UK. But was unable to flash the same as the phone gave an error message while trying to install. Hence, thought of using efrant's guide..
Any pointers would be appreciated..Else I was thinking that probably taking a backup through Titanium and reflashing stock might be the best bet?
Click to expand...
Click to collapse
Update : Issue Resolved
Seems like this was an issue with ROM..I was on Jr 8 of MoDaCo 4.2.2, upgraded to Jr11 4.2.2 and am able to use ADB again now. It prompts me with that confirmation dialogue on both Unix and Windows :good:
dotvezz said:
Code:
~ $ adb shell
error: device unauthorized. Please check the confirmation dialog on your device.
This is the obvious result on that side. However, the confirmation dialog is not present at all on the device.
Click to expand...
Click to collapse
I am experiencing the same thing on my stock rom/rooted Nexus 7 running 4.3...wtf happened to this all of a sudden? It will NOT re-authorize for the life of me. I have tried all sorts of things and it will not prompt me on the device to authorize. I basically am left with a choice to return to 4.2.2 and redo my ADB authorization and then update back to 4.3 or what? Aggravating!!!!!
zimmy28 said:
I am experiencing the same thing on my stock rom/rooted Nexus 7 running 4.3...wtf happened to this all of a sudden? It will NOT re-authorize for the life of me. I have tried all sorts of things and it will not prompt me on the device to authorize. I basically am left with a choice to return to 4.2.2 and redo my ADB authorization and then update back to 4.3 or what? Aggravating!!!!!
Click to expand...
Click to collapse
Did you go into developer options and force it to deauthorize usb debugging? That worked for me.
Yes, but I already fixed it on my own by rebuilding the adb_keys file on the device by appending to that from the key files from my PC that is hooked up to it. It still will not prompt for authorization prior to that even if I did as you said. I don't get it. Something broke somewhere after I updated to 4.3 from 4.2.2. I think I should maybe start 4.3 from scratch and root from there and give that a try. Thanks anyways for the suggestion!
Sent from my Nexus 7 using Tapatalk 4
Did you check your Android SDK Manager?
After upgrading to Android 4.2.2, I saw the same message.
I solved this issue installing packages like
SDK Platform API 17 Rev. 2
Google APIs API 17 Rev. 1
under Android 4.2.2 (API 17) using Android SDK Manager.
Galaxy Nexus Android 4.2.2 + Windows 7 32bit
Thanks and regards,
Dong Kyu
J3FFTXD said:
Did you go into developer options and force it to deauthorize usb debugging? That worked for me.
Click to expand...
Click to collapse
bam!!! worked perfect lol was wondering why i was feeling like my iq was slipping and this made perfect sense
ben.nesheim said:
bam!!! worked perfect lol was wondering why i was feeling like my iq was slipping and this made perfect sense
Click to expand...
Click to collapse
Nice! Glad I could help.
Hey all,
I just wasted a few hours getting my axon 7 to connect to my pc running ArchLinux without luck.
lsusb gives me the following:
Code:
$ lsusb
Bus 002 Device 014: ID 19d2:0306 ZTE WCDMA Technologies MSM
I think I've tried just about every combination of udev rules I could find on the internet. At the moment they are:
Code:
$ cat /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTRS{idVendor}=="19d2", ATTRS{idProduct}=="0306", MODE="0666", GROUP="adbusers"
SUBSYSTEM=="usb",ATTRS{idVendor}=="19d2",ATTRS{idProduct}=="0306",SYMLINK+="android_adb", GROUP="adbusers"
My user is a member of 'adbusers' and my phone is in USB debugging mode, also the USB thing is set to MTP.
Still, adb devices gives the following:
Code:
$ adb devices
List of devices attached
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
6f7f7da7 unauthorized
The phone also never asks for confimation or anything like that.
Has anyone here encountered something similar or know what I'm missing?
Thanks in advance
unrealpowerz said:
Hey all,
I just wasted a few hours getting my axon 7 to connect to my pc running ArchLinux without luck.
lsusb gives me the following:
I think I've tried just about every combination of udev rules I could find on the internet. At the moment they are:
My user is a member of 'adbusers' and my phone is in USB debugging mode, also the USB thing is set to MTP.
Still, adb devices gives the following:
The phone also never asks for confimation or anything like that.
Has anyone here encountered something similar or know what I'm missing?
Thanks in advance
Click to expand...
Click to collapse
I had the same problem in Windows when using a custom rom. Enabling 'adb over network' solved it for me (the 'Allow USB debugging' window came up). even though it's seemingly unrelated
If that doesn't work try adb while phone is in TWRP (if you have it)
Hey fellow arch user here, (pacman ftw)
I had this same problem earlier with adb and fastboot. The solution is to run adb and fastboot commands as superuser. ie sudo fastboot ..... and sudo adb ......