Hacking Emunand black screen causes?

[NEO117]

I'm making this topic mainly seeking information for I have already solved my problem.

What happened is that my emunand blackscreened on me for no reason at all. It was working fine this morning and then no matter what I tried it just didn't boot up. I did not install, uninstall or do anything at all with it. It simply died on me because it felt like it.

What could be the cause for this and how would I be able to fix it if it happens again WITHOUT having to format my SD card and redump?

I'm using a N3DS 9.0.0U

 

[lemanuel]

Were you using a N3DS?

 

[NEO117]

Were you using a N3DS?

Yes.

 

[lemanuel]

Yes.

Then you most likely updated emunand without noticing. That's the most obvious reason since it's literally what happens after being updated.
You would only get a black screen if you were also messing with something that could break it, like a poorly created theme or something else that can affect it.

 

[NEO117]

Then you most likely updated emunand without noticing. That's the most obvious reason since it's literally what happens after being updated.
You would only get a black screen if you were also messing with something that could break it, like a poorly created theme or something else that can affect it.

I always have wifi off. It may have been a bad theme or something.

 

[lemanuel]

I always have wifi off. It may have been a bad theme or something.

Yeah. Trying to run themes that aren't build properly can also do it. That has actually happened to me in the past but with a O3DS.

 

[NEO117]

Yeah. Trying to run themes that aren't build properly can also do it. That has actually happened to me in the past but with a O3DS.

The strange thing is that I didn't install anything at all that day. Didn't even use the 3ds. I just turn it on and it was like that. No relatives that would mess with it either.

 

[lemanuel]

The strange thing is that I didn't install anything at all that day. Didn't even use the 3ds. I just turn it on and it was like that. No relatives that would mess with it either.

Well.. it's hard to tell exactly what it is if nothing was done at all before it happened.
It could have been something that you did previously and that only affected it after turning the console back on again but it's only suppositions anyway.