Hacking Black screen with boot9strap and Luma3DS 8.1

  • Thread starter Thread starter someguy42
  • Start date Start date
  • Views Views 18,801
  • Replies Replies 18

someguy42

Member
Newcomer
Joined
May 14, 2017
Messages
10
Reaction score
0
Trophies
0
XP
98
Country
United States
So, I might have a brick, but I still have some hope.

I've updated AL9H to boot9strap and Luma3DS 8.1, but after completing the guide, nothing boots. I can't enter chain-loader menu, Luma settings, recovery mode, etc. I checked boot9strap and Luma versions, they're okay. 3ds turns on, but the screen doesn't. What's especially strange is that if I put Godmode9 in the root of SD card as boot.firm, the screen turns on as well, but I only see black screen. It booted GodMode9 once or twice (I hoped to restore NAND), but now it doesn't boot at all.

Anything I can do?
 
Yeah, I've tried everything from this guide.

1. 3ds doesn't boot without SD card (it turns off after a second)
2. Tried booting without a cartridge
3. Tried using another SD card
4. Can't enter recovery mode

Oh, and one more thing: I was getting some ARM9 and ARM11 "data abort" exceptions from Luma. Here's a dump of ARM9 exception, if it's of any help.
 

Attachments

Yeah, I've tried everything from this guide.

1. 3ds doesn't boot without SD card (it turns off after a second)
2. Tried booting without a cartridge
3. Tried using another SD card
4. Can't enter recovery mode

Oh, and one more thing: I was getting some ARM9 and ARM11 "data abort" exceptions from Luma. Here's a dump of ARM9 exception, if it's of any help.
The fact that it's turning off after a second without an SD card is a good sign. This means you don't have the Luma3DS boot.firm on your CTRNAND, but it means B9S is installed and intact. Here's what I would do:
  1. Take a different SD card and format it with SD Formatter.
  2. Put the Luma3DS 8.1 boot.firm onto the new SD card.
  3. Create a /luma/ folder on the root of the SD card.
  4. In the /luma/ folder, create a /payloads/ folder.
  5. Download the latest GodMode9 and put the .firm into the /luma/payloads/ folder.
  6. Attempt to boot the 3DS, which should automatically load the Luma3DS configuration settings.
If it does, what happens next after you hit Start?
 
Last edited by Lacius,
The fact that it's turning off after a second without an SD card is a good sign. This means you don't have the Luma3DS boot.firm on your CTRNAND, but it means B9S is installed and intact. Here's what I would do:
  1. Take a different SD card and format it with SD Formatter.
  2. Put the Luma3DS 8.1 boot.firm onto the new SD card.
  3. Create a /luma/ folder on the root of the SD card.
  4. In the /luma/ folder, create a /payloads/ folder.
  5. Download the latest GodMode9 and put the .firm into the /luma/payloads/ folder.
  6. Attempt to boot the 3DS, which should automatically load the Luma3DS configuration settings.
If it does, what happens next after you hit Start?

Unfortunately, it still doesn't boot settings or GodMode9 (the screen doesn't light up). Btw, putting latest Godmode9 as boot.firm doesn't light screen up as well, only previous version does it (or maybe older, will have to check).

UPD: Yep, 1.2.8 lights the screen (but still black screen), 1.3.0. does nothing, though 3ds doesn't turn off.
 
Last edited by someguy42,
Unfortunately, it still doesn't boot settings or GodMode9 (the screen doesn't light up). Btw, putting latest Godmode9 as boot.firm doesn't light screen up as well, only previous version does it (or maybe older, will have to check).

UPD: Yep, 1.2.8 lights the screen (but still black screen), 1.3.0. does nothing, though 3ds doesn't turn off.
What happens if you use the Luma3DS 7.1 boot.firm on the root of your SD card?
 
What happens if you use the Luma3DS 7.1 boot.firm on the root of your SD card?
Nothing, holding Start or Select does nothing as well. I've tried lots of Luma3DS versions, none of them did anything. As for GodMode9: 1.2.8. lights up the screen, 1.2.7 booted once after several tries.

JFYI: there was no physical damage to 3DS, previously GodMode9 booted consistently, I've tried to restore NAND, but it freezed, after the second or third try I gave up and tried different versions of GodMode9/Luma3DS and now I'm kinda stuck with this situation.
 
Nothing, holding Start or Select does nothing as well. I've tried lots of Luma3DS versions, none of them did anything. As for GodMode9: 1.2.8. lights up the screen, 1.2.7 booted once after several tries.

JFYI: there was no physical damage to 3DS, previously GodMode9 booted consistently, I've tried to restore NAND, but it freezed, after the second or third try I gave up and tried different versions of GodMode9/Luma3DS and now I'm kinda stuck with this situation.
When did the problem start? What were you doing before the problem started?
 
When did the problem start? What were you doing before the problem started?
I previously had AL9H and Luma 7.0, everything worked well. Then I updated to boot9strap using Plailect's guide, everything went as expected, but then I got a variety of errors (crypto fail, tried aeskeydb.bin, then arm9/11 errors, wrong firmware, etc.), then I tried recovering NAND via GodMode9, but it failed (never reached 100%, freezed at 20-30%), then I started trying different Luma/GodMode/boot9strap configurations, but nothing helped and here I am.
 
I previously had AL9H and Luma 7.0, everything worked well. Then I updated to boot9strap using Plailect's guide, everything went as expected, but then I got a variety of errors (crypto fail, tried aeskeydb.bin, then arm9/11 errors, wrong firmware, etc.), then I tried recovering NAND via GodMode9, but it failed (never reached 100%, freezed at 20-30%), then I started trying different Luma/GodMode/boot9strap configurations, but nothing helped and here I am.
First, when did you go through the guide? Second, when exactly did the errors start?
 
Whats your firmware. And try the legacy of luma.
11.3. I tried, got nothing. But I've tried Luma 8.1.1. and at least settings booted. I set "Show NAND or user string in System Settings" and got crypto fail on reboot. Put aeskeydb.bin in boot9strap folder, but then got "CTR firm is invalid or corrupt" and then it stopped booting again.
 
11.3. I tried, got nothing. But I've tried Luma 8.1.1. and at least settings booted. I set "Show NAND or user string in System Settings" and got crypto fail on reboot. Put aeskeydb.bin in boot9strap folder, but then got "CTR firm is invalid or corrupt" and then it stopped booting again.
restor a nand backup
 
I would, but sadly I can't enter GodMode9.
For some reason 3DS stopped booting again with the latest Luma. Seems like something is really broken.
Just to rule it out as an issue, you haven't changed SD card recently have you? And you're using a name brand SD card from a reputable seller? (no eBay or 3rd party Amazon sellers)
The issues restoring NAND and booting payloads could be caused by a bad SD card.
And your 3DS' NAND was probably bricked by the failed restore.
If you can get GodMode9 working again and complete the NAND restore, and put boot.firm in CTRNAND, your 3DS should work again.
Maybe try with another known good SD card, and put only the Luma3DS boot.firm as well as Luma\payloads\GodMode9.firm (redownload both) on the SD and see if you're able to boot into Luma or GodMode9. If Luma doesn't work but GM9 does, put the NAND backup on and try restoring it again.
 
Last edited by The Real Jdbye,

Site & Scene News

Popular threads in this forum