Is anyone else having issues with Root Explorer not saving the build prop right after edit. I go back in to system and the backup file is full size, but the file I edited was 0 kb . I checked the r/w icon so it would let me do it. I've done this at least a hundred times and had it work, but now it doesn't work right. The first few times I didn't notice what happened and rebooted. It was ugly, no boot animation, and black screen from there on.
SigLover21 said:
Is anyone else having issues with Root Explorer not saving the build prop right after edit. I go back in to system and the backup file is full size, but the file I edited was 0 kb . I checked the r/w icon so it would let me do it. I've done this at least a hundred times and had it work, but now it doesn't work right. The first few times I didn't notice what happened and rebooted. It was ugly, no boot animation, and black screen from there on.
Click to expand...
Click to collapse
mine works. what are you trying to do?
sorry i have to cover the basics
after you switch r/w to r/o are you long pressing build.prop and slecting "Open in Text Editor"?
how are you saving it? do you press "save & exit" or "save changes"?
have you tired uninstalling root explorer and reinstalling it?
Root Explorer
Yup, tried that. I even bought Root Manager and used it's buidprop editor, with the same results. Maybe it's the rom I'm Running. It's Desired Inc HD 3D V5. It worked with V3 though.
I had no problems editing the build.prop file using Root Explorer on the stock 2.3.4 OTA.
Related
if i edit my build.prop with astro, on a reboot the changes are lost, the file is marked r-w, so something altering it on bootup, anybody know where the source comes from??
Download Root Explorer and use that. Trust.
tried that, it keeps getting overwritten with some king of backup.
mallard729 said:
tried that, it keeps getting overwritten with some king of backup.
Click to expand...
Click to collapse
If that's the case, then it's a problem specific to the ROM. I haven't tried it on my TP2 but it worked flawlessly on my G1.
Lemme take a look once I get a second.
why cant i find the directory /system/ ?!?! i cant find the build.prop from within windows or winmo?!
norpan111 said:
why cant i find the directory /system/ ?!?! i cant find the build.prop from within windows or winmo?!
Click to expand...
Click to collapse
Because it does not excist in winmo. It only excists in android.
I tried Root Explorer and it workers . I use latest froyo build with lower incall volume kernel .
Can somebody tell me when I delete apps in system/apps folder I delete from data.img or from system.ext2 ?
Same here, I change my build.prop file or replace it and it gets overwritten.
Using the build.prop for protected apps but can't get it to stay.
I am using the latest BLAZEN build from PPCGEEKS/Reefer.
Being an Ext2 file instead of sqsh I figure this would have worked flawless.
I'd really like to download logmein, gbahours, paypal and a few other protected apps. I can't without fixing this build.prop file....
OR
Find some way to get a working fingerprint Google has already approved.
Glad to see I'm not the only one looking into this I have the same problem in my android OS - different phone, but same custom OS. Hopefully this thread won't die - if I ever figure it out I'll be sure to post here as well
I dont know if you guys already know this.
But I just found out that you can completely hide the virtual keys completely, not moving it to the notification bar.
Here's how to do it:
1. Make sure your filesystem is r/w
2. Use root explorer, rename folder /system/board_properties to other name (i just put "z" in the end of the name)
3. Reboot!
I've test it in Urukdroid 1.1b2 and it works like charm. Buttons mode still can be used, but i prefer Button Savior. New version of Button Savior is perfect, no more bug like before.
Try it and tell me if it works!
[UPDATE]
Sibere method (if my method doesnt work) [Post #22]
1. rename or move /system/board_properties folder
2. add this to /data/local.prop:
Code:
ro.board.has_buttonbar=no
ro.board.has_soft_keys=yes
thanks sibere!
btw your kernel for uruk rocks!
Thank you, I will test that afterwards.
But which version is the latest version of button savior? And what's better in the pro version?
And can I undo it, if I rename the folder to board_properties?
Button Savior pro only enable us to change the button arrangement..
The latest version is 1.1.2
Yes, you can undo the change! Just rename it back and reboot..
Why I can't change the name? I've 2.1.08 with chulri's root and r/w filesystem and I can't rename the folder.
What can I do? Should I reinstall the SDE and root?
maybe it only works on UrukDroid because it is fully rooted..
sad to hear that
Now I put the folder to /board_propertiesx but it doesn't work. I could move the folder, and I could rename it, when it was in /.
There isn't a folder in system anymore, but the buttons are still there. Maybe because I don't have Urukdroid?
so you move the folder from /system to / ?
i think it should work..
have you reboot?
Yes, I've rebooted and put the folder from /system/ to / and I renamed it.
But I don't know, why I couldn't rename it in /system but could move it and renamed it in /?...
But is there maybe an other possibility in the local.prop? I tested ro.board.has_soft_keys=yes, but then the touchscreen doesn't work.
I'm still finding other ways to hide the virtualkeys..
Maybe this method only works in UrukDroid I guess..
thank you for trying!
But are there any other guys with stock firmware who want to try it? Maybe I'm not the only one can't hide the buttons.
But what about UrukDroid? Do my files and apps will be removed when I install Urukdroid? Is Urukdroid like the SDE with root?
during Urukdroid installation, there is an option to copy all apps from old firmware to Urukdroid..
but it is not recommended by sauron..
The installation guide can be found @ Urukdroid wiki - http://code.google.com/p/urukdroid/wiki/Installation#Step_one
I think, I will stay with the stock firmware.
But it would be great, if other people with stock firmware would test that, too.
Hi. It works with chulri's ROOT. I'm on firmware 2.3.26. First it won't work with just renaming the folder. Then I moved the folder to / but it is also still there in /system. I deleted the board_properties - folder in /system, renamed the copy in / to board_properties.bak and moved this one back to /system as a backup. After a reboot the buttons were gone. Hope this helps.
Edit: After every reboot the Archos-Widget App crashes. I think, it is looking for files in the board_properties folder and can't find them. I freezed this app with titanium-backup and now everything seems fine. Maybe it needs only to disable the archos-widget app without the need to rename the folder to get rid of the buttons.
glimmling said:
Hi. It works with chulri's ROOT. I'm on firmware 2.3.26. First it won't work with just renaming the folder. Then I moved the folder to / but it is also still there in /system. I deleted the board_properties - folder in /system, renamed the copy in / to board_properties.bak and moved this one back to /system as a backup. After a reboot the buttons were gone. Hope this helps.
Click to expand...
Click to collapse
nice..
glad to hear that its working
glimmling said:
Hi. It works with chulri's ROOT. I'm on firmware 2.3.26. First it won't work with just renaming the folder. Then I moved the folder to / but it is also still there in /system. I deleted the board_properties - folder in /system, renamed the copy in / to board_properties.bak and moved this one back to /system as a backup. After a reboot the buttons were gone. Hope this helps.
Click to expand...
Click to collapse
I tested the same, but it doesn't work.
I will reinstall the SDE and the kernel and will test it again.
I reformatted my Archos 70, put the SDE on it, but it still doesn't work.
Maybe it's because of the firmware 2.1.08?
Hey. Just recognized, that some games will work now without the softbuttons on my a70. Cut the rope and MonkeyBlast didn't run before the modification and now they do.
Sent from my A70S using Tapatalk
Anyone with Chulri's R/W root, try this:
Go into the board_properties folder, find the file that relates to your model(mine is an A101, so my file was virtualkeys.A101IT), and rename it(add .old to the end of it), and reboot. If that doesn't work, try opening the file as text and delete all the text in it, then save as the original filename(not with the .old extension). Also, make sure you haven't turned off the Soft Buttons through UrukConfig or manual edits. You have to reenable the softkeys(remove them from notification bar) to make them disappear completely with this method.
Another option is to hide them mostly--edit the right board_properties file and set their width to something really small, like 10 pixels. Then they remain usable (though the label will be cut-off), but they take up very little screen space.
Worked for me on Archos 101 Churli's R/W Root
I have the 101 with Chulri's R/W root. All I did was move the board_properties to my sd card and rebooted. Abracadabra, their gone. Renamed to board_properties.bak and put back into the system folder. Rebooted again just to make sure it stuck and it did, no soft buttons.
Since we now have the LK8 leak, and no custom Roms, yet. I've seen the "how do I disable camera sounds" question asked a few times.
I'm sure your favorite developer will incorporate this feature, like they have in the past, as they update to the new base. This is mainly for us impatient noobs
You must be rooted. Using a root explorer, navigate to /system. Select build.prop. Scroll until you find this line:
# Camera sound play enforced for SPR
ro.camera.sound.forced=1
and change to:
# Camera sound play enforced for SPR
ro.camera.sound.forced=0
If you also want to be able to toggle the sound in the camera menu, navigate to /system/csc, and select feature.xml.
Scroll to the "Camera" section, and change this line from this:
<CscFeature_Camera_ShutterSoundMenu>false</CscFeature_Camera_ShutterSoundMenu>
to this:
<CscFeature_Camera_ShutterSoundMenu>true</CscFeature_Camera_ShutterSoundMenu>
Save, exit,
Make sure permissions are set to: rw-r--r--,
and reboot.
yes happend
Man, I must be doing something wrong.
I used ES file explorer to make the changes and rebooted twice but the sound is still there and the menu doesn't show the camera option either...
I am trying my hand at this instead of the apk I found.
scoobmd said:
Man, I must be doing something wrong.
I used ES file explorer to make the changes and rebooted twice but the sound is still there and the menu doesn't show the camera option either...
I am trying my hand at this instead of the apk I found.
Click to expand...
Click to collapse
Make sure ES has root permission, and also make sure you are saving the updated file, before exiting. I'll try to do it from ES File explorer, in a little while, to see if I can make it work.
Okay, I was able to follow this procedure, with ES File Explorer, also. I just made sure all of the "root" boxes were checked in settings.
Thanks for the help.
I confirmed the setting and everything where correct after a reboot, I wonder if installing that camera app to silence the sounds did something...
scoobmd said:
Thanks for the help.
I wonder if installing that camera app to silence the sounds did something...
Click to expand...
Click to collapse
Not sure, but I do know people reported that the app from that other post, killed Spen, and lock screen sounds, too.
Using Root Explorer, when I try to tap on "build.prop" nothing happens.
There is a tiny yellow icon in the shape of a shield with a star on it on that line. What does that mean? Why won't it let me go in?
Thank You OP for the instructions. It worked.
I used RomToolbox Pro toget it done.
slthree said:
Using Root Explorer, when I try to tap on "build.prop" nothing happens.
There is a tiny yellow icon in the shape of a shield with a star on it on that line. What does that mean? Why won't it let me go in?
Thank You OP for the instructions. It worked.
I used RomToolbox Pro toget it done.
Click to expand...
Click to collapse
Thanks for the feedback, I'm glad you got it working.
Thanks it works great on MA5 also thank u much
Galaxy Note 2
Thanks a million, works perfectly on my stock rooted!!
Sent from my SPH-L900 using Tapatalk 2
Worked great for me on stock rooted with exynos abuse and ES File explorer.
Still working strong! Thanks.
twoscomplement said:
Still working strong! Thanks.
Click to expand...
Click to collapse
Glad I could help.
Ive been trying to edit hw_config.sh file to remove the led backlight on my arc. Im using the latest CM10 fxp150.
However every time i try editing the file using root explorer or es file explorer they create a backup-file (as they should), but the original file ends up being empty of script.
Does anyone know what im missing?
monty1234 said:
Ive been trying to edit hw_config.sh file to remove the led backlight on my arc. Im using the latest CM10 fxp150.
However every time i try editing the file using root explorer or es file explorer they create a backup-file (as they should), but the original file ends up being empty of script.
Does anyone know what im missing?
Click to expand...
Click to collapse
Navigate to Sys/Class/Leds/Button-Backlight and Change brightness and max_current to 1
. Save.
Now go to System/etc and open hw_config. Now Scroll down a bit and change Max_current to 1, too. Reboot.
If Backlights are not Blinking it Works
I just flashed developer preview 4 and rooted but I cannot get the build.prop edited. I've tried multiple apps but always says error saving. Had anyone gotten the build.prop edited?
lawtalking said:
I just flashed developer preview 4 and rooted but I cannot get the build.prop edited. I've tried multiple apps but always says error saving. Had anyone gotten the build.prop edited?
Click to expand...
Click to collapse
I have successfully edited the build prop by using root explorer. Make sure you are rooted and allow super su to use root explorer.
You will will need to hold down on build.prop to highlight it, then go to menu and select, open in text editor.
lucky_strike33 said:
I have successfully edited the build prop by using root explorer. Make sure you are rooted and allow super su to use root explorer.
You will will need to hold down on build.prop to highlight it, then go to menu and select, open in text editor.
Click to expand...
Click to collapse
I am rooted and I did give permission to root explorer. I am able to mount the other files and folders as read write but it will not let me Mount the system as read write. I've tried multiple apps it all says error saving.
lawtalking said:
I am rooted and I did give permission to root explorer. I am able to mount the other files and folders as read write but it will not let me Mount the system as read write. I've tried multiple apps it all says error saving.
Click to expand...
Click to collapse
What file explorer are you using. Fx works fine.
toknitup420 said:
What file explorer are you using. Fx works fine.
Click to expand...
Click to collapse
I've tried multiple. Its not the file explorer. I've tried re flashing the factory image but still will not let me edit any system folders or files. I think that maybe it is systemless root. Not sure how I got systemless root or if it is possible to get regular root. Is there a setting is Supersu?
lawtalking said:
I've tried multiple. Its not the file explorer. I've tried re flashing the factory image but still will not let me edit any system folders or files. I think that maybe it is systemless root. Not sure how I got systemless root or if it is possible to get regular root. Is there a setting is Supersu?
Click to expand...
Click to collapse
You may have a SUPER.img - i just learned about this myself - its a combined image containing /system - /vendor & /Product - it looks like it is similar to Systemless root or system as root... idk they are weird but i do think its possible to modify build.rpop, but it may require a PC.... Im looking for a way to edit build.prop myself and learning all this now.