Database Users

[Water Damage/Troubleshooting] Details inside,

Long time lurker, been behind the "scene" since 2011.
Well about 2 weeks ago I had my s6 e+ behind the shifter (automatic) in my maxima, put it into gear and the phone went right through a chick-fil-a lemonade cup :/ (styrofoam)
Didn't realize until I got home later that night what had happened, just kept on playing music no problem.
Long story short (heh short), it started acting stupid and phantom pressing multi-task over and over. Disabled multitask; still unaware of the water damage. Wouldn't charge, so I cleaned the charger out... nothing.
Then I realized there was a puddle of sticky liquid in the case. Took it out wiped everything down (99% Isopropyl) charged fine. 2 days later it stops charging completely nothing helped, decided to check in on my "protection plan" ofcourse accidental liquid damage isn't covered (So glad I pay monthly for this protection!)
Let it swim in alcohol for 20 minutes, dried out for a day. Worked great, no problems back to normal. Took a nap watching youtube, woke up to a fuzzy black screen quickly shut device off and ever since I've had noo image displayed. I have it taken apart right now, I tried another bath I tried letting it sit in silica pearls for a few days. Its very dry inside.
Phone comes on, long blue led on power, flashing blue led (missed notifications) all buttons work. Screen still registers touch but only directly in the middle.
- Dead LCD?
- Dead GPU?
- Dead phone?
Tl;DR ^
Any help/thoughts greatly appreciated

The S6 Edge + got a SAMOLED display. The LEDs inside of it are made out of an organic semiconducting material. I'm not absolutely sure, but I don't think they liked this highly concentrated alcohol that much...
The GPU is a module inside the Exynos SoC. If the GPU would be dead, the whole phone would be.

WerWolv said:
The S6 Edge + got a SAMOLED display. The LEDs inside of it are made out of an organic semiconducting material. I'm not absolutely sure, but I don't think they liked this highly concentrated alcohol that much...
The GPU is a module inside the Exynos SoC. If the GPU would be dead, the whole phone would be.
Click to expand...
Click to collapse
Ah, wasn't sure if it was built-in to the chip itself or running like older motherboards where the nb/sb has the gpu.
Wonder if it's worth spending $170 and chancing if it works or not. Knowing that the GPU is in the chip makes me believe that it is the display, the only reason I mentioned a gpu was because i've seeen similar things happen with liquid and a gpu
Thanks for your help, friend

Theory on Potential Partial Cure for Random Restarts/Freezing (Long Post)

