build.prop deleted *HELP* - Gen8, Gen9, Gen10 Q&A, Help & Troubleshooting

"build.prop editor" app has overwritten my /system/build.prop, and now there is just a single line in it, the one which i wanted to add to my existing build.prop. instead "build.prop editor" replaced my entire build.prop. lesson learnt!
my device (Archos 70b Cobalt) is not booting up completely. i can get to the stock recovery.. i need the stock build.prop, and i don't have a backup!! can anyone post theirs please urgent? thx

can i push build.prop to /system via recovery? i want to know how to create update.zip (containing /system/build.prop) which i can push via stock recovery.. or any other alternative methods please. thx

Related

Edit settings.db and replacing into file system

Hello guys
I need your help, i'm working on a mod and a friend said me to modify the file: settings.db located in data/data/com.android.providers.settings/databases/settings.db
I only have to change "1" to "0" in the "secure" tab
for this I used Sql Lite browser for windows 7.
So i did it and saved the database, and then with root explorer replaced with the original settings.db but ....
I entered in a boot loop, why ?
I know for sure the "0" is a secure value, because used in a stock old rom
Why bootloop so? Have I to changed permissions to file?
Can please help me to do it without a new bootloop?
Thanks
hello
please i need to know if to change the permissions like that of original file prevent me to enter in a boot loop.
Noone have never edited settings.db file and replaced it?
If i am in wrong section, please, move the thread in the correct one.
I've done it before to modify wifi timeout. Here's the instructions I used:
http://forum.xda-developers.com/showthread.php?t=774507
polobunny said:
I've done it before to modify wifi timeout. Here's the instructions I used:
http://forum.xda-developers.com/showthread.php?t=774507
Click to expand...
Click to collapse
Did you change file permissions?
maRRRco89 said:
hello
please i need to know if to change the permissions like that of original file prevent me to enter in a boot loop.
Noone have never edited settings.db file and replaced it?
If i am in wrong section, please, move the thread in the correct one.
Click to expand...
Click to collapse
I bet you replaced the settings.db file with the edited version using ADB? If so you likely stamped the file with shell as the owner... This might have been the problem if the original file had different permissions / owner.
polobunny said:
I've done it before to modify wifi timeout. Here's the instructions I used:
http://forum.xda-developers.com/showthread.php?t=774507
Click to expand...
Click to collapse
THX
I have to crack the password for 9650108725

[Q] How to edit build.prop with flashable zip?

Hello
I want to ask, how to edit build.prop with the flashable zip?
I think it's complicated to do manual edit in build.prop
I hope there is someone that can teach me the method step by step
Thanks before ^^
Do you want to edit build.prop file in a rom of zip format
If yes then
Extract the zip first
Go to system/build.prop
Long press on it in
A dialogue box will apperar select open in text editor .
Or if you want to edit build.prop of ur current rom then
Use root explorer.
PM me if u need help
Sent from MOON......
In case someone comes to this thread looking for an answer, check out dynamic automated build.prop editing.

[Q] Bad build.prop edit

Hi guys, before I start I'll say that I have searched all over the internet and here on the forums and I couldn't find my particular issue. Well the thing is that I edited the line in my build.prop "ro.build.version.codename=REL" to "ro.build.version.codename=L" so I could get the material design on the Google Now Launcher pulled from a Android L build here's the thread I got that app: http://forum.xda-developers.com/android/apps-games/app-android-lollipop-apps-launcher-apps-t2912905
I did that and now my device will boot up normally then I will reboot by itself then show the boot animation then repeat the same process again and again until I force the phone to recovery or fastboot.
By the way my device is the LG Optimus G (E970) running GEE 3 ROM 1.2 and TRWP 2.6.3.0 and I have a backup of the original build.prop on my PC. I don't want to lose my data and apps since I forgot to make a backup (silly me).
I would like to know if there is a way to push the build.prop file on my PC to my phone so I could just replace it, or create a flashable zip.
Please help me, and thanks in advance.
Nevermind. I managed to push the original build.prop file to /system set the correct permissions and now my phone is working again.
Admin feel free to delete or close this thread.
question
AntonyOrtega said:
Nevermind. I managed to push the original build.prop file to /system set the correct permissions and now my phone is working again.
Admin feel free to delete or close this thread.
Click to expand...
Click to collapse
how were you able to do it when you couldnt get past booting.

Tethering[mod] "build prop edit"vs985

