yashsingh1/xdaforums huggingface dataset:
[Ouya Android Development] tennisbgc:
I'm trying to do step 7. I input C:\Android\sdk\platform-tools into comand promt but get not regognizable message. What am I doing wrong?
[Ouya Android Development] tcollum:
You need to open the command prompt from wherever within platform-tools, or navigate to that folder from your command prompt. You can't run the adb command (which is located in platform-tools) unless your in that directory.
[Ouya Android Development] dh4645:
thanks. hopefully i'll get my OUYA soon. only 1 state away.
[Ouya Android Development] tennisbgc:
I dont get a number after adb devices. I editited the google usb file. Im using the 64 version of android sdk is that ok?
[Ouya Android Development] dibblebill:
[MENTION=3641294]tcollum[/MENTION]: Perhaps you should add this to the OP, I tested and it worked. You can add that ;Ouya to the amd64 section of the USB driver, too
[Ouya Android Development] dibblebill:
I just find it easier to ADB over Network and install from my laptop.
[Ouya Android Development] uncynd:
This was a great post...I did what you suggested and selected the latest Samsung ADB Interface driver in the windows list (think it was 23/1//2013) and voila. Thanks!
[Ouya Android Development] dibblebill:
You can also do the original USB driver edit in the OP and add it under the amd64 section in the inf file. Its how I did it.
[Ouya Android Development] uncynd:
Ahh, did not see your post that would have been a lot faster, good advice and maybe should be added to OP?
[Ouya Android Development] dibblebill:
I made that suggestion, too, that it be appended to the OP. I didn't wanna put KIES on my computers.

EDIT: Of course, now that I permanently enabled adb over network, its irrelevant.
[Ouya Android Development] tcollum:
What does putting that under the amd64 section do exactly?
[Ouya Android Development] dibblebill:
I noticed that the driver information and identifiers were identical in both sections. It allows tree driver tweak to function properly on 64 bit Windows 7 installations
[Ouya Android Development] tcollum:
Is that necessary?
[Ouya Android Development] dibblebill:
For the simple Google USB driver tweak to work in Windows 7 x64? Yes. Also necessary if, like me, people don't want to download KIES to their computer to get Samsung's ADB driver.
[Ouya Android Development] DivinityCycle:
Many thanks to OP, this thread made rooting my Ouya easy, and now I have both ADB working over the network AND an SSH / SFTP server running on my Ouya as well. That plus a static IP has made sideloading apps and messing around with the device trivial, and I can easily do that without removing it from my home theater or changing any cabling :)
[Ouya Android Development] tcollum:
I'm on 64bit Windows 7, and didn't need that, or KIES.
[Ouya Android Development] dibblebill:
Interesting. Neither my laptop nor desktop would use the driver until I added that to the 64 section. I have the 64-bit SDK.
[Ouya Android Development] TadeoNYC:
Out of curiosity, when putting the driver in both sections did it install automatically
[Ouya Android Development] tennisbgc:
After rooting the ouya I resently connected it to my pc and it doesnt show up at all under device manager.

Update: I did a factory reset and ouya showed up under mobile device and other device and I was able to have it show up as android adb device but when I run this command

adb kill-server

echo 0x2836 >> "%USERPROFILE%\.android\adb_usb.ini"

adb start-server

adb devices

theres no number after adb devices

Update: got it working
[Ouya Android Development] dibblebill:
Yes. Did the new OTA mess with the adb over network tweak in build.prop for anybody else? The tweak is still there but an adb over network won't connect
[Ouya Android Development] jhitesma:
Ok, something odd seems to have happened to my adb/su and I'm trying to figure out what...

After the last OTA I went to restore SU access and was able to modify the build prop to re-enable wireless adb which is what I prefer since the computer next to my Ouya has a lousy keyboard so I prefer using on in the other room for adb stuff.

I was able to get wireless adb going and can connect - but when I try to 'su' I get 'Permission Denied'.

And when I plug in over USB the Ouya isn't showing up under adb devices anymore (I've tried killing and restarting the adb server.) The Ouya gives a notification that USB debugging is connected, but I can't find it in device manager (I do get the media device connection still.)

So I can't load busybox superuser and the modified su.

