Here's what happens when Devolution loads a game, by my understanding (simplified more than Rydian's diagram, seeing as you apparently couldn't cope with it):
Thanks for the personal attack. While I may think that the person who wrote Devolution is a good programmer, I have very little respect for the way he and those who support him treat others. Nor do I think that most of the people who have attacked me have been helpful, although some have at least made a civil attempt to clarify the situation. Far too many here have been very mean-spirited and not anywhere close to respectful. In the future, I plan to report all such posts.
The above may be correct. I cannot corroborate that fact. There is one person who could explain the exact sequence of events and provide evidence showing this to be the case, but this individual has been unwilling to provide the necessary evidence. Rather, I have been belittled and told to look at logs which I cannot produce because I lack the necessary hardware.Select game -> Run apploader from game -> Check for DVV -> (if DVV doesn't exist, verify game and create DVV) -> load game
The bit in red is where IOS crashes (or rather, did crash, seeing as it is now fixed). Nothing after that happens at all. Part of the code that is on the original disc causes the IOS in use to crash. Therefore, the whole program crashes. It does NOT fail verification, because it does not get to that point.
EDIT: And running the apploader is NOT part of the AP process. It has to be done regardless, to load the game (it happens every time you load the disc via the disc channel or on a GC as well). So it crashing has nothing to do with AP.