diff --git a/FAQ-and-Troubleshooting.md b/FAQ-and-Troubleshooting.md
index c50c394..5604de1 100644
--- a/FAQ-and-Troubleshooting.md
+++ b/FAQ-and-Troubleshooting.md
@@ -11,7 +11,7 @@ Your payload is out of date. You can get the latest version for Decrypt9/EmuNAND
 If your Old 3DS/Old 3DS XL has been downgraded to 4.5 from the Gateway menu in the past, your CTRNAND has leftovers from one or more previous FIRMs, and this causes issues with the CTRNAND code. This is not an issue with Luma itself, but rather with the GW downgrade process which doesn't do any cleanup and leaves CTRNAND in a messy state.
 Thankfully there's a method for cleaning your CTRNAND (at least the parts required by Luma3DS to operate normally):
 
-1. Get the FIRM .bins package from [here](http://www70.zippyshare.com/v/Fbj6n1vB/file.html) and the NAND FIRMs package from [here](http://www64.zippyshare.com/v/deaIdQMn/file.html)
+1. Get the FIRM .bins package from [here](http://www42.zippyshare.com/v/aqbG6Hlj/file.html) and the NAND FIRMs package from [here](http://www64.zippyshare.com/v/deaIdQMn/file.html)
 2. Copy the O3DS `firmware.bin` file from the FIRM .bins package to the `luma` folder
 3. From the NAND FIRMs package, copy `O3DS NATIVE.cia`, `O3DS AGB.cia` and `O3DS TWL.cia` to the SD card
 4. Boot the NAND you need to fix