So my G3 has suddenly decided to be unstable. A little frustrated about it as this is my 2nd replacement device already, and my upgrade is not available until September. (In all fairness, it does take 6-9 months in between failures, and I think the last one was me being stupid and forgetting to flash the correct modem/baseband before re-installing a ROM, but it is a little frustrating, since the phone itself is fairly nice.)
As far as the issues:
I am running stock, rooted 47A. And things had been fine for a long while. Now, however, the phone has suddenly decided to occasionally "hide" apps and block functionality from me.
Google now will not launch from the home button, and google on tap is unavailable. I can launch google now from the app shortcut, or by swiping to the far left when using the Google launcher. When using the stock LG camera, sometimes the phone will shut off for no apparent reason, the way Google camera used to do on custom roms...
If I reboot, 50% of the time, Google launcher will not show as an installed option, and along with that, google keyboard will be missing, and several other apps too. If I turn off the phone let it sit for a few minutes and reboot, the missing aps mysteriously reappear. Running apps do not seem to be affected, and will remain in memory and be selectable and usable after a reboot, as in normal MM behavior.
I suspect imminent hardware failure of the internal, baked in storage or other hardware, as I cannot think of a software issue that would give me these intermittent problems. The phone is occasionally running warm to the touch, but not unusually hot, and I have gotten no thermal warnings to shut it down so far.
Flash the 10B TOT. After you confirm everything's working okay, you can re-root with the Stump app, put TWRP on with TWRP Manager from the Play Store, then flash whichever Bootstack and ROM you want.
You can use the built-in LG Backup to backup your user apps and data, and some system data, although with your phone having weird problems it's always a possibility that restoring any of that information may cause the same problem to start happening again.
TOTs flash more partitions than KDZs and can fix some weird issues that flashing KDZs or ROMs can't fix - I can attest that's the truth from personal experience.
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
OK, this is really weird - after getting the 4.2.2 update, my phone reboots itself every night, not 100% sure it's exactly the same time, but it's been while sitting in my pocket or on the table, not even in use. At first I assumed it was Zooper, which I had installed right after the update, but I disabled it yesterday and got the reboot again tonight.
I even checked my Tasker to make sure some auto-reboot profile hadn't installed itself!
Any hints about how to diagnose this? Do I have no choice but to remove apps one by one? Most of the apps I run are the same ones I run on my TF300 tablet which also has 4.2.2, so don't know if it could be an app.
Did it again tonight and it is the exact same time - 9:19pm It's also interesting is that this is about the time of day I did the update to 4.2.2 It's like some daily thing going on. It must be some new app applied by default by the update, I've disabled some of the obvious new apps.
Does anyone know if I do a factory reset will it go back to 4.1 (which worked fine for me), or will it stay at 4.1?
PhysicalEd said:
Did it again tonight and it is the exact same time - 9:19pm It's also interesting is that this is about the time of day I did the update to 4.2.2 It's like some daily thing going on. It must be some new app applied by default by the update, I've disabled some of the obvious new apps.
Does anyone know if I do a factory reset will it go back to 4.1 (which worked fine for me), or will it stay at 4.1?
Click to expand...
Click to collapse
the Factory reset will erase all ur Apps and will stay in 4.2.2 ......
Looks like this update has really screwed up my phone. After a couple of more nights of trying to disable more apps, and trying to catch the error with logcat (nothing that makes any sense in the log, no error or crashes preceding the reboot) I decided to factory reset.
It rebooted again tonight, about 24 hours after the factory reset.
Also, intermittently now the power button will not suspend the phone, though I can hold it and reboot, I don't know any other way to put it to sleep.
Looking at the log some more, the only thing that gives any hint is that there was Location Services activity before the crash. Googling around about my problem showed there was a bug in Location Services early in 4.2 but the claim was that it was fixed. I guess tomorrow night I'll try turning off Location Services as well.
PhysicalEd said:
Looks like this update has really screwed up my phone. After a couple of more nights of trying to disable more apps, and trying to catch the error with logcat (nothing that makes any sense in the log, no error or crashes preceding the reboot) I decided to factory reset.
It rebooted again tonight, about 24 hours after the factory reset.
Also, intermittently now the power button will not suspend the phone, though I can hold it and reboot, I don't know any other way to put it to sleep.
Looking at the log some more, the only thing that gives any hint is that there was Location Services activity before the crash. Googling around about my problem showed there was a bug in Location Services early in 4.2 but the claim was that it was fixed. I guess tomorrow night I'll try turning off Location Services as well.
Click to expand...
Click to collapse
The update may have screwed up somewhere in the middle, you could try to re-ruu your phone or unlock the bootloader and flash a custom rom, also the thing about the power button not putting the phone to sleep or doing anything than reboot on long press happened to me on each and every custom rom and I never did any OTA, got my phone, unlocked bootloader and flash away from sense, my hboot is still the one that it came with, but for me that thing happens really randomly, like once every 1 or 2 weeks, and when that happens for me the volume buttons stop working also till reboot, I was thinking I was the only one facing it so I kinda decided not to talk about that as I saw no one say anything about it, but I am also one of those for who the phone turns off exactly when my phone goes to 6% battery whatever I do, on whatever rom I am and even in the recovery, so I was thinking that maybe vodafone modified something on it, that's an other reason I didn't say anything about the buttons becoming unresponsive...
So what I would recommend is to re-ruu your phone or go to a custom rom (or if none solves anything the phone may have some kind of hard brick).
Just to help out anyone else who ever has this problem.
It was not location services.
I can see clearly in two logs an HTC process crashing. This seems to cause a cascade that leads to reboot.
I contacted HTC tech support, they suggested I boot up in a recovery mode and try to wipe data cache. They were surprised to find that attempting to do that caused a reboot.
So as Ranomez suggests above, they want me to re-do the update with the RUU when they release it, which they said would be "soon" last weekend.
On the other hand, my battery life after this update is fantastic, so I've decided I can live with this to not have to worry about recharging by mid-afternoon!
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
Anyone else had this since the latest stable miui update? The GPS issue arose and had issues with various apps and games causing the phone not to respond, others would hang for ages then work eventually after it kicked back into life.
I went to the developer global ROM to see and the GPS worked but the app hangs still persisted.
I unlocked the bootloader yesterday and put lineage 14.1 on (official). Same issue is persisting. I've formatted the entire internal storage before flashing the latest nightly along with firmware and gapps.
Games such as Crossy road, smashy road, mario run all won't load just sit on a black screen. Dawn of titans however does seem to work.......
Any thoughts?? :silly:
Just tried the Disney version of Crossy road as a test.....loads then hangs on the 1st screen for an age.....then loads to the screen where you have to press the play button......5 app isn't responding messages later (after clicking wait) and finally kicks into life......not sure why all these apps hang for so long then eventually work?
Any options in developer options that may resolve this?
Just reinstalled the original game and eventually got it to load after freezing forever and a ton of not responding messages, then after selecting a gift to open the freezing came back again.....it's struggling with something as works fine during gameplay
No worries found the problem, was the micro SD card it's knackered.....didn't think it would affect the apps and system as there stored on internal memory??