Any thought?
[Ouya Android Development] jhitesma:
Apparently I got further than I remember last night after the reset. I was able to install busy box and superuser and they both worked, could also run titanium. So maybe I did get su updated before I fell asleep. But I can't su in the adb shell and still don't see the Ouya when I plug in through USB. Is this normal when using wireless adb?
[Ouya Android Development] tcollum:
In the past I haven't seen the Ouya when I plug it in, after I've enabled adb over wireless. I don't know why you can't get su in the shell, however.
[Ouya Android Development] lovekeiiy:
I had a few issues trying to get Ouya to be seen by ADB. I was having a driver issue. I found a nice YouTube that help me a lot. And just goes over a few more details that the OP does cover, which are more to cover some potential problems

[YOUTUBE]454JFvFTxww[/YOUTUBE]

I found both the OP and what Ouya gave were on the same lines: Setting Up OUYA ODK
[Ouya Android Development] OreBoySwaggin:
Don't Do ADB over network!

I don't want to sound like a n00b but i did adb over network and i couldn't install CWM because in the bootloader i couldn't adb since network adb was default. everytime i'd turn on my ouya ADB over network was on. Caused me to screw up my ouya and return it :( but whatever ill buy a new one later.
[Ouya Android Development] simbaba:
Hi,

I have a problem with this part :

The dos window say that :

What the problem ?

Thanks a lot.
[Ouya Android Development] TadeoNYC:
Those are individual commands. This should be easier to follow

http://xdaforums.com/showthread.php?p=41412675
[Ouya Android Development] Phen0m:
So, I am able to push the su and superbusy/busybox apks, to my Ouya, but The superuser app, always fails to update when I enter it. It states that I should contact the developer. The busybox then states that SU cannot be found, so it also will not run.

I have used rootchecker to check my root status, and it says im ok in that regard.

Any thoughts?
[Ouya Android Development] simbaba:
Thanks but same error when after i write "mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP" :
[Ouya Android Development] professorpoptart:
Your not in the shell as root. After you type "su" in the shell you should get a "#" instead of a "$"... which means su in xbin is messed up... I would restart from step one, and run each step one line at a time.
[Ouya Android Development] simbaba:
Hello,

Thanks for your reply but i don't understand. I repeat the tut :

1. Make sure you have ADB set up and working (wired or wireless). OK

2. Download and unzip the needed files here. OK

3. Place unzipped files in /android-sdk/platform-tools OK

4. Run the following commands to put su in the proper place: NOK
[Ouya Android Development] professorpoptart:
before mounting anything...

type "adb shell" hit enter... no quotes

you should see "$"

type "su" hit enter... no quotes

you should see "#"

does it still say "$"... do you get any feedback like "su not found" or "access denied"?

If su is broke we can always sideload the stock ota rom from the official recovery to get back to square one in case su got messed up somewhere along the line... or as long as it still boot into the system, the next regular ota update should do that for you... they have been doing an update about once a month... so worst case hang on until the update and try the above steps again.
[Ouya Android Development] simbaba:
Thanks but i have never "#", always "$" with su...
[Ouya Android Development] professorpoptart:
So it sounds like su is broke. So I would either

1) boot into recovery and sideload the current ota zip

2) wait for ouya to push out the next one.
[Ouya Android Development] simbaba:
Okay, thanks.
[Ouya Android Development] Phen0m:
How do you boot into recovery on the ouya?
[Ouya Android Development] professorpoptart:
If you can adb, "adb reboot recovery"

If you cant adb, with a usb keyboard plugged into the ouya hit "alt+sysrq+i" 5 to 10 times when its starting up.
[Ouya Android Development] lux209:
I don't kow if it has been posted already but just in case, here is the solution for the windows 8 driver! It is working great:

Windows 8 users: You will need to disable driver signature verification to install the unsigned Android driver. This involves restarting your PC so do this before you start. See the step-by-step instructions here https://devs.ouya.tv/developers/docs/windows8.md

Then just follow the procedure written on the first page.

source: https://devs.ouya.tv/developers/docs/setup
[Ouya Android Development] TadeoNYC:
Can anyone confirm adb reboot recovery still works. I tried to reboot recovery from android tuner and got the "OUYA !" screen. Reboot bootloader turns the OUYA on to a black screen.
[Ouya Android Development] Ouya-XD:
It honestly doesn't seem as if all your files you need to use are in the same directory. That would be first thing.

