My build.prop file was modified with LCD Density Mode to modify the density of the screen. Before that modificatiln I made a backup of the stock version of build.prop.
Tonight i tried the OTA installation of .30 but it failed (after boot : android with red triangle and back on .26 and no OTA .30 available anymore) and it's probably failed because of the modified build.prop file (i read on other thread tbat the OTA checks that file).
So now i would like to restore the original file (the backup is stored in /sdcard/documents/build.prop).
To do that i do :
- launch Terminal Emulator
- su (to be root)
- mount -ro rw,remount /system
- launch Astro File manager and witb that app copy the backup of build.prop into /system/
But there i got an error msg "read-only file system"
I don't find what mistake i'm doing. Does somebody know how to help me ? Thanks
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
I'm guessing Astro is not being given root permissions. I recommend using Root Explorer instead of Terminal Emulator + Astro. One step, simple copy-paste. You will need to tap the "Mount R/O" button after starting the app.
Use Solid Explorer
Thank you for your answers, i will try that later (now i'm at office and i cannot connect to internet to get Root or Solid explorer
+1 on using Root Explorer -- although I have been using Total Commander for the exact same task and it worked beautifully. (TC has a better interface in my opinion, as well.)
Finally the ww file of the new firmware was available on asus support site and i did the updatd manually (put the file on /sdcard and reboot), that way it's not checking if build.prop was stock or not.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Ghorin said:
- mount -ro rw,remount /system
Click to expand...
Click to collapse
There's a typo here. It should read "mount -o" (for "option(s)", not "ro").
Edit: And btw, you don't have to use a file manager for this, personally I prefer to do these things commandline-style, just cp backupfilepath /system/build.prop and then mount -o ro,remount /system
d14b0ll0s said:
There's a typo here. It should read "mount -o" (for "option(s)", not "ro").
Edit: And btw, you don't have to use a file manager for this, personally I prefer to do these things commandline-style, just cp backupfilepath /system/build.prop and then mount -o ro,remount /system
Click to expand...
Click to collapse
In fact i first tryed the unix way by using nix commands but cp command was not found (connected as root in terminal)
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
You can copy it back in ES File Explorer (free).. make sure you change it in the settings to mount system as writable
I had ES File Explorer since july but i never went into settings since i've rooted my tab and thd settings yoj indicate are very knteresting. I'll use them next time. Thanks
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Ghorin said:
In fact i first tryed the unix way by using nix commands but cp command was not found (connected as root in terminal)
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
Right. I sometimes forget how crappy android shell experience can be without BusyBox installed.
Related
I just unlocked and rooted my nexus s. Now im trying to stop the phone from reinstalling the custom recovery image and all im getting is problems.
I put in the command
mount-o rw,remount/dev/block/mtdblock3 /system
And every single time i get
mount-o : permission denied
Anyone have any ideas? im worried about rebooting my phone now cause i don't want to go through the whole process again. After reading around on XDA it doesn't seem like you are required to do this. Does anyone know if it will reinstall the custom recovery image if i don't do this step? I have searched everywhere to figure out the problem. But stilll im coming up with nothing. I have found people with other devices that have this problem. But nothing about fixing it.
If anyone has any ideas i really need help ASAP
try and grant yourself superuser & then try.
"su"
"mount -o rw,remount /dev/block/mtdblock3 /system"
You need a space after mount. -o specifies the mount options. The command is mount
Sent from my Nexus S using XDA App
aye, didn't notice that, couple of needed spaces. I've modified my original post.
Thanks i tried it but now it says mount-o not found.
Sent from my Nexus S using XDA App
If it says mount-o not found there's not a space between mount and -o.
mount -o remount,rw .........
Sent from my Nexus S using XDA App
Sorry I read the post about the space after I posted it. But of course I'm having more problems sorry for being such an idiot.
After putting su the command works. But then I try
Mv install-recovery.sh install-recovery-no.sh
It says no such file found. Sorry if I sound like an idiot. It's just rooting my Nexus S is much harder than it was to root my old mt3g.
Sent from my Nexus S using XDA App
No Android expert but I have experience with the CL. Pretty sure you're going to need to cd into the dir or write the full path to the file.
BTW what are the cool kids using for command line these days? Any of them have tab type features? ex: cd /syst<TAB>/me<TAB> for cd /system/media/
B2L said:
Sorry I read the post about the space after I posted it. But of course I'm having more problems sorry for being such an idiot.
After putting su the command works. But then I try
Mv install-recovery.sh install-recovery-no.sh
It says no such file found. Sorry if I sound like an idiot. It's just rooting my Nexus S is much harder than it was to root my old mt3g.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I just used root explorer to rename the install-recovery.sh to install-recovery-no.sh. It disabled it from flashing over the clockwork mod recovery on reboot. After disabling it I flashed clockwork recovery again permanently.
Edit: The file is in the etc folder.
Sent from my Nexus S using XDA App
sarge363 said:
I just used root explorer to rename the install-recovery.sh to install-recovery-no.sh. It disabled it from flashing over the clockwork mod recovery on reboot. After disabling it I flashed clockwork recovery again permanently.
Edit: The file is in the etc folder.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Thanks i tried to just rename it with Root Explorer but it says it's a read only file. I can't figure out how to change it so it's not read only.
B2L said:
Sorry I read the post about the space after I posted it. But of course I'm having more problems sorry for being such an idiot.
After putting su the command works. But then I try
Mv install-recovery.sh install-recovery-no.sh
It says no such file found. Sorry if I sound like an idiot. It's just rooting my Nexus S is much harder than it was to root my old mt3g.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
B2L said:
Thanks i tried to just rename it with Root Explorer but it says it's a read only file. I can't figure out how to change it so it's not read only.
Click to expand...
Click to collapse
you have to include the path
Code:
su
mount -o rw,remount /dev/block/mtdblock3 /system
mv /etc/install-recovery.sh /etc/install-recovery.sh.bak
or
Code:
su
mount -o rw,remount /dev/block/mtdblock3 /system
cd /etc
mv install-recovery.sh install-recovery.sh.bak
It's really just a lot easier with Root Explorer. If you use root explorer app, you have to push the little button at the top that says "mount r/w" or something like that. I usually do that rather than run the mount command, because I always forget the syntax for that one.
Yeah just hit the "mount R/W" button on top when u open Root Explorer. It changes to "Mount R/O" and u can rename it after that.
Sent from my Nexus S using XDA App
hey guys!
i didn't know where to post this, mods please move it to the appropriate forum.
NOW FOR THE GOOD PART,
GUIDE: HOW TO SET /SYSTEM TO RW
this question has been asked a lot, and i felt a need to post a guide: the easiest method is to use root explorer and on the top right corner is a button saying either ro, or rw. ro means read-only, and rw means read-write.
now some of you may be asking: so what's the point of this thread? i can already set /system to rw in root explorer. and yes, that is true (and much easier than this way), but what if for some reason root explorer refuses to set the /system to rw when you really need to edit that one file? or what if you're in adb, and can't access root explorer? that has happened to me before, and maybe some of you. so instead of panicking and freaking out, try this method:
1) download terminal emulator from market (anyone will work)
2) open and type "su" (NO QUOTES) to make sure you have root access. (if you don't know what root is, then don't read this, it's a waste of time)
3) to remount /system to rw, type EXACTLY: mount -o remount rw /system (enter)
so it should look like this:
Code:
su
mount -o remount rw /system
this method does work on every android phone, and works in terminal emulator as well as in adb
in adb just do:
Code:
adb shell
su
mount -o remount rw /system
as always, i am not responsible for anything that happens to your phone.
also, you can download the following apps (example) that show you to set r/w access to system for the typing challenged...
Root explorer - not free
Es file explorer - free
I use es, haven't had a problem since.
Sent from my HTC Glacier using XDA App
h22aboi said:
also, you can download the following apps (example) that show you to set r/w access to system for the typing challenged...
Root explorer - not free
Es file explorer - free
I use es, haven't had a problem since.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
There are a few ways to do this. I personally encourage people to learn the ADB end of things. Sometime a nice pretty GUI will not get you out of a pickle.
h22aboi said:
also, you can download the following apps (example) that show you to set r/w access to system for the typing challenged...
Root explorer - not free
Es file explorer - free
I use es, haven't had a problem since.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Good for you. I have confronted this problem before, and just wanted to share my findings. This could be useful in the future.
Sent from my HTC Glacier using xda premium
It's always good to know another way to do things, but I also have never had a problem with ES File Explorer.
I installed Astro File Manager and I have a few questions.
1) When I look in the /data directory in the phone, it shows as empty. When I do a nandroid backup, and untar the result, I find numerous folders and files in data.tar and even find the original .apk files from the Market (/data/apps)
2) I found out my phone (obtained second hand from ebay) already has a custom ROM (InsertCoin) and expect is should already be rooted. So I tried Astro File Manager to edit the /build.prop where it says "screen capture=false" to switch it to true. Astro File Manager, is claimed to have root capability in this article
http://www.freeyourandroid.com/guide...dit-build-prop
But I find the Save button disabled and cannot write out the file. Why?
Is it possible or likely to have InsertCoin and NOT be rooted? How do I tell if my device is rooted?
Try es file explorer I don't think astro can access root files. Es can root explorer can to. Just go into settings and check the root access and mount /system I think is what it is.
And yes with a custom Rom you should be rooted.
You can check by downloading terminal emulator from the market then type su if super user pops up and asks to allow your rooted
Sent from my HTC Sensation XE with Beats Audio using xda premium
another useful tool is called root checker. downloadable on the maret. one click and it will tell you if your rooted. also give you the best way to root for your device if you arent.
and yes es file manager is good for re-writing files.
wadill said:
Try es file explorer I don't think astro can access root files. Es can root explorer can to. Just go into settings and check the root access and mount /system I think is what it is.
And yes with a custom Rom you should be rooted.
You can check by downloading terminal emulator from the market then type su if super user pops up and asks to allow your rooted
Sent from my HTC Sensation XE with Beats Audio using xda premium
Click to expand...
Click to collapse
I confirmed my device is rooted with the terminal emulator.
When I try to edit /system/build.prop (by choosing to use the text file editor) from es file explorer, it is still leaving the Save button disabled and I cannot write the file back out. I remembered to check root access and mount /system.
So, how do I edit /system/build.prop on a rooted device?
(And es file explorer shows me my /data directory.)
tk_xda said:
I confirmed my device is rooted with the terminal emulator.
When I try to edit /system/build.prop (by choosing to use the text file editor) from es file explorer, it is still leaving the Save button disabled and I cannot write the file back out. I remembered to check root access and mount /system.
So, how do I edit /system/build.prop on a rooted device?
(And es file explorer shows me my /data directory.)
Click to expand...
Click to collapse
I use Root Explorer, it has an easy mount r/w option.
If everything else fails use ADB and Notepad++ on the PC.
In essence:
adb pull /system/build.prop AN_UNEDITED_FILE
Notepad++ to edit it, making sure EOL is set to UNIX
adb shell, su, "mount /system as r/w", cd /system, cp build.prop build.prop-
adp push AN_EDITED_FILE /system/build.prop
The mount r/w comand is:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
I think that's it, I'm sure folks will correct me if I'm wrong.
tk_xda said:
I confirmed my device is rooted with the terminal emulator.
When I try to edit /system/build.prop (by choosing to use the text file editor) from es file explorer, it is still leaving the Save button disabled and I cannot write the file back out. I remembered to check root access and mount /system.
So, how do I edit /system/build.prop on a rooted device?
(And es file explorer shows me my /data directory.)
Click to expand...
Click to collapse
I just was able to change my build prop with es so I'm unsure why you cannot. I used the es note also and when finished I pressed the menu button and save was available.
Also this version of es file explorer I just used is brand new I've never used this update, it was included in the newest hd revolution sense 3.0.
I suggest just trying again. Possibly try another app or use the adb method if you think you can. Adb only looks hard really its just copy and paste.
I wish I had more advice but I can't replicate the same problem. Keep at it its just something simple were overlooking.
Sent from my HTC Sensation XE with Beats Audio using xda premium
wadill said:
I just was able to change my build prop with es so I'm unsure why you cannot. I used the es note also and when finished I pressed the menu button and save was available.
Also this version of es file explorer I just used is brand new I've never used this update, it was included in the newest hd revolution sense 3.0.
I suggest just trying again. Possibly try another app or use the adb method if you think you can. Adb only looks hard really its just copy and paste.
I wish I had more advice but I can't replicate the same problem. Keep at it its just something simple were overlooking.
Sent from my HTC Sensation XE with Beats Audio using xda premium
Click to expand...
Click to collapse
True regarding ADB, but it's guaranteed to work. The other thing is you can also do so much more with it.
As always YMMV.
I rooted with the method from this thread: http://forum.xda-developers.com/showthread.php?t=1531646 and then installed superuser. I then tried to update the binary from 3.0.3.2 or whatever to 3.1, but it fails on mounting /system as rw. I tried reinstalling superuser but no dice. Thanks in advance.
Super user apk doesn't come with the binary. I too had issues, couldn't mount /system as RW, I mounted as RW using ES File Explorer and then reran the binary update.
You could manually install it from the V6 Supercharger files, copy/paste using a rooted file explorer or pushing with adb.
Sent from my Acer Iconia Tab A100 using xda app-developers app
DJ_SpaRky said:
Super user apk doesn't come with the binary. I too had issues, couldn't mount /system as RW, I mounted as RW using ES File Explorer and then reran the binary update.
You could manually install it from the V6 Supercharger files, copy/paste using a rooted file explorer or pushing with adb.
Sent from my Acer Iconia Tab A100 using xda app-developers app
Click to expand...
Click to collapse
Worked like a charm. Thanks!
Glad to hear.
Sent from my SGH-T679 using xda app-developers app
DJ_SpaRky said:
Super user apk doesn't come with the binary. I too had issues, couldn't mount /system as RW, I mounted as RW using ES File Explorer and then reran the binary update.
You could manually install it from the V6 Supercharger files, copy/paste using a rooted file explorer or pushing with adb.
Sent from my Acer Iconia Tab A100 using xda app-developers app
Click to expand...
Click to collapse
Hi,
I am having the same peoblems and have no idea how to remount as rw with ES explorer or how to use the other method you mentioned, i rooted my archos 70H 250gb with the chulri root method.
bigmoe42 said:
Hi,
I am having the same peoblems and have no idea how to remount as rw with ES explorer or how to use the other method you mentioned, i rooted my archos 70H 250gb with the chulri root method.
Click to expand...
Click to collapse
Open es file explorer, go to settings > root enhancements > check all of them, the third one down is "mount /system rw". Then re-run the binary update. If its cool, you can revert the root enhancements if you want.
Romman0 said:
Open es file explorer, go to settings > root enhancements > check all of them, the third one down is "mount /system rw". Then re-run the binary update. If its cool, you can revert the root enhancements if you want.
Click to expand...
Click to collapse
Thanks. I've tried that about 5 times but it isnt working. Should I in some way try to update the binary within ES explorer?
bigmoe42 said:
Thanks. I've tried that about 5 times but it isnt working. Should I in some way try to update the binary within ES explorer?
Click to expand...
Click to collapse
I'm not familiar with how to do that. If your using superuser, you could try using supersu.
I have tried superuser about 10-15 times to update the binary also but that doesn't work either.
Romman0 said:
I'm not familiar with how to do that. If your using superuser, you could try using supersu.
Click to expand...
Click to collapse
have been searching for a while.
DJ_SpaRky said:
Super user apk doesn't come with the binary. I too had issues, couldn't mount /system as RW, I mounted as RW using ES File Explorer and then reran the binary update.
You could manually install it from the V6 Supercharger files, copy/paste using a rooted file explorer or pushing with adb.
Sent from my Acer Iconia Tab A100 using xda app-developers app
Click to expand...
Click to collapse
Thanks!!..worked easily..
I have installed supersu
Inviato dal mio A100 con Tapatalk 2
bit different
Halo xda
I've got here something bad with my zopo 980. rootingvia framaroot went fine everything worked but then I update SU and when it was done it
told me to update binary so I tried (but I dont even know what it is) but it just went wrong every time... so I a bit pi**... you know and I unroot again via framaroot... now I tried to root again but it again told me to update binary and I'm still not able to do that.. it always kick me out of SuperSU...
so please if someone know how to solve give me please a reply... :'-(
oh yes and the other thing is that I dont have root acces
thakns a lot for any possibility and sorry for my bad english...
Alright I want to move my location spoofer app to /system/app so I can watch my hometown team on MLB.tv. This worked fine on my LG Nitro running CM10, but when I tried on my stock infinity (rooted, not updated), it won't let me. It just says "paste failed" when I try to move it. Anyone have any advice as to how to fix this?
Have y o u tried mounting the directory as rw so you can paste in there?
Sent from my ASUS Transformer Pad TF700T using xda premium
Sinker1345 said:
Have y o u tried mounting the directory as rw so you can paste in there?
Sent from my ASUS Transformer Pad TF700T using xda premium
Click to expand...
Click to collapse
No I haven't, but just to clarify the app is currently installed on the internal memory, not sd card. I am just trying to move it from one folder to a different folder. Is this still necessary?
It may be, if the directory is mounted as read only you won't be able to copy into it
Sent from my SCH-I535 using xda premium
mgoblueno1 said:
No I haven't, but just to clarify the app is currently installed on the internal memory, not sd card. I am just trying to move it from one folder to a different folder. Is this still necessary?
Click to expand...
Click to collapse
In normal operation, /system is mounted read-only, so you need to remount it as writable first. Root-enabled file managers usually have an option for that.
Thanks guys, will try this out tonight
Alright I tried editing permissions on the system folder, the app, and the root manager app, but they were already all checked (read, write, execute). I also tried just cut/pasting a picture i took to /system/app and I didn't work either...
EDIT: I just tried the remount app, and rewrote the /system folder as rw and it still didn't work
If anyone else has any suggestions on how to fix this let me know!
mgoblueno1 said:
If anyone else has any suggestions on how to fix this let me know!
Click to expand...
Click to collapse
mgoblueno1 said:
Alright I tried editing permissions on the system folder, the app, and the root manager app, but they were already all checked (read, write, execute). I also tried just cut/pasting a picture i took to /system/app and I didn't work either...
Click to expand...
Click to collapse
That's not how you do it. Those are chmod permissions for files and directories. That controls which user groups have rwx permissions for access; nothing to do with mounts. To allow for rw access to /system you need to either do it from within a root browser (ES file explorer, tools), the remount app, or type this into the terminal:
Code:
su
mount -o remount,rw /system
Copy your file or directory, then remount the system back as ro (so you don't accidentally delete something - that's why its mounted ro by default)
Code:
su
mount -o remount,ro /system
mgoblueno1 said:
EDIT: I just tried the remount app, and rewrote the /system folder as rw and it still didn't work
Click to expand...
Click to collapse
I just tried this and it works fine. After you made your selections for /system and rw, did you click the top "Remount" button and get a small pop-up "Success!..." notification that it completed its operation? I also verified that I could copy a test file into /system/app after toggling these settings. You are doing something wrong. Read this all again.
[Edit] The only reason I can think of that it might be failing is you are really not rooted or have a corrupt root. If all else fails, run the Root Checker app to see if you really have valid root. Open up your su app and see if it prompts you to update its binaries and let it if it does (superSU).
elfaure said:
That's not how you do it. Those are chmod permissions for files and directories. That controls which user groups have rwx permissions for access; nothing to do with mounts. To allow for rw access to /system you need to either do it from within a root browser (ES file explorer, tools), the remount app, or type this into the terminal:
Code:
su
mount -o remount,rw /system
Copy your file or directory, then remount the system back as ro (so you don't accidentally delete something - that's why its mounted ro by default)
Code:
su
mount -o remount,ro /system
I just tried this and it works fine. After you made your selections for /system and rw, did you click the top "Remount" button and get a small pop-up "Success!..." notification that it completed its operation? I also verified that I could copy a test file into /system/app after toggling these settings. You are doing something wrong. Read this all again.
[Edit] The only reason I can think of that it might be failing is you are really not rooted or have a corrupt root. If all else fails, run the Root Checker app to see if you really have valid root. Open up your su app and see if it prompts you to update its binaries and let it if it does (superSU).
Click to expand...
Click to collapse
Thanks this worked!
mgoblueno1 said:
Thanks this worked!
Click to expand...
Click to collapse
Glad you got it worked out. Which way worked for you?