Database Users

HD2 sync with Win7 64bit and Outlook 2007

Hi,
my new Win7 premium home (64bit) PC can't connect with my HD2 (stock rom). Driver install always ends with a access denied. Outlook is 2007.
In the past I had no (only few) problems with XP(SP3) and Outlook 2003 and my hd2 and my X1.
I uninstalled and reinstalled the whole win mob sw several times.
What can I do - any ideas?
regards

Are you trying to connect with Activesync or disc drive?

I couldn't install active sync under win7. I had to install 'win mobile device manager 6.1' which ist ok but driver install always says 'access denied'.
The hole thing should last about 20 seconds but I'm working on it severel hours
Ideas would be wellcome.
Edit. My hd2 has settings 'active sync' with 'fast synchronisation off'. I hpe this is correct in english, my settings are german.

i'm usign Windows 7 Pro x64 with Office 2007.
No problems at all.
Do you have enough priviledge when you install drivers?
Did you download the correct driver package?

I'm logged in as admin and I loaded the package from MS (drvupdate-amd64.exe 12.749kB).
Edit: I found a 'trick' in another forum (search registry for 'KLFLTDEV' and delete this branch - HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control/Class UpperFilters in Portable Device) which didn't work for me.

Mine worked fine, but I'm not sure if I had to run as admin or not. Did you try the whole right click-run as admin option? Or in properties set the compatibility to something else? Otherwise, there may be a problem with your phone's software and a hard reset could fix that. With a good backup program, it doesn't suck as bad as it sounds. =p

Hi,
hard reset of my hd2 is not a problem.
I have a unknown device under portable devices and after driver update I get a 'driver found' and afterwards an 'access denied'.

after googling this turned up in microsoft forum about getting "access is denied" error when installing drivers:
This issue is caused by the monitor driver update fails to access following
files.
C:\Windows\inf\infpub.dat
C:\Windows\inf\infstor.dat
C:\Windows\inf\infstrng.dat
C:\Windows\inf\drvindex.dat
C:\Windows\inf\INFCACHE.1
Please follow these steps to set the permission of these files.
1. Negative to C:\Windows\inf\
2. Right click infpub.dat and choose properties.
3. Select Security tab, click Edit.
4. Click the current User Account name, check Full Control checkbox as Allow.
Note : If the current User Account name is not listed, please click “Add”,
following the “Enter the object name to select” title, type in the current
User Account name and then click Ok.
5. Click Apply, click OK.
Please repeat the above steps with infstor.dat, infstrng.dat, drvindex.dat
and INFCACHE.1.
After that trying to install the driver once again.
Click to expand...
Click to collapse

Hi,
I found the mentioned fiiles in \windows\system32\driverstore and did what you told me - but no success Access denied.
thanks

I also have Win 7, and Windows Mobile Device Center. I have had problems with Activesync before, but was due to "Enable faster data syncronization" being checked. However, I was always able to connect with the computer through "Disc Drive" option. This won't solve your problems entirely, but you can find out if your computer will recognize the phone at all.

dmsc said:
Hi,
I found the mentioned fiiles in \windows\system32\driverstore and did what you told me - but no success Access denied.
thanks
Click to expand...
Click to collapse
did you take the ownership of that directory and files?

thats mysterious...i have also win7 x64 and outlook 2007.
when i first connect my hd2, it automatically downloads WMDC and hd2 drivers...
did you try different usb ports?
DN41

richteralan said:
did you take the ownership of that directory and files?
Click to expand...
Click to collapse
Yes I did and I checked it too.
I tried all again and recogniced that after taking the ownership all is fine but a moment later the ownership disappears again. So how can I do this permanantly?
And yes I tried different USB boards.
thanks

THIS IS THE ANSWER
I had same issues and resolved it by using the MITTY without driver solution!!
http://forum.xda-developers.com/showthread.php?t=623356
It works - just follow all the instryctions and load all drivers they say!

