I linked to this earlier. it's the best one based on your version "9.2.0-9U". rxTools 2.5.2
sysNAND is now 9.2.0-20U!!! And I already have Homebrew Menu setup!!! YAY!!!
Okay...
On Part 3 (RedNAND)
I already have sysNAND updated to 9.2.0-20U w/Homebrew Launcher installed.
I also have a GWemuNAND updated to 11.0.0-33U.
Both .bin and .sh backups of NANDs are backed up and the proper size (Toshiba).
So now I'm making the third in-between layer which is my RedNAND. Basically a copy of my sysNAND. I back up RedNAND on 9.2 then update it to 11.0 and back it up again. Then if anything happens, it happens to my RedNAND not my sysNAND.
Then I'm going to tell sysNAND to skip directly to emuNAND with autoboot.
To do this I must downgrade sysNAND to 2.1???
So theme color sysNAND white, RedNAND red, and emuNAND whatever (black).
All autoboot will do is skip directly into emuNAND but give me option to use RedNAND to do all my dirty work, while emuNAND I have my fun. Meanwhile I leave sysNAND alone on 2.1.
Did I get this right?
So if I already have GWemuNAND do I need Luma?
On Part 3 (RedNAND)
I already have sysNAND updated to 9.2.0-20U w/Homebrew Launcher installed.
I also have a GWemuNAND updated to 11.0.0-33U.
Both .bin and .sh backups of NANDs are backed up and the proper size (Toshiba).
So now I'm making the third in-between layer which is my RedNAND. Basically a copy of my sysNAND. I back up RedNAND on 9.2 then update it to 11.0 and back it up again. Then if anything happens, it happens to my RedNAND not my sysNAND.
Then I'm going to tell sysNAND to skip directly to emuNAND with autoboot.
To do this I must downgrade sysNAND to 2.1???
So theme color sysNAND white, RedNAND red, and emuNAND whatever (black).
All autoboot will do is skip directly into emuNAND but give me option to use RedNAND to do all my dirty work, while emuNAND I have my fun. Meanwhile I leave sysNAND alone on 2.1.
Did I get this right?
So if I already have GWemuNAND do I need Luma?
Last edited by Osmosis,
Just follow as the guide says, don't try to assume, take shortcuts to do your way or you going to end into trouble.
Right now you have sysNAND 9.2.0-20 and have to create the RedNAND (emuNAND) from it. Don't try to use your GW emuNAND and instead start with a fresh RedNAND on the same console SD card or use a spare one. You can backup your current GW emuNAND to PC using EmuNAND Tool for Windows. Then boot into RedNAND using Luma3DS as per guide (follow Part 3 - RedNAND) and update the RedNAND to latest version.
Step 5 of Section I in Part 4 clearly says to boot in RedNAND (emuNAND) so kindly do that. Don't try to downgrade sysNAND.
https://github.com/Plailect/Guide/wiki/Part-4-(2.1.0-Downgrade)
Right now you have sysNAND 9.2.0-20 and have to create the RedNAND (emuNAND) from it. Don't try to use your GW emuNAND and instead start with a fresh RedNAND on the same console SD card or use a spare one. You can backup your current GW emuNAND to PC using EmuNAND Tool for Windows. Then boot into RedNAND using Luma3DS as per guide (follow Part 3 - RedNAND) and update the RedNAND to latest version.
Step 5 of Section I in Part 4 clearly says to boot in RedNAND (emuNAND) so kindly do that. Don't try to downgrade sysNAND.
https://github.com/Plailect/Guide/wiki/Part-4-(2.1.0-Downgrade)
Last edited by Just3DS,
I just made few edits on my previous post for clarity. Yes you should backup your GW emuNAND and "Nintendo 3DS" folder to your PC if you care about your stuff in GW emuNAND.
Then follow from Part 3 with a fresh SD card (if you using same SD card then backup all contents of it to your PC, use MiniTool Partition Wizard to remove all partitions from SD card, and create a Primary partiton formatted to FAT32, put all the content back to SD card then follow Part 3).
Once you have AL9H completed you can use your GW emuNAND again if you want to. That requires you to write your backed up emuNAND.bin using EmuNAND9 or Decrypt9 payload on console to RedNAND (emuNAND) partition. Also put the "Nintendo 3DS" folder.
EDIT: Looks like you can format emuNAND partition using EmuNAND9. Have you backed up your current GW emuNAND.bin to PC? If yes then press A to format. You may need to copy all SD card content back again after doing that.
Last edited by Just3DS,
So now I have an EMUNAND9SD with an EmuNAND9 folder....
So just copy everything back on and keep the EmuNAND9 folder...
And yes, I backed up both SysNAND and emuNAND and even saved the .sh files.
Still waiting on initial boot to show redNAND homescreen... considering the size of the mSD this might take a while...
(ABOUT 10 MINS LATER) Now I'm getting concerned... But it does take about 30 mins to do a GWemuNAND format... so... ???
So just copy everything back on and keep the EmuNAND9 folder...
And yes, I backed up both SysNAND and emuNAND and even saved the .sh files.
Still waiting on initial boot to show redNAND homescreen... considering the size of the mSD this might take a while...
(ABOUT 10 MINS LATER) Now I'm getting concerned... But it does take about 30 mins to do a GWemuNAND format... so... ???
Last edited by Osmosis,
Nope, this doesn't seem to be working. Even rebooted a couple of times. Let it go into sysNAND and it doesn't seem to a problem with the mSD.. Not getting a "Can't fiind SD Card" prompt.
Going to reformat mSD, put all content back on, launch homebrew and do a redNAND setup again... see if it helps.
But first.... sleep.
Going to reformat mSD, put all content back on, launch homebrew and do a redNAND setup again... see if it helps.
But first.... sleep.
There was really no need to create a new RedNAND and all, your EmuNAND was enough.
I don't get what is your end goal actually. Do you want to install arm9loaderhax but also keep an EmuNAND to use Gateway with it?
I don't get what is your end goal actually. Do you want to install arm9loaderhax but also keep an EmuNAND to use Gateway with it?
The goal is that I'm tired of using browser hax to load into Gateway. Don't want to downgrade sysNAND to 4.1 and use settings entry. I really want to be able to autoboot into GWemuNAND but was impressed by Homebrew Launcher's capabilities. I also want to use FBI because BlueMenu doesn't handle 128GB very well.
End goal: autoboot into GWemuNAND and be able to dump savedata without soft bricking all the time. I also like the idea of being able to have a choice to boot into other NANDs without an internet connection. Even being able to convert carts into .CIA is exciting.
End goal: autoboot into GWemuNAND and be able to dump savedata without soft bricking all the time. I also like the idea of being able to have a choice to boot into other NANDs without an internet connection. Even being able to convert carts into .CIA is exciting.
Alright, so you mainly have 2 choices I guess.
• First is to setup menuhax, choose type 1 or type 2 (depending on whether or not you'd want the default behaviour to be booting to SysNAND unless you press a button, or the opposite).
After that, you can stay with that setup, or install a boot manager (CTRBootManager or BootCTR). With that you will have a nice screen on boot to choose whether you want to boot Gateway Mode on you EmuNAND, or another CFW like Luma3DS (still on your EmuNAND), or just boot to the Homebrew Launcher.
• Second is go on with Plailect's guide from part 4, use your EmuNAND where it says RedNAND, and set up arm9loaderhax.
When finished, you will still be able to use multiple CFWs (Luma3DS, GW) and use a boot manager (CTRBootManager9 or BootCTR9).
You'll be able to move your EmuNAND to your SysNAND and use just that (arm9loaderhax is protected, so it's not dangerous to use SysNAND) or use SysNAND and an EmuNAND.
The main visible difference will be this:
You'll also have brick protection (since arm9loaderhax takes over the system early on boot), and you will never loose arm9loaderhax even after updating the console (unless you chose to uninstall it someday).
• First is to setup menuhax, choose type 1 or type 2 (depending on whether or not you'd want the default behaviour to be booting to SysNAND unless you press a button, or the opposite).
After that, you can stay with that setup, or install a boot manager (CTRBootManager or BootCTR). With that you will have a nice screen on boot to choose whether you want to boot Gateway Mode on you EmuNAND, or another CFW like Luma3DS (still on your EmuNAND), or just boot to the Homebrew Launcher.
• Second is go on with Plailect's guide from part 4, use your EmuNAND where it says RedNAND, and set up arm9loaderhax.
When finished, you will still be able to use multiple CFWs (Luma3DS, GW) and use a boot manager (CTRBootManager9 or BootCTR9).
You'll be able to move your EmuNAND to your SysNAND and use just that (arm9loaderhax is protected, so it's not dangerous to use SysNAND) or use SysNAND and an EmuNAND.
The main visible difference will be this:
You'll also have brick protection (since arm9loaderhax takes over the system early on boot), and you will never loose arm9loaderhax even after updating the console (unless you chose to uninstall it someday).
Last edited by Kyojin,
Second option. Yes. Definitely.
Problem is, I already tried to install RedNAND with Luma. Luma won't boot. Even did a clean wipe of mSD and tried. Still no luck.
So should I wipe mSD and just do a fresh install of GWemuNAND from GW Menu like normal and make sure sys/emu are unlinked? Then proceed with step 4?
I'm not trying to save data or anything. I'm trying to do a clean install, backing it up, then will go crazy...
I have a backup of both my sysNAND at 9.2-9U and 20U. Clean. Unlinked. No Homebrew Launcher.
Just not sure where to go from here...
So in the Guide where it says "Complete RedNAND" setup I choose to "Complete emuNAND (GW) setup" instead? Thus making a partition from my GWemuNAND?
Problem is, I already tried to install RedNAND with Luma. Luma won't boot. Even did a clean wipe of mSD and tried. Still no luck.
So should I wipe mSD and just do a fresh install of GWemuNAND from GW Menu like normal and make sure sys/emu are unlinked? Then proceed with step 4?
I'm not trying to save data or anything. I'm trying to do a clean install, backing it up, then will go crazy...
I have a backup of both my sysNAND at 9.2-9U and 20U. Clean. Unlinked. No Homebrew Launcher.
Just not sure where to go from here...
So in the Guide where it says "Complete RedNAND" setup I choose to "Complete emuNAND (GW) setup" instead? Thus making a partition from my GWemuNAND?
please don't use GW menu for this. if you need EmuNAND instead of RedNAND (for Gateway), use "Complete EmuNAND Setup" in EmuNAND9.
Okay... I thought about it some more...
I want to be able to pokegen.
I want my 3DS to autoboot into GWemuNAND when I press the power button using arm9loaderhax. But I also want the option to hold a button and load a boot manager during startup with the following selections:
Title manager doesn't cut it on 128GB. It works for installing .CIA's, but not so well for dumping and restoring savedata. I need savedata dumping/restore for pokegenning and backing up game progress. GWemuNAND works fine for installing .CIA''s and using redcart, but I also like using bluecart and DSTwo, and even Sky3DS. I like using the Sky3DS with Pokemon XYORAS because of Powersaves. Redcart cheats are nice, but Powersaves Pro is better. But I also want to be able to pokegen using PKHeX.
Does this help? I'm not interested in a free CFW. I already have the GW. I just want to skip the browser load for GW Menu or having to go through settings entrypoint.
EDIT:
I like using the DSTwo to save mSD space. This way I can DL NES, SNES, etc. ROMs onto the DSTwo instead of installing Virtual Console .CIA's (except for new Pokemon Red, Blue, Green which HAS to be an eShop DL). I like Bluecart because it saves space on DSTwo. This way I can have retro games on DSTwo, DS games on Bluecart, and eShop games on Redcart while installing all the .CIA's I want on my mSD.
The Sky3DS is mostly for Powersaves Pro and being able to share games with non-hacked 3DS units for multiplayer/sharing. This way I can use Powersaves on Pokemon, or share my Sky3DS with friends without having to worry about their FW# or not having an extra copy.
Yes, I'm aware that eventually I'll have to upgrade to a Sky3DS+, or a DSTwo+ and I still need to add an N2Elite and get an N3DSXL which I'll then use GW on and keep my O3DSXL just for reasons, I guess. So right now, I'm okay with not being able to play the N3DSXL games. That's kewl. But I'm more than willing to put an O3DSXL to good use...
I want to be able to pokegen.
I want my 3DS to autoboot into GWemuNAND when I press the power button using arm9loaderhax. But I also want the option to hold a button and load a boot manager during startup with the following selections:
Title manager doesn't cut it on 128GB. It works for installing .CIA's, but not so well for dumping and restoring savedata. I need savedata dumping/restore for pokegenning and backing up game progress. GWemuNAND works fine for installing .CIA''s and using redcart, but I also like using bluecart and DSTwo, and even Sky3DS. I like using the Sky3DS with Pokemon XYORAS because of Powersaves. Redcart cheats are nice, but Powersaves Pro is better. But I also want to be able to pokegen using PKHeX.
Does this help? I'm not interested in a free CFW. I already have the GW. I just want to skip the browser load for GW Menu or having to go through settings entrypoint.
EDIT:
I like using the DSTwo to save mSD space. This way I can DL NES, SNES, etc. ROMs onto the DSTwo instead of installing Virtual Console .CIA's (except for new Pokemon Red, Blue, Green which HAS to be an eShop DL). I like Bluecart because it saves space on DSTwo. This way I can have retro games on DSTwo, DS games on Bluecart, and eShop games on Redcart while installing all the .CIA's I want on my mSD.
The Sky3DS is mostly for Powersaves Pro and being able to share games with non-hacked 3DS units for multiplayer/sharing. This way I can use Powersaves on Pokemon, or share my Sky3DS with friends without having to worry about their FW# or not having an extra copy.
Yes, I'm aware that eventually I'll have to upgrade to a Sky3DS+, or a DSTwo+ and I still need to add an N2Elite and get an N3DSXL which I'll then use GW on and keep my O3DSXL just for reasons, I guess. So right now, I'm okay with not being able to play the N3DSXL games. That's kewl. But I'm more than willing to put an O3DSXL to good use...
Last edited by Osmosis,
Gateway's arm9loaderhax.bin doesn't support chain-loading AFAIK (like Luma3DS does). So, you won't be able to have that setup using just GW A9LH.bin I think.
Though, you could just set up a A9LH compatible boot manager (links a few posts above) and have it auto-boot GW after X seconds if you don't press anything.
You could have something more simple I guess:
• Boot manager that boots GW mode on your EmuNAND by default
• Luma3DS as a secondary CFW that boots on your SysNAND (it protects it) for Sky3DS, DS flashcarts, VC games and everything else (Luma has extended support for DS flashcarts, since it patches the TWL FIRM (or "DSi mode"))
-> You could have FBI and install CIAs on both your SysNAND and EmuNAND.
-> You can dump stuff using Decrypt9, which you can chain-load using Luma or boot from the boot manager.
-> For dumping and restoring saves, you could use JK's Save Manager.
Though, you could just set up a A9LH compatible boot manager (links a few posts above) and have it auto-boot GW after X seconds if you don't press anything.
You could have something more simple I guess:
• Boot manager that boots GW mode on your EmuNAND by default
• Luma3DS as a secondary CFW that boots on your SysNAND (it protects it) for Sky3DS, DS flashcarts, VC games and everything else (Luma has extended support for DS flashcarts, since it patches the TWL FIRM (or "DSi mode"))
-> You could have FBI and install CIAs on both your SysNAND and EmuNAND.
-> You can dump stuff using Decrypt9, which you can chain-load using Luma or boot from the boot manager.
-> For dumping and restoring saves, you could use JK's Save Manager.
Right, but from what I've experienced, the 128GB is sometimes a drag because some .CIA managers don't handle the full 128GB. From what I understand, FBI does. However, I'm not shooting down options.
I like your idea better. Autoboot naturally into GWemuNAND, and use Luma as classic mode. Will Luma support BlueCart? I thought that only works with Gateway emuNAND?
I'd really like to leave sysNAND alone. The less I touch it, the better. But I could leave Homewbrew Launcher on it. That doesn't bother me.
Not going to install any .CIA's on sysNAND. That's what GWemuNAND is for.
Does JK's Dump Manager support 128GB?
Might as well use Decrypt9 from Boot manager... but yeah, using Luma is always safer.
I like the CTRBootManager idea. Which is better? BootCTR or CTRBootManager? Are these A9LH compatible?
Will I lose the boot speed of arm9loaderhax? Or could I boot into my other NANDs from Menuhax? Instead of a boot manager I just hold DOWN and load my other NANDs from Menuhax/Homebrew Launcher?
Now I'm getting confused... but I think you know what I'm aiming for. This is very helpful.
EDIT:
So let's sit on this before I do anything else. I need to go clean up and play some Pokemon TCG at store. Keep coming up with ideas, but don't burn out over it. 3DS is just going to sit here for a while until we figure out a good strategy.
I really appreciate everyone's help. This is why I love GBATemp.net.
In the meantime, spam away... I'll catch up later tonight.
I like your idea better. Autoboot naturally into GWemuNAND, and use Luma as classic mode. Will Luma support BlueCart? I thought that only works with Gateway emuNAND?
I'd really like to leave sysNAND alone. The less I touch it, the better. But I could leave Homewbrew Launcher on it. That doesn't bother me.
Not going to install any .CIA's on sysNAND. That's what GWemuNAND is for.
Does JK's Dump Manager support 128GB?
Might as well use Decrypt9 from Boot manager... but yeah, using Luma is always safer.
I like the CTRBootManager idea. Which is better? BootCTR or CTRBootManager? Are these A9LH compatible?
Will I lose the boot speed of arm9loaderhax? Or could I boot into my other NANDs from Menuhax? Instead of a boot manager I just hold DOWN and load my other NANDs from Menuhax/Homebrew Launcher?
Now I'm getting confused... but I think you know what I'm aiming for. This is very helpful.
EDIT:
So let's sit on this before I do anything else. I need to go clean up and play some Pokemon TCG at store. Keep coming up with ideas, but don't burn out over it. 3DS is just going to sit here for a while until we figure out a good strategy.
I really appreciate everyone's help. This is why I love GBATemp.net.
In the meantime, spam away... I'll catch up later tonight.
Last edited by Osmosis,
-> Yes, GW's blue cart should work just fine as it is an R4i clone AFAIK.
-> About JK's Save Manager, never heard of issues with 128GB cards (only for DevMenu and other Nintendo leaked apps)
-> I never tried a boot manager yet (Luma3DS is enough for me), but CTRBootManager is more popular. And yes, their xxx9 versions are A9LH compatible (so, CTRBootManager9 and BootCTR9).
-> No, there will still be a huge gap between using a boot manager with A9LH, and using menuhax (even without a boot manager). Of course, it will take a couple seconds more, but in the end you'll boot within roughly 10 seconds (so nearly two times faster than w/ menuhax).
What I could suggest is, seeing how you already are on 9.2 and already have your setup working, just configure menuhax to auto-boot, and set up CTRBootManager or BootCTR (you could try both to see which one you prefer).
If after a few days you find that the boot time is too much, then consider switching to arm9loaderhax.
You don't really need A9LH to use JK's Save Manager or FBI, so your current setup might be satisfactory after using menuhax + a boot manager instead of using the browser!
-> About JK's Save Manager, never heard of issues with 128GB cards (only for DevMenu and other Nintendo leaked apps)
-> I never tried a boot manager yet (Luma3DS is enough for me), but CTRBootManager is more popular. And yes, their xxx9 versions are A9LH compatible (so, CTRBootManager9 and BootCTR9).
-> No, there will still be a huge gap between using a boot manager with A9LH, and using menuhax (even without a boot manager). Of course, it will take a couple seconds more, but in the end you'll boot within roughly 10 seconds (so nearly two times faster than w/ menuhax).
What I could suggest is, seeing how you already are on 9.2 and already have your setup working, just configure menuhax to auto-boot, and set up CTRBootManager or BootCTR (you could try both to see which one you prefer).
If after a few days you find that the boot time is too much, then consider switching to arm9loaderhax.
You don't really need A9LH to use JK's Save Manager or FBI, so your current setup might be satisfactory after using menuhax + a boot manager instead of using the browser!
Okay, I've decided to use the CTRBootManager method for now (Will work on BootCTR for later):
My only problem is I erased my mSD. I have both sysNAND and GWemuNAND.bin/.sh files. I also have the Nintendo3DS folder backed up. So uh, how should I go about restoring my mSD and emuNAND? Should I just copy my folders & files back to mSD and proceed with above guide? Or must I complete emuNAND setup from menuhax manager? Does this require a copy of the GWemuNAND.bin and .sh files on mSD?
=====================
Otherwise, this way I can just autoboot into GWemuNAND (with RedCart) without pressing anything. If I hold LT it'll take me into Gateway Menu for CLASSIC Mode (BlueCart, DSTwo, Sky3DS), hold RT = Homebrew Launcher where I can use Decrypt9, and D-PAD UP = sysNAND (Just in case).
Then I'll just install FBI/JKSM.cia to emuNAND. (I got this right, yes?)
Wish I could do a LT+RT combo for sysNAND...
I also wish there was a way to hide the Menuhax autoboot screens. Seizure inducing acid trips are not Pokepals...
But I'll start working with BootCTR and maybe make a nice little splash screen.
Maybe someday Gateway will work with arm9loaderhax... and we'll have a boot manager for arm9loaderhax...?? Or can we still hold down during boot to get into Homebrew Launcher? If so, why not just make a GW Menu boot from there? Then people could just skip into Homewbrew Launcher to boot GW Menu for Classic mode and whatnot...?
My only problem is I erased my mSD. I have both sysNAND and GWemuNAND.bin/.sh files. I also have the Nintendo3DS folder backed up. So uh, how should I go about restoring my mSD and emuNAND? Should I just copy my folders & files back to mSD and proceed with above guide? Or must I complete emuNAND setup from menuhax manager? Does this require a copy of the GWemuNAND.bin and .sh files on mSD?
=====================
Otherwise, this way I can just autoboot into GWemuNAND (with RedCart) without pressing anything. If I hold LT it'll take me into Gateway Menu for CLASSIC Mode (BlueCart, DSTwo, Sky3DS), hold RT = Homebrew Launcher where I can use Decrypt9, and D-PAD UP = sysNAND (Just in case).
Then I'll just install FBI/JKSM.cia to emuNAND. (I got this right, yes?)
Wish I could do a LT+RT combo for sysNAND...
I also wish there was a way to hide the Menuhax autoboot screens. Seizure inducing acid trips are not Pokepals...
But I'll start working with BootCTR and maybe make a nice little splash screen.
Maybe someday Gateway will work with arm9loaderhax... and we'll have a boot manager for arm9loaderhax...?? Or can we still hold down during boot to get into Homebrew Launcher? If so, why not just make a GW Menu boot from there? Then people could just skip into Homewbrew Launcher to boot GW Menu for Classic mode and whatnot...?
Last edited by Osmosis,
You'll have to restore your EmuNAND backup to the microSD using EmuNAND9. Just copying the files back won't be enough.
With the default CTRBootManager config (stated in that GW tutorial), you need to hold L to boot SysNAND. For your case, I think that adding:
Code:
{
title = "HomeMenu";
path = "homemenu";
key = 6;
},will make you boot the SysNAND Home Menu when holding DPAD UP.
Also, to make holding R boot HBL, you should add "key = 6;" to the HBL entry.
Yes!
I also wish there was a way to hide the Menuhax autoboot screens. Seizure inducing acid trips are not Pokepals...
arm9loaderhax.
But more seriously, you can use the lesshax payload.
It does already, as I briefly mentioned here.
There are already, as I mentioned here.
There is no need to, really. With arm9loaderhax you can load important stuff on console's boot (boot managers, Gateway, a CFW, Decrypt9, etc.). After installing arm9loaderhax, most people barely use HBL again I guess.
Again, if you are talking about arm9loaderhax, there is no need for HBL to boot Gateway stuff. A9LH is an entry point installed to the console itself, so no need for HBL.
Similar threads
-
-
-
-
-
@
CameronCataclysm:
Why no blog posts about Nitendont going after Garry's Mod repos that have been up for a decade or 2? -
-
-
@
Xdqwerty:
Is it safe to update a modded ps3?
Can I play online in pirated games? (with ps3hen either enabled or not) -
-
-
-
-
-
@
Xdqwerty:
@salazarcosplay, I used apollo save tool to activate my ps3 offline so i could play a game that wasnt working
-
S @ salazarcosplay:from what I understood. you load up the piratged game. you the clear the syscalls, then you play
-
-
-
-
-
-
-
-
-
-
