Separate names with a comma.
Discussion in '3DS - Flashcards & Custom Firmwares' started by ShadowWolfHaxX, Dec 14, 2016.
Short answer: downgrade with 4 DSiWare that have been pulled from eShop on 11.0/11.1 without a second 3DS that has CFW.
thi may not be correct, but is my interpretation of information ive read:
from what ive read it is something that "allows one to (slowly) overflow the reference count for a handle object to zero" which results in ARM11 kernel code execution, such as installing legit cias, for example updates (but you can no longer update to a lower firmware thanks to a new 'list' added in 11.0) or accessing a small amount of the nand where dsiware saves are stored thanks to something called AM_ImportTwlBackup. an oversight in the 3ds software grants dsiware access to the nand, so a hacked save should allow some homebrew app to change the consoles native firm to below 11.0, causing the arm9 not to use that 'list' and allow your system to "update" down to 9.2 where the last arm 9 kernel exploit existed.
i got this information from https://www.3dbrew.org/wiki/3DS_System_Flaws#Kernel11, https://gbatemp.net/threads/why-the...simple-explanation-for-the-rest-of-us.441373/, https://3ds.guide/dsiware-downgrade-(save-injection), and some other places.
i probably didn't put the little chunks of information together correctly, so while somewhere in the process the arm11 does access where dsiware is installed (which is in the nand), and AM_ImportTwlBackup has something to do with either the process of downgrading using slowhax on 11.0/11.1, or is at least closely related to one or more parts of the process but may not be the reason something happens, the nand may not be accessing a small amount of the nand where dsiware saves are stored because of AM_ImportTwlBackup.
It's hax, but slower than what we usually use.