They are not allowed to look at sd card and how would they check ctrnand?
This is why I politely asked. They could check on hacked devices, obviously.
They are not allowed to look at sd card and how would they check ctrnand?
Mainly because most people associate hacking with genning pokemon.Can I ask why 3DSes with CFW are banned from tournaments? Is it for hacked pokemons or something?
Ah okey, I'm not really that in to battling other players so I have no clue about this. I only created 1 pokemon since it was 1% chance to get it and I have hunted it for 4-5 hours. I didn't even make it special just the most basic things I could so I got the stupid sidemission done in Moon.Mainly because most people associate hacking with genning pokemon.
(Despite the fact many people with cfw don't gen pokemon)
Would you um.. clarify which SD card is in use on Section 1 ? Thanks!This is a patch for Luma3DS intended to help hide that you're running CFW. It's primarily designed for Pokemon VGC players who may want to hide their CFW from overstepping judges, or other players. It can also be used to help child-proof your 3DS, or be used if lending out your CFW 3DS.
This patch changes the following from stock Luma3DS:
Testing, ideas and comments are appreciated!
- Option to save config.bin to CTRNAND. (You can also put arm9loaderhax.bin onto CTRNAND for a 100% clean SD card)
- Option to disable region-free/flashcart patches. (This stops someone from putting an out-of-region cart, or banned flashcart in to test for CFW)
- Option to ignore all key presses on boot. (Stops someone from detecting CFW via holding start/select on boot)
- Option to set hidden Key-Combo to remove the lock above.
The ideal setup for a completely hidden CFW is you have 2 SD cards:
- a main SD card with an EmuNAND and all of your good stuff.
- a clean SD card and Vanilla SysNAND (formatted with TinyFormat) for tournaments.
This will show you how to setup a "main" EmuNAND SD card for your normal usage, and a vanilla SysNAND for tournaments which you can use with a clean SD card.
Prerequisites:
Section 1:
- A 3DS with A9LH installed.
- Your main SD card.
- An empty SD card for tournaments.
Section 2:
- Copy latest version of GodMode9 onto SD card in /luma/payloads/.
- Copy TinyFormat CIA onto SD card.
- Backup all content from your main SD card to your computer. This SD card will be erased.
- Boot 3DS with main SD card inserted.
- Install TinyFormat with FBI.
- Start GodMode9 (turn on 3DS and hold Start, select GodMode9).
- <instructions to format an emunand here.
To install, simple put the attached arm9loaderhax.bin on your SD card, or onto CTRNAND with GodMode9.
- a main SD card without an EmuNAND, but with all of your good stuff.
Cool! Could you in the future create an app that hides any selected TitleID? And then hide that app using a computer and configuring bin?
It might be simpler for it to check for arm9loaderhax.bin on the SD card, and if present then use it rather than the one on CTR NAND.
Someone checking for a9lh could use this, but if they know enough to use this then they could also just look up the key combo and try that, so not really losing anything.
Would you um.. clarify which SD card is in use on Section 1 ? Thanks!
I think user set is a bad idea. If they forget the password they could end up with a bricked console they can't restore. Same problems as having a PIN.Hmm, maybe. To be honest, I'm not super familiar with the code, but I *think* thats implementable in /injector/source/patcher.c by patching homemenu to fail a check on selected titles... Another method might be making a separate tool to move the program on the ExData to another folder temporarily... probably the easier solution.
Thanks. So for your first point, Auroras A9Lh build already gives priority to arm9loaderhax.bin, so in a sense what you want implemented should already work unless you use custom firm payloads. For your second point, the key combo is user-set, so they' need to guess one of the 256 possible combinations. Also note that all of these are optional; you don't need to have a custom key combo for instance.
Sorry, I just wrote what I could before my plane left. I will be filling out the guide (to one possible setting) on the 2nd hopefully, but for now just ignore it. But thanks for your catch!
I think user set is a bad idea. If they forget the password they could end up with a bricked console they can't restore. Same problems as having a PIN.
BUT if you say that having Kacleon in your CTR-NAND and having regular Luma on your SD card will mean you can now access payloads normally, then that works out fine!! The key combo is then just to be able to use payloads without having to move files around (eg. if giving it to a child, you don't want them to accidentally access Decrypt9 etc).
Well, this is great! I wanted something like this for ages, but someone made an issue on Luma's GitHub about the console still creating a luma folder even when arm9loaderhax.bin was on CTR NAND and AuroraWright had said that it wasn't a mistake and she had zero plans to fix it. So I thought it would never happen, unless I was brave enough to try modifying it myself and run it on my console. Now I don't have to :-)
Wouldn't checking SD cards be illegal? Or do you forfeit that right when you enter a tournament?
Sorry, I just wrote what I could before my plane left. I will be filling out the guide (to one possible setting) on the 2nd hopefully, but for now just ignore it. But thanks for your catch!
What about PowerSaves? The 3DS remain virgin but game get hacked. And theres no way to know if PowerSave was used or not.Mainly because most people associate hacking with genning pokemon.
(Despite the fact many people with cfw don't gen pokemon)
What about PowerSaves? The 3DS remain virgin but game get hacked. And theres no way to know if PowerSave was used or not.