Separate names with a comma.
Discussion in '3DS - Homebrew Development and Emulators' started by hacksn5s4, Jan 8, 2016.
idk how do do this
Open menuhax manager and choose "Configure/check haxx trigger button(s)". Then choose "Type 2: Only trigger the haxx when the PAD state doesn't match the specified value". Then hold down the button you want to press to stop menuhax booting, and while holding it touch the bottom screen. Then quit the menuhax manager. The next time you reboot your 3DS it should boot straight to HBL via menuhax. If you reboot and hold down the button you held when setting up the trigger button, you should get to the system home menu.
It's easier to pick type 1 and hit the touch screen without any buttons pressed; after that everything cancels homebrew loading rather than just one specific button.
Or you could choose type 1, only trigger when the PAD state matches the specific value.
And then instead of pressing buttons, just press nothing.
The home menu will start if you press a but.
The home-brew launcher will launch if you press nothing
The only problem with that is that some homebrew launchers use certain keys for other functions. For example, the old emergency launcher I made and the better version based on its source will boot a different 3dsx depending on what button is held. So if you're using any of these, you would be better off configuring a specific button to force a system home menu boot.
other thing is menuhax some times boots to yellow screen its nto 100% stable
I'd also add that if you make your 3DS autoboot, it's not only for convenience. For people using an emuNAND it is also to avoid people booting into sysNAND and updating it by ignorance. Which means that if it's easy to boot to sysNAND (press any key), you are more likely to get problems than if you use Type 2 and put stupid keys yourself. So I agree with @mashers solution with Type2.
Oooooh. I didn't know that was a thing.
— Posts automatically merged - Please don't double post! —
I just color coded mine. Blue sysNAND, black emuNAND. Favorite colors.
While I agree, it's the end user's own fault if they "update by ignorance." The first thing I did when I unlinked my sysNAND and emuNAND was lock up my sysNAND like a mutant boar. Set up tubehax on sysNAND (and later emuNAND, with the possibly coming 10.4 news) and set menuhax to Type 2. Now my 3DS autoboots Ctr Boot Manager unless I hold R while it's turning on. CTRBM autoboots rxTools in 3 seconds; if I don't want it to, I have other options to boot in the manager. IMO everyone should use CTR Boot Manager. But that's just me! I'm also relatively new to CFW and emuNAND so there might be other preferred options I've not yet discovered.
I had to format my system in order for my downgrade to be successful, so of course my sysNAND's home menu was reset and had nothing but the default icons and stuff. When I was setting up the emuNAND, I had to change the theme on emuNAND so I could tell the difference easily. lol
Read my post again and read it with my mind that time (I mean that yeah, maybe that was poorly worded ). I was not talking about the 3DS owner but someone random like a cousin or a friend who would borrow the 3DS (and not be aware of your color code). That guy could boot to sysNAND by mistake if you can easily boot to sysNAND (and "press any key" is easy, "press Down+B" isn't) then update. That's why I really recommend Type 2 with a combination rather than Type 1 with nothing.
Why would you ever let someone borrow your 3DS, much less not tell them exactly what you put on it
smh my shit is guarded like a fucking fortress; my ten year old cousin was allowed to use it originally but he's now barred from access to it permanently because i want my shit safe
I don't often let people borrow my 3DS, and when I do, I boot everything myself before letting them touch it (like boot Smash for example, they never see any 3DS menu).
But I was not talking about "borrowing", maybe someone would touch your 3DS when it's on your desktop. And yeah, you may say "don't leave it on your desktop", ok but even if it's in your bag, someone (very poorly educated) could think "hey, but I can borrow that 3DS in that bag while waiting for my friend to get out of the toilets" or something.
Yes, these things shouldn't happen, but whatever, if as you say you like to keep your shit safe, then Type 2 is safer, that's all. Whatever security you put around your 3DS, IF someone has access to it, Type 2 would protect you better than Type 1.
You didn't say anything about that in your post, though. Forgive me for not reading between the lines to find text that wasn't there. You do make a good point, though. But to that end, I agree with darklordrs. lol
Nobody uses anything of mine. Not my 3DS, not my Wii U, not my Xbox 360, not my PC. ESPECIALLY not my PC. I learned from an early age that you don't let anybody use anything you care about. Case and point, my sister would get violent with devices if she got angry.
Well you're from the USA and I'm from France so of course sometimes I think I say things in English even though I don't. And when I wrote "For people using an emuNAND it is also to avoid people booting into sysNAND and updating it by ignorance", I wrote "people" twice so that the second "people" are not the same as the first "people". But yeah, poorly worded I guess...
Lifehack: never let people touch things you own.
Sometimes they get violent that you don't lmao, my sister broke the laptop I got for my birthday in Dec. 2013. Amazing.
Don't worry about it, misunderstandings happen. Besides, your English is fine. Better than most native English speakers, in fact. I find that's almost always the case with non-native English speakers. lol
But back on topic... I assume you use Type 2, yes? What buttons do you have set for yours? Just curious. I simply went with R since nobody ever gets near my 3DS so I'm at no risk of idiots fiddling with it.
Yeah, I use Type 2, with Down+B. I considered adding a trigger too, like L+Down+B but figured that already no one would do Down+B while booting. And same, no one gets near my 3DS when they are vulnerable (turned off; once in Smash there is almost nothing to fear) but still, I just really want no one to be able to boot to sysNAND by mistake. At one point I even made "Quick Shutdown" the default thing to happen when turning the 3DS on, thinking that would deter people from using the 3DS, but then I figured it would make them try keys, and that's not something I want.