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

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

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

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

Hi andy,

I take it you mean an external toxic image?

John.

andyfuk

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