Database Info

Root and SU issues

Hello Everyone,
I have recently rooted my phone again but am having an issue. I cannot do an adb remount becase it says that permission is denied. This is going to be due to the fact that when I adb shell it starts with a $ instead of #. If I do the following it will work so that I can push files and system files:
PHP:
adb shell //enter adb shell
su //activate superuser
mount -o rw,remount /dev/block/mmcblock1p21 /system //mounts the drive and allows read/write
exit //exit superuser
exit //exit shell
adb push xxxxxxxxxx.apk /system/xxxxxxxxx/ //push whatever file is needed
My question is why can I not just adb push or remount? Does anyone know how to make it so that I auto superuser when doing adb shell so i get # instead of $?

you should be able to just type adb remount and have the /system turned either RW or RO depending on what its changing from...

Have you granted superuser permissions to adb? It should pop up on the phone.

yes superuser works on the phone. I can access superuser and it will work but I have to do it manually.

jj702561 said:
you should be able to just type adb remount and have the /system turned either RW or RO depending on what its changing from...
Click to expand...
Click to collapse
I understand that it should allow it but its not. That is exactly what this post is for. If i do the commands list in the first window this is manually change it to RW and then after I finish I set it back to RO.

theecho said:
yes superuser works on the phone. I can access superuser and it will work but I have to do it manually.
Click to expand...
Click to collapse
Right, but a superuser request will pop up when you use adb remount. Try it again and check the phone for it.

its not getting to that point. It is giving me an error on the command prompt. I have checked for it and the SU wasnt there

how to unroot my nexus s pls help

hello,
i need help to remove superuser and lock my nexus s
+after doing that should i get official updates?
i did see this topic
http://forum.xda-developers.com/showthread.php?t=879041
and i try this solution
ryude said:
You need to use adb to go in the file system and delete all trace of superuser and busybox. That is the only things rooting does, places those files on your phone and changes file permissions. File permissions, they won't look for, but I've had best buy scroll through the app drawer on multiple occasions looking for superuser/rom manager.
I have attached a zip containing all the files needed for adb. Since they no longer package adb with the sdk. Just open command prompt and cd to the directory containing adb. Make sure your phone has Usb Debugging enabled, then connect your phone.
You might need to download usb drivers in order for windows to recognize the device, but probably not. Once your phone is connected, do the following.
Code:
adb devices
adb shell
su
rm /system/app/Superuser.apk
rm /system/bin/su
rm /system/bin/busybox
rm /system/bin/rootshell
reboot
Click to expand...
Click to collapse
but when i write rm /system/app/Superuser.apk it say
Read-only file system
so what should i do i only get my XS unlock then install superuser using
install-superboot-windows.bat
and i never do recovery!!!!!!
so any help
i need to get my nexus like new and i should then gt updates

You can have superuser and get updates. The update will remove root though. You could always wait for the cm nightly to include 2.3.3
Sent from my Nexus S using XDA App

You have to mount the /system partition as read/write.
Easiest way is use Root Explorer.
You can also try the following from adb or terminal on the phone:
Code:
su
mount -o rw,remount /dev/block/mtdblock3 /system

thanks for your reply
i used Root Explorer to mount the /system partition as read/write.
and then
i did write this codes
adb devices
adb shell
su
rm /system/app/Superuser.apk
and every thing was ok
but i have an error on those lines
rm /system/bin/su
rm /system/bin/busybox
rm /system/bin/rootshell
and every time i get file not found
so what i should do???

hello, tominater12 and thank you for reply
cold you tell me how i can remove superuser and root using the update??????
i want to get my nexus s like new no root no superuser
so any one can help?

hi guys,
this is my first post in the forums, but after reading and watching many videos on how to remove it i have found a solution...my nexus s is now unrooted with no superuser...
make sure u have android sdk installed, and have usb debugging on.
restart phone into recovery
open cmd and type -
cd c:/AndroidSDK/tools/
adb shell mount /system
adb shell rm /system/app/Superuser.apk
ALL CREDITS GO TO 'TheUltraLinx' ON YOUTUBE,
who has fixed my phone to factory settings

flash oem rom and fastboot oem unlock?

[Q] Problems with ADB remount / pushing app

