Hacking 3DS will not turn on after updating luma?

kevinshorts · Jun 21, 2017

I recently updated to boot9strap from a9lh, and everything was working fine... until I chose to update luma through the lumaupdater app. Although it said "update successful", when I tried rebooting my 3DS, it would not turn on. As of now, when I press the power button, it turns on for about 1 second and immediately turns off (black screen, no speaker popping). I've tried to boot into safe mode, removing the SD card, taking out the battery, etc. but nothing works. What should I do? (I'm a noob so try to be simple with your answers pls)

KunoichiZ · Jun 21, 2017

How recently did you update from a9lh to b9s?

Deleted member 414991 · Jun 21, 2017

kevinshorts said:
I recently updated to boot9strap from a9lh, and everything was working fine... until I chose to update luma through the lumaupdater app. Although it said "update successful", when I tried rebooting my 3DS, it would not turn on. As of now, when I press the power button, it turns on for about 1 second and immediately turns off (black screen, no speaker popping). I've tried to boot into safe mode, removing the SD card, taking out the battery, etc. but nothing works. What should I do? (I'm a noob so try to be simple with your answers pls)

Delete boot.firm from your sd card and remove the .bak from boot.firm.bak.

reminon · Jun 21, 2017

kevinshorts said:
I recently updated to boot9strap from a9lh, and everything was working fine... until I chose to update luma through the lumaupdater app. Although it said "update successful", when I tried rebooting my 3DS, it would not turn on. As of now, when I press the power button, it turns on for about 1 second and immediately turns off (black screen, no speaker popping). I've tried to boot into safe mode, removing the SD card, taking out the battery, etc. but nothing works. What should I do? (I'm a noob so try to be simple with your answers pls)

Yeah. If you are on b9s 1.2, delete the current install, download, and install a fresh copy of Luma 8.

kevinshorts · Jun 21, 2017

KunoichiZ said:
How recently did you update from a9lh to b9s?

Around 2 weeks ago?

-G- · Jun 21, 2017

kevinshorts said:
Around 2 weeks ago?

Update B9S BEFORE you update luma.

EDIT: Use this guide: https://3ds.guide/updating-b9s

kevinshorts · Jun 21, 2017

I was able to get my 3DS working again! Can't thank you guys enough!

MZ-4 · Jun 21, 2017

Can you explain more detailed what you did to "unbrick"?
A friend's New3DS shows the same symptoms after updating B9S.
Yet I do not know exactly, what she did. But the device shows blue LED for a second then switches off again.
...like under A9LH when arm9loaderhax.bin was missing or the SD was not inserted (early A9LH, when there was no copy of arm9loaderhax.bin in CTRNAND).

reminon · Jun 21, 2017

MZ-4 said:
Can you explain more detailed what you did to "unbrick"?
A friend's New3DS shows the same symptoms after updating B9S.
Yet I do not know exactly, what she did. But the device shows blue LED for a second then switches off again.
...like under A9LH when arm9loaderhax.bin was missing or the SD was not inserted (early A9LH, when there was no copy of arm9loaderhax.bin in CTRNAND).

What version of b9s and Luma does she have? It's not really a brick per se, it's just looking for necessary files. Luma 8 requires b9s 1.2.

keyra · Jun 21, 2017

is it me or we have like 30 messages like this everyday. did the search button disappear?

MZ-4 · Jun 21, 2017

reminon said:
What version of b9s and Luma does she have? It's not really a brick per se, it's just looking for necessary files. Luma 8 requires b9s 1.2.

She worked the "A9LH to B9S" and after deleting arm9loaderhax.bin from CTRNAND and SD and rebooting, the problem came up.
My first thought was that the console is still under A9LH but copying a new arm9loaderhax.bin to SD didn't work.
Of course it's no real brick, but it behaves as such.

I will receive the console in a couple of days so I can have a look myself and will probably install a hardmod in the process (recent FW backups are available).
As I understand, it might simply be a non compatible combination of versions of boot.firm and Luma.
I thought of such a problem but it's hard to explain it to a not-so-techy person.
And it's a pity, Luma cannot print a text message giving the slightest hint of what is wrong...

reminon · Jun 21, 2017

MZ-4 said:
She worked the "A9LH to B9S" and after deleting arm9loaderhax.bin from CTRNAND and SD and rebooting, the problem came up.
My first thought was that the console is still under A9LH but copying a new arm9loaderhax.bin to SD didn't work.
Of course it's no real brick, but it behaves as such.

I will receive the console in a couple of days so I can have a look myself and will probably install a hardmod in the process (recent FW backups are available).
As I understand, it might simply be a non compatible combination of versions of boot.firm and Luma.
I thought of such a problem but it's hard to explain it to a not-so-techy person.
And it's a pity, Luma cannot print a text message giving the slightest hint of what is wrong...

I'm 99% sure that a hardmod will not be necessary. It really sounds like a mix/match of versions. Everything is relatively safe these days, compared to the days of old. I wish you luck on the repair.

Quantumcat · Jun 21, 2017

MZ-4 said:
She worked the "A9LH to B9S" and after deleting arm9loaderhax.bin from CTRNAND and SD and rebooting, the problem came up.
My first thought was that the console is still under A9LH but copying a new arm9loaderhax.bin to SD didn't work.
Of course it's no real brick, but it behaves as such.

I will receive the console in a couple of days so I can have a look myself and will probably install a hardmod in the process (recent FW backups are available).
As I understand, it might simply be a non compatible combination of versions of boot.firm and Luma.
I thought of such a problem but it's hard to explain it to a not-so-techy person.
And it's a pity, Luma cannot print a text message giving the slightest hint of what is wrong...

Try putting boot.firm from Luma 7.1 or 8.0 on the SD card. One of these should get it to boot up.

MZ-4 · Jun 24, 2017

It was a mixture of Luma being on 7.1 and the boot.firm 8.0.
I put the 7.1-boot.firm on SD-root and the console came up!

Thanks Quantumcat for the hint!
Updated now to 8.0 with Rosalina allowing HB from unsuspicious Apps and all is fine now.

I think, Luma 8.0 already shows an error message on incompatible boot.firm ("Unsupported launcher (argc = 0)") but the 7.1 does not, right?

godreborn · Jun 24, 2017

MZ-4 said:
It was a mixture of Luma being on 7.1 and the boot.firm 8.0.
I put the 7.1-boot.firm on SD-root and the console came up! Thanks Quantumcat for the hint!
Updated now to 8.0 with Rosalina allowing HB from unsuspicious Apps and all is fine now.

I think, Luma 8.0 already shows an error message on incompatible boot.firm ("Unsupported launcher (argc = 0)") but the 7.1 does not, right?

I think that error occurs if u update b9s before updating luma. only use luma 8.0 if u've updated.

Hacking 3DS will not turn on after updating luma?

Member

Well-Known Member

awagga

Well-Known Member

Member

Well-Known Member

Member

Active Member

Well-Known Member

Spoderman self proclamed fan

Active Member

Well-Known Member

Dead and alive

Active Member

Welcome to the Machine

Similar threads

Popular threads in this forum