[Q] HELP... Problem with ADB in C# Program. - Hero CDMA Q&A, Help & Troubleshooting

ok, so i wrote a program in C# that will open a process CMD.exe and send adb Commands from a Working directory i setup previously that includes Adb and all the other goodies i need for automating the process of rooting and such.
here's my issue, the program will work perfectly in Win 7, but when i run in XP,
i run ADB shell reboot. the phone will reboot. but never reconnect until i end the my program process. ive tried adb kill-server. tried closing the process within my program. i do notice in XP adb will open two adb.exe processes. even when running outside of my program in the command prompt.
i am using a backgroundworker thread to send the commands.
any help is appreciated.
let me know if you want me to post some code. though i don't think its the programming.

Don't think its the programming either. XP has all sorts of weird bugs and why I jumped ship immediately when 7 came out and have been quite happy since. Don't know much about programming but I've read alot of issues with XP and adb. Stick with 7 if you can.

ok, so still haven't found out why adb doesn't like Win XP. the way i got around it was to drop C# for the ADB commands. i made a batch script to run my adb commands. and a C# console app to send the Serial Modem Commands(for PRL and NV item writing) that i call in my Batch file.
but if anyone has any tips to try ill for sure try them.
more detailed description.
i create a new thread that will create a Process of cmd.exe then do a process.StandardInput("ADB Commands");
the current running thread will finish before the next can be started so no prob with multiple threads running.
all my adb commands ie. adb push recovery.img /wherever/recovery.img
work just fine and does what its 'spose to.
until i get to adb shell reboot.
the phone will reboot but the adb driver is never reconnected after the reboot. like it normally would when running the command from the terminal.
i will have to close my C# program before it will connect and recognize the driver again.
again all this works just fine in Win 7.
i also tried to do a "Scan new Hardware" in device manager after reboot and both programs will just go unresponsive at that point.
next, i will attempt to make my own ADB in C#. if im not mistaken adb uses a TCP connection to communicate with the device. default port 5037 me thinks.

@TronofTroy
Hey do you mind sharing a couple of commands with me in C# on how to write the prl n nv items please.
Also I have been trying to send commands from a windows based form in C# but I can figure out how to do it properly.
Thank You very much!

I just use batch scripts and run them.

filmaker said:
I just use batch scripts and run them.
Click to expand...
Click to collapse
U mean u can write prl, nam, and Evdo with a batch script?
Slinged from my iPhone 4 On Straight Talk using Tapatalk

Related

"ADB server didn't ACK" error while trying to access with sdk

