Yes it is possible to fix this issue on a Gen2. Only difference being is that you have to rewrite all of B0 using the normal write command hf mf wrbl
The only limiting factor which can prevent fixing this issue on a Gen2 would be if the sector bits (control write/read access to sector) are set in a way that restrict modifying S0.
I’m also assuming you are having the same issue as above with a bad BCC0 only.
In order to understand the issue further and be able to try to get some data from the card, we can disable anti-collision which is the feature that give this error.
Steps to disable anti-collision & write good B0 data (no backdoor commands)
- View current anti-collision configuration
hf 14a config
- Disable BCC0 checking
hf 14a config --bcc ignore
- Try to read card data
hf 14a info
2.1 If above command works, read S0 contents
hf mf rdsc -s <Sector number> -k <key|12Hex> 2.1.1 Write good B0 to fix BCC0 issue
hf mf wrbl --blk 0 -k <key|12Hex> -d <data|16hex>`
Example data/good B0: 010203040408040000004A495256494E - Reset anti-collision to defaults
hf 14a config --bcc st
Please try the above and let me know how it goes.