Develop Bugs

[Q] Adb is not recognized as an intern or extern command

Hi, so i'm very new to Android and while attempting to do the gfree permaroot for my desire Z, i came across a problem. When I type the commands, it says that adb is not and intern or extern command. I have adb file in platform-tools (400ko). When i open it, it make a cmd screen for about 2 seconds then shuts down. Can someone help me with this problem
I just installed HTC sync and my computer cannot find any device attached. It says: the htc vision htc port does not repons.
Thanks
Vince

are you doing CD C:/location of adb/adb?
You must direct your command line to the directory of adb.
also run cmd as administrator if you're on vista or win7.
If you're not a command line pro I suggest you just rename your folder to whatever you want in C:/folderhere
For example heres the folder renamed to "android"
then just do CD C:/android
Then type "adb" and hit enter
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and boom! you're in adb!
Hope this helps
I'm no adb pro but I'm ok at cmd. Maybe I should make a video or something on the basics to getting adb running if there isn't one already?

Thanks for the quick reply! It helped me figure out that you need to open adb before using the adb command but the same error occurs (is not an intern/extern command) when i try it

Vincethedevil said:
Thanks for the quick reply! It helped me figure out that you need to open adb before using the adb command but the same error occurs (is not an intern/extern command) when i try it
Click to expand...
Click to collapse
Nah, you still aren't getting it
How did you install ADB? If you search in Windows for the file "adb.exe" what does it tell you?

it's in the platform tools folder in the sdk

Vincethedevil said:
Thanks for the quick reply! It helped me figure out that you need to open adb before using the adb command but the same error occurs (is not an intern/extern command) when i try it
Click to expand...
Click to collapse
I'm not quite sure what you mean by this, I wonder if you're doing something wrong. Have you followed this guide ? http://forum.xda-developers.com/showthread.php?t=865685
If you have added the correct folders to your path, as explained in the guide, it should find adb ok.
If it's finding adb ok, then if you run "adb devices", is that not showing your phone ? Are you using the original HTC cable to connect to your phone ? Third-party ones sometimes will not work.

Yeah i'm using the original Htc cable. I have downloaded Htc Sync and it appears as "my htc" in device manager. Although, Htc sync doesn't recognize any plugged in phone.
For adb, i go in cmd, change the path with cd to the path where is the adb.exe, then type adb. A series of text follow. Then, i switch to the folder where is gfree (with cd) and type the first line for temp root. That when it says that adb is not recognized as an intern or extern command

Since adb.exe is not located in your gfree directory, it's not a recognized command. You either need to run the commands directly from your platform tools directory (and use the full directory paths for the gfree commands) or place the path for adb in your environment variables so that adb can be called from any directory (step four in the ADB for noobies linked earlier). This is the easier method.

I tried it but it's not working. I'll take pictures tomorrow so my obvious noob error can be spotted

Adding adb to your path
Hey there,
Here's a quick guide to fix your problem (basically, you don't have adb added to your path). Btw, this guide was made on Windows 7, but the principle should be the same for Vista and XP (though the steps are different).
Step 1: Right click "Computer" or "My Computer"
Step 2: On the left side find "Advanced system settings" and click it.
Step 3: On the Advanced tab, click "Environment variables"
Step 4: In the bottom part of the window, scroll until you find the row that starts with "Path" and click "Edit"
Step 5: At the end of the existing line, add a semicolon ( ; ) and the path to your android toolkit. If the path contains spaces, don't forget to enclose it in quote marks ( "C:\path to adb\tools\" )

Vincethedevil said:
For adb, i go in cmd, change the path with cd to the path where is the adb.exe, then type adb. A series of text follow. Then, i switch to the folder where is gfree (with cd) and type the first line for temp root. That when it says that adb is not recognized as an intern or extern command
Click to expand...
Click to collapse
You haven't set the Path up so that it can find adb, as has been said, and that's all covered in the guide that I previously linked to. But the previous poster has provided you with an excellent step-by-step solution.

Thanks alot, my adb problem is now solved! I just have one more question, when i plug my phone, htc sync cannot recognize it. Although, when i write adb devices in cmd, my phone appear. Am I still gonna be able to permaroot or should i mess with the drivers.
Thx
Vince

