oh and before someone says "but with arm11 kernel exploit we can downgrade withouth this" NO WE CAN'T. 11.0 added a check and if you try to install a title of a lower version it rejects the install
--------------------- MERGED ---------------------------
maybe HE can use it, but i don't think HE is gonna release a kexploit
--------------------- MERGED ---------------------------
by the way, can anyone tell me if luma3ds protects you from sysupdater? if it does, i may be considering downgrading my a9lh'ed 3ds to 10.3 and check if his thingy works.
The way to achieve downgrades on 11.0> is to plaintext attack NATIVE_FIRM, get only NATIVE_FIRM Down to firmware version 2.50 (10.4), then use the normal downgrade methods, since this reenables memchunkhax2.1 IIRC, and allows you to downgrade.
This is the same for HARDMOD downgrades, and normal dsiware systransfers downgrades. just that here you don't need to use a second 3ds for the transfer of the exploited savefile.
--------------------- MERGED ---------------------------
ok, so just an additional check, i get it
The way the check got usually done was that:
Downgrade attempts to install 9.2 native firm, current installed version is 9.4.
9.4 version is > 9.2 version. can't install older title, abort.
Then, it was discovered that if you uninstalled the title in question BEFORE attempting to install an older version of the title, the 3ds had nothing to check the version against and "forgot" it didn't have permissions to install a lower version title. But this meant that if your system crashed or the exploit was unreliable, you would end up with a brick because of incomplete titles in the NAND. (specially if the title it failed to install was NATIVE_FIRM after uninstalling it beforehand)
Since 11.0 you get a HARDCODED list of minimum versions, hence uninstalling the previous version before installing the older one does not work, because even though the title is not present to compare it with, the 3ds compares the older version title with the hardcoded list, and if it's lower than the register, it aborts. This list is handled by the ARM9, and can't be patched out without arm9 access (that defeats the point of downgrading)
I think i should also mention that if you have a9lh you should NOT do this dsiware downgrade, you'll write garbage to firm0/1 and uninstall a9lh, thus rendering your 3ds unusable. The same applies for the usual systransfer dsiware downgrade.