hello fellow xda junkies!
HERE IS A SIMPLE WAY TO GET DATA TETHERING THROUGH BUILD.PROP EDIT
NOTE:MESSING WITH BUILD.PROP COULD MESS YOUR PHONE UP BE CAREFUL
Step 1.) download a text editor.i suggest 920 text editor.
Step 2.) you will also need an root explorer so download that also.
Step 3).open up your root explorer and navigate to system/build.prop. and copy that file to another directory. i.e example sdcard/download.then rename
original build.prop file to build.prop.bak
Step 4).open up your text editor and navigate to the directory where you copied the build.prop file
Step 5.)look for this line [they are both close to the end of the build.prop file] "net.tethering.nonprovisioning=true" [once you find it change the true
to false] so it reads "net.tethering.nonprovisioning=false" NOTEDO NOT TYPE THE QUOTATION MARKS!!!
Step 6.) " look for line "persist.data.tethering_oc=1" change the variable 1 to 0 so it reads "persist.data.tethering_oc=0
Step 7.) move the build.prop file that you copied and edited from location you placed it in to its rightful spot in system/.change permissions to rw--r--r
reboot phone and your good to go!works on my vs985 LIKE A CHAMP.
deathsquad737 said:
hello fellow xda junkies!
HERE IS A SIMPLE WAY TO GET DATA TETHERING THROUGH BUILD.PROP EDIT
NOTE:MESSING WITH BUILD.PROP COULD MESS YOUR PHONE UP BE CAREFUL
Step 1.) download a text editor.i suggest 920 text editor.
Step 2.) you will also need an root explorer so download that also.
Step 3).open up your root explorer and navigate to system/build.prop. and copy that file to another directory. i.e example sdcard/download.then rename
original build.prop file to build.prop.bak
Step 4).open up your text editor and navigate to the directory where you copied the build.prop file
Step 5.)look for this line [they are both close to the end of the build.prop file] "net.tethering.nonprovisioning=true" [once you find it change the true
to false] so it reads "net.tethering.nonprovisioning=false" NOTEDO NOT TYPE THE QUOTATION MARKS!!!
Step 6.) " look for line "persist.data.tethering_oc=1" change the variable 1 to 0 so it reads "persist.data.tethering_oc=0
Step 7.) move the build.prop file that you copied and edited from location you placed it in to its rightful spot in system/.change permissions to rw--r--r
reboot phone and your good to go!works on my vs985 LIKE A CHAMP.
Click to expand...
Click to collapse
You know there is already a flash for this and an apk.
Yes i do know this but some like to do it on there own.but hey nice to meet ya!
deathsquad737 said:
Yes i do know this but some like to do it on there own.but hey nice to meet ya!
Click to expand...
Click to collapse
Just checking.
I'm a tinkerer also which is how I figured out the thermal throttling.
Nice to met you.
tech_head said:
Just checking.
I'm a tinkerer also which is how I figured out the thermal throttling.
Nice to met you.
Click to expand...
Click to collapse
Thermal daemon mitigation?is that what you are referring too?
A.L.B/E.B.B
deathsquad737 said:
Thermal daemon mitigation?is that what you are referring too?
A.L.B/E.B.B
Click to expand...
Click to collapse
Actually not.
Instead of trying to stop the thermal mitigation from working I did just the opposite, I changed the parameters on how it operates.
The file /system/etc/thermal-engine-8974.conf.
This file controls what happens to cpu speed at various temperatures.
That is what you tweak and it just works.
I also used ROM Toolbox to change the governor.
tech_head said:
Actually not.
Instead of trying to stop the thermal mitigation from working I did just the opposite, I changed the parameters on how it operates.
The file /system/etc/thermal-engine-8974.conf.
This file controls what happens to cpu speed at various temperatures.
That is what you tweak and it just works.
I also used ROM Toolbox to change the governor.
Click to expand...
Click to collapse
Wow that's heavy I don't know if I have a high enough pay grade to do that lol
A.L.B/E.B.B
deathsquad737 said:
Wow that's heavy I don't know if I have a high enough pay grade to do that lol
A.L.B/E.B.B
Click to expand...
Click to collapse
I can always get you a copy of the file.
tech_head said:
I can always get you a copy of the file.
Click to expand...
Click to collapse
Yes please I pm you
A.L.B/E.B.B
Thank you but...
First of all, thanks for the post. Although I appreciate the helpful post, my phone is now stuck in boot loop . I hate to be the one to open up an old thread but I'm freaking out at the moment due to brick fever :crying: My current setup was a rooted LG G3 VS98512b. My goal was simple, I didn't want to do anything crazy, I just wanted to enable wifi tether now I'm afraid I've lost everything... Is there a way I can get back into the storage of my phone and delete the modified build.prop, remove the ".bak" from the original and be back to the good life? Any assistance is greatly appreciated, this seemed like such a simple modification that led to such a big headache.
It sounds like you might have used an editor on your build.prop that could not handle the file size, resulting in your editted build.prop being truncated. Otherwise, maybe your permissions were left wrong. Either of these will cause your phone to bootloop.
Sent from my VS985 4G using Tapatalk
trent999 said:
It sounds like you might have used an editor on your build.prop that could not handle the file size, resulting in your editted build.prop being truncated. Otherwise, maybe your permissions were left wrong. Either of these will cause your phone to bootloop.
Sent from my VS985 4G using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply. I used the editor recommended in the tutorial, 920 text editor. I followed the instructions word for word, I don't know what the problem is. Maybe its because I have the newest update and this mod was for 10b???As far as the permissions, the phone asked automatically if I wanted to change the permissions. The original build.prop is still there... is there a way I can delete the modified build.prop and replace it with the original? I really wish I would not have followed this tut, it didn't seem like a popular method. There has to be a way to delete the modified build.prop right?
soundmasterx said:
Thanks for the reply. I used the editor recommended in the tutorial, 920 text editor. I followed the instructions word for word, I don't know what the problem is. Maybe its because I have the newest update and this mod was for 10b???As far as the permissions, the phone asked automatically if I wanted to change the permissions. The original build.prop is still there... is there a way I can delete the modified build.prop and replace it with the original? I really wish I would not have followed this tut, it didn't seem like a popular method. There has to be a way to delete the modified build.prop right?
Click to expand...
Click to collapse
Yes you can reflash the firmware or if you don;t want to restore to stock you can use ADB to fix the files and restore your .bak
Digital_MD said:
Yes you can reflash the firmware or if you don;t want to restore to stock you can use ADB to fix the files and restore your .bak
Click to expand...
Click to collapse
Again, thank you for the response. Do you recommend a specific method or tutorial for trying restore the original build.prop? I did search however, because this scenario is so specific I'm not sure there is an exact solution to my problem.
Again, just in case someone else can chime in, I followed the instructions on the first post of this thread (see first post for detailed info). I copied the original build.prop then changed the name of the original build.prop, edited the copy, moved it to the original directory and restarted the phone. Now my phone doesn't make it to the Verizon screen (I think it is stuck in boot loop), the screen stays black and the small led on the left corner flashes blue and green. If I can just get access to the storage I can replace the modified build.prop with the original that is still in the same directory just renamed. It seems like such an easy task but, I just don't know how to go about it I'm a somewhat of an old school tinker, I'm just now getting back into the swing of Android... Thanks in advance!!
Bump
Bump please
This is crazy... I changed 2 values in build.prop for tethering and my phone wont boot now... I didnt install a ROM, change DPI, or make any major changes WTF???
Do you have a custom recovery (twrp)?
Can you connect to your phone with adb?
If you have twrp, search the board for the startup hardware key sequence to reach twrp, else from adb do a reboot recovery.
In twrp, you can select to mount system, then go to advanced - file manager. You can delete the bad build.prop, rename the good one, then set the permissions on the good one. If your good copy of build.prop is on a PC, put it on a flash drive, and use twrp's file manager to get it into your phone.
If you have a saved copy of build.prop on your PC, you can also use adb's push command. (You may also want to look at the adb shell command. The sequence might be to open a shell, delete the bad build. prop, get the right build.prop into the right directory, then chmod the right build.prop so it has the proper permissions.)

[ATTENTION] Can't Modify Build.prop on CM7-based Rom

Good day!
Hi!
I had my Sony Ericson W8 E16i (Android 2.1 Update-1) obtained from an old box...
I decided to upgrade it to Android 2.3.7 via custom rom (thru the help of GingerDX)...
Everything's fine.
Now, I can't edit the "build.prop"...
I want to edit the phone model from "X8" to "W8"...
And also, to edit and delete some lines...
But it always reverts back to the original build.prop of that custom rom every after reboot...
Here's the actions I've already done:
1. Copy build.prop on sdcard. Edit it the way i wanted. Move it to root directory then fix the permission. Then move to /system to replace the existing build.prop. After reboot, it reverts.
2. I created a flashable zip of the editted build.prop, after system boot, nothing has changed.
3. I edit the build.prop directly to /system directory then save it. (It creates .bak file for its backup after I save.) After reboot, it reverts back again to the original build.prop of the custom rom.
Additional info.:
The "GingerDX v031b" is a CM7-based rom.
Any other info should I be provided?
Please help.

Categories

Resources