I tried to modify the build.prop lines, I can save it successfully and I can see the build.prop content updated without problem. But after reboot my Mate 9, all my modifications were gone and restored to original. Are all those files under /system on Android N or Huawei require special tricks to modify? Because I also found that I am unable to add new file under /system directory, any new file created will be removed after reboot. Sorry for my dumb questions, I am new to Huawei and Android N... THANKS
Doesn't editing the build.prop require root? Are you rooted?
Sent from my Nexus 6 using XDA-Developers mobile app
Sammath said:
Doesn't editing the build.prop require root? Are you rooted?
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes, my Mate 9 is rooted. The build.prop can be modified and saved before reboot, I can see all changed by reading the file. But the file will be replaced with original unmodified one after reboot... I also tried to modify an XML file under /system/emui/base/xml/ with same problem.
raychak said:
Yes, my Mate 9 is rooted. The build.prop can be modified and saved before reboot, I can see all changed by reading the file. But the file will be replaced with original unmodified one after reboot... I also tried to modify an XML file under /system/emui/base/xml/ with same problem.
Click to expand...
Click to collapse
You can't make any changes to the system partition directly... This is why we need to root with a systemless root procedure. It is also the reason why adaway and other things that modify system don't work.
One way around it is to unpack the system partition, modify it, and repack and then flash it. Big pain to do that though so I have not tried myself. Also OTA updates would no longer work right.
duraaraa said:
You can't make any changes to the system partition directly... This is why we need to root with a systemless root procedure. It is also the reason why adaway and other things that modify system don't work.
One way around it is to unpack the system partition, modify it, and repack and then flash it. Big pain to do that though so I have not tried myself. Also OTA updates would no longer work right.
Click to expand...
Click to collapse
so , without changing build.props how can you rebrand to others region FW?
OnimushaPooh said:
so , without changing build.props how can you rebrand to others region FW?
Click to expand...
Click to collapse
You have to modify the oeminfo, and then repartition (partitions layouts vary between regions) and flash the firmware with eRecovery. FunkyHuawei can handle the repartition and the flashing with eRecovery.
duraaraa said:
You have to modify the oeminfo, and then repartition (partitions layouts vary between regions) and flash the firmware with eRecovery. FunkyHuawei can handle the repartition and the flashing with eRecovery.
Click to expand...
Click to collapse
cool thanks, it quite complicate things, not simple as others huawei's phone.
OnimushaPooh said:
cool thanks, it quite complicate things, not simple as others huawei's phone.
Click to expand...
Click to collapse
They changed a lot when they went to Android N, unfortunately.
The real build.prop is under vendor, not system. Just for information.
Related
Hello,
My brother and I both have d2gs. I changed/removed apps in the system/apps folder as a result I was unable to upgrade to 2.4.3. My brother hasn't changed anything or rooted. If I copy his folder and overwrite my directory will I be able to update? (His phone is already updated)
Thx
Not going to work. Update updates bootloader, recovery and kernel beside system.
My advice if you can't get system stock manually is flash SBF, then update OTA
Sent from my DROID2 GLOBAL
leobg said:
Not going to work. Update updates bootloader, recovery and kernel beside system.
My advice if you can't get system stock manually is flash SBF, then update OTA
Sent from my DROID2 GLOBAL
Click to expand...
Click to collapse
Yea I didn't think it would be that easy haha
leobg said:
Not going to work. Update updates bootloader, recovery and kernel beside system.
My advice if you can't get system stock manually is flash SBF, then update OTA
Sent from my DROID2 GLOBAL
Click to expand...
Click to collapse
Yea I didn't think it would be that easy haha
leobg said:
Not going to work. Update updates bootloader, recovery and kernel beside system.
My advice if you can't get system stock manually is flash SBF, then update OTA
Sent from my DROID2 GLOBAL
Click to expand...
Click to collapse
I think Vexorg might mean the system/apps folder, which he or she modified to disable bloatware. It seems that removing apps from that folder makes the update fail. One should rename the apps instead to disable (e.g. CityID.apk -> CityID.apk.bak) so the original state can be recovered when updating.
Correct me if I'm wrong, but in that case copying the brother's system/apps should work fine. I've read that you can download the same APKs online to recover them, so I would imagine using the brother's directory contents should be fine as well.
adridge said:
I think Vexorg might mean the system/apps folder, which he or she modified to disable bloatware. It seems that removing apps from that folder makes the update fail. One should rename the apps instead to disable (e.g. CityID.apk -> CityID.apk.bak) so the original state can be recovered when updating.
Correct me if I'm wrong, but in that case copying the brother's system/apps should work fine. I've read that you can download the same APKs online to recover them, so I would imagine using the brother's directory contents should be fine as well.
Click to expand...
Click to collapse
Yup that's exactly what I meant, can anyone confirrm?
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-----
Hey guys,
I think I accidentally deleted the people system APK?! I can no longer save contacts. Wondering what the best way to fix this issue would be without flashing back to stock rom. I am currently rooted and running stock 4.4.2 KK, but I have made a lot of MODS and am running the Galaxy Gear Manager for my watch which is a huge process to get running that I don't want to have to repeat.
Any help is mucho appreciated!!!
If you can find the apk somewhere install that. Otherwise flash the system.img from the factory image.
jd1639 said:
If you can find the apk somewhere install that. Otherwise flash the system.img from the factory image.
Click to expand...
Click to collapse
Will flashing the system.img reset everything?
jason.T said:
Will flashing the system.img reset everything?
Click to expand...
Click to collapse
No, it'll reinstall all the system files. If you modified any of them you'll lose that but I doubt you modified any. This will only work if your bootloader is unlocked. If it isn't then you'll lose everything unlocking it.
jd1639 said:
No, it'll reinstall all the system files. If you modified any of them you'll lose that but I doubt you modified any. This will only work if your bootloader is unlocked. If it isn't then you'll lose everything unlocking it.
Click to expand...
Click to collapse
Awesome, my bootloader is unlocked, thanks!
jason.T said:
Awesome, my bootloader is unlocked, thanks!
Click to expand...
Click to collapse
Have super su on your internal sd card so you can flash it in your recovery. You'll lose root.
jason.T said:
Hey guys,
I think I accidentally deleted the people system APK?! I can no longer save contacts. Wondering what the best way to fix this issue would be without flashing back to stock rom. I am currently rooted and running stock 4.4.2 KK, but I have made a lot of MODS and am running the Galaxy Gear Manager for my watch which is a huge process to get running that I don't want to have to repeat.
Any help is mucho appreciated!!!
Click to expand...
Click to collapse
Do you still need help with this? It's not that difficult to just pull the app and move it into the right system folder. Once you do that, change permissions to match the other apps, and reboot, you should be back to normal. I'll post the apk if you need it.
es0tericcha0s said:
Do you still need help with this? It's not that difficult to just pull the app and move it into the right system folder. Once you do that, change permissions to match the other apps, and reboot, you should be back to normal. I'll post the apk if you need it.
Click to expand...
Click to collapse
The APK would be amazing! I haven't been able to find it, I got the System.img that I was going to flash after work, but the APK would be a lot easier! Thanks!!
Hi,
It's Contact.apk you would need?
jason.T said:
The APK would be amazing! I haven't been able to find it, I got the System.img that I was going to flash after work, but the APK would be a lot easier! Thanks!!
Click to expand...
Click to collapse
No problem. I'll have it uploaded in a bit. It's just the People / Contacts apk, right? And you're odexed or deodexed?
jason.T said:
The APK would be amazing! I haven't been able to find it, I got the System.img that I was going to flash after work, but the APK would be a lot easier! Thanks!!
Click to expand...
Click to collapse
You can pretty much just download any ROM available, extract the Contacts.apk file (I think its in system/priv-app/) and put it on your device.
es0tericcha0s said:
No problem. I'll have it uploaded in a bit. It's just the People / Contacts apk, right? And you're odexed or deodexed?
Click to expand...
Click to collapse
Yes, the People/contacts apk, and I am still stock, just rooted and have an unlocked bootloader, so odexed, I believe.
jsgraphicart said:
You can pretty much just download any ROM available, extract the Contacts.apk file (I think its in system/priv-app/) and put it on your device.
Click to expand...
Click to collapse
I tried that with one of the apk's I found, but I couldn't get it to work. I may have gotten a corrupt file though.
Here's a flashable zip in attachment (wipe Dalvik cache just in case) for Contacts.apk (with the .odex file)...
You still have ContactsProvider.apk?
jsgraphicart said:
You can pretty much just download any ROM available, extract the Contacts.apk file (I think its in system/priv-app/) and put it on your device.
Click to expand...
Click to collapse
He might not be in a situation where he can download a large file like a complete rom. He did mention being at work. Anyway, these should work:
https://dl.dropboxusercontent.com/u/9903887/Apps/Contacts.apk
https://dl.dropboxusercontent.com/u/9903887/Apps/Contacts.odex
If you are deodexed, let me know, and don't use just the apk ^ there or it will force close constantly.
Just use a file manager that has root access (ES File Manager is a good, free choice, if you don't have another) and move the app and odex file to:
/system/priv-app
Make sure to change the permissions. The 3 Read options should be checked and the first Write option. If you aren't sure, just read the permissions of another app in that folder and match it. Then just reboot and should be back to normal.
viking37 said:
Here's a flashable zip in attachment (wipe Dalvik cache just in case) for Contacts.apk...
You still have ContactsProvider.apk?
Click to expand...
Click to collapse
Awesome!, thanks. The only thing I see in my app/system directory that pertains to contacts is the "GoogleContactsSyncAdapter.apk" I will be attempting to get this fixed when I get home in a couple hours.
jason.T said:
I tried that with one of the apk's I found, but I couldn't get it to work. I may have gotten a corrupt file though.
Click to expand...
Click to collapse
You need to change the permissions. If you didnt do that, then it wont work. es0tericcha0s explained it in his last post
jason.T said:
Awesome!, thanks. The only thing I see in my app/system directory that pertains to contacts is the "GoogleContactsSyncAdapter.apk" I will be attempting to get this fixed when I get home in a couple hours.
Click to expand...
Click to collapse
Re,
Contacts.apk and ContactsProvider.apk are in /system/priv-app...
You are odexed, right?
es0tericcha0s said:
He might not be in a situation where he can download a large file like a complete rom. He did mention being at work. Anyway, these should work:
https://dl.dropboxusercontent.com/u/9903887/Apps/Contacts.apk
https://dl.dropboxusercontent.com/u/9903887/Apps/Contacts.odex
If you are deodexed, let me know, and don't use just the apk ^ there or it will force close constantly.
Just use a file manager that has root access (ES File Manager is a good, free choice, if you don't have another) and move the app and odex file to:
/system/priv-app
Make sure to change the permissions. The 3 Read options should be checked and the first Write option. If you aren't sure, just read the permissions of another app in that folder and match it. Then just reboot and should be back to normal.
Click to expand...
Click to collapse
Dropped those 2 files into the correct /system/priv-app, changed permissions, still nothing? What am I missing?
jason.T said:
Dropped those 2 files into the correct /system/priv-app, changed permissions, still nothing? What am I missing?
Click to expand...
Click to collapse
Dumb question, but did you reboot?
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
This is my first time rooting my phone (tried rooting an o+ phone but couldn't unlock the bootloader) and I want to know how to my get phone's firmware. I tried using the Samsung Firmware Downloader but it won't accept my model and region.
I've tried using SuperSu to root but Root Checker says root access wasn't properly installed. What do I do now? Can I download a different firmware from a different site and is it safe? Does showing my pda code safe?
Edit: Forgot to mention I've already flashed TWRP.
Excuse me but what is your region and model number
tech-mаn said:
Excuse me but what is your region and model number
Click to expand...
Click to collapse
Never mind, I manage to download the firmware and root my phone thanks to Samsung Downloader. I wasn't able to download it at first because I keep using XXU (the one I saw in *#1234#, samsung firmware) as my region but it was actually XTC (I checked Software information in the About Phone).
Ok
if twrp is installed
root the phone with magisk
My next problem is changing the /system/ into read/write. I can't access build.prop. Haven't tried using adbd insecure but I have a feeling it won't work with Android 13. I'm currently trying to find the flashable zip from this thread to convert my /system/ into read/write.
MasterKwonKaichi said:
My next problem is changing the /system/ into read/write. I can't access build.prop. Haven't tried using adbd insecure but I have a feeling it won't work with Android 13. I'm currently trying to find the flashable zip from this thread to convert my /system/ into read/write.
Click to expand...
Click to collapse
Maybe it'll work
MasterKwonKaichi said:
My next problem is changing the /system/ into read/write. I can't access build.prop. Haven't tried using adbd insecure but I have a feeling it won't work with Android 13. I'm currently trying to find the flashable zip from this thread to convert my /system/ into read/write.
Click to expand...
Click to collapse
first root your device
then use mt manager to access build.prop file
i tested this in my sm-t585 with lineage os custom rom
alireza9082 said:
then use mt manager to access build.prop file
Click to expand...
Click to collapse
Accessing the build.prop file was not the problem, I can access it with any app (build.prop file, root explorer, etc..). My problem is whatever change I did to the build.prop file will not be saved since I don't have read/write access.
MasterKwonKaichi said:
Accessing the build.prop file was not the problem, I can access it with any app (build.prop file, root explorer, etc..). My problem is whatever change I did to the build.prop file will not be saved since I don't have read/write access.
Click to expand...
Click to collapse
as i said
use mt manager to save changes in build.prop
Since our system is F2FS you can't modify system it stays RO you can make a magisk module yourself to modify build prop also don't use supersu rooting is very easy just flash twrp then flash magisk. I'm making a custom rom which I'm hoping to release soon that's ext4 but I'm limited by time and the recent events from where I live so I can't give a ETA