Hardware nand flash dump (3ds xl)

[pasc]

I doubt the wiring is off.

This was done by a professional.

He even sent two dumps on disc back to me.

The problem is just that I can't get it to work.

The XL was simple to mod by comparison.

 

[how_do_i_do_that]

It can be as simple as the pinouts used on the SD card adapter that is giving you that error.

 

[kyogre123]

You could check the continuity between the pins of the NAND and the SD card.

 

[junn]

This mod works wonderful on my 3DS XL.


However

My normal 3DS however will only show this in the diskmgmt:

Removable Drive (E:954MB) 954 MB
Write protected Not assigned


and this when trying to read it:

Did anyone have this aswell and can tell me what I'm doing wrong ?

well,i had a similar problem, win32diskimager can't read my 3ds on 2 different laptops.
and also mod my 3ds LL, same thing. win32diskimager just cant read both systems.
updated the usb card,sd card reader drivers, shortened the cables,etc,no dice..
so i tried USB Image Tool,
http://www.alexpage.de/usb-image-tool/
one temper mentioned the software on a different thread, and it's all good.
here's mine.
http://img28.imageshack.us/img28/717/f09o.jpg
http://img545.imageshack.us/img545/2965/5oz4.jpg

got an error after replacing the micro usb cable that goes to the usb sd card reader.
http://img138.imageshack.us/img138/5527/83r3.jpg
but after i reduced the lenght, the error disappeared.

 

[how_do_i_do_that]

well,i had a similar problem, win32diskimager can't read my 3ds on 2 different laptops.
and also mod my 3ds LL, same thing. win32diskimager just cant read both systems.
updated the usb card,sd card reader drivers, shortened the cables,etc,no dice..
so i tried USB Image Tool,
http://www.alexpage.de/usb-image-tool/
one temper mentioned the software on a different thread, and it's all good.
here's mine.
http://img28.imageshack.us/img28/717/f09o.jpg
http://img545.imageshack.us/img545/2965/5oz4.jpg

got an error after replacing the micro usb cable that goes to the usb sd card reader.
http://img138.imageshack.us/img138/5527/83r3.jpg
but after i reduced the lenght, the error disappeared.

Where do you get the female micro usb port board for the 3DS? Yours just wants me to clean up my fugly mess of a mod.

 

[mvmiranda]

Hello,

I'm a new user but I already did this mod on a friend's blue 4.5.0-10u XL. It worked flawlessly.