Somebody please help me out of my misery. I followed the rooting directions to the letter, but when I type "adb devices" I get the following error:
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
I'm in the right directory ( AndroidSDK\tools\ ), I have the android driver installed, I have USB debugging checked, I don't understand why this is not working.
Please help me out here.
I had no problem rooting my palm pre, which was infinately more complicated than this.
Thank you in advance.
flaav8r said:
Somebody please help me out of my misery. I followed the rooting directions to the letter, but when I type "adb devices" I get the following error:
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
I'm in the right directory ( AndroidSDK\tools\ ), I have the android driver installed, I have USB debugging checked, I don't understand why this is not working.
Please help me out here.
I had no problem rooting my palm pre, which was infinately more complicated than this.
Thank you in advance.
Click to expand...
Click to collapse
had a pre and "rooted" it as well..... using putty is more complicated that this but this is a little more like hacking... whereas on the pre you are just accessing root rather than breaking into it.
anyway... try these
nstall htc sync from htc's website, can you sync?
run cmd as administrator
cd untill you are in the same directory as your adb
type "adb devices"
does it display your hero?
type "adb shell"
does is display "$" ?
johnsongrantr said:
had a pre and "rooted" it as well..... using putty is more complicated that this but this is a little more like hacking... whereas on the pre you are just accessing root rather than breaking into it.
anyway... try these
nstall htc sync from htc's website, can you sync?
run cmd as administrator
cd untill you are in the same directory as your adb
type "adb devices"
does it display your hero?
type "adb shell"
does is display "$" ?
Click to expand...
Click to collapse
Yes, I can sync with HTC Sync. When I do the adb devices I get the error I described above and I cannot do adb shell because I cannot communicate via android sdk.
flaav8r said:
Yes, I can sync with HTC Sync. When I do the adb devices I get the error I described above and I cannot do adb shell because I cannot communicate via android sdk.
Click to expand...
Click to collapse
windows 7? VISTA? XP?
restart phone/computer
unplug/plugin usb
also find another copy of adb.exe i heard there's a old copy floating out there that doesn't reccognize the hero for some reason but if you got it from a guide you shouldn't have a problem.
download sprint RUU and wipe your phone (if it will connect) also if you want to dig down the ruu has a working adb.exe twisted into their install they dump in your %TEMP% folder
johnsongrantr said:
windows 7? VISTA? XP?
restart phone/computer
unplug/plugin usb
also find another copy of adb.exe i heard there's a old copy floating out there that doesn't reccognize the hero for some reason but if you got it from a guide you shouldn't have a problem.
download sprint RUU and wipe your phone (if it will connect) also if you want to dig down the ruu has a working adb.exe twisted into their install they dump in your %TEMP% folder
Click to expand...
Click to collapse
Windows XP, and I got the files from this site and androidsdk from the google site linked from theunlockr.com.
flaav8r said:
Windows XP, and I got the files from this site and androidsdk from the google site linked from theunlockr.com.
Click to expand...
Click to collapse
try this known good version
http://forum.xda-developers.com/attachment.php?attachmentid=244916&stc=1&d=1257827184
johnsongrantr said:
try this known good version
http://forum.xda-developers.com/attachment.php?attachmentid=244916&stc=1&d=1257827184
Click to expand...
Click to collapse
I tried the new files, and still got the exact same error.
well i'm out of ideas.... and i'm tired.... anyone else throw a little help this guy's way?
if by tomorrow you/they haven't figured it out I'll see if I can't think of something else for ya
johnsongrantr said:
well i'm out of ideas.... and i'm tired.... anyone else throw a little help this guy's way?
if by tomorrow you/they haven't figured it out I'll see if I can't think of something else for ya
Click to expand...
Click to collapse
Thank you for your help. Greatly appreciated.
The ADB server binds and listen to port 5037. If that port is taken and/or if the daemon is already running, you'll see that error message.
Start task manager and kill adb.exe (all the instances of it).
If that don't work, try rebooting your computer and your phone, and trying again.
If it still don't work, try this:
http://groups.google.com/group/android-developers/msg/dfae5da4a3c80aa8
simplyphp said:
The ADB server binds and listen to port 5037. If that port is taken and/or if the daemon is already running, you'll see that error message.
Start task manager and kill adb.exe (all the instances of it).
If that don't work, try rebooting your computer and your phone, and trying again.
If it still don't work, try this:
http://groups.google.com/group/android-developers/msg/dfae5da4a3c80aa8
Click to expand...
Click to collapse
I'm gonna give it a shot right now.
simplyphp said:
The ADB server binds and listen to port 5037. If that port is taken and/or if the daemon is already running, you'll see that error message.
Start task manager and kill adb.exe (all the instances of it).
If that don't work, try rebooting your computer and your phone, and trying again.
If it still don't work, try this:
http://groups.google.com/group/android-developers/msg/dfae5da4a3c80aa8
Click to expand...
Click to collapse
Haha, success. I'm gonna try and root it now.
Thank you so much.
flaav8r said:
Haha, success. I'm gonna try and root it now.
Thank you so much.
Click to expand...
Click to collapse
Np glad to help
simplyphp said:
Np glad to help
Click to expand...
Click to collapse
Sucussfully rooted, thanks again.
Sorry for reviving an ancient post, but I just wanted to say that I ran into the same issue and opening up "taskmgr" and killing the active instance of "adb.exe" resolved the issue.
Just for help :
I had the same issue and it was my Firewall which blocked the starting of deamon.
Turn off your Firewall can fix the problem
cheers guys, followed the instructions and flashed rec. radio
This solved it for me: edit adb_usb.ini
This solved it for me:
Edit ~/.android/adb_usb.ini file to make sure that there is no extra empty line after the 0x0006 line entry
For other users: I also found this:
After killing ADB.exe run netstat (just "netstat", no parameters) and
see if port 5037 is opened. It probably will be. Wait a while. Run
netstat again, now there are less connections on the port. After a
port 5037 is no longer opened. Only then it's OK to run ADB again.
Please note that this worked for when I killed the ADB.exe process &
process tree from Sysintenal's Process Explorer.
Also, I still don't know why running ADB again before all connection
are closed led to the port never being freed (albeit netstat didn't
show any open connections anymore). Moreover, the problem that forced
me to kill ADB in the first place needs to be solved and there's
enough on that in the forum.
AsafR.
Click to expand...
Click to collapse
Problem is HTC Sync
lucbloom said:
This solved it for me:
Edit ~/.android/adb_usb.ini file to make sure that there is no extra empty line after the 0x0006 line entry
For other users: I also found this:
Click to expand...
Click to collapse
HTC Sync Manager has adb.exe at location C:\Program Files\htc\htc sync manager\htc sync\adb.exe
You have 2 options now:-
1) Delete this adb.exe
2) Copy latest adb.exe from android sdk to this path.
Note: You need to make the 2 copies of adb.exe in sync always(when android sdk is updated) else this problem will come up again.
On windows 7, you can make a link of adb.exe from android sdk to this folder, which will avoid copying manually.
C:\> cd "C:\Program Files\htc\htc sync manager\htc sync"
C:\Program Files\htc\htc sync manager\htc sync\> mklink adb.exe C:\<path to your sdk>\platform-tools\adb.exe
kill htc sync
nevermind someone already posted

