- Joined
- Dec 18, 2015
- Messages
- 313
- Reaction score
- 102
- Trophies
- 1
- Location
- Hellfire Peninsula
- XP
- 402
- Country

You certainly need to unplug those before doing anything with the pcb.Without removing any ribbon cables?

You certainly need to unplug those before doing anything with the pcb.Without removing any ribbon cables?

How do i remove them with out ripping them? Is there a image to which ribbon cables i need to remove to flip the mother board to the other side?You certainly need to unplug those before doing anything with the pcb.

You don't rip them, you free them by pulling these into release position. And pull the cable.How do i remove them with out ripping them? Is there a image to which ribbon cables i need to remove to flip the mother board to the other side?


Refer to my last edited post.Cant see the images, just says [img/]


Yeah I get 400 too. Even though 3dbrew people wrote it's an error when 3ds can't find nand.i think the error should be 0400 instead of 0200 in the 3rd line
and why are you using all the data lines? data0 is enaugh

The wires are actually soft and bend easily. I'm more scared not to brake the wires. It's from nexus 7 usb cable.ok
the wires you are using are thick , just be carefull when assembling your n3ds to not rip off the test popints you soldered your wires to....also i have an idea about those card readers that can read o3ds nand , but not n3ds...will test it and report tomorrow if i suuceed

Haha, happy i'm not the only one with this problemGot myself an adapter which is Transcend P8 TS-RDP8K.
The error which bootloader shows is supposedly correct unlike my laptop reader.
00F800FE
00000000 00000000
00000200 00000000
Afaik it's the only error that's supposed to show if hardmod was successful and the modded sd slot was inserted into card-reader before boot.
Win32 disk images still wouldn't recognize 3ds.(launched with admin privileges)
Tomorrow will try to swap drivers and whatnot.
Cheers.

I feel you brother.Haha, happy i'm not the only one with this problem
N3DSXL does everything like it should be, but none of my computers recognize the nand as drive (while it works perfect with my other O3Ds systems.)
Anyway shipping it out today to @gamesquest1 to get it look over, since it's bricked the same way as you (something got wrong with the xorpads ended up writting a faulty sysnand.bin to nand.

CLK is located here -I don't think it would, as this is CLK.