Related
Anyone have any idea what may have happened here?
I was unexpectedly away from home, but using the device quite heavily, and didn't have a method to charge the battery.
Once the battery had drained to about 3%, I switched the phone off but I ended up needing to make another call. The phone booted, but all core apps returned a force close message. Phone, Maps, Google Account, all the main stuff... Other apps would launch and function with no problem though.
Thinking it may have just been a glitch, I rebooted the phone again thinking there would still be just enough juice to allow a phone call, but while booting, the battery totally failed.
Once I had a chance to plug in the charger, all core apps continued to fail, even though the phone now had plenty of power.
Even after a battery pull, the same issues continued, rendering the phone pretty much useless. No link to Sprint, no WiFi network, nothing...
The phone is rooted with v1.5.2 RC and Fresh ROM v1.0, so lacking anything else to do, I performed a Nandroid restore from a backup made about 2 days ago and that seems to have fixed up the problem. (whew.. I did not want to resort to the RUU)
But, I just can't figure out what may have caused this odd behavior in the first place....
Are you using apps2sd?
No, I'm not using the apps2sd feature.
The lockscreen text showed "No service" and the notification bar icon showed the same. The "phone" application was the only one that would attempt to restart after being forced closed. After a second fc though, it would apparently give up.
Oh, and just remembered one other oddity.. Once booted and all force close messages removed, attempting to turn on the mobile network resulted in a hard reboot. I really didn't expect anything since there was no service link, but I was just clicking various shortcuts to see what did or didn't work.
Good part is that a Nandroid restore saved the day, so it's more of a curiosity at this point to what the root cause might have been.
I wouldn't have thought that a battery drain could have corrupted the apps or prevented the root filesystem from mounting.
You probably had too many apps installed. It's a known issue with the Hero, where having too many apps installed causes a bunch of core apps to fail to load for no apparent reason. The phone losing power just caused it to reboot, which triggers the issue.
mkhopper said:
Anyone have any idea what may have happened here?
I was unexpectedly away from home, but using the device quite heavily, and didn't have a method to charge the battery.
Once the battery had drained to about 3%, I switched the phone off but I ended up needing to make another call. The phone booted, but all core apps returned a force close message. Phone, Maps, Google Account, all the main stuff... Other apps would launch and function with no problem though.
Thinking it may have just been a glitch, I rebooted the phone again thinking there would still be just enough juice to allow a phone call, but while booting, the battery totally failed.
Once I had a chance to plug in the charger, all core apps continued to fail, even though the phone now had plenty of power.
Even after a battery pull, the same issues continued, rendering the phone pretty much useless. No link to Sprint, no WiFi network, nothing...
The phone is rooted with v1.5.2 RC and Fresh ROM v1.0, so lacking anything else to do, I performed a Nandroid restore from a backup made about 2 days ago and that seems to have fixed up the problem. (whew.. I did not want to resort to the RUU)
But, I just can't figure out what may have caused this odd behavior in the first place....
Click to expand...
Click to collapse
oddly enough I've had a similar experience. it was 2 days before christmas and i was doing all my last minute shopping. heavy use of the phone caused the battery to die, so i just threw it on my car charger. it booted, but REFUSED to get any data at all (i didn't run into any fc's, however). I rebooted it 3 times and each time the issue persisted.
I was running the AOSP 2.0 build at the time, so i flashed my backup of 2.1 and everything was fine from there...
patches11 said:
You probably had too many apps installed. It's a known issue with the Hero, where having too many apps installed causes a bunch of core apps to fail to load for no apparent reason. The phone losing power just caused it to reboot, which triggers the issue.
Click to expand...
Click to collapse
Hmm, good possibility there. Just did a count and I do have 85 apps installed.
(whoof, I had no idea the number had gotten that high. just too many useful apps for this phone.
I had previously posted an issue I have had with my phone randomly shutting down when it was in sleep mode. The only way to get it back on was to pull the battery. It was not ROM specific, and was driving me crazy!. I Odined back to stock, formatted my sd card, rerooted, put a ROM on my phone and the problem seemed to go away. I just installed Launcher Pro, to see if It will happen again, so far working fine. I think Titanium backup may have something to do with this issue, because last time it started happening, I had done a restore with titanium. It might also have something to do with the SD card. I am going to play with this more over the next few days, and If I can figure it out, I will update this post. Any comments will be very appreciated.
I'm on the latest non-rooted stock. Lately, I've been having lots of serious bugginess and slowdown, crashes, all sorts of issues. I've had this tab since 3 week after it came out, so it's been a while. I've though about wiping it and starting over, but I don't know if that will fix my problems, and doing so will force me to have to reconfigure EVERYTHING, since Google still allows us no local data backup system and their supposed cloud data backup seems to only remember minor settings, and often doesn't work at that.
(seriously, you'd think they would at least offer some sort of explanation about how it works, what it backs up, or even just let you log into their services and see what's been backed up. very odd for a cloud computing company to be inferior to the iPad's backup system right now....)
I honestly don't want to root, because I keep seeing posts about glithces and serious malfunctions resulting, and honestly I don't have time to deal with it, I've rooted 3 phones and it's just a pain to unroot for updates, hope it gets rooted agains, without bugs, etc.
So, does anyone know what the cause of these problems may be, if it would be fixed by wiping and restarting, any other ways to fix it, etc.?
Making a backup now will only backup your issue
Sounds like a rogue app is causing your issues.. Chances are if you did a backup. then reset your device. If you restore a backup you will put the problem back..
Its not that much to allow google to reinstall your purchased apps back from market after a data wipe. I say go for a tablet reset.
Then consider a backup before you have a Issue.
Good Luck
Would be helpful to know what problems you've had and in what programs.
Reset to factory dude...
You loose all settings, apps, but at least you come back on a fresh tablet without anything making trouble.
I got a weird problem a week ago after updating the leaked version of ICS my tablet was starting, then after unlock screen, between 1s to 1mn of playing (not game, just using the tablet like usual) the tablet was rebooting...
tried many times... to see what happenned..
so I go fast as flash and reach RESET TO FACTORY
and VOILA... problem solved.
I'm in similar boat with you, I'm on the latest stock, and have some problems. I did a hard reset, as soon as I setup my google account, google push some settings back, even the wifi settings. But nothing really got fixed. I have map crash like crazy, and I got a new problem that the gps logo in info tab at bottom kept blinking, while I had nothing running. Really got tired with all these problems. I thought I didn't install too many apps other than some basic google's apps. Somebody pointed to the Latitude for the gps logo, but I didn't have that on at all, not logged in. I found enter/exit navigation sometime will help.
Hello,
I noticed this problem a few weeks ago. For some reason, my phone (N9005) has no problems connecting to my home WiFi and a few other ones that I have saved, but when scanning it doesn't show any other WiFis except the ones that I have saved, it's like it isn't even scanning. I tried to delete my home WiFi off of the list and sure enough, when I scanned it was completely gone and the phone couldn't see it. And then I manually added the network and it connected without a problem.
If anyone has any input on why this could be happening, it would be greatly appreciated because it is a huge pain in the ass, especially when you're out and about. Thanks in advance.
This being XDA forum, first question would be is your phone modded?
My wild guess: it could be some software interfering. Why don't try to boot in safe mode, just like windows safe mode, should load minimum programs and if it works then it's one of the programs, if it doesn't then I would wipe cache.
Yeah, forgot to mention that. It's only rooted with De La Vega, everything else is stock. I removed some of the bloat with Titanium Backup, but that's about it. I do remember that stock Messages app started FCing after that so I ended up removing it too, maybe I removed something that messed up the WiFi as well?
Tried the safe mode thing, but it didn't work. Deleting the cache didn't work either.
In that case I would go on a limb and suspect you deleted something you shouldn't. When I was going over the list of programs to stop from booting, for many of them I couldn't find any references, what they are for, so I left them alone. What I would do if I was you, I would reload everything back to stock (I think you can do that without tripping Knox) and then freeze those programs instead of deleting, so you can always unfreeze them if things go south. Also some of the programs I don't use now, I may find useful in the future. IMO the phone is powerful enough and has enough memory and battery power to handle little extra bloatware, no need to go Spartan.
In the last few days my S5 has started just locking up briefly and then rebooting. It doesn't do it from a particular app, only when using the camera, or any other specific symptom I can find. It will even lock up and reboot during a reboot sometimes. It's happened running various unrelated apps that don't have anything (apparent) in common, when running no apps, when closing apps, and when sitting all by its lonesome next to me while I'm doing something else entirely.
When it started I was running Safestrap with AllianceROM 1.1 installed on the boot partition. I wiped and installed AllianceROM 2.0 and it still does it. The only change I can think of that happened anywhere around the time the problem developed is I replaced a broken charging port cover (can't imagine how that would have messed anything up.)
One common symptom that may or may not be helpful: during the short unresponsive time during the crash before it reboots, one or two lines of "static" a few pixels tall running horizontally across the display will often (but not always) appear. It's happened when using the phone, when not using the phone, and during reboot from a previous crash. It's crashed while rebooting prior to the Safestrap screen displaying. It crashes and reboots with and without the SD card installed.
At this point I'm thinking the phone is just plain broken (still under warranty) and a replacement is in order. So my questions are:
1. Anyone seen this before and know a fix?
2. Is there anything I'm overlooking and should test before pursing warranty replacement?
3. Is there any reason to avoid a replacement unit (ie. would a new phone resist root/safestrap/etc)?
Thanks.
Sounds like you've covered everything but one.
Try returning the phone to stock and see if the problem persist. If it does then phone is ready to be exchanged.
If not, you'll know it is something other than a hardware issue.
c4manceph said:
Sounds like you've covered everything but one.
Try returning the phone to stock and see if the problem persist. If it does then phone is ready to be exchanged.
If not, you'll know it is something other than a hardware issue.
Click to expand...
Click to collapse
Yeah, I suppose I ought to do that just to be sure. But to be absolutely certain that would require Odin'ing back to stock to get rid of the root, Safestrap, and all the trimmings, right?
So I need a nandroid backup of my current image so I can resurrect that if it doesn't work so I have a phone that only annoys me intermittently while I wait for the replacement. While if that does solve the problem I need my Titanium Backup files so I can gradually restore my apps/settings after redoing all the root, Safestrap, and custom ROM work.
Am I missing anything?
This is the method I would use to return to stock:
http://forum.xda-developers.com/showthread.php?t=2784880
Sounds like you've got it covered.
Thanks. That link mentions repartitioning as being optional... under what conditions would it be advantageous? Is it just one of those "if you wanna be absolutely sure" things or are there cases where the partitioning has been changed and needs to be reset?
New symptom: twice now the phone has rebooted into Odin mode with the message "Could not do normal boot, mmc_read failed".
Doesn't look good... at least I've been able to reboot the phone to the OS each time. Once it even did it itself.
Sounds like internal memory failure. Do your best to ODIN back to 100% stock & do a warranty return.
I've been back to stock for a day without any spontaneous reboots.
I figure the next step is to root, install Safestrap, and then flash the AllianceROM and not restore my Titanium backups except those that are absolutely necessary (and taking a nandroid backup before doing any of those). Let it run for a day or two like that, see if the reboots stay gone and then slowly restore the backups a few at a time to see if one of them causes the problem to return.
Thanks for the update, I wondered if you were having any luck.
I'll keep this updated just in case anyone else has the same problem, so they can have a better idea how to resolve it.
Currently I've been running AllianceROM 2 for about 10 straight hours with no misbehavior. From stock I installed towelroot, Safestrap, then flashed the ROM according to instructions. Once that was loaded and the Play store done downloading everything I shut down, backed up via nandroid, and then used Titanium Backup to restore some key apps and data. Actually I restored more than a few, but not close to all. With the backup if the problem returns I have a clean restore point to use for a more conservative approach.
My plan going forward is that if nothing else goes wrong, I'll restore a few more backups as I need the related app, and after a week or so if things don't fall apart I'll go through and delete the entire contents of the Titanium Backup folder and re-backup the apps as they are in a stable state. Whatever was causing the problem seems to have died in the repartition/odin-to-stock/root-and-return-to-custom, or it's lurking in one of the unrestored backups.
Fingers crossed.
Aaaaand just had a spontaneous reboot. Second time it's done it while scrolling the newsfeed in Facebook. (First time was pre-wipe to stock.) It's possible I just didn't have the restored stock version running long enough since this took over a day to happen.
So I'm restoring the backup and not restoring any of the Titanium Backup stuff. If it still reboots on its own after this, I'm considering it hardware and pursuing a replacement.
There's been another spontaneous reboot. At this point I'm pretty comfortable calling it a hardware failure. I believe the absence of reboots while the phone was Odin'd back to stock was a fluke and, had I given it enough time, I'd have seen a spontaneous reboot there as well. I'm going to forego testing this theory to expedite a resolution to the problem.
So my next step is to call Verizon and start the ball rolling on a warranty replacement. I'll Odin the phone back to stock just before turning it in, until then I'll let it run (as much as it does) the way it is.
The warranty replacement was easy. Went over the steps I'd taken (leaving out all the bits about root, custom Roms, and so on since it's none of their business) after spending about a half hour on hold between the initial customer support person and the actual phone tech guy. He kept saying, as I was telling him what I'd done, "yeah, that's what I was going to recommend next". Set me up for a replacement, next day air, and that's what I'm running now.
Wiped the old phone back to stock via Odin, set up the new one and restored every backup I wanted from Titanium backup. So far, no problems.
It's kinda neat how they send the replacement phones. No back cover, no battery, nada. You take all the stuff out/off of your old phone, use it to finish up the new one, and you're done. Put the old one back in the package, slap the return label over the previous label, and send it on its way. (Be sure to go to a FedEx store or something where you can get a receipt and so on to PROVE you sent it in case it gets lost, or you're paying for a new phone.)
It's clearly not a new new phone, it's a refurb, but aside from some minor scratches on the screen that a screen protector would make invisible, it's essentially new.
Still no sign of a spontaneous reboot, looks like this is fixed.