• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help LG G2 Screen Freeze (blank screen) ??

Here are some pics:

xofdxk.jpg



dxgv29.jpg



sobeag.jpg


120pfs1.jpg
 
Ok, the blank screen in download mode doesn't concern me a great deal. I've seen it still work with a dark screen and the fact you're showing up in device manager as LGE AndroidNET USB Serial Port, then I would instead try to flash a F320k tot file. I would somewhat prefer to flash the F320L firmware instead but I can't find a tot for that and you said you were previously running F320K firmware anyway so if it worked then, it should work again no?


Download and install LG Flash Tool 1.8.6.52 to the root of your PC's C drive.

Download the megalock dll.
- Remove the existing megalock dll located at C:\LG\LGFlashTool and replace it with the new megalock dll you just downloaded.

Download the dll and tot file for your variant.
- The tot is zipped so unzip to reveal it.

Power off phone entirely. Place the phone into download mode by pressing volume up while at the same time plugging the charge cable into USB on PC. At this time the PC should recognize/install the device. Open device manager to check if it shows up as LGE AndroidNet for USB Serial Port (COM##) If the COM number is anything other than 41, which it probably will be...right click on it and choose properties, then go to port settings tab and click advanced. On the bottom choose COM41 and hit ok, then close out of properties.

Open LG Flash Tool.
- You may get a menu asking Korean ???? Choose that one hit OK.

Tick the "Select Manual Mode" checkbox on top then on the top DLL box choose the dll you download above (the one from the same site as the tot file), then in the S/W box click add and choose your tot file.

Then hit OK.

Now click the yellow arrow in the top left of the main window. It will prepare and may give a "milky way" error. Ignore it.

Now unplug your phone, power it off and then go back into download mode again, (volume up + plug into USB). It should immediately connect and start flashing.

It will restart around 80% or a little above (on Flash Tools software). At this time, you're done.

If it does not restart on its own, long press power to turn off/reboot phone.
 
Thanks, ill give it another go and post back.

BTW... when the phone is in download mode the lg logo stays on the screen and doesn't go blank.

Is the operator logo stored in the firmware or on another part of the phone?
 
Yeah I'm almost at a loss at this point. The factory reset should make no difference if you have already flashed that tot as it does the same thing only cleaner. I've never seen this set of circumstances.
 
Well, if its not working normally after a new LCD screen and a tot flash, I'm afraid I'd lean toward a memory issue or other hardware related problem.
 
I didn't think of a memory issue.

Its seems like the longer I leave the screen off, the longer I get to play with it before it freezes again.

It does seem strange that the tot reflash has fixed it to some extent, as if it was hardware then I wouldn't have thought a reflash would do anything at all.

Well idk, if you had a bunch of user apps trying to start post boot before, they will all be gone now since you flashed the tot. Should be back to a truly new out of the box state as it relates to the OS. The only apps on it would be anything that came preloaded. So in theory it could, and probably is running a little leaner now. That's what made me think memory actually. But it could be anything on the motherboard or daughterboard for that matter, but I'm not sure what is all housed on the latter. I'd guess it's nothing to do with that.

Could be a battery issue possibly? Seems not terribly likely but it does seem a little bit like a power management problem. As I say, it doesn't seem like the front runner for possible issues. Usually power is either there or it isn't.

As to your earlier question, it's not a bad recovery flash since right now you have all stock partitions returned to the phone, including stock recovery.
 
Assume one or both of you guys has tried updating your touch firmware via hidden menu settings. If you have that on your variant Inked, not sure.

@AMOCO, did your deal start after some sort of significant event or just out of the blue?
 
No,I think it has been doing it ever since I got the phone.
Wow, I assume you bought it used with no recourse to replace? Only having the screen on for a couple seconds before you have to turn it back off again seems like it'd be completely unusable.
 
Assume one or both of you guys has tried updating your touch firmware via hidden menu settings. If you have that on your variant Inked, not sure.

@AMOCO, did your deal start after some sort of significant event or just out of the blue?


I cant find that option in my hidden menu.

It seems like the more I do to this phone the better its getting.

Ive been playing with it now for 40 minutes and it hasn't froze.

What is the best recovery for this phone now?

I remember twrp was causing issues with the screen.
 
I got it new and free with 2 yr. contract,But it was only doing it when I had a lot of things open.Plus I have returned to stock from root about a week ago to get ready for Lollipop update in Jan. or Feb.
I had always thought it was a software glitch.Now I am not even sure its even doing it now.
 
I cant find that option in my hidden menu.

It seems like the more I do to this phone the better its getting.

Ive been playing with it now for 40 minutes and it hasn't froze.

What is the best recovery for this phone now?

I remember twrp was causing issues with the screen.

Those screen problems are gone but root, and more so recovery, have become a convoluted mess on this phone. Though I'll admit I have near zero knowledge of the 320 series, most every other variant require a downgraded aboot and patched kernel to retain the old Loki exploit. So it's a pain and a little more danger than usual. Google Autorec if you can't help yourself though, it's an installer which does all that via an apk. Again, not sure about support on your variant though. Same goes for root. Stump Root is probably the most likely to work right now, may or may not need to use the brute force option in that.

I've gone back to stock, rooted with a bump'd twrp but wouldn't recommend that setup for flashing roms as many won't be compatible. I just did it to get on the full KK bootstack and have a bailout option for adb if I have boot issues.
 
The last time I used autorec it didn't install well but maybe that's been fixed as well.

And for rooting, I find Iroot the best.

Can you believe that my phone is still working :)

It does seem to be getting a bit hot and the screen is a little glitchy but ill upload a vid to show you what I mean ;)
 
Cool. Yeah I don't think IORoot will work if you're on KK but it could be worth a shot. Again, the 320's aren't my forte. The may have allowed the exploit to remain. All the US carriers patched that.
 
Back
Top Bottom