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.
Related
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.
Ok. So 14 days ago my wife and I both got S6's for Verizon from a local big box store. (yes, 14. Today is the last day I have to take it back.)
We took the OTA to OE2 and I was able to root both phones with PingPong. Everything was fine until yesterday. Her phone wasn't responding when a call was coming in, so she restarted it by holding in the power button. Now, when it boots up it goes to a black screen after showing the initial "Samsung Galaxy S6" screen. Nothing changes. There is a teal/blue pulsing LED that doesn't go away.
I can enter the recovery and wipe cache, factory reset, safemode, etc. I've tried all of those many times. I can enter download mode and use Odin 3.10.6 to reflash OE2 and it says "Pass". After rebooting, it goes to the "Android is upgrading" dialog and goes through and updates about 248 apps, and then changes to read "Starting apps." It won't go past that screen. I left it on that from 10pm last night until 6am this morning with no change. The battery eventually went dead (from 100%). I've tried Odin many times, and it passes every time.
What are my options? When booting, the padlock is unlocked and says "Custom". I'd really like to get rid of that so I can return it to today without problems. When in Download mode, the system status says "custom".
Please help!!
I've also tried using SmartSwitch on the PC, and it doesn't detect the phone.
Update: I'm trying an Emergency Recovery with Smart Switch. It's at 52% right now. I got a serial number from another S6 so it would allow the download/recovery process to start. It's kind of ridiculous you can't get the serial number for your device from anywhere but the settings page on the phone. (Note: not the IMEI, the actual SN). It's not on the box or back of the phone.
Ok, another update. Emergency Recovery didn't work. It finished, and said that it was successful, but didn't fix the issue.
I took the phone back to the place of purchase and they tried about everything that I had already tried. They ended up just replacing the phone. They said that they never saw this issue before.
I have almost an identical issue except I have not roOted or installed any custom ROMs everything is stock . The fingerprint scanner quit working today and said it required a restart, when I restarted the phone I'm experiencing exactly what you are a black screen and a blue pulsing light. In the stock recovery screen I've tried booting to safe mode USB debugging everything except the factory restore yet I think that is my last resort.
Hi, i have a rooted Samsung galaxy prevail 2, and just recently my phone has appeared to stop working. when i reboot it, the message 'shell has been given superuser permissions' is displayed and the screen is frozen. in this state none of the hardware buttons work except the power button except it only works to reboot, not turn the screen off. the low memory icon is also displayed in the top left. i should mention that this has happened before a while ago but my phone returned to normal after three days and i did nothing to fix it. this time its on day seven of freezing on every reboot. i have tried to factory reset using the hardware buttons but once it gets to the second logo and displays the message at the top left, it doesnt continue to the recovery menu and instead shuts back off. i have also tried to connect it to my computer to look through the files but it will not accept the driver the computers trying to install. i even downloaded the correct driver from the samsung website. any help? thanks.
Is this N5 hosed?
Android 5.1.1
( I know the following because I have a second N5 that was purchased at the same time that Is still running flawlessly and they both would update within a day or so of each other, assuming this info is the same)
Baseband Version
M8974A-2.0.50.2.26
Kernel Version
3.4.0-gbebb36b
[email protected]#1
Tue Mar 10 18:17:45 UTC 2015
Build Number
LMY48B
I have a completely stock N5 that started presenting problems some months ago with random reboots, just occasionally. It would just restart no big deal, didn’t worry to much about it pretty soon the restarts came more often.
I installed the “Device Assist” App as suggested in a google forum group, to which it immediately started to recognize “Device Randomly rebooting? Try Safe Mode” ( which I didn’t at that time) it did give me the option to call a google tech and speak with them about the issue, they saw, through device assist that indeed the device had been randomly restarting. The tech ran me through clearing the device cache from the recover menu, I rebooted and everything worked fine for several weeks.
Then the reboots started again, but this time more seriously, often the unit would just power down and attempt to reboot would be meet with a short vibrate with a flash of the word google.
Eventually it would boot back up, often it would run through an “optimizing apps” routine.
I remembered as well, often the reboot(s) would begin with the “power off” screen coming up, even if I didn’t choose it it would shut down anyway and often if I dismissed it, it would wait 10 seconds or so then shut down.
All really strange.
So I got a hold of a google tech again, this time they suggested rebooting in safe mode and running several days like that to see if it was a software or hardware issue.
In safe mode it ran without issue for 48 hours( normally this would have resulted in a handful of restarts at best. Google tech seemed to think it was an app issue since the problem didn’t return in safe mode and suggested a complete factory restore,( and to setup the phone as a new phone rather than restore any back info form google) I was backed up so I ran the factory restore from system settings “back up and restore” .
Once restored it worked fine for a day and then it all went downhill from there, power off screen would appear (often when I short pressed the power button to sleep the unit) and again if I dismissed that dialogue it would power down anyway and it would take numerous tries to get it to power back up, almost every time it would run through the “optimizing apps” routine.
Within a day, it just stopped powering up. If I plug the unit in to charge it does this odd cycle of black-screen/short vibrate/Flash the word Google, about every 2 seconds, it never shows a battery charge indicator
If it is not plugged it won’t do anything, if it is plugged in when I tried to boot into recovery, the recovery screen would appear for a brief second and then it will start the vibrate/flash “google “ cycle.
It does nothing when placed on a wireless charging plate.
Google tech said it is out of warranty ( which I knew) and gave me a number to LG to see what options they suggested.
I suspect it has something to do with a sticky or malfunctioning power button, but wanted to see if anyone here has and experience with this type of issue or has a suggestion.
Thanks
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.