My phone is stock and I am not interested in any mods.
The m9 has a lot of issues and I found another.
HTC told me to boot in safe mode to try to see if an app was causing issues. For the record, I get a screen black out when swipping away a screen or returning to home screen when first booted up. I reset twice and it's still there.
Anyway, I try safe mode out and when I boot back up, all of my apps seemed to have their data erased. All of my app placement customizations were gone and I started getting an error for LTE, which has never happened prior. It was a mess.
I factory reset again and it seems fine, appearing to be as it was before.
What was that glitch about? It was such an odd and incredibly bad thing to happen.
ghostblonde said:
My phone is stock and I am not interested in any mods.
The m9 has a lot of issues and I found another.
HTC told me to boot in safe mode to try to see if an app was causing issues. For the record, I get a screen black out when swipping away a screen or returning to home screen when first booted up. I reset twice and it's still there.
Anyway, I try safe mode out and when I boot back up, all of my apps seemed to have their data erased. All of my app placement customizations were gone and I started getting an error for LTE, which has never happened prior. It was a mess.
I factory reset again and it seems fine, appearing to be as it was before.
What was that glitch about? It was such an odd and incredibly bad thing to happen.
Click to expand...
Click to collapse
It is not a glitch, that's how safe mode works. It turns off all network connection, 3rd party apps and only loads necessary drivers. Similar to the way safe mode works on a computer. However Android can't recover data once it is lost after reboot.
So you're telling me safe mode is suppose to basically screw up your phone in order for you to see if maybe a third party app is a problem? That. Is. Crazy. It really defeats the purpose of any aid it could have.
It's a huge risk to take. I wonder why they'd design it this way. On the sprint forums, anyone who reported putting their phone in safe mode never mentioned any losses after. Maybe they didn't want to state them then?
schmeggy929 said:
It is not a glitch, that's how safe mode works. It turns off all network connection, 3rd party apps and only loads necessary drivers. Similar to the way safe mode works on a computer. However Android can't recover data once it is lost after reboot.
Click to expand...
Click to collapse
Wait, are you referring to data that could have happened during safe mode? And once it was back to normal, it didn't save any new data? If so, that's not what I was talking about.
Literally all app data, even preexisting was gone and my phone set up was hugely altered.
ghostblonde said:
Wait, are you referring to data that could have happened during safe mode? And once it was back to normal, it didn't save any new data? If so, that's not what I was talking about.
Literally all app data, even preexisting was gone and my phone set up was hugely altered.
Click to expand...
Click to collapse
Yes all app data is erased during safe mode that includes Sense Home which is you home screens setup. Android is setup that way because it loads only apps no data. Data is usually the cause of issues. If everything works fine in Safe Mode mostly the issue is the apps data. It is an Android thing and not phone specific.
Related
I'm not sure if anyone has experienced this on their 3d before and when I searched the topic there was no real definition or solution. Yesterday while playing around on the phone I had a random reboot (ZR3D Rom using Anthrax) and when the phone booted again I had the message "Safe Mode" in the lower left hand of the screen.
God knows I thought I really screwed something up, booted to recovery, wiped cache, dalvik, and fixed permission to no avail. So this morning I get to work and have some time to look up this safe mode and came across this article:
http://androinica.com/2010/08/how-to-activate-android’s-safe-mode-to-get-out-of-a-force-close-loop/
I had no idea that our phones could do this and its quit the neat feature, in a nut shell if you have a program that keeps force closing and you can not use the phone because of this, the phone can be booted into the safe mode which prevents the phone from loading 3rd party apps so you can remove the app that was giving you problems. All that is needed is a battery pull then hold the menu button while powering the phone on and vice versa to get rid of safe mode.
Like I said I'm not sure if anyone else had this problem or even knew about it but I thought I would share just in case someone needs help.
That's some good info. Thanks.
Holding the volume down once the splash screen appears will put you in safe mode as well, with any reboot no need for a battery pull. You will feel a hard vibrate, stronger than the normal quick one you get on a normal boot.
interesting info... didn't know that.
on another note.... i have never had a third party app repeatedly force close on me. in the ROM flashing world it has always been a system app.... this method would be useless in that scenario lol.
interesting, though, learn something new everyday.
It has actually been helpful for me, finding out what apps are comparable with joelz's cm9 kang rom.
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
Maybe once every couple of days my phone goes crazy. It doesn't reboot, but it starts randomly dialing phone numbers again and again, the screen goes black, then comes back, and basically the only fix is to reboot. Any thoughts on what might be going on? I'm running the original Kitkat rooted, and that's the only thing really modified. Oh, and the hotspot mod to allow tethering.
Try a factory reset (wipe data/cache/dalvik)?
My only other suggestion would be to flash the 10B TOT and start from scratch.
You can use the built in LG Backup to backup your user apps/data and limited system data, and restore if you attempt either. Note that flashing the 10B TOT will wipe your internal storage.
If you restore apps, be sure and test the phone first to verify if the problem happens without restoring your apps and data first, or at least with a limited set of your restored apps.
android94301 said:
Maybe once every couple of days my phone goes crazy. It doesn't reboot, but it starts randomly dialing phone numbers again and again, the screen goes black, then comes back, and basically the only fix is to reboot. Any thoughts on what might be going on? I'm running the original Kitkat rooted, and that's the only thing really modified. Oh, and the hotspot mod to allow tethering.
Click to expand...
Click to collapse
If "@roirraW "edor" ehT" suggestion doesn't work, do you happen to notice if it happens when either the phone is in your hands, etc? Makes me wonder if the digitizer/touch screen is going bad and it's mistakenly thinking you're hitting a quick dial or something. That is strange though.
How old is the phone? Could also be an issue with the hardware other than the digitizer and/or touch screen.
Also, have you side-loaded APKs from places other than Google Play and Amazon App store? If so, which specific apps? I try not to side-load anything that isn't from Google Play or Amazon. Too many malware things out there. It's one of the reasons why I don't root with Kingroot. I don't trust that at all considering where it's from.
I have a G2 that does the same thing. Goes crazy for no apparent reason. it's completely factory original and I suspect it's the digitizer too It acts like someone is just tapping away at the screen but at warp speed. I finally just retired it to my desk drawer.
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?
So, my Samsung Galaxy A10 got into a bootloop and I'm 90% sure it was caused by short storage, because seconds before it started I saw the storage was full. I've had a similar problem before, where my phone would randomly reboot and stop when I clean up some space, but now it just locks itself on a bootloop and freezes on the Samsung logo.
I tried entering Safe Mode, but my phone just won't load it no matter how many times and how many buttons i press. Alright, "let's try Recovery Mode", i thought, but it was also very hard to do because the buttons wouldn't work most of the time. I managed to enter it around 4 times in a span of 3 hours and I got two different screens. One screen was what I believe to be the standart, with options to clear cache, factory reset and etc. The other one only had the option to clear app data, no idea why it changed or what triggered it. In these few instances where i could access the Recovery Mode, I tried clearing cache, repairing apps and clearing app data, but nothing worked.
I can't turn off my phone either, I tried holding the power button for almost a minute with no results. Maybe that's why the recovery mode didn't work...? Right now I'm waiting for my phone to run out of battery and see if it helps.
Also, one thing that is kinda concerning... everytime it reboots, before the Android logo appears, the screen glitches for a millisecond in a vibrant color.
Please, is there any way to fix it without losing my data? I'm sort of a noob so I have no idea how bootloaders and similar things work, I'd be really thankful if you guys could help
Welcome to XDA
Meh... why isn't your data on a SD card?
If you used a SD card as a data drive... you be able to do a factory reset and not lose critical data.
If you can't connect with the PC and you can't get into safe mode I don't see how you can recover the data. Maybe someone here has a plan for you...
blackhawk said:
Welcome to XDA
Meh... why isn't your data on a SD card?
If you used a SD card as a data drive... you be able to do a factory reset and not lose critical data.
If you can't connect with the PC and you can't get into safe mode I don't see how you can recover the data. Maybe someone here has a plan for you...
Click to expand...
Click to collapse
Thanks! Yeah, no SD card for me
Draining the power didn't help, but I figured out why the buttons didn't work: I was supposed to press them when my screen started glitching, not on the android logo (leaving this info here in case someone else has the same problem). Still unable to access safe mode tho, only recovery.
Welp, most of my data was only personal things and at least I can backup some stuff with my google account, so I did a factory reset. Now it's working again, which is great, I just wanted my phone back honestly :,)
Lik_2345678 said:
Thanks! Yeah, no SD card for me
Draining the power didn't help, but I figured out why the buttons didn't work: I was supposed to press them when my screen started glitching, not on the android logo (leaving this info here in case someone else has the same problem). Still unable to access safe mode tho, only recovery.
Welp, most of my data was only personal things and at least I can backup some stuff with my google account, so I did a factory reset. Now it's working again, which is great, I just wanted my phone back honestly :,)
Click to expand...
Click to collapse
Boot loops are tough. Sometimes after a couple tries it may go into safe mode but don't count on it. Another question is what caused it, a poorly coded or incompatible 3rd party app running at start up? You don't want a repeat. It may have been a single event upset that corrupted the user data partition, these are rare but can happen.
Get a SD card and use it as a data drive, everything you need to do a complete reload should be on it including installable copies of all your apps. A full reload with no internet connection can be done like this. Since all the data is already on it for a reload, no time is wasted reloading data.
The SD card is a valuable asset if you use it correctly.