Hei All, Nubie got problem here, and getting crazy LOL..
I have Droid X ME811, and it has been 2 weeks I've trying to rooting my droid in manual way, im following this awesome steps
and what happen is I always get stuck when I try to restart adb because after restart adb device cant be detected anymore.
C:\android-sdk-windows\tools>adb shell
* daemon not running. starting it now *
* daemon started successfully *
$ cd data/local/tmp
cd data/local/tmp
$ chmod 0755 rageagainstthecage-arm5.bin
chmod 0755 rageagainstthecage-arm5.bin
$ ./rageagainstthecage-arm5.bin
./rageagainstthecage-arm5.bin
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3814, 3814}
[*] Searching for adb ...
[+] Found adb as PID 1170
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] [email protected] so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
$
C:\android-sdk-windows\tools>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
(in this step, list always empty)
so I cant go to the next steps, I also try to go back to step $ cd data/local/tmp.
but seems like no different.
need advise
same exact problem here
Followed exact same steps, tried manually with adb, also tried other roms, pc mode, all other modes..nothing seems to work help please! I'm using ubuntu, adb works fine otherwise. Thanks
Related
now i know this is pretty basic i couldnt find anywhere that tells you how to root on linux or any other unix os but here it is. Thanks goes to bubby!!! PLEASE check out his original post and HELP HIS EFFORTS
FOR bubbys ONE CLICK ROOT BUSYBOX INSTALLER SAMSUNG CONTINUUM V0.1!!
Finally, i after days of searching and trying to execute the commands for this root Manually i pulled my sd, and Formatted my phone and then Found the command to run the one click root on my continuum.
MAKE SURE YOU BACK UP YOUR FILES!! ITS A MUST,, ALSO DEFINATELY ODIN BEFORE THE ROOT.
Next, Open terminal Locate your Unzip folder i recommend you place the folder near your sdk folder Ex. CD ~/android-sdk-linux_x86/oneclickroot
since we've located the destination Check to make sure your in the right place ls. Look at the list make sure you see the run.sh Ok Now Type in the terminal
sh run.sh you should then see
One Click Root v 0.1 for the Samsung Continuum
Scripted by bubby323
read: 11: Illegal option -n
[: 18: Linux: unexpected operator
-e
Starting adb server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
-e
Copy and run the exploit (may take up to two minutes)
74 KB/s (5392 bytes in 0.070s)
0 KB/s (43 bytes in 0.075s)
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3712, 3712}
[*] Searching for adb ...
[+] Found adb as PID 2961
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] [email protected] so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
it comes to adb connection will reset, restart adb server on desktop and re-login.
unplug your phone and wait 10sec and plug it back in
then you should see
Wait for phone to reconnect...
run.sh: 77: [[: not found
Mount system as r/w, cleanup old files, do some basic configuration
rm failed for /system/bin/playlogo, No such file or directory
failed on '/system/bin/playlogo-orig' - No such file or directory
Unable to chmod /system/bin/playlogo: No such file or directory
63 KB/s (4793 bytes in 0.073s)
Copying files onto phone...
361 KB/s (26264 bytes in 0.070s)
1120 KB/s (196521 bytes in 0.171s)
1219 KB/s (978414 bytes in 0.783s)
1207 KB/s (486948 bytes in 0.393s)
9 KB/s (483 bytes in 0.051s)
Setting permissions...
Installing busybox...
Waiting for phone to reboot...
run.sh: 117: [[: not found
Cleaning up files...
read: 129: Illegal option -n
now your rooted to check go to the market and try installing Titanium back-up
if all goes well you have root access
I have written a small procedure to get temporary root on HTC Wildfire S with S-ON (posting it I've noticed the argument has already been treated, even if in another way).
The procedure works in a temporary way, until next restart.
Superuser permissions do work only with applications that accept su binary located in /sbin and NOT in standard directories /system/bin or /system/xbin, (not writeable on this phone due to S-ON lock). I have tested the patch with Titanium Backup and Proxydroid, and they both work fine.
The procedure uses Revolutionary - zergRush binary to get root and then installs su binary in /sbin directory for future uses. Unfortunately /sbin folder is regenerated at every boot and this is the reason why this root is only temporary.
As usual, you apply the patch at your own risk (but considering that we’re not going to flash anything, I suppose the worst case could be a terminal crash).
Ok, let’s go straight to the steps to follow:
1. we’re assuming you have already downloaded and installed HTC drivers
2. download and install superuser from market (even if you have not yet rooted your phone). run it and try to update su binary in its settings page (it will fail but nevermind)
3. enable settings->applications->development->usb debugging
4. download and unpack the temproot.zip attachment in a pc folder
5. close HTC Sync from PC system tray
6. connect wildfire s to usb port
7. choose HTC sync connection mode
8. open dos prompt and go to the folder chosen at step 4
9. run temproot.bat and you're done
steps from 5 to 9 must be repeated at every boot to achieve root grant.
Note 1: if after having got root you can't see the sd card, reactivate it on settings->sd card and phone storage->Mount SD card
Note 2: after phone reboot do not try to open a shell (with adb shell) before running temproot batch, otherwise zergRush won't work
works 4 me. thnx
Hello
I try it on my S ON phone
So the first time, I've passed the steps and my phone was rooted
But I have restarted mly phone
So i don't have the root privileges...
So I try to launch temproot.bat but i have the same message :
adb server is out of date.......
I saw my scdard was not detected too when I had privileges roots.
Thanks
Stucking after "* daemon started successfully *"
not always after the same command, but the case is all the same.
i don't understand
C:\New Folder>temproot.bat
***************************************
*** HTC Wildfire S Temporary root ****
******** by wiseminosse 2011 **********
running step 1...
adb server is out of date. killing...
* daemon started successfully *
error: device offline
running step 2...
adb server is out of date. killing...
* daemon started successfully *
error: device offline
running step 3...
adb server is out of date. killing...
* daemon started successfully *
error: device offline
Unfortunaly an error occurred on step 3.
mxvc200 said:
C:\New Folder>temproot.bat
***************************************
*** HTC Wildfire S Temporary root ****
******** by wiseminosse 2011 **********
running step 1...
adb server is out of date. killing...
* daemon started successfully *
error: device offline
running step 2...
adb server is out of date. killing...
* daemon started successfully *
error: device offline
running step 3...
adb server is out of date. killing...
* daemon started successfully *
error: device offline
Unfortunaly an error occurred on step 3.
Click to expand...
Click to collapse
Device is in USB debugging mode?
snyker said:
i don't understand
Click to expand...
Click to collapse
was talking to OP
was not in debugging will try again and tell
---------- Post added at 12:56 PM ---------- Previous post was at 12:52 PM ----------
C:\New Folder>temproot.bat
***************************************
*** HTC Wildfire S Temporary root ****
******** by wiseminosse 2011 **********
running step 1...
adb server is out of date. killing...
* daemon started successfully *
rm failed for /data/local/tmp/boomsh, No such file or directory
running step 2...
adb server is out of date. killing...
* daemon started successfully *
rm failed for /data/local/tmp/sh, No such file or directory
running step 3...
adb server is out of date. killing...
* daemon started successfully *
480 KB/s (23056 bytes in 0.046s)
running step 4...
adb server is out of date. killing...
* daemon started successfully *
running step 5...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00015118
[*] Scooting ...
[*] Sending 149 zerglings ...
[+] Zerglings found a way to enter ! 0x10
[+] Overseer found a path ! 0x00015180
[*] Sending 149 zerglings ...
[+] Zerglings caused crash (good news): 0x401219dc 0x0064
[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0xafd252b7 0xafd397b7
[*] Popping 8 more zerglings
[*] Sending 157 zerglings ...
[+] Rush did it ! It's a GG, man !
[+] Killing ADB and restarting as root... enjoy!
running step 6...
adb server is out of date. killing...
* daemon started successfully *
error: device offline
adb server is out of date. killing...
* daemon started successfully *
error: device offline
Unfortunaly an error occurred on step 6.
C:\NEWFOL~1>
---------- Post added at 12:57 PM ---------- Previous post was at 12:56 PM ----------
work it out plzz???
mxvc200 said:
was not in debugging will try again and tell
---------- Post added at 12:56 PM ---------- Previous post was at 12:52 PM ----------
C:\New Folder>temproot.bat
***************************************
*** HTC Wildfire S Temporary root ****
******** by wiseminosse 2011 **********
running step 1...
adb server is out of date. killing...
* daemon started successfully *
rm failed for /data/local/tmp/boomsh, No such file or directory
running step 2...
adb server is out of date. killing...
* daemon started successfully *
rm failed for /data/local/tmp/sh, No such file or directory
running step 3...
adb server is out of date. killing...
* daemon started successfully *
480 KB/s (23056 bytes in 0.046s)
running step 4...
adb server is out of date. killing...
* daemon started successfully *
running step 5...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00015118
[*] Scooting ...
[*] Sending 149 zerglings ...
[+] Zerglings found a way to enter ! 0x10
[+] Overseer found a path ! 0x00015180
[*] Sending 149 zerglings ...
[+] Zerglings caused crash (good news): 0x401219dc 0x0064
[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0xafd252b7 0xafd397b7
[*] Popping 8 more zerglings
[*] Sending 157 zerglings ...
[+] Rush did it ! It's a GG, man !
[+] Killing ADB and restarting as root... enjoy!
running step 6...
adb server is out of date. killing...
* daemon started successfully *
error: device offline
adb server is out of date. killing...
* daemon started successfully *
error: device offline
Unfortunaly an error occurred on step 6.
C:\NEWFOL~1>
---------- Post added at 12:57 PM ---------- Previous post was at 12:56 PM ----------
work it out plzz???
Click to expand...
Click to collapse
Close process HTC Sync from system tray.
adb should be the ONLY process trying to connect to the phone
snyker said:
adb server is out of date.......
Click to expand...
Click to collapse
Try closing HTC sync from PC system tray
snyker said:
I saw my scdard was not detected too when I had privileges roots.
Click to expand...
Click to collapse
Remount it from settings->sd card and phone storage->mount sd card
I try it closing HTC tray
But it doesn't work again....
I think I must write commands to remove old files....but I don't know what...
What can you possibly do after this temp root? plz explain in detail plz
---------- Post added at 06:18 PM ---------- Previous post was at 05:54 PM ----------
yaa got root now what can i do with temporary root?
problem
Hye im new on xda,i want to root my phone htc wildfire s and i also do u tutorial to get temporary root on my htc wildfire s,but im still dont know what to do..when i run temproot.bat n done all ,my phone always restat,can u tell me the next step?sory for bad english
---------- Post added at 06:34 PM ---------- Previous post was at 06:11 PM ----------
Can someone post the video how to get temporary root on this tutorial,because I
Still dont understand step by step..plzzzzz,im crazy to root my phone.....LOL...
snyker said:
I think I must write commands to remove old files....but I don't know what...
Click to expand...
Click to collapse
try executing commands manually
0) connect phone to pc
1) open task manager and kill any htc sync process
2) open command prompt and add "adb usb"
3) then edit temproot.bat and execute each command manually. relevant command are "adb shell ...". some commands are already included to remove scripts from previous executions (adb shell rm ...)
I try another and the phone is rooted but when the screen is off, my phone restarts...
Why?
And so after restart, it is not rooted !
morozzkin said:
works 4 me. thnx
Click to expand...
Click to collapse
Hye wiseminosse can u tell me why my phone is restat and restat when run temproot.bat
try executing commands step by step as indicated in a previous post and try to understand at what point the phone restarts
try executing all the commands except the final "remount -ro". it could be a side effect of the read only filesystem remount
Okay thnks,but i still dont understand what is the meaning" steps from 4 to 7 must be repeated at every boot to achieve root grant"?
Originally, my Arc was on 2.3.4 Stock, it is allowed for BootLoader unlocking.
I followed this guide to unlock the BootLoader
http://forum.xda-developers.com/showthread.php?t=1042978
I did Step 1, everything fine.
Then i did Step 2, then bad things starts to happen. Even at the command prompt, it state Flash is successful, my Arc got stuck at the Sony Ericsson Logo.
The Remedy I did:
I download the O2 Stock ROM from here
http://forum.xda-developers.com/showthread.php?t=1093523
Reinstall it using the FlashTool.
After reinstalling, I activated the SU using FlashTool.
So Far, everything is fine.
Seeing the Android is at 2.3.3, I connect using Sony Ericsson Phone Companion to attempt to update to 2.3.4.
Phone Companion complained my Firmware disable them from doing it.
Is there anywhere i can get 2.3.4?
Which then still allows me to ROOT, unlock Bootloader and subsequently, remove some of the bloated apps?
Thank you very much!
hello
use THIS to flash via flashtool : http://www.multiupload.com/GQO5RNQ856
and THIS to root your device: http://forum.xda-developers.com/showthread.php?t=1320350
if you don't want to lose root then you can just uncheck Wipe data and wipe cache in flashtool
hope it helped !
realfelix said:
hello
use THIS to flash via flashtool : http://www.multiupload.com/GQO5RNQ856
and THIS to root your device: http://forum.xda-developers.com/showthread.php?t=1320350
if you don't want to lose root then you can just uncheck Wipe data and wipe cache in flashtool
hope it helped !
Click to expand...
Click to collapse
What is the ROM in the first link?
Thks!!
---------------------------------------------------------------
Easy rooting toolkit (v3.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using latest zergRush exploit (16 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
--- cleaning
adb server is out of date. killing...
* daemon started successfully *
rm failed for *, No such file or directory
--- pushing zergRush"
adb server is out of date. killing...
* daemon started successfully *
22 KB/s (23056 bytes in 1.000s)
--- correcting permissions
adb server is out of date. killing...
* daemon started successfully *
--- executing zergRush
adb server is out of date. killing...
* daemon started successfully *
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00015118
[*] Scooting ...
[*] Sending 149 zerglings ...
[+] Zerglings found a way to enter ! 0x10
[+] Overseer found a path ! 0x000151e0
[*] Sending 149 zerglings ...
[+] Zerglings caused crash (good news): 0x2abcccc4 0x0054
[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0x6fd19483 0x6fd39847
[*] Popping 24 more zerglings
[*] Sending 173 zerglings ...
[+] Rush did it ! It's a GG, man !
[+] Killing ADB and restarting as root... enjoy!
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
--- pushing busybox
adb server is out of date. killing...
* daemon started successfully *
error: device not found
--- correcting permissions
adb server is out of date. killing...
* daemon started successfully *
error: device not found
--- remounting /system
adb server is out of date. killing...
* daemon started successfully *
error: device not found
--- copying busybox to /system/xbin/
adb server is out of date. killing...
* daemon started successfully *
error: device not found
--- correcting ownership
adb server is out of date. killing...
* daemon started successfully *
error: device not found
--- correcting permissions
adb server is out of date. killing...
* daemon started successfully *
error: device not found
--- installing busybox
adb server is out of date. killing...
* daemon started successfully *
error: device not found
adb server is out of date. killing...
* daemon started successfully *
error: device not found
--- pushing SU binary
adb server is out of date. killing...
* daemon started successfully *
error: device not found
--- correcting ownership
adb server is out of date. killing...
* daemon started successfully *
error: device not found
--- correcting permissions
adb server is out of date. killing...
* daemon started successfully *
error: device not found
--- correcting symlinks
adb server is out of date. killing...
* daemon started successfully *
rm failed for /system/xbin/su, Read-only file system
adb server is out of date. killing...
* daemon started successfully *
link failed Read-only file system
--- pushing Superuser app
adb server is out of date. killing...
* daemon started successfully *
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
adb server is out of date. killing...
* daemon started successfully *
--- rebooting
adb server is out of date. killing...
* daemon started successfully *
ALL DONE!!!
Press any key to continue . . .
Click to expand...
Click to collapse
I have this all over the execution
adb server is out of date. killing...
Another error is this
rm failed for /system/xbin/su, Read-only file system
adb server is out of date. killing...
* daemon started successfully *
link failed Read-only file system
--- pushing Superuser app
adb server is out of date. killing...
* daemon started successfully *
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
My phone is able to boot up after the installation, how to i verify whether the objective of the bat file is achieved?
Thank you.
It is the 4.0.A.2.0.58 generic HK(World) firmware
Sent from my LT15i using XDA App
realfelix said:
It is the 4.0.A.2.0.58 generic HK(World) firmware
Sent from my LT15i using XDA App
Click to expand...
Click to collapse
Ok. Thank you!
my arc is currently on Android 2.3.4
and the bootloader is unlocked.
i can install titanium backup, so i think everything should be fine!
Thank you very much!!
Hi, I read tons of threads and I can't find a solution to root my Atrix 2, all ways I finish with an error message, the first error, here is the log ( I use 1-click exploit) I have 2.3.6 thanks for any help
[*] Motorola universal root script by P3Droid
[*]
[*] This should work on most motorola phones
[*]
[*] Press any key to get this phone rooted !
Press any key to continue . . .
[*]
[*] Waiting for device...
* daemon not running. starting it now *
* daemon started successfully *
[*] Motorola Phone Connected...
[*] Starting the Root Process, Do Not Disconnect Phone...
712 KB/s (22776 bytes in 0.031s)
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[-] Cannot copy boomsh.: No such file or directory
[1] Segmentation fault /data/local/zerg
[*] Waiting for phone to reboot.
* daemon not running. starting it now *
* daemon started successfully *
[*] Installing Root Packages ...
remount failed: Operation not permitted
failed to copy 'su' to '/system/xbin/su': Read-only file system
Unable to chmod /system/xbin/su: No such file or directory
link failed Read-only file system
failed to copy 'busybox' to '/system/bin/busybox': Read-only file system
Unable to chmod /system/bin/busybox: No such file or directory
/system/bin/busybox: not found
3783 KB/s (785801 bytes in 0.202s)
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
cannot create /data/local.prop: permission denied
[*] Rebooting...
* daemon not running. starting it now *
* daemon started successfully *
[*] Your Phone is Rooted !
[*] Press any key to exit.
Press any key to continue . . .
Terminate batch job (Y/N)?
Thanks in advance..FROM ALL VIEWS NOT ONE HAVE A CLUE?
Really frustrating belong to a forum where you can't get any help, only curious people, 98 views and no one clue or idea?
Maybe you can root this way?
Dig hole in back yard and bury phone. maybe it will root then. LOL
Thanks I now I know why I get not any ideas or help, yes I going to wait for you to come and help me. I ready solved the problem,
how did you solve the problem
The devs in the Atrix 2 forums only have a way to root 2.3.5. if you upgraded to 2.3.6 you are not going to be able to root the device. If you head over the the Atrix 2 forums that probably would have helped you out a little more.
Here is the link where you can learn how to update to 2.3.6 and keep root as well:
http://forum.xda-developers.com/showthread.php?t=1477656
Then here is the link for the Deodexed 2.3.6:
http://forum.xda-developers.com/showthread.php?t=1420980
And the custom ROM based off of 2.3.6:
http://forum.xda-developers.com/showthread.php?t=1441397
Head over to the Atrix 2 forums and we will be able to help you out more.
1031917104 said:
Dig hole in back yard and bury phone. maybe it will root then. LOL
Click to expand...
Click to collapse
Yes I going to open your a..hole and bury the phone there
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.
try something like
Code:
adb shell
su
mount -o remount /system
gianptune said:
try something like
Code:
adb shell
su
mount -o remount /system
Click to expand...
Click to collapse
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:
[email protected]:/ # adb push bootanimation.zip system/media/
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/ #
It doesn't recognize it...
Hyd- said:
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:
[email protected]:/ # adb push bootanimation.zip system/media/
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/ #
It doesn't recognize it...
Click to expand...
Click to collapse
Try adb insecure http://forum.xda-developers.com/showthread.php?t=1687590
djden said:
Try adb insecure http://forum.xda-developers.com/showthread.php?t=1687590
Click to expand...
Click to collapse
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)
[email protected]:~$
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...
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?
Try doing adb shell as as super user and doing chmod 777 to any relevant directories on your Ouya (like /sdcard/ etc).