The 6 most common reasons why Pine64 won't boot

[pcfr33k]

RemixOS for Win32DiskImager (32GB):
http://files.pine64.org/os/remix/remix-v...4-32GB.zip

Android for Win32DiskImager (32GB):
http://files.pine64.org/os/android/andro...4-32GB.zip

Android for Win32DiskImager (32GB, ROOTED):
http://files.pine64.org/os/android/andro...4-32GB.zip

Android for Win32DiskImager (LCD Touchscreen version, 32GB):
http://files.pine64.org/os/android/andro...4-32GB.zip

Android for Win32DiskImager: (LCD Touchscreen version, 32GB, ROOTED):
http://files.pine64.org/os/android/andro...4-32GB.zip

I just don't know why but the RemixOS is not booting and the processor gets too HOT!! If I left it in that state I bet it would burn!!

The only ones that boot so far is  Debian Linux Jessie that is it!!

Something must be happening to the bootloader  or kernel during the burn process to my Scandisk Extreme Pro 32Gb.  That MicroSD works perfectly on all my other devices, Raspberry Pi 3, Pi2, DragonBoard and LinkSPrite PCDuino. I also checked the SD card with the H2testw no problems.

Has anyone tested these 32Gb releases burning with WinDiskManager and to see if Pin64 2GB version boots?  Why would the processor continue to get warmer and even hot when its not booting up correctly?

pcfr33k -   I may have missed it, but have you tried the dedicated PhoenixCard Image burned via PhoenixCard?

Yes,

I have tried Phoenix Card, Win32DiskImager and the dd command in OSX terminal.  Not one single image boots and the CPU gets extremely hot when I continue to wait.  The only one that boots is Debian Jessie. Luke told me after trying many other things such as power supplies etc that it could be a bad CPU or something else hardware wise is bad.  Debian Jessie only runs at half the CPU speed so maybe that is why that image boots, while all the other images require the full CPU speed.  At this point it no longer matters, they are sending me a pine64 2gb plus version replacement