Homebrew Bricked system?

[trainboy2019]

no no the dump file, located in \luma\dumps

You could copy the contents to pastebin and post a link

 

[Ghaleon1982]

You could copy the contents to pastebin and post a link

How do you open a .dmp file?

 

[redunka]

That's probably not the case, but have you ever installed something like custom HOME Menu, by any chance?

 

[trainboy2019]

That's probably not the case, but have you ever installed something like custom HOME Menu, by any chance?

He can't even access Sysnand

How do you open a .dmp file?

Have you tried notepad?

 

[Ghaleon1982]

I just put the dumps in a rar

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

Do you mean like if I hold down L it boots into rxTools? If thats the case then yes, if not then no I followed everything in that guide.

 

[trainboy2019]

I just put the dumps in a rar

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

Do you mean like if I hold down L it boots into rxTools? If thats the case then yes, if not then no I followed everything in that guide.

Sorry, this Seems beyond me. You may need to wait for @Plailect for help.

 

[redunka]

He can't even access Sysnand

OP said they've been using rxTools before, they could have installed it back then.
IIRC, rxTools has no region free by default, and there was a way to apply it by installing custom patched HOME Menu.
But since there's no confirmation about this from OP, you can just ignore everything I just said.

 

[Tenshi_Okami]

My suggestion is to try to CTR Transfer

Why? Tbh RxTools was basically a mess of code that actually worked..

 

[Ghaleon1982]

That's probably not the case, but have you ever installed something like custom HOME Menu, by any chance?

OP said they've been using rxTools before, they could have installed it back then.
IIRC, rxTools has no region free by default, and there was a way to apply it by installing custom patched HOME Menu.
But since there's no confirmation about this from OP, you can just ignore everything I just said.

Then no, I've never done that

 

[Ghaleon1982]

I got everything up and running thanks to @Zeta

 

[Master_Goofy]

Can you tell us the trick how you fixed it? I have exactly the same error as shown in the pictures...

 

[Ghaleon1982]

I scaned my mem card for any errors and fixed it, after that problem went away

 

[Majickhat55]

When you hear hoofbeats in the park, think horses not zebras! By that I mean, the solution is most often the simplest explanation.

 

[Master_Goofy]

I fixed it holding select at start. In the Luma3DS v8.0 configuration menu I checked the option "Autoboot EmuNAND". After that the error disappeasred and I could use my 3ds as before...

 

[smoop]

I scaned my mem card for any errors and fixed it, after that problem went away

Can you explain how you scanned your mem card for errors (as in, what/where were the errors)? I have the same issue but Master_Goofy's option didn't work for me. Had menuhax before.

 

[dkire13]

I'm having the same issue. Using O3DS with Luma 8.0 and boot9strap 1.2

Tried to enable Autoboot EmuNAND, and that doesn't work. How exactly did you scan the card to test it? @Ghaleon1982 @Zeta