Database Info

Stock and unrooted but acting weird

I was using an app on Sunday, when the app froze completely and the screen of the s3 went black. The only thing I could see was the status bar up top, but even that was unresponsive. So I pulled the battery and turned it back on, and it was acting extremely slow so I got impatient and started trying to get into settings, when it went unresponsive again.
This time I held down the power button to see if I could get it to respond and the lock screen came up, without my wallpaper and instead of Verizon Wireless at the top, it said "No Service". After a couple of seconds my wallpaper showed up and then it said Verizon Wireless. After I get through the lock screen, I would go through the same whole routine - e.g. try and get into settings, freeze, hold power, have it come back up, etc. So I battery pulled again.
Finally, I got it to boot OK, by just letting it be for 10 minutes and completely ignoring it.
However, today my battery drain was pretty fast, it was on for 12 hours and was down to 40% after only 30 minutes of screen time. The culprit was "Android System" at 61%, i've never seen this that high before. Because of the high "Android System" power usage, I thought it might be good to power it down. Upon boot up, I assumed I'd be able to use it immediately, so I started going into Settings, and yet again it went unresponsive.
Are the two issues unrelated? What should I do?
As a warning, I'm extremely new to anything smarter than a Nokia brick, so be patient - Thanks!

As inconvenient as it is, I would recommend a full system wipe and go back to out of the box. That seems to fix everything and unfortunately it is rather difficult to diagnose issues on phones, especially unrooted.
In order to do a wipe you can do one of two things, goto settings then backup and reset, then hit factory data reset.
-OR-
Turn off the phone. When you start it again hold volume-up, power, and home to get into recovery. Then do the factory reset.

Ok, I thought that's what my option was. Thanks dwibbles.

[Q] Samsung Galaxy Tab 2 10.1 Hacked, Touchscreen unresponsive

