Any idea why my phone suddenly crashed?

[two250]

Running Vicious 4.1.1...

So Saturday morning the signal on my phone was "grayed out", so I toggled airplane mode to bring it back, nothing happened. So I decided to reboot, the phone never came back. First it sat on the google logo, so I tried re-flashing my ROM, same thing. Then I tried wiping a flashing, still nothing. So I wiped and flashed a ICS ROM, now I got to the boot animation but still wouldn't boot. Tried a restore with the same result. I was forced to unroot, lock, and restore my phone to stock 4.0.2 to get it working. Why would this happen? I am going to re-root today but I would like to avoid this...

[Ads]

[bkdodger]

How long did you wait on the Google screen? cache and dalvik should've done the trick...re flashing the ROM as you did was good idea...how long did you wait it out? Also what recovery you used and did you change anything before it happened?

[two250]

How long did you wait on the Google screen? cache and dalvik should've done the trick...re flashing the ROM as you did was good idea...how long did you wait it out? Also what recovery you used and did you change anything before it happened?

About 5 minutes, usually passes it in less than 30 seconds. All I did was a reboot to try and get rid of my "grayed out" signal. After re-flashing the ROM (did not wipe yet) I waited about 10 minutes, never got passed google. Wiped cache and Dalvik, sat there for about 5 minutes again. Then when I did a full wipe and installed my old ICS ROM it bootlooped; google->bootani->google->bootani...

[bkdodger]

Sounds like you did the right thing...Interesting as I was just reading a post on Rootz in AOKP thread..
Quote below:

Hey guys. I just want to tackle this before this thread explodes. About the sometimes long boot times on JB? It's a feature, not a bug.

Abqnm can back me up on this since I believe he was the one who noticed it first, but JB now has a filesystem check built in to the boot sequence. Much like Windows' "check disk" feature, if JB detects a dirty or odd shutdown it will run a integrity check on the filesystem before proceeding on to boot. It will check everything, data, system, and media (your SD card), for issues and attempt to correct them.

When this is happening all you see is the Google logo. It will sit there for as long as the check takes to complete. The more stuff you have, the longer it will take. When dirty flashing, boot times over 5 minutes have been reported for those with a lot of apps or a lot of system errors.

Please note that this is a common, but somewhat sporadic incident due to the way we have used our phones up to this point. Other than an on-mount SD card check Android has never fixed filesystem errors before, so it may be fixing a ton of them you never knew you had. Also, most apps that include a shutdown or reboot feature from within the app (looking at you ROM Manager) don't do a "graceful shutdown" sequence and just simply kill processes and then shutdown or reboot the phone. This is one of the flags that JB is now checking the system after detecting, so to reduce the cases of longer boot times try to always use the phone's native shutdown option. (If you happen to be running a mod that adds in the reboot feature to the power menu this is usually a graceful reboot which is OK to use). Since JB, apps will now have an API to use for graceful shutdowns and reboots, so apps eventually will be OK to use this way once they incorporate it.

[two250]

Maybe it could have been that but what's strange is I couldn't get any old ROMs or backups to work. They just bootlooped, maybe it's because I interrupted that process...

[bkdodger]

Strange indeed...I've read post on people having different kind of issues with backups and restores....Also are you on regular Clockwork?

[Nemo Aeternamn]

Thanks for sharing bk.... I knew it was checking for systems.. didn't know it was correcting them...Haha.. I guess if u wanna avoid long boot times I should probably stop pulling the battery like it's going out of style :P

Cellar Door


“Who are you people and where is my horse"

[two250]

Strange indeed...I've read post on people having different kind of issues with backups and restores....Also are you on regular Clockwork?

Clockwork Touch, but now I just installed TWRP instead. So much work to do now that I lost 100+ apps...

Thanks for sharing bk.... I knew it was checking for systems.. didn't know it was correcting them...Haha.. I guess if u wanna avoid long boot times I should probably stop pulling the battery like it's going out of style :P

Cellar Door


“Who are you people and where is my horse"

Thing is I never pull my batt, it was just a regular power off...

[bkdodger]

Man sorry to hear it on the apps bro...I've also just powered off a few times and got the long boot up on Google... unfortunately it didn't come back for you and no explanation on why makes it worst...TWRP has some good reviews ...

[Mujibar]

Sorry to hear about the app loss. TWRP has been running well for me. Lots of great features that CWM doesn't have. Hope it works for you.

You may have already mentioned this (and sorry if I missed it), but have you flashed the JB bootloader?

~ GNexified ~