First and foremost, I don't promise this will fix anything as it has only worked for myself, but let me share my experience/journey and see if this can help at least another person in the same boat as I am.
If you do not want to read the entire story, feel free to skip to the break below.
Back story:
I got the phone in Hong Kong back in November. It's a 505 H815TR. (Don't ask me why I ended up with a Turkish phone, I have no idea)
The phone worked fine for about two weeks, then it would one day start to restart randomly. It also started happening more and more frequent, and the phone might fail to boot at all.
Sometimes it would just freeze on a screen and there'll be artifacts like the GPU overheated. When that happens the phone wouldn't even respond to a hard power-off (holding power for 4 seconds+) and I'd have to take out the battery.
Unfortunately for me, I have since went overseas and LG would not honour the motherboard swap. I also didn't want to sell this otherwise great new phone to another unfortunate soul either. So I'm stuck with the few hundred bux worth of not-quite junk. Determined to not let the money go to waste, I still tried to use it as a daily driver but it had gotten so bad at one point that I had to keep taking the battery off and restarting every few minutes during a meeting like an idiot.
So I tried upgrading the firmware, in hopes that it'll at least improve the situation. It was the 20c firmware. I used LGUP to upgrade it and it got better, if only for a while.
I thought, hey it ran better! Maybe I can stick it out, and sucker up the less frequent restarts. It will run okay for a week or so with occasional restarts. Then it suddenly got bad one day I opened up Maps for navigation. It would suddenly go back to a few restarts an hour.
At this point my hypothesis is that apps/sensors that would require a hike in power can trigger the crash. (duh!) So I turned off Bluetooth/GPS/disable every other app that I can think of. While it help a BIT, it certainly did not alleviate the problem. It had only gotten worse as time goes.
A few weeks went by, 20d came around. Hoping situations would improve, I upgraded the phone.
The problem got WORSE. I thought that's weird, the new version should have came with optimizations and gave less work the phone - hence it should freeze less. Puzzled and disappointed, I flashed back to 20c and was prepared to bite the bullet and accept it as lost cause. To my surprise however, when 20c finished generating cache and booted up, things started looking better again. It would run a few DAYS without problems. I got even more confused. If the problem was purely triggered by spikes of load, going back to the old firmware should have little to no effect. Something else must be going on. Before long, the problems came back and I'm plagued by the restarts again.
I came up with 2 possible hypotheses:
1 - It had something to do with cache
2 - It had something to do with Doze optimizations
Number 2 was easy to test. I went to settings and ignored every possible optimization (****ty UI on that screen by the way. It takes forever to scroll to anything and the checkboxes don't save until you exit the menu. When a restart hits before I exit the menu all progress is lost and I had to start from beginning :crying: ). I ran for a few more days and it seemed to have little impact.
So I was fairly confident at one point that it had to do with cache. Unfortunately, the G4 (at least my G4) does not have an easy access to erasing cache (which was incredibly annoying LG!). The so-called stock recovery only has an option to wipe the phone and obviously I didn't want to do that. I also did not want to temper with bootloader for the same reasons aside from the risk of bricking the phone. I had remembered that when I upgraded the firmware the cache gets wiped and it'll be regenerated on first boot. So I thought I'll just flash the same firmware and I'll be done! To my demise, apparently flashing the same kdz does NOT trigger the cache generation process. What I had to do was to flash 20d, boot that, and flash 20c again.
Things started to look better here. It ran fine. It did not crash for about a week or so. I thought it was a fair compromise. I can deal with a quick refresh(flashing 20d and then 20c again) once a week. Whenever I see signs of the restarts, I would quickly refresh when I got home that evening and it will be good for a week or so. Here I was ready to finalize my theory until...
It crashed. Soon after one of my routine refresh. I thought this was interesting? If it had to do with some kind of cache buildup, surely it would not crash right after a refresh? What's weirder still was it stopped doing that after 2-3 times. Something ELSE MUST be contributing to this. What else was related to the process of cache generation that could affect the stability of my system?
Here ladies and gentlemen, is what my little pea brain have came up with, through trial and error, no engineering background, limited tech knowledge, and limited common-sense:
It had to do with the activity of the CPU; or more precisely, it may have to do with the extended heating process that caused some component around the area to change in some kind of state, and thus improving the stability for a duration until it gradually changes back with time.
Engineers are probably laughing at me right now. I know it probably makes no sense, but it's the best that I can come up with. So I come to you guys, maybe some may help shed some light on this issue that plagues those of us who are stuck with the problematic phones that are not eligible for exchanges/repairs.
Anyway, to test my theory out, I downloaded some kind of stress tester from Google Play (I used StabilityTest v2.7)
I would wait until the phone starts restarting again (and it will, and when it does happen the stability dropped SHARPLY, from no restarts to maybe 2-3 an hour).
Then, I would run StabilityTest. I chose the classic stability test, and just let it run.
The first time it ran, it did not survive the first 10-15 mins. The phone would restart, and I would try again.
This time it ran for 2 hours without restarting (double the time needed for generating cache twice on my phone). I manually stopped the test and started using it normally.
Lo and behold! It was rock solid stable! No crashes, no matter what I did! Wifi, bluetooth, GPS, games, maps, youtube,... all of the above?!
And it would stay this way for me for about 2 weeks. When the phone starts restarting again, I would run the stress tester for a couple of hours, and it would be stable again.
I have since tried the 20d firmware, which also ran fine. I also flashed 20e yesterday, and so far it has been very smooth. I have tried various amounts of times like 1hr, 3hrs, 10hrs, but it would seem that going longer than 3hrs have no impact on the interval between restarts. So personally I find 2hrs will last me 2weeks or so and that works best for me.
I may not have completely solved the problem, and I still don't understand why it works, but it is sort of working for me.
And I hope it would work for you as well!
So here you go! And thanks for reading this unnecessarily long post!
TL;DR
Summary - I have found that by putting the cpu on load for an extended amount of time will dramatically increase the stability of the problematic phone. Here's something you can try:
Disclaimer: I do not guarantee this will work on your phone. I am no engineer. I take no responsibility if it causes any problem on your phone or if it explodes. That being said, it has worked for me. Please try at your own risk!
1. Make sure the area is well ventilated, the phone has sufficient battery or is charging.
2. Download and run "StabilityTest (ROOT Optional)" from Play Store.
3. Run "CLASSIC STABILITY TEST"
4. Let it run for at least 2 hours. If your phone restarts during the test, try again.
*However I would keep an eye on the temperature. I normal at around 50-60 Celsius.
5. It SHOULD be okay now. Depending on how bad your particular problem is, you may have to repeat this process every week or two. Experiment with different load times and see where your sweet spot is.
Thanks,
cbpneuma

Thanks for writing up your experience and theory. I wonder if the additional stress load is generating a large amount of heat that is curing some type of mechanically related electrical fault like a cold solder joint or marginally loose connection.
Some people bake or freeze their phones once the phone is continuously bootlooping so that they can get it to boot up and stay operational long enough to pull their data off the phone.
LG should take responsibility of their shoddy product and replace all affected serial numbers now without questions or provide a 3 year extended warranty.

Wow
That's great TC.
This is the first real lead that anyone has made ( to my knowledge)
And may be why LG is quiet on the cause of the hardware failures
Similar heading would help red ringed Xbox 360 and yellow light ps3's back in the day

cbpneuma said:
Engineers are probably laughing at me right now. I know it probably makes no sense, but it's the best that I can come up with. So I come to you guys, maybe some may help shed some light on this issue that plagues those of us who are stuck with the problematic phones that are not eligible for exchanges/repairs.
Click to expand...
Click to collapse
Not laughing if anything your patience and dogged determination is inspiring.
Great write up

I have found out something !!!
After 6 months of use of my LG G4 H815 S/N 509 Germany... When I put it over heavy load and let it heat up pretty well ( about 70-80 degrees Celsius ) I used to take the back cover off !!! I smelled it several times through out this period !!! And guess what I used to smell ??? The smell of flux !!! which shouldn't be there... I used to work daily fixing Mobos and PCBs so I know how flux smells like !!! My theory is that there is an excess of flux with the solder on the board and as we know flux helps solder to melt at lower temps, so at certain high temps on the G4, flux is slightly boiling... which is causing these fumes ( no smoke though !!! ) !!! Which could cause either of both:
1. An isolation if flux wastes get between the solder and the PCB !!!
2. If solder is deforming or melting which might cause loose contact between the components and the PCB !!!
How to fix this, it is all about burning the flux away without causing damage to the mobo :
1. Heat the hell out of your LG G4 while it is sitting still on a table !!! ( AND I REPEAT, SITTING STILL !!! NOT MOVING AROUND !!! )
2. The better solution would be to fix it like we fix GPUs !!! And this will burn the flux away so the solution should work...
a. Disassembled your LG G4 and remove your mobo.
b. Turn on your oven and heat it to 200 Degrees Celcsus .
c. Place your mobo on the Aluminium foil stand onto a cooking sheet or Aluminium foil with the EMI shield Up.
d. Once Oven has reached the 200 Degrees Celsius... place it into the Oven and bake it for 7 min.
e. When time up, leave the Oven door opened and the it stand or cool down for at least 60 min. (but I recommend you wait 120 min. to be on the safe side !!! ). Do not touch it or move it or eat it ( LOL, that sounded dirty... ) !!! Be patient.
f. Finally, reassemble your G4 and turn it on !!! It should work fine now !!!
Don't attempt this fix unless you are aware of what you are doing !!! And only if LG refused to fix your precious device !!! Don't attempt to fix it if you lack the required experience and skills !!! Learn how to do things first...
" DISCLAIMER: "
I am not responsible of any damage you cause to your device, yourself, your surroundings... or even your entire god damn country !!! LOL... I am not responsible if you cause a thermonuclear war or get the USA and Russia into war trying to fix your device !!! So please be aware of what you are doing and be careful !!!
BTW I hear a weird sound ( similar to spinning HDD if you ever heard one ) coming from the SoC area on the LG G4 when I put it under heavy load !!! I wonder if it is normal or due to the loose contact which usually causes similar sounds to come out of electronic components !!! Does anyone else hear that ??? Is it normal ???
( btw before you start saying that, I know smartphones don't have HDDs !!! I was just describing the sound !!! )

Just a comment... flux does not actually lower the melting point of solder, but rather helps it to flow better to the metal traces of the components and printed circuit board.
From Wikipedia (https://en.wikipedia.org/wiki/Flux_(metallurgy))
In high-temperature metal joining processes (welding, brazing and soldering), the primary purpose of flux is to prevent oxidation of the base and filler materials. Tin-lead solder (e.g.) attaches very well to copper, but poorly to the various oxides of copper, which form quickly at soldering temperatures. Flux is a substance which is nearly inert at room temperature, but which becomes strongly reducing at elevated temperatures, preventing the formation of metal oxides. Additionally, flux allows solder to flow easily on the working piece rather than forming beads as it would otherwise.
The role of a flux in joining processes is typically dual: dissolving of the oxides on the metal surface, which facilitates wetting by molten metal, and acting as an oxygen barrier by coating the hot surface, preventing its oxidation. In some applications molten flux also serves as a heat transfer medium, facilitating heating of the joint by the soldering tool or molten solder.

cbpneuma said:
First and foremost, I don't promise this will fix anything as it has only worked for myself, but let me share my experience/journey and see if this can help at least another person in the same boat as I am.
If you do not want to read the entire story, feel free to skip to the break below.
Back story:
I got the phone in Hong Kong back in November. ...
Click to expand...
Click to collapse
Very interesting. Keep in mind that almost all of the bootloop problems are fatal - the phones won't boot up unless placed in a freezer, and eventually many of those phones won't boot up at all, even if placed in freezer. And the oven method doesn't provide for a long term fix.
For most of us, once it starts to bootloop, the phone is basically dead.

kwarwick said:
Just a comment... flux does not actually lower the melting point of solder, but rather helps it to flow better to the metal traces of the components and printed circuit board.
From Wikipedia...
In high-temperature metal joining processes (welding, brazing and soldering), the primary purpose of flux is to prevent oxidation of the base and filler materials. Tin-lead solder (e.g.) attaches very well to copper, but poorly to the various oxides of copper, which form quickly at soldering temperatures. Flux is a substance which is nearly inert at room temperature, but which becomes strongly reducing at elevated temperatures, preventing the formation of metal oxides. Additionally, flux allows solder to flow easily on the working piece rather than forming beads as it would otherwise.
The role of a flux in joining processes is typically dual: dissolving of the oxides on the metal surface, which facilitates wetting by molten metal, and acting as an oxygen barrier by coating the hot surface, preventing its oxidation. In some applications molten flux also serves as a heat transfer medium, facilitating heating of the joint by the soldering tool or molten solder.
Click to expand...
Click to collapse
You probably misunderstood me... But it is okay !!!
Flux helps the solder to melt faster ( not lowering the melting point of solder ) cuz it allows better heat transfer... It also helps soder to better stock to the PCB and the terminals of electronic components !!!
Flux with solder works like oil when you want to fry potatoes... It will make them get cooked faster !!! Without oil they will take longer time !!! I hope you get my point....

starfcker69 said:
Very interesting. Keep in mind that almost all of the bootloop problems are fatal - the phones won't boot up unless placed in a freezer, and eventually many of those phones won't boot up at all, even if placed in freezer. And the oven method doesn't provide for a long term fix.
For most of us, once it starts to bootloop, the phone is basically dead.
Click to expand...
Click to collapse
I feel like this more because of the **** implementation of CPU, since I disabled 2 main cores almost 3 or 4 weeks ago my phone is running pretty well and I'm even on a custom ROM.

Adam Myczkowski said:
I feel like this more because of the **** implementation of CPU, since I disabled 2 main cores almost 3 or 4 weeks ago my phone is running pretty well and I'm even on a custom ROM.
Click to expand...
Click to collapse
What was your phone doing before you disabled those two main cores and do you feel any performance decrease with them disabled?

divineBliss said:
What was your phone doing before you disabled those two main cores and do you feel any performance decrease with them disabled?
Click to expand...
Click to collapse
My wasn't completely dead, it was booting up sometimes, rarely but usually in the really low temps, I tried baking the mobo, worked for few hours and phone died, I put thermal pads on all the components what made pressure on them pushing them apart into the processor, phone worked, but again in REALLY low temps if it got up to like 27•C the phone constantly rebooting. ( I was on stock Marshmallow btw ). Then I found this reddit thread about disabling big cores, somehow it worked. Works only on 5.1, just saying. Anyway even though I disabled only 2 cores, the phone have been booting up only on 1 (WTF), what made it really slow and laggy. Fortunately, if you root your device you can enable all 4 cores in device manager. Or if you have H815 with unlocked bootloader as I do, you can flash any AOSP, CM, AOKP etc based ROM, with root and enable all for cores as well, I don't feel that big difference since I'm on pure android really. I already found a bug that disabling 2 cores is causing, on SUPERXE AOSP ROM this is somehow causing lockscreen settings to crash as I am not able to have any screen lock, weird bug... I didn't try any other ROMs.

All of your G3 hardware problems - SOLVED!! (BSOD, screen flicker, sim card, etc)

Hello all
I had a chance to buy 15 units of G3, all broken or faulty. The purchase was made via an Swiss operator who was about to recycle the devices, but instead of recycling I bought them via some program for that. They dont pay for recycling, I get the devices extremely cheap, no one pays any tax (Switzerland stuff and their laws)
First of all I want to say - LG made a phenomenal job of envisioning a device - G3 was superb compared to all the phones released in that time period (S5, OPO1, Z2/Z3, etc) with it's bleeding edge technology and phenomenal design (which I am sure inspired others to go bezel-less and edgy and so on). 2K screen, great chipset, infrared focus and insane camera quality, etc.
Only thing they made bad was actual hardware assembly: I have never seen such bad work in modern electronics judging just by the amount of extra-flux you can see on the motherboards, looks extremely sloppy. That kind of assembly eventually led to 1000 problems, which I am sure all of us G3 owners experienced past the 24 month warranty period. Some would go so far to say that this stuff with G3 could be considered Planned obsolescence with all the problems appearing just around the 24 months clock, and with the MM update (taking into account that LG held the Nexus flag at that moment and they went over their heads thinking they are going to surpass Samsung, just like Samsung did to HTC)
My 15 units were:
- 6 units BSOD
- 5 units screen flicker
- 2 units "wifi turning on"
- 2 units sim card removed and restart/No sim card/invalid card
Note: I am not electrician and I dont understand how to read schematics, all of my info came from people that I figured best know how to repair mobile phone stuff (and also speak THE WORST english)
G3 motherboard layout for future reference:
http://i.imgsafe.org/1b64bf1021.jpg
1. BSOD -
The problem is with bad BGA solder of MMC chip. Not the actual chip (very rare occurrence). In short: BGA Solder is type of assembly that uses little balls of solder instead of pins, to hold the chip in place. There are more than 60+ balls on the MMC chip so no homemade replacement is possible (there is actually a turkish video which is NOT the way to do it as the guy doesnt add new balls, just strips old ones away)
permanent solution: give it into a repair shop to replace or do a proper reball of the Sandisk memory chip
semi-permanent solution (sometimes works 100%): give the chip a heat of 120-150 celsius (no american units, sorry) for 2 minutes (using a high powered hair dryer of at least 2000W, or a proper heat-gun) with slight push (I used wooden objects so that Metalic ones wouldnt damage the chip) > this repaired total of 5 BSOD phones, just one went dead completely after several tries. ALL of my 5 units never went back to BSOD. Please, DO NOT use ovens or anything like that, If you dont have a god-damn hair dryer give it to a technician and ask him to blow it for a minute or so. Ovens WILL burn other parts of the board, and knowing how shi*ty the whole assembly is, baking the board will just detach other chips. If you apply pressure to the chip, use something wooden like a chopstick or a pencil (dont use bamboo, it will release oils, use dry wood)
2. screen flicker -
The problem IS NOT a graphic chip (analogix), the problem is NOT CPU, as many have speculated in the past and the people who putt thermal paste over a CPU need serious education on the topic. Thermal paste is in no way a magical substance that lowers temperature when applied - it's purpose is to fill the gaps between a heating body (CPU) and heat dispenser (cooling unit, cooler, aluminum grill, etc), so thermal paste is a gap filler, not a cooling magical stuff. With that out of the picture, the problem of the screen flicker is a completely separate integrated circuit which goes haywire due to some magnetic stuff:
PERMANENT SOLUTION (homemade doable):
Now first, go back to motherboard image, and on the front side of the board find Gyro Sensor chip - just above that chip, there is a grid of 5x5 pin-like circuits.
http://i.imgsafe.org/1ba7e9ccc9.jpg
Now that you have located them, that is your LCD screen flicker solution: I didnt quite understand what is really going on there, but you need to apply heat (just like in the BSOD solution, same time same temperature), and use metallic object to "clean" the pins. He explained to me that the screen flicker is due to some magnetic residue that builds up in that circuits, and a clean metal will remove it. (how that is even possible I dont know but the solution works) Long story short - I used a really fine metallic brush (Dremel set) and once I heated it up, just strolled with brush over those pin-heads. According to the guy, the metallic object needed for cleaning should be non-magnetic. If you dont remove the screen flicker at first, use a really fine object to give all the pins a push (once heated), I used broken needle (regular needle is too sharp) or smallest Phillips screwdriver in my set. IMPORTANT: when doing this, there is a ton of chips nearby so it's smart to protect rest of the board with Alu-foil
total of my 5 screen flicker units NEVER went back to screen flicker issue. Special note: 2 of my units after completely removed screen flicker issue, immediately went to "no sim card" issue and I dont know how that is connected, but there is also a method for sim-card issue repair further down the topic
3. Wifi turning on/wifi grayed out/wifi scanning
The problem over here is also not the problem of the actual Wifi chip (motherboard image back side, red mark). The problem is the power controller located on the front side (red mark). It is also a BGA solder issue so it's repairable
permanent solution: reball or replace chip in proper mobile service shop
semi-permanent solluton: Use the same method of repairing as for the BSOD problem, but with applying heat + pressure onto the power controller chip. Be careful as there are tons of IC's nearby. Homemade solution worked partially for me - one unit (out of 2) is completely repaired, other unit actually went dead (I believe I gave it too much pressure, that was my first repair )
4. Sim card removed and restart/No sim card/invalid card -
The problem with this is also not a problem of RF chip (backside green) or the 2g/3g/4g chip (backside light red), and it is NOT a problem of Sim card slot: it's one lousy mo-fo chip that's not even listed in the hardware parts image, and it's only noted in the actual schematics (I believe it's a chip for regulating power onto the sim card slot and transferring data further)
this one (red arrow pointing onto it):
http://i.imgsafe.org/1c52a74d87.jpg
permanent solution: replace, reball or reflow in service shops (when I say replace, it makes sense as new chips out of the box have BGA balls already on it, just need to place it and heat it up)
semi-permanent solution: same method goes like BSOD and wifi problems - apply heat and moderate pressure with wooden object. The problem with this one is that it will reappear as a problem. I had one unit in the service shop where the repair guy gave it some insane heat for 5-6 seconds while protecting rest of the board, and it was permanent, no sim problem any more. In homemade variant, the problem seems almost unable to fix, but you need to be persistent. sometimes it takes 4-5 tries for the phone (placing the board, and removing it again and so on is a pain in the arse) to recognize sim and after that you are good for a month or so, once it "catches" I gave it a try with a higher temperature / less time (200c, 30 seconds) and it shows better results, I dont need to try the board for 3-4-5 times until it recognizes the SIM, it's imediately good to go, but even with that it reappears after a month, 2 months, but sometimes after only couple of days
one unit is permanent (reflow in service shop), others (repaired screen flickers that went "no sim card" ) bug me still with reappearing SIM problem.
There you go, I wanted to share this with everyone so you people wouldnt lose your mind with paper tricks, ovens, and such, as G3 is still really powerful device and it would be bad for all the units to end up in a bin. I am using 3/32 version with fulmics and it works as any new 600 usd device, if G3 still works without a flaw there is really no need to go newer, not yet.
END NOTE: every attempt at trying this is on your own responsibility, I am not responsible if you fry your board, break your device, or tear your flex cables and such.
END NOTE2: in my experience, dont attempt to try the newly repaired board with battery less than 40%, I wont get into it right now but all Li-ion/Li-poly devices work at their best when there is a good charge
good luck with potential experiments fellow XDA people

Thank you for this thread, I'm sure it will help a lot of more technologically-minded users on XDA. As for me, I did have a sim card removed problem but thankfully it appeared within my warranty period so I took it to them and they replaced the entire PCB (MoBo).
Sent from my LG-D855 using Tapatalk

Thanks for the info. After troubleshooting a few BSOD & flicker phones I came to pretty much the same conclusion as well. Although some temporary G3 fixes work for a short time, nothing is actually "repaired" until you replace the BGA ball solder; so unless you have the proper equipment to work on BGA components you're kind of screwed.
LG has a quality problem with their manufacturing techniques of their motherboards; the latest issue was bootloop issues on the later G-series phones that were also tied to poor soldering(which they are now being sued over). It's a shame too, because I like LG's devices...just hard to trust them completely at this point. But I guess that's the philosophy of these huge OEM's these days: skimp on quality to meet sales demands. Samsung is a good example of this as well with their exploding note 7's and red tinted S8 displays(that they refuse to admit is a hardware problem - "lets just make the red tint slider longer!" just like their software "fix" for the Note 7 battery that didn't work and eventually required a massive recall). Buying a phone is turning into a crap shoot these days

@startswithPendswithOOH - you are right about everything, they really have crappy assembly. But for me, almost all of BSOD and screen flicker issues are repairable in the home conditions using methods from original post. Luckily I do have a professional heat gun so I can even experiment on the temperature and time of heating and my repair rate is great (fortunately I had 15 devices to experiment on). I actually made some money of it, sold almost all of them that were repaired and not a single buyer called me back with a problem. My girlfriend and my nephew are going with my repaired G3s and they use it constantly. Especially my girl, she abuses it to the point that I get annoyed and remove all her running apps (sums up to 20+ ) cause she uses just 10 of some social apps and such, her phone should overheat and problems should reappear if it were not for a good repair. She usesd BSOD repaired device and didnt have one for 4 months now

Update on possible solution for the sim card problem
I did a little tempering with a piece of dry wood, and I made it EXACTLY into a shape of the square of the SIM card chip (described in the original post). I used a stick and shaped it with dremel sandpapering tool, to be exactly the size of the square. Then I putt a cloth underneath the board (so when applying pressure from the upper side you wont break some other stuff opposite) and made a pressure with wooden stick, approximately the force needed to pierce the styrofoam with index finger. That's about the strongest pressure you can give it, and not damage the board. heated it up with 200c with a heat gun for a minute
6th day without problems, without sim card failure, should be noted that I am abusing that board via data and calls going all the time and it seems the problem is solved, will report again in 3 weeks (full month)

Hey!
Do you have any fix for rear camera problem?

Sp3cTeR said:
Hey!
Do you have any fix for rear camera problem?
Click to expand...
Click to collapse
well I do - only problem with rear camera should be - replace rear camera :cyclops:
Oooooh, I stand corrected after a bit of google-ing. I see that it IS an actual problem with no solution, camera sometimes works, sometimes it doesnt. Well, it could be yet another chip on the board, actually the way people described the problem on Androidcentral forums, seems it's 100% a chip issue. If it was HW issue it would work or not work, this partial usability points to another motherboard problem
anyways you should check all the stuff that should NOT be motherboard issue
1. camera module gone bad - replacement should be extremely cheap, check out service shops for spare or Aliexpress for mega-cheap spare, if you know how to open ask someone with G3 to replace cam modules for couple of days to check
2. camera flex cable - in the process of fiddling with the phone and removing motherboard several times, one can easily tear the flex cable of the cam, examine it
3. motherboard connector for camera - for this I really dont see even a remote chance of happening, but im still mentioning it
4. software problem - eliminate the possibility of tempering with root access with files, by doing a factory reset

Well, just bought lg g3 for $60. Pretty clean. The problem was that owner couldn't get it out of Firwmare Upgrade screen, had no experience nor time / patience. So I bought it. Later that night, managed to flash v10e from lgg3root(dot)com tutorial for it. From the first try.
But using the phone got laggier and laggier, and if I were to do multiple tasks like switching between apps and stuff like this, the phone would freeze and then in about 15-20 seconds it would give me the LG logo and pretty much stay there, eventually giving the "kernel crashed" screen (BSOD ?? )
Please, what do u think the problem is?
Managed eventually get v20h / v30b on it but was pretty much unusable, and most of the time, when trying to get it connect with the ADB and run "reboot recovery" and do factory wipe, it would just crash again. Now I'm stuggling to get v10e again on it ... but it's really a pain. I've got about a week worth of hours into making it work. Please, read my thread to get some more 'clues' https://forum.xda-developers.com/lg-g3/help/help-horrible-experience-d855-t3600094

AKAndrew41 said:
Well, just bought lg g3 for $60. Pretty clean. The problem was that owner couldn't get it out of Firwmare Upgrade screen, had no experience nor time / patience. So I bought it. Later that night, managed to flash v10e from lgg3root(dot)com tutorial for it. From the first try.
But using the phone got laggier and laggier, and if I were to do multiple tasks like switching between apps and stuff like this, the phone would freeze and then in about 15-20 seconds it would give me the LG logo and pretty much stay there, eventually giving the "kernel crashed" screen (BSOD ?? )
Please, what do u think the problem is?
Managed eventually get v20h / v30b on it but was pretty much unusable, and most of the time, when trying to get it connect with the ADB and run "reboot recovery" and do factory wipe, it would just crash again. Now I'm stuggling to get v10e again on it ... but it's really a pain. I've got about a week worth of hours into making it work. Please, read my thread to get some more 'clues' https://forum.xda-developers.com/lg-g3/help/help-horrible-experience-d855-t3600094
Click to expand...
Click to collapse
Hi, the links arr down?

i fixed my screen flickering issue thank you so much i will report if it comes back it's no problem for me but the fix you described works that means those circuits have something to do with this,i would like to know if it's possible to clean those circuits with alcohol it's maybe stupid but idk you tell me other than that thank you
edit:it's back sorry if got anyone excited,i'm back to putting the pressure on the SOC

Thank bro u saved my device!
Updated : flickering to fading comes again after less than an hour with less usage , just charging it, so i tried heated up and put pressure again but this time on the processor.

Igoritza said:
4. Sim card removed and restart/No sim card/invalid card -
The problem with this is also not a problem of RF chip (backside green) or the 2g/3g/4g chip (backside light red), and it is NOT a problem of Sim card slot: it's one lousy mo-fo chip that's not even listed in the hardware parts image, and it's only noted in the actual schematics (I believe it's a chip for regulating power onto the sim card slot and transferring data further)
this one (red arrow pointing onto it):
http://i.imgsafe.org/1c52a74d87.jpg
Click to expand...
Click to collapse
Well done mate, but according to service manual the chip you pointing with red arrow is NFC
Im bit confused now what it have to do with the sim

