Hacking [Question] How to access Homebrew while on emuNAND?

  • Thread starter Thread starter andzalot55
  • Start date Start date
  • Views Views 7,568
  • Replies Replies 56
I'm sure it's super simple, but I lack the tools/know-how to do it. I've submitted a request in the HB development thread, so hopefully this will solve our problem: https://gbatemp.net/threads/homebrew-development.360646/page-215#post-5902860

EDIT: Oh wait a second, this is way easier than I thought. Just hex-edit the string that says "boot.3dsx" hex editor to change the filename the payload attempts to load.

EDIT2: I've added a modified payload for OP. Replace your payload with this and rename your homebrew channel boot.3dsx to "boo2.3dsx": https://mega.nz/#!uAshlSzb!8si7tNOFnQwESgCLL_uYALfqXROptzbPtnLDgr4hZhw
exactly XD
 
Nvm I turned on my internet on my 2DS to get it loading but it just went back to ctrbootmanager 'cause I have menuhax installed. What do I do?
Of course, because the cia loader does nothing more than reboot the console and start boot.3dsx which is your ctrbootmanager. You need to edit the payload with a hex editor or notepad++ and make it point to whatever your homebrew launcher 3dsx is called, instead of boot.3dsx
 
I think that's separated by filename already actually, because the filename starts with "hblauncher_...". I suspect it's expecting the payload for SysNAND, but EmuNAND is running a different version? What version are your EmuNAND and SysNANDs?

EDIT: You can also try deleting the payload, turning on Wi-Fi, and let the app download the payload by itself. (Hold Y as you're running it so it keeps it on your SD card)

^If this method worked, can you tell us the filename of the payload for future reference? I'm curious why manually downloading it didn't work.

Okay so holding Y to download it works. Thanks but one question, since I renamed my homebrew boot.3dsx to boot_hb.3dsx, is there a way to modify the .cia file to load boot_hb.3dsx file instead of boot.3dsx?
 
Okay so holding Y to download it works. Thanks but one question, since I renamed my homebrew boot.3dsx to boot_hb.3dsx, is there a way to modify the .cia file to load boot_hb.3dsx file instead of boot.3dsx?
It's the payload file that needs to be modified, not the cia. Open it in hexeditor and search boot.3dsx, then replace it with what you want. We've tested it to work with 4-character file names, making it longer might break something (though probably not)
 
It's the payload file that needs to be modified, not the cia. Open it in hexeditor and search boot.3dsx, then replace it with what you want. We've tested it to work with 4-character file names, making it longer might break something (though probably not)

Is it possible for me to upload my payload so someone can modify it or is that consider piracy in anyway?
 
Is it possible for me to upload my payload so someone can modify it or is that consider piracy in anyway?
The payloads themselves are not illegal nor do they contain copyrighted information

Post the file name of yours and I'll make one for you
 
What is your emunand version out of curiosity

edit: right before it crashes to black screen it says home menu ropbin is ready (things go too fast to read, for the most part) so I'm wondering if it isn't loading the ropbin that's necessary for menuhax to load instead of the otherapp payload

edit2: oh snap. the problem is I've been using 9.5.0-22U when I'm 9.5.0-23U :blush:
The last number doesn't matter. Payloads are the same regardless.
 
The last number doesn't matter. Payloads are the same regardless.
The file name is important because that's where it's looking for the payload, otherwise it will download it, which is the problem I was having since I wanted to use the modified payload
 
The file name is important because that's where it's looking for the payload, otherwise it will download it, which is the problem I was having since I wanted to use the modified payload
That's the thing, for the same firmware version the payloads are the same regardless of the last number, down to their file name.
 
That's the thing, for the same firmware version the payloads are the same regardless of the last number, down to their file name.
On a New3DS 9.5.0-23U, hblauncher will look for hblauncher_otherapp_payload_NEW-9-5-0-23-USA.bin
On a New3DS 9.5.0-22U, hblauncher will look for hblauncher_otherapp_payload_NEW-9-5-0-22-USA.bin

The contents of the files might very well be identical (I'll take your word for it), but the file names themselves are NOT the same and need to be named appropriately, otherwise the launcher will not find the file you're trying to use.

I'm speaking from experience here. I just did this and a misnamed payload was preventing me from loading the custom named boot.3dsx that I wanted to load.
 
Last edited by Kohmei,
On a New3DS 9.5.0-23U, hblauncher will look for hblauncher_otherapp_payload_NEW-9-5-0-23-USA.bin
On a New3DS 9.5.0-22U, hblauncher will look for hblauncher_otherapp_payload_NEW-9-5-0-22-USA.bin

The contents of the files might very well be identical (I'll take your word for it), but the file names themselves are NOT the same and need to be named appropriately, otherwise the launcher will not find the file you're trying to use.

I'm speaking from experience here. I just did this and a misnamed payload was preventing me from loading the custom named boot.3dsx that I wanted to load.
Oh I thought you were saying that you thought you downloaded the wrong payload from smea's website, not that you had named it wrong.
 
For future reference, holding Y while running hblauncher_loader when you don't have the payload on your SD card already will download it and place it on your SD card, properly named and all.
Then all that's left is editing it if you feel you want or need to edit it.
 

Site & Scene News

Popular threads in this forum