Database Users

[Q] URGENT HELP with a fully bricked defy

Hi Everybody,
I believe that I am now in serious trouble with my Motorola Defy. I have tried to look everywhere today to find a similar problem to what I am experiencing, and although I can find all the problems, I can't find anyone which has happened like this. It would be so great if someone could help me. I am so so desperate and in total panic right now. I need this phone to work which I had bought in Germany (where my home base is set up) but I am currently working in Estonia where salary really does not allow me to just go out and buy a new one - not even a cheap 20€ phone.
I originally bought the phone about 1 1/2 years ago with Android 2.1. After about 6 months I did the official update to Android 2.2. This is where a few things started to go wrong. Google maps would crash the phone so that I would have to take the battery out to restart it. The camera didn't work properly, and not at all with the flash, and the phone would quite often restart itself. I could however live with all this and just accepted it as I didn't want to do anything to make it worse - I trust myself 100% with computers and there isn't much that I can't do with them. But with phones, that's where I have to put my hands up as I really don't trust myself to do anything because of the fear of bricking one.
Anyway, today as I was using the phone after taking a few pictures the phone had frozen, so as always I took the battery out and turned it on again, when it loaded up and as soon after I put my pin and unlock number in, it restart itself, So I again I put my pin and unlock number in, and it restarted itself. After this I couldn't even put my pin number in.
I then did went into Bootloader to do a wipe and restore, This however, after taking two hours and just watching the yellow dots move along, was clear to me that this also wasn't working. After coming home from work I then copied the instructions found I think in the Beginners Defy Guide on this site for using RSD Lite and an SBF File. This then failed and in Bootloader it also then said Corrupt.
So I then started to watch a video on youtube for a complete guide from unbricking to installing CM10 (something I wanted to do the whole time and never trusted myself). Meanwhile, whilst everything was downloading, although the phone still had about 60% battery, I thought I would plug it in just to charge it for a bit, this however also did not work but I left it in just in case it was working.
After everything was finished downloading, I unplugged the phone from the wall and now it won't even turn on,, neither in Bootloader, or the screen. It does NOTHING! :crying::crying:
When I plug it into the computer the little white led light comes on (top left of the phone) and the computer makes the sound that something is plugged in. This is also recognised my RSD Lite, however once a file has been created it cannot be flashed. It's like the phone is there, but it isn't.
I am really desperate to get this working as I really need this phone for work, and like I said just cannot afford to run and buy anything.
I'm very sorry if I have posted this in a wrong area, but I honestly did try to find something. I just don't understand how plugging it in to charge can stop it from not even opening bootloader, It's like it's got a mind of it's own.
Thank you very very much for reading, and I apologise that it's so long,
Best Wishes,
Steve

To get into the bootloader , keep the volume up button pressed and then press the power button. Is this what you tried to do?
And I didn't get the part where you wiped through the bootloader. As far as I know there is no option there. Do you mean the stock recovery?( The yellow dots are there in the stock recovery)
Sent from my MB526 using xda app-developers app

wahat3 said:
Hi Everybody,
I believe that I am now in serious trouble with my Motorola Defy. I have tried to look everywhere today to find a similar problem to what I am experiencing, and although I can find all the problems, I can't find anyone which has happened like this. It would be so great if someone could help me. I am so so desperate and in total panic right now. I need this phone to work which I had bought in Germany (where my home base is set up) but I am currently working in Estonia where salary really does not allow me to just go out and buy a new one - not even a cheap 20€ phone.
I originally bought the phone about 1 1/2 years ago with Android 2.1. After about 6 months I did the official update to Android 2.2. This is where a few things started to go wrong. Google maps would crash the phone so that I would have to take the battery out to restart it. The camera didn't work properly, and not at all with the flash, and the phone would quite often restart itself. I could however live with all this and just accepted it as I didn't want to do anything to make it worse - I trust myself 100% with computers and there isn't much that I can't do with them. But with phones, that's where I have to put my hands up as I really don't trust myself to do anything because of the fear of bricking one.
Anyway, today as I was using the phone after taking a few pictures the phone had frozen, so as always I took the battery out and turned it on again, when it loaded up and as soon after I put my pin and unlock number in, it restart itself, So I again I put my pin and unlock number in, and it restarted itself. After this I couldn't even put my pin number in.
I then did went into Bootloader to do a wipe and restore, This however, after taking two hours and just watching the yellow dots move along, was clear to me that this also wasn't working. After coming home from work I then copied the instructions found I think in the Beginners Defy Guide on this site for using RSD Lite and an SBF File. This then failed and in Bootloader it also then said Corrupt.
So I then started to watch a video on youtube for a complete guide from unbricking to installing CM10 (something I wanted to do the whole time and never trusted myself). Meanwhile, whilst everything was downloading, although the phone still had about 60% battery, I thought I would plug it in just to charge it for a bit, this however also did not work but I left it in just in case it was working.
After everything was finished downloading, I unplugged the phone from the wall and now it won't even turn on,, neither in Bootloader, or the screen. It does NOTHING! :crying::crying:
When I plug it into the computer the little white led light comes on (top left of the phone) and the computer makes the sound that something is plugged in. This is also recognised my RSD Lite, however once a file has been created it cannot be flashed. It's like the phone is there, but it isn't.
I am really desperate to get this working as I really need this phone for work, and like I said just cannot afford to run and buy anything.
I'm very sorry if I have posted this in a wrong area, but I honestly did try to find something. I just don't understand how plugging it in to charge can stop it from not even opening bootloader, It's like it's got a mind of it's own.
Thank you very very much for reading, and I apologise that it's so long,
Best Wishes,
Steve
Click to expand...
Click to collapse
Check out this link all the best :good:

