ok it looks like there *might* be a short between 2 of the legs on the resistor array next to the loose circled component...
the one labled RA1
Looks a little bit more cleaned up now and a multimeter doesn't show the two as being connected anymore but still I'm getting the same thing.
hmmm struggling to see anything else on there.....seeing as that post i linked said the 3ds still worked without c154,,,,,,maybe just try lifting one of the sides to see if that's causing issues....other than that im kinda out of ideas
Pulled it and still nothing. I guess I can try sending it to someone more confident in this.
It was mentioned to me it might be possible to cut the traces for those pads and then just use alternate points to force erase/flash a new nand.
It was mentioned to me it might be possible to cut the traces for those pads and then just use alternate points to force erase/flash a new nand.
OK, I have done a couple restores that worked great. I just have a couple questions. I noticed that I don't always get the same error codes I have seen about 3 or 4. Is that normal? Every dump from different codes is the right size and viewing in a hex editor shows the unencrypted block starting at 0x4000 so I assume the codes don't matter much.
Also I assume that as long as I always keep my confirmed working backups I am safe that I can never be permanently bricked by a bad flash. Even if I end up flashing a bad backup somehow I can just hookup again and flash a known working one.
My assumption being that nothing is on the NAND that is really needed to get the 3DS booted to the blue screen, is that right?
Also I assume that as long as I always keep my confirmed working backups I am safe that I can never be permanently bricked by a bad flash. Even if I end up flashing a bad backup somehow I can just hookup again and flash a known working one.
My assumption being that nothing is on the NAND that is really needed to get the 3DS booted to the blue screen, is that right?
From what I have gathered the error codes generally depend on the card reader, like my PC card reader generally gives a 400,whilst the usb one.I used gives somewhat random codes, if I had to guess it's probably down to how long the pc takes to take control of the nand or something like that, but yeah the codes aren't set in stone, but I think the most common is 00000400, as long as it's working I think it's all good
And yeah If you flash a bad dump you can.just overwrite it with a good one
And yeah If you flash a bad dump you can.just overwrite it with a good one
So I was able to solder everything properly but I just can't get my computer or any of my other computers to recognize the sd adapter that I'm using. I've tried two different adapters to no avail. Also do I have to use an external sd card reader to recognize it (currently using internal readers)? I do get the blue screen when I plug it in but it just won't recognize.
You can dump the nand flash from any 3DS or 2DS with any firmware version (as long as it isn't GW-bricked). But it only makes sense if the firmware version you dump is worth restoring. Generally, any firmware version 4.50 or lower is worth dumping.
If you love hardware hacking your 3DS, I'd advise you to make the dump anyway, because it's coded with a machine specific key, which means that once a 3DS is bricked, you can't restore the dump from another 3DS on it, that simply doesn't work. When killing your nand, an earlier dump from the same 3DS is your only means of recovery.
You don't need to know the coded key and currently there's no way to retrieve it from your 3DS (and there probably never will be, because it's strongly encrypted). But as long as you have a nand dump, you can always restore it, you don't need the key for that.
Hi! I've just ended moding my 3DS Xl, but after that strange thig happens - It just can't read SD card. I've checked my wires - there is no short, but something is wrong. Maybe I've damaged motherboard, because I tried accidently to screwdrive too big screw ang it made a hole in case, but seems that everything is OK, because there's no screw, which can make hole in motherboard :/ I can't open it now - one of the screws is damaged and I just cant get rid of it. I will try to do something tomorrow. Anyone have an idea what might happend?
EDIT: I've soldered one point really high temperature (325C?) Could that damage something. Tommorow I'll check oneof chips, because I've shorted its pins accidently, but I was sure I've repaired it...
EDIT: One more thing - when I tried to use flashcard's exploit with and without SD card instead of getting just black screen - which is normal when there's no card- I got kicked to system menu and got an error. Similiar error saying that SD card apps cannot be loaded I'm getting on system startup. Console still recognises card, but just can't read it's content :/
EDIT: I've soldered one point really high temperature (325C?) Could that damage something. Tommorow I'll check oneof chips, because I've shorted its pins accidently, but I was sure I've repaired it...
EDIT: One more thing - when I tried to use flashcard's exploit with and without SD card instead of getting just black screen - which is normal when there's no card- I got kicked to system menu and got an error. Similiar error saying that SD card apps cannot be loaded I'm getting on system startup. Console still recognises card, but just can't read it's content :/
Is it still starting normally when you remove your sd adapter from the cardreader? (No need to desolder the wires, just pull the card and power on the 3DS)
If the 3DS doesn't start anymore, there's a chance you damaged something.
If the 3DS doesn't start anymore, there's a chance you damaged something.
Similar threads
] On Guard 
