Rom 102toRom10 Dec 20 Black screen FIX!!

[Intergalactix]

k anyone using 102torom10-8b possibly older needs to simply update the keys, here is a simple way incase nobody knows.
open the 102torom10-8b.bin file, click on PATCH then past lines below:

$C940=BFB7BFAE3FE6809DE7885A2AF8CCCC30
$C950=0000000000000000CDCDB7AE07E688E7
$CC30=C60309A886AA0F9097AE0F90D6D863D7
$CC40=0200905A5A2AF4CCC958000000000000
$D863=AF0CBD48D8516DDCFE44D60CA36E5942
$D873=3D731922275DC2C997965A0CA57927F9

click RUN PATCH then write card and all should be good dont forget to create your password on D0D6:

[RT02]

would this be for the 851p or the 834p

[coolgrin]

great job on the patch been trying to do a card for a couple day now only to get nothing but black screen.Keys change and i tried your patch and presto tv. thanks again for the great job

[Intergalactix]

dont matter, were not changing anything here but decryption keys, this will work on any rom 102torom10 as they are all based off the same bins key change methods are the same... this info is as current, future updates may be changed but i dont think so only thing that will change are the banks i posted herein.

[felix the cat]

Thank you Intergalactix .
I did not know it was so easy till i read your post.
got my 102torom10 going again (all ch. open except locals)
I even saved file and renamed it dish.bin for cemu.

Now i got to figure how to get my miami locals back ?

[Intergalactix]

well glad the post helped ya, not like i envented the wheel here... simply broke it down into laymens terms, as for getting locals... heh that will have to be another chapter.

[coolwind]

Need a new fix for black screen after yesterday
TKS Coolwind

[Crazy1_79]

coolwind, the patch at the top of this thread is your fix.

[df11]

HMMM! Tried above patch in my penga 8c and get message- card not valid for this receiver. Do I have to delete the lines that the patch replaces? I just pasted them above the existing $C940= ----- line.
Maybe I'll have to change to 8 b?:(

I'm real new to this. DUH!:o

[tavo]

coolwind, the patch at the top of this thread is your fix.

No, used this one myself and worked for about 12 hours and about 10 min. ago I got a black screen. I think they rolled the Idea keys again.. My 3M has the same keys of yesterday so I'm screwed. I am using the keys program from maestra.tv but getting no keys as of yesterday, I C/P this one.. We need a 102 to rom10-001-8-ab key auto roll.. ............




Patience is a virtue

[df11]

HMMM! Tried above patch in my penga 8c and get message- card not valid for this receiver. Do I have to delete the lines that the patch replaces? I just pasted them above the existing $C940= ----- line.
Maybe I'll have to change to 8 b?:(

I'm real new to this. DUH!:o

This gets more embarassing as I go along. Noticed I forgot to reapply the 3M patch so I redid it, now I get "your receiver is not yet authorized" so what the H*ll did I forget to do?:o

[tavo]

This gets more embarassing as I go along. Noticed I forgot to reapply the 3M patch so I redid it, now I get "your receiver is not yet authorized" so what the H*ll did I forget to do?:o

Are you using the mod for the reciever? If so ther should be no problems like these.. Just apply the Rom 102toRom10-8b run patch test patch and the same for the key patch and for the 3M patch.

[ussatravel]

No, used this one myself and worked for about tweleve hours and about 10 min. ago I got a black screen. I think they rolled the Idea keys again.. My 3M has the same keys of yesterday so I'm screwed. I am using the keys program from maestra.tv but getting no keys as of yesterday, I C/P this one.. We need a 102 to rom10-001-8-ab key auto roll.. ............
Patience is a virtue
Try the keys from dssevolution.

[tavo]

Try the keys from dssevolution.

Could you post a direct link as to where exactly they are?

[6speed]

Hello all, I'm new here...

I just updated my Keychange patch used in conjunction with the other usual steps/files.
My keychange patch just had this line in it but the code was different/old.

So I just used the line as listed below: $D863=AF0CBD48D8516DDCFE44D60CA36E5942

I was up and running everything open.

and still going strong 1 day later ;)

why would one need all those other lines? I'm curious as to what their purpose is, do they help autorolling?


k anyone using 102torom10-8b possibly older needs to simply update the keys, here is a simple way incase nobody knows.
open the 102torom10-8b.bin file, click on PATCH then past lines below:

$C940=BFB7BFAE3FE6809DE7885A2AF8CCCC30
$C950=0000000000000000CDCDB7AE07E688E7
$CC30=C60309A886AA0F9097AE0F90D6D863D7
$CC40=0200905A5A2AF4CCC958000000000000
$D863=AF0CBD48D8516DDCFE44D60CA36E5942
$D873=3D731922275DC2C997965A0CA57927F9

click RUN PATCH then write card and all should be good dont forget to create your password on D0D6:

[tavo]

