Possibly bricked my 3DS by updating Luma3DS

Discussion in '3DS - Homebrew Development and Emulators' started by szymon170, Jun 8, 2017.

  1. szymon170
    OP

    szymon170 Pr0FessiuNal HelPeR wiTh HaxXX

    Member
    368
    108
    Jan 2, 2016
    Poland
    Where I live
    I've updated Luma3DS with Luma3DS Updater fork from 3ds.guide to stable Luma 8.0. When the updater asked me, I've checked the option to allow copying to CTRNAND, everything went fine and I've rebooted my 3DS. However, when it turns on, it instantly shuts down. It doesn't even stay on for a second. When I turn it on, the blue LED indicating that it's on quickly flashes and then it stops glowing, so basically the 3DS turns off. When I try to hold SELECT on boot nothing happens. Payloads won't load. Now I can't do anything.
    I've got a New 3DS with B9S 1.0 installed. What can I do?

    EDIT: Sorry, I've posted it in a wrong section of the forum. If you're a moderator and you see it, please, remove it.

    The main thread is here now: http://gbatemp.net/threads/possibly-bricked-my-3ds-by-updating-luma3ds.473599/
     
    Last edited by szymon170, Jun 8, 2017
  2. lisreal2401

    lisreal2401 GBAtemp Fan

    Member
    476
    193
    Jun 4, 2013
    United States
    You needed to update to b9s 1.2 before installing luma 8,0. Don't know if you can boot firms from SD or not if you CTRNAND luma since I don't. Fairly sure this is bricked.

    Okay maybe not. Seems like SD firms do work.
     
    Last edited by lisreal2401, Jun 8, 2017
  3. mikey420

    mikey420 GBAtemp Fan

    Member
    410
    123
    Dec 11, 2015
    United States
    try another build?
     
  4. Pyra

    Pyra do we have an official quilava mascot yet?

    Member
    306
    153
    May 7, 2017
    United States
    Ohio, USA
    Invalid "boot.firm". Either downgrade back to Luma 7.1 or follow this:

    this

    Sent from my SM-G360T using Tapatalk
     
    Last edited by Pyra, Jun 8, 2017