Mr Kipper said:
THIS IS THE ANSWER
I had same issues and resolved it by using the MITTY without driver solution!!
http://forum.xda-developers.com/showthread.php?t=623356
It works - just follow all the instryctions and load all drivers they say!
Click to expand...
Click to collapse
Thanks,
but this isn't the solution I'm looking for because this is to much modification of my hd2. I just want to install mobile device center 6.1 to win7 64bit + driver.
regards

I never had any issues getting Win7 pro 64 and Outlook 7 / 2010 syncing up.
I did change my windows setup a fair abit. If you are not full admin that could be it. Did you do a fresh windows install or upgrade an existing install to windows 7?
Taking control of folders can be problematic, even with a full install. I still have a few folders being annoying but most of them I got working.
There is a hidden full access admin account hidden on the computer, you might try enabling that and giving it a go. Or to see if it can bump your access levels up.
1. Click on “Start button -> All Programs -> Accessories“. Right-click on “Command Prompt” and select “Run As Administrator“. If you are prompted to enter password, enter the password and continue. You can also open Command Prompt in Administrator mode by typing “cmd” in Startmenu Search box and press “Ctrl+Shift+Enter“.
2. Now provide following command:
net user administrator /active:yes
3. Thats it. The Administrator account will be enabled. If you want to disable it again, simply replace "yes" with "no" in above command.
Click to expand...
Click to collapse
I saw your post about logging in as admin, but that one is even more admin so it might do something. Folder control is also a big deal with windows now so be sure you have control.
Did you sync your phone with older computers? I cant remember if this phone had issues with multiple PCs in its sync list or not, I only use two and thats what my old one would only allow.

10332007 said:
Did you do a fresh windows install or upgrade an existing install to windows 7?
Click to expand...
Click to collapse
It is a brand new PC and Win7 is a fresh install.
10332007 said:
There is a hidden full access admin account hidden on the computer, you might try enabling that and giving it a go. Or to see if it can bump your access levels up.
I saw your post about logging in as admin, but that one is even more admin so it might do something. Folder control is also a big deal with windows now so be sure you have control.
Click to expand...
Click to collapse
I guess this is my problem.
10332007 said:
Did you sync your phone with older computers? I cant remember if this phone had issues with multiple PCs in its sync list or not, I only use two and thats what my old one would only allow.
Click to expand...
Click to collapse
I did sync with my older PC with WinXP Sp3 and Outlook 2003. With active sync I had only minor problems. Maybe it would be the same with Win7 and Outlook 2007 - but I can't install the driver.
Thanks for your suggestions, I'll give them a try.
regards

Sorry,
but I can't get ownership of \windows\system32\driverstore. I guess it would be neccessary but I get always 'access denied' - even I'm logged in as administrator. Why I can't get ownership of this directories/files ?
Sh.t Win7

I'm have the same issue also with Device Center not recognizing my HD2. It will recognize the HD2 as a "Disk Drive" but not as "Active sync" I tried with/without the underbox checked.
I've tried all of my USB ports. I just tried the cmd: "net user administrator /active:yes", but I get "System error 5 has occurred. Access denied"
I'm running windows 7 Ultimate 64bit-Outlook 2007

Hi,
I did it.
Unfortunately I don't know exactly what I did. Something like get ownership of some Files in \windows\system32 (belonging to windows mobile) and getting ownership of some registry entries (belonging to windows mobile) - only black despair.
After restart I changed the usb port and - 30 seconds later sync was running
I'm happy now but can't tell you exactly what to do.
regards

[Q] "adb server didn't ack * failed to start daemon"

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

Clockworkmod Tether on Windows 8

Trying to install clockworkmod tether on windows 8 laptop but is failing saying tapinstall.exe failed. Eventvwr shows error 1722. Any help would be appreciated.

