I am trying to cover all the bases before attempting my one chance at an ota update to .28 after originally using the build.prop mod.
Using root explorer I deleted the modded build.prop and renamed my build.prop.bak file back to build.prop and tablet rebooted fine. However, I now seem to remember that the listed "owner" of the modded build prop, when I looked at the file properties in root explorer one time, was "system", and now when I look at the original build.prop file which I restored it says the owner is "root"
Anyway, could somebody who successfully upgraded ota (or someone who never modded their build.prop) please look at the properties of their build.prop file using root explorer and tell me what the owner and group are listed as.
Thank you so much in advanced.
Mine says root/root
Thank you very much. Mine did also. Was able to successfully update by simply renaming build.prop.bak to build.prop
So this confirms that as long as one restores the original backup build.prop file, the ota update will work.
Mine says Owner-root, group-root
Mine updated to .28 manually and rooted.
Do the custom build.props still work after the .28 OTA update?
We need to wait till the thread is updated for 28 version, or you could do change by yourself. There are minor differences between original 21 and 28 build.prop.
Related
Hi I changed the stock build prop and want to change it back to before, so I was wondering if someone can post the stock build.prop, thanks
lolololten
Here you go (had to zip it, wouldn't accept .prop file)
Hello everyone, I've an mt6575 based ics device and I'd like to tweak some part of it like the build.prop, and update it via the stock recovery. but my recovery has "everything" except the update option! can I update the said parts if that option was present?
The reason why I want to update the build.prop is because it has some bad lines in it, it says 240 ppi on this 800x480, 7" device! funny! and I also would like to root it if possible...
Any help regarding the said things (recovery, updating build.prop, rooting etc.) is highly appreciated.
Regards.
dakocha said:
Hello everyone, I've an mt6575 based ics device and I'd like to tweak some part of it like the build.prop, and update it via the stock recovery. but my recovery has "everything" except the update option! can I update the said parts if that option was present?
The reason why I want to update the build.prop is because it has some bad lines in it, it says 240 ppi on this 800x480, 7" device! funny! and I also would like to root it if possible...
Any help regarding the said things (recovery, updating build.prop, rooting etc.) is highly appreciated.
Regards.
Click to expand...
Click to collapse
It might come late, but build.prop is not neccessery to be updated, or edited trough recovery, simply, you need to have rrot premission, then use root explorer, or es explorer, navigate to /system and at the end of the scroll line you should be able to see buil.prop file, open it with text editor and change what you need. Another option is to copy it to sdcard and send to PC, where you can use Notepad++ (because regular notepad will stirr things up otherwise) and edit lines. This applies to all devices, but best is to backup your ROM trough recovery prior to doing this. And also you should know what lines you will change and what consequences are going to happen. Good luck
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.
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.
Hi There
I have been a long time Hacker of largely MTK devices. So I wanted to ask a question and see if there's anything I am missing here:
I have an Android 8.1 device, I have rooted it using Magisk no problem and I have successfully changed the bootanimation.zip and also the audio files. I have been able to release the rooted OS, get the OS back to a released state with the changes as I have simply kept the removed dm-verity flags that Magisk uses on the OS.
However, I am unable to change the build.prop at all.
If I copy the build.prop file from the device, edit it on the PC, and save it back it bootloops. If I edit it, roll back all the changes and re-copy it back to the device it is fine.
I noticed the original build.prop permissions are RW (Chmod 600). I tested the above chmodding to 600 and 644 and it makes no difference. If it has changes in it, it fails, if not it works!
So something somewhere is maybe checking the build.prop against an original and not liking it.
Is there anyone on here that could help shed some light on this at all?
Bump...Anyone?
So an update to this is that I have now successfully removed DM-Verity from this device. I have also managed this on many other devices. I prove this by installing all kinds of changes on the device.
So I can pretty much do anything with this device, almost like pre-Android 5.1, however whenever I edit the build.prop at all it bootloops.
What I have tried so far:
I have tried all kinds of permissions on the file
I have duplicated the /vendor/build.prop in an attempt to get round possible build.prop variety issue.
I have removed the /vendor/build.prop
I have replaced system/prop with original build.prop but still edited (and changed back) from my PC and the device boots OK.
So it looks like somethiung is looking up the build.prop file and checking something. Almost like a DM-verity for the build.prop.
Really out of ideas now. i can literally unlock/change anything MTK now except for this issue.
Any help is much appreciated.
Oh i forgot to mention, this is a systemless and not TREBLE OS.
I usually change /system/build.prop and have never had an issue up through Android 10. I know this is elementary and no intention to offend anyone - but are you sure the file is being saved with unix-style line endings.
File-permission must be set to 644.