Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,736,817 Members 53,628 Now Online
XDA Developers Android and Mobile Development Forum

[Q] adb - OUYA stuck as read-only, why?

Tip us?
 
Hyd-
Old
#1  
Junior Member - OP
Thanks Meter 0
Posts: 3
Join Date: Mar 2014
Default [Q] adb - OUYA stuck as read-only, why?

Hello beautiful people.

Keep in mind that I'm using Ubuntu 13.10 to do this. I'm trying to transfer my own bootanimation.zip to the OUYA but I can't because the system is set as read-only. adb recognizes my OUYA, if I use "adb devices" it shows the device, but I can't do anything else with it besides that. I read online that if I use "adb remount", it would mount as read/write. I tried that and I got "remount failed: Operation not permitted". I also read something about "adb root", I can't remember what exactly I had to do with that, but I got this "adbd cannot run as root in production builds".

If any more information is needed, please do ask for it. Help is appreciated. Thanks.
 
gianptune
Old
#2  
Senior Member
Thanks Meter 70
Posts: 188
Join Date: Oct 2010
try something like

Code:
adb shell
su
mount -o remount /system
 
Hyd-
Old
#3  
Junior Member - OP
Thanks Meter 0
Posts: 3
Join Date: Mar 2014
Quote:
Originally Posted by gianptune View Post
try something like

Code:
adb shell
su
mount -o remount /system
After I used that, I tried to push the bootanimation.zip to the OUYA with:

Code:
adb push bootanimation.zip system/media/
And I got this:

Code:
shell@android:/ # adb push bootanimation.zip system/media/
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|shell@android:/ #
It doesn't recognize it...
 
djden
Old
#4  
Member
Thanks Meter 7
Posts: 91
Join Date: Aug 2011
Quote:
Originally Posted by Hyd- View Post
After I used that, I tried to push the bootanimation.zip to the OUYA with:

Code:
adb push bootanimation.zip system/media/
And I got this:

Code:
shell@android:/ # adb push bootanimation.zip system/media/
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|shell@android:/ #
It doesn't recognize it...
Try adb insecure http://forum.xda-developers.com/show....php?t=1687590
 
Hyd-
Old
(Last edited by Hyd-; 8th April 2014 at 05:56 AM.)
#5  
Junior Member - OP
Thanks Meter 0
Posts: 3
Join Date: Mar 2014
Quote:
Originally Posted by djden View Post
I think that worked. I installed that, pushed it to the OUYA while on adb shell and got this:

Code:
1319 KB/s (2971409 bytes in 2.199s)

Acer@Aspire5315:~$
I couldn't see my bootanimation though, the screen was pitch-black until the "OUYA" voice and logo popped out. I suppose it was an error on my end, I'll have to try with another bootanimation and see. Thanks.

Edit: I tried to push another bootanimation but now it won't recognize it again...

Edit 2: It worked again but without adb shell... I downloaded another bootanimation, and got the same results. Odd...
 
ucenna
Old
#6  
Junior Member
Thanks Meter 0
Posts: 20
Join Date: May 2012
I'm having the same problem. The above commands presumably changed the filesystem to RW, but now when I try to push my file it says:
cannot stat 'OuyaCWMrecovery6.0.3.2flashable.zip': No such file or directory

I've tried everything I can think of. Restarting everything. Using the entire system path. Trying to leave shell and then run the command (which seems to send it back to r-o filesystem)
trying to rename the zip to make sure I'm typing the full thing correctly.

Any help?
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


XDA PORTAL POSTS

Cell Phone SIM Unlock Bill Just Steps Away from President’s Desk

For all those who believe that Cinderella stories don’t actually … more

Get Your Cargo to its Destination in 4×4 Military Operations Reborn

Racing games have evolved quite a bit since the days of Pole … more

Automate Your Device with Sfen

Changing the profile of yourdevice manually is now long forgotten. Since the advent of Android automation … more