Hacking I have a problem during Ntrboot CFW.

[Jangmonim]

My nintendo is New 2DS XL. It was CFWed and it has changed another country. It also has Emunand. (Sysnand:Korean / Emunand:English) Then I forgot to erase the Emunand and change to my country, and I uninstalled CFW. (Godmode9 - uninstall Hax) So I thought to unbrick it, that is to do Ntrboot. I have checked the files in the R4 cartridge, and Nintendo one also. I tried so many times but it never entered in SafeB9Sinstaller. I need you guys' help.

 

[Jangmonim]

My nintendo is New 2DS XL. It was CFWed and it has changed another country. It also has Emunand. (Sysnand:Korean / Emunand:English) Then I forgot to erase the Emunand and change to my country, and I uninstalled CFW. (Godmode9 - uninstall Hax) So I thought to unbrick it, that is to do Ntrboot. I have checked the files in the R4 cartridge, and Nintendo one also. I tried so many times but it never entered in SafeB9Sinstaller. I need you guys' help.

I have a strong magnet and it was correct position. I think it's maybe sleep mode error.

 

[KleinesSinchen]

My nintendo is New 2DS XL. It was CFWed and it has changed another country. It also has Emunand. (Sysnand:Korean / Emunand:English) Then I forgot to erase the Emunand and change to my country, and I uninstalled CFW. (Godmode9 - uninstall Hax) So I thought to unbrick it, that is to do Ntrboot. I have checked the files in the R4 cartridge, and Nintendo one also. I tried so many times but it never entered in SafeB9Sinstaller. I need you guys' help.