I just bought a blue Kario Kart 7 bundle (4.3.0-10u) and I'll use Jay.T's (post #399) idea and try to attach, either a mini/micro USB or a molex connector, like he did.

The reason I decided to post is something already discussed here: efuses.

I know someone already mentioned that a way to block you from downgrading from your own NAND is less likely to be done, but what if N1ntendo uses the "presumably" existing efuses in the SoC to prevent you to downgrade to a lower sys version after you upgraded from an "original" cartridge or internet sys version 7 (or something later)?

What are you guys take on this? Do you believe this could be feasible from the company perspective?

Cheers!

 

[Duo8]

Hello,

I'm a new user but I already did this mod on a friend's blue 4.5.0-10u XL. It worked flawlessly.
View attachment 4852View attachment 4851View attachment 4850

I just bought a blue Kario Kart 7 bundle (4.3.0-10u) and I'll use Jay.T's (post #399) idea and try to attach, either a mini/micro USB or a molex connector, like he did.

The reason I decided to post is something already discussed here: efuses.

I know someone already mentioned that a way to block you from downgrading from your own NAND is less likely to be done, but what if N1ntendo uses the "presumably" existing efuses in the SoC to prevent you to downgrade to a lower sys version after you upgraded from an "original" cartridge or internet sys version 7 (or something later)?

What are you guys take on this? Do you believe this could be feasible from the company perspective?

Cheers!

I think if there are such efuses, this wouldn't be possible in the first place.
Could be wrong though.

 

[mvmiranda]

I think if there are such efuses, this wouldn't be possible in the first place.
Could be wrong though. Are efuses software-controlled?

in a nutshell: yes!
Think about bigger consoles, like Xbox 360. Everytime you install a new update, it blows one efuse, that prevent you, along with other techniques, from downgrading. We all know the dash was decrypted and hacked, but you cannot downgrade, even from your own old NAND, if your efuses don't match.

 

[Duo8]

in a nutshell: yes!
Think about bigger consoles, like Xbox 360. Everytime you install a new update, it blows one efuse, that prevent you, along with other techniques, from downgrading. We all know the dash was decrypted and hacked, but you cannot downgrade, even from your own old NAND, if your efuses don't match.

What?

Also, if there are efuses, why didn't they just use it in the first place already? How many efuses there usually are in a CPU?

 

[shinonome]

maybe dumping is using in official repairing centers and they don't want to block it in this reason?

 

[mvmiranda]

What?

Also, if there are efuses, why didn't they just use it in the first place already? How many efuses there usually are in a CPU?

Well, I don't know for sure how many efuses there are in xbox 360 or N3DS, so I can't confirm this info to you. Also, efuses are present in almost any SoC or chip nowadays, that's why I brought this into subject again.

Assuming there are really efuses present in N3DS, the reason the big N didn't use are unknown, as the reasons to not block old unencrypted FW from being installed into PSP in the beginning of the CFW old days was

Anyway, I'm just discussing something that was pretty much obvious that it would be in place but was not, and could **possibly** be done in a future.

 

[Duo8]

maybe dumping is using in official repairing centers and they don't want to block it in this reason?

Efuses prevent downgrading, not dumping.

 

[Duo8]

Well, I don't know for sure how many efuses there are in xbox 360 or N3DS, so I can't confirm this info to you. Also, efuses are present in almost any SoC or chip nowadays, that's why I brought this into subject again.

Assuming there are really efuses present in N3DS, the reason the big N didn't use are unknown, as the reasons to not block old unencrypted FW from being installed into PSP in the beginning of the CFW old days was

Anyway, I'm just discussing something that was pretty much obvious that it would be in place but was not, and could **possibly** be done in a future.

Hmmm... They probably won't use it until downgrading can be done without hardware mod, as I see a lot of people are afraid of opening up their 3DS, let alone soldering

 

[mvmiranda]

Hmmm... They probably won't use it until downgrading can be done without hardware mod, as I see a lot of people are afraid of opening up their 3DS, let alone soldering

Hehe! Yup! it's kind of scary to open such a tiny thing. Of course the XL is easier to do, but a little extra heat from your solder iron could burn a pad or two or you could end up ripping one of the small flat cables.
What about the original 3DS? You need to remove the entire motherboard, that, my friend, for ppl not used to handle these kind of small board, could mean doom!

I'm glad to know that even with 6.3 we're still able to downgrade. Let's hope it continue this way.

Cheers

Guys, I got a:

00F800FE
00000000 00000000
00000400 00000000

but I was able to dump 3 times all equal...

Since this bootloader code was mentioned in page 10 as a "bad" errorcode, what are you guys take on this?

Thanks!

Alright! Turns out that some wire was probably shorting to other one... I changed the conector and tried after the third attempt and now I got this:

00F800EF
FFFFFFFF FFFFFFFF
00000003 00000000

What should I accept as the working one?

PS: I can dump successfully!

PS2:
Interesting! I compared MD5 from the two different errorcodes (00000400 and 00000003) and they are the same...
Now I have 6 NAND dumps (3 from each errorcode) and they all match...

Clues?

 

[pelago]

I've had several different error codes but, like you, have successfully been able to dump (and I've used those same dumps to successfully downgrade, so I know they work.)

 

[mvmiranda]

Thx Pelago!
I'm gonna wrap up here then and close everything...
Will try to flash the same dump and cross fingers hoping everything end up well... If I'm ok, I'll update to the latest sys upd via internet, do a backup and downgrade again.

Thx!

ok!
After the 6 dumps, I turned on the console to see it was ok and it was... phew!
Extracting a diff dump after gives me a different MD5 than the ones I extracted earlier. Since the day changed, I guess that after I boot the console, something changed in the NAND... that's the only logical thing I can think of.

Am I right?

PS: two dumps now gives me the same MD5, but different MD5 than the old dumps... So I guess I'm still fine

Hey guys,

Sorry if I'm being too sticky to this, but I gotta admit: I loved this mod!

I just found out something really interesting.

With the very same wiring, I get different errorcodes based on "how" I do the connection to the PC. I'll explain.
I use a 8 inch long shielded USB cable with 4 terminals and a female connection soldered to the console. At the other end of the cable I use a MicroSD to SD adapter. To onnect the SD part to my console I use a cheap-a$$ multi SD read stuff, china made.


If I connect everything up (cable to console, cable SD to card reader and the card reader to my PC USB) and then I turn on the 3DS, I get the errorcode 00000003. Also the read speed is 2.5MB/s at most.
If I connect the cable to the console and to the card reader, turn on the console, I get the errorcode 00000400. Then I plug the card reader to my console and the speed is also 2.5Mb/s at most
If I only connect the cable to the console and turn it on, I get the errorcode 00000020. Then I plug the rest up, but this time the speed is much faster. It's 5.3MB/s

All of the NAND dumps are the same (MD5 matches). I tested them all and they all work on my console, but indeed the read/write speed count when you're dumping 3 times to be on the safe side.

Cheers!

 

[how_do_i_do_that]

Just bought a spare Red XL on 4.4. Read out nand and also installing a 3dscapture card on main Blue XL





i am adding a female micro usb port on the internally under Select button and wiring up a microusb to SDCARD adaptor (like how capture cards are installed)

[IMG]http://optimize.ath.cx/LL-SPA3/CIMG06981.jpg

Where did you order your female micro usb port, I haven't found anything small enough to fit there.

 

[junn]

Where do you get the female micro usb port board for the 3DS? Yours just wants me to clean up my fugly mess of a mod.

ebay:
http://www.ebay.com/sch/i.html?_trk...kw=micro+usb+female+solder&_sacat=0&_from=R40

or a micro usb with board:
http://www.ebay.com/itm/Micro-USB-B..._USB_Cables_Hubs_Adapters&hash=item1c37c75b5f

 

[how_do_i_do_that]

hmmm, that is a month or more before I can get it in hand and thats just waiting on shipping from either china or the UK.

The one with the board is gonna probably cause some problems, since I would have to remove the pins to get it flush.

gonna have to mull this over how I want to handle this.

 

[pelago]

ok!
After the 6 dumps, I turned on the console to see it was ok and it was... phew!
Extracting a diff dump after gives me a different MD5 than the ones I extracted earlier. Since the day changed, I guess that after I boot the console, something changed in the NAND... that's the only logical thing I can think of.

Am I right?

If you boot up the console at all then shut it down and make a new dump (even on the same day) the dumps will be different. Looks like the console writes something to NAND on every successful boot.