[Q] Adventures in SMQ, Brickedness, and Little Green Lights

Hello all; apologies in advance if this is retreading old ground, but I couldn't find anything about this on the forum as is.
So, while taking some video the other night, my Razr M (all recent software/OS updates, stock software + commercial apps , no flashed ROM/no root/hell, I wasn't even using GoLauncher anymore) decided to freak out on me. By the end of the night, it got itself stuck on booting, and by the next day, it's more or less bricked. Called, got my replacement phone from Verizon, but before I ship this off, figured I'd plug it into the PC and see if there was anything I could do to salvage data -- most things are backed up, but the video/things from that day obviously aren't.
So, no screen. When I plug in, I get the little green light intermittently. For fun, I tried getting to a boot screen (Vol down/Vol up/Power), and now I have this fun thing where my PC tells me it's installed "Fastboot SMQ S" drivers, and is "searching preconfigured folder drivers". Every few seconds, the phone's light will be green, a few seconds later, it will go off. Likewise, my device manager keeps trying to recognize a Human Interface Device, and now and then Windows tells me a connected device has failed. (Once every now and again it tells me it can't recognize it, for about a half second.)
I should note that at no time during any of this does the screen on the phone itself give me any sort of image or feedback.
This leads me to think there's still something inside the phone fighting to work -- as stated, I don't need it to get back to functionality per se, but if there's enough left to work with to at least pull data off of it before it clinks out, I'd be quite happy.
This seemed like a question for the XDA folks, even though it isn't mod/dev related, because you guys are usually the forum I read when I have questions, as you all seem to really know the insides of the phones and systems. If there is a better forum/place for asking this question, please just let me know. I'd be grateful for any sort of advice/insight you may have.
Thank you, and have a great afternoon!
p.s. I assume, based on other similar threads, that the whole "stealthily open the case, yank out of the flash and kitbash it into my pc while somehow not voiding the warranty" route is unfeasable/undoable. If this is not the case, I'm game for that. I'm not a phone dev, but I've seen the inside of an electronic device or ten in my time, so I might be able to pull it off.

Need Help with APX Mode Brick.

Running (was) a stock rooted N7 v1 on 4.3. Bought a data recovery tool off of the play store to try and recover some photos I had deleted. At some point it rebooted into safe mode, my battery was running low and I shut it off to let it charge. Now it's dead in the water. Stuck in APX mode. I am asking if there is anyway to breathe life back into this tablet.
The tablet does nothing on the screen, period, no matter what you do. When plugged in to a computer it sometimes registers as an unknown device, sometimes APX. None of these get you anywhere. Toolkits on these forums won't recognize the device, installing the android development kit and drivers does nothing, executing commands from the command line is worthless because the device won't register. I do not have any "blobs" and have no clue at this point even what they are or what they could have done for me had I made them.
I've searched this forum and found bits and pieces here and there and wanted to start a thread dealing solely with devices stuck like this and what has or hasn't worked and get others input if warranty service was done and the state your tablet was in when you sent it in (locked/unlocked, rooted etc).
Anyone stuck here will have probably tried the same things as I have but here is is a minor rundown...
1) Every button combo press known to man for short, medium, and extended periods of time.
2) Charging with the Original charger/cable for 1 hour, then button presses then charging for 12 hours.
3) Same as above but with different aftermarket chargers at different amperages.
4) Uninstalling and deleting drivers. Trying different drivers. Getting the Android drivers etc.
5) Trying every toolkit on the forums to no avail because the device won't register.
6) Checking to make sure the battery cables are seated correctly.
7) Screaming and yelling at your new paperweight.
My hope here is that I've missed some important thread about recovery and someone can point me in the right direction. Failing that, if I should get a new mobo or try and send it in for warranty service in the state it's in.
Any help would be much appreciated.
Sent from my Rooted Frameworked SCH-I545 using xda app-developers app