It's not a driver problem, it's an HTC Sync problem. Your phone has to be in Sync mode and you have to wait a few minutes (mine takes up to 20 mins) for HTC Sync to recognize it.

sounds like you'll be able to root just fine if it recognizes and responds to adb.
Not sure about htc sync, I don't even know what that is...lol

not able to root
i am using this procedure
http://forum.xda-developers.com/showthread.php?t=1601038
as i am running runme.bat i am getting this screen please help

Need to set up adb, there are tons of guides on xda and the web to do this properly, follow one of them and then try your whatever you're doing again
Sent from my Nexus 7 using xda premium

demkantor said:
Need to set up adb, there are tons of guides on xda and the web to do this properly, follow one of them and then try your whatever you're doing again
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
thanx for reply/..
not able to to set up adb.. please help if you can
should i uninstall existing drivers and again install it

You may need to reinstall drivers but first make sure you have the right ones as well as adb.exe download from the sdk or whereever you get it
See the third post. In this thread
http://forum.xda-developers.com/showthread.php?p=31899577
If you're still having issues let me know and ill help ya
Sent from my MyTouch 4G Slide using xda premium

[ROOT][ONE-CLICK][UPDATED 11-30-11] Get ADB running AND Root with SuperOneClick

So I was messing around with different one clicks since I got ADB going on my kindle fire and I was able to Successfully use SuperOneClick 2.2 to root my kindle fire!
Sorry for the mess. Its late, and I wanted to type this up so I could crash...
To get adb going you must download the android sdk (google it).
*Run SDKManager.exe and download the google-usb_drivers package from "3rd party tools"
* Download platform-tools as well
Open a command prompt and run adb update usb to get the .android folder to appear.
goto: %USERPROFILE%\.android and edit the adb_usb.ini and add this to the end of the file and save:
Code:
0x1949
then go into where you have the sdk at and open the google-usb_driver folder and edit android_winusb.inf and add this to the [Google.NTx86] section and [Google.NTamd64] section:
Code:
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
save and close
If you have already plugged your kindle into the usb you may have to open device manager and find "Kindle" under other devices and choose the android_winusb.inf file.
Turn on Installation of apps from unknown sources: tap the top bar>choose more...(+)>device
open a command prompt and run adb kill-server then try adb devices..
you should see a device listed.
go here: http://forum.xda-developers.com/showthread.php?t=803682a
download and run SuperOneClick and choose the "root" option. let it go!
Enjoy!
Proof:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Awesome!

Why do I have a mac

That was quick. I wonder if Amazon prefers the device to be rootable or not? Normal Kindle is quite easy to root too.

soundslikemitch said:
Why do I have a mac
Click to expand...
Click to collapse
^^ now THAT is funny ^^

Magnesus said:
That was quick. I wonder if Amazon prefers the device to be rootable or not? Normal Kindle is quite easy to root too.
Click to expand...
Click to collapse
Supposedly it was supposed to be easy to root. So I would think so. I am sure amazon could have made it a lot harder if they wanted to.

