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
Related
I am in need of read/write access to my system folder. I am simply trying to copy some ringtones and add a boot animation.
I have SGS tools and ran the r/w script, which allowed me to VIEW the folder with Droid Explorer, however I am unable to actually copy TO the system folder or its subfolders.
Any ideas on what I'm doing wrong?
EDIT - I've also tried to push the files to the phone via ADB, but I get an error telling me "Failed: Operation Not Permitted".
EDIT x2 - I've also got Root Explorer installed on the phone and it showed R/W access, but again, I can't get any files pushed to the phone.
Did you allow sgs tools to get a root permission?
Sent from my SGH-I897 using XDA App
Did you try fixing permissions through cwm recovery?
try root explorer. and double check superuser permissions
goob1284 said:
Did you allow sgs tools to get a root permission?
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
Yup.
Did you try fixing permissions through cwm recovery?
Click to expand...
Click to collapse
I noticed a section for both "mount /system" and also permissions... Both: DONE.
try root explorer. and double check superuser permissions
Click to expand...
Click to collapse
Done & Done...
I've still got no access to R/W in any of the system folders/subs. Any ideas?
I am having the same problem with root explorer..
I have fixed permissions in CWM
It had worked once but now it wont mount r/rw in system folder. Press the icon and it does nothing.
Superuser permission in SGS tools, Root exploer all show active
Any ideas?
Anyone else have any ideas? I'm totally puzzled at this point.
I have sort of fixed the problem..
I go into SGS tools and run the batch file to give r/rw permissions, then I can mount r/rw in system folder, but I loose this each time I reboot and I think when I connect USB..
but it works for the purpose I needed!
I think I've found a work around (or maybe the way it was SUPPOSED to work)...
I rebooted the phone in recovery. Then, selected "mount /system". Then I went to Advanced and "Fix Permissions" (don't know if I had do, just did).
THEN - I was able to FINALLY push the files to the correct folders! I tried it using ADB commands and also with Droid Explorer - Both worked great.
I don't know if the phone was always supposed to be in recovery to do it, but it worked!
OK. Pardon Adndroid Noooobness.
I have the device incompatible Android Market problem with NC.
Running CM7
I found two fixes.
1. Set DPI to 160
2. Edit Build.prop to make nook present itself as smamsung *something S*
I downloaded ROM Toolbox and after going through what I think is EVERY icon and setting I cannot find where or how to change the DPI setting.
I have modified the build.prop file using ES File Explorer but cannot get the file to copy back from the sdcard to the system folder. Protected or in use probably. Tried booting to CW to copy but dont know how to do that either.
How can I get actully appy either of these. I have searched but cannot find this answer.
Thanks
How about just reverting to the old market, clearing the market data/cache and uninstalling the market updater app?
did not seem to help for me
Did that as well and that did not work. As soon as I connected to the Market it closed and updated. This was after removing the updater and clearing the cache.
On another note, does anyone have the BN reader.apk and the Kindle.apk. Hope I have that terminology right, and the instructions for installing apk files. Sure I can find those instructions.
Thanks
To edit the file in /system, start up Terminal, become root by typing "su" and remount the /system partition by typing "mount -o rw,remount /system". Then you can edit all you like. When you're done type "mount -o ro,remount /system" or just reboot.
aegrotatio said:
To edit the file in /system, start up Terminal, become root by typing "su" and remount the /system partition by typing "mount -o rw,remount /system". Then you can edit all you like. When you're done type "mount -o ro,remount /system" or just reboot.
Click to expand...
Click to collapse
I have CM7 on an SD card and tried this command. I get the following:
mount: not found
Any suggestions?
I tried this command and I am not sure I am putting it in right. I do not a space "remount/system" and a bunch of commands come up. I do use a space and nothing. Either way, I am unable to edit or copy a new file in. Copy failed or cannot save file.
Do I have to copy from within the Terminal window? After running this command I go into ES file explorer to edit or copy with no luck.
<Set DPI to 160>
There is an app called LCDDensity which allows you to alter the DPI on the nook. If the market allows you to download it, or you are able to sideload it, you might try that.
What happens for me is my market will stop working, then I use LCDDensity to set the DPI to 160 or 240, and reboot. Then the market works, but only for a day or two, and then things seem to reset. (I have tried freezing and renaming the market app, and market updater app, but it doesn't seem to have any effect. Then again I'm new to these things myself, and could be missing something silly.)
It isn't an ideal solution, but it seems fine unti a more permanent fix comes along.
Hi mates. I am experiencing issues in editing the build.prop. I mean: even if I can access the file, when I try to save it, it tells me I cannot...
I use file expert to browse and jota text to edit (both free). Es file explorer does not allow me to set root option...maybe it it's not working with note yet...
In any case I don't know what to do to save the new build.prop.
Any suggestions?
Thx to all...
Sent from my GT-N7000 using XDA App
Diamantes said:
Hi mates. I am experiencing issues in editing the build.prop. I mean: even if I can access the file, when I try to save it, it tells me I cannot...
I use file expert to browse and jota text to edit (both free). Es file explorer does not allow me to set root option...maybe it it's not working with note yet...
In any case I don't know what to do to save the new build.prop.
Any suggestions?
Thx to all...
Sent from my GT-N7000 using XDA App
Click to expand...
Click to collapse
Es explorer works well. u might have found it if u searched.
Just make sure that u have enabled root options in the settings.
No.
As I wrote before, I don't know why but Es doesn't allow me to have root options enabled, so I was forced to find a new root explorer. The problem is that I can't save the new build.prop: the app tells me it cannot save the file...
Suggestions?
Sent from my GT-N7000 using XDA App
Install File Expert, go to settings and enable "Root Explorer" (under "File Explorer Settings"), go back, press menu, more and then "Mount".
/system is mounted RO by default.
use a shell and as root type
Code:
busybox mount -o remount,rw /system
you should get a full access now to all /system filesystem.
THANKS
BazookaAce said:
Install File Expert, go to settings and enable "Root Explorer" (under "File Explorer Settings"), go back, press menu, more and then "Mount".
Click to expand...
Click to collapse
Thx mate. It worked. After chose the option "Mount", I edit also the properties of the file (write,read,all...). After that, File expert allowed me to choose the app to open the text file: I choose ES text, because Jota text continued not saving the file. I finally saved the build.prop file.
THX.
sibere said:
/system is mounted RO by default.
use a shell and as root type
Code:
busybox mount -o remount,rw /system
you should get a full access now to all /system filesystem.
Click to expand...
Click to collapse
Thank you too.
uff!! what a pain in the ....ss!
Thanks guys! I enabled the Root checkbox, but I cant mount!
I get a Mount failed message.
I tried to be in the / directory when issued the Mount command for RW (using GUI in that application), and being inside /system as well - same error.
I've granted the application Superuser permissions, so thats not it.
Using Root Browser I am unable to delete or rename the install-recovery.sh file. Does anyone know why? Thank you. I also tried ES file explorer.
You need to have R/W privileges. Do you have root?
Mark Once Again said:
You need to have R/W privileges. Do you have root?
Click to expand...
Click to collapse
Yes root has been verified. Thanks for any help you can give Mark.
I use root explorer. Just navigate to the file. Make sure the permissions are R/W. If not, just push the Mount button so that it shows R/W instead of R/O. Should be good to go....
Mark Once Again said:
I use root explorer. Just navigate to the file. Make sure the permissions are R/W. If not, just push the Mount button so that it shows R/W instead of R/O. Should be good to go....
Click to expand...
Click to collapse
Thanks Bro. Good to go now.
I had the same problem, which is how I found this thread, and was not able to resolve it by remounting /system RW. However it turns out the file had the immutable attribute "i". I was able to remove the attribute and delete the file via:
Code:
su
chgattr -i /system/etc/install-recovery.sh
rm /system/etc/install-recovery.sh
recovery upgrade
how to upgrade the recovery. i have a old recovery. i want upgrade it to touch philz recovery plz help
both methods require a root explorer.
Method 1:
navigate to the system folder
find "App" folder
Change the name of "dtcp_apk.apk" to dtcp_apk.bat
Method 2:
Navigate to system folder
find "App" folder
change permissions of Dtcp_apk.apk to all blank
Hope this helped someone.
Credits to spunker88 for sharing this info.
the first method worked great for me
thanks
Dassen said:
both methods require a root explorer.
Method 1:
navigate to the system folder
find "App" folder
Change the name of "dtcp_apk.apk" to dtcp_apk.bat
Method 2:
Navigate to system folder
find "App" folder
change permissions of Dtcp_apk.apk to all blank
Hope this helped someone.
Credits to spunker88 for sharing this info.
Click to expand...
Click to collapse
I tried both without success.. What explorer are you using? I tried with ES and got an error "the operation failed".. and I couldnt change permissions neither
thanks for any help
Are you rooted?
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
blazeplacid said:
Are you rooted?
Click to expand...
Click to collapse
I supposed to. I rooted my device to install google play.. but I dont know if I continue been root.. I checked my permissions on system\app and I only have readable..
Could you explain me how to check if I am root, and if not, how to be root again to apply your process?
Thanks for your help
karacc said:
I supposed to. I rooted my device to install google play.. but I dont know if I continue been root.. I checked my permissions on system\app and I only have readable..
Could you explain me how to check if I am root, and if not, how to be root again to apply your process?
Thanks for your help
Click to expand...
Click to collapse
You go to the setting of ES,then at the bottom of setting menu, it has Root setting. Go there and checked all check boxes. If you can, that's mean your KF is rooted.
Sent from my KFTT using xda app-developers app
tried method 1 and it worked right away :good:
Worked
Method 1 worked for me.
Thanks.
Dassen said:
both methods require a root explorer.
Method 1:
navigate to the system folder
find "App" folder
Change the name of "dtcp_apk.apk" to dtcp_apk.bat
Method 2:
Navigate to system folder
find "App" folder
change permissions of Dtcp_apk.apk to all blank
Hope this helped someone.
Credits to spunker88 for sharing this info.
Click to expand...
Click to collapse
Worked for me, too. Was surprised about the beautiful wallpapers to see now everytime i turn the thingy on
Adding a Boot Animation
Thanks for this info. I used the 2nd method and it worked immediately. Are there Boot Animations for the KFHD? Or can Boot Animations from, say my LG ICS Spectrum work?
Dassen said:
both methods require a root explorer.
Method 1:
navigate to the system folder
find "App" folder
Change the name of "dtcp_apk.apk" to dtcp_apk.bat
Method 2:
Navigate to system folder
find "App" folder
change permissions of Dtcp_apk.apk to all blank
Hope this helped someone.
Credits to spunker88 for sharing this info.
Click to expand...
Click to collapse
Awesome, confirmed working on kindle fire 2 running 10.2.1
frieked said:
Awesome, confirmed working on kindle fire 2 running 10.2.1
Click to expand...
Click to collapse
Thanks a lot for this :highfive:
Confirmed works on KF 8.9, thanks OP! I renamed to dtcp_apk.ads
finally, those horrific ad screens are gone! thank you sir!
if you have adb available, you should be able to do this without a root explorer.
use one of the following codes:
adb shell
su
mount -o remount,rw /system
mv /system/app/dtcp_apk.apk /system/app/dtcp_apk.apk.bak
exit
exit
adb shell
su
mount -o remount,rw /system
chmod 000 /system/app/dtcp_apk.apk
exit
exit
adb shell
su
mount -o remount,rw /system
rm /system/app/dtcp_apk.apk
exit
exit
The first one will rename it. The second one will clear its permissions. The third one will remove it completely.
It should go without saying, but its not my fault if you screw something up, or if it is necessary to have this apk in your system, and you use the third method. I haven't tried it, but it should work. I do know what the commands do.
Didn't also work for me with es file explorer the first time i've tried it, although i've enabled all root options.
Rebooting the device helped me, but it's also important to make sure that you give the explorer the permission to change system data
Sent from my KFTT using XDA Premium HD app
Method 1 working
I tried it just out of curiosity and it worked right away. Using ES explorer, BTW.
Thanks!
Dassen said:
both methods require a root explorer.
Method 1:
navigate to the system folder
find "App" folder
Change the name of "dtcp_apk.apk" to dtcp_apk.bat
Method 2:
Navigate to system folder
find "App" folder
change permissions of Dtcp_apk.apk to all blank
Hope this helped someone.
Credits to spunker88 for sharing this info.
Click to expand...
Click to collapse
Thank you so much!!! Method 1 worked great. Also renamed the odex file to .odex.bat through root explorer. Note, in root explorer you will probably have to push the little 'Mount R/W" button once you get into system/app
Sweet. $15 saved.
Thanks for the quick 'how to'.