[HELP] Several issues with a LG G2 D802 - Android Q&A, Help & Troubleshooting

(Feel free to move this thread to anywhere where it belongs, if it's an issue. And sorry for my non-native english).
Good night for everyone,
To make it short:
- I bought an LG G2 D802 from amazon.com (description says it's a factory unlocked phone).
- Tried to install a modified kitkat rom.
- The phone bricked into fastboot mode, but then I could repair the download mode and installed a Hong Kong (without noticing it and messed up the phone, because I'm form Venezuela and it went to a Locked state) stock firmware. But couldn't repair the recovery mode.
- When the phone booted it had an apparent screen calibration problem, where it doesn't respond accurately to touch, but going to the sensor->calibrate sensor option from settings menu didn't fix the problem at all. So I think it's something related to the Android system files (partitions maybe?) and not the settings or S/W at all.
- Installed an Open kitkat firmware hoping that it would fix the issue, but with no result. It correctly changed the S/W, but the screen problem persisted.
Some ideas that I have (but haven't found any propper methot to fix the phone) are:
1. If it applies: repairing the Android system files, to fix the touchscreen problem.
2. Rooting the phone and installing the best Recovery Mode to fix the phone.
3. Wiping the phone to blank.
4. Install a correct S/W from zero.
5. Hoping that it works
If it's possible doing it from a pc software or command line (connected to the phone obviously) I think it would be the easier solution, but don't know how to do it.
I would be really grateful with anyone who reads this and can help me fixing this...
Thanks.

Related

Screen freeze

Hi to all,
I have a strange problem with my p500.
Sometimes when the phone is in standby mode, the screen freezes and the touch screen does not work. after a few seconds (after pressing any key) the phone reboots itself and everything returns to normal
Does anyone have a similar problem?
What can i do for fix it?
Thanks
You may be facing the random sd card unmount issue (which sometimes results in rebooting of the phone).
LG has released a new firmware which addresses this issue (it worked for me ). Use the LG suite to update the firmware...
If you are the adventurous type then refer here http://forum.xda-developers.com/showthread.php?t=876447
Thanks for the answer,
I tried to update the firmware, but LG suite say that is already updated (v10a) .
My carrier is vodafone. It may be that different operators will have different versions of firmware? (I'm newbie here)

[Q] how to test touchscreen with adb

Hello, all ROM makers, developers, hackers and advanced users.
I have a problem and hope you can give me some good advice.
Here is my sad story
You can read the full description if you want. Or you can skip it - the main question in the end of this post..
I have bought a new Sony ericsson Live! with walkman (wt19i) phone during my newyear holydays in Prague. It seemd to be working fine.
It is from rev.3, manufacture date 11/49 (mounth/week)
When I came back home and started using it, I saw that after some inactivity period (about couple hours or maybe more) the touch screen, back and menu snsor buttons stops any responsing. Hardware buttons (home, volume, camera, walkman and power) are still working. The system also continues to work as usual, so I can turn it on (but can not slide to unlock), I can hear if somebody calls me (but can not answer). Alarms, notifications and all another functions are still working.
Once or twise it started to work again (by itself, without any actions by me) but after few time the problem repeated. I was very unhappy and sure it was a hardware problem (and of course the Czech warranty does not work in Russia), but now i'm not so sure.
The phone had 4.0.2.A.0.58 firmware (android 2.3.4) from the box. First of all I tried to install SE PC Companion software, connect phone with usb and make factory reset... touchscreen started to work! But soon I saw this problem again.
The next day a new update was released and installed it (firmware .62). My phone was working again, but with the same result after some time.
You shoud know, that simple softreset (or ejecting and inserting battery) has absolutesy no effect on problem. After system starts I can not even unlock it. But flashing a new (or even the same) firmware (with flash tool or SE PCC) makes touchscreen and buttons working for some time. Have no idea why, but installing ROM with CWM (even with full wipe) does not make touch working.
Then I tried to use another custom kernels and ROMs. I unlocked the bootloader with fastboot tool, flashed one of custom ROMs from this forum (pre-rooted and with CWM). Then tried to use CM7.2 ROM... then another kernel and another ROM. Official, official-based, totally unofficial. The problem was with me each time after couple hours
I thought it is because some troubles in lock screen. Tried to install "no lock" app, so my phone did not use lock... but after some time touch freezes in home screen.
I disabled screen off while charging in settings and tried to leave the phone "wired" for some time... actually it worked fine all the time, and when I dicsonnected it it was still working... for couple hours.
I tried to install "no sleep" applications that does not allow CPU and screen to suspend. But it have no influense.
I even flashed CM9.0 ICS (very) beta ROM with the same result.
If it is just hardware problem - why it solves (for some time, but solves) with flashing? If it is a software problem - why it doesnt solve with new kernels and ROMs? My brain is ready to explode.
Now I have only one last idea and ask you to help me.
The question is:
How can I use adb or adb shell comands to get more information about the problem with touch?
I saw there is some log (logcat, stderr) tools, debug tools. I saw working lsmod, dmesg and mount commands in shell.
I think I shoud get all this information when all is ok. And then get it again when touch stops working and then compare, is it a good idea?
Where exactly shoud I see? How to test or get some touch input device info with adb? Is there any item in /dev that i can explore? Or something in dmesg? Where are touch driver located and how can I check if it is working?
I have some basic linux and andriond skills, but have not enought expierence.
I very (VERY) hope somebody can give me any useful advice to continue solving the problem. Where to see, what to do?
Thank you
P.S.: and sorry for mistakes, of course. English is not my native language.
P.P.S.: i am not sure where is the best place for this question: here or in xperia subforums. But I decided that this question is not xperia-specific and can be useful for other people in future.
Anybody? I have Lenovo Yoga B6000 with touchscreen problem and will be good if anyone know how can i test TS through ADB or shell.

Solve Display init failures by Android update?

Dear Experts,
Months ago my 2y old XZU on 4.4.4 (6833, towel rooted, locked, CWM recovery) started to fail on init of LCD, when coming out of standby. LCD init not only fails when device gets waked up by "power" button, but also when power is applied (Dock connector or USB). So I guess in fact it is a firmware issue (not a defective power button or the like).
It gets worse and worse; when device is warm it sometimes needs 30 or more off/on cycles.
When LCD init fails, the screen either stays black (only backlight) or colored lines show up shortly and fade away. But in fact the device is running - only LCD is not working.
But when init is successful, the XZU can run nicely for hours (as navi).
I hope that a android FW update might help!?
Unfortunately OTA doesn't seem to work on routed devices even with still locked boot loader.
Is there a way to update directly to 5.1.1 available now? Is it possible to update in two steps?
I would not mind to loose root, but loosing the possibility to write to external SDCARD!
Any help/ideas? THANKS A LOT!
Thomas
Sounds like SOD, or Sleep Of Death. The Ultra had some issues with it back on Jelly Bean, but I hardly read about it being an issue on KitKat, but yeah, it's probably a software issue, so an update to 5.1.1 might just cure it. You have a couple of options here:
1. Update the official way by installing Sony's PC Companion app on your computer and updating it that way
2. Update it in a little less official way by updating it manually yourself with Flashtool on your computer
3. Update by flashing a customized version through a recovery system on your device (like CWM or TWRP)
I would personally update it through PC Companion if I were you, since I guess you're not that technical when it comes to flashing and troubleshooting things. PC Companion should notify you about the update as soon as you plug your Ultra to your computer. If it notifies you about the 5.0.2 update, then I guess you'll have to update to 5.0.2 first, and then you'll be able to update to 5.1.
Flashtool allows you to manually download a FTF, or the ROM file from XDA and then flash it yourself. It's a lot quicker than PC Companion, but also a lot more complicated for people who haven't used it before.
Flashing through a recovery is mainly for people who already are used to flashing and stuff like that, and know what they're (mostly) doing.
Any other questions?
Thanks for your very valuable hints!!!
I'm really curious if it will work with PC comp (vs. OTA) and if I will loose write access to SDRAM (introduced in Android 4.4 and regained by root and SDFix).
Currently the download is running..
Will post results
zamzon said:
Thanks for your very valuable hints!!!
I'm really curious if it will work with PC comp (vs. OTA) and if I will loose write access to SDRAM (introduced in Android 4.4 and regained by root and SDFix).
Currently the download is running..
Will post results
Click to expand...
Click to collapse
The OTA will only tell you to connect to the computer to update. And regarding SD-card, that won't be an issue. Android will ask you to grant permission to the SD-card in some cases, but I haven't had any issues with it. Most if not all file explorers works just fine, and you won't experience any issues with the SD-card.
The update worked (no error on PC), but device seemed dead afterwads
After a reset and numerous power off/on cycles, the LCD init worked and I could see the result. :laugh:
Root was gone, of course. Recovery system and write access to SDCARD, too. Therefore Sygic app (navi), which had been moved to ext. SDCard. could not run anymore and moved itself to .android again.
But worst of all: the init of LCD now works even more seldom!
It does not even work when device has been shut down before, cooled down and is then switched on.
As far as I read, the SOD is different, cause my device in fact is "awake". It runs fine - only LCD is not working and not displaying anything.
I have no idea how to fix this. I can not imagine any hardware defect, causing such behavior (and I designed embeded systems with gfx controllers, myself).
Thomas
zamzon said:
The update worked (no error on PC), but device seemed dead afterwads
After a reset and numerous power off/on cycles, the LCD init worked and I could see the result. :laugh:
Root was gone, of course. Recovery system and write access to SDCARD, too. Therefore Sygic app (navi), which had been moved to ext. SDCard. could not run anymore and moved itself to .android again.
But worst of all: the init of LCD now works even more seldom!
It does not even work when device has been shut down before, cooled down and is then switched on.
As far as I read, the SOD is different, cause my device in fact is "awake". It runs fine - only LCD is not working and not displaying anything.
I have no idea how to fix this. I can not imagine any hardware defect, causing such behavior (and I designed embeded systems with gfx controllers, myself).
Thomas
Click to expand...
Click to collapse
But that does sound like a hardware issue. The final thing you can do, before you'll have to send it in for repairs, or get a new device, is to do a full factory resetting and see if that finally helps. You just updated now, but there's still a lot of crap left over from the previous version, that might screw things up.
So my advice would be to do a wipe, check if it help, and if not either send it in for repairs or get a new device. It's not a software issue if the issue travels over several OS versions with you. It may be a faulty display connector.

unresponsive touch screen on unroot phone after reinstalling original rom

the phone is a Homtom Zoji z6 which so far seems to not have many root'ing options available and I have been trying to root it but failed and quit trying so I reinstalled the original rom, which is not a backup or anything, just a rom from the homtom website which should work fine
the main problems are:
- unrooted phone with no custom bootloader installed which means no cache or dalvik reset
- phone just got a fresh installed rom and no usb debugging or oem unlocked, therefore stuck on the launguage select menu of android's first time boot
- unresponsive touchscreen, cannot use touchscreen at all (not sure about home, return and option buttons as I don't think that they do anything at the language select screen)
- non removable battery, removable by unscrewing the phone and removing back cover though at least 3 sensors can be seen inside which may be the most likely reason for the unresponsive touchscreen
- otg to usb female adapter unavailable (been trying to ask friends and find a place to buy one but so far no luck besides buying online which would take more time that I would like to spend on this)
- chinese factory menu (fml), also! ...got into this menu a few times but it doesn't seem to be working anymore, no idea why
- I want my phone back, dammit!
been trying to find some kind of software for pc that could redirect a usb mouse to android without root but apparently there is none or I'm looking in the wrong places
already tried to use the touchscreen calibration from the chinese factory menu but don't think it's detecting at all, factory reset doesn't work either
I'm all ears to suggestions

Nokia 7.1 constantly restarting (possibly after the upgrade to Pie)

Hello!
My dad was using Nokia 7.1 for a while but recently he asked for help with his phone which is constanlty restarting... Looking into other threads, I can see it is kind of known problem, so I hope you can help me somehow. The phone is running now on 00WW_3_51F. He doesn't remember what was recently done with the phone but I guess he simply updated it do Android 9.0... When I power on the phone, it boots correctly but restarts after few seconds (sometimes it's longer, up to 1 minute).
- I have already reseted phone to factory default but problem remained.
- I have tried to boot it in safe mode but same problem occurred.
I managed to access Settings>Advanced>Updates and noticed that there is an update available (V3.54H) with size 1299.4 MB. When I started to download it, phone crashed...
I was able to download V3.54H OTA from another thread in this forum with size 119MB (pretty weird...) and I am wondering if there is any chance to update it manually from SD Card or Fastboot. Assuming there is V3.51F version installed, can I simply execute command fastboot update update.zip in fastboot? Will it install only this patch to exisiting OS or replace it?
Do you have any other ideas how to fix it?
Thanks!

Categories

Resources