Not again one of those bricks by uninstalling B9S after critical changes to the system. The Guide has a lot of checks, including booting native firm to see if proceeding with Uninstall Hax will brick the device. (And uninstalling B9S still doesn't make any sense).

The EmuNAND doesn't do anything here. Without CFW it is just a partition on the SD.
============

The problem with ntrboot failing is, that there are way too many variables and possible causes that lead to the same result: "Doesn't work." My favorite method for things like this is the process of elimination. Find out what is not the problem to narrow down the possibilities.
Reasons for ntrboot failing:

• Magnet too weak and/or positioning wrong (yes, I read that you are sure about this, I mention it anyway)
  • Temporarily not triggering the magnetic switch while touching the buttons is enough for make it fail.
• Holding the button combination not long enough or too long → I got the best results with releasing (Power) a little before releasing the other buttons
• boot.firm not found
  • file missing
  • file corrupted (not a valid firm)
  • wrong name due to Windows operating system not showing extensions (boot.firm.firm)
    
  • bad SD
  • wrong file system (must be FAT32)
  • damaged file system
  • defective SD reader (that one is really bad)
• ntrboothax cart not found
  • Flashcart not correctly flashed with ntrboothax
  • Contact issues → flashcarts are often not as precisely manufactured as legit games
  • defective cartridge reader (also obviously very bad)

Having everything listed that comes to my mind at the moment I would advise you to use your ntrboot cart on an O2DS (no magnet problems) with a µSD inside and adapter (so you can use the same µSD on your N2DSXL). The µSD should only contain SafeB9SInstaller (and B9S files) or GodMode9 or Luma3DS as boot.firm
If this works it will rule out a bunch of possible causes from my list at once.

Last comment: When using ntrboot to get into GodMode9 on my (non-CFW) N2DSXL to dump universal legit Mario Kart 7 I was pulling my hair out. That thing was stubborn as a mule while I can pull off ntrboot on N3DS(XL) pretty consistently.

Good luck!

 

[Jangmonim]

Not again one of those bricks by uninstalling B9S after critical changes to the system. The Guide has a lot of checks, including booting native firm to see if proceeding with Uninstall Hax will brick the device. (And uninstalling B9S still doesn't make any sense).

The EmuNAND doesn't do anything here. Without CFW it is just a partition on the SD.
============

The problem with ntrboot failing is, that there are way too many variables and possible causes that lead to the same result: "Doesn't work." My favorite method for things like this is the process of elimination. Find out what is not the problem to narrow down the possibilities.
Reasons for ntrboot failing:

• Magnet too weak and/or positioning wrong (yes, I read that you are sure about this, I mention it anyway)
  • Temporarily not triggering the magnetic switch while touching the buttons is enough for make it fail.
• Holding the button combination not long enough or too long → I got the best results with releasing (Power) a little before releasing the other buttons
• boot.firm not found
  • file missing
  • file corrupted (not a valid firm)
  • wrong name due to Windows operating system not showing extensions (boot.firm.firm)
    
  • bad SD
  • wrong file system (must be FAT32)
  • damaged file system
  • defective SD reader (that one is really bad)
• ntrboothax cart not found
  • Flashcart not correctly flashed with ntrboothax
  • Contact issues → flashcarts are often not as precisely manufactured as legit games
  • defective cartridge reader (also obviously very bad)

Having everything listed that comes to my mind at the moment I would advise you to use your ntrboot cart on an O2DS (no magnet problems) with a µSD inside and adapter (so you can use the same µSD on your N2DSXL). The µSD should only contain SafeB9SInstaller (and B9S files) or GodMode9 or Luma3DS as boot.firm
If this works it will rule out a bunch of possible causes from my list at once.

Last comment: When using ntrboot to get into GodMode9 on my (non-CFW) N2DSXL to dump universal legit Mario Kart 7 I was pulling my hair out. That thing was stubborn as a mule while I can pull off ntrboot on N3DS(XL) pretty consistently.

Good luck!

I have tried another 3DS if the R4 cartridge really work. On the 3DS, It worked very well. It's not problem in the file both Nintendo and R4. Maybe the problem is in the magnet or the cartridge reader. I'm looking forward to save this. Thanks for your good comment.

 

[Jangmonim]

Oh Is it right? I closed the nintendo and the blue light doesn't decrease and still bright. Is it means nintendo cannot go to sleep mode?

 

[KleinesSinchen]

Oh Is it right? I closed the nintendo and the blue light doesn't decrease and still bright. Is it means nintendo cannot go to sleep mode?

As far as I know this is expected.*
The software has to react on the (magnetic) sleep switch. Since the Home Menu never loads, there is nothing active that could go to sleep mode.

The magnetic switch should still trigger with a good magnet (please don't use some ridiculously strong magnet) and make ntrboot possible.



_______________
* I will softbrick my test console later to verify this and update this post with the result.

 

[Jangmonim]

As far as I know this is expected.*
The software has to react on the (magnetic) sleep switch. Since the Home Menu never loads, there is nothing active that could go to sleep mode.

The magnetic switch should still trigger with a good magnet (please don't use some ridiculously strong magnet) and make ntrboot possible.



_______________
* I will softbrick my test console later to verify this and update this post with the result.

Oh Thanks a lot I’ll try until it can be loaded.

 

[KleinesSinchen]

Confirmed. I got my O3DSXL to a condition where loading native firm will always fail (wrong data in LocalFriendCodeSeed_B). With Luma3DS it boots fine, without I get double black screen and standby doesn't trigger when closing the shell (blue LED stays on same brightness).

I've no idea what else to say or how to further help here. Troubleshooting ntrboot failure is a pain.

I wish you good luck once again.

 

[Jangmonim]

Confirmed. I got my O3DSXL to a condition where loading native firm will always fail (wrong data in LocalFriendCodeSeed_B). With Luma3DS it boots fine, without I get double black screen and standby doesn't trigger when closing the shell (blue LED stays on same brightness).

I've no idea what else to say or how to further help here. Troubleshooting ntrboot failure is a pain.

I wish you good luck once again.

Thanks for your help. I think the magnet is too big or too strong to enter sleep mode. I gotta change smaller one and retry it. Thanks so much.