I mean with "mismatch" to an error type caused by an inexactly memory access or code interpretation, because with new NATIVE_FIRM some internal memory adresses/pointers changed, afaik (I don't know the exactly terms or facts, but approximately it could be on that way).What do you mean by a mismatch? Do you think Nintendo purposely made that happen or was it unintentional?
If you want, check this commit of Luma's github (which error related to new version is fixed through a simple change on the source code):
https://github.com/LumaTeam/Luma3DS/commit/94b5113b17a54d8595a0d2195f06b27bfd73ee79
--------------------- MERGED ---------------------------
Reason is practically the same that above. And about that, @PabloMK7 (one of the developers of BootNTR) has pronounced already:I can't get NTR CFW to work on my 3ds for some reason. When I try to get NTR CFW, it will not finish because it encounters something and can't continue on. I only have Luma3ds.
Looks like the addresses have changed, so more research is needed. Also, with the latest ctrulib updates, bootntr selector is broken in many places, so this update will take longer to release...
I've found the proper addresses for 11.14 and ntr works properly on it. However as I previously mentioned updating bootntr selector will take some time as it needs to be updated to latest ctrulib. If you really need ntr streaming use that feature from the latest CTGP-7 version, as 11.14 support was added in v1.1.20 (including ntr stream).
Last edited by fmkid,