Secondly, are you using "su" as soon as you register the device into ADB? That would be something to think about.

If you keep having this issue, delete the folder and try using everything again but take your time and read over to make sure you're not forgetting anything! It seems like you may have skipped a step by accident.
[Ouya Android Development] simbaba:
I have re-install SDK totally and restart the tut :

:(
[Ouya Android Development] simbaba:
I have FACTORY RESET the OUYA + re-install SDK/ Driver on PC = same error :

/system/bin/sh: can't create /system/xbin/su: Read-only file system
[Ouya Android Development] professorpoptart:
The factory reset just wipes the /data partition, If the issue is with su this would not have fixed it, as su lives on the /system partition. The easiest way to get to 100% stock it to sideload the ota zip via recovery.

get ota zip here:

http://xdaforums.com/showthread.php?t=2266629

sideload instructions here:

http://xdaforums.com/showthread.php?t=2344097
[Ouya Android Development] tcollum:
That error is just telling you that you haven't yet mounted /system as rw.
[Ouya Android Development] simbaba:
And how i can do that ? Thanx.
[Ouya Android Development] tcollum:
That's what the mount command is for in the guide
[Ouya Android Development] simbaba:
Hello,

The update firmware 1.0.346 can fixed my problem ?

Thnaks.
[Ouya Android Development] professorpoptart:
After you do the update, your /system will be at stock. So anything that might have happened to su will be fixed. I would update and then;

If you see "#" instead of "$"your good to go for the rest of the steps!
[Ouya Android Development] simbaba:
Thanks, can i flash in stock without keyboard µ USB ?
[Ouya Android Development] professorpoptart:
You can boot cwm via fastboot without a keyboard in the ouya, but without a usb keyboard plugged into the ouya you wont be able to navigate the cwm menu to install the zip
[Ouya Android Development] 27scoob:
How do you go about reinstalling SU and busy box after an update. I did it a week or so ago but can not seem to repeat the process. I have tried deleting both and trying again , but I keep getting an error when updating the binary library in su . Any help would be great thanks...
[Ouya Android Development] HaYNigloo:
OP I was having trouble pushing SU to console. I'm not sure if this makes sense, but I changed the code here:

adb shell

su

mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP

exit

exit

adb shell push su /sdcard/su **I didn't think there was the SU folder, because adb kept saying dosen't exist. I removed su and proceeded one command at a time.

adb shell

su

cat /sdcard/su > /system/xbin/su

ln -s /system/xbin/su /system/bin/su

chmod 6755 /system/xbin/su

exit

exit

After putting su in its proper place, I was able to push modified build.prop back to console. I was getting the "permission denied" but I did had su access hennce # and not $

Again, I'm not sure if this makes sense, I am a noob when it comes to this sort of thing. I just wanted to let those who were having trouble, know what I did to get it working.
[Ouya Android Development] Ozz465:
Newb Here, anyone else getting error from such on ouya 'problem installing su, please send log of error to dev?
[Ouya Android Development] HaYNigloo:
Were you able to adb new su file to it's appropriate place, or were you getting errors, it may look like su file adb'd properly. Refer to my post above, on installing su file properly. Why you're getting that error, I don't think your su file is properly installed.

PS-My trick may or may not work for you, but that's what I did.
[Ouya Android Development] dully79:
After going through the initial steps to install the su binary:

adb shell
su
mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP
exit
exit
adb push su /sdcard/su
adb shell
su
cat /sdcard/su > /system/xbin/su
ln -s /system/xbin/su /system/bin/su
chmod 6755 /system/xbin/su
exit
exit

Why do we not need to remount the dev/block as read only, when we do after modifying the build.prop?

mount -o ro,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP

Thanks.
[Ouya Android Development] dark_saian:
Why do we not need to remount the dev/block as read only, when we do after modifying the build.prop?

mount -o ro,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP

I think that line is the origin of my problem too. I did a factory reset, lost root and I wanted to follow this guide again, but as soon as I try to enter adb shell I've got this :

dmx@toto:~/adt-bundle-linux-x86-20130522/sdk/platform-tools$ ./adb shell
/system/bin/sh: /system/etc/mkshrc[8]: id: not found [MENTION=1901967]androi[/MENTION]d:/ $ su
sh: /system/etc/mkshrc[8]: id: not found [MENTION=1901967]androi[/MENTION]d:/ #
[Ouya Android Development] foil:
Run my tool, if you don't mind, and see if it helps, and let me know, please.

Thank you! http://xdaforums.com/showthread.php?t=2350900

Edit: Nevermind, I see you're using Linux, and not Windows. My bad!
[Ouya Android Development] dark_saian:
I have a dual boot with Windows 7 as well. I've installed Android SDK on both system. I'm going to try this tool.
[Ouya Android Development] foil:
Some people are having issues with my released version, if it crashes on startup for you, this one will work for sure http://www.f0il.com/test3.zip

:)
[Ouya Android Development] dh4645:
did this last night, worked right after a few mess ups by me

