Related
This guide was taken from AndroidCentral and I thought I would share it here because it's taken me 4 hours this morning to figure out why I was having so many problems trying to flash a recovery image when I know my phone was rooted and flashed in order to get 2.1 a month or so ago. I have been searching these forums and google and hope anyone else who has my issue finds this post.
1. Make sure you have the Android SDK installed.
2. Download flash_image.zip
3. Download recovery-RA-heroc-v1.5.2.img
4. Unzip the first file, and place both in your Android SDK/tools folder.
5. Make sure USB debugging is ON
6. Connect your phone to the PC
7. Open the command window and navigate to the Android-sdk/tools folder on your computer.
8. At the prompt enter the following, one line at a time followed by enter
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
exit
exit
adb push flash_image /system/bin
adb push recovery-RA-heroc-v1.5.2.img /sdcard
adb shell
chmod 0755 /system/bin/flash_image
reboot
9. Your phone will reboot. When it is finished, back at your command window, once again enter
Code:
adb shell
su
cd /sdcard
flash_image recovery recovery-RA-heroc-v1.5.2.img
reboot recovery
10. With any luck, you'll have the recovery image back and can load custom 2.1 based ROMS again.
Hope this helps. All credit goes to gbhil at Android Central.
You might want to change the title of the post. People might get confused thinking you found a way to downgrade the hboot and not how to flash the recovery image.
Can't get it to work.
I ran the RUU earlier.
Tried to root the old way.......didn't work.
Just tried this to get the recovery image back.
At the SU command it says: permission denied
Thanks,
Bubba.
bubbacs1 said:
Can't get it to work.
I ran the RUU earlier.
Tried to root the old way.......didn't work.
Just tried this to get the recovery image back.
At the SU command it says: permission denied
Thanks,
Bubba.
Click to expand...
Click to collapse
This won't work for the leak that was put out today. You lost root. This process requires root.
bubbacs1 said:
Can't get it to work.
I ran the RUU earlier.
Tried to root the old way.......didn't work.
Just tried this to get the recovery image back.
At the SU command it says: permission denied
Thanks,
Bubba.
Click to expand...
Click to collapse
If you used the new RUU that was leaked today you're screwed. The older 2.1 leaks were test ROMs that were already rooted so you could use the instructions above to flash the RECOVERY. Notice recovery in bold, not bootloader. Once hboot is updated there is no known way to downgrade so you could use an older RUU file.
This rom has no root. There is NO WAY to re-root after flashing the newest RUU. I'm sorry to say... you're ****ed.
HeroMeng said:
This rom has no root. There is NO WAY to re-root after flashing the newest RUU. I'm sorry to say... you're ****ed.
Click to expand...
Click to collapse
So they can't run an older ruu with 1.5?
HeroMeng said:
This rom has no root. There is NO WAY to re-root after flashing the newest RUU. I'm sorry to say... you're ****ed.
Click to expand...
Click to collapse
To clear that up, if you run the RUU you have no root. If you extract the ROM, set it up, and flash it, you will preserve root, just like damageless made for all of us. But, yeah, you are not gonna be able to get back from this one. at least until someone figures it out.
I changed the thread title to hopefully alleviate some confusion. I didn't realize there was a newer RUU released.
I flashed the Damageless Rom and it's running smoothly so far, but I'm still trying to figure out why wifi tethering isn't working out for me. :-(
celemew2 said:
I changed the thread title to hopefully alleviate some confusion. I didn't realize there was a newer RUU released.
I flashed the Damageless Rom and it's running smoothly so far, but I'm still trying to figure out why wifi tethering isn't working out for me. :-(
Click to expand...
Click to collapse
Did you get wifi tether version 1_60? That's the only version that ever worked for me.
Yeah, I have 1.60 installed on my phone right now, but when I try to start tethering, a SU Request black screen comes up and nothing happens until I get an error, "Activity SU Request (in application Superuser Permissions) is not responding."
I'm sure there's an answer somewhere, but lately I haven't been having luck searching for it.
Edit:
Thank you 98classic! All I had to do was enable USB Debugging. (I had it turned off cause I didn't like the warning up top when my phone was plugged into the computer)
"flash_image not found" what the f**k
need the binary? physically check its there with a root explorer
Sent from my broken Typewriter!!!
or do this download and set up the android SDK it itself includes the flash_image binary. after that u will need to open a command prompt on your computer u will have to change directory to platform tools
cd /path/to/platform-tools
after that u will get the chance to do
flash_image recovery /path/to/recovery.img
that will flash the recovery
now reboot into recovery
Typed from my broken Typewriter!!!
Hey guy's, I've beentrying to install clockworkmod on my Epic for some time now to no avail. See, I just rooted my phone using the noobnl's "one click method v2.2.6". The only recovery I have on my phone as of right now is tthe stock recovery. I've read just about every post about the installation on clockworkmod recovery and tried accordingly. Still no custom ecovery. Im really noob to all this "wiz stuff", and would greatly appreciate any help you guy's could give me. Perhaps some DETAILED step by step instructions ( CUZ IM REAL BRAIN DEAD AT TIMES )?? I have DI11 installed on my phone as of now, and im running the stock kernel v2.6.29. again, Im rooted with "noobnl's one click" and I do have root. Also, I need to know if you download to my pc, then push it to my phone using command prompt? Do I flash it with Odin? And what do I do after I run the clockworkmod exploit? Will I have custom recovery after that, is there anymore steps involved? Thank you all for making this site the best web site I"ve been on so far. You guy's are the best. Please hel[p with my dumb question, and sorry to waste your time. Thankx IA..
http://forum.xda-developers.com/showthread.php?t=782300
Download the .zip from that. Extract it to your desktop and rename the folder "cwm". Open up command prompt. Type this:
Code:
cd C:\Users\YOUR USER NAME\Desktop\cwm
adb shell
su
remount rw
exit
exit
After that, run the run.bat from the folder.
Download the .zip from that. Extract it to your desktop and rename the folder "cwm". Open up command prompt. Type this:
Code:
cd C:\Users\YOUR USER NAME\Desktop\cwm
adb shell
su
remount rw
exit
exit
After that, run the run.bat from the folder.
Click to expand...
Click to collapse
Excuse the stupid question please, do I have the sdcard mounted, or unmounted? I heard it can be done either way...
The only thing you use Odin for is to flash a complete .tar file. Ie, returning to stock, or updating to a new release DG27, DI07, or DI18
sniperkill said:
Excuse the stupid question please, do I have the sdcard mounted, or unmounted? I heard it can be done either way...
Click to expand...
Click to collapse
Make sure it is NOT mounted as a mass storage device. Make sure you can access it from the phone. So, don't mount it.
LSanna1488 said:
The only thing you use Odin for is to flash a complete .tar file. Ie, returning to stock, or updating to a new release DG27, DI07, or DI18
Click to expand...
Click to collapse
Technically, custom ROMs can be made for Odin, too... But since it's not a very good method, everyone prefers the recovery method. noobnl released his first rooted kernel for Odin. Odin does a lot more than just complete .tars.
LSanna1488 said:
The only thing you use Odin for is to flash a complete .tar file. Ie, returning to stock, or updating to a new release DG27, DI07, or DI18
Click to expand...
Click to collapse
I ran the commands as you stated, then ran the exploit. It keeps saying,
"remove stock recovery patcher"
"device not found"
system (something) install recovery.sh permission denied
"system/recovery-from-boot.p permission denied
failed to copy 'zImage' to /sdcard/zImage: permission denied
reboot: operation not permitted
im failed for /sdcard/zImage, permission denied
So what do you think is going on? Any thoughts?
I had same exact issue. Went back to completely stock then rooted then did clockwork. Do not mount sd card. Follow instructions exactly.
Sent from my SPH-D700 using XDA App
I'm having the same issue. When trying to 'su' to do the remount I'm getting a permission denied... but apps that require root seem to be working.
sniperkill said:
I ran the commands as you stated, then ran the exploit. It keeps saying,
"remove stock recovery patcher"
"device not found"
system (something) install recovery.sh permission denied
"system/recovery-from-boot.p permission denied
failed to copy 'zImage' to /sdcard/zImage: permission denied
reboot: operation not permitted
im failed for /sdcard/zImage, permission denied
So what do you think is going on? Any thoughts?
Click to expand...
Click to collapse
Is your phone in debug mode? (Settings -> Applications -> Development -> USB Debugging) Did it actually let your run those commands I told you?
Yes, my phone is in fact in debugg mode. My desktop command prompt does let me run the commands.
Adb devices
Adb shell
Su #
Remount rw
Exit
Exit
After I type the command "su" it gives me the #. Then on my phone a superuser request comes thru and askes to chose "yes" or "no". So I hit "yes". But when I run the exploit in the beginning it says "mount", and it says that the operation is not permitted... then it starts saying "I'm failed for" and "operation not permitted" and so on.. I think I'm missing a step somewhere but I don't kno...
Sent from my SPH-D700 using XDA App
Running su through adb shouldn't ask for permission the phone... that is weird.
Sent from my SPH-D700 using XDA App
I spent the weekend trying to get my Epic rooted and cwm installed. I was finally successful with both. CWM I had to install by typing in each command that was in the bat through the cmd window with adb.
Flak said:
I spent the weekend trying to get my Epic rooted and cwm installed. I was finally successful with both. CWM I had to install by typing in each command that was in the bat through the cmd window with adb.
Click to expand...
Click to collapse
So exactly what are the steps you took to install clockworkmod manually through windows command prompt? Do I just look in the bat exploit?
Hey guys, this is my first post, and I just wanted to say first off that all of you who have figured out how to root phones are awesome! Because of xda-developers and androidforums, I helped a friend root and put cyanogenmod 6 on his HTC Hero (cdma).
Anyway, I'm trying to put Zefie's CM7 on my LG Optimus V, and I'm stuck. First off I'm trying to root my phone. I'm following this guide: [How-To] Root the LG Optimus V on Android Central (I'd post the link, but the system won't let me since I'm a new user.). Usually I'd follow the instructions step by step, but I had to make some changes. I see this guide is written for Windows, but I'm running Ubuntu 10.10. After doing a lot of searching I was able to figure out that I had to install the Linux version of the Android SDK and use mono to run SuperOneClick.exe. That part was easy since I have a good knowledge of Linux and how it runs. The part that I'm stuck at is performing a Shell Root. When I click on Shell Root, SuperOneClick is stuck at "Waiting for device..." It's been like this for a while. If I click on Root, it gets stuck at "chmod psneuter..." Either way it's stuck and I don't know what to do.
Just to let you guys know, I have USB Debugging turned on, and I'm running Android version 2.2.1.
When I rooted my friend's HTC Hero, all I had to do was run a downloaded apk onto his SD card and run it, and then it would instantly root it. Is there a similar apk for the Optimus V? If not, is there a way I can manually root it via the terminal? Anyway, I'm stuck and would appreciate any suggestions or comments. Don't forget, I'm running Ubuntu 10.10, so some issues may arise since the tutorial was meant to be run on Windows machines.
Later tonight I'm going to try to root my phone at my friend's house since he has a computer running Windows XP. Hopefully I can get some better progress on his computer instead of mine. Thanks in advance for all your help!
Okay, nevermind. I did a little more searching and found a way to root my phone without running SuperOneClick.exe. I'll post if I have any more problems.
Well I spoke too soon. Here are the steps I followed to get to a # prompt in adb:
./adb push psneuter /data/local/tmp
./adb shell chmod 777 /data/local/tmp/psneuter
./adb shell /data/local/tmp/psneuter
I then did the following commands:
adb shell
mount -o remount,rw -t yaffs2 /system /system
exit
adb push su /system/bin
adb push busybox /system/bin
adb shell
cd /system/bin
chmod 4755 su
chmod 555 busybox
exit
adb reboot
After rebooting the phone, I installed Superuser and TitaniumBackup. I opened TitaniumBackup and it gave me an error stating that it could not acquire root privileges. I know for a fact that my phone has su and Busybox installed on it and have the correct permissions.
What bugs me even more is that when I run su via the adb shell root prompt or a terminal emulator on my phone, it returns the following error:
link_image[1997]: failed to link su
CANNOT LINK EXECUTABLE
What's up with that? I did find out that some people have had issues with Android 2.2.1 on their phone, and unfortunately that's what my phone had when I bought it about a month ago.
Okay, I figured it out finally and have my phone rooted. I had to run SuperOneClick.exe on my buddy's Windows computer. Instead of doing a Shell Root, I just clicked Root and it rooted. Now I'm stuck at figuring out how to do a Nandroid backup. I backed up everything using Titanium Backup, but I know I want to make a backup rom in case something goes wrong during the flash. What are the steps to performing a Nandroid backup?
Lol nevermind. I got Zefie's CM7 up and running this morning.
Nandroid is made using recovery. Glad you got it working
Sent from my VM670 using XDA App
bhambalek said:
Okay, nevermind. I did a little more searching and found a way to root my phone without running SuperOneClick.exe. I'll post if I have any more problems.
Click to expand...
Click to collapse
I am having the same problem as you, can you link me the other method?
EDIT: I do see the instructions in the next post, however where did you find them and get the files?
Any suggestions on how to regain root after the OTA ICS update using Linux? I've read through various posts scattered about the innerwebs regarding how using Windows but I'm a stubborn Linux user. I've downloaded the A2_ICS_Root Zip and explored the contents but not sure how to properly utilize them. I've rooted the phone in the past manually using Android SDK, Linux Terminal, push/adb shell commands and Motofail but of course lost root with the ICS update. If I don't get an answer I may attempt to follow some of the scripting used for Droid/Razors post ICS, of course tailored a bit. Although my Superuser app is still showing it's pretty much useless, like others with the same issue I've read about, it's still written into the system but no longer rooted. I've tested phone access in terminal but get the R/W error message ... no permission, etc. So ... I thought maybe folks here may have an answer for us semi skilled Linux users.
You should be able to just run the root.bat if you have the folder with all contents extracted to desktop.
Sent from my MB865 using xda premium
Aimless Rambler said:
Any suggestions on how to regain root after the OTA ICS update using Linux? I've read through various posts scattered about the innerwebs regarding how using Windows but I'm a stubborn Linux user. I've downloaded the A2_ICS_Root Zip and explored the contents but not sure how to properly utilize them. I've rooted the phone in the past manually using Android SDK, Linux Terminal, push/adb shell commands and Motofail but of course lost root with the ICS update. If I don't get an answer I may attempt to follow some of the scripting used for Droid/Razors post ICS, of course tailored a bit. Although my Superuser app is still showing it's pretty much useless, like others with the same issue I've read about, it's still written into the system but no longer rooted. I've tested phone access in terminal but get the R/W error message ... no permission, etc. So ... I thought maybe folks here may have an answer for us semi skilled Linux users.
Click to expand...
Click to collapse
Use the process and scripts I created for the leak/OTA. All you need to do is step 6 in the following link, and use the shell not the bat as others noted... if you are running linux, I am sure you already knew that.
Link:
http://forum.xda-developers.com/showthread.php?t=1779968
6) Boot into ICS, and root using the zip below, you will connect the phone to your computer and use the root.bat (unzip this folder to your desktop) for windows and root.sh for linux/mac.
The script and root files:
http://www.androidfilehost.com/main/Motorola_ATRIX_2_Developers/jimbridgman/A2_ICS_root.zip
Re-Rooted!
jimbridgman said:
Use the process and scripts I created for the leak/OTA. All you need to do is step 6 in the following link, and use the shell not the bat as others noted... if you are running linux, I am sure you already knew that.
Link:
http://forum.xda-developers.com/showthread.php?t=1779968
6) Boot into ICS, and root using the zip below, you will connect the phone to your computer and use the root.bat (unzip this folder to your desktop) for windows and root.sh for linux/mac.
The script and root files:
http://www.androidfilehost.com/main/Motorola_ATRIX_2_Developers/jimbridgman/A2_ICS_root.zip
Click to expand...
Click to collapse
Thanks Jim! I actually figured it out on my own, of course using the same zip file you provided which I had found in another thread.
I extracted the file into it's own folder, put the phone into debug mode and made sure MTP (media device) was checked, hooked to USB then ran a few checks in Terminal to make sure the device was recognized. Then I dragged "a2_ics_root.sh" into the open Terminal window and let it do its thing. I already had Superuser installed in earlier root (prior to ICS) so maybe that's why I got the "cannot stat 'su': No such file or directory cannot stat 'Superuser.apk': No such file or directory" error but then it said "You are rooted!". So to check to make sure I was actually rooted I ran the adb shell command and got this "[email protected]:/ $" then entered su, and got this "[email protected]:/ #"
Success!!
Hmm
Aimless Rambler said:
Thanks Jim! I actually figured it out on my own, of course using the same zip file you provided which I had found in another thread.
I extracted the file into it's own folder, put the phone into debug mode and made sure MTP (media device) was checked, hooked to USB then ran a few checks in Terminal to make sure the device was recognized. Then I dragged "a2_ics_root.sh" into the open Terminal window and let it do its thing. I already had Superuser installed in earlier root (prior to ICS) so maybe that's why I got the "cannot stat 'su': No such file or directory cannot stat 'Superuser.apk': No such file or directory" error but then it said "You are rooted!". So to check to make sure I was actually rooted I ran the adb shell command and got this "[email protected]:/ $" then entered su, and got this "[email protected]:/ #"
Success!!
Click to expand...
Click to collapse
Well I don't have root after all? Once unplugged from computer I ran a terminal emulator app on the phone and tried to access root but it says I don't have permission, as well as a few other apps I tried to install. Strangeness. As it looks above in quote is it just a temporary root? One thing I did notice after the OTA ICS update is that the superuser app remained. I tried a factory data reset thinking it would take it off but it didn't. Is my original rooting (GB Motofail) SU somehow stuck in perpetuity within some system file somewhere which is fouling up this root? So how would I go about a clean install of Superuser? I updated Superuser on Play Store but no difference. Hmm
update on strange problem
Aimless Rambler said:
Well I don't have root after all? Once unplugged from computer I ran a terminal emulator app on the phone and tried to access root but it says I don't have permission, as well as a few other apps I tried to install. Strangeness. As it looks above in quote is it just a temporary root? One thing I did notice after the OTA ICS update is that the superuser app remained. I tried a factory data reset thinking it would take it off but it didn't. Is my original rooting (GB Motofail) SU somehow stuck in perpetuity within some system file somewhere which is fouling up this root? So how would I go about a clean install of Superuser? I updated Superuser on Play Store but no difference. Hmm
Click to expand...
Click to collapse
First of all I apologize for all this confusion with replies to my own questions but I don't know any other way to relay the information. I'm troubleshooting as I go and hope it helps define what the issue may be and maybe a fix haha! Okay!! So I get root access easy as pie in terminal, no issues whatsoever, so I did a little searching and this is what I've found. The problem seems to be su is listed twice within my system folder (see below).
PROBLEM
[email protected]:/system/app # ls
Superuser.apk <<< is listed in the right location
# cd ..
[email protected]:/system #
[email protected]:/system/bin #
su <<< is listed here
[email protected]:/system/xbin #
su <<< is also listed here?
That can't be right? Shouldn't it only be in the /bin folder? Having downloaded the A2 ICS Root zip file I explored the Windows root.bat file in a text editor and saw that SU is suppose to install to /bin. So how the heck did it get in 2 different locations? ha!!! I'm guessing this would cause some issue but before I go deleting the extra file I thought I should inquire first. Haha!
Doh!!!! I know it's got to be something I did!
Aimless Rambler said:
First of all I apologize for all this confusion with replies to my own questions but I don't know any other way to relay the information. I'm troubleshooting as I go and hope it helps define what the issue may be and maybe a fix haha! Okay!! So I get root access easy as pie in terminal, no issues whatsoever, so I did a little searching and this is what I've found. The problem seems to be su is listed twice within my system folder (see below).
PROBLEM
[email protected]:/system/app # ls
Superuser.apk <<< is listed in the right location
# cd ..
[email protected]:/system #
[email protected]:/system/bin #
su <<< is listed here
[email protected]:/system/xbin #
su <<< is also listed here?
That can't be right? Shouldn't it only be in the /bin folder? Having downloaded the A2 ICS Root zip file I explored the Windows root.bat file in a text editor and saw that SU is suppose to install to /bin. So how the heck did it get in 2 different locations? ha!!! I'm guessing this would cause some issue but before I go deleting the extra file I thought I should inquire first. Haha!
Doh!!!! I know it's got to be something I did!
Click to expand...
Click to collapse
That is completely correct. The su in /system/xbin is a link to /system/bin/su. And that is correct, and how it should be.
Please explain your issue in more detail as I am not fully understanding what is not working.
Rooted again??
jimbridgman said:
That is completely correct. The su in /system/xbin is a link to /system/bin/su. And that is correct, and how it should be.
Please explain your issue in more detail as I am not fully understanding what is not working.
Click to expand...
Click to collapse
The issue was my phone was not actually rooted after running a2_ics_root.sh in Terminal (computer). I got the "cannot stat 'su': No such file or directory cannot stat 'Superuser.apk': No such file or directory" error message in terminal and also checked root by running a terminal emulator app within the phone and received the no permission message after entering su at the prompt. Once I reconnected the phone to the computer and ran the sh file again I gained temporary root. That's when I noticed su was in two different locations as I mentioned above and you subsequently replied was normal. Of course before I saw your response I had already removed (rm command) the extra su ha! After removing the su file from /xbin it alone did not fix the problem. I still could not access root. So I reran the a2_ics_root.sh in terminal (computer) and got root with no error messages and verified it with my phone's terminal app (also got the Superuser root access permission check, which I hadn't got before). No idea why this worked if su was suppose to be in two locations. As I was in the phones terminal emulator app I checked the /xbin folder and did not see it reappear yet it all seems rooted now! Ha! Gosh my brain hurts.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
remount succeeded
492 KB/s (22372 bytes in 0.044s)
3434 KB/s (397229 bytes in 0.112s)
You are rooted!
Aimless Rambler said:
The issue was my phone was not actually rooted after running a2_ics_root.sh in Terminal (computer). I got the "cannot stat 'su': No such file or directory cannot stat 'Superuser.apk': No such file or directory" error message in terminal and also checked root by running a terminal emulator app within the phone and received the no permission message after entering su at the prompt. Once I reconnected the phone to the computer and ran the sh file again I gained temporary root. That's when I noticed su was in two different locations as I mentioned above and you subsequently replied was normal. Of course before I saw your response I had already removed (rm command) the extra su ha! After removing the su file from /xbin I reran the a2_ics_root.sh in terminal (computer) and got root with no error messages and verified it with my phone's terminal app (also got the Superuser root access permission check, which I hadn't got before). No idea why this worked if su was suppose to be in two locations. As I was in the phones terminal emulator app I checked the /xbin folder and did not see it reappear yet it all seems rooted now! Ha! Gosh my brain hurts.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
remount succeeded
492 KB/s (22372 bytes in 0.044s)
3434 KB/s (397229 bytes in 0.112s)
You are rooted!
Click to expand...
Click to collapse
Did you by chance try and use some sort of root keeper before trying to do the OTA, then had these problems after the OTA was completed?
We have seen this before, and the reason you got the stat errors is because the wrong versions of the files were in /system/bin and /system/xbin. Yeah we have found that trying to use any OTA root keepers are BAD on this phone. Motorola is so anal about updates. That is why we mention to do an fxz before doing any OTA, then using the root scripts afterwards.
If you still have any more issues you might think about using the new ICS fxz in the development section and using/redoing the script from there.
P.S. I saw that you said you dragged the script into the terminal, that is a bad way to run it, BTW.... Try and open a terminal and cd into the dir that you unzipped the script in, and then into the ics_root dir and type ./root.sh and see if that works a little better next time, that might be why you only got temp root, because it was not able to find the proper su and superuser.apk to copy over with adb, I use relative paths in the script just for ease.
jimbridgman said:
Did you by chance try and use some sort of root keeper before trying to do the OTA, then had these problems after the OTA was completed?
We have seen this before, and the reason you got the stat errors is because the wrong versions of the files were in /system/bin and /system/xbin. Yeah we have found that trying to use any OTA root keepers are BAD on this phone. Motorola is so anal about updates. That is why we mention to do an fxz before doing any OTA, then using the root scripts afterwards.
If you still have any more issues you might think about using the new ICS fxz in the development section and using/redoing the script from there.
P.S. I saw that you said you dragged the script into the terminal, that is a bad way to run it, BTW.... Try and open a terminal and cd into the dir that you unzipped the script in, and then into the ics_root dir and type ./root.sh and see if that works a little better next time, that might be why you only got temp root, because it was not able to find the proper su and superuser.apk to copy over with adb, I use relative paths in the script just for ease.
Click to expand...
Click to collapse
Thanks! I'm sure I did something to cause the troubles but can't recall exactly what it was I did wrong! My brain is getting old. Ha! But to answer your question ... other than my original root (using Motofail) I've hesitated to do anything until after the ICS update. I recently bought the phone 2nd hand to replace my Samsung Captivate so I could experiment with a Lapdock (in my line of work portability and multi-role is a plus). The phone was stock when I got it. Also, I had moved the root.sh file and superuser.apk into my Android/Platform_Tools folder which is in my system path (android rules,etc), so there was some forethought prior to dragging the script into terminal. Next time I'll 'cd it like ya recommend!
Could it be there was an issue with how I did the original GB motofail root?
In any case all seems to be good now.
Thanks again!
Hi everyone, I'm trying to Install busybox,SuperUser and SU Binaries on my OUYA ...
I Have:
-ADB set up and working(wired)
-Downloded and unzipped the needed files
-Placed unzipped files in /android-sdk/platform-tools
Then i run the following commands to make sure my console is connected:
-adb kill-server
-echo 0x2836
-adb start-server
-adb devices
After 'adb devices' I see a number(My console #), which signifies my connected console...
Then i run the following commands to put SU in the proper place:
-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<-----here is where i get an error (cannot stat 'su': No Such Files Or Directory :crying What am i doing wrong here/ i don't get it!...Can anyone please help me?
cronikman84 said:
Hi everyone, I'm trying to Install busybox,SuperUser and SU Binaries on my OUYA ...
I Have:
-ADB set up and working(wired)
-Downloded and unzipped the needed files
-Placed unzipped files in /android-sdk/platform-tools
Then i run the following commands to make sure my console is connected:
-adb kill-server
-echo 0x2836
-adb start-server
-adb devices
After 'adb devices' I see a number(My console #), which signifies my connected console...
Then i run the following commands to put SU in the proper place:
-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<-----here is where i get an error (cannot stat 'su': No Such Files Or Directory :crying What am i doing wrong here/ i don't get it!...Can anyone please help me?
Click to expand...
Click to collapse
:good:never mind i figured it out...but when i go to Run SuperUser on the OUYA (Make > Software > SuperUser) and allow it to update, it gives me an error saying---->there was an error installing superuser. please send a log of the error to the developer. what now?
cronikman84 said:
:good:never mind i figured it out...but when i go to Run SuperUser on the OUYA (Make > Software > SuperUser) and allow it to update, it gives me an error saying---->there was an error installing superuser. please send a log of the error to the developer. what now?
Click to expand...
Click to collapse
Never mind LMAO...i got it :victory:
cronikman84 said:
Never mind LMAO...i got it :victory:
Click to expand...
Click to collapse
How'd you get it?! I'm stuck here too, thanks!
thanamesjames said:
How'd you get it?! I'm stuck here too, thanks!
Click to expand...
Click to collapse
Are you stuck at the error saying---->"there was an error installing superuser" still? cause if you are i think i can help you..., just on your ouya head over to MANAGE-SYSTEM-ADVANCED and scroll down to apps and delete the BUSYBOX FREE and SUPERUSER APPS...after that's done just repeat the commands again and reboot the system, then go click on MAKE>SOFTWARE>SUPERUSER and allow it to UPDATE but not from recovery and if that doesn't work let me know and ill tell you what to do next...BUT if your stuck at "adb push su /sdcard/su cannot stat 'su': No Such Files Or Directory" error then i can also help you...let me know, it's very simple, less than a minute
cronikman84 said:
Are you stuck at the error saying---->"there was an error installing superuser" still? cause if you are i think i can help you..., just on your ouya head over to MANAGE-SYSTEM-ADVANCED and scroll down to apps and delete the BUSYBOX FREE and SUPERUSER APPS...after that's done just repeat the commands again and reboot the system, then go click on MAKE>SOFTWARE>SUPERUSER and allow it to UPDATE but not from recovery and if that doesn't work let me know and ill tell you what to do next...BUT if your stuck at "adb push su /sdcard/su cannot stat 'su': No Such Files Or Directory" error then i can also help you...let me know, it's very simple, less than a minute
Click to expand...
Click to collapse
Hi,
I'm at the point where I've installed 'superuser' apk via adb. I've rebooted the console, gone to MAKE>SOFTWARE>SUPERUSER but when I click on 'install', I just get the error message: "There was an error installing Superuser. Please send a log to the error to the developer" but there are no logs.
Any ideas?
diazamet said:
Hi,
I'm at the point where I've installed 'superuser' apk via adb. I've rebooted the console, gone to MAKE>SOFTWARE>SUPERUSER but when I click on 'install', I just get the error message: "There was an error installing Superuser. Please send a log to the error to the developer" but there are no logs.
Any ideas?
Click to expand...
Click to collapse
yes, the best way to do it is with this tool OUYA toolbox and you can find it over here-----> http://forum.xda-developers.com/showthread.php?t=2350900 follow the instructions plug in your OUYA to your pc and download the test version of the tool, open it, click on install superuser and install it, then istall busybox and install it...then go to make- software-superuser and Update but not from recovery, then plug you OUYA back on to the pc and run the ouya toolbox program again and root(if you want to), you will be all set with SuperUser apk and busybox apk and root working perfect with no errors...
cronikman84 said:
yes, the best way to do it is with this tool OUYA toolbox and you can find it over here-----> http://forum.xda-developers.com/showthread.php?t=2350900 follow the instructions plug in your OUYA to your pc and download the test version of the tool, open it, click on install superuser and install it, then istall busybox and install it...then go to make- software-superuser and Update but not from recovery, then plug you OUYA back on to the pc and run the ouya toolbox program again and root(if you want to), you will be all set with SuperUser apk and busybox apk and root working perfect with no errors...
Click to expand...
Click to collapse
I think I might have found the issue. I think I forgot to copy the 'su' executable from /sdcard to /system/xbin. I've copied the correct 'su' executable to /system/xbin now. I'll have to test it later, I'm connected remotely at the moment so I can only do the shell stuff, I can't run Superuser.
What is the difference between the nativesu and the su copied from the attachment on this thread. There is a significant difference in size. Is the native su crippled in someway?
diazamet said:
I think I might have found the issue. I think I forgot to copy the 'su' executable from /sdcard to /system/xbin. I've copied the correct 'su' executable to /system/xbin now. I'll have to test it later, I'm connected remotely at the moment so I can only do the shell stuff, I can't run Superuser.
What is the difference between the nativesu and the su copied from the attachment on this thread. There is a significant difference in size. Is the native su crippled in someway?
Click to expand...
Click to collapse
:good: i hope you found the issue...i was having the same issue as you "There was an error installing Superuser. Please send a log to the error to the developer" and no matter what i tried it wouldn't work, so i just downloaded the OUYA toolbox test version and it took me less then 1 minutes to have superuser apk and busybox apk running and rooted, i didn't know you were connected remotely, i had mines connected straight up with the usb cable and it makes it easier for me..."What is the difference between the nativesu and the su copied from the attachment on this thread. There is a significant difference in size. Is the native su crippled in someway?" <----yes, i'm 90% sure that the native SU is crippled in some type of way, and i've heard other people confirm this.
cronikman84 said:
:good: i hope you found the issue...i was having the same issue as you "There was an error installing Superuser. Please send a log to the error to the developer" and no matter what i tried it wouldn't work, so i just downloaded the OUYA toolbox test version and it took me less then 1 minutes to have superuser apk and busybox apk running and rooted, i didn't know you were connected remotely, i had mines connected straight up with the usb cable and it makes it easier for me..."What is the difference between the nativesu and the su copied from the attachment on this thread. There is a significant difference in size. Is the native su crippled in someway?" <----yes, i'm 90% sure that the native SU is crippled in some type of way, and i've heard other people confirm this.
Click to expand...
Click to collapse
Yep. That was the problem. I guess I thought I'd copied the correct version of 'su' across without checking properly.
diazamet said:
Yep. That was the problem. I guess I thought I'd copied the correct version of 'su' across without checking properly.
Click to expand...
Click to collapse
Sweet!!...glad you got it fixed... I knew that the native SU was crippled the first time i tried it...that's why i tried the OUYA toolbox cause i knew people had success with SU on that toolbox, so i gave it a try and SU was workin...tha's how i knew something was wrong with the native SU...