I don't exactly know how it works, I just know that it's able to access both sysNAND and emuNAND, no matter where you launch it from.
Whether you boot it from emuNAND, sysNAND, or A9LH. It'll detect everything.
- Thread starter Reisyukaku
- Start date
- Views 811,853
- Replies 6,480
- Likes 115
Whether you boot it from emuNAND, sysNAND, or A9LH. It'll detect everything.
Yeah, I thought that emuNAND's purpose is to have a completely isolated environment from sysNAND. I'm now wondering whether Nintendo could do the same and update sysNAND through emuNAND.
From what I know, they are separate and emuNAND is isolated (especially if your NANDs are unlinked). But something like Decrypt9 is running through Arm9, which has access to both NANDs. This is why you need to completely restart your system when exiting Decrypt9. This is also why you can run Decrypt9 from A9LH (before boot).
I may be wrong though, some correct me if I am.
Er.. Yeah I was probably wrong then XD
I just know that Nintendo can't update your sysNAND through emuNAND. Why is works that way? I don't know
Someone more knowledgeable should answer that.No, you weren't wrong. Do you think Nintendo would make a DS mode updater? Probably not. And would people run it? Even more unlikely.Er.. Yeah I was probably wrong then XD
I just know that Nintendo can't update your sysNAND through emuNAND. Why is works that way? I don't know
That's why it's always good to wait a few minutes before updating your system. Wait until it's confirmed to update.
Also, if you're using A9LH with something like AuReiNAND, it blocks FIRM0/FIRM1 so you won't be affected, if Nintendo were to ever do that.
Not sure if it works that way. After all, Decrypt9 is perfectly able to work with AuReiNand...
I know, but I mean, when you say " it blocks FIRM0/FIRM1 so you won't be affected, if Nintendo were to ever do that.", I'm not sure that Nintendo wouldn't be able to bypass this using ARM9-based updater.
However, it's very unlikely that it will happen. Sounds like a "dirty" way to do it ^^
FIRM0/FIRM1 doesn't affect arm9 stuff, which is why you can still use Decrypt9 just fine.
From what I've been told over at #cakey, with FIRM0/FIRM1 blocked Nintnedo will never be able to remove A9LH from your system.
That's what I said : FIRM protection doesn't affects ARM9. So, IF Nintendo decides to do an update based on ARM9 stuff (even if it's very unlikely as I said), it could overwrite it because the patch would be, well, ineffective.
Does ReiNAND lack the support of O3DS now? I'm asking this because the tutorials I have seen from this year have N3DS's running ReiNAND.
Also, my screen hangs on the ReiNAND Splash screen.
Small info in case of reference
Australian O3DS
Also, my screen hangs on the ReiNAND Splash screen.
Small info in case of reference
Australian O3DS
Last edited by GlitchyDavid,
Yes, ReiNAND does not work on the o3DS.
There is a version of ReiNAND that works on the o3DS and it's called AuReiNAND.
Edit: Ninja'd
Technically yeah. It's based off ReiNAND.
Has a few more features here and there, but essentially the same.
It's roughly the same as the original, but it supports O3DS and is slightly more ARM9LoaderHax friendly. They're both stable and minimalist CFWs, so you can't go wrong by using ARN until the original supports O3DS too.
Last edited by daxtsu,
How would i know if intalled aureinand correctly? Im using a9lh with reunand now.. I wanted to try the updated sysnand.. Im a bit cautious cause i dont want to update nd lose all my hax.. Does it mean i can update my sysnand safely without worrying loss of hax?
To play it safe, delete all your current reinand files/folder.
Then drag everything from the latest AuReiNAND zip file to your SD card. Don't forget to get the firmware files for your system and place them in the /rei/ folder.
Also, create a file called "updatedsysnand" but remove the .txt extension from it, then place it in the /rei/ folder.
Similar threads
-
- Article
