3100 No Power after flashing TSOP few times

[texdss]

I was planing to convert my BEV 3100-10 With Build(EAFD) to Dish, did a junk yard jumper then after few blinks this system did not come back!! I downloaded Rev. 433 U22 build EAFA and U23, used Wall 2.0 and manged to bring the unit to blink but kept getting yyyy for fotware and model ID, created virgin EEPROM and applied to it, whenever left it on Data stream to get it updated after 5 Min light stays on then goes off and never comes back again until I use Wall to reprogram Flash 1 and 2 U22 and U23 again. samething over and over. i have tested few TSOP from this site, 301 (p212 and p213) & 3100 (e430 & E433) did not make any different.
Now it got worse!! anytime trying to flash the TSOP after 25% of flashing U23 times out at address 1fc80002 and U22 at 1fe80000.
I also noticed I can no longer readd my EEPROM and rwrite to it! tells me EEPROM not available.!!!
I can not even get the LED light up!!
I have also tried to us JKEY to reflash both U22 and U23 with no hope!

So is this the end of this receiver? Is there a solution to this problem?

[Chapster99]

Did you erase the TSOPs a few times before writing to them? Did you follow the 'resurrecting a dead 3100' instructions? If not, check the Echostar Files' section. One more question.....

Why did you do a junkyard when you have a jtag?

[texdss]

Did you erase the TSOPs a few times before writing to them? Did you follow the 'resurrecting a dead 3100' instructions? If not, check the Echostar Files' section. One more question.....

Why did you do a junkyard when you have a jtag?

Answers:
Yes I did erase it few times. 1st. time says "erased successfuly" then just to make sure I did it few more times kept coming back with "erased failed" but I did get FFFFFFFFF for boxkey after reset.

2- I did follow "resurrectig a dead 3100"

3- I did Junkyard because I originally I did not cut a whole at the bottum of receiver.

[qwertyuiop]

I had same problem before. I had to erase both TSOP by using Jkeys. Then wrote C23 first and then C22. I works.

[express99]

well same here 3100 with build EAFD tried everything but cant get it to boot led does not come on i have a jtag R-W-M dont know if this is any good for the 3100

[rayman190]

Where can I find the instructions for resurrecting a dead 3100

[Darnat]

In the Files under Echostar.

[hjs]

lofl,

Sorry brother...sounds like you've got a dead IRD. You did exactly what I did and I had the same results.

Because my IRD was actually subbed (but running a DSSRev card), I ended up buying another unit and cloning my old IRD. This involved loading IC23 with my old TSOP image and erasing IC22. Put the unit into the stream and viola! I was up and running...

I don't know if IC23 became hosed because of the jtaging procedure or due to the ECM or what...I just know that there was no way to write to it. It only took me 4 sleepless nights to determine the problem was due to hardware failure and not my procedure...

[sdavies]

Use Wall to program it. Program U22 / FC and then after it takes, then let it update in the stream. Do a search on Wall and learn how to use that program. It was made for 301 / 3100.

I never got jkeys to work with my 301's. You have to erase both tsops in Wall. then program 60000 of U22. Then close the program and unplug the receiver. Then plug it back in and load up wall again. You should now see your boxkeys here. Program U22 (FC) 200000 - a full write. It will probably use slow programming first and then will pick up halfway through. After its done, let it update in the stream

This process always worked for me.