[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Hrm. I think there might be a language barrier here... I'll do my best to answer what I believe are questions.

I apologize in advance for anyone reading this post, it's quite long and rambling.

First, there is no "SenseUI.apk" attached with any (current) XDAndroid build (not really mine, but thanks.) There's an old rosie build, but it's Eclair (2.1).

I don't know why you deleted other files, the issue certainly sounds like a bad data.img - which you proved by deleting it and it works.

Now why did this remove all the stuff you installed/setup? Well that's a simple answer - the data.img holds all of that stuff. That's the /data section of Android, which is where pretty much every single user-changed stuff goes. That's where all your personal info goes like call logs, text messages, etc. Other stuff like installed apps, any customization to any apps, etc etc. The list goes on.

So what can you do? There's many methods. The main theory is not umounting this partition is causing corruption. So if you run one of Starfox's kernels you can try to use a ext4 data.img (data.ext4 is what he calls it). This is experimental, and not really "supported" if you will. So this you would have to do on your own. That's the most drastic "fix" for the issue. The next potential solution is fix_permissions.sh, which doesn't always fix a broken data.img. This is a CyanogenMod script, and again not a "supported" fix - so you're on your own again ;). The last "solution" is about the only supported fix - and you've already done it. Delete data.img. Now you say, but what about all my data? Well, back it up. I like Titanium Backup - use what works best for you. I liked this app so much, I bought it. You can use it for free, but it is limited (mainly on restoring).

The fact that it happens at all is frustrating, but deleting your data.img has been an unavoidable bear for a very long time. You can run dedicated partitions as some of the "other builds" you use have, and perhaps that will help with the corruption? I doubt it. So long as the issue of not properly umounting the partition exists, potential corruption is always there. Hence the reason for suggesting a journaled FS.

Perhaps the main reason that I hardly ever experience the need to reset my data.img is I hardly never reboot to WinMo. I'm pretty much always in Android, day in & day out. So my data.img doesn't get corrupt very often... Perhaps that's why, I can't know for sure. I also don't install many apps, I have the ones I like/use and don't really go looking for new ones all the time. Again, not sure if this contributes to the data.img not becoming corrupted so easily or not... Just my speculation.

As for netloc, that works great for me on CDMA. Are you GSM? The tech is significantly different (especially with netloc) so it does make a difference. Both work, heck the guy that wrote a lot of that stuff is on GSM... But as he described it to me, GSM actually has to triangulate and CDMA towers just send their location data, so netloc evidently works "better" on CDMA in this sense.

If it's not working at all, the only thing I can say is provide logs of it failing. I might spot something awry, or more likely someone else will look at the logs and point to the failure. Again, both CDMA and GSM works for netloc on this build and has for quite a while.

GPS is a whole nother bag of worms - first, we don't have a lot of the advanced features in Android (warm injection, etc), there's a thread on this topic use search. So it takes a LONG time to get a lock. If you use QuickGPS in WinMo before booting Android, it seems to help getting a GPS lock in Android immensely. But either way, GPS in Android will take some patience. As always, make sure you have a clear view of the sky - even if you're outside, big buildings can cause issues with getting a fix.