Database Info

[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.

Ultra Power Saving Mode - unusable phone

Hey guys-
Was on a long international flight yesterday and decided to put my (unrooted) Galaxy S6 into "ultra power saving" mode for the first time. It was a horrible mistake and I'm not sure how to undo it!
The first issue it had was that it said Ultra Power Saving mode doesn't support the use of themes, so it was reverting to the default theme (I use Material Black).
After a long time of saying it was reverting to the default theme, I'm not sure if it worked - it ended up in the state that it is currently in: if I turn the phone on, the screen is just black - it has the status bar at the top of the screen, but just a blank black screen below it. It does not look like images I've seen on other websites for what Ultra Power Saving mode is supposed to look like (no icons on the screen, no "More" at the top right). If I go to settings by dragging from the top of the screen and hitting the settings button, I get a very limited set of settings: WiFi, Bluetooth, Airplane Mode, Mobile Networks, Location, Sound, and Brightness - nothing that enables me to turn off Ultra Power Saving mode.
I am afraid to reboot the device, because when I did that yesterday, I had major issues. My device is encrypted, and I think this mode doesn't play nicely with encryption; when I rebooted the device, I was asked to sign in to unlock the encryption (as normal), but then the encryption booting screen (an unlock symbol with a circle around it) just idled indefinitely - for an hour or two. I couldn't do anything to get the phone to actually boot. Eventually, many hours later, rebooting the phone and logging in allowed it to boot to the state I described above; I don't know what went differently that time.
I tried various key combinations on restart, one of which seemed to result in the device trying to boot to Safe Mode (it said safe mode in the bottom left corner when asking me to sign in to device encryption), but ended up leaving me in the exact same place - the extremely limited Ultra Power Saving mode black screen I described above.
Anyway - is there anything I can try to get my phone out of Ultra Power Saving mode and back to normal? It is unusable right now and I can't figure out how to get it back. Would like to avoid a factory reset if possible (because I'm overseas with ****ty internet, and don't have access to my office to get it re-set up with enterprise mail etc.).
If I have to factory reset the device - I'm not even sure how to do it from this current UPSM state, so any tips there would be helpful too.
Thanks a ton in advance for the help guys

Go to download mode, reflash original rom with odin. You need your rom file from sammobile or samsung-updates or xda and odin 3.

Sorry, I am no power user although I am not totally tech incompetent. Can you tell me in a little more detail what your instructions mean? It sounds like it is basically a total reset of the OS; is that right? Any implications for my warranty? Any alternatives?

If you had package disabler and disabled any of the packages required to run ultra power saving mode, you get symptoms like this.
com.sec.android.emergencylauncher is one package amongst many.
I have honestly only heard of factory resetting working.
http://www.hardreset.info/devices/samsung/samsung-g920f-galaxy-s6/

[Completed] Samsung S5 Stuck in an installation loop.

I just downloaded the update for Cyanogen Mod 13 and I clicked install then my phone powers on (no matter what buttons I press; power, power and volume up and home) it has the Samsung S5 logo and the text "Recovery booting..." (as well as the other warranty text stuff). It then quickly flashes the screen with the Android and cog logo with the text "Installing system update" for the shortest time (making it almost impossible to read the text) it then flashes this screen on and off every 5-10s for the rest of the time. I thought that the screen maybe just a little glitchy but the "update has been running for almost an hour now. How can I fix this problem if my phone doesn't allow me to put it into recovery mode .

So I spent about 3 hours trying to fix this problem trying every combination of buttons to press on boot as well as trying to make my phone detectable or something like that. Let my Mum try fiddling with it (she has no idea what she doing with new tech) some how she managed to press the buttons just right. It went into download mode and I was able to flash it with an update of TWRP using ODIN and it rebooted and started up. If you haven't already try putting it into download mode, I've heard getting the timing right can be tricky when your phone is doing unusual things. Now I'm unsure whether to try updating again but I might try wiping and going back to a stable 12.1.
Mod Edit:
Thread closed as ODIN fixed it

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.

[Solved] S6 G920V reboot loop, cannot boot into maintenance, only ODIN mode

Hi!
Very weird situation. Before that everything was stock and OK (no custom ROM or anything).
- If the phone is unplugged, nothing works at all (key combinations,...)
- The battery is charged, at some point, when totally off, it showed the battery charging, 60% at least. But have not been able to go back into this mode.
- When connected, it starts booting, but keeps rebooting very fast (1-2 s after Samsung splash screen).
- Unable to boot into Recovery mode (UP+HOME+PWR, for wiping cache,...). Just does nothing, howerver long I wait
- Unable to boot "directly" into Maintenance Mode (all buttons), more on that later
- Can boot into Download (ODIN) mode (DOWN+HOME+PWR) very easily. I was able to flash stock ROM, but nothing changed.
- From ODIN mode I can boot into Maintenance mode (all buttons). I can navigate the menu, but any choice, even Factory Reset, gets me directly back to the reboot loop...
As I can not even turn it off, I cannot drain the battery (at least not quick). As soon as I disconnect the cable it goes dark (whatever mode I am in).
Anything I missed that I could try before throwing the phone?
Thanks!

SOLVED
Just to leave a trace on what happened:
- Left the phone alone, un plugged, for 8-10 hours.
- Just to see, tried to reboot it normally,
- It booted on a blue/cyan display, with "installing updates".
- At one point before I had that screen, but after 10 seconds it rebooted into the loop cycle. And after playing with the recovery reboots, I had never managed to get this special boot again.
- This time it stayed on "installing updates" for 1-2 mn, then rebooted, and Voilà!!!
So apart from my magic touch of doing nothing, don't really know what happened... So much for the recovery recipe!

A fairly similar thing happened to my girlfriend's g920v yesterday. We haven't been that lucky that it got fixed.
The situation is slightly different though, it boots for about 3 seconds, makes the low battery sound, battery indicator says 0%, then shuts back down.
Tried flashing stock in odin a few times, a few factory resets, nothing.
It seems like an OTA update failed and now the stupid locked bootloader won't let me or the or OS fix it.

Sorry you were not as lucky... But as you said the problem seems a little bit different, as I never had an empty battery warning. I agree though that it looks as a bad update stuck somewhere.

guimou_qc said:
Sorry you were not as lucky... But as you said the problem seems a little bit different, as I never had an empty battery warning. I agree though that it looks as a bad update stuck somewhere.
Click to expand...
Click to collapse
There's got to be some connection of some sort, yours is the 4th post I've seen here or on Reddit this month about bootloops probably related to updates