Well No, the problem for me is not the key roll,I have the current ones. The problem is the current software for my 2800. I have a 301 working with latest software and a 2700 working @8.51p so I need to get my 2800 to 8.51p. Any one have the RSAnew 102to10 2700-2800-3700 but for the 851p it's not on the files section.

[felix the cat]

For anyone who might want to know
I added my blackout string, and local tiers under the patch that intergalactix posted ,then hit run patch then write to card .
now i have my locals to (in order and under the 100's) :D

[Intergalactix]

but isint 2700 and 2800 the same... to my memory it is if your 2700 @ 851P RSA moded then you might as well just copy the TSOP and put it on the 2800 now people talk about boot strap and build config... blah blah blah, the only reason you had to make sure you had the correct build config was with boot strap 10(something) i cant really remember but i do remember it was a very old 2700 receiver and the reason is because a trace going upto the eeprom was 0 instead of 1 (for example) thus making the build config only for that type (sorry if i lost ya, i have the documents if an explanation is really needed) but what im getting at is unless you have a very OLD 2700 build configs never mattered, i flash IRD's with what ever was handy, i cary only 1 flash of each type of IRD, those who dont belive me... open up the eeproms in a hex editor and see for yourself but my post here are not for arguing here. i simply pass on my experience, if i dont see it for myself then i wont write about it. another tip to finish off my day here is when flashing your IRD from fresh, always flash the eeprom with a virgin flash FIRST, then proceed to erase your TSOP(s) i find the IRD's dont go into "coma" on ya when you do this making a first time flash successful. i wish i could help everyone with problems they face but i work day and night here and just dont get much time for my own familly so i will try to post all i can in different posts to hopefully help those in need. i dont come on here very often but i find milli to be the coolest... like what other forum can i say fuckady fuck fuck fuck when i get pissed and not get banned... lol.
***happy holidays everyone.***
(all my knowlage comes from many people involved in this comunity, i take no credit for codes etc, just for the time i take to type it all out)

[Intergalactix]

For anyone who might want to know
I added my blackout string, and local tiers under the patch that intergalactix posted ,then hit run patch then write to card .
now i have my locals to (in order and under the 100's) :D

HEY!! great work, see your getting the hang of it now... lol

[snaplunt]

Idid mine last night with the patch above and still running you may have done something wrong

[tavo]

[QUOTE=Intergalactix]but isint 2700 and 2800 the same... to my memory it is if your 2700 @ 851P RSA moded then you might as well just copy the TSOP and put it on the 2800 now people talk about boot strap and build config... blah blah blah,

Well that's a good job buddy, tip of the hat to you for trying to explain it. You are reading of a how to.. You can never ever change a tsop from a 2700 to a 2800 that would going one step back, it simply wont work and you would have a black screen or ur reciever would not have a sat. signal trust me I have been down that road before with countless hours of testing. The build config is there for a reason, you can't erase a tsop from a 2800 and write a 2700 go ahead and do it and see what happens. You can't use a tsop from a 2800 CACA and try to use it with a 2800 CACO or to a 2800 DAIA get my point. The build config is not a blah blah blah thing and don't get me wrong guys I am not trying to bash anyone I am trying to help. Although some build config's are compatible with each other because I have used the when all else goes to crap but have a hard time with the testing. And yes the 2700/2800/3700 software is the same but with the same or compatible build config. It would be like trying to write a 2800 tsop to a 3900.. Hope this help someone out there and learn from my mistakes and testing...

[Intergalactix]

[quote=tavo]
Well that's a good job buddy, tip of the hat to you for trying to explain it. You are reading of a how to.. You can never ever change a tsop from a 2700 to a 2800 that would going one step back, it simply wont work and you would have a black screen or ur reciever would not have a sat. signal trust me I have been down that road before with countless hours of testing. quote]

i think you are trying to say that im getting my info from a howto?? not at all, i do have a 2700 in which i flashed with a 2800 TSOP bin... works great and still to this day, i dunno about going 2800 to 2700 cause i never done that yet thus i wont say forsure and i just dont guess, im not saying you are wrong in this matter neither simply cause i dont know your work, but i have successfully put a 2800 bin on a 2700 IRD, as for build configs i stand by what i say cause well, i have schematics i have read, which hinted me that it wouldnt matter, maybe it was luck but i flashed all 3100's (301) with different original build configs with my single tsop file which proved my schematics theory that build configs just dont matter, i must correct something tho and that is my test of the above meantioned were on done on newer 2700's (2700A) most build config's and i belive every build config on a 3100. im not telling people to just flash with what they wish here, im simply stateing my work hoping to find someone who agree's but im guessing nobody has really tried this. remember this tho, if you are going to jump to a completly differnet build config, dont forget to load a virgin eeprom FIRST! EEPROM's and the Flash's build config must match or problem will arise, so instead of modifying an eeprom to match the build config, simply load a virgin eeprom. (see what im saying here)
anyways i do enjoy a good chat about this kinda stuff aslong as there is no flaming, i will just leave others to flame away alone. i belive everybody has something good to say as long as its something good.
peace