As far as i think, if bsod or screen flicker comes up, theres no need to fix it because its dead, so just buy a new mobo and thats it.

startswithPendswithOOH said:
Thanks for the info. After troubleshooting a few BSOD & flicker phones I came to pretty much the same conclusion as well. Although some temporary G3 fixes work for a short time, nothing is actually "repaired" until you replace the BGA ball solder; so unless you have the proper equipment to work on BGA components you're kind of screwed.
LG has a quality problem with their manufacturing techniques of their motherboards; the latest issue was bootloop issues on the later G-series phones that were also tied to poor soldering(which they are now being sued over). It's a shame too, because I like LG's devices...just hard to trust them completely at this point. But I guess that's the philosophy of these huge OEM's these days: skimp on quality to meet sales demands. Samsung is a good example of this as well with their exploding note 7's and red tinted S8 displays(that they refuse to admit is a hardware problem - "lets just make the red tint slider longer!" just like their software "fix" for the Note 7 battery that didn't work and eventually required a massive recall). Buying a phone is turning into a crap shoot these days
Click to expand...
Click to collapse
Preach on. Lol i got a g4 im in the lawsuit over

Yeah black screen comes back when the tmperature was hot. So its time to throw away this crap g3. Hopeless .

2 years ago a yellow coffe spot appeared on the top corner of my lg3 display, so i sent back to warranty and they changed the lcd screen.
Some month after the same coffe spot appear in the same area, i brought back the phone in warranty they changed the lcd. again
Now i have the problem for the 3rd time, im not in warranty anymore.
In my opinion is not the lcd, the lcd cant burn itself in that way, i think is a glue problem and maybe i can buy a new 13$ glass on amazon and replace it.
But before to risk to broke the phone, anyone experienced that?
This is an image i found on google image, is not my G3 but that explain my situation.
{
"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"
}

