didn't know that. thanksYou can no longer use 3DNUS to download the 9.2 update files, Nintendo removed them from their servers which 3DNUS relied on. You can find the 9.2 update files on "some iso site."
didn't know that. thanksYou can no longer use 3DNUS to download the 9.2 update files, Nintendo removed them from their servers which 3DNUS relied on. You can find the 9.2 update files on "some iso site."
Have you tried installing FBI via FBI injection? Maybe rxTools isn't liking the HBL version for some reason.
The version of rxTools you're using might need you to hold L instead of R, they changed it on one of the releases.What methods are there to do so? I've looked at this: https://gbatemp.net/threads/release...ect-generator-jpn-usa-eur-chn-kor-twn.391525/
But it turns out that the folder 00020300 isn't in the img file.
I've also tried looking at rxTools, but when I boot from it using HBL, I tried holding R but still boots into emunand.
As it says, it's not necessary to update emuNAND to follow the tutorial, but if you plan on updating emuNAND you might as well do it at that point.ok, so yesterday I was told to follow this tutorial
https://gbatemp.net/threads/tutorial-installing-rxtools-custom-firmware-3ds-and-2ds.390867/
in order to install a CFW to run 3ds roms on my 2ds with 7.2.0-17E firmware and I have a question about step 3:
at the end of the step it says "At this point, you may update your emunand to 10.3 before continuing to step 4a (specifically), although you don't have to if everything works out. Read the guidelines below in the emunand section first."
Do I need to do that?
I have no gateway or cubic ninja (and I don't really know what they are...)
Thanks a million
And what's the point on updating emuNAND?As it says, it's not necessary to update emuNAND to follow the tutorial, but if you plan on updating emuNAND you might as well do it at that point.
EmuNAND allows you to play games that require a higher firmware without actually updating your 3DS. So if you plan on playing games that have come out more recently, you'll want to update it.And what's the point on updating emuNAND?
Sorry, i'm a noob at this.
Do you recomend me to do it? I have 7.2.0-17E firmware (i'm not even sure if what i'm asking is reasonable)EmuNAND allows you to play games that require a higher firmware without actually updating your 3DS. So if you plan on playing games that have come out more recently, you'll want to update it.
Yes, I would recommend updating emuNAND.Do you recomend me to do it? I have 7.2.0-17E firmware (i'm not even sure if what i'm asking is reasonable)
Is that possible on N3DS, too?Yes, I would recommend updating emuNAND.
For the N3DS you'll need to use SysUpdater and follow these instructions:Is that possible on N3DS, too?
To update emuNAND, download the 9.5.0-23 update cias from "some iso site." I'd reccomend backing up your emuNAND with EmuNAND Tool before doing this.
1. Create a folder on the root of your 3DS's SD card named "updates" without the quotes.
2. Place all of the update cias inside the "updates" folder.
3. Download SysUpdater and place the SysUpdater cia on the root of your SD card.
4. Boot emuNAND and use the cia installer of your choice to install the SysUpdater cia.
5. Launch SysUpdater and press the A button to update. Once it finishes reboot your 3DS. Your emuNAND should now be 9.5.0-23!
The only way you could've bricked is by using SysUpdater in sysNAND. It wouldn't brick your 3DS if something went wrong in emuNAND. Did you enter the system settings before launching SysUpdater? If you entered the system settings you would've been kicked back to sysNAND.Well, in regards to my earlier question, I think I may have bricked my 3ds. I copied the files into the update folder, installed and ran sysupdater, it installed without problems, said it would reboot in 10 seconds, and upon reboot my 3ds is at a black screen with the top screen completely black and the bottom screen has the brightness flicker on every 5 seconds or so. Am I completely boned? And what could have possibly went wrong? I am completely sure I was in emunand when I did everything. This is why I posted before I did anything...
I didn't go into settings and was NOT in sysnand. I booted my 3ds, went to ds-> profile and booted into gateway's emunand. I pressed select and opened bbm. In bbm, I installed sysupdater then pressed the home button to return to the dashboard and then clicked on the gift with sysupdater in it, started it, and pressed A. It said rebooting in 10 seconds, the screen went black, and that was all she wrote.The only way you could've bricked is by using SysUpdater in sysNAND. It wouldn't brick your 3DS if something went wrong in emuNAND. Did you enter the system settings before launching SysUpdater? If you entered the system settings you would've been kicked back to sysNAND.
If you're 100% sure that the 3DS is bricked, you can perform a hardmod and flash a NAND backup to the 3DS as long as you've got one.
Sounds like a brick, I'd double check to verify that it won't turn on though. I don't know how SysUpdater could've bricked your console from emuNAND; that should be impossible (once you're in emuNAND, NAND writes and reads are redirected to the SD card, so the actual NAND shouldn't ever be touched). I've used it many times and never had any issues.I didn't go into settings and was NOT in sysnand. I booted my 3ds, went to ds-> profile and booted into gateway's emunand. I pressed select and opened bbm. In bbm, I installed sysupdater then pressed the home button to return to the dashboard and then clicked on the gift with sysupdater in it, started it, and pressed A. It said rebooting in 10 seconds, the screen went black, and that was all she wrote.
Is the symptom I described not a brick?
For the N3DS you'll need to use SysUpdater and follow these instructions: