Not sure about 6.X, for 4.X it's 2102
It was mentioned somewhere in this thread: http://3dbrew.org/wiki/FIRM#Variations
For example: FIRM version for 4.0 is 2.33 (0x0221 in hexadecimal).
There's required firmware (kernel) version value stored in every game. 3DS checks this value during boot and if it's higher than your system menu version you'll face black screen error. FW spoof, basically, overwrites this value, but only if original value exceeds the one you entered (if original value is lower comparing to one you entered, it'll be left untouched). There's no best FW spoof version, just go as high as you can. 3DS performs additional configuration based on this value so spoofing to very low version most likely result in non-working CIA.Can someone explain the fw spoof. obviously its in the description but can someone explain what and how does it spoof for example. Does it trick the console into thinking that the needed fw for a particular cia is the spoof version required. How exactly does the spoof work, its not explained clearly anywhere. I thought rxtools and gw enand take care of this problem so cant understand the point of it.
tldr
Exactly what is (fw spoofing) spoofing and to where, and why is it useful?
also whats the best fw spoof version?
There's required firmware (kernel) version value stored in every game. 3DS checks this value during boot and if it's higher than your system menu version you'll face black screen error. FW spoof, basically, overwrites this value, but only if original value exceeds the one you entered (if original value is lower comparing to one you entered, it'll be left untouched). There's no best FW spoof version, just go as high as you can. 3DS performs additional configuration based on this value so spoofing to very low version most likely result in non-working CIA.
noDoes the .cia file need to remain on the SD card after the game has been installed onto the console?