V20 issues - LG V20 Questions & Answers

I've had a VS995 for about two months. One of the first things I did when I got it was root(dirty santa) and install custom firmware. After doing this I noticed that watching any type of video on the phone would lag extremly bad (<10 fps), unless I held my finger on the screen, and I would get different screen glitches (turn black, turn all static, half and half, etc). I then decided to go back to stock so I flashed a stock KDZ with lgup. This didn't fix the problem. After several weeks of putting up with it, It's gotten to the point where the phone is unusable. It freezes constantly. To get the screen to unfreeze I have to lock then unlock the screen, and half the time it freezes again instantly. Attempting to watch a video (or even a GIF) stutters and chokes after 1-2s and turns the whole screen into static.
At first I was thinking something might be corrupted so today I re-rooted but once I tried to get into twrp the screen kept turning to static. So I flashed back to stock KDZ with no change in performance. Also I can not boot into recovery or fastboot, I've tried several times. Does KDZ upgrade also flash the bootloader?
I'm starting to think it might be something bad on the main board, has anyone ever reflowed one?
I bought the phone used online and it only came with a 30 day warrenty, so no luck there.
Any input would be greatly appreciated.
Thank you

SmokeyMP said:
I've had a VS995 for about two months. One of the first things I did when I got it was root(dirty santa) and install custom firmware. After doing this I noticed that watching any type of video on the phone would lag extremly bad (<10 fps), unless I held my finger on the screen, and I would get different screen glitches (turn black, turn all static, half and half, etc). I then decided to go back to stock so I flashed a stock KDZ with lgup. This didn't fix the problem. After several weeks of putting up with it, It's gotten to the point where the phone is unusable. It freezes constantly. To get the screen to unfreeze I have to lock then unlock the screen, and half the time it freezes again instantly. Attempting to watch a video (or even a GIF) stutters and chokes after 1-2s and turns the whole screen into static.
At first I was thinking something might be corrupted so today I re-rooted but once I tried to get into twrp the screen kept turning to static. So I flashed back to stock KDZ with no change in performance. Also I can not boot into recovery or fastboot, I've tried several times. Does KDZ upgrade also flash the bootloader?
I'm starting to think it might be something bad on the main board, has anyone ever reflowed one?
I bought the phone used online and it only came with a 30 day warrenty, so no luck there.
Any input would be greatly appreciated.
Thank you
Click to expand...
Click to collapse
Yes upgrade in lgup flashes EVERYthing, bootloader, modem, recovery, even the download mode partition. Have to use partition dl mode to be picky (needs the modified lg up files from the mismatched variant thread). The static screen sounds like you need a custom kernel or a new twrp, depending on where its occuring (its related to the dirtysanta bootloader and theres workarounds to fix it builtinto custom kernels and recent twrp)

It's prolly water damage. My V20 was doing exactly the same thing after rooting. I opened the phone and noticed the LCD plug to the Mobo had corrosion on it, I unplugged the LCD from the Mobo and got a clean cheap brand new toothbrush and gently brushed and blew debris off then followed with cleaning with a ear Qtip with a bit of alcohol. Check the seal around the LCD and make sure any gaps are closed with slices of clear tape. I don't know how rooting messed up my phone, it's something strange with resetting the phone, the glitches kicked in from the corrosion on the gold parts. After my first boot from cleaning, my phone was totally normal again. A month later I got screen retention..... Lol but that's a whole other Obvious story everybody shares and knows about lol. I hope you get your situation solved.

Related

[Q] Melting LG Logo and Permanent Black Lines-Help