I've unlocked my phone via HTCDev, which to my understanding should give enough permissions and whatnot for adb to work on system files too.
I'm trying to push application to replace system application, I know the application works, I got both signed & unsigned versions of it but same thing with either one of them.
adb remount says "remount failed: operation not permitted" and adb push [file] /system/apps says "failed to copy '[file]' to '/system/apps/': read-only file system
--
What am I doing wrong, or do I really have to root the phone just to get one damn application replaced with modified one?

Bump

Have you rooted?

frazzeld said:
Have you rooted?
Click to expand...
Click to collapse
This^
You need to have SU# access, which be definition needs root permissions. If you haven't already, use the all in one tool kit to flash clockwork and root that beech. Then when in ADB you enter SU and you will get a prompt like this #, indicating you have root privileges.

Update, I have rooted, stock rom still though
If I use adb shell, I get $, but writing "su" in shell gives me #
still, I've tried both the adb remount and in shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
the latter seems to work, but however still when I try to push something to /system/app it still says permission denied
edit:
not quite sure what I did, but i finally got SUCCESS from installing from shell

how did you install through the shell

Help on pushing files to device (ADB)

Hello guys, experiencing another problem now :silly:
Have search all around, couldn't find any valid answers so I decided to ask myself.
So I was just making a rom, which I have already installed. It's based on Cataclysm (personal use only - Till I ask for perm).
I have installed the rom, then I decided to theme some system files. And so I did. I theme the "Settings.apk" for now, and decided to push it to my device instead of installing the whole rom over again. Now mind you when I made roms and modified system apps, pushing these files to the device was straight forward. However on this Hammerhead, I've been running into some issues.
When pushing the file to my device like this
Code:
adb push Settings.apk system/priv-app
.
I get an error that says -
Code:
failed to copy "Settings.apk" to "system/priv-app/Settings.apk" : Read only file system.
So I then decided to try the following -
Code:
[x] adb root - Permission Denied
[x] adb remount - Permission Denied
So then I decided to use some shell commands to set the system as rw, I did the following.
Code:
[x] adb shell
[x] $ su - gave it permission
[x] $ mount -o rw,remount /system - It mounts it.
I then restarted cmd with root permission.
Code:
adb root"
- it restarted however, this time it stated.
Code:
Device not found.
I probably did the wrong thing above, so how exactly can I push files to /system?
SOLVED
Thanks to everyone that answered my question in detail.

The easiest way I know to push files to /system through adb is using a custom recovery . Try with it.

Why not use usb or AirDroid to transfer files?

gee2012 said:
Why not use usb or AirDroid to transfer files?
Click to expand...
Click to collapse
Is it possible to push files to /sustem/priv-app with it?
varuntis1993 said:
The easiest way I know to push files to /system is using a custom recovery . Try with it.
Click to expand...
Click to collapse
How would I do so? I've ever only used recovery to flash. And that was it, thanks if you can guide me through it?
Sent from this toast making Nexus 5, you wish your Nexus could make toast don't you? (;

krishneelg3 said:
Is it possible to push files to /sustem/priv-app with it?
How would I do so? I've ever only used recovery to flash. And that was it, thanks if you can guide me through it?
Sent from this toast making Nexus 5, you wish your Nexus could make toast don't you? (;
Click to expand...
Click to collapse
Boot into recovery and connect the usb cable. Open a cmd prompt.
Code:
adb shell
mount /system
exit
adb push c:\users\krishneelg3\desktopmyfile /system/priv-app
You can also use the "mount system" option in recovery and skip the first 2 commands above.

krishneelg3 said:
How would I do so? I've ever only used recovery to flash. And that was it, thanks if you can guide me through it?
Sent from this toast making Nexus 5, you wish your Nexus could make toast don't you? (;
Click to expand...
Click to collapse
Open recovery, mount system partition and connect it to pc and then normal procedure.
It will be running as adbd to no need to type adb root. Hope this helps

rootSU said:
Boot into recovery and connect the usb cable. Open a cmd prompt.
Code:
adb shell
mount /system
exit
adb push c:\users\krishneelg3\desktopmyfile /system/priv-app
You can also use the "mount system" option in recovery and skip the first 2 commands above.
Click to expand...
Click to collapse
Thank you so much! Greatly appreciated.
Sent from this toast making Nexus 5, you wish your Nexus could make toast don't you? (;

