huh, I always thought they were different in some way. The more you knowThat's weird, because I think this should work normally. There is no real difference between the SysNAND and EmuNAND aside from their location.
huh, I always thought they were different in some way. The more you knowThat's weird, because I think this should work normally. There is no real difference between the SysNAND and EmuNAND aside from their location.
Yeah, people used the trick to write their EmuNAND to SysNAND (and vice versa) to accomplish a few things, like downloading patches from the eShop even though EmuNAND didn't support eShop at that time.huh, I always thought they were different in some way. The more you know
Oh, I always though they'd updated their sysNAND and kept the data on the SD card. Is it because the update data and eshop purcahses are tied to NAND, not just the machine? Or maybe people have just meant the NAND all along but used 'tied to the machine' for convenience?Yeah, people used the trick to write their EmuNAND to SysNAND (and vice versa) to accomplish a few things, like downloading patches from the eShop even though EmuNAND didn't support eShop at that time.
Well, it's technically tied to the NAND, but since the NAND is specific to your device (It won't work on any other 3DS), effectively it's tied to your 3DS.Oh, I always though they'd updated their sysNAND and kept the data on the SD card. Is it because the update data and eshop purcahses are tied to NAND, not just the machine? Or maybe people have just meant the NAND all along but used 'tied to the machine' for convenience?
So since sysNAND andd emuNAND are byte for byte copies, wouldn't eShop purchases work on both. From what I've read on here is that purchases made on one type of NAND do not work on the other?Well, it's technically tied to the NAND, but since the NAND is specific to your device (It won't work on any other 3DS), effectively it's tied to your 3DS.
It's not like that. It's that if you purchase something on, say, your EmuNAND, then it will store the purchase ticket on the EmuNAND. Similarly, if you purchase something on SysNAND, then it will store the purchase ticket on the SysNAND.So since sysNAND andd emuNAND are byte for byte copies, wouldn't eShop purchases work on both. From what I've read on here is that purchases made on one type of NAND do not work on the other?
Ah this makes a lot of sense, thanks much for clearing all this up. In other news Gateway decided to magically format emuNAND after the nth try, all is looking upIt's not like that. It's that if you purchase something on, say, your EmuNAND, then it will store the purchase ticket on the EmuNAND. Similarly, if you purchase something on SysNAND, then it will store the purchase ticket on the SysNAND.
If you then copy the EmuNAND with the tickets over to the SysNAND, then your SysNAND will also have these tickets. (Or vice versa.)
Now, the thing is... If you check your Data Management in SysNAND while you purchased something in EmuNAND, then it will notice you have eShop content on your SD card even though it can't find the purchase tickets for this. Your SysNAND will then remove this eShop data from the SD card.
I think that is what people are talking about when they say eShop purchases don't work on both.
......well yeah, if you remove the emunand partition or use a different SD card, but if emunand is set up on the SD card it will always boot emunandQuick question: After creating the emuNAND, is it possible to access GW mode without booting into it?
I've noticed a red light coming from inside the 3DS XL, on the down left corner, while playing in a dark room. What is it? Should I be worried?