STB model 6E736B20 and ins7E (CAID 09BB)

[dhiweb]

any one have 09BB working oscam?

- Set prio List in your DVB. Api
P:09BB
I:09AA

- Right Boxid and Ins7E

- Compile Osacam with Right Reader Baseyear Yours is 2004

Look Here

Spoiler: Log Part Modified CW KEY

2021/02/15 01:02:01 5441E252 r (reader) Airtel_India [videoguard2] classD3 ins54: Tag55_01 = 8B, CW-overcrypt may not be required
2021/02/15 01:02:01 5441E252 r (reader) Airtel_India [videoguard2] classD3 ins54: CW is crypted, trying to decrypt unique pairing mode 0x8B
2021/02/15 01:02:01 5441E252 r (reader) Airtel_India [videoguard2] crypted CW is: 000000000000000000B02A282F141F75E
2021/02/15 01:02:01 5441E252 r (reader) Airtel_India [videoguard2] k1 for unique pairing mode is not set
2021/02/15 01:02:01 5441E252 r (reader) Airtel_India [videoguard2] cardreader_do_ecm: after csystem->do_ecm rc=0
2021/02/15 01:02:01 5441E252 r (reader) Airtel_India [videoguard2] cardreader_do_ecm: ret rc=0
2021/02/15 01:02:01 5441E252 r (reader) Airtel_India [videoguard2] cardreader_process_ecm: cardreader_do_ecm returned rc=0 (ERROR=0)
2021/02/15 01:02:01 5441E252 r (reader) Airtel_India [videoguard2] Error processing ecm for caid 09BB, provid 000000, srvid 33E2, servicename: 09BB@000000:33E2 unknown
2021/02/15 01:02:01 5441E252 r (reader) Airtel_India [videoguard2] ecm hash: BCCA86D50E01D2E764AC7DB7AE740815 real time: 93 ms
2021/02/15 01:02:01 5356491B c (ecm) 123 (09BB@000000/0497/33E2/62:BCCA86D50E01D2E764AC7DB7AE740815:0F06000000000found: not (96 ms) by Airtel_India
2021/02/15 01:02:01 5356491B c (ecm) cw:
2021/02/15 01:02:01 5356491B c (ecm) 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

When Evrything Looks Like This Here You Can Think Thinking About K1

Did you get the k1 key? or dcw key?

 

[dhiflix]

forget about this....this is airtel caid 09BB red card encrypted type 3des..

 

[sweden1]

yes still not possibel to get key with easy way may be 2023 solve this issue and get 3des easy...

 

[ohmza]

Okay, so this card is 3DES overcrypt. However, you did not config BOXID correctly. That is why the log shows “Card needs pairing/extra data”.

Let’s start from ins7e, you should be able to see your ins7e from the menu as a format like this:

6E736B20AAAAAAAABBBBBBBBCCCCCCCC 02 11 04 N 132 0

Then, you should be able to grab BBBBBBBB from ins7e and adds 80 to the first two digits and then take that as your BOXID.

And lastly your ins7e will be like this:

6E736B20AAAAAAAABBBBBBBBCCCCCCCC00010202030000000000

With all of the above configurations your card should be able to enter the mode so called “8B”. And then you will be stuck with 3DES k1_unique key same as me. ;P