Hacking Creating a North American, non-XL New 3DS
- Thread starter Wowfunhappy
- Start date
- Views 147,935
- Replies 908
- Likes 5
Well, I can't update using a rom (console freezes), and I can't play N3DS games (Xenoblade tells "this gamecard cannot be read" error)
Gonna keep trying until I can do it!
Gonna keep trying until I can do it!
did you uninstall the JPN keyboard? maybe having more than one installed is causing the issue, on a side not its kind of weird that the safe mode keyboard is n3ds unique yet the standard keyboard actually uses the same title as the o3DS, idk, but if you moved from JPN to US see if removing 000400300000C002 and 000400302000C003 has any effect (also making sure that 000400300000C802 and 000400300000C803 have be installed properly too)
wow are you going for the record of most system apps installed on one systemWell, I can't update using a rom (console freezes), and I can't play N3DS games (Xenoblade tells "this gamecard cannot be read" error)
Gonna keep trying until I can do it!
One can dream of having a JP SysNAND and a US EmuNAND. But getting all the JP titles to the New 3DS would be a bit of a pain. Especially purchases. Unless EmuNAND transfer and install EmuNand titles to sysnad is a thing. I'd love to have one SINGLE 3DS instead of having a big 3ds xl that I cannot take with me.
It's just what I had and what I got rid of.
If you wanted that why not just import a Japanese 3DS?
I do have a Japanese 3DS. The question I was trying to ask if I could do a system transfer from SysNAND to EmuNAND, then install everything to sysNAND (on the N3DS), then region change the EmuNAND to US and transfer my US 3DS to the EmuNAND.
To clarify, is 3DSInstallTickets only for use on sysNAND, or can it be done via Cubic on classic mode or something?
Okay, I'm somewhat hesitant to say this, but I'm going to encourage everyone who's trying to do a region change to hold off for a bit—or at the very least, don't switch back and forth.
Some of you may have seen this thread which I made yesterday—I didn't post it here because I didn't think it was related to region changing. I figured it had something to do with my NAND hardmod.
The thing is, my NAND mod is working fine, and I've talked with a couple of knowledgable people who have no idea what's going on. This leaves me with a semi-bricked system that can't be fixed by restoring from a NAND backup.
What really worries me though is if this problem is happening between different NANDs, it also means that using EmuNAND may not be enough to keep you safe.
Obviously, this stuff always comes with a huge "do at your own risk" warning, but I feel semi-responsible since I created this thread, and have really been encouraging others to try it.
Some of you may have seen this thread which I made yesterday—I didn't post it here because I didn't think it was related to region changing. I figured it had something to do with my NAND hardmod.
The thing is, my NAND mod is working fine, and I've talked with a couple of knowledgable people who have no idea what's going on. This leaves me with a semi-bricked system that can't be fixed by restoring from a NAND backup.
What really worries me though is if this problem is happening between different NANDs, it also means that using EmuNAND may not be enough to keep you safe.
Obviously, this stuff always comes with a huge "do at your own risk" warning, but I feel semi-responsible since I created this thread, and have really been encouraging others to try it.
So, even if we just work in emuNAND, there's still a chance we "semi-brick" our consoles, or is this a "better safe than sorry" situation?
I don't know at this point—I'm am using sysNAND after all—but I think that it could.
Using EmuNAND is essentially the same thing as switching between different NAND backups, and for me, the issue is persisting across backups.
Using EmuNAND is essentially the same thing as switching between different NAND backups, and for me, the issue is persisting across backups.
I've already decided to stop trying. I can't get BRM to uninstall anything, and it seems to be deleting the wrong things some times and causes my emunand to brick. I've also not been able to get 3DSInstallTickets to run properly.
I guess I'll just wait until more research is done on this.
I guess I'll just wait until more research is done on this.
Well guess I got somewhat lucky. Nothing seems to be crashing on my emuNAND (tested amiibo, notifications, etc.) running 9.5U now.
Only thing is, even after running the Codename STEAM 9.4 and 3DNUS 9.5 update methods, I seem to be without a fair amount of the default system apps (StreetPass Mii Plaza, Mii Maker, etc.)
Can these be installed manually via CIA, or is there more to it?
Only thing is, even after running the Codename STEAM 9.4 and 3DNUS 9.5 update methods, I seem to be without a fair amount of the default system apps (StreetPass Mii Plaza, Mii Maker, etc.)
Can these be installed manually via CIA, or is there more to it?
They need to be installed manually via CIA, as they've never been updated for the N3DS. In other words, this is expected.
Note that this is where you can have freezing issues when you suspend software—make sure to uninstall the old versions of Streetpass Mii Plaza, Mii Maker, and AR Games with Big Red Menu.
They can, yes. Get their TitleIDs here and download with 3DNUS. http://3dbrew.org/wiki/Title_list
Make a backup of your emunand first though since it's working! After you install those they might cause freezing/etc. Unless you've uninstalled the original region's equivalents already.
Thanks for the quick replies! Yes, the original E region versions have been removed via (several attempts with) BRM.
I'll go ahead and back things up, give it a shot, and report back. Thanks again!
You're welcome. Again, I advise against switching back to EU if you can avoid it, and setting up or linking any NNIDs.
Damn, so close yet so far. I did the injection of SecureInfo_A yesterday and got a lot of dupped apps and an unstable system, but today it seems I've snapped something during the use of BRM, because not either unxoring or using 3DSFat16tools seems to work with my emuNAND dump to extract the fat16 partition. I even deleted the old emuNAND I made yesterday and after a lot of stuff in my Recycle Bin, I don't know which one was. Heck, I just want to use my N3DS
I hate my life
I hate my life
Aaand we're good!
So at this point, HYPOTHETICALLY if I removed the remaining E region sysapps, would there be anything that would necessarily prevent me from dumping the emuNAND and writing it to sysNAND? Assuming I don't run into what happened to you wowfunhappy, anything going wrong would be repairable via hardmod and older dumps, correct?
So at this point, HYPOTHETICALLY if I removed the remaining E region sysapps, would there be anything that would necessarily prevent me from dumping the emuNAND and writing it to sysNAND? Assuming I don't run into what happened to you wowfunhappy, anything going wrong would be repairable via hardmod and older dumps, correct?
Wait for others to confirm before you do it, but I don't think there should be—If you've installed all the US CIAs, emuNAND has all the FIRMs installed, which makes it flashable. Others in this thread have done it successfully.
Edit: If you're using SysNAND anyway, I still think that installing US titles via NTR is a lot cleaner—that way, we know for sure that we're not missing any titles that could cause problems in the future.
Then I again, I used NTR, and look where I ended up :/
Edit: If you're using SysNAND anyway, I still think that installing US titles via NTR is a lot cleaner—that way, we know for sure that we're not missing any titles that could cause problems in the future.
Then I again, I used NTR, and look where I ended up :/
Can somebody lend me a hand with the whole injection thing? I think I'm doing something wrong.
I have one folder with
I try to run the following line using cmd
The result is output.bin, but yesterday I remember I opened the file with winimage, injected the SecureInfo_A and then reinjected the file again using this line
But today, the output.bin file seems corrupted, I've tried several times opening it with winimage but it just doesn't work. I formatted the emuNAND, dumped it with emuNANDtool1.0.3, and done the xorpad like 3 times (decrypt9 took like 2 hours to do it). Am I doing somethig wrong or missing something else? Thanks in advance, I'm pulling my hair trying to think what am I doing wrong.
I have one folder with
I try to run the following line using cmd
The result is output.bin, but yesterday I remember I opened the file with winimage, injected the SecureInfo_A and then reinjected the file again using this line
But today, the output.bin file seems corrupted, I've tried several times opening it with winimage but it just doesn't work. I formatted the emuNAND, dumped it with emuNANDtool1.0.3, and done the xorpad like 3 times (decrypt9 took like 2 hours to do it). Am I doing somethig wrong or missing something else? Thanks in advance, I'm pulling my hair trying to think what am I doing wrong.
Similar threads
- Question
-
-
-
-
-
-
-
-
-
S @ salazarcosplay:@Xdqwerty FMA seemed more metaphysical. Like Alchemy was a mysterious comic phenomenon, that gave you an experience.+1
In brotherhood it seemed more direct. Like there was a "god of alchemy that" one met. And it liked humbling people -
S @ salazarcosplay:At the end of the game Ed beather Truth at his own game giving up his ability to do alchemy
-
-
-
-
-
-
-
-
S @ salazarcosplay:@Xdqwerty good. thats great fma takes more time to to build up the beginning. brotherhood rushed the beginnign because the beginning had already been told+1
-
-
-
-
-
-
-
