prejudice I have noticed that since version 1.5 I do not have all the permissions of root, after having installed the system with :
./adb shell
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
exit
exit
./adb push framework-res.apk /system/framework/framework-res.apk
I have been informed that I do not have permission, I also tried to install the original firmware, making the root of this (and everything is fine) and install Paranoid Android 1.6a (I have no permission). please can you help me? Thanks to all
massinegro204 said:
prejudice I have noticed that since version 1.5 I do not have all the permissions of root, after having installed the system with :
./adb shell
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
exit
exit
./adb push framework-res.apk /system/framework/framework-res.apk
I have been informed that I do not have permission, I also tried to install the original firmware, making the root of this (and everything is fine) and install Paranoid Android 1.6a (I have no permission). please can you help me? Thanks to all
Click to expand...
Click to collapse
have u check your device with ROOT CHECKER https://play.google.com/store/apps/...GwsMSwxLDEsImNvbS5qb2V5a3JpbS5yb290Y2hlY2siXQ.. before u install Paranoid Android Rom??
Hit thanks if i helped you friend
Try "adb remount" before trying to push file into /system
If the command come back with error, you will need adbd insecure. Normally custom kernel would have include it, but for stock kernel it was not included.
There is an app made by chainfire to enable this feature, you can find it here. Enable USB debugging on your phone, patch it.
Related
Hi,
I am trying to alter the boot xml file to get my boot sound back. I am on Modaco 2.5.1 now.
Pulled the boot sound xml file, edited. But when I try push back to phone I get the 'android adb push read-only file system' message.
How do I get round this?
Thanks
Phil
Phil_UK said:
Hi,
I am trying to alter the boot xml file to get my boot sound back. I am on Modaco 2.5.1 now.
Pulled the boot sound xml file, edited. But when I try push back to phone I get the 'android adb push read-only file system' message.
How do I get round this?
Thanks
Phil
Click to expand...
Click to collapse
Do a adb remount before doing the push should solve it.
Thanks
That solved it!
Phil
i'm having the same error when i want to delete stock apps. i'm rooted already, but not sure how to get myself to read write rights. any idea?
Get around read-only
I am having the same problem. Have you had any luck??
woowoowooty said:
I am having the same problem. Have you had any luck??
Click to expand...
Click to collapse
adb remount
"remount failed: Operation not permitted"
you cant do it while in recovery,you have to be booted up.
EXAMPLE to remove Sim Toolkit
adb remount
remount successful
adb shell rm /system/app/Stk.apk
Done...
If you still have problems type adb shell, type su,press allow on your phone screen then try again.
If it shows a $ sign when u type adb shell then u got no root son
................ delete post. ....
sorry but i am quite new to android and rootin... can u please tell me what is recovery and what is boot up.. cause i am facing teh same issue and when i try adb remount from my command prompt, i get permission denied error . Can this also be done from terminal emulator in android.. my device is rooted and i have superuser permission..
thanks in advance,
Rejo
rejo_nazi said:
sorry but i am quite new to android and rootin... can u please tell me what is recovery and what is boot up.. cause i am facing teh same issue and when i try adb remount from my command prompt, i get permission denied error . Can this also be done from terminal emulator in android.. my device is rooted and i have superuser permission..
thanks in advance,
Rejo
Click to expand...
Click to collapse
You can try it in terminal emulator after su.
Code:
$ su
# mount -o rw,remount /system
<do what you want>
# mount -o ro,remount /system
thanks for the information!
Hi.
Samsung Galaxy Ace - FroYo 2.2.1 - Rooted with superuser.
Pulled framework.jar from /system/framework/framework.jar
edited it and now pushing back.
I get
failed to copy 'framework.jar' to '/system/framework/framework.jar': Read-only file system.
I know it's a read-only file system, but I need to push that (and other files) back there.
How to allow that process?
My other option is to "FLASH" a .zip file which contains these files, and I think that puts them in their desired location, but:
What is Flashing and how is it done on my device? I've been googling for a couple hours now with no luck. Adobe Flash is taking all the search results, and some found forum entries aren't helping.
Many thanks, I hope for a quick reply.
Hi, same problem trying to push some libs and framework.jar back to where they originally pulled from. I need to do that for Arabization on Samsung Galaxy Ace running Froyo 2.2.1 with Root.
Error returs "failed: read-only file system"
I've beek googling and searching forums for a couple days now with no luck. Tried many things, commands and chmod which all failed.
The other option, which is to use update.zip on stock recovery to send the files home has failed. Got the following:
Finding update package...
Opening update package...
Installing upate...
E:Error in /sdcard/update.zip (Status 0)
Installation aborted.
I couldn't install ClockworkMod to try it there because Rom Manager does not list my phone (Samsung Galaxy Ace) in the options it gives me when I ask it to Flash ClockworkMod Recovery into my phone. I don't know which phone to choose form the list:
- Huawei Pulse Mini
- Dell Streak
- Huawei Pulse
- Commtiva Z71 (Boston, blaze, and more)
- Geeksphone ONE
- Spice MI700, Commtiva Link N700 and more)
- Huawei Ascend
Halp.
Oh just noticed I have both last posts. How progress works.
By the way,
#mount -o rw,remount /system
does not help. Trying to copy files using 'cp' commant in shell now simply brings 'file exists'. Is there an 'overwrite' attribute to add that'll fix it?
adb remount worked for me thanks..
pigfoot said:
You can try it in terminal emulator after su.
Code:
$ su
# mount -o rw,remount /system
<do what you want>
# mount -o ro,remount /system
Click to expand...
Click to collapse
champagne post. tnx!!!
pigfoot said:
You can try it in terminal emulator after su.
Code:
$ su
# mount -o rw,remount /system
<do what you want>
# mount -o ro,remount /system
Click to expand...
Click to collapse
Worked for me, thank you!
hey guys,
ive just started to learn how to modify apks and use adb.
my problem is that after i pull the file, i modify the icon i want to change, re-sign it and push it back to the phone. after i reinstall, the icons have not changed :S i re-pulled it, and the icons in the drawable_hdpi file are the one i wanted.
also, completely unrelated to that.... in adb when i try to run adb remount, it says permission denied, but im rooted and i even tried running the shell root beforehand aswell.
i ran a search and followed the various instructions from the different threads and forums but im just stuck at that point
thanks guys
kylec said:
also, completely unrelated to that.... in adb when i try to run adb remount, it says permission denied, but im rooted and i even tried running the shell root beforehand aswell.
Click to expand...
Click to collapse
If you're getting permission denied how have you pushed it back?
XperiaX10iUser said:
If you're getting permission denied how have you pushed it back?
Click to expand...
Click to collapse
i push it to the sdcard lol because it wont let me push to the system/app folder nor the data/app folder. i check my screen and a pop up appears saying that superuser granted access, so i have that.
kylec said:
i push it to the sdcard lol because it wont let me push to the system/app folder nor the data/app folder.
Click to expand...
Click to collapse
Then it's no wonder your icons haven't changed if you haven't installed it to the phone.
Try, but keep your phones screen on whilst you try it...
adb shell (enter)
su (enter)
...allow super user access on phone...
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
XperiaX10iUser said:
Then it's no wonder your icons haven't changed if you haven't installed it to the phone.
Try, but keep your phones screen on whilst you try it...
adb shell (enter)
su (enter)
...allow super user access on phone...
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
Click to expand...
Click to collapse
ok i just tried that. when i typed su, it echoed and on my phone it said "unknown has been grandted superuser permissions" so i didnt need to click allow or anything.
then i typed the mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system and got mount: operation not permitted
any ideas?
kylec said:
any ideas?
Click to expand...
Click to collapse
Try...
cd C:\android-sdk-windows\tools
adb shell
su
chmod 4755 /system/bin/sh
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
...and report back.
XperiaX10iUser said:
Try...
cd C:\android-sdk-windows\tools
adb shell
su
chmod 4755 /system/bin/sh
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
...and report back.
Click to expand...
Click to collapse
yup that worked, i got an echo without errors
EDIT: ok after that i then tried to push the apk to the system/app and also the data/app folders, but i got a different error this time.
it said failed to copy .apk permission denied
kylec said:
it said failed to copy .apk permission denied
Click to expand...
Click to collapse
Try, in a terminal on the phone...
su
chmod 4755 /system/bin/sh
I always struggle trying to get permissions after I've first rooted but can never remember the exact sequence, but do know it's a combination of what I've suggested.
XperiaX10iUser said:
Try, in a terminal on the phone...
su
chmod 4755 /system/bin/sh
I always struggle trying to get permissions after I've first rooted but can never remember the exact sequence, but do know it's a combination of what I've suggested.
Click to expand...
Click to collapse
ill give it a try after uni lol. thanks for all the help mate, its awesome having a place to get advice and help
EDIT: finally got it working... i pushed the file to sdcard then used the terminal emulator and used:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
cd sdcard
cat x.apk /data/app/x.apk
and that worked perfectly lol
I thought I'd bricked my NT but it would appear that it is actually alive because it turns up with adb and I can get shell and then issue command su, but what I can't do is replace the old build.prop because file system is not writable. How do I remount it to be writeable from a shell please?
Thanks!
CelticWebSolutions said:
I thought I'd bricked my NT but it would appear that it is actually alive because it turns up with adb and I can get shell and then issue command su, but what I can't do is replace the old build.prop because file system is not writable. How do I remount it to be writeable from a shell please?
Thanks!
Click to expand...
Click to collapse
mount -o rw,remount -t ext4 /dev/block/mmcblk0p8 /system
Type mount to verify rw, make your changes
mount -o ro,remount -t ext4 /dev/block/mmcblk0p8 /system
Type mount to verify ro
Thank you!
hwong96 said:
mount -o rw,remount -t ext4 /dev/block/mmcblk0p8 /system
Type mount to verify rw, make your changes .....
Click to expand...
Click to collapse
I don't have this tablet but a phone with similar problem.
this does not work for me, although I have ROOTED phone MTK6572, android 4.2.2 ;
"/ root" gets RW, but "/system" stays RO.
I get this message:
error
"the item "system" is read only"
I have tried many apps in phone (remount system RW, FX file expl. ....), and mtkdroid-tools and ADB shell in PC.
I have tried many similar version of that command, too, inc. busybox remount. non of those work.
any ideas, what to try next?
what file or thing or item and where I need to change to get this remounting system to RW done?
it is ext4, and remountable.
I have SuperSU in phone but can't update its binaries: /system stays RO, what ever I try...
I can't change audios, anything in /system.
very annoying...
Jack_Rover said:
I don't have this tablet but a phone with similar problem.
this does not work for me, although I have ROOTED phone MTK6572, android 4.2.2 ;
"/ root" gets RW, but "/system" stays RO.
I get this message:
error
"the item "system" is read only"
I have tried many apps in phone (remount system RW, FX file expl. ....), and mtkdroid-tools and ADB shell in PC.
I have tried many similar version of that command, too, inc. busybox remount. non of those work.
any ideas, what to try next?
what file or thing or item and where I need to change to get this remounting system to RW done?
it is ext4, and remountable.
I have SuperSU in phone but can't update its binaries: /system stays RO, what ever I try...
I can't change audios, anything in /system.
very annoying...
Click to expand...
Click to collapse
I understand your frustration, however, you should try to post your question to the MTK6572 or Samsung S4 thread. Anyway, since you have asked I'll answer. The mount point for /system is different on each phone model. There is no one standard /system mount point. On the Nook Tablet and Nook Color it is mmcblk0p8. On your device it is different, so the command you tried will not work.
You need to find out what the /system mount point is for your phone.
Open terminal from phone and type su.
Press enter.
At the # prompt type cat /proc/mtd
Press enter.
Look at the output on the screen and see what the mount point is for /system.
A the the # prompt type mount -o rw,remount -t ext4 /dev/block/enteryoursystemmountpointhere /system
Note: replace enteryourmountpointhere with your mount point from the previous step.
Change /system to ro when done. Hope this works for you.
Also download root checker app to ensure you rooted properly.
hwong96 said:
I understand your frustration, however, you should try to post your question to the MTK6572 or Samsung S4 thread. ......
Click to expand...
Click to collapse
thanks for your responce.
with that "cat ..." I got : "no such file or dir"...
I know already that my mnt point is (did try already these earlier):
mount -o rw,remount /dev/block/mmcblk0p4 system
mount -o remount,rw -t ext4 /[email protected] /system
but no success, " system read only" stays, and no change.
Jack_Rover said:
thanks for your responce.
with that "cat ..." I got : "no such file or dir"...
I know already that my mnt point is (did try already these earlier):
mount -o rw,remount /dev/block/mmcblk0p4 system
mount -o remount,rw -t ext4 /[email protected] /system
but no success, " system read only" stays, and no change.
Click to expand...
Click to collapse
Did you use the root checker app to verify for proper root?
hwong96 said:
Did you use the root checker app to verify for proper root?
Click to expand...
Click to collapse
yes.
I have many apps (e.g. FX, ATools, TitaniumBup, busybox, ES, mount /system rw, SD maid, root expl., adbd insec., rootAppDel, a.s.o.) that use root rights, and phone's superSU gives the rights to them.
AT:s terminal has # prompt, so it must be root. (?)
adbd insecure's current status = binary: insecure; usb debugging: enabled.
I have earlier version SU's binaries working ok, but updating SU made this binary-update-issue: " binary update failure" and so SU-app won't open (it closes after failing binary update), though otherwise it works ok (and worked earlier until I did let G-play to update it, silly me!).
somehow my /system has been "open" i.e. RW earlier, since busybox and superSU has been installed, but now it is "stuck" to that RO-status. "/" opens, but "/system" not.
MTK Droid Root & Tools v2.5.3 (from here xdadevs) gets root shell ok, but fails when trying to install SU, busybox a.s.o. ("read-only system") - and it "crashes".
maybe kernel related? or boot loader, or .... what?
-----
btw, my apologises, that I wrote this issue to this thread, but I found my "problem" here with the search, and after posting I realized that this is "tablet area..."
so this part can be moved to better place by those who know best where to - though not to trash, anyway....
Jack_Rover said:
yes.
I have many apps (e.g. FX, ATools, TitaniumBup, busybox, ES, mount /system rw, SD maid, root expl., adbd insec., rootAppDel, a.s.o.) that use root rights, and phone's superSU gives the rights to them.
AT:s terminal has # prompt, so it must be root. (?)
adbd insecure's current status = binary: insecure; usb debugging: enabled.
I have earlier version SU's binaries working ok, but updating SU made this binary-update-issue: " binary update failure" and so SU-app won't open (it closes after failing binary update), though otherwise it works ok (and worked earlier until I did let G-play to update it, silly me!).
somehow my /system has been "open" i.e. RW earlier, since busybox and superSU has been installed, but now it is "stuck" to that RO-status. "/" opens, but "/system" not.
MTK Droid Root & Tools v2.5.3 (from here xdadevs) gets root shell ok, but fails when trying to install SU, busybox a.s.o. ("read-only system") - and it "crashes".
maybe kernel related? or boot loader, or .... what?
-----
btw, my apologises, that I wrote this issue to this thread, but I found my "problem" here with the search, and after posting I realized that this is "tablet area..."
so this part can be moved to better place by those who know best where to - though not to trash, anyway....
Click to expand...
Click to collapse
Don't know what else to suggest, except maybe contact Chainfire on G+.
.
Hi! I'm having a few problems with my Galaxy Nexus, as it's been not booting with this CyanogenMod 11S bootanimation.zip I've been trying. I now want to remove it, but I can't boot into recovery due to hardware issues. I can adb into the phone though, but only shortly, before the system locks up.
I'm trying to do the following:
Code:
su
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
cp /sdcard/bootanimation.zip /system/media/bootanimation.zip
However, I can't use "su" - nothing really happens. It won't give me root, but it doesn't give any errors either, the $ sign doesn't change into a # sign, thus remounting system to rw fails and subsequently, I can't copy anything there.
I'm running PACman (4.4.2) and I have SuperSU installed. Any ideas?
Edit - Kind of solved, forgot adb reboot recovery existed.
Hello everyone
Can somebody help me i have accidently changed the permission of the folder /System/bin to [rw-r-r] in my lg g3 using CM13 nightly latest version.
now the phone wont boot only in recovery mode even if i reboot system it goes to the recovery.
is there a way to undo the changes i did or fix this problem ?
tetouan22 said:
Hello everyone
Can somebody help me i have accidently changed the permission of the folder /System/bin to [rw-r-r] in my lg g3 using CM13 nightly latest version.
now the phone wont boot only in recovery mode even if i reboot system it goes to the recovery.
is there a way to undo the changes i did or fix this problem ?
Click to expand...
Click to collapse
How do you accidently changed them?
Reffering to this Thread you could use adb to change permissions in recovery by:
Code:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
chmod 755 /system/bin
Edit: When just coying and pasting I forgot, that the part
Code:
yaffs2 /dev/block/mtdblock3
may be a little bit different on your device. I do not have a G3 at hand and did not find the fstab that fast, but you can run
Code:
mount
Code:
cat /proc/partitions
and so on out of the CM Porting tutorial to find out your parameter.
MichaelSX said:
How do you accidently changed them?
Reffering to this Thread you could use adb to change permissions in recovery by:
Code:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
chmod 755 /system/bin
Edit: When just coying and pasting I forgot, that the part
Code:
yaffs2 /dev/block/mtdblock3
may be a little bit different on your device. I do not have a G3 at hand and did not find the fstab that fast, but you can run
Code:
mount
Code:
cat /proc/partitions
and so on out of the CM Porting tutorial to find out your parameter.
Click to expand...
Click to collapse
I have reflashed my ROM now,
and about the accident ... well i was reading a tutorial about how to install stock G3 apps on cm13 and i did the permission things for the wrong folder, and that was the probleme :laugh: