I have the same thing with 4.4.4, no reboots, fast and stable. And everything works. I'm not doubting that his build doesn't run smooth. But there's quite a few items not related to smoothness that doesn't work/bugged. I don't mind waiting a bit for the worst bugs to get cleared out. CM11 is rock solid, so i'm ok with that for while more.
Try to hold power during more than 10 seconds. It should either reboot or shutdown.
Then hold volume down during the reboot (or power on) and you should get into bootloader. From there you'll be able to flash a recovery (fastboot flash recvovery <filename>).
Don't panic if it doesn't work the fist time, I often need to try 2 or 3 times as the volume down button is kind of bad.
First hold volume up, then (with volume up held down) press power button to enter the main recovery menu. This keys combination may vary from device to device. Try different keys combination if the above one doesn't work (might be all three keys all together too)
I believe this is the stock recovery.
See step 10 of method 2 from this post: http://android-revolution-hd.blogspot.fr/2013/12/how-to-manually-install-ota-update.html
That's the second time someone has reported this.
Try cleaning the plug and blowing out the port
For those having headset/headphone mic not working try the following:I'm having the SAME problem. I'm on a nightly release; 11-20150105. However, it does *sometimes* work as normal, but the fix for it now is to unplug and plug back in a couple or more times and then it finally kicks in. What I've noticed is that the volume in the headphones is also a little lower when the microphone isn't working.
Could a different radio or kernel help? I'm currently on 1.15.50.05.29_10.30.50.08U. Kernel is 3.4.82-g0129413. It's really unfortunate because I use a single in-ear headphone and mic when in the car ('hands free'), so this gets used a LOT as I do 160km every day. Other than that, the ROM is absolutely flawless, nothing else seems to be faulty, no random reboots, nothing. It's basically 99.7% complete.
Not sure I said that exactly, but I think that support for our device is definitely a low priority since our maintainer was hired by CM and likely spends most of his time on tasks that bring in revenue. As it stands now, it doesn't seem we will ever get a stable release, so will be stuck here in xda purgatory complaining back and forth about the same things until we can afford to get a pure AOSP device and give up the crack flashing life.