Is there a way to program a rom 10, 11 or 102 and enter your own boxkeys for bev?

[fubr]

no answer yet?

maybe the guys missed this one or might be in another thread.

I still can't find the answer either, I keep messing up equipment / cards trying.

Getting very frustrating, I miss the good old days

Anyway, if anyone knows, please post....

[Pyotr]

It may be possible. Look into the program called GenDT08_SK 3.3. Depending on what you have it can be done.

[woods]

gendt08 will allow you to use your own ird# boxkeys and camid, it will generate all the needed tsop mods and the proper bin for a rom 10 101 or a 102

woods

do you need to do any reading or writing of the IRD or just the card? The problem is the 301 I have won't allow me to jtag it and the 6000 fails when reading or writing but will pull box keys. All the other ird's work fine with the jtag.

[seaboard18]

Originally Posted by 94ws7

do you need to do any reading or writing of the IRD or just the card? The problem is the 301 I have won't allow me to jtag it and the 6000 fails when reading or writing but will pull box keys. All the other ird's work fine with the jtag.

That is a ridiculous statement. Any 301 will allow you to jtag it. The 301.013's still have to be vid modded again even if you change to RSA OR No RSA tsop's. Just remember that and then the TSOP will read and write 100%. Try this link, it will help you remember the steps using Jkeys.

Vid Mod - 301-013 With Jkeys instructions.
http://www.bellexpress.vu/vidmod.html


And This Link, gives a great deal of discussion on the 301.013
http://www.dssftp.com/forum/showthread.php?t=19555

it is a 301 10 with bev e538, I am not the only one who has reported problems jtagging a 301 (in this case a true 3100) with bev e538.

If anyone has jtagged a 301 with e538 on it I would love to know how because I wouldn't be asking the initial question in this thread.

[seaboard18]

Originally Posted by 94ws7

it is a 301 10 with bev e538, I am not the only one who has reported problems jtagging a 301 (in this case a true 3100) with bev e538.

If anyone has jtagged a 301 with e538 on it I would love to know how because I wouldn't be asking the initial question in this thread.

From dudeman316's guide....... Rom10x

A little incite: The 301.005 is the JVC version of the 301.010. They both have two 2MB TSOPs generally referred to as IC22 (Flash 1, 1FE, u22, or z22) and IC23 (Flash 2, 1FC, u23, or z23). The u23 is the TSOP that contains your box keys & the starting address is 1FC00000 with length 200000. Be sure to erase & reflash, Flash 1 first then Flash 2.
.........................

A little known fact about the 301/3100 (.005&. 010) is as long as the bin files are good working bins , (check it with Flash Edit 2.0)

you can flash any 301.010/3100 (.005&. 010) build to any of the tsops just as long as you flash a matching EEPROM. For example, if

your IRD has the build sticker "EAED" & you want to flash an "EAFA" to it. Just make sure you flash the eeprom with "EAFD". Or if

yours is a "EACJ" and want to change it to an "EAFA" again the eeprom bin would have to be "EAFJ". Last letter pertains to the

eeprom, & 1st 3 to the tsop but in the case of the 301/3100 .010's you can use any EA** for TSOP... Just make sure you flash a

virgin EEPROM bin that matches the last letter of the build config sticker. They all begin with EA, end with D, J, or V, & the 3rd letter
can be changed to what you like as long as the bins are good.
..........................

Reflashing Flash 1 (IC22) with Jkeys ,


Follow this method for reflashing 301.010 flash 1 (IC22).

· 1. Hook up Jtag and make sure Jkeys gets your IRD# and Box keys (to be sure the Box Keys are correct, just make sure the IRD# in Jkeys matches that on the back of the IRD).

· 2. Now make sure Flash 1 (IC22 or 1FE00000) is selected in the Region area.

· 3. Now click on Flash Programming.

· 4. Once you click Flash Programming, you will arrive at the window.

· 5. At the Flash Programming window make sure Flash1 (IC22-29LV160) is selected.

· 6. Make sure Full is selected.

· 7. Click Erase to erase Flash 1, (may want to do this multiple times, 3 times is usually good, to assure it is completely empty).

· 8. Once it is erased click Program.

