System corrupt after power loss
 

My phone wasn't charged for 8 hours when in XDAndroid. When the battery became low, the phone rebooted itself into Windows Mobile and gave the low battery sound before shutting itself off again. I do not know how it exited XDAndroid, whether it was graceful or not, but after charging and booting into XDAndroid, all of my installed apps and nearly all of my customizations are missing. My guess is that XDAndroid did not exit gracefully and the file system (data.img) was corrupted. So, I have a few questions for those who may have been through this before:

1) Is there a way to restore the system to it's original state before the problem? I have a Titanium Backup from a few days ago that I can use, but would like to salvage the file system if possible, since I don't think Ti BU restores certain things like desktop folders and widgets. I also had a resized data.img file to 512MB.

2) Is there a way to determine what happened and what went wrong? Since the phone rebooted into WinMo instead of shutting down completely, it makes me think that XDAndroid did exit gracefully, so why did the file system become corrupt?

3) Is there a way to prevent this from happening in the future? Can we force XDAndroid to shutdown gracefully when the battery reaches a certain level, or is the battery reading too inaccurate? I was testing XDAndroid to put on someone else's phone that isn't technically capable of troubleshooting a problem like this, so is there a way to make XDAndroid more robust?

Thanks for any feedback you guys can give.

Re: System corrupt after power loss
 

1. Do you have the original data.img...?

2. /data/system/dropbox. Look for the SYSTEM_LAST_KMSG files. These are basically kernel messages, and really the only record from a reboot.

3. Keep the battery charged? Not sure what you want here. I've honestly never experienced what you described. I have a feeling it was a coincidence that it rebooted - because every time my battery has outright died, I just check the phone and it's dead. No reboot to WinMo, just unresponsive.