Related
Hi everyone,
I've had my Desire Z for little over 2 years now and two months ago (was running CM7.2 at the time) I started getting a weird issue where my touchscreen would only be responsive when the keyboard was slid out (so the opposite problem of what quite a few other people have reported where the touchscreen becomes unresponsive when the keyboard is out). The status LED would also stay off whenever the keyboard was closed, and the keyboard backlight didn't come on anymore at all. Also, I had to make sure that the keyboard was slid out during boot, if the phone booted without the keyboard out the screen would not become responsive at all until after another reboot. My earpiece speaker stopped working around the same time so I was wondering whether it was just an issue with the flex cable becoming a bit loose, but the touchscreen would consistently start working again when I flipped the keyboard out, and also the physical scroll button on the top bit would always work, so I was still hoping it would be some weird software issue.
I then upgraded to Flinny's (amazing) Andromadus ROM (build 22, complete data+dalvik wipe) after which the keyboard backlight started working again, but the rest remained pretty much the same. Since then the touchscreen issues have been getting worse, so that I sometimes have to flip the keyboard in and out again a few times, or turn the screen on or off with the power button several times before it becomes responsive again, but then it tends to work fine until I lock the screen again, with no noticeable dead spots anywhere on the screen. I've had days where it worked all day without problems (except having to flip out the keyboard, that's been a constant for the past two months), and then today I haven't been able to get the screen to do anything at all even after dozens of reboots.
I've already bought a new digitizer and am all ready to put it in (I'll have to replace the broken earpiece anyway), but was wondering whether anyone has any thoughts on whether it could still be a software issue after all, or if anyone has experienced anything similar? The thing with having to flip the keyboard out to get not only the touchscreen but also the status LED to work is just so weird and makes me doubt that it's a pure broken digitizer or lose flex cable issue, so I'm wondering whether it would be better to first try reverting to a stock ROM before taking on the messy sticky glue stuff (I should be fine but still, never done it before)?
Many thanks!
From what you describe my best guess would be the main flex cable is what needs to be replaced. Flash a touch based recovery and see if you have the issue there as well, if so its very unlikely that its anything but a hardware fault
Sent from my Nexus 4 using Tapatalk 2
Thanks for the heads-up, I've been playing around a bit more with software and I do manage to get the screen working again occasionally, typically after the second boot into a newly flashed ROM or restoring a backup, and only until one or two reboots later when it becomes completely unresponsive again. I've tried CM 7.2.0 as well as Flinny's Andromadus 10, and it is only complete flashing that does the trick, cache wipe or factory reset alone does nothing. The two occasions where the touchscreen worked were still limited to when the keyboard was flipped out, and it also had to be flipped out during boot, otherwise nothing would work. I've learned to navigate my way around the phone by just using the hardware navigation button, but I'll have a close look at the flex cable when I take it apart to replace the earpiece speaker tonight...
Hello,
so I took my dear phone apart yesterday to replace the broken earpiece - everything went fine but after reassembly the replacement earpiece isn't working either, which leads me to think that all those little broken bits might actually be related to some contacts being a bit lose, all in the same region. Should've thought about that earlier really since the earpiece and the LED (only works when keyboard flipped out) are both in that top region that the digitiser data presumable also has to run through before passing through the flex cable.
In any case, I also took a picture of the flex cable which is slightly bent but doesn't seem straightforwardly damaged (see attachment, that thing on the right is *not* a rip). Think it's worth trying to replace it anyway?
What was truly bizarre is that after the first boot following reassembly the touchscreen worked quite consistently for the entire evening - I thought I might've fixed a lose contact by un- and replugging the digitiser cable, but then the screen went nonreactive again at some point. I wonder if the working screen was again actually related to some software reset caused by the battery being taken out for so long? In the meantime the actual screen and trackball are still working away perfectly. Bizarre.
Just to let people know the solution to the mystery: the increasingly odd behaviour was actually caused by an initially small rip in the flex ribbon cable that got bigger and bigger - it's actually half-visible in the picture I uploaded above, only that the rip is where the cable comes out from underneath the case, and not where it's wrinkled!
Just in case it could be useful for anyone, here's the (top half of phone) components in the order in which they failed on me, which I guess corresponds to the order of the respective data lines in the ribbon cable (from the top of the phone towards the center):
environment brightness sensor (I thought that the sensor had been broken for almost a year, but as soon as I rebooted with the new flex cable I noticed how my phone stopped shining into my face at full brightness - if your brightness sensor gets stuck reporting the same (low) value this means your flex cable is on its way out!)
earpiece speaker
status led
touchscreen
screen (non-alignment with edge of screen, visual artefacts)
screen (fade to black/power interrupt)
obstacle3 said:
Just to let people know the solution to the mystery: the increasingly odd behaviour was actually caused by an initially small rip in the flex ribbon cable that got bigger and bigger - it's actually half-visible in the picture I uploaded above, only that the rip is where the cable comes out from underneath the case, and not where it's wrinkled!
Just in case it could be useful for anyone, here's the (top half of phone) components in the order in which they failed on me, which I guess corresponds to the order of the respective data lines in the ribbon cable (from the top of the phone towards the center):
environment brightness sensor (I thought that the sensor had been broken for almost a year, but as soon as I rebooted with the new flex cable I noticed how my phone stopped shining into my face at full brightness - if your brightness sensor gets stuck reporting the same (low) value this means your flex cable is on its way out!)
earpiece speaker
status led
touchscreen
screen (non-alignment with edge of screen, visual artefacts)
screen (fade to black/power interrupt)
Click to expand...
Click to collapse
I'll for sure keep that in mind. Mine is still going strong for the time being, but it's good to know some warning signs if I need to replace parts or if it's time to get a new phone
fireball0093 said:
I'll for sure keep that in mind. Mine is still going strong for the time being, but it's good to know some warning signs if I need to replace parts or if it's time to get a new phone
Click to expand...
Click to collapse
Replacement parts all the way, the repair was 15$ and it feels as good as new! Well, it could do with a new battery but that's just another 5..
Just realised that the proximity sensor should actually be added to the very top of the list - just noticed that faint red light when taking a phone call, don't remember seeing that in almost a year :]
obstacle3 said:
Replacement parts all the way, the repair was 15$ and it feels as good as new! Well, it could do with a new battery but that's just another 5..
Just realised that the proximity sensor should actually be added to the very top of the list - just noticed that faint red light when taking a phone call, don't remember seeing that in almost a year :]
Click to expand...
Click to collapse
That's not a bad cost at all. I know I'm going to have to replace my keyboard in probably 2 months or so (maybe sooner) because some buttons are starting to not work. Other than that fact my phone is currently still going strong for being going on a 3 and a half year old phone
Moved from General:
I made an attempt to replace my cracked Silver Bezel on my T999L that I purchased from eBay, (http://www.ebay.com/itm/400733714927?_trksid=p2059210.m2749.l2649&ssPageName=STRK:MEBIDX:IT)
I realized that I did not have the proper tools to complete the replacement due not having a Heat Gun to remove the Screen from the Silver Bezel which is quite literally in the middle of the phone.. I caused no visible damage, I gently removed the connectors, and the mother board, the camera and the light sensor with ease, photographing every single step so I remembered where each went where.. It was very simple, and I just realized I couldn't go any further.... Upon putting everything back together, I made a call, played some music, tested everything out and it looked ok....Until I tried to rotate it.. The phone will not rotate into Landscape unless I use an App to force it.. I tried calibrating the G sensor, but it sits in the center not moving, like there was no sensor at all.. Other than the G Sensor, the phone works perfectly..
What am I missing, and what can I do to repair this?
I have tried going into Download mode, and then pulling the battery for 30 mins,
I have also tried a factory reset, that didn't work.. I pulled it apart again to double check on the connections, all seated properly in place, nothing looks out of whack.. I have looked at about a Dozen Youtube videos and tear downs, and I used the proper pry tools, all looks good on the inside..
I'm about to flash VIA Oden the Stock 4.3 rom in hopes that may correct the issue, but I doubt that will do anything different.. What am I missing here?
Suggestions would be greatly appreciated.. The phone works just as it did, Except the Rotation..
I am wondering is my using a slightly magnetized mini screw driver may be the culprit, that causes the sensor not to work..
I flashed to the latest Version of Stock Jelly Bean, ran another Factory reset.. used a couple of calibration apps.. and Zippo..
I see this is a difficult or not answerable question, but where is the Rotating/Gyro Sensor located on the mother board?
I'm wondering if I can get a replacement board and install it..
Suggestions are always helpful..
Dear community.
A few weeks ago I rooted my LG G3 and installed Fulmics 6.0.
Everything went as planned and worked seemlessly.
Today, while watching YT-videos my device turned off and tried to reeboot. After the first, non-animated LG screen, the blue screen appeared.
Same to say while trying to boot into TWRP recovery. After the blue TeamWin Startscreen, the blue screen shows up again. :crying:
Is there any help left?
Kind regards
Thomas
My friend also happen problem
He asked people to help take
Finally, open the motherboard
Then take heat
That seems to be a common problem LG G3
Welding where welding is not good
PS. I use google translate
hi guys, i had the same problem now for 2 days searching the forums for any sign of hope even ringing lg them selves to for them to tell me the repairs will cost more than the phone
so i new at this point i had nothing to lose.. after playing around for 13 hours with my phone i have got it all up and running at the minute for a full day an not once gone off so i might be the lucky one buts its worth a shot
this is what i did.
disassembled my lg g3 and took out the logic board
took off both heat i/o sheilds from the i/o
with a fine tooth brush and some contact cleaner (ipa 90%) i cleaned the main part of the board and let it dry out half hour
i then applied hot air onto the board both sides and let the contacts reseat them selves and the put phone back together (make sure you out the i/o shields back on)
i then tried resetting my phone with lg flash tools and the correct fireware for my phone
(when you are cleaning your phone there is a little sticker on the chip stating what firmware you phone came with, find this firm where as you know it will work)
anyways it didnt work for some random reason so i tried lg flash tools 2014 (i will link everything below).
so when i found the correctish .kdz file i flash the firmware making sure everything went
and for the first time it went to 100% first time.
played with my phone for a while all seamed ok wasnt the standard firmware what was on when cam out the factory.
so i then tried lg flash tools again with the correct firmware and it worked spot-on and has never played up are missed a beat since....
everything i used:
lg flash tools 2014= http://forum.xda-developers.com/showthread.php?t=2797190
lg flash-tools and lg drivers= http://lg-firmware-rom.com/lg-tools-software/lg-flash-tools-flashing-lg-tot-stock-firmware/
firmware's = http://storagecow.eu/index.php?dir=Xda/LG+G3/Stock/D855/
Novamatic Mike said:
hi guys, i had the same problem now for 2 days searching the forums for any sign of hope even ringing lg them selves to for them to tell me the repairs will cost more than the phone
so i new at this point i had nothing to lose.. after playing around for 13 hours with my phone i have got it all up and running at the minute for a full day an not once gone off so i might be the lucky one buts its worth a shot
this is what i did.
disassembled my lg g3 and took out the logic board
took off both heat i/o sheilds from the i/o
with a fine tooth brush and some contact cleaner (ipa 90%) i cleaned the main part of the board and let it dry out half hour
i then applied hot air onto the board both sides and let the contacts reseat them selves and the put phone back together (make sure you out the i/o shields back on)
i then tried resetting my phone with lg flash tools and the correct fireware for my phone
(when you are cleaning your phone there is a little sticker on the chip stating what firmware you phone came with, find this firm where as you know it will work)
anyways it didnt work for some random reason so i tried lg flash tools 2014 (i will link everything below).
so when i found the correctish .kdz file i flash the firmware making sure everything went
and for the first time it went to 100% first time.
played with my phone for a while all seamed ok wasnt the standard firmware what was on when cam out the factory.
so i then tried lg flash tools again with the correct firmware and it worked spot-on and has never played up are missed a beat since....
everything i used:
lg flash tools 2014= http://forum.xda-developers.com/showthread.php?t=2797190
lg flash-tools and lg drivers= http://lg-firmware-rom.com/lg-tools-software/lg-flash-tools-flashing-lg-tot-stock-firmware/
firmware's = http://storagecow.eu/index.php?dir=Xda/LG+G3/Stock/D855/
Click to expand...
Click to collapse
Just an quick update the phone is still working like a dream. Also upgraded to lasted OS. So this could of been a lucky fix or just a bad section in software.
Sent from my LG-D855 using XDA-Developers mobile app
I actually just got this yesterday, and fixed it. It started blue-screening and rebooting sporadically but quickly got to the point where I'd turn the phone on and it would blue-screen and shut off after two seconds. I could still hold Vol Down and power to get into the STOCK system recovery screen, and by choosing Safe mode (Factory data reset went to blue-screen) it went into TWRP. I tried a whole bunch of different things (and luckily was able to get a backup of the internal storage to my SD card) before doing a full wipe. FULL wipe. I then flashed the stock image via KDZ which is where I sit right now. No blue-screens. I had been on Jasmine 9.1 and Skydragon kernel, I'm thinking maybe a recent update didn't play nicely with either of those, or maybe some other custom firmwares too.
I also got this and somehow i manage to resurrect the phone. I was installing another stock-based ROM (Zoe ROM 3.0 - based on V30N) and after setup my phone got a blue screen. I unplugged the battery, i tried to start it again but only showed LG logo for one second, and after that was dead. I mean, completely dead. No power, no charging, no PC detection, nada!
What I've done:
1. disassembled the phone and pull out the motherboard (G3 is really easy to disassemble, really);
2. open the protective cover near the CPU/Memory (it's a weak metal cover, easy to pull down);
3. i wiped gently with a toothbrush and alcohol all the components (i put a lot of medicinal alcohol);
4. i used a hair drawer (hot) to clean the excess of alcohol and to heat the CPU zone (about 1-2 min);
5. i assembled all back together and i prayed to God (no joke, believe it or not);
6. after that i pressed the power button + vol- (to enter recovery) ... and surprise, it's alive;
7. i restored a anterior software backup, just in case... (now i use Zoe ROM 2.7 based on V30J);
Now it's working for about ~4 hrs and no problem at all... i will edit this if something is happening.
Good look! And pray... sometime it really helps.
FusionGFX said:
Dear community.
A few weeks ago I rooted my LG G3 and installed Fulmics 6.0.
Everything went as planned and worked seemlessly.
Today, while watching YT-videos my device turned off and tried to reeboot. After the first, non-animated LG screen, the blue screen appeared.
Same to say while trying to boot into TWRP recovery. After the blue TeamWin Startscreen, the blue screen shows up again. :crying:
Is there any help left?
Kind regards
Thomas
Click to expand...
Click to collapse
I'd suggest flashing an original factory image and re-rooting / re-installing TWRP.
Worked for me also !!! Without praying
Novamatic Mike said:
hi guys, i had the same problem now for 2 days searching the forums for any sign of hope even ringing lg them selves to for them to tell me the repairs will cost more than the phone
so i new at this point i had nothing to lose.. after playing around for 13 hours with my phone i have got it all up and running at the minute for a full day an not once gone off so i might be the lucky one buts its worth a shot
this is what i did.
disassembled my lg g3 and took out the logic board
took off both heat i/o sheilds from the i/o
with a fine tooth brush and some contact cleaner (ipa 90%) i cleaned the main part of the board and let it dry out half hour
i then applied hot air onto the board both sides and let the contacts reseat them selves and the put phone back together (make sure you out the i/o shields back on)
Click to expand...
Click to collapse
This worked for me! Didn't even need to reset the OS. My wife's G3 shut down on her one day. I started trying to fix it, but couldn't get past it showing blue screen, boot looping, and then going dead to the point where it wouldn't even boot to the flash recovery screen. I couldn't even get it to turn on at all until I took the battery out and held the power button down for 20 sec.
Then I read this post, removed the circuit board and shields on both sides, blow dried on hot/low setting for about 7 min each side, and let it cool off for about 10 min, then re-assembled everything. First boot it went right to the PIN lock screen like normal. So far so good it's been running for about 30 min no issues. Thank you!
Glad it's working mate I got my phone to my little one now and still going strong it did have a little TIFF a few weeks ago with not even turning on but left on charge for a day as for some reason the battery drained that much it couldn't even charge so yeah
Yeah just did a drop test and smacked it around a little, so far so good still going...
I have a solution to this problem.
When you disassembly phone and remove protective cover (from processor site) remove little battery from motherboard - near to processor.
Thats all. G3 is back to live (at least mine)
The bsod happened to me as well. After trying everything, flash stock firmware, boot to recovery and wipe data, cache etc and nothing worked. I then disassembled the phone and put the motherboard in the oven at 180degree for 10 minutes. So far so good, it booted up fine and it's working pretty well till now. Flahed v30b version and it's working since 10 hours. Will report back how long it stay alive eheh
Sent from my LG-D855 using XDA Labs
Looks like this disassambling things really works cuz i read so many places and heard from friends that it works.
But really strange why it suddenly started this problem on everybody
I solved the problem by putting CPU limit. It is not a good solution while your phone works as half of its potantial but it works. Maybe one day i will bake it too
Here's another proof that the heatgun solution seems to work.
My G3 was randomly crashing from time to time over last month but the bluescreen appeared for the first time today. Since then it didn't make it past the LG logo before it would turn blue and shut itself of. So same problem as described above.
I took it apart and took of the metal "heatspreaders" from the motherboard, then heatgunned it from both sides for like two minutes each (with waving the heatgun around so I wouldn't burn the entire thing ), let it cool down a little and reassembled it.
I then just powered it up normally and it works just fine.
I'll update you in a few days.
KaiTech96 said:
Here's another proof that the heatgun solution seems to work.
Click to expand...
Click to collapse
Yeah, it works, in most cases. The question is - for how long... You may be lucky, and it could be a permanent fix for you. However, the nature of the issue is a manufacturing defect which can only be fixed for sure by reballing the chip (or by just replacing the whole board). Going a bit deeper into technical details, the chip in question is a BGA type (Ball Grid Array). It means that it doesn't have traditional leads for soldering on the board (the ones that are either sticking out or just located on the sides). Instead, it has soldering pads on the underside, and the soldering is done by putting a pre-arranged set of solder balls (hence the name), and the flux on the pads, and then heating up the assembly until it melts. A flaw in preparation or in the soldering process itself results in a bad contact on some pads which usually manifests itself either after the chip and board heat up under load, or when the board is physically deformed even a tiny bit (hit or dropped), or just after some deterioration/oxidation over time...
Sorry for the nerdy stuff, I am done now... Basically, consider the heatgun trick to be about the same as banging on the side of the old tube TV trying to fix the static on the screen...
I do not know whether this counts as ghost touch or not, but randomly there is a persistent touch on the bottom right corner of my Zenfone 2, ZE551ML. If i Lock the device and unlock it back again, (Through the power button), the issue goes away. It re appears after a while again.
I saw videos of people facing such issues on youtube, but in their cases, the entire touch automatically starts to act up. whereas in my case, this happens only if i start using the phone. And that too on the same area ( Bottom Right, Just over the Recents Button)
I wiped the screen / Scratch guard thoroughly. I even changed my scratch guard. but still the issue stays.
Im on Stock 183 (Not yet updated to 184).
Is this a hardware issue or a software one?
(My warranty just ended yesterday).
I feel this is software, because the touch works normally if i lock the device and then unlock it back.
Just for the record, my device passed the SMMI touch and multi touch test without issues.
Also i enabled the graph option under developer options. And i do not see any touch being registered under normal course.
But then when all the tools are off, randomly the issue just pops up again.
Does anyone have such issues?
Does CM or other Non-stock ROM solve this??
I actually a similar issue a month ago, which I thought was a software thing (completely wiped my phone, then installed latest XOSP) or me losing my mind, and it turns out it was neither.
It came back yesterday, and I learned that there's entirely a chance that the screen connectors are loose. Simply remove the back panel (the one with the screws, you'll need one of those eyeglass-repair screwdrivers) and press down on the connectors to make sure they're 100% snapped in and the issue should stop!
Also, see if Glove mode fixes it, since I know that works for a lot of people.
I had the problem. I just removed back cover and plugged a bit more the connectors that you can see when removing battery cover.
Its been 3 months without the problem.
gREENNNNN said:
I had the problem. I just removed back cover and plugged a bit more the connectors that you can see when removing battery cover.
Its been 3 months without the problem.
Click to expand...
Click to collapse
Kavka.V said:
I actually a similar issue a month ago, which I thought was a software thing (completely wiped my phone, then installed latest XOSP) or me losing my mind, and it turns out it was neither.
It came back yesterday, and I learned that there's entirely a chance that the screen connectors are loose. Simply remove the back panel (the one with the screws, you'll need one of those eyeglass-repair screwdrivers) and press down on the connectors to make sure they're 100% snapped in and the issue should stop!
Also, see if Glove mode fixes it, since I know that works for a lot of people.
Click to expand...
Click to collapse
Okay so
My issue is because of my flip cover.
I knew this wasn't hardware, coz the issue was only on one small area of the screen.
I did the following:
When there was ghost random touch.
I immediately removed my flip cover, and the issue went off
Did It twice, both times, it worked.
Thanks anyways.
Sent from my ASUS_Z00AD using XDA-Developers mobile app
Hi and thank you for checking my thread
I have a problem with my G3 as described in the tittle, I did the Paper trick I saw on YouTube but sadly it didn't work
After a while I found out that placing a piece cut from Credit card under the CPU might work and I did , but one week later I had the same problem, likely I can just click sleep button and it returns to normal
After these many problems I decided to give up on it and sell it, but I need a permanent Fix so I don't get involved in Cheating
Also , does replacing motherboard will fix the issue ?
Does G4 Worth it now ? I know about bootloop problem
Probably is a bad motherboard
When my G3 finally died (digitizer went bad), I just replaced it with a used G4 for $150. That was like 6 months ago. The phone has been phenomenal. I know there is many who say that every G4 will bootloop eventually, but I really don't see how thats possible if you just browse google for the issue. Yeah, a lot of people had the problem, but if everyone did you wouldn't see the G4 still being sold at a ton of outlets, and you would see hundreds of links to the issue. I think there was a large batch of them that were bad... and they got past QC, but the vast majority of them are probably fine.
resinis said:
Probably is a bad motherboard
When my G3 finally died (digitizer went bad), I just replaced it with a used G4 for $150. That was like 6 months ago. The phone has been phenomenal. I know there is many who say that every G4 will bootloop eventually, but I really don't see how thats possible if you just browse google for the issue. Yeah, a lot of people had the problem, but if everyone did you wouldn't see the G4 still being sold at a ton of outlets, and you would see hundreds of links to the issue. I think there was a large batch of them that were bad... and they got past QC, but the vast majority of them are probably fine.
Click to expand...
Click to collapse
Replacing the Motherboard will fix the issue ?
Yea, i saw "1 month/year after" Reviews on youtube and no one montion the bootloop issue, people ask them in comments and they reply that the phone works normal with no issues
Thank you for replying dude appreciate it
I was skeptical at first, but by baking the motherboard in the oven did the trick for me. It has been a couple of hours now an no flickering, no black screen and no troubles. And i know i'm asking for Murphy to come and bite my as*, but as a little trick, i'd like to suggest before putting the mobo in the oven to try something: i have an old Akasa X4 cpu cooler which has metal fins which are removable. I took one of those things and cut a square a little bit smaller than the power IC to the right of the SoC and then cut another one the exact same size then stacked the two one on top of each other, making sure to not short any capacitor around the IC and then put the metal shield back, making sure to put pressure on the IC. Then preheated the oven at roughly 180 degrees celsius, then put the motherboard SoC face up into the preheated oven on three balls of aluminium foil, one at the bottom near the micro usb, and the others to balance the motherboard, like a BMW Isetta, and put the timer for 10 minutes. After these nervous 10 minutes, I took out the mobo and let it to cool at room temperature for ~30 minutes. And voila, now it works. I do hope that it is going to last, and i will be very careful with this phone, unlike the previous owner. Seriously, how can you put a freaking button (small one, from a shirt) between the SoC and the mid-frame? Crazy. And that's why i got it for ~8000 JPY (about 70 bucks).
Takadi said:
Hi and thank you for checking my thread
I have a problem with my G3 as described in the tittle, I did the Paper trick I saw on YouTube but sadly it didn't work
After a while I found out that placing a piece cut from Credit card under the CPU might work and I did , but one week later I had the same problem, likely I can just click sleep button and it returns to normal
After these many problems I decided to give up on it and sell it, but I need a permanent Fix so I don't get involved in Cheating
Also , does replacing motherboard will fix the issue ?
Does G4 Worth it now ? I know about bootloop problem
Click to expand...
Click to collapse
I had a similar problem for about two months. I tried the paper thing over the camera sensor and I felt like it helped some but the problem still continued. The screen would just slowly go dark with vertical lines running through it. All apps would still work in the background while this was happening. I could boot to TWRP and this problem never happened while in TWRP which was odd. Seemed like if it was a screen issues or hardware malfunction it would happen all the time. That's when I decided to just flash back to stock. I was thinking about getting the S8 anyways so what the hell. I flashed to stock 10B and took every single OTA. Took all night but I've been running stock for over a day now and the issue has not replicated itself one time since reverting back to stock. I was on RR Nougat and Fulmics when it happened prior. Has to be a root or Rom issue?
Pozman1 said:
I had a similar problem for about two months. I tried the paper thing over the camera sensor and I felt like it helped some but the problem still continued. The screen would just slowly go dark with vertical lines running through it. All apps would still work in the background while this was happening. I could boot to TWRP and this problem never happened while in TWRP which was odd. Seemed like if it was a screen issues or hardware malfunction it would happen all the time. That's when I decided to just flash back to stock. I was thinking about getting the S8 anyways so what the hell. I flashed to stock 10B and took every single OTA. Took all night but I've been running stock for over a day now and the issue has not replicated itself one time since reverting back to stock. I was on RR Nougat and Fulmics when it happened prior. Has to be a root or Rom issue?
Click to expand...
Click to collapse
Just wondering if your G3 is still functioning without the issue.
It really feels like a hardware issue but as you pointed out it didn't happen in TWRP... but like many, I encounter the issue when the phone gets a bit warm (>35C), so maybe TWRP and your stock android is not as hot as RR Nougat? Then again, I'm on MM when this happened...
Update: Actually the flicker n fade happened to me in TWRP while I was backing up. The temperature read about 60C.
I had bigger problems with my g3 and they started as follows
Problem 1. camera not being detected and crashing. 2. Reboot once a while which got worse over time. 3. Bluetooth sketchy and WiFi not connecting. 4. Sd card being ejected and mounted constantly. 5. Mobile data stopped working.
Solution: baked it in the oven 10min with cpu side up at 185c removed to cool 4 30min. Problems gone for the meantime.
This morning at work my D852 died with the exact same screen fades to black and would only stay on for at most like 10 seconds and would only come on again after the processor cooled enough. I came across this youtube video.
https://www.youtube.com/watch?v=UF1s4RCZAvc
Since I didn't have any copper foil tape, I substituted with Aluminum foil tape and placed the tape in the same places as detailed in the video. (copper works better than aluminum for heat dispersal)
My phone is now back to normal and hasn't shown any issues with the past 5 hours since I applied the fix.
UPDATE: My phone has worked perfectly for several days now until I turned on the GPS from Cell Tower to High Accuracy and it immediately started to die again. Once it cooled down I was able to get to the settings screen to turn off GPS and it went back to functioning like normal
How to fix
I tried the paper trick and it did not work. No need to replace the motherboard or the phone. The issue is just a bad connection between the motherboard to the LCD display.. Probably due to dirt (in my case, I found that quite a few places in my motherboard had corrosion buildup). Here is the fix...
1. Remove battery cover and Unscrew The back plastic from the base of the phone to get to the motherboard.
2. Disconnect all the connectors from the motherboard.
3. Scan the motherboard for anything unusual. (My motherboard had corrosion on several different places).
5. Clean any dirt or corrosion with lint-free cloth. (I didn't have one so I had to use a Q-tip).
*if needed, Dip the cloth in rubbing alcohol to assist in cleaning. make sure that the cloth is JUST BARELY Damp and not dripping, otherwise you will risk water-damaging the phone. If you use rubbing alcohol, make sure that you dry the spot right after you wipe it.
6. Once you have cleaned the motherboard, check the base of the phone and clean any dirt from here also.
7. Replace the motherboard, re-connect the connections, screw on the back, and put the battery cover back on.
Viola! Mine has been working like new for 4 days so far with no issues...
Takadi said:
Hi and thank you for checking my thread
I have a problem with my G3 as described in the tittle, I did the Paper trick I saw on YouTube but sadly it didn't work
After a while I found out that placing a piece cut from Credit card under the CPU might work and I did , but one week later I had the same problem, likely I can just click sleep button and it returns to normal
After these many problems I decided to give up on it and sell it, but I need a permanent Fix so I don't get involved in Cheating
Also , does replacing motherboard will fix the issue ?
Does G4 Worth it now ? I know about bootloop problem
Click to expand...
Click to collapse
So a permanent fix is a new motherboard or a new screen?