I was using emunand, on 7.1 on a 3dsXL
I actually saw this topic before it bricked so i made a note not to go messing around with things in the settings.
It's all very strange, i just followed to usual bootup procedure. but it froze when loading the exploit like it some times does. but this time when i retarted it i got the error!!
good thing i got my nand backup but my 3ds is almost a weekold and im a little nervous about openeing. what should i do guys!!??
Your only alternative is flashing the NAND via hardware mod.
For the record, today I discovered that my 3DS ran out of battery, so turned it on and... everything is normal actually, emuNAND working fine.
Well I can't go against your word, what launcher are you using? 3.3 or 3.2?
I'm sorry but i have to say that from my point of view it's random. Today i booted 3ds three times only to start exploit and to play 3ds rom. It happened on the third (for the day) boot and start of the exploit - the console freeze after "ds profile", i powered of holding power button, and then the blue screen appeared
Launcher - 3.2
So you are saying that you have the same problem as covtops. Are you using Gateway or R4i?
So far, only XL got the BSOD, all of them using emunand (either 6. something because, one of you used e-shop, or 7.1). Is there any reports of someone using a "normal" 3DS, who had the same problem?
covtops, i don't know how to help you, but even if you send it to nintendo, and even if they decide to help you, at some point you, or someone who can do it, have to solder something in your XL to downgrade your nand : /
covtops, i don't know how to help you, but even if you send it to nintendo, and even if they decide to help you, at some point you, or someone who can do it, have to solder something in your XL to downgrade your nand : /
Uh oh, my 3ds is flat ATM, this is the problem with all cards using the exact same software, does seem more common on the clones though...for the sake of not getting fanboy cries I'll just say this must be because the R4i is so much more popular, there is no other possible explanation, but guess time will tell,
hmmm so not doing emunand could be a safe way of preventing this ? I don't know
Maybe the problems would be launchers 3.2 - 3.3 ( 3.1 is a no no too since it causes save corruption , so you would have to fall back to 3.0) since those got released recently and then the problems started to appear
Maybe the problems would be launchers 3.2 - 3.3 ( 3.1 is a no no too since it causes save corruption , so you would have to fall back to 3.0) since those got released recently and then the problems started to appear
Thanks for the feedback.
I'm trying to get all this information together.
First, a Gateway user reported this:
System bricked due to emuNAND overwriting information on the realNAND. After exiting emuNAND, the 3DS couldn't boot again.
R4i users reported:
From the real NAND, accessing DS Profile caused an error/system freeze (as usually happens when the launcher doesn't boot). The 3DS was shut down, then turned on again and couldn't boot again. This process didn't involve emuNAND as the first one.
I'm curious about the R4i issue. I wonder if those 3DS Link users faced exactly the second case. That would be interesting to know since it would be another problem related to the current day as the save issues that happened after the change of the year.
This is really worrying. Could it be that when you go online that Nintendo changes something on systems with the exploit and thus brick it? I enabled internet to buy Phoenix Wright from eshop but hearing these stories I wont turn wireless on untill its clear what causes these bricks.
Well it was a rumor for the longest of times XD. But if they really wanted to do something I'm sure they would just do a full system update automatically or something
I think in the case of the OP, it is pretty obvious what happened
Moral of the story: do not go into "data management" in settings. Data management and emuNAND/sysNAND do not mix well.
For the R4is, it may well be a problem with their launcher, given that it is a hacked gateway launcher; they may have messed it up when they tinkered with it. Time will tell.
Moral of the story: do not go into "data management" in settings. Data management and emuNAND/sysNAND do not mix well.
For the R4is, it may well be a problem with their launcher, given that it is a hacked gateway launcher; they may have messed it up when they tinkered with it. Time will tell.
Nintendo wouldnt brick no 3DS, thats just dumb. what would Nintendo gain in do this? nothing.
i wish Nintendo was bricking 3DS on purpose than, hackers will release they hacks like there is no tomorrow.
And version 3.36545q might be delayed as well, but I'm sure we will all get there in the end in one harmonious happy family
While I drained the battery of the unit I checked the SD card (as suspected, it didn't work).
These were the files that were written to the SD card, if it's of any importance:
E:\Nintendo 3DS\(Gibberish named folder I suspect could be unique to the unit)\(And another folder named like that)\exdata\00000000\00000220\00000000\00000001
E:\Nintendo 3DS\(Gibberish named folder I suspect could be unique to the unit)\(And another folder named like that)\exdata\00000000\00000220\00000000\00000002
E:\Nintendo 3DS\(Gibberish named folder I suspect could be unique to the unit)\(And another folder named like that)\exdata\00000000\00000220\00000000\00000003
All of these files were written to the SD-card when the brick happened.
I'm going to try and reflash the NAND with the original NAND i dumped before installing the exploit tomorrow.
I will keep you updated.
These were the files that were written to the SD card, if it's of any importance:
E:\Nintendo 3DS\(Gibberish named folder I suspect could be unique to the unit)\(And another folder named like that)\exdata\00000000\00000220\00000000\00000001
E:\Nintendo 3DS\(Gibberish named folder I suspect could be unique to the unit)\(And another folder named like that)\exdata\00000000\00000220\00000000\00000002
E:\Nintendo 3DS\(Gibberish named folder I suspect could be unique to the unit)\(And another folder named like that)\exdata\00000000\00000220\00000000\00000003
All of these files were written to the SD-card when the brick happened.
I'm going to try and reflash the NAND with the original NAND i dumped before installing the exploit tomorrow.
I will keep you updated.
