[Q] adb - OUYA stuck as read-only, why? - Ouya Q&A, Help & Troubleshooting

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).

Related

Need Help with ADB

i'm new to adb. i finally got it working. the correct string is added to Path, it's in my root directory C:\. i'm able to list my device, list directories, and even push/pull (did test to sdcard). i cannot, however, mount the /system directory to r/w.
this is what's happening
C:\android\android-sdk_r06-windows\android-sdk-windows\tools> adb remount
remount failed: Invalid argument
i'm in recovery trying to do this. anyone know what's going on or can maybe lend some help? thank you
mrvirginia said:
i'm new to adb. i finally got it working. the correct string is added to Path, it's in my root directory C:\. i'm able to list my device, list directories, and even push/pull (did test to sdcard). i cannot, however, mount the /system directory to r/w.
this is what's happening
C:\android\android-sdk_r06-windows\android-sdk-windows\tools> adb remount
remount failed: Invalid argument
i'm in recovery trying to do this. anyone know what's going on or can maybe lend some help? thank you
Click to expand...
Click to collapse
if you do not have a rooted, NAND unlocked, phone, you will not be able to mount /system
timothydonohue said:
if you do not have a rooted, NAND unlocked, phone, you will not be able to mount /system
Click to expand...
Click to collapse
it is rooted and NAND unlocked lol
i was actually able to push but not where i wanted.
i did
adb push com.htc.resources.apk /system/framework
but that's not where it needs to go
so i then did
adb push com.htc.resources.apk /system/framework/
and it says /system/framework is a directory, which i know lol that's where i need the file to go.
oh yeah, and i got it mounted as r/w. so now i'm just having trouble getting the file where it needs to be with the whole "is a directory" error instead of it actually pushing the file. still unable to pull a file from that location, though.
try writing the filename. it 'should' append it automatically, but if not then try
adb push com.htc.resources.apk /system/framework/com.htc.resources.apk
timothydonohue said:
try writing the filename. it 'should' append it automatically, but if not then try
adb push com.htc.resources.apk /system/framework/com.htc.resources.apk
Click to expand...
Click to collapse
this will prob work but...
now i'm getting "error: more than one device and emulator"
edit: i'm going to reboot and start all over. not sure how to kill it off since this is a little new to me ha
timothydonohue said:
try writing the filename. it 'should' append it automatically, but if not then try
adb push com.htc.resources.apk /system/framework/com.htc.resources.apk
Click to expand...
Click to collapse
this was a successful push, but the file is still not updating so i'm lost now
also, trying to pull this file back out is not working using
C:\android\android-sdk_r06-windows\android-sdk-windows\tools>adb pull /system/fr
amework/com.htc.resources.apk com.htc.resources.apk
remote object '/system/framework/com.htc.resources.apk' does not exist
edit: this is what i'm looking at
C:\android\android-sdk_r06-windows\android-sdk-windows\tools>adb shell mount -o
rw, remount /dev/block/mtdblock3 /system
adb server is out of date. killing...
* daemon started successfully *
BusyBox v1.15.3 (2010-02-06 17:13:19 CET) multi-call binary
Usage: mount [flags] DEVICE NODE [-o OPT,OPT]
Mount a filesystem. Filesystem autodetection requires /proc be mounted.
Options:
-a Mount all filesystems in fstab
-r Read-only mount
-w Read-write mount (default)
-t FSTYPE Filesystem type
-O OPT Mount only filesystems with option OPT (-a only)
-o OPT:
loop Ignored (loop devices are autodetected)
[a]sync Writes are [a]synchronous
[no]atime Disable/enable updates to inode access times
[no]diratime Disable/enable atime updates to directories
[no]relatime Disable/enable atime updates relative to modification ti
me
[no]dev (Dis)allow use of special device files
[no]exec (Dis)allow use of executable files
[no]suid (Dis)allow set-user-id-root programs
[r]shared Convert [recursively] to a shared subtree
[r]slave Convert [recursively] to a slave subtree
[r]private Convert [recursively] to a private subtree
[un]bindable Make mount point [un]able to be bind mounted
bind Bind a directory to an additional location
move Relocate an existing mount point
remount Remount a mounted filesystem, changing its flags
ro/rw Read-only/read-write mount
There are EVEN MORE flags that are specific to each filesystem
You'll have to see the written documentation for those filesystems
C:\android\android-sdk_r06-windows\android-sdk-windows\tools>adb pull /system/fr
amework/com.htc.resources.apk com.htc.resources.apk
remote object '/system/framework/com.htc.resources.apk' does not exist
/system is under mtdblock4 on our device.
if you need to mount /system as read/writeable from adb, you should just be able to use
adb remount
if you are doing it in shell, use mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
timothydonohue said:
/system is under mtdblock4 on our device.
if you need to mount /system as read/writeable from adb, you should just be able to use
adb remount
if you are doing it in shell, use mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
Click to expand...
Click to collapse
yeah adb remount won't work for me either.
C:\android\android-sdk_r06-windows\android-sdk-windows\tools>adb remount
adb server is out of date. killing...
* daemon started successfully *
remount failed: Invalid argument
i'm going to try mtdblock4
also, if you are having issues with the adb daemon, use
adb kill-server
adb start-server
that'll reboot the adb daemon
timothydonohue said:
also, if you are having issues with the adb daemon, use
adb kill-server
adb start-server
that'll reboot the adb daemon
Click to expand...
Click to collapse
thanks. yeah i started just killing it in task manager
after using "mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system" and trying to pull, i'm still getting /system/framework/com.htc.resources.apk does not exist
yeah, not sure what to tell you then. i can't piddle around in my own, because i'm on cm6, and won't have that.
are you sure it exists?
adb shell
# cd /system/framework
# ls
that will tell you what's in there. if you can't see it, it's not there.
from a brand new shell, (or bounce back up to the root directory)
try
find -name "*resources*.*"
that should tell you every file that contains 'resources' as a part of the file name, and where it is located.
timothydonohue said:
yeah, not sure what to tell you then. i can't piddle around in my own, because i'm on cm6, and won't have that.
are you sure it exists?
adb shell
# cd /system/framework
# ls
that will tell you what's in there. if you can't see it, it's not there.
from a brand new shell, (or bounce back up to the root directory)
try
find -name "*resources*.*"
that should tell you every file that contains 'resources' as a part of the file name, and where it is located.
Click to expand...
Click to collapse
it exists. i navigated to it using root explorer. but according to this, it doesn't exist
C:\android\android-sdk_r06-windows\android-sdk-windows\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
/ # cd /system/framework
cd /system/framework
/sbin/sh: cd: can't cd to /system/framework
/ #
you can't navigate to the folder if /system isn't mounted. if you just restarted the adb server, then it won't be mounted.
timothydonohue said:
you can't navigate to the folder if /system isn't mounted. if you just restarted the adb server, then it won't be mounted.
Click to expand...
Click to collapse
that was prob the case, can't remember if i re-mounted or not when i was doing that. regardless, i was positively mounted when trying to push/pull and it wasn't working so i guess i'll just have to wait for someone to put it in a flashable zip.
i hate adb
thanks for your help dude

