Originally Posted by kjwaugh
I was on March 06 nightly build and did the usual - flashed M4 over what was there with just clearing the Dalvik and it just kept circling occasionally showing the lock screen for a brief second - then back to the CM logo. I flashed the March 08 Nightly and all is good. I wonder if it is better to do a clean install with the M releases...
I had the same issue. I also got an error dialog (which I cannot recall now, but mentioned something about a core Android process having stopped, and that's when it went back to the boot animation). I re-flashed the M4 snapshot and this time I also flashed the latest PA GApps, and I thought this had done the trick, because the "Android is Upgrading" dialog appeared and my apps seemed to be updating. But after that process completed, the bootloop began again. I flashed the 03/08 nightly and it appeared to boot correctly, but this time some of my home screens went missing (by missing, I mean "went away"). I had one screen with just the DashClock widget - it disappeared. One screen had not only a near-full-screen widget but also shortcuts for Fox Sports GO and Chrome - it went away. The screen with my Wunderground Map - disappeared. Also, the widgets on the pages that remained disappeared as well.
Methinks after I rebuild my homescreens I will probably flash the 03/09 nightly and stay away from the M4 snapshot. When the M5 comes out, then I may once again be adventurous.
BTW, the M4 snapshot works fine on my HTC Vivid (albeit it's an "unofficial" build) and on my Samsung Captivate (which does not have the PA GApps). So could it be a device issue?
HTC Vivid (albinoman887's CM 11 KitKat 4.4.2)
AT&T Captivate (backup - CyanogenMod CM 11 KitKat 4.4.2, but might go back to stock)
Asus Transformer TF300T (Cyanogenmod CM11 KitKat 4.4.2)
And an HP G62 laptop dual-booting Windows 7 and Ubuntu 13.10