3.7 Funcard & Atmega guide on how to fix

[jamesb4]

From reading the numerous threads on updatding funcards and atmega cards to cope with the new 3.7 software there is obvioulsy some problems being encountered and I think it best to compile the information into a guide so that everyone can get their channels back, albeit for the short time that remains before N3 hits us all.

The following guide has been compiled from advice given by many members, but in particular, AndyfUK who has provided plenty of help in the cable section on this subject.

1. Download appropriate software for your area, funcard or atmega.

2. Put your card in your programmer, read card and save external eeprom which may be required if next step does not work. When reading your card the flash will be erased.

3. In the flash, place the new flash hex file you downloaded and write just the flash to your card. You now have your existing card with the new 3.7 hex. Place the card in box and put onto an encrypted channel and in most cases the channel should clear in 2 to 10 minutes.

4. If it still does not work then you need to check that you have a CAM ID in your external eeprom. Using Swapbinhex convert the hex external eeprom file, which you saved in Step 2 into a bin file. To do this just drag your hex file over the Swapbinhex file icon and the bin file will be generated in the same folder as the hex file. Change the file extension from bin to bn11 and then open this file in in Nagraedit 4.1. Ignore the message of incorrect file size and click on the Data Editor tab. If the three CAM ID fields are blank then you need to put in an ID for your area. Starting with 24 for pure ntl, 27 for exC&W and 2C for Telewest. If you have a CAM ID already, just check that it is correct for your area. If you prefer you can create a new external eeprom file using Toxic 7, putting in your IRD, BK and CAM ID, clicking on your area and then saving the file.

Whilst in Nagraedit just check your tier expiry and rights date as some images run out in May 2010. It might be an idea to advance these, just in case there is a delay in the upgrade to N3. Well, we all live in hope of some slippage in the rollout.

Once all done save your Nagraedit file and then change the extension back to bin. If your programmer software does not allow you to use bin files then you will need to convert back to a hex file with Swapbinhex. Place the downloaded flash hex file into flash and the file you have just saved from NagraEdit into external eeprom in programmer application, erase card and then write the card. Normally your programmer will write external eeprom first and then the flash. If not, then manually write the external eeprom first and then the flash. Place the card in box and put onto an encrypted channel and in most cases the channel should clear in 2 to 10 minutes.

5. If still not working, then carry out Step 4 again, but this time put a completely fake and not the correct CAM ID for your area. Something AndyfUK found out worked in certain cases and I am not sure why it works.

6. If card still does not work try a different card from an alternative manufacturer. 4th Generation Atmega cards have not worked where other Atmegas have.

7. If you get a checksum error when writting to the card then convert the downloaded flash hex file into a bin file using Swapbinhex or similar software and then convert back into a hex file. This will correct the checksum error.

I trust your card is now working, but if not, then please post stating what type of card, card manufacturer, what cc area you are in, make and model of box, how you created your external eeprom file. Then it might be possible to determine other steps required to get cards working.

James

 

[andyfuk]

Nice post James,just hope they get it lol:Clap:

To add its worth trying to get an external working eeprom from a working box in your area and changing the details but leaving the cam id.
This has worked for most of the problem boxes.

Andy.

 

[cfw69]

just had to say this is a very helpfull post to all that my be stuck

 

[jaffamuffin]

I just fixed a card with the shanti 3.7 flash. Using an old image of the card and creating a new card did not work. But using the same card and only updating the flash did work.

Strange thing though, the card that worked had cam ids of cc cc cc cc, but the card that didn't work had a 27 etc .... cam. pure ntl. ( read the eeprom and compared ) - is there a way to compare two eeproms to generate a diff that may be useful for others?

 

[cozzy]

hi james,gotta say thanks for your very helpful post,i could not get my mates pace 4000 to work untill i read your advice

 

[mrhotdoguk]

I just fixed a card with the shanti 3.7 flash. Using an old image of the card and creating a new card did not work. But using the same card and only updating the flash did work.

Strange thing though, the card that worked had cam ids of cc cc cc cc, but the card that didn't work had a 27 etc .... cam. pure ntl. ( read the eeprom and compared ) - is there a way to compare two eeproms to generate a diff that may be useful for others?

Guys,

Changed the Cam ID to CCCCCCCC but it didn't make a difference. What I have done as a test was put the old flash in to see if I get a Mute Err but I don't I get a card status of Removed. So I think there is an issue with the flash.

 

[andyfuk]

Guys,

Changed the Cam ID to CCCCCCCC but it didn't make a difference. What I have done as a test was put the old flash in to see if I get a Mute Err but I don't I get a card status of Removed. So I think there is an issue with the flash.

I would try a new toxic image with the cam id starting with AC then anything after that.
This has worked for a few people,

Andy.

 

[mrhotdoguk]

I would try a new toxic image with the cam id starting with AC then anything after that.
This has worked for a few people,

Andy.

Hi andy,

I take it you mean an external toxic image?

John.

 

[andyfuk]

Hi andy,

I take it you mean an external toxic image?

John.

