

This resulted in the fake bricked state which lead me to do this testing in the first place. Lastly I tested the FIRM protection by installing a cartridge update. So signature patches were active while loading Luma v10.0.1. After that I made the safety test for uninstalling CFW → H&S did not show any banner anymore and booted to black screens. However, injecting HB Launcher Wrapper into H&S made HB Launcher appear on Home Menu (it loads to an error message because of missing Rosalina module).
#3ds games version 4.5 software
No Rosalina, no "Sys" before the version number in settings, no trace of unsigned software (main SD:/Nintendo 3DS/ folder incompatible with this old firmware even after removing Home Menu data.) All others come with a higher minimal firmware version.Ĭlick to expand.In fact I had trouble finding any indication that Luma was – in fact – loaded. As far as my tests go, only O3DS(XL) can be affected by this problem. The guide advises to use the latest version of everything so people with devices on low very firmware might run into this problem. There are good reasons for installing B9S on older firmware versions before updating instead of updating first and using *miner: I guess it would have killed Fastboot as there was no indication of a loaded CFW protecting FIRM0/FIRM1.Įdit:See post below a different, more positive result for 1.0Ĭonclusion: Latest Luma not loading Home Menu on 4.5 is a problem – if this can be confirmed – because there might be quite a few devices out there with this version because of Gateway 3DS usage in the past.
#3ds games version 4.5 Patch
I could not get any Luma version to patch the firmware. At first I thought Fastboot 3DS might have been overwritten, but no: All good. Literally normally! No Rosalina, no “Sys” before the version number in System Settings.

The process of constantly flashing different firmware versions and restoring the NAND afterwards is very time consuming so I stopped trying at some point. I tried my best to test more and even older versions from somewhere, but could not get many to work – one would not even install. I totally missed testing the important version 9.2.0-20 (thanks This widely used version is fully working with Luma v10.0.1
#3ds games version 4.5 series
6.0.0-12 is the initial version for O2DS.įor the 4.x series I’m pretty sure I can call this a regression in Luma3DS since the official Wiki states that more or less all Luma functions should work starting with 4.0.0. Luma loads for firmware 1.0 and other very low versions, but it’s hard to see that (no obvious indication of CFW presence). In the earlier version of this post I was wrong about some parts (see spoiler below, NOT corrected the mistakes). Results of the tedious testing with various old firmware versions: As I ran into a “bricked” state (black screens) with firmware 4.5.0-10E when trying to boot the console with latest Luma – while no problems with v9.1. Because of this post in the 3DS NOOB PARADISE I did some tests with old firmware versions and Luma.
