Database Users

Safe mode

So I was playing with my nexus s and the screen shut off with out the old TV animation and woke it back up and I see SAFE MODE in the bottom left.
I rebooted and was back to normal..... has anybody else had this problem and how did it happen? What caused it?
Sent from my Nexus S using XDA App

I had the same thing happen to me last night as well. I'm not sure what caused it? Like you I rebooted my phone, and I was all good again.

Happened to me yesterday when booting the phone. Rebooted and everything went back to normal.

that happened to me when i had my HTC Hero CDMA
i never figured out what it was.

I had this same thing on my myTouch 3G. If you held down a button while starting up it put the
Phone in Safe Mode. It basically made all non-default applications not work. Did you guys try starting it up while holding a button?
Sent from my T-Mobile myTouch 3G Slide using XDA App

I had the same thing. I remember I was trying to boot into bootloader with the down volume key. That didn't work but I think that may have been the cause. Of course I now know it's the up button that does it all.
Sent from my Nexus S using XDA App

Hi guys from what i have read the safe mode is in case you get app. that starts to act up my making your phone go nuts you can go in to safe mode by turn off your phone and while turning it on hold the menu button you go in to safe mode that way no third party app. are loaded so you can delete the app. that gave you the trouble that's what i have seen on the nexus s!!!!!!

good deal. I remember that I was wiping the screen off on my shirt while booting. Must have been what caused it. Useful info for the future for sure.

It happens when you turn on teh phone and half way through the boot process you hold the volume buttons

[Q] My Nexus 7 just exploded. What do I do?

Hey XDA,
I received my 16GB Nexus 7 from Google 4 days ago. I immediately updated to 4.2.1, rooted, and then flashed franco.Kernel. I was running the latest update to franco's kernel, and had left the settings untouched from the defaults with interactive governor. Yesterday I flashed the latest nightly for Cyanogenmod.
I was using the Facebook app when my tablet ran out of battery (I intentionally let it die), and after it powered itself off, I plugged it in with the charger provided to me by Asus/Google. Because I am new to this tablet, I wasn't aware that plugging the charger in meant that the device would power on. Anyways, it did power on, and I had no plans to turn it off now that it had turned itself off. I went to turn the wi-fi off so that it would charge with less power drain, but just before I turned the wi-fi off, the device began to power down again (The charger is still plugged in, and it didn't become unhooked at any time). I begin to walk away to do other things while it turns off again, but I stop when I hear a weird grinding noise. It's hard to explain, other than it sounded like a kettle getting progressively louder and then shutting itself off when it reaches its desired temperature, only it sounded like gears and not a kettle.
A little worried, I wait a bit and then I turn it on. I'm relieved when I see the Google logo appear, and then the Cyanogenmod logo appear. After a long boot, I'm greeted by a black screen with what tiny white flashing dots randomly appearing. I turn the device off, and restart it. Same thing, only now it seems like there may be more flashing white dots than the last boot. I unplugged the device from the wall, and force shut it off (power + volume keys).
I've never heard of this happening before, which is why I'm hoping someone can give me some advice. Obvious things for me to do would be to flash stock 4.2.1 onto my Nexus 7. The reason I haven't done this is that I'm worried that my device may now be dangerous (battery melt, processor malfunction). Does XDA have any recommendations before I phone Google? I'd like to avoid Google because I've voided my warranty with them by rooting and flashing a custom kernel, so any other help is MUCH appreciated.
Thank you so much for reading my essay, and for taking the time to help,
Robert

Do your very best to revert it back to stock os and kernel and re lock the bootloader. Yes it is possible. Look for the nexus 7 toolkit. Then send it to google/asus. Best I can think of dude.
Sent from my MB612 using xda app-developers app

I have heard people with similar issues start device in bootloader and leave it there to charge to prevent the on/off loop and after a few hours when charged boot normally.
Hope this helps
Sent from my SGH-I927 using xda app-developers app

The screen with white dots has turned into what appears to be a screen with no signal like you see on tv's.
This is even happening while I'm in recovery mode, it'll just randomly happen.
What's going on?

Can you get it into fastboot? Does it still respond to adb?
Sent from my MB612 using xda app-developers app
---------- Post added at 05:05 AM ---------- Previous post was at 05:02 AM ----------
Here you go dude. It'll help. http://forum.xda-developers.com/showthread.php?t=1809195

BlackFire27 said:
Can you get it into fastboot? Does it still respond to adb?
Sent from my MB612 using xda app-developers app
---------- Post added at 05:05 AM ---------- Previous post was at 05:02 AM ----------
Here you go dude. It'll help. http://forum.xda-developers.com/showthread.php?t=1809195
Click to expand...
Click to collapse
Thanks, that's actually what I'm using =) The issue I'm having is getting it into recovery mode. I am always able to do it prior to this incident, at least after two tries anyways. Now every time the Google logo displays and I hit the down volume, it just begins to boot into Android ignoring the fact I hit the volume down.
Robert

