I hereby claim:
- I am mariomasta64 on github.
- I am mariomasta64 (https://keybase.io/mariomasta64) on keybase.
- I have a public key ASB3L39ce860TQVSItp_vQqi6hL4jVhF3UPGlVg6Xs3Aogo
To claim this, I am signing this object:
This is an ADVANCED guide and should not be attempted by anyone who does not COMPLETELY understand each step and what it does to their device. Additionally, the prerequisite is that you have already performed a region change on your 3DS. You also need access to another 3DS on the target region that you can format to a non-NNID linked state (you can use emuNAND here). For simplicity, I am going to assume you are region changing a N3DS from Japan to USA and have access to a USD O3DS. The guide is in two parts: System Transfer and NNID Linking. For those who wish to just have access to USA eShop (and the ability to download free games; if you only want to use eShop to purchase games, you do not have to link a NNID) you can skip to the second part. | |
To modify requests, I use Charles Proxy to set breakpoints so I can change requests and responses as they come in. However, you can do it in any why you choose. Also, since 9.2 eShop was disabled, you may have to additionally modify all requests from the 3DS to send a |
I hereby claim:
To claim this, I am signing this object:
# The following is adapted from https://github.com/reswitched/loaders/blob/master/nxo64.py | |
# | |
# =========================================================================================== | |
# | |
# Copyright 2017 Reswitched Team | |
# | |
# Permission to use, copy, modify, and/or distribute this software for any purpose with or | |
# without fee is hereby granted, provided that the above copyright notice and this permission | |
# notice appear in all copies. | |
# |
mariomasta64.me/browser/
Due to so many misinformation, false claims and confusion that goes around the web I've decided to make this quick comparison of all backup enabling tools, hackable vita firmwares and which one you should be using and why.
Date of last update: 20.08.2018
NoNpDRM Rips | Vitamin / MaiDumpTool Dumps | |
---|---|---|
All original files untouched | ✅ | ❌ |
Support Retail DLCs | ✅ | ❌ |
Support Ripped (NoNpDRM) DLCs | ✅ | ❌ |
Support Dumped (Vitamin/Mai) DLCs | ✅1 | ✅ |
#!/usr/bin/env python3 | |
# encoding: utf-8 | |
""" | |
Revisionist: logs Discord message edits and revisions | |
Copyright © 2017 Benjamin Mintz | |
https://bmintz.mit-license.org/@2017 | |
""" | |
import discord |
This guide assumes you have previous experience with hactool and messing with your NAND. You aren't supposed to blindly copy commands in this, so read before pasting!
Also, the Python sections require Python 2.7 and pycrypto.
sd:/Nintendo/contents/private
in a hex editor./save/8000000000000043
in a hex editor.from Crypto.Cipher import AES | |
from Crypto.Util import Counter | |
import struct | |
""" | |
typedef struct boot_dat_hdr | |
{ | |
unsigned char ident[0x10]; | |
unsigned char sha2_s2[0x20]; | |
unsigned int s2_dst; |
So you want to decrypt switch content ? Well, the good news is that all the tools required to do that are written up! The great news is, since this is crypto we're talking about, you'll have to find the keys. Yourself. Like it's easter.
So here you can find a template of the $HOME/.switch/prod.keys
file that hactool uses to decrypt content. It contains all the SHA256 and location of the keys and seeds, so you can find them yourselves.
Note that all the seeds (the keys that end with _source
) are used along with the master_key_##
to derive an actual key.
If you have somehow obtained the key without the seed, you can rename xxx_source
to xxx_##
(where ## is the master key number) and put your key there.
So you want to decrypt switch content ? Well, the good news is that all the tools required to do that are written up! The great news is, since this is crypto we're talking about, you'll have to find the keys. Yourself. Like it's easter.
So here you can find a template of the $HOME/.switch/prod.keys
file that hactool uses to decrypt content. It contains all the SHA256 and location of the keys and seeds, so you can find them yourselves.
Note that all the seeds (the keys that end with _source
) are used along with the master_key_##
to derive an actual key.
If you have somehow obtained the key without the seed, you can rename xxx_source
to xxx_##
(where ## is the master key number) and put your key there.