Samsung Galaxy Tab 2 10.1 Hacked, Touchscreen unresponsive
Hi! I need help with my tablet.
Device: Samsung Galaxy Tab 2 10.1 Tablet, model GT-P5113 TS. This model doesn't have a way to yank out the battery.
What's wrong: Touchscreen is not responding.
Current state: Attempting to drain the battery. Doesn't appear to be turned on. Factory reset apparently performed.
What happened: Sorry, this is long. It is as best as I can remember it. It may be somewhat inaccurate.
Yesterday evening, I was on my Windows laptop and logged into my Google account. I *thought* I used the Google Play Store to install Chrome to the tablet. (I had looked at the html5test website and it said Chrome had a higher HTML5 rating than the Dolphin/Jetpack browser I've been using on my tablet.)
But something went terribly wrong.
After sending Chrome to it, I unlocked the tablet and used both Chrome and Dolphin to go to html5test website. They both scored the same or nearly the same. I don't know if any of that is relevant, but I'm including it just in case.
At some point after that, I woke the tablet with the power key and used my unlock pattern on the dots lock screen.
That's when I saw what I believe was mal-ware in action. The settings menus were scrolling and sub-menus being selected, all by themselves. I couldn't say exactly what was changed because whatever program or script that was running the process was going extremely fast.
When I realized it might be trying to send out data over my Wifi network, I turned off the Wifi router in my home.
I repeatedly held down the power key to turn the system off, but doing so only rebooted back to the useless lock screen which was not responding to anything. The normal method of holding the power button for a few seconds to bring up the menu and then tapping the "Power Off" option on that menu refused to power off the system. Nothing on that menu responded to touch.
Entering my pattern on the lock screen did absolutely nothing. I didn't even see any lines traced when I ran my finger over the screen.
At some point, I pulled out the external SD card. I have no idea if whatever hacked the tablet also put a copy of itself on the SD card.
I called a friend who looked up how to restore the tablet to factory settings. I didn't understand the directions exactly, so I ended up on a screen with a Warning!! about installing a Custom OS. (Holding down the Power + Volume Up seems to get me there)
I left it on this screen, and I turned my router back on and using my laptop, contacted Live Chat at Samsung but they didn't understand my problem. They told me to reboot the device and swipe my pattern several times and then after several failed attempts I would have the chance to use my Google credentials to get into it. But the device apparently never registered that my swipe attempts were failing.
So my device was booted up with me locked out, with the WiFi router on for a little while again. I turned off the router as soon as I realized that. That disconnected the chat session, but since Samsung chat wasn't helping me anyway, I didn't bother trying to go back.
I got the device back to the "Warning!!" screen. Then turned the router back on and searched for how to do a factory reset of the device. I found a video on YouTube and followed it.
I pressed the Volume Down and Power buttons simultaneously, followed by letting go of the power button. That brought up a menu which contained several options, including an option to do a factory reset. I used the volume buttons to highlight that and pressed Power key. A second screen came up and I used the volume buttons and power button to select "Yes" to confirm the reset.
It appeared to have done a factory reset, rebooting eventually.
However, after that, when I tried to tap on the touch screen to move forward through the selections, the touch screen was still unresponsive!
So I brought back the "Warning!!" screen and ran the battery down until the screen was blank and it wouldn't start when I held the power key.
Then I charged it for about 20 minutes and rebooted it. I think when it came back it was on the Recovery menu. I think I did a second factory reset, but not 100% sure. It eventually rebooted after a lot longer than usual.
When it came up, it was saying battery was low. I tried to tap the OK button, but nothing happened. Behind the battery window was the first setting screen to set up the device for the first time after a factory reset. (I think selecting USA?)
I brought back the "Warning!!" screen and left it on overnight so that the battery would run down.
That was about 8 hours ago. When I woke up, I used clear tape to keep the power button pressed down, to ensure that the battery will continue to run down.
____________________________________________
What do I do next? How do I get the touch screen to start working again? It is not a hardware problem, unless mal-ware can break the hardware. The touchscreen had been working fine until this happened.
Should I take the tablet back to Best Buy where I bought it at least a year (maybe 2 years) ago? I don't know if it's still under warranty.
I have over 20 year of experience as a software developer, but not for Android. I am not very experienced with doing anything to hardware.
Should I try to fix it myself?
I have never rooted any Android device and I'm not sure what that means, either.
I've never re-installed the ______ ? (rom? image? Odin?)
I read on this and/or other forums that there's a way to replace something, but the instructions were beyond my level of understanding. I would need the procedures to be broken down into steps which don't assume too much about what I know.
I understand how to download a file to Windows, given a URL for it. I understand what a zip file is and how to extract it. I understand how to press hardware buttons and plug in cables, and do these steps in the order I'm told.
I don't understand what I'd use to get the downloaded whatever-they-are onto the tablet to replace whatever-the-other-thing-is so that the touchscreen works again.
As far as I know, Odin is a Norse god.
The only firmware updates I've ever done are the ones that the device does on it's own through Samsung's updates.
I'd deeply appreciate getting this device back since I have extremely limited funds and probably won't be able to buy a replacement.
Thank you,
Linda

LMurphy said:
Samsung Galaxy Tab 2 10.1 Hacked, Touchscreen unresponsive
Hi! I need help with my tablet.
Device: Samsung Galaxy Tab 2 10.1 Tablet, model GT-P5113 TS. This model doesn't have a way to yank out the battery.
What's wrong: Touchscreen is not responding.
Current state: Attempting to drain the battery. Doesn't appear to be turned on. Factory reset apparently performed.
What happened: Sorry, this is long. It is as best as I can remember it. It may be somewhat inaccurate.
Yesterday evening, I was on my Windows laptop and logged into my Google account. I *thought* I used the Google Play Store to install Chrome to the tablet. (I had looked at the html5test website and it said Chrome had a higher HTML5 rating than the Dolphin/Jetpack browser I've been using on my tablet.)
But something went terribly wrong.
After sending Chrome to it, I unlocked the tablet and used both Chrome and Dolphin to go to html5test website. They both scored the same or nearly the same. I don't know if any of that is relevant, but I'm including it just in case.
At some point after that, I woke the tablet with the power key and used my unlock pattern on the dots lock screen.
That's when I saw what I believe was mal-ware in action. The settings menus were scrolling and sub-menus being selected, all by themselves. I couldn't say exactly what was changed because whatever program or script that was running the process was going extremely fast.
When I realized it might be trying to send out data over my Wifi network, I turned off the Wifi router in my home.
I repeatedly held down the power key to turn the system off, but doing so only rebooted back to the useless lock screen which was not responding to anything. The normal method of holding the power button for a few seconds to bring up the menu and then tapping the "Power Off" option on that menu refused to power off the system. Nothing on that menu responded to touch.
Entering my pattern on the lock screen did absolutely nothing. I didn't even see any lines traced when I ran my finger over the screen.
At some point, I pulled out the external SD card. I have no idea if whatever hacked the tablet also put a copy of itself on the SD card.
I called a friend who looked up how to restore the tablet to factory settings. I didn't understand the directions exactly, so I ended up on a screen with a Warning!! about installing a Custom OS. (Holding down the Power + Volume Up seems to get me there)
I left it on this screen, and I turned my router back on and using my laptop, contacted Live Chat at Samsung but they didn't understand my problem. They told me to reboot the device and swipe my pattern several times and then after several failed attempts I would have the chance to use my Google credentials to get into it. But the device apparently never registered that my swipe attempts were failing.
So my device was booted up with me locked out, with the WiFi router on for a little while again. I turned off the router as soon as I realized that. That disconnected the chat session, but since Samsung chat wasn't helping me anyway, I didn't bother trying to go back.
I got the device back to the "Warning!!" screen. Then turned the router back on and searched for how to do a factory reset of the device. I found a video on YouTube and followed it.
I pressed the Volume Down and Power buttons simultaneously, followed by letting go of the power button. That brought up a menu which contained several options, including an option to do a factory reset. I used the volume buttons to highlight that and pressed Power key. A second screen came up and I used the volume buttons and power button to select "Yes" to confirm the reset.
It appeared to have done a factory reset, rebooting eventually.
However, after that, when I tried to tap on the touch screen to move forward through the selections, the touch screen was still unresponsive!
So I brought back the "Warning!!" screen and ran the battery down until the screen was blank and it wouldn't start when I held the power key.
Then I charged it for about 20 minutes and rebooted it. I think when it came back it was on the Recovery menu. I think I did a second factory reset, but not 100% sure. It eventually rebooted after a lot longer than usual.
When it came up, it was saying battery was low. I tried to tap the OK button, but nothing happened. Behind the battery window was the first setting screen to set up the device for the first time after a factory reset. (I think selecting USA?)
I brought back the "Warning!!" screen and left it on overnight so that the battery would run down.
That was about 8 hours ago. When I woke up, I used clear tape to keep the power button pressed down, to ensure that the battery will continue to run down.
____________________________________________
What do I do next? How do I get the touch screen to start working again? It is not a hardware problem, unless mal-ware can break the hardware. The touchscreen had been working fine until this happened.
Should I take the tablet back to Best Buy where I bought it at least a year (maybe 2 years) ago? I don't know if it's still under warranty.
I have over 20 year of experience as a software developer, but not for Android. I am not very experienced with doing anything to hardware.
Should I try to fix it myself?
I have never rooted any Android device and I'm not sure what that means, either.
I've never re-installed the ______ ? (rom? image? Odin?)
I read on this and/or other forums that there's a way to replace something, but the instructions were beyond my level of understanding. I would need the procedures to be broken down into steps which don't assume too much about what I know.
I understand how to download a file to Windows, given a URL for it. I understand what a zip file is and how to extract it. I understand how to press hardware buttons and plug in cables, and do these steps in the order I'm told.
I don't understand what I'd use to get the downloaded whatever-they-are onto the tablet to replace whatever-the-other-thing-is so that the touchscreen works again.
As far as I know, Odin is a Norse god.
The only firmware updates I've ever done are the ones that the device does on it's own through Samsung's updates.
I'd deeply appreciate getting this device back since I have extremely limited funds and probably won't be able to buy a replacement.
Thank you,
Linda
Click to expand...
Click to collapse
Definitely sounds like malware. You have two choices that I see, either root and custom rom or flash back to stock. Since you are stock you'd just be overwriting your existing install. Read this thread and decide your course of action http://forum.xda-developers.com/showthread.php?t=2203309

[Q] Starting Problems

I encountered my first problems with my Nexus 5, which i am very happy with, about 1-2 weeks ago. After about 11 months of happy, problem free use, without dropping it or anything else, it started misbehaving (about a month with Android L so far). It crashed and wouldn't start up farther than the 'android' screen most of the times. Rarely it would fully boot, but the seemed to go into the lock screen and crash after a max. time of about 1 Minute of normal use. After going through this a few times I checked some forums and found a solution suggesting to repeatitly press the lock screen button while it boots. This solution worked quite good, even though i had go through the process multiple time the following days.
Last thursday evening (today is saturday) though my phone crashed fully once more (just after checking and having an 80% charged battery) , but now the quick hits on the Power button did not work at all. Instead my phone wouldn't react at all. Neither pressing the volume rockers alone or together with the power button would work either. Having plugged in the Nexus though acheived it to at least reach a state which seems to be a more common problem. It has been discussed and solved for many (seemingly everyone) in another thread called '[Q] Nexus 5 constantly rebooting at 'Google' ' (Link to this at bottom). Long explanations and videos of the situation have been given here, depicting my exact situation along with two solutions:
1. Using magnets near the power button (to apparently loosen two magnets used when pressing the power button)
2. Two flick and quickly press the button (for some this had to be done many minutes)
After seeing many (surprisingly) positive reactions to both methods, I tried them myself. I began with the magnet method and without having it connected to a charger it would boot to the google screen twice (note: As said, without a charger nothing happened). First once about as long as when connected to power and once very briefly. This method didn't prevail more than once and i couldn't start it up any diffrently than before.
So next I tried the flicking method and (maybe because of the magnets) it booted al the way to the 4 colored dots flying around. I let go and it crashed once more. I fooled around with the magnets again and tried the flicking method again, without stopping, as other users mentioned a long time needed (15-30 Min.) and after about 20 Minutes I stopped. My Nexus did not crash, but it is now 'stuck' at the colored Dots. I have tried connecting it to a power outlet, my PC and again started pressing the power button and volume rockers, without effect. It has been so for about an hour if not more. I will try to drain the battery and then continue, but if any other solutions are known Please help, thank you!
Link to other Question: http://forum.xda-developers.com/google-nexus-5/help/nexus-5-constantly-rebooting-google-t2809617

Update
After having drained the battery completely and then charging it again, the normal 'charging battery' icon popped up. Trying to start the phone, however resulted in getting into the flying dots loop again... I am able to go into fastboot mode, but neither start or Power Off help the situation. Should I go into recovery mode? I would strongly dislike losing all my data....
(Update)
I tried going into recovery mode, but the only thing that happened was that a little android figure, lying down with a red exclamation mark showed up (which should be normal as I recall going into recovery mode before my problems), and a text saying 'no command' above it. What now? I'm all out of ideas and back up plans, except calling google as it should still be under my warranty. But I don't want to give up my data as I haven't saved anything and I don't want to give up my phone either.

Can't boot, restarts constantly

Bought a Nexus 5 about 6 months ago USED. It has been amazing. I got the latest OTA a week ago or so, not sure if that has anything to do with current issues.
About 2 days ago started randomly restarting. Today, it shut down and has been in continuous loop restarting. I see "Google" and maybe even the boot dots loading, then it is off. Three seconds later, starts again and repeats. Never makes it all the way into Android system. I let it sit for a while and when I pick it up, without touching any buttons, it repeats all of this. I suppose it is probably dead in general, but I don't know. Do you guys have any ideas? Again, I bought it used and from a ma/pap store who said they buy 100 in bulk, which made me skeptical, but they also had a 60 day guarantee and it was amazing the first 60 days and even after. It has been error free for 6 months, so I don't know if this is just a random issue or if the previous owner dropped it in a lake and I got lucky, or what. FWIW the damn thing has been in a case and never dropped, so it isn't anything that I have done I don't think. Thanks for any help.
edit: never rooted, never messed with, always been stock

Another user reported some instability since the last OTA update.
Flashing the full factory images did the trick.

a friend of mine gave me his nexus 5 to repair and its doing something similar. He had ir rooted and on latest 5.1.1 (i think). Either way, he said it was randomly locking up and rebooting. When i got it it had the red blinking light when plugged so i got a new battery. That got fixed but then the constant bootloop showed itself. I flashed TWRP (many versions, 2.6.3.1; 2.7.1.1; 2.8.7.1; the one that worked best was 2.7.1.1). So, once in twrp wiped, pushed cm 12 snapshot, flashed it, pushed gapps, falshed, pushe supersu flashed. Started the system. That precise order of things (ie: pushing flashing, then pushing something new and flashing it) was what gave me best results to actually boot up at least once. Once booted up and logging in and everything to cm i had some sort of stability (even rebooting and powering off) but i think that everything went wrong when i plugged the phone to the computer and it was back to bootloops and not even getting to the recovery. Flashed everything again. Didnt work. Had to leave the phone sit for a while (without the back casing) before trying again, in order, before getting any success. Im starting to think of ovrheating but it doesnt even get that hot...
Dunno if you guys have any ideas on this. Or if i can give you mor details to help us out.
Regards!

Looks like I'm having a similar problem to what is described here, as well as http://forum.xda-developers.com/google-nexus-5/help/bootlooped-dont-how-to-enable-debugging-t3215951
I've had one of my Nexus 5 phones running OmniROM 5.1.1 for some time now, very stably. After trying out the Marshmallow preview and going back to that ROM, I started having spontaneous hard reboots and hard crashes. The phone would often boot loop before even getting to the OmniROM boot animation. It was also very recalcitrant about entering and staying in the boot loader, rebooting spontaneously shortly after rendering the boot loader screen. I was occasionally able to "grab" control long enough to get it to boot into TWRP, from which a boot to Android seemed to usually get it out of the loop and into running Android.
I've flashed back the boot loader and baseband from factory-stock 5.1.1 LMY48M (HHZ12h and 2.0.50.2.26) using the flash-base.sh script from a freshly downloaded and extracted hammerhead-lmy48m. Things appeared to be OK last evening and this morning, but things got worse today.
Now the phone is in a state where it is not responsive to the power button when unplugged. I can hold it down for 30 seconds with no response.
If I plug in USB, it spontaneously starts rebooting, not showing more than about two seconds of the Google boot loader screen. If I hold the down-volume button, I can get the boot-loader screen, but no matter how fast I try to be, I can't select anything more than "Restart bootloader" (or "Power off") option before it spontaneously reboots (to boot loader).
As far as I know, the battery had a significant charge before this started happening.
I see the same behavior if the phone is connected to a USB charging source, rather than a USB port.
I've tried pulling the SIM, but that doesn't change the behavior.
adb wait-for-device never returns, so poking it over adb doesn't seem to be an option.
fastboot devices also doesn't see the phone, for the brief time the boot loader is running.
Any suggestions on how to get this into the boot loader so I can at least re-flash it?
Nexus 5 D820(E) 32 GB
Edit:
WaxLarry said:
In my opinion your problems seems power button's related.
Click to expand...
Click to collapse
Trying to see how I can "clean" or "clear" the power button now.
Edit:
Paul22000 said:
This morning my Nexus 5 was turned off all of a sudden after not having used it for 20-30 minutes. I held the power button and nothing. I plugged it into power and the "Google" screen appeared. It then went into a reboot loop on and off, on and off, on and off. I held the Volume Buttons and it went into fastboot, but then boot looped out again and again. Searching on Google yielded that this was indeed a common problem. [...]
Click to expand...
Click to collapse
Edit: Repeatedly pressing the power button seems to have temporarily allowed a boot to Android.
In retrospect, I had noticed over the last few days that the phone didn't seem to respond properly to the power button, either "ignoring" it, or when a second press got things started, it would unexpectedly come up with the long-press-volume menu.
One link on how to replace the power switch yourself is http://protyposis.net/blog/replacing-the-nexus-5-power-button/

Ok @jeffsf keep going on this thread. I had the same damn experience, that ended with RMA. LG said that the problem is related to some tension change in the power button. After the RMA I used the phone totally stock and never had a problem. Two months ago I switched to blu_spark kernel and some weeks after i noticed some problem. When I pressed the button to lock the screen, phone locked itself and then screen turned on, sometimes showing the shutdown option. So i understood that something was happening to the power button. I tried to overvolt with a +5mV on general offset and since then i never had problem. If you can enter recovery or bootloader i suggest you to flash some kernel with volt change support and then overvolt the general offset... and keep finger crossed

jeffsf said:
Looks like I'm having a similar problem to what is described here, as well as http://forum.xda-developers.com/google-nexus-5/help/bootlooped-dont-how-to-enable-debugging-t3215951
I've had one of my Nexus 5 phones running OmniROM 5.1.1 for some time now, very stably. After trying out the Marshmallow preview and going back to that ROM, I started having spontaneous hard reboots and hard crashes. The phone would often boot loop before even getting to the OmniROM boot animation. It was also very recalcitrant about entering and staying in the boot loader, rebooting spontaneously shortly after rendering the boot loader screen. I was occasionally able to "grab" control long enough to get it to boot into TWRP, from which a boot to Android seemed to usually get it out of the loop and into running Android.
I've flashed back the boot loader and baseband from factory-stock 5.1.1 LMY48M (HHZ12h and 2.0.50.2.26) using the flash-base.sh script from a freshly downloaded and extracted hammerhead-lmy48m. Things appeared to be OK last evening and this morning, but things got worse today.
Now the phone is in a state where it is not responsive to the power button when unplugged. I can hold it down for 30 seconds with no response.
If I plug in USB, it spontaneously starts rebooting, not showing more than about two seconds of the Google boot loader screen. If I hold the down-volume button, I can get the boot-loader screen, but no matter how fast I try to be, I can't select anything more than "Restart bootloader" (or "Power off") option before it spontaneously reboots (to boot loader).
As far as I know, the battery had a significant charge before this started happening.
I see the same behavior if the phone is connected to a USB charging source, rather than a USB port.
I've tried pulling the SIM, but that doesn't change the behavior.
adb wait-for-device never returns, so poking it over adb doesn't seem to be an option.
fastboot devices also doesn't see the phone, for the brief time the boot loader is running.
Any suggestions on how to get this into the boot loader so I can at least re-flash it?
Nexus 5 D820(E) 32 GB
Edit:
Trying to see how I can "clean" or "clear" the power button now.
Edit:
Edit: Repeatedly pressing the power button seems to have temporarily allowed a boot to Android.
In retrospect, I had noticed over the last few days that the phone didn't seem to respond properly to the power button, either "ignoring" it, or when a second press got things started, it would unexpectedly come up with the long-press-volume menu.
One link on how to replace the power switch yourself is http://protyposis.net/blog/replacing-the-nexus-5-power-button/
Click to expand...
Click to collapse
I got a notification for this post since you quoted me. I'm not sure if you're having the same problem but I'll tell you what happened to me, just in case. I called T-Mobile and they referred me to the nearest 3rd party phone repair shop. I went there and after an evaluation, the repairman told me the power button on my phone was indeed broken. They replaced it for $55.
The story doesn't end there though. I took my phone home and a few hours later I tried to use bluetooth and it didn't work. I took it back and found out that unfortunately, when the guy replaced the power button, he inadvertently broke the bluetooth. There's no way to fix bluetooth without replacing the motherboard entirely, which would cost $200. I'd rather buy a new phone at that point since my Nexus 5 was getting old. He refunded me, which was nice. At least the power button worked so I could use my phone. Bluetooth isn't as valuable as being able to you know, turn on the phone, so at least it was a net gain.
After that, I purchased a Nexus 6 and rooted it so I could use double-tap-to-wake (along with the automatic screen on when you pick up the Nexus 6). I also use the following app in order to turn off the screen by swiping up from the home button (I don't care about losing the shortcut to Google Now): Screen Off and Lock
I can now literally go weeks without using the power button on my Nexus 6. (I literally only use it when tap to wake sometimes becomes unresponsive which is rare.)
Bottom line: I will never buy another phone without tap to wake functionality! :good:

A local repair shop here indicated that one sometimes does changing the power switch resolve the issue. They have seen situations where the issue appears to be one of the power-management ICs. Just something to be aware of when examining the potential cost of a repair and who you would have do the work.

How to restore into operation LG G2 D800 phone that says "Fastboot mode started"?

How to restore into operation LG G2 D800 phone that says "Fastboot mode started"?
Current problem: phone is not operational (does not boot properly).
What I see:
Boot Screen 1:
Phone appears to boot as normal, makes the start-up sound, then it shows a white message box on a gray-screen background. The message box says "Unfortunately, Settings has stopped."
It gives me an option to click "OK".
Clicking OK, message box disappears, screen momentarily flashes an all-white background, (which sometimes changes into black and sometimes not), and then it goes back to the message box.
Boot Screen 2:
"[xxxx] Fastboot mode started" on a blank screen,
where xxxx is a number. 6180 one time, 9790 another during 2 individual boots.
Then the phone just sits there doing nothing seemingly indefinitely.
I am not sure yet how I bring those two different boot modes up but via pressing Power and / or Power and Down buttons in some fashion.
How do I fix this? Is my device bricked?
How I got to that screen
I was using a web browser or some other app on the phone when I have received a text message. I clicked on it inside text box to reply. But changed my mind, and clicked back on the background app. Suddenly the phone shut off unexpectedly. I thought it was related to phone drawing suddenly high battery power, not receiving it and shutting off as sometimes happens on very low battery power level 2-4%. However, my battery was charged over 40% so that was most likely not the cause.
Possibly relevant history (anything that could be contributed to the above):
phone worked okay for a while (since purchase)
~1 year in I tried rooting phone with towelroot/other options unsuccessfully. Gave up. Was never able to root the device. Lived with is as is for a while.
~2 years since purchase, somehow Bluetooth option started failing to turn on. Trying to fix that via doing a Factory Reset did not help. So I lived with BT being non-operational
A week ago I swapped SIM card with my buddy for a week, then swapped it back. Phone kept working as normal.
Today I charged the phone perhaps not using the best power source - it is possible I may have damaged phone using a questionable quality charger. Possibly. This could be the issue. However the phone seemingly worked fine after that for 2-3 hours.
Since my unexpected Shut-Off (most recent), I tried rebooting the phone, but that does not work as expected. First time it got stuck on LG screen forever. Kept pressing Power button, or Power & Down buttons to try to make it come alive. Other two times it brings up a message with "[xxxx] Fastboot mode started" on a blank screen and then it just sits there doing nothing.
Another boot, the process went further, past LG G2 logo, into white screen, and then it brought up a message "Unfortunately, Settings has stopped.", I clicked okay. It looped back to bringing up the message. I clicked Okay over 10 times, it was stuck in a loop.