I'm using the adb.exe command directly from the Android SDK to connect to my Xperia X10's file system. Here are the commands I issued:
D:\android_sdk\tools>adb shell
$ cd data/app-private
cd data/app-private
$ ls
ls
opendir failed, Permission denied
$ su
su
pwd
pwd
ls -l
ls -l
Permission denied
$ /data/app-private
$ opendir failed, Permission denied
$ exit
exit
D:\android_sdk\tools>
Two questions: 1) Why is it commands entered after typing "su" are echoed? 2) How come I can't browse the app-private directory even after entering su?
Thanks.
Have you rooted your X10 ? (think not)
A # prompt indicates superuser privileges, you did not get to be a superuser.
Why you get an echo I don't know.
mattiL said:
Have you rooted your X10 ? (think not)
A # prompt indicates superuser privileges, you did not get to be a superuser.
Why you get an echo I don't know.
Click to expand...
Click to collapse
Yes the phone is rooted. I have the AT&T branding, but used the one-click exploid to root the phone, and it works as Titanium Backup when running tells me it gained Superuser priviledges. I don't know what I'm doing wrong. This is from an MS-DOS prompt in Windows.
When you use SU for the first time, you need to have the phone screen on and unlocked. It will ask for superuser permissions. Then it will work.
naplesbill said:
When you use SU for the first time, you need to have the phone screen on and unlocked. It will ask for superuser permissions. Then it will work.
Click to expand...
Click to collapse
Ha, thanks, it worked. The key was typing SU just before I unlock the phone, then it asks me on the phone that "Unknown" wants superuser access. Thanks again.
I was finally able to apply the 'Enable Non-Market apps' fix via adb thanks to this little tip
I'm learning- slowly...
How exactly do I run scripts on this phone when connected to a PC?
Code:
C:\android_sdk\tools>adb shell
$ su
su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
# cd sdcard
cd sdcard
# ls -l testscript.sh
ls -l testscript.sh
----rwxr-x system sdcard_rw 54 2010-10-06 10:52 testscript.sh
# sh testscript.sh
sh testscript.sh
: not foundsh: ■#!/bin/sh
: not foundsh: /sh
: not found
mkdir <target>
#
Any ideas?
If anyone told me "You should save your files in UNIX format where each text line ends in 0x0A, and not 0x0D 0x0A as in Windows, it will work" ... you'd be right. UNIX doesn't like carriage return & line feed pairs when trying to run a shell script.
First off I'm not a Dev just a guy with a Mac and to much time on his hands. So use with caution. Secondly I'm not really positive on the exact steps take because of multiple mistakes and attempts. So this is how I think it all went down.
1) Unistall Lagfix
2) Download http://dl.dropbox.com/u/458252/Fasci...Mfascinate.zip disregard the read me its missing steps i'll try to hit here.
3) drop the zimage file on the sdcard.
4) put the redbend_ua in the tools folder of the sdk.
5) open terminal
$ cd ..
$ cd ..
$ cd and*
$ cd tools
$ ./adb push redbend_ua /data/local
$ ./adb shell
$ cd /data/local/tmp
$ chmod 0755 rage.bin
$ ./rage.bin
Wait for rage.bin to complete. When it's finished you should be back in the tools folder again as shown below.
your computer name: tools your user name$ ./adb shell
# mount -t rfs -o remount,rw /dev/block/stl9 /system
# cd /data/local
# chmod 755 redbend_ua
# ./redbend_ua restore /sdcard/zImage /dev/block/bml7
lots of stuff and your phone restarts…
quit terminal (don't know if its necessary)
recopy zimage to sdcard. yes overwrite.
open terminal (I did the whole rage.bin thing a couple times through this whole fiasco, im not sure if its nessecary, just get remounted..)
# cd ..
# cd ..
# cd and*
# cd tools
#./adb shell
# mount -t rfs -o remount,rw /dev/block/stl9 /system
# cd /data/local
# chmod 755 redbend_ua
# ./redbend_ua restore /sdcard/zImage /dev/block/bml8
more stuff phone restarts again.
market download rom manager. cwrecovery flash for fascinate, back up current rom and you're good.
If guys are having trouble I'll try and answer questions, but this was trial and error for me. if I missed something and someone figures it out let me know so I can update the tutorial.
I've found a pretty simple way to do it as well, without so much stuff and less download even. This is if you have adb/android tools installed with a bash profile and you're in the folder with redbend and zimage.
1. Install ROM Manager and "flash" CWM. Mount your sdcard
2. adb push redbend_ua /data/local
3. adb push zImage /data/local
4. adb shell
5. su
6. chmod -R 755 /data/local
7. cd /data/local
8. ./redbend_ua restore ./zImage /dev/block/bml7
Phone reboots, remount sdcard to comp
1. adb shell
2. su
3. cd /data/local
4. ./redbend_ua restore ./zImage /dev/block/bml8
I actually had to use a bit of both of your posts to get mine working. These are the steps I followed:
Copy zImage to the root folder of your SD Card
Open Terminal
$ cd (path to android sdk)/tools
$ ./adb push (path to redband_ua)/redbend_ua /data/local
$ ./adb shell
$ cd /data/local/tmp
$ chmod 0755 rage.bin
$ ./rage.bin
(username)$ ./adb shell
# mount -t rfs -o remount,rw /dev/block/stl9 /system
# cd /data/local
# chmod 755 redbend_ua
# ./redbend_ua restore /sdcard/zImage /dev/block/bml7
--Phone Reboots--
$ ./adb shell
$ su
# cd /data/local
# ./redbend_ua restore /sdcard/zImage /dev/block/bml8
Thank you kindly for all your efforts peeps. Not sure it's quite dummy-proof enough for my implementation yet but I'm glad this ball is rolling.
Haven't had a Windows machine in a while, tried running a virtual machine but wouldn't recognize my phone after I installed the Samsung drivers. BootCamp...meh...
I'm pretty sure there's an easier way. It's hard to find the exact steps on a phone that's already hacked with cwrecovery.
I'm pretty sure I could compile some solid instructions based off of what everyone posted, but I'd rather go through the process myself before I write something up for others to use. The only thing stopping me is the question of having Clockwork installed and receiving an OTA from Verizon? I'm also seeing that going back to stock requires Odin which requires a PC, which is not a huge deal, but it just seems like it'll be a pain in the ass to get back to stock if I need to - especially since I'm not doing anything drastic to my phone that'll require a backup.
Clockwork is recovery. It doesn't affect anything ota. And you wont have to use odin for messing up cwm unless you're a complete idiot.
Posted from my SCH-I500 (Samsung Fascinate with Voodoo @ 1200 MHz)
Gitykins said:
Clockwork is recovery. It doesn't affect anything ota. And you wont have to use odin for messing up cwm unless you're a complete idiot.
Posted from my SCH-I500 (Samsung Fascinate with Voodoo @ 1200 MHz)
Click to expand...
Click to collapse
I understand what Clockwork is used for. I just don't understand what exactly is happening when you flash bml7 and bml9 (or whatever mount points you flash). I'm curious as to whether flashing these have any effect on future updates in any way.
chrisw27 said:
I actually had to use a bit of both of your posts to get mine working. These are the steps I followed:
Copy zImage to the root folder of your SD Card
Open Terminal
$ cd (path to android sdk)/tools
$ ./adb push (path to redband_ua)/redbend_ua /data/local
$ ./adb shell
$ cd /data/local/tmp
$ chmod 0755 rage.bin
$ ./rage.bin
(username)$ ./adb shell
# mount -t rfs -o remount,rw /dev/block/stl9 /system
# cd /data/local
# chmod 755 redbend_ua
# ./redbend_ua restore /sdcard/zImage /dev/block/bml7
--Phone Reboots--
$ ./adb shell
$ su
# cd /data/local
# ./redbend_ua restore /sdcard/zImage /dev/block/bml8
Click to expand...
Click to collapse
Brilliant! it worked!!!
chrisw27 said:
I actually had to use a bit of both of your posts to get mine working. These are the steps I followed:
Copy zImage to the root folder of your SD Card
Open Terminal
$ cd (path to android sdk)/tools
$ ./adb push (path to redband_ua)/redbend_ua /data/local
$ ./adb shell
$ cd /data/local/tmp
$ chmod 0755 rage.bin
$ ./rage.bin
Click to expand...
Click to collapse
What am I doing wrong here? cd to the /tmp directory i get nothing after hitting enter.
MBP:tools BenjaminDover$ ./adb push /Users/BenjaminDover/Desktop/nixCWMfascinate/redbend_ua /data/local
596 KB/s (313888 bytes in 0.513s)
MBP:tools BenjaminDover$ ./adb shell
$ cd /data/local/tmp
$ chmod 0755 rage.bin
Unable to chmod rage.bin: No such file or directory
I just want to make a nandroid before loading a new ROM lol
do:
cd /data/local
^It was late and didn't even think to do a search for the file lol. My windows VM wasn't recognizing my Fascinate, Captivate or my friends' Vibrant anymore. I had to boot to my Bootcamp partition to finally get it recognized and just used the Odin method.
Thanks though
So you could at least throw a thank you to me for getting the files together, instead of just linking to my files.
Some peoples kids
CW issues
I select "Backup current ROM" and my phone immediate boots into recovery and if I try and apply the update.zip, it fails.
Any ideas??
I was really good at the Eris, but this one is mocking me
You've got to push rage.bin to your phone before you can run it. Like this (disregard unixisms, don't have a mac but its relevant):
[email protected]:~# ls
rage.bin Superuser.apk
[email protected]:~# adb push rage.bin /data/local/tmp
18 KB/s (5392 bytes in 0.277s)
[email protected]:~#
Now rage.bin is on your phone's internal memory, proceed with the chmod and execute steps.
Yeah, I have all that running and I have superuser and I even got su to not give me access denied.
The problem for me is when it tries to apply the zip in recovery, it fails.
Sent from my SCH-I500 using XDA App
help
hi,
I get to:
# mount -t rfs -o remount,rw /dev/block/st19 /system
and it just sits there. i've waited 10 minutes. is it supposed to take longer? sorry noob here.
Finally installed Clockworkmod - I know... welcome to last year
The instructions in the sticky say to follow the instructions in the readme.txt file in the .zip - as stated by the OP, the instructions in here are missing a few key things that would keep people from worrying during installation. The [Mac] information in the sticky should be updated with instructions from this post.
All the instructions provided helped with my installation, but I ran into an issue I didn't see posted anywhere.
Here are the steps I used:
Code:
[mac] $ cd <sdk_path>
[mac] $ ./adb push <zip_path>/redbend_ua /data/local/
[mac] $ ./adb push <zip_path>/zImage /sdcard/
[mac] $ ./adb shell
[adb] $ su
[adb] # cd /data/local
[adb] # chmod 755 redbend_ua
[adb] # ./redbend_ua restore /sdcard/zImage /dev/block/bml7
*** At this point, the phone screen goes black and says "System updated. Rebooting.." and the phone reboots.
What went different for me after this point is I had to disconnect the phone from the USB port to get it to be recognized by the SDK/adb. When I did get it to recognize, once I got into the shell adb would freeze and I couldn't type the last command. I rebooted the phone, tried different USB ports, restarted the SDK... same... adb would just freeze up and I couldn't type anything. When I run ./adb devices, it seems the phone disconnects itself after a while which is very strange.
From that point I just used the Terminal Emulator app to type the last few commands directly from the phone:
Code:
[term] $ su
[term] # cd /data/local
[term] # ./redbend_ua restore /sdcard/zImage /dev/block/bml8
Then the phone reboots again like it did the first time.
After this last command it seems my phone can keep its adb connection to the SDK again, which is good.
Thanks to everyone who put the instructions together. I didn't really have a need for Clockworkmod up to this point, but seeing as how the updates are taking forever to come from Samsung/Verizon I'd rather get some of these annoying bugs fixed myself instead of waiting until 2012 for a fix.
I have tried all the methods above and can't get this to work. After ./rage.bin completes it never returns to tools it was just a $ or #. Now after ./adb shell, in the first part, I get #, at one point I was getting $. I am a little confused and have attempted way to may times. Should I just find a PC or can someone help? I have attempted all methods in this forum. Yes I am rooted and no I have never put lagfix on my phone.
used deeznotes method and worked like a charm. Thanks.
I could successfully install Ubuntu 13.10 via Complete Linux Installer under Android 4.4.2 (on a Nexus 5). If I reboot and then open Ubuntu 13.10, everything works fine. But if I close Ubuntu and open it again (without reboot), I get:
[email protected]:/ $
[email protected]:/ $ cd /sdcard/ubuntu
[email protected]:/sdcard/ubuntu $ su
sh /data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh /sdcard/ubuntu/ubuntu.img
sh /data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh /sdcard/ubuntu/ubuntu.img
[email protected]:/storage/emulated/legacy/ubuntu # sh /data/dcom.zpwebsites .linuxonandroid/files/bootscript.sh /sdcard/ubuntu/ubuntu.img
/data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh[39]: dirname: not found
Checking loop device... FOUND
mount: mounting /dev/block/loop255 on /data/local/mnt failed: Device or resource busy
Error: Unable to mount the loop device!
1|[email protected]:/storage/emulated/legacy/ubuntu #
What is the problem?
Hear hear. Same issue Galaxy S5 g900r4. SELINUX is permissive(finally).
I'have rooted a Primux zeta 2 with Android 4.4.2. I can see what stuff is stored in my (internal/emulated) sdcard (/storage/sdcard0) and external one (/storage/sdcard1) using ls command in Terminal Emulator. But if I do su, I can't see it:
[email protected]:/ $ ls /storage/sdcard0/
Alarms
Android
....
[email protected]:/ $
[email protected]:/ $ su -
[email protected]:/ # ls /storage/sdcard0/
(empty)
[email protected]:/ #
Hi all,
im using a rooted samsung galaxy note 3 with lollipop
i have installed tasker to automate a few things ...
in addition i have installed the app "secure settings" to open the lookscreen
because of the message from secure settings in "System+ Module", that "Root access was not detected. The System+ module requires root access to function, i try the following:
Found on https://www.reddit.com/comments/3uf5bn ....
---------------------------------
adb shell
su
mount -o remount,rw /system
touch /sbin/su /system/bin/su /system/xbin/su
mount -o remount,ro /system
exit
reboot
---------------------------
im using Android Debug Bridge version 1.0.41
Version 28.0.3-5475833 <-- i think that's the latest version
C:\adb>adb shell
[email protected]:/ $ su
[email protected]:/ # mount -o remount,rw /system
[email protected]:/ # touch /sbin/su /system/bin/su /system/xbin/su
touch: usage: touch [-alm] [-t YYYYMMDD[.hhmmss]] <file>
1|[email protected]:/ # exit
1|[email protected]:/ $ exit
C:\adb>adb shell
[email protected]:/ $ su
[email protected]:/ # mount -o remount,rw /system
[email protected]:/ # touch /sbin/su /system/bin/su /system/xbin/su <-- don't work
touch: usage: touch [-alm] [-t YYYYMMDD[.hhmmss]] <file>
1|[email protected]:/ # exit
1|[email protected]:/ $ exit
C:\adb>adb shell
[email protected]:/ $ su
[email protected]:/ # touch /sbin/su <-- tried single step
255|[email protected]:/ # < -- is that the problem?
----------------------------
please help me ....
thanks Mikel