Homebrew Official [Download] Decrypt9 - Open Source Decryption Tools (WIP)

Datalogger · Dec 4, 2015

d0k3 said:
Make sure you download my version (see the opening post for the link).

Changed username, quite confusing . Anyways, what can 3DS Multi Decryptor do that Decrypt9 can't at this point? If there still is something, I'd be interested in adding that feature to Decrypt9.

Yeah, I've been putting off changing it, but I kept getting PM/asked if I'm the same smyers75 from some Drone site (I'm not), so I finally changed it.
I resurrected my Datalogger nick from my old DishNetwork/DirecTV ST-20 hacking days.

There's nothing on the 3DS side that Decrypt9 can't do, but on the PC side Multi Decryptor's "SCDNto3DS.py" comes in might handy for pulling down eShop content.

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

d0k3 said:
Alright, I've just readded the experimental SD formatter feature. You need to compile yourself, and the SD formatter itself won't clone the SysNAND to the EmuNAND. Everything looks fine when using this on a 3DS, however, Windows complains about errors in the formatted SD card (although it should be totally fine). No idea about that yet... Maybe you'll find something.

Testing now - had to wait a few minutes for Windows10 to re-boot from the update that FINALLY fixed the ridiculous "512 Start Menu entries" bug.

Datalogger · Dec 4, 2015

Still tracking this down, maybe the 6th byte just before the name is entry causing Windows to puke..

I'm doing a little test, changing one byte and re-writing the SD card - takes a while.

In the mean time, I made a disk image before and after repairing the SD card with chkdsk /f
Results are below:

Code:

C:\Users\Admin>chkdsk m: /f
The type of the file system is FAT32.
Volume Serial Number is DEC9-DEC9
The \ entry contains a nonvalid link.
Windows is verifying files and folders...
File and folder verification is complete.

Windows has made corrections to the file system.
No further action is required.
   14,588,928 KB total disk space.
           32 KB in 1 files.
   14,588,864 KB are available.

       32,768 bytes in each allocation unit.
      455,904 total allocation units on disk.
      455,902 allocation units available on disk.

Binary File Compare

Code:

G:\3>fc /b "Decrypt9_made_emuNAND" "Decrypt9_made_emuNAND_fixed"
Comparing files Decrypt9_made_emuNAND and DECRYPT9_MADE_EMUNAND_FIXED
3AF00241: 01 00
3AF005E8: DE DC
3AF005EC: 03 06

Errored Code

Code:

3AF00240  80>01<29 C9  DE C9 DE 44  45 43 52 59  50 54 39 53  _ú)úúúúDECRYPT9S 
3AF00250  44 20 46 41  54 33 32 20  20 20 00 00  00 00 00 00  D FAT32   ...... 
3AF00260  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................

Good Code

Code:

3AF00240  80>00<29 C9  DE C9 DE 44  45 43 52 59  50 54 39 53  _ú)úúúúDECRYPT9S 
3AF00250  44 20 46 41  54 33 32 20  20 20 00 00  00 00 00 00  D FAT32   ...... 
3AF00260  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................

Datalogger · Dec 4, 2015

OK, in order to finish testing this, I need the byte being set at 0x3AF00241 to be 00 instead of 01
Not sure how Decrypt9WIP is setting this byte, but it is what causes chkdisk to see the disk in error.

This is apparently a Flag byte that is telling Windows that there is a problem with the disk.

(The address is always 0x3AF00241 regardless of the size of the SD card I use on my O3DS....)

I have confirmed that all 3 bytes need to be change for Windows to "see" the SD card without errors. I tried changing one-at-time, but until I reset all 3, it did not work.

On a 16GB SD Card - If I change

Code:

3AF00241: 01 to 00
3AF005E8: DE to DC
3AF005EC: 03 to 06

On 8GB Card - If I change

Code:

3AF00241: 01 to 00
3AF0420B: F0 to FF
3AFD6A0B: F0 to FF

It works fine in Windows the 3DS and in Gateway emuNAND after injecting the NAND in Decrypt9WIP and after changing these three bytes.

Edit:
Oh, and before I forget - this does not have the LEFT-RIGHT-DOWN-UP-A verification check.
A little dangerous for those that don't keep backups of backups of backups (and another backup on cloud servers)

Also, hate to be the bearer of more issues, but the "Gateway User Manual" fix does not work with other region .CIA files.

