System UI Crash after DPI Adjusting - LG V10 Q&A, Help & Troubleshooting

TLDR: My freshly rooted phone is completely unusable due to the System UI FC. Tried adjusting DPI back to 640 but getting "system/bin/wm[6] no found".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm in a pickle. Trying to avoid factory resetting, but I'm slowing starting to accept this fate.
Anything else I could try?
Thanks in advance.

R4NDR01D said:
TLDR: My freshly rooted phone is completely unusable due to the System UI FC. Tried adjusting DPI back to 640 but getting "system/bin/wm[6] no found".
I'm in a pickle. Trying to avoid factory resetting, but I'm slowing starting to accept this fate.
Anything else I could try?
Thanks in advance.
Click to expand...
Click to collapse
Hate to be that guy, but you should try searching. It's a known issue. Root has been available for V10s for a long time and now that it's available for a couple new versions there's a flood of threads and posts that could be avoided if people simply read through what others went through months ago.

R4NDR01D said:
TLDR: My freshly rooted phone is completely unusable due to the System UI FC. Tried adjusting DPI back to 640 but getting "system/bin/wm[6] no found".
I'm in a pickle. Trying to avoid factory resetting, but I'm slowing starting to accept this fate.
Anything else I could try?
Thanks in advance.
Click to expand...
Click to collapse
Check out this thread....good luck..
http://forum.xda-developers.com/showthread.php?p=64679305
D855
RUNNING:N&N 2.0 STOCK MM

If your system are crushed and you have H960A, just simply flash TOT u used for rooting, but remember to use upgrade option in LGUP Your Data will be saved and DPI will back to 640

Related

[Q] Resolution issues

I flashed this ROM yesterday and so far everything has been working great except for one little detail. A few applications are being stretched off the screen. The two I've noticed this on so far are the ROM OTA Updater and the market app Fishing Superstars.
I tried completely wiping everything and reflashing the ROM several times but it's never made any difference. I'm starting to get frustrated and considering trying another ROM (but I like everything else about this one). Does anyone have any ideas about how to fix this?
Here's a screenshot of what I'm talking about. I can't get the OTA Updater to come back up but it cuts off the "Accept" button so I can't ever do any OTA updates =/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What Rom are you using? The dpi maynot be set correctly for that app. It's more than likely a Rom issue.
Jsparta26 said:
What Rom are you using? The dpi maynot be set correctly for that app. It's more than likely a Rom issue.
Click to expand...
Click to collapse
I'm using SOS M | VER 2.6.1 found here. For reference, here is what the OTA updater (included in that ROM) looks like when I try to apply the ROM update.
179, chaimio
Anyone have any idea? I'd post this in the actual ROM thread but I don't have 10 posts yet =/

[Q] Screen discoloring and flickering after installing custom ROM

