בעיות ופתרונות - GamerTunerit/Guide GitHub Wiki

אם אתה לא מסוגל להדליק את ה-3DS שלך, בבקשה תסתכל בחלק הרלוונטי אליך בדף הזה, ועקוב אחרי ההוראות. ברגע שהפתרון יעבוד עבורך, תוכל להמשיך מאיפה שהפסקת במדריך הראשי.

(החלק הזה מאוד ארוך, לחץ Ctrl+f על מנת לחפש את הבעיה שלך יותר מהר)

אם אתה עדיין לא מסוגל לפתור את הבעיה שלך וצריך עזרה, בבקשה תעלה את כל קבצי ה.log הרולוונטים משורש כרטיס הזיכרון שלך ל-Up1, ואז תבוא לעזרה עם מידע מפורט עם הבעיה שלך ומה שניסית לעשות.

פריצה מבוססת דפדפן אינה עובדת פריצות מבוססות דפדפן(כמו browserhax או 2xrsa) הם רוב הפעמים לא יציבים ונותים גם לקרוס, אבל ניתן רוב הפעמים לתקן את זה בביצוע הפעולות הבאות:

1.פתח את הדפדפן, ואז פתח את ההגדרות של הדפדפן

1. גלול לתחתית ובחר Initialize Savedata(זה אולי יכול להיקרא גם Clear All Save Data)
2. נסה שוב את האקספלויט

You copied the wrong arm9loaderhax.bin file to your SD card (you were only supposed to copy the 3ds folder and SafeA9LHInstaller.dat file from the SafeA9LHInstaller zip).

1. Use the correct arm9loaderhax.bin
   1. Copy arm9loaderhax.bin from the Luma3DS zip to the root of your SD card
   2. Reboot holding select and continue

1. Try resetting Luma's config and fix options
   1. Delete /luma/config.bin from your SD card
   2. Set your options when it boots
2. Try restoring a backup to RedNAND. (You should have one of these)

Do the steps for the error you are getting.

####"FIRM0 hash mismatch!"

1. STOP; DO NOT TOUCH ANYTHING; A REBOOT RIGHT NOW COULD BRICK YOU IF AN INCORRECT FIRM WAS INSTALLED TO SYSNAND
2. Download the 2.1.0 firm.bin (mirror)
3. On your 3DS, press B until you see the main menu
4. Carefully press the SELECT button to eject your SD card
5. WITHOUT TURNING OFF YOUR 3DS, take your SD card out and put it in your computer
6. Copy firm.bin to the root of your SD card
7. Reinsert your SD card into your 3DS
8. Press B until you see the main menu
9. Select "FIRM Dump & Inject..."
10. Select "EmuNAND FIRM0 Inject" from firm.bin
11. Select "EmuNAND FIRM1 Inject" from firm.bin
12. Press B until you see the main menu
13. Perform "One Click Setup"
14. If this still fails, restore SysNAND from sysNAND_original.bin, restore RedNAND from emuNAND_formatted.bin and retry from Part 4 - Section II - Step 9.

####"Validation Stage 1: FAILED" and "Validation Stage 2: FAILED"

The workaround for this issue was confusing and bricked a few users, so it has been removed.

You should restore SysNAND from sysNAND_original.bin, restore RedNAND from emuNAND_formatted.bin and retry from Part 4 - Section II - Step 9.

####"Validation Stage 1: SUCCESS" and "Validation Stage 2: FAILED"

This will happen due to having a fragmented NAND (caused by various things such as rxTools' shitty FBI injection or some Gateway software). OTPHelper cannot check the files of a fragmented NAND, but if you got "Validation Stage 1: SUCCESS" then "Validation Stage 2: FAILED" will rarely be an anything but a false positive.

You can either flash to SysNAND at your own risk, or attempt to defragment your NAND by using Decrypt9 to dump your CTRNAND partition, then mounting it on your computer using something like OSFMount and defragging that mounted CTRNAND using something like Defraggler.

1. Make sure you do not have any folder named "Decrypt9" on the root of your SD card
2. Try redownloading and recopying the OTPHelper files
3. Try checking your SD card file system with something like fsck.vfat <sd partition path> (on *nix) or CHKDSK <sd drive letter> /F (on Windows)
4. Try backing up your SD card files, then formatting it and copying them back
5. Try a different SD card

1. Try booting with your SD card out, and then reinserting it after booting.
   1. Power off your 3DS by holding down the power button.
   2. Take out the SD card.
   3. Power on the 3DS.
   4. When the home menu appears, reinsert your SD card.
2. If you have a hardmod and a NAND backup, flash the backup back to SysNAND.
3. Try booting into recovery mode and updating your system.
   This probably will not work for an Old 3DS downgraded to 2.1.0
   This will BRICK a New 3DS downgraded to 2.1.0
   1. Power off your 3DS by holding down the power button.
   2. Hold L+R+A+Up.
   3. Power on the 3DS.
   4. If you enter safe mode, update your 3DS only if you have an entrypoint for the latest FW version and it is possible to downgrade from it and attempt the downgrade again.
4. Your 3DS may be bricked. For real time support, contact me or any other channel operator at #3dshacks on Rizon IRC.

1. Ensure you have a working payload.
   1. Check for the existence of arm9loaderhax.bin in the root of your SD card.
   2. Check that
      1. /luma/firmware.bin exist; and
      2. /luma/firmware.bin is the correct one for your console.
2. Try resetting Luma's config and fix options
   1. Delete /luma/config.bin from your SD card
   2. Set your options when it boots
3. Test booting Decrypt9 2. On Luma3DS, hold Start on boot
4. Try this test payload (mirror).
   1. Rename /arm9loaderhax.bin, if it exists, to something else.
   2. Place the arm9loaderhax.bin from the archive linked above in your SD root.
   3. Insert your SD card into your 3DS and power on.
   4. Press A. Your 3DS should power off; this means arm9loaderhax is working and something else is broken; your device is not bricked.
5. Your 3DS may be bricked. For real time support, contact me or any other channel operator at #3dshacks on Rizon IRC.

1. Your 3DS is bricked.
2. You will need to get a hardmod or repair / replace the device.