1. Povka

    OP Povka Member
    Newcomer

    Joined:
    Mar 10, 2017
    Messages:
    18
    Country:
    So the story is kinda long but I will try to make it clear.

    I was using my 2ds for about 3 years now. My stock sysNAND is still 9.8 or 9.2 (can't remember. basically the browserhax version :D)
    I was using menuhax with aureinand (or something like that) for about a year until it stopped working, looked online and changed to Luma3ds. Still menuhax. All good.

    After not using my 2ds for couple months, I turned it on today and updated my emuNAND. Tried launching homebrew launcher (failed to update payload).
    I looked online, tried updating Luma3ds. Didn't work, still was 6.6 Luma
    Updater said to switch to boot9strap, followed a tutorial and... bricked my 2ds.
    After installing boot9strap with safeb9sinstaller my 2ds boots into this crash screen (I can also boot into godmode9 (whatever that is, it was in tutorial)).
    Also, I cannot even boot into my sysnand. Holding R doesn't work, and booting without SD card just makes the blue light turn off immediately. Is this fixable or am i totally screwed?

    EDIT: HOLDING L WHEN BOOTING PUTS ME INTO MY emuNAND :O (This actually gives me hope now)
    EDIT2: I can go into my sysNAND (Which is 9.2 btw, by booting with SD card with write-protection locked (the little switch on micro-sd card adapter)). It boots me into my sysnand with error message saying write protection is on, but i can just click ok. So maybe I can actually disable menuhax from here.
     

    Attached Files:

    Last edited by Povka, Feb 16, 2019
  2. Shadowehh

    Shadowehh Also known as Shadd
    Member

    Joined:
    Jan 27, 2016
    Messages:
    301
    Country:
    United States
    At what step exactly did you get this error in? This would be a great help to unbricking your console (or at least your console's system) and possibly successfully upgrade your LumaCFW.

    You might be able to get the backup of your system before you bricked it if you delete your "boot.firm" in the "luma" folder in "SYSNAND CTRNAND" with Godmode9 (just make a backup of that for whatever reason) and rename the "boot.firm.bak" to "boot.firm".
     
    TurdPooCharger and Lacius like this.
  3. Povka

    OP Povka Member
    Newcomer

    Joined:
    Mar 10, 2017
    Messages:
    18
    Country:
    I had this error as soon as I installed boot9strap. However now, things are even worse, now I cannot do anything. When I turn on I just have a black screen that goes forever. I'm currently copying back my sd content from couple tries ago when it was still giving me this error
     
  4. Povka

    OP Povka Member
    Newcomer

    Joined:
    Mar 10, 2017
    Messages:
    18
    Country:
    Okay, I'm in my godmode9 sysnand ctrnand. Where do I look for boot.firm?

    EDIT: If it's supposed to be in top folder then only emuNAND ctrnand has one. I think maybe that's why it doesn't boot without SD card anymore :/
     

    Attached Files:

    Last edited by Povka, Feb 16, 2019
  5. Amapola62

    Amapola62 GBAtemp Advanced Fan
    Member

    Joined:
    Oct 25, 2015
    Messages:
    965
    Country:
    France
    Wait... maybe you're not bricked but getting an error because of Menuhax... have you tried clearing your home menu extdata?

    Clear Home Menu extdata
    1. Power off your device
    2. Insert your SD card into your computer
    3. Navigate to the /Nintendo 3DS/<32-character-id>/<32-character-id>/extdata/00000000/ folder on your SD card
    4. Delete the extdata file corresponding to your region:
      • EUR Region: 00000098
      • JPN Region: 00000082
      • USA Region: 0000008f
      • CHN Region: 000000A1
      • KOR Region: 000000A9
      • TWN Region: 000000B1
    5. Reinsert your SD card into your device
     
    TurdPooCharger likes this.
  6. Povka

    OP Povka Member
    Newcomer

    Joined:
    Mar 10, 2017
    Messages:
    18
    Country:
    Thanks, deleting the folder now boots me into my sysnand. So what is my next objective? I don't know if I am in my real sysnand, or the b9s luma. It says "sys" instead of just numbers so i assume it's not an actual one. Should I follow the guide importing my emunand into this sysnand and update ir if I am on cfw sysnand?

    EDIT: I can still boot into my emunand with L, godmode with start and luma options with select if that matters.
    EDIT2: Rosalina menu works which means I am in custom cfw :)
     

    Attached Files:

    Last edited by Povka, Feb 16, 2019
  7. Amapola62

    Amapola62 GBAtemp Advanced Fan
    Member

    Joined:
    Oct 25, 2015
    Messages:
    965
    Country:
    France
    Well it says sys... so it would seem you are on Luma Bs9 sysnand... try pressing select before booting to see if you get Luma's config screen to be sure you have Luma installed :unsure:
     
  8. Povka

    OP Povka Member
    Newcomer

    Joined:
    Mar 10, 2017
    Messages:
    18
    Country:
    Okay, all fixed. Succesfully booted and imported data from my previous emunand. Thank you :)
     
    TurdPooCharger likes this.
  9. Somari128

    Somari128 Member
    Newcomer

    Joined:
    Oct 28, 2020
    Messages:
    33
    Country:
    United States
    My 2ds had cfw on it it said it had a system update and now it has a blue light no WiFi light and a black screen can someone please help me
     
  10. lone_wolf323

    lone_wolf323 GBAtemp Psycho!
    Member

    Joined:
    May 27, 2011
    Messages:
    3,852
    Country:
    Canada
    Did you update luma to 10.2.1? If not grab that file and put it on sd card root.
     
    KleinesSinchen likes this.
  11. Somari128

    Somari128 Member
    Newcomer

    Joined:
    Oct 28, 2020
    Messages:
    33
    Country:
    United States
    No I mean a 3ds system update because the eshop said it needed a system update to load
     
  12. KleinesSinchen

    KleinesSinchen GBAtemp's Backup Reminder + Fearless Testing Sina
    Member

    Joined:
    Mar 28, 2018
    Messages:
    2,013
    Country:
    Germany
    Did you by any chance disable the ARM11 crash handler (not a good idea)?
    All version 10.x of Luma except for the new v10.2.1 should crash with an ARM11 exception (process pm) on latest firmware 11.14.
    It should not go black screens (except for when ARM11 crash handler is disabled).

    Replace boot.firm with latest version and see if this fixes the problem.
    https://github.com/LumaTeam/Luma3DS/releases/tag/v10.2.1

    Remember to update the failsafe file on the NAND as well → CTRNAND Luma3DS


    Good luck and have fun!
     
    Last edited by KleinesSinchen, Nov 24, 2020
    TurdPooCharger and Somari128 like this.
  13. lone_wolf323

    lone_wolf323 GBAtemp Psycho!
    Member

    Joined:
    May 27, 2011
    Messages:
    3,852
    Country:
    Canada
    Did you complete the latest firmware update?
     
  14. Somari128

    Somari128 Member
    Newcomer

    Joined:
    Oct 28, 2020
    Messages:
    33
    Country:
    United States
    A no I didn’t disable it and b it completed but it went to restart and now I’m here
     
  15. Somari128

    Somari128 Member
    Newcomer

    Joined:
    Oct 28, 2020
    Messages:
    33
    Country:
    United States
    I’m screwed aren’t I
     
  16. KleinesSinchen

    KleinesSinchen GBAtemp's Backup Reminder + Fearless Testing Sina
    Member

    Joined:
    Mar 28, 2018
    Messages:
    2,013
    Country:
    Germany
    Have you already updated Luma3DS? This is the very first thing to try. Only v10.2.1 (and v9.1) will boot on latest official firmware.

    If there is a softbrick from bad update there are troubleshooting methods as well.
     
    TurdPooCharger likes this.
  17. Somari128

    Somari128 Member
    Newcomer

    Joined:
    Oct 28, 2020
    Messages:
    33
    Country:
    United States
    This is my firmware version and I can’t access safe mode
     

    Attached Files:

    KleinesSinchen likes this.
  18. KleinesSinchen

    KleinesSinchen GBAtemp's Backup Reminder + Fearless Testing Sina
    Member

    Joined:
    Mar 28, 2018
    Messages:
    2,013
    Country:
    Germany
    See… you disabled ARM11 crash handler (last checkbox) and still have v10.2 instead of v10.2.1

    Removing (x) Disable Arm11 exception handlers should make your console boot into ARM11 crash instead of black screens and replacing boot.firm with latest version should make everything go back to normal.
     
    TurdPooCharger likes this.
  19. Somari128

    Somari128 Member
    Newcomer

    Joined:
    Oct 28, 2020
    Messages:
    33
    Country:
    United States
    Can you link me to that please
     
  20. KleinesSinchen

    KleinesSinchen GBAtemp's Backup Reminder + Fearless Testing Sina
    Member

    Joined:
    Mar 28, 2018
    Messages:
    2,013
    Country:
    Germany
    TurdPooCharger likes this.
Draft saved Draft deleted
Loading...

Hide similar threads Similar threads with keywords - Bricked,