Incidentally, the reason a factory reset helps after a botched update is that it redistributes the information evenly. As you use your device, you inevitably create pockets of a higher density of information. If you do a system update at this stage, you may exceed the critical information density and - bang!
I had similar issue after upgrading to 2.0.3.14 - one of the patches was the culprit - I think the ultimate statusbar. After disabling it through SSH, it started loading.
The strangest thing was that it only happened on the tablet, so I didn't report it as I thought the problem was with mine only.
I think I can almost safely say that since the second my phone was updated to 2.0.4, the battery drain of 2.0.2 ended. Battery usage during 8-10 hours of sleep is now 4-5% with Wi-Fi on, 12 open applications and Android support running and 1-2% with Wi-Fi off, where it was 15-30% with 2.0.2. Nothing else changed, so it seems to be fixed.
Is there a way to make a backup of the whole system with rsync?
Yes, of course. You only need to run it as root OFC. And you probably don't want to backup /sys, /proc and such...
I recommend you mount your mmcblk0p28 to some other directory and then rsync that. Much neater than trying to rsync live root.
Note that to restore that is not so trivial; I'd imagine you cannot rsync back your rootfs when running the said system
I however have found it necessaty to rsync only /home/nemo since everything else can be recovered from images and the apps are easy to re-download from the store.
