Hello.
Last night I was riding my bike through São Paulo. Then I passed into a pothole. I was listening to the radio. After that, the radio turned off. I didn´t stop to solve the issue. When I arrived to my destination, I took my mobile and it was on a safe mode. Some of my apps wasn´t on the desktop at all. Yes, I rebooted and everything went well.
But my question is: what is, how can I acess and what the purpose of the safe mode?
I'm trying the old methods by holding menu and home or just menu while it's booting and can't get into safe mode so they must have changed the key combo, but anyway Safe mode is the same as on Windows so you can boot up if you get stuck in a boot loop and need to fix it.
I see, thanks for trying. But I want to understand what happen last night!
Your best bet is to Google Android + safe mode. The same thing happened to me yesterday, but it happened after trying to open a website while I only had a bad connection only at Edge.. Apparently there's a belief that there may have been a corrupt app installed & yesterday there were a bunch of new app updates from Google, so maybe just the amount of updates caused one to get corrupted?
After rebooting twice, everything came back, except that the widgets on the desktop failed to load.
Rather than mess around I just did a nandroid restore (I do a nandroid backup almost every night & then delete the older ones every few days).
Sent from, The Eclectic Chair.
Related
Hi.
My Galaxy S3 is frequently getting into hotboot looping state for no apparent reason. The only way to get it out of this state is to wipe the phone or restore a backup of the "data" folder only.
After that, it might work for a week, but it might not work for a day (not work = start to hotboot loop).
It happens when after the phone screen is locked, it doesn't wake up anymore. It doesn't answers to any calls (like if it's off) or notifications. Just dies.
Forcing a reboot (by holding the power button) or removing the battery ables me to reboot it, but enter in hotboot looping state. I can make it go thru the whole booting state and I see the homescreen (And that's weird because I'm supposed to see the lockscreen first). Some widgets animation works but the device doesn't answer to touch (two softbuttons vibrates when touched, they do vibrate but don't render anything on Android) and then hotboots. Keeps doing this forever. Booting into safemode USED to work, but it doesn't work anymore, I don't know why.
After wiping the device or restoring the Data backup, device turns on as expected (restoring data takes it back to working state exactly like it was before the backup, even the same lockscreen pattern). I've tried to leave a terminal running logcat to catch the error, but it doesn't write in realtime, so when the bug breaks out, the logfile is empty.
I even thought it could be the S3 memory issue with firmware, but I'm using the "fixed" kernels. Also, it is recoverable, and not permanently dead.
I suspect of some rogue app, but I have too many apps to just go through installing one by one (and waiting even weeks to install the other one). Is there any way I can get a postmortem logfile or make logcat write in realtime?
Thanks
GTMoraes said:
Hi.
My Galaxy S3 is frequently getting into hotboot looping state for no apparent reason. The only way to get it out of this state is to wipe the phone or restore a backup of the "data" folder only.
After that, it might work for a week, but it might not work for a day (not work = start to hotboot loop).
It happens when after the phone screen is locked, it doesn't wake up anymore. It doesn't answers to any calls (like if it's off) or notifications. Just dies.
Forcing a reboot (by holding the power button) or removing the battery ables me to reboot it, but enter in hotboot looping state. I can make it go thru the whole booting state and I see the homescreen (And that's weird because I'm supposed to see the lockscreen first). Some widgets animation works but the device doesn't answer to touch (two softbuttons vibrates when touched, they do vibrate but don't render anything on Android) and then hotboots. Keeps doing this forever. Booting into safemode USED to work, but it doesn't work anymore, I don't know why.
After wiping the device or restoring the Data backup, device turns on as expected (restoring data takes it back to working state exactly like it was before the backup, even the same lockscreen pattern). I've tried to leave a terminal running logcat to catch the error, but it doesn't write in realtime, so when the bug breaks out, the logfile is empty.
I even thought it could be the S3 memory issue with firmware, but I'm using the "fixed" kernels. Also, it is recoverable, and not permanently dead.
I suspect of some rogue app, but I have too many apps to just go through installing one by one (and waiting even weeks to install the other one). Is there any way I can get a postmortem logfile or make logcat write in realtime?
Thanks
Click to expand...
Click to collapse
Try flashing another ROM for S3 and doing a full wipe.
TenKoX said:
Try flashing another ROM for S3 and doing a full wipe.
Click to expand...
Click to collapse
Thanks for the reply.
I already did. It started to happen out of nowhere while I used the Android Revolution HD ROM, then after a few wipes and reinstalls with the same problem, I gave a shot to WanamLite ROM. Exactly same problem. Both are based on the original 4.1.2 Android.
I'm pretty sure it is being caused by some rogue app, because the only thing in common between those ROMs is that I "batch-install" all my apps back from Google Play.
So far, I'm suspecting about Vine (it's the last install that I remember since it started to have this issue) and I have already uninstalled it, but it might have been caused by some app update that broke hell to my phone.
If there were some kind of "black box" that I could retrieve after a crash, it could be the solution
GTMoraes said:
Thanks for the reply.
I already did. It started to happen out of nowhere while I used the Android Revolution HD ROM, then after a few wipes and reinstalls with the same problem, I gave a shot to WanamLite ROM. Exactly same problem. Both are based on the original 4.1.2 Android.
I'm pretty sure it is being caused by some rogue app, because the only thing in common between those ROMs is that I "batch-install" all my apps back from Google Play.
So far, I'm suspecting about Vine (it's the last install that I remember since it started to have this issue) and I have already uninstalled it, but it might have been caused by some app update that broke hell to my phone.
If there were some kind of "black box" that I could retrieve after a crash, it could be the solution
Click to expand...
Click to collapse
If you wipe data, your apps disappear, so I think this is not the problem.
Do another full wipe and DON'T restore your data. Just download again from Google Play and see if the problem appear again.
TenKoX said:
If you wipe data, your apps disappear, so I think this is not the problem.
Do another full wipe and DON'T restore your data. Just download again from Google Play and see if the problem appear again.
Click to expand...
Click to collapse
Thanks for the reply.
I started doing this the first time, but it still crashes it. And as I was wasting too much time with this, the backup option came as a option to not have to click to download over 200 apps one by one. Also, it once happened during a long holiday, and I was in a friend's ranch with no decent internet connection for downloading. All my apps were gone and I was stuck with a default phone for five days.
The backup is exactly the point where I finish downloading all the apps and they're installed. There are no cracked programs or adapted (e.g. Nexus camera). Every single app is obtainable from Play Store, so it's pretty fresh
Funny (actually sad) thing is that it's a system-wide error that a wipe solves it. If I don't wipe data and reinstall the same ROM (which under normal condition is no big deal), it doesn't get past from boot screen.
The worst is it happens instantly. It's working now, but then it crashes. Bam, gone. Few hours ago I was texting my gf and I left the phone for a while, waiting for her answer. After some time I knew something was off, picked up the phone and it was pretty warm (first signal), with the LED blinking some Facebook notification. Tried to wake up but it is in coma. I force a restart and it hotboot loops like I described on first post
It -only- happens when screen is locked. I disabled the screen lock for now to see if it's a workaround, but I'm not holding my breath
It could be a hardware malfunction if it can carry through all the roms you flashed and even when you tried a fresh install without your apps it still happened.
WildfireDEV said:
It could be a hardware malfunction if it can carry through all the roms you flashed and even when you tried a fresh install without your apps it still happened.
Click to expand...
Click to collapse
That's pretty much discarded. Wiping data instantly solves it. It did indeed run for 5 days with no external app without a single problem.
But also it ran over one week with external apps without a problem. I've executed some memory integrity tests and they all reported a-OK.
I'm kinda ruling out the "rogue-app" issue. I thought that recovering "data" from NAND backup was the /sdcard/android/data. But it's deeper than that. Now I don't even have a lead.
Phone already crashed today, without Vine and lockscreen, so that's not the problem. I really need to get some logs out of him. Just need to know how. Only if it could write a realtime log, so I could pull through ADB.
My last resort will be a fresh-fresh android installation, default S3 i9300 ROM, with only essential apps. Already have it triggered for the next crash.
If it goes rogue even this way, I'm running triangleaway and returning it (will be a profit too, the silver border is stripping).
This time around, I'm trying running it without a external sdcard (several files were being corrupted in it, don't know if it's due to force restart by removing battery, or some real issue on the card)
It's a problem within the Facebook social app or Youtube.
I've managed to run the phone flawlessly for weeks without signing in on Facebook, suspecting it might be it.
Today I logged in on Youtube app accidentally, and had to login on Facebook app to retrieve some info. Three hours later, phone went mad again.
I don't know which app caused it, but I think there's some relation to Facebook due to a greater ~involvement~ (couldn't find a proper word.. forgot it) with Android.
I've changed ROMs, launchers, system versions.. but not Kernel. I'll try another kernel and report on Boeffla main thread to see if there's some known bug
Greetings reader. I'm new to the forum but have been viewing threads every now and then, so after having read plenty of times that people should search before posting. I have searched and didn't find what I was looking for, so that's why you can read this now ;p.
4 days ago when I was trying to browse the web in college I wasn't able to connect to the wifi network or even open the wifi settings, so I reset my phone only to find the problem persisting. As if something locked me out of the wifi settings.
I'm perfectly able to access any of the other settings, so I think it's kinda weird.
Shortly after I realised I couldn't get to the wifi anymore my phone started to reboot itself automatically. Ever since that first reboot it just keeps rebooting at the same pace over and over again until I either power it off or until the battery dies.
The phone also get's unusually hot now. Not like, super hot, but definitely hotter than any other time I can remember.
I also get error messages since the problems started saying: 'Process system is not responding'. I then get the option to either force close it or wait. Neither seem to do much if anything at all other than taking away the error message. Sounds kinda critical if you'd ask me.
But so after all these symptoms started to appear I figured I'd just do a factory reset and be done with it, but every time I go into the factory reset settings, I put in my lock screen pattern and then at the last step (pressing the Erase all data button) it just does nothing.
I can touch the button and it does give the animation that it is being pressed, but it just doesn't do anything.
The phone doesn't freeze though, I can still navigate after pressing the button only to see it reboot again shortly after.
After that I tried to flash the rom, but for some reason my PC refuses to show my phone's internal memory in my pcor any sign of my phone's connection at all.
I haven't tried it on any other pc yet, so it might just be my pc, though I doubt it is since it was perfectly able to recognize it shortly before all this started.
The device hasn't endured any shocks lately or expsure to water or whatever, so I think that's ruled out as well.
I am running the stock rom, 2.3 Gingerbread I believe, and the warranty is already way over date (I think. I'll have to check that).
Any suggestions as on how to determine what could be causing this, or how to fix it? Because I really don't want to buy a new phone xD.
Macowski said:
Greetings reader. I'm new to the forum but have been viewing threads every now and then, so after having read plenty of times that people should search before posting. I have searched and didn't find what I was looking for, so that's why you can read this now ;p.
4 days ago when I was trying to browse the web in college I wasn't able to connect to the wifi network or even open the wifi settings, so I reset my phone only to find the problem persisting. As if something locked me out of the wifi settings.
I'm perfectly able to access any of the other settings, so I think it's kinda weird.
Shortly after I realised I couldn't get to the wifi anymore my phone started to reboot itself automatically. Ever since that first reboot it just keeps rebooting at the same pace over and over again until I either power it off or until the battery dies.
The phone also get's unusually hot now. Not like, super hot, but definitely hotter than any other time I can remember.
I also get error messages since the problems started saying: 'Process system is not responding'. I then get the option to either force close it or wait. Neither seem to do much if anything at all other than taking away the error message. Sounds kinda critical if you'd ask me.
But so after all these symptoms started to appear I figured I'd just do a factory reset and be done with it, but every time I go into the factory reset settings, I put in my lock screen pattern and then at the last step (pressing the Erase all data button) it just does nothing.
I can touch the button and it does give the animation that it is being pressed, but it just doesn't do anything.
The phone doesn't freeze though, I can still navigate after pressing the button only to see it reboot again shortly after.
After that I tried to flash the rom, but for some reason my PC refuses to show my phone's internal memory in my pcor any sign of my phone's connection at all.
I haven't tried it on any other pc yet, so it might just be my pc, though I doubt it is since it was perfectly able to recognize it shortly before all this started.
The device hasn't endured any shocks lately or expsure to water or whatever, so I think that's ruled out as well.
I am running the stock rom, 2.3 Gingerbread I believe, and the warranty is already way over date (I think. I'll have to check that).
Any suggestions as on how to determine what could be causing this, or how to fix it? Because I really don't want to buy a new phone xD.
Click to expand...
Click to collapse
Since you've not modified your Sola in any way.
Give this official method a try.
http://xperiafirmware.com/component/content/article/2-uncategorised/29-sony-update-service
Hello
I've had a Samsung Galaxy S3 for ages, unfortunately for me, the phone recently just switched off, then on, then won't go past the "Samsung" screen. Ah, I thought (well, something a bit more sweary) - but I had a backup identical model phone in case one broke, so I started using that. Moved all my apps, installed banking app etc, and then happy.
Or so I thought...
The new (well, it's an old phone, but one I haven't been using, bought as back up) phone now switches off when charging every night, an issue which was going to switch to me charging it during the day when I can stare at it and see if anything happens to make it switch off, but then I realised it switches off each night even when it isn't charging.
I have a bigger battery to hold a charge for a few days, and so even when I don't charge it, just have it next to me as I sleep - and next morning it will be off. I presume it might be switching off around 5am... this is only a rough guide as if I switch it back on, and flick through the phone, I see my unread emails are up to around 5am, and then after a few minutes it logs back into the internet etc and brings me newer emails.
I first thought it was that it kept switching off when charging... but now I know it does it at (I presume) the same time every night even when it's not charging. Can't use it as an alarm clock anymore, as it's off before the alarm goes off. Anyone have any idea what's happening?
Did you copy all of your data and settings?. Most likely you have a software conflict going on.
I highly recommend you backup your data from all 3rd party apps. Do not backup your system apps data, google data, apps or games that cloud sync or phone settings, ie wifi passwords etc.
You must allow samsung apps, google and other cloud apps to sync their own way and you must calibrate the phone for wifi manually.
Beyond that you'll need to reflash stock firmware and start over using the guidlines I have given you above after restoration of the firmware (and root if required).
Beamed in by telepathy.
I assume when I installed on the other phone, it switched settings when I log in to various things. Because I installed everything asap, I've no idea if one thing is causing the issue.
How do I get the phone to calibrate manually? Apologies, I'm not great with techie stuff I add the wifi details, and logged into settings - is that manually? Things are backed up to themselves, so when I log back in it resets to previous settings when it syncs. Should I try and work out how to prevent all things from backing up manually? Haven't logged back into any games, although they might be installed, haven't actually signed in or used them.
How would I go about reflashing stock firmware? Doesn't sound like anything I've ever done before, but up for a challenge
By manually i mean just setup wifi yourself rather than allowing a backup. Same for system apps.
The app data will contain references to the old phone which will confuse it. All of that must be rewritten on the specific device to match the phones identity.
3rd party apps are usually OK with backups but still shouldn't be trusted, but they don't usually bootloop the phone. They just force close instead.
Flashing firmware will reset the phone back to factory and rewrite the operating system, removing any software bugs in the process. To learn how to use odin you can find countless guides online too.
A straight forward "factory reset" via either the phone software or the recovery menu could solve the problem rather than flashing.
If I were you, I'd just factory reset it and then allow the phone to run for a few hours to see if the problem reoccurs in a factory state. If the phone asks for a google login just use the normal account and allow all updates to happen but switch off backup and sync for the short term. If all seems good then you know there was a bad app somewhere.
Beamed in by telepathy.
shivadow said:
By manually i mean just setup wifi yourself rather than allowing a backup. Same for system apps.
The app data will contain references to the old phone which will confuse it. All of that must be rewritten on the specific device to match the phones identity.
3rd party apps are usually OK with backups but still shouldn't be trusted, but they don't usually bootloop the phone. They just force close instead.
Flashing firmware will reset the phone back to factory and rewrite the operating system, removing any software bugs in the process. To learn how to use odin you can find countless guides online too.
A straight forward "factory reset" via either the phone software or the recovery menu could solve the problem rather than flashing.
If I were you, I'd just factory reset it and then allow the phone to run for a few hours to see if the problem reoccurs in a factory state. If the phone asks for a google login just use the normal account and allow all updates to happen but switch off backup and sync for the short term. If all seems good then you know there was a bad app somewhere.
Beamed in by telepathy.
Click to expand...
Click to collapse
Ahh, cool, gottcha! Ok, will try soon. Surprisingly, I've switched off the phone every night instead of it auto-switching off at around 5-6am, and surprisingly it's so far going well. Had it on for 3 days and only at 47% now, so it's promising, still does switch off occasionally during the day, but I've just ignored that. Will do a factory reset in the next couple of days and report back Thanks for the help
Hello guys, something really weird happened, heres a little background on events that may be related.
First of all the device is a rooted Samsung Galaxy S8+, yesterday I arrived abroad, and today I bought a local SIM card and had no issues with it, and later today I rented a car for a long trip and half way I realized that the car has Android Auto on its multimedia system, so I looked up the Android Auto app on the store and didn't find any so I googled it and downloaded the APK.
At first the car refused to even find my phone and did not want to connect to it, after a while I suspected that Developer Mode may be the culprit so I turned it off and voila, it connected, the rest of the ride went flawless with Waze on the car's screen.
When it was finally time to head back to the hotel, I got on the car, turned on Android Auto again, waze screen showed up but it completely froze, I tried messing around with it but nothing happened, screen is frozen shut, so I decided to try and restart my phone, the next thing I know it isn't booting up with a red "Custom Binary blocked by FRP Lock."
I've read online that I need to reflash the stock ROM, but keep in mind I'm in a foreign country with no access to a computer (writing this on my mom's phone's)
Is there anything I can do? Why did this even happen? And most importantly, would reflashing format my phone? I really don't want to lose my stuff.
Thanks in advance for any kind of support.
The only thing you can do is flash a stock rom using odin and you will lose all your data so i would advise you to flash recovery and do a backup then pull the backup file using adb after that you can flash your stock rom
Hey there Guys,
so, I am desperate enough with this issue, that I'd actually pay the one who fixes it for me.
If you need specific infos, let me know what and where to find. Cuz I'm hella stupid with this stuff.
Bought a Samsung S9+ on Amazon. (should work just fine)
Model Number: SM-G965F/DS
Here we go, (try to remember as much as possible, as its 1 year ago)
since I can't live without root, I did do so by the magisk method. I think it didn't work so well, cuz there were system issues. Couldn't boot anymore. Thought I "bricked" it.
I managed to factory reset and boot it again, with an operating system I downloaded from google results, of which I thought was the correct one for this model. (problem might be here? Wrong OS? If so, where and what exactly do I have to download?) Its kinda bs to me, that there are different versions depending on the country etc.
Lets continue:
Managed to successfully root it then. Everything worked fine. Samsung s9+ rooted.
After a short while, I encountered the issue I am facing since then.
Problem:
My Samsung is rebooting every day. Suddenly turns black, reboot with Samsung Logo. Fun fact, all tabs are still opened in the background afterwards. (no real reboot?)
Happens when:
- time is not fixed. Anytime possible.
- even when I'm not using it. (but mostly)
- Even while video recording. Not app specific. (I always keep only one app open btw.)
- sometimes when it happens while I use Instagram, I'm logged out of Instagram afterwards. (not sure if it happened with Facebook, but might) (I use Insta a lot, Facebook almost never)
Solutions I tried.
- Empty cache. (I think I tried it the correct way.)
- Factory reset
Not confident in the app issue belief, that I'd uninstall every single app for 2 days each.
Assumption:
I don't feel/think its one app. If so, maybe Instagram? But shouldn't be the case though. As said, I always close all apps after I put down my phone.
Maybe its the OS? What do i know..I'm a scrub.
Help highly appreciated. The reboots are driving me crazy and are tremendously inconvenient sometimes.
pkenso said:
Problem:
My Samsung is rebooting every day. Suddenly turns black, reboot with Samsung Logo. Fun fact, all tabs are still opened in the background afterwards.
Click to expand...
Click to collapse
Reasons to Cause Android Phones Keep Restarting
1. Corrupted data in memory.
2. Incompatible third-party apps.
3. Outdated cached data.
4. Hardware issue.
Boot Android into Safe Mode
Safe Mode is a good place to help you to track down the causes of problems occurring on your Android phone. Once you boot your phone into safe mode, all third-party apps installed on your device will be got rid of. In this mode, check if your phone still keeps restarting without any reason. In case the problem disappears, then a third party app is the main cause of the problem. All you need is to find out and delete it from your phone.
jwoegerbauer said:
Reasons to Cause Android Phones Keep Restarting
1. Corrupted data in memory.
2. Incompatible third-party apps.
3. Outdated cached data.
4. Hardware issue.
Boot Android into Safe Mode
Safe Mode is a good place to help you to track down the causes of problems occurring on your Android phone. Once you boot your phone into safe mode, all third-party apps installed on your device will be got rid of. In this mode, check if your phone still keeps restarting without any reason. In case the problem disappears, then a third party app is the main cause of the problem. All you need is to find out and delete it from your phone.
Click to expand...
Click to collapse
So I assume if the problem still persists in safe mode, its a firmware issue?
I'll try the wiped cache now until it reboots again. If so, then safe mode.
safe mode (no apps) just seems hard as I use my phone for work and the issue appears randomly within 48 hours..
--- Instead of safe mode, would be the same if I just uninstall for example a few apps for a certain time?
--- I read about a master reset. Wouldnt the simpliest and 100% working method be to just reset the phone with a new firmware? Which I can download where?