aimbdd said:
Supposedly it was supposed to be easy to root. So I would think so. I am sure amazon could have made it a lot harder if they wanted to.
Click to expand...
Click to collapse
I almost suspect from their coy comments (yes, it will be rooted, no we don't care, type of thing) That they're just after market share, period. Now let's bring on CM ICS! (impatient optimist in me, sorry!)

My question is can anyone get TTS to work?

soundslikemitch said:
Why do I have a mac
Click to expand...
Click to collapse
I lawl'd
* * *
Amazon said they wouldn't get in the way of root.

wow, this was quick! i hope we get custom gingerbread and later on ICS roms quick

Rooted Fire
Death2All - Rooting instructions worked like a champ!
Thanks for posting.
Donation to Shortfuse OTW.
Kind regards

Worked Beautifully!
Success!
My Kindle Fire is rooted and happily working with ADB.
Now lets get some dev-action love going on here . Thanks.

Good work
hey so can we now get the Amazon VOD app on our android phones with this root? If So...How do we do it?

soundslikemitch said:
Why do I have a mac
Click to expand...
Click to collapse
You could do it manually using the zergRush exploit, SuperOneClick just makes it easier for Windows people.
zergRush exploit: http://forum.xda-developers.com/showthread.php?t=1296916
(Usage instructions are there, it's fairly simple - push the binary to device with adb, chmod binary and then execute binary. this gives temp root, push su and busybox binaries for perm root and install superuser.apk)
[This replaces the SuperOneClick part of the original post, you still need to do everything leading up to that (editing adb_usb.ini etc.) - some parts may be changed slightly for mac/linux e.g. I would assume you need to edit a different file than "android_winusb.inf"]
EDIT: Guide for getting ADB working on Mac: http://blog.actlocalmedia.com/2011/11/developing-on-kindle-fire.html (probably applicable to Linux too). Do this, then you can manually root via ADB and zergRush.

Did rooting break video on demand playback for anyone else? When i go to watch a prime instant video now the play buttons are greyed out, and my device is "no longer configured correctly to play Amazon videos.

death2all110 said:
<snip> To get adb going you must already have the sdk on your machine and used it. <snip>
Click to expand...
Click to collapse
Never used it, but I have it installed. I don't even know where to begin

mipakr said:
Never used it, but I have it installed. I don't even know where to begin
Click to expand...
Click to collapse
to get the adb_usb file to show up, you can go into the tools directory of the sdk, open a command prompt and run android update adb - thatll at least create the file, then you just edit it as the directions state.

abremel said:
Did rooting break video on demand playback for anyone else? When i go to watch a prime instant video now the play buttons are greyed out, and my device is "no longer configured correctly to play Amazon videos.
Click to expand...
Click to collapse
Ditto for me. I called customer service, they claim to be looking into it. Debating whether to do factory reset and see what happens.
Sent from my ADR6300 using xda premium

smtom said:
Ditto for me. I called customer service, they claim to be looking into it. Debating whether to do factory reset and see what happens.
Sent from my ADR6300 using xda premium
Click to expand...
Click to collapse
Actually an easy fix - the unroot button on superoneclick unroots it, and a reboot restores video playback - the instant video app must have some sort of check in place to see if the device is rooted.

abremel said:
to get the adb_usb file to show up, you can go into the tools directory of the sdk, open a command prompt and run android update adb - thatll at least create the file, then you just edit it as the directions state.
Click to expand...
Click to collapse
You also need to install the Google USB driver via the SDK Manager I think to generate the other files that need editing.

[Resolved] ADB No Longer Working on Android 4.2.2? - Update your ADB!

4.2.2 now enforces RSA authentication via ADB. This is only supported in later versions of ADB.
On Windows, you can see your local user profile folder's .android folder and see if there's a file called 'adbkey'.
Or use 'adb version' to see if you have the latest version. ADB version 1.0.31 is working.
Google just added this in the ADB protocol last November, so you need the NEWEST ADB:
https://github.com/android/platform_system_core/commit/d5fcafaf41f8ec90986c813f75ec78402096af2d
The keys for your hosts are stored at /data/misc/adb/adb_keys, I believe.
If your ADB works correctly, you will see this when you plug in for the first time. You may still have to reseat your cable.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(Pic credit to rickbosch)
* * *
This will not affect all of you.
But on the stock Android 4.2.2 kernel from Google, I cannot get adb to work (always shows 'adb offline') on the stock kernel. This is with my laptop (a Lenovo Thinkpad), and I never had issues with this before with the same setup.
My current workaround is to use a custom kernel for 4.2.2 (thanks to renaud for delivering)
A custom Fugumod kernel that works with 4.2.2 and does not have this issue with ADB:
http://forum.xda-developers.com/showpost.php?p=37892325&postcount=2167
Stable builds (future?):
http://fugumod.org/galaxy_nexus/stable-4.2.2/
Please report back with the PC/Mac and possibly the cable you are using, thanks.

In default.prop is new line!
That is ro.adb.secure=1 or something like that, I think this is the issue! changing it to 0 may let you to use ADB!
I gonna test it out in 5 minutes.

It'll ask you to give ADB permission if you're all set up correctly. Mine did...Seems it's a whitelist system now where you can allow or not allow individual PCs to use ADB on your device.

manumanfred said:
In default.prop is new line!
That is ro.adb.secure=1 or something like that, I think this is the issue! changing it to 0 may let you to use ADB!
I gonna test it out in 5 minutes.
Click to expand...
Click to collapse
That's default.
I resolved my issue swapping my kernel, not the ramdisk (that's where default.prop is in anyway). Hm...
rickbosch said:
It'll ask you to give ADB permission if you're all set up correctly. Mine did...Seems it's a whitelist system now where you can allow or not allow individual PCs to use ADB on your device.
Click to expand...
Click to collapse
This never came up for me . Didn't wipe though.
How do you manage devices?

I'm using 4.2.2 and I didn't got that popup!
I extracted boot.img and made it to insecure and changed adb secure line from 1 to 0 and now I can use ADB!

neither did I. Just flashed via TWRP over stock Takju 4.2.1
edit: And about managing devices, I have no idea.

You shouldn't have to make ro.adb.secure=0 default. I think something is definitely wrong with this OTA lol.
Or maybe this is a new feature. Was the screenshot taken with Linux? How the heck do I get a RSA key with ADB on Windows?

xaueious said:
Or maybe this is a new feature. Was the screenshot taken with Linux? How the heck do I get a RSA key with ADB on Windows?
Click to expand...
Click to collapse
Screenshot was taken on my phone, and about RSA key and ADB on Windows, I'm afraid I can't answer those for you.

xaueious said:
You shouldn't have to make ro.adb.secure=0 default. I think something is definitely wrong with this OTA lol.
Or maybe this is a new feature. Was the screenshot taken with Linux? How the heck do I get a RSA key with ADB on Windows?
Click to expand...
Click to collapse
Why not!
It lets to use ADB then, now I can use ADB without any issues, before editing default.prop I wasn't able to use ADB!

This is probably a new feature of some sort. Linux works fine, Windows doesn't. Mac probably works too.

Windows works fine for me. Maybe you changed something somewhere. I had 0 problems.

Never changed anything on the phone. Fixed the issue though. I was using an older version of ADB: 1.0.31
Older versions don't support key RSA authentication.

I also had this problem.
Then I deleted some spare copy of adb.exe and its dlls that where installed under \windows\ by some "do-it-all" tool and updated the adb tools with SDK-Manager.
After connecting to the PC, my GNexus asked for confirmation before allowing USB debugging and since then everything is fine :victory:

I updated android sdk tools on my mac today (before that I couldn't launch abd sideload update.zip) and haven't noticed any issues with adb/fastboot commands.

AH, so it's the outdated ADB drivers playing up, perhaps good to mention in OP as a solution.

For me with stock kernel adb and fastboot ok.
I'm using bigxie rom deodex.

rickbosch said:
AH, so it's the outdated ADB drivers playing up, perhaps good to mention in OP as a solution.
Click to expand...
Click to collapse
Done

It may seem obvious for some, but wasn't for me.
I flashed the upgrade, with the cable always connected then couldn't get adb to work. Just need to re-plug the cable for the prompt to show up

Is this new version in the latest Android SDK? If not, where can you get it from?

EddyOS said:
Is this new version in the latest Android SDK? If not, where can you get it from?
Click to expand...
Click to collapse
Yes, it is in the new SDK.
On a side note, OP, the image you used and credited in the first post was mine, not manumanfred's.

[Tool]i9505 Quick Flasher

Now next to the i9500 Quick Flasher there also is the i9505 Quick Flasher, just slight changes to make partitions match
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download:
www.broodplank.net/I9505-Quick-Flasher-1.0.zip
Created for a fail-safe flash operation of boot.img and recovery.img, all other partitions (currently only system) are experimental.

broodplank1337 said:
Now next to the i9500 Quick Flasher there also is the i9505 Quick Flasher, just slight changes to make partitions match
Download:
www.broodplank.net/I9505-Quick-Flasher-1.0.zip
Created for a fail-safe flash operation of boot.img and recovery.img, all other partitions (currently only system) are experimental.
Click to expand...
Click to collapse
Tried this, it cannot connect to my S4. Yes, I have debugging enabled, and yes my device is in mtp mode.
I get:
Running checks, please wait...
<<< I9505 USB Connection >>>
[ ] I9505 USB Connection
Your I9505 is not connected or unreachable! Please read the instructions for reference.

Snakefood said:
Tried this, it cannot connect to my S4. Yes, I have debugging enabled, and yes my device is in mtp mode.
I get:
Running checks, please wait...
<<< I9505 USB Connection >>>
[ ] I9505 USB Connection
Your I9505 is not connected or unreachable! Please read the instructions for reference.
Click to expand...
Click to collapse
I had some issues with usb as well when I was testing the tool out, but It was fixed after a while, its actually not the tool but the way of mounting usb on the i9505. I fixed it by replacing the adb.exe file with the latest one (which is also included in the zip tho). Can you please test for me if your able to get a normal adb shell? (open cmd window in the quickflasher dir and type "adb shell"), if it says device not found there is an issue with debugging mode. if not then you should test this and pls give me the info:
adb get-state (should return "device")
adb devices (should return a connected device)
If you get negative results here you should kill adb.exe (taskkill /f /im adb.exe for group kill) and try again.
If it does work pls enter:
adb root
adb remount
adb shell
and tel me what you see.
The usb mode is a struggle on the i9505.. I thought hey lets upgrade to CM so I will have mass storage mode.. but no way, only MTP and PTP... (I added the Mass storage option and forced it to be available on my private build, but it still doesn't work..)
Currently trying to find out how to permanently enable oldskool mass storage + adb.

broodplank1337 said:
I had some issues with usb as well when I was testing the tool out, but It was fixed after a while, its actually not the tool but the way of mounting usb on the i9505. I fixed it by replacing the adb.exe file with the latest one (which is also included in the zip tho). Can you please test for me if your able to get a normal adb shell? (open cmd window in the quickflasher dir and type "adb shell"), if it says device not found there is an issue with debugging mode. if not then you should test this and pls give me the info:
adb get-state (should return "device")
adb devices (should return a connected device)
If you get negative results here you should kill adb.exe (taskkill /f /im adb.exe for group kill) and try again.
If it does work pls enter:
adb root
adb remount
adb shell
and tel me what you see.
The usb mode is a struggle on the i9505.. I thought hey lets upgrade to CM so I will have mass storage mode.. but no way, only MTP and PTP... (I added the Mass storage option and forced it to be available on my private build, but it still doesn't work..)
Currently trying to find out how to permanently enable oldskool mass storage + adb.
Click to expand...
Click to collapse
My results:
C:\Windows\system32>cd \
C:\>cd s4 root
C:\S4 root>cd qflash
C:\S4 root\qflash>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: more than one device and emulator
C:\S4 root\qflash>adb get-state
unknown
C:\S4 root\qflash>adb devices
List of devices attached
12138fc0 device
emulator-5554 offline
C:\S4 root\qflash>adb root
error: more than one device and emulator
C:\S4 root\qflash>

Snakefood said:
My results:
C:\Windows\system32>cd \
C:\>cd s4 root
C:\S4 root>cd qflash
C:\S4 root\qflash>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: more than one device and emulator
C:\S4 root\qflash>adb get-state
unknown
C:\S4 root\qflash>adb devices
List of devices attached
12138fc0 device
emulator-5554 offline
C:\S4 root\qflash>adb root
error: more than one device and emulator
C:\S4 root\qflash>
Click to expand...
Click to collapse
ah so you have the emulator in there as well.. thats the problem. to bypass the emulator use:
adb -d
for example adb -d shell or adb -d get-state
do you have an AVD emulator running currently?

broodplank1337 said:
ah so you have the emulator in there as well.. thats the problem. to bypass the emulator use:
adb -d
for example adb -d shell or adb -d get-state
do you have an AVD emulator running currently?
Click to expand...
Click to collapse
What emulator do I have, I've only used the files in your download, as far as I know. Any way to check / remove?
Edit: I had bluestacks installed a while back, but uninstalled it, could this have left some crap behind after it?

Snakefood said:
What emulator do I have, I've only used the files in your download, as far as I know. Any way to check / remove?
Click to expand...
Click to collapse
Hmm the emulator that comes with android sdk, is afaik the only one who can correspond with adb, but it would be odd if you ran it all the time.
check taskmgr, and look for emulator.exe/java.exe, to be sure also kill adb.
You can check if there is an existing emulator if you start AVD manager (if you don't have android sdk at all then its really strange )

broodplank1337 said:
Hmm the emulator that comes with android sdk, is afaik the only one who can correspond with adb, but it would be odd if you ran it all the time.
check taskmgr, and look for emulator.exe/java.exe, to be sure also kill adb.
You can check if there is an existing emulator if you start AVD manager (if you don't have android sdk at all then its really strange )
Click to expand...
Click to collapse
I didn't have sdk installed; I installed it and ran avd manager, doesn't show any installed.
when I run adb -d shell I get [email protected]:/ $

Snakefood said:
I didn't have sdk installed; I installed it and ran avd manager, doesn't show any installed.
when I run adb -d shell I get [email protected]:/ $
Click to expand...
Click to collapse
Ok the output is good. ill add a function to the tool to force adb usb connection
for the meanwhile you can use:
(put boot.img in adb dir)
adb -d push boot.img /sdcard/boot.img
adb -d shell su -c 'dd if=/sdcard/boot.img of=/dev/block/mmcblk0p20'
adb -d shell reboot

broodplank1337 said:
Ok the output is good. ill add a function to the tool to force adb usb connection
for the meanwhile you can use:
(put boot.img in adb dir)
adb -d push boot.img /sdcard/boot.img
adb -d shell su -c 'dd if=/sdcard/boot.img of=/dev/block/mmcblk0p20'
adb -d shell reboot
Click to expand...
Click to collapse
Do I rename my recovery.img from cwm to boot.img for the above, or is this for a different process?

Snakefood said:
Do I rename my recovery.img from cwm to boot.img for the above, or is this for a different process?
Click to expand...
Click to collapse
boot.img = mmcblk0p20
recovery.img = mmcblk0p21
the name of the .img doesn't matter but the partition is important.

Ahh, looking at your image, this now makes sense, I can see the destination partition names as you describe..
Well have a go at this later, unless you plan to release an update later today?
Sent from my Nexus 7 using xda app-developers app
Edit: couldn't get this working, so I just flashed using odin. Thanks for trying to get resolved tho.

Odin is the tool for me, no need more than that.

broodplank1337 said:
ah so you have the emulator in there as well.. thats the problem. to bypass the emulator use:
adb -d
for example adb -d shell or adb -d get-state
do you have an AVD emulator running currently?
Click to expand...
Click to collapse
Hi brood,
just stumbled upon this thread and read about Snakefood's problem.
Although he worked around the error by using Odin I want to give you a hint regarding this specific problem:
he obviously has an adb device installed called emulator-5554 but which is offline. He already gave himself the correct answer:
"I had bluestacks installed a while back, but uninstalled it, could this have left some crap behind after it?"
My diagnose is: yes, BlueStacks definitely leaves a lot of crap behind and does NOT uninstall cleanly. I tested it once and I saw myself compelled to restore an older windows image which I made BEFORE I installed BlueStacks on my windows machine.
BTW: BlueStacks is an Android emulator for Windows but a piece of *%$~#!!! crap, but that's just my humble opinion.
And BlueStacks uses such an adb emulator device entry although I'm not sure if it was called like that. But BlueStacks is not the only Android emulator and most probably other programs of this kind create such an adb entry as well.

skywalker01 said:
Hi brood,
just stumbled upon this thread and read about Snakefood's problem.
Although he worked around the error by using Odin I want to give you a hint regarding this specific problem:
he obviously has an adb device installed called emulator-5554 but which is offline. He already gave himself the correct answer:
"I had bluestacks installed a while back, but uninstalled it, could this have left some crap behind after it?"
My diagnose is: yes, BlueStacks definitely leaves a lot of crap behind and does NOT uninstall cleanly. I tested it once and I saw myself compelled to restore an older windows image which I made BEFORE I installed BlueStacks on my windows machine.
BTW: BlueStacks is an Android emulator for Windows but a piece of *%$~#!!! crap, but that's just my humble opinion.
And BlueStacks uses such an adb emulator device entry although I'm not sure if it was called like that. But BlueStacks is not the only Android emulator and most probably other programs of this kind create such an adb entry as well.
Click to expand...
Click to collapse
Hi Skywalker.
Long time no see . Anyways, OT. I have installed BlueStacks once (in the alpha or beta phase I believe) and I don't remember much of it but I do remember that it was crap idd. Also that it leaves "traces" (if you call adb a trace xd, more like a fail uninstall ) is very lame.. and causing problems for people who are not 100% familiar with adb and its daemon.
The AVD Emulator from the SDK may lag a bit but atleast it doesn't interfere with adb :silly:

Great tool broodplank1337, well done mate this will save ppl from making stupid mistakes

dublinz said:
Great tool broodplank1337, well done mate this will save ppl from making stupid mistakes
Click to expand...
Click to collapse
Thanks ^^, I think that is true hehe, using 'dd' to flash images isn't for the absolute beginner idd ;p

Hi guys,
If you need me to assist more with ahh testing just let me know. Is there an uninstaller to remove what bluestacks left behind, or is the Windows disc the only definite uninstaller
Sent from my GT-I9505 using xda app-developers app

Snakefood said:
Hi guys,
If you need me to assist more with ahh testing just let me know. Is there an uninstaller to remove what bluestacks left behind, or is the Windows disc the only definite uninstaller
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
You should first look in msconfig (start > run > msconfig) at the startup tab and look if there is any startup item from bluestacks.
If there is nothing there look in services.msc (start > run > services.msc) and check for any blue stacks service, and if there is any, disable it.
Next to that you can also use HijackThis (http://sourceforge.net/projects/hjt/) to find startup items. hope it helps

Hey Brood,
See you're doing great work here on the S4 section.:good:
I'm missing your input in the S+ section unfortunatly:crying:

[Q] Can't figure out how to flash CWM via Mac OS X

Hello everyone, I have an OUYA and I really want to get CyanogenMod on it. The first step is obviously CWM. I have tried flashing via this method http://forum.xda-developers.com/showthread.php?t=2295645 on my Windows 7 PC, I get the error message "no device found" every time, tried numerous drivers, nothing worked. So I decided to try it out on my Mac. Well its still not working. I run the .sh file and nothing happens.
My question is, how do I do this?
Im kinda new to terminal on Mac OS X, and I've barely used it in Linux, so I think I need some help here :/ I hope someone has advice.
Thanks

Orange_furball said:
Hello everyone, I have an OUYA and I really want to get CyanogenMod on it. The first step is obviously CWM. I have tried flashing via this method http://forum.xda-developers.com/showthread.php?t=2295645 on my Windows 7 PC, I get the error message "no device found" every time, tried numerous drivers, nothing worked. So I decided to try it out on my Mac. Well its still not working. I run the .sh file and nothing happens.
My question is, how do I do this?
Im kinda new to terminal on Mac OS X, and I've barely used it in Linux, so I think I need some help here :/ I hope someone has advice.
Thanks
Click to expand...
Click to collapse
hmm,
On my MBP the script worked,
Did you navigated to the folder with the terminal ? (i'm also not a terminal hero ) and run the script ?. with Osx the "dir" fuction is "ls" so you can see the folders. Navigate to the specific MacOSX folder and with the Ouya and your MAc connected, type ./adb devices (with the ./). It should give you a line with "List of devices attached " and the line below that a long number that stands for your ouya.
Sometimes i had to do this twice or three times for the ouya to show up. If the ouya showes up. Then run type ./InstallOuyaCWMRecovery.sh (with the ./). It should work that way.
Greetz,
Michel

Re-Mi said:
hmm,
On my MBP the script worked,
Did you navigated to the folder with the terminal ? (i'm also not a terminal hero ) and run the script ?. with Osx the "dir" fuction is "ls" so you can see the folders. Navigate to the specific MacOSX folder and with the Ouya and your MAc connected, type ./adb devices (with the ./). It should give you a line with "List of devices attached " and the line below that a long number that stands for your ouya.
Sometimes i had to do this twice or three times for the ouya to show up. If the ouya showes up. Then run type ./InstallOuyaCWMRecovery.sh (with the ./). It should work that way.
Greetz,
Michel
Click to expand...
Click to collapse
I think I'm royally failing. I can't even access my downloads directory and ./adb devices renders no results
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ps: I'm not Paul.. The guy I bought this Mac off of left his info and I never took the time to take t off..

Orange_furball said:
I think I'm royally failing. I can't even access my downloads directory and ./adb devices renders no results
Click to expand...
Click to collapse
ok when first entering the terminal type
Code:
cd \
(then enter, you will see a > enter again)
then type
Code:
ls
( its an L )
you can scroll up but i'm pretty sure there is a folder "Downloads" to get into this folder you have to type (just like windows)
Code:
cd Downloads
As i'm not a terminal hero also i type everything Cap sensitive (this way i know it works)
do the "ls" and "cd" commands until you reach the downloaded folder and you are into the MacOSX folder, then do the
Code:
./adb devices
and if you mac sees the ouya then run the bash file

Re-Mi said:
ok when first entering the terminal type
Code:
cd \
(then enter, you will see a > enter again)
then type
Code:
ls
( its an L )
you can scroll up but i'm pretty sure there is a folder "Downloads" to get into this folder you have to type (just like windows)
Code:
cd Downloads
As i'm not a terminal hero also i type everything Cap sensitive (this way i know it works)
do the "ls" and "cd" commands until you reach the downloaded folder and you are into the MacOSX folder, then do the
Code:
./adb devices
and if you mac sees the ouya then run the bash file
Click to expand...
Click to collapse
I feel like I'm so close! Thank you! But my Mac doesn't see the OUYA in devices attached :/

Orange_furball said:
I feel like I'm so close! Thank you! But my Mac doesn't see the OUYA in devices attached :/
Click to expand...
Click to collapse
I pm-ed you.

Re-Mi has helped me solved my issue! Thank you so much!

Here is more detail on what I did, First of all I followed Re-Mi's instructions. Here they are:
So first things first Root
http://forum.xda-developers.com/show....php?t=2387507
Sideload the app and run the apk
second install the xposed installer (latest apk file at the end of the first post) make sure it's installed (Launch the Xposed Installer and click on "Install/Update" ,Reboot ,Done!)
http://forum.xda-developers.com/show....php?t=1574401
Then install mod collection for Ouya and install CWM from there
http://forum.xda-developers.com/show....php?t=2359390
It's a long detour but i think it will work. After that just install stockplus rom and you got everything you wanted (otherwise you would not even bother to install cwm )
Click to expand...
Click to collapse
Now let me go into more detail. What you do is type the first link into your OUYA's web browser (It is under Make>Software>Web Browser I believe) Then download the file. Now go to Manage>Settings>Advanced>Storage>Downloads and hit the file you just downloaded. Install that APK, hit open, then hit root. Now accept the SU request. After this is done repeat the steps until you have the other file downloaded. Now install that APK for the Xposed Installer and hit "Install/Update" then reboot. Now download the mod collection from the third link.
Install it and install CWM from there. It will take you to a download link, wait a few seconds, then hit install CWM again. Now it'll be installed.
Plug your Ouya into your computer, If its a Mac you will need the program from www.android.com/filetransfer . If its Windows you wont need that. Go in XDA and download whatever ROM tickles your fancy. Drag and drop that into your Ouya's storage. Now on the Ouya reboot to recovery (Via the Mods app)
Now im CWM hit the install zip from SD card, select the .zip of the ROM you chose, and install. Now wait until its all done, reboot, and enjoy!
*IF YOUR OUYA GETS BRICKED, NEITHER I NOR RE-MI NOR ANYONE EXCEPT YOURSELF ARE RESPONSIBLE!*
Good luck! If this helps be sure to thank Re-Mi!!!