Yes mate make a fresh toxic image with your ird and bk,start cam id AC and anything after that and leave keys blank and select area,
Drag file over swapbinhex,changes file from bin to hex.
Use this as your external eep followed by the flash hex for your region.
There are definately a few issues with cam id,that will be your problem unless you can get a working card and pinch the cam id off that,
Ive found that works most of time.
Also try turning box off and om with card inserted.
Hope that helps

Andy

 

[jamesb4]

Whilst watching England v Wales yesterday afternoon I thought I would test out various types of funcards from various manufacturers to see if this maybe the cause of some failures to get cards working.

I programmed standard funcards and funcard 4's from 4th Generation open platform and Galaxy. The cards were programmed with a Cam ID starting with 24 for Pure ntl, no Cam ID, all C's, starting with 27 and starting with 2C. All external eeprom were finally saved as hex files and were both created using Toxic 7 (NTL area selected) and NagraEdit (NTL image). All cards were programmed with Infinity USB Phoenix and cleared channels within 2 to 10 minutes with exception of the No Cam ID eeprom which always gave "Wrong smartcard inserted" as soon as the card was placed in the box, which was to be expected.

Assumption: it does not matter what Cam ID you have as long as you use one. Also, all types of funcard seem to work regardless of version or manufacturer, although I did not test a funcard 6.

Conclusion: failure to obtain a working card if you have used a Cam ID is not the cause of the problem. Possible cause is a corrupt IRD in your external eeprom file or expiry or rights dates have expired, the latter being less likely.

When I get a chance I will try the same test out on a couple of Atmegas.

James

 

[andyfuk]

Whilst watching England v Wales yesterday afternoon I thought I would test out various types of funcards from various manufacturers to see if this maybe the cause of some failures to get cards working.

I programmed standard funcards and funcard 4's from 4th Generation open platform and Galaxy. The cards were programmed with a Cam ID starting with 24 for Pure ntl, no Cam ID, all C's, starting with 27 and starting with 2C. All external eeprom were finally saved as hex files and were both created using Toxic 7 (NTL area selected) and NagraEdit (NTL image). All cards were programmed with Infinity USB Phoenix and cleared channels within 2 to 10 minutes with exception of the No Cam ID eeprom which always gave "Wrong smartcard inserted" as soon as the card was placed in the box, which was to be expected.

Assumption: it does not matter what Cam ID you have as long as you use one. Also, all types of funcard seem to work regardless of version or manufacturer, although I did not test a funcard 6.

Conclusion: failure to obtain a working card if you have used a Cam ID is not the cause of the problem. Possible cause is a corrupt IRD in your external eeprom file or expiry or rights dates have expired, the latter being less likely.

When I get a chance I will try the same test out on a couple of Atmegas.

James

Hi James,ive done exactly the same thing with rom 11 images and externals made with toxic and have had no problems but the thing is some people ive made up toxic externals with correct cam ids for area like 24 for Pure and they aint worked.
Like you say this could be incorecct ird and bk or human error but we seem to get alot of cases with people who have programmed cards before so dont you think this is strange?
I cant see this all being human error and suspect the update has changed this for some areas and not others.
Nice posts by the way.

Andy.

 

[jaffamuffin]

Actually I had written a load of rubbish there - it was a 24... cam not a 27 one.

Closer inspection reveals that card which did not work had 2 tiers defined. The other card had one tier. Modify is 00 00, on the non working card its 1c21. Dates on both are fine.

 

[benny59]

I just fixed a card with the shanti 3.7 flash. Using an old image of the card and creating a new card did not work. But using the same card and only updating the flash did work.

Strange thing though, the card that worked had cam ids of cc cc cc cc, but the card that didn't work had a 27 etc .... cam. pure ntl. ( read the eeprom and compared ) - is there a way to compare two eeproms to generate a diff that may be useful for others?

looks to me the old image you used for a new card was diffrent from the image that you only updated the flash on...otherwise you wouldnt have diffrent camids

the image that didn't work will have something wrong other than the camid....could be anything/ dates/wrong tiers/ etc etc etc

camid wont stop a card working if you alter it to something other than the original for the box and your image details are upto scratch

 

[jamesb4]

I will create some multi-tier images and see if these fail. Best to use a single tier, which Toxic produces.

If anyone has a Pure single tier image which uses a Cam ID and it still does not work then please PM it and I will have a play with it to see why it fails.

James

 

[Dazza]

I've got three legit boxes here, currently unused, and not been hooked up at all for the last couple of months.

What would I need to make use of these, with minimal outlay?

 

[rimdogg]

Hi guys

Jamesb4 and Andyfuk, both of you great posts. But im stuck

I have been following James's instructions and have come to point where im not sure what to do.

I have a Pace ntl box
I am in a ex-c&w area.
I have a atmega 163 card.

I do not have an orginal card that i can read and get the cam id from.

So as you may have guessed, my box is down and I am trying to get it back up and running. i am only getting FTA channes, other channels are greyed out and a message appear talking about wrong smart card

I have flashed my card with the new atmega 3.7 fix download from chatterbox tool bar.