· 9. Now you will be at an Open window.

· 10. Select your flash 1 backup tsop image.

· 11. Click Open and Jkeys will begin to reflash Flash 1.
................................

Reflashing Flash 2 (IC23) with Jkeys ,


Follow this method for reflash 301.010 flash 2 (IC23).

· 1. With Jtag still hooked up & still having correct IRD# & Box Keys let's erase & reflash Flash 2.

· 2. Now make sure Flash 2 (IC23 or 1FC00000) is selected in the Region area.

· 3. Now click on Flash Programming.

· 4. Once you click Flash Programming, you will arrive at the window.

· 5. At the Flash Programming window make sure Flash2 (IC23-29LV160) is selected.

· 6. Make sure Full is selected.

· 7. Click Erase to erase Flash 2, (may want to do this multiple times, 3 times is usally good, to assure it is completely empty).

· 8. Once it is erased click Program.

· 9. Now you will be at an Open window.

· 10. Select you backup flash 2 tsop image.

· 11. Click Open and Jkeys will begin to reflash Flash 2.

Look, I'm not new at this, I tried everything you have said. This is a receiver that I could read and write to just fine until the e538 update. All I can say is take a 301 10 and make it bev, then allow it to update to e538 and see what happens.

I appreciate the help but I have tried all of that, I have another thread somewhere around here about the 301 problem.

Jkeys won't even pull up the boxkeys since the update and wall just errors right away, no slow programming, no erase, nothing.

I even tried the junkyard fix in a dish stream with no luck, I thought maybe I could restream it to dish and either use dish or hopefully be able to read and write and put e537 back on it.

Do a search for e538 and you will see, I am not the only one who has reported this problem.

I am tempted to try it with another 301 but I don't want to lose another, the others I can read and write just fine to as it is now.

[seaboard18]

Originally Posted by 94ws7

Look, I'm not new at this, I tried everything you have said. This is a receiver that I could read and write to just fine until the e538 update. All I can say is take a 301 10 and make it bev, then allow it to update to e538 and see what happens.

I appreciate the help but I have tried all of that, I have another thread somewhere around here about the 301 problem.

Jkeys won't even pull up the boxkeys since the update and wall just errors right away, no slow programming, no erase, nothing.

I even tried the junkyard fix in a dish stream with no luck, I thought maybe I could restream it to dish and either use dish or hopefully be able to read and write and put e537 back on it.

Do a search for e538 and you will see, I am not the only one who has reported this problem.

I am tempted to try it with another 301 but I don't want to lose another, the others I can read and write just fine to as it is now.

Well, I don't see what you have to lose. Don't mean to be sarcastic about this to you but its highly unlikely that this IRD can't be restored. You may want to look at AMD's page and look at the locking sequence of sectors. Its possible that your provider has figured a way to sabotage the IRD with the new firmware. Don't forget that they also test with the same tools we use. This is in part of why the new firmware is issued, in order to stop testing. Good luck, I am sorry I could not help you at this time. I will keep looking and if I find anything, I will post it.

Use the Search feature to find your tsop.
hxxp://www.spansion.com/

thanks for your help, I'll let you know fi I try another receiver

[seaboard18]

Originally Posted by 94ws7

thanks for your help, I'll let you know fi I try another receiver

Here is a link to a modded e538 tsop that is working as of 4-06. Maybe this will help you on your other 301. 010 -3100 BEV.

With the public rsa key, good for rom10to102
hxxp://www.rom10x.com/forums/showthread.php?t=25476&highlight=e538
File Type: zip Bell_3100_e538_u22_for_public_rsa.zip (290.8 KB, 154 views )

Best I can do.

Thanks, I am going to keep trying it and will try with a different receiver tonight. thanks again

[BGW]

Hard to belive that IRD went south because of a new flash.
If jkeys is talking to the tsop, simply erase it & re-write a new bin file to it.
If jkeys won't talk to the chip, then investigate why......
The problem will NOT be with the software already on the chip.
Re-read the instuctions for use of the jkeys program and follow step-by-step.
If still no go, either there is something preventing communication with the chip, (jtag or wiring connections) or the chip is dead.
End of story.
Good luck with it, and let us know what you find.
Regards,
BGW