View attachment 169927So here is what happened. I wanted to upgrade to el capitan and clover, so I made a boot drive, backed up on an external time machine my chimera yosemite and started clean. In the fresh install the only problem I encountered was another boot loop, which was fixed by installing the correct nvidia drivers. Then, I transfer all of my data with migration assistant, and I am in a boot loop again. I've tried everything that I have found on these forums and got nothing. However, after reading the "big list of el capitan install problems" I think I might have figured it out. After transfering ALL of my data, the kexts and old multibeast from chimera yosemite are now on the ssd. In the big list, it says that one cause to my problem is having old kexts, specifically evoreboot.kxt and codeccommander.kxt. I know I had evoreboot in yosemite. The problem is that I don't know how I can get rid of it when I can't boot. To be sure this is the problem, attached is where the verbose boot code ends before rebooting.
So here is what happened. I wanted to upgrade to el capitan and clover, so I made a boot drive, backed up on an external time machine my chimera yosemite and started clean. In the fresh install the only problem I encountered was another boot loop, which was fixed by installing the correct nvidia drivers. Then, I transfer all of my data with migration assistant, and I am in a boot loop again. I've tried everything that I have found on these forums and got nothing. However, after reading the "big list of el capitan install problems" I think I might have figured it out. After transfering ALL of my data, the kexts and old multibeast from chimera yosemite are now on the ssd. In the big list, it says that one cause to my problem is having old kexts, specifically evoreboot.kxt and codeccommander.kxt. I know I had evoreboot in yosemite. The problem is that I don't know how I can get rid of it when I can't boot. To be sure this is the problem, attached is where the verbose boot code ends before rebooting.