L33TaS said:
As far as i think, if bsod or screen flicker comes up, theres no need to fix it because its dead, so just buy a new mobo and thats it.
Click to expand...
Click to collapse
that's is also a temporary solution,if you're wasting money better buy another smartphone that is no an lg,go with another reliable brand

Khalid47 said:
i fixed my screen flickering issue thank you so much i will report if it comes back it's no problem for me but the fix you described works that means those circuits have something to do with this,i would like to know if it's possible to clean those circuits with alcohol it's maybe stupid but idk you tell me other than that thank you
Click to expand...
Click to collapse
how close did you hold the heat gun/ hair dryer?
Khalid47 said:
that's is also a temporary solution,if you're wasting money better buy another smartphone that is no an lg,go with another reliable brand
Click to expand...
Click to collapse
This is true. I bought a new mobo from DhGate to fix the famous "WiFi saved but not connecting issue" only to end up with the screen flickering, lines, and fade to black issue with the replacement mobo. I want to get a new phone but I'm waiting for the note 8/ pixel 2 .

unbreakabl3 said:
how close did you hold the heat gun/ hair dryer?
This is true. I bought a new mobo from DhGate to fix the famous "WiFi saved but not connecting issue" only to end up with the screen flickering, lines, and fade to black issue with the replacement mobo. I want to get a new phone but I'm waiting for the note 8/ pixel 2 .
Click to expand...
Click to collapse
i held a hairdryer for 3 mins with my hand i'm thinking the problem will comeback but i don't care i fixed it many times temporarely,as for the mobo you shouldn't have wasted your money it's really dumb people who buy it again we already know that it will die really what's the point of that,as for your future daily driver i would recommand you go with a sony i'm not working for them or anything i had a sony and my brother has one never experienced anything hardware related or software related,just talking from my experience with this brand i can't advise you something that i never tried samsung or xiaomi etc...,goodluck with your fixing

