[HOWTO] adb / sideloading / superuser access

[professorpoptart]

Thanks but same error when after i write "mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP" :

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.

 

[simbaba]

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.

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

 

[professorpoptart]

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

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.

 

[simbaba]

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.

Thanks but i have never "#", always "$" with su...

 

[professorpoptart]

Thanks but i have never "#", always "$" with su...

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.



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

 

[simbaba]

Okay, thanks.

 

[Phen0m]

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.



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

How do you boot into recovery on the ouya?

 

[professorpoptart]

How do you boot into recovery on the ouya?

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.

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

 

[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

 

[TadeoNYC]

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.

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

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.

Sent from my SCH-I535 using Tapatalk 2

 

[Ouya-XD]

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

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.

Sent from my HTC One VX using xda app-developers app

 

[simbaba]

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.

Sent from my HTC One VX using xda app-developers app

I have re-install SDK totally and restart the tut :

/system/bin/sh: can't create /system/xbin/su: Read-only file system

 

[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

 

[professorpoptart]

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

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://forum.xda-developers.com/showthread.php?t=2266629

sideload instructions here:
http://forum.xda-developers.com/showthread.php?t=2344097

 

[tcollum]

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

That error is just telling you that you haven't yet mounted /system as rw.

 

[simbaba]

That error is just telling you that you haven't yet mounted /system as rw.

And how i can do that ? Thanx.

 

[tcollum]

And how i can do that ? Thanx.

That's what the mount command is for in the guide

 

[simbaba]

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://forum.xda-developers.com/showthread.php?t=2266629

sideload instructions here:
http://forum.xda-developers.com/showthread.php?t=2344097

Hello,
The update firmware 1.0.346 can fixed my problem ?

Thnaks.

 

[professorpoptart]

Hello,
The update firmware 1.0.346 can fixed my problem ?

Thnaks.

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;

adb shell
su

If you see "#" instead of "$"your good to go for the rest of the steps!

 

[simbaba]

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