ixiduffixi said:
Trying to install clockworkmod tether on windows 8 laptop but is failing saying tapinstall.exe failed. Eventvwr shows error 1722. Any help would be appreciated.
Click to expand...
Click to collapse
You must shut off windows 8 driver signing security. It installed fine after i did this.
Click Advanced Startup Under The General Heading Under More PC Settings
After Reboot Click Troubleshoot Advanced Options, Advanced System Setting
After Reboot Type Number To Disable Driver Signing Security
Then Load Up windows 8 then install. This time it will ask you weather or not to install the drivers.

JSmith549 said:
You must shut off windows 8 driver signing security. It installed fine after i did this.
Click Advanced Startup Under The General Heading Under More PC Settings
After Reboot Click Troubleshoot Advanced Options, Advanced System Setting
After Reboot Type Number To Disable Driver Signing Security
Then Load Up windows 8 then install. This time it will ask you weather or not to install the drivers.
Click to expand...
Click to collapse
I will try this once I get home. If this works you, my friend, are my hero.

Thank you for this, solved my problem as well!

JSmith549 said:
You must shut off windows 8 driver signing security. It installed fine after i did this.
Click Advanced Startup Under The General Heading Under More PC Settings
After Reboot Click Troubleshoot Advanced Options, Advanced System Setting
After Reboot Type Number To Disable Driver Signing Security
Then Load Up windows 8 then install. This time it will ask you weather or not to install the drivers.
Click to expand...
Click to collapse
Looks like it changed a little with 8.1. Now its located in:
Setting > Change PC Settings > Update and Recovery > Under Advanced Click Restart Now

JSmith549 said:
You must shut off windows 8 driver signing security. It installed fine after i did this.
Click Advanced Startup Under The General Heading Under More PC Settings
After Reboot Click Troubleshoot Advanced Options, Advanced System Setting
After Reboot Type Number To Disable Driver Signing Security
Then Load Up windows 8 then install. This time it will ask you weather or not to install the drivers.
Click to expand...
Click to collapse
Thank you - mine also worked!!!! :good: ur my :angel:

Is Samsung ADB Driver ALSO Not Digitally Signed In Windows 8.1?
crsmith6196 said:
Thank you - mine also worked!!!! :good: ur my :angel:
Click to expand...
Click to collapse
Your solution allowed Tether to install for me. Do I need to do the same thing for the Samsung ADB drivers?
73 DE N4RPS
Rob

I can get Tether installed on both my Windows 8 Laptop and my Galaxy Nexus device (running 4.3, no root) and I used to be able to use Tether with no issue about one year ago. Now, however, when trying to initiate Tether, this is what I'm presented with:
Starting Tether...
C:\Program Files (x86)\ClockworkMod\Tether\node-tuntap
Opening tun device.
Opening tun device: null
Waiting for interface to get ready... (forker, waiting 5 seconds)
Waiting for interface to get ready... (postSetup, waiting 5 seconds)
Forking worker.
Tun/tap device IP: 10.0.0.1
Reading tun/tap device...
Opening tun device.
adb binary path: "C:\Program Files (x86)\ClockworkMod\Tether\win32\adb.exe"
Checking phone status...
tun worker initialized.
Listening on tether port...
0A3C31D90400C017 New device found.
0A3C31D90400C017 Connecting to device.
0A3C31D90400C017 Checking if package is installed.
Error listing pacakges. Assuming Tether.apk is already installed.
0A3C31D90400C017 Setting up adb port forwarding to port 30002.
0A3C31D90400C017 adb port forwarding results:
{ '0':
{ [Error: Command failed: error: device offline
] killed: false, code: 1, signal: null },
'1': '',
'2': 'error: device offline\r\n' }
0A3C31D90400C017 Error forwarding:
{ [Error: Command failed: error: device offline
] killed: false, code: 1, signal: null }
0A3C31D90400C017 Creating relay for device.
0A3C31D90400C017 Tether error:
{ '0':
{ [Error: connect ECONNREFUSED]
code: 'ECONNREFUSED',
errno: 'ECONNREFUSED',
syscall: 'connect' } }
cleaing up relay connection
0A3C31D90400C017 Tether connection closed.
cleaing up relay connection
0A3C31D90400C017 Tether connection closed.
This is just repeated infinitely until I manually stop Tether on my computer.
Since this is the only thread that comes up when searching for Tether issues on Windows 8 machines I could find, is there anyone who can help me figure out how to get this back to working order?

