Database Develop

Cannot edit build.prop anymore - read-only.

Using Nook Color, CM7 nighly 107.
Got Netflix working a while back by modifying the build.prop file using ES File Explorer - no issues.
Tried again to make some mods and cannot save it anymore. ES reports "writable - NO"
Tried to "su chmod 666" it and it comes back with "File system read-only"
Is anybody else seeing this? What am I missing?
Thanks...

I encountered a similar situation during the build.prop edit while using ES File Explorer on my NC running CM7 on internal memory.
Possibly, the permissions in the program need to be changed to enable it to "write".
Here's what I did: Menu==>Settings==>Root options. "Check" Root Explorer and if my memory serves me correctly, click "Yes" to get past the "Experimental Feature", toggle the "Cyanogen Mod" (if you're using CM7) radio button, click OK and check the "Mount File System" box to make the system writable.
Now, it should be writable. Hope this helps.

dhyamato said:
... check the "Mount File System" box to make the system writable.
Click to expand...
Click to collapse
Thanks for the tip, that wasn't it
I remember setting those originally. I just checked again and "Root Explorer" and "Mount FIle System" are both checked.

mwilli20 said:
Using Nook Color, CM7 nighly 107.
Got Netflix working a while back by modifying the build.prop file using ES File Explorer - no issues.
Tried again to make some mods and cannot save it anymore. ES reports "writable - NO"
Tried to "su chmod 666" it and it comes back with "File system read-only"
Is anybody else seeing this? What am I missing?
Thanks...
Click to expand...
Click to collapse
In 106 SU wasn't working correctly until I reinstalled it. You can't modify build.prop without superuser rights. Check the thread about SU / Superuser missing in 106 (and I bet 107) for instructions. It worked for me.

