sammy 2100 f**ked !!!!!

[mancmw]

k i tried 2 funcards just incase it was a faulty card then i tried an atmega card im goin to try a mosc next i just dnt know how yet ......

[Tesla]

You could try your card in it with his IRD and BK on it, if it does not work then I would say that the BK number you have for the box is incorrect. I think that if the IRD number is incorrect you get an error something about the smart card is not inserted or words to that effect. Do you get the freeview channels or are they all off?

[mancmw]

iv tried my card lol and its the same i get a black screen for the channels u should pay for i get like 1-5 and bbc 3-4 and itv 2-4 and 4+1

[Tesla]

I would think that the bK is wrong then. So what area are you from, what software revision are you on from the engineers menu and what jtag address did you use?

[mancmw]

well when i first did it i used the 3.5 bytes (pure ntl) but then i rechicked last night and box was updated to 3.6 (pure ntl) and used the latest bytes for that and the bk was identical to the other so how could i get the wrong bk using both the latest bytes for the latest software and get same bk it has to be right i would think

[ouzi1212]

Try both of the bk that u got.

[spikebaby]

when you are using toxic put letters in lower case

[mancmw]

Iv only got one bk from both bytes thats why im saying it must be the correct bk and i didnt realise you could use lower case in toxic ill try tht lol cheers for the help going to give all the things you guys said a try soon as get home keep the info coming lol cheers guys

[Ciwan]

Hello again Mancmw

what method are you creating your exteep by ?? are you using Toxic along with Swapbinhex ?? If yes, then I would suggest you try doing it the NagraEdit 4.1 way.

I've created a guide on how this is done (a very simple guide..baby steps) if you want it >> PM me your e-mail and I'll send it to you

Good Luck

[Tesla]

Originally Posted by mancmw

well when i first did it i used the 3.5 bytes (pure ntl) but then i rechicked last night and box was updated to 3.6 (pure ntl) and used the latest bytes for that and the bk was identical to the other so how could i get the wrong bk using both the latest bytes for the latest software and get same bk it has to be right i would think

Yea its very strange this one!!
3.6 pure is 0x00895934
I believe this is the address for pure on 3.6 is this the one you used? what software were you using on the jtag?

3.6 excw is 0x008D6284