Hacking 3DS NOOB PARADISE - Ask questions here

[Arubaro]

Is there any "proper steps" guide like the extremely detailed A9LHax guide? I really don't want to mess anything up and lose all my stuff.

Some time ago, you had to follow some confusing steps to copy sysnand to emunand, unlink them and make eshop work on emunand.

You had to create your emunand as a clone of your sysnand (that means, two "systems" sharing the SD's extdata folder, they're linked).
To unlink them, you would need to format sysnand (to generate a new extdata folder only for sysnand and unlinking your NNID from sysnand).
The thing is that when you format a system, you're saying to nintendo servers that you will not use that NNID until you relink it into another system or something in a future.
The problem is that you have your NNID on your emunand, so when you go to eshop, you're trying to use a NNID that is not suposed to be in use, hence, an error.
To fix it, you need to format emunand, go to system settings in this now empty emunand and relink your NNID (saying to nintendo servers "hey, I'm using this NNID again"). Once done, reinject your emunand.bin/nand.bin on your emunand and paste the SD content you had when you dumped before all this process.

Now you can simply use tinyformat on sysnand.
With that you can format sysnand (creating a new extdata folder for sysnand) without connecting to internet and without saying to nintendo servers that you will not use the current NNID (because you want to use it on emunand).


I don't know if I have left something behind...

 

[LittleXiao]

Some time ago, you had to follow some confusing steps to copy sysnand to emunand, unlink them and make eshop work on emunand.

You had to create your emunand as a clone of your sysnand (that means, two "systems" sharing the SD's extdata folder, they're linked).
To unlink them, you would need to format sysnand (to generate a new extdata folder only for sysnand and unlinking your NNID from sysnand).
The thing is that when you format a system, you're saying to nintendo servers that you will not use that NNID until you relink it into another system or something in a future.
The problem is that you have your NNID on your emunand, so when you go to eshop, you're trying to use a NNID that is not suposed to be in use, hence, an error.
To fix it, you need to format emunand, go to system settings in this now empty emunand and relink your NNID (saying to nintendo servers "hey, I'm using this NNID again"). Once done, reinject your emunand.bin/nand.bin on your emunand and paste the SD content you had when you dumped before all this process.

Now you can simply use tinyformat on sysnand.
With that you can format sysnand (creating a new extdata folder for sysnand) without connecting to internet and without saying to nintendo servers that you will not use the current NNID (because you want to use it on emunand).


I don't know if I have left something behind...

So I downgrade, back up sysNAND, create a new emuNAND SD by cloning sysNAND, use Tinyformat on sysNAND and somehow Nintendo won't think I have my NNID linked to my sysNAND backup?

 

[Arubaro]

So I downgrade, back up sysNAND, create a new emuNAND SD by cloning sysNAND, use Tinyformat on sysNAND and somehow Nintendo won't think I have my NNID linked to my sysNAND backup?

That's it.
Make sure you backup your SD card when you dump your nand, before using tinyformat on sysnand.

 

[LittleXiao]

That's it.
Make sure you backup your SD card when you dump your nand, before using tinyformat on sysnand.

You mean when I make the emunand partition on SD? I don't think dumping the nand requires a backup, but I guess two backups is better than one. Still wondering how Nintendo doesn't think my NNID is linked to my sysnand backup.

 

[Arubaro]

You mean when I make the emunand partition on SD? I don't think dumping the nand requires a backup, but I guess two backups is better than one. Still wondering how Nintendo doesn't think my NNID is linked to my sysnand backup.

I mean, when you create your emunand you make a backup of your SD card too.
Because once you format your sysnand, you'll generate a new folder where only sysnand will store things (in other words, the SD backup you made will not be read by sysnand anymore) besides, your NNID will not be "turned off"

PD: Sorry, my english is not the best

 

[LittleXiao]

Does PlaiSysUpdater work with 10.7? It gets stuck on "HaxInit..." every time for me.

 

[ghostpotato]

uh-oh. I do not have a Decrypt9 folder on my root.

http://imgur.com/gv9t0AF - this is my setup - I really tried following the guide to the letter

Where did Decrypt9 dump the hs.app?

 

[warriosbest]

No go to the guide that you linked and go to the section that talks about getting the OTP. Basically, ypu downgrade emunand to 2.1 and then flash that over to sysnand, but there's more steps so read closely.

so, i completed part 1 and in Get-Started
If your version is between 9.0.0 and 9.2.0, start on "Part 1 - Homebrew" then skip most of "Part 2 - Downgrading" (more info on that page).

My FW is 9.1.0-20J, so i just need : ?