You can still do it through Android, but it's more difficult because adb root doesn't always work (requires kernel) and you have to mount r/w which is just a pain. I always adb push in recovery.
However, here is an example of a successful attempt to adb push on my nexus 5.
Code:
C:\Users\rootsu\Desktop\tools>adb root
adbd is already running as root
C:\Users\rootsu\Desktop\tools>adb shell
[email protected]:/ # mount -o remount,rw /system
mount -o remount,rw /system
[email protected]:/ # exit
exit
C:\Users\rootsu\Desktop\tools>adb push [B][COLOR="Red"]test.txt[/COLOR][/B] /system/
C:\Users\rootsu\Desktop\tools>adb shell
[email protected]:/ # cd system
cd system
[email protected]:/system # ls
ls
addon.d
app
bin
build.prop
core
etc
fonts
framework
lib
lost+found
media
priv-app
[B][COLOR="red"]test.txt[/COLOR][/B]
tts
usr
vendor
xbin
[email protected]:/system #

rootSU said:
You can still do it through Android, but it's more difficult because adb root doesn't always work (requires kernel) and you have to mount r/w which is just a pain. I always adb push in recovery.
However, here is an example of a successful attempt to adb push on my nexus 5.
Code:
C:\Users\rootsu\Desktop\tools>adb root
adbd is already running as root
C:\Users\rootsu\Desktop\tools>adb shell
[email protected]:/ # mount -o remount,rw /system
mount -o remount,rw /system
[email protected]:/ # exit
exit
C:\Users\rootsu\Desktop\tools>adb push [B][COLOR="Red"]test.txt[/COLOR][/B] /system/
C:\Users\rootsu\Desktop\tools>adb shell
[email protected]:/ # cd system
cd system
[email protected]:/system # ls
ls
addon.d
app
bin
build.prop
core
etc
fonts
framework
lib
lost+found
media
priv-app
[B][COLOR="red"]test.txt[/COLOR][/B]
tts
usr
vendor
xbin
[email protected]:/system #
Click to expand...
Click to collapse
Thank you I will keep my eye on this and see if the process is similar. Thanks for the info.
Sent from this toast making Nexus 5, you wish your Nexus could make toast don't you? (;

Root user cannot 'remount'

Hi,
after a lots of hassle I finally accessed the root access into my Sony z2 tablet. But the Root Checker Basic app says
Sorry! Root access is not properly installed on this device.
Click to expand...
Click to collapse
I can still run
Code:
adb root
without error. And the
Code:
adb shell whoami
returns "root".
Still when I run
Code:
adb remount
it says
remount of /system failed; couldn't make block device /dev/block/platform/msm_sdcc.1/by-name/system writable: Permission denied
remount failed
Click to expand...
Click to collapse
I need to remount the device because I want to move an APK to the "/system/priv-apps" folder.

Did you try remounting directly from an adb shell ?
mount -o remount,rw /system

ddscentral said:
Did you try remounting directly from an adb shell ?
mount -o remount,rw /system
Click to expand...
Click to collapse
Yes I tried. it says
mount: Operation not permitted
Click to expand...
Click to collapse

Toriq100 said:
Yes I tried. it says
Click to expand...
Click to collapse
Are you trying to mount as root ? (your shell prompt should start with # and not $). If not, use "su" command to get root and then try mounting again.
If remount fails even from a root shell, check your SELinux status with "getenforce" command.

ddscentral said:
Are you trying to mount as root ? (your shell prompt should start with # and not $). If not, use "su" command to get root and then try mounting again.
If remount fails even from a root shell, check your SELinux status with "getenforce" command.
Click to expand...
Click to collapse
Yes, I am trying to mount as root so that I can move an APK to "system/priv-apps". My shell prompt does start with #. I cannot use "su", it says "[-] Daemon is stop".
I checked SELinux status. It says "Enforcing", then I tried "adb shell setenforce 0" it says "setenforce: Couldn't set enforcing status to '0': Permission denied". :'(

Likely SELinux is preventing remount.
Are you still using the original software or a custom ROM ?

ddscentral said:
Likely SELinux is preventing remount.
Are you still using the original software or a custom ROM ?
Click to expand...
Click to collapse
Original software (I gained the root access using KingRoot, tried everything else, didn't work)

I would either flash SuperSU with a custom recovery (assuming you can unlock the bootloader) or flash a third party ROM.

ddscentral said:
I would either flash SuperSU with a custom recovery (assuming you can unlock the bootloader) or flash a third party ROM.
Click to expand...
Click to collapse
I tried recovering with custom ROM but failed. Here I asked a question for reference, but didn't find working solution.