so.. if i boot sysnand from rxtools and install fbi.cia. its then safe for me install gba.cia on sys and emunand?Yes. It is safe. You can only do so from emuNAND or using a patched version of sysNAND (rxMode for example)
In fact.. before GBA VC will boot from emuNAND it MUST be installed to sysNAND.
To use FBI through sysNAND, you must be booted into rxMode or using pasta.. as unpatched sysNAND will NOT install anything using FBI.so.. if i boot sysnand from rxtools and install fbi.cia. its then safe for me install gba.cia on sys and emunand?
Youre better off just using FBI through emuNAND to install to both that and sysNAND... then running your VC through emuNAND.
To change installation location (at least with older FBI builds) simply press L trigger, you should see "SD" change to "NAND". SD=emuNAND, while NAND=sysNAND
However if you insist on using FBI through sysNAND, you must be booted into rxMode or using pasta.. as unpatched sysNAND will NOT install anything using FBI.
Thats just HOW its done.. regarding safety.. its safe, provided you know what youre installing/doing.
This is not true. Whether using emuNAND or sysNAND, both install to the SD.No. SD = Install to sdcard. Nand = Install to the nand you're currently in.
So you have to boot to sysnand using rxtools or minipasta and install FBI there, then install the GBA VCs.
That's a really common misconception!!! Would be best to edit your post to take this incorrect information away before any noobs see it and believe it. There's enough trouble caused when noobs come up with this idea on their own.Youre better off just using FBI through emuNAND to install to both that and sysNAND... then running your VC through emuNAND.
To change installation location (at least with older FBI builds) simply press L trigger, you should see "SD" change to "NAND". SD=emuNAND, while NAND=sysNAND
However if you insist on using FBI through sysNAND, you must be booted into rxMode or using pasta.. as unpatched sysNAND will NOT install anything using FBI.
Thats just HOW its done.. regarding safety.. its safe, provided you know what youre installing/doing.
Well I was half right to start.. lol I couldnt remember or try myself without emuNAND anymore.That's a really common misconception!!! Would be best to edit your post to take this incorrect information away before any noobs see it and believe it. There's enough trouble caused when noobs come up with this idea on their own.
Some correct information:
EmuNAND's 'NAND' is a partition on the SD card, sysNAND's 'NAND' is stored on the console. Both emuNAND's 'SD' and sysNAND's 'SD' are files on the main partition on the SD card. If unlinked, then they're separate folders inside the Nintendo 3DS folder, if linked they are the same.
When you are in emuNAND and you install to 'NAND' you are installing to that small partition on the SD card. When in sysNAND, if you install to 'NAND' you are installing to the console itself. When in emuNAND if you install to 'SD', you are installing to emuNAND's folder inside the Nintendo 3DS folder, and if you install to 'SD' on sysNAND, to sysNAND's folder inside the Nintendo 3DS folder.
Im curious now if im crazy or not. Cause I thought this was possible with older builds as well..If your using a9lh and have a nand backup, mess around and experiment as you please. I think before FBI used to allow installation to the sysnand (not 3ds folder) that caused bricks, especially on updating.