Hacking [HELP!] Crazy Problems with Friend's O3DSXL

[seijinshu]

My friend had a 16GB SD card that was used for CFW. When he upgraded to a 64GB (The same one as mine) and moved EmuNAND over, Dev Menu and BBM stopped working. We had to make backups of everything and we re-hacked from scratch (from 9.2 sysNAND backup). Now his EmuNAND only sees his legit games. I've tried rxTools, AuReiNAND, and the NANDs are unlinked. We are using the right SD backup, but it only detects legit games. When he got FBI.3dsx loaded, he installed FBI.cia, but it didn't appear.

Help?

 

[samiam144]

My friend had a 16GB SD card that was used for CFW. When he upgraded to a 64GB (The same one as mine) and moved EmuNAND over, Dev Menu and BBM stopped working. We had to make backups of everything and we re-hacked from scratch (from 9.2 sysNAND backup). Now his EmuNAND only sees his legit games. I've tried rxTools, AuReiNAND, and the NANDs are unlinked. We are using the right SD backup, but it only detects legit games. When he got FBI.3dsx loaded, he installed FBI.cia, but it didn't appear.

Help?

It's a known issue, IIRC you must make the SD card free space small enough so that the 3DS can properly read it. For example, place a couple movies on the SD card to get the free space down to about 32GB(?), then see if BBM and Devmenu will work.

 

[seijinshu]

It's a known issue, IIRC you must make the SD card free space small enough so that the 3DS can properly read it. For example, place a couple movies on the SD card to get the free space down to about 32GB(?), then see if BBM and Devmenu will work.

It has never been an issue. SDF works. It was working on my 64gb

 

[astronautlevel]

It's a known issue, IIRC you must make the SD card free space small enough so that the 3DS can properly read it. For example, place a couple movies on the SD card to get the free space down to about 32GB(?), then see if BBM and Devmenu will work.

That's only with 128 gigs of space. 64 gigs is not an issue. Also, it's an issue only if BBM/DevMenu, FBI works fine.

 

[seijinshu]

That's only with 128 gigs of space. 64 gigs is not an issue. Also, it's an issue only if BBM/DevMenu, FBI works fine.

My issue is not with dev menu. It is the games.

 

[Faolan]

Try formatting to 64kb clusters

 

[seijinshu]

Try formatting to 64kb clusters

K. Trying...

 

[Deleted User]

Did you use Decrypt9WIP to restore backup? Also, did you possibly corrupt data on the SD card? I know that my computer corrupted the Nintendo 3DS folder once

 

[DjoeN]

My 64GB SD is formatted this way:

Used software:
- MiniTool Partition Wizard

Formatted as:
- Primary
- FAT32
- 32kb Cluster Size

Next steps in short:
- Get Homebrew Launcher
- Get EmuNand9
- Have a backup of your emunand ready as emunand.bin
- Setup your system to boot into Homebrew Launcher
- Use EmuNand9 to create a new EmuNand partition
- Move your old EmuNand to the new SD with EmuNand9
- Copy all files from your old SD to the new SD.

That should be it

 

[The Real Jdbye]

My friend had a 16GB SD card that was used for CFW. When he upgraded to a 64GB (The same one as mine) and moved EmuNAND over, Dev Menu and BBM stopped working. We had to make backups of everything and we re-hacked from scratch (from 9.2 sysNAND backup). Now his EmuNAND only sees his legit games. I've tried rxTools, AuReiNAND, and the NANDs are unlinked. We are using the right SD backup, but it only detects legit games. When he got FBI.3dsx loaded, he installed FBI.cia, but it didn't appear.

Help?

Delete the "Nintendo 3DS" folder (or just the folder inside it belonging to emuNAND) and copy it over again from the backup. It has solved similar issues for other people, myself included.

 

[seijinshu]

My friend has resolved this by doing a system format and starting from scratch.
Your replies have been about setting it up. It was working, but upon transfer to new card, it went all wrong.

--------------------- MERGED ---------------------------

Delete the "Nintendo 3DS" folder (or just the folder inside it belonging to emuNAND) and copy it over again from the backup. It has solved similar issues for other people, myself included.

Well... We did that many times. Oh well, we got it working anyways