Setting up ADB? Windows 7

im trying to set up a adb so i can use my g1 as a webcam:
http://forum.xda-developers.com/showpost.php?p=4975656&postcount=17
however when i plug in my g1 it says everything was installed except the adb.
Do you have ADB setup on your computer in the first place? If not, http://forum.xda-developers.com/showthread.php?t=532719.
I installed the adb with the sdk as it was mentioned and my computer still doesnt show my phone as an adb device
Did you install the drivers for adb?
i cant find out how!
85Mario85 said:
i cant find out how!
Click to expand...
Click to collapse
a little search and VOILA!!!
http://forum.xda-developers.com/showthread.php?t=446274&highlight=64bit+usb
this works if you are running windoze 7 x64
i dont get how im supposed to put windows 7 on test mode =S
im getting this aswel "When running the command prompt adb install I receive an error dialog stating:
"This application has failed to start because AdbWinApi.dll was not found. Re-installing the application may fix this problem.""
im getting so frustrrated with thiss
bump! i dont get this =[
Search for pdanet and install it. That's how I set up adb for Windows. (Btw - get rid of Windows. Finally did my switch to ubuntu today - ahahahahahahaha I'm sad I ever even used Windows.)
Yea, but adb is kind of a ***** about permissions and such on ubuntu. But each has its quarks.
@85mario85 - You have to cd to the adb.exe in the tools folder ie. c:\sdk\tools\ then run adb. Or add it to the paths part, but I can't remember at the moment.
evilkorn said:
Yea, but adb is kind of a ***** about permissions and such on ubuntu. But each has its quarks.
@85mario85 - You have to cd to the adb.exe in the tools folder ie. c:\sdk\tools\ then run adb. Or add it to the paths part, but I can't remember at the moment.
Click to expand...
Click to collapse
adding it to the path just saves time. instead of having to cd all the time you can just run adb. i highly suggest it. and i agree - ubuntu is a ***** about permissions all the time. i love it, but i have to learn to use it. however, i'll probably always have a copy of windows in case i can't find out how to do something and have to have it done. better safe than sorry. =]

ADB HELP

