From 9455d8d1048ea9db297ebd6c1215b8bcf76320d0 Mon Sep 17 00:00:00 2001 From: lifehackerhansol Date: Tue, 16 Jan 2024 17:24:59 +0000 Subject: [PATCH] =?UTF-8?q?Deploying=20to=20gh-pages=20from=20@=20cfw-guid?= =?UTF-8?q?e/dsi.cfw.guide@fb55f6012a7ab60ab1a8da2fb13870c1ae285d4c=20?= =?UTF-8?q?=F0=9F=9A=80?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- 404.html | 13 +-- alternate-exploits.html | 25 ++---- assets/404.7e7dd6bd.js | 1 - ....html.3e67d2f2.js => 404.html-LriIqlkn.js} | 2 +- assets/404.html-POh9F63p.js | 1 + assets/404.html.1244b7c1.js | 1 - assets/404.html.1972a2fc.js | 1 - assets/404.html.241a3bfe.js | 1 - assets/404.html.253ce897.js | 1 - assets/404.html.25cc16bb.js | 1 - assets/404.html.34559d27.js | 1 - assets/404.html.35a5a0e7.js | 1 - assets/404.html.40567751.js | 1 - assets/404.html.4dcc8308.js | 1 - assets/404.html.797ccca6.js | 1 - assets/404.html.7ac5113a.js | 1 - assets/404.html.7cffd467.js | 1 - assets/404.html.879a949d.js | 1 - assets/404.html.8b51d6f8.js | 1 - assets/404.html.a625a05b.js | 1 - assets/404.html.acaf0607.js | 1 - assets/404.html.b55b4735.js | 1 - assets/404.html.cc293232.js | 1 - assets/404.html.d5818d0d.js | 1 - assets/404.html.e8fa2dfd.js | 1 - assets/404.html.f4bf4981.js | 1 - assets/Layout.fd61c638.js | 27 ------ assets/Tab-NmAeYXh6.js | 1 + assets/Tab.1a03f8dd.js | 1 - assets/Tabs-Pu6bnuAw.js | 1 + assets/Tabs.38981e92.js | 1 - assets/alternate-exploits.html-ocXv1DJG.js | 1 + ...js => alternate-exploits.html-vBuFFl6W.js} | 2 +- assets/alternate-exploits.html.0303eb15.js | 1 - assets/alternate-exploits.html.03904bef.js | 1 - assets/alternate-exploits.html.0531607f.js | 1 - assets/alternate-exploits.html.0c805215.js | 1 - assets/alternate-exploits.html.1b51d524.js | 1 - assets/alternate-exploits.html.2f13ec14.js | 1 - assets/alternate-exploits.html.42bd011d.js | 1 - assets/alternate-exploits.html.5ffa05d0.js | 1 - assets/alternate-exploits.html.73604076.js | 1 - assets/alternate-exploits.html.7b4b059e.js | 1 - assets/alternate-exploits.html.9825c1cb.js | 1 - assets/alternate-exploits.html.998b04d6.js | 1 - assets/alternate-exploits.html.b0e5c2b0.js | 1 - assets/alternate-exploits.html.b1ad08d5.js | 1 - assets/alternate-exploits.html.b8d37145.js | 1 - assets/alternate-exploits.html.baf364ca.js | 1 - assets/alternate-exploits.html.cf2b2029.js | 1 - assets/alternate-exploits.html.d2506977.js | 1 - assets/alternate-exploits.html.dec961a5.js | 1 - assets/alternate-exploits.html.f5bec0ce.js | 1 - assets/alternate-exploits.html.f7fcddb7.js | 1 - assets/app-yIkf6V5Q.js | 48 +++++++++++ assets/app.dee26283.js | 10 --- assets/back-to-top.8efcbe56.svg | 1 - ...l.33157cef.js => credits.html-TfDvKXaR.js} | 2 +- ...l.f2bc8d43.js => credits.html-vxG94Np9.js} | 2 +- assets/credits.html.0df33721.js | 1 - assets/credits.html.1667fccf.js | 1 - assets/credits.html.3fcc009d.js | 1 - assets/credits.html.3fd1fd62.js | 1 - assets/credits.html.50dda71a.js | 1 - assets/credits.html.5d3c2db3.js | 1 - assets/credits.html.610de7b7.js | 1 - assets/credits.html.67e32b57.js | 1 - assets/credits.html.69eecd9f.js | 1 - assets/credits.html.69f8a4d1.js | 1 - assets/credits.html.7066fd3a.js | 1 - assets/credits.html.8b056ada.js | 1 - assets/credits.html.922c178b.js | 1 - assets/credits.html.99601007.js | 1 - assets/credits.html.abd83a0c.js | 1 - assets/credits.html.c139bf88.js | 1 - assets/credits.html.c15542ca.js | 1 - assets/credits.html.d2d30ca6.js | 1 - assets/credits.html.dc24af6d.js | 1 - assets/credits.html.e602a7f1.js | 1 - ...e4.js => dsiware-backups.html-4cubhJlF.js} | 2 +- assets/dsiware-backups.html-pyT4wBYB.js | 1 + assets/dsiware-backups.html.0e4842e8.js | 1 - assets/dsiware-backups.html.116cb38d.js | 1 - assets/dsiware-backups.html.2a216475.js | 1 - assets/dsiware-backups.html.2d6b1764.js | 1 - assets/dsiware-backups.html.346b41b9.js | 1 - assets/dsiware-backups.html.5011a0b9.js | 1 - assets/dsiware-backups.html.50419e33.js | 1 - assets/dsiware-backups.html.528669d2.js | 1 - assets/dsiware-backups.html.53216945.js | 1 - assets/dsiware-backups.html.627b4865.js | 1 - assets/dsiware-backups.html.742074a0.js | 1 - assets/dsiware-backups.html.8b22beff.js | 1 - assets/dsiware-backups.html.9a51bef2.js | 1 - assets/dsiware-backups.html.a6fff0cb.js | 1 - assets/dsiware-backups.html.bd22a114.js | 1 - assets/dsiware-backups.html.c3daaa30.js | 1 - assets/dsiware-backups.html.c6f26fa8.js | 1 - assets/dsiware-backups.html.d530a09e.js | 1 - assets/dsiware-backups.html.f632566c.js | 1 - assets/dsiware-backups.html.fb9a2303.js | 1 - assets/dsiware-backups.html.fe0f52aa.js | 1 - ...js => dumping-game-cards.html-BH0ZUZq_.js} | 2 +- assets/dumping-game-cards.html-S_9zIrgu.js | 1 + assets/dumping-game-cards.html.035bcec9.js | 1 - assets/dumping-game-cards.html.0f310264.js | 1 - assets/dumping-game-cards.html.0f3f183b.js | 1 - assets/dumping-game-cards.html.24136168.js | 1 - assets/dumping-game-cards.html.29060e56.js | 1 - assets/dumping-game-cards.html.33ca88d4.js | 1 - assets/dumping-game-cards.html.452e3d20.js | 1 - assets/dumping-game-cards.html.469318e4.js | 1 - assets/dumping-game-cards.html.4db772f5.js | 1 - assets/dumping-game-cards.html.6fbd3c08.js | 1 - assets/dumping-game-cards.html.944e9149.js | 1 - assets/dumping-game-cards.html.9fca2346.js | 1 - assets/dumping-game-cards.html.a0d6e45b.js | 1 - assets/dumping-game-cards.html.aa9098bd.js | 1 - assets/dumping-game-cards.html.b9857bb6.js | 1 - assets/dumping-game-cards.html.d2c61ba6.js | 1 - assets/dumping-game-cards.html.d455304d.js | 1 - assets/dumping-game-cards.html.deb8cc92.js | 1 - assets/dumping-game-cards.html.e21b5d52.js | 1 - assets/dumping-game-cards.html.ef17f70d.js | 1 - assets/dumping-game-cards.html.f9c6f36c.js | 1 - ...6c135.js => dumping-nand.html-9ppCjrZL.js} | 2 +- assets/dumping-nand.html-Iammg12x.js | 1 + assets/dumping-nand.html.1f69c4ac.js | 1 - assets/dumping-nand.html.29f3c4a9.js | 1 - assets/dumping-nand.html.351e0ec4.js | 1 - assets/dumping-nand.html.38430bea.js | 1 - assets/dumping-nand.html.38a6e01d.js | 1 - assets/dumping-nand.html.3f3961e2.js | 1 - assets/dumping-nand.html.4ecef543.js | 1 - assets/dumping-nand.html.55478a52.js | 1 - assets/dumping-nand.html.5e22f4db.js | 1 - assets/dumping-nand.html.69608bc7.js | 1 - assets/dumping-nand.html.7342b7e1.js | 1 - assets/dumping-nand.html.8c80c088.js | 1 - assets/dumping-nand.html.93d45bb5.js | 1 - assets/dumping-nand.html.98f40ec5.js | 1 - assets/dumping-nand.html.b883979b.js | 1 - assets/dumping-nand.html.bccd9c91.js | 1 - assets/dumping-nand.html.c1390a86.js | 1 - assets/dumping-nand.html.c7e47651.js | 1 - assets/dumping-nand.html.cbf1004f.js | 1 - assets/dumping-nand.html.e5ef8ca3.js | 1 - assets/dumping-nand.html.ef2f6139.js | 1 - assets/facebook-check.a40c2972.js | 1 - ....html.c7a6762f.js => faq.html-BpG_zlj5.js} | 2 +- assets/faq.html-VjmhWoRW.js | 1 + assets/faq.html.08809d7d.js | 1 - assets/faq.html.38b88ac7.js | 1 - assets/faq.html.43e45ca9.js | 1 - assets/faq.html.470e4ddc.js | 1 - assets/faq.html.4d54914c.js | 1 - assets/faq.html.50c0c142.js | 1 - assets/faq.html.53454531.js | 1 - assets/faq.html.671c32bf.js | 1 - assets/faq.html.7f47ebe8.js | 1 - assets/faq.html.85d568ad.js | 1 - assets/faq.html.972ad4a8.js | 1 - assets/faq.html.98b815b9.js | 1 - assets/faq.html.9b2c1de7.js | 1 - assets/faq.html.c592bfd9.js | 1 - assets/faq.html.d9296555.js | 1 - assets/faq.html.d96f3d18.js | 1 - assets/faq.html.e668a7a3.js | 1 - assets/faq.html.e7eed8db.js | 1 - assets/faq.html.ec2c3653.js | 1 - assets/faq.html.f3645f8c.js | 1 - assets/faq.html.f48cbbdf.js | 1 - ...file-extensions-(windows).html.1fb6ba24.js | 1 - ...file-extensions-(windows).html.5ff085f7.js | 1 - .../file-extensions-windows.html-7rJlexbx.js | 1 + .../file-extensions-windows.html-CY71hixJ.js | 1 + .../file-extensions-windows.html.04d6bf57.js | 1 - .../file-extensions-windows.html.0f860332.js | 1 - .../file-extensions-windows.html.20f37a8e.js | 1 - .../file-extensions-windows.html.2ef5df31.js | 1 - .../file-extensions-windows.html.306ed54f.js | 1 - .../file-extensions-windows.html.4986e0c7.js | 1 - .../file-extensions-windows.html.5772f0ca.js | 1 - .../file-extensions-windows.html.6aef26fc.js | 1 - .../file-extensions-windows.html.7bae9a4b.js | 1 - .../file-extensions-windows.html.845d5d61.js | 1 - .../file-extensions-windows.html.9a188dc0.js | 1 - .../file-extensions-windows.html.9aa4fc2e.js | 1 - .../file-extensions-windows.html.b1f93401.js | 1 - .../file-extensions-windows.html.bc87b86f.js | 1 - .../file-extensions-windows.html.c183cd24.js | 1 - .../file-extensions-windows.html.d9a59d03.js | 1 - .../file-extensions-windows.html.e1d1e6b2.js | 1 - .../file-extensions-windows.html.e3a1d8e8.js | 1 - .../file-extensions-windows.html.e54296b9.js | 1 - .../file-extensions-windows.html.fa1f3edb.js | 1 - assets/get-started.html-ddzMOKtz.js | 1 + ...50f9f0.js => get-started.html-n9PIV3MW.js} | 2 +- assets/get-started.html.0e0df7cd.js | 1 - assets/get-started.html.3b18fe3e.js | 1 - assets/get-started.html.42c6a17f.js | 1 - assets/get-started.html.5e92875f.js | 1 - assets/get-started.html.5ef3e583.js | 1 - assets/get-started.html.7d3e3d7e.js | 1 - assets/get-started.html.8fdcc809.js | 1 - assets/get-started.html.a1f59e27.js | 1 - assets/get-started.html.a31ca6d4.js | 1 - assets/get-started.html.b6f7535b.js | 1 - assets/get-started.html.bc21bb95.js | 1 - assets/get-started.html.c2a161f2.js | 1 - assets/get-started.html.ccaf7fd1.js | 1 - assets/get-started.html.db74146b.js | 1 - assets/get-started.html.dfea6606.js | 1 - assets/get-started.html.e348e57c.js | 1 - assets/get-started.html.ea7af6a1.js | 1 - assets/get-started.html.f2e164ec.js | 1 - assets/get-started.html.fc463575.js | 1 - assets/index.html-5kRAbWd2.js | 1 + ...tml.238b6ec0.js => index.html-PbQxpEgV.js} | 2 +- assets/index.html.0c876f5c.js | 1 - assets/index.html.528d2a64.js | 1 - assets/index.html.52c5fc8e.js | 1 - assets/index.html.63483a4c.js | 1 - assets/index.html.691829c1.js | 1 - assets/index.html.707408d9.js | 1 - assets/index.html.7642ff60.js | 1 - assets/index.html.7aed6467.js | 1 - assets/index.html.7cf6d19e.js | 1 - assets/index.html.8f55e5f6.js | 1 - assets/index.html.a1bc9cbf.js | 1 - assets/index.html.bc0239fe.js | 1 - assets/index.html.cbe0a789.js | 1 - assets/index.html.d6193011.js | 1 - assets/index.html.dc55036c.js | 1 - assets/index.html.e1ac195e.js | 1 - assets/index.html.e931f420.js | 1 - assets/index.html.eb533b4b.js | 1 - assets/index.html.f0297c17.js | 1 - assets/index.html.f1d49603.js | 1 - assets/index.html.fc4379ff.js | 1 - assets/installing-unlaunch.html-SOp7FDNn.js | 1 + ...s => installing-unlaunch.html-UlEWADRN.js} | 2 +- assets/installing-unlaunch.html.01b3ea30.js | 1 - assets/installing-unlaunch.html.0f1a0ca7.js | 1 - assets/installing-unlaunch.html.160722ac.js | 1 - assets/installing-unlaunch.html.1b936eb1.js | 1 - assets/installing-unlaunch.html.24b4264b.js | 1 - assets/installing-unlaunch.html.2b7c06c5.js | 1 - assets/installing-unlaunch.html.4b3a313b.js | 1 - assets/installing-unlaunch.html.4e9c735d.js | 1 - assets/installing-unlaunch.html.700ed972.js | 1 - assets/installing-unlaunch.html.7933c70f.js | 1 - assets/installing-unlaunch.html.827d63f4.js | 1 - assets/installing-unlaunch.html.82aaba87.js | 1 - assets/installing-unlaunch.html.84c89cc3.js | 1 - assets/installing-unlaunch.html.85e51b27.js | 1 - assets/installing-unlaunch.html.9882c647.js | 1 - assets/installing-unlaunch.html.9c6f22a9.js | 1 - assets/installing-unlaunch.html.be25ecd8.js | 1 - assets/installing-unlaunch.html.c402eb77.js | 1 - assets/installing-unlaunch.html.e4af593c.js | 1 - assets/installing-unlaunch.html.f8614cd7.js | 1 - assets/installing-unlaunch.html.fc07ebc4.js | 1 - ...ching-the-browser-exploit.html-M3ESNW79.js | 1 + ...hing-the-browser-exploit.html-Xe7erL1F.js} | 2 +- ...ching-the-browser-exploit.html.12e4109b.js | 1 - ...ching-the-browser-exploit.html.1a806d2f.js | 1 - ...ching-the-browser-exploit.html.323ad998.js | 1 - ...ching-the-browser-exploit.html.57d2fc9a.js | 1 - ...ching-the-browser-exploit.html.5c98e819.js | 1 - ...ching-the-browser-exploit.html.7a252a8c.js | 1 - ...ching-the-browser-exploit.html.7fb7f0b4.js | 1 - ...ching-the-browser-exploit.html.87a42ee1.js | 1 - ...ching-the-browser-exploit.html.8dbf926a.js | 1 - ...ching-the-browser-exploit.html.9f1c0bdb.js | 1 - ...ching-the-browser-exploit.html.a36c9f22.js | 1 - ...ching-the-browser-exploit.html.bd8fcf13.js | 1 - ...ching-the-browser-exploit.html.c17ae60f.js | 1 - ...ching-the-browser-exploit.html.d232dbed.js | 1 - ...ching-the-browser-exploit.html.d5e23cf0.js | 1 - ...ching-the-browser-exploit.html.d67c4691.js | 1 - ...ching-the-browser-exploit.html.d9b48f65.js | 1 - ...ching-the-browser-exploit.html.dc18986c.js | 1 - ...ching-the-browser-exploit.html.f4ebb121.js | 1 - assets/launching-the-exploit.html-TSxdOSGC.js | 1 + assets/launching-the-exploit.html-f3mAAz_r.js | 1 + assets/launching-the-exploit.html.241d3e9c.js | 1 - assets/launching-the-exploit.html.261bc9a3.js | 1 - assets/launching-the-exploit.html.2dbb335c.js | 1 - assets/launching-the-exploit.html.3d64ee7d.js | 1 - assets/launching-the-exploit.html.5ee883a4.js | 1 - assets/launching-the-exploit.html.66ec8917.js | 1 - assets/launching-the-exploit.html.7fe7b8d2.js | 1 - assets/launching-the-exploit.html.97c47b98.js | 1 - assets/launching-the-exploit.html.9862b573.js | 1 - assets/launching-the-exploit.html.9bc30041.js | 1 - assets/launching-the-exploit.html.a18a1598.js | 1 - assets/launching-the-exploit.html.a89a049a.js | 1 - assets/launching-the-exploit.html.acd7f9a1.js | 1 - assets/launching-the-exploit.html.b85a0f53.js | 1 - assets/launching-the-exploit.html.bcae185f.js | 1 - assets/launching-the-exploit.html.d2165032.js | 1 - assets/launching-the-exploit.html.d34fd8dd.js | 1 - assets/launching-the-exploit.html.def2565e.js | 1 - assets/launching-the-exploit.html.e4e9cdca.js | 1 - assets/launching-the-exploit.html.ecb2f285.js | 1 - assets/launching-the-exploit.html.f0417248.js | 1 - assets/launching-the-exploit.html.f8af7505.js | 1 - ...hing-the-flipnote-exploit.html-JdthyTfk.js | 1 + ...hing-the-flipnote-exploit.html-_srbGBVk.js | 1 + ...hing-the-flipnote-exploit.html.034356bf.js | 1 - ...hing-the-flipnote-exploit.html.0876db44.js | 1 - ...hing-the-flipnote-exploit.html.0a3522bf.js | 1 - ...hing-the-flipnote-exploit.html.0eb71cf2.js | 1 - ...hing-the-flipnote-exploit.html.26ccad98.js | 1 - ...hing-the-flipnote-exploit.html.26e8e849.js | 1 - ...hing-the-flipnote-exploit.html.38f2bf71.js | 1 - ...hing-the-flipnote-exploit.html.3b658d49.js | 1 - ...hing-the-flipnote-exploit.html.6385b669.js | 1 - ...hing-the-flipnote-exploit.html.747bd25d.js | 1 - ...hing-the-flipnote-exploit.html.81a0596b.js | 1 - ...hing-the-flipnote-exploit.html.88dfbe64.js | 1 - ...hing-the-flipnote-exploit.html.90727d02.js | 1 - ...hing-the-flipnote-exploit.html.9d7e7844.js | 1 - ...hing-the-flipnote-exploit.html.b1abaa7a.js | 1 - ...hing-the-flipnote-exploit.html.b31b1900.js | 1 - ...hing-the-flipnote-exploit.html.bf0f7824.js | 1 - ...hing-the-flipnote-exploit.html.d926f272.js | 1 - ...hing-the-flipnote-exploit.html.e8aa3cc4.js | 1 - ...hing-the-flipnote-exploit.html.f2d4aa58.js | 1 - assets/lazy-dsi-downloader.html.006c7b2d.js | 1 - assets/lazy-dsi-downloader.html.04f5cc4d.js | 1 - assets/lazy-dsi-downloader.html.14116ada.js | 1 - assets/lazy-dsi-downloader.html.28d58a68.js | 1 - assets/lazy-dsi-downloader.html.2c0ec81f.js | 1 - assets/lazy-dsi-downloader.html.3ea557c6.js | 1 - assets/lazy-dsi-downloader.html.4740c1ab.js | 1 - assets/lazy-dsi-downloader.html.4c1748c9.js | 1 - assets/lazy-dsi-downloader.html.55f71b45.js | 1 - assets/lazy-dsi-downloader.html.5d067611.js | 1 - assets/lazy-dsi-downloader.html.7544f72c.js | 1 - assets/lazy-dsi-downloader.html.7b4e5a9d.js | 1 - assets/lazy-dsi-downloader.html.86e9a592.js | 1 - assets/lazy-dsi-downloader.html.a481166a.js | 1 - assets/lazy-dsi-downloader.html.b0feb6a1.js | 1 - assets/lazy-dsi-downloader.html.bc37bdb9.js | 1 - assets/lazy-dsi-downloader.html.c641e21c.js | 1 - assets/lazy-dsi-downloader.html.d4afc485.js | 1 - assets/lazy-dsi-downloader.html.d5c9f358.js | 1 - assets/lazy-dsi-downloader.html.fdbbc18c.js | 1 - ...3de.js => restoring-nand.html-5jfrni5j.js} | 2 +- assets/restoring-nand.html-Ae4RDn9L.js | 1 + assets/restoring-nand.html.076d43e7.js | 1 - assets/restoring-nand.html.12f57e46.js | 1 - assets/restoring-nand.html.2277286e.js | 1 - assets/restoring-nand.html.345b85d5.js | 1 - assets/restoring-nand.html.3f8abe42.js | 1 - assets/restoring-nand.html.440d7b1d.js | 1 - assets/restoring-nand.html.4ca5e18d.js | 1 - assets/restoring-nand.html.68c83b68.js | 1 - assets/restoring-nand.html.71ab5872.js | 1 - assets/restoring-nand.html.73baeeb4.js | 1 - assets/restoring-nand.html.79bec8cb.js | 1 - assets/restoring-nand.html.86991693.js | 1 - assets/restoring-nand.html.8d05d93c.js | 1 - assets/restoring-nand.html.94dc5222.js | 1 - assets/restoring-nand.html.a4a37179.js | 1 - assets/restoring-nand.html.a4bcdb5d.js | 1 - assets/restoring-nand.html.aa1cdef6.js | 1 - assets/restoring-nand.html.c140fab5.js | 1 - assets/restoring-nand.html.cc032eed.js | 1 - assets/restoring-nand.html.d5a6aa5c.js | 1 - assets/restoring-nand.html.e082d297.js | 1 - assets/sd-card-formatter.7ed06060.js | 1 - assets/sd-card-setup.html-DsjOI2JY.js | 1 + ...9d41.js => sd-card-setup.html-kwu5A5RY.js} | 14 +-- assets/sd-card-setup.html.22c8e099.js | 1 - assets/sd-card-setup.html.3019fa7a.js | 42 --------- assets/sd-card-setup.html.45cd32d3.js | 1 - assets/sd-card-setup.html.475a1b59.js | 1 - assets/sd-card-setup.html.6124495b.js | 1 - assets/sd-card-setup.html.63bc0df3.js | 42 --------- assets/sd-card-setup.html.7103f4ff.js | 42 --------- assets/sd-card-setup.html.73e0246d.js | 42 --------- assets/sd-card-setup.html.795e25a3.js | 14 --- assets/sd-card-setup.html.8c1c5ba4.js | 1 - assets/sd-card-setup.html.9f63dccf.js | 1 - assets/sd-card-setup.html.b40ba6f9.js | 1 - assets/sd-card-setup.html.b8906bf6.js | 42 --------- assets/sd-card-setup.html.c455c3f0.js | 42 --------- assets/sd-card-setup.html.cf7c59aa.js | 42 --------- assets/sd-card-setup.html.db8549e6.js | 1 - assets/sd-card-setup.html.df6fea81.js | 42 --------- assets/sd-card-setup.html.e3300641.js | 1 - assets/sd-card-setup.html.eeb74b13.js | 1 - assets/sd-card-setup.html.eec340da.js | 1 - assets/sd-card-setup.html.f32e21d9.js | 42 --------- assets/search.0782d0d1.svg | 1 - assets/site-navigation.html-V7nod6VV.js | 1 + assets/site-navigation.html-iVOyZHn-.js | 1 + assets/site-navigation.html.10f93cda.js | 1 - assets/site-navigation.html.17673531.js | 1 - assets/site-navigation.html.20134b5d.js | 1 - assets/site-navigation.html.342e2d6b.js | 1 - assets/site-navigation.html.4ddc00bb.js | 1 - assets/site-navigation.html.5174cca6.js | 1 - assets/site-navigation.html.6619cdc1.js | 1 - assets/site-navigation.html.6859e5db.js | 1 - assets/site-navigation.html.6cc07c06.js | 1 - assets/site-navigation.html.709a62ff.js | 1 - assets/site-navigation.html.74a87f92.js | 1 - assets/site-navigation.html.77bd3a65.js | 1 - assets/site-navigation.html.8f6a7ccb.js | 1 - assets/site-navigation.html.8f8c5136.js | 1 - assets/site-navigation.html.a0be164c.js | 1 - assets/site-navigation.html.aa74ff4f.js | 1 - assets/site-navigation.html.b5eb7148.js | 1 - assets/site-navigation.html.b8d0ff60.js | 1 - assets/site-navigation.html.d501ff82.js | 1 - assets/site-navigation.html.e1e96813.js | 1 - assets/site-navigation.html.eee8a0ee.js | 1 - assets/site-navigation.html.f44df8c8.js | 1 - assets/style-qWdKKepg.css | 1 + assets/style.f7a00e79.css | 1 - ...78.js => troubleshooting.html-Dr8osdca.js} | 2 +- assets/troubleshooting.html-OVpmNPgb.js | 1 + assets/troubleshooting.html.1c66b7dc.js | 1 - assets/troubleshooting.html.38cd1a24.js | 1 - assets/troubleshooting.html.3bcae2fc.js | 1 - assets/troubleshooting.html.3f63e310.js | 1 - assets/troubleshooting.html.413f84d8.js | 1 - assets/troubleshooting.html.53b28a84.js | 1 - assets/troubleshooting.html.63a6da50.js | 1 - assets/troubleshooting.html.753540b9.js | 1 - assets/troubleshooting.html.7775e942.js | 1 - assets/troubleshooting.html.7a5aa972.js | 1 - assets/troubleshooting.html.8ad5ffd0.js | 1 - assets/troubleshooting.html.9922e01d.js | 1 - assets/troubleshooting.html.a217e474.js | 1 - assets/troubleshooting.html.a8869cb1.js | 1 - assets/troubleshooting.html.aee7a89e.js | 1 - assets/troubleshooting.html.b0cf5728.js | 1 - assets/troubleshooting.html.b318b2f2.js | 1 - assets/troubleshooting.html.c448d7a8.js | 1 - assets/troubleshooting.html.d040c9ca.js | 1 - assets/troubleshooting.html.ee6d2b08.js | 1 - assets/troubleshooting.html.fc2ee9e0.js | 1 - assets/uninstalling-unlaunch.html-Wbgbkb1X.js | 1 + ...=> uninstalling-unlaunch.html-xypHBKNg.js} | 2 +- assets/uninstalling-unlaunch.html.0acd41cd.js | 1 - assets/uninstalling-unlaunch.html.0ef36e8f.js | 1 - assets/uninstalling-unlaunch.html.1a51bea3.js | 1 - assets/uninstalling-unlaunch.html.20a31d89.js | 1 - assets/uninstalling-unlaunch.html.3072b863.js | 1 - assets/uninstalling-unlaunch.html.323cc184.js | 1 - assets/uninstalling-unlaunch.html.39deeca0.js | 1 - assets/uninstalling-unlaunch.html.71d5135a.js | 1 - assets/uninstalling-unlaunch.html.7cd5b1ea.js | 1 - assets/uninstalling-unlaunch.html.82c40d22.js | 1 - assets/uninstalling-unlaunch.html.8d9fa8cf.js | 1 - assets/uninstalling-unlaunch.html.a915f92d.js | 1 - assets/uninstalling-unlaunch.html.bfb063ad.js | 1 - assets/uninstalling-unlaunch.html.c4eaff03.js | 1 - assets/uninstalling-unlaunch.html.d4761cc3.js | 1 - assets/uninstalling-unlaunch.html.dde61a18.js | 1 - assets/uninstalling-unlaunch.html.de817425.js | 1 - assets/uninstalling-unlaunch.html.e49a92b2.js | 1 - assets/uninstalling-unlaunch.html.e5089919.js | 1 - assets/uninstalling-unlaunch.html.eeb8812d.js | 1 - assets/uninstalling-unlaunch.html.fe75d8ad.js | 1 - assets/windows-7-folder-options.73715046.js | 1 - credits.html | 25 ++---- de_DE/404.html | 33 ------- de_DE/alternate-exploits.html | 44 ---------- de_DE/credits.html | 44 ---------- de_DE/dsiware-backups.html | 44 ---------- de_DE/dumping-game-cards.html | 44 ---------- de_DE/dumping-nand.html | 44 ---------- de_DE/faq.html | 44 ---------- de_DE/file-extensions-windows.html | 44 ---------- de_DE/get-started.html | 44 ---------- de_DE/index.html | 43 ---------- de_DE/installing-unlaunch.html | 44 ---------- de_DE/launching-the-browser-exploit.html | 44 ---------- de_DE/launching-the-exploit.html | 44 ---------- de_DE/launching-the-flipnote-exploit.html | 44 ---------- de_DE/lazy-dsi-downloader.html | 44 ---------- de_DE/restoring-nand.html | 44 ---------- de_DE/sd-card-setup.html | 85 ------------------- de_DE/site-navigation.html | 44 ---------- de_DE/troubleshooting.html | 44 ---------- de_DE/uninstalling-unlaunch.html | 44 ---------- dsiware-backups.html | 25 ++---- dumping-game-cards.html | 25 ++---- dumping-nand.html | 25 ++---- es_ES/404.html | 33 ------- es_ES/alternate-exploits.html | 44 ---------- es_ES/credits.html | 44 ---------- es_ES/dsiware-backups.html | 44 ---------- es_ES/dumping-game-cards.html | 44 ---------- es_ES/dumping-nand.html | 44 ---------- es_ES/faq.html | 44 ---------- es_ES/file-extensions-windows.html | 44 ---------- es_ES/get-started.html | 44 ---------- es_ES/index.html | 43 ---------- es_ES/installing-unlaunch.html | 44 ---------- es_ES/launching-the-browser-exploit.html | 44 ---------- es_ES/launching-the-exploit.html | 44 ---------- es_ES/launching-the-flipnote-exploit.html | 44 ---------- es_ES/lazy-dsi-downloader.html | 44 ---------- es_ES/restoring-nand.html | 44 ---------- es_ES/sd-card-setup.html | 85 ------------------- es_ES/site-navigation.html | 44 ---------- es_ES/troubleshooting.html | 44 ---------- es_ES/uninstalling-unlaunch.html | 44 ---------- faq.html | 25 ++---- file-extensions-windows.html | 25 ++---- fr_FR/404.html | 33 ------- fr_FR/alternate-exploits.html | 44 ---------- fr_FR/credits.html | 44 ---------- fr_FR/dsiware-backups.html | 44 ---------- fr_FR/dumping-game-cards.html | 44 ---------- fr_FR/dumping-nand.html | 44 ---------- fr_FR/faq.html | 44 ---------- fr_FR/file-extensions-windows.html | 44 ---------- fr_FR/get-started.html | 44 ---------- fr_FR/index.html | 43 ---------- fr_FR/installing-unlaunch.html | 44 ---------- fr_FR/launching-the-browser-exploit.html | 44 ---------- fr_FR/launching-the-exploit.html | 44 ---------- fr_FR/launching-the-flipnote-exploit.html | 44 ---------- fr_FR/lazy-dsi-downloader.html | 44 ---------- fr_FR/restoring-nand.html | 44 ---------- fr_FR/sd-card-setup.html | 85 ------------------- fr_FR/site-navigation.html | 44 ---------- fr_FR/troubleshooting.html | 44 ---------- fr_FR/uninstalling-unlaunch.html | 44 ---------- get-started.html | 25 ++---- hu_HU/404.html | 33 ------- hu_HU/alternate-exploits.html | 44 ---------- hu_HU/credits.html | 44 ---------- hu_HU/dsiware-backups.html | 44 ---------- hu_HU/dumping-game-cards.html | 44 ---------- hu_HU/dumping-nand.html | 44 ---------- hu_HU/faq.html | 44 ---------- hu_HU/file-extensions-windows.html | 44 ---------- hu_HU/get-started.html | 44 ---------- hu_HU/index.html | 43 ---------- hu_HU/installing-unlaunch.html | 44 ---------- hu_HU/launching-the-browser-exploit.html | 44 ---------- hu_HU/launching-the-exploit.html | 44 ---------- hu_HU/launching-the-flipnote-exploit.html | 44 ---------- hu_HU/lazy-dsi-downloader.html | 44 ---------- hu_HU/restoring-nand.html | 44 ---------- hu_HU/sd-card-setup.html | 85 ------------------- hu_HU/site-navigation.html | 44 ---------- hu_HU/troubleshooting.html | 44 ---------- hu_HU/uninstalling-unlaunch.html | 44 ---------- index.html | 23 ++--- installing-unlaunch.html | 25 ++---- it_IT/404.html | 33 ------- it_IT/alternate-exploits.html | 44 ---------- it_IT/credits.html | 44 ---------- it_IT/dsiware-backups.html | 44 ---------- it_IT/dumping-game-cards.html | 44 ---------- it_IT/dumping-nand.html | 44 ---------- it_IT/faq.html | 44 ---------- it_IT/file-extensions-windows.html | 44 ---------- it_IT/get-started.html | 44 ---------- it_IT/index.html | 43 ---------- it_IT/installing-unlaunch.html | 44 ---------- it_IT/launching-the-browser-exploit.html | 44 ---------- it_IT/launching-the-exploit.html | 44 ---------- it_IT/launching-the-flipnote-exploit.html | 44 ---------- it_IT/lazy-dsi-downloader.html | 44 ---------- it_IT/restoring-nand.html | 44 ---------- it_IT/sd-card-setup.html | 85 ------------------- it_IT/site-navigation.html | 44 ---------- it_IT/troubleshooting.html | 44 ---------- it_IT/uninstalling-unlaunch.html | 44 ---------- ja_JP/404.html | 33 ------- ja_JP/alternate-exploits.html | 44 ---------- ja_JP/credits.html | 44 ---------- ja_JP/dsiware-backups.html | 44 ---------- ja_JP/dumping-game-cards.html | 44 ---------- ja_JP/dumping-nand.html | 44 ---------- ja_JP/faq.html | 44 ---------- ja_JP/file-extensions-windows.html | 44 ---------- ja_JP/get-started.html | 44 ---------- ja_JP/index.html | 43 ---------- ja_JP/installing-unlaunch.html | 44 ---------- ja_JP/launching-the-browser-exploit.html | 44 ---------- ja_JP/launching-the-exploit.html | 44 ---------- ja_JP/launching-the-flipnote-exploit.html | 44 ---------- ja_JP/lazy-dsi-downloader.html | 44 ---------- ja_JP/restoring-nand.html | 44 ---------- ja_JP/sd-card-setup.html | 85 ------------------- ja_JP/site-navigation.html | 44 ---------- ja_JP/troubleshooting.html | 44 ---------- ja_JP/uninstalling-unlaunch.html | 44 ---------- launching-the-browser-exploit.html | 25 ++---- launching-the-exploit.html | 25 ++---- launching-the-flipnote-exploit.html | 25 ++---- pl_PL/404.html | 33 ------- pl_PL/alternate-exploits.html | 44 ---------- pl_PL/credits.html | 44 ---------- pl_PL/dsiware-backups.html | 44 ---------- pl_PL/dumping-game-cards.html | 44 ---------- pl_PL/dumping-nand.html | 44 ---------- pl_PL/faq.html | 44 ---------- pl_PL/file-extensions-windows.html | 44 ---------- pl_PL/get-started.html | 44 ---------- pl_PL/index.html | 43 ---------- pl_PL/installing-unlaunch.html | 44 ---------- pl_PL/launching-the-browser-exploit.html | 44 ---------- pl_PL/launching-the-exploit.html | 44 ---------- pl_PL/launching-the-flipnote-exploit.html | 44 ---------- pl_PL/lazy-dsi-downloader.html | 44 ---------- pl_PL/restoring-nand.html | 44 ---------- pl_PL/sd-card-setup.html | 85 ------------------- pl_PL/site-navigation.html | 44 ---------- pl_PL/troubleshooting.html | 44 ---------- pl_PL/uninstalling-unlaunch.html | 44 ---------- restoring-nand.html | 25 ++---- ro_RO/404.html | 33 ------- ro_RO/alternate-exploits.html | 44 ---------- ro_RO/credits.html | 44 ---------- ro_RO/dsiware-backups.html | 44 ---------- ro_RO/dumping-game-cards.html | 44 ---------- ro_RO/dumping-nand.html | 44 ---------- ro_RO/faq.html | 44 ---------- ro_RO/file-extensions-windows.html | 44 ---------- ro_RO/get-started.html | 44 ---------- ro_RO/index.html | 43 ---------- ro_RO/installing-unlaunch.html | 44 ---------- ro_RO/launching-the-browser-exploit.html | 44 ---------- ro_RO/launching-the-exploit.html | 44 ---------- ro_RO/launching-the-flipnote-exploit.html | 44 ---------- ro_RO/lazy-dsi-downloader.html | 44 ---------- ro_RO/restoring-nand.html | 44 ---------- ro_RO/sd-card-setup.html | 85 ------------------- ro_RO/site-navigation.html | 44 ---------- ro_RO/troubleshooting.html | 44 ---------- ro_RO/uninstalling-unlaunch.html | 44 ---------- sd-card-setup.html | 35 +++----- site-navigation.html | 25 ++---- translate/404.html | 33 ------- translate/alternate-exploits.html | 44 ---------- translate/credits.html | 44 ---------- translate/dsiware-backups.html | 44 ---------- translate/dumping-game-cards.html | 44 ---------- translate/dumping-nand.html | 44 ---------- translate/faq.html | 44 ---------- translate/file-extensions-(windows).html | 44 ---------- translate/index.html | 43 ---------- translate/installing-unlaunch.html | 44 ---------- translate/launching-the-exploit.html | 44 ---------- translate/lazy-dsi-downloader.html | 44 ---------- translate/restoring-nand.html | 44 ---------- translate/sd-card-setup.html | 57 ------------- translate/site-navigation.html | 44 ---------- translate/troubleshooting.html | 44 ---------- translate/uninstalling-unlaunch.html | 44 ---------- troubleshooting.html | 25 ++---- uninstalling-unlaunch.html | 25 ++---- zh_CN/404.html | 33 ------- zh_CN/alternate-exploits.html | 44 ---------- zh_CN/credits.html | 44 ---------- zh_CN/dsiware-backups.html | 44 ---------- zh_CN/dumping-game-cards.html | 44 ---------- zh_CN/dumping-nand.html | 44 ---------- zh_CN/faq.html | 44 ---------- zh_CN/file-extensions-windows.html | 44 ---------- zh_CN/get-started.html | 44 ---------- zh_CN/index.html | 43 ---------- zh_CN/installing-unlaunch.html | 44 ---------- zh_CN/launching-the-browser-exploit.html | 44 ---------- zh_CN/launching-the-exploit.html | 44 ---------- zh_CN/launching-the-flipnote-exploit.html | 44 ---------- zh_CN/lazy-dsi-downloader.html | 44 ---------- zh_CN/restoring-nand.html | 44 ---------- zh_CN/sd-card-setup.html | 85 ------------------- zh_CN/site-navigation.html | 44 ---------- zh_CN/troubleshooting.html | 44 ---------- zh_CN/uninstalling-unlaunch.html | 44 ---------- 685 files changed, 250 insertions(+), 10112 deletions(-) delete mode 100644 assets/404.7e7dd6bd.js rename assets/{404.html.3e67d2f2.js => 404.html-LriIqlkn.js} (58%) create mode 100644 assets/404.html-POh9F63p.js delete mode 100644 assets/404.html.1244b7c1.js delete mode 100644 assets/404.html.1972a2fc.js delete mode 100644 assets/404.html.241a3bfe.js delete mode 100644 assets/404.html.253ce897.js delete mode 100644 assets/404.html.25cc16bb.js delete mode 100644 assets/404.html.34559d27.js delete mode 100644 assets/404.html.35a5a0e7.js delete mode 100644 assets/404.html.40567751.js delete mode 100644 assets/404.html.4dcc8308.js delete mode 100644 assets/404.html.797ccca6.js delete mode 100644 assets/404.html.7ac5113a.js delete mode 100644 assets/404.html.7cffd467.js delete mode 100644 assets/404.html.879a949d.js delete mode 100644 assets/404.html.8b51d6f8.js delete mode 100644 assets/404.html.a625a05b.js delete mode 100644 assets/404.html.acaf0607.js delete mode 100644 assets/404.html.b55b4735.js delete mode 100644 assets/404.html.cc293232.js delete mode 100644 assets/404.html.d5818d0d.js delete mode 100644 assets/404.html.e8fa2dfd.js delete mode 100644 assets/404.html.f4bf4981.js delete mode 100644 assets/Layout.fd61c638.js create mode 100644 assets/Tab-NmAeYXh6.js delete mode 100644 assets/Tab.1a03f8dd.js create mode 100644 assets/Tabs-Pu6bnuAw.js delete mode 100644 assets/Tabs.38981e92.js create mode 100644 assets/alternate-exploits.html-ocXv1DJG.js rename assets/{alternate-exploits.html.f398e3ee.js => alternate-exploits.html-vBuFFl6W.js} (88%) delete mode 100644 assets/alternate-exploits.html.0303eb15.js delete mode 100644 assets/alternate-exploits.html.03904bef.js delete mode 100644 assets/alternate-exploits.html.0531607f.js delete mode 100644 assets/alternate-exploits.html.0c805215.js delete mode 100644 assets/alternate-exploits.html.1b51d524.js delete mode 100644 assets/alternate-exploits.html.2f13ec14.js delete mode 100644 assets/alternate-exploits.html.42bd011d.js delete mode 100644 assets/alternate-exploits.html.5ffa05d0.js delete mode 100644 assets/alternate-exploits.html.73604076.js delete mode 100644 assets/alternate-exploits.html.7b4b059e.js delete mode 100644 assets/alternate-exploits.html.9825c1cb.js delete mode 100644 assets/alternate-exploits.html.998b04d6.js delete mode 100644 assets/alternate-exploits.html.b0e5c2b0.js delete mode 100644 assets/alternate-exploits.html.b1ad08d5.js delete mode 100644 assets/alternate-exploits.html.b8d37145.js delete mode 100644 assets/alternate-exploits.html.baf364ca.js delete mode 100644 assets/alternate-exploits.html.cf2b2029.js delete mode 100644 assets/alternate-exploits.html.d2506977.js delete mode 100644 assets/alternate-exploits.html.dec961a5.js delete mode 100644 assets/alternate-exploits.html.f5bec0ce.js delete mode 100644 assets/alternate-exploits.html.f7fcddb7.js create mode 100644 assets/app-yIkf6V5Q.js delete mode 100644 assets/app.dee26283.js delete mode 100644 assets/back-to-top.8efcbe56.svg rename assets/{credits.html.33157cef.js => credits.html-TfDvKXaR.js} (58%) rename assets/{credits.html.f2bc8d43.js => credits.html-vxG94Np9.js} (87%) delete mode 100644 assets/credits.html.0df33721.js delete mode 100644 assets/credits.html.1667fccf.js delete mode 100644 assets/credits.html.3fcc009d.js delete mode 100644 assets/credits.html.3fd1fd62.js delete mode 100644 assets/credits.html.50dda71a.js delete mode 100644 assets/credits.html.5d3c2db3.js delete mode 100644 assets/credits.html.610de7b7.js delete mode 100644 assets/credits.html.67e32b57.js delete mode 100644 assets/credits.html.69eecd9f.js delete mode 100644 assets/credits.html.69f8a4d1.js delete mode 100644 assets/credits.html.7066fd3a.js delete mode 100644 assets/credits.html.8b056ada.js delete mode 100644 assets/credits.html.922c178b.js delete mode 100644 assets/credits.html.99601007.js delete mode 100644 assets/credits.html.abd83a0c.js delete mode 100644 assets/credits.html.c139bf88.js delete mode 100644 assets/credits.html.c15542ca.js delete mode 100644 assets/credits.html.d2d30ca6.js delete mode 100644 assets/credits.html.dc24af6d.js delete mode 100644 assets/credits.html.e602a7f1.js rename assets/{dsiware-backups.html.444c81e4.js => dsiware-backups.html-4cubhJlF.js} (80%) create mode 100644 assets/dsiware-backups.html-pyT4wBYB.js delete mode 100644 assets/dsiware-backups.html.0e4842e8.js delete mode 100644 assets/dsiware-backups.html.116cb38d.js delete mode 100644 assets/dsiware-backups.html.2a216475.js delete mode 100644 assets/dsiware-backups.html.2d6b1764.js delete mode 100644 assets/dsiware-backups.html.346b41b9.js delete mode 100644 assets/dsiware-backups.html.5011a0b9.js delete mode 100644 assets/dsiware-backups.html.50419e33.js delete mode 100644 assets/dsiware-backups.html.528669d2.js delete mode 100644 assets/dsiware-backups.html.53216945.js delete mode 100644 assets/dsiware-backups.html.627b4865.js delete mode 100644 assets/dsiware-backups.html.742074a0.js delete mode 100644 assets/dsiware-backups.html.8b22beff.js delete mode 100644 assets/dsiware-backups.html.9a51bef2.js delete mode 100644 assets/dsiware-backups.html.a6fff0cb.js delete mode 100644 assets/dsiware-backups.html.bd22a114.js delete mode 100644 assets/dsiware-backups.html.c3daaa30.js delete mode 100644 assets/dsiware-backups.html.c6f26fa8.js delete mode 100644 assets/dsiware-backups.html.d530a09e.js delete mode 100644 assets/dsiware-backups.html.f632566c.js delete mode 100644 assets/dsiware-backups.html.fb9a2303.js delete mode 100644 assets/dsiware-backups.html.fe0f52aa.js rename assets/{dumping-game-cards.html.00f31dc3.js => dumping-game-cards.html-BH0ZUZq_.js} (86%) create mode 100644 assets/dumping-game-cards.html-S_9zIrgu.js delete mode 100644 assets/dumping-game-cards.html.035bcec9.js delete mode 100644 assets/dumping-game-cards.html.0f310264.js delete mode 100644 assets/dumping-game-cards.html.0f3f183b.js delete mode 100644 assets/dumping-game-cards.html.24136168.js delete mode 100644 assets/dumping-game-cards.html.29060e56.js delete mode 100644 assets/dumping-game-cards.html.33ca88d4.js delete mode 100644 assets/dumping-game-cards.html.452e3d20.js delete mode 100644 assets/dumping-game-cards.html.469318e4.js delete mode 100644 assets/dumping-game-cards.html.4db772f5.js delete mode 100644 assets/dumping-game-cards.html.6fbd3c08.js delete mode 100644 assets/dumping-game-cards.html.944e9149.js delete mode 100644 assets/dumping-game-cards.html.9fca2346.js delete mode 100644 assets/dumping-game-cards.html.a0d6e45b.js delete mode 100644 assets/dumping-game-cards.html.aa9098bd.js delete mode 100644 assets/dumping-game-cards.html.b9857bb6.js delete mode 100644 assets/dumping-game-cards.html.d2c61ba6.js delete mode 100644 assets/dumping-game-cards.html.d455304d.js delete mode 100644 assets/dumping-game-cards.html.deb8cc92.js delete mode 100644 assets/dumping-game-cards.html.e21b5d52.js delete mode 100644 assets/dumping-game-cards.html.ef17f70d.js delete mode 100644 assets/dumping-game-cards.html.f9c6f36c.js rename assets/{dumping-nand.html.9206c135.js => dumping-nand.html-9ppCjrZL.js} (88%) create mode 100644 assets/dumping-nand.html-Iammg12x.js delete mode 100644 assets/dumping-nand.html.1f69c4ac.js delete mode 100644 assets/dumping-nand.html.29f3c4a9.js delete mode 100644 assets/dumping-nand.html.351e0ec4.js delete mode 100644 assets/dumping-nand.html.38430bea.js delete mode 100644 assets/dumping-nand.html.38a6e01d.js delete mode 100644 assets/dumping-nand.html.3f3961e2.js delete mode 100644 assets/dumping-nand.html.4ecef543.js delete mode 100644 assets/dumping-nand.html.55478a52.js delete mode 100644 assets/dumping-nand.html.5e22f4db.js delete mode 100644 assets/dumping-nand.html.69608bc7.js delete mode 100644 assets/dumping-nand.html.7342b7e1.js delete mode 100644 assets/dumping-nand.html.8c80c088.js delete mode 100644 assets/dumping-nand.html.93d45bb5.js delete mode 100644 assets/dumping-nand.html.98f40ec5.js delete mode 100644 assets/dumping-nand.html.b883979b.js delete mode 100644 assets/dumping-nand.html.bccd9c91.js delete mode 100644 assets/dumping-nand.html.c1390a86.js delete mode 100644 assets/dumping-nand.html.c7e47651.js delete mode 100644 assets/dumping-nand.html.cbf1004f.js delete mode 100644 assets/dumping-nand.html.e5ef8ca3.js delete mode 100644 assets/dumping-nand.html.ef2f6139.js delete mode 100644 assets/facebook-check.a40c2972.js rename assets/{faq.html.c7a6762f.js => faq.html-BpG_zlj5.js} (99%) create mode 100644 assets/faq.html-VjmhWoRW.js delete mode 100644 assets/faq.html.08809d7d.js delete mode 100644 assets/faq.html.38b88ac7.js delete mode 100644 assets/faq.html.43e45ca9.js delete mode 100644 assets/faq.html.470e4ddc.js delete mode 100644 assets/faq.html.4d54914c.js delete mode 100644 assets/faq.html.50c0c142.js delete mode 100644 assets/faq.html.53454531.js delete mode 100644 assets/faq.html.671c32bf.js delete mode 100644 assets/faq.html.7f47ebe8.js delete mode 100644 assets/faq.html.85d568ad.js delete mode 100644 assets/faq.html.972ad4a8.js delete mode 100644 assets/faq.html.98b815b9.js delete mode 100644 assets/faq.html.9b2c1de7.js delete mode 100644 assets/faq.html.c592bfd9.js delete mode 100644 assets/faq.html.d9296555.js delete mode 100644 assets/faq.html.d96f3d18.js delete mode 100644 assets/faq.html.e668a7a3.js delete mode 100644 assets/faq.html.e7eed8db.js delete mode 100644 assets/faq.html.ec2c3653.js delete mode 100644 assets/faq.html.f3645f8c.js delete mode 100644 assets/faq.html.f48cbbdf.js delete mode 100644 assets/file-extensions-(windows).html.1fb6ba24.js delete mode 100644 assets/file-extensions-(windows).html.5ff085f7.js create mode 100644 assets/file-extensions-windows.html-7rJlexbx.js create mode 100644 assets/file-extensions-windows.html-CY71hixJ.js delete mode 100644 assets/file-extensions-windows.html.04d6bf57.js delete mode 100644 assets/file-extensions-windows.html.0f860332.js delete mode 100644 assets/file-extensions-windows.html.20f37a8e.js delete mode 100644 assets/file-extensions-windows.html.2ef5df31.js delete mode 100644 assets/file-extensions-windows.html.306ed54f.js delete mode 100644 assets/file-extensions-windows.html.4986e0c7.js delete mode 100644 assets/file-extensions-windows.html.5772f0ca.js delete mode 100644 assets/file-extensions-windows.html.6aef26fc.js delete mode 100644 assets/file-extensions-windows.html.7bae9a4b.js delete mode 100644 assets/file-extensions-windows.html.845d5d61.js delete mode 100644 assets/file-extensions-windows.html.9a188dc0.js delete mode 100644 assets/file-extensions-windows.html.9aa4fc2e.js delete mode 100644 assets/file-extensions-windows.html.b1f93401.js delete mode 100644 assets/file-extensions-windows.html.bc87b86f.js delete mode 100644 assets/file-extensions-windows.html.c183cd24.js delete mode 100644 assets/file-extensions-windows.html.d9a59d03.js delete mode 100644 assets/file-extensions-windows.html.e1d1e6b2.js delete mode 100644 assets/file-extensions-windows.html.e3a1d8e8.js delete mode 100644 assets/file-extensions-windows.html.e54296b9.js delete mode 100644 assets/file-extensions-windows.html.fa1f3edb.js create mode 100644 assets/get-started.html-ddzMOKtz.js rename assets/{get-started.html.3a50f9f0.js => get-started.html-n9PIV3MW.js} (97%) delete mode 100644 assets/get-started.html.0e0df7cd.js delete mode 100644 assets/get-started.html.3b18fe3e.js delete mode 100644 assets/get-started.html.42c6a17f.js delete mode 100644 assets/get-started.html.5e92875f.js delete mode 100644 assets/get-started.html.5ef3e583.js delete mode 100644 assets/get-started.html.7d3e3d7e.js delete mode 100644 assets/get-started.html.8fdcc809.js delete mode 100644 assets/get-started.html.a1f59e27.js delete mode 100644 assets/get-started.html.a31ca6d4.js delete mode 100644 assets/get-started.html.b6f7535b.js delete mode 100644 assets/get-started.html.bc21bb95.js delete mode 100644 assets/get-started.html.c2a161f2.js delete mode 100644 assets/get-started.html.ccaf7fd1.js delete mode 100644 assets/get-started.html.db74146b.js delete mode 100644 assets/get-started.html.dfea6606.js delete mode 100644 assets/get-started.html.e348e57c.js delete mode 100644 assets/get-started.html.ea7af6a1.js delete mode 100644 assets/get-started.html.f2e164ec.js delete mode 100644 assets/get-started.html.fc463575.js create mode 100644 assets/index.html-5kRAbWd2.js rename assets/{index.html.238b6ec0.js => index.html-PbQxpEgV.js} (95%) delete mode 100644 assets/index.html.0c876f5c.js delete mode 100644 assets/index.html.528d2a64.js delete mode 100644 assets/index.html.52c5fc8e.js delete mode 100644 assets/index.html.63483a4c.js delete mode 100644 assets/index.html.691829c1.js delete mode 100644 assets/index.html.707408d9.js delete mode 100644 assets/index.html.7642ff60.js delete mode 100644 assets/index.html.7aed6467.js delete mode 100644 assets/index.html.7cf6d19e.js delete mode 100644 assets/index.html.8f55e5f6.js delete mode 100644 assets/index.html.a1bc9cbf.js delete mode 100644 assets/index.html.bc0239fe.js delete mode 100644 assets/index.html.cbe0a789.js delete mode 100644 assets/index.html.d6193011.js delete mode 100644 assets/index.html.dc55036c.js delete mode 100644 assets/index.html.e1ac195e.js delete mode 100644 assets/index.html.e931f420.js delete mode 100644 assets/index.html.eb533b4b.js delete mode 100644 assets/index.html.f0297c17.js delete mode 100644 assets/index.html.f1d49603.js delete mode 100644 assets/index.html.fc4379ff.js create mode 100644 assets/installing-unlaunch.html-SOp7FDNn.js rename assets/{installing-unlaunch.html.dc43550c.js => installing-unlaunch.html-UlEWADRN.js} (86%) delete mode 100644 assets/installing-unlaunch.html.01b3ea30.js delete mode 100644 assets/installing-unlaunch.html.0f1a0ca7.js delete mode 100644 assets/installing-unlaunch.html.160722ac.js delete mode 100644 assets/installing-unlaunch.html.1b936eb1.js delete mode 100644 assets/installing-unlaunch.html.24b4264b.js delete mode 100644 assets/installing-unlaunch.html.2b7c06c5.js delete mode 100644 assets/installing-unlaunch.html.4b3a313b.js delete mode 100644 assets/installing-unlaunch.html.4e9c735d.js delete mode 100644 assets/installing-unlaunch.html.700ed972.js delete mode 100644 assets/installing-unlaunch.html.7933c70f.js delete mode 100644 assets/installing-unlaunch.html.827d63f4.js delete mode 100644 assets/installing-unlaunch.html.82aaba87.js delete mode 100644 assets/installing-unlaunch.html.84c89cc3.js delete mode 100644 assets/installing-unlaunch.html.85e51b27.js delete mode 100644 assets/installing-unlaunch.html.9882c647.js delete mode 100644 assets/installing-unlaunch.html.9c6f22a9.js delete mode 100644 assets/installing-unlaunch.html.be25ecd8.js delete mode 100644 assets/installing-unlaunch.html.c402eb77.js delete mode 100644 assets/installing-unlaunch.html.e4af593c.js delete mode 100644 assets/installing-unlaunch.html.f8614cd7.js delete mode 100644 assets/installing-unlaunch.html.fc07ebc4.js create mode 100644 assets/launching-the-browser-exploit.html-M3ESNW79.js rename assets/{launching-the-browser-exploit.html.88647736.js => launching-the-browser-exploit.html-Xe7erL1F.js} (92%) delete mode 100644 assets/launching-the-browser-exploit.html.12e4109b.js delete mode 100644 assets/launching-the-browser-exploit.html.1a806d2f.js delete mode 100644 assets/launching-the-browser-exploit.html.323ad998.js delete mode 100644 assets/launching-the-browser-exploit.html.57d2fc9a.js delete mode 100644 assets/launching-the-browser-exploit.html.5c98e819.js delete mode 100644 assets/launching-the-browser-exploit.html.7a252a8c.js delete mode 100644 assets/launching-the-browser-exploit.html.7fb7f0b4.js delete mode 100644 assets/launching-the-browser-exploit.html.87a42ee1.js delete mode 100644 assets/launching-the-browser-exploit.html.8dbf926a.js delete mode 100644 assets/launching-the-browser-exploit.html.9f1c0bdb.js delete mode 100644 assets/launching-the-browser-exploit.html.a36c9f22.js delete mode 100644 assets/launching-the-browser-exploit.html.bd8fcf13.js delete mode 100644 assets/launching-the-browser-exploit.html.c17ae60f.js delete mode 100644 assets/launching-the-browser-exploit.html.d232dbed.js delete mode 100644 assets/launching-the-browser-exploit.html.d5e23cf0.js delete mode 100644 assets/launching-the-browser-exploit.html.d67c4691.js delete mode 100644 assets/launching-the-browser-exploit.html.d9b48f65.js delete mode 100644 assets/launching-the-browser-exploit.html.dc18986c.js delete mode 100644 assets/launching-the-browser-exploit.html.f4ebb121.js create mode 100644 assets/launching-the-exploit.html-TSxdOSGC.js create mode 100644 assets/launching-the-exploit.html-f3mAAz_r.js delete mode 100644 assets/launching-the-exploit.html.241d3e9c.js delete mode 100644 assets/launching-the-exploit.html.261bc9a3.js delete mode 100644 assets/launching-the-exploit.html.2dbb335c.js delete mode 100644 assets/launching-the-exploit.html.3d64ee7d.js delete mode 100644 assets/launching-the-exploit.html.5ee883a4.js delete mode 100644 assets/launching-the-exploit.html.66ec8917.js delete mode 100644 assets/launching-the-exploit.html.7fe7b8d2.js delete mode 100644 assets/launching-the-exploit.html.97c47b98.js delete mode 100644 assets/launching-the-exploit.html.9862b573.js delete mode 100644 assets/launching-the-exploit.html.9bc30041.js delete mode 100644 assets/launching-the-exploit.html.a18a1598.js delete mode 100644 assets/launching-the-exploit.html.a89a049a.js delete mode 100644 assets/launching-the-exploit.html.acd7f9a1.js delete mode 100644 assets/launching-the-exploit.html.b85a0f53.js delete mode 100644 assets/launching-the-exploit.html.bcae185f.js delete mode 100644 assets/launching-the-exploit.html.d2165032.js delete mode 100644 assets/launching-the-exploit.html.d34fd8dd.js delete mode 100644 assets/launching-the-exploit.html.def2565e.js delete mode 100644 assets/launching-the-exploit.html.e4e9cdca.js delete mode 100644 assets/launching-the-exploit.html.ecb2f285.js delete mode 100644 assets/launching-the-exploit.html.f0417248.js delete mode 100644 assets/launching-the-exploit.html.f8af7505.js create mode 100644 assets/launching-the-flipnote-exploit.html-JdthyTfk.js create mode 100644 assets/launching-the-flipnote-exploit.html-_srbGBVk.js delete mode 100644 assets/launching-the-flipnote-exploit.html.034356bf.js delete mode 100644 assets/launching-the-flipnote-exploit.html.0876db44.js delete mode 100644 assets/launching-the-flipnote-exploit.html.0a3522bf.js delete mode 100644 assets/launching-the-flipnote-exploit.html.0eb71cf2.js delete mode 100644 assets/launching-the-flipnote-exploit.html.26ccad98.js delete mode 100644 assets/launching-the-flipnote-exploit.html.26e8e849.js delete mode 100644 assets/launching-the-flipnote-exploit.html.38f2bf71.js delete mode 100644 assets/launching-the-flipnote-exploit.html.3b658d49.js delete mode 100644 assets/launching-the-flipnote-exploit.html.6385b669.js delete mode 100644 assets/launching-the-flipnote-exploit.html.747bd25d.js delete mode 100644 assets/launching-the-flipnote-exploit.html.81a0596b.js delete mode 100644 assets/launching-the-flipnote-exploit.html.88dfbe64.js delete mode 100644 assets/launching-the-flipnote-exploit.html.90727d02.js delete mode 100644 assets/launching-the-flipnote-exploit.html.9d7e7844.js delete mode 100644 assets/launching-the-flipnote-exploit.html.b1abaa7a.js delete mode 100644 assets/launching-the-flipnote-exploit.html.b31b1900.js delete mode 100644 assets/launching-the-flipnote-exploit.html.bf0f7824.js delete mode 100644 assets/launching-the-flipnote-exploit.html.d926f272.js delete mode 100644 assets/launching-the-flipnote-exploit.html.e8aa3cc4.js delete mode 100644 assets/launching-the-flipnote-exploit.html.f2d4aa58.js delete mode 100644 assets/lazy-dsi-downloader.html.006c7b2d.js delete mode 100644 assets/lazy-dsi-downloader.html.04f5cc4d.js delete mode 100644 assets/lazy-dsi-downloader.html.14116ada.js delete mode 100644 assets/lazy-dsi-downloader.html.28d58a68.js delete mode 100644 assets/lazy-dsi-downloader.html.2c0ec81f.js delete mode 100644 assets/lazy-dsi-downloader.html.3ea557c6.js delete mode 100644 assets/lazy-dsi-downloader.html.4740c1ab.js delete mode 100644 assets/lazy-dsi-downloader.html.4c1748c9.js delete mode 100644 assets/lazy-dsi-downloader.html.55f71b45.js delete mode 100644 assets/lazy-dsi-downloader.html.5d067611.js delete mode 100644 assets/lazy-dsi-downloader.html.7544f72c.js delete mode 100644 assets/lazy-dsi-downloader.html.7b4e5a9d.js delete mode 100644 assets/lazy-dsi-downloader.html.86e9a592.js delete mode 100644 assets/lazy-dsi-downloader.html.a481166a.js delete mode 100644 assets/lazy-dsi-downloader.html.b0feb6a1.js delete mode 100644 assets/lazy-dsi-downloader.html.bc37bdb9.js delete mode 100644 assets/lazy-dsi-downloader.html.c641e21c.js delete mode 100644 assets/lazy-dsi-downloader.html.d4afc485.js delete mode 100644 assets/lazy-dsi-downloader.html.d5c9f358.js delete mode 100644 assets/lazy-dsi-downloader.html.fdbbc18c.js rename assets/{restoring-nand.html.2ab243de.js => restoring-nand.html-5jfrni5j.js} (98%) create mode 100644 assets/restoring-nand.html-Ae4RDn9L.js delete mode 100644 assets/restoring-nand.html.076d43e7.js delete mode 100644 assets/restoring-nand.html.12f57e46.js delete mode 100644 assets/restoring-nand.html.2277286e.js delete mode 100644 assets/restoring-nand.html.345b85d5.js delete mode 100644 assets/restoring-nand.html.3f8abe42.js delete mode 100644 assets/restoring-nand.html.440d7b1d.js delete mode 100644 assets/restoring-nand.html.4ca5e18d.js delete mode 100644 assets/restoring-nand.html.68c83b68.js delete mode 100644 assets/restoring-nand.html.71ab5872.js delete mode 100644 assets/restoring-nand.html.73baeeb4.js delete mode 100644 assets/restoring-nand.html.79bec8cb.js delete mode 100644 assets/restoring-nand.html.86991693.js delete mode 100644 assets/restoring-nand.html.8d05d93c.js delete mode 100644 assets/restoring-nand.html.94dc5222.js delete mode 100644 assets/restoring-nand.html.a4a37179.js delete mode 100644 assets/restoring-nand.html.a4bcdb5d.js delete mode 100644 assets/restoring-nand.html.aa1cdef6.js delete mode 100644 assets/restoring-nand.html.c140fab5.js delete mode 100644 assets/restoring-nand.html.cc032eed.js delete mode 100644 assets/restoring-nand.html.d5a6aa5c.js delete mode 100644 assets/restoring-nand.html.e082d297.js delete mode 100644 assets/sd-card-formatter.7ed06060.js create mode 100644 assets/sd-card-setup.html-DsjOI2JY.js rename assets/{sd-card-setup.html.f2419d41.js => sd-card-setup.html-kwu5A5RY.js} (60%) delete mode 100644 assets/sd-card-setup.html.22c8e099.js delete mode 100644 assets/sd-card-setup.html.3019fa7a.js delete mode 100644 assets/sd-card-setup.html.45cd32d3.js delete mode 100644 assets/sd-card-setup.html.475a1b59.js delete mode 100644 assets/sd-card-setup.html.6124495b.js delete mode 100644 assets/sd-card-setup.html.63bc0df3.js delete mode 100644 assets/sd-card-setup.html.7103f4ff.js delete mode 100644 assets/sd-card-setup.html.73e0246d.js delete mode 100644 assets/sd-card-setup.html.795e25a3.js delete mode 100644 assets/sd-card-setup.html.8c1c5ba4.js delete mode 100644 assets/sd-card-setup.html.9f63dccf.js delete mode 100644 assets/sd-card-setup.html.b40ba6f9.js delete mode 100644 assets/sd-card-setup.html.b8906bf6.js delete mode 100644 assets/sd-card-setup.html.c455c3f0.js delete mode 100644 assets/sd-card-setup.html.cf7c59aa.js delete mode 100644 assets/sd-card-setup.html.db8549e6.js delete mode 100644 assets/sd-card-setup.html.df6fea81.js delete mode 100644 assets/sd-card-setup.html.e3300641.js delete mode 100644 assets/sd-card-setup.html.eeb74b13.js delete mode 100644 assets/sd-card-setup.html.eec340da.js delete mode 100644 assets/sd-card-setup.html.f32e21d9.js delete mode 100644 assets/search.0782d0d1.svg create mode 100644 assets/site-navigation.html-V7nod6VV.js create mode 100644 assets/site-navigation.html-iVOyZHn-.js delete mode 100644 assets/site-navigation.html.10f93cda.js delete mode 100644 assets/site-navigation.html.17673531.js delete mode 100644 assets/site-navigation.html.20134b5d.js delete mode 100644 assets/site-navigation.html.342e2d6b.js delete mode 100644 assets/site-navigation.html.4ddc00bb.js delete mode 100644 assets/site-navigation.html.5174cca6.js delete mode 100644 assets/site-navigation.html.6619cdc1.js delete mode 100644 assets/site-navigation.html.6859e5db.js delete mode 100644 assets/site-navigation.html.6cc07c06.js delete mode 100644 assets/site-navigation.html.709a62ff.js delete mode 100644 assets/site-navigation.html.74a87f92.js delete mode 100644 assets/site-navigation.html.77bd3a65.js delete mode 100644 assets/site-navigation.html.8f6a7ccb.js delete mode 100644 assets/site-navigation.html.8f8c5136.js delete mode 100644 assets/site-navigation.html.a0be164c.js delete mode 100644 assets/site-navigation.html.aa74ff4f.js delete mode 100644 assets/site-navigation.html.b5eb7148.js delete mode 100644 assets/site-navigation.html.b8d0ff60.js delete mode 100644 assets/site-navigation.html.d501ff82.js delete mode 100644 assets/site-navigation.html.e1e96813.js delete mode 100644 assets/site-navigation.html.eee8a0ee.js delete mode 100644 assets/site-navigation.html.f44df8c8.js create mode 100644 assets/style-qWdKKepg.css delete mode 100644 assets/style.f7a00e79.css rename assets/{troubleshooting.html.21bf4878.js => troubleshooting.html-Dr8osdca.js} (90%) create mode 100644 assets/troubleshooting.html-OVpmNPgb.js delete mode 100644 assets/troubleshooting.html.1c66b7dc.js delete mode 100644 assets/troubleshooting.html.38cd1a24.js delete mode 100644 assets/troubleshooting.html.3bcae2fc.js delete mode 100644 assets/troubleshooting.html.3f63e310.js delete mode 100644 assets/troubleshooting.html.413f84d8.js delete mode 100644 assets/troubleshooting.html.53b28a84.js delete mode 100644 assets/troubleshooting.html.63a6da50.js delete mode 100644 assets/troubleshooting.html.753540b9.js delete mode 100644 assets/troubleshooting.html.7775e942.js delete mode 100644 assets/troubleshooting.html.7a5aa972.js delete mode 100644 assets/troubleshooting.html.8ad5ffd0.js delete mode 100644 assets/troubleshooting.html.9922e01d.js delete mode 100644 assets/troubleshooting.html.a217e474.js delete mode 100644 assets/troubleshooting.html.a8869cb1.js delete mode 100644 assets/troubleshooting.html.aee7a89e.js delete mode 100644 assets/troubleshooting.html.b0cf5728.js delete mode 100644 assets/troubleshooting.html.b318b2f2.js delete mode 100644 assets/troubleshooting.html.c448d7a8.js delete mode 100644 assets/troubleshooting.html.d040c9ca.js delete mode 100644 assets/troubleshooting.html.ee6d2b08.js delete mode 100644 assets/troubleshooting.html.fc2ee9e0.js create mode 100644 assets/uninstalling-unlaunch.html-Wbgbkb1X.js rename assets/{uninstalling-unlaunch.html.e732eabc.js => uninstalling-unlaunch.html-xypHBKNg.js} (92%) delete mode 100644 assets/uninstalling-unlaunch.html.0acd41cd.js delete mode 100644 assets/uninstalling-unlaunch.html.0ef36e8f.js delete mode 100644 assets/uninstalling-unlaunch.html.1a51bea3.js delete mode 100644 assets/uninstalling-unlaunch.html.20a31d89.js delete mode 100644 assets/uninstalling-unlaunch.html.3072b863.js delete mode 100644 assets/uninstalling-unlaunch.html.323cc184.js delete mode 100644 assets/uninstalling-unlaunch.html.39deeca0.js delete mode 100644 assets/uninstalling-unlaunch.html.71d5135a.js delete mode 100644 assets/uninstalling-unlaunch.html.7cd5b1ea.js delete mode 100644 assets/uninstalling-unlaunch.html.82c40d22.js delete mode 100644 assets/uninstalling-unlaunch.html.8d9fa8cf.js delete mode 100644 assets/uninstalling-unlaunch.html.a915f92d.js delete mode 100644 assets/uninstalling-unlaunch.html.bfb063ad.js delete mode 100644 assets/uninstalling-unlaunch.html.c4eaff03.js delete mode 100644 assets/uninstalling-unlaunch.html.d4761cc3.js delete mode 100644 assets/uninstalling-unlaunch.html.dde61a18.js delete mode 100644 assets/uninstalling-unlaunch.html.de817425.js delete mode 100644 assets/uninstalling-unlaunch.html.e49a92b2.js delete mode 100644 assets/uninstalling-unlaunch.html.e5089919.js delete mode 100644 assets/uninstalling-unlaunch.html.eeb8812d.js delete mode 100644 assets/uninstalling-unlaunch.html.fe75d8ad.js delete mode 100644 assets/windows-7-folder-options.73715046.js delete mode 100644 de_DE/404.html delete mode 100644 de_DE/alternate-exploits.html delete mode 100644 de_DE/credits.html delete mode 100644 de_DE/dsiware-backups.html delete mode 100644 de_DE/dumping-game-cards.html delete mode 100644 de_DE/dumping-nand.html delete mode 100644 de_DE/faq.html delete mode 100644 de_DE/file-extensions-windows.html delete mode 100644 de_DE/get-started.html delete mode 100644 de_DE/index.html delete mode 100644 de_DE/installing-unlaunch.html delete mode 100644 de_DE/launching-the-browser-exploit.html delete mode 100644 de_DE/launching-the-exploit.html delete mode 100644 de_DE/launching-the-flipnote-exploit.html delete mode 100644 de_DE/lazy-dsi-downloader.html delete mode 100644 de_DE/restoring-nand.html delete mode 100644 de_DE/sd-card-setup.html delete mode 100644 de_DE/site-navigation.html delete mode 100644 de_DE/troubleshooting.html delete mode 100644 de_DE/uninstalling-unlaunch.html delete mode 100644 es_ES/404.html delete mode 100644 es_ES/alternate-exploits.html delete mode 100644 es_ES/credits.html delete mode 100644 es_ES/dsiware-backups.html delete mode 100644 es_ES/dumping-game-cards.html delete mode 100644 es_ES/dumping-nand.html delete mode 100644 es_ES/faq.html delete mode 100644 es_ES/file-extensions-windows.html delete mode 100644 es_ES/get-started.html delete mode 100644 es_ES/index.html delete mode 100644 es_ES/installing-unlaunch.html delete mode 100644 es_ES/launching-the-browser-exploit.html delete mode 100644 es_ES/launching-the-exploit.html delete mode 100644 es_ES/launching-the-flipnote-exploit.html delete mode 100644 es_ES/lazy-dsi-downloader.html delete mode 100644 es_ES/restoring-nand.html delete mode 100644 es_ES/sd-card-setup.html delete mode 100644 es_ES/site-navigation.html delete mode 100644 es_ES/troubleshooting.html delete mode 100644 es_ES/uninstalling-unlaunch.html delete mode 100644 fr_FR/404.html delete mode 100644 fr_FR/alternate-exploits.html delete mode 100644 fr_FR/credits.html delete mode 100644 fr_FR/dsiware-backups.html delete mode 100644 fr_FR/dumping-game-cards.html delete mode 100644 fr_FR/dumping-nand.html delete mode 100644 fr_FR/faq.html delete mode 100644 fr_FR/file-extensions-windows.html delete mode 100644 fr_FR/get-started.html delete mode 100644 fr_FR/index.html delete mode 100644 fr_FR/installing-unlaunch.html delete mode 100644 fr_FR/launching-the-browser-exploit.html delete mode 100644 fr_FR/launching-the-exploit.html delete mode 100644 fr_FR/launching-the-flipnote-exploit.html delete mode 100644 fr_FR/lazy-dsi-downloader.html delete mode 100644 fr_FR/restoring-nand.html delete mode 100644 fr_FR/sd-card-setup.html delete mode 100644 fr_FR/site-navigation.html delete mode 100644 fr_FR/troubleshooting.html delete mode 100644 fr_FR/uninstalling-unlaunch.html delete mode 100644 hu_HU/404.html delete mode 100644 hu_HU/alternate-exploits.html delete mode 100644 hu_HU/credits.html delete mode 100644 hu_HU/dsiware-backups.html delete mode 100644 hu_HU/dumping-game-cards.html delete mode 100644 hu_HU/dumping-nand.html delete mode 100644 hu_HU/faq.html delete mode 100644 hu_HU/file-extensions-windows.html delete mode 100644 hu_HU/get-started.html delete mode 100644 hu_HU/index.html delete mode 100644 hu_HU/installing-unlaunch.html delete mode 100644 hu_HU/launching-the-browser-exploit.html delete mode 100644 hu_HU/launching-the-exploit.html delete mode 100644 hu_HU/launching-the-flipnote-exploit.html delete mode 100644 hu_HU/lazy-dsi-downloader.html delete mode 100644 hu_HU/restoring-nand.html delete mode 100644 hu_HU/sd-card-setup.html delete mode 100644 hu_HU/site-navigation.html delete mode 100644 hu_HU/troubleshooting.html delete mode 100644 hu_HU/uninstalling-unlaunch.html delete mode 100644 it_IT/404.html delete mode 100644 it_IT/alternate-exploits.html delete mode 100644 it_IT/credits.html delete mode 100644 it_IT/dsiware-backups.html delete mode 100644 it_IT/dumping-game-cards.html delete mode 100644 it_IT/dumping-nand.html delete mode 100644 it_IT/faq.html delete mode 100644 it_IT/file-extensions-windows.html delete mode 100644 it_IT/get-started.html delete mode 100644 it_IT/index.html delete mode 100644 it_IT/installing-unlaunch.html delete mode 100644 it_IT/launching-the-browser-exploit.html delete mode 100644 it_IT/launching-the-exploit.html delete mode 100644 it_IT/launching-the-flipnote-exploit.html delete mode 100644 it_IT/lazy-dsi-downloader.html delete mode 100644 it_IT/restoring-nand.html delete mode 100644 it_IT/sd-card-setup.html delete mode 100644 it_IT/site-navigation.html delete mode 100644 it_IT/troubleshooting.html delete mode 100644 it_IT/uninstalling-unlaunch.html delete mode 100644 ja_JP/404.html delete mode 100644 ja_JP/alternate-exploits.html delete mode 100644 ja_JP/credits.html delete mode 100644 ja_JP/dsiware-backups.html delete mode 100644 ja_JP/dumping-game-cards.html delete mode 100644 ja_JP/dumping-nand.html delete mode 100644 ja_JP/faq.html delete mode 100644 ja_JP/file-extensions-windows.html delete mode 100644 ja_JP/get-started.html delete mode 100644 ja_JP/index.html delete mode 100644 ja_JP/installing-unlaunch.html delete mode 100644 ja_JP/launching-the-browser-exploit.html delete mode 100644 ja_JP/launching-the-exploit.html delete mode 100644 ja_JP/launching-the-flipnote-exploit.html delete mode 100644 ja_JP/lazy-dsi-downloader.html delete mode 100644 ja_JP/restoring-nand.html delete mode 100644 ja_JP/sd-card-setup.html delete mode 100644 ja_JP/site-navigation.html delete mode 100644 ja_JP/troubleshooting.html delete mode 100644 ja_JP/uninstalling-unlaunch.html delete mode 100644 pl_PL/404.html delete mode 100644 pl_PL/alternate-exploits.html delete mode 100644 pl_PL/credits.html delete mode 100644 pl_PL/dsiware-backups.html delete mode 100644 pl_PL/dumping-game-cards.html delete mode 100644 pl_PL/dumping-nand.html delete mode 100644 pl_PL/faq.html delete mode 100644 pl_PL/file-extensions-windows.html delete mode 100644 pl_PL/get-started.html delete mode 100644 pl_PL/index.html delete mode 100644 pl_PL/installing-unlaunch.html delete mode 100644 pl_PL/launching-the-browser-exploit.html delete mode 100644 pl_PL/launching-the-exploit.html delete mode 100644 pl_PL/launching-the-flipnote-exploit.html delete mode 100644 pl_PL/lazy-dsi-downloader.html delete mode 100644 pl_PL/restoring-nand.html delete mode 100644 pl_PL/sd-card-setup.html delete mode 100644 pl_PL/site-navigation.html delete mode 100644 pl_PL/troubleshooting.html delete mode 100644 pl_PL/uninstalling-unlaunch.html delete mode 100644 ro_RO/404.html delete mode 100644 ro_RO/alternate-exploits.html delete mode 100644 ro_RO/credits.html delete mode 100644 ro_RO/dsiware-backups.html delete mode 100644 ro_RO/dumping-game-cards.html delete mode 100644 ro_RO/dumping-nand.html delete mode 100644 ro_RO/faq.html delete mode 100644 ro_RO/file-extensions-windows.html delete mode 100644 ro_RO/get-started.html delete mode 100644 ro_RO/index.html delete mode 100644 ro_RO/installing-unlaunch.html delete mode 100644 ro_RO/launching-the-browser-exploit.html delete mode 100644 ro_RO/launching-the-exploit.html delete mode 100644 ro_RO/launching-the-flipnote-exploit.html delete mode 100644 ro_RO/lazy-dsi-downloader.html delete mode 100644 ro_RO/restoring-nand.html delete mode 100644 ro_RO/sd-card-setup.html delete mode 100644 ro_RO/site-navigation.html delete mode 100644 ro_RO/troubleshooting.html delete mode 100644 ro_RO/uninstalling-unlaunch.html delete mode 100644 translate/404.html delete mode 100644 translate/alternate-exploits.html delete mode 100644 translate/credits.html delete mode 100644 translate/dsiware-backups.html delete mode 100644 translate/dumping-game-cards.html delete mode 100644 translate/dumping-nand.html delete mode 100644 translate/faq.html delete mode 100644 translate/file-extensions-(windows).html delete mode 100644 translate/index.html delete mode 100644 translate/installing-unlaunch.html delete mode 100644 translate/launching-the-exploit.html delete mode 100644 translate/lazy-dsi-downloader.html delete mode 100644 translate/restoring-nand.html delete mode 100644 translate/sd-card-setup.html delete mode 100644 translate/site-navigation.html delete mode 100644 translate/troubleshooting.html delete mode 100644 translate/uninstalling-unlaunch.html delete mode 100644 zh_CN/404.html delete mode 100644 zh_CN/alternate-exploits.html delete mode 100644 zh_CN/credits.html delete mode 100644 zh_CN/dsiware-backups.html delete mode 100644 zh_CN/dumping-game-cards.html delete mode 100644 zh_CN/dumping-nand.html delete mode 100644 zh_CN/faq.html delete mode 100644 zh_CN/file-extensions-windows.html delete mode 100644 zh_CN/get-started.html delete mode 100644 zh_CN/index.html delete mode 100644 zh_CN/installing-unlaunch.html delete mode 100644 zh_CN/launching-the-browser-exploit.html delete mode 100644 zh_CN/launching-the-exploit.html delete mode 100644 zh_CN/launching-the-flipnote-exploit.html delete mode 100644 zh_CN/lazy-dsi-downloader.html delete mode 100644 zh_CN/restoring-nand.html delete mode 100644 zh_CN/sd-card-setup.html delete mode 100644 zh_CN/site-navigation.html delete mode 100644 zh_CN/troubleshooting.html delete mode 100644 zh_CN/uninstalling-unlaunch.html diff --git a/404.html b/404.html index 9833f2577..e552ee33a 100644 --- a/404.html +++ b/404.html @@ -3,7 +3,7 @@ - + - - Seite nicht gefunden | DSi-Guide - - - - -
- - - diff --git a/de_DE/alternate-exploits.html b/de_DE/alternate-exploits.html deleted file mode 100644 index 37e8cdb9e..000000000 --- a/de_DE/alternate-exploits.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Alternative Exploits | DSi-Guide - - - - -
DSi-Guide

Alternative Exploits

Trete dem "DS⁽ⁱ⁾ Mode Hacking!" Discord Server bei, um Verbesserungen für die Anleitung vorzuschlagen und Hilfe zu erhalten.

-

Wenn beim Starten der Nintendo DSi-Kamera-Anwendung ein Tutorial angezeigt wird und es beim Versuch, es fertigzustellen abstürzt, kannst du Memory Pit nicht nutzen. Hier findest du alternative Exploits, die anstelle von Memory Pit funktionieren können.

If you have Flipnote Studio installed, you can use Flipnote Lenny.

TIP

Ensure you have set up TWiLight Menu++ on your SD card before proceeding with any of the following.

If you're on an older firmware, you may have access to save game exploits for a select list of gamesin einem neuen Fenster öffnen. These will not be covered here as they are largely obsolete. They should only be used as a last resort, if both Memory Pit and Flipnote Lenny aren't working for you.

petit-compwner will not be usable for the purpose of working around Memory Pit, as it requires a working camera to launch the exploit.

- - - diff --git a/de_DE/credits.html b/de_DE/credits.html deleted file mode 100644 index 36869ea29..000000000 --- a/de_DE/credits.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Credits | DSi-Guide - - - - -
DSi-Guide

Credits

Trete dem "DS⁽ⁱ⁾ Mode Hacking!" Discord Server bei, um Verbesserungen für die Anleitung vorzuschlagen und Hilfe zu erhalten.

-

Die Credits für Personen, welche bei der Website, homebrew und anderen Sachen geholfen haben.

Wenn dir gefällt, was sie gemacht haben, erwäge zu spenden (wenn sie einen Spendenlink haben).

Du kannst auch bei der Anleitung mithelfen, sende nur eine Pull-Requestin einem neuen Fenster öffnen!

Wenn du andere Sprachen kennst, kannst du uns helfen, die Anleitung in diese Sprache zu übersetzen. Trete unserem Crowdin Projektin einem neuen Fenster öffnen bei um anzufangen.

- - - diff --git a/de_DE/dsiware-backups.html b/de_DE/dsiware-backups.html deleted file mode 100644 index 2f60a384c..000000000 --- a/de_DE/dsiware-backups.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - DSiWare Backups | DSi-Guide - - - - -
DSi-Guide

DSiWare Backups

Trete dem "DS⁽ⁱ⁾ Mode Hacking!" Discord Server bei, um Verbesserungen für die Anleitung vorzuschlagen und Hilfe zu erhalten.

-

Anforderungen

Nintendo DSi - Anleitung

Abschnitt I - DSiWare dumpen

  1. Führe GodMode9i aus
  2. Drücke START, um das Startmenü zu öffnen
  3. Wähle Title manager...
    • Wenn dies nicht angezeigt wird, stelle sicher, dass du deine SD-Karte und NAND montiert hast. Wenn du mit hiyaCFW lädst, lade es von einem anderen Ort neu
  4. Wähle den Titel den du dumpen willst
  5. Wähle, was du dumpen willst
  6. Wiederhole Schritt 4-5 für jede DSiWare die du dumpen willst

TIP

Die gedumpte DSiWare befindet sich in sd:/gm9i/out.

- - - diff --git a/de_DE/dumping-game-cards.html b/de_DE/dumping-game-cards.html deleted file mode 100644 index ddb54b856..000000000 --- a/de_DE/dumping-game-cards.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Spielkarten dumpen | DSi-Guide - - - - -
DSi-Guide

Spielkarten dumpen

Trete dem "DS⁽ⁱ⁾ Mode Hacking!" Discord Server bei, um Verbesserungen für die Anleitung vorzuschlagen und Hilfe zu erhalten.

-

Dieser Abschnitt ist zum dumpen von Spielkarten mit GodMode9i, damit sie mit Emulatoren, Flashcards oder deiner SD-Karte via nds-bootstrap gespielt werden können.

Voraussetzungen

  • Die Spielkarte vom Spiel, das du dumpen willst
  • Your Nintendo DSi console with Unlaunch installed

Anweisungen

Abschnitt I - Vorbereitung der SD-Karte

  1. Lade die neueste Version von GodMode9iin einem neuen Fenster öffnen herunter
  2. Entpacke GodMode9i.nds aus dem GodMode9i Archiv und platziere es irgendwo auf deiner SD-Karte

Abschnitt II - Nintendo DSi Anweisungen

  1. Führe GodMode9i aus
  2. Stelle sicher, dass die Spielkarte sich in der Konsole befindet
  3. Wähle die "NDS GAMECARD" option in GodMode9i
  4. Wähle aus, was du dumpen willst
    • Die "Trimmed" Version für die ROM wird eine kleinere Datei dumpen, die SD-Kartenplatz sparen kann, wird aber für die meisten Patches wie ROM Hacks nicht funktionieren
  5. Wiederhole Schritt 2-4 für alle Spielkarten die du dumpen willst

TIP

The dumped Game Cards will be found in sd:/gm9i/out.

- - - diff --git a/de_DE/dumping-nand.html b/de_DE/dumping-nand.html deleted file mode 100644 index 6f97ce9c0..000000000 --- a/de_DE/dumping-nand.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - NAND dumpen | DSi-Guide - - - - -
DSi-Guide

NAND dumpen

Trete dem "DS⁽ⁱ⁾ Mode Hacking!" Discord Server bei, um Verbesserungen für die Anleitung vorzuschlagen und Hilfe zu erhalten.

-

Diese Seite dient dazu ein NAND backup zu erstellen, was eine Kopie der Daten des inneren Speichersystem's des DSi's ist. Dies kann sowohl genutzt werden um hiyaCFW einzurichten, als auch no$gba und melonDS für DSi emulation.

TIP

Make sure the SD card has at least 250MB of free space, or else you'll run into an error message in dumpTool.

TIP

It is highly recommended that you do this. A NAND backup can be used as a restore point in the future, in case of a brick.

Abschnitt 1 -Einrichtung der SD-Karte

TIP

If you have already downloaded dumpTool from another section of this guide, you can skip this section.

  1. Lade dir die neueste Version von dumpToolin einem neuen Fenster öffnen herunter
  2. Platziere dumpTool.nds irgendwo auf deiner SD-Karte

Abschnitt II - NAND-Dump durchführen

  1. Starte dumpTool mithilfe von TWiLight Menu++
  2. Drücke die A Taste auf deinem DSi um den NAND-Dump zu starten
    • Ein NAND-Backup dauert in der Regel um die 7 Minuten
  3. Sobald das NAND-Backup fertig ist, drücke START auf deinem DSi um dumpTool zu verlassen
  4. Schalte die Konsole aus und schiebe die SD-Karte zurück in den Computer
  5. Verschiebe das Nand-Backup an einen Ort, wo es nicht verloren geht
    • Wenn möglich, mache eine Kopie/backup vom Nand-Backup auf verschiedenen Geräten
    • Erst wenn das NAND-Backup auf einem anderen Gerät gespeichert wurde, kann man es von der SD-Karte löschen

WARNING

The SHA1 hash of the nand.bin will not match the hash stored in nand.bin.sha1. This is because dumpTool adds additional data known as a no$gba footer to the nand.bin file after the SHA1 hash is calculated. You can use the hiyaCFW Helperin einem neuen Fenster öffnen to create a copy without the footer.

TIP

Continue to Installing Unlaunch (Optional)

- - - diff --git a/de_DE/faq.html b/de_DE/faq.html deleted file mode 100644 index 55ea85104..000000000 --- a/de_DE/faq.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - FAQ | DSi-Guide - - - - -
DSi-Guide

FAQ

Trete dem "DS⁽ⁱ⁾ Mode Hacking!" Discord Server bei, um Verbesserungen für die Anleitung vorzuschlagen und Hilfe zu erhalten.

-

Sollte ich ein Systemupdate durchführen?

It is not recommended to update your DSi unless you know there are purchased DSiWare. While it still possible to follow this guide if you do so, the only benefit to updating is the ability to access the Nintendo DSi Shop to redownload already purchased titles. All other benefits, such as Facebook integration in the Nintendo DSi Camera application, are no longer usable or are not significant enough to justify the downsides:

  • Installing System Updates is known to occasionally brick consoles, with roughly the same frequency as when installing Unlaunch
  • Older exploits are no longer possible to use, which may be required if you are unable use the recommended exploits
  • Flashcard compatibility is reduced, however this is bypassed if you install Unlaunch

Which is the best exploit?

Unlaunch is overall the best exploit for the DSi, with the only downside being that there is a minor brick risk on install. In general it's recommended to use Memory Pit to install Unlaunch. If you want to avoid any risk it's recommended to instead use Flipnote Lenny as it has fewer issues in homebrew than Memory Pit while being just as safe and simple to remove. Below is a list of the pros and cons of each exploit:

Memory Pit

Pros:

  • Quick and easy to use
  • No risk of damaging the console, uninstalling is as simple as removing the SD or deleting one file
  • Compatible with all DSi consoles unless they have a broken camera and haven't completed the camera tutorial

Cons:

  • Requires loading the DSi Camera application every time you want to access homebrew
  • Incompatible with certain DSi mode titles and homebrew due to WRAM only being open to the ARM7 CPU
  • Access to Slot-1 (the DS Game Card) is blocked in homebrew
  • Access to the DSP is blocked resulting in worse sound in GBARunner2
  • Photos on the SD card cannot be viewed in the DSi Camera application while Memory Pit is installed, as this is the trigger for the exploit
    • The only way to view SD card photos while Memory Pit is installed, is to launch a ROM dump of the DSi Camera application using TWiLight Menu++ to boot it via nds-bootstrap (v0.61.3 or later)

stylehax

Pros:

  • Better compatibility with DSi mode titles and homebrew than Memory Pit
  • Easy to use
  • No risk of damaging the console
  • Useable on consoles with broken camera
  • Better sound in GBARunner2

Cons:

  • Requires internet access
  • Requires loading the DSi Browser every time you want to access homebrew, slightly more time consuming than Memory Pit
  • Access to Slot-1 (the DS Game Card) is blocked in homebrew

Flipnote Lenny

Pros:

  • Better compatibility with DSi mode titles and homebrew than Memory Pit
  • No risk of damaging the console, uninstalling is as simple as removing the SD or deleting one folder
  • Useable on consoles with broken camera
  • Better sound in GBARunner2

Cons:

  • Requires loading Flipnote Studio every time you want to access homebrew, slightly more time consuming than Memory Pit
  • Access to Slot-1 (the DS Game Card) is blocked in homebrew

Unlaunch

Pros:

  • Allows loading homebrew and DSiWare immediately on system boot, with optional button hotkeys
  • Full access to the system without any restrictions, including:
    • Access to Slot-1 allowing dumping Game Cards and loading incompatible flashcards
    • Better sound in GBARunner2
  • Removes region locks on DSi-Enhanced/Exclusive Game Cards
  • Protection against most ways a DSi could brick
  • DSi-Enhanced games can be run in DSi mode without a Donor ROM
  • Old homebrew can be run via nds-bootstrap-hb

Cons:

  • Very minor risk of bricking the console when installing
  • Another, slightly higher, risk of bricking if you decide to uninstall it
  • Not compatible with development consoles

Will I lose any functionality by modding my system?

If you install Unlaunch or use Flipnote Lenny, no functionality will be lost. If you use Memory Pit, you will be unable to view photos on the SD card using the DSi Camera, unless you launch a ROM dump of the DSi Camera application using TWiLight Menu++ to boot it via nds-bootstrap.

  • To regain the ability to view your SD card photos when launching the DSi Camera from the DSi Menu, install Unlaunch or switch to a different exploit, then delete Memory Pit's pit.bin file
    • If tip.bin exists in the same folder, rename it back to pit.bin

How do I play Nintendo DS Game Card dumps?

Playing Game Card dumps on the console requires the use of a flashcard or nds-bootstrap, a program which enables games to be played from the internal SD card by redirecting Slot-1 reads and writes to it.

  • With TWiLight Menu++ you can navigate your SD card to find ROM files to play with nds-bootstrap. The advantages to using TWiLight Menu++ are having a cheat menu, per-game settings, and avoiding the restrictions that forwarders bring. In other words, you can drop your ROM files directly and play without any setup. There is no 39 title limit, neither hiyaCFW or Unlaunch are required and there are no restrictions on SD card free space you can have
  • hiyaCFW users can create forwarders for the SDNAND's DSi Menu using the DS Game Forwardersin einem neuen Fenster öffnen guide on the DS-Homebrew Wiki, but it has some limitations. There is a hard limit of 39 titles, and they are less convenient to make than using TWiLight Menu++

How do I update my homebrew?

  • Unlaunch - Follow the instructions on the Installing Unlaunch page
    • You do not need to uninstall Unlaunch before doing this
  • hiyaCFW - Replace hiya.dsi on the root of the SD card from the updated releasein einem neuen Fenster öffnen
  • TWiLight Menu++ - Follow the instructions on the DS-Homebrew Wikiin einem neuen Fenster öffnen
  • nds-bootstrap - Copy nds-bootstrap-hb-release.nds & nds-bootstrap-release.nds to the _nds folder on the root of your SD card
    • If you use TWiLight Menu++, there is a high chance that the latest nds-bootstrap release is included with TWiLight Menu++
  • GodMode9i, dumpTool, Forwarder3-DS, etc - Follow the instructions used to download them

Other homebrew might use other methods to update.

I am new or I would like to redo my setup. Where do I start?

  • If you have not already modified your console or are looking to update Unlaunch on your system, we recommend starting from the beginning of the guide and following through the pages. Be sure to read everything on the homepage
  • If you have the latest version Unlaunch, follow the TWiLight Menu++ install guidein einem neuen Fenster öffnen to set up TWiLight Menu++ on your system

How can I remove parental controls?

Can I change my Nintendo DSi's region?

Yes, there are a few different methods depending on what you want to change:

What happened to the hiyaCFW installation guide?

Because hiyaCFW does not serve much functional purpose and was a problematic and confusing part of the guide for many users, it was moved to the DS-Homebrew Wikiin einem neuen Fenster öffnen.

  • If you were linked to the page in question from another guide, the instructions you were following were most likely outdated. Please use this guide instead, as it is maintained constantly by the developers of these projects

What kind of SD card should I use?

  • You should buy an SD card from a trusted brand
  • A full-size SD card or a microSD card with an adapter will both work
  • Any capacity between 1 GB and 2 TB will work. For general usage, 8 GB is enough
    • Some software, such as hiyaCFW, may experience incrementally longer loading times with larger SD card capacities
  • Speed class 8 or higher is recommended

Can I use my DSi SD card on other systems?

Generally, yes, with two exceptions:

  • hiyaCFW will only work on the system it was set up for
  • Even if you are using nds-bootstrap or a flashcard, friend codes in online NDS games will be reset when attempting to go online using a different console

How do I switch to a new SD card after setting up homebrew?

Format your new SD card using the SD Card Setup instructions, then simply move your data from the old SD card to the new one.

Can I still use my system normally without the SD card inserted after setting up homebrew?

Yes. If you did not install Unlaunch, your system will remain completely unmodified. If you did install Unlaunch, you may need to configure Unlaunch to automatically boot the original DSi Menu under specified conditions.

The Unlaunch pagein einem neuen Fenster öffnen says that version 2.0 is not known to be safe. Should I use a previous version instead?

The Unlaunch page has not been updated since version 2.0 was released, which was over two years ago. The vast majority of users experience no issues with this version, so it is considered safe.

How do I run dumped DSiWare?

The recommended method is to simply launch them with TWiLight Menu++, due to the simple drag-and-drop method and there being no arbitrary limit. When nds-bootstrap is set as the launch method, it also gains the benefits of cheats and screenshots, as well as any other benefit provided by the in-game menu.

However, for the few titles that are incompatible, you can use NTMin einem neuen Fenster öffnen to install them on either internal memory or hiyaCFW's SDNANDin einem neuen Fenster öffnen. In addition to lacking the benefits above, there is also a limit of 39 titles that cannot exceed 128 MiB/1,024 blocks in size. For SysNAND, there is also a very small risk of bricking the system when writing to the internal NAND.

- - - diff --git a/de_DE/file-extensions-windows.html b/de_DE/file-extensions-windows.html deleted file mode 100644 index 287f6a2fe..000000000 --- a/de_DE/file-extensions-windows.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Dateierweiterungen (Windows) | DSi-Guide - - - - -
DSi-Guide

Dateierweiterungen (Windows)

Trete dem "DS⁽ⁱ⁾ Mode Hacking!" Discord Server bei, um Verbesserungen für die Anleitung vorzuschlagen und Hilfe zu erhalten.

-

Dies ist ein Extraabschnitt zum Deaktivieren vom Standardverhalten von Windows, Dateierweiterungen zu verstecken, welches es vereinfacht, genannte Dateien in der Anleitung zu finden.

  1. Führe den Datei-Explorer aus, indem du ein Verzeichnis, wie beispielsweise das Verzeichnis deiner SD-Karte, öffnest
  2. Click the "View" option on the top bar
    • If the option is not present, click the ··· button on the rightmost part of the top bar
  3. Click or hove your cursor on the Show > submenu
  4. Check the option labeled File name extensions Screenshot of hovering the "File name extensions" checkbox on Windows 11
  1. Führe den Datei-Explorer aus, indem du ein Verzeichnis, wie beispielsweise das Verzeichnis deiner SD-Karte, öffnest
  2. Click the "View" option on the ribbon menu
  3. Check the box labeled "File name extensions" Screenshot of hovering the "File name extensions" checkbox on Windows 10
  1. Open the start menu by clicking on it or using the Windows key
  2. Search for "Folder Options" and select the corresponding result Screenshot of a search for "folder options" in the Windows 7 Start Menu
  3. Click the "View" option at the top of the Folder Options menu
  4. Make sure the box labeled "Hide extensions for known file types" is unchecked Screenshot of the "Folder Options" window on Windows 7 with "Hide extensions for known types" turned off
- - - diff --git a/de_DE/get-started.html b/de_DE/get-started.html deleted file mode 100644 index a08861141..000000000 --- a/de_DE/get-started.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Get Started | DSi-Guide - - - - -
DSi-Guide

Get Started

Trete dem "DS⁽ⁱ⁾ Mode Hacking!" Discord Server bei, um Verbesserungen für die Anleitung vorzuschlagen und Hilfe zu erhalten.

-

The main homebrew application this guide has you install is TWiLight Menu++, which is an upgrade/replacement to the Nintendo DSi Menu that allows running other homebrew applications, retail DS games, emulators for various older systems, and more.

We'll begin with downloading it as well as some other homebrew tool(s), in preparation for the exploit steps.

Anforderungen

Section I - Prep Work

WARNING

Ensure your SD card is formatted correctly.

  1. Insert your SD card into your PC
  2. Download the latest release of TWiLight Menu++in einem neuen Fenster öffnen
  3. Lade dir die neueste Version von dumpToolin einem neuen Fenster öffnen herunter
  4. Copy the _nds folder from TWiLightMenu-DSi.7z to the root of your SD card
  5. Copy the BOOT.NDS file from TWiLightMenu-DSi.7z to the root of your SD card
  6. Copy the dumpTool.nds file to the root of your SD card

TIP

Unsure what the SD "root" is? See this imagein einem neuen Fenster öffnen

Section II - Selecting an exploit

From here you have three options, with a minor difference in what each entails.

Installing Unlaunch via Memory Pit

Memory Pit is an exploit utilizing the DSi Camera, compatible with all firmware versions. Optionally, this exploit can be used to install Unlaunch, a bootcode exploit that allows full control of the console on boot.

As Memory Pit is somewhat limited in homebrew compatibility, it is recommended to install Unlaunch, instead of using Memory Pit standalone. As this is the easiest method to install Unlaunch, this is the recommended path. However, there is a very minor risk of bricking your console when installing Unlaunch, so if this is a concern, see the alternate method below.

TIP

Continue to Launching the Exploit

stylehax

stylehax is an exploit utilizing the DSi Browser application, and can be used as an alternative to Memory Pit for installing Unlaunch (explained above) if your DSi has a broken camera.

For an Unlaunch-free experience, this exploit is recommended as using Memory Pit causes issues in some games and homebrew.

TIP

Continue to Launching the Exploit (stylehax)

Flipnote Lenny

Flipnote Lenny is an exploit utilizing the Flipnote Studio application.

If you have Flipnote Studio and do not plan on installing Unlaunch (explained above), this exploit is recommended for the same reason as stylehax.

You can always install Unlaunch later if you decide later on that you want it.

TIP

Continue to Launching the Exploit (Flipnote Lenny)

For a more detailed pros and cons comparision of the available exploits, please see the Which is the best exploit? FAQ.

- - - diff --git a/de_DE/index.html b/de_DE/index.html deleted file mode 100644 index 4cb855b56..000000000 --- a/de_DE/index.html +++ /dev/null @@ -1,43 +0,0 @@ - - - - - - - - - Startseite | DSi-Guide - - - - -
DSi-Guide

DSi-Guide

Die vollständige Anleitung zum Modifizieren deines Nintendo DSi

TIP

Für komplette Anleitungen zu homebrew und benutzerdefinierter Firmware für andere Geräte, besuche CFW.Anleitungin einem neuen Fenster öffnen.

TIP

Lese alle Einleitungsseiten (einschließlich dieser!) gründlich durch, bevor du fortfährst.

Was ist Homebrew?

Homebrewin einem neuen Fenster öffnen Anwendungen sind unlizensierte Software gemacht für geschlossene Systeme wie den Nintendo DSi. Diese Anwendungen beinhalten Dienstprogramme sowie benutzerdefinierten Homebrew-Spiele.

Homebrew kann gratis auf allen Nintendo DSi Konsolen genutzt werden, unabhängig von Firmware-Version oder Region. Alles was du brauchst ist ein Einstiegspunkt und eine SD-Karte, um dein homebrew zu speichern. Der Haupteinstiegspunkt in dieser Anleitung wird Memory Pit genannt, es gibt aber auch andere Einstiegspunkte, die man verwenden kann, wenn Memory Pit instabil ist.

What can I do by modding my system?

  • Run Nintendo DS(i) game backups or ROM hacks from your DSi SD card without the need of a flashcard
  • Launch any DSiWare from your SD card
    • This means out-of-region and 3DS-exclusive DSiWare will also work
  • Boot into DSiWare and homebrew applications by holding specific buttons when turning on your Nintendo DSi
  • Run old-time classics using various emulators
  • Use normally incompatible flashcards
  • Redirect your NAND to the SD card using hiyaCFW
  • Watch your favorite movies using either FastVideoDSPlayer or tuna-viDS
    • FastVideoDSEncoder requires a CPU supporting AVX2 (newer CPUs will likely support it)
  • Display an image (referred to as the boot splash) on system launch
  • Play homebrew games

Where can I find homebrew applications?

What should I know before starting?

  • On Windows, it's recommended to show file extensions if you are using the default File Explorer
  • The only brick risk comes from installing Unlaunch, and the brick risk is minimal

TIP

Continue to Get Started

- - - diff --git a/de_DE/installing-unlaunch.html b/de_DE/installing-unlaunch.html deleted file mode 100644 index afdb25a0d..000000000 --- a/de_DE/installing-unlaunch.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Installation von Unlaunch | DSi-Guide - - - - -
DSi-Guide

Installation von Unlaunch

Trete dem "DS⁽ⁱ⁾ Mode Hacking!" Discord Server bei, um Verbesserungen für die Anleitung vorzuschlagen und Hilfe zu erhalten.

-

DANGER

If you have not yet done so, please follow Dumping NAND. While the chances are slim, Unlaunch can accidentally brick your Nintendo DSi. A NAND backup + hardmodin einem neuen Fenster öffnen would allow you to restore this backup, provided you know how to solder.

WARNING

Make sure your console is charged when following this process. A sudden power loss could result in serious damage.

WARNING

Unlaunch is not compatible with Nintendo DSi development consoles.

Abschnitt I- SD Kartensetup

  1. Lade die neueste version von Unlaunchin einem neuen Fenster öffnen herunter
  2. Extrahiere UNLAUNCH.DSI vom unlaunch.zip-Archiv und plaziere es irgendwo auf deiner SD Karte
  3. Vergewissere dich, dass sich TWiLight Menu++ auf deiner SD Karte befindet

Abschnitt II - Installation/Updaten von Unlaunch

  1. Öffne TWiLight Menu++
    • If this is your first time installing Unlaunch, relaunch TWiLight Menu++ through the exploit that you used
    • If you have already installed Unlaunch and are looking to update it, hold A + B while booting and select the option labeled TWiLight Menu++
    • If several options are labeled TWiLight Menu++, select the option in where BOOT.NDS is shown at the end of the path on the bottom screen
  2. Starte die TWiLight Menu++ Einstellungen
    • If you haven't changed your theme, press SELECT and touch the small DS icon on the bottom of the touch screen. Sonst sieh dir das TWiLight Menu++ Handbuch an
  3. Drücke L / R or X / Y bis du die Unlaunch einstellungen seite erreichst
  4. Wenn du Unlaunch's Hintergrund ändern willst, wähle Hintergrund aus und suche dir einen Hintergrund aus
  5. Exit TWiLight Menu++ Settings
  6. In the file navigation menu, launch Unlaunch DSi Installer
    • If you see two black screens after launching, download GodMode9iin einem neuen Fenster öffnen, put its .dsi file on the SD root, then launch GodMode9i using TWiLight Menu++, and start Unlaunch.dsi
      This method does not enable Unlaunch to use custom patches and background
  7. Select the "install now" option
    • If Unlaunch freezes at ERROR: MISMATCH IN FAT COPIES, please take a look at the Troubleshooting page
  8. When completed, reboot your system

If you see Unlaunch's Filemenu screen at this point, you have successfully modded your Nintendo DSi.

Abschnitt III - Konfiguration nach Unlaunchinstallation

Currently, Unlaunch defaults to launching its Filemenu on boot, but this can be changed launch whatever you want.

  1. Starte die Konsole während du A und B gedrückt hältst
    • Dies sollte ins Unlaunch Dateimenü starten
    • If only the background is shown, or if no files from the SD card are shown (ex. TWiLight Menu++), then you'll need to reformat the SD card
  2. Navigiere zu OPTIONS und sieh dir die verfügbaren Optionen an
    • A + B ist unveränderbar einprogrammiert, Unlaunch's Dateimenü zu starten
    • Die NO BUTTON und BUTTON A / B / X / Y Optionen können eingestellt werden wie immer man will, und bestimmen, was der DSi beim Systemstart ausführt, je nachdem welche Tasten man gedrückt hält. Man kann jegliche DSiWare, homebrew, die Slot-1 Spielkarte, wifiboot oder Unlaunch's Dateimenü auswählen
      • For TWiLight Menu++, select TWiLight Menu++
      • Für das orgiginale DSi-Menü wähle Launcher
    • LOAD ERROR führt der DSi aus, wenn die ausgewählte Ladeoption nicht funktioniert, z: B. wenn die SD-Karte nicht eingesteckt ist
  3. Wähle SAVE & EXIT, um die Einstellungen zu speichern und schalte deinen DSi aus

Abschnitt IV- Die SD-Karte bereinigen

TIP

This section is optional and only serves for keeping your SD card tidy of files you won't need.

  • Delete the sd:/private/ds/app/484E494A/pit.bin file from your SD card
    • If tip.bin still exists, then rename it back to pit.bin
  • You can now restore the DCIM folder that was on the root of your SD card, if this folder existed
  • Lösche die UNLAUNCH.DSI Datei von deiner SD-Karte
  • Delete the 800031_104784BAB6B57_000.ppm and T00031_1038C2A757B77_000.ppm files from inside the following folders:
    • sd:/private/ds/app/4B47554A/001 (Japan)
    • sd:/private/ds/app/4B475545/001 (USA)
    • sd:/private/ds/app/4B475556/001 (Europe/Australia)
    • You can also delete the entire folders for the regions besides your own
  • Lösche die UNLAUNCH.DSI Datei von deiner SD-Karte
- - - diff --git a/de_DE/launching-the-browser-exploit.html b/de_DE/launching-the-browser-exploit.html deleted file mode 100644 index 53fe69954..000000000 --- a/de_DE/launching-the-browser-exploit.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Launching the Exploit (stylehax) | DSi-Guide - - - - -
DSi-Guide

Launching the Exploit (stylehax)

Trete dem "DS⁽ⁱ⁾ Mode Hacking!" Discord Server bei, um Verbesserungen für die Anleitung vorzuschlagen und Hilfe zu erhalten.

-

We'll start by first launching our exploit. For the best Unlaunch-free experience, or if the DSi camera is broken to install Unlaunch, we recommend using an exploit called "stylehax" which takes advantage of a flaw in how the DSi Browser application handles webpages.

Das Ausführen des Exploits wird TWiLight Menu++ starten, eine Homebrewanwednung, die als Ersatz für das DSi Menü dient.

Anforderungen

  • Nintendo DSi Browser installed on your Nintendo DSi
    • If you do not have the DSi Browser, then use Memory Pit instead

Launching the exploit

  1. Ensure your SD card is inserted into your Nintendo DSi
  2. Boot your Nintendo DSi and launch the DSi Browser application
  3. Touch the Go to Page button
    • The button will have a green www icon
  4. Type opera:about, and touch Go to load the page
  5. Touch the HOME icon
  6. Touch the Go to Page button
  7. Type stylehax.net, and touch Go to load the page

TIP

The exploit should take 21 seconds to take effect. If it takes longer than 30 seconds, then reboot, and try again.

WARNING

If the top screen turns green, you do not have TWiLight Menu++'s BOOT.NDS on the root of your SD card. Follow the prep work again.

You can now use TWiLight Menu++! First, it will ask you to select your language and region. These do not need to match your console's language or region, so set them to whichever you prefer. Next, it's recommended to continue on and make a NAND backup. This can potentially be used to save your console if anything bad happens in the future.

TIP

Continue to Dumping NAND

- - - diff --git a/de_DE/launching-the-exploit.html b/de_DE/launching-the-exploit.html deleted file mode 100644 index f435af2e9..000000000 --- a/de_DE/launching-the-exploit.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Den Exploit ausführen | DSi-Guide - - - - -
DSi-Guide

Den Exploit ausführen

Trete dem "DS⁽ⁱ⁾ Mode Hacking!" Discord Server bei, um Verbesserungen für die Anleitung vorzuschlagen und Hilfe zu erhalten.

-

Wir fangen damit an, die SD-Karte einzurichten, um den Exploit zu starten. Für die meisten Nutzer empfehlen wir einen Exploit namens "Memory Pit", welches einen Fehler in der Handhabung der Bildmetadaten durch die DSi-Kamera-Anwendung ausnutzt.

Das Ausführen des Exploits wird TWiLight Menu++ starten, eine Homebrewanwednung, die als Ersatz für das DSi Menü dient.

TIP

If you don't plan on installing Unlaunch and have either the DSi Browser or Flipnote Studio, it is recommended to use either stylehax or Flipnote Lenny instead. Which is the best exploit?

Section I - Checking your DSi Camera Version

  1. Starte deine Konsole
  2. Open Nintendo DSi Camera
    • If you are prompted to complete the camera tutorial, do so now
    • If the tutorial crashes as you try to complete it, your Nintendo DSi camera hardware is likely broken in some way and you will not be able to use Memory Pit. Please use an alternate exploit
  3. Open the album using the large button on the right
  4. Take note of whether you have a Facebook icon alongside the star, clubs, and heart, outlined in red here: Screenshot of where the Facebook icon is located

Section II - Memory Pit

  1. Download the correct Memory Pit binary for your Nintendo DSi Camera version:
  2. Navigate to the sd:/private/ds/app/484E494A/ folder on your SD card
    • You will already have this directory if you have previously taken photos to your SD card via the Nintendo DSi Camera application. If so, you do not need to delete it and recreate it
    • If it does not exist, please create the individual folders
  3. If there is already a pit.bin file in that path, rename it to tip.bin
  4. Place the Memory Pit pit.bin file in this folder
  5. If there's a folder named DCIM in the root of your SD card, make a back up of it so you don't lose the pictures inside, and then remove it from the SD card

Section III - Launching the exploit

  1. Ensure your SD card is inserted into your Nintendo DSi
  2. Boot your Nintendo DSi and launch the Nintendo DSi Camera application
  3. Select the SD Card icon in the top-right
    • If you receive a message saying your SD card isn't inserted, please use another SD card
    • If you receive a message saying that your SD card cannot be used, ensure your SD card is formatted correctly
  4. Open the album using the large button on the right
    • The screen should flash magenta if Memory Pit was copied correctly

WARNING

If the top screen turns green, you do not have TWiLight Menu++'s BOOT.NDS on the root of your SD card. Follow the prep work again.

WARNING

If you enter the SD card camera album and nothing unusual happens, ensure that you downloaded the correct version of Memory Pit for your version and region, and placed it into the correct folder on your SD card. Also ensure that the DCIM folder does not exist on your SD card.

You can now use TWiLight Menu++! First, it will ask you to select your language and region. These do not need to match your console's language or region so set them to whichever you prefer. Next it's recommended to continue on and make a NAND backup. This can potentially be used to save your console if anything bad happens in the future.

TIP

Continue to Dumping NAND

- - - diff --git a/de_DE/launching-the-flipnote-exploit.html b/de_DE/launching-the-flipnote-exploit.html deleted file mode 100644 index 102f0ccc4..000000000 --- a/de_DE/launching-the-flipnote-exploit.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Launching the Exploit (Flipnote Lenny) | DSi-Guide - - - - -
DSi-Guide

Launching the Exploit (Flipnote Lenny)

Trete dem "DS⁽ⁱ⁾ Mode Hacking!" Discord Server bei, um Verbesserungen für die Anleitung vorzuschlagen und Hilfe zu erhalten.

-

Wir fangen damit an, die SD-Karte einzurichten, um den Exploit zu starten. For the best Unlaunch-free experience, we recommend using an exploit called "Flipnote Lenny" which takes advantage of a flaw in how the Flipnote Studio application handles flipnotes.

Das Ausführen des Exploits wird TWiLight Menu++ starten, eine Homebrewanwednung, die als Ersatz für das DSi Menü dient.

Anforderungen

  • Flipnote Studio installed on your Nintendo DSi
    • If you do not have Flipnote Studio, then use Memory Pit instead

Abschnitt 1 -Einrichtung der SD-Karte

  1. Download the latest version of Flipnote Lennyin einem neuen Fenster öffnen
  2. Copy the private folder from the Flipnote Lenny archive to the root of your SD card

Section II - Launching the exploit

  1. Ensure your SD card is inserted into your Nintendo DSi
  2. Boot your Nintendo DSi and launch the Flipnote Studio application
    • If you receive a message saying that your SD card cannot be used, ensure your SD card is formatted correctly
  3. Open the Flipnote Studio settings on the top-right of the main menu and ensure that Start on Calendar is disabled and Frog is enabled
  4. View the flipnotes stored on the SD card
    • If you are unable to view the flipnotes on the SD card, please use another SD card
  5. Tap on the face corresponding to your region
    • If you have an AUS console, select EUR
  6. Edit the selected flipnote
  7. Tap the frog icon on the bottom-left
  8. Tap on the film roll icon
  9. Select Copy -> Back -> Exit
  10. Tap on the second note with a larger face, and select Edit
  11. Tap on the frog icon on the bottom-left
  12. Tap on the film roll icon
  13. Select paste

WARNING

If the top screen turns green, you do not have TWiLight Menu++'s BOOT.NDS on the root of your SD card. Follow the prep work again.

You can now use TWiLight Menu++! First, it will ask you to select your language and region. These do not need to match your console's language or region, so set them to whichever you prefer. Next, it's recommended to continue on and make a NAND backup. This can potentially be used to save your console if anything bad happens in the future.

TIP

Continue to Dumping NAND

- - - diff --git a/de_DE/lazy-dsi-downloader.html b/de_DE/lazy-dsi-downloader.html deleted file mode 100644 index 4600dfb30..000000000 --- a/de_DE/lazy-dsi-downloader.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Lazy DSi Downloader | DSi-Guide - - - - -
DSi-Guide

Lazy DSi Downloader

Trete dem "DS⁽ⁱ⁾ Mode Hacking!" Discord Server bei, um Verbesserungen für die Anleitung vorzuschlagen und Hilfe zu erhalten.

-

"Lazy DSi Downloader" ist ein Werkzeug, dass den Prozess des Moddens einer Nintendo-DSi-Konsole erleichtern soll.

Verifikationsschritte

  1. Schalte deine Nintendo-DSi-Konsole an
  2. Starte die Nintendo DSi Kamera-Anwendung

If at this point you get a tutorial and crash when trying to follow it, then you cannot use Memory Pit.

Einrichtungsanleitung

  1. Download the latest release of Lazy DSi File Downloaderin einem neuen Fenster öffnen for your OS
  2. Launch it via the instructions for your operating system listed in the release page
  3. Hit the Next button
    • The intro text isn't mandatory to read
  4. If your Nintendo DSi crashed during the verification steps above, toggle off the Memory Pit option
  5. Hit the check boxes for "Download latest GodMode9i version?"
    • Feel free to select any of the other homebrew applications in Click to add Additional homebrew..., but this is not mandatory
  6. Wait for everything to download, then hit Finish
- - - diff --git a/de_DE/restoring-nand.html b/de_DE/restoring-nand.html deleted file mode 100644 index f4bebb336..000000000 --- a/de_DE/restoring-nand.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - NAND-Backup wiederherstellen | DSi-Guide - - - - -
DSi-Guide

NAND-Backup wiederherstellen

Trete dem "DS⁽ⁱ⁾ Mode Hacking!" Discord Server bei, um Verbesserungen für die Anleitung vorzuschlagen und Hilfe zu erhalten.

-

DANGER

WARNUNG! Dies ist gefährlich. Selbst wenn du diesen Schritten exakt folgst, gibt es immer noch ein Risiko, den DSi zu beschädigen, da die NAND sehr niedrige Qualität hat, besonders, wenn du mehrere male flashst! Dies sollte nur als letzter Ausweg benutzt werden!

TIP

Überspringe nichts auf dieser Seite, jeder Fehler erhöht das Risiko stark, den DSi zu beschädigen.

Zunächst ein paar sicherere alternativen, zu dem, was du machen willst:

  • Installation von DSiWare kann mit HiyaCFW oder TWiLight Menu++ durchgeführt werden
  • Bilder können mit ninfsin einem neuen Fenster öffnen, in Kombination mit hiyaCFW oder TWiLight Menu++, wenn du sie auf der Konsole haben willst, wiederhergestellt werden. Die neueste Version vom hiyaCFW Helfer erlaubt dir, während der Einrichtung, deine Fotos von der NAND zur SDNAND zu kopieren
  • Die Wiederherstellung einer Unlaunch Tastenkonfiguration kann über das Unlaunch Menü gemacht werden, welches geöffnet wird, indem man A + B beim Systemstart drückt
  • Löst der Unlaunch Systemstart einen Fehler aus? Entferne deine SD-Karte und versuche einen Systemstart erneut. Wenn es nun funktioniert, dann ist die SD-Karte Schuld und die wiederherstellung eines NAND-Backups wird dies nicht reparieren
  • "An error has occured..." beim Systemstart ist höchstwarscheinlich ein hiyaCFW Fehler und steht nicht im Zusammenhang mit deiner NAND, siehe hiyaCFW FAQ & Problembehandlungin einem neuen Fenster öffnen im DS-Homebrew Wiki für mehr Information
  • Alle Fehler im TWiLight Menu++ stehen nicht damit im Zusammenhang und du solltest versuchen, TWiLight Menu++ erneut zu Installieren oder um Hilfe im Discordin einem neuen Fenster öffnen zu fragen
  • Unlaunch zu deinstallieren, entweder durch NAND flashen oder durch den Deinstallierer sollte gemieden werden, wenn es nicht unbedingt nötig ist, du kannst nämlich die Autostart Tasten zu "Launcher" setzen und dein DSi wird wie normal sein

Die einzige Sache, die du mit deiner NAND machen solltest, ist Unlaunch zu Installieren. Verwende sonst die alternativen.

Voraussetzungen

Das Bios für no$gba Verwendung dumpen

  1. Extrahiere dsibiosdumper.nds vom dsibiosdumper.zip Archiv und plaziere es irgendwo auf deiner SD-Karte
  2. Starte deine Konsole während du A und B gedrückt hältst
    • Dies sollte das Unlaunch Dateimenü starten
  3. Führe dsibiosdumper vom Unlaunch Dateimenü aus
  4. Drücke A, um das BIOS zu deiner SD-Karte zu dumpen
  5. Drücke START, um dsibiosdumper zu verlassen

Teste dein NAND-Backup

Es ist sehr wichtig auszuprobieren, ob dein NAND-Backup funktioniert, bevor du versuchst, es zu deiner Konsole wiederherzustellen, wenn es brick error in no$gba anzeigt, wird es deine Konsole höchstwahrscheinlich auch beschädigen.

  1. Extrahiere NO$GBA.EXE von no$gba-w.zip zu einem Ordner auf deinem Computer
  2. Kopiere dein NAND-BAckup zum Ordner, in den du NO$GBA.EXE plaziert hast und benenne es zu DSI-1.MMC um
  3. Kopiere bios7i.bin und bios9i.bin, genannt BIOSDSI7.ROM und BIOSDSI9.ROM zum Ordner, in den du NO$GBA.EXE plaziert hast.
  4. Führe NO$GBA.EXE aus
  5. Click Options > Emulation Setup to open the Emulation Setup window
  6. Change Reset/Startup Entrypoint to GBA/NDS BIOS (Nintendo logo)
  7. Change NDS Mode/Colors to DSi (retail/16MB)
  8. Click Save Now
  9. Launch any Nintendo DS ROM (.nds file)

If no$gba loads the DSi menu (or the Unlaunch Filemenu), then continue to the next section. If it shows any kind of error do not flash that backup!

Uninstalling Unlaunch from your NAND backup (optional)

Follow this if you dumped your NAND backup after you installed Unlaunch and you would like to uninstall Unlaunch from your system. If you are not trying to uninstall Unlaunch, you do not need to do this section.

  1. Download the latest version of the Unlaunch installerin einem neuen Fenster öffnen
  2. Extract UNLAUNCH.DSI from unlaunch.zip
  3. Launch UNLAUNCH.DSI in no$gba and start it from the Game Card slot
    • This should start the Unlaunch installer, which looks similar to to the Unlaunch Filemenu
  4. Choose Uninstall
  5. Once complete, choose Power down
  6. Launch any Nintendo DS ROM again, and ensure your DSi menu loads and is working properly

If no$gba shows any kind of error instead of loading the DSi menu, do not flash that backup! If you have an older NAND backup you may want to try using that instead. Do not try to uninstall Unlaunch using its uninstaller on the console, it is extremely likely doing so will brick your DSi.

Flashing your NAND backup (Software)

DANGER

Make sure you have read through the above steps as this is where it gets dangerous. If you were linked directly to here without following the above, then go back to the top and read this whole page.

DANGER

Make sure your Nintendo DSi system is well charged before beginning this section.

  1. With your SD card inserted, power on your Nintendo DSi while holding A and B
  2. Launch SafeNANDManager
  3. Press the button to begin NAND restore
  4. Once the restore finishes, press START to turn off your DSi

Your NAND should now be restored.

Flashing your NAND backup (Hardmod)

If you cannot boot your Nintendo DSi, a hardmod is the only way to restore a NAND backup. The best guide that currently exists is the Nintendo DSi hardmod guide on the DS-Homebrew Wikiin einem neuen Fenster öffnen.

- - - diff --git a/de_DE/sd-card-setup.html b/de_DE/sd-card-setup.html deleted file mode 100644 index ac1a09848..000000000 --- a/de_DE/sd-card-setup.html +++ /dev/null @@ -1,85 +0,0 @@ - - - - - - - - - Einrichtung der SD-Karte | DSi-Guide - - - - -
DSi-Guide

Einrichtung der SD-Karte

Trete dem "DS⁽ⁱ⁾ Mode Hacking!" Discord Server bei, um Verbesserungen für die Anleitung vorzuschlagen und Hilfe zu erhalten.

-

This page is for preparing your SD card for your device. In the process, we'll format the SD card and check the card for errors.

DANGER

Make sure to backup your SD card contents BEFORE following this. Your SD card will be WIPED in the process.

Section I - Formatting your SD card with SD Formatter

TIP

This section formats the SD card to the specifications by the SD Card Association. This can fix many issues that may occur with running homebrew applications.

DANGER

Any 64GB or larger SD cards will be formatted to exFAT in this process. You must follow Section II to re-format to FAT32.

  1. Download the latest version of SD Formatterin einem neuen Fenster öffnen
  2. Run SD Card Formatter Setup (the .exe file) in the downloaded .zip file with Adminstrator privileges, then install the program
  3. Run SD Card Formatter from the Start Menu with Adminstrator privileges
  4. Select your SD card
  5. Make sure the Quick Format check box is checked
  6. Press Format to start the format process Screenshot of SD Card Formatter on Windows 11

Section II - Formatting your SD card with GUIFormat

This section formats SD cards larger than 32GB to FAT32.

TIP

If your SD card is 32GB or less in capacity, skip to Section III.

  1. Download the latest version of GUIFormatin einem neuen Fenster öffnen
    • Click on the picture on the website to download the app
  2. Run GUIFormat with Administrator permissions
  3. Select your drive letter
  4. Set the Allocation size unit to 32768
    • If this is too large for your SD, set it to the highest one that works
  5. Make sure the Quick Format check box is checked
  6. Start the format process

Section III - Checking for errors

  1. Go to the properties window of your SD card
    • Windows Explorer -> This PC -> Right click your SD card -> Properties
  2. In the tools tab, Select Check Now
  3. Check both Automatically fix file system errors and Scan for and attempt recovery of bad sectors
  4. Start the checking process

This will scan the SD card and correct any errors it finds.

Section IV - Checking SD card read/write

  1. Download and extract the h2testw archivein einem neuen Fenster öffnen anywhere on your computer
  2. With your SD card inserted into your computer, run h2testw.exe
  3. Select which language you'd like to see h2testw in
  4. Set your SD card's drive letter as your target
  5. Ensure all available space is selected
  6. Click Write + Verify
  • Wait until the process is completed

TIP

If the test shows the result Test finished without errors, your SD card is healthy and you can delete all .h2w files on your SD card.

DANGER

If the test shows any other results, your SD card may be corrupted or damaged and you may have to replace it!

TIP

If TWiLight Menu++ fails to start after following this method, please follow the Windows method instead, by either rebooting to Windows or running a Windows Virtual Machine

Section I - Formatting your SD card

  1. Make sure your SD card is not inserted into your Linux machine
  2. Launch the Linux Terminal
  3. Type watch "lsblk"
  4. Insert your SD card into your Linux machine
  5. Observe the output. It should match something like this:
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
-mmcblk0     179:0    0   3,8G  0 disk
-└─mmcblk0p1 179:1    0   3,7G  0 part /run/media/user/FFFF-FFFF
-
  1. Take note of the device name. In our example above, it was mmcblk0p1
    • If RO is set to 1, make sure the lock switch is not slid down
    • Make sure you're targetting the partition, mmcblk0p1 not mmcblk0
  2. Hit CTRL + C to exit the menu
  3. Follow the instructions relevant to your SD card's capacity:
    • 2GB or lower: sudo mkdosfs /dev/(device name from above) -s 64 -F 16
      • This creates a single FAT16 partition with 32 KB cluster size on the SD card
    • 4GB or higher: sudo mkdosfs /dev/(device name from above) -s 64 -F 32
      • This creates a single FAT32 partition with 32 KB cluster size on the SD card

Section II - Using F3

  1. Download and extract the F3 archivein einem neuen Fenster öffnen anywhere on your computer.
  2. Launch the terminal in the F3 directory
  3. Run make to compile F3
  4. With your SD card inserted and mounted, run ./f3write <your sd card mount point>
    • Wait until the process is complete. See below for an example output:
    $ ./f3write /media/michel/6135-3363/
-Free space: 29.71 GB
-Creating file 1.h2w ... OK!
-...
-Creating file 30.h2w ... OK!
-Free space: 0.00 Byte
-Average Writing speed: 4.90 MB/s
-
  5. Run ./f3read <your sd card mount point>
  • Wait until the process is complete. See below for an example output:
    $ ./f3read /media/michel/6135-3363/
-                  SECTORS      ok/corrupted/changed/overwritten
-Validating file 1.h2w ... 2097152/        0/      0/      0
-...
-Validating file 30.h2w ... 1491904/        0/      0/      0
-
-   Data OK: 29.71 GB (62309312 sectors)
-Data LOST: 0.00 Byte (0 sectors)
-            Corrupted: 0.00 Byte (0 sectors)
-   Slightly changed: 0.00 Byte (0 sectors)
-         Overwritten: 0.00 Byte (0 sectors)
-Average Reading speed: 9.42 MB/s
-

TIP

If the test shows the result Data LOST: 0.00 Byte (0 sectors) your SD card is healthy and you can delete all .h2w files on your SD card.

DANGER

If the test shows any other results, your SD card may be corrupted or damaged and you may have to replace it!

Section I - Formatting your SD card with SD Formatter

TIP

This section formats the SD card to the specifications by the SD Card Association. This can fix many issues that may occur with running homebrew applications.

DANGER

Any 64GB or larger SD cards will be formatted to exFAT in this process. You must follow Section II to re-format to FAT32.

  1. Download the latest version of SD Formatterin einem neuen Fenster öffnen
    • Accept the End User License Agreement to start the download
  2. Run Install SD Card Formatter (the .mpkg file) in the downloaded .zip file
  3. Run SD Card Formatter
  4. Select your SD card
  5. Make sure the Quick Format check box is checked
  6. Start the format process

Section II - Formatting your SD card with Disk Utility

This section formats SD cards larger than 32GB to FAT32.

TIP

If your SD card is 32GB or less in capacity, skip to Section III.

OS X El Capitan (10.11) and later

  1. Launch the Disk Utility application
  2. Select Show All Devices in the top-left View panel
  3. Select your SD card from the sidebar
    • Make sure you choose the correct device, otherwise you might accidentally erase the wrong drive!
  4. Click Erase at the top
  5. Ensure that Format is set to MS-DOS (FAT32)
    • On El Capitan (10.11) through Catalina (10.15) choose MS-DOS (FAT)
  6. Ensure that Scheme is set to Master Boot Record
    • If Scheme does not appear, click Cancel and make sure to choose the device instead of a volume
  7. Click Erase, then click Close

OS X Yosemite (10.10) and earlier

  1. Launch the Disk Utility application
  2. Select your SD card from the sidebar
    • Make sure you choose the correct device, otherwise you might accidentally erase the wrong drive!
  3. Click Partition at the top
    • If Partition does not appear, make sure to choose the device instead of a volume
  4. Ensure that Partition Layout is set to 1 Partition
  5. Ensure that Format is set to MS-DOS (FAT)
  6. From the Options button (below the partition table), select Master Boot Record.
  7. Click OK -> Apply -> Partition

Section III - Using F3

  1. Open Terminal
  2. Install F3 from brew by running brew install f3
  3. With your SD card inserted and mounted, run f3write <your sd card mount point>
    • Wait until the process is complete. See below for an example output:
    $ f3write /Volumes/SD\ CARD
-Free space: 29.71 GB
-Creating file 1.h2w ... OK!
-...
-Creating file 30.h2w ... OK!
-Free space: 0.00 Byte
-Average Writing speed: 4.90 MB/s
-
  4. Run f3read <your sd card mount point>
    • Wait until the process is complete. See below for an example output:
    $ f3read /Volumes/SD\ CARD
-                  SECTORS      ok/corrupted/changed/overwritten
-Validating file 1.h2w ... 2097152/        0/      0/      0
-...
-Validating file 30.h2w ... 1491904/        0/      0/      0
-
-   Data OK: 29.71 GB (62309312 sectors)
-Data LOST: 0.00 Byte (0 sectors)
-            Corrupted: 0.00 Byte (0 sectors)
-   Slightly changed: 0.00 Byte (0 sectors)
-         Overwritten: 0.00 Byte (0 sectors)
-Average Reading speed: 9.42 MB/s
-

TIP

If the test shows the result Data LOST: 0.00 Byte (0 sectors) your SD card is healthy and you can delete all .h2w files on your SD card.

DANGER

If the test shows any other results, your SD card may be corrupted or damaged and you may have to replace it!

TIP

You can now restore the contents of your SD card and continue.

- - - diff --git a/de_DE/site-navigation.html b/de_DE/site-navigation.html deleted file mode 100644 index 99477aeb8..000000000 --- a/de_DE/site-navigation.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Seteinnavigation | DSi-Guide - - - - -
DSi-Guide

Seteinnavigation

Trete dem "DS⁽ⁱ⁾ Mode Hacking!" Discord Server bei, um Verbesserungen für die Anleitung vorzuschlagen und Hilfe zu erhalten.

-

- - - diff --git a/de_DE/troubleshooting.html b/de_DE/troubleshooting.html deleted file mode 100644 index 1cc7fd549..000000000 --- a/de_DE/troubleshooting.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Problembehandlung | DSi-Guide - - - - -
DSi-Guide

Problembehandlung

Trete dem "DS⁽ⁱ⁾ Mode Hacking!" Discord Server bei, um Verbesserungen für die Anleitung vorzuschlagen und Hilfe zu erhalten.

-

Unlaunch

Unlaunch friert ein bei MISMATCH IN FAT COPIES

twlnf hat einen kritischen Fehler, bei dem es nach einer Modifikation das ganze NAND nicht korrekt aktualisiert, wodurch bei manchem Homebrew (z. B. dem Unlaunch Installierer) Fehler ausgelöst werden.

Um dies zu reparieren, öffne NAND Title Manager (NTM)in einem neuen Fenster öffnen und wähle Fix FAT copy mismatch aus.

Es gibt kein Ton- oder Boot-splash beim ausführen von "Launcher" mit Unlaunch

The developer of Unlaunch (nocash) has intentionally patched out the background audio and boot-splash by default. You can regain these effects by reinstalling Unlaunch using TWiLight Menu++ with "Launcher Patches" set to "Default" on the Unlaunch page of TWiLight Menu++ settings, or by using hiyaCFWin einem neuen Fenster öffnen.

Der Systemstart nach Unlaunchinstallation zeigt nur einen schwarzen Bildschirm

Try ejecting the SD card and powering the console on again. If it still only shows a black screen, you may need to flash your NAND via a hardmodin einem neuen Fenster öffnen.

Nach der Unlaunchinstallation stecke ich beim Systemstart in einer Anwendung oder dem Unlaunch Dateimenü fest

This was likely caused by choosing the wrong app for the NO BUTTON option in Unlaunch. Hold A + B while starting the console, go to OPTIONS, and set NO BUTTON to whatever your preference is.

Andere Unlaunch Probleme

If Unlaunch displays Clusters too large, Bad VBR, Bad MBR, or doesn't display any applications while the SD card is inserted, your SD card likely wasn't formatted correctly. Re-follow SD Card Setup.

TWiLight Menu++

For general TWiLight Menu++ troubleshooting, see its FAQ & Troubleshootingin einem neuen Fenster öffnen page on the DS-Homebrew Wiki.

Weitere Assistenz

If you have encountered an issue that is not solved here, or one that persists despite the given solutions, ask for assistance in the DS(i) Mode Hacking!in einem neuen Fenster öffnen Discord server.

- - - diff --git a/de_DE/uninstalling-unlaunch.html b/de_DE/uninstalling-unlaunch.html deleted file mode 100644 index e0e0b9d79..000000000 --- a/de_DE/uninstalling-unlaunch.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Unlaunch Deinstallieren | DSi-Guide - - - - -
DSi-Guide

Unlaunch Deinstallieren

Trete dem "DS⁽ⁱ⁾ Mode Hacking!" Discord Server bei, um Verbesserungen für die Anleitung vorzuschlagen und Hilfe zu erhalten.

-

DANGER

Die Installation oder Deinstallation von Unlaunch könnte deine Konsole beschädigen! Du wurdest gewarnt!

WARNUNG: Die Deinstallation von Unlaunch könnte deinen Nintendo DSi beschädigen. Dies könnten Gründe sein, warum du Unlaunch deinstallieren willst, aber mit Lösungen die keine Deinstallation benötigen.

  • The Unlaunch Background is scary: Reinstall Unlaunch using the new instructions. Sie beschreiben einen Weg, den Hintergrund zu ändern
  • Ich habe ein Problem mit Unlaunch oder der Konsole nach der Installation: Die Troubleshooting Seite erklärt Lösungen für Probleme die sie haben könnten

WARNING

Um das Risiko zu verringern, den DSi zu beschädigen, stelle sicher, dass du keine unzulässige DSiWare zu deinem NAND backup installiert hast (die SDNAND umleitung von hiyaCFW zählt nicht), oder in anderer Weise Systemdateinen manipuliert hast.

WARNING

When uninstalling Unlaunch, you should NOT use its built-in uninstaller directly on your console as there is a chance that it will brick the console. Siehe die korrekte Information zur Deinstallation unten.

Once you have reviewed the above information, follow the Dumping NAND instructions to make a new NAND bacup, then proceed to Restoring a NAND Backup. This will guide you through uninstalling Unlaunch from the NAND backup and flashing that to your console.

If you are not able to use no$gba or get an error after uninstalling Unlaunch in no$gba it is also possible to flash a NAND backup made prior to installing Unlaunch if you still have one, however it is recommended to try using a NAND backup that previously had Unlaunch first. This will make recovery significantly easier in the case of a brick requiring a hardmod as Unlaunch leaves the no$gba footer embedded in the NAND even when uninstalled.

- - - diff --git a/dsiware-backups.html b/dsiware-backups.html index 85c633bb5..25839a51e 100644 --- a/dsiware-backups.html +++ b/dsiware-backups.html @@ -3,7 +3,7 @@ - + - - Página no encontrada | Guía de DSi - - - - -
- - - diff --git a/es_ES/alternate-exploits.html b/es_ES/alternate-exploits.html deleted file mode 100644 index 6eeffe802..000000000 --- a/es_ES/alternate-exploits.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Exploits Alternativos | Guía de DSi - - - - -
Guía de DSi

Exploits Alternativos

Únete al servidor DS⁽ⁱ⁾ Mode Hacking! en Discord para obtener soporte y seguir el desarrollo de la guía.

-

Si al lanzar la aplicación Cámara Nintendo DSi te salta un tutorial y al intentar completarlo la aplicación falla, no puedes usar el exploit Memory Pit. Aquí puedes encontrar exploits alternativos que pueden funcionar de ser este el caso.

Si tienes Flipnote Studio instalado en tu consola, puedes usar Flipnote Lenny.

TIP

Asegúrate de que tienes los archivos necesarios de TWiLight Menu++ en tu tarjeta SD antes de continuar.

Si utilizas una version antigua del firmware de la consola, es posible que puedas usar exploits de archivos de guardado de una lista selecta de juegosabrir en una ventana nueva. Estos no serán cubiertos aquí ya que están, en gran medida, obsoletos. Solo deberían ser utilizados como último recurso, en caso de que ni Memory Pit ni Flipnote Lenny funcionen para ti.

petit-compwner no es una alternativa víable para Memory Pit, ya que requiere que la aplicación de cámara funcione correctamente para lanzar el exploit.

- - - diff --git a/es_ES/credits.html b/es_ES/credits.html deleted file mode 100644 index 5f832f628..000000000 --- a/es_ES/credits.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Créditos | Guía de DSi - - - - -
Guía de DSi

Créditos

Únete al servidor DS⁽ⁱ⁾ Mode Hacking! en Discord para obtener soporte y seguir el desarrollo de la guía.

-

Estos son los créditos para aquellos que han ayudado con el sitio web de la guía, homebrew y otras cosas.

Si te gusta lo que han hecho, considera la posibilidad de donar (si tienen un enlace de donación).

¡Puedes contribuir a nuestra guía simplemente enviando una pull request en GitHubabrir en una ventana nueva!

Si conoces otros idiomas, puedes ayudarnos traduciendo la guía a ese idioma. Puedes unirte a nuestro proyecto en Crowdinabrir en una ventana nueva para empezar.

- - - diff --git a/es_ES/dsiware-backups.html b/es_ES/dsiware-backups.html deleted file mode 100644 index 00d55501f..000000000 --- a/es_ES/dsiware-backups.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Respaldos de DSiWare | Guía de DSi - - - - -
Guía de DSi

Respaldos de DSiWare

Únete al servidor DS⁽ⁱ⁾ Mode Hacking! en Discord para obtener soporte y seguir el desarrollo de la guía.

-

Requisitos

Nintendo DSi - Instrucciones

Sección I - Volcar el título DSiWare

  1. Inicia GodMode9i
  2. Presiona START para abrir el menú START
  3. Selecciona Explorador de títulos...
    • Si esta opción no aparece, asegúrate de que tanto tu tarjeta SD como tu NAND están montadas. Si iniciaste GodMode9i desde hiyaCFW, inícialo desde otra aplicación
  4. Selecciona el título que quieras volcar
  5. Selecciona lo que quieras volcar
  6. Repite los pasos 4 y 5 para todos los títulos DSiWare que quieras volcar

TIP

Lo que hayas volcado estará en la ruta sd:/gm9i/out.

- - - diff --git a/es_ES/dumping-game-cards.html b/es_ES/dumping-game-cards.html deleted file mode 100644 index f22b03859..000000000 --- a/es_ES/dumping-game-cards.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Volcar cartuchos de juegos | Guía de DSi - - - - -
Guía de DSi

Volcar cartuchos de juegos

Únete al servidor DS⁽ⁱ⁾ Mode Hacking! en Discord para obtener soporte y seguir el desarrollo de la guía.

-

Esta sección es para volcar los cartuchos de juegos usando GodMode9i para que puedan ser jugados en emuladores, flashcarts o desde tu tarjeta SD usando nds-bootstrap.

Requisitos

  • El cartucho del juego que quieras volcar
  • Una consola Nintendo DSi con Unlaunch instalado

Instrucciones

Sección I - Preparación de la Tarjeta SD

  1. Descarga la última versión de GodMode9iabrir en una ventana nueva.
  2. Extrae GodMode9i.nds del archivo .7z de GodMode9i y colócalo en cualquier lugar de tu tarjeta SD

Sección II - Instrucciones para Nintendo DSi

  1. Inicia GodMode9i
  2. Asegúrate de que el cartucho de juego esté insertado en la consola
  3. Selecciona la opción "TARJETA DE JUEGO NDS" en GodMode9i
  4. Selecciona lo que quieras volcar
    • La opción "Trimmeado" volcará un archivo más pequeño, útil para ahorrar espacio en la tarjeta SD. Estos archivos no funcionarán para la mayoría de parches y romhacks
  5. Repite los pasos 2 a 4 para todos los cartuchos que quieras volcar

TIP

Las ROMs volcadas estarán en el directorio sd:/gm9i/out.

- - - diff --git a/es_ES/dumping-nand.html b/es_ES/dumping-nand.html deleted file mode 100644 index 129ac0cd3..000000000 --- a/es_ES/dumping-nand.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Hacer Copia de Seguridad de la NAND | Guía de DSi - - - - -
Guía de DSi

Hacer Copia de Seguridad de la NAND

Únete al servidor DS⁽ⁱ⁾ Mode Hacking! en Discord para obtener soporte y seguir el desarrollo de la guía.

-

Esta página es para hacer un respaldo de la NAND, es decir, una copia de los datos en el almacenamiento interno de la consola. Puedes usar este respaldo para configurar HiyaCFW, también para usarlo con los emuladores no$gba y melonDS para emular una consola Nintendo DSi.

TIP

Asegúrate de que la tarjeta SD tenga al menos 250MB de espacio libre, o de lo contrario te encontrarás con un mensaje de error en dumpTool.

TIP

Se recomienda encarecidamente realizar este proceso. Un respaldo de la NAND de tu consola se puede usar para restaurar el sistema en el futuro, en caso que tu sistema deje de funcionar.

Sección I - Configuración de la tarjeta SD

::: consejo

Si ya has descargado dumpTool desde otra sección de esta guía, puedes saltarte esta sección.

:::

  1. Descarga la última versión de dumpToolabrir en una ventana nueva
  2. Coloca dumpTool.nds en cualquier lugar de tu tarjeta SD

Seccion II - Volcar la NAND

  1. Inicia dumpTool desde TWiLight Menu++
  2. Presiona el botón A de la Nintendo DSi para empazar a volcar la NAND
    • Hacer un respaldo de la NAND usualmente toma al rededor de 7 minutos
  3. Cuando el respaldo esté completo, presiona el botón START de tu consola para salir de dumpTool
  4. Apaga la consola e introduce la tarjeta SD en tu dispositivo
  5. Guarda este respaldo en un lugar seguro, donde no puedas perderlo
    • De ser posible, haz multiples copias y almacénalas en dispositivos distintos
    • Cuando lo hayas guardado en otro lugar, puedes borrarlo de la tarjeta SD

::: advertencia

El hash SHA1 del nand.bin no coincidirá con el hash almacenado en nand.bin.sha1. Esto se debe a que dumpTool añade datos adicionales llamados "no$gba footer" al archivo nand.bin después de calcular el hash SHA1. Puedes usar hiyaCFW Helperabrir en una ventana nuevapara crear una copia sin dichos datos.

:::

::: consejo

Continuar a Instalar Unlaunch (Opcional)

:::

- - - diff --git a/es_ES/faq.html b/es_ES/faq.html deleted file mode 100644 index a79e0d092..000000000 --- a/es_ES/faq.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Preguntas Frecuentes | Guía de DSi - - - - -
Guía de DSi

Preguntas Frecuentes

Únete al servidor DS⁽ⁱ⁾ Mode Hacking! en Discord para obtener soporte y seguir el desarrollo de la guía.

-

¿Debería actualizar el sistema?

No se recomienda instalar una actualización a no ser que sepas que se han comprado DSiWare con tu consola. Si bien es posible seguir esta guía si actualizas, el único beneficio real sería acceder a la tienda de Nintendo DSi para volver a descargar tus títulos comprados. Todos los demás beneficios, como la integración de Facebook a la aplicación Cámara Nintendo DSi, ya no son utilizables o suficientemente provechosos para justificar las desventajas:

  • Instalar actualizaciones de sistema ha causado bloqueos totales a algunas consolas, con más o menos la misma frecuenciaque instalar Unlaunch lo ha causado
  • Ya no podrás usar exploits antiguos, lo que es posible que necesites hacer si no puedes usar los exploits recomendados
  • La compatibilidad con flashcards se ve reducida. Instalar Unlaunch previene que esto ocurra

¿Cuál es el mejor exploit?

Unlaunch suele ser la mejor opción. La única desventaja es que tiene un pequeño riesgo de bloqueo total al instalar. En general, se recomienda usar Memory Pit para instalar Unlaunch. Si quieres evitar riesgos, se recomienda usar Flipnote Lenny en su lugar, ya que tiene menos problemas con homebrew que Memory Pit mientras que es igual de seguro y fácil de desinstalar. Abo podrás ver una lista de ventajas y desventajas de cada exploit principal:

Memory Pit

Ventajas:

  • Rápido y fácil de usar
  • No hay riesgo de dañar la consola, y desinstalar es tan simple como remover la tarjeta SD o eliminar un archivo
  • Compatible con todas las consolas DSi a no ser que la cámara esté dañada y el tutorial de la aplicación Cámara DSi no se haya completado

Desventajas:

  • Requiere iniciar la aplicación Cámara Nintendo DSi cada vez que quieras acceder a aplicaciones homebrew
  • Incompativle con ciertos homebrew y títulos en modo DSi debido a que la WRAM sólo es accesible por la CPU ARM7
  • Las aplicaciones homebrew no pueden acceder a la ranura Slot-1 (donde van los cartuchos de DS)
  • El acceso al DSP está bloqueado, lo que resulta en peor calidad de audio en GBARunner2
  • Las fotos en la tarjeta SD no se pueden ver en la aplicación Cámara Nintendo DSi mientras Memory Pit esté instalado, ya que por ahí se accede al exploit
    • La única forma de acceder a las fotos en la tarjeta SD mientras Memory Pit esté instalado, es iniciar una rom volcada de la aplicación Cámara Nintendo DSi usando nds-bootstrap (v0.61.3 o posterior) a través de TWiLight Menu++

stylehax

Ventajas:

  • Mejor compatibilidad con títulos en modo DSi y homebrew, en comparación con Memory Pit
  • Fácil de usar
  • No existe riesgo de averiar la consola
  • Utilizable en las consolas que tengan la cámara averiada
  • Mejor sonido en GBARunner2

Desventajas:

  • Requiere acceso a internet
  • Requiere cargar la aplicación Nintendo DSi Browser cada vez que quieras acceder a aplicaciones homebrew, lo cual es un poco más lento que usar Memory Pit
  • Las aplicaciones homebrew no pueden acceder a la ranura Slot-1 (donde van los cartuchos de DS)

Flipnote Lenny

Ventajas:

  • Mejor compatibilidad con títulos en modo DSi y homebrew, en comparación con Memory Pit
  • No hay riesgo de dañar la consola, y desinstalar es tan simple como remover la tarjeta SD o eliminar una carpeta
  • Utilizable en las consolas que tengan la cámara averiada
  • Mejor sonido en GBARunner2

Desventajas:

  • Requiere cargar Flipnote Studio cada vez que quieras acceder a aplicaciones homebrew, lo cual es un poco más lento que usar Memory Pit
  • Las aplicaciones homebrew no pueden acceder a la ranura Slot-1 (donde van los cartuchos de DS)

Unlaunch

Ventajas:

  • Permite cargar homebrew y títulos DSiWare inmediatamente al encender la consola, con comandos de acceso rápido opcionales
  • Acceso completo a las funciones del sistema sin ninguna restricción, lo que permite:
    • Acceder a la ranura Slot-1, permitiéndote volcar roms de cartuchos de juego y cargar flashcards incompatibles
    • Mejor sonido en GBARunner2
  • Remueve el bloqueo regional en cartuchos de juego con mejoras DSi o exlcusivos para DSi
  • Protección ante la mayoría de formas de ocasionar un bloqueo total
  • Se pueden ejectuar juegos con mejoras DSi en modo DSi sin necesidad de una ROM donante
  • Pueden ejecutarse aplicaciones homebrew antiguas a través de nds-bootstrap-hb

Desventajas:

  • Pequeñísimo riesgo de bloqueo total al instalar
  • Riesgo ligeramente mayor de ocasionar un bloqueo total si decides desinstalarlo
  • No es compatible con consolas de desarrollo

¿Perderé funcionalidades si modifico mi consola?

Si instalas Unlaunch o Flipnote Lenny, no se perderá ninguna funcionalidad. Si usas Memory Pit, no podrás ver las fotos en la tarjeta SD usando la aplicación Camara Nintendo DSi, a no ser que inicies una rom volcada de dicha aplicación usando nds-bootstrap a traves de TWiLight Menu++.

  • Para recuperar la habilidad de ver las fotos en la tarjeta SD al usar la aplicación Camara Nintendo DSi desde el menú DSi, instala Unlaunch o usa un exploit distinto, luego, elimina el archivo pit.bin de Memory Pit
    • Si tip.bin existe en la misma carpeta, renómbralo a pit.bin

¿Cómo juego a ROMs volcadas de cartuchos de Nintendo DS?

Jugar ROMs volcadas en la consola requiere el uso de una flashcart o de nds-bootstrap, un programa que permite cargar juegos desde la tarjeta SD redirigiendo hacia esta las instrucciones de lectura/escritura originalmente dirigidas a la ranura Slot-1 de la consola.

  • Con TWiLight Menu++ puedes navegar por tu tarjeta SD para buscar ROMs que puedas ejecutar con nds-bootstrap. Las ventajas de usar TWiLight Menu++ son: tener un menú de trucos, configuraciones separadas para cada juego, y evitar las restricciones que conlleva utilizar redireccionadores. En otras palabras, puedes colocar ROMs directamente en tu tarjeta SD y jugar sin más configuraciones. No hay límite de 39 juegos por pantalla, no se requieren hiyaFCW o Unlaunch, y no hay restricciones en cuanto al tamaño disponible en la tarjeta SD
  • Los usuarios de hiyaCFW pueden crear redireccionadores a para el Menú DSi de la SDNAND usando la guía para Redireccionadores para juegos de DSabrir en una ventana nueva en la wiki de DS-Homebrew, pero esto tiene algunas limitaciones. Sólo se pueden tener 39 títulos en pantalla, y es menos conveniente hacerlos que usar TWiLight Menu++

¿Como actualizo mis aplicaciones homebrew?

  • Unlaunch - Sigue las instrucciones en la página de Instalación de Unlaunch
    • Ojo, NO es necesario desinstalar Unlaunch antes de hacer esto
  • hiyaCFW - Reemplaza el archivo hiya.dsi en la carpeta raíz de la tarjeta SD con la última versiónabrir en una ventana nueva
  • TWiLight Menu++ - Sigue las instrucciones en la Wiki de DS-Homebrewabrir en una ventana nueva
  • nds-bootstrap - Copia los archivos nds-bootstrap-hb-release.nds y nds-bootstrap-release.nds a la carpeta _nds en la raíz de tu tarjeta SD
    • Si usas TWiLight Menu++, es muy probable que la última versión de nds-bootstrap esté incluida en TWiLight Menu++
  • GodMode9i, dumpTool, Forwarder3-DS, etcétera - Sigue las instrucciones usadas para descargarlos

Otras aplicaciones homebrew pueden usar otros métodos para actualizar.

Soy nuevo o me gustaría rehacer mi configuración. ¿Por dónde empiezo?

  • Si todavía no has modificado tu consola o quieres actualizar Unlaunch en tu sistema, recomendamos empezar por el inicio de esta guía y continuar con las páginas siguientes. Asegúrate de leer todo en la página de inicio
  • Si estás en la última versión de Unlaunch, sigue la guía de instalación de TWiLight Menu++abrir en una ventana nueva para instalar y configurar TWiLight Menu++ en tu sistema

¿Cómo elimino el control parental?

¿Puedo cambiar la región de mi consola?

Sí, hay distintos métodos para hacerlo, dependiendo de lo que quieras cambiar:

¿Qué pasó con la guía de instalación de hiyaCFW?

Como hiyaCFW no tiene mucha utilidad y era una parte problemática y confusa de la guía para muchos usuarios, fue movida a la wiki de DS-Homebrewabrir en una ventana nueva.

  • Si fuiste referido a la página en cuestión desde otra guía, las instrucciones que estabas siguiendo muy probablemente estaban desactualizadas. Se te recomienda seguir esta guía en su lugar, ya que es mantenida y constantemente actualizada por los desarrolladores de estos proyectos

¿Qué tipo de tarjeta SD debería usar?

  • Deberías comprar una tarjeta SD de una marca confiable
  • Funcionarán tanto una tarjeta SD de tamaño normal como una tarjeta micro SD con un adaptador
  • Cualquier capacidad de entre 1 GB y 2 TB funcionarán. 8 GB suele ser suficiente para el uso general
    • Algunas aplicaciones, como hiyaCFW, pueden ver tiempos de carga prolongados según la capacidad de la tarjeta utilizada
  • Se recomienda el uso de tarjetas de velocidad clase 8 o superior

¿Puedo usar la tarjeta SD de mi consola en otros sistemas?

Usualmente, sí, con un par de excepciones:

  • hiyaCFW solo funcionará en el sistema para el que se configuró
  • Incluso si usas nds-bootstrap o una flashcard, los códigos de amigo en juegos en línea se resetearán cuando se intente entrar en línea usando una consola diferente

¿Puedo cambiar de tarjeta SD después de que ya esté todo listo y configurado?

Sí, asegúrate de formatear tu nueva tarjeta SD usando la página de preparación de tarjeta SD, y luego simplemente mueve tus archivos de tu tarjeta antigua a la nueva.

¿Puedo usar mi consola normalmente sin introducir la tarjeta SD después de instalar homebrew?

Sí. Si no instalaste Unlaunch, tu consola permanecerá con el sistema intacto. Si sí instalaste Unlaunch, puede que necesites configurar Unlaunch para iniciar el Menú DSi original automáticamente bajo ciertas condiciones.

La página de Unlaunchabrir en una ventana nueva dice que la versión 2.0 no es segura. ¿Debería usar una versión anterior?

La página de Unlaunch no ha sido actualizada desde que se publicó la versión 2.0, cosa que ocurrió hace más de dos años. La gran mayoría de usuarios no han experimentado problemas usando esta versión, así que puede considerarse segura.

¿Cómo puedo jugar títulos DSi volcados?

La forma recomendado es iniciarlos usando TWiLight Meni++, debido a su métedo simple para añadir juegos al menú, y que no hay un límite arbitrario de cuántos títulos puedes instalar. Si el método de ejecución de DSiWare es nds-bootstrap, además, ganas el beneficio de poder hacer capturas de pantalla y usar trucos, junto con cualquier otra ventaja proporcionada por el menú dentro del juego.

Sin embargo, para los pocos títulos incompatibles, puedes usar NTMabrir en una ventana nueva para instalarlos bien en la memoria interna, o en la SDNAND de hiyaCFWabrir en una ventana nueva. Además de carecer de los beneficios previamente mencionados, también hay un límite de 39 títulos, y no se pueden exceder 128Mib/1024 bloques en tamaño. Para la memoria interna, también hay un pequeño riesgo de bloqueo total del sistema al escribir al almacenamiento interno.

- - - diff --git a/es_ES/file-extensions-windows.html b/es_ES/file-extensions-windows.html deleted file mode 100644 index fdd6c9def..000000000 --- a/es_ES/file-extensions-windows.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Extensiones de archivo (Windows) | Guía de DSi - - - - -
Guía de DSi

Extensiones de archivo (Windows)

Únete al servidor DS⁽ⁱ⁾ Mode Hacking! en Discord para obtener soporte y seguir el desarrollo de la guía.

-

Esta es una sección adicional para desactivar el comportamiento predeterminado de Windows de ocultar las extensiones de archivo, lo que facilitará mucho la búsqueda de archivos referenciados en la guía.

  1. Inicia el explorador de archivos, puedes hacerlo abriendo cualquier carpeta (como la de tu tarjeta SD), o clicando el ícono en la barra de tareas
  2. Haz clic en la opción "Ver" en la barra superior
    • Si la opción no está presente, haz clic en el botón ··· en la parte derecha de la barra superior
  3. Haz clic o mantén el cursor en el submenú Mostrar >
  4. Marca la opción Extensiones de archivo Captura de pantalla al poner el cursor sobre la casilla "extensiones de nombre de archivo" en Windows 11
  1. Inicia el explorador de archivos, puedes hacerlo abriendo cualquier carpeta (como la de tu tarjeta SD), o clicando el ícono en la barra de tareas
  2. Haz clic en la opción "Ver" en el menú de cinta de la barra superior
  3. Marca la opción "Extensiones de nombre de archivo" Captura de pantalla al poner el cursor sobre la casilla "extensiones de nombre de archivo" en Windows 10
  1. Abre el menú de inicio haciendo clic en él o usando la tecla Windows
  2. Busca "Opciones de carpeta" y selecciona el resultado con el mismo nombre Captura de pantalla al buscar "opciones de carpeta" en el menú inicio de Windows 7
  3. Haz clic en la opción "Ver" en la parte superior del menú Opciones de carpeta
  4. Asegúrate de que la casilla "Ocultar extensiones para tipos de archivo conocidos" no está marcada Captura de pantalla de la ventana "Opciones de carpeta" con la opción "Ocultar extensiones de archivo" desmarcada en Windows 7
- - - diff --git a/es_ES/get-started.html b/es_ES/get-started.html deleted file mode 100644 index 200bf3b65..000000000 --- a/es_ES/get-started.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Empezando el proceso | Guía de DSi - - - - -
Guía de DSi

Empezando el proceso

Únete al servidor DS⁽ⁱ⁾ Mode Hacking! en Discord para obtener soporte y seguir el desarrollo de la guía.

-

La aplicación homebrew principal que esta guía te ayuda a instalar es TWiLight Menu++, que es una versión mejorada/un reemplazo del Menú Nintendo DSi, que te permite ejecutar otras aplicaciones homebrew, juegos comerciales, emuladores para varios sistemas antiguos, y demás.

Comenzaremos descargándolo, junto con otra(s) herramienta(s) homebrew, a modo de preparación para lanzar un exploit.

Requisitos

Sección I - Preparación

WARNING

Asegúrate de que tu tarjeta SD esté formateada correctamente.

  1. Inserta tu tarjeta SD en tu ordenador
  2. Descarga la version más reciente de TWiLight Menu++abrir en una ventana nueva
  3. Descarga la versión más reciente de dumpToolabrir en una ventana nueva
  4. Copia la carpeta _nds del archivo TWiLightMenu.DSi.7z a la carpeta raíz de tu tarjeta SD
  5. Copia el archivo BOOT.NDS del archivo TWiLightMenu-DSi.7z a la carpeta raíz de tu tarjeta SD
  6. Copia el archivo dumpTool.nds a la carpeta raíz de tu tarjeta SD

TIP

Si no sabes qué carpeta es la carpeta raíz, echa un vistazo a esta imagenabrir en una ventana nueva

Sección II - Elegir un exploit

A partir de aquí, tienes tres opciones, cada una implica un proceso ligeramente distinto.

Instalar Unlaunch usando Memory Pit

Memory Pit es un exploit que utiliza la aplicación Cámara Nintendo DSi, compatible con todas las versiones de firmware. De forma opcional, este exploit puede ser usado para instalar Unlaunch, un exploit de código de arranque que permite control total de la consola al encenderla.

Ya que Memory Pit está algo limitado en cuanto a compatibilidad, se recomienda instalar Unlaunch en lugar de usar Memory Pit exclusivamente. Ya que este es el método más fácil de instalar Unlaunch, esta es la opción recomendada. Sin embargo, hay un pequeñísimo riesgo de causar un bloqueo total de la consola al instalar Unlaunch, así que si la posibilidad te preocupa, echa un vistazo al método de más abajo.

TIP

Continuar a Lanzar el Exploit

stylehax

stylehax es un exploit que utiliza la aplicación Nintendo DSi Browser, y puede ser usado como una alternativa a Memory Pit para instalar Unlaunch si tu consola tiene la cámara averiada.

Si no quieres instalar Unlaunch, se recomienda usar este exploit ya que Memory Pit causa problemas en algunos juegos y aplicaciones homebrew.

TIP

Continuar a Lanzar el Exploit (stylehax)

Flipnote Lenny

Flipnote Lenny es un exploit que utiliza la aplicación Flipnote Studio.

Si tienes Flipnote Studio y no planeas instalar Unlaunch, se recomienda usar este exploit por la misma razón que stylehax.

Siempre puedes instalar Unlaunch más tarde si es lo que deseas.

TIP

Continuar a Lanzar el Exploit (Flipnote Lenny)

Para una comparación más detallada de ventajas y desventajas de cada exploit, echa un vistazo a la pregunta ¿Cuál es el mejor exploit? en la página de Preguntas Frecuentes.

- - - diff --git a/es_ES/index.html b/es_ES/index.html deleted file mode 100644 index da2a6a6b6..000000000 --- a/es_ES/index.html +++ /dev/null @@ -1,43 +0,0 @@ - - - - - - - - - Inicio | Guía de DSi - - - - -
Guía de DSi

Guía de DSi

Una guia completa para modificar tu Nintendo DSi

TIP

Para guías completas sobre homebrew y custom firmware para otros dispositivos, revisa la Guía CFWabrir en una ventana nueva.

TIP

Lea detenidamente todas las páginas introductorias (¡incluyendo esta!) antes de proceder.

¿Qué es el homebrew?

Las aplicaciones Homebrewabrir en una ventana nueva son piezas de software sin licencia hechas para sistemas cerrados, como la Nintendo DSi. El objetivo puede variar, desde ser usadas como herramientas hasta ser jugadas como juegos no licenciados.

Las aplicaciones Homebrew pueden ejecutarse de forma gratuita en todas las consolas Nintendo DSi, independientemente de la versión de firmware o de la región. Todo lo que necesitas es un punto de entrada y una tarjeta SD para almacenar tu homebrew. El punto de entrada principal usado en esta guía se llama Memory Pit (foso de memoria), pero existen otros puntos de entrada que puedes utilizar en caso de que no puedas hacer provecho de Memory Pit.

Si modifico my consola, ¿qué puedo hacer?

  • Ejecutar ROMs volcadas de juegos para Nintendo DS(i) desde la tarjeta SD de tu consola, sin necesidad de una flashcart
  • Ejecutar cualquier título DSiWare desde tu tarjeta SD
    • Incluyendo títulos fuera de tu región y títulos DSiWare exclusivos de 3DS
  • Iniciar automáticamente DSiWare y aplicaciones Homebrew al mantener pulsados ciertos botónes mientras enciendes tu consola
  • Ejecutar títulos de consolas clásicas utilizando distintos emuladores
  • Utilizar flashcarts normalmente incompatibles
  • Redirigir tu NAND a la tarjeta SD usando hiyaCFW
  • Ver tus películas favoritas usando FastVideoDSPlayer o tuna-viDS
    • FastVideoDSEncoder requiere un CPU que soporte AVX2 (es probable que las CPUs más recientes lo soporten)
  • Mostrar una imagen (llamada boot splash) al inciar el sistema
  • Ejecutar aplicaciones y juegos homebrew

¿Dónde puedo encontrar aplicaciones homebrew?

¿Qué debería saber antes de empezar?

  • En Windows se recomienda mostrar extensiones de archivo si estas usando el explorador de archivos por defecto
  • El único riesgo de bloqueo total del sistema viene de instalar Unlaunch, pero este riesgo es sumamente pequeño

TIP

Continuar a Empezando el proceso

- - - diff --git a/es_ES/installing-unlaunch.html b/es_ES/installing-unlaunch.html deleted file mode 100644 index e8be1ffc1..000000000 --- a/es_ES/installing-unlaunch.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Instalar Unlaunch | Guía de DSi - - - - -
Guía de DSi

Instalar Unlaunch

Únete al servidor DS⁽ⁱ⁾ Mode Hacking! en Discord para obtener soporte y seguir el desarrollo de la guía.

-

DANGER

Si aún no lo has hecho, por favor, haz una copia de seguridad de la NAND. Si bien las probabilidades son escasas, Unlaunch puede bloquear totalmente tu consola de forma accidental. Una copia de respaldo de la NAND y modificación del hardwareabrir en una ventana nueva te permiten restaurar esta copia de respaldo, siempre y cuando sepas como soldar.

WARNING

Asegúrate de que tu consola está cargada mientras sigues estos pasos. Si el sistema se apaga repentinamente en medio del proceso, podría causar daños graves.

WARNING

Unlaunch no es compatible con consolas de desarrollo de Nintendo DSi.

Sección I - Preparación de la tarjeta SD

  1. Descarga la última version de Unlaunchabrir en una ventana nueva
  2. Extrae UNLAUNCH.DSI del archivo unlaunch.zip, y colócalo en cualquier lugar de tu tarjeta SD
  3. Comprueba que aún tienes TWiLight Menu++ en tu tarjeta SD

Sección II - Instalar/Actualizar Unlaunch

  1. Abre TWiLight Menu++
    • Si esta es tu primera vez instalando Unlaunch, lanza TWiLight Menu++ a través del exploit que utilizaste anteriormente
    • Si ya has instalado Unlaunch y lo que quieres es actualizarlo, mantén presionados A y B mientras enciendes la consola, y escoge la opción TWiLight Menu++
    • Si aparecen varias opciones con el nombre TWiLight Menu++, escoge la opción en la que se muestra BOOT.NDS al final de la ruta en la pantalla inferior
  2. Entra en la configuración de TWiLight Menu++
    • Por defecto, puedes entrar en los ajustes presionando SELECT y tocando el pequeño botón con un ícono de DS en la parte inferior de la pantalla táctil. Si has cambiado el tema, consulta el manual de TWiLight Menu++ para saber como entrar en los ajustes
  3. Presiona L/R o X/Y hasta que llegues a la sección Ajustes de Unlaunch.
  4. Si quieres cambiar el la imágen que Unlaunch utiliza como fondo. selecciona la opción Fondo y elige el que quieras.
  5. Sal de la Configuración de TWiLight Menu++
  6. En el menú de navegación de archivos, ejecuta la aplicación Unlaunch DSi Installer
    • Si ves dos pantallas negras después de lanzar, descarga GodMode9iabrir en una ventana nueva, pon su . si en la raíz SD, luego inicia GodMode9i usando TWiLight Menu+++, e inicia Desiniciar. si
      Este método no habilita Unlaunch para usar parches personalizados y fondo
  7. Selecciona la opción "Install now"
    • Si Unlaunch se congela y muestra el mensaje ERROR: MISMATCH IN FAT COPIES, echa un vistazo a la página de solución de problemas
  8. Al terminar, reinicia tu consola

Si en este punto ves el sistema de archivos de Unlaunch, significa que has modificado exitosamente tu Nintendo DSi.

Sección III - Configuración posterior

Por defecto, Unlaunch inicia su sistema de archivos al encender la consola, pero esto puede ser cambiado para iniciar lo que desees.

  1. Enciende tu consola mientras mantienes pulsado A y B.
    • Esto deberia iniciar el sistema de archivos de Unlaunch.
    • Si sólo se muestra el fondo, o si no se muestran archivos de la tarjeta SD (ej.: TWiLight Menu++), necesitarás reformatear tu tarjeta SD
  2. Ve a OPTIONS y echa un vistazo a las opciones disponibles.
    • La opción A + B está configurada para inciar el sistema de archivos de Unlaunch. Esta opción está bloqueada y no puede ser cambiada.
    • Las opciónes NO BUTTON y BUTTON A / B / X / Y pueden ser modificadas como quieras para escoger qué cargará tu consola al encenderse dependiendo de los botones que mantengas persionados. Puedes configurar estas opciones para iniciar cualquier título DSiWare, Homebrew, la ranura Slot-1, Wifiboot o el sistema de archivos de Unlaunch.
      • Para TWiLight Menu++, escoge TWiLight Menu++
      • Para que alguna de estas opciones inicie el Menú DSi original, selecciona el archivo Launcher.
    • La opción LOAD ERROR es en lo que tu DSi iniciará si lo que tú hayas configurado falla, como por ejemplo, una archivo en la tarjeta SD cuando esta no está en la consola.
  3. Selecciona SAVE & EXIT para guardar la configuración, luego, apaga la consola.

Sección IV - Limpiar la tarjeta SD

TIP

Esta sección es opcional y solo sirve para mantener ordenada la tarjeta SD y remover archivos que no necesites.

  • Elimina el archivo sd:/private/ds/app/484E494A/pit.bin de tu tarjeta SD
    • Si tip.bin aún existe, renómbralo de vuelta a pit.bin
  • Ahora puede restaurar la carpeta DCIM que se encontraba en la carpeta raíz de su tarjeta SD, si esta carpeta existía
  • Elimina el archivo UNLAUNCH.DSI de tu tarjeta SD
  • Elimina los archivos 800031_104784BAB6B57_000.ppm y T00031_1038C2A757B77_000.ppm de dentro de las siguientes carpetas:
    • sd:/private/ds/app/4B47554A/001 (Japón)
    • sd:/private/ds/app/4B475545/001 (EEUU)
    • sd:/private/ds/app/4B475556/001 (Europa/Australia)
    • También puedes eliminar las carpetas de otras regiones que no sean la tuya
  • Elimina el archivo UNLAUNCH.DSI de tu tarjeta SD
- - - diff --git a/es_ES/launching-the-browser-exploit.html b/es_ES/launching-the-browser-exploit.html deleted file mode 100644 index 514662e95..000000000 --- a/es_ES/launching-the-browser-exploit.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Lanzar el Exploit (stylehax) | Guía de DSi - - - - -
Guía de DSi

Lanzar el Exploit (stylehax)

Únete al servidor DS⁽ⁱ⁾ Mode Hacking! en Discord para obtener soporte y seguir el desarrollo de la guía.

-

Comenzemos con el proceso para iniciar el exploit. Para obtener una mejor experiencia sin Unlaunch, o si la cámara de la consola está averiada y no puedes instalar Unlaunch, recomendamos usar un exploit llamado "stylehax," que se aprovecha de una falla en cómo la aplicación Nintendo DSi Browser maneja las páginas web.

Lanzar el exploit hará que inicies TWiLight Menu++, una aplicación homebrew que actúa como un reemplazo del Menú DSi.

Requisitos

  • Tener Nintendo DSi Browser instalado en tu consola
    • Si no tienes la aplicación instalada, usa Memory Pit en su lugar

Lanzar el exploit

  1. Asegúrate de que tu tarjeta SD está insertada en tu consola
  2. Enciende tu consola e inicia la aplicación Nintendo DSi Browser
  3. Toca el botón Ir a página
    • El botón tendrá un gráfico www de color verde
  4. Escribe opera:about, y luego toca Ir para cargar la página
  5. Toca el botón con el ícono de una casa
  6. Toca el botón Ir a página
  7. Escribe stylehax.net, y luego toca Ir para cargar la página

TIP

El exploit debería tardar 21 segundos en hacer efecto. Si toma más de 30 segundos, reinicia tu consola e inténtalo nuevamente.

WARNING

Si la pantalla superior se torna verde, no tienes el archivo BOOT.NDS de TWiLight Menu++ en la carpeta raíz de tu tarjeta SD. Sigue la guía de preparación de nuevo.

¡Ahora puedes usar TWiLight Menu++! Primero se te pedirá que selecciones tu lenguaje y región. Estos no tienen que coincidir con el lenguaje or región de tu consola, así que puedas configurarlo como prefieras. A continuación se recomienda que hagas una copia de seguridad de la NAND. Puedes usarla para restaurar tu consola a un estado seguro si algo malo ocurre en el futuro.

TIP

Continuar a Hacer Copia de Seguridad de la NAND

- - - diff --git a/es_ES/launching-the-exploit.html b/es_ES/launching-the-exploit.html deleted file mode 100644 index ca790f69d..000000000 --- a/es_ES/launching-the-exploit.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Lanzar el Exploit | Guía de DSi - - - - -
Guía de DSi

Lanzar el Exploit

Únete al servidor DS⁽ⁱ⁾ Mode Hacking! en Discord para obtener soporte y seguir el desarrollo de la guía.

-

Empezaremos primero preparando tu tarjeta SD para iniciar nuestro exploit. Para la mayoría de usuarios, recomendamos usar un exploit llamado "Memory Pit", que se aprovecha de un fallo en como la aplicaión Cámara Nintendo DSi maneja los metadatos de las imágenes.

Lanzar el exploit hará que inicies TWiLight Menu++, una aplicación homebrew que actúa como un reemplazo del Menú DSi.

TIP

Si no planea instalar la desejecución y tiene el DSi Browser o Flipnote Studio, se recomienda usar stylehax o Flipnote Lenny en su lugar. ¿No sabes cual exploit es el mejor para ti?

Sección I - Comprobar la versión de la aplicación de la cámara

  1. Enciende tu consola
  2. Abre la aplicación Cámara Nintendo DSi
    • Si se te pide completar el tutorial de la cámara, hazlo
    • Si el tutorial se cuelga antes de terminar, es probable que los componentes necesarios para usar la cámara de tu consola estén dañados de alguna forma, y no podrás usar Memory Pit. En este caso tendrás que usar un exploit alternativo
  3. Abre el álbum usando el botón grande que está en la derecha
  4. Toma nota de si hay un icono de Facebook junto a las figuras de estrella, trébol y corazón que se resaltan en rojo aquí: Captura de pantalla de donde se encuentra el icono de Facebook

Sección II - Memory Pit

  1. Descarga el archivo binario de Memory Pit correspondiente a la versión de la aplicación Cámara Nintendo DSi:
  2. Ve a la carpeta sd:/private/ds/app/484E494A/ en su tarjeta SD
    • Si anteriormente has tomado o copiado fotos a tu tarjeta SD a través de la aplicación Cámara Nintendo DSi, este directorio ya debería existir. De ser el caso, no necesitas eliminarlo y crearlo nuevamente
    • Si este directorio no existe, por favor, crea las carpetas de foma individual
  3. Si ya hay un archivo llamado pit.binen esa ruta, cámbiale el nombre a tip.bin
  4. Coloca el archivo pit.bin de Memory Pit en esta carpeta
  5. Si hay una carpeta llamada DCIM en la carpeta raíz de tu tarjeta SD, haz un respaldo para que no pierdas las fotos que hay dentro, y remuévela de la tarjeta SD

Seccion III - Lanzar el exploit

  1. Asegúrate de que tu tarjeta SD está insertada en tu consola
  2. Enciende la consola e inicia la aplicación Cámara Nintendo DSi
  3. Selecciona el icono de tarjeta SD en la esquina superior derecha
    • Si recibes un mensaje diciendo que tu tarjeta SD no está insertada, por favor, usa otra tarjeta SD
    • Si recibes un mensaje diciendo que no se puede utilizar tu tarjeta SD, asegúrate de que tu tarjeta SD esté formateada correctamente
  4. Abre el álbum con el botón grande de la derecha
    • La pantalla debería parpadear y mostrar el color magenta si el exploit se lanza de forma exitosa

WARNING

Si la pantalla superior se torna verde, no tienes el archivo BOOT.NDS de TWiLight Menu++ en la carpeta raíz de tu tarjeta SD. Sigue la guía de preparación de nuevo.

WARNING

Si ingresas al álbum de la tarjeta SD y no pasa nada inusual, asegúrate de que descargaste la versión correcta de Memory Pit para la versión y región de tu consola, y que la colocaste en la carpeta correcta en tu tarjeta SD. Asegúrate también de que la carpeta DCIM no existe en tu tarjeta SD.

¡Ahora puedes usar TWiLight Menu++! Primero se te pedirá que selecciones tu lenguaje y región. Estos no tienen que coincidir con el lenguaje or región de tu consola, así que puedas configurarlo como prefieras. A continuación se recomienda que hagas una copia de seguridad de la NAND. Puedes usarla para restaurar tu consola a un estado seguro si algo malo ocurre en el futuro.

TIP

Continuar a Hacer Copia de Seguridad de la NAND

- - - diff --git a/es_ES/launching-the-flipnote-exploit.html b/es_ES/launching-the-flipnote-exploit.html deleted file mode 100644 index d1b732383..000000000 --- a/es_ES/launching-the-flipnote-exploit.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Lanzar el Exploit (Flipnote Lenny) | Guía de DSi - - - - -
Guía de DSi

Lanzar el Exploit (Flipnote Lenny)

Únete al servidor DS⁽ⁱ⁾ Mode Hacking! en Discord para obtener soporte y seguir el desarrollo de la guía.

-

Empezaremos preparando tu tarjeta SD para iniciar nuestro exploit. Para la mejor experiencia libre de Unlaunch, recomendamos usar un exploit llamado "Flipnote Lenny", que toma ventaja de un fallo en como la aplicación Flipnote Studio maneja las flipnotes.

Lanzar el exploit hará que inicies TWiLight Menu++, una aplicación homebrew que actúa como un reemplazo del Menú DSi.

Requisitos

  • Tener Flipnote Studio instalado en tu Nintendo DSi
    • Si no tienes Flipnote Studio, usa Memory Pit en su lugar

Sección I - Preparación de la Tarjeta SD

  1. Descarga la última versión de Flipnote Lennyabrir en una ventana nueva
  2. Copia la carpeta private del archivo de Flipnote Lenny a la carpeta raíz de tu tarjeta SD

Seccion II - Lanzar el exploit

  1. Asegúrate de que tu tarjeta SD está insertada en tu consola
  2. Enciende tu consola e inicia la aplicación Flipnote Studio
    • Si recibes un mensaje diciendo que no se puede utilizar tu tarjeta SD, asegúrate de que tu tarjeta SD esté formateada correctamente
  3. Abre los ajustes de Flipnote Studio tocando la llave en la esquina superior derecha del menú principal, y asegúrate de que la opción Calendario al inicio esté desactivada y que la opción 🐸 Rana esté activada
  4. Toca en "Ver Notas" y luego en "Tarjeta SD"
    • Si no puedes ver las notas en la tarjeta SD, por favor usa otra tarjeta SD
  5. Toca en la nota con la cara correspondiente a tu región
    • Si tu consola es de la región AUS, selecciona EUR
  6. Modifica la nota seleccionada
  7. Toca el ícono de la rana en la ezquina inferior izquierda
  8. Toca el ícono de rollo de película
  9. Toca en Copiar, luego en Atrás, y luego en Salir
  10. Toca en la segunda nota con una cara más grande, toca Modificar
  11. Toca el ícono de la rana en la ezquina inferior izquierda
  12. Toca el ícono de rollo de película
  13. Toca en pegar

WARNING

Si la pantalla superior se vuelve verde, no tienes el archivo BOOT.NDS de TWiLight Menu++ en la carpeta raíz de tu tarjeta SD. Sigue la guía de preparación de nuevo.

¡Ahora puedes usar TWiLight Menu++! Primero se te pedirá que selecciones tu lenguaje y región. Estos no tienen que coincidir con el lenguaje or región de tu consola, así que puedas configurarlo como prefieras. A continuación se recomienda que hagas una copia de seguridad de la NAND. Puedes usarla para restaurar tu consola a un estado seguro si algo malo ocurre en el futuro.

TIP

Continuar a Hacer Copia de Seguridad de la NAND

- - - diff --git a/es_ES/lazy-dsi-downloader.html b/es_ES/lazy-dsi-downloader.html deleted file mode 100644 index 00ae059ca..000000000 --- a/es_ES/lazy-dsi-downloader.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Lazy DSi Downloader | Guía de DSi - - - - -
Guía de DSi

Lazy DSi Downloader

Únete al servidor DS⁽ⁱ⁾ Mode Hacking! en Discord para obtener soporte y seguir el desarrollo de la guía.

-

"Lazy DSi Downloader" es una herramienta para simplificar el proceso de modificar una Nintendo DSi.

Pasos de verificación

  1. Enciende tu Nintendo DSi.
  2. Inicia la aplicación Cámara Nintendo DSi.

Si en este punto salta un tutorial y al intentar completarlo la aplicación se congela, no puedes usar Memory Pit.

Guía de preparación

  1. Descarga la última versión de Lazy DSi File Downloaderabrir en una ventana nueva para tu sistema operativo
  2. Inicialo siguiendo las instrucciones para tu sistema operativo listadas en la página vinculada
  3. Haz clic en el botón Next
    • No es obligatorio leer el texto introductorio
  4. Si al hacer los pasos de verificación la consola se cuelga, desactiva la opción Memory Pit
  5. Marca las casilla de la opción "Download latest GodMode9i version?"
    • Si quieres, puedes seleccionar cualquiera de las demás opciones para instalar aplicaciones homebrew haciendo clic en el botón Click to add Additional homebrew..., pero esto no es obligatorio
  6. Espera a que todo se descargue, y luego haz clic en Finish
- - - diff --git a/es_ES/restoring-nand.html b/es_ES/restoring-nand.html deleted file mode 100644 index 07cad5a12..000000000 --- a/es_ES/restoring-nand.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Restaurar un respaldo de la NAND | Guía de DSi - - - - -
Guía de DSi

Restaurar un respaldo de la NAND

Únete al servidor DS⁽ⁱ⁾ Mode Hacking! en Discord para obtener soporte y seguir el desarrollo de la guía.

-

DANGER

¡ADVERTENCIA! Esto es peligroso. Incluso siguiendo al pie de la letra estos pasos, existe la poslibilidad de bloquear al completo la consola, ya que la memoria NAND es de muy baja calidad, especialmente si la sobreescribes multiples veces. ¡Esto debería ser usado única y exclusivamente como último recurso!

TIP

No te saltes nada de esta página. Cualquier error incrementa las posbilidades de causar un bloqueo total de tu consola.

Primero te presentaremos algunas alternativas más seguras para solucionar cosas por las que querrías hacer esto.

  • La instalación de títulos DSiWare se puede hacer utilizando hiyaCFW o TWiLight Menu++
  • Puedes recuperar fotos utilizando ninfsabrir en una ventana nueva, en conjuncion con hiyaCFW o TWiLightMenu++ si quieres que estén en la consola. La última version de HiyaCFW Helper te permite copiar las fotos de tu memoria NAND a la SDNAND durante la configuración.
  • Puedes restaurar alguna de las configuraciones de botónes de Unlaunch desde su menú, al que puedes acceder manteniendo pulsado A y B mientras enciendes la consola.
  • ¿Te salta error al iniciar Unlaunch? Saca tu tarjera SD e intenta iniciar el sistema de nuevo. Si funciona, entonces el error es a causa de tu tarjeta SD, y que restaurar la NAND no lo solucionará.
  • El mensaje de error "Ha ocurrido un error..." con el texto blanco sobre negro es probable que sea un error de hiyaCFW y que no esté relacionado a la NAND de tu consola. Echa un vistazo a la página de resolución de problemas de hiyaCFW en la wiki de DS-Homebrewabrir en una ventana nueva para más información.
  • Cualquier error en TWiLight Menu++ no está relacionado con la NAND. Deberías intentar reinstalar TWiLight Menu++ o pedir ayuda en el servidor de Discord.
  • Desinstalar Unlaunch (ya sea sobreescribiendo la NAND o utilizando su desinstalador) debería ser evitado al menos que sea absolutamente necesario. Puedes configurar que el inicio automático ejecute "Launcher" y consola estará como en su estado original.

La única cosa que deberías hacer con tu NAND es instalar Unlaunch. De cualquier otra forma, recomendamos usar las alternativas.

Requisitos

Volcar la BIOS para su uso en no$gba

  1. Extrae dsibiosdumper.nds del archivo dsibiosdumper.zip y colócalo en cualquier lugar de tu tarjeta SD.
  2. Enciende tu consola manteniendo pulsado A y B.
    • Esto debería iniciar el sistema de archivos de Unlaunch.
  3. Ejecuta dsbiosdumper desde el sistema de archivos de Unlaunch.
  4. Pulsa A para volcar la BIOS a la tarjeta SD.
  5. Pulsa START para salir de dsibiosdumper.

Probar tu respaldo de la NAND

Es muy importante asegurarse de que tu respaldo de la NAND funciona antes de intentar restaurarla. Si al probarla en no$gba resulta en un bloqueo total, es muy posible que pase lo mismo en tu consola.

  1. Extrae NO$GBA.EXE del archivo no$gba-w.zip a una carpeta en tu ordenador.
  2. Copia tu respaldo de la NAND a la carpeta en donde extraíste NO$GBA.EXE, y cámbiale el nombre a DSI-1.MMC.
  3. Copia los archivos bios7i.bin y bios9i.bin a la carpeta en donde extraíste NO$GBA.EXE, y nómbralos BIOSDSI7.ROM y BIOSDSI9.ROM, respectivamente.
  4. Executa NO$GBA.EXE.
  5. Haz clic en Options > Emulation Setup para abrir la ventana de configuración de ejecución.
  6. Cambia la opción Reset/Startup Entrypoin a GBA/NDS BIOS (Nintendo logo).
  7. Cambia la opción NDS Mode/Colors a DSi (retail/16MB).
  8. Haz clic en Save Now.
  9. Ejecuta cualquier rom de Nintendo DS (la extensión de archivo debería ser .nds)

Si no$gba carga el menú DSi (o el sistema de archivos de Unlaunch), continúa a la siguiente sección. Si en su lugar salta cualquier clase de error, ¡no debes usar este respaldo!

Desinstalar Unlaunch de tu respaldo de NAND (opcional)

Sigue estos pasos si has volcado tu respaldo de la NAND después de instalar Unlaunch y te gustaría removerlo de tu sistema. Si no estás intentando desinstalar Unlaunch, no debes seguir esta sección.

  1. Descarga la última versión del instalador de Unlaunchabrir en una ventana nueva.
  2. Extrae el archivo UNLAUNCH.DSI del archivo comprimido unlaunch.zip.
  3. Ejecuta UNLAUNCH.DSI como ROM en no$gba e inícialo desde la ranura para cartuchos.
    • Esto debería iniciar el instalador, que se ve parecido al sistema de archivos de Unlaunch.
  4. Elige la opción Uninstall.
  5. Una vez terminado, elige la opción Power Down.
  6. Ejecuta cualquier otra ROM de Nintendo DS para segurarte de que el menú carga y funciona correctamente.

Si no$gba muestra cualquier clase de error en vez de cargar el menú de la consola, ¡no debes usar este respaldo! Si tienes un respaldo antiguo dela NAND, intenta usar ese en su lugar. NO intentes desinstalar Unlaunch usando el instalador en la consola, es muy posible que causes un bloqueo total al hacerlo así.

Sobreescribir utilizando tu respaldo de la NAND (por software)

DANGER

Aquí es donde la cosa se vuelve peligrosa, así que asegúrate de haber leído bien los pasos anteriores. Si llegaste aquí a través de un enlace sin seguir los pasos anteriores, vuelve al principio de la página y leela por completo.

DANGER

Asegúrate de que tu consola está cargada antes de comenzar con esta sección.

  1. Con tu tarjeta SD dentro de tu consola, enciende la misma mientras mantienes pulsados A y B.
  2. Ejecuta SafeNANDManager.
  3. Pulsa el botón indicado para la opción begin NAND restore.
  4. Una vez finalizada la restauracion, pulsa START para apagar tu consola.

La memoria NAND de tu consola debería estar restaurada.

Sobreescribir utilizando tu respaldo de la NAND (por modificación del hardware)

Si tu consola no enciende o no incia el sistema, la única forma de restaurar un respaldo de la NAND es hacer una modificación por hardware. La mejor guía que existe actualmente es la guía de modificación de hardware de Nintendo DSi en la Wiki de DS-Homebrewabrir en una ventana nueva.

- - - diff --git a/es_ES/sd-card-setup.html b/es_ES/sd-card-setup.html deleted file mode 100644 index eee5ed1c0..000000000 --- a/es_ES/sd-card-setup.html +++ /dev/null @@ -1,85 +0,0 @@ - - - - - - - - - Preparacion de la tarjeta SD | Guía de DSi - - - - -
Guía de DSi

Preparacion de la tarjeta SD

Únete al servidor DS⁽ⁱ⁾ Mode Hacking! en Discord para obtener soporte y seguir el desarrollo de la guía.

-

En ésta página te mostraremos cómo preparar tu tarjeta SD para ser usada en tu dispositivo. En el proceso, formatearemos la tarjeta SD y haremos comprobación de errores.

DANGER

Asegúrate de hacer una copia de seguridad del contenido de tu tarjeta SD antes de seguir estos pasos. El contenido de tu tarjeta SD será ELIMINADO en el proceso.

Sección I - Formatear tu tarjeta SD con SD Formatter

TIP

Esta sección formatea la tarjeta SD según las especificaciones de la Asociación de tarjetas SD. Esto puede solucionar muchos problemas que pueden ocurrir con la ejecución de aplicaciones homebrew.

DANGER

Cualquier tarjeta SD de 64GB o mayor será formateada a exFAT en este proceso. Debes seguir la sección II para reformatear a FAT32.

  1. Descarga la última versión de SD Formatterabrir en una ventana nueva
  2. Ejecuta SD Card Formatter Setup (el archivo .exe en el .zip descargado) con privilegios de administrador, e instala el programa
  3. Ejecuta SD Card Formatter desde el Menú de Inicio con privilegios de administrador
  4. Selecciona tu tarjeta SD
  5. Asegúrate de que la casilla de la opción Quick Format esté marcada
  6. Pulsa Formato para iniciar el proceso de formato Captura de pantalla de Formatter de Tarjeta SD en Windows 11

Sección II - Formatear tu tarjeta SD con GUIFormat

Esta sección formatea tarjetas SD de tamaños mayores a 32GB al formato FAT32.

TIP

Si tu tarjeta SD es de 32GB o de una menor capacidad, salta a la sección III.

  1. Descarga la última versión de GUIFormatabrir en una ventana nueva
    • Haz clic en la imagen en el sitio web para descargar la aplicación
  2. Ejecuta GUIFormat con permisos de administrador
  3. Selecciona la letra de tu unidad
  4. Establece la opción Allocation size unit a 32768
    • Si este tamaño de asignación es muy alto para tu tarjeta SD, selecciona el valor más alto que funcione
  5. Asegúrate de que la casilla de la opción Quick Format esté marcada
  6. Inicia el proceso de formato

Sección III - Comprobación de errores

  1. Ve a la ventana Propiedades de tu tarjeta SD
    • Abre el Explorador de Windows, ve a Equipo y haz clic derecho en tu tarjeta SD. Luego, haz clic en Propiedades
  2. En la pestaña de Herramientas, selecciona la opción Comprobar ahora
  3. Marca las casillas Reparar automáticamente errores en el sistema de archivos y Examinar e intentar recuperar sectores defectuosos
  4. Inicia el proceso de verificación

Esto escaneará la tarjeta SD y corregirá cualquier error que el sistema encuentre.

Sección III - Comprobar que se pueden leer y escribir datos de/a la tarjera SD

  1. Descarga y extrae el archivo h2testwabrir en una ventana nueva en cualquier lugar de tu ordenador
    • Si el enlace de arriba no funciona, intenta descargar desde archive.orgabrir en una ventana nueva
    • También se puede extraer en un dispositivo externo mientras ese dispositivo externo no sea tu tarjeta SD
  2. Con tu tarjeta SD insertada en tu ordenador, ejecuta h2testw.exe
  3. Selecciona el lenguaje en el que te gustaría ver la interfaz de h2test2. En esta guía se utilizará la interfaz en inglés
  4. Establece como objetivo la letra de unidad de tu tarjeta SD
  5. Asegúrate de que la opción all available space esté seleccionada
  6. Haz clic en Write + Verify
  • Espera hasta que el proceso se complete

TIP

Si la prueba muestra el resultado Test finished without errors, tu tarjeta SD está en buen estado y puedes eliminar todos los archivos cuya extensión sea .h2w de tu tarjeta SD.

DANGER

Si la prueba muestra otro tipo de resultado, tu tarjeta SD puede estar corrupta o dañada, y tendrás que reemplazarla.

TIP

Si TWiLight Menu++ falla al iniciar después de seguir este método, sigue las instrucciones para Windows en su lugar, ya sea iniciando Windows en otra partición, o utilizando una máquina virtual

Sección I - Formatear tu tarjeta SD

  1. Asegúrate de que tu tarjeta SD no esté insertada en tu máquina Linux.
  2. Ejecuta la terminal de Linux
  3. Escribe watch "lsblk".
  4. Inserta tu tarjeta SD en tu máquina Linux.
  5. Observa el mensaje que aparece en pantalla. Debería coincidir con algo como esto:
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
-mmcblk0     179:0    0   3,8G  0 disk
-└─mmcblk0p1 179:1    0   3,7G  0 part /run/media/user/FFFF-FFFF
-
  1. Toma nota del nombre del dispositivo. En nuestro ejemplo, era mmcblk0p1
    • Si en la fila RO el valor está en 1, asegúrate de que la tarjeta SD tiene el interruptor para la protección de escritura no esté bajado
    • Asegúrese de que está dirigiendo la partición ****, mmcblk0p1 no mmcblk0
  2. Haz la combinación de teclas CTRL + C para salir del menú
  3. Sigue las instrucciones pertinentes a la capacidad de tu tarjeta SD:
    • 2GB o menos: sudo mkdosfs /dev/(nombre del dispositivo) -s 64 -F 16
      • Este comando creará en tu tarjeta SD una única partición con formato FAT16 y asignación de página de 32KB
    • 4GB o más: sudo mkdosfs /dev/(nombre del dispositivo) -s 64 -F 32
      • Este comando creará en tu tarjeta SD una única partición con formato FAT32 y asignación de página de 32KB

Sección II - Usar F3

  1. Descarga y extrae el archivo F3abrir en una ventana nueva en cualquier lugar de tu ordenador.
  2. Lanza la terminal en el directorio de F3
  3. Ejecuta make para compilar F3
  4. Con tu tarjeta SD insertada y montada, ejecuta ./f3write <punto de montura de tu tarjeta SD>
    • Espera hasta que se complete el proceso. A continuación se muestra un ejemplo de mensaje de resultado:
    $ ./f3write /media/michel/6135-3363/
-Free space: 29.71 GB
-Creating file 1.h2w ... OK!
-...
-Creating file 30.h2w ... OK!
-Free space: 0.00 Byte
-Average Writing speed: 4.90 MB/s
-
  5. Ejecuta ./f3read <punto de montura de tu tarjeta SD>
  • Espera hasta que se complete el proceso. A continuación se muestra un ejemplo de mensaje de resultado:
    $ ./f3read /media/michel/6135-3363/
-                  SECTORS      ok/corrupted/changed/overwritten
-Validating file 1.h2w ... 2097152/        0/      0/      0
-...
-Validating file 30.h2w ... 1491904/        0/      0/      0
-
-   Data OK: 29.71 GB (62309312 sectors)
-Data LOST: 0.00 Byte (0 sectors)
-            Corrupted: 0.00 Byte (0 sectors)
-   Slightly changed: 0.00 Byte (0 sectors)
-         Overwritten: 0.00 Byte (0 sectors)
-Average Reading speed: 9.42 MB/s
-

TIP

Si la prueba muestra el resultado Data LOST: 0. 0 Byte (0 sectors) tu tarjeta SD está bien y puedes borrar todos los archivos .h2w de tu tarjeta SD.

DANGER

Si la comprobación muestra otro tipo de resultado, tu tarjeta SD puede estar corrupta o dañada y tendrás que reemplazarla.

Sección I - Formatear tu tarjeta SD con SD Formatter

TIP

Esta sección formatea la tarjeta SD según las especificaciones de la Asociación de tarjetas SD. Esto puede solucionar muchos problemas que pueden ocurrir con la ejecución de aplicaciones homebrew.

DANGER

Cualquier tarjeta SD de 64GB o mayor será formateada a exFAT en este proceso. Debes seguir la sección II para reformatear a FAT32.

  1. Descarga la última versión de SD Formatterabrir en una ventana nueva.
    • Acepta el Acuerdo de Licencia de Usuario Final para iniciar la descarga.
  2. Ejecuta Install SD Card Formatter (el archivo .mpkg en el archivo .zip descargado).
  3. Ejecuta SD Card Formatter.
  4. Elige tu tarjeta SD.
  5. Asegúrate de que la casilla de la opción Quick Format esté marcada.
  6. Inicia el proceso de formato.

Sección II - Formatear tu tarjeta SD con Disk Utility

Esta sección formatea tarjetas SD de tamaños mayores a 32GB al formato FAT32.

TIP

Si tu tarjeta SD es de 32GB o de una menor capacidad, salta a la sección III.

OS X El Capitan (10.11) y posteriores

  1. Lanza la aplicación Disk Utility
  2. Selecciona Mostrar todos los dispositivos en el panel Ver de la esquina superior izquierda.
  3. Selecciona tu tarjeta SD desde la barra lateral.
    • ¡Asegúrate de elegir el dispositivo correcto, de lo contrario podrías borrar accidentalmente la unidad equivocada!
  4. Haz clic en borrar en la parte superior.
  5. Asegúrate de que la opción Formato está establecida en MS-DOS (FAT32).
    • Desde las versiones El Capitan (10.11) hasta Catalina (10.15), elige MS-DOS (FAT).
  6. Asegúrate de que la opción Esquema está establecida a Master Boot Record.
    • Si la opción Esquema no aparece, haz clic en Cancelar y asegúrate de elegir el dispositivo en lugar sólamente un volúmen.
  7. Haz clic en Borrar, y luego en Cerrar.

OS X Yosemite (10.10) y anteriores

  1. Lanza la aplicación Disk Utility
  2. Selecciona tu tarjeta SD desde la barra lateral.
    • ¡Asegúrate de elegir el dispositivo correcto, de lo contrario podrías borrar accidentalmente la unidad equivocada!
  3. Haz clic en Partición en la parte superior.
    • Si la opción Partición aparece, asegúrate de elegir la unidad en lugar de sólo un volumen.
  4. Asegúrate de que la opción Disposición de la Partición está establecida en 1 Partición.
  5. Asegúrate de que la opción Formato está establecida en MS-DOS (FAT).
  6. En el botón Opciones (debajo de la tabla de particiones), selecciona Master Boot Record.
  7. Haz clic en Aceptar, luego en Aplicar y después en Particionar.

Sección III - Usar F3

  1. Abre Terminal
  2. Instala F3 desde brew ejecutando brew install f3.
  3. Con tu tarjeta SD insertada y montada, ejecuta ./f3write <el punto de montaje de tu tarjeta sd>.
    • Espera hasta que se complete el proceso. A continuación se muestra un ejemplo de mensaje de resultado:
    $ f3write /Volumes/SD\ CARD
-Free space: 29.71 GB
-Creating file 1.h2w ... OK!
-...
-Creating file 30.h2w ... OK!
-Free space: 0.00 Byte
-Average Writing speed: 4.90 MB/s
-
  4. Ejecuta ./f3read <el punto de montaje de tu tarjeta sd>
    • Espera hasta que se complete el proceso. A continuación se muestra un ejemplo de mensaje de resultado:
    $ f3read /Volumes/SD\ CARD
-                  SECTORS      ok/corrupted/changed/overwritten
-Validating file 1.h2w ... 2097152/        0/      0/      0
-...
-Validating file 30.h2w ... 1491904/        0/      0/      0
-
-   Data OK: 29.71 GB (62309312 sectors)
-Data LOST: 0.00 Byte (0 sectors)
-            Corrupted: 0.00 Byte (0 sectors)
-   Slightly changed: 0.00 Byte (0 sectors)
-         Overwritten: 0.00 Byte (0 sectors)
-Average Reading speed: 9.42 MB/s
-

TIP

Si la prueba muestra el resultado Data LOST: 0. 0 Byte (0 sectors) tu tarjeta SD está bien y puedes borrar todos los archivos .h2w de tu tarjeta SD.

DANGER

Si la comprobación muestra otro tipo de resultado, tu tarjeta SD puede estar corrupta o dañada y tendrás que reemplazarla.

TIP

Ahora puedes restaurar el contenido de tu tarjeta SD y continuar.

- - - diff --git a/es_ES/site-navigation.html b/es_ES/site-navigation.html deleted file mode 100644 index 7c372c8c7..000000000 --- a/es_ES/site-navigation.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Navegación del sitio | Guía de DSi - - - - -
Guía de DSi

Navegación del sitio

Únete al servidor DS⁽ⁱ⁾ Mode Hacking! en Discord para obtener soporte y seguir el desarrollo de la guía.

-

- - - diff --git a/es_ES/troubleshooting.html b/es_ES/troubleshooting.html deleted file mode 100644 index 84f98ad2c..000000000 --- a/es_ES/troubleshooting.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Solucion de problemas | Guía de DSi - - - - -
Guía de DSi

Solucion de problemas

Únete al servidor DS⁽ⁱ⁾ Mode Hacking! en Discord para obtener soporte y seguir el desarrollo de la guía.

-

Unlaunch

Unlaunch se congela y muestra el mensaje MISMATCH IN FAT COPIES

twlnf tiene un error critico en el que no actualiza correctamente toda la NAND después de modificarla, lo que hace que ciertos homebrew (como el instalador de Unlaunch) tire error.

Para solucionar esto, abre NAND Title Manager (NTM)abrir en una ventana nueva, y selecciona la opción Fix FAT copy mismatch.

No hay audio o pantalla de inicio al ejectar Launcher (el menú original de DSi) usando Unlaunch

El desarrollador de Unlaunch (nocash) parcheó intencionalmente el sonido del menú y la pantalla de inicio por defecto. Puedes restaurar estas características reinstalando Unlaunch usando TWiLight Menu++ cambiando la opción "Parches del Launcher" a "Por Defecto" en la página de Ajustes de Unlaunch en los Ajustes de TWiLight Menu++, o usando hiyaCFWabrir en una ventana nueva.

Encender la consola solo muestra una pantalla en negro después de instalar Unlaunch

Intenta extraer la tarjeta SD y encender la consola nuevamente. Si el problema persiste, es posible que tengas que restaurar tu respaldo de la NAND modificando el hardware de la consolaabrir en una ventana nueva.

Se inicia una aplicación o salta el sistema de archivos de Unlaunch al encender la consola, estoy atascado

La causa más probable es haber una aplicación incorrecta para la opción NO BUTTON en Unlaunch. Mantén presionados A y B mientras enciendes la consola, ve a OPTIONS y establece NO BUTTON a la aplicación que quieras ejecutar al inicio.

Otros problemas de Unlaunch

Si Unlaunch muestra el mensaje Clusters too large, Bad VBR, Bad MBR o no muestra niguna aplicación mientras la tarjeta SD está insertada, es probable que tu tarjeta SD no fuese formateada correctamente. Vuelve a seguir los pasos de preparación de la tarjeta SD.

TWiLight Menu++

Para solución de problemas generales de TWiLight Menu++, revisa su página de Preguntas Frecuentes y Resolución de problemasabrir en una ventana nueva en la Wiki de DS-Homebrew.

Más asistencia

Si has encontrado un problema que no se resuelve con ninguna de las indicaciones anteriores, o que persiste a pesar de seguir las mismas, pide asistencia en el servidor de discord DS(i) Mode Hacking!abrir en una ventana nueva

- - - diff --git a/es_ES/uninstalling-unlaunch.html b/es_ES/uninstalling-unlaunch.html deleted file mode 100644 index 6cf3b12b4..000000000 --- a/es_ES/uninstalling-unlaunch.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Desinstalar Unlaunch | Guía de DSi - - - - -
Guía de DSi

Desinstalar Unlaunch

Únete al servidor DS⁽ⁱ⁾ Mode Hacking! en Discord para obtener soporte y seguir el desarrollo de la guía.

-

DANGER

¡Instalar o desinstalar Unlaunch puede bloquear totalmente tu consola de manera aleatoria! ¡Fuiste advertido!

ADVERTENCIA: Desinstalar Unlaunch puede bloquear totalmente tu consola. Aquí hay algunos casos por los que podrías querer desinstalar Unlaunch, junto con soluciones que no lo requerirían.

  • El fondo de Unlaunch da miedo: Reinstala Unlaunch siguiendo las nuevas instrucciones. Ahora hay instrucciones para cambiar el fondo
  • Tengo problemas con Unlaunch o con mi consola después de instalarlo: La página de solución de problemas puede tener la solución a muchos de los problemas que podrías estar experimentando.

WARNING

Para reducir la posibilidad de bloqueo total, asegúrate de que no has instalado títulos DSiWare de forma no legítima a tu respaldo de la NAND (la redirección a títulos desde la SDNAND de hiyaCFW no cuenta), o que no has tocado y movido de alguna otra forma los archivos del sistema.

WARNING

Al desinstalar la desinstalación, NO debes usar su desinstalador integrado directamente en tu consola ya que existe la posibilidad de que brickee la consola. Echa un vistazo a la información de más abajo para desinstalar Unlaunch de la manera correcta.

Una vez que hayas revisado la información anterior, sigue las instrucciones de Volcar la NAND para hacer un nuevo muelle de la NAND, luego proceda a Restaurar una copia de seguridad de la NAND. Esto te guiará a través de la desinstalación de la desinstalación de la copia de seguridad de la NAND y flashear a tu consola.

Si no puedes usar ningún$gba o obtener un error después de desinstalar Unlaunch en ningún$gba también es posible flashear una copia de seguridad de la NAND hecha antes de instalar Unlaunch si todavía tienes una, Sin embargo, se recomienda intentar usar una copia de seguridad de la NAND que previamente tenía Unlaunch primero. Esto facilitará significativamente la recuperación en el caso de que un bloque requiera un hardmod ya que Unlaunch deja el pie de página no$gba incrustado en la NAND incluso cuando se desinstala.

- - - diff --git a/faq.html b/faq.html index 1dbb46e9e..70b88c186 100644 --- a/faq.html +++ b/faq.html @@ -3,7 +3,7 @@ - + - - Page non trouvée | Guide DSi - - - - -
- - - diff --git a/fr_FR/alternate-exploits.html b/fr_FR/alternate-exploits.html deleted file mode 100644 index b8bc08a34..000000000 --- a/fr_FR/alternate-exploits.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Exploits alternatifs | Guide DSi - - - - -
Guide DSi

Exploits alternatifs

Rejoignez le serveur Discord DS⁽ⁱ⁾ Mode Hacking! pour le développement du guide et l'aide.

-

Si un tutoriel vous est présenté lors du lancement de l'application de l'appareil photo Nintendo DSi et que vous obtenez un plantage en essayant de le terminer, vous ne pouvez pas utiliser Memory Pit. Vous trouverez ici des exploits alternatifs qui peuvent remplacer Memory Pit.

Si vous avez installé Flipnote Studio, vous pouvez utiliser Flipnote Lenny.

TIP

Assurez-vous d'avoir configuré TWiLight Menu++ sur votre carte SD avant de procéder à l'une des opérations suivantes.

Si vous utilisez un ancien firmware, vous pouvez avoir accès à des exploits de sauvegarde pour une liste de jeuxouvrir dans une nouvelle fenêtre sélectionnés. Nous ne les aborderons pas ici, car ils sont largement obsolètes. Ils ne doivent être utilisés qu'en dernier recours, si Memory Pit et Flipnote Lenny ne vous conviennent pas.

petit-compwner ne sera pas utilisable pour contourner Memory Pit, car il nécessite un appareil photo fonctionnel pour lancer l'exploit.

- - - diff --git a/fr_FR/credits.html b/fr_FR/credits.html deleted file mode 100644 index 7dd5952b6..000000000 --- a/fr_FR/credits.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Crédits | Guide DSi - - - - -
Guide DSi

Crédits

Rejoignez le serveur Discord DS⁽ⁱ⁾ Mode Hacking! pour le développement du guide et l'aide.

-

Il s'agit des crédits pour ceux qui ont aidé à faire le site Web du guide, les homebrews, et d'autres choses.

Si vous aimez ce qu'ils ont fait, pensez à faire un don (s'ils ont un lien de don).

Vous pouvez également contribuer à notre guide en envoyant simplement une demande de tirageouvrir dans une nouvelle fenêtre !

Si vous connaissez d'autres langues, vous pouvez nous aider en traduisant le guide dans celles-ci. Vous pouvez rejoindre notre projet Crowdinouvrir dans une nouvelle fenêtre pour commencer.

- - - diff --git a/fr_FR/dsiware-backups.html b/fr_FR/dsiware-backups.html deleted file mode 100644 index 679bb6536..000000000 --- a/fr_FR/dsiware-backups.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Sauvegardes des DSiWare | Guide DSi - - - - -
Guide DSi

Sauvegardes des DSiWare

Rejoignez le serveur Discord DS⁽ⁱ⁾ Mode Hacking! pour le développement du guide et l'aide.

-

Prérequis

Nintendo DSi - Instructions

Section I - Dumping des DSiWare

  1. Lancez GodMode9i
  2. Appuyez sur START pour ouvrir le menu START
  3. Sélectionnez Gestionnaire de titres…
    • Si ce n'est pas affiché, assurez-vous que votre carte SD et votre NAND sont montées. Si vous chargez à partir de hiyaCFW, rechargez à partir d'un autre endroit
  4. Sélectionnez le titre que vous voulez dumper
  5. Sélectionnez ce que vous voulez dumper
  6. Répétez les étapes 4 et 5 pour tous les DSiWare que vous souhaitez dumper

TIP

Les DSiWare dumpés se trouveront dans sd:/gm9i/out.

- - - diff --git a/fr_FR/dumping-game-cards.html b/fr_FR/dumping-game-cards.html deleted file mode 100644 index b27df6e72..000000000 --- a/fr_FR/dumping-game-cards.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Dumping des cartes de jeu | Guide DSi - - - - -
Guide DSi

Dumping des cartes de jeu

Rejoignez le serveur Discord DS⁽ⁱ⁾ Mode Hacking! pour le développement du guide et l'aide.

-

Cette section est dédiée au dumping des cartes de jeu avec GodMode9i, afin que les jeux puissent être joués sur des émulateurs, des linkers ou votre carte SD via nds-bootstrap.

Prérequis

  • La carte de jeu du titre que vous souhaitez dumper
  • Votre Nintendo DSi avec Unlaunch installé

Instructions

Section I - Configuration de la carte SD

  1. Téléchargez la dernière version de GodMode9iouvrir dans une nouvelle fenêtre
  2. Extrayez GodMode9i.nds de l'archive GodMode9i et placez-le n'importe où sur votre carte SD

Section II - Instructions Nintendo DSi

  1. Lancez GodMode9i
  2. Assurez-vous que la carte de jeu est insérée dans la console
  3. Sélectionnez l'option CARTE DS dans GodMode9i
  4. Sélectionnez ce que vous voulez dumper
    • Les options trimmée pour la ROM vont dumper un fichier plus petit qui peut économiser de l'espace sur la carte SD, mais elles ne fonctionneront pas pour la plupart des patchs tels que les ROMs hacks
  5. Répétez les étapes 2 à 4 pour toutes les cartes de jeu que vous souhaitez dumper

TIP

Les cartes de jeu dumpées se trouvent dans sd:/gm9i/out.

- - - diff --git a/fr_FR/dumping-nand.html b/fr_FR/dumping-nand.html deleted file mode 100644 index 94ea90096..000000000 --- a/fr_FR/dumping-nand.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Dumping de la NAND | Guide DSi - - - - -
Guide DSi

Dumping de la NAND

Rejoignez le serveur Discord DS⁽ⁱ⁾ Mode Hacking! pour le développement du guide et l'aide.

-

Cette page permet de sauvegarder de la NAND, qui est une copie des données sur le stockage interne de la Nintendo DSi. Elle peut être utilisée pour configurer hiyaCFW, ainsi que no$gba et melonDS pour l'émulation DSi.

TIP

Assurez-vous que la carte SD dispose d'au moins 250 Mo d'espace libre, sinon vous rencontrerez un message d'erreur dans dumpTool.

TIP

Il est fortement recommandé de le faire. Une sauvegarde de la NAND peut être utilisée comme point de restauration dans le futur, en cas de brick de la console.

Section I - Configuration de la carte SD

TIP

Si vous avez déjà téléchargé dumpTool dans une autre section de ce guide, vous pouvez sauter cette section.

  1. Téléchargez la dernière version de dumpToolouvrir dans une nouvelle fenêtre
  2. Placez dumpTool.nds n'importe où sur votre carte SD

Section II - Dumping de la NAND

  1. Lancez dumpTool via TWiLight Menu++
  2. Appuyez sur le bouton A de votre Nintendo DSi pour commencer à dumper votre NAND
    • Une sauvegarde de la NAND prend, généralement, 7 minutes environ
  3. Lorsque la sauvegarde de la NAND est terminée, pressez le bouton START de votre Nintendo DSi pour quitter dumpTool
  4. Éteignez votre console et réinsérez votre carte SD dans votre périphérique
  5. Stockez cette sauvegarde dans un endroit sûr, là où vous ne la perdrez pas
    • Si possible, faites plusieurs sauvegardes sur différents périphériques de stockage
    • Une fois que vous l'avez sauvegardée ailleurs, vous pouvez la supprimer de la carte SD

WARNING

Le hachage SHA1 de nand.bin ne correspondra pas à celui stocké dans nand.bin.sha1. Ceci est dû au fait que dumpTool ajoute des données supplémentaires, connues comme un pied de page no$gba, au fichier nand.bin après le calcul du hachage SHA1. Vous pouvez utiliser hiyaCFW Helperouvrir dans une nouvelle fenêtre pour créer une copie sans le pied de page.

TIP

Continuer vers Installation d'Unlaunch (optionnel)

- - - diff --git a/fr_FR/faq.html b/fr_FR/faq.html deleted file mode 100644 index b0078c589..000000000 --- a/fr_FR/faq.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - FAQ | Guide DSi - - - - -
Guide DSi

FAQ

Rejoignez le serveur Discord DS⁽ⁱ⁾ Mode Hacking! pour le développement du guide et l'aide.

-

Dois-je faire une mise à jour du système ?

Il n'est pas recommandé de mettre à jour votre DSi à moins que vous ne sachiez qu'il y a des DSiWare achetés. Il est toujours possible de suivre ce guide si vous le faites, mais le seul avantage de la mise à jour est la possibilité d'accéder à la boutique Nintendo DSi pour retélécharger des titres déjà achetés. Tous les autres avantages, comme l'intégration de Facebook dans l'application Appareil photo Nintendo DSi, ne sont plus utilisables ou ne sont pas suffisamment importants pour justifier les inconvénients :

  • L'installation des mises à jour du système est connue pour occasionnellement bricker des consoles, avec à peu près la même fréquence que lors de l'installation d'Unlaunch
  • Il n'est plus possible d'utiliser des exploits plus anciens, ce qui peut être nécessaire si vous ne pouvez pas utiliser les exploits recommandés
  • La compatibilité des linkers est réduite, mais cela peut être contourné si vous installez Unlaunch

Quel est le meilleur exploit ?

Unlaunch est globalement le meilleur exploit pour la DSi, le seul inconvénient étant qu'il y a un risque mineur de brick à l'installation. En général, il est recommandé d'utiliser Memory Pit pour installer Unlaunch. Si vous voulez éviter tout risque, il est recommandé d'utiliser plutôt Flipnote Lenny car il a moins de problèmes que Memory Pit avec les homebrews, tout en étant tout aussi sûr et simple à supprimer. Vous trouverez ci-dessous une liste des avantages et des inconvénients de chaque exploit :

Memory Pit

Avantages :

  • Rapide et simple d'utilisation
  • Aucun risque d'endommager la console, la désinstallation est aussi simple que de retirer la carte SD ou de supprimer un fichier
  • Compatible avec toutes les consoles DSi, à moins qu'elles n'aient un appareil photo cassé et qu'elles n'aient pas terminé le tutoriel sur l'appareil photo

Inconvénients :

  • Nécessite le lancement de l'appareil photo DSi chaque fois que vous voulez accéder à un homebrew
  • Incompatible avec certains titres en mode DSi et homebrews car la WRAM n'est ouverte qu'au processeur ARM7
  • L'accès au Slot-1 (la carte de jeu DS) est bloqué dans les homebrews
  • L'accès au DSP est bloqué, ce qui entraîne une dégradation du son dans GBARunner2
  • Les photos sur la carte SD ne peuvent pas être visualisées dans l'appareil photo DSi lorsque Memory Pit est installé, car c'est le déclencheur de l'exploit
    • La seule façon de visualiser les photos de la carte SD alors que Memory Pit est installé, est de lancer un dump de la ROM de l'application Appareil photo Nintendo DSi en utilisant TWiLight Menu++ pour le lancer via nds-bootstrap (v0.61.3 ou plus)

stylehax

Avantages :

  • Meilleure compatibilité avec les titres en mode DSi et homebrews que Memory Pit
  • Facile à utiliser
  • Aucun risque d'endommager la console
  • Utilisable sur les consoles avec un appareil photo cassé
  • Meilleur son dans GBARunner2

Inconvénients :

  • Nécessite un accès à Internet
  • Nécessite de charger le Nintendo DSi Browser chaque fois que vous voulez accéder à un homebrew, ce qui prend un peu plus de temps que Memory Pit
  • L'accès au Slot-1 (la carte de jeu DS) est bloqué dans les homebrews

Flipnote Lenny

Avantages :

  • Meilleure compatibilité avec les titres en mode DSi et homebrews que Memory Pit
  • Aucun risque d'endommager la console, la désinstallation est aussi simple que de retirer la carte SD ou de supprimer un dossier
  • Utilisable sur les consoles avec un appareil photo cassé
  • Meilleur son dans GBARunner2

Inconvénients :

  • Nécessite le chargement de Flipnote Studio chaque fois que vous voulez accéder à un homebrew, ce qui prend un peu plus de temps que Memory Pit
  • L'accès au Slot-1 (la carte de jeu DS) est bloqué dans les homebrews

Unlaunch

Avantages :

  • Permet de lancer les homebrews et DSiWare immédiatement au démarrage du système, avec des boutons de raccourci facultatifs
  • Accès complet au système sans aucune restriction, y compris :
    • Accès au Slot-1 permettant de dumper les cartes de jeu et de charger des linkers incompatibles
    • Meilleur son dans GBARunner2
  • Supprime les verrouillages régionaux sur les cartes de jeu optimisées/exclusives DSi
  • Protection contre la plupart des risques de brick de la DSi
  • Les jeux optimisés DSi peuvent être exécutés en mode DSi sans ROM donatrice
  • Les anciens homebrews peuvent être exécutés via nds-bootstrap-hb

Inconvénients :

  • Risque très mineur de bricker la console lors de l'installation
  • Autre risque, légèrement plus élevé, de brick si vous décidez de le désinstaller
  • Non compatible avec les consoles de développement

Est-ce que je perdrai des fonctionnalités en moddant mon système ?

Si vous installez Unlaunch ou utilisez Flipnote Lenny, vous ne perdrez aucune fonctionnalité. Si vous utilisez Memory Pit, vous ne pourrez pas visualiser les photos sur la carte SD à l'aide de l'application Appareil photo Nintendo DSi, à moins de lancer un dump de cette ROM en utilisant TWiLight Menu++ pour le charger via nds-bootstrap.

  • Pour retrouver la possibilité de visualiser les photos de votre carte SD lors du lancement de l'appareil photo DSi à partir du menu DSi, installez Unlaunch ou passez à un autre exploit, puis supprimez le fichier pit.bin de Memory Pit
    • Si tip.bin existe dans le même dossier, renommez-le en pit.bin

Comment puis-je jouer aux dumps de cartes de jeu Nintendo DS ?

La lecture des dumps de cartes de jeu sur la console nécessite l'utilisation d'un linker ou de nds-bootstrap, un programme qui permet de jouer à partir de la carte SD interne en redirigeant les lectures et les écritures du Slot-1 vers celle-ci.

  • Avec TWiLight Menu++, vous pouvez naviguer sur votre carte SD pour trouver des fichiers ROMs à jouer avec nds-bootstrap. L'avantage d'utiliser TWiLight Menu++ est d'avoir un menu de triche, des paramètres par jeu et d'éviter les restrictions apportées par les forwarders. En d'autres termes, vous pouvez déposer vos fichiers ROMs directement et les lire sans aucune configuration. Il n'y a pas de limite de 39 titres, ni hiyaCFW ou Unlaunch ne sont nécessaires et il n'y a aucune restriction sur l'espace libre de la carte SD que vous pouvez avoir
  • Les utilisateurs de hiyaCFW peuvent créer des forwarders pour le menu DSi de la SDNAND en utilisant le guide des forwarders de jeux DSouvrir dans une nouvelle fenêtre sur le wiki DS-Homebrew, mais il présente certaines limites. Il y a une limite stricte de 39 titres, et ils sont moins pratiques à réaliser qu'en utilisant TWiLight Menu++

Comment puis-je mettre à jour mes homebrews ?

  • Unlaunch - Suivez les instructions de la page Installation d'Unlaunch
    • Vous n'avez pas besoin de désinstaller Unlaunch avant de faire cela
  • hiyaCFW - Remplacez hiya.dsi à la racine de la carte SD par la version mise à jourouvrir dans une nouvelle fenêtre
  • TWiLight Menu++ - Suivez les instructions sur le wiki DS-Homebrewouvrir dans une nouvelle fenêtre
  • nds-bootstrap - Copiez nds-bootstrap-hb-release.nds et nds-bootstrap-release.nds dans le dossier _nds à la racine de votre carte SD
    • Si vous utilisez TWiLight Menu++, il y a beaucoup de chance que la dernière version de nds-bootstrap soit incluse avec celui-ci
  • GodMode9i, dumpTool, Forwarder3-DS, etc - Suivez les instructions utilisées pour les télécharger

D'autres homebrews peuvent utiliser d'autres méthodes de mise à jour.

Je suis nouveau ou je voudrais refaire mon installation. Par où dois-je commencer ?

  • Si vous n'avez pas encore modifié votre console ou si vous cherchez à mettre à jour Unlaunch sur votre système, nous vous recommandons de commencer par le début du guide et de suivre les pages. Assurez-vous de lire tout ce qui figure sur la page d'accueil
  • Si vous disposez de la dernière version d'Unlaunch, suivez le guide d'installation de TWiLight Menu++ouvrir dans une nouvelle fenêtre pour configurer TWiLight Menu++ sur votre système

Comment puis-je supprimer le contrôle parental ?

Puis-je changer la région de ma Nintendo DSi ?

Oui, il existe plusieurs méthodes différentes selon ce que vous voulez changer :

Qu'est-il arrivé au guide d'installation de hiyaCFW ?

Parce que hiyaCFW n'a pas beaucoup d'utilité fonctionnelle et constituait une partie problématique et confuse du guide pour de nombreux utilisateurs, elle a été déplacée vers le wiki DS-Homebrewouvrir dans une nouvelle fenêtre.

  • Si le lien vers la page en question provient d'un autre guide, les instructions que vous suiviez étaient très probablement périmées. Veuillez plutôt utiliser ce guide, car il est maintenu en permanence par les développeurs de ces projets

Quel type de carte SD dois-je utiliser ?

  • Vous devez acheter une carte SD d'une marque de confiance
  • Une carte SD de taille normale ou une carte microSD avec un adaptateur fonctionneront toutes les deux
  • Toute capacité comprise entre 1 Go et 2 To fonctionnera. Pour un usage général, 8 Go suffisent
    • Certains logiciels, comme hiyaCFW, peuvent avoir des temps de chargement plus longs avec des cartes SD de plus grande capacité
  • La classe de vitesse 8 ou plus est recommandée

Puis-je utiliser ma carte SD DSi sur d'autres systèmes ?

En général, oui, à deux exceptions près :

  • hiyaCFW ne fonctionnera que sur le système pour lequel il a été configuré
  • Même si vous utilisez nds-bootstrap ou un linker, les codes amis dans les jeux DS en ligne seront réinitialisés si vous tentez de vous connecter en utilisant une autre console

Comment passer à une nouvelle carte SD après avoir configuré un homebrew ?

Formatez votre nouvelle carte SD en suivant les instructions de la page Configuration de la carte SD, puis déplacez simplement vos données de l'ancienne carte SD vers la nouvelle.

Puis-je toujours utiliser mon système normalement sans la carte SD insérée après avoir configuré un homebrew ?

Oui. Si vous n'avez pas installé Unlaunch, votre système ne sera pas du tout modifié. Si vous avez installé Unlaunch, vous devrez peut-être configurer Unlaunch pour démarrer automatiquement le menu DSi original dans des conditions spécifiques.

La page d'Unlaunchouvrir dans une nouvelle fenêtre dit que la version 2.0 n'est pas connue pour être sûre. Dois-je utiliser une version antérieure à la place ?

La page d'Unlaunch n'a pas été mise à jour depuis la sortie de la version 2.0, il y a plus de deux ans. La grande majorité des utilisateurs ne rencontrent aucun problème avec cette version, qui est donc considérée comme sûre.

Comment puis-je exécuter un DSiWare dumpé ?

La méthode recommandée est de simplement les lancer avec TWiLight Menu++, en raison de la méthode simple de glisser-déposer et du fait qu'il n'y a pas de limite arbitraire. Lorsque nds-bootstrap est défini comme méthode de lancement, il bénéficie également des avantages des triches et des captures d'écran, ainsi que de tout autre avantage fourni par le menu du jeu.

Cependant, pour les quelques titres qui sont incompatibles, vous pouvez utiliser NTMouvrir dans une nouvelle fenêtre pour les installer soit sur la mémoire interne, soit sur la SDNAND de hiyaCFWouvrir dans une nouvelle fenêtre. En plus de l'absence des avantages ci-dessus, il y a également une limite de 39 titres dont la taille ne peut pas dépasser 128 Mio/1 024 blocs. Pour SysNAND, il y a également un très faible risque de bricker le système lors de l'écriture sur la NAND interne.

- - - diff --git a/fr_FR/file-extensions-windows.html b/fr_FR/file-extensions-windows.html deleted file mode 100644 index 89d149455..000000000 --- a/fr_FR/file-extensions-windows.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Extensions de fichiers (Windows) | Guide DSi - - - - -
Guide DSi

Extensions de fichiers (Windows)

Rejoignez le serveur Discord DS⁽ⁱ⁾ Mode Hacking! pour le développement du guide et l'aide.

-

Il s'agit d'une section complémentaire permettant de désactiver le comportement par défaut de Windows qui consiste à masquer les extensions de fichiers, ce qui vous permettra de trouver beaucoup plus facilement les fichiers référencés dans le guide.

  1. Lancez l'Explorateur de fichiers en ouvrant n'importe quel répertoire, comme celui de votre carte SD
  2. Cliquez sur l'option « Afficher » dans la barre supérieure
    • Si l'option n'est pas présente, cliquez sur le bouton ··· dans la partie la plus à droite de la barre supérieure
  3. Cliquez ou déplacez votre curseur sur le sous-menu Afficher >
  4. Cochez l'option intitulée Extensions de noms de fichier Capture d'écran du survol de la case à cocher « Extensions de noms de fichier » sur Windows 11
  1. Lancez l'Explorateur de fichiers en ouvrant n'importe quel répertoire, comme celui de votre carte SD
  2. Cliquez sur l'option « Affichage » dans le menu du ruban
  3. Cochez la case « Extensions de noms de fichier » Capture d'écran du survol de la case à cocher « Extensions de noms de fichier » sur Windows 10
  1. Ouvrez le menu Démarrer en cliquant dessus ou en utilisant la touche Windows
  2. Recherchez « Options des dossiers » et sélectionnez le résultat correspondant Capture d'écran d'une recherche de « options des dossiers » dans le menu Démarrer de Windows 7
  3. Cliquez sur l'option « Affichage » en haut du menu Options des dossiers
  4. Assurez-vous que la case « Masquer les extensions des fichiers dont le type est connu » n'est pas cochée Capture d'écran de la fenêtre « Options des dossiers » sur Windows 7 avec « Masquer les extensions des fichiers dont le type est connu » désactivé
- - - diff --git a/fr_FR/get-started.html b/fr_FR/get-started.html deleted file mode 100644 index 2a0bb13f2..000000000 --- a/fr_FR/get-started.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Pour commencer | Guide DSi - - - - -
Guide DSi

Pour commencer

Rejoignez le serveur Discord DS⁽ⁱ⁾ Mode Hacking! pour le développement du guide et l'aide.

-

La principale application homebrew que ce guide vous demande d'installer est TWiLight Menu++, qui est une mise à niveau/un remplacement du menu Nintendo DSi permettant d'exécuter d'autres applications homebrews, des jeux DS commerciaux, des émulateurs pour diverses anciennes consoles, etc.

Nous commencerons par le télécharger ainsi que d'autres outils homebrew, en préparation des étapes de l'exploit.

Prérequis

Section I - Travail préparatoire

WARNING

Assurez-vous que votre carte SD est correctement formatée.

  1. Insérez votre carte SD dans votre PC
  2. Téléchargez la dernière version de TWiLight Menu++ouvrir dans une nouvelle fenêtre
  3. Téléchargez la dernière version de dumpToolouvrir dans une nouvelle fenêtre
  4. Copiez le dossier _nds de TWiLightMenu-DSi.7z à la racine de votre carte SD
  5. Copiez le fichier BOOT.NDS de TWiLightMenu-DSi.7z à la racine de votre carte SD
  6. Copiez le fichier dumpTool.nds à la racine de votre carte SD

TIP

Vous ne savez pas ce qu'est la « racine » de la carte SD ? Consultez cette imageouvrir dans une nouvelle fenêtre

Section II - Sélection d'un exploit

À partir de là, trois options s'offrent à vous, avec une différence mineure dans ce que chacune implique.

Installation d'Unlaunch via Memory Pit

Memory Pit est un exploit utilisant l'appareil photo DSi, compatible avec toutes les versions du firmware. Facultativement, cet exploit peut être utilisé pour installer Unlaunch, un exploit bootcode qui permet le contrôle total de la console au démarrage.

Comme Memory Pit est quelque peu limité dans sa compatibilité avec les homebrews, il est recommandé d'installer Unlaunch, au lieu d'utiliser Memory Pit de manière autonome. Comme c'est la méthode la plus facile pour installer Unlaunch, c'est le chemin recommandé. Cependant, il existe un risque très mineur de brick de votre console lors de l'installation d'Unlaunch, donc si cela vous préoccupe, consultez la méthode alternative ci-dessous.

TIP

Continuez vers Lancement de l'exploit

stylehax

stylehax est un exploit utilisant l'application Nintendo DSi Browser, et peut être utilisé comme une alternative à Memory Pit pour installer Unlaunch (expliqué ci-dessus) si votre DSi a un appareil photo cassé.

Pour une expérience sans Unlaunch, cet exploit est recommandé car l'utilisation de Memory Pit cause des problèmes dans certains jeux et homebrews.

TIP

Continuez vers Lancement de l'exploit (stylehax)

Flipnote Lenny

Flipnote Lenny est un exploit utilisant l'application Flipnote Studio.

Si vous possédez Flipnote Studio et que vous ne prévoyez pas d'installer Unlaunch (expliqué ci-dessus), cet exploit est recommandé car l'utilisation de Memory Pit cause des problèmes dans certains jeux et homebrews.

Vous pouvez toujours installer Unlaunch plus tard si vous décidez plus tard que vous le voulez.

TIP

Continuez vers Lancement de l'exploit (Flipnote Lenny)

Pour une comparaison plus détaillée des avantages et inconvénients des exploits disponibles, veuillez consulter sur la section Quel est le meilleur exploit ? de la FAQ.

- - - diff --git a/fr_FR/index.html b/fr_FR/index.html deleted file mode 100644 index efca65cf6..000000000 --- a/fr_FR/index.html +++ /dev/null @@ -1,43 +0,0 @@ - - - - - - - - - Accueil | Guide DSi - - - - -
Guide DSi

Guide DSi

Le guide complet pour modder votre Nintendo DSi.

TIP

Pour des guides complets sur les homebrew et les firmwares personnalisés pour d'autres appareils, consultez CFW.Guideouvrir dans une nouvelle fenêtre.

TIP

Lisez attentivement toutes les pages d'introduction (y compris celle-ci !) avant de poursuivre.

Qu'est-ce qu'un homebrew ?

Les applications homebrewsouvrir dans une nouvelle fenêtre sont des logiciels sans licence conçus pour des systèmes fermés tels que la Nintendo DSi. Ces applications peuvent aller d'utilitaires à des jeux homebrews personnalisés.

Les homebrews peuvent être exécutés gratuitement sur toutes les consoles Nintendo DSi, quelle que soit la version du firmware ou la région. Tout ce dont vous avez besoin est d'un point d'entrée et d'une carte SD pour stocker votre homebrew. Le point d'entrée principal utilisé dans ce tutoriel est Memory Pit, mais il y en a d'autres que vous pouvez utiliser si Memory Pit est inutilisable.

Que puis-je faire en moddant mon système ?

  • Exécutez des sauvegardes de jeux Nintendo DS(i) ou des ROMs hacks à partir de votre carte SD DSi sans avoir besoin d'un linker
  • Lancez n'importe quel DSiWare à partir de votre carte SD
    • Cela signifie que les DSiWare hors région et exclusifs 3DS fonctionneront également
  • Démarrez les applications DSiWare et homebrews en maintenant enfoncés certains boutons lorsque vous allumez votre Nintendo DSi
  • Exécutez de vieux classiques en utilisant divers émulateurs
  • Utilisez des linkers normalement incompatibles
  • Redirigez votre NAND vers la carte SD en utilisant hiyaCFW
  • Regardez vos films préférés à l'aide de FastVideoDSPlayer ou de tuna-viDS
    • FastVideoDSEncoder nécessite un processeur supportant AVX2 (les processeurs plus récents le supporteront probablement)
  • Affichez une image (en tant qu'écran d'accueil) au lancement du système
  • Jouez à des jeux homebrews

Où puis-je trouver des applications homebrews ?

Que dois-je savoir avant de commencer ?

  • Sous Windows, il est recommandé d'afficher les extensions de fichiers si vous utilisez l'Explorateur de fichiers par défaut
  • Le seul risque de brick vient de l'installation d'Unlaunch, et le risque de brick est minime

TIP

Continuez vers Pour commencer

- - - diff --git a/fr_FR/installing-unlaunch.html b/fr_FR/installing-unlaunch.html deleted file mode 100644 index 2b8b21a66..000000000 --- a/fr_FR/installing-unlaunch.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Installation d'Unlaunch | Guide DSi - - - - -
Guide DSi

Installation d'Unlaunch

Rejoignez le serveur Discord DS⁽ⁱ⁾ Mode Hacking! pour le développement du guide et l'aide.

-

DANGER

Si vous ne l'avez pas encore fait, veuillez suivre Dumping de la NAND. Même si les chances sont minces, Unlaunch peut accidentellement bricker votre Nintendo DSi. Une sauvegarde NAND peut être restaurée avec du hardmodouvrir dans une nouvelle fenêtre, à condition de savoir souder.

WARNING

Assurez-vous que votre console est chargée lorsque vous suivez cette procédure. Une perte soudaine de batterie pourrait causer de graves dégâts.

WARNING

Unlaunch n'est pas compatible avec les consoles de développement Nintendo DSi.

Section I - Configuration de la carte SD

  1. Téléchargez la dernière version d'Unlaunchouvrir dans une nouvelle fenêtre
  2. Extrayez UNLAUNCH.DSI depuis unlaunch.zip et placez-le n'importe où sur votre carte SD
  3. Vérifiez que vous avez toujours TWiLight Menu++ sur votre carte SD

Section II - Installation/Mise à jour d'Unlaunch

  1. Ouvrez TWiLight Menu++
    • Si c'est la première fois que vous installez Unlaunch, relancez TWiLight Menu++ avec l'exploit que vous avez utilisé
    • Si vous avez déjà installé Unlaunch et que vous cherchez à le mettre à jour, maintenez A + B pendant le démarrage et sélectionnez l'option intitulée TWiLight Menu++
    • Si plusieurs options sont intitulées TWiLight Menu++, sélectionnez l'option dans laquelle BOOT.NDS apparaît à la fin du chemin sur l'écran inférieur
  2. Lancez les paramètres de TWiLight Menu++
    • Si vous n'avez pas changé de thème, appuyez sur SELECT et touchez la petite icône DS en bas de l'écran tactile. Sinon, consultez le manuel de TWiLight Menu++
  3. Pressez L / R ou X / Y jusqu'à ce que vous atteigniez la page Paramètres d'Unlaunch
  4. Si vous voulez changer l'image en fond d'écran d'Unlaunch, sélectionnez Fond d'écran et choisissez celle qui vous convient
  5. Quittez les paramètres de TWiLight Menu++
  6. Dans le menu de navigation des fichiers, lancez Unlaunch DSi Installer
    • Si vous voyez deux écrans noirs après le lancement, téléchargez GodMode9iouvrir dans une nouvelle fenêtre, mettez son fichier .dsi à la racine de la carte SD, puis lancez GodMode9i en utilisant TWiLight Menu++ et lancez Unlaunch.dsi
      . Cette méthode ne permet pas à Unlaunch d'utiliser des patchs et des fonds personnalisés
  7. Sélectionnez l'option « install now »
    • Si Unlaunch plante à ERROR: MISMATCH IN FAT COPIES, veuillez consulter la page de dépannage
  8. Une fois terminé, redémarrez votre système

Si vous voyez l'écran du menu de fichiers d'Unlaunch, vous avez moddé votre Nintendo DSi avec succès.

  • Si vous voyez un écran noir, veuillez consulter la page de dépannage

Section III - Configuration post-Unlaunch

Actuellement, Unlaunch lance par défaut son menu Fichier au démarrage, mais cela peut être modifié pour lancer ce que vous voulez.

  1. Allumez votre console en maintenant A et B
    • Cela devrait lancer le menu Fichier d'Unlaunch
    • Si seul l'arrière-plan est affiché, ou si aucun fichier de la carte SD n'est affiché (comme TWiLight Menu++), alors vous devrez reformater la carte SD
  2. Naviguez vers OPTIONS et regardez les options disponibles
    • A + B est codé en dur pour être lancé dans le menu de Unlaunch, et ne peut donc pas être modifié
    • Les options NO BUTTON et BUTTON A / B / X / Y peuvent être réglées comme vous le souhaitez et choisiront ce que votre DSi charge au démarrage en fonction des boutons maintenus. Vous pouvez sélectionner n'importe quel DSiWare ou homebrew, la carte Slot-1, wifiboot, ou le menu Fichier d'Unlaunch
      • Pour TWiLight Menu++, sélectionnez TWiLight Menu++
      • Pour le menu DSi original, sélectionnez Launcher
    • LOAD ERROR est ce que votre DSi chargera si le chargement de ce que vous avez défini échoue, comme la carte SD qui n'est pas insérée
  3. Sélectionnez SAVE & EXIT pour enregistrer vos paramètres, puis éteignez votre DSi

Section IV - Nettoyage de votre carte SD

TIP

Cette section est facultative et ne sert qu'à débarrasser votre carte SD des fichiers dont vous n'avez pas besoin.

  • Supprimez le fichier sd:/private/ds/app/484E494A/pit.bin de votre carte SD
    • Si tip.bin existe toujours, alors renommez-le en pit.bin
  • Vous pouvez maintenant restaurer le dossier DCIM qui était à la racine de votre carte SD, si ce dossier existait
  • Supprimez le fichier UNLAUNCH.DSI de votre carte SD
  • Supprimez les fichiers 800031_104784BAB6B57_000.ppm et T00031_1038C2A757B77_000.ppm des dossiers suivants :
    • sd:/private/ds/app/4B47554A/001 (Japon)
    • sd:/private/ds/app/4B475545/001 (États-Unis)
    • sd:/private/ds/app/4B475556/001 (Europe/Australie)
    • Vous pouvez également supprimer tous les dossiers des régions autres que la vôtre
  • Supprimez le fichier UNLAUNCH.DSI de votre carte SD
- - - diff --git a/fr_FR/launching-the-browser-exploit.html b/fr_FR/launching-the-browser-exploit.html deleted file mode 100644 index 1d8f40041..000000000 --- a/fr_FR/launching-the-browser-exploit.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Lancement de l'exploit (stylehax) | Guide DSi - - - - -
Guide DSi

Lancement de l'exploit (stylehax)

Rejoignez le serveur Discord DS⁽ⁱ⁾ Mode Hacking! pour le développement du guide et l'aide.

-

Nous allons commencer par lancer notre exploit. Pour une expérience optimale sans Unlaunch, ou si l'appareil photo DSi est cassé pour installer Unlaunch, nous recommandons d'utiliser un exploit appelé « stylehax » qui tire parti d'une faille dans la façon dont l'application Nintendo DSi Browser traite les pages Web.

Le lancement de l'exploit vous fera démarrer dans TWiLight Menu++, une application homebrew qui remplace le menu DSi.

Prérequis

  • Le Nintendo DSi Browser installé sur votre Nintendo DSi
    • Si vous ne disposez pas du Nintendo DSi Browser, utilisez plutôt Memory Pit

Lancement de l'exploit

  1. Assurez-vous que votre carte SD est insérée dans votre Nintendo DSi
  2. Démarrez votre Nintendo DSi et lancez l'application Nintendo DSi Browser
  3. Appuyez sur le bouton Aller à la page
    • Le bouton aura une icône www verte
  4. Tapez opera:about, et touchez Aller pour charger la page
  5. Touchez l'icône ACCUEIL
  6. Appuyez sur le bouton Aller à la page
  7. Tapez stylehax.net, et touchez Aller pour charger la page

TIP

L'exploit devrait prendre 21 secondes pour faire effet. Si cela prend plus de 30 secondes, redémarrez et réessayez.

WARNING

Si l'écran supérieur devient vert, vous n'avez pas le BOOT.NDS de TWiLight Menu++ à la racine de votre carte SD. Suivez à nouveau le travail préparatoire.

Vous pouvez maintenant utiliser TWiLight Menu++ ! Tout d'abord, il vous demandera de sélectionner votre langue et votre région. Celles-ci n'ont pas besoin de correspondre à la langue ou à la région de votre console, alors réglez-les sur celles que vous préférez. Ensuite, il est recommandé de continuer et de faire une sauvegarde de la NAND. Cela peut potentiellement être utilisé pour sauver votre console si quelque chose de mauvais se produit à l'avenir.

TIP

Continuez vers Dumping de la NAND

- - - diff --git a/fr_FR/launching-the-exploit.html b/fr_FR/launching-the-exploit.html deleted file mode 100644 index f83a4d1f1..000000000 --- a/fr_FR/launching-the-exploit.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Lancement de l'exploit | Guide DSi - - - - -
Guide DSi

Lancement de l'exploit

Rejoignez le serveur Discord DS⁽ⁱ⁾ Mode Hacking! pour le développement du guide et l'aide.

-

Nous allons commencer par configurer votre carte SD pour lancer notre exploit. Pour la plupart des utilisateurs, nous recommandons d'utiliser un exploit appelé « Memory Pit » qui tire parti d'une faille dans la façon dont l'application de l'appareil photo Nintendo DSi traite les métadonnées des images.

Le lancement de l'exploit vous fera démarrer dans TWiLight Menu++, une application homebrew qui remplace le menu DSi.

TIP

Si vous ne prévoyez pas d'installer Unlaunch et que vous avez le Nintendo DSi Browser ou Flipnote Studio, il est recommandé d'utiliser stylehax ou Flipnote Lenny à la place. Quel est le meilleur exploit ?

Section I - Vérification de la version de votre appareil photo DSi

  1. Allumez votre console
  2. Ouvrir l'appareil photo Nintendo DSi
    • Si vous êtes invité à terminer le tutoriel sur l'appareil photo, faites-le maintenant
    • Si le tutoriel se bloque lorsque vous essayez de le terminer, il est probable que le matériel de votre appareil photo Nintendo DSi soit défectueux et que vous ne puissiez pas utiliser Memory Pit. Veuillez utiliser un exploit alternatif
  3. Ouvrez l'album à l'aide du gros bouton à droite
  4. Vérifiez si vous avez une icône Facebook à côté de l'étoile, des trèfles et du cœur, indiqués en rouge ici : Capture d'écran de l'emplacement de l'icône Facebook

Section II - Memory Pit

  1. Téléchargez le bon binaire Memory Pit pour la version de votre appareil photo Nintendo DSi :
  2. Accédez au dossier sd:/private/ds/app/484E494A/ sur votre carte SD
    • Vous aurez déjà ce répertoire si vous avez déjà pris des photos sur votre carte SD via l'application de l'appareil photo Nintendo DSi. Si c'est le cas, vous n'avez pas besoin de le supprimer et de le recréer
    • S'il n'existe pas, veuillez créer les dossiers individuels
  3. S'il existe déjà un fichier pit.bin dans ce chemin, renommez-le en tip.bin
  4. Placez le fichier Memory Pit pit.bin dans ce dossier
  5. S'il y a un dossier nommé DCIM à la racine de votre carte SD, faites-en une sauvegarde afin de ne pas perdre les images qu'il contient, puis retirez-le de la carte SD

Section III - Lancement de l'exploit

  1. Assurez-vous que votre carte SD est insérée dans votre Nintendo DSi
  2. Démarrez votre Nintendo DSi et lancez l'application de l'appareil photo Nintendo DSi
  3. Sélectionnez l'icône de la carte SD en haut à droite
    • Si vous recevez un message indiquant que votre carte SD n'est pas insérée, veuillez utiliser une autre carte SD
    • Si vous recevez un message indiquant que votre carte SD ne peut pas être utilisée, assurez-vous que votre carte SD est formatée correctement
  4. Ouvrez l'album à l'aide du gros bouton à droite
    • L'écran doit clignoter en magenta si Memory Pit a été copié correctement

WARNING

Si l'écran supérieur devient vert, vous n'avez pas le BOOT.NDS de TWiLight Menu++ à la racine de votre carte SD. Suivez à nouveau le travail préparatoire.

WARNING

Si vous entrez dans l'album de l'appareil photo de la carte SD et que rien d'inhabituel ne se produit, assurez-vous d'avoir téléchargé la bonne version de Memory Pit pour votre version et votre région, et de l'avoir placé dans le bon dossier de votre carte SD. Assurez-vous également que le dossier DCIM n'existe pas sur votre carte SD.

Vous pouvez maintenant utiliser TWiLight Menu++ ! Tout d'abord, il vous demandera de sélectionner votre langue et votre région. Celles-ci n'ont pas besoin de correspondre à la langue ou à la région de votre console, alors réglez-les sur celle que vous préférez. Ensuite, il est recommandé de continuer et de faire une sauvegarde de la NAND. Cela peut potentiellement être utilisé pour sauver votre console si quelque chose de mauvais se produit à l'avenir.

TIP

Continuez vers Dumping de la NAND

- - - diff --git a/fr_FR/launching-the-flipnote-exploit.html b/fr_FR/launching-the-flipnote-exploit.html deleted file mode 100644 index a0af64903..000000000 --- a/fr_FR/launching-the-flipnote-exploit.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Lancement de l'exploit (Flipnote Lenny) | Guide DSi - - - - -
Guide DSi

Lancement de l'exploit (Flipnote Lenny)

Rejoignez le serveur Discord DS⁽ⁱ⁾ Mode Hacking! pour le développement du guide et l'aide.

-

Nous allons commencer par configurer votre carte SD pour lancer notre exploit. Pour une expérience optimale, nous vous recommandons d'utiliser un exploit appelé « Flipnote Lenny » qui tire parti d'une faille dans la façon dont l'application Flipnote Studio gère les flipnotes.

Le lancement de l'exploit vous fera démarrer dans TWiLight Menu++, une application homebrew qui remplace le menu DSi.

Prérequis

  • Flipnote Studio installé sur votre Nintendo DSi
    • Si vous ne disposez pas de Flipnote Studio, utilisez plutôt Memory Pit

Section I - Configuration de la carte SD

  1. Téléchargez la dernière version de Flipnote Lennyouvrir dans une nouvelle fenêtre
  2. Copiez le dossier private de l'archive Flipnote Lenny à la racine de votre carte SD

Section II - Lancement de l'exploit

  1. Assurez-vous que votre carte SD est insérée dans votre Nintendo DSi
  2. Démarrez votre Nintendo DSi et lancez l'application Flipnote Studio
    • Si vous recevez un message indiquant que votre carte SD ne peut pas être utilisée, assurez-vous que votre carte SD est formatée correctement
  3. Ouvrez les paramètres de Flipnote Studio en haut à droite du menu principal et assurez-vous que Démarrer sur le calendrier est désactivé et que Grenouille est activé
  4. Affichez les flipnotes stockées sur la carte SD
    • Si vous ne parvenez pas à visualiser les flipnotes sur la carte SD, veuillez utiliser une autre carte SD
  5. Tapez sur le visage correspondant à votre région
    • Si vous avez une console AUS, sélectionnez EUR
  6. Modifiez la flipnote sélectionnée
  7. Appuyez sur l'icône de grenouille en bas à gauche
  8. Appuyez sur l'icône du rouleau de film
  9. Sélectionnez Copier -> Retour -> Quitter
  10. Appuyez sur la deuxième note avec un visage plus grand et sélectionnez Modifier
  11. Appuyez sur l'icône de grenouille en bas à gauche
  12. Appuyez sur l'icône du rouleau de film
  13. Sélectionnez coller

WARNING

Si l'écran supérieur devient vert, vous n'avez pas le BOOT.NDS de TWiLight Menu++ à la racine de votre carte SD. Suivez à nouveau le travail préparatoire.

Vous pouvez maintenant utiliser TWiLight Menu++ ! Tout d'abord, il vous demandera de sélectionner votre langue et votre région. Celles-ci n'ont pas besoin de correspondre à la langue ou à la région de votre console, alors réglez-les sur celles que vous préférez. Ensuite, il est recommandé de continuer et de faire une sauvegarde de la NAND. Cela peut potentiellement être utilisé pour sauver votre console si quelque chose de mauvais se produit à l'avenir.

TIP

Continuez vers Dumping de la NAND

- - - diff --git a/fr_FR/lazy-dsi-downloader.html b/fr_FR/lazy-dsi-downloader.html deleted file mode 100644 index 9da3a1b00..000000000 --- a/fr_FR/lazy-dsi-downloader.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Lazy DSi Downloader | Guide DSi - - - - -
Guide DSi

Lazy DSi Downloader

Rejoignez le serveur Discord DS⁽ⁱ⁾ Mode Hacking! pour le développement du guide et l'aide.

-

« Lazy DSi Downloader » est un outil destiné à simplifier le processus de moddage d'une console Nintendo DSi.

Étapes de vérification

  1. Allumez votre Nintendo DSi
  2. Lancez l'application de l'appareil photo Nintendo DSi

Si, à ce stade, vous obtenez un tutoriel et que vous obtenez un plantage en essayant de le suivre, alors vous ne pouvez pas utiliser Memory Pit.

Guide d'installation

  1. Téléchargez la dernière version de Lazy DSi File Downloaderouvrir dans une nouvelle fenêtre pour votre OS
  2. Lancez-le en suivant les instructions relatives à votre système d'exploitation figurant sur la page de publication
  3. Appuyez sur le bouton « Next »
    • La lecture du texte d'introduction n'est pas obligatoire
  4. Si votre Nintendo DSi a planté pendant les étapes de vérification ci-dessus, désactivez l'option « Memory Pit »
  5. Cochez les cases pour Download latest GodMode9i version? (« Télécharger la dernière version de GodMode9i ? »)
    • N'hésitez pas à sélectionner l'une des autres applications homebrews dans Click to add Additional homebrew… (« Cliquez pour ajouter un homebrew supplémentaire… »), mais ce n'est pas obligatoire
  6. Attendez que tout soit téléchargé, puis cliquez sur Finish (« Terminer »)
- - - diff --git a/fr_FR/restoring-nand.html b/fr_FR/restoring-nand.html deleted file mode 100644 index a9e19e2d5..000000000 --- a/fr_FR/restoring-nand.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Restauration d'une sauvegarde de la NAND | Guide DSi - - - - -
Guide DSi

Restauration d'une sauvegarde de la NAND

Rejoignez le serveur Discord DS⁽ⁱ⁾ Mode Hacking! pour le développement du guide et l'aide.

-

DANGER

ATTENTION ! Ceci est dangereux. Même en suivant exactement ces étapes, il y a toujours un risque potentiel de brick de la DSi car la NAND est de très mauvaise qualité, surtout si vous flashez plusieurs fois ! Cela ne devrait être utilisé qu'en dernier recours !

TIP

Ne sautez rien sur cette page, toute erreur augmente considérablement les chances de bricker votre DSi.

Tout d'abord, quelques alternatives plus sûres pour expliquer pourquoi vous pourriez vouloir faire cela :

  • L'installation de titres DSiWare peut être faite en utilisant hiyaCFW ou TWiLight Menu++
  • La récupération des images peut se faire en utilisant ninfsouvrir dans une nouvelle fenêtre, en combinaison avec hiyaCFW ou TWiLight Menu++ si vous les voulez sur console. La dernière version de HiyaCFW Helper vous permet de copier vos photos de votre NAND vers la SDNAND pendant l'installation
  • La restauration d'une configuration de boutons d'Unlaunch peut se faire à partir du menu d'Unlaunch, auquel on accède en maintenant A + B tout en allumant la console
  • Démarrer sur Unlaunch entraîne une erreur ? Retirez votre carte SD et essayez de redémarrer le système. Si cela fonctionne, alors c'est un défaut avec votre carte SD et la restauration d'une sauvegarde de la NAND ne le corrigera pas
  • « Une erreur est survenue… » au démarrage est probablement une erreur de hiyaCFW et n'est pas liée à votre NAND, consultez FAQ et dépannage de hiyaCFWouvrir dans une nouvelle fenêtre sur le wiki DS-Homebrew pour plus d'informations
  • Toute erreur dans TWiLight Menu++ n'est pas liée et vous devriez essayer de réinstaller TWiLight Menu++ ou demander de l'aide sur Discordouvrir dans une nouvelle fenêtre
  • La désinstallation d'Unlaunch, que ce soit en flashant la NAND ou en utilisant son désinstallateur, devrait être évitée sauf en cas de nécessité absolue, vous pouvez régler les touches de démarrage automatique sur « Launcher » et votre DSi sera comme avant

La seule chose que vous devriez faire avec votre NAND est d'installer Unlaunch. Sinon, utilisez les alternatives.

Prérequis

Dumping du BIOS pour une utilisation sur no$gba

  1. Extrayez dsibiosdumper.nds depuis l'archive dsibiosdumper.zip et placez-le n'importe où sur votre carte SD
  2. Allumez votre console en maintenant A et B
    • Cela devrait lancer le menu Fichier d'Unlaunch
  3. Lancez dsibiosdumper depuis le menu Fichier d'Unlaunch
  4. Appuyez sur A pour dumper le BIOS sur la carte SD
  5. Appuyez sur START pour quitter dsibiosdumper

Test de votre sauvegarde NAND

Il est très important de tester que votre sauvegarde NAND fonctionne avant d'essayer de la restaurer sur votre console, si elle montre une erreur de brick dans no$gba, il est fort probable que votre console sera également brickée.

  1. Extrayez NO$GBA.EXE depuis no$gba-w.zip vers un dossier sur votre ordinateur
  2. Copiez la sauvegarde de votre NAND dans le dossier dans lequel vous avez placé NO$GBA.EXE et renommez-la DSI-1.MMC
  3. Copiez bios7i.bin et bios9i.bin dans le dossier où vous avez mis NO$GBA.EXE, nommés respectivement BIOSDSI7.ROM et BIOSDSI9.ROM.
  4. Lancez NO$GBA.EXE
  5. Cliquez sur Options > Emulation Setup pour ouvrir la fenêtre de configuration d'émulation
  6. Changez Reset/Startup Entrypoint en GBA/NDS BIOS (Nintendo logo)
  7. Changez NDS Mode/Colors en DSi (retail/16MB)
  8. Cliquez sur Save Now
  9. Lancez n'importe quelle ROM Nintendo DS (fichier.nds)

Si no$gba charge le menu DSi (ou le menu Fichier d'Unlaunch), passez à la section suivante. S'il montre n'importe quel type d'erreur ne flashez pas cette sauvegarde !

Désinstallation d'Unlaunch à partir de votre sauvegarde NAND (facultatif)

Suivez ceci si vous avez dumpé votre sauvegarde NAND après avoir installé Unlaunch et que vous souhaitez désinstaller Unlaunch de votre système. Si vous n'essayez pas de désinstaller Unlaunch, vous n'avez pas besoin de suivre cette section.

  1. Téléchargez la dernière version de l'installateur d'Unlaunchouvrir dans une nouvelle fenêtre
  2. Extrayez UNLAUNCH.DSI de unlaunch.zip
  3. Lancez UNLAUNCH.DSI dans no$gba et démarrez-le depuis l'emplacement de la carte de jeu
    • Cela devrait démarrer le programme d'installation d'Unlaunch, qui ressemble au menu Fichier d'Unlaunch
  4. Choisissez Uninstall
  5. Une fois terminé, choisissez Power down
  6. Lancez à nouveau n'importe quelle ROM Nintendo DS et assurez-vous que votre menu DSi se charge et fonctionne correctement

Si no$gba affiche une erreur quelconque au lieu de charger le menu DSi, ne flashez pas cette sauvegarde ! Si vous avez une ancienne sauvegarde NAND, vous pouvez essayer de l'utiliser à la place. N'essayez pas de désinstaller Unlaunch à l'aide de son programme de désinstallation sur la console, car il est très probable qu'il bricke votre DSi.

Flashage de votre sauvegarde NAND (logiciel)

DANGER

Assurez-vous d'avoir lu les étapes ci-dessus car c'est là que cela devient dangereux. Si vous avez été directement lié ici sans suivre ce qui précède, retournez en haut et lisez toute cette page.

DANGER

Assurez-vous que votre console Nintendo DSi est bien chargée avant de commencer cette section.

  1. Avec votre carte SD insérée, allumez votre Nintendo DSi en maintenant A et B
  2. Lancez SafeNANDManager
  3. Appuyez sur le bouton pour commencer la restauration de la NAND
  4. Une fois la restauration terminée, appuyez sur START pour éteindre votre DSi

Votre NAND devrait maintenant être restaurée.

Flashage de votre sauvegarde NAND (hardmod)

Si vous ne pouvez pas démarrer votre Nintendo DSi, un hardmod est le seul moyen de restaurer une sauvegarde de la NAND. Le meilleur guide qui existe actuellement est le guide de hardmod Nintendo DSi sur le wiki DS-Homebrewouvrir dans une nouvelle fenêtre.

- - - diff --git a/fr_FR/sd-card-setup.html b/fr_FR/sd-card-setup.html deleted file mode 100644 index 42070b470..000000000 --- a/fr_FR/sd-card-setup.html +++ /dev/null @@ -1,85 +0,0 @@ - - - - - - - - - Configuration de la carte SD | Guide DSi - - - - -
Guide DSi

Configuration de la carte SD

Rejoignez le serveur Discord DS⁽ⁱ⁾ Mode Hacking! pour le développement du guide et l'aide.

-

Cette page est destinée à préparer votre carte SD pour votre appareil. Au cours de ce processus, nous formaterons la carte SD et vérifierons qu'il n'y a pas d'erreurs sur la carte.

DANGER

Assurez-vous de sauvegarder le contenu de votre carte SD AVANT de continuer. Toutes les données de votre carte SD seront EFFACÉES pendant le processus.

Section I - Formatage de votre carte SD avec SD Formatter

TIP

Cette section formate la carte SD selon les spécifications de la SD Card Association. Cela peut résoudre de nombreux problèmes pouvant survenir lors de l'exécution d'applications homebrews.

DANGER

Toutes les cartes SD de 64 Go ou plus seront formatées en exFAT au cours de ce processus. Vous devez suivre la section II pour reformater en FAT32.

  1. Téléchargez la dernière version de SD Formatterouvrir dans une nouvelle fenêtre
  2. Exécutez SD Card Formatter Setup (le fichier .exe) avec les droits d'administrateur dans le fichier .zip téléchargé, puis installez le programme
  3. Exécutez SD Card Formatter à partir du menu Démarrer avec les droits d'administrateur
  4. Sélectionnez votre carte SD
  5. Assurez-vous que la case Quick Format (« formatage rapide ») est cochée
  6. Appuyez sur Format pour lancer le processus de formatage Capture d'écran de SD Card Formatter sur Windows 11

Section II - Formatage de votre carte SD avec GUIFormat

Cette section formate les cartes SD supérieures à 32 Go en FAT32.

TIP

Si votre carte SD a une capacité de 32 Go ou moins, passez à la section III.

  1. Téléchargez la dernière version de GUIFormatouvrir dans une nouvelle fenêtre
    • Cliquez sur l'image du site pour télécharger l'application
  2. Exécutez GUIFormat avec les droits d'administrateur
  3. Sélectionnez votre lettre de lecteur
  4. Définissez l'unité de taille d'allocation (Allocation size unit) à 32768
    • Si cette taille est trop grande pour votre SD, définissez-la à la plus haute qui fonctionne
  5. Assurez-vous que la case Quick Format (« formatage rapide ») est cochée
  6. Lancez le processus de formatage

Section III - Vérification des erreurs

  1. Allez dans la fenêtre des propriétés de votre carte SD
    • Explorateur Windows -> Ce PC -> Clic droit sur votre carte SD -> Propriétés
  2. Dans l'onglet Outils, sélectionnez Vérifier maintenant
  3. Cochez à la fois Réparer automatiquement les erreurs de système de fichiers et Rechercher et tenter une récupération des secteurs défectueux
  4. Lancez le processus de vérification

Cette opération permet de scanner la carte SD et de corriger les erreurs qu'elle trouve.

Section IV - Vérification de la lecture/écriture de la carte SD

  1. Téléchargez et extrayez l'archive h2testwouvrir dans une nouvelle fenêtre n'importe où sur votre ordinateur
  2. Avec votre carte SD insérée dans votre ordinateur, exécutez h2testw.exe
  3. Sélectionnez la langue dans laquelle vous souhaitez voir h2testw. Étant donné qu'il n'est pas disponible en français, les noms anglais seront utilisés et traduits pour ce guide
  4. Définissez la lettre de lecteur de votre carte SD en tant que cible
  5. Assurez-vous que All available space (« Tout l'espace disponible ») est sélectionné
  6. Cliquez sur Write + Verify (« Écrire + Vérifier »)
  • Attendez que le processus se termine

TIP

Si le test affiche le résultat Test finished without errors (« Test terminé sans erreur »), votre carte SD est saine et vous pouvez supprimer tous les fichiers .h2w sur votre carte SD.

DANGER

Si le test donne d'autres résultats, votre carte SD est peut-être corrompue ou endommagée et vous devrez peut-être la remplacer !

TIP

Si TWiLight Menu++ ne démarre pas après avoir suivi cette méthode, veuillez plutôt suivre la méthode Windows, soit en redémarrant sous Windows, soit en exécutant une machine virtuelle Windows

Section I - Formatage de votre carte SD

  1. Assurez-vous que votre carte SD n'est pas insérée dans votre machine Linux
  2. Lancez le terminal Linux
  3. Tapez watch "lsblk"
  4. Insérez votre carte SD dans votre machine Linux
  5. Observez le résultat. Cela devrait ressembler à quelque chose comme cela :
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
-mmcblk0     179:0    0   3,8G  0 disk
-└─mmcblk0p1 179:1    0   3,7G  0 part /run/media/user/FFFF-FFFF
-
  1. Prenez note du nom de l'appareil. Dans notre exemple ci-dessus, c'était mmcblk0p1
    • Si RO est réglé sur 1, assurez-vous que l'interrupteur de verrouillage n'est pas glissé vers le bas
    • Assurez-vous que vous ciblez la partition, mmcblk0p1 et non mmcblk0
  2. Appuyez sur CTRL + C pour quitter le menu
  3. Suivez les instructions relatives à la capacité de votre carte SD :
    • 2 Go ou moins : sudo mkdosfs /dev/(nom de l'appareil ci-dessus) -s 64 -F 16
      • Cela crée une seule partition FAT16 avec une taille de cluster de 32 ko sur la carte SD
    • 4 Go ou plus : sudo mkdosfs /dev/(nom de l'appareil ci-dessus) -s 64 -F 32
      • Cela crée une seule partition FAT32 avec une taille de cluster de 32 ko sur la carte SD

Section II - Utilisation de F3

  1. Téléchargez et extrayez l'archive F3ouvrir dans une nouvelle fenêtre n'importe où sur votre ordinateur.
  2. Lancez le terminal dans le dossier F3
  3. Exécutez make pour compiler F3
  4. Avec votre carte SD insérée et montée, exécutez ./f3write <le point de montage de votre carte SD>
    • Attendez que le processus soit terminé. Regardez ci-dessous pour un exemple de sortie du terminal :
    $ ./f3write /media/michel/6135-3363/
-Free space: 29.71 GB
-Creating file 1.h2w ... OK!
-...
-Creating file 30.h2w ... OK!
-Free space: 0.00 Byte
-Average Writing speed: 4.90 MB/s
-
  5. Exécutez ./f3read <le point de montage de votre carte SD>
  • Attendez que le processus soit terminé. Regardez ci-dessous pour un exemple de sortie du terminal :
    $ ./f3read /media/michel/6135-3363/
-                  SECTORS      ok/corrupted/changed/overwritten
-Validating file 1.h2w ... 2097152/        0/      0/      0
-...
-Validating file 30.h2w ... 1491904/        0/      0/      0
-
-   Data OK: 29.71 GB (62309312 sectors)
-Data LOST: 0.00 Byte (0 sectors)
-            Corrupted: 0.00 Byte (0 sectors)
-   Slightly changed: 0.00 Byte (0 sectors)
-         Overwritten: 0.00 Byte (0 sectors)
-Average Reading speed: 9.42 MB/s
-

TIP

Si le test affiche le résultat Data LOST: 0.00 Byte (0 sectors) votre carte SD est saine et vous pouvez supprimer tous les fichiers .h2w sur votre carte SD.

DANGER

Si le test donne d'autres résultats, votre carte SD est peut-être corrompue ou endommagée et vous devrez peut-être la remplacer !

Section I - Formatage de votre carte SD avec SD Formatter

TIP

Cette section formate la carte SD selon les spécifications de la SD Card Association. Cela peut résoudre de nombreux problèmes pouvant survenir lors de l'exécution d'applications homebrews.

DANGER

Toutes les cartes SD de 64 Go ou plus seront formatées en exFAT au cours de ce processus. Vous devez suivre la section II pour reformater en FAT32.

  1. Téléchargez la dernière version de SD Formatterouvrir dans une nouvelle fenêtre
    • Acceptez les conditions générales d'utilisation pour lancer le téléchargement
  2. Exécutez Install SD Card Formatter (le fichier .mpkg) dans le fichier .zip téléchargé
  3. Exécutez SD Card Formatter
  4. Sélectionnez votre carte SD
  5. Assurez-vous que la case Quick Format (« formatage rapide ») est cochée
  6. Lancez le processus de formatage

Section II - Formatage de votre carte SD avec l'Utilitaire de disque

Cette section formate les cartes SD supérieures à 32 Go en FAT32.

TIP

Si votre carte SD a une capacité de 32 Go ou moins, passez à la section III.

OS X El Capitan (10.11) et versions ultérieures

  1. Lancez l'application Utilitaire de disques
  2. Sélectionnez Afficher tous les appareils dans le panneau Présentation en haut à gauche
  3. Sélectionnez votre carte SD dans la barre latérale
    • Assurez-vous de choisir le bon périphérique, sinon vous risquez d'effacer accidentellement le mauvais lecteur !
  4. Cliquez sur Effacer en haut
  5. Assurez-vous que le Format est défini à MS-DOS (FAT32)
    • De El Capitan (10.11) à Catalina (10.15) choisissez MS-DOS (FAT)
  6. Assurez-vous que Schéma est réglé sur Master Boot Record
    • Si Schéma n'apparaît pas, cliquez sur Annuler et assurez-vous de choisir le périphérique au lieu d'un volume
  7. Cliquez sur Effacer, puis cliquez sur Fermer

OS X Yosemite (10.10) et versions antérieures

  1. Lancez l'application Utilitaire de disques
  2. Sélectionnez votre carte SD dans la barre latérale
    • Assurez-vous de choisir le bon périphérique, sinon vous risquez d'effacer accidentellement le mauvais lecteur !
  3. Cliquez sur Partitionner en haut
    • Si Partitionner n'apparaît pas, assurez-vous de choisir le périphérique au lieu d'un volume
  4. Assurez-vous que la Configuration de volume est définie à 1 partition
  5. Assurez-vous que le Format est défini à MS-DOS (FAT)
  6. Depuis le bouton Options (en dessous de la table de partitions), sélectionnez Master Boot Record.
  7. Cliquez sur OK -> Appliquer -> Partition

Section III - Utilisation de F3

  1. Ouvrez le terminal
  2. Installez F3 depuis brew en exécutant brew install f3
  3. Avec votre carte SD insérée et montée, exécutez ./f3write <le point de montage de votre carte SD>
    • Attendez que le processus soit terminé. Regardez ci-dessous pour un exemple de sortie du terminal :
    $ f3write /Volumes/SD\ CARD
-Free space: 29.71 GB
-Creating file 1.h2w ... OK!
-...
-Creating file 30.h2w ... OK!
-Free space: 0.00 Byte
-Average Writing speed: 4.90 MB/s
-
  4. Exécutez f3read <le point de montage de votre carte SD>
    • Attendez que le processus soit terminé. Regardez ci-dessous pour un exemple de sortie du terminal :
    $ f3read /Volumes/SD\ CARD
-                  SECTORS      ok/corrupted/changed/overwritten
-Validating file 1.h2w ... 2097152/        0/      0/      0
-...
-Validating file 30.h2w ... 1491904/        0/      0/      0
-
-   Data OK: 29.71 GB (62309312 sectors)
-Data LOST: 0.00 Byte (0 sectors)
-            Corrupted: 0.00 Byte (0 sectors)
-   Slightly changed: 0.00 Byte (0 sectors)
-         Overwritten: 0.00 Byte (0 sectors)
-Average Reading speed: 9.42 MB/s
-

TIP

Si le test affiche le résultat Data LOST: 0.00 Byte (0 sectors) votre carte SD est saine et vous pouvez supprimer tous les fichiers .h2w sur votre carte SD.

DANGER

Si le test donne d'autres résultats, votre carte SD est peut-être corrompue ou endommagée et vous devrez peut-être la remplacer !

TIP

Vous pouvez maintenant restaurer le contenu de votre carte SD et continuer.

- - - diff --git a/fr_FR/site-navigation.html b/fr_FR/site-navigation.html deleted file mode 100644 index f60b511db..000000000 --- a/fr_FR/site-navigation.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Navigation du site | Guide DSi - - - - -
Guide DSi

Navigation du site

Rejoignez le serveur Discord DS⁽ⁱ⁾ Mode Hacking! pour le développement du guide et l'aide.

-

- - - diff --git a/fr_FR/troubleshooting.html b/fr_FR/troubleshooting.html deleted file mode 100644 index f2326fa09..000000000 --- a/fr_FR/troubleshooting.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Dépannage | Guide DSi - - - - -
Guide DSi

Dépannage

Rejoignez le serveur Discord DS⁽ⁱ⁾ Mode Hacking! pour le développement du guide et l'aide.

-

Unlaunch

Unlaunch plante à MISMATCH IN FAT COPIES

twlnf a un bug critique où il ne met pas correctement à jour la NAND entière après l'avoir modifiée, ce qui fait que certains homebrews (comme l'installateur d'Unlaunch) montrent une erreur.

Pour résoudre ce problème, ouvrez NAND Title Manager (NTM)ouvrir dans une nouvelle fenêtre et sélectionnez Fix FAT copy mismatch.

Il n'y a pas de son ni d'écran de démarrage lors du lancement de « LAUNCHER » en utilisant Unlaunch

Le développeur d'Unlaunch (nocash) a intentionnellement corrigé l'audio d'arrière-plan et l'écran de démarrage par défaut. Vous pouvez retrouver ces effets en réinstallant Unlaunch à l'aide de TWiLight Menu++ avec les « patchs de lancement » définis sur « Défaut » sur la page Unlaunch des paramètres de TWiLight Menu++, ou en utilisant hiyaCFWouvrir dans une nouvelle fenêtre.

Après l'installation de Unlaunch, l'écran est noir à la mise sous tension

Essayez d'éjecter la carte SD et de rallumer la console. S'il n'affiche toujours qu'un écran noir, vous devrez peut-être flasher votre NAND via un hardmodouvrir dans une nouvelle fenêtre.

Après avoir installé Unlaunch, je suis bloqué au démarrage d'une application ou du menu Fichier d'Unlaunch

Cela a probablement été causé par le choix de la mauvaise application pour l'option NO BUTTON dans Unlaunch. Maintenez A + B lors du démarrage de la console, accédez à OPTIONS et définissez NO BUTTON selon vos préférences.

Autres problèmes d'Unlaunch

Si Unlaunch affiche Clusters too large, Bad VBR, Bad MBR, ou n'affiche aucune application alors que la carte SD est insérée, votre carte SD n'a probablement pas été formatée correctement. Suivez de nouveau Configuration de la carte SD.

TWiLight Menu++

Pour un dépannage général de TWiLight Menu++, consultez sa page FAQ et dépannageouvrir dans une nouvelle fenêtre sur le wiki DS-Homebrew.

Assistance supplémentaire

Si vous avez rencontré un problème qui n'est pas résolu ici, ou qui persiste malgré les solutions données, demandez de l'aide sur le serveur Discord DS(i)Mode Hacking!ouvrir dans une nouvelle fenêtre.

- - - diff --git a/fr_FR/uninstalling-unlaunch.html b/fr_FR/uninstalling-unlaunch.html deleted file mode 100644 index bb31c56aa..000000000 --- a/fr_FR/uninstalling-unlaunch.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Désinstallation d'Unlauch | Guide DSi - - - - -
Guide DSi

Désinstallation d'Unlauch

Rejoignez le serveur Discord DS⁽ⁱ⁾ Mode Hacking! pour le développement du guide et l'aide.

-

DANGER

Installer ou désinstaller Unlaunch peut bricker aléatoirement votre console ! Vous êtes prévenu !

AVERTISSEMENT : Une désinstallation d'Unlaunch peut bricker votre Nintendo DSi. Voici quelques cas pour lesquels vous pourriez vouloir désinstaller Unlaunch, mais avec des solutions qui ne nécessitent pas de désinstallation.

  • L'arrière-plan d'Unlaunch est effrayant : Réinstallez Unlaunch en suivant les nouvelles instructions. La façon de changer l'arrière-plan y est désormais expliquée
  • Je rencontre un problème avec Unlaunch ou ma console après l'avoir installé : La page Dépannage vous expliquera comment résoudre de nombreux problèmes que vous pouvez rencontrer

WARNING

Pour réduire les risques de brick, assurez-vous que vous n'avez pas installé de DSiWare illégitime sur votre sauvegarde NAND (la redirection de la SDNAND fournie par hiyaCFW ne compte pas), ou que vous n'avez pas altéré les fichiers système.

WARNING

Lorsque vous désinstallez Unlaunch, n'utilisez PAS son désinstalleur intégré directement sur votre console car il y a une chance qu'il bricke la console. Veuillez voir ci-dessous pour obtenir des informations sur la façon de le désinstaller correctement.

Une fois que vous avez examiné les informations ci-dessus, suivez les instructions de la page Dumping de la NAND pour faire une nouvelle sauvegarde NAND, puis passez à Restauration d'une sauvegarde de la NAND. Cela vous guidera dans la désinstallation d'Unlaunch à partir de la sauvegarde NAND et le flashage de celle-ci sur votre console.

Si vous n'êtes pas en mesure d'utiliser no$gba ou si vous obtenez une erreur après avoir désinstallé Unlaunch dans no$gba, il est également possible de flasher une sauvegarde NAND faite avant l'installation d'Unlaunch si vous en avez encore une. Cependant, il est d'abord recommandé d'essayer d'utiliser une sauvegarde NAND qui avait précédemment Unlaunch. Cela rendra la récupération beaucoup plus facile dans le cas d'un brick nécessitant un hardmod car Unlaunch laisse le pied de page no$gba intégré dans la NAND même lorsqu'il est désinstallé.

- - - diff --git a/get-started.html b/get-started.html index df9cdbf38..dbeae90fd 100644 --- a/get-started.html +++ b/get-started.html @@ -3,7 +3,7 @@ - + - - Az oldal nem található | DSi Útmutató - - - - -
- - - diff --git a/hu_HU/alternate-exploits.html b/hu_HU/alternate-exploits.html deleted file mode 100644 index e7ddd975e..000000000 --- a/hu_HU/alternate-exploits.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Alternatív Exploit-ok | DSi Útmutató - - - - -
DSi Útmutató

Alternatív Exploit-ok

Csatlakozz a DS⁽ⁱ⁾ Mode Hacking! Discord szerverhez az útmutató fejlesztéséhez és segítségért.

-

Ha a tutorialt kapod, amikor elindítod a Nintendo DSi Camera alkalmazást, és összeomlik, amikor megpróbálod befejezni azt, nem használhatod a Memory Pit-et. Itt találhatsz alternatív exploitokat, amik működhetnek, arra az esetre ha a Memory Pit nem használható.

Ha van Flipnote Studio-d telepítve, használhatod a Flipnote Lenny-t.

TIP

Ellenőrizd, hogy telepítve van a TWiLight Menu++ az SD kártyádon, mielőtt folytatod bármelyikkel a következők közül.

Ha régebbi firmware-en vagy, akkor lehetőséged lehet save game exploitokra a listázott játékoknálmegnyitás új ablakban. Ezek nem kerülnek ismertetésre itt, mert jó részük elavult. Csak utolsó mentsvárként alkalmazandók, ha sem a Memory Pit, sem a Flipnote Lenny nem működik számodra.

petit-compwner nem használható a Memory Pit körüli dolgokra, mert működő kamerát igényel az exploit indítására.

- - - diff --git a/hu_HU/credits.html b/hu_HU/credits.html deleted file mode 100644 index e9856a925..000000000 --- a/hu_HU/credits.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Készítők | DSi Útmutató - - - - -
DSi Útmutató

Készítők

Csatlakozz a DS⁽ⁱ⁾ Mode Hacking! Discord szerverhez az útmutató fejlesztéséhez és segítségért.

-

Ez a készítők listája, akik segítettek az útmutató weboldalon, homebrew és egyéb dolgokban.

Ha tetszik amit csináltak, gondolkozz el a támogatásukon (ha van támogatási linkjük).

Részt vehetsz az útmutató készítésében, egyszerűen egy Pull Request beküldésévelmegnyitás új ablakban!

Ha beszélsz más nyelveken, segíthetsz nekünk az úmtutató fordításával arra a nyelvre. Csatlakozz a Crowdin Projectmegnyitás új ablakban-ünkhöz a kezdéshez.

- - - diff --git a/hu_HU/dsiware-backups.html b/hu_HU/dsiware-backups.html deleted file mode 100644 index 995434511..000000000 --- a/hu_HU/dsiware-backups.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - DSiWare mentések | DSi Útmutató - - - - -
DSi Útmutató

DSiWare mentések

Csatlakozz a DS⁽ⁱ⁾ Mode Hacking! Discord szerverhez az útmutató fejlesztéséhez és segítségért.

-

Követelmények

  • A GodMode9imegnyitás új ablakban legfrissebb kiadása
    • Töltsd le az archívot, csomagold ki a tartalmát és helyezd aGodMode9i.nds-t bárhova az SD kártyára

Nintendo DSi - Lépések

I. rész - A DSiWare dumpolása

  1. Indítsd el a GodMode9i-t
  2. Nyomj START gombot a START menü megnyitásához
  3. Válaszd a Cím kezelő... opciót
    • Ha ez nem jelenik meg, ellenőrizd, hogy az SD kártyád és a NAND csatoltak. Ha hiyaCFW-ből töltötted, töltsd újra máshonnan
  4. Válaszd ki a címet, amit dumpolni akarsz
  5. Válaszd ki amit dumpolni akarsz
  6. Ismételd meg a 4-5. lépéseket minden DSIWare-re, amit szeretnél dumpolni

TIP

A dumpolt DSiWare-k az sd:/gm9i/out mappában lesznek megtalálhatók.

- - - diff --git a/hu_HU/dumping-game-cards.html b/hu_HU/dumping-game-cards.html deleted file mode 100644 index ed69ef334..000000000 --- a/hu_HU/dumping-game-cards.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Játékkártyák dumpolása | DSi Útmutató - - - - -
DSi Útmutató

Játékkártyák dumpolása

Csatlakozz a DS⁽ⁱ⁾ Mode Hacking! Discord szerverhez az útmutató fejlesztéséhez és segítségért.

-

Ez a rész a játék kártyák dumpolásáról szól GodMode9i-vel, így játszhatók emulátorral, flashcard-ról vagy az SD kártyádról nds-bootstrap segítségével.

Követelmények

  • A dumpolando cím játék kártyája
  • A Nintendo DSi konzolod telepített Unlaunch-csel

Instrukciók

I. rész - SD kártya telepítés

  1. Töltsd le a GodMode9imegnyitás új ablakban legfrissebb kiadását
  2. Csomagold ki a GodMode9i.nds-t a GodMode9i archívból és rakd valahova az SD kártyádon

II. rész - Nintendo DSi lépések

  1. Indítsd el a GodMode9i-t
  2. Biztosítsd, hogy a játékkártya csatlakoztatott legyen a konzolra
  3. Válaszd az "NDS JÁTÉKKÁRTYA" opciót a GodMode9i-ben
  4. Válaszd ki amit dumpolni akarsz
    • A "Vágott" opciók a ROM-okhoz kisebb fájlt dumpolnak, ami SD kártya helyet takart meg, de nem fognak működni a legtöbb patch-el, mint példul a ROM hack-ek
  5. Ismételd meg a 2-4. lépéseket minden játék kártyára, amit szeretnél dumpolni

TIP

A dumpolt játék kártyák az sd:/gm9i/out mappában lesznek megtalálhatók.

- - - diff --git a/hu_HU/dumping-nand.html b/hu_HU/dumping-nand.html deleted file mode 100644 index 34fb3f0f9..000000000 --- a/hu_HU/dumping-nand.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - NAND dumpolása | DSi Útmutató - - - - -
DSi Útmutató

NAND dumpolása

Csatlakozz a DS⁽ⁱ⁾ Mode Hacking! Discord szerverhez az útmutató fejlesztéséhez és segítségért.

-

Ez az oldal a NAND mentés készítéséről szól, ami egy másolata a Nintendo DSi belső tárolójának. Ez a hiyaCFW telepítéséhez és a NO$gba-hoz és melonDS-hez DSi emulációhoz használható.

TIP

Legyél biztos benne, hogy az SD kártyán van legalább 250MB szabad hely, egyébként hibáüzenetbe fogsz futni a dumpTool-ban.

TIP

Erősen ajánlott, hogy végrehajtsd ezt. Egy NAND mentés használható visszaállítási pontjaként a jövőben, ha brickelődne az eszközöd.

I. rész - SD kártya telepítés

TIP

Ha már letöltötted a dumpTool-t az útmutató egy másik része alapján, akkor átugorhatod ezt a részt.

  1. Töltsd le a dumpToolmegnyitás új ablakban legfrissebb kiadását
  2. Rakd a dumpTool.nds-t bárhova az SD kártyádon

II. rész - A NAND dumpolása

  1. Indítsd el a dumpTool-t a TWiLight Menu++-on keresztül
  2. Nyomd meg az A gombot a Nintendo DSi-den a NAND dumpolás indításához
    • Egy NAND mentés általában 7 percig tart
  3. Ha a NAND mentés kész, nyomd meg a START gombot a Nintendo DSi-den, hogy kilép a dumpTool-ból
  4. Kapcsold ki a konzolodat és helyezd vissza az SD kártyádat az eszközödbe
  5. Tárold ezt a mentés egy biztonságos helyen, ahol nem veszted el
    • Ha lehet, több mentésed legyen különböző tároló eszközökön
    • Ha elmentetted máshová, törölheted az SD kártyádról

WARNING

Az SHA1 hash-e a nand.bin-nek nem fog egyezni a nand.bin.sha1 fájlban tárolt értékkel. Ez azért van, mert a dumpTool további adatokat ad hozzá a nand.bin-hez, amit no$gba láblécnek hívunk, miután az SHA1 hash kiszámításra került. Használhatod a hiyaCFW Helpermegnyitás új ablakban-t olyan másolat létrehozásához, amiben nincs benne ez a lábléc.

TIP

Folytatás az Unlaunch telepítésével (Opcionális)

- - - diff --git a/hu_HU/faq.html b/hu_HU/faq.html deleted file mode 100644 index d3e4c56b1..000000000 --- a/hu_HU/faq.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - GYIK | DSi Útmutató - - - - -
DSi Útmutató

GYIK

Csatlakozz a DS⁽ⁱ⁾ Mode Hacking! Discord szerverhez az útmutató fejlesztéséhez és segítségért.

-

Kell frissítenem a rendszert?

Nem ajánlott a DSi frissítése, ha nem tudod biztosan, hogy van-e rajta vásárolt DSiWare. Habár továbbra is folytatható az útmutató, ha így teszel, az egyetlen előnye a frissítésnek, a képesség, hogy elérd a Nintendo DSi Shop-ot, hogy újra letöltsd a már megvásárolt címeket. Minden más előny, mint például a Facebook integráció a Nintendo DSi Camera alkalmazásban már nem használható vagy nem fontos annyira, hogy igazolja a hátrányokat:

  • A rendszer frissítések telepítése alkalmanként brickeli a konzolokat, közel hasonló frekvenciával, mint az Unlaunch telepítése
  • A régi exploitok már nem használhatók, amik szükségesek lehetnek, ha nem tudod használni az ajánlott exploitokat
  • A flashcard kompatibilitás csökkentett, azonban ez megkerült, ha telepíted az Unlaunch-öt

Melyik a legjobb exploit?

Az Unlaunch a legjobb exploit a DSi-hez, az egyetlen hátránya, hogy van egy kicsi kockázata a brickelésnek a telepítéskor. Általában ajánlott, hogy a Mamory Pit-et használd az Unlaunch telepítéséhez. Ha szeretnél elkerülni bármilyen kockázatot, akkor ajánlott a Flipnote Lenny használata helyette, mert kevesebb homebrew problémája van mint a Memory Pit-nek, miközben ugyanannyira biztonságos és egyszerű eltávolítani. Alább az előnyök és hátrányok listája minden exploithoz:

Memory Pit

Előnyök:

  • Gyorsan és könnyen használható
  • Nincs kockázata a konzol sérülésének, az eltávolítás olyan egyszerű, mint kivenni az SD kártyát vagy letörölni egy fájl
  • Kompatibilis minden DSi konzollal, kivéve ha rossz a kamerája és még nem lett végrehajtva a kamera oktatóprogram

Hátrányok:

  • Szükség van a DSi Camera betöltésére minden alkalommal, amikor a homebrew-okat szeretnéd elérni
  • Inkompatibilis bizonyos DSi módú címekkel és homebrew-val azért mert a WRAM csak az ARM7 CPU számára nyitott
  • Hozzáférés a Slot-1-hez (a DS játék kártyához) blokkolt homebrew esetén
  • A hozzáférés a DSP-hez blokkolt, ezért rosszabb a hang a GBARunner2-ben
  • A fényképek az SD kártyán nem megtekinthetők a DSi Camera alkalmazásban, amíg a Memory Pit telepített, mert ez a trigger az exploithoz
    • Az egyetlen módja, hogy az SD kártyán található fotókat megtekintsd amíg a Memory Pit telepített, hogy elindítod a ROM dumpját a DSi Camera alkalmazásnak TWiLight Menu++-szal, hgy bootoljon nds-bootstrap-re (v0.61.3 vagy későbbi)

stylehax

Előnyök:

  • Jobb kompatibilitás a DSi módú címekkel és homebrew-okkal, mint a Memory Pit esetében
  • Könnyen használható
  • Nincs kockázata a konzol sérülésének
  • Használható hibás kamerával rendelkező konzolokon
  • Jobb hang a GBARunner2-ben

Hátrányok:

  • Internet hozzáférést igényel
  • Szükség van a DSi Browser betöltésére minden alkalommal, amikor a homebrew-okat szeretnéd elérni, ami kicsit több időt igényel, mint a Memory Pit
  • Hozzáférés a Slot-1-hez (a DS játék kártyához) blokkolt homebrew esetén

Flipnote Lenny

Előnyök:

  • Jobb kompatibilitás a DSi módú címekkel és homebrew-okkal, mint a Memory Pit esetében
  • Nincs kockázata a konzol sérülésének, az eltávolítás olyan egyszerű, mint kivenni az SD kártyát vagy letörölni egy mappát
  • Használható hibás kamerával rendelkező konzolokon
  • Jobb hang a GBARunner2-ben

Hátrányok:

  • Szükség van a Flipnote Studio betöltésére minden alkalommal, amikor a homebrew-okat szeretnéd elérni, ami kicsit több időt igényel, mint a Memory Pit
  • Hozzáférés a Slot-1-hez (a DS játék kártyához) blokkolt homebrew esetén

Unlaunch

Előnyök:

  • Lehetővé teszi Allows homebrew és DSiWare azonnali betöltését rendszer bootoláskor, opcionális gyorsgombokkal
  • Teljes hozzáférés a rendszerhez, korlátozások nélkül, beleértve:
    • Hozzáférés a Slot-1-hez, ami lehetővé teszi a játék kártyák dumpolását és inkompatibilis flashcard-ok betöltését
    • Jobb hang a GBARunner2-ben
  • A régió zárakat eltávolítja a DSi-Enchanced/Exkluzív játék kártyák esetében
  • Védelem a legtöbb lehetőség ellen, ami a DSi-t brickelheti
  • DSi-Enhanced játékok futhatnak DSi módban Donor ROM nélkül
  • Régi homebrew futtatható az nds-bootstrap-hb-n keresztül

Hátrányok:

  • Van egy nagyon kicsi kockázata a konzol brickelésének a telepítésekor
  • Egy másik kicsit magasabb kockázata van a brickelésnek, amikor eltávolítod
  • Nem kompatibilis fejlesztői konzolokkal

Vesztek el funkcionalitást, ha moddolom a rendszerem?

Ha telepíted az Unlaunch-öt vagy a Flipnote Lenny-t használod, nem vesztesz el funkcionalitást. Ha a Memory Pit-et használod, nem fogsz tudni fotókat megnézni az SD kártyáról a DSi Camera alkalmazással, kivéve ha egy DSi Camera ROM-ot indítasz aTWiLight Menu++ használatával, bootoljon be rá az nds-bootstrap használatával.

  • Ahhoz, hogy újra tudjál az SD kártyáról fotókat megtekinteni a DSi Camera indításakor, telepítsd az Unlaunch-öt vagy válts más exploitra és töröld a Memory Pit pit.bin fájlját
    • Ha a tip.bin létezik ugyanabban a mappában, nevezd vissza azt pit.bin-re

Hogyan játszhatok Nintendo DS játék kártya dumpokkal?

A játék kártya dump játékok használatához a konzolnak szüksége van flashcard-ra vagy nds-bootstrap-re, egy programra, ami lehetővé teszi, hogy a belső SD kártyáról játszhatók legyenek a játékok a Slot-1 írás és olvasás átirányításával.

  • A TWiLight Menu++-szal navigálhatsz az SD kártyádon, hogy megtaláld a ROM fájlokat, amiket nds-bootstrap-pel játszhatsz. A TWiLight Menu++ használatának előnye a csalás menü, a játékonkénti beállítások és hogy megkerüli a korlátozásokat, amikkel a forwarder-ek rendelkeznek. Más szavakkal, csak felmásolod a ROM fájlokat és játszhatsz velük bármilyen telepítés nélkül. Nincs 39 cím limit, sem hiyaCFW, sem Unlaunch nem szükséges és nincs korlátozás az SD kártya szabad tárhelyével kapcsolatosan sem
  • A hiyaCFW felhasználók létrehozhatnak forwarder-eket az SDNAND DSi Menu-be a DS-Homebrew Wiki DS játék forwarder-ekmegnyitás új ablakban útumutató használatával, de vannak korlátozásai. Van egy 39 címes limit és kevésbé kényelmes beállítani, mint használni a TWiLight Menu++-t

Hogyan tudom frissíteni a homebrew appjaim?

  • Unlaunch - Kövesd az útmutatót az Unlaunch telepítése oldalon
    • Nem kell eltávolítanod az Unlaunch-öt mielőtt ezt csinálod
  • hiyaCFW - Cseréld a hiya.dsi-t az SD kártyád gyökerében a legfrissebb kiadásbólmegnyitás új ablakban
  • TWiLight Menu++ - Kövesd a DS-Homebrew Wikimegnyitás új ablakban lépéseit
  • nds-bootstrap - Másold az nds-bootstrap-hb-release.nds & nds-bootstrap-release.nds fájlokat az _nds mappába, az SD kártyád gyökerében
    • Ha használsz TWiLight Menu++-t, erős rá az esély, hogy a legfrissebb nds-bootstrap kiadás is megtalálható a TWiLight Menu++-ban
  • GodMode9i, dumpTool, Forwarder3-DS, stb. - Kövesd azokat az útmutatókat ami alapján letöltötted őket

Más homebrew-ok elképzelhető, hogy más metódust használnak a frissítésre.

Új vagyok vagy szeretném újra csinálni a telepítést. Hol kezdjem?

  • Ha még nem módosítottad a konzolodat, vagy frissíteni szeretnéd az Unlaunch-öt a rendszereden, azt ajánljuk, hogy kezd az elejétől az útmutatót, követve az oldalakat. Legyél biztos abban, hogy mindent elolvastál a honlapon
  • Ha rendelkezel a legutolsó Unlaunch verzióval, kövesd a TWiLight Menu+ telepítési útmutatótmegnyitás új ablakban a TWiLight Menu++ rendszeredre telepítéséhez

Hogyan tudom eltávolítani a szülői felügyeletet?

Meg tudom változtatni a Nintendo DSi konzolom régióját?

Igen, néhány különböző metódus áll rendelkezésre, attól függően mit szeretnél változtatni:

Mi történt a hiyaCFW telepítési útmutatóval?

Mivel a hiyaCFW nem ad sok funkcionalitást és problémás és zavaró része volt az útmutatónak, átmozgatásra került a DS-Homebrew Wikimegnyitás új ablakban-be.

  • Ha linkelve lettél az oldalra egy másik útmutatóból, akkor a lépések amit követtél valószínűleg elavultak. Kérjük használd ezt az útmutatót helyette, mert folyamatosan karbantartott a projekt fejlesztői által

Milyen SD kártyát kell, hogy használjak?

  • Megbízható márkájú SD kártyát kell vásárolnod
  • Egy teljes méretű SD kártya vagy egy microSD kártya adapterrel is megfelelő
  • Bármilyen méret 1 GB és 2 TB között működni fog. Általános használatra 8 GB elég
    • Néhány szoftver, mint például a hiyaCFW, hosszabb töltési idővel rendelkezhet nagyobb SD kártya kapacitás esetén
  • 8-as sebesség osztályú vagy gyorsabb ajánlott

Használhatom a DSi SD kártyámat más rendszereken is?

Általában igen, két kivétellel:

  • A hiyaCFW csak azon a rendszeren fog működni, amin telepítve lett
  • Még ha nds-bootstrap-et vagy egy flashcard-ot is használsz, a friend code-ok az online NDS játékok esetében alaphelyzetbe állnak, ha megpróbálsz online lenni egy másik konzolon

Hogyan váltok egy új SD kártyára, miután beállítottam a homebrew-t?

Formázd az SD kártyát a SD kártya telepítés lépései alapján, majd egyszerűen mozgasd az adatod a régi SD kártyáról az újra.

Tudom használni a rendszeremet normálisan az SD kártya behelyezése nélkül, miután telepítettem a homebrew-t?

Igen. Ha nem telepíted az Unlaunch-öt, a rendszered teljesen módosítatlan marad. Ha did telepíted az Unlaunch-öt, szükséged lehet az Unlaunch beállítására, hogy automatikusan bootolj az eredeti DSi Menüre bizonyos kondíciók esetén.

Az Unlaunch oldalmegnyitás új ablakban azt mondja, hogy a 2.0 verzió nem tekinthető biztonságosnak. Javasolt helyette egy korábbi verzió használata?

Az Unlaunch oldal nem került frissítésre, mióta a 2.0 verzió kiadásra került, ami két évvel ezelőtt volt. A legtöbb felhasználó nem tapasztalt problémát ezzel a verzióval, így biztonságosnak tekinthető.

Hogyan futtathatok dumpolt DSiWare-t?

Az ajánlott módszer, hogy egyszerűen futtasd a TWiLight Menu++-szal az egyszerű húzd-és-vidd metódussal és nincs semmilen korlátja. Ha az nds-bootstrap a beállított indítási metódus, akkor még megkapja a csalások és a képernyőképek előnyeit és minden más előnyt ami a játékbani menüből érhető el.

Azonban a néhány inkompatibilis címhez használhatod az NTMmegnyitás új ablakban-et, hogy telepítsd őket vagy a belső memóriára vagy a hiyaCFW SDNAND-járamegnyitás új ablakban. Továbbá a fenti előnyök hiánya mellett a 39 címes limit is megmarad, amik nem léphetik től a 128 MiB/1,024 block méretet. A SysNAND esetén van egy nagyon kicsi rizikója a rendszer brickelésének, amikor az ír a belső NAND-ba.

- - - diff --git a/hu_HU/file-extensions-windows.html b/hu_HU/file-extensions-windows.html deleted file mode 100644 index 434b4bcc7..000000000 --- a/hu_HU/file-extensions-windows.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Fájlkiterjesztések (Windows) | DSi Útmutató - - - - -
DSi Útmutató

Fájlkiterjesztések (Windows)

Csatlakozz a DS⁽ⁱ⁾ Mode Hacking! Discord szerverhez az útmutató fejlesztéséhez és segítségért.

-

Ez egy kiegészítő rész, amelyben kikapcsoljuk a Windows azon alap viselkedését, hogy elrejti a fájlkiterjesztéseke, ami könnyebbé teszi számodra, hogy megtaláld a hivatkozott fájlokat.

  1. Nyiss meg bármilyen mappát, mint például az SD kártyád, hogy elindítsd a Fájlkezelőt
  2. A felső sávban válaszd a "Nézet" opciót
    • Ha az opció nem látható, kattints a ··· gombra a jobb szélén a felső sávnak
  3. Kattints vagy mozgasd a kurzort a Megjelenés > almenüre
  4. Pipáld be a Fájlnévkiterjesztések opciót Képernyőkép a "Fájl név kiterjesztések" jelölőnégyzetről Windows 11-en
  1. Nyiss meg bármilyen mappát, mint például az SD kártyád, hogy elindítsd a Fájlkezelőt
  2. A menüszalagon válaszd a "Nézet" opciót
  3. Pipáld be a "Fájlnév kiterjesztések" dobozt Képernyőkép a "Fájl név kiterjesztések" jelölőnégyzetről Windows 10-en
  1. Nyisd meg a Start menüt kattintással, vagy a Windows gombbal a billentyűzeteden
  2. Keress a "Mappabeállítások" kulcsszóra, majd válaszd ki a megfelelő találatot Képernyőkép a "mappa opciók" keresésésről a Windows 7 Start Menüben
  3. Válaszd a "Nézet" fület a Mappabeállítások ablak felső részén
  4. Biztosítsd, hogy az "Ismert fájltípusok kiterjesztésének elrejtése" ne legyen kipipálva Képernyőkép a "Mappa beállítások" ablakról Windows 7-en az "Ismert fájltípusok kiterjesztésének elrejtése" opció kikapcsolt állapotával
- - - diff --git a/hu_HU/get-started.html b/hu_HU/get-started.html deleted file mode 100644 index 36e3916bc..000000000 --- a/hu_HU/get-started.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Kezdeti lépések | DSi Útmutató - - - - -
DSi Útmutató

Kezdeti lépések

Csatlakozz a DS⁽ⁱ⁾ Mode Hacking! Discord szerverhez az útmutató fejlesztéséhez és segítségért.

-

A fő homebrew alkalmazás, amit ez az útmutató telepít a TWiLight Menu++, ami egy feljavítása/cseréje a Nintendo DSi Menu-nek, és ami lehetővé teszi más homebrew-ok, kereskedelmi DS játékok, más régebbi rendszerek emulátorainak és egyebeknek a futtatását.

A letöltésével fogunk kezdeni, illetve más homebrew eszköz(ök) letöltésével, hogy előkészüljünk az exploit lépéseire.

Követelmények

  • Egy mód arra, hogy a letöltött fájlokat az SD kártyádra másold
  • Egy alkalmazás, ami ki tud tömöríteni csomagolt állományokat, mint például a7-Zipmegnyitás új ablakban (Windows) vagy a The Unarchivermegnyitás új ablakban (macOS)
    • Azt tanácsoljuk, hogy ne használj WinRAR-t, mert ismert arról, hogy elront dolgokat

I. rész - Előkészületek

WARNING

Biztosítsd, hogy az SD kártyád megfelelően formázott legyen.

  1. Tedd be az SD kártyád a PC számítógépedbe
  2. Töltsd le a TWiLight Menu++megnyitás új ablakban legfrissebb kiadását
  3. Töltsd le a dumpToolmegnyitás új ablakban legfrissebb kiadását
  4. Másold ki az _nds mappát TWiLightMenu-DSi.7z fájlból az SD kártyád gyökerébe
  5. Másold ki a BOOT.NDS fájlt TWiLightMenu-DSi.7z fájlból az SD kártyád gyökerébe
  6. Másold a dumpTool.nds fájlt az SD kártyád gyökerébe

TIP

Nem tudod, mi az SD "gyökér"? Tekintsd meg ezt a képetmegnyitás új ablakban

II. rész - Az exploit kiválasztása

Innentől kezdve három lehetőséged van, egy kis különbséggel, hogy melyik mivel jár.

Az Unlaunch telepítése Memory Pit-tel

A Memory Pit egy exploit ami a DSi Camera-t használja és kompatibilis minden firmware verzióval. Opcionálisan, ez az exploit használható az Unlaunch telepítésére, ami egy bootcode exploit és teljes hozzáférést ad a konzolhoz bootoláskor.

A Memory Pit valamennyire korlátozott homebrew kompatibilitással rendelkezik, ajánlott, hogy telepítsd az Unlaunch-öt, a Memory Pit önálló használata helyett. Ez a legkönnyebb metódusa az Unlaunch telepítésének, így ez az ajánlott módja. Azonban van egy nagyon kicsi kockázata a konzolod brickelésének az Unlaunch telepítésekor, így ha ez számít, akkor válassz másik metódust alább.

TIP

Folytatás Az Exploit indítása útmutatóval

stylehax

A stylehax egy olyan exploit, ami a DSi Browser alkalmazást használja és alternatívaként használható a Memory Pit helyett az Unlaunch telepítéséhez (részletezve fentebb) ha a DSi-d kamerája hibás.

Az Unlaunch mentes élményhez ez az exploit ajánlott, mert a Memory Pit problémát okoz néhány játéknál vagy homebrew-nál.

TIP

Folytatás Az Exploit indítása (stylehax) útmutatóval

Flipnote Lenny

A Flipnote Lenny egy exploit ami a Flipnote Studio alkalmazást használja.

Ha van Flipnote Studio-d és nem tervezed az Unlaunch (fentebb bemutatva) telepítését, akkor ez az exploit ajánlott, ugyanazon okból, mint a stylehax.

Mindig teleptheted az Unlaunch-öt később, ha úgy döntenél, hogy szeretnéd.

TIP

Folytatás Az Exploit indítása (Flipnote Lenny) útmutatóval

Részletesebb előnyök és hátrányok összehasonltásért az elérhető exploitokról tekints meg a Melyik a legjobb exploit? GYIK-et.

- - - diff --git a/hu_HU/index.html b/hu_HU/index.html deleted file mode 100644 index 9747e68ef..000000000 --- a/hu_HU/index.html +++ /dev/null @@ -1,43 +0,0 @@ - - - - - - - - - DSi Útmutató | DSi Útmutató - - - - -
DSi Útmutató

DSi Útmutató

A Nintendo DSi moddolás teljes útmutatója

TIP

Más készülékekhez szóló teljes homebrew és egyedi firmware útmutatókért keresd fel a CFW.Guidemegnyitás új ablakban oldalt.

TIP

Alaposan olvasd végig az összes bevezető oldalt (beleértve ezt is) mielőtt bármibe belekezdenél.

Mi az a Homebrew?

A Homebrewmegnyitás új ablakban alkalmazások nem licencszelt szoftverek, zárt rendszerekre mint például a Nintendo DSi. Ezek az alkalmazások lehetnek segédeszközök, egyedi homebrew játékok.

Egy Homebrew ingyenesen futtatható bármilyen Nintendo DSi konzolon, függetlenül a firmware-től és a régiótól. Az egyetlen amire szükséged van egy belépési pont és egy SD kártya, amint a homebrew-ot tárolod. A fő belépési pont ebben az útmutatóban a Memory Pit, de léteznek más belépési pontok is, amit használhatsz, ha a Memory Pit nem elérhető számodra.

Mit tehetek a rendszerem moddolásával?

  • Futtathatsz Nintendo DS(i) játék mentéseket és ROM hackeket a DSi-d SD kártyájáról, a nélkül, hogy flashcard-ra lenne szükséged
  • Indíts bármilyen DSiWare-t az SD kártyádról
    • Ez azt jelenti, hogy a régiónk ívüli és 3DS-exklúzív DSiWare is működni fog
  • Bebootolhatsz DSiWare és homebrew alkalmazásokba a megfelelő gombok nyomva tartásával a Nintendo DSi bekapcsolásakor
  • Régi idők klasszikusait futtathatod különböző emulátorokkal
  • Használhatsz alaphelyzetben inkompatibilis flashcard-okat
  • Átirányíthatod a NAND-ot SD kártyára hiyaCFW-vel
  • Megtekintheted a kedvenc filmjeidet vagy a FastVideoDSPlayer vagy a tuna-viDS használatával
    • A FastVideoDSEncoder-nek olyan CPU-ra van szüksége, amely támogatja az AVX2-t (az új CPU-k valószínűleg támogatják)
  • Megjeleníthetsz egy képet (amire boot képernyőként hivatkozunk) a rendszer indulásakor
  • Játszhatsz homebrew játékokat

Hol találhatok homebrew alkalmazásokat?

Mit kell tudnom, mielőtt belekezdenék?

  • Windows-on ajánlott, hogy megjelenjenek a fájl kiterjesztések, ha az alapértelmezett Fájlkezelőt használod
  • Ez egyetlen brickelési kockázat az Unlaunch telepítésekor lehetséges, de a kockázat minimális

TIP

Folytasd a Kezdeti lépések-kel

- - - diff --git a/hu_HU/installing-unlaunch.html b/hu_HU/installing-unlaunch.html deleted file mode 100644 index 7e9459d1f..000000000 --- a/hu_HU/installing-unlaunch.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Unlaunch telepítése | DSi Útmutató - - - - -
DSi Útmutató

Unlaunch telepítése

Csatlakozz a DS⁽ⁱ⁾ Mode Hacking! Discord szerverhez az útmutató fejlesztéséhez és segítségért.

-

DANGER

Ha még nem tetted meg, kérjük készíts egy NAND mentést. Habár az esélyek kicsik, az Unlaunch brickelheti véletlenül a Nintendo DSi-det. Egy NAND mentés + hardmodmegnyitás új ablakban lehetővé teszi, hogy helyreállítsd ezt a mentést, ha tudod, hogy hogyan kell forrasztani.

WARNING

Biztosítsd, hogy a konzol legyen feltöltve, a következő folyamat alatt. Egy véletlen áram elvesztés komoly hibákhoz vezethet.

WARNING

Az Unlaunch nem kompatibilis a Nintendo DSi fejlesztői konzolokkal.

I. rész - SD kártya telepítés

  1. Töltsd le az Unlaunchmegnyitás új ablakban legfrissebb kiadását
  2. Csomagold ki az UNLAUNCH.DSI-t az unlaunch.zip archívból és rakd valahova az SD kártyádon
  3. Ellenőrizd, hogy még rajta van a TWiLight Menu++ az SD kártyádon

II. rész - Az Unlaunch telepítése/frissítése

  1. Indítsd el a TWiLight Menu++-t
    • Ha ez az első alkalom, hogy telepíted az Unlaunch-öt, indítsd újra a TWiLight Menu++-t az exploiton keresztül, amit használsz
    • Ha már telepítetted az Unlaunch-öt és frissíteni szeretnéd, tartsd nyomva az A + B gombokat, amíg bootolsz és válaszd a TWiLight Menu++ opciót
    • Ha több opció neve is TWiLight Menu++, válaszd azt az opciót, ahol a BOOT.NDS látható az útvonal végén az alsó képernyőn
  2. Indítsd el a TWiLight Menu++ Beállításokat
    • HA nem cserélted még a témádat, nyomj SELECT gombot és éríntsd meg a kis DS ikont az érintő képernyő alján. Egyéként tekintsd meg a TWiLight Menu++ kézikönyvet
  3. Nyomj L / R vagy X / Y gombokat, amíg el nem éred az Unlaunch Beállítások oldalt
  4. Ha szeretnéd cserélni az Unlaunch hátterét, válaszd a Háttér opciót és válaszd ki a neked tetszőt
  5. Lépj ki a TWiLight Menu++ Beállításokból
  6. A fájl navigáció menüből indítsd el az Unlaunch DSi Installer-t
    • Ha indítás után két fekete képernyőt látsz tölds le a GodMode9imegnyitás új ablakban-t és rakd a .dsi fájlját az SD kártya gyökerébe majd indítsd el a GodMode9i-t a TWiLight Menu++ használatával indítsd el az Unlaunch.dsi-t.
      Ez a metódus nem teszi lehetővé az Unlaunch-nek az egyedi patch-eket és az egyedi háttér beállítását
  7. Válaszd az "install now" opciót
    • Ha az Unlaunch lefagy az ERROR: MISMATCH IN FAT COPIES üzenetnél, tekintsd meg a Hibaelhárítás oldalt
  8. Ha végzett, indítsd újra a rendszered

Ha az Unlaunch Filemenu képernyőt látod ezen a ponton, akkor sikeresen moddoltad a Nintendo DSi-det.

III. rész - Unlaunch-utáni konfiguráció

Jelenleg az Unlaunch alapértelmezésben a Filemenu-t indítja bootoláskor, de ez módosítható bármire, amit szeretnél.

  1. Kapcsold be a konzolod, miközben nyomva tartod az A és B gombokat
    • Ez el kell indítsa az Unlaunch Filemenu-t
    • Ha csak a háttér látszik vagy nem jelenik meg fájl az SD kártyáról (például TWiLight Menu++), akkor újra kell formáznod az SD kártyát
  2. Navigálj az OPTIONS-höz és nézd meg az elérhető opciókat
    • A + B hardkódolt az Unlaunch menühöz, így az nem cserélhető
    • A NO BUTTON és BUTTON A / B / X / Y opciók beállíthatók, ahogy szeretnéd, hogy mit töltsön a DSi-d a bootolásnál, attól függően melyik gomb volt lenyomva. Kiválaszthatsz bármilyen DSiWare-t, homebrew-t, a Slot-1 kártyát vagy az Unlaunch Filemenu-t
      • A TWiLight Menu++-hoz válasz a TWiLight Menu++ opciót
      • Az eredeti DSi Menühöz, válaszd a Launcher-t
    • LOAD ERROR az, amit a DSi be fog tölteni, amikor amit beállítottál az hibára fut, mert például az SD kártya nem lett beillesztve
  3. Válaszd a SAVE & EXIT opciót a beállításaid mentéséhez, majd kapcsold ki a DSi konzolod

IV. rész - Takarítás az SD kártyán

TIP

Ez a rész opcionális és csak azt a célt szolgálja, hogy az SD kártyádon ne maradjon fájl, amire nincs szükséged.

  • Töröld az sd:/private/ds/app/484E494A/pit.bin fájlt az SD kártyádról
    • Ha a tip.bin még mindig létezik, nevezd vissza azt pit.bin-re
  • Most már visszaállíthatod a DCIM mappát, ami az SD kártyád göykerében volt, ha volt ilyen
  • Töröld az UNLAUNCH.DSI fájlt az SD kártyádról
  • Töröld a 800031_104784BAB6B57_000.ppm és a T00031_1038C2A757B77_000.ppm fájlokat a következő mappából:
    • sd:/private/ds/app/4B47554A/001 (Japán)
    • sd:/private/ds/app/4B475545/001 (USA)
    • sd:/private/ds/app/4B475556/001 (Europa/Ausztrália)
    • Törölheted az összes mappát a saját régiódón kívül is
  • Töröld az UNLAUNCH.DSI fájlt az SD kártyádról
- - - diff --git a/hu_HU/launching-the-browser-exploit.html b/hu_HU/launching-the-browser-exploit.html deleted file mode 100644 index 2a2e7ae48..000000000 --- a/hu_HU/launching-the-browser-exploit.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Az Exploit indítása (stylehax) | DSi Útmutató - - - - -
DSi Útmutató

Az Exploit indítása (stylehax)

Csatlakozz a DS⁽ⁱ⁾ Mode Hacking! Discord szerverhez az útmutató fejlesztéséhez és segítségért.

-

Az exploit indításával kezdjük. A legjobb Unlaunch-mentes élményhez vagy ha DSi camera sérült és az Unlaunch nem telepíthető, javasoljuk, hogy a "stylehax" exploitot használd, ami a DSi Browser alkalmazás a weboldalak kezelésében található egy hibáját használja.

Az exploit indítása a TWiLight Menu++-ba bootol, egy homebrew alkalmazásba, ami a DSi Menü cseréjeként szolgál.

Követelmények

  • Nintendo DSi Browser telepítve a Nintendo DSi-den
    • Ha nincsen DSi Browser-ed, használd a Memory Pit-et helyette

Az Exploit indítása

  1. Biztosítsd, hogy az SD kártyád bekerüljön a Nintendo DSi-dbe
  2. Bootold be a Nintendo DSi-d és indítsd el a DSi Browser alkalmazást
  3. Érintsd meg a Go to Page gombot
    • A gomb zöldwww ikonnal rendelkezik
  4. Írd be opera:about, majd éríntsd meg a Go-t az oldal betöltéséhez
  5. Érintsd meg a HOME ikont
  6. Érintsd meg a Go to Page gombot
  7. Írd be a stylehax.net címet, majd érintsd meg a Go-t az oldal betöltéséhez

TIP

Az exploitnak 21 másodperc szükséges a futáshoz. Ha több mint 30 másodpercig tart, bootolj újra és próbáld meg újra.

WARNING

Ha a felső képernyő zöldre vált, akkor nincs a TWiLight Menu++ BOOT.NDS fájlja az SD kártyád gyökerében. Hajtsd végre az előkészítő lépéseket újra.

Most már használhatod TWiLight Menu++-t! Először kérni fogja, hogy válassz nyelvet és régiót. Ezeknek nem kell egyezniük a konzolod nyelvével vagy régiójával, szóval állítsd őket arra, amik neked megfelelnek. Utána ajánlott, hogy folytasd és készíts egy NAND mentést. Ez potenciálisan használható lesz arra, hogy megmentsd a konzolod, ha valami rossz történne a jövőben.

TIP

Folytasd a NAND Dumpolásával

- - - diff --git a/hu_HU/launching-the-exploit.html b/hu_HU/launching-the-exploit.html deleted file mode 100644 index e70b74d9d..000000000 --- a/hu_HU/launching-the-exploit.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Az Exploit indítása | DSi Útmutató - - - - -
DSi Útmutató

Az Exploit indítása

Csatlakozz a DS⁽ⁱ⁾ Mode Hacking! Discord szerverhez az útmutató fejlesztéséhez és segítségért.

-

Először az SD kártyád állítjuk be az exploit futtatásához. A legtöbb felhasználónak a "Memory Pit" exploitot ajánljuk, ami a Nintendo DSi Camera alkalmazás kép metaadat kezelésének hibáját használja ki.

Az exploit indítása a TWiLight Menu++-ba bootol, egy homebrew alkalmazásba, ami a DSi Menü cseréjeként szolgál.

TIP

Ha nem tervezed az Unlaunch telepítését és van vagy DSi Browser-ed vagy Flipnote Studio-d, ajánlott vagy a stylehax vagy a Flipnote Lenny használata helyette. Melyik a legjobb exploit?

I. rész - DSi Camera verziójának ellenőrzése

  1. Kapcsold be a konzolod
  2. Nyisd meg a Nintendo DSi Camera alkalmazást
    • Ha még nem hajtottad végre a kamera oktatást, tedd meg
    • Ha a tutorial megjelenik és összeomlik, akkor a Nintendo DSi kamera hardvered valószínűleg hibás valamilyen módon és nem fogod tudni használni a Memory Pit-et. Használj egy alternatív exploitot
  3. Nyisd meg az albumot a nagy gombot használva a jobb oldalon
  4. Jegyezd meg, hogy van-e Facebook ikonod a csillagok, klubok és szívek mellett, ott ahol pirossal jelöltük: Képernyőkép arról, ahol a Facebook ikon megtalálható

II. rész - Memory Pit

  1. Töltsd le a megfelelő Memory Pit binárist a Nintendo DSi Camera verziódhoz:
  2. Navigálj az sd:/private/ds/app/484E494A/ mappába az SD kártyádon
    • Ha már létezik ez a könyvtár, korábban készítettél fotókat az SD kártyádra az Nintendo DSi Camera alkalmazással. Ha így van, nem kell törölnöd és újra létrehoznod
    • Ha nem létezik, hozd létre az egyes mappákat
  3. Ha már van egy pit.bin fájl ezen az útvonalon, nevezd át tip.bin-re
  4. Rakd a Memory Pit pit.bin fájlját ebbe a mappába
  5. Ha létezik mappa DCIM néven az SD kártya gyökerében, készts róla mentést, így nem veszted el belőle a képeket, majd töröld a mappát az SD kártyáról

III. rész - Az Exploit indítása

  1. Biztosítsd, hogy az SD kártyád bekerüljön a Nintendo DSi-dbe
  2. Bootold be a Nintendo DSi-d és indítsd el a Nintendo DSi Camera alkalmazást
  3. Válaszd az SD kártya ikont a jobb oldalt felül
    • Ha üzentet kapsz, hogy az SD kártya nincs berakva, használj másik SD kártyát
    • Ha üzentet kapsz, hogy az SD kártyád nem használható, biztosítsd, hogy az SD kártyád megfelelően formázott
  4. Nyisd meg az albumot a nagy gombot használva a jobb oldalon
    • Ha a képernyő magenta színnel villan, a Memory Pit megfelelően másolásra került

WARNING

Ha a felső képernyő zöldre vált, akkor nincs a TWiLight Menu++ BOOT.NDS fájlja az SD kártyád gyökerében. Hajtsd végre az előkészítő lépéseket újra.

WARNING

Ha beléptél az SD kártya kamera albumba és semmi szokatlan nem történt, ellenőrizd, hogy jó verzióját töltötted-e le a Memory Pit-nek, ami a verziódhoz és a régiódhoz tartozik és hogy jó mappába raktad-e az SD kártyádon. Továbbá győződj meg arról, hogy nincs DCIM mappa az SD kártyád gyökerében.

Most már használhatod a TWiLight Menu++-t! Először kérni fogja, hogy válassz nyelvet és régiót. Ezeknek nem kell egyezniük a konzolod nyelvével vagy régiójával, szóval állítsd őket arra, amik neked megfelelnek. Utána ajánlott, hogy folytasd és készíts egy NAND mentést. Ez potenciálisan használható lesz arra, hogy megmentsd a konzolod, ha valami rossz történne a jövőben.

TIP

Folytasd a NAND Dumpolásával

- - - diff --git a/hu_HU/launching-the-flipnote-exploit.html b/hu_HU/launching-the-flipnote-exploit.html deleted file mode 100644 index 574954277..000000000 --- a/hu_HU/launching-the-flipnote-exploit.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Az Exploit indítása (Flipnote Lenny) | DSi Útmutató - - - - -
DSi Útmutató

Az Exploit indítása (Flipnote Lenny)

Csatlakozz a DS⁽ⁱ⁾ Mode Hacking! Discord szerverhez az útmutató fejlesztéséhez és segítségért.

-

Először az SD kártyád állítjuk be az exploit futtatásához. A legjobb Unlaunch-mentes élményhez a "Flipnote Lenny" exploitot ajánljuk, ami a a Flipnote Studió flipnote kezelésében található hibát használja ki.

Az exploit indítása a TWiLight Menu++-ba bootol, egy homebrew alkalmazásba, ami a DSi Menü cseréjeként szolgál.

Követelmények

  • Telepített Flipnote Studio a Nintendo DSi-den
    • Ha nincsen Flipnote Studio-d, használd a Memory Pit-et helyette

I. rész - SD kártya telepítés

  1. Töltsd le az Flipnote Lennymegnyitás új ablakban legfrissebb kiadását
  2. Másold át a private mappát a Flipnote Lenny archívból az SD kártyád gyökerébe

II. rész - Az Exploit indítása

  1. Biztosítsd, hogy az SD kártyád bekerüljön a Nintendo DSi-dbe
  2. Bootold be a Nintendo DSi-d és indítsd el a Flipnote Studio alkalmazást
    • Ha üzentet kapsz, hogy az SD kártyád nem használható, biztosítsd, hogy az SD kártyád megfelelően formázott
  3. Nyisd meg a Flipnote Studio beállításait jobb oldalt felül a főmenüben, és ellenőrizd, hogy a Start on Calendar kikapcsolt és a Frog bekapcsolt
  4. Nyisd meg a flipnote-okat amik tárolva vannak az SD kártyán
    • Ha nem tudod megnézni a flipnote-okat az SD kártyán, használj egy másik SD kártyát
  5. Kattints a régiódnak megfelelő arcra
    • Ha AUS konzolod van, választ az EUR-t
  6. Szerkeszd a kiválasztott flipnote-ot
  7. Érintsd meg a béka ikon bal oldalt alul
  8. Érintsd meg a filmtekercs ikont
  9. Válaszd a Copy -> Back -> Exit opciókat
  10. Válaszd ki a második note-ot, amin nagyobb arc van és válaszd az Edit opciót
  11. Érintsd meg a béka ikon bal oldalt alul
  12. Érintsd meg a filmtekercs ikont
  13. Válaszd a beillesztést

WARNING

Ha a felső képernyő zöldre vált, akkor nincs a TWiLight Menu++ BOOT.NDS fájlja az SD kártyád gyökerében. Hajtsd végre az előkészítő lépéseket újra.

Most már használhatod TWiLight Menu++-t! Először kérni fogja, hogy válassz nyelvet és régiót. Ezeknek nem kell egyezniük a konzolod nyelvével vagy régiójával, szóval állítsd őket arra, amik neked megfelelnek. Utána ajánlott, hogy folytasd és készíts egy NAND mentést. Ez potenciálisan használható a konzolod megmentésére, ha bármi rossz történik a jövőben.

TIP

Folytatás a NAND Dumpolásával

- - - diff --git a/hu_HU/lazy-dsi-downloader.html b/hu_HU/lazy-dsi-downloader.html deleted file mode 100644 index e42934b57..000000000 --- a/hu_HU/lazy-dsi-downloader.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Lazy DSi Downloader | DSi Útmutató - - - - -
DSi Útmutató

Lazy DSi Downloader

Csatlakozz a DS⁽ⁱ⁾ Mode Hacking! Discord szerverhez az útmutató fejlesztéséhez és segítségért.

-

A "Lazy DSi Downloader" egy eszköz, ami egyszerűsíti a Nintendo DSi konzol moddolásának folyamatát.

Ellenőrzési lépések

  1. Kapcsold be Nintendo DSi-d
  2. Indítsd el a Nintendo DSi Camera alkalmazást

Ha ezen a ponton egy oktató anyagot kapsz és egy összeomlást, ha megpróbálod követni, akkor nem tudod használni a Memory Pit-et.

Telepítési útmutató

  1. Töltsd le a Lazy DSi File Downloadermegnyitás új ablakban az OS-ednek megfelelő legutolsó kiadását
  2. Indítsd el a kiadás oldalon található az operációs rendszerednek megfelelő lépések szerint
  3. Kattints a Next gombra
    • Az intro szöveget nem kötelező elolvasni
  4. Ha a Nintendo DSi-d összeomlott a korábbi ellenőrzési lépések során, kapcsold ki a Memory Pit opciót
  5. Jelöld be a "Download latest GodMode9i version?" opciót
    • Nyugodtan jelöl még be bármennyi homebrew alkalmazást a Click to add Additional homebrew... pontban, de ez nem kötelező
  6. Várj amíg minden letöltődik, majd nyomd meg a Finish-t
- - - diff --git a/hu_HU/restoring-nand.html b/hu_HU/restoring-nand.html deleted file mode 100644 index 0b4bb3e8c..000000000 --- a/hu_HU/restoring-nand.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - A NAND biztonsági másolat visszaállítása | DSi Útmutató - - - - -
DSi Útmutató

A NAND biztonsági másolat visszaállítása

Csatlakozz a DS⁽ⁱ⁾ Mode Hacking! Discord szerverhez az útmutató fejlesztéséhez és segítségért.

-

DANGER

FIGYELEM! Ez veszélyes. Még ha követed is pontosan a lépéseket, meg van a lehetősége annak, hogy brick-eled a DSi-t - mert a NAND nagyon alacsony minőségű - főleg akkor, ha többször flashelsz! Ezt az utolsó lehetőségként szabad csak használni!

TIP

Ne ugorj át semmit ezen az oldalon, bármi hiba erősen növeli a DSi-d brick-elésének esélyeit.

Először, pár biztonságos alternatíva, hogy miért érdemes ezt tenni:

  • DSiWare-ek telepítése történhet a hiyaCFW vagy a TWiLight Menu++ alkalmazással
  • A képek helyreállítása elvégezhető a ninfsmegnyitás új ablakban segítségével, kombinálva a a hiyaCFW vagy a TWiLight Menu++ alkalmazással, ha szeretnéd őket a konzolon. A HiyaCFW Helper legutolsó verziója lehetővé teszi, hogy kimásold a fotóid a NAND-ról az SDNAND-odra a telepítés során
  • Az Unlaunch gomb konfiguráció helyreállítás megtörténhet az Unlaunch menüből, ami a bekapcsoláskor nyomva tartott A + B gombokkal érhető el
  • Az Unlaunch-ba bootolás hibát adott? Vedd ki az SD kártyád és próbáld újra indítani a rendszered. Ha működik, akkor a hiba az SD kártyáddal van és a NAND mentés helyreállítása nem fogja javítani azt
  • Az "An error has occurred..." üzenet bootoláskor valószínűleg egy hiyaCFW hiba és nem kapcsolódik a NAND-hoz, lásd a hiyaCFW GYIK & hibaelhárításmegnyitás új ablakban oldalt a DS-Homebrew Wiki-n további információkért
  • Bármi hiba a TWiLight Menu++-ben nem kapcsolódik, meg kell próbálnod újra telepíteni a TWiLight Menu++-t vagy kérj segítséget a Discord szerverenmegnyitás új ablakban
  • Az Unlaunch eltávolítása, akár a NAND flashelésével vagy az uninstallerrel, kerülendő, amíg kifejezetten nem szükséges; beállíthatod az autoboot gombokat "Launcher"-re és a DSi-d olyan lesz mint a gyári

Az egyetlen dolog, amit a NAND-oddal kell tenned az az Unlaunch telepítése. Használd az alternatívakat egyébként.

Követelmények

A BIOS dumpolása a no$gba-ban történő használathoz

  1. Csomagold ki az dsibiosdumper.nds-t az dsibiosdumper.zip archívból és rakd valahova az SD kártyádon
  2. Kapcsold be a konzolod, miközben nyomva tartod az A és B gombokat
    • Ez el kell indítsa az Unlaunch Filemenu-t
  3. Indítsd el dsibiosdumper-t az Unlaunch Filemenu-ből
  4. Nyomj A gombot a BIOS SD kártyára dumpolásához
  5. Nyomj START gombot a dsibiosdumper-ből kilépéshez

A NAND mentésed tesztelése

Nagyon fontos, hogy teszteld a NAND mentésedet, hogy működik, mielőtt helyreállítod a konzolodra; ha brick hibát mutat a no$gba-ban, akkor jó eséllyel brick-eli a konzolodat is.

  1. Csomagold ki a NO$GBA.EXE-t az no$gba-w.zip archívból és rakd egy mappába a számítógépeden
  2. Másold a NAND mentésedet abba a mappába, ahova a NO$GBA.EXE-t raktad és nevezd át DSI-1.MMC-re
  3. Másold a bios7i.bin és a bios9i.bin fájlokat a mappába, ahova a NO$GBA.EXE-t raktad, nevezd őket BIOSDSI7.ROM és BIOSDSI9.ROM nevekre.
  4. Futtasd a NO$GBA.EXE fájlt
  5. Kattints az Options > Emulation Setup opciókra, hogy megnyisd az Emulation Setup ablakot
  6. Módosítsd a Reset/Startup Entrypoint-ot GBA/NDS BIOS (Nintendo logo)-ra
  7. Módosítsd az NDS Mode/Colors-t DSi (retail/16MB)-ra
  8. Kattints a Save Now-ra
  9. Indítsd el egy tetszőleges Nintendo DS ROM-ot (.nds fájl)

Ha a no$gba betölti a DSi menüt (vagy az Unlaunch Filemenu-t), folytasd a következő résszel. Ha bármilyen hibát ad ne flasheld a mentést!

Az Unlaunch eltávolítása a NAND mentésedből (opcionális)

Kövesd ezt, ha a NAND mentésed az után készítetted, hogy telepítetted az Unlaunch-öt és el szeretnéd távolítani az Unlaunch-öt a rendszeredről. Ha nem akard eltávolítani az Unlaunch-öt, nem kell végrehajtanod ezt a részt.

  1. Töltsd le az Unlaunchmegnyitás új ablakban legfrissebb kiadását
  2. Csomagold ki az UNLAUNCH.DSI-t az unlaunch.zip fájlból
  3. Töltsd be az UNLAUNCH.DSI-t a no$gba-ban és indítsd el a Game Card slot-ból
    • Ez el kell indítsa az Unlaunch telepítőt, ami hasonlóan néz ki, mint az Unlaunch Filemenu
  4. Válaszd az Uninstall-t
  5. Ha befejezte, válaszd a Power down-t
  6. Tölts be bármilyen Nintendo DS ROM-ot újra és ellenőrizd, hogy a DSi menüd betölts és megfelelően működik

Ha no$gba bármilyen problémát mutat, a DSi menü betöktése helyett, ne flash-eld a mentésed! Ha van egyrégebbi NAND mentésed, megpróbálhatod azt helyette. Ne próbáld meg eltávolítani az Unlaunch-öt az eltávolítóval (uninstaller) a konzolon, mert extrém nagy az esélye, hogy brick-eli a DSi-det.

A NAND mentés flashelése (szoftver)

DANGER

Legyél biztos abban, hogy elolvastad az előző lépéseket, mert itt válik a folyamat veszélyessé. Ha közvetlenül ide lettél linkelve, az előbbiek követése nélkül, menj vissza az oldal tetejére és olvasd el az egész oldalt.

DANGER

Legyél biztos abban, hogy Nintendo DSi rendszered rendesen fel van töltve, mielőtt elkezdenéd ezt a részt.

  1. Behelyezett SD kártyával kapcsold be a konzolod, miközben nyomva tartod az A és B gombokat
  2. Indítsd el a SafeNANDManager-t
  3. Nyomd meg a gombot, hogy elkezd a NAND visszaállítást
  4. Ha a visszaállítás végzett, nyomd meg a START gombot a DSi-d kikapcsolásáshoz

A NAND-od most már helyreállított kell legyen.

NAND mentés flashelése (Hardmod)

Ha nem tudsz bebootolni a Nintendo DSi-dbe, csak a hardmod megoldás a NAND visszaállítására mentésből. A legjobb útmutató erre a Nintendo DSi hardmod útmutató a DS-Homebrew Wikimegnyitás új ablakban-ben.

- - - diff --git a/hu_HU/sd-card-setup.html b/hu_HU/sd-card-setup.html deleted file mode 100644 index 2cf117eb8..000000000 --- a/hu_HU/sd-card-setup.html +++ /dev/null @@ -1,85 +0,0 @@ - - - - - - - - - SD kártya telepítés | DSi Útmutató - - - - -
DSi Útmutató

SD kártya telepítés

Csatlakozz a DS⁽ⁱ⁾ Mode Hacking! Discord szerverhez az útmutató fejlesztéséhez és segítségért.

-

Ez az oldal az SD kártyád előkészítéséről szól az eszközödhöz. A folyamat során formázzuk az SD kártyát, majd ellenőrizzük hibákra.

DANGER

Legyél biztos abban, hogy lementetted az SD kártyád tartalmát MIELŐTT követnéd a lépéseket. Az SD kártya WIPEOLVA lesz a folyamat során.

I. rész - Az SD kártya formázása az SD Formatter-rel

TIP

Ez a rész leformázza az SD kártyát az SD Card Association előírásai szerint. Ez javíthat számtalan problémát, ami homebrew alkalmazások futtatásakor előfordulhat.

DANGER

Bármilyen 64GB vagy nagyobb SD exFAT-ra lesz formázva ebben a folyamatban. Követned kell a II. részt a FAT32-re újra formázáshoz.

  1. Töltsd le az SD Formattermegnyitás új ablakban legfrissebb verzióját
  2. Futtasd az SD Card Formatter Setup-ot (az .exe fájlt) a letöltött .zip fájlból rendszergazda joggal a program telepítéséhez
  3. Futtasd az SD Card Formatter-t a Start menüből rendszergazda joggal
  4. Válaszd ki az SD kártyád
  5. Ellenőrizd, hogy a Quick Format opció be van-e pipálva
  6. Nyomd meg a Format gombot a formázás elindításához Képernyőkép a SD Card Formatter-ről Windows 11-en

II. rész - Az SD kártya formázása az SD GUIFormat-tal

Ez a rész 32 GB-nál nagyobb kártyák FAT32-re formázását írja le.

TIP

Ha az SD kártyád 32GB vagy kevesebb ugorj a III. részhez

  1. Töltsd le a GUIFormatmegnyitás új ablakban legfrissebb kiadását
    • Kattints a képre a weboldalon, hogy letöltsd az appot
  2. Futtasd a GUIFormat-ot Adminisztrátor joggal
  3. Válaszd ki az SD kártyád betűjelét
  4. Állítsd be az Allocation size unit-ot 32768-ra
    • Ha ez túl nagy az SD-d számára, állítsd a legnagyobbra ami működik
  5. Ellenőrizd, hogy a Quick Format opció be van-e pipálva
  6. Indíts el a formázást

III. rész - Ellenőrzés hibákra

  1. Menj a tulajdonságaihoz az SD kártyádnak
    • Windows Explorer -> Ez a gép -> Jobb kattintás az SD kártyádon -> Tulajdonságok
  2. Az eszközök fülön válaszd az Ellenőrzés most opciót
  3. Válaszd ki Fájl rendszer hibák automatikus javítása és Hibás szektorok kereséses és javítása opciókat egyaránt
  4. Indítsd el az ellenőrzési folyamatot

Ez ellenőrizni fogja az SD kártyádat és kijavít minden hibát, amit talál.

IV. rész - Az SD kártya írás/olvasás ellenőrzése

  1. Töltsd le és csomagold ki the h2testw archívotmegnyitás új ablakban bárhova a számítógépeden
  2. Az SD kártyád legyen beillesztve a gépbe, majd futtasd a h2testw.exe fájlt
  3. Válaszd ki milyen nyelven szeretnéd a h2testw-t látni
  4. Válaszd ki az SD kártyád betűjelét, mint célt
  5. Bizonyosodj meg róla, hogy az all available space van kiválasztva
  6. Kattints a Write + Verify gombra
  • Várj, amíg a folyamat befejeződik

TIP

Ha a teszt eredménye Test finished without errors, az SD kártyád hibátlan, és törölheted a .h2w fájlokat az SD kártyádról.

DANGER

Ha a teszt bármi más eredményt mutat, akkor az SD kártyád valószínűleg hibás, vagy sérült, és le kell cserélned!

TIP

Ha TWiLight Menu++ indtása sikertelen ezen metódus végrehajtása után, kérjük kövesd a Windows metódust helyett, vagy Windows-ra bootolással, vagy Windows virtuális gép használatával

I. rész - Az SD kártya formázása

  1. Ellenőrizd, hogy az SD kártyád nincs bedugva a Linux gépedbe
  2. Indítsd el a Linux Terminal-t
  3. Írd be a watch "lsblk" parancsot
  4. Helyezd az SD kártyád a Linux számítógépbe
  5. Figyeld a kimenetet. Valami hasonlót kell kapj:
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
-mmcblk0     179:0    0   3,8G  0 disk
-└─mmcblk0p1 179:1    0   3,7G  0 part /run/media/user/FFFF-FFFF
-
  1. Jegyezd fel az eszköz nevét. A fenti példában ez mmcblk0p1 volt
      • Ha az RO 1-re állított, ellenőrizd, hogy a zároló csúszka nincs-e lehúzva
    • Legyél biztos benne, hogy a megcélzott partíció, az mmcblk0p1 nem pedig az mmcblk0
  2. Nyomj CTRL + C-t a menüből kilépéshez
  3. Kövesd az SD kártyád kapacitásának megfelelő lépéseket:
      • 2GB vagy kisebb: sudo mkdosfs /dev/(az eszköz neve fentről) -s 64 -F 16
      • Ez létrehoz egy FAT16 partíciót 32 KB cluster mérettel az SD kártyán
      • 4GB vagy nagyobb: sudo mkdosfs /dev/(az eszköz neve fentről) -s 64 -F 32
      • Ez létrehoz egy FAT32 partíciót 32 KB cluster mérettel az SD kártyán

II. rész - Az F3 használata

  1. Töltsd le és csomagold ki az F3 archívotmegnyitás új ablakban bárhova a számítógépeden.
  2. Indítsd el a terminált az F3 könyvtárában
  3. Futtasd a make-et az F3 fordításához
  4. Bedugott és csatolt SD kártya mellett futtasd a következő parancsot: ./f3write <az sd kártyád csatolási pontja>
    • Várj, amíg a folyamat befejeződik. Alább egy példa kimenet látható:
    $ ./f3write /media/michel/6135-3363/
-Free space: 29.71 GB
-Creating file 1.h2w ... OK!
-...
-Creating file 30.h2w ... OK!
-Free space: 0.00 Byte
-Average Writing speed: 4.90 MB/s
-
  5. Futtasd a következő parancsot: ./f3write <az sd kártyád csatolási pontja>
  • Várj, amíg a folyamat befejeződik. Alább egy példa kimenet látható:
    $ ./f3read /media/michel/6135-3363/
-                  SECTORS      ok/corrupted/changed/overwritten
-Validating file 1.h2w ... 2097152/        0/      0/      0
-...
-Validating file 30.h2w ... 1491904/        0/      0/      0
-
-   Data OK: 29.71 GB (62309312 sectors)
-Data LOST: 0.00 Byte (0 sectors)
-            Corrupted: 0.00 Byte (0 sectors)
-   Slightly changed: 0.00 Byte (0 sectors)
-         Overwritten: 0.00 Byte (0 sectors)
-Average Reading speed: 9.42 MB/s
-

TIP

Ha a teszt eredménye Data LOST: 0.00 Byte (0 sectors), az SD kártyád rendben van és most már törölheted az összes .h2w fájlt róla.

DANGER

Ha a teszt bármi más eredményt mutat, akkor az SD kártyád valószínűleg hibás, vagy sérült, és le kell cserélned!

I. rész - Az SD kártya formázása az SD Formatter-rel

TIP

Ez a rész leformázza az SD kártyát az SD Card Association előírásai szerint. Ez javíthat számtalan problémát, ami homebrew alkalmazások futtatásakor előfordulhat.

DANGER

Bármilyen 64GB vagy nagyobb SD exFAT-ra lesz formázva ebben a folyamatban. Követned kell a II. részt a FAT32-re újra formázáshoz.

  1. Töltsd le az SD Formattermegnyitás új ablakban legfrissebb verzióját
    • Fogadd el a Végfelhasználói licencszerződést a letöltés indításához
  2. Futtasd az Install SD Card Formatter Setup-ot (az .mpkg fájlt) a letöltött .zip fájlból
  3. Futtasd az SD Card Formatter-t
  4. Válaszd ki az SD kártyád
  5. Ellenőrizd, hogy a Quick Format opció be van-e pipálva
  6. Indíts el a formázást

II. rész - Az SD kártyád formázása Disk Utility-vel

Ez a rész 32 GB-nál nagyobb kártyák FAT32-re formázását írja le.

TIP

Ha az SD kártyád 32GB vagy kevesebb ugorj a III. részhez.

OS X El Capitan (10.11) és későbbi

  1. Indítsd el a Disk Utility alkalmazást
  2. Válaszd a Show All Devices opciót a bal felső View panelen
  3. Válaszd ki az SD kártyád az oldalpanelen
    • Legyél biztos abban, hogy a jó meghajtót választod, egyébként rossz merevlemezt törölhetsz!
  4. Kattints az Erase-re felül
  5. Ellenőrizd, hogy a Format beállítása MS-DOS (FAT32)
    • El Capitan (10.11)-tól Catalina (10.15)-ig válaszd az MS-DOS (FAT) opciót
  6. Ellenőrizd, hogy a Scheme beállítása Master Boot Record
    • Ha a Scheme nem jelenik meg, nyomj Cancel-t és ellenőrizd, hogy az eszközt választottad-e ki egy kötet helyett
  7. Kattints az Erase-re, majd a Close-ra

OS X Yosemite (10.10) és korábbi

  1. Indítsd el a Disk Utility alkalmazást
  2. Válaszd ki az SD kártyád az oldalpanelen
    • Legyél biztos abban, hogy a jó meghajtót választod, egyébként rossz merevlemezt törölhetsz!
  3. Kattints az Partition-re felül
    • Ha a Partition nem jelenik meg, ellenőrizd, hogy az eszközt választottad-e ki egy kötet helyett
  4. Ellenőrizd, hogy a Partition Layout beállított 1 Partition-re
  5. Ellenőrizd, hogy a Format beállítása MS-DOS (FAT)
  6. Az Options gombnál (a partíciós tábla alatt), válaszd a Master Boot Record opciót.
  7. Kattintsd az OK -> Apply -> Partition opciókra

III. rész - Az F3 használata

  1. Nyisd meg a terminált
  2. Telepítsd az F3-t a brew-ból a brew install f3 futtatásával
  3. Bedugott és csatolt SD kártya mellett futtasd a következő parancsot: ./f3write <az sd kártyád csatolási pontja>
    • Várj, amíg a folyamat befejeződik. Alább egy példa kimenet látható:
    $ f3write /Volumes/SD\ CARD
-Free space: 29.71 GB
-Creating file 1.h2w ... OK!
-...
-Creating file 30.h2w ... OK!
-Free space: 0.00 Byte
-Average Writing speed: 4.90 MB/s
-
  4. Futtasd a következő parancsot: ./f3write <az sd kártyád csatolási pontja>
    • Várj, amíg a folyamat befejeződik. Alább egy példa kimenet látható:
    $ f3read /Volumes/SD\ CARD
-                  SECTORS      ok/corrupted/changed/overwritten
-Validating file 1.h2w ... 2097152/        0/      0/      0
-...
-Validating file 30.h2w ... 1491904/        0/      0/      0
-
-   Data OK: 29.71 GB (62309312 sectors)
-Data LOST: 0.00 Byte (0 sectors)
-            Corrupted: 0.00 Byte (0 sectors)
-   Slightly changed: 0.00 Byte (0 sectors)
-         Overwritten: 0.00 Byte (0 sectors)
-Average Reading speed: 9.42 MB/s
-

TIP

Ha a teszt eredménye Data LOST: 0.00 Byte (0 sectors), az SD kártyád rendben van és most már törölheted az összes .h2w fájlt róla.

DANGER

Ha a teszt bármi más eredményt mutat, akkor az SD kártyád valószínűleg hibás, vagy sérült, és le kell cserélned!

TIP

Most már helyreállíthatod az SD kártyád tartalmát és folytathatod.

- - - diff --git a/hu_HU/site-navigation.html b/hu_HU/site-navigation.html deleted file mode 100644 index f601c78fe..000000000 --- a/hu_HU/site-navigation.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Webhely navigáció | DSi Útmutató - - - - -
DSi Útmutató

Webhely navigáció

Csatlakozz a DS⁽ⁱ⁾ Mode Hacking! Discord szerverhez az útmutató fejlesztéséhez és segítségért.

-

- - - diff --git a/hu_HU/troubleshooting.html b/hu_HU/troubleshooting.html deleted file mode 100644 index b42d7116f..000000000 --- a/hu_HU/troubleshooting.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Hibaelhárítás | DSi Útmutató - - - - -
DSi Útmutató

Hibaelhárítás

Csatlakozz a DS⁽ⁱ⁾ Mode Hacking! Discord szerverhez az útmutató fejlesztéséhez és segítségért.

-

Unlaunch

Az Unlaunch lefagy a MISMATCH IN FAT COPIES üzenetnél

A twlnf-nek van egy kritikus hibája, amikor nem frissíti megfelelően az egész NAND-ot a módosítása után, ami bizonyos homebrew-ok esetén (mint példul az Unlaunch telepítő) hibát dob.

Ennek a javításához, niysd meg a NAND Title Manager (NTM)megnyitás új ablakban-t és válaszd a Fix FAT copy mismatch opciót.

Nincs hang vagy boot képernyő, amikor a "LAUNCHER" kerül indításra az Unlaunch-csel

Az Unlaunch fejlesztője (nocash) szándékosan kipatchelte alapértelmezésként háttérzenét és a boot képernyőt. Visszaszerezheted ezeket az effekteket az Unlaunch újratelepítésével a TWiLight Menu++-ban az Unlaunch beállítások oldalon "Indító patch"-ek "Alapértelmezett"-re állítását követően, vagy a hiyaCFWmegnyitás új ablakban használatával.

A bekapcsolás csak fekete képernyőt mutat az Unlaunch telepítése után

Vedd ki az SD kártyád és próbáld újra indítani a rendszered. Ha továbbra is fekete képernyőt mutat, lehet, hogy flash-elned kell a NAND-od hardmodmegnyitás új ablakban-on keresztül.

Az Unlaunch telepítése után beragadok egy alkalmazásba bootolásnál

Ez valószínűleg egy rossz app választása miatt van a NO BUTTON opciónál az Unlaunch-ben. Tartsd nyomva az A + B gombokat a konzol indításakor és menj az OPTIONS menübe, majd állítsd be a NO BUTTON opciót arra, amire szeretnéd.

Egyéb Unlaunch problémák

Ha az Unlaunch Clusters too large, Bad VBR, Bad MBR hibát jelenít meg vagy nem jelenít meg semmilyen alkalmazást, miközben az SD kártya behelyezett, az SD kártyád valószínűleg nem jól formázott. Kövesd újra az SD kártya telepítést.

TWiLight Menu++ hibaelhárítás

Az általános TWiLight Menu++ hibaelhárításhoz tekintsd meg a GYIK & hibaelhárításmegnyitás új ablakban oldalt a DS-Homebrew Wiki-n.

További segítség

Ha olyan hibába ütköztél, ami nincs megoldva itt, vagy egy olyanba, ami továbbra is fenn áll a megadott megoldások ellenére kérj segítséget a DS(i) Mode Hacking!megnyitás új ablakban Discord szerveren.

- - - diff --git a/hu_HU/uninstalling-unlaunch.html b/hu_HU/uninstalling-unlaunch.html deleted file mode 100644 index 030ed67c2..000000000 --- a/hu_HU/uninstalling-unlaunch.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Unlaunch eltávolítása | DSi Útmutató - - - - -
DSi Útmutató

Unlaunch eltávolítása

Csatlakozz a DS⁽ⁱ⁾ Mode Hacking! Discord szerverhez az útmutató fejlesztéséhez és segítségért.

-

DANGER

Az Unlaunch telepítése és eltávolítása random módon brickelheti a konzolodat! Figyelmeztetve lettél!

FIGYELEM: Az Unlaunch eltávolítása brick-elheti a Nintendo DSi-det. Itt van néhány eset, ami miatt arra gondolhatsz, hogy eltávolítsd az Unlaunch-öt de vannak más megoldások is, mint az eltávolítás.

  • Az Unlaunch háttér félelmetes: Telepítsd újra az Unlaunch-öt az új lépések alapján. Ezek már tartalmazzák a lépéseit a háttér csere módjának
  • Nincs kezdőképernyő és a zene hiányzik: Telepítsd újra az Unlaunch-öt az új lépések alapján. Most már tartalmaznak elhárítási lépéseket

WARNING

A brick-elés esélyeinek csökkentésére, legyél biztos abban, hogy nem telepítették nem-legális DSiWare-t a System NAND-odra (az SDNAND átirányítás, amit a hiyaCFW biztosít nem számít) vagy más módon módosított rendszer fájlokat.

WARNING

Ha eltávolítod az Unlaunch-öt, NEM szabad használnod a beépített eltávolítót közvetlenl a konzolodon, mert megvan az esélye, hogy brickeli a konzolt. Tekintsd át az alábbi információt a megfelelő eltávolításhoz.

Ha áttekintetted a fenti információt, kövesd a NAND mentése lépéseit, hogy egy új NAND mentést készíts, majd folytasd a NAND mentés helyreállításával. Ez az útmutató végig vezet az Unlaunch eltávolításán a NAND mentésből és annak flashelésén a konzolodra.

Ha nem tudod használni a no$gba-t vagy hibát kapsz az Unlaunch eltávolítását követőne a no$gba-ban, lehtséges egy NAND mentés flashelése, ami az Unlaucnh telepítése előtt készült (ha rendelkezel még ilyennel), azonban javasolt, hogy próbáld meg először egy NAND mentéssel ami körábban tartalmazott Unlaunch-öt. Ez a visszaállítást jelentősen könnyebbé teszi ha egy brick miatt szükséges a hardmod, mivel az Unlaunch benne hagyja a no$gba láblécet a NAND-ban akkor is, ha eltávolításra kerül.

- - - diff --git a/index.html b/index.html index b1dd2204b..58c8e50fa 100644 --- a/index.html +++ b/index.html @@ -3,7 +3,7 @@ - + - - Pagina non trovata | Guida DSi - - - - -
- - - diff --git a/it_IT/alternate-exploits.html b/it_IT/alternate-exploits.html deleted file mode 100644 index e55dc82c8..000000000 --- a/it_IT/alternate-exploits.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Exploit Alternativi | Guida DSi - - - - -
Guida DSi

Exploit Alternativi

Unisciti al server Discord DS⁽ⁱ⁾ Mode Hacking! per lo sviluppo di guide e aiuto.

-

Se si è stati introdotti ad un tutorial quando si avvia l'applicazione Fotocamera Nintendo DSi e si ottiene un crash quando si tenta di completarlo, non si può usare Memory Pit. Qui, si possono trovare exploit alternativi che possono funzionare al posto di Memory Pit.

Se hai installato Flipnote Studio, puoi usare Flipnote Lenny.

TIP

Assicurati di aver inserito TWiLightMenu++ nella tua scheda SD prima di procedere.

Se sei su un firmware vecchio, hai accesso a degli exploit che sfruttano i salvataggi dei giochi presenti in questa listaapri in nuova finestra. Quest'ultimi non verranno discussi qui, poiché sono per la maggior parte obsoleti. Dovrebbero essere utilizzati solamente come ultima risorsa, solo nel caso in cui sia Memory Pit che Flipnote Lenny non dovessero funzionare.

petit-compwner non sarà utilizzabile allo scopo di aggirare Memory Pit, in quanto richiede una fotocamera funzionante per avviare l'exploit.

- - - diff --git a/it_IT/credits.html b/it_IT/credits.html deleted file mode 100644 index 1af1011c9..000000000 --- a/it_IT/credits.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Crediti | Guida DSi - - - - -
Guida DSi

Crediti

Unisciti al server Discord DS⁽ⁱ⁾ Mode Hacking! per lo sviluppo di guide e aiuto.

-

Questi sono i crediti per coloro che hanno aiutato con il sito web della guida, homebrew e altre cose.

Se ti piace quello che hanno fatto, considera una donazione (se hanno un link di donazione).

Puoi contribuire anche alla nostra guida semplicemente inviando un pull requestapri in nuova finestra!

Se conosci altre lingue, puoi aiutarci traducendo la guida in quelle lingue. Puoi unirti al nostro Progetto Crowdinapri in nuova finestra per iniziare.

- - - diff --git a/it_IT/dsiware-backups.html b/it_IT/dsiware-backups.html deleted file mode 100644 index a3da191ea..000000000 --- a/it_IT/dsiware-backups.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Backup DSiWare | Guida DSi - - - - -
Guida DSi

Backup DSiWare

Unisciti al server Discord DS⁽ⁱ⁾ Mode Hacking! per lo sviluppo di guide e aiuto.

-

Requisiti

Nintendo DSi - Istruzioni

Sezione I - Dump dei DSiWare

  1. Avvia GodMode9i
  2. Premi START per aprire il menu START
  3. Seleziona Gestore titoli...
    • Se non appare, assicurarsi di avere la scheda SD e NAND montate. Se lo hai avviato da hiyaCFW, riavvialo da un'altra parte
  4. Seleziona il titolo di cui vuoi creare il dump
  5. Seleziona i dump da effettuare
  6. Ripeti i passaggi 4-5 per tutti i DSiWare di cui desideri effettuare un dump

TIP

I dump dei DSiWare sono trovati in sd:/gm9i/out.

- - - diff --git a/it_IT/dumping-game-cards.html b/it_IT/dumping-game-cards.html deleted file mode 100644 index 1b925a48b..000000000 --- a/it_IT/dumping-game-cards.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Dumping delle cartucce di gioco | Guida DSi - - - - -
Guida DSi

Dumping delle cartucce di gioco

Unisciti al server Discord DS⁽ⁱ⁾ Mode Hacking! per lo sviluppo di guide e aiuto.

-

Questa sezione riguarda il dumping delle cartucce utilizzando GodMode9i, per usarle su emulatori, flashcard o sulla scheda SD tramite nds-bootstrap.

Requisiti

  • La cartuccia di gioco del titolo che si desidera effettuare un dump
  • Una console Nintendo DSi con Unlaunch installato

Istruzioni

Sezione I - Configurazione della Scheda SD

  1. Scarica l'ultima versione di GodMode9iapri in nuova finestra
  2. Estrai GodMode9i.nds dall'archivio GodMode9i e mettilo in un percorso qualsiasi sulla scheda SD

Sezione II - Istruzioni Nintendo DSi

  1. Avvia GodMode9i
  2. Assicurati che la scheda di gioco sia inserita nella console
  3. Seleziona l'opzione "SCHEDA NDS" in GodMode9i
  4. Seleziona i dump da effettuare
    • Le opzioni "Trimmed" per la ROM scaricheranno un file più piccolo che può salvare lo spazio della scheda SD. tuttavia non funzioneranno per la maggior parte delle patch come le ROM hack
  5. Ripeti i passaggi 2-4 per tutte le cartucce di cui desideri effettuare un dump

TIP

I dump delle schede di gioco saranno trovati in sd:/gm9i/out.

- - - diff --git a/it_IT/dumping-nand.html b/it_IT/dumping-nand.html deleted file mode 100644 index 51c863646..000000000 --- a/it_IT/dumping-nand.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Effettuare dump della NAND | Guida DSi - - - - -
Guida DSi

Effettuare dump della NAND

Unisciti al server Discord DS⁽ⁱ⁾ Mode Hacking! per lo sviluppo di guide e aiuto.

-

Questa pagina riguarda la creazione di un backup della NAND, una copia dei dati della memoria interna del Nintendo DSi. Può essere usato per installare hiyaCFW, e per l'emulazione del DSi tramite no$gba e melonDS.

TIP

Assicurati che la scheda SD abbia almeno 1250MB di spazio libero, altrimenti riceverai un messaggio di errore da dumpTool.

TIP

Si consiglia vivamente di farlo. Un backup della NAND può essere utilizzato come punto di ripristino in futuro, nel caso in cui il DSi smetta di funzionare.

Sezione I - Configurazione della scheda SD

TIP

Se hai già scaricato dumpTool da un'altra sezione di questa guida, puoi saltare questa parte.

  1. Scarica l'ultima versione di dumpToolapri in nuova finestra
  2. Posiziona dumpTool.nds in un percorso qualsiasi sulla tua scheda SD

Sezione II - Dump della NAND

  1. Avvia dumpTool attraverso TWiLight Menu++
  2. Premi il pulsante A sul tuo Nintendo DSi per iniziare a creare un backup della NAND
    • Un backup della NAND richiede in genere circa 7 minuti
  3. Quando il backup della NAND è completato, premi il pulsante START sul tuo Nintendo DSi per uscire da dumpTool
  4. Spegni la console e inserisci la scheda SD nel tuo computer
  5. Salva questo backup in un posto sicuro, dove non lo perderai
    • Se possibile, effettua molteplici backup su diversi dispositivi di archiviazione
    • Una volta conservato il backup altrove, lo si può eliminare dalla scheda SD

WARNING

L'hash SHA1 di nand.bin non corrisponderà all'hash memorizzato in nand.bin.sha1. Questo accade poiché dumpTool aggiunge dei dati aggiuntivi, noti come footer NO$gba, al file nand.bin dopo che l'hash SHA1 è stato calcolato. È possibile utilizzare hiyaCFW Helperapri in nuova finestra per creare una copia senza il footer.

TIP

Continua con Installazione di Unlaunch (facoltativo)

- - - diff --git a/it_IT/faq.html b/it_IT/faq.html deleted file mode 100644 index 7b54cb957..000000000 --- a/it_IT/faq.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - FAQ | Guida DSi - - - - -
Guida DSi

FAQ

Unisciti al server Discord DS⁽ⁱ⁾ Mode Hacking! per lo sviluppo di guide e aiuto.

-

Devo aggiornare il sistema?

Non è consigliato aggiornare il tuo DSi a meno che non sai che ci sono DSiWare acquistati. Mentre è ancora possibile seguire questa guida se lo fai, l'unico vantaggio di aggiornare la console è la possibilità di accedere al Nintendo DSi Shop per scaricare i titoli già acquistati. Tutti gli altri vantaggi, come l'integrazione di Facebook nell'applicazione Fotocamera Nintendo DSi, non sono più utilizzabili o non sono sufficientemente significativi da giustificare gli aspetti negativi:

  • L'installazione di aggiornamenti di sistema è conosciuta per causare occasionalmente dei brick alle console, con approssimativamente la stessa frequenza di quando si installa Unlaunch
  • Gli exploit più vecchi non sono più possibili da usare, che potrebbero essere necessari se non sei in grado di utilizzare gli exploit consigliati
  • La compatibilità con le flashcard è minore, tuttavia questo è bypassato se si installa Unlaunch

Qual è l'exploit migliore?

Unlaunch è nel complesso il miglior exploit per il DSi, con l'unico lato negativo è che c'è un rischio minore di causare un brick all'installazione. In generale si consiglia di utilizzare Memory Pit per installare Unlaunch. Se desideri evitare qualsiasi rischio si consiglia invece di utilizzare Flipnote Lenny in quanto ha meno problemi in homebrew rispetto a Memory Pit mentre è altrettanto sicuro e semplice da rimuovere. Sotto c'è una lista di tutti i pro e i contro di ciascun exploit:

Memory Pit

Pro:

  • Facile e semplice da usare
  • Nessun rischio di danneggiare la console, la disinstallazione è talmente semplice che basta rimuovere la scheda SD o eliminare un file
  • Compatibile con tutte le console DSi a meno che non abbiano una fotocamera rotta e non abbiano completato il tutorial dellla fotocamera

Contro:

  • Richiede di aprire l'app Fotocamera Nintendo DSi ogni volta che si desidera accedere all'homebrew
  • Incompatibile con alcuni titoli in modalità DSi e applicazioni homebrew a causa di WRAM aperto solo alla CPU ARM7
  • L'accesso alla Slot-1 (la scheda di gioco DS) è bloccato con gli homebrew
  • L'accesso al DSP è bloccato e ciò comporta un peggioramento del suono in GBARunner2
  • Le foto sulla scheda SD non possono essere visualizzate tramite l'applicazione Fotocamera Nintendo DSi mentre Memory Pit è installato, dato che ciò attiverebbe l'exploit
    • L'unico modo per visualizzare le foto della scheda SD mentre Memory Pit è installato è tramite l'esecuzione di un dump della ROM dell'applicazione Fotocamera Nintendo DSi usando TWiLight Menu++ per avviarlo tramite nds-bootstrap (v0.61.3 o successive)

stylehax

Pro:

  • Migliore compatibilità con titoli e app homebrew in modalità DSi rispetto a Memory Pit
  • Facile da usare
  • Nessun rischio di danneggiare la console
  • Utilizzabile su console con fotocamera rotta
  • Audio migliore in GBARunner2

Contro:

  • Richiede accesso a internet
  • Richiede di aprire DSi Browser ogni volta che si desidera accedere all'homebrew, e ciò richiede un po' più di tempo rispetto a Memory Pit
  • L'accesso alla Slot-1 (la scheda di gioco DS) è bloccato con gli homebrew

Flipnote Lenny

Pro:

  • Migliore compatibilità con titoli e app homebrew in modalità DSi rispetto a Memory Pit
  • Nessun rischio di danneggiare la console, la disinstallazione è talmente semplice che basta rimuovere la SD o eliminare una cartella
  • Utilizzabile su console con fotocamera rotta
  • Audio migliore in GBARunner2

Contro:

  • Richiede di aprire Flipnote Studio ogni volta che si desidera accedere all'homebrew e ciò richiede poco più tempo di Memory Pit
  • L'accesso alla Slot-1 (la scheda di gioco DS) è bloccato con gli homebrew

Unlaunch

Pro:

  • Consente di aprire app homebrew e DSiWare immediatamente all'avvio del sistema, con tasti di scelta rapidi opzionali
  • Pieno accesso al sistema senza alcuna limitazione, tra cui:
    • Accesso alla Slot-1 che consente di eseguire i backup di schede di gioco e l'avvio di flashcard non compatibili
    • Audio migliore in GBARunner2
  • Rimuove i blocchi regionali sulle schede di gioco DSi-Enhanced/Esclusive DSi
  • Protezione contro la maggior parte dei modi con cui un DSi potrebbe rompersi
  • I giochi DSi-Enhanced possono essere eseguiti in modalità DSi senza una ROM donatrice
  • Vecchie app homebrew possono essere eseguite tramite nds-bootstrap-hb

Contro:

  • Un bassissimo rischio di rompere la console durante l'installazione
  • Un altro rischio, leggermente più alto, di rompere la console se si decide di disinstallarlo
  • Non compatibile con console di sviluppo

Perderò qualche funzionalità se modifico il mio sistema?

Se si installa Unlaunch o si usa Flipnote Lenny, non si perderà alcuna funzionalità. Se si usa Memory Pit, non sarà possibile visualizzare le foto sulla scheda SD utilizzando la fotocamera DSi, a meno che non avvii un dump ROM dell'applicazione Fotocamera Nintendo DSi utilizzando TWiLight Menu++ per avviarlo tramite nds-bootstrap.

  • Per recuperare la possibilità di visualizzare le foto salvate sulla scheda SD quando avvii la Fotocamera Nintendo DSi dal menu DSi installa Unlaunch o passa a un exploit differente, poi elimina il file pit.bin
    • Se tip.bin esiste ancora nella stessa cartella, rinominalo a pit.bin

Come faccio a giocare ai backup delle schede di gioco per Nintendo DS?

Giocare ai backup delle schede di gioco sulla console richiede l'uso di una flashcard o di nds-bootstrap, un programma che consente di riprodurre i giochi dalla scheda SD interna reindirizzando le scritture e le letture della Slot-1.

  • Con TWiLight Menu++ puoi navigare nella tua scheda SD per trovare i file ROM da avviare tramite nds-bootstrap. I vantaggi di utilizzare TWiLight Menu++ sono di avere un menu per i trucchi, impostazioni per gioco, e di evitare le restrizioni che le scorciatoie comportano. In altre parole, è possibile spostare i file ROM direttamente e giocare senza alcuna configurazione. Non c'è nessun limite di 39 titoli, né hiyaCFW o Unlaunch sono necessari e non ci sono restrizioni sullo spazio libero della scheda SD che si può avere
  • gli utenti di hiyaCFW possono creare scorciatoie per il menu DSi della SDNAND utilizzando la guida Scorciatoie per i giochi DSapri in nuova finestra sulla DS-Homebrew Wiki, ma hanno alcune limitazioni. C'è un limite non aggirabile di 39 titoli, e sono meno convenienti da creare rispetto all'uso di TWiLight Menu++

Come faccio ad aggiornare il mio homebrew?

  • Unlaunch - Segui le istruzioni sulla pagina Installazione di Unlaunch
    • Non devi disinstallare Unlaunch prima di farlo
  • hiyaCFW - Sostituisci hiya.dsi nella scheda SD con la versione aggiornataapri in nuova finestra
  • TWiLight Menu++ - Segui le istruzioni sulla DS-Homebrew Wikiapri in nuova finestra
  • nds-bootstrap - Copia nds-bootstrap-hb-release.nds & nds-bootstrap-release.nds nella cartella _nds sulla scheda SD
    • Se utilizzi TWiLight Menu++, c'è un'alta probabilità che l'ultima versione di nds-bootstrap sia inclusa con TWiLight Menu++
  • GodMode9i, dumpTool, Forwarder3-DS, ecc - Segui le istruzioni su come scaricarli

Altre app homebrew potrebbero usare altri metodi per essere aggiornate.

Sono nuovo o vorrei rifare la mia configurazione. Da dove inizio?

  • Se non hai già modificato la console o stai cercando di aggiornare Unlaunch sul tuo sistema, si consiglia di partire dall'inizio della guida e di seguirla attraverso le pagine. Assicurati di leggere tutto sulla pagina principale
  • Se hai l'ultima versione di Unlaunch, segui la guida per l'installazione di TWiLight Menu++apri in nuova finestra per installare TWiLight Menu++ sul tuo sistema

Come posso eliminare il filtro famiglia?

Posso cambiare la regione del mio Nintendo DSi?

Sì, ci sono alcuni metodi diversi a seconda di ciò che si desidera cambiare:

Cosa è successo alla guida all'installazione di hiyaCFW?

Poiché hiyaCFW non è molto pratico ed è stato un passaggio problematico e confusionario della guida per parecchi utenti, È stata spostata alla DS-Homebrew Wikiapri in nuova finestra.

  • Se sei stato collegato alla pagina in questione da un'altra guida, le istruzioni che stai seguendo sono obsolete. È consigliato invece di utilizzare questa guida, dato che viene aggiornata costantemente dagli sviluppatori di questi progetti

Che tipo di scheda SD dovrei utilizzare?

  • Dovresti acquistare una scheda SD di un marchio affidabile
  • Funzionerà sia una scheda SD sia una scheda microSD in un adattatore
  • Qualsiasi capacità compresa tra 1 GB e 2 TB andrà bene. Per un uso generale, 8 GB sono sufficienti
    • Con alcuni software, come hiyaCFW, si possono avere tempi di caricamento molto più lunghi con schede SD con capienze più grandi
  • Si raccomanda una classe di velocità 8 o superiore

Posso usare la mia scheda SD del DSi su altri sistemi?

Generalmente sì, ma con due eccezioni:

  • hiyaCFW funzionerà solo sul sistema su cui è stato configurato
  • Anche se stai usando nds-bootstrap o una flashcard, i codici amico dei giochi online NDS verranno reimpostati quando si tenta di andare online utilizzando una console diversa

Come posso passare a una nuova scheda SD dopo aver impostato gli homebrew?

Formatta la tua nuova scheda SD utilizzando le istruzioni Configurazione scheda SD, poi semplicemente sposta i dati dalla vecchia scheda SD a quella nuova.

Posso ancora usare il mio sistema normalmente senza la scheda SD inserita dopo aver impostato gli homebrew?

Sì. Se non è stato installato Unlaunch, il sistema rimarrà completamente non modificato. Se hai installato Unlaunch, potresti aver bisogno di configurare Unlaunch per avviare automaticamente il menu DSi originale in condizioni specifiche.

La pagina di Unlaunchapri in nuova finestra dice che la versione 2.0 non è notoriamente sicura. Dovrei usare una versione precedente?

La pagina di Unlaunch non è stata aggiornata da quando è stata rilasciata la versione 2.0, più di due anni fa. La stragrande maggioranza degli utenti non hanno problemi con questa versione, ed è perciò considerata sicura.

Come faccio ad avviare i dump dei DSiWare?

Il metodo consigliato è quello di avviarli semplicemente con TWiLight Menu++, a causa del semplice metodo trascina-e-rilascia e non ci sono limiti arbitrari. Quando nds-bootstrap è impostato come metodo di avvio, ottiene anche i benefici di trucchi e screenshot, così come qualsiasi altro vantaggio fornito dal menu in-gioco.

Tuttavia, per i pochi titoli che sono incompatibili, puoi usare NTMapri in nuova finestra per installarli su memoria interna o SDNANDapri in nuova finestra di hiyaCFW. Oltre alla mancanza dei benefici di cui sopra, vi è anche un limite di 39 titoli che non possono superare 128 MiB/1.024 blocchi di dimensione. Per SysNAND, c'è anche un rischio molto piccolo di causare un brick al sistema quando si scrive sulla NAND interna.

- - - diff --git a/it_IT/file-extensions-windows.html b/it_IT/file-extensions-windows.html deleted file mode 100644 index d93af3d8f..000000000 --- a/it_IT/file-extensions-windows.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Estensioni File (Windows) | Guida DSi - - - - -
Guida DSi

Estensioni File (Windows)

Unisciti al server Discord DS⁽ⁱ⁾ Mode Hacking! per lo sviluppo di guide e aiuto.

-

Questa è una sezione aggiuntiva per disabilitare il comportamento predefinito di Windows di nascondere le estensioni dei file, che renderà la ricerca dei file di riferimento nella guida molto più facile per voi.

  1. Avvia Esplora File aprendo una qualsiasi directory, come ad esempio quella della scheda SD
  2. Clicca sul menu "Visualizza" nella barra superiore
    • Se l'opzione non è presente, cliccare sul pulsante ·· sulla parte più destra della barra superiore
  3. Cliccare o spostare il cursore sul sottomenu Mostra >
  4. Controllare l'opzione etichettata Estensioni nome file Schermata della casella delle "Estensioni nomi file" su Windows 11
  1. Avvia Esplora File aprendo una qualsiasi directory, come ad esempio quella della scheda SD
  2. Clicca sul menu "Visualizza" nella barra superiore
  3. Spunta la casella denominata "Estensioni nomi file" Schermata della casella delle "Estensioni nomi file" su Windows 10
  1. Apri il menu start cliccandoci sopra o premendo il tasto Windows
  2. Cerca "Opzioni cartella" e seleziona il risultato corrispondente Schermata di una ricerca "opzioni cartella" nel menu Start di Windows 7
  3. Clicca sulla scheda "Visualizzazione" nella parte superiore della finestra Opzioni cartella
  4. Assicurati che la casella denominata "Nascondi estensioni per tipi di file conosciuti" non sia selezionata Schermata della finestra "Opzioni cartelle" su Windows 7 con "Nascondi estensioni per i tipi di file conosciuti" disattivato
- - - diff --git a/it_IT/get-started.html b/it_IT/get-started.html deleted file mode 100644 index c2b306740..000000000 --- a/it_IT/get-started.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Per iniziare | Guida DSi - - - - -
Guida DSi

Per iniziare

Unisciti al server Discord DS⁽ⁱ⁾ Mode Hacking! per lo sviluppo di guide e aiuto.

-

L'applicazione homebrew principale che installerai con questa guida è TWiLight Menu++, un aggiornamento/sostituzione del menu del Nintendo DSi che consente l'esecuzione di altre applicazioni homebrew, giochi commerciali per DS, emulatori di vecchie console e altro ancora.

Per prima cosa lo scaricheremo, insieme ad altre applicazione homebrew, in preparazione dell'esecuzione dell'exploit.

Requisiti

Sezione I - Preparazione

WARNING

Assicurati che la scheda SD sia formattata correttamente.

  1. Inserisci la scheda SD nel PC
  2. Scarica la versione più recente di TWiLight Menu++apri in nuova finestra
  3. Scarica la versione più recente di dumpToolapri in nuova finestra
  4. Copia la cartella _nds estratta da TWiLightMenu-DSi.7z nella root della scheda SD
  5. Copia il file BOOT.NDS estratto da TWiLightMenu-DSi.7z nella root della scheda SD
  6. Copia il file dumpTool.nds nella root della scheda SD

TIP

Non sai cosa sia la "root" della SD? Guarda questa immagineapri in nuova finestra

Sezione II - Scegliere l'exploit

Da qui hai tre opzioni, con una piccola differenza in ciò che ciascuna comporta.

Installazione di Unlaunch tramite Memory Pit

Memory Pit è un exploit che utilizza la Fotocamera Nintendo DSi, compatibile con tutte le versioni del firmware. Facoltativamente, questo exploit può essere utilizzato per installare Unlaunch, un exploit del bootcode che consente il pieno controllo della console all'avvio.

Poiché Memory Pit ha una compatibilità limitata con gli homebrew, si raccomanda di installare Unlaunch, invece di utilizzare Memory Pit in modo autonomo. Visto che questo è il metodo più semplice per installare Unlaunch, è perciò il percorso più consigliato. Tuttavia, c'è un rischio molto marginale di causare un brick della console durante l'installazione di Unlaunch, quindi se questo ti preoccupa, segui il metodo alternativo sottostante.

TIP

Continua con Avvio dell'exploit

stylehax

stylehax è un exploit che utilizza l'applicazione DSi Browser e può essere utilizzato come alternativa a Memory Pit per l'installazione di Unlaunch (spiegato sopra) nel caso in cui il DSi abbia la fotocamera rotta.

Questo exploit è raccomandato se non si vuole utilizzare Unlaunch, poiché l'utilizzo dell'exploit Memory Pit causa problemi in alcuni giochi e homebrew.

TIP

Continua con Avvio dell'exploit(stylehax)

Flipnote Lenny

Flipnote Lenny è un exploit che utilizza l'applicazione Flipnote Studio.

Se hai Flipnote Studio e non hai intenzione di installare Unlaunch (spiegato sopra), questo exploit è raccomandato per la stessa ragione di stylehax.

È sempre possibile installare Unlaunch più tardi se dovessi cambiare idea.

TIP

Continua con Avvio dell'exploit (Flipnote Lenny)

Per un confronto più dettagliato di pro e contro degli exploit disponibili, consulta Qual è l'exploit migliore? nelle FAQ.

- - - diff --git a/it_IT/index.html b/it_IT/index.html deleted file mode 100644 index 73a6de064..000000000 --- a/it_IT/index.html +++ /dev/null @@ -1,43 +0,0 @@ - - - - - - - - - Pagina principale | Guida DSi - - - - -
Guida DSi

Guida DSi

La guida completa per moddare il tuo Nintendo DSi

TIP

Per guide complete su homebrew e custom firmware per altri dispositivi, controlla CFW.Guideapri in nuova finestra.

TIP

Leggi attentamente tutte le pagine introduttive (compresa questa!) prima di procedere.

Cos'è l'homebrew?

Le applicazioni Homebrewapri in nuova finestra sono software senza licenza fatte per sistemi chiusi come il Nintendo DSi. Queste applicazioni possono variare dalle utility ai giochi custom homebrew.

L'Homebrew può essere eseguito gratuitamente su tutte le console Nintendo DSi, indipendentemente dalla versione del firmware o dalla regione. Tutto ciò di cui hai bisogno è un punto di ingresso e una scheda SD per memorizzare i tuoi homebrew. Il punto di entrata principale utilizzato in questa guida sarà chiamato Memory Pit, ma ce ne sono altri che si potrebbero utilizzare se Memory Pit è inutilizzabile.

Cosa posso fare moddando il mio sistema?

  • Avviare i backup dei giochi Nintendo DS(i) o ROM hacks dalla scheda SD del DSi senza la necessità di una flashcard
  • Avvia qualsiasi DSiWare dalla tua scheda SD
    • Questo significa che pure i DSiWare fuori regione ed esclusive 3DS funzioneranno
  • Avviare DSiWare e app homebrew tenendo premuti pulsanti specifici quando si accende il Nintendo DSi
  • Avvia classici dei vecchi tempi utilizzando vari emulatori
  • Usare flashcard normalmente incompatibili
  • Reindirizzare la NAND alla scheda SD utilizzando hiyaCFW
  • Guarda i tuoi film preferiti con FastVideoDSPlayer o tuna-viDS
    • FastVideoDSEncoder richiede una CPU che supporti AVX2 (le CPU più recenti dovrebbero supportarlo)
  • Mostrare un'immagine (definita come immagine d'avvio) all'avvio del sistema
  • Giocare a giochi homebrew

Dove posso trovare delle applicazioni homebrew?

Cosa dovrei sapere prima di iniziare?

  • Su Windows, si consiglia di mostrare le estensioni di file se si utilizza il File Explorer predefinito
  • L'unico rischio di rompere il DSi deriva dall'installazione di Unlaunch, ma il rischio è minimo

TIP

Continua a Per iniziare

- - - diff --git a/it_IT/installing-unlaunch.html b/it_IT/installing-unlaunch.html deleted file mode 100644 index 6a9223d1d..000000000 --- a/it_IT/installing-unlaunch.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Installazione di Unlaunch | Guida DSi - - - - -
Guida DSi

Installazione di Unlaunch

Unisciti al server Discord DS⁽ⁱ⁾ Mode Hacking! per lo sviluppo di guide e aiuto.

-

DANGER

Se non lo hai ancora fatto, sei pregato di seguire Effettuare dump della NAND. Nonostante le probabilità minime, Unlaunch potrebbe accidentalmente causare un brick al tuo Nintendo DSi. Un backup della NAND + un hardmodapri in nuova finestra ti permetterebbe di ripristinare questo backup, a condizione che tu sappia come saldare.

WARNING

Assicurati che la console sia carica quando si esegue questo processo. Uno spegnimento improvviso potrebbe causare gravi danni.

WARNING

Unlaunch non è compatibile con le console di sviluppo Nintendo DSi.

Sezione I - Configurazione della scheda SD

  1. Scarica l'ultima versione di Unlaunchapri in nuova finestra
  2. Estrai UNLAUNCH.DSI da unlaunch.zip e mettilo ovunque sulla tua scheda SD
  3. Verifica di avere ancora TWiLight Menu++ sulla tua scheda SD

Sezione II - Installazione/Aggiornamento di Unlaunch

  1. Avvia TWiLight Menu++
    • Se questa è la tua prima volta che installi Unlaunch, avvia TWiLight Menu++ attraverso l'exploit che hai utilizzato
    • Se hai già installato Unlaunch e stai cercando di aggiornarlo, tieni premuto A + B durante l'avvio e seleziona TWiLight Menu++
    • Se più opzioni sono etichettate TWiLight Menu++, seleziona l'opzione in cui BOOT. NDS è mostrato alla fine del percorso nella schermata inferiore
  2. Apri le impostazioni di TWiLight Menu++
    • Se non hai cambiato tema, premi SELECT e tocca la piccola icona del DS nella parte inferiore del touch screen. Altrimenti, consulta il Manuale di TWiLight Menu++
  3. Premi L / R o X / Y finché non raggiungi la pagina Impostazioni Unlaunch
  4. Se vuoi modificare l'immagine di sfondo di Unlaunch, fai clic su Sfondo e scegli quello che vuoi
  5. Esci dalle impostazioni di TWiLight Menu++
  6. Avvia Unlaunch DSi Installer dal menu di navigazione
    • Se vedi due schermate nere dopo l'avvio, scarica GodMode9iapri in nuova finestra, sposta il file .dsi nella root della scheda SD, avvia GodMode9i utilizzando TWiLight Menu++ e infine avvia Unlaunch.dsi
      Questo metodo non consente a Unlaunch di utilizzare patch e sfondi personalizzati
  7. Seleziona l'opzione d'installazione
    • Se Unlaunch si blocca a ERROR: MISMATCH IN FAT COPIES, si prega di dare un'occhiata alla pagina Risoluzione dei problemi
  8. Una volta completato, riavvia il sistema

Se vedi la schermata del menu di Unlaunch a questo punto, significa che hai modificato con successo il tuo Nintendo DSi.

Sezione III - Configurazione di Unlaunch

Attualmente, Unlaunch apre il suo menu all'avvio per impostazione predefinita, ma può essere cambiato aprendo all'avvio quello che vuoi.

  1. Accendi la console tenendo premuto A e B
    • Si dovrebbe avviare il menu di Unlaunch
    • Se viene mostrato solo lo sfondo, o se non viene visualizzato alcun file dalla scheda SD (es. TWiLight Menu++), allora avrai bisogno di riformattare la scheda SD
  2. Vai a OPTIONS, e guarda le opzioni disponibili
    • A + B è stato fatto in codifica fissa per avviarsi nel menu di Unlaunch, e perciò non può essere modificato
    • Le opzioni NO BUTTON e BUTTON A /B / X / Y possono essere impostate come preferisci e sceglieranno come caricare il tuo DSi all'avvio a seconda dei pulsanti che vengono premuti. Puoi selezionare qualsiasi DSiWare, homebrew, la scheda Slot-1, wifiboot, o il menu di Unlaunch
      • Per TWiLight Menu++, seleziona TWiLight Menu++
      • Per il menu DSi originale, seleziona Launcher
    • LOAD ERROR è quello che il tuo DSi caricherà se il caricamento di quello che hai impostato fallisce, come ad esempio se la scheda SD non viene inserita
  3. Seleziona SALVA ed ESCI per salvare le tue impostazioni, poi spegni il tuo DSi

Sezione IV - Pulizia della scheda SD

TIP

Questa sezione è facoltativa e serve solo per mantenere la scheda SD ordinata.

  • Elimina il file sd:/private/ds/app/484E494A/pit.bin dalla tua scheda SD
    • Se tip.bin esiste ancora, rinominalo a pit.bin
  • Puoi ripristinare la cartella DCIM che era nella root della scheda SD, se questa cartella esisteva
  • Elimina il file UNLAUNCH.DSI dalla tua scheda SD
  • Elimina i file 800031_104784BAB6B57_000.ppm e T00031_1038C2A757B77_000.ppm dall'interno delle seguenti cartelle:
    • sd:/private/ds/app/4B47554A/001 (Giappone)
    • sd:/private/ds/app/4B475545/001 (USA)
    • sd:/private/ds/app/4B475556/001 (Europa/Australia)
    • È inoltre possibile eliminare le cartelle per le altre regioni
  • Elimina il file UNLAUNCH.DSI dalla tua scheda SD
- - - diff --git a/it_IT/launching-the-browser-exploit.html b/it_IT/launching-the-browser-exploit.html deleted file mode 100644 index 045a5f14e..000000000 --- a/it_IT/launching-the-browser-exploit.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Avvio dell'exploit (stylehax) | Guida DSi - - - - -
Guida DSi

Avvio dell'exploit (stylehax)

Unisciti al server Discord DS⁽ⁱ⁾ Mode Hacking! per lo sviluppo di guide e aiuto.

-

Inizieremo con l'avvio dell'exploit. Se non vuoi utilizzare Unlaunch o se lo vuoi usare ma la fotocamera del DSi è rotta, si consiglia di utilizzare un exploit chiamato "stylehax" che sfrutta un difetto nel modo in cui l'applicazione DSi Browser gestisce le pagine web.

Una volta lanciato l'exploit, ci avvierà TWiLight Menu++, un'applicazione homebrew che funge da sostituto al menu DSi.

Requisiti

  • Nintendo DSi Browser installato sul Nintendo DSi

Avvio dell'exploit

  1. Assicurati che la scheda SD sia inserita nel tuo Nintendo DSi
  2. Avvia il Nintendo DSi e avvia l'applicazione DSi Browser
  3. Tocca il pulsante Vai alla pagina
    • Il pulsante avrà un'icona verde www
  4. Digita opera:about, e tocca Vai per caricare la pagina
  5. Tocca l'icona HOME
  6. Tocca il pulsante Vai alla pagina
  7. Digita stylehax.net, e tocca Vai per caricare la pagina

TIP

L'exploit dovrebbe richiedere 21 secondi per avere effetto. Se ci mette più di 30 secondi, allora riavvia e riprova.

WARNING

Se lo schermo superiore diventa verde, significa che non hai il file BOOT.NDS di TWiLight Menu++ nella root della tua scheda SD. Segui di nuovo la preparazione.

Ora puoi utilizzare TWiLight Menu++! Prima di tutto ti chiederà di selezionare la lingua e la regione. Non devono per forza combaciare con la lingua o la regione della console, perciò impostale a tuo piacimento. In seguito è fortemente consigliato fare un backup della NAND. Un backup della NAND è potenzialmente utilizzabile per salvare la tua console se si dovesse verificare qualcosa di negativo in futuro.

TIP

Continua a Effettuare un dump della NAND

- - - diff --git a/it_IT/launching-the-exploit.html b/it_IT/launching-the-exploit.html deleted file mode 100644 index d97ae1e81..000000000 --- a/it_IT/launching-the-exploit.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Avvio dell'exploit | Guida DSi - - - - -
Guida DSi

Avvio dell'exploit

Unisciti al server Discord DS⁽ⁱ⁾ Mode Hacking! per lo sviluppo di guide e aiuto.

-

Inizieremo configurando la tua scheda SD per avviare il nostro exploit. Per la maggior parte degli utenti, consigliamo di utilizzare un exploit chiamato "Memory Pit" che sfrutta un difetto nel modo in cui la fotocamera DSi gestisce i dati.

Una volta lanciato l'exploit, ci avvierà TWiLight Menu++, un'applicazione homebrew che funge da sostituto al menu DSi.

TIP

Se non hai intenzione di installare Unlaunch e hai o DSi Browser o Flipnote Studio, è consigliabile utilizzare stylehax o Flipnote Lenny invece. Qual è il miglior exploit?

Sezione I - Controllo della versione di Fotocamera Nintendo DSi

  1. Accendi la console
  2. Apri Fotocamera Nintendo DSi
    • Se ti viene chiesto di completare il tutorial della fotocamera, fallo
    • Se il tutorial si blocca mentre provi a completarlo, la tua fotocamera Nintendo DSi è probabilmente rotta in qualche modo e non potrai utilizzare Memory Pit. Utilizza un exploit alternativo
  3. Apri l'album usando il pulsante grande sulla destra
  4. Prendi nota se c'è un'icona di Facebook accanto a quella della stella, del fiore e del cuore, delineati in rosso qui: Screenshot di dove la versione del sistema è posizionata

Sezione II - Memory Pit

  1. Scarica il file corretto di Memory Pit a seconda della versione di Fotocamera Nintendo DSi:
  2. Entra nella cartella sd:/private/ds/app/484E494A/ della scheda SD
    • Avrai già questa directory se hai precedentemente salvato delle foto nella scheda SD attraverso l'applicazione Fotocamera Nintendo DSi. In tal caso, non è necessario eliminarla e ricrearla
    • Se non esiste, crea le cartelle manualmente
  3. Se c'è già un file pit.bin dentro quel percorso, rinominalo in tip.bin
  4. Copia il file Memory Pit pit.bin dentro questa cartella
  5. Se c'è una cartella chiamata DCIM nella root della scheda SD, creane un backup in modo da non perdere le immagini all'interno, dopodiché eliminala dalla scheda SD

Sezione III - Avvio dell'exploit

  1. Assicurati che la scheda SD sia inserita nel tuo Nintendo DSi
  2. Avvia il tuo Nintendo DSi e apri l'applicazione Fotocamera Nintendo DSi
  3. Seleziona l'icona della scheda SD in alto a destra
    • Se ricevi un messaggio che dice che la scheda SD non è inserita, utilizzane un'altra
    • Se ricevi un messaggio che dice che la scheda SD non può essere usata, assicurati che sia formattata correttamente
  4. Apri l'album usando il pulsante grande sulla destra
    • Lo schermo dovrebbe lampeggiare color magenta se Memory Pit è stato copiato correttamente

WARNING

Se lo schermo superiore diventa verde, significa che non hai il file BOOT.NDS di TWiLight Menu++ nella root della tua scheda SD. Segui di nuovo la preparazione.

WARNING

Se entri nel'album foto della scheda SD e non succede nulla d'insolito, assicurati di aver scaricato la corretta versione di Memory Pit per la tua versione e regione e di averla posizionata nella cartella corretta della scheda SD. Assicurati inoltre che la cartella DCIM non esista sulla tua scheda SD.

Ora puoi utilizzare TWiLight Menu++! Prima di tutto ti chiederà di selezionare la lingua e la regione. Non devono per forza combaciare con la lingua o la regione della tua console, perciò impostale a tuo piacimento. Successivamente, e fortemente consigliato di fare un backup della NAND. Un backup della NAND è potenzialmente utilizzabile per salvare la tua console se si dovesse verificare qualcosa di negativo in futuro.

TIP

Continua a Effettuare un dump della NAND

- - - diff --git a/it_IT/launching-the-flipnote-exploit.html b/it_IT/launching-the-flipnote-exploit.html deleted file mode 100644 index 9c750987e..000000000 --- a/it_IT/launching-the-flipnote-exploit.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Avvio dell'exploit (Flipnote Lenny) | Guida DSi - - - - -
Guida DSi

Avvio dell'exploit (Flipnote Lenny)

Unisciti al server Discord DS⁽ⁱ⁾ Mode Hacking! per lo sviluppo di guide e aiuto.

-

Inizieremo configurando la scheda SD per avviare l'exploit. Se non desideri installare Unlaunch, si consiglia di utilizzare l'exploit chiamato "Flipnote Lenny" che sfrutta un difetto nel modo in cui l'applicazione Flipnote Studio gestisce i flipnotes.

Una volta lanciato l'exploit, verrà avviato TWiLight Menu++, un'applicazione homebrew che funge da sostituto al Menu DSi.

Requisiti

  • Flipnote Studio installato sul Nintendo DSi
    • Se non hai Flipnote Studio, dovrai usare Memory Pit

Sezione I - Configurazione della scheda SD

  1. Scarica la versione più recente di Flipnote Lennyapri in nuova finestra
  2. Copia la cartella private estratta dall'archivio di Flipnote Lenny nella root della scheda SD

Sezione II - Avvio dell'exploit

  1. Assicurati che la scheda SD sia inserita nel Nintendo DSi
  2. Accendi il Nintendo DSi e avvia l'applicazione Flipnote Studio
  3. Apri le impostazioni di Flipnote Studio in alto a destra del menu principale e assicurati che Apri calendario all'avvio sia disabilitato e che Rana sia abilitata
  4. Visualizza i flipnote presenti nella scheda SD
    • Se non riesci a visualizzare i filpnote nella scheda SD, utilizzane un'altra
  5. Tocca il volto corrispondente alla regione del tuo sistema
    • Se hai una console AUS, seleziona EUR
  6. Modifica il flipnote selezionato
  7. Tocca l'icona della rana in basso a sinistra
  8. Tocca l'icona della pellicola cinematografica
  9. Seleziona Copia -> Indietro -> Esci
  10. Tocca sul secondo foglio con la faccia più grande, poi seleziona Modifica
  11. Tocca l'icona della rana in basso a sinistra
  12. Tocca l'icona della pellicola cinematografica
  13. Seleziona incolla

WARNING

Se lo schermo superiore diventa verde, significa che non hai il file BOOT.NDS di TWiLight Menu++ nella root della scheda SD. Segui di nuovo la preparazione.

Ora puoi utilizzare TWiLight Menu++! Prima di tutto chiederà di selezionare la lingua e la regione. Non devono per forza combaciare con la lingua o la regione della console, perciò impostale a tuo piacimento. In seguito è fortemente consigliato fare un backup della NAND. Un backup della NAND è potenzialmente utilizzabile per salvare la tua console se si dovesse verificare qualcosa di negativo in futuro.

TIP

Continua con Effettuare dump della NAND

- - - diff --git a/it_IT/lazy-dsi-downloader.html b/it_IT/lazy-dsi-downloader.html deleted file mode 100644 index 0d8ecf541..000000000 --- a/it_IT/lazy-dsi-downloader.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Lazy DSi Downloader | Guida DSi - - - - -
Guida DSi

Lazy DSi Downloader

Unisciti al server Discord DS⁽ⁱ⁾ Mode Hacking! per lo sviluppo di guide e aiuto.

-

"Lazy DSi Downloader" è uno strumento che serve a semplificare il modding delle console Nintendo DSi.

Passaggi di verifica

  1. Accendi il tuo Nintendo DSi
  2. Apri l'applicazione Fotocamera Nintendo DSi

Se a questo punto il tutorial si arresta in modo anomalo mentre cerchi di completarlo, allora non puoi utilizzare Memory Pit.

Guida di configurazione

  1. Scarica la versione più recente di Lazy DSi File Downloaderapri in nuova finestra per il tuo sistema operativo
  2. Avvialo tramite le istruzioni per il tuo sistema operativo elencate nella pagina di rilascio
  3. Premi il pulsante "Next"
    • La lettura del testo iniziale non è obbligatoria
  4. Se si verifica un arresto anomalo del Dsi durante i passaggi di verifica, disattiva l'opzione Memory Pit
  5. Seleziona le caselle per "Download latest GodMode9i version?"
    • Sentiti libero di selezionare qualsiasi altra applicazione homebrew di Click to add Additional homebrew..., ma non è obbligatorio
  6. Aspetta che i download finiscano, poi premi "Finish"
- - - diff --git a/it_IT/restoring-nand.html b/it_IT/restoring-nand.html deleted file mode 100644 index 6babad462..000000000 --- a/it_IT/restoring-nand.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Ripristino di un backup della NAND | Guida DSi - - - - -
Guida DSi

Ripristino di un backup della NAND

Unisciti al server Discord DS⁽ⁱ⁾ Mode Hacking! per lo sviluppo di guide e aiuto.

-

DANGER

ATTENZIONE! Questo processo è potenzialmente pericoloso. Anche seguendo questi passaggi esattamente c'è ancora il potenziale di causare un brick ak DSi, poiché la sua NAND è di qualità molto bassa, soprattutto se si effettuano flash più volte! Questo procedimento dovrebbe essere usato solo come ultima risorsa!

TIP

Non saltare niente in questa pagina, visto che qualsiasi errore aumenta notevolmente le possibilità di causare un brick al tuo DSi.

In primis, alcune alternative più sicure per le ragioni che portano al voler fare questo:

  • L'installazione di DSiWare può essere eseguita utilizzando hiyaCFW o TWiLight Menu++
  • Le immagini possono essere recuperate usando ninfsapri in nuova finestra, insieme a hiyaCFW o TWiLight Menu++ se le vuoi su console. L'ultima versione di HiyaCFW Helper ti permette di copiare le tue foto dalla NAND alla SDNAND durante la configurazione
  • Si può ripristinare la configurazione dei pulsanti di Unlaunch dal menu, a cui è possibile accedere tenendo premuto A + B durante l'accensione della console
  • Avviare Unlaunch risulta in un errore? Estrai la scheda SD e prova a riavviare il sistema. Se funziona, allora è un difetto con la scheda SD e il ripristino di un backup della NAND non lo risolverà
  • "Si è verificato un errore..." all'avvio è un errore di hiyaCFW e non è relativo alla tua NAND, consulta la pagina FAQ e risoluzione dei problemi di hiyaCFWapri in nuova finestra sulla DS-Homebrew Wiki per maggiori informazioni
  • Eventuali errori in TWiLight Menu++ non sono correlati e dovresti provare a reinstallare TWiLight Menu++ o chiedere aiuto su Discordapri in nuova finestra
  • La disinstallazione di Unlaunch, che sia facendo un flash alla NAND oppure usando il suo disinstallatore, deve essere evitata a meno che non sia assolutamente necessaria, è possibile impostare le key autoboot su "Launcher" e il tuo DSi sarà come se fosse di fabbrica

L'unica cosa che dovresti fare con la tua NAND è installare Unlaunch. Altrimenti usa le alternative.

Requisiti

Fare un dump della BIOS per utilizzarlo in no$gba

  1. Estrai dsibiosdumper.nds dall'archivio dsibiosdumper.zip e posizionalo ovunque sulla tua scheda SD
  2. Accendi la console tenendo premuto A e B
    • Questo dovrebbe avviare il menu di Unlaunch
  3. Avvia dsibiosdumper tramite il menu di Unlaunch
  4. Premi A per scaricare la BIOS sulla scheda SD
  5. Premi START per uscire da dsibiosdumper

Testare il backup della NAND

È molto importante verificare che il backup della NAND funzioni prima di tentare di ripristinarlo sulla tua console, visto che se mostra un errore di brick in no$gba allora molto probabilmente ne causerà uno pure alla tua console.

  1. Estrai NO$GBA.EXE da no$gba-w.zip in una cartella sul tuo computer
  2. Copia il tuo backup della NAND nella cartella in cui hai inserito NO$GBA.EXE e rinominalo in DSI-1.MMC
  3. Copia bios7i.bin e bios9i.bin nella cartella in cui hai messo NO$GBA.EXE, rinominati rispettivamente in BIOSDSI7.ROM e BIOSDSI9.ROM.
  4. Avvia NO$GBA.EXE
  5. Clicca su Options > Emulation Setup per aprire la finestra Emulation Setup
  6. Cambia Reset/Startup Entrypoint in GBA/NDS BIOS (Nintendo logo)
  7. Cambia NDS Mode/Colors in DSi (retail/16MB)
  8. Clicca Save Now
  9. Avvia qualsiasi ROM Nintendo DS (file .nds)

Se no$gba carica il menu del DSi (o il menu di Unlaunch), allora continua alla sezione successiva. Se mostra qualsiasi tipo di errore, non fare un flash a quel backup!

Disinstallazione di Unlaunch dal backup della tua NAND (facoltativo)

Segui questa sezione se hai eseguito il dump del backup della tua NAND dopo aver installato Unlaunch e volessi disinstallarlo dal sistema. Se non vuoi disinstallare Unlaunch, non devi seguire questa sezione.

  1. Scarica l'ultima versione dell'installer di Unlaunchapri in nuova finestra
  2. Estrai UNLAUNCH.DSI da unlaunch.zip
  3. Avvia UNLAUNCH.DSI su no$gba e avvialo dallo slot delle cartucce di gioco
    • Dovrebbe avviare l'installer di Unlaunch, che assomiglia al menu di Unlaunch
  4. Seleziona Uninstall
  5. Una volta completato, seleziona Power down
  6. Avvia qualsiasi ROM per Nintendo DS e assicurati che il menu del DSi si avvii e funzioni correttamente

Se no$gba mostra qualsiasi tipo di errore invece di caricare il menu DSi, non fare un flash a quel backup! Se hai un backup della NAND più vecchio, potresti voler provare a usare quello. Non provare a disinstallare Unlaunch usando il suo disinstallatore sulla console, visto che è molto probabile che causi un brick al tuo DSi.

Flash del backup della NAND (Software)

DANGER

Assicurati di aver letto i passaggi sopra visto che è qui che diventa pericoloso. Se ti sei collegato qui direttamente senza seguire quanto scritto sopra, allora torna in alto e leggi l'intera pagina.

DANGER

Assicurati che il tuo sistema Nintendo DSi sia ben caricato prima di iniziare questa sezione.

  1. Con la scheda SD inserita, accendi il tuo Nintendo DSi tenendo premuto A e B
  2. Avvia SafeNANDManager
  3. Premi il pulsante per avviare il ripristino della NAND
  4. Una volta terminato il ripristino, premi START per spegnere il tuo DSi

La tua NAND dovrebbe ora essere ripristinata.

Flash del backup della NAND (Hardmod)

Se non riesci ad avviare il tuo Nintendo DSi, un hardmod è l'unico modo per ripristinare un backup della NAND. La migliore guida che attualmente esiste è quella sulla DS-Homebrew Wikiapri in nuova finestra.

- - - diff --git a/it_IT/sd-card-setup.html b/it_IT/sd-card-setup.html deleted file mode 100644 index a45c5d00f..000000000 --- a/it_IT/sd-card-setup.html +++ /dev/null @@ -1,85 +0,0 @@ - - - - - - - - - Configurazione Scheda SD | Guida DSi - - - - -
Guida DSi

Configurazione Scheda SD

Unisciti al server Discord DS⁽ⁱ⁾ Mode Hacking! per lo sviluppo di guide e aiuto.

-

Questa pagina serve a preparare la scheda SD per il tuo dispositivo. In questo processo, formatteremo la scheda SD e controlleremo la presenza di errori.

DANGER

Assicurarsi di eseguire il backup dei contenuti della scheda SD PRIMA di seguire la guida. La tua scheda SD verrà FORMATTATA e i file dentro essa verrano eliminati nel processo.

Sezione I - Formattazione della scheda SD con SD Formatter

TIP

Questa sezione serve per formattare la scheda SD secondo le specifiche della SD Card Association. Questo serve a risolvere problemi che potrebbero verificarsi con l'esecuzione di applicazione homebrew.

DANGER

Tutte le schede SD da 64GB o più saranno formattate in exFAT con questo processo. Devi seguire la Sezione II per riformattare in FAT32.

  1. Scarica la versione più recente di SD Formatterapri in nuova finestra
  2. Esegui SD Card Formatter Setup (il file .exe) nel file .zip scaricato, con i privilegi Amministratore, quindi installa il programma
  3. Esegui SD Card Formatter dal Menu Start con i privilegi Amministratore
  4. Seleziona la tua scheda SD
  5. Assicurati che la casella Quick Format sia spuntata
  6. Premi Format per avvuare il processo di formattazione Schermata della formattazione della scheda SD su Windows 11

Sezione II - Formattazione della scheda SD con GUIFormat

Questa sezione serve per formattare schede SD più grandi di 32GB in FAT32.

TIP

Se la tua scheda SD ha una capacità di 32GB o meno, salta questa sezione e vai alla Sezione III.

  1. Scarica la versione più recente di GUIFormatapri in nuova finestra
    • Clicca sulla foto nel sito per scaricare l'applicazione
  2. Esegui GUIFormat con i permessi dell'amministratore
  3. Seleziona la lettera del drive
  4. Imposta l'unità di dimensioni di allocazione a 32768
    • Se questa impostazione è troppo grande per la tua SD, seleziona quella più alta possibile
  5. Assicurati che la casella Quick Format sia spuntata
  6. Avvia il processo di formattazione

Sezione III - Controllo degli errori

  1. Vai alla finestra delle proprietà della scheda SD
    • Windows Explorer -> Questo PC -> Clicca con il tasto destro sulla tua scheda SD -> Proprietà
  2. Nella scheda "tools", seleziona Check Now
  3. Seleziona sia Automatically fix file system errors che Scan for and attempt recovery of bad sectors
  4. Avvia il processo di controllo

Questo processo esegue la scansione della scheda SD per correggere eventuali errori.

Sezione IV - Controllo lettura/scrittura della scheda SD

  1. Scarica ed estrai l'archivio h2testwapri in nuova finestra ovunque sul tuo computer
    • Se il link qui sopra non ti funziona, scarica da archive.orgapri in nuova finestra
    • Può anche essere estratto su un dispositivo esterno purché quel dispositivo esterno non sia la scheda SD
  2. Con la scheda SD inserita nel computer, esegui h2testw.exe
  3. Seleziona in quale lingua vuoi vedere h2testw
  4. Imposta la lettera di unità della tua scheda SD come obiettivo
  5. Assicurati che all available space sia selezionato
  6. Clicca Write + Verify
  • Attendere fino al completamento del processo

TIP

Se il test mostra il risultato Test finito senza errori, la tua scheda SD è buona e puoi eliminare tutti i .file.h2w sulla tua scheda SD.

DANGER

Se il test mostra altri risultati, la tua scheda SD potrebbe essere corrotta o danneggiata e potrebbe essere necessario sostituirla!

TIP

Se TWiLight Menu++ non riesce ad avviarsi dopo aver seguito questo metodo, si prega di seguire il metodo di Windows, riavviando su Windows oppure tramite esecuzione di una Windows Virtual Machine

Sezione I - Formattazione della scheda SD

  1. Assicurati che la tua scheda SD non sia inserita nella tua macchina Linux
  2. Avvia il terminale Linux
  3. Digita orologio "lsblk"
  4. Inserisci la tua scheda SD nella tua macchina Linux
  5. Osserva l'output. Dovrebbe corrispondere a qualcosa del genere:
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
-mmcblk0     179:0    0   3,8G  0 disk
-└─mmcblk0p1 179:1    0   3,7G  0 part /run/media/user/FFFF-FFFF
-
  1. Prendi nota del nome del dispositivo. Nell'esempio sopra, era mmcblk0p1
    • Se RO è impostato a 1, assicurati che l'interruttore di blocco non sia scivolato
    • Assicurati di puntare alla partizione: mmcblk0p1 non mmcblk0
  2. Premi CTRL + C per uscire dal menu
  3. Segui le istruzione relative alla capacità della tua scheda SD:
    • 2GB o meno: sudo mkdosfs /dev/(nome dispositivo indicato prima) -s 64 -F 16
      • Verrà creata un'unica partizione FAT16 con dimensione di allocazione di 32 KB sulla scheda SD
    • 4GB o più: sudo mkdosfs /dev/(nome dispositivo indicato prima) -s 64 -F 32
      • Verrà creata un'unica partizione FAT32 con dimensione di allocazione di 32 KB sulla scheda SD

Sezione II - Uso Di F3

  1. Scarica ed estrai l'archivio F3apri in nuova finestra in un percorso qualsiasi sul tuo computer.
  2. Avvia il terminale nella directory F3
  3. Esegui make per compilare F3
  4. Con la scheda SD inserita e montata, avvia ./f3write <your sd card mount point>
    • Attendi che il processo venga completato. Qui sotto vedrai un esempio di output:
    $ ./f3write /media/michel/6135-3363/
-Free space: 29.71 GB
-Creating file 1.h2w ... OK!
-...
-Creating file 30.h2w ... OK!
-Free space: 0.00 Byte
-Average Writing speed: 4.90 MB/s
-
  5. Esegui ./f3read <your sd card mount point>
  • Attendi che il processo venga completato. Qui sotto vedrai un esempio di output:
    $ ./f3read /media/michel/6135-3363/
-                  SECTORS      ok/corrupted/changed/overwritten
-Validating file 1.h2w ... 2097152/        0/      0/      0
-...
-Validating file 30.h2w ... 1491904/        0/      0/      0
-
-   Data OK: 29.71 GB (62309312 sectors)
-Data LOST: 0.00 Byte (0 sectors)
-            Corrupted: 0.00 Byte (0 sectors)
-   Slightly changed: 0.00 Byte (0 sectors)
-         Overwritten: 0.00 Byte (0 sectors)
-Average Reading speed: 9.42 MB/s
-

TIP

Se il test mostra Data LOST: 0.00 Byte (0 sectors) come risultato, la tua scheda SD va bene e puoi eliminare tutti i file .h2w dalla scheda SD.

DANGER

Se il test mostra altri risultati, la tua scheda SD potrebbe essere corrotta o danneggiata e potrebbe essere necessario sostituirla!

Sezione I - Formattazione della scheda SD con SD Formatter

TIP

Questa sezione riguarda la formattazione della scheda SD secondo le specifiche della SD Card Association. Può risolvere moltissimi problemi che potrebbero verificarsi con l'esecuzione di applicazioni homebrew.

DANGER

Tutte le schede SD da 64GB o più grandi saranno formattate in exFAT con questo processo. Devi seguire la Sezione II per riformattare in FAT32.

  1. Scarica la versione più recente di SD Formatterapri in nuova finestra
    • Accetta il Contratto di Licenza per l'Utente Finale per avviare il download
  2. Esefui Install SD Card Formatter (il file .mpkg) nel file.zip scaricato
  3. Esegui Sd Card Formatter
  4. Seleziona la tua scheda SD
  5. Assicurati che la casella Quick Format sia spuntata
  6. Avvia il processo di formattazione

Sezione II - Formattazione della scheda SD con Utility Disco

Questa sezione serve per formattare schede SD più grandi di 32GB in FAT32.

TIP

Se la tua scheda SD ha una capacità di 32GB o minori, salta questa sezione e vai alla Sezione III.

OS X El Capitan (10.11) e successivi

  1. Avviare l'applicazione Utility Disco
  2. Seleziona Mostra tutti i dispositivi nel pannello Vista in alto a sinistra
  3. Seleziona la tua scheda SD dalla barra laterale
    • Assicurati di selezionare il dispositivo correto, altrimenti potresti formattare l'unità sbagliata!
  4. Clicca su Cancella in alto
  5. Assicurati che il Formato sia impostato su MS-DOS (FAT32)
    • Su El Capitan (10.11) attraverso Catalina (10.15) scegli MS-DOS (FAT)
  6. Assicurati che Schema sia impostato su Master Boot Record (MBR)
    • Se Schema non appare, clicca Annulla e assicurati di selezionare il dispositivo invece di un volume
  7. Clicca Cancella, e infine clicca Chiudi

OS X Yosemite (10.10) e precedenti

  1. Avvia l'applicazione Utility Disco
  2. Seleziona la tua scheda SD dalla barra laterale
    • Assicurati di selezionare il dispositivo correto, altrimenti potresti formattare l'unità sbagliata!
  3. Clicca Partiziona in alto
    • Se Partiziona non appare, assicurati di selezionare la SD invece di un volume
  4. Assicurati che Schema Volume sia impostato su 1 Partizione
  5. Assicurati che Formato sia impostato su MS-DOS (FAT)
  6. Dal pulsante Opzioni (sotto la tabella di partizione) seleziona Master Boot Record (MBR).
  7. Clicca OK -> Applica -> Partiziona

Sezione III - Uso di F3

  1. Apri il terminale
  2. Installa F3 da brew esegunedo brew install f3
  3. Con la scheda SD inserita e montata, esegui run f3write <your sd card mount point>
    • Attendi che il processo sia completato. Vedi sotto per un esempio dell'output:
    $ f3write /Volumes/SD\ CARD
-Free space: 29.71 GB
-Creating file 1.h2w ... OK!
-...
-Creating file 30.h2w ... OK!
-Free space: 0.00 Byte
-Average Writing speed: 4.90 MB/s
-
  4. Esegui ./f3write <la tua scheda sd>
    • Attendi che il processo sia completato. Vedi sotto per un esempio dell'output:
    $ f3read /Volumes/SD\ CARD
-                  SECTORS      ok/corrupted/changed/overwritten
-Validating file 1.h2w ... 2097152/        0/      0/      0
-...
-Validating file 30.h2w ... 1491904/        0/      0/      0
-
-   Data OK: 29.71 GB (62309312 sectors)
-Data LOST: 0.00 Byte (0 sectors)
-            Corrupted: 0.00 Byte (0 sectors)
-   Slightly changed: 0.00 Byte (0 sectors)
-         Overwritten: 0.00 Byte (0 sectors)
-Average Reading speed: 9.42 MB/s
-

TIP

Se il test mostra Data LOST: 0.00 Byte (0 sectors) come risultato, la tua scheda SD va bene e puoi eliminare tutti i file .h2w dalla scheda SD.

DANGER

Se il test mostra altri risultati, la tua scheda SD potrebbe essere corrotta o danneggiata e potrebbe essere necessario sostituirla!

TIP

Ora è possibile ripristinare il contenuto della scheda SD e continuare.

- - - diff --git a/it_IT/site-navigation.html b/it_IT/site-navigation.html deleted file mode 100644 index 373bb309d..000000000 --- a/it_IT/site-navigation.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Navigazione Sito | Guida DSi - - - - -
Guida DSi

Navigazione Sito

Unisciti al server Discord DS⁽ⁱ⁾ Mode Hacking! per lo sviluppo di guide e aiuto.

-

- - - diff --git a/it_IT/troubleshooting.html b/it_IT/troubleshooting.html deleted file mode 100644 index 8732608e0..000000000 --- a/it_IT/troubleshooting.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Risoluzione dei problemi | Guida DSi - - - - -
Guida DSi

Risoluzione dei problemi

Unisciti al server Discord DS⁽ⁱ⁾ Mode Hacking! per lo sviluppo di guide e aiuto.

-

Unlaunch

Unlaunch si blocca a MISMATCH IN FAT COPIES

twlnf ha un bug critico che non aggiorna correttamente l'intera NAND dopo averla modificata, che porta alcuni homebrew (come Unlaunch installer) a generare un errore.

Per risolvere questo problema, apri NAND Title Manager (NTM)apri in nuova finestra, e seleziona Fix FAT copy mismatch.

Non c'è alcun audio o schermata d'avvio quando si avvia "Launcher" utilizzando Unlaunch

Lo sviluppatore di Unlaunch (nocash) ha intenzionalmente rimosso l'audio di sottofondo e la schermata d'avvio come impostazione predefinita. Puoi riattivare questi effetti reinstallando Unlaunch utilizzando TWiLight Menu++ con l'impostazione "Patch del Launcher" impostata su "Predefinita" nella pagina "Impostazioni Unlaunch", oppure usando hiyaCFWapri in nuova finestra.

Accendere la console mostra solo uno schermo nero dopo aver installato di Unlaunch

Prova ad espellere la scheda SD e riaccendere la console. Se continua a mostrare uno schermo nero, potresti aver bisogno di eseguire un flash della NAND con un hardmodapri in nuova finestra.

Dopo aver installato Unlaunch, sono bloccato all'avvio di un'applicazione o al menu di Unlaunch

La causa è probabilmente la scelta dell'app sbagliata per l'opzione NO BUTTON in Unlaunch. Tieni premuto A + B durante l'avvio della console, vai a OPTIONS, e imposta NO BUTTON come preferisci.

Altri problemi con Unlaunch

Se Unlaunch mostra Clusters too large, Bad VBR, Bad MBR, oppure non mostra alcuna applicazione mentre la scheda SD è inserita, probabilmente la scheda SD non è stata formattata correttamente. Segui di nuovo Configurazione scheda SD.

TWiLight Menu++

Per la risoluzione dei problemi generali di TWiLight Menu++ leggi la pagina FAQ & Risoluzione dei problemiapri in nuova finestra sulla DS-Homebrew Wiki.

Ulteriore assistenza

Se hai incontrato un problema che non viene risolto qui, o che persiste nonostante le soluzioni fornite, chiedi assistenza nel server Discord DS(i) Mode Hacking!apri in nuova finestra.

- - - diff --git a/it_IT/uninstalling-unlaunch.html b/it_IT/uninstalling-unlaunch.html deleted file mode 100644 index b6455f9c1..000000000 --- a/it_IT/uninstalling-unlaunch.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Disinstallazione di Unlaunch | Guida DSi - - - - -
Guida DSi

Disinstallazione di Unlaunch

Unisciti al server Discord DS⁽ⁱ⁾ Mode Hacking! per lo sviluppo di guide e aiuto.

-

DANGER

Installare o disinstallare Unlaunch potrebbe causare un brick in maniera del tutto casuale alla tua console! Sei stato avvertito!

ATTENZIONE: Disinstallare Unlaunch potrebbe causare un brick al tuo Nintendo DSi. Ecco alcune ragione per cui potresti voler disinstallare Unlaunch ma con soluzioni che non necessitano la disinstallazione.

  • Lo sfondo di Unlaunch fa paura:Reinstalla Unlaunchseguendo le nuove istruzioni. Ora contengono istruzioni su come cambiare lo sfondo
  • Ho un problema con Unlaunch o la mia console dopo averlo installato: La pagina Risoluzione dei problemi spiegherà come risolvere i problemi che potrebbero verificarsi

WARNING

Per ridurre le probabilità di brick, assicurati di non aver installato nessun titolo DSiWare illegale nel backup della tua NAND (la SDNAND fornita da hiyaCFW non conta), o di non aver manomesso file di sistema.

WARNING

Per disinstallare Unlaunch, NON si dovrebbe utilizzare il suo disinstallatore incorporato direttamente sulla console in quanto c'è la possibilità che causi un brick alla tua console. Si prega di consultare quanto segue per la corretta disinstallazione.

Dopo aver esaminato le informazioni qui sopra, segui le istruzioni Effettuare dump della NAND per fare un nuovo backup della NAND, poi procedi a Ripristino di un backup della NAND. Ti guiderà attraverso la disinstallazione di Unlaunch dal backup della NAND e al suo flash alla tua console.

Se non sei in grado di usare no$gba o di ottenere un errore dopo la disinstallazione di Unlaunch in no$gba è anche possibile effettuare un flash del backup della NAND fatto prima dell'installazione di Unlaunch se ne hai ancora uno; tuttavia, si consiglia di provare a utilizzare un backup della NAND che precedentemente aveva Unlaunch prima. Questo renderà il recupero significativamente più facile nel caso di un brick che richiede un hardmod poiché Unlaunch lascia il footer no$gba incorporato nella NAND anche quando disinstallato.

- - - diff --git a/ja_JP/404.html b/ja_JP/404.html deleted file mode 100644 index 8cdc4db26..000000000 --- a/ja_JP/404.html +++ /dev/null @@ -1,33 +0,0 @@ - - - - - - - - - ページが見つかりません | DSi ガイド - - - - -
- - - diff --git a/ja_JP/alternate-exploits.html b/ja_JP/alternate-exploits.html deleted file mode 100644 index 6e5ed836c..000000000 --- a/ja_JP/alternate-exploits.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - 代替エクスプロイト | DSi ガイド - - - - -
DSi ガイド

代替エクスプロイト

DS⁽ⁱ⁾ Mode Hacking! Discordサーバーに参加してガイドの開発とヘルプをご覧ください。

-

お使いのDSiでニンテンドーDSiカメラを起動した時にチュートリアルが始まり、完了前にクラッシュする場合、Memory Pitは使用できません。 ここでは、Memory Pitの代わりに動作するかもしれない別のエクスプロイトを紹介します。

うごくメモ帳がインストールされている場合は、Flipnote Lennyを使用できます。

TIP

以下に進む前に、SDカードにTWiLight Menu++のファイルなどがセットアップされていることを確認してください。

古いファームウェアをお使いの場合は、いくつかのゲーム新しいウィンドウで表示で起動できるセーブデータエクスプロイトを利用することができます。 これらはほとんど時代遅れなので、ここでは扱いません。 Memory PitとFlipnote Lennyがどちらもうまく行かない場合の最終手段としてのみ使うべきです。

pit-compwnerは、エクスプロイトを起動するためにカメラを必要とするので、Memory Pitの代わりとしては使用できません。

- - - diff --git a/ja_JP/credits.html b/ja_JP/credits.html deleted file mode 100644 index a5a9a9294..000000000 --- a/ja_JP/credits.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - 謝辞 | DSi ガイド - - - - -
DSi ガイド

謝辞

DS⁽ⁱ⁾ Mode Hacking! Discordサーバーに参加してガイドの開発とヘルプをご覧ください。

-

このガイドやHomebrewアプリなどでご協力くださった方々への謝辞です。

彼らの功績に感心したら、是非寄付をご検討ください（寄付リンクがある場合）。

プルリクエストを送る新しいウィンドウで表示だけで、あなたもガイドに貢献できます！

他の言語をご存知なら、ガイドの翻訳作業を通じて私たちの活動にご協力いただけます。 是非Crowdinプロジェクト新しいウィンドウで表示にご参加ください！

- - - diff --git a/ja_JP/dsiware-backups.html b/ja_JP/dsiware-backups.html deleted file mode 100644 index 44d42571a..000000000 --- a/ja_JP/dsiware-backups.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - DSiウェアのバックアップ | DSi ガイド - - - - -
DSi ガイド

DSiウェアのバックアップ

DS⁽ⁱ⁾ Mode Hacking! Discordサーバーに参加してガイドの開発とヘルプをご覧ください。

-

必要事項

ニンテンドーDSi - 手順

セクション I - DSiウェアの吸出し

  1. GodMode9iを起動します
  2. STARTを押してSTARTメニューを開きます
  3. タイトル マネージャー...を選択します
    • 表示されていない場合は、SDカードとNANDがマウントされていることを確認してください。 hiyaCFWから起動した場合は、別の場所から起動してください
  4. バックアップするタイトルを選択します
  5. バックアップするデータを選択します
  6. 目的のDSiウェアのすべてに対して、ステップ4〜5を繰り返します

TIP

DSiウェアのバックアップはsd:/gm9i/outにあります。

- - - diff --git a/ja_JP/dumping-game-cards.html b/ja_JP/dumping-game-cards.html deleted file mode 100644 index 4b346bbd1..000000000 --- a/ja_JP/dumping-game-cards.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - ゲームカード（DSソフト）の吸い出し | DSi ガイド - - - - -
DSi ガイド

ゲームカード（DSソフト）の吸い出し

DS⁽ⁱ⁾ Mode Hacking! Discordサーバーに参加してガイドの開発とヘルプをご覧ください。

-

このセクションでは、GodMode9iを使ってゲームカードの吸い出しをします。エミュレータ、マジコン、またはnds-bootstrap経由でSDカードから遊べるようになります。

必要事項

  • 吸い出したいソフトのゲームカード
  • UnlaunchがインストールされたDSi

手順

セクション I - SDカードのセットアップ

  1. 最新のGodMode9i新しいウィンドウで表示をダウンロードします
  2. GodMode9i.ndsをGodMode9iの圧縮ファイルから取り出し、SDカードの好きな場所へ配置します

セクション II - ニンテンドーDSi上での操作

  1. GodMode9iを起動します
  2. ゲームカードが本体に挿入されていることを確認します
  3. GodMode9iで「NDS GAMECARD」オプションを選択します
  4. 吸い出すデータを選択します
    • 「Trimmed」オプションはROMの無駄な部分を削って吸い出し、SDカードのスペースを節約します。しかしROMハックのようなパッチがほとんど使えなくなります。
  5. 目的のゲームカードのすべてに対して、ステップ2〜4を繰り返します

TIP

The dumped Game Cards will be found in sd:/gm9i/out.

- - - diff --git a/ja_JP/dumping-nand.html b/ja_JP/dumping-nand.html deleted file mode 100644 index 58eb02042..000000000 --- a/ja_JP/dumping-nand.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - NANDのバックアップ | DSi ガイド - - - - -
DSi ガイド

NANDのバックアップ

DS⁽ⁱ⁾ Mode Hacking! Discordサーバーに参加してガイドの開発とヘルプをご覧ください。

-

このページは、NAND（DSi内部ストレージ）のバックアップ作成に関するものです。 hiyaCFWのセットアップや、DSiエミュレータ「No$GBA」や「melonDS」のセットアップに使用できます。

TIP

Make sure the SD card has at least 250MB of free space, or else you'll run into an error message in dumpTool.

TIP

It is highly recommended that you do this. A NAND backup can be used as a restore point in the future, in case of a brick.

セクション I - SD カードのセットアップ

TIP

If you have already downloaded dumpTool from another section of this guide, you can skip this section.

  1. 最新のdumpTool新しいウィンドウで表示をダウンロードします
  2. SDカードの好きな場所にdumpTool.ndsを移動します

Section II - NANDのバックアップ

  1. dumpToolをTWiLight Menu++から起動します
  2. NANDのバックアップを開始するには、DSiのAボタンを押します
    • NANDバックアップは通常約7分かかります
  3. NANDバックアップが完了したら、STARTボタンを押してdumpToolを終了します
  4. 本体の電源を切ってSDカードをパソコンなどに挿入します
  5. このバックアップを、安全で、失くす心配のない場所に保管します
    • 可能であれば、異なるストレージ機器に複数のバックアップを作成します
    • 他の場所にバックアップできたら、SDカードからは消してOKです

WARNING

The SHA1 hash of the nand.bin will not match the hash stored in nand.bin.sha1. This is because dumpTool adds additional data known as a no$gba footer to the nand.bin file after the SHA1 hash is calculated. You can use the hiyaCFW Helper新しいウィンドウで表示 to create a copy without the footer.

TIP

Continue to Installing Unlaunch (Optional)

- - - diff --git a/ja_JP/faq.html b/ja_JP/faq.html deleted file mode 100644 index 3c2142bb4..000000000 --- a/ja_JP/faq.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - よくある質問 | DSi ガイド - - - - -
DSi ガイド

よくある質問

DS⁽ⁱ⁾ Mode Hacking! Discordサーバーに参加してガイドの開発とヘルプをご覧ください。

-

本体の更新を行う必要がありますか？

購入したDSiウェアがない限り、DSiの更新は推奨しません。 更新してもガイドを進めることは可能ですが、更新による利点はニンテンドーDSiショップで購入済みタイトルを再ダウンロードできることくらいです。 その他、DSiカメラのFacebook連携をはじめとした様々な恩恵はもう得られないか、あっても更新の欠点を補えるものではありません。

  • 本体の更新では時折本体がブリックすることが知られており、Unlaunchのインストールとほぼ同じ可能性で起こります。
  • 古いエクスプロイトはもう利用できません。推奨されるエクスプロイトを現状で利用できないようであれば更新が必須かもしれません。
  • マジコンの互換性が低下します。しかしながらUnlaunchをインストールすればこの問題は回避できます。

最も良いエクスプロイトはどれですか？

Unlaunchは全体的に最良のDSiエクスプロイトです。唯一の欠点は、インストール時に僅かなブリックの危険があることです。 一般的には、Memory Pitを使用してUnlaunchをインストールするのがおすすめです。 あらゆるリスクを回避したい場合は、代わりにFlipnote Lennyの使用をお勧めします。これは、Memory Pitと同じくらい安全で除去も簡単でありながら、Homebrewに関する問題がより少ないためです。 以下は、それぞれのエクスプロイトの長所・短所の一覧です。

Memory Pit

長所

  • 手っ取り早くて簡単
  • 本体に損傷を与える危険性なし（アンインストールもSDを抜き取るか、ファイルを1つ削除するだけ）
  • 全DSi機種と互換性あり（カメラが正しく動作し、カメラのチュートリアルを終えることが条件）

短所

  • HomebrewにアクセスするたびにDSiカメラアプリを起動する必要がある
  • WRAMがARM7 CPUにのみ開いているため、特定のDSiモードのタイトルおよびHomebrewと互換性がない
  • HomebrewではSlot-1（DSゲームカード）へのアクセス不能
  • DSPへのアクセスが不能で、結果としてGBARunner2の音質が悪化
  • Memory Pitがインストールされている間は、SDカード上の写真がDSiカメラアプリで表示できない（エクスプロイトのトリガーであるため）
    • Memory PitがインストールされているときにSDカードの写真を見る唯一の方法は、TWiLight Menu++でＤＳｉカメラアプリを吸い出して（v0.61.3以降の）nds-bootstrapから起動することです

stylehax

長所

  • Memory PitよりもDSiモードのタイトルとHomebrewとの互換性が高い
  • Easy to use
  • No risk of damaging the console
  • Useable on consoles with broken camera
  • GBARunner2での音質が良い

短所

  • Requires internet access
  • Requires loading the DSi Browser every time you want to access homebrew, slightly more time consuming than Memory Pit
  • HomebrewではSlot-1（DSゲームカード）へのアクセス不能

Flipnote Lenny（うごくメモ帳エクスプロイト）

長所

  • Memory PitよりもDSiモードのタイトルとHomebrewとの互換性が高い
  • 本体に損傷を与える危険性なし（アンインストールもSDを抜き取るか、フォルダを1つ削除するだけ）
  • Useable on consoles with broken camera
  • GBARunner2での音質が良い

短所

  • Homebrewにアクセスするために毎回うごくメモ帳を読み込む手間（Memory Pitより少し時間がかかる）
  • HomebrewではSlot-1（DSゲームカード）へのアクセス不能

Unlaunch

長所

  • 本体起動時にHomebrewやDSiウェアを直ちに読み込み可能。また任意のショートカットキーを指定可能
  • システムへの無制限なフルアクセス
    • Slot-1にアクセスしてゲームカードの吸出し、互換性のないマジコンの読込みが可能
    • GBARunner2での音質が良い
  • DSi対応・専用ソフトのリージョンロックを解除可能
  • 起こりうるDSiブリックに対する保護機能
  • ドナーROMを使わずにDSi対応ゲームをDSiモードで起動可能
  • nds-bootstrap-hb経由で古いHomebrewを起動可能

短所

  • インストール時のごく僅かなブリックの可能性
  • アンインストールはインストールよりもわずかながら高リスク
  • 開発用機種との互換性なし

システムを改造することで、失われる機能はありますか？

Unlaunchをインストールしても、Flipnote Lennyを使用しても、何ら機能は失われません。 Memory Pitを使用すると、DSiカメラを使ってSDカード上の写真を閲覧できなくなります。TWiLight Menu++を使用してnds-bootstrap経由でDSiカメラアプリのROMダンプを起動するというのが閲覧する唯一の方法です。

  • DSiメニューからカメラアプリを起動したときにSDカードの写真閲覧機能を取り戻すには、Unlaunchをインストールするか別のエクスプロイトに切り替えるかして、その後Memory Pitのpit.binファイルを消去します
    • tip.binが同じフォルダに存在する場合、pit.binに名前を戻します

吸い出したDSソフトはどうやってプレイできますか？

吸い出したDSソフトで遊ぶには、マジコンもしくはnds-bootstrap（Slot-1の読み書きをリダイレクトすることで、内部SDカードからゲームをプレイ可能にするプログラム）の使用が必要です。

  • TWiLight Menu++を使えば、SDカード内のROMをnds-bootstrapでプレイすることができます。 TWiLight Menu++を使用する利点は、チートメニューが使えること、ゲームごとに設定を変更できること、フォワーダ（下記リンク参照）による制限を回避できることです。 つまり、ROMファイルを適当に配置するだけで、事前準備なしでプレイできます。 39タイトルという制約（後述）もなく、hiyaCFWやUnlaunchも必要なく、利用できるSDカードの（空き）容量制限もありません
  • hiyaCFWユーザならDS-Homebrew WikiのDSゲームフォワーダ新しいウィンドウで表示ガイドを参考に、SD NAND DSiメニュー用のフォワーダを作成できますが、いくつか制限があります。 39タイトルまでの厳しい制限があり、作成自体がTWiLight Menu++を使うよりも不便です。

Homebrewを更新するにはどうすればいいですか？

  • Unlaunch―Unlaunchのインストールページの手順に従ってください
    • 更新前にアンインストールする必要はありません
  • hiyaCFW―SDカードのルートにあるhiya.dsiを更新されたリリース新しいウィンドウで表示で置き換えてください
  • TWiLight Menu++―DS-Homebrew Wiki新しいウィンドウで表示の指示に従ってください
  • nds-bootstrap―SDカードのルートにある_ndsフォルダに、nds-bootstrap-hb-release.ndsとnds-bootstrap-release.ndsをコピーしてください
    • TWiLight Menu++を使用している場合は、すでに最新のnds-bootstrapが含まれている可能性が高いです
  • GodMode9i, dumpTool, Forwarder3-DS, etc―ダウンロード時の手順に従ってください

他のHomebrewはそれぞれのやり方で更新できます。

初めて改造します。（あるいは）セットアップをやり直したいです。 なにから始めればいいですか？

  • まだ本体に変更を加えてない、またはインストール済みのUnlaunchを更新しようとしている場合、このガイドのはじめから順にページをたどることをお勧めします。 書いてあることはすべて必ず読んでください
  • 最新バージョンのUnlaunchをお使いの場合は、TWiLight Menu++インストールガイド新しいウィンドウで表示に従って本体のTWiLight Menu++をセットアップしてください

ペアレンタルコントロールを解除するにはどうしたらいいですか？

DSiのリージョン（地域）を変更できますか？

はい。変更したいものによって方法が異なります。

hiyaCFWのインストールガイドはどうなったんですか？

hiyaCFWはあまり機能的な役目を果たさず、多くのユーザにとって問題・混乱の種となるガイドでした。 そのためDS-Homebrew Wiki新しいウィンドウで表示に移動しました。

  • 他のガイドからそのページに誘導された場合、おそらく古いガイドを参考にしてしまったのでしょう。 代わりにこのガイドを使用してください。こちらはプロジェクト開発者によって絶えず維持されています

どんな種類のSDカードを使うべきですか？

  • 信頼できるブランドからSDカードを購入しましょう
  • フルサイズのSDカードまたはmicroSDカード（アダプター併用）はどちらでも使用できます
  • 1GB以上2TB以下のどんな容量でもいけます。 一般的な使い方では、8GBで十分です
    • hiyaCFWなどの一部のソフトウェアでは、SDカードの容量が大きいほどロード時間が長くなることがあります
  • スピードクラス8以上をお勧めします

他の本体で同じDSiのSDカードを使用できますか？

一般的には可能です。ただし2つの例外があります。

  • hiyaCFWははじめにセットアップされたシステムでのみ動作します
  • nds-bootstrapやマジコンを使用している場合でも、オンライン対応ゲームのフレンドコードは別の本体でオンラインにしたときにリセットされます

Homebrew環境構築後、新しいSDカードに切り替えるにはどうすればよいですか？

SDカードのセットアップの手順で新しいSDカードをフォーマットして、古いSDカードから新しいSDカードへデータを移すだけでOKです。

Homebrew環境構築後、SDカードを挿入せずに本体を正常に使用できますか?

はい。 Unlaunchをインストールしなければ、システムは何ら変更されません。 Unlaunchをインストールした場合は、Unlaunchの設定で元のDSiメニューを自動起動するように変更を加える必要があるかもしれません。

Unlaunchのサイト新しいウィンドウで表示には「バージョン2.0は安全性不明」と書かれています。 以前のバージョンを使用するほうが良いですか？

Unlaunchのサイトは、2年以上前にバージョン2.0がリリースされて以来更新されていません。 多くのユーザがこのバージョンを使っていて問題が発生していないため、安全だと考えられます。

How do I run dumped DSiWare?

The recommended method is to simply launch them with TWiLight Menu++, due to the simple drag-and-drop method and there being no arbitrary limit. When nds-bootstrap is set as the launch method, it also gains the benefits of cheats and screenshots, as well as any other benefit provided by the in-game menu.

However, for the few titles that are incompatible, you can use NTM新しいウィンドウで表示 to install them on either internal memory or hiyaCFW's SDNAND新しいウィンドウで表示. In addition to lacking the benefits above, there is also a limit of 39 titles that cannot exceed 128 MiB/1,024 blocks in size. For SysNAND, there is also a very small risk of bricking the system when writing to the internal NAND.

- - - diff --git a/ja_JP/file-extensions-windows.html b/ja_JP/file-extensions-windows.html deleted file mode 100644 index 87d064532..000000000 --- a/ja_JP/file-extensions-windows.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - ファイル拡張子（Windows） | DSi ガイド - - - - -
DSi ガイド

ファイル拡張子（Windows）

DS⁽ⁱ⁾ Mode Hacking! Discordサーバーに参加してガイドの開発とヘルプをご覧ください。

-

この補足セクションでは、ファイル拡張子を隠すWindowsのデフォルト動作を無効にします。 ガイド内で示されるファイルを見つけるのが簡単になります。

  1. エクスプローラでSDカード等の任意のディレクトリを開きます
  2. トップバーの「表示」オプションをクリックします
    • オプションがない場合は、トップバーの右端にある···ボタンをクリックしてください
  3. 表示 >サブメニューにカーソルを合わせるかクリックします
  4. ファイル名拡張子のオプションをチェックします Windows 11で「ファイル名拡張子」のオプションにカーソルを合わせた図
  1. エクスプローラでSDカード等の任意のディレクトリを開きます
  2. リボンメニューの「表示」オプションをクリックします
  3. 「ファイル名拡張子」にチェックを入れます Windows 10で「ファイル名拡張子」のチェックボックスにカーソルを合わせた図
  1. クリックするかWindowsキーを押して、スタートメニューを開きます
  2. 「フォルダー オプション」と検索し、一致した項目を選びます Windows 7のスタートメニューで「フォルダー オプション」を検索する図
  3. フォルダー オプション メニューの上部にある「表示」オプションをクリックします
  4. 「登録されている拡張子は表示しない」のチェックを外します Windows 7のフォルダー オプションで「登録されている拡張子は表示しない」をオフにする図
- - - diff --git a/ja_JP/get-started.html b/ja_JP/get-started.html deleted file mode 100644 index 735448480..000000000 --- a/ja_JP/get-started.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - はじめる | DSi ガイド - - - - -
DSi ガイド

はじめる

DS⁽ⁱ⁾ Mode Hacking! Discordサーバーに参加してガイドの開発とヘルプをご覧ください。

-

The main homebrew application this guide has you install is TWiLight Menu++, which is an upgrade/replacement to the Nintendo DSi Menu that allows running other homebrew applications, retail DS games, emulators for various older systems, and more.

改造の準備として、TWiLight Menu++とその他Homebrewツールをダウンロードすることから始めます。

必要事項

セクション I - 準備

WARNING

Ensure your SD card is formatted correctly.

  1. SDカードをPCに挿入します
  2. 最新のTWiLight Menu++新しいウィンドウで表示をダウンロードします
  3. 最新のdumpTool新しいウィンドウで表示をダウンロードします
  4. _ndsフォルダをTWiLightMenu-DSi.7zからSDカードのルートへコピーします
  5. BOOT.NDSファイルをTWiLightMenu-DSi.7zからSDカードのルートへコピーします
  6. dumpTool.ndsファイルをSDカードのルートへコピーします

TIP

Unsure what the SD "root" is? See this image新しいウィンドウで表示

セクション II - エクスプロイトの選択

From here you have three options, with a minor difference in what each entails.

Memory Pit経由でUnlaunchをインストール

Memory Pit is an exploit utilizing the DSi Camera, compatible with all firmware versions. Optionally, this exploit can be used to install Unlaunch, a bootcode exploit that allows full control of the console on boot.

As Memory Pit is somewhat limited in homebrew compatibility, it is recommended to install Unlaunch, instead of using Memory Pit standalone. As this is the easiest method to install Unlaunch, this is the recommended path. However, there is a very minor risk of bricking your console when installing Unlaunch, so if this is a concern, see the alternate method below.

TIP

Continue to Launching the Exploit

stylehax

stylehax is an exploit utilizing the DSi Browser application, and can be used as an alternative to Memory Pit for installing Unlaunch (explained above) if your DSi has a broken camera.

For an Unlaunch-free experience, this exploit is recommended as using Memory Pit causes issues in some games and homebrew.

TIP

Continue to Launching the Exploit (stylehax)

Flipnote Lenny（うごくメモ帳エクスプロイト）

Flipnote Lenny is an exploit utilizing the Flipnote Studio application.

If you have Flipnote Studio and do not plan on installing Unlaunch (explained above), this exploit is recommended for the same reason as stylehax.

You can always install Unlaunch later if you decide later on that you want it.

TIP

Continue to Launching the Exploit (Flipnote Lenny)

For a more detailed pros and cons comparision of the available exploits, please see the Which is the best exploit? FAQ.

- - - diff --git a/ja_JP/index.html b/ja_JP/index.html deleted file mode 100644 index 6903630b5..000000000 --- a/ja_JP/index.html +++ /dev/null @@ -1,43 +0,0 @@ - - - - - - - - - ホーム | DSi ガイド - - - - -
DSi ガイド

DSi ガイド

ニンテンドーDSiを改造するための完全なガイド

TIP

他機種のHomebrewとカスタムファームウェアのガイドに関しては、CFW.Guide新しいウィンドウで表示をご参照ください。

TIP

このページを含め、入門ガイドの全ページをしっかり読んでから作業に移ってください。

Homebrewとは何ですか？

自作ソフト（Homebrew）新しいウィンドウで表示アプリは、ニンテンドーDSiなどのクローズドシステム向けに作られた、公式ライセンスを受けてないソフトウェアです。 これには、ユーティリティから自作ゲームまで様々なものがあります。

ファームウェアのバージョンや地域に関係なく、すべてのニンテンドーDSi機種で費用をかけずにHomebrewを実行できます。 必要なのは、改造に使うエントリポイントとHomebrewを保存するためのSDカードだけです。 このガイドで使用される主なエントリポイントは、Memory Pitと呼ばれます。もしMemory Pitが使用できない場合でも選択肢は他にもあります。

改造することで何ができますか？

  • マジコン不要で、SDカードからDSiソフトの吸出しやチートを実行する
  • Launch any DSiWare from your SD card
    • This means out-of-region and 3DS-exclusive DSiWare will also work
  • DSiの起動時に特定のボタンを押して、DSiウェアやHomebrewアプリを起動する
  • 様々なエミュレータを使用して古いゲームを動かす
  • 互換性のないマジコンを使用する
  • hiyaCFWを使用してNAND（システムデータ領域）をSDカードにリダイレクトする
  • Watch your favorite movies using either FastVideoDSPlayer or tuna-viDS
    • FastVideoDSEncoder requires a CPU supporting AVX2 (newer CPUs will likely support it)
  • 本体起動時に画像（スプラッシュ画面）を表示する
  • 自作ゲームで遊ぶ

Homebrewアプリはどこで入手できますか？

始める前に知っておくべきことは何ですか？

  • Windowsで標準のファイルエクスプローラをお使いの場合は、ファイル拡張子を表示させておくことをお勧めします
  • ブリックの危険があるのはUnlaunchのインストールだけですが、危険は最小限になっています

TIP

はじめるへ進む

- - - diff --git a/ja_JP/installing-unlaunch.html b/ja_JP/installing-unlaunch.html deleted file mode 100644 index a0ef1c26e..000000000 --- a/ja_JP/installing-unlaunch.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Unlaunchのインストール | DSi ガイド - - - - -
DSi ガイド

Unlaunchのインストール

DS⁽ⁱ⁾ Mode Hacking! Discordサーバーに参加してガイドの開発とヘルプをご覧ください。

-

DANGER

まだ完了していない場合は、先にNANDバックアップを行ってください。 可能性は僅かながら、Unlaunchの事故でDSiをブリックすることがあります。 はんだ付けの技術があれば、NANDバックアップとHardmod（ハード的改造）新しいウィンドウで表示から、バックアップを復元できます。

WARNING

この手順を実行するときは、本体が十分に充電されていることを確認してください。 作業中に電池切れを起こすと本体に深刻なダメージを与える可能性があります。

WARNING

UnlaunchにはニンテンドーDSi開発機との互換性はありません。

セクション I - SD カードのセットアップ

  1. 最新版Unlaunch新しいウィンドウで表示をダウンロードします
  2. UNLAUNCH.DSIをunlaunch.zipから取り出し、SDカードの好きな場所へ配置します
  3. SDカードにTWiLight Menu++が残っていることを確認します

セクション II - Unlaunchのインストール・更新

  1. TWiLight Menu++を起動します
    • Unlaunchをインストールするのが初めてなら、以前使ったエクスプロイトでTWilight Menu++を再起動してください
    • Unlaunchをインストール済で更新を考えている場合は、起動時にAとBを長押しし、TWiLight Menu++というラベルの付いたオプションを選択します
    • TWiLight Menu++がいくつもある場合、下画面のPathの最後にBOOT.NDSと表示されるものを選びます
  2. TWiLight Menu++設定を起動します
    • テーマを変更していない場合は、SELECTを押し、タッチスクリーン下部のDSアイコンをタッチします。 それ以外の場合は、TWiLight Menu++ Manualを参照してください
  3. L/RまたはX/Yを押してUnlaunch設定ページに移動します
  4. Unlaunchの背景画像を変更したい場合は、背景画像を選択し、好みの画像を選択してください
  5. TWiLight Menu++設定を終了します
  6. In the file navigation menu, launch Unlaunch DSi Installer
    • If you see two black screens after launching, download GodMode9i新しいウィンドウで表示, put its .dsi file on the SD root, then launch GodMode9i using TWiLight Menu++, and start Unlaunch.dsi
      This method does not enable Unlaunch to use custom patches and background
  7. Select the "install now" option
  8. 完了したら、本体を再起動します

If you see Unlaunch's Filemenu screen at this point, you have successfully modded your Nintendo DSi.

セクション III - Unlaunchインストール後の設定

Currently, Unlaunch defaults to launching its Filemenu on boot, but this can be changed launch whatever you want.

  1. AとBを押したままDSiの電源を入れる
    • これはUnlaunchのファイルメニューを開くホットキーです
    • 背景しか表示されない、またはSDカードのファイルが表示されない（TWiLight Menu++など）場合は、SDカードの再フォーマットが必要かもしれません。
  2. OPTIONSに移動し、利用可能なオプションを確認します
    • A + BはUnlaunchメニューを起動するためにハードコードされているため変更はできません
    • NO BUTTONおよびBUTTON A / B / X / Yは好きなように設定できます。本体起動時にどのボタンが長押しされているかに応じてロードするものを選択します。 DSiウェアも、Homebrewも、Slot-1ゲームカードも、wifibootも、UnlaunchのFilemenuも選べます
      • TWiLight Menu++の場合、TWiLight Menu++を選択します
      • もともとのDSiメニューの場合は、Launcherを選択します
    • LOAD ERRORは、SDカードが挿入されてないなどで、設定されたものが開始できなかったときのオプションです
  3. SAVE & EXITを選択し、本体の電源を切ります

セクション IV - SDカードのクリーンアップ

TIP

This section is optional and only serves for keeping your SD card tidy of files you won't need.

  • SDカードからsd:/private/ds/app/484E494A/pit.binファイルを削除します
    • tip.binがまだ存在する場合、pit.binに名前を戻します
  • SDカードのルートにDCIMがあった場合、もう元に戻しても大丈夫です
  • SDカードからUNLAUNCH.DSIファイルを削除する
  • 以下のフォルダから800031_104784BAB6B57_000.ppmとT00031_1038C2A757B77_000.ppmの2ファイルを削除します
    • sd:/private/ds/app/4B47554A/001（日本）
    • sd:/private/ds/app/4B475545/001（アメリカ）
    • sd:/private/ds/app/4B475556/001（ヨーロッパ・オーストラリア）
    • 自分の地域以外のフォルダを丸ごと削除してもOKです
  • SDカードからUNLAUNCH.DSIファイルを削除する
- - - diff --git a/ja_JP/launching-the-browser-exploit.html b/ja_JP/launching-the-browser-exploit.html deleted file mode 100644 index e8bcd18de..000000000 --- a/ja_JP/launching-the-browser-exploit.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Launching the Exploit (stylehax) | DSi ガイド - - - - -
DSi ガイド

Launching the Exploit (stylehax)

DS⁽ⁱ⁾ Mode Hacking! Discordサーバーに参加してガイドの開発とヘルプをご覧ください。

-

We'll start by first launching our exploit. For the best Unlaunch-free experience, or if the DSi camera is broken to install Unlaunch, we recommend using an exploit called "stylehax" which takes advantage of a flaw in how the DSi Browser application handles webpages.

エクスプロイトを起動すると、DSiメニューの代替として機能するHomebrewアプリ「TWiLight Menu++」を起動します。

必要事項

  • Nintendo DSi Browser installed on your Nintendo DSi
    • If you do not have the DSi Browser, then use Memory Pit instead

Launching the exploit

  1. 本体にSDカードが挿入されていることを確認してください
  2. Boot your Nintendo DSi and launch the DSi Browser application
  3. Touch the Go to Page button
    • The button will have a green www icon
  4. Type opera:about, and touch Go to load the page
  5. Touch the HOME icon
  6. Touch the Go to Page button
  7. Type stylehax.net, and touch Go to load the page

TIP

The exploit should take 21 seconds to take effect. If it takes longer than 30 seconds, then reboot, and try again.

WARNING

上画面が緑色になった場合は、TWiLight Menu++のBOOT.NDSがSDカードのルートにありません。 準備からやり直してください。

TWiLight Menu++を使えるようになりました！ まず、言語と地域を選択するように求められます。 本体の言語やリージョンに一致させる必要はないので、好きなものを選んでください。 更に続けて、NANDバックアップを作成することをお勧めします。 これは後で何か悪いことが起きたとき、本体を修復するのに使えます。

TIP

NANDバックアップに進む

- - - diff --git a/ja_JP/launching-the-exploit.html b/ja_JP/launching-the-exploit.html deleted file mode 100644 index a778805be..000000000 --- a/ja_JP/launching-the-exploit.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - エクスプロイトの起動 | DSi ガイド - - - - -
DSi ガイド

エクスプロイトの起動

DS⁽ⁱ⁾ Mode Hacking! Discordサーバーに参加してガイドの開発とヘルプをご覧ください。

-

まずエクスプロイトを起動できるようにSDカードをセットアップします。 ほとんどのユーザには「Memory Pit」という、ニンテンドーDSiカメラのメタデータ処理のバグを利用するエクスプロイトをお勧めします。

エクスプロイトを起動すると、DSiメニューの代替として機能するHomebrewアプリ「TWiLight Menu++」を起動します。

TIP

If you don't plan on installing Unlaunch and have either the DSi Browser or Flipnote Studio, it is recommended to use either stylehax or Flipnote Lenny instead. 詳しくは最も良いエクスプロイトはどれですか？を参照。

セクション I - DSiカメラのバージョンを確認する

  1. 本体の電源を入れます
  2. ニンテンドーDSiカメラを開きます
    • チュートリアルを始めるよう促されたら、すべて完了してしまってください
    • チュートリアルの実行中にクラッシュする場合、DSiカメラのハードウェアがどこか壊れているかもしれません。そうなるとMemory Pitは起動できません。 別のエクスプロイトを使ってください。
  3. 右側の大きなボタンを押してアルバムを開きます
  4. Facebookのアイコンが、スター、クラブ、ハートの隣に表示されていることを確認してください。図の赤線のように見えているはずです： Facebookアイコンの場所を示すスクリーンショット

セクション II - Memory Pit

  1. ニンテンドーDSiカメラのバージョンに対応したMemory Pitのバイナリをダウンロードします
  2. SDカードのsd:/private/ds/app/484E494A/に移動します
    • ニンテンドーDSiカメラを使ってSDカードに写真を保存したことがあるなら、すでにこのディレクトリがあるでしょう。 その場合、これを消して再作成する必要はありません
    • 存在しない場合は、フォルダを作成します
  3. pit.binが既にそこにある場合、tip.binに改名しておきます
  4. このフォルダにMemory Pitのpit.binファイルを配置します
  5. SDカードのルートにDCIMという名前のフォルダがある場合、写真を紛失しないようにバックアップを作成して、SDカード以外の場所へ移動します

セクション III - エクスプロイトを実行する

  1. 本体にSDカードが挿入されていることを確認してください
  2. 本体を起動し、ニンテンドーDSiカメラをはじめます
  3. 右上のSDカードボタンを押します
    • SDカードが挿入されていないと表示された場合は、別のSDカードを使用してください
    • SDカードを使用できないと表示された場合は、SDカードが正しくフォーマットされているか確認してください
  4. 右側の大きなボタンを押してアルバムを開きます
    • Memory Pitが正しくコピーされた場合、画面がマゼンタ色に光ります

WARNING

上画面が緑色になった場合は、TWiLight Menu++のBOOT.NDSがSDカードのルートにありません。 準備からやり直してください。

WARNING

SDカードのカメラアルバムに入っても特に異常がない場合、正しいバージョン用・地域用のMemory Pitをダウンロードしたか、SDカードの正しいフォルダに配置したか確かめてください。 また、DCIMフォルダがSDカードに存在しないことを確認してください。

これでTWiLight Menu++を使えるようになりました！ まず、言語と地域を選択するように求められます。 本体の言語やリージョンに一致させる必要はないので、好きなものを選んでください。 更に続けて、NANDバックアップを作成することをお勧めします。 これは後で何か悪いことが起きたとき、本体を修復するのに使えます。

TIP

NANDバックアップに進む

- - - diff --git a/ja_JP/launching-the-flipnote-exploit.html b/ja_JP/launching-the-flipnote-exploit.html deleted file mode 100644 index a8bfdb735..000000000 --- a/ja_JP/launching-the-flipnote-exploit.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Flipnote Lennyの起動 | DSi ガイド - - - - -
DSi ガイド

Flipnote Lennyの起動

DS⁽ⁱ⁾ Mode Hacking! Discordサーバーに参加してガイドの開発とヘルプをご覧ください。

-

まずエクスプロイトを起動できるようにSDカードをセットアップします。 最高のUnlaunch不要環境を作るには、エクスプロイト「Flipnote Lenny」の使用がお勧めです。うごくメモ帳でのメモの取り扱いにおける脆弱性を利用したものです。

エクスプロイトを起動すると、DSiメニューの代替として機能するHomebrewアプリ「TWiLight Menu++」を起動します。

必要事項

  • 「うごくメモ帳」がDSiにインストールされていること
    • うごくメモ帳がない場合は、代わりにMemory Pitを使用してください

セクション I - SDカードのセットアップ

  1. 最新版のFlipnote Lenny新しいウィンドウで表示をダウンロードします
  2. Flipnote Lenny圧縮ファイルからprivateフォルダをSDカードのルートにコピーします

セクション II - エクスプロイトを起動する

  1. DSi本体にSDカードが挿入されていることを確認してください
  2. 本体を起動し、うごくメモ帳をはじめます
  3. メインメニューの右上にある設定画面を開き、カレンダーから起動を「OFF」にして、カエルを「表示」にします
  4. SDカードに保存されているメモを表示します
    • SDカードのメモを表示できない場合は、別のSDカードを使用してください
  5. お住まいの地域に合った顔（日本はJPN）をタッチします
    • AUS機種をお持ちの場合は、EURを選択してください
  6. 書くをタッチします
  7. 左下のカエルアイコンをタッチします
  8. フィルムのアイコンをタッチします
  9. コピー -> 戻る -> 終了とタッチしていきます
  10. 大きい顔のメモをタッチし、書くを選択します
  11. 左下のカエルアイコンをタッチします
  12. フィルムのアイコンをタッチします
  13. 貼り付けを選びます

WARNING

上画面が緑色になった場合は、TWiLight Menu++のBOOT.NDSがSDカードのルートにありません。 準備からやり直してください。

TWiLight Menu++を使えるようになりました！ まず、言語と地域を選択するように求められます。 本体の言語やリージョンに一致させる必要はないので、好きなものを選んでください。 更に続けて、NANDバックアップを作成することをお勧めします。 これは後で本体にマズイことが起きたとき、本体を修復するのに使えます。

TIP

NANDバックアップに進む

- - - diff --git a/ja_JP/lazy-dsi-downloader.html b/ja_JP/lazy-dsi-downloader.html deleted file mode 100644 index 14d75879d..000000000 --- a/ja_JP/lazy-dsi-downloader.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Lazy DSi Downloader | DSi ガイド - - - - -
DSi ガイド

Lazy DSi Downloader

DS⁽ⁱ⁾ Mode Hacking! Discordサーバーに参加してガイドの開発とヘルプをご覧ください。

-

「Lazy DSi Downloader」は、DSi本体の改造処理を簡単にするためのツールです。

確認作業

  1. DSiの電源を入れます
  2. ニンテンドーDSiカメラアプリを起動します

この時点でチュートリアルが表示され、進めるとクラッシュする場合は、Memory Pitは使用できません。

セットアップガイド

  1. 使用中のOSに合わせて最新版のLazy DSi File Downloader新しいウィンドウで表示をダウンロードします
  2. リリースページに掲載されているOS毎の手順に従い、起動します
  3. 「Next」ボタンを押します
    • 最初の文章は読まなくても構いません
  4. 上記の確認作業でDSiがクラッシュした場合は、Memory Pitのチェックを外します
  5. 「Download latest GodMode9i version?」オプションにチェックを入れます
    • 他のHomebrewアプリをClick to add Additional homebrew...から自由に選べますが、必須ではありません
  6. 「Click to select folder」でSDカードを選び、「Start」を押して、ダウンロードがすべて終わるまで待って、最後に「Finish」を押します
- - - diff --git a/ja_JP/restoring-nand.html b/ja_JP/restoring-nand.html deleted file mode 100644 index 61aa83f39..000000000 --- a/ja_JP/restoring-nand.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - NANDバックアップの復元 | DSi ガイド - - - - -
DSi ガイド

NANDバックアップの復元

DS⁽ⁱ⁾ Mode Hacking! Discordサーバーに参加してガイドの開発とヘルプをご覧ください。

-

DANGER

警告！ これは危険です。 NANDは非常に繊細であり、特に複数回書き込みした場合は、これらのステップに忠実に従ってもブリックする危険性があります。 最後の手段としてのみ使用するべきです！

TIP

このページのどれか一つでもスキップしてはいけません。一つでも間違うと、DSiをブリックする可能性が大幅に増加します。

まず、復元を行いたい問題について、より安全な解決策を提示します：

  • DSiウェアのインストールは、hiyaCFWまたはTWiLight Menu++を使って行うことができます
  • 写真の復元にはninfs新しいウィンドウで表示が利用できます。本体上で行いたい場合はhiyaCFWやTWiLight Menu++と組み合わせて使用します。 HiyaCFW Helperの最新版では、セットアップ中にNANDからSDNANDへ写真をコピーすることができます
  • Unlaunchのボタン設定の復元はUnlaunchメニューから行えます。本体の電源投入時にA + Bを長押しすることでメニューを開けます
  • Unlaunchの起動時にエラーが発生してお困りですか？ SDカードを取り出し、本体を再起動してみてください。 動く場合は、問題はSDカードにあるため、NANDバックアップを復元しても問題は解決されません
  • 起動時に「エラーが発生しました（An error has occurred）...」などと出たときはhiyaCFWのエラーで、NANDは無関係かもしれません。詳細は、DS-Homebrew WikiのhiyaCFW よくある質問・トラブルシューティング新しいウィンドウで表示を参照してください
  • TWiLight Menu++のエラーはNANDとは無関係で、修正にはTWiLight Menu++の再インストールをするかDiscord新しいウィンドウで表示で助けを求めるべきです
  • Unlaunchの削除は、NANDをフラッシュするか、付属アンインストーラを使用するかにかかわらず、絶対に必要でない限り行うべきではありません。UnlaunchのAutoboot設定をLauncherにすれば、DSiは純正品のように機能します

NANDの操作を必要とする事柄は、Unlaunchのインストールのみです。 それ以外の場合は上記の代替案を使用してください。

必要事項

no$gbaに使用するBIOSのダンプ

  1. dsibiosdumper.zipアーカイブから dsibiosdumper.ndsを取り出し、SDカード上の任意の場所に配置します
  2. AとBを押したままDSiの電源を入れます
    • これはUnlaunchのファイルメニューを開くホットキーです
  3. メニューからdsibiosdumperを起動します
  4. Aを押してBIOSをSDカードにダンプします
  5. STARTを押して、dsibiosdumperを終了します

NANDバックアップのテスト

本体へNANDバックアップを復元する前に、まずそれが動くかテストすることが非常に重要です。no$gbaでブリックエラーが表示される場合は、おそらく本体もブリックしてしまいます。

  1. NO$GBA.EXEをno$gba-w.zipから取り出します
  2. NANDバックアップをNO$GBA.EXEのあるフォルダにコピーし、DSI-1.MMCに名前を変更します
  3. bios7i.binとbios9i.binをNO$GBA.EXEのフォルダへコピーし、それぞれBIOSDSI7.ROMとBIOSDSI9.ROMに改名します
  4. NO$GBA.EXEを実行します
  5. Options > Emulation Setupをクリックしてエミュレーション設定ウィンドウを開きます
  6. Reset/Startup EntrypointをGBA/NDS BIOS (Nintendo logo)に変更します
  7. NDS Mode/ColorsをDSi (retail/16MB)に変更します
  8. Save Nowをクリックします
  9. 任意のDS ROM（.ndsファイル）を起動します

no$gbaでDSiメニューかUnlaunch Filemenuがロードされた場合は、次のセクションに進みます。 何かエラーが表示された場合、そのバックアップを利用してはいけません！

NANDバックアップからUnlaunchを除去（任意）

もしUnlaunchをインストールした後にNANDバックアップを作成し、かつシステムからUnlaunchを削除したいなら、この手順に従ってください。 Unlaunchの削除をするつもりがなければ、この操作は必要ありません。

  1. 最新版のUnlaunch installer新しいウィンドウで表示をダウンロードします
  2. UNLAUNCH.DSIをunlaunch.zipから取り出します
  3. UNLAUNCH.DSIをno$gbaで起動してゲームカード スロットから開始します
    • Unlaunch installerが起動します。見た目はUnlaunch Filemenuに似ています
  4. Uninstallを選びます
  5. 完了したらPower downを選びます
  6. DS ROMを再度起動し、DSiメニューがロードされ正常に動作することを確認します

no$gbaでDSiメニューが表示されずに何かエラーが出た場合、そのバックアップを利用してはいけません！ 古いNANDバックアップをお持ちの場合は、代わりにそれを試したほうが良いです。 本体上でUnlaunch付属のアンインストーラーを使ってUnlaunchの削除をしてはいけません。DSiをブリックする可能性が非常に高いためです。

NANDバックアップの書き込み（ソフト的手法）

DANGER

ここからが危険な場所になるので、上記の手順をしっかり読み終えたか確認してください。 外部から直接ここにリンクされて上記の手順を読んでいない場合は、上に戻って、このページ全体を読んでください。

DANGER

このセクションを始める前に、DSiが十分に充電されていることを確認してください。

  1. SDカードを挿入した状態で、AとBを押したままDSiの電源を入れます
  2. SafeNANDManagerを起動します
  3. begin NAND restoreに対応するボタンを押して復元を開始します
  4. 復元が完了したら、STARTを押してDSiの電源を切ります

これでNANDが復元されたはずです。

NANDバックアップの書き込み（ハード的手法）

DSiが起動できない場合は、Hardmod（ハードウェア改造）がNANDバックアップを復元する唯一の方法です。 現存する最良のガイドは、DS-Homebrew Wiki上のDSi Hardmodガイド新しいウィンドウで表示です。

- - - diff --git a/ja_JP/sd-card-setup.html b/ja_JP/sd-card-setup.html deleted file mode 100644 index 7508b4f8e..000000000 --- a/ja_JP/sd-card-setup.html +++ /dev/null @@ -1,85 +0,0 @@ - - - - - - - - - SDカードのセットアップ | DSi ガイド - - - - -
DSi ガイド

SDカードのセットアップ

DS⁽ⁱ⁾ Mode Hacking! Discordサーバーに参加してガイドの開発とヘルプをご覧ください。

-

このページは、お持ちの機器用にSDカードの準備をするためのものです。 この操作でSDカードをフォーマットし、エラーがないかの確認をします。

DANGER

この手順を進める前に必ずSDカードの内容をバックアップしてください。 処理によってカード内のデータは完全に失われます。

セクション I - SDメモリカードフォーマッターでフォーマット

TIP

このセクションでは、SDアソシエーションの仕様に合わせてSDカードをフォーマットします。 Homebrewアプリの実行において発生しうる多くの問題を修正できるでしょう。

DANGER

この操作では、64GB以上のSDカードはexFATでフォーマットされます。 その場合はセクション II に従ってFAT32で再フォーマット_しなければなりません_。

  1. SDメモリカードフォーマッター新しいウィンドウで表示の最新版をダウンロードします
  2. ダウンロードした.zipファイルに含まれるSD Card Formatter Setup（.exeファイル）を管理者権限で実行し、プログラムをインストールします
  3. スタートメニューからSD Card Formatterを管理者権限で実行する
  4. SDカードを選択します
  5. クイックフォーマットが選択されていることを確認します
  6. フォーマットを押してフォーマット作業を開始します Windows 11でのSD Card Formatterのスクリーンショット

セクション II - GUIFormatでフォーマット

このセクションでは、32GBより大きいSDカードをFAT32でフォーマットします。

TIP

SDカードの容量が32GB以下の場合は、ここを飛ばしてセクション III に進んでください。

  1. GUIFormat新しいウィンドウで表示の最新版をダウンロードします
    • ダウンロードするにはサイトの画像をクリックしてください
  2. 管理者権限でGUIFormatを実行します
  3. ドライブレターを選択します
  4. Allocation unit sizeを32768に設定します
    • この数値がお使いのSDカードには大きすぎる場合、SDカードが動作する一番大きい値に設定してください
  5. Quick Formatチェック ボックスがオンになっていることを確認します
  6. フォーマットを開始します

セクション III - エラーのチェック

  1. SDカードのプロパティウィンドウを表示します
    • エクスプローラー -> PC -> SDカードを右クリック -> プロパティ
  2. ツールタブで、チェックを選択します
  3. 存在する場合は、ファイル システム エラーを自動的に修復すると不良セクターをスキャンし、回復するの両方にチェックを入れます
  4. 画面の指示に従い、チェックを開始します

これでSDカードがスキャンされ、発見されたすべてのエラーが修正されます。

セクション IV - SDカードの読み書きのチェック

  1. H2testwのアーカイブ新しいウィンドウで表示をダウンロード・展開します
  2. SDカードをコンピュータに挿入した状態でh2testw.exeを実行します
  3. H2testwで表示する言語を選択します
  4. Select targetでお使いのSDカードを選択します
  5. 忘れずにall available spaceを選択します
  6. Write + Verifyをクリックします
  • 処理が完了するまで待ちます

TIP

テスト結果がTest finished without errorsであればお持ちのSDカードは正常です。SDカード上の.h2wファイルはすべて削除して構いません。

DANGER

異なる結果が表示されていれば、お持ちのSDカードは破損・損傷している恐れがあり、新しいSDカードに交換が必要です！

TIP

この方法に従ってTWiLight Menu++が起動できない場合は、代わりにWindows実マシンか仮想マシンを起動して、Windowsの方法に従ってください。

セクション I - SDカードのフォーマット

  1. SDカードがLinuxマシンに挿入されていないことを確認します
  2. Linuxのターミナルを起動します
  3. watch "lsblk"を打ちます
  4. SDカードをLinuxマシンに挿入します
  5. 出力を見ます。 以下のように映るはずです：
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
-mmcblk0     179:0    0   3,8G  0 disk
-└─mmcblk0p1 179:1    0   3,7G  0 part /run/media/user/FFFF-FFFF
-
  1. 追加されたデバイス名をメモしてください。 上記の例ではmmcblk0p1です
    • ROが1になっていたら、ロックスイッチが下にスライドしないようにしてください
    • Make sure you're targetting the partition, mmcblk0p1 not mmcblk0
  2. Ctrl + C を押してメニューを終了します
  3. 次のうち、お使いのSDカードの容量にあった手順に従ってください：
    • 2GB以下：sudo mkdosfs /dev/(上で見つけたデバイス名) -s 64 -F 16
      • これにより、SDカード上にクラスタサイズが32KBのFAT16パーティションが一つ作成されます
    • 4GB以上：sudo mkdosfs /dev/(上で見つけたデバイス名) -s 64 -F 32
      • これにより、SDカード上にクラスタサイズが32KBのFAT32パーティションが一つ作成されます

セクションII - F3の使用

  1. F3のアーカイブ新しいウィンドウで表示をダウンロード・展開します
  2. F3のディレクトリでターミナルを起動します
  3. makeを実行してF3をコンパイルします
  4. SDカードを挿入してマウントしたら、./f3write <your sd card mount point>を実行します
    • 処理が完了するまで待ちます。 下記は出力の例です：
    $ ./f3write /media/michel/6135-3363/
-Free space: 29.71 GB
-Creating file 1.h2w ... OK!
-...
-Creating file 30.h2w ... OK!
-Free space: 0.00 Byte
-Average Writing speed: 4.90 MB/s
-
  5. ./f3read <your sd card mount point>を実行します
  • 処理が完了するまで待ちます。 下記は出力の例です：
    $ ./f3read /media/michel/6135-3363/
-                  SECTORS      ok/corrupted/changed/overwritten
-Validating file 1.h2w ... 2097152/        0/      0/      0
-...
-Validating file 30.h2w ... 1491904/        0/      0/      0
-
-   Data OK: 29.71 GB (62309312 sectors)
-Data LOST: 0.00 Byte (0 sectors)
-            Corrupted: 0.00 Byte (0 sectors)
-   Slightly changed: 0.00 Byte (0 sectors)
-         Overwritten: 0.00 Byte (0 sectors)
-Average Reading speed: 9.42 MB/s
-

TIP

テスト結果がData LOST: 0.00 Byte (0 sectors)であればお持ちのSDカードは正常です。SDカード上の.h2wファイルはすべて削除して構いません。

DANGER

異なる結果が表示されていれば、お持ちのSDカードは破損・損傷している恐れがあり、新しいSDカードに交換が必要です！

セクション I - SDメモリカードフォーマッターでフォーマット

TIP

このセクションでは、SDアソシエーションの仕様に合わせてSDカードをフォーマットします。 Homebrewアプリの実行において発生しうる多くの問題を修正できるでしょう。

DANGER

この操作では、64GB以上のSDカードはexFATでフォーマットされます。 その場合はセクション II に従ってFAT32で再フォーマット_しなければなりません_。

  1. SDメモリカードフォーマッター新しいウィンドウで表示の最新版をダウンロードします
    • エンドユーザーライセンス契約に同意してダウンロードを始めてください
  2. ダウンロードした.zipファイルに含まれるInstall SD Card Formatter（.mpkgファイル）を実行します
  3. SDカードフォーマッタを実行します
  4. SDカードを選択します
  5. Quick Formatチェック ボックスがオンになっていることを確認します
  6. フォーマットを開始します

セクション II - ディスクユーティリティでフォーマット

このセクションでは、32GBより大きいSDカードをFAT32でフォーマットします。

TIP

SDカードの容量が32GB以下の場合は、ここを飛ばしてセクション III に進んでください。

OS X El Capitan (10.11) 以降

  1. ディスクユーティリティアプリケーションを起動します
  2. 左上の表示パネルですべてのデバイスを表示を選択します
  3. サイドバーからSDカードを選択します
    • SDカードが正しく選択されていることを確認してください。さもないと、意図しないドライブを消してしまう可能性があります！
  4. 上部にある消去をクリックします
  5. フォーマットをMS-DOS (FAT32)に設定します
    • El Capitan（10.11）〜Catalina（10.15）ではMS-DOS (FAT)を選択してください。
  6. 方式をマスター・ブート・レコードに設定します
    • 方式が表示されない場合、キャンセルをクリックし、ボリュームではなくデバイスを選択してください
  7. 消去をクリックし、完了をクリックします

OS X Yosemite (10.10) 以前

  1. ディスクユーティリティアプリケーションを起動します
  2. サイドバーからSDカードを選択します
    • SDカードが正しく選択されていることを確認してください。さもないと、意図しないドライブを消してしまう可能性があります！
  3. 上部にあるパーティション作成をクリックします
    • パーティション作成が表示されない場合、ボリュームではなくデバイスを選択してください
  4. パーティションのレイアウト：を1 パーティションに設定します
  5. フォーマットをMS-DOS (FAT)に設定します
  6. オプションボタン（パーティション テーブルの下）から、マスター・ブート・レコードを選択します
  7. OK -> 適用 -> パーティションとクリックしていきます

セクション III - F3の使用

  1. ターミナルを開きます
  2. brew install f3を実行して、brewからF3をインストールします
  3. SDカードを挿入してマウントしたら、f3write <your sd card mount point>を実行します
    • 処理が完了するまで待ちます。 下記は出力の例です：
    $ f3write /Volumes/SD\ CARD
-Free space: 29.71 GB
-Creating file 1.h2w ... OK!
-...
-Creating file 30.h2w ... OK!
-Free space: 0.00 Byte
-Average Writing speed: 4.90 MB/s
-
  4. f3read <your sd card mount point>を実行します
    • 処理が完了するまで待ちます。 下記は出力の例です：
    $ f3read /Volumes/SD\ CARD
-                  SECTORS      ok/corrupted/changed/overwritten
-Validating file 1.h2w ... 2097152/        0/      0/      0
-...
-Validating file 30.h2w ... 1491904/        0/      0/      0
-
-   Data OK: 29.71 GB (62309312 sectors)
-Data LOST: 0.00 Byte (0 sectors)
-            Corrupted: 0.00 Byte (0 sectors)
-   Slightly changed: 0.00 Byte (0 sectors)
-         Overwritten: 0.00 Byte (0 sectors)
-Average Reading speed: 9.42 MB/s
-

TIP

テスト結果がData LOST: 0.00 Byte (0 sectors)であればお持ちのSDカードは正常です。SDカード上の.h2wファイルはすべて削除して構いません。

DANGER

異なる結果が表示されていれば、お持ちのSDカードは破損・損傷している恐れがあり、新しいSDカードに交換が必要です！

TIP

もうSDカードの内容を復元して、次に進んでOKです。

- - - diff --git a/ja_JP/site-navigation.html b/ja_JP/site-navigation.html deleted file mode 100644 index ca68ca7fe..000000000 --- a/ja_JP/site-navigation.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - サイトマップ | DSi ガイド - - - - -
DSi ガイド

サイトマップ

DS⁽ⁱ⁾ Mode Hacking! Discordサーバーに参加してガイドの開発とヘルプをご覧ください。

-

- - - diff --git a/ja_JP/troubleshooting.html b/ja_JP/troubleshooting.html deleted file mode 100644 index 8f0a61ac7..000000000 --- a/ja_JP/troubleshooting.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - トラブルシューティング | DSi ガイド - - - - -
DSi ガイド

トラブルシューティング

DS⁽ⁱ⁾ Mode Hacking! Discordサーバーに参加してガイドの開発とヘルプをご覧ください。

-

Unlaunch

MISMATCH IN FAT COPIESでUnlaunchがフリーズする

twlnfには、NAND変更後に全体を適切に更新しない重大なバグがあります。これはUnlaunchインストーラなどの特定のHomebrewアプリでエラーが発生する原因となります。

これを修正するには、NAND Title Manager (NTM)新しいウィンドウで表示を開き、Fix FAT copy mismatchを選択します。

Unlaunchで「Launcher」を起動すると音や起動スプラッシュ画面がない

Unlaunchの開発者（nocash）は、意図的にBGMとスプラッシュ画面を消すパッチをデフォルトで適用しています。 You can regain these effects by reinstalling Unlaunch using TWiLight Menu++ with "Launcher Patches" set to "Default" on the Unlaunch page of TWiLight Menu++ settings, or by using hiyaCFW新しいウィンドウで表示.

Unlaunchインストール後、電源を入れても画面が点かない

SDカードを取り出して、本体の電源を入れてみてください。 それでもまだ画面が黒いままの場合は、Hardmod新しいウィンドウで表示によってNANDをフラッシュする必要があるかもしれません。

Unlaunchのインストール後、アプリやUnlaunchファイルメニューの起動が止まる

これはおそらく、UnlaunchのNO BUTTONオプションで間違ったアプリを選択したことによって引き起こされます。 電源を入れるときにA + Bを長押しし、OPTIONSからNO BUTTONの設定をお好みに合わせて設定してください。

その他のUnlaunchの問題

UnlaunchでClusters too large、Bad VBR、Bad MBRと表示される、あるいはSDカードを挿入してもアプリが何も表示されない場合、SDカードが正しくフォーマットされていない可能性があります。 SDカードセットアップをもう一度試してください。

TWiLight Menu++

一般的なTWiLight Menu++トラブルシューティングについては、DS-Homebrew Wikiのよくある質問とトラブルシューティング新しいウィンドウで表示ページを参照してください。

サポート

ここで解決できない問題に出くわした、あるいは上記の方法で解決しなかった場合は、DS(i) Mode Hacking!新しいウィンドウで表示のDiscordサーバで質問してください。

- - - diff --git a/ja_JP/uninstalling-unlaunch.html b/ja_JP/uninstalling-unlaunch.html deleted file mode 100644 index 12a904d9b..000000000 --- a/ja_JP/uninstalling-unlaunch.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Unlaunchのアンインストール | DSi ガイド - - - - -
DSi ガイド

Unlaunchのアンインストール

DS⁽ⁱ⁾ Mode Hacking! Discordサーバーに参加してガイドの開発とヘルプをご覧ください。

-

DANGER

Unlaunchのインストール・アンインストールでは本体がランダムにブリック（文鎮化）することがあります！ 警告しましたよ！

**警告：**Unlaunchのアンインストールにより、お使いのDSiがブリックする可能性があります。 Unlaunchをアンインストールしたくても、そうせずに済む場合がいくつかあります。例えば：

WARNING

ブリックの可能性を減らすために、NANDバックアップ上に不正なDSiウェアがインストールされていないか（hiyaCFWによるSD NANDリダイレクトは除く）、システムファイルが改ざんされていないかを確認してください。

WARNING

Unlaunchを削除するとき、本体上でUnlaunch付属のアンインストーラを使ってはいけません。本体がブリックするおそれがあります。 正しくアンインストールする方法については、以下をご覧ください。

上記の情報を確認し終えたら、まずNANDのバックアップの手順を完了して新しくバックアップを取ります。それからNANDバックアップの復元に進みます。 これにより、NANDバックアップからUnlaunchをアンインストールし、本体に書き込むことができます。

no$gbaを使用できない場合や、no$gbaでUnlaunchをアンインストール後にエラーが発生した場合は、Unlaunchインストール以前のNANDバックアップをフラッシュすることも可能です。しかし、以前Unlaunch含んでいたNANDバックアップをまず使ってみるのをお勧めします。 UnlaunchはアンインストールされてもNANDにno$gbaフッターを埋め込んだままなので、上記操作によって、Hardmodが必要となるブリックの場合も修復が格段に簡単になるためです。

- - - diff --git a/launching-the-browser-exploit.html b/launching-the-browser-exploit.html index 51920e50f..16e4068eb 100644 --- a/launching-the-browser-exploit.html +++ b/launching-the-browser-exploit.html @@ -3,7 +3,7 @@ - + - - Strona nie znaleziona | Przewodnik DSi - - - - -
- - - diff --git a/pl_PL/alternate-exploits.html b/pl_PL/alternate-exploits.html deleted file mode 100644 index 92e3b1429..000000000 --- a/pl_PL/alternate-exploits.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Alternatywne Exploity | Przewodnik DSi - - - - -
Przewodnik DSi

Alternatywne Exploity

Join the DS⁽ⁱ⁾ Mode Hacking! Discord server for guide development and help.

-

Jeśli zostaniesz wprowadzony do samouczka podczas uruchamiania aplikacji Nintendo DSi Camera i pojawi się awaria podczas próby jej zakończenia, nie możesz użyć Memory Pit. Tutaj możesz znaleźć alternatywne exploity, które mogą zadziałać zamiast Memory Pit.

If you have Flipnote Studio installed, you can use Flipnote Lenny.

TIP

Ensure you have set up TWiLight Menu++ on your SD card before proceeding with any of the following.

If you're on an older firmware, you may have access to save game exploits for a select list of gamesopen in new window. These will not be covered here as they are largely obsolete. They should only be used as a last resort, if both Memory Pit and Flipnote Lenny aren't working for you.

petit-compwner will not be usable for the purpose of working around Memory Pit, as it requires a working camera to launch the exploit.

- - - diff --git a/pl_PL/credits.html b/pl_PL/credits.html deleted file mode 100644 index 263fc218a..000000000 --- a/pl_PL/credits.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Podziękowania | Przewodnik DSi - - - - -
Przewodnik DSi

Podziękowania

Join the DS⁽ⁱ⁾ Mode Hacking! Discord server for guide development and help.

-

To są zasługi dla tych, którzy pomagali przy stronie przewodnika, homebrew i innych rzeczach.

Jeśli podoba Ci się to, co zrobili, rozważ przekazanie darowizny (jeśli mają link).

Ty też możesz przyczynić się do rozwoju naszego przewodnika wysyłając pull requestopen in new window!

Jeśli znasz inne języki, możesz nam pomóc, tłumacząc go na swój język. Możesz dołączyć do naszego projektu Crowdinopen in new window aby rozpocząć pracę.

- - - diff --git a/pl_PL/dsiware-backups.html b/pl_PL/dsiware-backups.html deleted file mode 100644 index c1d9d5fea..000000000 --- a/pl_PL/dsiware-backups.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Kopie zapasowe DSiWare | Przewodnik DSi - - - - -
Przewodnik DSi

Kopie zapasowe DSiWare

Join the DS⁽ⁱ⁾ Mode Hacking! Discord server for guide development and help.

-

Wymagania

  • Najnowsza wersja GodMode9iopen in new window
    • Pobierz archiwum, rozpakuj zawartość i umieść GodMode9i.nds w dowolnym miejscu na karcie SD

Nintendo DSi - Instrukcje

Section I - Dumping the DSiWare

  1. Launch GodMode9i
  2. Press START to open the START Menu
  3. Select Title manager...
    • If this isn't shown, ensure you have your SD card and NAND mounted. If loading from hiyaCFW reload from somewhere else
  4. Select the title you want to dump
  5. Select what you want to dump
  6. Repeat steps 4-5 for all of the DSiWare you wish to dump

TIP

The dumped DSiWare will be found in sd:/gm9i/out.

- - - diff --git a/pl_PL/dumping-game-cards.html b/pl_PL/dumping-game-cards.html deleted file mode 100644 index 03ec2c37a..000000000 --- a/pl_PL/dumping-game-cards.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Zrzucanie kart gry | Przewodnik DSi - - - - -
Przewodnik DSi

Zrzucanie kart gry

Join the DS⁽ⁱ⁾ Mode Hacking! Discord server for guide development and help.

-

Ta sekcja służy do zrzucania kart z grami przy użyciu GodMode9i, aby można je było odtwarzać na emulatorach, flashcardach lub na karcie SD poprzez nds-bootstrap.

Wymagania

  • Tytuł, który chcesz zrzucić
  • Your Nintendo DSi console with Unlaunch installed

Instrukcje

Sekcja I - Konfiguracja karty SD

  1. Pobierz najnowszą wersję GodMode9iopen in new window
  2. Wyodrębnij GodMode9i.nds z archiwum GodMode9i i umieść go gdziekolwiek na karcie SD

Sekcja II – Instrukcje Nintendo DSi

  1. Launch GodMode9i
  2. Ensure the Game Card is inserted into the console
  3. Select the "NDS GAMECARD" option in GodMode9i
  4. Select what you want to dump
    • The "Trimmed" options for the ROM will dump a smaller file that can save SD card space, however they won't work for most patches such as ROM hacks
  5. Repeat steps 2-4 for all Game Cards you wish to dump

TIP

The dumped Game Cards will be found in sd:/gm9i/out.

- - - diff --git a/pl_PL/dumping-nand.html b/pl_PL/dumping-nand.html deleted file mode 100644 index bcb497718..000000000 --- a/pl_PL/dumping-nand.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Zrzucanie NAND | Przewodnik DSi - - - - -
Przewodnik DSi

Zrzucanie NAND

Join the DS⁽ⁱ⁾ Mode Hacking! Discord server for guide development and help.

-

Ta strona służy do tworzenia kopii zapasowej NAND, która jest kopią danych znajdujących się w pamięci wewnętrznej Nintendo DSi. It can be used to set up hiyaCFW, as well as no$gba and melonDS for DSi emulation.

TIP

Make sure the SD card has at least 250MB of free space, or else you'll run into an error message in dumpTool.

TIP

It is highly recommended that you do this. A NAND backup can be used as a restore point in the future, in case of a brick.

Sekcja I - Konfiguracja karty SD

TIP

If you have already downloaded dumpTool from another section of this guide, you can skip this section.

  1. Pobierz najnowszą wersję dumpToolopen in new window
  2. Umieść dumpTool.nds w dowolnym miejscu na karcie SD

Sekcja II – Dumping NAND

  1. Uruchom dumpTool przez TWiLight Menu++
  2. Naciśnij przycisk A na swoim Nintendo DSi, aby zacząć zrzucać swój NAND
    • Kopia zapasowa NAND zajmuje zazwyczaj około 7 minut
  3. Kiedy kopiowanie NAND zostanie zakończona, naciśnij przycisk START na swoim Nintendo DSi, aby wyjść z dumpTool
  4. Wyłącz konsolę i włóż kartę SD z powrotem do komputera
  5. Przechowuj tę kopię w bezpiecznym miejscu, gdzie jej nie stracisz
    • Jeśli to możliwe, utwórz wiele kopii zapasowych na różnych urządzeniach pamięci masowej
    • Po wykonaniu kopii zapasowej w innym miejscu, możesz usunąć ją z karty SD

WARNING

The SHA1 hash of the nand.bin will not match the hash stored in nand.bin.sha1. This is because dumpTool adds additional data known as a no$gba footer to the nand.bin file after the SHA1 hash is calculated. You can use the hiyaCFW Helperopen in new window to create a copy without the footer.

TIP

Continue to Installing Unlaunch (Optional)

- - - diff --git a/pl_PL/faq.html b/pl_PL/faq.html deleted file mode 100644 index 6ad008b3d..000000000 --- a/pl_PL/faq.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - FAQ | Przewodnik DSi - - - - -
Przewodnik DSi

FAQ

Join the DS⁽ⁱ⁾ Mode Hacking! Discord server for guide development and help.

-

Should I do a system update?

It is not recommended to update your DSi unless you know there are purchased DSiWare. While it still possible to follow this guide if you do so, the only benefit to updating is the ability to access the Nintendo DSi Shop to redownload already purchased titles. All other benefits, such as Facebook integration in the Nintendo DSi Camera application, are no longer usable or are not significant enough to justify the downsides:

  • Installing System Updates is known to occasionally brick consoles, with roughly the same frequency as when installing Unlaunch
  • Older exploits are no longer possible to use, which may be required if you are unable use the recommended exploits
  • Flashcard compatibility is reduced, however this is bypassed if you install Unlaunch

Which is the best exploit?

Unlaunch is overall the best exploit for the DSi, with the only downside being that there is a minor brick risk on install. In general it's recommended to use Memory Pit to install Unlaunch. If you want to avoid any risk it's recommended to instead use Flipnote Lenny as it has fewer issues in homebrew than Memory Pit while being just as safe and simple to remove. Below is a list of the pros and cons of each exploit:

Memory Pit

Pros:

  • Quick and easy to use
  • No risk of damaging the console, uninstalling is as simple as removing the SD or deleting one file
  • Compatible with all DSi consoles unless they have a broken camera and haven't completed the camera tutorial

Cons:

  • Requires loading the DSi Camera application every time you want to access homebrew
  • Incompatible with certain DSi mode titles and homebrew due to WRAM only being open to the ARM7 CPU
  • Access to Slot-1 (the DS Game Card) is blocked in homebrew
  • Access to the DSP is blocked resulting in worse sound in GBARunner2
  • Photos on the SD card cannot be viewed in the DSi Camera application while Memory Pit is installed, as this is the trigger for the exploit
    • The only way to view SD card photos while Memory Pit is installed, is to launch a ROM dump of the DSi Camera application using TWiLight Menu++ to boot it via nds-bootstrap (v0.61.3 or later)

stylehax

Pros:

  • Better compatibility with DSi mode titles and homebrew than Memory Pit
  • Easy to use
  • No risk of damaging the console
  • Useable on consoles with broken camera
  • Better sound in GBARunner2

Cons:

  • Requires internet access
  • Requires loading the DSi Browser every time you want to access homebrew, slightly more time consuming than Memory Pit
  • Access to Slot-1 (the DS Game Card) is blocked in homebrew

Flipnote Lenny

Pros:

  • Better compatibility with DSi mode titles and homebrew than Memory Pit
  • No risk of damaging the console, uninstalling is as simple as removing the SD or deleting one folder
  • Useable on consoles with broken camera
  • Better sound in GBARunner2

Cons:

  • Requires loading Flipnote Studio every time you want to access homebrew, slightly more time consuming than Memory Pit
  • Access to Slot-1 (the DS Game Card) is blocked in homebrew

Unlaunch

Pros:

  • Allows loading homebrew and DSiWare immediately on system boot, with optional button hotkeys
  • Full access to the system without any restrictions, including:
    • Access to Slot-1 allowing dumping Game Cards and loading incompatible flashcards
    • Better sound in GBARunner2
  • Removes region locks on DSi-Enhanced/Exclusive Game Cards
  • Protection against most ways a DSi could brick
  • DSi-Enhanced games can be run in DSi mode without a Donor ROM
  • Old homebrew can be run via nds-bootstrap-hb

Cons:

  • Very minor risk of bricking the console when installing
  • Another, slightly higher, risk of bricking if you decide to uninstall it
  • Not compatible with development consoles

Will I lose any functionality by modding my system?

If you install Unlaunch or use Flipnote Lenny, no functionality will be lost. If you use Memory Pit, you will be unable to view photos on the SD card using the DSi Camera, unless you launch a ROM dump of the DSi Camera application using TWiLight Menu++ to boot it via nds-bootstrap.

  • To regain the ability to view your SD card photos when launching the DSi Camera from the DSi Menu, install Unlaunch or switch to a different exploit, then delete Memory Pit's pit.bin file
    • If tip.bin exists in the same folder, rename it back to pit.bin

How do I play Nintendo DS Game Card dumps?

Playing Game Card dumps on the console requires the use of a flashcard or nds-bootstrap, a program which enables games to be played from the internal SD card by redirecting Slot-1 reads and writes to it.

  • With TWiLight Menu++ you can navigate your SD card to find ROM files to play with nds-bootstrap. The advantages to using TWiLight Menu++ are having a cheat menu, per-game settings, and avoiding the restrictions that forwarders bring. In other words, you can drop your ROM files directly and play without any setup. There is no 39 title limit, neither hiyaCFW or Unlaunch are required and there are no restrictions on SD card free space you can have
  • hiyaCFW users can create forwarders for the SDNAND's DSi Menu using the DS Game Forwardersopen in new window guide on the DS-Homebrew Wiki, but it has some limitations. There is a hard limit of 39 titles, and they are less convenient to make than using TWiLight Menu++

How do I update my homebrew?

  • Unlaunch - Follow the instructions on the Installing Unlaunch page
    • You do not need to uninstall Unlaunch before doing this
  • hiyaCFW - Replace hiya.dsi on the root of the SD card from the updated releaseopen in new window
  • TWiLight Menu++ - Follow the instructions on the DS-Homebrew Wikiopen in new window
  • nds-bootstrap - Copy nds-bootstrap-hb-release.nds & nds-bootstrap-release.nds to the _nds folder on the root of your SD card
    • If you use TWiLight Menu++, there is a high chance that the latest nds-bootstrap release is included with TWiLight Menu++
  • GodMode9i, dumpTool, Forwarder3-DS, etc - Follow the instructions used to download them

Other homebrew might use other methods to update.

I am new or I would like to redo my setup. Where do I start?

  • If you have not already modified your console or are looking to update Unlaunch on your system, we recommend starting from the beginning of the guide and following through the pages. Be sure to read everything on the homepage
  • If you have the latest version Unlaunch, follow the TWiLight Menu++ install guideopen in new window to set up TWiLight Menu++ on your system

How can I remove parental controls?

Can I change my Nintendo DSi's region?

Yes, there are a few different methods depending on what you want to change:

What happened to the hiyaCFW installation guide?

Because hiyaCFW does not serve much functional purpose and was a problematic and confusing part of the guide for many users, it was moved to the DS-Homebrew Wikiopen in new window.

  • If you were linked to the page in question from another guide, the instructions you were following were most likely outdated. Please use this guide instead, as it is maintained constantly by the developers of these projects

What kind of SD card should I use?

  • You should buy an SD card from a trusted brand
  • A full-size SD card or a microSD card with an adapter will both work
  • Any capacity between 1 GB and 2 TB will work. For general usage, 8 GB is enough
    • Some software, such as hiyaCFW, may experience incrementally longer loading times with larger SD card capacities
  • Speed class 8 or higher is recommended

Can I use my DSi SD card on other systems?

Generally, yes, with two exceptions:

  • hiyaCFW will only work on the system it was set up for
  • Even if you are using nds-bootstrap or a flashcard, friend codes in online NDS games will be reset when attempting to go online using a different console

How do I switch to a new SD card after setting up homebrew?

Format your new SD card using the SD Card Setup instructions, then simply move your data from the old SD card to the new one.

Can I still use my system normally without the SD card inserted after setting up homebrew?

Yes. If you did not install Unlaunch, your system will remain completely unmodified. If you did install Unlaunch, you may need to configure Unlaunch to automatically boot the original DSi Menu under specified conditions.

The Unlaunch pageopen in new window says that version 2.0 is not known to be safe. Should I use a previous version instead?

The Unlaunch page has not been updated since version 2.0 was released, which was over two years ago. The vast majority of users experience no issues with this version, so it is considered safe.

How do I run dumped DSiWare?

The recommended method is to simply launch them with TWiLight Menu++, due to the simple drag-and-drop method and there being no arbitrary limit. When nds-bootstrap is set as the launch method, it also gains the benefits of cheats and screenshots, as well as any other benefit provided by the in-game menu.

However, for the few titles that are incompatible, you can use NTMopen in new window to install them on either internal memory or hiyaCFW's SDNANDopen in new window. In addition to lacking the benefits above, there is also a limit of 39 titles that cannot exceed 128 MiB/1,024 blocks in size. For SysNAND, there is also a very small risk of bricking the system when writing to the internal NAND.

- - - diff --git a/pl_PL/file-extensions-windows.html b/pl_PL/file-extensions-windows.html deleted file mode 100644 index 3090792c6..000000000 --- a/pl_PL/file-extensions-windows.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Rozszerzenia plików (Windows) | Przewodnik DSi - - - - -
Przewodnik DSi

Rozszerzenia plików (Windows)

Join the DS⁽ⁱ⁾ Mode Hacking! Discord server for guide development and help.

-

Jest to dodatek wyłączający domyślne zachowanie systemu Windows polegające na ukrywaniu rozszerzeń plików, co znacznie ułatwi odnalezienie plików, do których odwołuje się przewodnik.

  1. Uruchom Eksplorator plików poprzez otworzenie dowolnego katalogu, np. folderu karty SD
  2. Click the "View" option on the top bar
    • If the option is not present, click the ··· button on the rightmost part of the top bar
  3. Click or hove your cursor on the Show > submenu
  4. Check the option labeled File name extensions Screenshot of hovering the "File name extensions" checkbox on Windows 11
  1. Uruchom Eksplorator plików poprzez otworzenie dowolnego katalogu, np. folderu karty SD
  2. Click the "View" option on the ribbon menu
  3. Check the box labeled "File name extensions" Screenshot of hovering the "File name extensions" checkbox on Windows 10
  1. Open the start menu by clicking on it or using the Windows key
  2. Search for "Folder Options" and select the corresponding result Screenshot of a search for "folder options" in the Windows 7 Start Menu
  3. Click the "View" option at the top of the Folder Options menu
  4. Make sure the box labeled "Hide extensions for known file types" is unchecked Screenshot of the "Folder Options" window on Windows 7 with "Hide extensions for known types" turned off
- - - diff --git a/pl_PL/get-started.html b/pl_PL/get-started.html deleted file mode 100644 index 77c116203..000000000 --- a/pl_PL/get-started.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Get Started | Przewodnik DSi - - - - -
Przewodnik DSi

Get Started

Join the DS⁽ⁱ⁾ Mode Hacking! Discord server for guide development and help.

-

The main homebrew application this guide has you install is TWiLight Menu++, which is an upgrade/replacement to the Nintendo DSi Menu that allows running other homebrew applications, retail DS games, emulators for various older systems, and more.

We'll begin with downloading it as well as some other homebrew tool(s), in preparation for the exploit steps.

Wymagania

Section I - Prep Work

WARNING

Ensure your SD card is formatted correctly.

  1. Insert your SD card into your PC
  2. Download the latest release of TWiLight Menu++open in new window
  3. Pobierz najnowszą wersję dumpToolopen in new window
  4. Copy the _nds folder from TWiLightMenu-DSi.7z to the root of your SD card
  5. Copy the BOOT.NDS file from TWiLightMenu-DSi.7z to the root of your SD card
  6. Copy the dumpTool.nds file to the root of your SD card

TIP

Unsure what the SD "root" is? See this imageopen in new window

Section II - Selecting an exploit

From here you have three options, with a minor difference in what each entails.

Installing Unlaunch via Memory Pit

Memory Pit is an exploit utilizing the DSi Camera, compatible with all firmware versions. Optionally, this exploit can be used to install Unlaunch, a bootcode exploit that allows full control of the console on boot.

As Memory Pit is somewhat limited in homebrew compatibility, it is recommended to install Unlaunch, instead of using Memory Pit standalone. As this is the easiest method to install Unlaunch, this is the recommended path. However, there is a very minor risk of bricking your console when installing Unlaunch, so if this is a concern, see the alternate method below.

TIP

Continue to Launching the Exploit

stylehax

stylehax is an exploit utilizing the DSi Browser application, and can be used as an alternative to Memory Pit for installing Unlaunch (explained above) if your DSi has a broken camera.

For an Unlaunch-free experience, this exploit is recommended as using Memory Pit causes issues in some games and homebrew.

TIP

Continue to Launching the Exploit (stylehax)

Flipnote Lenny

Flipnote Lenny is an exploit utilizing the Flipnote Studio application.

If you have Flipnote Studio and do not plan on installing Unlaunch (explained above), this exploit is recommended for the same reason as stylehax.

You can always install Unlaunch later if you decide later on that you want it.

TIP

Continue to Launching the Exploit (Flipnote Lenny)

For a more detailed pros and cons comparision of the available exploits, please see the Which is the best exploit? FAQ.

- - - diff --git a/pl_PL/index.html b/pl_PL/index.html deleted file mode 100644 index d429513e2..000000000 --- a/pl_PL/index.html +++ /dev/null @@ -1,43 +0,0 @@ - - - - - - - - - Dom | Przewodnik DSi - - - - -
Przewodnik DSi

Przewodnik DSi

Kompletny przewodnik do modyfikacji twojego Nintendo DSi

TIP

Aby uzyskać całkowity przewodnik do homebrew i niestandardowych firmware dla innych urządzeń, sprawdź poradnik CFW.Poradnikopen in new window.

TIP

Dokładnie przeczytaj wszystkie strony wprowadzające (łącznie z tą!) przed przystąpieniem do pracy.

Czym jest homebrew?

Aplikacje Homebrewopen in new window są nielicencjonowanymi programami stworzonymi dla systemów zamkniętych, takich jak Nintendo DSi. Aplikacje te mogą obejmować zarówno programy użytkowe, jak i niestandardowe gry homebrew.

Homebrew można uruchomić za darmo na wszystkich konsolach Nintendo DSi, niezależnie od wersji firmware'u czy regionu. Wszystko, czego potrzebujesz, to punkt wejścia i karta SD do przechowywania swojego homebrew. Główny punkt wejścia użyty w tym poradniku nazywa się Memory Pit, ale istnieją inne punkty wejścia, których możesz użyć, jeśli Memory Pit jest dla ciebie bezużyteczny.

What can I do by modding my system?

  • Run Nintendo DS(i) game backups or ROM hacks from your DSi SD card without the need of a flashcard
  • Launch any DSiWare from your SD card
    • This means out-of-region and 3DS-exclusive DSiWare will also work
  • Boot into DSiWare and homebrew applications by holding specific buttons when turning on your Nintendo DSi
  • Run old-time classics using various emulators
  • Use normally incompatible flashcards
  • Redirect your NAND to the SD card using hiyaCFW
  • Watch your favorite movies using either FastVideoDSPlayer or tuna-viDS
    • FastVideoDSEncoder requires a CPU supporting AVX2 (newer CPUs will likely support it)
  • Display an image (referred to as the boot splash) on system launch
  • Play homebrew games

Where can I find homebrew applications?

What should I know before starting?

  • On Windows, it's recommended to show file extensions if you are using the default File Explorer
  • The only brick risk comes from installing Unlaunch, and the brick risk is minimal

TIP

Continue to Get Started

- - - diff --git a/pl_PL/installing-unlaunch.html b/pl_PL/installing-unlaunch.html deleted file mode 100644 index 6d2eaab2e..000000000 --- a/pl_PL/installing-unlaunch.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Instalacja Unlaunch | Przewodnik DSi - - - - -
Przewodnik DSi

Instalacja Unlaunch

Join the DS⁽ⁱ⁾ Mode Hacking! Discord server for guide development and help.

-

DANGER

If you have not yet done so, please follow Dumping NAND. While the chances are slim, Unlaunch can accidentally brick your Nintendo DSi. A NAND backup + hardmodopen in new window would allow you to restore this backup, provided you know how to solder.

WARNING

Make sure your console is charged when following this process. A sudden power loss could result in serious damage.

WARNING

Unlaunch is not compatible with Nintendo DSi development consoles.

Sekcja I - Konfiguracja karty SD

  1. Pobierz najnowszą wersję Unlaunchopen in new window
  2. Wypakuj UNLAUNCH.DSI z archiwum unlaunch.zip i umieść go w dowolnym miejscu na swojej karcie SD
  3. Zweryfikuj TWiLight Menu++ na karcie SD

Sekcja II - Instalacja/aktualizacja Unlaunch

  1. Otwórz TWiLight Menu++
    • If this is your first time installing Unlaunch, relaunch TWiLight Menu++ through the exploit that you used
    • If you have already installed Unlaunch and are looking to update it, hold A + B while booting and select the option labeled TWiLight Menu++
    • If several options are labeled TWiLight Menu++, select the option in where BOOT.NDS is shown at the end of the path on the bottom screen
  2. Uruchom Ustawienia TWiLight Menu++
    • If you haven't changed your theme, press SELECT and touch the small DS icon on the bottom of the touch screen. Otherwise, see the TWiLight Menu++ Manual
  3. Naciśnij L / R lub X / Y, aż dojdziesz do strony Ustawienia Unlaunch
  4. Jeśli chcesz zmienić obraz tła Unlauncha, wybierz Tło i wybierz to, które chcesz
  5. Exit TWiLight Menu++ Settings
  6. In the file navigation menu, launch Unlaunch DSi Installer
    • If you see two black screens after launching, download GodMode9iopen in new window, put its .dsi file on the SD root, then launch GodMode9i using TWiLight Menu++, and start Unlaunch.dsi
      This method does not enable Unlaunch to use custom patches and background
  7. Select the "install now" option
    • If Unlaunch freezes at ERROR: MISMATCH IN FAT COPIES, please take a look at the Troubleshooting page
  8. When completed, reboot your system

If you see Unlaunch's Filemenu screen at this point, you have successfully modded your Nintendo DSi.

Sekcja III - Konfiguracja po-Unlaunch

Currently, Unlaunch defaults to launching its Filemenu on boot, but this can be changed launch whatever you want.

  1. Włącz konsolę przytrzymując A i B
    • To powinno uruchomić Unlaunch Filemenu
    • If only the background is shown, or if no files from the SD card are shown (ex. TWiLight Menu++), then you'll need to reformat the SD card
  2. Przejdź do OPTIONSi spójrz na dostępne opcje
    • A + B jest zakodowane, aby uruchomić w menu Unlaunch i jako takie nie może być zmienione
    • Opcje NO BUTTON i BUTTON A / B / X / Y mogą być ustawione jakkolwiek chcesz i będą wybierać co twój DSi załaduje przy starcie w zależności od tego, które przyciski są trzymane. Możesz wybrać dowolne DSiWare, homebrew, kartę Pola-1, wifiboot lub menu plików Unlaunch
      • For TWiLight Menu++, select TWiLight Menu++
      • Dla oryginalnego menu DSi wybierz Launcher
    • LOAD ERROR jest tym, co DSi pokaże, jeśli załadowanie plików się nie powiedzie, np. karta SD nie została włożona
  3. Select SAVE & EXIT to save your settings, then turn off your DSi

Sekcja IV - Czyszczenie karty SD

TIP

This section is optional and only serves for keeping your SD card tidy of files you won't need.

  • Delete the sd:/private/ds/app/484E494A/pit.bin file from your SD card
    • If tip.bin still exists, then rename it back to pit.bin
  • You can now restore the DCIM folder that was on the root of your SD card, if this folder existed
  • Usuń plik UNLAUNCH.DSI z karty SD
  • Delete the 800031_104784BAB6B57_000.ppm and T00031_1038C2A757B77_000.ppm files from inside the following folders:
    • sd:/private/ds/app/4B47554A/001 (Japan)
    • sd:/private/ds/app/4B475545/001 (USA)
    • sd:/private/ds/app/4B475556/001 (Europe/Australia)
    • You can also delete the entire folders for the regions besides your own
  • Usuń plik UNLAUNCH.DSI z karty SD
- - - diff --git a/pl_PL/launching-the-browser-exploit.html b/pl_PL/launching-the-browser-exploit.html deleted file mode 100644 index 8e85ec2ca..000000000 --- a/pl_PL/launching-the-browser-exploit.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Launching the Exploit (stylehax) | Przewodnik DSi - - - - -
Przewodnik DSi

Launching the Exploit (stylehax)

Join the DS⁽ⁱ⁾ Mode Hacking! Discord server for guide development and help.

-

We'll start by first launching our exploit. For the best Unlaunch-free experience, or if the DSi camera is broken to install Unlaunch, we recommend using an exploit called "stylehax" which takes advantage of a flaw in how the DSi Browser application handles webpages.

Uruchomienie exploita spowoduje uruchomienie TWiLight Menu++, aplikacji homebrew, która działa jako zamiennik Menu DSi.

Wymagania

  • Nintendo DSi Browser installed on your Nintendo DSi
    • If you do not have the DSi Browser, then use Memory Pit instead

Launching the exploit

  1. Ensure your SD card is inserted into your Nintendo DSi
  2. Boot your Nintendo DSi and launch the DSi Browser application
  3. Touch the Go to Page button
    • The button will have a green www icon
  4. Type opera:about, and touch Go to load the page
  5. Touch the HOME icon
  6. Touch the Go to Page button
  7. Type stylehax.net, and touch Go to load the page

TIP

The exploit should take 21 seconds to take effect. If it takes longer than 30 seconds, then reboot, and try again.

WARNING

If the top screen turns green, you do not have TWiLight Menu++'s BOOT.NDS on the root of your SD card. Follow the prep work again.

You can now use TWiLight Menu++! First, it will ask you to select your language and region. These do not need to match your console's language or region, so set them to whichever you prefer. Next, it's recommended to continue on and make a NAND backup. This can potentially be used to save your console if anything bad happens in the future.

TIP

Continue to Dumping NAND

- - - diff --git a/pl_PL/launching-the-exploit.html b/pl_PL/launching-the-exploit.html deleted file mode 100644 index b477178d2..000000000 --- a/pl_PL/launching-the-exploit.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Uruchamianie Eksploratora | Przewodnik DSi - - - - -
Przewodnik DSi

Uruchamianie Eksploratora

Join the DS⁽ⁱ⁾ Mode Hacking! Discord server for guide development and help.

-

Zaczniemy od skonfigurowania karty SD do uruchomienia naszego exploita. Dla większości użytkowników zalecamy użycie exploita o nazwie "Memory Pit", który wykorzystuje lukę w sposobie obsługi metadanych obrazu przez aplikację Nintendo DSi Camera.

Uruchomienie exploita spowoduje uruchomienie TWiLight Menu++, aplikacji homebrew, która działa jako zamiennik Menu DSi.

TIP

If you don't plan on installing Unlaunch and have either the DSi Browser or Flipnote Studio, it is recommended to use either stylehax or Flipnote Lenny instead. Which is the best exploit?

Section I - Checking your DSi Camera Version

  1. Power on your console
  2. Open Nintendo DSi Camera
    • If you are prompted to complete the camera tutorial, do so now
    • If the tutorial crashes as you try to complete it, your Nintendo DSi camera hardware is likely broken in some way and you will not be able to use Memory Pit. Please use an alternate exploit
  3. Open the album using the large button on the right
  4. Take note of whether you have a Facebook icon alongside the star, clubs, and heart, outlined in red here: Screenshot of where the Facebook icon is located

Section II - Memory Pit

  1. Download the correct Memory Pit binary for your Nintendo DSi Camera version:
  2. Navigate to the sd:/private/ds/app/484E494A/ folder on your SD card
    • You will already have this directory if you have previously taken photos to your SD card via the Nintendo DSi Camera application. If so, you do not need to delete it and recreate it
    • If it does not exist, please create the individual folders
  3. If there is already a pit.bin file in that path, rename it to tip.bin
  4. Place the Memory Pit pit.bin file in this folder
  5. If there's a folder named DCIM in the root of your SD card, make a back up of it so you don't lose the pictures inside, and then remove it from the SD card

Section III - Launching the exploit

  1. Ensure your SD card is inserted into your Nintendo DSi
  2. Boot your Nintendo DSi and launch the Nintendo DSi Camera application
  3. Select the SD Card icon in the top-right
    • If you receive a message saying your SD card isn't inserted, please use another SD card
    • If you receive a message saying that your SD card cannot be used, ensure your SD card is formatted correctly
  4. Open the album using the large button on the right
    • The screen should flash magenta if Memory Pit was copied correctly

WARNING

If the top screen turns green, you do not have TWiLight Menu++'s BOOT.NDS on the root of your SD card. Follow the prep work again.

WARNING

If you enter the SD card camera album and nothing unusual happens, ensure that you downloaded the correct version of Memory Pit for your version and region, and placed it into the correct folder on your SD card. Also ensure that the DCIM folder does not exist on your SD card.

You can now use TWiLight Menu++! First, it will ask you to select your language and region. These do not need to match your console's language or region so set them to whichever you prefer. Next it's recommended to continue on and make a NAND backup. This can potentially be used to save your console if anything bad happens in the future.

TIP

Continue to Dumping NAND

- - - diff --git a/pl_PL/launching-the-flipnote-exploit.html b/pl_PL/launching-the-flipnote-exploit.html deleted file mode 100644 index ebdb03112..000000000 --- a/pl_PL/launching-the-flipnote-exploit.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Launching the Exploit (Flipnote Lenny) | Przewodnik DSi - - - - -
Przewodnik DSi

Launching the Exploit (Flipnote Lenny)

Join the DS⁽ⁱ⁾ Mode Hacking! Discord server for guide development and help.

-

Zaczniemy od skonfigurowania karty SD do uruchomienia naszego exploita. For the best Unlaunch-free experience, we recommend using an exploit called "Flipnote Lenny" which takes advantage of a flaw in how the Flipnote Studio application handles flipnotes.

Uruchomienie exploita spowoduje uruchomienie TWiLight Menu++, aplikacji homebrew, która działa jako zamiennik Menu DSi.

Wymagania

  • Flipnote Studio installed on your Nintendo DSi
    • If you do not have Flipnote Studio, then use Memory Pit instead

Sekcja I - Konfiguracja karty SD

  1. Download the latest version of Flipnote Lennyopen in new window
  2. Copy the private folder from the Flipnote Lenny archive to the root of your SD card

Section II - Launching the exploit

  1. Ensure your SD card is inserted into your Nintendo DSi
  2. Boot your Nintendo DSi and launch the Flipnote Studio application
    • If you receive a message saying that your SD card cannot be used, ensure your SD card is formatted correctly
  3. Open the Flipnote Studio settings on the top-right of the main menu and ensure that Start on Calendar is disabled and Frog is enabled
  4. View the flipnotes stored on the SD card
    • If you are unable to view the flipnotes on the SD card, please use another SD card
  5. Tap on the face corresponding to your region
    • If you have an AUS console, select EUR
  6. Edit the selected flipnote
  7. Tap the frog icon on the bottom-left
  8. Tap on the film roll icon
  9. Select Copy -> Back -> Exit
  10. Tap on the second note with a larger face, and select Edit
  11. Tap on the frog icon on the bottom-left
  12. Tap on the film roll icon
  13. Select paste

WARNING

If the top screen turns green, you do not have TWiLight Menu++'s BOOT.NDS on the root of your SD card. Follow the prep work again.

You can now use TWiLight Menu++! First, it will ask you to select your language and region. These do not need to match your console's language or region, so set them to whichever you prefer. Next, it's recommended to continue on and make a NAND backup. This can potentially be used to save your console if anything bad happens in the future.

TIP

Continue to Dumping NAND

- - - diff --git a/pl_PL/lazy-dsi-downloader.html b/pl_PL/lazy-dsi-downloader.html deleted file mode 100644 index 256312961..000000000 --- a/pl_PL/lazy-dsi-downloader.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Lazy DSi Downloader | Przewodnik DSi - - - - -
Przewodnik DSi

Lazy DSi Downloader

Join the DS⁽ⁱ⁾ Mode Hacking! Discord server for guide development and help.

-

"Lazy DSi Downloader" jest narzędziem upraszczającym proces modyfikacji konsoli Nintendo DSi.

Etapy weryfikacji

  1. Włącz swój Nintendo DSi
  2. Uruchom aplikację Nintendo DSi Camera

If at this point you get a tutorial and crash when trying to follow it, then you cannot use Memory Pit.

Poradnik konfiguracji

  1. Download the latest release of Lazy DSi File Downloaderopen in new window for your OS
  2. Launch it via the instructions for your operating system listed in the release page
  3. Hit the Next button
    • The intro text isn't mandatory to read
  4. If your Nintendo DSi crashed during the verification steps above, toggle off the Memory Pit option
  5. Hit the check boxes for "Download latest GodMode9i version?"
    • Feel free to select any of the other homebrew applications in Click to add Additional homebrew..., but this is not mandatory
  6. Wait for everything to download, then hit Finish
- - - diff --git a/pl_PL/restoring-nand.html b/pl_PL/restoring-nand.html deleted file mode 100644 index 59d2958d8..000000000 --- a/pl_PL/restoring-nand.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Przywracanie kopii zapasowej NAND | Przewodnik DSi - - - - -
Przewodnik DSi

Przywracanie kopii zapasowej NAND

Join the DS⁽ⁱ⁾ Mode Hacking! Discord server for guide development and help.

-

DANGER

OSTRZEŻENIE! To jest niebezpieczne. Nawet podążając za tymi krokami, nadal istnieje potencjał do zablokowania DSi, ponieważ NAND jest bardzo niskiej jakości, zwłaszcza jeśli flashujesz wiele razy! Powinno to być stosowane tylko w ostateczności!

TIP

Nie pomiń niczego na tej stronie, jakikolwiek błąd znacznie zwiększa szansę na zablokowanie twojego DSi.

Po pierwsze, kilka bezpieczniejszych alternatyw dla tego:

  • Instalacja DSiWare może być wykonana za pomocą hiyaCFW lub TWiLight Menu++
  • Recovering pictures can be done using ninfsopen in new window, in combination with hiyaCFW or TWiLight Menu++ if you want them on console. The latest version of the HiyaCFW Helper allows you to copy your photos from your NAND to the SDNAND during setup
  • Restoring an Unlaunch button configuration can be done from the Unlaunch menu, which can be accessed by holding A + B while powering the console on
  • Uruchamianie w Unlaunch skutkujące błędem? Take out your SD card and try starting the system again. Jeśli zadziała, to jest to błąd na twojej karcie SD i przywrócenie kopii zapasowej NAND tego nie naprawi
  • "An error has occurred..." on boot is likely a hiyaCFW error and is not related to your NAND, see hiyaCFW FAQ & Troubleshootingopen in new window for more information
  • Any errors in TWiLight Menu++ are unrelated and you should try reinstalling TWiLight Menu++ or ask for help on Discordopen in new window
  • Odinstalowanie Unlauncha, czy to poprzez flashowanie NAND czy użycie deinstalatora, powinno być unikane, chyba że jest to absolutnie konieczne, możesz ustawić klucze autobootu na "Launcher" i DSi będzie jak nowy

Jedyną rzeczą, którą powinieneś zrobić ze swoją pamięcią NAND jest instalacja Unlaunch. W przeciwnym razie należy korzystać z innych rozwiązań.

Wymagania

Zrzucenie BIOS do użycia w no$gba

  1. Wypakuj dsibiosdumper.nds z archiwum dsibiosdumper.zip i umieść go w dowolnym miejscu na karcie SD
  2. Włącz konsolę przytrzymując A i B
    • To powinno uruchomić Unlaunch Filemenu
  3. Uruchom dsibiosdumper z Unlaunch Filemenu
  4. Naciśnij A aby zrzucić BIOS do karty SD
  5. Naciśnij START aby wyjść z dsibiosdumpera

Testowanie kopii zapasowej NAND

Bardzo ważne jest, aby sprawdzić, czy kopia zapasowa NAND działa przed próbą przywrócenia jej na konsolę, jeśli pokaże zablokowanie w no$gba, najprawdopodobniej zablokuje również konsolę.

  1. Wyodrębnij NO$GBA.EXE z no$gba-w.zip do folderu na komputerze
  2. Skopiuj swoją kopię zapasową NAND do folderu, w którym umieściłeś NO$GBA.EXE i zmień nazwę na DSI-1.MMC
  3. Skopiuj bios7i.bin i bios9i.bin do folderu, w którym umieściłeś NO$GBA. XE, nazwany odpowiednio BIOSDSI7.ROM i BIOSDSI9.ROM.
  4. Uruchom NO$GBA.EXE
  5. Kliknij Options > Emulation Setup aby otworzyć okno konfiguracji Emulacji
  6. Zmień Reset/Startup Entrypoint na GBA/NDS BIOS (logo Nintendo)
  7. Zmień NDS Mode/Colors na DSi (retail/16MB)
  8. Kliknij OK
  9. Uruchom dowolny ROM NDS (plik .nds)

If no$gba loads the DSi menu (or the Unlaunch Filemenu), then continue to the next section. Jeśli pokaże jakikolwiek błąd nie flashuj(nie wgrywaj) tej kopii zapasowej!

Uninstalling Unlaunch from your NAND backup (optional)

Follow this if you dumped your NAND backup after you installed Unlaunch and you would like to uninstall Unlaunch from your system. If you are not trying to uninstall Unlaunch, you do not need to do this section.

  1. Download the latest version of the Unlaunch installeropen in new window
  2. Extract UNLAUNCH.DSI from unlaunch.zip
  3. Launch UNLAUNCH.DSI in no$gba and start it from the Game Card slot
    • This should start the Unlaunch installer, which looks similar to to the Unlaunch Filemenu
  4. Choose Uninstall
  5. Once complete, choose Power down
  6. Launch any Nintendo DS ROM again, and ensure your DSi menu loads and is working properly

If no$gba shows any kind of error instead of loading the DSi menu, do not flash that backup! If you have an older NAND backup you may want to try using that instead. Do not try to uninstall Unlaunch using its uninstaller on the console, it is extremely likely doing so will brick your DSi.

Wgrywanie kopii zapasowej NAND (Urządzenie)

DANGER

Make sure you have read through the above steps as this is where it gets dangerous. If you were linked directly to here without following the above, then go back to the top and read this whole page.

DANGER

Make sure your Nintendo DSi system is well charged before beginning this section.

  1. Po włożeniu karty SD włącz Nintendo DSi, trzymając A i B
  2. Uruchom SafeNANDManager
  3. Naciśnij begin NAND restore
  4. Po zakończeniu przywracania, naciśnij START, aby wyłączyć DSi

Your NAND should now be restored.

Wgrywanie kopii zapasowej NAND (Hardmod)

If you cannot boot your Nintendo DSi, a hardmod is the only way to restore a NAND backup. The best guide that currently exists is the Nintendo DSi hardmod guide on the DS-Homebrew Wikiopen in new window.

- - - diff --git a/pl_PL/sd-card-setup.html b/pl_PL/sd-card-setup.html deleted file mode 100644 index 7435f043d..000000000 --- a/pl_PL/sd-card-setup.html +++ /dev/null @@ -1,85 +0,0 @@ - - - - - - - - - Konfiguracja karty SD | Przewodnik DSi - - - - -
Przewodnik DSi

Konfiguracja karty SD

Join the DS⁽ⁱ⁾ Mode Hacking! Discord server for guide development and help.

-

This page is for preparing your SD card for your device. In the process, we'll format the SD card and check the card for errors.

DANGER

Upewnij się, że stworzyłeś kopię zapasową karty SD PRZED Zaczęciem konfiguracji. Twoja karta SD będzie zresetowana w tym procesie.

Section I - Formatting your SD card with SD Formatter

TIP

This section formats the SD card to the specifications by the SD Card Association. This can fix many issues that may occur with running homebrew applications.

DANGER

Any 64GB or larger SD cards will be formatted to exFAT in this process. You must follow Section II to re-format to FAT32.

  1. Download the latest version of SD Formatteropen in new window
  2. Run SD Card Formatter Setup (the .exe file) in the downloaded .zip file with Adminstrator privileges, then install the program
  3. Run SD Card Formatter from the Start Menu with Adminstrator privileges
  4. Select your SD card
  5. Upewnij się, że pole wyboru Quick Format jest zaznaczone
  6. Press Format to start the format process Screenshot of SD Card Formatter on Windows 11

Section II - Formatting your SD card with GUIFormat

This section formats SD cards larger than 32GB to FAT32.

TIP

If your SD card is 32GB or less in capacity, skip to Section III.

  1. Pobierz najnowszą wersję GUIFormatopen in new window
    • Kliknij na zdjęcie na stronie internetowej, aby pobrać aplikację
  2. Uruchom GUIFormat z uprawnieniami administratora
  3. Wybierz literę dysku
  4. Set the Allocation size unit to 32768
    • Jeśli jest on zbyt duży dla twojego SD, ustaw go na najwyższy, który działa
  5. Upewnij się, że pole wyboru Quick Format jest zaznaczone
  6. Rozpocznij proces formatowania

Sekcja III – Sprawdzanie błędów

  1. Przejdź do okna właściwości karty SD
    • Menedżer Plików -> Ten komputer -> Kliknij prawym przyciskiem myszy na kartę SD -> Właściwości
  2. W zakładce Narzędzia wybierz Sprawdź teraz
  3. Sprawdź Automatycznie napraw błędy systemu plików i Skanowanie i próba odzyskania złych sektorów
  4. Rozpocznij proces sprawdzania

Spowoduje to skanowanie karty SD i poprawienie wszelkich wykrytych przez nią błędów.

Sekcja IV - Sprawdzanie odczytu/zapisu karty SD

  1. Pobierz i rozpakuj archiwum h2testwopen in new window w dowolnym miejscu na komputerze
    • If the above link doesn't work for you, download from archive.orgopen in new window
    • Można go również rozpakować na urządzeniu zewnętrznym, o ile to urządzenie zewnętrzne nie jest twoją kartą SD
  2. Z kartą SD włożoną do komputera, uruchom h2testw.exe
  3. Wybierz język, w którym chcesz zobaczyć h2testw
  4. Ustaw literę napędu karty SD jako swój cel (dysk główny to zazwyczaj C:)
  5. Upewnij się, że all available space jest zaznaczone
  6. Kliknij Write + Verify
  • Poczekaj do zakończenia procesu

TIP

If the test shows the result Test finished without errors, your SD card is healthy and you can delete all .h2w files on your SD card.

DANGER

Jeśli test pokazuje inne wyniki, karta SD może być uszkodzona, i być może będziesz musiał ją wymienić!

TIP

If TWiLight Menu++ fails to start after following this method, please follow the Windows method instead, by either rebooting to Windows or running a Windows Virtual Machine

Sekcja I - Formatowanie karty SD

  1. Upewnij się, że Twoja karta SD nie jest włożona do maszyny Linux
  2. Uruchom Terminal Linux
  3. Wpisz watch "lsblk"
  4. Włóż kartę SD do urządzenia Linux
  5. Obserwuj wyniki. Powinny wyglądać podobnie:
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
-mmcblk0     179:0    0   3,8G  0 disk
-└─mmcblk0p1 179:1    0   3,7G  0 part /run/media/user/FFFF-FFFF
-
  1. Take note of the device name. In our example above, it was mmcblk0p1
    • Jeśli RO jest ustawione na 1, upewnij się, że przełącznik blokady nie jest przesunięty w dół
    • Make sure you're targetting the partition, mmcblk0p1 not mmcblk0
  2. Naciśnij CTRL + C, aby wyjść z menu
  3. Follow the instructions relevant to your SD card's capacity:
    • 2GB or lower: sudo mkdosfs /dev/(device name from above) -s 64 -F 16
      • This creates a single FAT16 partition with 32 KB cluster size on the SD card
    • 4GB or higher: sudo mkdosfs /dev/(device name from above) -s 64 -F 32
      • This creates a single FAT32 partition with 32 KB cluster size on the SD card

Sekcja II – Używanie F3

  1. Pobierz i rozpakuj archiwum F3open in new window w dowolnym miejscu na swoim komputerze.
  2. Uruchom terminal w katalogu F3
  3. Uruchom make aby skompilować F3
  4. Z kartą SD włożoną, uruchom ./f3write <your sd card mount point>
    • Poczekaj do zakończenia procesu. Poniżej przedstawiono przykładowe wyniki:
    $ ./f3write /media/michel/6135-3363/
-Free space: 29.71 GB
-Creating file 1.h2w ... OK!
-...
-Creating file 30.h2w ... OK!
-Free space: 0.00 Byte
-Average Writing speed: 4.90 MB/s
-
  5. Run ./f3read <your sd card mount point>
  • Poczekaj do zakończenia procesu. Poniżej przedstawiono przykładowe wyniki:
    $ ./f3read /media/michel/6135-3363/
-                  SECTORS      ok/corrupted/changed/overwritten
-Validating file 1.h2w ... 2097152/        0/      0/      0
-...
-Validating file 30.h2w ... 1491904/        0/      0/      0
-
-   Data OK: 29.71 GB (62309312 sectors)
-Data LOST: 0.00 Byte (0 sectors)
-            Corrupted: 0.00 Byte (0 sectors)
-   Slightly changed: 0.00 Byte (0 sectors)
-         Overwritten: 0.00 Byte (0 sectors)
-Average Reading speed: 9.42 MB/s
-

TIP

If the test shows the result Data LOST: 0.00 Byte (0 sectors) your SD card is healthy and you can delete all .h2w files on your SD card.

DANGER

Jeśli test pokazuje inne wyniki, karta SD może być uszkodzona, i być może będziesz musiał ją wymienić!

Section I - Formatting your SD card with SD Formatter

TIP

This section formats the SD card to the specifications by the SD Card Association. This can fix many issues that may occur with running homebrew applications.

DANGER

Any 64GB or larger SD cards will be formatted to exFAT in this process. You must follow Section II to re-format to FAT32.

  1. Download the latest version of SD Formatteropen in new window
    • Accept the End User License Agreement to start the download
  2. Run Install SD Card Formatter (the .mpkg file) in the downloaded .zip file
  3. Run SD Card Formatter
  4. Select your SD card
  5. Upewnij się, że pole wyboru Quick Format jest zaznaczone
  6. Rozpocznij proces formatowania

Section II - Formatting your SD card with Disk Utility

This section formats SD cards larger than 32GB to FAT32.

TIP

If your SD card is 32GB or less in capacity, skip to Section III.

OS X El Capitan (10.11) i później

  1. Uruchom aplikację na dysku
  2. Wybierz Show All Devices w panelu View
  3. Wybierz kartę SD z paska bocznego
    • Upewnij się, że wybrałeś właściwe urządzenie, w przeciwnym razie możesz przypadkowo usunąć zły napęd!
  4. Kliknij Erase na górze
  5. Upewnij się, że Format jest ustawiony na MS-DOS (FAT32)
    • Na El Capitan (10.11) przez Katalinę (10.15) wybierz MS-DOS (FAT)
  6. Upewnij się, że Scheme jest ustawiony na Master Boot Record
    • Jeśli Scheme nie pojawia się, kliknij Cancel i upewnij się, że wybrano urządzenie zamiast głośności
  7. Kliknij Erase a potem Close

OS X Josemite (10.10) i wcześniej

  1. Uruchom aplikację na dysku
  2. Wybierz kartę SD z paska bocznego
    • Upewnij się, że wybrałeś właściwe urządzenie, w przeciwnym razie możesz przypadkowo usunąć zły napęd!
  3. Kliknij partition na górze
    • Jeśli partition nie pojawia się, upewnij się, że wybrano urządzenie zamiast głośności
  4. Upewnij się, że Partition jest ustawiona na 1 partition
  5. Upewnij się, że Format jest ustawiony na MS-DOS (FAT)
  6. Z przycisku Opcje (poniżej tablicy partycji), wybierz Master Boot Record.
  7. Kliknij OK -> Apply -> Partition

Sekcja III – Używanie F3

  1. Otwórz terminal
  2. Zainstaluj F3 z brew poprzez uruchomienie brew install f3
  3. Z kartą SD włożoną i zamontowaną, uruchom f3write <your sd card mount point>
    • Poczekaj do zakończenia procesu. Poniżej przedstawiono przykładowe wyniki:
    $ f3write /Volumes/SD\ CARD
-Free space: 29.71 GB
-Creating file 1.h2w ... OK!
-...
-Creating file 30.h2w ... OK!
-Free space: 0.00 Byte
-Average Writing speed: 4.90 MB/s
-
  4. Uruchom f3read <your sd card mount point>
    • Poczekaj do zakończenia procesu. Poniżej przedstawiono przykładowe wyniki:
    $ f3read /Volumes/SD\ CARD
-                  SECTORS      ok/corrupted/changed/overwritten
-Validating file 1.h2w ... 2097152/        0/      0/      0
-...
-Validating file 30.h2w ... 1491904/        0/      0/      0
-
-   Data OK: 29.71 GB (62309312 sectors)
-Data LOST: 0.00 Byte (0 sectors)
-            Corrupted: 0.00 Byte (0 sectors)
-   Slightly changed: 0.00 Byte (0 sectors)
-         Overwritten: 0.00 Byte (0 sectors)
-Average Reading speed: 9.42 MB/s
-

TIP

If the test shows the result Data LOST: 0.00 Byte (0 sectors) your SD card is healthy and you can delete all .h2w files on your SD card.

DANGER

Jeśli test pokazuje inne wyniki, karta SD może być uszkodzona, i być może będziesz musiał ją wymienić!

TIP

You can now restore the contents of your SD card and continue.

- - - diff --git a/pl_PL/site-navigation.html b/pl_PL/site-navigation.html deleted file mode 100644 index d4d7d8dcc..000000000 --- a/pl_PL/site-navigation.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Nawigacja stroną | Przewodnik DSi - - - - -
Przewodnik DSi

Nawigacja stroną

Join the DS⁽ⁱ⁾ Mode Hacking! Discord server for guide development and help.

-

- - - diff --git a/pl_PL/troubleshooting.html b/pl_PL/troubleshooting.html deleted file mode 100644 index 908c27ada..000000000 --- a/pl_PL/troubleshooting.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Rozwiązywanie problemów | Przewodnik DSi - - - - -
Przewodnik DSi

Rozwiązywanie problemów

Join the DS⁽ⁱ⁾ Mode Hacking! Discord server for guide development and help.

-

Unlaunch

Czy Unlaunch zamraża się na MISMATCH IN FAT COPIES

twlnf ma krytyczny błąd, w którym nie aktualizuje poprawnie całego NAND po jego modyfikacji, który powoduje, że niektóre homebrew (takie jak Unlaunch installer) wyrzucą błąd.

To fix this, open NAND Title Manager (NTM)open in new window, and select Fix FAT copy mismatch.

Nie ma dźwięku lub boot splashu podczas uruchamiania "LAUNCHER" za pomocą Unlaunch

The developer of Unlaunch (nocash) has intentionally patched out the background audio and boot-splash by default. You can regain these effects by reinstalling Unlaunch using TWiLight Menu++ with "Launcher Patches" set to "Default" on the Unlaunch page of TWiLight Menu++ settings, or by using hiyaCFWopen in new window.

Powering on only shows a black screen after installing Unlaunch

Try ejecting the SD card and powering the console on again. If it still only shows a black screen, you may need to flash your NAND via a hardmodopen in new window.

After installing Unlaunch, I'm stuck booting into an application

This was likely caused by choosing the wrong app for the NO BUTTON option in Unlaunch. Hold A + B while starting the console, go to OPTIONS, and set NO BUTTON to whatever your preference is.

Other Unlaunch problems

If Unlaunch displays Clusters too large, Bad VBR, Bad MBR, or doesn't display any applications while the SD card is inserted, your SD card likely wasn't formatted correctly. Re-follow SD Card Setup.

TWiLight Menu++ troubleshooting

For general TWiLight Menu++ troubleshooting, see its FAQ & Troubleshootingopen in new window page on the DS-Homebrew Wiki.

Further assistance

If you have encountered an issue that is not solved here, or one that persists despite the given solutions, ask for assistance in the DS(i) Mode Hacking!open in new window Discord server.

- - - diff --git a/pl_PL/uninstalling-unlaunch.html b/pl_PL/uninstalling-unlaunch.html deleted file mode 100644 index f3d6215d7..000000000 --- a/pl_PL/uninstalling-unlaunch.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Odinstalowywanie | Przewodnik DSi - - - - -
Przewodnik DSi

Odinstalowywanie

Join the DS⁽ⁱ⁾ Mode Hacking! Discord server for guide development and help.

-

DANGER

Instalacja lub odinstalowanie Unlaunch może losowo zablokować konsolę! Zostałeś ostrzeżony!

OSTRZEŻENIE: Odinstalowanie może zablokować Twój Nintendo DSi. Oto kilka przypadków powodów, dla których możesz chcieć odinstalować Unlaunch, ale z rozwiązaniami które nie wymagają odinstalowania.

  • The Unlaunch Background is scary: Reinstall Unlaunch using the new instructions. Obecnie zawierają instrukcje dotyczące zmiany tła
  • I'm having an issue with Unlaunch or my console after installing it: The Troubleshooting page will explain how to fix many issues you may have

WARNING

Zmniejszenie szans na zablokowanie, upewnij się, że nie zainstalowałeś żadnych nielegalnych DSiWare do twojego systemu NAND (przekierowanie SDNAND dostarczone przez hiyaCFW nie liczy się), lub w inny sposób manipulowałeś plikami systemowymi.

WARNING

When uninstalling Unlaunch, you should NOT use its built-in uninstaller directly on your console as there is a chance that it will brick the console. Please see below for information on uninstalling it properly.

Once you have reviewed the above information, follow the Dumping NAND instructions to make a new NAND bacup, then proceed to Restoring a NAND Backup. This will guide you through uninstalling Unlaunch from the NAND backup and flashing that to your console.

If you are not able to use no$gba or get an error after uninstalling Unlaunch in no$gba it is also possible to flash a NAND backup made prior to installing Unlaunch if you still have one, however it is recommended to try using a NAND backup that previously had Unlaunch first. This will make recovery significantly easier in the case of a brick requiring a hardmod as Unlaunch leaves the no$gba footer embedded in the NAND even when uninstalled.

- - - diff --git a/restoring-nand.html b/restoring-nand.html index 92aedbf4e..68346638a 100644 --- a/restoring-nand.html +++ b/restoring-nand.html @@ -3,7 +3,7 @@ - + - - Pagina nu a fost găsită | Ghidul DSi - - - - -
- - - diff --git a/ro_RO/alternate-exploits.html b/ro_RO/alternate-exploits.html deleted file mode 100644 index 1db683908..000000000 --- a/ro_RO/alternate-exploits.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Exploit-uri Alternative | Ghidul DSi - - - - -
Ghidul DSi

Exploit-uri Alternative

Alătură-te serverului de Discord DS⁽ⁱ⁾ Mode Hacking! pentru dezvoltarea ghidului și ajutor.

-

Dacă ești introdus într-un tutorial când lansezi aplicația Nintendo DSi Camera și se blochează când încerci să îl completezi, nu poți folosi Memory Pit. Aici, poți găsi exploit-uri alternative care pot funcționa în locul lui Memory Pit.

If you have Flipnote Studio installed, you can use Flipnote Lenny.

TIP

Ensure you have set up TWiLight Menu++ on your SD card before proceeding with any of the following.

If you're on an older firmware, you may have access to save game exploits for a select list of gamesdeschide într-o fereastră nouă. These will not be covered here as they are largely obsolete. They should only be used as a last resort, if both Memory Pit and Flipnote Lenny aren't working for you.

petit-compwner will not be usable for the purpose of working around Memory Pit, as it requires a working camera to launch the exploit.

- - - diff --git a/ro_RO/credits.html b/ro_RO/credits.html deleted file mode 100644 index 8cb6ff882..000000000 --- a/ro_RO/credits.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Mulțumiri | Ghidul DSi - - - - -
Ghidul DSi

Mulțumiri

Alătură-te serverului de Discord DS⁽ⁱ⁾ Mode Hacking! pentru dezvoltarea ghidului și ajutor.

-

Acestea sunt mulțumirile pentru cei care ne-au ajutat cu site-ul ghid, homebrew, și alte lucruri.

Dacă îți place ce au făcut, ia în considerare să donezi (dacă ei au un link de donație).

Poți contribui la ghidul nostru doar prin a trimite un pull requestdeschide într-o fereastră nouă!

Dacă știi alte limbi, poți să ne ajuți prin a traduce ghidul în alte limbi. Poți să te alături Proiectului nostru Crowdindeschide într-o fereastră nouă pentru a începe.

- - - diff --git a/ro_RO/dsiware-backups.html b/ro_RO/dsiware-backups.html deleted file mode 100644 index 0022de601..000000000 --- a/ro_RO/dsiware-backups.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Copii DSiWare | Ghidul DSi - - - - -
Ghidul DSi

Copii DSiWare

Alătură-te serverului de Discord DS⁽ⁱ⁾ Mode Hacking! pentru dezvoltarea ghidului și ajutor.

-

Cerințe

Nintendo DSi - Instrucțiuni

Secțiunea I - Creere copii DSiWare

  1. Lansează GodMode9i
  2. Apasă START pentru a deschide Meniul START
  3. Selectați Title manager...
    • Dacă nu apare, asigură-te că ai un NAND și un card SD montate. Dacă se încarcă din hiyaCFW reîncarcă din altă parte
  4. Selectează titlul căruia vrei să-i creezi o copie
  5. Selectează ce vrei să copiezi
  6. Repetă pașii 4-5 pentru toate jocurile DSiWare pe care vrei să le copiezi

TIP

Jocul DSiWare copiat se va afla în sd:/gm9i/out.

- - - diff --git a/ro_RO/dumping-game-cards.html b/ro_RO/dumping-game-cards.html deleted file mode 100644 index 3cc3140e1..000000000 --- a/ro_RO/dumping-game-cards.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Creere Copii ale Cardurilor de Joc | Ghidul DSi - - - - -
Ghidul DSi

Creere Copii ale Cardurilor de Joc

Alătură-te serverului de Discord DS⁽ⁱ⁾ Mode Hacking! pentru dezvoltarea ghidului și ajutor.

-

Această secțiune este pentru creerea de copii de Carduri de Joc folosind GodMode9i pentru a fi jucate pe emulatoare, flashcard-uri, sau de pe cardul SD prin nds-bootstrap.

Cerințe

  • Cardul de Joc al titlului căruia vrei să-i creezi o copie
  • Your Nintendo DSi console with Unlaunch installed

Instrucțiuni

Secțiunea I - Setarea cardului SD

  1. Descarcă ultima versiune a GodMode9ideschide într-o fereastră nouă
  2. Extrage GodMode9i.nds din arhiva GodMode9i și plasează-l oriunde pe cardul tău SD

Secțiunea II - Instrucțiuni Nintendo DSi

  1. Lansează GodMode9i
  2. Asigură-te că ai introdus cardul de joc în consolă
  3. Selectează opțiunea "NDS GAMECARS" în GodMode9i
  4. Selectează ce vrei să copiezi
    • Opțiunile "Trimmed" pentru ROM vor crea un fișier mai mic ce va fi salvat pe cardul SD, dar nu vor funcționa cu majoritatea patch-urilor precum ROM hack-uri
  5. Repetă pași 2-4 pentru toate cardurile de joc pe care vrei să le copiezi

TIP

The dumped Game Cards will be found in sd:/gm9i/out.

- - - diff --git a/ro_RO/dumping-nand.html b/ro_RO/dumping-nand.html deleted file mode 100644 index 267346c7e..000000000 --- a/ro_RO/dumping-nand.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Copiere NAND | Ghidul DSi - - - - -
Ghidul DSi

Copiere NAND

Alătură-te serverului de Discord DS⁽ⁱ⁾ Mode Hacking! pentru dezvoltarea ghidului și ajutor.

-

Această pagină este pentru creerea unei copii NAND, ce este o copie a datelor de pe stocarea interna a Nintendo DSi. Ea poate fi folosit pentru a seta hiyaCFW, precum și no$gba și melonDS pentru emularea DSi.

TIP

Make sure the SD card has at least 250MB of free space, or else you'll run into an error message in dumpTool.

TIP

It is highly recommended that you do this. A NAND backup can be used as a restore point in the future, in case of a brick.

Secțiunea I - Setarea cardului SD

TIP

If you have already downloaded dumpTool from another section of this guide, you can skip this section.

  1. Descarcă ultima versiune a dumpTooldeschide într-o fereastră nouă
  2. Plasează dumptool.nds oriunde pe cardul tău SD

Secțiunea II - Creerea unei copii NAND

  1. Lansează dumpTool prin TWiLight Menu++
  2. Apasă butonul A pe Nintendo DSi pentru a începe creerea unei copii NAND
    • O copiere NAND durează de obicei 7 minute
  3. Când copierea NAND este completă, apasă butonul START pe Nintendo DSi pentru a ieși din dumpTool
  4. Oprește-ți consola și inserează cardul SD înapoi în dispozitiv
  5. Păstrează această copie undeva în siguranță, unde nu-l poți pierde
    • Dacă este posibil, creează mai multe copii pe mai multe dispozitive
    • Odată ce ai salvat-o în alt loc, poți să o ștergi de pe cardul SD

WARNING

The SHA1 hash of the nand.bin will not match the hash stored in nand.bin.sha1. This is because dumpTool adds additional data known as a no$gba footer to the nand.bin file after the SHA1 hash is calculated. You can use the hiyaCFW Helperdeschide într-o fereastră nouă to create a copy without the footer.

TIP

Continue to Installing Unlaunch (Optional)

- - - diff --git a/ro_RO/faq.html b/ro_RO/faq.html deleted file mode 100644 index b1640ef06..000000000 --- a/ro_RO/faq.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - FAQ | Ghidul DSi - - - - -
Ghidul DSi

FAQ

Alătură-te serverului de Discord DS⁽ⁱ⁾ Mode Hacking! pentru dezvoltarea ghidului și ajutor.

-

Should I do a system update?

It is not recommended to update your DSi unless you know there are purchased DSiWare. While it still possible to follow this guide if you do so, the only benefit to updating is the ability to access the Nintendo DSi Shop to redownload already purchased titles. All other benefits, such as Facebook integration in the Nintendo DSi Camera application, are no longer usable or are not significant enough to justify the downsides:

  • Installing System Updates is known to occasionally brick consoles, with roughly the same frequency as when installing Unlaunch
  • Older exploits are no longer possible to use, which may be required if you are unable use the recommended exploits
  • Flashcard compatibility is reduced, however this is bypassed if you install Unlaunch

Which is the best exploit?

Unlaunch is overall the best exploit for the DSi, with the only downside being that there is a minor brick risk on install. In general it's recommended to use Memory Pit to install Unlaunch. If you want to avoid any risk it's recommended to instead use Flipnote Lenny as it has fewer issues in homebrew than Memory Pit while being just as safe and simple to remove. Below is a list of the pros and cons of each exploit:

Memory Pit

Pros:

  • Quick and easy to use
  • No risk of damaging the console, uninstalling is as simple as removing the SD or deleting one file
  • Compatible with all DSi consoles unless they have a broken camera and haven't completed the camera tutorial

Cons:

  • Requires loading the DSi Camera application every time you want to access homebrew
  • Incompatible with certain DSi mode titles and homebrew due to WRAM only being open to the ARM7 CPU
  • Access to Slot-1 (the DS Game Card) is blocked in homebrew
  • Access to the DSP is blocked resulting in worse sound in GBARunner2
  • Photos on the SD card cannot be viewed in the DSi Camera application while Memory Pit is installed, as this is the trigger for the exploit
    • The only way to view SD card photos while Memory Pit is installed, is to launch a ROM dump of the DSi Camera application using TWiLight Menu++ to boot it via nds-bootstrap (v0.61.3 or later)

stylehax

Pros:

  • Better compatibility with DSi mode titles and homebrew than Memory Pit
  • Easy to use
  • No risk of damaging the console
  • Useable on consoles with broken camera
  • Better sound in GBARunner2

Cons:

  • Requires internet access
  • Requires loading the DSi Browser every time you want to access homebrew, slightly more time consuming than Memory Pit
  • Access to Slot-1 (the DS Game Card) is blocked in homebrew

Flipnote Lenny

Pros:

  • Better compatibility with DSi mode titles and homebrew than Memory Pit
  • No risk of damaging the console, uninstalling is as simple as removing the SD or deleting one folder
  • Useable on consoles with broken camera
  • Better sound in GBARunner2

Cons:

  • Requires loading Flipnote Studio every time you want to access homebrew, slightly more time consuming than Memory Pit
  • Access to Slot-1 (the DS Game Card) is blocked in homebrew

Unlaunch

Pros:

  • Allows loading homebrew and DSiWare immediately on system boot, with optional button hotkeys
  • Full access to the system without any restrictions, including:
    • Access to Slot-1 allowing dumping Game Cards and loading incompatible flashcards
    • Better sound in GBARunner2
  • Removes region locks on DSi-Enhanced/Exclusive Game Cards
  • Protection against most ways a DSi could brick
  • DSi-Enhanced games can be run in DSi mode without a Donor ROM
  • Old homebrew can be run via nds-bootstrap-hb

Cons:

  • Very minor risk of bricking the console when installing
  • Another, slightly higher, risk of bricking if you decide to uninstall it
  • Not compatible with development consoles

Will I lose any functionality by modding my system?

If you install Unlaunch or use Flipnote Lenny, no functionality will be lost. If you use Memory Pit, you will be unable to view photos on the SD card using the DSi Camera, unless you launch a ROM dump of the DSi Camera application using TWiLight Menu++ to boot it via nds-bootstrap.

  • To regain the ability to view your SD card photos when launching the DSi Camera from the DSi Menu, install Unlaunch or switch to a different exploit, then delete Memory Pit's pit.bin file
    • If tip.bin exists in the same folder, rename it back to pit.bin

How do I play Nintendo DS Game Card dumps?

Playing Game Card dumps on the console requires the use of a flashcard or nds-bootstrap, a program which enables games to be played from the internal SD card by redirecting Slot-1 reads and writes to it.

  • With TWiLight Menu++ you can navigate your SD card to find ROM files to play with nds-bootstrap. The advantages to using TWiLight Menu++ are having a cheat menu, per-game settings, and avoiding the restrictions that forwarders bring. In other words, you can drop your ROM files directly and play without any setup. There is no 39 title limit, neither hiyaCFW or Unlaunch are required and there are no restrictions on SD card free space you can have
  • hiyaCFW users can create forwarders for the SDNAND's DSi Menu using the DS Game Forwardersdeschide într-o fereastră nouă guide on the DS-Homebrew Wiki, but it has some limitations. There is a hard limit of 39 titles, and they are less convenient to make than using TWiLight Menu++

How do I update my homebrew?

  • Unlaunch - Follow the instructions on the Installing Unlaunch page
    • You do not need to uninstall Unlaunch before doing this
  • hiyaCFW - Replace hiya.dsi on the root of the SD card from the updated releasedeschide într-o fereastră nouă
  • TWiLight Menu++ - Follow the instructions on the DS-Homebrew Wikideschide într-o fereastră nouă
  • nds-bootstrap - Copy nds-bootstrap-hb-release.nds & nds-bootstrap-release.nds to the _nds folder on the root of your SD card
    • If you use TWiLight Menu++, there is a high chance that the latest nds-bootstrap release is included with TWiLight Menu++
  • GodMode9i, dumpTool, Forwarder3-DS, etc - Follow the instructions used to download them

Other homebrew might use other methods to update.

I am new or I would like to redo my setup. Where do I start?

  • If you have not already modified your console or are looking to update Unlaunch on your system, we recommend starting from the beginning of the guide and following through the pages. Be sure to read everything on the homepage
  • If you have the latest version Unlaunch, follow the TWiLight Menu++ install guidedeschide într-o fereastră nouă to set up TWiLight Menu++ on your system

How can I remove parental controls?

Can I change my Nintendo DSi's region?

Yes, there are a few different methods depending on what you want to change:

What happened to the hiyaCFW installation guide?

Because hiyaCFW does not serve much functional purpose and was a problematic and confusing part of the guide for many users, it was moved to the DS-Homebrew Wikideschide într-o fereastră nouă.

  • If you were linked to the page in question from another guide, the instructions you were following were most likely outdated. Please use this guide instead, as it is maintained constantly by the developers of these projects

What kind of SD card should I use?

  • You should buy an SD card from a trusted brand
  • A full-size SD card or a microSD card with an adapter will both work
  • Any capacity between 1 GB and 2 TB will work. For general usage, 8 GB is enough
    • Some software, such as hiyaCFW, may experience incrementally longer loading times with larger SD card capacities
  • Speed class 8 or higher is recommended

Can I use my DSi SD card on other systems?

Generally, yes, with two exceptions:

  • hiyaCFW will only work on the system it was set up for
  • Even if you are using nds-bootstrap or a flashcard, friend codes in online NDS games will be reset when attempting to go online using a different console

How do I switch to a new SD card after setting up homebrew?

Format your new SD card using the SD Card Setup instructions, then simply move your data from the old SD card to the new one.

Can I still use my system normally without the SD card inserted after setting up homebrew?

Yes. If you did not install Unlaunch, your system will remain completely unmodified. If you did install Unlaunch, you may need to configure Unlaunch to automatically boot the original DSi Menu under specified conditions.

The Unlaunch pagedeschide într-o fereastră nouă says that version 2.0 is not known to be safe. Should I use a previous version instead?

The Unlaunch page has not been updated since version 2.0 was released, which was over two years ago. The vast majority of users experience no issues with this version, so it is considered safe.

How do I run dumped DSiWare?

The recommended method is to simply launch them with TWiLight Menu++, due to the simple drag-and-drop method and there being no arbitrary limit. When nds-bootstrap is set as the launch method, it also gains the benefits of cheats and screenshots, as well as any other benefit provided by the in-game menu.

However, for the few titles that are incompatible, you can use NTMdeschide într-o fereastră nouă to install them on either internal memory or hiyaCFW's SDNANDdeschide într-o fereastră nouă. In addition to lacking the benefits above, there is also a limit of 39 titles that cannot exceed 128 MiB/1,024 blocks in size. For SysNAND, there is also a very small risk of bricking the system when writing to the internal NAND.

- - - diff --git a/ro_RO/file-extensions-windows.html b/ro_RO/file-extensions-windows.html deleted file mode 100644 index c02a92faf..000000000 --- a/ro_RO/file-extensions-windows.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Extensii de Fișiere (Windows) | Ghidul DSi - - - - -
Ghidul DSi

Extensii de Fișiere (Windows)

Alătură-te serverului de Discord DS⁽ⁱ⁾ Mode Hacking! pentru dezvoltarea ghidului și ajutor.

-

Aceasta este o secție suplimentară pentru a schimba ascunderea implicită extensiilor pe Windows, ce va face găsirea fișierelor menționate în ghid mult mai simplă pentru tine.

  1. Lansează File Explorer prin deschiderea oricărui dosar, precum dosarul cardului SD
  2. Click the "View" option on the top bar
    • If the option is not present, click the ··· button on the rightmost part of the top bar
  3. Click or hove your cursor on the Show > submenu
  4. Check the option labeled File name extensions Screenshot of hovering the "File name extensions" checkbox on Windows 11
  1. Lansează File Explorer prin deschiderea oricărui dosar, precum dosarul cardului SD
  2. Click the "View" option on the ribbon menu
  3. Check the box labeled "File name extensions" Screenshot of hovering the "File name extensions" checkbox on Windows 10
  1. Open the start menu by clicking on it or using the Windows key
  2. Search for "Folder Options" and select the corresponding result Screenshot of a search for "folder options" in the Windows 7 Start Menu
  3. Click the "View" option at the top of the Folder Options menu
  4. Make sure the box labeled "Hide extensions for known file types" is unchecked Screenshot of the "Folder Options" window on Windows 7 with "Hide extensions for known types" turned off
- - - diff --git a/ro_RO/get-started.html b/ro_RO/get-started.html deleted file mode 100644 index 27f3cb9b6..000000000 --- a/ro_RO/get-started.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Get Started | Ghidul DSi - - - - -
Ghidul DSi

Get Started

Alătură-te serverului de Discord DS⁽ⁱ⁾ Mode Hacking! pentru dezvoltarea ghidului și ajutor.

-

The main homebrew application this guide has you install is TWiLight Menu++, which is an upgrade/replacement to the Nintendo DSi Menu that allows running other homebrew applications, retail DS games, emulators for various older systems, and more.

We'll begin with downloading it as well as some other homebrew tool(s), in preparation for the exploit steps.

Cerințe

Section I - Prep Work

WARNING

Ensure your SD card is formatted correctly.

  1. Insert your SD card into your PC
  2. Download the latest release of TWiLight Menu++deschide într-o fereastră nouă
  3. Descarcă ultima versiune a dumpTooldeschide într-o fereastră nouă
  4. Copy the _nds folder from TWiLightMenu-DSi.7z to the root of your SD card
  5. Copy the BOOT.NDS file from TWiLightMenu-DSi.7z to the root of your SD card
  6. Copy the dumpTool.nds file to the root of your SD card

TIP

Unsure what the SD "root" is? See this imagedeschide într-o fereastră nouă

Section II - Selecting an exploit

From here you have three options, with a minor difference in what each entails.

Installing Unlaunch via Memory Pit

Memory Pit is an exploit utilizing the DSi Camera, compatible with all firmware versions. Optionally, this exploit can be used to install Unlaunch, a bootcode exploit that allows full control of the console on boot.

As Memory Pit is somewhat limited in homebrew compatibility, it is recommended to install Unlaunch, instead of using Memory Pit standalone. As this is the easiest method to install Unlaunch, this is the recommended path. However, there is a very minor risk of bricking your console when installing Unlaunch, so if this is a concern, see the alternate method below.

TIP

Continue to Launching the Exploit

stylehax

stylehax is an exploit utilizing the DSi Browser application, and can be used as an alternative to Memory Pit for installing Unlaunch (explained above) if your DSi has a broken camera.

For an Unlaunch-free experience, this exploit is recommended as using Memory Pit causes issues in some games and homebrew.

TIP

Continue to Launching the Exploit (stylehax)

Flipnote Lenny

Flipnote Lenny is an exploit utilizing the Flipnote Studio application.

If you have Flipnote Studio and do not plan on installing Unlaunch (explained above), this exploit is recommended for the same reason as stylehax.

You can always install Unlaunch later if you decide later on that you want it.

TIP

Continue to Launching the Exploit (Flipnote Lenny)

For a more detailed pros and cons comparision of the available exploits, please see the Which is the best exploit? FAQ.

- - - diff --git a/ro_RO/index.html b/ro_RO/index.html deleted file mode 100644 index 7b04b5d60..000000000 --- a/ro_RO/index.html +++ /dev/null @@ -1,43 +0,0 @@ - - - - - - - - - Acasă | Ghidul DSi - - - - -
Ghidul DSi

Ghidul DSi

Ghidul complet pentru a-ți modifica sistemul Nintendo DSi

TIP

Pentru ghiduri complete spre homebrew și custom firmware pentru alte dispozitive, uită-te la CFW.Guidedeschide într-o fereastră nouă.

TIP

Citește cu atenție toate paginile introductive (inclusiv pe aceasta!) înainte de a continua.

Ce este homebrew?

Aplicațiile Homebrewdeschide într-o fereastră nouă sunt programe nelicențiate făcute pentru sisteme închise precum Nintendo DSi. Aceste aplicații pot varia de la utilități la jocuri personalizate homebrew.

Homebrew poate rula gratuit pe toate consolele Nintendo DSi, indiferent de versiunea firmware sau regiune. Tot ce-ți trebuie este un punct de intrare și un card SD pentru a-ți stoca aplicațiile homebrew. Punctul de intrare principal folosit în acest ghid se numește Memory Pit, dar există și alte puncte de intrare pe care le poți folosi dacă Memory Pit este inutilizabil.

What can I do by modding my system?

  • Run Nintendo DS(i) game backups or ROM hacks from your DSi SD card without the need of a flashcard
  • Launch any DSiWare from your SD card
    • This means out-of-region and 3DS-exclusive DSiWare will also work
  • Boot into DSiWare and homebrew applications by holding specific buttons when turning on your Nintendo DSi
  • Run old-time classics using various emulators
  • Use normally incompatible flashcards
  • Redirect your NAND to the SD card using hiyaCFW
  • Watch your favorite movies using either FastVideoDSPlayer or tuna-viDS
    • FastVideoDSEncoder requires a CPU supporting AVX2 (newer CPUs will likely support it)
  • Display an image (referred to as the boot splash) on system launch
  • Play homebrew games

Where can I find homebrew applications?

What should I know before starting?

  • On Windows, it's recommended to show file extensions if you are using the default File Explorer
  • The only brick risk comes from installing Unlaunch, and the brick risk is minimal

TIP

Continue to Get Started

- - - diff --git a/ro_RO/installing-unlaunch.html b/ro_RO/installing-unlaunch.html deleted file mode 100644 index 8a618a183..000000000 --- a/ro_RO/installing-unlaunch.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Instalarea Unlaunch | Ghidul DSi - - - - -
Ghidul DSi

Instalarea Unlaunch

Alătură-te serverului de Discord DS⁽ⁱ⁾ Mode Hacking! pentru dezvoltarea ghidului și ajutor.

-

DANGER

If you have not yet done so, please follow Dumping NAND. While the chances are slim, Unlaunch can accidentally brick your Nintendo DSi. A NAND backup + hardmoddeschide într-o fereastră nouă would allow you to restore this backup, provided you know how to solder.

WARNING

Make sure your console is charged when following this process. A sudden power loss could result in serious damage.

WARNING

Unlaunch is not compatible with Nintendo DSi development consoles.

Secțiunea I - Setarea cardului SD

  1. Descarcă ultima versiune a Unlaunchdeschide într-o fereastră nouă
  2. Extrage UNLAUNCH.DSI din arhiva unlaunch.zip și plaseaz-o oriunde pe cardul SD
  3. Verifică dacă încă mai ai TWiLight Menu++ pe cardul SD

Secțiunea II - Instalarea/Actualizarea Unlaunch

  1. Deschide TWiLight Menu++
    • If this is your first time installing Unlaunch, relaunch TWiLight Menu++ through the exploit that you used
    • If you have already installed Unlaunch and are looking to update it, hold A + B while booting and select the option labeled TWiLight Menu++
    • If several options are labeled TWiLight Menu++, select the option in where BOOT.NDS is shown at the end of the path on the bottom screen
  2. Lansarea Setărilor TWiLight Menu++
    • If you haven't changed your theme, press SELECT and touch the small DS icon on the bottom of the touch screen. Altfel, consultă Manualul TWiLight Menu++
  3. Apasă L / R sau X / Y până ajungi la pagina Setări Unlaunch
  4. Dacă vrei să schimbi imaginea de fundal a Unlaunch, selectează Fundalși alege pe cea pe care o vrei
  5. Exit TWiLight Menu++ Settings
  6. In the file navigation menu, launch Unlaunch DSi Installer
    • If you see two black screens after launching, download GodMode9ideschide într-o fereastră nouă, put its .dsi file on the SD root, then launch GodMode9i using TWiLight Menu++, and start Unlaunch.dsi
      This method does not enable Unlaunch to use custom patches and background
  7. Select the "install now" option
    • If Unlaunch freezes at ERROR: MISMATCH IN FAT COPIES, please take a look at the Troubleshooting page
  8. When completed, reboot your system

If you see Unlaunch's Filemenu screen at this point, you have successfully modded your Nintendo DSi.

Secțiunea III - Configurarea după Instalarea Unlaunch

Currently, Unlaunch defaults to launching its Filemenu on boot, but this can be changed launch whatever you want.

  1. Pornește-ți consola în timp ce ții apăsat pe A și B
    • Aceasta ar trebui să lanseze Meniul de Fișiere Unlaunch
    • If only the background is shown, or if no files from the SD card are shown (ex. TWiLight Menu++), then you'll need to reformat the SD card
  2. Navighează la OPȚIUNI, și uită-te la opțiunile disponibile
    • A + B este hard-codat pentru a lansa în meniul Unlaunch, deci nu poate fi schimbat
    • Opțiunile NO BUTTON și BUTTON A / B / X / Y pot fi setate cum îți dorești și vor alege ce va lansa pe DSi la pornire în funcție debutoanele care sunt apăsate. Poți selecta orice DSiWare, homebrew, cardul Slot-1, wifiboot, sau Meniul de Fișiere al Unlaunch
      • For TWiLight Menu++, select TWiLight Menu++
      • Pentru Meniul DSi original, selectează Launcher
    • LOAD ERROR este ceea ce DSi va afișa dacă încarci ceve ce ai setat eșuează, precum faptul că nu ai introdus cardul SD
  3. Selectează SAVE & EXIT pentru a-ți salva setările, apoi oprește consola DSi

Secțiunea IV - Curățarea cardului SD

TIP

This section is optional and only serves for keeping your SD card tidy of files you won't need.

  • Delete the sd:/private/ds/app/484E494A/pit.bin file from your SD card
    • If tip.bin still exists, then rename it back to pit.bin
  • You can now restore the DCIM folder that was on the root of your SD card, if this folder existed
  • Șterge fișierul UNLAUNCH.DSI de pe cardul SD
  • Delete the 800031_104784BAB6B57_000.ppm and T00031_1038C2A757B77_000.ppm files from inside the following folders:
    • sd:/private/ds/app/4B47554A/001 (Japan)
    • sd:/private/ds/app/4B475545/001 (USA)
    • sd:/private/ds/app/4B475556/001 (Europe/Australia)
    • You can also delete the entire folders for the regions besides your own
  • Șterge fișierul UNLAUNCH.DSI de pe cardul SD
- - - diff --git a/ro_RO/launching-the-browser-exploit.html b/ro_RO/launching-the-browser-exploit.html deleted file mode 100644 index c84e64a27..000000000 --- a/ro_RO/launching-the-browser-exploit.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Launching the Exploit (stylehax) | Ghidul DSi - - - - -
Ghidul DSi

Launching the Exploit (stylehax)

Alătură-te serverului de Discord DS⁽ⁱ⁾ Mode Hacking! pentru dezvoltarea ghidului și ajutor.

-

We'll start by first launching our exploit. For the best Unlaunch-free experience, or if the DSi camera is broken to install Unlaunch, we recommend using an exploit called "stylehax" which takes advantage of a flaw in how the DSi Browser application handles webpages.

Lansarea exploit-ului va porni TWiLight Menu++, o aplicație homebrew ce se comportă ca un înlocuitor pentru Meniul DSi.

Cerințe

  • Nintendo DSi Browser installed on your Nintendo DSi
    • If you do not have the DSi Browser, then use Memory Pit instead

Launching the exploit

  1. Ensure your SD card is inserted into your Nintendo DSi
  2. Boot your Nintendo DSi and launch the DSi Browser application
  3. Touch the Go to Page button
    • The button will have a green www icon
  4. Type opera:about, and touch Go to load the page
  5. Touch the HOME icon
  6. Touch the Go to Page button
  7. Type stylehax.net, and touch Go to load the page

TIP

The exploit should take 21 seconds to take effect. If it takes longer than 30 seconds, then reboot, and try again.

WARNING

If the top screen turns green, you do not have TWiLight Menu++'s BOOT.NDS on the root of your SD card. Follow the prep work again.

You can now use TWiLight Menu++! First, it will ask you to select your language and region. These do not need to match your console's language or region, so set them to whichever you prefer. Next, it's recommended to continue on and make a NAND backup. This can potentially be used to save your console if anything bad happens in the future.

TIP

Continue to Dumping NAND

- - - diff --git a/ro_RO/launching-the-exploit.html b/ro_RO/launching-the-exploit.html deleted file mode 100644 index 52d8151e9..000000000 --- a/ro_RO/launching-the-exploit.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Lansarea Exploit-ului | Ghidul DSi - - - - -
Ghidul DSi

Lansarea Exploit-ului

Alătură-te serverului de Discord DS⁽ⁱ⁾ Mode Hacking! pentru dezvoltarea ghidului și ajutor.

-

Vom începe prin a-ți seta cardul SD pentru a lansa exploit-ul. Pentru majoritatea utilizatorilor, noi recomandăm să folosești un exploit numit "Memory Pit" care profită de o eroare în modul prin care aplicația Nintendo DSi Camera tratează metadatele de imagini.

Lansarea exploit-ului va porni TWiLight Menu++, o aplicație homebrew ce se comportă ca un înlocuitor pentru Meniul DSi.

TIP

If you don't plan on installing Unlaunch and have either the DSi Browser or Flipnote Studio, it is recommended to use either stylehax or Flipnote Lenny instead. Which is the best exploit?

Section I - Checking your DSi Camera Version

  1. Pornește-ți consola
  2. Open Nintendo DSi Camera
    • If you are prompted to complete the camera tutorial, do so now
    • If the tutorial crashes as you try to complete it, your Nintendo DSi camera hardware is likely broken in some way and you will not be able to use Memory Pit. Please use an alternate exploit
  3. Open the album using the large button on the right
  4. Take note of whether you have a Facebook icon alongside the star, clubs, and heart, outlined in red here: Screenshot of where the Facebook icon is located

Section II - Memory Pit

  1. Download the correct Memory Pit binary for your Nintendo DSi Camera version:
  2. Navigate to the sd:/private/ds/app/484E494A/ folder on your SD card
    • You will already have this directory if you have previously taken photos to your SD card via the Nintendo DSi Camera application. If so, you do not need to delete it and recreate it
    • If it does not exist, please create the individual folders
  3. If there is already a pit.bin file in that path, rename it to tip.bin
  4. Place the Memory Pit pit.bin file in this folder
  5. If there's a folder named DCIM in the root of your SD card, make a back up of it so you don't lose the pictures inside, and then remove it from the SD card

Section III - Launching the exploit

  1. Ensure your SD card is inserted into your Nintendo DSi
  2. Boot your Nintendo DSi and launch the Nintendo DSi Camera application
  3. Select the SD Card icon in the top-right
    • If you receive a message saying your SD card isn't inserted, please use another SD card
    • If you receive a message saying that your SD card cannot be used, ensure your SD card is formatted correctly
  4. Open the album using the large button on the right
    • The screen should flash magenta if Memory Pit was copied correctly

WARNING

If the top screen turns green, you do not have TWiLight Menu++'s BOOT.NDS on the root of your SD card. Follow the prep work again.

WARNING

If you enter the SD card camera album and nothing unusual happens, ensure that you downloaded the correct version of Memory Pit for your version and region, and placed it into the correct folder on your SD card. Also ensure that the DCIM folder does not exist on your SD card.

You can now use TWiLight Menu++! First, it will ask you to select your language and region. These do not need to match your console's language or region so set them to whichever you prefer. Next it's recommended to continue on and make a NAND backup. This can potentially be used to save your console if anything bad happens in the future.

TIP

Continue to Dumping NAND

- - - diff --git a/ro_RO/launching-the-flipnote-exploit.html b/ro_RO/launching-the-flipnote-exploit.html deleted file mode 100644 index 0d0de566f..000000000 --- a/ro_RO/launching-the-flipnote-exploit.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Launching the Exploit (Flipnote Lenny) | Ghidul DSi - - - - -
Ghidul DSi

Launching the Exploit (Flipnote Lenny)

Alătură-te serverului de Discord DS⁽ⁱ⁾ Mode Hacking! pentru dezvoltarea ghidului și ajutor.

-

Vom începe prin a-ți seta cardul SD pentru a lansa exploit-ul. For the best Unlaunch-free experience, we recommend using an exploit called "Flipnote Lenny" which takes advantage of a flaw in how the Flipnote Studio application handles flipnotes.

Lansarea exploit-ului va porni TWiLight Menu++, o aplicație homebrew ce se comportă ca un înlocuitor pentru Meniul DSi.

Cerințe

  • Flipnote Studio installed on your Nintendo DSi
    • If you do not have Flipnote Studio, then use Memory Pit instead

Secțiunea I - Setarea cardului SD

  1. Download the latest version of Flipnote Lennydeschide într-o fereastră nouă
  2. Copy the private folder from the Flipnote Lenny archive to the root of your SD card

Section II - Launching the exploit

  1. Ensure your SD card is inserted into your Nintendo DSi
  2. Boot your Nintendo DSi and launch the Flipnote Studio application
    • If you receive a message saying that your SD card cannot be used, ensure your SD card is formatted correctly
  3. Open the Flipnote Studio settings on the top-right of the main menu and ensure that Start on Calendar is disabled and Frog is enabled
  4. View the flipnotes stored on the SD card
    • If you are unable to view the flipnotes on the SD card, please use another SD card
  5. Tap on the face corresponding to your region
    • If you have an AUS console, select EUR
  6. Edit the selected flipnote
  7. Tap the frog icon on the bottom-left
  8. Tap on the film roll icon
  9. Select Copy -> Back -> Exit
  10. Tap on the second note with a larger face, and select Edit
  11. Tap on the frog icon on the bottom-left
  12. Tap on the film roll icon
  13. Select paste

WARNING

If the top screen turns green, you do not have TWiLight Menu++'s BOOT.NDS on the root of your SD card. Follow the prep work again.

You can now use TWiLight Menu++! First, it will ask you to select your language and region. These do not need to match your console's language or region, so set them to whichever you prefer. Next, it's recommended to continue on and make a NAND backup. This can potentially be used to save your console if anything bad happens in the future.

TIP

Continue to Dumping NAND

- - - diff --git a/ro_RO/lazy-dsi-downloader.html b/ro_RO/lazy-dsi-downloader.html deleted file mode 100644 index c33c1afb8..000000000 --- a/ro_RO/lazy-dsi-downloader.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Lazy DSi Downloader | Ghidul DSi - - - - -
Ghidul DSi

Lazy DSi Downloader

Alătură-te serverului de Discord DS⁽ⁱ⁾ Mode Hacking! pentru dezvoltarea ghidului și ajutor.

-

"Lazy DSi Downloader" este un instrument de simplificare a procesului de modificare al consolei Nintendo DSi.

Etapele de verificare

  1. Pornește-ți consola Nintendo DSi
  2. Lansează aplicația Nintendo DSi Camera

If at this point you get a tutorial and crash when trying to follow it, then you cannot use Memory Pit.

Ghid de configurare

  1. Download the latest release of Lazy DSi File Downloaderdeschide într-o fereastră nouă for your OS
  2. Launch it via the instructions for your operating system listed in the release page
  3. Hit the Next button
    • The intro text isn't mandatory to read
  4. If your Nintendo DSi crashed during the verification steps above, toggle off the Memory Pit option
  5. Hit the check boxes for "Download latest GodMode9i version?"
    • Feel free to select any of the other homebrew applications in Click to add Additional homebrew..., but this is not mandatory
  6. Wait for everything to download, then hit Finish
- - - diff --git a/ro_RO/restoring-nand.html b/ro_RO/restoring-nand.html deleted file mode 100644 index c38e9ec16..000000000 --- a/ro_RO/restoring-nand.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Restaurarea unei copii NAND | Ghidul DSi - - - - -
Ghidul DSi

Restaurarea unei copii NAND

Alătură-te serverului de Discord DS⁽ⁱ⁾ Mode Hacking! pentru dezvoltarea ghidului și ajutor.

-

DANGER

ATENŢIE! Aceasta este periculoasă. Chiar și urmărirea acestor pași cu exactitate are potențialul de a cauza un brick consolei DSi deoarece NAND-ul este de calitate foarte joasă, în special dacă îl instalezi de mai multe ori! Aceasta ar trebui folosită doar în ultimă instanță!

TIP

Nu sări peste nimic de pe această pagină, orice greșeală mărește șansele de brick.

Pentru început, câteva alternative mai sigure la motivul pentru care vrei să faci asta:

  • Instalarea jocurilor DSiWare se poate face folosind hiyaCFW sau TWiLight Menu++
  • Recuperarea pozelor se poate face folosind ninfsdeschide într-o fereastră nouă, în combinație cu hiyaCFW sau TWiLight Menu++ dacă le vrei pe consolă. Ultima versiune a HiyaCFW Helper îți permite să-ți copiezi pozele de pe NAND pe SDNAND în timpul configurării
  • Restaurarea unui buton de configurare Unlaunch poate fi făcută din meniul Unlaunch, ce poate fi accesat dacă ții apăsat pe A + B în timp ce pornești consola
  • Pornirea în Unlaunch cauzează o eroare? Scoate cardul SD și încearcă să repornești sistemul. Dacă funcționează, atunci există o eroare cu cardul tău SD și restaurarea unei copii NAND nu o va repara
  • "An error has occurred..." la lansare este probabil o eroare cu hiyaCFW și nu este legată de NAND, vezi hiyaCFW FAQ & Troubleshootingdeschide într-o fereastră nouă pe DS-Homebrew Wiki pentru mai multe informații
  • Orice eroare în TWiLight Menu++ nu are legătură și ar trebui să încerci să reinstalezi TWiLight Menu++ sau să ceri ajutor pe Discorddeschide într-o fereastră nouă
  • Dezinstalarea Unlaunch, fie prin instalarea NAND-ului sau folosind dezinstalatorul, ar trebui evitate cu orice preț dacă nu este absolut necesar, poți seta tastele de autopornire la "Launcher" și consola ta DSi va fi în siguranță

Singurul lucru pe care trebuie să-l faci cu NNAD-ul tău este să instalezi Unlaunch. Altfel folosește alternative.

Cerințe

Crearea unei copii BIOS pentru a o folosi în no$gba

  1. Extrage dsibiosdumper din arhiva dsibiosdumper.zip și plaseaz=o oriunde pe cardul SD
  2. Pornește-ți consola în timp ce ții apăsat pe A și B
    • Aceasta ar trebui să lanseze Meniul de Fișiere Unlaunch
  3. Lansează dsibiosdumper din Meniul de Fișiere Unlaunch
  4. Apasă Apentru a crea o copie BIOS pe cardul SD
  5. Apasă START pentru a ieși din dsibiosdumper

Testarea copiei tale NAND

Este foarte important să testezi copia NAND pentru a vedea dacă este funcțională înainte de a o restaura pe consolă, iar dacă arată o eroare de brick în no$gba aceasta cel mai sigur va cauza un brick și consolei tale.

  1. Extrage NO$GBA.EXE din no$gba-w.zip într-un dosar ce calculatorul tău
  2. Copiează copia NAD în dosarul în care ai pus NO$GBA.EXE și redenumește-o în DSI-1.MMC
  3. Copiază bios7i.bin și bios9i.bin în dosarul în care ai pus NO$GBA.EXE, numite BIOSDSI7.ROM și BIOSDSI9.ROM, respectiv.
  4. Rulează NO$GBA.EXE
  5. Apasă Options > Emulation Setup pentru a deschide fereastra Emulation Setup
  6. Schimbă Reset/Startup Entrypoint în GBA/NDS BIOS (Nintendo logo)
  7. Schimbă NDS Mode/Colors în DSi (retail/16MB)
  8. Apasă Save Now
  9. Lansează orice ROM Nintendo DS (fișier .nds)

Dacă no$gba lansează meniul DSi (sau Meniul de Fișiere Unlaunch), atunci continuă la secțiunea următoare. Dacă arată orice fel de eroare nu instala acea copie!

Dezinstalarea Unlaunch de pe copia NAND (opțional)

Urmează acești pași dacă ai creat o copie a NAND-ului după ce ai instalat Unlaunch și ai dori să dezinstalezi Unlaunch de pe sistemul tău. Dacă nu vrei să dezinstalezi Unlaunch, nu trebuie să urmezi această secțiune.

  1. Descarcă ultima versiune a instalatorului Unlaunchdeschide într-o fereastră nouă
  2. Extrage UNLAUNCH.DSI din unlaunch.zip
  3. Lansează UNLAUNCH.DSI în no$gba și pornește-l din slotul Cardului de Joc
    • Acesta ar trebui să pornească instalatorul Unlaunch, care arată similar cu Meniul de Fișiere Unlaunch
  4. Alege Uninstall
  5. Odată finalizat, alege Power down
  6. Lansează orice ROM Nintendo DS din nou, și asigură-te că meniul DSi se încarcă și funcționează corect

If no$gba shows any kind of error instead of loading the DSi menu, do not flash that backup! If you have an older NAND backup you may want to try using that instead. Do not try to uninstall Unlaunch using its uninstaller on the console, it is extremely likely doing so will brick your DSi.

Instalarea copiei tale NAND (Software)

DANGER

Make sure you have read through the above steps as this is where it gets dangerous. If you were linked directly to here without following the above, then go back to the top and read this whole page.

DANGER

Make sure your Nintendo DSi system is well charged before beginning this section.

  1. Cu cardul SD introdus, pornește consola Nintendo DSi în timp ce ții apăsat pe A și B
  2. Lansează SafeNANDManager
  3. Apasă butonul begin NAND restore
  4. Odată ce restaurarea s-a încheiat, apasă START pentru a opri consola DSi

Your NAND should now be restored.

Instalarea copiei tale NAND (Hardmod)

If you cannot boot your Nintendo DSi, a hardmod is the only way to restore a NAND backup. The best guide that currently exists is the Nintendo DSi hardmod guide on the DS-Homebrew Wikideschide într-o fereastră nouă.

- - - diff --git a/ro_RO/sd-card-setup.html b/ro_RO/sd-card-setup.html deleted file mode 100644 index 207bdc72b..000000000 --- a/ro_RO/sd-card-setup.html +++ /dev/null @@ -1,85 +0,0 @@ - - - - - - - - - Setarea Cardului SD | Ghidul DSi - - - - -
Ghidul DSi

Setarea Cardului SD

Alătură-te serverului de Discord DS⁽ⁱ⁾ Mode Hacking! pentru dezvoltarea ghidului și ajutor.

-

This page is for preparing your SD card for your device. In the process, we'll format the SD card and check the card for errors.

DANGER

Asigură-te că ai făcut un backup cardului SD ÎNAINTE de a urmări acest ghid. Cardul tău SD va fi ȘTERS în acest proces.

Secțiunea I - Formatarea cardului SD cu SD Formatter

TIP

Această secțiune formatează cardul SD la specificațiile ale Asociației Cardului SD. Aceasta poate rezolva multe probleme ce pot apărea la rularea aplicațiilor homebrew.

DANGER

Orice card SD de peste 64GB va fi formatat la exFAT în acest proces. Trebuie să urmărești Secțiunea II pentru a reformata la FAT32.

  1. Descarcă ultima versiune a SD Formatterdeschide într-o fereastră nouă
  2. Rulează SD Card Formatter Setup (fișierul .exe) în fișierul .zip descărcat cu privilegii de Administator, după aceea instalează programul
  3. Rulează SD Card Formatter din Meniul de Start cu privilegii de Administrator
  4. Selectează-ți cardul SD
  5. Asigură-te că Quick Format este bifat
  6. Press Format to start the format process Screenshot of SD Card Formatter on Windows 11

Secțiunea II - Formatarea cardului SD cu GUIFormat

Această secțiune formatează cardulie SD mai mari de 32GB în FAT32.

TIP

Dacă ai un card SD mai mic de 32GB, sari la Secțiunea III.

  1. Descarcă ultima versiune a GUIFormatdeschide într-o fereastră nouă
    • Apasă pe imaginea de pe site pentru a descărca aplicația
  2. Rulează GUIFormat cu permisiuni de Administrator
  3. Selectează litera drive-ului
  4. Set the Allocation size unit to 32768
    • Dacă este prea mare pentru cardul tău SD, setează-l la cea mai mare valoare care funcționează
  5. Asigură-te că Quick Format este bifat
  6. Începe procesul de formatare

Secțiunea III – Căutarea de erori

  1. Mergi la fereastra de proprietăți a cardului SD
    • Windows Explorer -> Acest PC -> Apasă click dreapta pe cardul SD -> Proprietăți
  2. În fila cu unelte, selectează Verifică Acum
  3. Bifează Repară automat erorile sistemului de fișiere și Scanează pentru și încearcă recuperarea sectoarelor rele
  4. Începe procesul de verificare

Acesta va scana cardul SD și va corecta orice eroare găsită.

Secțiunea IV - Verificarea citirii/scrierii cardului SD

  1. Descarcă și extrage arhiva h2testwdeschide într-o fereastră nouă oriunde pe calculatorul tău
  2. Cu cardul SD introdus în calculatorul tău, rulează h2testw.exe
  3. Selectează în ce limbă ai vrea să vezi h2testw
  4. Setează litera cardului SD ca și țintă
  5. Asigură-te că all available space este selectat
  6. Apasă Write + Verify
  • Așteptă până când procesul este terminat

TIP

Dacă testul afișează rezultatul Test finished without errors,, cardul tău SD este sănătos și poți șterge toate fișierele .h2w de pe cardul SD.

DANGER

Dacă testul afișează orice alt rezultat, cardul tău SD ar putea fi corupt sau deteriorat și s-ar putea să trebuiască să-l înlocuiți!

TIP

If TWiLight Menu++ fails to start after following this method, please follow the Windows method instead, by either rebooting to Windows or running a Windows Virtual Machine

Secțiunea I - Formatarea cardului SD

  1. Asigură-te că nu ai introdus cardul SD în calculatorul tău Linux
  2. Lansează Terminalul Linux
  3. Scrie watch "lsblk"
  4. Introdu cardul SD în calculatorul Linux
  5. Observă rezultatul. Ar trebui să arate în genul acesta:
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
-mmcblk0     179:0    0   3,8G  0 disk
-└─mmcblk0p1 179:1    0   3,7G  0 part /run/media/user/FFFF-FFFF
-
  1. Take note of the device name. In our example above, it was mmcblk0p1
    • Dacă RO este setat la 1, asigură-te că butonul de blocare nu este în jos
    • Make sure you're targetting the partition, mmcblk0p1 not mmcblk0
  2. Apasă CTRL + C pentru a ieși din meniu
  3. Urmează instrucțiunile conform capacității cardului SD:
    • 2GB or lower: sudo mkdosfs /dev/(device name from above) -s 64 -F 16
      • This creates a single FAT16 partition with 32 KB cluster size on the SD card
    • 4GB or higher: sudo mkdosfs /dev/(device name from above) -s 64 -F 32
      • This creates a single FAT32 partition with 32 KB cluster size on the SD card

Secţiunea II – Utilizarea F3

  1. Descarcă și extrage arhiva F3deschide într-o fereastră nouă oriunde pe calculatorul tău.
  2. Lansează terminalul în dosarul F3
  3. Rulează make pentru a compila F3
  4. Cu cardul SD introdus și montat, rulează ./f3write <your sd card mount point>
    • Așteaptă până procesul s-a încheiat. Vezi mai jos un exemplu de rezultat:
    $ ./f3write /media/michel/6135-3363/
-Free space: 29.71 GB
-Creating file 1.h2w ... OK!
-...
-Creating file 30.h2w ... OK!
-Free space: 0.00 Byte
-Average Writing speed: 4.90 MB/s
-
  5. Rulează ./f3read <your sd card mount point>
  • Așteaptă până procesul s-a încheiat. Vezi mai jos un exemplu de rezultat:
    $ ./f3read /media/michel/6135-3363/
-                  SECTORS      ok/corrupted/changed/overwritten
-Validating file 1.h2w ... 2097152/        0/      0/      0
-...
-Validating file 30.h2w ... 1491904/        0/      0/      0
-
-   Data OK: 29.71 GB (62309312 sectors)
-Data LOST: 0.00 Byte (0 sectors)
-            Corrupted: 0.00 Byte (0 sectors)
-   Slightly changed: 0.00 Byte (0 sectors)
-         Overwritten: 0.00 Byte (0 sectors)
-Average Reading speed: 9.42 MB/s
-

TIP

If the test shows the result Data LOST: 0.00 Byte (0 sectors) your SD card is healthy and you can delete all .h2w files on your SD card.

DANGER

Dacă testul afișează orice alt rezultat, cardul tău SD ar putea fi corupt sau deteriorat și s-ar putea să trebuiască să-l înlocuiți!

Secțiunea I - Formatarea cardului SD cu SD Formatter

TIP

Această secțiune formatează cardul SD la specificațiile ale Asociației Cardului SD. Aceasta poate rezolva multe probleme ce pot apărea la rularea aplicațiilor homebrew.

DANGER

Orice card SD de peste 64GB va fi formatat la exFAT în acest proces. Trebuie să urmărești Secțiunea II pentru a reformata la FAT32.

  1. Descarcă ultima versiune a SD Formatterdeschide într-o fereastră nouă
    • Acceptă Accordul de Licență cu Utilizatorul pentru a începe descărcarea
  2. Rulați Instalați cardul SD Formatter (fișierul .mpkg) în fișierul descărcat .zip
  3. Rulează SD Card Formatter
  4. Selectează-ți cardul SD
  5. Asigură-te că Quick Format este bifat
  6. Începe procesul de formatare

Secțiunea II - Formatarea cardului SD cu Disk Utility

Această secțiune formatează cardulie SD mai mari de 32GB în FAT32.

TIP

Dacă ai un card SD mai mic de 32GB, sari la Secțiunea III.

OS X El Capitan (10,11) și ulterior

  1. Lansează aplicația Disk Utility
  2. Selectează Show All Devices în panoul View din stânga sus
  3. Selectează cardul SD din bara laterală
    • Asigură-te că ai ales dispozitivul corect, altfel ai putea șterge din greșeală drive-ul greșit!
  4. Apasă Erase în vârf
  5. Asigură-te că Format este setat la MS-DOS (FAT32)
    • De la El Capitan (10.11) până la Catalina (10.15) alege MS-DOS (FAT)
  6. Asigură-te că Scheme este setat la Master Boot Record
    • Dacă Scheme nu apare, apasă Cancel și asigură-te că ai ales dispozitivul corect în loc de un volum
  7. Apasă Erase, apoi apasă Close

OS X Yosemit (10.10) și anterior

  1. Lansează aplicația Disk Utility
  2. Selectează cardul SD din bara laterală
    • Asigură-te că ai ales dispozitivul corect, altfel ai putea șterge din greșeală drive-ul greșit!
  3. Apasă Partition în vârf
    • Dacă Partition nu apare, asigură-te că ai ales dispozitivul în loc de un volum
  4. Asigură-te că Partition Layout este setat la 1 Partition
  5. Asigură-te că Format este setat laMS-DOS (FAT)
  6. Din butonul de Opțiuni (sub tabelul de partiții), selectează Master Boot Record.
  7. Apasă OK -> Apply -> Partition

Secțiunea III – Utilizarea F3

  1. Deschide Terminalul
  2. Instalează F3 din brew prin rularea a brew install f3
  3. Cu cardul SD introdus și montat, rulează f3write <your sd card mount point>
    • Așteaptă până procesul s-a încheiat. Vezi mai jos un exemplu de rezultat:
    $ f3write /Volumes/SD\ CARD
-Free space: 29.71 GB
-Creating file 1.h2w ... OK!
-...
-Creating file 30.h2w ... OK!
-Free space: 0.00 Byte
-Average Writing speed: 4.90 MB/s
-
  4. Rulează f3read <your sd card mount point>
    • Așteaptă până procesul s-a încheiat. Vezi mai jos un exemplu de rezultat:
    $ f3read /Volumes/SD\ CARD
-                  SECTORS      ok/corrupted/changed/overwritten
-Validating file 1.h2w ... 2097152/        0/      0/      0
-...
-Validating file 30.h2w ... 1491904/        0/      0/      0
-
-   Data OK: 29.71 GB (62309312 sectors)
-Data LOST: 0.00 Byte (0 sectors)
-            Corrupted: 0.00 Byte (0 sectors)
-   Slightly changed: 0.00 Byte (0 sectors)
-         Overwritten: 0.00 Byte (0 sectors)
-Average Reading speed: 9.42 MB/s
-

TIP

If the test shows the result Data LOST: 0.00 Byte (0 sectors) your SD card is healthy and you can delete all .h2w files on your SD card.

DANGER

Dacă testul afișează orice alt rezultat, cardul tău SD ar putea fi corupt sau deteriorat și s-ar putea să trebuiască să-l înlocuiți!

TIP

You can now restore the contents of your SD card and continue.

- - - diff --git a/ro_RO/site-navigation.html b/ro_RO/site-navigation.html deleted file mode 100644 index 3e60dbe05..000000000 --- a/ro_RO/site-navigation.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Navigarea Site-ului | Ghidul DSi - - - - -
Ghidul DSi

Navigarea Site-ului

Alătură-te serverului de Discord DS⁽ⁱ⁾ Mode Hacking! pentru dezvoltarea ghidului și ajutor.

-

- - - diff --git a/ro_RO/troubleshooting.html b/ro_RO/troubleshooting.html deleted file mode 100644 index 59de8dd22..000000000 --- a/ro_RO/troubleshooting.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Troubleshooting | Ghidul DSi - - - - -
Ghidul DSi

Troubleshooting

Alătură-te serverului de Discord DS⁽ⁱ⁾ Mode Hacking! pentru dezvoltarea ghidului și ajutor.

-

Unlaunch

Unlaunch îngheață la MISMATCH IN FAT COPIES

twlnf are o eroare critică în care nu actualizează corect întregul NAND după ce este modificat, ce cauzează anumite aplicații homebrew (precum instalatorul Unlaunch) să afișeze o eroare.

Pentru a remedia asta, deschide NAND Title Manager (NTM)deschide într-o fereastră nouă, și selectează Fix FAT copy mismatch.

Nu se aude nimic sau splash-ul de lansare nu apare când lansez "Launcher" în Unlaunch

The developer of Unlaunch (nocash) has intentionally patched out the background audio and boot-splash by default. You can regain these effects by reinstalling Unlaunch using TWiLight Menu++ with "Launcher Patches" set to "Default" on the Unlaunch page of TWiLight Menu++ settings, or by using hiyaCFWdeschide într-o fereastră nouă.

Când pornesc consola după ce am instalat Unlaunch apare doar un ecran negru

Try ejecting the SD card and powering the console on again. If it still only shows a black screen, you may need to flash your NAND via a hardmoddeschide într-o fereastră nouă.

După ce am insatlat Unlaunch, sunt blocat la pornirea unei aplicații sau în Meniul de Fișiere Unlaunch

This was likely caused by choosing the wrong app for the NO BUTTON option in Unlaunch. Hold A + B while starting the console, go to OPTIONS, and set NO BUTTON to whatever your preference is.

Alte probleme cu Unalunch

If Unlaunch displays Clusters too large, Bad VBR, Bad MBR, or doesn't display any applications while the SD card is inserted, your SD card likely wasn't formatted correctly. Re-follow SD Card Setup.

TWiLight Menu++

For general TWiLight Menu++ troubleshooting, see its FAQ & Troubleshootingdeschide într-o fereastră nouă page on the DS-Homebrew Wiki.

Asistență suplimentară

If you have encountered an issue that is not solved here, or one that persists despite the given solutions, ask for assistance in the DS(i) Mode Hacking!deschide într-o fereastră nouă Discord server.

- - - diff --git a/ro_RO/uninstalling-unlaunch.html b/ro_RO/uninstalling-unlaunch.html deleted file mode 100644 index fe2556f2b..000000000 --- a/ro_RO/uninstalling-unlaunch.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Dezinstalarea Unlaunch | Ghidul DSi - - - - -
Ghidul DSi

Dezinstalarea Unlaunch

Alătură-te serverului de Discord DS⁽ⁱ⁾ Mode Hacking! pentru dezvoltarea ghidului și ajutor.

-

DANGER

Instalarea sau dezinstalarea a Unlaunch poate cauza un brick la întâmplare! Ai fost avertizat!

ATENȚIE: O dezinstalare Unlaunch poate cauza consolei Nintendo DSi un brick. Aici sunt câteva cazuri despre motivul pentru care vrei să dezinstalezi Unlaunch dar cu soluți care nu necesită dezinstalare.

  • The Unlaunch Background is scary: Reinstall Unlaunch using the new instructions. Acestea conțin acum instrucțiuni privind modul de schimbare a fundalului
  • Am o problemă cu Unlaunch sau consola mea după instalare: Pagina de Troubleshooting îți va explica cum să rezolvi multe probleme pe care le ai

WARNING

Pentru a reduce șansele de brick, asigură-te că nu ai instalat DSiWare nelegitim pe copia de NAND (redirecționarea SDNAND de la hiyaCFW nu se pune), sau dacă ai umblat la fișierele de sistem.

WARNING

When uninstalling Unlaunch, you should NOT use its built-in uninstaller directly on your console as there is a chance that it will brick the console. Te rugăm să vezi mai jos pentru informații despre cum să-l dezinstalezi corect.

Once you have reviewed the above information, follow the Dumping NAND instructions to make a new NAND bacup, then proceed to Restoring a NAND Backup. This will guide you through uninstalling Unlaunch from the NAND backup and flashing that to your console.

If you are not able to use no$gba or get an error after uninstalling Unlaunch in no$gba it is also possible to flash a NAND backup made prior to installing Unlaunch if you still have one, however it is recommended to try using a NAND backup that previously had Unlaunch first. This will make recovery significantly easier in the case of a brick requiring a hardmod as Unlaunch leaves the no$gba footer embedded in the NAND even when uninstalled.

- - - diff --git a/sd-card-setup.html b/sd-card-setup.html index 966ae4954..f7a5ab942 100644 --- a/sd-card-setup.html +++ b/sd-card-setup.html @@ -3,7 +3,7 @@ - + - - crwdns2814:0crwdne2814:0 | crwdns5445:0crwdne5445:0 - - - - -
- - - diff --git a/translate/alternate-exploits.html b/translate/alternate-exploits.html deleted file mode 100644 index e13c90b1e..000000000 --- a/translate/alternate-exploits.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - crwdns5521:0crwdne5521:0 | crwdns5445:0crwdne5445:0 - - - - -
crwdns5445:0crwdne5445:0

crwdns5521:0crwdne5521:0

crwdns5469:0crwdne5469:0

-

crwdns5523:0crwdne5523:0 crwdns5525:0crwdne5525:0

crwdns5527:0crwdne5527:0

crwdns5529:0crwdne5529:0

crwdns5531:0crwdne5531:0

crwdns5533:0crwdne5533:0

crwdns5535:0crwdne5535:0 crwdns5537:0crwdne5537:0

crwdns5539:0crwdne5539:0

crwdns5541:0crwdne5541:0

crwdns5543:0crwdne5543:0

crwdns5545:0crwdne5545:0 crwdns5547:0crwdne5547:0

crwdns5549:0crwdne5549:0

crwdns5551:0crwdne5551:0

crwdns3212:0crwdne3212:0

crwdns2644:0crwdne2644:0

  • crwdns3214:0crwdne3214:0
    • crwdns4580:0crwdne4580:0

crwdns4584:0crwdne4584:0

  1. crwdns3220:0%Ccrwdnd3220:0%Ccrwdnd3220:0%9Ccrwdnd3220:0%Ccrwdnd3220:0%96crwdnd3220:0%Ccrwdne3220:0
  2. crwdns3222:0crwdne3222:0

crwdns5553:0crwdne5553:0

crwdns3226:0crwdne3226:0

  1. crwdns3228:0crwdne3228:0
  2. crwdns4588:0crwdne4588:0
  3. crwdns3232:0crwdne3232:0
  4. crwdns3234:0crwdne3234:0
    • crwdns3236:0crwdne3236:0
  5. crwdns3238:0crwdne3238:0
  6. crwdns4590:0crwdne4590:0
  7. crwdns3242:0crwdne3242:0
  8. crwdns3244:0crwdne3244:0
  9. crwdns4402:0crwdne4402:0
  10. crwdns4592:0crwdne4592:0
  11. crwdns3250:0crwdne3250:0
  12. crwdns3252:0crwdne3252:0

crwdns5555:0crwdne5555:0

crwdns5557:0crwdne5557:0

crwdns5559:0crwdne5559:0

crwdns5561:0crwdne5561:0

crwdns5563:0crwdne5563:0

crwdns6693:0crwdne6693:0

crwdns5567:0crwdne5567:0

- - - diff --git a/translate/credits.html b/translate/credits.html deleted file mode 100644 index 0c3dc8112..000000000 --- a/translate/credits.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - crwdns6215:0crwdne6215:0 | crwdns5445:0crwdne5445:0 - - - - -
crwdns5445:0crwdne5445:0

crwdns6215:0crwdne6215:0

crwdns5469:0crwdne5469:0

-

crwdns2580:0crwdne2580:0

crwdns2582:0crwdne2582:0

  • crwdns4716:0crwdne4716:0
  • crwdns4718:0crwdne4718:0
  • crwdns3458:0crwdne3458:0
  • crwdns2592:0crwdne2592:0
  • crwdns2594:0crwdne2594:0
  • crwdns4720:0crwdne4720:0
  • crwdns4722:0crwdne4722:0
  • crwdns4849:0crwdne4849:0
  • crwdns4724:0crwdne4724:0
  • crwdns6217:0crwdne6217:0

crwdns6219:0crwdne6219:0

crwdns6221:0crwdne6221:0 crwdns6223:0crwdne6223:0

- - - diff --git a/translate/dsiware-backups.html b/translate/dsiware-backups.html deleted file mode 100644 index b4186e1e3..000000000 --- a/translate/dsiware-backups.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - crwdns6099:0crwdne6099:0 | crwdns5445:0crwdne5445:0 - - - - -
crwdns5445:0crwdne5445:0

crwdns6099:0crwdne6099:0

crwdns5469:0crwdne5469:0

-

crwdns2508:0crwdne2508:0

  • crwdns3506:0crwdne3506:0
    • crwdns3508:0crwdne3508:0

crwdns3512:0crwdne3512:0

crwdns5287:0crwdne5287:0

  1. crwdns5289:0crwdne5289:0
  2. crwdns5291:0crwdne5291:0
  3. crwdns5293:0crwdne5293:0
    • crwdns5295:0crwdne5295:0
    • crwdns5297:0crwdne5297:0
    • crwdns5299:0crwdne5299:0
    • crwdns5301:0crwdne5301:0
    • crwdns5303:0crwdne5303:0
  4. crwdns5305:0crwdne5305:0
  5. crwdns5307:0crwdne5307:0 crwdns5309:0crwdne5309:0 crwdns5311:0crwdne5311:0
    • crwdns5313:0crwdne5313:0
    • crwdns5315:0crwdne5315:0

crwdns5317:0crwdne5317:0

  1. crwdns5319:0crwdne5319:0
  2. crwdns5321:0crwdne5321:0
  3. crwdns5323:0crwdne5323:0
    • crwdns5325:0crwdne5325:0
    • crwdns5327:0crwdne5327:0

crwdns6101:0crwdne6101:0

crwdns5331:0crwdne5331:0

  1. crwdns5333:0crwdne5333:0
  2. crwdns5335:0crwdne5335:0 crwdns5337:0crwdne5337:0
    • crwdns5339:0crwdne5339:0 crwdns5341:0crwdne5341:0
    • crwdns5343:0crwdne5343:0
- - - diff --git a/translate/dumping-game-cards.html b/translate/dumping-game-cards.html deleted file mode 100644 index 4df1a4143..000000000 --- a/translate/dumping-game-cards.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - crwdns6149:0crwdne6149:0 | crwdns5445:0crwdne5445:0 - - - - -
crwdns5445:0crwdne5445:0

crwdns6149:0crwdne6149:0

crwdns5469:0crwdne5469:0

-

crwdns4851:0crwdne4851:0

crwdns3364:0crwdne3364:0

  • crwdns4853:0crwdne4853:0
  • crwdns2470:0crwdne2470:0

crwdns3372:0crwdne3372:0

crwdns4704:0crwdne4704:0

crwdns6151:0crwdne6151:0

crwdns6153:0crwdne6153:0 crwdns6155:0crwdne6155:0

crwdns6157:0crwdne6157:0

  1. crwdns4857:0crwdne4857:0
  2. crwdns2478:0crwdne2478:0

crwdns4708:0crwdne4708:0

  1. crwdns3394:0crwdne3394:0
    • crwdns3396:0crwdne3396:0
  2. crwdns4370:0crwdne4370:0
  3. crwdns4859:0crwdne4859:0
  4. crwdns3406:0crwdne3406:0
  5. crwdns3408:0crwdne3408:0
    • crwdns3412:0crwdne3412:0
    • crwdns3414:0crwdne3414:0
  6. crwdns4861:0crwdne4861:0

crwdns6159:0crwdne6159:0

crwdns6161:0crwdne6161:0

crwdns6163:0crwdne6163:0

- - - diff --git a/translate/dumping-nand.html b/translate/dumping-nand.html deleted file mode 100644 index aed151a85..000000000 --- a/translate/dumping-nand.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - crwdns5603:0crwdne5603:0 | crwdns5445:0crwdne5445:0 - - - - -
crwdns5445:0crwdne5445:0

crwdns5603:0crwdne5603:0

crwdns5469:0crwdne5469:0

-

crwdns3724:0crwdne3724:0 crwdns4865:0$gbacrwdne4865:0

crwdns5611:0crwdne5611:0

crwdns5613:0crwdne5613:0 crwdns5615:0crwdne5615:0

crwdns5617:0crwdne5617:0

crwdns4670:0crwdne4670:0

crwdns5619:0crwdne5619:0

crwdns5621:0crwdne5621:0 crwdns5623:0crwdne5623:0

crwdns5625:0crwdne5625:0

  1. crwdns3740:0crwdne3740:0
  2. crwdns2938:0crwdne2938:0

crwdns3742:0crwdne3742:0

  1. crwdns3744:0crwdne3744:0
  2. crwdns3746:0crwdne3746:0
    • crwdns4672:0crwdne4672:0
  3. crwdns3750:0crwdne3750:0
  4. crwdns3752:0crwdne3752:0
  5. crwdns3754:0crwdne3754:0
    • crwdns3756:0crwdne3756:0
    • crwdns3758:0crwdne3758:0

crwdns5627:0crwdne5627:0

crwdns5629:0crwdne5629:0 crwdns5631:0$gbacrwdne5631:0 crwdns5633:0crwdne5633:0

crwdns5635:0crwdne5635:0

crwdns5637:0crwdne5637:0

crwdns5639:0crwdne5639:0

crwdns5641:0crwdne5641:0

- - - diff --git a/translate/faq.html b/translate/faq.html deleted file mode 100644 index 4737b998e..000000000 --- a/translate/faq.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - crwdns6015:0crwdne6015:0 | crwdns5445:0crwdne5445:0 - - - - -
crwdns5445:0crwdne5445:0

crwdns6015:0crwdne6015:0

crwdns5469:0crwdne5469:0

-

crwdns6017:0crwdne6017:0

  • crwdns3268:0crwdne3268:0
  • crwdns5213:0crwdne5213:0 crwdns6697:0crwdne6697:0
    • crwdns5217:0crwdne5217:0

crwdns6019:0crwdne6019:0

crwdns6021:0crwdne6021:0

  • crwdns3282:0crwdne3282:0 crwdns3284:0crwdne3284:0 crwdns3286:0crwdne3286:0 crwdns3288:0crwdne3288:0
  • crwdns6023:0crwdne6023:0 crwdns5225:0crwdne5225:0
    • crwdns5227:0crwdne5227:0

crwdns6025:0crwdne6025:0

  • crwdns6027:0crwdne6027:0
    • crwdns6029:0crwdne6029:0
  • crwdns3302:0crwdne3302:0
  • crwdns4730:0crwdne4730:0
  • crwdns2908:0crwdne2908:0
    • crwdns2910:0crwdne2910:0
  • crwdns5229:0crwdne5229:0

crwdns6031:0crwdne6031:0

crwdns6033:0crwdne6033:0 crwdns6035:0crwdne6035:0

  • crwdns4738:0crwdne4738:0 crwdns3334:0crwdne3334:0
  • crwdns6037:0crwdne6037:0

crwdns6039:0crwdne6039:0

  • crwdns4734:0crwdne4734:0

crwdns6041:0crwdne6041:0

crwdns6043:0crwdne6043:0

  • crwdns4746:0crwdne4746:0
  • crwdns4748:0crwdne4748:0
  • crwdns4750:0crwdne4750:0

crwdns6045:0crwdne6045:0

crwdns6047:0crwdne6047:0

  • crwdns6049:0crwdne6049:0 crwdns6051:0crwdne6051:0
- - - diff --git a/translate/file-extensions-(windows).html b/translate/file-extensions-(windows).html deleted file mode 100644 index f47b8205b..000000000 --- a/translate/file-extensions-(windows).html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - crwdns6225:0crwdne6225:0 | crwdns5445:0crwdne5445:0 - - - - -
crwdns5445:0crwdne5445:0

crwdns6225:0crwdne6225:0

crwdns5469:0crwdne5469:0

-

crwdns6227:0crwdne6227:0

crwdns2378:0crwdne2378:0

  1. crwdns2380:0crwdne2380:0
  2. crwdns2382:0crwdne2382:0
  3. crwdns6233:0crwdne6233:0crwdns6231:0crwdne6231:0

crwdns2390:0crwdne2390:0

  1. crwdns2392:0crwdne2392:0
  2. crwdns6239:0crwdne6239:0crwdns6237:0crwdne6237:0
  3. crwdns2400:0crwdne2400:0
  4. crwdns6245:0crwdne6245:0crwdns6243:0crwdne6243:0
- - - diff --git a/translate/index.html b/translate/index.html deleted file mode 100644 index ce0d6d135..000000000 --- a/translate/index.html +++ /dev/null @@ -1,43 +0,0 @@ - - - - - - - - - crwdns6105:0crwdne6105:0 | crwdns5445:0crwdne5445:0 - - - - -
crwdns5445:0crwdne5445:0

crwdns5445:0crwdne5445:0

crwdns5447:0crwdne5447:0

crwdns6111:0crwdne6111:0

crwdns6113:0crwdne6113:0crwdns6115:0crwdne6115:0

crwdns6117:0crwdne6117:0

crwdns6119:0crwdne6119:0

crwdns6121:0crwdne6121:0

crwdns6123:0crwdne6123:0

crwdns6125:0crwdne6125:0

crwdns6127:0crwdne6127:0

crwdns6129:0crwdne6129:0

crwdns2304:0crwdne2304:0

crwdns6131:0crwdne6131:0 crwdns6133:0crwdne6133:0

crwdns6135:0crwdne6135:0 crwdns6137:0crwdne6137:0 crwdns6139:0crwdne6139:0

crwdns3526:0crwdne3526:0

crwdns6141:0crwdne6141:0

  • crwdns3530:0crwdne3530:0
  • crwdns3532:0crwdne3532:0
  • crwdns4770:0crwdne4770:0 crwdns4648:0crwdne4648:0
    • crwdns3542:0crwdne3542:0 crwdns3544:0crwdne3544:0

crwdns2334:0crwdne2334:0

  • crwdns5231:0crwdne5231:0
  • crwdns4774:0crwdne4774:0
  • crwdns3562:0crwdne3562:0
  • crwdns4776:0crwdne4776:0
  • crwdns4778:0crwdne4778:0
  • crwdns5233:0crwdne5233:0
  • crwdns4782:0crwdne4782:0
  • crwdns5235:0crwdne5235:0
  • crwdns5237:0crwdne5237:0

crwdns3576:0crwdne3576:0

  • crwdns4784:0crwdne4784:0
  • crwdns4654:0crwdne4654:0

crwdns3582:0crwdne3582:0

  • crwdns3584:0%28crwdnd3584:0%29crwdne3584:0
  • crwdns3586:0crwdne3586:0
  • crwdns3588:0crwdne3588:0

crwdns6143:0crwdne6143:0

crwdns6145:0crwdne6145:0

crwdns6147:0crwdne6147:0

- - - diff --git a/translate/installing-unlaunch.html b/translate/installing-unlaunch.html deleted file mode 100644 index 728c63538..000000000 --- a/translate/installing-unlaunch.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - crwdns6053:0crwdne6053:0 | crwdns5445:0crwdne5445:0 - - - - -
crwdns5445:0crwdne5445:0

crwdns6053:0crwdne6053:0

crwdns5469:0crwdne5469:0

-

crwdns6055:0crwdne6055:0 crwdns6057:0crwdne6057:0

  • crwdns3598:0crwdne3598:0
  • crwdns4811:0crwdne4811:0
  • crwdns4813:0crwdne4813:0
  • crwdns4610:0crwdne4610:0
  • crwdns6059:0crwdne6059:0
  • crwdns6061:0crwdne6061:0
    • crwdns6063:0crwdne6063:0
    • crwdns6065:0crwdne6065:0

crwdns6067:0crwdne6067:0

crwdns4815:0crwdne4815:0 crwdns3614:0crwdne3614:0 crwdns4817:0crwdne4817:0

crwdns6069:0crwdne6069:0

crwdns6071:0crwdne6071:0

crwdns6073:0crwdne6073:0 crwdns6075:0crwdne6075:0

crwdns6077:0crwdne6077:0

crwdns4819:0crwdne4819:0

crwdns6079:0crwdne6079:0

crwdns6081:0crwdne6081:0 crwdns6083:0crwdne6083:0

crwdns6085:0crwdne6085:0

  1. crwdns4376:0crwdne4376:0
    • crwdns4378:0crwdne4378:0
  2. crwdns3634:0crwdne3634:0
  3. crwdns3636:0crwdne3636:0
    • crwdns6087:0crwdne6087:0

crwdns3640:0crwdne3640:0

  1. crwdns3642:0crwdne3642:0
    • crwdns4618:0crwdne4618:0
    • crwdns3646:0crwdne3646:0
  2. crwdns4620:0crwdne4620:0
    • crwdns3650:0crwdne3650:0 crwdns3652:0crwdne3652:0
  3. crwdns4823:0crwdne4823:0
  4. crwdns4624:0crwdne4624:0
    • crwdns4626:0crwdne4626:0
  5. crwdns4628:0crwdne4628:0
    • crwdns4825:0crwdne4825:0
  6. crwdns4630:0crwdne4630:0
  7. crwdns3664:0crwdne3664:0
  8. crwdns3666:0crwdne3666:0
    • crwdns3668:0crwdne3668:0
  9. crwdns3670:0crwdne3670:0

crwdns6089:0crwdne6089:0

  • crwdns3674:0crwdne3674:0

crwdns4632:0crwdne4632:0

crwdns6091:0crwdne6091:0

crwdns6093:0crwdne6093:0

  1. crwdns4827:0crwdne4827:0
    • crwdns4829:0crwdne4829:0
  2. crwdns3684:0crwdne3684:0
    • crwdns3686:0crwdne3686:0
    • crwdns4636:0crwdne4636:0 crwdns4638:0crwdne4638:0
      • crwdns3692:0crwdne3692:0
      • crwdns3694:0crwdne3694:0
    • crwdns3696:0crwdne3696:0
  3. crwdns3698:0crwdne3698:0
  4. crwdns3700:0crwdne3700:0
  5. crwdns3702:0crwdne3702:0
  6. crwdns4640:0crwdne4640:0 crwdns4642:0crwdne4642:0
  7. crwdns4644:0crwdne4644:0

crwdns4646:0crwdne4646:0

crwdns6247:0crwdne6247:0

crwdns6249:0crwdne6249:0

crwdns6251:0crwdne6251:0

  • crwdns3716:0crwdne3716:0
    • crwdns3718:0crwdne3718:0
  • crwdns3720:0crwdne3720:0
- - - diff --git a/translate/launching-the-exploit.html b/translate/launching-the-exploit.html deleted file mode 100644 index ba2c99c62..000000000 --- a/translate/launching-the-exploit.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - crwdns5761:0crwdne5761:0 | crwdns5445:0crwdne5445:0 - - - - -
crwdns5445:0crwdne5445:0

crwdns5761:0crwdne5761:0

crwdns5469:0crwdne5469:0

-

crwdns5765:0crwdne5765:0 crwdns5769:0crwdne5769:0

crwdns5773:0crwdne5773:0

crwdns3806:0crwdne3806:0

  • crwdns3808:0crwdne3808:0
  • crwdns3810:0crwdne3810:0

crwdns4578:0crwdne4578:0

crwdns5783:0crwdne5783:0

crwdns3814:0crwdne3814:0

crwdns5789:0crwdne5789:0

crwdns5793:0crwdne5793:0

crwdns5795:0crwdne5795:0 crwdns5799:0crwdne5799:0

crwdns5803:0crwdne5803:0

crwdns3820:0crwdne3820:0

  1. crwdns4869:0crwdne4869:0
    • crwdns4871:0crwdne4871:0
      • crwdns4873:0crwdne4873:0 crwdns4875:0crwdne4875:0
  2. crwdns4877:0crwdne4877:0
    • crwdns5817:0crwdne5817:0
    • crwdns5821:0crwdne5821:0
    • crwdns5825:0crwdne5825:0
  3. crwdns4885:0crwdne4885:0
    • crwdns4887:0crwdne4887:0 crwdns4889:0crwdne4889:0
    • crwdns4891:0crwdne4891:0
  4. crwdns4893:0crwdne4893:0
  5. crwdns4895:0crwdne4895:0

crwdns5839:0crwdne5839:0

crwdns5843:0crwdne5843:0

crwdns5847:0crwdne5847:0

crwdns3838:0crwdne3838:0

  1. crwdns3840:0crwdne3840:0
  2. crwdns3842:0crwdne3842:0
  3. crwdns3844:0crwdne3844:0

crwdns3846:0crwdne3846:0

  1. crwdns3848:0crwdne3848:0
  2. crwdns4897:0crwdne4897:0
  3. crwdns4594:0crwdne4594:0
    • crwdns3858:0crwdne3858:0
    • crwdns3860:0crwdne3860:0
  4. crwdns3862:0crwdne3862:0
    • crwdns3864:0crwdne3864:0

crwdns5869:0crwdne5869:0

crwdns5873:0crwdne5873:0 crwdns5877:0crwdne5877:0

crwdns5881:0crwdne5881:0

crwdns5885:0crwdne5885:0

crwdns5889:0crwdne5889:0

crwdns5893:0crwdne5893:0

crwdns5897:0crwdne5897:0

crwdns3874:0crwdne3874:0

  1. crwdns4907:0crwdne4907:0
  2. crwdns4909:0crwdne4909:0
  3. crwdns4911:0crwdne4911:0
  4. crwdns4913:0crwdne4913:0 crwdns4915:0crwdne4915:0
  5. crwdns4917:0crwdne4917:0
  6. crwdns4919:0crwdne4919:0
    • crwdns4921:0crwdne4921:0

crwdns5915:0crwdne5915:0

crwdns5919:0crwdne5919:0

crwdns5923:0crwdne5923:0

- - - diff --git a/translate/lazy-dsi-downloader.html b/translate/lazy-dsi-downloader.html deleted file mode 100644 index 53ab8da2f..000000000 --- a/translate/lazy-dsi-downloader.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - crwdns6165:0crwdne6165:0 | crwdns5445:0crwdne5445:0 - - - - -
crwdns5445:0crwdne5445:0

crwdns6165:0crwdne6165:0

crwdns5469:0crwdne5469:0

-

crwdns3152:0crwdne3152:0

crwdns3154:0crwdne3154:0

  1. crwdns3156:0crwdne3156:0
  2. crwdns3158:0crwdne3158:0

crwdns4845:0crwdne4845:0 crwdns4847:0crwdne4847:0

crwdns3162:0crwdne3162:0

  1. crwdns3164:0crwdne3164:0
    • crwdns3166:0crwdne3166:0 crwdns4736:0crwdne4736:0
  2. crwdns3170:0crwdne3170:0
  3. crwdns3172:0crwdne3172:0
  4. crwdns3174:0crwdne3174:0
    • crwdns3176:0crwdne3176:0
  5. crwdns3178:0crwdne3178:0
  6. crwdns3180:0crwdne3180:0
    • crwdns3182:0crwdne3182:0
  7. crwdns3184:0crwdne3184:0
- - - diff --git a/translate/restoring-nand.html b/translate/restoring-nand.html deleted file mode 100644 index 1fcb6e975..000000000 --- a/translate/restoring-nand.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - crwdns5643:0crwdne5643:0 | crwdns5445:0crwdne5445:0 - - - - -
crwdns5445:0crwdne5445:0

crwdns5643:0crwdne5643:0

crwdns5469:0crwdne5469:0

-

crwdns5645:0crwdne5645:0

crwdns4246:0crwdne4246:0 crwdns4248:0crwdne4248:0 crwdns4250:0crwdne4250:0 crwdns4252:0crwdne4252:0

crwdns5647:0crwdne5647:0

crwdns5649:0crwdne5649:0

crwdns5651:0crwdne5651:0

crwdns5653:0crwdne5653:0

crwdns5655:0crwdne5655:0

  • crwdns4262:0crwdne4262:0
  • crwdns4927:0crwdne4927:0 crwdns4929:0crwdne4929:0
  • crwdns4931:0crwdne4931:0
  • crwdns4268:0crwdne4268:0 crwdns4933:0crwdne4933:0 crwdns4272:0crwdne4272:0
  • crwdns5657:0crwdne5657:0
  • crwdns4937:0crwdne4937:0
  • crwdns4278:0crwdne4278:0

crwdns5659:0crwdne5659:0 crwdns5661:0crwdne5661:0

crwdns4284:0crwdne4284:0

  • crwdns4286:0crwdne4286:0
  • crwdns4288:0crwdne4288:0
  • crwdns4290:0crwdne4290:0
  • crwdns6685:0$gbacrwdne6685:0
    • crwdns6687:0$gbacrwdne6687:0
  • crwdns6691:0crwdne6691:0

crwdns4302:0$gbacrwdne4302:0

  1. crwdns4304:0crwdne4304:0
  2. crwdns4306:0crwdne4306:0
    • crwdns4308:0crwdne4308:0
  3. crwdns4310:0crwdne4310:0
  4. crwdns4312:0crwdne4312:0
  5. crwdns4314:0crwdne4314:0

crwdns4316:0crwdne4316:0

crwdns5669:0$gbacrwdne5669:0

  1. crwdns4320:0$GBAcrwdnd4320:0$gbacrwdne4320:0
  2. crwdns4322:0$GBAcrwdne4322:0
  3. crwdns4324:0$GBAcrwdne4324:0
  4. crwdns4326:0$GBAcrwdne4326:0
  5. crwdns4328:0crwdne4328:0
  6. crwdns4330:0crwdne4330:0
  7. crwdns4332:0crwdne4332:0
  8. crwdns5671:0crwdne5671:0
  9. crwdns4336:0crwdne4336:0

crwdns5673:0$gbacrwdne5673:0 crwdns5675:0crwdne5675:0

crwdns5677:0crwdne5677:0

crwdns5679:0crwdne5679:0 crwdns5681:0crwdne5681:0

  1. crwdns5683:0crwdne5683:0
  2. crwdns5685:0crwdne5685:0
  3. crwdns5687:0$gbacrwdne5687:0
    • crwdns5689:0crwdne5689:0
  4. crwdns5691:0crwdne5691:0
  5. crwdns5693:0crwdne5693:0
  6. crwdns5695:0crwdne5695:0

crwdns5697:0crwdne5697:0

crwdns5699:0crwdne5699:0

crwdns5701:0crwdne5701:0 crwdns5703:0crwdne5703:0

crwdns5705:0crwdne5705:0

crwdns5707:0crwdne5707:0

crwdns5709:0crwdne5709:0

crwdns5711:0crwdne5711:0

  1. crwdns5713:0crwdne5713:0
  2. crwdns5715:0crwdne5715:0
  3. crwdns5717:0crwdne5717:0
  4. crwdns5719:0crwdne5719:0

crwdns5721:0crwdne5721:0

crwdns5723:0crwdne5723:0

crwdns5725:0crwdne5725:0 crwdns5727:0crwdne5727:0

- - - diff --git a/translate/sd-card-setup.html b/translate/sd-card-setup.html deleted file mode 100644 index 0b09323ca..000000000 --- a/translate/sd-card-setup.html +++ /dev/null @@ -1,57 +0,0 @@ - - - - - - - - - crwdns5729:0crwdne5729:0 | crwdns5445:0crwdne5445:0 - - - - -
crwdns5445:0crwdne5445:0

crwdns5729:0crwdne5729:0

crwdns5469:0crwdne5469:0

-

crwdns3894:0crwdne3894:0 crwdns3896:0crwdne3896:0

crwdns5731:0crwdne5731:0

crwdns5733:0crwdne5733:0 crwdns5735:0crwdne5735:0

crwdns5737:0crwdne5737:0

crwdns6581:0crwdne6581:0

crwdns6583:0crwdne6583:0

crwdns6255:0crwdne6255:0

crwdns6585:0crwdne6585:0

crwdns6587:0crwdne6587:0 crwdns6589:0crwdne6589:0

crwdns6591:0crwdne6591:0

crwdns6593:0crwdne6593:0

crwdns6595:0crwdne6595:0 crwdns6597:0crwdne6597:0

crwdns6599:0crwdne6599:0

  1. crwdns6273:0crwdne6273:0
    • crwdns6275:0crwdne6275:0
  2. crwdns6277:0crwdne6277:0
  3. crwdns6279:0crwdne6279:0
  4. crwdns6281:0crwdne6281:0
  5. crwdns6283:0crwdne6283:0
  6. crwdns6285:0crwdne6285:0

crwdns6287:0crwdne6287:0

crwdns6601:0crwdne6601:0

crwdns6603:0crwdne6603:0

crwdns6605:0crwdne6605:0

crwdns6607:0crwdne6607:0

  1. crwdns6297:0crwdne6297:0
    • crwdns6299:0crwdne6299:0
  2. crwdns6301:0crwdne6301:0
  3. crwdns6303:0crwdne6303:0
  4. crwdns6305:0crwdne6305:0
    • crwdns6307:0crwdne6307:0
  5. crwdns6309:0crwdne6309:0
  6. crwdns6311:0crwdne6311:0

crwdns6315:0crwdne6315:0

  1. crwdns6317:0crwdne6317:0
    • crwdns6319:0crwdne6319:0
  2. crwdns6321:0crwdne6321:0
  3. crwdns6323:0crwdne6323:0
  4. crwdns6325:0crwdne6325:0

crwdns6611:0crwdne6611:0

crwdns6329:0crwdne6329:0

  1. crwdns6331:0crwdne6331:0
    • crwdns6333:0crwdne6333:0
  2. crwdns6335:0crwdne6335:0
  3. crwdns6337:0crwdne6337:0
  4. crwdns6339:0crwdne6339:0
  5. crwdns6341:0crwdne6341:0
  6. crwdns6343:0crwdne6343:0
  • crwdns6345:0crwdne6345:0

crwdns6613:0crwdne6613:0

crwdns6615:0crwdne6615:0

crwdns6617:0crwdne6617:0

crwdns6619:0crwdne6619:0

crwdns6621:0crwdne6621:0

crwdns6623:0crwdne6623:0

crwdns6625:0crwdne6625:0

crwdns6627:0crwdne6627:0

crwdns6361:0crwdne6361:0

  1. crwdns6363:0crwdne6363:0
  2. crwdns6365:0crwdne6365:0
  3. crwdns6367:0crwdne6367:0
  4. crwdns6369:0crwdne6369:0
  5. crwdns6371:0crwdne6371:0 crwdns6373:0crwdne6373:0
crwdns6375:0crwdne6375:0
-
  1. crwdns6377:0crwdne6377:0 crwdns6379:0crwdne6379:0
    • crwdns6381:0crwdne6381:0
  2. crwdns6383:0crwdne6383:0
  3. crwdns6385:0crwdne6385:0
    • crwdns6387:0crwdne6387:0
    • crwdns6389:0crwdne6389:0

crwdns6391:0crwdne6391:0

  1. crwdns6393:0crwdne6393:0
  2. crwdns6395:0crwdne6395:0
  3. crwdns6397:0crwdne6397:0
  4. crwdns6399:0crwdne6399:0
    • crwdns6401:0crwdne6401:0 crwdns6403:0crwdne6403:0
    crwdns6405:0crwdne6405:0 crwdns6407:0crwdne6407:0
-crwdns6409:0crwdne6409:0
-crwdns6411:0crwdne6411:0 crwdns6413:0crwdne6413:0
-crwdns6415:0crwdne6415:0
-
  5. crwdns6417:0crwdne6417:0
  • crwdns6419:0crwdne6419:0 crwdns6421:0crwdne6421:0
    crwdns6423:0crwdne6423:0
-crwdns6425:0crwdne6425:0
-

crwdns6629:0crwdne6629:0

crwdns6631:0crwdne6631:0

crwdns6633:0crwdne6633:0

crwdns6635:0crwdne6635:0

crwdns6637:0crwdne6637:0

crwdns6639:0crwdne6639:0

crwdns6641:0crwdne6641:0

crwdns6643:0crwdne6643:0

crwdns6441:0crwdne6441:0

crwdns6645:0crwdne6645:0

crwdns6647:0crwdne6647:0 crwdns6649:0crwdne6649:0

crwdns6457:0crwdne6457:0

crwdns6651:0crwdne6651:0

crwdns6653:0crwdne6653:0 crwdns6655:0crwdne6655:0

crwdns6657:0crwdne6657:0

  1. crwdns6459:0crwdne6459:0
    • crwdns6461:0crwdne6461:0
  2. crwdns6463:0crwdne6463:0
  3. crwdns6465:0crwdne6465:0
  4. crwdns6467:0crwdne6467:0
  5. crwdns6469:0crwdne6469:0
  6. crwdns6471:0crwdne6471:0

crwdns6473:0crwdne6473:0

crwdns6659:0crwdne6659:0

crwdns6561:0crwdne6561:0

crwdns6661:0crwdne6661:0

crwdns6565:0crwdne6565:0

crwdns6483:0crwdne6483:0

  1. crwdns6485:0crwdne6485:0
  2. crwdns6487:0crwdne6487:0
  3. crwdns6489:0crwdne6489:0
    • crwdns6491:0crwdne6491:0
  4. crwdns6493:0crwdne6493:0
  5. crwdns6495:0crwdne6495:0
    • crwdns6497:0crwdne6497:0
  6. crwdns6499:0crwdne6499:0
    • crwdns6501:0crwdne6501:0
  7. crwdns6503:0crwdne6503:0

crwdns6505:0crwdne6505:0

  1. crwdns6507:0crwdne6507:0
  2. crwdns6509:0crwdne6509:0
    • crwdns6511:0crwdne6511:0
  3. crwdns6513:0crwdne6513:0
    • crwdns6515:0crwdne6515:0
  4. crwdns6517:0crwdne6517:0
  5. crwdns6519:0crwdne6519:0
  6. crwdns6521:0crwdne6521:0
  7. crwdns6523:0crwdne6523:0

crwdns6525:0crwdne6525:0

  1. crwdns6527:0crwdne6527:0
  2. crwdns6529:0crwdne6529:0
    • crwdns6531:0crwdne6531:0
  3. crwdns6533:0crwdne6533:0
    • crwdns6535:0crwdne6535:0 crwdns6537:0crwdne6537:0
    crwdns6539:0crwdne6539:0 crwdns6541:0crwdne6541:0
-crwdns6543:0crwdne6543:0
-crwdns6545:0crwdne6545:0 crwdns6547:0crwdne6547:0
-crwdns6549:0crwdne6549:0
-
  4. crwdns6551:0crwdne6551:0
    • crwdns6553:0crwdne6553:0 crwdns6555:0crwdne6555:0
    crwdns6557:0crwdne6557:0
-crwdns6559:0crwdne6559:0
-

crwdns6663:0crwdne6663:0

crwdns6665:0crwdne6665:0

crwdns6571:0crwdne6571:0

crwdns6667:0crwdne6667:0

crwdns6669:0crwdne6669:0

crwdns6671:0crwdne6671:0

crwdns6673:0crwdne6673:0

crwdns6675:0crwdne6675:0

crwdns6677:0crwdne6677:0

crwdns6679:0crwdne6679:0

crwdns6681:0crwdne6681:0

- - - diff --git a/translate/site-navigation.html b/translate/site-navigation.html deleted file mode 100644 index 212241b29..000000000 --- a/translate/site-navigation.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - crwdns6167:0crwdne6167:0 | crwdns5445:0crwdne5445:0 - - - - -
crwdns5445:0crwdne5445:0

crwdns6167:0crwdne6167:0

crwdns5469:0crwdne5469:0

-

- - - diff --git a/translate/troubleshooting.html b/translate/troubleshooting.html deleted file mode 100644 index d8ae2be61..000000000 --- a/translate/troubleshooting.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - crwdns6175:0crwdne6175:0 | crwdns5445:0crwdne5445:0 - - - - -
crwdns5445:0crwdne5445:0

crwdns6175:0crwdne6175:0

crwdns5469:0crwdne5469:0

-

crwdns1700:0crwdne1700:0

crwdns5239:0crwdne5239:0

crwdns6177:0crwdne6177:0

crwdns6179:0crwdne6179:0 crwdns6181:0crwdne6181:0

crwdns6183:0crwdne6183:0

crwdns6185:0crwdne6185:0

  1. crwdns5245:0crwdne5245:0
  2. crwdns5247:0crwdne5247:0 crwdns5249:0crwdne5249:0
  3. crwdns6187:0crwdne6187:0

crwdns6189:0crwdne6189:0

crwdns6191:0crwdne6191:0 crwdns6699:0crwdne6699:0

crwdns5261:0crwdne5261:0

crwdns6195:0crwdne6195:0 crwdns6197:0crwdne6197:0

crwdns6199:0crwdne6199:0

crwdns6201:0crwdne6201:0 crwdns6203:0crwdne6203:0

crwdns5273:0crwdne5273:0

crwdns6205:0crwdne6205:0 crwdns6207:0crwdne6207:0

crwdns6209:0crwdne6209:0

crwdns6211:0crwdne6211:0

crwdns5283:0crwdne5283:0

crwdns6213:0crwdne6213:0

- - - diff --git a/translate/uninstalling-unlaunch.html b/translate/uninstalling-unlaunch.html deleted file mode 100644 index f45ad471b..000000000 --- a/translate/uninstalling-unlaunch.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - crwdns5569:0crwdne5569:0 | crwdns5445:0crwdne5445:0 - - - - -
crwdns5445:0crwdne5445:0

crwdns5569:0crwdne5569:0

crwdns5469:0crwdne5469:0

-

crwdns5571:0crwdne5571:0

crwdns5573:0crwdne5573:0 crwdns5575:0crwdne5575:0

crwdns5577:0crwdne5577:0

crwdns5579:0crwdne5579:0 crwdns5581:0crwdne5581:0

  • crwdns5583:0crwdne5583:0 crwdns3784:0crwdne3784:0
  • crwdns5585:0crwdne5585:0

crwdns5587:0crwdne5587:0

crwdns5589:0crwdne5589:0

crwdns5591:0crwdne5591:0

crwdns5593:0crwdne5593:0

crwdns5595:0crwdne5595:0 crwdns5597:0crwdne5597:0

crwdns5599:0crwdne5599:0

crwdns5601:0crwdne5601:0 crwdns5605:0crwdne5605:0

  • crwdns5607:0crwdne5607:0 crwdns5609:0crwdne5609:0
- - - diff --git a/troubleshooting.html b/troubleshooting.html index 0bdf81a27..f98eda4e1 100644 --- a/troubleshooting.html +++ b/troubleshooting.html @@ -3,7 +3,7 @@ - + - - 找不到页面 | DSi 破解指南 - - - - -
- - - diff --git a/zh_CN/alternate-exploits.html b/zh_CN/alternate-exploits.html deleted file mode 100644 index a4c7d3d11..000000000 --- a/zh_CN/alternate-exploits.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - 其他漏洞 | DSi 破解指南 - - - - -
DSi 破解指南

其他漏洞

加入 DS⁽ⁱ⁾ 模式破解! Discord ，为本指南贡献力量。

-

如果你按照本教程在启动Nintendo DSi 相机应用时遇到闪退，那么Memory Pit将不适用 Here, you may find alternate exploits that may work in lieu of Memory Pit.

如果您安装了 Flipnote Studio，您可以使用Flipnote Lenny。

TIP

Ensure you have set up TWiLight Menu++ on your SD card before proceeding with any of the following.

If you're on an older firmware, you may have access to save game exploits for a select list of games在新窗口打开. These will not be covered here as they are largely obsolete. They should only be used as a last resort, if both Memory Pit and Flipnote Lenny aren't working for you.

petit-compwner will not be usable for the purpose of working around Memory Pit, as it requires a working camera to launch the exploit.

- - - diff --git a/zh_CN/credits.html b/zh_CN/credits.html deleted file mode 100644 index 7d3a859ee..000000000 --- a/zh_CN/credits.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - 制作人员 | DSi 破解指南 - - - - -
DSi 破解指南

制作人员

加入 DS⁽ⁱ⁾ 模式破解! Discord ，为本指南贡献力量。

-

这是那些对指南网站、 homebrew和其他东西提供过帮助的人的名单。

如果你喜欢他们的所做，请考虑捐助(如果他们有捐赠链接)。

You can contribute to our guide too by simply sending in a pull request在新窗口打开!

如果你懂其他语言，你可以帮助我们把指南翻译成那种语言。 您可以通过加入我们的 Crowdin 项目在新窗口打开 来开始。

- - - diff --git a/zh_CN/dsiware-backups.html b/zh_CN/dsiware-backups.html deleted file mode 100644 index ce20f758a..000000000 --- a/zh_CN/dsiware-backups.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - DSiware备份 | DSi 破解指南 - - - - -
DSi 破解指南

DSiware备份

加入 DS⁽ⁱ⁾ 模式破解! Discord ，为本指南贡献力量。

-

首先需要…

Nintendo DSi - 说明

Section I - Dumping the DSiWare

  1. Launch GodMode9i
  2. Press START to open the START Menu
  3. Select Title manager...
    • If this isn't shown, ensure you have your SD card and NAND mounted. If loading from hiyaCFW reload from somewhere else
  4. Select the title you want to dump
  5. Select what you want to dump
  6. Repeat steps 4-5 for all of the DSiWare you wish to dump

TIP

The dumped DSiWare will be found in sd:/gm9i/out.

- - - diff --git a/zh_CN/dumping-game-cards.html b/zh_CN/dumping-game-cards.html deleted file mode 100644 index 83d91d55a..000000000 --- a/zh_CN/dumping-game-cards.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Dumping Game Cards | DSi 破解指南 - - - - -
DSi 破解指南

Dumping Game Cards

加入 DS⁽ⁱ⁾ 模式破解! Discord ，为本指南贡献力量。

-

This section is for dumping Game Cards using GodMode9i so they can be played on emulators, flashcards, or your SD card via nds-bootstrap.

需要准备

  • The Game Card of the title you would like to dump
  • Your Nintendo DSi console with Unlaunch installed

操作步骤

第一节 - SD 卡设置

  1. 下载最新版本的 GodMode9i在新窗口打开
  2. 从 GodMode9i 目录中解压 GodMode9i.nds 并复制到你SD卡的任意位置

第二节——DSi上的操作

  1. Launch GodMode9i
  2. Ensure the Game Card is inserted into the console
  3. Select the "NDS GAMECARD" option in GodMode9i
  4. Select what you want to dump
    • The "Trimmed" options for the ROM will dump a smaller file that can save SD card space, however they won't work for most patches such as ROM hacks
  5. Repeat steps 2-4 for all Game Cards you wish to dump

TIP

The dumped Game Cards will be found in sd:/gm9i/out.

- - - diff --git a/zh_CN/dumping-nand.html b/zh_CN/dumping-nand.html deleted file mode 100644 index b2a7f1265..000000000 --- a/zh_CN/dumping-nand.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - 提取NAND | DSi 破解指南 - - - - -
DSi 破解指南

提取NAND

加入 DS⁽ⁱ⁾ 模式破解! Discord ，为本指南贡献力量。

-

这个页面用于备份NAND，它是DSi内部数据的拷贝。 It can be used to set up hiyaCFW, as well as no$gba and melonDS for DSi emulation.

TIP

Make sure the SD card has at least 250MB of free space, or else you'll run into an error message in dumpTool.

TIP

It is highly recommended that you do this. A NAND backup can be used as a restore point in the future, in case of a brick.

第一节 - SD 卡设置

TIP

If you have already downloaded dumpTool from another section of this guide, you can skip this section.

  1. 下载最新版本的 dumpTool在新窗口打开
  2. 将 dumpTool.nds 放置在你SD卡的任意位置

第二节——提取NAND

  1. 通过 TWiLight 菜单++ 启动 dumpTool
  2. 点击Nintendo DSi上的 A 键来开始提取你的 NAND
    • NAND备份一般需要7分钟左右
  3. 当NAND备份完成后，按 START 按钮退出提取工具
  4. 关闭DSi并将SD卡插入您的电脑中
  5. 将此备份存储在任何安全且不会丢失的地方
    • 如果可能，请在不同的存储设备上做多个备份
    • 如果你在其他地方完成了备份，你可以在SD卡中将其删除

WARNING

The SHA1 hash of the nand.bin will not match the hash stored in nand.bin.sha1. This is because dumpTool adds additional data known as a no$gba footer to the nand.bin file after the SHA1 hash is calculated. You can use the hiyaCFW Helper在新窗口打开 to create a copy without the footer.

TIP

Continue to Installing Unlaunch (Optional)

- - - diff --git a/zh_CN/faq.html b/zh_CN/faq.html deleted file mode 100644 index 427910055..000000000 --- a/zh_CN/faq.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - 常见问题 | DSi 破解指南 - - - - -
DSi 破解指南

常见问题

加入 DS⁽ⁱ⁾ 模式破解! Discord ，为本指南贡献力量。

-

我是否应该进行系统更新？

It is not recommended to update your DSi unless you know there are purchased DSiWare. While it still possible to follow this guide if you do so, the only benefit to updating is the ability to access the Nintendo DSi Shop to redownload already purchased titles. All other benefits, such as Facebook integration in the Nintendo DSi Camera application, are no longer usable or are not significant enough to justify the downsides:

  • Installing System Updates is known to occasionally brick consoles, with roughly the same frequency as when installing Unlaunch
  • Older exploits are no longer possible to use, which may be required if you are unable use the recommended exploits
  • Flashcard compatibility is reduced, however this is bypassed if you install Unlaunch

Which is the best exploit?

Unlaunch is overall the best exploit for the DSi, with the only downside being that there is a minor brick risk on install. In general it's recommended to use Memory Pit to install Unlaunch. If you want to avoid any risk it's recommended to instead use Flipnote Lenny as it has fewer issues in homebrew than Memory Pit while being just as safe and simple to remove. Below is a list of the pros and cons of each exploit:

Memory Pit

Pros:

  • Quick and easy to use
  • No risk of damaging the console, uninstalling is as simple as removing the SD or deleting one file
  • Compatible with all DSi consoles unless they have a broken camera and haven't completed the camera tutorial

Cons:

  • Requires loading the DSi Camera application every time you want to access homebrew
  • Incompatible with certain DSi mode titles and homebrew due to WRAM only being open to the ARM7 CPU
  • Access to Slot-1 (the DS Game Card) is blocked in homebrew
  • Access to the DSP is blocked resulting in worse sound in GBARunner2
  • Photos on the SD card cannot be viewed in the DSi Camera application while Memory Pit is installed, as this is the trigger for the exploit
    • The only way to view SD card photos while Memory Pit is installed, is to launch a ROM dump of the DSi Camera application using TWiLight Menu++ to boot it via nds-bootstrap (v0.61.3 or later)

stylehax

Pros:

  • Better compatibility with DSi mode titles and homebrew than Memory Pit
  • Easy to use
  • No risk of damaging the console
  • Useable on consoles with broken camera
  • Better sound in GBARunner2

Cons:

  • Requires internet access
  • Requires loading the DSi Browser every time you want to access homebrew, slightly more time consuming than Memory Pit
  • Access to Slot-1 (the DS Game Card) is blocked in homebrew

Flipnote Lenny

Pros:

  • Better compatibility with DSi mode titles and homebrew than Memory Pit
  • No risk of damaging the console, uninstalling is as simple as removing the SD or deleting one folder
  • Useable on consoles with broken camera
  • Better sound in GBARunner2

Cons:

  • Requires loading Flipnote Studio every time you want to access homebrew, slightly more time consuming than Memory Pit
  • Access to Slot-1 (the DS Game Card) is blocked in homebrew

Unlaunch

Pros:

  • Allows loading homebrew and DSiWare immediately on system boot, with optional button hotkeys
  • Full access to the system without any restrictions, including:
    • Access to Slot-1 allowing dumping Game Cards and loading incompatible flashcards
    • Better sound in GBARunner2
  • Removes region locks on DSi-Enhanced/Exclusive Game Cards
  • Protection against most ways a DSi could brick
  • DSi-Enhanced games can be run in DSi mode without a Donor ROM
  • Old homebrew can be run via nds-bootstrap-hb

Cons:

  • Very minor risk of bricking the console when installing
  • Another, slightly higher, risk of bricking if you decide to uninstall it
  • Not compatible with development consoles

Will I lose any functionality by modding my system?

If you install Unlaunch or use Flipnote Lenny, no functionality will be lost. If you use Memory Pit, you will be unable to view photos on the SD card using the DSi Camera, unless you launch a ROM dump of the DSi Camera application using TWiLight Menu++ to boot it via nds-bootstrap.

  • To regain the ability to view your SD card photos when launching the DSi Camera from the DSi Menu, install Unlaunch or switch to a different exploit, then delete Memory Pit's pit.bin file
    • If tip.bin exists in the same folder, rename it back to pit.bin

How do I play Nintendo DS Game Card dumps?

Playing Game Card dumps on the console requires the use of a flashcard or nds-bootstrap, a program which enables games to be played from the internal SD card by redirecting Slot-1 reads and writes to it.

  • With TWiLight Menu++ you can navigate your SD card to find ROM files to play with nds-bootstrap. The advantages to using TWiLight Menu++ are having a cheat menu, per-game settings, and avoiding the restrictions that forwarders bring. In other words, you can drop your ROM files directly and play without any setup. There is no 39 title limit, neither hiyaCFW or Unlaunch are required and there are no restrictions on SD card free space you can have
  • hiyaCFW users can create forwarders for the SDNAND's DSi Menu using the DS Game Forwarders在新窗口打开 guide on the DS-Homebrew Wiki, but it has some limitations. There is a hard limit of 39 titles, and they are less convenient to make than using TWiLight Menu++

How do I update my homebrew?

  • Unlaunch - Follow the instructions on the Installing Unlaunch page
    • You do not need to uninstall Unlaunch before doing this
  • hiyaCFW - Replace hiya.dsi on the root of the SD card from the updated release在新窗口打开
  • TWiLight Menu++ - Follow the instructions on the DS-Homebrew Wiki在新窗口打开
  • nds-bootstrap - Copy nds-bootstrap-hb-release.nds & nds-bootstrap-release.nds to the _nds folder on the root of your SD card
    • If you use TWiLight Menu++, there is a high chance that the latest nds-bootstrap release is included with TWiLight Menu++
  • GodMode9i, dumpTool, Forwarder3-DS, etc - Follow the instructions used to download them

Other homebrew might use other methods to update.

I am new or I would like to redo my setup. Where do I start?

  • If you have not already modified your console or are looking to update Unlaunch on your system, we recommend starting from the beginning of the guide and following through the pages. Be sure to read everything on the homepage
  • If you have the latest version Unlaunch, follow the TWiLight Menu++ install guide在新窗口打开 to set up TWiLight Menu++ on your system

How can I remove parental controls?

Can I change my Nintendo DSi's region?

Yes, there are a few different methods depending on what you want to change:

What happened to the hiyaCFW installation guide?

Because hiyaCFW does not serve much functional purpose and was a problematic and confusing part of the guide for many users, it was moved to the DS-Homebrew Wiki在新窗口打开.

  • If you were linked to the page in question from another guide, the instructions you were following were most likely outdated. Please use this guide instead, as it is maintained constantly by the developers of these projects

What kind of SD card should I use?

  • You should buy an SD card from a trusted brand
  • A full-size SD card or a microSD card with an adapter will both work
  • Any capacity between 1 GB and 2 TB will work. For general usage, 8 GB is enough
    • Some software, such as hiyaCFW, may experience incrementally longer loading times with larger SD card capacities
  • Speed class 8 or higher is recommended

Can I use my DSi SD card on other systems?

Generally, yes, with two exceptions:

  • hiyaCFW will only work on the system it was set up for
  • Even if you are using nds-bootstrap or a flashcard, friend codes in online NDS games will be reset when attempting to go online using a different console

How do I switch to a new SD card after setting up homebrew?

Format your new SD card using the SD Card Setup instructions, then simply move your data from the old SD card to the new one.

Can I still use my system normally without the SD card inserted after setting up homebrew?

Yes. If you did not install Unlaunch, your system will remain completely unmodified. If you did install Unlaunch, you may need to configure Unlaunch to automatically boot the original DSi Menu under specified conditions.

The Unlaunch page在新窗口打开 says that version 2.0 is not known to be safe. Should I use a previous version instead?

The Unlaunch page has not been updated since version 2.0 was released, which was over two years ago. The vast majority of users experience no issues with this version, so it is considered safe.

How do I run dumped DSiWare?

The recommended method is to simply launch them with TWiLight Menu++, due to the simple drag-and-drop method and there being no arbitrary limit. When nds-bootstrap is set as the launch method, it also gains the benefits of cheats and screenshots, as well as any other benefit provided by the in-game menu.

However, for the few titles that are incompatible, you can use NTM在新窗口打开 to install them on either internal memory or hiyaCFW's SDNAND在新窗口打开. In addition to lacking the benefits above, there is also a limit of 39 titles that cannot exceed 128 MiB/1,024 blocks in size. For SysNAND, there is also a very small risk of bricking the system when writing to the internal NAND.

- - - diff --git a/zh_CN/file-extensions-windows.html b/zh_CN/file-extensions-windows.html deleted file mode 100644 index c4b64bdbb..000000000 --- a/zh_CN/file-extensions-windows.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - 文件扩展名 (Windows) | DSi 破解指南 - - - - -
DSi 破解指南

文件扩展名 (Windows)

加入 DS⁽ⁱ⁾ 模式破解! Discord ，为本指南贡献力量。

-

这是一个禁用 Windows 默认隐藏文件扩展名的设置的附加指南，使你在查找指南中提到的文件更加方便。

  1. 打开资源管理器，导航到任意目录，例如SD卡的根目录。
  2. Click the "View" option on the top bar
    • If the option is not present, click the ··· button on the rightmost part of the top bar
  3. Click or hove your cursor on the Show > submenu
  4. Check the option labeled File name extensions Screenshot of hovering the "File name extensions" checkbox on Windows 11
  1. 打开资源管理器，导航到任意目录，例如SD卡的根目录。
  2. Click the "View" option on the ribbon menu
  3. Check the box labeled "File name extensions" Screenshot of hovering the "File name extensions" checkbox on Windows 10
  1. Open the start menu by clicking on it or using the Windows key
  2. Search for "Folder Options" and select the corresponding result Screenshot of a search for "folder options" in the Windows 7 Start Menu
  3. Click the "View" option at the top of the Folder Options menu
  4. Make sure the box labeled "Hide extensions for known file types" is unchecked Screenshot of the "Folder Options" window on Windows 7 with "Hide extensions for known types" turned off
- - - diff --git a/zh_CN/get-started.html b/zh_CN/get-started.html deleted file mode 100644 index fff4b08ae..000000000 --- a/zh_CN/get-started.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Get Started | DSi 破解指南 - - - - -
DSi 破解指南

Get Started

加入 DS⁽ⁱ⁾ 模式破解! Discord ，为本指南贡献力量。

-

The main homebrew application this guide has you install is TWiLight Menu++, which is an upgrade/replacement to the Nintendo DSi Menu that allows running other homebrew applications, retail DS games, emulators for various older systems, and more.

We'll begin with downloading it as well as some other homebrew tool(s), in preparation for the exploit steps.

首先需要…

Section I - Prep Work

WARNING

Ensure your SD card is formatted correctly.

  1. Insert your SD card into your PC
  2. Download the latest release of TWiLight Menu++在新窗口打开
  3. 下载最新版本的 dumpTool在新窗口打开
  4. Copy the _nds folder from TWiLightMenu-DSi.7z to the root of your SD card
  5. Copy the BOOT.NDS file from TWiLightMenu-DSi.7z to the root of your SD card
  6. Copy the dumpTool.nds file to the root of your SD card

TIP

Unsure what the SD "root" is? See this image在新窗口打开

Section II - Selecting an exploit

From here you have three options, with a minor difference in what each entails.

Installing Unlaunch via Memory Pit

Memory Pit is an exploit utilizing the DSi Camera, compatible with all firmware versions. Optionally, this exploit can be used to install Unlaunch, a bootcode exploit that allows full control of the console on boot.

As Memory Pit is somewhat limited in homebrew compatibility, it is recommended to install Unlaunch, instead of using Memory Pit standalone. As this is the easiest method to install Unlaunch, this is the recommended path. However, there is a very minor risk of bricking your console when installing Unlaunch, so if this is a concern, see the alternate method below.

TIP

Continue to Launching the Exploit

stylehax

stylehax is an exploit utilizing the DSi Browser application, and can be used as an alternative to Memory Pit for installing Unlaunch (explained above) if your DSi has a broken camera.

For an Unlaunch-free experience, this exploit is recommended as using Memory Pit causes issues in some games and homebrew.

TIP

Continue to Launching the Exploit (stylehax)

Flipnote Lenny

Flipnote Lenny is an exploit utilizing the Flipnote Studio application.

If you have Flipnote Studio and do not plan on installing Unlaunch (explained above), this exploit is recommended for the same reason as stylehax.

You can always install Unlaunch later if you decide later on that you want it.

TIP

Continue to Launching the Exploit (Flipnote Lenny)

For a more detailed pros and cons comparision of the available exploits, please see the Which is the best exploit? FAQ.

- - - diff --git a/zh_CN/index.html b/zh_CN/index.html deleted file mode 100644 index a0bb0fce5..000000000 --- a/zh_CN/index.html +++ /dev/null @@ -1,43 +0,0 @@ - - - - - - - - - 首页 | DSi 破解指南 - - - - -
DSi 破解指南

DSi 破解指南

最完整的 Nintendo DSi 破解指南

TIP

欲了解其他设备的自制程序和自定义固件的完整指南，请参阅 CFW.Guide在新窗口打开

TIP

在继续之前，请详细阅读包括本页在内的全部介绍页面。

自制程序（Homebrew）是什么 ？

自制在新窗口打开 软件 是指为一个封闭生态的系统上开发并使用非正常渠道安装的软件，例如我们将会提到的 Nintendo DSi. 这些软件涵盖实用工具到自制游戏。

自制软件可以在所有 Nintendo DSi 机器上免费、自由地运行，与固件版本或区域无关。 您需要的只是一个入口点和一个SD卡来存储您的自制程序。 本指南中使用的主要入口点将称为 Memory Pit. 但如果 Memory Pit 不可用，您还可以使用其他入口点。

我可以通过修改我的主机来做什么？

  • 直接从 DSi 的SD卡上运行 Nintendo DS(i) 游戏备份或ROM模组，而不需要烧录卡
  • Launch any DSiWare from your SD card
    • This means out-of-region and 3DS-exclusive DSiWare will also work
  • 在Nintendo DSi开机时通过长按特定的按钮来启动至DSiWare和自制程序
  • 用各种模拟器玩老游戏
  • 使用通常情况下不兼容的烧录卡
  • 将 NAND 重定向到 SD 卡中安装的 hiyaCFW
  • Watch your favorite movies using either FastVideoDSPlayer or tuna-viDS
    • FastVideoDSEncoder requires a CPU supporting AVX2 (newer CPUs will likely support it)
  • 在启动时显示自定义图像（取代原生启动动画）
  • 玩自制游戏

在哪里能找到自制软件？

在开始之前我应该知道什么？

  • 在 Windows 操作系统中，如果使用默认的文件资源管理器，建议显示文件扩展名
  • 唯一会使设备变砖的风险来自 Unlaunch，但机率微乎其微

TIP

继续至 开始

- - - diff --git a/zh_CN/installing-unlaunch.html b/zh_CN/installing-unlaunch.html deleted file mode 100644 index 5a019e2e0..000000000 --- a/zh_CN/installing-unlaunch.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - 安装 Unlaunch | DSi 破解指南 - - - - -
DSi 破解指南

安装 Unlaunch

加入 DS⁽ⁱ⁾ 模式破解! Discord ，为本指南贡献力量。

-

DANGER

If you have not yet done so, please follow Dumping NAND. While the chances are slim, Unlaunch can accidentally brick your Nintendo DSi. A NAND backup + hardmod在新窗口打开 would allow you to restore this backup, provided you know how to solder.

WARNING

Make sure your console is charged when following this process. A sudden power loss could result in serious damage.

WARNING

Unlaunch is not compatible with Nintendo DSi development consoles.

第一节 - SD 卡设置

  1. 下载最新版本的 Unlaunch 在新窗口打开
    • 使用镜像链接在新窗口打开，如果上述链接无法工作 1.从unlaunch.zip中解压UNLAUNH.DSI并复制到你SD卡的任意位置 1.确认你的SD卡上仍然有TWiLight菜单++
  2. 从SD卡中删除UNLAUNH.DSI文件
  3. 确认你的SD卡上仍然有 TWiLight 菜单++

第二节——安装/更新Unlaunch

  1. 打开TWiLight Menu++
    • If this is your first time installing Unlaunch, relaunch TWiLight Menu++ through the exploit that you used
    • If you have already installed Unlaunch and are looking to update it, hold A + B while booting and select the option labeled TWiLight Menu++
    • If several options are labeled TWiLight Menu++, select the option in where BOOT.NDS is shown at the end of the path on the bottom screen
  2. 启动 TWiLight Menu++ 设置
    • If you haven't changed your theme, press SELECT and touch the small DS icon on the bottom of the touch screen. Otherwise, see the TWiLight Menu++ Manual
  3. 点击 L / R 或 X / Y 直到您到达 Unlaunch settings 页面
  4. If you want to change Unlaunch's background image, select Background and choose the one you want
  5. Exit TWiLight Menu++ Settings
  6. In the file navigation menu, launch Unlaunch DSi Installer
    • If you see two black screens after launching, download GodMode9i在新窗口打开, put its .dsi file on the SD root, then launch GodMode9i using TWiLight Menu++, and start Unlaunch.dsi
      This method does not enable Unlaunch to use custom patches and background
  7. Select the "install now" option
    • If Unlaunch freezes at ERROR: MISMATCH IN FAT COPIES, please take a look at the Troubleshooting page
  8. When completed, reboot your system

If you see Unlaunch's Filemenu screen at this point, you have successfully modded your Nintendo DSi.

第三部分 - 启动后配置

Currently, Unlaunch defaults to launching its Filemenu on boot, but this can be changed launch whatever you want.

  1. 摁住 A 和 B键 后，再摁下 Dsi 的电源键
    • 这应该能启动到Unlaunch Filemenu
    • If only the background is shown, or if no files from the SD card are shown (ex. TWiLight Menu++), then you'll need to reformat the SD card
  2. 导航到 OPTIONS, 并查看可用的选项
    • A + B被硬编码启动到Unlaunch的菜单，因此无法更改
    • “NO BUTTON”和“BUTTON A / B / X / Y”选项可以根据您的喜好进行设置，并根据按住的按钮选择 DSi 在启动时加载的内容。您可以选择任何 DSiWare、自制软件、Slot-1 卡、wifiboot 或 Unlaunch 的文件菜单 您可以选择任何DSIWare，Homebrew，Slot-1卡，Wifiboot或Unlaunch能引导的文件
      • For TWiLight Menu++, select TWiLight Menu++
      • 想要原生 DSi 菜单，请选择 Launcher
    • LOAD ERROR出现时说明加载出现问题，例如SD卡未插入
  3. 选择SAVE & EXIT以保存设置，然后关闭您的DSI

第四部分 - 清理你的 SD 卡

TIP

This section is optional and only serves for keeping your SD card tidy of files you won't need.

  • Delete the sd:/private/ds/app/484E494A/pit.bin file from your SD card
    • If tip.bin still exists, then rename it back to pit.bin
  • You can now restore the DCIM folder that was on the root of your SD card, if this folder existed
  • 从SD卡中删除sd:/private/ds/app/484E494A/pit.bin文件
  • Delete the 800031_104784BAB6B57_000.ppm and T00031_1038C2A757B77_000.ppm files from inside the following folders:
    • sd:/private/ds/app/4B47554A/001 (Japan)
    • sd:/private/ds/app/4B475545/001 (USA)
    • sd:/private/ds/app/4B475556/001 (Europe/Australia)
    • You can also delete the entire folders for the regions besides your own
  • 从SD卡中删除sd:/private/ds/app/484E494A/pit.bin文件
- - - diff --git a/zh_CN/launching-the-browser-exploit.html b/zh_CN/launching-the-browser-exploit.html deleted file mode 100644 index 3b68d4551..000000000 --- a/zh_CN/launching-the-browser-exploit.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Launching the Exploit (stylehax) | DSi 破解指南 - - - - -
DSi 破解指南

Launching the Exploit (stylehax)

加入 DS⁽ⁱ⁾ 模式破解! Discord ，为本指南贡献力量。

-

We'll start by first launching our exploit. For the best Unlaunch-free experience, or if the DSi camera is broken to install Unlaunch, we recommend using an exploit called "stylehax" which takes advantage of a flaw in how the DSi Browser application handles webpages.

运行这个漏洞，它就会引导进入 TWiLight Menu++ ，一个DSi菜单的自制替换版本。

首先需要…

  • Nintendo DSi Browser installed on your Nintendo DSi
    • If you do not have the DSi Browser, then use Memory Pit instead

Launching the exploit

  1. Ensure your SD card is inserted into your Nintendo DSi
  2. Boot your Nintendo DSi and launch the DSi Browser application
  3. Touch the Go to Page button
    • The button will have a green www icon
  4. Type opera:about, and touch Go to load the page
  5. Touch the HOME icon
  6. Touch the Go to Page button
  7. Type stylehax.net, and touch Go to load the page

TIP

The exploit should take 21 seconds to take effect. If it takes longer than 30 seconds, then reboot, and try again.

WARNING

If the top screen turns green, you do not have TWiLight Menu++'s BOOT.NDS on the root of your SD card. Follow the prep work again.

You can now use TWiLight Menu++! First, it will ask you to select your language and region. These do not need to match your console's language or region, so set them to whichever you prefer. Next, it's recommended to continue on and make a NAND backup. This can potentially be used to save your console if anything bad happens in the future.

TIP

Continue to Dumping NAND

- - - diff --git a/zh_CN/launching-the-exploit.html b/zh_CN/launching-the-exploit.html deleted file mode 100644 index 3de580935..000000000 --- a/zh_CN/launching-the-exploit.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - 启动漏洞 | DSi 破解指南 - - - - -
DSi 破解指南

启动漏洞

加入 DS⁽ⁱ⁾ 模式破解! Discord ，为本指南贡献力量。

-

我们首先准备好SD卡来启动漏洞。 对于大多数用户，我们建议用一个叫做“Memory Pit”的漏洞，是一个利用Nintendo DSi Camera（iQue DSi 趣照）应用在处理数据时存在的漏洞实现的。

运行这个漏洞，它就会引导进入 TWiLight Menu++ ，一个DSi菜单的自制替换版本。

TIP

If you don't plan on installing Unlaunch and have either the DSi Browser or Flipnote Studio, it is recommended to use either stylehax or Flipnote Lenny instead. Which is the best exploit?

Section I - Checking your DSi Camera Version

  1. 打开你的机器电源
  2. Open Nintendo DSi Camera
    • If you are prompted to complete the camera tutorial, do so now
    • If the tutorial crashes as you try to complete it, your Nintendo DSi camera hardware is likely broken in some way and you will not be able to use Memory Pit. Please use an alternate exploit
  3. Open the album using the large button on the right
  4. Take note of whether you have a Facebook icon alongside the star, clubs, and heart, outlined in red here: Screenshot of where the Facebook icon is located

第二节 - Memory Pit

  1. Download the correct Memory Pit binary for your Nintendo DSi Camera version:
  2. Navigate to the sd:/private/ds/app/484E494A/ folder on your SD card
    • You will already have this directory if you have previously taken photos to your SD card via the Nintendo DSi Camera application. If so, you do not need to delete it and recreate it
    • If it does not exist, please create the individual folders
  3. If there is already a pit.bin file in that path, rename it to tip.bin
  4. Place the Memory Pit pit.bin file in this folder
  5. If there's a folder named DCIM in the root of your SD card, make a back up of it so you don't lose the pictures inside, and then remove it from the SD card

Section III - Launching the exploit

  1. Ensure your SD card is inserted into your Nintendo DSi
  2. Boot your Nintendo DSi and launch the Nintendo DSi Camera application
  3. Select the SD Card icon in the top-right
    • If you receive a message saying your SD card isn't inserted, please use another SD card
    • If you receive a message saying that your SD card cannot be used, ensure your SD card is formatted correctly
  4. Open the album using the large button on the right
    • The screen should flash magenta if Memory Pit was copied correctly

WARNING

If the top screen turns green, you do not have TWiLight Menu++'s BOOT.NDS on the root of your SD card. Follow the prep work again.

WARNING

If you enter the SD card camera album and nothing unusual happens, ensure that you downloaded the correct version of Memory Pit for your version and region, and placed it into the correct folder on your SD card. Also ensure that the DCIM folder does not exist on your SD card.

You can now use TWiLight Menu++! First, it will ask you to select your language and region. These do not need to match your console's language or region so set them to whichever you prefer. Next it's recommended to continue on and make a NAND backup. This can potentially be used to save your console if anything bad happens in the future.

TIP

Continue to Dumping NAND

- - - diff --git a/zh_CN/launching-the-flipnote-exploit.html b/zh_CN/launching-the-flipnote-exploit.html deleted file mode 100644 index a3c1052c5..000000000 --- a/zh_CN/launching-the-flipnote-exploit.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Launching the Exploit (Flipnote Lenny) | DSi 破解指南 - - - - -
DSi 破解指南

Launching the Exploit (Flipnote Lenny)

加入 DS⁽ⁱ⁾ 模式破解! Discord ，为本指南贡献力量。

-

我们首先准备好SD卡来启动漏洞。 For the best Unlaunch-free experience, we recommend using an exploit called "Flipnote Lenny" which takes advantage of a flaw in how the Flipnote Studio application handles flipnotes.

运行这个漏洞，它就会引导进入 TWiLight Menu++ ，一个DSi菜单的自制替换版本。

首先需要…

  • Flipnote Studio installed on your Nintendo DSi
    • If you do not have Flipnote Studio, then use Memory Pit instead

第一节 - SD 卡设置

  1. Download the latest version of Flipnote Lenny在新窗口打开
  2. Copy the private folder from the Flipnote Lenny archive to the root of your SD card

Section II - Launching the exploit

  1. Ensure your SD card is inserted into your Nintendo DSi
  2. Boot your Nintendo DSi and launch the Flipnote Studio application
    • If you receive a message saying that your SD card cannot be used, ensure your SD card is formatted correctly
  3. Open the Flipnote Studio settings on the top-right of the main menu and ensure that Start on Calendar is disabled and Frog is enabled
  4. View the flipnotes stored on the SD card
    • If you are unable to view the flipnotes on the SD card, please use another SD card
  5. Tap on the face corresponding to your region
    • If you have an AUS console, select EUR
  6. Edit the selected flipnote
  7. Tap the frog icon on the bottom-left
  8. Tap on the film roll icon
  9. Select Copy -> Back -> Exit
  10. Tap on the second note with a larger face, and select Edit
  11. Tap on the frog icon on the bottom-left
  12. Tap on the film roll icon
  13. Select paste

WARNING

If the top screen turns green, you do not have TWiLight Menu++'s BOOT.NDS on the root of your SD card. Follow the prep work again.

You can now use TWiLight Menu++! First, it will ask you to select your language and region. These do not need to match your console's language or region, so set them to whichever you prefer. Next, it's recommended to continue on and make a NAND backup. This can potentially be used to save your console if anything bad happens in the future.

TIP

Continue to Dumping NAND

- - - diff --git a/zh_CN/lazy-dsi-downloader.html b/zh_CN/lazy-dsi-downloader.html deleted file mode 100644 index 6e23e824d..000000000 --- a/zh_CN/lazy-dsi-downloader.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - Lazy DSi File Downloader（DSi懒人下载包） | DSi 破解指南 - - - - -
DSi 破解指南

Lazy DSi File Downloader（DSi懒人下载包）

加入 DS⁽ⁱ⁾ 模式破解! Discord ，为本指南贡献力量。

-

“Lazy DSi Downloader”是一个简化破解Nintendo DSi 过程的工具。

核查步骤

  1. 打开你的任天堂DSi
  2. 启动到 Nintendo DSi 相机应用程序

If at this point you get a tutorial and crash when trying to follow it, then you cannot use Memory Pit.

设置指南

  1. Download the latest release of Lazy DSi File Downloader在新窗口打开 for your OS
  2. Launch it via the instructions for your operating system listed in the release page
  3. Hit the Next button
    • The intro text isn't mandatory to read
  4. If your Nintendo DSi crashed during the verification steps above, toggle off the Memory Pit option
  5. Hit the check boxes for "Download latest GodMode9i version?"
    • Feel free to select any of the other homebrew applications in Click to add Additional homebrew..., but this is not mandatory
  6. Wait for everything to download, then hit Finish
- - - diff --git a/zh_CN/restoring-nand.html b/zh_CN/restoring-nand.html deleted file mode 100644 index 0e8de43ad..000000000 --- a/zh_CN/restoring-nand.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - 还原 NAND备份 | DSi 破解指南 - - - - -
DSi 破解指南

还原 NAND备份

加入 DS⁽ⁱ⁾ 模式破解! Discord ，为本指南贡献力量。

-

DANGER

警告！ 这非常 危险！！！ 即使严格按照这些步骤操作也有可能使DSi变砖，因为机器的NAND闪存质量很低，尤其是如果你已经多次刷机！ 这只能作为最后手段使用！

TIP

请勿跳过此页上的 任何步骤, 任何错误都会使得你DSi的变砖几率增加.

首先，除了你打算这样做的原因之外，还有几种更安全的替代选择：

  • 可以使用 hiyaCFW 或 TWiLight 菜单++安装DSiWare
  • 如果您想要在终端上同时使用 TWiLight Menu++与hiyaCFW ，可以使用 ninfs在新窗口打开来恢复图片。 HiyaCFW助手的最新版本允许您在设置过程中将您的照片从 NAND 复制到 SDNAND
  • Restoring an Unlaunch button configuration can be done from the Unlaunch menu, which can be accessed by holding A + B while powering the console on
  • 启动至Unlaunch导致错误？ 取出SD卡，并且重启系统。 如果这有用，那么是SD卡出了错，还原NAND备份将不会修复它
  • "An error has occurred..." on boot is likely a hiyaCFW error and is not related to your NAND, see hiyaCFW FAQ & Troubleshooting在新窗口打开 on the DS-Homebrew Wiki for more information
  • TWiLight 菜单++中的任何错误都与NAND无关，您应该尝试重新安装 TWiLight 菜单++或在 Discord在新窗口打开 上寻求帮助
  • 除非绝对有必要，否则应避免通过刷入NAND或使用其卸载器来卸载 您可以将自动启动密钥设置为“Launcher”，您的 DSi就会恢复正常了

你唯一应该用你的NAND做的事情是安装Unlaunch 除此之外，请用其他替代方法

需要准备

提取BIOS 以便使用no$gba

  1. 从 dsibiodumper.zip 压缩包中解压 dsibiosdumper.nds 并将其放置在你SD卡的任意位置
  2. 摁住 A 和 B键 后，再摁下 Dsi 的电源键
    • 这应该能启动到Unlaunch Filemenu
  3. 从Unlaunch Filemenu启动 dsibiosdumper。
  4. 按 A 将BIOS 导出到SD卡
  5. 按 Start 退出 dsibiosdumer

测试你的NAND备份

在尝试将NAND备份恢复到您的机器之前，测试您的NAND备份是否能用非常重要， 如果它在no$gba 时显示变砖错误，它很可能也会使您的机器变砖。

  1. 将 NO$GBA.EXE 从 no$gba-w.zip 解压到您计算机上的一个文件夹中
  2. 将您的NAND备份复制到您放置 NO$GBA.EXE 的文件夹，并重命名为 DSI-1.MMC
  3. 复制 bios7i.bin 和 bios9i.bin 到您放置 NO$GBA. EXE的文件夹, 分别命名为 BIOSDSI7.ROM 和 BIOSI9.ROM
  4. 运行 NO$GBA.EXE
  5. 点击 Options > Emulation Setup 来打开模拟器设置窗口
  6. 改变 Reset/Startup Entrypoint 为 GBA/NDS BIOS (Nintendo logo)
  7. 改变 NDS Mode/Colors为 DSi (retail/16MB)
  8. Click Save Now
  9. 加载任何 NDS ROM (.nds 文件)

If no$gba loads the DSi menu (or the Unlaunch Filemenu), then continue to the next section. 如果出现任何错误 不要刷入那个备份！

Uninstalling Unlaunch from your NAND backup (optional)

Follow this if you dumped your NAND backup after you installed Unlaunch and you would like to uninstall Unlaunch from your system. If you are not trying to uninstall Unlaunch, you do not need to do this section.

  1. Download the latest version of the Unlaunch installer在新窗口打开
  2. Extract UNLAUNCH.DSI from unlaunch.zip
  3. Launch UNLAUNCH.DSI in no$gba and start it from the Game Card slot
    • This should start the Unlaunch installer, which looks similar to to the Unlaunch Filemenu
  4. Choose Uninstall
  5. Once complete, choose Power down
  6. Launch any Nintendo DS ROM again, and ensure your DSi menu loads and is working properly

If no$gba shows any kind of error instead of loading the DSi menu, do not flash that backup! If you have an older NAND backup you may want to try using that instead. Do not try to uninstall Unlaunch using its uninstaller on the console, it is extremely likely doing so will brick your DSi.

刷入你的NAND备份 (软件方式)

DANGER

Make sure you have read through the above steps as this is where it gets dangerous. If you were linked directly to here without following the above, then go back to the top and read this whole page.

DANGER

Make sure your Nintendo DSi system is well charged before beginning this section.

  1. 在插入 SD 卡的状态下，按住 A 和B 开机
  2. 启动 SafeNANDManager
  3. 按下 begin NAND restore
  4. 一旦恢复完成，按 start 关闭您的 DSi

Your NAND should now be restored.

刷入你的NAND备份 (硬件修改)

If you cannot boot your Nintendo DSi, a hardmod is the only way to restore a NAND backup. The best guide that currently exists is the Nintendo DSi hardmod guide on the DS-Homebrew Wiki在新窗口打开.

- - - diff --git a/zh_CN/sd-card-setup.html b/zh_CN/sd-card-setup.html deleted file mode 100644 index e2086f738..000000000 --- a/zh_CN/sd-card-setup.html +++ /dev/null @@ -1,85 +0,0 @@ - - - - - - - - - SD 卡设置 | DSi 破解指南 - - - - -
DSi 破解指南

SD 卡设置

加入 DS⁽ⁱ⁾ 模式破解! Discord ，为本指南贡献力量。

-

This page is for preparing your SD card for your device. In the process, we'll format the SD card and check the card for errors.

DANGER

请确保以此操作之前，备份您SD卡的内容。 您的SD卡将在这个过程中被擦除数据。

Section I - Formatting your SD card with SD Formatter

TIP

This section formats the SD card to the specifications by the SD Card Association. This can fix many issues that may occur with running homebrew applications.

DANGER

Any 64GB or larger SD cards will be formatted to exFAT in this process. You must follow Section II to re-format to FAT32.

  1. Download the latest version of SD Formatter在新窗口打开
  2. Run SD Card Formatter Setup (the .exe file) in the downloaded .zip file with Adminstrator privileges, then install the program
  3. Run SD Card Formatter from the Start Menu with Adminstrator privileges
  4. 选择你的 SD 卡
  5. 确认 Quick Format 复选框已被勾选
  6. Press Format to start the format process Screenshot of SD Card Formatter on Windows 11

Section II - Formatting your SD card with GUIFormat

This section formats SD cards larger than 32GB to FAT32.

TIP

If your SD card is 32GB or less in capacity, skip to Section III.

  1. 下载最新版本的 GUIFormat在新窗口打开
    • 点击网页上的图片以下载应用程序
  2. 使用管理员权限运行 GUIFormat
  3. 选择 SD 卡对应的盘符
  4. Set the Allocation size unit to 32768
    • 如果这对于您的 SD卡来说太大的话，请将它尽可能设置为最高
  5. 确认 Quick Format 复选框已被勾选
  6. 开始格式化进程

第三节——检查错误

  1. 转到SD卡的属性窗口
    • Windows 文件管理器 -> 此电脑 -> 右键点击你的SD卡 -> 属性
  2. 在“工具”选项卡中选择检查
  3. 同时检查"自动修复文件系统错误"和"扫描并尝试恢复错误扇区"
  4. 开始进行检查

这将扫描SD卡并纠正它发现的任何错误.

第四节 - 检查 SD 卡读/写

  1. 下载 the h2testw archive在新窗口打开 并将其解压到你电脑上任意地方
  2. 将SD卡插入您的计算机，运行 h2testw.exe
  3. 在 h2testw 中选择中文或其他语言
  4. 在“Drive”一行选择你的 SD 卡盘符
  5. 确保 all available space 已勾选
  6. 点击 Write + Verify
  • 等待完成

TIP

If the test shows the result Test finished without errors, your SD card is healthy and you can delete all .h2w files on your SD card.

DANGER

如果测试结果显示任何其他结果，您的 SD 卡可能已经出错或损坏，可能需要更换 ！

TIP

If TWiLight Menu++ fails to start after following this method, please follow the Windows method instead, by either rebooting to Windows or running a Windows Virtual Machine

第一节 - 格式化您的 SD 卡

  1. 请确保你的SD卡 没有 插入到你的Linux设备
  2. 启动Linux终端
  3. 输入 watch "lsblk"
  4. 插入你的SD卡到你的Linux设备
  5. 观察终端输出内容 输出内容应该与以下内容搭配：
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
-mmcblk0     179:0    0   3,8G  0 disk
-└─mmcblk0p1 179:1    0   3,7G  0 part /run/media/user/FFFF-FFFF
-
  1. Take note of the device name. In our example above, it was mmcblk0p1
    • 如果 RO 设置为1, 确保锁定开关并没有滑下
    • Make sure you're targetting the partition, mmcblk0p1 not mmcblk0
  2. 按 CTRL + C 键退出菜单
  3. Follow the instructions relevant to your SD card's capacity:
    • 2GB or lower: sudo mkdosfs /dev/(device name from above) -s 64 -F 16
      • This creates a single FAT16 partition with 32 KB cluster size on the SD card
    • 4GB or higher: sudo mkdosfs /dev/(device name from above) -s 64 -F 32
      • This creates a single FAT32 partition with 32 KB cluster size on the SD card

第 二 节 - 使用F3

  1. 下载并解压 F3 文件在新窗口打开 到你的计算机的任意地方
  2. 在F3文件夹里启动终端
  3. 输入 make 对F3进行打包
  4. 插入并安装SD卡，输入 ./f3write <your sd card mount point>
    • 等待处理完毕。 请参阅下面的示例。
    $ ./f3write /media/michel/6135-3363/
-Free space: 29.71 GB
-Creating file 1.h2w ... OK!
-...
-Creating file 30.h2w ... OK!
-Free space: 0.00 Byte
-Average Writing speed: 4.90 MB/s
-
  5. 运行 ./f3read <your sd card mount point>
  • 等待处理完毕。 请参阅下面的示例。
    $ ./f3read /media/michel/6135-3363/
-                  SECTORS      ok/corrupted/changed/overwritten
-Validating file 1.h2w ... 2097152/        0/      0/      0
-...
-Validating file 30.h2w ... 1491904/        0/      0/      0
-
-   Data OK: 29.71 GB (62309312 sectors)
-Data LOST: 0.00 Byte (0 sectors)
-            Corrupted: 0.00 Byte (0 sectors)
-   Slightly changed: 0.00 Byte (0 sectors)
-         Overwritten: 0.00 Byte (0 sectors)
-Average Reading speed: 9.42 MB/s
-

TIP

If the test shows the result Data LOST: 0.00 Byte (0 sectors) your SD card is healthy and you can delete all .h2w files on your SD card.

DANGER

如果测试结果显示任何其他结果，您的 SD 卡可能已经出错或损坏，可能需要更换 ！

Section I - Formatting your SD card with SD Formatter

TIP

This section formats the SD card to the specifications by the SD Card Association. This can fix many issues that may occur with running homebrew applications.

DANGER

Any 64GB or larger SD cards will be formatted to exFAT in this process. You must follow Section II to re-format to FAT32.

  1. Download the latest version of SD Formatter在新窗口打开
    • Accept the End User License Agreement to start the download
  2. Run Install SD Card Formatter (the .mpkg file) in the downloaded .zip file
  3. Run SD Card Formatter
  4. 选择你的 SD 卡
  5. 确认 Quick Format 复选框已被勾选
  6. 开始格式化进程

Section II - Formatting your SD card with Disk Utility

This section formats SD cards larger than 32GB to FAT32.

TIP

If your SD card is 32GB or less in capacity, skip to Section III.

OS X El Capitan (10.11) 及更高版本

  1. 启动"Disk Utility"应用程序
  2. 通过左上角的 View 面板，选择 Show All Devices
  3. 从侧边栏选择你的SD卡
    • 确保你选择的是正确的设备, 否则你可能会格式化错误的驱动器
  4. 点击顶端的Erase
  5. 确保 Format 设置为 MS-DOS (FAT32)
    • 在 El Capitan(10.11) 中通过 Catalina (10.15) 选择 MS-DOS (FAT)
  6. 确保 Scheme 被设置为 Master Boot Record
    • 如果"Scheme"不显示, 点击"Cancel"并确保你选择的不是声音设备
  7. 点击 Erase, 再点击 Close

OS X Yosemite (10.10) 及更早版本

  1. 启动"Disk Utility"应用程序
  2. 从侧边栏选择你的SD卡
    • 确保你选择的是正确的设备, 否则你可能会格式化错误的驱动器
  3. 点击顶部的 Partition
    • 如果"Partition"不显示, 请确保你选择的不是声音设备
  4. 确保Partition Layout 被设为 1 Partition
  5. 确保 Format 设置为 MS-DOS (FAT)
  6. 从设置按钮 (分区表下方), 选择"Master Boot Record"
  7. 点击 OK -> Apply -> Partition

第 三 节 - 使用F3键

  1. 打开终端
  2. 输入 brew install f3，从brew安装 F3
  3. 插入并安装SD卡，输入 f3write <your sd card mount point>
    • 等待处理完毕。 请参阅下面的示例。
    $ f3write /Volumes/SD\ CARD
-Free space: 29.71 GB
-Creating file 1.h2w ... OK!
-...
-Creating file 30.h2w ... OK!
-Free space: 0.00 Byte
-Average Writing speed: 4.90 MB/s
-
  4. 运行 f3read <your sd card mount point>
    • 等待处理完毕。 请参阅下面的示例。
    $ f3read /Volumes/SD\ CARD
-                  SECTORS      ok/corrupted/changed/overwritten
-Validating file 1.h2w ... 2097152/        0/      0/      0
-...
-Validating file 30.h2w ... 1491904/        0/      0/      0
-
-   Data OK: 29.71 GB (62309312 sectors)
-Data LOST: 0.00 Byte (0 sectors)
-            Corrupted: 0.00 Byte (0 sectors)
-   Slightly changed: 0.00 Byte (0 sectors)
-         Overwritten: 0.00 Byte (0 sectors)
-Average Reading speed: 9.42 MB/s
-

TIP

If the test shows the result Data LOST: 0.00 Byte (0 sectors) your SD card is healthy and you can delete all .h2w files on your SD card.

DANGER

如果测试结果显示任何其他结果，您的 SD 卡可能已经出错或损坏，可能需要更换 ！

TIP

You can now restore the contents of your SD card and continue.

- - - diff --git a/zh_CN/site-navigation.html b/zh_CN/site-navigation.html deleted file mode 100644 index f7b761dc3..000000000 --- a/zh_CN/site-navigation.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - 网站导航 | DSi 破解指南 - - - - -
DSi 破解指南

网站导航

加入 DS⁽ⁱ⁾ 模式破解! Discord ，为本指南贡献力量。

-

- - - diff --git a/zh_CN/troubleshooting.html b/zh_CN/troubleshooting.html deleted file mode 100644 index 584d43aa4..000000000 --- a/zh_CN/troubleshooting.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - 故障排查 | DSi 破解指南 - - - - -
DSi 破解指南

故障排查

加入 DS⁽ⁱ⁾ 模式破解! Discord ，为本指南贡献力量。

-

Unlaunch

Unlaunch 停留在 MISMATCH IN FAT COPIES

在没有正确更新整个NAND时破解，twlnf会有一个关键的bug。 这会导致某些自制程序(如Unlaunch安装程序) 出现错误。

To fix this, open NAND Title Manager (NTM)在新窗口打开, and select Fix FAT copy mismatch.

在使用 Unlaunch启动"LAUNCHER"时没有声音或启动画面

The developer of Unlaunch (nocash) has intentionally patched out the background audio and boot-splash by default. You can regain these effects by reinstalling Unlaunch using TWiLight Menu++ with "Launcher Patches" set to "Default" on the Unlaunch page of TWiLight Menu++ settings, or by using hiyaCFW在新窗口打开.

Powering on only shows a black screen after installing Unlaunch

Try ejecting the SD card and powering the console on again. If it still only shows a black screen, you may need to flash your NAND via a hardmod在新窗口打开.

After installing Unlaunch, I'm stuck booting into an application

This was likely caused by choosing the wrong app for the NO BUTTON option in Unlaunch. Hold A + B while starting the console, go to OPTIONS, and set NO BUTTON to whatever your preference is.

Other Unlaunch problems

If Unlaunch displays Clusters too large, Bad VBR, Bad MBR, or doesn't display any applications while the SD card is inserted, your SD card likely wasn't formatted correctly. Re-follow SD Card Setup.

TWiLight Menu++ troubleshooting

For general TWiLight Menu++ troubleshooting, see its FAQ & Troubleshooting在新窗口打开 page on the DS-Homebrew Wiki.

Further assistance

If you have encountered an issue that is not solved here, or one that persists despite the given solutions, ask for assistance in the DS(i) Mode Hacking!在新窗口打开 Discord server.

- - - diff --git a/zh_CN/uninstalling-unlaunch.html b/zh_CN/uninstalling-unlaunch.html deleted file mode 100644 index 2fdfe4bd7..000000000 --- a/zh_CN/uninstalling-unlaunch.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - 卸载 Unlaunch | DSi 破解指南 - - - - -
DSi 破解指南

卸载 Unlaunch

加入 DS⁽ⁱ⁾ 模式破解! Discord ，为本指南贡献力量。

-

DANGER

正在安装或卸载Unlaunch，可能会随机是你的机器变砖！ 你已被警告！

警告: 卸载Unlaunch可能会砖掉你的 DSi 。 这里有一些关于您可能想要卸载Unlaunch，但并不需要卸载Unlaunch就可解决问题的例子。

  • The Unlaunch Background is scary: Reinstall Unlaunch using the new instructions. 它们现在包含关于如何改变背景的说明
  • 没有开机界面，且音乐丢失： 使用 新操作说明 重新安装。 它们现在包含缓解此问题的说明

WARNING

减少变砖的几率， 请确保您的系统NAND中的没有安装任何非合法的 DSiWare(不包括HiyaCFW 提供的 SDNAND 重定向)， 或以其他方式篡改系统文件。

WARNING

When uninstalling Unlaunch, you should NOT use its built-in uninstaller directly on your console as there is a chance that it will brick the console. Please see below for information on uninstalling it properly.

Once you have reviewed the above information, follow the Dumping NAND instructions to make a new NAND bacup, then proceed to Restoring a NAND Backup. This will guide you through uninstalling Unlaunch from the NAND backup and flashing that to your console.

If you are not able to use no$gba or get an error after uninstalling Unlaunch in no$gba it is also possible to flash a NAND backup made prior to installing Unlaunch if you still have one, however it is recommended to try using a NAND backup that previously had Unlaunch first. This will make recovery significantly easier in the case of a brick requiring a hardmod as Unlaunch leaves the no$gba footer embedded in the NAND even when uninstalled.

- - -