Related
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.
Hi Guys,
I'm trying to start some Android development however I've run into a couple of problems during Dev environment set up. I've been following the adt-bundle install instructions as I opted to use the ADT bundle.
This first problem is that the Android Virtual Device Manager will not run. I get a message saying "Failed to execute tools\android.bat The system cannot find the specified file". No idea what to do about that one.
The second is that I cannot run my app. I'm trying to run it on my phone (HTC Desire C) how I keep getting the message :
Code:
[2013-07-13 07:33:37 - MyFirstApp] ------------------------------
[2013-07-13 07:33:37 - MyFirstApp] Android Launch!
[2013-07-13 07:33:37 - MyFirstApp] The connection to adb is down, and a severe error has occured.
[2013-07-13 07:33:37 - MyFirstApp] You must restart adb and Eclipse.
[2013-07-13 07:33:37 - MyFirstApp] Please ensure that adb is correctly located at 'C:\Program Files\adt-bundle-windows-x86_64-20130522\sdk\platform-tools\adb.exe' and can be executed.
I've tried resetting adb via command prompt using adb kill-server and then restarting using adb devices and checking that a device is connected however it doesn't seem to make a difference.
I've also tried connecting my N7 tablet up and install the usb drives in the sdk and I get the same errors
It's incredibly frustrating and I would really appreciate some guidance.
Thanks in advance
Samishal
[2013-07-13 07:33:37 - MyFirstApp] Please ensure that adb is correctly located at 'C:\Program Files\adt-bundle-windows-x86_64-20130522\sdk\platform-tools\adb.exe' and can be executed.
is your adb there? and is it executable? (are you running as admin?)
I have also got same error AVD error.. ihad solved it by opening this file "C:\android\sdk\tools\android.bat" and updating its component..
I have google nexs 4, kitkat 4.4 updated to
I have debugger mode enabled
I try to reset abd from my eclipse i get
[2013-12-24 23:18:49 - DeviceMonitor] Adb connection Error:An existing connection was forcibly closed by the remote host
[2013-12-24 23:18:50 - DeviceMonitor] Connection attempts: 1
my device is detected by my computer..but when i try running application, my eclipse doesnt detect it?
please help
my project build target android 4.4
jdk compliance 1.6
minmiunm required sdk android 2.2 froyo chosen
target sdk: api 18
compile with: api 19 android 4.4 kitkat
so anyone?
my winbdows is windows 8
problem is not from device, because it works on windows 7...and another pc.
I also done this http://developer.android.com/sdk/win-usb.html#top
Hi
Are you sure you have ADB set up properly? You may want to get to know ADB here. At least run the devices command to see where the problem is. What you should try is restarting both Windows and your phone (we all know windows...). If that doesn't work you'll want to try a different USB cable and socket but as you are saying the device is detected by windows so the hardware shouldn't be a problem. A complete reinstall of eclipse may be needed as well.
There is an edit button so no need to post 5! times.
i fixed it by updating driver software in device managers..and selecting the google usb driver location i donwloaded via the sdk manager
thanks
krikor1 said:
i fixed it by updating driver software in device managers..and selecting the google usb driver location i donwloaded via the sdk manager
thanks
Click to expand...
Click to collapse
Great! Have fun developing!
This guide is for people that have always problems with drivers, ADB or fastboot problems, with this guide you will clear all.
Tested and working with windows 8.1 (it will work with all other versions of windows, probably not with Windows 10 preview).
*0) Unplug of course the phone from the PC
1) Download USBDeview (32bit version here http://www.nirsoft.net/utils/usbdeview.zip - 64bit version here http://www.nirsoft.net/utils/usbdeview-x64.zip) to erase every driver on the pc (look under "Description" tab and uninstall all Asus things, MOOREFIELD, delete also your previous phones drivers or unused devices)
2) Reboot
3) If you are on windows 8 or 8.1 disable driver signature verification and than install
1- Intel Drivers https://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
2- ADB Installer http://forum.xda-developers.com/showthread.php?p=48915118#post48915118 (don't change installation path)
4) Reboot
5) Go in C:/adb, hold shift on keyboard, right click in the folder and "Open command prompt here"
6) Go to recovery with the phone plugged in
7) Tap apply update from ADB Sideload
7) Type in the previous cmd window: adb devices
If you can see your device, congratulations!
Thanks to @cangcan to this other tip:
If you installed bluestack on your pc, adb will show 'device emulator' something like that and you need to turn off the bluestack service..
1. Go to start and type services.msc
2. Look for Bluestack android service
3. Stop or disable the service
Its messing up my adb connection in windows 7 and now the zf2 device is recognised on adb after disabled Bluestack services..
Thanks to- Everyone in this section
Snoop05 for "15 seconds ADB Installer"
another thing i found for adb device not recognised for example in my case before..
if you installed bluestack on your pc or laptop, adb will show 'device emulator' something like that..
you need to turn off the bluestack service..
1. go to start and type services.msc
2. look for bluestack android service
3. stop or disable the service
its messing up my adb connection in windows 7 and now the zf2 device is recognised on adb after disabled bluestack services..
type adb devices to confirm it.
cangcan said:
another thing i found for adb device not recognised for example in my case before..
if you installed bluestack on your pc or laptop, adb will show 'device emulator' something like that..
you need to turn off the bluestack service..
1. go to start and type services.msc
2. look for bluestack android service
3. stop or disable the service
its messing up my adb connection in windows 7 and now the zf2 device is recognised on adb after disabled bluestack services..
type adb devices to confirm it.
Click to expand...
Click to collapse
I will add this to first post, thanks
Hello, I badly need someones assistance. I accidentally installed the OTA update on my rooted zenfone 2 causing it to be bricked. I have spent the last 3 hours uninstalling and then reinstalling the drivers per the above directions. My PC recognized when I connect the phone via USB, and it is showing up as a working device in the device manager screen. It shows the drivers are installed properly and everything but I just cannot view it. I tried disabling the bluestack (it actually was not turned on but I made sure to disable it in case) and that did not work as well. I now have a zenfone 2 that is currently a paperweight and I cannot for the life of me figure out what to do next. Any help would be greatly appreciated.
Thank you for this
I happen to update platform-tools in the Android SDK from version 23.1 to version 24 on an older PC.
The newest adb.exe included with v24 no longer works on WinXP.
You will get the following error upon startup:
adb.exe - Entry Point Not Found
The procedure entry point WSAPoll could not be located in the dynamic link library WS2_32.dll.
Click to expand...
Click to collapse
In case anyone is curious, I tracked the change down to this one:
https://android-review.googlesource.com/#/c/203387/
ADB
I've attached the v23.1 adb and fastboot to this post in case someone needs the previous version (which works fine with 5x up to at least MTC20F)
Just unzip and you can use adb/fastboot from the resulting platform-tools-v23.1 directory or copy them over to where your normal platform-tools directory is.
USB drivers for 5x
I also included USB drivers that work with 5x. These should work for 32/64-bit for winxp and vista. Win7 is maybe, haven't tested.
They WILL NOT work with win8 and above due to changes in driver enforcement. I am not sure about win8.x but on win10, there is a built-in driver that works with adb. To get bootloader/fastboot driver, just allow win10 to search for drivers. It will load Marshall London Bootloader Interface. This is for a different phone from music company Marshall, but it works fine since it is an Android-based device.
I could never find one official driver from google or lg that would work with adb inside android, adb inside twrp, adb sideload inside stock recovery, and fastboot.
I stopped worrying about why it works for other people and just fixed the problem myself.
Not sure if it matters to that many people these days, but it was confirmed the change in adb is not a bug and will persist going forward, so if you ever need to run adb on a WinXP box or emulator, you'll need to retrieve platform-tools-23.1 or earlier.
WinXP compatible platform-tools also could be downloaded from official repository:
http://dl-ssl.google.com/android/repository/platform-tools_r23.1.0-windows.zip
Thank you so much for this sfhub. This was driving me crazy getting bootloader access with Win 7. Updated to the driver you linked and worked great. I guess most people out there are using Win 8 or 10 now? Minblowing that so few use 7.
Greefus said:
Thank you so much for this sfhub. This was driving me crazy getting bootloader access with Win 7. Updated to the driver you linked and worked great. I guess most people out there are using Win 8 or 10 now? Minblowing that so few use 7.
Click to expand...
Click to collapse
Actually Windows 7 is still installed on nearly half of all desktop and laptop computers: https://www.netmarketshare.com/operating-system-market-share.aspx?qprid=10&qpcustomd=0. Did the most recent SDK drop support for it?
For anyone who wants to use adb on the latest version of Android Studio running on Windows XP use the adb .exe from version 23 and paste it into the platform tool folder. Keep a copy of the new adb.exe just in case you need it. No need to use the entire v23 platform tool folder.
The references in this thread have so far appear to refer to latest adb compatibility, particularly for Windows XP.
Does the latest fastboot still work fine with Windows XP? If not, what was the last known-good or thought to be last known-good version for Windows XP?
Hi
The adb from the v2.3.1 works fine with my win xp, thank you for the file.
Hello,
I am another WinXP user facing the error
"adb.exe - Entry Point Not Found. The procedure entry point WSAPoll could not be located in the dynamic link library WS2_32.dll."
@sfhub & @Sintetix
Thanks for the info and provide the latest version supported by XP ...
Are you aware of any important changes / additions in the future versions to be concerned of?
Regards
---------- Post added at 11:16 ---------- Previous post was at 10:47 ----------
Just to let you know,
C:\v23.1>adb devices
List of devices attached
adb server is out of date. killing...
error: protocol fault (couldn't read status): Invalid argument
error: could not install *smartsocket* listener: cannot bind to 127.0.0.1:5037:
I am trying to connect an Asus Transformer tablet with "MTP file transfer" mode on WinXP Service Pack 3 laptop... cable is fine and the plan is to move from custom ROM (Android 6.0) to Stock (JellyBean) ... Something I already did few years ago having Win10 (I have the receipe used then)
I think I better get a fresh Win7 on my primary Win10 PC and start from there... I never liked W10 anyway ... and since I did mods to [finally &effectively] stop the [annoying, unwanted & plenty of bugs] Win10 updates ... I got funny errors when using dev stuff ... even DotNet ...
And I need to think a better O.S for the XP PC ...
Time to change. Regards
Before jumping to my major O.S actions,
I gave a chance to my Asus Transformer tablet with another cable under the W10 PC and the latest adb (r29.0.2-win) and this second time it worked fine ...
The first time and first cable did not work (reason that drove me to the WinXP PC thinking the cause was Win10)
fastboot devices
was literally returning
???????????? fastboot
But this second time with another cable
fastboot devices
returned
BLAxxIDxxSTRING fastboot
And I was finally able to perform the format and flash series of commands to return my tablet to the stock ROM ...
As I understand this thread is about WinXP, for testing purposes, I hooked my fresh flashed tablet to the WinXP PC with the successful spare cable, and
adb devices
got again
List of devices attached
adb server is out of date. killing...
error: protocol fault (couldn't read status): Invalid argument
error: could not install *smartsocket* listener: cannot bind to 127.0.0.1:5037
Certainly I don't have the explanation of this, but I can tell you is not because a faulty cable or something related to the tablet.
And something scary to add: the first cable looks in good shape and is the one used every day to charge the tablet without any delays or issues ...
Hope someone find this useful and provide more insight. Regards