Hello,
I'll try to keep it short.
Pretext:
LG G4, H815
Latest MM Build (I think 20g or something..it's the latest original stock software)
Rooted, Unlocked, XPosed, NO Android debugging enabled ( I'm an idiot )
Wanted to improve battery life, changed the resolution to 1080p via wm size 1080x1920.
-> Icons too big
Changed Density to 440 via wm density 440
Rebooted.
nothing works. Everything just crashes, cannot bring up LG Keyboard, process com.phone crashes constantly, cannot get into settings to activate Debugging, because it crashes. Basically every damn LG App crashes.
I can boot into TWRP without a problem.
I can boot into Android without a problem!
I cannot install Apps due to constant force closes of everything LG Related (even Settings)
I tried changing my build.prop and default.prop to
Code:
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
When I do that the whole thing bootloops...
Question: How can I reset density?
How can I FORCE enable Android debugging?
Hope it's not too long and greetings. All help appreciated ^^
Related
Hello all,
I'm running into an issue when trying to change the build.prop to 240DPI. I used rom toolbox and a couple other LCD density modder apps from the play store. Each one causes my phone to get stuck at the Samsung logo, doing a cache wipe allows it to load to the "Android is updating" screen then once complete reboots and gets stuck again in boot. I am using a stock debloated rom by Geo411m. I also loaded up some 240DPI modded apps to play nicely with the new DPI but havent gotten to test it. I am using the stock touchwiz launcher, so could that be the issue?
just an update I installed Apex launcher and then removed defaults for the launcher. Set the DPI in Rom Toolbox and rebooted. I was able to successfully reboot this time. Only issue I have now is that I use the PIN unlock for the phone while crashes soon as you being entering your PIN. So looks like another system restore for me..... :crying:
forgot to mention I wiped cache and also fixed permissions.... now waiting on the restore to try it all again..
Strange...boot loops would happen to me on my Note 1 when I changed the DPI manually (like through root explorer) but when I used ROM toolbox it would work fine. If you want 240 dpi, I would suggest using DAGr8's hybrid ROM. I was running it at 240dpi with no problems. You also have to flash his multi dpi fix zip though because some of the stock apps won't be formatted properly.
Hello,
I run CM 12..1 and update at almost every nightly. Every time, I change build.prop to set the dpi to 200 instead of 240; i figured out that there's an option for the default dpi in the latest versions so I set the dpi to 200.
But now, I've got a "Unfortunately, system ui has stopped working" popup which lead to an unusable device. I've done a factory reset and reinstalled the last CM version, redone a factory reset and installed a february version and flashed a stock ftf of android 4.3; only this allowed me to use the phone.
So, what can I do to go CM again? Thanks for your help !
Anyone?
Hello, after using LASER WOLF metod my lg g4 vs986 have bootloop problem.
((Enable all apps for dual window on LG G4 (new build prop, root required)) THAT IS THE TITLE OF THE YOUTUBE VIDEO.
I did everything what he say in the video without changing anything, and after restart the problem occurred.
(What is did is change one thing in buld.prop file with BUILDPROP EDITOR (persist.splitwindow.support_all) from false to true)
There is some way to go back to the original build.prop and resolve the bootloop problem?
I do not have any custom recovery installed, and the phone is rooted.
I do not want to format the device because I have an authentication application that if I deleted it, I will not be able to enter my account. (Battle.net Authenticator)
My android version is 5.0 Lollipop (Rooted)
look up flex window mod on play store. you now can root the latest firmware by unlocking the bootloader by UsU
JMLS15 said:
Hello, after using LASER WOLF metod my lg g4 vs986 have bootloop problem.
((Enable all apps for dual window on LG G4 (new build prop, root required)) THAT IS THE TITLE OF THE YOUTUBE VIDEO.
I did everything what he say in the video without changing anything, and after restart the problem occurred.
(What is did is change one thing in buld.prop file with BUILDPROP EDITOR (persist.splitwindow.support_all) from false to true)
There is some way to go back to the original build.prop and resolve the bootloop problem?
I do not have any custom recovery installed, and the phone is rooted.
I do not want to format the device because I have an authentication application that if I deleted it, I will not be able to enter my account. (Battle.net Authenticator)
My android version is 5.0 Lollipop (Rooted)
Click to expand...
Click to collapse
well just saw this, sorry that the method has caused you a problem, i haven't had this phone for awhile after i broke my phone, hope you was able to get it back up and going again
Thread closed at Op's request.
Thanks
SacredDeviL666.
Hello, when using (D855) stock rom and stock based rom (Fulmics 8), the phone freezes extremely after the account and apps are installed, I can't take any action, The system is not responding, the home screen is not responding errors, also the phone is unavailable when I put a screen lock it becomes, the password cannot be entered (I don't think it's hardware related as it works very well when using Lineage OS) Used when Nova Launcher is installed (no screen lock), but when you open the notification panel, vibrate the phone, the phone becomes unusable when the settings are in overview. This only happens when using stock and stock-based rom (Fulmics 8). Is there a solution?
Lineage OS is better and useful but I am getting some bugs (Wi-Fi low shooting, video recorder not working) so I want to use stock rom but my phone does not allow it
Hi,
Is there any way to keep DPI changed after reboot? I tried with and without root and it reverts back to default after reboot
I've had the same issue. Custom DPI works on stock Android and Samsung phones, but won't stick on OxygenOS.