After flashing Carbonrom 6/22 nightly my screen developed black lines that are permanent on the right side. They do not go away in recovery. I walked away from my phone when I flashed it so I didnt catch it doing anything weird until a came back a few minutes later. I can live with few thin lines on my screen but now the lg logo has started to melt and artifact during boot and it stays like that. I can only get it to boot maybe 1 out of every 10 times with a normal screen otherwise the screen will stay melted or artifacting while I hear notification beeps and ringing.
So my questions are:
Am I doing more damage everytime I boot? Or is it done breaking.(I have since flashed dr87 twrp with thermal safeguards)
Is there any tricks like sticking it in the freezer or something to bring the screen back?
Will I only need to change the LCD or is something broken on the board also?
Any and all help is appreciated.
gorgutron said:
After flashing Carbonrom 6/22 nightly my screen developed black lines that are permanent on the right side. They do not go away in recovery. I walked away from my phone when I flashed it so I didnt catch it doing anything weird until a came back a few minutes later. I can live with few thin lines on my screen but now the lg logo has started to melt and artifact during boot and it stays like that. I can only get it to boot maybe 1 out of every 10 times with a normal screen otherwise the screen will stay melted or artifacting while I hear notification beeps and ringing.
So my questions are:
Am I doing more damage everytime I boot? Or is it done breaking.(I have since flashed dr87 twrp with thermal safeguards)
Is there any tricks like sticking it in the freezer or something to bring the screen back?
Will I only need to change the LCD or is something broken on the board also?
Any and all help is appreciated.
Click to expand...
Click to collapse
Maybe bring back to stock to see if anything changes or try a different rom, couldn't hurt
RubbleTea said:
Maybe bring back to stock to see if anything changes or try a different rom, couldn't hurt
Click to expand...
Click to collapse
I did flash stock rom but it made no difference. Ive never had a hardware issue happen from flashing a rom and I have flashed tons on many devices.
You and me both, brother.
http://forum.xda-developers.com/showthread.php?p=53654415
Neither of you two are alone. See this thread. No resolution yet... http://forum.xda-developers.com/showthread.php?t=2769770

Phone instantly reboots?

I was listening to an audiobook when my phone suddenly died. It would not start back up, so I removed the battery. When I replaced the battery, the samsung logo would pop up but after about a second it would go black again. It will not start again until I remove/replace the battery, at which point it does the one second shutdown again.
At one point I got the phone to boot (no idea what I did differently) and I noticed that it got very hot around the camera area before going black again. A second time I was able to get into recovery, where I did a factory reset. Booted back up and it seemed to be okay, but then heated up very quickly and shut down.
Now, even if the phone is totally cool, I cant get past that 1 second of samsung logo. I'm really at a loss here, and totally screwed without my phone because I am traveling non-stop for the next 2 weeks. Does anyone know how I might try to troubleshoot this? Thanks
Possibly flash a new ROM and start over. That's what I would do
This EXACT situation happened to me yesterday! I was streaming from Google music, it was on the charger and things were fine. A call came in and the phone started vibrating like crazy and wouldn't stop. The screen went black and it kept vibrating. Finally it went off. On boot it will get to my lock screen and then crash after about 30 seconds. If I take the battery out and try again it lasts another few seconds after boot. If I leave it for a LONG time with the battery out and restart it I can get like 2 mins on the next boot without it crashing. The top part by the camera is getting hot on my phone as well. Recovery mode and download mode start fine and the phone doesn't crash. I have some data on the internal that I want to save so I tried to use Odin to flash the most recent build L720VPUFNG2 as that would just install the OS and not touch the data. On the next reboot things seemed to be working fine and I got maybe 5 mins out of the phone before it crashed again. I still don't have enough time to get the data off so I think I'm just going to say screw it and wipe it completely. You guys know of a way I can backup this app data using Odin or recovery mode? My phone is currently unrooted. I'm new to all this tinkering stuff. Phone is out of warranty now anyway.
Threw on a custom recovery, backed up all my data, did a full wipe, now I am good as new.
It worked for awhile but now it is back to rebooting itself. Any idea what could be the issue? I'm assuming at this point it is hardware related. Why can recovery and download mode run consistently without crashing but when an os is fired up it has issues? If it was a hardware issue shouldn't it not work across the board?
So I had Sprint replace my phone on the 8th. I have been using my same batteries (1 stock 1 Anker) and chargers (some stock some not) without issue the past 5 days. I rooted and installed xposed and some modules (original broken phone was never rooted and was completely stock). Things were going great until tonight when it started reboot looping exactly like the old phone. I switched battery and same proble. After I took the battery out and left it out awhile it fired back up but I'm afraid the problem will return. Is it possible that the battery or charger randomly are causing damage to the phone? I only have 14 day warranty on this replacement and need to figure this out.
I have no idea maybe try just using your stock battery for a couple days. See how that goes then use your other battery for a couple days and see what happens.
i7vSa7vi7y said:
I have no idea maybe try just using your stock battery for a couple days. See how that goes then use your other battery for a couple days and see what happens.
Click to expand...
Click to collapse
I think it was one of the xposed modules causing the issue. I realized the rebooting seemed to happen whenever I pressed the power button. I had installed a power menu module so perhaps it was the cause. I restored from a nandroid and uninstalled that module and things seem to be working now. Hopefully that was the cause and this thing won't start acting up again after the return period.
killerz298 said:
I think it was one of the xposed modules causing the issue. I realized the rebooting seemed to happen whenever I pressed the power button. I had installed a power menu module so perhaps it was the cause. I restored from a nandroid and uninstalled that module and things seem to be working now. Hopefully that was the cause and this thing won't start acting up again after the return period.
Click to expand...
Click to collapse
That makes a lot of sense. Have to be careful with those Xposed modules. Don't get too carried away installing so many at one time and playing with them and then rebooting. You'll have a hard time figuring out which one is causing it. I'm pretty sure you found your problem.
i7vSa7vi7y said:
That makes a lot of sense. Have to be careful with those Xposed modules. Don't get too carried away installing so many at one time and playing with them and then rebooting. You'll have a hard time figuring out which one is causing it. I'm pretty sure you found your problem.
Click to expand...
Click to collapse
That is exactly what I did I installed like 6 at once and things were working well for a few hours then disaster stuck. I think I won't play with this phone anymore as I am upgrading anyway and want to sell it in working order.
So things were going well for awhile and then the reboot loops started up again. I did some digging and read that apparently Samsung phones are notorious for sticking power buttons and the symptoms were exactly what I was experiencing. I watched some videos online how to open the phone and clean out the power button but it didn't make a difference. I then read that squeezing the connector for the power button with a pair of pliers sometimes does the trick. Not for me. So finally since I'm not under warranty, have no insurance, and the phone wasn't working anyway, I just ripped the white plastic part of the power button right off. Well, that seemed to do the trick. Phone immediately fired back up without issue and has been going strong. I glued a small thin piece of plastic where the old one used to be and I am back in action. If my little plastic piece solution eventually fails or breaks off I will consider soldering on a new button but so far so good.
If you have tried everything else, and are looking for last resort, try cleaning the power button with some alcohol, and if that fails, rip off that power button! Here is the video that gave me the idea: https://www.youtube.com/watch?v=3Glllc7bEJs and here are some other power button videos: https://www.youtube.com/results?search_query=s4%20power%20button&search_type=&aq=f&oq=

