1st. What is an MCU brick?
Two things can happen:
- the MCU is in an invalid state, preventing you from booting
- the MCU_FIRM is overwritten by sending garbage data to the MCU
2nd. It can't even be recovered by a hardmod?
No, doesn't matter what.
1st. What is an MCU brick?
2nd. It can't even be recovered by a hardmod?
The MCU is in a different chip, that's why you can't use a NAND backup to restore it. (afaik, it controls power button, leds, home button...)1st. What is an MCU brick?
2nd. It can't even be recovered by a hardmod?
Sorry, I just love to learn about these sort of things!
Sent from my Browser on a New 3DS XL with A9LH
Brick risk? And what's the difference between RGB_rave and MCUbricker?For people who are interested, I uploaded the sooscode with a compiled example to my Github repo: https://github.com/MarcuzD/MCU_examples
https://github.com/MarcuzD/MCU_examples/raw/master/LED_dim/LED_dim.cia
what's the difference between RGB_rave and MCUbricker?
Oh, OK, it's just strange because the md5 doesn't match.Nothing at all, just moved it to the directory, and renamed it It generates the exact same cia, just with a different filename.
Maybe differences in the SMDH? (Disclaimer: I haven't looked yet)Oh, OK, it's just strange because the md5 doesn't match.
So, you can't send any command to the MCU after brick?
Is it possible to replace MCU with another one, or it's mainboard specific?
Also, what about custom MCU firmware?
1st. What is an MCU brick?
2nd. It can't even be recovered by a hardmod?
Sorry, I just love to learn about these sort of things!
Sent from my Browser on a New 3DS XL with A9LH
What? I'm almost certain this isn't possible with only software instructions.Sometimes the MCU becomes fried and you need a new motherboard.
Do people even know how to do that MCU hardmod?MCU brick, basically confusing the MCU by sending it garbage data (usually when it gets too much data than it can process). It can't be fixed as the MCU is pretty much on par with the bootrom with how soon into boot it is run. Since the MCU firmware is ran before the NAND is even initialized, restoring the NAND won't do a thing.
Usually this can be solved with a reflashing of the MCU firmware, but I think this is more difficult than a normal hardmod.
Sometimes the MCU becomes fried and you need a new motherboard.
There are some, but the information is private.Do people even know how to do that MCU hardmod?
Sent from my Browser on a New 3DS XL with A9LH
I must find one. I need that MCU hardmod. I need to be safe from EVERYTHING. I want to be able to change my led color without worrying about bricking anyway.There are some, but the information is private.
Check the hardmod installer page, and their proof of work.I must find one. I need that MCU hardmod. I need to be safe from EVERYTHING. I want to be able to change my led color without worrying about bricking anyway.
Do you know any people who knows how to do it and will take a request?
Sent from my Browser on a New 3DS XL with A9LH
Yes, I know someone who can do it, but no, they don't do it for other people.Do you know any people who knows how to do it and will take a request?
Oh, well, it's fine! I will just see if I stumble on one.Yes, I know someone who can do it, but no, they don't do it for other people.
I don't think there is anyone on there who does MCU hardmods on there. ;-;Check the hardmod installer page, and their proof of work.
If it's not an MCU mod, then they must have replaced the physical light. Cool.Oh, well, it's fine! I will just see if I stumble on one.
--------------------- MERGED ---------------------------
I don't think there is anyone on there who does MCU hardmods on there. ;-;
Still want that hardmod, but like I said, I will have to stumble on someone, or learn how the motherboard works and do it myself.If it's not an MCU mod, then they must have replaced the physical light. Cool.