EDIT: SOLVED
I just flashed the latest ROM but when I enable debugging and type "adb shell" im getting "$" instead of "#"...? I'm trying to remount the filesystem "mount -o rw,remount /dev/block/mtdblock3 /system" but am getting access denied because of this.
Do I need to try reflashing?
you need to adb shell then type "su" to get to a root shell i believe
EDIT: SOLVED! I was too blind to notice i had to allow the root request on my phone. thanks!
after i type 'adb shell' and get "$" everything i type next just gets echoed
ex:
Code:
$ su
su
test
test
etc
gohamstergo said:
EDIT: SOLVED! I was too blind to notice i had to allow the root request on my phone. thanks!
after i type 'adb shell' and get "$" everything i type next just gets echoed
ex:
Code:
$ su
su
test
test
etc
Click to expand...
Click to collapse
Usually if you have root, adb shell will automatically grant root access...the notification on the phone is a new one to me...
xsnipuhx said:
Usually if you have root, adb shell will automatically grant root access...the notification on the phone is a new one to me...
Click to expand...
Click to collapse
It seems to be caused by the "Superuser Permissions" app, included with the ROM
Related
Hey all,
I'm trying to create a linux script that executes some adb commands. For example, I would like it to be able to automatically exchange nv_data.bin (which need 'su' rights as you certainly know). The problem begins here:
if I execute command: 'adb shell cp x.x y.y' is fine,
but 'adb shell su cp x.x y.y' is just now working.
So I would need help with this. How can I make it work? I tried adb shell & su and stuff like this, but just did not work... THanks in advance!
94kram01 said:
Hey all,
I'm trying to create a linux script that executes some adb commands. For example, I would like it to be able to automatically exchange nv_data.bin (which need 'su' rights as you certainly know). The problem begins here:
if I execute command: 'adb shell cp x.x y.y' is fine,
but 'adb shell su cp x.x y.y' is just now working.
So I would need help with this. How can I make it work? I tried adb shell & su and stuff like this, but just did not work... THanks in advance!
Click to expand...
Click to collapse
adb shell su -c ls
Thanks! It seems to work, but somehow it just did not ask for permission on the phone, so returns 'Permission denied.' I checked phone, but it didn't ask me if I want to enable or not.
Try
Code:
adb shell su -c "ls" -root
Hm, now it asks for it. Thanks! Is it possible, to ask for permission only once, at the beginning, and then be able to do everything?
94kram01 said:
Hm, now it asks for it. Thanks! Is it possible, to ask for permission only once, at the beginning, and then be able to do everything?
Click to expand...
Click to collapse
I'd think if u call it with -root it should only ask once.
Not sure though.
If it asks more than once, could you push a script to the device (somewhere that normally has full r/w access), run it with a single command, then delete it?
I trying to downgrade in order to root my phone. I am stock in the command prompt with adb shell cat/dev/msm_rotator. I know I should get dev/msm_rotator: invalid length, but i get permission denied. I searched in the internet and i havent found a solution. Please someone help me and i want to root my phone. I wil be very very thankful.
do you actually see your phone trough adb?
type "adb devices" to see if your phone shows up... and did you enable usb debugging?
Yes I did. When I check adb devices I got my serial number. My phone is in debugging too and nothing all I got is permission denied
hm... strange
from your posting i see this: adb shell cat/dev/msm_rotator
but it should be: adb shell cat /dev/msm_rotator ...there is a space between cat and /dev
hoffmas said:
hm... strange
from your posting i see this: adb shell cat/dev/msm_rotator
but it should be: adb shell cat /dev/msm_rotator ...there is a space between cat and /dev
Click to expand...
Click to collapse
yeah, the way he has it there is no valid command and cat is being referred to as if its a folder
Might also be trying to run 'adb shell cat /dev/...' inside adb shell, which would throw a permission denied error.
-Nipqer
when I type cat /dev/msm_rotator/ i get no such file in directory.
Yes I did it. I was putting \ instead of / noob error, but thank you to all that help me.
grdo said:
Yes I did it. I was putting \ instead of / noob error, but thank you to all that help me.
Click to expand...
Click to collapse
Glad it worked out Don't feel too bad! I STILL get backslash/fowardslash mixed up sometimes lol
[Q] After entering "adb shell", it returns "sh-4.1$" instead only "$"
After entering "adb shell", it returns "sh-4.1$" instead only "$".
What does this mean?
And when I type "mount -o rw, remount /system", it returns "sh: mount: command not found".
When I type "su", it returns "sh: su: command not found"
I am running on ...0089_ROW and I lose root after update
What does this **** means?
I could be wrong, but pretty sure it's a strong reminder you don't have root. I'm not well-versed, but I thought you needed root to use adb.
Yes, I don't have root.
I've tried to update with temp unroot via Rootkeeper and now i cannot take my root back.
I have su-backup in /system, but OTA Rootkeeper just say "su backup restored".
But root isn't restored.
That's while I try to take my root back via adb.
Оbviously I must wait for ICS, I don't know.
Addition, my DHCP server doesn't work and when I what to connect to WiFi I must enter manually everythink (IP,DNS etc)
I cannot find any solution to my problems in the most popular forums.
Sorry I can't help. I'm lucky to have root through the efforts of others.
Which Rom are you on now?
I'm now on A400_03_0069_0121_ROW
Sorry for the late answer!
There's no hope for me
I have bricked my device when I tried to copy framework-res.apk to the system folder. I renamed the old framework-res.apk to framework-res.apk.bak but before I could paste the new one the phone freaked out and rebooted and now I'm stuck at the ATT white screen. I have adb access though so I'm hoping I can just push the framework-res file using adb. Every time I try this though I get an error saying file system is read only. I know all I probably need to do is get the computer to mount system as read/write. I just don't know how to do this. Is there anyone out there who can help me out?
Modified from:
http://forum.xda-developers.com/showthread.php?p=41339365
You may need to do:
mount -o remount,rw /system
chmod 777 /system/framework
Thank you for your quick reply. I'm kind of a novice when it comes to adb so bear with me, but when I use those commands I get 'mount' is not recognized as an internal or external command. I'm not sure if it matters or not but I'm running windows XP and my working directory is in c:\android-sdk\platform-tools when I tried executing "mount -o remount,rw /system".
Okay I tried changing the command to "adb shell mount -o remount,rw /system" now I get the error mount operation not permitted. I hope this doesn't mean I borked it. . . Also want to note that I did root the phone.
jack_slapped said:
Thank you for your quick reply. I'm kind of a novice when it comes to adb so bear with me, but when I use those commands I get 'mount' is not recognized as an internal or external command. I'm not sure if it matters or not but I'm running windows XP and my working directory is in c:\android-sdk\platform-tools when I tried executing "mount -o remount,rw /system".
Click to expand...
Click to collapse
You need to do some reading before you go any further - please. ADB is a command shell, and the commands he gave you are for running IN ADB after it's successfully connected to the phone.
There are lots of good writeups on using ADB all over the place.
jack_slapped said:
Okay I tried changing the command to "adb shell mount -o remount,rw /system" now I get the error mount operation not permitted. I hope this doesn't mean I borked it. . . Also want to note that I did root the phone.
Click to expand...
Click to collapse
You need to get INTO the shell first -- then execute the commands.
Also, always stop the system before modifying stuff, especially framework!
like so:
Code:
> [B]adb shell[/B]
$ [B]su[/B]
# [B]mount -o rw,remount /system[/B]
# [B]stop[/B]
# **[I]cp or mv whatever here[/I]**
# [B]reboot[/B]
your cmd prompt will return after reboot
alacrify said:
You need to do some reading before you go any further - please. ADB is a command shell, and the commands he gave you are for running IN ADB after it's successfully connected to the phone.
There are lots of good writeups on using ADB all over the place.
Click to expand...
Click to collapse
I know believe me when I say I'm trying to read as much as I possibly can. Nobody wants this phone fixed more than me. It's just alot of new stuff and I'm not entirely familiar with it. I think I'm connected with adb and started a shell using "adb -s myserial shell". I input the first command and got "mount: operation not permitted". Not really sure why it would say that considering I rooted the device.
jack_slapped said:
I know believe me when I say I'm trying to read as much as I possibly can. Nobody wants this phone fixed more than me. It's just alot of new stuff and I'm not entirely familiar with it. I think I'm connected with adb and started a shell using "adb -s myserial shell". I input the first command and got "mount: operation not permitted". Not really sure why it would say that considering I rooted the device.
Click to expand...
Click to collapse
Be sure to follow gwbard's directions a little closer. The first command inside the ADB shell is "su" which will elevate you to root - this will be necessary in order to execute the "mount" command.
From your command line (assuming in Windows), you'll run the "adb shell" command that gwbard showed. It should give you a prompt that ends with a dollar sign. Once you execute the "su" command, you'll see that change to a pound/hash sign (#).
gwbard said:
You need to get INTO the shell first -- then execute the commands.
Also, always stop the system before modifying stuff, especially framework!
like so:
Code:
> [B]adb shell[/B]
$ [B]su[/B]
# [B]mount -o rw,remount /system[/B]
# [B]stop[/B]
# **[I]cp or mv whatever here[/I]**
# [B]reboot[/B]
your cmd prompt will return after reboot
Click to expand...
Click to collapse
Dude you are the man! That did the trick. I really appreciate it. I'm still trying to figure out exactly what a shell is and how that ties into adb but I learned a good bit about it from today. I've used linux before and I have heard of a shell but never really understood what exactly it was. Anyways thanks again for everyone who helped me get this working.
Aou said:
Be sure to follow gwbard's directions a little closer. The first command inside the ADB shell is "su" which will elevate you to root - this will be necessary in order to execute the "mount" command.
From your command line (assuming in Windows), you'll run the "adb shell" command that gwbard showed. It should give you a prompt that ends with a dollar sign. Once you execute the "su" command, you'll see that change to a pound/hash sign (#).
Click to expand...
Click to collapse
Yea I posted that last one before I saw his instructions. They were right on point. Thanks guys!
jack_slapped said:
Dude you are the man! That did the trick. I really appreciate it. I'm still trying to figure out exactly what a shell is and how that ties into adb but I learned a good bit about it from today. I've used linux before and I have heard of a shell but never really understood what exactly it was. Anyways thanks again for everyone who helped me get this working.
Click to expand...
Click to collapse
When you click "start" and type "cmd", you're starting a shell. They're command interpreters that extend functionality in specific ways. like "dir" for the Windows/DOS command shell, and "su" or "mount" for adb. Lots of good writeups on that around too
Recently my phone got back from warranty with a retail board (don't know if it's relevant), so I had to do all the unlocking and rooting things. but all the times that I changed custom roms my phone only booted if I went to bootloader and pressed start, any other way it boots directly into rcovery mode.
actualy using Ressurection Remix (Pie) no root.
redejcr said:
Recently my phone got back from warranty with a retail board (don't know if it's relevant), so I had to do all the unlocking and rooting things. but all the times that I changed custom roms my phone only booted if I went to bootloader and pressed start, any other way it boots directly into rcovery mode.
actualy using Ressurection Remix (Pie) no root.
Click to expand...
Click to collapse
In ADB shell type
Code:
adb shell dd if=/dev/zero of=/dev/block/platform/soc/7824900.sdhci/by-name/misc
[email protected] said:
In ADB shell type
Code:
adb shell dd if=/dev/zero of=/dev/block/platform/soc/7824900.sdhci/by-name/misc
Click to expand...
Click to collapse
Only shows permission denied even if adb interface was authorized.
redejcr said:
Only shows permission denied even if adb interface was authorized.
Click to expand...
Click to collapse
You can root it, and get permission, or.... add "sudo", or "su" command to beginning of command shell. Haven't done it without root, but that should get you root permission for bash shell. Something like this
Code:
adb shell su -c "your command here"
[email protected] said:
You can root it, and get permission, or.... add "sudo", or "su" command to beginning of command shell. Haven't done it without root, but that should get you root permission for bash shell. Something like this
Code:
adb shell su -c "your command here"
Click to expand...
Click to collapse
Yeap, that worked, thanks a lot. You saved me from this headache.
The only diference is that I had to root AND add su to the command.