Database Users

ugh

hey guys has anyone else had problems doing the first step with the android SDK. I always fail during when in CMD after I do the AndroidSDK/tools/ adb devices
i get the error of
** daemon still not runningerror: cannot connect to daemon

Did you run it with admin rights?

how would open cmd with admin rights? all I know is search cmd

ok ran cmd with admin rights now my new error is
ABD server didn't ACK
*failed to start daemon*

BrianDigital said:
ok ran cmd with admin rights now my new error is
ABD server didn't ACK
*failed to start daemon*
Click to expand...
Click to collapse
I am assuming you are using Windows. If so, did you install the driver?

chuckhriczko said:
I am assuming you are using Windows. If so, did you install the driver?
Click to expand...
Click to collapse
its odd, I was following the unlocker setup, and no the drivers didn't install on their own.
I used the USBDeview program, I didn't even have any htc drivers installed so after I just went to devices in windows and uninstalled all the drivers there. I then was able to install a driver for the dream and thats where I am at now.

BrianDigital said:
its odd, I was following the unlocker setup, and no the drivers didn't install on their own.
I used the USBDeview program, I didn't even have any htc drivers installed so after I just went to devices in windows and uninstalled all the drivers there. I then was able to install a driver for the dream and thats where I am at now.
Click to expand...
Click to collapse
Ok. Well there are a couple guides here for doing it, I dont know if they will help but it can't hurt to read them anyway. If the driver is installed properly from the ANdroid SDK then you should be able to adb no problem. Also make sure you go to settings->Applications and make sure USB Debugging is on. That must be on for adb to work.

yep thats done too, Maybe a hard reset would help?

ok well nothing guess i cannot root, super

got it did on my girls 32 bit win7 and it worked

cool but I cant do anything from comp

Using the RUU Issues

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....

[Q] Can't install win usb drivers on XP. Tried everything

I've used different guides, searched to death, but cannot seem to get the driver installed on this XP computer. Some of the guides seem to be for Vista or Windows 7. Is there a good video for XP, or one that relates to the driver issue?

xp is a good choice for this because you don't have to care about the uac (user access control)
maybe this one helps:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6

I was in the same boat as you but luckly i had a netbook with windows 7 starter that worked for me. I couldn't find any help for XP either.
Sent from my Kindle Fire using xda premium

Unfortunately, that did not work for me. I'm fairly computer savvy, but this has stumped me. I will keep looking.

I was getting rather upset because I could get the USB drivers installed, but ADB still wouldn't recognize my Fire.
Is this the problem you guys are having? Or can you just not get the drivers to install at all?
It turned out that my problem was a complete, "I'm an Idiot!" deal. Especially because I'm a System Engineer and should know better than to overlook the steps I did. But, in very few of the instructions of how to load the drivers, does it tell you where the adb_usb.ini file needs to be located. I was thrown off because with the Kindle Fire Utility (ver. 0.9.3 at least), it comes located in the drivers folder. Plus, just about every time this file was mentioned, it always had a big thing about adding the 0x1949 device ID, which caused me to miss the couple times I ran across instructions that said where it needs to be located.
The adb_usb.ini needs to be, in XP, located in the ".android" folder that is located in your username's folder. For example, if I am logged into my computer as PBFred, the path would be the following...
C:\Documents and Settings\PBFred\.android
I also ran into one other problem. When you manually select the path for the driver, android_winusb.inf, (which you can place where ever you want) XP shows you a list of compatible device drivers. The correct device driver, "Android Composite ADB Interface", isn't listed unless you uncheck the box that says "show compatible devices only". If you don't uncheck that box, it just lists "Android ADB Interface", which is not the right one.
Once I did that, I was good to go. The only issue I have now with the driver is for no apparent reason, it asks for the driver to be reinstalled about half the time I plug my Fire in, even though I haven't plugged any other devices in inbetween. But since the path to the driver is still saved, it only takes 2 seconds.
I hope this helps you guys out.

I did these things that you've mentioned. I've gotten to the point of "rooting..."
And nothing happens...but I feel like I've gotten further than before. I will keep working at it.
I'm using the method from rootkindlefire.com
Any other suggestions to try?
And thanks for the suggestions.

