Hacking Failed to apply 1 Firm patch(es).

[PrimordialDusknoir]

Hey, so I recently got a bigger sd card, so I copy and pasted all the files from the old sd card to the new one. But now whenever I turn on my 3ds (while new sd card is in), it says "An error has ocurred: Failed to apply 1 Firm patch(es). Press any button to shutdown" (This doesn't occur when I have the old sd card in, btw). From what I've found online, I'm supposed to download the most recent boot.firm for Luma, and then put it on the root of the sd card, thus overwriting the old boot.firm, but that doesn't change anything, I still get the exact same error when I turn my 3ds on. I am on Luma v8.1.1 and in the Luma configuration menu, "enable loading external FIRMS and modules" is checked.

 

[TurdPooCharger]

Your SD card needs to be formatted FAT32 + 32 KB cluster size in order for the 3DS to read it. If it's bigger than 32 GB, use guiformat.

For a thorough rundown on checking whether your newly purchased card is fake, updating the custom firmware on both SD card and CTRNAND, and making backups of your most important data, follow this post.

 

[PrimordialDusknoir]

Formatting my new sd card resolved the issue, thank you so much!

 

[lAkdaOpeKA]

Formatting my new sd card resolved the issue, thank you so much!

You might also want to update the Luma3DS FIRM on your CTRNAND since it looks like it's out of date. Instructions are on section VI of this page

 

[PrimordialDusknoir]

So when I go to section VI of that guide, I get stuck on the 6th step, bc when I press the home button, there is no "scripts" option.

 

[lAkdaOpeKA]

So when I go to section VI of that guide, I get stuck on the 6th step, bc when I press the home button, there is no "scripts" option.

You didn't copy the gm9 folder

 

[PrimordialDusknoir]

You didn't copy the gm9 folder

Thank you for letting me know what the issue was! Luma3ds on my 3ds is now successfully updated to v9.1

 

[firewraith]

so i looked at the site that you gave and how important is "Backup your SysNAND image and save this somewhere on your computer or external drive." i dont have enough space to do it using a 64 gb

--------------------- MERGED ---------------------------

sorry, this is new. that was for TurdPoocharger. using the process, what can be deleted safely and disrupt the software?

 

[TurdPooCharger]

so i looked at the site that you gave and how important is "Backup your SysNAND image and save this somewhere on your computer or external drive." i dont have enough space to do it using a 64 gb

sorry, this is new. that was for TurdPoocharger. using the process, what can be deleted safely and disrupt the software?

As said best by

There are two kinds of data:
* data you have backed up multiple times
* unimportant data
No backup? No sympathy/pity!

Yes, that sounds harsh/mean or even cruel. But it has an element of truth in it. Please keep your data save by copying it on time.
Trying to recover often fails and is a lot more work than making backups.

For peace of mind, get yourself a spare SD card, flash drive, or external portable hard drive for the express purpose of backing up your data. Look at Amazon or my signature as a starting reference.
If money's tight, there's cloud storage using Google drive. There's absolutely no excuse in NOT backing up important files.

• SysNAND *.bin image: Creating a NAND Backup
  
• Games, updates, and DLCs: Dumping a Title
• 3D game saves + extdata: Checkpoint or JKSM
• GBA Virtual Console saves: Backup GBA VC Saves
• DSiWare saves: [Tutorial] How to perform a System Transfer without losing non-legitimate titles [post #9]

 

[firewraith]

ok. with dumping a title, what does it mean to move it to .cia? Also, in order, what would the back up files from the above look like on the sd card? so that i coud back it up.

--------------------- MERGED ---------------------------

ok. with dumping a title, what does it mean to move it to .cia? Also, in order, what would the back up files from the above look like on the sd card? so that i coud back it up.

for TurdPooCharger

 

[ParseThisCode]

I had same issue. If You have gm9 and backup previous boot.firm, ie. boot.firm.bak, then on boot hold START, on gm9 select backup firm, then image options and boot firm. This will boot to home menu. In FBI remove boot.firm which prevents to boot, then rename boot.firm.bak to boot.firm. Next reboot will works