I have tried using nargra and when i did that my cam id was blank so I gave it a new cam id which was 27 CC CC CC. wrote it back to the eeprom with the new flash file per james instructions and no luck.

Tried again this time giving it a completely fake Cam id 24 CC CC CC but no luck.

Am i doing something wrong. Will i have to use toxic7.
just been looking at how to use toxic 7 and got a not confused.
you have to launch the app, give it a cam id - is this a fake one.
then you have to give it IRD AND BK. where do i find these as i have not got an orginal card to copy from.

one of the steps say to write the saved hex file in exteep. this i got.
after the it says you must write 'toxi7b' file in flash (this must be correct for your area. here i am lost, where do i get this toxic7b file from as the one i created using toxic7 was written to exteep.

So firstly going back to james instuction, i have done something wrong. maybe the way i editing it. One thing to mention, i am using Narga 4.0 Not 4.1. Does that matter.

Secondly, if am not doin something wrong then do i need to use toxic 7 and what about the toxic7b file. (do i no longer need to use the atmega fix 3.7 downloaded from bigmaq)

Lookign forward to your advice

 

[andyfuk]

Hi guys

Jamesb4 and Andyfuk, both of you great posts. But im stuck

I have been following James's instructions and have come to point where im not sure what to do.

I have a Pace ntl box
I am in a ex-c&w area.
I have a atmega 163 card.

I do not have an orginal card that i can read and get the cam id from.

So as you may have guessed, my box is down and I am trying to get it back up and running. i am only getting FTA channes, other channels are greyed out and a message appear talking about wrong smart card

I have flashed my card with the new atmega 3.7 fix download from chatterbox tool bar.

I have tried using nargra and when i did that my cam id was blank so I gave it a new cam id which was 27 CC CC CC. wrote it back to the eeprom with the new flash file per james instructions and no luck.

Tried again this time giving it a completely fake Cam id 24 CC CC CC but no luck.

Am i doing something wrong. Will i have to use toxic7.
just been looking at how to use toxic 7 and got a not confused.
you have to launch the app, give it a cam id - is this a fake one.
then you have to give it IRD AND BK. where do i find these as i have not got an orginal card to copy from.

one of the steps say to write the saved hex file in exteep. this i got.
after the it says you must write 'toxi7b' file in flash (this must be correct for your area. here i am lost, where do i get this toxic7b file from as the one i created using toxic7 was written to exteep.

So firstly going back to james instuction, i have done something wrong. maybe the way i editing it. One thing to mention, i am using Narga 4.0 Not 4.1. Does that matter.

Secondly, if am not doin something wrong then do i need to use toxic 7 and what about the toxic7b file. (do i no longer need to use the atmega fix 3.7 downloaded from bigmaq)

Lookign forward to your advice

Get a working version of Toxic to make up your external eeprom.
Open Toxic and put in your ird forwards and boxkey in forwards.
Dont think it matters to much if ird is forward or backwards but forwards is easier.
Now put in a cam id,ive tried loads and all seem to work but if your ex C/W start it with 27 and any number 1 to 9 or letter A to F.
Leave the keys empty and save the image to your area ex C/W.
This is your exernal eeprom but its a bin file and we need it to be a hex file.
Drag the file over Swapbinhex,this changes the file from Bin to Hex.
This is now your new external eeprom.
Load his into your external eeprom and the Atmega Redneck8b flash hex into flash memory.
Only write the external Toxic image on its own first.
Follow this by only writing the Redneck8b hex flash file in flash memory.
Thats basically it.
There are a couple of Atmega 3.7 flash fixes out there,Redneck 8b C/w is one of them.

Only need Nagra Edit if you're using a Rom 11 bin image as external eeprom.
Only using Nagra Edit to put details in like ird and boxkey and save to .Bin.

Andy.

Ive read over your post again.You wont get anything without your ird and boxkey numbers.
It doesnt matter that much about the cam id.
The question is do you have the ird and bk??

 

[jamesb4]

@rimdogg

Reading your post I think Andy hit the nail on the head. It appears you do not have the BK for your box. Depending on what model of box you have will dictate how you can obtain the BK. If it is one of the later models and you do not have an original paired card then you may be out of luck. Also if you have to purchase additional equipment in order to get the BK, then it maybe a waste of money considering the few weeks that the cable scene has left.

James

 

[rimdogg]

Andyfuk and jamesb4u. A big massive THANK YOU to both of you.
I am back up running.

Last night I read my card and saved a copy of my eeprom and saved it.
After ready your guys recent post, I opened my saved eeprom as Rom 11 in Narga edit 4.0
The hit the IRD INFO tab
There i noted down my boxkey and IRD.

Then followed Andyfuk's instructions on using toxic and creating a new eeprom.

Thanks a ton guys. you guys are the man... or men shall i say....

 

[andyfuk]

Glad you got it sorted,its not that hard as long as you follow a guide.
Hope this aint the last we see of you rimdogg.
Theres alot more than just cable in this forum.
Enjoy.

Andy.