Database Develop

tatoo M7 root completed but applications say it is not rooted

I have completed my Tattoo M7 root however applications say it is not rooted.
basically if i do ADB SHELL and then SU i get the root console but can not write to /system folder via adb push since i get permisison denied which means i always have to adb shell and su.
I believe this is somehow creating problems also to applications (i am testing Titanium Backup) which require root permissions and say i am not.
Anyone can help understanding why i can su only in console or terminal emultor but cannot use apps requiring root permissions.

Dude, you have to remount EVERY TIME /system and /data if you reboot, otherwise it says permission denied because system is read only...
Get RootExplorer, there is a little button which lets you remount partitions with one tap...

pardol said:
I have completed my Tattoo M7 root however applications say it is not rooted.
basically if i do ADB SHELL and then SU i get the root console but can not write to /system folder via adb push since i get permisison denied which means i always have to adb shell and su.
I believe this is somehow creating problems also to applications (i am testing Titanium Backup) which require root permissions and say i am not.
Anyone can help understanding why i can su only in console or terminal emultor but cannot use apps requiring root permissions.
Click to expand...
Click to collapse
hi
as ur question in the related thread
see link : http://forum.xda-developers.com/showthread.php?t=637927
CLOSED

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

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

adb.exe shell>su>denied???

I have a problem..... If the title didnt say it, then ill describe my situation
When i open command windows from platform-tools folder in the SDK folder, i type in adb.exe shell. it says daemon started successfully then the line: [email protected]:/$ comes up and i type in: su. but permission denied??????????? I have superuser flashed on my phone and i have root level access on my phone though. Am i doing something wrong????

072665995 said:
I have a problem..... If the title didnt say it, then ill describe my situation
When i open command windows from platform-tools folder in the SDK folder, i type in adb.exe shell. it says daemon started successfully then the line: [email protected]:/$ comes up and i type in: su. but permission denied??????????? I have superuser flashed on my phone and i have root level access on my phone though. Am i doing something wrong????
Click to expand...
Click to collapse
If you're using CM ROM, then you also have to enable ADB root access under Developer options. The default settings is root access for apps only.

itandy said:
If you're using CM ROM, then you also have to enable ADB root access under Developer options. The default settings is root access for apps only.
Click to expand...
Click to collapse
o wow thanks man +thanks

[Q] adb with root rights

Hello
Is there a solution to have adb with root access with a stock kernel ?
Or the only way is to unlock the bootloader and flash an alternative kernel ?
Thanks.

Adb can access stock ROM with root rights on stock kernel.
Just type "adb su" and you'll get prompt to allow superuser access to your device. But you should be rooted in order to do this.
And having unlocked Bootloader is very necessary to flash custom kernel
Sent from my C5302 using XDA Free mobile app

My bad, I forgot that.
I was trying using "adb root" and it answers something like impossible.
Thanks !

No problem
Always there to help
Sent from my C5302 using XDA Free mobile app

To fully use the adb root function on your device it has to be rooted;
So when rooted just enter the following commands:
Adb shell >enter<
Su >enter<
- A SuperUser prompt will appear on your device press approve or ok or whatever
And you can now use adb with your phone and root rights
~~ Regards

mrjraider said:
To fully use the adb root function on your device it has to be rooted;
So when rooted just enter the following commands:
Adb shell >enter<
Su >enter<
- A SuperUser prompt will appear on your device press approve or ok or whatever
And you can now use adb with your phone and root rights
~~ Regards
Click to expand...
Click to collapse
No. Even running a shell as root I continue with:
- adb root : "adbd cannot run as root in production builds"
- adb push xxxx /system/xxxx : failed to copy 'xxxx' to '/system/xxxxx': Permission denied
I think the only way to do that is to have a rooted kernel.

Last one is because /system is Read-Only
~~ Regards

mrjraider said:
Last one is because /system is Read-Only
~~ Regards
Click to expand...
Click to collapse
Nope ...
it's rw, verified ...

oh it is RW protected ofcourse
~~ Regards

mrjraider said:
oh it is RW protected ofcourse
~~ Regards
Click to expand...
Click to collapse
? rw protected ?

Without proper root you cannot push files to /system.
I even had issues with adb pull /system
To be honest I have no idea.
~~ Regards