Hacking [HELP] Weird brick after update to 11.0

[Intronaut]

First of all don't get scared about this, my 3ds got bricked before, and I think that is a potential reason for this new problem.

Let's start: two months ago my o3ds xl got bricked after installing a corrupted a9lh build. However, a friend of mine restored my NAND backup by a temporal hardmod.

I've played a lot with my o3ds without major problems. However, today I turned on my 3ds and every icon dissapeared. I couldnt ever turn off the console. I was only able to navigate through the home menu. I tried to restore a nand backup through A9LH, but now sysnand doesnt boot (a9lh boots fine anyway).

I tried to launch safe mode with the last luma commit but it freezes. I've tried to restore a lot of nand backups (of my console, obviously) but they doesnt boot. I tried to put a backup in a emunand and it doesnt boot either.

The only thing the console now can do is to load a9lh payloads.

The last thing I did was update my console to 11.0 and play with my r4.

Can you help me please?

 

[hobbledehoy899]

Nintendo did it, they bricked it.

 

[Intronaut]

Nintendo did it, they bricked it.

I dont think so. I think a part of my hardware is broken and the 3ds, after doing a hardware check, refuses to boot. But i want to be sure.

 

[JCR1]

There are more cases like you, only boots A9LH but sysnand is hard bricked, nobody knows the real causes, "hardware" failure someone claims, you can follow these recommendations to see if can boot emunand at least.


http://gbatemp.net/threads/sysnand-broken-emunand-fine-on-a9lh.422073/


http://gbatemp.net/threads/so-is-my-n3ds-dead.424291/

http://gbatemp.net/threads/q-error-on-boot-followed-by-strange-brick.425916/

 

[Intronaut]

Tempers! I'm glad to say that I unbricked my 3ds. I just use all the remaining battery, and then I turned on my console. I was surprised when it booted.



MODS, please close this thread.

 

[Lumince]

Most people that ive seen with this problem just said that turning it off and letting it sot for a few hours fixes it. They cant explain it and im pretty sure it just sounds like hardware failure but eh. Let it live a little longer i suppose.

 

[MajinCubyan]

Most people that ive seen with this problem just said that turning it off and letting it sot for a few hours fixes it. They cant explain it and im pretty sure it just sounds like hardware failure but eh. Let it live a little longer i suppose.

Very true. Seems to me to be an o3ds thing, cause I have never have had any issues with my a9lh n3ds. My girlfriends had similar issues and I waited a bit and everything just sorta fixed itself.

 

[cots]

Masterbrick!

 

[mokmoki]

damnit, reports like this are getting more common.. i'm thinking of using EmuNand on my A9LH because of these stories. but...

emunand boots like 10-13 seconds
sysnand boots in 8 seconds.

i kinda want the full experience hahahaha =))

 

[JCR1]

save few seconds in the boot some times and then wait hours for black screen, I agree is better emunand for consoles with these problems

 

[Lumince]

damnit, reports like this are getting more common.. i'm thinking of using EmuNand on my A9LH because of these stories. but...

emunand boots like 10-13 seconds
sysnand boots in 8 seconds.

i kinda want the full experience hahahaha =))

save few seconds in the boot some times and then wait hours for black screen, I agree is better emunand for consoles with these problems

Im just wondering if a9lh messes with something on the o3ds's itself and the 3ds doesnt recognize the nand properly? Im not sure why letting it sit solves the issues, but atleast its not a permanent thing. The N3DS seems just fine though, ive never had a failed boot with a9lh on my N3DS. Id just say that if you have a backup before this happened, keep it handy. The devs really should look into this issue and see whats up.