I am about to go crazy with this evil phone. j320a variant with complete stock firm

Ok, so this all started about a week ago. My dad has had this phone and for the most part has enjoyed it. The other day he calls (from the house phone) to let me know that his phone doesn't work. I was expecting the typical black screen so hold all the buttons to force a reboot and boom hero for the day.
God no. This phone would suddenly not boot properly at all. I mean I had trouble getting stock Recovery mode to even come up or download mode. I bought a new battery thinking it could help. Twice now I have managed to use ODIN to reflash stock firmware of 7.1.1 . Both times the phone would be fine and suddenly it would turn off and bam the same thing over again. Firmware screwed and it doesn't want to turn on reliably. Recovery mode would display all sorts of errors with mounting /efs and dm verity errors....
This must be a hardware problem right? I don't know what else to think at this point. Is it possible the restore of his backup from sammy cloud is corrupting it? I am willing to try this one more time and not restore any of his files or is it hopeless? Is there something fried?
And just for the record, I am not new to ODIN/Rooting/Custom Roms/ etc but at no point EVER has this damn phone been attempted to be rooted or anything. I hope someone has something positive to share or just put me out of my misery so I can destroy this f******* phone into a thousand pieces.
Has anyone ever had an issue where the plastic back cover is somehow causing the phone to short out or overload which makes it freeze or turn off? I swear this back cover is the cause of all of this. Last night i reflashed everything and really just forgot to put the cover on. It stayed on all night without a single issue. I rebooted and powered down multiple times and it turned right back on. Then I put the back cover on and what do you know, difficulties with powering on and freezing.
On the top right above the sim/microsd slot there is that spot with metal looking conduction material or something and it is also at the bottom near the charge port. What are those things? At this point the phone has become a pet project and I just have to have the answer. My dad already got a new phone lol. Any ideas?

