Homebrew Updated to 11.3 with A9LH installed, getting black screen on boot

[DutchyDutch]

I updated to 11.3 with A9LH. I got a black screen when it finished, so I turned off my 3DS by force. Now I can't get it to boot ;( Please help, did I brick by updating?

 

[DutchyDutch]

I can however boot into decrypt9 and Luma.

 

[Infidel]

What version of Luma are you running?

 

[naddel81]

yes, you are bricked

 

[DutchyDutch]

yes, you are bricked

Please tell me you're joking.

What version of Luma are you running?

Luma3DS v6.1.1.

 

[Infidel]

Please tell me you're joking.


Luma3DS v6.1.1.

Update to Luma 6.6 and you should be okay.

 

[Shadowxp13]

Please tell me you're joking.


Luma3DS v6.1.1.

I think you softbricked. Anyway, try the 6.6 release.
If it does not work, you can always restore a nand backup.

 

[naddel81]

Please tell me you're joking.


Luma3DS v6.1.1.

update your luma and try again. don't forget to update CTRNAND, too.

 

[DutchyDutch]

Update to Luma 6.6 and you should be okay.

Just to be sure, all I need to do is download Luma, and put the arm9loaderhax.bin file on my sd card?

 

[naddel81]

and after booting, put it into CTRNAND.

 

[huma_dawii]

Just UPDATE LUMA and youll be fine.

 

[Infidel]

Just to be sure, all I need to do is download Luma, and put the arm9loaderhax.bin file on my sd card?

Yeah that should at least get you booted.

 

[DutchyDutch]

Now that I updated Luma, I can't even get THAT to boot..... I'm holding Select but it just doesn't work.


OK nvm my mistake, anyways @naddel81 with CTRNand do you mean I should enable "Autoboot SysNAND"?

It finally works again. Sorry for the trouble, I just reakly love my 3DS. Mods, you can delete this thread. Thanks everyone

 

[Infidel]

Now that I updated Luma, I can't even get THAT to boot..... I'm holding Select but it just doesn't work.

--------------------- MERGED ---------------------------

OK nvm my mistake, anyways @naddel81 with CTRNand do you mean I should enable "Autoboot SysNAND"?

Yes tick that, show user string in system settings and there is one more. Its the first 2 options then the user string option.

--------------------- MERGED ---------------------------

Its: Autoboot SysNAND
Use SysNAND FIRM if booting with R
Show NAND or user string in system settings.

Also: You should use FBI to copy arm9loaderhax.bin to your CTRNAND. So you will be able to boot your 3ds without a sd card inserted.

 

[redmagejosh]

Now that I updated Luma, I can't even get THAT to boot..... I'm holding Select but it just doesn't work.


OK nvm my mistake, anyways @naddel81 with CTRNand do you mean I should enable "Autoboot SysNAND"?

It finally works again. Sorry for the trouble, I just reakly love my 3DS. Mods, you can delete this thread. Thanks everyone

No, he means that you use FBI to copy the arm9loaderhax.bin to CTRNAND. Check https://3ds.guide/installing-arm9loaderhax - Section VI - Finalizing setup

 

[Somebody Whoisbored]

For the love of god he is not bricked. MAYBE soft-bricked, which is recoverable.

 

[naddel81]

Now that I updated Luma, I can't even get THAT to boot..... I'm holding Select but it just doesn't work.


OK nvm my mistake, anyways @naddel81 with CTRNand do you mean I should enable "Autoboot SysNAND"?

It finally works again. Sorry for the trouble, I just reakly love my 3DS. Mods, you can delete this thread. Thanks everyone

what was the problem and why does it work now? tell us!

 

[Majickhat55]

No he didn't brick. Lumav 6.1.1 doesn't work on 11.3 that's it, plain and simple. Incompatible programs/software caused the problem, using the correct version of said program fixed it. This is common knowledge to those that know how to use google or at the least visit the Github release page and check for issues. I'm not sure if some of you were just being facetious telling OP he bricked but even so, that's in bad taste. If you honestly thought it was a brick, you should probably hang around a bit more and read other threads before giving advice.

 

[naddel81]

No he didn't brick. Lumav 6.1.1 doesn't work on 11.3 that's it, plain and simple. Incompatible programs/software caused the problem, using the correct version of said program fixed it. This is common knowledge to those that know how to use google or at the least visit the Github release page and check for issues. I'm not sure if some of you were just being facetious telling OP he bricked but even so, that's in bad taste. If you honestly thought it was a brick, you should probably hang around a bit more and read other threads before giving advice.

we already know OP is a damn b00n, no need to rub it in even more.

 

[Majickhat55]

My comment wasn't directed at the OP. It was directed at everyone else in this thread giving him bad information. You've missed the point. I'm saying those who tried to help, should have googled before assuming "brick". Noobs helping noobs.... is destined to failure.