Hacking Why not a Gateway 3ds 2.0b1 video tutorial?

  • Thread starter Thread starter Enigma Hall
  • Start date Start date
  • Views Views 5,354
  • Replies Replies 38
Holding down the L button for the menu, using the EmuNAND... That's all stuff for Gateway 2.0! It seems you're still on Gateway 1.2
 
OK, got 'er done. It was a bit involved and scary tbh, so let's be a little more understanding to those that are not as seasoned at this eh?? :)
 
Instead of making another thread about this...uh... wow. This is complicated!

I have my Gateway which currently has FW1.2 and a 3DSXL on 4.1. Works fine this way.

So I'm reading the release notes to update to 2.0 beta. 'Hold down L while turning on Gateway mode'. What does that mean? Selecting the 'DS profile' option in Settings? Why don't they use the same terminology throughout? I'm guess that's NOT what it means, because I get no menu. Am I supposed to have already put the new firmware on the mSD? Gah, the documentation for Gateway is a joke! Even the step-by-steps on here aren't miss out on a few steps because they're written by smart people that take certain things for granted and forget that noobs like me need every step detailed. :P Anybody know of an idiots guide? :P

Sorry, I had assumed that one would have already copied the Launcher.dat file from the GW2.0b distribution to their 3DS's SD before starting my tutorial. Step one has been adjusted.

And what is sysNAND and emuNAND? Is the first the systems natural NAND, and the other the hacked emulated one?

Yes. sysNAND is the "real" one in your 3DS proper, and the emuNAND is "emulated" one on a partition on your SD.


Then why does the guide say different. I agree with your logic, so did they make a mistake?

Not a mistake, they're just doing it in a different step then I am because I want the NAND.bin file to survive the format w/o having to copy it to my computer first. I also started w/ a brand new SD card (I needed a larger one) so there was nothing for me to "back up" in their step one, and by doing it "my" way it meant less swaps of the SD between the computer and the 3DS. Their step order is not incorrect, but neither is mine.
 
Sorry, I had assumed that one would have already copied the Loader.bin file from the GW2.0b distribution to their 3DS's SD before starting my tutorial. Step one has been adjusted.
Loader.bin? Do you mean Launcher.dat? Or is there some other file I am not aware of?
 
If you are one of those people that does not enable WiFi on their 3DS to avoid system updates and prompts, you are going to need to enable it long enough somewhere your 3DS has an internet connection for the update to be downloaded. DO NOT UPDATE FROM THE PROMPT, USE IT ONLY AS AN INDICATION THAT YOU HAVE ALREADY DOWNLOADED THE UPDATE. If you have not been nagged at some point about a new system update your not ready to go, or at the minimum you will have to leave WiFi on in step 9, which may be dangerous but I'm not sure why.

So you have to set up your wifi in 3DS mode and wait for the system notification that there are new FW to update? Then you will be able to do all the steps? Some people say they just set up wifi when they in GW mode and do not have to wait for the notification for system update.
 
why the hell do you need a video tutorial for something like this?
how is it even possible to do it wrong?!
even without a tutorial its self explaining and simple.

setup you damn emunand and activate your wifi connection, load gwmode and update the emunand, I dont get it how you guys still manage to screw this up.

the only important thing is to check if you are really in gwmode before hitting the update button and never ever leave the system settings before you update.
 
So you have to set up your wifi in 3DS mode and wait for the system notification that there are new FW to update? Then you will be able to do all the steps? Some people say they just set up wifi when they in GW mode and do not have to wait for the notification for system update.

From what I've been reading from some of the screw ups, they would not have happened if the person had the new update already downloaded before starting, and that is the only indication I know to tell someone that they have. I'm trying to make this as safe as possible.

Do you HAVE TO wait for a notification? No, but doing so removes just one more of the things that seem to be going wrong for people.
 
From what I've been reading from some of the screw ups, they would not have happened if the person had the new update already downloaded before starting, and that is the only indication I know to tell someone that they have. I'm trying to make this as safe as possible.

Do you HAVE TO wait for a notification? No, but doing so removes just one more of the things that seem to be going wrong for people.

Wouldn't the new update gone when you format emunand which format your memory card?
 
From what I've been reading from some of the screw ups, they would not have happened if the person had the new update already downloaded before starting, and that is the only indication I know to tell someone that they have. I'm trying to make this as safe as possible.

Do you HAVE TO wait for a notification? No, but doing so removes just one more of the things that seem to be going wrong for people.
I had to set up my internet connection and download the whole update.
everything works like a charm, so I can confirm you wont mess up if you download it in gwmode.
 
Wouldn't the new update gone when you format emunand which format your memory card?

No, it is still stored in the 3DS's flash memory. If you remove your SD, your 3DS will still nag you that it is ready to update if it has downloaded one.

The reason I recommend having the update already downloaded is to remove the need to mess around in the system menu at all. I've just read enough "and then I did this" which kicked them out of GW mode w/o them realizing it. This way the EULA should already be accepted, you don't need to set up WiFi settings if you chose to remove them, etc... One can go straight to the update after insuring that they see the GW3D and there is no room for the mistakes people seem to be making. It is not required, just a minor safeguard for the above reason and that's why I put it there, and as an added bonus you can leave your WiFi off (and your connections settings remove if you choose to do so) through the whole process.

I really don't want someone to say, "I did what KidIce said and now my sysNAND is on 6.3!!"
 
No, it is still stored in the 3DS's flash memory. If you remove your SD, your 3DS will still nag you that it is ready to update if it has downloaded one.

The reason I recommend having the update already downloaded is to remove the need to mess around in the system menu at all. I've just read enough "and then I did this" which kicked them out of GW mode w/o them realizing it. This way the EULA should already be accepted, you don't need to set up WiFi settings if you chose to remove them, etc... One can go straight to the update after insuring that they see the GW3D and there is no room for the mistakes people seem to be making. It is not required at all, just a minor safeguard for the above reason and that's why I put it there.

okay, thank you for clean thing up for me, so system update will download just by open up wifi even if you didn't accept the update?
 
If your 3DS can make a WiFi connection and you have already accepted the EULA by playing in the plaza or some such it will try to download an update, even in a Nintendo Zone. If you are at a McDonald's, your WiFi is enabled and there is a new update, your 3DS will download it if you are there long enough for it to do so.
 
why the hell do you need a video tutorial for something like this?
how is it even possible to do it wrong?!
even without a tutorial its self explaining and simple.

setup you damn emunand and activate your wifi connection, load gwmode and update the emunand, I dont get it how you guys still manage to screw this up.

the only important thing is to check if you are really in gwmode before hitting the update button and never ever leave the system settings before you update.
They aren't saying they are likely to mess it up... They are saying that if, by some small chance, they mess up, the effects will be disastrous. It's still a high risk in that regard, and people just want to be extra 100% sure. I honestly can understand that.
 
Well I just lost about 45 minutes of Zelda progress. Funny thing is, the save file didn't corrupt, it just dumped me back several saves past.

Yeah... I think I'll be waiting for the finished 2.0 release. This beta can't even 'close software' properly.
 

Site & Scene News

Popular threads in this forum