My 4G will be 2 years old in February. It is quite buggy now, it likes to lag a lot or glitch, it's definitely not the lightning machine that it used to be. I saved all of my data and am going to perform a wipe/factory reset and wipe the cache partition (hopefully I am allowed to do that, if not, oh well too late).
Is there something more potent then a factory data reset using the Android Recovery mode while not in the phone OS? It resets the phone but I have the latest OS, which I think could end up keeping all of my bugs. Can I go back to the original OS when the phone shipped and legitimately start over and re-update everything? I logged back in and an app widget was still there with writing on it, some of my pictures, and some icons I moved around. this is after I did a rest outside of the phone, then went in the phone and did another reset. So much for wiping all of my data I guess.
So, if this does not fix the buggyness of the phone, what should I do? The phone likes to press buttons randomly and I have to hit the power button to lock it, and then unlock it for the magic button pressing to stop. This is common. Apps are slow or time out a lot and it takes the phone FOREVER to reboot. It love to randomly restart, especially using pandora or spotify. It takes a long time to connect to Wifi, sometimes I have to go to the wifi settings to wait for it to automatically choose my saved network, which baffles me like crazy.I did have the most recent update of course. I think the finger print scanner also stopped working... or it never did work. Lastly, the vibrating unit doesnt always vibrate, it likes to vibrate on a few keystrokes and it randomly stops, then starts up again. **** this phone. It really makes me want to go to an iPhone... and I am a hardcore windows computer tech and I hate apple, but ****, why cant anyone build a stable OS?
So, assuming my phone works correctly, what should I do to it once it's up and running? I am ready to Root the phone and try some new apps and hacks and what not, especially if it makes the laptop dock mode faster, cause right now it's slow as ****.
Factory reset basically wipes the /data partition.
I would also recommend you do a format of the internal sd, after the factory reset (see storage in the system settings). This way, files on the sd will have no impact on apps as you reinstall things.
Regarding returning to an earlier Rom version, I would not recommend as being part of the solution. Newer Rom version are better usually. Gb by motto is solid.
Sent from my MB860 using Tapatalk 2
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
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.
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
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.