2014-04-06, 00:19
Sounds like filesystem corruption and possibly bugs in the filesystem code triggering a kernel panic when reading the corrupt filesystem on subsequent boots... Have you tried ext4 instead of f2fs ?
As you read in another thread I was experiencing corruption of guisettings.xml when doing a hard reset with f2fs, I'm yet to reproduce that with ext4...
As you read in another thread I was experiencing corruption of guisettings.xml when doing a hard reset with f2fs, I'm yet to reproduce that with ext4...