ROM102rev103 - what all to add to get it current?

[cover]

I have been trying to get all the necessary updates on a ROM102rev103 virgin image so it will be current at rev10C with no blocker. I also need to marry it to my IRD.

I've been trying to get this going for a month and my st19 emulation setup works fine with some AIO bins but they have blockers which I don't want with emulation.

So the questions are not about emulation but are about how to get my ROM102 updated with all the current codespace, MECMs and 101/106 keys and not have a blocker on the image.

Here's what I have done.
1)Take virgin Rom102 rev103 and clean it again to rev103 just to make sure.

2)Apply the rev10C update patch using NagraEdit

3)Apply all the recent MECMs (Feb 6, Feb 14, Feb 20) using NagreEdit

4)Update the 101 AND 106 Keys using the Dish 106 Key Changer utility.

5)Apply my RSA keys to marry it to my 3900 IRD using GenDT08 and save it with 'unlocked' selected. (I have no previously married image).

6)Create tiers using MRTierworks and apply them to the image.

7)Add the resultant image as my .cor file on my st19 boot disk.

The result is that I get the 005 nag 'the smart card is not authorized...'. The barker channels work fine. The IRD likes my image as they appear to be married. The 'all sub' guide displays the expected channels matching the tiers I created. My locals remap properly. I waitedfo rthree hours andstill the 005 nag.

I just can't get rid of the 005 nag and can't get video/audio on any channels except the barker channels.

Ihave read all the step-by-step procedures for doing this that I can find, though there is none that details it all.

One thing I should mention is that the Dish106KeyChangerutility initially does not find the 106 keys and adds the 106 keys and updates the 101 keys, though it does not find a 96 key for the 101 (it's blank) when I initialy read in the image's keys. After getting the keys and applying them, if I read in the image's keys again form the updated image, the 96 key for the 101 is still blank although it seemed to write it. I've checked many other images and the 101 keys both 86 and 96 read in just fine. I'm wondering if the sequence of applying the patches and updates is causing some corruption or misplacment of the 101 key 96?

Any ideas on the proper sequence to do these steps or are there different or additional steps that need to be done?

Thanks,
Cover

[Little Kenobe]

does your cor file have a DT08 0A data type on it?
check your data space for a dt08

you might need to remarry bin to ird with DT08 3.3
open your 3900 tsop in dt08
select use ird secondary keys in dt08 .. dont FF old box keys
open your clean rev103 bin in dt08
under command at top click add 0A data type if your bin doesnt already have one
then click TSOP rsa button at bottom
then click CARD rsa button
then go to the CARD PATCH tab and click apply patch .. it will apply the changes to your TSOP flash
and rev103 bin.
click save TSOP
click save CARD
write new TSOP back to 3900 that you just created in DT08
add your tiers then add your 10c update patch with 0106 image to rev103 bin u just created and rename it st19.cor
if the 0106 image is not correct it will not work .. PM me if you need the correct 10c patch with 0106 keys already on it
ready to go

[cover]

does your cor file have a DT08 0A data type on it?
check your data space for a dt08

you might need to remarry bin to ird with DT08 3.3
open your 3900 tsop in dt08
select use ird secondary keys in dt08 .. dont FF old box keys
open your clean rev103 bin in dt08
under command at top click add 0A data type if your bin doesnt already have one
then click TSOP rsa button at bottom
then click CARD rsa button
then go to the CARD PATCH tab and click apply patch .. it will apply the changes to your TSOP flash
and rev103 bin.
click save TSOP
click save CARD
write new TSOP back to 3900 that you just created in DT08
add your tiers then add your 10c update patch with 0106 image to rev103 bin u just created and rename it st19.cor
if the 0106 image is not correct it will not work .. PM me if you need the correct 10c patch with 0106 keys already on it
ready to go

OK, I did all that with my working .cor file that is from an AIO as modified by me with updated keys and marrying the card and IRD using GenDT08 as you suggested. I did one more step in that I saved keys and that is the RSA keys I've been using to marry any new image I've created using the SK (secondary keys) as the author of GenDT08_SK suggests. The image then seems to be liked by the IRD and seems married. But in checking, the only image that has the DT08 data type is the working image that I've been using for my core file. All the other images that I created, that I only applied the RSA keys to, do not have the DT08 data type. But according to the author of GenDT08_SK and the several step-by-step procedures that tell how to add personal numbers to the AIO's public numbers, you only need apply the RSA keys that you saved from the first time you did the marrying, and you don't need to read and rewrite your TSOP to make the AIO work.

I can be easily convinced that the DT08 data type must be on the image as that's the obvious thing that is different and I can not get any of my created images or any of the other AIOs to work by adding only the RSA keys.

Is it certain that the DT08 data type has to be there for it to work? I just hate to rewrite my TSOP unnecessarily as I can't just easily write it like I can with my boot floppy for the .cor file. I have to disconect everything and take it to another room to do the update on the TSOP.

Though I'm sure getting tired of updating and rewriting my .cor file every few hours every time when Dish updates the keys. I wish I knew how to remove the blocker that is on the AIO I'm using so my .cor would roll keys automatically. Or where there's a AIO with no blocker. That would help eliminate all my operator errors in creating my own image from scratch.

I'll have to wait till everyone is asleep in the house to shut down the TV and give it a try. Some night when I can sleep late the next morning ;)


Thanks,
Cover