Just performed a successful DSiware downgrade with hyperbanned 3DS as a source. Source 3DS had both 002-0102 and 022-2812 ban.
I haven't found any informations on that so I decided to mention it here. That said, use this information at your own risk - I take no responsibility if your target console ends up getting banned after performing a system transfer - I'm just saying that was not the case for me. I would also like to know if there are any other files (that are checked by Nintendo servers) that I should compare to make sure they haven't been transferred? If so, which ones?
- I've used this method to bypass 002-0102 ban (regain access to eShop) and unlink my NNID from banned console (changing the console ID, stored at the end of SecureInfo_A AND injecting a blank nnidsave.bin is neccessary on the banned console!) Accessing NNID settings still resulted in 022-2812 error, but it allowed me to use System Transfer again.
- I've purchased Fieldrunners with no NNID linked to the source 3DS and System Transfered it to unbanned, target 3DS without any issues.
- Most importantly, it seems that SecureInfo_A and LocalFriendCodeSeed_B didn't get transferred from the banned, source 3DS - I have used a hex editor to compare these files dumped from source console before the transfer and dumped from target console after the transfer with hex editor, their contents are completely different.
- Target console has A9LH installed now and remains unbanned after the process - no issues with accessing NNID settings, eShop, playing games online.
I haven't found any informations on that so I decided to mention it here. That said, use this information at your own risk - I take no responsibility if your target console ends up getting banned after performing a system transfer - I'm just saying that was not the case for me. I would also like to know if there are any other files (that are checked by Nintendo servers) that I should compare to make sure they haven't been transferred? If so, which ones?
Last edited by Wojton,