DiDGR8 said:
Check the thread about SU / Superuser missing in 106 (and I bet 107) for instructions. It worked for me.
Click to expand...
Click to collapse
Interesting... the OP withdrew his post: (apparently it's back in 107)
http://forum.xda-developers.com/showthread.php?t=1131369
However when I checked it, the SU app was misbehaving, Force closing, refusing to respond to the menu command. So I reinstalled it. Now it's OK.
Unfortunately I still cannot edit the build.prop file.
I don't think it's a superuser problem because without SU access ES cannot even see the system folder!!! I can see it, and edit the file, just cannot save it.

You might try fixing permissions under recovery.

have you tried the app: nook netflix fixer?

I've changed it successfully on the past 6 consecutive nightlies using adbwireless pull/push. However since 106 I've hsd to reflash su. N108 hasn't given me the su issue. Is it fixed?

Same problem with the build.prop file: cannot save changes, or copy over it. Running in nightly 108 today. Tried both Root Explorer and ES File manager.

I think you need to change the build.prop file properties to be rw using chmod. Don't forget to mount system as rw before doing the chmod.
Sent from my Huawei Ascend using XDA App

foltz61 said:
I think you need to change the build.prop file properties to be rw using chmod.
Click to expand...
Click to collapse
Tried that (sudo chmod 666...), get the same message. "file system is read-only"

backup and restore fresh start....?

I'm not great at linux but I do it differently. Try chmod +rw /system/build.prop . Make sure you have system mounted as RW first. I'd also check superuser to make sure whatever terminal/file explorer you are using still has root privileges.
Sent from my Huawei-M860 using XDA App

foltz61 said:
Try chmod +rw /system/build.prop
Click to expand...
Click to collapse
666 is the same thing as +rw in this case...
It looks like the "fresh start" suggestion a couple of posts up is the best

All those numbers always confuse me . Sorry. Good luck.
Sent from my Huawei-M860 using XDA App

bike2002 said:
have you tried the app: nook netflix fixer?
Click to expand...
Click to collapse
Thanks! That did it!
Does anybody know why this app can modify the build.prop file while ES File Explorer cannot?

I had to mount the folder containing build.prop with rw access in order to use chmod. I think the latest version of the netflix fixer may do the same (see my post in that thread). In short, I used;
Code:
su
busybox mount -0 rw,remount /dev/block/mmcblk1p3 /system
in the terminal before using the chmod command in order to give myself rw permissions in the folder. I'm only two days old at this, so it beats me why root doesn't have normal rw permissions on the folder.

NCKevo said:
I had to mount the folder containing build.prop with rw access in order to use chmod...
Click to expand...
Click to collapse
Thanks for the tip. I ran the command successfully (by the way, small typo, I believe it's -o not -0) and was able to chmod and edit the file with vi.
That's where confusion began. I reboot and after the reboot I was able to modify the file without remounting the /system directory. The mount command does not surive a reboot does it?

Have you tried just pulling the build.prop
Code:
c:/<target_folder> adb pull /system/build.prop
then editing it with note pad then pushing it back and rebooting>

mwilli20 said:
That's where confusion began. I reboot and after the reboot I was able to modify the file without remounting the /system directory. The mount command does not surive a reboot does it?
Click to expand...
Click to collapse
That is confusing. What are the full (i.e. ls -l) permissions on the file now? (It's possible that it somehow ended up with o+w, but I don't understand how - vi isn't exactly known for changing permissions on-the-fly.)
Rodney

how to edit hosts file

I've been trying to work on this and still can't figure out how to do this can somebody give me a step by step
So far I've tried to inStall an ash server to go in and edit it but I cannot get it to work somebody to help

maxgohan said:
I've been trying to work on this and still can't figure out how to do this can somebody give me a step by step
So far I've tried to inStall an ash server to go in and edit it but I cannot get it to work somebody to help
Click to expand...
Click to collapse
two ways to change your hostname
1. open edit /system/etc/dhcpcd/dhcpcd.conf with your favorite text editor. under "interface eth0", type: hostname yourdesiredhostname
2. open your favorit terminal emulator, type: vi /system/etc/dhcpcd/dhcpcd.conf
make above mentioned changes.
-> reboot and it should be working. try to ping your device from another piece of hardware in your home network
if you want to change your hosts file - do the same with /etc/hosts ^^

I keep getting this line...
mv: can't remove '/etc/hosts': Read-only file system

is your device rooted? if yes, you have either so mount your root file system as writeable in your file explorer (if it supports root access, like ES File Explorer), or you have to type "su root" at the beginning of your terminal emulator operations.

same problem with a rooted and unlocked device
two_handed said:
is your device rooted? if yes, you have either so mount your root file system as writeable in your file explorer (if it supports root access, like ES File Explorer), or you have to type "su root" at the beginning of your terminal emulator operations.
Click to expand...
Click to collapse
my device is rooted with kingroot I have installed root explorer and ES file explorer too with giving them root permission as well , but when ever I tried to delete or edit hosts file nothing gets change (with root explorer) and with ES file explorer it says " read only file " I tried to change the permission in properties but failed to save the check boxes result. oh man I forget to mention my problem here my cell is infected by a "freedom" app when finally I found it useless I changed the freedom app setting to "freecore" my device got reboot after that I uninstalled the app , now I am unable to connect with google servers , can't use play store , I also tried hosts file Editor but got no result I know my problem is to delete the hosts file , but something is not letting me to take control over hosts file , my android is 5.1 and model is huawei honor 4c ?

need to delete system file but can't :(

I need to follow these instructions -
Originally Posted by Robbie Hood
i will upload a revert back too mtp mod once the party is over.
If you really need it now then do this :
go to /system/build.prop and open it with a rooted text editor ( most file explorers have one) and remove this line:
Code:
persist.sys.usb.config=mass_storage,adb
then go to /system/etc/init.d and remove the S98MassStorage script.
Reboot and it should work fine.
If not , then you need to check rom customizer/. manage system apps / uninstalled tab and install anything kies, usb or mtp related
I have done the first part and removed - persist.sys.usb.config=mass_storage,adb but I can't change/delete/edit/move the S98MassStorage script, I have tried Root Browser Lite, ZArchiver and ES File Explorer.
Can somebody help me please, recommend a method/app?

Try "su -"
Then "rm whateverscript.sh"
To delete the file.
Assuming u got root perms.
Sent from my GT-N7000 using xda app-developers app

Make sure your /system is mounted read-write. It should be, since you edited build.prop, but you can double-check (there's an option in ES File Explorer to mount /system as read-write).

[Q] How can I change the hangouts emoticons (emoji) back to Google ones?

Hi,
I have updated my HTC One to android 4.4, sense 5.5 (latest update from HTC). After the update I see that the emoticons in the Google hangouts app have been changed to HTC emoticons.
I was used to the emoticons in my hangouts app and now they have been changed and I am very disappointed.
Is there a way to get the Google emoticons back? I don't like the ones that HTC provides.
I have attached a screen shot.
If I could also change the emoticons/emojis to Google system-wide I would be more glad.

183.amir said:
Hi,
I have updated my HTC One to android 4.4, sense 5.5 (latest update from HTC). After the update I see that the emoticons in the Google hangouts app have been changed to HTC emoticons.
I was used to the emoticons in my hangouts app and now they have been changed and I am very disappointed.
Is there a way to get the Google emoticons back? I don't like the ones that HTC provides.
I have attached a screen shot.
If I could also change the emoticons/emojis to Google system-wide I would be more glad.
Click to expand...
Click to collapse
I'd like to know this as well. I much prefer the Google emoticons in Hangouts.

imminentwill said:
I'd like to know this as well. I much prefer the Google emoticons in Hangouts.
Click to expand...
Click to collapse
I think this should either be provided by Google Hangouts app or we need to use a custom framework.

Finally figured it out myself and thought I should share! You need root for this to work.
Get a file browser app that can browse system files. I suggest Root Browser or ES File Explorer.
Navigate to /system/fonts/
While in the fonts folder, you should see a font named "AndroidEmoji-htc.ttf" and a "AndroidEmoji.ttf".
Rename "AndroidEmoji-htc.ttf" to "AndroidEmoji-htc.ttf.nothankyou" or whatever file extension you prefer. Just make sure it's not .ttf or any other font file extension or the system will still read it.
Doing this will make the system fall back to "AndroidEmoji.ttf" which contains the hangous emojis.
Reboot and you will see the results.
Enjoy!

Okay, so you changed the Emoji in your conversation to match your keyboard. What if I wanted to go the other way ’round and skin my keyboard Emoji to match what’s in the conversation?

Musenkishi said:
Finally figured it out myself and thought I should share! You need root for this to work.
Get a file browser app that can browse system files. I suggest Root Browser or ES File Explorer.
Navigate to /system/fonts/
While in the fonts folder, you should see a font named "AndroidEmoji-htc.ttf" and a "AndroidEmoji.ttf".
Rename "AndroidEmoji-htc.ttf" to "AndroidEmoji-htc.ttf.nothankyou" or whatever file extension you prefer. Just make sure it's not .ttf or any other font file extension or the system will still read it.
Doing this will make the system fall back to "AndroidEmoji.ttf" which contains the hangous emojis.
Reboot and you will see the results.
Enjoy!
Click to expand...
Click to collapse
do you think there is a way to get the emoticons used in whatsapp for hangouts also?

herwegan said:
do you think there is a way to get the emoticons used in whatsapp for hangouts also?
Click to expand...
Click to collapse
Well... I don't know. In my post, I basically just remove the emojis that HTC put in the Android system and let it fall back on the original emojis in KitKat, which is the same as the Hangouts.
If there is an emoji font inside the whatsapp APK, then it might be possible to rename it to "AndroidEmoji-htc.ttf", and put it in /system/fonts/. This way, your phone would think it's loading the HTC emojis, but in reality it would be the whatsapp emojis. Might be possible with any emoji font pack actually.

thank you this worked perfectly!

Musenkishi said:
Finally figured it out myself and thought I should share! You need root for this to work.
Get a file browser app that can browse system files. I suggest Root Browser or ES File Explorer.
Navigate to /system/fonts/
While in the fonts folder, you should see a font named "AndroidEmoji-htc.ttf" and a "AndroidEmoji.ttf".
Rename "AndroidEmoji-htc.ttf" to "AndroidEmoji-htc.ttf.nothankyou" or whatever file extension you prefer. Just make sure it's not .ttf or any other font file extension or the system will still read it.
Doing this will make the system fall back to "AndroidEmoji.ttf" which contains the hangous emojis.
Reboot and you will see the results.
Enjoy!
Click to expand...
Click to collapse
is there a way to do this without having root?

Any ideas on making this work without root?
Sent from my HTC One using Tapatalk

robgee789 said:
Any ideas on making this work without root?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I'd love to find a non rooted solution as well. Anyone got any ideas?

IIIMik3 said:
I'd love to find a non rooted solution as well. Anyone got any ideas?
Click to expand...
Click to collapse
I also need a non rooted solution for my HTC One M8. This is driving me crazy.

Musenkishi said:
Finally figured it out myself and thought I should share! You need root for this to work.
Get a file browser app that can browse system files. I suggest Root Browser or ES File Explorer.
Navigate to /system/fonts/
While in the fonts folder, you should see a font named "AndroidEmoji-htc.ttf" and a "AndroidEmoji.ttf".
Rename "AndroidEmoji-htc.ttf" to "AndroidEmoji-htc.ttf.nothankyou" or whatever file extension you prefer. Just make sure it's not .ttf or any other font file extension or the system will still read it.
Doing this will make the system fall back to "AndroidEmoji.ttf" which contains the hangous emojis.
Reboot and you will see the results.
Enjoy!
Click to expand...
Click to collapse
Obviously I have not rooted yet. What type of root does this require to have permissions to do this? Thanks in advance.

Musenkishi said:
Finally figured it out myself and thought I should share! You need root for this to work.
Get a file browser app that can browse system files. I suggest Root Browser or ES File Explorer.
Navigate to /system/fonts/
While in the fonts folder, you should see a font named "AndroidEmoji-htc.ttf" and a "AndroidEmoji.ttf".
Rename "AndroidEmoji-htc.ttf" to "AndroidEmoji-htc.ttf.nothankyou" or whatever file extension you prefer. Just make sure it's not .ttf or any other font file extension or the system will still read it.
Doing this will make the system fall back to "AndroidEmoji.ttf" which contains the hangous emojis.
Reboot and you will see the results.
Enjoy!
Click to expand...
Click to collapse
I have a rooted M7, I've granted ES File Explorer SuperUser, and I get "task failed" when i try to rename it, and "Read only file system" when I try to delete it. Nothing is working
EDIT: Using Root Explorer instead of ES File Explorer worked. Not sure why, but I'm glad I know Root Explorer will work for me.

JMB2772 said:
I have a rooted M7, I've granted ES File Explorer SuperUser, and I get "task failed" when i try to rename it, and "Read only file system" when I try to delete it. Nothing is working
EDIT: Using Root Explorer instead of ES File Explorer worked. Not sure why, but I'm glad I know Root Explorer will work for me.
Click to expand...
Click to collapse
still hoping for a non-root solution to this. :fingers-crossed:

Me too mate but I don't think it's gonna happen
Sent from my HTC One using Tapatalk

Just run the weaksauce root for your HTC One M8 guys and you'll have no problems following the OP's instructions- literally takes 1 minute to root, 30 seconds to change the emoticons and you are good to go!
I rooted on my first day picking up the M8 and it's been awesome since

JMB2772 said:
I have a rooted M7, I've granted ES File Explorer SuperUser, and I get "task failed" when i try to rename it, and "Read only file system" when I try to delete it. Nothing is working
EDIT: Using Root Explorer instead of ES File Explorer worked. Not sure why, but I'm glad I know Root Explorer will work for me.
Click to expand...
Click to collapse
Just an FYI for anyone else who gets the "read only file system error" in ES File Explorer. There are actually two steps required to configure ES to be able to access and modify files on the system partition.
Step one, you've done, is grant ES superuser access. But all this does is give ES read-only access to the protected system partition. In order to actually make changes to any files on system, you also need to enable read-write access to system.
Step two, In the same place you enable superuser access in ES, you can tap the option to open up another menu, choose Mount R/W, and then select /system.
Now you will be able to actually modify files on the system partition. This is essentially what root explorer does in the background, it just starts up with system mounted as readwrite. But since ES can be used by users without root, it defaults to read-only for system, and must be specifically configured for read-write.
---------- Post added at 02:23 PM ---------- Previous post was at 02:15 PM ----------
IIIMik3 said:
still hoping for a non-root solution to this. :fingers-crossed:
Click to expand...
Click to collapse
Well, there's no way for a non-root device to modify files on the system partition. This is what root gives you, access to modify /system. So without root, there's just no way to accomplish this modification. If the emoji files were stored on /data, then you'd be able to make some changes. But they're stored on /system, which the user on a non-root device is blocked from accessing.
A little background on the "why" this is:
If the user had full read-write to /system by default on a stock device, then any app in the Play Store or sideloaded could compromise your security and make unauthorized changes to your device. This is why /system is protected. By rooting your device, you are removing this protection. You the user are essentially taking on the responsibility to ensure that anything you install from that point forward is safe and trusted. If you install something and grant it root access, it then has access to every file on your device. Because of the very real security dangers involved with rooting, no device will ever come rooted from the factory, and no Play Store app will be able to access /system without being rooted.

trjlive said:
Just an FYI for anyone else who gets the "read only file system error" in ES File Explorer. There are actually two steps required to configure ES to be able to access and modify files on the system partition.
Step one, you've done, is grant ES superuser access. But all this does is give ES read-only access to the protected system partition. In order to actually make changes to any files on system, you also need to enable read-write access to system.
Step two, In the same place you enable superuser access in ES, you can tap the option to open up another menu, choose Mount R/W, and then select /system.
Now you will be able to actually modify files on the system partition. This is essentially what root explorer does in the background, it just starts up with system mounted as readwrite. But since ES can be used by users without root, it defaults to read-only for system, and must be specifically configured for read-write.
---------- Post added at 02:23 PM ---------- Previous post was at 02:15 PM ----------
Well, there's no way for a non-root device to modify files on the system partition. This is what root gives you, access to modify /system. So without root, there's just no way to accomplish this modification. If the emoji files were stored on /data, then you'd be able to make some changes. But they're stored on /system, which the user on a non-root device is blocked from accessing.
A little background on the "why" this is:
If the user had full read-write to /system by default on a stock device, then any app in the Play Store or sideloaded could compromise your security and make unauthorized changes to your device. This is why /system is protected. By rooting your device, you are removing this protection. You the user are essentially taking on the responsibility to ensure that anything you install from that point forward is safe and trusted. If you install something and grant it root access, it then has access to every file on your device. Because of the very real security dangers involved with rooting, no device will ever come rooted from the factory, and no Play Store app will be able to access /system without being rooted.
Click to expand...
Click to collapse
Ah, thanks for this! I'm glad I was able to get it to work with root explorer before this, but I'm glad I know how ES works now.

Hello everyone
I just want to get feedback on something... I use Go SMS Pro, but people using hangouts that I speak with, because I use the emoji provided by the app (iPhone emoji), they don't get most of them, which is very annoying... has anyone faced this? Is this happening just because of the emojis not being integrated? (If I press the button for emojis on the app, I get iPhone' s emojis, but not if i use the SwiftKey shortcut...)
Btw, I tried sending about 50 emoji. Hangouts got 25... :S
Sent from my GT-N5110 using XDA Free mobile app

[Fix] ES File Explorer root error

When you try and toggle the "Root Explorer" switch to enable root in ES File Explorer, you are met with and error
"Sorry, test failed. This feature cannot run on your device. Root Explorer"
Use another root explorer app with root permissions, and copy the contents of /su/bin/ (about 7 files) and paste them inside /system/xbin/
Now try turning root explorer on in ES File Explorers Tools setting
It should now turn on and work fine
Credit: Youtube commenter "Daniel Velez"
Code:
https://www.youtube.com/watch?v=TlWoSlvhzI0

*Detection* said:
When you try and toggle the "Root Explorer" switch to enable root in ES File Explorer, you are met with and error
"Sorry, test failed. This feature cannot run on your device. Root Explorer"
Use another root explorer app with root permissions, and copy the contents of /su/bin/ (about 7 files) and paste them inside /system/xbin/
Now try turning root explorer on in ES File Explorers Tools setting
It should now turn on and work fine
Credit: Youtube commenter "Daniel Velez"
Code:
https://www.youtube.com/watch?v=TlWoSlvhzI0
Click to expand...
Click to collapse
Thank you[emoji106]!!
It works fine on G900F Marshmallow rooted with SuperSU 2.72 systemless!
Inviato dal mio SM-G900F utilizzando Tapatalk

Thanks for the hint!
But this error made me change from ESFE to FX + Root Add On.
It's more comfortable in my opinion.

Perfect! Thanks!!!
[emoji106][emoji106]
[emoji122][emoji122][emoji122]

Thank you very much! Worked on my 900F as well!

Great
Thank you so much for a solution :highfive:

New ES File Explorer version now supports Systemless root. Works on my Note 5

If this happens after installing a new ROM you must enable developer options and then set route and then restart the phone or tablet and then that won't happen

Great, thank you.

ES File explorer root error
Thanks, works great!

Titanium Backup
Thanks for the hint (works also with secure settings)
Unfortunately Titanium Backup doesn't recognize root anymore
It got a problem with the /system/xbin/su command.

Still no success. I followed your steps still failed to get root access

Same here with jiayu s3 on Android 7.1 fom M.A.D.
Edit: Got Root Access with copying /su from rootdirectory to system/bin...

Hi!
I have es file explorer version 4.1.4.3 and I have root access without problems

This method works for me, though I'm running a Note Edge MM 6.0.1

I'm on the J7 and having this problem because of Samsung. Moving the files to xbin doesn't work with Root Explorer. Says Copy failed. So even after it's mounted RW I can't copy and paste files. Strangely I was able to rename a file. Don't know why.
Did this trick. But copy still failed even though ES File Explorer got root successfully.
(FYI: Trying to copy sound files into the system.)
Any other ideas?
I am fed up with Samsung!!!

FOR ANY SAMSUNG: Figured it out. All my folder access troubles are Knox's fault! But I had to do a command line trick along with disabling Knox.
You'll need: Root Package Disabler and Terminal Emulator
*So after rooting get either Titanium Backup Pro (not free) or Root Package Disabler (free) or Package Disabler Pro (not free). (They do the same thing.)
*Open the program you installed. Find anything with "knox" in the name and disable it. I, personally, disabled Lookout as well because it often doesn't like advanced root apps or modifications. But it shouldn't block ES File Explorer.
*Open Terminal Emulator. Put in the commands below, one-at-a-time. Hit Enter after each. REBOOT WHEN YOUR DONE. (Source here.)
Code:
su
Code:
mount -o remount,rw /system
Code:
touch /sbin/su /system/bin/su /system/xbin/su
Code:
mount -o remount,ro /system
Code:
exit
Reboot and Root ES File Explorer again.
Note: ES File Explorer won't copy files to the system or other sensitive folders. You still need "Root Explorer" or maybe "Solid Explorer" for that. This makes ES File Explorer useless to me. However, you still need the steps above to copy sensitive system files in the other root enabled file browsers. So do it anyway.

Hi guys! I know this is an old thread and Samsung Space, but i still use ES File Explorer Pro 1.1.4.1 because i like it. But somehow i lost root. Don't know how and why, everything worked fine on my rooted (with Magisk 23.0) Xiaomi Redmi Note 7 with Android 10 (Sorry for that, but i didn't find anything else in the www about this problem). Now i receive the same message "Sorry, test failed. This feature cannot run on your device." and don't know how to solve this. I uninstalled and reinstalled ESFX, deleted it from the list of rooted Apps in Magisk and it asked for the permissions again.... fine..... granted! But still i can't activate it's root explorer. This doesn't work :
" Use another root explorer app with root permissions, and copy the contents of /su/bin/ (about 7 files) and paste them inside /system/xbin/"
....because there is no "/su/bin" and therefore i can't copy anything.

sensei_fritz01 said:
I still use ES File Explorer Pro 1.1.4.1 because i like it.
....because there is no "/su/bin" and therefore i can't copy anything.
Click to expand...
Click to collapse
Same issue here. I ended up copying all files from any folder containing "bin" (sbin, xbin, bin) to /system/xbin to no avail.
Not sure if it is accurate, but it seems like it is, but old ES cannot work on devices that have systemless root.