try renaming the boothbl.3dsx to something with 4 letters (and change the payload to whatever you choose to name it). That might work.
Aaah damn I didnt realise how much it was restricted. I wonder if it would be possible to add support for .xml and game selection, that would be awesome.This will not work with any homebrew that uses a .xml file and asks you to select a game before booting (such as svdt or hans.)
Honestly don't see the point in it since so much homebrew only really works if you run them from hbl, and it's only going to clutter your home menu even more. Not to mention the root of your sd card becoming cluttered with 4-letter long .3dsx files, you would get lost in it after a while.
Just keep one icon for homebrew launcher and then every .3dsx homebrew as their own icon in HBL.
damn :L try wading through the pages of the hblauncher thread for a solution because thats how I found my information. Good luck :LTried it too, still got the same issue.
Still, thanks for the help. ^^
OHWIAT I think I may know what is wrong. Did you choose the firmware of your sysnand or emunand when getting the payload because it needs to be that of your emunand.Tried it too, still got the same issue.
Still, thanks for the help. ^^
Aaah damn I didnt realise how much it was restricted. I wonder if it would be possible to add support for .xml and game selection, that would be awesome.
I thought it would be cool for people's homebrew games because it would kinda seem like their games where more legit since legit and homebrew games are separated. Also if it had support for everything then it would completely remove everyone asking for developers to release their homebrew as a .cia
--------------------- MERGED ---------------------------
damn :L try wading through the pages of the hblauncher thread for a solution because thats how I found my information. Good luck :L
--------------------- MERGED ---------------------------
OHWIAT I think I may know what is wrong. Did you choose the firmware of your sysnand or emunand when getting the payload because it needs to be that of your emunand.
Wait is your emunand not on the latest firmware?Yes I made sure I chose the right one NEW9.2.0.20E.
Wait is your emunand not on the latest firmware?
oh... Yeah in that case I still have no idea what is wrong xDNo, on n3DS we can only go up to 9.5, and I don't really have the use of 9.5, 9.9 could have been usefull tho. ^^
sorry just to make sure,root of sd card
sorry just to make sure,
i don't need to rename the otherapp payload .bin right?
i downloaded the .bin manually it's named POST5_U_23552_usa_9221.bin
i still don't need to rename it to hblauncherloader_otherapp_payload_OLD-10-3-0-28-USA.bin ?
i have o3ds usa
No Problem! Happy to helpThis has all actually saved me.
It depends on your use in the end. For me this means editing only one and then everything works more directly "out of the box" so to speak. I'm using CTRBootManager with MenuHax and if you're not doing that then you don't want to go that way around perhaps. This way around though my system boots the unusual file that I won't update terribly often by default and all the homebrew stuff that may just get frequent updates I can just extract straight to the card.The reason I chose not to edit the payload for menuhax is because it requires to change two 'boot.3dsx' instead of one xD
Try this maybe?No, on n3DS we can only go up to 9.5, and I don't really have the use of 9.5, 9.9 could have been usefull tho. ^^