I think I've noticed a pattern... because this has definitely happened to me before.
I just ran into an apparently common issue of El Capitan spamming the user with notifications about some USB device drawing too much power (even when no USB devices are plugged in), so I tried doing a PRAM reset, as it was said that that fixes it.
Well, it now refuses to boot after I did the PRAM reset. Every time I turn it on, it continues to do the extra loud bong (which is done once the PRAM has been reset), but never gets anywhere. I currently have a non-flashed GTX 660 in here, but since this has happened to me before (with GPUs that support boot screens), I'm fairly sure it's stuck on the Apple logo and "progress" bar.
Note that this system is obviously using pike's custom Boot.EFI - could a PRAM reset have reversed the patch somehow?
I'll come back tomorrow (my God... it's 2:24 in the morning) with an update, since I'm planning on re-patching and seeing what happens. If I find that the PRAM reset did it, I may regard it with caution; however, I - of course - would not be able to speak for the thousands of other El Cap 1,1/2,1 machines out there.
I just ran into an apparently common issue of El Capitan spamming the user with notifications about some USB device drawing too much power (even when no USB devices are plugged in), so I tried doing a PRAM reset, as it was said that that fixes it.
Well, it now refuses to boot after I did the PRAM reset. Every time I turn it on, it continues to do the extra loud bong (which is done once the PRAM has been reset), but never gets anywhere. I currently have a non-flashed GTX 660 in here, but since this has happened to me before (with GPUs that support boot screens), I'm fairly sure it's stuck on the Apple logo and "progress" bar.
Note that this system is obviously using pike's custom Boot.EFI - could a PRAM reset have reversed the patch somehow?
I'll come back tomorrow (my God... it's 2:24 in the morning) with an update, since I'm planning on re-patching and seeing what happens. If I find that the PRAM reset did it, I may regard it with caution; however, I - of course - would not be able to speak for the thousands of other El Cap 1,1/2,1 machines out there.