Khalid47 said:
i held a hairdryer for 3 mins with my hand i'm thinking the problem will comeback but i don't care i fixed it many times temporarely,as for the mobo you shouldn't have wasted your money it's really dumb people who buy it again we already know that it will die really what's the point of that,as for your future daily driver i would recommand you go with a sony i'm not working for them or anything i had a sony and my brother has one never experienced anything hardware related or software related,just talking from my experience with this brand i can't advise you something that i never tried samsung or xiaomi etc...,goodluck with your fixing
Click to expand...
Click to collapse
i meant how far away from the chip did you hold the hairdryer? 10cm, 20cm etc.
well I wanted to keep the phone going till the Fall lol.. and plus i didnt think that the replacement would have issues tbh. Thanks for the recommendation. I'll look into them.

Possible bootloop fix? (Hardware based)

Ok so, I work in a phone repair shop.
Today a guy came in with 2 6P's. One with battery issues, one with BLOD.
Well I tried the software fix for him for the BLOD 6P.....no dice. So he said, you take it. I have no use for a brick.
Well guess what phone I'm writing this on ?
So I tried a couple different flashes of software, different ROMs, stock and otherwise with the 4 core fixes and twrp. Saw no life regardless.
So I thought, nothing to lose, let's see what I can do.
First though was to just heat the SOC and see what happens, still nothing. Just a basic heating nothing extreme. I've brought back a few devices just doing a basic heating before (iPhone and Android)
Obviously not the case here.
So with nothing left to use I went extreme.
Removed the EM shield. Sat with the heat gun on the SOC (moving around slowly of course) till I smelt the sweet sweet smell of solder. As soon as I did I took these little clamps we have for holding down screens like iPads, and used a single one to ensure the SOC was held down to the board. Let it cool.
Then cleaned up the paste, and took some thermal pads from a broken screen Samsung a5 2017 we had. And replaced the old paste with those pads( a little cutting required) replaced both on top of the SOC and on top of the shield.
Put back together, and 4 hours after receiving it in bootloop this 6p booted up with all 8 cores running like a beast!
Don't know how long this will last, hopefully for a long time. We're going on almost 24 hours now so here's hoping ?
On another note, I plan to tear down the A5 screen for the copper heatpipe tommorow and replace the EM shield thermal pad with the heatpipe and see how that goes.
Hopefully this mini guide can help someone out who may be more willing to go all out to fix their fancy brick ?
UPDATE:
Heat pipes have been added.
Applied Arctic silver 5 with a copper shim directly on the SOC.
Put the em shield back on, took copper "heatpipes" from a Sony z5 screen, and noticed how thin they were. Arctic silver on the EM shield, cut a large piece of copper from the back of a Samsung S5 screen, then cut that into 2 pieces to about 3x1". To simulate proper "heatpipes."
Sat the copper pieces in the spot the EM shield sits and re-assembled.
Phone is still working just fine, I've been monitoring temps and the 4 bad cores. They haven't had an issue and the SOC sits at idle at 32°
I decided to stress it a little bit with multiple apps running, split screen YouTube(1080p60fps) and facebook. Max temp it hit was 37°.
Using "CPU Monitor" from the play store for this information.
And currently using it as my daily driver as my own sort of stress test lol

