I wanted to point out I have 3 of the same machines. After successfully installing on one if them (fully working minus a SD card reader), I wanted to speed up the process. So I built an installer on a USB 3.0 drive. The machine would panic, and garble the text, but I was able to make out that it was a USB related crash. I tried a different manufacture USB 3.0 drive with the same issue. These drives work perfectly on the installed machine, but I did use a USB 2.0 drive for that one. Using the USB 2.0 drive didn't crash booting the installer. I tried a USB extension cable to force the USB 3.0 drive to work as a 2.0, and that didn't crash either. This may be a bug with the XHCI-unsupported kext, or something I did mapping the USB ports. However, again the live system has no problem using the USB 3.0 drive, just booting the installer from them. (I just change the SMbios info in the same EFI for the other machines)

I wanted to recommend to add to the guide that if using a USB 3.0 drive, to force it to USB 2.0, or use a USB 2.0 drive to possibly improve the chance of booting the installer, if getting a panic while booting related to USB.

I do understand that this is not the real solution, but it is a minor problem, with an easily bypassed solution. The real solution is something that will not be possible for myself to troubleshoot, based on my available time and knowledge. Plus it is only a problem for the install, and not use. I just wanted to share a solution, that I know has stumped me in the past. I know I have had trouble in the past trying to do a clean install, with my current EFI on the same hardware, experiencing this issue. I just chalked it up to using a different USB drive, not its USB generation.