mainly on this line

i kept putting a space between the comma and remount. ha

so do we need to change rw back to ro at the end or is ok to just follow as is then close cmd and turn off ouya?

it worked fine and the ouya works fine, i just dont want to have issues like the dude 4 posts above me if there is an update or if i do a factory reset.
[Ouya Android Development] dh4645:
so do we need to change rw back to ro at the end or is ok to just follow as is then close cmd and turn off ouya?
[Ouya Android Development] TadeoNYC:
I think it's just a matter of preference and comfort. If you don't plan on making any more changes to system then switch it ro and you can change it again if you want it. If I was sharing my OUYA with children or roommates I would definitely make it ro.

Be a little patient, why bump a very active thread after less than a day? The question is not that important.
[Ouya Android Development] dh4645:
the question was originally asked july 4th by someone else, so i was trying to help get an answer.

thanks.

so would keeping it on rw screw things up if there is an update or someone (as the dude above) does a factory reset?
[Ouya Android Development] TadeoNYC:
Having rw enabled has no bearing on an OTA or factory reset. All OTAs have overwritten the system folder, so all steps to enable su must be repeated every time. I believe factory reset only resets the data in the SD folder, that is why those people who some how lose the su file itself must reinstall the OTA with recovery, the factory reset does not put it back.

If you haven't already, you need to install CWM and backup.
[Ouya Android Development] dh4645:
i did get titanium on there, but havent done a nandroid with cwm yet since i havent had a chance to see how put cwm on the ouya
[Ouya Android Development] frickinjerms:
installing superuser was a breeze the headache was settng up adb haha but after an hour of updating my sdk and drivers i totally got her going :D
[Ouya Android Development] Kpyto:
Hello!

I need a little help... While I run script:

I'm always got an error: "Operation not permitted" :(

How to fix it? Thank a lot!
[Ouya Android Development] TadeoNYC:
It's not a script! Every line is an individual command. This is a little clearer http://xdaforums.com/showthread.php?p=41412675
[Ouya Android Development] lemonoid:
so I have a problem. I had just rooted and installed CWM on my OUYA yesterday. I was going to make a backup, but as I just finished installing CWM a friend walked in I haven't seen in years and wanted to play, so I didn't get around to the backup. I started messing with this, I plugged up to windows, connected to adb and everything was working fine, went through the first steps to setting up wireless adb, I got through

adb shell
su
mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP
chmod 666 system/build.prop

