Related
Hero had a hardware fault w/ the SD slot(good thing too! I dropped it last week and had a bit of rub on the top left that was bothering the hell out of me)
Was going to go get it replaced tonight, but for some damn reason the RUU won't work.
I have the latest RUU(1.56?)
Tried with phone w/ and without USB debugging
Went into fastboot mode(which made W7 install drivers for Android 1.0?) yet the RUU still won't recognize the phone.
I'm not computer illiterate, I'm just having problems with this damn RUU.
Halp?
What's the error you're getting?
The RUU basically says like
"Finding your Android Device" for about 30 seconds then says it cannot find it.
error 170...
ahh we meet again
i've helped a few people through this but i don't want to spoil the fun..
read this
all the way through it has the steps needed to get you up and going.
what os are you running?
just read windows 7..
try right clicking and "run as administrator"
thedudejdog said:
error 170...
ahh we meet again
i've helped a few people through this but i don't want to spoil the fun..
read this
all the way through it has the steps needed to get you up and going.
what os are you running?
just read windows 7..
try right clicking and "run as administrator"
Click to expand...
Click to collapse
I've read this before, I got it from geekfor.me
My windows 7 has the real administrator account enabled, running as administrator won't do anything.
intx said:
I've read this before, I got it from geekfor.me
My windows 7 has the real administrator account enabled, running as administrator won't do anything.
Click to expand...
Click to collapse
ok.
basically my next question is do you want my help or not?
i know how to make it work for you, at least three other people have gotten it to run by following my directions.
thedudejdog said:
ok.
basically my next question is do you want my help or not?
i know how to make it work for you, at least three other people have gotten it to run by following my directions.
Click to expand...
Click to collapse
Why wouldn't I want help?
ok try this.
type "adb devices"
if that sees your phone type reboot into fastboot then type "fastboot devices"
if that sees your phone then run the ruu
adb devices sees it.
boot into fastboot, fastboot devices sees it.
run the RUU, error 170 still >_<
intx said:
adb devices sees it.
boot into fastboot, fastboot devices sees it.
run the RUU, error 170 still >_<
Click to expand...
Click to collapse
have you tried this?
realmrealm said:
For some of the people running into problems with Windows 7 you may want to try:
1. Right-click on the executable file "ARUWizard.exe" and then go to "properties"
2. I believe there is a tab called "Compatibility" or something, click on it.
3. there should be a place for you to click next to a "run this program in compatibility mode" put a check there
4. below that there should be a drop down box, try choosing "Windows XP SP3" (or something similar to that)
5. near the bottom should be a place to check "run as administrator" check that.
6. click "ok" and then try running the program again.
I'm in front of a windows xp computer right now, not windows 7, so excuse me if i don't remember the options correctly, but I should be pretty close.
I also don't even know if this will work, but it's definitely worth a shot.
-AndyS-
Click to expand...
Click to collapse
or this?
10 char...
flipzmode said:
Possible resolutions would be:
1) Putting it in to fast boot and trying it again. Check your error log if it fails and seeing if it identified your phone this time.
2) Open a command prompt and "cd" to the folder where your \sdk\tools\ folder and type in "adb devices" and hit enter and see if it sees your phone. If not then that's your problem. If it DOES see your phone then enter the following command
3) adb shell reboot oem-78 -- that will reboot your phone in to RUU-ready fastboot. If you had the RUU still open then close it. Then open it and try running again.
Click to expand...
Click to collapse
or this?
crunchybutternut said:
Just had a thought.. after updating my HTC Sync software the adb included with my RUU might be out of date. I copied adb.exe, AdbWinApi.dll and fastboot.exe from C:\AndroidSDK\Tools and overwrote the files in the RUU folder. Then I ran it without a hitch.. weird, eh?
Click to expand...
Click to collapse
Tried the first two things, neither helped
I figured out part of the problem though. I had to dig up some 64 bit drivers.
I got the RUU to recognize my phone and it sends it to the bootloader and gets stuck on Waiting for bootloader then errors 170 out.
I'll try copying the files over now.
Replacing those 3 files did the trick!
Thanks
intx said:
Replacing those 3 files did the trick!
Thanks
Click to expand...
Click to collapse
no problem, when i did it i tried all of those steps at once, so i wasn't sure which one fixed it for me. so now (in theory) it should work for you on that machine every time.
wont run and get "ARUGlobal.dll can not be found" even tho im looking right at it....
I have my 2.1 DamageControl ROM running fine (thx damage!). I'm just trying to connect to adb. I'm on win7, 64bit.
I used to connect fine when I was on fresh 1.1.
I thought it was b/c I had an outdated sdk, which I did. I upgraded from v3 to v5, and made sure I downloaded all the latest, including the latest usb driver.
I also checked to make sure I have HTC sync 2.08.
but I just keep getting this.
C:\android-sdk-windows\tools>adb remount
error: device not found
Click to expand...
Click to collapse
anyone else getting this issue, or know the solution?
Try this. It worked for me with Windows 7.
http://theunlockr.com/2009/10/06/how...droid-devices/
I started at Step II. Reinstall Drivers since I already had the SDK.
crunchybutternut said:
Try this. It worked for me with Windows 7.
http://theunlockr.com/2009/10/06/how...droid-devices/
I started at Step II. Reinstall Drivers since I already had the SDK.
Click to expand...
Click to collapse
Link no worky.
I had this same problem. Go into your device manager and reinstall your ADB driver. If you're in the same situation I was in, it'll have a "!" on the ADB item in your list. Right click ADB, update driver, pick from a list of available drivers... or something like that. In the list it gives you, you should see something along the lines of "Android ADB Interface." Pick that... it may give you some kind of warning but install it anyway and you're done.
Try this,
adb kill-server
abd start-server
illogic6 said:
Link no worky.
I had this same problem. Go into your device manager and reinstall your ADB driver. If you're in the same situation I was in, it'll have a "!" on the ADB item in your list. Right click ADB, update driver, pick from a list of available drivers... or something like that. In the list it gives you, you should see something along the lines of "Android ADB Interface." Pick that... it may give you some kind of warning but install it anyway and you're done.
Click to expand...
Click to collapse
Ah hah.. thanks for the heads up. Here's the correct link. I also fixed my original post.
thanks for all the advice! I'll give them all a try.
This is what makes this website awesome. I'm glad everyone has come back together after all of that madness.
Tipharet said:
Try this,
adb kill-server
abd start-server
Click to expand...
Click to collapse
FYI, this one didn't work.
@crunchy - hm, I don't see any adb driver reference
I also went to device mgr in win7, and yeah, it has the !, but when I tried to update, it still failed. I even tried pointing to the usb driver folder in my android sdk, but it didn't like it. maybe something specific to win7 64bit?
Maybe I need to install the drivers manually? But what driver should I look for, for this Damagecontrol 2.1 ROM Sprint Hero now?
Did you make sure to enable debugging?
I don't have a link handy, but just go to the HTC support site for the Eris and download the latest HTC sync. It will fix your drivers, no fuss and straight forward.
smw6180 said:
Did you make sure to enable debugging?
Click to expand...
Click to collapse
Yes, tried with it off, and on. I also tried reinstalling HTC sync 2.08.
I didn't tell you to reinstall sync 2.0.8
Go here http://member.america.htc.com/download/Driver/DROID_ERIS_Verizon/HTCSync2.0.25.zip
And install THAT version of sync it has the proper drivers.
Think I told you to go to the Eris page by accident? Think again. Do it, fix your problem and let's all move on.
Sorry for being so blunt, just frustrated you that you wrote off my original suggestion, responding that you already tried reinstalling the same version of sync that wasn't working in the first place. If you paid attention to my first tip this would have already been solved.
obelisk79 said:
I didn't tell you to reinstall sync 2.0.8
Go here http://member.america.htc.com/download/Driver/DROID_ERIS_Verizon/HTCSync2.0.25.zip
And install THAT version of sync it has the proper drivers.
Think I told you to go to the Eris page by accident? Think again. Do it, fix your problem and let's all move on.
Sorry for being so blunt, just frustrated you that you wrote off my original suggestion, responding that you already tried reinstalling the same version of sync that wasn't working in the first place. If you paid attention to my first tip this would have already been solved.
Click to expand...
Click to collapse
actually, I didn't read your post yet when I posted my statement that I installed 2.08. I was responding to someone else. I'll try out your tip. thx.
obelisk79 said:
I didn't tell you to reinstall sync 2.0.8
Go here http://member.america.htc.com/download/Driver/DROID_ERIS_Verizon/HTCSync2.0.25.zip
And install THAT version of sync it has the proper drivers.
Think I told you to go to the Eris page by accident? Think again. Do it, fix your problem and let's all move on.
Sorry for being so blunt, just frustrated you that you wrote off my original suggestion, responding that you already tried reinstalling the same version of sync that wasn't working in the first place. If you paid attention to my first tip this would have already been solved.
Click to expand...
Click to collapse
Try your own link. It doesn't have a link to the Eris page.
EDIT: the joys of technology. When I used google chrome, the download link didn't work - when I used firefox, it did.
FYI, HTC sync 2.0.25 for the Eris didn't work.
ro_bro said:
Try your own link. It doesn't have a link to the Eris page.
googled and found it myself:
http://www.htc.com/us/support/droid-eris-verizon/downloads/
edit: ugh, the download link leads to a general support page again.
Click to expand...
Click to collapse
Must be a problem with the htc site, the link I provided was a direct link. I'll see if I can find another
Edit: now you do have some kind of weirdness going on. If that didn't work.
First make sure you have done the following... reboot pc and phone. Usb debugging enabled. Then connect phone attempt and shell and copy error here.
Also a question, did you install sync 2.0.8 prior to installing the 2.0.25version ?
A few other possible steps you could try.
Go to your start menu and type cmd one you see the cmd icon pop up in the menu rightclick and run as administrator. Then,
adb kill-server
adb start-server
adb shell
If you still get device not found try: adb devices and paste the output here.
obelisk79 said:
Must be a problem with the htc site, the link I provided was a direct link. I'll see if I can find another
Edit: now you do have some kind of weirdness going on. If that didn't work.
First make sure you have done the following... reboot pc and phone. Usb debugging enabled. Then connect phone attempt and shell and copy error here.
Also a question, did you install sync 2.0.8 prior to installing the 2.0.25version ?
A few other possible steps you could try.
Go to your start menu and type cmd one you see the cmd icon pop up in the menu rightclick and run as administrator. Then,
adb kill-server
adb start-server
adb shell
If you still get device not found try: adb devices and paste the output here.
Click to expand...
Click to collapse
Yes, I had 2.0.8 installed, but i uninstalled first before installing the 2.0.25. but I haven't tried the pc reboot, nor the kill server yet, I'll give those a try. thx!
obelisk79 said:
Must be a problem with the htc site, the link I provided was a direct link. I'll see if I can find another
Edit: now you do have some kind of weirdness going on. If that didn't work.
First make sure you have done the following... reboot pc and phone. Usb debugging enabled. Then connect phone attempt and shell and copy error here.
Also a question, did you install sync 2.0.8 prior to installing the 2.0.25version ?
A few other possible steps you could try.
Go to your start menu and type cmd one you see the cmd icon pop up in the menu rightclick and run as administrator. Then,
adb kill-server
adb start-server
adb shell
If you still get device not found try: adb devices and paste the output here.
Click to expand...
Click to collapse
This advice got me further... but here's what I get:
C:\>cd android-sdk-windows
C:\android-sdk-windows>cd tools
C:\android-sdk-windows\tools>adb remount
adb server is out of date. killing...
* daemon started successfully *
error: device not found
C:\android-sdk-windows\tools>adb kill-server
C:\android-sdk-windows\tools>adb start-server
* daemon not running. starting it now *
* daemon started successfully *
C:\android-sdk-windows\tools>adb shell
error: device not found
C:\android-sdk-windows\tools>adb devices
List of devices attached
C:\android-sdk-windows\tools>
Click to expand...
Click to collapse
FYI, I still see a '!' beside my 'Android Phone' icon in my device manager.
Try to download and Install
HTC Sync Version 2.0.18 from HTC Support and it must work for you
Thanks
okay, I devoutly hope someone can help me here, because I'm at my wit's end with this. I'm using windows 7x64. I followed the instructions in THIS thread first(after installing the android sdk directly from the main website ), and got through everything okay, but when I try to do anything with adb(adb devices, for example) I get
"
*Daemon not running, starting it now on port 5037*(this does successfully start the adb.exe process)
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon*
"
Here's what I've tried so far:
1. Killing and restarting the adb.exe process, both with task manager and with adb kill-server(which is the only adb command I've found that does anything other than return an error message)
2. reinstalling both the drivers posted in this thread and those at nookdevs
3. rebooting both the computer and the nook color multiple times.
4. deleting all SDK files and both re-downloading and re-installing.
5. deleting every file I could find and the drivers and following the Nookdevs instructions. same problem
6. using the adb_wireless app, where it tells me to use adb connect <iP address> after running the app. same error message appears. Because of this step I'm less inclined to believe that it's a driver error, since the wifi app bypasses the USB driver, at least as far as I understand. I do, however, believe my drivers are installed correctly, I have ADB Composite android device in the device manager
The only google results I got with this error(for different devices) referred to the port adb needs being locked in to something else, but that doesn't appear to be the case here, I see nothing running on port 5037 in netstat
Thank you for taking the time to read my short novel, and I appreciate the help.
*shameless bump*
seriously though, 65 views and not a single person with even a suggestion? would this be better off in a different portion of the forums? Any advice at all?
dumb question, but with out the NC plugged in, when you type in "adb devices", what get's returned?
if you get that error message, than that's a config symptom.
Hey i'm no pro and got adb to work on accident...What i found is that the android sdk folder needs to be in your user folder. So when i go to start and click my user name my android sdk folder is in there with my downloads folder, desktop folder, and music folder. Makes sense? ALso any thing i push to my device i put into that folder in the tools directory. I found that that fixed most of my problems as i had the folder in the root of my c drive. Let me know if that helps.
No luck there, but thanks for the reply anyway. gives me the same error. I suspect in your case that you were not getting into the c:\android-sdk-windows folder and moving it to your username folder fixed that problem because that's the default path when you open a cmd prompt. Thanks for trying, though
Last thing i can think of is maybe your firewall? Kill it for a few mins and see what happens.
Still happens when the device isn't connected. I agree that its a config error rather than a driver issue. Also, disabling my firewall has no effect. Thanks for the suggestions though
Sent from my NookColor using XDA App
I have the same
nicbennett said:
*Daemon not running, starting it now on port 5037*(this does successfully start the adb.exe process)
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon*
Click to expand...
Click to collapse
W7/64.
ADB worked for me for months. I used it regularly. The last thing I did was *trying* to use Wireless ADB Widget and issueing ADB TCPIP command. I have made no changes to the system.
The error occurs when no device device connected. Same error when device IS connected.
-Downloaded ADB/SDK again to a different directory, same error
-Updated USB driver and SDK components, same error
-Disabled all firewall/anti-malware/anti-virus, same error
-Rebooted multiple times, same error off boot
-Port 5037 is not bound by any app or process
-ADB, upon failed load, is not listed in Taskmgr, nothing to kill
-Deleted temp files
-Issued at prompt: ADB Disconnect, ADB USB, ADB devices: All return same error as above
-Issued at prompt: ADB kill-server, only prompt returns
Read lots of posts on the web, nothing helps.
I am really interested in a solution and would like to understand what is causing the problem. If in fact it is a configuration issue, where is the ADB config file?
Thanks.
Edit: I am running the command prompt as an administrator.
not sure what was causing the issue, I ended up reformatting my HD and re-installing, it worked fine after. Sorry I couldn't be of more help, I looked everywhere for about 2 weeks and didn't find a thing that worked
nicbennett said:
not sure what was causing the issue, I ended up reformatting my HD and re-installing, it worked fine after. Sorry I couldn't be of more help, I looked everywhere for about 2 weeks and didn't find a thing that worked
Click to expand...
Click to collapse
Wow... I would hate to have to rebuild my computer just to get ADB back. I will post this in the Evo forum and see if there is some help.
Edit: Started a new thread in Evo forum:
http://forum.xda-developers.com/showthread.php?p=10730809#post10730809
so i transferred my music from my laptop to my tab, but while looking at my music on the tab it all of a sudden exits and asks me to either force close or report. Anyone have any idea why this could be happening? I thought all was good once i got the files to tranfer, but then this happened...
could you try reproducing the issue with logcat running?
Sure, would you mind explaining how to do that though? Not wuite sure what logcat is... Appreciate all the help! Hope to get this squared away.
yeah, I figured I would have to do that but I hate writing out instructions just to find out that the person already knows everything I had to say.
I'll write this assuming you're using windows.. hopefully that's not a mistake
this may be a lot more work than you're willing to do and it may not give any useful results. you're certainly more than welcome to try it though.
for a much easier, but less helpful method, skip to the end.
first, install the adb driver. there is a link floating around somewhere to just the driver, but I can't find it so you're probably better off just installing samsung kies. this will install the drivers for you.
http://www.samsung.com/ca/support/m...softwaremanual.do?page=MOBILE.SOFTWARE.MANUAL
then, you'll need to download the android sdk.
http://developer.android.com/sdk/index.html
download it, open the sdk manager and then let it install it's stuff. all you really need is "Android SDK Platform-tools, revision X." I believe the most recent revision is 5, but it doesn't really matter.
now, open a command prompt. in windows 7, you can just hit start and then type cmd. in xp or vista I believe if you have to use start->run or windows key + r, then type cmd and click run.
from here, change directory to the platform tools folder of your sdk. most likely something like this
Code:
cd C:\Program Files\android-sdk-windows\platform-tools\
though it will depend on where you installed your sdk
now go into settings->applications->development and check "usb debugging" on your tablet. after that is done, connect it to your computer with usb and type
Code:
adb devices
if something shows up, your device is recognized. otherwise.. ask for help, I guess
finally, type
Code:
adb logcat -c
adb logcat
and then try to reproduce the error. this will give you tons of information about what's going on in the system. hopefully, it will give you some idea why it is crashing.
Note: the "-c" will clear all previous logs
now, for the short version.
In the android market, download "Android Terminal Emulator"
attempt to reproduce the error then open the terminal emulator and type
Code:
logcat &
this will show you all logs since the last reboot, assuming you haven't cleared them with "logcat -c." It might be a good idea to use "logcat -c" before you start trying to reproduce the error.
hope that helps,
Sam
First of all cant thank you enough for trying to help out. So i went with the second option as to limit my chances of having to ask more questions...yeah about that. With option 2 i could not run the "logcat -c" and after reproducing the error and running "logcat &" i get a permission error... Ideas? Thanks again!
hard to say, man.. what does the error say exactly?
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