Database Develop

[Q] permission denied error

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.

[Q] ADB shell how to access?

I have rooted but I have no clue on how to access the adb shell......or the teminal...

adb , you can go look for it in theunlocker.com .. terminal , you can use it from your tab .. its depend in what codes you wanna use..

What do you want to do? Give more information.

[Q] CM7.2 - no write permission in /system?

I had Emanon's ROM on it for a while, but it just came crashing down so I flashed CM7.2... boots a lot faster, seems a bit more stable.
But I used to have full access, and now I don't. How do I get it back? I just want to switch out the bootanimation.zip.
Came across this:
status_six said:
Hi there, you need to have s-off (aka security off or full root) to write to /system and /data with the device booted, i.e. using root explorer etc.
You can also do it with s-on, but you have to to that with your PC via cmd prompt and adb shell which is less convenient.
Great guide to getting s-off here, took me <10 mins!
http://forum.xda-developers.com/showthread.php?t=794314
Click to expand...
Click to collapse
I've just finished mucking around with a HTC, so I'm a bit confused, but I gather there's no fastboot mode on the Mini, so I can't see how I can access the phone's flash from the PC without using the ADB shell...
And I'm not sure s-on/off is even relevant to the Mini... halp!

Okay, I was able to do it with Absolute System; must have missed the SU prompt or suffered a system glitch when I was installing ES File Explorer.
Anyone know how I can grant SU privileges to ES?

Kimmoth said:
Okay, I was able to do it with Absolute System; must have missed the SU prompt or suffered a system glitch when I was installing ES File Explorer.
Anyone know how I can grant SU privileges to ES?
Click to expand...
Click to collapse
Go to the su app and grant the permission for ES

you are coming from HTC so I am clearing some points some of them are of-topic
no fastboot instead download mode
bootloaders are not locked so no s-on no s-off in Samsung devices
use Odin multidownloader to flash firmware through PC
never use rom manager on this mobile, else a brick will be waiting for you
galaxy mini is easily root able
just flash an update.zip in recovery and you will be rooted
after root to change something in system
type mount -o remount,rw /system then do whatever you want to
stock rom cannot be backed up with the help of cwm

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

Can't root my S5830 2.3.6 - tried everything.

Yesterday I installed Windows XP on my PC, cause I couldn't install phone drivers on 8.1. I downloaded Odin for S5830 and flashed a Polish 2.3.6 ROM (from updato.com) over the existing 2.1. Next I flashed 5.0.2.6 fix CWM. Then I realized, that to root my phone I need to have a stock recovery, so I flashed it and then rooted with root.zip. I ran the phone to look if there's a superuser app and there was, so I flashed the CWM back. When I wanted to upgrade the CWM (to flash custom ROMs) via terminal, I typed 'su' and it said that I don't have root access, so I installed an app to see if I have root and it said, that I don't. I tried everything to root my phone. I flashed the ROM again, did a factory reset. Every time I tried to root, it was like it's rooted but not or it failed to root. What I did wrong?

My guess is that the root.zip didn't install the su binary correctly(E.g. into the wrong path so that the vendor su binary is still called).
To verify that, you could try(from the terminal):
echo $PATH
That should show you a ":" seperated list of paths in which the shell(The thing running in the Terminal) looks for a binary.
You'd now need to go through every path in this list, and check for a su binary. If you find one, run it. For example:
ls /example/path/su
If this finds a file(indicated by it showing the filename, su), run it:
/example/path/su
If you find more than one su binary, chances are that one of them will work. If you don't find any su binary, the root.zip probably wasn't able to remount rw.
If you're a little more advanced, you could try rooting your phone manually(I needed to to this yesterday because I'm on linux):
Download SuperOneClick 2.3. The .zip contains a folder called exploits. These programs initially get you the root permissions. To use them, adb push them to /data/local/tmp (Because you have write and execute permissions there), and execute them. They either directly drop you to a root shell or restart the adbd with root permissions. Either way, you can then remount /system and copy the su binary from the SuperOneClick to your /system/bin and set the correct permissions. I can't really recommend this method unless you know what you're doing though.
Good luck!