Damaged screen causes reboot, eventually gets stuck in boot loop

Hello, so I have a J7 2017 (SM-J730GM/DS) 32 GB Unlocked Dual SIM which has served me well for a while. I ended up dropping the phone at some point in a sliver of time without a case and the screen cracked. After replacing the screen I noticed if the screen was pressed in a certain area it would go crazy and reboot the phone (crazy as in the pixels would do weird things like dimming, going grainy, like the display shorted in some area, then the phone would reboot itself), probably some error on my installation of the screen and the ribbon cables (I can see an area where it looks creased, it never sat flush with the body of the phone as the OEM screen did). I was able to just be careful and not trigger the reboot for some good time until it happened again and the phone would continuously reboot, allowing me to only get back to the OS through the boot menu, selecting "reboot now". That worked for a while until it would never boot into the OS, just looping at the screen where it says the phone name, where it would vibrate, go black, and go back to the phone name screen. I gave up trying to fix it, as I had a backup phone, and just now had some ideas. I figure the OS is corrupted in some way, I am no master in knowing the details on how phone boots up and such, so I did some research and successfully flashed the most recent ROM onto the phone using Odin 3.14. It still doesn't stop the looping, unfortunately.
Any ideas? I hear people talking about using TWRP or something to do things boot related, but I don't want to possibly mess anything up further nor do I know what they were talking about.
Thanks,
Stella

Need help identifying Bootloop cause on my M1A1

Greetings everyone,
As the title of the thread states, I have in my possession a M1A1 that is stuck on a Bootloop.
First of all, let me explain the situation a bit. This phone was accidentally put inside a washing machine, lasting inside there for what may have been a good 20 minutes until it was noticed there and promptly removed.
Upon removal it was still showing some signs of life, such as the LED lights going off. My first decision was to quickly open the phone and remove the battery in order to avoid further possible damage. I then decided to disassemble the phone while at the same time removing the water and letting the components dry up in a lit location. Once they dried up, I proceeded to wash them with alcohol, fully bathing the motherboard while giving a slight rinse to the other components, and used a soft brush to very gently clean the slight corrosion that formed in some places. I repeated this process up to 4 times, each time letting the components dry before giving it another go. It is worth mentioning that i was not able to remove the electromagnetic shielding due to the lack of tools.
Upon seeing no more corrosion, I decided to reassemble the phone and test if it was still alive. To my surprise, it did actually turn on. However, once it got to loading the OS, the loading bar got frozen and the phone restarted, resulting in a bootloop. I argued that maybe, somehow, the OS may have been corrupted, and I decided to try to flash a new ROM. I don't exactly remember whether I first tried via Fastboot or if I went straight to unlocking the phone in order to use TWRP, but long story short, I ended up unlocking the phone and therefore wiping all the data, however allowing me to freely use TWRP to flash new ROMs.
In retrospective, that may have been an extremely foolish decision, as no matter which ROM I tried, the result was the same as it previously was: The phone shows the Mi logo, it then starts loading the OS, the loading animation freezes up, and then restarts. So not only did I end up wiping all the data, but I am still stuck with the same problem.
This is my main issue. I do not know how to identify what is causing this Bootloop. The phone is at least somewhat working, seeing as how I am able to fully use TWRP. Is there maybe some component that may have been fried that is preventing the booting sequence? I would really appreciate some pointers. Thanks.
Something similar happened to me using the adriane tool , I resolved it by unpluging the phone from the PC and the forcing the phone off and rebooting into fastboot mode, and when I got it to boot the first boot was slow, A couple minutes maybe ?. I don't know if this can be helpful, I wish I could do more bro.
lionr2 said:
Something similar happened to me using the adriane tool , I resolved it by unpluging the phone from the PC and the forcing the phone off and rebooting into fastboot mode, and when I got it to boot the first boot was slow, A couple minutes maybe ?. I don't know if this can be helpful, I wish I could do more bro.
Click to expand...
Click to collapse
Hmmm, I don't think this approach would work for me. I have tried every possible rebooting combination to no result, but I really appreciate the help man.

Categories

Resources