If you're only interested in ARM9 payloads, the only service that needs to be initialized is gfxInitDefault(), this is according CakeBrah: https://github.com/mid-kid/CakeBrah/blob/master/source/main. Note that you should call gfxExit() only after brahma_exit(), though.
Not required... the BrahmaLoader project also loads from disc without initializing that service and it works fine. Same with CakeBrah. Also, the source code checks if the file is properly loaded into memory before even continuing.
There's still the remote possibility that something doesn't work with your rxTools installation. You can load it via other means, correct? If so, you may try fix5. That one does everything the same as rxTools own loader, save for the bootfix (but that should not be a problem).
Thanks a ton! Well, who wouldn't have thought thsi would require so many tries. Removing the previous versions now. Fix5 has the (minor) disadvantage that it won't display any error messages, so be extra careful to actually put the correct paths into the XML <arg> tag.Yes, i can load it auto through menuhax and mset, will try fix5 now and report back
--------------------- MERGED ---------------------------
@d0k3
Fix 5 works 100% no error message, no garble on bottom screen, rxTools splash screen and then emuNAND
Well done you did it !!!
I am officially a tester too
So, fix 2 has the best boot rate (up till fix4)... What does "without pb" mean? And, how do these boot rates compare to what you get in either CTR Boot Manager or BootCTR (if you know)?
Okay, thanks both of you! In fact, I have a rather bad boot rate for Decrypt9 from CTR Boot Manager at times, so it seems to be different based on what payload you are loading, too :/. I'll see that I can make it work more like CTR Boot Manager does and post later. For now, I'll just put fix2 back up, just in case it helps someone.
Good start already. It is still possible that no better boot rate is possible when HB Launcher is already loaded. I'll need to try and see. It would be a lot better if someone could finally find out what made Brahma 1 so stable and why Brahma 2 doesn't boot at times.
I know this is offtopic but where can I find that glorious theme?It will may be usefull in some case... like decrypt9:
You can have error messages even when booting rxTools. You just need to call gfxInitDefault() without calling consoleInit(). When you need to actually print an error message, call consoleInit() before calling printf() and this should work.
Did you try calling this piece of code?
// call this right after initializing services, you may need to call aptInit() for it to work
// offset potential issues caused by homebrew that just ran
aptOpenSession();
APT_SetAppCpuTimeLimit(NULL, 0);
aptCloseSession();