Trewyy said:
Thanks, that's actually what I'm using =) The issue I'm having is getting it into recovery mode. I am always able to do it prior to this incident, at least after two tries anyways. Now every time the Google logo displays and I hit the down volume, it just begins to boot into Android ignoring the fact I hit the volume down.
Robert
Click to expand...
Click to collapse
Make sure the device is off. Hold the volume up, down, and power for 2 or 3 seconds. Then let go of the power button while holding the volumes. That'll bring you to the bootloader. From there you can also get into recovery mode. By selecting with the power and volume keys.

BlackFire27 said:
Make sure the device is off. Hold the volume up, down, and power for 2 or 3 seconds. Then let go of the power button while holding the volumes. That'll bring you to the bootloader. From there you can also get into recovery mode. By selecting with the power and volume keys.
Click to expand...
Click to collapse
I'm going to leave it charging for a while and see if that will give me enough time to do what I need. I'll report back here either within an hour, or sometime tomorrow around this time.
Thanks for the help so far!
Robert

Trewyy said:
I'm going to leave it charging for a while and see if that will give me enough time to do what I need. I'll report back here either within an hour, or sometime tomorrow around this time.
Thanks for the help so far!
Robert
Click to expand...
Click to collapse
Anytime man! PM me if you have anything else man.

It's 4 days old. Send it back as defective.

turn it off, let it charge for long time, after tha download toolkit and revert it back to stock.
You should be good to go.

I'd bring it back, as it is possible to cause an injury to you. Better to be safe than sorry.
Its new so just bring it back (or send) and get a new one.
Sent from my Nexus 7 using xda premium

Try to relock it and flash the stock rom.
After that, phone up Google and explain what happened AND ask for a compensation. This could have harmed you, and Google/ASUS IS responsible for it. Unless, of course you have messed something up while rooting or flashing the custom rom.
Anyway, you should be able to get a compensation, maybe a 32GB version.
This is not something that should happen to a 4 days old device.

