can i get my otp when i dgrade my emunand to 2.1??? or do i have to do it with sysnand? (in other threads they are ignoring me )
No because to get into emunand you have to load a higher firmware first(9.2) for your hax. After this the OTP is already locked.can i get my otp when i dgrade my emunand to 2.1??? or do i have to do it with sysnand? (in other threads they are ignoring me )
if your showing the benefits of it, go ahead already. we dont really care about what you do with your system
thats why I didn't put a theme on emunand
--------------------- MERGED ---------------------------
It seems like there isn't a full definition on getting it up and running and working (at least from that thread and what I've seen elsewhere), however, and how to do specific things with it. I'm going to wait until its fully developed and there are more tutorials to do specific things with it.
can i get my otp when i dgrade my emunand to 2.1??? or do i have to do it with sysnand? (in other threads they are ignoring me )
Here is the full info on the differences in methods:
All things considered, it sounds far scarier than it looks. It is all relatively safe, and I would definitely do your research to fully take advantage of what you need. A9LH isn't necessary if you just want emulators, for example.
- HomeMenuHax or any other LESShax-based exploit takes advantages of miscellaneous bugs in the existing 3DS software, resulting in the ability to run basic code like the Homebrew Menu. It does not give you access to lower-level system stuff, so you can't install pirated games/custom home menu stuff but you can run homebrew such as emulators. No system files are modified, and this is very, very safe.
- Custom Firmware and emuNAND/emulated NAND is a file backup of your existing NAND that the Nintendo 3DS can't tell is being run off of the SD card. In order to launch an emuNAND, you need a custom firmware, which is fancy verbiage for "more exploits". Using an exploit like the ones described above, a secondary exploit is run that allows custom code to run on the system menu. This allows some level of piracy and such and allows you to install homebrew CIA files (which are just compressed packages of game content, like how an eShop game would appear on your home menu). This can modify system files, but it is still safe unless you go out of your way to blow it up.
- A9LH, or ARM9 Loader Haxx, goes even further - the last version of the Nintendo 3DS firmware files that had an exploit that gave full system control was version 2.1. A9LH requires you to downgrade to frankenstein together a version of 2.1 that will run on an N3DS and can be used to modify a newer firmware file. Once you reach that point, you get OTP.bin, which is simply the exploitable system files that are needed to re-introduce those exploits on newer firmwares. Because firmware files are marked with which console installed them, you can not use this file from somebody else's 3DS. Once you have this file, you flash the firmware you originally were running to get back to a normal system.
What the A9LH installer does (once it is compiled and run) is that it goes into the boot process and pretty much blows up half of it. This results in the 3DS looking to the next part of the boot process for a fallback, at which point A9LH provides it custom boot code rather than the actual 3DS boot code that normally would exist. This gives ARM9 access to the system, meaning all kinds of fun things can be done with the full control we have.
The A9LH process is relatively safe if you know exactly what you are doing and are diligent to not make silly mistakes. Unlike other processes, recovery isn't really possible, as you'll botch your system's ability to boot if you mess up. Proceed with caution if you are at any step and feel you are in over your head.
well my sysnand ain't changing anytime soon, so I'll get it when I need it. I'll also probably have to wait for an actual build that explicitly states how to use it and do certain things with it installed instead of that one thread where the OP just listed the possibilities of it and suddenly its like everyone there somehow magically got a working copy of it that they know everything about.Well, I'm not telling you to use it right now but to be prepared to use it when the right time comes for you
Like, get the otp.bin now and save it somewhere safe and wait the A9LH homebrews to get more mature to start using it
well my sysnand ain't changing anytime soon, so I'll get it when I need it. I'll also probably have to wait for an actual build that explicitly states how to use it and do certain things with it installed instead of that one thread where the OP just listed the possibilities of it and suddenly its like everyone there somehow magically got a working copy of it that they know everything about.
Safer? Probably not. The current guide is as safe as it's gonna get (most likely anyways). Unless CFW devs support 2.1 emuNAND, but that's kind of a waste of time.Im sure that whiten the next 2 weeks there will be a "safer" or "easier" way to do it.
Also don't listen to the "Emunand is useless" comments.
While it is unlikely, Nintendo could throw out an update that stops this in its tracks, at least initially before someone fixes it.
Switch to sysnand and update if you want (It's faster than emunand), but always keep a bare-bones 9.2 Emunand on your SD that you can boot to, and always check on forums if it's ok to update Sysnand before doing so.
im just being honest with him, so yo shouldnt concern yourself or anythingno need to be rude.
im just being honest with him, so yo shouldnt concern yourself or anything
the OP clearly stated benefits of using A9LH. so i dont know why he/she made this threadHonesty has nothing to do with it,you don't call every fat person you see fat do you?The OP is asking a simple question,if you don't want to answer it in a polite manner don't bother posting on the thread.