miguelshihto said:
I can get Tether installed on both my Windows 8 Laptop and my Galaxy Nexus device (running 4.3, no root) and I used to be able to use Tether with no issue about one year ago. Now, however, when trying to initiate Tether, this is what I'm presented with:
Starting Tether...
C:\Program Files (x86)\ClockworkMod\Tether\node-tuntap
Opening tun device.
Opening tun device: null
Waiting for interface to get ready... (forker, waiting 5 seconds)
Waiting for interface to get ready... (postSetup, waiting 5 seconds)
Forking worker.
...........
This is just repeated infinitely until I manually stop Tether on my computer.
Since this is the only thread that comes up when searching for Tether issues on Windows 8 machines I could find, is there anyone who can help me figure out how to get this back to working order?
Click to expand...
Click to collapse
I'm getting the same thing - no luck with it so far.
Anyone who's figured this out - it'd be much appreciated if you can help!

Surface Pro 3
So i just bot a surface pro 3 and i was trying to instal clockworks tethering system and it wants me to download .net frameworks version 2.0, but when i try to download it, it says i already have it. I could relay use some help!

bit late...
javiertrevino73 said:
So i just bot a surface pro 3 and i was trying to instal clockworks tethering system and it wants me to download .net frameworks version 2.0, but when i try to download it, it says i already have it. I could relay use some help!
Click to expand...
Click to collapse
.NET Framework 2.0 is not installed on Windows 8 by default.
To install it, go to Control Panel – Programs – Turn Windows features on or off – Check ‘Microsoft .NET Framework 3.5.1′ – OK.
Note, that .NET Framework 2.0 is included into version 3.5.
Source: wishmesh.com/2011/09/net-framework-2-0-is-not-installed-on-windows-8-developer-preview-by-default

I just bumped up from windows 7 to 10 and when I go to use my tether all I get is this C:\Program Files (x86)\ClockworkMod\Tether when I push start. I haven't read any issuse regaruding tether and windows 10 I doubt I am the the first, does anyone here have any idea what is going on?

Durteedee said:
I just bumped up from windows 7 to 10 and when I go to use my tether all I get is this C:\Program Files (x86)\ClockworkMod\Tether when I push start. I haven't read any issuse regaruding tether and windows 10 I doubt I am the the first, does anyone here have any idea what is going on?
Click to expand...
Click to collapse
I'm also having this same issue so compatibility appears to be broken in Windows 10.

Durteedee said:
I just bumped up from windows 7 to 10 and when I go to use my tether all I get is this C:\Program Files (x86)\ClockworkMod\Tether when I push start. I haven't read any issuse regaruding tether and windows 10 I doubt I am the the first, does anyone here have any idea what is going on?
Click to expand...
Click to collapse
I'm having the same problem myself, I just reported it to the developer so hopefully there will be a fix before too long.

Temp fix at least.
XTCrefugee said:
I'm having the same problem myself, I just reported it to the developer so hopefully there will be a fix before too long.
Click to expand...
Click to collapse
Not too sure, I'm no developer, but I believe there may be issues with the adb drivers. I installed PdaNet+ (same type of app.) and it specifically says Win10 compatible. I allowed it to overwrite the adb drivers with the driver's it determined to be correct and the PdaNet+ app works and tethers to my laptop. I am unfortunately in an area right now with only 2G service so I will not be messing around with it too much tonight but maybe tomorrow I can see if it is going to be a replacement or maybe the new drivers will work with the CM Tether software.