did you void the warranty by flashing? i don't actually know.
granted, this sounds like a hardware malfunction (again, i don't know, could be a kernel), but, modder beware. this is a risk we take.

I'd put it back in the box and return it if possible. Save some time. If they are jerks about it then proceed:
If you can flash anything to it through recovery, download the updated Galaxy Nexus (Samsung) JB Bootloader and flash it.
I have a Galaxy Nexus and a Nexus 7. I killed my first N7 by getting confused and flashing it to my N7. It won't even power on afterwards. That should screw up your partitions enough where it won't be recoverable without a full format/reflash.

I had this issue when my battery died. I took off the back cover and unplugged the battery and plugged it back in. Put it back together and charged it up for a few hours. All has been well since, I'm pretty sure its a common issue with N7's when the battery gets low.

Had a similar issue once after letting it discharge to 0 and plugging it in and trying to boot right away. Mind you I didn't have the noise, just the snow effect. My solution was to turn it off and let it charge for a few minutes while off. After that it worked fine.
Sent from my Galaxy Nexus using xda app-developers app

Do your best to revert it back to factory and call them up about that possible firecracker before something else can happen
keep us informed about what happens too if thats ok

Stock - and the same problem...
Hi, my N7 is two months old and worked perfectly. It's clear stock - never rooted, modded etc. Today I suddenly can't run it - it boots, battery level is 24% (on bootscreen), and after few seconds shows 1% and starts to snow - sometimes with sound. I haven't installed anything new for few weeks, so I'm sure it's not a virus, trojan etc. WTF?
PS. Sorry for my English...

djexacto said:
Had a similar issue once after letting it discharge to 0 and plugging it in and trying to boot right away. Mind you I didn't have the noise, just the snow effect. My solution was to turn it off and let it charge for a few minutes while off. After that it worked fine.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I confirm that. I had this issue already a lot of times. When the battery is completley discharged it seems that the display or the graphics hardware is not able to start as expected. I just left it powered of (or in that charging screen) for some time (>1h) without using it. Then it started normal.
But also for me, no noise, just the screen like on an old TV without signal.

[Q] Does anyone have a power button bug?

I am current using PA mar11 build with franco r102 kernel.
I have issues bringing the menu up when you hold the power button. My power button is not broken, because after a restart (using power toggles) it works again.
Happens randomly. I have searched the forums and have not seen anyone mention this, has anyone else experience this?
Update: Do a fresh wipe, problem will go away

What issues do you have exactly? I mean, what exactly do you see when you long-press your power button?
Sent from my Nexus 4 using xda premium

jamesc760 said:
What issues do you have exactly? I mean, what exactly do you see when you long-press your power button?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
after a long-press no menu comes out and my screen turns off like I pressed it normally.

I have the exact same problem, except that my nexus 4 isn't rooted and I can't use toggle buttons to restart. So basically I cannot restart my phone unless i let the battery running out or i reset the phone.

Weird... I just got this too... restart and it's working again... but for how long.... and I never would have noticed if I wasn't trying to take a screenshot!
Sent from my Nexus 4 using Tapatalk 2

I have exactly the same problem running slimrom 6.5 and anarkia kernel.
After a reboot the reboot menu always comes up. After a while it doesn't work anymore. Turning on/off the screen always works, the problem only affects long press.
Has anyone a sultuion for that?

br0ok1ynb0i said:
I am current using PA mar11 build with franco r102 kernel.
I have issues bringing the menu up when you hold the power button. My power button is not broken, because after a restart (using power toggles) it works again.
Happens randomly. I have searched the forums and have not seen anyone mention this, has anyone else experience this?
Thanks
Click to expand...
Click to collapse
Did anyone find a solution to this problem?
My Nexus 4 is now having this same issue

I thought I was the only one! It happened after a bit of rain with my phone in the pocket and I thought that was the cause but after holding it down and seeing it reset I see that it is not. Wonder why this is happening.
Note: I am running completely stock 4.3 at the moment with a locked bootloader, but this has also happened on 4.2.

I got this issue with franco kernel. putting back the original kernel fixed the issue for me. I was able to reproduce the problem with another nexus 4 phone. there's maybe a config to tweak or i'm messing something up.

nikwist said:
I have the exact same problem, except that my nexus 4 isn't rooted and I can't use toggle buttons to restart. So basically I cannot restart my phone unless i let the battery running out or i reset the phone.
Click to expand...
Click to collapse
Exactly same problem.. But a long press of the button for about ten to fifteen shuts down the phone in my case.. Stock 4.3 no root

I no longer have this issue. The fix: fresh wipe

Had my first phone lockup :(

Was using this app, then long press on home button to search from Google now. Phone froze, screen went black and just left the keyboard open. Couldn't do anything apart from a battery pull. Hope this isn't a sign of things to come!
Sent from my SM-G900F using Tapatalk

Never happened to me on the S5 yet but it happened for me some times on the nexus 7 2014 while using chrome (only on kitkat). Guess its a general problem that can happen in android since KitKat. Hope google can fix it asap.

Hasn't happened to me, would be sad if it did since it's new, and hope it never will (yeah right...)

Hold both Vol+/Vol- , Home & power button to perform a hard reboot

dynospectrum said:
Hold both Vol+/Vol- , Home & power button to perform a hard reboot
Click to expand...
Click to collapse
Was wandering if there were any special keypresses I could use to reboot
Sent from my SM-G900F using Tapatalk

dynospectrum said:
Hold both Vol+/Vol- , Home & power button to perform a hard reboot
Click to expand...
Click to collapse
Good to know!

There is no need for breaking your fingers by pressing all buttons,just hold the power button as long until it restarts
Sent from my Nexus 7 using XDA Premium 4 mobile app

simacca said:
Was using this app, then long press on home button to search from Google now. Phone froze, screen went black and just left the keyboard open. Couldn't do anything apart from a battery pull. Hope this isn't a sign of things to come!
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
That sucks. Let us know if it happens again and how.

happens to me all the time, very annoying. The screen just goes black but the background apps continue to work (at least half the time anyway).

mastermarc said:
happens to me all the time, very annoying. The screen just goes black but the background apps continue to work (at least half the time anyway).
Click to expand...
Click to collapse
ALL the time? I wouldn't have had the patience to keep with it and probably have sent it back or something...

Experiencing Major Reboot Issues

Let me preface this by saying this is my experience. I am passing this off to see if others are experiencing the same thing. I am not dissing this phone because I really like it.
I have seen more than 10 random reboots with this phone. The crazy part is when the phone reboots, I lose settings.... Like a lot of them. I recently experienced and my notification bar started malfunctioning where the settings would not pull up and I could not long press panels. I finally had to factory reset my phone.... After that, it rebooted again this morning while I was listening to the radio.
At this point I am going to have start a log to try to correlate where the problem might be.
This is very concerning. I have never experienced anything like this even with custom Roms.
Please let me know if anyone else is experiencing this.
Sent from my SM-G935T using Tapatalk

I've read that other people are experiencing this too. Hopefully mine doesn't come like this. I would recommend returning it and getting a new one. This is ridiculous that this is happening

Try removing all apps you installed and see if you cant pin it down to an app but if all said and done and phone is stock meaning you installed no additional apps and still see it happen then to me sounds like a Hardware problem and you should return it for a replacement.

anrchy666 said:
Try removing all apps you installed and see if you cant pin it down to an app but if all said and done and phone is stock meaning you installed no additional apps and still see it happen then to me sounds like a Hardware problem and you should return it for a replacement.
Click to expand...
Click to collapse
Unfortunately, I think you are right.
Sent from my SM-G935T using Tapatalk

I'm having the exact same issues. Once or twice a day, usually in USA Today or IHeartRadio, it reboots. Once I experienced that loss of settings also and had to factory reset. I'm going to return the phone.

Try wiping the cache partition
Sent from my SM-N920T using Tapatalk

rocolema said:
I'm having the exact same issues. Once or twice a day, usually in USA Today or IHeartRadio, it reboots. Once I experienced that loss of settings also and had to factory reset. I'm going to return the phone.
Click to expand...
Click to collapse
I also experienced this in iHeartRadio... Do you use bluetooth?
Sent from my SM-G935T using Tapatalk

[email protected] said:
Try wiping the cache partition
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Is there a way to do this on a non-rooted phone?
Sent from my SM-G935T using Tapatalk

Go into recovery mode with phone completely off .volume down+home button+power button.If that doesn't work factory reset and if that doesn't work return the phone or if possible reflash stock firmware through ODIN.
Sent from my SM-N920T using Tapatalk

Yes, I use bluetooth to listen to IHeartRadio. I tried clearing the cache thru recovery. It did not work.

rocolema said:
Yes, I use bluetooth to listen to IHeartRadio. I tried clearing the cache thru recovery. It did not work.
Click to expand...
Click to collapse
I have been watching watchespn for about an hour with my bluetooth headphones... No problem. I need to test iHeartRadio some more. With that said, I think there is a deeper issue here just because I've never seen settings get changed like that.
Sent from my SM-G935T using Tapatalk

My Bluetooth streaming was janky got this notification and restarted the phone. Problem gone. Dunno the relevance but this was a system notification

Just switched back to iHeartRadio on bluetooth, I was coming here to read a reply so I clicked the home button and rebooted.
Sent from my SM-G935T using Tapatalk

The beta version (6.0.0) of the IHeartRadio app seems to have fixed my reboot problem (which was happening on both bluetooth and earphone modes).
Update, it is still rebooting, even using the beta.

First reboot of the day. IHeartRadio and Bluetooth. I am already running 6.0.0 of the app.
Sent from my SM-G935T using Tapatalk

(note that I don't typically do iHeartRadio and Bluetooth on the weekends.)
Sent from my SM-G935T using Tapatalk

My experience was different. I didn't have any random reboot but I did get the phone just hang.
Before my Springbreak trip I was testing out a sport camera and downloaded an app that could remotely control the camera. Everything seemed to be working smoothly during the test. Then when I was done, I shut down the camera, turned off the phone and started packing up.
Then I needed to use the phone, so I turned it on.. it's turned on but I couldn't do anything, the screen was unresponsive.. I couldn't swipe or press anything... I attempted to reboot it... the power button still worked... the reboot menu came on but I couldn't press anything... I still could turn the screen on and off and brought up the reboot menu.. but jsut couldn't do anything with it..
Only one option was available which is to force it reboot by holding Power and Down volumne.
That was weird, especially on a brand new device.

I've seen it reboot a few times, and it is especially annoying when you are trying to show your device off and it reboots...in front of people...randomly. I am not sure if I want to return it just yet because it is a Touchwiz/android bug that I have experienced on other devices as well. It MAY be an app issue but I can't pinpoint it yet.
I was trying to launch my DJI Phantom app and it just hung/restarted - got stuck on tmobile screen and it wouldn't let me do a hard-reset! Had to wait a few mins and it recycled.

vnguyen972 said:
My experience was different. I didn't have any random reboot but I did get the phone just hang.
Before my Springbreak trip I was testing out a sport camera and downloaded an app that could remotely control the camera. Everything seemed to be working smoothly during the test. Then when I was done, I shut down the camera, turned off the phone and started packing up.
Then I needed to use the phone, so I turned it on.. it's turned on but I couldn't do anything, the screen was unresponsive.. I couldn't swipe or press anything... I attempted to reboot it... the power button still worked... the reboot menu came on but I couldn't press anything... I still could turn the screen on and off and brought up the reboot menu.. but jsut couldn't do anything with it..
Only one option was available which is to force it reboot by holding Power and Down volumne.
That was weird, especially on a brand new device.
Click to expand...
Click to collapse
This is exactly what happened to mine, I was going to return it and put it on the charger and it rebooted. Knock on wood, No problems since. I'm going to keep a close eye on this in case I need to exchange.

Yes, same here. Bluetooth headset with iHeartRadio makes the phone reboot and lose some settings. Maybe a bug with iHeartRadio and 6.0.1.