Nice...
are you able to boot into recovery before heating up the soc??
Mine unable to boot to recovery at all cost...
Tried heating with heat gun at soc but still unable to boot recovery...

ronald_loulan said:
Nice...
are you able to boot into recovery before heating up the soc??
Mine unable to boot to recovery at all cost...
Tried heating with heat gun at soc but still unable to boot recovery...
Click to expand...
Click to collapse
Were you running android pie before it started bootlooping?

imjuz4you said:
Were you running android pie before it started bootlooping?
Click to expand...
Click to collapse
1st bootloop was on 7.1 and suscessfully rebooted.
So I quickly flash 4 core mod.
After 1 month of battery replacement the device bootloop forever.
It survived for 2months+ from the day I flash 4 core mod.
I tried oreo and with 4core mod and etc but failed.
Moved to hardware repair, as above but still failed.
It bootloop and unable to boot into TWRP, not even booting TWRP thru ADB.

I can't say without having the device on hand, and running some tests. But from what your describing and the processes you've tried it sounds to me like the flash storage chip may be your issue. Either it's doing the same as the SOC and slowly separating from the board, or it's a generally bad chip.
Just taking an educated guess so don't take my word for it lol

However, to answer your original question (I'm sorry I didn't see it)
When the phone was booplooping I was UNABLE to access recovery, even after flashing an OS, however I was able to adb transfer and flash twrp without any issues.

Romain1911 said:
However, to answer your original question (I'm sorry I didn't see it)
When the phone was booplooping I was UNABLE to access recovery, even after flashing an OS, however I was able to adb transfer and flash twrp without any issues.
Click to expand...
Click to collapse
You mean adb push file.zip?

ronald_loulan said:
You mean adb push file.zip?
Click to expand...
Click to collapse
Yes

Tried that but my device doesn't boot into recovery...

Romain1911 said:
Yes
Click to expand...
Click to collapse
When the phone was not working you was able to send with adb files to it? This is strange. Normaly you can then just flash with fastboot (fastboot flash recovery filenname.img) the 4 core twrp and from there on you can use usb file transfer to load for example your LineageOS and after flashing lineage os, you then configure the kernel with N5X-6P_BLOD_Workaround_Injector_Addon-AK2-signed.zip . This have really not worked (to make the phone usable with just 4 cores) but reheating the SOC worked?
Can you explain some more in detail what temperature (in celsius) you have used to make the solder of the soc fluid again?
Did you think this would also work when you just have a regulated SMD soldering station and no other tools? I ask that because you told that you have been using some other tools to hold something (if i understood you right).

nexus 6p BLOD
whats up guys, i have a nexus 6p with BLOD, i am unable to flash the 4 core fix provided by XDA due to USB debugging being disabled before the loop. is my only option to dissasemble and go for a reflow of the cpu? or is there anything i can do using fastboot or adb? cheers

You dont need usb-debugging. You need a unlocked bootloader. You unlock the bootloader with "fastboot oem unlock" when your phone is in bootloader mode. It does not matter what Android you have installed when your bootloader is unlocked or unlockable.
If you have missed to enable the option to unlock the bootloader previous, then you have to heat up your phone to boot up once and then immidietly enable the option to unlock the bootloader.
But thats all not relevant in this thread. This thread is about fixing up the SoC again and not for "getting it at work again with just 4 cores". There are ton of other forum posts that cover that.

ncc8uetou5et said:
You dont need usb-debugging. You need a unlocked bootloader. You unlock the bootloader with "fastboot oem unlock" when your phone is in bootloader mode. It does not matter what Android you have installed when your bootloader is unlocked or unlockable.
If you have missed to enable the option to unlock the bootloader previous, then you have to heat up your phone to boot up once and then immidietly enable the option to unlock the bootloader.
But thats all not relevant in this thread. This thread is about fixing up the SoC again and not for "getting it at work again with just 4 cores". There are ton of other forum posts that cover that.
Click to expand...
Click to collapse
well i have no way of getting the phone on, i cannot unlock the bootloader due to allow bootloader unlock not being enabled. i dont have access to settings. ive heated the phones exterior to no avail. so i will have to dissasemble it and fix the soc so yes i am on the right thread thanks.

ncc8uetou5et said:
When the phone was not working you was able to send with adb files to it? This is strange. Normaly you can then just flash with fastboot (fastboot flash recovery filenname.img) the 4 core twrp and from there on you can use usb file transfer to load for example your LineageOS and after flashing lineage os, you then configure the kernel with N5X-6P_BLOD_Workaround_Injector_Addon-AK2-signed.zip . This have really not worked (to make the phone usable with just 4 cores) but reheating the SOC worked?
Can you explain some more in detail what temperature (in celsius) you have used to make the solder of the soc fluid again?
Did you think this would also work when you just have a regulated SMD soldering station and no other tools? I ask that because you told that you have been using some other tools to hold something (if i understood you right).
Click to expand...
Click to collapse
Yes it worked just fine sending files too it however the 4 core fix still did not work hence why I went into the hardware method.
If I remember correctly the heat gun was set to max for this, so in our case it stops at about 430°.
As for it working without other tools, I can't say.
What was used is a clamp that we use in my shop to hold down screens that have been just been replaced so that the glue solidifies with the screen held down.
I can only assume that the clamp held it down so that the solder would make proper contact while it re-solidified, at least that was my hope when I clamped the chip down. Whether or not it was the main reason for it working I can't say, and at my shop we lack the hardware to do a full chip removal, re-ball, or anything of that sort unfortunately.