I don't know what you tried before to revive your tablet and what the tool did to get you into this state, but generally APX mode can be left by pushing the power button *only* for about 10-20 sec, as long as there us enough power within your battery and the hardware / software is working / consistent.
Sent from my Nexus 7 using xda app-developers app

I don't think I've ever seen anyone in here describe a situation where they observed the tablet in bootloader mode without seeing *something* on the screen.
And as you found out through your reading, using "nvflash" on the N7 is only useful at this time for folks that made prior disaster recovery preparations. So, APX mode is of no use to you (at this date 12/2013).
So, until you see something happen on that screen, drivers on a PC are of no value to you anyway.
It is really unfortunate that the N7 doesn't have a physical charging indicator - that makes it difficult to distinguish between a tablet which is truly borked vs. one that refuses to boot simply because the battery isn't charged.
Holding down a specific button combo (iirc Pwr+VolUp) during an attempt to get "something, anything" to happen will put the tab into APX mode, so it isn't particularly diagnostic that you have observed APX mode once or twice.
Really about the only way to know if the battery in a non-responsive N7 is charged or not is to put it in another tablet or measure the open-circuit voltage. (About 4.15v fully charged & about 3.5v discharged)
The reason that I mention this is that there have been a few reports from users in similar straits as you that report something like "I don't know what happened, but I tried it a few days later and all of a sudden the tablet booted up". Almost every one of those reports involved mentions of low battery conditions, just as your narrative does.
I don't know what file recovery program you used, but I suspect that is a red herring . It might have to have root privileges in order to read raw partitions, and might even want the tablet in safe mode to minimize write activity by *other apps* while it does it's forensics, but it certainly isn't going to recover files by writing in raw mode on a mounted, live filesystem - it would do all it's writing through normal kernel syscalls. That's the long way of saying that a low battery is more likely to be the original source of your troubles.
So what to do now? I think the first order of business is to figure out if your battery is charged or failing to take a charge. If it really is well charged, then a warranty return is probably in your future.
If you can't find a second N7 or a voltmeter, then you could try just leaving it on the charger for a couple of days... but that really is just a "grope about in the dark, wing & prayer" kind of strategy.
good luck
Button sequences & USB Identifiers (VID/PID pairs):
http://forum.xda-developers.com/showthread.php?t=2133986

You are in the same situation I was in - nothing shows up on screen. I got APX drivers to finally install (had to search all over the internet to find them) and that STILL didn't help. I was never able to get it to come back. Nothing ever showed up on the screen.
No combination of button presses helped. I finally gave up and, since my N7 was still under warranty, I RMA'd it back to ASUS. It took about 3 weeks, but I got it back with a new motherboard installed on it.
It was borked and your's sounds the same way as mine. Just either register your N7 on the ASUS website and RMA it that way, or call it in over the phone and RMA it that way. Hopefully, you still have the box your N7 came in because you'll need the serial number.
Others have stated you can get it by opening the back, but that will void your warranty. I do believe you MUST have the serial number, so find the box and get it from there.
Also, you'll definitely lose everything that was there, especially if they replace the motherboard. So hopefully, you backed it up. I backed mine up just before it got borked, so I was lucky.
Good luck!

I am wary of trying to do the battery swap. I went and bought a new version after it crashed but I would be voiding both warranties to try the battery swap.
I do have the serial number if I want to try and get service.
I have done some reading about "deep discharge" battery issues and I suspect this may be a part if it but I have tried leaving it plugged in for days and nada.
I don't know if there is a way to "shock" or jump start the charging process and I am going to put the multimeter on it tomorrow and see what I get.
Thanks for everyone's input. I will keep you up to date.
Sent from my Rooted Frameworked Verizon Galaxy S4 on MJ7 using the XDA App.

Black Screen Of Death (New OPT just out of the box)

