Database Users

No default.prop file in root explorer to change my tw screen layout

Hi, im rooted with 2.3.4 firmware, i tried to use root explorer to edit the default.prop file so i could change the layout of my touchwiz homescreen but its not in the system folder where it should be?? I know it was there yesterday cos i done the procedure and changed the layout but i updated to 2.3.4 firmware tonight and rooted again, ive gone to do the default.prop procedure but its not there in the system folder?? Does anyone have any ideas how i could do it please??
Many thanks
Sent from my GT-I9100 using XDA Premium App

Yes, in the new ROM there is no default file to change this. I´m also looking for a solution.

Changing boot animation on stock rom

I made my own boot animation, but cannot seem to find where to put it, and I can't get access to /data/cust/media. Has anyone successfully changed their boot animation? I'm running U8800-51 stock rom with Android 2.2.2. Also any help with installing custom roms/a higher Android version with 3g would be appreciated. Thank you!

Uhm its stored as bootanimation.zip & bootanimationex.zip in /curst/hw/default/media/ but ive tryed serval times to make it change my self but something is blocking my permissions to do it... anyone please help us

arnemw said:
Uhm its stored as bootanimation.zip & bootanimationex.zip in /curst/hw/default/media/ but ive tryed serval times to make it change my self but something is blocking my permissions to do it... anyone please help us
Click to expand...
Click to collapse
/cust is a spool. It's a virtual folder created from cust.img and cannot be modified without modifying cust.img. Check the marketplace for an application that does just that. I believe that there are several.

REQ : Stock 4.3 build.prop

Hi,
Would someone be kind enough to send me his stock 4.3 build.prop for Nexus4 because I have modified it without backup (hey I know that's not smart... ) and I cannot use the OTA for JWR66Y because build.prop file does not pass the binary verification.
Thanks !

Flav106 said:
Hi,
Would someone be kind enough to send me his stock 4.3 build.prop for Nexus4 because I have modified it without backup (hey I know that's not smart... ) and I cannot use the OTA for JWR66Y because build.prop file does not pass the binary verification.
Thanks !
Click to expand...
Click to collapse
Just to remind, remember to delete the TXT extension when you put it back in because if i dont add an extention I cant upload it. I extracted it from Cataclysm, don't worry, it doesnt matter. Its still a JWR based build.prop.

KiD3991 said:
Just to remind, remember to delete the TXT extension when you put it back in because if i dont add an extention I cant upload it. I extracted it from Cataclysm, don't worry, it doesnt matter. Its still a JWR based build.prop.
Click to expand...
Click to collapse
Make sure it doesn't have any names of custom roms or anything like that.
Sent from my Nexus 4 using Tapatalk 4

Thanks a lot !
But I can see your are already in JWR66Y. I am not sure this will work for the OTA...
I think it would be better to have a JWR66V version don't you think ?

AFAIK, it doesnt have and even if it does it doesnt affect the ROM.
Because any names in the build.prop is just stated in the About in the phone. I trolled my classmates for having Beta android 4.4

Well, it worked for the build.prop verification, but i have some errors ...
It passed the patching of system files but I have an error set_perm : some changes failed.Installation aborted.
The phone rebooted properly.
So now I don't know what version i'm in with the modified build.prop !
Do you know how to check my version other than checking the build.prop file ?

Finally I'v been able to update with this fix :
http://forum.xda-developers.com/showpost.php?p=44940220&postcount=556
Status 7 error was due to my root.
Thanks.

KiD3991 said:
Just to remind, remember to delete the TXT extension when you put it back in because if i dont add an extention I cant upload it. I extracted it from Cataclysm, don't worry, it doesnt matter. Its still a JWR based build.prop.
Click to expand...
Click to collapse
Yeah this didn't work for me. I verified that the build.prop matches what you linked, but I'm still getting the build.prop error. So had any of you also flashed different radios or the LTE enabler zip that floats around the All LTE Discussion board? I just don't understand why I'm still getting that error if it worked for you.

Pokley said:
Yeah this didn't work for me. I verified that the build.prop matches what you linked, but I'm still getting the build.prop error. So had any of you also flashed different radios or the LTE enabler zip that floats around the All LTE Discussion board? I just don't understand why I'm still getting that error if it worked for you.
Click to expand...
Click to collapse
I'm not using any LTE. My radio is the pure 4.3 radio.
It could be that the build.prop you used is edited by computer. (one that might effect)

[Q] How to change build.prop

I want to change some proprieties of the build.prop
(ro.secure=0==>1
ro.debuggable=1==>0
persist.service.adb.enable=1==>0)
But I don't know to change that in Rom 4.2 onwards (I could change it in Kayant's 4.1.1 AOKP Rom by changing /system/bootmenu/config/default.prop but this method don't work on another CM android 4.2 Rom)
How to change the build.prop (or the corresponding values)?
(Coz the app I want to use is checking those values, and refuses to start if it detects ro.secure=0 or ro.debuggable=1 or persist.service.adb.enable=1)
(I want to move to a new Rom but I have to solve this problem first)

dicksonlok said:
I want to change some proprieties of the build.prop
(ro.secure=0==>1
ro.debuggable=1==>0
persist.service.adb.enable=1==>0)
But I don't know to change that in Rom 4.2 onwards (I could change it in Kayant's 4.1.1 AOKP Rom by changing /system/bootmenu/config/default.prop but this method don't work on another CM android 4.2 Rom)
How to change the build.prop (or the corresponding values)?
(Coz the app I want to use is checking those values, and refuses to start if it detects ro.secure=0 or ro.debuggable=1 or persist.service.adb.enable=1)
(I want to move to a new Rom but I have to solve this problem first)
Click to expand...
Click to collapse
Use Root Explorer and change it, easiest way

sorry for the typo, I intended to say default.prop
edi194 said:
Use Root Explorer and change it, easiest way
Click to expand...
Click to collapse
Yeah I get your meaning, but I typed "default.prop" as "build.prop", which have huge difference in terms of how to change its value, sorry for the muddled I caused.
I think I'll start a new post, as I can't edit the title..., and to be more clear to other who read it. Please also answer in the new post
P.S. please wait for me to open the new post at least five minute as I still have the five-minute post restriction lol

Can not modify gps.conf for a better performance

Hello everybody.
I have a problem about my Redmi Note 7.I want to ask to you about it, if another one had the same problem with me.
My phone is unlocked and rooted (Magisk).And i use original MIUI 11 version with oem kernel.
-The problem is, i want to modify gps.conf file to get a better gps performance.I know to tweak it, i had been doing that on my old phone also.And the problem starts here.I use "es file explorer" by root rights and can modify the file and save it.Everyting seems okay.But when i restart the phone and check the file, i see that the phone restores that file (gps.conf) to its original oem state.So although i can modify and save it by a root file manager after a restart it turns the original state.I can not prevent it.Is there any way to fix that situation?
Thank you.

Test this module from magisk download section. And maybe modify it with ur gps.conf

joke19 said:
Test this module from magisk download section. And maybe modify it with ur gps.conf
Click to expand...
Click to collapse
Thank you.it works well.:good:

stranger_88 said:
Thank you.it works well.:good:
Click to expand...
Click to collapse
?