(Sorry if this is the wrong thread, since this is my first time here.)
So, I’ve recently put files from a 3DS Development Kit onto my retail Nintendo 3DS XL’s SysNAND via FBI, (since I was too lazy to get an EmuNAND back then), and booted it up. It had DevMenu 11.4 and Config and CTRAging v1 and all that. But, when I went to Luma3DS’s Configuration Menu, and enabled the Developer Mode, it would soft-brick, (Likely because I enabled the Test Menu with Dev2 on Config, while on Developer Mode) and I’d have to perform a hard reset and go back to the Luma3DS configuration menu and disable Developer Mode. Anyways, after I stupidly installed Development Kit files onto my Retail System, I booted up some apps to test it out. My digital games were booting fine, FBI and HBL were booting perfectly, so I tested out the ‘DS-Mode’ by going onto ‘Download Play’, booting up the ‘Nintendo DS’ setting, and seeing if it would load. It loaded perfectly fine, and the clock and calender still displayed the accurate time. But, when I went to exit out of the DS Download Play, a Luma3DS error popped up, displaying ‘An error has occurred: Failed to apply 1 FIRM patch(es). Press any button to shutdown’, so I pressed ‘A’, shutting it down. Now, I thought the problem was that I was on the Retail Mode instead of Developer Mode, so I went to the Luma3DS configuration menu, enabled Developer Mode, and booted it up. The splash screen was there, and I could still boot up GodMode9, but when it booted up, It was the same error screen as before, but it said ‘Failed to apply 2 FIRM patch(es)’, instead of 1. Now, I searched the internet for this, but I could only find a thread about this one dude trying to boot up TwilightMenu++, and getting ‘Failed to apply 4 FIRM patch(es)’, so it was a no-go. Also, keep in mind, when I tried to boot up ‘Recovery Mode’, (or ‘Safe Mode’), it would go through the update stuff, and the prompt for the TOS and COPPA stuff blah blah blah, but when I updated it with INTERNET CLEARLY BEING AT FULL 3 BARS, it would say ‘an error has occurred with the update, please shutdown your console’, or something like that. But now, when I try to boot the Recovery/Safe Mode up, it just says the same error, ‘Failed to apply 1 FIRM patch(es)’. (Yes, it still says ‘2’ instead of ‘1’ while on Developer Mode). Now, also keep in mind, when I tried installing it through sysupdater (CIA version), it didn’t work. When I tried DevMenu (11.4 & this older version that I have), also didn’t work. However, FBI did work, so I installed it through that, instead of sysupdater. I tried updating Luma3DS, (I updated to both the latest Hourly & Nightly versions and it still wouldn’t work, shocker.), I tried updating every single thing that I had, which didn’t work, since they were already on the latest versions, (again, what a shocker.). I even updated to the latest version of my 3DS’S firmware via GodMode9 and it still didn’t work. I even deleted unnecessary files, and sysupdater.cia. Yes, I have the latest boot.firm of both the Luma3DS Hourly & Nightly on my SD Card. Yes, it has enough space, it’s a 32GiB card with 16 GiB left. Yes, HBL is at the latest version, the boot.3dsx from luma3DS and HBL. I even tried ntrboot by holding a magnet in the middle of the B and power buttons and holding Start, Select, and X, simultaneously, while having New Super Mario Bros. (DS), then Super Mario 64 DS in the cartridge slot, which did nothing but automatically power it off, or simulate a soft-brick. I haven’t played any homebrew or games or virtual console on my 3DS for 3-4 whole days because of this, which I personally think is the worst punishment ever for somebody who’s modded both a RVL-001 Wii, a Model 1 Nintendo Switch, and a 3DS XL, i.e.: Me. So I really need to get this fixed because I think I’ve hard-bricked my 3DS with no way of getting back. If somebody has a solution to this, or a way to bypass this error screen, (Yes, I was thinking about messaging/emailing one or more of the Luma3DS developers about this problem), then please PLEASE tell me, because I am in fear that I might’ve hard-bricked my 3DS, with NO WAY OF GOING BACK, at least that’s what I fear. So, please, if anyone has had a similar issue, or has a possible solution to this, (such as a way to bypass the error screen), then please, tell me!
So, I’ve recently put files from a 3DS Development Kit onto my retail Nintendo 3DS XL’s SysNAND via FBI, (since I was too lazy to get an EmuNAND back then), and booted it up. It had DevMenu 11.4 and Config and CTRAging v1 and all that. But, when I went to Luma3DS’s Configuration Menu, and enabled the Developer Mode, it would soft-brick, (Likely because I enabled the Test Menu with Dev2 on Config, while on Developer Mode) and I’d have to perform a hard reset and go back to the Luma3DS configuration menu and disable Developer Mode. Anyways, after I stupidly installed Development Kit files onto my Retail System, I booted up some apps to test it out. My digital games were booting fine, FBI and HBL were booting perfectly, so I tested out the ‘DS-Mode’ by going onto ‘Download Play’, booting up the ‘Nintendo DS’ setting, and seeing if it would load. It loaded perfectly fine, and the clock and calender still displayed the accurate time. But, when I went to exit out of the DS Download Play, a Luma3DS error popped up, displaying ‘An error has occurred: Failed to apply 1 FIRM patch(es). Press any button to shutdown’, so I pressed ‘A’, shutting it down. Now, I thought the problem was that I was on the Retail Mode instead of Developer Mode, so I went to the Luma3DS configuration menu, enabled Developer Mode, and booted it up. The splash screen was there, and I could still boot up GodMode9, but when it booted up, It was the same error screen as before, but it said ‘Failed to apply 2 FIRM patch(es)’, instead of 1. Now, I searched the internet for this, but I could only find a thread about this one dude trying to boot up TwilightMenu++, and getting ‘Failed to apply 4 FIRM patch(es)’, so it was a no-go. Also, keep in mind, when I tried to boot up ‘Recovery Mode’, (or ‘Safe Mode’), it would go through the update stuff, and the prompt for the TOS and COPPA stuff blah blah blah, but when I updated it with INTERNET CLEARLY BEING AT FULL 3 BARS, it would say ‘an error has occurred with the update, please shutdown your console’, or something like that. But now, when I try to boot the Recovery/Safe Mode up, it just says the same error, ‘Failed to apply 1 FIRM patch(es)’. (Yes, it still says ‘2’ instead of ‘1’ while on Developer Mode). Now, also keep in mind, when I tried installing it through sysupdater (CIA version), it didn’t work. When I tried DevMenu (11.4 & this older version that I have), also didn’t work. However, FBI did work, so I installed it through that, instead of sysupdater. I tried updating Luma3DS, (I updated to both the latest Hourly & Nightly versions and it still wouldn’t work, shocker.), I tried updating every single thing that I had, which didn’t work, since they were already on the latest versions, (again, what a shocker.). I even updated to the latest version of my 3DS’S firmware via GodMode9 and it still didn’t work. I even deleted unnecessary files, and sysupdater.cia. Yes, I have the latest boot.firm of both the Luma3DS Hourly & Nightly on my SD Card. Yes, it has enough space, it’s a 32GiB card with 16 GiB left. Yes, HBL is at the latest version, the boot.3dsx from luma3DS and HBL. I even tried ntrboot by holding a magnet in the middle of the B and power buttons and holding Start, Select, and X, simultaneously, while having New Super Mario Bros. (DS), then Super Mario 64 DS in the cartridge slot, which did nothing but automatically power it off, or simulate a soft-brick. I haven’t played any homebrew or games or virtual console on my 3DS for 3-4 whole days because of this, which I personally think is the worst punishment ever for somebody who’s modded both a RVL-001 Wii, a Model 1 Nintendo Switch, and a 3DS XL, i.e.: Me. So I really need to get this fixed because I think I’ve hard-bricked my 3DS with no way of getting back. If somebody has a solution to this, or a way to bypass this error screen, (Yes, I was thinking about messaging/emailing one or more of the Luma3DS developers about this problem), then please PLEASE tell me, because I am in fear that I might’ve hard-bricked my 3DS, with NO WAY OF GOING BACK, at least that’s what I fear. So, please, if anyone has had a similar issue, or has a possible solution to this, (such as a way to bypass the error screen), then please, tell me!
