Hello!
I'm happily rooted and would like to dump my density from 480 to say, 360. I edit build.prop and all is good it seems until I reboot whereby the settings is apparently unchanged. Huh? Any ideas please folks?
I also tried disabling fast reboot from the power settings menu and also mounting system rw before applying the change. Density remains at 480.
bonstio said:
Hello!
I'm happily rooted and would like to dump my density from 480 to say, 360. I edit build.prop and all is good it seems until I reboot whereby the settings is apparently unchanged. Huh? Any ideas please folks?
I also tried disabling fast reboot from the power settings menu and also mounting system rw before applying the change. Density remains at 480.
Click to expand...
Click to collapse
Using ViperOne Rom, and the 400 density in build.prop stick...
It's because /system is write protected. You need to edit the build.prop and upload it in recovery mode (I use TWRP) and then chmod the file to 644. Running 360dpi, looks great.
plisk3n said:
It's because /system is write protected. You need to edit the build.prop and upload it in recovery mode (I use TWRP) and then chmod the file to 644. Running 360dpi, looks great.
Click to expand...
Click to collapse
I'll give it a try but I have a feeling this isn't the full story. As I said, I have mounted /system as RW. If I manually edit the file and save it, I get no permissions errors; the file really does save. It's almost as if something is reverting the file at boot time but that seems too weird...
Same problem
I had my HTC M8 rooted specifically for changing my density to 320. It is not working for me either. Is there an easy way to do what was said about system folder being protected?
I'm an M8 noob still, but don't you need to be s-off to make system changes like this.... Ones that survive a reboot anyway?
Related
Hello.
Since this is the first phone I actually trying learn and modify myself I have no experience with possible side effects and such, however what I've read somewhere else, SystemUI.apk as well as framework-res.apk should NOT cause boot loops or no boot at all.
On Nitro however it does both: first it boot loops then after battery pull it doesn't boot at all, hanging at second LG logo.
Then booting into CWM and replacing SystemUI.apk with the original one does not bring phone back to life, in fact restoring whole system partition doesn't do a damn thing. Only restoring full backup brings it back.
So the question is, what the __ is wrong with this phone?
P.S.
I've tried replacing files with Root Explorer as well with adb push. After any .apk files replaced I do chmod 644 and also chown root.root to make sure.
[email protected] said:
Hello.
Since this is the first phone I actually trying learn and modify myself I have no experience with possible side effects and such, however what I've read somewhere else, SystemUI.apk as well as framework-res.apk should NOT cause boot loops or no boot at all.
On Nitro however it does both: first it boot loops then after battery pull it doesn't boot at all, hanging at second LG logo.
Then booting into CWM and replacing SystemUI.apk with the original one does not bring phone back to life, in fact restoring whole system partition doesn't do a damn thing. Only restoring full backup brings it back.
So the question is, what the __ is wrong with this phone?
P.S.
I've tried replacing files with Root Explorer as well with adb push. After any .apk files replaced I do chmod 644 and also chown root.root to make sure.
Click to expand...
Click to collapse
[email protected], I replaced both those files, if im not mistaken, when I applied the percentage battery mod and no carrier mod, but i never went into boot loops or soft brick. What, if i may ask, were you attempting to do replacing those two files?
Ok, here is my observations so far:
It can boot loop if used any android based software to copy files (Root Explorer, ES File Explorer, etc), unless you somehow manage properly chmod and chown the replaced file, otherwise you'll end up with ridiculous ---rw-r-- permissions (0064 - owner can't read write or execute).
In my tests it's pretty much impossible change chmod on replaced SystemUI.apk because of FC on everything.
Next, when something went wrong and SystemUI.apk that was replaced via adb push didn't work resulting in boot animation loop, it can get to the point, that even restoring unmodified file won't bring the system back. Something happening during that loop that destroys/corrupts other stuff in the data partition. When that happens even restoring system partition doesn't work, only restore data or factory reset can help.
As of what I'm doing with SystemUI.apk, I'm trying figure out why the space in the taskbar where clock is, is not dynamic, when you change to 24H mode it wastes so much space. I already tried use the same data from SU640 rom, it didn't change a thing.
And also trying get the CRT ON effect, which will be a beautiful with already implemented CRT OFF
[email protected] said:
Ok, here is my observations so far:
It can boot loop if used any android based software to copy files (Root Explorer, ES File Explorer, etc), unless you somehow manage properly chmod and chown the replaced file, otherwise you'll end up with ridiculous ---rw-r-- permissions (0064 - owner can't read write or execute).
In my tests it's pretty much impossible change chmod on replaced SystemUI.apk because of FC on everything.
Next, when something went wrong and SystemUI.apk that was replaced via adb push didn't work resulting in boot animation loop, it can get to the point, that even restoring unmodified file won't bring the system back. Something happening during that loop that destroys/corrupts other stuff in the data partition. When that happens even restoring system partition doesn't work, only restore data or factory reset can help.
As of what I'm doing with SystemUI.apk, I'm trying figure out why the space in the taskbar where clock is, is not dynamic, when you change to 24H mode it wastes so much space. I already tried use the same data from SU640 rom, it didn't change a thing.
And also trying get the CRT ON effect, which will be a beautiful with already implemented CRT OFF
Click to expand...
Click to collapse
LOL! Now I remember you were the one so anal about that extra space by the clock when you convert to 24h setup haha.
Also, what do you mean get the CRT ON effect? I dont understand what that is
Okay, maybe I'm missing something, but I've been replacing framework-res.apk and SystemUI.apk more than once a day on average every day, and have never had a problem while using root explorer with any bootloops/not booting, etc. You should not have any problems at all changing SystemUI.apk or framework-res.apk as long as you are properly changing their permissions after you have put them in /system/ but BEFORE you have put them in /system/app and /system/framework, respectively. If you are trying to change permissions "after the file has been replaced" that's too late. It's probably corrupt. Must be changed before.
itiskonrad said:
Okay, maybe I'm missing something, but I've been replacing framework-res.apk and SystemUI.apk more than once a day on average every day, and have never had a problem while using root explorer with any bootloops/not booting, etc. You should not have any problems at all changing SystemUI.apk or framework-res.apk as long as you are properly changing their permissions after you have put them in /system/ but BEFORE you have put them in /system/app and /system/framework, respectively. If you are trying to change permissions "after the file has been replaced" that's too late. It's probably corrupt. Must be changed before.
Click to expand...
Click to collapse
You can't change permissions on the file that is not there yet.
The bootloops I'm experiencing is when for example I decompile SystemUI.apk, don't change anything and recompile it back. It worked before but not anymore, and I yet to figure out why. Using apktool v1.4.3
All I could think of is this started happening after I attempted install xUltimate-v2.3.3 to deodex files. It's probably just coincidence though...cause I also tried do recompilling on fresh virtual windows on just unbricked phone files.
It's weird.
[email protected] said:
You can't change permissions on the file that is not there yet.
Click to expand...
Click to collapse
You put the file in /system/ so it IS there. Then you change the permissions. Now that the file has correct permissions, you put it in /system/app or /system/framework and let it overwrite the original, so the INSTANT it replaces the original one it already has the correct permissions. You HAVE to put it into /system/, otherwise you can't change to those permissions, but you need to do it before you overwrite the originals.
Nice, I never thought of that. Thanks!
LG optimus LTE Won't turn on after install CWM
hi, my lg optimus LTE won't turn of after i try to install CWM and try to boot it. Phone is dead now and every time i try turn it on, only the 3 touch button is flashing for couples seconds and went off. Any one can help?? When i try plug it it in the computer it only recognize it as QHUSB_LG (can't get the correct name, don't have my PC with me). PLease help!!
Remove battery, put it back in, then plug the phone into wall charger. Let it charge.
yea i did all that, still only the touch screen button is flashing. Gonna try a different battery and see what happen. Just got this phone less than 2 weeks. Let hope it is a better problem.
[email protected] said:
Nice, I never thought of that. Thanks!
Click to expand...
Click to collapse
[email protected], I made the same mistake but with the framework-res.apk and now my phone is stuck in a bootloop. Were you able to fix the permissions for the file? Or did you have to do a factory reset?
Thanks
Yes, but I had original file at the same directory just renamed and also I had to re-do root while it was boot looping, sometimes I had to repeat the root process 50 times before it succeeded, like killing half a day.
Hi, I am currently using stock JB with a couple of mods/extras i managed to link in via the kitchen. But frustratingly so I cannot change the boot image and are hoping with appreciation someone in here can direct me. So far I have tried everything I am capable of. That is from within the kitchen enabling the function which is suppose to allow you to change your boot animation. Although it gives you the tick and creates a different directory for your boot animation this still doesn't work. I have tried replacing hTC_boot_one.zip file but does not work. Whenever i do replace or alter that file the boot starts as normal with white htc and then goes to black with android with a back light rolling from side to side, like kit in night rider. I also have tried flashing Mattmans-Boot-Animation which uses aroma installer. Still didnt work and as far as I know it just added the file in system/customize/resource/. There appears to be a command file preventing any changes internally in stock. Really appreciate and hope someone can help. Thanks in advance......happy new years.....:good:
Did you root the rom ?
You need root acces to write in the system directory's ......
You need SU
Mr Hofs said:
Did you root the rom ?
You need root acces to write in the system directory's ......
Click to expand...
Click to collapse
Yeah rooted with su access to system files.....cheers!
basically is just stock jb base.....
veroby said:
Hi, I am currently using stock JB with a couple of mods/extras i managed to link in via the kitchen. But frustratingly so I cannot change the boot image and are hoping with appreciation someone in here can direct me. So far I have tried everything I am capable of. That is from within the kitchen enabling the function which is suppose to allow you to change your boot animation. Although it gives you the tick and creates a different directory for your boot animation this still doesn't work. I have tried replacing hTC_boot_one.zip file but does not work. Whenever i do replace or alter that file the boot starts as normal with white htc and then goes to black with android with a back light rolling from side to side, like kit in night rider. I also have tried flashing Mattmans-Boot-Animation which uses aroma installer. Still didnt work and as far as I know it just added the file in system/customize/resource/. There appears to be a command file preventing any changes internally in stock. Really appreciate and hope someone can help. Thanks in advance......happy new years.....:good:
Click to expand...
Click to collapse
Dude. I think you need root your rom to get custom boot (-:
There're a lot ready-to-go tools for booting animation
Good luck !
allv.newbie said:
Dude. I think you need root your rom to get custom boot (-:
There're a lot ready-to-go tools for booting animation
Good luck !
Click to expand...
Click to collapse
its rooooooooooteeeeeeeed thx..
veroby said:
its rooooooooooteeeeeeeed thx..
Click to expand...
Click to collapse
lol
https://play.google.com/store/apps/details?id=com.simproductions.bachanger&hl=it I think it can works
fez vrasta said:
lol
https://play.google.com/store/apps/details?id=com.simproductions.bachanger&hl=it I think it can works
Click to expand...
Click to collapse
hey thx, but it did not work. I cant even find where it has placed the file. If it managed to. Man im p-i-s-s-e-d. not your fault its just on my tits. cheers....
allv.newbie said:
Dude. I think you need root your rom to get custom boot (-:
There're a lot ready-to-go tools for booting animation
Good luck !
Click to expand...
Click to collapse
Its rooooooooooooooooooteeeeeeeeeeeeeeeeeeeeed cheers....
Its my own custom rom but this little simple thing i cannot get around. I can only semis that within stock base there's a system file preventing any change...
Have you mounted system as rw? In root explorer you just press the button, not sure on other apps, and have you set the right permissions? rw-r--r-- to match everything else in system/customize/resource.
maXimus One X
evo1rs said:
Have you mounted system as rw? In root explorer you just press the button, not sure on other apps, and have you set the right permissions? rw-r--r-- to match everything else in system/customize/resource.
maXimus One X
Click to expand...
Click to collapse
Thanks for your help. Not sure what you mean by mount the system as rw. The permissions - yes always changed permissions when trying to replace the hTC_bootup_one.zip file. Cheers...
veroby said:
Thanks for your help. Not sure what you mean by mount the system as rw. The permissions - yes always changed permissions when trying to replace the hTC_bootup_one.zip file. Cheers...
Click to expand...
Click to collapse
If system is mounted as ro (read only) you can't change anything in the folder, this is the default setting I think and it needs to be mounted as rw to allow changes.
You could try to rename something in the system directory and if it doesn't actually change then you need to change it, or check if the filesize of the boot animation you replace changes.
Like I said, rootexplorer app changes it with a tap of the button, not sure what else to use
maXimus One X
evo1rs said:
If system is mounted as ro (read only) you can't change anything in the folder, this is the default setting I think and it needs to be mounted as rw to allow changes.
You could try to rename something in the system directory and if it doesn't actually change then you need to change it, or check if the filesize of the boot animation you replace changes.
Like I said, rootexplorer app changes it with a tap of the button, not sure what else to use
maXimus One X
Click to expand...
Click to collapse
Thanks again. No problem renaming any file within system so I guess it is mounted as rw. As to file size, i have tried different file sizes and identical file sizes to the hTC_boot_one.zip file. I have even tried using the same Zip file and just replacing with different images. Making sure to end up with the same values. Nothing seems to work.
Strange, I had rooted stock Rom and it worked fine, maybe you have the wrong format of files or haven't zipped as store only, no compression. I assume it is a sense one x Rom?
Maybe try this one I made for the Rom I use
http://forum.xda-developers.com/showthread.php?p=31136343#post31136343
maXimus One X
evo1rs said:
Strange, I had rooted stock Rom and it worked fine, maybe you have the wrong format of files or haven't zipped as store only, no compression. I assume it is a sense one x Rom?
Maybe try this one I made for the Rom I use
http://forum.xda-developers.com/showthread.php?p=31136343#post31136343
maXimus One X
Click to expand...
Click to collapse
Lol - hadnt planned on having maximus on my own custom rom but will give it a try tomorrow. Let you know...cheers again...:good:
Yeah, just to test formats and setup of course!
maXimus One X
So i recently just reflashed the 5.1 N750XXUDOK5 ROM on my N750 Everthings running just fine as but i was trying to change my DPI With RomToolbox but it kept giving me an error saying "Failed to get any build properties" So i tried changing it manually and noticed that the Build.prop file wasn't even there in /system/ It was missing. but the weird thing is that my Device still works just fine. Normally if i dont have the build.prop file my device shouldn't even boot up but it did and its working too.
My device is rooted surely since I'm able use other root apps.
I dont wanna reflash the ROM all over again so i was wondering if there was any easier way to do this?
I have no idea what in the world happened that my Build.prop just disappeared but is there any way to bring it back or could someone please just provide me their Build.prop file so i could push it on mine ?
Thanks!
Mount your system as r/w
Sorry for the newb question but, I'm not able to get venom rom tweaks to hold the ability to keep system as r/w. I'm trying to make changes to build.prop and default.prop but they keep reverting on boot. I imagine I need to flash one of the boot images as mentioned in the first couple posts but am not sure which one would work with Rogers/Tbaytel GSM. It's odd tho cause selinux does hold permissive when set thru venom tweaks. Kernel changes thru an editor won't stick either.
Running
Viper 6.0
Elemental X 5 kernel
Rooted and S-off
Managed to get kernel to save settings now by disabling remaining write protection using su adb shell command. Haven't tested the .prop edits yet but I will shortly. Also wondering what does ro.rilvmail settings effect as viper build seems to be based of European area.
Update: Prop settings still revert on reboot. Going to try to adb push and pull a configured prop file.
How are you changing the file? It could be an app issue. I have had issues with certain file explorers not saving files properly or at all. I have best luck with es file explorer.
Make sure the file permissions are correctly set before you reboot.
Beamed in by telepathy.
shivadow said:
How are you changing the file? It could be an app issue. I have had issues with certain file explorers not saving files properly or at all. I have best luck with es file explorer.
Make sure the file permissions are correctly set before you reboot.
Beamed in by telepathy.
Click to expand...
Click to collapse
All good man I was able to use adb with root permission to remount and push altered build.prop file just not able to do default.prop but no biggie it was only to change the default USB connection. My only question relates to the ro.rilvmail settings now and what they would be for Canadian Rogers/tbaytel. Phone is almost perfect just have to use qpst and such to enable all network bands in my area and I will finally have my ultimate M9. There are not enough words to describe how amazing this phone is with all these tweaks and mods thank you so much to xda for making this all possible and the community of devs for your invaluable work.
Bump anyone have any info??
THIS IS NOT FOR FAINT OF HEART. DON'T BLAME ME IF YOU BREAK SOMETHING.
Mount system as RW in TWRP. (this took mounting, unmounting, then remounting for me)
Use the following commands CAREFULLY from a computer.
cat /system/build.prop > /sdcard/build.prop
Open the build.prop from the sdcard and edit the following line numbers: 25, 26
You are changing:
ro.product.name=perseus
ro.product.device=perseus
To this:
ro.product.name=perseus_global
ro.product.device=perseus_global
save the file on the sdcard
Go back to ADB session and do this:
cat /sdcard/build.prop > /system/build.prop
IF THIS FAILS YOUR SYSTEM IS NOT RW, UNMOUNT AND REMOUNT IN THE MOUNTS MENU.
Go back to the mounts menu and unmount /system
Flash Magisk 17.3 (18.0 seems to be having intermittent issues with passing checks)
Reboot, and enjoy your CN device running Global with ROOT.
out-file : Could not find a part of the path 'C:\sdcard\build.prop'.
I got that error above. How do i know twrp mounted system correctly?
nvm... i went into advance and did via terminal
Great find, works!!
Thanks!!
You're welcome. I may try to make a flashable zip to do this automatically, but I haven't had a chance to look at it.
Work so well, Thanks @PWn3R!
xterminater07 said:
out-file : Could not find a part of the path 'C:\sdcard\build.prop'.
I got that error above. How do i know twrp mounted system correctly?
nvm... i went into advance and did via terminal
Click to expand...
Click to collapse
Here is the clue. " 'C:\sdcard\build.prop'."
What is a Windows drive letter doing on an Android? Adb session?
@PWn3R YOU ARE THE MAN
Has anyone tried a custom kernel on the latest global? I tried androplus v 0.6 and it didnt really work. It allows me to replace files in system but not rename because when I overwrite it still says there is an existing file with same name.
Any kernel that works please let me know. I am working with defcomg to get gcam modded more than the current ones.
I would like to try, i already had install last global, and this rtemove my twrp instead the official recovery.... Can you give me all the steps to do from this position? Thank you
I have a problem with camera, force close no matter what I've done. may be build.prop change?
kbello said:
I have a problem with camera, force close no matter what I've done. may be build.prop change?
Click to expand...
Click to collapse
i got this as well... oh well going back to xiaomi eu rom
Hi the change to the build.prop did not break the camera. Mine is working fine. Maybe clear app data for that app?
I do many times, didn't work,
---------- Post added at 11:45 PM ---------- Previous post was at 11:23 PM ----------
This is the error:
java.lang.RuntimeException: unSupported Saturation
at com.android.camera2.compat.MiCameraCompatBaseImpl.applySaturation(MiCameraCompatBaseImpl.java:248)
at com.android.camera2.compat.MiCameraCompat.applySaturation(MiCameraCompat.java:49)
at com.android.camera2.MiCamera2.applySaturation(MiCamera2.java:2486)
at com.android.camera2.MiCamera2.applyCommonSettings(MiCamera2.java:2858)
at com.android.camera2.MiCamera2.applySettingsForCapture(MiCamera2.java:2971)
at com.android.camera2.MiCamera2ShotNormal.generateRequestBuilder(MiCamera2ShotNormal.java:141)
at com.android.camera2.MiCamera2ShotNormal.startShot(MiCamera2ShotNormal.java:59)
at com.android.camera2.MiCamera2.captureStillPicture(MiCamera2.java:2042)
at com.android.camera2.MiCamera2.triggerCapture(MiCamera2.java:1892)
at com.android.camera2.MiCamera2.takePicture(MiCamera2.java:991)
at com.android.camera.module.Camera2Module.startNormalCapture(Camera2Module.java:1130)
at com.android.camera.module.Camera2Module.onWaitingFocusFinished(Camera2Module.java:406)
at com.android.camera.module.loader.camera2.FocusManager2.capture(FocusManager2.java:767)
at com.android.camera.module.loader.camera2.FocusManager2.doSnap(FocusManager2.java:326)
at com.android.camera.module.Camera2Module.onShutterButtonClick(Camera2Module.java:1057)
at com.android.camera.fragment.bottom.FragmentBottomAction.onSnapClick(FragmentBottomAction.java:1653)
at com.android.camera.ui.CameraSnapView$1.handleMessage(CameraSnapView.java:67)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:201)
at android.app.ActivityThread.main(ActivityThread.java:6806)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:547)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:873)
@PWn3R, the root is working but there are some functionalities that disappeared in the setting menu such as slider settings, screen color.
For those who wants to revert to CN rom, revert the changes you have done and DO NOT forget to remove Magisk by flashing the uninstaller zip otherwise the device will bootloop.
I restore the original build.prop and boot.img, the camera came back to work. Any workaround?
kbello said:
I have a problem with camera, force close no matter what I've done. may be build.prop change?
Click to expand...
Click to collapse
I didn't notice if the slider settings were there before changing the build.prop. The problem here is that when you flash magisk it's enabling secure boot, which is triggering a check that normally runs when the device is locked. I think we can probably fix that by modifying the file that causes it and then this will work without build.prop changes. I have not had a chance to look into that, but will try to do so.