Yeah, just try adding a bit of pressure to the case, and make sure it lines up perfect when closed
Hmm. Is it confirmed that FFFFFFFF FFFFFFFF 00000007 00000000 *definitely* means CMD and DAT2 are connected? Because I just bridged the CMD and DAT0 with the tweezers (according to this image, which I've been working from) directly rather than through the adapaters and still got that error rather than the 200 error which you're apparently supposed to get from CMD+DAT0. So something strange seems to be going on.
Oh, a bit hard to see in that pic. In that gap between the first third wires I've cut off the end of the second wire and it's soldered onto that rail going across there, connecting to the pin.In your pic it doesn't look like you've got your GND pogo soldered but I could be wrong. I believe it was said somewhere in the forums that it doesn't even matter if GND truly needs to be connected but again...I could be wrong. I would think not having it soldered would be dangerous.
Damn good job on your mod by the way.
I've tested the full connection, there's no problems there. Current makes it all the way through from the SD adapter to the pins.try wiring the SD adapter straight to the pogo pins, see if there is an issue with the ribbon cable,
In your pic it doesn't look like you've got your GND pogo soldered but I could be wrong. I believe it was said somewhere in the forums that it doesn't even matter if GND truly needs to be connected but again...I could be wrong. I would think not having it soldered would be dangerous.
Damn good job on your mod by the way.
i have knocked the SD adapter out during writing, just plugged it back in and restarted....no perma brickYeah, great job but with any low level flashing, it being not soldered onto the board runs the risk of disconnection mid flash which should definitely perma-brick your 3ds unless you jtag it or something.
When i did mine i thought of making the cuts of the pcb attach to the bottom case protuberances, like Lego pieces, but I soon gave up as it would be a pain in the ass to get the position right, so I just decided to go with a piece of duct tape to hold it in place, that way can clearly see if the pogo pins are aligned with the 3ds pcb and when the shell is closed it will not move away, maybe that's the problem ur having...? I didn't have any problem with the plastic lump tho, didn't even notice if there was one there, everytime I tried to read the nand, windows never failed once to detect and read correctly.I kinda went and tried resoldering the three vertical pins so they were a bit better aligned, since it looked like they weren't quite hitting the spots properly. Got them done really nice, exactly 2mm apart at the ends. Aaaaaaand seem to have buggered something up in the process, since now I can't make it trigger the CMD+DAT0 error at all. Oops
The annoying thing is that I propped up the board to have it sitting out from the case but perfectly flat, just so I could better see that the pins align with the pads. Still really hard to do but it looked like they were good. But now it acts like they aren't at all. Although there is that small lump of plastic on the back of the case (injection point I think?), which irritatingly sits right where one of the pins has to go so there's no drilling a hole in the board to avoid it. Dunno if it makes that much of a difference in angling of the board, but it's a possibility I guess.
yeahFrom what I understand it's possible to downgrade a 3DS as long as you have a backup of it's NAND from that firmware? So if I was to perform this mod, back up my NAND at it's current fw version (6.3.0-12E), I could then update to play newer 7.x games and if an exploit for 6.x is ever discovered I could flash back my backup and take advantage of it? Is this correct?
Shit. Shit. Shit. Shit. I've gone and snapped the ground wire on the ribbon cable where it joins to the board.
Shit.