Cpu reflow
Romain1911 said:
Ok so, I work in a phone repair shop.
Today a guy came in with 2 6P's. One with battery issues, one with BLOD.
Well I tried the software fix for him for the BLOD 6P.....no dice. So he said, you take it. I have no use for a brick.
Well guess what phone I'm writing this on
So I tried a couple different flashes of software, different ROMs, stock and otherwise with the 4 core fixes and twrp. Saw no life regardless.
So I thought, nothing to lose, let's see what I can do.
First though was to just heat the SOC and see what happens, still nothing. Just a basic heating nothing extreme. I've brought back a few devices just doing a basic heating before (iPhone and Android)
Obviously not the case here.
So with nothing left to use I went extreme.
Removed the EM shield. Sat with the heat gun on the SOC (moving around slowly of course) till I smelt the sweet sweet smell of solder. As soon as I did I took these little clamps we have for holding down screens like iPads, and used a single one to ensure the SOC was held down to the board. Let it cool.
Then cleaned up the paste, and took some thermal pads from a broken screen Samsung a5 2017 we had. And replaced the old paste with those pads( a little cutting required) replaced both on top of the SOC and on top of the shield.
Put back together, and 4 hours after receiving it in bootloop this 6p booted up with all 8 cores running like a beast!
Don't know how long this will last, hopefully for a long time. We're going on almost 24 hours now so here's hoping
On another note, I plan to tear down the A5 screen for the copper heatpipe tommorow and replace the EM shield thermal pad with the heatpipe and see how that goes.
Hopefully this mini guide can help someone out who may be more willing to go all out to fix their fancy brick
UPDATE:
Heat pipes have been added.
Applied Arctic silver 5 with a copper shim directly on the SOC.
Put the em shield back on, took copper "heatpipes" from a Sony z5 screen, and noticed how thin they were. Arctic silver on the EM shield, cut a large piece of copper from the back of a Samsung S5 screen, then cut that into 2 pieces to about 3x1". To simulate proper "heatpipes."
Sat the copper pieces in the spot the EM shield sits and re-assembled.
Phone is still working just fine, I've been monitoring temps and the 4 bad cores. They haven't had an issue and the SOC sits at idle at 32°
I decided to stress it a little bit with multiple apps running, split screen YouTube(1080p60fps) and facebook. Max temp it hit was 37°.
Using "CPU Monitor" from the play store for this information.
And currently using it as my daily driver as my own sort of stress test lol
Click to expand...
Click to collapse
Hey man, im in the same boat with my nexus 6p.. when reflowing the SOC do i need to use any flux ?
cheers

dyl2526 said:
Hey man, im in the same boat with my nexus 6p.. when reflowing the SOC do i need to use any flux ?
cheers
Click to expand...
Click to collapse
Eh, when I did it I did not use any. But that was for lack of having any, otherwise I would have used it lol
So I would use flux for sure

Legend
Romain1911 said:
Eh, when I did it I did not use any. But that was for lack of having any, otherwise I would have used it lol
So I would use flux for sure
Click to expand...
Click to collapse
Thanks for the reply man, I’m new enough to this so what’s the best type of flux for this phone or is there one that’s good for smartphones in general?

dyl2526 said:
Thanks for the reply man, I’m new enough to this so what’s the best type of flux for this phone or is there one that’s good for smartphones in general?
Click to expand...
Click to collapse
No worries, Novacan old Masters flux in an 8oz bottle is what we usually use here, just didn't have any at the time. It's on Amazon, and fairly cheap.

This is exactly what I thought was going to work, just never had another 6P to give it a whirl. I have brought back numerous dead-GPU laptops this way by resetting the solder. Getting it to 385-400°F for 10 minutes and letting it cool reset the solder and allowed the GPU to work like new again (although results varied). No telling how long this will last but glad to see it worked on a phone.

My Nexus 6p today almost completely dead, I was flashing a ROM bootloggers android 9.0 and before finishing flashing the cell phone has been. off and now when trying to turn it on, Eve does not get anything, I connect it to the computer and it is detected as QS-loader-9008 or something like that, from what I have read it is a hard brick, I will try to make a complete rework to the SoC of the processor to see what happens I would like to know if someone here has done it before to guide me

BLACK SCREEN OF DEATH PHONE DIES UNEXPECTEDLY

G900V KLTE - BLACK SCREEN OF DEATH PHONE DIES UNEXPECTEDLY!!! (new battery)
Still having a problem with black screen of death. I had made a post about it earlier in the week but no response. I have kept everything basically the same, except I use Magisk 21.4-23 (newest), and TWRP 3.5.2 upgraded from 3.5.0 like maybe a couple months ago. Ever since last month have had the problem. I have brand new batteries installed as I thought maybe that was what was causing it (previous experience). Screen goes black, phone vibrates a couple times, then I have to battery pull to try to power on. Sometimes it works, other times it doesnt. In other instances have had screen freeze and get all static and soft reboot itself. I can see the white captive touch buttons working and sound but screen does not wake. Battery pulls for X amount of time does not solve the screen issue. I have flashed correct firmware several times in ODIN. I had this black screen issue and phone died while at the store earlier today. I need a phone thats dependable! This has been happening on any custom roms I use 14.1-18.1. I'm so frustrated I nearly broke my phone in half last night!
Any ideas what's causing the screen issue?

I had a very similar problem on my Galaxy S7. It used to suddenly shutdown, sometimes reboots by itself. Sometimes it won't just turn on at all except after some time.
Sometimes, it vibrates, shows the bootsplash for a few milliseconds, then shutdown.
What a coincidence that when I upgraded to TWRP 3.5, it was when the problem started to hit.
I was using crDroid based on R, It wasn't stable, so I thought the problem was the ROM/Kernel/Recovery. I tried an already known stable ROM.
The same thing happened, then I was semi sure that it is on hardware problem. I teared the device apart. The problem was .. Water Damage.
I thought the phone was water proof/resistant. What a disappointment. Anyway I've cleaned every molecules of water from the phone. It worked fine afterwards.
But I lost the battery percentage diode or something, so the phone can't read battery percentage/voltage.
It took me 3 months to know all these things. I hope it be of help to you.

