Hacking [Release] Yellows8's Homebrew Launcher Loader for CFW users (.cia HBL Launcher!)

  • Thread starter Thread starter Zidapi
  • Start date Start date
  • Views Views 332,392
  • Replies Replies 599
  • Likes Likes 44
Status
Not open for further replies.
You can also modify the otherapp payload with a hex editor to launch another file rather than boot.3dsx like we did with themehax. I like this.

¿Has anyone tried this with that hblauncher with arm9 payload support? I'm specially interested in going from the menu to the gateway launcher.
Probably have to keep emunand on 9.2 or lower, I don't know if an emunand above 9.2 would be able to boot GW launcher at all. But it might be possible.

Also, people have reported that editing the payload for this loader caused problems, so I'm not sure if that actually works.
 
Probably have to keep emunand on 9.2 or lower, I don't know if an emunand above 9.2 would be able to boot GW launcher at all. But it might be possible.

Also, people have reported that editing the payload for this loader caused problems, so I'm not sure if that actually works.

Of course, I always meant in 9.2 or lower. It's just for convenience.
The payload edit works fine for me. It's critical to avoid changing the payload file size.
 
So it opens HBL successfully in my N3DS Gateway emunand, but when I try to boot reinand it freezes and I have to hold power to shut down. Does it not allow switching between CFW and Gateway?
 
I have rxTools 3.0 Nightly and it's working fine.

boot.3dsx is in the root of my SD, the renamed payload too, and the 3ds folder.

emuNAND 10.1.0
 
The payload corresponds to the emunand fw, correct? Like if I'm running rxTools 9.5 on my n3DS, I'd use the 9.5 payload? Or does it have to match my updated nver?
 
Payload matches the emunand firmware. The NVer normally doesn't matter for *hax exploits (only really matters for Ninjhax I think, and -maybe- Ironhax.)
 
Last edited by ,
  • Like
Reactions: conradcervantes
Completely useless so strictly necessary!

Here is a build with a 3D banner:
HNI_0006.JPG
 

Attachments

Last edited by FONZD,
9.0 SysNAND 10.3 EmuNAND.

- Extract the CIA to root of SD
- Install CIA on EMUNAND using appmanager or w/e.
- Run CIA and let it install.

That correct?
 
Okay so I managed to get this working alongside CtrBootManager (autoboot to rxTools) in a N3DS.
Beforehand, I will start off assuming you have:
  1. ThemeHax/MenuHax already installed. (This should give you a file called ropbinpayload.bin)
  2. CtrBootManager running and configured
  3. You have already installed the Homebrew CIA.
Let's start:
  • First off, I have to say that I had the original ropbinpayload_menuhax_USA11272_new3ds.bin in the root of the SD card that got installed with MenuHax/ThemeHax
    You should NOT edit this file! This is the one that boots to a file called "boot.3dsx"
    This one should be left alone.
  • Download the "otherapp" payload from the Homebrew Launcher site that corresponds for the Firmware version of the NAND where you installed the Homebrew CIA. (sysNAND or emuNAND) This is important.
    Another way to do it could be to boot the HBL CIA for the first time and letting it download the .bin automatically, although this could sometimes fail, so it is better to be on the safe side by downloading the "otherapp" .bin file from the official Homebrew Launcher website.

  • Once you have the "otherapp" .bin file for your NAND Firmware version, rename it to something like this:
    hblauncherloader_otherapp_payload_NEW-9-0-0-20-USA.bin
    Obviously, my 3DS is a New 3DS on firmware version 9.0.0-20U, so you should change NEW-9-0-0-20-USA according to your version of both 3DS and firmware.
    i.e. OLD-9-0-0-20-USA

  • Open the hblauncherloader_otherapp_payload_NEW-9-0-0-20-USA.bin file that you have just renamed with any HEX editor (like HxD) and search for the string "boot.3ds" (without quotes obviously).

  • Change "boot.3dsx" to the name of the 3DSX file for the Homebrew Launcher. Something like "nhax.3dsx" or "dick.3dsx" or "boob.3dsx" or "shit.3dsx" or "fuck.3dsx". You get the point. :lol:
    Just be sure to keep it 4 characters long, no more, no less.

  • You should now have two 3DSX files in your SD card's root directory.
    One named "boot.3dsx"; which should be CtrBootManager, and another called "nhax.3dsx"; which should be the Homebrew Launcher.

  • Power on your 3DS.
    ropbinpayload should kick in first, which is the payload loaded by Themehax, booting whatever boot.3dsx app you had in the root.
    In my case I had CtrBootManager, which points to rxTools, so it boots directly to my emuNAND.

  • Once on your NAND of preference (sys or emu), open up the HBL installed CIA and boot it up.
    This loads up the hblauncherloader.bin payload, which should boot up your nhax.3dsx file and you should now be in the Homebrew Launcher!
    Enjoy!
So that's it.
It took me quite a while to figure things out on my own, but I hope this helps other out so that they don't struggle as hard as I did. :P
 
Last edited by ShadowOne333,
Don't think you've figured this out on your own (where else would you have come up with nhax.3dsx? I mentioned that one several times in several other threads as this is the one I use.)

Also, plenty of people have reported that editing the payload used by yellows8's launcher often caused problems, so I tell people to edit the menuhax payload instead.
 
  • Like
Reactions: ric.
Don't think you've figured this out on your own (where else would you have come up with nhax.3dsx? I mentioned that one several times in several other threads as this is the one I use.)

Also, plenty of people have reported that editing the payload used by yellows8's launcher often caused problems, so I tell people to edit the menuhax payload instead.
Yeah I'm aware of your posts, but even so the information I gathered in general was somewhat vague and sometimes not well explained.

For example, you mention modifying menuhax's payload.
I did not modify that at all, but rather the otherapp payload which is the one in charge of booting the HBL CIA, not the menuhax ropbinloader since that screws up with autobooting and this way we still have the original payload intact if something new comes up down the road.

Besides, I thought making a nice step by step tuto would be really helpful for others.
 
Last edited by ShadowOne333,
Status
Not open for further replies.

Site & Scene News

Popular threads in this forum