You're only in 2.1 for a few seconds, so I really find it to be a non-issue.
I didn't say that he shouldn't properly remove it...?
I only said that it's safe with little to no danger.
I don't know about you, but I'm living in 2016...
taking out SD cards on the 3DS has always been completely safe and so has hotswapping USB drives.
Just because I said it's usually safe to pull out a card doesn't mean that it's always safe or that people are crazy for not doing it... don't assume.
The effects of this are rare and miniscule.
Because the console could be writing to the SD Cards when the user doesn't know it? The Home Menu constantly updates and writes extdata and spotpasses/streetpasses could always come unexpectedly.Ugh, no. No. Let me repeat and drill this into you; removing a drive without safely unmounting is never safe. Whether it's Windows, Linux, or a 3DS. Why do you think the HOME menu bitches at you when you pull it? Why do you think it's mandatory in D9?
I'll drop it here, this is pointless and OT now.
Just because I said it's usually safe to pull out a card doesn't mean that it's always safe or that people are crazy for not doing it... don't assume.
The effects of this are rare and miniscule.
Ugh, no. No. Let me repeat and drill this into you; removing a drive without safely unmounting is never safe. Whether it's Windows, Linux, or a 3DS. Why do you think the HOME menu bitches at you when you pull it? Why do you think it's mandatory in D9?
I'll drop it here, this is pointless and OT now.
Because the console could be writing to the SD Cards when the user doesn't know it? The Home Menu constantly updates and writes extdata and spotpasses/streetpasses could always come unexpectedly.
It isn't mandatory in D9, just given the nature of the app, the app itself could break.
Also yeah, it really is not that big of a deal
You might not have called me crazy but you might as well have with your "witty" remark of you living in 2016. Like wow, really man? Way to go bashing on someone who doesn't want to take unnecessary risks.
Yes, you are. You go in Decrypt9 or Hourglass9 and you press a button to suspend the console and dismount the SD card. You're crazy to turn it off. And unplugging a USB like that has not corrupted anything since windows 98.
Nobody knows for sure - the most accepted theory (not that anyone has seriously discussed this since quite a few months) is that of the operating system sending invalid commands to the mcu (which still has a N3DS firmware) and it taking the issue too personallyHavent bricked a n3ds thus far. However,why does this cause a MCU brick,Could someone please explain as easy as possible?
I'm impressed that neither Crystal or Quantumcat have jumped to answer this question. This has been discussed previously a lot, @CeeDee .
It's sort of an MCU Brick. Well, sorta; i prefer to call it "function mismatch"
The reason for the "brick" is caused whenever a bad signal is read/interpreted by the Microprocessor unit on the 3DS.
Old 3DSes and New3DSes have very different chipsets in themselves, and the MCU units also differ on both the way they were programmed when they were produced, and the version of the chip used. Different units have different interpretations for signals and such
Simply put: Firm 2.X doesn't support N3DS' chipset for the MCU unit it was designed (since it's a newer model, it's not contemplated; then again, this is a downgrade, you're not supposed to have access to that firmware with a newer unit anyway); if you manage to send/receive a signal WHENEVER you're in sleep mode (Even receiving notifications, streetpass or spotpass), the system will enter a loop of sending the correspondent LED-signal to the MCU, but the newer model won't "understand" what's sent, return nothing, and repeat this process PERMANENTLY...even if the system is turned off (because it reads the returning LED-signals the moment it's booted up as well, so scratch that one out from your ideas of "unbricking")...until someone gets a way to communicate with the MCU chip directly (way too difficult to get without a lot of specialized tools and knowledge)
I remember some chinese and koreans were trying to do some research job about this to prevent it, but it was last year. And assuming that there isn't any sign of progress of those on any forum, i guess they still haven't got anything.
And for the guys saying that nothing happened to you when you put your N3DSes in sleep mode, YOU WERE LUCKY. Either by accident you didn't have internet open, and streetpass/spotpass activated, but if i were you and were helping another friend to hack their 3DSes, i wouldn't risk it.
Again, as it had been said countless of times, if you REALLY need to suspend your work while in Firmware 2.X, then I would exhort you to rather turn the system off.
(then again, you're almost done; you should go all the way in a simple run if you got that far, but oh well...people has to sleep and such, i guess )
I'm beginning to think this should be put on the FAQ as well...how is it that even when it's been discussed countless of times, there's people that doesn't know about this?
I was actually hoping someone would know, otherwise I only have speculation on this one.I'm impressed that neither Crystal
That is what everyone above has said in some way.Just my opinion, but I think it's because maybe the n3ds has a better wifi chip/whatever streetpass uses, and the 2.1 firmware doesn't have the right code to be able to deal with it, but thats just me.