I have tried every process I can find in the forum regarding rooting and ADB but I cannot seem to figure this out. I would like to think that I am computer literate and that I know my way around pretty well but somehow this escapes me. I am running Windows 7 64 bit and can't seem to get anything right as far as this process goes.
Is there a rooting/adb for dummies section that someone can point me to?
the sticky wiki for guides at the top of the front page....
try to look around a little before starting new threads.
beyondinferno said:
the sticky wiki for guides at the top of the front page....
try to look around a little before starting new threads.
Click to expand...
Click to collapse
Thanks for your help...I did look around but I still can't get it to work. I've been through quite a few threads. I don't know if I'm missing something somewhere or what.
is your problem your computer not seeing the phone?
i RUU'd my phone earlier today to test out something i did, but then i found out that adb couldn't connect anymore. i'm still trying to figure it out.
Exactly what are ya having problems with?
http://forum.xda-developers.com/showthread.php?t=502010
1. HTC Sync installed?
2. Android SDK downloaded?
3. Debugging enabled on the phone?
4. is ADB showing up in the Device manager?
5. Check this thread out dealing with x64 drivers
http://forum.xda-developers.com/showthread.php?t=560962
Hmmm..
I have Win7 64bit too
I think I just downloaded the newest Android SDK and HtcSync for the Eris. It
works fine for me. What exactly is the issue? You have the phone in debug mode or whatever mode right?
some folks have used PdaNet
http://www.junefabrics.com/android/download.php
first off, I can't get Sync to work at all no matter which version I've tried. Then the drivers won't load for sdk. it just seems like nothing is working together at all.
alright, i figured it out.
uninstall HTC Sync and the HTC Drivers.
reinstall.
done.
justinisyoung said:
alright, i figured it out.
uninstall HTC Sync and the HTC Drivers.
reinstall.
done.
Click to expand...
Click to collapse
yeah just make sure you use the newest HTC Sync for the Eris!
just out of curiosity why the eris? am i going to have issues later down the road?
DanWalker said:
I have tried every process I can find in the forum regarding rooting and ADB but I cannot seem to figure this out. I would like to think that I am computer literate and that I know my way around pretty well but somehow this escapes me. I am running Windows 7 64 bit and can't seem to get anything right as far as this process goes.
Is there a rooting/adb for dummies section that someone can point me to?
Click to expand...
Click to collapse
Alright... what's your main problem? Are you not able to get the ADB driver to work with your phone in Windows 7 64 bit -- if so, do know that it is possible, because I have it working fine on my computer (Win 7 64B).
If ADB driver situation is your problem, do as follows:
1. Download the file below (to desktop for easy access - This is the Vista 64 bit Drivers)
2. Unzip
3. Go to Device Manager
4. Find ADB (It should come up as ADB with a Yellow Exclamation mark next to it)
5. Right click on it, choose update driver
6. When it asks you to auto find the driver or browse for the driver -- choose BROWSE.
7. Set the path to where you downloaded the file, and then click next.
8. If done correctly, you should see a window pop up that says "Successfully installed My HTC driver".
ADB will work after that is complete. To test, open CMD - go to androidsdk\tools folder, and then run adb devices (If serial # appears, there you have it).
Also with the method above, this will allow the HTC Sync application to work as well.
Source: ME, tested extensively and more than once.
DanWalker said:
just out of curiosity why the eris? am i going to have issues later down the road?
Click to expand...
Click to collapse
HTC Sync for the Hero was released before Win7, so the Vista drivers will work but you have to jump through some hoops.
Now the Eris version is the same HTC Sync but it has drivers for Windows 7, it is the same software but is bundled with newer drivers.
Roger that guys, thanks for the help. I will attempt tonight when I get back to my computer.
Ok just got home and am doing the suggested things, after installing the SDK it wants me to install packages and when I choose cancel, windows says the program was not installed correctly. what do i need to install?!
Also no ADB in device manager!
yeah they took out the packages of the SDK, so you have to add them in as needed.
I have a 2nd Win7 box that's an Android virgin, I will try and run through the install tonight(off at 5pm PST)when I get home and I'll document the install.
hang in there.
rlaxton said:
yeah they took out the packages of the SDK, so you have to add them in as needed.
I have a 2nd Win7 box that's an Android virgin, I will try and run through the install tonight(off at 5pm PST)when I get home and I'll document the install.
hang in there.
Click to expand...
Click to collapse
That would be awesome, I'm at the point where I am just about to give up. I have never been so frustrated with a computer. This is the first Windows 7 system I have done anything with and I already don't like it.
DanWalker said:
Ok just got home and am doing the suggested things, after installing the SDK it wants me to install packages and when I choose cancel, windows says the program was not installed correctly. what do i need to install?!
Also no ADB in device manager!
Click to expand...
Click to collapse
Install packages? What? Weird, the Android SDK is natively 32 bit, but will work in Windows 7 64 BIT (That's what I'm running now).
Alright, steps to take:
1. Uninstall/remove everything you did before.
2. Grab the Windows Android SDK -- download it (to the desktop is fine)
3. UNZIP/Extract the SDK
4. Drag the Android SDK to the root of your drive (Local Disk C: )
5. For easy access purposes, RENAME the Android SDK from what you see to something like: androidsdk
6. Open Command Prompt
7. Verify that you can get to the "androidsdk" directory by running the command: cd androidsdk\tools
8. If you can get there -- then good, so far.
9. Now to test "adb" -- Have your phone connected to the PC.
10. While still in command prompt and STILL in the c:\androidsdk\tools: dir... run command: adb devices
11. This should return your Serial #
12. If your serial # shows up, then make sure you can run the command adb shell and see if you get the # sign, which indicates that you are rooted -- If not, then you need to begin the process of rooting your phone.
Also, if ADB doesn't work after this point, do what I told you earlier, I can guarantee that it does work, because I actually did it this morning on my work computer (Which is Windows 7 64 Bit).
Good luck, report back.
Holy crap it looks like it worked!! Thanks Pseudo! Now if I could only get my damn phone to find Sync I'd be all set.
Still can't get sync to register with phone but that's no biggie. But have a small issue that I dunno where to look to find an answer. I'm trying to update my recovery from 1.5.2 to 1.6.2 and can't seem to follow the directions appropriately.
via adb -> Requires a custom recovery (with test-keys)
Code:
Copy recovery-RA-heroc-v1.6.2.img to the root of your sdcard
Boot into your current custom recovery (boot while holding HOME)
Connect your Hero via usb to your pc/mac/...
adb shell
$su (not required if you have root already)
#mount -a
#flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2.img
None of that seems to work lol.
So since we're on the subject does anyone know how to set up the drivers for linux mint kde? I'm brand new to linux and I've managed to do some things but that is just one thing that i cant do so far and after almost a day pf searching this forum and others i just cant seem to get it
DanWalker said:
Holy crap it looks like it worked!! Thanks Pseudo! Now if I could only get my damn phone to find Sync I'd be all set.
Still can't get sync to register with phone but that's no biggie. But have a small issue that I dunno where to look to find an answer.
Click to expand...
Click to collapse
First off, no problem for the help -- glad it worked. What ROM are you currently running, that would be helpful in solving your sync issue.
DanWalker said:
I'm trying to update my recovery from 1.5.2 to 1.6.2 and can't seem to follow the directions appropriately.
Click to expand...
Click to collapse
Alright, lets begin - To upgrade to RA 1.6.2, (You have to be in recovery mode (Home + Power) -- and also have your phone connected to the PC). Then do as follows:
1. Download the 1.6.2 file
2. Copy or move it to your androidsdk\tools folder
3. Run commands below:
Code:
adb push recovery-RA-heroc-v1.6.2.img /sdcard
Code:
C:\AndroidSDK\tools>adb shell
Code:
mount -a
You'll probably get the next line below -- that's okay.
Code:
mount: mounting /dev/block/mmcblk0p2 on /system/sd failed: No such file or directory
Keep going...
Code:
flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2.img
After you do this, the shell should return #, if it does, then run:
Code:
reboot recovery
Now verify that your recovery says 1.6.2.
Good luck.
thatguythatdid said:
So since we're on the subject does anyone know how to set up the drivers for linux mint kde? I'm brand new to linux and I've managed to do some things but that is just one thing that i cant do so far and after almost a day pf searching this forum and others i just cant seem to get it
Click to expand...
Click to collapse
Well, since you've asked a good question, I shall direct you in the right direction. Linux Mint is a derivative of Ubuntu, so this guide should work for you., however do note that I have not tested this in Linux Mint, as I currently run Ubuntu 9.10, but you should be okay.
Go HERE and bookmark this page for reference, it has some good stuff -- Now this guide is not directly for our phones (CDMA HERO), however the directions, if followed correctly... DO WORK and have been tested by me (did this last night) with successful results.
When you get to the web page, start at "Generic Linux Instructions". Also, when you get to the heading "Set up ubuntu to recognize your phone, and the adb/fastboot commands in the terminal" -- step 4 will ask you to create an empty file, use the Ubuntu 9.10 format and NOT the older versions, again this format should work in the latest version of Linux Mint.
Hope that helps. Also, if have problems or want a step by step tutorial (pending how "new" to Linux you are), just ask me or PM me, I'll write one up.

[Q] N1 ADB & Fastboot for Ubuntu 10.04

I didn't really know where to put this question, but since it involves my Nexus One I put it here. I put Ubuntu 10.04 on a old Compaq V2000 laptop that I resurrected from the dead, and it's running beautifully. I spend more time on my Ubuntu machine then my new Toshiba/w/ W7. Anyway I need things working like I have on my Toshiba. I set up ADB after getting bits and pieces of information here and there, I just could never get fastboot to work for my N1, except when I'm in fastboot and I plug in my usb it changes from fastboot to fastboot usb, so it's recognized in fastboot, well sorta. But, when I run fastboot devices the terminal just hangs on >>waiting for device<<. Now I have another problem, adb works just fine, but yesterday I used it and where the number of your devices appears is blank now, no number shows up, but I can still run commands. I've done just about everything and I'm at a loss here. Some real help here, no snide remarks, and no [email protected], I need dev help or someone familiar with Ubuntu 10.04, or if you've had this problem lend some help. Once again I already have adb setup, but my number isn't showing anymore, and I need fastboot working, and yes I gave it executable permissions, I exported my path, I created my android rules, I edited my .bashrc file. Thanks much in advance. Long Live Linux!!!!!!
I'm good, found a executable script that solved my problem.
I think you just had to sudo adb. It's always polite to post what you did to fix a problem that way someone can search and find the answer, not just a question that says fixed.
Read Read Read!!!!!!!!!!
evilkorn said:
I think you just had to sudo adb. It's always polite to post what you did to fix a problem that way someone can search and find the answer, not just a question that says fixed.
Click to expand...
Click to collapse
I said in my post that I used a executable script, I mean thats all you should need to know. I read about it somewhere, that's all I needed to know, and I found it on my own. They have nuff post on how to setup your adb, but none are 100%, so you have to take bits and pieces from them, and kinda wing it from there. I don't sudo adb on my system, sudo adb =can't be found. It would be senseles to have to type sudo every time you wanted to run adb, I have my to autostart as root as soon as I run adb. If someone needed help all they have to do is ask. Since this post I've had to re-install ubuntu 3 times and I've gotten my adb & fastboot working with the same method I used the first time. I have my adb setup where I can push and pull from any directory, so I don't fill up my tools directory with too many files, and so I don't have to move files, I can just push & pull to & from anywhere.
Perhaps you can share the script you found?
Dude, chill out. The guides are fine and 100%. I don't need to know ****, I know how to setup adb. How the hell is someone going to find that script when you didn't link it.
First, you have to tell sudo where to look for adb, you obviously didn't link it init.d or some other way to tell the software what to do with adb. You have to do 'sudo /home/name/sdk/tools'.
google query: somewhere executable script ubuntu adb
rm -r -f /
Hope this helps
prettyboy85712 said:
Perhaps you can share the script you found?
Click to expand...
Click to collapse
Here's the links, the script isn't mine to give, and I think that would be against the rules. Go to the first link to get the installer, and the next one to get the fastboot exe. I would follow the instructions in the second link. Once you finish that, run the adb script, If nothing pops out of the script when it starts to run , run it again, or try running (in terminal) command. If you need detailed instructions PM me, it's a little process, you have to edit some files.
http://www.droidforums.net/forum/hacking-help/38186-linux-sdk-adb-autoinstaller-script.html
http://forum.xda-developers.com/showthread.php?t=537508
Good for you.

ADB Help

Okay. After looking around, I couldn't find much but here's my dilemma. I got a new laptop and wanted to start Modding my phone like how I can with my desktop and my older laptop. For me to get into ADB shell all I did was copy ADB and adbwinapi.dll to C:\windows\system32. I did the same for my new laptop, but when I launch ADB shell I get an error saying that I a missing the adbwinapi.dll file. Is there a solution for me to get my new laptop to Modding my phone? :3
Please and thank you!
Sent from my SGH-I897 using XDA App
Make sure C:\Windows\System32 is in your path.
Does this involve going into control panel, system, advanced settings, and environment variables?
(If you were talking about the command line in dos, then I still get the "missing AdbWinApi.dll" message.)

Categories

Resources