Originally Posted by vertcam9
no, the issue is more complicated than that.
Here's a scenario, for example i'm using it still @ 60% battery, then suddenly it will shut-off, when i try to re-start it it won't boot properly, it get stuck in the cyanogen logo, it seems some file gets corrupted, the only for it to work again is to reflash. (which im getting tired off
There was a user a while back that ended up with the eMMC bug and had to repartition his device to skip over the bad blocks. In doing so, he didn't allocate enough space for a proper cache partition (something like 150MB, I believe) and his device would do the exact same thing.
I would suggest clearing your cache and see if that helps. You may have to do a true wipe though, because I don't think a wipe in custom recovery will cut it.
You might want to check the cache, system, and boot partitions for bad blocks while you're at it.