Hacking Injecting Emunand to Sysnand?

  • Thread starter Thread starter Zachers
  • Start date Start date
  • Views Views 3,706
  • Replies Replies 19

Zachers

Well-Known Member
Newcomer
Joined
Jan 3, 2014
Messages
66
Reaction score
18
Trophies
0
Age
27
Location
Georgia
XP
157
Country
United States
I read somewhere that if you inject a emunand into a sysnand, it will be a guaranteed brick. However, later on, it was stated that only happens if the emunand was upgraded from 4.x to 9.x. Here is my situation:
I am trying to be able to use RAM dumps and AR codes and such, and I have upgraded my 3DS' sysnand to 9.2 via my friend's Smash Bros card. Game card updates don't include the browser though, bringing up the need to install it as a spoofed cia. I have a formatted emunand like the person in the forum said, to make it safe. Installed the cia and extracted it. I need to make sure this is safe to do though. There are no other changes besides that.

A: Can I inject this emuNAND into my sysNAND safely?
B: How exactly do I restore a sysNAND backup? I have downgraded before with Gateway, but I don't see an option to restore a NAND.bin anywhere. How do I go about restoring my old 4.x backup if needed?

Any help would be appreciated!
 
I read somewhere that if you inject a emunand into a sysnand, it will be a guaranteed brick. However, later on, it was stated that only happens if the emunand was upgraded from 4.x to 9.x. Here is my situation:
I am trying to be able to use RAM dumps and AR codes and such, and I have upgraded my 3DS' sysnand to 9.2 via my friend's Smash Bros card. Game card updates don't include the browser though, bringing up the need to install it as a spoofed cia. I have a formatted emunand like the person in the forum said, to make it safe. Installed the cia and extracted it. I need to make sure this is safe to do though. There are no other changes besides that.

A: Can I inject this emuNAND into my sysNAND safely?
B: How exactly do I restore a sysNAND backup? I have downgraded before with Gateway, but I don't see an option to restore a NAND.bin anywhere. How do I go about restoring my old 4.x backup if needed?

Any help would be appreciated!

A) There is no safe way to do anything to sysNAND, make sure you have a backup of your NAND at all costs. I can't really help you with the process as I have never attempted this before unfortunately.
B) Two ways. The first is by holding UP on the D-pad while selecting the downgrade feature, the other way (which is the ONLY way if you manage to fuck it up) is to solder a connector to the nand pinouts and flash it.

Good luck!
 
A) There is no safe way to do anything to sysNAND, make sure you have a backup of your NAND at all costs. I can't really help you with the process as I have never attempted this before unfortunately.
B) Two ways. The first is by holding UP on the D-pad while selecting the downgrade feature, the other way (which is the ONLY way if you manage to fuck it up) is to solder a connector to the nand pinouts and flash it.

Good luck!
Thanks for the quick reply!

You need the firm 0/1 from system nand injected into emunand in order to flash it over system nand
Can you PM me with further details? Once I get it working, I'll update the post for anyone else trying the same thing.
 
we will need tests from people with hardware nand backup/restore but i think back when emunand was new, emunand backups was stored in the format with the first sector at the end of the dump like how it was stored on the SD cards, example[2,3,4,1], but modern backup tools rearrange the sectors so that the first sector is actually in the front of the file when its dumped to the PC, example[1,2,3,4]. i believe these backups will work find when written to sysnand, while the earlier [2,3,4,1] backups would fail.
 
we will need tests from people with hardware nand backup/restore but i think back when emunand was new, emunand backups was stored in the format with the first sector at the end of the dump like how it was stored on the SD cards, example[2,3,4,1], but modern backup tools rearrange the sectors so that the first sector is actually in the front of the file when its dumped to the PC, example[1,2,3,4]. i believe these backups will work find when written to sysnand, while the earlier [2,3,4,1] backups would fail.
I have also heard this, which made me think it was closer to being safe. Just wondering if there are any foolproof steps I can take to ensure that I won't get a brick. No matter what I do, I can't find a way to install this one browser .cia on the 9.2 sysNAND. This was all I could think of, but very risky. Don't want to break it when I don't know how to do what DarkKaine said, for if I screw up.
 
I accidentally generated a NAND.BIN from my emunand and injected it at sysnand. It turned out ok, everything worked fine but I had to do a hard mod since my emunand was at 9.5 and I could no longer hack my 3ds
 
  • Like
Reactions: tipsytoto
I accidentally generated a NAND.BIN from my emunand and injected it at sysnand. It turned out ok, everything worked fine but I had to do a hard mod since my emunand was at 9.5 and I could no longer hack my 3ds
Is it difficult to do a hard mod? I've seen a tutorial on how to do it. It seems like something most people couldn't do. Again, why I want to be very careful.
 
Is it difficult to do a hard mod? I've seen a tutorial on how to do it. It seems like something most people couldn't do. Again, why I want to be very careful.
I didn't do it myself, I payed someone to do it for me. But it's as simple as soldering 4 wires to the 3DS PCB, and 4 wires to a SD card adapter. How difficult is it depends what model of 3DS you have. I heard the o3DS XL is the easiest one to mod, while the regular o3DS is more difficult. Of course, you must have good experience to soldering this kind of stuff, otherwise you would be risking your 3ds
 
As long as you're restoring a 9.0-9.2 emunand created from a 9.0-9.2 sysnand its safe. If you restore an emunand updated with gateway from a lower firmware (like 8.1) then yes you'll brick your console.

I advise you this (only if you have a 9.0-9.2 sysnand) :
- Format your emunand
- Update it to 9.2.0-20 with sysupdater
- check if your emunand still boot
- extract your emunand, rename it nand.bin, and flash it.
Then you will have a complete 9.2 update. :)
 
As long as you're restoring a 9.0-9.2 emunand created from a 9.0-9.2 sysnand its safe. If you restore an emunand updated with gateway from a lower firmware (like 8.1) then yes you'll brick your console.

I advise you this (only if you have a 9.0-9.2 sysnand) :
- Format your emunand
- Update it to 9.2.0-20 with sysupdater
- check if your emunand still boot
- extract your emunand, rename it nand.bin, and flash it.
Then you will have a complete 9.2 update. :)
Ah, thank you! I will look into sysupdater now. This way I don't have to worry about the cia file causing the brick, or not working because it is spoofed and maybe not "legit".
 
I've flashed my Emunand a few times onto my sysnand. I've never bricked any of my consoles doing so. From my understanding, it appears that as long as emunand boots and works normally, it should work as a sysnand too. I don't think I've tested 4.x emunand updated to 9.x then flashed though
 
Alright, thanks. After I extract the emuNAND with EmuNAND tool, is there anything I need to do to it, or do I just rename it NAND.bin and flash it? There is a program alongside emuNAND tool in the folder I have, "drag_emunand_here.bat" that says "Adding dummy data" and then makes a REDNAND.bin file. Is this necessary?
 
Did you try to boot into your emunand first ?

And don't use the drag_emunand_here.bat, it was for the old 4.X cfw.
 
I am still installing the cia's. There was an error in one of them for some reason so I had to find and delete that one file.

Edit: Injecting the emuNAND now.
 
Last edited by Zachers,

Site & Scene News

Popular threads in this forum