I've noticed between the different CFW/Entrypoints you can get really mixed results when coming to boot your emunand/CFW enviroment.
Palantine-PBT days bootrates through mset used to be around ~30%
mset-rxtools (either 2.6 or 3.0b) around ~90%
menuhax-rxtools 3.0b around ~80%
But recent cakes (first half of may) seems to be around ~45-50%
Haven't tried AuReiNand/Luma yet to confirm it's bootrate on my systems
I know for a fact A9LH enables a full 98-100% bootrate provided you have no menuhax leftovers and it's overall the maximum entrypoint of preference at this point in the cfw 3ds life.
What i want to know is more-or-less what does this entrypoints/cfw combinations rely on to give such bootrates.
I don't know if the term to be used is still ROP chains on how the exploit is executed into the payload, then the CFW.
Palantine-PBT days bootrates through mset used to be around ~30%
mset-rxtools (either 2.6 or 3.0b) around ~90%
menuhax-rxtools 3.0b around ~80%
But recent cakes (first half of may) seems to be around ~45-50%
Haven't tried AuReiNand/Luma yet to confirm it's bootrate on my systems
I know for a fact A9LH enables a full 98-100% bootrate provided you have no menuhax leftovers and it's overall the maximum entrypoint of preference at this point in the cfw 3ds life.
What i want to know is more-or-less what does this entrypoints/cfw combinations rely on to give such bootrates.
I don't know if the term to be used is still ROP chains on how the exploit is executed into the payload, then the CFW.