Actually no it doesn't. I used TinyFormat today on a new N3DS setup, so nothing has changed, the version number is still 1.0.0. All it does is allows us to skip needing an internet connection, and doesn't delete//wipe our Nintendo 3DS folder.Its faster to access and cuts out the BS of the initial setup (Whats your name, where do you live, test the 3D, etc)
Think we are way past that.Use SafeSysUpdater to check files, and use PlaiSysUpdater to actually downgrade
..oh. I wanted to use V1, but I took the lastest release, so it seems.No need for internet connection, and it doesn't delete the Nintendo 3DS folder contents. Since we are unlinking NANDs, it is best we do not delete the folder that pertains to one NAND.
You use GW's a9lh.bin file of course. After you have setup a GW EmuNAND, you place the Launcher.dat on the root of the SD Card. Then you take GW's "arm9loaderhax.bin" file and place it in the /luma/payloads folder, you then rename it to down_GW9.bin. Or use any of the other naming combos as described in Luma3DS' wiki on Payload Chainloading.
Link: https://github.com/AuroraWright/Luma3DS/wiki/Other-features-and-notes#payload-chainloading
This is of course assuming you are using v1 A9LH. v2 A9LH will black-screen with Luma3DS' chainloader, unless you add BootCTR9 into the mix, as I explained earlier.
How was I wrong with what I said? Yes I forgot to regard that it doesnt delete your Nintendo 3DS folder but it definitely skips the setup and depending on what your homebrew launcher setup is its faster to access.Actually no it doesn't. I used TinyFormat today on a new N3DS setup, so nothing has changed, the version number is still 1.0.0. All it does is allows us to skip needing an internet connection, and doesn't delete//wipe our Nintendo 3DS folder.
So I am not sure what you are using.
Think we are way past that.
Only if you have a NNID linked to the system, it required for the Nnid to be unlinked server sideYou NEED a internet connection to FORMAT THE SYSTEM?
What kind of logic is that!![]()
This really explains a lot on why I couldnt unlink my Nintendo ID back when I had a menuhax+emunand setup. Good to know.Only if you have a NNID linked to the system, it required for the Nnid to be unlinked server side
Because it is. I was forced to go through the setup each time, after I used Tiny Format. Even the guide tells you.How was I wrong with what I said? Yes I forgot to regard that it doesnt delete your Nintendo 3DS folder but it definitely skips the setup and depending on what your homebrew launcher setup is its faster to access.
Because it is. I was forced to go through the setup each time, after I used Tiny Format. Even the guide tells you.
Taken from Part 3.
Link: https://github.com/Plailect/Guide/wiki/Part-3-(RedNAND)
19. Open TinyFormat
20. Press Y to format your SysNAND (Don't worry, everything is still saved on RedNAND)
21. Go through initial setup without linking your Nintendo Network ID, you want it to remain linked only to RedNAND to prevent issues
22. Reinstall menuhax on SysNAND as the format will have removed it
Again, Tiny Format does not skip you having to go through the setup. I would know, as I just used it three times today.
Also, I am not trying to be rude or offensive or mean, and I apologize if I do come off as that. However, what you are saying is incorrect.
The method with bootloader worked surprisingly well.. I've set Gateway on D-Pad down and it works perfect. But Luma won't load as default.. damn. I have no Luma.bin, only Luma.dat - and writing Luma.dat in the config does not work out.Otherwise, if you haven't made one or don't have one yet. You'll need to do the "Complete EmuNAND Setup" - Making sure to backup your SD Card contents, prior to doing that. Then copying them back onto the SD Card once done. You'll also have to unlink them by using Tiny Format on whichever one.
One format works, well. Unless you want to use BootCTR9, I wouldn't suggest it. Since Hayleia posted a new workaround, that doesn't need BootCTR9.The method with bootloader worked surprisingly well.. I've set Gateway on D-Pad down and it works perfect. But Luma won't load as default.. damn. I have no Luma.bin, only Luma.dat - and writing Luma.dat in the config does not work out.
Does 1 format do the job? In the guide I had to do this twice to unlink the Nands.
I figured it out, kind of. The Bootloader has it's own Armloader.bin, as well as Luma. When I copied the Bootloader data in the root of the SD-card, it did overwrite Lumas Armloader.bin file. Renamed it Luma.bin and put it over on the SD card again - works like a charm!One format works, well. Unless you want to use BootCTR9, I wouldn't suggest it. Since Hayleia posted a new workaround, that doesn't need BootCTR9.
Link: https://gbatemp.net/threads/using-gateway-on-a9lh-v2.431222/page-4#post-6464898
Tested it with N3DS on v2 A9LH using only Luma3DS' chainloader. Should work well in any scenario for people who want to stick with Luma3DS' chainloader.
As for the format, you only need one. The guide explains why we must do 2 when we downgrade the RedNAND//EmuNAND, basically when NANDs reach the same amount of formats, they re-link. So if I had previously formatted SysNAND, then went ahead and formatted EmuNAND, I would technically be re-linking them again, and so to unlink them, I'd have to perform another format on one of them. In your case, both should technically be at 0, as if you are setting up a fresh RedNAND//EmuNAND, then both of them have the same format counter, so only 1 format is needed to unlink them.
Your NANDs will unlink with just one format. You'll have to go through the setup process on the one you formatted, and you'll also have to make sure you don't link the NNID to the other, if it's already linked to one.I figured it out, kind of. The Bootloader has it's own Armloader.bin, as well as Luma. When I copied the Bootloader data in the root of the SD-card, it did overwrite Lumas Armloader.bin file. Renamed it Luma.bin and put it over on the SD card again - works like a charm!
Ah, it was because of the downgrade - I remember again. Right, thank you!
So I'm going to use Tiny Formatter and everything should be unlinked.
Right.Your NANDs will unlink with just one format. You'll have to go through the setup process on the one you formatted, and you'll also have to make sure you don't link the NNID to the other, if it's already linked to one.
So, to close this thread..
- I have downgraded to 9.2, upgraded to 11.0, then downgraded again to 2.1
- I have installed armloader9 hax
- I have installed updated Luma3DS on SysNand, booting every time with no error
- I have Gateway set on a shortcut so I can access that a well anytime
- I have an .cia installer, a play coin setter and an ftp program for little files
..and learned many many things from you. Thanks for the patience, hope I can bring that back to you all someday.![]()