Hacking New 3DS XL Brick after Downgrade from 10.5 to 9.2 Without Backup.

[geocamus]

Hi, i have a new 3ds model 2015, when i try to downgrade to FW 9.2 and reboot not show any video on any of two screens. I think i bricked, also i dont do it a backup, so, i searched that doing a hardmod it can be restore, but need a backup nand.bin, but i dont doing it, cause the console has the original systema without mod. My question is: Do i need to buy it a new mainboard? or use a nand.bin of other new 3ds? to restore my console.

So, i encourage to do the hardmode and well i soldier every wired on every part of the circuit and every pin of the sdcard.
But when i connected to sdreader (without connect to usb PC), I get this error and only turn on the bottom screen and the up screen remains black:

BOOTROM 8046
ERRCODE: 00F800FE
00000000 00000000
00000200 00000000


Sorry for my bad english, but im spanish person.
This are the pictures of my 3ds.

So, if a good option to buy a mainboard? On aliexpress are on $58, i dont spend on shipping. Im considering if i srewed whit this, buy it and replaced. Could i have problem whitout another board?.. For your Information I have a degree on electronic. By the way, the wired cables are enameled and dont make contact each.

 

[Quantumcat]

If you had asked before doing the hardmod I would have suggested just trying to boot without the SD inserted.

 

[CrispyYoshi]

First of all, this thread belongs here: http://gbatemp.net/forums/3ds-console-accessories-and-hardware.200/

In any case, if you never had a NAND.bin in the first place, the hardmod won't save your 3ds from a brick. It's gone for good, and no, you can't flash a NAND.bin from someone else's 3DS, because they are tied to the system they were dumped from (with publicly known knowledge, at least).

How did you brick it, anyway?

 

[geocamus]

If you had asked before doing the hardmod I would have suggested just trying to boot without the SD inserted.

That is the firt thing i doing it. And dont work!

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

First of all, this thread belongs here: http://gbatemp.net/forums/3ds-console-accessories-and-hardware.200/

In any case, if you never had a NAND.bin in the first place, the hardmod won't save your 3ds from a brick. It's gone for good, and no, you can't flash a NAND.bin from someone else's 3DS, because they are tied to the system they were dumped from (with publicly known knowledge, at least).

How did you brick it, anyway?

I imagine that, well i try to downgrade from 10.5 to 9.2 and i confuse by my mistake to put on the sdcard the files that has the name: DOWNGRADE 10-6 old3ds + 2ds USA and my is new 3ds not old3ds, again my mistake to confuse the files.

 

[CrispyYoshi]

I imagine that, well i try to downgrade from 10.5 to 9.2 and i confuse by my mistake to put on the sdcard the files that has the name: DOWNGRADE 10-6 old3ds + 2ds USA and my is new 3ds not old3ds, again my mistake to confuse the files.

Yes, if you BSOD-bricked your N3DS using an O3DS downgrade pack, a hardmod will not be able to fix your system unless you already have a NAND.bin from the N3DS.

 

[GerbilSoft]

BOOTROM 8046
ERRCODE: 00F800FE
00000000 00000000
00000200 00000000

Did you actually try to take a NAND backup with the hardmod, or even read the description for hardmods? That error is *expected* when you have the SD adapter connected to a reader and turn on the 3DS. https://www.3dbrew.org/wiki/Bootloader#Boot_ROM

EDIT: ...is that *uninsulated* wire connected between the 3DS and the SD adapter? That's a terrible setup; I recommend redoing it with insulated wire.

 

[invaderyoyo]

Did you try recovery mode?

 

[CrispyYoshi]

Did you actually try to take a NAND backup with the hardmod, or even read the description for hardmods? That error is *expected* when you have the SD adapter connected to a reader and turn on the 3DS. https://www.3dbrew.org/wiki/Bootloader#Boot_ROM

EDIT: ...is that *uninsulated* wire connected between the 3DS and the SD adapter? That's a terrible setup; I recommend redoing it with insulated wire.

Judging from the bootrom error code, the wires are not properly connected to the NAND. Also, even if they succeeded, the hardmod will not be able to save them from a brick unless they already have a NAND dump from that 3ds.

Did you try recovery mode?

Bootrom BSOD brick can't even get to the OS, so that won't work. EDIT: Well actually nevermind, they'd have to disconnect all their solder work to test that though.

Now that you mention it, if Recovery Mode can in-fact put them on a clean 11.0, they will be able to hardmod to attempt the downgrade again, if they have a hax game. This is assuming that SAFE_FIRM had not been touched by the o3ds downgrade pack in sysupdater.

 

[geocamus]

Did you actually try to take a NAND backup with the hardmod, or even read the description for hardmods? That error is *expected* when you have the SD adapter connected to a reader and turn on the 3DS. https://www.3dbrew.org/wiki/Bootloader#Boot_ROM

You mean that the error i have, is that the page describe?
00F800FE 00000000 00000000 00000200 00000000 ----- Error when having SD-card reader connected to NAND during boot.

