[Q] permission denied error - Galaxy S I9000 Q&A, Help & Troubleshooting

every time i use this code in adb
adb shell
cd /dev/block
dd if=/dev/block/bml3 of=/sdcard/bml3.bak
copy to sdcard / upload
i get a "/dev/block/blm3: cannot open for read: permission denied"
what did i do wrong? my phone is unock i have a app called superuser and busybox
Thanks in advance

Type "su" first. You need super user permission, i.e. your phone must be rooted.

i tried that it gives me the error after
cd /dev/block
Edit: i just spamed the code and now it work but i gives me error "cannot open for read: no such file or directory"
Edit: when i use the su command i get a permission denied error. and everything afterwords. i have the superuser app and the busybox app i used the one - click rogram to unlock my samsung galaxy s i9000m from bell. i also updated to the latest firmware could that be the issue? it seems like i can look into the file(using astro file manager) and see that the file exists but i cant read or write to it.
ahh seems like superuser wasnt updated to 2.3.3 .... got it thanks man

From your phone, not adb, try:
Code:
su
dd if=/dev/block/bml3 of=/sdcard/bml3.bak
Then connect your phone to your PC and copy bml3.bak manually.

Related

Rooting

Alright, so I've used the SuperOneClick application to root my phone, which tells me was done successfully, however, I don't seem to be able to access files in the system folder through adb.
Is there some way I can positively confirm whether my phone is or isn't actually rooted? Like I said I was using adb to push a file into the system folder, and was given a permission denied message. At this time the only thing I'm attempting to do to the phone is this:
/showthread.php?t=820749&page=3
It seems pretty basic and it's my first android phone, so I'm starting off small here..
Using the leaked 2.2 FW, other than the being rooted (attempted), the phone is stock 2.2..
cryo.burned said:
Alright, so I've used the SuperOneClick application to root my phone, which tells me was done successfully, however, I don't seem to be able to access files in the system folder through adb.
Is there some way I can positively confirm whether my phone is or isn't actually rooted? Like I said I was using adb to push a file into the system folder, and was given a permission denied message. At this time the only thing I'm attempting to do to the phone is this:
/showthread.php?t=820749&page=3
It seems pretty basic and it's my first android phone, so I'm starting off small here..
Using the leaked 2.2 FW, other than the being rooted (attempted), the phone is stock 2.2..
Click to expand...
Click to collapse
Do you have the "superuser" app on your phone?
cryo.burned said:
Alright, so I've used the SuperOneClick application to root my phone, which tells me was done successfully, however, I don't seem to be able to access files in the system folder through adb.
Is there some way I can positively confirm whether my phone is or isn't actually rooted? Like I said I was using adb to push a file into the system folder, and was given a permission denied message. At this time the only thing I'm attempting to do to the phone is this:
/showthread.php?t=820749&page=3
It seems pretty basic and it's my first android phone, so I'm starting off small here..
Using the leaked 2.2 FW, other than the being rooted (attempted), the phone is stock 2.2..
Click to expand...
Click to collapse
If you type:
adb shell
su (after hitting enter, you should get a popup on your phone asking for superuser permission, click allow)
If you see this:
C:\Users\*yournamehere*>adb shell
$ su
su
#
Then you have root permissions.
TheRomero09 said:
Do you have the "superuser" app on your phone?
Click to expand...
Click to collapse
Yes, I have it on my phone
miztaken1312 said:
If you type:
adb shell
su (after hitting enter, you should get a popup on your phone asking for superuser permission, click allow)
If you see this:
C:\Users\*yournamehere*>adb shell
$ su
su
#
Then you have root permissions.
Click to expand...
Click to collapse
I have the app on my phone, but when I try this, I do not get a prompt for super user permissions, and the CL shell returns permission denied
EDIT: I was going to look at the superuser app to see what was in it to give you more info, but it the "app" that I assume is actually my computer had denied permissions. After changing it back to allow, the shell returns
Code:
su
#

Temp-root for IS on Android 2.3 without PC

I tested this and it work on Incredible S with Android 2.3!
Gingerbreak download here: http://forum.xda-developers.com/showthread.php?t=1044765
1. Copied v1.2 apk in a fresh sd card and installed it to phone.
2. ran the tool and clicked root
3. Message saying "Not sure what happened here..." came within like 30sec of clicking root.
4. waited for another 5-6 mins with the message on screen no crash no restart on the device.
5. Clicked Ok on the message and checked if i have a root(without a restart): SUCCESS!!!
Click to expand...
Click to collapse
If you get a get a permission denied error to copy files on /system partition
please type:
su
chmod 777 /system in terminal emulator
Pacjonek said:
I tested this and it work on Incredible S with Android 2.3!
Gingerbreak download here: http://forum.xda-developers.com/showthread.php?t=1044765
If you get a get a permission denied error to copy files on /system partition
please type:
chmod 777 /system/app in terminal emulator
Click to expand...
Click to collapse
This should not be used for temproot on a S-On device. You can't use your sdcard and it also makes a few apps unusable.
Please read the original thread carefully.