Mohamedkam000 said:
I had a very similar problem on my Galaxy S7. It used to suddenly shutdown, sometimes reboots by itself. Sometimes it won't just turn on at all except after some time.
Sometimes, it vibrates, shows the bootsplash for a few milliseconds, then shutdown.
What a coincidence that when I upgraded to TWRP 3.5, it was when the problem started to hit.
I was using crDroid based on R, It wasn't stable, so I thought the problem was the ROM/Kernel/Recovery. I tried an already known stable ROM.
The same thing happened, then I was semi sure that it is on hardware problem. I teared the device apart. The problem was .. Water Damage.
I thought the phone was water proof/resistant. What a disappointment. Anyway I've cleaned every molecules of water from the phone. It worked fine afterwards.
But I lost the battery percentage diode or something, so the phone can't read battery percentage/voltage.
It took me 3 months to know all these things. I hope it be of help to you.
Click to expand...
Click to collapse
So I did some more testing tonight. I first downgraded TWRP to 3.5.0 from 3.5.2 had same issues. Now i'm on 3.4.0, and I pounded on the display upside down while in recovery. It did the reboot thing and screen went black. Phone would not power up, even after removing and re-installing batteries. It has taken several tries with and without plugging it in. Finally it has booted up and I went into recovery to re-flash yet another rom. The phone would do the black screen thing at random and have issues if placed down too hard.
Obviously it's not software related it's hardware.
So my question is the display bad or the motherboard?
Should I just look into getting a 5G brand new phone or try to get it repaired somewhere?
I've been considering switching to T-mobile once I get a 5G device.

Droid9684 said:
So I did some more testing tonight. I first downgraded TWRP to 3.5.0 from 3.5.2 had same issues. Now i'm on 3.4.0, and I pounded on the display upside down while in recovery. It did the reboot thing and screen went black. Phone would not power up, even after removing and re-installing batteries. It has taken several tries with and without plugging it in. Finally it has booted up and I went into recovery to re-flash yet another rom. The phone would do the black screen thing at random and have issues if placed down too hard.
Obviously it's not software related it's hardware.
So my question is the display bad or the motherboard?
Should I just look into getting a 5G brand new phone or try to get it repaired somewhere?
I've been considering switching to T-mobile once I get a 5G device.
Click to expand...
Click to collapse
That's obviously water damage. I used to get all that on my old S7. It is fixable, you need to untie your motherboard, heat it till it literally dries up. Then it won't repeat that BSOD thing.
However, if you tried to boot the device while there's still some water, it will cause more damage to the components, diodes.
Galaxy S5 is for about 40$ in my country. You should consider buying another, more recent phone. Midrange 5G phones are for about 250$ - 400$ here. Though I still miss 2014 phones.

Mohamedkam000 said:
That's obviously water damage. I used to get all that on my old S7. It is fixable, you need to untie your motherboard, heat it till it literally dries up. Then it won't repeat that BSOD thing.
However, if you tried to boot the device while there's still some water, it will cause more damage to the components, diodes.
Galaxy S5 is for about 40$ in my country. You should consider buying another, more recent phone. Midrange 5G phones are for about 250$ - 400$ here. Though I still miss 2014 phones.
Click to expand...
Click to collapse
I have no idea how to untie a motherboard or take apart my phone. I'm sure I'd end up doing more damage to it knowing my luck. I have no such tools either to take my phone apart. I've seen S5 for sale here in US for $50 or less and motherboards for a little less. Right now it's hard to afford a brand new 5G phone.
I'm not sure how my phone got water damage? I've always been careful with it over the years never submerged or anything.

Droid9684 said:
I have no idea how to untie a motherboard or take apart my phone. I'm sure I'd end up doing more damage to it knowing my luck. I have no such tools either to take my phone apart. I've seen S5 for sale here in US for $50 or less and motherboards for a little less. Right now it's hard to afford a brand new 5G phone.
I'm not sure how my phone got water damage? I've always been careful with it over the years never submerged or anything.
Click to expand...
Click to collapse
Water Damage usually shows a few days up to a few weeks after it's interaction with water. I thought S7 was water resistant.
A tiny drop of water can cause this issue.
Don't know why people rush towards 5G phones, knowing it ain't stable just yet. I've heard USA is shutting down 2G/3G, so the least you should own is a Dual-VoLTE device. I got A70 for ~162$.

Mohamedkam000 said:
Water Damage usually shows a few days up to a few weeks after it's interaction with water. I thought S7 was water resistant.
A tiny drop of water can cause this issue.
Don't know why people rush towards 5G phones, knowing it ain't stable just yet. I've heard USA is shutting down 2G/3G, so the least you should own is a Dual-VoLTE device. I got A70 for ~162$.
Click to expand...
Click to collapse
Yes 3G has been getting shutdown. 5G is still building out the network. If I were to stay with 4G I might as well stick with S5 since I know it and all my data is saved with titanium backup.
I have read to soak my phone in isopropyl alcohol for up to a couple hours. https://www.orduh.com/water-damaged-samsung-galaxy-s5/
It might be cheaper for me to just find another S5 right now. Can I restore backed up titanium data to a different phone?
I got this phone back in 2015 off eBay after my developer edition SD card slot was broken. Near the front camera it looked like some sort of damage may have occurred after I had received the phone. But I didn't have any of these problems other than a few years ago the BSOD once in awhile which went away.
Currently the BSOD issues have been since earlier this month/last month. As long as I don't put my phone down on table or hit it too hard it has no issue. If it's placed on table as gentle as a feather it's fine. But I have to do lot of battery pulls when I'm out doing errands walking with it.

And screen takes forever to wake when receiving phone calls sometimes I miss them. It's very delayed.

Droid9684 said:
Yes 3G has been getting shutdown. 5G is still building out the network. If I were to stay with 4G I might as well stick with S5 since I know it and all my data is saved with titanium backup.
I have read to soak my phone in isopropyl alcohol for up to a couple hours. https://www.orduh.com/water-damaged-samsung-galaxy-s5/
It might be cheaper for me to just find another S5 right now. Can I restore backed up titanium data to a different phone?
I got this phone back in 2015 off eBay after my developer edition SD card slot was broken. Near the front camera it looked like some sort of damage may have occurred after I had received the phone. But I didn't have any of these problems other than a few years ago the BSOD once in awhile which went away.
Currently the BSOD issues have been since earlier this month/last month. As long as I don't put my phone down on table or hit it too hard it has no issue. If it's placed on table as gentle as a feather it's fine. But I have to do lot of battery pulls when I'm out doing errands walking with it.
Click to expand...
Click to collapse
So I looked at the water damage indicator sensor. My phone's patch is still white with a reddish x pattern, there is no water damage. If there was damage it would be all red.

There's no other explanation for BSOD the way you described except for damaged components, unless the phone was water damaged, it must have received a very hard hit.
That hit will definitely affect the screen, if the phone was refurbished, you won't notice it, cause the motherboard is connected to a good working device.
If you think it is software, there's bootloader, baseband, kernel, and system that you can change to confirm your thoughts.
It's very easy to untie S5, only needs one tool.

Mohamedkam000 said:
There's no other explanation for BSOD the way you described except for damaged components, unless the phone was water damaged, it must have received a very hard hit.
That hit will definitely affect the screen, if the phone was refurbished, you won't notice it, cause the motherboard is connected to a good working device.
If you think it is software, there's bootloader, baseband, kernel, and system that you can change to confirm your thoughts.
It's very easy to untie S5, only needs one tool.
Click to expand...
Click to collapse
I know it's not software the bootloader, kernels, baseband have all been same and worked fine up until this month or so. I smacked the front of it while in recovery to see if it would have the issue. Sure enough it is hardware related! I just messaged a local repair shop on how much a fix would cost. I dont feel comfortable taking apart my phone and I dont have tools or anything.