I've had this Galaxy Tap 10.1 for over a year now and this weekend I decided to install a custom ROM, first I tried CM10.1/SGT7, then tried CM10.1 nightlies, then went back to CM10.1/SGT7.
During this third install I noticed some screen discoloring and flickering. I thought it had something to do with the ROM (both are based on CM10.1 nightlies), so decided to try an rooted/deodexed ICS Stock ROM, but the same problem persisted.
So decided to go back to Stock Honeycomb by doing a factory reset via ODIN, hoping that everything could be fixed by going full original stock.
But it didn't, the screen discoloring and flickering continues even after the full factory reset.
Have anyone seen anything like this? Is there a way to fix this?
Below some photos
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(more photos here: http://imgur.com/a/muGHU)
Thanks!
your cable (what connects board to digitizer/display) most likely went bad (ocurred to someone else I know a few months back). surprised you still have a display.
send it back to samsung for replacement (or you can attempt to replace it yourself).
pershoot said:
your cable (what connects board to digitizer/display) most likely went bad (ocurred to someone else I know a few months back). surprised you still have a display.
send it back to samsung for replacement (or you can attempt to replace it yourself).
Click to expand...
Click to collapse
Thanks!
Being out of warranty (is over a year), this is something they can repair? I'm assuming I would have to pay for the parts and service.
Anyone else had this problem and how it was fixed?

[Q] brick? modem n/a

hello everybody.
Here is the story, a friend of mine tried to install a custom rom on its brand new galaxy s3 and messed all things up. He came to me and we installed back an original rom, but we got this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
for what I understand, he isn't able to make the modem work, and the camera maybe. He told me he have done "something" to the efs partition, so I thought he messed up that. But esf files are all there and it seems the phone still have a valid imei (353*********151).
We were unable to recover it so we restored everything, resetted the counter, and bring it to assistance for warranty. They told us that there is a crack in the main board and they have to change it
They also said that there is a problem with the screen and it has to be changed. But it seems fine to us!
They also told us that those operations are not covered by warranty, and we have to pay 270 euros!!
Now we are looking for an alternative solution. It sound strange to me that is a hardware problem, because it happened when my friend started to play with the OS. Any suggestion? anything we can try before changing the mainboard?
any help will be appreciated!!
this is factory mode, use search
Glebun said:
this is factory mode, use search
Click to expand...
Click to collapse
LOL
thank you!! I managed to fix it, saving 270 euros !!
XDA vs samsung assistance 3 - 0

I made a big mistake everything force close

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
every app keep force close I remove some bloatware I probably made a mistake on deleting stuff how can I fix this issue
lox2013 said:
how can I fix this issue[/QUOTE]
Reflash whole firmware via adb: [url]http://forum.xda-developers.com/moto-e-2015/general/guide-restore-moto-e-2015-stock-firmware-t3044936[/url]
Pro tip: Never delete apps you don't know, just freeze em. :)
Click to expand...
Click to collapse
Bazilli said:
Reflash whole firmware via adb: http://forum.xda-developers.com/mot...e-restore-moto-e-2015-stock-firmware-t3044936
Pro tip: Never delete apps you don't know, just freeze em.
Click to expand...
Click to collapse
I have boost mobile lte
Reflashing your ROM should only be done as a last resort. You can hard brick your device if you don't do it right or use an incompatible ROM. I stress this with all Moto E surnia varients because not all ROMs are available yet. Trust me.
For force close issues, make sure you have a TWRP recovery installed. Boot into it.
Under Advanced, select Fix Permissions. Allow to fix, should take less than 20 seconds.
Reboot
Most of the time this will solve your problem.
Otherwise, you can always try to reinstall the system apps you think might have caused the issue.
If you're not rooted boot into stock recovery, wipe cache, and do a factory reset. Or you can try through the settings, but I don't know if that will work.

Stupid mistake Firmware update bootloop (Flashed twrp too early)

Hi Guy's,
I think I may have made a really blooming stupid mistake. After re-flashing stock due to some funny errors in my rooted rom I attempted to enter the bootloader again and flash trwp without unlocking the bootloader. I had the same adb window open from my first root and cycled through the commands and simply pressed the wrong command
So I'm in the infamous yellow "lock the bootloader" problem wherein it simply boots me into the firmware update. I had tried to do my previous restore to stock with LGUP that was successful however it throws up an error now as I believe it doesn't like that I updated in the mean time from buggering my phone up. (see attached pic) I have also tried to use a kdz for the 10i found here from the forum to only have LGUP crash upon initiating usb connection at 3%.
I know of no way to go back at lock/unlock the bootloader and I do apologise for the inconvenience but any help or pointers would be greatly appreciated.
Thanks a million!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Problem solved
Solved the problem now feel free to close this thread
ChrisNelson93 said:
Solved the problem now feel free to close this thread
Click to expand...
Click to collapse
For future people in your situation. Care to give details on how you fixed issue?
Nick216ohio said:
For future people in your situation. Care to give details on how you fixed issue?
Click to expand...
Click to collapse
"LGUP crash upon initiating usb connection at 3%..."
Maybe replacing dll file solved crash problem of LGUP and he flashed the stock Rom.

Categories

Resources