AIO ZV 8 rooter/CVM NOT WORKING.

I've followed EVERY GAWDAMN suggestion/guide/direction listed, and ZV8 refused to root/CWM for me.
Here's what the AIO says:
Root and Recovery for ZV8
Press any key to continue . . .
* daemon not running. starting it now *
* daemon started successfully *
Device found
Mounting Device
remount failed: Operation not permitted
Pushing Root Permissions
Unable to chmod /system/bin/su: No such file or directory
3720 KB/s (5345280 bytes in 1.403s)
Unable to chmod /system/xbin/busybox: Read-only file system
--install: applet not found
Installing CWM Recovery
/dev/block/mmcblk0p14: cannot open for write: Permission denied
Remove Trash
rm failed for /system/etc/install-recovery.sh, Read-only file system
rm failed for /system/recovery-from-boot.p, Read-only file system
rm failed for /data/local.prop, No such file or directory
CWM Recovery!!!
Just a note for MT. I wish the process were a bit more visible, as I've had to manually push things with adb before on rooting attempts.
I've spent 3 days trying to get this piece of sh!t rooted, and I'm tired of it.
I've followed EVERY DIRECTION/GUIDE/INSTRUCTION to the T, and still nothing, so a hearty STFU if all you can offer is a "Did you follow the directions?"
On the "Regain Root after update" post there is talk of using a terminal emulator to make the root stick on V8. The only thing that worked for me is the post at the top of page 7 (or 8?) that has about 8 steps. If you haven't already tried it.
Sent from my BROKEN OUT VS910
antiwesley said:
I've followed EVERY GAWDAMN suggestion/guide/direction listed, and ZV8 refused to root/CWM for me.
Here's what the AIO says:
Root and Recovery for ZV8
Press any key to continue . . .
* daemon not running. starting it now *
* daemon started successfully *
Device found
Mounting Device
remount failed: Operation not permitted
Pushing Root Permissions
Unable to chmod /system/bin/su: No such file or directory
3720 KB/s (5345280 bytes in 1.403s)
Unable to chmod /system/xbin/busybox: Read-only file system
--install: applet not found
Installing CWM Recovery
/dev/block/mmcblk0p14: cannot open for write: Permission denied
Remove Trash
rm failed for /system/etc/install-recovery.sh, Read-only file system
rm failed for /system/recovery-from-boot.p, Read-only file system
rm failed for /data/local.prop, No such file or directory
CWM Recovery!!!
Just a note for MT. I wish the process were a bit more visible, as I've had to manually push things with adb before on rooting attempts.
I've spent 3 days trying to get this piece of sh!t rooted, and I'm tired of it.
I've followed EVERY DIRECTION/GUIDE/INSTRUCTION to the T, and still nothing, so a hearty STFU if all you can offer is a "Did you follow the directions?"
Click to expand...
Click to collapse
Try booting into CWM the old-fashioned way (hold down button and power). When I went through all the steps, everything looked liked it failed and all I had was an unrooted ZV8. Even Root Checker said I was unrooted. But then I tried to manually boot into CWM, and it worked! I flashed the new rom, and superuser came with it! Might as well give it a try. There's the possibility that you end up wiping data if you don't actually have CWM, but it sounds like you don't really care at this point...
I went through 2 days of hell to get root. There are so many things to try but I think the one thing that worked for me was that after you root the stock V7 is to run titanium backup. When I ran it it said it had to change su access or something and then I rebooted and did this in a terminal program
su<enter>
echo 'ro.kernel.qemu=1' > /data/local.prop<enter>
but also made sure by then doing this:
cat /data/local.prop
if you don't see exactly the ro.kernel.qemu=1 redo it. I was surprised that I had it wrong but for some reason the terminal app missed characters sometimes.
-Keith
What a maroon.
Sent from my VS910 4G using Tapatalk
$ su
su
su: permission denied
$ echo 'ro.kernel.qemu=1' > /data/local.prop
echo 'ro.kernel.qemu=1' > /data/local.prop
cannot create /data/local.prop: permission denied
$
If you are able to have cwm breakout is rooted.
Sent from my Galaxy Nexus using xda premium
Thanks!
Thanks Antiwesley!
I had tried a few different times to get this working, your post below finally got it for me:
"LGNPST to ZV7.
Using AIO 1 LG Revo AIO, Root ZV7 ONLY.
Install "Rom Manager" (thanks to slimzim for this one)
Manually create local.prop as seen elsewhere in a few other versions of this kind of thing.
LGNPST to ZV8.
In a command prompt, 'adb remount'
'adb push su /system/bin/su'
'adb push superuser.apk /system/bin/superuser.apk'
'adb push busybox /system/bin/busybox'
Use AIO 2 to install CWM. It will error on a couple of things, don't panic. (one is an applet failure in the rooting process and the other are rm failures.) DO NOT USE OPTION #1! Only use Option #2!
Reboot.
Use Rom Manager's "Reboot Recovery" option and it boots straight into CWM.
(I had zero success using the hardware (power/down button) to boot into CWM.
Apply Broken Out 1.1
Back up while you're in CWM.
Reboot.
Enjoy ZV8."
The only thing I did differently was OTA to ZV8 rather than LGNPST. Also when I ran option two of AIO 2 I didn't get any errors.
The whole process took right around an hour.
Thanks again!
FYI I would have posted this in the dev section in the Regain Root thread but am lacking the posts to do so.
stinkyjak said:
$ su
su
su: permission denied
$ echo 'ro.kernel.qemu=1' > /data/local.prop
echo 'ro.kernel.qemu=1' > /data/local.prop
cannot create /data/local.prop: permission denied
$
Click to expand...
Click to collapse
koda1789 said:
Thanks Antiwesley!
I had tried a few different times to get this working, your post below finally got it for me:
"LGNPST to ZV7.
Using AIO 1 LG Revo AIO, Root ZV7 ONLY.
Install "Rom Manager" (thanks to slimzim for this one)
Manually create local.prop as seen elsewhere in a few other versions of this kind of thing.
LGNPST to ZV8.
In a command prompt, 'adb remount'
'adb push su /system/bin/su'
'adb push superuser.apk /system/bin/superuser.apk'
'adb push busybox /system/bin/busybox'
Use AIO 2 to install CWM. It will error on a couple of things, don't panic. (one is an applet failure in the rooting process and the other are rm failures.) DO NOT USE OPTION #1! Only use Option #2!
Reboot.
Use Rom Manager's "Reboot Recovery" option and it boots straight into CWM.
(I had zero success using the hardware (power/down button) to boot into CWM.
Apply Broken Out 1.1
Back up while you're in CWM.
Reboot.
Enjoy ZV8."
The only thing I did differently was OTA to ZV8 rather than LGNPST. Also when I ran option two of AIO 2 I didn't get any errors.
The whole process took right around an hour.
Thanks again!
FYI I would have posted this in the dev section in the Regain Root thread but am lacking the posts to do so.
Click to expand...
Click to collapse
I am having the problem Stinkjak is having. No matter how I try and copy the .prop into the /data folder. I get a message that says java.io.filenotfoundexception:/data/local.prop (permission denied). Can anyone crack this error?
Plumbert said:
I am having the problem Stinkjak is having. No matter how I try and copy the .prop into the /data folder. I get a message that says java.io.filenotfoundexception:/data/local.prop (permission denied). Can anyone crack this error?
Click to expand...
Click to collapse
Are you already on stock ZV7 and rooted? Use Root Explorer and go to /data and create new file, name it local.prop. Open in text editor, enter ro.kernel.qemu=1 then save it. If you can't do that in Root Explorer then you aren't rooted.

JB OTA Forgot to Update Superuser binaries but ES File Explorer has Root

I followed the steps here
http://forum.xda-developers.com/showthread.php?p=33774480
But I forgot to update the binaries... actually I did not know I had to click where I need to click in order to update the binaries. I opened SuperUser up and it never said I needed to update binaries like Supersu does. ES File Explorer and Voodoo OTA still has root. Anyway I can fix this issue?
I tried "RestoreRoot.zip" that was posted and it says:
"Have drivers installed, phone connected, and USB Debugging enabled in Develope
r Options."
4371 KB/s (380532 bytes in 0.085s)
failed to copy 'Superuser.apk' to '/system/app//Superuser.apk': Permission denie
d
/system/bin/sh: su: can't execute: Permission denied
"Rebooting..."
uid=2000(shell) gid=2000(shell) groups=1003(graphics),1004(input),1007(log),1009
(mount),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt)
,3003(inet),3006(net_bw_stats)
If the above id shows 0 then you are rooted. Press any key to exit.
I have the same problem, either upgrade to 3.1.1 binaries and only has the voodoo root and titanium, we can do?
"Have drivers installed, phone connected, and USB Debugging enabled in Develope
r Options."
failed to copy 'su' to '/system/bin//su': Permission denied
failed to copy 'Superuser.apk' to '/system/app//Superuser.apk': Permission denie
d
Unable to chmod /system/bin/su: Operation not permitted
"Rebooting..."
Click to expand...
Click to collapse
ok, well then, i dont think its going to work, but here what ive done... it might help
Restored with vodoo OTA rootkeeper, saying that root is back ! but not really lol
I've had es file explorer already rooted, so, i just copied the binary files and reboot ... nada ! was having root permission but was denied everytime automaticaly, so i reeponned the es file explorer, and cannont be granted for root acces
i oppened up the super user app, and unavailable to acces root doing the update ......
superuser status was : rwxr-xr-x : conflict (showed in red) -binary : ok (showed in green) - path : ok (showed in green aswell)....
So, that is probably why it wont allow me root acces to succesfully re-update the su binary trough the native way of the superuser.apk
so here what i've done....
Re-used vodoo to reset the root to the old binairies (wich is actually enough for adb to work as root), i've then changed superuser.apk permissions that was actually resseted to :rw-r-x-r-- .... <--- WTF ????
So changed that to : rwxr-xr-x and then, i copied the su binary to the corect place, and boom, voila, was able to set binary permission and use it as usual .....
So my guess is if you guys wont have root on an explorer, adb will have with the old binairies restored from vodoo, so you should be able to change permissions to the /system/app/superuser.apk to : rwxr-xr-x and see if something magic occured that will let you update via superuser.apk in a native way so you wont need to copy/paste the binary manually !
But what i find odd is that you have a permissions denied !
did you tried it with the OLD binairies in place from voodoo directly inside adb shell
if you just type adb shell : ittl go in $ and if u type su (hit enter) you should now see the lasp part of command line protocol changing to : #
Right ?
then you should be able to change permissions of the superuser app ? right ?
or am i completely lost in the dust !?
Edit : well, if you want to keep root on an old leaked, its your thing, but i would recomand THIS tutorial instead cause you have a real ROM through OTA now.... dont know if it will change anything, but i followed this one !
Partial Root Restore
I was able to restore root to my phone after the 4.1.1 update using the information in this thread...
http://forum.xda-developers.com/showthread.php?t=1911261
Basically, if you had a root backup before the update, you may still have partial root on your phone.
To verify...
adb shell
su
If you find yourself at the # prompt, not all hope is lost!
:fingers-crossed:
Regained root on my Atrix using this instructions
http://forum.xda-developers.com/showthread.php?p=35905543#post35905543

Issues With Installing Busybox

I've tried using the app from the android store, I even was able to install it through that by mounting /xbin using root explorer and then installing it. The problem with that is when I reboot my phone busybox is no longer installed. So I figure I can install it manually using the adb tools but therein lies the problem. I cannot execute the busybox binary from the data folder. These are my steps to trying:
Code:
adb shell
su
cd /data/local
mkdir busybox
exit
adb push busybox /data/local/busybox
adb shell
su
cd /data/local
chmod 755 busybox
cd /data/local/busybox
./busybox
sh: ./busybox: can't execute: Permission denied
And here I am stuck... btw the binary I downloaded was here: busybox dot net/downloads/binaries/latest/ (under 10 posts cant post links for some reason...) And I downloaded the armv71, which I'm assuming is the right architecture for the moto x. Maybe it's wrong but since the moto x uses a custom architecture, I have no idea what binary to use. Anyways any suggestions would be appreciated.
Well, you're trying to cd to the file rather than the directory containing the file. Not sure if that's the issue or not, but it surely isn't helping.
You have not turned write protect off. Run motowpnomo
Sent from my XT1060 using Tapatalk
Problem was that I was chmodding the directory instead of the binary also I was missing arguments and the directory of installation. (had to mount system as root as well).
Well I was able to get it to install but the problem is the write protection, when I reboot my phone all the files that were in the /system/xbin directory were gone. Unfortunately that program no longer exists, all links point to a "Page Not Found" page. I would rather not download it from an unofficial source so I'm sol unless I can install it through recovery but I have no idea how to go about doing that and I don't see any instructions.
Thanks for the help guys.
Well, I think this is new: just downloaded Stericson's BusyBox Pro installer (as usual) to my Moto X Play on 6.0 Marshmallow and it is asking for the unusual default installation path of "/su/bin". As you know, " system/xbin" or "system/sbin" are usually the preferred installation paths for BusyBox, so this change simply got me stuck in the process thinking where to install BusyBox. My first thought is BusyBox auto-choose where to be installed according to system characteristics and I should go on and just install where it is asking me to, but... I don't know. Does somebody have a similar experience?

Categories

Resources