Cept the op already specified.this would help greatly over all the you will brick if you do this posts.
They had finished a9lh installation and when it rebooted it wasn't working.
Can't possibly be more specific.
Cept the op already specified.this would help greatly over all the you will brick if you do this posts.
Nope, you're right. That one's on me.Cept the op already specified.
They had finished a9lh installation and when it rebooted it wasn't working.
Can't possibly be more specific.
i read, "luma didnt load" from the op a couple pages back, so i wasnt sure if he actually got a chance to finish.
Ok, 2.1.0, just finished installing arm9 through my browser, shutdown, and after that, nothing.
I can assure you the .bin is in my root.
I'm not going to read all 4 pages.
Anyhow, from this last page I see you bricked after installing a9lh, now was this done from 2.1 or what it done for a 11.xx state and a otpless method?
I already quoted this on this last page.Ok, 2.1.0, just finished installing arm9 through my browser, shutdown, and after that, nothing.
I can assure you the .bin is in my root.
If they followed the Guide, it's unlikely that this is a widespread issue.Seems to me like it was a bad a9lh install.
Which raises concerns, what caused it, how many others have been bricked due to this?
Nope. That would be a UNRECOVERABLE mcu brick.If you have an N3DS and put it into sleep mode while it was in 2.1.0, it's a guaranteed brick. If you did that, that would be the case. As stated a few posts back, you can STILL recover it with a hard mod. I've heard putting it into sleep mode during any NAND writing could also brick it.
N3DS 2.1.0 sleep mode bricks are believed to be caused by invalid Spotpass data.Nope. That would be a UNRECOVERABLE mcu brick.
Taken from 3ds.guide.I don't know where you got this information, but it's wrong. N3DS 2.1.0 sleep mode bricks can be recovered, and they are believed to be caused by invalid Spotpass data.
Most aren't following "the guide" but a YouTube video. Seems like every single one I helped that had issues used the video.If they followed the Guide, it's unlikely that this is a widespread issue.
This seems a lot more like human error and I feel like some details are being left out. If the OP followed the guide, it's highly unlikely that they were bricked because of the Guide.
I stand corrected. I'm not certain that the MCU is implicated, given that sleep mode bricked consoles get an "An error has occurred." screen, I believe.Taken from 3ds.guide.
Do you have a nand backup?I've given all I know about the problem. Nothing is being hidden.
According to this thread, you get an "An error has occurred." screen.And how would a sleep brick look like, would it have a blue screen (like normal bricks?) or would it have no screen?
C'mon, tell us the truth.I've given all I know about the problem. Nothing is being hidden.
Probably a long shot, but I briefly had this problem on one of mine. I simply powered down and ejected/reinserted the SD card. I believe it just wasn't making full contact.I'll send a picture of how my 3DS looks at the moment.
Later.
Definitely didn't sleep brick it then.