Separate names with a comma.
Discussion in '3DS - Flashcards & Custom Firmwares' started by Kwongger, Jan 23, 2015.
Can't seem to find a guide. This is possible, correct?
Dude no, if you bricked your console without a backup you cannot fix it, only nintendo can and possibly won't if the nature of the bricking was with gateway or such
Depends on the brick.
If it was just the eMMC being locked it can be unlocked via Raspberry Pi - but it's far from a windows solution.
If you f'd it up via downgrade or other method - your only option is restoring from a backup via flashing.
There are people doing it.
I didn't brick mine. I saw that it's being done by some websites, and was curious as to how they are doing so.
Can you please link these websites - interested to see what they're doing.
Without a backup, it's impossible as every 3DS has a per-console encryption key that is unique. Due to this, it is impossible to fix, and honestly, I even doubt Nintendo would be able to fix it without doing something drastic such as flashing a new encryption key (if that's even possible - e.g. not read-only)
Ah, I now see that this is a different situation than a standard brick.
Yes - that's what I linked it my first post. That's a locked eMMC. But still requires a Raspberry Pi to be connected to unlock it.
Haha, sorry. Last time I delved into this was in the early 00's
Even still, OP is asking for a solution using Windows OS, there is none. The market is mostly using Unix/Linux code so unless he wants to learn he will have to pay someone to try to unbrick it, which is impossible without a backup of his own NAND dump.
To quote what I said earlier
"I didn't brick mine. I saw that it's being done by some websites, and was curious as to how they are doing so."
Its impossible to unbrick without a backup of your own NAND dump. You cannot use another NAND dump because the console has its own unique ID.
Also already stated. You're late to the party dude.
To quote what I typed earlier AGAIN;
'Ah, I now see that this is a different situation than a standard brick."
I know your already aware of the situation now, but just to clarify in case someone finds this thread in the future
flashing a bad nand/cia or whatever will result in a blackscreen brick(console will power on, but screen remains black)....only way to recover from this type is with a valid working nand dump from that specific console, this type of brick can be recovered using a hardware nand mod and a standard computer windows/mac etc, by writing a valid nand dump back to the nand as the nand is still fully functional, the FW is just not usable by the 3ds
old launcher files such as R4 gold deluxe,3dslink,orange 3ds, FW's 3.1,3.2, and GW 2.0b2, these launcher are known to brick consoles by purposefully locking the nand which results in a bootrom error,this is often referred to as a BSOD(stupidly as B could stand for blue or black, screen of death, but is mostly referring to blue) the only way currently (and probably ever as they don't really happen no more unless someone purposefully hunts down an old FW, so nobody is likely to develop any new methods) is using a raspberry pi A or B (not the A+ or B+) and a hardware mod to manually unlock the nand, this cannot be done really on windows as the nand has to be communicate in via a sort of vendor mode to issue the unlock command, i dont think there is any SD readers that allow this level of communication to the SD interface from within windows, anything like that would be dependent on specific card readers and custom made drivers.....which would be a lot of effort when the raspeberry pi/arduino allows this kind of feature to be used with their default hardware for relatively cheap
TL;DR black screen can be fixed with SD reader and a valid nand backup, blue screen brick needs a raspberry pi, and in most cases will not need a nand backup
I"m clarifying it AGAIN for others who will search for something similar to your question. Maybe you should think about that.