ok so im trying to emulate my phone onto my PC windows 7...
heres the line im putting in...
emulator -avd MyDevicesName
and here the error im getting
emulator: ERROR: unknown virtual device name: 'MyDeviceName
emulator: could not find virtual device named 'MyDevicesName'
droidgenius said:
ok so im trying to emulate my phone onto my PC windows 7...
heres the line im putting in...
emulator -avd MyDevicesName
and here the error im getting
emulator: ERROR: unknown virtual device name: 'MyDeviceName
emulator: could not find virtual device named 'MyDevicesName'
Click to expand...
Click to collapse
Try asking.this in the general q&a I think you'll have better luck there
There is an emulator built into the SDK and Eclipse.
Related
i downloaded the sdk and i downloaded a samsung galaxy driver and when i look for my phone in the command line it just doesnt show up. theunlockt just isnt helping. anybody got a good link for dummies?
antonio91282 said:
i downloaded the sdk and i downloaded a samsung galaxy driver and when i look for my phone in the command line it just doesnt show up. theunlockt just isnt helping. anybody got a good link for dummies?
Click to expand...
Click to collapse
Did you put your phone in debug? Settings>Applications>Development
yes. and i been going over the directions repeatedly on theunlockr. im running xp 32 i believe
ADB for Dummies: Download http://de.codeplex.com/
- Once installed... open command prompt:
cd C:\Program Files\Droid Explorer\SDK\tools
Click to expand...
Click to collapse
- <type your ADB command here> e.g.
adb shell
Click to expand...
Click to collapse
^ yeah...
adb devices
Click to expand...
Click to collapse
should show your device...
To the OP, I don't know if this is the case for you but I changed my path on my Windows PC like the guides said to and that didnt completely work. (Maybe neede a restart). But in any case if you go to the command prompt, change directories to were you have adb and run your commands from there, it works like a charm.
For example if you unzip the the SDK in your download directory, open up the command line and type:
cd C:\Documents and Settings\<your user name>\Downloads\<whatever-you-named-the-unzipped-folder>\tools
ADB is in the tools directory you just went to. From here you can run the adb command without having to set up the system paths. This is a quick and dirty explanantion and might not even work for you. I was running this on Windows XP when I had this problem. Same thing had to be done on my Ubuntu Linux box b/c I'm to lazy to set up paths on that one, lol.
zephiK said:
ADB for Dummies: Download http://de.codeplex.com/
- Once installed... open command prompt:
- <type your ADB command here> e.g.
Click to expand...
Click to collapse
Oops, didnt see that you allready posted this. Yea do what zephiK says and it should work.
i have not been able to get adb to work no matter what i did (i am using xp) and i have been trying since i had the htc magic last year. here is how i recently got it working.
i downloaded the one-click root zip file and unzipped it. inside there is a adb.exe file. i clicked it and then then made sure my phone was in debugging mode and connected to my pc and used the command prompt to point to where adb is in my android sdk which for me is cd\androidsdk\tools
adb devices
i hit enter after tools and enter after devices and now it works. not sure why but it does. i couldnt get my magic, my nexus one or even the galaxy to work until i did this.
i got everything done. i think? only problem is im getting $ sign instead of # sign. any ideas?
i got adb working. thanks everyone.
A thread success story without any casualties. Almost makes me weep.
im using windows 7 64bit and trying to learn adb and cmd
i was watch how to install adb and following..
after installing adb and drivers and added adb on system variables
i type cmd and then typed C:\android-sdk-windows\platform-tools
after that i typed adb devices but got an error
C:\android-sdk-windows\platform-tools\adb.exe is not a valid Win32 application.
what do i have to do here?? T.T
If I'm not mistaken in Win7 64, the Android SDK installs ADB to c:\Program Files(x86)\Android\android-sdk\platform-tools\adb.exe
feedhead said:
If I'm not mistaken in Win7 64, the Android SDK installs ADB to c:\Program Files(x86)\Android\android-sdk\platform-tools\adb.exe
Click to expand...
Click to collapse
that is correct. i'm on win 7 x64 and its there.
Type cd then space in front of C:\....
That changes directories.
Sent from my ADR6400L using XDA Premium App
qudwis said:
im using windows 7 64bit and trying to learn adb and cmd
i was watch how to install adb and following..
after installing adb and drivers and added adb on system variables
i type cmd and then typed C:\android-sdk-windows\platform-tools
after that i typed adb devices but got an error
C:\android-sdk-windows\platform-tools\adb.exe is not a valid Win32 application.
what do i have to do here?? T.T
Click to expand...
Click to collapse
First confirm that adb installed where you think it did.
Code:
C:\android-sdk-windows\platform-tools
Hit the start button in Windows and copy and paste your path from above into the Search programs and files box. If the path is valid, Windows Explorer will open to that directory.
If the path is not valid, try typing adb.exe in the search box to see if Windows knows where it is. If it comes up in the search results, right click on it and select "Open file location" and Explorer will open to where it is installed.
Once you have verified where adb is, you should be able to pick up from where you ran into a problem.
I attached the .pdf that I followed when I first installed adb ... I wish I remembered where I got it so I could credit them appropriately. The screen-shots might be helpful to you.
(Note: there is a typo on page 8 where the System Variables are setup paltform should be platform)
Oops the file was too big.
It is zipped and attached to this post.
Edit: I found where I got the document from. http://forum.xda-developers.com/showthread.php?t=1009419
http://forum.xda-developers.com/showthread.php?p=9959449
When I put in the ubuntu, ubuntu, local host and 5900 in the vnc veiwer. I click connect and it gives an error message saying "connection refused"
What am I doing wrong?
Anybody? Im super excited to get ubuntu up and running, but ive been stuck here for 2 days now.
You have opened the terminal emulator, right?
The part where you type in "su" then CD to wherever you put the ubuntu files and start the shell?
If you are using the paid app you might want to contact the dev for support.
Crisis, yes I did that. Then pressed home, then opened up vnc, and typed all that good stuff in.
Hi all,
I searched quite a lot, but seems to me not nearly enough. I've been using adb on my Windows 7 machine for a while now, but would like to have adb at work on my Ubuntu 11.04 machine where I am going to start some boring development.
I have installed the sdk and eclipse and and and (if it is important WHAT I installed more than this, I will elaborate)
lsusb returns
Code:
Bus 002 Device 009: ID 04e8:689e Samsung Electronics Co., Ltd
so I have set my
/etc/udev/rules.d/51-android.rules
to reflect like this:
Code:
SUBSYSTEM=="usb",ATTRS{idVendor}=="04e8",ATTRS{idProduct}=="689e",SYMLINK+="android_adb",MODE="0666
I'm kinda hoping this is wrong and there is an easy fix that I can laugh about.
When I have the emulator running and my phone plugged in
Code:
$sudo adb devices
returns a blank line and something about an emulator, only emulator running yields no blank line and only phone plugged in yields a nice and quiet blank line.
I had this on Windows as well when I struggled with drivers, but the CD sorted it out. I read that the necessary drivers comes with the SDK, but I might be wrong.
I have tried different tutorials and different values for the idProduct and idVendor as some tutorials claim they should be kept constant and not vary per phone... I restarted adb each time I made a change with
Code:
$sudo adb kill-server; sudo adb start-server; sudo adb devices
I'm currently running FirstUA v1.2 if that changes anything.
If you need more info, don't hesitate to ask, I know it's easier to solve problems with the right info (coming from an IT helpdesk).
Digi.Gram said:
Hi all,
I searched quite a lot, but seems to me not nearly enough. I've been using adb on my Windows 7 machine for a while now, but would like to have adb at work on my Ubuntu 11.04 machine where I am going to start some boring development.
I have installed the sdk and eclipse and and and (if it is important WHAT I installed more than this, I will elaborate)
lsusb returns
Code:
Bus 002 Device 009: ID 04e8:689e Samsung Electronics Co., Ltd
so I have set my
/etc/udev/rules.d/51-android.rules
to reflect like this:
Code:
SUBSYSTEM=="usb",ATTRS{idVendor}=="04e8",ATTRS{idProduct}=="689e",SYMLINK+="android_adb",MODE="0666
I'm kinda hoping this is wrong and there is an easy fix that I can laugh about.
When I have the emulator running and my phone plugged in
Code:
$sudo adb devices
returns a blank line and something about an emulator, only emulator running yields no blank line and only phone plugged in yields a nice and quiet blank line.
I had this on Windows as well when I struggled with drivers, but the CD sorted it out. I read that the necessary drivers comes with the SDK, but I might be wrong.
I have tried different tutorials and different values for the idProduct and idVendor as some tutorials claim they should be kept constant and not vary per phone... I restarted adb each time I made a change with
Code:
$sudo adb kill-server; sudo adb start-server; sudo adb devices
I'm currently running FirstUA v1.2 if that changes anything.
If you need more info, don't hesitate to ask, I know it's easier to solve problems with the right info (coming from an IT helpdesk).
Click to expand...
Click to collapse
The SDK Drivers are not for Galaxy Ace , Google for the drivers , they should be easy to find
Sent from my Ultma Weapon using XDA App
It seems that my problem begins with our Proxy server.... As the SDK manager and I had a quarrel about authentication, I downloaded some of the packages directly and forced the manger to use them instead of those on Google. With this, I accidentally downloaded an outdated adb, which had problems specifically with the Galaxy line of phones.... Downloading the correct package now, will see if it works better
Maybe I must just stop before I think of continuing I installed the newer r06 version, and my device is picked up, but now adb shell gives me this:
Code:
:~$ adb devices
List of devices attached
S58300c017faf device
:~$ adb shell
sh: applet not found
Any ideas where to look for the applet? Maybe I must continue tomorrow, new day new ideas.
Do you have Debugging turned on? And is the device rooted with Busybox? I assume yes since you're running a custom ROM but double checking.
If you're having trouble, I'd either: a) run a VM with XP SP3; b) head to the Android Q&A board here.
mmm, I never though of looking at that, since I figured they do say busybox is installed on this ROM, but thanx for nudging me into that direction, I found this post from ketut.kumajaya so I'm looking into that. Had some issues with not abling to get rw access, but my only problem there was a spelling error in the terminal.
I still get the error with the sh: applet not found, even after I tried the advice on that link. I tried installing all 3 versions shipped with BusyBox Installer on all 3 locations, still nothing. Just had an idea I'll try, if you invoke sh in linux you get a new shell, when I invoke sh I get the applet not found error. Maybe I should upgrade my sh or something. Worth a try
I am running a VM for the VB programming I do at work, but that doesn't have USB support (to much trouble to reinstall Virtual Box now just for USB support). Last night I tested on Windows 7 (first time since I started using this ROM) and it failed with the same error. I'm sure it's the sh that's broken or something. Will test on my wife's phone tonight (running the same ROM).
Thanx for your ideas so far. That's what I love about an online community, even if you don't exactly know what's wrong, people sling ideas around that nudge you in the right direction. One error message at a time
Solved thanx to Ketut
Thanx for all your help guys.
I've read lots of the posts here about rooting and I've closely followed the directions, but I'm still having a problem. Also, apologies if I'm posting in the wrong section, but I don't have enough posts for the Dev section, which seems the better destination.
Anyway...I tried both the manual process via ADB and also the one-click method.
In both cases, the problem seems to be that there are two devices running, my Photon (TAxxxxxxBJC) and an emulator (emulator-5554). With the ADB method it appears that I should be able to stop the emulator device via the ADB command, but then the next time I use ADB (for example, to get a list of devices) a Daemon kicks in and restarts the emulator.
I'm pretty sure if I can disable the emulator and keep it disabled that I could root my phone. But even when I stop the emulator and then do the one-click method, the first command restarts the Daemon and the emulator.
Can anyone help me with how to defeat the emulator and keep it from loading during the rooting process? I'm including a screen grab of the feedback from the one-click method to illustrate my issue.
Thanks for any ideas or suggestions...
____________________________________________________
* daemon not running. starting it now *
* daemon started successfully *
Getting temp root
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
RE-boot-en
error: more than one device and emulator
error: more than one device and emulator
Hackin Things
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
deleting all yo
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
Copying files onto phone...
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
Setting permissions...
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
Installing busybox...
error: more than one device and emulator
Cleaning up files...
error: more than one device and emulator
error: more than one device and emulator
"You should have root!"
Press any key to continue . . .
____________________________________________________
Do you have something like blue stacks cloud connect running?
Sent from my MB855 using xda premium
Yes, I did have Blue Stacks running. So, I killed it via Task Manager and then tried to root again. But when I run ADB I'm still seeing both my device and the emulator.
I was previously experimenting with Android Screen Cast, so I checked to see if I could find anything related to that in the running processes but didn't see anything obvious. I'll take a deeper look after sending this note, but any other suggestions that might be causing the eMulator to load?
Thanks for the suggestion and quick reply.
I figured out that I needed to kill the service for Blue Stacks rather than the process. When I did that and then checked the connected devices via ADB it only showed my phone.
Now rooted. One weird thing is that now AndroidScreenCast will not load and I get an "Unable to Load Application" message. Before, I could view my phone screen on my desktop but not interact with it (that required rooting). So, sort of one step forward, one step back.
Thanks very much for the great help.
Have you checked to see if the bluestacks service is running again? (I honestly have no idea what the problem would be; I'm just shooting in the dark.)
Sent from my MB855 using xda premium
In fact, I started Blue Stacks again, because it had been running when Android Screen Cast was working earlier (albeit only in one direction).
So, I just went back and stopped the Blue Stacks service again, and then retried ASC without luck. FWIW, ASC seems to fail during the process of "Getting devices list."
But thanks again for the additional suggestion. You were right on the money with the cause of my not getting rooted, so I'm grateful for that.
Thanks again.
Then don't forget to hit the thanks button please.
Sent from my MB855 using xda premium
Were you able to get rooted?
Yes, or at least I'm pretty sure.
Root Check reports that I'm rooted, but Screenshot produces an error message whenever I try to to take a screenshot and it asks whether I'm rooted. I've also managed to get Android Screen Cast to run again, but it's view-only rather than being able to interact with my phone via my PC screen (rooting required for interactivity)..
On the other hand, Ad Free and My Backup Root seem to be working fine.