Can a Jtag read from 1 receiver be programmed to another?

[freecharlie]

I have a problem! Thanks to any who can help.

I bought a 4900 off Ebay(how many times you heard that?) and did a read and saved the tsop. Got box keys etc... Programmed my MC1 & put it in, I got "please inseart smart card" flashing on the screen every couple of seconds. Even without the MC in, the receiver is giving me flashing error messages. I KNOW the MC is fine, I use it on my other 4900. So I erased the TSOP & tried to reprogram with the read from my OLD 4900. It didn't work of course but the freak-show of messages is gone... How do I go about reprogramming in a different TSOP, if the one I have is corrupted? Is this cloning?

FC

[JT]

Check your build, then go to the tsop bank and find an image that matches your IRD. Use flashedit to open the image and change the box keys and ird info and save the altered image. Then use jkeys to write the new image. Don't forget to erase a few times first.

Cloning is just putting the box keys and ird number off one receiver on another. They don't even have to be the same make and model to 'clone'.

[freecharlie]

Hey thanks JT! I've been waiting for someone with some know-how to respond.

OK, how close does the build have to be? An EXACT match? I've never used flashedit before so I'm usuming I can find it in echostar file section? I am to change the boxkeys/ IRD # of the new image to that of my original IRD? I can't use the new image boxkeys?

Your a big help I'll kee you posted, thanks!

FC

[freecharlie]

Alright found flashedit and a tsop.bin for a 4700/4900. There are several #'s here, but the only ones I need to be concerned with are the CCED #'s, right? OK, moving on...

[JT]

The image you download will almost certainly have the box keys and ird info zero'd out. You can input almost any info you want. May as well clone it to another receiver in the process. Then cards will be interchangeable between the two. Yep, flashedit is in the files section somewhere. I think the current version is 2.0.1a or something to that effect. You want the first three letters of the build to match if you can find it. Some models are more forgiving than others. Usually, if only the first two letters match the image should work fine. Another trick to making this all work is to make a virgin eprom image using the tsop image you plan to write. Flashedit will do this for you. Here is a brief how to use flashedit.

Open flashedit then
1-Select the tsop image by clicking the three dots to the right of the file window
2-click 'open' tab
3-click 'advanced' tab
4-change IRD and box key info
5-check 'fix irc' box so that the cue turns green
6-click 'save as' tab and save adjusted tsop image
7-click 'save as' tab and save virgin eeprom image
8-write virginized eprom then tsop using jkeys

Flashedit is an outstanding little proggy for these purposes. Kudos go out the whome ever gave us this great little tool.

[freecharlie]

On the image I have saved it says: Software Version P149CCEA
Is that CCEA at the end supposed to be the build? I have CCED on the motherboard... I would assume that since I opened up this IRD and can see a sticker that says only: CCED
That that is the Build. Could you confirm this?

FC

[freecharlie]

Well this is interesting as hell! So I assume then that the receiver I have has ALREADY been cloned... By whoever I bought it from off of EBAY. So your telling me that I can clone the 2 4900's to use the same card?? What if only 1st 2 #'s of the build are the same? can it still be done? By what you refer to above I would guess not. -Not that it matters...This receiver is for a friend(for the short time it can be used)

Well hell JT, Thank you! I've had this reciever around for some time & was going to dump it, but maybe I can get it going now... I gotta go, I'll have to finish this later. I'll let you know how it comes out and thanks again :)

FC

[JT]

CCEA=CCED They are the exact same build. The last letter doesn't have to match. 'Cloning' can be done regardless of build or model. All your changing to 'clone' is the box keys and ird number. You can clone a 2700 to a 510 or any combination of models. Current firmware for the 4900 is P2.18, so that P1.49 image is pretty old. Shouldn't really matter much though. It should update once in the stream. If it doesn't, you can erase just sector SA30 using jkeys then restream. This is what's known as the quick ECM repair, but it also forces the receiver to update firmware. You may get away with doing just this instead of writing an entire new tsop.

[barabbas]

Tsop builds always end in "A".
The eeprom build has to match the build sticker on the board.
Don't use flashedit 2.0a.1, it was buggy. Use 2.0a.2.
Always use uppercase letters for the eeprom build, or it will
never update in the stream.

[skinerd]

Tsop builds always end in "A".
The eeprom build has to match the build sticker on the board.No it don't.
Don't use flashedit 2.0a.1, it was buggy. Use 2.0a.2.
Always use uppercase letters for the eeprom build, or it will
never update in the stream.

You can call you eeprom build what ever you like, I always use xxxD, don't matter what the board says. Try it sometime....you'll see. There really is no difference when you make a virgin eeprom, except for the last letter of course. Virgin eeprom does not equal factory eeprom. A flashedit made eeprom file will contain 48 bytes of code at the beginnning and the rest will be all FF. Factory fresh eeproms have other code , mainly a lot of 00, but other stuff too, that's why loading a virgin eeprom is advised.

[barabbas]

A bogus eeprom build or lowercase letters will prevent stream updates.
That's how I keep my 3900 from updating. A true factory fresh eeprom
will kick the receiver to the dishpointing screen on powerup.
Also, an eeprom build from a different model receiver will prevent
stream updates; like a 2700 build on a 3900.
A bogus tsop build alone has no effect on stream updates.

[skinerd]

A bogus eeprom build or lowercase letters will prevent stream updates.
That's how I keep my 3900 from updating. A true factory fresh eeprom
will kick the receiver to the dishpointing screen on powerup.
Also, an eeprom build from a different model receiver will prevent
stream updates; like a 2700 build on a 3900.
A bogus tsop build alone has no effect on stream updates.

I have used FlashEdit created virgin xxxD for eeprom board stickers of xxxC, xxxJ and xxxV, xxx representing the first 3 letters of the tsop build, all CAPS of course. Never a problem.
Even the first 3 letters don't have to match always, that you just have to get a feel for, and/or test by trial and error.
So when you say or read "must match", that is not always the case.

[JT]

Thanks skinerd.