Hacking 2DS Doesn't Work; Dropped Mid-Boot (Help)

[Kwyjor]

What do you mean, soldered in a microSD card reader? That never happened.

Then what exactly did happen? Because that thread I linked to is the principal guide for hardmodding. That is why I am not sure if that is what you mean by "hardmodding". It has been a highly unusual procedure for several years now.

 

[Kwyjor]

@luckyboy66666666, the reason your o2DS won't boot without the SD card inserted (ie, blue LED turns on and then off) is because CTRNAND Luma3DS is missing.

Apparently the light in question is the blue power light and not the blue notification light, as per the second post in the thread.

 

[luckyboy66666666]

Then what exactly did happen? Because that thread I linked to is the principal guide for hardmodding. That is why I am not sure if that is what you mean by "hardmodding". It has been a highly unusual procedure for several years now.

The person who modded my 2DS used a set of six wires that were connected to each other via a plug at the end. They soldered four onto the motherboard and plugged that directly into the computer. They didn't need to use an SD card. (At least, I don't think so. It's been a few years since I saw it happen.) When they turned on the 2DS to put CFW on it, it showed the exact same boot error as you would see in a hardmod guide. Then, they injected the custom firmware downloaded from here. At the time, my 2DS was at the firmware version 11.8.0.

 

[TurdPooCharger]

Apparently the light in question is the blue power light and not the blue notification light, as per the second post in the thread.

Maybe the light he's seeing are the Blue Screens of Death?

The person who modded my 2DS used a set of six wires that were connected to each other via a plug at the end. They soldered four onto the motherboard and plugged that directly into the computer. They didn't need to use an SD card. (At least, I don't think so. It's been a few years since I saw it happen.) When they turned on the 2DS to put CFW on it, it showed the exact same boot error as you would see in a hardmod guide. Then, they injected the custom firmware downloaded from here. At the time, my 2DS was at the firmware version 11.8.0.

Holup.. Do you mean when your turn on the o2DS, you're greeted with bootrom 8046 error? Like this:

Can you verify what's the readout for the row right under 00F800EE? This would be the second-to-last row (not the last row).

• If you see FFFFFFFF FFFFFFFF or values that have more FFs, your o2DS has a software bricked firmware.
• If you see 000000000 000000000 or values that have more 00s, the o2DS has a hardware bricked NAND chip (eMMC).

 

[luckyboy66666666]

Holup.. Do you mean when your turn on the o2DS, you're greeted with bootrom 8046 error? Like this:

Can you verify what's the readout for the row right under 00F800EE? This would be the second-to-last row (not the last row).

• If you see FFFFFFFF FFFFFFFF or values that have more FFs, your o2DS has a software bricked firmware.
• If you see 000000000 000000000 or values that have more 00s, the o2DS has a hardware bricked NAND chip (eMMC).

I was saying that's what it looked like when the person hardmodded it for me. I don't get anything like that right now. Just nothing. The screen isn't even lighting up.

 

[luckyboy66666666]

Welp, couldn't resurrect it after all. Ended up buying a new 2DS. Thanks for all the help, guys.

 

[User154]

Then what exactly did happen? Because that thread I linked to is the principal guide for hardmodding. That is why I am not sure if that is what you mean by "hardmodding". It has been a highly unusual procedure for several years now.

It sounds like his acquaintance used a JTAG probe, which generally speaking is the 'proper' way to use test points. While I don't know a huge amount about usage with the 2/3DS specifically I would imagine using this method would have allowed b9s to be installed directly without the need to pull the whole NAND, patch it, and reflash.


Using an SD adapter capable of 1 bit data transfer is a hacky way to mount an eMMC. It just happens to be cheap, easy, and (If we know the pinout) does not require any specialist hardware.