Related
I have a problem with Root Explorer! It ocurred as:
I copy a file, and I can to paste it in System/framework, but when I try paste it the Root Explorer don´t permit me to paste and says me this message:
"The paste operation failed. Would you like to send diagnostic information to the developer to assist with fixing the problem?"
WHY?
Thx 4 all! =)
Not development related Moved
Anybody can help me? =(
Sent from my GT-I5800 using Tapatalk
fersago said:
I have a problem with Root Explorer! It ocurred as:
I copy a file, and I can to paste it in System/framework, but when I try paste it the Root Explorer don´t permit me to paste and says me this message:
"The paste operation failed. Would you like to send diagnostic information to the developer to assist with fixing the problem?"
WHY?
Thx 4 all! =)
Click to expand...
Click to collapse
It's just a guess, but maybe you need to root your phone? Don't know if it's already rooted but...
Yes! Its perfectly rooted with SuperOneClick! I too use TBackup!
Sent from my GT-I5800 using Tapatalk
Did you tried the "RW" option on the rootexplorer? Or just delete first the file, and not try to overwrite them...
You can do this over adb too...
GL!
The R/W Option is Enabled! =(
UP! UP! UP!
First make sure u are rooted and then
try remounting the system by typing in terminal:
mount -o remount,rw /dev/block/stl6 /system
NOTE: When u open Root Explorer a text should appear "Root Explorer has been granted Superuser permission"... If this doesnt appear check the su app for allowing permission to ROOT EXPLORER or u will need 2 reroot ur phone...
Go to the location where you want to paste a file or perform action.
Now click on Mount RW at the top of the screen. It will change to Mount RO.
Now you can copy files.
PS: Your need a rooted phone
jaskiratsingh said:
Go to the location where you want to paste a file or perform action.
Now click on Mount RW at the top of the screen. It will change to Mount RO.
Now you can copy files.
PS: Your need a rooted phone
Click to expand...
Click to collapse
My phone is rooted, and root explorer HAS ROOT ACCESS but clicking on the "Remount as RW" button on the top of the screen does nothing in "/system"
it works on "/sdcard" and anywhere els. But not in "/system"
Any ideas?
Edit: actually in "Superuser" the root access has been allowed but when I start "Root Explorer" there will be no notification of giving the root access ("Root Explorer has been granted Superuser permission")
acutally i got a solution for remounting to rw mode
e.savisaar said:
acutally i got a solution for remounting to rw mode
Click to expand...
Click to collapse
And how did you do it?
Got the same problem on my rooted Nexus 10 running 4.2.1 JB. Rooted it with SuperSU.zip via CWM and root seems to work fine.
Sadly I cant write anything to the system folder.
I tired to use the command "mount -o remiunt,rw /dev/block/stl6 /system" mentioned earlier in this thread but even with the use of "su" and granting SuperSU rights it wont allow me to create directories there. The mount command seems to work fine as there are no error messages but mkdir throws an error:
"mkdir: can't create directory 'test': Read-only file system"
Oh and there are no toast notifications about granting root access to the shell except the first time I typed su.
Anybody else having that problem on the Nexus 10?
fersago said:
I have a problem with Root Explorer! It ocurred as:
I copy a file, and I can to paste it in System/framework, but when I try paste it the Root Explorer don´t permit me to paste and says me this message:
"The paste operation failed. Would you like to send diagnostic information to the developer to assist with fixing the problem?"
WHY?
Thx 4 all! =)
Not development related Moved
Click to expand...
Click to collapse
Long press on the file that you want to paste in , then choose permission and press yes and ok
markus4000 said:
And how did you do it?
Got the same problem on my rooted Nexus 10 running 4.2.1 JB. Rooted it with SuperSU.zip via CWM and root seems to work fine.
Sadly I cant write anything to the system folder.
I tired to use the command "mount -o remiunt,rw /dev/block/stl6 /system" mentioned earlier in this thread but even with the use of "su" and granting SuperSU rights it wont allow me to create directories there. The mount command seems to work fine as there are no error messages but mkdir throws an error:
"mkdir: can't create directory 'test': Read-only file system"
Oh and there are no toast notifications about granting root access to the shell except the first time I typed su.
Anybody else having that problem on the Nexus 10?
Click to expand...
Click to collapse
i got a solution for this issue :
just install es explorer and turn on the root explorer mode then grant the permissions then again click on the tab root explorer and then a popup window will appear where you can allow permissions for each folder differently.
click thanks button if it worked for you.
Gang, I've searched and couldn't find. I rooted the Sprint Nexus S 4G and installed CW recovery.
Would some one please be kind enough to point me on how to unroot and return to stock recovery for a return.
Thank you!
Why do you want to return it?
dmora01 said:
Why do you want to return it?
Click to expand...
Click to collapse
Exchanging for another, I appear to have a defective screen which flickers when phone is shaken.
Yeah this would be good to know, as when you unlock it there is now a big unlocked icon when booting. I could see a sprint rep throwing the phone in my face saying they can't support it.
r80ies said:
Yeah this would be good to know, as when you unlock it there is now a big unlocked icon when booting. I could see a sprint rep throwing the phone in my face saying they can't support it.
Click to expand...
Click to collapse
Use a file manager like Root Explorer or SuperManager (any file manager that can run with root access)
Delete /system/app/Superuser.apk
Delete /system/xbin/su
Delete /system/bin/su
Reboot the phone into the bootloader.
Plug the phone into USB.
Type "fastboot oem lock"
Good to go.
What about the custom CWM recovery?
oldblue910 said:
Use a file manager like Root Explorer or SuperManager (any file manager that can run with root access)
Delete /system/app/Superuser.apk
Delete /system/xbin/su
Delete /system/bin/su
Reboot the phone into the bootloader.
Plug the phone into USB.
Type "fastboot oem lock"
Good to go.
Click to expand...
Click to collapse
a2k said:
What about the custom CWM recovery?
Click to expand...
Click to collapse
Oh, my bad. Before deleting root, go to /system/etc and find whatever you renamed the install-recovery.sh file to, and rename it back to install-recovery.sh. Then follow my instructions to delete root, and once you reboot back into the ROM, it will erase ClockworkMod and install the stock recovery. That said, here is a set of updated instructions:
Use a file manager like Root Explorer or SuperManager (any file manager that can run with root access)
Go into /system/etc and find the install-recovery.sh file that you renamed originally, and rename it back to install-recovery.sh. (This will ensure that the stock recovery will be restored on first boot)
If you installed busybox, you'll have to delete it along with all the symlinks that it created.
Delete /system/app/Superuser.apk
Delete /system/xbin/su
Delete /system/bin/su
Reboot the phone into the bootloader.
Plug the phone into USB.
Type "fastboot oem lock"
Good to go.
Click to expand...
Click to collapse
oldblue910 said:
Oh, my bad. Before deleting root, go to /system/etc and find whatever you renamed the install-recovery.sh file to, and rename it back to install-recovery.sh. Then follow my instructions to delete root, and once you reboot back into the ROM, it will erase ClockworkMod and install the stock recovery. That said, here is a set of updated instructions:
Use a file manager like Root Explorer or SuperManager (any file manager that can run with root access)
Go into /system/etc and find the install-recovery.sh file that you renamed originally, and rename it back to install-recovery.sh. (This will ensure that the stock recovery will be restored on first boot)
If you installed busybox, you'll have to delete it along with all the symlinks that it created.
Delete /system/app/Superuser.apk
Delete /system/xbin/su
Delete /system/bin/su
Reboot the phone into the bootloader.
Plug the phone into USB.
Type "fastboot oem lock"
Good to go.
Click to expand...
Click to collapse
Many thanks!!!!
Titanium Backup did install busybox, how do I delete it along with all the symlinks that it created?
a2k said:
Titanium Backup did install busybox, how do I delete it along with all the symlinks that it created?
Click to expand...
Click to collapse
Did Titanium Backup install busybox into /system/xbin? If so, (I assume you have a nandroid backup just in case), I would delete absolutely everything in that folder except dexdump. If it installed busybox somewhere other than /system/xbin, then we'll cross that bridge when we get there.
oldblue910 said:
Did Titanium Backup install busybox into /system/xbin? If so, (I assume you have a nandroid backup just in case), I would delete absolutely everything in that folder except dexdump. If it installed busybox somewhere other than /system/xbin, then we'll cross that bridge when we get there.
Click to expand...
Click to collapse
I don't believe it to be installed in /system/xbin/ as the only two items showing there are:
dexdump
su
a2k said:
I don't believe it to be installed in /system/xbin/ as the only two items showing there are:
dexdump
su
Click to expand...
Click to collapse
OK check /system/bin then. Is BusyBox in there?
oldblue910 said:
OK check /system/bin then. Is BusyBox in there?
Click to expand...
Click to collapse
OldBlue, I really appreciate your assistance!
I feel really stupid, there are numerous files inside /system/bin, heck I stopped counting at 40!! I do not see a "BusyBox" file there, what should I look for?
a2k said:
OldBlue, I really appreciate your assistance!
I feel really stupid, there are numerous files inside /system/bin, heck I stopped counting at 40!! I do not see a "BusyBox" file there, what should I look for?
Click to expand...
Click to collapse
Yeah there will be a bunch. Do you have a terminal emulator installed? If so, go into the terminal emulator:
Type "su" (without quotes)
Type "busybox which busybox" (without quotes)
Tell me what it says.
oldblue910 said:
Yeah there will be a bunch. Do you have a terminal emulator installed? If so, go into the terminal emulator:
Type "su" (without quotes)
Type "busybox which busybox" (without quotes)
Tell me what it says.
Click to expand...
Click to collapse
I installed Terminal Emulator:
Typed: su
Typed: busybox which busybox
Response: busybox: not found
Although TB says:
Root Access: OK (BusyBox 1.16.0 from app)
a2k said:
I installed Terminal Emulator:
Typed: su
Typed: busybox which busybox
Response: busybox: not found
Although TB says:
Root Access: OK (BusyBox 1.16.0 from app)
Click to expand...
Click to collapse
Oh no wonder! You're all set then. BusyBox is located within Titanium Backup's data folder. You don't need to worry. BusyBox will go away when you uninstall Titanium. So just follow my updated instructions and you're good. Let me know if you have any problems. Make sure you have a nandroid backup of your ROM before you delete root, just in case! You can never be too careful!
Use a file manager like Root Explorer or SuperManager (any file manager that can run with root access)
Go into /system/etc and find the install-recovery.sh file that you renamed originally, and rename it back to install-recovery.sh. (This will ensure that the stock recovery will be restored on first boot)
If you installed busybox, you'll have to delete it along with all the symlinks that it created.
Delete /system/app/Superuser.apk
Delete /system/xbin/su
Delete /system/bin/su
Reboot the phone into the bootloader.
Plug the phone into USB.
Type "fastboot oem lock"
Good to go.
Click to expand...
Click to collapse
Quote: Go into /system/etc and find the install-recovery.sh file that you renamed originally, and rename it back to install-recovery.sh. (This will ensure that the stock recovery will be restored on first boot)
what if there is no install-recovery.sh file!!!!!! under system/etc?
i didnt delete it!!!!!!! i was woundering way everybody was talking about renameing it? i dont have that file..
spdwiz18 said:
Quote: Go into /system/etc and find the install-recovery.sh file that you renamed originally, and rename it back to install-recovery.sh. (This will ensure that the stock recovery will be restored on first boot)
what if there is no install-recovery.sh file!!!!!! under system/etc?
i didnt delete it!!!!!!! i was woundering way everybody was talking about renameing it? i dont have that file..
Click to expand...
Click to collapse
Hmmm....try just /etc. Is it in there? Every stock Android build since 2.3.1/GRH78 has had that file in there. It checks the MD5 hash of the current recovery and if it doesn't match up, it flashes the stock one over it. That's really strange.
oldblue910 said:
Hmmm....try just /etc. Is it in there? Every stock Android build since 2.3.1/GRH78 has had that file in there. It checks the MD5 hash of the current recovery and if it doesn't match up, it flashes the stock one over it. That's really strange.
Click to expand...
Click to collapse
Nope .... no such file. I even did a search for it with root explorer and it does not come up. If worse come to worse ill pull it from someone's Tom just so I have it on my phone. But I know I did not delete it.
Sent from my Nexus S 4G using XDA Premium App
That is very strange indeed. I wonder if Google didn't install it on the Nexus S 4G. Can any other NS4G owners verify if /etc/install-recovery.sh exists on your phone?
Alright so here's my problem: After rooting my phone, I started to play around with a couple of camera apps from different ROMs such as MIUI. Me being an idiot though, deleted the stock Blur camera Apk. Using a system dump of the Atrix, 2 I tried to reinstall it, by placing it in system/app. For some reason. It wouldn't install (show up on my app directory). Anybody have any idea as to why this is happening? Any help would be greatly appreciated, because I really need a camera app.that's supports 1080p video. Thanks in advance!!!
farshad525hou said:
Alright so here's my problem: After rooting my phone, I started to play around with a couple of camera apps from different ROMs such as MIUI. Me being an idiot though, deleted the stock Blur camera Apk. Using a system dump of the Atrix, 2 I tried to reinstall it, by placing it in system/app. For some reason. It wouldn't install (show up on my app directory). Anybody have any idea as to why this is happening? Any help would be greatly appreciated, because I really need a camera app.that's supports 1080p video. Thanks in advance!!!
Click to expand...
Click to collapse
Push the sick app via adb. I read somewhere that with apps such as root explorer it doesn't work for some reason. Hope this helps.
Sent from my MB865 using Tapatalk
Yes, always use adb to push system apps. Root Explorer will not work.
Sent from my mAtrix2!!
For some reason i get permission denied whenever i try to push through adb. How do i get around this?
farshad525hou said:
For some reason i get permission denied whenever i try to push through adb. How do i get around this?
Click to expand...
Click to collapse
To copy anything to /system/app, you need root access.
This will be a 2 step process.
1) push the file from your computer to your phone in a directory that the shell has access to, i.e. /data/local for instance.
2) adb shell into the phone and su, remount /system as rw, then cp the file from /data/local/ to /system/bin
That should elimiate the issue with permission denied, with adb push.
jimbridgman said:
To copy anything to /system/app, you need root access, have you rooted the phone?
If you have rooted the phone, this will be a 2 step process.
1) push the file from your computer to your phone in a directory that the shell has access to, i.e. /data/local for instance.
2) adb shell into the phone and su, remount /system as rw, then cp the file from /data/local/ to /system/bin
That should elimiate the issue with permission denied, with adb push.
Click to expand...
Click to collapse
Yes my phone is rooted. How do I remount /system as rw? Then how do i cp the file? Thanks for your help!
I figured out how to push the file with adb, but the app still does not show up. Any other ideas?
farshad525hou said:
Yes my phone is rooted. How do I remount /system as rw? Then how do i cp the file? Thanks for your help!
Click to expand...
Click to collapse
Ok, run EVERYTHING between Code:, and End code from the command line. Just make sure you are in the directory you saved your backup camera.apk to, from your windows command prompt, before you run the commands below.
Code:
adb push BlurCamera.apk /data/local
adb shell
su
mount -o remount, rw /system
cd /data/local
cp BlurCamera.apk /system/app
chown root /system/app/BlurCamera.apk
chgrp root /system/app/BlurCamera.apk
chmod 644 /system/app/BlurCamera.apk
mount -o remount, ro /system
exit
exit
End code
That should hopefully fix it.
jimbridgman said:
Ok, run EVERYTHING between Code:, and End code from the command line. Just make sure you are in the directory you saved your backup camera.apk to, from your windows command prompt, before you run the commands below.
Code:
adb push BlurCamera.apk /data/local
adb shell
su
mount -o remount, rw /system
cd /data/local
cp BlurCamera.apk /system/app
chown root /system/app/BlurCamera.apk
chgrp root /system/app/BlurCamera.apk
chmod 644 /system/app/BlurCamera.apk
mount -o remount, ro /system
exit
exit
End code
That should hopefully fix it.
Click to expand...
Click to collapse
Sadly this didn't work either. I don't know what I'm doing wrong. Btw, thanks for your help so far!
Quick question....is the blurcamera.odex file still in the system/app. If you have deleted it also you will have to replace it as well.
JRW 28 said:
Quick question....is the blurcamera.odex file still in the system/app. If you have deleted it also you will have to replace it as well.
Click to expand...
Click to collapse
I could only find a deodexed system dump
Here ya go, zip has both camera.apk and odex. Try using file explorer again and make sure it is r/w . Hope it helps
http://db.tt/v0FQKpKr
JRW 28 said:
Here ya go, zip has both camera.apk and odex. Try using file explorer again and make sure it is r/w . Hope it helps
http://db.tt/v0FQKpKr
Click to expand...
Click to collapse
Thanks for the files! But once again sadly the file doesn't appear under my app drawer. I tried using adb and root explorer, with no luck. Is there anything I'm missing? Btw, JRW are those files from the atrix 2?
There both straight off of my phone...that's weird cause I have removed both of them trying out various cameras and never had a problem reinstalling them?
Are you rebooting afterwards?
JRW 28 said:
There both straight off of my phone...that's weird cause I have removed both of them trying out various cameras and never had a problem reinstalling them?
Are you rebooting afterwards?
Click to expand...
Click to collapse
Yeah I am. Can you walk me through what you do when you re install the apps? I am really confused. Is there anything that might be interfering?
Go into file explorer and make sure your system folder is r/w along with both the blurcamera.apk and blurcamera.odex.... then drop both of them into system/app and reboot. Wouldn't think anything else would be interfering?
JRW 28 said:
Go into file explorer and make sure your system folder is r/w along with both the blurcamera.apk and blurcamera.odex.... then drop both of them into system/app and reboot. Wouldn't think anything else would be interfering?
Click to expand...
Click to collapse
How do I make sure that BlurCamera.apk and BlurCamera.odex are both r/w?
Im not sure if it really matters on them but long pressing on either of them in file explorer should bring up the permissions and you can change from there. Do the same on your system folder just to double check that the permissions are correct
JRW 28 said:
Im not sure if it really matters on them but long pressing on either of them in file explorer should bring up the permissions and you can change from there. Do the same on your system folder just to double check that the permissions are correct
Click to expand...
Click to collapse
Yeah still no luck... no idea whats wrong
Try pushing them with ADB .....usually that will take care of it
Please read the problem completely before answering and saying something.
I have S3 Feel os ROM in my HTC Pico.
When i tried to copy any files inside /system/ its saying : Permission denied read only file system.
I tried to use chmod 777 to system through terminal emulator its also given same warning.
Then I tried remounting with the command: mount -o rw,remount /system (using terminal emulator) didn't do the trick for me.
Can you guys tell what should i do to get the write permission. (Its actually showing read and write permission when I saw file/folder properties with a file explorer inside the system directory, but actually its not allowing to write).
It should be fine if you try with some file manager that can get root permissions. (my choice is 'es')
But if you are using the new oc kernel, there things might be different.
What is terminal emulator giving you back?
You also can try by flashing superuser, I have not tryed exactly this rom, but there may be something wrong with su
shortyoko said:
It should be fine if you try with some file manager that can get root permissions. (my choice is 'es')
Click to expand...
Click to collapse
Yes I am using ES File explorer only. Still it says, error permission denied to copy a new file/create a new file/overwrite a file.
shortyoko said:
But if you are using the new oc kernel, there things might be different.
Click to expand...
Click to collapse
I have flashed a oc kernal almost a month back. In between I have changed lot of roms and got back to S3 Feel os rom. I think that won't effect now right?
shortyoko said:
What is terminal emulator giving you back?
Click to expand...
Click to collapse
If I give chmod 777 /system, it's giving permission denied (I have granted super user permission to terminal emulator and i am in su mode)
When I tried mount -o rw,remount /system, it didn't output any thing. Then again I tried to copy a file into system dir, still its the same result.
shortyoko said:
You also can try by flashing superuser, I have not tryed exactly this rom, but there may be something wrong with su
Click to expand...
Click to collapse
Its the last choice I have now, will try.
Try changing mounting
smartksr said:
Please read the problem completely before answering and saying something.
I have S3 Feel os ROM in my HTC Pico.
When i tried to copy any files inside /system/ its saying : Permission denied read only file system.
I tried to use chmod 777 to system through terminal emulator its also given same warning.
Then I tried remounting with the command: mount -o rw,remount /system (using terminal emulator) didn't do the trick for me.
Can you guys tell what should i do to get the write permission. (Its actually showing read and write permission when I saw file/folder properties with a file explorer inside the system directory, but actually its not allowing to write).
Click to expand...
Click to collapse
Had same problem with same ROM. So i go to ES then root explorer then mount R/W then change both path and system to RW and restart.. that solved my problem. try it.
shree15 said:
Had same problem with same ROM. So i go to ES then root explorer then mount R/W then change both path and system to RW and restart.. that solved my problem. try it.
Click to expand...
Click to collapse
Thanks bro, it has solved me the problem.
I'm trying to copy a boot animation in the system/media folder. My device is rooted, and I use Root Browser. But when I paste the file, the operation fails.
What should I do?
Sent from my M-PPxG501
Andre1299 said:
I'm trying to copy a boot animation in the system/media folder. My device is rooted, and I use Root Explorer. But when I paste the file, the operation fails.
What should I do?
Sent from my M-PPxG501
Click to expand...
Click to collapse
Grab the app Terminal Emulator and run this:
Code:
su
mount -o rw,remount /dev/block/mmcblk0p5 /system
exit
exit
Should get you going.
ИΘΘK¡€ said:
Grab the app Terminal Emulator and run this:
Code:
su
mount -o rw,remount /dev/block/mmcblk0p5 /system
exit
exit
Should get you going.
Click to expand...
Click to collapse
Thank you for the answer. I types these lines in the terminal, but nothing changed..
Sent from my M-PPxG501 using XDA Free mobile app
ES File Explorer
Andre1299 said:
Thank you for the answer. I types these lines in the terminal, but nothing changed..
Sent from my M-PPxG501 using XDA Free mobile app
Click to expand...
Click to collapse
ES File Explorer has a huge amount of features.
This includes RO/RW GUI.
Download ES File Explorer (free, no IAP) from Google Play.
Open it and go to the menu>Tools on the left and enable "Root Explorer"
Once it was enabled open Root Explorer options by tapping on it.
Go to "Mount RO/RW" and check RW on every directory.
Now you should be able to edit.
If you can't you may not have proper root.
Hit that Thanks button if I helped.
janekmuric said:
ES File Explorer has a huge amount of features.
This includes RO/RW GUI.
Download ES File Explorer (free, no IAP) from Google Play.
Open it and go to the menu>Tools on the left and enable "Root Explorer"
Once it was enabled open Root Explorer options by tapping on it.
Go to "Mount RO/RW" and check RW on every directory.
Now you should be able to edit.
If you can't you may not have proper root.
Hit that Thanks button if I helped.
Click to expand...
Click to collapse
Thank you, it worked