Hello Guys,
I am posting this thread with a great deal of frustration and of course i'll try to leave the emotions out of this, although it's pretty hard (since that's NOT how i imagined i'll unbox the OPT which i was waiting for, for so long).
Anyways,
I'll cut to the point, I received my OPT package and happily went a head opened the box (hoped not to get a broken phone or anything (like someone who posted a thread here), and indeed the package looked okay and the device looked good (physically speaking).
I started the phone, and i can see the black background white android logo, and then.. Black Screen... I'm telling myself "Ahh that's probably nothing.. let's wait a bit or worse case another restart" waiting didn't help and as you probably know restarts did not help as well.
Okay, since i am not newbie to the android troubleshooting, i said to myself, probably a bad OS boot or some sort of OS issue, let's enter the RECOVERY to reset / wipe / factory reset.
Volume Down + Power Button, can't enter recovery just a Black Screen showing.
Starting the phone again regularly shows the Black Screen but the buttons are glowing blue and if i click on the volume buttons i can hear the sound tick.
Okay, at that point i was getting a bit worried, no recovery, several reboots and Black Screen when going to recovery or normal mode.
So now, i knew i had to go over and search the forums (XDA | One Plus) for more solutions on soft bricked / hard bricked devices.
I found the restoration thread of:
http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449
Including the QualCom driver method and 2 FULL restoration kits (1 Hidro OS 1 Oxygen).
I followed the steps (trying first the lighter Hidro Kit (without .img's of system etc') finished the process but when it should logon to recovery SAME result.
Then i went ahead and tried the OxygenOS recovery kit, same procedure it finished, phone restarting but same Black Screen.
This is where i am at right now, very frustrated, i raised a TT to the one plus support, i will update how it goes, i assume i passed most of the troubleshooting phases but if anyone has ANY ideas on how to proceed or assist i would be glad to try it out.
In addition i will use this stage to also update on the OnePlus support (refund wise, and TT dealing wise) as i think it's also important to report on the support when actual problems occur and how they handle it.
In any case guys, thanks for reading this, i really hope you will receive your products WORKING as they should, there's not much worse things when it comes to getting a NEW device starting it for the first time and not being able to use it, after waiting for so long for it.
--Video is also attached below.
https://dl.dropboxusercontent.com/u/33088939/20151005_132402.mp4
I will keep you updated.
Thanks & Regards,

Rest in peace. Contact Oneplus support m8 and send that **** back
Sent from my ONE A2003 using XDA Free mobile app

Small Update: I just wish you all to never wait for the OP customer service / technical support. (waiting time is really outrageous for a company which support customers online).
In addition, the technical support team sent me files to download (while i'm explaining her that i tried all of those already) + sending me ROM for OPO (Cyanogen........)
I was in a kind of a shock, while i'm correcting her and telling her there's no CM for OPT and the files she sent me (CM11s?!) are not the correct ones, she sent another mail.
Anyways, i guess you have to go for that "entire process" until they allow you to get a refund.
Hate to type it, but for me it's probably "Never Again" instead of "Never Settle".

CS is the same for most companies, someone in a call centre with little knowledge and a book of instructions to follow. There's no point you saying "I did this already" because they get in trouble if they don't follow the script they have.

I have got the black screen of death too and im a couple of mot=nths into using it
[/COLOR]
Tricepz said:
Hello Guys,
I am posting this thread with a great deal of frustration and of course i'll try to leave the emotions out of this, although it's pretty hard (since that's NOT how i imagined i'll unbox the OPT which i was waiting for, for so long).
Anyways,
I'll cut to the point, I received my OPT package and happily went a head opened the box (hoped not to get a broken phone or anything (like someone who posted a thread here), and indeed the package looked okay and the device looked good (physically speaking).
I started the phone, and i can see the black background white android logo, and then.. Black Screen... I'm telling myself "Ahh that's probably nothing.. let's wait a bit or worse case another restart" waiting didn't help and as you probably know restarts did not help as well.
Okay, since i am not newbie to the android troubleshooting, i said to myself, probably a bad OS boot or some sort of OS issue, let's enter the RECOVERY to reset / wipe / factory reset.
Volume Down + Power Button, can't enter recovery just a Black Screen showing.
Starting the phone again regularly shows the Black Screen but the buttons are glowing blue and if i click on the volume buttons i can hear the sound tick.
Okay, at that point i was getting a bit worried, no recovery, several reboots and Black Screen when going to recovery or normal mode.
So now, i knew i had to go over and search the forums (XDA | One Plus) for more solutions on soft bricked / hard bricked devices.
I found the restoration thread of:
http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449
Including the QualCom driver method and 2 FULL restoration kits (1 Hidro OS 1 Oxygen).
I followed the steps (trying first the lighter Hidro Kit (without .img's of system etc') finished the process but when it should logon to recovery SAME result.
Then i went ahead and tried the OxygenOS recovery kit, same procedure it finished, phone restarting but same Black Screen.
This is where i am at right now, very frustrated, i raised a TT to the one plus support, i will update how it goes, i assume i passed most of the troubleshooting phases but if anyone has ANY ideas on how to proceed or assist i would be glad to try it out.
In addition i will use this stage to also update on the OnePlus support (refund wise, and TT dealing wise) as i think it's also important to report on the support when actual problems occur and how they handle it.
In any case guys, thanks for reading this, i really hope you will receive your products WORKING as they should, there's not much worse things when it comes to getting a NEW device starting it for the first time and not being able to use it, after waiting for so long for it.
--Video is also attached below.
https://dl.dropboxusercontent.com/u/33088939/20151005_132402.mp4
I will keep you updated.
Thanks & Regards,
Click to expand...
Click to collapse
So the phone should be responsive even if you cant see the screen. SOOO forget letting it drain, but instead, connect it to pc and install latest twrp. Or crm. Unlocking the bootloader may be difficult as you have to use the power and volume buttons to choose yes or no but i think it starts on yes so just press the power button. Now copy over any rom and gapps (i used exodus and lollipop gapps). Flash them and the phone will boot up surprisingly quickly. This will hopefully stop you from wasting time with support teams that are already overloaded with queries. I hope this helped

I have the same problem I dont know what to do! please someone help !

This is really old news, I'll just add that I've sent the device back and got my money back,rocking a new lg v10 and happy a hell.
Sent from my LG-H960 using Tapatalk

LG randomly overheating and won't stay on - No previous heat issues

Hi, I have a LG K20 Plus. I currently can't turn the phone on, so I don't have much software information to give you. The phone was bought at T-Mobile (Metro by T-Mobile) and I had a SafeLink sim card and a 16 gb micro sd card inserted when the issue started. I have since removed both. It says Qualcomm snapdragon on the screen when it starts. It was also rooted and the bootloader is unlocked.
I broke the screen on my phone and I decided to do the repair myself. I have done about 7 or 8 screen replacements and I actually did this phone a year ago with no issues, so I felt I could manage this one as well. I bought an entire display (from ebay) and switched it out with no problems. Initially it worked great! I used it for a few days before realizing that I had no sound. I opened it back up and noticed the loud speaker had fallen out. I found it, put it back in, reassembled it as I normally do and turned it on.
NOTE: when I was reassembling it the second time, I actually tried to put a screw in a hole that wasn't a screw hole. I used a light to normal amount of pressure but I didn't force it. I think it's the hole where the moisture detector is. Picture #1
I turned it on and right after the logo screen I got a message that said "High temperature detected Powering off for your safety" and it immediately shut off. The phone does appear to charge normally but it won't stay on. I did a factory reset (I'm not sure if it's still rooted but the bootloader is still unlocked). I also switched back to the old (broken) display just to check if that would work. I couldn't see any difference in the shielding but I switched them just to be sure. I bought a new battery and installed it. I took a q-tip and 95% Isopropyl Alcohol and cleaned pretty much the entire motherboard, paying special attention to the battery connections. After each one of these things, I tried to start it with the same error message immediately upon start up.
NOTE: At no point has the phone every physically felt hot or even warm. I don't think it's on long enough for it to get hot. But something is wrong and I have no idea what it is. I, literally, took the phone apart, put in the speaker and put it back together in less than 5 minutes. Could it be I just bumped something and knocked it loose?
I searched for any information I could find both here and with google but there is next to no information on the LG K20 Plus. I did find some information on the LG V20 that had overheating issues, and that has been all the luck I've had. I watched several videos and it seems the solution is to apply thermal paste. But my phone doesn't have any evidence that thermal paste was ever on it. I went and bought some but I have no idea where exactly to put it or even if it's needed. Most videos showed people using some kind of aluminum foil but I'm not sure if that is safe. I have several old phone laying around and I managed to get some of the silver tape and a copper square thing but, again, my phone did not have these things to begin with. I don't want to start adding things only to make it worse.
There is a slight difference of the tape that is on my phone now (the display I just bought) as compared to the old one (broken display). Picture #2 Again, I have no idea if that means anything but I thought it worth mentioning. Picture #3 is how it looks now as if I were going to put it back together. Picture #4 is the part (don't know name) where the videos show to apply the thermal paste and the shielding.
I'm really at a loss as to what to do next and I can't really afford to take it in to have it repaired before next month. If anybody has any insight or answers as to what happened, I'd be very grateful for your help. I'm sorry for the long post. I just wanted to tell you everything I have done in detail. Thank you

If you're using Kernel Auditor or any other kernel adjustment simply reset to default and use only ondemand or interactive. There's also options for the thermal portion of the kernel, don't mess with those. If VCC or another thermal option was checked off turn it back on. Putting the GPS to the moderate setting (the one below high accuracy) will keep the temps down as well. Are you using a custom ROM? If you're on Discord you can feel free to message me SCOPE★ BRΞΛD #8460 . I am only offering that so we can get this resolved quickly for you, just copy and paste since I use special characters.

Omgosh, thank you so much for taking the time to respond! Although I'm sure everything you are saying is very smart, I have absolutely no idea what you're saying. I'll do my best to try and answer you. I don't know what SCOPE is or how to send a message there. I don't think I'm using any thing for the "kernal". Also, I don't know what VCC or Discord is. As far as turning off setting for GPS or any other app, the phone will not stay on. I get about 1 sec after the logo when it boots up, then the error message about overheating and it immediately shuts off. I did a factory reset so everything should be good to go as far as apps. I don't think I'm using a custom ROM. The only thing I did was install TWRP, unlocked the bootloader and rooted the phone a year ago but nothing since then. As I stated earlier, this happened right after I did a display repair. Is there something on the MOBO that can get bumped that will make your phone get hot or send a overheating error. My phone doesn't show any sign that there was ever thermal paste on it prior but should I add some now. Will that help?

Update... Now the phone does not power on at all. When I plug it in to charge it I get an error that says "Device temperature is too high or low. Please move to another place to charge. I wonder where you went. I googled SCOPE so I could sign up to message you like you asked me to but nothing but definitions came up. I know I'm out of my league here. You guys all talk so technical. I didn't understand one thing the person asked me for. I know it's rare to get a response as quickly as I did and I was so happy to see someone had responded. Now, I just feel stupid and defeated. I thought this site was inexperienced with cell phones friendly. I'm just trying to get help so I don't have to go out and buy another phone again. Can someone refer me to a site that is more directed toward people who don't know much about the technical side of cell phones... please! Again, thank you for your time.

HelpNeededPlz said:
Update... Now the phone does not power on at all. When I plug it in to charge it I get an error that says "Device temperature is too high or low. Please move to another place to charge. I wonder where you went. I googled SCOPE so I could sign up to message you like you asked me to but nothing but definitions came up. I know I'm out of my league here. You guys all talk so technical. I didn't understand one thing the person asked me for. I know it's rare to get a response as quickly as I did and I was so happy to see someone had responded. Now, I just feel stupid and defeated. I thought this site was inexperienced with cell phones friendly. I'm just trying to get help so I don't have to go out and buy another phone again. Can someone refer me to a site that is more directed toward people who don't know much about the technical side of cell phones... please! Again, thank you for your time.
Click to expand...
Click to collapse
Hey, I just wanted to say sorry this happened to you. The same thing happened to me. My LG K20 Plus, no matter what button combinations I push and for how long I hold them, will not turn on or go into download mode. Plugging it in to a charger or PC does nothing either. Before it got to this state, I got the infamous green screen of death/Demigod crash handler (google this--it's a known issue with some models of LG phones and it happens when they overheat). It's definitely a hardware/build issue, and especially since this issue keeps the phone from turning on or connecting to a computer, I don't see a workable fix short of buying a new phone, unfortunately. Again, I'm in the same boat so I'm not happy about it either. I would say XDA is by far the best site to find a fix to this sort of problem, so if no one here has any suggestions on how to fix it, I think you (we) may be out of luck.

Thank you for letting me know. I'm not sure of some of what you said but I did catch the bottom line. Basically, just hold onto the phone until someone here comes up with a fix or workaround? I have a question for you. Did your problem start after you did some kind of repair? I'm wondering if I bumped something on the mobo to make it give a false overheating error. Do you happen to know where that sensor might be located? Sorry you are having problems to. It really stinks when your phone breaks and no matter how much time and energy you put it to figuring out the problem to fix it, there just isn't any good answers out there. I wish you lots of luck and if you figure anything out, please update here so I can try it too.

You need a whole new phone.
That or you're gonna have to replace the hardware