You have full access to the OUYA store even when you are rooted.Do you still have access to the ouya store after SU installed? I heard rumors that access to the store was blocked until root access removed?
Sent from my GT-N7100 using Tapatalk 2
You have full access to the OUYA store even when you are rooted.Do you still have access to the ouya store after SU installed? I heard rumors that access to the store was blocked until root access removed?
Sent from my GT-N7100 using Tapatalk 2
Newbie here learning the ways and reading books/sites. Is this the SU binary and apk by Koush and are SU binaries interchangeable with differing superuser.apk?./adb push su/system/bin/su /sdcard/su
Inputting the adb shell su I get device not found message. Im opening a comand promt in platform-tools.The command should be "adb push su /sdcard/su" (pushing su to the sdcard).
- Setup wired and/or wireless ADB
- (Optional) Put adb.exe in your Windows PATH variable so you can run it from anywhere
- Download and unzip the SuperUser files from http://d-h.st/BBk
- Open an ADB shell with elevated permissions
Code:adb shell su- Mount the system partition as read-write
Code:mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP- Exit the ADB shell
or CTRL + CCode:exit exit- Push su to the sdcard
Code:adb push su /sdcard/su- Open an ADB shell with elevated permissions
Code:adb shell su- Cat su into /system/xbin
Code:cat /sdcard/su > /system/xbin/su- Create a symbolic link to su in /system/xbin from /system/bin (safer/cleaner than just putting su directly in the bin folder)
Code:ln -s /system/xbin/su /system/bin/su- Set the su permissions to -rwsr-sr-x
Code:chmod 6755 /system/xbin/su- Exit the ADB shell
or CTRL + CCode:exit exit- Install SuperUser
Code:adb install com.koushikdutta.superuser.apk- Install BusyBox
Code:adb install stericson.busybox.apk- Run SuperUser on the OUYA (Make > Software > SuperUser) and allow it to update
Do you have adb properly set up as on http://forum.xda-developers.com/showthread.php?p=41247928 ?Inputting the adb shell su I get device not found message. Im opening a comand promt in platform-tools.
This worked perfect thanks!!!The command should be "adb push su /sdcard/su" (pushing su to the sdcard).
- Setup wired and/or wireless ADB
- (Optional) Put adb.exe in your Windows PATH variable so you can run it from anywhere
- Download and unzip the SuperUser files from http://d-h.st/BBk
- Open an ADB shell with elevated permissions
Code:adb shell su- Mount the system partition as read-write
Code:mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP- Exit the ADB shell
or CTRL + CCode:exit exit- Push su to the sdcard
Code:adb push su /sdcard/su- Open an ADB shell with elevated permissions
Code:adb shell su- Cat su into /system/xbin
Code:cat /sdcard/su > /system/xbin/su- Create a symbolic link to su in /system/xbin from /system/bin (safer/cleaner than just putting su directly in the bin folder)
Code:ln -s /system/xbin/su /system/bin/su- Set the su permissions to -rwsr-sr-x
Code:chmod 6755 /system/xbin/su- Exit the ADB shell
or CTRL + CCode:exit exit- Install SuperUser
Code:adb install com.koushikdutta.superuser.apk- Install BusyBox
Code:adb install stericson.busybox.apk- Run SuperUser on the OUYA (Make > Software > SuperUser) and allow it to update
You really should just watch an adb tutorial on YouTube, because I'm not sure what it is that you don't understand at this point. I'm a complete noob to android and Linux and figured this out in a few hours. If you are this uncertain about what to do, maybe you shouldn't do it.how exactly do you do step 4 Open an ADB shell with elevated permissions. Sorry for the stupid question.
actually it turns out on the instrustion for setting up adb im not getting a device number after I input thisYou really should just watch an adb tutorial on YouTube, because I'm not sure what it is that you don't understand at this point. I'm a complete noob to android and Linux and figured this out in a few hours. If you are this uncertain about what to do, maybe you shouldn't do it.
Sent from my GT-P3113 using Tapatalk 4 Beta
Okay, go through this thread and look at all the steps others took to troubleshoot the device not being functional in the device manager in system panel. I told you to do this earlier, have you?actually it turns out on the instrustion for setting up adb im not getting a device number after I input this
adb kill-server
echo 0x2836 >> "%USERPROFILE%\.android\adb_usb.ini"
adb start-server
adb devices
its listed as a portable device.What should it be listed as?Okay, go through this thread and look at all the steps others took to troubleshoot the device not being functional in the device manager in system panel. I told you to do this earlier, have you?
Let us know what type of device ouya is listed as in the device manager.
Sent from my GT-P3113 using Tapatalk 4 Beta
Since mine isn't connected I'm not certain but I think it should be mtp. You need to go I'm too advanced properties and make sure it using adb drivers, if it isn't you need to manually add them by selecting update driver and then selecting have disk and pointing it to the adb driver.its listed as a portable device.What should it be listed as?
Hello,The command should be "adb push su /sdcard/su" (pushing su to the sdcard).
- Setup wired and/or wireless ADB
- (Optional) Put adb.exe in your Windows PATH variable so you can run it from anywhere
- Download and unzip the SuperUser files from http://d-h.st/BBk
- Open an ADB shell with elevated permissions
Code:adb shell su- Mount the system partition as read-write
Code:mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP- Exit the ADB shell
or CTRL + CCode:exit exit- Push su to the sdcard
Code:adb push su /sdcard/su- Open an ADB shell with elevated permissions
Code:adb shell su- Cat su into /system/xbin
Code:cat /sdcard/su > /system/xbin/su- Create a symbolic link to su in /system/xbin from /system/bin (safer/cleaner than just putting su directly in the bin folder)
Code:ln -s /system/xbin/su /system/bin/su- Set the su permissions to -rwsr-sr-x
Code:chmod 6755 /system/xbin/su- Exit the ADB shell
or CTRL + CCode:exit exit- Install SuperUser
Code:adb install com.koushikdutta.superuser.apk- Install BusyBox
Code:adb install stericson.busybox.apk- Run SuperUser on the OUYA (Make > Software > SuperUser) and allow it to update

The command should be "adb push su /sdcard/su" (pushing su to the sdcard).
- Cat su into /system/xbin
Code:cat /sdcard/su > /system/xbin/su- Create a symbolic link to su in /system/xbin from /system/bin (safer/cleaner than just putting su directly in the bin folder)
Code:ln -s /system/xbin/su /system/bin/su- Set the su permissions to -rwsr-sr-x
You combined two commands into one. "su" is one command (to get elevated privileges), and "cat /sdcard/su > /system/xbin/su" is the next command.Whenever I type this it says
1|[email protected]:/ $ su cat /sdcard/su > /system/xbin/su
/system/bin/sh: can't create /system/xbin/su: Read-only file system
adb push su /sdcard/su
adb shell
su
mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP
cat /sdcard/su > /system/xbin/su
ln -s /system/xbin/su /system/bin/su
chmod 6755 /system/xbin/su
exit
exit
adb install com.koushikdutta.superuser.apk
adb install stericson.busybox.apk
su is not working for me after I doY
Code:adb shell su
./adb shell
su
Operation not permitted
Something must be wrong with your image. This issue usually happens if you've messed with su already (the one that comes built in) and either changed its permissions or removed it. You'll need to grab the latest OTA zip and flash it via recovery.su is not working for me after I do
nothing changes and still I getCode:./adb shell suwhy?Code:Operation not permitted