flashing new rom issue please help

okay i'm following these steps, and once i get to adb shell su cd /data/local
Code:
cd\
cd c:\AndroidSDK\Tools
adb devices (A serial number should pop up saying your phone can be seen by ADB, if so continue typing the following with hitting enter at the end of each line)
adb push flash_image /data/local
adb push mtd0.img /data/local (that is a zero, not an oh in “mt0.img”)
adb shell su cd /data/local
chmod 04755 *
/data/local/flash_image misc /data/local/mtd0.img (again that is a zero, not an oh in “mt0.img”)
it tells me permission denied... i have full root, and am able to su and get #... im stuck at this part and don't know what to do, i've searched and can't find an answer.
Please help!
Are you sure that adb push actually pushed the files?
Did you get a confirmation?
Faud said:
Im blind..one sec
Click to expand...
Click to collapse
ummm okay.....

ADB: Permission denied...no matter what i do!!!

OK...I'm beginning to think that rooting is not for me!!!! Getting a bit frustrated!!!
OK, so I installed SDK on my pc (Win XP Ver 2002 SP3), and I cannot get it recognize the device.
I tried the guide for dummies here on XDA, and I follow all the indications, server starts up, I can kill it too....but every time I try to run it I get:
"error: device cannot be found"
The line that I am writing is as follows:
Code:
c:\android-sdk-windows\tools>adb shell
and I get the error above.
When I try to see if devices are connected, and Use this:
Code:
c:\android-sdk-windows\tools>adb devices
I get:
"List of Devices attached", but there is no list!!!!!
But I can see the SDCARD from my computer....I can access the files...
Maybe I can try to pull instead of push, but I'm not sure how that would be written (line wise), not if will work.
BTW...I have never done anything like this on android....very new to this!!!!
umm.. HELP!!!
OK changed pc's,....on this one it does recognize the device, but does not allow me to push anything.....when i try:
Code:
adb push su /sdcard/su
I get adb: permissions denied
------
I tried su +, and that got me to the # prompt. So I tried typing
Code:
# adb push su /sdcard/su
and I get adb: not found???
Running out of options here!
...
Thanks!
I think you are mounting the sdcard. You don't want to do that. Just connect your phone to the computer and run ADB. Don't click "USB Connected. Select to copy files to/from your computer" on your phone.
funkeee said:
I think you are mounting the sdcard. You don't want to do that. Just connect your phone to the computer and run ADB. Don't click "USB Connected. Select to copy files to/from your computer" on your phone.
Click to expand...
Click to collapse
Funkeeeeeee thank you for the reply.
OK...I am not getting an option when I connect to the pc..on the one I get it, I shose do nothing. I have also disabled mass storage on the device once loaded, adn I get the same error. Here is some of the code that I get thorught the PC's terminal:
C:\>cd android-sdk-windows\tools
C:\android-sdk-windows\tools>adb devices
List of devices attached
HT09YR200737 device
C:\android-sdk-windows\tools>adb shell
$ adb push su /sdcard/su
adb push su /sdcard/su
adb: permission denied
$ adb kill-server
adb kill-server
adb: permission denied
$
Click to expand...
Click to collapse
Notice that once I get the initial permission denied, the terminal seems to get locked up on that no matter what I type....see above...
Anything else to try??? AM I missing something here?
That's fine. There are a few things I can suggest for you to try..
First, I want you to enable USB debugging on your phone by going to Settings > Applications > Development and check that first option.
Then connect the phonoe, but don't use 'adb shell' before pushing files. It should look like this:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Funkz>cd c:\g2
c:\g2>adb pull /system/build.prop
501 KB/s (3596 bytes in 0.007s)
c:\g2>
Click to expand...
Click to collapse
If you are trying to run it from within adb shell, it will spit back 'adb: not found.' That should do fix it for you.
If it does not, go to Control Panel > System > Advanced > Environment Variables. Then click on Path and Edit, then ";C:\android-sdk-windows\tools\" at the very end and try again.
By the way, you don't have to run adb from the installation directory. After adding the path I just mentioned, you should be able to run it from anywhere.
funkeee said:
That's fine. There are a few things I can suggest for you to try..
First, I want you to enable USB debugging on your phone by going to Settings > Applications > Development and check that first option.
Then connect the phonoe, but don't use 'adb shell' before pushing files. It should look like this:
If you are trying to run it from within adb shell, it will spit back 'adb: not found.' That should do fix it for you.
If it does not, go to Control Panel > System > Advanced > Environment Variables. Then click on Path and Edit, then ";C:\android-sdk-windows\tools\" at the very end and try again.
By the way, you don't have to run adb from the installation directory. After adding the path I just mentioned, you should be able to run it from anywhere.
Click to expand...
Click to collapse
Thanks.....I finally can run it without having to type the entire path!!!! That was great help!!!
AS for the permission denied.....still having that issue! The one thing I didn't understand was when you changed the path to >g2.....what do you mean???? path to be g2?
Thanks again for the help!
Just a note...I am trying to do this post OTA, which I downloaded, never got the push...Would having the OTA have any effect on this? DO I need to consider reverting to stock and trying from there? If so how? run recovery?
Dude thanks for the help!
did you try typing SU? IMO you cant tamper with ADB Shell if you dont have su access so try typing down SU to ask for permission.
Alright first things first. ADB requires special drivers to work. Which is probably why it didn't work on the original PC. If you download the PDANet client on the PC that you need to do adb it will install the necessary drivers and you can uninstall the program without losing the drivers.
Another ADB requirement is to enable USB Debugging. MENU>Settings>Applications>Development and check the USB Debugging Box.
I don't know about anyone else but with my phone will automount the card. It is recommended to pull down the notification bar and make sure that your SD card isn't mounted.
You need to navigate your command prompt to whatever folder you keep ADB.exe for me
Code:
C:\Users\etnie>cd C:\Users\etnie\Downloads\G2\Android\tools
for me this returns
Code:
C:\Users\etnie\Downloads\G2\Android\tools>
to confirm this
Code:
C:\Users\etnie\Downloads\G2\Android\tools>adb devices
I won't post all the code but it should start the daemon successfully and list your device.
to be able to push files to your phone they also need to be in the same folder as the ADB.exe ie the tools folder. of course you can push it from any folder if you type the full path
Code:
C:\Users\etnie\Downloads\G2\Android\tools>adb push C:\Users\etnie\Downloads\G2\bootanimation.zip /data/local
the above code would push the bootanimation.zip from my G2 folder located in my Downloads folder to /data/local on the phone. changing the boot screen animation when you turn on the phone. I actually have the BIOS one. Because I am huge nerd lol. Moving on...
I think I covered everything necessary....If you are still having problems either PM me or reply here.
Thanks guys for the replays...here are some comments...
Acid_Wir3 said:
did you try typing SU? IMO you cant tamper with ADB Shell if you dont have su access so try typing down SU to ask for permission.
Click to expand...
Click to collapse
I have tried SU, and it does grant access, BUT!!!! so here is what happens...
I get to .....\tools> adb shell ... then i get.... the $ prompt. At this point I type $su .... then my prompt changes from $ to #. I understand that it should be $ # In any case once I get to # it says adb: not found code looks like this:
Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\carlos>cd\
C:\>adb shell
$ su
su
# adb push su /sdcard/su
adb push su /sdcard/su
adb: not found
#
BTW, the path has been predfined to C:\android-sdk-windows\tools\
Not sure how to navigate from #prompt
RuncaProfundus said:
1Alright first things first. ADB requires special drivers to work. Which is probably why it didn't work on the original PC. If you download the PDANet client on the PC that you need to do adb it will install the necessary drivers and you can uninstall the program without losing the drivers.
2Another ADB requirement is to enable USB Debugging. MENU>Settings>Applications>Development and check the USB Debugging Box.
3I don't know about anyone else but with my phone will automount the card. It is recommended to pull down the notification bar and make sure that your SD card isn't mounted.
4 You need to navigate your command prompt to whatever folder you keep ADB.exe for me
Code:
C:\Users\etnie>cd C:\Users\etnie\Downloads\G2\Android\tools
for me this returns
Code:
C:\Users\etnie\Downloads\G2\Android\tools>
to confirm this
Code:
C:\Users\etnie\Downloads\G2\Android\tools>adb devices
I won't post all the code but it should start the daemon successfully and list your device.
to be able to push files to your phone they also need to be in the same folder as the ADB.exe ie the tools folder. of course you can push it from any folder if you type the full path
Code:
C:\Users\etnie\Downloads\G2\Android\tools>adb push C:\Users\etnie\Downloads\G2\bootanimation.zip /data/local
the above code would push the bootanimation.zip from my G2 folder located in my Downloads folder to /data/local on the phone. changing the boot screen animation when you turn on the phone. I actually have the BIOS one. Because I am huge nerd lol. Moving on...
I think I covered everything necessary....If you are still having problems either PM me or reply here.
Click to expand...
Click to collapse
Runca thanks for the detailed reply....going in order here:
1 - I did and I still have pdanet isntalled
2 - it's been like that since the first day I got the phone.
3 - How do I ensure??? you are talking about from the phone....I should turn off USB Storage? Will try this one.
UPDATE: tried unmounting and re running without success....
Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\carlos>cd\
C:\>adb shell
$ adb push su /sdcard/su
adb push su /sdcard/su
adb: permission denied
$
4 - It's pretty much what I have. Other that I'm not running su before doing so......
Any thoughts?
Crey23 said:
AS for the permission denied.....still having that issue! The one thing I didn't understand was when you changed the path to >g2.....what do you mean???? path to be g2?
Click to expand...
Click to collapse
The "g2> " bit is just his command prompt. He's changed directory to one called "g2" on his phone but that's nothing to do with how adb works etc (just that if he pushes or pulls files then that'll be the current directory on the PC for that).
Crey23 said:
Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\carlos>cd\
C:\>adb shell
$ su
su
# adb push su /sdcard/su
adb push su /sdcard/su
adb: not found
#
Click to expand...
Click to collapse
Those "adb push" commands should be done from your PC's command prompt, not from within an Android shell prompt on your phone.
"adb shell" starts a command shell on the phone. Which is fine for doing some stuff. But "adb" commands won't work because now you're issuing them to your phone, not your PC.
steviewevie said:
Those "adb push" commands should be done from your PC's command prompt, not from within an Android shell prompt on your phone.
"adb shell" starts a command shell on the phone. Which is fine for doing some stuff. But "adb" commands won't work because now you're issuing them to your phone, not your PC.
Click to expand...
Click to collapse
Thanks Steve.....that makes a lot of sense, and in part why i am a bit lost here....but knowing that....how can I get to "push" things to my phone?
Don't run the adb shell command. That takes you into the phone's prompt. Any commands you run from adb shell with $ or # are run within the phone. You want to run adb push from command prompt. Look at my previous post. It should look like:
C:/>adb push ...
not
#adb push...
Sent from my HTC Vision using XDA App
Funkeee,x thank you I will try that as soon as I can.
funkeee said:
Don't run the adb shell command. That takes you into the phone's prompt. Any commands you run from adb shell with $ or # are run within the phone. You want to run adb push from command prompt. Look at my previous post. It should look like:
C:/>adb push ...
not
#adb push...
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Sent from my T-Mobile G2 using XDA App
Finally progress
Guys thank you for your help!!!!!
I was finally able to push all the files to the phone. Now my problem has changed..., still dealing with Permission denied....when executing rage I get a buch of errors, please see image:
Code:
$ $su
# /data/local/tmp/rage
I get this.....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I then figured that since I was temp rooted through Visionary r10, that was the reason for the errors above. I then proceeded to reboot without temp-rooting.
When I come up to the terminal I get:
Code:
export PATH=/data/local/bin:$PATH
$ $su
su: permission denied
$
SO if I understand this correctly, I need NOT be temp-rooted in order to run rage, but if I'm not temp-rooted, I don't have permissions to get to execute rage....there a chicken and egg story here somewhere! lol
Can I use a hybrid of the visionary temp root and perm root in that post?
From what I recall you need to uninstall visionary and reboot prior to using the rage method.
Sent from my HTC Vision using XDA App
Thanks funkeee...I will try in the morning.
But part of the problem is that without visionary I cannot get su access to run any of this. I'll backup VIS r10 before removing, and try again.
I post my results...goodnight and thanks!
funkeee said:
From what I recall you need to uninstall visionary and reboot prior to using the rage method.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Sent from my T-Mobile G2 using XDA App
I looked at the rage instructions and the prompt is misleading. You may forgetting to use chmod to change permssions. I've put my version of the instructions (just the start).
Uninstall visionary, reboot and from command prompt on your pc, navigate to the folder where you have these files and run:
c:/> adb push su /sdcard/su
c:/> adb push Superuser.apk /sdcard/Superuser.apk
c:/> adb push rage /data/local/tmp/rage
c:/> adb push busybox /data/local/tmp/busybox
c:/> adb push root /data/local/tmp/root
c:/> adb shell chmod 0755 /data/local/tmp/*
Don't forget the last entry, which changes the permissions.
Then on your phone, open terminal and put in:
$ /data/local/tmp/rage
It will say Forked Childs...
Then Menu > Reset Term. It will close, then launch terminal again, it will force close and then launch it again and you will have rage root.
If you get to there, you're in good shape. You can then follow those instructions to to push hboot and wpthis. Be careful with the dd command and be sure you have it exactly right. There are no do-overs with 'dd'.
http://forum.xda-developers.com/showthread.php?t=834228
Thanks man I will try it shortly.
funkeee said:
I looked at the rage instructions and the prompt is misleading. You may forgetting to use chmod to change permssions. I've put my version of the instructions (just the start).
Uninstall visionary, reboot and from command prompt on your pc, navigate to the folder where you have these files and run:
c:/> adb push su /sdcard/su
c:/> adb push Superuser.apk /sdcard/Superuser.apk
c:/> adb push rage /data/local/tmp/rage
c:/> adb push busybox /data/local/tmp/busybox
c:/> adb push root /data/local/tmp/root
c:/> adb shell chmod 0755 /data/local/tmp/*
Don't forget the last entry, which changes the permissions.
Click to expand...
Click to collapse
Up to here I am fine.
funkeee said:
Then on your phone, open terminal and put in:
$ /data/local/tmp/rage
It will say Forked Childs...
Then Menu > Reset Term. It will close, then launch terminal again, it will force close and then launch it again and you will have rage root.
If you get to there, you're in good shape. You can then follow those instructions to to push hboot and wpthis. Be careful with the dd command and be sure you have it exactly right. There are no do-overs with 'dd'.
http://forum.xda-developers.com/showthread.php?t=834228
Click to expand...
Click to collapse
But is with this part that I have issues with......
I uninstalled VISONary as suggested, and I got the same result as before.....error, error, error.....permission denied! Basically without visionary and su I cannot get access to the run rage. I gave me this error:
Code:
$ /data/local/tmp/rage
/data/local/tmp/rage: /data/local/tmp/busybox: permission denied
mount: Operation not permitted
mkdir failed for /system/xbin, Read-only file system
/data/local/tmp/rage: /data/local/tmp/busybox: permission denied
Unable to chmod /system/xbin/busybox: no such file or directory
/data/local/tmp/rage: /data/local/tmp/busybox: not found
cp: Permission denied
cp: Permission denied
Unable to chmod /system/xbin/su: no such file or directory
Mount: Operation not permitted
$
SO as i interpret this as I dont have the rights or permission to run the rage script. What puzzles me is the fact the it cannot "mount" the sdcard...after running this, I cannot take a picture (screenshot) bcs it does not recognize the sdcard. I have to Reboot.
Any ideas?
Thanks!
Crey23 said:
Up to here I am fine.
But is with this part that I have issues with......
Code:
$ /data/local/tmp/rage
/data/local/tmp/rage: /data/local/tmp/busybox: permission denied
mount: Operation not permitted
mkdir failed for /system/xbin, Read-only file system
/data/local/tmp/rage: /data/local/tmp/busybox: permission denied
Unable to chmod /system/xbin/busybox: no such file or directory
/data/local/tmp/rage: /data/local/tmp/busybox: not found
cp: Permission denied
cp: Permission denied
Unable to chmod /system/xbin/su: no such file or directory
Mount: Operation not permitted
$
Click to expand...
Click to collapse
I think there's something majorly wrong here. Funny, I saw someone else with a similar problem recently. It looks like when you're running "rage" it's actually running the "root" script that you use at a later stage, and not "rage" at all. Double check what you've got, I think "rage" is a binary and not a script. Are you sure you didn't push "root" to "rage" ?

Cant Run ADB Commands

Im trying to downgrade my Desire Z. Using this code:
Code:
adb push psneuter /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/psneuter
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/psneuter
adb shell
When i type:
adb push psneuter /data/local/tmp
I get this message:
cannot stat 'psneuter': No such file or directory
I then tried to push the same file if i added .txt at the end of psneuter.
This still did not work.
I then typed cd [directory] and tried it (without .txt) and it still did not work.
I then tried it with .txt and it works.
So i had to cd the directory and then add the file extension? Guessing this isn't normal, but i could deal with it.
However when i got to the third line, i don't know the file extension of misc_version, so i was unable to continue. Can anyone shed some light please? What am i doing wrong or what haven't i done?
Thanks
NthZ said:
Im trying to downgrade my Desire Z. Using this code:
Code:
adb push psneuter /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/psneuter
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/psneuter
adb shell
When i type:
adb push psneuter /data/local/tmp
I get this message:
cannot stat 'psneuter': No such file or directory
I then tried to push the same file if i added .txt at the end of psneuter.
This still did not work.
I then typed cd [directory] and tried it (without .txt) and it still did not work.
I then tried it with .txt and it works.
So i had to cd the directory and then add the file extension? Guessing this isn't normal, but i could deal with it.
However when i got to the third line, i don't know the file extension of misc_version, so i was unable to continue. Can anyone shed some light please? What am i doing wrong or what haven't i done?
Thanks
Click to expand...
Click to collapse
Sounds like you didn't set your path; either set a path to adb or make sure all the files are in the same directory of adb and run the commands from that directory
Sent from my T-Mobile G2 using XDA App
OriginalGabriel said:
Sounds like you didn't set your path; either set a path to adb or make sure all the files are in the same directory of adb and run the commands from that directory
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
i thought i did set a path though. and it doesn't explain why i need to add the file extension...or is that normal?
can you remind me how to set a path please? i went to computer and path>edit then added the directory of platform-tools and tools to the list. is that all thats needed? where should i save the files such as psneuter?
thanks
All I do is rip out the needed adb files and put them in a folder on my dekstop. Then you can push the files you need to your device.
Sent from my SCH-I500 using Tapatalk
NthZ said:
i thought i did set a path though. and it doesn't explain why i need to add the file extension...or is that normal?
can you remind me how to set a path please? i went to computer and path>edit then added the directory of platform-tools and tools to the list. is that all thats needed? where should i save the files such as psneuter?
thanks
Click to expand...
Click to collapse
Sounds like you added the path correctly; if you did, you should be able to run adb from anywhere. It doesn't matter where the files are on your computer, what matters is that you're running the commands from that folder.
For example, if all the files are in C:\root_files then when you open up a command prompt, you need to type 'cd C:\root_files', hit enter and then run the adb commands from there.
Sent from my T-Mobile G2 using XDA App
Can you not drag and drop the files into the terminal in Windows like you can on Mac?
thanks for all the comments. will have another go tomorrow.
i made another thread but no one has answered, my desire z is running android 2.2.1. do i need to downgrade to 2.2, then 1.74, then 1.34 to root it, or can i go straight from 2.2.1 to 1.34?
Thanks
The 2.2.1 is android version, not sense version.
You need to downgrade to 1.34 sense version, which is also running 2.2 I think.
-Nipqer
i solved the above problem but now have a new problem.
After i typed "adb shell /data/local/tmp/psneuter"
to try and get temporary root, i got this message: /data/local/tmp/psneuter: permission denied
I googled about a bit and tried another command:
C:\Root_Files>adb shell
adb server is out of date. killing...
* daemon started successfully *
$ cd /data/local/tmp
cd /data/local/tmp
$ chmod 0755 psneuter
chmod 0755 psneuter
$ ./psneuter
./psneuter
property service neutered.
killing adbd. (should restart in a second or two)
Then tried adb shell again.
It granted me root access, but i figured i'd try and stick to the tutorial i was on.
so i went back and typed adb shell /data/local/tmp/psneuter again, and now i get this message:
mmap() failed. Operation not permitted
however if i typed "adb shell" i get #.

Bootanimations for Suzuran

Hi there,
here comes my collection of bootanimations for Suzuran. Maybe they are useful for other devices?
Klick
bootanimation_Berni.zip: My used one
bootanimation_google.zip: From Google inspired, minimal and playful one
bootanimation_lineage.zip: The one from LineageOS team
bootanimation_stock.zip: The original one from Stock ROM 7.x
How to change the current bootanimation?
Enter these commands line by line:
Code:
adb root
adb shell
mount -o remount,rw /
exit
adb push <name_of_bootanimation_file> /system/media/bootanimation.zip
exit
Reboot.
If you want to save your current bootanimation file, you should perform this command FIRST:
Code:
adb pull /system/media/bootanimation.zip
Berni-0815 said:
Hi there,
here comes my collection of bootanimations for Suzuran. Maybe they are useful for other devices?
Klick
bootanimation_Berni.zip: My used one
bootanimation_google.zip: From Google inspired, minimal and playful one
bootanimation_lineage.zip: The one from LineageOS team
bootanimation_stock.zip: The original one from Stock ROM 7.x
How to change the current bootanimation?
Enter these commands line by line:
Code:
adb root
adb shell
mount -o remount,rw /
exit
adb push <name_of_bootanimation_file> /system/media/bootanimation.zip
exit
Reboot.
If you want to save your current bootanimation file, you should perform this command FIRST:
Code:
adb pull /system/media/bootanimation.zip
Click to expand...
Click to collapse
bootanimation.zip: 1 file pushed, 0 skipped. 436.3 MB/s (1496312 bytes in 0.003s)
but it still the same animation as before. renamed it to bootanimation
tarukanav said:
1496312 bytes
Click to expand...
Click to collapse
That's the file size of the bootanimation file from LineageOS team (see attached picture). I've tested every one of those four files and everytime after reboot I've gotten the wanted result.
You're doing something wrong!
Berni-0815 said:
That's the file size of the bootanimation file from LineageOS team (see attached picture). I've tested every one of those four files and everytime after reboot I've gotten the wanted result.
You're doing something wrong!
Click to expand...
Click to collapse
yea that am doing something wrong is the thing i cant figure out
Is every command executed successfully?
Code:
adb root
adb shell
mount -o remount,rw /
exit
adb push bootanimation_google.zip /system/media/bootanimation.zip
exit
There should be not one single error message:
Code:
[email protected]:~/Tmp$ adb root
restarting adbd as root
[email protected]:~/Tmp$ adb shell
suzuran:/ # mount -o remount,rw /
suzuran:/ # exit
[email protected]:~/Tmp$ adb push bootanimation_google.zip /system/media/bootanimation.zip
bootanimation_google.zip: 1 file pushed. 18.4 MB/s (1858574 bytes in 0.097s)
[email protected]:~/Tmp$
And after a reboot I can see this Google inspired animation.
Edit: Have you executed the "exit" command after the "mount" command?
Berni-0815 said:
Is every command executed successfully?
Code:
adb root
adb shell
mount -o remount,rw /
exit
adb push bootanimation_google.zip /system/media/bootanimation.zip
exit
There should be not one single error message:
Code:
[email protected]:~/Tmp$ adb root
restarting adbd as root
[email protected]:~/Tmp$ adb shell
suzuran:/ # mount -o remount,rw /
suzuran:/ # exit
[email protected]:~/Tmp$ adb push bootanimation_google.zip /system/media/bootanimation.zip
bootanimation_google.zip: 1 file pushed. 18.4 MB/s (1858574 bytes in 0.097s)
[email protected]:~/Tmp$
And after a reboot I can see this Google inspired animation.
Edit: Have you executed the "exit" command after the "mount" command?
Click to expand...
Click to collapse
yes , had no error messages, had same thing once before cant rememeber how i fixxed it .Also tried to just copy it with rootexplorer and same thing copies fine , but animation stays same
Which OS are you using at your device?
Berni-0815 said:
Which OS are you using at your device?
Click to expand...
Click to collapse
win10 ,but i know there was something else am doing wrong, had same situation a while ago but cant remember how i fixed it , tried to use different apps to change bootanimation and nothing worked , at the end it was something simple just cant remember what it was
No. Not the OS of your computer, the OS of your z5c.
I'm using los18. Maybe with other OS's this is not working?
hhe android is also 10, so los 17
I've flashed los17.1 yesterday and the changing of the bootanimation works flawlessly; as expected.
ook soo am just stupid as hell ,copied bootanimation.zip to just bootanimation.

Categories

Resources