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.
Related
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.
I'm currently getting some strange errors while trying to control my N4 over adb.
http://prntscr.com/1km24i
On Ubuntu I get "device unauthorized" and on Windows 8 I get "device offline".
Same thing happens over USB.
Any idea?
PS: I'm currently on 4.2.2. I where on 4.3 yesterday but installed 4.2.2 again after some strange errors.
HashWorks said:
I'm currently getting some strange errors while trying to control my N4 over adb.
http://prntscr.com/1km24i
On Ubuntu I get "device unauthorized" and on Windows 8 I get "device offline".
Same thing happens over USB.
Any idea?
PS: I'm currently on 4.2.2. I where on 4.3 yesterday but installed 4.2.2 again after some strange errors.
Click to expand...
Click to collapse
As the message have stated, you need to allow the adb access on your phone.
You need to first connect the phone to your PC with USB cables, then the authorization message will pop out on the screen. Tick remember your choice, then allow it.
ksilver89 said:
As the message have stated, you need to allow the adb access on your phone.
You need to first connect the phone to your PC with USB cables, then the authorization message will pop out on the screen. Tick remember your choice, then allow it.
Click to expand...
Click to collapse
I'm not getting any message.
Maybe because I already authorized my pc before. A few weeks ago adb worked just fine.
HashWorks said:
I'm not getting any message.
Maybe because I already authorized my pc before. A few weeks ago adb worked just fine.
Click to expand...
Click to collapse
Remove /data/misc/adb/adb_key, reboot your phone and try connect again. The message should come up.
Perfect, worked. Thanks!
I just got my phone back from LG (the mainboard "Fried"). I have the new update pushed to the phone. I have to re-root the phone now as its basically a new phone.
I am getting the Device offline as well message in ADB. As I don't have root, how can I fix this error? I can't navigate to that particular directory. I had no authotization message show up on my computer when I plugged the phone in for the first time... so not sure how to get past this...
usafle said:
I just got my phone back from LG (the mainboard "Fried"). I have the new update pushed to the phone. I have to re-root the phone now as its basically a new phone.
I am getting the Device offline as well message in ADB. As I don't have root, how can I fix this error? I can't navigate to that particular directory. I had no authotization message show up on my computer when I plugged the phone in for the first time... so not sure how to get past this...
Click to expand...
Click to collapse
This shouldn't be happening on new phone, because the key won't be created if you haven't authorized it.
Can you check your adb version? Try updating it with android sdk manager.
I am going to try and re-download the ADB SDK. I think it's an issue with whatever version I downloaded. I've tried to run the ADB Manager.exe and nothing happens. Currently flying to London so it will have to wait until I get back. Nice of LG to fix my phone and they didn't charge me a dime. Although I did lose everything.
Hello,
I'm having the same problem "Please check the confirmation dialog on your device", but there is no such dialog on the device.
Things I tried and DID NOT SOLVE:
1) Remove /data/misc/adb/* - Failed, there was nothing there (full wipe before flash a new rom)
2) Try different ROMs - Failed, tried AOKP Milestone 1 and 2 and CM10. Dialog never showed up.
3) Try different usb cable OR usb port - Failed, adb is recognized, but no confirmation dialog on the device (device shows as unauthorized)
4) Removed all drivers and installed them again - Failed, same problem;
5) Updated android-sdk (or full delete and reinstall [remembering to adb kill-server]) - Failed, problem continues even with platform-tools up-to-date.
6) Removed all folder C:\Users\Myself\.android - Failed, it was never recreated;
7) Tried to connect via adb over wifi, device is found but unauthorized persists;
Things that gave me some clues:
1) Reboot to recovery mode allowed me to use ADB without any authorization (only while in recovery);
2) Recovery sideload works without any problem;
3) HOWEVER, when connecting to another computer (Windows XP, fresh install on a virtual machine), dialog appears and adb works!
The scenario:
1) Devices tried: Galaxy Nexus / Galaxy S3 I9300
2) ROMs tried: AOKP (4.2.2) / CM10 (4.2.2)
3) Windows 7 x64
The problem is on the computer side, that's a fact. However, I would like to SOLVE it without having to reformat my computer, or change my OS.
Where to start?
Thanks!
legalbrr2 said:
Hello,
I'm having the same problem "Please check the confirmation dialog on your device", but there is no such dialog on the device.
Things I tried and DID NOT SOLVE:
1) Remove /data/misc/adb/* - Failed, there was nothing there (full wipe before flash a new rom)
2) Try different ROMs - Failed, tried AOKP Milestone 1 and 2 and CM10. Dialog never showed up.
3) Try different usb cable OR usb port - Failed, adb is recognized, but no confirmation dialog on the device (device shows as unauthorized)
4) Removed all drivers and installed them again - Failed, same problem;
5) Updated android-sdk (or full delete and reinstall [remembering to adb kill-server]) - Failed, problem continues even with platform-tools up-to-date.
6) Removed all folder C:\Users\Myself\.android - Failed, it was never recreated;
7) Tried to connect via adb over wifi, device is found but unauthorized persists;
Things that gave me some clues:
1) Reboot to recovery mode allowed me to use ADB without any authorization (only while in recovery);
2) Recovery sideload works without any problem;
3) HOWEVER, when connecting to another computer (Windows XP, fresh install on a virtual machine), dialog appears and adb works!
The scenario:
1) Devices tried: Galaxy Nexus / Galaxy S3 I9300
2) ROMs tried: AOKP (4.2.2) / CM10 (4.2.2)
3) Windows 7 x64
The problem is on the computer side, that's a fact. However, I would like to SOLVE it without having to reformat my computer, or change my OS.
Where to start?
Thanks!
Click to expand...
Click to collapse
Make sure to use the latest ADB executable, also check if you don't have any other adb.exe in your computer, from command promt: where adb.exe
maxrfon said:
Make sure to use the latest ADB executable, also check if you don't have any other adb.exe in your computer, from command promt: where adb.exe
Click to expand...
Click to collapse
Hello,
No, adb.exe is up-to-date and there's a single instance of it on my computer.
Problem must be somewhere else.
Thanks anyway
legalbrr2 said:
Hello,
No, adb.exe is up-to-date and there's a single instance of it on my computer.
Problem must be somewhere else.
Thanks anyway
Click to expand...
Click to collapse
Hello,
please delete the sdk settings folder on your pc, on my linux box i deleted ~/.android and it worked
Regards
c.cicali said:
Hello,
please delete the sdk settings folder on your pc, on my linux box i deleted ~/.android and it worked
Regards
Click to expand...
Click to collapse
Doesn't work yet..
Tried to delete "C:\Users\Myself\.android" and "Documents\.android".
Did a full search on filesystem, and found no other .android folders.
Thanks anyway.
legalbrr2 said:
Doesn't work yet..
Tried to delete "C:\Users\Myself\.android" and "Documents\.android".
Did a full search on filesystem, and found no other .android folders.
Thanks anyway.
Click to expand...
Click to collapse
After removing your .android directories, you need to restart the adb server to send fresh credentials to the phone.
First unplug the phone from your computer, then run:
Code:
$ adb kill-server
$ adb start-server
Now plug your phone back in and you should see a dialog on the device asking to confirm new credentials for your computer.
After confirming the credentials you should be able to connect to your device.
I hope that this helps...
legalbrr2 said:
Hello,
I'm having the same problem "Please check the confirmation dialog on your device", but there is no such dialog on the device.
Things I tried and DID NOT SOLVE:
1) Remove /data/misc/adb/* - Failed, there was nothing there (full wipe before flash a new rom)
2) Try different ROMs - Failed, tried AOKP Milestone 1 and 2 and CM10. Dialog never showed up.
3) Try different usb cable OR usb port - Failed, adb is recognized, but no confirmation dialog on the device (device shows as unauthorized)
4) Removed all drivers and installed them again - Failed, same problem;
5) Updated android-sdk (or full delete and reinstall [remembering to adb kill-server]) - Failed, problem continues even with platform-tools up-to-date.
6) Removed all folder C:\Users\Myself\.android - Failed, it was never recreated;
7) Tried to connect via adb over wifi, device is found but unauthorized persists;
Things that gave me some clues:
1) Reboot to recovery mode allowed me to use ADB without any authorization (only while in recovery);
2) Recovery sideload works without any problem;
3) HOWEVER, when connecting to another computer (Windows XP, fresh install on a virtual machine), dialog appears and adb works!
The scenario:
1) Devices tried: Galaxy Nexus / Galaxy S3 I9300
2) ROMs tried: AOKP (4.2.2) / CM10 (4.2.2)
3) Windows 7 x64
The problem is on the computer side, that's a fact. However, I would like to SOLVE it without having to reformat my computer, or change my OS.
Where to start?
Thanks!
Click to expand...
Click to collapse
I know that this post is old, but I came across the same problem while attempting to root my Galaxy S4 today. This ended up being the solution:
1. Grant yourself root access on the PC that is running adb
2. Remove RSA Keys:
rm /home/username/.android/*
3. Restart adb server:
adb kill-server
adb start-server
I hope that this helps.
SOLVED!
I guess I should have read the previous post before I posted this but anyway maybe this helps.
I had this happen to my Verizon Samsung Galaxy S4 SCH-I545 running 4.3 (VRUEM2K) after I rooted using saferoot, then removed the SuperSU app using SuperSU's so-called "safely unroot" menu option. It will no longer request the RSA key from the Ubuntu system I previously authorized (and used to root) and won't re-root using saferoot or motochopper. But since I dual-boot Windows 7 (I hardly use it, came with the laptop), I figured I'd give Odin a try and re-flash it to stock which didn't do anything to the "custom" flag and I still got "unauthorized" in adb in Ubuntu, but I noticed it does show up fine with adb in Windows. I tried the windows verison of saferoot and it was able to re-root my phone and re-install SuperSU just fine. Phone still showed "unauthorized" in Ubuntu.
After posting this I saw the previous comment saying to rm -rf ~/.android/ in Ubuntu. I also cleared all previously authorized computers and disable dev mode on my phone, rebooted, turned dev mode back on, rebooted again. Not sure if this helped, but I went through the following steps as root:
[email protected]:~# adb kill-server
[email protected]:~# adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
15506b89 unauthorized
At this point I pretty much said "F it, not gonna work" and walked away to get a snack, leaving my phone plugged in. I was only gone a couple minutes and when I came back, the RSA authorization request had popped up on my phone. I checked the box to always allow this computer and authorized it. Then SUCCESS, as seen below:
[email protected]:~# adb devices
List of devices attached
15506b89 device
Removing the .android directory seemed to do it, but you need to wait a few minutes for the computer to re-request the RSA key.
after a week of searching. I NEVER KNEW it pop to accept to authorized. WOW cant believe it... after reading this thread im lol'ding right now.
I had tried to kill adb etc but keep saying aunauthorized. solution was to reboot my phone with usb connected,after boot it the dialog to connect appear and my s4 got authorized. backup success.
thanks to the adb kill-server guy! worked for me
gonpwnya said:
thanks to the adb kill-server guy! worked for me
Click to expand...
Click to collapse
Ditto
Here's a funky issue. I've been using ADB without any problems on 4.2.1 and 4.2.2 on this device (Stock Android and some CM10-based ROMs). When I flashed a CM10.2-based rom (JellyBro, I believe?) a few months ago, I was never able to get ADB to work, so I restored a nandroid of my previous setup. After a while, I decided to flash the stock 4.3 image (today) and see if I still have the problem. I do.
Here are the details in a format that I hope is both entertaining and helpful for troubleshooting
Okay fine, what's the problem now?
- I cannot use ADB with my N4 on 4.3.
- I cannot authorize my device.
Seriously? Simple ADB problems? Shut up and search the forums.
- I did. I tried many things.
Well what did you try, then?
I just tried to use the default feature. The phone should prompt to authorize my computer, but I never get a prompt.
I checked /data/misc/adb/ and the directory was empty.
Even so, I decided to click the "Revoke USB debugging authorizations" option in Developer options.
I copied ~/.android/adbkey.pub from my Linux box and put its contents in a new file named /data/misc/adb/adb_key on my device.
When that didn't work, I rebooted the device.
When that didn't work, I disabled/enabled ADB on the device.
When that didn't work, I killed adb on my computer, then restarted it.
When 3a-3c didn't work, I did them all sequentially before trying again, which also didn't work.
Exactly the same as above, but put it in /data/misc/adb/adb_keys intead of adb_key (because XDA and other sites cite both filenames).
Clicked the "Revoke USB debugging authorizations" button again. Rebooted the phone, killed ADB on my computer. Still no prompts to authorize.
It only removed /data/misc/adb/adb_keys, not adb_key. So I'm pretty sure adb_key is the wrong filename (despite being cited at a frequency on par with the correct name).
Update my platform-tools package. No dice.
Can't actually update; I have the most recent version (18.0.1)
Remove and reinstall platform-tools. No dice.
By the way, my permissions for the adb_keys file are 300. Owner is root. Group is root. Or in other terms:
Code:
#: ls -l adb_keys
-rw------- root root
Are you sure this is only happening to you on 4.3?
Yes. I have no problems after installing any 4.2 rom with recovery, or the 4.2.2 factory image with fastboot.
And it's exactly the same issue with factory 4.3 or a 4.3-based ROM?
Yes. Although I've only tried two or three roms, plus the factory image. There may be a magical rom out there somewhere that does work though.
Any other devices?
I tested adb with my girlfriend's 2012 Nexus 7 running 4.3. It had no issues at all.
Any other computers?
Unfortunately no. I only have my Linux Mint 15 box.
-------
Okay, so that's basically the gist of it. Does anyone else have any clever ideas? (Or does anyone see where I was an idiot and made a mistake?)
Check adb version. You need 1.0.31.
vkn said:
Check adb version. You need 1.0.31.
Click to expand...
Click to collapse
I had the same issue several weeks ago and the update to 1.0.31 fixed it here as well.
pjc123 said:
I had the same issue several weeks ago and the update to 1.0.31 fixed it here as well.
Click to expand...
Click to collapse
I did mention in the post that I already tried that. (EDIT: Well, I mentioned platform-tools, not adb specifically. Points to you.)
Code:
$ adb version
Android Debug Bridge version 1.0.31
Any other suggestions? =(
dotvezz said:
I did mention in the post that I already tried that. (EDIT: Well, I mentioned platform-tools, not adb specifically. Points to you.)
Code:
$ adb version
Android Debug Bridge version 1.0.31
Any other suggestions? =(
Click to expand...
Click to collapse
Oops, I didn't notice that. As I am using Windows when I communicate with the Nexus 4 on 4.3, I can't speak for anything related to Linux, although I do have several Linux computers.
pjc123 said:
Oops, I didn't notice that. As I am using Windows when I communicate with the Nexus 4 on 4.3, I can't speak for anything related to Linux, although I do have several Linux computers.
Click to expand...
Click to collapse
Ah, I gotcha. Thanks for trying though! =). Until I get an working solution, I'm just running 4.2 (Because really, 4.3 isn't THAT big of a deal for me).
i have the exact same problem!
i realy realy need ur help, my phone is dead without it.. i need that adb to work so i can fix this,
please help me im desprete
I had similar issues before w/ my N4 and basically did a full re-install of SDK. Have you tried that yet, might work.
Hi.
I have a nexus 7 2012 edition which turns on with The Google written logo and under the screen with a padlock. After that it will be in bootloop with a black screen ( I can see the backlight turning on/off). This is also if pressing the power+volume down combination. Seems bootloader is corrupted. Anyway I installed everything on pc plus I'm using the WugFresh Nexus Root Toolkit and here are some examples which show what errors I'm encountering when trying to flash stock firmware .
Log:
Checking ADB/FASTBOOT Connectivity
adb devices
015d4a5ed8500c01 unauthorized
fastboot devices
There is also a notification popup which tells me:
"An ADB Interface device was found but it was listed as "unauthorized"
-Accept the RSA security prompt and check "Always allow from this computer"
At this point I don't know what to do, can you help me?
Same issue - following
I have the same issue now after trying to flash a kernel to fix the slow charging issue. Following this post for any update.
Sunil_511 said:
I have the same issue now after trying to flash a kernel to fix the slow charging issue. Following this post for any update.
Click to expand...
Click to collapse
Hi, Sunil_511...
Bit speculative this, and I can't say for certain if the following solution would work, because I've never had this problem myself. It also requires that your Nexus 7 be in a fully bootable state.
Go to your Nexus 7 Developer Options in the devices settings and tap on 'Revoke USB debugging authorisations'. Tap on OK to confirm. See attached screenshot.
This, theoretically, should wipe the slate clean.
Reboot both your N7 and your PC/laptop and when you next reconnect your N7 to your PC/laptop, you'll be asked to authorise this new USB connection when you perform some action that requires it.
Well, that's the plan anyway.
Good luck?.
Rgrds,
Ged.
Nope, in my case my tab is not booting to recovery or system. The only option is adb and it is showing unauthorized. My last option what i think off is to change the motherboard.
Following
I have the same error and like to follow
Sunil_511 said:
I have the same error and like to follow
Click to expand...
Click to collapse
Google search is your friend. I found the following two methods which seems to have worked for some people.
1. If you are using OS X*:
Reboot your phone into recovery mode.
Connect it to your computer.
Open the terminal and type:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
All done! Just adb shell reboot and feel the power!
*For Windows 10, .android directory is located in your the base of your C:\User\user_name directory.
2. Go to where you have stored adb files, open that folder and press "CTRL+SHIFT+Right Click" and select and click on Open Command Prompt option
Now enter following command
adb start-server (Enter)
adb usb (Enter)
After that your device is no longer unauthorized and you should be able to use any command in your Android Mobile using PC/ Computer.
If these fixes don't work, SEARCH.
thanks buddy, i have tried pushing the adb keys but no luck. I will try tge second option. Will let you know after trying.
No difference still the same
BxG4ever said:
Hi.
I have a nexus 7 2012 edition which turns on with The Google written logo and under the screen with a padlock. After that it will be in bootloop with a black screen ( I can see the backlight turning on/off). This is also if pressing the power+volume down combination. Seems bootloader is corrupted. Anyway I installed everything on pc plus I'm using the WugFresh Nexus Root Toolkit and here are some examples which show what errors I'm encountering when trying to flash stock firmware .
Log:
Checking ADB/FASTBOOT Connectivity
adb devices
015d4a5ed8500c01 unauthorized
fastboot devices
There is also a notification popup which tells me:
"An ADB Interface device was found but it was listed as "unauthorized"
-Accept the RSA security prompt and check "Always allow from this computer"
At this point I don't know what to do, can you help me?
Click to expand...
Click to collapse
tnsmani said:
Google search is your friend. I found the following two methods which seems to have worked for some people.
1. If you are using OS X*:
Reboot your phone into recovery mode.
Connect it to your computer.
Open the terminal and type:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
All done! Just adb shell reboot and feel the power!
*For Windows 10, .android directory is located in your the base of your C:\User\user_name directory.
2. Go to where you have stored adb files, open that folder and press "CTRL+SHIFT+Right Click" and select and click on Open Command Prompt option
Now enter following command
adb start-server (Enter)
adb usb (Enter)
After that your device is no longer unauthorized and you should be able to use any command in your Android Mobile using PC/ Computer.
If these fixes don't work, SEARCH.
Click to expand...
Click to collapse
Tried your suggestion.. Which i might have tried eventually from googling.. Doesn't make any difference.
Fixed
After doing all the researches, i had to buy a new motherboard and then replace it. Installed new rom and now using it. Spared about 1400INR for a 32 gig version.
Anyone get ADB working? I'm getting a no permissions (udev rules) on my linux machine. I'm guessing we need to add the device into udev
EDIT: Solution for Ubuntu/Linux here: https://forum.xda-developers.com/showpost.php?p=73619079&postcount=20
hmm it works on my Mac though..
did you use Sudo?
stewa2jm said:
did you use Sudo?
Click to expand...
Click to collapse
Yeah, it's not working.. I tried adding the dev in my android.rules file and still nothing. I'm going to play with it more now
Sent from my PH-1 using Tapatalk
Do you need to update your ADB version on your Linux box? I had this issue at one point. With a different phone a couple years ago. Wouldn't recognize the device.
stewa2jm said:
Do you need to update your ADB version on your Linux box? I had this issue at one point. With a different phone a couple years ago. Wouldn't recognize the device.
Click to expand...
Click to collapse
I'm always on the latest version since I do a lot of Android development. I don't get why it's not working.. I've had to add devices in udev so many times, never did it give me an issue before. I'll see if I can figure it out though
Sent from my PH-1 using Tapatalk
ADB Debugging is on in Dev Options right? lol
I know its super basic, but got to check anyway.
whatever you figure out, please let us know! Good luck, and congrats on getting your device!
IM0001 said:
ADB Debugging is on in Dev Options right? lol
I know its super basic, but got to check anyway.
Click to expand...
Click to collapse
Really? Lol I did mention it works on my Mac, so yeah.. It's turned on.. I've even tried turning it off and then on again. [emoji1] [emoji1] [emoji1] [emoji1]
stewa2jm said:
whatever you figure out, please let us know! Good luck, and congrats on getting your device!
Click to expand...
Click to collapse
Will do!
Sent from my PH-1 using Tapatalk
any idea whats causing adb to not work?
drocny87 said:
I found a work-a-round to transfer your files from one phone to the Essential.
create a folder on your desktop and copy and paste all files you want transferred to the PH1. Once you have completed that just copy and paste those files from that folder to the phone.
Click to expand...
Click to collapse
wow, an extremely obvious solution to a problem no one asked about and has nothing to do with this thread!!
I've got ADB to connect somewhat. Instead of cd\sdk\platform-tools just run cd\sdk. ADB devices shows my phone, but once I ADB reboot bootloader, it will boot into the bootloader, but that's it.
I can't get it to work at all windows 10
Sent from my PH-1 using Tapatalk
I'm on Windows 10 as well. ADB works as long as the phone is booted into the OS. Once I enter the bootloader ADB nor fastboot can see the device
skw5115 said:
I'm on Windows 10 as well. ADB works as long as the phone is booted into the OS. Once I enter the bootloader ADB nor fastboot can see the device
Click to expand...
Click to collapse
What is your usb setting? Charging, file transfer?
bricky23 said:
What is your usb setting? Charging, file transfer?
Click to expand...
Click to collapse
I tried on both already
Sent from my PH-1 using Tapatalk
I got ADB working on linux. You need to add this to your 51-android.rules
#Essential
SUBSYSTEM=="usb",ATTR{idVendor}=="2e17", ATTR{idProduct}=="c032", MODE="0666", GROUP="plugdev"
I still can't get fastboot to work yet though. To get it to work I need to run: sudo $(which fastboot) devices
I'm going to play around with it more to see if I can get it to work just using fastboot devices
ADB is working on Windows 10, but as mentioned above, fastboot isn't recognized. Can't unlock the effing bootloader without that dammit.
---------- Post added at 08:20 PM ---------- Previous post was at 08:14 PM ----------
bricky23 said:
What is your usb setting? Charging, file transfer?
Click to expand...
Click to collapse
File transfer
Okay so to get it my PC to recognize the device in fastboot, I had to open Computer Management < Device Manager and find the device listed as Mata while booted into the bootloader. Windows didn't know what driver to use so I manually selected the Android Bootloader driver. You have to list all installed drivers on your machine and it should show up for windows 10 users. Device is now unlocked
skw5115 said:
Okay so to get it my PC to recognize the device in fastboot, I had to open Computer Management < Device Manager and find the device listed as Mata while booted into the bootloader. Windows didn't know what driver to use so I manually selected the Android Bootloader driver. You have to list all installed drivers on your machine and it should show up for windows 10 users. Device is now unlocked
Click to expand...
Click to collapse
Same here, just manually installed Google USB Driver and installed it as "Fastboot Interface" and it worked.
Ok I got adb and fastboot both working on Ubuntu/Linux now. Instead of adding the line I posted in my previous post just run this:
sudo sh -c "echo 'SUBSYSTEM=="usb", ATTR{idVendor}=="2e17", MODE="0666", GROUP="plugdev"' >> /etc/udev/rules.d/51-android.rules"
Then
sudo service udev restart
Then ubplug your device if it's plugged in via USB and then plug it back in. adb works as well as fastboot