Hacking Locked myself out of EMUNand. Quick question.

[Garrincho]

So I had my O3ds on 9.2 with emunand already on 10.3 and installing cias no problem (I followed this guide https://gbatemp.net/threads/tutorial-more-or-less-catch-all-tutorial.407080/).

It was all fine until I installed the HBLauncher cia. According to the guide I had to launch it pressing Y to download the payload and then edit it to launch HBL8.3dsx instead of boot.3dsx.

I edited what I thought was the correct payload .bin but then menuhax wouldn't trigger, I'd go straight to sysnand with "an error has occurred". I edited the file I had edited earlier to trigger boot.3dsx again but same happens. Do I need to reinstall menuhax or something? what files should I edit back to leave it as it was?

 

[Chuu]

Okay, so reinstall menuhax though your sysnand. after that, you want to edit the hblauncher payload or whatever its called and have that point to "hbl8"

 

[Garrincho]

Alright I'll go ahead and do that... How can I identify what the hblauncher payload is? Because I clearly edited the wrong file.

 

[Bull Moose 2016]

Alright I'll go ahead and do that... How can I identify what the hblauncher payload is? Because I clearly edited the wrong file.

Mine is called this: hblauncherloader_otherapp_payload_NEW-9-5-0-28-EUR

 

[coreycubed]

Alright I'll go ahead and do that... How can I identify what the hblauncher payload is? Because I clearly edited the wrong file.

I haven't read that guide, but I can tell you what I did. I installed hblauncher.cia, but I did not manually download the payload from smea's site. Instead, after I installed the CIA, I held Y when launching the Homebrew Launcher. This downloaded the payload to my SD card. I then restarted my 3DS, then opened that payload file on my SD card in Notepad++ and modified the name of boot.3dsx to bhbl.3dsx. I was then able to use the Homebrew Launcher in emuNAND to launch homebrew.

edit: I see in your post that you did hold Y, sorry. In that case, maybe just try using four letters, all lowercase, no numbers. While that shouldn't be required, that's what worked for me.

Other guides I read suggested manually downloading the payload, editing the file and renaming it, then copying it to your SD card. For some reason, this did not work for me. I'm not sure if I downloaded the wrong payload or what, but letting the app download it for me worked first try.

(Obviously, you can either remove the SD card from your 3DS to access the downloaded payload, or you can transfer it over FTP, make the modification, and then write it back via FTP.)

 

[Garrincho]

I haven't read that guide, but I can tell you what I did. I installed hblauncher.cia, but I did not manually download the payload from smea's site. Instead, after I installed the CIA, I held Y when launching the Homebrew Launcher. This downloaded the payload to my SD card. I then restarted my 3DS, then opened that payload file on my SD card in Notepad++ and modified the name of boot.3dsx to bhbl.3dsx. I was then able to use the Homebrew Launcher in emuNAND to launch homebrew.

Other guides I read suggested manually downloading the payload, editing the file and renaming it, then copying it to your SD card. For some reason, this did not work for me. I'm not sure if I downloaded the wrong payload or what, but letting the app download it for me worked first try.

(Obviously, you can either remove the SD card from your 3DS to access the downloaded payload, or you can transfer it over FTP, make the modification, and then write it back via FTP.)

Yeah that's what I tried to do, I started the HBlauncher pressing Y and saw the download happening (i think), then it went ahead and loaded CTRbootmanager and then it crashed. What's the name of the payload the HBlauncher downloades?

 

[coreycubed]

Yeah that's what I tried to do, I started the HBlauncher pressing Y and saw the download happening (i think), then it went ahead and loaded CTRbootmanager and then it crashed. What's the name of the payload the HBlauncher downloades?

hblauncherloader_otherapp_payload_OLD-10-3-0-28-USA.bin or something like that. It'll be on the root of your SD card. It's normal that CTRBootManager will crash the first time. Until you make the modification to that file, it won't launch the other bhbl.3dsx.

I just did this yesterday so it's still fresh in my head. Let me know if you still run into issues.

 

[Garrincho]

hblauncherloader_otherapp_payload_OLD-10-3-0-28-USA.bin or something like that. It'll be on the root of your SD card. It's normal that CTRBootManager will crash the first time. Until you make the modification to that file, it won't launch the other bhbl.3dsx.

I just did this yesterday so it's still fresh in my head. Let me know if you still run into issues.

Weird, that file isn't on my sd card, even tho I started the HBlauncher with Y pressed and it was downloading something.

Maybe downloading it manually could work for me? (I don't really want to launch the hblauncher cia again since I just reinstalled menuhax and I'm back in emunand)

 

[coreycubed]

Weird, that file isn't on my sd card, even tho I started the HBlauncher with Y pressed and it was downloading something.

Maybe downloading it manually could work for me? (I don't really want to launch the hblauncher cia again since I just reinstalled menuhax and I'm back in emunand)

I'm still not sure how hblauncher.cia is breaking your menuhax for sysNAND. Didn't you say it only broke when you modified the bin? Which file did you modify last time?

 

[jaksy]

That whole HBL8.3dsx step is really needlessly complicated in that tutorial and I don't understand why it exists.
If you use ctrbootmanager then when the HBlauncher cia calls for a boot.3dsx it would boot to ctrbootmanager's menu allowing you to choose where to go including the HBmenu (made by renaming smea's ORIGINAL boot.3dsx to boot_hb.3dsx and putting it on root, making sure boot.cfg references it as such)