and I accidentally skipped the step to pull the build.prop and tried to run the service xxx.xxx.xxx:5555 whatever the IP is, and i of course got a failure so I went back and looked, and tried to pull the build.prop and it pretty much told me that my device was no longer connected. I exited, killed the adb server and tried to restart it, and no devices showed up. I turned my ouya on and off and it worked, I tried adb again, didn't work. then I rebooted the OUYA again, only to a black screen. adb is not connecting to my device, and my device is not loading on my TV. So I ran OUYA ToolBox by foil to see if there was anything I could do there, and when I pull it up, it shows my device connected at the bottom with the id that adb usually pulls up 015d8eb1855c060a. And to get the ToolBox working, I had to use your directions for modifying the adb_winusb.inf file before I could get it working because it needs to connect through adb. so SOMEHOW ToolBox is connecting through adb, but I cannot connect to adb through command prompt. Do you think running these few commands, doing the mount, remount, and chmod build.prop and do you think that running the code that I needed to edit (service ip:5555 as a command) could've bricked the device? That makes no sense to me, it would just seem that it would've failed. I don't know what's going on here. If you could help me with this it would really help. I don't know how to get in and do a factory reset because I can't pull up the screen and I can't factory reset through ToolBox. If you can help me it would save my day.
[Ouya Android Development] sqkid89:
What did you do to fix this? Having same result. Thanks!
[Ouya Android Development] dh4645:
i think thats what mine originally did..when i went into the device manager, there were 2 listings for ouya and one had an exclamation sign of a missing driver (not the same one as mentioned in the instructions) so i updated the driver and then i got a device #
[Ouya Android Development] sqkid89:
figured it out. since i have windows 8 64-bit (and amd processor?), had to add the same lines to NTamd64 in the inf file. also had to reboot and turn off driver signature. thanks for the help
[Ouya Android Development] rossdret:


How do you turn off the driver signature? And where did you find the ouya driver?
[Ouya Android Development] nex86:
When you didn't change the permission of the build.prop, your Ouya is softbricked.

If you have no way to access ADB shell to fix the permissions you have to reflash the firmware.

Download the latest firmware here: https://ouyafw.skumler.net/

shutdown your Ouya, plug a USB keyboard on, boot it and hold down ALT+PRINT SC+I several times until you get into the recovery.

If you see the Ouya logo with an ! press home.

Flash the new Firmware via ADB in recovery, sideload the zip with "ADB sideload filename.zip"

If you have luck your Ouya might haven't lost all data.
[Ouya Android Development] rossdret:
How did you update the driver? Im using win7 and I have searched high and low. I even installed the Samsung keis software as suggested in this thread but no luck.

Same issue with me...doesnt list any devices.
[Ouya Android Development] TadeoNYC:
I accidentally discovered a great tool to cleanup and install as well as test adb drivers. http://xdaforums.com/showthread.php?p=43869563
[Ouya Android Development] rossdret:
You are the man!!!
[Ouya Android Development] Petesky:
Should this work on Windows XP, I followed instructions in first post and I've got the usb driver installed but it just wont work , should I have usb debugging turned on , I've tried it on and off ,when its off I can see contents of ouya on my pc ,with it off it's looking for an mtp driver
[Ouya Android Development] Midnitte:
Followed original OP directions, then tried universal + original + adding to AMD64 section (Using Windows 8 64 bit on AMD) plus disabling driver verification... still no work :(
[Ouya Android Development] Ch4m3l30n:
Thanks for posting this concise information with which I was able to root my OUYA on the first try in less than 5 minutes using my Ubuntu Linux system.
[Ouya Android Development] cnnxda:
i tried everything and when i finish the first part of the command. adb devices.. i dont get any sserial number. all i get is "device is listed" or something similar.

any help? i opened ouya toolbox and doesnt recognize the ouya.

i have already rooted it via the sideload method.
[Ouya Android Development] elmerohueso:
Bumping this up as the newest OTA update breaks the oneclickroot app. OUYA rep says the update should still ship with terminal/ADB root access, like always, so manual method should still work (I don't have access to my OUYA to test, though).
[Ouya Android Development] lscheres:
This does in fact still work for the new OTA... first time i had to do it this way, the new hotfix made all the buttons on my mele f10 pro stop working
[Ouya Android Development] lscheres:
For some reason after the recent update i cant get root back even doing it manually. I have adb access and have busy box and super user installed on the ouya. Even uninstalled and reinstalled and restarted and still super user wont update the binarys..... I dont know what im doing wrong. Ive done this before a million times. Did anything change in the recent update???
[Ouya Android Development] rah2501:
Link for busybox, superuser and su binaries no longer working.

Unforunately this link no longer works. Does anybody have a copy of the file that this link used to go to?

Thanks.

Edit: For those who may come after me, I found an archive here that contains superuser.apk, busybox.apk and su binaries. Not tested yet though.
[Ouya Android Development] ivanovjohn2018:
Hi, the device is not detected on the computer in the device manager in any way, adb does not work. Only the fastboot works.How easy is it to make adb work? The problem is that the device is not detected in Windows and device manager.