020 on 501 -- Stumped!

[r0ckf0rd]

Greetings All!

I am a bit stumped.. I picked up an Enigma to play with & cannot get the thing to work in a 501 (DCEA) I have laying around.

Here is what I have done so far:

1. Programed the Enigma with the STD Rom with the keys changed
2. Flashed the 501 back to the P063 DCEA Virgin Bin, with necessary IRD & Box Key changes.
3. Re-programed 501 and saw Enigma marry to the unit (Oddly enough, at P063 I was able to get the preview channel).
4. Erased SA54 per this thread (http://www.dssftp.com/forum/showthread.php?t=69268)
5. Plugged unit into stream and it took an update to P365 within 20 minutes.
6. Powered unit back up, did a reset to factory defaults & ran 2 switch tests.
7. Put Enigma back in & unit loads up, goes to a black screen for 30 seconds (I can see a "Please Wait for Hard Drive to Spin up" message occasionally) then the unit goes to a 020 error.

Checked the ROM and verified that the proper box keys are set properly.

I also pulled out my old Rom10 with the public bin & the 10 to 102 mod and get the same 020 error when the unit powers up.

When I pulled the 501 out of storage (hasnt been used in ages) I put the Enigma in just to try it as-is and the deivce would boot, but never get past step 1 in the Acquiring SAT signal stage. If I put my rom10 to 102 in, it would finish and take me to the preview channel...

I am stumped on this one.. The one thing worth noting is that with my Rom10 to 102 public card, the receiver shows a card number of S04-XXXX-XXXXX-XX while the enigma shows a card # of S00-0000-0000-00 (All 0's).

I am thinking its a bad bin or the way the bin is getting loaded to the Enigma that is causing the 020 error???

I am temped to put a fresh, 10 to 102 bin on my 10, marry the device, then program the EG with the same bin & see what happens...

Any help would be greatly appreciated!

[mopar611]

Shit, I forgot what 020 nag was...LOL

Its been awhile..

Mopar

[mopar611]

Its either your BKs or your Ird#..

That reply of S#00000000 seems to be your problem..

I also see you did not say anything about erasing your SKs on
the recevier.. You will need to do that after the recevier updates
or you will get 005.

So I think you have the right idea.. Probably has something to do
with the flash to the card..


Mopar

[r0ckf0rd]

I cleared the SK's when I wrote to the IRD, but didnt double check after the update.

I just re-flashed and am in the process of having the update come back down. Once its down I will re-check the SK's and see what they report back.

Thanks!

[r0ckf0rd]

SK's are good...

Loaded EnigmaEDIT 3.3a and receiver loaded right up --- To preview channels only, everything else is red. If I load 3.4, I get a 020 error. if I try 2.5, it times out... Its an enigma that this thing actually works on some receivers...................................

[mopar611]

Red means your tiers are expired..

Between that and your S000000, I believe you have something wrong
with your card image..

Mopar

[r0ckf0rd]

It def seems to be the bin... I dug out my battle-scarred 301.13, wiped the mexico FTA hack off of it and re-loaded the pub mod tsop. Programmed the enigma for 301.13 and got the same thing.. What the@#$$! I am using the supplied bin.

I created a custom bin using DT Tierworks and can get it to load on both, but get an activation error. Does anyone have a bin I could test out? Tried a few virgin bins that I added tiers to, but no go.

Thanks!

[r0ckf0rd]

FYI,

The beast is working.. I went back to 3.3B and tried a custom bin & all is finally good!

Thanks for the help!

[kelowna_pitboy]

what are SK's that you keep saying to clear in the ird?

[ARM]

SK=SessionKeys (or SecondaryKeys)
-only on SK IRDs.
ie 301-013, 510 etc.
For No RSA,
see "moved bootstrap" in Flashedit.

[kelowna_pitboy]

i always get that moved bootstrap on the flash edit but i always ignore it and it never has meant anyting in testing to me until now. mine is a 501 and dont know if that can cause 020 with enigma. i am trying a new 301010 right now just to make sure it is not the 2 cards i have are the problem. would like to know more about this seesion key stuff though if it pertains to a 501 or my unused 301-013' in the closet.

kb