JTAG for Dummies

[biggeorge]

My current list of tools at my disposal are:
Various dead, alive and half alive smartcards. I have a legitimate subscription.
OLD ADB 8776 box, v3.9 firmware that seemingly fell off a truck somewhere.
Season dragon 2 card
4658x box and serial cables
JTAG interface
Jaycar card programmer
1.04 smart card with OS, never used.
Hammer

I have an apetite to learn here, i'd search the old forum to glean the information I require, but alas the old forum is smeared across the bottom of a hard drive casing.

Can somebody please take the time to explain jtag to me, relative to the 8776 box, and what I can possibly do with this stuff.

I kind of have the basics covered, I modify the box, presumably by inserting a 20 pin header into the board of the 8776, and I know I can use it to access the eeprom in the box.

I am not 100% sure on what modifications I need to do to the box, or even why, and what I can do.

Discuss...

[biggeorge]

anybody?

[Decapper]

Mate ppl's lips are squeezed tighter than a fishes ass at the moment.



Good luck hope it help

[Dave001]

What version is the mainboard?

It's written under ADB on the board, will be something like 05500-001b.

[Dave001]

Here's the circuit diagram and pin out.

[Dave001]

Here's the Jkeys software.

[RHCP]

There are two files, the U4 or bootloader which is specific to each mainboard and written by ADB (not austar), and the U8 which has austars 'operating system' on it. Don't touch the u4.

Don't load the U4 from other mainboards (types) onto yours, as the colour controls are different and you won't see shit!.

Mainboard CPU Flash Chip
05500-001A STi5500BCV-X 29LV160
05500-001B STi5500BCV-X 29LV160
05500-002B STi5500MVB-X 29LV160
05500-002D STi5500MVB-X 39VF160
05500-002E STi5500MVB-X 39VF160 - Not sure?
05500-002G STi5500MVB-X 39VF160 - Can't be downgraded.

The u8 contained an update key which was necessary for austar to perform an over the air upgrade - some of the firmwares may be missing this (to prevent firmware upgrades)...don't know what effect this will have if you try to update the box yourself.

I am not 100% sure on what modifications I need to do to the box, or even why, and what I can do.

I think people are jtag'n their boxes back to 'pre-marriage' firmware's, then updating the boxes (over the air) so they are capable of decoding current austar - the box will then marry their whitey when it's put it.

or

They use the jtag to modify one of the marriage bytes stored on an up-to-date box...when the box reads these marriage bytes, the new checksum wont = the old checksum and an error will be produced, the box will then marry next card put into it.

Also, some people are using certain CS programs to mask the whiteys coco with a DTH coco which allows most of the channels to be selected via the DTH bouquet.

Cheers, RHCP.

[fandtm666]

thanks for the explanation RHCP , by the off chance do you know what the password for the hidden menu that can be accessed as it boots is

[RHCP]

do you know what the password for the hidden menu that can be accessed as it boots is

No, i would love to know what's in there though. I remember a member spent a night trying to brute force it (by hand with the remote) lol

Cheers, RHCP.

[CrYpto]

What version Csclient software is needed for masking the whiteys coco.

[SatGuRu]

Can anyone explain how to Jtag a STB3110 for Intelsat 701?

thanks