Copy and merge the 3ds folder from the EmuNAND9 zip to root of your SD card

1. 
   
   
   • Launch the Homebrew Launcher using the entrypoint of your choice (such as menuhax)
   • Open EmuNAND9 (This can sometimes take a few tries)
   • Go to EmuNAND Manager Options, then backup SysNAND to sysNAND.bin
   • Press Select on the main menu to eject your SD card
   • Put your SD card in your computer, then copy sysNAND.bin to a safe location; make backups in multiple locations; this backup will save you from a brick if anything goes wrong in the future (Your backup should match one of the sizes on this page; if it does not, you should delete it and make a new one!)
   • You can delete sysNAND.bin from your SD card after copying it
   • Reinsert your SD card into your 3DS, then press Start to reboot

 

[Just Passing By]

so, i completed part 1 and in Get-Started
If your version is between 9.0.0 and 9.2.0, start on "Part 1 - Homebrew" then skip most of "Part 2 - Downgrading" (more info on that page).

My FW is 9.1.0-20J, so i just need : ?

Copy and merge the 3ds folder from the EmuNAND9 zip to root of your SD card

1. 
   
   
   • Launch the Homebrew Launcher using the entrypoint of your choice (such as menuhax)
   • Open EmuNAND9 (This can sometimes take a few tries)
   • Go to EmuNAND Manager Options, then backup SysNAND to sysNAND.bin
   • Press Select on the main menu to eject your SD card
   • Put your SD card in your computer, then copy sysNAND.bin to a safe location; make backups in multiple locations; this backup will save you from a brick if anything goes wrong in the future (Your backup should match one of the sizes on this page; if it does not, you should delete it and make a new one!)
   • You can delete sysNAND.bin from your SD card after copying it
   • Reinsert your SD card into your 3DS, then press Start to reboot

Sorry what's your question? Are you confused on what to do?

 

[warriosbest]

Sorry what's your question? Are you confused on what to do?

my n3dsll fw is 9.1.0, i need copy/merge EmuNAND9 to MicroSD and start from step 19 ?

 

[Just Passing By]

my n3dsll fw is 9.1.0, i need copy/merge EmuNAND9 to MicroSD and start from step 19 ?

Yes.

 

[warriosbest]

Yes.

edit....

 

[Just Passing By]

edit....

Is it fixed?

 

[warriosbest]

Is it fixed?

forgot insert my MicroSD , now i'm backup SysNAND.bin (1888MB)

 

[warriosbest]

Is it fixed?

Part 4 :

11.Open Decrypt9 (This can sometimes take a few tries), then go to "RedNAND Options", then select the "Health & Safety Dump" option to dump Health & Safety to hs.app (you can use Up and Down / Left and Right to change the name)

I only saw EmuNAND not RedNAND , when i click on emunand->health safety dump - it say : SD is not formatted for EmuNAND, health.....dump : failed

 

[Just Passing By]

Part 4 :

11.Open Decrypt9 (This can sometimes take a few tries), then go to "RedNAND Options", then select the "Health & Safety Dump" option to dump Health & Safety to hs.app (you can use Up and Down / Left and Right to change the name)

I only saw EmuNAND not RedNAND , when i click on emunand->health safety dump - it say : SD is not formatted for EmuNAND, health.....dump : failed

Have you created emunand?

 

[warriosbest]

Have you created emunand?

no, i need create emunand again(from part 3 ) ?

 

[Just Passing By]

no, i need create emunand again(from part 3 ) ?

No you shouldn't... that shouldn't happen. You've gone into Rednand already right?

 

[warriosbest]

No you shouldn't... that shouldn't happen. You've gone into Rednand already right?

yep

7.Update your RedNAND to the latest version using system settings if it is not already (DO NOT ENTER DATA MANAGEMENT OR EXIT SYSTEM SETTINGS AS THIS WILL REBOOT YOU INTO SYSNAND)
8.Reboot into SysNAND (AND I HOLD DOWN BUTTON to boot to homebrew loader-Decrypt9WIP)

 

[Just Passing By]

yep

7.Update your RedNAND to the latest version using system settings if it is not already (DO NOT ENTER DATA MANAGEMENT OR EXIT SYSTEM SETTINGS AS THIS WILL REBOOT YOU INTO SYSNAND)
8.Reboot into SysNAND (AND I HOLD DOWN BUTTON to boot to homebrew loader-Decrypt9WIP)

Alright then. Perhaps it's a bug with Rednand and D9. Try this build of D9:
http://workupload.com/file/Y9KNCIV3