It has been reported and confirmed that newer Japan and Europe region .CIA files still will not load in Gateways even after being Decrypt9 "Deep" or "GW" fixed.

They still crash at 99% when trying to add the User Manual using a Gateway (using both FBI and dEVmEn)

The same exact .CIA files DO load just fine in any CFW....only Gateway has a problem loading them.

I still think the best fix for GATEWAY's SCREW-UP is to have a function that completely removes the User Manual for Gateway users.

Since CFW users can use the Manuals with no problems (SKY3DS, reiNAND, rxTools, Cakes, and all other properly working CFW), there is still a need for an easy way to either leave the User Manual or to completely strip it out of the ROM for the unfortunate ones using the flawed Gateway's that cannot read a properly decrypted User Manual.

d0k3 · Dec 4, 2015

Datalogger said:
OK, in order to finish testing this, I need the byte being set at 0x3AF00241 to be 00 instead of 01
Not sure how Decrypt9WIP is setting this byte, but it is what causes chkdisk to see the disk in error.

This is apparently a Flag byte that is telling Windows that there is a problem with the disk.

(The address is always 0x3AF00241 regardless of the size of the SD card I use on my O3DS....)

I have confirmed that all 3 bytes need to be change for Windows to "see" the SD card without errors. I tried changing one-at-time, but until I reset all 3, it did not work.

On a 16GB SD Card - If I change

Code:

3AF00241: 01 to 00 3AF005E8: DE to DC 3AF005EC: 03 to 06

On 8GB Card - If I change

Code:

3AF00241: 01 to 00 3AF0420B: F0 to FF 3AFD6A0B: F0 to FF

It works fine in Windows the 3DS and in Gateway emuNAND after injecting the NAND in Decrypt9WIP and after changing these three bytes.

Edit:
Oh, and before I forget - this does not have the LEFT-RIGHT-DOWN-UP-A verification check.
A little dangerous for those that don't keep backups of backups of backups (and another backup on cloud servers)

Also, hate to be the bearer of more issues, but the "Gateway User Manual" fix does not work with other region .CIA files.

It has been reported and confirmed that newer Japan and Europe region .CIA files still will not load in Gateways even after being Decrypt9 "Deep" or "GW" fixed.

They still crash at 99% when trying to add the User Manual using a Gateway (using both FBI and dEVmEn)

The same exact .CIA files DO load just fine in any CFW....only Gateway has a problem loading them.

I still think the best fix for GATEWAY's SCREW-UP is to have a function that completely removes the User Manual for Gateway users.

Since CFW users can use the Manuals with no problems (SKY3DS, reiNAND, rxTools, Cakes, and all other properly working CFW), there is still a need for an easy way to either leave the User Manual or to completely strip it out of the ROM for the unfortunate ones using the flawed Gateway's that cannot read a properly decrypted User Manual.

Thanks a ton, you solved it! I already put up a new commit that let's FATFS handle the formatting, but there is some minor problem with that (namely, there is a large, unexplained delay when formatting for the EmuNAND). That new fix works as well (without manual changing of bytes), but it doesn't properly set the volume label (aka drive name in Windows). I'll have to decide which solution to use.

EDIT: The label issue is fixed, the delay is not. Further testing required for that new method. I'm pretty sure the FATFS format is better than mine so we'll use that (the delay might be a problem specific to my SD card). Also, the new code is a mess right now, will fix that later.

Now, the byte at offset ?????241 is easily explained (the FAT 'current head' position, I wondered what FAT32 does with that), but the other two (in both cases) are not. Could you show me more of the data surrounding these offsets (only if you still have it, of course)?

Unlock sequence: coming if this makes it into the release. Exactly this is also the reason why you had to compile yourself

. This will need some special text in unlock sequence, and I might also offer the user the possibility to switch his SD card before actually running the function.

Now, about the GW user manual fix - do you mean out of region CIAs? Meaning you tested it on a US 3DS console? If so, I'm pretty sure you also applied a region fix somewhere, and maybe even a FW spoof, correct? Well, that might have changed the manual as well, thus breaking the compatibility (cause emanual sigs are broken then). The function in Decrypt9 should actually be working well, but it can't fix what other tools have already broken

