Quote (killg0re @ 28 Oct 2014 00:23)
What happened?
It bricked. If you attempt to access the apps menu by pressing the menu/list button from the home page, the phone then corrupts an ext4 partition file in the partition folder. Though this file isn't used by Cyanogenmod, the ROM does check it on boot. The file corrupts over time starting with random freezing, then restarting, then finally a soft brick. The boot cycle doesn't have error checking on this file/partition and eventually causes infinite boot iterations.
AKA: Infinite boot loop!! Yeah!!
Once you figure out how to actually fix the shit, it's easy. Load into Fast Boot, download the Android SDK and Fast Boot whatever program, do some other stuff, and essentially copy a fresh image of the file to the partition. One that isn't corrupted.
Very annoying and confusing when you don't know what the fuck is going on. Haha this is a known and common bug. OPO should have done WAY more testing. So instead of unfucking the OPO, they are moving onto the OPT. (ONE PLUS TWO)
I doubt they will completely ignore the first gen though. Then again, they might and just might run the company into the ground to get rich fast.