Okay, let me see if I can explain this so everyone here is on the same page.
I bought the Gateway 3DS before any other 'free' exploits were even available yet. At the time, I had my original, updated original 3DS and managed to find a 3DS XL that was thankfully on a vulnerable firmware. When the card finally arrived, I updated the loader files at the time, set up and created an emunand on the XL, and did the system transfer from my original, ambassador 3DS to it. so the XL's sysNAND is on 4.4, and everything there has been working fine since. Even better now with cheats support through the Gateway mode.
So why am I even looking at CFW? The only thing that the Gateway 3DS lacks currently, is a way for me to play the GBA or DSiWare that I currently already own, including the ambassador titles, and the legit DSiWare I gained through club Nintendo when it was still up. I was told by some friends that do more tinkering with this stuff, and by other users on here, that I should be able to have it so that I could just run the respective sploit install and boot from there as I please. I get that there are some other 'sploits out there, but the whole install sploit thing from the DS cart is simple enough and has worked fine for me. Also the only times I really power cycled the system was in the event of taking the SD out, to either back up the emunand or for fiddling with save editors on save files.
What I want, is for the CFW to be able to boot the emunand and work with running at least the GBA and DSIWare. I have the Gateway for literally everything else. I don't want to mess with the sysnand on this board as much as possible. And I want to be able to load it the same way as the Gateway currently does (install sploit, go to DS profile, and launch). If it can't do that, I'm already not interested. Telling me to go do it another way will just be ignored. are we clear?
I just know the last time that I tried doing this, I was suggested to get rxtools. Well, first time around, rxtools exploit launcher did start up, but refused to open the emunand at all. After it did finally launch the emunand, it then just black screened on the very games that I was installing it for. The final straw, was that it kept borking up in its launcher, so that in the inevitable power cycles in trying to get the thing to work, it eventually got to the state where it would error out and restart sysNAND until I reinstalled a different version of the same exploit installer, only for it to still not work.
It frustrated me to the point I just deleted it all and wiped it from my SD card. So as far as the CFW path, I'm starting from square one. Which means I need anything and everything needed to make it work. Now, with that said, I still don't know where to start... or rather, where to start on a path that actually works...
I bought the Gateway 3DS before any other 'free' exploits were even available yet. At the time, I had my original, updated original 3DS and managed to find a 3DS XL that was thankfully on a vulnerable firmware. When the card finally arrived, I updated the loader files at the time, set up and created an emunand on the XL, and did the system transfer from my original, ambassador 3DS to it. so the XL's sysNAND is on 4.4, and everything there has been working fine since. Even better now with cheats support through the Gateway mode.
So why am I even looking at CFW? The only thing that the Gateway 3DS lacks currently, is a way for me to play the GBA or DSiWare that I currently already own, including the ambassador titles, and the legit DSiWare I gained through club Nintendo when it was still up. I was told by some friends that do more tinkering with this stuff, and by other users on here, that I should be able to have it so that I could just run the respective sploit install and boot from there as I please. I get that there are some other 'sploits out there, but the whole install sploit thing from the DS cart is simple enough and has worked fine for me. Also the only times I really power cycled the system was in the event of taking the SD out, to either back up the emunand or for fiddling with save editors on save files.
What I want, is for the CFW to be able to boot the emunand and work with running at least the GBA and DSIWare. I have the Gateway for literally everything else. I don't want to mess with the sysnand on this board as much as possible. And I want to be able to load it the same way as the Gateway currently does (install sploit, go to DS profile, and launch). If it can't do that, I'm already not interested. Telling me to go do it another way will just be ignored. are we clear?
I just know the last time that I tried doing this, I was suggested to get rxtools. Well, first time around, rxtools exploit launcher did start up, but refused to open the emunand at all. After it did finally launch the emunand, it then just black screened on the very games that I was installing it for. The final straw, was that it kept borking up in its launcher, so that in the inevitable power cycles in trying to get the thing to work, it eventually got to the state where it would error out and restart sysNAND until I reinstalled a different version of the same exploit installer, only for it to still not work.
It frustrated me to the point I just deleted it all and wiped it from my SD card. So as far as the CFW path, I'm starting from square one. Which means I need anything and everything needed to make it work. Now, with that said, I still don't know where to start... or rather, where to start on a path that actually works...
