Homebrew N3ds faster file transfer speed

[Seita]

Maybe someone already found out about this?
Anyway, if you have a N3ds, you can transfer files to it much fatser. Something up to 3mb/s. Simply load microsd management app from hans using the overclocked speed. There you go

This should be very useful for bigger files.

 

[ihaveahax]

I would suggest, if you're handling large amounts of files, that it might be easier and more reliable to unscrew the back and physically insert the microSD card.

that aside, I'm surprised they wouldn't force 804MHz already on it. it would make the above less necessary (at least for me).

 

[Seita]

Oh no. That's exactly why I use the app. I never want to open my N3ds. More hassle for me and bad in the long run for the cover.

 

[ihaveahax]

Oh no. That's exactly why I use the app. I never want to open my N3ds. More hassle for me and bad in the long run for the cover.

if I'm transferring several gigabytes of data, it's usually faster if the microSD is inside the computer.

 

[Deleted User]

snip

 

[Giodude]

Wow, that's kind of stupid. Really? Overclock? Surprised it wasnt there to begin with.

 

[uyjulian]

If you know you are going to take the cover off often, don't screw in the back.

 

[ihaveahax]

If you know you are going to take the cover off often, don't screw in the back.

the battery is exposed and could fall out though. also this post I made was probably stupid but eh.

 

[uyjulian]

the battery is exposed and could fall out though. also this post I made was probably stupid but eh.

No, I meant, don't take out the screwdriver and screw it in

 

[Acryt]

No, I meant, don't take out the screwdriver and screw it in

This. It stays secure in place without even being screwed in.

 

[ArugulaZ]

I hate that damn back case. It's obvious that Nintendo didn't want anyone having direct access to the Micro SD card, and it's just as clear that later firmware updates will be designed to keep people from loading exploits onto it.

 

[Pedeadstrian]

I hate that damn back case. It's obvious that Nintendo didn't want anyone having direct access to the Micro SD card, and it's just as clear that later firmware updates will be designed to keep people from loading exploits onto it.

What, you think Nintendo designed it that way for the sole purpose of making people say "...meh, not worth it" when it comes to putting launchers in their SD card, even though you can transfer files without even opening it up?

 

[ihaveahax]

I hate that damn back case. It's obvious that Nintendo didn't want anyone having direct access to the Micro SD card, and it's just as clear that later firmware updates will be designed to keep people from loading exploits onto it.

I don't see how the two are related at all. microSD Management doesn't block files.

 

[ArugulaZ]

Couldn't they add file blocking in a later firmware update?

 

[ihaveahax]

Couldn't they add file blocking in a later firmware update?

I am not a lawyer but I'm sure this wouldn't be allowed, much like Nintendo can't make the 3DS delete files unrelated to it (which is why it never deletes boot.3dsx and stuff).

of course I could just be crazy but correct me if that's the case. if they could, why haven't they done it yet?

 

[spoonm]

I am not a lawyer but I'm sure this wouldn't be allowed, much like Nintendo can't make the 3DS delete files unrelated to it (which is why it never deletes boot.3dsx and stuff).

of course I could just be crazy but correct me if that's the case. if they could, why haven't they done it yet?

Too busy trying to figure out a smart way not to let the .3dsx files be run instead of getting rid of them. Wouldn't it also give room for another possible entrypoint? Not a security expert, but more walls = more bricks that can be accidentally left behind.

In other words: make it so the 3DS can never learn .3dsx-ese instead of burning the .3dsx-ese books.

 

[ihaveahax]

Too busy trying to figure out a smart way not to let the .3dsx files be run instead of getting rid of them. Wouldn't it also give room for another possible entrypoint? Not a security expert, but more walls = more bricks that can be accidentally left behind.

In other words: make it so the 3DS can never learn .3dsx-ese instead of burning the .3dsx-ese books.

yeah good luck with that. it's the payload that allows 3dsx files to run, but they haven't been able to stop ninjhax 2.x yet.