Separate names with a comma.
Discussion in '3DS - Homebrew Development and Emulators' started by zezzo, Jan 24, 2016.
Can't find it...
why remove them that's what makes it cool
You put your firmware in and click download ropbin. It doesn't go up to 10.4 though, only 10.3.
Unless that is the wrong thing and it's just this part you need to do
Blank image display at boot
If you want to hide the image display so it won't display junk or "the menuhax loader", you want to place this imagedisplay.png at /3ds/menuhax_manager and then configure image display within menuhax_manager.
Seriously, how this I missed this all this time?
Anyways, are these ropbin updated for 10.4? No payload version?
I heard that these might lower the success rate for CFW coldboot, is that true? If so, how?
I have no idea of why it happens but success rate is definitely lower on my o3ds. Specially when it's rebootting from settings or from smash (it crashes almost 100% of the time)
is there a way to modify my existing payload which has an awesome boot rate to be free of Debug / Colors?
the point is that modifying the payload is what seems to be affecting the boot rate.
Also doesnt help you CANT TELL if your 3DS is booting because there is no flashing colours lol
You can tell if it hangs for more than five seconds and it looks more 'clean'.
Removing the code that displays the words or colors will not impact boot rate - I have a modified payload already that has a close to 90% Boot Rate - and just want to see if I can modify it
Removing chunks of code in a payload that requires precise timing to run properly - and even when finetuned it still has a slim chance of crashing - is always going to impact boot rate in one way or the other. Things like these are extremely finicky - sometimes even the smallest change will prevent them from booting at all.