. I think the best place for an actual 'removement' fix would be Riku's converter (I'm sure you used that). Riku's tool should also be the one responsible for any modifications on content 1, content 2, ..., so the GW fix should be right at home there, and also easy to add. I'm unsure if Riku would still be willing to put more work into that converter, though, but asking can't hurt. I myself am somewhat averse to the idea of actually irreversibly removing data in Decrypt9. I'm not averse to doing this in an external tool, though. Maybe there's also some way to just 'disarm' these contents, so they are still in there but not installed when installing via GW.

Datalogger · Dec 4, 2015

There's not much near the changed code, just a bunch of null characters...
8GB Card Before Fix

Code:

3AF04140  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF04150  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF04160  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF04170  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF04180  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF04190  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF041A0  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF041B0  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF041C0  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF041D0  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF041E0  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF041F0  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF04200  F8 FF FF FF  FF FF FF 7F  FF FF FF F0  FF FF FF 0F  ...............
3AF04210  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF04220  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF04230  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF04240  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF04250  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF04260  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF04270  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF04280  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF04290  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF042A0  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF042B0  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF042C0  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................

8GB Card After Fix

Code:

3AF04140  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF04150  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF04160  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF04170  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF04180  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF04190  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF041A0  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF041B0  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF041C0  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF041D0  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF041E0  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF041F0  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF04200  F8 FF FF FF  FF FF FF 7F  FF FF FF FF  FF FF FF 0F  ...............
3AF04210  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF04220  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF04230  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF04240  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF04250  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF04260  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF04270  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF04280  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF04290  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF042A0  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF042B0  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF042C0  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................

16GB Card Before Fix

Code:

3AF00520  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF00530  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF00540  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF00550  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF00560  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF00570  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF00580  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF00590  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF005A0  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF005B0  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF005C0  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF005D0  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF005E0  00 00 00 00  72 72 41 61  DE F4 06 00  03 00 00 00  ....rrAa........
3AF005F0  00 00 00 00  00 00 00 00  00 00 00 00  00 00 55 AA  ..............U.
3AF00600  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF00610  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF00620  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF00630  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF00640  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF00650  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF00660  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF00670  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF00680  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF00690  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF006A0  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................

16GB Card After Fix

Code:

3AF00520  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF00530  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF00540  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF00550  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF00560  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF00570  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF00580  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF00590  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF005A0  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF005B0  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF005C0  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF005D0  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF005E0  00 00 00 00  72 72 41 61  DC F4 06 00  06 00 00 00  ....rrAa........
3AF005F0  00 00 00 00  00 00 00 00  00 00 00 00  00 00 55 AA  ..............U.
3AF00600  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF00610  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF00620  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF00630  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF00640  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF00650  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF00660  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF00670  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF00680  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF00690  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
3AF006A0  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................

-dl

urherenow · Dec 4, 2015

