He said he had the 2.1.0 CTR transfer files on the sd card. With that old method of downgrading to 2.1.0 to install a9lh, you CAN get a MCU brick by putting a N3DS into sleep mode while on 2.1.0. You can also get an MCU brick by sending invalid LED patterns to the MCU on firmware 8.X or lower. Sorry, but you're wrong....
Nope, both of your statements are wrong, since putting a N3DS on lower firmware in sleep mode, just causes a bug that makes the console unable to ever wake up again caused by some hardware difference and how the sleep mode is being handled by o3ds fw. As said, this can be recovered, and there is no public way to restore the MCU Firmware, therefore it there's no MCU brick because every known brick can be recovered (well except Yellows8's weird one), and tinkering with the MCU's LED registeres also does not brick anything. Yellows8 who has written said code for the LED registers, just had forgotten to charge his console, and his battery died while testing his code, which kind of fried the FW of his console's MCU chip. Yellows8's code works fine on any Firmware, tinkering with the LED's cannot brick anything. Yellows8's battery died thats all, his code works fine.
First I've heard of that, got a source?
No, you made the claim, its your obligation to provide proof. I'm not going to bother yellows8 over a claim someone made on the internet. I also don't have a twitter account and do not intend to make one just for this purpose. If you don't want to, then fine, but I'm also not going to believe that MCU bricks are impossible without proof, as very respected members of the community have already told me otherwise.
Well, on a N3DS, if you did a CTRTransfer to 2.1.0, then, if you closed the 3ds, it would MCU brick.
Yeah then go, downgrade the os to 8. something and mess with the led, if your console's MCU Firmware bricks and you cannot recover it, then show it to me, cause I've never encountered an actual mcu brick except that one that yellows8's empty battery caused
No it doesn't. If the MCU Firmware would be bricked you could not recover the system and would have to send it to Ninty 4 a repair
Right, so because you claim something I don't believe, I should brick my 3ds and show it to you as proof to.... me? Your logic is retarded....
He said there was no otp.bin. I'm guessing that A9LH actually wasn't installed yet by the origional owner, and that they updated when the prompt came up after turning it on.
It will not brick because of tinkering with the led's there's nothing that can happen. N3DS on 2.1 will just "brick" because of the difference of how the os handles the sleep mode. why don't you show me proof of a real mcu brick?
Ok, first of all, MCU bricks are not because of messing with the firmware, it is because of the MCU being fried.
I already sent you a quote from Plailect saying "MCU bricking was fairly common." That's called proof. Now its your turn to DISprove it. Do you seriously not get how this works?
These type of bricks you are calli
umm, I also had talks with Plailect, and what? Do you think everything he says is true? Just go and Ask Yellows8, He is the one who messed with it and accidentaly fried his MCU Firmware, and that then caused the 3DS-LED-Phobia were noone wanted to change anything on the LED's judt downgrade and use MarcuzD's "MCU Bricker" to change the LED's and then, wow nothing is going to happen.
That's far from proof, rather it's appeal to authority - and just because person X wrote about something called "MCU brick" (almost a year ago, too) does not guarantee they were talking about what someone else calls "MCU brick", especially given how underresearched and vague is the item of interest
