Hi. So my phone will sometimes freeze up in operation and then reboot indefinitely. Previously it would eventually load normally. However, when I use the app Switch Me and set up a new profile, it doesn't have the reboot problems. So I think it must be an app, or the internal SD card must be malfunctioning.
What I've tried:
-copied everything off the internal SD, reformatted, and copied everything back.
-factory reset, phone worked normally; rooted, worked normally; restored apps in sets of four using TB, rebooting twice after each, worked normally; could not detect a problematic app
-used others' suggestions of disabling wireless and GPS, so they weren't active during boot, did not work
-did not use TB to force move apps to the SD after doing so previously, thought it worked, but was temporary
It's very frustrating. The blinking light that indicates no service will usually be on during the boot loop. The homescreen battery and weather widgets will say "Loading..." indefinitely. Sometimes the battery will show incorrect percentages during bootup. Sometimes it'll just freeze on the USCC boot animation. Twice, I just left it in that case and let the battery completely discharge. Once, the phone started normally the first try; the other, it still remained in the boot loop.
My phone will be replaced anyway in the next week or so, since my screen is cracked. So I can probably wait to see of the next one will have the same problems, if it turns out to be the internal SD. I can't think of any other culprit. Thanks for any help.
-Brandon
Sent from my Motorola Electrify using XDA App
Brandroid28 said:
Hi. So my phone will sometimes freeze up in operation and then reboot indefinitely. Previously it would eventually load normally. However, when I use the app Switch Me and set up a new profile, it doesn't have the reboot problems. So I think it must be an app, or the internal SD card must be malfunctioning.
What I've tried:
-copied everything off the internal SD, reformatted, and copied everything back.
-factory reset, phone worked normally; rooted, worked normally; restored apps in sets of four using TB, rebooting twice after each, worked normally; could not detect a problematic app
-used others' suggestions of disabling wireless and GPS, so they weren't active during boot, did not work
-did not use TB to force move apps to the SD after doing so previously, thought it worked, but was temporary
It's very frustrating. The blinking light that indicates no service will usually be on during the boot loop. The homescreen battery and weather widgets will say "Loading..." indefinitely. Sometimes the battery will show incorrect percentages during bootup. Sometimes it'll just freeze on the USCC boot animation. Twice, I just left it in that case and let the battery completely discharge. Once, the phone started normally the first try; the other, it still remained in the boot loop.
My phone will be replaced anyway in the next week or so, since my screen is cracked. So I can probably wait to see of the next one will have the same problems, if it turns out to be the internal SD. I can't think of any other culprit. Thanks for any help.
-Brandon
Sent from my Motorola Electrify using XDA App
Click to expand...
Click to collapse
I would RSD back to stock, factory reset after (using stock recovery), and then re-root the phone and install apps one by one...don't restore using Ti.
Related
So I got bootlooped yesterday, my phone started up, I saw my home screen, then it shut itself off again and restarted. This is weird because I am not messing with any Custom ROMS. I am rooted, unlocked and am using the Stock ROM which I debloated.
Because of this, I deleted cache and Dalvik cache and did a Factory Reset through Amon Ra. Google Locations and the GPS weren't working, and although it had zero VZ bloat, I decided to just restore my Nandroid backup from a week or so ago since the interface seemed a little more familiar.
Once restored, I debloated a little again and restarted the phone multiple times (to make sure I wasn't messing about with any important apps that could be causing the original issue). The phone ended up restarting fine so I thought I was good to go. Then, today, after installing all my apps, and uninstalling the the Watch widget, I came to the HTC bootscreen. However, the phone wasn't really rebooting, the bootscreen just came on and then immediately went to my homescreen. Regardless, I thought I may restart just to check it out. The first time I restarted, I cycled through the homescreens immediately after boot and the phone turned off. Then I booted it up again and although it's running, I am getting no data. The Mobile Network tab is grayed out. I don't know what to do. I really don't want to factory reset again/restore my original nandroid backup.
I tried *228 but it just says that "A Verizon Wireless Sim card has activated your service and updated your phone's roaming capabilities.
So I tried the Bootlooping and Network fix on the stickied thread (sorry just found it on the website, it wasn't on Google). Regardless, I still have a reservation. If I do indeed bootloop again, even without the battery cover on, would I need to do a factory reset? Because that's what happened last time and I really do not want to go through that experience again.
Does you phone stay booted with the battery cover off?
Sent from my ADR6425LVW using XDA App
JT75 said:
Does you phone stay booted with the battery cover off?
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
No, it wasn't. It froze and then restarted seemingly 5-8 seconds after arrival on the lock screen and unlocking.
Also, after restoring, the Voice Mail app icon cannot be deleted. I have tried Titanium Back up, and now even though its deleted there, the icon is still visible.
I guess I had a different issue when my phone was bootlooping I was able get it to boot with the covers off then do the network fix (it was on wcdma)
Sent from my ADR6425LVW using XDA App
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
Hi,
I'm looking for some general advice and troubleshooting for my phone's issues. My phone started crashing very often, sometimes at complete random, as well as when I was using it fairly heavily (any app that froze my phone for a second before loading before the crashing would now crash my phone). Sometimes it would reboot fine, other times it would bootloop once or twice before reloading fine. I previously tried doing a factory reset, removing my external microSD card, and updating everything via Kies and nothing worked.
I got bored and rooted my phone, did a full wipe, and flashed the latest Infamous update. The problem was still there but it wouldn't crash as often while using it because my phone could handle higher app activity but it's still there. Oddly enough, after flashing Infamous, it often fails to reboot and so I have to do a battery pull before turning it back on, otherwise it won't even vibrate after holding the power button.
I'm just wondering if you guys have any idea what the issue could be. Is it likely still something I can fix? Is this potentially a battery issue or is it a hardware issue?
Thanks so much!
jasonale said:
Hi,
I'm looking for some general advice and troubleshooting for my phone's issues. My phone started crashing very often, sometimes at complete random, as well as when I was using it fairly heavily (any app that froze my phone for a second before loading before the crashing would now crash my phone). Sometimes it would reboot fine, other times it would bootloop once or twice before reloading fine. I previously tried doing a factory reset, removing my external microSD card, and updating everything via Kies and nothing worked.
I got bored and rooted my phone, did a full wipe, and flashed the latest Infamous update. The problem was still there but it wouldn't crash as often while using it because my phone could handle higher app activity but it's still there. Oddly enough, after flashing Infamous, it often fails to reboot and so I have to do a battery pull before turning it back on, otherwise it won't even vibrate after holding the power button.
I'm just wondering if you guys have any idea what the issue could be. Is it likely still something I can fix? Is this potentially a battery issue or is it a hardware issue?
Thanks so much!
Click to expand...
Click to collapse
So when your phone have become unstable , in what condition it was ? did you ever flash it before ... so my s2x did the same thing afer a update with odin on 4.2 ... so i have reflashed it and evrything was working good after
I recently restarted my phone after the battery died, and now everytime it gets to the lock screen, I can unlock it, and it'll function seemingly fine for up to 30 seconds (usually more like 5-10), but then it automatically restarts.
The only apps I've installed since last restarting, maybe a week ago, are FolderSync and Tasker. It's possible I haven't restarted since installing AnyConnect and OpenConnect, although I'm pretty sure I did restart at least once after those, and haven't touched them since. OpenConnect did have some permissions fix item in the settings menu that would supposedly attempt to get it to work on devices where it wouldn't (it didn't work on mine), so that has me suspicious, especially since it seems sometimes these boot loops are related to permissions errors.
I'm running Philz recovery, which I can get into fine. I read about a permissions fix in some recoveries, but Philz (at least mine) doesn't seem to have it.
When the battery died, I was connected to a bluetooth speaker, playing music with Spotify. Not sure if something could have gotten corrupted having it die while the bluetooth connection was active.
It's a T-Mobile S5 and the ROM I'm running XtreSoLite 2.1 Lollipop XXU1BOC7.
Any suggestions for things to check to get it to stop restarting? If I have to wipe it, are there any ways to sort of partially wipe it? Are there a series of things I can try that would go from least extreme (not losing anything) to most extreme (fully re-flashing)? I have been able to open an adb shell and pull everything from internal storage that I don't want to lose.
Thanks in advance for any help.
Hello all,
I have a Moto Z Force Droid (XT1650-02). It's running on Android version 8.0.0, and build number OCLS27.76-69-6. It was acquired from Verizon. It is not rooted (sadly), and the bootloader is locked. It has 32GB of internal storage, however, I added an SDCard(64GB) to increase that storage space.
I'm having some problem(s) with my SDCard, or more so its usage as adopted storage. I've had the phone with the storage for quite a while and everything has been fine. However, 3-4 days ago was when the issues started. One night, my phone was acting really laggy. Which I just chalked up to tech being tech. I let it sit for a bit, tried rebooting it, etc. Well, as time progresses it seems to me that Facebook Messenger is what's slowing it down. So, I try uninstalling it. Of course, this isn't working and android just keeps giving me a helpful little notification that the app is uninstalling (for much longer than it *should* take). I figured I'd reboot into safe mode and try uninstalling it from there. The phone powers off and reboots fine. However, when I tried to unlock the screen, the entire phone froze and crashed after a minute or two. Once it reboots, it gets stuck in the bootloader (or, more specifically, where it says "DROID" and there are little shiny spots moving around the letters). So I used the power button to force the device off and try rebooting again. Again, boots up fine but it freezes at unlock and the cycle starts again.
Around 2 days ago I took it to a Verizon store. Originally I was just told I was going to have to factory reset (which I didn't want to because all the pictures I have and such would be lost. Apps are backed up by Google though). They told me to take out the SDCard, to help save what I could. Then, I got the bright idea to try booting without the card. This time the phone booted fine and unlocked like it should (the only problem now is that I had no internal storage and all the apps that were on the SDCard aren't loading since no SDCard).
When I leave the phone on and install the SDCard, I can browse the internal storage again. However, I can't see any of the files when I try transferring them to PC over USB. As well, after a while of using the phone, or even letting it idle, it will eventually crash and go back to the above botting and not-unlocking scenarios.
Based on how/when the problem started, and the logcats I've grabbed as the phone was crashing, I have reason to believe it has something to do with Facebook Messenger not being removed correctly. [Logcats in the comment below.]
Any help would be greatly appreciated. As well, please tell me if there's anything that needs clarification. (Sorry for the wall of text. I just don't know what else to do at the moment.)
Logcats:
View attachment First.txt
View attachment Second.txt
View attachment Third.txt
So. Bit of an update.
Turns out it's not actually just getting locked in the bootloader. It seems it's been doing a soft reboot.
I've been running "adb logcat" whilst trying different things, until the phone crashes. That's how I got the previous logcats. However, upon "rebooting" the adb logcat continues to run. I can provide a logcat for those, should anybod want it.
WeButterTheBread said:
Hello all,
I have a Moto Z Force Droid (XT1650-02). It's running on Android version 8.0.0, and build number OCLS27.76-69-6. It was acquired from Verizon. It is not rooted (sadly), and the bootloader is locked. It has 32GB of internal storage, however, I added an SDCard(64GB) to increase that storage space.
I'm having some problem(s) with my SDCard, or more so its usage as adopted storage. I've had the phone with the storage for quite a while and everything has been fine. However, 3-4 days ago was when the issues started. One night, my phone was acting really laggy. Which I just chalked up to tech being tech. I let it sit for a bit, tried rebooting it, etc. Well, as time progresses it seems to me that Facebook Messenger is what's slowing it down. So, I try uninstalling it. Of course, this isn't working and android just keeps giving me a helpful little notification that the app is uninstalling (for much longer than it *should* take). I figured I'd reboot into safe mode and try uninstalling it from there. The phone powers off and reboots fine. However, when I tried to unlock the screen, the entire phone froze and crashed after a minute or two. Once it reboots, it gets stuck in the bootloader (or, more specifically, where it says "DROID" and there are little shiny spots moving around the letters). So I used the power button to force the device off and try rebooting again. Again, boots up fine but it freezes at unlock and the cycle starts again.
Around 2 days ago I took it to a Verizon store. Originally I was just told I was going to have to factory reset (which I didn't want to because all the pictures I have and such would be lost. Apps are backed up by Google though). They told me to take out the SDCard, to help save what I could. Then, I got the bright idea to try booting without the card. This time the phone booted fine and unlocked like it should (the only problem now is that I had no internal storage and all the apps that were on the SDCard aren't loading since no SDCard).
When I leave the phone on and install the SDCard, I can browse the internal storage again. However, I can't see any of the files when I try transferring them to PC over USB. As well, after a while of using the phone, or even letting it idle, it will eventually crash and go back to the above botting and not-unlocking scenarios.
Based on how/when the problem started, and the logcats I've grabbed as the phone was crashing, I have reason to believe it has something to do with Facebook Messenger not being removed correctly. [Logcats in the comment below.]
Any help would be greatly appreciated. As well, please tell me if there's anything that needs clarification. (Sorry for the wall of text. I just don't know what else to do at the moment.)
Logcats:
View attachment 4613124
View attachment 4613125
View attachment 4613126
Click to expand...
Click to collapse