DukeSilver79 said:
I did these things that you've mentioned. I've gotten to the point of "rooting..."
And nothing happens...but I feel like I've gotten further than before. I will keep working at it.
I'm using the method from rootkindlefire.com
Any other suggestions to try?
And thanks for the suggestions.
Click to expand...
Click to collapse
I don't quite follow where you are stuck.
Does running the command "adb devices" list your device? If so, your USB drivers are installed correctly. Which means that the version of Windows you are running pretty much doesn't matter any more.

[Q] Developing Processing on Oppo Find 5 on Windows 8

Hey everybody,
I got my Oppo since 3 days now and I am very satified with it. But this morning I was trying to connect the device via USB to continue developing an app in Processing and the IDE didn't find my device. The IDE is waiting for the device to become available and that's it.
After this, I tried the universal adb drivers, the usb drivers of the SDK and the usb drivers of the pdanet app. Nothing worked for me so far. In the device manager the device is listed as "Android ADB Device", so it should be working, right? I am working on Windows 8 on my laptop right now and I think this is where the evil comes from
Any Processing developers here, which got Processing working with their Oppo??
Greetings
digga_mies

I use windows 8 on my PC, but OPPO is recognized when plugged in. I'm pretty sure my correct drivers were installed when I connected the phone.
sent from my Find 5 using Tapatalk 4 Beta

Coreym said:
I use windows 8 on my PC, but OPPO is recognized when plugged in. I'm pretty sure my correct drivers were installed when I connected the phone.
sent from my Find 5 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Okay, and what drivers did you use? The stock drivers of Win 8? Or do you have downloaded others?
I don't know if it helps, but I have installed the stock firmware X909EN_12.A.09_GLO_009_130514

digga_mies said:
Okay, and what drivers did you use? The stock drivers of Win 8? Or do you have downloaded others?
I don't know if it helps, but I have installed the stock firmware X909EN_12.A.09_GLO_009_130514
Click to expand...
Click to collapse
I remember having some issues trying to get Casual to work as it wasn't seeing my phone. I'm pretty sure I used this reference to get everything working correctly.. Install Drivers for any Android

Okay, tried it again with pdanet and got no success again. Even the platform tools adb.exe doesn't recognize my phone as an adb device. I'm getting a little bit frustrated right now.
By the way, I tested it on Windows 7 and it doesn't work either.
Anyone got another idea?

digga_mies said:
Okay, tried it again with pdanet and got no success again. Even the platform tools adb.exe doesn't recognize my phone as an adb device. I'm getting a little bit frustrated right now.
By the way, I tested it on Windows 7 and it doesn't work either.
Anyone got another idea?
Click to expand...
Click to collapse
Try wireless adb, and connect manually to your phone via command line (something like: adb connect YOURIP). I pretty much use only wireless adb (as I do tend to develop stuff that relies a lot on the 9 DOF sensors...) Cheers.

I got it. My device was shown in the device manager all the time as adb device, but the Processing IDE didn't found it. In the Oppo forums is the same error described with eclipse.
The solution was, to change the adb_usb.ini in "C:\Users\YOURUSER\.android". In my file wasn't any entry and I simply added "0x22D9". That's it! Worked for Windows 7 and 8.
:victory::victory:

digga_mies said:
I got it. My device was shown in the device manager all the time as adb device, but the Processing IDE didn't found it. In the Oppo forums is the same error described with eclipse.
The solution was, to change the adb_usb.ini in "C:\Users\YOURUSER\.android". In my file wasn't any entry and I simply added "0x22D9". That's it! Worked for Windows 7 and 8.
:victory::victory:
Click to expand...
Click to collapse
I dont understand what you mean adb_usb.ini
can you make a guide?

digga_mies said:
I got it. My device was shown in the device manager all the time as adb device, but the Processing IDE didn't found it. In the Oppo forums is the same error described with eclipse.
The solution was, to change the adb_usb.ini in "C:\Users\YOURUSER\.android". In my file wasn't any entry and I simply added "0x22D9". That's it! Worked for Windows 7 and 8.
:victory::victory:
Click to expand...
Click to collapse
Thanks for the device code!

Oneplus 5 ADB

Can someone guide me how to get ADB working on OnePlus 5?

stalvekio said:
Can someone guide me how to get ADB working on OnePlus 5?
Click to expand...
Click to collapse
i'm using 'block this!'

What's the problem about it?
download android platform tools or minimal adb and fastboot, make sure drivers are installed and activate ADB Debugging in Developer Options