I imagine you're already using theme/homemenuhax as an entrypoint, so you might as well give yourself more control over what you boot into during firmware shifts.

 

[coreycubed]

That whole HBL8.3dsx step is really needlessly complicated in that tutorial and I don't understand why it exists.
If you use ctrbootmanager then when the HBlauncher cia calls for a boot.3dsx it would boot to ctrbootmanager's menu allowing you to choose where to go including the HBmenu (made by renaming smea's ORIGINAL boot.3dsx to boot_hb.3dsx)

I imagine you're already using theme/homemenuhax as an entrypoint, so you might as well give yourself more control over what you boot into during firmware shifts.

Yeah, I considered doing that when I set mine up, but my ctrbootmanager autoboots, and would I ever really want to go to rxtools? (the only other boot 3dsx I use) Easier to just not have to hold a button and go straight to where I want to go.

 

[jaksy]

Yeah, I considered doing that when I set mine up, but my ctrbootmanager autoboots, and would I ever really want to go to rxtools? (the only other boot 3dsx I use) Easier to just not have to hold a button and go straight to where I want to go.

ctrbootmanager can be set to autoboot into whatever entry you choose by default based on your set timeout.

Also you considered doing what when you set up ctrbootmanager? That's HOW ctrbootmanger works.

And of course you would want to go into rxtools if it's your cfw. I really don't understand your post.

 

[coreycubed]

ctrbootmanager can be set to autoboot into whatever entry you choose by default based on your set timeout.

Also you considered doing what when you set up ctrbootmanager? That's HOW ctrbootmanger works.

Also of course you would want to go into rxtools if it's your cfw. I really don't understand your post.

If I understand what you said, you were asking why I wouldn't just let hblauncher.cia boot to ctrbootmanager.

Here's why:

Scenario: O3DS 9.2 sysNAND, 10.3 emuNAND

Ctrbootmanager is autobooting to rxtools. If I hold select, I can choose between rxtools and homebrew menu.

When I turn on my 3DS, Menuhax triggers, launches ctrbootmanager, which autoboots rxtools.

Now let's say hblauncher.cia in emuNAND goes back to ctrbootmanager. I'm just autobooting to rxtools again unless I hold my ctrbootmanager button (SELECT by default). I don't want to launch rxtools when I'm ALREADY in emuNAND. So I have to hold Select and then choose homebrew menu.

Instead, I change my payload to redirect me straight to homebrew. No button holding needed, and I don't end up back in rxtools.


What is unclear about this?

 

[jaksy]

What is unclear about this?

Why go to that length when you can accomplish the same thing easier by using ctrbootmanager?

Are you sure you aren't thinking of bootctr or perhaps you have rxtools set to autoboot from themehax, instead of having ctrbootmanager set to autoboot instead.

With ctrbootmanager properly installed you should just boot to it between firmware shifts and if you idle it autoboots you into your CFW, if you move the dpad up or down you can choose another entry from the list.
You can change the autoboot entry and how fast it boots. You can change the buttons that trigger or do not trigger themehax.
You can access the HB menu from both sysnand and emunand this way quite easily and quickly.
If you change your mind about where you want to go you can choose another entry or even direct yourself to a file on the fly to boot.
It gives you way more control.

I don't understand why you don't just use this.

 

[coreycubed]

Why go to that length when you can accomplish the same thing easier by using ctrbootmanager?

Are you sure you aren't thinking of bootctr or perhaps you have rxtools set to autoboot from themehax, instead of having ctrbootmanager set to autoboot instead.

Nope. Ctrbootmanager is set to autoboot. What's weird about that?

Challenge: design a solution that can do all of the following:

Press no buttons: boot to emuNAND, preferably fast as possible
Hold a button during boot: boot to sysNAND
Hold a button during boot: allow booting to Homebrew Launcher (for sysNAND)
Hold a button during boot: boot to rxTools debug menu
Access Homebrew Launcher by pressing only one button from emuNAND

My current solution does all of the above.

--------------------- MERGED ---------------------------

Why go to that length when you can accomplish the same thing easier by using ctrbootmanager?

Are you sure you aren't thinking of bootctr or perhaps you have rxtools set to autoboot from themehax, instead of having ctrbootmanager set to autoboot instead.

With ctrbootmanager properly installed you should just boot to it between firmware shifts and if you idle it autoboots you into your CFW, if you move the dpad up or down you can choose another entry from the list.
You can change the autoboot entry and how fast it boots. You can change the buttons that trigger or do not trigger themehax.
You can access the HB menu from both sysnand and emunand this way quite easily and quickly.
If you change your mind about where you want to go you can choose another entry or even direct yourself to a file on the fly to boot.
It gives you way more control.

I don't understand why you don't just use this.

I don't want to wait any number of seconds at ctrbootmanager. I don't even want to see the menu unless I hold a button. It's just wasting boot seconds.

 

[jaksy]

Nope. Ctrbootmanager is set to autoboot. What's weird about that?

Challenge: design a solution that can do all of the following:

Press no buttons: boot to emuNAND, preferably fast as possible
Hold a button during boot: boot to sysNAND
Hold a button during boot: allow booting to Homebrew Launcher (for sysNAND)
Hold a button during boot: boot to rxTools debug menu
Access Homebrew Launcher by pressing only one button from emuNAND

My current solution does all of the above.

It would do all that too, short of having two different autoboot entries, though you might be able to configure different ones to boot based on different key presses.

I honestly don't think you understand how this whole bootmanager thing works.

To be clear I'm not knocking YOUR setup, I'm knocking the tutorial using these convoluted steps instead of simply using ctrbootmanager.

I've seen many users caught up on this part already.

 

[coreycubed]

It would do all that too, short of having two different autoboot entries, though you might be able to configure different ones to boot based on different key presses.

I honestly don't think you understand how this whole bootmanager thing works.

Stop patronizing me; I understand how it works.

If you read the design requirements, you would understand why pressing additional buttons does not meet the criteria.

I don't want to have to hold down buttons when performing common tasks. The two most common tasks that involve launching 3dsx files are booting to emuNAND and accessing Homebrew Launcher from emuNAND. It is rare that I need to access sysNAND, access Homebrew Launcher for sysNAND during boot or rxTools' debug menu. Those actions have associated buttons to hold during launch. All others do not.

 

[jaksy]

I don't want to have to hold down buttons when performing common tasks. The two most common tasks that involve launching 3dsx files are booting to emuNAND and accessing Homebrew Launcher from emuNAND. It is rare that I need to access sysNAND, access Homebrew Launcher for sysNAND during boot or rxTools' debug menu. Those actions have associated buttons to hold during launch. All others do not.

Again, that's fair for your own setup, but it doesn't make sense to have new users go to such lengths to get the homebrew launcher autobooting when they can just select it from the ctrbootmanager list.

That's literally the only thing different between my setup with ctrbootmanager and your specifications. After running the homebrew launcher cia I'd have to press down once to enter the HBmenu, otherwise it would default to my autoboot if no action is taken, which is in my case rxtools, so I'd be in emunand automatically on boots.
If I wanted the rxtools menu I hold the rxtools modifier key when it's booting.
If I want into sysnand I hold the modifier key that doesn't activate themehax.

 

[coreycubed]

Again, that's fair for your own setup, but it doesn't make sense to have new users go to such lengths to get the homebrew launcher autobooting when they can just select it from the ctrbootmanager list.

That's literally the only thing different between my setup with ctrbootmanager and your specifications. After running the homebrew launcher cia I'd have to press down once to enter the HBmenu, otherwise it would default to my autoboot if no action is taken.

Just out of curiosity, what happens when you autoboot back into rxTools? Also, how long does the screen linger on the ctrbootmanager menu before autobooting?

 

[jaksy]

Just out of curiosity, what happens when you autoboot back into rxTools? Also, how long does the screen linger on the ctrbootmanager menu before autobooting?

It lingers to whatever you set it to in the boot.cfg or settings.
If I keep chaining autoboots from emunand to emunand to emunand it eventually redscreen hangs on themehax. But this would be common if you forced that through any method.