Database Info

Help :/ Bruce JB Rom

Hy i can't post in developers forum and now i open new topic sorry admins but i can't get sweep2wake working :/ i try all even "daddyspud" made video for meee and i folow this video exacly how he did and still nothing :/ then i download temcore kernel install it and still same can't run sweep2wake :/ does anyone know what is wrong tny guys !!!

can be enabled in system/etc/init.d/01bruce) script adapted from tamcore's.

i allready chance in bruce01 sweep2wake to 1 save it then bun it in scriptmeneger and in therminal emulator :/ but still don't work :/

? help plz :/

XporteR21 said:
i allready chance in bruce01 sweep2wake to 1 save it then bun it in scriptmeneger and in therminal emulator :/ but still don't work :/
Click to expand...
Click to collapse
Mount the system in RW mode -> change sweep2wake to 1 -> Restart.
I was facing the same issue and I tried the RW mode - it worked for me.

How to run it in recowery mod and then change the value ?

XporteR21 said:
How to run it in recowery mod and then change the value ?
Click to expand...
Click to collapse
Use Root Explorer or ES File Explorer.
1.Make System partition writable in the setting.
2.Then navigate to /system/etc/init.d, open the 01bruce file and change value for sweep2wake to 1.
3. After this, you will also need to change to the permission of the file to rwx rx rx.
4.Reboot.

[Q] Build.prop tweaks don't stick, reset when I reboot

