Homebrew sd card need a little help please

  • Thread starter Thread starter hamodii_87
  • Start date Start date
  • Views Views 1,436
  • Replies Replies 12
  • Likes Likes 1

hamodii_87

Member
Newcomer
Joined
Nov 10, 2016
Messages
15
Reaction score
5
Trophies
0
Age
39
XP
508
Country
dears

i have my n3ds xl qith luma i think the latest update

\i opened it and clean it now in will turn only blue light with black screen for both screens without yellow light
i was thinking its ok use my sd card in another new 3dsxl ?? and how ??
 
  • Like
Reactions: NoNAND
You don't have to put the SD card in another system. That's now how CFW gets transfered.
First thing first plug it in to your PC and see if it's corrupted or not. If it is then you should format it with guiformat on FAT32+32KB cluster size to prevent data issues.
While at it grab h2testw to do a checkup on your card whether It's a fake or not.

By open it did just open it as in just unscrew the back cover and take out the SD card or you did further teardowns?
 
You don't have to put the SD card in another system. That's now how CFW gets transfered.
First thing first plug it in to your PC and see if it's corrupted or not. If it is then you should format it with guiformat on FAT32+32KB cluster size to prevent data issues.
While at it grab h2testw to do a checkup on your card whether It's a fake or not.

By open it did just open it as in just unscrew the back cover and take out the SD card or you did further teardowns?
yeah i opened it and teardowns it to clean the down screen then put everything together

my sd card is fine i can see all the files in my pc
thats why i want it in another n3ds if it possible ?
 
  • Like
Reactions: NoNAND
yeah i opened it and teardowns it to clean the down screen then put everything together

my sd card is fine i can see all the files in my pc
thats why i want it in another n3ds if it possible ?
Don't give up on your current 3DS, A ribbon cable might be loose.

As per that question. You can use it in another 3DS just fine. Keep note however that you'll have to start fresh with the B9S and Luma installation.
Find out more about it here
http://3ds.hacks.guide
 
Don't give up on your current 3DS, A ribbon cable might be loose.

As per that question. You can use it in another 3DS just fine. Keep note however that you'll have to start fresh with the B9S and Luma installation.
Find out more about it here
http://3ds.hacks.guide


thanks for the help

but will i lose everything ??
 
  • Like
Reactions: NoNAND
thanks for the help

but will i lose everything ??
For one the games that were on the previous system won't show up on your new one.
Next, save files (assuming you didn't back them up with Checkpoint) will be gone too.
Hopefully you didn't progress that far in games on your old 3ds.
 
  • Like
Reactions: Deleted User
For one the games that were on the previous system won't show up on your new one.
Next, save files (assuming you didn't back them up with Checkpoint) will be gone too.
Hopefully you didn't progress that far in games on your old 3ds.


i think i didnt do checkpoint to my save files and yes i progress alot :(

so its mean no use for my sd card in my new 3ds
 
  • Like
Reactions: NoNAND
i think i didnt do checkpoint to my save files and yes i progress alot :(

so its mean no use for my sd card in my new 3ds
If you're concerned about your saves then don't move on to the new 3ds.
Have it someone repair it for you if you're having a hard time with it.
 
Unless you have a previously backed up SysNAND *.bin image or essential.exefs from the n3DSXL, you won't be able to reuse the contents from its Nintendo 3DS folder on your n3DS. This is due to console unique encryption, which can only be decrypted with a matching movable.sed from the n3DSXL.

Edit - If you find the n3DSXL's movable.sed, do not inject it to the n3DS.

What you should do instead is mount the Nintendo 3DS folder with ninfs using the movable.sed and copy the decrypted contents of that folder. You can rebuild titles into CIAs in GodMode9 with the decrypted copy.
To backup the saves, you'll need to use 3ds-save-tool.
 
Last edited by TurdPooCharger,
  • Like
Reactions: hamodii_87
Unless you have a previously backed up SysNAND *.bin image or essential.exefs from the n3DSXL, you won't be able to reuse the contents from its Nintendo 3DS folder on your n3DS. This is due to console unique encryption, which can only be decrypted with a matching movable.sed from the n3DSXL.

Edit - If you find the n3DSXL's movable.sed, do not inject it to the n3DS.

What you should do instead is mount the Nintendo 3DS folder with ninfs using the movable.sed and copy the decrypted contents of that folder. You can rebuild titles into CIAs in GodMode9 with the decrypted copy.
To backup the saves, you'll need to use 3ds-save-tool.

i think i have the previously up sysnand image , but about the movable.sed i dont know where it save in the sd card?
if i find it can you provide em with faqs on how to do it ?
 
i think i have the previously up sysnand image , but about the movable.sed i dont know where it save in the sd card?
The movable.sed is a file that comes from the 3DS internal memory. It is not created on the SD card except when it's copied or dumped by either backing up the SysNAND *.bin image, essential.exefs, or that individual file.

In GodMode9, this file is found at:
  • [1:] SYSNAND CTRNAND/private/movable.sed
Only the movable.sed with the correct 16 bytes KeyY can decrypt whichever Nintendo 3DS folder that *.sed was tied to.
if i find it can you provide em with faqs on how to do it ?
I'm reluctant to go into details helping with decrypting and backing up the Nintendo 3DS folder. This type of data recovery is one of hardest 3DS issues to tackle per an individual case because of how many unknown factors there are and all the hoops one has to go through to get back stuff.

Even if you find the n3DSXL's movable.sed, that doesn't guarantee it contains the intact KeyY that matches set to the Nintendo 3DS folder's 32-char <ID0> subfolder.
You can run into the trouble that the KeyY in the movable.sed does not contain the exact 16 bytes key. A (mostly) intact key can be corrected by brute forcing with the gm9 script, CTRTransfer (Type D9) - Fix movable.sed KeyY.

Matters can be made worse if your n3DSXL was involved in a System Transfer where it received its Nintendo 3DS folder from another 3DS/2DS; this makes it neigh impossible to find the correct key. * Last ditch effort would be recreating the KeyY from scratch by finding someone who added your n3DSXL to their Friend's List, have that person (who has CFW) dump your Friend Code info that has the 1st half of the KeyY using seedstarter, and then bruteforce the 2nd half with https://bruteforcemovable.com/.

Read up the ninfs thread in how to use that program. You'll need to install that with the accompanying boot9.bin dumped from a 3DS, mount the NAND image, wait for the program to finish loading it, extract the movable.sed from either the essential.exefs or ctrnand_full.img, (attempt) mounting the Nintendo 3DS folder with said movable.sed, copy the decrypted contents, backup the saves with 3ds-save-tool, and then search the TMD files of that decrypted copy in GodMode9 to rebuild into CIAs.
 
Last edited by TurdPooCharger,

Site & Scene News

Popular threads in this forum