Well i hope they can get too or soon. I dont think its my adb drivers

sprint users
pdanet+ is blocked by sprint.
masqman said:
Not too sure, I'm no developer, but I believe there may be issues with the adb drivers. I installed PdaNet+ (same type of app.) and it specifically says Win10 compatible. I allowed it to overwrite the adb drivers with the driver's it determined to be correct and the PdaNet+ app works and tethers to my laptop. I am unfortunately in an area right now with only 2G service so I will not be messing around with it too much tonight but maybe tomorrow I can see if it is going to be a replacement or maybe the new drivers will work with the CM Tether software.
Click to expand...
Click to collapse

Its *not* usb drivers...
...because
adb devices
and
adb shell ps
...work just fine (after authorising).
Justin C thinks its changes to .Net on the ClockWorkMod forum (I can't post a link unfortunately).
Specifically I think the exe is failing to create the virtual network device (TAP) which then gets passed to run.bat
run.bat should then open up the windows firewall but it just fails with very little output when given no TAP index.
So it could also be driver related. I tried briefly adding some third party Windows 10 TAP driver but to no avail.

[Q] ADB error: device unauthorized and device offline

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

MTP Solution!

Hi!
I've been having some problems with MTP and I've been searching for days and finally found a solution!
My problem was that MTP was showing a yellow exclamation in device manager and an error "Code 31"
After installing, uninstalling and re-installing dozens of drivers I found this solution:
1. With phone unplugged open cmd (Run as Administrator)
2.Type this command:
Code:
net localgroup Administrators "local service" /add
3. Plug phone
4. ???
5. Profit!
Check this thread for more info - all credits here: http://forum.xda-developers.com/showthread.php?t=1115366

It looks dangerous for your computer security.
Regards

Magissia said:
It looks dangerous for your computer security.
Regards
Click to expand...
Click to collapse
Well maybe it is a bit dangerous..however, it does not add your local account to the administrator group. just the "Local Service" account.
This is the only solution I've found for my MTP problem and I thought it would be good to share cause I've spent days trying to fix it.
Anyway, I believe there are many things we do in these forums here(generally, at xda forums. not m8 specific), that make our phones less secure, but we still do it because we love to control our devices in any way we want.
:highfive:

Easiest way is just to swich off device (yes off ?) plug to Pc and wait for Windows to install correct drivers
Works for me ?

pawslo1984 said:
Easiest way is just to swich off device (yes off ?) plug to Pc and wait for Windows to install correct drivers
Works for me ?
Click to expand...
Click to collapse
This for didn't work on my PC. But what did work (similar) is to manually select the device in Device Manager, and pick the option to pick the drivers, then selected the generic Android MTP device.

andreasyeah said:
Hi!
I've been having some problems with MTP and I've been searching for days and finally found a solution!
My problem was that MTP was showing a yellow exclamation in device manager and an error "Code 31"
After installing, uninstalling and re-installing dozens of drivers I found this solution:
1. With phone unplugged open cmd (Run as Administrator)
2.Type this command:
Code:
net localgroup Administrators "local service" /add
3. Plug phone
4. ???
5. Profit!
Check this thread for more info - all credits here: http://forum.xda-developers.com/showthread.php?t=1115366
Click to expand...
Click to collapse
OMG...I just want to thank you so much! I know you may not be the original credit, but thank you so much for reposting this! I have had my Galaxy Tab Pro 8.4 for months now with its damned MTP Device was unsuccessful and have not been able to enact a solution til now! I am truly appreciative...

simplepinoi177 said:
OMG...I just want to thank you so much! I know you may not be the original credit, but thank you so much for reposting this! I have had my Galaxy Tab Pro 8.4 for months now with its damned MTP Device was unsuccessful and have not been able to enact a solution til now! I am truly appreciative...
Click to expand...
Click to collapse
Glad you finally found a solution!