[Q] Weird unprovoked Jellybean Samsung logo brick question
A few days ago I upgraded my Note from a very ancient (stock) Gingerbread ROM to (stock) Jellybean. I hadn't been getting OTA updates because the Gingerbread was originally German rather than UK, so quite a long time had passed without any updates. Anyway, because of the no OTA, I used Odin. Everything went fine and I had a nice few days of usage, although the battery consumption seemed to suddenly be quite high, mainly due to additional wakelocks from the new Google Search it looked like. The night before last at about 3% the phone turned itself off, which is unusual as normally the battery will run itself lower than that. BTW, it's an official battery bought just a few months ago to replace the one before, which was getting old.
Yesterday evening when I went to use the phone it was dead. Completely unresponsive. It wouldn't charge either. (The battery had been at about fourteen percent I think, so it should have still had a lot of juice left.) Turning it on would leave it stuck on the Samsung logo only. Recovery mode didn't work, but I could get download mode up, so I installed the Philz kernel as people have said, and then did a reset using that, and all was okay again and after reflashing the ROM I could use the phone again, although because of the reset I had to set everything up again.
Just wondering what people think caused it. Just a weird coincidence, or something else? As far as I'm concerned, the problem has been sort of mitigated for now, but definitely not fixed, because what's to stop it happening again? Has anyone heard of strange things going on with Jellybean? I know there's an issue with flashing/resetting from ICS, but I never used that so I don't think that's an issue, and it looks like it was just a soft brick only. Still, a bit weird and worrying. Does anyone have any ideas?