Some people use 32GB and 64GB cards... do you need different offsets for those? There are also 128GB cards floating around; for O3DS, I even have a 256GB card (although I'm not using that one at the moment...)

Datalogger · Dec 4, 2015

I'm sure there's an offset value in the MBR that points to where the tables are.
I'll look into it and map it out, but I'm not sure how a 3DS lib could use the data...

Gruntzer · Dec 4, 2015

can this be used to update sysnad manually or from SOAP server ?

d0k3 · Dec 4, 2015

urherenow said:
Some people use 32GB and 64GB cards... do you need different offsets for those? There are also 128GB cards floating around; for O3DS, I even have a 256GB card (although I'm not using that one at the moment...)

Datalogger said:
I'm sure there's an offset value in the MBR that points to where the tables are.
I'll look into it and map it out, but I'm not sure how a 3DS lib could use the data...

It's in the MBR (the first sector of the SD card). Easy to take a look at HxD and you can also take a look at my last few commits or just look it up in the Wikipedia. But hey, why not compile fresh? With the last few commits it should work with any SD card and right from the start. Be careful, no safety clamps in that function yet, and it will obviously wipe your SD card.

Also @Datalogger thanks for the data. But, these changes shouldn't be required at all, I'm completely stumped. I guess it's better to let FatFS handle the formatting and build the MBR myself. This is how it is handled now.

ayanekochan · Dec 4, 2015

d0k3 said:
Make sure you download my version (see the opening post for the link).

Yep, I made sure I installed your latest release, still the same though.

urherenow said:
Have you tried from ctrbootmanager? Not sure if you can load that directly from CN, but you can use CN to install menuhax. And you are loading from 9.2 or below sysnand, correct? It will never work on emunand if your CFW is using Firmlaunch and/or above 9.2.

9.2 sysnand here, I've been auto booting pasta with ninjhax 2.5 from CN for normal use. Is there any way to load decrypt9 other than menuhax? If it works with that shouldn't homebrew loader load decrypt9 successfully as well?

Shadowtrance · Dec 4, 2015

ayanekochan said:
9.2 sysnand here,
Is there any way to load decrypt9 other than menuhax?
If it works with that shouldn't homebrew loader load decrypt9 successfully as well?

HB menu, MSET, broswer (old 3ds only)...
It does load it fine...

d0k3 · Dec 4, 2015

ayanekochan said:
Yep, I made sure I installed your latest release, still the same though.

9.2 sysnand here, I've been auto booting pasta with ninjhax 2.5 from CN for normal use. Is there any way to load decrypt9 other than menuhax? If it works with that shouldn't homebrew loader load decrypt9 successfully as well?

You can also try with Decrypt9.bin and my BrahmaLoader. Needs to be loaded from HBL 2.5 and needs a small bit of manual work, but I promise it's easy.

peteruk · Dec 4, 2015

Shadowtrance said:
HB menu, MSET, broswer (old 3ds only)...
It does load it fine...

Is there a .NDS file to load via MSET ?

Shadowtrance · Dec 4, 2015

peteruk said:
Is there a .NDS file to load via MSET ?

There is, it should be in the release zip.

peteruk · Dec 4, 2015

Shadowtrance said:
There is, it should be in the release zip.

thanks for the speedy reply mate, i had the full zip and didn't even realise, as you may know i am a big fan of MSET so this is just great, thank you !

Shadowtrance · Dec 4, 2015

peteruk said:
thanks for the speedy reply mate, i had the full zip and didn't even realise, as you may know i am a big fan of MSET so this is just great, thank you !

Np.

So @d0k3 any idea why the debug_bg and unmount images aren't working yet? (I'm only using placeholders of the same size (one for top and one for bottom screen) at the moment, so doesn't really matter what you use to test).

peteruk · Dec 4, 2015

Something I can't quite understand, if great developer's like you guys are able to make your homebrew work directly through MSET, creating your own .dat loader file and own .nds file to work in this manner, why can HBL not be made to work in the same kind of way?

dark_samus3 · Dec 4, 2015

peteruk said:
Something I can't quite understand, if great developer's like you guys are able to make your homebrew work directly through MSET, creating your own .dat loader file and own .nds file to work in this manner, why can HBL not be made to work in the same kind of way?

The crash caused by MSET crashes most of the services which HBL uses... Since this and CFW don't use any of the 3ds services these work fine

peteruk · Dec 4, 2015

dark_samus3 said:
The crash caused by MSET crashes most of the services which HBL uses... Since this and CFW don't use any of the 3ds services these work fine

Thanks for the clear explanation, I finally see it more clearly

Datalogger · Dec 5, 2015

d0k3 said:
It's in the MBR (the first sector of the SD card). Easy to take a look at HxD and you can also take a look at my last few commits or just look it up in the Wikipedia. But hey, why not compile fresh? With the last few commits it should work with any SD card and right from the start. Be careful, no safety clamps in that function yet, and it will obviously wipe your SD card.

Also @Datalogger thanks for the data. But, these changes shouldn't be required at all, I'm completely stumped. I guess it's better to let FatFS handle the formatting and build the MBR myself. This is how it is handled now.

Is there room in a buffer to store a payload to save to the root of the SDCard, maybe an optional parameter setup before compiling? (boot.3dsx, bootrx.3dsx, Launcher.dat or ??)

What would really be the icing on the cake would be a boot payload and a small FTP server.
Then you would never need to take the card out to the 3DS after making the emuNAND

(I know, you're thinking "What do you want next, eggs in your beer?")

Homebrew Official [Download] Decrypt9 - Open Source Decryption Tools (WIP)

Living the Dream

Living the Dream

Living the Dream

3DS Homebrew Legend

Living the Dream

Well-Known Member

Living the Dream

Well-Known Member

3DS Homebrew Legend

Well-Known Member

Well-Known Member

3DS Homebrew Legend

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Living the Dream

Similar threads

Popular threads in this forum