[HOWTO] adb / sideloading / superuser access

[professorpoptart]

Thanks, can i flash in stock without keyboard µ USB ?

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

Sent from my SAMSUNG-SGH-I337 using xda app-developers app

 

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

 

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

 

[Ozz465]

Newb Here, anyone else getting error from such on ouya 'problem installing su, please send log of error to dev?

Sent from my Amazon Kindle Fire using xda app-developers app

 

[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.
Sent from my Galaxy Nexus using xda app-developers app

 

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

 

[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 :

[email protected]:~/adt-bundle-linux-x86-20130522/sdk/platform-tools$ ./adb shell
/system/bin/sh: /system/etc/mkshrc[8]: id: not found
 [user=1901967]@androi[/user]d:/ $ su
sh: /system/etc/mkshrc[8]: id: not found
 [user=1901967]@androi[/user]d:/ #

 

[foil]

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 :

[email protected]:~/adt-bundle-linux-x86-20130522/sdk/platform-tools$ ./adb shell
/system/bin/sh: /system/etc/mkshrc[8]: id: not found
 [user=1901967]@androi[/user]d:/ $ su
sh: /system/etc/mkshrc[8]: id: not found
 [user=1901967]@androi[/user]d:/ #

Run my tool, if you don't mind, and see if it helps, and let me know, please.
Thank you! http://forum.xda-developers.com/showthread.php?t=2350900

Edit: Nevermind, I see you're using Linux, and not Windows. My bad!

 

[dark_saian]

Run my tool, if you don't mind, and see if it helps, and let me know, please.
Thank you! http://forum.xda-developers.com/showthread.php?t=2350900

Edit: Nevermind, I see you're using Linux, and not Windows. My bad!

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.

 

[foil]

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.

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

 

[dh4645]

did this last night, worked right after a few mess ups by me

mainly on this line

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

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.

 

[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?

 

[TadeoNYC]

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?

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.
Sent from my GT-P3113 using Tapatalk 4 Beta

 

[dh4645]

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.
Sent from my GT-P3113 using Tapatalk 4 Beta

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?

 

[TadeoNYC]

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?

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.

Sent from my GT-P3113 using Tapatalk 4 Beta

 

[dh4645]

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.

Sent from my GT-P3113 using Tapatalk 4 Beta

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

 

[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

 

[Kpyto]

Hello!

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

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

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

How to fix it? Thank a lot!

 

[TadeoNYC]

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!

It's not a script! Every line is an individual command. This is a little clearer http://forum.xda-developers.com/showthread.php?p=41412675

Sent from my GT-P3113 using Tapatalk 4 Beta

 

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