Ok, I tried to modify a system file and now it won't boot. I've done some searching but can't find something to work.
I tried to change my build.prop to change my dpi setting. I found instructions that said ". Scroll down to ro.sf.lcd_density=240. Change the value to anywhere between 180 and 240. The lower the value, the higher density your screen will have."
Mine was set to 640. I didn't want a major change so I set it to 600. Not it gets stuck with the AT&T logo. I have rooted. I can get into download mode. When I changed the setting it made a back up of the build.prop. All I really need to do is to delete my build.prop and change the backup filename and it should be fixed, right?
How do I do that? I used "[ROOT] TMO/VZW/ATT/SPRINT/INTL Root your LG G4 with Low Effort Root!" to get root.
One other thing. I have already removed the install image I used to root off the phone. That would have been easy to simply install it again. Unfortunately, I can't. Any way to send it to the phone so I can load it?
Please help!
Ralph
Good news. I went into AT&T and my phone is still under warranty. They are shipping me a new phone. I will keep my image on the phone this time.
Ralph
Related
Hi folks
I've got a little problem wich some of you I hope, may have a solution to.
From some time I was experiencing trouble with my data bandwidth, so far i believed that it had something to do with my carrier, but today, i wished to try some of the build.prop tweak i had see on this forum.
So I went looking for my own build.prop wich was not on the root of my play...
From then I recovered one from an nandroid backup of mine, after that i changed the file permission to rw--r--r and rebooted my phone and like poof, the file was gone.
The amazing thing is that I noticied some major improvement in my upload rate for a little time^^ but after a while it just droped back to what I was used to.
I tried to recover it several times but it disapears every time I reboot my play.
Is this a normal behavior?
Must I use the default.prop in order to make the change persistent?
I'm on a stock 4.0.2.A.0.42 baseband -36 with a locked bootloader
Thanks in advance for you feedback
Have a nice evening
Well if your build.prop actually disappeared, your phone wouldn't boot. Are you sure you're looking in /system?
jacklebott said:
Well if your build.prop actually disappeared, your phone wouldn't boot. Are you sure you're looking in /system?
Click to expand...
Click to collapse
Ok i dont know why but i was thinkin it was at the root of the phone^^
Plus es explorer didn't found it when i searched for it... it is in fact... there...
Thank you jacklebott
Would you know where i could fiind the meaning of the semc properties in there, and maybe you could also point me to a thread where i can find tweaks meant for the play?
guys im in deep trouble here. my phone got softbricked after i made changes in build.prop(just changed dpi) using some text editor. after saving the file and restarting the phone. its not turning on, just blue and green led flashing. tried to use the pc suite, and flash tool 2014, but still no success. i can still go to download mode though. hope someone help me here
Sent from my SM-T705 using Tapatalk 2
deejay6901 said:
guys im in deep trouble here. my phone got softbricked after i made changes in build.prop(just changed dpi) using some text editor. after saving the file and restarting the phone. its not turning on, just blue and green led flashing. tried to use the pc suite, and flash tool 2014, but still no success. i can still go to download mode though. hope someone help me here
Sent from my SM-T705 using Tapatalk 2
Click to expand...
Click to collapse
Flash Rom using Normal instead of CSE? Next time either read more threads or use a proper editor or even better: a pc to edit build.prop.
Otherwise you can try to adb push original build.prop to your phone but flashing Rom is much easier imho.
Pfeffernuss said:
Flash Rom using Normal instead of CSE? Next time either read more threads or use a proper editor or even better: a pc to edit build.prop.
Otherwise you can try to adb push original build.prop to your phone but flashing Rom is much easier imho.
Click to expand...
Click to collapse
i wanted to try and flash a build.prop but dont know how. ive already tried flashing kdz file but didnt work out. actually im not new to this as ive been rooting my phone since s2 days, even when i bought this amazing phone i rooted it right away. but after i update it to 10i, i tried rooting back which worked fine, however when i tried editing the build.prop thsts where this problem comes out.
Sent from my SM-T705 using Tapatalk 2
You didn't set the permissions right for the prop file, that's why it's stuck in a bootloop.
Permissions are suppose to be rw r r.
Also, modifying via 920 Text Editor or via your PC, then load it back into the phone.
Could be the editor used did not handle the whole very large build.prop file and truncated when you saved it.
Follow this guide.
http://forum.xda-developers.com/showthread.php?t=2799647
Read it. You might get Download Fail can not restart to download mode a few times. Keep trying, use different usb ports restart computer, try again, restart phone to download mode. I must have got that message 50 times then all of a sudden it worked. Its a pain but see how it goes. There is another way but it is a pain and involves lots of setup.
Check post 202-203:
without flash back after bootloop. (for next time)
http://forum.xda-developers.com/lg-...s-free-ram-t2825693/post55094520#post55094520
A warring about build.prop without the right app. (from what dorimanx said ! )
http://forum.xda-developers.com/showpost.php?p=54970011&postcount=171
to find & download your right and last Ver. rom stock by your imei
http://forum.xda-developers.com/showthread.php?t=2683691
If you chance settings on Build.prop to worng setings you can and will have bootloop.
here are what in that post said about DPI and more...
#Best dpi for G3
#default value 640
ro.sf.lcd_density=560
Source:
http://forum.xda-developers.com/lg-g3/general/guide-build-prop-tweaks-free-ram-t2825693
http://forum.xda-developers.com/showthread.php?t=2781043
App fot DPI Ch...
https://play.google.com/store/apps/details?id=com.texdroider.texdroider_dpi
or
https://play.google.com/store/apps/details?id=com.theSushi.dpichanger
scarecrow2012 said:
Follow this guide.
http://forum.xda-developers.com/showthread.php?t=2799647
Read it. You might get Download Fail can not restart to download mode a few times. Keep trying, use different usb ports restart computer, try again, restart phone to download mode. I must have got that message 50 times then all of a sudden it worked. Its a pain but see how it goes. There is another way but it is a pain and involves lots of setup.
Click to expand...
Click to collapse
yes this did worked for me. i tried to chaged port then suddenly firmware update did run. and now my phone has resurrected back from the dead...
now... back to modding!! hahaha...
Sent from my LG-D855 using Tapatalk 2
deejay6901 said:
yes this did worked for me. i tried to chaged port then suddenly firmware update did run. and now my phone has resurrected back from the dead...
now... back to modding!! hahaha...
Sent from my LG-D855 using Tapatalk 2
Click to expand...
Click to collapse
Congrats, all the best with the modding.
Anybody tried to change LCD density in build.prop file? My G4 F500S unable to boot normally after I changed the value to 480. My phone is able to pass the LG logo screen, sometimes it will display the apps optimization in progress.. when optimization done, it display something like system ui problem (can't see clearly as it rebooted in very short time)... Still finding a solution to fix the problem now
raychak said:
Anybody tried to change LCD density in build.prop file? My G4 F500S unable to boot normally after I changed the value to 480. My phone is able to pass the LG logo screen, sometimes it will display the apps optimization in progress.. when optimization done, it display something like system ui problem (can't see clearly as it rebooted in very short time)... Still finding a solution to fix the problem now
Click to expand...
Click to collapse
I think anything less than 530 causes issues. I'm running 540 fine.
Juzman said:
I think anything less than 530 causes issues. I'm running 540 fine.
Click to expand...
Click to collapse
I see... I think that is the root cause of the problem making my phone unable to boot up.
raychak said:
I see... I think that is the root cause of the problem making my phone unable to boot up.
Click to expand...
Click to collapse
Quite possibly. I am guessing you may be able to change it to 540 or something via ADB. I'm not too sure. Maybe an adb pull /system/build.prop then edit and push it back.
Hey! Everyone I am thankful to all of you who are shraing your knowledge and also to the entire XDA community.You guys are truly awesome.So sometime back I got a G4 and was pretty excited becasue I thought that was an awesome phone.You guys helped me root the image,as no pre-root image for my model was there.I am very greatful for that.
So my phone just went to hell (bootloop),I stumbled around the internet,a few fixes here and there,but I think that the best one is disabling the 2 big cores.Thanks God I made a backup of the system image.
What I need your help in is,to help me edit the system image of my phone to disable cpu4 and cpu5 (I presume those are the faulty ones).Then over write my rooted system image in download mode so that I can run it with four cores for atleast a few days.
P.S Is what ever I said above even possible or am I doomed.Thank you.:crying:
Bey the way My model is h810o
Can someone tell my what just happened here?
My 7 year old son just gave me back my device and the screen is smaller than usual.
He can't remember doing such things and I can't reverse it. Have a look in the attachment.
Restart didn't help
try this
go-to SETTINGS - ADDITIONAL SETTINGS - ACCESSIBILITY - DISPLAY SIZE ... you can adjust the size from there if you are in miui
Found that already, didn't work.
Will try to restore a TWRP backup tonight, if I can't find anything else
Didn't work. Seems I have to do it the hard way and do a factory reset.
Edit: tried one thing before the hard reset. Changed the DPI from currently 404 to 440 and waaaaaaaaaaaaaay better now.
Tischbein said:
Didn't work. Seems I have to do it the hard way and do a factory reset.
Edit: tried one thing before the hard reset. Changed the DPI from currently 404 to 440 and waaaaaaaaaaaaaay better now.
Click to expand...
Click to collapse
In MIUI9 that is the default DPI value