colin.pohle said:
What's the problem about it?
download android platform tools or minimal adb and fastboot, make sure drivers are installed and activate ADB Debugging in Developer Options
Click to expand...
Click to collapse
I have tried all of those. All i get is emty list. It cant detect my phone.
Probably i havent found the right drivers

stalvekio said:
I have tried all of those. All i get is emty list. It cant detect my phone.
Probably i havent found the right drivers
Click to expand...
Click to collapse
Try these.

I had driver issue for side loading even after Installing OnePlus drivers windows wanted to use standard ADB drivers

Download the Android SDK kit first. Then plug in your OP5 to your PC and you should see something called "CD Drive (F: ) OnePlus Drivers". Click on it and it will install the OP5 drivers. Then enable developer options on your phone, by hitting the build number 7 times. Then go into developer settings and enable USD debugging. After that, go to the Android SDK folder and go to tools/platform tools, then hold shift and right click and open a command/powershell window and type adb devices. After that you should receive a fingerprint notification on your phone so just say yes to it. Ten type in adb devices again in the command/powershell window and it should be able to detect your device. I said everything from scratch so I hope it sort of helps!

What exactly do you want to accomplish. Because I just flashed everything on my phone. When the phone was running normal ADB was not recognized in my phone. However when I was in bootloader mode I got to unlock my bootloader and flash TWRP.

ddaharu said:
What exactly do you want to accomplish. Because I just flashed everything on my phone. When the phone was running normal ADB was not recognized in my phone. However when I was in bootloader mode I got to unlock my bootloader and flash TWRP.
Click to expand...
Click to collapse
Adb still somehow has to work... The drivers are there (although all my win 10 devices installed the correct ones automatically) and it doesn't even really matter which adb he is using

shadowstep said:
Try these.
Click to expand...
Click to collapse
I tried. Device manager still shows adb interface yellow.
d0nsman said:
Download the Android SDK kit first. Then plug in your OP5 to your PC and you should see something called "CD Drive (F: ) OnePlus Drivers". Click on it and it will install the OP5 drivers. Then enable developer options on your phone, by hitting the build number 7 times. Then go into developer settings and enable USD debugging. After that, go to the Android SDK folder and go to tools/platform tools, then hold shift and right click and open a command/powershell window and type adb devices. After that you should receive a fingerprint notification on your phone so just say yes to it. Ten type in adb devices again in the command/powershell window and it should be able to detect your device. I said everything from scratch so I hope it sort of helps!
Click to expand...
Click to collapse
I did that. ADB devices gives me empty list.

stalvekio said:
I tried. Device manager still shows adb interface yellow.
Click to expand...
Click to collapse
Do you have Windows? If yes, what version? With 10, I know they work a 100% for sure. With 7, after installing these, there is still a yellow exclamation mark in Device Manager. To resolve that, right click on the device in Device Manager, uninstall the driver. Then, reconnect the device after enabling USB Debugging, and then let windows download the required drivers from Windows Update. It should be ~8.5 MB. Once it's downloaded and installed automatically, you should be good to go.

shadowstep said:
Do you have Windows? If yes, what version? With 10, I know they work a 100% for sure. With 7, after installing these, there is still a yellow exclamation mark in Device Manager. To resolve that, right click on the device in Device Manager, uninstall the driver. Then, reconnect the device after enabling USB Debugging, and then let windows download the required drivers from Windows Update. It should be ~8.5 MB. Once it's downloaded and installed automatically, you should be good to go.
Click to expand...
Click to collapse
win 8.1.
Did as you sugsested but no change .... adb interface is yellow

stalvekio said:
win 8.1. Did as you sugsested but no change .... adb interface is yellow
Click to expand...
Click to collapse
Stop using the worst windows ever! Jokes apart, try using the these or these. I had them installed before, and they worked fine, in Windows 7 & 10 at least. Good luck! :good:

shadowstep said:
Stop using the worst windows ever! Jokes apart, try using the these or these. I had them installed before, and they worked fine, in Windows 7 & 10 at least. Good luck! :good:
Click to expand...
Click to collapse
Nope. No help.
I think it´s something very easy i have missed

Finaly - got it working.
This guide helped:
http://www.asunsoft.com/android/how-to-manually-install-usb-driver-for-android-phone.html