diff --git a/dumping-movable-(nimhax).html b/dumping-movable-(nimhax).html index 4fb41c36a7..0d2b9aad8e 100644 --- a/dumping-movable-(nimhax).html +++ b/dumping-movable-(nimhax).html @@ -495,6 +495,8 @@ window.cookieconsent.initialise({
If you are using Luma3DS, your custom firmware loader (boot9strap) will never be removed when performing a system update. There have been updates in the past that have resulted in Luma3DS crashing on boot, so it is a good idea to wait a couple of hours to ensure that the latest update will not temporarily render the device unusable until Luma3DS is updated. System updates can be performed the same way as they are on a stock 3DS: through System Settings, Safe Mode, or the update prompt when the update is automatically downloaded.
+If you are using Luma3DS, your custom firmware loader (boot9strap) will never be removed when performing a system update. There have been updates in the past that have resulted in Luma3DS crashing on boot, so it is a good idea to wait a couple of hours to ensure that the latest update will not temporarily render the device unusable until Luma3DS is updated. System updates can be performed the same way as they are on an unmodified 3DS: through System Settings, Safe Mode, or the update prompt when the update is automatically downloaded.
Yes, system transfers can be performed through the official System Transfer function to other consoles with CFW (inconsistencies may occur if the target console is stock). Tickets for illegitimate titles (homebrew) will not transfer, but the titles can be made to reappear with faketik. Make sure that you do not perform a wireless transfer, as this will delete illegitimate titles. CFW will remain on both consoles.
+Yes, system transfers can be performed through the official System Transfer function to other consoles with CFW (inconsistencies may occur if the target console is unmodified). Tickets for illegitimate titles (homebrew) will not transfer, but the titles can be made to reappear with faketik. Make sure that you do not perform a wireless transfer, as this will delete illegitimate titles. CFW will remain on both consoles.
In this section, you will visit the browser exploit webpage, which will launch the Homebrew Launcher.
diff --git a/images/screenshots/hblusm-root-layout.png b/images/screenshots/hblusm-root-layout.png index bcbea0894a..d0899ec3e4 100644 Binary files a/images/screenshots/hblusm-root-layout.png and b/images/screenshots/hblusm-root-layout.png differ diff --git a/images/screenshots/nimhax-location.png b/images/screenshots/nimhax-location.png new file mode 100644 index 0000000000..9f3fe5a877 Binary files /dev/null and b/images/screenshots/nimhax-location.png differ diff --git a/images/screenshots/skater-root-layout.png b/images/screenshots/skater-root-layout.png new file mode 100644 index 0000000000..59ad952778 Binary files /dev/null and b/images/screenshots/skater-root-layout.png differ diff --git a/installing-boot9strap-(hbl-usm).html b/installing-boot9strap-(hbl-usm).html index dbe330ed89..fdce44d8ae 100644 --- a/installing-boot9strap-(hbl-usm).html +++ b/installing-boot9strap-(hbl-usm).html @@ -488,11 +488,7 @@ window.cookieconsent.initialise({boot9strap
on the root of your SD cardboot9strap.firm
and boot9strap.firm.sha
from the boot9strap .zip
to the /boot9strap/
folder on your SD cardSafeB9SInstaller.bin
from the SafeB9SInstaller .zip
to the root of your SD cardusm.bin
from the unSAFE_MODE .zip
to the root of your SD cardusm.bin
to the root of your SD card