hi again. I am a mac osx user and I was trying to install androidscreencast following the steps from http://code.google.com/p/androidscreencast/ , but it doesn't worked for me. can somebody to give some more details? I got this message...
At which step did you get this message? What happens if you click on the "Details" button from your picture?
Perhaps you need Java Web Start.
this error happens to me as well, before running the screencast. You need to make sure "daemon" is running (what ever that is) by simply running an adb command, such as "adb devices"
Related
Hero had a hardware fault w/ the SD slot(good thing too! I dropped it last week and had a bit of rub on the top left that was bothering the hell out of me)
Was going to go get it replaced tonight, but for some damn reason the RUU won't work.
I have the latest RUU(1.56?)
Tried with phone w/ and without USB debugging
Went into fastboot mode(which made W7 install drivers for Android 1.0?) yet the RUU still won't recognize the phone.
I'm not computer illiterate, I'm just having problems with this damn RUU.
Halp?
What's the error you're getting?
The RUU basically says like
"Finding your Android Device" for about 30 seconds then says it cannot find it.
error 170...
ahh we meet again
i've helped a few people through this but i don't want to spoil the fun..
read this
all the way through it has the steps needed to get you up and going.
what os are you running?
just read windows 7..
try right clicking and "run as administrator"
thedudejdog said:
error 170...
ahh we meet again
i've helped a few people through this but i don't want to spoil the fun..
read this
all the way through it has the steps needed to get you up and going.
what os are you running?
just read windows 7..
try right clicking and "run as administrator"
Click to expand...
Click to collapse
I've read this before, I got it from geekfor.me
My windows 7 has the real administrator account enabled, running as administrator won't do anything.
intx said:
I've read this before, I got it from geekfor.me
My windows 7 has the real administrator account enabled, running as administrator won't do anything.
Click to expand...
Click to collapse
ok.
basically my next question is do you want my help or not?
i know how to make it work for you, at least three other people have gotten it to run by following my directions.
thedudejdog said:
ok.
basically my next question is do you want my help or not?
i know how to make it work for you, at least three other people have gotten it to run by following my directions.
Click to expand...
Click to collapse
Why wouldn't I want help?
ok try this.
type "adb devices"
if that sees your phone type reboot into fastboot then type "fastboot devices"
if that sees your phone then run the ruu
adb devices sees it.
boot into fastboot, fastboot devices sees it.
run the RUU, error 170 still >_<
intx said:
adb devices sees it.
boot into fastboot, fastboot devices sees it.
run the RUU, error 170 still >_<
Click to expand...
Click to collapse
have you tried this?
realmrealm said:
For some of the people running into problems with Windows 7 you may want to try:
1. Right-click on the executable file "ARUWizard.exe" and then go to "properties"
2. I believe there is a tab called "Compatibility" or something, click on it.
3. there should be a place for you to click next to a "run this program in compatibility mode" put a check there
4. below that there should be a drop down box, try choosing "Windows XP SP3" (or something similar to that)
5. near the bottom should be a place to check "run as administrator" check that.
6. click "ok" and then try running the program again.
I'm in front of a windows xp computer right now, not windows 7, so excuse me if i don't remember the options correctly, but I should be pretty close.
I also don't even know if this will work, but it's definitely worth a shot.
-AndyS-
Click to expand...
Click to collapse
or this?
10 char...
flipzmode said:
Possible resolutions would be:
1) Putting it in to fast boot and trying it again. Check your error log if it fails and seeing if it identified your phone this time.
2) Open a command prompt and "cd" to the folder where your \sdk\tools\ folder and type in "adb devices" and hit enter and see if it sees your phone. If not then that's your problem. If it DOES see your phone then enter the following command
3) adb shell reboot oem-78 -- that will reboot your phone in to RUU-ready fastboot. If you had the RUU still open then close it. Then open it and try running again.
Click to expand...
Click to collapse
or this?
crunchybutternut said:
Just had a thought.. after updating my HTC Sync software the adb included with my RUU might be out of date. I copied adb.exe, AdbWinApi.dll and fastboot.exe from C:\AndroidSDK\Tools and overwrote the files in the RUU folder. Then I ran it without a hitch.. weird, eh?
Click to expand...
Click to collapse
Tried the first two things, neither helped
I figured out part of the problem though. I had to dig up some 64 bit drivers.
I got the RUU to recognize my phone and it sends it to the bootloader and gets stuck on Waiting for bootloader then errors 170 out.
I'll try copying the files over now.
Replacing those 3 files did the trick!
Thanks
intx said:
Replacing those 3 files did the trick!
Thanks
Click to expand...
Click to collapse
no problem, when i did it i tried all of those steps at once, so i wasn't sure which one fixed it for me. so now (in theory) it should work for you on that machine every time.
wont run and get "ARUGlobal.dll can not be found" even tho im looking right at it....
so i transferred my music from my laptop to my tab, but while looking at my music on the tab it all of a sudden exits and asks me to either force close or report. Anyone have any idea why this could be happening? I thought all was good once i got the files to tranfer, but then this happened...
could you try reproducing the issue with logcat running?
Sure, would you mind explaining how to do that though? Not wuite sure what logcat is... Appreciate all the help! Hope to get this squared away.
yeah, I figured I would have to do that but I hate writing out instructions just to find out that the person already knows everything I had to say.
I'll write this assuming you're using windows.. hopefully that's not a mistake
this may be a lot more work than you're willing to do and it may not give any useful results. you're certainly more than welcome to try it though.
for a much easier, but less helpful method, skip to the end.
first, install the adb driver. there is a link floating around somewhere to just the driver, but I can't find it so you're probably better off just installing samsung kies. this will install the drivers for you.
http://www.samsung.com/ca/support/m...softwaremanual.do?page=MOBILE.SOFTWARE.MANUAL
then, you'll need to download the android sdk.
http://developer.android.com/sdk/index.html
download it, open the sdk manager and then let it install it's stuff. all you really need is "Android SDK Platform-tools, revision X." I believe the most recent revision is 5, but it doesn't really matter.
now, open a command prompt. in windows 7, you can just hit start and then type cmd. in xp or vista I believe if you have to use start->run or windows key + r, then type cmd and click run.
from here, change directory to the platform tools folder of your sdk. most likely something like this
Code:
cd C:\Program Files\android-sdk-windows\platform-tools\
though it will depend on where you installed your sdk
now go into settings->applications->development and check "usb debugging" on your tablet. after that is done, connect it to your computer with usb and type
Code:
adb devices
if something shows up, your device is recognized. otherwise.. ask for help, I guess
finally, type
Code:
adb logcat -c
adb logcat
and then try to reproduce the error. this will give you tons of information about what's going on in the system. hopefully, it will give you some idea why it is crashing.
Note: the "-c" will clear all previous logs
now, for the short version.
In the android market, download "Android Terminal Emulator"
attempt to reproduce the error then open the terminal emulator and type
Code:
logcat &
this will show you all logs since the last reboot, assuming you haven't cleared them with "logcat -c." It might be a good idea to use "logcat -c" before you start trying to reproduce the error.
hope that helps,
Sam
First of all cant thank you enough for trying to help out. So i went with the second option as to limit my chances of having to ask more questions...yeah about that. With option 2 i could not run the "logcat -c" and after reproducing the error and running "logcat &" i get a permission error... Ideas? Thanks again!
hard to say, man.. what does the error say exactly?
I have tried to install KFU v0.9.3, but i get a command message stating that not recognised as an internal or external command. How can i fix this to allow the installation of KFU? I using XP if that helps
Thanks
oh so very vague.... try following the steps carefully 1 by 1 and you'll get it done.
which step are you currently on of the guide your trying to follow, and if you could link to it
Thanks Zothes, the guide im following is this
youtube.com/watch?v=AZ88CYWv0FU
So im pretty much at the first step, where i need to install Kindle Fire Utility to my PC, but the command screen flashes up stating 'and is not recognised...
Apologies for being vague, let me know what other details you require
what is not recognized, which command?
do you have the KFU opened or are you unable to install the drivers?
'and' is not recognised, im unable to install the drivers
i suggest you search through this thread
When I try to flash something via ADB on my computer it doesn't work because I get an error message that multiple terminals are open. I'm not good with command line stuff on the computer and usually figure out a way around it so I can flash what I need to, but the next time I need to flash something I'm in the same boat again with the same error message. Is there a way to close everything that is supposedly running so I don't get that error?
jhs39 said:
When I try to flash something via ADB on my computer it doesn't work because I get an error message that multiple terminals are open. I'm not good with command line stuff on the computer and usually figure out a way around it so I can flash what I need to, but the next time I need to flash something I'm in the same boat again with the same error message. Is there a way to close everything that is supposedly running so I don't get that error?
Click to expand...
Click to collapse
Hello,
What's the output of:
adb devices
Also, can you paste the exact error displayed on the command prompt?
You could try:
adb kill-server
Which kill the adb.exe process
Then:
adb start-server
Cheers...
Updated Android platform tools and when I flashed the latest bootloader didn't get that error again. The update must have cleared up the problem. Hopefully it won't happen again. Is there something you are supposed to do after flashing to ensure that the terminal doesn't rename open in the background in windows?
jhs39 said:
Updated Android platform tools and when I flashed the latest bootloader didn't get that error again. The update must have cleared up the problem. Hopefully it won't happen again. Is there something you are supposed to do after flashing to ensure that the terminal doesn't rename open in the background in windows?
Click to expand...
Click to collapse
Hello,
By "rename" you meant "remain" ?
I don't think so... But you can right click on your windows taskbar and open task manager.
Look at processes and see if ADB.exe is still running. You can also tic:
"Show processes for all users" and see here...
Cheers...
Hello everyone! I'm looking some advice from the wise about bypassing the region restrictions for the Soli Radar (Motion Sense) in my Pixel 4. I am pretty new at running ADB (Android Debug Bridge) from my Windows PC. That said, I'm sure I overlooked something very simple. I can't get the commands to work at all. I followed the XDA YouTube video step by step on how to install and setup the SDK Platform tools on my PC. As well as how to prepare my device to receive commands from my PC. But it fails every time. I'm pretty sure that I'm just running the ADB incorrectly, but I don't know. I have only been able to find instructions on how to install and setup the SDK package. But no clear instructions on how exactly to utilize it. Again, I've never done this before. I am running the latest version on Android 10 on my phone and my PC is running Windows 10. And before running any commands, I verified that the device is in fact attached to the PC by running "adb devices" first. I wish there was an option to attach a screenshot of failure message I'm getting. But it says:
setprop: failed to set property 'pixel.oslo.allowed_override' to 'true'
I get this same failure when I run the alternative command line as well. And I have tried both command prompt and Power Shell and receive the same failure message. Anything advice that can be shot my way would be greatly appreciated. Thanks!
First check the windows 10 device manager to confirm that your device and computer are successfully connected.
Then try to replace with a new data cable, a USB 2.0 cable may be better.
Is the phone bootloader unlocked or have you rooted it yet? Honestly I am not sure if either of those are required for the changes, but I suspect they are. If you haven't rooted the phone yet, then I bet you don't have the correct privileges to make those kind of changes to the phone.