[rushco]

Wirelessly posted (Opera/9.5 (Microsoft Windows; PPC; Opera Mobi/17992; U; en))

Originally Posted by MultiMatt

Hey guys,
I have been playing with this on my TP2 for over a week now, and following the thread all the way through. I have been taking notes on the differences between Android and WM so I can do a demo of the dual-boot at a monthly meeting we have here in Louisville, KY.

I have added some apps & widgets, and have set up the device quite nicely. Obviously, there are things still not working, but I was set to go for this Tuesday's meeting (23rd).

I routinely play with the Android portion for a while, then boot back over to WM for my regular use. Hasn't been a problem at all.

Suddenly yesterday, I attempted to boot into Android and noticed it was taking an excessively long time. I did a soft-reset and tried again. Seems the boot is getting stuck in an endless loop at the part where the colorful X is animated. It will freeze up for a moment on the X, then will do that "double-vibrate thing again" and begin animating the X again. Never gets beyond that.

Aside from cosmetic tweaks I have been doing for demo purposes, such as adding widgets to the home screen, saving some bookmarks in Opera Mini, etc, I have not done anything different, but I'm stuck in this loop.

Tried some of the latest zImage and modules files, but the result is still the same. I REALLY don't want to start from scratch on my card again - I've done a lot of work to prepare for my Tuesday meeting. Aside from the zImage and Modules files, is there something else I can try overwriting to get past this endless loop at startup?

Thanks, and sorry for being lengthy...

Maybe try a new startup.txt or post it here so we can look at it. Not sure if that could be the reason.