Yes, the card is in the same mode 88 as the thread-starters.
My card isn’t recognized by oscam. However, I have another T3TV card that isn’t recognized by oscam as well but there is crypted CW in the oscam log when that card was read by oscam (Mode 8B).
Both T3TV and T3VV cards are the same CAID.
Edit:
I can confirm that this is a problem with the oscam alone as I logged the traffic between card and official STB and put the ins7e and boxid from the log to the oscam.server, then the problem still exists. I even went further by adjusting ins4C and ins40 to match the log from official STB but the problem still there.
Edit2:
I have the solution to this problem. It is all about the one emm, which has the length of 25 in hex, that was sent to the card right after where ins7e was sent.
In order to obtain this EMM, you need Acute TravelBus logic analyzer to log the traffic between smart card and official STB. And then modify reader-videoguard2.c in the oscam source code to have oscam send that EMM right after where the ins7e was sent. You only need to do this once. Based on my observation, this emm has never changed for a year.