Well, i dont try yet to doing the nand backup, and i dont conected to USB PC yet. Finish the hardmod and conected to sd reader, onlly that. When i disconected from sdreader, no one of the two screens turn on.

 

[GerbilSoft]

Judging from the bootrom error code, the wires are not properly connected to the NAND. Also, even if they succeeded, the hardmod will not be able to save them from a brick unless they already have a NAND dump from that 3ds.

3dbrew lists that specific code as "Error when having SD-card reader connected to NAND during boot."

Either way, since the system was downgraded with the wrong FW and there's no backup, there's probably no solution here.

 

[invaderyoyo]

Judging from the bootrom error code, the wires are not properly connected to the NAND. Also, even if they succeeded, the hardmod will not be able to save them from a brick unless they already have a NAND dump from that 3ds.


Bootrom BSOD brick can't even get to the OS, so that won't work. EDIT: Well actually nevermind, they'd have to disconnect all their solder work to test that though.

Now that you mention it, if Recovery Mode can in-fact put them on a clean 11.0, they will be able to hardmod to attempt the downgrade again, if they have a hax game. This is assuming that SAFE_FIRM had not been touched by the downgrading tool.

But that's because of a bad mod, no? If he undoes the mod isn't there a chance?

 

[GerbilSoft]

Yowikipediau mean that the error i have, is that the page describe?
00F800FE 00000000 00000000 00000200 00000000 ----- Error when having SD-card reader connected to NAND during boot.

Well, i dont try yet to doing the nand backup, and i dont conected to USB PC yet. Finish the hardmod and conected to sd reader, onlly that. When i disconected from sdreader, no one of the two screens turn on.

You need to redo the mod using insulated wire. Those wires are touching each other, which *will* cause data corruption if you try a backup or restore.

Either way, I'm not sure if there's a way to fix a wrong-FW error if you didn't have any initial backups.

 

[CrispyYoshi]

3dbrew lists that specific code as "Error when having SD-card reader connected to NAND during boot."

Either way, since the system was downgraded with the wrong FW and there's no backup, there's probably no solution here.

You are right, my bad. (Mine works despite showing a different error code, strange. I'll have to double-check my error code whenever mine is connected)

But that's because of a bad mod, no? If he undoes the mod isn't there a chance?

Yes, there is definitely a chance! This is the only solution they can try at the moment, really. (Assuming they do not have a NAND.bin from that 3ds)

 

[geocamus]

Did you try recovery mode?

Yeah, dont work!

Judging from the bootrom error code, the wires are not properly connected to the NAND. Also, even if they succeeded, the hardmod will not be able to save them from a brick unless they already have a NAND dump from that 3ds.


Bootrom BSOD brick can't even get to the OS, so that won't work. EDIT: Well actually nevermind, they'd have to disconnect all their solder work to test that though.

Now that you mention it, if Recovery Mode can in-fact put them on a clean 11.0, they will be able to hardmod to attempt the downgrade again, if they have a hax game. This is assuming that SAFE_FIRM had not been touched by the o3ds downgrade pack in sysupdater.

Could you be more specific?.. Some tutorial for doing that?

 

[bowser]

Even with a hard mod you cannot fix your 3ds. Very slim chance that recovery mode will work but you have to remove the hard mod.

 

[invaderyoyo]

You need to redo the mod using insulated wire. Those wires are touching each other, which *will* cause data corruption if you try a backup or restore.

Either way, I'm not sure if there's a way to fix a wrong-FW error if you didn't have any initial backups.

He's using enameled wire. If he did the mod correctly, the problem isn't the wire.

 

[GerbilSoft]

He's using enameled wire. If he did the mod correctly, the problem isn't the wire.

Bah, didn't see that in the first post. In that case, the mod might be working properly, and the question is what to do next.

 

[GraFfiX420]

That wire is insulated, it's just a really small gauge. As others have suggested, I would try recovery mode:

Hold A+R+L+Up(DPad) and then power on the system.

If you can recover, you will be on 11 so will need a solid entry point. The error you're seeing while the SD is connected is normal, and the hardmod is most likely fine.

 

[CrispyYoshi]

Could you be more specific?.. Some tutorial for doing that?

Disconnect your 3ds from the SD connector so it boots up "like normal", and hold L+R+Up+A as you boot up.

If it continues to hang on a black screen, then you cannot do anything to fix that system for now...

If you manage to enter the Recovery Menu, use it to update to 11.0, then use your hardmod to downgrade your NATIVE_FIRM and then use a haxgame to run the downgrader again, using the correct 9.2 N3DS downgrade pack: https://github.com/Plailect/Guide/wiki/Hardmod-Downgrade

 

[geocamus]

You are right, my bad. (Mine works despite showing a different error code, strange. I'll have to double-check my error code whenever mine is connected)


Yes, there is definitely a chance! This is the only solution they can try at the moment, really. (Assuming they do not have a NAND.bin from that 3ds)

I mean, there is a chance to recover my 3ds?.. I mean recover the FW?