P
It works on n3ds, it won't brick unless you are stupidly unlucky, but a9lh won't save you from an mcu brick anyways.This works on n3ds, correct? Heard there were bricks and I dont have a9lh on my n3ds :/
It works on n3ds, it won't brick unless you are stupidly unlucky, but a9lh won't save you from an mcu brick anyways.
What?Actually, it can as long as you have NoScreenInit A9LH.
Actually, it can as long as you have NoScreenInit A9LH.
Source?
--------------------- MERGED ---------------------------
What?
It isn't possible is what I was getting at. I think they are talking about something else though...I don't think that's possible. AFAIK the MCU is entirely separate from the NAND. So I don't see how a9lh could save you from anything in the event of a brick.
Even if we could run code. Do we even know how to unbrick the MCU anyways? Would we need a backup?
It isn't possible is what I was getting at. I think they are talking about something else though...
It is indeed possible to recover from an MCU bricked unit. But you have to be using a Kernel9LoaderHax stage1/2 combo that doesn't screen init. (old original K9LHax doesn't screen init). You'd have to get a payload that can unbrick. There was only one person known to have bricked playing with LEDs and that's the guy who originally wrote the example code for playing with LEDs. Maybe he was unlucky but it hasn't happened to anyone sense. Unless bricks start coming out of the woodwork from this, there isn't even a payload to unbrick for those lucky enough to have nonscreen init K9LHax. Not yet anyways.
It is a qr code for freeshopHas anyone been able to install it via the QR code by the way?
I may be wrong but I'm pretty sure there's a no-screen-init version of AW's A9LH fork, so if MCU backup/restore does become a thing then people could potentially switch to that. Also in the most recent commit for that fork, it was changed so screen-init is dependant on the name of your A9LH payload (appending _si to the bin's name will screen init, otherwise it won't) which is always nice.It is indeed possible to recover from an MCU bricked unit. But you have to be using a Kernel9LoaderHax stage1/2 combo that doesn't screen init. (old original K9LHax doesn't screen init). You'd have to get a payload that can unbrick. There was only one person known to have bricked playing with LEDs and that's the guy who originally wrote the example code for this that was on pastebin. Maybe he was unlucky but it hasn't happened to anyone sense. Unless bricks start coming out of the woodwork from this, there isn't even a payload to unbrick for those lucky enough to have nonscreen init K9LHax. Not yet anyways.
You mean NotifyMii?Now all we need is areal brickercia which lets you setup custom notifications...
Doesn't the power button and led also depend on MCU? If that's true you wouldn't that make you unable to power on the console?Alright, found them:
Basically, the MCU has no involvement in early boot normally. With ScreenInit A9LH the MCU has involvement in stage2 where it turns on the screen. However, with non-screeninit A9LH it never talks to the MCU before booting the payload at arm9loaderhax.bin. In theory, this would let you restore your MCU firmware back to before it was bricked if you had a backup/obtained it from somewhere (the MCU firmware is the same across all consoles of the same model I believe). Therefore, you'd be able to recover from an MCU brick with Non ScreenInit A9LH.
Doesn't the power button and led also depend on MCU? If that's true you wouldn't be able to power on the console?
Here is the adapted ntr version of the code: (Call Rainbowize(1) to enable led and Rainbowize (0) to disable) Most of the modifications are made by MarcusD and Nanquitas, so credits to them