Hi,
I'm pretty sure this problem could be common to all rooted devices, so I'm posting it in the general Q&A.
Basically, I would like to experiment with some build.prop tweaks I found around other XDA topics. I'm sure all of you know about the general tweaking of the said file, so I won't get into too much detail about it.
However, the changes just don't stick. They reset to default every time I reboot, as if the build.prop file never changed. So, how do I make them stick?
Phone details:
Phone: Xperia X8
ROM: FroyoPro v2.5
Kernel: Stock (can't unlock the bootloader, unfortunately)

Are you saving before exiting?

XperienceD said:
Are you saving before exiting?
Click to expand...
Click to collapse
Of course! I even double-check if the changes were still there by opening the modified build.prop after the work is done. For the changes I used Root Browser Lite with the Text Editor pre-installed inside. This method does work well, as I used it to modify hw_config parameters related to governors a couple of weeks back.
I've read somewhere that sometimes changes aren't possible if the kernel is stock. Could that be the case here?
If not, are there any other methods I could use to modify build.prop?

xWhiskey said:
Of course! I even double-check if the changes were still there by opening the modified build.prop after the work is done. For the changes I used Root Browser Lite with the Text Editor pre-installed inside. This method does work well, as I used it to modify hw_config parameters related to governors a couple of weeks back.
I've read somewhere that sometimes changes aren't possible if the kernel is stock. Could that be the case here?
If not, are there any other methods I could use to modify build.prop?
Click to expand...
Click to collapse
A quick google caused me to find this thread and I too am having the same problem. I'm currently trying to edit my build.prop to unlock games which say they are incompatible. I'm using ES File Explorer and the built in text editor to edit and save the .prop file, I check if the changes have saved before rebooting my phone but when I turn it back on it has reverted back to stock.

sircrisp said:
A quick google caused me to find this thread and I too am having the same problem. I'm currently trying to edit my build.prop to unlock games which say they are incompatible. I'm using ES File Explorer and the built in text editor to edit and save the .prop file, I check if the changes have saved before rebooting my phone but when I turn it back on it has reverted back to stock.
Click to expand...
Click to collapse
Check if your ROM has a dual build.prop file. If one exists in system/bin, you ought to edit that one for the change to stick. This solved the issue for me, and might solve it for you.
If it isn't there, try using search, and if you find another one somewhere else then try editing that one. A simple matter, but apparently easily missed

xWhiskey said:
Check if your ROM has a dual build.prop file. If one exists in system/bin, you ought to edit that one for the change to stick. This solved the issue for me, and might solve it for you.
If it isn't there, try using search, and if you find another one somewhere else then try editing that one. A simple matter, but apparently easily missed
Click to expand...
Click to collapse
I'm here to wake this thread up, because I'm having this same issue and I can't seem to find any duplicate build.prop file...
Anyone having a good suggestion for me please give it, all assistance is welcome.
Android version 4.4.4
Galaxy Note Edge
Sent from my SM-N915P using Tapatalk 2

me too have the same problem , please some dev or expert help with these problem

You install root explorer and mount as r/w and copy the build.prop into your sd card (the unmoded one) and connect your phone to your pc and turn on usb copy file transfer or something like that. In your pc go into your sd and open your copied build.prop with notepad and mod it as you like. After that go into your root explorer and replace it with your original build.prop. Try on not bricking your phone bcz i bricked mine like that when i put a lot mods on it haha, make a cwm backup or if you know how to unbrick it in every case Hope i helped
Be sure its mounted as r/w otherwise you will not be able to do anything to system files.
Use the original root explorer or Andro Zip is recommeded by me
Sent from my GT-S5830i using XDA Free mobile app

Are you setting the file permissions correctly as rw-r--r-- ??

[/COLOR]
flexton said:
You install root explorer and mount as r/w and copy the build.prop into your sd card (the unmoded one) and connect your phone to your pc and turn on usb copy file transfer or something like that. In your pc go into your sd and open your copied build.prop with notepad and mod it as you like. After that go into your root explorer and replace it with your original build.prop. Try on not bricking your phone bcz i bricked mine like that when i put a lot mods on it haha, make a cwm backup or if you know how to unbrick it in every case Hope i helped
Be sure its mounted as r/w otherwise you will not be able to do anything to system files.
Use the original root explorer or Andro Zip is recommeded by me
Sent from my GT-S5830i using XDA Free mobile app
Click to expand...
Click to collapse
samsungrockz said:
Are you setting the file permissions correctly as rw-r--r-- ??
Click to expand...
Click to collapse
thank u for answering but sorry guys to say this , it's not the way of editing it , or the permission , when i make changes they are saved correctly and the device apply the changes in the start of the first boot after these changes are made , but during the boot (after applying the changes) the device restore the stock build.prop , so when the device finishes boot up the changes are applyed but the build.prop (i cheked it) is back to stock , this mean another boot & the changes are gone , :crying: :crying: no matter how many times or changes u do they are applyed only for the first boot after they are made

Maybe it has some stock security feed, try to go to custom roms i dont now what else can you do
Sent from my GT-S5830i using XDA Free mobile app

flexton said:
Maybe it has some stock security feed, try to go to custom roms i dont now what else can you do
Sent from my GT-S5830i using XDA Free mobile app
Click to expand...
Click to collapse
it my first ported rom -porting by replacing files ,not expert work- and i'm having this problem

Kico.MMK said:
it my first ported rom -porting by replacing files ,not expert work- and i'm having this problem
Click to expand...
Click to collapse
Try finding your device on xda and look for a custom rom that someone more expirienced than you if it doesnt work i dont know what will
Sent from my GT-S5830i using XDA Free mobile app

flexton said:
Try finding your device on xda and look for a custom rom that someone more expirienced than you if it doesnt work i dont know what will
Sent from my GT-S5830i using XDA Free mobile app
Click to expand...
Click to collapse
thanks for the advice , actually i did that but you know there is always something to be fixed :silly:

I have the same issue with my Vodafone Smart Ultra 6. I have root and system has read write access according to ES File Explorer. But any app that has root privileges, writes just fine without errors. However, if I close the app and load it again, or reboot, any changes are lost. So if I remove a system app using a root uninstaller it will say the app has been uninstalled. But it's still there. Drives me insane.

Exactly the same on the Smart Ultra 6.
Was hard enough to get it rooted but seems any changes to the system partition/file system just don't stick. Short of putting a custom rom on it I'm stuck for ideas.
I'd love to know what causes this behaviour.

Any updates here? I just started running into this after updating to the 7.1.1 January factory image on my 5x. The weird thing is when i reboot in TWRP it all looks fine but when I look at my system directory from Android the boot-from-recovery.p is still there and my build.prop changes aren't...push TWRP again, boot to recovery read build.prop and it's my edited version. wtf?

I have found a solution which works in my case.
Edit build prop using any root explorer and save it.
Now once again edit the file with different root explorer app like amaze or es explorer with some comment line like
#comment
and save it.
Now it should prevent the build prop from resetting after a reboot.

I have the same problem: after reboot all the changes are gone....
ashd63 said:
I have found a solution which works in my case.
Edit build prop using any root explorer and save it.
Now once again edit the file with different root explorer app like amaze or es explorer with some comment line like
#comment
and save it.
Now it should prevent the build prop from resetting after a reboot.
Click to expand...
Click to collapse
It's not working for me ☹
---------- Post added at 09:43 AM ---------- Previous post was at 09:30 AM ----------
Is it normal that my build.prop has the permissions -rw------ ?
This could be the problem.

ullie4404 said:
I have the same problem: after reboot all the changes are gone....
It's not working for me ☹
---------- Post added at 09:43 AM ---------- Previous post was at 09:30 AM ----------
Is it normal that my build.prop has the permissions -rw------ ?
This could be the problem.
Click to expand...
Click to collapse
Did you ever find the solution to this? I'm having the same problem..all changes reset with every reboot and the file's permission is like -rw-----

[Q] how to enable system write

I installed several kernels with system write protection disabled but every time i try to edit an xml file i cant save it i cant copy files to system its just not enabled i try to enable it through es file explorer but it says everythings already r/w i tried fixing permissions in twrp i have a kernel installed with write protection disabled but still no luck any help would be greatly appreciated thank you

power950 said:
I installed several kernels with system write protection disabled but every time i try to edit an xml file i cant save it i cant copy files to system its just not enabled i try to enable it through es file explorer but it says everythings already r/w i tried fixing permissions in twrp i have a kernel installed with write protection disabled but still no luck any help would be greatly appreciated thank you
Click to expand...
Click to collapse
Need more information.. What base are you on? 1.55.605.2? Which kernel did you flash? What mod exactly are you trying to do?

nicholi2789 said:
Need more information.. What base are you on? 1.55.605.2? Which kernel did you flash? What mod exactly are you trying to do?
Click to expand...
Click to collapse
clean rom 1.1 http://forum.xda-developers.com/showthread.php?t=2732877
checkm8 team code craft says it disables write protection http://forum.xda-developers.com/showthread.php?t=2716686
as for the base how do i check i was on the latest update when i s offed and rooted and flashed everything around may 5th i think it was the latest base but how do i check i can let you know? im just trying to edit my default.xml in system/customize/ACC/ and i cant i just wanna write to system copy files to the root of the system etc

power950 said:
clean rom 1.1 http://forum.xda-developers.com/showthread.php?t=2732877
checkm8 team code craft says it disables write protection http://forum.xda-developers.com/showthread.php?t=2716686
as for the base how do i check i was on the latest update when i s offed and rooted and flashed everything around may 5th i think it was the latest base but how do i check i can let you know? im just trying to edit my default.xml in system/customize/ACC/ and i cant i just wanna write to system copy files to the root of the system etc
Click to expand...
Click to collapse
Yes you can check by going into settings>aabout phone>software information>software number. If your on Cleanrom v1.1 it will be 1.55.605.2 which is the latest base. What mod are you trying to do by editing your default . XML? There are a lot of things you can tweak in there.
Also, Cleanrom v1.1 has system r/w enabled by default. So you didn't need to flash that kernel to have it.
"Pre Rooted with SuperSU and Busybox pre-installed
Writeable /system partition
Unsecured kernel with ADB remount capabilities"
My advice would be to re-flash the rom, or restore a nandroid backup to get the roms stock kernel back. You could just dirty flash the rom and only wipe cache and davlik. You should be fine.
But once again, what mod are you trying to do in your default.xml? It may be I can help you sort it out, or at least tell you why it's not working.

nicholi2789 said:
Yes you can check by going into settings>aabout phone>software information>software number. If your on Cleanrom v1.1 it will be 1.55.605.2 which is the latest base. What mod are you trying to do by editing your default . XML? There are a lot of things you can tweak in there.
Also, Cleanrom v1.1 has system r/w enabled by default. So you didn't need to flash that kernel to have it.
"Pre Rooted with SuperSU and Busybox pre-installed
Writeable /system partition
Unsecured kernel with ADB remount capabilities"
My advice would be to re-flash the rom, or restore a nandroid backup to get the roms stock kernel back. You could just dirty flash the rom and only wipe cache and davlik. You should be fine.
But once again, what mod are you trying to do in your default.xml? It may be I can help you sort it out, or at least tell you why it's not working.
Click to expand...
Click to collapse
i would just like to write to system for future purposes for the mean time i used adb to pull the default xml then i modified the file on my pc to enable harman kardon and music channel then went to recovery mounted system and pushed it back its just a pain seeing i can't write to system when i want to yes it says 1.55.605.2 so i should be able to write to system and you suggest a fresh install? or should i just pull the kernel image out of the rom zip and flash through fastboot?

CleanROM has this capability without any 3rd party kernels or other modifications. I use ES File Explorer on a clean install of CleanROM 1.1 to write to the /system partition. You do need to enable R/W permission in the ES File Explorer app by clicking the upper left icon, going to Tools, enabling the toggle for Root Explorer, clicking on the words Root Explorer, clicking on Mount R/W, and enabling RW permission on whatever directory you want to.

shortstuff_mt said:
CleanROM has this capability without any 3rd party kernels or other modifications. I use ES File Explorer on a clean install of CleanROM 1.1 to write to the /system partition. You do need to enable R/W permission in the ES File Explorer app by clicking the upper left icon, going to Tools, enabling the toggle for Root Explorer, clicking on the words Root Explorer, clicking on Mount R/W, and enabling RW permission on whatever directory you want to.
Click to expand...
Click to collapse
was trying to avoid i clean install but i'll give it a go i did enable r/w with es file explorer and made sure all the bubbles were checked with still no luck ill do a fresh install without flashing any other files but clean rom and see what happens i'll let you guys know after i do it thanks

okay so I did a fresh install i factory reset x3 wiped data i know this wasn't necessary but i typed yes and wiped data x3 i went into advanced wipe and and checked every box except usb otg after backing up sd cards and then swiped to format x3 i then powered off the phone ejected my sd card put clean rom 1.1 on it and flashed it with no other files rebooted my phone went through the setup installed es file explorer enebled root access clicked on root access clicked on mount r/w and made sure everything was bubbled in on the right side mount r/w and i still cannot right to system im ready to give up

power950 said:
okay so I did a fresh install i factory reset x3 wiped data i know this wasn't necessary but i typed yes and wiped data x3 i went into advanced wipe and and checked every box except usb otg after backing up sd cards and then swiped to format x3 i then powered off the phone ejected my sd card put clean rom 1.1 on it and flashed it with no other files rebooted my phone went through the setup installed es file explorer enebled root access clicked on root access clicked on mount r/w and made sure everything was bubbled in on the right side mount r/w and i still cannot right to system im ready to give up
Click to expand...
Click to collapse
Why not make a copy of the files you want to edit... fix them up how you like.. then copy them back into place using file explorer function of TWRP (make sure you mount system).... OR put them in a flashable zip template and flash them. The changes will stick. You are likely trying to change files in use.

doh
dottat said:
Why not make a copy of the files you want to edit... fix them up how you like.. then copy them back into place using file explorer function of TWRP (make sure you mount system).... OR put them in a flashable zip template and flash them. The changes will stick. You are likely trying to change files in use.
Click to expand...
Click to collapse
oh lol your'e right i just copied a file over from my sd to the system to test it wow I should of known that thanks so much this issue is solved I'm disappointed in myself gotta give myself 10 minutes time out now thanks tho

Ram issue fix

http://forum.xda-developers.com/showpost.php?p=61260005&postcount=80
Above is the ram fix for the s6, I am pretty new to this kind of stuff and I read some verizon users were getting bootloops from editing the build.prop . If it is possible can anyone make a guide through it or post their build.prop if successful?

NumberTwoinQQ said:
http://forum.xda-developers.com/showpost.php?p=61260005&postcount=80
Above is the ram fix for the s6, I am pretty new to this kind of stuff and I read some verizon users were getting bootloops from editing the build.prop . If it is possible can anyone make a guide through it or post their build.prop if successful?
Click to expand...
Click to collapse
I gave it a whirl. No bootloop here. I'm on OC3 firmware running Ricks rom.

Tulsadiver said:
I gave it a whirl. No bootloop here. I'm on OC3 firmware running Ricks rom.
Click to expand...
Click to collapse
so did you have to do anything after editing the build.prop? Like "after editing make sure permissions are 0644 on it or you will boot loop."
I do not know where to find permissions
EDIT: I just changed these and it worked:
ro.config.dha_cached_max=12
ro.config.dha_empty_max=36
ro.config.dha_th_rate=2.3
ro.config.dha_lmk_scale=0.545
ro.config.sdha_apps_bg_max=70
ro.config.sdha_apps_bg_min=8
ro.config.oomminfree_high=7628,9768,11909,14515,16655,20469

NumberTwoinQQ said:
so did you have to do anything after editing the build.prop? Like "after editing make sure permissions are 0644 on it or you will boot loop."
I do not know where to find permissions
Click to expand...
Click to collapse
Most root explorers will show and allow permissions to be changed.
I actually edited mine via an app but I've done it through my root explorer text editor as well. Probably need to copy it off root drive. Edit it, then copy back. Some people say to copy it to the root folder first. Set permissions, them copy/move it to the system folder to overwrite it. Then, reboot.

I left this line out. Should I have?
ro.config.oomminfree_high=7628,9768,11909,14515,16 655,20469
It was on on CleanROM to begin with.

musicfreak190 said:
I left this line out. Should I have?
ro.config.oomminfree_high=7628,9768,11909,14515,16 655,20469
It was on on CleanROM to begin with.
Click to expand...
Click to collapse
According to the post, that line should have been inserted.

so i had quite an issue - my first go at it was done by copying build.prop via adb to my computer, editing and pushing back - after that, i nearly bricked the device. had to roll back to stock rom using odin .. not fun. now i decided to try again (cause i'm a masochist apparently) but i just edited the file using ES - no problems, no boot loops.. all is well for now - hopefully will see fewer apps closing for no reason. hooray.

i can say downloading the build prop that was posted here and replacing mine with it will brick a phone

Help with read-only and /vendor

Hi!
I've been trying to boost my volume with changing values in mixer_volumes_FRD_ce with both solid explorer and with root browser. But I always get the same problem and the problem is that it says I can't do it in read-only mode but when I've booted into twrp I've deselected the mount system as read only. Another problem is that I can't change values in the under mixer path because it says I can't do it under /vendor... I'll gladly take any help or suggestions ... Stock rom btw

I don't know about the last part but if you are using some kind of system explorer you must enable r w (read write) in it.

Indigoeyes said:
Hi!
I've been trying to boost my volume with changing values in mixer_volumes_FRD_ce with both solid explorer and with root browser. But I always get the same problem and the problem is that it says I can't do it in read-only mode but when I've booted into twrp I've deselected the mount system as read only. Another problem is that I can't change values in the under mixer path because it says I can't do it under /vendor... I'll gladly take any help or suggestions ... Stock rom btw
Click to expand...
Click to collapse
Just use dolby bro